yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 General] RavMust:
SIGNED
[Galaxy Tab 10.1 General] sfermat:
One more

Enviado desde mi GT-P7510 usando Tapatalk 2
[Galaxy Tab 10.1 General] gveloce:
Signed.

But i think Sams is deaf....?
[Galaxy Tab 10.1 General] bogdan1234:
Signed! Let's hope Sammy will do smth about it even though I don't have high hopes.
[Galaxy Tab 10.1 General] njfoses:
Samsung has already stated that support for this tab is finished.
[Galaxy Tab 10.1 General] Technical:
Where? A link please.

How long did they give support? 2 months?! I cannot believe...
[Galaxy Tab 10.1 General] ChiAn:
Signed! But I bet samsung wants us to move onto their new tabs....

Yes I'm a pessimist
[Galaxy Tab 10.1 General] Technical:
Shame on Samsung... Although you're not being pessimist... Seems we're abandoned :crying:
[Galaxy Tab 10.1 General] Albertum:
Done
[Galaxy Tab 10.1 General] redhk886:
don't think samsung will ever update this model. : (
[Galaxy Tab 10.1 General] Nacgmal:
it's official? samsung abandoned support for this tablet?
[Galaxy Tab 10.1 General] MicheyM:
Signed

Check out http://xdaforums.com/showthread.php?t=2215532 , they may be testing it
[Galaxy Tab 10.1 General] smaxxuk:
signed
[Galaxy Tab 10.1 General] mr.fast:
Even though I'm no longer a Tab owner I have redesigned the petition making it more user-friendly. I have also posted some blog posts regarding the SamMobile article.

I would also like to once again thank all signers.

Thanks,

mr.fast

http://www.ipetitions.com/petition/update-to-jb-for-the-galaxy-tab/
[Galaxy Tab 10.1 General] crispychips99:
Signed.

Like everyone else, I doubt it will work, but we can hope right.

Probably saving their money for lawsuits against Apple.
[Galaxy Tab 10.1 General] Albertum:
Did it again :)
[Galaxy Tab 10.1 General] mr.fast:
Maybe it will work. Maybe it won't.

It's better than doing nothing though :)
[Galaxy Tab 10.1 General] Gust30:
Signed
[Galaxy Tab 10.1 General] Technical:
The initial target of 1000 signs was overpassed.

Now we're going to 2000. How many should we get to call Samsung attention?
[Galaxy Tab 10.1 General] mr.fast:
I'd say 2000 is enough. The initial target wasn't really good enough for Samsung to care about.

In terms of the device's sales (100s of thousands) 1000 isn't enough :highfive:
[Galaxy Tab 10.1 General] Capthowdy2410:
Yeah I'll definitely sign this hopefully it helps...
[Galaxy Tab 10.1 General] mr.fast:
Thanks.
[Galaxy Tab 10.1 General] :
Samsung is most likely not to respond to your petition because:

There are a lot of petitions like this for multiple devices, and Samsung has made 800 million phones already, most Android, and Samsung can't develop updates for all of them. They take time, and a lot of it.

I would personally recommend you to use a Jellybean ROM like CyanogenMod.
[Galaxy Tab 10.1 General] Jay Rock:
Never hurts to try.
[Galaxy Tab 10.1 General] annson08:
Right
[Galaxy Tab 10.1 General] Technical:
Until we got something from Samsung, try this very good ROM: Ganbarou http://xdaforums.com/showthread.php?t=1674000
[Galaxy Tab 10.1 General] mr.fast:
Just because Samsung makes so many devices it doesn't mean it has the right not to support them.
[Galaxy Tab 10.1 General] :
Firstly, Samsung has the rights not to support their devices and secondly imagine one company developing Android updates for 800 million phones.
[Galaxy Tab 10.1 General] mr.fast:
Just out of curiosity. How do you know they have 40 employees?

