Database Info

[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!

nooby: can not update from zip file GT-P5110 4.0.4

I'm new with android.
I like to try it and put my Apple days behind me.
Never had a problem with 'rooting' it. But it’s time for something new.
I bought a Samsung TaB2 10.1 GT-P5110
After reading ( a lot ) on forums and google-ing youtube walkthroughs, I wanted to start the rooting process.
First problem ... the tablet is new but already updated to 4.0.4.
I don’t think I can undo that :-/
So I used Odin3-v1.85_3.zip and the file "GT-P5110_ClockworkMod-Recovery_5.5.0.4.tar"
All went fine but then i had to root it.
Getting into "download mode" wasn’t easy.
I think my mistake was that I have to do this immediately after I used ODIN and rebooted the tablet.
But l’ll try that later.
The real problem is that I don’t have the choice in the menu "install zip from" sdcard
im reading the toppic "[How To] ROOT- Galaxy Tab 2 10.1 [GT-P5113 / 5100 / 5110 & 4.0.4 UPGRADE or OEM".
The menu i get :
Android system recovery <3e>
Volume uo/down to move highlight:
power button to select
reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
This is NOT the CWM menu
I can see the external drive and can click on the file CWM-root-gtab2a.zip if i use "apply update from external storage" but it gives an error.
There is a link with "workaround at post 325. " but i dont know what to do.
The "workaround" is not for newbies i gues ?
ok.i read someware that the "Android system recovery <3e>" is not the CWM menu
Originally Posted by notoriousB
Uncheck the option to automatically reboot in odin. Upload the cwm tar file. When the upload is completed and shows green, power off the tablet using the power button. Then immediately reboot into cwm and apply the root zip file. Do not boot into android after loading cwm, you must go right into recovery and install the root package.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Now i can update the "CWM-root-gtab2a.zip" file.
Next step would be => go to CWM => backup BEFORE you chance anything.
I can only go in the CWM menu if i do ALL the steps again.
Gonna try this this evening.
Thanx in advance

rooting help
Okay, Im not an expert, but I've rooted several android devices before. Some steps that i go through to make sure that everything will go smoothly are:
0. Check the forums first with a search to see if the topic hasn't been answered before. READ EVERYTHING CAREFULLY. Most mistakes are usually user error. If you don't understand what you are doing, maybe you shouldn't doing it. Or you need to read up on it more.
1. Make sure that i have the absolutely appropriate packages to do what i intend to.
2. Make sure my Samsung drivers are up to date. You can install them with Kies or install them separately link in a development topic about rooting and so.
3. Download mode is accessed by powering off the tablet and holding volume down and the power button. Connect your tablet after you've set up the basics (pda file is correct for rooting, recovery, etc)
4. Go over everything and look for the right signs fora completed operation (PASS!, GOOD!, etc.)
5. Recovery mode is accessed by powering off the tablet and holding volume up and the power button. If you don't see the gear and top hat, chances are that you don't have the clockworkmod recovery successfully flashed. Try it again and if it still doesn't work, be as clear as you can with your next post why it doesn't.
I've the same model p5110 with 4.0.3 ICS build WALD2 and I've rooted and flash several times from stock to Rom to stock again. It's never easy the first time, but you'll get the hang of it soon.:good:

I am working on this just like you. I have rooted my phone but trying to root my p5113. The menu you are getting is the android stock recovery menu. When you reboot after rooting you cannot allow to boot up all the way or it will overwrite the cwm recover. So while you are rooting and it reboots, quickly unplug it and hold the power and left/volumn down key. That should do the trick

Yep,
Got it working.
Can manualy instal progs.
But im not sure im going keep this tablet yet.
Its a verry good tablet but,... maybe its because im an iphone user, and im used to cydia..
Keeping it for at least 1 month more before i decide.
Strange ,... there is no tomtom or garmin gps program ?
Are you guys using CyanogenMod ?
Dont see the point yet for using it.
Its fun using android do (boys and there toys ;-o )
a while later...
ByBy Iphone...Welkom Nexus

[Q] Problem during rooting help

I was attempting to get root access to my galaxy tab 2 10.1 running android 10.2.1 (or whatever the latest Samsung update was it is 10.2 on my phone but am sure it was 10.2.1 on the tablet.
I was following this guide that someone here recommended
http://www.ibtimes.co.uk/articles/4...-p5113-android41-jellybean-android404-ics.htm
I set usb debug and made sure the drivers were on my pc and made sure KIES was completely not running
Followed the instructions to the letter but should have worried when I found the instructions to get to download were wrong - I found on videos that it was reboot using power and right volume key. That was successful
It connected to ODIN fine and the yellow box came up
I made sure the two boxes were ticked and then searched for the file
CF-Auto-Root-espresso10wifi-espresso10wifibby-gtp5113.zip and started ODIN
it seemed to be going fine until suddenly a red box came up with update failed
Now all I can get on the device is "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
No matter how I try to restart this I get the same screen and imagine I couldn't connect to kies even if I should
Can anyone help as I am worried that I have bricked my device - I was looking for a simple way to get root without flashing a whole rom - or is that what I was doing anyway?

Here is a link that may can help you : http://forum.xda-developers.com/showthread.php?t=1722745
Try to do the point A to install CWM Recovery and root correctly the tab then do the point E to install the stock Android 4.0.4
ps : if you want to do something to your tab, try to search here before other websites, big community, good informations/tips (personnal advise) :good:

Maybe file you downloaded is corrupted , redownload it from xda or sammobile and do steps again

n0is said:
Here is a link that may can help you : http://forum.xda-developers.com/showthread.php?t=1722745
Try to do the point A to install CWM Recovery and root correctly the tab then do the point E to install the stock Android 4.0.4
ps : if you want to do something to your tab, try to search here before other websites, big community, good informations/tips (personnal advise) :good:
Click to expand...
Click to collapse
I will take a look but so far the only thing I get is the message to connect to KIES and it wont of course connect - cant get into any other modes - you would think they would have some kind of hard boot recovery button that gets you to basic screen to download the latest firmware.
And I did start here and believe that this led from a post here - I was trying to find the least complicated method of getting root access without changing what I already had too much - the only other process that I found on here seemed to have lots of people reporting problems if it wasn't a 3g model
It is beginning to look like I may have found out what bricking is - thanks for the reply anyway

would like to do that
mjrshark said:
Maybe file you downloaded is corrupted , redownload it from xda or sammobile and do steps again
Click to expand...
Click to collapse
In fact the instructions do say if it doesn't work first time, to run it again with the boxes unticked - the problem is that I cant get back to download mode, or any mode other than the message to connect to kies, so have no way of doing this. So looks like it may have bricked - is there any way of unbricking a tablet?:crying:
It's going to be an expensive mistake especially as I haven't even had the £50 cash back from Samsung yet and I would have to pay full price now to replace it,

So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium

not optamistic but will try!
samsgun357 said:
So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I will try but I don't think it is going to work. Whenever I connect the tablet by USB I get the usb connecting sound followed immediately by the USB disconnect sound - this just continues to happen every 4 seconds or so all the time that the device is connected. At the moment I have it on charge as once the error screen comes on it doesnt seem to go off for a very long time and then it wont start unless I charge it first. After a few minutes on charge - The firmware upgrade encountered an issue message comes up. I am going to leave it a while until I am sure it is fully charged and then try what you suggest - not optamistic though since I now realise that it is not even connecting properly. I just have a bad feeling about this. I had to disconnect it from the power yesterday because the error screen stays on continuously and the device starts to get warm
Assuming that I ever manage to get a stock image installed will this mean I can go back to normal kies updates - all I really wanted was the standard samsung android O/S but with super user added.
Unfortunately I had read the linked article a while back and what made me more confident was the statement that said it was "virtually impossible to brick this device"

Since it's still going into Charging mode and spitting out error messages, it's not completely bricked. It's just in a reboot loop (a.k.a. soft brick).
Keep trying to get it into Download mode. Sometimes the timing is a little tricky if it's in a boot loop.
1. Disconnect it before trying to get it into Download Mode. If it's plugged in (charger or PC), the device will go into Charging mode instead.
2. Hold the Power button for 10 seconds to make it reboot.
3. When you see the screen turn off, let go of Power and then press and hold Power and Volume Right/Up.
4. If done correctly, it will immediately go into Download Mode. If you see the Samsung logo instead, repeat from Step 2.

some progress but still stuck - any more ideas please
samsgun357 said:
So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Hi well thanks -
when I connected Odin it did show up yellow and so I downloaded the P5110 stock from from the other thread - all went well and it reported all OK and re-booted - saw the animated sequence but now it has stalled on the samsung logo and still wont connect to kies
So still stuck but at least it has moved on - The instructions on the other page were a little unclear about one stage
It said if there was pit file included to set something and tick repartition - this was all in one line and so I assumed part of the pit instruction - as there was no pit file I did not tick re-partition - I wonder if I should have done?
I have just reconnected to ODIN and the ID Com is still lit up yellow so presumably I could try running it again, or should I look on here for another stock rom - I am wondering if I have somehpw scewed up the bootloader and if so how I go about restoring it
ODIN is the only thing it connects to right now

[Q] Flashing Cyanogenmod 10 first time, won't get past boot up

Noob looking for all the help he can get!!!!!
Hi, I recently rooted my Samsung Galaxy S 2 for T-mobile, because I was sick of waiting for jelly bean to officialy come out for it, and ever since it's been a nightmare. I was running the most recent version of ICS that t-mobile has for my phone.
I got instructions on how to root at the unlocker . com
After that, I went to the Cyanogenmod website, went through their wiki and found the zip for my phone, (I also put the gapps zip on too). I booted into Clockwork mod recovery, did a back up, did a data wipe, but not a cache wipe as the instructions i was using from theunlocker.com did not say I had too. Flashed both zips from my external sd, then restarted. It booted with the Cyanogenmod name inside two spining circles. I left it like this knowing it may take a bit, and I come back 20 mins later expecting it to be done and it is in the same place i left it 20 mins ago. I decide to take out the battery, boot into Clockworkmod and restore. It booted fine back into ICS and all my data was still there, except all of the apps I had stored on my sd card would not work/show up with the icon it was supposed to. when i tapped it, it said that it was not installed on the phone. I decided not to let this worry me, as i decided to use ROM Manager app to do the job instead.
When i opened ROM Manager it prompted me to flash Clockworkmod recovery, so I did. It flashed my phone to Clockworkmod Recovery v6.0.2.7. I then went to download Cyanogenmod 10 for my phone. It downloaded with gapps 4.1. When I tapped install, it restarted my phone into Clockworkmod recovery, but did not install anything, just sent me to the main menu. So I decided i'd try getting the zip from the Cyanogenmod website again. I booted into Clockworkmod, wiped data AND cache this time. installed the zips, and restarted. I get the same problem, stuck at the cyanogenmod boot up circles spining. so i turn off my phone, boot back into clockworkmod, restore, and now i'm stuck in boot cycle with the stock ICS.
Please can anyone help me!?!?!?!

airplane888 said:
Noob looking for all the help he can get!!!!!
Hi, I recently rooted my Samsung Galaxy S 2 for T-mobile, because I was sick of waiting for jelly bean to officialy come out for it, and ever since it's been a nightmare. I was running the most recent version of ICS that t-mobile has for my phone.
I got instructions on how to root at the unlocker . com
After that, I went to the Cyanogenmod website, went through their wiki and found the zip for my phone, (I also put the gapps zip on too). I booted into Clockwork mod recovery, did a back up, did a data wipe, but not a cache wipe as the instructions i was using from theunlocker.com did not say I had too. Flashed both zips from my external sd, then restarted. It booted with the Cyanogenmod name inside two spining circles. I left it like this knowing it may take a bit, and I come back 20 mins later expecting it to be done and it is in the same place i left it 20 mins ago. I decide to take out the battery, boot into Clockworkmod and restore. It booted fine back into ICS and all my data was still there, except all of the apps I had stored on my sd card would not work/show up with the icon it was supposed to. when i tapped it, it said that it was not installed on the phone. I decided not to let this worry me, as i decided to use ROM Manager app to do the job instead.
When i opened ROM Manager it prompted me to flash Clockworkmod recovery, so I did. It flashed my phone to Clockworkmod Recovery v6.0.2.7. I then went to download Cyanogenmod 10 for my phone. It downloaded with gapps 4.1. When I tapped install, it restarted my phone into Clockworkmod recovery, but did not install anything, just sent me to the main menu. So I decided i'd try getting the zip from the Cyanogenmod website again. I booted into Clockworkmod, wiped data AND cache this time. installed the zips, and restarted. I get the same problem, stuck at the cyanogenmod boot up circles spining. so i turn off my phone, boot back into clockworkmod, restore, and now i'm stuck in boot cycle with the stock ICS.
Please can anyone help me!?!?!?!
Click to expand...
Click to collapse
First things first: the Jelly Bean update brings with it changes to the core file system organization in Android. Google "Android 4.2 Updates, Multi-User, and TWRP | TeamWin" for a brief explanation from TWRP (which, by the way, I recommend over ClockworkMod Recovery, although both can do the job). That, I believe, explains your missing data.
How are you obtaining your ROM/gapps zips? Are you downloading on your phone? If so, over wifi or mobile data? It is always a good idea to a) download on your computer and transfer the file to the phone and b) make a note of the MD5 checksum and verify the zip file before installing (any file browser worth its salt should be able to generate an MD5 sum). What it sounds like to me is your ROM download was borked in some way but it installed far enough to screw with your file system. I would recommend using your ICS backup to connect to a computer and load a ROM file downloaded from there before attempting to re-flash.

