yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 10.1 Android Development] jerome.d:
First of all, sorry for the laaate reply, but things have been a bit hectic for me in the last two weeks (baby sick, some urgent matters at work, etc.).

So, yes, I finally understood by myself (actually the night after I posted my last message, I just didn't have time to come here to tell the story) that this "verify zip signature" was not some kind of md5 sum checking, but an "official" Android signature that root.zip and other files like that don't have. I also realised something else: I had never flashed CWM in the first place!

The first time I tried to flash CWM, everything went well but I had left the 'auto-reboot' check in Odin. Hence, I was always under stock recovery, without knowing it (I had never used stock recovery or CWM before). So my trials to flash "root.zip" could only fail since stock recovery does not allow you to not check the zip signature. Following your advice, I flashed TWRP without the 'auto-reboot'. Understanding that I needed to remove the zip signature check, I was able to flash root.zip without any further problems. Although I probably factory reset my tablet 5-6 times overall during the whole process.

A side note: I already flashed a number of roms (including some with non-stock recoveries) in the past for my Galaxy S2,3,4 and I never unticked the "auto-reboot" button in Odin, but it did not seem to bother the recovery flashing...

Thanks again for your help.
[Galaxy Tab 3 10.1 Android Development] kb8no:
I wondered where you went so thanks for getting back. This is about Samsung ideosyncrosies (e.g. Odin) superimposed on x86 ideosyncrosies. It's just trial and error until you find out what works. What it boils down to is it works just fine as long as you keep it simple, don't over analyze, and understand the basic principles.

1. Always uncheck autoreboot in Odin or you will flash the old recovery right over top of your newly flashed recovery. DO NOT do anything else and try to out guess Odin.

2. After flashing your new custom recovery in Odin, unplug your Tab, shut it down, and reboot into recovery to root your stock ROM with root.zip. DO NOT try to use Odin or fastboot or anything to reboot your Tab from your computer.

3. TWRP for this Samsung x86 is less glitchy than CWM and the new TWRP is a big improvement over old TWRP. (Be patient, the guys will eventually fix TWRP and CWM but since they work it is a low priority.)

4. Factory Reset (= full wipe in other terminology) only once with TWRP is all that is needed. DO NOT do any other wipes because it messes up somehow the partitioning unique to Samsung and x86. DO NOT change any TWRP settings, just use the default.

5. Don't do a dirty flash on general principles, just bite the bullet and do a full wipe and restore apps with Titanium and you will cause less problems and the baby won't cry.

6. Do Nandroid backups, this is alpha stuff. Particularly, the guys who understand this better than we do, like to setup the rooted stock to a usable form that is already logged in with the Google login widget with some basic apps and then do a backup so you can always restore a working ROM when you screw up.

7. Backups of this ROM are huge. Get as big an SD card as you can afford and tell TWRP to backup to the external SD. Don't bother with a 16G and go straight to at least 32G. (I just bought a 64 and haven't had time to test exFAT yet but I expect it will work.) The main problem with CWM is the backups take hours and are even bigger so don't go there.

8. Keep a copy in advance of the stock ROM (with stock recovery) on your computer with Odin incase you have to Odin back to stock for any reason. Basically you will not need to Odin back to stock if you don't try to get too fancy and keep it simple, unless you get sunk by one of these new alpha ROM's that we love to play with that screws up the partitioning. It's just as easy to Odin back to stock to fix a partitioning problem as it is to Odin TWRP so don't work yourself into a twit.

I'm new to tablets and I am really having fun learning how to understand them. Hope this information helps somebody as you seem to be over the hump now.
[Galaxy Tab 3 10.1 Android Development] brokie:
Just installed this on my 1 hour old Galaxy tab 3 10.1. Works fine! Thank you!
[Galaxy Tab 3 10.1 Android Development] chuko303:
Did you used the method in the op? You have CWM? easy peasy
[Galaxy Tab 3 10.1 Android Development] brokie:
Yes I did use that method. Flashed using odin.

Are you having trouble with flashing?
[Galaxy Tab 3 10.1 Android Development] chuko303:
Nope my friend havent got to it I am however going to do it today ! Exitted any tips?
[Galaxy Tab 3 10.1 Android Development] brokie:
Well if it is your first time doing it, I suggest you find a more detailed tutorial. The one in the first post is a bit incomplete.
[Galaxy Tab 3 10.1 Android Development] chuko303:
How did you do it m8? Mind sharing

