yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Q&A, Help & Troubleshooting] supac:
Do you guys mind sharing your gmd configuration?
[Galaxy Note II Q&A, Help & Troubleshooting] kenmok963:
you set your own gesture to operate different command.

For example, i swipe from left to right by using two fingers can open the recent app page..

it really depends on your own choice.
[Galaxy Note II Q&A, Help & Troubleshooting] supac:
So I am trying to see what gestures you guys have. Comparing to mine.
[Galaxy Ace S5830i General] carlos9545:
anyone can help me to split the S5830MWHLE3 firmware to multipackage? i dont know how to use splitFUS, please i really need this multipackage :(

http://www.hotfile.com/dl/177161036/b186ea1/S5830MWHLE3_S5830MCOLLE1_COL.zip.html

I tried to use it but i cant understand plz.
[Galaxy Ace S5830i General] Qeemi:
PETITION to split a firmware? WTF? Is a joke?
[Galaxy Ace S5830i General] carlos9545:
here in my country petition is "peticion" in spanish is formally ask for something. FORMALLY

sorry if im bad , here is the download link

http://www.4shared.com/zip/mfoBm2-5/S5830M_WHLE3_COLLE1_WHLE2_by_S.html
[RAZR i Android Development] turl1:
I've seen you haven't been able to unpack the boot images so I investigated a bit on this "weird format" Moto used. This is what I could figure out by looking at the image and the bootstub code Motorola released:

0x00000000 kernel CMDLINE, filled with zeroes where unused
0x00000400 bzImage size
0x00000404 initrd size
0x00000408 SPI UART suppression
0x0000040B SPI type (0: SPI0, 1: SPI1)
0x00001000 future stack for bootstub (?)
0x00002000 actual bzImage start

On the boot image I grabbed from the root post, using the awesome "hexdump" tool we can see at 0x400

60 a8 46 00 90 6c 1a 00

Which means (remember x86 is Little Endian) bzImage size 0x0046A860 (~4.5MB) and initrd size of 0x001A6C90 (~1.65MB)

So let's go to the practical side:

0x00002000 + 0x0046A860 = 4638816

$ dd if=razr_i_boot.img of=ramdisk.cpio skip=4638816 bs=1
$ zcat ramdisk.cpio|cpio -i

gzip: ramdisk.cpio: decompression OK, trailing garbage ignored
8927 blocks
$ ls
android.fstab dev init.moto.usb.rc init.sc1.rc init.wifi.rc ramdisk.cpio system ueventd.smi.rc
charger init init.moto.usb.sh init.sdcard1.rc init.xmm.rc res ueventd.goldfish.rc xbin
data init.goldfish.rc init.nfs.rc init.sdcard2.rc lib sbin ueventd.rc
default.prop init.moto.rc init.rc init.sdcard.rc proc sys ueventd.sc1.rc

$ dd if=razr_i_boot.img of=bzImage skip=8192 count=4630624 bs=1
$ file bzImage
bzImage: Linux kernel x86 boot executable bzImage, version 3.0.8-g229e199 (hudsoncm@il93lnxdroid52) #1 SMP PREEMPT Sat Sep, RO-rootFS, root_dev 0x806, swap_dev 0x4, Normal VGA

Ta-da! Unpacked. It wasn't that hard really :p

Now, is there interest on a tool to repack/unpack these images? I don't own the phone (and probably won't, no $$ :() but if there's enough interest I can make one, it should be relatively easy.

EDIT: Okay, so I wrote a pair of tools to unpack existing images and package new images, you can get them at

https://github.com/turl/razr-i-boot-tools

Just run "make" to build the tools, the usage is really simple

$ ./pack
Usage: ./pack <valid image> <bzImage> <ramdisk> <output>

From left to right, an already existing boot image (to copy bootstub from, it could be built from source on the future), the kernel, the gzipped cpio ramdisk and the output filename

$ ./unpack
Usage: ./unpack <image to unpack> <bzImage out> <ramdisk out>

From left to right, the image you want to unpack, and the destination files for bzImage and ramdisk. You can then unpack the ramdisk with something like

$ mkdir ramdisk-unpack
$ cd ramdisk-unpack
$ zcat ../ramdisk.cpio.gz|cpio -i

And then repack it with something like

$ find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz
[RAZR i Android Development] mattlgroff:
Making it look so simple ;)