Maybe, just maybe you didn't clear cache and dalvik when installing cm. I had this problem and I realised I didn't wipe it. I wiped cache and dalvik cache from cwm and it booted fine.
Sent from my Xperia Mini Pro

ooddiittyy said:
First things first: the Jelly Bean update brings with it changes to the core file system organization in Android. Google "Android 4.2 Updates, Multi-User, and TWRP | TeamWin" for a brief explanation from TWRP (which, by the way, I recommend over ClockworkMod Recovery, although both can do the job). That, I believe, explains your missing data.
How are you obtaining your ROM/gapps zips? Are you downloading on your phone? If so, over wifi or mobile data? It is always a good idea to a) download on your computer and transfer the file to the phone and b) make a note of the MD5 checksum and verify the zip file before installing (any file browser worth its salt should be able to generate an MD5 sum). What it sounds like to me is your ROM download was borked in some way but it installed far enough to screw with your file system. I would recommend using your ICS backup to connect to a computer and load a ROM file downloaded from there before attempting to re-flash.
Click to expand...
Click to collapse
Thanks I will look into TWRP. I am getting my ROM/gapps zips straight from cyanogenmod's wiki for my phone, i get gapps from the link they provide. As for MD5, I do not know what that is other than it was generated when i backed up, and checked when i restored.

