yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 General] Jamison904:
I m uploading a dump for the SM-T210R so we can get this thing rooted. Here is the build.prop for anyone wanting to look. Dump - http://d-h.st/zmN

Root thread in development section

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JZO54K
ro.build.display.id=JZO54K.T210RUEAMF1
ro.build.version.incremental=T210RUEAMF1
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Sun Jun 2 21:57:39 KST 2013
ro.build.date.utc=1370177859
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-63
ro.build.tags=release-keys
ro.product.model=SM-T210R
ro.product.brand=samsung
ro.product.name=lt02wifiue
ro.product.device=lt02wifi
ro.product.board=PXA986
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product_ship=true
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=mrvl
ro.build.PDA=T210RUEAMF1
ro.bootloader=T210RUEAMF1
ril.sw_ver=
ril.official_cscver=I8268CHNALK2
ro.build.changelist=1219080
ro.build.modelname=SM-T210R
# ro.build.product is obsolete; use ro.product.device
ro.build.product=lt02wifi
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=lt02wifiue-user 4.1.2 JZO54K T210RUEAMF1 release-keys
ro.build.fingerprint=samsung/lt02wifiue/lt02wifi:4.1.2/JZO54K/T210RUEAMF1:user/release-keys
ro.build.characteristics=tablet
# end build properties
#
# system.prop for nevocmcc
#

# System property for Default Brightness
ro.lcd_brightness=195
ro.sf.lcd_density=160

# minimum brightness value
ro.lcd_min_brightness=20

# rotation setting in potrait mode.
ro.sf.hwrotation=270

ro.kernel.qemu=0
ro.carrier=wifi-only

#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=1
persist.service.blcr.enable=0
persist.sys.tools.enable=0
ro.wifi.active_roaming.enable=true
ro.tel.config.path=/system/etc/tel/
ro.sf.lcd_density=240
ro.carrier=unknown
ro.com.google.clientidbase=android-samsung
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.sec.fle.encryption=true
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.config.voip_dvfs_freq=3
ro.error.receiver.default=com.samsung.receiver.error
ro.tvout.enable=false
ro.setupwizard.mode=DISABLED
ro.com.google.apphider=off
ro.com.google.gmsversion=4.1_r5
boot.fps=9
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
[Galaxy Tab 3 General] mythi:
Could you dump the boot IMG please so that I can root it what the heck Samsung why don't you realise sources fast
[Galaxy Tab 3 General] Jamison904:
Brain fart. What is the command line?

Dump - http://d-h.st/zmN

/system	ext4	/dev/block/mmcblk0p14
/cache	ext4	/dev/block/mmcblk0p15
/data	ext4	/dev/block/mmcblk0p17 length=-16384
/efs ext4 /dev/block/mmcblk0p6
/misc emmc misc
/boot	emmc	/dev/block/mmcblk0p9
/recovery	emmc /dev/block/mmcblk0p10
/bootloader	emmc	/dev/block/mmcblk0p5
/modem	emmc	/dev/block/mmcblk0p8
/sdcard	vfat	/dev/block/mmcblk1p1	/dev/block/mmcblk1e
/preload	ext4	/dev/block/mmcblk0p16

dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p10

Info for me. This is how to install a recovery through terminal straight from the tab (odin not needed.) BE VERY CAREFUL! This can really jack you up!
[Galaxy Tab 3 General] jesmann:
I just started a pull for the same thing for system. I couldn't get it out of my wife's hands until now.
[Galaxy Tab 3 General] Jamison904:
Yeah I am going through with draw here....lol. I can't wait to get a hold of the source so I can build my kernel. Heck I am about to build a ROM from the dump
[Galaxy Tab 3 General] eggert82:
I just bricked my Tab 3 installing the wrong 4.2.2 firmware... anyone know where I can download the original official Tab 3 7.0 SM-T210R firmware?
[Galaxy Tab 3 General] mirrin:
umm there is no right 4.2.2 firmware yet the 7 shipped with 4.1.2 the 8 and 10 got 4.2.2 as far as a factory firmware not released yet and unless a rom can be made from the system dump your stuck waiting till the factory image gets released.
[Galaxy Tab 3 General] eggert82:
I'm attempting to download and install 4.1.2 australian version... if that doesn't work then I'm sure I can return it to Wal-Mart tomorrow lol
[Galaxy Tab 3 General] mythi:
Does it include the boot.img
[Galaxy Tab 3 General] Jamison904:
Lol, I won't ask if you knew the command line to pull the boot.img if it did now would I?
[Galaxy Tab 3 General] mythi:
actually the kernel source has been realsed check it here press ctrl+F and search for SM-T210

