yashsingh1/xdaforums huggingface dataset:
[AT&T HTC One (M7)] hafizimtiaz:
You can convert to Developer Edition. You will get Sense 6.0 update ota immediately. You can also flash the at&t sense 6.0 ota via stock recovery. For both the cases you will need s-off. You can follow the tutorial on my signature.
[AT&T HTC One (M7)] Wonders_Never_Cease:
None of the stock roms have tethering unlocked without appropriate service plan,you will need to flash a developer build or international rom that have tethering unlocked.
[One (M8) Q&A, Help & Troubleshooting] valery.m:
Hi, recently I have bought an M8, unlocked it's bootloader via HTCDev, installed latest TWRP, rooted it by flashing SuperSU zip, and while trying to S-Off, got message that it doesn't work on my phone yet, so no S-Off available.

May be I'm doing something wrong?

Here's some info:

$ sudo fastboot getvar all

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P****000
(bootloader) cidnum: HTC__A07
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.005s

Does anybody here with the same phone S-Off'ed it via firewater?
[One (M8) Q&A, Help & Troubleshooting] EddyOS:
You're doing nothing wrong, your phone just isn't compatible at this time (and maybe never)...nothing you can do other than voice your concerns in this thread...:(

http://xdaforums.com/showthread.php?t=2733870
[One (M8) Q&A, Help & Troubleshooting] ashyx:
Did you ota before unlocking? I believe HTC patched the exploit with the latest update.
[One (M8) Q&A, Help & Troubleshooting] EddyOS:
He's on 1.54.401.10 (the latest) so I'll assume so (or the person the OP bought it from did)
[One (M8) Q&A, Help & Troubleshooting] valery.m:
Thanks. Yes, I had installed some OTAs. They arrived too quickly, before I have read detailed S-off manuals. :o
[One (M8) Q&A, Help & Troubleshooting] Mr Hofs:
Ota is not the issue ! I s-offed mine and was on 1.54.401.10.......that's a myth !
[One (M8) Q&A, Help & Troubleshooting] valery.m:
Kind of magic? Can i ask you to post your "fastboot getvar all"?
[One (M8) Q&A, Help & Troubleshooting] EddyOS:
It won't show anything, it's a hardware change between M8 handsets and some work others won't. If yours doesn't work now, it won't work ever unless the firewater (or other devs) get it working...
[One (M8) Q&A, Help & Troubleshooting] ashyx:
I doubt it's hardware, if it's implemented in the first place it must be software especially seeing as s-off can be achieved on any device with a java card, apparently.
[One (M8) Q&A, Help & Troubleshooting] EddyOS:
I'm only going on what was said in the firewater thread when it was first released. Apparently there's a check and if your phone gives a certain result it means your phone won't work...
[One (M8) Q&A, Help & Troubleshooting] Mr Hofs:
I can post my "all info" but it won't be of any use ! It works or it doesn't......
[One (M8) Q&A, Help & Troubleshooting] valery.m:
ok, will wait.
[One (M8) Q&A, Help & Troubleshooting] nO.One2:
some CIDs are unsupported till now, you can see it's the problem of many:

http://xdaforums.com/showthread.php?t=2733870
[One (M8) Q&A, Help & Troubleshooting] jeetaryan:
I have the same issue :-

Below are the info:-

getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.16.0.0000

(bootloader) version-baseband: 1.15.21331831.A17G

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.56.720.4

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno:

(bootloader) imei:

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B65000

(bootloader) cidnum: HTC__038

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: c3d94491

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.007s

Can anyone help regarding how to S-OFF this device !!

It will really be helpful.

Thanks in advance
[One (M8) Q&A, Help & Troubleshooting] Mr Hofs:
If firewater doesn't work the only option is sunshine. No other way.
[One (M8) Q&A, Help & Troubleshooting] sirio87s:
the only way for s-off is sunshine method, but it has a in-app purchase of $25...!!!
[One (M8) Q&A, Help & Troubleshooting] Mr Hofs:
Yes and ? That's a fair price for s-off. The profit you gain for having it is well worth the money....

- lock the bootloader again

- flash recoveries from within the recovery or app. In other words no pc needed anymore

- return the phone back to stock 100% for warranty issues.

- down and upgrade the hboot anytime

- flash any firmware to convert the phone as it's unbranded if you have a branded one.

All nice examples.

And the choice to buy it or not is in the hands of the user. People should not complain that it cost a bit, be happy it's there. The firewater team also invested in the exploit, especially time and maybe also some bricked devices.

Cheers.
[One (M8) Q&A, Help & Troubleshooting] EddyOS:
The Firewater team

IS

the Sunshine team ;)