i have the same problem
i tried it with my galaxy fit s5670
i tried to flash cm-10.1-20130117-NIGHTLY-beni, some another version named of jelly bean pure rom and also TouchWiz_JB_V5
always the same thing it gets stuck at logo than nothing
i did everithing in order clear data, factory reset, clear cache, clear dalvik cache through cwm recovery
can someone help?
is it because of low int. space?
i found app named s2e to make sd card as int. memory but it didn't work
any suggestions?
thanks in advance

Here's my new problem, I'm stuck in boot loop with my restore of stock ICS, so when I go into download mode (+and- with power button while usb plugged in) I hear the "ching" that windows makes when you plug in a usb device, bu when I navigate to where removable disc should be in my computer, it is not there, so i don't know what to do, I just want my phone to work again, even if that means starting all over with stock ICS.
I appreciate your time and help.

airplane888 said:
Here's my new problem, I'm stuck in boot loop with my restore of stock ICS, so when I go into download mode (+and- with power button while usb plugged in) I hear the "ching" that windows makes when you plug in a usb device, bu when I navigate to where removable disc should be in my computer, it is not there, so i don't know what to do, I just want my phone to work again, even if that means starting all over with stock ICS.
I appreciate your time and help.
Click to expand...
Click to collapse
what ROM are you coming from?

