Database Info

[Q] My Nexus S won't boot at all... Help, please

Hi
I'm facing a problem with my Nexus S, before it was working... but, unfourtunatlly i just make some modification in the system file and now my phone not working and stuck at the google logo black screen... exactly, i think the problem in the java runtime.jar file that was in the system folder, i replace it with another file and all that done since i want to add another language to the system so that it can understand it. but, the device now is not working....
I tried to enter the recovery mode and wipe all data, but nothing change. its keep the same. so i tried also to format the system (from the recovery) since, the modification done in that folder... also, its not working....
So, I think the best way right now is to return it to the default rom(official one from google) , i download it, and tried to flash it using the "fastboot" command but it keep give me error when writing for system.img file....
What can I do right know ??? I can't use my device at all...
Help me Guys, please.....

For future reference Factory wipe doesn't touch /system...just /data.
If you formatted your /system, and it actually formatted, all you can do now is restore a working system.
If you didn't make your own nandroid backup of the system (and you ALWAYS should in the future before messing with system level modifications) to have a known working configuration, then your best bet in my opinion is to go to this thread: http://forum.xda-developers.com/showthread.php?t=884093
Download the nandroid image from there and flash it to your phone using Clockwork Recovery.
Good luck.

distortedloop said:
For future reference Factory wipe doesn't touch /system...just /data.
If you formatted your /system, and it actually formatted, all you can do now is restore a working system.
If you didn't make your own nandroid backup of the system (and you ALWAYS should in the future before messing with system level modifications) to have a known working configuration, then your best bet in my opinion is to go to this thread: http://forum.xda-developers.com/showthread.php?t=884093
Download the nandroid image from there and flash it to your phone using Clockwork Recovery.
Good luck.
Click to expand...
Click to collapse
But, The question here is.... how can i flash it when i can't get access to the memory(since the Nexus S doesn't have sd memory slot) and to the system ??
when i enter the recovery, all i can do is use the fastboot command.... can i use it here ??
Thanks alot .....

If you boot into Clockwork, you should be able to use it's mounts menu to mount the sdcard...then use adb to push the files to your sdcard. adb should be active and working in clockwork.
If that doesn't work out for you, you could also try the Odin and "download mode" approach from this thread: http://forum.xda-developers.com/showthread.php?t=947950

distortedloop said:
If you boot into Clockwork, you should be able to use it's mounts menu to mount the sdcard...then use adb to push the files to your sdcard. adb should be active and working in clockwork.
If that doesn't work out for you, you could also try the Odin and "download mode" approach from this thread: http://forum.xda-developers.com/showthread.php?t=947950
Click to expand...
Click to collapse
Thank you sooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo much distortedloop....
as what u said.... the mount already available in the clockwork.. but i didn't see it before.....
Now i got my Nexus S back to me again.....
Thank u soooooooooooooo much Man... I appreciate it

abd640 said:
Thank you sooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo much distortedloop....
as what u said.... the mount already available in the clockwork.. but i didn't see it before.....
Now i got my Nexus S back to me again.....
Thank u soooooooooooooo much Man... I appreciate it
Click to expand...
Click to collapse
Glad you're up and running again.

Hello guys
I have the same problem, but i guess for different reasons.
I applyed the superboot from the modaco´s forum on my nexus s, but I guess I did it with the wrong version (i had got the 2.3.4 ota before doing so and used a 2.3.3 version) and now my phone won´t boot. My rom was stock. Now, it remains on that google initial screen. I can´t get to upload anything for the device since I guess the usb debug mode is off, although when I connect the device to the computer, the system shows the usb driver. I guess my device is GT90 something, can´t say for sure. Have to check at the box.
That said, I´d like some help on what to do about it.
I´ll be forever grateful!