I really appreciate you taking the time to look at this, especially since you don't even have the device. I definitely have interest in a tool if at all possible. I'd donate and encourage others to as well :)
[RAZR i Android Development] sparkyman216:
I agree with everything he said. Awesome job
[RAZR i Android Development] turl1:
Okay, so I wrote a tool to package images, check the edit on the first post and let me know how it works. I'll make another one to unpack current images when I get some more time :)
[RAZR i Android Development] mattlgroff:
Been working all day yesterday to get up and running on Linux again, time to redouble my efforts and try a new distro so I can get packin'!

EDIT:Got everything set up besides ramdisk I believe. First attempt is progress, instead of error booting into fastboot it sticks on the boot logo, then reboots and loops that. I'm pretty sure its because I did ramdisk wrong but we'll see if anyone else can get it further.

File includes ramdisk folder, boot.img, and my compiled bzImage. http://d-h.st/Cyn
[RAZR i Android Development] turl1:
What did you use to repackage the ramdisk? Something like this should work

$ cd ramdisk
$ find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz

Then use the generated 'newramdisk.cpio.gz' when calling pack; something like

$ ./pack boot.img bzImage newramdisk.cpio.gz newboot.img
[RAZR i Android Development] mattlgroff:
Getting a 4.6 MB boot.img with this, trying to boot now.
[RAZR i Android Development] turl1:
Yes, a smaller boot.img is to be expected, the dumped one you guys got has garbage on its tail :)
[RAZR i Android Development] mattlgroff:
Same bootloop issue, looping the bootlogo and phone reboots :(
[RAZR i Android Development] turl1:
Well, it turns out I fail when programming on the late AM :p

https://github.com/turl/razr-i-boot-tools/commit/34f618b5cb2d6fb4b4c7d8affb194113a0b11270

Update/reclone your tools repo, rebuild it and try again. Rebuild your ramdisk image too, just in case the tool corrupted it.
[RAZR i Android Development] mattlgroff:
Updated tools, rebuilt tools, rebuilt ramdisk....

6.5 MB newboot.img now.

Boot animation....

Booted!

Where's your donation link? :)
[RAZR i Android Development] turl1:
Awesome! I just wrote the unpack tool by the way, same repo. Check the first post for more info and let me know if you have any issues with it.

I also completed the "donate to me" box on the XDA profile for those looking for it :)
[RAZR i Android Development] ReeSilva:
OMG, I sure won't make use of it but I know how important it is to build Custom Recovery and Custom Roms sooo I'll make a donate soon as I can.
[RAZR i Android Development] zizouth:
Make boot.img

Hi,

I can't manage to make the boot.img with my compiled kernel for Razr I. Anyone can make the boot.img for me please :victory:

Thank you
[RAZR i Android Development] Robbilie:
"Direct booting from floppy is no longer supported...Please use a boot loader program instead...Remove disk and press any key to reboot..."

WTF?! :D

open your bzImage with a hex editor, the first lines :D
[RAZR i Android Development] Daniel 9999:
Hai mattlgroff, I have switch from your homemade 40002 to 31006 with RST & then OTA auto update to 40002 & then do root & CWM but now the kernel version is older (Sept 2012), so can i copy the recovery.signed in 31006 & change the file name to recovery.img & put into the CWM folder & ADB/Fastboot.

Can i have this better matt-desktop #1 too.Thks.
[RAZR i Android Development] mattlgroff:
Its not better, worse actually because things are broken.
[RAZR i Android Development] Daniel 9999:
However,thanks Mattlgroff, For you & all info.,I take your 40002 boot.img & Fastboot flash boot boot.img after RSDlite 31006 & got back the newest Nov,2 kernel. It really run very smooth & fast ( I overwrite your ADB file to a newer ADB from android-sdk folder as dont know why ADB devices cant read/see).Cheers.
[RAZR i Android Development] rickwyatt:
mat have you got this to complied because iv only got cgywin or could you build my boot.img to unlink data/media
[RAZR i Android Development] mattlgroff:
http://batakang.com/ftp/incoming/boot.img