---------- Post added at 12:58 PM ---------- Previous post was at 12:29 PM ----------

I cant find the downloaded files anywhere in odin to flash. I moved them to downloads after that to othwe folders and when I click on pda nothing shows where I put it
[Galaxy Tab 3 10.1 Android Development] brokie:
You have to extract the zip until you get the .md5 file. That is the one you need to flash in pda section.

Also make sure re-partition is UNCHECKED. Only reset f. Time or something like that should be checked.
[Galaxy Tab 3 10.1 Android Development] chuko303:
This is where I stand m8
[Galaxy Tab 3 10.1 Android Development] chuko303:
Got it. what about the "root. zip" do I have to also extract that? I dont think so huj

---------- Post added at 01:27 PM ---------- Previous post was at 01:23 PM ----------

Also is it normal that the date is 9/8/2013? Even tho its 2014. Why did it date like that? Is it the one I need dont want to brick my tablet
[Galaxy Tab 3 10.1 Android Development] chuko303:
Hey bro ignore the other posts I was wondering how can I make sure repartition is unchecked???? Al I see is repartition "PIT" but not an option to uncheck it?
[Galaxy Tab 3 10.1 Android Development] chuko303:
hahaha wow nevermind feel like an idiot. Its the weed I swear

---------- Post added at 02:03 PM ---------- Previous post was at 01:48 PM ----------

It said pass but the recovery didnt stick I had auto reboot unchecked. do I have to run it again or what
[Galaxy Tab 3 10.1 Android Development] brokie:
You can boot into CWM recovery by pushing and holding the volume up and power button simultaneously. Power and volume down boots into download mode.

If it said pass then it should work. You had to uncheck auto-reboot only because otherwise it would normally boot your device.

You do not have to extract the root.zip since you will flash that one using CWM and not ODIN. CWM works with .zip.

And one more thing. If you succesfully installed and booted into CWM I suggest you do a full backup of your device using CWM in the 'backup and restore' menu. In case you flash a bad rom you always have your original. Please note that this can take long. Maybe a few hours but it is worth it.
[Galaxy Tab 3 10.1 Android Development] chuko303:
Im going to flash TWRP via odin then will flash root.zip see if that helps. Heard it taks hours to backup rom in cwm and I dont doubt it .been using twrp since my evo 3D.
[Galaxy Tab 3 10.1 Android Development] brokie:
I also flashed TWRP. The same way I flashed CWM. It boots but haven't tested any options yet. But it seems alright.
[Galaxy Tab 3 10.1 Android Development] chuko303:
People have actually had a successful backup with CWM? Second time I tried with it and both failed seccomed time I deleted all the big files almost all my apps except 5. Seccond time I made my backup it was at 96% cant get TWRP to stick
[Galaxy Tab 3 10.1 Android Development] chuko303:
Can I just download a rom and the stock rom and flash away?
[Galaxy Tab 3 10.1 Android Development] brokie:
Yes you could. But it is not advisable. To be honest, I also do not have a working backup of my original rom.
[Galaxy Tab 3 10.1 Android Development] chuko303:
How did you get gravious workinv bro?
[Galaxy Tab 3 10.1 Android Development] brokie:
By follow the tutorial that is posted in his thread. Do everything except for the "wipe /system" part.
[Galaxy Tab 3 10.1 Android Development] chuko303:
So just like any other ROM I never wipe system, I do factory reset/wipe cache/dalvik and flash
[Galaxy Tab 3 10.1 Android Development] brokie:
Well yes. I did wipe the /system and it did not boot anymore. I had to download a stock rom. The one I downloaded that worked had some east European language, but after reset and wipe I installed Grievous and it worked with English language.
[Galaxy Tab 3 10.1 Android Development] chuko303:
Thanks for your help ive for grevious rom running great with wannam and other modules. Love how fast it is
[Galaxy Tab 3 10.1 Android Development] Brian9391:
having some issues here. maybe i missed something or its just a stupid mistake on my half, but odin is not showing anything to flash when i go to select the recovery in the download section in the OP.

Windows 7, tried running in administrative mode and also compressed vs unpacked. not sure why i cant find the CWM file. sure im looking in the right spot too. lol

would like to avoid TWRP cause its seemed so buggy last time i used it,
[Galaxy Tab 3 10.1 Android Development] :
hey