ectole said:
Hello guys
I have the same problem, but i guess for different reasons.
I applyed the superboot from the modaco´s forum on my nexus s, but I guess I did it with the wrong version (i had got the 2.3.4 ota before doing so and used a 2.3.3 version) and now my phone won´t boot. My rom was stock. Now, it remains on that google initial screen. I can´t get to upload anything for the device since I guess the usb debug mode is off, although when I connect the device to the computer, the system shows the usb driver. I guess my device is GT90 something, can´t say for sure. Have to check at the box.
That said, I´d like some help on what to do about it.
I´ll be forever grateful!
Click to expand...
Click to collapse
try to boot into bootloader. root the phone n install a recovery.img, then reinstall a custom rom or the stock rom.

deeren said:
try to boot into bootloader. root the phone n install a recovery.img, then reinstall a custom rom or the stock rom.
Click to expand...
Click to collapse
The thing is that i already have clockworkmode installed and i can access it through bootload, in fact is the only thing i can do. My problem is that i just can´t send the recovery.img from the pc to the phone. And I also think that the usb debug mode is unavailabe, so I can´t activate it.
I´m new to this thing so the only way I could move files into the phone was through windows explorer drag and drop. Honestly I´m lost without it.
Is there a different way to push it to the phone ?
I understand this forum is intended to more experienced users, and for that I apologise.

Guys I found a solution by enabling USB from clockwork! Thanks! Keep the good work!
Sent from my Nexus S using XDA Premium App

Hello "ectole", could you let me know how you get out of it. I am in the same problem. I followed this guide http://forum.xda-developers.com/showthread.php?p=13800735#post13800735 to root my phone, now I always boot into clockwork. I can I boot into Nexux again?

Hi guys,
I'm in a similar situation. I tried to install CyanogenMod 7 to my Nexus S (ATT), got stuck at the skating dude.
Booted back into Clockwork, and tried to flash back to the stock firmware, but I think I accidentally flashed the wrong one (for the 9020T instead of 9020A) build. Now I can't get into ClockworkMod or anything on the screen whatsoever.
Does anyone have any tips at all? I'm really screwed here, would appreciate it a lot...
J

Hey bante just go to clockwork then to mount/dismount menu and the last option should be mount USB storage. Mount it and stay there and your PC should see the sd card. Then upload what you want.
Sent from my Nexus S using XDA Premium App

HELP!!! Odin bricked my Nexus S i9020a
I attempted to use odin to restore my phone. Could not get past bootloading screen. Put phone in recovery mode and used odin and grh78 firmware.
Odin went thru the whole process and said success, then my phone shut off, and will not power back on. Any ideas?

OkNewMedia said:
I attempted to use odin to restore my phone. Could not get past bootloading screen. Put phone in recovery mode and used odin and grh78 firmware.
Odin went thru the whole process and said success, then my phone shut off, and will not power back on. Any ideas?
Click to expand...
Click to collapse
Which phone version you got?
Sent from my Nexus S using XDA App

OkNewMedia said:
I attempted to use odin to restore my phone. Could not get past bootloading screen. Put phone in recovery mode and used odin and grh78 firmware.
Odin went thru the whole process and said success, then my phone shut off, and will not power back on. Any ideas?
Click to expand...
Click to collapse
By 'recovery mode', do you mean download mode? (you hold both vol up and vol down then plug in USB)

My Nexus s not boot at all
Hi
I'm facing a problem with my Nexus S, before it was working... but, unfourtunatlly i just make some modification in the system file and now my phone not working and stuck at the google logo black screen...
it doesn't entering the recovery mode. it only stucks at the google black logo screen
What can I do right know ??? I can't use my device at all...
Help me Guys, please.....

shavinder said:
Hi
I'm facing a problem with my Nexus S, before it was working... but, unfourtunatlly i just make some modification in the system file and now my phone not working and stuck at the google logo black screen...
it doesn't entering the recovery mode. it only stucks at the google black logo screen
What can I do right know ??? I can't use my device at all...
Help me Guys, please.....
Click to expand...
Click to collapse
flash either clockwork or twrp recovery via fastboot.

but how can i do this thing