Having some troubles with this Jellybean boot.img. Anyone want to take a stab at it?
[RAZR i Android Development] hiemanshu:
Yeah, I am going to take a look at it. Care to make an english fastboot for us? :)

Update:

I was able to unpack using the tools provided.

hiemanshu@hiemanshu-desktop:~/src/smi$ file kernel

kernel: Linux kernel x86 boot executable bzImage, version 3.0.34-gc6f8fd7 (hudsoncm@il93lnxdroid80) #1 SMP PREEMPT Thu Ja, RO-rootFS, root_dev 0x816, swap_dev 0x3, Normal VGA

hiemanshu@hiemanshu-desktop:~/src/smi$ file ramdisk

ramdisk: ASCII cpio archive (SVR4 with no CRC)
[RAZR i Android Development] mattlgroff:
Cool, good to know it was just me being silly :)

and the english FB is uploading now.
[RAZR i Android Development] planktoid:
better late than never.

Just to make sure... I posted our mkbootimg.sh tool in this thread last year. OP.

https://forums.motorola.com/posts/8cf473f2df
[RAZR i Android Development] Omar-Avelar:
I've been using that one :)
[RAZR i Android Development] zainifame:
[MENTION=4370056]mattlgroff[/MENTION] [MENTION=4040302]turl1[/MENTION] help sir, try to unpack boot.img Lenovo K900 but have a output "0 byte" file size, how to fix that's sir?
[RAZR i Android Development] mattlgroff:
I'd wager the kernel offset is different from the RAZR i but I have no working knowledge of finding it for new devices. Best of luck!
[RAZR i Android Development] zainifame:
but in the source k900 is support sir?
[RAZR i Android Development] zainifame:
please help sir [MENTION=4370056]mattlgroff[/MENTION]
[RAZR i Android Development] Hazou:
Compile the source with that flag set ;)
[RAZR i Android Development] zainifame:
i have compile intel-boot-tools from K900 device tree but i got same problem sir, "0 byte" size of both file extracted?

try unpack kernel & recovery cm11 k900 btw,

and also i use ur tools to unpack boot image, but showing "premature archive"? try all tools unpack but same problem i got :(
[RAZR i Android Development] Hazou:
My unpack tool work only on the razr.

Can u upload an example boot.img or recovery and I will see how it is at my end
[RAZR i Android Development] zainifame:
this sample for kernel & recovery sir, thanks before :D
[RAZR i Android Development] osm0sis:
Well it's been a year, and the most I've come up with are some possible values for imgtype, based on another fork of turl's original tools that were modified for the ZTE Grand X (https://github.com/pm-cz/zte-gxi-boot-tools) but seems to be otherwise pretty much the same in formatting as the Leno K900.

I've updated the above info post, and will put out another call to [MENTION=4040302]turl1[/MENTION], [MENTION=1813976]shakalaca[/MENTION], and also [MENTION=5941423]pm-cz[/MENTION] to see if they might be able to help make a more generalized tool using it.

I've also found the AndImgTool by And_PDA (http://4pda.ru/forum/index.php?showtopic=496786&st=0#entry24790314) from 4PDA (basically the Russian XDA), and it seems to have support for more than one kind of $OS$ image, but again, not all (the 728 byte signing block variant isn't supported), not to mention it's Windows only. Unfortunately the author has refused to release the sources multiple times when asked.. even though I imagine he probably used turl's work at some point..

Edit: My Google-Fu is still pretty decent after all I guess, the output from AndImgTool provided some clues and I just found this which appears to give the entire header layout, straight from Intel: http://git.yoctoproject.org/cgit/cg...on-bsp/recipes-bsp/u-boot/u-boot-osip.inc#n66

And post #262-3 here I found show fully what the imgtype ("attribute") means: https://prohardver.hu/tema/op3n_dott_tablet_melyviz/hsz_251-300.html

Finally, some more interesting insights into the creation of the $OS$ boot.img from the osip .c files here, which Intel refers to as "stitching":

https://github.com/STS-Dev-Team/android_device_intel_kboot/tree/aosp-404/flash_stitched

and an actual stitching bash script!:

