yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 4 Original Android Development] daavvis:
OK so I'm using the kernel from Samsung, and trying to build a kernel specific device tree table with your script, and I keep getting ==> found 0 unique dtbs, and no output file... What am I doing wrong lol

Edit: I'm getting there.... Def progress... Cross your fingers....
[Galaxy Tab 4 Original Android Development] sub77:
you need either the custom_mkbootimg.mk or a prebuild dtb.
[Galaxy Tab 4 Original Android Development] daavvis:
I ended up getting everythig set up, thanks to [MENTION=3034891]gr8nole[/MENTION] tab 3 7" device files, [MENTION=5153662]Android-Andi[/MENTION] sepolicies, and a lollipop updated gps.h, and I got mokee (an ASOP based ROM) to build almost completely, then it failed at creating the userdata.img, because of the data folder, it says lol... I'm gonna try and build clean...
[Galaxy Tab 4 Original Android Development] daavvis:
[MENTION=4021423]ketut.kumajaya[/MENTION], OK I'm ridiculously close, at the end of the build, its trying to make userdata.img, but it fails because it 'need size of filesystem'...

I'm sure this is a derp/brain fart I'm having, but what am I missing... ? Having a total nube moment lol...

My girlfriend is having surgery this morning so I'll be at the hospital waiting for her and trying to figure it out via github and my faithful tab 2, anyone with any ideas would be a great help :)

My device tree:

https://github.com/daavvis/device_samsung_degaswifiue

Edit: yup, I'm dumb sometimes, I think I found what I was looking for..... Derp....
[Galaxy Tab 4 Original Android Development] ketut.kumajaya:
[MENTION=4503423]daavvis[/MENTION] partition size = partition block count * 1024, you can check block count from /proc/partitions.

EDIT: Don't take this too serious, girlfriend first :good: I hope she will get better soon.
[Galaxy Tab 4 Original Android Development] daavvis:
Thanks buddy :).. She is getting a ovary and felopian tube removed.... I gotta do something in the waiting room, or I'll go nuts lol... just updated my device tree with partition sizes, installed busybox, and ran fdisk -l /dev/block/mmc0p* and it gave me the byte size, is that correct?
[Galaxy Tab 4 Original Android Development] daavvis:
OK, well it builds, but it won't flash...

I get:

Detected filesystem ext4 for /dev/block/platform/soc.2/by-name/SYSTEM

Mount: failed to mount /dev/block/platform/soc.2/by-name/SYSTEM at /system :invalid argument

then twrp reboots,

When I boot back into twrp, as soon as it loads I get a red "E: Unable to mount '/system'

After i restore back to my backup, everything is OK... I'm totally missing something...
[Galaxy Tab 4 Original Android Development] g_ding84:
Have you tried using :

/dev/block/platform/soc.2/mmcblk0p15 for /system

/dev/block/platform/soc.2/mmcblk0p16 for /data

/dev/block/platform/soc.2/mmcblk0p10 for kernel

Just some ideas.
[Galaxy Tab 4 Original Android Development] daavvis:
Interesting idea....

Looks to me like once it unmounts /system, it can't find it again, prob because I'm missing something, or its an issue with twrp, either way I think its related to this thread...
[Galaxy Tab 4 Original Android Development] :
D,

maybe this will help, you should be able to reference the block device directly

instead of the by device way in twrp and cwm builds

/dev/block/mmcblk0p??

this is the layout for sm-t230/nu/31

