yashsingh1/xdaforums huggingface dataset:
[Nexus S Q&A, Help & Troubleshooting] Suomalainen:
Happy New Year All,

I've been trying to problem solve the following issue with no success. Perhaps it's time to ask someone here if they can help me conquer the challenge I'm faced with..... Here we go!

I have a Nexus S and and use Ubuntu 12.04 LTS. Here is what I want to do. On my Nexus S, I have installed the app "GPS over BT". Then on my Ubuntu machine I installed Blueman and GPSD. To be even more precise, I followed the instructions found here:

http://gaygeekramblings.wordpress.c...onnect-ubuntu-laptop-to-gps-on-android-phone/

As far as installing everything the article suggests, mine was a perfect mirror image. Yet for some reason data is not moving as it should. The app "GPS over BT" shows that it is connected cause I can see my laptop name and the BT icon burns "green". Even when I connect via serial using Blueman I'm notified that connection was successful although a green dot does not burn over the "B" in the panel. Perhaps this isn't an issue?

Anyway, I really would like to get this working before the year ends and hope someone here may be able to offer assistance.

Thank you very much!

Happy New Year to all!
[Nexus S Q&A, Help & Troubleshooting] Suomalainen:
Bump...
[Nexus S Q&A, Help & Troubleshooting] Suomalainen:
I still haven't got this to work and want to attempt a step by step approach.

Firstly, I'd like the terminal code "hcitool scan" to see the GPS in my Nexus s. Currently, this code only sees my nexus s and not the GPS inside it.

I have an Android app installed called "GPS over BT" and it indicates that the apps BT is discoverable but still isn't seen.

Any ideas how to get hcitool scan to see my GPS?

Thanks.
[Acer Iconia Tab A100] heX79:
Any of the A100 talent, have the A110?

It's a decent machine for the price. It goes for around 150, comes with 8gb internal, expandable to 32g via micro SDHC, 1gig of RAM, Tegra 3 quad core @ 1.2ghz.

Only current issue, no recovery (I believe the recovery and kernel are combined), root method or ROMs available for this beast. There was a root tool for 4.1.1, but some have updated (for better ui enhancements) to 4.1.2, and there's no root option for it.

Just wondering if any of the A100 talent have this, it would be great to see this thing unleashed!

Sorry if anyone is upset about this being the wrong category/thread... Unfortunately, XDA has no dedicated thread for the A110, at this time.
[Acer Iconia Tab A100] pio_masaki:
No I went with a nexus 7, no unlocking is a deal breaker right off the bat with me. Plus I heard they didn't upgrade the screen or battery in it, two things I hated about the a100, and were also deal breakers for me.
[Acer Iconia Tab A100] heX79:
Unlocking the BL is easy on the A110. I did it with adb. :)
[Acer Iconia Tab A100] pio_masaki:
Then why no root? If its unlocked just flash a rooted stock ROM or something.
[Acer Iconia Tab A100] heX79:
Nothing seems to be available, at the moment. I wouldn't know where to begin, compiling from source.
[Acer Iconia Tab A100] pio_masaki:
Will it use an update.zip that's been changed if its unlocked?

Sent from my Thrive - Kuroikaze B19
[Acer Iconia Tab A100] heX79:
Wouldn't know, there is an os upgrade file on acers page, the same image name as my current version (after updating to 4.1.2), can that be renamed to update.zip, modded and flashed? I've not used a stock recovery before lol.

Sent from the Tab
[Acer Iconia Tab A100] pio_masaki:
If its a zip file maybe if not its anyone's guess how to mess with it.
[Acer Iconia Tab A100] heX79:
Yes it's a zip, 54MB in size, just an update from 4.1.1 to 4.1.2.

Name: OS_Acer_AV051.A110.RV00RC09.WW.CUS1_A41J_A.zip

File/Folder layout:

/firmware

/META-INF

/patch

/recovery

/system

blob

Download link, for anyone interested.
[Acer Iconia Tab A100] pio_masaki:
Then do a quick signature test, add a random file into it then see if it flashes or not. Doesn't matter how big or what it is.
[Acer Iconia Tab A100] jondi23:
Need to add a new source for the A110 to get developers. Its still a new tab but the down side is the battery sucks and they never change the screen angle. I guess to keep it in the $200 mark. Then again the nexus 7 has no micro sd port, hdmi port, but the screen is so clear and it support otg.
[Acer Iconia Tab A100] heX79:
I tried to add the Superuser.apk to the /system/app and SU to the /system/bin, but it gives a corruption error. I'll have to completely unzip it, add the files and re-zip in order to add them.

