Database Info

[Q] Problems with LGP999 Wind

A friend and I were trying to update his Wind LGP999 phone from 2.2 to 2.3. So we followed the instructions from this thread http://forum.xda-developers.com/showthread.php?t=1327929 and things were going good until we got to the connection part. The program continues to freeze and close and the phone is stuck on the s/w update please wait while updating screen. Now we've tried hard reset and even tried to reinstall V10G_00 but the program still freezes. I've been doing some research and unless I haven't searched enough I haven't seen any thread or post with someone with the same problem. So any help in this would be greatly appreciated.
Edit: Done some more research and found How To Load a Custom ROM by David Cogen from The Unlockr and follower his steps and things seemed to work out pretty well but I still get this screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
can anyone please help with this?

You need to use nvflash to install clockwork recovery then you will be able to install whichever rom you want. There are a few threads out there showing how to install the recovery permanently.
Don't worry you aren't bricked
Edit: Here is a thread that will be useful for ya:
http://forum.xda-developers.com/showthread.php?t=1056847
Pin it to Win it.

I.R.Chevy said:
You need to use nvflash to install clockwork recovery then you will be able to install whichever rom you want. There are a few threads out there showing how to install the recovery permanently.
Don't worry you aren't bricked
Edit: Here is a thread that will be useful for ya:
http://forum.xda-developers.com/showthread.php?t=1056847
Pin it to Win it.
Click to expand...
Click to collapse
Thanks for the post but I've already used nvflash to install CWR and have tried multiple roms and all have ended in the same way. I know I've been doing it right because I even followed the video from the unlockr to the T but at the end where he reboots I instead get the same screen in my earlier post. Is it possible I'm doing something wrong or maybe using the wrong roms?

Its most likely you are just missing a step somewhere. Try heading to the Hellfire rom help thread and read through there see if your missing something.... Usually this is a cut and dry process I don't see how its not working for you ...
Edit:
http://forum.xda-developers.com/showthread.php?t=1513387
Pin it to Win it.

I.R.Chevy said:
Its most likely you are just missing a step somewhere. Try heading to the Hellfire rom help thread and read through there see if your missing something.... Usually this is a cut and dry process I don't see how its not working for you ...
Edit:
http://forum.xda-developers.com/showthread.php?t=1513387
Pin it to Win it.
Click to expand...
Click to collapse
Thanks for thee help I really do appreciate it. And I do believe I found the missing step, some where along the line I thought flashing and rooting where the same so when I flashed CWR I didn't root the phone before I started. And since I'm stuck on that screen does that mean I pretty much screwed?

KingsKnight21 said:
Thanks for thee help I really do appreciate it. And I do believe I found the missing step, some where along the line I thought flashing and rooting where the same so when I flashed CWR I didn't root the phone before I started. And since I'm stuck on that screen does that mean I pretty much screwed?
Click to expand...
Click to collapse
Not at all. Just use nvflash rom for recovery. It will put completely stock tmo 2.3.3 . On phone, sorry no links. Search for that and it should give you a bootable phone. Then just nvflash cwm recovery and flash rom of choice. Don't forget to wipe data. No root required.

I dunno if mentioned before but when I used the method from these links http://forum.xda-developers.com/showthread.php?t=1327929 & http://forum.xda-developers.com/showthread.php?t=1473781 once I had gotten to installer update part it had a connection error which brought me to my present situation also now whenever i tried to repeat the process the program freezes and crashes. If it were my phone I'd just forget the whole thing but since it's my friends I'd rather fix this problem if possible.

KingsKnight21 said:
I dunno if mentioned before but when I used the method from these links http://forum.xda-developers.com/showthread.php?t=1327929 & http://forum.xda-developers.com/showthread.php?t=1473781 once I had gotten to installer update part it had a connection error which brought me to my present situation also now whenever i tried to repeat the process the program freezes and crashes. If it were my phone I'd just forget the whole thing but since it's my friends I'd rather fix this problem if possible.
Click to expand...
Click to collapse
This is what I meant: http://forum.xda-developers.com/showthread.php?t=1248644 That should fix it, and then follow this: http://forum.xda-developers.com/showthread.php?t=1056847 and you should have cwm.

tahahawa said:
This is what I meant: http://forum.xda-developers.com/showthread.php?t=1248644 That should fix it, and then follow this: http://forum.xda-developers.com/showthread.php?t=1056847 and you should have cwm.
Click to expand...
Click to collapse
Well i followed the link and the instructions and now the phone wont even turn on. So the question is what now?
Edit: Battery was dead, charging now

KingsKnight21 said:
Well i followed the link and the instructions and now the phone wont even turn on. So the question is what now?
Click to expand...
Click to collapse
No white LG logo? Or nothing at all? Which link were you following? If it was the first one, then you may want to try it again, I was in the same situation. Not even backlight worked, but I used the NVflash script again and it booted to T-Mobile official 2.3.3 unrooted. Did you hold the volume buttons the entire time?

tahahawa said:
No white LG logo? Or nothing at all? Which link were you following? If it was the first one, then you may want to try it again, I was in the same situation. Not even backlight worked, but I used the NVflash script again and it booted to T-Mobile official 2.3.3 unrooted. Did you hold the volume buttons the entire time?
Click to expand...
Click to collapse
Battery was just dead, it workin now and thank you very much for the help

KingsKnight21 said:
Battery was just dead, it workin now and thank you very much for the help
Click to expand...
Click to collapse
Phew. I thought something went REALLY wrong. -.-' No problem. If ever you have a problem, and want support ASAP, PM me now and take down my email, or just PM me in the future and I'll see what I can do .

tahahawa said:
Phew. I thought something went REALLY wrong. -.-' No problem. If ever you have a problem, and want support ASAP, PM me now and take down my email, or just PM me in the future and I'll see what I can do .
Click to expand...
Click to collapse
I'll do just that Thanks again.

[28/06/2012][v3.07][ODIN] All Latest ODIN (Flash program) Versions for Galaxy S III

[size=+2] Windows ODIN (Samsung Flashing Application)[/size]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All latest versions and download links are below! of course courtesy of samsung-updates.com portal!
[size=+2]Odin (v3.07) is HERE [/size]
[size=+1]Odin (v3.06) is HERE [/size]
[size=+1]ALWAYS DO BACKUP OF PRECIOUS DATA BEFORE FLASHING!! IM NOT TAKING RESPONSIBILITY FOR DATA LOSS!
FLASHING CUSTOM ROM WILL TOP UP YOUR CUSTOM ROM COUNTER!!
FLASHING ROMS MAY (OR NOT) CAUSE DATA LOSS (SMS, CONTACTS, SETTINGS , APPS) - YOU HAVE BEEN WARNED![/size]​
Enjoy!
Watch us on twitter for latest updates! @SamsungUpdates !

Custom Rom Counter?
Hey everyone!
I am new to samsung phones...coming from a Droid x2 and wanted to get some clarity on what the Custom Rom Counter is.
So is it a setting that verizon can check to see if you have ever flashed a custom rom on top of your stock rom?

keatond said:
Hey everyone!
I am new to samsung phones...coming from a Droid x2 and wanted to get some clarity on what the Custom Rom Counter is.
So is it a setting that verizon can check to see if you have ever flashed a custom rom on top of your stock rom?
Click to expand...
Click to collapse
It increments each time a custom rom is flashed. They will know if you void your warranty, unless you reset it. There will be ways to reset this once we have devs cracking open the phone

