yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] Magaboo:
Thanks Roto

Rotohammer, I always suspected that you're a bit of a genius, but this confirms my suspicion. I'm amazed at what people like you are willing and able to do for our cause.

Many thanks Roto.
[Galaxy Tab  Android Development] Landroid:
rotohammer, you're the man! did u already figure out the steps u are going to do, or are they still the same u posted here some time ago?
[Galaxy Tab  Android Development] rotohammer:
I flashed a protected bootloader, then tried flashing a stock at&t kernel as well as CF-Root, both failed to flash. Then I flashed the recovery bootloaders using the jtag box, and I now Its unprotected.

Next step: force a new sbl via redbend!
[Galaxy Tab  Android Development] Landroid:
Ok, this means there IS a way to downgrade, thats good to know :) good luck!

Btw. What is redbend? I read it several times here in the forums
[Galaxy Tab  Android Development] rotohammer:
Its an app that flashes partitions of data. Very handy, very destructive.

I've down graded the bootloaders for a 3rd time today using 3 simple commands, but bricked it 5 times trying as well. Its starting to appear like theres some timing involved, like I need to do certain steps within a certain window of time.
[Galaxy Tab  Android Development] msewidan:
You are amazing. see if you can figure out how to rebuild the NV_data file from scratch to fix tue IMEI.
[Galaxy Tab  Android Development] dawitt1995:
ok, sounds great! i hope u figure out the right timings, or even a easier method to reflash them! i would even be happy with the dangerous method ;)!

if u manage to do it, u get the bounty, its 95$ now :O

good luck
[Galaxy Tab  Android Development] Chainfire:
KA2 also seems to have the protected bootloaders. I've not properly checked or uploaded the ROM yet (no time right now), just a heads up.
[Galaxy Tab  Android Development] rotohammer:
Successful removal of protected boot loaders

Complete success, I got it. But the bounty is too low, so Ill wait a few more months before I release it.
[Galaxy Tab  Android Development] crisvillani:
Seriously?! :O
[Galaxy Tab  Android Development] mniewiera:
he was just joking! (thankfully!)

he posted a reply here
[Galaxy Tab  Android Development] Chainfire:
Ok, I have spoken to Rotohammer, and he has sent me the files for the fix.

It is a sensitive fix, and thus we are not just releasing it. We will be making an APK that does the unlocking for you, so there's no chance you mess up the commands and brick your device. That is, at least, if we don't mess up the APK ;)

Expect the APK to go into (closed!) testing early next week, with hopefully a public release early the week after that.
[Galaxy Tab  Android Development] humberos:
Sounds great!

You are the man!
[Galaxy Tab  Android Development] humberos:
Yes!!

Security does not hurt!

Roto, congratulations for you,... to the dedication and solidarity.
[Galaxy Tab  Android Development] crisvillani:
Awseome news!
[Galaxy Tab  Android Development] Monrad:
Im donating 20 usd. I can fix it myself with the jtag but I always appreciate the hard work and knowledge.
[Galaxy Tab  Android Development] rmanaudio:
Can you please go here to donate: http://xdaforums.com/showthread.php?t=906464 and post your donation amount. Thanks.
[Galaxy Tab  Android Development] RWOLUPO:
if you need a tester cf, just ask ... i'll risk that test with my signed euro-tab :)

great work so far rotohammer!
[Galaxy Tab  Android Development] faust86:
I have Samsung service behind the corner so i think i can help testing too :rolleyes:
[Galaxy Tab  Android Development] grellanl:
Ahhhhh.... this explains things. I was on JM6 (and very happy with it) and decided to try another, newer build before Christmas... bricked it. Just got my replacement today!

It's a shame, the JM builds really felt much more responsive. Maybe we'll see a super-responsive ext4-based 2.3 build come out in the coming months!
[Galaxy Tab  Android Development] Chainfire:
Whoa, lots of new JM* ROMs released by Samsung ... wonder if they all have the bootloaders. Can't check it out 'til Monday ...
[Galaxy Tab  Android Development] rotohammer:
Even though its fun to test apps, this is one that carries risk even when its perfect, in that its overwriting your boot loaders. You would be a good candidate for the first round of public testing.

Everyone should be prepared to have their tab in perfect working order in advance. I highly suggest everyone backup their data, then flash Roto-JME-Full-v4 so that your Tab is in a known tested state, which is what my test Tab will be running during testing.

In hindsight, I could have just packaged the fix into a JME-v5 but unfortunately this weekend I have to be on vacation :)
[Galaxy Tab  Android Development] Dark-Master:
This is such a great news. Hope it works flawlessly on mine.

