MOVED TO Q&A, Help & Troubleshooting forum
Hey!
My first post and it is a sad one! I think i've bricked my Hercules!
I just rooted the T989D. It was ok. I've flashed the PA 3.6 for hercules ROM, whit gapps and stuff, than flashed the latest radio and uber kernel. I noticed i had 13% of batery and when i rebootet it, the screen went off and it dosn't respond to any comand, just vibrate and show the baterry loading (it's connected to force) for like 2 seconds. It could be a heavy baterry drain?
It is like this for 15 minutes.
What should i do? I'm desperate :crying:
I had this situation before and somehow it booted. Try to let it fully charge and boot to recovery (power up plus volume +/- press while it's booting). Hopefully it will boot and you can recover a dependable nandroid. If that all doesn't work try powering while connected to pc and Odin stock Touchwiz and start all over again
Sent from my SGH-T989D using Tapatalk 2
strobel said:
MOVED TO Q&A, Help & Troubleshooting forum
Hey!
My first post and it is a sad one! I think i've bricked my Hercules!
I just rooted the T989D. It was ok. I've flashed the PA 3.6 for hercules ROM, whit gapps and stuff, than flashed the latest radio and uber kernel. I noticed i had 13% of batery and when i rebootet it, the screen went off and it dosn't respond to any comand, just vibrate and show the baterry loading (it's connected to force) for like 2 seconds. It could be a heavy baterry drain?
It is like this for 15 minutes.
What should i do? I'm desperate :crying:
Click to expand...
Click to collapse
Re-flash your rom. Make sure your battery is at least 70% charged. Make sure you wipe data/factory reset, wipe cache partition, wipe dalvik, and format system. Also if you are able to with your recovery, once your battery is at 100%, wipe battery stats. I personally like keeping my phone plugged in for any type of mod I do, just to be safe. Do this and let us know if it fixes. I know a lot of the time, the flash you use can mess up and cause issues, causing a re-flash.
Cheers,
jtgr94
Sent from my Samsung Galaxy SII T989D Hercules CM11 Android 4.4.4
jtgr94 said:
Re-flash your rom. Make sure your battery is at least 70% charged. Make sure you wipe data/factory reset, wipe cache partition, wipe dalvik, and format system. Also if you are able to with your recovery, once your battery is at 100%, wipe battery stats. I personally like keeping my phone plugged in for any type of mod I do, just to be safe. Do this and let us know if it fixes. I know a lot of the time, the flash you use can mess up and cause issues, causing a re-flash.
Cheers,
jtgr94
Sent from my Samsung Galaxy SII T989D Hercules CM11 Android 4.4.4
Click to expand...
Click to collapse
You just responded to a thread from one year ago
Hahaha my bad! I must of gotten consumed in browsing...smh
jtgr94
Sent from my Samsung Galaxy SII T989D Hercules CM11 Android 4.4.4
Related
running franco nightly #107 anyways i dont know wtf happen but today while at work everything was fine, phone ended up dying toward the end of my shift, i get off work, plug it into my car charger and it gets stuck at google screen. so i unplug it, turn it on normally, unplugged from car, and it boots for a half second and immediately dies before i could unlock it, plug it back into car again, bootloops, get home, plug it into wall charger, bootloop. my phone just wont power on... and i cant even get into recovery, it automatically resets itself while entering recovery. me = frustrated....
Edit: got into recovery and installed latest nightly saved to SD card and it still seems to be boot looping, am i going to have to wipe my phone? ):
Edit 2: did an advanced restore form a restore i had from about a month ago, flashed only boot. still looping.
Edit 3: phone is getting hot during bootloop, reflashed recovery and fixed red triangle error, still stick please help. i need to fix this before i got go school in the morning ):
Pull battery put it back in. Plug it in to the charger and let it sit for like half an hour the try to boot into recovery and wipe everything and flash a new rom. See if that helps.
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
Pull battery put it back in. Plug it in to the charger and let it sit for like half an hour the try to boot into recovery and wipe everything and flash a new rom. See if that helps.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
i just dont have hat kind of time right now, i mean ill do what i have too, and im pretty sad if i have to wipe everything...
edit, eff it whats your favorite rom? ill just start over. ive always wanted too try a new rom but i didnt want to have to wipe evrything and i liked stock 4.0.4 but i might as well give it a shot
Dylerium said:
i just dont have hat kind of time right now, i mean ill do what i have too, and im pretty sad if i have to wipe everything...
edit, eff it whats your favorite rom? ill just start over. ive always wanted too try a new rom but i didnt want to have to wipe evrything and i liked stock 4.0.4 but i might as well give it a shot
Click to expand...
Click to collapse
Right now I'm running the new gummy super fast and stable. Battery is the best I've had
Sent from my Galaxy Nexus using xda premium
Hello, I have a weird issue, I looked in the brick thread but didn't see any thing that was just like my issue. Last night I tried flashing the rom and used the zero system wipe available in the dev thread (not saying that is the issue just saying what I was doing). It was clearing the cache(never got passed the cache) for over an hour, then it powered off. I tried restarting it into recovery and it did half the time(especially if I removed the sd card) but couldn't mount anything(sd card /system, /data, etc). But this is were it starts getting weird and not like the brick thread. This morning I tried it again and it booted to recovery and mounted everything!!! Thought it was fixed so I went to do a factory reset to install a new rom. That was an hour ago and it is still clearing cache. The lines in the progress bar slowly move but no blue progress bar at all. Any help at all will be appreciated. I am afraid it will power off again and be a true brick this time (then again maybe it already is)
I am using TWRP and was on the 9/02 cm10 nightly before this all happened.
Thank You.
Edit: still clearing/formating cache but upon closer look it did format /data
nsmith4 said:
Hello, I have a weird issue, I looked in the brick thread but didn't see any thing that was just like my issue. Last night I tried flashing the rom and used the zero system wipe available in the dev thread (not saying that is the issue just saying what I was doing). It was clearing the cache(never got passed the cache) for over an hour, then it powered off. I tried restarting it into recovery and it did half the time(especially if I removed the sd card) but couldn't mount anything(sd card /system, /data, etc). But this is were it starts getting weird and not like the brick thread. This morning I tried it again and it booted to recovery and mounted everything!!! Thought it was fixed so I went to do a factory reset to install a new rom. That was an hour ago and it is still clearing cache. The lines in the progress bar slowly move but no blue progress bar at all. Any help at all will be appreciated. I am afraid it will power off again and be a true brick this time (then again maybe it already is)
I am using TWRP and was on the 9/02 cm10 nightly before this all happened.
Thank You.
Edit: still clearing/formating cache but upon closer look it did format /data
Click to expand...
Click to collapse
I've seen this happen one other time, though it happened just running in android, lost cache etc but just magically came back to life after being off for awhile. In that case AFAIK it didn't brick, or it did and they just never mentioned it.
It does however sound like its gonna give out and just lose them for good.
Only thing I can really suggest is just flash a ROM and see how it goes.
Tapatalked from my Galaxy S II.
pio_masaki said:
I've seen this happen one other time, though it happened just running in android, lost cache etc but just magically came back to life after being off for awhile. In that case AFAIK it didn't brick, or it did and they just never mentioned it.
It does however sound like its gonna give out and just lose them for good.
Only thing I can really suggest is just flash a ROM and see how it goes.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
It still says formatting cache should I just force shut down.
The diagonal lines in the progress bar are moving more smoothly now if that means anything.
Thanks for the reply.
nsmith4 said:
It still says formatting cache should I just force shut down.
The diagonal lines in the progress bar are moving more smoothly now if that means anything.
Thanks for the reply.
Click to expand...
Click to collapse
It will probably eventually shut down or reboot on its own if its having filesystem problems.
If you have adb up you can do adb reboot recovery and bypass the cache format it usually does when you use the volume button. Also you can pull a dmesg which will show what's going on in the file systems.
Tapatalked from my Galaxy S II.
well the device shut down again. It won't even boot to the acer screen, blue light just flashes. The computer knew I plugged something in but ADB says no devices. Guess it is bricked.
thanks for your help
nsmith4 said:
well the device shut down again. It won't even boot to the acer screen, blue light just flashes. The computer knew I plugged something in but ADB says no devices. Guess it is bricked.
thanks for your help
Click to expand...
Click to collapse
Yeah sounds like failsafe apx which happens on numerous sequential failed system or boot reads. If its under a year old I should suggest getting a rep on acer chat to set a repair in motion. If its under warranty it just costs shipping it to them. The rep can tell you if you're still covered.
Tapatalked from my Galaxy S II.
Thanks for all your help. Hopefully since it won't boot they won't notice I rooted and unlocked the boot loader.
nsmith4 said:
Thanks for all your help. Hopefully since it won't boot they won't notice I rooted and unlocked the boot loader.
Click to expand...
Click to collapse
If its in failsafe no they just replace the board and send it back. If it can get to the Acer screen then they can tell.
Tapatalked from my Galaxy S II.
Stuck on the samsung logo.
The battery drained dead, and I waited until I got home to charge it. I plugged it in and the grey battery popped up and a loading wheel, but it froze.
Now it doesn't turn on. I switched batteries and it goes to the samsung logo and sits there. I tried VolUP+VolDown+HOME+Power and All the other button combos and still nothing just goes to samsung screen and reboots, then I notice the led light flashes red very faintly and once quickly then the logo comes back up.
Any ideas?
Did you root or install custom recovery?
kirkla79 said:
Did you root or install custom recovery?
Click to expand...
Click to collapse
No I haven't tried to do anything of the sort. I just got this phone when it got released, and haven't explored that much with it yet. It just suddenly doesn't work after the battery drained dead.
I would just go back from where you bought it a get it exchanged then.
kirkla79 said:
I would just go back from where you bought it a get it exchanged then.
Click to expand...
Click to collapse
Yeah I'm just going to hate to lose everything because I couldn't do a backup...
Sucks.
Root install recovery and clear cashe partition and dalvik cashe. Use stock rom image with SU injected and do not wipe. Or exchange and loose everything
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
My girlfriend drained her battery until the phone shut off. Had to leave it on the charger for almost an hour before it would boot. I thought it should boot as soon as I plugged it in but that's not the case. Try letting it sit and charge for awhile.
jethro650 said:
My girlfriend drained her battery until the phone shut off. Had to leave it on the charger for almost an hour before it would boot. I thought it should boot as soon as I plugged it in but that's not the case. Try letting it sit and charge for awhile.
Click to expand...
Click to collapse
I left it on the charger for almost 3 hours. And nothing, not even the loading icon over the battery would disappear.
Could someone point me in the right direction for rooting etc... as the user described above?
PrestigeA said:
I left it on the charger for almost 3 hours. And nothing, not even the loading icon over the battery would disappear.
Could someone point me in the right direction for rooting etc... as the user described above?
Click to expand...
Click to collapse
Not sure your going to be able to root with a non-booting phone. Here are a couple links about rooting
Chainfire's method you need download mode
mrRobinson's root injected stock Roms, also need download mode
Good luck hope one of these works for you.
Just my $0.02 worth.
My suggestion is make sure you are using the original, Samsung battery. Let it charge for 8 - 10 hours. Take it off the charger, remove the battery from the phone, wait several minutes; then replace the battery and try to boot.
If that doesn't restore, I'd take it back to the store from which you purchased it, and see if a new, oem battery will let it boot. The store should try to do everything they can to help, short of replacing the phone. But it may just be your phone has gone bad -- in which case rooting isn't going to help...
Good luck.
PrestigeA said:
I left it on the charger for almost 3 hours. And nothing, not even the loading icon over the battery would disappear.
Could someone point me in the right direction for rooting etc... as the user described above?
Click to expand...
Click to collapse
Intall CWM with odin then reboot in recovery and install stock rooted .zip or stock based ROM. Its called a dirty install. You can do this by placing the .zip in a microSD then install from external in CWM. You will end up with all your old crap but the .zip will replace your corrupted files. I recommend you save everthing as soon as it boots and yhen do a clean install of whatever ROM you want even if its stock.
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
reinstalled stock ROM, stuck on logo
I recently got an AT&T note 2. I rooted and installed cwm recovery. I tried installing Android Revolution HD 5.0 after running their superwipe script. Everything went smoothly except the SIM was not recognized. I couldn't get it to work so I tried 2 other ROMs and I had the same issue. I decided to go back to stock and wait for Cyanogen to release a ROM.
The issue I am having now is that the stock ROM downloaded from http://forum.xda-developers.com/showthread.php?t=2004650 and another stock ROM (KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.tar) won't boot. I can successfully push them to the phone from Odin, but then they reboot and get stuck on the Samsung logo. The phone doesn't give any error messages, no strange leds on, no reboots, it just sits there with the Samsung logo pulsing. I can still boot into the download mode (vol down, home, power).
Any advice on how to get to a functoning ROM? At this point I don't care if it is stock or custom, I just need something that works. Any help would be greatly appreciated!
cdt710 said:
I recently got an AT&T note 2. I rooted and installed cwm recovery. I tried installing Android Revolution HD 5.0 after running their superwipe script. Everything went smoothly except the SIM was not recognized. I couldn't get it to work so I tried 2 other ROMs and I had the same issue. I decided to go back to stock and wait for Cyanogen to release a ROM.
The issue I am having now is that the stock ROM downloaded from http://forum.xda-developers.com/showthread.php?t=2004650 and another stock ROM (KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.tar) won't boot. I can successfully push them to the phone from Odin, but then they reboot and get stuck on the Samsung logo. The phone doesn't give any error messages, no strange leds on, no reboots, it just sits there with the Samsung logo pulsing. I can still boot into the download mode (vol down, home, power).
Any advice on how to get to a functoning ROM? At this point I don't care if it is stock or custom, I just need something that works. Any help would be greatly appreciated!
Click to expand...
Click to collapse
You should only flash ROMs from the "AT&T Galaxy Note II Android Development" section. I think Revolution HD is not an AT&T ROM, I don't know about the other ROMs you flashed (as you didn't say what they where). Those ROMs probably flash a non AT&T compatible radio on you phone. You should read and re-read and make sure you know what to do and what ROM can can flash before you start flashing.
Do you have a custom recovery installed, CWM or TWRP? Have you tried using a different computer and different cable?
Maybe try flashing the AT&T modem and them a correct ROM and see if that helps. Honestly, I'm not sure how to help you beyond that.
Good luck...
Back up and running
RojasTKD said:
You should only flash ROMs from the "AT&T Galaxy Note II Android Development" section. I think Revolution HD is not an AT&T ROM, I don't know about the other ROMs you flashed (as you didn't say what they where). Those ROMs probably flash a non AT&T compatible radio on you phone. You should read and re-read and make sure you know what to do and what ROM can can flash before you start flashing.
Do you have a custom recovery installed, CWM or TWRP? Have you tried using a different computer and different cable?
Maybe try flashing the AT&T modem and them a correct ROM and see if that helps. Honestly, I'm not sure how to help you beyond that.
Good luck...
Click to expand...
Click to collapse
I was able to get into the cwm recovery and load a new ROM onto the external SD card, then install it. I went with the Jedi ROM this time and it worked. I think you are correct that I was using ROMs for the wrong version of the phone. Everything is up and running and I have full functionality. Thanks for the tip!
cdt710 said:
I was able to get into the cwm recovery and load a new ROM onto the external SD card, then install it. I went with the Jedi ROM this time and it worked. I think you are correct that I was using ROMs for the wrong version of the phone. Everything is up and running and I have full functionality. Thanks for the tip!
Click to expand...
Click to collapse
Excellent, glad you were able to get it working.
Enjoy!
cdt710 said:
I was able to get into the cwm recovery and load a new ROM onto the external SD card, then install it. I went with the Jedi ROM this time and it worked. I think you are correct that I was using ROMs for the wrong version of the phone. Everything is up and running and I have full functionality. Thanks for the tip!
Click to expand...
Click to collapse
get yourself a jig dude, if you were really stuck you could have just put that badboy in and it would take you to dl mode, from there you could have odin'd yourself anywhere you wanted to. A thought for next time you get yourself into a situation you think isn't recoverable.
if you are a in a bloop you can usually get to recovery and from there sort yourself out. I know you are ok now, but this may still help someone else.
A jig is like a condom... protection even if you think you don't need it, you should prolly use it.
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 brought my phone in to have the charger port replaced. It worked fine ad then all of a sudden the phone boots up, stays booted for a minute and then reboots. also the screen is unresponsive.
I have used a gnex kit to get into CWM and erase cache and dalvik cache and fix permission and the problem is not resolved.
with out the gnex kit i can't even get into CWM and all i get is a little droid guy with an open stomach hatch with a red mark.
i would erase all data and factory reset as a last option but i have some work photos on the device that are extremely important for me to extract. I should also mention that with the CWM kit I am unable to find the files I wish to pull yet for the few seconds I am able to boot into android my photos are there in the album.
can someone please help me find a way to extract those files so I can try to wipe the device and move on?
cardozanick said:
I brought my phone in to have the charger port replaced. It worked fine ad then all of a sudden the phone boots up, stays booted for a minute and then reboots. also the screen is unresponsive.
I have used a gnex kit to get into CWM and erase cache and dalvik cache and fix permission and the problem is not resolved.
with out the gnex kit i can't even get into CWM and all i get is a little droid guy with an open stomach hatch with a red mark.
i would erase all data and factory reset as a last option but i have some work photos on the device that are extremely important for me to extract. I should also mention that with the CWM kit I am unable to find the files I wish to pull yet for the few seconds I am able to boot into android my photos are there in the album.
can someone please help me find a way to extract those files so I can try to wipe the device and move on?
Click to expand...
Click to collapse
With factory reset your sdcard will not be touched. You will have all your files (unless youre in stock recovery I think). You can use adb pull /sdcard/ to get all youre files.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
With factory reset your sdcard will not be touched. You will have all your files (unless youre in stock recovery I think). You can use adb pull /sdcard/ to get all youre files.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
so what you're saying is if I boot into CWM with the kit, do a factory reset, all my photos will be there? can you please elaborate?
cardozanick said:
so what you're saying is if I boot into CWM with the kit, do a factory reset, all my photos will be there? can you please elaborate?
Click to expand...
Click to collapse
Yes that is correct. You can wipe everything as long as you dont wipe /sdcard. I am not a 100% sure since you are on stock but I know sure for 99%. Google is your friend
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Yes that is correct. You can wipe everything as long as you dont wipe /sdcard. I am not a 100% sure since you are on stock but I know sure for 99%. Google is your friend
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Alright,
alright, we have 50% success!
I was able to get all the files off that I was looking to get, albeit during 20 second intervals in which the phone would allow me to before rebooting....
which brings me to my next point - Phone is stuck in bootloop after following (successfully) this guide to flash stock and unroot which, needless to say, seems strange to me.
Now I supposedly have a fully formatted i9250 maguro with a fresh flash of stock running and i'm stuck in a boot loop which if i leave sitting long enough will eventually get to the "Welcome" [choose your language] screen with an unresponsive display panel until it reboots after about 30 seconds.
please help.
EDIT: I flashed the Factory Image Android 4.2.2 (JDQ39) and still stuck in bootloop with unresponsive screen. maybe this is better as a paperweight??
cardozanick said:
Alright,
alright, we have 50% success!
I was able to get all the files off that I was looking to get, albeit during 20 second intervals in which the phone would allow me to before rebooting....
which brings me to my next point - Phone is stuck in bootloop after following (successfully) this guide to flash stock and unroot which, needless to say, seems strange to me.
Now I supposedly have a fully formatted i9250 maguro with a fresh flash of stock running and i'm stuck in a boot loop which if i leave sitting long enough will eventually get to the "Welcome" [choose your language] screen with an unresponsive display panel until it reboots after about 30 seconds.
please help.
EDIT: I flashed the Factory Image Android 4.2.2 (JDQ39) and still stuck in bootloop with unresponsive screen. maybe this is better as a paperweight??
Click to expand...
Click to collapse
Thats strange. But you have your files and you are on completely stock unrooted. If you still have warranty you can send it back. Maybe you can try this: http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop
Sent from my Galaxy Nexus using XDA Premium HD app
Strange Fix reveals deeper issue
good news and bad news
Alright, so I have swapped the motherboard with an old gnex i had laying around that has a broken screen that wouldn't turn on at all..
I found out that the motherboard on the old phone must be dead because it won't work in the newer phone so I put the guts of the newer on into the broken screen phone and it worked perfectly - albeit with a huge crack in it. so i then thought maybe the issue was solved and put the guts that worked back into the original phone and it is unresponsive and reboots... I've come to the conclusion that the screen is the issue on that device.
but is this fixable??? i have taken the whole thing apart and can't see how that screen could be shorting the device and cause it to reboot nor can i understand why it wouldn't be responsive to the touch for no reason.
anybody have a clue how i can fix that?