They were going to charge eventually, seeing as up til now it's been optional (and I'm gonna assume most didn't donate)
[One (M8) Q&A, Help & Troubleshooting] valery.m:
As for my initial question - how to s-off - it's now solved by sunshine.
[One (M8) Q&A, Help & Troubleshooting] Mr Hofs:
I know firewater made sunshine ;)

What i meant to say was that a user can invest in their s-off, because firewater team also did that with making sunshine ;)
[One (M8) Q&A, Help & Troubleshooting] sirio87s:
i know what's the "pro" of s-off.... i did s-off on a old htc desire and htc ville... all for free... if will be released a free-tool with a FREE donation :good:, if not, no problem.... peace!
[General Omni Discussion] Trendsbuz:
Hello !

I am using the latest nightly build of omni rom 4.4.3 on galaxy s3, everything is working fine except my headphones aren't working

i tried everything

i searched the forum and people believe switching to nova launcher fixed their problems but didn't work for me..

few people on the forum recommend to disable the google hot word detection in voice settings, i tried the same but still no luck

Hold the Home screen > Settings > Voice > Uncheck Hotword Detection. Then reboot... but still no sound :(

and even i tried Boeffla-Kernel but still no sounds through headphone while playing music in apollo or google music player.

i switched to different CPU profiles from ondemand to performance but still not working

" i faced the same problem in cm11 nightly builds that's why i switched to omni rom but no luck "

please help me out...
[General Omni Discussion] Trendsbuz:
It seems people and developer out there don't want to help me..:( stuck with these custom rom issues
[General Omni Discussion] Entropy512:
You're on a device that is likely to get pulled for the next Android cycle due to lack of a maintainer. You also didn't post this bug via Omni's official bugreporting process documented in the FAQ, although I will admit that bug likely would have sat there.

Basically everyone that was working on the I9300 in the past either:

Had it die

Got rid of it

Has taken a break from Android development (Rebellos was our original I9300 maintainer but he's had to take a leave of absence from Android stuff.)

Exynos4 devices in general have been on minimal life support since late 2012. #blamesamsung - all of the former Samsung Exynos guys (including myself) got tired of dealing with their BS and prefer working with other devices.

The only person still working on I930x is Mark with the I9305 and I haven't seen him recently.
[Galaxy Note II Q&A, Help & Troubleshooting] fundoosite:
See this link..

http://www.thewestsidestory.net/201...-4-3-update-galaxy-note-2-verizon-att-sprint/

:confused:
[PDA2, XDA IIi, 2020i Software Upgrading] Astro1:
Team

Ive recently upgraded to Pugs patched software (from O2 )and all is very good however.

I used to be able to connect to loads of wifi spots ( some public some private ) but now nearly all tell me I dont have a certificate !!

Is this just me( and how it should be ?) or is there some setting I didnt put in the XDA11i after the patch that it had with the original O2 ??

Any ideas ? I know I shouldnt be connecting to private wifi but Im sure weve all done it at some time .eh !

PS read a thread that recommended hitchhiker and will try that next week .

Astro1
[PDA2, XDA IIi, 2020i Software Upgrading] reo:
Hi

i also experienced but on a different brand of PPC, is it possible to load certificates ?

how can i optimise my Wifi to connect on most networks ??

regards

reo
[AT&T HTC One (M7)] Daluvgurushine:
I have a HTC One AT&T Version Unlocked. i am having some problem. help me please?????

I have a HTC One AT&T Version Unlocked. My sense version is 5.0 and android version is 4.3. How to update it? I have also haviong issues on activating WiFi hotspot, every time i am enabling that, an error would occur and it says that contach att.com/mywireless or call 611 what to do.?/ I have searched on google and found that, they adviced me to change my at&t phone into google play editio using bootloader process. Is it safe to do?? and if not is there any other process to do. the main thing i am in india now. help me please help me???
[AT&T HTC One (M7)] Sloth:
Greetings,

You already have another post asking the same question and you have been given help.

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

In the future please do not post duplicate threads on the same subject.

Thread closed.

Thanks,

BD619
[Android Apps and Games] androinoo:
Hello everyone!

I'd love to introduce you to one of my game called "Magic Land"! :D

Some basic information about the game:

The game uses the ANDENGINE with the following extensions:

- Limbo

- TMXTiledMapExtension

- PixelPerfectCollisionDetection

- GooglePlayServices.

Game features:

There are a total of 45 levels (3 worlds, 15 levels each). Worlds 1 and 2 are easy-ish, however, world 3 is really hard, it's going to take you some time and thinking to complete it.

You can save your time and deaths counter for each level and compare them with other players from all around the globe. You can also log in to the Google+ services and see your and others results on the Google Play platform.

Controls are really easy, you can choose one out of two available options, which are ANALOG and DIGITAL. Using the DIGTAL setting you can move your character up, down, left and right. Using the ANALOG setting you can move your character up, down, left, right and diagonally.

If you can, please, download my game, rate it, and leave your comment. Constructive criticism is always appreciated, as it helps me improve! If you find any bugs feel free to forward them to me, thanks!

Google play link:

GOOGLE PLAY LINK

Video:

[YOUTUBE]VrpmvA3dRqg[/YOUTUBE]

Screenshots:

Thank you and enjoy!
[Android Apps and Games] Whookid:
Good game, only thing that could be really improved is the way the item is controlled. (Joystick)
[Android Apps and Games] dragon658:
Cool game. Addictive.

But it is really difficult to control the square. And in my opinion it is the main difficulty of the game.
[Android Apps and Games] androinoo:
Do you have any suggestions/ideas for control ?
[Android Apps and Games] ExoticHamster:
I just rated your game under username "BudMccrud.

Can you check out my game, and tell me what you think? http://bit.ly/1utlvFV

Also, I think you should make the box move a bit faster. I agree with the earlier comment, regarding the joystick control being hard.
[Android Apps and Games] androinoo:
Thanks. I rated you game also. Back button doesn't work and I don't see an exit button. Is it not possible to start without facebook login ?
[Android Apps and Games] ExoticHamster:
yeah right now there's a bug with the back button. Just close the app, and register using an email. You don't need Facebook to login. :)
[Android Apps and Games] Maurils:
So dificult :mad:. Like the other user said, the joystick controls are a little bad, but thats the only problem !
[Android Apps and Games] smartideas:
Nice!

I think that it is really good! What markets for ads do you use?
[Android Apps and Games] TapirL:
Great game! Landscape really is more engaging than portrait for games.
[Galaxy Tab 4 Original Android Development] ketut.kumajaya:
Boot image tools for Samsung Galaxy Tab 4 7.0, Degas board Marvell PXA1088

Unpack boot.img:

$ mkdir boot
$ tools/degas-unpackbootimg -i boot.img -o boot
$ mkdir -p boot/ramdisk
$ cd boot/ramdisk/
$ gunzip -c ../boot.img-ramdisk.gz | cpio -i
$ cd ../

Repack boot.img:

$ ../tools/mkbootfs ramdisk | ../tools/minigzip > boot.img-ramdisk-new.gz
$ ../tools/degas-mkbootimg --kernel boot.img-zImage
--ramdisk boot.img-ramdisk-new.gz --dt boot.img-dt
--signature boot.img-signature -o ../boot-new.img
$ cd ../

I'm not sure about boot image signature, you can try without --signature option. By comparing boot image to recovery image, I found a different signature and of course a different ramdisk but the rest is the same, including kernel and device tree table.

To confirm this tools reliability, you can unpack and then repack original boot/recovery image without modification. You will got two identical image, check it using a diff tool.

Generate kernel spesific device tree table:

$ tools/degas-dtbTool -o boot.img-dt-new -p kernel/scripts/dtc/ kernel/arch/arm/boot/dts/

Repack a new recovery as a flashable Odin:

$ tar -H ustar -c recovery-testkey.img > recovery-testkey.img.tar
$ md5sum -t recovery-testkey.img.tar >> recovery-testkey.img.tar
$ mv recovery-testkey.img.tar recovery-testkey.img.tar.md5

DISCLAIMER:

USE THIS TOOLS AT YOUR OWN RISK, I DON'T OWN TAB 4 7.0 FOR TESTING

Ketut P. Kumajaya, June 2014

XDA:DevDB Information

degas-mkbootimg, Tool/Utility for the Samsung Galaxy Tab 4

Contributors

ketut.kumajaya, Android Open Source Project, CyanogenMod Team, The Linux Foundation

Version Information

Status: Testing

Created 2014-06-17

Last Updated 2014-07-31
[Galaxy Tab 4 Original Android Development] ketut.kumajaya:
Android boot image:

Standard Android header:

Magic (8B)

kernel size (4B)

kernel addr (4B)

ramdisk size (4B)

ramdisk addr (4B)

2ndary size (4B)

2ndary addr (4B)

tags addr (4B)

page size (4B)

unused #1 (4B) (zero in standard Android)

unused #2 (4B) (zero in standard Android)

product name (16B)

kernel cmdline (512B)

id (8B)

Samsung Galaxy Tab 4 7.0 header:

Magic (8B, ANDROID!)

kernel size (4B)

kernel addr (4B, 0x10008000)

ramdisk size (4B)

ramdisk addr (4B, 0x11000000)

2ndary size (4B, 0x0)

2ndary addr (4B, 0x10f00000)

device tree size (4B, 534528)

unknown (4B, 0x02000000)

tags addr (4B, 0x10000100)

page size (4B, 2048)

product name (24B, empty)

kernel cmdline (512B, empty)

id (8B, empty)

Samsung Galaxy Tab 4 7.0 layout:

A. header (as above - 1 page)

B. kernel (n pages)

C. ramdisk (m pages)

D. second stage (o pages)

E. device tree table (started with PXA-DT magic, p pages)

F. signature (256 bytes)

Samsung Galaxy Tab 4 7.0 PXA1088 device tree format:

magic (6B, PXA-DT)

version (uint32)

num of DTBs (uint32)

platform id #1 (uint32)

soc rev #1 (uint32)

offset #1 (uint32)

size #1 (uint32)

...

platform id #Z (uint32)

soc rev #Z (uint32)

offset #Z (uint32)

size #Z (uint32)

0 ("zero")

padding

DTB #1

padding

...

DTB #Z

That's why standard tool fail to unpack this degas board boot.img :mad:
[Galaxy Tab 4 Original Android Development] ketut.kumajaya:
We need a brave Tab 4 7.0 owner here :laugh: Don't hesitate to ask me to repack a slight modified boot.img or a recovery repack with Google testkey so you can flash a signed flashable zip using stock recovery.
[Galaxy Tab 4 Original Android Development] ShinySide:
And let the games begin...Kernel check...Shoot for recovery tomorrow/later today.... Thanks bro Ive been killing myself over this
[Galaxy Tab 4 Original Android Development] ketut.kumajaya:
Great, a dead man back alive :laugh:
[Galaxy Tab 4 Original Android Development] ketut.kumajaya:
Device tree combiner tool added!
[Galaxy Tab 4 Original Android Development] St34lth:
Can I use it on my tab 4 10.1 T530?
[Galaxy Tab 4 Original Android Development] ketut.kumajaya:
No. The tools that I share here special for Tab 4 7.0 PXA1088. For Qualcomm based platform, I think you can use standard CM boot tools (unpackbootimg, mkbootimg, and dtbToolCM).
[Galaxy Tab 4 Original Android Development] 404-Not Found:
I may be up for testing what are the risks?
[Galaxy Tab 4 Original Android Development] slowfax:
If you still need an idiot to brick his brand new 4.7, you can count on me :)
[Galaxy Tab 4 Original Android Development] soldier1184:
im in