cmg5461 said:
It increments each time a custom rom is flashed. They will know if you void your warranty, unless you reset it. There will be ways to reset this once we have devs cracking open the phone
Click to expand...
Click to collapse
That similiar to the HTC dev unlock thing?
Sent from my vivow using Tapatalk 2

No, odin is a flashing program not unlocking program

So to flash anything must Odin be used? We can't just download a kernel or Rom via phone, boot into cwm and flash the kernel or Rom through there?
Sent from my vivow using Tapatalk 2

yes you can. But your recovery MUST be CWM then. Also you cant back to stock using CWM cause CWM is no stock
I see your're new to this things, and i can assure you. You will be using ODIN as your daily driver

I'm 100% New to Samsung. I have had the dinc and dinc2. The only time I ever used a pc was to load a new bootloader and soff. Everything else was dine via phone. Even stock, I just flash the pb32img and boom, run revolutionary s on and no worries. 100% back to stock.. after my dinc I didn't even use cwm, I used 4ext recovery.. 1000x better... I need to fond me a noon Samsung forum because I know I'm going to get annoying quick. And I hate it when people don't read up on vivow forums moat of the time.
Sent from my vivow using Tapatalk 2

I am glad to see that odin is going to be used for this phone. Still don't quite get ADB and whatnot. For those not familiar with Odin it is pretty much your best friend. Odin allows for flashing of factory images along with radios and clockwork mod recoveries.
I will use my Fascinate as an example. If i want to flash back to stock i have a stock odin file that will to go to Eclair,Froyo, or Gingerbread. Any and all modifications go back to stock at that point so bootloaders, radios, and obviously the rom itself and the kernel. Odin then also allows for you to switch radios. Again the Fascinate for example, the fascinate has 6 over all radios give or take. One is designed for Elcair, one or two for Froyo and the rest for Gingerbread. With there being more then one option for certain android operating systems you can use the one which is best for you. If you flash the wrong modem the phone will still work and what not but might not properly call or send and receive txt msgs. Last but not least you can use Odin to flash recoveries. When going to any ICS rom on the fascinate you actually have to flash a recovery that allows for you to install the appropriate files. This is done through Odin. So in a lot of major cases you go back to Odin. Flashing new roms and kernels are still done via the phone in recovery.
The flash counter thing i will admit is new to me. I heard about it on some of the newer Samsung phones but i never heard or encountered it with the Fascinate
We also should sooner or later have a mobile odin available to us if not already. Pretty much what this means is that all the things i described above can be done from your phone independently without the use of a computer from a mobile version of odin. So you can fix things on the go.
EDIT***** Forgot another cool feature of Odin. Custom Odin files. So try to follow me. So as I mentioned you can through Odin go back to a factory image. What you can create on your own though is a custom image to go back to. So again to go from Stock Eclair,Froyo or Gingberbread to ICS on the Fascinate requires 2 flashes through odin and 3 reboots technically. Instead of going through all that i can create my own custom Odin file that will have me right back to the latest and greatest, So straight to a ICS rom with the proper kernel,bootloaders & radio. So no need for a step by step process to get you back to where you were you can just flash through Odin. I have yet to do this and really see how it works but the ability to do something like this is pretty awesome.
All in all the Samsung experience is a very unique one and what i would like to say is the best. You don't have to worry about s-off and hboots and locked bootloaders and what not. Its straight and to the point. Hope this was of more help to better understand Odin and its uses.

Aali1011 said:
I am glad to see that odin is going to be used for this phone. Still don't quite get ADB and whatnot. For those not familiar with Odin it is pretty much your best friend. Odin allows for flashing of factory images along with radios and clockwork mod recoveries.
I will use my Fascinate as an example. If i want to flash back to stock i have a stock odin file that will to go to Eclair,Froyo, or Gingerbread. Any and all modifications go back to stock at that point so bootloaders, radios, and obviously the rom itself and the kernel. Odin then also allows for you to switch radios. Again the Fascinate for example, the fascinate has 6 over all radios give or take. One is designed for Elcair, one or two for Froyo and the rest for Gingerbread. With there being more then one option for certain android operating systems you can use the one which is best for you. If you flash the wrong modem the phone will still work and what not but might not properly call or send and receive txt msgs. Last but not least you can use Odin to flash recoveries. When going to any ICS rom on the fascinate you actually have to flash a recovery that allows for you to install the appropriate files. This is done through Odin. So in a lot of major cases you go back to Odin. Flashing new roms and kernels are still done via the phone in recovery.
The flash counter thing i will admit is new to me. I heard about it on some of the newer Samsung phones but i never heard or encountered it with the Fascinate
We also should sooner or later have a mobile odin available to us if not already. Pretty much what this means is that all the things i described above can be done from your phone independently without the use of a computer from a mobile version of odin. So you can fix things on the go.
EDIT***** Forgot another cool feature of Odin. Custom Odin files. So try to follow me. So as I mentioned you can through Odin go back to a factory image. What you can create on your own though is a custom image to go back to. So again to go from Stock Eclair,Froyo or Gingberbread to ICS on the Fascinate requires 2 flashes through odin and 3 reboots technically. Instead of going through all that i can create my own custom Odin file that will have me right back to the latest and greatest, So straight to a ICS rom with the proper kernel,bootloaders & radio. So no need for a step by step process to get you back to where you were you can just flash through Odin. I have yet to do this and really see how it works but the ability to do something like this is pretty awesome.
All in all the Samsung experience is a very unique one and what i would like to say is the best. You don't have to worry about s-off and hboots and locked bootloaders and what not. Its straight and to the point. Hope this was of more help to better understand Odin and its uses.
Click to expand...
Click to collapse
The fact of not worrying about the unlocked bootloader and soff seems really nice, otherwise like I said everything else was done right via my phone. It does help me understand it 100x better though. I really appreciate you taking the time to break it down
Sent from my vivow using Tapatalk 2

check out this guide i made for the fascinate below...the sgsIII flashing methods should be very similar. i plan on creating a similar guide soon as devs get working on it.
http://forum.xda-developers.com/showthread.php?t=1238070

Odin has been my friend many times with my charge ....
SENT FROM THE DOG POUND

droidstyle said:
check out this guide i made for the fascinate below...the sgsIII flashing methods should be very similar. i plan on creating a similar guide soon as devs get working on it.
http://forum.xda-developers.com/showthread.php?t=1238070
Click to expand...
Click to collapse
Wow I have to say that is beyond a thorough and very well explained guide I look forward to it here and you answered a lot of noobish questions to without freaking out lol

droidstyle said:
check out this guide i made for the fascinate below...the sgsIII flashing methods should be very similar. i plan on creating a similar guide soon as devs get working on it.
http://forum.xda-developers.com/showthread.php?t=1238070
Click to expand...
Click to collapse
Boy am i glad to see you here. But yes droidstyle's guide is a good illustration of how odin is very much so integrated in conjunction with the phone.

