[Q] Tab not booting, strange error screen is given

romskii

Senior Member
Mar 9, 2009
2,232
410
0
Viersen
So can anybody help me pls?



to tell what i've done
  • updated to Overcome 1.2.1
  • SIM Card was not accepted
  • searched via google about this and it was said, that might the SIM Card slot is damaged
  • tried to install a official ROM
  • after installation via odin, ROM was stuck on samsung boot animation for 30 minuetes
  • tried again to flash overcome rom
  • after this instruction everything was dead ^^ http://forum.xda-developers.com/showthread.php?p=11713685
  • tried to flash Overcome_Kernel_v1.0 but it failed and i rebooted and get this strange message on screen
 

romskii

Senior Member
Mar 9, 2009
2,232
410
0
Viersen
Before I forget, make sure you remove your SIM and external SDCard, also this is for GSM devices.

Cheers and good luck ;-)
ah this one you mean :p but if i really got a damaged SIM card slot, i need again a stock rom, how to manage it?

and before i forget, i can't get into downloading mode, because nothing happens when i use any button, only this screen
 

RunTimeWorld

Senior Member
Nov 10, 2010
156
28
0
Switzerland
runtimeworld.com
ah this one you mean :p but if i really got a damaged SIM card slot, i need again a stock rom, how to manage it?

and before i forget, i can't get into downloading mode, because nothing happens when i use any button, only this screen
uhmm... not sure what you mean. Have a tab since 3 days, but managed twice to get the similar screen like you, once because i turned off the device bevore the flashing was done (punch me), second time when i actually removed the memory card, however, restarting Odin 1.7 with the above posted link to the roto files, I was always able to flash - ahh.. and once I even locked the bootloader, no other ROM was flashable, ROTO still worked.
I learned my lesson, and unlocked the bootloader as described in the sticky.
You might want to check if you got the correct drivers, also other users reported that they had to drain the device, then reload for 10 - 20 mins, then it worked..
Hope this helps.