yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] Chainfire:
It is contained in PHONE part, so it doesn't make you safe.

Re: the RIFF box, do you need to make your own cables / connector ?

Also, it'll be a while before I can make binaries, if still needed by then. If I had a working JTAG unit on me right now, I probably would have already fixed both my Tab, and have devised a fix for the protected bootloader :/
[Galaxy Tab  Android Development] Monrad:
I have to make my own connector but that shouldn't be a problem. I guess the JTAG adapter will be available soon.
[Galaxy Tab  Android Development] Joao Oliveira:
@chainfire.

I've opened the tar flile I flashed and there is no sign of boot files inside?!

Why don't you write the app for checking if we have the protected bootloader and have us testing it?

Anyway as fast as xda-dev works we will have a fix in the next few days hehehe.
[Galaxy Tab  Android Development] rotohammer:
Could you share a diagram of the jtag pinout? I'm debating the purchase of a riffbox. If the jtag points are easy to get to I'd be more inclined to purchase it.
[Galaxy Tab  Android Development] Chainfire:
Then you're likely to be fine :)
[Galaxy Tab  Android Development] Monrad:
Ill post it tomorrow, I have the riff iface at the office.
[Galaxy Tab  Android Development] Squishie:
I followed ayman07's guide and used Roto-JMC for my final flash, I took a peek in pre-flash and post-flash tars and the only 'suspicious' item located within was a 7.8mb zimage in Roto-jmc.

So 1/3 gives me a decent chance. ^^

However something to note is my JMC doesn't have 'true' root, just SU access. adb root gives me an error regarding a production build. Rageinthecage works fine for temproot.
[Galaxy Tab  Android Development] rotohammer:
You're 100% safe, I reviewed ayman07's procedure and you flashed no bootloaders. I never noticed the adb root issue until you mentioned it (I dont use adb root normally).
[Galaxy Tab  Android Development] Squishie:
I probably wouldn't have noticed that either until I tried to replace a few files in /system/lib - Root Explorer gave me a weird disk full error. I looked into it some more and found out through AndroidCommander that I don't have actual root with it.

Even after manually re-installing Busybox/Su/Su.apk I still don't have full root.
[Galaxy Tab  Android Development] seven2099:
This happened to me at one point having flahsed rotojma. All it takes is a full reflash of jm6 and then jmc on top. Full restore and that issue will be fixed.
[Galaxy Tab  Android Development] Alcibiade:
Rotohammer: were your versions of JM6 and JMC safe from thi issue ?

They are the only ones I flashed from the JM family so I am crossing fingers...

Anyway I can be wrong but I guess Samsung will probably use the same trick for all their upcoming ROMs... (Reminds me about Softbank in Japan using a special bootloader for the Hermes that could not be downgraded and prevented us from unlocking the phone...)
[Galaxy Tab  Android Development] appelflap:
Thanks for the heads up!! Good luck getting your tab repaired.
[Galaxy Tab  Android Development] jstuart83:
so is it possible to get back to the stock firmware for example att's i have an att tab i flashed and now im starting to regret it
[Galaxy Tab  Android Development] rotohammer:
Yes, all my firmwares are safe, your Tab is safe :)
[Galaxy Tab  Android Development] rotohammer:
It depends on exactly which firmwares you flashed. It looks like flashing JMA, JMC or JMD from samfirmware.com is a one way ticket.

If you flashed Roto-JM6, Roto-JMA or Roto-JMC then you can go back to stock.
[Galaxy Tab  Android Development] Khoral:
Seems like you forgot to put the zImage file in the org directory in the zip from 1st post ^^

I'm trying to look at the bootloader's files atm, thx for telling where to look ;)

Edit : As it is my first time taking a deep look in bootloader, do you have any useful directions to give, known bytes or something so I can take marks ? Thanks :)

And fyi, I'm using UltraCompare to try to focus on matching differencies between files ^^ (if you have any better method, I'm always listening :D)