Aali1011 said:
I am glad to see that odin is going to be used for this phone. Still don't quite get ADB and whatnot. For those not familiar with Odin it is pretty much your best friend. Odin allows for flashing of factory images along with radios and clockwork mod recoveries.
I will use my Fascinate as an example. If i want to flash back to stock i have a stock odin file that will to go to Eclair,Froyo, or Gingerbread. Any and all modifications go back to stock at that point so bootloaders, radios, and obviously the rom itself and the kernel. Odin then also allows for you to switch radios. Again the Fascinate for example, the fascinate has 6 over all radios give or take. One is designed for Elcair, one or two for Froyo and the rest for Gingerbread. With there being more then one option for certain android operating systems you can use the one which is best for you. If you flash the wrong modem the phone will still work and what not but might not properly call or send and receive txt msgs. Last but not least you can use Odin to flash recoveries. When going to any ICS rom on the fascinate you actually have to flash a recovery that allows for you to install the appropriate files. This is done through Odin. So in a lot of major cases you go back to Odin. Flashing new roms and kernels are still done via the phone in recovery.
The flash counter thing i will admit is new to me. I heard about it on some of the newer Samsung phones but i never heard or encountered it with the Fascinate
We also should sooner or later have a mobile odin available to us if not already. Pretty much what this means is that all the things i described above can be done from your phone independently without the use of a computer from a mobile version of odin. So you can fix things on the go.
EDIT***** Forgot another cool feature of Odin. Custom Odin files. So try to follow me. So as I mentioned you can through Odin go back to a factory image. What you can create on your own though is a custom image to go back to. So again to go from Stock Eclair,Froyo or Gingberbread to ICS on the Fascinate requires 2 flashes through odin and 3 reboots technically. Instead of going through all that i can create my own custom Odin file that will have me right back to the latest and greatest, So straight to a ICS rom with the proper kernel,bootloaders & radio. So no need for a step by step process to get you back to where you were you can just flash through Odin. I have yet to do this and really see how it works but the ability to do something like this is pretty awesome.
All in all the Samsung experience is a very unique one and what i would like to say is the best. You don't have to worry about s-off and hboots and locked bootloaders and what not. Its straight and to the point. Hope this was of more help to better understand Odin and its uses.
Click to expand...
Click to collapse
Chainfire has a Mobile Odin on Google Play. Used it on my 7.7 and ..wow! Way too cool. Got real familiar with ADB with the TF (necessity!) but you;re right...ODIN is slick! Not sure if Chainfire's Mobile Odin will work for the SGSII (getting mine from VZW next week) but if it does it'll be more than welcome!

Odin method is far better than the CWR (clockwork recovery) method. I never understood exactly why, but if you load your software using Odin, it will work really well every time assuming you don't mess up. Clockwork Recovery flashed roms tend to be a bit hit or miss, they tend to have more incomplete flashes....it just doesn't seem to do as thorough a job as Odin.
I always choose the Odin method given the choice. I will wait until I get around a pc to do this, would really rather not be sitting somewhere flashing in clockwork and get a bad flash and end up without a phone until I can get back to a pc with Odin to fix it.....

jamesnmandy said:
Odin method is far better than the CWR (clockwork recovery) method. I never understood exactly why, but if you load your software using Odin, it will work really well every time assuming you don't mess up. Clockwork Recovery flashed roms tend to be a bit hit or miss, they tend to have more incomplete flashes....it just doesn't seem to do as thorough a job as Odin.
I always choose the Odin method given the choice. I will wait until I get around a pc to do this, would really rather not be sitting somewhere flashing in clockwork and get a bad flash and end up without a phone until I can get back to a pc with Odin to fix it.....
Click to expand...
Click to collapse
I couldn't agree with more...
SENT FROM THE DOG POUND

jamesnmandy said:
Odin method is far better than the CWR (clockwork recovery) method. I never understood exactly why, but if you load your software using Odin, it will work really well every time assuming you don't mess up. Clockwork Recovery flashed roms tend to be a bit hit or miss, they tend to have more incomplete flashes....it just doesn't seem to do as thorough a job as Odin.
I always choose the Odin method given the choice. I will wait until I get around a pc to do this, would really rather not be sitting somewhere flashing in clockwork and get a bad flash and end up without a phone until I can get back to a pc with Odin to fix it.....
Click to expand...
Click to collapse
I agree with this too but I don't think we are going to see many roms come in a Odin package. Regarding the Fascinate I think we mainly had stock system packages. In the beginning of development for the phone on a lot of the Touchwiz based roms we had Odin packages too IIRC. When it progressed to CM7 & CM9 it was all done through the phone. Its all up to our developers. That is my main concern for this phone. Time will only tell who we will see but from the looks of it thanks to Verizon's ploy to destroy unlimited data a lot of people seem to be hopping on the bandwagon.
With talks already of having developers from all carriers having a "Kitchen" of sorts where we can get roms and maybe kernels from say the AT&T version or Sprint version that work with our phones, things are looking good and I hope to have a repeat of the experience if not better then what I had with the Fascinate. The devs MADE that phone what it was and I thank them wholeheartedly.

This is very interesting (coming from rooting on a Droid X)
I was watching videos of people using Odin on Youtube and heard about that counter in the phones, got really nervous until I read that they can be reset. Very excited.

so noone still has the verizon phone version ?

[ROM][HEIMDALL] Package For T959W Wind/Mobilicity Canadian Users