~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all
print all
print all
Model: MMC 008GE0 (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 4194kB 6291kB 2097kB MRD
2 6291kB 8389kB 2097kB MRD_BK
3 8389kB 10.5MB 2097kB MEP2
4 10.5MB 31.5MB 21.0MB ext4 EFS
5 31.5MB 46.1MB 14.7MB RESERVE
6 46.7MB 48.2MB 1573kB LOKE2ND
7 48.8MB 50.3MB 1573kB LOKE1ST
8 50.3MB 67.1MB 16.8MB PARAM
[COLOR="Red"]9[/COLOR] 67.1MB 83.9MB 16.8MB RECOVERY
[COLOR="Red"]10[/COLOR] 83.9MB 101MB 16.8MB KERNEL
11 101MB 126MB 25.2MB MODEM
12 126MB 143MB 16.8MB ext4 NVM
13 143MB 153MB 10.5MB ext4 HIDDEN
[COLOR="Red"]14[/COLOR] 153MB 363MB 210MB ext4 CACHE
[COLOR="Red"]15[/COLOR] 363MB 2587MB 2224MB ext4 SYSTEM
[COLOR="Red"]16[/COLOR] 2587MB 7817MB 5230MB ext4 USER

as long as fstab format/version are correct.

also with lollipop you can return to the tried and true packaging scheme

by removing --block from one of the files in source.

Naturally the actual file name/location escapes me atm but i'll post it here when i find it.

okay it's from either

tools/releasetools/ota_from_target_files

first, so that any changes made to the system partition are done
using the new recovery (new kernel, etc.).
[COLOR="Red"]--block[/COLOR]

Generate a block-based OTA if possible. Will fall back to a
elif o == "--block":
OPTIONS.block_based = True
elif o in ("-b", "--binary"):
OPTIONS.updater_binary = a

or from core/Makefile

@echo -e ${CL_YLW}"Package OTA:"${CL_RST}" $@"
$(hide) MKBOOTIMG=$(MKBOOTIMG) \
$(OTA_FROM_TARGET_SCRIPT) -v \
[COLOR="Red"]--block \[/COLOR]
-p $(HOST_OUT) \

it's been a while, just backup the originals and test it out

ps-this is more for my reference so i don't have to keep looking for it :eek:

m
[Galaxy Tab 4 Original Android Development] JayDream:
For the life of me I cant get into my bootloader to unlock it. I've tried adb, manual button combo, and nothing. Its like it doesnt even have a bootloader.
[Galaxy Tab 4 Original Android Development] :
in terminal run

su

reboot download

m
[Galaxy Tab 4 Original Android Development] osm0sis:
This is all great work here [MENTION=4021423]ketut.kumajaya[/MENTION]!

Have these tools been confirmed working for repacks yet? Most posts in this thread seem hung up on building whole ROMs and custom dtbs, but I saw no testing of just the bootimg tools. I was thinking about trying to incorporate them into my Android Image Kitchen by using the "unknown" header entry (pagesize in the standard) as the indicator to switch to using your degas-bootimg tools. :)

Seems like fairly safe logic, since 02000000 would be insane as a pagesize. ;)
[Galaxy Tab 4 Original Android Development] Matt07211:
Well I'm using a slightly modified fork of this, https://github.com/AKuHAK/pxa1088-mkbootimg

And I can say that unpack and repack boot.img is fine, repack of a recovery is fine (unpack a recovery screws up, believe the offsets is off by a little bit), the dtb tool works. Overall it functions and does what it is needed, you just need to know the correct command to put everything back together correctly.

I was also caught off guard by the page size initially as well, but yea...
[Galaxy Tab 4 Original Android Development] Anticolick:
Hi guy when i give this command i see this error pls help me

root@ubuntu-512mb-fra1-01:~/degas-mkbootimg-tools# tools/degas-unpackbootimg -i boot.img -o boot
-bash: tools/degas-unpackbootimg: Permission denied
root@ubuntu-512mb-fra1-01:~/degas-mkbootimg-tools#
[Galaxy Tab 4 Original Android Development] osm0sis:
Hmm.. Seems like a good fork for wider support of these deviations from the standard, but the different signature size issue would need to be resolved. Is the creator of that fork on XDA?

chmod 755 degas-mkbootimg degas-unpackbootimg