But to work in the stock recovery, I assume it would need to be renamed to update.zip, and placed on the internal /sdcard?
[Acer Iconia Tab A100] pio_masaki:
Probably external SD.
[Acer Iconia Tab A100] sky007:
Did you make it? I am waiting to root my A110 as well.
[Acer Iconia Tab A100] pio_masaki:
OK well let's see. Is there a twrp or something for a510? I can see about making a twrp but its extremely risky without some precise information since I don't have one to even look at for information. I'll be somewhat willing to work a little to get it opened up but you'll all need to do the homework and be willing to test it. Recoveries are very dangerous potential brickers.

Or someone that owns one can do it.

Or someone can send me one. I'm not willing to sell my n7 for what I consider a downgrade (battery and screen), especially when I just started working on deving on it lol

Sent from my Nexus 7 - JBSourcery 4.1
[Acer Iconia Tab A100] heX79:
I did make it, haven't used a auto-signer on the zip yet. Got a bit busy with family being over, for new years. So no I haven't attempted a flash yet; not that I believe this will actually root the device, as the updater-script/binary won't have been updated.

I'm willing to test/give any and all info you may need. I figured a decent starting point might be from the download on Acers page, but I could be wong. I'm completely ignorant on porting a recovery. There is a dev that wrote a tool kit for the a110, but it only rooted 4.1.1. On 4.1.2 all it's capable of (at this time) is unlocking the BL. Some method of rooting was patched (from what I've gathered so far) in 4.1.2, so the tool kit was using some form of (now patched) exploit.
[Acer Iconia Tab A100] heX79:
Update: Some better support in this thread: http://xdaforums.com/showthread.php?t=1915459

For anyone with the A110 who's interested, and stumbled here. Feel free to give support, it will show XDA how many of us own the A110, with the hopes of a dedicated thread for us to collaborate our efforts.
[Acer Iconia Tab A100] pio_masaki:
OK good luck guys

Sent from my Thrive - Kuroikaze B19
[Acer Iconia Tab A100] heX79:
pio_masaki,

Did you run into "loop" files in the /dev/block when using a custom recovery, during early builds for the A100?

Something is changing the devices when the custom recovery is loading, preventing us from even mounting /cache. The devices are listed as loop1, loop2, loop3 etc. Seem familier at all?
[Acer Iconia Tab A100] pio_masaki:
Yeah, just get ignored so they don't show up in recovery, you'll see them in android, though.

Iirc I saw its using initramfs or wtf ever Sammy uses, which will require more work on recovery inits.
[Android Software Development] osm0sis:
WIP Soon-to-be FAQ 😉

If you are reporting a problem with your device, please clearly state your device name and model/variant, attach a log, as well as provide a link to the image file.

Frequently Asked Questions (FAQ)

Q: Why don't my .img.lz4 and .img.tar files unpack, I tried renaming them to .img and everything?!

A: File extensions exist for a reason, they denote the format of a file. AIK supports .img files, but renaming things isn't the same as changing the file format, e.g. for .img.lz4 you actually need to unlz4 to get .img, and for .img.tar you actually need to untar to get .img.

Q: Why is the repacked .img smaller than the original, how will this even work?!

A: It's smaller because most of a partition dump is empty space, so AIK's repack is only the actual data inside. If you tried it you'd see it probably works fine (provided you haven't changed anything). Modern devices also AVBv2 sign images, which uses a bit of space at the end of the partition as well, but this must be done separately with the avbtool Python script from AOSP, and not all devices enforce this signing. You can also try the --origsize option if you want to ensure writing the new image blanks out the old (a fastboot bug on some old bootloaders).

Q: How come nothing works, there's nothing in bin / android_win_tools?!

A: That's because no binaries are hosted on GitHub so you can't just clone/download it and expect it to work. Only use the complete AIK package download links/attachments from the OP of this thread.

Q: This triggered some generic antivirus alert, what the f*ck, are you hax me?!

A: No. Antivirus heuristics recognize patterns in executables and try to guess what might be a threat because it's "similar" code. Some compression formats (especially the older UPX-compressed Go built sudo.exe AIK uses for Windows Administrator privilege requests) trigger these. Everything here's open source, I've been doing this for over 10 years and I'm an XDA Senior Recognized Developer, so you can either trust my track record, or build them yourself if you're that worried.

Q: Why is default.prop 0 bytes, why can't I edit it or prop.default and/or why my changes don't stick?!

