I bricked my phone with the ICS 4.0.4 firmware
Recovered using the PIT file
i9100_u1_02_20110310_emmc_EXT4-patched-standard
So the phone booted, and I lost 2 gb of internal sd space, as expected.
But why am I not able to copy anything to the internal SD card?? Copying to ext sd is ok.. If I connect to the pc to copy to int sd the phone freezes..
Sometimes it freeze while downloading apps or opening apps.. Why? Can also freeze if I open the camera app..
A brilliant xda member helped me recover the phone.. Thanks to XDA forum and its members..
Jst wanted to knw if anyone have encountered such a problem, and know the reason for the freeze
Pls help
Same her man,i have bricked my phone with 4.0.4 lq5 and full wipe with cwm recovery. Than i flashed ums bricked pit ext4 becouse standard pached pit wont bot rom. Now my phone is working but have freazes when instaling apps and games. Best working is on android 2.3.5 . I am waiting if ther any solutions for that problem . I have tried twice flashing pits to repair problem but then my phone is hardbricked and i have then go to repair shop and worked jtag,after jtag same thing phone only bots with ums bricked pit????
Sent from my GT-I9100 using xda app-developers app
vislavskid said:
Same her man,i have bricked my phone with 4.0.4 lq5 and full wipe with cwm recovery. Than i flashed ums bricked pit ext4 becouse standard pached pit wont bot rom. Now my phone is working but have freazes when instaling apps and games. Best working is on android 2.3.5 . I am waiting if ther any solutions for that problem . I have tried twice flashing pits to repair problem but then my phone is hardbricked and i have then go to repair shop and worked jtag,after jtag same thing phone only bots with ums bricked pit????
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Try to completely restore Stock Rom (doesnt matter if its Gb ir Ics) and get rid of any clues it has ever been tempered with. Then send it to Samsung for warrany repair.
Sent from my Galaxy S2 GT i9100
boki9999 said:
Try to completely restore Stock Rom (doesnt matter if its Gb ir Ics) and get rid of any clues it has ever been tempered with. Then send it to Samsung for warrany repair.
Sent from my Galaxy S2 GT i9100
Click to expand...
Click to collapse
But i dont have warranity ???
How? The warranty is 2 years and the phone has been out about a year and half, maybe less.
Sent from my Galaxy S2 GT i9100
Well i have byed used phone and i dont have waranity. I am asking to any solutions for my problem not for waranity problems...
Sent from my GT-I9100 using xda app-developers app
saiyanajay said:
I bricked my phone with the ICS 4.0.4 firmware
Recovered using the PIT file
i9100_u1_02_20110310_emmc_EXT4-patched-standard
So the phone booted, and I lost 2 gb of internal sd space, as expected.
But why am I not able to copy anything to the internal SD card?? Copying to ext sd is ok.. If I connect to the pc to copy to int sd the phone freezes..
Sometimes it freeze while downloading apps or opening apps.. Why? Can also freeze if I open the camera app..
A brilliant xda member helped me recover the phone.. Thanks to XDA forum and its members..
Jst wanted to knw if anyone have encountered such a problem, and know the reason for the freeze
Pls help
Click to expand...
Click to collapse
how about factroy reset?
I have tried factory reset but same thing
Sent from my GT-I9100 using xda app-developers app
don't think anything can be done in all honesty
boki9999 said:
How? The warranty is 2 years and the phone has been out about a year and half, maybe less.
Sent from my Galaxy S2 GT i9100
Click to expand...
Click to collapse
The warranty is for one year
So replacing the motherboard is the only solution I guess
How did you manage to boot the bricked phone and load the pit file? jtag? Thanks
saiyanajay said:
I bricked my phone with the ICS 4.0.4 firmware
Recovered using the PIT file
i9100_u1_02_20110310_emmc_EXT4-patched-standard
So the phone booted, and I lost 2 gb of internal sd space, as expected.
Click to expand...
Click to collapse
Help us!
Before I recovery my Galaxy S2 from emmc brick, when i download an app or anything my phone freezy. I'm crazy . I found a forum which looks will help us. http://forum.xda-developers.com/showthread.php?t=1760107
Somebody who knows how to use this tutorial, please put step by step here or post a new tread.
Thanks for all anyway
Hello , I had the same problem , I searched a lot ,but It seems that the only solution is to replace the motherboard.
BUT:
I have tried many roms , I found that cm10 , cm10.1 is working very well , with no freeze . try cyanogenmod
Lol, everyone that soft bricks their devices thinks that it's eMMc's bug.
And I dunno why everybody loves to dance with pit files.
Monsters never scared me, pit files do.
gastonw said:
Lol, everyone that soft bricks their devices thinks that it's eMMc's bug.
And I dunno why everybody loves to dance with pit files.
Monsters never scared me, pit files do.
Click to expand...
Click to collapse
Yeah and everyone who simply cant get system partition to boot seem to think their device is "soft" bricked.
No such thing as a soft-brick. Your device is either bricked or it isnt, ie when you need to JTAG flash or motherboard replace. Anything less, ie when you can simply just re-flash a kernel or rom via download/recovery is not bricked in any way.
TheATHEiST said:
Yeah and everyone who simply cant get system partition to boot seem to think their device is "soft" bricked.
No such thing as a soft-brick. Your device is either bricked or it isnt, ie when you need to JTAG flash or motherboard replace. Anything less, ie when you can simply just re-flash a kernel or rom via download/recovery is not bricked in any way.
Click to expand...
Click to collapse
I think we had this conversation before....went something like...this:
Your statement:
Bricked Phone: useless phone.
Non Bricked Phone: working phone/system failure/whatever phone has got that can be reverted.
Unbrick: Something that is accomplished by a riff box jtag or mobo replacement.
Mine (and a whole lotta people):
Bricked phone / hard bricked phone: Dead man, dead.
Soft-bricked phone: system failure/whatever phone has got that can be reverted.
Unbrick: revert the system issues making it work properly, re partition, riff box jtag or mobo replacement or whatever that brings the phone back to life.
As you can see, we are talking about the same, we only brand it with different names.
Now, the thing is that we call it a brick because we can't use it, and judging by the device's wheight we call it a brick, it's got brick's uses only.
Same applies to Soft brick, that stands for Software bricks, an unusable software , that without of people wanting to help other people (here at xda and forums alike) would became either bricks or just a service center scam ( giving them the possibility to say "You must have dropped it, we changed the hardware and it costs $ 250").
Same happens with the unbrick concept. Tell me, as you are being "technical", how in gods name do you unbrick a brick? what, you apply some glue?
Exactly, makes no sense, that's why we call it a metaphor.
wouldn't you agree now?
No.
Bricked is when you need extra hardware to repair problem other then standard USB cable. ie new motherboard or riff box/jtag connection. If you can simply boot device and re-flash something by normal means there is nothing wrong with your device and PEBCAK, and is not "bricked".
"soft-brick" is just a term coined by n00bs who find it easier to use the term when they screw system up somehow and cant get partition to boot or have boot loop etc etc. Only reason its used allot is because we have many many n00bs on here and the term has simply stuck.
The term "bricked" is used far too loosely noways.
TheATHEiST said:
No.
Bricked is when you need extra hardware to repair problem other then standard USB cable. ie new motherboard or riff box/jtag connection. If you can simply boot device and re-flash something by normal means there is nothing wrong with your device and PEBCAK, and is not "bricked".
"soft-brick" is just a term coined by n00bs who find it easier to use the term when they screw system up somehow and cant get partition to boot or have boot loop etc etc. Only reason its used allot is because we have many many n00bs on here and the term has simply stuck.
The term "bricked" is used far too loosely noways.
Click to expand...
Click to collapse
Yeah, I meantioned what you thought about that term in my previous post, here, let me get auto quoted:
gastonw said:
Your statement:
Bricked Phone: useless phone.
Non Bricked Phone: working phone/system failure/whatever phone has got that can be reverted.
Unbrick: Something that is accomplished by a riff box jtag or mobo replacement. HENCE THIRD PARTY INVOLVED
Click to expand...
Click to collapse
+
I'm sticking with the Soft-Brick term, It's just so cool to use.
Guess I'm a noob then....hold on a sec...I am a noob, first flashed Dec, 19 2012.
So, nothing new here, oh yes, unbrick term is missing.
Let me know when you think of a non-loose answer for that.
I'd really like to see a brick become unbrick (explained with technicalities).
Lol, if we get thru this, the next thing we all gonna be arguing about is english language.
gastonw said:
Yeah, I meantioned what you thought about that term in my previous post, here, let me get auto quoted:
+
I'm sticking with the Soft-Brick term, It's just so cool to use.
Guess I'm a noob then....hold on a sec...I am a noob, first flashed Dec, 19 2012.
So, nothing new here, oh yes, unbrick term is missing.
Let me know when you think of a non-loose answer for that.
I'd really like to see a brick become unbrick (explained with technicalities).
Lol, if we get thru this, the next thing we all gonna be arguing about is english language.
Click to expand...
Click to collapse
The term "bricked" has always meant same on XDA, Its only these past few years when smartphones have become more popular with mainstream public and XDA has had a huge flood of n00bs screaming "hey I haz bricked me fone " that terms like "soft-bricked" has come into play because n00bs kept thinking their device was bricked when it was simply a bad flash or system had problems booting etc.
Bricked is when your phone cannot be used/flashed without extra hardware like when you corrupt your bootloader for example.
A "unbrick" would be when you use this extra hardware to resolve issue with your device.
TheATHEiST said:
The term "bricked" has always meant same on XDA, Its only these past few years when smartphones have become more popular with mainstream public and XDA has had a huge flood of n00bs screaming "hey I haz bricked me fone " that terms like "soft-bricked" has come into play because n00bs kept thinking their device was bricked when it was simply a bad flash or system had problems booting etc.
Bricked is when your phone cannot be used/flashed without extra hardware like when you corrupt your bootloader for example.
A "unbrick" would be when you use this extra hardware to resolve issue with your device.
Click to expand...
Click to collapse
Following that reasoning PC should be consider considered extra hardware.
As I said before, we are talking about the same thing here, we only call it differently.
Related
Hey,, I recently got my galaxy s2 and im new in the android thing,, i want to flash my phone to litening rom but im worried that i might brick it,, what are the chances that i may brick my phone? tnx and more power
The risk is very small as long as you follow the instructions to the letter. Read from start to finish a few times before doing anything and double check everything. It's actually all very easy and straightforward
Edit: and have a look at the thread about backing up your EFS folder before flashing (you'll need root) it's in the dev section somewhere.
Sent from my GT-I9100 using XDA Premium App
99% chance of no problem rising to 100% chance of a brick if not following instructions .
Recover from a bricked phone = 99% success rate .
jje
JJEgan said:
99% chance of no problem rising to 100% chance of a brick if not following instructions .
Recover from a bricked phone = 99% success rate .
jje
Click to expand...
Click to collapse
^^^^^^^^^^^^^^^^^^^^^^^^ THIS
But how hard is it to really brick a SGS2 ?
I think i read about 1 person who couldnt get his phone up and running again .
SGS2 i belive is really hard to brick.
Sorry for my bad english
There are enough who totally brick a phone in the course of a year . But its hard to do plenty of oh hell moments but recovered flashing stock rom .
Brick tends to be a misused term SGS brick means it should work after flashing stock rom via odin . Other phones brick means dead phone return to factory no hope .
jje
As long as you never tick "Re-Partition" and insert the PIT in Odin its almost imposable to brick unless you somehow nuke the bootloader(which you shouldn't be able todo via flashing custom roms).
I dont even think theres much of a chance of radio bricks, worst that happens is that you have to re-flash.
veyka said:
As long as you never tick "Re-Partition" and insert the PIT in Odin its almost imposable to brick unless you somehow nuke the bootloader(which you shouldn't be able todo via flashing custom roms).
I dont even think theres much of a chance of radio bricks, worst that happens is that you have to re-flash.
Click to expand...
Click to collapse
I think once the radio is corrupted a new flash is impossible, well it is on HTC devices
[email protected]
Sent from my Samsung Galactic Crusader S II
tnx guys for the reply,, will follow the instruction carefully,, hope everything will be ok,,
Is it possible to recover from a bricked phone?
svj1187 said:
Is it possible to recover from a bricked phone?
Click to expand...
Click to collapse
As long as one of the (secondary) bootloaders is still intact and you can get into download-mode (maybe by using the USB jig), then yes.
JupiterdroidXDA said:
I think once the radio is corrupted a new flash is impossible, well it is on HTC devices
[email protected]
Sent from my Samsung Galactic Crusader S II
Click to expand...
Click to collapse
Nah, just flash the modem and all is good.
sadly,am new to android !! I read a forum in d web tat asked to load a file in pit for lightening rom and i bricked d device. Now its in service centre,hope it comes back alive
santhoshkcsk said:
sadly,am new to android !! I read a forum in d web tat asked to load a file in pit for lightening rom and i bricked d device. Now its in service centre,hope it comes back alive
Click to expand...
Click to collapse
If the service centre can't fix (when I sent mine to one they told me it was beyond economic repair) don't lose hope as this guy will probably be able to repair it for you: http://forum.xda-developers.com/member.php?u=1602851
Ended up being cheaper than if my local service centre had been able to repair it too.
Being new to flashing I was also very scared at the start. I was pulling my hair out when the first time I flashed a new rom and got stuck in a boot loop. Luckily I backed up the entire system and I was able to restore.
Make sure you do a back up of your system first.
The first time its scary, I had no nails after the first flash lol. But after that its fun, just make sure to read everything and follow the instructions to the letter.
Good Luck!!
Sim card not recognized
I have rooted by galaxy s2 and my phone fails to recognize the sim card and unfortunately I didn't backup my original rom to restore the previous settings
I tried various things: hard reset, install alternative (custom) roms all seem to have no effect on the sim card.
I am getting quite frustrtated with this, is there an original ROM for my location (GREECE, VODAFONE) to try with odin ? I should note that my mobile seems not to connect with the PC when I try to connect it via kies (odin works instead)
Is there a possibility that the phone's card sensors are physically damaged, thus return it for repairs ?
Thanks for your time
Hi,
I have a Galaxy S2 i9100.
I was using ODIN to update de OS but I left checked the RE-PARTITION
box and now it´s dead.
I think that I erased the main memory so I can´t turn it on, no
charge, no nothing.
I couldn´t even enter in Download mode.
So I think it needs a hard reset... can you help me?
same problem if some one can answer this i will be happy
rocholaroca said:
Hi,
I have a Galaxy S2 i9100.
I was using ODIN to update de OS but I left checked the RE-PARTITION
box and now it´s dead.
I think that I erased the main memory so I can´t turn it on, no
charge, no nothing.
I couldn´t even enter in Download mode.
So I think it needs a hard reset... can you help me?
Click to expand...
Click to collapse
was using odin with checked re-partition and now its dead
is there any way to fix it?
the phone is 2 days old i dont think the store will take it back becasue of the rooting and rom changing
A JTAG repair is the only thing that can fix it I believe.
SGS2 - Download mode but no recovery
Hi!
I have a bit of a problem here as well when i was trying to flash back to the stock firmware. Now when I try to get to the clockwork recovery mod, I get the famous dead screen with symbols of mobile phone, exclamation point and a pc. I have been searching solution to this problem for hours now, and still I don't want to quit.
My previous custom rom was installed in with no problems. Litening rom 3.0.
Now, with usb jig i can get into the download mode, no problem there. It just seems that the traffic is just jammed.
Download mode works but Odin doesn't transfer anything. Gets stuck on the factoryfs.img while i'm trying to flash. Kies doesn't recognize the phone but pc recognizes the USB device with no problem. Original stock firmware doesn't load on the phone. Odin just stops transferring.
Things I've tried so far.
-Reflash (both litening rom again and stock firmware) with odin (Kies is not on while I do this, I checked)
-Kies (doesn't work)
-Download mode does work but it seems that phone doesn't accept any files.
-I tried the one-click unbrick which seemed to do something god but failed at the end.
What could I still try? I'm running out of options now.
I apologize for my bad english.
I have a Galaxy Ace that I upgraded to Gingerbread manually. It worked fine, to the point where I decided to flash ClockworkMod. I backed-up the ROM when the screen turned off (and the device too, apparently). Great, brick.
But I received it as a brick and recovered it once, so no big deal - I fired up ODIN, got all the firmware files ready, got the phone in the three-button (volume down + power + home) download mode, the OS detected the device (still no Download... label on the screen) but when I try to flash it, ODIN is stuck at "Setting up connection".
I've done a fair amount of research and so far I read that a CWM-induced brick is pretty much hopeless - the phone needs to be sent in to the service center. Also, it appears that in many cases JIG isn't of much help with the same conditions.
Any ideas on whether I can unbrick this phone?
If may ask, from where did u get the cwm?
Sent from your phone
Via ROM Manager.
And so, this is the answer.....
ROM MANAGER BRICK GALAXY ACE GT-S5830
That is obvious. As I said - I've read about similar situations. Too late to look back at it.
My question is - is there any chance of manual revival through existing tools?
Have you try this? http://forum.xda-developers.com/showthread.php?t=1071970
Rom manager known to hard brick ace. As u already stated that u've tried jig and it doesnt works, so no, theres no other way except to send it for repair. Sorry for your lost.
Sent from your phone
@Teflon Yes, that is the first thing I tried. No go.
@an0 curious - it is not possible, even though the modem is supposedly detected? ODIN has the StartThread indicators, so I am guessing the phone is in some type of "download mode".
i dont know for sure what it does to make ace brick, maybe messed up bootloader, maybe messed up partition layout, but as for now theres no known way to recover ace from bricking with rom manager.
It's worth exploring though. There's always a logical reason for these things.
@ZeBond sorry to hear your phone is bricked, but if you do find a solution (or even a reason for why it did/does it) could you update this thread with it?
what i'm always thinking every time this type of thread appear, in all these time rom manager known to brick our device with many users experience it themself, no one bother to contact rom manager dev (its koush right?) and inform him about this?
from all the person in the world, he might know what could possibly go wrong to make such disaster.
I will update this thread if I find a solution. Contacting the dev sounds like a plausible idea, going to look into that now.
same situation here.. ill apreciate if you post the solution when you find it! thanks.
Use JTAG To revive it
Sent from my GT-S5830 using xda premium
jtag
Ty Farooq.. But that seems very technical.. I dont think i can do it easily. I found this service: http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-ace-s5830-1/
Any experiences?
thnxs alot
Rom manager bricked my phone too..though i was at fault in flashing the wrong recovery..lmfao..but the service center fixed the phone without much ado..i guess they replaced the motherboard...
Sent from my SGA rocking CM7.2 by vo-1 + all-in-one script
Hello
I have a question to do with the jtag, actually a couple of questions.
So here is what happened:
I have (or had :crying: ) an samsung galaxy s2 and I think I have hard bricked it, don't know how tough. I was prompted to download the updates for the apps i have on the play store, afterwards i came across an error saying something like 'failed to install'. And after that everything started crashing, so i thought a restart would do the trick and fix it. So i left it for about 5 minutes and the it still hasn't shut down, so the best thing i could think of was to take out the battery, afterwards i couldn't turn it on(No vibration, screen was black) I have tried the usb jig and failed (either because i was using Stock ICS or probably because the bootloader has been messed up somehow), So the last thing i could try is to send it off to a company near my area who jtag phones(already found one).
The cost is not that big so it doesn't really matter to me (only £25) and im about 99.9% sure that i will do this, but i just want to know a couple things to be sure before i send it off to be jtagged.
1. Does my whole phone memory get deleted in the process?
2. Will a jtag solve my problem?
3. After the riff box or something other has finished jtagging my phone, will i be able to use the phone normally and be able to flash roms?
4. Does jtagging affect anything else other than the software (bootloader,modem etc....) ?
5. Will jtagging my phone bring any thing extra (except the fact that it will work :3 )?
And also i am not really worried if it don't ever work any more because i do have any other sgs2 that i can use but having 2 would be better for my personal use ( long story about why). Any answers will be appreciated. And sorry if i posted this in the wrong sub-forum but i guess it is mostly questions so i think i got it right.
Thanks
If you haven't rooted or installed a custom rom, send it for warranty repair. No need for Jtag.
Sent from my Galaxy S2 GT i9100
boki9999 said:
If you haven't rooted or installed a custom rom, send it for warranty repair. No need for Jtag.
Sent from my Galaxy S2 GT i9100
Click to expand...
Click to collapse
i have rooted and installed custom rom's on it many times, but i have reset my flash counter using some program by an xda dev. i dont seem to have a warranty and i'm willing to pay £25 for the jtag so that i don't have to wait long for my phone to be back where it belongs i just want to know a couple of things before i send it off
Well, as far as I know, Jtag brings your phone back into clean factory working state. And I think the entire memory is wiped.
A new bootloader is installed as well since the phone cant be booted. When the bootloader is screwed, the phone is bricked beyond repair for the user. Everything stock is installed, similar to flashing stock rom.
After that you can flash roms again like nothing happened.
And Jtag doesnt bring anything else than a working phone.
Sent from my Galaxy S2 GT i9100
boki9999 said:
Well, as far as I know, Jtag brings your phone back into clean factory working state. And I think the entire memory is wiped.
A new bootloader is installed as well since the phone cant be booted. When the bootloader is screwed, the phone is bricked beyond repair for the user. Everything stock is installed, similar to flashing stock rom.
After that you can flash roms again like nothing happened.
And Jtag doesnt bring anything else than a working phone.
Sent from my Galaxy S2 GT i9100
Click to expand...
Click to collapse
Thanks for the answer, i was hoping it wouldn't wipe the memory (Internal 16gb that i have) because i have data on it that would be useful for me but as long as i get this phone working i'm happy Thnaks again
Well, you could ask the serviceman what could be done with the data...
Sent from my Galaxy S2 GT i9100
I asked but no luck :L, because of how jtagging is done there is no way of retrieving the memory its self. Now i know to always use external SD cards. I still don't get how it happened though since i wasn't flashing anything and haven't flashed anything for the past 2-3 months
Hi!
I just had the weirdest experience with my sgsii
I have been using the unofficial vsync patched cm10 rom for this modelfor the last month or so.
I have been updating at least one per week but this week I decided to give my phone a break and not flash it... i am actually really busy at job.
Suddenly tonight, the phone looked like when you have a SOD... so i just pulled the battery.
Now, it does not pass from the first logo stage, just prior to start booting.
I cannot access cwm recovery either, but download mode seems to work-
Now the odd thng is that i am attempting to flash somethng to get the phone working but it gets stuck in the step "NAND Write start!".... it goes no furter than that...
I have chosen the options auto reboot and f.reset time.
a pda file, phone and csc file from the eaked jb rom.....
The system I am attempting to flash from is a windows 7 pro 64 bit.... and odin is Odin3 v1.85...
Please, tell me i didnt get a brick and there is a way tofix it... :crying:
EDIT: Desperated, i tried to flash latest jb leak again, and chose the pit file that comes with it, which re-partitions the phone...
After 20 minutes not responding, i pulld the battery out... now i cannot even enter download mode....nothing....nada....
Sounds like you bricked it, good job.
Sent from my GT-I9100 using Forum Runner
GFXi0N said:
EDIT: Desperated, i tried to flash latest jb leak again, and chose the pit file that comes with it, which re-partitions the phone...
After 20 minutes not responding, i pulld the battery out... now i cannot even enter download mode....nothing....nada....
Click to expand...
Click to collapse
too bad never repartition unless you make your own pit file with heimdall .. if you would've wait a couple hours I just pmed you.
and for other people instead of flashing samsung's bricksquadroms you can flash CM9 resurrection edition. http://forum.xda-developers.com/showthread.php?t=1419102
Make a pit file with heimdall of your own device. Don't trust pitfile that comes with a rom.
I re-partitioned my device and i got like 3GB intern memory back.
There's probably a way to get your device alive. it isn't the mmc cap bug so. search some threads on xda about brickbugs etc of galaxy phones and you'll find people who hardbricked and unbricked their device.
Probably usb jig could get you into download mode i'm not sure though. Or else jtag. Ask some people over there they will know it
I will try to revive it with jig.... i must find the thingy though.,..... if not.. i will send it to the service but i'm not sure i'm on warranty....
Being not patient made me f*ck it up bad....
Any clue on how to recover a phone after re-partitioning.... i really don't know where to start...
EDIT: JIG does not switch it on either... why did i have to re-partition?!??!?!?!?!?!
That was a dumb move....... any more ideas?
If you cant enter recovery or download mode you have no choice but to JTAG repair or mobo replacement.
Hard brick.... on its way to service
Wish me luck..
Mobo replacement it is, this incident will at least teach you to be patient, I explained you my problem in PM, I waited for 1 week for USB jig to arrive from eBay then flashed stock ROM. I trust the f/w it came with the most.
Sent from my GT-I9100 using xda app-developers app
Sh4Dy said:
Mobo replacement it is, this incident will at least teach you to be patient, I explained you my problem in PM, I waited for 1 week for USB jig to arrive from eBay then flashed stock ROM. I trust the f/w it came with the most.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
USB JIG didn't work at all..... I have one and it was not able to boot the phone ....
Isn't this kind of brick fixable with Jtag?
Sent from my GT-I9100
Ok, before I repartitioned, making the problem worse, I was experiencing some kind of R/W problem..... there was something odd with the nand because I was able to boot in download mode, but not in recovery (CWM) mode....
Then, when I plugged the phone to the computer, Odin was able to recognize the phone.
I followed some thread around XDA to flash 4.1.2 leak from sammy and when I hit the "Start" button in Odin, it would not pass from the first stages, revealing that R/W or I/O problem.... the internal nand was, somehow broken.... it didn't read or write properly.... so, even If i could find a workaround, I would have lost some internal storage (some posts talk about around 3 Gb or something similar as lost space in these cases).... that is IF i had been able to fix it..... but then, that's what warranty is for..... so I gave it a last (dumb) try..... including the pit file, which attempted a format, which ended messing (i would say the f. word) everything up.
The good side is that unable to even boot, at least i lost the blue loading bar the vsync patched cm10 mod has in the first bootup screen.... which could have revealed to sammy that I was tempering with unofficial roms....
Lesson learned: Be patient people: But also, don't think this could not happen to you: The phone was perfectly working the last time I saw it... and I even was making some phone calls and browsing the internet.... I mean... it gave no prior symptoms or warnings... I t just died..... I guess I have to be glad I'm not one of those people whose phone gets caught up on fire on their pockets for malfunctioning.....
Now waiting for it to come back revived from samsung..... I have hope
hope it will be able to recover
Great: After losing the phone and past almost three months, samsung says the phone has been manipulated and the warranty is voided....
I wasn't able to flash back an original firmware prior to sending it to the tech service.....
What do you recommend me to do?
I guess paying for the repair would be quite expensive....
GFXi0N said:
Great: After losing the phone and past almost three months, samsung says the phone has been manipulated and the warranty is voided....
I wasn't able to flash back an original firmware prior to sending it to the tech service.....
What do you recommend me to do?
I guess paying for the repair would be quite expensive....
Click to expand...
Click to collapse
Well what is it you expect us to say, some secret magic word that will fix it for free?
The choice is pay for it to be fixed or dont.
So no magic word or secret passphrase so they will upgrade my device to a SGSIV for free?
Damn.....
I'm asking for advice, since I'm convinced the brick was not caused by flashing anything.....
Does anyone have any experience with this in the past to know more or less how expensive bill could I be facing for the repair?
GFXi0N said:
So no magic word or secret passphrase so they will upgrade my device to a SGSIV for free?
Damn.....
I'm asking for advice, since I'm convinced the brick was not caused by flashing anything.....
Does anyone have any experience with this in the past to know more or less how expensive bill could I be facing for the repair?
Click to expand...
Click to collapse
Dude, it WAS caused by flashing something.
Initially your device wasn't "bricked" and was likely a kernel issue and possibly a dirty usb data connection.
The point when it was bricked was when you tried flashing the pit file, had bad connection and you then pulling battery. This f**ked your nand chip up and only way to fix it is to replace motherboard.
You will need to either purchase a mobo replacement and replace it yourself or pay somebody to purchase/replace it for you. Probably looking at around £100.
When bricks happen, you really need to BRICK it before claiming warranty.
I've got a couple of guys here that own a PhD in bricking.
Brick is the new flash.
Sent from the little guy
Jig wasn't working
Flashing anyting.. even just a recovery wasn't working
FLashing official didnt work
Flashing CM didnt work either
Tested different cables and different ports
It was f*cked up already... anyway: 4 samsung devices owned: 3 gave problems of hardware..... that cannot be a coincidence...
Repartitioning erased my tracks, if anything... because the 3 key combo for recovery was working until then..... but either way they managed to access the memory somehow, I guess.....
GFXi0N said:
anyway: 4 samsung devices owned: 3 gave problems of hardware..... that cannot be a coincidence....
Click to expand...
Click to collapse
Maybe a PEBCAK?
GFXi0N said:
Jig wasn't working
Flashing anyting.. even just a recovery wasn't working
FLashing official didnt work
Flashing CM didnt work either
Tested different cables and different ports
It was f*cked up already... anyway: 4 samsung devices owned: 3 gave problems of hardware..... that cannot be a coincidence...
Repartitioning erased my tracks, if anything... because the 3 key combo for recovery was working until then..... but either way they managed to access the memory somehow, I guess.....
Click to expand...
Click to collapse
Don't blame the phone, blame the user.
Yeah, sure... anyway... thanks for the help... I hope some day you need it and someone will come not trying to mocking you..... anyway... this is the trend around here lately...
Happy trolling
Hey guys !
Well...
Yesterday, I decided to flash a new ROM on my aunt's SII...
It wasn't the first time I did this : my own phones have all been flashed, I know how it works !
But... I got a problem ! While I was wiping the data/cache, the phone got stuck on this step. Then, shut down. And now, it doesn't boot anymore. Screen stays black. I did everything I found on the web : tried to boot on recovery and on download mode, tried to press the buttons to get into these modes and inserting the battery while pressing, tried to connect it on USB (not even detected)...
After some researches, I found out that it was a eMMC problem...
Anyway, in a nutshell, my phone is hard bricked. What can I do ?
Thanks.
rohecla said:
Hey guys !
Well...
Yesterday, I decided to flash a new ROM on my aunt's SII...
It wasn't the first time I did this : my own phones have all been flashed, I know how it works !
But... I got a problem ! While I was wiping the data/cache, the phone got stuck on this step. Then, shut down. And now, it doesn't boot anymore. Screen stays black. I did everything I found on the web : tried to boot on recovery and on download mode, tried to press the buttons to get into these modes and inserting the battery while pressing, tried to connect it on USB (not even detected)...
After some researches, I found out that it was a eMMC problem...
Anyway, in a nutshell, my phone is hard bricked. What can I do ?
Thanks.
Click to expand...
Click to collapse
what stock firmware version was the Phone when u did the wipe from recovery (if it was on ICS 4.0.4 then ur phone will be bricked because of the kernel of ICS4.0.4 being plagued with the 'EMMMC' brick bug and only a JTAG or a MB replacement is the solution for it) .
JTAG won't work; motherboard replacement or bin.
I think it was 4.0.4...
Motherboard replacement is the only thing I can do ?
Mate.... Samsung KNOWS this is a problem.......I'd try for warranty repair/replacement.....if the phone is less than two years old, you have a good chance......
Just remember to 'act dumb' at the service center..... Tell them you were trying to use kies to update from ICS and the phone died...... If it is the emmc brickbug, there's NO WAY they can check what os was on ur phone or whether you'd rooted or modified it in any way.....right now it's an unrecoverable (expensive) paperweight........
This might be my S2, or it might be my W...but it's definitely CM
Yeah, I saw this is a quite common problem... But often, it's just a soft brick. In my case, it's a hard brick...
And warranty expired two months ago...
Well, it's unlikely to succeed, but you could try emailing Samsung explaining your situation regarding expired warranty and going on to explain that updating with kies is a 'normal' procedure and that it's that 'normal' Samsung provided procedure plus the 'unstable' OS version (having read on the internet about 4.0.4 brickbug) that have killed a phone that would otherwise be working today. Stress the point that the ICS firmware AND kies were both supplied by Samsung for official (end user) use on Samsung devices......see what they say.....can't hurt right?
This might be my S2, or it might be my W...but it's definitely CM
Yeah, they're going to honour an expired warranty. That happens all the time
Mb....I *did* say right at the start that it probably wouldn't work..... But what has he got to lose?
Lol.....they *might* be suffering from an excess of Xmas and new year goodwill.......
This might be my S2, or it might be my W...but it's definitely CM
I have twice super bricked my two SGS-2s.... EMMC bug is one hell of a pain in ass. You have to let go some SD card space, but u can revive you phone using the URL in my signature. I revived both my phones losing about a GB space in one and a couple GBs in other. Good Luck
alvinasnow said:
but u can revive you phone using the URL in my signature
Click to expand...
Click to collapse
People have said he needs a new motherboard.Do you know something they dont?.
S4 victim
The problem is that I can't flash anything ! The phone simply doesn't turn on ! No recovery mode, no download mode, nothing ! It doesn't even charge !
Yes try this link from alvinasnow
http://forum.xda-developers.com/showthread.php?t=1667886
So far as I know if you only connect your phone normally if it os charging then it already has some kind of connection with the pc I believe its adb.
But since you dont have warranty you can give it a shot to save money so just give it a try and read carefully. I was surprised when I got this phone, that samsung would make a big mistake like that its a just shame.
Edit: i dont know or you need jtag or riff and I will not test it cause I dont have a superbrick phone with mmc cap erase.
But just open device manager on the pc and connect the phone and see if there is a new device connected.
In my opinion my previous phone has one of the best options to make it unbrickable
It was nvflash but it sucked.nvidia wouldnt release sources.
Gooodluck with your phone
Sent from my GT-I9100 using Tapatalk
Which part of this phone needs a motherboard replacement are you lot having trouble comprehending ?
OK...For all the slow kids who keep posting to this thread (including the OP); this phone needs a new motherboard. No threads promising magical fixes are going to work, there is no other way to fix this.
Is this clear now or do I have to make another post in bolded caps to make it really clear ?
There is a SLIGHT chance that if a JTAG recovery house can boot a kernel via JTAG (I do not know if RIFFBox can do this or not), they can use the solution that the Kindle Fire community used. (This was a recent discovery 2-3 months ago)
The problem is, I have attempted to provide information on this solution to these JTAG houses with no response. I don't know if they can boot a modified kernel via JTAG or not.
Currently:
All Exynos4 devices that are Superbricked are unrecoverable, as Samsung refuses to provide any way to boot these from USB, and anyone who could develop a solution hasn't responded (since most dead devices are long gone at this point...)
All Qualcomm-based Samsungs that are Superbricked are hosed too
Kindle Fires that are Superbricked are recoverable as of 2-3 months ago thanks to some discoveries by Oranav that were used by Hashcode to develop a recovery solution. This solution can't be used on Samsung Exynos4 devices as it depends on the ability to boot the device from USB.
And folks...... @Entropy512 needs to be listened to.......he is the dev who has done the most research into this issue and (somebody cmiiw) was the one who discovered the "emmc cap erase" command was the culprit. I think he also wrote the original (much copied) 'got brickbug' app which tells you if your phone is affected or not. If what he says doesn't work, then as @MistahBungle says, the ONLY OTHER OPTION is a new motherboard........
This might be my S2, or it might be my W...but it's definitely CM
Well...
I think I'm just going to call the insurance, and see what they can do ! Even if my warranty is now void, they may replace the phone !
Thank you all !