Sounds to me like the new multi-user stuff
I experienced something similar and determined that the phone wasn't hung at that bootscreen -- it was busy moving my 18 gigs of stuff (i9300) from /storage/sdcard to /storage/sdcard/0. Apparently this is the "home data" folder for the primary user of a 4.2 device and CM10.1 (I'm assuming you're using that because of the problem) appears to be that way. It would have been nice to know beforehand that I should have just waited the 1/2-hour I needed (took about that long to move back what had been moved; very little hadn't)
So look for that 0 folder and move the contents up one -- your old ROM will (hopefully) be the way it was before. If you decide to go CM10.1 again, just wait, *really* long, at first boot -- or clean out your internal sd card to make the transition quicker.
---------- Post added at 11:06 PM ---------- Previous post was at 10:53 PM ----------
airplane888 said:
Here's my new problem, I'm stuck in boot loop with my restore of stock ICS, so when I go into download mode (+and- with power button while usb plugged in) I hear the "ching" that windows makes when you plug in a usb device, bu when I navigate to where removable disc should be in my computer, it is not there, so i don't know what to do, I just want my phone to work again, even if that means starting all over with stock ICS.
I appreciate your time and help.
Click to expand...
Click to collapse
You won't see it appear as removable storage because it's in download mode -- removable storage (and the later MTP mode) are done by the OS, and the downloader screen is much "dumber" than that.
HOWEVER, all is not lost!
Try get a ROM which you can flash with ODIN. Either something off of www . samfirmware . com (stock firmwares available there) or DarkyROM (darkyrom . com) (Sorry, can't post actual links because I'm apparently not allowed to until I've posted more stuff . I've found the S1 and S3 to be practically unbrickable in this regard -- I assume the S2 to be the same. ODIN can push a completely new ROM onto your device, rescuing it. If you download from samfirmware, there is a pdf with instructions available on their site, but it basically boils down to:
1) Download a ROM. If you are downloading a zip file, extract the .tar.md5 file inside somewhere -- this is the file you need to flash via ODIN
1) ensure you have the samsung drivers installed (they will be if you have Kies installed, otherwise google for them -- or ask, and I'll try to help)
2) put your phone into download mode (vol-down+home+power)
3) plug your phone into your PC
4) fire up ODIN, you should see a message about a connected device on-screen
5) click the "PDA" button, browse to the ROM image (the .tar.md5 file) and select it
6) the default options have always worked for me -- just click "Start". The process will take some time, but there is feedback in ODIN. Your phone should (after 1-5 minutes) reboot into a fresh, clean ROM.
If you installed a stock ROM from samfirmware.com, you'll have to go about rooting and installing Clockwork mod again. Hope this helps.

