Just in case you brick your phone... Use this method. - EVO 4G General

When you copy your ROM to your SD card, be sure to leave it on there after you flash. If you somehow manage to brick your phone, go into recovery, wipe data, wipe cache, and wipe dalvik cache. Flash the saved ROM that was on your SD card. Boom. Simple.
I had a personal experience that made me post this. Though It's obvious to most, it probably isn't to noobs.
Sure saved me a trip to the Sprint store
Sorry if this was already posted before by somebody else.
Sent from my PC36100 using XDA Premium App

Actually, I think if you brick your phone there isn't much of anything you can do. When the phone is bricked it will not power up, into recovery charge anything. Now, bootloops on the other hand this works for.

Isn't boot loop soft bricking? If so, that's what I meant.
Sent from my PC36100 using XDA Premium App

Jardicel said:
Isn't boot loop soft bricking? If so, that's what I meant.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
No it is not, you can get a loop just by placing a mismatch file on your phone. I get bootloops if my phone dont like framework apk's I change. I think you should remove the work "brick" from the heading. Alot of people get confused about bricking. Now in all honesty if you brick your phone you are generally S.O.L....
Also the ability alone to go into recovery means its not bricked...

From what I've learned on different threads, there are three types of bricking. Including soft brick, where you cannot load the system UI and are stuck somewhere before. You could access recovery.
Sent from my PC36100 using XDA Premium App

This is very basic stuff.. I wouldn't consider boot loop to be soft brick.
Deck's + SZ + SuperCharger script + ViperMod script.

Jardicel said:
From what I've learned on different threads, there are three types of bricking. Including soft brick, where you cannot load the system UI and are stuck somewhere before. You could access recovery.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
ok but really bricking is not good and a boot loop is not a big deal my friend.. Just saying don't throw that word around in my opinion unless its really over for you... like not booting up at all
Edit; why not change titile Just in case you Bootloop your phone... Use this method

I agree that people use the term brick a bit too often. A brick is nothing less than a paper weight of a phone. No booting, no recovery, and won't charge.
Sent from my PC36100 using XDA App

Bricked is a state, like being dead, there are no shades of grey it is a binary, it is either bricked or it isn't. It is bricked because you can't bring it back to life.

Mine is so dead the Jig doesn't even phase it. It is graveyard, doornail dead. Dead as dead gets.

Jardicel said:
When you copy your ROM to your SD card, be sure to leave it on there after you flash. If you somehow manage to brick your phone, go into recovery, wipe data, wipe cache, and wipe dalvik cache. Flash the saved ROM that was on your SD card. Boom. Simple.
I had a personal experience that made me post this. Though It's obvious to most, it probably isn't to noobs.
Sure saved me a trip to the Sprint store
Sorry if this was already posted before by somebody else.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
my phone very well

Related

Formatting partitions

I'm not interested in a2sd if that's what your thinking. I had a Rom install go wrong and now I've lost root but can still boot into clockwork recovery. I'm really annoyed by the fact I can boot to recovery for no reason, also I tried to install the. 6 software update and the installation fails then leaves me in recovery mode. I just want to know what would happen were I to format any of the partitions, boot and system come to mind. Please be very specific as I think this may be one way to brick the phone.
Sent from my HERO200 using Tapatalk
It's nearly impossible to brick your phone. I'm still very new to this whole world and the wealth of info out there, but have found if all else fails run the ruu and start all over again from scratch and back up your work frequently. The greatest ways to learn are by messing up and having to start over or figure out what YOU messed up or where YOU went wrong. That and read, read and read some more.... oh and did I mention READ?!
Sent from my HERO200 using XDA App
Lol yeah, I went up to a Sprint store today hoping to get them to redo the 2.1 Ruu and was told that it cannot be done. Based on this, I have no idea how to get back to stock without re-rooting I guess.
Sent from my HERO200 using Tapatalk

[Q] How to Completely Erase Everything?

