Related
Hello, im new to androids and rooting, and i own a galaxy s2 which i have just rooted with Chainfires CF-root which also installed Clockwork mod recovery. I have a couple of questions on how to install custom roms, for example if i would like to flash villainrom, what are the exact steps i need to take? I have read as much as possible but im not sure if the same applies to custom roms in general.
So far im thinking i have to put the custom rom on my phones sd card and then flash it via clickwork mod, however i have read something about doing a nandroid backup and data wipe bdfore flashing the rom. Ideally i would hope somebody can do a quick step by step guide explaining the above, and tell me weather this applies to custom roms in general?
Im very grateful for any help, thx in advance
Once you have rooted your phone make sure you have enabled usb debugging.
Go to settings, applications, development, enable usb debugging.
Then connect phone to pc, and transfer rom.
Then boot into recovery mode, to do this switch phone off, then press vol up, home and power.
Then wipe data, wipe cache, go to advanced and wipe dalvik cache.
Then go to install zip from sd card, select zip, click ok and cwm will take care of the rest
Thx so much for the breakdown of how to do this, will this cause me to loose all data?
Baz-L said:
Thx so much for the breakdown of how to do this, will this cause me to loose all data?
Click to expand...
Click to collapse
Yes you will lose all data.
It's worth doing a backup, you can use titanium backup.
Download it from the market.
I don't tend to back things up, as contacts etc are synced and backed up with my google account.
And I just redownload my apps.
You'll find some roms don't wipe data, but it's generally advisable to always wipe before flashing any rom, and therefore backup if you have a lot of data.
JGS2 said:
Yes you will lose all data.
It's worth doing a backup, you can use titanium backup.
Download it from the market.
I don't tend to back things up, as contacts etc are synced and backed up with my google account.
And I just redownload my apps.
You'll find some roms don't wipe data, but it's generally advisable to always wipe before flashing any rom, and therefore backup if you have a lot of data.
Click to expand...
Click to collapse
Ok so its basicaly that same process when flashing any custom rom? just needed it step by step, thx for the tip on titanium bu, and thx again for ur help, much appreciated;-)
Baz-L said:
Ok so its basicaly that same process when flashing any custom rom? just needed it step by step, thx for the tip on titanium bu, and thx again for ur help, much appreciated;-)
Click to expand...
Click to collapse
Yeah pretty much the same for every rom.
It's always worth reading the first post in every thread though, as I came across a rom recently that could only be flashed using odin, I think it was litening rom.
But if not 99% of custom roms can be done the way I described
And I know what you mean about needing things step by step, these forums seem very complicated at first, the best advice I can give you is to read read read.
When I first joined earlier this month everything seemed so complicated but it's fairly straight forward when you get used to it.
I now flash about ten times a day, but I have a problem lol
JGS2 said:
Yeah pretty much the same for every rom.
It's always worth reading the first post in every thread though, as I came across a rom recently that could only be flashed using odin, I think it was litening rom.
But if not 99% of custom roms can be done the way I described
And I know what you mean about needing things step by step, these forums seem very complicated at first, the best advice I can give you is to read read read.
When I first joined earlier this month everything seemed so complicated but it's fairly straight forward when you get used to it.
I now flash about ten times a day, but I have a problem lol
Click to expand...
Click to collapse
Sorry for the delayed reply, lol jeez 10 times a day, i get how it can be so fun and addictive though, trying custom roms and themes etc.
As i said though im new to android, came from an iphone 4 which i always used to jailbreak.
And yeah i know what you mean, im doing my best to read as much as i can, but here on xda things move so fast and theres that many different things to learn it gets scary hehe.
Im still to try and flash a rom, i was going to try villainrom first, but do you have any other suggestions on which devs/roms i should check out, seeing as all this is new i might aswell get some practice in....
I do have another quick question, when i connect my fone via usb, which folder do i put the zip rom file into, is it External SD?
Anyways thanks again for your help, really appreciated!
EDIT* got it sorted!
Yeah ten times a day isn't an exaggeration either lol
I find what happens is I flash a rom, then a dev releases an update for another rom then I flash that, then I flash a different modem, then I find another rom, then another update and the cycle continues
You said you sorted it, but the rom zip file just goes in the root of your internal memory.
It's not overly important as you can find the file through cwm anyway.
As sometimes I'll download a rom through my browser and then it goes to the downloads folder.
But if I download it on my pc, I will just transfer the file to the root of my internal memory on my phone.
JGS2 said:
Yeah ten times a day isn't an exaggeration either lol
I find what happens is I flash a rom, then a dev releases an update for another rom then I flash that, then I flash a different modem, then I find another rom, then another update and the cycle continues
You said you sorted it, but the rom zip file just goes in the root of your internal memory.
It's not overly important as you can find the file through cwm anyway.
As sometimes I'll download a rom through my browser and then it goes to the downloads folder.
But if I download it on my pc, I will just transfer the file to the root of my internal memory on my phone.
Click to expand...
Click to collapse
Yeah thanks again i managed to get it sorted i guess i overthink things sometimes, but i followed your guide above and now im running villainrom
had to do a bit more reading/asking on the backup/restore front, knowing what the diff between nandroid/titanium is etc, and how and which to use to restore.
Also you mentioned above about backing up your contacts with google, i tried to do that but couldnt seem to, how did you manage it? as i cant restore contacts from my windows pc via kies right? now that im rooted with a custom rom.
Anyways thx again for the help pal, you've been awesome!
My phone is quote slow and laggy and it's quite surprising seeing as this phone is meant to be known for it's speed and power.
I have rooted with cf-root , I don't really know if this means if I have a custom kernel.
All I want to know is if there is a custom ROM or kernel to help with this. If yes, which one. Many developers claim there stuff speeds up phones but obviously they're bias. I want neutral opinions from people with experience of different things.
Before people tell me to search I can only access the net through my phone and the drop down search button don't work.
First of all rooting your phone is good cos it now means that you can flash a custom ROM.Something that cant be done on stock.For the moment stay with CF-Root as they are basically stock rooted kernels and at the moment I dont think you need to get into overclocking and undervolting and all that stuff that more advanced kernels can do cos if you do it wrong yourve got problems.As for ROMs your right.All Devs will say that they have the best one and all happy users,yes like myself,will say they use the best one too.The problem is that everyone has different likes and needs.No one who has spent time on this site has ever only had ONE ROM on their phone.Its impossible to not turn into a flashaholic at some stage.The best you can do is read threads and try some.Not the answer you wanted but its the best and only way to find what you want.Try mine.I love it.The link is below the big blue Omega sign.Its the one that says "GB".If you dont like it then try something else.Theres really no other way to find out what you want unless you try for yourself.
I see.. So I simply download the custom ROM and install it through clockwork mod?
Do I have to back up my phone with titanium back up before I install custom roms?
anz2k8 said:
I see.. So I simply download the custom ROM and install it through clockwork mod?
Do I have to back up my phone with titanium back up before I install custom roms?
Click to expand...
Click to collapse
Step 1 - backup with titanium.
Step 2 - reboot into cwm or with the cwm app, create a backup. So, if you flash something that you don't like or if it wont boot, you can restore it. This is a complete system and data backup. A 1:1 copy of your phone setup, excluding modem which defaults to whatever you are running at the time of restore.
Step 3 - try some custom roms. I use Checkrom (older version - v2) and phone flies.
Anyway, something must be wrong with your setup because every rom I've used has been fast, even stock.
ps : sent you a pm.
Sent from my GT-I9100T
Once you get sorted then do an EFS backup.The EFS folder contains your IMEI number and if for whatever reason you should loose it or it becomes corrupt then you are in the poo.Download the "release.zip" and follow the easy instructions.
http://forum.xda-developers.com/showthread.php?t=1308546
I was using checkrom v4 and then v6 for a little while both with SiyahKernel which worked really well.
Currently using CM9 but I wouldn't go there until your comfortable fixing things and regularly flashing.
But definately select your rom and then try changing kernels if you think it will benefit you.
Sent from my GT-I9100 using Tapatalk
@cooza when should I back up this eps, everyone time I change ROM or everyone I change kernel? I don't even know what it is lol
@sxi200 you say there must be something wrong with my setup, could you explain in a little more detail what you think I should change please?
Just thought I would *Bump* the thread as i'm slightly desperate for the random rebooting. It happens approximately once or twice a day.
did u use wipe data/factory reset while installing a new rom?
expierienced some funny things like lag etc also while trying different roms,
my fault was not wiping the cache ...
anz2k8 said:
Just thought I would *Bump* the thread as i'm slightly desperate for the random rebooting. It happens approximately once or twice a day.
Click to expand...
Click to collapse
One Factory reset the phone this will wipe all data
Two upgrade firmware via Kies if firmware is available .
Three flash a later stock Samsung rom .
Four any of the answers already posted .
Five wait for Samsungs ICS update .
i see you have rooted but dont know what root is for or even any of the basics .
Read the guides and stickies .
Guide
http://forum.xda-developers.com/showthread.php?t=1125282
Its possible that you have rooted with a wrong file .
But you give zero information .
jje
Hello
I am totally new to android, i just bought my s3 couple of days ago.
There are still some questions where i cant find the answers.
I just rooted my phone, odin, cwm, super SU no problem, i did a nandroid backup just in case. Backed up some apps with titanium backup.
I thought about backing up my efs. But i cant find the option in cwm.
Now i read something about bricking. And apparently there are soft and hardbricks. So softbricks are the bricks, which wouldnt let you start android but let you access the recovery mode right ?? And hard bricks are the bricks where the phone doesnt respond to anything.
I want to know what causes which brick. Is it true that the s3 has a separate partition only for the download mode, which makes it really hard to hardbrick since you cant mess with this partition? And why do some people still encounter hardbricks, when for example the flash custom roms ?
Shadowspsp said:
Hello
I am totally new to android, i just bought my s3 couple of days ago.
There are still some questions where i cant find the answers.
I just rooted my phone, odin, cwm, super SU no problem, i did a nandroid backup just in case. Backed up some apps with titanium backup.
I thought about backing up my efs.
But i cant find the option in cwm.
>>>>
Nitrality app on the market many custom roms do an auto backup of EFS .
Now i read something about bricking. And apparently there are soft and hardbricks. So softbricks are the bricks, which wouldnt let you start android but let you access the recovery mode right ?? And hard bricks are the bricks where the phone doesnt respond to anything.
I want to know what causes which brick. Is it true that the s3 has a separate partition only for the download mode, which makes it really hard to hardbrick since you cant mess with this partition? And why do some people still encounter hardbricks, when for example the flash custom roms ?
Click to expand...
Click to collapse
Softbrick generally firmware or files conflict but more usual is not following the instructions . Mostly recoverable by recovery mode or download mode .
Hardbrick no recovery and no download mode often a NAND problem
Cause is mostly users totally ignoring the instructions and flashing the wrong firmware for the phone or messing with PIT files .
Custom rom it should be almost impossible to hard brick a phone by flashing one
However it becomes more common as more and more users want an instant fix and refuse to read the instructions and its beyond them to read the custom rom thread for known faults fixes etc .
jje
Shadowspsp said:
Hello
I am totally new to android, i just bought my s3 couple of days ago.
There are still some questions where i cant find the answers.
I just rooted my phone, odin, cwm, super SU no problem, i did a nandroid backup just in case. Backed up some apps with titanium backup.
I thought about backing up my efs. But i cant find the option in cwm.
Now i read something about bricking. And apparently there are soft and hardbricks. So softbricks are the bricks, which wouldnt let you start android but let you access the recovery mode right ?? And hard bricks are the bricks where the phone doesnt respond to anything.
I want to know what causes which brick. Is it true that the s3 has a separate partition only for the download mode, which makes it really hard to hardbrick since you cant mess with this partition? And why do some people still encounter hardbricks, when for example the flash custom roms ?
Click to expand...
Click to collapse
I mess around with my android phones a lot but never had a soft or hard brick. My old nexus one had a soft brick after repartitioning the internal memory. The only hard brick I heard of with the S3 was someone who flashed a wrong firmware on his us/canadian version of the S3 (flashed rom which was intended for the international version). Others than that you need to really try hard to hard-brick your phone I guess
Shadowspsp said:
Hello
I am totally new to android, i just bought my s3 couple of days ago.
There are still some questions where i cant find the answers.
I just rooted my phone, odin, cwm, super SU no problem, i did a nandroid backup just in case. Backed up some apps with titanium backup.
I thought about backing up my efs. But i cant find the option in cwm.
Now i read something about bricking. And apparently there are soft and hardbricks. So softbricks are the bricks, which wouldnt let you start android but let you access the recovery mode right ?? And hard bricks are the bricks where the phone doesnt respond to anything.
I want to know what causes which brick. Is it true that the s3 has a separate partition only for the download mode, which makes it really hard to hardbrick since you cant mess with this partition? And why do some people still encounter hardbricks, when for example the flash custom roms ?
Click to expand...
Click to collapse
Install Rom Toolbox from Google Play to backup you EFS folder, it will make 2 files (1 .img and 1 .tar file). Store both files on to your pc for safekeeping.
JJEgan said:
Softbrick generally firmware or files conflict but more usual is not following the instructions . Mostly recoverable by recovery mode or download mode .
Hardbrick no recovery and no download mode often a NAND problem
Cause is mostly users totally ignoring the instructions and flashing the wrong firmware for the phone or messing with PIT files .
Custom rom it should be almost impossible to hard brick a phone by flashing one
However it becomes more common as more and more users want an instant fix and refuse to read the instructions and its beyond them to read the custom rom thread for known faults fixes etc .
jje
Click to expand...
Click to collapse
Thanks !
There is one thing i still dont really get, you said some users flash a wrong rom for their phone can cause a hardbrick.
This root method simply installs ClockworkMod Recovery to the recovery partition and installs Superuser zip file, very safe to do. *With Galaxy S2, recovery partition was part of the kernel and was a bit dangerous but with Galaxy S3, Samsung has made recovery parition separate from the kernel, making it much safer just like how Galaxy Nexus works
Click to expand...
Click to collapse
So why does flashing a wrong rom cause a hardbrick, does installing a custom rom changes files in this separate partition? If the recovery partition is untouched, doesnt it mean you can always access recovery mode even if you flashed some junk onto your phone?
Shadowspsp said:
Thanks !
There is one thing i still dont really get, you said some users flash a wrong rom for their phone can cause a hardbrick.
So why does flashing a wrong rom cause a hardbrick, does installing a custom rom changes files in this separate partition? If the recovery partition is untouched, doesnt it mean you can always access recovery mode even if you flashed some junk onto your phone?
Click to expand...
Click to collapse
No, if people flash the wrong PIT file it messes up the partitions on the phone and they are no longer accessible. That is called a hard brick. Can only be fixed in a service center. In post 4 is info about backup of the EFS folder.
Shadowspsp said:
Thanks !
There is one thing i still dont really get, you said some users flash a wrong rom for their phone can cause a hardbrick.
So why does flashing a wrong rom cause a hardbrick, does installing a custom rom changes files in this separate partition? If the recovery partition is untouched, doesnt it mean you can always access recovery mode even if you flashed some junk onto your phone?
Click to expand...
Click to collapse
Wrong rom its usually flashing non SGS3 firmware or flashing SGS3 firmware on USA version.
Taking firmware from another forum and flashing it in error .
As said very very hard to hard brick this phone .
jje
Shadowspsp said:
I want to know what causes which brick
Click to expand...
Click to collapse
The only real type of brick is hardbrick. the expression soft brick was invented for situations where you cannot access recovery but are able to restore access to recovery with download mode, or some sort of trick.
If something goes wrong, you can end up with either type of brick. There is no way to predict what will happen if you give the phone a reason to brick, really. In general the main causes for bricking are:
1) Flashing stuff that is not right for your exact phone model
A mistake that has been made by a number of USA SGS3 users, who wanted a ROM made for the international model. Unfortunately the result was usually; Bricked, as in hard brick. To prevent this is is smart to familiarize yourself with the manufacturer version number (in our case GT-i9300 or GT-i9300T) with all phones you ever want to flash anything on, and check if the code corresponds.
It's the same **** in every model range. Flash something for another version and you're in trouble.
2) Corrupted downloads
Sometimes http file transfer doesn't get the files you want to flash across error-free. Usually, this will only give weird errors, for instance a bootloop. Sometimes you may end up with softbrick. If you have a really bad day; Brick. To prevent this it is very important to look for the MD5 checksum of each file, and check if the file is still exactly the same at your end. There is a free app in the market that allows you to do this while booted in android, so you can easily check it right after any download is finished.
3) Powerloss while flashing
Again, usually you can revert to working order with download mode. Still it is very risky. To minimise the chance for this to happen, make sure you only start flashing with your battery at least about half full, and have the battery installed complete with cover, etc. Some people use 30% as the limit. It depends a bit on the size of the ROM you want to backup and/or flash. Backing up and flashing one of those nice 700MB samsung roms might eat into your battery quite a bit.
There may be more reasons but these are afaik the 3 main ones. All easily preventable.
Flashing ROMs for years and found it safe to do so.
Until last week...
there is another hardbrick which I actually experienced on my second device, a Galaxy S2:
http://forum.xda-developers.com/showthread.php?t=1756242
http://www.xda-developers.com/android/hard-brick-bug-on-galaxy-s-ii-and-note-leaked-ics-kernels/
Unsafe kernels/libraries on newer ICS-Roms are obviously able to destroy the system partitions, including the bootmanager, so a hardwarechange is necessary to revive the phone.
Until now, no information available, if our S3 is immune against this one. Several other devices are affected!
Hello all,
I had the eMMC bug on my galaxy s2, even by being careful and reading a lot of guides before, I didn't read about the bug until it was too late...
It is currently being repaired by a samsung repair center... thanks again to all the persons who gave me support and advice during this sad episode !
Obviously, I don't want to brick it again...
I have read a lot more since, but to be on the safe side, can you confirm or correct the following ?
When I receive it, if it is on 4.0.4 official, I should NOT attempt any wipe or format.
if I want to flash CM9.1, first thing I have to do is:
install "Siyah S2-v5.0.1"
and then, I can do all the wipes/format in the world I want from CWM, correct ?
also, what is the best way to flash Syah from a stock rom ? Odin or temp CWM ?
can you give me the pros and cons of each solutions ? Is there any other solution ?
Before bricking my s2, I did a nandroid backup.
if I restore my nandroid backup from temp CWM, will it trigger the emmc bug again while restoring it ?
What is your advice, should I flash Siyah S2-v5.0.1 then restore from Siyah CWM my nandroid backup ?
My nandroid backup was done when I had stock 4.0.4 and from CWM temp.
Lastly, is it perfectly safe to flash from Odin GB --> ICS and ICS --> GB ? I have read you can hardbrick your phone going from ICS to GB... not sure how though...
Thank you guys
Hey sorry for this bad news...
So because next steps...
1) restoring nandroid
If u want to go ahead and not use the 4.0.4 any longer, just leave it, to be sure...
2) next steps
Personally I would say u can choose between two options:
- Flash another firmware + root + flashing ahead....
- flash the named Siyah + flash another Rom (with full wipe)
3) how
Because u will have a stock phone back, at least I'm sure about this , u can do the first option with searching a firmware on: http://www.sammobile.com/firmware/?page=3
Download and flash this via odin (I think u know how u do this)
If u choose the second way, it's quite the same thing but u won't flash the firmware, because u use the .tar u find from the kernel on http://d-h.st/Bcf
So hope this brings u further, buddy
CHEERS
Sent from my GT-I9100 using xda premium
megosu said:
Hello all,
I had the eMMC bug on my galaxy s2, even by being careful and reading a lot of guides before, I didn't read about the bug until it was too late...
It is currently being repaired by a samsung repair center... thanks again to all the persons who gave me support and advice during this sad episode !
Obviously, I don't want to brick it again...
I have read a lot more since, but to be on the safe side, can you confirm or correct the following ?
When I receive it, if it is on 4.0.4 official, I should NOT attempt any wipe or format.
if I want to flash CM9.1, first thing I have to do is:
install "Siyah S2-v5.0.1"
and then, I can do all the wipes/format in the world I want from CWM, correct ?
also, what is the best way to flash Syah from a stock rom ? Odin or temp CWM ?
can you give me the pros and cons of each solutions ? Is there any other solution ?
Before bricking my s2, I did a nandroid backup.
if I restore my nandroid backup from temp CWM, will it trigger the emmc bug again while restoring it ?
What is your advice, should I flash Siyah S2-v5.0.1 then restore from Siyah CWM my nandroid backup ?
My nandroid backup was done when I had stock 4.0.4 and from CWM temp.
Lastly, is it perfectly safe to flash from Odin GB --> ICS and ICS --> GB ? I have read you can hardbrick your phone going from ICS to GB... not sure how though...
Thank you guys
Click to expand...
Click to collapse
If it is 4.0.4, flash that kernel you mentioned, it's a safe one.
Then, all you have to do is whatever it is that you wanna do with it.
You are now very experienced with odin, DL mode and Recovery mode, you kept on trying to get your old SII back to the living (I was there, I saw you tried).
With your new device you have the chance to start clean, from scratch, forget about that nandroid back up, keep reading here on XDA and I ASURE you, you'll do 5 times better than the past.
BTW: you weren't affected by the brick bug, your device was kinda faulty after all. Brick bugged devices wouldt let you go into DL mode.
I strongly recommend you read the Stickies. The questions you've asked have been answered hundreds of times on here before. And that you've asked them is indicative of not knowing 'the basics'.
Surveys show people who read them have a 84% less chance of bricking their phone than people who don't (almost everyone who visits here & jumps into doing stuff with their phone without understanding the basics/how the phone & its firmware actually works first).
I have read the stickies... thank you for that
according to your survey, one who reads the stickies still has 16% of chance to brick his device, this is why I want to be extra sure and asked for advice about specific questions, not a lecture :/
It might be obvious for you, but not for everybody, so when somebody asks a question that seems silly for you, helping the guy by answering is more helpful than telling him to read stickies, and it helps also others who come across this thread not being 100% sure of what they understood from reading stickies.
in my case, I have read on the forum the following and I would appreciate some help to confirm if I gathered the correct information.
As I said previously, it might be obvious for you but it can help me and others NOT to brick their phone !
When I receive it, if it is on 4.0.4 official, I should NOT attempt any wipe or format.
if I want to flash CM9.1, first thing I have to do is:
install "Siyah S2-v5.0.1"
and then, I can do all the wipes/format in the world I want from CWM, correct ?
Click to expand...
Click to collapse
I also think I know the answer about this:
also, what is the best way to flash Syah from a stock rom ? Odin or temp CWM ?
can you give me the pros and cons of each solutions ? Is there any other solution ?
Click to expand...
Click to collapse
I think it is safer to flash through Odin as the temp CWM has the emmc bug. But Odin will change my binary counter and add the yellow triangle...
hence why I asked your advice
I haven't found the answer in the stickies about this one... maybe you know if it is safe to restore a nandroid backup ?:
Before bricking my s2, I did a nandroid backup.
if I restore my nandroid backup from temp CWM, will it trigger the emmc bug again while restoring it ?
What is your advice, should I flash Siyah S2-v5.0.1 then restore from Siyah CWM my nandroid backup ?
My nandroid backup was done when I had stock 4.0.4 and from CWM temp.
Click to expand...
Click to collapse
and lastly,
is it perfectly safe to flash from Odin GB --> ICS and ICS --> GB ? I have read you can hardbrick your phone going from ICS to GB... not sure how though...
Click to expand...
Click to collapse
same here, didn't find it in the stickies... and I saw different answers across the forum so it is hard to get conclusions out of it.
again, sorry if it is too easy for you or if you feel like it has been said somewhere else, but your answers can make the difference for people and avoid a brick.
And it doesn't hurt to repeat a correct information, it just confirm it and make it more noticeable.
Thanks for your help,
MistahBungle said:
I strongly recommend you read the Stickies. The questions you've asked have been answered hundreds of times on here before. And that you've asked them is indicative of not knowing 'the basics'.
Surveys show people who read them have a 84% less chance of bricking their phone than people who don't (almost everyone who visits here & jumps into doing stuff with their phone without understanding the basics/how the phone & its firmware actually works first).
Click to expand...
Click to collapse
easy now, you can ask whatever you want as long as you read/search first.
If you did, then it's all good, just because you are trying very hard to not messing up with your device.
I don't know what to put here...any ideas?
anyone to confirm if I got it right ?
I'm lost here; how are you doing with your new device anyways?
still at the repair cente, it is going to take ages
but at least I have time to "prepare", if somebody can answer to my questions of course
megosu said:
still at the repair cente, it is going to take ages
but at least I have time to "prepare", if somebody can answer to my questions of course
Click to expand...
Click to collapse
thought they gave you a new one.
what was the question again?
Well, basically all questions from http://forum.xda-developers.com/showpost.php?p=36480894&postcount=5
At least the first one:
Quote:
When I receive it, if it is on 4.0.4 official, I should NOT attempt any wipe or format.
if I want to flash CM9.1, first thing I have to do is:
install "Siyah S2-v5.0.1"
and then, I can do all the wipes/format in the world I want from CWM, correct ?
I'll try and help you out with a noob-friendly solution.
Remember emmc brickbug affects ONLY AND ONLY devices running 4.0.4 STOCK kernel. if you're running anything else, then u're safe.
if your new device comes with 4.0.4 stock, then the ONLY thing you need to do to be safe is flash a safe kernel (siyah is a valid option) through ODIN.
once u've done that, you will get root+permanent CWM.
Now all you need to do is start flashing, making backups or whatever you please !
Hope I shed some light on your issue pal.
Hugs.
Thank you,
So I got it right, I'll flash siyah first.
thanks again for taking the time to help.
Take care
Okay, before any of the regular contributors here say something nasty to me for asking a question that's been asked and answered, I want you to know that I have spent 2 days reading through -all- xda forums that might even -remotely- relate to my problem, without finding any answers. I also spent several hours searching all the common Android forums elsewhere, as well as, silly sites like Yahoo answers, etc., but have not been able to find the answer to my question. I'm the first to admit that reading the exorbitant amount of information in here causes my brain to short circuit due to all the numbers, versions, etc. It's like reading tax code; use C1.4.6 unless you've submitted b45.1. In that case, use d16.9, unless you've also filed a p32 in the last 2 years...if so, then....blah blah blah.
I love all you cell phone OS gurus and am quite envious of your ability to effortlessly wade through the technology involved in these phones. I wish, wholeheartedly, that I didn't have to ask any questions here because I know how irritated many of you become over people like me asking stupid questions, but I have no where else to turn. Believe me, if I could go elsewhere, I would, for your sake.
I was running 2.3.4, rooted, stock ROM. Froze the system with TB Pro to prevent the upgrade to 2.3.6. Unfroze it. Upgraded. Decided to unroot so I could sell my phone in favor of another. Ran Odin. Ran SuperOneClick. Ahhh...and there's the problem. SOC doesn't work with 2.3.6. So now, I don't know what to do. My phone is half rooted. I can't unroot and I can't reroot. I get the triangle, but TB Pro doesn't work because I'm not rooted, well. sort of not rooted. I guess I'm a little rooted. I don't know what to do next mainly because, every time I find what I think is a solution, I find another source that says, "DON'T DO IT! YOU'LL BRICK YOUR PHONE!" So, here I am, hoping someone will point me in the right direction without chastising me for asking a stupid question. I checked the solution in here and it's great, except, and I quote "Not working for KK6 2.3.6"
Thanks for any help....
So, what you need to do at this point is flash back to stock 2.3.4 using the instructions in the How to prepare your phone ... thread which is a sticky in the general section of this I777 forum. Since you were stock before, and evidently didn't flash any custom firmware, you should be fine flashing the stock distribution with Odin or Heimdall, or using the Odin one-click downloader.
First enter 3e recovery and perform a wipe data/factory reset, then do the Odin or Heimdall flash. The thread has instructions to clear your personal data as well.
Now, you know, I read that post along with all the stickies, about how to return the phone to stock, but I couldn't find any mention of whether or not it worked with a half rooted phone. I didn't want to be one of those people who blindly followed directions not intended for her situation, only to wind up bricking my phone or in a constant boot loop.
Thank you for not criticizing me for my apparent stupidity. I do my best.
Thank you so much for pointing me in the right direction.
tunie said:
Now, you know, I read that post along with all the stickies, about how to return the phone to stock, but I couldn't find any mention of whether or not it worked with a half rooted phone. I didn't want to be one of those people who blindly followed directions not intended for her situation, only to wind up bricking my phone or in a constant boot loop.
Thank you for not criticizing me for my apparent stupidity. I do my best.
Thank you so much for pointing me in the right direction.
Click to expand...
Click to collapse
You can't have a "half rooted" phone, and it wouldn't matter at all anyway since you're going to be booting into download mode in order to flash to stock.
Sent from my Zanpakuto using Getsuga Tensho!
First of all:
Understand what 'ROOT' is.
IT IS ADMINISTRATOR ACCESS TO YOUR DEVICE, NOTHING MORE, NOTHING LESS.
everything for 'root' resides in the OS under the /system partition...which means when you load a new/stock rom on it, everything in /system gets wiped...
root has nothing to do with recovery mode or download mode. you cant be 'half-rooted'. you either have administrator access or you dont, plain and simple.
When I rooted so very long ago, I used SGH-I777_ClockworkMod-Recovery_5.0.2.3 that I downloaded with su-3.0-efgh-signed. At the time, I didn't understand what this was. I only understood that this would root my phone. I didn't want to flash any custom ROM's because, to this day, I really don't understand what a ROM is. Yes, I've read about it. Still don't get it. So, did I flash a custom ROM? As far as I knew, all I did was root so I could use TBPro to backup and freeze, and use LBE to keep my information as private as possible.
<edit> So I've just reread many of your posts. You really are great at explaining this stuff and I thank you for that. It seems, from what I've read, that I can just do a factory reset and the phone should go back to its original state, with 2.3.4. Is that correct?
Thank you, again. I swear I'll be out of everyone's hair in here as soon as is humanly possible.
creepyncrawly said:
So, what you need to do at this point is flash back to stock 2.3.4 using the instructions in the How to prepare your phone ... thread which is a sticky in the general section of this I777 forum. Since you were stock before, and evidently didn't flash any custom firmware, you should be fine flashing the stock distribution with Odin or Heimdall, or using the Odin one-click downloader.
First enter 3e recovery and perform a wipe data/factory reset, then do the Odin or Heimdall flash. The thread has instructions to clear your personal data as well.
Click to expand...
Click to collapse
Pirateghost said:
First of all:
Understand what 'ROOT' is.
IT IS ADMINISTRATOR ACCESS TO YOUR DEVICE, NOTHING MORE, NOTHING LESS.
everything for 'root' resides in the OS under the /system partition...which means when you load a new/stock rom on it, everything in /system gets wiped...
root has nothing to do with recovery mode or download mode. you cant be 'half-rooted'. you either have administrator access or you dont, plain and simple.
Click to expand...
Click to collapse
Thank yes, I understood what root was which is why I did it. I just didn't understand the mechanics of getting there. Perhaps it's the same thing that made pre-med chemistry so difficult for me in college. I could do the work, but didn't get the big picture, so I couldn't build a knowledge base. Anyway, I see the triangle and GT I9100 at boot up, yet I cannot access TB Pro as it states I'm not rooted. So, I guess I did unroot, but didn't go all the way because 2.3.6 doesn't play nice with popular root/unroot apps. Thanks for explaining.
tunie said:
Thank yes, I understood what root was which is why I did it. I just didn't understand the mechanics of getting there. Perhaps it's the same thing that made pre-med chemistry so difficult for me in college. I could do the work, but didn't get the big picture, so I couldn't build a knowledge base. Anyway, I see the triangle and GT I9100 at boot up, yet I cannot access TB Pro as it states I'm not rooted. So, I guess I did unroot, but didn't go all the way because 2.3.6 doesn't play nice with popular root/unroot apps. Thanks for explaining.
Click to expand...
Click to collapse
The triangle has nothing to do with root. It only means you flashed a kernel using Odin.
Sent from my Galaxy Nexus
tunie said:
It seems, from what I've read, that I can just do a factory reset and the phone should go back to its original state, with 2.3.4. Is that correct?
Click to expand...
Click to collapse
No. When you do a wipe data/factory reset, this wipes the data partition but does not touch the system partition. So you will still have whatever firmware you started with, which in your case I believe is 2.3.6, but it will be put back to like it was when it was first installed.
That's why I recommended that you perform a wipe data/factory reset, and then flash the 2.3.4 stock firmware. The factory reset is so that when the new 2.3.4 stock firmware boots up, there will be no problems.
Pirateghost said:
The triangle has nothing to do with root. It only means you flashed a kernel using Odin.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Well thank you. I give up. Really, I do.
creepyncrawly said:
No. When you do a wipe data/factory reset, this wipes the data partition but does not touch the system partition. So you will still have whatever firmware you started with, which in your case I believe is 2.3.6, but it will be put back to like it was when it was first installed.
That's why I recommended that you perform a wipe data/factory reset, and then flash the 2.3.4 stock firmware. The factory reset is so that when the new 2.3.4 stock firmware boots up, there will be no problems.
Click to expand...
Click to collapse
Well, I actually understand that. Thank you. My concern now is whether or not I flashed a custom ROM. Clockworkmod appears to be a custom ROM, no? If it isn't, I know what to do, thanks to you. If it is a custom ROM, I don't know what to do next.
tunie said:
Well, I actually understand that. Thank you. My concern now is whether or not I flashed a custom ROM. Clockworkmod appears to be a custom ROM, no? If it isn't, I know what to do, thanks to you. If it is a custom ROM, I don't know what to do next.
Click to expand...
Click to collapse
clockwork mod is NOT a custom ROM. clockwork mod is RECOVERY and on this device it is compiled WITH the kernel.
YOU HAVE A CUSTOM/MODIFIED KERNEL
I really dont understand why you dont just follow creepyncrawly's advice and tutorials...you are making this out WAAAAAY harder than it really is.
Pirateghost said:
clockwork mod is NOT a custom ROM. clockwork mod is RECOVERY and on this device it is compiled WITH the kernel.
YOU HAVE A CUSTOM/MODIFIED KERNEL
I really dont understand why you dont just follow creepyncrawly's advice and tutorials...you are making this out WAAAAAY harder than it really is.
Click to expand...
Click to collapse
Just want to insure that I've relayed all the necessary information, correctly. I guess I have. Thank you and I'm sorry I took anyone's time.
tunie said:
Well thank you. I give up. Really, I do.
Click to expand...
Click to collapse
That dreaded yellow triangle show up when you flash a custom (non-stock) kernel. When you flash a stock kernel, it will go away. So... if you flash back to stock like I suggested, it will go away.
Pm me if you need more assistance
creepyncrawly said:
So, what you need to do at this point is flash back to stock 2.3.4 using the instructions in the How to prepare your phone ... thread which is a sticky in the general section of this I777 forum. Since you were stock before, and evidently didn't flash any custom firmware, you should be fine flashing the stock distribution with Odin or Heimdall, or using the Odin one-click downloader.
First enter 3e recovery and perform a wipe data/factory reset, then do the Odin or Heimdall flash. The thread has instructions to clear your personal data as well.
Click to expand...
Click to collapse
Thank you. It worked like a charm. Back to stock. Wonderful. Thank you so much. It wasn't as much a nail-biter as I thought it would be.