If they do, they should hire more.
[Galaxy Tab 10.1 General] Jay Rock:
Maybe they shouldn't be putting out so many phones so they can focus on their flagship devices.
[Galaxy Tab 10.1 General] Theblaze973T:
Samsung is comprised of roughly 80 companies. Not all are electronics, but such a huge global company has several thousand, if not several hundred thousand, employees.

Also, 800 million phones? I think you are talking about phones they sold, not actual devices. Say for example, they sell 2 million Galaxy S3's across 4 distinct regions, that's only 4 updates for thousands of employees to work on, and it can serve millions of devices.
[Galaxy Tab 10.1 General] mr.fast:
When did I say they had 800 million phones. I think you're confusing me with someone else ;)
[Galaxy Tab 10.1 General] demon25:
could you tell me the benefits of having JB instead of ICS ? On a side note, I am hoping to find a phone and messaging mod for my tablet, i have the sgh-i497 4G/LTE 10.1, so the 2g/3g enable phone mod on this forum for the 10.1 probably wont work for me
[Galaxy Tab 10.1 General] t1mman:
I think you could easely find the answer to that with google!

But, basicaly, the main optimisation is "Project Butter", where it optimises the wole deal and make it faster and beter!
[Galaxy Tab 10.1 General] jtdc:
signed. need project butter on official stock ROM. i saw petition count is 1,839 now.
[Galaxy Tab 10.1 General] xmilitary:
Signed :laugh:
[Galaxy Tab 10.1 General] icemang:
Signed! Good call on this, hopefully it works! :cowboy:
[Galaxy Tab 10.1 General] PRichardson:
Signed.
[Galaxy Tab 10.1 General] nnaatthhaannx2:
Signed!
[Galaxy Tab 10.1 General] Technical:
Any news about the petition itself?