I want to do this as more of a starting new kind of thing. I know you can clear the sd cards and factory reset, but does that truly erase everything? And i understand theres also some options to clear delvik cache and others in CWM. Are these caches erased w/ factory reset? thx brah
Odin maybe?
Sent from my SGH-T959 using XDA App
yeah ive used odin a bunch to flash eugenes roms and stock rom if i get a soft brick. But weird thing is it doesnt wipe my internal sd. BTW this ISNT like a serious issue and i NEED to erase everything...but ive flashed so many roms over each other i thought it would be good to give my phone a breath of fresh air. haha
okay so just about an hour ago i was trying to install the 2825 radio. i flashed it onto the phone in recovery mode and now my phone wont go past the boot screen. (tmobile g1) i can still get to recovery and fastboot and all of that but even when i tried to restore it, it still wont go past the boot screen!!!!! what did i do wrong, and is there any hope for me?? please help!
roguly said:
I want to do this as more of a starting new kind of thing. I know you can clear the sd cards and factory reset, but does that truly erase everything? And i understand theres also some options to clear delvik cache and others in CWM. Are these caches erased w/ factory reset? thx brah
Click to expand...
Click to collapse
Hopefully you will not accomplish your objective. "Everything" includes the Primary Boot Loader, in which case your phone will be permanently bricked, for all intents and purposes.
You will not be able to access the phone by any means other than an expensive tester after you delete USB drivers from the phone.
To erase everything...you need to go settings.phone & sdcard.umount...under phone storage.format....it will mount back on its own
Sent from my SGH-T959 using XDA App
jmcghee1973 said:
To erase everything...you need to go settings.phone & sdcard.umount...under phone storage.format....it will mount back on its own
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Will this hurt anything if I do this while running a custom rom? Just wondering.
Sent from my SGH-T959 using XDA App
ZachLL88 said:
Will this hurt anything if I do this while running a custom rom? Just wondering.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
you'll lose everything on the rom including apps that the dev added. only thing you wont lose is stock apps, but no it shouldnt matter what rom your running.
jmcghee1973 said:
you'll lose everything on the rom including apps that the dev added. only thing you wont lose is stock apps, but no it shouldnt matter what rom your running.
Click to expand...
Click to collapse
Great! Thanks for the info!
Appreciate the fast response.

Correct me if I am wrong.......

Had my X for a week now. It is rooted and running DarkSlideBlur 4.2, I have several other ROM's I am wanting to try out......
If I understand what I have been reading right, I can use Nandroid Backups to return to ROM's I like, or is it better to reflash them?
Trying to avoid the whole setup process....
Thanks in advance
Mace
A nandroid would be the route to go. It restores your phone to the exact state it was when you backed it up. Every call text message everything will be as it was.
Nandroid all the way. Works every time
Sent from my HTC Glacier using XDA App
MaceBewley said:
Had my X for a week now. It is rooted and running DarkSlideBlur 4.2, I have several other ROM's I am wanting to try out......
If I understand what I have been reading right, I can use Nandroid Backups to return to ROM's I like, or is it better to reflash them?
Trying to avoid the whole setup process....
Thanks in advance
Mace
Click to expand...
Click to collapse
As already stated, a nandroid is a best bet. Just keep in mind if you do any updates (OTA) and the radio gets updated (i.e. 2.3.15 to 2.3.340) an old nandroid will brick your phone due to an older bootloader
Sent from my DROIDX using XDA App
Thanks guys! I thought that was the case, as I have been all over these forums "researching" for a couple months before I got the X!
Now off to research "Radio"?? (thats a new one to me)
But what if you mount your system and get stuck in the bootup. i cant even get to the recovery. i dont know what to do.
Nandroid always has your back. Something gets screwed and you are stuck in a boot loop, plug in the usb or charger, pull the battery, put it in and boot up. That will hijack back into Clockwork.
Always Wipe Data/Factory Reset, Wipe Cache/Advanced/Wipe Dalvik before you flash a new ROM and you "almost" always avoid a boot loop.
Sent from my DROIDX using XDA App
that is clockwork recovery, the stock recovery is accessed with a combination of hard keys which i am not sure which they are off the top of my head. in that you can wipe, but unfortunately no nandroid restore.
I tried every rom out there. The fastest most stable best battery life is stock. Deodexed stock. You can theme and font.
Sent from my DROIDX using XDA Premium App
mattmartin77 said:
that is clockwork recovery, the stock recovery is accessed with a combination of hard keys which i am not sure which they are off the top of my head. in that you can wipe, but unfortunately no nandroid restore.
Click to expand...
Click to collapse
The hard keys are volume down and camera button if you wanted to know
Thats to get to the bootloader. Recovery is home and power and hold on until it comes up. To get into safe mode you hold power and the menu button
Sent from my DROIDX using XDA Premium App

Can't mount internal or external storage