A: Since project Treble brought system-as-root (SAR) - which is years now - default.prop is now a symlink to prop.default, and you can't open prop.default because the root / filesystem is in the system partition. In boot-as-recovery devices (no recovery partition) there is still a ramdisk containing another prop.default in the boot partition, but it's only used when booting to recovery so any changes will have no effect on booted Android.

Q: Why does it warn there's no ramdisk, it can't unpack it or something?!

A: It tells you there's no ramdisk because there's no ramdisk. Your device uses system-as-root (SAR), but doesn't have recovery in boot, so there's no boot.img ramdisk at all (0 bytes). See also the above answer for boot-as-recovery devices (no recovery partition).
[Android Software Development] dancer_69:
I just tried it with a recovery.img. I don't get any errors on unpacking/repacking process, but how to get the repacked recovery.img? When I run the repackimg.bat, I don't get any error, but it doesn't generate a new recovery.img.
[Android Software Development] dancer_69:
Thanks, seems that works fine now.

EDIT:

Generates new-image.img, but this recovery is unbootable. I tested it with the same recovery.img, without to change anything, just unpack/repack. The generated image is unbootable. Device just stuck on boot logo.
[Android Software Development] trevd:
Hi Buddy,

I like what you're doing here, cygwin dependencies are no good........ native on whatever platform you're using is the way to go.... with that in mind here's a mkbootimg compiled from the aosp source tree.using the MIN_GW toolchain, not a cygwin in sight :D

not tested it but should be alright for you.......I think I'll finish the job and smash it althought into one tool, saving f***king about., it'll will come in useful on linux too :D
[Android Software Development] osm0sis:
Crap. I'll take it down for now and do some testing. Might be a few days. Things were working over here with the few images I'd tried before. Maybe I messed something up once the scripts got more robust. Batch is an ugly way to do things. :(

Thanks for the help testing.

Thanks bro! I'll throw that in with the new (hopefully working) version. :good: :)

And hey go ahead and finish the job if you like. Coding is better than scripting so I'd be happy to get a mod to remove this thread once something better comes along.
[Android Software Development] osm0sis:
Alright people, sorry about those initial issues. OP updated with the new, fully working, v1.0. There was just some craziness in the one before with cpio not behaving like it should.

It's all Cygwin for now but trevd has been great and offered to port some things over properly while weeding out the issues, so expect a new release, completely dependency free and automated as always in the coming months, all thanks to him. :)
[Android Software Development] ZeRo2o9:
wow this is so helpful i spent a long time trying to mess with linux thank you!!! :good:
[Android Software Development] Goatshocker:
Hm, doesnt seem to work for me. I unpacked boot.img, repacked it (didnt change anything) and then flashed it with fastboot - resulted in a bootloop.

The boot.img before unpack/repack boots fine.
[Android Software Development] osm0sis:
Interesting. Worked for both dancer_69 and myself. Device info and image in PM please. :)
[Android Software Development] ZeRo2o9:
Yes i confirm it worked for me on htc vivid jellybean

Sent from my HTC Vivid 4G
[Android Software Development] trevd:
Hi Folks....

The boot loop maybe because ueventd /watchdogd in the sbin directory haven't been created, they are (normally) symlinked back to ../init, obviously windows doesn't support symlinks. a work around when using windows would be to copy-rename the /init to sbin/ueventd and sbin/watchdogd.

This is just "finger in the air" guessing but just something I've noticed :laugh:
[Android Software Development] osm0sis:
No that doesn't seem to be the issue here, though I think that's what the issue was when I was using the gnuwin32 cpio. I was also worried about permissions being set correctly but I haven't seen any issues with that yet either. I just made sure of both by unpacking and repacking the maguro CWM recovery image then flashing it to my device, and both symlinks and permissions are restored correctly in the filesystem. What's going on with Goatshocker's One S is a bit more bizarre.

