Can anyone say when galaxy tab p1000 gets hard bricked? Everytime mine gets bricked, its a soft brick
If you try to flash, say a rom from another device and the rom contains a boot loader, you will hard brick it.
Sent from my GT-P1000 using XDA
If I heard right, if 2 files aren't flashed properly in Odin or Heimdall (boot and something else?), you can hard brick that way too.
The 2 files are the first things flashed in Odin if I recall correctly
About the only way to hard brick your Tab is by damaging the Primary boot loader (boot.bin) and the Secondary boot loader (sbl.bin). If these are damaged, you can't get to download or recovery mode anymore, and need extra hardware to be able to flash a ROM again. You can do this for instance by yanking out the cable during a flash, but even then you would have to be unlucky, because these files are small, and will be flashed in seconds. Flashing a ROM with boot loaders for the wrong Tab could do it too I bet.
BTW, it sounds like you are trying to hard brick it, and are frustrated you're not succeeding. Surely I'm wrong about that.
gogol1996 said:
Can anyone say when galaxy tab p1000 gets hard bricked? Everytime mine gets bricked, its a soft brick
Click to expand...
Click to collapse
There is no such thing as a "soft brick", Thats is something n00bs just say when they screwed something up and cant boot into rom, your device is either bricked or it isnt. Its "bricked" when you cant get into download mode/recovery etc and only solution is hardware recovery like JTAG.
What you are referring to as "soft brick" is simply you not installing an OS correctly. Go and read/learn and then you will have no more "soft bricks"
TheATHEiST said:
There is no such thing as a "soft brick", Thats is something n00bs just say when they screwed something up and cant boot into rom, your device is either bricked or it isnt. Its "bricked" when you cant get into download mode/recovery etc and only solution is hardware recovery like JTAG.
What you are referring to as "soft brick" is simply you not installing an OS correctly. Go and read/learn and then you will have no more "soft bricks"
Click to expand...
Click to collapse
i can only confirm.
you can also brick you device by playing with efs partition , i saw this in some samsung devices wich have unock code reading protection .
TheATHEiST said:
There is no such thing as a "soft brick", Thats is something n00bs just say when they screwed something up and cant boot into rom, your device is either bricked or it isnt. Its "bricked" when you cant get into download mode/recovery etc and only solution is hardware recovery like JTAG.
What you are referring to as "soft brick" is simply you not installing an OS correctly. Go and read/learn and then you will have no more "soft bricks"
Click to expand...
Click to collapse
From my readings, "Soft brick" is a very common term that refers to a screen that shows a handset connecting to a computer. A form of DL mode that doesn't show the expected Andy construction sign. This is the only thing that will ever show on the screen until you successfully flash it.
Regarding the OP, if you ever manage to hard brick, check this guy out.
mobiletechvideos.mybigcommerce.com/samsung-galaxy-tab-jtag-brick-repair
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
arachnophile said:
From my readings, "Soft brick" is a very common term that refers to a screen that shows a handset connecting to a computer. A form of DL mode that doesn't show the expected Andy construction sign. This is the only thing that will ever show on the screen until you successfully flash it.
Regarding the OP, if you ever manage to hard brick, check this guy out.
mobiletechvideos.mybigcommerce.com/samsung-galaxy-tab-jtag-brick-repair
Click to expand...
Click to collapse
No, your device is either "bricked" or its not, its as simple as that. If you havent "bricked" it you simply go into download or recovery mode and reflash a rom, simple.
If you need extra hardware to recover your device like JTAG or you need to replace mobo, That is considered a "brick".
Thanks. At last hard bricked my device after deleting the *.bin files from the firmware before flashing.
Well download mode cannot be opened. Device does not light up.
Sent from my GT-P1000 using xda premium
Congrats! Let us know how the JTAG goes, will you?
Peace,
C.
gogol1996 said:
Thanks. At last hard bricked my device after deleting the *.bin files from the firmware before flashing.
Click to expand...
Click to collapse
Why are you trying to brick your device?
My second hand gt-p1000 was used by me for testing rooms before flashing on this one. Now I will try to unbrick it.
Sent from my GT-P1000 using xda premium
Ok
Sent from my GT-P1000 using xda premium
gogol1996 said:
Thanks. At last hard bricked my device after deleting the *.bin files from the firmware before flashing.
Click to expand...
Click to collapse
You are, Sir, very brave, Sir!
All this time I've been trying to avoid even a 'so called soft-brick' (Ok, I know there is no such thing, but I can't find other term) my tab, let a lone to brick it.
I can not imagine that I have to do that "Unbrickable Mod" fix requiring soldering and tweaking hardware.
---------- Post added at 10:28 AM ---------- Previous post was at 10:22 AM ----------
TheATHEiST said:
There is no such thing as a "soft brick", Thats is something n00bs just say when they screwed something up and cant boot into rom, your device is either bricked or it isnt. Its "bricked" when you cant get into download mode/recovery etc and only solution is hardware recovery like JTAG.
What you are referring to as "soft brick" is simply you not installing an OS correctly. Go and read/learn and then you will have no more "soft bricks"
Click to expand...
Click to collapse
May be the correct term is boot-loop or boot failure?
That's one way of looking at it, but it's actually not a bad idea to differentiate between two states of brickedness, and give them different names.
One state, familiar to many who flash their Tabs (which some may not even call a bricked state), is the result of a bad flash: the boot loader is intact, and you can get to download mode. However, if you just try to boot it, it will hang or get into a boot loop. This way it's as useful as a brick if you don't fix it, and many people won't know how to fix it. But more importantly, you'll need software to fix it (special hardware isn't necessary). So I like to think of this as a "soft brick".
In the other state there's something wrong with the boot loaders, and the Tab will not go into recovery mode. And yes, you've guessed it, you'll need special hardware to fix such a Tab, because the software inside a Tab needed to flash a ROM is itself damaged and therefore can't be used to flash a working ROM. It's definitely slightly less useful than a brick if you don't fix it, and even fewer people will have the resources to fix it, but it still can be fixed if you have those. Because it needs hardware I like to think of this state as a "hard brick".
You know it makes sense!
gogol1996 said:
Well download mode cannot be opened. Device does not light up.
Sent from my GT-P1000 using xda premium
Click to expand...
Click to collapse
I'd say you are crazy, but the fact is your post just made me calm when I experienced a boot-loop. Thanks man.
all you have to do is delete the *.bin files (boot.bin & sbl.bin) from the .tar archive before flashing to get a hard brick
Huh?
Didn't someone said removing those files us removing boot loader.
And that us recommended when you get a rom you are not sure of.
Now I am confused.
Sent from my GT-P1000 using XDA
Related
im pretty confuse of these two terms here, semi and hard bricks. for what i know semi brick is when you see the phone--->pc thingy on your phone after a flash failure. and can be resolve by a JIG or tricks to get into download mode.
but what about HARD BRICKS?? can they be resolve with a JIG or tricks? what are the symptoms of hard brick phones? is there anyone from the forum that could not enter download mode with the use of JIG or tricks?
pls answer the following. it will help me with my phone before flashing.
Hard brick is just like soft brick, but you cant go download or recovery menu, and you have to send it to shop where you bought it.
Tuhoaja said:
Hard brick is just like soft brick, but you cant go download or recovery menu, and you have to send it to shop where you bought it.
Click to expand...
Click to collapse
ah! thank you!.
can you tell me how hard brick often happens??
when in a hard brick does JIG still works to go to download mode??
scapula101 said:
ah! thank you!.
can you tell me how hard brick often happens??
when in a hard brick does JIG still works to go to download mode??
Click to expand...
Click to collapse
You cant use JIG if your phone is hard bricked.
And, well your phone bricks if you flash wrong file with odin (sometimes) or wrong .zip
IN XDA/SGS 1 bricked means phone wont boot may be described as soft brick as its probably recoverable . Only one culprit in a soft bricked phone the user has not bothered to read/follow instructions .
Recovery is usually via download mode /jig and flash a stock rom .
Hardbricked dead never ever recover nothing the user can do combination of above or blown hardware .
jje
JJEgan said:
IN XDA/SGS 1 bricked means phone wont boot may be described as soft brick as its probably recoverable . Only one culprit in a soft bricked phone the user has not bothered to read/follow instructions .
Recovery is usually via download mode /jig and flash a stock rom .
Hardbricked dead never ever recover nothing the user can do combination of above or blown hardware .
jje
Click to expand...
Click to collapse
ah. it's really to think it it up then whether to flash and custom ro like darky's or stay on samsung official firmware in kies. T_T.
do guys know if someone here in the forum ever had a HARD brick??
in case of HARD brick in which it's dead forever like you mention. what can I do or have to do??
scapula101 said:
do guys know if someone here in the forum ever had a HARD brick??
in case of HARD brick in which it's dead forever like you mention. what can I do or have to do??
Click to expand...
Click to collapse
Yup I know about 10-20 with bricked phones.
You can't do anything, just send back to Samsung and they'll fix it
guys i have a question relatad to this topic ..
what makes the diffrence beetwin semi brick and hard brick while flashing in odin ?
shedox said:
guys i have a question relatad to this topic ..
what makes the diffrence beetwin semi brick and hard brick while flashing in odin ?
Click to expand...
Click to collapse
I think its all by luck...
I've once semi bricked my sgs...
Tuhoaja said:
I think its all by luck...
I've once semi bricked my sgs...
Click to expand...
Click to collapse
really?? how? wat did you do??
shedox said:
guys i have a question relatad to this topic ..
what makes the diffrence beetwin semi brick and hard brick while flashing in odin ?
Click to expand...
Click to collapse
from the post above semi can still be recovered and hard brick cant.
scapula101 said:
do guys know if someone here in the forum ever had a HARD brick??
Click to expand...
Click to collapse
I guess the guy recently on the Q&A forum had who did a fatal mistake on flashing (see attachment).
Semi bricks seem to happen far more often but from what I read here it doesn't really matter much on the SGS. I'm way no expert but it sounds you gotta mess up big time to hard brick it or be extremely unlucky when flashing boot loaders or something (correct me if I'm wrong).
Hard bricked phones have to be sent in for repair afaik. There are also some guys trying to figure out a different kind of cable to get into some more advanced service mode or so for hard bricks (?).
Anyways, what to do when you semi brick? Usually go to download or recovery mode and flash again.
My very first flash was about enabling these modes (my SGS came without them) so I had neither mode and semi bricked (better use direct USB). Luckily, thanks to all the info on XDA I knew I'd be screwed if things go wrong so I bought myself a JIG dongle off Ebay prior and thus could plug it in, get into download mode and re-flash, all fixed.
Landorin said:
I guess the guy recently on the Q&A forum had who did a fatal mistake on flashing (see attachment).
Semi bricks seem to happen far more often but from what I read here it doesn't really matter much on the SGS. I'm way no expert but it sounds you gotta mess up big time to hard brick it or be extremely unlucky when flashing boot loaders or something (correct me if I'm wrong).
Hard bricked phones have to be sent in for repair afaik. There are also some guys trying to figure out a different kind of cable to get into some more advanced service mode or so for hard bricks (?).
Anyways, what to do when you semi brick? Usually go to download or recovery mode and flash again.
My very first flash was about enabling these modes (my SGS came without them) so I had neither mode and semi bricked (better use direct USB). Luckily, thanks to all the info on XDA I knew I'd be screwed if things go wrong so I bought myself a JIG dongle off Ebay prior and thus could plug it in, get into download mode and re-flash, all fixed.
Click to expand...
Click to collapse
HE IS MESSED up. i wonder what happened his phone?
When starting my HTC Dream it stays on the boot splash screen and does nothing. Attempting to go into the bootloader or recovery fails. This happened directly after installing DangerSPL, I believe I might have accidentally messed up when flashing its radio and not have done so at all, although I did downgrade the firmware. Is there any possible solution?
incompatible radio. Thats why its called dangerSPL.
You have bricked your phone, only way is jtag... http://forum.xda-developers.com/showthread.php?t=591048
shadowch31 said:
You have bricked your phone, only way is jtag... http://forum.xda-developers.com/showthread.php?t=591048
Click to expand...
Click to collapse
Yes, I've read of the infamous JTAG fix. I've decided that I could either pay for a fix, probably by someone here since they would probably know what they're doing, as I'm sure I'd mess up in the process since I don't have much experience with soldering small devices or even opening them up. Or if that isn't an option I might just donate it to someone who would like to mess with the bricked thing.
gralco said:
Is there any possible solution?
Click to expand...
Click to collapse
code DOT google DOT com/p/android-roms/wiki/Unbrick
(Sorry, as a new user, I can't post outside links without 8 posts first...) Hopefully no mods see this is a deliberate bypass of their "security" I assure all, I am not a spammer. Honestly trying to help here =P
This looks possible. I mean, with a bricked phone, it's worth a shot? Let me know if anything works out!
DoogleDood said:
code DOT google DOT com/p/android-roms/wiki/Unbrick
(Sorry, as a new user, I can't post outside links without 8 posts first...) Hopefully no mods see this is a deliberate bypass of their "security" I assure all, I am not a spammer. Honestly trying to help here =P
This looks possible. I mean, with a bricked phone, it's worth a shot? Let me know if anything works out!
Click to expand...
Click to collapse
... you should also read the comments of the page you are linking to .
If you have a *real* brick you are stuck at the G1 screen and all software based tricks will not work, JTAG is the only chance for you.
Just cause you have a hard bricked phone, doesn't mean all tips and tricks don't work. My friend had a bricked mytouch slide and couldn't access recovery or anything of the sort, but using my boot.img, and other essentials and adb, we could unbrick the phone. Not saying that link will work... since I hadn't realized recovery was not accesible, but I'm just pointing out that hard bricked does not mean you only have one way out, if that.
Sent from my Sapphire/Dream using XDA App
Tried to install CWM from market as Galaxy Tab 10.1. The tab is bricked, if you choose to boot into recovery you will get sutck in an endless loop of reboots. With a little effort and connecting the tab to a PC you can get back to the choice menu and enter download mode.
You have been warned!
Bec07 said:
Tried to install CWM from market as Galaxy Tab 10.1. The tab is bricked, if you choose to boot into recovery you will get sutck in an endless loop of reboots. With a little effort and connecting the tab to a PC you can get back to the choice menu and enter download mode.
You have been warned!
Click to expand...
Click to collapse
At least its only a soft brick...
Definitely good to know...sorry you went through the hassle to find out.
Thanks for sharing with us, lets hope someone can get a recovery working soon so I can be more dangerous!!!!
Sent from my GT-P7310 using xda premium
http://forum.xda-developers.com/showthread.php?t=1133590
Thanks, downloading now from: http://www.samsung-firmware.de/pxxx_62889641.html
This is the netload folder for the wi-fi version: http://netfolder.in/folder.php?folder_id=VgnYQ90 and the password: samsung-stuff.de
Samfirmware uses awful slow hosts lately.
Just got it today and I really got scared as the boot menu didn't show up anymore (the sammy logo did appear but it was followed by immediate shutdown) I was starting to think I got myself a hard brick
Got it from Amazon.fr, sorry I won't be able to share my firmware anymore...
Bec07 said:
Thanks, downloading now from: http://www.samsung-firmware.de/pxxx_62889641.html
This is the netload folder for the wi-fi version: http://netfolder.in/folder.php?folder_id=VgnYQ90 and the password: samsung-stuff.de
Samfirmware uses awful slow hosts lately.
Just got it today and I really got scared as the boot menu didn't show up anymore (the sammy logo did appear but it was followed by immediate shutdown) I was starting to think I got myself a hard brick
Got it from Amazon.fr, sorry I won't be able to share my firmware anymore...
Click to expand...
Click to collapse
Be careful. Sometimes it clears your SD card as well (depending on what exactly you're doing).
To be safe, make a backup of you SD card on your computer.
Only flashed the bootloader from that pack, seems to work!
... more or less. Trying to boot into recovery will restart the tabled, trying to do so from the CWM app will bring you back to the reboot loop...
Bec07 said:
Only flashed the bootloader from that pack, seems to work!
Click to expand...
Click to collapse
Sweet bro.
Sure wished I'd seen this message last night.....
Well, now to see if I can fix mine.
-dana
Thanks for finding this trick. I applied it but I moved from soft brick to what I thought was hard brick. Leaving it on the charger for a half hour as I took the dogs for a walk "woke the dead".
Thanks,
-dana
Amateur Geologist said:
Thanks for finding this trick. I applied it but I moved from soft brick to what I thought was hard brick. Leaving it on the charger for a half hour as I took the dogs for a walk "woke the dead".
Thanks,
-dana
Click to expand...
Click to collapse
A hard brick is when nothing shows up no matter what. Screen stays black no matter what you do, power button doesnt work, you cant get into any recovery or bootloader or anything..
I was a little iffy to install it...so glad I didn't. Had some issues with it on my GS2..pfft
i think i have bricked mine new P 7500
but there is nothing wrong i did with this device
tab is now in only conecting in APX
NVIDIA USB Boot-recovery driver for Mobile devices
no sign of charging and no light on display
is there any way to recover it back??????????
this is semi or hard bricked?????
How? this thread is meant for the 8.9 tabs...
This topic should be a sticky!
Anyway too late for me, just trying to work out what brick I have. Basically I done the above too but I'm trying to work out what type of brick I've got. I cannot see a charge light when put on charge. I can get to an option for recovery or download but can't get to recovery. I just get a bootloop of powering on as far as the samsung logo before shutting down, or at least the screen going black. I've never connected to computer yet but I think I've found the files I need should it be a soft brick. Any help in getting me through this would be appreciated.
---------- Post added at 06:15 AM ---------- Previous post was at 05:50 AM ----------
Bec07 said:
Only flashed the bootloader from that pack, seems to work!
... more or less. Trying to boot into recovery will restart the tabled, trying to do so from the CWM app will bring you back to the reboot loop...
Click to expand...
Click to collapse
Hmmm, can someone tell me a little more about this. What files exactly, from that german site? Now I'm confused. Could someone provide a link. I've got a uk unlocked sim free wifi only. And I know its a pita but some guidance on what do do with that file would be a great help
Many thanks
Dunbad said:
This topic should be a sticky!
Anyway too late for me, just trying to work out what brick I have. Basically I done the above too but I'm trying to work out what type of brick I've got. I cannot see a charge light when put on charge. I can get to an option for recovery or download but can't get to recovery. I just get a bootloop of powering on as far as the samsung logo before shutting down, or at least the screen going black. I've never connected to computer yet but I think I've found the files I need should it be a soft brick. Any help in getting me through this would be appreciated.
---------- Post added at 06:15 AM ---------- Previous post was at 05:50 AM ----------
Hmmm, can someone tell me a little more about this. What files exactly, from that german site? Now I'm confused. Could someone provide a link. I've got a uk unlocked sim free wifi only. And I know its a pita but some guidance on what do do with that file would be a great help
Many thanks
Click to expand...
Click to collapse
Trapped myself in this lobster pot too. Probably hold the record for purchase to soft brick in 10 hrs!
there is a link in second post from op which has the roms and the flashing software (Odin)eunfortunately they only had a 7310 rom when I looked. You need a 7300 rom for your phone to work. Please read as many forums as you can on this first. I ended up flashing an Asian image just to get back on my feet, then ended up flashing overcome and over clocking which works very well. Wish you luck!
same
same thing happened to me .I should of looked here before trying a backup. Used Odin to install this and its all good, and 3.2. megaupload.com/?d=0KYNVV4Z
FYI, I was stupid yesterday and allowed ROM manager to update my recovery partition (it told me there was an update available). Of course the update was for a Tab 10.1 and soft bricked my tab (it went into a boot loop). I recovered by going into download mode and using odin to flash only Tab 8.9 clockwork recovery image.
So, if anyone else bricks their tab by using an incompatible recovery, you should be able to recover back to where you were by just flashing a compatible recovery instead of using a full odin ROM.
So I think I bricked my Note by misunderstanding the lpy bug (tried to flash directly to cm9, didn't realise that was the wrong way). I don't seem to even be able to get into the bootloader though, is that a normal symptom of this emmc bug brick? Just want to make sure it really is bricked before trying to return it to Samsung. Basically holding vol down+home+power does nothing. Plugging it in to charge doesn't show the charging icon etc. Looks pretty bricked to me but perhaps I'm missing something?
Can you get into recoverymode vol-up+home+power?
nope
slightly said:
nope
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=1257434
To force your phone into Download mode !
Hey, thanks for the suggestion. It doesn't seem to detect anything unfortunately. I think it might not apply to the Galaxy Note anyway.
Welcome to superbrick club.
Your best bet is to take the Note to SSC.
Act dumb, don't tell em' about rooting, flashing and roming.
What's SSC? Samsung something something I presume but..?
Ah Service Centre
Yeah and forgot to tell, flash stock kernel before you take your phone to SSC.
You don't wanna get caught with Clockwork Recovery, do you ?
---------- Post added at 12:54 AM ---------- Previous post was at 12:52 AM ----------
Sorry, if it is stone cold dead it is not necessary and you are not able to enter download mode either.
Heh, yeah it's dead as a dodo!
Anyone know if it might be worth trying a USB jig?
If you have access to a JIG. Its allways worth a try, it wont hurt your phone more. But I dont think it will help.
Thanks. I've ordered one as they're cheap and I guess it's worth a try.
So your screen is just all black. Nothing lights up？
Sent from my GT-N7000 using XDA App
Yeah absolutely no response from holding any button combination. Tried charging and also battery pulling between trying button combinations too.
Same here. JIG didn't make any difference
:/
Figure I'll get the same but as the bug can affect different bits of memory I suppose there's a small chance.
Have you RTM'd it to Samsung?
slightly said:
Heh, yeah it's dead as a dodo!
Click to expand...
Click to collapse
Try the procedures suggested by the following threads:
ATTENTION! my way out of a MMC_CAP_ERASE brick!
http://forum.xda-developers.com/showthread.php?t=1667886
How to revive your bricked Gnote
http://forum.xda-developers.com/showthread.php?t=1661590
My device is not being recognized neither by my Computer, nor by Odin.
Yeah same here, also the phone won't even enter download mode. Thanks for the links though tknguyencsu.
Welcome. What a beautiful week after returning my black from the site. I want to upload to the different versions of android by smartflash. And here what? Instead of loading bar appeared strip of negatives. Literally. Instead he charged up, the bar was in place and was -23% Disassociate so I took the phone and batteries, and now a repeat of entertainment: nothing again, the phone died, will not turn on. No it does not refer to life. You somehow in safe mode or something? I know a little bit on that. Either way home. Even the logo lg does not blink, nothing, the phone does not respond. Help, in desperate need of help, not che went to the site again. I beg Is there any other way to fix it? Sorry for my english :crying:
Sorry man, but you should maybe buy a NOKIA 3110 again
Couldnt help myself
Ok, can you still turn it into download mode? Plug in USB cable, while you are holding the Volume UP key?
N00BY0815 said:
Sorry man, but you should maybe buy a NOKIA 3110 again
Couldnt help myself
Ok, can you still turn it into download mode? Plug in USB cable, while you are holding the Volume UP key?
Click to expand...
Click to collapse
I tried this and nothing, as the phone will not even turn on.
Off to the LG service center and better dont touch it again after you get it back... If you dont have special hardware, which costs definitly more than a repair, you cant bring it to live again.
N00BY0815 said:
Off to the LG service center and better dont touch it again after you get it back... If you dont have special hardware, which costs definitly more than a repair, you cant bring it to live again.
Click to expand...
Click to collapse
Hi N00BY0815, sorry for asking here, supposed to be contacted on PM
Actually, what problems cause the HARD BRICKING ?
Generally, I know is Erasing entire CP and loose cable while ROM installation is going on.
Literally, you helped with your (BIG NOOB HOW TO), all the noobs who are using OB..
What I meant is, prepare some instructions to avoid HARD BRICKING and create a thread for OB users.
I know XDA from CM7, but never tried. After only seeing your NOOB HOW TO, I dare to try CM10.
Tons of THANKS to you.
sekhar13515 said:
Hi N00BY0815, sorry for asking here, supposed to be contacted on PM
Actually, what problems cause the HARD BRICKING ?
Generally, I know is Erasing entire CP and loose cable while ROM installation is going on.
Literally, you helped with your (BIG NOOB HOW TO), all the noobs who are using OB..
What I meant is, prepare some instructions to avoid HARD BRICKING and create a thread for OB users.
I know XDA from CM7, but never tried. After only seeing your NOOB HOW TO, I dare to try CM10.
Tons of THANKS to you.
Click to expand...
Click to collapse
Hard Bricking is only possible with SFT when
a)you disconnect (or power failure,anything that interrupts the process) the phone during when busy with the u-boot or x-loader (you can say update gone bad and they should fix)
b)there is a previous hw problem with the phone that caused a mistake (they should fix this as your tinkering didn't cause this)
c)bad cable or usb port that caused a mistake (might refuse since it's your bad hw)
d)flashing wrong (wrong as in :firmware for phone with different bootloader) or seriously corrupt firmware. (Highly unlikely to get corrupt as it's only 512kb odd out of the whole file that needs to be ok for emergency recovery to be accessible), (they won't fix, their update tools checks validity and model before flashing)
xonar_ said:
Hard Bricking is only possible with SFT when
a)you disconnect (or power failure,anything that interrupts the process) the phone during when busy with the u-boot or x-loader (you can say update gone bad and they should fix)
b)there is a previous hw problem with the phone that caused a mistake (they should fix this as your tinkering didn't cause this)
c)bad cable or usb port that caused a mistake (might refuse since it's your bad hw)
d)flashing wrong (wrong as in :firmware for phone with different bootloader) or seriously corrupt firmware. (Highly unlikely to get corrupt as it's only 512kb odd out of the whole file that needs to be ok for emergency recovery to be accessible), (they won't fix, their update tools checks validity and model before flashing)
Click to expand...
Click to collapse
Port and cable are good because they've a thousand times podpinałem the same cable to the same port, so it's not possible that it would suddenly angry. And he heard someone plug something about the service?
sekhar13515 said:
Hi N00BY0815, sorry for asking here, supposed to be contacted on PM
Actually, what problems cause the HARD BRICKING ?
Generally, I know is Erasing entire CP and loose cable while ROM installation is going on.
Literally, you helped with your (BIG NOOB HOW TO), all the noobs who are using OB..
What I meant is, prepare some instructions to avoid HARD BRICKING and create a thread for OB users.
I know XDA from CM7, but never tried. After only seeing your NOOB HOW TO, I dare to try CM10.
Tons of THANKS to you.
Click to expand...
Click to collapse
Lol...i would have told you to ask xonar!