Database Develop

[DEV] RECOVERY-create own recovery images For Vivid

BoardConfig
Code:
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := msm8660
TARGET_BOARD_PLATFORM_GPU := qcom-adreno200
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a-neon
TARGET_CPU_SMP := true
ARCH_ARM_HAVE_TLS_REGISTER := true
BOARD_USES_ADRENO_200 := true
TARGET_BOOTLOADER_BOARD_NAME := rider
BOARD_KERNEL_CMDLINE := console=ttyHSL0 androidboot.hardware=rider no_console_suspend=1
BOARD_KERNEL_BASE := 0x48000000
BOARD_KERNEL_PAGESIZE := 2048
TARGET_USE_SCORPION_BIONIC_OPTIMIZATION := true
# cat /proc/emmc
#dev: size erasesize name
#mmcblk0p34: 000ffa00 00000200 "misc"
#mmcblk0p22: 00fffc00 00000200 "recovery"
#mmcblk0p21: 01000000 00000200 "boot"
#mmcblk0p23: 31fffc00 00000200 "system"
#mmcblk0p25: 06ebde00 00000200 "cache"
#mmcblk0p24: 4aabc400 00000200 "userdata"
#mmcblk0p28: 01400000 00000200 "devlog"
#mmcblk0p30: 00040000 00000200 "pdata"
TARGET_USERIMAGES_USE_EXT4 := true
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 838859776
BOARD_USERDATAIMAGE_PARTITION_SIZE := 1252770816
BOARD_BOOTIMAGE_PARTITION_SIZE := 16777216
BOARD_FLASH_BLOCK_SIZE := 131072
TARGET_RELEASETOOLS_EXTENSIONS := device/htc/common
TARGET_PREBUILT_KERNEL := device/htc/rider/kernel
BOARD_HAS_LARGE_FILESYSTEM := true
BOARD_HAS_NO_SELECT_BUTTON := true
BOARD_SDCARD_DEVICE_PRIMARY := /dev/block/mmcblk1p1
BOARD_SDCARD_DEVICE_SECONDARY := /dev/block/mmcblk1
BOARD_SDEXT_DEVICE := /dev/block/mmcblk1p2
BOARD_USES_MMCUTILS := true
BOARD_HAS_NO_MISC_PARTITION := true
BOARD_CUSTOM_GRAPHICS:= ../../../device/htc/rider/graphics.c
BOARD_USES_RECOVERY_CHARGEMODE := true
First, Extract the contents of the ramdisk with:
Code:
./unpack-bootimg.pl recovery.img
In all ramdisk you will have a few folders and files
Code:
./etc
./res(images for recovery go here)
./sbin(the actually recovery binary goes here & adbd)
./system
./tmp
./init
./default.prop
./init.holiday.rc
./init.rc
lift the security default.prop
Code:
[B]Original source code[/B]
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
[B]Changed source code [/B]
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
Pack-up Ramdisk
Code:
./mkbootfs ./recovery.img-ramdisk | gzip > ramdisk_recovery-edited.gz
Repack to IMG
Code:
./mkbootimg --base 0x48000000 --cmdline 'console=-ttyHSL3 androidboot.hardware=holiday' --kernel recovery.img-kernel.gz --ramdisk ramdisk_recovery-edited.gz -o new_recovery.img

is this to dump recovery?
Sent from my HTC-X710a using Tapatalk

Please provide more explanation.
Sent from my HTC PH39100 using xda premium

ceo.mtcl said:
Please provide more explanation.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
This is still very much a work in progress.

Even if we do get a custom recovery, we will still need s-off to do anything with it correct
Edit: in fact, there wouldn't even be a way to flash a custom recovery without s-off.
She's too young for you bro.Sent.

This is for Rooted devices
Rooted cwm recovery for vivid & raider(Holiday)
fixed by me
original by 2프로부족(pgpia)
tested
Extract zip file
Fastboot flash recovery root_recovery.img
recovery_download

Recovery working

trell959 said:
Even if we do get a custom recovery, we will still need s-off to do anything with it correct
Edit: in fact, there wouldn't even be a way to flash a custom recovery without s-off.
She's too young for you bro.Sent.
Click to expand...
Click to collapse
I believe this will only work for the Canadian and Korean versions of this phone. You can unlock the bootloaders for those phones but not the AT&T version yet. Hopefully that will change by the time my phone gets here.

pside15 said:
I believe this will only work for the Canadian and Korean versions of this phone. You can unlock the bootloaders for those phones but not the AT&T version yet. Hopefully that will change by the time my phone gets here.
Click to expand...
Click to collapse
Read somewhere that HTC will be unlocking the bootloader for ATT phones within a week.
Sent from my HTC PH39100 using xda premium

pside15 said:
I believe this will only work for the Canadian and Korean versions of this phone. You can unlock the bootloaders for those phones but not the AT&T version yet. Hopefully that will change by the time my phone gets here.
Click to expand...
Click to collapse
Oh thanks man
Sent from my Desire HD using xda premium

This can be used, but it feels somewhat unstable!However, still very grateful to!