0.00 internal storage and the external reads 0. I have flashed every Odin file I could find, tried the heimdall one click. Nothing is working. Any ideas? I promised the phone to my father in law and he is in town for the weekend.
Sent from my Triumph using xda premium
Wow have you tried Eugene Froyo umm no brick rom? Also have you tried to partition the phone?
Sent from my GT-I9000 using Tapatalk
iwillkillyou said:
Wow have you tried Eugene Froyo umm no brick rom? Also have you tried to partition the phone?
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Sure did. About 59 times already lol. Repartition has no effect.
Sent from my Triumph using xda premium
Hmm how about making your phone soft brick, then use odin.
Sent from my GT-I9000 using Tapatalk
I don't really know, but here are some ideas.
Did you disable voodoo lagfix?
Try "eugenes froyo that doesn't brick" for the 60th time.
On ODIN put a check mark next to Re-Partition, but you said that had no effect.
Hmmmmmm, I bet eugene knows the answer. I feel like there is a thread somewhere that discusses this issue.
If you figure it out, let us know!
SamsungVibrant said:
I don't really know, but here are some ideas.
Did you disable voodoo lagfix?
Try "eugenes froyo that doesn't brick" for the 60th time.
On ODIN put a check mark next to Re-Partition, but you said that had no effect.
Hmmmmmm, I bet eugene knows the answer. I feel like there is a thread somewhere that discusses this issue.
If you figure it out, let us know!
Click to expand...
Click to collapse
I was on cm7. No voodoo. I didn't have a SD in the phone and plugged it in for mass storage. Upon realizing that, I popped one in with the phone still connected. That's when I noticed the problem. I haven't been using my phone. I Odin'd from cm7 weeks ago and didn't touch the phone until I plugged it in for mass storage.
Sent from my Triumph using xda premium
Bump it up. Still stuck.
Sent from my MOTWX435KT using xda premium
maybe the information in this post will help?
http://forum.cyanogenmod.com/topic/...ternal-storage/page__view__findpost__p__67870
Take a look at this, not sure if it's the same thing as that on cyanogenmod link above:
http://forum.xda-developers.com/showthread.php?t=1230059
I hope this will help
I had the same issue when I was coming back to a froyo rom from CM 7.1, I did everything you did flashed froyo that didn't brick and nothing so this is what I did I used Odin JI6 file from this thread ODIN JI6 and the zip comes with ODIN 1.3, 512 PIT,T959UVJI6.TAR. I used that version of odin 1.3 to flash JI6 tar and pit files and checked re partition, when it rebooted it was stuck at the factory recovery so I pulled the battery, held vol up vol down and plugged in the usb cord to get back into download mode. Now I opened ODIN 1.7(DL LINK) and flashed froyo that doesn't brick also check re partition when it re boots it will go into a boot loop you know this, so THEN yes one more odin I kept the same version of odin open 1.7 and I flashed Eugene_2E_JK2_Froyo.zip also with re partition checked. After all this I was still having issues with market then I cleared market catch installed trigger rom and now I can install apps again I would like to tell you the three odins was unnecessary but it wasn't until odin with JI6 that now my phone work right as for CM roms I never have one issue flashing then but if I want to revert back to a 2.2 rom it's a all day event hope this helps
EDIT LOL try the two peoples above me^^^ method first they seem to be on the right track ^^^
Also noticed that when I flash JFD, I get no errors(datadata, sd card, mmcblk0) in recovery after it boots from odin. The catch is, it goes black after the boot animation. Only the soft keys will light up. Really super stumped. Adb wont see my phone, so its making it really hard to manually repartition the internal storage. I have never been a adb wiz.
I thought you got this fixed?
Br1cK'd said:
I thought you got this fixed?
Click to expand...
Click to collapse
Negative Ghostrider I thought I did. But no dice.
Well damn. Have you tried different versions of Odin? What about a Voodoo kernel and conversion, any difference? There is something I remember reading a while back about an issue like this, I don't remember exactly what it said, but I'll try to find it for you.
Sent from my ZenDroid, meditating on the XDA App
I can't find the thread I was thinking of, sorry. I was thinking that your issue here sounds very similar to when people had done the partitioning via rom manager/cwm. Perhaps fixes for that will lead you in the right direction.
Sent from my ZenDroid, meditating on the XDA App
Update:
Still no luck. But after screwing with it, it now says I have a damaged internal SD, doest say blank internal SD anymore. I think that the phone is all done : (
Sent from my MOTWX435KT using xda premium
Dan_Brutal said:
Update:
Still no luck. But after screwing with it, it now says I have a damaged internal SD, doest say blank internal SD anymore. I think that the phone is all done : (
Sent from my MOTWX435KT using xda premium
Click to expand...
Click to collapse
format the sd card
laylovj said:
format the sd card
Click to expand...
Click to collapse
Doesn't work. If there was a actual/physical button for it, I would have worn it out already haha.
Sent from my MOTWX435KT using xda premium
Dan, sounds like it's time for a new Galaxy S2!
Vibrantnew-b said:
Dan, sounds like it's time for a new Galaxy S2!
Click to expand...
Click to collapse
Sure does. Im going to jump on the new T-Mobile pre-paid plan. $70 a month for unlimited everything with 5gb of 4g speed before they throttle you. Use my old ass G1 until I either get a sgs2 or a prime.
I was reading a thread about the storage issue(http://forum.xda-developers.com/showthread.php?t=957615), and Im 300% sure that the phone is ****ed. I think I roasted the internal storage completely. A true brick. Do I get a cookie for bricking the un-brickable?

Brick while on safe kernel

Guys I still don't believe it but I did very well this evening I just managed to brick my device by copying some avi and wmv files from the external SD-Card to my internal storage. How did I do that? I have no f...... clue. The phone froze, I waited almost half an hour but nothing happened. So I finally decided to pull the battery and restart the phone. And what did I get? I phone nicely stuck at the boot logo. Ok I thought, no biggie. Let's try to clean cache and dalvik cache, this action had helped in the past when the phone had been stuck at the boot logo. But no, it did not help at all. Then I thought ok, before I restore my nand backup I can still try to reflash the kernel. And I think that killed my phone. After the kernel had successfully been flashed (according to the log in CWM) I tried to reboot but nothing worked anymore. I could not even boot into CWM recovery. Hm, that's not good but now I could still try reflashing the rom using pc odin because the download mode still worked (in fact it still works). But it does absolutely nothing. It does not even start to flash. So bang, there it is, my own full brick. Huray. Off to the service center I go. At least I always paid attention not to increase the flash counter/ trigger the red triangle. So since the phone is completely dead I am optimistic that they should not be able to proof that my phone was rooted (fingers crossed).
In case you are interested, my rom was LRQ, my kernel was the latest version of the PhilZ kerne with it's touch recovery.
did you check to see if the drivers on the computer are properly installed? I'm tinking it might be a case of pc not finding the phone.
or maybe you had some bad blocks since the days of unsafe kernels
altae said:
Guys I still don't believe it but I did very well this evening I just managed to brick my device by copying some avi and wmv files from the external SD-Card to my internal storage. How did I do that? I have no f...... clue. The phone froze, I waited almost half an hour but nothing happened. So I finally decided to pull the battery and restart the phone. And what did I get? I phone nicely stuck at the boot logo. Ok I thought, no biggie. Let's try to clean cache and dalvik cache, this action had helped in the past when the phone had been stuck at the boot logo. But no, it did not help at all. Then I thought ok, before I restore my nand backup I can still try to reflash the kernel. And I think that killed my phone. After the kernel had successfully been flashed (according to the log in CWM) I tried to reboot but nothing worked anymore. I could not even boot into CWM recovery. Hm, that's not good but now I could still try reflashing the rom using pc odin because the download mode still worked (in fact it still works). But it does absolutely nothing. It does not even start to flash. So bang, there it is, my own full brick. Huray. Off to the service center I go. At least I always paid attention not to increase the flash counter/ trigger the red triangle. So since the phone is completely dead I am optimistic that they should not able to proof that my phone was rooted (fingers crossed).
In case you are interested, my rom was LRQ, my kernel was the latest version of the PhilZ kerne with it's touch recovery.
Click to expand...
Click to collapse
I have never considered the "hex-patched" kernels to be safe...
jeriz said:
did you check to see if the drivers on the computer are properly installed? I'm tinking it might be a case of pc not finding the phone.
or maybe you had some bad blocks since the days of unsafe kernels
Click to expand...
Click to collapse
Yep. I don't think the drivers are the problem since the phone is recognized. But it does not start to flash. It simply does nothing and the phone stays in download mode forever.
Entropy512 said:
I have never considered the "hex-patched" kernels to be safe...
Click to expand...
Click to collapse
this in itself is a huge statement
altae said:
I could still try reflashing the rom using pc odin because the download mode still worked (in fact it still works). But it does absolutely nothing. It does not even start to flash.
Click to expand...
Click to collapse
This is diferent... not even start to flash...
Sent from my GT-P3110 using Tapatalk 2
Entropy512 said:
I have never considered the "hex-patched" kernels to be safe...
Click to expand...
Click to collapse
It seems that remaining on Gingerbread (until official JB) for the moment is the best thing for people who do not have a warranty for their Note.
Many people confuse superbrick (phone dead right away, no life even if you plug a charger) and other bricks. This is just an unfortunate other brick not related in any way to emmc described one. Good luck at RMA
Also, copying big video to your sdcard is a good way to kill it. Old i9000 thread was popular with that
Sent from my GT-I9100 using Tapatalk 2
Was running Paranoid Android
Tried to restore the Note back to the latest UK stock ICS ROM via ODIN
Forgot to wipe/davlik before hand
then got stuck in boot loop
more boot loops
Then tried flashing a rooted GB rom in ODIN
stuck now on the Samsung Note boot screen occasionally looping.
Then tried flashing an original non-rooted GB rom in Odin
got stuck on Data.img
Then tried again and it stuck on FACTORYFS wont even get passed this.
Took battery out, then back in...
Now the screen shows three images and the message
firmware upgrade encountered an issue
Now with the Samsung Repair centre in Eastbourne and they are failing to be able to do anything...they still have my NOTE:crying:
Entropy512 said:
I have never considered the "hex-patched" kernels to be safe...
Click to expand...
Click to collapse
Sure, you can theorically miss the binary check in rare circumstances. But this is just "an other brick" without any common relation typical to described emmc brick: no wipe, no flash, and mainly no right away (or even) complete dead phone
Sent from my GT-I9100 using Tapatalk 2
@ Entropy. Even guy above Phil3759 his bricked his note starting from PA which has a "safe" kernel, and eventually superbricking just useing PC Odin (long time considered safe). No wipes involved. Anyway, is Tungstwenty's detection method flawed for stock ICS kernels? Or is there are problem changing the offending byte from a 1 to a zero
Sent from my GT-N7000 using xda app-developers app
At least this brick has made me decide to leave my note well alone, after flashing roms practically daily for the last month or so, I have become insanely addicted to changing roms...once i get the Note back from the Sammy Service place, I am sticking with stock and wait till the official JB update arrives, which looks fantastic.
As it states on all these roms flashing custom roms at your own risk, thus its my own fault, finger crossed it can be sorted.
You can brick any phone, it happens, yes. Superbrick related to emmc bug occurs under special circumstances with typical symptoms.
Binary patching kernels, in theory, if you happen to have duplicate binary code or different, you could miss it. But, as far as i know, and for all manual checks i did, it never happened...
Sent from my GT-I9100 using Tapatalk 2
Since this is not the usual EMMC brick, what is the diagnosis? Just so it can be prevented/avoided in the future
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
Markuzy said:
Since this is not the usual EMMC brick, what is the diagnosis? Just so it can be prevented/avoided in the future
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
I have no clue. And since the phone is now completely dead (even download mode does not work anymore) it's kind of hard to examine it. So I would say we will never now what exactly bricked my phone.
As i said, it is really non recommended to use your internal sdcard for regular heavy write operations like videos. It will be corrupted at a certain point. On the i9000 this used to be a way for some to get warranty. Phone stuck often after a continuous write/wipe overnight
But this is not the superbrick. And one day, all your phones will brick. That's flash storage
Sent from my GT-I9100 using Tapatalk 2
altae said:
I have no clue. And since the phone is now completely dead (even download mode does not work anymore) it's kind of hard to examine it. So I would say we will never now what exactly bricked my phone.
Click to expand...
Click to collapse
I have read about this before. First can't flash with PC Odin. Then recovery mode goes, then download mode and finally dead phone. Friggin' Samsung
Sent from my GT-N7000 using xda app-developers app
shoey63 said:
I have read about this before. First can't flash with PC Odin. Then recovery mode goes, then download mode and finally dead phone. Friggin' Samsung
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
If you read across HTC and other forums, you'll see so much bricks and unhappy people. Why blame Samsung, there will be always faulty devices and unhappy unfortunate people
Sent from my GT-I9100 using Tapatalk 2
Yeah, you're right. Even PC Nand causes grief. Just hoped a Company on the cutting edge of technology like Samsung would have been able to resolve such problems.
Sent from my GT-N7000 using xda app-developers app
I would better trust seagate or corsair to push it further. Samsung HDD always failed on me. Ditched them long ago
Sent from my GT-I9100 using Tapatalk 2
---------- Post added at 11:40 AM ---------- Previous post was at 11:35 AM ----------
By the way, for people that want to know more about binary patching kernels, read here, it is worth it
http://forum.xda-developers.com/showthread.php?p=29609295
Sent from my GT-I9100 using Tapatalk 2

Categories

Resources