Related
Hi,
1. For a month ago i've learned how to root my galaxy s2, and since then i've flashed new ROM's and kernels almost every week, and thats because almost everyone told me that it was almost impossible to brick the phone.
In 2 days i will recive my new Galaxy Nexus, and i don't know if i will Root it or not, is it worth doing this to this phone?
thanks
People say it's almost impossible.. Just search the threads where people think they bricked their phones
It is EXTREMELY hard to brick the Galaxy Nexus.
And it is definitely worth rooting. There are some amazing ROMs and kernels available
Learning to root and use android from scratch, I bricked this fella at least six times, but mostly due to bad file transfers and user error.
Use a toolkit, wugfresh's makes it excessivlely easy.
Sent from my Galaxy Nexus using xda premium
I did not wipe data out before flashing, my phone could not start. I thought i bricked my phone but after went to recovery mode to wipe data, my phone worked fine.
As far as I know, the only time that you can brick this phone is when flashing bootloaders. For example, the lights go out during the 2 secs required to flash it. But the window of opportunity is so small you have to really be unlucky, and if you have UPS or do it on a laptop, that won't be a problem at all. The more probable scenario is flashing a corrupted image of the bootloader (that's what md5 checksums are for) or, god forbid, a bootloader for a completely different device (that's what intelligence is for). Besides, you shouldn't be flashing bootloaders all the time. Maybe once every time a new version of ICS comes out.
TwilightSparkle said:
I bricked this fella at least six times
Click to expand...
Click to collapse
So what you really mean, is that you didn't actually brick it once?
Lol - interesting thread...
I'll bet that I can brick one in a few minutes, so it can't be that hard... xD
I was under the impression that bricking can also occur by mismatching radios/kernels/roms, not just the wrong bootloader. Like using a 4.0.2 version of one with a 4.0.3 version of another, for instance. I want to upgrade from 4.0.2 to 0.3 or 0.4 but I'm not sure of the correct order of updating everything, since I've customized all of them. Unless I'm just mistaken altogether...
thirtynation said:
I was under the impression that bricking can also occur by mismatching radios/kernels/roms, not just the wrong bootloader. Like using a 4.0.2 version of one with a 4.0.3 version of another, for instance. I want to upgrade from 4.0.2 to 0.3 or 0.4 but I'm not sure of the correct order of updating everything, since I've customized all of them. Unless I'm just mistaken altogether...
Click to expand...
Click to collapse
No. As long as your volume button and power button are not broken, you can start into the bootloader and start over.
Bricking is a very final thing that one can not repeat on the same device. Once bricked, it's only good as a paperweight. If you can revive the device, then it was never bricked in the first place
Wrong radio will brick your device for certain. Kernel and ROM not so much...
danger-rat said:
Wrong radio will brick your device for certain. Kernel and ROM not so much...
Click to expand...
Click to collapse
I thought CWM just gives an error and doesn't complete the flash in that scenario, no..?
danger-rat said:
Wrong radio will brick your device for certain. Kernel and ROM not so much...
Click to expand...
Click to collapse
I thought I remembered reading that in some /r/android comments a few months ago. Thanks for confirming.
So since I'm on 4.0.2 running the leaked 4.0.3 radios, if I wanted to run 4.0.4 everything would you recommend just reverting back to pure stock 4.0.2 via this thread or similar method, and then going from there?
Vangelis13 said:
I thought CWM just gives an error and doesn't complete the flash in that scenario, no..?
Click to expand...
Click to collapse
Not confirmed with this phone, but typically the bootloader will do an md5 type check, but recovery doesn't. If you disable signature verification in recovery, then it's all in your hands...
j.go said:
[snip]
The more probable scenario is flashing a corrupted image of the bootloader (that's what md5 checksums are for) or, god forbid, a bootloader for a completely different device (that's what intelligence is for). Besides, you shouldn't be flashing bootloaders all the time. Maybe once every time a new version of ICS comes out.
Click to expand...
Click to collapse
Not sure if the bootloader flow is the same on the Galaxy Nexus (probably not), but on the Nexus One, the bootloader will not flash a bootloader that is not signed. Period. Unless of course there is no NAND lock (i.e., S-OFF for HTC devices).
Afaik,you have to screw up fast boot to truly brick the device. Not even messed up boot loaders will brick it. You can always go to fastboot and factory restore.
Sent from my Galaxy Nexus
psycho2097 said:
Afaik,you have to screw up fast boot to truly brick the device. Not even messed up boot loaders will brick it. You can always go to fastboot and factory restore.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Dare you to flashable radio from another phone...
danger-rat said:
Dare you to flashable radio from another phone...
Click to expand...
Click to collapse
LOL!!!!!
Sent from my Galaxy Nexus using Tapatalk
I Dare y'all to flash the 4.0.4 update on a GSM phone. ;P
Sent from my Galaxy Nexus using xda premium
Please Note: No other method listed in the GN2, GS3 forums work for this particular problem. I, as well as a few others have had this happen when flashing different ROMs. I have no idea what causes it but I do have an idea as to how to fix it. I just can't because what I need seems to be disabled in the phone.
Also, I did make a backup of my EFS and a restore does not fix this particular problem.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
Problem #3:
And probably the biggest problem: ADB does not recognize the phone. ADB debugging is enabled on the phone in Developer Options but the icon on the notification button doesn't appear. Nor does ADB recognize the phone in recovery. So therefor I cannot transfer files this way either. "nvbackup/nvrestore" can not be used because of this either.
The following methods have all been tried and have failed. Yes, I know what I am doing,
http://forum.xda-developers.com/showthread.php?t=1867442
http://forum.xda-developers.com/showthread.php?t=1852255
http://forum.gsmhosting.com/vbb/f606/tutorial-galaxy-s3-backup-restore-imei-without-root-1513909/
I fell victim to #1 the IMEI wipeout I had to take my phone back for a replacement
Sent from my SPH-L900 using xda premium
Me too. ..
Sent from my MASSIVE Galaxy Note® II...*
mackentosh said:
I fell victim to #1 the IMEI wipeout I had to take my phone back for a replacement
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
but how did it happened ? can u please explain steps what u did that wiped yr imei?
t3project said:
Please Note: No other method listed in the GN2, GS3 forums work for this particular problem. I, as well as a few others have had this happen when flashing different ROMs. I have no idea what causes it but I do have an idea as to how to fix it. I just can't because what I need seems to be disabled in the phone.
Also, I did make a backup of my EFS and a restore does not fix this particular problem.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
Problem #3:
And probably the biggest problem: ADB does not recognize the phone. ADB debugging is enabled on the phone in Developer Options but the icon on the notification button doesn't appear. Nor does ADB recognize the phone in recovery. So therefor I cannot transfer files this way either. "nvbackup/nvrestore" can not be used because of this either.
The following methods have all been tried and have failed. Yes, I know what I am doing,
http://forum.xda-developers.com/showthread.php?t=1867442
http://forum.xda-developers.com/showthread.php?t=1852255
http://forum.gsmhosting.com/vbb/f606/tutorial-galaxy-s3-backup-restore-imei-without-root-1513909/
Click to expand...
Click to collapse
i got the same problem with tmobile ver the problem is the partition i did tried to repartition in odin with gt-7100 pit file it did not work
can you see your storge and see your internal sd space
sorry for my english
An fyi when u get ur baseband back 3g will not work. I was able to get mine all back and working but I was always on 1x. T3 hit me up in gtalk.
Sent from my SPH-L900 using Tapatalk 2
gotojanoo said:
but how did it happened ? can u please explain steps what u did that wiped yr imei?
Click to expand...
Click to collapse
Well I was testing a rom for someone, I wont tell which rom but he said it was the "in call recorder" he added. He's got it fixed now but it did wipe everything. I managed to restore it back to stock with no root but it bricked after that. Now I see why carriers dont like to unlock bootloaders cause of people bricking their phone and taking them back
Sent from my SPH-L900 using xda premium
t3project said:
Please Note: No other method listed in the GN2, GS3 forums work for this particular problem. I, as well as a few others have had this happen when flashing different ROMs. I have no idea what causes it but I do have an idea as to how to fix it. I just can't because what I need seems to be disabled in the phone.
Also, I did make a backup of my EFS and a restore does not fix this particular problem.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
Problem #3:
And probably the biggest problem: ADB does not recognize the phone. ADB debugging is enabled on the phone in Developer Options but the icon on the notification button doesn't appear. Nor does ADB recognize the phone in recovery. So therefor I cannot transfer files this way either. "nvbackup/nvrestore" can not be used because of this either.
The following methods have all been tried and have failed. Yes, I know what I am doing,
http://forum.xda-developers.com/showthread.php?t=1867442
http://forum.xda-developers.com/showthread.php?t=1852255
http://forum.gsmhosting.com/vbb/f606/tutorial-galaxy-s3-backup-restore-imei-without-root-1513909/
Click to expand...
Click to collapse
You care to clarify which ROM you flashed in particular caused this to happen so that we don't replicate your problem? I want to assume it's your own ROM but just want to make sure.
mackentosh said:
Well I was testing a rom for someone, I wont tell which rom but he said it was the "in call recorder" he added. He's got it fixed now but it did wipe everything. I managed to restore it back to stock with no root but it bricked after that. Now I see why carriers dont like to unlock bootloaders cause of people bricking their phone and taking them back
Click to expand...
Click to collapse
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
ffolkes said:
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
Click to expand...
Click to collapse
i did flash the s3 rom and after that i lost everythng my phone i need to know how to restor the orgenal sd card cuz im looking with rootexplore it sdcard0
when i go to setting storge it only show 266mb used and 0.00 avilabel any body can help please
mackentosh said:
Well I was testing a rom for someone, I wont tell which rom but he said it was the "in call recorder" he added. He's got it fixed now but it did wipe everything. I managed to restore it back to stock with no root but it bricked after that. Now I see why carriers dont like to unlock bootloaders cause of people bricking their phone and taking them back
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Which ROM had the "In Call Recorder"? I've been looking for a replacement to that functionality after dropping HTC/ Qualcomm with the 2WCR patch on the kernel. ..
Sent from my SPH-L900 using xda app-developers app
You cant flash a s3 rom the partitions are different. Even the partitions forbthe international note 2. Tmo. Att. Verizon and sprint note 2 are different.
Try flashing the stock tar from sex tape or viper boy. This should fix those issues. Then update the phones prl. Profile. Software. And firmware. And see if u have 3g and everything else.
Then start over.
Sent from my SPH-L900 using Tapatalk 2
ffolkes said:
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
Click to expand...
Click to collapse
it wasnt a rogue rom. it was two seperate private roms that were never released to the public
there is a very simple fix to this, i've fixed 2 phones this morning already with it. i'll post it up in a few
gotojanoo said:
but how did it happened ? can u please explain steps what u did that wiped yr imei?
Click to expand...
Click to collapse
it didnt actually wipe our imei. it repartitioned the phone.
t3project said:
it wasnt a rogue rom. it was two seperate private roms that were never released to the public
there is a very simple fix to this, i've fixed 2 phones this morning already with it. i'll post it up in a few
Click to expand...
Click to collapse
Good to know it wasn't released here publicly. Happy to hear you found a solution to the problem too.
dc13 said:
You cant flash a s3 rom the partitions are different. Even the partitions forbthe international note 2. Tmo. Att. Verizon and sprint note 2 are different.
Try flashing the stock tar from sex tape or viper boy. This should fix those issues. Then update the phones prl. Profile. Software. And firmware. And see if u have 3g and everything else.
Then start over.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Try this.
ffolkes said:
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
Click to expand...
Click to collapse
I said I was testing a rom which means I was the only person he released it to at the time. I dont want to reveal the rom or the dev because I dont want any negativity towards him he's a great dev and your probably running his rom right now. So dont worry there isnt a rogue rom floating around
Sent from my SPH-L900 using xda premium
t3project said:
it wasnt a rogue rom. It was two seperate private roms that were never released to the public
there is a very simple fix to this, i've fixed 2 phones this morning already with it. I'll post it up in a few
Click to expand...
Click to collapse
whats the fix cuz im going thru this problem right now ...i cant get any service (radios)
EDIT: NVM I JUST FLASHED TO STOCK RECOVERY THEN FLASHED STOCK LJ1 THRU ODIN AND ALL IS WELL NOW
mccurt29 said:
whats the fix cuz im going thru this problem right now ...i cant get any service (radios)
EDIT: NVM I JUST FLASHED TO STOCK RECOVERY THEN FLASHED STOCK LJ1 THRU ODIN AND ALL IS WELL NOW
Click to expand...
Click to collapse
simple, wasnt it? lol..................
mackentosh said:
I said I was testing a rom which means I was the only person he released it to at the time. I dont want to reveal the rom or the dev because I dont want any negativity towards him he's a great dev and your probably running his rom right now. So dont worry there isnt a rogue rom floating around
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Was it mine? I can tell you that if any of the previous stuff happened to you, it wasn't from the ROM. Could have been a bad download, coinsidence, etc. The ROM flash wouldn't have caused it.
Sent from my SPH-L900 using Tapatalk 2
I wrote this request in another thread and I think hasn't been read by many people, so I opened a specific thread.
Our phone may remain stucked for several reasons in a QLOAD 9008 device state, or similar device (easily verifiable even with Windows). It's better to test a solution very simple and useful for all.
To do this is required to extract some files residing in an area of the phone's memory and only a working phone can be used to extract a dump of this files following how explained in this thread:
http://forum.xda-developers.com/showthread.php?t=2136738
Don't think an hardbrick can't happens to you, it may happens and without a tested solution your phone may become a paperweight. Alas my phone is bricked (!), I cannot extract any file from it, I can only try to repair the phone but I need this files to test this method. I invite anyone who has care of his phone to read the topic linked above and try to extract the files needed to repair the phone locked in QDLOAD mode (05c6:9008), we have only this way to unbrick the hardbricked phone for free (if the phone warranty is expired or invalid).
I thank anyone (uhm... mr. Arco68?...) who gives a hand to solve the "Qload 9008 mode" brick problem with this method!
I hope that someone will help you.
I've read the thread, and I'm willing to help... but what exactly I have to do?
Honestly, I can't make any sense of the thread...
Sent from my GT-I8150 using xda app-developers app
yep,,,, and i thought so too,,,,,
even arco himself mentioned he had two hard bricks,,, i dont think,, he just returned it to sammy for warranty use.. i think he had that unbricker you're mentioning..
R: Help to repair the phone stucked on Qload state
santiagoruel13 said:
yep,,,, and i thought so too,,,,,
even arco himself mentioned he had two hard bricks,,, i dont think,, he just returned it to sammy for warranty use.. i think he had that unbricker you're mentioning..
Click to expand...
Click to collapse
Why don't give a try?
Inviato dal mio GT-I8150 con Tapatalk 2
Today, or as soon as possible, I'll try to make backups of the bootloader, partition table and a .pit from an i9100. If I cannot do that, as soon as possible I will try with a i9001 that has hardware very similar to the i8150. I hope I can do it, so I will explain here how to do it step by step to allow other users do the same more easily. Stay tuned!
orsonbear said:
Today, or as soon as possible, I'll try to make backups of the bootloader, partition table and a .pit from an i9100. If I cannot do that, as soon as possible I will try with a i9001 that has hardware very similar to the i8150. I hope I can do it, so I will explain here how to do it step by step to allow other users do the same more easily. Stay tuned!
Click to expand...
Click to collapse
Will a dd dump be enough?
Sent from my GT-I8150 using xda app-developers app
pepoluan said:
Will a dd dump be enough?
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
I don't think, because i think isn't compatible with the tool...
I used heimdall to flash stock rom (extracted the varios bin and img files from N7100XXDMB2_N7100OXEDMC2_SER), and missed out sboot and recovery. Once it finished, I tried restarting the phone -> and it wouldn't do anything. Now I cant enter the download mode.
I tried a home-made USB JIG (300k ohms b/w pin 4 (the left out pin) and pin 5 (ground)), and it wouldn't kick the download mode either (does nothing).
I am seriously stuck and have no clue on what to do. If it helps, when I try to boot (with any combination of keys), the indicator (left) blinks red once.
Begging for help right now... Please tell me what to do. I love my phone, and I have a decent understanding of Computers/Electronics - so it's okay if you go all technical
More Info:
Extra Info: Verified that the USB JIG is doing the same thing, i.e after 3 seconds or so, the indicator blinks red... (and so on after every 5 seconds in a loop thereafter).
Good chance of SDS
You have messed up bootloader so won't get download mode
But if you have heimdall and some techy here is guide to flash bootloader blindly, if you succeed to flash it, you will get download mode and subsequently use odin to flash stock rom
http://forum.xda-developers.com/showthread.php?t=1220181
Goodluck!
Sent from my GT-N7100 using xda premium
You need jtag. This is not sds issue.
You will need jtag to flash back bootloader.
Sent from my GT-N7100 using xda premium
dr.ketan said:
You have messed up bootloader so won't get download mode
But if you have heimdall and some techy here is guide to flash bootloader blindly, if you succeed to flash it, you will get download mode and subsequently use odin to flash stock rom
http://forum.xda-developers.com/showthread.php?t=1220181
Goodluck!
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I am going to try this... Looks like I will need a lot of good luck for this to actually work..
UtkarshGupta said:
You need jtag. This is not sds issue.
You will need jtag to flash back bootloader.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I have never actually used jtag to debug anything! Is it worth buying one just for this purpose? Also, I'm not able to find any wiki on how to use jtag specially to download a particular bootloader (Learning JTAG and its usage as a whole seems very tedious)...
cheenu_sri said:
I am going to try this... Looks like I will need a lot of good luck for this to actually work..
Click to expand...
Click to collapse
No luck
cheenu_sri said:
I have never actually used jtag to debug anything! Is it worth buying one just for this purpose? Also, I'm not able to find any wiki on how to use jtag specially to download a particular bootloader (Learning JTAG and its usage as a whole seems very tedious)...
Click to expand...
Click to collapse
You have to attach the wires directly to the nand or internal memory chip or whatever it is(could be memory controller if there is any). Then you have to connect it to a box? I don't know much about it. You can check on the internet. You have to flash sboot.bin I guess
Sent from my GT-N7100 using xda premium
Off-topic
On a side note (not sure if I am violating forum policies), I am still within warranty period - is there a way Samsung can pinpoint what caused this? Or can I still get it repaired with some generic reasons?
cheenu_sri said:
On a side note (not sure if I am violating forum policies), I am still within warranty period - is there a way Samsung can pinpoint what caused this? Or can I still get it repaired with some generic reasons?
Click to expand...
Click to collapse
Well if it were sds or it's symptoms then yeah.
But you could try maybe they would just consider it sds or something else.
And don't worry. Talking about Samsung isn't against the forum rules
Sent from my GT-N7100 using xda premium
Best answer if samsung guys ask you, tell them it was happened when I got OTA and after getting update device never started, there are cases reported bootloader can't update while on ota and device fail to boot further.
Just don't show them you are technically sound, and behave like noob, they will install it with jtag.
Sent from my GT-N7100 using xda premium
Thanks for the suggestions!
dr.ketan said:
Best answer if samsung guys ask you, tell them it was happened when I got OTA and after getting update device never started, there are cases reported bootloader can't update while on ota and device fail to boot further.
Just don't show them you are technically sound, and behave like noob, they will install it with jtag.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
UtkarshGupta said:
Well if it were sds or it's symptoms then yeah.
But you could try maybe they would just consider it sds or something else.
And don't worry. Talking about Samsung isn't against the forum rules
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Thanks for those suggestions I will try my luck at this tomorrow. Looks like whether I get it repaired free or not, I can't use my phone for a couple of weeks
Thanks again guys! Really appreciate it!
If it is just sw issue, you will get back in few hrs,(basically it takes same time like we flashing with odin, few minutes) and under warranty you should get it free.
Sent from my GT-N7100 using xda premium
UtkarshGupta said:
You have to attach the wires directly to the nand or internal memory chip or whatever it is(could be memory controller if there is any). Then you have to connect it to a box? I don't know much about it. You can check on the internet. You have to flash sboot.bin I guess
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
n7100 can do JTAG? with JTAG box can fix n7100?
Depends on your service centre. Last time I messed up and I was lucky enough to get the motherboard free of cost under warranty. Anyways good luck
Sent from my GT-N7100 using Tapatalk 2
mps5566 said:
n7100 can do JTAG? with JTAG box can fix n7100?
Click to expand...
Click to collapse
Hi
Many of new exynos model have a predisabled jtag access by samsung...so,not supported by all jtag-box..
But .i can repair hard bricked N7100 Without Jtag...Plz see : http://forum.gsmhosting.com/vbb/9306319-post324.html
This is my post about i9300,...but i can do it for N7100 too
Hi guys
i want to root and install custom roms on my note 2 . i just want to know what are the most common problem comes that make your phone completely dead!
is it even possible that one can kill his phone completely that it can never be recovered?
Bumping the thread
why no one answers?
nicholes said:
Hi guys
i want to root and install custom roms on my note 2 . i just want to know what are the most common problem comes that make your phone completely dead!
is it even possible that one can kill his phone completely that it can never be recovered?
Click to expand...
Click to collapse
If you flashed wrong custom ROM via recovery won't be a problem, just reflash any other compatible stock ROM then your problem will be fixed. BUT if you flashed wrong stock ROM via ODIN and you will end up brick. You need a JTAG to revive your phone.
Its pretty hard to destroy your phone completely just by flashing another rom.
Flashing bootloader through recovery is a bad idea.
Repartitioning your device in odin, with files not specific to your device, is a bad idea
Dramatic over-clocking with increased voltages, can be a bad idea
Dropping your device is a bad idea.
Bumping a thread without waiting more than 24 hours, is a bad idea
EmptyArea said:
Flashing bootloader through recovery is a bad idea.
Repartitioning your device in odin, with files not specific to your device, is a bad idea
Dramatic over-clocking with increased voltages, can be a bad idea
Dropping your device is a bad idea.
Bumping a thread without waiting more than 24 hours, is a bad idea
Click to expand...
Click to collapse
i understood sir:good:
soralz said:
If you flashed wrong custom ROM via recovery won't be a problem, just reflash any other compatible stock ROM then your problem will be fixed. BUT if you flashed wrong stock ROM via ODIN and you will end up brick. You need a JTAG to revive your phone.
Click to expand...
Click to collapse
and what is JTAG here?please explain
nicholes said:
i understood sir:good:
and what is JTAG here?please explain
Click to expand...
Click to collapse
JTAG = Joint Test Action Group.
http://en.m.wikipedia.org/wiki/Joint_Test_Action_Group
Sent from my GT-N7100 using XDA Premium 4 mobile app