jstennis1591 said:
Hi guys,
I'm in a similar situation. I tried to install CyanogenMod 7 to my Nexus S (ATT), got stuck at the skating dude.
Booted back into Clockwork, and tried to flash back to the stock firmware, but I think I accidentally flashed the wrong one (for the 9020T instead of 9020A) build. Now I can't get into ClockworkMod or anything on the screen whatsoever.
Does anyone have any tips at all? I'm really screwed here, would appreciate it a lot...
J
Click to expand...
Click to collapse
Sounds like you flashed i9023 software. You could try Odin. Does your computer recognize the phone?
Sent from my Nexus S 4G using xda premium

[Q] How can I unbrick my Infuse with a mac?

Well I was caught my the new MIUI ROM i saw this morning and decided to switch from Bionix. I have flashed many phones and farmiliar with the process. I left my phone alone while the install occured. I watched it wipe data and cache. Now when it powers up, the samsung logo appears for 2 seconds and a quick I9000 logo flashes for like .25 of a second. The 3 button method to force it into recovery. I dont have a usable copy of windows to boot camp from my mac so ODIN is currently not an option.
I can get the phone into download mode so i know its not a lost sailor, i just need a mac solution without booting windows. I really dont want a refurb replacement from warranty either

You want heimdall.

Yup. heimdall rocks

samsung screen of death...
LinuxBozo said:
You want heimdall.
Click to expand...
Click to collapse
SO here goes...
first off i am rooted, have all appropriate drivers, etc, have used dab to root.
I am a total newb, and was experiencing issues flashing a new ROM. when trying to install the zip through cwm the phone said "signature verification failed" or something to that extent. so being the deductive thinker that I am, I formatted everything: boot, system, sd, etc. After doing this, I realized that I totally wiped out all the files on the internal sd.
so i downloaded the heimdall one click- it connects but fails regardless of whether i flash boot loader.
i can access blue 3e recovery and download mode.
now. i want to know if it is possible to push or even install a ROM through adb. I've been playing around with it all day and have gotten nowhere.
i thought maybe i could load up a rom to an external sd but obviously you can't mount an extsd in cwm.
am i screwed?
ill gladly donate through paypal if someone can help me get my baby up and running again. i do not want to be using my nokia from middle school anymore!!
thank you in advance for ANY help you can give me.
Rob

[Q] botched ROM load, now stuck in recovery hell

I got in a SK4g for my wife intent on upgrading her current phone. I own a 4g myself, and have Rooted/ROM'd it with no issues, we we thought it best to get her the same phone for ease of use/manipulation.
I got the phone in and used superoneclick to root it, then went through the process of putting CWM in place and installing GenericGinger_2.0_SK4G. The process ran smooth as glass (as expected) until it got to reboot. On reboot it hung up on the sidekick screen. After about an hour of waiting I pulled the battery and restarted the machine.
It came back up in recovery mode with the stock recovery (blue) text. Since then I haven't been able to get it to do anything but restart into that recovery screen. Odin doesn't see the phone in download mode and t839-Sidekick4G-UVKG2-One-Click does nothing. It shows it uploading, reboots the phone, and I'm back at the blue text. flashing the bootloaders with One-Click shows success on everything *except* uploading the bootloaders. If I tell it to re-install packages I get a 'cannot validate signature' response. I've tried using android commander to push CWM's recovery file to the phone and get 'permission' denied.
I've done a lot of searching on this site, trying most suggested fixes I've come across with no luck.
what can be done with this phone to get it back in operating condition?
Thanks in advance!

try installing kies odin wouldnt see my phone until i installed it

Kies installed and Odin saw the phone. excellent, thanks!
now, the next issue... lol
I used Odin to push KD1OdinSTOCK onto the phone. it's doing more than it was (going to the initial sidekick screen then dumping to recovery). Now it'll load through the sidekick and samsung splash screens, then reset and do it again. The same thing happens when I tried StockKG2ODIN. I'm using the sk4g.pit that I pulled from this site, could that have anything to do with it/is there another one around that I could try? Anybody have thoughts or ideas on what to do next? I've tried using t839-Sidekick4G-UVKG2-One-Click again, but it nuked the drivers kies put into place and dropped the phone back to what it was doing before.

