Related
If this is in wrong place pleas move as needed.
When I try to boot debian on my g1 I get some errors.
Here is what I get:
/sdcard/debian # su bootdeb
su bootdeb
←[H←[JAndroid Filesytem remounted as read/write
insmod: can't read 'ext2': No such file or directory
mknod: /dev/loop2: File exists
←[H←[J
a888a
d888888b
8P YP Y88
8|o||o|88
8. .88
8 ._. Y8.
d/ 8b.
.dP . Y8b.
d8: ::88b.
d8 Y88b
:8P :888
8a. : _a88P
._/ Yaa_ : .| 88P|
\ YP | 8P \.
/ \._____.d| .|
--..__)888888P ._.|
mount: mounting /dev/block/loop2 on /data/local/mnt failed: Invalid argument
mount: mounting devpts on /data/local/mnt/dev/pts failed: No such file or direct
ory
mount: mounting proc on /data/local/mnt/proc failed: No such file or directory
mount: mounting sysfs on /data/local/mnt/sys failed: No such file or directory
Custom Linux Pseudo Bootstrapper V1.0 - by Mark Walker
WEB: http://www.androidfanatic.com
EML: [email protected]
Starting init process
INIT: Debian booting.....
Running Linux Kernel
net.ipv4.ip_forward = 1
AutoMounter started
Type EXIT to end session
Make sure you do a proper EXIT for a clean kill of Debian!
chroot: cannot execute /bin/bash: No such file or directory
umount: can't forcibly umount /data/local/mnt/dev/pts: No such file or directory
umount: can't forcibly umount /data/local/mnt/proc: No such file or directory
umount: can't forcibly umount /data/local/mnt/sys: No such file or directory
umount: can't forcibly umount /data/local/mnt: Invalid argument
Filesystems have unmounted
losetup: /dev/block/loop2: No such device or address
Loopback device shutdown - success
Debian down
Coded by Mark Walker
http://www.androidfanatic.com
admin.androidfanatic.com
Reverted back to Android console
/sdcard/debian #
Click to expand...
Click to collapse
Can anyone help me out there?
Thanks...but is there a faster mirror for debian? I'm trying to get a new build of Win7 (still using pre beta 1,going to RC) and I cant spare any bandwidth
Here I consolidate the custom tools necessary to unpack, modify, repack and loki your JB 4.2.2 ROM zip boot.img!
These Windows/cygwin tools invoke the djrbliss loki bootloader exploit for your rooted SGS4!
See my Instructional Demo below! Results are tested working on my AT&T SGH-I337 running Liquid Smooth v2.8 (JB 4.2.2) and TWRP Recovery 2.5.0.2.
SGS4 Boot Image Toolset (sgs4-boot-tools.zip): http://www.mediafire.com/?6sp3pp33lxgm3ua
Contents
Executive shell script: modify-boot-sgs4.sh to unpack boot image to kernel and ramdisk, thus enabling user to modify boot image
Perl scripts: unpack-bootimg-sgs4.pl and repack-bootimg-sgs4.pl
mkbootimg.exe (make boot image from kernel and ramdisk)
loki-boot directory with ROM-like directory structure --- contains all files needed to “loki” your boot.img
The loki-boot directory also contains two boot files: boot-ref.img (extracted directly from Liquid Smooth ROM zip) and a modified boot.img (generated using the Instructional Demo further below).
My custom repack-bootimg-sgs4.pl invokes the following command string:
./mkbootimg.exe --cmdline 'androidboot.hardware=qcom user_debug=31 zcache' --base 0x80200000 --kernel boot.img-kernel --ramdisk ramdisk-repack.cpio.gz -o $boot-repack.img
Detail:
--cmdline 'androidboot.hardware=qcom user_debug=31 zcache' (command line tellback from unpack-bootimg-sgs4.pl)
--base 0x80200000 (from Liquid Smooth /proc/config.gz: CONFIG_PHYS_OFFSET=0x80200000)
--kernel $boot.img-kernel (ROM kernel file)
--ramdisk ramdisk-repack.cpio.gz (gzipped cpio of/ramdisk)
-o $boot-repack.img (output file)
Click to expand...
Click to collapse
Preliminaries
If you don’t have cygwin, you can download it here: http://www.cygwin.com/ and install.
Cygwin packages installed on my XP workstation are shown below. You probably don’t need all of them, though I believe many come with the base cygwin.
But you definitely need perl
Code:
$ cygcheck -c
Cygwin Package Information
Package Version Status
_autorebase 000199-1 OK
_update-info-dir 01102-1 OK
alternatives 1.3.30c-10 OK
base-cygwin 3.1-1 OK
base-files 4.1-1 OK
bash 4.1.10-4 OK
bzip2 1.0.6-2 OK
coreutils 8.15-1 OK
cpio 2.11-2 OK
crypt 1.2-1 OK
cygutils 1.4.10-2 OK
cygwin 1.7.17-1 OK
cygwin-doc 1.7-1 OK
dash 0.5.7-1 OK
diffutils 3.2-1 OK
dos2unix 6.0.3-1 OK
editrights 1.01-2 OK
file 5.11-1 OK
findutils 4.5.9-2 OK
gawk 4.0.2-1 OK
gettext 0.18.1.1-2 OK
grep 2.6.3-1 OK
groff 1.21-2 OK
gzip 1.4-1 OK
ipc-utils 1.0-1 OK
less 444-1 OK
libattr1 2.4.46-1 OK
libbz2_1 1.0.6-2 OK
libdb4.5 4.5.20.2-3 OK
libexpat1 2.1.0-1 OK
libgcc1 4.5.3-3 OK
libgdbm4 1.8.3-20 OK
libgmp3 4.3.2-1 OK
libiconv2 1.14-2 OK
libintl8 0.18.1.1-2 OK
liblzma5 5.0.2_20110517-1 OK
libncurses10 5.7-18 OK
libncursesw10 5.7-18 OK
libopenssl100 1.0.1c-2 OK
libpcre0 8.21-2 OK
libpopt0 1.6.4-4 OK
libreadline7 6.1.2-3 OK
libsigsegv2 2.10-1 OK
libssp0 4.5.3-3 OK
libstdc++6 4.5.3-3 OK
libxml2 2.9.0-1 OK
login 1.10-10 OK
man 1.6g-1 OK
mintty 1.1.2-1 OK
perl 5.14.2-3 OK
perl_vendor 5.14.2-3 OK
rebase 4.4.0-1 OK
run 1.1.13-1 OK
sed 4.2.1-2 OK
tar 1.26-1 OK
terminfo 5.7_20091114-14 OK
texinfo 4.13-4 OK
tzcode 2012j-1 OK
vim 7.3.762-1 OK
vim-common 7.3.762-1 OK
which 2.20-2 OK
xxd 7.3.762-1 OK
xz 5.0.2_20110517-1 OK
zlib0 1.2.7-1 OK
Instructional Demo
1. Boot SGS4 to recovery and Nandroid backup existing ROM for peace of mind
2. (One time) Create a cygwin working directory (e.g. ~/cygwin/home/modify-boot-sgs4) and unzip the SGS4 Boot Image Toolset files to it
3. On Windows, extract ROM boot.img (e.g. from Liquid-JB-v2.8-OFFICIAL-jflteatt.zip) and place boot.img in cygwin working directory.
4. Launch cygwin command window in working directory and enter script command:
sh modify-boot-sgs4.sh boot.img (produces ramdisk directory: boot.img-ramdisk/)
CNTL-C out of shell script and back to cygwin prompt.
5. Edit boot.img-ramdisk/default.prop, set: ro.secure=0 and save and close.
Note: The setting: ro.secure=0 instructs Android to grant root to ADB so user does not have to keep entering “su” at the beginning of each ADB session.
6. At cygwin terminal enter:
perl repack-bootimg-sgs4.pl boot.img
This yields boot-repack.img.
Here’s a dump of my cygwin session…
Code:
[email protected] /home
$ mkdir modify-boot-sgs4
[email protected] /home
$ cd modify-boot-sgs4
[email protected] /home/modify-boot-sgs4
$ pwd
/home/modify-boot-sgs4
[email protected] /home/modify-boot-sgs4
$ sh modify-boot-sgs4.sh boot.img
Unpack/Repack SGS4 ROM Boot Image
Initial Release (14 Jul 2013)
sendust7 @ xda developers
Current directory: /home/modify-boot-sgs4
Unpacking boot image...
Page size: 2048 (0x00000800)
Kernel size: 4961224 (0x004bb3c8)
Ramdisk size: 488535 (0x00077457)
Second size: 0 (0x00000000)
Board name:
Command line: androidboot.hardware=qcom user_debug=31 zcache
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
Unzipping: boot.img-ramdisk.gz to boot.img-ramdisk
1708 blocks
Press ENTER to repack boot image or CNTL C to exit (and modify ramdisk offline):
[COLOR="Blue"](Modify /ramdisk/default.prop then resume cygwin session)[/COLOR]
[email protected] /home/modify-boot-sgs4
$ perl repack-bootimg-sgs4.pl boot.img
find . | cpio -o -H newc | gzip > /home/modify-boot-sgs4/ramdisk-repack.cpio.gz
1708 blocks
./mkbootimg.exe --cmdline 'androidboot.hardware=qcom user_debug=31 zcache' --base 0x80200000 --kernel boot.img-kernel --ramdisk ramdisk-repack.cpio.gz -o boot-repack.img
Repacked boot image written to boot-repack.img
[email protected] /home/modify-boot-sgs4
$
7. Exit cygwin and drop boot-repack.img into loki-boot directory and rename to boot.img. Then 7-zip contents of loki-boot directory to loki-boot.zip (CNTL-A (Select All) then right-click > 7-zip > Add to “loki-boot.zip”).
8. Connect SGS4 to your ADB-enabled computer, then
adb push loki-boot.zip /external_sd/Download (or your favorite flash directory)
9. Boot to recovery and flash loki-boot.zip (takes a few seconds)
10. Reboot system and achieve “pre-rooted” ADB sessions on Liquid Smooth!
C:\Program Files\Android\android-sdk\platform-tools>adb kill-server
C:\Program Files\Android\android-sdk\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ #
Click to expand...
Click to collapse
BTW here's a nice little app: https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot&hl=en
With Quick Boot, you can reboot to recovery via soft key, which is easier than booting to recovery from cold start.
Blessings. Enjoy!
Credits:
djrbliss @ xda developers and other contributors for the loki exploit: https://github.com/djrbliss/loki)
William Enck (split_bootimg): http://www.enck.org/
Android Development Team (Unpack, Edit, Repack Boot Images): http://www.android-dls.com/wiki/?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Cygwin Project Team: http://cygwin.com/who.html
sendust7 said:
If you don’t have cygwin, you can
Click to expand...
Click to collapse
use native Linux
svs57 said:
use native Linux
Click to expand...
Click to collapse
L.O.L, I totally agree
;
;Warning: Boot.ini is used on Windows XP and earlier operating systems.
;Warning: Use BCDEDIT.exe to modify Windows Vista boot options.
;
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /NOEXECUTE=OPTIN /FASTDETECT
C:\wubildr.mbr="Ubuntu"
Click to expand...
Click to collapse
But my past experience is that most users prefer Windows
I am not sure, but I don't think this will work on a fresh install of Cygwin. When i installed cygwin i selected "all" for packages. The directory structure does not match your script, /bin is not under /usr but in the root of cygwin directory. Also, i checked the installed packages, many are missing, and when i search cygwin.com for the missing, i cant find quite a few. Im new to cygwin, as in this op, but not new to software. i tried several boot.img (4.3) thinking it might be the image, but it was a strech and all failed the same. I dont find the .dll your script is looking for, so the error is correct.
I get this error:
$ sh modify-boot-sgs4.sh boot.img
Unpack/Repack SGS4 ROM Boot Image
Initial Release (14 Jul 2013)
sendust7 @ xda developers
Current directory: /home/modify-boot-sg4
Unpacking boot image...
/usr/bin/perl.exe: error while loading shared libraries: cygssp-0.dll: cannot open shared object file: No such file or directory
UPDATE: well I went through the cygwin install/update again and after searching for each package you listed, installing everything associated with each package, your scripts WORK. I have unpacked/edited/repacked and loaded. ADB as root......profit
Thanks for this
Thanks
sendust7 said:
Here I consolidate the custom tools necessary to unpack, modify, repack and loki your JB 4.2.2 ROM zip boot.img!
These Windows/cygwin tools invoke the djrbliss loki bootloader exploit for your rooted SGS4!
See my Instructional Demo below! Results are tested working on my AT&T SGH-I337 running Liquid Smooth v2.8 (JB 4.2.2) and TWRP Recovery 2.5.0.2.
SGS4 Boot Image Toolset (sgs4-boot-tools.zip): http://www.mediafire.com/?6sp3pp33lxgm3ua
Contents
Executive shell script: modify-boot-sgs4.sh to unpack boot image to kernel and ramdisk, thus enabling user to modify boot image
Perl scripts: unpack-bootimg-sgs4.pl and repack-bootimg-sgs4.pl
mkbootimg.exe (make boot image from kernel and ramdisk)
loki-boot directory with ROM-like directory structure --- contains all files needed to “loki” your boot.img
The loki-boot directory also contains two boot files: boot-ref.img (extracted directly from Liquid Smooth ROM zip) and a modified boot.img (generated using the Instructional Demo further below).
My custom repack-bootimg-sgs4.pl invokes the following command string:
Preliminaries
If you don’t have cygwin, you can download it here: http://www.cygwin.com/ and install.
Cygwin packages installed on my XP workstation are shown below. You probably don’t need all of them, though I believe many come with the base cygwin.
But you definitely need perl
Code:
$ cygcheck -c
Cygwin Package Information
Package Version Status
_autorebase 000199-1 OK
_update-info-dir 01102-1 OK
alternatives 1.3.30c-10 OK
base-cygwin 3.1-1 OK
base-files 4.1-1 OK
bash 4.1.10-4 OK
bzip2 1.0.6-2 OK
coreutils 8.15-1 OK
cpio 2.11-2 OK
crypt 1.2-1 OK
cygutils 1.4.10-2 OK
cygwin 1.7.17-1 OK
cygwin-doc 1.7-1 OK
dash 0.5.7-1 OK
diffutils 3.2-1 OK
dos2unix 6.0.3-1 OK
editrights 1.01-2 OK
file 5.11-1 OK
findutils 4.5.9-2 OK
gawk 4.0.2-1 OK
gettext 0.18.1.1-2 OK
grep 2.6.3-1 OK
groff 1.21-2 OK
gzip 1.4-1 OK
ipc-utils 1.0-1 OK
less 444-1 OK
libattr1 2.4.46-1 OK
libbz2_1 1.0.6-2 OK
libdb4.5 4.5.20.2-3 OK
libexpat1 2.1.0-1 OK
libgcc1 4.5.3-3 OK
libgdbm4 1.8.3-20 OK
libgmp3 4.3.2-1 OK
libiconv2 1.14-2 OK
libintl8 0.18.1.1-2 OK
liblzma5 5.0.2_20110517-1 OK
libncurses10 5.7-18 OK
libncursesw10 5.7-18 OK
libopenssl100 1.0.1c-2 OK
libpcre0 8.21-2 OK
libpopt0 1.6.4-4 OK
libreadline7 6.1.2-3 OK
libsigsegv2 2.10-1 OK
libssp0 4.5.3-3 OK
libstdc++6 4.5.3-3 OK
libxml2 2.9.0-1 OK
login 1.10-10 OK
man 1.6g-1 OK
mintty 1.1.2-1 OK
perl 5.14.2-3 OK
perl_vendor 5.14.2-3 OK
rebase 4.4.0-1 OK
run 1.1.13-1 OK
sed 4.2.1-2 OK
tar 1.26-1 OK
terminfo 5.7_20091114-14 OK
texinfo 4.13-4 OK
tzcode 2012j-1 OK
vim 7.3.762-1 OK
vim-common 7.3.762-1 OK
which 2.20-2 OK
xxd 7.3.762-1 OK
xz 5.0.2_20110517-1 OK
zlib0 1.2.7-1 OK
Instructional Demo
1. Boot SGS4 to recovery and Nandroid backup existing ROM for peace of mind
2. (One time) Create a cygwin working directory (e.g. ~/cygwin/home/modify-boot-sgs4) and unzip the SGS4 Boot Image Toolset files to it
3. On Windows, extract ROM boot.img (e.g. from Liquid-JB-v2.8-OFFICIAL-jflteatt.zip) and place boot.img in cygwin working directory.
4. Launch cygwin command window in working directory and enter script command:
sh modify-boot-sgs4.sh boot.img (produces ramdisk directory: boot.img-ramdisk/)
CNTL-C out of shell script and back to cygwin prompt.
5. Edit boot.img-ramdisk/default.prop, set: ro.secure=0 and save and close.
Note: The setting: ro.secure=0 instructs Android to grant root to ADB so user does not have to keep entering “su” at the beginning of each ADB session.
6. At cygwin terminal enter:
perl repack-bootimg-sgs4.pl boot.img
This yields boot-repack.img.
Here’s a dump of my cygwin session…
Code:
[email protected] /home
$ mkdir modify-boot-sgs4
[email protected] /home
$ cd modify-boot-sgs4
[email protected] /home/modify-boot-sgs4
$ pwd
/home/modify-boot-sgs4
[email protected] /home/modify-boot-sgs4
$ sh modify-boot-sgs4.sh boot.img
Unpack/Repack SGS4 ROM Boot Image
Initial Release (14 Jul 2013)
sendust7 @ xda developers
Current directory: /home/modify-boot-sgs4
Unpacking boot image...
Page size: 2048 (0x00000800)
Kernel size: 4961224 (0x004bb3c8)
Ramdisk size: 488535 (0x00077457)
Second size: 0 (0x00000000)
Board name:
Command line: androidboot.hardware=qcom user_debug=31 zcache
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
Unzipping: boot.img-ramdisk.gz to boot.img-ramdisk
1708 blocks
Press ENTER to repack boot image or CNTL C to exit (and modify ramdisk offline):
[COLOR="Blue"](Modify /ramdisk/default.prop then resume cygwin session)[/COLOR]
[email protected] /home/modify-boot-sgs4
$ perl repack-bootimg-sgs4.pl boot.img
find . | cpio -o -H newc | gzip > /home/modify-boot-sgs4/ramdisk-repack.cpio.gz
1708 blocks
./mkbootimg.exe --cmdline 'androidboot.hardware=qcom user_debug=31 zcache' --base 0x80200000 --kernel boot.img-kernel --ramdisk ramdisk-repack.cpio.gz -o boot-repack.img
Repacked boot image written to boot-repack.img
[email protected] /home/modify-boot-sgs4
$
7. Exit cygwin and drop boot-repack.img into loki-boot directory and rename to boot.img. Then 7-zip contents of loki-boot directory to loki-boot.zip (CNTL-A (Select All) then right-click > 7-zip > Add to “loki-boot.zip”).
8. Connect SGS4 to your ADB-enabled computer, then
adb push loki-boot.zip /external_sd/Download (or your favorite flash directory)
9. Boot to recovery and flash loki-boot.zip (takes a few seconds)
10. Reboot system and achieve “pre-rooted” ADB sessions on Liquid Smooth!
BTW here's a nice little app: https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot&hl=en
With Quick Boot, you can reboot to recovery via soft key, which is easier than booting to recovery from cold start.
Blessings. Enjoy!
Credits:
djrbliss @ xda developers and other contributors for the loki exploit: https://github.com/djrbliss/loki)
William Enck (split_bootimg): http://www.enck.org/
Android Development Team (Unpack, Edit, Repack Boot Images): http://www.android-dls.com/wiki/?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Cygwin Project Team: http://cygwin.com/who.html
Click to expand...
Click to collapse
Hi,
When I understand more I can't wait to revisit this instruction. But I love that it's here for me.
Ms. K:angel:
nevermind
nevermind
hello
Hi! I'm trying...but my ramdisk folder remains empty!
dump:
$ sh modify-boot-sgs4.sh boot.img
Unpack/Repack SGS4 ROM Boot Image
Initial Release (14 Jul 2013)
sendust7 @ xda developers
Current directory: /cygdrive/c/cygwin64/home/modify-boot-sgs4
Unpacking boot image...
Page size: 2048 (0x00000800)
Kernel size: 7157864 (0x006d3868)
Ramdisk size: 1142288 (0x00116e10)
Second size: 0 (0x00000000)
Board name:
Command line: console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
Unzipping: boot.img-ramdisk.gz to boot.img-ramdisk
modify-boot-sgs4.sh: line 23: cpio: command not found
_____________________________________________________
I'm doing this on 4.3 MJ7 I9505 kernel.
I assume I can unzip myself boot.img-ramdisk.gz, right?
ocaldini said:
Hi! I'm trying...but my ramdisk folder remains empty!
dump:
$ sh modify-boot-sgs4.sh boot.img
Unpack/Repack SGS4 ROM Boot Image
Initial Release (14 Jul 2013)
sendust7 @ xda developers
Current directory: /cygdrive/c/cygwin64/home/modify-boot-sgs4
Unpacking boot image...
Page size: 2048 (0x00000800)
Kernel size: 7157864 (0x006d3868)
Ramdisk size: 1142288 (0x00116e10)
Second size: 0 (0x00000000)
Board name:
Command line: console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
Unzipping: boot.img-ramdisk.gz to boot.img-ramdisk
modify-boot-sgs4.sh: line 23: cpio: command not found
_____________________________________________________
I'm doing this on 4.3 MJ7 I9505 kernel.
I assume I can unzip myself boot.img-ramdisk.gz, right?
Click to expand...
Click to collapse
Make sure you install the cpio packages for cygwin.
You can install additional packages by running the setup/install again.
You can also search for cpio via the search bar at the top left when presented with the list of packages.
Hope that helps.
Hello
Can anyone tell what is wrong? it keeps saying its doing it, but it does nothing...
[email protected] ~
$ cd modify-boot-sgs4
[email protected] ~/modify-boot-sgs4
$ pwd
/home/Home/modify-boot-sgs4
[email protected] ~/modify-boot-sgs4
$ sh modify-boot-sgs4.sh boot.img
Unpack/Repack SGS4 ROM Boot Image
Initial Release (14 Jul 2013)
sendust7 @ xda developers
Current directory: /home/Home/modify-boot-sgs4
Unpacking boot image...
Page size: 2048 (0x00000800)
Kernel size: 7195952 (0x006dcd30)
Ramdisk size: 1144962 (0x00117882)
Second size: 0 (0x00000000)
Board name:
Command line: console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
Directory: boot.img-ramdisk already exists
Press ENTER to repack boot image or CNTL-C to exit (and modify ramdisk offline):
Repacking boot image...
find . | cpio -o -H newc | gzip > /home/Home/modify-boot-sgs4/ramdisk-repack.cpio.gz
4560 blocks
./mkbootimg.exe --cmdline 'androidboot.hardware=qcom user_debug=31 zcache' --base 0x80200000 --kernel boot.img-kernel --ramdisk ramdisk-repack.cpio.gz -o boot-repack.img
sh: ./mkbootimg.exe: Permission denied
Althoug, now it is telling me Permission Denied, I don't know why, or how to change that in windows 7, but it wasn't giving me any errors before, it just wasn't writing the image
lijojohnson said:
Make sure you install the cpio packages for cygwin.
You can install additional packages by running the setup/install again.
You can also search for cpio via the search bar at the top left when presented with the list of packages.
Hope that helps.
Click to expand...
Click to collapse
Thank you, you helped me a lot! It worked!
Oh, when I searched for cpio I had to click on "default" ( and select "install" on the windows before clicking "advance"), to install it properly!
A VERY IMPORTANT INFORMATION:
I was trying with Cygwin 64 bit and I had problem repacking it.
I found out mkbootimg only works on Linux 32 bits.
So it is necessary to use Cygwin 32 bit version!
Finally it worked! Thanks a lot!
---------- Post added at 04:09 AM ---------- Previous post was at 03:18 AM ----------
Yeah, I did that...same result...the problem is with permissions, when I run it in compatibility mode, it tells me permission denied. I'm suspecting
it is a Windows 7 problem, mkbootimg.exe is saying permission denied. I appreciate the answer though. maybe an antivirus program is blocking it or something. my cygwin icon is showing the security essentials icon on it for some reason...i dunno, i'll research it some more and figure it out when I have time, thanks again
Keithgordon said:
Yeah, I did that...same result...the problem is with permissions, when I run it in compatibility mode, it tells me permission denied. I'm suspecting
it is a Windows 7 problem, mkbootimg.exe is saying permission denied. I appreciate the answer though. maybe an antivirus program is blocking it or something. my cygwin icon is showing the security essentials icon on it for some reason...i dunno, i'll research it some more and figure it out when I have time, thanks again
Click to expand...
Click to collapse
I'm doing this on windows 8.1 64bit with cygwin 32 bits. It works. I don't use antivirus, turn off security essentials and other system protecting programs, I'm sure you will do it.
Try it with boot.img from I9505 International , unpack and repack without problem , flash it and phone restart and vibrate constantly.
Any ideas how to fix this problem ?
As the title suggests I'm porting cyanogenmod to my old phone so when I root my hydro wave c6740n...I'll have the source & knowledge to do the same with the hydro wave as well, but back to my problem. I keep getting this error when ever i try to build the recovery.
build/core/tasks/kernel.mk:290: warning: overriding recipe for target '/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/kernel'
build/core/Makefile:46: warning: ignoring old recipe for target '/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/kernel'
Target boot image: /media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/boot.img
/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/boot.img maxsize=3514368 blocksize=135168 total=6680576 reserve=270336
error: /media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/boot.img too large (6680576 > [3784704 - 270336])
build/core/Makefile:570: recipe for target '/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/boot.img' failed
make: *** [/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/boot.img] Error 1
make: *** Deleting file '/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/boot.img'
#### make failed to build some targets (02:55 (mm:ss)) ####
it keeps stating its too large & i'm just stuck at this point..
also im trying to build recovery NOT the boot.img which I don't why it states boot.img instead of recovery.
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00380000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00480000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x08c60000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_FLASH_BLOCK_SIZE := 131072
aslo I am having trouble with the board config as well
BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 no_console_suspend=1 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 vmalloc=312M
BOARD_KERNEL_BASE := 0x
BOARD_KERNEL_PAGESIZE := 2048
I don't know what the kernel base would be in the mess below...
Kernel size 5820152
Kernel address 0x80208000
Ramdisk size 336324
Ramdisk address 0x82200000
Secondary size 0
Secondary address 0x81100000
Kernel tags address 0x80200100
Flash page size 2048
if you need more info to help just ask...I'm truly new to all this.
update-still not working, but...
Target boot image: /media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/boot.img
/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/boot.img maxsize=10040448 blocksize=135168 total=6676480 reserve=270336
Made boot image: /media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/boot.img
target StaticExecutable: recovery (/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/obj/EXECUTABLES/recovery_intermediates/LINKED/recovery)
target Symbolic: recovery (/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/symbols/system/bin/recovery)
target Strip: recovery (/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/obj/EXECUTABLES/recovery_intermediates/recovery)
----- Making recovery image ------
Copying baseline ramdisk...
Modifying ramdisk contents...
cp: cannot stat ‘/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/root/init.recovery.*.rc’: No such file or directory
build/core/Makefile:944: recipe for target '/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/ramdisk-recovery.img' failed
make: [/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/ramdisk-recovery.img] Error 1 (ignored)
/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/recovery.img maxsize=8177664 blocksize=135168 total=9250816 reserve=270336
error: /media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/recovery.img too large (9250816 > [8448000 - 270336])
build/core/Makefile:978: recipe for target '/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/recovery.img' failed
make: *** [/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/recovery.img] Error 1
make: *** Deleting file '/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/recovery.img'
#### make failed to build some targets (11:50 (mm:ss)) ####
build error!
I tried many things now, but I can't seem to get the recovery maxsize right during build...
im going to change the recovery size from 8000000 to 8177664
update 2-not working
----- Making recovery image ------
Copying baseline ramdisk...
Modifying ramdisk contents...
cp: cannot stat ‘/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/root/init.recovery.*.rc’: No such file or directory
build/core/Makefile:944: recipe for target '/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/ramdisk-recovery.img' failed
make: [/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/ramdisk-recovery.img] Error 1 (ignored)
/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/recovery.img maxsize=8162880 blocksize=135168 total=9250816 reserve=270336
error: /media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/recovery.img too large (9250816 > [8433216 - 270336])
build/core/Makefile:978: recipe for target '/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/recovery.img' failed
make: *** [/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/recovery.img] Error 1
make: *** Deleting file '/media/xstar97/Acer/Users/xstar97/Desktop/cm12.1/out/target/product/c6522n/recovery.img'
#### make failed to build some targets (10:29 (mm:ss)) ####
I'm honestly stuck trying to build the recovery
almost working
It's still saying that it's too large & i finally noticed i been missing a file called init.recovery.*.rc
I gotten boardconfig.mk all set up and correct
BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 no_console_suspend=1 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 vmalloc=312M
BOARD_KERNEL_BASE := 0x80200000
BOARD_KERNEL_PAGESIZE := 2048
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 10485760
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 8388608
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 674234368
BOARD_USERDATAIMAGE_PARTITION_SIZE := 1073741824
BOARD_FLASH_BLOCK_SIZE := 131072
recovery.fstab
# mount point fstype device [device2]
/boot mtd /dev/block/mmcblk0p7
/cache yaffs2 /dev/block/mmcblk0p15
/data yaffs2 /dev/block/mmcblk0p13
/misc mtd /dev/block/mmcblk0p17
/recovery mtd /dev/block/mmcblk0p18
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 /dev/block/mmcblk0p12
/sd-ext ext4 /dev/block/mmcblk0p2
do I need to add more?
such as ...0p1 to ..0p37
what else do I need to do?
I give up on cyanogenmod recovery
BUT, I found a perfect substitute for it...PhilZ recovery.img for hydro xtrm c6522 varients
I tested it & works like a charm, but the only downside is that you have to constantly connect your PC and boot(NOT FLASH) into PhilZ recovery.
so I made all steps easier by creating script(s) & provide the PhilZ recovery & stock recovery.
1. please open a terminal within the folder with all the files
2. you can either run & read the help.sh or just run setup.sh (basically the same info, but setup.sh starts the process)
to run the scripts please type "./setup.sh" without ""
the following info in the script will tell you what to do from then on.
NOTE:
DO NOT FLASH PhilZ recovery because it's NOT a standalone recovery.
click the link below to download from my dropbox, if by any chance that dropbox decides to stop allowing you to download, just PM & I WILL send you a new link personally.
philz.zip
You can check the scripts/edit them to your hearts content, but there's nothing in them that will harm your PC, device, or your mom..
also the credits
the one & only dev who built this recovery for us! is hroark13
i used x86 installer for installing bliss os in my hp laptop and this showing error install failed and log
================Installer Info================
Installer Directory:C:\Users\Ram Kankar\Downloads\Programs\Androidx86-Installv26.0003
Installer Version:2.6.0.0
Secure Boot ... Disabled
Manufacturer: HP
Model: HP Notebook
Product: 81EB
BIOS info:
HPQOEM - 0
F.24
INSYDE Corp. - F240000
Available GPU(s):
GPU: Intel(R) HD Graphics 520
=============[REQUIREMENTS CHECK]============
Administrator privilege ... ok
CPU Architecture: 9
CPU Name: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
OSVer: Microsoft Windows NT 10.0.16299.0
OperatingSystem Version ... ok
Windows Security: Access NVRAM Privilege ... Not All Set
System Firmware: UEFI
==========================================
====Install Started on 28-03-2018 19:43:28====
-ISO File: C:\Users\Ram Kankar\Downloads\Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1217_k4.9.iso
-TargetDrive: G
-UserData: 25165824
-Setup Directories...
-Folder Created: G:\AndroidOS
-Extracting ISO
#Launch:C:\Users\Ram Kankar\Downloads\Programs\Androidx86-Installv26.0003\7z.exe x "C:\Users\Ram Kankar\Downloads\Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1217_k4.9.iso" "kernel" "ramdisk.img" "initrd.img" "system.*" -oG:\AndroidOS
#Launch:C:\Users\Ram Kankar\Downloads\Programs\Androidx86-Installv26.0003\7z.exe e "C:\Users\Ram Kankar\Downloads\Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1217_k4.9.iso" "boot\grub\grub.cfg" -oG:\AndroidOS
-Creating Data.img
#Launch:C:\Users\Ram Kankar\Downloads\Programs\Androidx86-Installv26.0003\dd.exeif=/dev/zero of=G:\AndroidOS\data.img count=25165824
-Initialize Data.img
#Launch:C:\Users\Ram Kankar\Downloads\Programs\Androidx86-Installv26.0003\mke2fs.exe-F -t ext4 "G:\AndroidOS\data.img"
===Installing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
-Setup Boot Directory...
-Boot Folder Created: Z:\EFI\boot\
-Copy Boot files
-Add UEFI Entry
UEFI Init Fail
==============Revert Installation==============
-Cleaning up Bliss Directory ... G:\AndroidOS
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
Error Executing C:\Windows\System32\mountvol.exe with Args: Z: /S
Error output:
The directory is not empty.
-UEFI Init ... fail
-Cleaning up Bliss Directory ... Z:\EFI\boot\
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D
==========================================
uefidbg log
===logging started===
BootCount: 6
Boot0002,0 : Windows Boot Manager
Boot3002,1 : Internal Hard Disk or Solid State Disk
Boot0000,2 : Notebook Hard Drive - TOSHIBA MQ01ABD100
Boot2001,3 : EFI USB Device
Boot2002,4 : EFI DVD/CDROM
Fail to Read BootOptions, 5
BootCount: 6
Boot0002,0 : Windows Boot Manager
Boot3002,1 : Internal Hard Disk or Solid State Disk
Boot0000,2 : Notebook Hard Drive - TOSHIBA MQ01ABD100
Boot2001,3 : EFI USB Device
Boot2002,4 : EFI DVD/CDROM
Fail to Read BootOptions, 5
BootCount: 6
Boot0002,0 : Windows Boot Manager
Boot3002,1 : Internal Hard Disk or Solid State Disk
Boot0000,2 : Notebook Hard Drive - TOSHIBA MQ01ABD100
Boot2001,3 : EFI USB Device
Boot2002,4 : EFI DVD/CDROM
Fail to Read BootOptions, 5
plz give me solution for this error , thanks in advance
Looks like it couldn't mount the UEFI partition. You should make sure that the Z: mount location isn't taken already
electrikjesus said:
Looks like it couldn't mount the UEFI partition. You should make sure that the Z: mount location isn't taken already
Click to expand...
Click to collapse
and how do we check that? im looking for new android os systems since i cant boot to phoenix os because my pc is uefi and i dont know how to fix it, but still cant install bliss wich is the OS that caught more my attention, plz help
UEFI Init Fail
electrikjesus said:
Looks like it couldn't mount the UEFI partition. You should make sure that the Z: mount location isn't taken already
Click to expand...
Click to collapse
I encountered exactly the same problem as the OP did, and no, the Z: mount location isn't taken. Any solution?
================Installer Info================
Installer Directory:C:\Users\Administrator\AppData\Local\Temp\RarSFX0
Installer Version:2.6.0.0
Secure Boot ... Disabled
Manufacturer: HP
Model: HP Notebook
Product: 81EE
BIOS info:
HPQOEM - 0
F.43
INSYDE Corp. - F430000
Available GPU(s):
GPU: AMD Radeon (TM) R5 M330
GPU: Intel(R) HD Graphics 620
=============[REQUIREMENTS CHECK]============
Administrator privilege ... ok
CPU Architecture: 9
CPU Name: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
OSVer: Microsoft Windows NT 10.0.17134.0
OperatingSystem Version ... ok
Windows Security: Access NVRAM Privilege ... Not All Set
System Firmware: UEFI
==========================================
====Install Started on 29-Oct-18 10:31:06 PM====
-ISO File: D:\Android\Bliss-v10.1-Beta-android_x86_64-NIGHTLY-20180808-0022_k4.16.5-blissified_2.iso
-TargetDrive: C
-UserData: 18853396
-Setup Directories...
-Folder Created: C:\AndroidOS
-Extracting ISO
#Launch:C:\Users\Administrator\AppData\Local\Temp\RarSFX0\7z.exe x "D:\Android\Bliss-v10.1-Beta-android_x86_64-NIGHTLY-20180808-0022_k4.16.5-blissified_2.iso" "kernel" "ramdisk.img" "initrd.img" "system.*" -oC:\AndroidOS
#Launch:C:\Users\Administrator\AppData\Local\Temp\RarSFX0\7z.exe e "D:\Android\Bliss-v10.1-Beta-android_x86_64-NIGHTLY-20180808-0022_k4.16.5-blissified_2.iso" "boot\grub\grub.cfg" -oC:\AndroidOS
-Creating Data.img
#Launch:C:\Users\Administrator\AppData\Local\Temp\RarSFX0\dd.exeif=/dev/zero of=C:\AndroidOS\data.img count=18853396
-Initialize Data.img
#Launch:C:\Users\Administrator\AppData\Local\Temp\RarSFX0\mke2fs.exe-F -t ext4 "C:\AndroidOS\data.img"
===Installing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
-Setup Boot Directory...
-Boot Folder Created: Z:\EFI\boot\
-Copy Boot files
-Add UEFI Entry
UEFI Init Fail
==============Revert Installation==============
-Cleaning up Bliss Directory ... C:\AndroidOS
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
Error Executing C:\Windows\System32\mountvol.exe with Args: Z: /S
Error output:
The directory is not empty.
-UEFI Init ... fail
-Cleaning up Bliss Directory ... Z:\EFI\boot\
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D
==========================================
how to wipe Z: partition? i got same problem pls help me
---------- Post added at 01:43 PM ---------- Previous post was at 01:16 PM ----------
electrikjesus said:
Looks like it couldn't mount the UEFI partition. You should make sure that the Z: mount location isn't taken already
Click to expand...
Click to collapse
How to solve it? since we're not expert why you dont help us?
VMolina141 said:
and how do we check that? im looking for new android os systems since i cant boot to phoenix os because my pc is uefi and i dont know how to fix it, but still cant install bliss wich is the OS that caught more my attention, plz help
Click to expand...
Click to collapse
Just find out bliss broke my Z: dir after uninstall it,, and now i cant install another Android OS because it. Damn god im regret using bliss
bad primary partition zero petition ends in the final partial cylinder
is the error i am getting when trying to install bliss os
I know this thread is old but this may help future people googling a solution
Here's what I did to fix this error...
==============Revert Installation==============
-Cleaning up Bliss Directory ... C:\AndroidOS
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
Error Executing C:\Windows\System32\mountvol.exe with Args: Z: /S
Error output:
The directory is not empty.
-UEFI Init ... fail
-Cleaning up Bliss Directory ... Z:\EFI\boot\
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D
==========================================
I ran CMD as Administrator and ran the command
mountvol Z: /d
You can also try running CMD and entering the command in "Safe Mode" as suggested on other threads
Bliss OS is a ****ing disaster. Ruined my ****ing day. Didn't install for some reason and got rid of winload.efi also
Poads said:
I know this thread is old but this may help future people googling a solution
Here's what I did to fix this error...
==============Revert Installation==============
-Cleaning up Bliss Directory ... C:\AndroidOS
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
Error Executing C:\Windows\System32\mountvol.exe with Args: Z: /S
Error output:
The directory is not empty.
-UEFI Init ... fail
-Cleaning up Bliss Directory ... Z:\EFI\boot\
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D
==========================================
I ran CMD as Administrator and ran the command
mountvol Z: /d
You can also try running CMD and entering the command in "Safe Mode" as suggested on other threads
Click to expand...
Click to collapse
Not working for me, unfortunately
Aaaahhhh yes, it feels good to not feel so much hate alone towards Bliss at the god that moment!!!!
Poads said:
I know this thread is old but this may help future people googling a solution
Here's what I did to fix this error...
==============Revert Installation==============
-Cleaning up Bliss Directory ... C:\AndroidOS
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
Error Executing C:\Windows\System32\mountvol.exe with Args: Z: /S
Error output:
The directory is not empty.
-UEFI Init ... fail
-Cleaning up Bliss Directory ... Z:\EFI\boot\
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D
==========================================
I ran CMD as Administrator and ran the command
mountvol Z: /d
You can also try running CMD and entering the command in "Safe Mode" as suggested on other threads
Click to expand...
Click to collapse
after this, i cant the drive i want to install in?? no drive z
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello,
I own a samsung xcover 3 (sm-g388f, android lollitop) and out of curiosity I start to be interested in the android system. I downloaded the ROM and get back the file boot.img, i try to get the file Image.gz (kernel) with Android Image Kitchen.
Code:
./unpackimg.sh boot.img
I get:
Code:
Android Image Kitchen - UnpackImg Script
by osm0sis @ xda-developers
Supplied image: boot.img
Setting up work folders...
Image type: AOSP-PXA
Footer with "SEAndroid" type detected.
Splitting image to "split_img/"...
BOARD_KERNEL_CMDLINE
BOARD_KERNEL_BASE 0x10000000
BOARD_NAME
BOARD_PAGE_SIZE 2048
BOARD_KERNEL_OFFSET 0x00008000
BOARD_RAMDISK_OFFSET 0x01000000
BOARD_SECOND_OFFSET 0x00f00000
BOARD_TAGS_OFFSET 0x00000100
BOARD_DT_SIZE 475136
BOARD_UNKNOWN 0x03000000
Unpacking ramdisk (as root) to "ramdisk/"...
Compression used: gzip
4739 blocs
Done!
I get the file boot.img-kernel, i use dumpimage:
Code:
./dumpimage -i boot.img-kernel -p 0 Image.gz
The return is:
Code:
./dumpimage: invalid option -- 'i'
Usage: ./dumpimage -l image
-l ==> list image header information
./dumpimage [-T type] [-p position] [-o outfile] image
-T ==> declare image type as 'type'
-p ==> 'position' (starting at 0) of the component to extract from image
-o ==> extract component to file 'outfile'
./dumpimage -h ==> print usage information and exit
./dumpimage -V ==> print version information and exit
I try the command:
Code:
./dumpimage -T boot.img-kernel -p 0 Image.gz
i get:
Code:
./dumpimage: Invalid type
I no longer see what to do, here is the boot.img
If anyone has an idea I’m interested
Thanks