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...
I just rooted my HTC Desire and installed CM7 on it (loved it on my HTC Legend). But suddenly today, after I turned Wifi on, it started rebooting all the time, couldn't do anything to stop it. I thought "Hey, there was the radio flash thing in the tutorial that I didn't do yet, I'll try that out" so I flashed the radio. Then I chose reboot system, but it just booted to a logo with an android coming out of a trash can, and looked kinda stuck there. So I took out the battery and plugged back in. Now if I try to turn it on, it'll just vibrate 7 times - no picture or anything. Also there's no LED when I plug it to the charger.
I had those 7 vibrates too.
Happened after i flashed the cm7 hboot over my stock hboot while trying to enter recovery. After i re-flashed my recovery using fastboot, everything worked again. What happens if you try to power up while holding down vol- ? Did you use fastboot or your phones recovery mode to install the radio?
I am not able to start in recovery or anything. I tried vol. down + power and back + power and no matter what I try, it just vibrates 7 times. I used the recovery mode to install the radio.
You could try to connect your phone via usb and check if fastboot discovers your device. If yes, flash hboot and recovery using fastboot. If not, well... i dont have a clue. Sorry :/
Computer discovers nothing when I plug in the phone.
Bad news when u pulled battery u interrupt the process n u now have a bricked device I would b very surprised if u managed to do anything
Pulling battery when doin a radio update is a BIG NO NO I'm sorry but ur stuck with a 400+ mirror now
Please look at this link
http://www.google.co.uk/m/search?site=images&client=ms-android-htc&hl=en&gl=uk&source=mog&aq=&oq=&aqi=&fkt=&fsdt=&cqt=&rst=&htf=&his=&maction=&q=android+radio+update#i=95
If that the image u saw when u pulled battery ur defo screwed
The Best Things Come To Those Who Wait
Your link doesn't work.. I found a picture of what was showing when I unplugged the battery, but I'm not allowed to post links to other sites on these forums yet.
U need to copy the link for some reason its not showing up
Pm the link u have
The Best Things Come To Those Who Wait
Inrego said:
Your link doesn't work.. I found a picture of what was showing when I unplugged the battery, but I'm not allowed to post links to other sites on these forums yet.
Click to expand...
Click to collapse
inrego
yes the image u just sent me is correct
the image showing would of ment it was installing the radio and because u pulled battery u have corrupt the flash and unfortuntly bricked ur device
i will look for a solution on the net but im not sure if ill find anythink sorrry
Inrego said:
Your link doesn't work.. I found a picture of what was showing when I unplugged the battery, but I'm not allowed to post links to other sites on these forums yet.
Click to expand...
Click to collapse
heres a few thread about some pulling battery on radio flash
http://android.modaco.com/content/g...m/304368/can-the-nexus-one-be-bricked/#entry0
http://android.modaco.com/content/h...50/help-cannot-turn-on-after-flash-new-radio/
i cant find anythink about fixin the issue sorry
Well thanks alot for trying. At least it seems like it shouldn't be too hard to get a replacement unit..
Inrego said:
Well thanks alot for trying. At least it seems like it shouldn't be too hard to get a replacement unit..
Click to expand...
Click to collapse
all depends on if ur on warranty if u have receipt and warranty then all is ok with out them u stuck basically
sorry couldn't help more hopefully lesson learnt playing with radio is risky business
Yea got warranty and reciept and all that, so np there
Inrego said:
Yea got warranty and reciept and all that, so np there
Click to expand...
Click to collapse
nice one then just make up a bull**** reason ok well hope u get a replacement
Wait a minute...
Inrego said:
Well thanks alot for trying. At least it seems like it shouldn't be too hard to get a replacement unit..
Click to expand...
Click to collapse
For the record to help some of you out who ended up here Googling: I had a similar issue. My HTC Desire SV did not boot, and when charging, only had an orange flashing light, and the phone vibrated 7 times. I did 2 things that got it back up:
1) left the phone off for say 10 minutes (I read about overheating issues in general, although the phone did not feel hot).
2) removed the battery for a couple of minutes.
VERY IMPORTANT: for step 2: make sure to have the battery removed long enough to drain internal charge. I removed and installed the battery in a second or so at first, and still the phone did not boot. After leaving out the battery long enough, it booted again. It appears to me that the issue in my case was a rather big internal charge capacity which kept internal state (memory and/or CPU?) from booting. Hope this helps...
Hi, experts, help needed here.
My galaxy nexus (GSM version) was 4.0.4 perviously, then I OTA it to 4.1.1 and my phone's unlocked but never rooted. After OTA to 4.1.1, everything works fine for couples months. But about 1 week ago, when i tried to update an App then an odd thing happeded, right after i pressed the update bottle, screen fliker happened, then the phone stopped responds, after I pull the battey out then put it in, the phone just kept restarting over and over, only showed me an google logo with a un-locked icon...
I tried to get into the recovery mode and flash it with the Galaxy Nexus toolkit for whatever 4.0.4 or 4.1.1 version factory images, but everytime right after starts, then screen fliker occurs and then the toolkit just hung there. - and this even occured while i tried to wipe the phone.
I tried to use the odin tool as well, but still, everytime right after start flash, screen fliker occurs and odin hung there. And the worse thing is, after my last try with Odin, now my phone is showing a phone connects to a computer icons and a yellow triangle...
Is there still a hope? Thanks in advance.
My guess is Odin messed up your partitions. Can you still access the bootloader?
Petrovski80 said:
My guess is Odin messed up your partitions. Can you still access the bootloader?
Click to expand...
Click to collapse
no.. prevously i can access it, but now, only the yellow triangle and the phone and computer's icon shows up.
what can I do? :crying::crying:
not sure if it would be wise to suggest this, but you could try omapflash. I'm curious about it myself, I guess I'll start looking into that. if it has power like nvflash, not sure if that would help, since you have no backup of your "good" partition table. If you have the guts, of course. I would just return the device in to warranty. :victory:
edit: first google hit, title says "gt-i9250", the gsm version, don't know what you roll op.
edit2: read the whole thread. pretty useful insight right there.
bk201doesntexist said:
not sure if it would be wise to suggest this, but you could try omapflash. I'm curious about it myself, I guess I'll start looking into that. if it has power like nvflash, not sure if that would help, since you have no backup of your "good" partition table. If you have the guts, of course. I would just return the device in to warranty. :victory:
edit: first google hit, title says "gt-i9250", the gsm version, don't know what you roll op.
edit2: read the whole thread. pretty useful insight right there.
Click to expand...
Click to collapse
Yup, OMAP Flash should work.
EDIT: Actually, I just re-read the post above: Odin generally will work if you see the screen with the yellow triangle. If not, use OMAP Flash and then re-try Odin.
efrant said:
Yup, OMAP Flash should work.
EDIT: Actually, I just re-read the post above: Odin generally will work if you see the screen with the yellow triangle. If not, use OMAP Flash and then re-try Odin.
Click to expand...
Click to collapse
hmm, i forgot that existed.
seriously, i think that a lot of the issues i see in that thread are probably caused by windows.
maybe OP's device's xloader/uboot went down the drain?
edit: found another good post on this. bookmarked.
edit2: and some more right here.
edit3: Naturally, I deviate away from toolkits or batch scripts, so I'm trying to look at this like nvflash. One thing that I read is that Omapflash commands are issued on the target instead of the host like fastboot, so that is making my mind spin.
edit4: here. "OMAP4460_TUNA_8G_HS_PRO 444007 01 HS" - 8G probably means hardware revision, the one we see in bootloader. HS could be High Speed device. Nope, High Security.
edit5: how many edits this going to have... "OMAP4 Jellybean Release Notes" - omappedia
edit6: totally different idea. OP, do you have an OTG cable? Because we got something called "SYSBOOT"
edit7: this is the most interesting thing yet. i'm salivating right now.
efrant said:
Yup, OMAP Flash should work.
EDIT: Actually, I just re-read the post above: Odin generally will work if you see the screen with the yellow triangle. If not, use OMAP Flash and then re-try Odin.
Click to expand...
Click to collapse
First of all, thanks for all the replys, that really fresh my mind..
For your addition information, yes, odin does recongnize my my while I connects to the PS, I guess the SCREEN FLIKER may be caused by the wrong odin tar packages... For my current situation, which version of the system should I flash? 4.0.4 or 4.1.1 or it doesn't matter? Besides, do you know where can I download a full packages of Odin flash packages which includes the partion table as well? Sorry to ask this stupid questions here cause I'm a newbee here and this is my first Android phone...
I've never used odin but I bookmarked this post just in case (I haven't seen any 4.1.1 ODIN repacks)
ge_johnny said:
First of all, thanks for all the replys, that really fresh my mind..
For your addition information, yes, odin does recongnize my my while I connects to the PS, I guess the SCREEN FLIKER may be caused by the wrong odin tar packages... For my current situation, which version of the system should I flash? 4.0.4 or 4.1.1 or it doesn't matter? Besides, do you know where can I download a full packages of Odin flash packages which includes the partion table as well? Sorry to ask this stupid questions here cause I'm a newbee here and this is my first Android phone...
Click to expand...
Click to collapse
You shouldn't need a partition table. It will work without one. And you can use either a 4.0.4 or a 4.1.1 tar. Both should be available in the dev section. Make sure you pay close attention to which boxes need checks in them - never put a check in box related to repartitioning.
For future reference, I would always recommend to use fastboot before resorting to odin. Less chances of you getting into the situation that you are currently in.
Sent from my Galaxy Nexus using Tapatalk 2
here is the update of the problem.
OMAPlash doesn't solve my problem at all, I run the defaullt omap4460_tuna_hs_pro.txt script, it looks like flash something to my phone but the problem still there.
I tried redownload some odin packages into my phone, but still screen fliker happened...
Any other suggestions?
from what i've read, you now have the ability to enter the target, omapflash commands are issued on the target, not on the host.
you can feed the device the x-loader and uboot, which will then give you fastboot, restoring then a factory image.
someone that has actually done the whole procedure or has more info on this, please share.
Sent from my i9250
Help!!
bk201doesntexist said:
from what i've read, you now have the ability to enter the target, omapflash commands are issued on the target, not on the host.
you can feed the device the x-loader and uboot, which will then give you fastboot, restoring then a factory image.
someone that has actually done the whole procedure or has more info on this, please share.
Sent from my i9250
Click to expand...
Click to collapse
Hey Could you please maybe explain how to go around this? I currently have a yellow triangle brick on my Gnex but it does get detected via USB on Odin so if there is a fix I would like to know!
Thanks in advance!
If I were you, I would just use a jig to get it into download mode, then just reflash. I dont think it will take a flash with that boot error.
Check this thread here.
http://forum.xda-developers.com/showthread.php?t=1925468
Sent from my i9250
Don't think I explained myself very well
bk201doesntexist said:
Check this thread here.
http://forum.xda-developers.com/showthread.php?t=1925468
Sent from my i9250
Click to expand...
Click to collapse
Hey guys thanks a lot for your replies! I don't think I got the severity of the problem across well enough. See, the phone was in bootloop but everything was going fuzzy all the time (including recovery) and the recovery mode was corrupt it wouldn't let me clear cache! and while it was running the clearing process, all I could see was yellow lines of errors saying cache cannot be mounted. After loads of failed attempts of trying to flash Stock ICS and Jellybean (Yakju, without wallet) the phone decided it wanted to brick and so didn't turn on at all! I found a forum online (http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/) which gave me the OMAPFlash method with which I unbricked the phone and got it started a couple of times. I tried to then flash stock again via fastboot, it didn't work it simply couldn't send files to my phone although the phone was connected because it was detected under fastboot devices. After this, I went into download mode and tried to flash using Odin, however, this crashed and the phone crashed too which required me to pull the battery out. From then, all I get is > phone!Pc < and now the phone is detected via USB and via OMAP but the OMAP doesn't bring me back to fastboot its stuck on that yellow triangle screen!
Again, Thanks a lot for all your help! If I don't get this sorted in a few days I'll be sending it to Samsung!
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
ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas
You probably going to get a better help at TAB S2 board this is for the tab S1.
If it is hard bricked there is JTAG methods that can help, just need to find one for your device, not easy though.
But all I can do is share my experience with something like this, in a more "cheap" way than JTAGs, dunno if it helps:
I never had a similar problem on the tab S. But in the past a galaxy player 5.0 of mine had a very similar problem (as far I remember the screen just powered the back light but without any letters or simbols)
in 2012, I bricked it trying to mount a swap partition (280mb RAM ftw) accidentally pointing the wrong partition, and got the entire internal storage corrupted.. everything.. system, bootloader, recovery etc
My player was turning on only connected to a USB or charger, like yours. in fact It was hard bricked
I was able to recover it using Linux (because it is the only system able to communicate with the bricked device I had)
The problem is that everything need to be very specific, for example I used a software made for the galaxy s1 to "revive" my player 5 (both have the same hardware) it just made the device be detected via ADB. So I needed to prepare a SD with the same size as the internal storage (in this case 8gb) using the Linux terminal to mount in the SD an exactly schematic of the internal memory using a dump of another device that a xda user shared, (the dump was empty only with the bootloader, recovery etc) but it still had 8gb decompressed. So after that I used ADB to push the SD card content to the internal memory. And it get back to life \○/
Well.. it took me 1 week with a guide!! On the trial and error method. But it worked.. not perfectly, I get bootloops every time I try to flash a rom via Odin, but recovery works, and I have the device working until today
Hi, I Greatly appreciate your reply and advice. Think tho that your solution is a bit beyond my know how I know a little about ADB etc but i would have difficulties in compiling necessary files to sideload. Also many tanks for the link din't realise. Thanks Pal!
Alpha1BA said:
ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas
Click to expand...
Click to collapse
If you can get it in to download mode you can flash stock rom back on it.......refer to xda samsung tab s2 for more details on this........
thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/
Alpha1BA said:
thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/
Click to expand...
Click to collapse
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....
stinka318 said:
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....
Click to expand...
Click to collapse
Stinka ure a superstar (atm!) I did as you suggest to no avail but I noticed a slight increase in the time it took to start rebooting again. I do not know which buttons did this but some 20 later it lasted long enough for me to be able to flash twrp. Now i havent actually tried that as yet as i wanted to check with you first... I have the battery logo on screen, i tried recovery and it started as it should but then rebooted, now im unsure at this time whether the battery is almost dead or not so i got it on charge and have the grey battery with a white flash inside... is this what i want for now until its charged? if so i'll keep you informed thamnks more than u know if uve helped me fix this, the reason i was flashing was because when i received it (no warranty!!) the screen sometimes flickered and it would constaly end up rebboting after digging around re that im lead to believe it need a new battery and for the connecting wires to be resoldered. Anyways thanks again n as I say i'll keep this updated
Cheers
Tony
one of the probs i hab/have with this unit is that it takes approx a day to fully charge!!! when i received it the screen flickered on the odd occasion but it was rebooting much more frequently. It came with stock n not messed with previously (i new this prior to purchase so got it for right price thinking it only needed flashing, how wrong was I!!!) so I flashed and encountered the above mentioned problems! thanks to stinka I surprisingly managed to flash a recovery... now provided all goes to plan, which rom would one suggest for stability and generally hassle free and prusuming the aforementioned probs, rebooting etc are still there what could i try to stop that? other than a debloated stock I found Lineage an excellent rom but still the problems got so bad the unit became unusable and was lucky not to go out the window. Im thinking do i start with a replacement battery and check the wires etc or could this still be a software issue??
if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again
In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/
RoIlingThunder said:
In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/
Click to expand...
Click to collapse
Thanks for that!!!
Tony
does look somewhat OTT!!!
will i have to odin stock first then flash rom i want or will it go straight from first flash via twrp considering there is absolutely nothing on phone at mo apart from twrp.
Alpha1BA said:
if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again
Click to expand...
Click to collapse
My guess is your issue is lack of charge in the device. That's the reason for the flashing failure and the reboot loop with the firmware error.
Bang it on charge for a while then irrespective of what it's doing, whether it's looping or not, hold POWER + HOME + VOL DOWN until download mode appears.
Reflash the stock firmware with odin.
swapped battery and reflashed stock via odin. It has helped although the issues are all still there its just they happen less frequently which doesnt mean its any less frustrating.