if you want to dump the boot.img it is impossible with out root sorry
[Galaxy Tab 3 General] Jamison904:
Sweet. Looks like I am building a kernel before we have root
[Galaxy Tab 3 General] Jamison904:
Here for those who don't want to download the source - https://github.com/jamison904/SM-T210_kernel
[Galaxy Tab 3 General] mythi:
Could you compile a boot.img from the source code and i will make an odin flashble file to flash a rooted rom so we can get a better idea for how the system works and define the mount points.
[Galaxy Tab 3 General] Jamison904:
We still need the ram disk for the boot.img. All the source will allow for is the zimage.
[Galaxy Tab 3 General] mythi:
Then how would we root this thing there must be an expliot ore something

---------- Post added at 06:40 PM ---------- Previous post was at 06:22 PM ----------

i actually noticed spomething in the build build.prop what is it??

ro.sec.fle.encryption=true
[Galaxy Tab 3 General] emwno:
as far as i remember you need root to dump anything except /system. so, this wont work until you have root.

get the partition you want:

cat /proc/mounts

to pull partition:

dd if=[partition point here] of=/sdcard/[partition name here]
[Galaxy Tab 3 General] mythi:
Yeah you are right but we need the boot img at least the recovery.img ???
[Galaxy Tab 3 General] emwno:
Im getting it for the tab 7.0 and 8.0 (recovery and ramdisks), as well as im working on root for it. will post, when i have something.

---------- Post added at 07:01 PM ---------- Previous post was at 06:44 PM ----------

Anyone have a galaxy tab 8.0 (SM-T310 just to be safe), i may have a working root solution for it.
[Galaxy Tab 3 General] mythi:
Well actually no we are trying to root the 7.0 version i think no one intrested in 8.0 and 10.1
[Nexus 7 (2013) Android Development] Jack$on:
I'm installing system and boot.

Rebooting without installing recovery

trying to keep TWRP recovery.

How long should I wait on the Boot image X?

---------- Post added at 07:27 PM ---------- Previous post was at 07:25 PM ----------

Also should I relock device?

Thanks for the work! and help!

---------- Post added at 07:30 PM ---------- Previous post was at 07:27 PM ----------

Didn't work for me.

Going to try again. but first lock device hopefully.

After installing system and boot. Recovery still had storage as 0 mg.

If I figure it out.... I will let you know
[Nexus 7 (2013) Android Development] Nburnes:
Try booting back into recovery and formatting data again.
[Nexus 7 (2013) Android Development] Jack$on:
All working!!!

HAD to install all three files.

