Database Develop

[Q] problem installing kinecto bundle for wifi calling

having trouble installing kineto bundle. Nexus one cm6.1.0, using intersectraven's kernel, and 5.12 radio. I have looked through several pages of this thread with not really any similar issues. here is the clockwork recovery report on why it won't install. any suggestions? phone storage is at 105 mb left and 1 gig on sd card don't understand why it says no space left on device?
Copying files...
minzip: Extracted file "/system/build.prop"
minzip: Extracted file "/system/etc/init.d/04modules"
minzip: Extracted file "/system/lib/libganril.so"
minzip: Extracted file "/system/lib/libhtc_ril.so"
minzip: Error writing 4096 bytes from zip file from 0xbec51ae4: No space left on device
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.
minzip: Error extracting "/system/lib/libkineto.so"
calling command set_perm_recursive
calling command set_perm
calling command set_perm
calling command set_perm
calling command set_perm
E:Can't chown/mod /system/lib/librilswitch.so
(No such file or directory)
E:Failure at line 7:
set_perm 0 2000 0644 SYSTEM:lib/librilswitch.so
Installation aborted.
Failure at line 3:
install_zip SDCARD:/download/kineto-n1-bundle-v1.0-signed.zip

[Q] REvolution oneclick root help

I was unsuccessful in my search so I am posting my question in this QA forum.
The original thread was in the Revolution Android Development subforum but I am unable to post on that thread as I am a useless noob.
I have a LG Revolution Android version 2.3.4
I followed the directions as posted:
How Do I Root and Install CWM?:
1) Download zip and extract
2) Install drivers if not already installed
3) Click root.bat and watch the magic!!!
I unzipped and was able to update drivers
I was sure to have the USB debugging on (before connecting).
I also set the the USB connection to Internet connection
I clicked root.bat and the following line is repeated almost every other line
'adb' is not recoginized as an internal or external command
At the very end it says:
[*] root complete, enjoy!
[*] Press any key to continue..
When I try to open Titanium backup or Barnacle it says I do not have root
A few other things I'm noticing is that I keep getting usb device not recognized when connecting the phone via usb.
I also noticed a LG software upgrade assistant in my PC tray that I cannot remove.
Any help would be greatly appreciated.

With adb not recognized it sounds like you just ran the root.bat without extracting the zip extract the zip to a folder the click on root.bat
Sent from my VS910 4G using xda premium

Yes, I believe I just unzipped the file and clicked the root.bat. Where do I extract the file to?
Thanks for your response.

Doesn't really matter you just need to extract it you can make a new folder and extract to that
Sent from my VS910 4G using xda premium

Beamer, that certainly did the trick.
Confirmed rooted with access to Barnacle and Titanium.
Now I need to figure out the Gingervolt process. Only about 75 more pages to read through.

Lol if you have clockwork mod recovery just download gingervolt put it on your sd card boot into recovery hold power button down and volume down at the same time until you get to the black screen asking to wipe data or something like that hit the power button to confirm this will not wipe your data but will boot into recovery once in recovery use the volume keys to navigate and power button to select then follow all of the directions in the 1st post every step is important.
Sent from my VS910 4G using xda premium

atlsud said:
Beamer, that certainly did the trick.
Confirmed rooted with access to Barnacle and Titanium.
Now I need to figure out the Gingervolt process. Only about 75 more pages to read through.
Click to expand...
Click to collapse
I appreciate you actually reading instead of instantly asking to be spoon fed!

atlsud said:
I was unsuccessful in my search so I am posting my question in this QA forum.
The original thread was in the Revolution Android Development subforum but I am unable to post on that thread as I am a useless noob.
I have a LG Revolution Android version 2.3.4
I followed the directions as posted:
How Do I Root and Install CWM?:
1) Download zip and extract
2) Install drivers if not already installed
3) Click root.bat and watch the magic!!!
I unzipped and was able to update drivers
I was sure to have the USB debugging on (before connecting).
I also set the the USB connection to Internet connection
I clicked root.bat and the following line is repeated almost every other line
'adb' is not recoginized as an internal or external command
At the very end it says:
[*] root complete, enjoy!
[*] Press any key to continue..
When I try to open Titanium backup or Barnacle it says I do not have root
A few other things I'm noticing is that I keep getting usb device not recognized when connecting the phone via usb.
I also noticed a LG software upgrade assistant in my PC tray that I cannot remove.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
how would one go about downloading
1) Download zip and extract
2) Install drivers if not already installed
3) Click root.bat and watch the magic!!![/I][/B]