Seeing the message in PBL, you seem to be right :) Didn't already checked the SBL, but I trust you :D
[Galaxy Tab  Android Development] kromosto:
Actually i read his message wrong then i said you are ok. First he seems to me that he did what i did exactly but then i realized that he doesnt use roto-jmc.

As for the topic i dont think this signature part will end. i think future roms from samsung will released compatible with new bootloader. also i think there must be a low level bootloader method for flashing old bootloaders.
[Galaxy Tab  Android Development] Khoral:
Right. And all the thing is to understand the signing part, as it will allow us to :

- create signed ROMs, or

- delete the signed verification from bootloader

As soon as we get there, this is a win :D
[Galaxy Tab  Android Development] goattee:
STUPID ME: Patched bootloader against warning. What now?

I never realized what stupidity I am capable of! Can you believe I chose to completely flake out and disregard this warning? If you can see the humor of my stupid mistake and can also tell me how to fix the situation, I will promise to be much more careful in the future!

THE SITUATION

- I have a rooted international GT-P1000 (GSM) with stock Gingerbread ROM

[currently reads: GINGERBREAD.DX..JPI Kernel 2.6.35.7 root@DELL125#2 Baseband version P1000DKJPE].

- I ran this bootloader patch in spite of an explicit warning that doing so under those conditions would break things. (Hanging my head in shame.)

- The tablet starts up and runs normally right now. And is still rooted.

- BUT while booting, the screen shows a vertical scramble of colors before stabilizing and displaying the launcher's home screen.

- An attempt to put the tablet into stock recovery mode shows that same vertical color bar covering the recovery menu choices.

I would like to install CM9 for p1 soon.

QUESTIONS

- Is there a simple way to reverse the changes made my this bootloader patch?

(And would that be the only thing I need to do? How?)

- Should I/can I load a custom recover app? (And if so, at what point?)

- What should I do to prevent problems in flashing the new ROM?

- Can I use ODIN to load and flash CM9 even though I cannot read the stock recovery?

- Do I have to load a different bootloader patch? Kernel?

(Please recommend what I should download or threads I should read. I promise to have a better attention span before acting!)

In advance thanks for putting up with foolish mistakes like mine.
[Galaxy Tab  Android Development] priyana:
Try Overcome method.

The GB-stock-safe-v5 package contains GB boot loader, so you should be back to good one.

Then flash overcome kernel 4.0 tar and you should have CWM recovery,

don't need to flash Overcome 4.1.0 ROM, just make use of its recovery and flash cm9.

(There is no Odin CM9 package)

http://www.teamovercome.net

Read the guide,

Missing pictures can be seen here.

https://docs.google.com/file/d/0B7k...EyNS00Yzg5LWE0MTktYmYyMjA1MThmYzQz/edit?pli=1

or

http://xdaforums.com/showthread.php?p=20974872

Follow the picture step by step.

missing files at

http://tabfirmware.com/2012/01/romk...e-7-series-v4-1-0-♫-overcome-kernel-v4-0-0-♫/

and missing kernel here

http://xdaforums.com/showpost.php?p=27801159&postcount=8

Basically to restock:

Download GB-stock-safe-v5.zip, unzip it and and flash with ODIN according to the guide.

Stop there and you will have Gingerbread JQ1

You can continue with the rest, and you will get Overcome 4.1 and you won't regret.

From there you can then try AOKP or CM9, all requires you to have Overcome Kernel with its CWM recovery to flash.

But since you want ICS, continue reading the guide.

- download ICS (CM9 or AOKP) and gapps-ics and put in external sd card.

- boot to download mode

- you need to use Odin to flash Overcome kerner tar

- once flashed the tab reboots.

- ignore the robotic voice, just force the tab to off

- boot to CWM recover (press vol-up and power )

- flash ICS (CM9 or AOKP)

- after flashing the system will convert your tab to MTD partition, but it will probably bring you to recovery or stuck at boot.

- force reboot to recovery again

- flash ICS again

- immediate after complete, flash gapps

- reboot
[Galaxy Tab  Android Development] goattee:
Thank you for taking so much time to walk me through the steps. You typify why I chose Android in the first place-- and why I have treasured XDA-Developers since the days of my Pocket PC phones!

I will make sure to save this project for a day when I've had a good night's sleep. In the meantime you've given me everything I need to study.
[Galaxy Tab  Android Development] goattee:
Among the links for the missing files: the modem file has a broken link. But 001001-GB-Stock-Safe-v5.7z contains the modem files. Are those OK for use as I flash new ROMs?

I have already installed the GB safe ROM with success. I'll go further over the weekend.

Thanks again!
[Galaxy Tab  Android Development] goattee:
Installing Overcome 4.1 is easy and it's a big improvement over stock Gingerbread

I now have Overcome 4.1. The responsiveness seems excellent. I wish I had done this many months ago.

I can see why you raved about this ROM. I would keep it BUT I have a certain magazine app that insists I have both the resolution of the Galaxy Tab and Android >= 3.x. I have tried every possible way of working around this limitation without success. Hence the need for ICS.

I performed a nandroid backup just in case. And I will now try using the standard image of CM9 for the p1.

Message to other GT-P1000 owners who are ultracautious:

Overcome 4.1 is excellent and relatively easy to install if you follow the guide step-by-step. It's clean and it improves perceived performance. And of course it gives you a rooted Android with lots of wonderful benefits (like adding the Samba Filesharing app).
[Galaxy Tab  Android Development] priyana:
Great that you sorted it out.

I don't particularly like Overcome ROM. It drains battle too much for me. I actually switched to Acudroid with redpill kernel.

But overcome method is 100% solid and we owe them much for it.

Best rom for me now is AOKP build 40.
[Galaxy Tab  Android Development] arjaylight:
washout bootloader

After patching my GT-P1000, bootloader mode seems to be washed-out or unreadable to perform any tasks.

Could someone help me fix this problem?

EDIT: i have the same problem with post 581 (previous post)
[Galaxy Tab  Android Development] priyana:
Why do you patch bootloader anyway.

Just move away from Froyo and you will be fine.

The guy in #581 patch a GB bootloader. Ignoring the warning.

Did you too?

The solution for you is exactly the same as my reply for #581

Fortunately, there is a new Overcome links that works

[ROM][2.3.6] Overcome Rom 4.1.0 new links

http://xdaforums.com/showthread.php?t=1881981

Get the guide, get GB-stock-safe-v5, jump to page 7 and flash.
[Galaxy Tab  Android Development] priyana:
Obviously..

it is called GB stock safe v5 for a reason.

It is STOCK? and it is GB, got it?

So, stock recovery is called 3e, not CWM.

You only get CWM after you flash Overcome Kernel 4.0 tar, don't jump the gun.

Now, bootloader?

Do you understand, it is GB, and red big warning said don't patch a GB boot loader.

What are you thinking?

All GB bootloader are signed, true, but they are not locked.

So there is NO NEED to patch the bootloader, and it is explicitly stated DON'T PATCH a GB bootloader.

Now what should you do?

( keep repeating myself)

restock with odin again to GB-stock-safe

then flash Overcome kernel tar

This time, READ the ENTIRE guide 10 times, before continuing.

You have to be able to follow the steps to the letter.

You obviously skipped step 8 but quoting step 9 as wrong
[Galaxy Tab  Android Development] Flynn:
But step 8 only tells me to copy the Overcome...zip into the root directory (which I did).

Nowhere is the Overcome_kernel...tar mentioned with even a single word.

And for Android ROM flashing noobs like still me ;) this is a big omission.