Welcome T959W users. This guide and package should help you either root your 959W, get it back to (almost) stock, get you out of a boot loop, or get you on your way to installing one of the variations of Ice Cream Sandwich.
The T959W is hardware wise 100% identical to the T959V but there are a few small stock software differences that cause problems using some of the initial T959V tools. Though risking my own phone and the help of I think just about all the Team Acid members, I have learned a lot and gotten a close to a stock dump as possible.
As of now, there is no 100% back to stock package for our phones. I have tried without success in getting a stock image from Wind or Samsung. They have both told me to ask the other one. Maybe someone can try Mobilicity or try Wind again and see what they say. It would greatly help me make a fully stock package, and understand any of the small differences. The T959V users got the phone when it came with Android 2.2 and an update was released to 2.3 for them, thus giving them the ability to have a stock image as it was provided. The W variant comes with 2.3 stock, so therefore no upgrade package exists for us and leaves us without a way to return to fully stock.
If you messed up your phone trying a different package, I can help get it 99% stock, or rooted and get you setup to install other ROM’s.
With that said, the standard disclaimer applies.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, broken hearts,
* thermonuclear war, you getting fired because the alarm app failed, or
* unfulfilled sexual partners. Please do some research if you have any
* concerns about features included in this ROM before flashing it! YOU are
* choosing to make these modifications, and if you point the finger at me
* for messing up your device, I will point that finger back at you and laugh.
* Then I will put it in your eye.
*/
By using the ROM you agree with the above terms!
First, I will assume some things as this is not a tutorial thread.
You can get your phone into download mode.
You have the Samsung drivers installed.
You can follow basic step by step instructions.
1) Download Heimdall 1.3.1 SUITE for the OS you are using from HERE Don't use 1.3.2 or any other versions, 1.3.1 works, so why screw with stuff and try something I don't recommend? Make sure to get the suite or the full package and not just the command line. Make sure you have the C++ libraries installed for Windows users. It's right underneath the download link I linked below.
This is the one for Windows, which I assume most users will be using. Others, download the suite for your OS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2) Download my package HERE. DO NOT UNCOMPRESS IT, LEAVE IT AS IS.
3) Unzip/uncompress the Heimdall package to a folder on your pc/mac
4) Put your phone into download mode
5) Startup the Heimdall-Frontend program with your preferred method depending on your OS (run that program)
6) Click on the utilities tab and click on the Device Detected button. If it shows device detected, proceed to the next step. If it doesn’t find your device and you are in download mode, it’s a drivers issue and read HERE for instructions on how to get the proper drivers working using the Zdiag software included with the Heimdall package. Ignore the 1click part of the linked thread, but follow the rest. you will have to run Zdiag manually from the "drivers folder" of the Heimdall suite.
7) Only process to this step when have determined that your device is detected by Heimdall.
8) Click on the first Tab in Heimdall Frontend that says Load Package. Click on the browse button and load up the T959Wpackage you downloaded in step 2. It may take up to 10 minutes for your PC to uncompress the files depending on the speed of it. Don’t rush it, waiting till all the messages are gone and the LOAD/CUSTOMIZE button is active, click on that button
9) This will bring you to the FLASH tab. Make sure repartition is CHECKED (it should) and don’t touch anything else. Finally, click on the START button at the bottom. Let it do it’s thing, it will take about 5 mins and then your phone will reboot. It will take another few minutes here before your phone fully boots and you are at the Google Setup screen.
10) Made it this far? Great, now you have saved your phone from a brick, but there are a few things that aren’t working yet, so don’t panic that you have no signal yet or no wifi, etc. We can fix those things fairly easily IF YOU CAN FOLLOW INSTRUCTIONS AND READ AND NOT RUSH. If you start whining you have no signal after step 9 and don’t read anymore or follow my instructions on how to flash the proper modem, I’ll ignore you. These are all proven steps, tested by thousands of people on these forums that aren’t impatient and do what they are told.
Now, the 3 choices you have.
1) Flash to an Ice Cream Sandwich Variation. If this is the case , Download the ROM you want to your SD card, reboot your phone into recovery and flash according to the directions given by the ROM you want to flash. I won’t answer questions why you can’t flash XXX ROM, your phone will be rooted with recovery using my method, and the rest of the information is out there.
2) Return to the 99% stock option (this will bring the phone exactly how you got it BUT will say T-mobile when you first boot it up. I have no way to fix this currently as I have no stock kernel to use. (hint, bug Wind or Mobilicity for the package and get it to me) Will work on this part.
3) Keep the phone rooted with recovery on Gingerbread. The kernel included in this is Blastoff kernel, which wifi doesn’t work off the start, so you can go to the Blastoff thread HERE and learn how to fix wifi, flash Antonx’s Basic with a Twist HERE or another compatible GB kernel, all from recovery. You will also need to flash a modem. I suggest the LB6 modem that came stock on our phones from, available HERE for GB and ICS, pick the correct one. Again, I provide no support for Blastoff or Basic with a twist or flashing them or something.
So to summarize, this will get your T959W with a rooted kernel and CWM version 5.2.something. Wifi will not work and there is no modem flashed, so read the above step if you want to fix those, read how to do that yourself, etc. I don't want any questions about CM9 or Blastoff or Heimdall or Jelly Bean or anything here. The above steps works if you're not all OCD and rush through and read my steps. I have tested them and the package probably 50 times and I'm doing it again right as I finish typing this all out, so it works. If you still have trouble, and explain in a detailed way what didn't work, I may help. If you SPAZ out that something didn't work and don't explain the steps and demand help, you will be ignored. You risk doing damage to your phone anytime you flash it and void warranties, so that is the risk and I assume none. This package works, the steps I have tried to detail in as much detail as possible including screen shots and everything and have spent hours making and testing the package, taking screenshots, detailing all this, all for the benefit of others as my phone works fine and I never bricked it because I took the time to read, so please read this thread 3 times over before you proceed.
Anyways, hope this helps, give me a Thanks if it does and a Thanks to any Team Acid members posts you see, as they have helped me get to this point.

Now we need to get you on the one click bandwagon and we'll be set for Linux and OS X users

FBis251 said:
Now we need to get you on the one click bandwagon and we'll be set for Linux and OS X users
Click to expand...
Click to collapse
Soon as Heimdall can flash the modem properly, I will. lol. It fails, git issue opened on it, gave Heimdall dude all my logs, so we'll see. Also, since most people get bootlooped and mess up the param, and other files trying to flash everything under the sun, this package was the best way to do everything in 1 step.
The package though will work for linux/osx, etc, just use that Heimdall version. I just have Windows directions as I assume most people will be on Windows. You can load the gz though into any Heimdall and flash it.

getochkn said:
Welcome T959W users.
*********
Great Job man.
That was just awesome and a single click did the trick.
As instructed , i installed an ICS and that took care of the modem & signal as well.
Thank you so much.
Click to expand...
Click to collapse

Was it necessary to quote the entire post?

Hi getochkn,
Thanks for this very informative guide.I seriously thought my son's phone was bricked, but after following your instructions, everything was restored perfectly.The only hiccup I had was, at step #6 Heimdall showed the device as detected, but when I went to flash it, it said that it couldn't detect the device.So I installed the drivers manually through Zdiag and it was smooth sailing from there.
I then flashed CM9 and noticed in your sig that you are running RemICS Rom so I flashed that and everything is looking great so far.
Thanks for taking the time to make this guide for those on the T959W

Glad it worked for you and you saved the phone.

