Hello, Ive searched for an answer to this but couldnt find one.
Whenever I flash a rom I always get super fast battery drainage, and random shutoffs every 5 minutes. What is the deal?
This is what I used to root/load the custom rom on my phone.
http://forum.xda-developers.com/showthread.php?t=849028
How many roms have you flashed? Have you tried reflashing the same rom?
Powered by Axura with a dash of Voodoo
GreggoryD502 said:
How many roms have you flashed? Have you tried reflashing the same rom?
Powered by Axura with a dash of Voodoo
Click to expand...
Click to collapse
I have tried with with the newest versions of Aurxora and Nero. And yes I flashed the nero twice and it still has super fast battery drainage and a lot of shutdowns.
Flonkas said:
Hello, Ive searched for an answer to this but couldnt find one.
Whenever I flash a rom I always get super fast battery drainage, and random shutoffs every 5 minutes. What is the deal?
This is what I used to root/load the custom rom on my phone.
http://forum.xda-developers.com/showthread.php?t=849028
Click to expand...
Click to collapse
I KNOW!
does your phone just soft reboot every 5 minutes? like it doesn't show the whole vibrant screen, just the tmobile and stuff.
i had this problem when i was on stock, and i called tmobile (didnt know about xda yet) and they told me to go boot into recovery, then choose... clear user data or something, and that erased everything(except sim and sd card ofc.) and fixed it, try that?
else, start using ODIN, to fix possibly every non-hardware issue.
xriderx66 said:
I KNOW!
does your phone just soft reboot every 5 minutes? like it doesn't show the whole vibrant screen, just the tmobile and stuff.
i had this problem when i was on stock, and i called tmobile (didnt know about xda yet) and they told me to go boot into recovery, then choose... clear user data or something, and that erased everything(except sim and sd card ofc.) and fixed it, try that?
else, start using ODIN, to fix possibly every non-hardware issue.
Click to expand...
Click to collapse
I get a full on shutdown. Does not start back up.
Flonkas said:
I get a full on shutdown. Does not start back up.
Click to expand...
Click to collapse
if you are able to get into download mode, i suggest you odin back is the best answer i can give you, and if that doesn't solve your problem, call tmobile and return it for another new/refurb(most likely a refurb)
xriderx66 said:
if you are able to get into download mode, i suggest you odin back is the best answer i can give you, and if that doesn't solve your problem, call tmobile and return it for another new/refurb(most likely a refurb)
Click to expand...
Click to collapse
I do not think theres a problem with the phone because this only started happening once I installed a custom rom. Im thinking I just messed up somewhere.
Flonkas said:
I do not think theres a problem with the phone because this only started happening once I installed a custom rom. Im thinking I just messed up somewhere.
Click to expand...
Click to collapse
every once in a while you must odin back to stock and start flashing, because if you keep flashing roms over and over without odin, they all leave behind a little bit of data, which keeps bugging the new version you have, and so on.
Turn off phone, take battery out.
get a computer, get your usb cord.
take battery out
plug in usb to a turned on computer
after usb, hold ONLY AND BOTH volume buttons.
while holding the buttons put in the battery.
it should now show a android digging with a yellow sign.
if your there, you can fix it, if not, try a few times again, and if you absolutely cannot get it to do this, then you have a hardware locked vibrant, which i don't know much about.
If you DO get on the download mode( yellow android digging)
go here: http://forum.xda-developers.com/showthread.php?t=771111
download the Samsung Drivers if you don't already have them, you may need to re-do everything i said up there again so the computer regcognizes your phone.
Your going to need to download a program called ODIN.
found here: http://forum.xda-developers.com/showpost.php?p=8863820&postcount=138
open odin while your phones in download mode, on the top does it say COM3, COM5 etc? any number at end is good, but if it says COM it means the computer has recognized your phone thats a good job.
now you need to download 2-3 more files which will take you to stock, unrooted everything like that.
for the sake of time, i have to leave, but i found you a thread with exact instructions as mine, and with other helpful things as well.
http://forum.xda-developers.com/showthread.php?t=799105
Well... if you're definition of battery drain extremely fast is 10-12 hours then that's all you're going to get, deal with it. But if somehow you're getting like 4-6 around this area that's not normal.
Make sure you have GPS and WIFI OFF and bluetooth also when you're not using them.
Use titanium backup pro to freeze all the apps you don't use, especially preinstalled apps like wifi calling and the like.
Or, wipe battery stats and recondition or use this link to flash stock rom and this should fix any unknown problems
http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
Related
Sorry for making this long. I am totally flummoxed/sad/angry.
My phone has been hard bricked for the 3rd time in a matter of 8-10 days. My vibrant was a hardware locked one when I first got it. Let me explain a brief history of what flashes have been performed on my vibrant:
1) To unlock my Vibrant I flashed this:
http://forum.xda-developers.com/showthread.php?t=785201
Result: This helped me get Download mode working by pressing Vol Up + Power. But recovery mode was no-go. One thing to notice was that on boot, the screen now says GT-i9000 for a few seconds and then a Vibrant screen for few more seconds.
2) Hence flashed this, http://forum.xda-developers.com/showthread.php?t=804305
Result: Bricked. Phone wouldn't boot. Completely dead. Got it fixed by paying $50. Got it back with stock JFD, Download mode working.
3) Stock JFD, worked fine. Flashed Bionix Fusion final 1.2, Obsidian V2.
Result: All fine. No issues.
4) Flashed Axura 2.0.5
Result: Bricked. Phone dead again. Wouldn't even turn ON. I thought perhaps some random issue must have happened which resulted in bricking my Vibrant. I got it fixed from a local mobile repair-shop who probably jtagged it (or used RIFF box to flash bootloader).
Got it fixed again. Got it back with Stock JFD, Download mode working.
5)First thing I try is flashing Axura.
Result: Got the phone back today. Don't know why, but the first thing I did after getting the phone was rooting JFD, installing ClockWork, booting in CW recovery and flashing Axura again. Guess what, it's bricked again. Wow. Unbelievable. Anyone has any idea whats going on?
Sounds like the axura file your using may be bad. If bionex worked then obviously it must have something to do with axura. Are you wiping before you flash? Do you have any lag fixes on?
it could be a bad copy of axura as stated y not try to odin back to stock ur self maybe it could be something that ur doin wrong when flashing axura... i did brick my fone once but i odin back to stock n fixed everything
Is your phone soft bricked? Does it turn on at all?
Ya, I'd double check the images your flashing. Have you tried another rom yet?
PS. It's a soft brick, which Vibrants are easily recoverable from. A hard brick means you get nothing, it's a useful as a... brick. You can sometimes get back from those with JTAG interfacing.
I think its Axura 2.5.. It keeps doing it to my phone too...
You must really want that ROM to keep trying it after it had bricked you twice.
pmartof said:
Sounds like the axura file your using may be bad. If bionex worked then obviously it must have something to do with axura. Are you wiping before you flash? Do you have any lag fixes on?
Click to expand...
Click to collapse
No. I do not wipe anything before flashing. And no lag fixes on. Directly flashing from JFD stock.
pmartof said:
Is your phone soft bricked? Does it turn on at all?
Click to expand...
Click to collapse
cwoodworth said:
Ya, I'd double check the images your flashing. Have you tried another rom yet?
PS. It's a soft brick, which Vibrants are easily recoverable from. A hard brick means you get nothing, it's a useful as a... brick. You can sometimes get back from those with JTAG interfacing.
Click to expand...
Click to collapse
I believe it is called a hard brick if you need to JTAG it to get back to life.
JD76 said:
I think its Axura 2.5.. It keeps doing it to my phone too...
Click to expand...
Click to collapse
How did you fix it then?
ColorNapkin said:
You must really want that ROM to keep trying it after it had bricked you twice.
Click to expand...
Click to collapse
First time it was bricked when I flashed 3 button fix. And It's not that. Just wanted to double check if it is the ROM or something wrong happened first time around.
Pat123 said:
First time it was bricked when I flashed 3 button fix. And It's not that. Just wanted to double check if it is the ROM or something wrong happened first time around.
Click to expand...
Click to collapse
I'd say avoid the ROM, if others don't cause the issue. Does Axura include a kernel? You could try it replacing the kernel in the package with a different one before flashing.
Invest in the JIG IMO
http://forum.xda-developers.com/showthread.php?t=819551
^^Already done that. But it seems that jig helps only people who cannot get into download mode but are soft-bricked (i.e. the display is not completely dead)! Anyways, have given the phone for repair yet again! Planning to sell this piece of **** soon and get G2!
I think you need to stay away from fiddling with your phone.
Master provides md5 sum for every ROM he offers, if download is corrupt the md5 sum won't match and you just don't flash the ROM.
I am having the same problem, my vibrant doesnt turn on, can you point me to where can i have it repaired?? my vibrant doesnt turn on anymore after flashing axura....
JD76 said:
I think its Axura 2.5.. It keeps doing it to my phone too...
Click to expand...
Click to collapse
There is no such thing as Axura 2.5.. We are still on Axura 2.2 (2.2.7.1 to be specific)
OP, I would make sure your .zip isn't corrupt.
Curious, If you are in India, do they use the Vibrant there, and do they have the same configuration as the USA Vibrant?
Assuming it is the same, when you download a Rom check the the exact quantity of bytes make sure they equal. Often when loading on the phone the phone will compile the upper number to a different sum, the lower number Must be the same.
Re-download what ever rom you want and make sure it matches in sum.
The problem appears not to be the ROM there is something that is happening/doing that is by the user
If you get a G2 you won't do much better. Vibrant is one of the toughest phones to hard brick. You won't last a day with a G2...the problem is not the phone, it's you.
Moved of: Samsung Vibrant > Vibrant General
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
I partitioned my SD card using ROM Manager, turned the phone off and got a black screen with lit keys. So, I read around and was told to use ODIN to reflash the stock TMO build, so I did. Now, Im getting the TMO logo and Galaxy S screen, but I get a black screen still.
I cannot get into download mode. I vol - and power and I get the Vibrant logo, then it goes back off. Even when plugged it, I get the batt charging animation, then back to the Vibrant screen.
I tried to push the update.zip to the SD card through ADB, but I get a permission denied message, meaning the root was killed.
So, is this phone pretty much screwed? I cant think of any other way to get it going outside of moving the update.zip to the sd card by a 3rd party measure i.e card reader/another phone
dude that's not even close to a brick as the phone is still responsive somehow..
do this:
1. pull out battery wait 5-10secs
2. connect USB to computer and phone
3. hold down the vol +/- buttons
4. plug in battery
5. you should be in download mode now
6. do what you gotta do with ODIN
good luck
Dont use that method to get to DL mode . Do it this way . First turn off your phone , then plug the usb cable into your computer ONLY . Next hold both volume buttons and plug the micro usb into your phone . Also use odin v1.3 and flash the rom of your preference .
Edit : xtone beat me to the punch
trill12 said:
I partitioned my SD card using ROM Manager, turned the phone off and got a black screen with lit keys. So, I read around and was told to use ODIN to reflash the stock TMO build, so I did. Now, Im getting the TMO logo and Galaxy S screen, but I get a black screen still.
I cannot get into download mode. I vol - and power and I get the Vibrant logo, then it goes back off. Even when plugged it, I get the batt charging animation, then back to the Vibrant screen.
I tried to push the update.zip to the SD card through ADB, but I get a permission denied message, meaning the root was killed.
So, is this phone pretty much screwed? I cant think of any other way to get it going outside of moving the update.zip to the sd card by a 3rd party measure i.e card reader/another phone
Click to expand...
Click to collapse
Yes using ROM Manager to repartition your phone will create the "soft-brick" you are experiencing. But as one person has already noted, this can pretty much be recovered using ODIN.
Definitely follow the advice given in Posts 2 and 3 of this thread to get into Download mode. If you're not getting the desired results using ODIN, what settings are you using? For example, what are the names of the .pit and .tar files you are using? Did you check or leave unchecked the "re-partition" option?
Sorry for the noobery. Im usually good at this.
Well, I was able to get into download mode and get ODIN to run, but im getting a MBD checksum error when I boot into recovery.
And I cannot install CWM through the market because my Application Storage is at 0.00B for some reason.
trill12 said:
Sorry for the noobery. Im usually good at this.
Well, I was able to get into download mode and get ODIN to run, but im getting a MBD checksum error when I boot into recovery.
And I cannot install CWM through the market because my Application Storage is at 0.00B for some reason.
Click to expand...
Click to collapse
What ROM did you flash. You might want to perform a factory reset and then flash the stock JFD ROM and see if that fixes your problem.
Good luck.
Oh this is a nightmare.... exactly what happened to me.
I'll be honest, I tried and tried and tried all sorts of stuff and somehow I got it back reading again.
I would ODIN to Eugenes Froyo that doesn't brick and see where that gets you. Thread is in developers section and I am pretty sure that's what got me back working but follow ALL the instructions. With no application room I couldn't push, unistall, install ect...
blizzard1017 said:
Oh this is a nightmare.... exactly what happened to me.
I'll be honest, I tried and tried and tried all sorts of stuff and somehow I got it back reading again.
I would ODIN to Eugenes Froyo that doesn't brick and see where that gets you. Thread is in developers section and I am pretty sure that's what got me back working but follow ALL the instructions. With no application room I couldn't push, unistall, install ect...
Click to expand...
Click to collapse
That's only needed if he flashed a rom with the wrong kernel or if he flashed a rom without disabling voodoo .
Sent from my SGH-T959 using XDA App
Just get to DL mode as xtone and I stated in post 2 & 3 . Then flashed to JFD with odin v1.3 and click the repartition box in odin and you'll be fine .
Sent from my SGH-T959 using XDA App
I had this problem for the last two days, but I found a way to fix it thanks to a user (whom I don't know the name of)
I did this to go back to stock firmware (JFD), make sure you have that downloaded.
Look for Eugene's Galaxy S Froyo PDA, for the i9000, not the Vibrant. Flash it through Odin with the 512 pit file. It's not going to boot up but take you to recovery mode instead, and it's going to remap your Volume buttons, but you can still get into DL mode (up is now down, and vice versa but whatever)
Now Odin back to stock, using the same 512 pit and there you go! Should boot up with no problem. Now you can redo everything, but remember to never partition through ROM Manager ever again!
Sent from my SGH-T959 using XDA App
Is there a link you could provide him?
AgentFour20 said:
That's only needed if he flashed a rom with the wrong kernel or if he flashed a rom without disabling voodoo .
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
His exact symptoms happened to me when the noob in me decided to repartition in Rom Manager awhile back. I am just suggesting he uses this tool as an option. It's definitely a good tool to use regardless of how he got where he got.
something like this happened to a buddy of mine, i'm trying to fix it, but the guy was completely stock so it makes no sense... I've tried everything, and i cant seem to find eugenes files...
Mr.Duck said:
something like this happened to a buddy of mine, i'm trying to fix it, but the guy was completely stock so it makes no sense... I've tried everything, and i cant seem to find eugenes files...
Click to expand...
Click to collapse
Eugenes rom are on his new site www.eb-production.proboards.com
Sent from my SGH-T959 using XDA App
OK, I got it fixed. Heres how.
I was finally able to get into ODIN and flash Eugenes Froyo.
So, from there, I was getting an MD5 checksum error when Id try to get into recovery, and I couldnt install the ROM Manager from the Market
Well, upon inspection of a the Nero V3 build I had downloaded, there was a ROMManager.apk there. So I pushed it onto my phone, reflashed to CWR (had to do it about 3 times) and reinstalled Nero V3.
After installing the build, I was able to re-enable voodoo and its theres no more MD5 craziness when I access the Recovery
trill12 said:
OK, I got it fixed. Heres how.
I was finally able to get into ODIN and flash Eugenes Froyo.
So, from there, I was getting an MD5 checksum error when Id try to get into recovery, and I couldnt install the ROM Manager from the Market
Well, upon inspection of a the Nero V3 build I had downloaded, there was a ROMManager.apk there. So I pushed it onto my phone, reflashed to CWR (had to do it about 3 times) and reinstalled Nero V3.
After installing the build, I was able to re-enable voodoo and its theres no more MD5 craziness when I access the Recovery
Click to expand...
Click to collapse
So voodoo was the culprit . lmao
I dont remember you ever mentioning that . Any way glad you figured it out and have your phone back .
AgentFour20 said:
So voodoo was the culprit . lmao
I dont remember you ever mentioning that . Any way glad you figured it out and have your phone back .
Click to expand...
Click to collapse
Apparently. Completely forgot I attempted to enable it. I was freaked all the way out trying to repair the damn thing.
So last night I decided to play around with my phone since I had been running stock ICS for a while. I still had some battery issues so was going to try out a few roms and see how they were all doing these days. I started off by flashing a siyah kernel using odin to get root. Everything went smooth. I then installed ROM manager and stupidly tried to flash CWM from within the app. The app completely froze and once I rebooted the phone would not boot correctly. I get the initial triangle bound galaxy s II screen but after that just a blank screen. Beyond that, the buttons and display flash ever so often very briefly but thats it. I could still get to download mode so I figured I would just use the "return to stock" thread to start over. Unfortunately I seem to have completely messed something up because I can't finish flashing anything, the computer beeps like I unplugged the USB cable and plugged it back in in the middle of anything that takes longer to flash than just a kernel and odin reports that it fails. When I used to just leave my phone plugged into my computer and it was at full charge it seemed to randomly do the same beeping as well. I think my next plan of action is to let the battery drain a bit and try to do a full flash (with bootloaders) and hope that it makes it all the way through without disconnecting as it seems to shut down the usb connection when at full battery for some reason.
In summary, I can get to download mode at this point, or a firmware failed to load screen. Ive tried various things with odin, heimdel and kies to no avail. Odin seems to have some marginal success except for the random disconnecting. Anyone have any advice for me (beyond trying to flash with the phone at around 50% battery or am I buying a Galaxy Nexus today?
Thanks in advance
If u can't get into cwm just flash a stock firmware from the download repository or from creepycrawlys sig. Odin should work fine in download mode regardless of what recovery rom manager installed. Make sure u have the latest drivers on your computer for the i777. Also I've found when I do the Odin flashes that the best way to get it to work is to start Odin with yer phone disconnected THEN connect it after Odin is started. Don't use rom manager in the future.
Sent from my SGH-I777 using Tapatalk 2
Please do not name your thread "Derp." I it is even less helpful than saying OMG HALP I BRICKEDED MAH PHONE PLZ HALP NAO.
Sent from my SGH-I777 using Tapatalk 2
Thanks Phalanx, I will continue to pound away at it with Odin later tonight, I hope I am able to get a full flash in and will of course share what I find.
I will use more meaningful title's in the future Nick, not sure if I can edit this one but will look.
DigitalElement said:
So last night I decided to play around with my phone since I had been running stock ICS for a while. I still had some battery issues so was going to try out a few roms and see how they were all doing these days. I started off by flashing a siyah kernel using odin to get root. Everything went smooth. I then installed ROM manager and stupidly tried to flash CWM from within the app. The app completely froze and once I rebooted the phone would not boot correctly. I get the initial triangle bound galaxy s II screen but after that just a blank screen. Beyond that, the buttons and display flash ever so often very briefly but thats it. I could still get to download mode so I figured I would just use the "return to stock" thread to start over. Unfortunately I seem to have completely messed something up because I can't finish flashing anything, the computer beeps like I unplugged the USB cable and plugged it back in in the middle of anything that takes longer to flash than just a kernel and odin reports that it fails. When I used to just leave my phone plugged into my computer and it was at full charge it seemed to randomly do the same beeping as well. I think my next plan of action is to let the battery drain a bit and try to do a full flash (with bootloaders) and hope that it makes it all the way through without disconnecting as it seems to shut down the usb connection when at full battery for some reason.
In summary, I can get to download mode at this point, or a firmware failed to load screen. Ive tried various things with odin, heimdel and kies to no avail. Odin seems to have some marginal success except for the random disconnecting. Anyone have any advice for me (beyond trying to flash with the phone at around 50% battery or am I buying a Galaxy Nexus today?
Thanks in advance
Click to expand...
Click to collapse
The random disconnecting sounds like either a bad cable or a bad USB port. Try to flash using a different USB cable...if that doesn't work, you may have a hardware issue.
mattdm said:
The random disconnecting sounds like either a bad cable or a bad USB port. Try to flash using a different USB cable...if that doesn't work, you may have a hardware issue.
Click to expand...
Click to collapse
Seems logical, I will try a different port and cable and see if I have better luck. Anybody have any suggestions on what package I should try first? Should I try one that includes the BLs or not? My end goal is going to be either cm9 or aokp.
DigitalElement said:
Seems logical, I will try a different port and cable and see if I have better luck. Anybody have any suggestions on what package I should try first? Should I try one that includes the BLs or not? My end goal is going to be either cm9 or aokp.
Click to expand...
Click to collapse
I would stay away from packages with bootloaders. Too easy to fully brick your phone. I would use the one creepyncrawly posted here. Make sure you read and follow the directions to avoid Brickbug. This will put you on rooted stock ICS. You should then be able to flash to your hearts content.
blutruck said:
I would stay away from packages with bootloaders. Too easy to fully brick your phone. I would use the one creepyncrawly posted here. Make sure you read and follow the directions to avoid Brickbug. This will put you on rooted stock ICS. You should then be able to flash to your hearts content.
Click to expand...
Click to collapse
I'd second this - if you get one of those random disconnects while flashing bootloaders, you could potentially be in a much bigger world of hurt...
Good news! I flashed with a different usb cable and port and it was able to complete successfully. Phone is up and running with the rooted ucle5 posted above.
I should have known to suspect layer 1 given my line of work...
Thanks again
DigitalElement said:
Good news! I flashed with a different usb cable and port and it was able to complete successfully. Phone is up and running with the rooted ucle5 posted above.
I should have known to suspect layer 1 given my line of work...
Thanks again
Click to expand...
Click to collapse
Glad it's working! Have fun flashing.
Nick281051 said:
Please do not name your thread "Derp." I it is even less helpful than saying OMG HALP I BRICKEDED MAH PHONE PLZ HALP NAO.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
The title was more helpful than your response.
DigitalElement said:
Good news! I flashed with a different usb cable and port and it was able to complete successfully. Phone is up and running with the rooted ucle5 posted above.
I should have known to suspect layer 1 given my line of work...
Thanks again
Click to expand...
Click to collapse
Glad to hear you are back up and running.
DigitalElement said:
I will use more meaningful title's in the future Nick, not sure if I can edit this one but will look.
Click to expand...
Click to collapse
ZeroIsntTheHero said:
The title was more helpful than your response.
Click to expand...
Click to collapse
Actually it looks like nicks response helped the op realize that the title of your posts are important, so that others having the same problem will see and maybe get the help they need without starting a new thread.
Shot straight outta my Taskatooned SGH-I777 Rocketship
DigitalElement said:
... I then installed ROM manager and stupidly tried to flash CWM from within the app...
Click to expand...
Click to collapse
I have read several times that you should not use ROM manager on the SGS2. I'm surprised nobody has mentioned this to the OP, so I'm starting to wonder if I misunderstood something?
Sent from my SGH-I777 using xda app-developers app
wgoldfarb said:
I have read several times that you should not use ROM manager on the SGS2. I'm surprised nobody has mentioned this to the OP, so I'm starting to wonder if I misunderstood something?
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
No, ROM manager is still one of the worst things you could use on an I777. Stay away from it. I believe OP realized his mistake after the fact, he included it so that others could better answer his question and help him get his phone up and running again.
ZeroIsntTheHero said:
The title was more helpful than your response.
Click to expand...
Click to collapse
No. Just no. Titles like that (no offense to op he said in the future he'll name them more appropriately) don't help us help them. It just means we have to dig harder to help find what the problem is.
Sent from my SGH-I777 using Tapatalk 2
I recently tried installing the LiquidSmooth. First, I installed the older version, and I tried to upgrade the ROM. I'm not sure what happened, but when I installed from ZIP on CWM, it looked fine and I tried rebooting and it turned off and never turned back on. It shows no response whatsoever, black screen, and the only slight response that it would show is the red charging light when I plug it in without a battery in. My computer will recognize that something is plugged in by USB but nothing shows up in Windows Explorer. I don't have a warranty, so any advice would be useful.
predstitans3797 said:
I recently tried installing the LiquidSmooth. First, I installed the older version, and I tried to upgrade the ROM. I'm not sure what happened, but when I installed from ZIP on CWM, it looked fine and I tried rebooting and it turned off and never turned back on. It shows no response whatsoever, black screen, and the only slight response that it would show is the red charging light when I plug it in without a battery in. My computer will recognize that something is plugged in by USB but nothing shows up in Windows Explorer. I don't have a warranty, so any advice would be useful.
Click to expand...
Click to collapse
is it still entering download mode?
sriram231092 said:
is it still entering download mode?
Click to expand...
Click to collapse
Completely unresponsive, black screen all the way, no start-up screen, nothing.
I'm able to get a warranty replacement, but it would still be great to know how to fix it for future reference.
predstitans3797 said:
Completely unresponsive, black screen all the way, no start-up screen, nothing.
I'm able to get a warranty replacement, but it would still be great to know how to fix it for future reference.
Click to expand...
Click to collapse
Its a very simple solution to your problem. Stop using CWM to flash ROMs.
Heres what you to fix your phone and follow it closely other wise you will have a paper weight. Pull out your battery for 5 mins. Pull out your sim card. After 5 mins, reinstall your battery, don't worry about the sim. See if it turns on. If it does, then you can flash using the download method and this method only. Flash a rooted stock rom to your phone. Get triangle and rest the counter. Install a stock recovery and have fun. No need for those other ROMS, they are buggy and have caused issues with so many phones.
If that doesn't work, get the Samsung GS3 toolkit and try with that. It will put your phone in download mode automatically and may help you out.
TheStrokerace said:
Its a very simple solution to your problem. Stop using CWM to flash ROMs.
Heres what you to fix your phone and follow it closely other wise you will have a paper weight. Pull out your battery for 5 mins. Pull out your sim card. After 5 mins, reinstall your battery, don't worry about the sim. See if it turns on. If it does, then you can flash using the download method and this method only. Flash a rooted stock rom to your phone. Get triangle and rest the counter. Install a stock recovery and have fun. No need for those other ROMS, they are buggy and have caused issues with so many phones.
If that doesn't work, get the Samsung GS3 toolkit and try with that. It will put your phone in download mode automatically and may help you out.
Click to expand...
Click to collapse
To be fair, the problems after flashing a rom are rarely caused by the rom itself..
It's usually just a noob who doesnt know the proper "way" to flash stuff.. Nothing wrong with flashing with CWM.
Etirel said:
To be fair, the problems after flashing a rom are rarely caused by the rom itself..
It's usually just a noob who doesnt know the proper "way" to flash stuff.. Nothing wrong with flashing with CWM.
Click to expand...
Click to collapse
I would say about 75% of the issues I have read, people have used CWM to flash a ROM or used a modified ROM of some sort. I had one that said it was simular to stock, it lasted on my phone 2 days. It drove me nuts, phone sluggish and battery drain. Flashed a rooted stock ROM and everything is great. Can do OTA updates with it. Have SU and can run linux on it. Don't have any custom recovery on it as its not needed. ANd I can still get warranty on the phone.
TheStrokerace said:
I would say about 75% of the issues I have read, people have used CWM to flash a ROM or used a modified ROM of some sort. I had one that said it was simular to stock, it lasted on my phone 2 days. It drove me nuts, phone sluggish and battery drain. Flashed a rooted stock ROM and everything is great. Can do OTA updates with it. Have SU and can run linux on it. Don't have any custom recovery on it as its not needed. ANd I can still get warranty on the phone.
Click to expand...
Click to collapse
once you are rooted, there's no warranty! btw how did you flash a custom rom with no CWM recovery? odin flashable?
sriram231092 said:
once you are rooted, there's no warranty! btw how did you flash a custom rom with no CWM recovery? odin flashable?
Click to expand...
Click to collapse
That is why you use triangle to reset the counter and an a rooted stock rom. Odin is the only way to flash a rom, much safer and alot easier. takes 1 min todo. Or you can get the samsung toolkit and use it. CWM is or shouldn't be used for updating a ROM, Its called recovery for a reason. And you don't have to worry about your SD card crapping out.
TheStrokerace said:
Odin is the only way to flash a rom, much safer and alot easier. takes 1 min todo. Or you can get the samsung toolkit and use it. CWM is or shouldn't be used for updating a ROM
Click to expand...
Click to collapse
That's nonsense
Glebun said:
That's nonsense
Click to expand...
Click to collapse
100% agree CWM is not the major cause of SDS and post that says it is is complete and utter noob nonsense .
jje
TheStrokerace said:
Its a very simple solution to your problem. Stop using CWM to flash ROMs.
Heres what you to fix your phone and follow it closely other wise you will have a paper weight. Pull out your battery for 5 mins. Pull out your sim card. After 5 mins, reinstall your battery, don't worry about the sim. See if it turns on. If it does, then you can flash using the download method and this method only. Flash a rooted stock rom to your phone. Get triangle and rest the counter. Install a stock recovery and have fun. No need for those other ROMS, they are buggy and have caused issues with so many phones.
If that doesn't work, get the Samsung GS3 toolkit and try with that. It will put your phone in download mode automatically and may help you out.
Click to expand...
Click to collapse
Sorry but this is straight bullsh*t!
This is your personal opninion. Guess what I use a Custom ROM and it works just fine. It`s faster than a Stock Sammy ROM. Everyone who flashes a ROM should always read what works and what doesn`t work. ROMs that are based on AOSP like the CyanogenMod are easily Daily Driver material. So I don`t know what you are talking about here.
TheStrokerace said:
I would say about 75% of the issues I have read, people have used CWM to flash a ROM or used a modified ROM of some sort. I had one that said it was simular to stock, it lasted on my phone 2 days. It drove me nuts, phone sluggish and battery drain. Flashed a rooted stock ROM and everything is great. Can do OTA updates with it. Have SU and can run linux on it. Don't have any custom recovery on it as its not needed. ANd I can still get warranty on the phone.
Click to expand...
Click to collapse
Funny how you seem to have problems with Custom ROMs while hundreds of thousands of people use them and are happy with them.
TheStrokerace said:
That is why you use triangle to reset the counter and an a rooted stock rom. Odin is the only way to flash a rom, much safer and alot easier. takes 1 min todo. Or you can get the samsung toolkit and use it. CWM is or shouldn't be used for updating a ROM, Its called recovery for a reason. And you don't have to worry about your SD card crapping out.
Click to expand...
Click to collapse
This is another case of straight false information and also your personal opinion that you state as fact. My opinion is that there are many things that could go wrong when flashing Stuff with Odin because 1. Your computer could screw up during the flashing process. 2. You could by accident disconnect the USB cable from your phone during the flashing process and and and. That`s why I only use Odin when I absolutely have to. I flashed ROMs with CWM Recovery many times and it worked without a problem (less stuff that could go wrong). I have rarely heard of cases where people screwed up their phones while flashing with CWM BUT I have heard a lot of cases where people screwed up their phones with Odin.
Hi there i have a SGH-i717 with AT&T 2.3.4 Stock installed..I did have Cyanogen 10.1 and Avatar all installed in the last 72hrs..I have wiped all that and did a return to the stock AT&T thinking that my HOME keys would return..NO LUCK..The problems started about 4 days ago when the phone started turning itself off automatically..I changed custom ROM's etc to try and fix the problem..then i read to use Kies to try and do a Firmware Upgrade and Initialization to go back to the start when i first got the phone..But now Kies will NOT recognise the phone..I have re-installed drives, Kies to no avail..Any tips ?
Also someone suggested to flash this kernel h0tcakez-JB-Kernel-v2.3.5-ALT but when i tried through system recovery is gives a falied error..
I have nothing on the phone i need to worry about loosing...Cheers
kakadu44 said:
Hi there i have a SGH-i717 with AT&T 2.3.4 Stock installed..I did have Cyanogen 10.1 and Avatar all installed in the last 72hrs..I have wiped all that and did a return to the stock AT&T thinking that my HOME keys would return..NO LUCK..The problems started about 4 days ago when the phone started turning itself off automatically..I changed custom ROM's etc to try and fix the problem..then i read to use Kies to try and do a Firmware Upgrade and Initialization to go back to the start when i first got the phone..But now Kies will NOT recognise the phone..I have re-installed drives, Kies to no avail..Any tips ?
Also someone suggested to flash this kernel h0tcakez-JB-Kernel-v2.3.5-ALT but when i tried through system recovery is gives a falied error..
I have nothing on the phone i need to worry about loosing...Cheers
Click to expand...
Click to collapse
If you are on stock 2.3.4 and tried to flash that kernel .. that is why it failed .. it would be the wrong kernel for that rom. Did you flash a stock rom in recovery? If so then I would suggest using oden to return to stock . then see what you end up with.
SGH-i717 Home Keys not working
Bubbajoe40356 said:
If you are on stock 2.3.4 and tried to flash that kernel .. that is why it failed .. it would be the wrong kernel for that rom. Did you flash a stock rom in recovery? If so then I would suggest using oden to return to stock . then see what you end up with.
Click to expand...
Click to collapse
Thanx for you reply..I did however flash stock 2.3.4 from oden..I deleted everything in recovery then went to oden and flashed the stock rom..Should i unroot/unbrick flash from oden?
That article about returning to original settings in Kies seems to make sense except for the fact that i cannot get Kies to recognise the phone...
Are we talking about Software ou Hardare issue in your opinion?
Cheers
Could be a hardware issue. Try this ... Put the phone into download mode then connect to the pc. Use the cable that came with the phone. Also use a port on the back of the pc ..not a hub. Then open kies and do the emergency firmware update.
Also ... When you used Odin to go to stock ..you installed the 3e recovery ..that's why it failed to flash. Which is a good thing. That kennel would have boot looped you.
Sent from my Big Ass Outlaw Phone
SGH-i717 Home Keys not working
Bubbajoe40356 said:
Could be a hardware issue. Try this ... Put the phone into download mode then connect to the pc. Use the cable that came with the phone. Also use a port on the back of the pc ..not a hub. Then open kies and do the emergency firmware update.
Also ... When you used Odin to go to stock ..you installed the 3e recovery ..that's why it failed to flash. Which is a good thing. That kennel would have boot looped you.
Sent from my Big Ass Outlaw Phone
Click to expand...
Click to collapse
Okay i installed from ODIN Stock 2.3.4.....I dont have a port on the back of the PC to use as i only have a Laptop...Kies will not recognise the phone..Even when the phone is at Stock it takes soooo long to boot up..approx 2 mins..can i not run the emergency firmware update from ODEN? If so where can i find the software please..
Also even when i go into recovery mode it shows error signs..it wont let me wipe cache or wipe data/factory reset..
cheers
kakadu44 said:
Okay i installed from ODIN Stock 2.3.4.....I dont have a port on the back of the PC to use as i only have a Laptop...Kies will not recognise the phone..Even when the phone is at Stock it takes soooo long to boot up..approx 2 mins..can i not run the emergency firmware update from ODEN? If so where can i find the software please..
Also even when i go into recovery mode it shows error signs..it wont let me wipe cache or wipe data/factory reset..
cheers
Click to expand...
Click to collapse
The lap top is fine. Emergency firmware is through kies and not Odin. You need download mode ... Not recovery.
Sent from my Big Ass Outlaw Phone
Bubbajoe40356 said:
The lap top is fine. Emergency firmware is through kies and not Odin. You need download mode ... Not recovery.
Sent from my Big Ass Outlaw Phone
Click to expand...
Click to collapse
It will not recognise the phone in KIES!!!!! i have uninstalled USB drivers and re-installed and still it will not recognise the phone..Is there USB debugging in Stock 2.3.6? If so where do i find it in Settings pls? thanx
kakadu44 said:
It will not recognise the phone in KIES!!!!! i have uninstalled USB drivers and re-installed and still it will not recognise the phone..Is there USB debugging in Stock 2.3.6? If so where do i find it in Settings pls? thanx
Click to expand...
Click to collapse
Please can you advise me what is the best way to WIPE my phone of ALL my info to start over again, just like a complete wipe on my laptop..cheers
Have you tried here, briefmobile. com /exclusive-ucld3-ics-leak-for-the-att-galaxy-note
sp73smith said:
Have you tried here, briefmobile. com /exclusive-ucld3-ics-leak-for-the-att-galaxy-note
Click to expand...
Click to collapse
Hi there thanx for your answer..I have not tried at that site..this program will do what? COMPLETELY wipe my phone??cheers
It will, it completely erases everything. Replaces recovery and losses root. Very simple to use, I use it every other month.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
SGH-i717 HOME keys are not working...
sp73smith said:
It will, it completely erases everything. Replaces recovery and losses root. Very simple to use, I use it every other month.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Yep i used it..very good..But my original and main problem..Continues..NONE of my HOME keys are working..I fear that it is a Hardware issue with the SGH-i717..I guess i have to take it to Samsung for repair..Until someone else can give me a solution..I have tried everything and nothing has worked..No HOME keys..Cheers
Definitely not a hardware issue, there where some changes made IIRC in the kernel driver files, once flashed they prevented the homerow buttons from working normally, the only way I ever found to make them work right was to flash the Flappjaxxx alternate kernel series, let it boot, then return completely to stock!
If you dig around, FJ's alt kernel's are around here somewhere!
SGH-i717 HOME keys are not working...
Hammerfest said:
Definitely not a hardware issue, there where some changes made IIRC in the kernel driver files, once flashed they prevented the homerow buttons from working normally, the only way I ever found to make them work right was to flash the Flappjaxxx alternate kernel series, let it boot, then return completely to stock!
If you dig around, FJ's alt kernel's are around here somewhere!
Click to expand...
Click to collapse
Good morning, well i believe i have finally arrived at a possible solution..I have searched hi and low for these Flappjaxxx alternate kernel ..I came up with a daunting array of alternatives for the complete amatuer as i am..I appreciate that your time is precious but i do need some general direction what exactly i am searching for..I have found this one but to be quite honest i am not sure if i need this whole ROM or just the Flappjaxxx alternate kernel'a..
http://db.communityrelease.com/developer_display.asp?DeveloperID=11381
https://github.com/flappjaxxx/kernel_samsung_sghi717
Also when i do eventually obtain the Kernel that i am looking for can i use ODIN to flash it? I installed this ROM which i beleive to be stock already..You wrote that i need to return COMPLETELY to stock..What is that 2.3.6???
http://briefmobile.com/exclusive-ucld3-ics-leak-for-the-att-galaxy-note
I appreciate any further input you may be able to supple..regards kakadu44
kakadu44 said:
Good morning, well i believe i have finally arrived at a possible solution..I have searched hi and low for these Flappjaxxx alternate kernel ..I came up with a daunting array of alternatives for the complete amatuer as i am..I appreciate that your time is precious but i do need some general direction what exactly i am searching for..I have found this one but to be quite honest i am not sure if i need this whole ROM or just the Flappjaxxx alternate kernel'a..
http://db.communityrelease.com/developer_display.asp?DeveloperID=11381
https://github.com/flappjaxxx/kernel_samsung_sghi717
Also when i do eventually obtain the Kernel that i am looking for can i use ODIN to flash it? I installed this ROM which i beleive to be stock already..You wrote that i need to return COMPLETELY to stock..What is that 2.3.6???
http://briefmobile.com/exclusive-ucld3-ics-leak-for-the-att-galaxy-note
I appreciate any further input you may be able to supple..regards kakadu44
Click to expand...
Click to collapse
My work schedule is absolute hell, and due to people flaking at work I have been called in 2x to cover on my only days off...
Needless to say, im about to pass out, so im going to make this useless post...
Either I, or someone else can link you to a FJ rom, and the FJ alternate kernel that match, what you will need to do prior is make sure you have EVERYTHING you want/need, backed up to GMail (in the case of Phone logs, SMS and MMS with the Backup to GMail app, yes, im whoring this fantastic app out) AND to your computer, NO not your SD card, but your computer!
Make sure you have the latest recovery (TWRP 2.5.0.0 is what I have, but whatever TWRP is latest will do), wipe everything, then install the rom, boot, wait 10min, reboot into recovery, flash the alt kernel, boot, wait 10min, then test the home/back/menu/search key row, they should work, at this point, you CAN go back to the 2.x.x rom you where running, but if you have an i717, I have had nothing but love for the Stock rom update on AT&T once I performed a complete ODIN to it (flashing the ones here on the forum's resulted in random reboots here and there, and while less then ever before, still annoying, after an ODIN however, havent had a random reboot yet!).
There are issues with the GNote i717 JB release, many posted here, and quite a few here:
http://forums.att.com/t5/Android-Di...getting-Jelly-Bean-update/td-p/3421041/page/5
Including my own rant towards the bottom...
Needless to say, ill try and get on tomorrow to get the right links you will need, or some other kind sirs can...... either way, I have fallen asleep in the middle of writing this, so if something doesnt make sense... well, sleep writing was never my skill of choice
SGH-i717 HOME keys are not working...
Hammerfest said:
My work schedule is absolute hell, and due to people flaking at work I have been called in 2x to cover on my only days off...
Needless to say, im about to pass out, so im going to make this useless post...
Either I, or someone else can link you to a FJ rom, and the FJ alternate kernel that match, what you will need to do prior is make sure you have EVERYTHING you want/need, backed up to GMail (in the case of Phone logs, SMS and MMS with the Backup to GMail app, yes, im whoring this fantastic app out) AND to your computer, NO not your SD card, but your computer!
Make sure you have the latest recovery (TWRP 2.5.0.0 is what I have, but whatever TWRP is latest will do), wipe everything, then install the rom, boot, wait 10min, reboot into recovery, flash the alt kernel, boot, wait 10min, then test the home/back/menu/search key row, they should work, at this point, you CAN go back to the 2.x.x rom you where running, but if you have an i717, I have had nothing but love for the Stock rom update on AT&T once I performed a complete ODIN to it (flashing the ones here on the forum's resulted in random reboots here and there, and while less then ever before, still annoying, after an ODIN however, havent had a random reboot yet!).
There are issues with the GNote i717 JB release, many posted here, and quite a few here:
http://forums.att.com/t5/Android-Di...getting-Jelly-Bean-update/td-p/3421041/page/5
Including my own rant towards the bottom...
Needless to say, ill try and get on tomorrow to get the right links you will need, or some other kind sirs can...... either way, I have fallen asleep in the middle of writing this, so if something doesnt make sense... well, sleep writing was never my skill of choice
Click to expand...
Click to collapse
READY AND WAITING..THANX
Okay thank you for reply..I am ready to go with the install/flash...
When you get time to direct me to the correct ROM and Kernel i would be much obliged..In the meantime enjoy your rest..Cheers Mick