Related
Ok so I don't have this device and there is a bunch of people that want to try it so here you go.
If you brick your **** don't blame me! Its a test build Don't even know if it will boot!
Adb me some logcats and we can get it working
logcat.miui.us and paste link I will see what I can do!
I would hope others would step in and help out with this!
Test 15 http://www.mediafire.com/?c1osls4cz4lnizg
Last test of the night
nattskift said:
"[3a] Revolutionary CWM
(i) download Revolutionary shutteru CWM recovery from here
(ii) reboot device in bootloader mode > plug in usb cable until u see FASTBOOT USB on device screen
(iii) now in adb type : fasboot flash recovery cwm-4.0.1.4-shooteru.img
(iv) Done."
This file.
Click to expand...
Click to collapse
just in case
ok last one for fun!
not a fan of miui but I'm willing to give it a try . what's the chances of a brick with this ?
shouldn't effect recouvery right so i can always restore ?
Garrytheogre said:
not a fan of miui but I'm willing to give it a try . what's the chances of a brick with this ?
shouldn't effect recouvery right so i can always restore ?
Click to expand...
Click to collapse
yeah I included the stock boot.img so you should be fine there is no recovery added so will not brick you device.
but test at your risk.
I have been asked a bunch of times to help out. if there is a aosp kernel that would help a bunch
will this suffice
forum.xda-developers.com/showthread.php?t=1313117
got an error 6 on flashing then it aborts the flash
Tld you guys he was working on it its always good to follow ppl on Twitter. Right Scott LOL
Sent from my PG86100 using xda premium
Garrytheogre said:
will this suffice
forum.xda-developers.com/showthread.php?t=1313117
got an error 6 on flashing then it aborts the flash
Click to expand...
Click to collapse
Cwm or twrp?
Sent from my PG86100 using XDA App
revolutionary cwm
ok test two with the kernel you said http://www.mediafire.com/?9bx2vmhd0ec82pg
Just making a backup now and will test it and report back.
By the way, does it support multilanguage like Arabic? Do we need to choose kernel ? Thanks
Hi,
Tried and get the error status 7.
coreless88 said:
Hi,
Tried and get the error status 7.
Click to expand...
Click to collapse
test 3 http://www.mediafire.com/?5xlvk3bsccjs4e3
I will be following this closely and will try flash tonight. How exciting its like xmas!
Sent from my Evo 3D GSM...bring on the AOSP!!!
Downloaded.
Error during flash.
Code:
Installing update...
mount() expects 4 args. got 3
E:Error in /sdcard/roms/SHOOTERU-MIUI-1.11.11.11-TEST-BUILD-3.zip
(Status 7)
Installation aborted.
Recovery.log coming up...
it does not work gave me status error 7
this one when ran on test 2, will check test 3 and report back
maaafeb05 said:
it does not work gave me status error 7
Click to expand...
Click to collapse
test3?
seems weird
Recovery.log:
Code:
-- Installing: /sdcard/rom/SHOOTERU-MIUI-1.11.11-TEST-BUILD-3.zip
Finding update package...
I:Update location: /sdcard/rom/SHOOTERU-MIUI-1.11.11-TEST-BUILD-3.zip
Opening update package...
Installing update...
Creating filesystem with parameters:
Size: 838859776
Block size: 4096
Blocks per group: 32768
Inodes per group: 7315
Inode size: 256
Journal blocks: 3200
Label:
Blocks: 204799
Block groups: 7
Reserved block group size: 55
Created filesystem with 11/51205 inodes and 6651/204799 blocks
script aborted: mount() expects 4 args, got 3
mount() expects 4 args, got 3
E:Error in /sdcard/rom/SHOOTERU-MIUI-1.11.11-TEST-BUILD-3.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/rom/SHOOTERU-MIUI-1.11.11-TEST-BUILD-3.zip")
Ok updater script and build prop are jacked up
scott951 said:
Ok updater script and build prop are jacked up
Click to expand...
Click to collapse
The two lines that contain mount and only has three args are
mount("MTD", "userdata", "/data");
mount("MTD", "system", "/system")
Must be one of those right?
Is there anything i can do to help?
Hallo, after two days of trying to make kexec working, got it working! Its based on hard boot kexec! We can create now multiboot menu and boot multi roms without need for flashing them! Will make this thread updated including files, kernel and instructions!
munjeni said:
Hallo, after two days of trying to make kexec working, got it working! Its based on hard boot kexec! We can create now multiboot menu and boot multi roms without need for flashing them! Will make this thread updated including files, kernel and instructions!
Click to expand...
Click to collapse
and probably now guys with locked bootloader can boot roms requiring custom kernels
DevSwift1 said:
and probably now guys with locked bootloader can boot roms requiring custom kernels
Click to expand...
Click to collapse
NO because kernel need enabled kexec and reguire some other modifications whick is not exist on stock kernel!!!
Tried to boot stock kernel but failed, seems not stable kexec by now! Need help!
Here is kernel changes (3 commits by Aug.09.2013) -> https://github.com/munjeni/android_kernel_xperiago/commits/jb-dev seems there is problem with clean reboot! Got kexec working with usind zImage from the same kernel version but seems when there is another kernel version its fail! I think it fail on my reboot function implementation! Need help to solve these things!
Got ansfer by self. Stock kernel and everyother without kexec patch ca not be loaded more info here -> http://forum.xda-developers.com/showthread.php?p=44077327
Tomorow will make it better, hope perfectly working.
Ok, lets go multiboot development!
My experience using kexec:
- since hard reboot owerwrite new kernel and ramdisk, I disabled hard reboot. So we need shutdown cpu instead of using function reboot! Since we have no shutdown cpu function we have very slow boot after executing new kernel and ramdisk (curently I am satisfied with slow boot because kexec can boot new kernel and ramdisk, yes its slow but working )
What is needed for kexec boot:
- kexec can not boot non kexec based kernels
- kexec can boot only kexec enabled kernel which mean only kernel which have my kexec patch (you can patch your kernel using kexec patch from my git)
- suported phones by now is only Sola and Go
My idea for multiboot by now:
- making boot menu based on modified CWM recovery
Modified CWM recovery plan:
- create new recovery and add new sub menu for multiboot feature
CWM multiboot menu idea:
- here we can write kexec multiboot functions
CWM kexec function idea:
- mount system, cache, userdata partition from external sdcard EXT4 partitons and mount them (only if these partions is created by you on your sdcard !!! We can create an small submenu for creating these partitons if these partitons not exist, but not now, we can do it later after creating simple kexec main menu))
- after mounting these partitions we can:
- boot android from allready installed android from these partitions
- ability to install new android to these partiton and boot them
Lets go! Before I start making new CWM, I need better ideas! What you think how we can do it??? Waiting your ideas!!!
Maybe we can do it without using CWM???
So, how about another kernel or rom which isn't supporting kexec yet?
Sent from risahikari
munjeni said:
Lets go! Before I start making new CWM, I need better ideas! What you think how we can do it??? Waiting your ideas!!!
Maybe we can do it without using CWM???
Click to expand...
Click to collapse
I cannot think of a way to do this without involving CWM. But we could make use of the volume buttons to select the ROM on boot (by mounting the appropriate partition based on the volume button that has been pressed down when the bootsplash screen is displayed). However this would limit us to the number of ROMs that can be installed to two (or max 3, if we have an option to set a default ROM to boot if no button is pressed).
Brilliant work by the way. You are Godlike! :victory:
itachilinux said:
So, how about another kernel or rom which isn't supporting kexec yet?
Sent from risahikari
Click to expand...
Click to collapse
Simple not supported!
First of all we need to create ramdisk which will boot android located on external sdcard, than if we get it working we can play with kexec. I need your help! If some one get android working from external sdcard than I will continue further. I am allso playing now with new ramdisk and trying to get external android booting!!
Our multiboot is not ready. Only ready is kexec tool and kexec kernel. Our multiboot feature is not yet implemented. Our multiboot is in plan and our multiboot need ideas!
can this be of any help?
http://forum.xda-developers.com/showpost.php?p=42057833&postcount=1
github:
https://github.com/tux-mind/tf201-dev
Changed fstab, recovery.fstab and sony fstab device paths to point to the external sdcard partition, modified updater_script paths, rebooted to the recovery, installed rom to the external sdcard partitions, rebooted, after abnormaly slow boot system booted but is abnormally unresponsive, so I deleted and reverted back to the emmc boot. Sory guys I am stopping here until some one get android booted from sdcard! I have no free time to play with external boot. When you done it I will continue
Any one have idea what is use of the fota kernel??? Got fota kernel and ramdisk kexeced and booted, found some tools in sbin folder, there is fota tools, for example after exacution of the fota-ua got this output:
./fota-ua --help
FOTA-UA May 21 2013 18:05:10
ERROR [181] Parameter Error
Info [745] No status file
Total physical memory: 407695360 bytes
Total available physical memory: 8314880 bytes
Configuration information at runtime:
The number of pages of physical memory SC_PHYS_PAGES: 99535
The number of currently available pages of physical memory _SC_AVPHYS_PAGES: 203
0
Info [88] The number of processors configured _SC_NPROCESSORS_CONF: 2
The number of processors currently online (available) _SC_NPROCESSORS_ONLN: 2
Size of a page in bytes _SC_PAGESIZE: 4096
Logging of resource usage measures:
Maximum resident set size ru_maxrss: 172 KB
Page reclaims ru_minflt: 84
Page faults ru_majflt: 0
Block input operations: 0
Block output operations: 0
Info [468] No sdcard found in mounts
Info [757] Update Failed
WARN [48] Failed to remove /sbin/fota-ua, Read-only file system
WARN [52] Failed to remove /sbin/fota-mke2fs, Read-only file system
WARN [56] Failed to remove /sbin/rb_repart, No such file or directory
Click to expand...
Click to collapse
What we can do with these tools???
Or another tool:
./rb_repart
Repartitioning Tool
(C) Copyright 1999-2011 Red Bend Ltd.
4 Hacharash St. Hod-Hasharon, Israel
Version: 7.0.15.5514
Usage: ./rb_repart
-r [OPTIONAL, DEFAULT] - Run full operation
-t [OPTIONAL] - Run in test mode. Do not perform writes
-c config_file [OBLIGATIONAL] - Configuration file
Click to expand...
Click to collapse
munjeni said:
Any one have idea what is use of the fota kernel??? Got fota kernel and ramdisk kexeced and booted, found some tools in sbin folder, there is fota tools, for example after exacution of the fota-ua got this output:
What we can do with these tools???
Or another tool:
Click to expand...
Click to collapse
Well have you ever updated Sola with OTA,you will notice it boots to recovery and thats fota kernel "f-ota" - friendly over the air update system
XperianPro said:
Well have you ever updated Sola with OTA,you will notice it boots to recovery and thats fota kernel "f-ota" - friendly over the air update system
Click to expand...
Click to collapse
When I tried on Xperia Go to update trought fota it was not worked! I never seen anything related to the fota recovery! Is recovery exist on fota kernel??? Have any menu???
Found some logs:
/data/local/tmp/sbin/fotatools # find / | grep fota
find / | grep fota
/cache/recovery/fota
/cache/recovery/fota/executed
/cache/recovery/fota/report
/cache/recovery/fota/status
/system/bin/fota-snoop
find: /proc/2652: No such file or directory
find: /proc/3172: No such file or directory
find: /proc/3554: No such file or directory
find: /proc/3610: No such file or directory
find: /proc/3723: No such file or directory
find: /proc/3884: No such file or directory
/data/local/tmp/sbin/fota-tad
/data/local/tmp/sbin/fotatools
/data/local/tmp/sbin/fotatools/rb_repart
/data/local/tmp/sbin/fotatools/vold.fstab
/data/local/tmp/sbin/fotatools/toolbox
/data/local/tmp/sbin/fota-mke2fs
/data/local/tmp/sbin/fota-ua
/dev/.fota_ui_down
/dev/.fota_ui_shutdown
/data/local/tmp/sbin/fotatools # ls /cache/recovery
ls /cache/recovery
fota
last_log
/data/local/tmp/sbin/fotatools # ls /cache/recovery/last_log
ls /cache/recovery/last_log
/cache/recovery/last_log
/data/local/tmp/sbin/fotatools # cat /cache/recovery/last_log
cat /cache/recovery/last_log
MR: Master reset starting Sat Aug 10 20:26:26 2013
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /data ext4 /dev/block/mmcblk0p11 (null)
2 /cache ext4 /dev/block/mmcblk0p12 (null)
3 /modemfs ext4 /dev/block/mmcblk0p6 (null)
MR: Got content --wipe_data from /cache/recovery/command
MR: Formatting /cache
Creating filesystem with parameters:
Size: 262144000
Block size: 4096
Blocks per group: 32768
Inodes per group: 8000
Inode size: 256
Journal blocks: 1024
Label: /cache
Blocks: 64000
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16000 inodes and 2065/64000 blocks
MR: Formatting /data
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label: /data
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
MR: Unlocking gesture
MR: Resetting RFHAL parameters
MR: Cleaning dir /modemfs/RFHAL
MR: Leaving dir /modemfs/RFHAL
MR: Master reset done
/data/local/tmp/sbin/fotatools #
Click to expand...
Click to collapse
I hope it will work on Xperia™ U, I don't know if it could be possible as I don't know how many differences are between Sola's and U's ramdisk and stuff. :/
munjeni said:
Any one have idea what is use of the fota kernel??? Got fota kernel and ramdisk kexeced and booted, found some tools in sbin folder, there is fota tools, for example after exacution of the fota-ua got this output:
What we can do with these tools???
Or another tool:
Click to expand...
Click to collapse
well, on xperia s for example we use fota partition like a it was a recovery partition
otherwise as soon as you unlock your bl (= no more OTA) it becomes usless
mirhl said:
well, on xperia s for example we use fota partition like a it was a recovery partition
otherwise as soon as you unlock your bl (= no more OTA) it becomes usless
Click to expand...
Click to collapse
How you load recovery from ota partition? Seems you have something like LK bootloader???
munjeni said:
How you load recovery from ota partition? Seems you have something like LK bootloader???
Click to expand...
Click to collapse
a sort of
newer kernels when booting recovery, check if FOTA partition has the custom one installed
if yes, they loads that. otherwise standard recovery
more information here
mirhl said:
a sort of
newer kernels when booting recovery, check if FOTA partition has the custom one installed
if yes, they loads that. otherwise standard recovery
more information here
Click to expand...
Click to collapse
Thats good idea, but thats not ideal solution in comparation with phones which have separated recovery/boot partition and bootloader ui like HTC devices which have direct recovery load trought bootloader, these solution only working if primary boot partition is modified and added "few lines" for booting recovery from seccond partition (like ota partition). Will be perfect solution if we make LK bootloader for separating recovery/boot partition, allso with LK we will be able to create custom emmc layout, by now I can not see any small bootloader for NovaThor on google search, seems thats not public. Searching for a way for creating bootloader based on kernel. How we can modify curent kernel and make them bootloader??? We can modify recovery and make them bootloader kexec based, but I am not happy with kexec because we need to fix them first because loading an kernel trought current kexec patch is very slow! I will be happy if some one look into my git and find a solution for fixing them!
mirhl said:
well, on xperia s for example we use fota partition like a it was a recovery partition
otherwise as soon as you unlock your bl (= no more OTA) it becomes usless
Click to expand...
Click to collapse
What about if I relock my bootloader, do I will be able to use fota??? Seems ota working only if drm keys is not broken??
munjeni said:
What about if I relock my bootloader, do I will be able to use fota??? Seems ota working only if drm keys is not broken??
Click to expand...
Click to collapse
i have a locked bootloader but on xperia u and if you want anything i will happly help and mine has never been unlocked
---------- Post added at 04:59 PM ---------- Previous post was at 04:44 PM ----------
bobthecooldad said:
i have a locked bootloader but on xperia u and if you want anything i will happly help and mine has never been unlocked
Click to expand...
Click to collapse
just read this about fota
http://forum.xda-developers.com/showpost.php?p=12615775&postcount=1
and the orginal file is checked and if it isnt the correct one the phone wont boot
[Recovery] Working CWM 6.0.2.8 & CWM 6.0.3.7 for Samsung Galaxy Star ( S5280 &S5282 )
Hey guys,
We got another victory. CWM 6.0.2.8 & CWM 6.0.3.7 has been released for our device galaxy star.
STATUS - Tested
Use at your own risk i will not responsible for any mishappening
Contributor :
@Doc_cheilvenerdi.org
Procedure -
i) Boot your phone in odin mode.
ii) Then open odin.
iii) Flash it & Enjoy.
Link - CWM 6.0.2.8 - https://drive.google.com/folderview...sp=drive_web&tid=0B3qe_9NlA1D_Q2RTRzVBRmFkeDA
CWM 6.0.3.7 - https://drive.google.com/folderview?id=0B3qe_9NlA1D_c3dmNm1yQzdyX2M&usp=drive_web
Here is the screenshot-
did u test it?
Pleas Hold on and read carefully!
Please Hold on!
No Release yet!
Releasing software is a long and hard process...
...actually my Phone is on Jellybean 4.1.2 but I don't have yet a local copy of my european archive due to hotfile.com shutdown...
...so I'm still waiting for a mirror to back it up:
it's a strong option to recover a phone from a soft brick...
So what I'm doing here now?
I build Cyanogenmod from long time ago... starting with Gingerbread 7.2 up to KitKat 11.0 (for me it's really a different beast from older ones...)...
Now i prepared a device Skeleton for my mintss phone, I populated it looking online (many thanks to Ankur850, Batman38102, Requisite0, Sakindia123, TeamRegular and many others) and followed the Cyanogenmod guidelines to build a CWm recovery...
And I built a 6.0.2.8 (tuned to Cyanogenmod 10.0) with a working Kernel, a simple ramdisk, and so on...
...But I didn't test it yet...
...I'm still waiting due to my lack of a full firmware archive...
I also tried - for fun - to build the CWM 6.0.4.5 for Cyanogenmod 11.0 (beware: just a Blind Shot)
...using the 10.0 Kernel... working kernel but wrong configuration: it lacks Selinux capabilities (Working on it right now)...
...using a ramdisk tuned to JellyBean...
...filesystem nor permissive neither enforced...
..etc...
All things which can lead to a disaster while testing...
So, please, hold on until I'll test it on my own phone...
...if everything will be fine I'll be really happy to share it for the community...
See you soon on this thread then...
...news scheduled on incoming new year...
Doc_cheilvenerdi.org said:
Please Hold on!
No Release yet!
Releasing software is a long and hard process...
...actually my Phone is on Jellybean 4.1.2 but I don't have yet a local copy of my european archive due to hotfile.com shutdown...
...so I'm still waiting for a mirror to back it up:
it's a strong option to recover a phone from a soft brick...
So what I'm doing here now?
I build Cyanogenmod from long time ago... starting with Gingerbread 7.2 up to KitKat 11.0 (for me it's really a different beast from older ones...)...
Now i prepared a device Skeleton for my mintss phone, I populated it looking online (many thanks to Ankur850, Batman38102, Requisite0, Sakindia123, TeamRegular and many others) and followed the Cyanogenmod guidelines to build a CWm recovery...
And I built a 6.0.2.8 (tuned to Cyanogenmod 10.0) with a working Kernel, a simple ramdisk, and so on...
...But I didn't test it yet...
...I'm still waiting due to my lack of a full firmware archive...
I also tried - for fun - to build the CWM 6.0.4.5 for Cyanogenmod 11.0 (beware: just a Blind Shot)
...using the 10.0 Kernel... working kernel but wrong configuration: it lacks Selinux capabilities (Working on it right now)...
...using a ramdisk tuned to JellyBean...
...filesystem nor permissive neither enforced...
..etc...
All things which can lead to a disaster while testing...
So, please, hold on until I'll test it on my own phone...
...if everything will be fine I'll be really happy to share it for the community...
See you soon on this thread then...
...news scheduled on incoming new year...
Click to expand...
Click to collapse
excelent will wait for it :good:
I cant test it
Chirtagh said:
did u test it?
Click to expand...
Click to collapse
I cant test it bcoz i have S5282.:crying:
Download stock firmware
Doc_cheilvenerdi.org said:
Please Hold on!
No Release yet!
Releasing software is a long and hard process...
...actually my Phone is on Jellybean 4.1.2 but I don't have yet a local copy of my european archive due to hotfile.com shutdown...
...so I'm still waiting for a mirror to back it up:
it's a strong option to recover a phone from a soft brick...
So what I'm doing here now?
I build Cyanogenmod from long time ago... starting with Gingerbread 7.2 up to KitKat 11.0 (for me it's really a different beast from older ones...)...
Now i prepared a device Skeleton for my mintss phone, I populated it looking online (many thanks to Ankur850, Batman38102, Requisite0, Sakindia123, TeamRegular and many others) and followed the Cyanogenmod guidelines to build a CWm recovery...
And I built a 6.0.2.8 (tuned to Cyanogenmod 10.0) with a working Kernel, a simple ramdisk, and so on...
...But I didn't test it yet...
...I'm still waiting due to my lack of a full firmware archive...
I also tried - for fun - to build the CWM 6.0.4.5 for Cyanogenmod 11.0 (beware: just a Blind Shot)
...using the 10.0 Kernel... working kernel but wrong configuration: it lacks Selinux capabilities (Working on it right now)...
...using a ramdisk tuned to JellyBean...
...filesystem nor permissive neither enforced...
..etc...
All things which can lead to a disaster while testing...
So, please, hold on until I'll test it on my own phone...
...if everything will be fine I'll be really happy to share it for the community...
See you soon on this thread then...
...news scheduled on incoming new year...
Click to expand...
Click to collapse
Bro here is link to your country stock firmware & its not on hotfile.
http://terafile.co/5a3646396569
hey
rahulsinghal said:
I cant test it bcoz i have S5282.:crying:
Click to expand...
Click to collapse
umm i dont think this cwm is only compatible for s5280
you can try it
even if it doesnt work,it wont give you a bootloop,just a cwm error which can be recovered easily by flashing stock recovery
link
rahulsinghal said:
Hey guys,
We got another victory. CWM 6.0.4.5 has been released for our device galaxy star.
STATUS - Untested
Use at your own risk i will not responsible for any mishappening
Contributor :
@Doc_cheilvenerdi.org
Link - https://docs.google.com/file/d/0B3qe_9NlA1D_bm5WbDc2YWM3ck0/edit
Click to expand...
Click to collapse
the download link is denying access :/
hmmm
swhackeristahsan said:
the download link is denying access :/
Click to expand...
Click to collapse
Hey just request that file after some minute you will get access. n whats going on akshaymod
Doc_cheilvenerdi.org said:
Please Hold on!
No Release yet!
Releasing software is a long and hard process...
...actually my Phone is on Jellybean 4.1.2 but I don't have yet a local copy of my european archive due to hotfile.com shutdown...
...so I'm still waiting for a mirror to back it up:
it's a strong option to recover a phone from a soft brick...
So what I'm doing here now?
I build Cyanogenmod from long time ago... starting with Gingerbread 7.2 up to KitKat 11.0 (for me it's really a different beast from older ones...)...
Now i prepared a device Skeleton for my mintss phone, I populated it looking online (many thanks to Ankur850, Batman38102, Requisite0, Sakindia123, TeamRegular and many others) and followed the Cyanogenmod guidelines to build a CWm recovery...
And I built a 6.0.2.8 (tuned to Cyanogenmod 10.0) with a working Kernel, a simple ramdisk, and so on...
...But I didn't test it yet...
...I'm still waiting due to my lack of a full firmware archive...
I also tried - for fun - to build the CWM 6.0.4.5 for Cyanogenmod 11.0 (beware: just a Blind Shot)
...using the 10.0 Kernel... working kernel but wrong configuration: it lacks Selinux capabilities (Working on it right now)...
...using a ramdisk tuned to JellyBean...
...filesystem nor permissive neither enforced...
..etc...
All things which can lead to a disaster while testing...
So, please, hold on until I'll test it on my own phone...
...if everything will be fine I'll be really happy to share it for the community...
See you soon on this thread then...
...news scheduled on incoming new year...
Click to expand...
Click to collapse
Dude batman38102 is me I changes my username long time back. Also dudes I got my Galaxy star unbricked so Im back. Ill help in anyway I can
Its Going To Be LEGEND--wait for it--DARY!- Barney Stinson(How I Met Your Mother)
---------- Post added at 10:46 AM ---------- Previous post was at 10:42 AM ----------
Also can u please pm me the test recovery. Im willing to test in anyway i can.
Its Going To Be LEGEND--wait for it--DARY!- Barney Stinson(How I Met Your Mother)
Hmmm
Ironman38102 said:
Dude batman38102 is me I changes my username long time back. Also dudes I got my Galaxy star unbricked so Im back. Ill help in anyway I can
Its Going To Be LEGEND--wait for it--DARY!- Barney Stinson(How I Met Your Mother)
---------- Post added at 10:46 AM ---------- Previous post was at 10:42 AM ----------
Also can u please pm me the test recovery. Im willing to test in anyway i can.
Its Going To Be LEGEND--wait for it--DARY!- Barney Stinson(How I Met Your Mother)
Click to expand...
Click to collapse
Hey thats gr8 hope we will get cm now.:victory:
CWM 6.0.2.8 Up and Running!
News about CWM 6.0.2.8 from CyanogenMod 10.0 (Jellybean 4.1.2):
I don't have a Github account (I'm not a developer) so I'll post here exactly what I did to build and set "up and running" this ClockWorkMod Recovery!
First of all, in my Google Drive you'll find everything we are Talking about... the experimental device tree, the recovery Odin archive, tools, binaries, ...
On first build everything was fine but the LCD screen didn't light up...
...Recovery was running, anyway, but I could not see anything...
...I could, perhaps, control the phone from PC with "adb shell"!
Code:
[email protected]:~$ [b]adb shell[/b]
~ # [b]ls[/b]
cache init.rc sdcard1
data preload sys
default.prop proc system
dev res tmp
efs root ueventd.goldfish.rc
etc sbin ueventd.rc
fstab.sp8810 sd-ext ueventd.sp8810.rc
init sdcard
~ #
Recovery log recorded the problem:
Code:
...
failed to put fb0 info
...
It's a framebuffer problem and the solution is pretty known; I pasted it from TeamRegular repository and put inside BoardConfig.mk with related sources:
Code:
...
BOARD_CUSTOM_GRAPHICS := ../../../device/samsung/sp8810/recovery/graphics.c
...
Well done! Recovery 6.0.2.8 up and running
Now testing:
- I can mount/unmount and list all filesystems
- I can backup the current firmware
- I can format and restore the external second partition (I use it a lot):
Code:
Creating filesystem with parameters:
Size: 1034944512
Block size: 4096
Blocks per group: 32768
Inodes per group: 7904
Inode size: 256
Journal blocks: 3948
Label:
Blocks: 252672
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/63232 inodes and 8244/252672 blocks
...
Found new backup image: /sdcard/clockworkmod/backup/2013-12-26.17.17.06//sd-ext.ext4.tar
Restoring sd-ext...
...
Code:
~ # [b]ls -l /sd-ext/[/b]
drwxrwx--x 2 system system 4096 Dec 22 12:54 dalvik-cache
drwxrwx--x 2 system system 4096 Dec 22 12:54 data
drwx------ 2 root root 4096 Dec 17 10:14 lost+found
~ #
- I can restore the boot image (and recovery of course):
Code:
...
Checking MD5 sums...
boot.img: OK
...
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
Restore complete!
- I can Install boot images inside zip files from sdcard:
Code:
-- Installing: /sdcard/update_boot.zip
Finding update package...
I:Update location: /sdcard/update_boot.zip
Opening update package...
Installing update...
########################
# Doc Modded #
# new boot image #
########################
Installing Boot...
script result was [ ]
Installation Completed!!!!
- I can install zip files from sideload:
Code:
Sideload started ...
Now send the package you want to apply
to the device with "adb sideload <filename>"...
sideload_service invoked
adbd exiting after successful sideload
E:listen on USB
E:userid is 2000
E:Event loop starting
Restarting adbd...
Finding update package...
I:Update location: /tmp/update.zip
Opening update package...
Installing update...
if you read this, you
own a relaxed recovery!
Cheers :)
~ #
- I can "wipe cache":
Code:
-- Wiping cache...
Formatting /cache...
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
Cache wipe complete.
- I can "wipe data/factory reset" :
Code:
-- Wiping data...
Formatting /data...
Creating filesystem with parameters:
Size: 2172633088
Block size: 4096
Blocks per group: 32768
Inodes per group: 7808
Inode size: 256
Journal blocks: 8287
Label:
Blocks: 530428
Block groups: 17
Reserved block group size: 135
Created filesystem with 11/132736 inodes and 17442/530428 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead
...
Data wipe complete.
/tmp #
Notice: Actually this "CWM build" deals with /data encryption so ther is no need to apply any patch after factory reset
I took an extra-check with the following 'shell command' before and after the wipe action:
Code:
/ # [b]tune2fs -l /dev/block/mmcblk0p25[/b]
...
looking for no relevant differences!
..after boot... everything fine!
- Last but not least:
- I fully restored the previously backupped firmware:
Code:
...
...
Restore complete!
Easy Play
What's Wrong in this recovery?
I Dont Know...
Wish List?
Sure: I cannot handle /efs partition via 'menu options'...
...and everybody knows how dangerous could be wander around it
Doc_cheilvenerdi.org said:
News about CWM 6.0.2.8 from CyanogenMod 10.0 (Jellybean 4.1.2):
I don't have a Github account (I'm not a developer) so I'll post here exactly what I did to build and set "up and running" this ClockWorkMod Recovery!
First of all, in my Google Drive you'll find everything we are Talking about... the experimental device tree, the recovery Odin archive, tools, binaries, ...
On first build everything was fine but the LCD screen didn't light up...
...Recovery was running, anyway, but I could not see anything...
...I could, perhaps, control the phone from PC with "adb shell"!
Code:
[email protected]:~$ [b]adb shell[/b]
~ # [b]ls[/b]
cache init.rc sdcard1
data preload sys
default.prop proc system
dev res tmp
efs root ueventd.goldfish.rc
etc sbin ueventd.rc
fstab.sp8810 sd-ext ueventd.sp8810.rc
init sdcard
~ #
Recovery log recorded the problem:
Code:
...
failed to put fb0 info
...
It's a framebuffer problem and the solution is pretty known; I pasted it from TeamRegular repository and put inside BoardConfig.mk with related sources:
Code:
...
BOARD_CUSTOM_GRAPHICS := ../../../device/samsung/sp8810/recovery/graphics.c
...
Well done! Recovery 6.0.2.8 up and running
Now testing:
- I can mount/unmount and list all filesystems
- I can backup the current firmware
- I can format and restore the external second partition (I use it a lot):
Code:
Creating filesystem with parameters:
Size: 1034944512
Block size: 4096
Blocks per group: 32768
Inodes per group: 7904
Inode size: 256
Journal blocks: 3948
Label:
Blocks: 252672
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/63232 inodes and 8244/252672 blocks
...
Found new backup image: /sdcard/clockworkmod/backup/2013-12-26.17.17.06//sd-ext.ext4.tar
Restoring sd-ext...
...
Code:
~ # [b]ls -l /sd-ext/[/b]
drwxrwx--x 2 system system 4096 Dec 22 12:54 dalvik-cache
drwxrwx--x 2 system system 4096 Dec 22 12:54 data
drwx------ 2 root root 4096 Dec 17 10:14 lost+found
~ #
- I can restore the boot image (and recovery of course):
Code:
...
Checking MD5 sums...
boot.img: OK
...
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
Restore complete!
- I can Install boot images inside zip files from sdcard:
Code:
-- Installing: /sdcard/update_boot.zip
Finding update package...
I:Update location: /sdcard/update_boot.zip
Opening update package...
Installing update...
########################
# Doc Modded #
# new boot image #
########################
Installing Boot...
script result was [ ]
Installation Completed!!!!
- I can install zip files from sideload:
Code:
Sideload started ...
Now send the package you want to apply
to the device with "adb sideload <filename>"...
sideload_service invoked
adbd exiting after successful sideload
E:listen on USB
E:userid is 2000
E:Event loop starting
Restarting adbd...
Finding update package...
I:Update location: /tmp/update.zip
Opening update package...
Installing update...
if you read this, you
own a relaxed recovery!
Cheers :)
~ #
- I can "wipe cache":
Code:
-- Wiping cache...
Formatting /cache...
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
Cache wipe complete.
- I can "wipe data/factory reset" :
Code:
-- Wiping data...
Formatting /data...
Creating filesystem with parameters:
Size: 2172633088
Block size: 4096
Blocks per group: 32768
Inodes per group: 7808
Inode size: 256
Journal blocks: 8287
Label:
Blocks: 530428
Block groups: 17
Reserved block group size: 135
Created filesystem with 11/132736 inodes and 17442/530428 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead
...
Data wipe complete.
/tmp #
Notice: Actually this "CWM build" deals with /data encryption so ther is no need to apply any patch after factory reset
I took an extra-check with the following 'shell command' before and after the wipe action:
Code:
/ # [b]tune2fs -l /dev/block/mmcblk0p25[/b]
...
looking for no relevant differences!
..after boot... everything fine!
- Last but not least:
- I fully restored the previously backupped firmware:
Code:
...
...
Restore complete!
Easy Play
What's Wrong in this recovery?
I Dont Know...
Wish List?
Sure: I cannot handle /efs partition via 'menu options'...
...and everybody knows how dangerous could be wander around it
Click to expand...
Click to collapse
Will dis wrk on s5282...??
Pls say Yes...
Yup u can use it
Sent from my GT-S5282 using Tapatalk
thanks
:good:
Doc_cheilvenerdi.org said:
News about CWM 6.0.2.8 from CyanogenMod 10.0 (Jellybean 4.1.2):
I don't have a Github account (I'm not a developer) so I'll post here exactly what I did to build and set "up and running" this ClockWorkMod Recovery!
First of all, in my Google Drive you'll find everything we are Talking about... the experimental device tree, the recovery Odin archive, tools, binaries, ...
On first build everything was fine but the LCD screen didn't light up...
...Recovery was running, anyway, but I could not see anything...
...I could, perhaps, control the phone from PC with "adb shell"!
Code:
[email protected]:~$ [b]adb shell[/b]
~ # [b]ls[/b]
cache init.rc sdcard1
data preload sys
default.prop proc system
dev res tmp
efs root ueventd.goldfish.rc
etc sbin ueventd.rc
fstab.sp8810 sd-ext ueventd.sp8810.rc
init sdcard
~ #
Recovery log recorded the problem:
Code:
...
failed to put fb0 info
...
It's a framebuffer problem and the solution is pretty known; I pasted it from TeamRegular repository and put inside BoardConfig.mk with related sources:
Code:
...
BOARD_CUSTOM_GRAPHICS := ../../../device/samsung/sp8810/recovery/graphics.c
...
Well done! Recovery 6.0.2.8 up and running
Now testing:
- I can mount/unmount and list all filesystems
- I can backup the current firmware
- I can format and restore the external second partition (I use it a lot):
Code:
Creating filesystem with parameters:
Size: 1034944512
Block size: 4096
Blocks per group: 32768
Inodes per group: 7904
Inode size: 256
Journal blocks: 3948
Label:
Blocks: 252672
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/63232 inodes and 8244/252672 blocks
...
Found new backup image: /sdcard/clockworkmod/backup/2013-12-26.17.17.06//sd-ext.ext4.tar
Restoring sd-ext...
...
Code:
~ # [b]ls -l /sd-ext/[/b]
drwxrwx--x 2 system system 4096 Dec 22 12:54 dalvik-cache
drwxrwx--x 2 system system 4096 Dec 22 12:54 data
drwx------ 2 root root 4096 Dec 17 10:14 lost+found
~ #
- I can restore the boot image (and recovery of course):
Code:
...
Checking MD5 sums...
boot.img: OK
...
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
Restore complete!
- I can Install boot images inside zip files from sdcard:
Code:
-- Installing: /sdcard/update_boot.zip
Finding update package...
I:Update location: /sdcard/update_boot.zip
Opening update package...
Installing update...
########################
# Doc Modded #
# new boot image #
########################
Installing Boot...
script result was [ ]
Installation Completed!!!!
- I can install zip files from sideload:
Code:
Sideload started ...
Now send the package you want to apply
to the device with "adb sideload <filename>"...
sideload_service invoked
adbd exiting after successful sideload
E:listen on USB
E:userid is 2000
E:Event loop starting
Restarting adbd...
Finding update package...
I:Update location: /tmp/update.zip
Opening update package...
Installing update...
if you read this, you
own a relaxed recovery!
Cheers :)
~ #
- I can "wipe cache":
Code:
-- Wiping cache...
Formatting /cache...
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
Cache wipe complete.
- I can "wipe data/factory reset" :
Code:
-- Wiping data...
Formatting /data...
Creating filesystem with parameters:
Size: 2172633088
Block size: 4096
Blocks per group: 32768
Inodes per group: 7808
Inode size: 256
Journal blocks: 8287
Label:
Blocks: 530428
Block groups: 17
Reserved block group size: 135
Created filesystem with 11/132736 inodes and 17442/530428 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead
...
Data wipe complete.
/tmp #
Notice: Actually this "CWM build" deals with /data encryption so ther is no need to apply any patch after factory reset
I took an extra-check with the following 'shell command' before and after the wipe action:
Code:
/ # [b]tune2fs -l /dev/block/mmcblk0p25[/b]
...
looking for no relevant differences!
..after boot... everything fine!
- Last but not least:
- I fully restored the previously backupped firmware:
Code:
...
...
Restore complete!
Easy Play
What's Wrong in this recovery?
I Dont Know...
Wish List?
Sure: I cannot handle /efs partition via 'menu options'...
...and everybody knows how dangerous could be wander around it
Click to expand...
Click to collapse
---------- Post added at 12:12 PM ---------- Previous post was at 12:09 PM ----------
after cwm recovery 6 when cm 10.1 will release
Here is the screenshot. Check it out. Its tested by me on my s5282.
Here is screenshots. Tested by me on my s5282. I have also tested geatures like wipe data and back up rom ans flash zip from sd card and its working perfecly. Sure you should go for it
Sent from my GT-S5282 using Tapatalk
rahulsinghal said:
Here is screenshots. Tested by me on my s5282. I have also tested geatures like wipe data and back up rom ans flash zip from sd card and its working perfecly. Sure you should go for it
Sent from my GT-S5282 using Tapatalk
Click to expand...
Click to collapse
GR8...Congratulations....now we can expect a cm rom for our star.....
I know you guys must be counting on me for compiling. But I cant untill u guys setup a working device tree and kernel. Also my pc cant compile cm as I have a pc with very low spec. Sorry
Although I will still try but I cant promise anything since I have never worked on a device like this. Spreadtrum cpus are pretty much hard to hack.
also dudes I know how much your excited but we need to keep all development threads on topic!
Its Going To Be LEGEND--wait for it--DARY!- Barney Stinson(How I Met Your Mother)
Doc_cheilvenerdi.org said:
News about CWM 6.0.2.8 from CyanogenMod 10.0 (Jellybean 4.1.2):
I don't have a Github account (I'm not a developer) so I'll post here exactly what I did to build and set "up and running" this ClockWorkMod Recovery!
First of all, in my Google Drive you'll find everything we are Talking about... the experimental device tree, the recovery Odin archive, tools, binaries, ...
On first build everything was fine but the LCD screen didn't light up...
...Recovery was running, anyway, but I could not see anything...
...I could, perhaps, control the phone from PC with "adb shell"!
Code:
[email protected]:~$ [b]adb shell[/b]
~ # [b]ls[/b]
cache init.rc sdcard1
data preload sys
default.prop proc system
dev res tmp
efs root ueventd.goldfish.rc
etc sbin ueventd.rc
fstab.sp8810 sd-ext ueventd.sp8810.rc
init sdcard
~ #
Recovery log recorded the problem:
Code:
...
failed to put fb0 info
...
It's a framebuffer problem and the solution is pretty known; I pasted it from TeamRegular repository and put inside BoardConfig.mk with related sources:
Code:
...
BOARD_CUSTOM_GRAPHICS := ../../../device/samsung/sp8810/recovery/graphics.c
...
Well done! Recovery 6.0.2.8 up and running
Now testing:
- I can mount/unmount and list all filesystems
- I can backup the current firmware
- I can format and restore the external second partition (I use it a lot):
Code:
Creating filesystem with parameters:
Size: 1034944512
Block size: 4096
Blocks per group: 32768
Inodes per group: 7904
Inode size: 256
Journal blocks: 3948
Label:
Blocks: 252672
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/63232 inodes and 8244/252672 blocks
...
Found new backup image: /sdcard/clockworkmod/backup/2013-12-26.17.17.06//sd-ext.ext4.tar
Restoring sd-ext...
...
Code:
~ # [b]ls -l /sd-ext/[/b]
drwxrwx--x 2 system system 4096 Dec 22 12:54 dalvik-cache
drwxrwx--x 2 system system 4096 Dec 22 12:54 data
drwx------ 2 root root 4096 Dec 17 10:14 lost+found
~ #
- I can restore the boot image (and recovery of course):
Code:
...
Checking MD5 sums...
boot.img: OK
...
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
Restore complete!
- I can Install boot images inside zip files from sdcard:
Code:
-- Installing: /sdcard/update_boot.zip
Finding update package...
I:Update location: /sdcard/update_boot.zip
Opening update package...
Installing update...
########################
# Doc Modded #
# new boot image #
########################
Installing Boot...
script result was [ ]
Installation Completed!!!!
- I can install zip files from sideload:
Code:
Sideload started ...
Now send the package you want to apply
to the device with "adb sideload <filename>"...
sideload_service invoked
adbd exiting after successful sideload
E:listen on USB
E:userid is 2000
E:Event loop starting
Restarting adbd...
Finding update package...
I:Update location: /tmp/update.zip
Opening update package...
Installing update...
if you read this, you
own a relaxed recovery!
Cheers :)
~ #
- I can "wipe cache":
Code:
-- Wiping cache...
Formatting /cache...
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
Cache wipe complete.
- I can "wipe data/factory reset" :
Code:
-- Wiping data...
Formatting /data...
Creating filesystem with parameters:
Size: 2172633088
Block size: 4096
Blocks per group: 32768
Inodes per group: 7808
Inode size: 256
Journal blocks: 8287
Label:
Blocks: 530428
Block groups: 17
Reserved block group size: 135
Created filesystem with 11/132736 inodes and 17442/530428 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead
...
Data wipe complete.
/tmp #
Notice: Actually this "CWM build" deals with /data encryption so ther is no need to apply any patch after factory reset
I took an extra-check with the following 'shell command' before and after the wipe action:
Code:
/ # [b]tune2fs -l /dev/block/mmcblk0p25[/b]
...
looking for no relevant differences!
..after boot... everything fine!
- Last but not least:
- I fully restored the previously backupped firmware:
Code:
...
...
Restore complete!
Easy Play
What's Wrong in this recovery?
I Dont Know...
Wish List?
Sure: I cannot handle /efs partition via 'menu options'...
...and everybody knows how dangerous could be wander around it
Click to expand...
Click to collapse
Lol i have uploaded all those codes to github. http://github.com/batman38102/android_device_samsung_mint
[Q&A] [GUIDE] How to build CWM-based Recovery from source in Ubuntu 12.04 with CM-11
Q&A for [GUIDE] How to build CWM-based Recovery from source in Ubuntu 12.04 with CM-11.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE] How to build CWM-based Recovery from source in Ubuntu 12.04 with CM-11.0. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
My phone has 16mb recovery part but the recovery.img I made is 25 mb so I can't flash it In BoardConfig.mk, I can wrote at least 24.936.448 at the line of BOARD_RECOVERYIMAGE_SIZE to compile the recovery image. How can I solve this problem? Can I reduce the size of the .img file to 16 mb?
denizyildizi345 said:
My phone has 16mb recovery part but the recovery.img I made is 25 mb so I can't flash it In BoardConfig.mk, I can wrote at least 24.936.448 at the line of BOARD_RECOVERYIMAGE_SIZE to compile the recovery image. How can I solve this problem? Can I reduce the size of the .img file to 16 mb?
Click to expand...
Click to collapse
I don't understand how you ended up with such a big recovery... The biggest ramdisk I saw (in TWRP) is not more than 4-5 Mb. Do you have a kernel over 20Mb? It can't be, otherwise the stock recovery will be oversized too. Somewhere you made a mistake probably.
And to answer your question, no you can't reduce the size of recovery that big; if you have a kernel compressed in xz, you may try to compress the ramdisk in xz too, and the size will be smaller, but not enough... you need to downsize it with 9Mb, which is not possible.
So check again, to see if there isn't a mistake somewhere.
carliv said:
I don't understand how you ended up with such a big recovery... The biggest ramdisk I saw (in TWRP) is not more than 4-5 Mb. Do you have a kernel over 20Mb? It can't be, otherwise the stock recovery will be oversized too. Somewhere you made a mistake probably.
And to answer your question, no you can't reduce the size of recovery that big; if you have a kernel compressed in xz, you may try to compress the ramdisk in xz too, and the size will be smaller, but not enough... you need to downsize it with 9Mb, which is not possible.
So check again, to see if there isn't a mistake somewhere.
Click to expand...
Click to collapse
I took a screenshot of my CM11-0/out/target/product/msm8226/root folder which is 25 mb. There is a boot.img file. I think the problem is that file. I unpacked a few recovery.img files but none of them included that file. If problem is this, how can I remove that file from my ramdisk?
I removed that file and flashed new recovery.img but now my phone isn't booting in recovery mode.
denizyildizi345 said:
I took a screenshot of my CM11-0/out/target/product/msm8226/root folder which is 25 mb. There is a boot.img file. I think the problem is that file. I unpacked a few recovery.img files but none of them included that file. If problem is this, how can I remove that file from my ramdisk?
I removed that file and flashed new recovery.img but now my phone isn't booting in recovery mode.
Click to expand...
Click to collapse
No, for checking recovery root you need to look here: CM11-0/out/target/product/msm8226/recovery/root . But anyway that folder looks strange (I see a perl script there)....
Check my screenshot below.
And type a
Code:
make clobber
before stating a new build, or
Code:
make clean
between repetitive builds.
im getting this error each time i try to compile:
make: *** No rule to make target `/etc/init.rc'
please any suggestions
george676 said:
im getting this error each time i try to compile:
make: *** No rule to make target `/etc/init.rc'
please any suggestions
Click to expand...
Click to collapse
You need to be more specific: what recovery you try to build, in what environment (if it's not cm-11), and post a link to your device folder tree. That error means that the compiler can't find an init.rc file to add in ramdisk.
Compiler stops after a few segments
This is shown in my terminal:
Code:
cp: cannot stat ‘/home/paul/cm-10.2/out/target/product/Ultra/root/init.recovery.*.rc’: No such file or directory
make: [/home/paul/cm-10.2/out/target/product/Ultra/recovery/root.ts] Error 1 (ignored)
mkdir -p /home/paul/cm-10.2/out/target/product/Ultra/recovery/root/system/bin
cp -rf device/CherryMobile/Ultra/recovery/root /home/paul/cm-10.2/out/target/product/Ultra/recovery/
cp: omitting directory ‘device/CherryMobile/Ultra’
make: *** [/home/paul/cm-10.2/out/target/product/Ultra/recovery/root.ts] Error 1
[email protected] ~/cm-10.2 $ make clobber
And you wrote about the problem:
During the build process you may encounter some errors or warnings.
*********************
Code:
Code:
cp: cannot stat `/home/carliv/CM11-0/out/target/product/P780/root/init.recovery.*.rc': No such file or directory
make: [/home/carliv/CM11-0/out/target/product/P780/recovery/root.ts] Error 1 (ignored)
This will not stop the build, and it appears if you don't use a init.recovery.{hardware}.rc file. Can be ignored, as the build process does.
Though in my terminal it just stopped at that part so I had to rename mine which was originally init.recovery.qcom.rc to init.recovery.*.rc
--edit--
And yet it still would not continue ... Any ideas on how to fix this?
--edit # 2--
Here's the pastebin link just in case ->biQ7kjV8 add that to pastebin...(I can't post links)
--edit # 3--
I fixed it... Turns out that it was just a BoardConfig.mk parameter that I forgot to complete
Calculate proper BoardConfig.mk partition sizes
I have this log:
Code:
----- Making recovery image ------
/home/paul/cm-10.2/out/target/product/Ultra/recovery.img maxsize=8380416 blocksize=135168 total=8409088 reserve=270336
error: /home/paul/cm-10.2/out/target/product/Ultra/recovery.img too large (8409088 > [8650752 - 270336])
make: *** [/home/paul/cm-10.2/out/target/product/Ultra/recovery.img] Error 1
make: *** Deleting file `/home/paul/cm-10.2/out/target/product/Ultra/recovery.img'
Meaning I have wrong sizes for the partitions so I need help on it...
When I ran the following:
cat /proc/mtd
cat /proc/emmc
they both return: No such file or directory...
Now If I run the command: cat /proc/partitions
it comes up with this:
As far as I know.... mmcblk1p1 is my external sd card which is about 32 GB...
My system image is about 1 GB and more(confirmed) when I used the dd command(to dump it) and is located at mmcblk0p16
Userdata reaches more than 4 GB as reported by the dd command(file size too large) and is located at mmbblk0p25
here(recovery.fstab):
/boot mtd /dev/block/mmcblk0p10
/cache yaffs2 /dev/block/mmcblk0p18
/data yaffs2 /dev/block/mmcblk0p25
/misc mtd /dev/block/mmcblk0p20
/recovery mtd /dev/block/mmcblk0p19
/system yaffs2 /dev/block/mmcblk0p16
-- edit --
I solved this already
Help required for compiling CWM for android 4.4.2 version only?
I am on Ubuntu 14.0.4 and I am trying to build a CWM recovery for Celkon Q 5009android 4.4.2, Broadcom processor). I have set up build environment and currently working on syncing repo. I have heard that it takes too much time and disk space to complete this process. I am interested to know in the following particular scenario : want to build only CWM recovery from source for an android running on version 4.4.2. So do I have to download all repositories or is there any shortcut that would enable me to not download all, but a certain part that is required for android 4.4.2? If yes, how to go about it? please help.
Please help. I do not undertstand why 'repo sync' always fails at a particular stage, though I have 30+ GB of disk space available in my working folder named 'cm12'. Following is the last screen message :
Fetching project platform/external/ant-glob
Fetching projects: 8% (40/495) Receiving objects: 86% (2389/2771), 26.68 MiBerror: RPC failed; result=56, HTTP code = 200iB | 124.00 KiB/s
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
remote: Sending approximately 1.94 GiB ...
remote: Counting objects: 85, done
remote: Finding sources: 100% (85/85)
error: RPC failed; result=56, HTTP code = 200iB | 88.00 KiB/s
fatal: The remote end hung up unexpectedly
Now should I run 'repo sync' again or should I use 'repo sync -j1' ?
fatal: early EOF
fatal: index-pack failed
error: Cannot fetch device/lge/mako-kernel
error: Exited sync due to fetch errors
Hey,
In which size are the values in BoardConfig.mk at BOARD_BOOTIMAGE_PARTITION_ZISE? bit?
And how I can convert blocks to this size because my lge only print out the partition sizes in blocks.
LG Noel
Black Manta said:
Hey,
In which size are the values in BoardConfig.mk at BOARD_BOOTIMAGE_PARTITION_ZISE? bit?
And how I can convert blocks to this size because my lge only print out the partition sizes in blocks.
LG Noel
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=60297989&postcount=51
Somewhere around that post you will find your answer.
Hi. Your guide is the most useful I found on the net. Much more than the official cyanogenmod wiki's porting one. Thanks a lot.
I'm trying to use it to build a cm 12.1 (lollipop) cwm on a mediatek device.
1) My stock rom (also Android 5.1) already ships a fstab.mt6795 file into the ramdisk. I moved it inside /recovery/root, and copied its content in /recovery/recovery.fstab
This is its content, should I make any change inside it?
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro wait
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,resize,encryptable=footer
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#please add cip or persist on project fstab
#/dev/block/platform/mtk-msdc.0/by-name/persist /persist ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#/dev/block/platform/mtk-msdc.0/by-name/custom /custom ext4 ro wait
/devices/mtk-msdc.0/11230000.MSDC0 auto vfat defaults voldmanaged=sdcard0:[email protected],noemulatedsd
/devices/mtk-msdc.0/11240000.MSDC1 auto vfat defaults voldmanaged=sdcard1:auto
/devices/bus.2/11270000.USB3_XHCI auto vfat defaults voldmanaged=usbotg:auto
/dev/block/platform/mtk-msdc.0/by-name/frp /persistent emmc defaults
2) How can I find out which of the .rc files available in stock ramdisk include in my recovery, besides the renamed init.rc copied from /bootable/recovery/etc ?
3) My stock rom obviously already ships a init.mt6795.rc. Should I merge any of its lines to the one I copied from /bootable/recovery/etc in my /recovery folder?
Thanks in advance for your time and your efforts.
4javier said:
Hi. Your guide is the most useful I found on the net. Much more than the official cyanogenmod wiki's porting one. Thanks a lot.
I'm trying to use it to build a cm 12.1 (lollipop) cwm on a mediatek device.
1) My stock rom (also Android 5.1) already ships a fstab.mt6795 file into the ramdisk. I moved it inside /recovery/root, and copied its content in /recovery/recovery.fstab
This is its content, should I make any change inside it?
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro wait
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,resize,encryptable=footer
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#please add cip or persist on project fstab
#/dev/block/platform/mtk-msdc.0/by-name/persist /persist ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,autoformat
#/dev/block/platform/mtk-msdc.0/by-name/custom /custom ext4 ro wait
/devices/mtk-msdc.0/11230000.MSDC0 auto vfat defaults voldmanaged=sdcard0:[email protected],noemulatedsd
/devices/mtk-msdc.0/11240000.MSDC1 auto vfat defaults voldmanaged=sdcard1:auto
/devices/bus.2/11270000.USB3_XHCI auto vfat defaults voldmanaged=usbotg:auto
/dev/block/platform/mtk-msdc.0/by-name/frp /persistent emmc defaults
2) How can I find out which of the .rc files available in stock ramdisk include in my recovery, besides the renamed init.rc copied from /bootable/recovery/etc ?
3) My stock rom obviously already ships a init.mt6795.rc. Should I merge any of its lines to the one I copied from /bootable/recovery/etc in my /recovery folder?
Thanks in advance for your time and your efforts.
Click to expand...
Click to collapse
First let me ask you where did you find a cwm for lollipop to build it? I'm interested to see that.
Second in recovery fstab you may want to add emmc partitions like boot, recovery... Check my github and look at elephone p6000 device folder (it's close enough to understand). If internal sdcard is on data/media you don't have to add it at all in fstab (at least that was the rule for kitkat... again I need to see the source for that lollipop cwm to tell you exactly). In elephone device recovery fstab you can see that usb and external sdcard are defined as auto for type not vfat because it is better to let minivold manage that.
Normaly for cm12.1 ther is no need to copy any rc file in root, only the fstab. {hardware}, which you said you did.
Again I can tell more if I will see the source code for the recovery, and last thing my guide is quite old now but I'm glad you found it useful.
Thanks for your quick reply.
I think I've not been so clear explaining what I'm doing: when I talk about "Lollipo CWM" I just mean that I'm working on 12.1 branch of cyanogenmod source tree, that as you know is based on the same sources of Lollipop, instead of the one the guide was originally aimed to.
1) I feel really dumb at this moment. I don't know exactly how many time I read that fstab file, and I never noticed that it lacks entries for partitions not managed by stock recovery. Sorry if I wasted your time with a stupid question.
2)For sdcards, then it's better to leave untouched the voldmanaged options, but change the filesystem type to auto?
3) I don't need to copy any other .rc file (init.mt6795.usb.rc, init.xlog.rc, etc...), nor to merge anything from init.mt6795.rc of the stock rom. Right?
Thanks again.
4javier said:
Thanks for your quick reply.
I think I've not been so clear explaining what I'm doing: when I talk about "Lollipo CWM" I just mean that I'm working on 12.1 branch of cyanogenmod source tree, that as you know is based on the same sources of Lollipop, instead of the one the guide was originally aimed to.
1) I feel really dumb at this moment. I don't know exactly how many time I read that fstab file, and I never noticed that it lacks entries for partitions not managed by stock recovery. Sorry if I wasted your time with a stupid question.
2)For sdcards, then it's better to leave untouched the voldmanaged options, but change the filesystem type to auto?
3) I don't need to copy any other .rc file (init.mt6795.usb.rc, init.xlog.rc, etc...), nor to merge anything from init.mt6795.rc of the stock rom. Right?
Thanks again.
Click to expand...
Click to collapse
I did understand it's cm12.1, but that was my question since there is no cwm for cm12.1 only cyanogenmod recovery which is different. At the moment I only recommend twrp for cm12.1+ and for that you have to use a different fstab, easy to find on github or here on xda in twrp threads.
Then, if I'm not too much confused:
- since CM12, Clockworkmod isn't anymore included in its source tree
- if I don't set any RECOVERY_VARIANT it defaults to CyanogenMod Recovery, not CWM anymore
- the recovery.img I built is, at its best, a Cyanogenmod recovery
- the recovery.fstab I used (the one i posted before, but now with /boot, /recovery and /nvram entries added) is in version 2 format, that twrp doesn't understand. So I have to find out how to convert in the old fstab format.
Am I right?
Another question: I used the last version of your CarlivKitchen. That doesn't offer anymore the choice to re/pack for standard android or for mtk images, because it automatically detect the format. But when it repacks, it adds the mtk header if the original image had it? Or am I forced to use a custom boot image maker?
4javier said:
Then, if I'm not too much confused:
- since CM12, Clockworkmod isn't anymore included in its source tree
- if I don't set any RECOVERY_VARIANT it defaults to CyanogenMod Recovery, not CWM anymore
- the recovery.img I built is, at its best, a Cyanogenmod recovery
- the recovery.fstab I used (the one i posted before, but now with /boot, /recovery and /nvram entries added) is in version 2 format, that twrp doesn't understand. So I have to find out how to convert in the old fstab format.
Am I right?
Another question: I used the last version of your CarlivKitchen. That doesn't offer anymore the choice to re/pack for standard android or for mtk images, because it automatically detect the format. But when it repacks, it adds the mtk header if the original image had it? Or am I forced to use a custom boot image maker?
Click to expand...
Click to collapse
Yes for all and for twrp fstab I think you can study device folders from twrp github (few are mediatek).
My kitchen now detects if image has mtk header and will repack it the same way (it stores a variable in unpacked folder which will tell that it must add a mtk header).
I decided to follow this guide to integrate the changes needed to build twrp instead of cwm: http://forum.xda-developers.com/showthread.php?t=1943625
It doesn't cover all the preparation steps like yours do. Do you think there are changes to be made to make your guide suitable for cm12 and twrp, or I can follow it until the " Build a CWM-based Recovery " paragraph?
Hi all. I have been trying to install the [ROM][5.1.1_r26][OFFICIAL] Resurrection Remix® Lollipop v5.5.9 - Togari [11/20] Final.
I have to post the problem here as I don't post enough. ( trust me. I research the **** out of everything so I don't have to annoy developers ).
Anyway this is the log I get......
Installing '/external_sd/My Stuff/Resurrection-Remix-LP-v5.5.9-20151120-togari.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: This package is for device: C6802,C6806,C6833,C6843,togari; this device is tianchi.
This package is for device: C6802,C6806,C6833,C6843,togari; this device is tianchi.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/My Stuff/Resurrection-Remix-LP-v5.5.9-20151120-togari.zip'
Error flashing zip '/external_sd/My Stuff/Resurrection-Remix-LP-v5.5.9-20151120-togari.zip'
Updating partition details...
Iata backup size is 0MB, free: 5683MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
...done
I know it's and was a standard C6833 as I use to be able to install roms before.
Anybody know of a way to change it back or have any ideas. Greatly appreciated everyone.
Gr1ffo said:
Hi all. I have been trying to install the [ROM][5.1.1_r26][OFFICIAL] Resurrection Remix® Lollipop v5.5.9 - Togari [11/20] Final.
I have to post the problem here as I don't post enough. ( trust me. I research the **** out of everything so I don't have to annoy developers ).
Anyway this is the log I get......
Installing '/external_sd/My Stuff/Resurrection-Remix-LP-v5.5.9-20151120-togari.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: This package is for device: C6802,C6806,C6833,C6843,togari; this device is tianchi.
This package is for device: C6802,C6806,C6833,C6843,togari; this device is tianchi.
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/My Stuff/Resurrection-Remix-LP-v5.5.9-20151120-togari.zip'
Error flashing zip '/external_sd/My Stuff/Resurrection-Remix-LP-v5.5.9-20151120-togari.zip'
Updating partition details...
Iata backup size is 0MB, free: 5683MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
...done
I know it's and was a standard C6833 as I use to be able to install roms before.
Anybody know of a way to change it back or have any ideas. Greatly appreciated everyone.
Click to expand...
Click to collapse
Open the updater-script and delete the lines with those C68XX numbers
Btw Tianchi is the codename for T2 Ultra isn't it?
Its the code name for the t2. I think he wants to flash a zu ROM to it. Not sure if it'll fully work, you might end up with a soft brick or an unresponsive touch screen.
Don't ever flash a different ROM for your device as it may hard brick your device!
Thanks all. I fixed the problem. Dumbo me installed Nuts TZU recovery first. Did some reading, removed it all and installed the correct zu recovery and all is okay. I can now install all the roms I want.
Lol wat... The T2 has a Snapdragon 400 with an adreno 305. Installing a Z Ultra recovery won't let you flash Z Ultra ROMs...