AssumedDarkness said:
how would one go about downloading
1) Download zip and extract
2) Install drivers if not already installed
3) Click root.bat and watch the magic!!![/I][/B]
Click to expand...
Click to collapse
Here:
http://forum.xda-developers.com/showthread.php?t=1348557

Follow this post, it's as simple as that.
http://forum.xda-developers.com/showthread.php?t=1326542&page=54
It's the easiest to understand for me & worked flawlessly.
Ed

please help
AssumedDarkness said:
how would one go about downloading
1) Download zip and extract
2) Install drivers if not already installed
3) Click root.bat and watch the magic!!![/I][/B]
Click to expand...
Click to collapse
no im coming up with this and im stuck
Removing Trash and Installing Root Files
rm failed for /system/tmp/su, No such file or directory
rm failed for /system/tmp/busybox, No such file or directory
rm failed for /system/tmp/Superuser.apk, No such file or directory
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
rmdir failed for /system/tmp, No such file or directory

AssumedDarkness said:
no im coming up with this and im stuck
Removing Trash and Installing Root Files
rm failed for /system/tmp/su, No such file or directory
rm failed for /system/tmp/busybox, No such file or directory
rm failed for /system/tmp/Superuser.apk, No such file or directory
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
rmdir failed for /system/tmp, No such file or directory
Click to expand...
Click to collapse
Copy and paste the whole thing to pastebin and drop a link in here and I will look at it. That small portion could be normal, I would just have to look at the rest to know for sure.
Sent from my VS910 4G using xda premium

I am trying to root my Revolution 2.3.4 ( I am a complete newb)
How will I know it is rooted?
This is what showed up when it was finished:
Rooting the LG Revolution
Tool Built by mtmichaelson
Exploit Built by the Revolutionary Team
Rooting
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Pushing Zergrush
1279 KB/s (22281 bytes in 0.017s)
Running Zergrush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x40121cd4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd255f1 0xafd39067
[*] Poping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
Removing Trash and Installing Root Files
rm failed for /system/tmp/su, No such file or directory
rm failed for /system/tmp/busybox, No such file or directory
rm failed for /system/tmp/Superuser.apk, No such file or directory
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
rmdir failed for /system/tmp, No such file or directory
3639 KB/s (22364 bytes in 0.006s)
3778 KB/s (828156 bytes in 0.214s)
2550 KB/s (843503 bytes in 0.323s)
Removing Trash
Finished Rooting!!!
Press any key to continue . . .
Is that normal?
Is there anything else I need to download on the phone to get rid of bloatware? I am not sure really how to do this.
Thanks!

AprilRevo said:
I am trying to root my Revolution 2.3.4 ( I am a complete newb)
How will I know it is rooted?
This is what showed up when it was finished:
Rooting the LG Revolution
Tool Built by mtmichaelson
Exploit Built by the Revolutionary Team
Rooting
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Pushing Zergrush
1279 KB/s (22281 bytes in 0.017s)
Running Zergrush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x40121cd4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd255f1 0xafd39067
[*] Poping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
Removing Trash and Installing Root Files
rm failed for /system/tmp/su, No such file or directory
rm failed for /system/tmp/busybox, No such file or directory
rm failed for /system/tmp/Superuser.apk, No such file or directory
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
rmdir failed for /system/tmp, No such file or directory
3639 KB/s (22364 bytes in 0.006s)
3778 KB/s (828156 bytes in 0.214s)
2550 KB/s (843503 bytes in 0.323s)
Removing Trash
Finished Rooting!!!
Press any key to continue . . .
Is that normal?
Is there anything else I need to download on the phone to get rid of bloatware? I am not sure really how to do this.
Thanks!
Click to expand...
Click to collapse
You are now rooted, I would install CWM and do a back up before doing anything else though.
Sent from my VS910 4G using xda premium