Is there *any* sign that it will work in *anyway*?
[Galaxy Tab 10.1 General] Jjmunky:
Signed. Kind of stupid that we have to do something like this just to show them we want an update though :\
[Galaxy Tab 10.1 General] custommx3:
Done!
[Galaxy Tab 10.1 General] Technical:
Well, we're on 2,014 signatures and... nothing...
[Galaxy Tab 10.1 General] lonelycount:
Technically speaking, the gtab 10.1 is dead. How sad...:(:(:(
[Galaxy Tab 10.1 General] Technical:
Just because of the patent fight with Apple?

Are you referring to anything else?
[Galaxy Tab 10.1 General] vadim881:
Signed.

Is an author of this thread alive?
[Galaxy Tab 10.1 General] Misledz:
What you should look forward to is KLP. They claim that older devices will get a second chance with it. Google assured that. If samsung says otherwise, then samsung is the real jackass here.
[Galaxy Tab 10.1 General] eushaun99:
Sorry to be a noob here but what is KLP? :D
[Galaxy Tab 10.1 General] Misledz:
Keylime Pie, otherwise known as Android 5.0

Source : http://gadgetinsiders.com/android-5...-older-devices-get-launched-in-october-10560/
[Galaxy Tab 10.1 General] eushaun99:
Oh..

If Samsung doesn't want to release JB for us, then why should we wait for KLP?
[Galaxy Tab 10.1 General] jmitr:
Basically, the last "universal" version of Android that had very loose restrictions (single core cpu, 512mb ram) was ICS. Jelly Bean, with project butter, Google now etc had higher hardware requirements to actually run properly. The rumour is Google was running "project roadrunner" for battery longevity and have themselves said KLP is being made to work on all devices regardless of hardware (low specs).

So, no manufacturer will have any excuse to NOT upgrade a device to KLP if it is capable of or currently running ICS.

But, with the tab 3 and more coming out.....I wouldn't hold my breath waiting.
[Galaxy Tab 10.1 General] eushaun99:
I agree. I don't think Samsung will ever update this tab forever. They didn't even bother to fix the deep sleep issue for the 3g tabs which was fixed by grzwolf in the end.
[Galaxy Tab 10.1 General] Taggahertz:
Signed. I hope it works!
[Galaxy Tab 10.1 General] Acedia:
Signed!

Sent from my GT-I9000 with cm10.1
[Galaxy Tab 10.1 General] VenpaCasa:
Signed but did I miss something? My SGN10.1 is stock at 4.1.2 is that not real jelly bean? Are u guys referring to 4.2? I would love 4.2 too

Edit: ANNNND I apologize I'm in the wrong forum..... I was looking for galaxy note 10.1 whoops
[Galaxy Tab 10.1 General] SahilC:
This still on? Signed!
[Galaxy Tab 10.1 General] gulstein86:
2,054 have signed. Is there any progress to it? Did samsung really received or see it?
[Galaxy Tab 10.1 General] VeryCoolAlan:
I signed because Samsung has a bad rap of not updating.
[Galaxy Tab 10.1 General] havrosh:
Signed...

but don't hope :(
[Galaxy Tab 10.1 General] DG42xda:
Seems to me this post regarding the Tegra 2's lack of NEON support, and the increasing use of NEON by Google apps, means that the chances of an official update for the Tab 10.1 beyond 4.0.4 is probably zero:

https://plus.google.com/+CyanogenMod/posts/8wcuSVkr7zR

Let it go. ;) I'm just grateful I have a chance to play with 4.2 via CM10.1. I love this site.
[Galaxy Tab 10.1 General] tinlunchbox:
Bummer. Thanks for the info.
[Galaxy Tab 10.1 General] Beartd:
Yeah I agree with the post above, thinking our device is too old, its normal to samsung not update our device to latest firmware. Then I think its better to use our device to max functionality than upgrade to latest firmware. What do you want from android 4.3 / 4.2.2 / 4.1.2? almost no different from ICS for me.
[Galaxy Tab 10.1 General] Gerixeon:
Update is never going to happen. :(
[Galaxy Tab 10.1 General] John Kester:
Who needs the update, which may just be to 4.1.2 perhaps. That is terribly outdated at the moment as I have about 4 or 5 flying, smooth and pretty stable 4.3 ROMs from which I can pick and change anytime I wish to. As long as there are developers out there ready and willing to develop ROMs for the P7500, I do not care about Samsung's touchwiz, neither can they compel me to buy another tablet!

Cheers.
[Galaxy Tab 10.1 General] eushaun99:
Agreed. Even if Samsung do release any update for us, I probably won't go back to stock, given I've been on AOSP ROMs for so long. Touchwiz sucks ass for me.
[Galaxy Tab 10.1 General] Gil81:
Signed..

I like the enthusiasm op...

But I'm afraid they don't care much.

Good Luck to all of us...
[Galaxy Tab 10.1 General] Lucas Kado:
Why an official update?

Which would be the benefits? Now in SGT7 by twa_priv -excellent ROM by the way-. I've used custom ROMs for this device since day 5, now it's two years old and still new builds. Developers around are just awesome.
[Galaxy Tab 10.1 General] EirikrHinnRauthi:
I posted a reply -- letting them know they could always just skip ICS and head straight to KitKat for these devices.
[HTC Pico (Explorer)] #define:
Hello guys..

If you have any questions, or want to contribute to gaining S-OFF, post here..

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Alright guys, check out this thread to know the benefits of S-OFF on an HTC phone :

http://xdaforums.com/showthread.php?t=1786498
[HTC Pico (Explorer)] Hpsgill:
Disadvantages of s off????
[HTC Pico (Explorer)] #define:
Disadvantages??

You can easily hard brick your phone.. If you dont know what you are doing..

Other disadvantages are really dependant on perspective..

But this is the main disadvantage..
[HTC Pico (Explorer)] Hpsgill:
And advantages???
[HTC Pico (Explorer)] #define:
Advantages of S-OFF..

You can resize the 'system' partition.. So you can fit a larger ROM into it, without having to delete stuff from it..

You have complete control over your phone..

You can change SIM lock..

Right now you only have read/write permissions to the 7 partitions..

If you have S-OFF, you can duplicate someone's IMEI number, if you know what to do..

And do some other cool stuff..
[HTC Pico (Explorer)] dead_eagle:
The "S" refers to NAND storage security, so "Security On" and "Security Off". It has a number of effects, but the most obvious is that if you have both S-Off and root you can write to the /system partition while running Android, so easily remove system apps (device changing the sizes of the internal storage partitions is the main use).
[HTC Pico (Explorer)] xpmode:
I can write to /system/ while running Android without S-OFF.
[HTC Pico (Explorer)] #define:
How?? If you're talking about flashing ROMs, and removing or adding system apps, then we are saying two different things..

If not, then please elaborate.. :)
[HTC Pico (Explorer)] xpmode:
I mean adding and removing files from /system/.

For example, I can remove Trebuchet.apk from /system/ with some kind of root explorer after installing Nova Launcher.
[HTC Pico (Explorer)] #define:
Yes that you can do from the OS.. You have unlocked bootloader, so you get access to these partitions.. But not to radio.. And also, you cannot write to any other partition, except /system and /recovery..
[HTC Pico (Explorer)] DanceOff:
I really loved my old optimus one , no need to unlock and s-off . It was rooted easily by gingerbreak and had nothing like a bootloader menu. So easy it was ;)
[HTC Pico (Explorer)] #define:
Same here.. Never buying an HTC again.. Never ever again!!!
[HTC Pico (Explorer)] DanceOff:
But bricking my o1 was very easy , I bricked it twice but due to the awesome service center they replaced the motherboard every time for free !
[HTC Pico (Explorer)] #define:
Alright guys, I have the code for the exploit written for the Wildfire S(thanks to the devs over at WFS forum), now I need an extracted RUU.. So if someone has it, please tell me.. I need a few files from the extracted RUU of Explorer.. Post here ASAP if you have the RUUs... And I'll tell you what files I need..

I'm a bit busy at the moment, as I need to re-download Android SDKs..
[HTC Pico (Explorer)] xpmode:
What RUU and which files?
[HTC Pico (Explorer)] #define:
I need all the files, except the ROM zip itself, from an European RUU.. HBOOT v1.03.0000/v1.02.0000, and Radio v1.11.82.17..

Both HBOOT versions if possible..

Can you provide them??
[HTC Pico (Explorer)] Hpsgill:
Are u trying to s off explorer?????
[HTC Pico (Explorer)] #define:
Yes.. And I need all the help I can get.. Can you get me the files I mentioned in the above posts?? So that I can get started?? It would take a while for me to download it myself, as I have some other things on my plate right now..
[HTC Pico (Explorer)] Hpsgill:
I will help but how to extract hboot radio????
[HTC Pico (Explorer)] #define:
Download an RUU.. It'll be a *.exe file.. Run it.. Then, while it is running, go to Start > Run > Temp folder(the command should be "tmp" or "%temp%" or something like that, I've lost touch on windows)..

