I've been thinking about the OV's that get bricked by way of factory reset after rooting and roming with the wrong recovery. When the phone can only be recognized in emergency mode by the PC, it's a brick. As I've been given to understand, at that point the only thing that can be done for it is to stuff some Optimus S firmware down it's gullet. What separates the firmware for the two? Is there any way to strip out the radio from the flash? (That's what nerfs it, right?) If so, I was thinking we could use a ROM meant for the S, hacked to remove whatever elements would nerf a V's radio, just to get up and running enough to push the correct recovery. If that were possible, it would save a few good phones.
So, am I just being naive? Or would this be possible?
So I guess not.
Sent from the BACKside of Tapatalk
Related
Hi guys,
I dont have my phone bricked yet even though i thought i did it wouldnt load past the DAS BAMF loading screen when i was upgrading from BAMF 2.1 MR 2 to BAMF Sense 3.0 , and i had to flash a MR1 Radio Ruu that came with my TB Root Kit. IT was the RUU that was flashed after the downgrade. I was like phew i just unbricked my phone I think... anyways i dunno if i really unbricked it or even if it was bricked in the first place.... MY question is IF you do have your TB Bricked how do you unbrick it? I know with Galaxys you just use a software called odin that pushes the whole system back on from scratch... is there an odin type of software for the TB that will unbrick our bricked phones. or are TB users for ever doomed to having to throw their bricks away if ever bricked?
over and out
the one and only BHBMASTER
Just read before flashing, don't do anything stupid, and you won't have to worry about it bricking.
I believe the term "brick" is used much too widely. A phone isn't bricked unless you cannot access the boot loader for whatever reason. By your sense of the term you would flash a different RUU in HBOOT. But just to verify, bricking your device means you have turned it into a $200 paper weight.
Someone feel free to correct me, but everything I've read tells me a "bricked" phone is one that has suffered some form of hardware failure, which results in an inability to get into hboot or CWR long enough to do anything.
Bricks have happened to stock unrooted users as well.
So no, there is no coming back yet from a true brick. Bootloops can be recovered (I know, I've had several).
Bottom line, root away, just read and follow directions.
Sent from my ADR6400L using XDA Premium App
Typically a full brick (or just brick) refers to one that can't be fixed (at least not without a JTAG device or desoldering the EEPROM/Flash/eMMC chip and using a seperate programmer). A semi-brick refers to one that you have to go into recovery to fix (i.e. flash a RUU or use a nandroid backup). Unfortunately, many people say brick when they really mean semi-brick.
nl3142 said:
Typically a full brick (or just brick) refers to one that can't be fixed (at least not without a JTAG device or desoldering the EEPROM/Flash/eMMC chip and using a seperate programmer). A semi-brick refers to one that you have to go into recovery to fix (i.e. flash a RUU or use a nandroid backup). Unfortunately, many people say brick when they really mean semi-brick.
Click to expand...
Click to collapse
This. Brick means you can't fix it, it's a paperweight. If you can Odin or flash in hboot, it's not bricked. To the OP, flashing an ruu in hboot is the equivalent of flashing through Odin.
Sent from my ThunderBolt using XDA Premium App
nl3142 said:
Typically a full brick (or just brick) refers to one that can't be fixed (at least not without a JTAG device or desoldering the EEPROM/Flash/eMMC chip and using a seperate programmer). A semi-brick refers to one that you have to go into recovery to fix (i.e. flash a RUU or use a nandroid backup). Unfortunately, many people say brick when they really mean semi-brick.
Click to expand...
Click to collapse
This "at least not without a JTAG device or desoldering the EEPROM/Flash/eMMC chip and using a seperate programmer" you speak of, sounds very interesting and fun... what is it exactly and where is the best place to learn about it... i know i could just google it but u guys on XDA are smarter then google
A bricked phone means that your phone is about as good as a brick. It can't be fixed. Period. I've never bricked a phone before. I've screwed some up royally, but was always able to fix. Rooting is not something for people who are not technically inclined, and aren't familiar with command prompts. Always do your homework. Read as much as you can before trying anything. If its too over your head, you probably shouldn't try it.
Sent from my HTC Gingerbolt with das BAMF 2.1 using Swype
So far I haven't found an exact rom/firmware to match the one on my UK Wifi Tab, the serial numbers differ slightly.
I'd like to find out if it's possible for me to make my own complete backup image, one that can be used if need be to put the Tab back to how it was out of the box. I'd do a factory reset before making the backup.
Is such a thing possible without having to root my device and without having CWM? Could it be done with ADB (not that I have a clue how to use it).
If it is possible, would someone be kind enough to tell me how it's done?
Many thanks.
UKseagull said:
So far I haven't found an exact rom/firmware to match the one on my UK Wifi Tab, the serial numbers differ slightly.
I'd like to find out if it's possible for me to make my own complete backup image, one that can be used if need be to put the Tab back to how it was out of the box. I'd do a factory reset before making the backup.
Is such a thing possible without having to root my device and without having CWM? Could it be done with ADB (not that I have a clue how to use it).
If it is possible, would someone be kind enough to tell me how it's done?
Many thanks.
Click to expand...
Click to collapse
Nope, not possible without root. With root, however, you can reset the device to factory. Is there a specific reason you don't want to root?
Thanks for the reply.
I do intend rooting the device at some point, but I've been putting it off until I can get hold off (or create) a rom that matches the one on my Tab right now. I see that samfirmware have a Euro rom, but it appears slighly different to what I have on my device.
I'm just trying to avoid the possibility of ending up with a non standard rom for my device, which might prevent me receiving future updates, or even from returning it if a warranty claim arises.
My HTC Desire is using a custom rom, but I have the security of having the original RUU that I can run to get my phone back to stock, I was hoping for something similar for the Tab.
I'm flashing to stock, what do I need to know before getting started? I am coming from an Atrix that was previously on rooted OTA updated gingerbread firmware.
Background...
I finally rooted my atrix because I really wanted the new swype beta. I got carried away freezing and uninstalling apps in titanium backup and now I'm getting a constantly recurring force close dialog that comes back up too fast to even click a button to get into the system folder and completely remove it. So basically i have to return to stock. A hard reset didn't help obviously.
I have a lot of experience flashing roms and rooting my old samsung captivate but I never messed with rooting or flashing on the atrix because of all this talk about locked bootloaders which sounded kind of scary.
Anyway, I'm following mobiletechvideo's (connexion's) video on youbtube on how to flash to stock which is titled "Motorola Atrix (How To Use RSD-Lite). Basically, I have the drivers installed, I have rds lite 5.0 installed, and I know how to get into RSD mode at boot. Is it really this simple?
Anyway, I guess what I'm asking is where are mistakes commonly made? What do I need to watch out for? Sorry for ranting, but I just want to be really cautious, I can't risk hard bricking this phone. It seems sometimes as if no matter how well prepared you are, there is a bit of info that you can miss which could really screw things up.
I am downloading the most recent firmware on this list. Is this what I need, or do I need something for the bootloaders too. I am assuming that I do not need to worry about unlocked bootloaders since I am staying on gingerbread and not upgrading, correct?
http://forum.xda-developers.com/showthread.php?t=1125944
I've managed to get a warranty replacement SGS4G from T-mobile, but I'd still like to figure out if I can recover any data and also verify exactly what I did wrong.
I found a Froyo .tar to flash via Heimdall to recover from a soft brick botched ROM/kernel upgrade. Either I selected the wrong file for the wrong thing in Heimdall or the tar was not compatible with the Vibrant but I think it messed up the bootloader.
The flash completed and then then screen would stay black no matter what I did.
No download mode regardless of buttons held, battery insert order, USB plug/unplug etc. No download mode even with USB resistor jig.
I found AdamOutler's UnbrickableMod stuff and tried the ModeDetect program which never saw the device which I guess confirms the hard-brick. So is the only option left for me to apply the Unbrickablemod (solder etc.)?
I've read people saying that it's almost impossible to brick these phones - is that true?
I assume I cannot recover any data from the internal SD card easily without unbricking.
Did I try to flash the wrong file, or would using an incompatible firmware do this? I'll try to post the exact file I used if I can find it.
[UPDATE]
I was trying to use a stock Froyo firmware from samfirmware that I found linked in a thread in the forums: I9000XXJVR_CL425308_REV03_user_low_ship
...and CFRoot kernel so I wouldn't have to root manually each time I had to reflash (CF-Root-XX_OXA_JVR-v4.1-CWM3RFS).
I thought this was compatible with the Vibrant, but are these only for the Galaxy S I9000?
HAHAHAHAHAHAHAHAHAHAHA, rotflmmfao.
I'm sorry, I needed a good laugh today
At the moment, the possibilities are too varied to narrow down. Could be the Froyo ROM you picked up was made for a different phone, or the program didn't install correctly, or the download was corrupt.
Our phones are virtually unbrickable, it's true. One of the few ways to hard brick them is to mess with the bootloader and fail.
djquick said:
HAHAHAHAHAHAHAHAHAHAHA, rotflmmfao.
I'm sorry, I needed a good laugh today
Click to expand...
Click to collapse
Riff box bro. Don't listen to DJ.
Sent directly to your brain from my cyanomodded not-so-Vibrant
Sadly, no. What you flashed was not compatible with the Vibrant. It's for the international version of the Galaxy S only, the i9000. Sounds like your phone is hard bricked thanks to the i9000 bootloader the flash must have added.
Thanks, stupid mistake on my part.
Noob question then: what must only be used for the specific phone it's made for vs. what can be used with other phones? Firmware, bootloader, kernel, modem, ROM, etc?
I got an AT&T Galaxy Mega I think its the i527, but I'm using it with MetroPCS. I wanted to flash a custom ROM but I'm totally new to this world. :silly:
Hopefully somebody could help me.
1.- What would happen if I do a factory reset? (would I be able to use it on MetroPCS)
2.- Since MetroPCS and T-Mobile are compatible could I use a ROM like this one?
And by the way, when I plug my cell phone to my laptop it starts to charge but I can't open files its like not recognizing it does anybody know whats up?
btw2: I still have the unlocking code would I be able to use it again?
AlejandroBAAO said:
I got an AT&T Galaxy Mega I think its the i527, but I'm using it with MetroPCS. I wanted to flash a custom ROM but I'm totally new to this world. :silly:
Hopefully somebody could help me.
1.- What would happen if I do a factory reset? (would I be able to use it on MetroPCS)
2.- Since MetroPCS and T-Mobile are compatible could I use a ROM like this one?
And by the way, when I plug my cell phone to my laptop it starts to charge but I can't open files its like not recognizing it does anybody know whats up?
btw2: I still have the unlocking code would I be able to use it again?
Click to expand...
Click to collapse
You may need to install drivers for computer to recognize, but mine does that automatically. If rooted, you may need to re-install.
Factory reset is just going to erase everything.
If it is an ATT model i527, there is no recovery for it yet and I beleive that transends all unlocking.
Do the smart thing for a noobie. Dont flash a darn thing until you educate yourself. Read read read. Google your questions. Put yourself in a situation where you understand what your doing. Dont guess or follow someone else unless you are confident in there level of expertise. Nobody will replace your phone here.
Post all information.
Example......you did not say whether your phone is upgraded to 4.4 or still running 4.2 ?????
1 little detail can mean the biggest difference.
Good luck
As always, I will check back, because I am still learning too.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app