Thanks for your hard works, guys.

Can't wait for the fix to be released. And I really love your Roto JME, Mr.Rotohammer.

Imma buy U A Drank! (borrowed from T-Pain's song, hehe)
[Galaxy Tab  Android Development] u3819013:
@chainfire

please add KM series at the top post.
[Galaxy Tab  Android Development] faust86:
So can I install Roto-JME-Full-v4 on existing JM6 with blocked bootloader?
[Galaxy Tab  Android Development] abuser0815:
yes you can, because roto-firmwares never touched the bootloaders so far.

i´m also on roto-jme-v4 full. i also can easy swap my tab if it is bricked (guaranteed by contract a replacement in 48 hours). i would offer my euro tab as well for first testings, as i know the very high risks. but if fails i have an acceptable solution for me ;)

btw, roto, you call it vacation doing bootloader-hacking? have a nice remaining stay in hungary!
[Galaxy Tab  Android Development] themokim:
just heard in the news about a panic in a club in budapest - people got hurt. although this city has an brilliant night life (probably one of the best in europe) i hope you didnt go into this club yesterday. enjoy your stay and thanks for all your effort.
[Galaxy Tab  Android Development] wgery:
Panic caused by a murder by knife (gipsies..)
[Galaxy Tab  Android Development] rotohammer:
I'm in a small town called Cegled with family. Back to Budapest tomorrow night.
[Galaxy Tab  Android Development] msgfromside3:
Yes. I've done it myself. It seems signatures are either the same or compatible.

Galaxy Tab Roto-JME
[Galaxy Tab  Android Development] t0dbld:
@roto so i see riff is working so thats good news . . . I will now order, hay ive been searching everywhere cant find do you know the name of the board on the tab ? Code name that is like passion and crespo etc ?
[Galaxy Tab  Android Development] Landroid:
The code name is gt-p1000 on european tabs, i dont know what it is on american ones but u can see it in build.prop!
[Galaxy Tab  Android Development] dhaddow:
In preparation for the upcoming fix, I downloaded P1000XWJJ7 (which I think is the latest version flashable with Kies) from samfirmware.

I noticed however that this software contains both boot.bin and sbl.bin, the zimage is however less than 5500.

Can anyone tell me if this version has infact got the signed bootloader? Don't really want to go thru the same carry on again. :mad:

There is a newer version on samfirmware P1000XXJK5 which does not have boot and sbl which I will prob use if there are signed bootloaders on JJ7

Ta

Duncan
[Galaxy Tab  Android Development] abuser0815:
your version should be fine because zimage has less than 7,5mb. if you flash a kernel with moreless 7,5mb, its a first sign of signed bootloaders. sure you are only with the tool from chainfire, because you can flash also signed zimages to unsigned bootloaders like roto´s firmwares does.

anyway, zimage of 5,5mb sure no signed bootloaders....
[Galaxy Tab  Android Development] t0dbld:
lol well i dont think that is it as other samsung devices have a like p1000 and board named crespo etc.... but never the less i have been using that in mean time anyhow thanks for the response
[Galaxy Tab  Android Development] rotohammer:
It would be best to look at the kernel source. As far as the physical board, mine has several names as seen in the photos at http://xdaforums.com/showpost.php?p=10572161&postcount=24
[Galaxy Tab  Android Development] rmanaudio:
Here is the correct RIFF box:

http://www.gsmserver.com/shop/gsm/riff_box_jtag.php
[Galaxy Tab  Android Development] lux209:
Hi all,

Roto, is it possible to have some details on your method to flash unsigned bootloader ?

I'm just curious, and want to know how you manage to bypass the security :-)

Thanks again for your work !
[Galaxy Tab  Android Development] t0dbld:
I agree as i have been working with the kernel quite a bit how ever what they have released is a joke :mad: i did look at your pictures as other pictures in the tear down @ifixit but nothing im finding is definitive, also i am having problems getting fastboot to correctly work with tab so needless to say doing a aosp builds for tab is becoming much harder than i had wished oh well, btw nice work on that riff box mod of tab i can only hope i can do such a good job !!
[Galaxy Tab  Android Development] Landroid:
you want to get fastboot running on galaxy tab?? i dont think this will work...
[Galaxy Tab  Android Development] crisvillani:
Soo hows.the testing going?
[Galaxy Tab  Android Development] Chainfire:
Not quite there yet :)
[Galaxy Tab  Android Development] Chainfire:
First test version has just been sent to Rotohammer. There'll be another test version after that, and if that works, we'll do some private testing with a select few daring users to make sure it doesn't just work on Rotohammer's Tab. After that, public release in this thread.
[Galaxy Tab  Android Development] crisvillani:
Sounds great dude , thanks for all the hard work!!
[Galaxy Tab  Android Development] crazylemon:
roto, you should change your nick to rotoGOD! just great.