now that i have CWM RECOVERY 5.0.2.7 on my phone i guess i just have to wait till we get s-off and then custom roms here i come!
update: nandroid backups work!

Can I have your boot.img and system.img from nandroid
erik10002 said:
now that i have CWM RECOVERY 5.0.2.7 on my phone i guess i just have to wait till we get s-off and then custom roms here i come!
update: nandroid backups work!
Click to expand...
Click to collapse
Sent from my Sensation using XDA App

mohsinkhan47 said:
Can I have your boot.img and system.img from nandroid
Click to expand...
Click to collapse
how and where do i find those files? thanks
also my first nandroid backup worked perfectly and i can restore it but when i try to backup now it gets stuck and freezes at certain points and i have to do a battery pull!

Its inside the nandoid folder.
I think its trying to mount to the system folder or something and its not mounting.
erik10002 said:
how and where do i find those files? thanks
also my first nandroid backup worked perfectly and i can restore it but when i try to backup now it gets stuck and freezes at certain points and i have to do a battery pull!
Click to expand...
Click to collapse
Sent from my Sensation using XDA App

mohsinkhan47 said:
Its inside the nandoid folder.
Click to expand...
Click to collapse
went inside the folder where my nandroid backup is and get these files
.android_secure.vfat.tar
cache.ext4.tar
data.ext4.tar
nandroid.md5
system.ext4.tar
is it any of these that you need?

Yeah that's good. Can you upload the system.tar file please
erik10002 said:
went inside the folder where my nandroid backup is and get these files
.android_secure.vfat.tar
cache.ext4.tar
data.ext4.tar
nandroid.md5
system.ext4.tar
is it any of these that you need?
Click to expand...
Click to collapse
Sent from my Sensation using XDA App

mohsinkhan47 said:
Yeah that's good. Can you upload the system.tar file please
Click to expand...
Click to collapse
it's a huge file, where can i upload and send this to you and FREE please! thanks

Github megaupload
erik10002 said:
it's a huge file, where can i upload and send this to you and FREE please! thanks
Click to expand...
Click to collapse
Sent from my Sensation using XDA App

mohsinkhan47 said:
Github megaupload
Click to expand...
Click to collapse
found github hard to navigate so i will use megaupload but it will have to wait till i get home because the upload speed on my work computers are sh!t.

SM-P605 based on Note 3 device tree

Hey there,
I hope that you don't mind me posting here, but I figure that this is the best place to get some assistance. I'm attempting to port CM11 to the Galaxy Note 10.1 2014 Edition (SM-P605). This is a very similar device to the Note 3, and as such, I've started by forking the Note 3 device tree. This is the first port that I've attempted, so I am very new to all of this.
I am using the Samsung stock 4.3 kernel sources for my device. When I run "make recoveryimage", everything seems to work fine and I get a recovery.img file. However, despite fiddling with all manner of settings in BoardConfig.mk, I cannot get it to boot. It just gets itself into a bootloop, saying "Recovery boooting..." at the top left, and then rinse-repeat.
I suspect that my problem lies with the ramdisk, and/or the ramdisk offset. The following is taken from the Note 3 BoardConfig.mk.
Code:
# Kernel
BOARD_KERNEL_CMDLINE := console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F
BOARD_KERNEL_BASE := 0x00000000
BOARD_KERNEL_PAGESIZE := 2048
BOARD_MKBOOTIMG_ARGS := --ramdisk_offset 0x02900000 --tags_offset 0x02700000
BOARD_KERNEL_SEPARATED_DT := true
BOARD_CUSTOM_BOOTIMG_MK := device/samsung/hlte/mkbootimg.mk
I presume that those offsets are different per device. After a bit of research, I came across an app called unmkbootimg which can supposedly tell me what I need to know. After feeding it my boot.img, I got the following result.
Code:
unmkbootimg version 1.2 - Mikael Q Kuisma <[email protected]>
Kernel size 7536872
Kernel address 0x8000
Ramdisk size 1375263
Ramdisk address 0x2000000
Secondary size 0
Secondary address 0xf00000
Kernel tags address 0x1e00000
Flash page size 2048
Board name is ""
Command line "console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F"
*** WARNING ****
This image is built using NON-standard mkbootimg!
OFF_KERNEL_ADDR is 0xFE208100
OFF_RAMDISK_ADDR is 0x00200100
OFF_SECOND_ADDR is 0xFF100100
Please modify mkbootimg.c using the above values to build your image.
****************
Extracting kernel to file zImage ...
Extracting root filesystem to file initramfs.cpio.gz ...
All done.
---------------
To recompile this image, use:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x1dfff00 --cmdline 'console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F' -o new_boot.img
---------------
I've tried 0x00200100 and 0x2000000 for ramdisk offset (purely because I am not sure which one is correct there), but both give the same result (ie. nothing).
I've also tried outputting the log to the LCD with
Code:
BOARD_KERNEL_CMDLINE := console=tty0,115200 fbcon=rotate:1 fbcon=font:VGA8x8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F
This made no difference at all either.
I'm not sure what else to try, so I'm looking for any suggestions please.
If you'd like to take a look at my device tree, it is here:
https://github.com/StNick
Thanks in advance.