That's what threw me off and I assumed that the "safe" meant that someone already integrated the comfy CWM recovery into the otherwise stock rom.

Did this, did that, also chose JPZ this time, now I'm at

Firmware: 2.3.3

Basisband: P1000XXJPZ

Kernel: 2.6.35.7, Overcome-v4.0.0 #40

Build: GINGERBREAD.XXJQ1

Overcome CWM Recovery v5.1.2.6

SIM still works, distortion is gone, CWM is accessible. Awesome!

I finished following the guide (to the letter ;) ) installing the Overcome_7_Series_v4.1.0_Wipe.zip, which brought me to

Firmware: 2.3.6

Basisband: P1000XXJPZ

Kernel: 2.6.35.7, Overcome-v4.0.0 #40

Build: Overcome 7 Series v4.1.0

Overcome CWM Recovery v5.1.2.6

The guide still doesn't mention the files "removed_apps", "Wifi_Fix", "Stock_Theme_Patch" and "RTL_Patch arabic", if they are necessary, their possible purposes and when and how to install them.

For trying CM9, I suspect the preferable version will be the latest nightly get.cm/get/jenkins/8181/cm-9-20120916-NIGHTLY-p1.zip .

Or are there possible reasons to stay with the stable get.cm/get/jenkins/7087/cm-9.1.0-p1.zip ?