eat this samsung!!!!!!! :D
[Galaxy Tab  Android Development] rotohammer:
Due to a hyper aggressive set of email filter rules, I didn't get chainfires email yet. As soon as I get it i will test. Sorry for the delay :)
[Galaxy Tab  Android Development] robertsydbrink:
I feel the love.

I'm so happy with my tab (altho with a locked bootloader atm) and that there's dedicated people to make it even better (:
[Galaxy Tab  Android Development] Chainfire:
That is unfortunate. Cant resend until tomorrow.
[Galaxy Tab  Android Development] Dark-Master:
I see the light coming. :)

Thanks to all dev for all this.
[Galaxy Tab  Android Development] Chainfire:
We have progress! Update soon :)
[Galaxy Tab  Android Development] Landroid:
Sounds great! :)
[Galaxy Tab  Android Development] crisvillani:
Exciting : )
[Galaxy Tab  Android Development] Chainfire:
Status update in first post.
[Galaxy Tab  Android Development] TheGrammarFreak:
Geniuses

Sent from my GT-P1000
[Galaxy Tab  Android Development] kay_kiat88:
I've flashed from jj1 -> jm4 -> rotojmev4 -> rotokm2v1 -> fastandtabiousrom

I'm sure all these roms don't have protected bootloaders and i've always checked before flashing. but when i use chainfire's sgtbootloadercheck, it says that everything is signed. any idea why?
[Galaxy Tab  Android Development] farahbolsey:
Hi kay,

JM4 has the protected bootloaders.

Did you first unrar the P1000DXJM4_P1000DXJM2_P1000OLBJM1_HOME.tar, then flash with heimdall everthing except the boot.bin and sbl.bin.

If you didn't, then your protected bootloaders come from JM4.
[Galaxy Tab  Android Development] kay_kiat88:
hi there, hmm if it has protected bootloaders, i wouldn't be able to flash rotojme4 right?
[Galaxy Tab  Android Development] farahbolsey:
Wrong. with protected bootloaders you can flash roto's files and any other files, even downgrade to JK5 for instance (which is tricky but doable). But so you know, when you manage to downgrade to JK5, every files contained in the firmware will be downgraded except the boot.bin and sbl.bin which will remain protected.

Anyway, that is true at least until a few days, as the fix is coming thanks to roto and chainfire's hardwork.
[Galaxy Tab  Android Development] dhaddow:
You would be able to flash roto's roms as the kernels he uses are signed. He just removes the bootloaders.

Oops typed too slow
[Galaxy Tab  Android Development] kay_kiat88:
ohhh i see. thanks man I get it now.. I'm new to android and the tab's my first adroid device but I'm learning lotsa stuffs here on xda forums!
[Galaxy Tab  Android Development] Chainfire:
Getting lots of testing offers, but no P1000L/N users yet ...
[Galaxy Tab  Android Development] rainbow ng:
ha..ha, gsmserver has branch in Hong Kong

To get a riff box is a good idea to continue FLASH:cool::cool:
[Galaxy Tab  Android Development] jgaviota:
Hi Chainfire,

It seems that I'm the only user here with a I9000N

and humberos the only one with an I9000L

The thing is, the Galaxy Tab I have access to is really my work's...