okay, I did some light reading of this thread here
and followed the directions closely. I also went through sduvick's list of things to do with the following results:
Black screen, no logo.
1. Get into download mode by using VolDown+Touchpad+Power
2. flash full sk4g.tar.md5 as posted.
device will boot through the logo and splash screens, then repeat. note: if I leave the USB cable plugged in on reboot it will go to the battery screen, otherwise it just boot loops.
_________________________________
logo only
1. Download mode
2. Flash full package
device boot loops
_________________________________
Can't flash recovery/boot/sbl
1. Download mode
2. use PIT only, run with repartition checked
3. reboot/reDownload mode
4. run the full image in Odin.
PIT only returns a black screen on the device. running the full image in afterward returns to the boot loop.
_________________________________
Anything else
1. Download mode
2. Full tar.md5 flash in Odin
3. Ask if it doesn't work
okay, so I'm asking...
I'm still able to boot into recovery mode (blue text).
I've noted a bit of strange behavior when trying to boot into download mode. holding vol down + trackball + power does nothing. however, if I plug the phone in while powered down while holding down the trackball it'll boot into download mode, no power or vol down required.

If you can't flash with Odin, you may have a hardware problem.
Judging from your issue with installing Kies, you had a driver problem previously.
Seems that you are bumbling in the dark here. Once again, people need to be better prepared to Odin their devices before they start modding them.
In fact, getting Odin working should be the first thing a person should do with their phone after rooting and installing CWM.
Anyhow, try a different version of Odin. If that doesn't clear up your problem, I suspect some bad blocks in your flash memory are responsible here. It's a dorment issue that would really only be a problem when you flashed the device. If that's the case, you have a new paperweight.
Good luck.

i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda

I don't think the problem is that I can't flash with Odin, but that the device isn't loading the ROM that's flashed. poking around in the filestructure with android commander after a fresh load shows that the system makes it onto the phone.
Speaking of poking around with Android Commander, I've noted that the device is software rooted, but not hardware rooted. the default.class file shows ro.debuggable set at 0 where it should be 1. this is keeping me from just pushing the CWM recovery onto the system and restoring the backup I made before getting into this mess. Anybody want to help me pull/edit/flash the image to change that?
As for a driver issue, that's a good possibility given that the one-click uses a driver set, kies mini uses another, kies has a different one yet and we (as a community) started screwing with the t839's using vibrant drivers. I've got them all. thusfar the only drivers I've found that work with both flavors of Odin I have (1.61 and 1.85) would be those that came with the Kies (thanks for the tip pmp326).
On bumbling in the dark, yes, yes I am. There isn't much of an instruction manual for Odin past what's written here, and 90% of that is 'put your phone in download mode, connect Odin, plug the pit in pit and the tar in PDA make sure only auto-reboot is checked and hit start'. to be honest I haven't had to use the program previously as the stock one-click actually worked on my T839. This new device is being ... difficult.
the dormant bad blocks issue you spoke about, was this something found in new-out-the-box phones? I haven't seen a lot about that in the threads, can you point in at more info, please?
at any rate, it doesn't matter which version of Odin I use, I got the same result from both. I tried using a different cable/different USB port as well. I haven't tried using a different system (yet), but don't want to go through all the trouble of setting up everything on another box. Win7 is finicky enough, trying to get everything operating on Server2k3 would most likely end up a challenge. *lol*
I'll try repartitioning with KG1 when I get back to the house.

Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.

also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin

orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
I've gotta pop the debug lock in the default.class to be able to push anything into the system folders with Android Commander. I've found a nice walk-thru to do this, it just requires a little knowledge of c++ and some patience. with any luck I should be able to pull default.class out of its img, edit it and flash that back (most likely with Heimdall since it can do itemized flashing).
pmp326 said:
i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda
Click to expand...
Click to collapse
tried it, no joy.
pmp326 said:
also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin
Click to expand...
Click to collapse
tried this, brings me back to the boot loop.

orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
currently I'm running into issues with getting ADB to push onto the system as the system is claiming it isn't rooted. Is there a way I haven't read about or found to root the phone without getting into the actual O/S (i.e. from the blue recovery screen)?

If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)

rpmccormick said:
If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)
Click to expand...
Click to collapse
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.

Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
I like turtles.

Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
Even the end... I mean, your not trying to odin a "tar.md5" are you?

rpmccormick said:
Even the end... I mean, your not trying to odin a "tar.md5" are you?
Click to expand...
Click to collapse
No....

Sorry man. I've never had to ODIN (this phone). I say check the md5 to make sure you downloaded a good copy, and maybe try a different USB cable. The ADB method seems nutz... if it doesn't boot after a successful ODIN, the phone is probably a paperweight.
Good luck!

[Q] Possible brick? Tab 2 7.0 GT-P3110

OK, I did watch the n00b guide and I did spend nigh-on 3 hours, no exaggeration, trying to find my solution among previous posts.
But it looks like I've really messed up.
Idiot that I am, I installed a P3113 ROM, and it worked, too. It was OK. But I was a bit worried so I thought I'd try to get a proper P3110 ROM going. I elected to go back to stock imagining that this would be the safest course.
What I think I did was wipe the thing altogether with some good old fashioned ham fisted clumsiness and not paying attention. I tried then getting a stock ROM and flashing it with ODIN. ODIN seems to think it's done the job, it goes to PASS and so on, but when I try to turn on I get the Tab 2 screen and then everything stops at the Samsung jingle screen. I can't power off completely, it just restarts. I CAN get into recovery and download but I can't do much else. ODIN mode says my Current binary is Samsung Official, so it's done something but I'm getting the fear.
When you stop laughing at me can you please advise my wisest course of action? Stupid thing is I can flash and mess around with my Desire S and GNex until the cows come home, but this has me flummoxed and greatly worried.

Can you go into recovery and wipe /data or factory reset?

imnuts said:
Can you go into recovery and wipe /data or factory reset?
Click to expand...
Click to collapse
I can. I tried that but it seems not to help. Thanks anyway.

Go to www.samfirmware.com
Download firmware and go to download mode and reflash again
Or if recovery stock so connect with kies and their is option to restore or recover firmware
Or if recovery Cwm, put cm10 or so in external sd ( copy from computer to card) then factory reset , delete cash and delete dalvik then flash it
Sent from Galaxy S2 or Galaxy Tab2

Panic over, but thanks for your time chaps.
Let joy and relief flow unconstrained!
It's taken six hours but I installed and reinstalled and factory reset half a dozen times with P3110XXBLH1 and P3110XXBLH2.
And then I tried P3110XXALD4_OXALD4. This has worked.
That's a weight off. Sorry to bother the threads, I was starting to panic a bit. Typical.

Mohamedselim said:
Go to www.samfirmware.com
Download firmware and go to download mode and reflash again
Or if recovery stock so connect with kies and their is option to restore or recover firmware
Or if recovery Cwm, put cm10 or so in external sd ( copy from computer to card) then factory reset , delete cash and delete dalvik then flash it
Sent from Galaxy S2 or Galaxy Tab2
Click to expand...
Click to collapse
Please I need help restoring my P3110 to it`s factory settings.
I was trying to change display density with LCD Density PRO and now I`m stuck with a bootloop. I can access both recovery and download modes, so I think an ODIN image will restore the tablet back again. I found some here http://forum.xda-developers.com/showthread.php?t=1838072
I purchased my P3110 in Brazil and none of those ODIN images refer to the brazilian model. Is there a problem if I just pick one of those (like the german or the UK firmware) and flash it to the brazilian P3110?
BTW, I can't mount my external_sd. CWM 6.0.1.1 just says it "can`t mount external_sd"

help
what recovery should i install should i install CWM or Phils
i want to install lollipop in gt-p3110 will it work or kitkat?
if u guys could help me i appreciate that thanks u guys
Sam Adams:fingers-crossed:

