HELP! Galaxy Tab Frozen - Galaxy Tab Q&A, Help & Troubleshooting

While trying to update my Galaxy Tab's Overcome mod using the instruction on the site, I failed to read the part that said "Do note that you should NEVER update Overcome ROMs across different bases, like 1.4.x to 1.6.x or God Forbid, 1.4.x/1.6.x to 2.x! You need to do the full-shebang listed below…". When I tried to boot up the Tab, the standard T-mobile screen came up, followed by the picture attached. Does anybody have a possible fix for this?

*sighs* thats why we say read the guide fully before attempting to flash. Do that first. After you're done read it again. It will tell you everything. Start by booting into download mode and restocking to the stock firmware then follow guide directions word by word to install FULL overcome.
PS make sure your tab is well charged and your FINAL warning: REAd THE GUIDE!

Thanks...but how do you restore to stock firmware? I can't seem to find a guide that makes sense to me (I'm new to this). I don't really want to attempt to follow the guide and mess up again...

Medikay said:
Thanks...but how do you restore to stock firmware? I can't seem to find a guide that makes sense to me (I'm new to this). I don't really want to attempt to follow the guide and mess up again...
Click to expand...
Click to collapse
this is the stock firmware from t-mo, thanks to rotohammer.
http://forum.xda-developers.com/showthread.php?t=855851

Sorry for all the questions, but, after restoring to stock and following the install instructions for Overcome v2.0.0, my Tab has been stuck at the "the Overcome experience" screen for quite some time now. When going through the instructions, there was only one step I did not follow exactly; on step 6, instead of letting the Tab automatically reboot (it never did), I manually rebooted it. After that, I put the zip folder on an external sd card (the Tab would not boot and instead stayed on the "android" screen) and installed overcome...Should I restore again?

Related

Need help.

Okay for those of you who don't know, I totally bricked my phone based on a dumb decision last time and not knowing what I was doing.
I am thinking off trying to root my phone again, any advice on what rom I should root to and which is the best and most stable for the G1.
Kaos Chase said:
Okay for those of you who don't know, I totally bricked my phone based on a dumb decision last time and not knowing what I was doing.
I am thinking off trying to root my phone again, any advice on what rom I should root to and which is the best and most stable for the G1.
Click to expand...
Click to collapse
u should really go with cyanogens roms
Cyanogen's latest is pretty sweet. As long as you follow the steps correctly to root your phone, you shouldn't have any problems flashing any of the roms available. Then you can test them out, and see what you like.
does anyone know any good tuts to use to do so?
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
melterx12 said:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
Click to expand...
Click to collapse
Thank you so much everyone! You all were a huge help. I have rooted my phone successfully this time and I love it!
I followed the instructions from the link on this thread to put cyanogen on my g1 but after the skateboarding android logo faded all I got was a illuminated phone I let it sit that way for 25 minutes hoping something would happen but nada so I restored a backup. Can anyone tell me what went wrong and how I can get cyanogen working?
Nobody can tell you what went wrong since we don't know what step you skipped/didn't do right based off that statement. All we can say is follow the guide to a T. The guides are the best the communitty has to offer/has produced on how to do what you want to do. If you can't follow the guide, sadly there is nothing we can do to help beyond repeating what the guide already says.
I've got cm recovery 1.4 so that step and the ones leading to it are done right, right? Then I ran the recovery, made a back up, wiped data, applied zip drc83 defanged, applied
Cm update 4.2.13 (I think 13, whatever stable version the "latest version" link give you), applied ota radio, and rebooted (automatically took me back to recovery) rebooted again, got g1 logo followed by the cyanogen android logo once that faded all the lights on my phone came on and stayed on and I had no display (apart from the backlight).
I tried multiple times with no luck. I downloaded the cm update from my phone could that of caused a problem? Everything else was dl'ed from a pc.
What's the differance between drc83 and signed dream devphone should I try that instead?
http://forum.xda-developers.com/showthread.php?t=563679
Follow the guide to a T, since you are partialy there I will tell you what you have left:
1. Download the developer recovery ROM (This is different than drc83 by a lot)
2. Download the latest CM
3. Put both on the root of your SD card
4. Boot into recovery mode, flash the developer ROM, then flash the latest CM
5. Use the "Home" and "Back" buttons to reboot the phone
6. Tada! Success!
7. Never, ever, do anything the guide doesn't tell you to do. If it says flash file X don't flash file Y because you think it is close enough. Never do extra stuff, ie if it doesn't say flash a radio by itself, don't flash a radio by itself because it seems like a good idea.

