Sigh.
Had been running LiquidSense and it was working just fine. I lent the tab to a coworker last night and the 3.2 update came up for it, they downloaded and installed it for me because they thought they were "helping" me out (in fairness I had talked about being interested in the 3.2 update and the coworker in question is not a tech idiot either) but long story short, ****'s broken and I think I may be SOL.
The install seemed to fail and I figured since I was running a custom ROM I could just reboot in to recovery, go back to stock and then do the upgrade. Unfortunately for me, when I tried to reboot it got stuck in a boot loop and now I'm in an apparent world of ****. I can put the device in to Odin download mode and the computer recognizes it but it fails whenever I try to flash the stock ROM via Odin, and if I try to put the tab in to recovery mode instead it just reboots and I'm right back to where I started, in a boot loop.
Any ideas? Am I just boned on this one? If I call up Verizon and play dumb ("I dunno what could have happened, I downloaded this software update and now it just boot loops") what are the odds that I send it in to Samsung and get them to fix it without charging me out the ass for voiding the warranty?
you can gives this a try http://www.galaxytabforums.net/forum/galaxy-tab-10-1-help/885-my-google-io-boot-loop.html
or get files for dummies here http://devphone.org/files/gtab101/FilesForDummies.zip
unzip it - you should a bunch of files including recovery.md5
Run Odin.exe, and load recovery.md5 file into PDA
Turn off tab - then boot to recovery, install your desired ROM from zip
BigBalledOX said:
Sigh.
Had been running LiquidSense and it was working just fine. I lent the tab to a coworker last night and the 3.2 update came up for it, they downloaded and installed it for me because they thought they were "helping" me out (in fairness I had talked about being interested in the 3.2 update and the coworker in question is not a tech idiot either) but long story short, ****'s broken and I think I may be SOL.
The install seemed to fail and I figured since I was running a custom ROM I could just reboot in to recovery, go back to stock and then do the upgrade. Unfortunately for me, when I tried to reboot it got stuck in a boot loop and now I'm in an apparent world of ****. I can put the device in to Odin download mode and the computer recognizes it but it fails whenever I try to flash the stock ROM via Odin, and if I try to put the tab in to recovery mode instead it just reboots and I'm right back to where I started, in a boot loop.
Any ideas? Am I just boned on this one? If I call up Verizon and play dumb ("I dunno what could have happened, I downloaded this software update and now it just boot loops") what are the odds that I send it in to Samsung and get them to fix it without charging me out the ass for voiding the warranty?
Click to expand...
Click to collapse
Just something to check but when my tab was failing part way through my flashing of the leaked 3.2 rom using Odin back in November it was a driver issue.
I ended up installing kies and trying various USB ports on my machine before finding one that worked. As it turned out I could not use my USB 3.0 controller nor could I use the USB hub that I have.
Just a thought.
BigBalledOX said:
Sigh.
Had been running LiquidSense and it was working just fine. I lent the tab to a coworker last night and the 3.2 update came up for it, they downloaded and installed it for me because they thought they were "helping" me out (in fairness I had talked about being interested in the 3.2 update and the coworker in question is not a tech idiot either) but long story short, ****'s broken and I think I may be SOL.
The install seemed to fail and I figured since I was running a custom ROM I could just reboot in to recovery, go back to stock and then do the upgrade. Unfortunately for me, when I tried to reboot it got stuck in a boot loop and now I'm in an apparent world of ****. I can put the device in to Odin download mode and the computer recognizes it but it fails whenever I try to flash the stock ROM via Odin, and if I try to put the tab in to recovery mode instead it just reboots and I'm right back to where I started, in a boot loop.
Any ideas? Am I just boned on this one? If I call up Verizon and play dumb ("I dunno what could have happened, I downloaded this software update and now it just boot loops") what are the odds that I send it in to Samsung and get them to fix it without charging me out the ass for voiding the warranty?
Click to expand...
Click to collapse
Quick question does a screen pop up with a device and a computer with an exclamation in the middle that says "Firmware upgrade encountered an issue please select recovery mode in Kies and try again"?
Was in the same situation a few months ago I rooted and unlocked my tab and through a post in here was suggested to flash CWM through ROM Manager which brought up the exact same problem you're having now. Unforunately no one here could help me and my tab turned into a paper weight for a month or so until I finally got the balls to call Samsung for tech support (Verizon don't know how to fix this problem, already tried) they never asked any questions just told me to send it in. I shipped it and within a few weeks or so I got my Tab back and it was like brand new.
The really sad part of all this is that one: I apperently didn't learn my lesson the first time and went through the root/unlock process again to get rid of that damn touchwiz and forgot that ROM Manager is what killed my tab the first time so I'm once again in the same boat. Stupid, stupid, stupid... My dilemma now is wether or not to call Samsung again and see if luck will find me a second time?
---------- Post added at 12:52 AM ---------- Previous post was at 12:44 AM ----------
guess I should've read the earlier post before I commented. will probably try this when I get home
---------- Post added at 12:57 AM ---------- Previous post was at 12:52 AM ----------
animatechnica said:
you can gives this a try http://www.galaxytabforums.net/forum/galaxy-tab-10-1-help/885-my-google-io-boot-loop.html
Click to expand...
Click to collapse
Ditch ROM Manager. I used it religiously on my nook color but I've seen a bunch of people report issues using it on the Galaxy Tabs. Do your backup and restore management from within CWM instead.
Most common reason people with Verizon LTE Galaxy Tab 10.1's end up in boot loop situations is trying to flash ROMs intended for other devices like wifi versions of the GT. Stick with ROMs that are intended for the LTE tablet and ask before flashing if unsure, these LTE tabs are not the same and there's a reason why special kernels are made for them.
As for fixing the boot loops as long as you can get the tablet into download mode you should be able to fix it. Just odin the stock ROM (found here: http://forum.xda-developers.com/showthread.php?t=1342995&highlight=verizon ).
If the odin flash is failing mid way then you're most likely having driver issues on the PC side. Reboot the PC, install the latest version of Kies so that it installs the driver for you and then try again. Failing that try another USB port. Take heed of any error messages either on the tab or in odin and report them back so people can help you with specifics.
Repair service for bricked Galaxy Tab 10.1 LTE
muzzy996 said:
Ditch ROM Manager. I used it religiously on my nook color but I've seen a bunch of people report issues using it on the Galaxy Tabs. Do your backup and restore management from within CWM instead.
Most common reason people with Verizon LTE Galaxy Tab 10.1's end up in boot loop situations is trying to flash ROMs intended for other devices like wifi versions of the GT. Stick with ROMs that are intended for the LTE tablet and ask before flashing if unsure, these LTE tabs are not the same and there's a reason why special kernels are made for them.
As for fixing the boot loops as long as you can get the tablet into download mode you should be able to fix it. Just odin the stock ROM (found here: http://forum.xda-developers.com/showthread.php?t=1342995&highlight=verizon ).
If the odin flash is failing mid way then you're most likely having driver issues on the PC side. Reboot the PC, install the latest version of Kies so that it installs the driver for you and then try again. Failing that try another USB port. Take heed of any error messages either on the tab or in odin and report them back so people can help you with specifics.
Click to expand...
Click to collapse
I did exactly what you just described. It was a stupid mistake. I actually had the right ROM but clicked on the wrong one when I loaded it. Now my Galaxy Tab 10.1 LTE is bricked. It doesn't even recognize the charger being plugged in so it won't charge.
I need to get it repaired. Does anyone know of a repair service other than Samsung? I'm afraid they will take 4 to 8 weeks and I need it fixed sooner than that.
Related
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.
The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.
No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).
Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.
Things I have tried:
-Different USB port
-Kies "Resolution connection errors" button, which seems to reinstall the drivers
-Reboot computer after above step
-Remove battery from phone and replace
After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
Remove Kies and reinstall see if it picks the phone up and installs the drivers .
jje
OperationIvy85 said:
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.
The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.
No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).
Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.
Things I have tried:
-Different USB port
-Kies "Resolution connection errors" button, which seems to reinstall the drivers
-Reboot computer after above step
-Remove battery from phone and replace
After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
Click to expand...
Click to collapse
That kernel is for the Epic touch 4g is that your phone or do you have the international version? If you flashed the wrong kernel it could cause problems.
Yes it's an Epic touch 4g from sprint.
EDIT: Uninstalled Kies, reinstalled Kies, restarted computer, still no kind of recognition of my phone in any state (powered off, at "Firmware upgrade encountered" screen it boots into, or in download mode). Starting to get nervous, I used to at least hear a sound when plugging my phone into my comp. It is like there is nothing on the other end of the USB cable.
More things I have tried:
-All of the above steps on a different computer
-Sweet talking it
-Talking dirty to it
Am I brick'd? I figure not, since I can at least get into download mode. Not sure what else I can do though. I'd go see what the Sprint store can do for me, but on the download mode screen it lists my custom binary download count as 5, I understand they will see that and tell me I'm out of luck?
OperationIvy85 said:
More things I have tried:
-All of the above steps on a different computer
-Sweet talking it
-Talking dirty to it
Am I brick'd? I figure not, since I can at least get into download mode. Not sure what else I can do though. I'd go see what the Sprint store can do for me, but on the download mode screen it lists my custom binary download count as 5, I understand they will see that and tell me I'm out of luck?
Click to expand...
Click to collapse
Try to reset your binary counter with a usb jig.
you could try and download the drivers again from here and see if it then connects
http://modem-techno.blogspot.com/2010/09/epic-4g-usb-driver-download.html
I also had a similar problem once with an old i9000 and what worked was doing this and then connecting the phone first and then opening Odin.For some reason opening Odin first and connecting wouldnt find the phone.If nothing else works try wipeing the bin counter with the jig and send it back.Youll have to say that kies crashed while updating on Win7 64bits.Samsung know that before the September 30th kies update kies wasnt fully functional with 64bit drivers and they had a few phones replaced under warranty because of crashing kies updates on Win7 64bits.
Thanks for the replies everyone.
I made a USB jig but it had no result. I checked the resistance with a multimeter and I am connected across pins 4 and 5 of the usb dongle I bought. I plug it in and nothing happens.
I can still get into download mode by the usual means, just no recognition from my computer, odin, or kies. Very frustrating. Am I going to have to buy a new one or is there another way to reset the bin counter?
EDIT: Got the USB jig to work! I was using a bad diagram and was on pins 1/2 instead of 4/5. Now I can't boot, can't get to recovery, can't get any PC to recognize my phone in download mode.. but at least my download screen says "Custom binary download: NO." So if nothing else works before tomorrow evening I'm gonna bring this thing back to the Sprint store and tell them what cooza said about kies crashing on win7 64 bit. Thanks everyone! Also I just realized there is a specific forum for Epic 4G touch.. sorry >.>
The good thing is that your bin counter is at "0" again.The Kies thing is the real deal as there are also posts here on XDA of the same thing happening.I also know its true from first hand experience as it has happened to me and when i told them about the Win7 64bit driver problem (this happened to me a couple of months back too) they had no option but to accept it cos they know its true.Also i offered to e-mail links from forums with other complaints from users on 64bit PCs but they didnt even dought my storey and in 4 days it was back in my hand.I told them that when the update finalized the programe froze and the phone rebooted to a black screen.Had to pull the battery cos it appeared to be dead and refused to reboot again.Important to say that you where on Kies prior to the update I mentioned.Ived update to the latest Kies and it works fine now on my Win7 64bit so be carefull there that date is important
Thanks cooza I really appreciate your help. I do have a couple questions though.
1. Is the update you are referring to an update to Kies software.. or an update to the Galaxy S2? Reason I ask is because my phone is the Epic 4G Touch (accidentally posted in this forum >.>), will they still believe my story?
2. Not sure if you will know the answer to this one, but should I go through Samsung tech support or can I take it back to the Sprint store where I bought it?
3. Just trying to get clear on the story I should tell them. I was using Kies to update my phone on a Win7 64bit computer, but I accidentally used the version of Kies from before the Sept. 30 update? And then the phone crashed resulting in it's current state. Correct? Anything else I should watch out for?
4. With the problem you are describing with Win7 x64, does the phone go into a soft brick where it won't boot up?
Thanks again.. you've been very helpful
OperationIvy85 said:
Thanks cooza I really appreciate your help. I do have a couple questions though.
1. Is the update you are referring to an update to Kies software.. or an update to the Galaxy S2? Reason I ask is because my phone is the Epic 4G Touch (accidentally posted in this forum >.>), will they still believe my story?
2. Not sure if you will know the answer to this one, but should I go through Samsung tech support or can I take it back to the Sprint store where I bought it?
3. Just trying to get clear on the story I should tell them. I was using Kies to update my phone on a Win7 64bit computer, but I accidentally used the version of Kies from before the Sept. 30 update? And then the phone crashed resulting in it's current state. Correct? Anything else I should watch out for?
4. With the problem you are describing with Win7 x64, does the phone go into a soft brick where it won't boot up?
Thanks again.. you've been very helpful
Click to expand...
Click to collapse
Kies via to its Sep 30th update was not fully compatable with 64bits and gave a lot of problems to a lot of people.I had a few problems with it when I got a new laptop (HP Win7 64bit) so started searching the web for solutions and found that kies was designed mainly to support the windowsXP versions 32bit and had caused Samsung to accept various repairs under warranty because of crashing Kies updates mainly on android running phones.For some reason Bada didnt seam to affected.Maybe cos there arnt to many around like android.In the 4G forum there is post from someone who has bricked their phone using Kies to update and a reply from another with the same problem.Take it into where you bought it to start with and if its not there problem then they might send it back to Samsung for you.All you need to say is that you where updating your firmware via kies and on completion it froze and the phone booted to a black screen like mine did.You had to pull the battery and restart your PC to close Kies cos it wouldnt close or minimize or anything.Tell them that you searched on the net for possible causes and found what i told you about Kies and since you have a Win7 64bits PC then thats most likely to have been the cause.Your bin counter is at 0 so there is no way they can counter-attack your story.
OperationIvy85 said:
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.
The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.
No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).
Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.
Things I have tried:
-Different USB port
-Kies "Resolution connection errors" button, which seems to reinstall the drivers
-Reboot computer after above step
-Remove battery from phone and replace
After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
Click to expand...
Click to collapse
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.
Is there anyway I can do anything to save my phone?
Who told you that the exclamation point means you voided your warranty?
bajaber said:
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.
Is there anyway I can do anything to save my phone?
Click to expand...
Click to collapse
The exclamation point on a normal boot up screen (Galaxy S II splash screen) means there is a custom rom installed. This can be removed with a USB jig, which will also reset your custom binary counter.
I have absolutely no idea still what [phone]....!....[computer] means though. I ended up taking my phone back to the Sprint store and they replaced it for a small service charge while telling me next time I won't be so lucky. My next step was going to be to try calling Samsung with the story cooza suggested. I told that same story to the people at Sprint but they definitely didn't buy it, but you may have better luck with Samsung. If you get this resolved I'd be curious to hear how, but I am not optimistic for you
bajaber said:
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.
Is there anyway I can do anything to save my phone?
Click to expand...
Click to collapse
The sign you see means that your phone is semi-bricked and that you needed a jig to force the phone to boot into download mode.You can buy one on ebay for a couple of bucks.Best you do cos it could may mean that your warranty is void.Let me explain,no one can actually say that your warranty is void because of this sign but being only "semi-bricked" the service centre are still able to enter the phone and see the bin counter.So if you semi-bricked flashing a non official firmware or you have done so earlier and your bin counter is not at 0 then YES your warranty is void.Semi-brick is not so bad as you can normally fix it yourself but Hard-brick is a dead phone and you gotta pay for a jtag .In your case buy a jig force the phone into download mode and re-flash it yourself.You shouldnt need to go anywhere.Semi-bricking is something you save yourself.Just wait till the jig arrives in the mail.
EDIT:there have been posts of people pulling the battery for 10min and re-trying and it has booted to download.They say they have had to do so 4 or 5 times for it to finally work but if youve got time on your hands then give it a try.
---------- Post added at 04:48 PM ---------- Previous post was at 04:22 PM ----------
OperationIvy85 said:
The exclamation point on a normal boot up screen (Galaxy S II splash screen) means there is a custom rom installed. This can be removed with a USB jig, which will also reset your custom binary counter.
I have absolutely no idea still what [phone]....!....[computer] means though. I ended up taking my phone back to the Sprint store and they replaced it for a small service charge while telling me next time I won't be so lucky. My next step was going to be to try calling Samsung with the story cooza suggested. I told that same story to the people at Sprint but they definitely didn't buy it, but you may have better luck with Samsung. If you get this resolved I'd be curious to hear how, but I am not optimistic for you
Click to expand...
Click to collapse
Well at least you got a phone now hope they didnt charge to much!!!!Good on ya mate
Update on my issue....
It turns out the problem is because I tried to flash an I1900 firmware while my phone is a G variant (I900G).
After using the right firmware, it worked.
OperationIvy85 said:
Thanks for the replies everyone.
I made a USB jig but it had no result. I checked the resistance with a multimeter and I am connected across pins 4 and 5 of the usb dongle I bought. I plug it in and nothing happens.
I can still get into download mode by the usual means, just no recognition from my computer, odin, or kies. Very frustrating. Am I going to have to buy a new one or is there another way to reset the bin counter?
EDIT: Got the USB jig to work! I was using a bad diagram and was on pins 1/2 instead of 4/5. Now I can't boot, can't get to recovery, can't get any PC to recognize my phone in download mode.. but at least my download screen says "Custom binary download: NO." So if nothing else works before tomorrow evening I'm gonna bring this thing back to the Sprint store and tell them what cooza said about kies crashing on win7 64 bit. Thanks everyone! Also I just realized there is a specific forum for Epic 4G touch.. sorry >.>
Click to expand...
Click to collapse
Hi, I'm having an exactly same problem with you and I just got a USB jig in mail, but even though I am following the instructions for the USB jig the counter is still not going back to 0 :/
This is the instruction I followed: take battery out for like a minute -> put the battery in but don't turn phone on -> put the usb jig in -> it's supposed to boot up with 0 flash count?
Mine still says 4... Can anyone please help?
sfoksn said:
Hi, I'm having an exactly same problem with you and I just got a USB jig in mail, but even though I am following the instructions for the USB jig the counter is still not going back to 0 :/
This is the instruction I followed: take battery out for like a minute -> put the battery in but don't turn phone on -> put the usb jig in -> it's supposed to boot up with 0 flash count?
Mine still says 4... Can anyone please help?
Click to expand...
Click to collapse
Is yours a i9100? If so is your firmware the latest 2.3.5 KI3 or KI8?
Could be your device has the new bootloader. If so check intratechs original firmware thread in original development section and install his old bootloader via Odin. Have a read while your there to get the latest info.
Good luck
Sent from my GT-I9100 using XDA App
aceofclubs said:
Is yours a i9100? If so is your firmware the latest 2.3.5 KI3 or KI8?
Could be your device has the new bootloader. If so check intratechs original firmware thread in original development section and install his old bootloader via Odin. Have a read while your there to get the latest info.
Good luck
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Yeah, I got stuck while flashing 2.3.5 Gingerbread... Yeah I think it has a new bootloader, as I remember Odin updating the bootloader section before messing up.
Is there any way I can get the USB jig to work? My phone is no longer recognized by the USB anymore so I can't even flash another bootloader or anything.
Is there anythign I could do to make the USB jig work without connecting it to the computer?
Can you get into download mode using the buttons?
Volume down+home+power
If so try and flash another Rom from intratechs thread to get back to stock.
If that works you can try again.
Sent from my GT-I9100 using XDA App
Hello guys, I have (I think) soft bricked my Galaxy S2.
(Details: UK Phone, Carrier was Orange but now I am running 3 on it, official phone model Galaxy I9100T (NFC support iirc) )
Right I am curious bunny hacking away at the phone from the day I bought it, reading pages after pages on different roms and kernel and everything. Finally I settled on CyanogenMod 9 and then went straight to the CM10.1 release. Today Morning I installed the 23/02/2013 CM10.1 realease and then started browsing the XDA forums on whats new. I came across the Siyah 6.0b kernel release and saw it was compatible with cm10.1, eager and foolish I downloaded the apk without doing any further reading or any instruction, overconfident from all the flashing I have been doing for the past year, flashed the kernel via CWM recovery. Now the phone is stuck in what I assume is a boot loop (again I am pretty noobish).
So What have I tried to fix the soft brick?
I tried to go "restore" an img I had taken a week ago of the system with CWM but the phone would no longer boot into recovery.
So I went ahead and got all the recovery package (I9100TDULP9_I9100THUTLP7_HUT) to reflash my phone with Odin 3.07.
This is where I hit a brick wall and now I am truly lost at what to do, my computer doesn't recognise the phone (Download Mode). I keep getting "there is a problem with this device" error and the Device manager shows an unknown device connected. So I installed the Samsung drivers from the samsung website with no luck. Still getting unknown device error. So I googled for a solution and the only solution that came up was reformat my PC since it could be a problem within the OS, so I went forward and used two other PC and still getting the error. Please Help SOS.
tl;dr: Getting Device not recognised error when I connect phone to the computer via USB cable.
Thanks in advance to all the knights to my rescue
DNoob92 said:
I came across the Siyah 6.0b kernel release and saw it was compatible with cm10.1, eager and foolish I downloaded the apk without doing any further reading or any instruction, overconfident from all the flashing I have been doing for the past year, flashed the kernel via CWM recovery. Now the phone is stuck in what I assume is a boot loop (again I am pretty noobish).
So What have I tried to fix the soft brick?
Click to expand...
Click to collapse
Just go to recovery menu (VOLUP+MENU+POWER) and wipe cache and wipe dalvik. That should fix it.
surplus mplieac
crocodilechris said:
Just go to recovery menu (VOLUP+MENU+POWER) and wipe cache and wipe dalvik. That should fix it.
Click to expand...
Click to collapse
I cannot enter Recovery Mode, the screen just goes blank
EDIT: So the only thing that works atm is
1) The battery charge animation (huge green battery in the middle of the screen) when plugged in.
2) Download/Odin mode (which 3 computer refuse to recognise when connected via a USB cable)
EDIT2: The other thing I forgot to mention was, that I have lost the original SII micro USB cable which was black and now I am using the white micro USB cable I received with my Galaxy Note 2.
You could try uninstalling all Samsung-related drivers/software (Ie: Kies), download the Android Naked Driver or the Android ADB Driver (I wish I could recall where I got it from, but it also came with the driver for the Galaxy SII... Sounds like it might be more of a driver issue than it would be a cable issue..
Borrow and S2 cable.
There are a lot of guys having issues with note's cable.
Try a laptop, and install kies on any other pc you try.
Flash siyah v5 instead of flashing v6.
You can relax, if the only thing you did is flash a kernel then there is nothing wrong with your phone.
Try different cables, try Odin 1.85 (that one always worked for me), try different pc's, reinstall drivers, make sure no kies process is running in the background.
First of all thanks for the replies
I couldn't get the drivers working still (after re-installing, installing kies). But while eating lunch I remembered reading about removing battery and pressing the Power button and it doing something I couldn't quite remember. So I thought to myself it wouldn't hurt trying. Did that and the phone Finally booted in recovery mode, I took a breather of relief and than located my previous backup img and restored the phone.
But now a new problem arose, the phone went into SIM lock as soon as it booted and now I guess I have to fix that
Well thanks guys
Quick question guys is SIM network unlock pin basically same unlocking phone form a carrier?
It's asking for a SIM pin or network code?
Get galaxysim unlock by searching xda (free here, paid at play store).
Sent from the little guy
I was going to theme my girlfriends Galaxy S5 with Nova Launcher, but when opening the app, for some reason the phone started to bootloop. It would show the Samsung Screen, then the ATT screen, then it would reach the home screen. After doing so, the same process would occur.
I wiped the dalvik cache and after that, the phone would just stop at the ATT splash screen, and has only done that since. It can last hours on that screen... which in my eyes, means the OS's system files are corrupted.
Now she just came back from Italy and had all of her pictures on the phone (which is only 2 weeks old). I am willing to do whatever to recover the pictures, as long as I don't void the warranty.
I can access the recovery mode and download mode on the device. I have Samsung Kies, ADB, an OTG cable, and a Note 3 for myself. What I am not willing to do is format the device...
Samsung Galaxy S5
ATT
Non Rooted
Stock ROM
Any help? It's all deeply appreciated!
Why not use Odin to reflash the official firmware? If I'm not mistaken, you shouldn't lose any of those pics...as long as you don't wipe data in recovery. I remember doing this for a friend and she was concerned about not losing any pics on her phone. Don't quote me on this though. Do it at your own risk.
If you have any questions, shoot me a PM
naelscp1 said:
I was going to theme my girlfriends Galaxy S5 with Nova Launcher, but when opening the app, for some reason the phone started to bootloop. It would show the Samsung Screen, then the ATT screen, then it would reach the home screen. After doing so, the same process would occur.
I wiped the dalvik cache and after that, the phone would just stop at the ATT splash screen, and has only done that since. It can last hours on that screen... which in my eyes, means the OS's system files are corrupted.
Now she just came back from Italy and had all of her pictures on the phone (which is only 2 weeks old). I am willing to do whatever to recover the pictures, as long as I don't void the warranty.
I can access the recovery mode and download mode on the device. I have Samsung Kies, ADB, an OTG cable, and a Note 3 for myself. What I am not willing to do is format the device...
Samsung Galaxy S5
ATT
Non Rooted
Stock ROM
Any help? It's all deeply appreciated!
Click to expand...
Click to collapse
Hmm ... that sounds quite weird. I would just bring it back to support and see if they can do anything.
As for the pictures, I guess the "Android File Transfer" app might still be working if the OS boots up to a certain stage. Have you tried that one yet?
kozen-s4bb said:
Hmm ... that sounds quite weird. I would just bring it back to support and see if they can do anything.
As for the pictures, I guess the "Android File Transfer" app might still be working if the OS boots up to a certain stage. Have you tried that one yet?
Click to expand...
Click to collapse
I have a windows computer... any other app you can think of that would be able to access the phone while its off/booting?
And regarding support... Like Samsung Support?
djnoicatse said:
Why not use Odin to reflash the official firmware? If I'm not mistaken, you shouldn't lose any of those pics...as long as you don't wipe data in recovery. I remember doing this for a friend and she was concerned about not losing any pics on her phone. Don't quote me on this though. Do it at your own risk.
If you have any questions, shoot me a PM
Click to expand...
Click to collapse
Thanks, I did some searching around and apparently it does wipe.
Bump. With me possessing her phone, she has no mobile device so I really want to make sure she can have a device soon.
Can anyone confirm the recovery by using Odin to flash official firmware?
Here are the steps you should do to recover your GF's phone,
1- download official firmware from Samsung-updates.com (make sure its official at&t firmware)
2- download Odin (this is used to flash official firmware)
3- unzip the firmware you downloaded. Inside should be .tar file. This is the file that must be flashed
4- unzip Odin if needed to, inside should be exe file to run Odin.
5- put phone into download mode (hold vol. Down + home button + power button same time) you'll get a screen where it asks you to press volume up or down to either cancel or proceed to download mode. Go into download mode
6- run Odin and plug in your phone
7- Odin should then recognize your phone telling which port your phone is plugged into (ex. Com4). If it is indeed connected and recognized move on to the next step.
8- press the PDA button on odin, a window should pop up where you can locate the .tar file. Look for the file wherever you extracted it to. After you find it double click it.
9- .tar file should now be in the PDA slot. (Please note that "auto reboot, reset time and pda should be the only boxes that should have a check, make sure nothing else is checked mark) by default the the checks should already be there and you shouldn't have to do anything but I thought I'd let you know just in case.
10- press start and wait till everything is done
---------- Post added at 01:24 AM ---------- Previous post was at 01:23 AM ----------
After some research of my own, it seems that flashing the stock firmware over your phone will not wipe any data or apps as long as you didnt wipe/factory reset your phone in recovery
---------- Post added at 01:30 AM ---------- Previous post was at 01:24 AM ----------
I've taken the liberty in helping you out in providing the links that needs to be downloaded.
Odin- https://www.google.ca/url?sa=t&sour...nU6_0obQ6fr_QnBsA&sig2=OZVGB7LZ4HEzhIe9X2JgwA
Official At&t firmware- http://samsung-updates.com/details/26862/Galaxy_S_4_AT&T/SGH-I337/ATT/I337UCUAMDL.html
Thank You, DJ!
Samsung s5 G900A REbooting issue
Hope Im posting this in the right spot. Hello I rooted my AT&T S5 G900A and had no problems until I went overboard and installed the lucky patch android software I believe its called.Iused it beofre and no problems so thought no biggie.I did the patch to android on the app.And well now Im stuck with a non starting phone.It doesnt get passed the samsung logo and if it does do anything its only to reloop.Ive tried odin and everything i can think of.Right now in recovery mode it says android system recovery<3e> LRX21T.G900AUCU3B0C4.
I dont know if it means I have that or need that.Im now so confused and Im usually pretty good with my phone stuff.Any that can help it would be so appreciated.Thanks,Aeron
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.
Hello Everyone,
So recently I got a new S4 and I decided to root and mess around with it a little bit... Didn't go so well.
First KNOX was pissed that I tried that because I had given SU power to SuperSU (I didnt want to use KingUser) so when that happened, SuperSU failed to set itself as the primary SuperUser app. So I decided to install recovery (TWRP) to do it the recover way, scripts and all that. After that, I went ahead and removed KNOX, via the settings menu on the app.
Now I fail to boot into RECOVERY, and I also fail to boot into normal Android mode. When I attempt to boot normally, the SAMSUNG logo comes up then verizon, Okay fine its booting. 5 miutes later, the phone gets hot, and still wont boot.
I cannot charge the normal way, or even use the charging port. I have to take the battery out and put it in a dock. So ODIN is out of the choice.
My Phone Specs:
Samsung Galaxy S4 i545 (Verizon)
1GB SD Card
No recovery or ODIN.
Please help...
If you can't get into download mode then you have a problem.
Without it there isn't much you can do. You also need the pc to recognize your phone.
I'd say flash a custom ROM because new update which I received on stock firmware of I9500 added some security and an app called smart manager which is causing instability. Connect your dead phone to charger and then flash TWRP 2-3 times and don't forget to untick F.rest time and auto reboot. Normally it is ticked, and manually boot to download mode each time I hope you know how to do that. Then try your luck. That's how I did it. And use latest recovery available on the web.
Hit thanks
I believe the Verizon s4 has a locked bootloader (http://forum.xda-developers.com/showthread.php?t=2681316); therefore, you cannot flash a custom ROM or custom recovery.
You may get more replies if you post your question here: http://forum.xda-developers.com/galaxy-s4-verizon/help
Read before posting!
THe thing is though, If I could use Download mode, i would. But because of damage in the port, it fails to work So this is why I am confused on what to do...
---Edit will go here if needed.
thedarkness523 said:
THe thing is though, If I could use Download mode, i would. But because of damage in the port, it fails to work So this is why I am confused on what to do...
---Edit will go here if needed.
Click to expand...
Click to collapse
if the port is physically damaged then you need to
get the port replaced
there is absolutely nothing you can do until you have the usb port repaired
. secondly hold power down while inserting the battery if that doesn't get it into download mode then congratulations you now have a 200.00 dollar brick
the i545 does not support custom recoveries or custom roms outside of modded stock roms attempting to flash one will result in a permabrick as you just found out
Once the usb is repaired if you are still unable to access download mode then you have a big problem. When the port is repaired see if the comouter recognizes the phone as QHUSB_dload, if so, you need jtag, if the computer doesnt recognize the phone then it is most likely damaged beyond repair.