In that folder, you'll find all the files that the RUU extracted.. There should be a ROM zip, an HBOOT file, a DIAG file, etc.. Bring all the contents except the ROM zip itself..

Download the asian RUU.. I'm almost done with the European RUU.. And PM me the files.. :good:
[HTC Pico (Explorer)] #define:
Wow.. I tried 4 times.. Everytime it skipped into the ROM.. Let me try again...

EDIT : Nope.. no luck.. still skipping into the ROM...
[HTC Pico (Explorer)] cute_prince:
@bhargz16,

Have you tested whether hboot becomes unresponsive if we use a stock unpatched hboot.img with exploit ??

If not can you test it ?

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

Thats strange... I can get into patched hboot without any SD card bro..

Try this.. before,after and while issuing "fastboot boot patch.img" command repeatedly press Vol Down key till the hboot page appears
[HTC Pico (Explorer)] #define:
Yes.. Even on an unchanged hboot, ie, stock, with no modifications at all, it becomes unresponsive..
[HTC Pico (Explorer)] no.human.being:
And on our device, even with a stock HBOOT, it restores the HBOOT from NAND (you can see it initializing the framebuffer again). It looks like if both events are triggered by the same conditions.

Errm .. on the Wildfire S the "locked"/"unlocked" status is not stored in the bootloader, but in the phone's "misc" partition. There's a word at a speific offset (don't know the correct offset any more) that's either 0xffffffff hexadecimal (for "locked") or 0x55435448 ("unlocked") or 0x4c435448 ("locked"). If you have a rooted phone, you can lock and unlock the bootloader at will by flashing "misc" images with the corresponding values.

That's not true. Once you have loaded a "hacked" HBOOT into RAM that thinks that the Radio is S-OFF you can flash anything (including of course the hacked HBOOT itself) to the phone's "hboot" partition using "fastboot flash hboot hboot.img" command. So once you get temporary S-OFF and a bootloader that responds to the Fastboot protocol, you'll also be able to make the S-OFF permanent.

The bootloader file itself is actually not signed at all, it's a raw image. The entire firmware file (it's called "PG76IMG.zip" for our phone) is signed "in a weird way" (some "non-standard" RSA stuff). As you see from the extension, it's a zip image. It contains partitions images, e. g. "hboot.img" (or "hboot*.img" - there's almost always some kind of "hash" in the file name) and this is a raw image (no signatures, no encryption).