Also, are the gapps_jb compatible with CM9/ICS or do I really need to use the older gapps_ics? wiki.cyanogenmod.com/wiki/Latest_Version#Google_Apps seems to suggest that it doesn't matter since CM7.

Oh, and one last thing: Can I go back to Overcome 7 S.4.1 if CM9 doesn't strike my father's fancy?
[Galaxy Tab  Android Development] priyana:
the guide I am staring at has the kernel tar odin flashing instruction.

[ROM][2.3.6] Overcome Rom 4.1.0 new links

http://xdaforums.com/showthread.php?t=1881981

Anyway

Quite inappropriate to discuss this here, so hopefully this post ends the conversation.

"removed_apps" obviously samsung apps that was removed in overcome rom such as the book reader and such and such, someone asked before, I listed it before, just search in overcome thread.

"Wifi_Fix" only needed by middle eastern tab user because of some wifi country code. Also to enable channel 13 and such, if not visible.

"Stock_Theme_Patch" - makes it to look stock

and "RTL_Patch arabic" - right to left arabic patch

all are installed via CWM from now on if it is a zip file with updater script inside.

CM9 stable or nightly, up to you to choose. No guidance there, more of preference.

gapps you do need to choose if it is GB, ICS, or JB because they have different framework, but you don't need latest date ones because it will get updated by play store anyway.
[Galaxy Tab  Android Development] Flynn:
My downloaded guide "The Overcome ROM A (Hopefully!) Comprehensive Guide To Installing & Other Tips! v0.01.pdf" only mentions the gb_stock_safe.tar, I can't find the mention of the file Overcome_kernel..tar and any instruction to install it.

But you are right, let's end OT.

Thank you very much for your helpful answers. I really appreciate them and hope the conversation will also help other lost souls.

Now off to find a place to ask about the downgrading before I take the plunge into CM.
[Galaxy Tab  Android Development] junnojules:
after i install and patch my tab. my pc wont detect my tab anymore? please help!
[Galaxy Tab  Android Development] brenzef:
Hi all,

Honestly, I tried to read the whole thread (and understand it), but unfortunately lot's of it is jimbobimbo for me.

To make sure I do the right thing and not leave me with a bricked tab the following:

My model is a GT-P1000

Firmware version 2.3.6

Baseband-version: P1000XXJPX

Kernel version: 2.3.6.35.7 root@DELL140#2

Build number: GINGERBREAD.XWJQ8

SGT Bootloader Patch says:

Device (reported by firmware) GT-P1000 European/International/Unbranded Galaxy Tab

Bootloaders - SIGNED !

Signed: PBL, SBL, Kernel

Not signed: SBL_Backup

Assessment: Can only flash SIGNED firmwares