Code:
*** WARNING ****
This image is built using NON-standard mkbootimg!
OFF_KERNEL_ADDR is 0xFE208100
OFF_RAMDISK_ADDR is 0x00200100
OFF_SECOND_ADDR is 0xFF100100
Please modify mkbootimg.c using the above values to build your image.
****************
Just to get that out of the way, did you try the above values?
What board does the SM-P605 use? (MSM8974AB?) Is it a Qualcomm or Exynos device?
You are able to get no output?
This may or may not be the right place to post such a question, but I think you'd be more likely to find the answer to your question here

StNickZA said:
Hey there,
I hope that you don't mind me posting here, but I figure that this is the best place to get some assistance. I'm attempting to port CM11 to the Galaxy Note 10.1 2014 Edition (SM-P605).
...
Click to expand...
Click to collapse
Are you certain that this one isn't a better place to start:
http://forum.xda-developers.com/galaxy-note-10-2014/development

xclub_101 said:
Are you certain that this one isn't a better place to start:
http://forum.xda-developers.com/galaxy-note-10-2014/development
Click to expand...
Click to collapse
Fairly certain, yes. The work being done on the Note 10.1 2014 Edition all pertains to the Exynos version which is less relevant to my device than the Note 3.
Just looking for some help from guys that have built for a similar device.

Error in flashing most of CM based ROMs in Moto X XT1052 EU version

I have Moto x XT1052 EU version and could not flash most of CM based ROMs. It fails with error message as "This package is for device:
xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcica,xt1060,ghost_verizon; this device is " + getprop("ro.product.device") + ".")".
This error is very much annoying. I found some tweak to successfully flash this ROM by following few simple steps:
ROMs causing this issue are,
[ROM] [4.4.4] [OFFICIAL] Ehndroix V 14.10.14 - Ghost
[Rom] [4.4.4] Cyanogenmod 11 for Moto X
N5X Experience ROM
1. Using 7z app, open flashable ROM zip file
2. go to META-INF\com\google\android\
3. drag and drop updater-script on your desktop
4. Open this script file with Notepad++
5. Delete the lines starting from "assert (getprop............ upto abort("this package....." (see screenshot attached)
6. Save the script in Notepad++
7. drag and drop this amended script file back to META-INF\com\google\android\
8. Close zip file
9. Copy to your phone sdcard memory
10. Don't forget to copy relevant gapps file as well
All done. Use your recovery (I prefer latest TWRP) and flash ROM and GAPPS.
Enjoy!!

IDK if I'm doing it wrong but the above edit did not fix the flash error for my xt1052 device. OP could you maybe redo your example picture by selecting/highlighting whatever text/lines need to go... Just to make it absolutely error proof. thx

Or in 7zip, find the updater-script and right-click, then edit.

What recovery are you using? Some XT1052 user reported that the newer twrp recoveries were not functional and we should hence use, 2.6.3.1. I am using the earlier build ( 2.6.3.1 ) and did face any problems. Flashing is easy and quick. Backing up and restoring is a piece of cake. No need of all these steps.
Cheers

TWRP 2.6.3.1 download link below for everybodies reference: Unfortunatly I don't have enough posts to my name to post the link fully so please attach both of the below lines
goo.
im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img/
This also worked for me.

omnomnomkimiiee said:
Or in 7zip, find the updater-script and right-click, then edit.
Click to expand...
Click to collapse
Did that but no go..
flasherruts said:
What recovery are you using? Some XT1052 user reported that the newer twrp recoveries were not functional and we should hence use, 2.6.3.1. I am using the earlier build ( 2.6.3.1 ) and did face any problems. Flashing is easy and quick. Backing up and restoring is a piece of cake. No need of all these steps.
Cheers
Click to expand...
Click to collapse
Was using latest TWRP and yeah you right 2.6.3.1 works flawlessly no more flash errors! No vibration feedback on 2.6.3.1 though...
JordTOC said:
TWRP 2.6.3.1 download link below for everybodies reference: Unfortunatly I don't have enough posts to my name to post the link fully so please attach both of the below lines
goo.
im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img/
This also worked for me.
Click to expand...
Click to collapse
Thanks for the link it worked!