if i remember your have to dig into the zip file for the .tar.md5 image, and you might need to remove the .md5 extension:confused:
[Galaxy Tab 3 10.1 Android Development] Angel_666:
Yes. It's because recovery don't work and skipping. I think it's skipping because we need correct init binary for our platform. With original Samsung init - cwm recovery binary do not work and recovery hanging. With another init (in your test 5) system can not initialize itself and recovery skipping.

The only way that will work i think, is to build recovery for our platform from scratch. Need to setup build environment in linux, then pull cwm sources from git, then extract our platform props from original recovery and after that - compile new recovery image.

P.S. I hope i'm wrong but.... :D
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
When building recovery I used original recovery files to build a custom recovery.

I use cwm recovery builder, that gets all info from git repositories... After the build, all files looked correct.

I seem to get my tab today, so I can play without having to post and wait for reply.

Send via my BinDroided HTC ONE
[Galaxy Tab 3 10.1 Android Development] Angel_666:
In theory - you right, but all those git rep are for arm arhiticture. Ti Omap, Exynos, Tegra, MTK - all they have arm processors. And recovery building for arm eabi. We have x86 architecture and i don't see any device on x86 with builded and working CWM. Across Moto Razr i, but as i knew, recovery was builded manualy..

Anyway, i hope all to be OK. :)
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
If I view the build output, it is using x86 toolchain

I can post the output if you wanna see/explore?

Send via my BinDroided HTC ONE
[Galaxy Tab 3 10.1 Android Development] Angel_666:
Yes please, it will be good.
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
I attached the file
[Galaxy Tab 3 10.1 Android Development] Angel_666:
There is one thing, that i can't understood:

in new recovery: "ro.product.cpu.abi=armeabi-v7a "

in original recovery: "ro.product.cpu.abi=x86 "

Is this mean, that binary builded as armeabi?
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
try this
[Galaxy Tab 3 10.1 Android Development] Angel_666:
Same thing: galaxy tab logo, then blank screen (when we hold + button and device trying to open recovery), then reset and normal OS booting.

Btw. Samsung upload opensources for P5200 and P5210.
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
got it, and compiling a build as we speak
[Galaxy Tab 3 10.1 Android Development] Angel_666:
Hm... In they BoardConfig.mk device positioned as :

TARGET_ARCH := arm
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := unknown
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a-neon
ARCH_ARM_HAVE_TLS_REGISTER := true

I think it not correct.
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
At least I have a custom kernel runing:
[Galaxy Tab 3 10.1 Android Development] Doctor_XXX:
Nice!

But still no root or CWM yet?
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
the new x86 architecture wil keep us busy

But no worrys...
[Galaxy Tab 3 10.1 Android Development] Angel_666:
Good news! Here is correct values of our BoardConfig.mk:

TARGET_ARCH := x86
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := clovertrail
TARGET_CPU_ABI := x86
TARGET_ARCH_VARIANT := x86-atom

And one more thing: here is the links on Motorola Razr-i github sources (intel atom 2480), this must help us to configure building environmetnt.

oxavelar

HazouPH
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
Isn't boardplatform = atom?
[Galaxy Tab 3 10.1 Android Development] Angel_666:
Nope. Coz in our default.prop on device:

ro.board.platform=clovertrail

:)
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
I have the 1st preview of our CWM.

I can navigate with volume buttons, and menu button.

Power button, home button & back button are NOT responding

Also colours are messed up
[Galaxy Tab 3 10.1 Android Development] Angel_666:
Finaly! How you build it? Manualy from sources?
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
from source
[Galaxy Tab 3 10.1 Android Development] confyzone:
i enjoy the colors like that aha

great work man
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
Now to figure out how to get all buttons working... And colours correct....
[Galaxy Tab 3 10.1 Android Development] Doctor_XXX:
Looks great! Keep going! ;)
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
Backing up.....

Send via my BinDroided HTC ONE
[Galaxy Tab 3 10.1 Android Development] confyzone:
how'd the backup go?
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
Backup went fine...

Working on root

Have a permission issue... Can't upgrade su binaries

Send via my BinDroided HTC ONE
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
Guess who has ROOT
[Galaxy Tab 3 10.1 Android Development] confyzone:
All of us shortly?
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
Published in OP
[Galaxy Tab 3 10.1 Android Development] confyzone:
*BOWS*

we are not worthy

lol
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
CLICK "Tip Us" top right of the thread, and get it to the portal
[Galaxy Tab 3 10.1 Android Development] confyzone:
recovery says invalid

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> MD5 hash value is invalid