Do I get CWM from the same file as the root?
If so, I did run the "CWM Recovery" from that file. Is that what you mean?
I also see that I am rooted, I downloaded the titinium backup and was able to uninstall a lot of Verizons app that I never use.
Anything else good to do with a rooted Revo?

Gingervolt it !!!! 2.0 is real good & removes all of the bloat. If you find yourself missing anything from the stock that youo want, get the "Stock app installer" & reload what you want...
\Ed

[DEV TOOLS] - Pack & Repack Boot.img Files - for Windows USERS

Plagiarism will not be tolerated on XDA-Developers:
http://forum.xda-developers.com/showpost.php?p=35640046&postcount=36

Reserved - Possible Updates Using Cygwin

I'm gonna take this one just in case as well

Thx for the app but i have an empty ramdisk folder...and all of the ramdisk files can't created or newer or same age version exists...cydwin won't let me copy the log...im using huawei not SE phone..if it has something to do!! But i can see the contents at boot.img-ramdisk.gz

Thanks but please mirror to other filehoster because mf is buggy on my phone
Sent from my WT19i using xda premium

$ ./extractboot boot.img
./extractboot: ./split_bootimg.pl: /usr/bin/perl: bad interpreter: Permission denied
./extractboot: line 17: cpio: command not found
gzip: ../../boot.img-ramdisk.gz: No such file or directory
what i missed here?
edit: opps. missed the REQUIRED packages. testing again.

$ ./extractboot boot.img
Android Magice not found in ./boot.img/ Giving up.
gzip: ../../boot.img-ramdisk.gz: unexpected end of file
cpio: premature end of archive
Any help with this error? I am trying to split and edit a custom CM9/ICS boot.img

very useful tool, thanks

This isn't working for me on my htc evo 4g lte. I am unpacking the stock boot.img and then repacking it with NO changes and get bootloops.

your image png should not exceed 20KB and your logo.rle should not exceed 60kb Otherwise you will almost always bootloop

stef67000 said:
your image png should not exceed 20KB and your logo.rle should not exceed 60kb Otherwise you will almost always bootloop
Click to expand...
Click to collapse
I didn't change any pngs, logos, or anything. I simply unpacked, repacked, and flashed.

maxdamage2122 said:
I didn't change any pngs, logos, or anything. I simply unpacked, repacked, and flashed.
Click to expand...
Click to collapse
Check on the way your kernel should be build.. Ours use as base 0x20 but yours may change..
Sent from my LT18i using Tapatalk

jimbo77 said:
Check on the way your kernel should be build.. Ours use as base 0x20 but yours may change..
Sent from my LT18i using Tapatalk
Click to expand...
Click to collapse
Is there a way to check without the source? Source for our kernel isn't released yet.

I've tried to unpack the last boot.img from cm9 RC2 to get the new cwm 6.x but I have an issue
Code:
$ ./extractboot boot.img
Page size: 2048 (0x00000800)
Kernel size: 3229308 (0x0031467c)
Ramdisk size: 1789254 (0x001b4d46)
Second size: 0 (0x00000000)
Board name:
Command line:
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
./extractboot: line 17: cpio: command not found

I use this way http://forum.xda-developers.com/showthread.php?t=1477845
how to change spash screen http://forum.xda-developers.com/showthread.php?t=1140406

You need to download the cpio package through cygic in order to have it fixed..
Sent from my SGS3... Yes I have it!!!!

jimbo77 said:
You need to download the cpio package through cygic in order to have it fixed..
Sent from my SGS3... Yes I have it!!!!
Click to expand...
Click to collapse
thanks

thomas.raines said:
$ ./extractboot boot.img
Android Magice not found in ./boot.img/ Giving up.
gzip: ../../boot.img-ramdisk.gz: unexpected end of file
cpio: premature end of archive
Any help with this error? I am trying to split and edit a custom CM9/ICS boot.img
Click to expand...
Click to collapse
Hello,I'm having the same error with CM9/10 ICS/JellyBean kernel boot.img,there are chances it comes from the kernel itself as it appears to be or should we better look into our configuration?