Wish I knew what I can do to get root without system going into 0 mg and wiping system. H'm?
[Nexus 7 (2013) Android Development] fix-this!:
can you please host these somewhere else? firefox will not download from that site for me.
[Nexus 7 (2013) Android Development] Nburnes:
Uploading to Dropbox as well now.
[Nexus 7 (2013) Android Development] fix-this!:
how long will the tablet boot after doing this? seems to be taking forever on the nexus boot logo.
[Nexus 7 (2013) Android Development] dexgen:
Can anyone else who followed this method verify if the Dropbox app is working for them? I keep getting the "Storage full or unavailable" error whenever I try to download something from dropbox (which I'm guessing is caused by messed up permissions.)

Thanks.
[Nexus 7 (2013) Android Development] Bawls:
Thank you! I wasn't paying attention and wiped /system (with the other partitions) when I couldn't get past the boot screen after unlocking/flashing TWRP. Flashed your system.img and like you said, already rooted \o/. Score,
[Nexus 7 (2013) Android Development] Nburnes:
If you still haven't gotten it to boot, reboot to bootloader, select recovery, at android with red triangle press Power and VOL UP at the same time once. Select wipe data/factory reset then reboot system now afterwards.

And Dropbox keeps erroring (4xx) whenever it gets fully uploaded, so idk mate :(
[Nexus 7 (2013) Android Development] dexgen:
Is the dropbox app working for you? ie. can you download files from the cloud to your tablet?

I'm getting all sorts of errors from apps that interact one way or another with the file system. Dropbox can't download, quickpic can't generate a database etc. etc.
[Nexus 7 (2013) Android Development] Nburnes:
Nope. Must be an issue with the app and 4.3

Edit: Redownloaded and it worked just fine.
[Nexus 7 (2013) Android Development] phuduong:
When you buy Nexus 7 2013, you should know you have to live with some smalls bugs especially applications because it is very new.... lolz
[Nexus 7 (2013) Android Development] dexgen:
I don't think it's a small bug. Almost every app that interacts with the file system is acting funny. Dropbox, quickpic, titanium etc etc. (The fix for titanium is known)

Also, at this point I don't know if the problem is with just those of us who followed this procedure or the device as a whole. I have 4.3 on my Nexus 4 and it doesn't have this problem.

---------- Post added at 08:38 PM ---------- Previous post was at 08:33 PM ----------

I have Dropbox on my 4.3 Nexus 4 and it's fine.
[Nexus 7 (2013) Android Development] Nburnes:
I do not know mate. Make a thread in Nexus 7 application forum asking others as this really isn't the place, not to sound rude.
[Nexus 7 (2013) Android Development] Blades:
Did you post the dropbox link? TWRP screwed up my data partition.. did the same thing on my SGS4. Need the stock recovery. Thank you so much for this.
[Nexus 7 (2013) Android Development] dexgen:
Mate, I have verified that unrooted devices do not have this problem. So the problem is either with the rooting procedure or your system image. Now I do appreciate the help you're providing people and I'm not trying to cause trouble here, just trying to figure out what's wrong with our devices.
[Nexus 7 (2013) Android Development] Nburnes:
I'm sorry, but every time I've tried to upload to Dropbox it errors out on me. :(

I do believe it is Dropbox or your device. I just tried multiple file sharing apps and they worked fine, including Box and Google Drive and they all pulled to /sdcard/Downloads just fine.

I actually even just retested Dropbox > clicked on a file > Export > picked Downloads and it downloaded just fine

I am sorry, I don't know whats up with the issue you're having :(
[Nexus 7 (2013) Android Development] Blades:
What about google drive? Or perhaps just the recovery? Mega has actually frozen on me twice now. The first time it was adorable and froze at 51%. It also creeps me out that it downloads to cache or something. Like a little phantom download. Yikes. I think its stalling out again.
[Nexus 7 (2013) Android Development] Nburnes:
OP updated with Google Drive upload
[Nexus 7 (2013) Android Development] Blades:
Thank you.. But I gotta warn ya.. You'll probably get a lot of requests for permission!
[Nexus 7 (2013) Android Development] Nburnes:
Yea, forgot to change it to public. :silly:
[Nexus 7 (2013) Android Development] phuduong:
Small bugs, I tried to polite with google, laughing
[Nexus 7 (2013) Android Development] androidfr33k:
Maybe this is something that has to be already known but should these commands be run after you do a "./adb reboot bootloader"?

Also once you done and you go back into recovery you hold down the power button the click the volume upward or downward away from the power button? I tried both and it never gets to any screen with choices to wipe data etc.

I'll keep trying.

EDITED:

What I should have asked is should we boot into fastboot to do the restore of images etc?
[Nexus 7 (2013) Android Development] phelixian:
Thanks this saved my butt after a weird issue with TWRP. THANKS THANKS THANKS!
[Nexus 7 (2013) Android Development] Nburnes:
Yes, you should be in the bootloader. Fastboot commands only work from the bootloader unlike ADB which works in both the system and recovery.
[Nexus 7 (2013) Android Development] scream4cheese:
Thanks! This worked beautifully! :good::good::good::good::good::good:
[Nexus 7 (2013) Android Development] macaumen:
SuperSU just got updated to 1.51 but I cannot get the binary updated. It just got stuck at the installing page.
[Nexus 7 (2013) Android Development] mssam:
DL the zip from chains thread and flash it in recovery...
[Nexus 7 (2013) Android Development] macaumen:
I have stock recovery.
[Nexus 7 (2013) Android Development] casonswag:
I need help guys!! Idk why its hanging at the flash system part its taking forever and now i dont have a system to bootup to what can i do how long does it take for the system to start flashing?

---------- Post added at 01:44 AM ---------- Previous post was at 01:24 AM ----------

Wow i did not know this wipes everything even the internal sdcard omg
[Nexus 7 (2013) Android Development] donshaffer:
This is what I get after flashing system.img:

C:\IMAGES>fastboot flash system system.img

erasing 'system' ...

OKAY [ 0.469s]

sending 'system' <471504 KB>...

FAILED <data transfer failure <Too many links>>

finished. total time: 9452.891s
[Nexus 7 (2013) Android Development] Nburnes:
/system on these devices is quite large and takes a good while to be pushed and set-up on the device. My fastboot time at the end was in the hundreds of seconds.

It is a full restore, just like if you used Google's factory images.

From my reading around, and I've never had this issue, it seems it can be different things.

A) Your cable

B) Your USB port

C) Drivers not set up correctly

D) Android tools not set up correctly

E) Any combination of that.