What I want to achieve is loading a new ROM (Cyanogenmod 10) and get rid of the Samsung ROM.

Nothing needs to be saved (backupped).

To my understanding Chainfire/Rotohammer say to not patch the tab bootloader when it is running Gingerbread.

Do I understand correctly that installing another bootloader is therefore not possible and it's not possible to install CWM (and CM10)?

What is it that I must do to have cm10 installed?
[Galaxy Tab  Android Development] gradd:
is it safe to patch this on XXJM8? i'm running froyo.

ok i installed this and this what i get:

Status information

Device (reported by firmware)

GT-P1000

European/International/Unbranded Galaxy Tab

Bootloaders - SIGNED !

Signed: PBL, SBL, Kernel

Not signed: SBL_Backup

Assessment: Can only flash SIGNED firmwares

Patch bootloaders

Dangerous! Flashes unprotected bootloaders
[Galaxy Tab  Android Development] priyana:
Yes, if it is froyo, patch away.

If it is GB, DON'T.

Edit: disclaimer, any bootloader patching is dangerous.

You can brick your device doing it.

Do it at your own risk.
[Galaxy Tab  Android Development] LTE 4G !:
At&t Samsung Galaxy Tab 8.9 4G LTE SGH-I957

Hi everyone,

I was wondering if I can get some help on getting my tab back on a road. Make long story short, here it goes.

OK. I was playing wit my tab last night and unfortunately it got stuck , nothing works , black screen. This happened after I tried to flash my tab to make calls with (Samsung TAB Euro Flash Package) From : http://xdaforums.com/showthread.php?t=847273

At the time this happened my tab was rooted and I had a TWRP 2.3.3.1 and Goo Manager installed on ICS 4.0.4. I also saved all the backup files on my PC.

I was following the steps on a first page, after first flash something went wrong and now Odin doesn't recognize the tab as before. And it's being recognized by computer as a Qualcomm HS-USB QDLoader 9008 (COM4) . Now i'm lost and don't know what to do. Please lead me in a right direction. Thank you. ;)
[Galaxy Tab  Android Development] priyana:
LTE 4G! you tripple posted.

What for?

I already told you this is not for your tab.

This forum is the Galaxy Tab 7" original forum.

And I mean the ENTIRE forum and its subforum.
[Galaxy Tab  Android Development] LTE 4G !:
I Am sorry about that is just i am frustrated trying to find something about that issue

and not having much luck Sorry ! :rolleyes:
[Galaxy Tab  Android Development] priyana:
There

http://xdaforums.com/forumdisplay.php?f=1438

Go to the Galaxy Tab 8.9 forum and ask away. Have you been there at all?
[Galaxy Tab  Android Development] LTE 4G !:
No I haven't looked in that section, all do that now

Thank you for the lead I appreciate your help !
[Galaxy Tab  Android Development] P1ro:
well i have same problem as this guy, weird colours at screen, i only getting old bootloaders to get working, CF-Root boot but thats all, cant do much with it.

My tabler is a P1000n (p1n) overcome team dont have kernels for p1n tablets, if anyone know what i can download or try please.

my p1n tablet had a UBJM6 firmware or it should be that one.
[Galaxy Tab  Android Development] tphone:
I also made the mistake that #581 and #603 made. Now I think that I have permanently crippled my TMobile Galaxy Tab since the bootloader patch may have damaged the core part of the system. The device show garbled boot screen but eventually does boot back into Overcome v 2.0.0. However, the USB can not be detected by the PC. I have to use the phone keypad trick "*#7284#" to set the USB to PDA for the device to be recognized by the PC. I've tried to use Odin to reflash but when I put the device in download mode, Odin can't detect the device. If I boot into Overcome and make USB available with by dialing as above, Odin can detect the device but can not flash anything because it hangs up and times out in the communication. I've tried using ROM Manager to flash the device just boot into garbled screen and stay does nothing. I've tried to perform factory reset, but that is also does not do anything. I think that my device is permanently crippled beyond repair. The hardware is working find and I hate to recycle it. If anyone has an idea what I should try, please let me know.