Oddly enough, even just recombining the original zImage and ramdisk from split_img doesn't work for him, meaning it's either unpackbootimg, or more likely mkbootimg at fault. All the commandline variables match for the original and built images (cmdline, pagesize, base), and I've tried the Cygwin executable and the native one you posted, so it's leading me to believe there is something different about how images must be packaged for the HTC One S. Another One S user that can confirm would be good though. :(

Edit: One S testing was done with Fusion v4 and CM stock from the latest Dark Jelly -

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

http://xdaforums.com/showthread.php?t=1848100
[Android Software Development] trevd:
I do know some htc boot images they have an additional 256 byte header which you have to strip off in linux you do that with dd, like so

dd if=htcsen.img of=htcstrip.img bs=256 skip=1

I've just done this with an HTC Sensation stock boot image and it unpacked alright after that..... not sure about repacking though :eek:

You can check if an additional header is present by opening the boot image in an hex editor, A standard boot image starts with the android magic, which is the byte sequence

41 4E 44 52 4F 49 44 21

This spells ANDROID! in ascii text. If it doesn't you can normally strip the additional header without any problems.

Looking at the various boot images in my htc sensation backups it seems my CM boot images don't have the special header..

HTC do have some specialness going on with the S-ON/OFF business etc but I'd just be speculating If I said anymore as my knowledge of the htc boot sequence is limited.
[Android Software Development] osm0sis:
Getting reports that HTC One X and One X+ are also not working, so it must be some kind of newer HTC thing. When I get a bit of free time I'll compare the custom kernels and recoveries for those devices and/or fire some PMs off to the kernel devs to see if there's anything special I should know and if there's a way I can fix it. :good:
[Android Software Development] Goatshocker:
Well, "good" to hear its not just me who were having issues then :)
[Android Software Development] osm0sis:
Was looking into this again today and found a nice build.sh on the One S Fusion Kernel github..

The mkbootimg command does have an extra parameter:

mkbootimg --kernel zImage --ramdisk ramdisk.cpio.gz --base 80400000 --ramdiskaddr 81800000 --cmdline console=ttyHSL0,115200,n8 -o boot.img

Not yet sure if that ramdiskaddr is the magic difference or not. That ramdiskaddr parameter doesn't even exist in any win32 compile I've seen of mkbootimg. I just downloaded a few images (the Dark Jelly ones we tested before) to hexedit and compare. I'll post again shortly on that.
[Android Software Development] osm0sis:
Took a look with HxD and "ANDROID!" is present in all of them, so it's not the HTC header problem.

Since repacking the original ramdisk still wouldn't boot for the HTC One S in my tests with Goatshocker (which is crazy because it should all be exactly the same), I did just that with Fusion v3.2 and then ran a diff on the original and repack. Doing the same for a GN kernel produces zero differences, ie. the files are identical, but interestingly enough for the One S images there is a single difference, and it's in the header.

fv32-boot.xxd versus repack-boot.xxd:

0000000: 414e 4452 4f49 4421 0879 5100 0080 4080 ANDROID!.yQ...@.
0000010: b4a2 0200 0000 [color=blue]80[/color]81 0000 0000 0000 3081 ......[color=blue].[/color].......0.
0000020: 0001 4080 0008 0000 0000 0000 0000 0000 ..@.............
0000030: 0000 0000 0000 0000 0000 0000 0000 0000 ................
0000040: 636f 6e73 6f6c 653d 7474 7948 534c 302c console=ttyHSL0,
0000050: 3131 3532 3030 2c6e 3800 0000 0000 0000 115200,n8.......
----
0000000: 414e 4452 4f49 4421 0879 5100 0080 4080 ANDROID!.yQ...@.
0000010: b4a2 0200 0000 [color=red]40[/color]81 0000 0000 0000 3081 ......[color=red]@[/color].......0.
0000020: 0001 4080 0008 0000 0000 0000 0000 0000 ..@.............
0000030: 0000 0000 0000 0000 0000 0000 0000 0000 ................
0000040: 636f 6e73 6f6c 653d 7474 7948 534c 302c console=ttyHSL0,
0000050: 3131 3532 3030 2c6e 3800 0000 0000 0000 115200,n8.......

Same change with the TWRP recovery images for the One S (ville) and One X (evita). So somehow I believe that's our problem with certain HTC devices... No idea why such a thing would occur. I looked into S-ON a bit and it seems that's controlled from the radio, and would prevent the image from being written, so it shouldn't have to do with that either. Perhaps it has to do with that extra ramdiskaddr parameter somehow affecting the header. :confused:

I could write an extra batch file that flips that byte as a workaround, but I'd prefer to actually figure out why it happens and fix that..
[Android Software Development] osm0sis:
OP updated with the workaround zip, instructions in the 2nd post. Tested and working fully, many thanks to Goatshocker for the assistance. :good:

Any ideas or leads on why this single byte difference would occur are welcome, but in the meantime the workaround should make this "universal" again. :)
[Android Software Development] ars0n:
Hello sir! Thank you first of all for this program, used it on my gnex...

Not sure if anyone has posted up a LG g2 recovery, but I tried to unpack and nothing is in the ram disk folder, however, the split img folder does populate.