So I cannot risk bricking it :(

I already posted my original boot.bin and sbl.bin on Roto's request on another thread.

Is the risk of bricking the Tab reaaally great? I have not flashed a locked bootloader.

humberos does have a locked bootloader on his. He is currently using a signed I9000N rom from samfirmares.

As he did flash an european rom with locked bootloader I'd say that your fix should work on his Tab.

I would love to contribute to the community, I have received lots from XDA and from you on the Raphael

On a side note, Latinamerican Tabs use different hardware (at least the digitizer) because when I flashed Roto's JME v4 I lost touchscreen capability, so did humberos.

Can you compare our bootloader with the standard JJ4? And is the digitizer driver on the kernel or on the rom?

I have a full Roto backup of my original rom .

Thanks and sorry if my thought sound like ramblings :D
[Galaxy Tab  Android Development] ivannw:
Hi all, I have P1000L too, from Brazil with digital TV and I can test the kernel.

I'm currently using P1000LVJJM9 fw.

waiting for instructions.

cya.

Ivan
[Galaxy Tab  Android Development] kay_kiat88:
Any chance yous guys want to test on a Singapore tab?
[Galaxy Tab  Android Development] Karl:
Anything being done for the sprint tab?
[Galaxy Tab  Android Development] rmanaudio:
I got a question for the DEV's:

So now that we can all have unsigned bootloaders....what happens when Gingerbread or Honeycomb comes to the TAB via Samsung or CM?

Will this bootloader from JJ4 or any other unsigned bootloader be up-to-date enough to book kernals from GB or HC???

Or do we have to load signed bootloaders eventually in the future?
[Galaxy Tab  Android Development] Chainfire:
Being a dev doesn't grant us magic power to see the future, you know :)

Who knows? Maybe, maybe not. If we do need to upgrade bootloaders for GB/HC there's a fair chance of it being an artificial limitation imposed by the firmware from Samsung, and that for example a CM version would run without it. Compare it the BIOS of your PC. Usually you never have to change it, but sometimes you do have to flash it when changing OS. It's not a very good analogy, but it works somewhat.

There's also the possibility we will be able to unsign the bootloaders, disable the check, etc.

We'll deal with it when we get there!
[Galaxy Tab  Android Development] sanderh:
Where can I get the .apk with the fix?
[Galaxy Tab  Android Development] Chainfire:
Well, so far in private testing 0 bricks and 100% success.

I'm still waiting on two more test results (one AT&T and one P1000L) if those are positive I'll release the APK here. Hopefully this'll be tomorrow!

It's not publicly available yet.
[Galaxy Tab  Android Development] abuser0815:
rotohammer and chainfire,

if the tests are positive and you release the fix, could you please give a short explanation what and how the apk does the job? Were was the dificulty to get this fixed?

Many thanx and best regards!
[Galaxy Tab  Android Development] Chainfire:
The APK just writes the correct bootloaders back to the flash directly, circumventing the protection present in "download mode". This by itself is not a major breakthrough, we long suspected this could be done. The problem was this has to be done exactly the right way, and figuring out what the right way was, that was the difficulty. Why was that difficult? Because if you don't do it exactly right you end up with a full brick. Replacing bootloaders is pretty much the only way to really brick a Tab :)

That's also why we are being so careful with the release. We don't want to see bricks, though it's not 100% avoidable. I dare say sooner or later there will be bricks.
[Galaxy Tab  Android Development] abuser0815:
Hi chainfire,

i know it was to write back the unprotected bootloader, but how?

What is the correct way to do it?

I assume you and rotohammer don't want to tell because of fearing more full bricks of users try it that way and i understand this. But i'm curious about it and i would like to know what was the right way to flashback. I tried it and luckily didn't end up like you with a brick and i listened to rotos and your warnings. But now as i know that roto figured it our i wolud like if you share your knowledge :-)
[Galaxy Tab  Android Development] Chainfire:
So you understand why we aren't telling, but you want us to tell anyways ...

We might release the info in the future - after the APK is released and most users have already fixed - but there's no way we're telling right now.
[Galaxy Tab  Android Development] abuser0815:
Ok, if you tell later its ok.

Just one thing, to not tell your doughter about how human relationships work doesn't avoid that she gets pregnant...

Big thanks anyway! Your effort for the community is great.
[Galaxy Tab  Android Development] rotohammer:
I would like to follow up on the reason for withholding the knowledge.

Anyone who knows me knows I'm a cocky SOB, always managing to catch some limelight.

There would be nothing more gratifying for me than to present the bootloader fix, singularly, taking all the glory. But, for the benefit of everyone with signed bootloaders, I could predict the fail fest that would ensue if i released the fix in the raw command line form. Hence I handed it to Chainfire who has the programing experience and bootloader knowledge to wrap the fix into the most fool proof app possible. The fix is simple. Of course everything is simple when you know the solution.

I'll be more than happy to release the exact method and theory behind the fix after everyone is in the clear. I plan on using the technique to allow self flashing new Roto-Firmware right from the Tabs sdcard in the near future.

What I would like to see in the meantime is a coordinated campaign to discourage folks from loading firmware directly from samfirmware.com. If you know what you're doing, then fine, do it. But don't go shooting off about how easy it is and how everyone should flash everything just because you can do it. It takes a lot of effort to give folks the satisfaction of flashing firmware without undue consequences. Sure, I shouldn't be the single source for flashable firmware, but we need to act responsibly. In no time there will be a dozen firmwares to choose from and I'll have moved on to using someone else's firmware.

Chainfire and I have spend a lot of man hours preparing and testing this fix for the entire communities benefit, so please be patient with us. Chainfire has put together the fix in a user friendly and relatively safe to use package, something that I just could not do.

Thanks man, well done!

Cheers to everyone all around!
[Galaxy Tab  Android Development] waz000000:
And on that note, I would be highly grateful if you could send me the APK, i keep getting screwed over because of this locked bootloader, coming from the galaxy S and flashing everything I didnt realise samsung where doing this and the first thing i did when i got my new tab was flash...sigh..

I will of course not disclose the apk or anything else, not interested in the code just a fix to this annoying inability to flash.
[Galaxy Tab  Android Development] crazylemon:
please man, be patient. roto and chainfire will publish the fix when it is save. for now, I hope you have learned from this matter, like I did. For flashing once, read twice! ;)
[Galaxy Tab  Android Development] wgery:
Did you read what you replied???Or the thread headline =[FIX IN CLOSED BETA]=some people who involved in testing got the apk.

