I've gotten the yellow exclamation mark countless times (over 20) and it's always been fixed with a simple flash back to any firmware.
Is it impossible to completely brick the X10?
It's not like I'm trying to brick my phone, I just noticed that every time I "brick" my phone it's fixed by flashing with any firmware.
The reason I ask is because when I tryd to flash my old phone and it went wrong there was nothing I could do to fix it, which led me to buying the X10.
Seems you've answered your own question...
Actually, I'm not sure if it is a question...
I didn't answer my own question. It's possible that I've never actually technically "bricked" my phone, which is why I was asking...
I once really bricked my X10. But that was because of some hardware fault (I read something about nand fault somwhere) I flashed it for the root process got the yellow triangle and exclamation mark. Reflashed it with stock rom, everything fine. Tried again to flsh if for root, somewhere during the flashing process suddenly some write errors appeared. Well after turning on I got the triangle again, tried reflashing about 100 times, but nothing ... I tried to flash it to stack rom with seus and again write errors ... well I sent it back to SE and got a new device.
So it was a brick, but most likely not because of some software but bacuase of a harwae fault.
The bootloader isn't hacked yet so I'm assuming its harder to just brick something if you wipe the firmware only.
You can only really brick it if you mess with the boot loader (or damage the hardware..).. because the bootloader brings up all the essential services before it loads the OS.. then if you knacker your OS you can simply reflash it..
Once the bootloader has been cracked (assuming that it will be at some point!), then you can bet we'll start seeing a lot more bricked x10's appearing..
Related
After thousands words, hundreds attempts I'm giving up and bringing up this discussion on this forum..I really hope your experience and deep knowledge of subject finally will help me..I live overseas and use to order HTC HD2 T-mobile for my friends and some times just for sale..It was my 7-th T-mobile HTC HD2 when I got problem with flashing custom ROM...I installed HSPL 2.08 and started to flash my usual custom ROM via USB for T-mobile 1024,I took out sim card and memory stick before flashing..When I finished I did a soft reset and got frozen STICK TOGETHER screen...Phone just stuck...Forgot to say that before flashing I format device with Task 29..So I format it again and flash one more time,process itself was successful , but again I got STICK TOGETHER and that's it...I decided to flash another radio, CORRECT one (50) special fot T-mobile 1024, after several updates error phone just died..I got a brick, I couldn't even go to bootloader mode..I reanimate device with JTAG, and tried almost all official ROMs, I flashed them via usb, using memory card..Sometimes during flashing it stopes and I have to reboot, sometimes i got a sign on screen that update is completed, but when I turn device on nothing happened..I tried MTTY method, didn't help...I don't really know what to do now..May be I missed something important but as I said I'm not a noob already, and have red tonnes of information regarding flashing ROMS... Any ideas would be highly appreciated, i still hope that is just software problem not hardware, otherwise I can just throw it away...thanks for reading this story
cementer said:
After thousands words, hundreds attempts I'm giving up and bringing up this discussion on this forum..I really hope your experience and deep knowledge of subject finally will help me..I live overseas and use to order HTC HD2 T-mobile for my friends and some times just for sale..It was my 7-th T-mobile HTC HD2 when I got problem with flashing custom ROM...I installed HSPL 2.08 and started to flash my usual custom ROM via USB for T-mobile 1024,I took out sim card and memory stick before flashing..When I finished I did a soft reset and got frozen STICK TOGETHER screen...Phone just stuck...Forgot to say that before flashing I format device with Task 29..So I format it again and flash one more time,process itself was successful , but again I got STICK TOGETHER and that's it...I decided to flash another radio, CORRECT one (50) special fot T-mobile 1024, after several updates error phone just died..I got a brick, I couldn't even go to bootloader mode..I reanimate device with JTAG, and tried almost all official ROMs, I flashed them via usb, using memory card..Sometimes during flashing it stopes and I have to reboot, sometimes i got a sign on screen that update is completed, but when I turn device on nothing happened..I tried MTTY method, didn't help...I don't really know what to do now..May be I missed something important but as I said I'm not a noob already, and have red tonnes of information regarding flashing ROMS... Any ideas would be highly appreciated, i still hope that is just software problem not hardware, otherwise I can just throw it away...thanks for reading this story
Click to expand...
Click to collapse
sorry for "stupid" answer,but...have you flash radio FIRST and rom than??I know,you're not a noob,but sometimes things more 'simple and obvious **** you
I had similar issues, it turned out to be a haware problem. HTC replaced the main board in the phone.
sorry to hear that
Just a 杯具
Yeah, you either need a new motherboard or use JTAG to reflash the bootloader..
Read here
geppo1975 said:
sorry for "stupid" answer,but...have you flash radio FIRST and rom than??I know,you're not a noob,but sometimes things more 'simple and obvious **** you
Click to expand...
Click to collapse
I flash ROM first and after i got problems with booting tried to resolve with flashing radio...anyway I guess it is hardware problems...It's vibrating time to time i go to boot loader mode,however it is ok when I reinstall HSPL, I still can see WE hacked it ...tofay I flashed an Ebergy ROM and it said that update was successful, but again when I turn device on I stuck on STICK TOGETHER ..Damn it,I'll try to flash radio, because I haven't had a success with it..By the way what abo0ut goldcard method, I don't really know what is it and how it can help..thanks
So i have tried Jit enabler v2 and bricked my SE
it freezes at Sony Ericsson logo,
what i can do is boot via xrecovery and since there i dont know how to remove Jit enabler,
Any advice?
Depending on what version of firmware you have, you need to download : http://forum.xda-developers.com/showthread.php?t=902974
and install as update.zip "*10* 2.0.A.0.*** Disable JIT.zip". That should help. If not, clear dalvik cache and reboot.
thanks, but how to put it to SD card because since its bircked i cant properly connect the phone so PC would read its SD card?
newestuser said:
thanks, but how to put it to SD card because since its bircked i cant properly connect the phone so PC would read its SD card?
Click to expand...
Click to collapse
I suppose that You don't have any card reader :/
I don't really remember if ADB works in xRecovery mode, but You can try, to unpack the "disable jit" package, and push manually files to "/system/bin", and "system/lib". The build.prop should not be a problem tho. You can do that with http://forum.xda-developers.com/showthread.php?t=868423 but, as I said, I'm not sure about working ADB in xRecovery. I figure You don't have enough time to push files on "Sony Ericsson" logo, cuz it reboots ;/
Just try.
thanks for helping out!
unfortunetly i have a reader, and only remembered after i did via xrecovery full reset (wipe data). BUT it still didnt booted, froze uppon sony ericsson logo, so im now moving files you gave a link and praying xrecovery still works
You moved to fast with wipe
I don't really know what to say to You right now.
but seems there is xrecovery backup, so in case...i think maybe i can reinstall via update service, than restore backup i made before wiping data out and installing jit disabler. Well thats by my logic should work. But im not really expierienced with phones and dont have x10 for a long time...
Unfortunately that I think is the last thing it's left to do. Just repair the phone via SEUS. I don't want to be a ****, but it's a bitter lesson for You, that if You have xRecovery, and ADB enabled theres always a way to get passed "Sony Ericsson logo reboot". Wipe was just to fast thinking. Hope You don't get in a trouble like that ever.
Yea, i tried too long time ago JiT v2 and i also bricked my phone, i also installed by accident wrong firmware ver JiT v1 and ended up, again, with a brick.
I that case, only solution to it is to Reflash whole firmware again. Trust me, i tried all possible solutions and it didnt worked. Luckily i had my contacts backed up on my g account.
I also learned my lesion hard way, and, this is 100% true.. "If you have xRec be sure to always have a backup."
P.S. Dont worry, mini/pro dont die that easily.. Its just get hardly wounded, it will always recover, but sometimes with memory loss (since u didnt had a backup)
When i first time bricked my phone it was a day old, i freaked out, but manage to get a grip and searched forum a bit. Since i like experimenting with my software i manager to brick my phone 10+ times per day..
And.. guess what phone im using now? x10 mini
Well, yea often flashes are not a big problem, but i don't wish that to anybody, cuz as you said, and all know it's a pain in the ass to get back settings, and all the data.
"Bricking" is defiantly to strong word. Boot loops, or hanging on SE logo is far from bricking, we always have a chance to "repair" our devices by ourself, so no problem here. The real problem can be in the future, when boot loader get fully cracked, and for example we interrupt his flashing process - situation well known for other android phones users. Phone gets bricked, and theres **** we can do about it, cuz recovery is obviously not working.
I did learned something else back then (5 years ago) when flashing my phone with with a desktop PC and suddenly power failure.. bricked my phone which not even got any bootloader to start with. Since that moment I always use my laptop to flash my phone as it has battery to continue the flashing process in case power failure happen again.
farsight73 said:
Since that moment I always use my laptop to flash my phone as it has battery to continue the flashing process in case power failure happen again.
Click to expand...
Click to collapse
Amen to that.
Hi *.
My I9100 [soft]bricked. Today neerajganga was trying to help me with it [thanks!], but we ended up where we started.
In last month I had few /data corruptions - phone freezed and cleared everything after reboot [I'm guessing fsck failed to recover], I though it was WIUI/MIUI rom instability.
Last week phone freezed but after rebooting it was stuck on siyah kernel logo. Also couldn't get into recovery mode - stuck on samsung logo with yellow triangle. I found that thread, downloaded ICS rom, flashed everything. System booted. So I've flashed siyah kernel again and restored rom from CWM backup.
Two days ago phone freezed again [damn!]. But this time, even though Odin showed no errors while flashing, it still had siyah kernel and freezed on it's logo.
Today we spent with neerajganga over an hour trying to flash ICS rom, bootloader, modem, pit, etc. Later we tried GB versions. Nothing changed, still Odin "thinks" flashing went ok [progress bar on phone moves nicely] but after restart phone has yellow exclamation and freezes on siyah logo. Looks like phone cheats Odin about writing kernel/rom, while ignoring all data.
I'll try USB JIG as soon as I'll get my hands on it, but according to neerajganga it probably won't work because I have new ICS bootloader.
I'm guessing faulty nand memory is causing those problems. Phone is still on warranty, but I can't return it until I get back to stock kernel/rom. They would probably reject it and cancel my warranty. Or maybe I can somehow "nicely" brick phone into state where nothing can be seen...
Any ideas? I really need that phone to work [24/7 access to business e-mail :/]
NAND is stuffed. Some JTAG repairers can repair these now (like these guys, for example). Or repair by Samsung/authorised repairer & hope they either don't care or can't tell it's been messed with (otherwise you'll end up paying to have it fixed).
You've exhausted all possible fixes anyone here can off. 'Or maybe I can somehow "nicely" brick phone into state where nothing can be seen...' Accordingly, I've asked mods to close this thread. What you've asked there is straightup fraud.
"I really need that phone to work [24/7 access to business e-mail :/] " If I really needed a phone to work 24/7 for business, I would not be flashing non-stock firmware which is experimental in nature in the first place
Tried to install the rom XXLQ5, this is the last leak
And how's that supposed to help exactly ?
Thread closed
There isn't anything left to try here, and encouraging fraud isnot something we allow here on XDA.
I've got a very definite hard brick situation going on. A few weeks ago I was using my phone, browsing Tapatalk and downloading something with the Dropbox app, and the phone went completely unresponsive (screen on but frozen, no response to any touches), came back after a few seconds, then froze completely. I powered off and tried to reboot, it hung on the boot animation. Not a bootloop, just hanging there. I powered off again and booted into CWM and tried to restore from my backup. It threw a couple errors which unfortunately I don't remember much about, and honestly, I can't remember now if they came up before or after I started the restore. It started restoring, but got hung up restoring system. After waiting what seemed like forever but was probably more like 10 minutes I very hesitantly powered off and went back into recovery, this time attempting to reflash the rom I was using. More or less the same thing, it started but just hung up during the install. I powered off again, intending to put my phone into download mode and try to flash something via Odin, but the poor guy had had enough and wouldn't even power back on. I left it charging overnight, but it never came back on and I've since bought a new phone. However, if it seems to anyone that it would be worthwhile to try a jig or jtag service, I wouldn't mind keeping this phone as a spare. Truth is, I actually miss it.
I was running WanamLite 12.5, which is XWLPX, 4.0.4, with SpeedMod K3-32. I had tried out a couple of what were then pretty much new JB leaks just before the bricking, I know I tried out Omega and Disaster, but I only kept them on for a few hours each time. All of the kernels I've used since 4.0.4 have been considered "safe".
Anyway, again, based on what I've described does anyone think there's a chance of unbricking my phone without replacing the motherboard?
shockwaverider said:
I've got a very definite hard brick situation going on....
Anyway, again, based on what I've described does anyone think there's a chance of unbricking my phone without replacing the motherboard?
Click to expand...
Click to collapse
Firstly, there is no such thing as a "hard brick" for same reason there is no such thing as a "soft brick". There is just "bricked" and no in between, your device is either bricked or it isnt.
What n00bs call "soft bricked" is just when they cant figure out how to get system to boot. Your device is bricked when it wont power on or if it powers on you cant use download/recovery to flash working rom/kernel.
In your case it sounds like you have had a hardware failure and thus will need to get the part fixed/replaced or maybe whole board. To answer your question though, yes you should first try a USB jig to see if you can get device to wake up in download mode and then try again to flash kernel ready for restoring backup or flashing new rom. If this fails then you will need to get it fixed.
TheATHEiST said:
Firstly, there is no such thing as a "hard brick" for same reason there is no such thing as a "soft brick". There is just "bricked" and no in between, your device is either bricked or it isnt.
What n00bs call "soft bricked" is just when they cant figure out how to get system to boot. Your device is bricked when it wont power on or if it powers on you cant use download/recovery to flash working rom/kernel.
In your case it sounds like you have had a hardware failure and thus will need to get the part fixed/replaced or maybe whole board. To answer your question though, yes you should first try a USB jig to see if you can get device to wake up in download mode and then try again to flash kernel ready for restoring backup or flashing new rom. If this fails then you will need to get it fixed.
Click to expand...
Click to collapse
yada yada yada I've heard some developers use "unbrick". Go tell 'em there's no such a thing.
And stop worrying about semantics.
Thanks for the replies. I understand that a so-called "soft brick" isn't really a brick per se, but when even articles in the XDA portal throw around the terms "soft" and "hard" bricks, I would say that the genie is out of the bottle and these terms have, for better or worse, entered the common parlance. I do, however, appreciate the input and quite possibly this is simply a hardware issue, although I will, when time allows, try to wake the phone up with a jig.
gastonw said:
yada yada yada I've heard some developers use "unbrick". Go tell 'em there's no such a thing.
And stop worrying about semantics.
Click to expand...
Click to collapse
BS!
If thats the case link me one single post where any respected dev refers to a system boot issue as a "soft brick".
The only conceivable time they would refer to that is simply to try and help a n00b and it was quicker to refer to it in that way then to explain things.
You can only "unbrick" if your device is "bricked" and having a rom or kernel issue resulting in a system not booting is not "bricked", Its as simple as that.
So there I was, trying to reset a few phones so I can return them back to the reseller. Only after I rooted them and started loading software did I realize they did NOT support 4G LTE. DEAL BREAKER!!! After unrooting and setting the binary counter back to zero (which I can now do in my sleep, or lack of sleep), no matter what I did or what instructions I followed the phones still came up as Custom.
Quite by accident I discovered a way that worked 100% on all the remaining phones I needed to reset.
While flashing a known good ROM (which, by the way, finding a known good ROM is harder than you would think for a total NOOB), Odin froze up and stopped! HORROR! Not to worry since I have recovered from a soft brick way too many times in the last two weeks. All other soft bricks were due to incompatible ROMS, not an interruption in the flashing process.
Turns out Odin freezing and stopping the rom flash reset something in the phone. I rebooted everything, did a reflash with the exact same ROM, factory/cache reset and now my phone shows "Official".
Yes it is nerve racking to pull the cable half way through the flashing process. Before you flame me remember that initially Odin stopped in the middle. I did not decide to bail half way through. I was forced into it. Any idiot knows you might brick your phone pulling the cable half way through the process.
I can now get OTA updates.
Just thought I would share rather than make my first post a question.