im familiar with linux and what not so im in just let me know in a PM ill brick it
[Galaxy Tab 4 Original Android Development] Dees_Troy:
I don't see links to download the degas-unpackbootimg or the degas-dtbTool or for source code for these tools. At least you outlined the differences between the boot image formats in post 2 though.
[Galaxy Tab 4 Original Android Development] toastcfh:
I managed to find what i believe is them here on github.
[Galaxy Tab 4 Original Android Development] jokowi:
[MENTION=912474]Dees_Troy[/MENTION] and Team Win Recovery Project, I almost forgot to say thank you for all your hard work

to make TWRP source code. Now i had compiled TWRP 2.8.0.0, and it seems working fine in my galaxy tab 7 SM-T231

mtp can detect, but still can't pullout backup at the moment. but it is not big problem fo me :)

[MENTION=4021423]ketut.kumajaya[/MENTION] thanks again for making degas unpackbootimg tools for pxa1088.

actually i was using it to unpack recoveryimage

mantap kali ah bro :good:

without you guys, i can't make my custom recovery

Thanks
[Galaxy Tab 4 Original Android Development] ketut.kumajaya:
http://xdaforums.com/devdb/project/?id=4629#downloads
[Galaxy Tab 4 Original Android Development] geseeker:
Aside from using the degas tools, did you do anything special to make the kernel work? By special I mean did you do anything besides:

