Related
Hey all, before I say my problem, firstly I have no idea if this is the right section in the forums so apologies in advance, secondly, I have held out for 3 days trying to work out various issues before I posted. I probably did just miss one thing or misread another but no matter how much I look, no idea what as new to this. Thanks in advance for your help.
Basically, wanted to flash some custom firmware to my phone, I have been having many issues with backing up on Kies, seems to be something related to my USB's and my computer, it keeps failing during the backing up of programs. I ended up giving up on this, made a titanium pro back up of System files and of programs, also made a Nandroid backup, both on my internal phone memory I believe. Have root access, installed busy box and such, backed up some other stuff using EFS Pro, now I am completely confused, I have followed a few guides dotted around the internet, tried to install some custom firmware, it was Carbon Rom 4.2 I believe. I went into the CMW menu, wiped data/factory reset, wiped partition cache, and wiped dalvik cache, installed the rom from my internal phone memory, as it would not find it on the memory card when I tried, and now after two attempts of it seemingly doing it, on rebooting the phone, I go back to the Samsung firmware.
I have tried to read up as much as I can but obviously I am missing something here and no amount of guides or google searches have hinted at my problem, could anyone help? I know people asking constantly for information on how to put on custom firmware will be irritating, but I have genuinely taken this as far as I can alone Cheers
Now after formating something under mount/system, my phone is stuck on the logo screen, reinstalling the ROM does not work either, no idea what to do now
reflash rom, wipe data and voila.
Hey, thanks for the reply. By reflash rom, which way do you mean, am pretty confused still. The rom I download basically bricked my phone, I don't know why, I think to recover it I use ODIN and get my stock software, so is that what you mean? Or can I somehow use my Nandroid back up..?
deancolt45 said:
Hey, thanks for the reply. By reflash rom, which way do you mean, am pretty confused still. The rom I download basically bricked my phone, I don't know why, I think to recover it I use ODIN and get my stock software, so is that what you mean? Or can I somehow use my Nandroid back up..?
Click to expand...
Click to collapse
If you have a Nandroid restore that or flash your original firmware via Odin .
Never restore system files after a firmware change with TB .
jje
Ok here is the situation now, I have made things 100 times worse, I possibly should not of been doing it this late... I followed guides exactly though and there is definitely something not working right with this phone, I just don't know what, all I know is its very temperamental with connecting to computers and will fail doing the custom firmware flashes half the time, no matter what I use, even using the stock ROM i got from samimobile has caused many problems. It might be me, I don't know, but in my frustration followed some advice on a forum and I think I formatted the mount/system. SO obviously I lost both my back up's. My fault and can live with that, phone was bricked and had to do that to get past it I think..
But now no matter what kernel I use and have tried quite a few including my original one, I am unable to connect to my home wifi. It definitely is not the wifi, it worked just fine before I flashed the phone and has been working with it for 4 months, now whenever I set up the phone its constantly stuck in this obtaining network ip infinite loop. No fixes I have used have helped at all so far Sorry to keep asking stuff, I am just literally at the end of my tether, was up until 7am messing with it to no avail.
Just to reiterate a point, the reason I wanted custom firmware was because the phone was crashing randomly and just dying on me and also the speaker had lost like 90% of the volume when I wanted to play music, also it would not connect to my computer with ease, now obviously before I did anything it had issues. So that is why I feel something might be wrong, not saying I did not break anything myself, just the process of flashing the firmware has been pretty straight forward once I did it a couple of times, it has just been failing and bricking every other time, so I am not sure what the problem actually is, did I miss a step, did I mess it up? If not what has. Please helps guys. Regards.
I formatted the mount/system. SO obviously I lost both my back up's
Click to expand...
Click to collapse
formatting system wouldn't touch your backups
deancolt45 said:
Just to reiterate a point, the reason I wanted custom firmware was because the phone was crashing randomly and just dying on me and also the speaker had lost like 90% of the volume when I wanted to play music, also it would not connect to my computer with ease, now obviously before I did anything it had issues. So that is why I feel something might be wrong, not saying I did not break anything myself, just the process of flashing the firmware has been pretty straight forward once I did it a couple of times, it has just been failing and bricking every other time, so I am not sure what the problem actually is, did I miss a step, did I mess it up? If not what has. Please helps guys. Regards.
Click to expand...
Click to collapse
Usual reply if you did not know what and why and had never bothered to read the faqs and guides before flashing .Then its nearly always user error .
Best take it to a service centre and pay for a repair .
jje
edinghn are
Close thread please
Found out something really handy
Hi guys,
TheGS3 has 1 huge trick when u got stuck in firmware, CSC, etc.
Especially when u used some super usefull toolkit (like me)
I used the Galaxy S3 Toolkit, option4 (ALL in ONE) just push enter 2 times
1 to start and the last one to exit...
Got all the issues i read on hundreds of pages searching for the solution.
Accidentialy i found this morning (its 4:45am right now and busy with it since 15:00)
Start Kies, connect GS3 with USB kabel and when it says not connected take out USB
Dont plug in USB for a while...
In KIES go to Tools and irmware upgrade.. Remember, DONT plug in USB
It will ask u for your model nr which is printed on sticker in baterycover
Confirm and it will ask u S / N' which is printed on same sticker
It will start downloading firmware and u will be guided through update progress
Good Luck to y'all.. Time to go to bed.......
I have a SGH-I747M 4.1.1 Galaxy S3.
I used the Unified Toolkit and rooted/installed CWM, backuped and ready for a new ROM.
As I was installing this custom ROM (Pardus HD), and error popped up and it was aborted, (still in the CWM main menu)
but having only the said custom ROM zip file in the internal memory,
I figured I just shut down and download a fresh copy of the ROM.
and put it in an external SD card then power on the phone back into recovery.
Only thing is it wont power on anymore, the screen is just black, plugging in USB and computer just makes connected/disconnected noise.
(Devices say its "Qualcomm HS-USB DQLoader 9008")
Also tried taking out putting in the battery.
(I know my mistake is I never re-installed the backup) I've run out of ideas, please help.
I have a very similar problem. I had my battery checked thinking that could be the problem. My battery shows that is no good. I tried a new one and still nothing. I can't help but think if it were a missing program it would still come on at least. Lucky for me its covered under insurance. I'd still like to know what happened and if I could fix it.
I'd like to know too if I could fix it myself, other than ''the jig'' or a repair service. currenty trying to revive it still
edit: currently trying this Heimdall thing, goodluck to me...
Have you checked the battery? If I wasn't sending mine back on an insurance claim I would take it apart. I have a Motorola that has a fuse next to the battery under the back of the case. Seems dumb, I know but how could changing the rom "short" out my battery. Dumb again I always thought bricking was only being able to bring up recovery.
I think the battery is fine, as CWM was still running after the error.
That's pretty much what happened to me. Maybe we got to the same problem 2 different ways. Hope you get it figured out.
THIS IS GT-I9300 SECTION..
c'mon there was an stickie on top of this section for you..
HERE.. http://forum.xda-developers.com/forumdisplay.php?f=1705
Your problem is that you flashed a rom for gt-i9300 (International) and you have some U.S. variant of s3. That in most cases bricks the phone.
Probably time for a service center visit.
Hey guys
1) Restarted my phone today using CM10.1 from a very recent nightly (within the past week).
2) On restart, phone froze and got kernel panic.
3) Restarted into CWM and tried to do a restore to an earlier backup I had made.
4) Half-way through the restore, I got ANOTHER kernel panic (never had that before)...
5) Only things I could do with the phone after that was enter download mode...nothing else...couldn't enter recovery mode anymore.
6) Went into download mode and flashed this CWM-Recovery (http://forum.xda-developers.com/showthread.php?t=1118693) and followed the instructions to the letter.
7) Odin 3.07 hung on NAND Write Start
8) Tried using Odin 1.3, and it seemed to flash correctly. It says completed no errors.
Phone will now not even start and is completely unresponsive...pressing any combination of buttons will not start the phone, and the phone is not recognized in Odin anymore...did I just hard brick it? Any other ideas?
Thanks,
Elliott
Service centre. Although if you can have someone who does JTAG's have a look at it to determine whether it can be JTAG'd without you giving them any money up front (I.E you only pay them if it can be JTAG'd), try that first.
Thanks that's what I thought.
Also, try a jig if you can get one. In all likelihood won't work, but stranger things have happened & you have nothing to lose.
Yeah thanks that's what I plan on doing. Any idea what I did wrong, though? I don't want it to happen again if I get it working with a jig.
Impossible to say. Not sure why you flashed that nondescript kernel/recovery in that situation tho given it probably wouldn't have worked even if the flash had been successful (You would probably have ended up with bootloop given recovery was obviously 'broken'). I would have flashed stock with Odin (And that's certainly what I tell people in your situation on here to do because it normally works).
But flashing recovery rather than a stock rom probably didn't break your phone, put it that way, so you didn't do anything 'wrong' per se. Just remember if you get into a similar situation again, go back to stock via Odin & start again (re-root your phone/restore a backup, flash your custom rom/kernel again, etc).
If the jig works (and don't get your hopes up or anything, we're talking a 1 in 10,000 chance, and that's probably being generous), flash stock with Odin (you wont have much choice).
Well...brought it to a JTAG specialist today and he couldn't fix it either...says it's very rare and he's had 5 out of 80 S2's like this happen without being able to fix them...
Bummer. Motherboard replacement in that case. If the phone's under warranty, take it to a service centre & say as little as possible. You might blag it for a warranty fix. No warranty ? You can still have a new motherboard put in by a service centre (more expensive option usually), or you can source a 2nd hand MB from a 'donor' phone (one with a broken screen that's otherwise OK, etc) & either swap it in yourself or pay a local mobile repair shop to do it (usually cheaper option).
@ OP By following what you flashed I noticed the date, we're talking about a 2 years old thread, a lot have changed since.
Not sure that was what bricked your device but I get that panic mode.
The other thing that it comes to mind is nand corruption, which has been quite common these days with people running custom.
I'm with bungle there, the best recovery package is going back to stock and start fresh.
I, on the other hand, wouldn't accept the situation you are on, I would spend a whole week trying to get that phone to boot again, whether a second opinion on a jtag, a new jig, another battery or any other thread on here at xda.
If the device gets hot near the rear camera and it won't even charge nor get warm around that area dismiss what I just said and proceed with the mobo replacement bungle suggested.
And of course, if you did something else to your device and didn't share it please, come clean so others don't freak out by reading this.
Sent from...this is not even my S2
Hey
Nothing else was done to the device...just what I stated exactly.
I caved today and bought a BNIB S3 because I couldn't go without a phone anymore...
Thanks for the help, guys
Elliott
Full story: Sold my phone, tried unrooting, soft brick, went back to stock, flashed Cameleon ROM 3.0.2, starts acting weird (more frequent freezes and reboots, vibrates for about 5-10 seconds when it's been off for a while), charge and boot up this morning, and now phone refuses to connect to any network. IMEI's not blocked or anything. TriangleAway formatted my internal SD, so no backups. Also said the battery was at 100% every time I rebooted, even though it was ~85%. Clean flashing CM10.1 didn't help. I've searched everywhere and nothing seems to help. Warranty's out long ago. I'm incredibly frustrated and desperate for a solution
Who knew running low on battery could cause this?
Running on low battery didn't cause it, tho it could be a simple case of needing a new battery. Might want to try that first, tho it does sounds like the USB board is on the way out. This gets discussed here all the time, search for these threads & read them very carefully. There's 4 different revisions of the board; you need to order the same one that's currently in the phone or your phone may not work properly. Other than that, it's quick/cheap to replace yourself.
So if a new battery doesn't do it, replace the USB board.
Edit - Re: the phone not connecting to networks, how do you know for certain the IMEI isn't blocked ?
MistahBungle said:
Running on low battery didn't cause it, tho it could be a simple case of needing a new battery. Might want to try that first, tho it does sounds like the USB board is on the way out. This gets discussed here all the time, search for these threads & read them very carefully. There's 4 different revisions of the board; you need to order the same one that's currently in the phone or your phone may not work properly. Other than that, it's quick/cheap to replace yourself.
So if a new battery doesn't do it, replace the USB board.
Edit - Re: the phone not connecting to networks, how do you know for certain the IMEI isn't blocked ?
Click to expand...
Click to collapse
Of course, I don't know for certain. I used AMTA's checker, and apparently it's not blocked.
I'll try repairing the board. In the meantime, I'll contact the police to find out about the IMEI. Thanks!
Something similar happened to me, try to flash your device with an official ROM, preferable Android 2.3 root your device, then search the GB's Modem or baseband, find the one compatible for your network or country and then you need to flash it via CWM recovery of course you need to be rooted, do a full wipe before you flash anything. Doing this you device should be fully functional and then you can install any Custom Rom. Hope that helps..!
Hello, This is my first Post on XDA so please help me to familiarize myself with rules and procedures and I apologize if I break any in any way.
Okay, So My phone (SM-G900T) is about 5 months old. I bought it in August, Without insurance (Terrible Idea), and now it is having problems. In the amount of time I've had it, I rooted it in mid to late September and used only an app called Xmod for a game. I then started using greenify, solid explorer and eventually used Xposed installer to try a few Xposed modules. Specifically I used, the YouTube adaway, Rich Pandora notification and that's about it. I also later installed Samsung Tools to backup my IMEI and important partitions.
A few days ago my phone randomly rebooted in the middle of a YouTube video so I let it reboot, but it rebooted again, and again, and again. I pulled the battery and turned it back on but the same problem persisted. I couldn't do anything to fix it so I just decided to factory reset the device through the stock recovery. Also, I did not install any custom roms or anything either. The factory reset did nothing. Now when I was in setup, everything force closed, froze and rebooted, repeatedly. So I found the original firmware that my phone came with and flashed it to my phone through Odin because I literally had no hope of what to do anymore. The problem lessened so I didn't install all my apps and overload the device as it would reboot when the RAM would get pretty full or too many things were running simultaneously in the background or foreground. The problem got a little worse so I factory reset one more time and it lessened again but now it came back and factory Resetting isn't lessening the problem. Now it just force closes a bunch of stuff and freezes and reboots into a bootloop midway through initial setup. I am desperate at this point right now and I need help from you guys. I don't have warranty because I rooted and I made the Extremely stupid decision of not getting insurance. So please can anyone help me out? I will be eternally grateful if you can help me turn this $609 brick into a phone again.
I will try to check this thread daily, but I go to school and I may not respond immediately, so please understand.
ahmed12534 said:
Hello, This is my first Post on XDA so please help me to familiarize myself with rules and procedures and I apologize if I break any in any way.
Okay, So My phone (SM-G900T) is about 5 months old. I bought it in August, Without insurance (Terrible Idea), and now it is having problems. In the amount of time I've had it, I rooted it in mid to late September and used only an app called Xmod for a game. I then started using greenify, solid explorer and eventually used Xposed installer to try a few Xposed modules. Specifically I used, the YouTube adaway, Rich Pandora notification and that's about it. I also later installed Samsung Tools to backup my IMEI and important partitions.
A few days ago my phone randomly rebooted in the middle of a YouTube video so I let it reboot, but it rebooted again, and again, and again. I pulled the battery and turned it back on but the same problem persisted. I couldn't do anything to fix it so I just decided to factory reset the device through the stock recovery. Also, I did not install any custom roms or anything either. The factory reset did nothing. Now when I was in setup, everything force closed, froze and rebooted, repeatedly. So I found the original firmware that my phone came with and flashed it to my phone through Odin because I literally had no hope of what to do anymore. The problem lessened so I didn't install all my apps and overload the device as it would reboot when the RAM would get pretty full or too many things were running simultaneously in the background or foreground. The problem got a little worse so I factory reset one more time and it lessened again but now it came back and factory Resetting isn't lessening the problem. Now it just force closes a bunch of stuff and freezes and reboots into a bootloop midway through initial setup. I am desperate at this point right now and I need help from you guys. I don't have warranty because I rooted and I made the Extremely stupid decision of not getting insurance. So please can anyone help me out? I will be eternally grateful if you can help me turn this $609 brick into a phone again.
I will try to check this thread daily, but I go to school and I may not respond immediately, so please understand.
Click to expand...
Click to collapse
Do you have SD card installed? If you do try taking it out and leave out or replace with another SdCard. Then flash the original stock firmware as you said you did before through (odin!) Then if that dont work try kias3 and use the emergency firmware recovery tool. Before you do any of this make sure you factory reset through stock recovery if possible.
Sent from my SM-G900T?
---------- Post added at 03:17 PM ---------- Previous post was at 03:07 PM ----------
Have you tried this tool? I had the same issue with my phone and reinstalled firmware and stock recovery through this tool and it stopped. If none of these tips work id say your phone may be borked or have faulty hardware. Take a look here as welll. Hope you can get your phone back to normal. I can understand what you're going through, like i said i had same issue with mine and mine has seems to be fine as of now. http://forum.xda-developers.com/showthread.php?t=2721146 . GOOD LUCK
Sent from my SM-G900T ?
beachbum40 said:
Do you have SD card installed? If you do try taking it out and leave out or replace with another SdCard. Then flash the original stock firmware as you said you did before through (odin!) Then if that dont work try kias3 and use the emergency firmware recovery tool. Before you do any of this make sure you factory reset through stock recovery if possible.
Sent from my SM-G900T?
---------- Post added at 03:17 PM ---------- Previous post was at 03:07 PM ----------
Have you tried this tool? I had the same issue with my phone and reinstalled firmware and stock recovery through this tool and it stopped. If none of these tips work id say your phone may be borked or have faulty hardware. Take a look here as welll. Hope you can get your phone back to normal. I can understand what you're going through, like i said i had same issue with mine and mine has seems to be fine as of now. http://forum.xda-developers.com/showthread.php?t=2721146 . GOOD LUCK
Sent from my SM-G900T ?
Click to expand...
Click to collapse
Okay, so I'm resetting it back to stock firmware through Odin as we speak. And yes, I had an SD card and have already taken it out and left it out and reset but still the problem has persisted, I will definitely try the solution you just mentioned, here I go. And thank you for replying...
Edit:
Hold on, which do you want me to try first? kias3(can you please link it if possible) with emergency firmware recovery tool? OR the Unified Android Toolkit?
Also... I don't exactly know how to use the toolkit, can you verify the steps to take to use the toolkit properly if I should use this solution? I'm sorry but I'm not very advanced at Android development, just intermediately experienced I suppose...
ahmed12534 said:
Okay, so I'm resetting it back to stock firmware through Odin as we speak. And yes, I had an SD card and have already taken it out and left it out and reset but still the problem has persisted, I will definitely try the solution you just mentioned, here I go. And thank you for replying...
Edit:
Hold on, which do you want me to try first? kias3(can you please link it if possible) with emergency firmware recovery tool? OR the Unified Android Toolkit?
Also... I don't exactly know how to use the toolkit, can you verify the steps to take to use the toolkit properly if I should use this solution? I'm sorry but I'm not very advanced at Android development, just intermediately experienced I suppose...
Click to expand...
Click to collapse
Try kies first that dont work try toolkit. Just Google how to use the toolkit it's pretty self explanatory but I don't think you'll need to use the tool kit anyways. http://www.sammobile.com/kies/
HOW TO USE RECOVERY TOOL IN KIES
http://forum.xda-developers.com/showthread.php?t=2261153&page=4
beachbum40 said:
Try kies first that dont work try toolkit. Just Google how to use the toolkit it's pretty self explanatory but I don't think you'll need to use the tool kit anyways. http://www.sammobile.com/kies/
HOW TO USE RECOVERY TOOL IN KIES
http://forum.xda-developers.com/showthread.php?t=2261153&page=4
Click to expand...
Click to collapse
okay, I tried resetting it using Kies3 but the device was not recognized so I had to find a different way because the guide on how to use Kies advised using Odin if Kies didn't recognize your phone. I don't have a code either, So I tried reflashing the stock firmware through Odin and it started up, froze and went into what I presume to be a bootloop as it is stuck on the T-Mobile splash screen with the notification light pulsing continuously. Did I also mention where my phone says Knox warranty void 0x1 there is another statement that says "Counter: 4" or something like that, while I am in download mode, does this have any significance? but yeah, other that Kies and Odin, I'm not sure if the android toolkit will help, because it's basically doing that same thing as I am with Odin, just more automated... Or am I wrong?
but as far as I know, that toolkit is literally the last option I have left, I guess I'll be trying that out tomorrow, with option 10 I believe where it says "10. Download, Extract + Flash Stock Firmware via Odin" but I'm not sure what ADB mode means... I can't really boot up the device so I don't know if that applies
Also, on a side note, how much do you think this will cost if I were to send the phone to Samsung and pay for repairs out of pocket, and do you think they could even repair it at all?
You know what... Do you think if I somehow installed CM12 on the device that the problem would fix itself? Because to me it seems like it's the Samsung software itself that is causing all this trouble along with a few Google apps. Now how would I root it and flash CM12 if it won't boot up fully...
Not sure if this would brick my phone either, let me know if it would if I tried to root through Odin and try to install CM12 through CWM recovery or something
Just throwing ideas, hoping this thread doesn't die before my problem is solved
Also, does geeksquad repair Samsung phones one time for a low fee if you've voided warranty?? If so then this could possibly be my final solution.
Also Never EVER buying a Samsung device again, they just aren't what they used to be back in the day, the other OEMs have caught up and left Samsung and their revenue in the dust...
ahmed12534 said:
Also Never EVER buying a Samsung device again, they just aren't what they used to be back in the day, the other OEMs have caught up and left Samsung and their revenue in the dust...
Click to expand...
Click to collapse
I disagree with this completely. Very few other handsets can hold a candle to the S5 or the Note 4. I don't know of anybody that has the problems you are describing with their phones without a hardware issue of some type or bad app. The Samsung software runs perfectly on millions of devices without the issues you're having. Therefore it's probably a bad app you've gotten a hold of, or you have a bad phone. CM12 will only introduce more issues and probably won't solve anything.
A stripped down custom rom might be a good bet because you can then start adding your apps back to find out where the issue is, or if it still has the same issues then it almost guarantees that there is some kind of a hardware issue.