Still having Tab2 woes

I have an earlier thread here http://forum.xda-developers.com/showthread.php?t=2107600 but that is now buried on page 2 and might be missed by new readers. After a disastrous time trying to root my Galaxy Tab 5100 I did manage with the help of people here to flash the recommended stock ROM - however while the tablet goes through its boot sequenece with the aminated Samsung sign - it sticks when it gets to the plain Samsung logo and wont go further.
Odin reported that it installed OK and the tab rebooted as it should but only this far - not sure what I should try next to get my stock Samsung image back and working. One thing I didn't do was to tick repartition because the instructions only said to do this when a certain type of file was included in the package, and it wasn't. Should I have ticked this after all, if so I can try the same thing again if I can force it back into download mode again. (though as the yellow pane still shows in odin when connected I wonder if I can just go ahead anyway)
I have also been looking for rooting software and came across this
http://root-android.org/?version=Tablet&country=Samsung&ios=Galaxy+Tab+2&submit.x=63&submit.y=104
I am wondering if next time (assuming I ever get it working!) I would be better shelling out $30 and getting software to do it all for me - is this any good? has anyone used it or had reports about it? I wish I had seen this before I read "that it was almost impossible to brick the tab 2"
Also I would like to have root access on my S3 as well but wouldn't dream of risking this I don't think now

gbswales said:
I have an earlier thread here http://forum.xda-developers.com/showthread.php?t=2107600 but that is now buried on page 2 and might be missed by new readers. After a disastrous time trying to root my Galaxy Tab 5100 I did manage with the help of people here to flash the recommended stock ROM - however while the tablet goes through its boot sequenece with the aminated Samsung sign - it sticks when it gets to the plain Samsung logo and wont go further.
Odin reported that it installed OK and the tab rebooted as it should but only this far - not sure what I should try next to get my stock Samsung image back and working. One thing I didn't do was to tick repartition because the instructions only said to do this when a certain type of file was included in the package, and it wasn't. Should I have ticked this after all, if so I can try the same thing again if I can force it back into download mode again. (though as the yellow pane still shows in odin when connected I wonder if I can just go ahead anyway)
Click to expand...
Click to collapse
Have you tried a factory reset from recovery? If you've restored the stock ROM, then all you need to do is the factory reset to get things working again. Don't repartition unless you really need to.
gbswales said:
I have also been looking for rooting software and came across this
http://root-android.org/?version=Tablet&country=Samsung&ios=Galaxy+Tab+2&submit.x=63&submit.y=104
I am wondering if next time (assuming I ever get it working!) I would be better shelling out $30 and getting software to do it all for me - is this any good? has anyone used it or had reports about it? Also I would like to have root access on my S3 as well but wouldn't dream of risking this I don't think now
Click to expand...
Click to collapse
I can't see any reason you should spend that kind of money given how easy the CF-AutoRoot is. In fact, that product looks very shady to me. "Root Any Android Device"? Well, there's lots of devices out there that nobody's been able to root, or devices that take a lot of work. I can't believe there's a single app that'll work across every Android device with a single click.

Be careful, which stock ROM have you flashed? I would use this sequence
flash the stock ROM
then immediately
flash CWM recovery, use CWM recovery to wipe the data (wipe data/factory reset).
Then reboot

CWM ?
DigitalMD said:
Be careful, which stock ROM have you flashed? I would use this sequence
flash the stock ROM
then immediately
flash CWM recovery, use CWM recovery to wipe the data (wipe data/factory reset).
Then reboot
Click to expand...
Click to collapse
Well I followed one of the posted routes on this forum, downloading from a list of recommended files for each version, and it mentioned nothing about CWM which I know nothing about. I have to say that everyone's definition of "easy" on here - I find complicated and difficult - I know my way around windows but android seems much more complex. The only reason I wanted to have root in the first place was to be able to make a complete image back up that would make it easy to restore my device without having to re-download all my software and set up. I do it with windows all the time. To me "easy" is, download and install something - click go - done! Even getting the device to go into download mode in the first place is a very hit and miss affair (as others say on here too) clearly Samsung don't want you to do this.
The other problem is that while the tablet is in this state it wont turn off, just reboots itself when you do and the screen stays on - so unless you leave it plugged in 24/7 - I start each time with a flat battery that I have to recharge before I can try something else