https://github.com/STS-Dev-Team/android_device_intel_kboot/blob/aosp-404/in/stitch.sh

update_osip.h and update_osip.c:

https://github.com/tank0412/aosp_device_asus_a500cg/tree/master/libintelprov

mfld_osimage.py:

https://github.com/tank0412/aosp_de...ter/libintelprov/releasetools/mfld_osimage.py

Seems like pm-cz, [MENTION=4821597]social-design-concepts[/MENTION] and [MENTION=2472806]vampirefo[/MENTION] already dug into this a fair bit a few years back. I'm surprised they never got together and ironed out an open source tool. :confused: :fingers-crossed:
[RAZR i Android Development] zainifame:
There's one more tools to unpack intel boot image, here https://drive.google.com/file/d/0BwEWY6gMvYOedDV1LVJUVkN2dms/view
[RAZR i Android Development] zainifame:
here https://github.com/arizaini/intel_bootimage_tool all intel tool i have push to my repos, that's all i can find on entire forum and site
[RAZR i Android Development] osm0sis:
Found this today: https://github.com/mirek190/x86-android-5.0/tree/master/vendor/intel/support

Windriver doesn't seem to provide the device tree files anymore (there used to be some leaked FTP info that indicated you had to get them from a rep), but I believe that's where vendor_intel_support comes from.

Shame that And_PDA from 4PDA has still never open sourced xImgTool or AndImgTool after all this time, he's definitely using and/or derived from lots of open source code, and it keeps his tools trapped on Windows only. :rolleyes::mad:

As of now I've just started working on updating the official Python mboot.py to support all variants, and provided that goes well I'll consider rewriting it all in C. :good:
[RAZR i Android Development] osm0sis:
[MENTION=4040302]turl1[/MENTION], [MENTION=1813976]shakalaca[/MENTION], [MENTION=5941423]pm-cz[/MENTION], [MENTION=4821597]social-design-concepts[/MENTION], [MENTION=2472806]vampirefo[/MENTION], [MENTION=6906625]zainifame[/MENTION]

https://github.com/osm0sis/mboot_py :cowboy:

Would be good if people could let me know if it works. :fingers-crossed:

Edit

: [MENTION=1813976]shakalaca[/MENTION] and I have been chatting and he's been helping immensely; mboot.py is now updated to work properly with all known Intel OSII/OSIP Android image types and respect all parts of the 'mystery spec' I detailed above. :victory::highfive:

I'll start out by mentioning [MENTION=7223862]KonstaT[/MENTION] here, and if that doesn't work I'll ping him on Twitter. Thanks for the heads up [MENTION=7914507]Palm Trees[/MENTION]! :good:

Edit 2

: Reached KonstaT on Twitter. His devices are all standard Android bootimg, so unfortunately he doesn't have any help for us.
[RAZR i Android Development] osm0sis:
Alright, time for me to unsubscribe here now that I've rewritten mboot.py in c: https://github.com/osm0sis/mboot :cowboy:

Intel OSIP format will be supported in the next release of my Android Image Kitchen (AIK v3.5) project and added to AnyKernel2 (AK2) shortly after that.

Find me in those threads if anyone needs anything!
[RAZR i Android Development] zainifame:
@osm0sis sorry sir mentioning you... just wondering few years ago i give the sample image for lenovo k900 i forgot the sample is signed or unsigned but seeing your research i assume the sample i give you is unsigned... so... i just want give the proper file here to research with signed file contain $OS$ on all header... because lenovo k900 only have 4.2 and 4.3... thank you sir
[RAZR i Android Development] osm0sis:
Thanks, yes it was unsigned. Should work already though, did you try repacking it with mboot/AIK?
[RAZR i Android Development] zainifame:
Sorry for late respond... Already try unpack & repacking it was smooth but i'm not able to flash it to the phone to test boot or not because my lenovo k900 dont know where

Try it with all signed image from all android version lenovo k900 421, 422, 43

On all signed image bootstub was 4kb and yes all intel from android 43 below was 4k bootstub and 44 above was 8k bootstub... But i didnt find this 8 byte 'BD 02 BD 02 BD 12 BD 12' hex on all lenovo image signed or unsigned but on some intel phone with ICS android that hex is present but not all phone... Just curious about that...

