Greetings-
I am trying to build my first Kernel, and following this tutorial http://forum.xda-developers.com/showthread.php?t=1748297 , I am getting the following errors and some success:
Code:
[email protected]:~/android/kernel/samsung/CivZ-KatTurbine-SM-N9005-900T-master# patch -p1 < kernelPatch
(Patch is indented 4 spaces.)
patching file drivers/cpufreq/cpufreq_interactivex.c
(Patch is indented 4 spaces.)
patching file drivers/cpufreq/cpufreq_lionheart.c
(Patch is indented 4 spaces.)
patching file drivers/cpufreq/cpufreq_ondemandx.c
(Patch is indented 4 spaces.)
patching file drivers/cpufreq/Kconfig
Hunk #1 succeeded at 94 with fuzz 2 (offset -5 lines).
Hunk #2 FAILED at 132.
Hunk #3 succeeded at 167 with fuzz 2 (offset -5 lines).
Hunk #4 FAILED at 244.
2 out of 4 hunks FAILED -- saving rejects to file drivers/cpufreq/Kconfig.rej
(Patch is indented 4 spaces.)
patching file drivers/cpufreq/Makefile
Hunk #1 FAILED at 7.
1 out of 1 hunk FAILED -- saving rejects to file drivers/cpufreq/Makefile.rej
(Patch is indented 4 spaces.)
patching file include/linux/cpufreq.h
Hunk #1 FAILED at 363.
Hunk #2 FAILED at 372.
2 out of 2 hunks FAILED -- saving rejects to file include/linux/cpufreq.h.rej
As you can see I put the patch in the same directory which was result of my unpacking the source zip file from Samsung. Am I doing this wrong? Should the patch be 100% successful?
I am S-Off and have tried both TWRP and CWM and keep getting - set_metadata: some changes failed Installer Error (Status 7). I have also tried Venom ROM to and get the same error. Should I go stock and re root, it seems like the installer isnt getting access to the directories? Thanks
AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
ROM Name : Android Revolution HD
ROM Version : 9.1
ROM Author : mike1986
Device : HTC One (M8)
Start at : Tue Jul 15 23:27:55 2014
I:emmc_scan_partitions:[partition_count:0] [allocat_num:50]
load_volume_table: Can't get the /proc/emmc table
=================================
Android Revolution HD by mike1986
=================================
>>> Formatting partitions
about to run program [/sbin/umount] with 2 args
umount: can't umount /system: Invalid argument
run_program: child exited with status 1
about to run program [/sbin/mke2fs] with 6 args
mke2fs 1.41.14 (22-Dec-2010)
Warning: the fs_type small is not defined in mke2fs.conf
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
5632 inodes, 22528 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=25165824
1 block group
32768 blocks per group, 32768 fragments per group
5632 inodes per group
Writing inode tables: 0/1done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 21 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
about to run program [/sbin/mount] with 2 args
mount: mounting /dev/block/mmcblk0p47 on /cache failed: Device or resource busy
run_program: child exited with status 255
about to run program [/sbin/mount] with 2 args
mount: mounting /dev/block/mmcblk0p48 on /data failed: Device or resource busy
run_program: child exited with status 255
about to run program [/tmp/wipe.sh] with 1 args
>>> Mounting partitions
about to run program [/sbin/mount] with 2 args
about to run program [/sbin/mount] with 2 args
mount: mounting /dev/block/mmcblk0p48 on /data failed: Device or resource busy
run_program: child exited with status 255
>>> Cleaning process
about to run program [/tmp/clean.sh] with 1 args
>>> Writing Data & System
about to run program [/sbin/busybox] with 5 args
about to run program [/sbin/sync] with 1 args
>>> Copying U.S. Verizon related files
>>> Installing Google Chrome
>>> Installing Google Maps & Google Street
>>> Installing Google Music
>>> Installing Google Plus
>>> Installing Google Now
>>> Installing Google Keep
>>> Installing Google Hangouts
>>> Installing Google YouTube
>>> Installing Google Drive
>>> Installing ES File Explorer
>>> Installing Facebook
>>> Installing Adobe Flash Player
>>> Installing Adobe Reader
>>> Installing Twitter
>>> Installing EXT4 Performance Tweak
about to run program [/tmp/ext4] with 1 args
tune2fs 1.42.9 (28-Dec-2013)
tune2fs 1.42.9 (28-Dec-2013)
tune2fs 1.42.9 (28-Dec-2013)
>>> Installing SQLite Tweaks
>>> Installing Seeder
>>> Installing Bytecode Verification disabler
about to run program [/tmp/dalvik.sh] with 1 args
>>> Installing Sense 6 Toolbox & Xposed
>>> Installing Harman & Kardon Sound Mod
about to run program [/tmp/hk.sh] with 1 args
sed: write error
sed: write error
run_program: child exited with status 4
>>> Creating toolbox symlinks
>>> Creating additional symlinks
>>> Installing busybox
about to run program [/system/xbin/busybox] with 4 args
>>> Setting permissions
ApplyParsedPerms: setcap of /system/bin/run-as to c0 failed: No space left on device
script aborted: set_metadata: some changes failed
set_metadata: some changes failed
Installer Error (Status 7)
End at : Tue Jul 15 23:29:11 2014
Adabow12 said:
I am S-Off and have tried both TWRP and CWM and keep getting - set_metadata: some changes failed Installer Error (Status 7). I have also tried Venom ROM to and get the same error. Should I go stock and re root, it seems like the installer isnt getting access to the directories? Thanks
End at : Tue Jul 15 23:29:11 2014
Click to expand...
Click to collapse
You s-off an have flashed SuperSU in twrp? Also uninstalled weak sauce an SuperSU prior?
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Tigerstown said:
You s-off an have flashed SuperSU in twrp? Also uninstalled weak sauce an SuperSU prior?
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes weaksauce is uninstalled and I installed SuperSU in CWM and it is working correctly from what I can see.I can run apps that need SU access. I have also made sure I installed the VZW TWRP and CWM and no success on either. I just got this phone 2 days ago.
Adabow12 said:
Yes weaksauce is uninstalled and I installed SuperSU in CWM and it is working correctly from what I can see.I can run apps that need SU access. I have also made sure I installed the VZW TWRP and CWM and no success on either. I just got this phone 2 days ago.
Click to expand...
Click to collapse
So I just answered my own question. I had been trying to install the ROM from the SD card and figured I would copy to the internal SD and give it a shot and that fixed the issues and the ROM installed no problem. Hope this helps anyone else out there having this problem. Thanks
Hello. I have problem with cyanogenmod 13 ported from MtkRoms. When i try flash rom, latest TWRP 2.8.2.0 give me that error :
apply parsed perms: lsetfilecon of /system/lost+found to u : object_r:system_file:s0 failed: Operation not supported on transport endpoint set_metadata_recursive: some changes failed
E: Error executing updater binary in zip
I try cm 12.1 or Resurrection Remix working fine. "Asserts" in updater-script don't exist.
My phone it is Goclever Insignia 500 here is specs:
720 x 1280 px (5,00") 294 ppi
CPU: MediaTek MT6582 4x1.3GHZ
GPU: ARM Mali-400 MP2 @500 MHz
1GB Ram
Any ideas?
Hello,
Welcome to XDA.
You can edit the updater script so that it recognizes your model number correctly by changing the line in the script for "ro.product".
Edit that line and enter the correct ro.product value for your device model(ro.product can be found in your stock build.prop file if you don't know what it is) then save the file and repackage everything correctly for flashing.
Or you can just remove the ro.product line from the script completely but that can be risky depending on anything you didn't get right in your porting of the ROM.
Hi there,
I have downloaded and installed flashtool which recognises my phone but it wont allow me to do anything else as it states 'root access denied' ive also had an error Please check your Phone and 'ALLOW' Superuseraccess! Im stuck guys and really need some help here, please!
Here is the log from the flashtool so if anyone can guide me then i really appreciate it. I have turned USB Debugging on too.
27/054/2016 17:54:17 - INFO - Flashtool Version 0.9.22.3 built on 08-06-2016 22:30:00
27/054/2016 17:54:17 - INFO - Executing search strategies to find proxy selector
27/054/2016 17:54:17 - INFO - No proxy found for IE. Trying next one
27/054/2016 17:54:17 - INFO - Strategy firefox failed trying next one : No Firefox installation found
27/054/2016 17:54:17 - INFO - No proxy found for java. Trying next one
27/054/2016 17:54:17 - INFO - Syncing devices from github
27/054/2016 17:54:17 - INFO - Opening devices repository.
27/054/2016 17:54:17 - INFO - Scanning devices folder for changes.
27/054/2016 17:54:27 - INFO - Pulling changes from github.
27/054/2016 17:54:28 - INFO - Quietly closing devices repository.
27/054/2016 17:54:28 - INFO - Devices sync finished.
27/054/2016 17:54:28 - INFO - Loading devices database
27/054/2016 17:54:28 - INFO - Loaded 94 devices
27/054/2016 17:54:28 - INFO - Starting phone detection
27/054/2016 17:54:28 - INFO - Device disconnected
27/055/2016 17:55:24 - INFO - Device connected with USB debugging off
27/055/2016 17:55:24 - INFO - For 2011 devices line, be sure you are not in MTP mode
27/055/2016 17:55:24 - INFO - Device connected with USB debugging on
27/055/2016 17:55:25 - INFO - Connected device : Sony Xperia Z3
27/055/2016 17:55:25 - INFO - Installed version of busybox : N/A
27/055/2016 17:55:25 - INFO - Android version : 4.4.4 / kernel version : 3.4.0-perf-g0961cdf / Build number : 23.0.A.2.93
27/055/2016 17:55:25 - INFO - Root access denied
27/055/2016 17:55:48 - WARN - Please check your Phone and 'ALLOW' Superuseraccess!
27/055/2016 17:55:48 - INFO - Root access denied
27/004/2016 18:04:44 - INFO - Flash canceled
27/005/2016 18:05:16 - INFO - Flash canceled
27/005/2016 18:05:48 - INFO - Pushing C:\Users\markg\.flashTool\devices\busybox\1.20.2\busybox to /data/local/tmp/busybox
27/005/2016 18:05:48 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\su to /data/local/tmp/su
27/005/2016 18:05:48 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
27/005/2016 18:05:49 - ERROR - Illegal key size or default parameters
27/011/2016 18:11:53 - INFO - Pushing C:\Users\markg\.flashTool\devices\busybox\1.20.2\busybox to /data/local/tmp/busybox
27/011/2016 18:11:54 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\su to /data/local/tmp/su
27/011/2016 18:11:54 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
27/011/2016 18:11:55 - ERROR - Illegal key size or default parameters
27/011/2016 18:11:59 - INFO - Pushing C:\Users\markg\.flashTool\devices\busybox\1.20.2\busybox to /data/local/tmp/busybox
27/012/2016 18:12:00 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\su to /data/local/tmp/su
27/012/2016 18:12:00 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\Superuser.apk to /data/local/tmp/Superuser.apk
27/012/2016 18:12:00 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\install-recovery.sh to /data/local/tmp/install-recovery.sh
27/012/2016 18:12:01 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\99SuperSUDaemon to /data/local/tmp/99SuperSUDaemon
27/012/2016 18:12:01 - ERROR - Illegal key size or default parameters
27/012/2016 18:12:59 - WARN - Please check your Phone and 'ALLOW' Superuseraccess!
27/012/2016 18:12:59 - INFO - Root access denied
27/013/2016 18:13:06 - INFO - List of connected devices (Device Id) :
27/013/2016 18:13:06 - INFO - - USB\VID_0FCE&PID_61BA\BH90YS7H1L Driver installed : true
27/013/2016 18:13:06 - INFO - - USB\VID_0FCE&PID_61BA&MI_00\6&2A43DAAB&0&0000 Driver installed : true
27/013/2016 18:13:06 - INFO - - USB\VID_0FCE&PID_61BA&MI_01\6&2A43DAAB&0&0001 Driver installed : true
27/013/2016 18:13:06 - INFO - List of ADB devices :
27/013/2016 18:13:06 - INFO - - BH90YS7H1L (Device : D6603. Model : D6603)
27/013/2016 18:13:06 - INFO - List of fastboot devices :
27/013/2016 18:13:06 - INFO - - none
No man, you need to follow the guide for rooting. 291 firmware, download all the things needed in that post 2 kernels and root and recovery tool) , after you downloaded. 291 kernel and .575 kernel, you need to unpack both and repack separately with extension .ftf , copy them to firmware folder (ex. c:/users/XX/.flashtool/firmware)
In flashtool click lighting icon select flashmode and find your 575 kernel.ftf select it and follow instructions on screen, now open your recovery tool and open install.bat, now connect phone again to PC be sure u have usb debugging and mtp mode selected. After the process end your phone should reboot in recovery, flash a supersu.zip ( u can find it on xda somewhere) after you successfully flashed supersu u will get root, now switch to flashtool and flash the same way like you did kernel 291
And you're done
Wysłane z mojego D6603 przy użyciu Tapatalka
Wooby said:
No man, you need to follow the guide for rooting. 291 firmware, download all the things needed in that post 2 kernels and root and recovery tool) , after you downloaded. 291 kernel and .575 kernel, you need to unpack both and repack separately with extension .ftf , copy them to firmware folder (ex. c:/users/XX/.flashtool/firmware)
In flashtool click lighting icon select flashmode and find your 575 kernel.ftf select it and follow instructions on screen, now open your recovery tool and open install.bat, now connect phone again to PC be sure u have usb debugging and mtp mode selected. After the process end your phone should reboot in recovery, flash a supersu.zip ( u can find it on xda somewhere) after you successfully flashed supersu u will get root, now switch to flashtool and flash the same way like you did kernel 291
And you're done
Wysłane z mojego D6603 przy użyciu Tapatalka
Click to expand...
Click to collapse
OK, So do you mean i need all 3 of these?
File Type: zip kernel291.zip - [Click for QR Code] (14.40 MB, 5270 views)
File Type: zip kernel575.zip - [Click for QR Code] (14.47 MB, 6230 views)
File Type: zip recovery_for_mm575.zip - [Click for QR Code] (4.56 MB, 6168 views)
yes it is them files sorry, ok so can i unpack and repack the two kernel files using winzip? If so could you explain how to do it so i know i get it right? regards Mark
You need to unpack the files inside a zip, select them all right click "add to archive" and add in the name of file ".ftf"
Wysłane z mojego D6603 przy użyciu Tapatalka
Wooby said:
You need to unpack the files inside a zip, select them all right click "add to archive" and add in the name of file ".ftf"
Wysłane z mojego D6603 przy użyciu Tapatalka
Click to expand...
Click to collapse
Thanks buddy one more question, when i add them to a archive, under archive format do i select RAR, RAR5 or ZIP?
ive done exactly as you have said but when i click the lightening symbol, then click flashmode the firmware selector box that pops up it does not show the .ftf files. I have put them into the correct folder
Are the kernels in ftf format?
Ex. Kernel575.ftf
Wysłane z mojego D6603 przy użyciu Tapatalka
Wooby said:
Are the kernels in ftf format?
Ex. Kernel575.ftf
Wysłane z mojego D6603 przy użyciu Tapatalka
Click to expand...
Click to collapse
yes, ive managed to sort that by selecting the zip box. Now ive donne the first part and flashed the 575 kernel and followed the instructions, got to the screen where it says to unplug phone, press and hold the volume down key and reconnect it which i then got 'root access allowed' in the log
Now the phone appears to be just turning on and off onto a black screen and when i run the install.bat file it shows:
daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb server version (32) doesn't match this client (36); killing...
* daemon started successfully *
But nothing else is happening other than the mobile going off and on by itself
Also in the flashtool it shows:
28/043/2016 14:43:19 - ERROR - Cannot identify your device.
28/043/2016 14:43:19 - INFO - Selecting from user input
28/043/2016 14:43:25 - INFO - Connected device : D66XX
28/043/2016 14:43:25 - INFO - Installed version of busybox : N/A
28/043/2016 14:43:25 - INFO - Android version : / kernel version : / Build number :
28/043/2016 14:43:25 - INFO - Phone in recovery mode
28/043/2016 14:43:25 - INFO - Root Access Allowed
28/043/2016 14:43:40 - INFO - Device connected with USB debugging on
28/043/2016 14:43:46 - INFO - Connected device : Sony Xperia Z3
28/043/2016 14:43:46 - INFO - Installed version of busybox : N/A
28/043/2016 14:43:46 - INFO - Android version : 4.4.4 / kernel version : / Build number : 23.0.A.2.93
28/043/2016 14:43:46 - INFO - Phone in recovery mode
28/043/2016 14:43:46 - INFO - Root Access Allowed
You need to close flashtool first, before u can flash recovery with that tool
Wysłane z mojego D6603 przy użyciu Tapatalka
Ok so i closed flashtool ad then run recovery tool and the phone continues to turn on and off every 10 secs or so, then when it turns on the recovery tool recognises the phone but it turns off again before it finishes what its supposed to do i think
this is what it shows in the recovery tool:
Device Detected!
Installing ...
error: closed
adb: error: connect failed: no devices/emulators found
adb: error: connect failed: no devices/emulators found
adb: error: connect failed: no devices/emulators found
adb: error: connect failed: no devices/emulators found
adb: error: connect failed: no devices/emulators found
adb: error: connect failed: no devices/emulators found
adb: error: connect failed: no devices/emulators found
adb: error: connect failed: no devices/emulators found
adb: error: connect failed: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
Finished!
Rebooting into TWRP recovery ...
error: no devices/emulators found
Press any key to continue . . .
You need to have your phone in mtp mode plugged in, not in charging only
Wysłane z mojego D6603 przy użyciu Tapatalka
Wooby said:
You need to have your phone in mtp mode plugged in, not in charging only
Wysłane z mojego D6603 przy użyciu Tapatalka
Click to expand...
Click to collapse
How do i do that it wont turn on anymore it like stuck in a loop where it turns on and off but only has a black screen when it turns on, then turns off after about 10 secs, and constantly just does that
My phone wont let me do anything more with it , am i able to go back to the start with it? What do / can i do now?
so dumb. just go easyway: unlock bootloader if not done. instal the 7.0 previewrom install fotarecovery and then u can go on and install any rom u want. so sumb to stay at 4.4.4 there is 0 benefit to be on ****ty 4.4.4 u dont nee root to have a recovery and most good rom nowadays have root packed in. recommning ExistenZ rom or the one in deelopment 14.1 unoficial CM. good day sir.