<OSM> recovery.tar.md5 is invalid.

<OSM> End...
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
try download again

I zipped the .md5 file now... hope downloads go better this way
[Galaxy Tab 3 10.1 Android Development] confyzone:
Worked Beautifully, and like I said, I love the colors :D

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

now for the custom CM or AOKP or PA and we're set :D
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
Bed time now for me....

Been long days gettin this done
[Galaxy Tab 3 10.1 Android Development] confyzone:
Beautiful
[Galaxy Tab 3 10.1 Android Development] Doctor_XXX:
CWM install via Odin seemed to go fine, but I can't get into the recovery itself. Thoughts?
[Galaxy Tab 3 10.1 Android Development] confyzone:
Power + vol up
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
Colour issue is fixed, will update later

Send via my BinDroided HTC ONE
[Galaxy Tab 3 10.1 Android Development] ShadowDice9100:
It's not that bad looking tho..kinda unique. O fyi can't access internal memory via recovery. It requires either an sd card or side load via adb
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
Ik know, still Working on it.

But we have it, and root ;)

Send via my BinDroided HTC ONE
[Galaxy Tab 3 10.1 Android Development] Doctor_XXX:
I go through Odin (like usual) and get this:

But then when trying to get into recovery, I get the stock image (I think), like this:

Almost like the Odin flash didn't take? :confused:
[Galaxy Tab 3 10.1 Android Development] confyzone:
That's weird I've never seen that. And your using the most recent upload?
[Galaxy Tab 3 10.1 Android Development] Doctor_XXX:
Yeah, I thought maybe I did something wrong last night, so I re-downloaded everything this morning and tried again, just to be sure. Do the Odin settings look OK? Anything else you can think of, as far as Odin or the Tab settings go? Could I have missed a step?
[Galaxy Tab 3 10.1 Android Development] Floflodu72:
I've the same problem ;)
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
Did you reboot, or go straight to recovery?

Preview 4 will be online in about 3/4 hours

Send via my BinDroided HTC ONE
[Galaxy Tab 3 10.1 Android Development] Doctor_XXX:
I rebooted... Not good that way? Should I go directly into recovery after the Odin install?
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
Should not matter, but give it a try

Send via my BinDroided HTC ONE
[Galaxy Tab 3 10.1 Android Development] ketut.kumajaya:
Don't check Odin's "Auto Reboot". Samsung normal boot init.rc will execute /etc/install-recovery.sh script to restore stock recovery.
[Galaxy Tab 3 10.1 Android Development] confyzone:
And your positive your not using the stock recovery file from the OP?
[Galaxy Tab 3 10.1 Android Development] Doctor_XXX:
I'm thinking you are right. If I recall, you needed to do a similar "deselection" on the SG2 & SG4.

Will re-test in about 10 mins ...
[Galaxy Tab 3 10.1 Android Development] confyzone:
I had auto reboot on no issues, but I also booted in to recovery immediately
[Galaxy Tab 3 10.1 Android Development] Doctor_XXX:
Cruddy picture, but that was it. All good here! :cool:
[Galaxy Tab 3 10.1 Android Development] Doctor_XXX:
Getting a "E:Can't mount /.sdcard/" error...so am unable to install the root.zip. Ideas?
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
While in recovery?

That's weird..... I never had that

Send via my BinDroided HTC ONE
[Galaxy Tab 3 10.1 Android Development] ShadowDice9100:
For The no sd.card mount you need an actual sd card or do like me and sideload via adb
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
and after reading, i found out USB Massstorage is NOT implemented in current CWM, no fault in the build
[Galaxy Tab 3 10.1 Android Development] Doctor_XXX:
I've got an actual/physical 64GB SD card in the external slot...that's where I've saved the root.zip file. I put it on the internal memory too, but can't get at that, either.

Are the instructions for adb install "easy"? :D Or, is there any way to "mount" my SD card properly for this recovery to read it?
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
When you pick: install from sdcard

You have no options?

I also work from sdcard

Send via my BinDroided HTC ONE
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
final version is available in op
[Galaxy Tab 3 10.1 Android Development] Doctor_XXX:
Correct.