helo, i repacket doomlord kernel v22 and when im trying to flash it i got this error :
FAILED (remote: Wrong range:0x10008000-0x103202d7. Ok:0x00200000 - 0x03dfff)
It's somethink about size of kernel and "fake size maker" file, but i dont know how to fix it.

So I pulled a working one apart and replaced the kernel with the compiled one.
Code:
[email protected] ~
$ cd /boot
[email protected] /boot
$ ./extractboot boot.img
Page size: 2048 (0x00000800)
Kernel size: 4463500 (0x00441b8c)
Ramdisk size: 372027 (0x0005ad3b)
Second size: 0 (0x00000000)
Board name:
Command line: console=ttyHSL0,115200,n8 androidboot.hardware=qcom loglevel=0
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
2881 blocks
[email protected] /boot
$ ./packboot
Using base address 0x40200000
Using command line 'console=ttyHSL0,115200,n8 androidboot.hardware=qcom loglevel=0'
No errors
I then put it back together and I'm getting the boot.img is like half the original size (even tho the kernel files were pretty close to almost deadon the same size) and when I try to send to boot I get this
Code:
>fastboot boot boot_new.img
downloading 'boot.img'...
OKAY [ 1.168s]
booting...
FAILED (remote: incomplete bootimage)
finished. total time: 1.168s
This is for a Pantech Burst (p9070) if that helps at all
Original boot.img
New repacked boot.img

[HOW TO] Extract kernel image from the Samsung Galaxy S5 VZW firmware

If you interested in extracting the kernel image from the Samsung Galaxy S5 ROM, you should follow the following steps.
This is was tested with the G900VVRU1ANCG_G900VVZW1ANCG_VZW stock ROM firmware.
The first is extracting the files from the ROM firmware file, this is explained in many places and won't be covered here.
Extract the boot.img to some directory, using the Android unpackbootimg utility:
Code:
unpackbootimg -i boot.img -o boot/
After extracting the boot.img file you will usually end up with the following file list:
Code:
boot.img-base
boot.img-cmdline
boot.img-pagesize
boot.img-ramdisk.gz <- this includes the root (/) files, like init*.rc and SELinux policy files
boot.img-zImage <- compressed image of the Android Linux kernel
Next step will be extracting the compressed kernel image from the zImage file. The Android kernel is a self-extracting compressed file, while different devices use different compression methods. While looking at the file contents using hex editor, you can see the decompression code at the beginning, and then at some point the compressed data begins. The compressed image begins where you find the LZO magic header.
Code:
static const unsigned char lzop_magic[9] = {
0x89, 0x4c, 0x5a, 0x4f, 0x00, 0x0d, 0x0a, 0x1a, 0x0a
};
Save the data from the LZO magic header to the end of the file with the zImage.kernel file name.
This firmware and kernel are using LZO compression, and there is an easy to use utility called lzop that is used for the decompression of the file. Just run the following command to decompress the kernel from the zImage.kernel file:
Code:
lzop -d -c zImage.kernel > zImage.kernel.decompressed
And now you have the decompressed kernel for the device ready for exploration, which is also attached to this post.
Note:
I've tried using different scripts that do the job, including galaxys2_kernel_repack and http://forum.xda-developers.com/showthread.php?t=901152 but both failed while extracting the kernel image, although were able to extract the begin position for the LZO compression header.