getochkn said:
Welcome T959W users. This guide and package should help you either root your 959W, get it back to (almost) stock, get you out of a boot loop, or get you on your way to installing one of the variations of Ice Cream Sandwich.
The T959W is hardware wise 100% identical to the T959V but there are a few small stock software differences that cause problems using some of the initial T959V tools. Though risking my own phone and the help of I think just about all the Team Acid members, I have learned a lot and gotten a close to a stock dump as possible.
As of now, there is no 100% back to stock package for our phones. I have tried without success in getting a stock image from Wind or Samsung. They have both told me to ask the other one. Maybe someone can try Mobilicity or try Wind again and see what they say. It would greatly help me make a fully stock package, and understand any of the small differences. The T959V users got the phone when it came with Android 2.2 and an update was released to 2.3 for them, thus giving them the ability to have a stock image as it was provided. The W variant comes with 2.3 stock, so therefore no upgrade package exists for us and leaves us without a way to return to fully stock.
If you messed up your phone trying a different package, I can help get it 99% stock, or rooted and get you setup to install other ROM’s.
With that said, the standard disclaimer applies.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, broken hearts,
* thermonuclear war, you getting fired because the alarm app failed, or
* unfulfilled sexual partners. Please do some research if you have any
* concerns about features included in this ROM before flashing it! YOU are
* choosing to make these modifications, and if you point the finger at me
* for messing up your device, I will point that finger back at you and laugh.
* Then I will put it in your eye.
*/
By using the ROM you agree with the above terms!
First, I will assume some things as this is not a tutorial thread.
You can get your phone into download mode.
You have the Samsung drivers installed.
You can follow basic step by step instructions.
1) Download Heimdall 1.3.1 SUITE for the OS you are using from HERE Don't use 1.3.2 or any other versions, 1.3.1 works, so why screw with stuff and try something I don't recommend? Make sure to get the suite or the full package and not just the command line. Make sure you have the C++ libraries installed for Windows users. It's right underneath the download link I linked below.
This is the one for Windows, which I assume most users will be using. Others, download the suite for your OS
2) Download my package HERE. DO NOT UNCOMPRESS IT, LEAVE IT AS IS.
3) Unzip/uncompress the Heimdall package to a folder on your pc/mac
4) Put your phone into download mode
5) Startup the Heimdall-Frontend program with your preferred method depending on your OS (run that program)
6) Click on the utilities tab and click on the Device Detected button. If it shows device detected, proceed to the next step. If it doesn’t find your device and you are in download mode, it’s a drivers issue and read HERE for instructions on how to get the proper drivers working using the Zdiag software included with the Heimdall package. Ignore the 1click part of the linked thread, but follow the rest. you will have to run Zdiag manually from the "drivers folder" of the Heimdall suite.
7) Only process to this step when have determined that your device is detected by Heimdall.
8) Click on the first Tab in Heimdall Frontend that says Load Package. Click on the browse button and load up the T959Wpackage you downloaded in step 2. It may take up to 10 minutes for your PC to uncompress the files depending on the speed of it. Don’t rush it, waiting till all the messages are gone and the LOAD/CUSTOMIZE button is active, click on that button
9) This will bring you to the FLASH tab. Make sure repartition is CHECKED (it should) and don’t touch anything else. Finally, click on the START button at the bottom. Let it do it’s thing, it will take about 5 mins and then your phone will reboot. It will take another few minutes here before your phone fully boots and you are at the Google Setup screen.
10) Made it this far? Great, now you have saved your phone from a brick, but there are a few things that aren’t working yet, so don’t panic that you have no signal yet or no wifi, etc. We can fix those things fairly easily IF YOU CAN FOLLOW INSTRUCTIONS AND READ AND NOT RUSH. If you start whining you have no signal after step 9 and don’t read anymore or follow my instructions on how to flash the proper modem, I’ll ignore you. These are all proven steps, tested by thousands of people on these forums that aren’t impatient and do what they are told.
Now, the 3 choices you have.
1) Flash to an Ice Cream Sandwich Variation. If this is the case , Download the ROM you want to your SD card, reboot your phone into recovery and flash according to the directions given by the ROM you want to flash. I won’t answer questions why you can’t flash XXX ROM, your phone will be rooted with recovery using my method, and the rest of the information is out there.
2) Return to the 99% stock option (this will bring the phone exactly how you got it BUT will say T-mobile when you first boot it up. I have no way to fix this currently as I have no stock kernel to use. (hint, bug Wind or Mobilicity for the package and get it to me) Will work on this part.
3) Keep the phone rooted with recovery on Gingerbread. The kernel included in this is Blastoff kernel, which wifi doesn’t work off the start, so you can go to the Blastoff thread HERE and learn how to fix wifi, flash Antonx’s Basic with a Twist HERE or another compatible GB kernel, all from recovery. You will also need to flash a modem. I suggest the LB6 modem that came stock on our phones from, available HERE for GB and ICS, pick the correct one. Again, I provide no support for Blastoff or Basic with a twist or flashing them or something.
So to summarize, this will get your T959W with a rooted kernel and CWM version 5.2.something. Wifi will not work and there is no modem flashed, so read the above step if you want to fix those, read how to do that yourself, etc. I don't want any questions about CM9 or Blastoff or Heimdall or Jelly Bean or anything here. The above steps works if you're not all OCD and rush through and read my steps. I have tested them and the package probably 50 times and I'm doing it again right as I finish typing this all out, so it works. If you still have trouble, and explain in a detailed way what didn't work, I may help. If you SPAZ out that something didn't work and don't explain the steps and demand help, you will be ignored. You risk doing damage to your phone anytime you flash it and void warranties, so that is the risk and I assume none. This package works, the steps I have tried to detail in as much detail as possible including screen shots and everything and have spent hours making and testing the package, taking screenshots, detailing all this, all for the benefit of others as my phone works fine and I never bricked it because I took the time to read, so please read this thread 3 times over before you proceed.
Anyways, hope this helps, give me a Thanks if it does and a Thanks to any Team Acid members posts you see, as they have helped me get to this point.
Click to expand...
Click to collapse
This was amazingly simple. My phone has been really messed up and I've tried everything to restore it and failed until today. Believe me when I tell you that my phone was a lost cause until I went through these steps even though they aren't for my phone but it still worked. I finally got it to flash something and work, lol.
Do you by chance have this same type of file for the US version? Any help is much appreciated. Thank you.

kdkd008 said:
This was amazingly simple. My phone has been really messed up and I've tried everything to restore it and failed until today. Believe me when I tell you that my phone was a lost cause until I went through these steps even though they aren't for my phone but it still worked. I finally got it to flash something and work, lol.
Do you by chance have this same type of file for the US version? Any help is much appreciated. Thank you.
Click to expand...
Click to collapse
You flashed this on a t959v? With bootloaders? And it works?

TwitchyEye said:
You flashed this on a t959v? With bootloaders? And it works?
Click to expand...
Click to collapse
No bootloaders in my package. For some reason the "W" model, it's impossible to flash the bootloader, the modem and EFS partition (I think it's that, been a while since I played with it) from Heimdall or Odin, so it's sort of impossible to brick them as you can never flash those items. Worst you can do is flash the param from the "V" to the "W" and it corrupts the bootup image but works fine otherwise.

Oh I see. Thanks for clearing that up, I've been wondering for a while what would happen.

Hi, I just needed to root my phone. I had previously tried SuperOneClick, for some reason it always fails because of some driver issue. However after I installed your ROM, the root works.
But now that I got your ROM, I cannot detect my SIM card.
I'm wondering if this issues is expected, and is it possible to fix it?
Thanks.

noobishuser said:
Hi, I just needed to root my phone. I had previously tried SuperOneClick, for some reason it always fails because of some driver issue. However after I installed your ROM, the root works.
But now that I got your ROM, I cannot detect my SIM card.
I'm wondering if this issues is expected, and is it possible to fix it?
Thanks.
Click to expand...
Click to collapse
Did you flash a modem? Heimdall can't flash the modem and it's has to be flashed with one of the ones I listed above.

getochkn said:
Did you flash a modem? Heimdall can't flash the modem and it's has to be flashed with one of the ones I listed above.
Click to expand...
Click to collapse
Thank you very much, I thought I broke my phone.
Do you have instruction on how to flash a modem?
The link you provided only gives a file, I'm not sure how to flash it.
I also looked for instruction here:
http://forum.xda-developers.com/showthread.php?t=1001759
but got stuck on step 7 as the file provided does not have a .tar file.

That is a very old thread. FBis251 has a thread with all the modems and you just have to flash them via recovery. Ill look for the thread link and post it back.
This is it here.
http://forum.xda-developers.com/showthread.php?t=1192436

Hi, after spending the past several hours reading/flashing I think I've finally understand most of what's going on.
I was able to successfully some modems. However none of them work perfectly for Mobilicity.
The call/text works fine, but there's no data.
I'm wondering if there is a modem that works for Wind mobile modem with data.
Since I'm planning to switch to Wind mobile anyways later.

noobishuser said:
Hi, after spending the past several hours reading/flashing I think I've finally understand most of what's going on.
I was able to successfully some modems. However none of them work perfectly for Mobilicity.
The call/text works fine, but there's no data.
I'm wondering if there is a modem that works for Wind mobile modem with data.
Since I'm planning to switch to Wind mobile anyways later.
Click to expand...
Click to collapse
It's more than likely your APN's aren't set and that's why you're not getting data. you can look online on what the mobilicity ones are and can through settings, mobile data, mobile networks or something like that, and either enter them manually or scan to force it to try and pick them up. If calls/txt work, data should work. It's on the network. Try and google what to figure out to change. If you can't pm me and I'll try and help.

