Hey guys, first time poster 3-4 year lurker.
I have a question about my Odin flash that I did last night. I followed these steps http://forum.xda-developers.com/showthread.php?t=2391367
and everything flashed and tablet is working. The only problem I have is when I restart or cold boot the device the screen stays on but with a black screen for about 20 seconds then the screen dims for another 15 seconds after that the screen goes black for another ten seconds. I wait another 10 seconds with the screen black (off) and then I can press the home button and my home screen comes up. The device is rooted and everything seems to working fine.
Power > Samsung splash screen > bright 20s > dim 15s > screen off 15s > wait 10s > home screen comes up. (no sound during this process)
during this process my power, volume and home screen button does not do anything till after I wait 10s after the screen off
I have attempted to re-flash the rom using the same method and even downloaded "prerooted.tar.md5" and the "odin 3.07 from other sources and I still get the same results. I have also download drivers directly form Samsung page, uninstalled, rebooted, re-installed. I have also used different USB ports and I still get the same results. I read a suggetion to try odin 3.09 but I receive a "FAILED" when flashing.
I am using windows 7 pro X64 my tablet is Mo:SM-T210, current kernal 3.4.5-1256430-user, Build JZO54K. T210XXAMG2
unfortunately I have searched for this problem on Google and the forums but nothing I have found fits this description. I am not allowed to post in the dev section due to my lack of post. Hope to hear from you soon and thank you for the years of support you have given me. Hopefully I will be able to be of some use to someone in the future.
Related
Hey guys. I have a samsung galaxy S3 SGH-i1747M Running ICS on Bell.
It asked me to do an update today, a full software update (Not jellybean clearly). I accepted it. It automatically turned off saying that it was going to re-boot. It never re-booted. Now it wont even boot. When I try and turn it on, it vibrates, splashes the samsung logo, says "Recovery Boot" in the top left corner, then just gives me a black screen. I cant get into download mode and Kies wont recognize my phone when plugged in. Im pretty stumped on what to do.
If you guys could help me out that would be great.
Thanks
ZiiC
ZiiC said:
Hey guys. I have a samsung galaxy S3 SGH-i1747M Running ICS on Bell.
It asked me to do an update today, a full software update (Not jellybean clearly). I accepted it. It automatically turned off saying that it was going to re-boot. It never re-booted. Now it wont even boot. When I try and turn it on, it vibrates, splashes the samsung logo, says "Recovery Boot" in the top left corner, then just gives me a black screen. I cant get into download mode and Kies wont recognize my phone when plugged in. Im pretty stumped on what to do.
If you guys could help me out that would be great.
Thanks
ZiiC
Click to expand...
Click to collapse
Don't panic simple to recover, what you need to do is flash your ROM manually using ODIN.
1 Of course you need to get ODIN
2 Since you already have kies, it should recognize the phone as soon as you plug in to PC when you get in Download modem you can only tell if it gets recognized in Kies you will see COM PORT number ON (Yello) or Blue
3 download the ROM from Bell...Here: http://samsung-updates.com/get/2569/Samsung_Firmware_SGH-I747M_BMC_I747MVLALH1_Android_4_0_4.html
once all all the files are ready, while phone off get it in Download mode
How to get into Download Mode (For Odin)need to extract the zip
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode
Open odin, CHECK ONLY PDA and direct to file (rom) you downloaded (might need to be extracted first)
Plug the phone, which by now should be showing the Download mode screen, WAIT until the computer is done recognizing and installing then Hit start button and wait be patient it might take some time, and the first boot will take a long time...
The above information is solid. However Bell has a 30 day "DOA" policy. So, if by chance you've only had it 29 days, you should rush to the bell store and tell them your newish phone couldn't handle a stock ICS update and they will swap it out. I tried updating mine (stock rom via kies) 5 hours after I bought it and I could never turn it on again... Complete brick. Bell store swapped it out no questions (I did not have the optional insurance).
If your past 30 days... See above post
Sent from my SGS3 i747m (Bell) on CM10 using TapaTalk2
I've got a sprint GS3 that is rooted and has the clockwork recovery mod on it, but was otherwise running stock OS. It had been acting up, hanging, that kind of thing so I decided to go ahead and accept the download new software prompt I've had for the last year or so. When it went to the bootimage(?) menu it asked if I wanted to install this untrusted image. That gave me pause, so I selected no. The little android icon got a red X-ish thing on it's chest and it rebooted. And sat at the samsung galaxy s3 screen for about a half an hour. I pulled the power and it kept going between hanging at that screen, or hanging at random points (app 6, 8, 9, 11) of an "upgrading android" screen I have never seen before. I tried going into the recovery mode but when I follow the instructions (up vol, home and power, when it vibrates for power release the power button) but that doesn't work at all. It just sits there. I'm 100% certain it's not a button/physical issue. I decided to try the download option and can get to a screen that warns me about custom rom. I've tried both installing (let it go for over an hour, gave up) and hitting cancel, to no avail. Before I take this as a sign from the android gods that it's time to go get a GS5, does anyone have any ideas/advice? TIA.
Wrong section.. Report it yourself and adj a mod to move it to correct section..
Sent from my GT-I9300 using xda app-developers app
Have you tried to plug the phone in with the USB cable into the computer?
Galaxy Tab S 8.4, SM-T700. Received the lollipop update and that worked fine. Immediately tried to run CF-Auto-Root on it using Odin 3.07 and CF-Auto-Root-klimtwifi-klimtwifixx-smt700.tar.md5. I booted into download mode, started Odin and clicked Start. Only the first progress block in Odin lit up and the Tab S only showed about an inch of blue progress line. That was it for about 4 hours.
The tab was not responsive, shutting down Odin did nothing and trying a different Odin version also did nothing. So I had no choice but to disconnect the Tab S. Immediately rebooted to the "Firmware upgrade encountered an issue...." message. Running Kies does not recognize the tablet, running different versions of Odin with the stock firmware does nothing and the Tab won't do anything but restart into the "Firmware encountered an issue" screen. Won't go into download mode at all and nothing I do in Kies or Odin seems to work.
Last several times I've used CF-Auto-Root went flawlessly. This time, not. So if it continually reboots in to the "Firmware encountered an issue" screen, is there any recourse?
I have let it run out of juice and left it plugged in long enough to recharge fully but no matter what I do, it won't do anything but get to that one annoying screen!
Maybe there's a sequence of steps I'm missing. Anyway, been trying everything I can find out there on this but it's not working.
Thoughts?
You likely have a bad cable there. That's what happens.
You should be able to get download mode if it boots to the firmware failed screen
If you can boot to recovery then just wipe cache and it should boot.
From the firmware failed screen hold POWER + VOL DOWN + HOME until it restarts then immediately change to VOL UP whilst still holding the other buttons.
If that doesn't work try again with POWER + VOL DOWN + HOME until download mode boots.
If you still can't get either you can try the usb jig, which apparantly does work on this device.
Ask skOrPn which one to use, he use to build these things.
Hmmmm, you're right. I was using the Samsung cable that came with the tablet so figured there wasn't anything wrong with it (since one of the popular solutions is to not use a generic and make sure to use the Samsung).
So I dug deep in the vault for a slightly older Samsung cable from a previous phone and tried it. Sure enough - it worked. Odin completed the CF-Auto-Root in the 10 seconds it usually takes.
Clearly even Samsung cables go bad.
Thanks for pointing out the obvious but not so obvious!
Bob
I've dug around trying to find a similar problem here and on google, so my apologies if this has already been addressed.
The problem originally began when the game pad stopped being responsive (or at times took multiple presses to get a response) and after no luck troubleshooting it, I tried to reset from clockwork recovery.
Ever since my phone no longer boots. It just sits on the LUPUS wolf logo (I do not recall exactly which rom I am running, but I hope this helps) and at first I thought it was your normal "this can take a bit" first boot, but I've let it eat the whole battery and it never gets anywhere. I've tried to prompt the phone to boot into both custom recovery and d/l mode and neither get me anywhere. Any suggestions?
Sacrifusion said:
I've dug around trying to find a similar problem here and on google, so my apologies if this has already been addressed.
The problem originally began when the game pad stopped being responsive (or at times took multiple presses to get a response) and after no luck troubleshooting it, I tried to reset from clockwork recovery.
Ever since my phone no longer boots. It just sits on the LUPUS wolf logo (I do not recall exactly which rom I am running, but I hope this helps) and at first I thought it was your normal "this can take a bit" first boot, but I've let it eat the whole battery and it never gets anywhere. I've tried to prompt the phone to boot into both custom recovery and d/l mode and neither get me anywhere. Any suggestions?
Click to expand...
Click to collapse
IMHO, it looks like faulty slider flex cable (exact same situation i had, but i was able to enter recovery after 2 minutes of logo on screen)
Try to power on phone with slider open.
If you can enter in recovery mode with "volume -" (if it light blue led or vibrate) and see is d-pad is working.
Sorry for the delayed reply. The notification went into my spam folder :/
Alright, I followed your steps in two ways. I opened the slider and held both the power and the volume down till I got the buzz buzz and the LED blinked green once and continued to hold volume down till I got the LUPUS logo. No luck. I did mostly the same thing the second time but I held the volume down for 3 minutes with the same result. I still have yet to make it back into recovery.
Sacrifusion said:
Sorry for the delayed reply. The notification went into my spam folder :/
Alright, I followed your steps in two ways. I opened the slider and held both the power and the volume down till I got the buzz buzz and the LED blinked green once and continued to hold volume down till I got the LUPUS logo. No luck. I did mostly the same thing the second time but I held the volume down for 3 minutes with the same result. I still have yet to make it back into recovery.
Click to expand...
Click to collapse
To be able to enter recovery, it is not "holding volume-" while powering on phone or keeping it pressed.
Press power button (and it should vibrate), and release it.
When blue led is on press and release vol- button many times untill you enter recovery (don't keep it pressed all time)
Ah, you are absolutely right. I've never entered recovery like that on another Android before. I loaded up the "near perfect" rom and my game pad seems to be working for now, so it appears I am back in business.
How problematic is it if my slider flex cable is going bad? Will it permanently fail eventually?
The problem started in monday, I woke up and the phone was in this blue/green screen, in the screen it said that I needed to hold Power Button + Vol. Down for 7 seconds to reboot (which I did several times) and then it went again to the same screen. I browse the internet a little and found that I needed to do a factory reset, so I went to the bios by pressing Vol. Up + Power Button + Bixby Button, navigate to where it says "wipe/factory reset" - i went in there but it dont change anything and I keep stucked in the blue/green screen after reboot. After I browse a little bit more and found out that sometimes the firmware is corrupted and need to flash a stock rom again to work - so I went through some tutorials, learned how to do it, downloaded the correct most recent firmware from Sammobile (G960U1UES8ETI1), Downloaded the Odin (3.13 and 3.14) and flashed the 4 archives, odin says it passed (took 4~5 minutes). But now I'm stucked in something that looks like an ethernal bootloop in that screen showing Samsung logo. I've already tried to flash again with other version of odin. Don't have a clue of what to do now.
Sorry for the text
Please help me, all help wold be much aprecciated.