;)
[Galaxy Tab 4 Original Android Development] Anticolick:
Now i see no such file or directory ?
[Galaxy Tab 4 Original Android Development] osm0sis:
.. silly question, but did you actually compile them first?
[Galaxy Tab 4 Original Android Development] Matt07211:
Sorry for a late reply, been offline for a while....

Now, yes the creator of the fork is here in XDA, pinging [MENTION=7770482]akuhak[/MENTION].

Now onto the signature size problem, if I remember correctly, the signature size is at the end of a boot.img, the start of the signature is "SEANDROIDENFORCING", so you mearly have to find the corresponding hexadecimal values corresponding to the word and go to end of file, this may get cumbersome if it's unpacking a DD of the whole boot partition (as it's got all the extra zeros on the end) instead of a boot.img from a firmware package (has no extra padding).
[Galaxy Tab 4 Original Android Development] osm0sis:
That footer would be in addition to the signature I think.. judging by the diff:

-** | signature | 256 bytes
+** | signature | 272 bytes

If that's all that's responsible for the size difference then I can easily handle it separately and keep the degas value.. though the unknown 0x02000000 also differs so my logic to determine which tools are required is now back to square one..
[Galaxy Tab 4 Original Android Development] Matt07211:
Not sure if it's in the boot.img header, but I believe the value is there. The Samsung xCover3 is little-endien, which threw me off and confused me before I realised it was little-endien. Keep that in mind.
[Galaxy Tab 4 Original Android Development] osm0sis:
Interestingly enough, TWRP's builds for degas and xcover3ltexx both use the 03000000 value for unknown (where degas was originally 02000000) and presumably it still works. Maybe it's a version number for Samsung's bootimg deviation, and isn't actually used anywhere else.

[MENTION=7770482]akuhak[/MENTION], TWRP's similarly modified degas source is here: https://github.com/TeamWin/android_device_samsung_xcover3ltexx/tree/android-4.4/tools and [MENTION=912474]Dees_Troy[/MENTION] didn't bother with changing the signature size, so that's a good sign for that question.

Edit: Ah wait, Dees didn't change sigsize in the bootimg.h documentation, but it is changed in unpackbootimg:

Chris@Homebase ~
$ diff degas-mkbootimg/bootimg.h twrp-pxa1088/bootimg.h

Chris@Homebase ~
$ diff degas-mkbootimg/mkbootimg.c twrp-pxa1088/mkbootimg.c
124c124
< unsigned unused = 0x02000000;
---
> unsigned unused = 0x03000000;

Chris@Homebase ~
$ diff degas-mkbootimg/unpackbootimg.c twrp-pxa1088/unpackbootimg.c
212c212
< byte* bsig = (byte*)malloc(256);
---
> byte* bsig = (byte*)malloc(271);
214,216c214,216
< fread(bsig, 256, 1, f);
< total_read += 256;
< fwrite(bsig, 256, 1, r);
---
> fread(bsig, 271, 1, f);
> total_read += 271;
> fwrite(bsig, 271, 1, r);

That should be 272 like in akuhak's from what I've seen.

I'll see if I can combine the two with some logic somehow, ideally I'd use the probable version number of unknown to differentiate, but TWRP's changes (using 03 for degas) break that idea.
[Galaxy Tab 4 Original Android Development] osm0sis:
[MENTION=6318002]Matt07211[/MENTION] other than SEANDROIDENFORCE is the signature required at all to boot? I was right that the signature size difference between "degas" and "xcoverltexx" is just that string.

If you just leave the signature out, does it work? TWRP certainly doesn't have any signature on their images for these devices.
[Galaxy Tab 4 Original Android Development] Matt07211:
String is there to stop the annoying "Device is not SEANDROIDENFORCING" at boot. Not sure what happens if you don't have it on. I could test it for you tonight if you want. You should be able to just echo SEANDROIDENFORCING onto the end of the boot.img to achieve the same effect.
[Galaxy Tab 4 Original Android Development] osm0sis:
Exactly. I'm mostly wondering if the other 256 bytes that [MENTION=4021423]ketut.kumajaya[/MENTION] first noted here (and come after the SEANDROID line in [MENTION=7770482]akuhak[/MENTION]'s) have any effect when missing.