getochkn said:
It's more than likely your APN's aren't set and that's why you're not getting data. you can look online on what the mobilicity ones are and can through settings, mobile data, mobile networks or something like that, and either enter them manually or scan to force it to try and pick them up. If calls/txt work, data should work. It's on the network. Try and google what to figure out to change. If you can't pm me and I'll try and help.
Click to expand...
Click to collapse
Omg thank you very much! I've successfully got data working now.
Now i feel like an idiot in the past 2 hours trying out every modem I can find...

noobishuser said:
Omg thank you very much! I've successfully got data working now.
Now i feel like an idiot in the past 2 hours trying out every modem I can find...
Click to expand...
Click to collapse
Good stuff. The LB6 modem seems to be the most liked for the most part and is the one I got from my Wind phone. Works good for me.

getochkn said:
Good stuff. The LB6 modem seems to be the most liked for the most part and is the one I got from my Wind phone. Works good for me.
Click to expand...
Click to collapse
Q here, does this modem support the 850mhz frequency and can I flash it to a T959V
Forgot to say it's the wcdma band
I'm new to this phone, exchange an IPhone 3GS for this one.......
Sent from my XT925 using xda app-developers app

Next8P12 (Big Lots 'Black Friday Edition' Nextbook)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm seeing a lot of confusion on the forums about the Nextbook Big Lots released on Black Friday so I see it worth making a thread over.
This Nextbook does *not* use the Rockchip RK2918. If you look at the build info and do a little research (http://yifang.en.made-in-china.com/...-4-0-Tablet-with-Amlogic-8726-M3-M805MC-.html) it's got an Amlogic 8726-M3 under the hood. That's the M3 chip people keep mentioning here.
I have gathered much information on this 'new' Nextbook and posted it here. I have found what I think to be a jtag mode where, as people described, "M3-Chip" shows up in device manager. That forum thread has an Android System Info dump posted and for the sake of space I won't be reposting it here so go there and check it out. I only omitted non-relevant personal info and replaced with a [Removed] tag.
I would really like to see some genius minds at work getting this tablet rooted and the 'ROM Train' chugging. I have donated my talents of information gathering. I'm calling for someone to pick up the torch and work it from here. I've noticed at least two people that said they bought at least 3 of these so maybe someone can work with someone on donating a device to a cause and XDA can add another 'rooted knotch' to it's seemingly infinitely long belt'
---
[Update]
Here is the chip MFG's original source code to include kernel and all the toppings. This should be good starter info: http://openlinux.amlogic.com/wiki/index.php/Arm/Platform_Info/Information_for_8726M/Build_system_for_8726M_Howto. Also I've brought Slatedroid in the loop on this one so hopefully we can get the ball moving quickly.

What's up...just got one of these as well and of course like other people I was surprised to find out this wasn't rk29 as I was super ready to root this thing...I have absolutely no idea if this will help any and you may have already come across this site but it seems that the admin here (finless) knows how to work with these devices.
I don't know if that would go for this particular version with the m3 chip but anybody else who can get this rooted would be of great help. I wish I knew how to do it myself because I would but I'm only good for graphics...glad I came across this thread and to see you gathering much needed info, I'll stay tuned and if I stumble across anything that can help I'll be sure to post it here.

I have one of these units as well and would like to get it rooted. Just chiming in.

therealrayzzor said:
What's up...just got one of these as well and of course like other people I was surprised to find out this wasn't rk29 as I was super ready to root this thing...I have absolutely no idea if this will help any and you may have already come across this site but it seems that the admin here (finless) knows how to work with these devices.
I don't know if that would go for this particular version with the m3 chip but anybody else who can get this rooted would be of great help. I wish I knew how to do it myself because I would but I'm only good for graphics...glad I came across this thread and to see you gathering much needed info, I'll stay tuned and if I stumble across anything that can help I'll be sure to post it here.
Click to expand...
Click to collapse
Thanks for the info! I have made some progress. Here's a thread on Slatedroid that has the M3-Chip driver and low level flash utility: http://www.slatedroid.com/topic/39037-amlogic-low-level-flashing-tool/
I am tinkering with it a little but I'd encourage someone smarter than I to have a look at it as well in case I fail. To get the tablet in the proper mode do vol up + plug in usb with device powered down. I'll go ahead and attach related files here for convenience. You will need to disable driver verification to get the driver installed.
My first attempt I think I might have bricked the tablet. I'll give more info as I get it.

Yeah I fu-barred it. Anyone with experience w/ AmlogicBurningTool -or- someone who can extract the firmware so I can flash; I think I wiped my device tinkering with this utility. Any help would be appreciated as I'm dead in the water until I get the device bootable again.
[Update] I contacted Nextbook on this issue. The sup seemed pretty pissed when I let him know what I was attempting to do but for being forthcoming he agreed to see about getting me the original firmware zip file. As per usual I will update should I get any info.

Nice job! Thanks for all the work on this. I've got one I'm willing to hack on too. Not sure how to get the firmware off of it but I'm willing to try anything. I've been looking around and I supposed I'd need to run the burning tool with the device in IPL (not sure if that's what it's called) to take the firmware off? Let me know how I can help.

I'm on a thread now with Finless on FreakTab and he said he can build a rom for us to get root...he just needs the stock rom to work with...I'm waiting on some type of instructions in case I need to take it from my tab and give to him.
Maybe this could be the break we're looking for.

therealrayzzor said:
I'm on a thread now with Finless on FreakTab and he said he can build a rom for us to get root...he just needs the stock rom to work with...I'm waiting on some type of instructions in case I need to take it from my tab and give to him.
Maybe this could be the break we're looking for.
Click to expand...
Click to collapse
I sure hope so.........this stock rom sucks! I've been trying to mess around with it and install some apps from SDcard but having absolutely no luck. Now mine wont even boot. Going to have to reset to out of box.

mascondante said:
Yeah I fu-barred it. Anyone with experience w/ AmlogicBurningTool -or- someone who can extract the firmware so I can flash; I think I wiped my device tinkering with this utility. Any help would be appreciated as I'm dead in the water until I get the device bootable again.
[Update] I contacted Nextbook on this issue. The sup seemed pretty pissed when I let him know what I was attempting to do but for being forthcoming he agreed to see about getting me the original firmware zip file. As per usual I will update should I get any info.
Click to expand...
Click to collapse
If they provide you with a copy, Finless can root it for sure.

shaunmt said:
If they provide you with a copy, Finless can root it for sure.
Click to expand...
Click to collapse
That would be awesome. My folks are getting me a Google Nexus 10 for Christmas. If I can get this one working I might be tempted to spend that money on something else. I feel really really dumb for wiping the NAND just because it was in Chinese and I clicked a random button. I thought surely it'd give some sort of popup warning to alert me I'm being an idiot first. But it happily wiped the thing no questions asked. So, when we get to the point of flashing a firmware in; If we have to use the low level flash tool be really freakin sure you got it in English and you read the instructions thoroughly before flashing. It's not normally like me to do something that dumb but I've not been getting good sleep and I've been in a real big rush to get this project done.
Lesson of the day:

So no one has been able to install google play on it so far ?

kristibaee said:
So no one has been able to install google play on it so far ?
Click to expand...
Click to collapse
That would require root access which has not yet been obtained. Once someone successfully roots it, installing market will be easy. Stay tuned.

No go on a ROM from TS
I opened a ticket with tech support to try to get the ROM from this thing and they said it's not available to consumers... I figured I'd get some response like that but just thought I'd give it a shot. +1 for a customer "needing" the ROM on their end.
So your tab is still not booting mascondante?!?

tread_water said:
I opened a ticket with tech support to try to get the ROM from this thing and they said it's not available to consumers... I figured I'd get some response like that but just thought I'd give it a shot. +1 for a customer "needing" the ROM on their end.
So your tab is still not booting mascondante?!?
Click to expand...
Click to collapse
nope after i wiped the nand it fails at the first phase of flashing

Still haven't heard back from Netbook.
Sent from my Nexus 10 using XDA Premium HD app

Still hoping someone will root this thing and make a decent ROM. Please?

My Ramos W13Pro AMlogic was pre-rooted in a way. I was able to ADB to it and type su and got the # prompt back.
What we need for sure is uImage dump (boot.img is the same). This will give us the kernel and boot which is the most important part!
Get Android Terminal Emulator. Run it and at the $ prompt type su
If it returns with # it means you have root access.
If you do not get # it is not pre rooted. However you can do this command without root I think
cat /proc/mtd
This will show the mounted blocks. We need to dump those to SDcard using DD command.
Bob

Nextbook ADB access
Bob, I've been lurking for a while on XDA and on your own Freaktab site trying to get this Nextbook 8p12 / 8SE with amlogic chip rooted as a christmas present for my son. I've managed to get the market and google services framework installed on the thing but they force close due to other necessary files missing. I saw your post above and jumped right into ADB on this thing, but got a permission denied error on the DD command trying to copy the bootloader. Any suggestions? Many thanks!

We may have a breakthrough over at freaktab.com!
Stay tuned...

eegorr: Could you link the discussion so folks from here can have a look at the progress?

[ROOT/GUIDE] SM-T210R For Dummies, or Rom display issues

Talking 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,
NOTE: KIES, will fix any display issue and bring you back to your original rom, i forget to add this, because ours is the pain in the bottom, to get it to work correctly, it go download, http://www.samsung.com/us/kies/, download windows version then follow this method, http://www.samsung.com/us/support/faq/FAQ00048586/52928, then it will get you back to basic then make sure to check usb debugging
Just and example video for visual learners http://www.youtube.com/watch?v=Xolmt...ature=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 (http://www.samsung.com/us/support/faq/FAQ00048586/52928) use this method, 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 wherever you wanna store in on tablet
so you should have odin 3.07
T210.CWM.6.0.4.5.recovery.tar.zip (lol make sure to extract this file so odin can see it xD)
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/showthread.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 on your tablet, and 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, just let it run and onces its on put the zip file andriod universal root in any place you like, then reboot while holding the power, vol up, home, then only hold the up vol button when you see the logo, while also holding the home 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!

Great guide. My friends SM-T210R kept getting kernal panic mode and the flickering screen. I did the same thing you did except I also installed Rocket Tab rom and Blackhawk kernel. It still Crashes every couple hours. I never could get the stock Kernal + Rom to work not sure what I was doing wrong. Perhaps I will follow your guide exactly this weekend.

morfn said:
Great guide. My friends SM-T210R kept getting kernal panic mode and the flickering screen. I did the same thing you did except I also installed Rocket Tab rom and Blackhawk kernel. It still Crashes every couple hours. I never could get the stock Kernal + Rom to work not sure what I was doing wrong. Perhaps I will follow your guide exactly this weekend.
Click to expand...
Click to collapse
thanks a lot this is my first guide i ever created in my life really lol so its kinda jumping around the place but this will root your samsung white, 8gb, and you wont get the display issue, and then download gl to sd with a 32gb card my god i can fit so many stuff, im so freaking happy, i found this method out, but im addding more stuff to it so you can start from scratch if your tablet can get in download mode then its never broken, i tested this like 15 times already, its been working fine for me, i was just trying to get step by step as low as possible

I'm trying to follow the instructions for the Kies restore.
I keep getting this error however. (Yes USB debugging is enabled. I also tried doing it from Download Mode)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

James1o1o said:
I'm trying to follow the instructions for the Kies restore.
I keep getting this error however. (Yes USB debugging is enabled. I also tried doing it from Download Mode)
Click to expand...
Click to collapse
OK, I could be wrong... I just got the tab 3 for my daughter and haven't done anything to it yet.
But from my S2 experience.... And this might be incorrect because I can say I never ever really used kies..... But I don't think keis will work anymore on a rooted device with a custom recovery ? It could be I'm wrong, that it won't work with a custom Rom tho... Maybe it should work with custom recovery and root.... But I thought it didn't.
Anyway, don't know if there's a file out there for this device, but I've always just used Odin to return to stock. I never used kies. Cause kies is an unstable, unreliable mess.
Anyone feel free to add to what I've said..... Or correct me tho.
Sent from my XT1058 using Tapatalk

kj2112 said:
OK, I could be wrong... I just got the tab 3 for my daughter and haven't done anything to it yet.
But from my S2 experience.... And this might be incorrect because I can say I never ever really used kies..... But I don't think keis will work anymore on a rooted device with a custom recovery ? It could be I'm wrong, that it won't work with a custom Rom tho... Maybe it should work with custom recovery and root.... But I thought it didn't.
Click to expand...
Click to collapse
I used to have an S3. From download mode, Kies would always restore it fine. Also I have stock rom and recovery when I tried to run Kies. I was simply trying to get back to my countries proper rom. (Which I can't download because SamMobile download hosts are awful)
I even emailed Samsung about it, they got back to me this morning. They told me to reinstall Kies, if that doesn't't work take it to a Samsung support center.

James1o1o said:
I used to have an S3. From download mode, Kies would always restore it fine. Also I have stock rom and recovery when I tried to run Kies. I was simply trying to get back to my countries proper rom. (Which I can't download because SamMobile download hosts are awful)
I even emailed Samsung about it, they got back to me this morning. They told me to reinstall Kies, if that doesn't't work take it to a Samsung support center.
Click to expand...
Click to collapse
Well, would be much simpler if there is an Odin flashable version out there. Saves allot of headaches.
Kies is just awful.
Sent from my XT1058 using Tapatalk

kj2112 said:
Well, would be much simpler if there is an Odin flashable version out there. Saves allot of headaches.
Kies is just awful.
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
The sad thing is, there is only one place I can get it. SamMobile...and its hosted on Terafile. Everyone on the site is complaining about it, but they seem to be refusing to change because they get money through affiliate program.

James1o1o said:
The sad thing is, there is only one place I can get it. SamMobile...and its hosted on Terafile. Everyone on the site is complaining about it, but they seem to be refusing to change because they get money through affiliate program.
Click to expand...
Click to collapse
Well.... At least you have answered a question I had. Just root and use stock system.... Or flash anything on it. I'll stick with stock. Just want to root to control the device better.... Battery issues in particular. My daughter is 5....she doesn't care about the Android version or touchwiz. Lol
Sent from my XT1058 using Tapatalk

my bad i was busy with work but, kies just gets you back to stock version, and this is for sm-t210r, which i rooted from stock version using this method, but it seems you have sm-t10 regular, if you have that, odin would do just fine this is for your model, this method is for sm-t10R, and model number

kj2112 said:
OK, I could be wrong... I just got the tab 3 for my daughter and haven't done anything to it yet.
But from my S2 experience.... And this might be incorrect because I can say I never ever really used kies..... But I don't think keis will work anymore on a rooted device with a custom recovery ? It could be I'm wrong, that it won't work with a custom Rom tho... Maybe it should work with custom recovery and root.... But I thought it didn't.
Anyway, don't know if there's a file out there for this device, but I've always just used Odin to return to stock. I never used kies. Cause kies is an unstable, unreliable mess.
Anyone feel free to add to what I've said..... Or correct me tho.
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
yea depends what he has though if he has sm-t210 then just use odin but using odin with a pre-rooted will get you flickering screen on sm-210R, if you have regular then you have to go a different route to restore it back to normal, if you have a flicker screen problem or any problem, then the kies method i have will recover it, in kies just use the update tab on sm-t210 and it will recover to stock thats all or use odin, your choice. if you want to root sm-t210 the method is here http://forum.xda-developers.com/showthread.php?t=2433853, this will root yours np ^^

biggyhead said:
yea depends what he has though if he has sm-t210 then just use odin but using odin with a pre-rooted will get you flickering screen on sm-210R, if you have regular then you have to go a different route to restore it back to normal, if you have a flicker screen problem or any problem, then the kies method i have will recover it, in kies just use the update tab on sm-t210 and it will recover to stock thats all or use odin, your choice. if you want to root sm-t210 the method is here http://forum.xda-developers.com/showthread.php?t=2433853, this will root yours np ^^
Click to expand...
Click to collapse
Thanks for the info!
Sent from my Moto X cell phone telephone.....

Thanks

Question. I followed the instructions which are more or less the same as what I did to root my S4. When I enter download mode in the device and open Odin (v3.047) and I select the folder where I downloaded the CWM file, T210.CWM.6.0.4.5.recovery.tar.zip, I am not able to see that file in the selection.
Odin itself does not recognize the .zip extension as a valid file type for PDA files so is this simply an issue of renaming that file and removing the .zip from the extension? If so then the OP needs to be corrected to include this step because otherwise people will sit there wondering why this same thing is happening to them.
For reference Odin PDA File extensions are *.tar, *.md5, *.smd, *.gz and *.tgz.

demonr6 said:
Question. I followed the instructions which are more or less the same as what I did to root my S4. When I enter download mode in the device and open Odin (v3.047) and I select the folder where I downloaded the CWM file, T210.CWM.6.0.4.5.recovery.tar.zip, I am not able to see that file in the selection.
Odin itself does not recognize the .zip extension as a valid file type for PDA files so is this simply an issue of renaming that file and removing the .zip from the extension? If so then the OP needs to be corrected to include this step because otherwise people will sit there wondering why this same thing is happening to them.
For reference Odin PDA File extensions are *.tar, *.md5, *.smd, *.gz and *.tgz.
Click to expand...
Click to collapse
it was the link towards yours, which is the tar file, which popped up on mine when i used odin 3.07, thats actually interesting, because i redid the steps and it showed up, let me look at it again, and thanks to you we can do this

demonr6 said:
Question. I followed the instructions which are more or less the same as what I did to root my S4. When I enter download mode in the device and open Odin (v3.047) and I select the folder where I downloaded the CWM file, T210.CWM.6.0.4.5.recovery.tar.zip, I am not able to see that file in the selection.
Odin itself does not recognize the .zip extension as a valid file type for PDA files so is this simply an issue of renaming that file and removing the .zip from the extension? If so then the OP needs to be corrected to include this step because otherwise people will sit there wondering why this same thing is happening to them.
For reference Odin PDA File extensions are *.tar, *.md5, *.smd, *.gz and *.tgz.
Click to expand...
Click to collapse
yea so its odin v3.07 and it is basically your steps lol, like every detail, but just a twist for our model sm-t210R model k, this method is for basically anyone who messed up their tablet because they did the prerooted version for sm-t210r,

Yeah, I thought it would be a quirk. I used an older version when I was mucking around with my GS4 and had a similar issue but by removing the .zip in the file name it recognized it and worked. My work around with this one though was unzipping the file contents and pointing to the unzipped file. Never a dull moment.
For a while it was a scare though yesterday because something screwed up with recovery and I got the dreaded screen flicker and could not find a way to correct it. Not only that but I was already having issues with recovery that I could not get any of them to install. I kept getting permission issues. I ended up blind guessing things and was able to fix it by using TWRP 2.6.3 MK1 then when that was fixed I used ODIN to install the T210RUEAMK1_T210RXACAMK1_XAC to get things back to stock'ish. From there I was finally able to root the device with the universal-root-signed-zip.
This nightmare has me gun shy and I am hesitant to even want to attempt a custom ROM now. I've successfully rooted my wife's HTC Sensation which was a series of hoops, my previous GS2, GS3 and the GS4 without ever so much as a hiccup. My personal phones I am a ROM whore. When I installed the triangle away last month and checked the counter on the GS4 I had 31 on the counter.. in four months. Unless there is a bullet-proof ROM for this pad I don't see it happening. It blows, I may unload it and get something different that is not so much of a mess.
Thanks for the replies guys.

demonr6 said:
Yeah, I thought it would be a quirk. I used an older version when I was mucking around with my GS4 and had a similar issue but by removing the .zip in the file name it recognized it and worked. My work around with this one though was unzipping the file contents and pointing to the unzipped file. Never a dull moment.
For a while it was a scare though yesterday because something screwed up with recovery and I got the dreaded screen flicker and could not find a way to correct it. Not only that but I was already having issues with recovery that I could not get any of them to install. I kept getting permission issues. I ended up blind guessing things and was able to fix it by using TWRP 2.6.3 MK1 then when that was fixed I used ODIN to install the T210RUEAMK1_T210RXACAMK1_XAC to get things back to stock'ish. From there I was finally able to root the device with the universal-root-signed-zip.
This nightmare has me gun shy and I am hesitant to even want to attempt a custom ROM now. I've successfully rooted my wife's HTC Sensation which was a series of hoops, my previous GS2, GS3 and the GS4 without ever so much as a hiccup. My personal phones I am a ROM whore. When I installed the triangle away last month and checked the counter on the GS4 I had 31 on the counter.. in four months. Unless there is a bullet-proof ROM for this pad I don't see it happening. It blows, I may unload it and get something different that is not so much of a mess.
Thanks for the replies guys.
Click to expand...
Click to collapse
i feel ya man, i been messing around with roms also only one i got to work was rocket lite, but that gave me a few bugs, so i just recovered back to rom, the only reason i used kies because when i would go to the samsung site to get the file for it, it was busy and would never download, so i found this method to just root our sm-t210R model K, so far i can't even get kernals to work either, like for exp cwm, you need that version or your screen flickers, its really anoying, unless you have that one, truthfully i think the most hard models to root or install rom, there are certain types of cwm, rom, etc just for it. Like how odian 3.07 only works with the cwm file, i used the new one but i get a bad screen or it doesn't even load...pretty much a big middle finger

Yeah, it kind of sucks and after coming from the S4 being able to pretty much throw everything at it and it works including the first versions of 4.4.. this tab has been a pretty big let down for me. I was going to try Rocket Tab but the download time is ridiculous so going to give Crash ROM an at bat next.

biggyhead said:
my bad i was busy with work but, kies just gets you back to stock version, and this is for sm-t210r, which i rooted from stock version using this method, but it seems you have sm-t10 regular, if you have that, odin would do just fine this is for your model, this method is for sm-t10R, and model number
Click to expand...
Click to collapse
I don't understand why it would though.
SM-T210 and SM-T210R are identical except the R model has infrared. Everything else is identical.