and from rotohammer's reply ".....please be patient with us..."

BE PATIENT, they will release the fix when they 100% sure that the fix won't brick your 600$ device...
[Galaxy Tab  Android Development] waz000000:
Don't think I was asking either of you was I?

I asked a Question to rotohammer, it's entirely up to him and chainfire If they decide to send it me or not ( I believe they can speak for themselves) and as for making an expensive brick that isn't your concern either :)

why do people on XDA decide to speak for others and try and get their tongues as far up the DEV's arse as possible. baffles me why people get involved in things that are not directed to them.
[Galaxy Tab  Android Development] wgery:
Because people like YOU don't understand that is a closed beta.Why didn't you applied as a beta-tester when the main thread was updated????after now you see it's a 100% succes of course you want the apk.Before then the testers didn't know the stat of succes/brick why you didn't applied for tester then?

diffident,impatient...

Or if you want to ask somebody why don't you send him/them a PM??
[Galaxy Tab  Android Development] waz000000:
I did as a matter of fact, i applied the moment it went up but again that's nothing to do with you either is it.

and id rather not bother them with a PM as im assuming they get a lot of PM's to deal with but this request was on the off chance Roto saw it and decided he would send it me.

The consequence of me bricking the device means nothing as I can go out tomorrow buy another and not think twice about it, if that one breaks I can do the same and so in fact I could probably buy a warehouse full. So please don't make assumptions when you don't know me.
[Galaxy Tab  Android Development] rotohammer:
The bootloader fix application is the intellectual property of Chainfire. I do not have the permission to release it.
[Galaxy Tab  Android Development] Chainfire:
This is getting completely out of hand, and my patience has run out.

Unless you are the owner of a P1000L or P1000N, don't bother PM-ing me - I won't reply. I am not sending out the APK to anyone else at this time. Release is one or two days off, exactly as scheduled, and you'll just have to wait it out. (After two months of this issue, is two days really so long ?)

For now, due to the general tone (smartassery, delusions of entitlement, first signs of an upcoming flamefest) of the last two pages, this thread is closed until the APK is ready for release.

EDIT: APK release (for non-L/N devices) will be TODAY !
[Galaxy Tab  Android Development] Chainfire:
Patch released !

Enjoy. Hope it doesn't brick anybody :)
[Galaxy Tab  Android Development] abuser0815:
Worked for me!

Edit:

P1000 euro (tab from vodafone spain and unlocked)

roto-jmev4 with former jmc signed primary bootloader, sbl was not signed

Thanks again roto and chainfire!
[Galaxy Tab  Android Development] humberos:
Hi abuser0815,

Please, post your tab and ROM versions.

Thank you!
[Galaxy Tab  Android Development] kay_kiat88:
yay! thanks roto and chainfire! worked!

asian tab with rotojmev4.
[Galaxy Tab  Android Development] faust86:
Unblocked. European Galaxy Tab with JM6 firmware, but bootloader from JMC. Next question is: can i flash any firmware and use this tool to unlock? Bootloadercheck shows me that my zImage is signed - is this any problem?
[Galaxy Tab  Android Development] rmanaudio:
We need to fix this issue as this is the main reason why most of us cannot flash any CWM or custome Kernals.

Why would samsung do this? Unless they are introducing this into all future ROM's so nobody can flash custome kernals or Roms!?!?!?!?
[Galaxy Tab  Android Development] Chainfire:
Or maybe it's to mess with us leak-users? Maybe its only a test? We really don't know. But indeed it had crossed my mind that they may be trying to limit our custom ROM/kernel use.