make ARCH=arm CROSS_COMPILE=arm-eabi- pxa1088_degaswifi_usa_defconfig

make ARCH=arm CROSS_COMPILE=arm-eabi- zImage

... and also possibly regenerate the device tree.

I was trying to compile & run the kernel, but it keeps getting stuck at the power-on screen (not boot animation). The kernel source is T230NUUE0ANE2, taken from the opensource center.
[Galaxy Tab 4 Original Android Development] ShinySide:
Just ran what was in the read me and used a Linaro toolchain. 4.7.4 I think. I havent messed with it much. Have it on my github but only have 2 commits pushed. stock source and update to the toolchain path but dont believe I did anything more then that.

Also dont know if you released it, but the modules are in/go in the boot.img
[Galaxy Tab 4 Original Android Development] geseeker:
I guess the modules you referred to are generated by running `make modules`? How were you able to pack them into boot.img? I thought the only things that are in boot.img are the kernel (zImage), ramdisk, and the device tree, no?
[Galaxy Tab 4 Original Android Development] ShinySide:
After you compile the kernel, taek the zimage and modules (modules are built when you compile the kernel so in your kernel working folder do a search for ".ko" and youll find them all, then take the stock boot.img and use this to unpack, swap the zimage in and then do a search for .ko in the extracted boot.img folder and paste your new .ko's / modules in there. I say search for them because I cant remember if the directory is system/lib/modules or lib/modules in the boot.img and then repack it with the same tool
[Galaxy Tab 4 Original Android Development] geseeker:
I've got it working! The modules are actually in the ramdisk under /lib/modules, so you'd have to update the ramdisk as well... I see.

Thanks bro, for the quick reply! :)
[Galaxy Tab 4 Original Android Development] Inside 4ndroid:
hi i have an issue or maybe not i dont realy know..???