And this old... but nice explanation

android_device_dell_venue3x40-common/mkosimage at cm-13.0 · venue3x40-dev/android_device_dell_venue3x40-common

Common device configuration for Dell Venue 3740/3840 - venue3x40-dev/android_device_dell_venue3x40-common

github.com

This old one too

GitHub - alan-shen/sign_stitch_intel: A tool for stitch and signing intel atom's boot images

A tool for stitch and signing intel atom's boot images - alan-shen/sign_stitch_intel

github.com

Almost forgot... I try unpack 'bos_signed' from razr i jellybean and failed after seeing with hexedit the image have royax signature 480 byte the rest was same like boot and recovery i guess

intel_android/Medfield_(Z24xx)/Motorola_RAZR_i_XT890/9.8.2I-50_SML-29_Retail_BR_SIGNED_SLATAMUnlk_USASMI01RETBRLA022.0R_S1FF_CFC_fb/bos_signed at master · arizaini/intel_android

Contribute to arizaini/intel_android development by creating an account on GitHub.

github.com

I dont know what is 'bos_signed' file but i guess its same like lenovo k900 'pos.bin'

I have all sample image from all intel platform smartphone android here:

GitHub - arizaini/intel_android

Contribute to arizaini/intel_android development by creating an account on GitHub.

github.com

I'm interest on something like this but have no knowledge... Trying to understand but nothing...
[RAZR i Android Development] zainifame:
hi @osm0sis try with all sample image i have here so this the result on screenshot:

file:

motorolla razr i "bos_signed"

zenfone 5 "droidboot.img"

edit: using latest AIK tools
[RAZR i Android Development] osm0sis:
Some of those are bootloader files, so likely no kernel or ramdisk to unpack
[RAZR i Android Development] zainifame:
there is kernel and ramdisk inside both file above... here:

zenfone 5 android L firmware
24 4F 53 24 00 00 01 AB | boot
24 4F 53 24 00 00 01 23 | recovery
24 4F 53 24 00 00 00 25 | droidboot
| |
after change it to 01 AIK can unpack and repack the droidboot.img

RAZR i android JB firmware

after remove 480 byte "RðŸåx" signature from bos_signed AIK can unpack and repack the bos_signed see screenshot bellow
[RAZR i Android Development] osm0sis:
I'll take a look when I can to see if there's some improvements to be made to the tools 👍
[RAZR i Android Development] zainifame:
thanks :)
[RAZR i Android Development] wairrior:
Thanks for this post. I can build and download boot.bin for my ramos i9 z2580 pad now. The boot.bin is signed by intel tool isu. Since mainline linux no longer supports SFI, can we do anything with bootstub, pxe loader or droidboot to load zImage with a device tree? ARM SoC supports zImge appended with dtb. Can we do the same thing on this x86 platform?
[Galaxy S III General] swy05:
I've seen some similar reports on the internet but, anyone else having this problem as well?

Updated the S3 (international version) to Jellybean yesterday and everything seems fine.

One thing I noticed is that the volume through the earphones are very very low. I've had to crank the volume all the way up and it's still not as loud as it was before I updated to Jellybean. It makes the music extremely quiet and it actually sounds worse bass/clarity wise.

:(
[Galaxy S III General] xukaisheng:
I noticed the same thing here. Just flash sound hack.
[Galaxy S III General] tmantanner4:
Syiah kernel and stweaks
[Galaxy S III General] JJEgan:
No lower sound for me on multiple JB roms .

Factory reset or flash firmware again .

jje
[HTC One V] shubhamchamaria:
RESERVED!!
[HTC One V] cammykool:
4.1 or 4
[HTC One V] aaronrw:
DL link is bad.....

sentfromybrain
[HTC One V] shubhamchamaria:
Click go anyway....
[HTC One V] shubhamchamaria:
4.1 lite version...
[HTC One V] aaronrw:
Wi-Fi is borked while using stock kernel. Other than that freaking smooth for a sense build! Thanks for showing primoc some love

sentfromybrain
[HTC One V] shubhamchamaria:
You need custom kernel....and flash the modules...you can push the bcmdhd.ko from the stock rom...
[HTC One V] Curiousn00b:
Shub, if your not going to PM me back, don't bother asking for files needed.

You couldve atleast added me to credits.
[HTC One V] shubhamchamaria:
I could but all the stuff you provided were already there in the earlier cdma converter for amazing sense and therefore, if you could fix MMS I would add you to the credits...
[HTC One V] Demo3827:
MMS fixer and CDMA converter

i fix it already =}
[HTC One V] shubhamchamaria:
Thanks babes :D

