Related
Is bricking your device easy to happen? I'm scared of bricking my phone. Can the phone still brick when you do everything correctly?
Anything is possible.
I took chances on all my phones and never had a problem .
sent from the Dark §¡3€
MarsHD2 said:
Is bricking your device easy to happen? I'm scared of bricking my phone. Can the phone still brick when you do everything correctly?
Click to expand...
Click to collapse
If you do everything correctly, most likely not. A lot of bricks occurs because of user error. Flashing the wrong Galaxy s2 ROM/recovery etc, on our devices... there are a total of 5 variants i think.. only two works with ours.. skyrocket and hercules (i727 and t989)
I haven't heard of any bricks that occurs for doing everything correctly.
I have read up on some rare cases where a phone just blacks out from normal use... from heating up... or just random stuff.. some of the users aren't even rooted. That is purely the fault of the hardware simply giving up.
It is very easy to Root our phone:
ODIN
Flash Recovery
Flash ROM or Superuser
you can even mess up on flashing the recovery but you can actually recover from it. You will get the message where it says "firmware update failed, please connect to kies and recover," this is easily recoverable.. You just go back to ODIN Mode and flash recovery again.
The only way you can BRICK the phone:
1. Flash a ROM that doesn't belong to our device.
2. Mess up on Flashing a Stock ROM (user fault) such as battery falling out.. battery dying.. cable falls out. cable is loose etc.. while in the middle of flashing.
I remember reading that people tried to flash a Modem that didn't belong to our device, but ODIN either prevented this from happening or you get the "firmware update failed..." message.
TL;DR: No it is fairly safe and the only chances of bricking is when flashing something that isn't for our phone.
1. Flash a ROM that doesn't belong to our device.
2. Mess up on Flashing a Stock ROM (user fault) such as battery falling out.. battery dying.. cable falls out. cable is loose etc.. while in the middle of flashing.
Click to expand...
Click to collapse
I still don't see how those two things can mess up the phone? Can't you just use odin to reflash? You would think that they make the download portion of the phone non-writable so you can always use it with odin to reflash in any state. I must be missing something here. Does flashing a ROM mess with the "Download" partition also?
It is normally unwritable to prevent such problems. By using odin, you are bypassing the safety feature of the ROM area. By interrupting the process mid-way, you might not do not copy over all the 'necessary' files for the phone to function at it's lowest levels of operation. IE turn on when you tell it to. Flashing a rom doesn't mess with the user accessible partition.
Is using ClockWorkMod to flash any safer?
Catch-22.
If you want to use the ClockWorkMod app to flash, you will need to grant it superuser permissions. How do you get superuser? You need to be rooted by installing ClockWorkMod.. odin is pretty safe. Make sure to have a half-way charged battery (at least), and click the pda button.
True but how about subsequent flashes
Look bro its hard to brick these samsung but its not impossible trust me i know from experience, my first ever phone i rooted and played with was the galaxy s 4g and lets just say i bricked the **** out of it. think of it like this you flash a rom for a phone that is not yours this phone has a physical keyboard and the only way that phone can get into download mode is a combination of keys on the keyboard (this is just hypothetical) and the only way to get odin to recognize device is to be in DL mode...How can you be in DL with a phone that doesnt have physical keyboard but requires use of it to get into DL mode.
I've never bricked. Been in a bootloop, but just had to wipe and flash again
Sent from my SGH-T989 using xda premium
jdubb1106 said:
Look bro its hard to brick these samsung but its not impossible trust me i know from experience, my first ever phone i rooted and played with was the galaxy s 4g and lets just say i bricked the **** out of it. think of it like this you flash a rom for a phone that is not yours this phone has a physical keyboard and the only way that phone can get into download mode is a combination of keys on the keyboard (this is just hypothetical) and the only way to get odin to recognize device is to be in DL mode...How can you be in DL with a phone that doesnt have physical keyboard but requires use of it to get into DL mode.
Click to expand...
Click to collapse
Get a jig?
Sent from my SGH-T989 using XDA App
jig didnt work on my sgs4g. And all that example was purely hypothetical, just using as example so op understands what people are trying to say.
Sent from my SGH-T989 using xda premium
jordanishere said:
Get a jig?
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
I tried to flash a kernel and a rom for the i9100 on mine using cwm. Flash went through just fine, went to reboot.... Nuthin. Not even a jig brought it back. Just be sure of what you're flashing and you'll be good. I've been flashing roms since the razr v3, and this is my first brick.
Sent from my Nexus One using Tapatalk
zak rabbit said:
I tried to flash a kernel and a rom for the i9100 on mine using cwm. Flash went through just fine, went to reboot.... Nuthin. Not even a jig brought it back. Just be sure of what you're flashing and you'll be good. I've been flashing roms since the razr v3, and this is my first brick.
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
Its tough with all the diff varients. doesnt help that they all have the exact same name too.
Props for not being one of the whiners who blames their brick on xda. hope you get a new t989.
Sent from my SGH-T989 using XDA App
Just to throw this in there - if your phone does ANYTHING when you try to turn it on (soft keys light up/some sort of response from the screen), or plug it in, it is a soft brick in which you should be able to recover the phone. Many times it takes multiple tries (due to picky button combos) but it will come back. Coming from the Vibrant 3g, I can tell you from experience that you know when you have a hard brick because the phone does not respond AT ALL. It doesn't do anything when it's plugged in or when buttons are pressed. The ONLY time I've legitimately bricked a sgs was when I flashed a rom on a low battery not knowing that the phone does not charge in recovery. The battery died during reboot and the phone would not respond to anything. This is a true hard brick.
Also i'm not sure if this has been said but I would never flash anything without art least 50% battery life
The galaxy is pretty cool because of how easy it is to unbrick. All you have to do it load the stock kernel from Odin and plug up the USB, mount the sd, and place the ROM onto the sd and unmount then flash it. In the case that you install a bad ROM, if it's just the kernel then just load the stock kernel with Odin then use the one you want.
Sent from my SGH-T989 using xda premium
iwasblown said:
The galaxy is pretty cool because of how easy it is to unbrick. All you have to do it load the stock kernel from Odin and plug up the USB, mount the sd, and place the ROM onto the sd and unmount then flash it. In the case that you install a bad ROM, if it's just the kernel then just load the stock kernel with Odin then use the one you want.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
that was very confusing, but I'm not sure if you really know what a true hard brick is, which is really hard to unbrick and need to do the jtag stuff.
what you addressed is a softbrick (i don't even consider this a brick because the phone turns on), which is flashing an incomplete rom or kernel that is for our device, however if it was another device's than it might lead to a hardbrick.
Teo032 said:
that was very confusing, but I'm not sure if you really know what a true hard brick is, which is really hard to unbrick and need to do the jtag stuff.
Click to expand...
Click to collapse
A true hard brick cannot be unbricked. With a true hard brick the phone won't turn on and therefore, you cannot use Odin. Jtag also won't work if the phone does not turn on/the hardware buttons don't work.
From bricking this pos I have learned a lot of what to do and what not to do. I am pretty sure but need to know for certain...is there a fix for this?
Like many others I tried to install cwm recovery from android terminal emulator and sounds like I either put the image in the wrong spot or tried to install over something important. Odin doesnt work on this phone and rom manager just kept giving me the messaging has stopped working error, I soft bricked once before this but was able to flash and fix. I installed cwm recovery from rom manager I thought but was not able to boot in recovery. Ive read tons of posts and tried all the little tricks. No download mode, never could boot in recovery, had to install the qhsusb_dload drivers and now when connected to pc its a 50/50 chance of either good connect sound or bad connect sound...either way the phone doesnt power on at all. Can someone help me or should I sell this to someone who can make use of it? I have flashed and rooted many phones in the past and used to come here regularly, this has always been the BEST site for answers and help so Im really hoping you tech devs can pull through for me on this one. Any help is appreciated!
What do you mean ROM manager stops working if your phone is hard bricked.
I'm not surprised Odin doesn't work I thought that was for Samsung phones but I've never used it.
Anyways I understand you think you might have used the adb shell and copied the cwm recovery to the wrong partition do you remember which it could have been?
boot.img at mmcblk0p8
recovery.img at mmcblk0p13
firmware.img at mmcblk0p1
baseband.img at mmcblk0p14
system.img at mmcblk0p27
Also I'm sure its been said but make sure you have a decent charge leave it plugged into the wall for at least an hour without trying anything.
I just am curious you don't see lg logo? battery animation? anything?
Sent from my LG-P930 using xda app-developers app
thanks for replying. i have tried switching batteries, waited overnight, tried everything i could find on here and no power no logo no start up whatsoever. i was getting so desperate to get cwm recovery to work that i probably followed directions i shouldnt have. i followed a youtube vid and typed the following into the terminal;
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6 bs=4096
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6 bs=4096
after this i powered off the phone and it never came back to life since. the problem with rom manager was it wouldnt update cwm recovery, even though i just installed it the night before, the next day there was a new update it said. every time i tried to install a rom from rom manager it force closed and said messaging has stopped working. (what messaging had to do with it i dont know) when i plugged in my phone to pc it said couldnt find qhsusb_dload drivers so i installed them and now my phone doesnt show up on my pc. i read somewhere to try lgtools but that comes with its own problems like smartcard driver errors. i hope this is enough info thanks
msincorporated said:
thanks for replying. i have tried switching batteries, waited overnight, tried everything i could find on here and no power no logo no start up whatsoever. i was getting so desperate to get cwm recovery to work that i probably followed directions i shouldnt have. i followed a youtube vid and typed the following into the terminal;
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6 bs=4096
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6 bs=4096
after this i powered off the phone and it never came back to life since. the problem with rom manager was it wouldnt update cwm recovery, even though i just installed it the night before, the next day there was a new update it said. every time i tried to install a rom from rom manager it force closed and said messaging has stopped working. (what messaging had to do with it i dont know) when i plugged in my phone to pc it said couldnt find qhsusb_dload drivers so i installed them and now my phone doesnt show up on my pc. i read somewhere to try lgtools but that comes with its own problems like smartcard driver errors. i hope this is enough info thanks
Click to expand...
Click to collapse
When you ran the command "dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096": you broke your phone.
Those instructions must have either been completely wrong or instructions for another phone.
Basically you installed the recovery right between boot and firmware thus bricking your phone. You can buy tools to fix it bit that costs big $$$
Sorry for the bad news. I've been trying to find out if this phone has UART capabilities. I'll post it here if I find anything useful
Sent from my LG-P930 using xda app-developers app
thanks, the news is no surprise as i have been reading other posts that say the same thing. its too bad i paid $700 for this brand new over a year ago...thats a pricey brick. hopefully someone will be able to fix it as i am not willing to spend too much more on tools to fix it i will just sell it for parts or something. thanks for taking the time to look into this for me and let this be a lesson to all you other noobs who want to make the nitro better. DO NOT FOLLOW MY LEAD
Maverick.Marq said:
When you ran the command "dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096": you broke your phone.
Those instructions must have either been completely wrong or instructions for another phone.
Basically you installed the recovery right between boot and firmware thus bricking your phone. You can buy tools to fix it bit that costs big $$$
Sorry for the bad news. I've been trying to find out if this phone has UART capabilities. I'll post it here if I find anything useful
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Never seen a phone technically hard bricked so I ask how installing the recovery between the boot and firmware would prevent from accessing Download mode? Logic would tell me, which can be wrong , that Download Mode comes before either of those thus no matter where he flashed recovery, download mode is still accessible. Please explain. Thanks in advance.
EDIT: From what I just read, dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096 makes a backup for the NitroHD before flashing the recovery. Found here. And, according to the article, the other command he ran was the recovery flash w/ the second command he used as a repeat, or excess.
after reading the above i noticed this is where i might have gone wrong.
[ NOTE: If you inadvertently copied "recovery.img" to the external or removable SD card, replace "/sdcard/" in the command above with "/sdcard/_ExternalSD/"
i didnt see this command in the first place but i did copy the recovery.img right to the removable sd card. im guessing the mistake i made is irreversible.
http://forum.xda-developers.com/showthread.php?t=1939436
Apprently this person had the same problem as you. Many told that person it was hard bricked which is just strange to me b/c I've never seen a totally bricked phone, but apparently this is my first.
im being told its hard bricked but fingers crossed that im wrong. ive bricked many phones but always been able to fix them, this is my first possible HARD BRICKED device. when someone says they havent seen an actual hard bricked phone that kind of gives me a little hope.
msincorporated said:
im being told its hard bricked but fingers crossed that im wrong. ive bricked many phones but always been able to fix them, this is my first possible HARD BRICKED device. when someone says they havent seen an actual hard bricked phone that kind of gives me a little hope.
Click to expand...
Click to collapse
That's the same boat I'm in. I've had 4 phones and fudged all of them to the point I thought I was bricked but could ALWAYS get download mode and flash stock firmware. I'm thinking you wrote over download mode thus not being able to access it and killing the phone. That's the only explanation I can come up with. Patiently waiting for maverick.marq to explain b/c I'm cursed w/ the having to know the how-to-the-why.
Just to be clear, you're trying to get to download mode by holding the vol UP button and plugging in to PC w/ phone off, right?
I'm assuming that all of the first sector p1 to p8 must be intact for download to work and since he wrote his recovery to p6 I assume it took out both firmware and recovery as (again a lot of assuming) the processor says OK look for firmware in block p1 doesn't find a complete image and it and then fails to boot.
Sent from my LG-P930 using xda app-developers app
i have held vol up, vol down, power, home, etc ive tried all the buttons. its my only phone so i will not give up easily i will continue to try all options until i either fix or replace it. this would have not happened if i could have only gotten the cwm recovery to flash properly the first time. i dont know why rom manager kept force closing and giving me the messaging error. i tried rom toolbox and it too gave me the same error. i soft bricked it and ended up getting stuck on the logo with security error but that was an easy fix. this is the only phone ive had a problem flashing, but this is a good learning experience. if i get it back up and running im not even going to try to mess with it after that.
msincorporated said:
i have held vol up, vol down, power, home, etc ive tried all the buttons. its my only phone so i will not give up easily i will continue to try all options until i either fix or replace it. this would have not happened if i could have only gotten the cwm recovery to flash properly the first time. i dont know why rom manager kept force closing and giving me the messaging error. i tried rom toolbox and it too gave me the same error. i soft bricked it and ended up getting stuck on the logo with security error but that was an easy fix. this is the only phone ive had a problem flashing, but this is a good learning experience. if i get it back up and running im not even going to try to mess with it after that.
Click to expand...
Click to collapse
Well, best of luck b/c it doesn't look promising from all I've read on this similar issue. :/
Send it to LG. I had this same problem a while ago and sent it to them and they fixed it no charge, no questions asked.
Sent from my SAMSUNG-SGH-I747 using xda premium
rani9990 said:
Send it to LG. I had this same problem a while ago and sent it to them and they fixed it no charge, no questions asked.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
thanks this was something i was curious about, i am going to contact them monday about it
mmcblk0p6 is the secondary bootloader. The idea is if you mess up your primary bootloader, you'll still be able to access download mode since it uses its own separate bootloader. By overwriting the secondary bootloader, you're making it impossible to use download mode.
msincorporated said:
i have held vol up, vol down, power, home, etc ive tried all the buttons. its my only phone so i will not give up easily i will continue to try all options until i either fix or replace it. this would have not happened if i could have only gotten the cwm recovery to flash properly the first time. i dont know why rom manager kept force closing and giving me the messaging error. i tried rom toolbox and it too gave me the same error. i soft bricked it and ended up getting stuck on the logo with security error but that was an easy fix. this is the only phone ive had a problem flashing, but this is a good learning experience. if i get it back up and running im not even going to try to mess with it after that.
Click to expand...
Click to collapse
how did you get the security error fixed?.....im stuck and cant access the recovery or download mode...
Did u try flashing the stock kdz back on to it? Can u access download mode? Not recovery I am talking about the download mode. And yeah this phone is a pos when it comes to battery I am using a fat 3800 may battery and when I get lucky it maybe last 14 hours. This phone has so bad battery consumption. No matter what ROM I use.
Sent from my LG-P930 using XDA Free mobile app
Hey folks,
I was trying to flash a custom kernel (Phenomenal Extreme 4.0) from Clockworkmod on a rooted stock 4.1.2 rom and kernel. I placed the zips on my sd card, then flashed, but it was unsuccessful. Then, when I rebooted from CWM's main menu, the phone went dead. Nothing worked, no buttons, no nothing. Any combination I tried failed, from a simple reboot, to reboot into recovery, to a reboot into download mode. Took battery out, and placed it back in, still nothing.
I'd appreciate any help you can give me! If there's anything like a factory cable, that is still better than nothing. I think I bricked it, and no warranty (Samsung's 3 month is quite short). When I plug the phone in, the laptop responds with a sound but it's not the usual sound when you dock the device. A balloon says that device driver installation failed. Then nothing happens. In any case, I rooted it and there's a flash counter of 1 on it, even if I'm running stock everything. Again, I appreciate any help!
seokhun said:
Hey folks,
I was trying to flash a custom kernel (Phenomenal Extreme 4.0) from Clockworkmod on a rooted stock 4.1.2 rom and kernel. I placed the zips on my sd card, then flashed, but it was unsuccessful. Then, when I rebooted from CWM's main menu, the phone went dead. Nothing worked, no buttons, no nothing. Any combination I tried failed, from a simple reboot, to reboot into recovery, to a reboot into download mode. Took battery out, and placed it back in, still nothing.
I'd appreciate any help you can give me! If there's anything like a factory cable, that is still better than nothing. I think I bricked it, and no warranty (Samsung's 3 month is quite short). When I plug the phone in, the laptop responds with a sound but it's not the usual sound when you dock the device. A balloon says that device driver installation failed. Then nothing happens. In any case, I rooted it and there's a flash counter of 1 on it, even if I'm running stock everything. Again, I appreciate any help!
Click to expand...
Click to collapse
What forum did you find that kernel? Hopefully it was made for d2tmo.
+Bound for Valhalla!
I just checked, it wasn't. It's actually made for the international version -- my fault. Oh crap, I'm totally screwed, aren't I? *rolling eyes and a long sigh*
http://forum.xda-developers.com/showthread.php?t=1917234 My question is, it failed regardless, and why would it die AFTER I reboot the phone? It should've died right when I tried to install it through CWM.
seokhun said:
I just checked, it wasn't. It's actually made for the international version -- my fault. Oh crap, I'm totally screwed, aren't I? *rolling eyes and a long sigh*
http://forum.xda-developers.com/showthread.php?t=1917234 My question is, it failed regardless, and why would it die AFTER I reboot the phone? It should've died right when I tried to install it through CWM.
Click to expand...
Click to collapse
Google jtag repair.
That's an expensive paper weight.
|When Emotion Goes Up, Logic Goes Down|
I made a Nandroid before messing around.
Once I do the JTAG repair, can I restore using that Nandroid after re-rooting and flashing CWM? The guy who will be doing the JTAG said that it's dangerous because there's a risk of bricking involved.
I would just restore things individually, personally. I don't know what you had on there, but is there anything that you can't restore some other way ?
That happened to me when i flash wromg kernel. And I had a panic attack...but I somehow manage to go into recovery mod....if you can go into recovery mod...have no fear back up is there lol
Just wipe everything and restore your backup.
Sent from my SGH-T999 using xda premium
Send it back
Sent from my SGH-T999 using xda premium
seshaz said:
Send it back
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Hopefully you can get odin to recognise it...
tdotdot said:
Hopefully you can get odin to recognise it...
Click to expand...
Click to collapse
I had the same problem when I first got my S3. I flashed a file that was for my S2 not realizing and the phone responded the same way or didnt respond at all. Im not saying this will work but you can try. Do the proper button combo to get into download. It wont show anything on your scrren but the phone could still be in download mode. Go ahead and try connecting it to your computer and see if odin will recognize it. Make sure you have your drivers installed and dont forget to push volume up to get all the way into download mode. It worked for me once before and I hope to never have to try it again. If you have already tried this then your out of luck and will have to jtag.
JTAG is no scam. It is a VERY reliable source! Go for it.
Sent from my Galaxy Nexus using xda premium
Never mind, warranty exchange. I don't want to send my phone to strangers, even if it's legitimate. Still $45-$60 on the credit card.
I have a question though, as long as the phone is under warranty, I can exchange for a replacement an unlimited number of times, right?
Warranty Exchange!
seokhun said:
Never mind, warranty exchange. I don't want to send my phone to strangers, even if it's legitimate. Still $45-$60 on the credit card.
I have a question though, as long as the phone is under warranty, I can exchange for a replacement an unlimited number of times, right?
Click to expand...
Click to collapse
Yes you can...I did it with my S2 until I got one that did'nt have any signs of being refurbished. It looked brand new! I have even told them that something was wrong with the phone (hardware issue) when there was nothing wrong just because the one year warranty was about to run out and it had a few cosmedic blemishes..I have given them a lot of money in the past 9 years so I do'nt feel too bad... I did it with my Vibrant as well.
I downloaded the Jedi Mind Trick JB 2 ROM and installed it via clocwork mod recovery .. That went fine but it took me a few days to realize I didnt have a working video camera anymore on my phone.. so I thought to flash a stock ROOTed rom instead...
Then I found this threat about an updated version of Jedi Mind Trick's ROM labled JB 3.. So I wiped as much as I could in recovery and chose to format all the options it gave me in recover , Format system , data , cache , emms(or something) .. and now when I boot the phone , it shows the first flash screen , and the samsung logo starts to shimmer then it reboots back to the splash screen and repeats this process everal times before just going black and sitting there..
So I've successfully bootlooped my phone doing this..
MY PROBLEM -- I don't know how to charge my phone or connect to it to install anything else..
Is this a serious problem? How can I charge my phone to continue troubleshooting it? It still has some battery to try some things but I don't know how to hook it up to transfer any other roms to it via USB cable and PC in it's current state..
I'm very computer savvy but I'm trying to learn this phone modding stuff and I realy hope I didn't brick my phone in this process.
Can someone please help me out here? I'll be on the forums religiously until I figure this out.
What should I start doing first??
Any help would be greatly appreciated!! Thanks!
still working at it
I think I'm at the point of having to use ODIN to flash a new rom since i cannot simply copy this rom to the sdcard to use clockwork to flash it .. Am I correct on this ?
For some reason this rom I found (should be stock rooted tmobile gSII rom) does not want to open from ODIN's PDA button cause its in .zip and not .tar or anything... I'm not sure how to flash this rom with ODIN ( I'm not even 100% sure this is how its supposed to go) Any suggestions ?
phew
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
zarklon said:
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
Click to expand...
Click to collapse
Is this true? Through a recommendation (haven't done anything to my phone from rooting/flashing KANGSJUGGERNAUT2 years ago), I tried to flash CM10 and ended up with a bootloop myself. Tried flashing through ODIN but it kept crashing; does anyone know why?
Afterward, I tried to reflash it through CWM and from then on bootloops into a installation process that never completes.
For some reason my CWM turned super slow, freezes/hangs and reboots after a few minutes.
I gave the phone to a friend who does this stuff on the regular but he said my initial flash wasn't complete cause in download mode says I'm still running official? No clue.
I was told this via email/chat: "No luck, it won't even boot anymore, I think I'll just bring it back tmrw morn
10:43 PM
Sorry I'm at a wedding (yea I know random) I left my phone with coat check
OK I've narrowed down the reason but not the solution, you had an AOKP based ROM which fundamentally is based on CyanogenMod, but it wasn't correctly flashed as the phone still thought it has factory ROMs still running
11:10 PM
Clockworkmod(even though it was working before) wasn't accessing the partitions of the phone correctly so it wasn't properly wiping or flashing properly.
11:12 PM
So basically from the first time you flashed cwm it didn't flash properly then the next time you flashed using the new recovery it didn't flash anything it was supposed to do itself properly , so basically it was a chain of events in addition to a bad boot loader, that's why it never went to recovery or download mode correctly
11:13 PM
That's something that had to do with the way the phone was built meaning you may of had a bad bootloader from the very begin and are now feeling the synptoms
Basically, and I would hate to be the reason or partially the reason you have a dead phone, basically it was a matter of coincedencr that it happened as this could of happened at anytime, once you have a bad boot loader its pretty much down hill from there"
Any helpful insight as how I can rectify this? is my phone truly dead? Sorry about the quoted format, it was copied and pasted.
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
tronmech said:
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
JahJahLoO said:
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
Click to expand...
Click to collapse
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
sam.balia1012 said:
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
Click to expand...
Click to collapse
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
dont give up
JahJahLoO said:
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
Click to expand...
Click to collapse
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
sam.balia1012 said:
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
Click to expand...
Click to collapse
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
JahJahLoO said:
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
Click to expand...
Click to collapse
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
sam.balia1012 said:
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
Click to expand...
Click to collapse
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
JahJahLoO said:
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
Click to expand...
Click to collapse
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
sam.balia1012 said:
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
Click to expand...
Click to collapse
It might as well have... :crying:
So i bricked my Samsung Galaxy S3. I believe it is hard bricked because there is absolutely no response from the phone. Can't boot into recover, download, or regular boot. The phone has at least 40% battery when I last saw it work.
I was attempting to roll back my android OS to see if I could extend my battery life but every time i tried using odin my download mode would give me "sv rev check fail" so i attempted to unlock the boot loader. I couldnt odin it so I flashed a custom rom to check if I could flash roms on my phone. The slimkat custom rom worked but when I tried to flash back to stock I would get the sv error. I saw that EZ-Unlock app would work so i tried it out. The app said it unlocked but when I restarted the phone to get into download mode, the phone seems to be bricked.
I have a usb jig but it doesnt seem to force my phone in to download mode and I am waiting on a micro SD card to try to un brick it. How can I use the micro card to un brick the Tmobile version of SG3?
Samsung Galaxy S3 SGH-T999
First of all the bootloader is NOT locked, so whatever that app does it was not mean for this device.. You should never attempt to downgrade firmware, it has been stated many times that there is high risk to hard brick when you try to bypass this restriction. The unbrick might work
Follow instructions in the debrick thread and hopefully it'll work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
NomNomMOn said:
I saw that EZ-Unlock app would work so i tried it out. The app said it unlocked but when I restarted the phone to get into download mode, the phone seems to be bricked
Click to expand...
Click to collapse
thats what i used on my first S3. bricked it like a............brick.lmfao.
gave it to some guy and i here now that he was able to revive it by some magical hoo-doo crap. well thats what i deserve for not reading reading and reading some more.
well , good for him is all i can say.! at least its gettin used ! :sly:
err on the side of kindness
Lol! I couldn't remember for sure if that's how it had happened on this thing, so I didn't want to say for certain that it was fixable. (Should a just asked you, but in my own defense, what's left of my mind these last few weeks is pretty much a scrambled mess!)
Anyway, I can 100% confirm that this type of brick is fixable. Using it as we speak/type!
And thanks to mrrocketdog for saving my a$$ with this thing! I may not have been around at all the last little while if not for him! (Might be back using my sad little MyTouch 3G Slide!)
Sent from my SGH-T999 using Tapatalk