This is the route I followed
DigitalMD said:
Be careful, which stock ROM have you flashed? I would use this sequence
flash the stock ROM
then immediately
flash CWM recovery, use CWM recovery to wipe the data (wipe data/factory reset).
Then reboot
Click to expand...
Click to collapse
I got this through earlier posts - the only thing I didn't do was to go into recovery and reset in step 2 because this simply wasn't possible - the device was stuck on the error message and no amount of button pressing did anything other than restart to the same screen. By this stage I couldn't even go back to check what version of android I was running - it would have been the latest jelly bean distributed to UK.
I also didn't check re-partition as in 6. because there was no pit file in the download
E. Restore to stock
THIS WILL WIPE YOUR DATA!
4.0.3 for p5100: https://hotfile.com/dl/155804946/76b...XALD9.rar.html
4.0.3 for p5110: http://www.hotfile.com/dl/159635395/...3_PEO.zip.html
4.0.4 for p5100: http://www.hotfile.com/dl/165065733/...1_SER.zip.html
4.0.4 for p5113: http://www.hotfile.com/dl/164415704/...5_XAR.zip.html
4.0.? for p5113: http://69.46.67.99/GT-P3113_XAR_1_20...ldcgx9tzmx.zip
4.0.4 for p3100: http://samsung-updates.com/fw/Samsun...3kdo3qe503.zip (PIT files: 16Gb p3100, 8GB p3100
Note: for more language options for stock ROM's for the tab 10, go here.
1. Unzip the downloaded ROM. If there is a file ending in .pit, skip to step 3
2. Reboot into recovery and select wipe data/factory reset.
3. Reboot into Download Mode.
4. Unzip/unrar the stock firmware
5. click PDA and find the stock file (PDA/PLATFORM file, the largest one).
6. Click PIT and open the .pit file you downloaded if one was included with your ROM. Check Re-Partition in ODIN
7. OPTIONAL: if you want to flash the bootloader and/or csc, you can select them as well. If you don't know what that means, you don't need to do it.
8. Click Start.
9. Enjoy!

Help please - this is where I am at the moment - some SIMPLE help needed please
I tried to install what I thought was the stock ROM - it appeared to install but wouldnt boot past the samsung screen. I now realise (a) that I may not have followed the full correct procedure and (b) may have downloaded the 5110 rom instead of the 5100 rom - silly mistake I know.
However reading all the guides I can find there doesnt seem to be a simple way I can find of restoring the standard un-rooted rom so that I can go back and try again. All of the things I can find seem to included downloading something onto the external card but cant do that as I cannot access it and don't have an external card reader.
What I can do now is
boot into download mode
connect to ODIN and see the yellow block
It will not boot normally past the samsung splash screen
and cannot connect to KIES in any mode (I do have the drivers installed and have connected before)
I also have no idea now what is installed on it because I cant get to the system to see!
Is there an easy way to install a stock samsung rom from this point? I don't mind if data is lost, I have nothing important on there and wouldnt mind re-installing apps as I had accumulated far too many anway - really I just want to get my tablet back the way it was from the factory but with the 4.2 jelly bean installed (though if it went back to an earlier version and I could update in Kies that would be ok too)
Can anyone give me simple instructions for doing this using just ODIN and my computer without involving the external card - please.
After that I will be looking for an equally easy way to root it again
I will credit you with a good answer if you can help -as well as appreciating it.