Please do test and let me know. I'm fairly confident I can add this to my image kitchen. Just trying to resolve the differences in the two versions and pare it down to what's necessary. :) :highfive:
[Galaxy Tab 4 Original Android Development] Matt07211:
If anything I believe it may just be from their private signing key. I'll test tonight, so that's a few hours away. Hope you can wait ;)
[Galaxy Tab 4 Original Android Development] Matt07211:
Okay I've flashed results are below:

- Boot, with full signature: Boots fine without any warnings (including the annoying "The kernel is not SEANDROID ENFORCING). Perfect.

- Boot, with SEANDROIDENFORCING echoed onto the bed of boot.img: I forgot to echo the needed characters, and only realised my mistake once I booted into my window's partition. Doesn't matter any way, it would have still booted (Read below for details)

- Boot, without any signature: Boots perfectly fine as well, only difference is that you've got the annoying "The Kernel is not SEANDROID ENFORCING​", it's a purely cosmetic thing, phone still boots up :)

Basically, the phone should boot up either way and it'll only affect the boot up cosmetics/look.
[Galaxy Tab 4 Original Android Development] osm0sis:
Perfect! My kitchen already handles SEANDROID footers, so I'll just leave out --signature support for pxa1088-mkbootimg and all should be well.
[Galaxy Tab 4 Original Android Development] osm0sis:
Since [MENTION=4021423]ketut.kumajaya[/MENTION] and [MENTION=7770482]akuhak[/MENTION] appear to have stepped away from xda, here's my updated fork:

https://github.com/osm0sis/pxa1088-mkbootimg/commits/master

It mainly resolves that TODO item to support both Galaxy Tab 4 7.0 (degas) and Galaxy Xcover 3 (xcoverltexx) in the same utility by having unpackbootimg check the signature for the added SEANDROIDENFORCE string, adjusting the output signature size accordingly; mkbootimg now just accepts whatever file you throw at it for a signature. :good:

I made some effort to also support signatureless files (TWRP's, for example) by checking that there is enough data left in the file for a signature to be possibly present before attempting to dump it - all the previous iterations of the tool would just dump garbage data in this case. Padding from a raw image dump would make an empty "signature" file but that's fine since technically it isn't needed anyway. ;) :cowboy:

I'll be adding support for it to my Android Image Kitchen v2.8 (and likely be unsubscribing from this thread at that point), so if anyone has any issues or questions either ask in my AIK thread or @ mention me here. :)
[Galaxy Tab 4 Original Android Development] Matt07211:
First of all, thanks for updating the tool, secondly, before you leave this thread, I've got a few questions;

1) With the makefile changes am I able to compile it by itself or does it still require some/certain android headers that you get an in android compile environment?

2) saw this when looking through the commits, "-board" name, and "-kerneloff" offset dumping. What do these do exactly?

Looks like "kerneloff" derives the kernel Offset from the Android Header and save the data to a file, is that correct?

Not really sure what "board" does but it looks like it writes data to a file.

Either way I'll test it against different boot.imgs, and recovery.imgs and all that and I'll post an issue on GitHub if something doesn't work.
[Galaxy Tab 4 Original Android Development] osm0sis:
1) Yes, should work with all standalone compilers now that I've included that and the headers/libs. I've made Cygwin and Linux builds for example. For Android NDK note you'll want to use a newer API level if you care about building dtbtool, e.g. android-9 doesn't contain the getline definition it needs, but android-21 does.