Now what HBOOT does is it reads the "data part" of the entire firmware file (so the "PG76IMG.zip") and somehow compares it for signature match. I don't know in detail how this comparison is done. I know how it's done for "standard RSA", but HTC has implemented RSA incorrectly (and probably way more easy to break than the "proper" RSA implementation but we didn't focus on breaking that one, we never considered the crypto implementation a "weak spot" even though from a cryptanalyst's view it probably is) so they do it somehow different. Like I said we didn't focus on this, so I can't tell you a lot.

The HBOOT you "chainload" is a bootloader and, like the "normal" HBOOT on your phone, it will boot straight into the ROM when no keys are pressed and will show the bootloader menu when Vol-Down key is held. At least on the WFS it works just as expected. The only "problem" is that once the "chainloaded" bootloader shows its menu, it will start "restoring" the original HBOOT. And again, if no keys are pressed on the phone when the original HBOOT is restored, the original HBOOT will boot straight into the ROM. If Vol-Down is held, the original HBOOT will show its menu so you're back at S-ON.

The "chainloader" exploit is designed to make the processor appear as if it was just coming out of a reset, as that's the "normal condition" for a bootloader to run. So the "payload" thinks that the processor is just coming out of reset and that the OEMSBL (part of the Radio) has loaded it into RAM (which is what happens during normal boot procedure), while in reality, the exploit has loaded it into RAM. ;)
[HTC Pico (Explorer)] #define:
I stand corrected(a lot).. :P

Anyways, about the not-responding problem.. Is it possible to implement a sort of "return 0" like we did with the S-OFF?? Something like, find the place where, the hboot tries to restore itself, and tell it not to?? Or is that check not performed in the hboot itself??

Also, I read somewhere in OneX forum that HTC signs their hboots by putting a few bytes of some kind of raw data in it, which is interpreted by disassemblers as corrupt data, but when examined by a hex editor, doesnt appear to be corrupt..
[HTC Pico (Explorer)] #define:
The Explorer behaves differently.. When booting into a modified hboot, whether you press the Vol-Dwn button or not, it doesnt check the SD card for any files.. It just... dies... And having the SD card in the phone while booting from the modified hboot doesnt make a difference either...
[HTC Pico (Explorer)] #define:
Actually what I meant here is that we wont be able to flash the modified hboot we use(the one with the exploit) to gain S-OFF.. After S-OFF anything is possible(almost literally).. :D
[HTC Pico (Explorer)] no.human.being:
Yes, it's either something like this (pseudo code) ...

if (check_if_hboot_has_been_tamperred_with())
restore_hboot_from_radio();