if you need the image or any other info please let me know! Would love to get this working for lg g2 verizon! =D
[Android Software Development] osm0sis:
Yes sir, image please and thanks. ;)
[Android Software Development] ars0n:
twrp image here ... thank you!!

https://drive.google.com/?authuser=0#folders/0BwAukw6XsW-0WTd0YkloZk16QzQ
[Android Software Development] osm0sis:
Hmm the ramdisk offset reported is weird, and so the ramdisk extracted is seen as just "data" and can't be extracted. I'll see what I can figure out. Thanks. :good:

BOARD_KERNEL_CMDLINE console=ttyHSL0,115200,n8 androidboot.hardware=g2 user_debu
g=31 msm_rtb.filter=0x0
BOARD_KERNEL_BASE 00000000
BOARD_PAGE_SIZE 2048
BOARD_KERNEL_OFFSET 00008000
BOARD_RAMDISK_OFFSET 0f8131f0
BOARD_TAGS_OFFSET 04800000
BOARD_DT_SIZE 366592

Unpacking ramdisk to "/ramdisk/" . . .

Compression used: data
Error!
[Android Software Development] ars0n:
you the man!! thank you! Ill keep posted!
[Android Software Development] Smart-X:
Waiting for 1.8

I tried to use this tool to unpack and repack TWRP 2.6.3.4 for my Nexus 5 without changing anything. Everything seemed right but when I flashed the repacked img to Nexus 5 it showed a black empty screen. I hope v1.8 can solve this issue soon.
[Android Software Development] osm0sis:
Check your PMs and let me know. :)

I took a look with HxD and I think the issue might be that it's a Loki image. I'd seen that mentioned in the CWM commits before but haven't run into the images yet. I found this resource on how to mod them so I'll see where that gets us.

Edit: Took a look at their scripts but they don't do anything special to extract only to flash, so I'm not sure what the deal is. There is definitely a bunch of weird data in between the usual sections though. I'll see if I can find some kind of unpack guide for this device that I can adapt, but if it can't be generalized and the changes to the android standard are too great than I'm going to have to leave it unsupported. :(

Edit 2: dsixda had a recent pull request to his extract ramdisk script that added lz4 compression for stock LG G2 support, but there doesn't seem to be anything else special there either, and I've had lz4 working for awhile now.

More loki info from the TWRP thread: http://xdaforums.com/showthread.php?t=2449670

I honestly think the real problem is that they pre-lokified them before distribution instead of letting people lokify them before flashing.
[Android Software Development] ars0n:
isnt loki something you do after you have the image? So, couldnt I get an un-lokid image, edit, then loki?If i am even thinking of that correctly..

I appreciate the help man, thank you so much!
[Android Software Development] osm0sis:
Exactly what I was thinking but I haven't seen a way to "un-loki" an image mentioned yet. If you see something let me know and I'll keep searching tomorrow or the next day. :good:
[Android Software Development] trevd:
[MENTION=4544860]osm0sis[/MENTION] I've not got a pm but I did get the mention , hence ...

I've been busy the last week so I haven't done much at all ....... Also I compiled it with MinGW on linux and just created ( and tested ) the Makefile afterwards ...

At a quick guess have you converted the Makefile to have Windows Line Endings - if not , try that , if you have then it's not that lol

I'll have a look myself later, although if you've got any error output ... well you know the drill :)

ta
[Android Software Development] Smart-X:
Yeah! v1.8 works perfect on my Nexus 5 now! Great job, man!
[Android Software Development] osm0sis:
Thank you sir! I also got confirmation it works on the Note 3, so I think I'll go ahead and release soon since the Vega is such a rare piece of hardware around these parts. I'll just make sure there's no way I can get the G2 working first so it'll be a few more days. :good:

Would you mind helping me out with this also:

http://xdaforums.com/showpost.php?p=47653254&postcount=281

PM me if you have any questions. :)
[Android Software Development] hanzoo1504:
Tôi đã thử, nhưng không thành công. My phone pantech vega A830L
[Android Software Development] osm0sis:
Translation: I tried, but without success.

I will message you the link for v1.8 to try in the morning. I am currently working. :)
[Android Software Development] hanzoo1504:
My God, I thank you very much. In my country there is no one to share this knowledge. I hope you can help me this job. I'm not good at English. We wish you pardon
[Android Software Development] garynych:
sorry , i do not speak english, and online translate very bad :(

question:

Android.Image.Kitchen.v1.6-Win32.zip

understand boot.img from nexus 5?

assembled and disassembled without any errors, but the phone with the new kernel will hang on the logo
[Android Software Development] osm0sis:
v1.8 needed. Please wait. I will release it soon.