gbswales said:
I tried to install what I thought was the stock ROM - it appeared to install but wouldnt boot past the samsung screen. I now realise (a) that I may not have followed the full correct procedure and (b) may have downloaded the 5110 rom instead of the 5100 rom - silly mistake I know.
However reading all the guides I can find there doesnt seem to be a simple way I can find of restoring the standard un-rooted rom so that I can go back and try again. All of the things I can find seem to included downloading something onto the external card but cant do that as I cannot access it and don't have an external card reader.
What I can do now is
boot into download mode
connect to ODIN and see the yellow block
It will not boot normally past the samsung splash screen
and cannot connect to KIES in any mode (I do have the drivers installed and have connected before)
I also have no idea now what is installed on it because I cant get to the system to see!
Is there an easy way to install a stock samsung rom from this point? I don't mind if data is lost, I have nothing important on there and wouldnt mind re-installing apps as I had accumulated far too many anway - really I just want to get my tablet back the way it was from the factory but with the 4.2 jelly bean installed (though if it went back to an earlier version and I could update in Kies that would be ok too)
Can anyone give me simple instructions for doing this using just ODIN and my computer without involving the external card - please.
After that I will be looking for an equally easy way to root it again
I will credit you with a good answer if you can help -as well as appreciating it.
Click to expand...
Click to collapse
What you need to do is to download the stock ROM for your 5100.
Go to www.samfirmware.com and put "GT-5100" into the search box. You'll see a list of the stock firmware for your device. Pick the appropriate firmware for your country and click "download".
Start up ODIN. Click on the "PDA" button and open the firmware file you downloaded above.
Restart in downloader mode (power and volume up), and connect the tablet to your PC. ODIN should now show the device.
Make sure repartition is not checked, and click on "Start". When it finishes, you now have stock firmware installed.
Power off, then restart in recovery mode. (Hold power and volume down.)
Choose "wipe data/factory reset" by using the volume keys to move the highlight, then pressing the power button to select an entry.
Once it's finished booting, you should be back to normal.

Thanks K1MU for this information which at least looks clear - the only problem I have is when I put in the model etc when I get to country it offers me only 3 choices
UK (BTU) GB (O2) or GB (vodafaone)
My phone was purchased from Amazon and is unlocked so I am worried if these might lock me to a carrier which I wouldn't want
I wonder if BTU is the unlocked one as it doesn't sound like any provider I know - but I am not sure
will post on their forum as well

I think I am getting more and more muddled by the minute (sign of old age I fear) I realise now that I have a p5110 - wifi only and not p5100 3g and wifi.
This means in all probablilty I downloaded the correct rom in the first place. As I had not done the factory reset afterwards so tried that - it appeared to work ok but when I restarted it just played the samsung tune and moving image - then went to "Samsung" and stuck there as it was before.
I am downloading the p5110 wifi only rom from Sam's site - awful download programme they use which doesn't accept paypal even to sign up for faster downloading - I will then try following exactly what you have suggested and keep my fingers crossed

thank you
k1mu said:
What you need to do is to download the stock ROM for your 5100.
Go to www.samfirmware.com and put "GT-5100" into the search box. You'll see a list of the stock firmware for your device. Pick the appropriate firmware for your country and click "download".
Start up ODIN. Click on the "PDA" button and open the firmware file you downloaded above.
Restart in downloader mode (power and volume up), and connect the tablet to your PC. ODIN should now show the device.
Make sure repartition is not checked, and click on "Start". When it finishes, you now have stock firmware installed.
Power off, then restart in recovery mode. (Hold power and volume down.)
Choose "wipe data/factory reset" by using the volume keys to move the highlight, then pressing the power button to select an entry.
Once it's finished booting, you should be back to normal.
Click to expand...
Click to collapse
Although I thought it had got nowhere after wipe restore - when I turned it back the next day I arrived at the start up guide - admitedly it was 4.0.3 and in Portugese but after exploring settings and working out what to click i got it back to uk english - it has now connected to kies ok and is currently downloading the latest firmware - thanks partcularly to the last poster and to all others who helped - I will go through and thank you others too,
Point is now - once I have jelly bean can I get root access easily -without installing another custom rom - ahh well tomorrows problem