Related
Is anyone manage to brick the phone already?
How likely/ or stupidity you need to actually bricking the phone?
What is a NO NO and how to avoid it?
That's the question.. thanks!
Main thing is read as much as you can before you do any changes, it helps to check what few sites say.
When I rooted my phone I could not get it to run the update part, tried time and time again, one site said "rename the file to update.zip and paste it" then I read on another site to just call it update as it is already a zip file.....and then it worked, small bit of detail like that stopped it working to start with so if I was you I check a few sites and get all the info you need, but also as many would say if you are that unsure dont take the risk and wait for samsung updates with Kies.
voodoochild2008 said:
if you are that unsure dont take the risk and wait for samsung updates with Kies.
Click to expand...
Click to collapse
Kies actually failed to update my phone, I have the Korean Galaxy S SHW-M100S, and it showed an update was available. So, I thought I was bricked for about 30 mins, kept trying to get it to work itself out of the problem in recovery mode, after about 4 tries (1 reboot of Windows, plus changing USB ports and 2nd try with this static new config) eventually it did, thank God.
Do not remove usb while in the middle of flashing with odin
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
amerikian said:
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
Click to expand...
Click to collapse
I was gonna say something along the lines of a smart ass, but I can't. That sucks.
why would you do a battery pull?
madjsp said:
I was gonna say something along the lines of a smart ass, but I can't. That sucks.
why would you do a battery pull?
Click to expand...
Click to collapse
I've been flashing all night and wanted to do it "right" this time....realized my SIM and SD card were still in there mid-flash so wanted to pull them and start clean..........................
Yeah....don't do that.
Guess I'll be that "guy" paying a visit to the local AT&T shop tomorrow....
Luckily I'm w/in my 14 days since getting it....
delete. ......
amerikian said:
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
Click to expand...
Click to collapse
I've removed the cable half way and rebooted, and it was fine..
You simply remove the USB cable, battery again, put the battery in, and you'll be able to get to downloader mode.
The phone seems to have a component that ODIN doesn't touch that is read-only that handles download mode. Most hardware devices tend to have safeguards. I haven't confirmed this, but I've noticed the same applies to NAS devices (which tend to have a special redboot which uses tftp).
I have still yet to have seen any evidence of anyone permanently bricking their phone, but I've seen a few cases of "oops, got it working again".
Remember, Samsung are eager to reduce their support costs, and failsafe's are cheap and easy to add.
yes, the odin doesn't touch the 'bootloader' , or the small piece of code that enable the download mode, so there's no way you can brick the phone.
I have tried to repartition the phone while flashing firmware that has nothing except the csc data (i.e. no kernel, no factory rfs, etc) and the flash procedure went succesfully but in actual fact, my phone contains a new set of partitions that contain nothing except the small csc data.
and i still able to reflash, although I must make sure that the phone is totally shutdown (i.e. take out battery, let it stay for awhile before putting back)
andrewluecke said:
I've removed the cable half way and rebooted, and it was fine..
You simply remove the USB cable, battery again, put the battery in, and you'll be able to get to downloader mode.
The phone seems to have a component that ODIN doesn't touch that is read-only that handles download mode. Most hardware devices tend to have safeguards. I haven't confirmed this, but I've noticed the same applies to NAS devices (which tend to have a special redboot which uses tftp).
I have still yet to have seen any evidence of anyone permanently bricking their phone, but I've seen a few cases of "oops, got it working again".
Remember, Samsung are eager to reduce their support costs, and failsafe's are cheap and easy to add.
Click to expand...
Click to collapse
I thought in the Big FAQ, it said... do not disconnect the usb-cable but to remove the battery if want to interrupt it...
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)
amerikian said:
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
Click to expand...
Click to collapse
Similar happened to me,although I didnt pull the battery, the phone just disconnected halfway through the flash.
Had half hour of panic,where I thought it was bricked.
Had to do a few battery pulls,restart PC a couple of times and mess around with different USB ports,but finally got it working.
Have flashed a 3 times since without a problem.
chluk2425 said:
I thought in the Big FAQ, it said... do not disconnect the usb-cable but to remove the battery if want to interrupt it...
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)
Click to expand...
Click to collapse
That means you shouldn't do any of those things! So don't disconnect usb, don't remove the battery and don't interrupt the process.
zenkinz said:
yes, the odin doesn't touch the 'bootloader' , or the small piece of code that enable the download mode, so there's no way you can brick the phone.
I have tried to repartition the phone while flashing firmware that has nothing except the csc data (i.e. no kernel, no factory rfs, etc) and the flash procedure went succesfully but in actual fact, my phone contains a new set of partitions that contain nothing except the small csc data.
and i still able to reflash, although I must make sure that the phone is totally shutdown (i.e. take out battery, let it stay for awhile before putting back)
Click to expand...
Click to collapse
Are you sure that flashing (through ODIN) in any case never touch that "Download Mode" piece of code ? Even you select all the options in ODIN ?
Can anyone confirm this ? Actually I want to play with Kernel and RFS (have some ideas to try) but afraid of full bricking. So if this download mode is always present then I can play with it without any problem.
Waiting for response.
amerikian said:
I've been flashing all night and wanted to do it "right" this time....realized my SIM and SD card were still in there mid-flash so wanted to pull them and start clean..........................
Yeah....don't do that.
Guess I'll be that "guy" paying a visit to the local AT&T shop tomorrow....
Luckily I'm w/in my 14 days since getting it....
Click to expand...
Click to collapse
Believe me! you can still access the download menu
The bootloader is almost always writeprotected and cannot be overwritten. You would probably have to connect a cable to some internal port like Jtag to be able to reflash the bootloader section. Atleast that is the case in 99% of all bootloaders. Im very certain that you cannot cripple the bootloader.
Sent from my GT-I9000 using XDA App
jackiechan8 said:
That means you shouldn't do any of those things! So don't disconnect usb, don't remove the battery and don't interrupt the process.
Click to expand...
Click to collapse
gosh man, thanks correcting me but if that's the case, what should i do if it doesn't reboot by itself?
take out the battery, wait for 30 to 60 secs, put the battery in and start phone with vol down + menu + power
Don't disconnect the usb or do anything else while flashing!!!
I removed the usb cable when it started flashing (i thinked it was stuck, happens sometimes), and since it does not boot anymore. I press the power button, volUp + home + power, volDown + home + power... nothing happens.... it's dead, doesn't turn on at all...
after all i have read i think it's almost impossible to brick the sgs since you always get back into download-mode. the only case i read where i believe that it's a goner is flashing with the wrong (in this case the at&t) odin version. those guy's just got a white sreen with at&t logo at boot. they didn't get into download mode any more because the button mapping on the captivate is different ... so thats really bad luck, dont't try that at home
jodue said:
after all i have read i think it's almost impossible to brick the sgs since you always get back into download-mode. the only case i read where i believe that it's a goner is flashing with the wrong (in this case the at&t) odin version. those guy's just got a white sreen with at&t logo at boot. they didn't get into download mode any more because the button mapping on the captivate is different ... so thats really bad luck, dont't try that at home
Click to expand...
Click to collapse
well, mine doesn't boot at all, and i flashed (technically not, because i removed the usb cable at the very start) with the RIGHT odin version
Maybe if it fails when flashig sbl (secondary boot loader ) you can't go into download/recovery mode...
Hello, everyone, I have a problem with my phone.
Before the problem, I was rooted without any custom roms. I have never installed any custom roms on my phone. I have always been stock, but rooted.
This morning, T Mobile pushed an updated to my phone. I did some research (not sure if I did enough) and apparently it was the UVLDE update. So I clicked it, phone restarted in 5 seconds, and restarted in clockwork mod, I believe. It was the screen that allows me to reboot along with some other options and is navigated by pressing up and down on the volume buttons.
I pressed reboot phone and the phone rebooted and worked normally throughout the day.
Now, I wake up (and I am not sure what happened, maybe I accidentally turned the phone off in my sleep) and I attempt to turn the phone on and it vibrates consecutively, on and off, and sometimes the screen blinks.
Is there any way I can fix this issue?
Thanks for your time. I performed a search, but I couldn't find the issue or I couldn't find any keywords.
Mr. Holmes said:
Hello, everyone, I have a problem with my phone.
Before the problem, I was rooted without any custom roms. I have never installed any custom roms on my phone. I have always been stock, but rooted.
This morning, T Mobile pushed an updated to my phone. I did some research (not sure if I did enough) and apparently it was the UVLDE update. So I clicked it, phone restarted in 5 seconds, and restarted in clockwork mod, I believe. It was the screen that allows me to reboot along with some other options and is navigated by pressing up and down on the volume buttons.
I pressed reboot phone and the phone rebooted and worked normally throughout the day.
Now, I wake up (and I am not sure what happened, maybe I accidentally turned the phone off in my sleep) and I attempt to turn the phone on and it vibrates consecutively, on and off, and sometimes the screen blinks.
Is there any way I can fix this issue?
Thanks for your time. I performed a search, but I couldn't find the issue or I couldn't find any keywords.
Click to expand...
Click to collapse
Maybe a brick? And questions go in the questions section for future reference.
Sent from my SGH-T989 using xda premium
Thanks. I'll remember that for the future.
I don't know if it's a brick or not. I haven't tried anything fancy yet. I'm looking for assistance before I go any further, if there is any further place to go.
Mr. Holmes said:
Thanks. I'll remember that for the future.
I don't know if it's a brick or not. I haven't tried anything fancy yet. I'm looking for assistance before I go any further, if there is any further place to go.
Click to expand...
Click to collapse
If you have clockwork mod on your phone and you can get to the clockwork mod menu, go to mounts and storage and plug your phone into your computer and click mount usb storage and copy this rom to your phone.
http://theunlockr.com/2011/11/29/how-to-unroot-the-samsung-galaxy-s-ii-t-mobile-version/
Then go to install zip from sd card and pick the one you just copied to your phone. It'll put you back on stock 2.3.5 hopefully that will work and if it does you will have to re root your device because this zip puts your phone to completely stock and removes the root. Hopefully this works for you it has for me in the past good luck.
Sent from my SGH-T989 using xda premium
Update.
I plugged it in to my computer via the USB.
Apparently, the computer can't recognize itbecause the device has malfunctioned (not sure how accurate that is), but the phone has turned on and I can use it.
I know the problem still, exists, so should I still follow your advice, JPOKeefe's, and go completely back to normal after erasing everything? I have no problem doing that to save my phone.
Modification:
Maybe the battery was just dead... which is why it's 0 % charged and it won't turn on after it was working perfectly before I slept.
If that is the case, then I am prepared to defend my intelligence! I guess it's just some paranoia from the update this morning that didn't actually go through.
Mr. Holmes said:
Update.
In plugged it in to my computer via the USB.
Apparently, the computer can't recognize itbecause the device has malfunctioned (not sure how accurate that is), but the phone has turned on and I can use it.
I know the problem still, exists, so should I still follow your advice, JPOKeefe's, and go completely back to normal after erasing everything? I have no problem doing that to save my phone.
Click to expand...
Click to collapse
Honestly you don't NEED to do it but if your phone is messing up and wont boot maybe you should go back to stock and re root when you read and learn more and feel more comfortable having a root.
Thanks for you quick replies.
I ninja edited my post, by the way. I'll give it a moment to charge and see what happens.
The phone was acting slightly stupid this morning after I attempted that update, so I guess I had to be sure it wasn't something drastic.
I have been comfortable with the root I had. If this phone bricks or blows up, then I have an excuse to get a GS3. Because, you know, I might as well. =p
Mr. Holmes said:
Thanks for you quick replies.
I ninja edited my post, by the way. I'll give it a moment to charge and see what happens.
The phone was acting slightly stupid this morning after I attempted that update, so I guess I had to be sure it wasn't something drastic.
I have been comfortable with the root I had. If this phone bricks or blows up, then I have an excuse to get a GS3. Because, you know, I might as well. =p
Click to expand...
Click to collapse
Just hit the thanks button!
And i have to wait till december for GSIII thats when my contract is up /:
Questions go in the Q&A section
I have created this thread for all you SG-SIII Noobs & Senior Members!
The purpose of this thread is to limit the number of (sometimes useless) threads, that are created over a simple problem that can easily be solved by READING OR SEARCHING.
This is the Emergency thread!
*Did you run into a problem and need quick assistance?
*Do you have a question or concern about your SG-SIII device?
Don't panic just ask here and I or WE THE SG-SIII COMMUNITY will gladly help!
In case of emergency!
Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?
Rayman0625 said:
Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?
Click to expand...
Click to collapse
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2
...Awesome... said:
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.
Sv: ***Emergency Thread*** Here To Help!
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app
lintz said:
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Phone wont boot without the battery in, and with it in I cant stay in recovery without with rebooting.
Rayman0625 said:
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.
Click to expand...
Click to collapse
Even better then lol just test it out at work. I'm about 80% its your battery specially if you OV/UC.
I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.
heartspains88 said:
I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.
Click to expand...
Click to collapse
after you odin, you need to wipe data/ factory reset to boot. If you can't get into recovery ( Power, Home Button, and Volume Up), then try reflashing your stock image in Odin and check your MD5 sum, so you can rule out a bad download
Thanks for the reply, I'm re-downloading the stock rom now to verify it's integrity and do a new flash. I cannot get into recovery, so we will see after the new flash. Pleading ignorance on one subject, how would I go about checking the MD5 sum to verify the file has no issues?
Additionally I did try to Odin recovery and still could not boot into it, this was however before attempting to re-download and flash a stock rom again.
**Edit//Update** Re-downloaded and flashed stock rom, was able to get into recovery and wipe, booted up fine.
Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!
frettfreak said:
Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!
Click to expand...
Click to collapse
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2
Towle said:
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!
frettfreak said:
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!
Click to expand...
Click to collapse
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2
Flashing stock with Odin can take up to ten minutes its normal like the man said above just let it do its thing
Towle said:
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Worked great! Thanks!!
http://forum.xda-developers.com/showthread.php?t=2113883
Let's see if you have any solution for me?
Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)
ohshootrawr said:
Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)
Click to expand...
Click to collapse
Do u happened to have apps that control frequency like setcpu etc? They might be conflicting each other
Sent from my HTC One S using Tapatalk 2
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 left my phone on the charger in the car because it was dying, came outside and it was stuck on the Galaxy Note II screen with the green light on. I unplugged the cord, the phone refused to come on so I did a battery pull. Upon powering it back on, I get this screen that looks like Poltergeist and phone does nothing. When in Poltergeist, I can't get the computer to see my phone, so that I can back it up before formatting. Volume up, menu, power doesn't get me into recovery mode. I can't get into safe mode either. ican however boot volume down, menu, power it into the mode where I can flash it, Odin will see it, but going straight to flashing means I lose everything.
Does anyone have an idea beforehand? I know I'm asking a lot, but these forums have gotten way over my head over the years. This is an isolated incident, so if you could even attach the file directly that I can attempt to flash vids Odin to fix my booting issue vs saying goto X thread because every thread seems to have it's own multiple files. I just wanna recover it so it'll come on, back up it and then I'll research on my own how to flash it completely. It's 6am my time and I've gotta be up by 1130am for work, so please reply for dummies as much as possible
Thank you ahead of time.
PS - phone is stock on 4.1.2 rooted using CF Auto Root and that's it.
Morning bump...no quick advice?
60 readings, no one comment? "Hey, flash XXXXX and see if the display drivers come back", etc? It'll boot into flash mode, looks normal and the compputer sees it. Safe mode or normal boot give me Poltergeist and the computer wont see it so that I can try to backup everything before flashing....that's a lot of boobies pics (just trying to get some sympathy here) to have deleted
79 views...for the love of god, someone throw me a bone here. I get it, these are old phones now, these forums are full of know-it-alls who can't be bothered (devs) and "search" nazis (me being one of them) as I should just figure it out on my own...but I'm not. I've got versions of ODIN, I've got CWM Recovery files, stock MC2 and NE2 ROM's, I even found myself a PIT file. NONE OF THEM ARE WORKING. No matter which ODIN I use, they all stick at PIT regardless of whether I have re-partition checked or not. I've tried flashing PIT, CWM recovery, stock recovery, CF Auto Root and/or stock 4.1.2 - 4.4 ROM's in just about any combination of one or two together using each version of ODIN. No bueno.
I've got a very nice and thick 24/28awg cord I'm using, I can boot into dowloader mode but can not go into safe, recovery or boot normally. I've watched brick recovery videos on YouTube, I've downloaded files from here on the forums and www.galaxynote2root.com using various downloading I have included a picture of.
Someone, somethg...
10 attempts later...
Holy crap you forget how nice the Note is when you're back on a Epic for two days while working 12hr days and going through 6 batteries each day...
m5james said:
Holy crap you forget how nice the Note is when you're back on a Epic for two days while working 12hr days and going through 6 batteries each day...
Click to expand...
Click to collapse
Did you ever get this figured out? I'm in the same boat with the L900 Sprint Note 2...
Solved it by getting a working logic board from eBay
I broke down and bought a Note 3 off Craigslist for $300 but I'd still like to fix the Note 2 to make it into my backup instead of pulling the Epic outta the box again.