[Q] Seriously need help :'(

Hi there, im new to this forum and Im kind of a novice to flashing and rooting.
Firstly, my device is a Samsung Galaxy Tab Sprint version.
Secondly, when I bought this tab, I got fed up of the stock software so I decided to flash the rom. I researched allot on how to do this. Then I came across a custom rom called Modaco and flashed my galaxy tab using Clockwork Recovery.
Thirdly, I started to experience a particular problem - the AutoRotation broke. Whenever I rotated my tab portrait in a way that the homescreen, back buttons etc are in the normal position, the screen itself will be upside down making it difficult for me use the tablet conveniently.
Next, I started to develop another problem, i wasn't able to boot into recovery mode so i came accross another method to remove the modaco custom rom to install the stock rom. I used ODIN and download mode. This worked but the whole autorotation situation still persisted. I downloaded a file that would attemp fixing the autorotation problem but didnt work so I tried booting into recovery mode using ADB recovery and Clockwork Recovery but whenever it attempts to get there, it then shows me the samsung logo and remains frozen.
Lastly, I have come to a conclusion that I dont want to be using custom roms and I think it has to do with the Kernal. I want my tablet to be as I just bought it, untouched, not flashed etc.
If anyone can provide me with a solution, then I will be extremely greatful. Thanks
Seriously move this to the QUESTION THREADS. You will get more help there.
Check this thread out: http://forum.xda-developers.com/showthread.php?t=1009926
thanks, i will
been here
TCstr8 said:
Check this thread out: http://forum.xda-developers.com/showthread.php?t=1009926
Click to expand...
Click to collapse
Hey I've been here already but that SW Update doesnt work. It tells me "Cannot open Binary file" can you tell me why?
See post #34 in that thread posted by cdguider.
download the : New File With Odin, Sprint_P100_Samsung_GALAXY_Tab_USB_Drivers, Installation Instructions
read and follow the .txt file that is included step by step and it will work....
I used it but the first time I was in a hurry and did not read the install txt, didn't work. I opened the imstructions and went step by step the next time and it worked no problems..
hope it works out for you.

[Q] Help: Bricked Tab, thoroughly confused, nothing seems to be working

This also seems to be fairly unique. I'm really not sure what caused it. I'll try to describe it as best I can, this has been going on all day, and between leaving for work and other stuff, I might remember this wrong.
I booted into recovery to install the latest build of Overcome, and it began to give me errors along the lines of "cannot mount E:, cannot mount SD card", crazy stuff like that. Can't wipe, can't restore backup, can't flash anything, I'm stuck.
I then attempted to do various things, including restarting, which just led me to the samsung logo. I go about searching google, decide I'm soft bricked, and follow the instructions word for word in the how to unbrick your tab thread. I download the Version 2.3.3 from Samfirmware.com, just as the guide says. I flash it.
Screen goes black. Heres the fun part, though, I can still restart the device, still boot it into recovery/download, but I can see nothing. The question I have for you guys is...now what? I'm somewhat scared to try anything else, I looked at this thread, but Odin says com4 rather than com7, and I'm not really willing to risk doing something even more wrong, just in case.
Brilliant ideas, anyone?
It doesn't matter what com# it is (it was once 5 then 23 then 8 for me lol). Look Download the stock safe v5 from the overcome website, then read the installation guide, then read it AGAIN, once you're confident enough go ahead and RESTOCK using the stock safe v5 that will give you a pure STOCK gingerbread ROM. From there you can choose to continue flashing the overcome kernel followed by the overcome ROM.
NB just make sure your tab has enough charge for that.
I hope it helps
it worked. THANK YOU<3

[Q] Boot Loop Frustration