I will make another Converter and add you to the credits...
[HTC One V] Curiousn00b:
Still files modified by me.

And you can still PM back, apart from when you want something.
[HTC One V] shubhamchamaria:
Ya....and also I am sorry for not replying back to you....I just have too many pm 's to reply to
[HTC One V] salvy512:
Not being a pain or anything but the accelerometer is off.. according to the "compass" app it doesn't work at all. (CDMA) if you want a logcat let me know..
[HTC One V] salvy512:
uhh.. ok I fixed the accelerometer didnt really test so I don't know HOW well it works but if your turn it left or right or normal it works..

sorry didnt have time to make a zip but here are the files
[HTC One V] Curiousn00b:
Our phone doesn't have the compass tools, according to HTC.
[HTC One V] salvy512:
I know that but I turned the phone sideways and it didn't change orientation.. I only mentioned the compass thing because the app says the accelerometer isn't present which we do have.. but I could be wrong about the orientation. I don't remember where it didn't flip so it could have just been a place where the phone refuses to change orientation
[HTC One V] edwinrodriguez810:
Hey thanks for the Rom but what happen to lockscreen animation theme ?
[HTC One V] shubhamchamaria:
I posted in my GSM Thread...forgot to here...Flash this: http://shubham.viperbravo.info/LockScreens.zip
[HTC One V] shubhamchamaria:
New CDMA Converter...Added credits in updater-script to whosoever wanted it.....Also I have tried to fix camera by using some libs from a CDMA rom
[HTC One V] robaho:
Does mms work? First post implies it doesn't.
[HTC One V] shubhamchamaria:
Try and flash the latest converter and then tell me....I don't have a cdma device so can't confirm it.
[HTC One V] mjw029:
tring your latest fix and now my phone wont boot. does not get bast the HTC build screen. DID the same thing with deleing framework for amzaing sense rom as well
[HTC One V] Demo3827:
SuPrimo v10.0 MMS converter

This is a other fixer for SuPrimo v10.0 ONLY if you keep using the wrong ones you will keep haven problem please as alway try do a FULL wipe fresh FLASH rom always flash the KERNEL and always ASK before do some that you arent sure WE are FAMILY all togother for help each others

Fixers
[HTC One V] JASONMAKS:
Where are the kernales? I don't understand that. Because I'm trying amazing sense and WiFi is my only problem.
[HTC One V] Demo3827:
ICS kernel

This is the ICS Kernel that im Using wThis one work great with: CM9 - AMAZING SENSE - STOCK ROM - SENSE 4.1 or ANY CDMA ICS ROM :good:
[HTC One V] salvy512:
just a little problem.. cdma doesn't boot I think because sensor.primoc.so file upload with 0bytes and idk why so here goes a new one..
[HTC One V] salvy512:
Yo, if you need any testers let me know, I have CDMA and am on my computer 95% of my day.. my gtalk is sfugarino512@gmail.com
[HTC One V] Demo3827:
Why everything is working on my phone without this file? I have CDMA from VirginMobile and I see too many people haven problem with this and otheres Roms :(
[HTC One V] salvy512:
did you flash the new converter? my phone didn't boot up :(
[HTC One V] dafzuka:
I love this rom so far but I can't get auto rotate to work. Anyone else having this issue?
[HTC One V] salvy512:
this is an easy fix and actually I believe he fixed it.. it's basically move the sensor file sensor.primoc.so from stock rom /hw to this rom..

and some others in /bin /etc/permissions and
[HTC One V] Demo3827:
TESTED

I didnt Flashed... because I make it and when i tested before give to him was working fine on my phone
[HTC One V] RFrancis:
When will you be updating this?
[HTC One V] Demo3827:


On his website... i guess he will update the link soon