i dumped my boot.img from my t230 an have used the tools to unpack and repack with no changes but the original file is 16.8mb and the boot-new.img is only 9.2mb??

does this matter at all???
[Galaxy Tab 4 Original Android Development] :
I4,

hi, if i understand the question correctly,

when you dump the/an image you pull the entire block the image actually resides in.

meaning if block size=16.blah mb & actual image size= 9.blah mb, when dump image, final output size will= 16.blah mb

now, if you unpack the image and immediately repack it with no changes,

unpacked image=16.blah mb, then unpacked and repacked, repacked image size [actual]= 9.blah mb

the actual image is always smaller than block which contains it otherwise it wouldn't fit.

You can get an idea if your image may be too small by it's size after repacking if for example,

we can guess the rough/expected size of the image should be about 9.blah mb in size, maybe even 8.blah mb or 10-11.blah mb

depending on what you're setting up in your kernel build or ramdisk.

BUT, knowing the general range of the image size, if your image comes out to be say 4.blah mb in size or is bigger than the set size

of the block device you need to write it to, in this example = 16.blah mb, then you can clearly tell that something is wrong.

m
[Galaxy Tab 4 Original Android Development] Inside 4ndroid:
I see now thanks for thd explanation.. it now makes sense.. cheers your a top dude..
[Galaxy Tab 4 Original Android Development] daavvis:
hey [MENTION=4021423]ketut.kumajaya[/MENTION], long time no speak :)

i just got a tab 4 7 and im getting ready to set up a device tree to port mokee to this tab (tab 2 was getting old hahaha)

i figured with our powers combined we could get a working custom ROM going ( once the device tree is set up we should be able to use it for all roms, cm/pa/mokee... bla bla )

would the tree from the tab 3 be a good place to start? i am sure the two of us could get this going :)... maybe get [MENTION=5153662]Android-Andi[/MENTION] involved as well, we work well together...

hope to here back from you !!! :):)
[Galaxy Tab 4 Original Android Development] ShinySide:
He's got a device tree on his github I believe
[Galaxy Tab 4 Original Android Development] daavvis:
No sir, but might be able to use pieces of his device repos for the tab 3
[Galaxy Tab 4 Original Android Development] huffmybrd:
not to hijack the tread or anything but im in desperate need for a PIT file for a sm-t230nu, somehow my partition tables got borked and now when i try and flash anything in ODIN, it states that there is no PIT partition at all. can someone pleaseeeeeeeeeeee help?????

(this is the ODIN log)

<ID:0/005> Added!!

<ID:0/005> Odin v.3 engine (ID:5)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Get PIT for mapping..

<ID:0/005>

<ID:0/005> There is no PIT partition.

<OSM> All threads completed. (succeed 0 / failed 1)
[Galaxy Tab 4 Original Android Development] ketut.kumajaya:
Any progress?
[Galaxy Tab 4 Original Android Development] daavvis:
It's been a busy week but I'm getting started right now and have 4 days to work on it

I have the kernel from samsung, I can pull the proprietary files from my tab, and am going to get started on the device tree tonight :)

I'll keep you updated :):)