I have searched around and can't seem to find a similar problem with a solution that I can understand. I used superoneclick to root my Verizon Galaxy 7" tablet. Everything seemed to go fine, but I really didn't have time to do anything "techy" with it. After a couple of weeks the tablet was acting kind of glitchy, nothing terrible, so I should have just left it alone. Instead I tried to do a complete factory reset. I tried several times, but it would never completely reset. My personalized wallpaper would show up, then all my apps were still there, settings didn't appear to change, etc.
I tried using Heimdall and loading new cache, param, system & zImage files. Now I am stuck in a boot loop. The machine will power up to the setup wizard, but every step generates multiple FCs until the setup wizard itself FC. Then it powers down and starts all over again. "Wipe data/factory reset" produces no change to the problem.
At this point I just want to restore my tablet to stock. No root, nothing fancy.
Can someone recommend a clear, easy to follow, current tutorial for me? I have downloaded Odin, but am uncertain which ROM I need to use. I really don't care which method you recommend as long as it is detailed (ie. written for a complete idiot to follow).
Thanks for any help.
I've gone back to stock using this tutorial, but you also can upgrade it to the Overcome GB ROM using this tutorial and you should have no issues. I know everything worked for for me using it:
Overcome Guide
Complete with filedownloads.
I think people have to stop recommending Overcome guide for CDMA tabs.
They may end up bricking their tab further.
priyana said:
I think people have to stop recommending Overcome guide for CDMA tabs.
They may end up bricking their tab further.
Click to expand...
Click to collapse
Agree!!
If your G-Tab is CDMA, please make sure to find CDMA ROMs in the Development section. Installing a GSM rom on your CDMA G-tab will mess up your device further.
Better yet, since yours is verizon, just search 'Verizon" in the Development section for Verizon ROMs (Firmwares).
E.g.:
http://forum.xda-developers.com/showthread.php?t=1325469&highlight=verizon

[Q] How do I reboot after installing ClockworkMod?