TWRP 2.8.5.0 for cm/ghost
The problem is in the "properties" TWRP sets; the official TWRP builds have
Code:
ro.build.product=moto_msm8960dt
and nothing for
Code:
ro.product.device
. moto_msm8960dt isn't listed in the CM12 script. So I unpacked the official 2.8.5.0, set the ro.product.device=ghost and packed it back. You can do it yourself or just grab the attachment and flash it.
- get the official TWRP image for ghost here: (ok, I'm new and not allowed to post links; it's something with techerrata, twrp2 and ghost)
- get CM12 source (search the net for something like build cyanogenmod 12 lollipop, there's plenty of posts)
(this will take like forever; I *think* you only need the folder android/system/system/core)
- fire up a terminal; notice the paths, make sure you execute the commands in the same directory
- first build mkbootimg and unpackbootimg
Code:
[email protected]:~/android/system/system/core > gcc -o /tmp/mkbootimg libmincrypt/*.c mkbootimg/mkbootimg.c -Iinclude
[email protected]:~/android/system/system/core > gcc -o /tmp/unpackbootimg libmincrypt/*.c mkbootimg/unpackbootimg.c -Iinclude
- unpack the official TWRP image:
Code:
[email protected]:~/twrp/work > /tmp/unpackbootimg -i ../openrecovery-twrp-2.8.5.0-ghost.img
Android magic found at: 0
BOARD_KERNEL_CMDLINE console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 vmalloc=400M androidboot.write_protect=0 zcache
BOARD_KERNEL_BASE 80200000
BOARD_RAMDISK_OFFSET 02200000
BOARD_SECOND_OFFSET 00f00000
BOARD_TAGS_OFFSET 00000100
BOARD_PAGE_SIZE 2048
BOARD_SECOND_SIZE 0
BOARD_DT_SIZE 835240
- make a new folder, cd to it and extract the ramdisk
Code:
[email protected]:~/twrp/work/rd > gunzip -c ../openrecovery-twrp-2.8.5.0-ghost.img-ramdisk.gz | cpio -i
15231 blocks
- edit the file
Code:
default.prop
(add line ro.product.device=ghost)
- pack the ramdisk back:
Code:
[email protected]:~/twrp/work/rd > find . | cpio -o -H newc | gzip > ../newramdisk.gz
15231 blocks
- make the recovery image (I got the arguments from the output of unpackbootimage, see above)
Code:
[email protected]:~/twrp/work > /tmp/mkbootimg --kernel openrecovery-twrp-2.8.5.0-ghost.img-zImage --ramdisk newramdisk.gz --cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 vmalloc=400M androidboot.write_protect=0 zcache' --base 0x80200000 --pagesize 2048 --dt openrecovery-twrp-2.8.5.0-ghost.img-dt --ramdisk_offset 0x02200000 -o twrp-2.8.5.0-ghost-modified-for-cm12.img

rrvvrr said:
The problem is in the "properties" TWRP sets; the official TWRP builds have
Code:
ro.build.product=moto_msm8960dt
and nothing for
Code:
ro.product.device
. moto_msm8960dt isn't listed in the CM12 script. So I unpacked the official 2.8.5.0, set the ro.product.device=ghost and packed it back. You can do it yourself or just grab the attachment and flash it.
- get the official TWRP image for ghost here: (ok, I'm new and not allowed to post links; it's something with techerrata, twrp2 and ghost)
- get CM12 source (search the net for something like build cyanogenmod 12 lollipop, there's plenty of posts)
(this will take like forever; I *think* you only need the folder android/system/system/core)
- fire up a terminal; notice the paths, make sure you execute the commands in the same directory
- first build mkbootimg and unpackbootimg
Code:
[email protected]:~/android/system/system/core > gcc -o /tmp/mkbootimg libmincrypt/*.c mkbootimg/mkbootimg.c -Iinclude
[email protected]:~/android/system/system/core > gcc -o /tmp/unpackbootimg libmincrypt/*.c mkbootimg/unpackbootimg.c -Iinclude
- unpack the official TWRP image:
Code:
[email protected]:~/twrp/work > /tmp/unpackbootimg -i ../openrecovery-twrp-2.8.5.0-ghost.img
Android magic found at: 0
BOARD_KERNEL_CMDLINE console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 vmalloc=400M androidboot.write_protect=0 zcache
BOARD_KERNEL_BASE 80200000
BOARD_RAMDISK_OFFSET 02200000
BOARD_SECOND_OFFSET 00f00000
BOARD_TAGS_OFFSET 00000100
BOARD_PAGE_SIZE 2048
BOARD_SECOND_SIZE 0
BOARD_DT_SIZE 835240
- make a new folder, cd to it and extract the ramdisk
Code:
[email protected]:~/twrp/work/rd > gunzip -c ../openrecovery-twrp-2.8.5.0-ghost.img-ramdisk.gz | cpio -i
15231 blocks
- edit the file
Code:
default.prop
(add line ro.product.device=ghost)
- pack the ramdisk back:
Code:
[email protected]:~/twrp/work/rd > find . | cpio -o -H newc | gzip > ../newramdisk.gz
15231 blocks
- make the recovery image (I got the arguments from the output of unpackbootimage, see above)
Code:
[email protected]:~/twrp/work > /tmp/mkbootimg --kernel openrecovery-twrp-2.8.5.0-ghost.img-zImage --ramdisk newramdisk.gz --cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 vmalloc=400M androidboot.write_protect=0 zcache' --base 0x80200000 --pagesize 2048 --dt openrecovery-twrp-2.8.5.0-ghost.img-dt --ramdisk_offset 0x02200000 -o twrp-2.8.5.0-ghost-modified-for-cm12.img
Click to expand...
Click to collapse
Hi!
Can you edit newest twrp-2.8.7.0?

BossToroech said:
Hi!
Can you edit newest twrp-2.8.7.0?
Click to expand...
Click to collapse
Done, attached 2.8.7

rrvvrr said:
Done, attached 2.8.7
Click to expand...
Click to collapse
Twrp 2.8.7 does not detect the SD card on my phone. It would be great if you edit twrp 2.8.6 as that worked.

Ishaan Gupta said:
Twrp 2.8.7 does not detect the SD card on my phone. It would be great if you edit twrp 2.8.6 as that worked.
Click to expand...
Click to collapse
I could, it only takes about 10 minutes... But I'm pretty sure you are looking for something else - this thread is about ghost, that's Moto X 2013, which doesn't have an SD card.
Please correct me if I'm wrong.

You are right. Moto X 2013 doesn't have an SD Card slot.

rrvvrr said:
I could, it only takes about 10 minutes... But I'm pretty sure you are looking for something else - this thread is about ghost, that's Moto X 2013, which doesn't have an SD card.
Please correct me if I'm wrong.
Click to expand...
Click to collapse
BossToroech said:
You are right. Moto X 2013 doesn't have an SD Card slot.
Click to expand...
Click to collapse
Thanks for your quick reply.
I am sorry I said wrong. I mean the /data partition. The internal storage.
I am on windows so I could not build the recovery. No idea how to do it.
Thanks for your work. It saved me from editing the updater-script every time.
EDIT: Got it to finally mount /data. Had to wipe everything then flash twrp 2.8.6.0 and then your edited 2.8.7.0.

smohanv said:
I have Moto x XT1052 EU version and could not flash most of CM based ROMs. It fails with error message as "This package is for device:
xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcica,xt1060,ghost_verizon; this device is " + getprop("ro.product.device") + ".")".
This error is very much annoying. I found some tweak to successfully flash this ROM by following few simple steps:
ROMs causing this issue are,
[ROM] [4.4.4] [OFFICIAL] Ehndroix V 14.10.14 - Ghost
[Rom] [4.4.4] Cyanogenmod 11 for Moto X
N5X Experience ROM
1. Using 7z app, open flashable ROM zip file
2. go to META-INF\com\google\android\
3. drag and drop updater-script on your desktop
4. Open this script file with Notepad++
5. Delete the lines starting from "assert (getprop............ upto abort("this package....." (see screenshot attached)
6. Save the script in Notepad++
7. drag and drop this amended script file back to META-INF\com\google\android\
8. Close zip file
9. Copy to your phone sdcard memory
10. Don't forget to copy relevant gapps file as well
All done. Use your recovery (I prefer latest TWRP) and flash ROM and GAPPS.
Enjoy!!
Click to expand...
Click to collapse
I'm getting the same error for cm 12.1 on my moto x 2013 xt1052. What do i do?

Use the modified recovery @rrvvrr posted a few posts back.

Flashing Error
I recently rooted my XT 1052 (Asian version) using TWRP 2.8.6. However, when installing CM 12.1's 30/8 nightly build, I got an error reading "error executing updater binary in zip". Someone help me to solve this problem. I have installed the latest official TWRP 2.8.7.

vamshi03 said:
I'm getting the same error for cm 12.1 on my moto x 2013 xt1052. What do i do?
Click to expand...
Click to collapse
Exit the recovery and try again. If that doesn't work then unzip the Rom.zip file, if it opens with error then re download the Rom, otherwise if it opens without error then make a complete wipe of the phone and try again.
Chimax said:
I recently rooted my XT 1052 (Asian version) using TWRP 2.8.6. However, when installing CM 12.1's 30/8 nightly build, I got an error reading "error executing updater binary in zip". Someone help me to solve this problem. I have installed the latest official TWRP 2.8.7.
Click to expand...
Click to collapse
Sent from my Moto X

Thanks... The file is intact.... I will try it today again...
Sent from my XT1052 using XDA Free mobile app

No use
bushako said:
Exit the recovery and try again. If that doesn't work then unzip the Rom.zip file, if it opens with error then re download the Rom, otherwise if it opens without error then make a complete wipe of the phone and try again.
Sent from my Moto X
Click to expand...
Click to collapse
I did as you had instructed but still no use... The same error keeps on popping up... It's pathetic... even after rooting I can't install CM

Chimax said:
I did as you had instructed but still no use... The same error keeps on popping up... It's pathetic... even after rooting I can't install CM
Click to expand...
Click to collapse
Can you confirm that you are running the latest bootloader version? You could still be on the older bootloader and that's why it returns with errors.
However, if you are reluctant to upgrade bootloader for whatever reason, then you can try and flash an older version of twrp from before 5.1 was released or use another recovery such as cynagoen recovery or cmw if available.
I can explain to you as to why this happens but I prefer you first give it a try.
Sent from my Moto X

integrate google apps to the build to be installed in /data/app

Hi all;
i try to make my own rom, and I want add google-apps to the build to be installed in /data/app
this is the steps :
1 - create new folder called "gapps" in vendor/ dir
2- in "gapps" add data/app/Youtube/app/youtube.apk,
3- create android.mk file in "gapps" folder with this content
Code:
LOCAL_PATH := $(call my-dir)
include $(CLEAR_VARS)
LOCAL_MODULE := YouTube
LOCAL_SRC_FILES := data/app/YouTube/YouTube.apk
LOCAL_MODULE_PATH := $(TARGET_OUT_DATA_APPS)
LOCAL_MODULE_CLASS := APPS
LOCAL_MODULE_OWNER := GOLDROM
LOCAL_MODULE_TAGS := optional
LOCAL_CERTIFICATE := PRESIGNED
LOCAL_MODULE_SUFFIX := $(COMMON_ANDROID_PACKAGE_SUFFIX)
include $(BUILD_PREBUILT)
4 - go to the build dir in the android root files build/target/product/core.mk and add YouTube to the PRODUCT_PACKAGES var
5- build, flash, but youtube not found.
plz correct me , if i made any errors.

Don't know, it's honestly something none of us have ever done since there's little to no advantage over simply flashing a separate gapps package.
The effort to do it for personal builds is greater than that of flashing gapps, and for legal reasons it'll NEVER happen for official builds.

solution is to add your module to PRODUCT_PACKAGES var
rootAndroid/build/target/product/generic_no_telephony.mk
Click to expand...
Click to collapse
and then youtube (or any other google-app) will work fine in /data as a user app
but its still a not clean solution.

HELP!! Need TWRP build for N950U to test BL Unlock

It is kinda sad that I don't have a good enough computer at home to build TWRP.
I simply lack the space to even download the sources.
I'm very close to an unlock and I really need TWRP.
Someone out there i'm sure has compiled it by now.
Please share I need this for testing.
Thank You

BigCountry907 said:
It is kinda sad that I don't have a good enough computer at home to build TWRP.
I simply lack the space to even download the sources.
I'm very close to an unlock and I really need TWRP.
Someone out there i'm sure has compiled it by now.
Please share I need this for testing.
Thank You
Click to expand...
Click to collapse
I have a goodish computer at home with lots of space. if I knew how I could build twrp for you. how is twrp built?

stantheandroidman said:
I have a goodish computer at home with lots of space. if I knew how I could build twrp for you. how is twrp built?
Click to expand...
Click to collapse
It's not as easy as asking "how is twrp built?" It requires Linux operating system not Windows and you have to have a build environment set up for that already.. Not as easy as some people think it is.

BigCountry907 said:
It is kinda sad that I don't have a good enough computer at home to build TWRP.
I simply lack the space to even download the sources.
I'm very close to an unlock and I really need TWRP.
Someone out there i'm sure has compiled it by now.
Please share I need this for testing.
Thank You
Click to expand...
Click to collapse
Have you tried contacting afaneh92, the fellow that made Safestrap for the Note 8? It has TWRP built in, though I don't know how that implementation differs from a standard device build. He might be able to help in some capacity, though I wouldn't be surprised if you've already thought of this.

Would the w version help u?

Johnmoerike said:
Would the w version help u?
Click to expand...
Click to collapse
I'm not sure what the difference is with the W version of the device.
if it's qualcomm chip-set it could be an ok starting point.
@CountKrzysztof
Yea i have contacted @afaneh92 and he has given me all of the source for the safestrap build.
He's been helpful. The original safestrap was made by hash of codes and afaneh92 ported to our devices. And a whole lot more.
There is not much documentation on safestrap itself but rightfully so. It primarily is a set of shell scripts. I've been tracing back through them to better understand the entire process.
I was hoping for someone like @Captain_Throwback to have already built TWRP for the N950U. But he is more of a HTC dev so I doubt he will build it for N950U. But you never know. He has helped me in the past and I know his system is setup to build already.
One of the problems with the safestrap build for the N950U is adb is not working. I'ts not the end of the world but its a lot harder to type everything in terminal compared to the PC.
@MrMike2182 is pretty much right that its not that easy to start compiling sources n stuff.
It's not extremely difficult either. Setting up ubuntu is pretty easy and getting the build system setup is not bad at all. It takes quite a bit of time to download sources. If everything goes well compiling isn't too bad either. But when something breaks in the middle of compiling and you have to start modifying .c and .h files and tracking down modules it gets to be time consuming.
At any rate I'm going to need to download sources for TWRP and the kernel.
I'm gonna try to build the kexec modules and see if we cant get that working again. It is always just a matter of having the time to do it all.

This link has complete guide to initialize minimal omni 6.0 source about 1GB size and all steps to compile twrp
https://gist.github.com/mohammad92/e2a131b738ea117c4bd82a5436a6bf23

BigCountry907 said:
It is kinda sad that I don't have a good enough computer at home to build TWRP.
I simply lack the space to even download the sources.
I'm very close to an unlock and I really need TWRP.
Someone out there i'm sure has compiled it by now.
Please share I need this for testing.
Thank You
Click to expand...
Click to collapse
I have an Ubuntu system that pretty much has the entire 18GB android sources and stuff available to you if you want to log in to the system I'll give you full root access to it to do what you want I'm trying to help you out but it looks like I'm about to be dispatched to the border to deal with the migrant issue so I'm running out of time if you have a good internet connection my system is pretty quick I'm not all sure what else needs to be done on its Ubuntu 18.04.. Up to you I'll keep trying until I have to leave I'm running into finding a viable tree to use on github though I mean they have 1 for the exynos version. I have the source code for Samsung though.

I appreciate the offer. The TWRP for the N950W came up and I will use that for now.
Later down the road having a good build system will be helpful. Not sure about Ubuntu 18. I've done a lot with 16.04 and have run into cases where older versions of python and other packages are needed.
Most likely there's a way to use 18.
Thanks again.
Never thought about running off a server. Bet I can rent one cheap these days.

BigCountry907 said:
I appreciate the offer. The TWRP for the N950W came up and I will use that for now.
Later down the road having a good build system will be helpful. Not sure about Ubuntu 18. I've done a lot with 16.04 and have run into cases where older versions of python and other packages are needed.
Most likely there's a way to use 18.
Thanks again.
Never thought about running off a server. Bet I can rent one cheap these days.
Click to expand...
Click to collapse
Yeah I've needed the older packages for several different roms I was doing but I just get them installed and move on until the next issue comes up.. Glad you at least got one TWRP to use! Thanks for all the work you're putting in! By the way do you happen to have a BoardConfig.mk file?

You should be able to start with the one from the safestrap sources. The TWRP he builds is modified slightly. It adds in a few options to the recovery. But I would guess the boardconfig should be about the same. Just double check any extra flags.
https://github.com/mohammad92/android_device_samsung
https://github.com/mohammad92/androi...very-safestrap

BigCountry907 said:
I appreciate the offer. The TWRP for the N950W came up and I will use that for now.
Later down the road having a good build system will be helpful. Not sure about Ubuntu 18. I've done a lot with 16.04 and have run into cases where older versions of python and other packages are needed.
Most likely there's a way to use 18.
Thanks again.
Never thought about running off a server. Bet I can rent one cheap these days.
Click to expand...
Click to collapse
the guide work for all versions of ubuntu!
but there some extra stuff to get old jdk to be installed on 18

The board_config uses the msm8998 common.
Did you find it.
LOCAL_PATH := device/samsung/msm8998-common
# Architecture
TARGET_ARCH := arm64
TARGET_ARCH_VARIANT := armv8-a
TARGET_CPU_ABI := arm64-v8a
TARGET_CPU_ABI2 :=
TARGET_CPU_VARIANT := kryo
TARGET_2ND_ARCH := arm
TARGET_2ND_ARCH_VARIANT := armv7-a-neon
TARGET_2ND_CPU_ABI := armeabi-v7a
TARGET_2ND_CPU_ABI2 := armeabi
TARGET_2ND_CPU_VARIANT := krait
TARGET_USES_64_BIT_BINDER := true
ENABLE_CPUSETS := true
ENABLE_SCHEDBOOST := true
# Bootloader
TARGET_BOOTLOADER_BOARD_NAME := msm8998
TARGET_NO_BOOTLOADER := true
# Kernel
TARGET_KERNEL_ARCH := arm64
TARGET_KERNEL_HEADER_ARCH := arm64
TARGET_PREBUILT_KERNEL := $(LOCAL_PATH)/kernel
# Image
BOARD_KERNEL_BASE := 0x00000000
BOARD_KERNEL_CMDLINE := console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 sched_enable_hmp=1 sched_enable_power_aware=1 service_locator.enable=1 swiotlb=2048 androidboot.selinux=permissive
BOARD_KERNEL_PAGESIZE := 4096
BOARD_KERNEL_TAGS_OFFSET := 0x01E00000
BOARD_RAMDISK_OFFSET := 0x02000000
# Platform
TARGET_BOARD_PLATFORM := msm8998
TARGET_BOARD_PLATFORM_GPU := qcom-adreno540
# Partitions
BOARD_BOOTIMAGE_PARTITION_SIZE := 67108864
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 67108864
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 4478795776
BOARD_USERDATAIMAGE_PARTITION_SIZE := 58543898624
BOARD_FLASH_BLOCK_SIZE := 262144
# Recovery
BOARD_HAS_LARGE_FILESYSTEM := true
BOARD_HAS_NO_SELECT_BUTTON := true
TARGET_USERIMAGES_USE_EXT4 := true
TARGET_RECOVERY_DEVICE_DIRS := $(LOCAL_PATH)
# TWRP
TW_THEME := portrait_hdpi
RECOVERY_SDCARD_ON_DATA := true
TARGET_RECOVERY_QCOM_RTC_FIX := true
TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888"
TW_BRIGHTNESS_PATH := "/sys/class/leds/lcd-backlight/brightness"
TW_MAX_BRIGHTNESS := 36500
TW_DEFAULT_BRIGHTNESS := 15000
TW_NO_REBOOT_BOOTLOADER := true
TW_HAS_DOWNLOAD_MODE := true
TW_INCLUDE_NTFS_3G := true
TW_EXCLUDE_SUPERSU := true
TW_EXCLUDE_DEFAULT_USB_INIT := true
TW_EXTRA_LANGUAGES := true
TW_INPUT_BLACKLIST := "hbtp_vm"
# Encryption support
TW_INCLUDE_CRYPTO := true
# System properties
-include $(LOCAL_PATH)/system_prop.mk

BigCountry907 said:
The board_config uses the msm8998 common.
Did you find it.
LOCAL_PATH := device/samsung/msm8998-common
# Architecture
TARGET_ARCH := arm64
TARGET_ARCH_VARIANT := armv8-a
TARGET_CPU_ABI := arm64-v8a
TARGET_CPU_ABI2 :=
TARGET_CPU_VARIANT := kryo
TARGET_2ND_ARCH := arm
TARGET_2ND_ARCH_VARIANT := armv7-a-neon
TARGET_2ND_CPU_ABI := armeabi-v7a
TARGET_2ND_CPU_ABI2 := armeabi
TARGET_2ND_CPU_VARIANT := krait
TARGET_USES_64_BIT_BINDER := true
ENABLE_CPUSETS := true
ENABLE_SCHEDBOOST := true
# Bootloader
TARGET_BOOTLOADER_BOARD_NAME := msm8998
TARGET_NO_BOOTLOADER := true
# Kernel
TARGET_KERNEL_ARCH := arm64
TARGET_KERNEL_HEADER_ARCH := arm64
TARGET_PREBUILT_KERNEL := $(LOCAL_PATH)/kernel
# Image
BOARD_KERNEL_BASE := 0x00000000
BOARD_KERNEL_CMDLINE := console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 sched_enable_hmp=1 sched_enable_power_aware=1 service_locator.enable=1 swiotlb=2048 androidboot.selinux=permissive
BOARD_KERNEL_PAGESIZE := 4096
BOARD_KERNEL_TAGS_OFFSET := 0x01E00000
BOARD_RAMDISK_OFFSET := 0x02000000
# Platform
TARGET_BOARD_PLATFORM := msm8998
TARGET_BOARD_PLATFORM_GPU := qcom-adreno540
# Partitions
BOARD_BOOTIMAGE_PARTITION_SIZE := 67108864
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 67108864
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 4478795776
BOARD_USERDATAIMAGE_PARTITION_SIZE := 58543898624
BOARD_FLASH_BLOCK_SIZE := 262144
# Recovery
BOARD_HAS_LARGE_FILESYSTEM := true
BOARD_HAS_NO_SELECT_BUTTON := true
TARGET_USERIMAGES_USE_EXT4 := true
TARGET_RECOVERY_DEVICE_DIRS := $(LOCAL_PATH)
# TWRP
TW_THEME := portrait_hdpi
RECOVERY_SDCARD_ON_DATA := true
TARGET_RECOVERY_QCOM_RTC_FIX := true
TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888"
TW_BRIGHTNESS_PATH := "/sys/class/leds/lcd-backlight/brightness"
TW_MAX_BRIGHTNESS := 36500
TW_DEFAULT_BRIGHTNESS := 15000
TW_NO_REBOOT_BOOTLOADER := true
TW_HAS_DOWNLOAD_MODE := true
TW_INCLUDE_NTFS_3G := true
TW_EXCLUDE_SUPERSU := true
TW_EXCLUDE_DEFAULT_USB_INIT := true
TW_EXTRA_LANGUAGES := true
TW_INPUT_BLACKLIST := "hbtp_vm"
# Encryption support
TW_INCLUDE_CRYPTO := true
# System properties
-include $(LOCAL_PATH)/system_prop.mk
Click to expand...
Click to collapse
Yeah I did thanks I forked it over to my git account. How's the N950W twrp working?

Haven't even tried it yet.
First I want to modify the safestrap so everything is running off the SD. Then It'll be easy to change things for testing.
If it don't boot right just have to pull the SD.

BigCountry907 said:
It is kinda sad that I don't have a good enough computer at home to build TWRP.
I simply lack the space to even download the sources.
I'm very close to an unlock and I really need TWRP.
Someone out there i'm sure has compiled it by now.
Please share I need this for testing.
Thank You
Click to expand...
Click to collapse
Do you still need a build of TWRP?

If your set up to do it that would be great.
Right now adb isn't working in safestrap and I use a lot of shell code.
I could easily switch the ramdisk and see.

BigCountry907 said:
If your set up to do it that would be great.
Right now adb isn't working in safestrap and I use a lot of shell code.
I could easily switch the ramdisk and see.
Click to expand...
Click to collapse
Good news, I was able to compile it.
https://www.mediafire.com/file/hx77ff4bn7wfszo/twrp.zip/file
I have included the boot image, ramdisk image, and recovery ramdisk image in addition to the recovery image itself. I hope this helps us get closer to an unlock.

Very Nice.
Thank you very much.

BigCountry907 said:
Very Nice.
Thank you very much.
Click to expand...
Click to collapse
No problem. If there's anything I can do to help you, please let me know.