I haven't found a definite cause of this issue on any of the multiple pages I read about it on. :( Though, it seems like the cable and USB port are being the most common with a fix of just switching both of them.
[Nexus 7 (2013) Android Development] casonswag:
Thanks man yea i see it is huge ima just be more patient next time but its working fine thanks i like that its pre rooted
[Nexus 7 (2013) Android Development] androidfr33k:
Very odd and did this 4 times now. SuperSU is installed and I still have root access? Doesn't flashing the system.img basically put it back to stock?

I even tried my backup system.img before I rooted with same results? I just can't figure out how SuperSu can still be there and how I can still be rooted?

EDITED:

I just uninstalled SuperSU through its settings. I thought when you erase then flash the new boot/system there would be no remnants of a root? When I checked with root checker it said the device was still rooted!!

I did install clean rom just before and I know there was an issue with the Mac address changing on the device reported on that thread, which was fixed in the latest version. I also did format and reset to factory settings. Just can't explain this one.
[Nexus 7 (2013) Android Development] Nburnes:
The OP mentions this image is pre-rooted. ;)
[Nexus 7 (2013) Android Development] androidfr33k:
So I tried it on my backup images and from the thread One CLick Restore ( Dead or Alive) images which I know for sure are factory images.

I am going to post over there to see if its something with TWRP or possible SuperSu.
[Nexus 7 (2013) Android Development] Fulbring:
Thanks man! It worked.

Just a slight note for people who got stuck on a step like I did. My Nexus 7 was not rooted but I still had SU installed and I had clockwork mod recovery instead of TWRP. I wasn't having any memory trouble, it was just I didn't install the root properly and messed it up by doing some random stuff I don't wanna get into cause its weird.

So I wanted to reset the entire thing and start from scratch. I followed the instruction as posted but after formating and putting all the FASTBOOT commands I restarted my tablet and I just had a Android sign with a red ! mark. There was no TWRP/Clockmod recovery. If people get stuck at thst follow this:

1. Hold the Power Button and Volume Down until the device shuts off.

2. Enter Bootloader and install the recovery again, by putting in the command of "fastboot flash recovery" ( I recommend TWRP now cause it works).

After this just follow his steps again and you should be good to go!

I hope this helps someone!
[Nexus 7 (2013) Android Development] RayLancer:
Very nice. Though I was hoping for something closer to stock (un-rooted) restore images. I had some weird boot loop issues with TWRP and I don't think it rooting was really necessary for what I wanted to do.
[Nexus 7 (2013) Android Development] Jamison904:
Here is a faster mirror for you man, feel free to add to OP Download link. Thanks for this. Stupid TWRP 2.6.0.0 caused boot loop for me. This worked great. Also if not running as root they would need to do sudo before fastboot
[Nexus 7 (2013) Android Development] casonswag:
Wth read this !!! http://www.androidpolice.com/2013/...m-ever-being-published-jbq-strongly-implies/
[Nexus 7 (2013) Android Development] Nburnes:
Thanks for this duderino.
[Nexus 7 (2013) Android Development] armoguy94:
This worked perfectly for me. Thanks!
[Nexus 7 (2013) Android Development] Nburnes:
Hope it is known you can unroot from within SuperSU itself.
[Nexus 7 (2013) Android Development] creeseph:
Thank you,this saved me. I thought i would have to install windows on the mac to fix my botched root attempt.
[Nexus 7 (2013) Android Development] crikev2:
Thanks for this

I just bought my n7 v2 first boot it would never load so upon further investigation there was no rom or recovery at all on my tablet, this post saved me from returning the tablet, had to install custom recovery and not wipe recovery but got it up and running thanks again for the post.
[Nexus 7 (2013) Android Development] Perka:
Hi great thread :)

Any chance you can tell me how you did the .imgs?

with yaffs?

Or

mkisofs -o /path/to/the/system/folder ~/system.iso

dd if=~/system.iso of=~/system.img

rm ~/system.iso