I attempted to root my SGS (which had stock Gingerbread Value 2.3.6) using a guide on the Snappyguides blogspot page (the system won't let me, as a newbie, post the URL).
Odin did its thing and then the Samsung Galaxy screen came up (just the white lettering, not the multicoloured animated S) and then... nothing. It just stayed like that for about five seconds, then the white Samsung Galaxy S came up again, then the blank screen ad infinitum.
I can access the download screen and I can access the recovery screen (which does seem to indicate that ClockworkMod v2.5.1.0 has been installed). The trouble is that none of the options seem to do anything.
I have tried searching the forum for similar problems and have read the sticky. The only answers I seem to have been able to find so far suggest flashing a new Rom.
Before I go this far, is flashing a new Rom really necessary in this instance? I have never done this procedure before, so I'm wary of messing things up even further. But obviously if the phone is past the point of no return as far as the stock Rom is concerned, then that'll be what I have to do.
I'd appreciate some advice before doing anything else to my phone though.
I now seem to be able to get the recovery menu options to respond, so maybe all is not lost. Have set it to root and it's currently converting to EXT4 and is about halfway through that.
I'm hoping once that's done, it'll be bootable.
If not, what do I need to do to make the SGS boot again? Is there any way of getting back to stock or can I only flash a stock rom back on?
Nope, still not booting. It just keeps going to the Samsung I9000 white lettering, stays there for five seconds, goes blank for five seconds, then the white lettering goes back and on, off like that forever.
So... anyone willing to help?
...
have a look in this thread http://forum.xda-developers.com/showthread.php?t=1225879
Lexrsk said:
have a look in this thread http://forum.xda-developers.com/showthread.php?t=1225879
Click to expand...
Click to collapse
Thanks for responding.
Sorry for being a n00b but I can't find anything in there that helps me. All I see is a lot of jargon about various roms, kernels and something called Voodoo.
I had a working phone with Gingerbread 2.3.6 Value. I added Clockworkmod via Odin. Now I can't get the phone to boot beyond the splash screen. It doesn't even get as far as the animated S, all I get is the splash screen going on and off every few seconds.
All I want is to get my phone working again, I really couldn't care less about custom roms etc.
If anyone can help this poor n00b, I'd be very grateful!
Incidentally, I've downloaded what I understand to be the factory rom for JW4 from sammobile.com - this is a 171MB zip file with just two files inside - a tar file called JW4_JW5_JW4 and a dll file called SS_DL.dll. I'm not really sure what to do with these to restore my phone via Odin. This is the kind of thing I need help with - the threads I've read so far don't make much sense to a poor confused n00b I'm afraid.
evilcartman2 said:
Thanks for responding.
Sorry for being a n00b but I can't find anything in there that helps me. All I see is a lot of jargon about various roms, kernels and something called Voodoo.
I had a working phone with Gingerbread 2.3.6 Value. I added Clockworkmod via Odin. Now I can't get the phone to boot beyond the splash screen. It doesn't even get as far as the animated S, all I get is the splash screen going on and off every few seconds.
All I want is to get my phone working again, I really couldn't care less about custom roms etc.
If anyone can help this poor n00b, I'd be very grateful!
Incidentally, I've downloaded what I understand to be the factory rom for JW4 from sammobile.com - this is a 171MB zip file with just two files inside - a tar file called JW4_JW5_JW4 and a dll file called SS_DL.dll. I'm not really sure what to do with these to restore my phone via Odin. This is the kind of thing I need help with - the threads I've read so far don't make much sense to a poor confused n00b I'm afraid.
Click to expand...
Click to collapse
I'll help u, I went through this when I was a noob and because I didn't know about xda I had to just figure a way out, I am sorry to say but u have soft bricked your phone, luckily its not hard to unbrick, here's a link to a post i made the other day with proper guides that I use often and they are noob friendly, the files u need to download are there but it 2.3.3 and it JW4 but it will be a start to get ur phone back to life,
If you like my posts hit thanks
Here the link http://forum.xda-developers.com/showthread.php?p=25572245
If you like my posts hit thanks
OK, thanks for that. I'm supposed to be asleep right now, so I'll come back to this later but thanks for helping.
But just to clarify for now - this will restore the phone to a working version of 2.3.3 and from there I can get back to the latest stock rom (2.3.6) via Kies, yes? I need to get into Kies anyway to restore my contacts from backups (as I haven't yet seen a way of restoring the backups except via Kies).
Thanks once again.
evilcartman2 said:
OK, thanks for that. I'm supposed to be asleep right now, so I'll come back to this later but thanks for helping.
But just to clarify for now - this will restore the phone to a working version of 2.3.3 and from there I can get back to the latest stock rom (2.3.6) via Kies, yes? I need to get into Kies anyway to restore my contacts from backups (as I haven't yet seen a way of restoring the backups except via Kies).
Thanks once again.
Click to expand...
Click to collapse
Yip I guess that is right. I have never tried it but yes it should work
If you like my posts hit thanks
Well, I did get it working again in the end by using a factory rom. Thanks for your help anyway, W1nst0n.
I do intend to attempt to root it again but this time I intend to do it properly.
Any suggestions on what may have caused the boot problem I had? Perhaps using a version of ClockworkMod that was incompatible with 2.3.6 Value?
evilcartman2 said:
Well, I did get it working again in the end by using a factory rom. Thanks for your help anyway, W1nst0n.
I do intend to attempt to root it again but this time I intend to do it properly.
Any suggestions on what may have caused the boot problem I had? Perhaps using a version of ClockworkMod that was incompatible with 2.3.6 Value?
Click to expand...
Click to collapse
Yeah that or the wrong root file for ur baseband
If you like my posts hit thanks
evilcartman2 said:
Well, I did get it working again in the end by using a factory rom. Thanks for your help anyway, W1nst0n.
I do intend to attempt to root it again but this time I intend to do it properly.
Any suggestions on what may have caused the boot problem I had? Perhaps using a version of ClockworkMod that was incompatible with 2.3.6 Value?
Click to expand...
Click to collapse
Check in about phone for the kernel version. for example mine is 2.6.35.7-I9000TDVJV6-CL530973
The important part is the bold text.
search the link that i posted earlier for a odin version and flash as PDA
Good luck
Evilcartman, when u wanna get me help find me on the I9000 q&a-ask me anything I got the answer thread, it where I spend most of my time.
If you like my posts hit thanks

Categories

Resources