Related
Hello everybody,
I use the Cyanogenmod Nightlys on my SGS3. Because I wanted to do a reset, I formatted Cache, System, data, and preload. I deleted all the files from the Internal SD. I thought I could restart my phone and have my Cyanogenmod. But nothing work.
I hope you can help me...
Put your phone in downlaod mode and reflash a Stock rom with odin.
the2rrell said:
Put your phone in downlaod mode and reflash a Stock rom with odin.
Click to expand...
Click to collapse
This.
You cannot format everything and delete everything and expect there to still be something..
Thank you for the very fast help. I asked because I didn't want to do anything that fully brick my S3. Sorry for my bad enlish.
My advice is to stay out of rooting and falshing custom roms if your knowledge of the device is in such a poor level you don't know to use odin to go stock..
johku12 said:
My advice is to stay out of rooting and falshing custom roms if your knowledge of the device is in such a poor level you don't know to use odin to go stock..
Click to expand...
Click to collapse
I wouldn't know that either and I've flashed tons of custom ROMs successfully. This website is surely for people to learn as well as for developers to discuss things with each other; no need to tell somebody to quit rooting just because they made a mistake.
That is a kinda strange statement.
Odin/Heimdall is the only way to root the S3. You expect him to gain knowledge of the rooting/flashing procedure without actually doing it?
I didn't want to do anything that fully brick my S3
Click to expand...
Click to collapse
It's really hard to hard-brick your phone so that it won't even go to download mode anymore. Flashing custom Roms -and especially CM9- won't cause this.
However you WILL need an efs backup, since that part of your phone could easily get lost and is not possible/very hard to recover.
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
Hey guys,
I'd like to return to stock samsung rom, resetting the device to factory setting (keep reading).
Reason for this is
1 I'am experiencing fastidious UI lags issue.
2 I've done several "Restore factory Setting/Wipe all data" and I can see folders of applications I installed at least three roms ago (and not installed anymore). Some of them are empty, some are not.
Maybe my device is just imploding bacause of the number of apps he keeps managing.
Maybe he doesn't like me anymore,
or maybe he is dying of cancer. :crying:
Info about my device:
Kernel: Siyah 1.8.9
1st ROM: Samsung 4.1.1
2nd ROM: CM10.1, 20120117 build
Goal:
I'd like to return to Stock Kernel with the stock 4.1.2 Samsung firmware.
So, how can I REALLY reset my device, starting againg form where I indicated?
domenicop said:
Hey guys,
I'd like to return to stock samsung rom, resetting the device to factory setting (keep reading).
Reason for this is
1 I'am experiencing fastidious UI lags issue.
2 I've done several "Restore factory Setting/Wipe all data" and I can see folders of applications I installed at least three roms ago (and not installed anymore). Some of them are empty, some are not.
Maybe my device is just imploding bacause of the number of apps he keeps managing.
Maybe he doesn't like me anymore,
or maybe he is dying of cancer. :crying:
Info about my device:
Kernel: Siyah 1.8.9
1st ROM: Samsung 4.1.1
2nd ROM: CM10.1, 20120117 build
Goal:
I'd like to return to Stock Kernel with the stock 4.1.2 Samsung firmware.
So, how can I REALLY reset my device, starting againg form where I indicated?
Click to expand...
Click to collapse
Anyone help????//??
The absolute cleanest way, is to do a mega wipe. Use Titanium Backup to save all the apps you want/need (NO SYSTEM APPS). Then, Factory Reset/Wipe Data, wipe internal sd card and wipe external sd (if you have one). Backup all pictures, photos and files you want on your pc first, then wipe everything. The Megawipe script can help you with this. Follow up by downloading one of the new 4.1.2 deodexed roms (Preferably LKC or LLA). You can keep the stock kernel or choose from my main 2 - Perseus Kernel or Yank kernel
Umh.. I'm not sure I got it.
First, I should remove Siyah kernel and the second ROM right?
How can I do it?
Will the Siyah Kernel be overwritten when I'll write the Stock Samsung 4.1.2 firmware?
domenicop said:
Will the Siyah Kernel be overwritten when I'll write the Stock Samsung 4.1.2 firmware?
Click to expand...
Click to collapse
Yes.
There is a sticky .
One run Triangle Away reset rom counter to zero .
Two flash your original saved stock rom Via Odin = wipes phone .
Three factory reset .
Four boot to download mode check status original and count is 0.
Boot phone settings about phone Status device status not modified .
Finally check there are no left over root apps on the phone .
jje
Need detailed info on this, anyone willing to help?
all the details are there for you to read
Thank you, anyway I'd like to advise that flashing via Odin doesn't format anything.
Step 0 is: Do a full data wipe (if you do it after triangle remover, I think counter will be incremented to 1, not tried though... )
domenicop said:
Thank you, anyway I'd like to advise that flashing via Odin doesn't format anything.
Step 0 is: Do a full data wipe (if you do it after triangle remover, I think counter will be incremented to 1, not tried though... )
Click to expand...
Click to collapse
Yes, yes, you are right, rest of the XDA community, with special attention to author of this are wrong, otherwise you have the headache and your nanny doesn't know what to do except from calling parents.
Would someone buy this kiddo a happy meal, please?
PS. Following the XDA RULES, especially search BEFORE posting, does not hurt.
Now im ****ed up! Im stuck at boot logo (samsung) need urgent help. it all happens after installing font installer. My phone was rooted. I want a clean format and i ended at this problem.
sometime flashing rom and than flah another rom may cause lag even the rom are really smooth. Try this, it work for me. Wipe Data, Cache Partition, Clear dalvike cache, format system and format preload. As far as i know, preload where it chaching framework. Sometime when flashing and keep flashing rom that different framework, the cache still there. that may cause lag.
zebroid said:
Now im ****ed up! Im stuck at boot logo (samsung) need urgent help. it all happens after installing font installer. My phone was rooted. I want a clean format and i ended at this problem.
Click to expand...
Click to collapse
That coz u replace roboto-bold. Lol. Im using JB multipack v3. It got quite font collection there. No bootloop. And yes, JB multipack replace roboto-bolt but no bootloop
zebroid said:
Now im ****ed up! Im stuck at boot logo (samsung) need urgent help. it all happens after installing font installer. My phone was rooted. I want a clean format and i ended at this problem.
Click to expand...
Click to collapse
If you want a clean install, without lags, I'd recommend not messing about with the fonts. Try running it stock for a while and see if your lags have gone, before fiddling with it.
Sent from my GT-I9300 using Tapatalk 2
What is all the complaining about? Do all of you complaining only have 1GB of RAM? Do you have windows animations turned off which also helps?
Sent from my 32GB Verizon Galaxy S III (SCH-1535) - stock (unrooted) JellyBean ROM with 64GB Class 10 MICROSDXC - using XDA Premium
Hello!
Please excuse me and my language. I am also kind of a noob.
Is there any way to completly remove Android from smartphone?
auroranova said:
Hello!
Please excuse me and my language. I am also kind of a noob.
Is there any way to completly remove Android from smartphone?
Click to expand...
Click to collapse
I find the best way is either letting it go for a swim or run over it with a large vehicle. But seriously, what do you mean by that? It's like asking how to remove Windows from your PC. There wouldn't be anything on it to actually use the device.
Wipe partitions
I want to wipe all my partitions (including the kernel) in order to reinstall my firmware. I have rooted my phone and messed up with some kernel settings. I want to erase everything so I can start over. I may be a little stupid to ask for this but sorry. I am a noob. Is there any way?
auroranova said:
I want to wipe all my partitions (including the kernel) in order to reinstall my firmware. I have rooted my phone and messed up with some kernel settings. I want to erase everything so I can start over. I may be a little stupid to ask for this but sorry. I am a noob. Is there any way?
Click to expand...
Click to collapse
For most devices, this is not necessary - to wipe everything. Rarely would you ever need to wipe the boot partition (where the kernel is stored), as just flashing another kernel, rom, or reloading the stock firmware with the appropriate tool would take care of this. Why don't we backup a bit and start with which device do you have, what update was it on before you started, and what have you done to it (which rom, kernel, etc) as any or all of those things can affect which steps you should take to resolve your issue.
Fixed it!
Nevermind.. I fixed my issue. There was a problem with com.android.systemui. And about partition wipping.... I managed to do that with SP Flash Tool from MediaTek
Thank you for your support!
The Auto Rotation worked on Miui, and then Lineage when I flashed it. But YouTube didn't work
Then I wanted to try Pixel experience, youtube still didn't work, then auto rotate didn't work
Then I tried Havoc, my favorite UI so far; youtube finally worked, but auto rotate still didn't work, and now Fire Emblem wouldn't install via APK or show up as compatible in the play store...
I want to know if there's a fix for auto rotate or a lightweight rom that will give me rotate and spare me from app issues.
Chocolina said:
The Auto Rotation worked on Miui, and then Lineage when I flashed it. But YouTube didn't work
Then I wanted to try Pixel experience, youtube still didn't work, then auto rotate didn't work
Then I tried Havoc, my favorite UI so far; youtube finally worked, but auto rotate still didn't work, and now Fire Emblem wouldn't install via APK or show up as compatible in the play store...
I want to know if there's a fix for auto rotate or a lightweight rom that will give me rotate and spare me from app issues.
Click to expand...
Click to collapse
Probably caused rotation bug yourself, dont remember exactly now, but you wiped partition you shouldnt have wiped. Maybe vendor partition, im not 100% sure. Just flash stock rom, get everything working again, and dont wipe what you not supposed to wipe. Do it only on cache, data, system. Also, be sure to follow guides exactly when flashing stock rom, you can easily brick the device if you relock bootloader or do other mistakes.
Edit. Remembered, its persist partition. You wiped it and lost all your sensors. There is absolutely no reason to wipe it. Just do everything as suggested in tutorials and everything will work as its supposed to.
Plekst said:
Probably caused rotation bug yourself, dont remember exactly now, but you wiped partition you shouldnt have wiped. Maybe vendor partition, im not 100% sure. Just flash stock rom, get everything working again, and dont wipe what you not supposed to wipe. Do it only on cache, data, system. Also, be sure to follow guides exactly when flashing stock rom, you can easily brick the device if you relock bootloader or do other mistakes.
Edit. Remembered, its persist partition. You wiped it and lost all your sensors. There is absolutely no reason to wipe it. Just do everything as suggested in tutorials and everything will work as its supposed to.
Click to expand...
Click to collapse
Any wiping I did was Dalvik, Internal, Data, System, and Cache, and if you can even count it, SD and OTG. There were no options to wipe vendor. Maybe vendor got overwritten, but I never specifically went to an option where I could wipe or delete any partitions. Everything I do/did was is in the Wipe or Install menu, with the exception of language change.
But now everything is destroyed because the mi flash tool bricked my device. I now learned that what the tool is known for, but being my first Xiaomi devices, it's not exactly on the user manual or common knowledge that Xiaomi likes bricking devices. I only heard of it after I started having problems
I wasn't cautious about the actions I was making because never before had I owned a device I couldn't recover from, including bricks. So I figured anything I did, I could just reverse it and go to stock
Chocolina said:
Any wiping I did was Dalvik, Internal, Data, System, and Cache, and if you can even count it, SD and OTG. There were no options to wipe vendor. Maybe vendor got overwritten, but I never specifically went to an option where I could wipe or delete any partitions. Everything I do/did was is in the Wipe or Install menu, with the exception of language change.
Click to expand...
Click to collapse
Well thats how it happens. You delete persist partition and you lose sensors. And im 100% sure thats what happened to you. So doesnt matter what you think you did or didnt, fact is it happened. Flash stock rom and fix it.
Plekst said:
Well thats how it happens. You delete persist partition and you lose sensors. And im 100% sure thats what happened to you. So doesnt matter what you think you did or didnt, fact is it happened. Flash stock rom and fix it.
Click to expand...
Click to collapse
Flashing stock rom is what bricked my device
Chocolina said:
Flashing stock rom is what bricked my device
Click to expand...
Click to collapse
Again, didnt follow guide properly then. Everyday hundreds of people do these things and nothing bad happens. Probably choose bad settings in flash software, like lock bootloader again
Plekst said:
Again, didnt follow guide properly then. Everyday hundreds of people do these things and nothing bad happens. Probably choose bad settings in flash software, like lock bootloader again
Click to expand...
Click to collapse
Im not arguing my ineptitude, you're right...
But the official flashing tool shouldn't be bricking devices regardless if there is or isn't a locked bootloader option, and should probably warn the user before hand the risks.
The flashing tool is supposed to be saving people from bricks, not causing them. Until I bricked my device, I wasn't seeing the "oh man I bricked my device using this" or "don't do this you'll brick your device" comments, it wasn't until after I did, did I have to search my issue.
But I've had time to sit down and tinker, I did manage to get it up and running regardless that the bootloader was locked.
Now my biggest regret is how I had to mangle the paint job just to get the damn thing open. By far one of the most difficult covers I had to remove
Chocolina said:
Im not arguing my ineptitude, you're right...
But the official flashing tool shouldn't be bricking devices regardless if there is or isn't a locked bootloader option, and should probably warn the user before hand the risks.
The flashing tool is supposed to be saving people from bricks, not causing them. Until I bricked my device, I wasn't seeing the "oh man I bricked my device using this" or "don't do this you'll brick your device" comments, it wasn't until after I did, did I have to search my issue.
But I've had time to sit down and tinker, I did manage to get it up and running regardless that the bootloader was locked.
Now my biggest regret is how I had to mangle the paint job just to get the damn thing open. By far one of the most difficult covers I had to remove
Click to expand...
Click to collapse
It shouldnt, same as you shouldnt be flashing custom made roms by random developers. Yet we do . If you only use phone as it was supposed to be used, and flash only official firmwares you will never brick.
Plekst said:
It shouldnt, same as you shouldnt be flashing custom made roms by random developers. Yet we do . If you only use phone as it was supposed to be used, and flash only official firmwares you will never brick.
Click to expand...
Click to collapse
Can you give backup files persistant twrp ? I lost my sensors too.. flash to stockrom is so harmful ..