But it does trip KNOX after flashing, doesn't it?
roman.blachman said:
If you interested in extracting the kernel image from the Samsung Galaxy S5 ROM, you should follow the following steps.
This is was tested with the G900VVRU1ANCG_G900VVZW1ANCG_VZW stock ROM firmware.
The first is extracting the files from the ROM firmware file, this is explained in many places and won't be covered here.
Extract the boot.img to some directory, using the Android unpackbootimg utility:
Code:
unpackbootimg -i boot.img -o boot/
After extracting the boot.img file you will usually end up with the following file list:
Code:
boot.img-base
boot.img-cmdline
boot.img-pagesize
boot.img-ramdisk.gz <- this includes the root (/) files, like init*.rc and SELinux policy files
boot.img-zImage <- compressed image of the Android Linux kernel
Next step will be extracting the compressed kernel image from the zImage file. The Android kernel is a self-extracting compressed file, while different devices use different compression methods. While looking at the file contents using hex editor, you can see the decompression code at the beginning, and then at some point the compressed data begins. The compressed image begins where you find the LZO magic header.
Code:
static const unsigned char lzop_magic[9] = {
0x89, 0x4c, 0x5a, 0x4f, 0x00, 0x0d, 0x0a, 0x1a, 0x0a
};
Save the data from the LZO magic header to the end of the file with the zImage.kernel file name.
This firmware and kernel are using LZO compression, and there is an easy to use utility called lzop that is used for the decompression of the file. Just run the following command to decompress the kernel from the zImage.kernel file:
Code:
lzop -d -c zImage.kernel > zImage.kernel.decompressed
And now you have the decompressed kernel for the device ready for exploration, which is also attached to this post.
Note:
I've tried using different scripts that do the job, including galaxys2_kernel_repack and http://forum.xda-developers.com/showthread.php?t=901152 but both failed while extracting the kernel image, although were able to extract the begin position for the LZO compression header.
Click to expand...
Click to collapse

I tried that and was given a warning of trailing bytes by `lzop`. Later when i do a `file` command on the resulting uncompressed file, it is not a vmlinux ELF image, rather it is a data file. How are we able to repack this image back into zImage? Any advise is appreciated thanks.

What i do if i have boot.img-kernel and boot.img-kernel_offset?

DGKG said:
What i do if i have boot.img-kernel and boot.img-kernel_offset?
Click to expand...
Click to collapse
The boot.img-kernel is your zimage file

What Source you used for Unpack?
Can you share link for you Scripts? or can you provide link to scripts for unpacking and repacking Note 9 Exynos Kernel?
Thanks

[Q] Problem Installing Roms

I've tried installing various custom roms (and versions) and they all seems to fail. The only successful flashes I've managed have been stock roms from this page. This is the log from when I attempted to install CM 10.2 in TWRP 2.6.6.3:
Code:
Starting ADB sideload feature...
failed to open driver control: No such file or directory
failed to open driver control: No such file or directory
sideload_service invoked
adbd exiting after successful sideload
failed to open driver control: No such file or directory
Restarting adbd...
failed to open driver control: No such file or directory
Installing '/data/media/0/sideload.zip'...
Checking for MD5 file...
I:Cannot find file /data/media/0/sideload.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
script aborted: assert failed: getprop("ro.product.device") == "m7" || getprop("ro.build.product") == "m7" || getprop("ro.product.device") == "m7ul" || getprop("ro.build.product") =="m7ul"
assert failed: getprop("ro.product.device") == "m7" || getprop("ro.build.product") == "m7" || getprop("ro.product.device") == "m7ul" || getprop("ro.build.product") == "m7ul"
E:Error executing updater binary in zip '/data/media/0/sideload.zip'
Anyone recognise these errors?

robtherobot101 said:
I've tried installing various custom roms (and versions) and they all seems to fail. The only successful flashes I've managed have been stock roms from this page. This is the log from when I attempted to install CM 10.2 in TWRP 2.6.6.3:
Code:
Starting ADB sideload feature...
failed to open driver control: No such file or directory
failed to open driver control: No such file or directory
sideload_service invoked
adbd exiting after successful sideload
failed to open driver control: No such file or directory
Restarting adbd...
failed to open driver control: No such file or directory
Installing '/data/media/0/sideload.zip'...
Anyone recognise these errors?[/QUOTE]
CM10 is really old are you sure that's what you want ? and it may require a special version of recovery .. check the developers thread
[QUOTE]First time installing CyanogenMod 10.2 to your HTC One (GSM), or coming from another ROM:
- Read the official wiki
- Unlock your device via http://www.htcdev.com
- [COLOR="Red"]Flash the latest official ClockworkMod-Recovery via Fastboot[/COLOR]
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into Recovery
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
[/QUOTE]
Click to expand...
Click to collapse