Any help is welcome :)
[Nexus 7 (2013) Android Development] Nburnes:
dd if=/dev/block/(partition mmcblkwhatever) of=/sdcard/********.img
[Nexus 7 (2013) Android Development] Airwolf79:
I keep getting "error, cannot load boot.img" etc... my computer definitely sees my device. What should I do? Also, I was able to erase the boot, system, and recovery, so am I SOL now?
[Nexus 7 (2013) Android Development] minazaki:
Thanks - this is very useful. IMO, this thread should be stickied until we get official factory images.
[Nexus 7 (2013) Android Development] matthew0776:
Have u tried a tool kit(Wug fresh) to flash boot and sys img...I've had similar probs but on a mac. For pc I use Wug fresh if fastboot is acting up ... Can u flash twrp in fast boot...? If so do that and use adb to push a Rom zip to tablet. Jus make sure u place zip after it's pushed in sdcard folder b4 u flash. But if u can get it done in fast boot that's the best way ...

Candy Painted
[Nexus 7 (2013) Android Development] minazaki:
I'd like to dump the remaining stock partitions: bootloader, baseband, userdata, cache, misc (am i missing any others)? I'm trying to figure out the partition table so I can get the mmcblk for each of those partitions and dump them. Any advice?

Thanks again for this. As I mentioned before, I think it's sticky-worthy.
[Nexus 7 (2013) Android Development] Perka:
adb shell

cat /proc/mounts | grep /dev/block

found it here http://xdaforums.com/showpost.php?p=30189789&postcount=3

EDIT: or maybe this? https://play.google.com/store/apps/details?id=com.cls.partition&hl=en
[Nexus 7 (2013) Android Development] minazaki:
Thanks, not sure that gave me the information I needed. Here's what I've tried so far:

u0_a78@flo:/ $ busybox cat /proc/partitions
major minor #blocks name

7 0 7308 loop0
7 1 7308 loop1
7 2 2111 loop2
7 3 9387 loop3
7 4 4190 loop4
179 0 30539776 mmcblk0
179 1 87536 mmcblk0p1
179 2 3072 mmcblk0p2
179 3 3072 mmcblk0p3
179 4 15000 mmcblk0p4
179 5 780 mmcblk0p5
179 6 780 mmcblk0p6
179 7 780 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 1500 mmcblk0p9
179 10 1500 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 5120 mmcblk0p12
179 13 512 mmcblk0p13
179 14 16384 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1 mmcblk0p16
179 17 1500 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 5120 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 860160 mmcblk0p22
179 23 573440 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 10240 mmcblk0p25
179 26 8 mmcblk0p26
179 27 8 mmcblk0p27
179 28 1 mmcblk0p28
179 29 32 mmcblk0p29
179 30 28180463 mmcblk0p30
254 0 7308 dm-0
254 1 7308 dm-1
254 2 2110 dm-2
254 3 9387 dm-3
254 4 4189 dm-4

root@flo:/ # busybox fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 31.2 GB, 31272730624 bytes
256 heads, 63 sectors/track, 3787 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes

Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 266306 2147483647+ ee EFI GPT

127|root@flo:/ # busybox cat /proc/mounts | grep /dev/block
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nodelalloc,data=ordered 0 0
[Nexus 7 (2013) Android Development] minazaki:
Installed Heimdall and ran the command you suggested. I get:

ERROR: Failed to detect compatible download-mode device.

I think Heimdall is only for Samsung devices, no?

Oh well. Don't want to clutter this thread any more than I have. Besides, it's not urgent, just thought why not dump all stock partitions, since Google will not be giving us a factory image for the new N7.
[Nexus 7 (2013) Android Development] Airwolf79:
I'll try wug fresh. I did try "One click restore, dead or alive", but it didn't work. My PC is an old pos, so I've been mostly trying this with my Mac. TWRP is installed and I can see my device thru adb, but when I try to push a file, it doesn't see my device. Any other suggestions?
[Nexus 7 (2013) Android Development] Airwolf79:
Finally got it to work, although I wasn't having any luck on my PC, probably because it's really old. I flashed the boot, system, and recovery img's from ATGadmin's "One click factory restore" thread through fastboot on my mac. In case anyone else has a Mac, here's the commands I used. (My device was unlocked during process) First I downloaded and navigated to the Nexus_7_Restore_F folder in terminal (cd /users/.....), made sure it saw my device in fastboot mode (fastboot devices), then

fastboot erase boot

fastboot erase system

fastboot erase recovery

fastboot flash boot boot.img

fastboot flash system system.img

fastboot flash recovery recovery.img
[Nexus 7 (2013) Android Development] Nburnes:
They are there in the first post. You can pull all of them if you want, and in fact I have, I just have found no need to distribute them. Not sure what all the sbl, aboot, tz, rpm images are so I didn't give them out.
[Nexus 7 (2013) Android Development] matthew0776:
Factory system img is up...

Finally...

https://developers.google.com/android/nexus/images#razor

Candy Painted
[Nexus 7 (2013) Android Development] Perka:
Ok thx, and how did you find all the partitions with what is in them? sbl recovery etc :)
[Nexus 7 (2013) Android Development] Nburnes:
Once again in the OP

adb shell

$ su

# cat /cache/recovery/last_log
[Nexus 7 (2013) Android Development] sopidos:
Big thanks :D though step 4-6 is probably not needed if you get the latest JSS15Q factory image, right?