When I select "- install zip from sdcard", then I select "- choose zip from sdcard", the bottom of the screen (almost immediately) shows "E:Can't mount /sdcard/", and I'm dropped back to the previous menu. I don't ever get to the point where I can actually go down the list of files on the sd card, pick one, install, etc. When I try to "choose", I immediately get the error and the screen pops back to the choose menu, if that makes sense.
[Galaxy Tab 3 10.1 Android Development] Angel_666:
Good! Can you please post the contents of "BoardConfig.mk"?
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
Try flash again

and the new one as well

and check your sdcard, and maybe format it, to make sure...safe content before you do ;)

source will be on github later on
[Galaxy Tab 3 10.1 Android Development] Doctor_XXX:
Re-flashed the NEW recovery. Looks great! But still no luck with the zip/root install.

How do you want me to (re)format the sdcard? Any way special...or just through the Storage menu on the Tab itself?

[Are there any settings on the Tab that might be stopping the mounting from working in CWM recovery? I can get to the card through the Tab and via the PC easily...just no luck via recovery. I don't have a clue about Android/UNIX, but am just thinking there MAY be a setting on the Tab that isn't allowing the card to mount like we're trying to do?]

Thanks for all the help!:good:
[Galaxy Tab 3 10.1 Android Development] BigManz:
Hello All,

confyzone has been a great help since my post count wasn't high enough to post here. Doctor_XXX I had the same issue as you! I have a feeling that the kernel for recovery image doesn't support the large filesystem or a 64GB card. I had a 2GB card kicking around that I didn't care about... reformatted it FAT (since the filesystem is small and so is the root.zip file). I tried again and it detected and loaded the root.zip :)

Give that a try!
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
I have a 32Gig SD, and that works.. donno about larger

But I put support for large files in the reovery.. again donno how large that can be.

Let me know how large your SD is confyzone
[Galaxy Tab 3 10.1 Android Development] BigManz:
Another thought is that it doesn't like having multiple dirs on the sdcard but that doesn't make much sense. (but another thought)

FS type? What did you format the card? ext3, fat32, fat16?

Thanks again DutchDanny!
[Galaxy Tab 3 10.1 Android Development] ShadowDice9100:
you going to have to do some reading and Google. its easy (in a manner of speaking). you just have to pick the right drivers from the device manger for the tab wile in recovery mode. learn a little about android adb cmd and using the command window to specify file location. and push the file directly
[Galaxy Tab 3 10.1 Android Development] Doctor_XXX:
Got it to work with a 32GB card. Not sure if the 64GB is too big, or ??? but the 32GB version worked like a charm, while the freshly re-formated 64GB did NOT. Not a huge deal, but maybe something that can be "fixed" in a future build?

Thanks for all the responses, all! :cool:
[Galaxy Tab 3 10.1 Android Development] nasaprinsloo:
Is there anyway to install from internal SD card? also doesn't show up as an option
[Galaxy Tab 3 10.1 Android Development] jeffw111:
Just FYI I was seeing the same issues with my cards as well. For me at least my MicroSD cards were all formatted to exFAT and once I reformatted one of the to FAT32 CWM was able to see and access the card.
[Galaxy Tab 3 10.1 Android Development] Doctor_XXX:
Yeah, in doing some research, there seems to have been a LOT of exFAT issues with CWM recoveries in the past. I had thought they were all worked out, but it looks like the version we have for our tablet still have them baked in (for 64GB cards, at least).

I'm going to do the FAT32 reformat tonight...I "need" the full 64GB in the tablet at most times, so dropping down to a 32GB or smaller just doesn't work, for me.

Thanks! :good:

---------- Post added at 12:52 PM ---------- Previous post was at 12:50 PM ----------

See post #61 earlier in the thread...
[Galaxy Tab 3 10.1 Android Development] Doctor_XXX:
Any chance of getting exFAT support on 64GB cards for this recovery? FAT32 is working, but the 4GB limit on file sizes makes for a tough time with video/movie watching.

Thanks for everything so far!
[Galaxy Tab 3 10.1 Android Development] DutchDanny:
I will look in to it later...

Send via my BinDroided HTC ONE
[Galaxy Tab 3 10.1 Android Development] xmaczi123:
Build fails because dalvik's atom support.

I'm trying to build 4.2.2 with the sources (GT-P5200_JB_Opensource_Update2.zip) found on opensource samsung, but it fail's because there is no support for x86-atom in 4.2.2's source tree. Basically there is no dalvik/vm/mterp/x86-atom directory. Interestingly it still exists in 4.1.2's source tree.

What do you guys think?