Here's the result of flashing CM 11:
Code:
Starting ADB sideload feature...
failed to open driver control: No such file or directory
failed to open driver control: No such file or directory
sideload_service invoked
adbd exiting after successful sideload
failed to open driver control: No such file or directory
Restarting adbd...
failed to open driver control: No such file or directory
Installing '/data/media/0/sideload.zip'...
Checking for MD5 file...
I:Cannot find file /data/media/0/sideload.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
mount: failed to mount /dev/block/mmcblk0p35 at /system: Device or resource busy
about to run program [/tmp/backuptool.sh] with 2 args
grep: /system/build.prop: No such file or directory
Not backing up files from incompatible version: 11
run_program: child exited with status 127
Creating filesystem with parameters:
Size: 1946152960
Block size: 4096
Blocks per group: 32768
Inodes per group: 7920
Inode size: 256
Journal blocks: 7423
Label:
Blocks: 475135
Block groups: 15
Reserved block group size: 119
Created filesystem with 11/118800 inodes and 15607/475135 blocks
minzip: Extracted file "/system/addon.d/50-cm.sh"
minzip: Extracted file "/system/addon.d/blacklist"
minzip: Extracted file "/system/app/Apollo.apk"
...
minzip: Extracted file "/system/xbin/strace"
minzip: Extracted file "/system/xbin/su"
minzip: Extracted file "/system/xbin/vim"
about to run program [/tmp/backuptool.sh] with 2 args
/tmp/backuptool.sh: cd: line 99: can't cd to /tmp/addon.d/
md5sum: can't open '*sh': No such file or directory
find: /tmp/addon.d/: No such file or directory
find: /tmp/addon.d/: No such file or directory
find: /tmp/addon.d/: No such file or directory
cp: can't stat '/tmp/addon.d/*': No such file or directory
script result was [/system]

On reboot TWRP reports that no OS is installed and the phone boots to a black screen

robtherobot101 said:
On reboot TWRP reports that no OS is installed and the phone boots to a black screen
Click to expand...
Click to collapse
Here is how to flash CM on the M7
just in case...
http://wiki.cyanogenmod.org/w/Install_CM_for_m7

What would cause the stock roms flash without a problem but all custom roms install improperly?

robtherobot101 said:
What would cause the stock roms flash without a problem but all custom roms install improperly?
Click to expand...
Click to collapse
Using the wrong custom recovery

TWRP 2.6.3.3 and Philz Recovery 6.25.0 are the only recoveries I've managed to get working

robtherobot101 said:
TWRP 2.6.3.3 and Philz Recovery 6.25.0 are the only recoveries I've managed to get working
Click to expand...
Click to collapse
Yeah, I'm not sure what's up with that. But it's for sure the reason why the other roms aren't working

When I bought the phone(supposedly brand new) the bootloader was locked but it was already S-OFF and had CID:11111111. The writing on the box is in German(I live in New Zealand) so I guess whoever I bought it off had fixed that for me...

Just in case anyone ever stumbles upon this thread in the distant future, let it be known that I managed to install this rom successfully and it's got all the useful features you'd expect from Cyanogenmod (and a few more).

robtherobot101 said:
Just in case anyone ever stumbles upon this thread in the distant future, let it be known that I managed to install this rom successfully and it's got all the useful features you'd expect from Cyanogenmod (and a few more).
Click to expand...
Click to collapse
or you just install maximus HD 50.0.0. this rom is super !

robtherobot101 said:
TWRP 2.6.3.3 and Philz Recovery 6.25.0 are the only recoveries I've managed to get working
Click to expand...
Click to collapse
This is the exact same problem I have only the 2 recoveries you mentioned work for me too, I've tried updating to newer versions of TWRP but it gets stuck on the HTC Logo with "entering recovery" at the top, I have the international version I also had to replace the screen because it smashed maybe that has something to do with it.