ROOT SM-T210R SIMPLE and Easy, 8gb, White

Okay so I've been at it for days and i mean like months.... when I first bought my 8 gb white Samsung galaxy tab 3 Kernel 3.4.5, android 4.1.2, model JZ054K.T210RUEAMK1 and all i have been running into is problems, like jittery display issues, or flickering display, I tried every method but none has worked but i finally found one and got it all working and running, First of all i would like to thank gr8nole for this method, and all who have helped him. So first let me explain the most easiest explanation for dummies like me, or noobs
Just and example video for visual learners http://www.youtube.com/watch?v=XolmtyvS3Yk&feature=youtu.be, but you want to click on the files i suggested on the bottom lol not what he has on his screen xD
Must Have: KIES, make sure you have fully updated rom from samsung themself which can be found on kies when you plug it in and update firmware, which your android should be on 4.1.2 and version because that's what i have
1. First lets Get all the files we need, First go download SM-T210.CWM.6.0.4.5.recovery.tar.zip at his xda post http://forum.xda-developers.com/showthread.php?t=2433853, after you have download that you will a friend name odin, which can be found here http://forum.xda-developers.com/showthread.php?t=2189539 (With odin you only want to use v3.07) and nothing else , Last but not least you want this file from gr8ole android-armeabi-universal-root-signed.zip and save that to your sd card or ext while click on usb debugging or w.e you wanna store in on tablet
so you should have odin 3.07
T210.CWM.6.0.4.5.recovery.tar.zip
android-armeabi-universal-root-signed.zip
2. Use the same method as g8nole and minor adjustments
Instructions:
1. Download ODIN on your computer (just do a google search to find it...version 3.07 will work fine). http://forum.xda-developers.com/show....php?t=2189539
2. Power off the device.
3. Restart in "Download Mode" by holding the "HOME" button, "Volume Down" and "Power" all at the same time (for about 5 seconds).
4. Hit the "Volume Up" to enter download mode.
5. Start the ODIN exe program using admin rights which means right click run as admin. I recommend un-checking Auto Reboot. DO NOT CHECK RE-PARTITION LEAVE UNCHECKED YOU BEEN WARNED (which it already should be). See notes about ODIN below.
6. Connect the device via USB to your computer. Verify the device shows as "Added" in the Message box. If it doesn't show then you need the Samsung USB drivers (just install KIES to get them) which can be found here http://www.samsung.com/us/kies/.
7. Select "PDA" then choose the T210.CWM.6.0.4.5.recovery.tar.zip.
8. Hit "START"
9. Wait for device to restart. Which means wait til odin says OKAY in the white box and the Picture ask you to reset, When the download icon under download updates is full bar, and odin says reset!, just unplug it. then restart by holding the power button down, with vol up, and home, once the samsung picture shows, only hold the up vol button, recovery mode should now be on. Select install zip, and locate the android-armeabi-universal-root-signed.zip)navigate with the up down volume button and power button to select) file, whichever you placed in sd, or exsd,
10. When all is done reboot device, then it will update your android once you turn it on, Now the anoying part, It will be rooted but what google play won't connect?, easy fix , first lets just update all the binaries since its already rooted in supersu app,
Google Store Fix, now first you have to delete your some things, your apps wont dissapear or nothing as long as you dont uinstall them, go to settings<application manager<all<google play store<clear data/cache w.e<force stop<uninstall updates<it will then ask you it will be factory installed<yes, next step, delete your gmail account if you haven't done so, now go to your time settings (Date and Time) and change it to recent date whichever today is , then open play store and it will ask you to sign in again, blah blah google needs sign up and it should be up and running
ALL DONE, remember this is for people who have run into flicker display problems, which is caused by kernal issue with our model, but with stock rom itself we can universally root it through odin with just that simple method which took me like 3 mins lol to do
Grats guys! you have root and cwm now who doesn't want that enjoy and thanks to developers hard work! and my ambition!