2) --kernel_offset and --board are just the other two things mkbootimg accepts on its command line (and akuhak did a really good job bringing mkbootimg up to date), so should be dumped along with ramdisk_offset, second_offset and tags_offset for completeness. kernel_offset is the standard and board is empty (also normal) on these devices so nothing to worry about.

Yes, no worries, please do test and let me know. You can @ mention me here or post on my AIK thread if you come across anything. I've currently got a Galaxy Core Mini 4G firmware downloading to make​ sure all works there as it's the other Marvell PXA1088 board phone I knew about.

Edit: Yup. Works great on Samsung Galaxy Core Mini 4G (SM-G3568V) images as well, which also have 02000000 as an unknown value and match the Tab 4 7.0 layout, furthering my theory that it's a layout version number. :)
[Galaxy Tab 4 Original Android Development] akuhak:
Just want to say: great work ))
[Galaxy Tab 4 Original Android Development] osm0sis:
Same to you, sir! :D

AIK v2.8 should be out early next week. :good: :highfive: :cowboy:
[LG Optimus 4X HD] triple_m:
can any budy help me, i´ve got a lg 4x hd and at night for no reason he spends 20% or higher in battery and i dont no why
[LG Optimus 4X HD] Buuzzaa:
Install this program and see what is causing the wakelock...

Also is always good to use greenify to hibernate applications.

PS: Both applications require root.

Best Regards.
[LG Optimus 4X HD] triple_m:
thanks but that got me no where it still does the same thing

my charger makes a strange noise like a buzz

maybe its the charger or the battery it self
[LG Optimus 4X HD] DerMoonEclipse:
The charger always make scary sounds ...

The same cautious if phone is off?
[LG Optimus 4X HD] triple_m:
still no solution for the problem, its strange the battery that he consumes over night
[LG Optimus 4X HD] Saenchai:
Well, probably depends also how old your mobile is... I mean, after 4 years the battery can have lost capacity. Mine also needs around that over night, with Wifi and all Syncs and pushes activated. But theres nothing to do in my case i reinstalled firmware several times, its just gets old. Dunno but i could imagine you have the same "problem"...
[LG Optimus 4X HD] n3mvn:
What rom are you using?

You should try to flash stock rom.

Find them here lg-phone-firmware.com
[LG Optimus 4X HD] Rudjgaard:
we need battery logs..
[Xperia Z2 Q&A, Help & Troubleshooting] daymon:
I have unlocked bootloader and kernel CWM 6.0.4.7

Can I flash stock .402 without kernel.sin and do not relock the bootloader?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] thierryIT:
Dears,

Moving around for 4 hours .... Reading forums .... Didn't find solution yet.

I have a new Samsung GT-i9195 LTE from the box, I have followed the procedure to install on this device CWM to install at the end CM-11.

I have the same pb if I am using the windows procedure (Odin) or the Mac procedure (heimdall), when I reboot on recovery mod, I can see CWM with all the menu (reboot system now, install zip, wipe data ....) ... But if I select, as example "advanced" nothing happen, same for "install zip" and all the rest .....

Any ideas ?

Thx
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Aronuser:
try phils touch recovery it's cwm too, just another design
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] MarkAndroid.UK:
It might be corrupted, I would try flashing with Odin again and/or downloading it from elsewhere. I had no problem running that version for a long time apart from the select button sometimes changed its mapping from the 'home' to 'power' button!

I now use and highly recommend TWRP. I shan't be going back to CWM.
[LG Optimus L9 P760, P765, P768, P769] j.han:
I'm currently using a P769 model with JB, and it's never been rooted. I remember the phone was 100% charged when I looked at it three days ago and I didn't use it at all the day after that, but when I tried to use it yesterday it didn't turn on and it hasn't been responding since (I did try to charge it a few times). Actually the exact same thing happened a few months ago but it fixed itself in a few hours, but this time it's been two days and I hope it doesn't mean my phone is completely bricked :( The main thing is that I want to avoid doing a factory reset if at all possible since I made the mistake of not creating a backup.

