Develop Bugs

Asia Firmware DXJM4

Reference http://www.samfirmware.com/WEBPROTECT-p1000.htm
Saw under the Asia Firmware 'P1000DXJM4 ## ODIN 1.7 | P1.PIT | Version 2.2 | 2010 December' is available and to be cautious, i seek seniors' opinion before i go ahead and flash mine ^^
Any recommendation on how to proceed is appreciated, esp with ODIN (dont know what it is even read so much about this word)!
I already backup with TB
edit: Connect to Kies and says 'This device's version cannot be updated.' Stating PDA: JK2 / Phone: JJ2 / CSC: JJ2. now even more confused
edit update after flashed JME instead of JM4 (long story short):
"i will write down the event by event of recovery as reference:
1. flash the JVJL1 (no problem on reboot) by mistake then flash JM4 (missing dbdata.rfs) tar file downloaded from samfirmware.com and failed to reboot due to the missing file.
2. did some silly step and resulted in (phone .. ! .. pc) icon
3. run odin 1.7 and plug the usb and odin show is connected with tab
4. flash JM4 (yes with missing dbdata.rfs) and able to bring the tab back to download mode but unable to reboot into tab
5. flash Roto's dbdata.rfs file (http://forum.xda-developers.com/show...91&postcount=1) and able to reboot right after but missing pda & csc info (*#1234#)
6. tried the hard reset (http://forum.xda-developers.com/show...&postcount=106) but no help
7. download Roto's pre-rooted JME 3 files as mentioned (http://forum.xda-developers.com/showthread.php?t=895827) and finally boot the tab with full *#1234# details.
* So if you see the (phone .. ! .. pc) icon dont panic. like KChauJen said, able to solve with enough reading. i listed my route to recovery as reference to give you positive hope to retry.
TB's backup in Internal SD and before flashing JME, i copied the TB folder to my hdd during the missing pda & csc boot and did a backup on JME reboot, copy paste back to TB folder under internal sd and the restore work flawlessly."

cant be updated? er, i was from jk2 to jm4. did you applied oclf? if you did, try undo it b4 anything.

Hi fastcx, thanks for replying and sharing your experience. I did some further reading in some singapore forum saying have to run the kies patch (http://forum.xda-developers.com/showthread.php?t=835628) and spoof firmware version in order to update. i have yet to try due to somewhere in the same forum also said that once updated:
1. cant go back version
2. z4root wont work (which i am already using)
may i know have you rooted your SGT? need more solid info before taking the route to update the firmware as already using SGT as my primary device. I havent OCLF yet

rooted, since day 1, after every update (jj1>jj2>jk2) able to root with z4root till jm4 which requires SOC(SuperOneClick). To use kies, switch back to samsung default launcher b4 u connect using kies. I do not have any issue there. Another note is that after root, i always go back to /system/app to check n remove any apps that I do not need using adb shell.
The interface changed, to darker color, dlna client really working now, oclf performance improvement might not be obvious this time around. I suspect they really optimized it, everything is more stable now. Over protective I would say, cause any previous flashlight apps isnt going to sustain the led light for over 2sec. Default browser is a wee bit smoother now.
SuperOneClick is very easy to use anyway, so give it a try, oclf is useful only when u have over 400mb apps + loads of sms & contacts..anything related to I/O will have improvement.
The worse case scenario is just if kies still do not allow u to update, just use odin..what did you do previously? How do you update previously?

VNPython said:
Reference http://www.samfirmware.com/WEBPROTECT-p1000.htm
Saw under the Asia Firmware 'P1000DXJM4 ## ODIN 1.7 | P1.PIT | Version 2.2 | 2010 December' is available and to be cautious, i seek seniors' opinion before i go ahead and flash mine ^^
Any recommendation on how to proceed is appreciated, esp with ODIN (dont know what it is even read so much about this word)!
I already backup with TB
edit: Connect to Kies and says 'This device's version cannot be updated.' Stating PDA: JK2 / Phone: JJ2 / CSC: JJ2. now even more confused
Click to expand...
Click to collapse
Yeah... I'm in your case.
Thinking does it would be updated or not???
1. cant go back version
2. z4root wont work (which i am already using)
Click to expand...
Click to collapse
Just look at inside of tar file, and according to the Chainfire's Warning, the three files:
* boot.bin
* Sbl.bin
* zImage > 7,000K
So, this firmware would be has the protected boot loader. It would give us a lot of trouble in the future of updating and downgrading.
I think, this firmware can be updated with the help from Roto, eliminate the three files above and just take the PDA part.

I was using CSC: XEV (Vietnam) then to SIN (Singtel) and feel good and when Nov'10 update came, updated via Kies wihtout any trouble. When Dec'10 update came, tried with SIN resulted unable to update, switch back to XEV also resulted unable to update. I havent try XSO which the singapore forum stated successful for those with that CSC.
So i have to try to switch to XSO and report in later. be it protected boot loader or not, as long as we want stable and more 'juice' to service our daily SGT needs, no choice but to follow. I do believe as days goes, seniors like Roto alike will crack the nut for us to appreciate further.
on other note, my default email (not gmail) app seem got problem whenever you click reply or forward any email will result in force close. do not know if this bug related to after i switch from SIN to XEV (to try update) then switch back to SIN and follow up by restore using TB.
anyone has similar force close on the default email app?
backing up with TB now should we (those yet to update jm4) wait for Roto to do his magic for this update?
edit: tried with XSO and also unable to update... that really puzzle me.
edit 2: unroot with z4root and try still unable to update... now looking at ODIN route

perhaps odin route is the best solution for your case, but from jk2 > jm4 not sure if pit file is needed? repartitioning needs it tho, perhaps its good that u do back up of everything, let us know ur flashing result. Odin will definitely able to do the job

oh no... T_T somehow i downloaded P1000JVJL1 (Arabic) by mistake and Odin 1.7 with Auto Reboot & F. Reset Time, selecting the mistaken Arabic firmware (PDA) and flash it without any problem (JVJL1 / JXJK3 / JVJK4) and able to reboot itself.
After notice the wrong firmware, downloaded the right one (P1000DXJM4) from samfirmware.com and using Odin 1.7. Repeating the above steps but the phone briefly flash and came back the 'download mode' and nothing happened although Odin stated passed without any error.
I able to hold the power to shutoff and turn on again and the screen shows the samsung logo screen and stay flashing the word 'samsung' with 1 then 2 quick vibrate (like force close) and didnt boot into the main screen!
what should i do next?? is it bricked?? T_T
edit: the downloaded filename is 'P1000DXJM4_P1000DXJM2_P1000OLBJM1_HOME.tar' and anyone know if correct one?
edit 2: now i am downloading DXJK2 and see if i am able to revert the flash of JM4 T_T
edit 3: is over T_T saw the (phone .. ! .. pc icon)

This is due to dbdata.rfs missing. Please refer to the guide of flashing JMC/D/E series.
BTW, I have a problem is Camera Faulty error when start the camera app. Somebody mentioned that the LCD density can't set too small, but I have reverted it back to default 240, the problem still there. Any clue about it?
Sent from my GT-P1000 using XDA App

thanks dahuzi, i wonder if i choose to flash eu rom by Roto, would his rooted bring my tab back to operation? appreciate any help to bring back my tab.
i am able to bring my (phone .. ! .. pc icon) to the download mode. flashing anything before JM4 wont work anymore (fail at odin 1.7 and 1.3) and i am able to go back to hard reset option (holding vol up and power up). now i need to get the TB backup from the int SD before i try anything new. possible to retrieve in download mode?
edit: where to find the dbdata.rfs for this JM4? can anyother dbdata.rfs from other firmware able to fill it in? help ~ T_T

Hi VNPython,
Your case is complecated one, take it easy and read the thread from Chainfire "WARNING! Do not flash ... ", in there, a lot people has solved with different path.
Be patient, Bro. At that moment, your TAB is not Brick yet, but be careful because it's on the way of the End.
Wish you luck.
Take care.

ha.. i hope to win this war ^^ and learning the way of android!!
edit: just a quick question - does TB backup all user and app data in internal SD or External SD? i got bunch of files in my ext SD folder '.android_secure' and inside have files like 'com.keramidas.TitaniumBackup-1.asec' can any senior confirm is a valid TB backup files and can be used to restore my user & app data? many thanks!

TB (TitaniumBackup) file in the internal SD (in my case is the default), please double check.
Please give us your detail of winning as I'm scare of Samsung flash. My history is, 4 years ago, I bricked my Omnia phone Samsung after I flashed the rom from SIN to AUS. And, this's my second device on Samsung but this is Android and I want to learn the new OS.
Take care, Bro.

hey guess what? i managed to get a file for dbdata.rfs from Roto and got the tab back live but missing PDA and CSC field (checking with *#1234#). tried the reset to get the pda and csc back but failed.
learned quite a few things along the way and will update this thread after completing my mission to update my tab to JM4.
windows seem cant extract and tar file for android tar files. i tried to extract jm4 files and add dbdata.rfs into it but when flashing, it fail.
worst come to worst, flash the JVJL1 to get the working tab again
i hope Mr. Roto could let me know what software to install on windows that able to 'untar' and 'tar' properly with android (linux) files. tried 7z and winrar both cant untar without error.

try using winrar to do the add on of dbdata.rfs, anyway, good luck next time, double check what you downloading

fastcx said:
try using winrar to do the add on of dbdata.rfs, anyway, good luck next time, double check what you downloading
Click to expand...
Click to collapse
Wow... another Maitre!!! What's your winrar???
Look and read:
.....i hope Mr. Roto could let me know what software to install on windows that able to 'untar' and 'tar' properly with android (linux) files. tried 7z and winrar both cant untar without error.
Click to expand...
Click to collapse
Thanks

sorry for the late update as yesterday too late to post anything after able to get my tab back to life! the learning curve is nice and not stressing since many time i see the icon of (phone .. ! .. pc) yet i am able to bring the download (digging) icon back again always.
i will write down the event by event of recovery as reference:
1. flash the JVJL1 (no problem on reboot) by mistake then flash JM4 (missing dbdata.rfs) tar file downloaded from samfirmware.com and failed to reboot due to the missing file.
2. did some silly step and resulted in (phone .. ! .. pc) icon
3. run odin 1.7 and plug the usb and odin show is connected with tab
4. flash JM4 (yes with missing dbdata.rfs) and able to bring the tab back to download mode but unable to reboot into tab
5. flash Roto's dbdata.rfs file (http://forum.xda-developers.com/showpost.php?p=9305891&postcount=1) and able to reboot right after but missing pda & csc info (*#1234#)
6. tried the hard reset (http://forum.xda-developers.com/showpost.php?p=9482192&postcount=106) but no help
7. download Roto's pre-rooted JME 3 files as mentioned (http://forum.xda-developers.com/showthread.php?t=895827) and finally boot the tab with full *#1234# details.
* So if you see the (phone .. ! .. pc) icon dont panic. like KChauJen said, able to solve with enough reading. i listed my route to recovery as reference to give you positive hope to retry.
TB's backup in Internal SD and before flashing JME, i copied the TB folder to my hdd during the missing pda & csc boot and did a backup on JME reboot, copy paste back to TB folder under internal sd and the restore work flawlessly.
after 1 days usage, the trouble found is email app still being force close whenever you reply or forward any email. any senior have similar force close on original email app?

KChauJen said:
Wow... another Maitre!!! What's your winrar???
Look and read:
Thanks
Click to expand...
Click to collapse
My bad. How polite of you.
Back to topic, VNPython everything there is a first time it's good info here. Perhaps you can edit your 1st post with info from your last post?
EDIT: 1 thing though, do you have any issue regarding using samsung apps?

samsung app can use, checked my CSC and its KOR. Apps: Vlingo words to action, Vietnamese Dictionary application & blinkx Beat. didnt try any of them. just *#272*IMEI# and there's no SIN or XEV or XSO or Asian Sales Code in the Roto JME (EU) multiCSC. maybe will try to download multicsc with asian sale code.
* on the email app force close, i delete the email account and re-setup them, and the force close is gone. could be due to TB's restore? anyway, is solved ^^
I wonder will i be able to flash DXJM4 if there is a full tar file?

VNPython said:
....
I wonder will i be able to flash DXJM4 if there is a full tar file?
Click to expand...
Click to collapse
Please consider it carefully, Bro.
What I looked inside of the tar file, and according to Chainfire's Warning, it has the protected boot.
If we can eleminate the three files:
* Boot.bin
* Spl.bin
* zImage
and put back to the tar file with the encrypted code by Samsung (maybe we can ask Roto) then we can flash this modified firmware JM4.
FYI.

(notes)backup official firmware

hi i opened this thread for explain how to backup your official firmware.
first downgrade your phone so that kies will detect an upgrade for you.
Now read on to see how to save the
firmware files during kies upgrade process.
On your pc, check the option
"Show hidden files"
Now connect your phone to pc via kies to begin the firmware upgrade.
Kies will begin to download the
firmware files...
The files will be saved in tmp files called "tmpA4CE.tmp" or other names
you can find it easily.
In Windows 7, this
tmp file is located at,
C:\Users\ * \AppData
\Local\Temp or type temp in run command.
(* is the pc user
session name, e.g. C:
\Users\chenna
\AppData\Local
\Temp)
When download iscomplete, kies
decompresses this tmp file into a zip folder and begins the firmware upgrading process.
The folder has same name as the tmp file but now with an extention of zipfolder.
When kies begins the upgrade process
starting from 1% until
it reaches 100%, quickly copy the "zipfolder" to your desktop.
You have about 2 to 3 minutes to do this.
Kies will delete the folder once upgrade is 100% (completed).
The "zipfolder" contains all the firmware files kies has used to upgrade
your phone.
Now you have a backup of official firmware from kies.
This is also useful in case kies fails to
complete the upgrade process.
Just use the saved files and manually flash your phone using odin or multiloader.
IF YOU LIKE THIS POST PLEASE PRESS THANKS

[HOW TO] Extract Rom.zip From RUU

Extracting ROM files from HTC RUU
Official HTC ROM updates are released as RUU (ROM Update Utility), which you run on your (Windows) PC to get the target device updated automatically.
Some of the big brains in the Android community release RUUs re-packaged into signed update files,
which in turn allow for whatever ROM customization you can imagine.
In this how to I will explain how to extract ROM files from a RUU image,
which you can then customize and use to flash your device without the fear of a new bootloader possibly making your device unrootable.
Requirements :
Windows PC,
Microsoft Process Monitor,
File Archiver capable of extracting ZIP files(eg, 7ZIP),
Official HTC RUU for your Android device.
The process of extracting ROM files from a RUU is really straightforward.
The idea behind it is that the self-contained update utility first needs to unpack the update payload into a temporary folder before pushing it onto the device.
This is when we grab the ROM file...
1. download the official RUU
2. start Process Monitor.
3. press CTRL+L
4. change "Architecture" to "Process Name"
5. leave the "is" field as it is
6. in the empty field copy and paste the name of your
RUU file (eg, RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe)
7. click "Add"
8. change "Process Name" to "Path"
9. change "is" to "Contains"
10. in the blank field type "rom.zip" (without quotes)
11. click add
Click "OK" to set the filter and then run the RUU file.
Once the utility starts switch back to Process Monitor and look for an entry in the "Path" column that ends with "\rom.zip".
Right click on that line and select "Jump to..."
this will open a Windows Explorer window in the folder which contains the zipped ROM files
Copy the "rom.zip" file to some other folder, outside of the temp RUU folder tree (eg, desktop)
Once copied, close Process Monitor and the RUU utility.
The copied "rom.zip" file contains the following files:
android-info.txt - list of CIDs this RUU will flash to,
boot.img - root file system image,
hboot (followed by a version string) - boot-loader update,
radio.img - radio driver update,
recovery.img - recovery partition image,
splash1_Hero_320x480.nb0 - boot loader splash image,
system_rel.img - system partition image,
userdata.img - data partition image.
You can now, among many other things, root the ROM
and then flash the updated boot.img and all the other image files on to your device using Recovery​

it doesnt work... the process monitor colum is all blank after running RUU... there are no processes listed

munnibhai said:
it doesnt work... the process monitor colum is all blank after running RUU... there are no processes listed
Click to expand...
Click to collapse
you mst be doing something wrong i double checked the method and it still works fine for me..
make sure your environment is set up correctly and run everything as administrator or disadle uac in windows..

thanks for the reply, let me check it again...
i will post back to u

rom.zip corrupted
I followed the directions and like another post in here procmon shows a blank screen. I went to task manager and opened processes and saw when it ran then clicked open file location and found it. I did this twice and both zips are corrupt. (used winzip)
error [D:\android apps\EVO root\EVO\rom.zip]: start of central directory not found; Zip file corrupt.
Possible cause: file transfer error
when I close the RUU all the files in that folder disappear so you have to leave the RUU running while you copy the zip file or it's gone.
At least that's what I saw.

update to last post
I found a zip repair tool and was able to repair and extract the 1.10.653.2 RUU rom capture. I will have to try to run it later. If anyone gets corrupted zip error, Zip Repair pro will repair it.

To get the rom zip without any errors just run the ruu.exe file, when the box with a picture of a phone pops up, click start on pc, type in "run" and click on run then in that box that pops up, type in %temp% and click ok. Another window pops up then just scroll down to the most recent folder and rom.zip will be in there, if not it will be in the next folder.

Hi,
when I try to open the rom.zip I get an error message, it just said it cannot open with 7zip and with windows it says its invalid.
I tried downloading the RUU multiple times but still the same error. I rune the RUU as administrator.
Tried copying it over to different locations and then open it.
RUU_ENRC2B_U_JB_45_O2_UK_1.14.206.13_Radio_3.1204.167.31_release_289474_signed
HTC ONE X+
Thank you
Update:
I used Zip Repair Pro.. however there is no boot.img inside the repaired zip -_-

For those which have problem with making Process Monitor detect RUU temp folder, make sure You add whole file name of RUU including .exe at the end.

Jmcclue's steps, work perfectly, Thank you post #7

htc RUU Rom
Inside 4ndroid said:
Extracting ROM files from HTC RUU
Official HTC ROM updates are released as RUU (ROM Update Utility), which you run on your (Windows) PC to get the target device updated automatically.
Some of the big brains in the Android community release RUUs re-packaged into signed update files,
which in turn allow for whatever ROM customization you can imagine.
In this how to I will explain how to extract ROM files from a RUU image,
which you can then customize and use to flash your device without the fear of a new bootloader possibly making your device unrootable.
Requirements :
Windows PC,
Microsoft Process Monitor,
File Archiver capable of extracting ZIP files(eg, 7ZIP),
Official HTC RUU for your Android device.
The process of extracting ROM files from a RUU is really straightforward.
The idea behind it is that the self-contained update utility first needs to unpack the update payload into a temporary folder before pushing it onto the device.
This is when we grab the ROM file...
1. download the official RUU
2. start Process Monitor.
3. press CTRL+L
4. change "Architecture" to "Process Name"
5. leave the "is" field as it is
6. in the empty field copy and paste the name of your
RUU file (eg, RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe)
7. click "Add"
8. change "Process Name" to "Path"
9. change "is" to "Contains"
10. in the blank field type "rom.zip" (without quotes)
11. click add
Click "OK" to set the filter and then run the RUU file.
Once the utility starts switch back to Process Monitor and look for an entry in the "Path" column that ends with "\rom.zip".
Right click on that line and select "Jump to..."
this will open a Windows Explorer window in the folder which contains the zipped ROM files
Copy the "rom.zip" file to some other folder, outside of the temp RUU folder tree (eg, desktop)
Once copied, close Process Monitor and the RUU utility.
The copied "rom.zip" file contains the following files:
android-info.txt - list of CIDs this RUU will flash to,
boot.img - root file system image,
hboot (followed by a version string) - boot-loader update,
radio.img - radio driver update,
recovery.img - recovery partition image,
splash1_Hero_320x480.nb0 - boot loader splash image,
system_rel.img - system partition image,
userdata.img - data partition image.
You can now, among many other things, root the ROM
and then flash the updated boot.img and all the other image files on to your device using Recovery​
Click to expand...
Click to collapse
this is good working 100% thank you :good:

i_4_u89 said:
this is good working 100% thank you :good:
Click to expand...
Click to collapse
no problem and please instead of saying thanks please remember to hit the thanks button on threads first post..

works great, to bad you cant open the zip file

jpwhre said:
works great, to bad you cant open the zip file
Click to expand...
Click to collapse
You can open the zip. Go back a page n try the way i said.

jmcclue said:
You can open the zip. Go back a page n try the way i said.
Click to expand...
Click to collapse
note path is desktop (last post showed from temp folder) and i still get same results. did some searching and aperantly htc now signs their zip files and they can't be opened anymore. having usb issues that causes fastboot force close errors and need to be able to flash boot.img thru flashify app to return it to stock. ran the htcguru reset rom that uses aroma installer to return to stock that lets me take ota's but i get qualcom location force close and other custom roms give me issues forcing me to reset phone to stock every few days with guru installer. flashing recovery in fastboot is a chore as well. I have s-off and can keep it, but doing fastboot oem lock wont relock the bootloader, even though it shows success in cmd line. i can cid and super cid with fastboot.
it leaves me at a point where i really need to pull everything out of the rom.zip file and it wont open.
pic 1, 7zip wont open archive on desktop
pic 2, how i get recovery to flash
pic 3, results from running RUU
i have to reboot device, set comand to reboot bootloader, set command to flash recovery all faster than phone will do all commands to get it to flash, and RUU doesnt work that fast. i know im on sprint with htc one m7, but google search "extract htc zip" "extract rom.zip" both lead to this thread as top result. no other searches will tell me how to open the archive, except one that resulted in "htc signed zips can no longer be opened"

you're more than welcome to give it a go
http://forum.xda-developers.com/showthread.php?t=2795856 Sprint_HTC_One_m7wls_5.05.651.2_RUU.exe

Did HTC change the way they create the exe? I don't find it, the biggest file is data1.cab file that I can't extract.
I'm trying to extract the stock rom for an ATT HTC One Mini (m4) because RUU keeps crashing on me and won't install. I am also rooted with S-off.
If anybody can help me get the stock m4 rom so I can go back to stock, I would really appreciate it.

SyPete said:
Did HTC change the way they create the exe? I don't find it, the biggest file is data1.cab file that I can't extract.
I'm trying to extract the stock rom for an ATT HTC One Mini (m4) because RUU keeps crashing on me and won't install. I am also rooted with S-off.
If anybody can help me get the stock m4 rom so I can go back to stock, I would really appreciate it.
Click to expand...
Click to collapse
No they didn't change it. Some ruu's use a different format requiring the use of a tool called unruu instead of trying to capture the zip file when using the exe (I just learned this today). I've gone ahead and used unruu and the resulting zips have been put in a single tar file. you can download it from here for about 30 days after which ill have to delete the file. also i dont know which zip has what in it.

hi
master how to open Zip firmware !!?
i want to open zip firmware (PM60IMG.zip Desire 400)with 7zip ! but shows below error :
"can not open file PM60IMG.zip az archive "
how to pass this encryption ?

gandolf007 said:
hi
master how to open Zip firmware !!?
i want to open zip firmware (PM60IMG.zip Desire 400)with 7zip ! but shows below error :
"can not open file PM60IMG.zip az archive "
how to pass this encryption ?
Click to expand...
Click to collapse
https://github.com/kmdm/ruuveal/tree/f4936338f19841c75edafbe7e622242105cb39aa

Please Help...

after rooting my samsung galaxy s 6 SM-G920P it does not recognize my 32 gigs internal memory and Google Play keeps shutting down what do I need to do to fix these problems?

First let me ask how you rooted your phone? I ask because I am pretty sure that I can show you a method that doesn't break anything.
While you are answering that, here is how to restore:
Download the latest version of Odin from here: http://www.samsungodindownload.com/ Extract that to your desktop.
Download this file to your computer: https://www.androidfilehost.com/?fid=24343351889231947 (It is the latest stock file zipped up for the 920P. If you have a different phone, don't use this.)
Extract the .md5 inside. Only the .md5, leave the stuff inside as it is.
Follow this video and you should be back to stock: https://www.youtube.com/watch?v=tv0BnfpNxEs

Samsung Galaxy Tab 3 7.0 SM-T210 problem

I recently found my old tablet and it had kingoroot installed and then I flashed stock rom to my tablet but now it randomly restarts and every time i try to setup it i got error "Unfortunately, the process com.android.systemui has stopped" and "settings has stopped"
Here is the tutorial I followed:
Code:
The following instructions are for Windows only. Please don't use a virtual machine as these can cause problems communicating with the device. There is an alternative method for Linux or macOS. Just tell me if you aren't on Windows, I can easily change the instructions. Please make sure you have Windows set to display all file extensions. This can really help for debugging purposes.
First we need to download the tool that downloads the stock firmware. It's called SamFirm and it downloads it using Samsung's servers. You can download the latest version [here](http://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462). Please also make sure you have the [Microsoft Visual C++ 2008](https://download.microsoft.com/download/1/1/1/1116b75a-9ec3-481a-a3c8-1777b5381140/vcredist_x86.exe) and [Microsoft Visual C++ 2010](https://download.microsoft.com/download/5/B/C/5BC5DBB3-652D-4DCE-B14A-475AB85EEF6E/vcredist_x86.exe) x86 Redistributable packages installed. Now to download the tool that flashes to the devices different partitions. On most devices you use a tool called fastboot, but Samsung devices aren't like most devices (excluding the Galaxy Nexus). This tool is called Odin, it's Windows only and leaked from Samsung so you need to get it from a trusted source. You can download the latest version [here](https://build.nethunter.com/samsung-tools/Odin_3.12.3.zip). Extract the "Odin_3.12.3.zip" file. You should now have a folder called "Odin_3.12.3". Treat this as your working directory and download all other files to this folder. While you're here, extract the contents of "SamFirm_v0.3.6.zip" into this folder.
Now to download the stock firmware. Open "SamFirm.exe" and make sure "Auto" is checked and "Manual" and "Binary Nature" isn't checked. In "Model" put `SM-T210` and in "Region" put `BTU`. Click "Check Update" and wait for it to find the firmware on the server. Now check "Check CRC32" and "Decrypt automatically". Then click "Download" and save it. Let it finish downloading, checking, and decrypting. Once it finishes you can now close SamFirm. Extract the zip file it gave you. You should now have a single file ending in `.tar.md5` (you may also have `.dll` file, ignore it). This tar.md5 file is your firmware. Do not modify it. If you have more than one .tar.md5 file, tell me.
Now shutdown the device and then hold the Volume Down, Home/Bixby, and Power buttons. This should put the device into download mode. Accept any warnings then plug the device in. Open "Odin.exe" from the "Odin_3.12.3" folder. In the log, it should say `Added!` and have a blue COM thing near the top, meaning it detected your device. If it didn't detect it, then you may need to configure drivers (you can ask me for the drivers if you need them). Click the "Option" tab and make sure "F. Reset Time" and "Auto Reboot" is enabled. Also check the checkbox next to the "AP" button and then click the button. Select the tar.md5 file. Now click "Start" in Odin.
It should now reboot and go to the boot animation. If it doesn't boot in 15 minutes, shutdown the device. Then hold the Volume Up, Home/Bixby, and Power buttons. Then use the keys to select "Factory reset". Please note this will wipe all user data. Once it finishes you can select "Reboot" and now it should boot correctly.
I have been battling with this problem so long I only wanted to root my tablet to have some fun with root required apps
Any help with the problem? I only need to root the device or get it to work with stock rom