this worked for my SM-T210 also. Thanks heaps for this how-to!

Ok my device is already rooted but I would like to install CWM Recovery on it. So I can make a backup. Or does anyone have the stock kernel for it
Sent from my SM-T210 using xda app-developers app

Odin 3.07
Link was busted so I posted a new one for lazy people.
http://www.android.gs/download-odin-3-07/
or something like this??
http://forum.xda-developers.com/attachment.php?attachmentid=1168421&d=1341114315

drolgnir said:
Link was busted so I posted a new one for lazy people.
http://www.android.gs/download-odin-3-07/
or something like this??
http://forum.xda-developers.com/attachment.php?attachmentid=1168421&d=1341114315
Click to expand...
Click to collapse
But you can also use Odin 3.09.
I'm portant is that you flash always the newest CWM / TWRP or PhilzTouch Version about the new updater scripts.

cspiresucks said:
Ok my device is already rooted but I would like to install CWM Recovery on it. So I can make a backup. Or does anyone have the stock kernel for it
Sent from my SM-T210 using xda app-developers app
Click to expand...
Click to collapse
Your best option is to get CWM sknce it will be your original backup instead of a Rom created from another device.

SM-T2105?
Hello,
I came here beacause of a shorcut link given by @gr8nole and another member (I forgot sorry).
But my English must be to bad, i read and re-read, still don't find the answer...
I have the G Tab 3 kids model, SM-T2105.
@bierma32 says: "Important is that you flash always the newest CWM / TWRP or PhilzTouch Version"
Could you tell me wich one is the best, CMW or TWRP, plz? (the last I can find for T210 is CMW-6.0.4.9 and/or TWRP-2.8.2.0)
More important, do you know where I can find the zip of a rooted stock rom, including that 'kids' stuff? (SM-T2105). Or will I not loose the stock rom? Is there no wipe? Sorry, I don't understand.
I want to root, because of lack of space, and the rest.. but I don't want to loose that..
And the most important, "last but not least", I could not find the zip " android-armeabi-universal-root-signed.zip", so can you help me please, putting a mirror or so? Or could it work only with flashing a SuperSU zip? Not so easy, right?
As you maybe can read, I am a newbie in Android rooting. Or is there another way to do?
Thanks for reply.