Thank you.
[Galaxy Tab  Android Development] Mjoelnir77:
Did you try heimdall?
[Galaxy Tab  Android Development] tphone:
Yes, I did. When the device in put in Download Mode, the PC doesn't recognize it as Samsung Composite device, it says "Unknown Device #1". I think that the device is permanently damaged by the patch.
[Galaxy Tab  Android Development] Ichijoe:
Ok I don't mean to blow new life into a what seems to be a dead thread... But!

I was recently given a neused Samsung Galaxy Tab P1000 (Voda Branded), GSM for my Birthday.

Since then I've pretty much found that Battery life gets bettter the closer to v2 I get, and progressively worsen the closer to v4 I get.

Now I think I might have forked up by installing these JK* JM* etc Froyo ROMs. (Wasn't easy to find them either). In any case to use that *.apk from the first page I had to downgrade back to JK2, which seemed to be ok zImage was only 4.33Mb.

Long story short I reinstalled that ROM again, then rechecked the Bootloader(s) again, and it said that I was clean.

I then installed the Overcome 4.1.0 ROM again. Having checked the state of my Bootloader(s) again under Overcome.

It states that my Bootloaders are again locked -- e.g. SIGNED.

My question does signed = locked?

Should I aspire myself towards having unlocked Bootloader(s)?

Or does it even matter after Froyo?
[Galaxy Tab  Android Development] priyana:
All GB bootloader for P1000 are signed but none are locked.

Only in Froyo it matters.

I hope you didn't try to patch GB bootloader. It will be broken if you did. You will see those rainbow colours like some of those who did.
[Galaxy Tab  Android Development] Ichijoe:
Yeah I did do just, that, and yep I was blessed by the "Rainbow" Effect durring the boot sequence. Once it got into the OS it was normal again.

In any case a fresh install via Oden was enough to fix it.

Interestingly though I noticed that Froyo seems to give the best Battery life where JB/ICS/GB report ~25% Battery Froyo reports back ~50%, or nearly double the current amount of life. Right now my Tab seems to get about 6 1/2h with mid to lowesh-high (i.e. Google Music), usage. I have since given up any hope of playing any Gamez on this. Thanks to only 512Mb RAM. Even on GB this thing lags badly.
[Galaxy Tab  Android Development] barberboy420:
I have the sprint t217 model and I rooted a few days ago on the kingoapp website. I'm trying to flash a rom but I'm new to the galaxy tab. Any tips suggestions?
[Galaxy Tab  Android Development] priyana:
That is a Tab 3.0

This is the original tab 7" forum.
[Galaxy Tab  Android Development] barberboy420:
um sorry man
[Galaxy Tab  Android Development] sedde:
So even if samsung is so dumb enough to "lock" their bootloaders even though they sold us the device with unlocked bootloaders, what keeps us from wiping the device off ( so it clears root apps and stuff ), and then flashing a "new" bootloader and before it finishes, to unplug the usb to it completely bricks the device and sprint to the nearest samsung repair center and pretend we never did something to the device ?
[Galaxy Tab  Android Development] blacklevel:
The "adb root" issue is due to the fact that the adb server process (/sbin/adbd) on the tab is running as user "shell" and not user "root".

For the same reason "adb remount" does not work either.

The "disk full" probably just means that the system partition is mounted read-only. To verify issue these shell commands first:

$ su

# mount -o remount,rw -t rfs /dev/block/stl9 /system

Then you should be able to replace files in /system/lib just fine.
[Galaxy Tab  Android Development] paulshields:
I like your positive attitude in this otherwise depressing thread :D.

I can see Samsung going down the signed bootloader route for official rom's in the future, so working on a way of bypassing this now will be helpful for those already with signed bootloaders and those looking at trying out future Samsung rom's. Let's just hope it's not a big job to get there...