PowerMinded

When i was using apktool to decompile an apk i got the following error:

The problem:

The solution:

Download the source of APKTool

1. git clone git://github.com/iBotPeaches/Apktool.git
2. cd Apktool
   Bold lines need to be added:
   Edit: Apktool/brut.apktool/apktool-lib/src/main/java/brut/androlib/res/data/value/ResValueFactory.java

Edit: Apktool/brut.apktool/apktool-lib/src/main/java/brut/androlib/res/data/ResTypeSpec.java

Then continue building steps, copied from (https://ibotpeaches.github.io/Apktool/build/):

1. For steps 3-5 use ./gradlew for unix based systems or gradlew.bat for windows.
2. [./gradlew][gradlew.bat] build shadowJar – Builds Apktool, including final binary.
3. Optional (You may build a Proguard jar) [./gradlew][gradlew.bat] build shadowJar proguard

The new apktool.jar will be in (Apktool/brut.apktool/apktool-cli/build/libs/apktool-cli-all.jar)

I was switching to another android 7.1 rom on my Galaxy Note 3 and when switching without a full data wipe the Phone service stopped working, the phone told there was no simcard available… the fix seems to be quite easy but i couldnt find it on the web.. So i thought i’ll share it so others can fix this issue easily 🙂
The thing with upgrading without a data wipe is that databases which already exist should be compatible with the apps in the rom… looks like some column was missing in my old database.

The following error occured:

 

Remove the old database and restart your phone, connect your phone and use adb to remove the old database.

After restarting the phone everything is working as expected again and simcard is being recognized again.

 

These days many linux distribution use hybrid ISO images.

Hybrid disc formats include the ability to be read by different devices, operating systems, or hardware. In the past, one example of this use was for a disc that supported both Microsoft Windows and Macintosh installations from a single disk image (by containing several file systems).

The problem when writing these iso images to an usb disk is that the usb flash drive needs to be recognized as harddisk. Hybrid iso’s add a MBR (Master Boot Record) in the first 512 bytes of the ISO image and pads the end of the image with zeros, so that the size of the final image is a multiple of 1M. Thus created MBR will have one partition listed, starting at offset zero (by default) and ending at the end of the hybrid image.

When booting a dell Poweredge with the auto option it recognizes the flash disk as a floppy disk, to prevent this the type of the flash disk has to be set to “Hard Disk” instead of auto.

Set the emulation type to “Harddisk” from “Auto” to make a hybrid iso image bootable from usb flash drive.

Also be sure to have the “USB Controller” set to type “On with BIOS Support”

 

And now have fun with your bootable usb FLASH drive and your poweredge!