... or it's something like this ...

if (check_if_hboot_has_been_tampered_with())
restore_hboot_from_radio();
else
continue_initialization();

In case one we may either have the "check_..." function always return zero (or whatever value is "not tampered") or we may modify the "restore_..." function so that it does nothing (returns immediately) and then the normal initialization continues.

In case two we cannot do the second one, since then neither "restore_..." nor "continue_..." is triggered, so we have to make sure the "check_..." function returns "pass".

So the (chainloaded) bootloader displays the HBOOT screen even if Vol-Down is not pressed? That's weird, since the exploit is designed to make the processor appear as if it was coming out of a reset. The chainloaded HBOOT should not be able to distinguish the handset's status from a normal cold boot and if you do a normal cold boot with Vol-Down button pressed, the HBOOT will go into the bootloader menu, right?

Well that's right. The main reason we're not able to do this is because we don't know how to write to NAND partitions from the machine level (in assembler code) so we use a "working" (security disabled) bootloader for this task.

It's also a lot safer, since it will provide "volatile S-OFF". If you modify the HBOOT partition in NAND you might do one thing wrong and end up with a bricked phone. On the other hand, we can be pretty sure that HBOOT has properly implemented writing to NAND. In addition, if the patched HBOOT runs stable from RAM, it'll most likely also run stable when booted from NAND. But the main reason is actually not knowing how to write to NAND at the machine code level. :D
[HTC Pico (Explorer)] rajko666:
hi guys, i have an idea, maybe a noobish...can we compare Revolutionary modified HBOOT for HTC Wildfire, and non-modified HBOOT version, and see how they did all those things?

i dont understand a thing about this, but maybe it will help, somehow :D
[HTC Pico (Explorer)] no.human.being:
Revolutionary performs a buffer overflow exploit in the device's "misc" partition. I guess that they can then "somehow" overwrite the HBOOT directly inside the Radio itself. Once you've done that, the comparison will yield "unmodified HBOOT" as the version provided by the Radio is then the same as the version running on the phone, so they probably don't face the problem we're facing here at all with their method, however, our method has other advantages over theirs.

Revolutionary have tried to perform their exploit on the MSM7227 processor (that the Wildfire S uses) and it failed because the vulnerability that they exploited wasn't present on this chipset. They haven't tried to find a vulnerability in the MSM7227 chipset though since it's "not widely used" and thus not a "valuable target" (they were a bit more harsh when they realized that the processor wasn't vulnerable to their exploit - they said that we had "crappy hardware" :) ). However, we have found another vulnerability and designed the "chainloader"-exploit to exploit it. It can probably be applied to many different chipsets with some processor-specific modifications since it exploits a fact that is guaranteed by the Linux kernel specification (remember that Android is based on Linux) and can thus not easily be fixed. Our shell-code is still not perfect though and somehow detects that we've been tampering around with the device's boot code. :)
[HTC Pico (Explorer)] cute_prince:
No bro, the exploit is working fine :)... The chainloaded bootloader displays HBOOT only when Vol-Down is pressed.. .

Only problem is it gets unresponsive even if SD card is inserted (i.e., it wont look for diagnostic file (PJ03DIAG.nbh in our case) although SD card is present)..
[HTC Pico (Explorer)] bulletproof136:
Thanks for awesome work guys :thumbup:

I pressed thanks to all guys which are helping here and thanks to op for this thread and make this possible :)
[HTC Pico (Explorer)] #define:
Actually its right.. with the sd card inserted, pressing the vol-down button doesnt make a difference.. it'll always become unresponsive.. without the sd card, pressing the vol dwn button gives the hboot screen, and not pressing it at all makes the phone boot directly into the ROM...
[HTC Pico (Explorer)] -igorok-:
hboot 1.01.0000

I have unmodified hboot v.1.01.0000 from ruu.
[HTC Pico (Explorer)] immortal_yash:
Here you go Orignal unmodified Hboot v1.00.0000 :)