I've tried some recovery tools (LG Mobile Support along with third-party) but the problem is that nothing seems to recognize my phone as connected. Weirdly enough, when I plug it in it without the battery, it connects and disconnects continuously (the device manager refreshes itself every 3-4 seconds); I've updated the USB drivers and everything, but nothing seems to work. Not sure what the Recovery Mode key combination is but I'm assuming the phone has to boot first for Recovery Mode to even be accessible anyway, so that's probably out of the question. However I have tried Vol+, power and Vol+, power, home, and nothing happens.
[LG Optimus L9 P760, P765, P768, P769] Euphemus:
To make the recovery software recognize your phone,you must put it in S/W mode by disconnecting your phone,taking out the battery,reinserting the battery and then,while holding the volume+ button,plugging it into your computer(keep holding volume+ until the screen says S/W just to be safe).At least that's what I always did.:)
[LG Optimus L9 P760, P765, P768, P769] j.han:
Hmm... I tried that, and nothing happens on my phone, but I get a popup from the system tray on my computer that says "USB device not recognized: The last USB device you connected to this computer malfunctioned, and Windows does not recognize it" which appears and disappears repeatedly. It appears that no software can recognize the phone as connected at this point. I think it might be a random battery failure but I don't know how to tell D:

The thing is all I really need out of the phone is the contact and app data if possible, which is why I'm so hesitant to do a hard reset :| I read around and I'm assuming what I should do is to flash the bootloader but I'm not sure how to go about doing that since I'm getting zero response from the phone itself.....

UPDATE: Tried a hard reset anyway, but still nothing from the phone. I attempted fastboot, however, I don't know how to make it work since "OMAP4430" does appear under TI Devices in Device Manager plus an "Unknown USB [device failed enumeration something something]" under USB Controllers, but that's it.... nothing appears under Other Devices, which seems to be where the bricked phone should show up. adb doesn't seem to recognize it either.
[LG Optimus L9 P760, P765, P768, P769] danro28:
i have the same problem with my lg p760.

any solutions?
[LG Optimus L9 P760, P765, P768, P769] foreverman:
you had a solution for this problem ?
[HTC One X] kinder771:
Hi,

I've installed that zip : http://xdaforums.com/showthread.php?t=2337762

Cause I didn't see it wasn't for the One X, now I'm blocked on the logo when booting...

I installed the cancel.zip via recovery but still nothing...

I re-flashed the boot.img of my ROM but nothing.

What to do please ?? I can't reinstall my ROM and wipe my data :((

Thanks in advance !
[HTC One X] Mr Hofs:
Why can't you install the rom. You have to install the rom again. Just make sure you dirty flash it (that means no wipe)
[HTC One X] kinder771:
Ok I did it but now I get "HTC Sense stopped", "Google Play Stopped", constantly, I can barely and hardly use my phone...

Could flashing the gapps package fix that ??

Thx for your answer !
[HTC One X] kinder771:
Ok I think the problem comes from the low internal memory (after reflashing ROM 2 times), I got only 200 mb free out of 5 gb

I deleted a lot of apps and moved a lot to sdcard and still got nearly 4 gb of "other" in internal memory...

I even tried CleanMaster but it couldn't free more than 100 mb.

What to do ????
[HTC One X] Mr Hofs:
What rom. If it needs gapps you have to install that too again !
[8525, TyTN, MDA Vario II, JasJam General] armedmetallica:
hi,

reg hacks section says to use total commander for reg edits.

i installed it, but don't see how to do it.

thanks!
[8525, TyTN, MDA Vario II, JasJam General] hanmin:
Go to your top directory (e.g. the "\" directory), at the top, you should have a "\\", click on it. And then you will see dirs like "ftp", "LAN", "registry". Click on the "registry" to modify your (duh) registry using total comm.
[8525, TyTN, MDA Vario II, JasJam General] armedmetallica:
Found it, thanks!