[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
Related
Does anyone know where I can find property files for Folio 100. I think that mblaster and DerArtem know the answer and when I type
Code:
sudo make_ext4fs -l 268435456 -a system output_file/system.img path_to_your_rom/folder_name
I get:
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 999/16384 inodes and 65063/65536 blocks
error: open_output_file: open: No such file or directory
Click to expand...
Click to collapse
Please help and sorry if I posted in wrong path
The system.prop is in the root of the repository, the default.prop is in the ramdisk subdirectory.
Here is DerArtems repository (seems to be the most up to date atm): https://github.com/DerArtem/android-device-betelgeuse
Don't know what is wrong with the make_ext4fs. I usually don't run it as root, but in principle this should not be a problem.
Thanks and do you know is this folio honeycomb kernel source?
https://github.com/DerArtem/android-tegra-2.6.36-honeycomb-folio-nvidia
What this mean? Can't find system.img?????????
error: open_output_file: open: No such file or directory
Found solution!!!
>>>>x_x<<<<...>>>>new error:
error: do_inode_allocate_extents: Failed to allocate 418 blocks
Jon2555 said:
Thanks and do you know is this folio honeycomb kernel source?
https://github.com/DerArtem/android-tegra-2.6.36-honeycomb-folio-nvidia
Click to expand...
Click to collapse
DerArtem started this, but afaik he never finished it.
Jon2555 said:
>>>>x_x<<<<...>>>>new error:
error: do_inode_allocate_extents: Failed to allocate 418 blocks
Click to expand...
Click to collapse
Sorry, never seen this error...
Thanks
Sent from my IDEOS S7 Slim using XDA App
I found what was the error. Size of files was bigger than 268 mb that I set when I want to pack system.img.
EDIT: It won't flash system.img. Only hope is to delete some files when packing if size is larger than 268.4 mb.
Hello.
I finaly post because I don't find help on the forum or on internet.
Fisrt, sorry for my bad English: I'm French and wasn't serious when at school
So please, for answer, use simple word
Like I said in the title, I have a problem with CWM.
History:
- I use original stock ROM in my Galaxy S2.
- I decide to change it to Cognition v1.5. So I root my phone, instal ROM with CWM: all is OK
- This was perfect during some month and for better performance upgrade to Cognition v1.6. No problem, phone work perfectly
- curious, I want to try another ROM. Test some, return to Cognition 1.6 retest another etc etc...
- recently, I want to return to Cognition 1.6 but I have some problem: difficult to flash under CWM but finaly taht work. But the ROM don't be very fast, not like I remember it was before. So I decide to reflashe it and now it's very problematic
Now:
- After CWM flash, the phone stay in the first screen: galaxy S2 with yellow triangle during long long time
- Trying to return to CWM, need to stay a very long time on butons to see finaly the CWM screen
- Error messages: can't mount /cache/ ... (4-5 line)
- Impossible to format, mount anything
- Only solution: flash with Odin
I try to flash stock ROM XXKI3 and after CF-root KI3 or stock ROM XXKL1 with CF-root KL1 but no difference
I try to do the same thing with ICS stock ROM and CF-root but one more time, same result
The stock ROM (with Odin) work perfectly. I try to flash with CWM another ROM (cognition v1.5) but same problem. At this time, I'm downloading simple&clean v2.4 for test another ROM.
I try to wipe data and cache before flash .zip, after flash .zip, 2-3 times but no more succes. I try to connect with adb shell (dmesg | grep mmc0) like see in this post but don't understand the result of the command (result different if I do the test under CWM or under a stock ROM working).
So I need help. I will tell here the result of the another custom ROM test later. But if you have idea, please help me !
Thanks for attention.
try this:
install a stock rom from odin use cf root to root,
go to recovery :
wipe data factory reset
wipe davik cache
go to moun and storage and format system
then go back and select the Rom zip to install from :install zip from SD card"
after isntallation dont boot,
again do a data factory wipe, and dalvik...and reboot...
hope this will work
zaheedahmed said:
try this:
install a stock rom from odin use cf root to root,
go to recovery :
wipe data factory reset
wipe davik cache
go to moun and storage and format system
then go back and select the Rom zip to install from :install zip from SD card"
after isntallation dont boot,
again do a data factory wipe, and dalvik...and reboot...
hope this will work
Click to expand...
Click to collapse
Worked for me long time ago, cant remember exacly what i did but its similar to this
OK this is the step I done:
- reboot and switch to download mode
- instal KI3 with Odin -> OK
- switch off and reboot
- switch off and reboot on download mode
- install CF-root KI3 with Odin -> OK
- switch off and reboot
- switch off and reboot on CWM mode (v4.0.0.2)
- make a log file, nothing special on the file
- wipe data -> data wipe completed without error
- wipe cache -> cache wipe completed without error
- select wipe dalvik cache menu
- error: E:unknown volume for path [/sd-ext] (maybe normal: no sd-card inserted)
- wipe dalvik cache -> without error
- reboot -> ok
- one more time, reboot in CWM mode, wipe data, wipe cache, wipe dalvik -> no error
- format system -> no error
- make a log file, result here:
Code:
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Wiping data...
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:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
Formatting /cache...
Creating filesystem with parameters:
Size: 104857600
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 25600
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6400 inodes and 1438/25600 blocks
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete
.
-- Wiping cache...
Formatting /cache...
Creating filesystem with parameters:
Size: 104857600
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 25600
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6400 inodes and 1438/25600 blocks
Cache wipe complete.
E:unknown volume for path [/sd-ext]
rm: can't remove '/data/dalvik-cache': No such file or directory
rm: can't remove '/cache/dalvik-cache': No such file or directory
rm: can't remove '/sd-ext/dalvik-cache': No such file or directory
Dalvik Cache wiped.
Formatting /system...
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
Done.
- ROM installation (zip file)
- try to do a log file -> no file writen on the directory
- wipe data
- wipe dalvik (again error unknown ...[/sd-ext])
- again try to do a log file -> no file writen on the directory
- reboot
- same result (first screen with yellow triangle)
sh*t, f**k and other world like this (in French, it's more easy )
any idea ?
The another ROM download is finish. I will try with another custom ROM
Later
OK, I try with another ROM and that work !!!
So I suppose my 2 Cognition file are corrupted .
It's strange because the file work 2 weeks ago.
I don't understand.
I'll try to find another copy of the Cognition ROM v1.6, because it's in my opinion the better ROM I have try. Light, quick with very low power consumption.
thanks for help
Ensure you are trying to restore your nandroid backup with the same cwm root kernel version which you used to make the original backup.
Flash the kernel. Tar with Odin or flash the zimage with many of the apps out there such as cwm manager and Hellcat k-tool etc
Sent from my GT-I9100 using xda premium
Thanks for help.
I'm sorry but don't understand all your explanation (French, don't forget )
I don't try to retrieve a backup, I tried to install a "fresh" version.
But don't worry, I finally find the solution (but I don't understand how I do that )
I download an old stock ROM (KG3) and try to install it.
Flash under Odin without problem (and without PIT) but a lot of message about impossible mount appears on screen during reboot. Phone freeze.
Flash again under Odin with PIT and without problem, and miracle: the ROM start
So flash the CF-root KG3, all good. Restart OK
Reboot under CWM and flash the ZIP file of the Cognition1.6 without problem. The phone restart ....
.... (unbearable suspense) ...
ALLELUIA !!!!
I'm back to cognition1.6 !!!!
More seriously, if someone can explain why that works, I'll be less stupid
Thanks all for your help, I hope my problem can help someone else.
Bye
Damaged partition information table is why flashing PIT fixed .
jje
Hello!
I think this post may be of more relevance to Development. But unfortunately, I do not have enough posts to do so. I usually don't have to post at all, thanks to searching.
This time I can't seem to find an answer to my problem, so here it goes;
I have an Eris that I'm using at the moment. I rooted it(or so I thought) back in the day. It seemed to work fine back then, and everything was dandy.
Never went about installing a custom ROM though, so I attempted. After I started it up, I realized I had made the worst mistake of them all. I didn't make a nandroid backup of the stock ROM. After a couple boot loops of the Cyanogen logo, I powered it into the bootloader to find that "S-ON" was showing. I cried a little at that moment.
If I try to install any other ROM(stock, EvilEris, etc.), it does not work. And after a couple of attempts of trying to install CM again, now only getting to the skateboarding androids, I have no idea what to do.
Does anyone possibly have a solution to this? I'm at a complete loss not being able to actually boot the phone into the ROM.
Also, everytime I try to just throw a PB00IMG.ZIP on the root of the SD card, it says there's "No image!"
Thank you for any help,
-Kickore
kickore said:
Hello!
I think this post may be of more relevance to Development. But unfortunately, I do not have enough posts to do so. I usually don't have to post at all, thanks to searching.
This time I can't seem to find an answer to my problem, so here it goes;
I have an Eris that I'm using at the moment. I rooted it(or so I thought) back in the day. It seemed to work fine back then, and everything was dandy.
Never went about installing a custom ROM though, so I attempted. After I started it up, I realized I had made the worst mistake of them all. I didn't make a nandroid backup of the stock ROM. After a couple boot loops of the Cyanogen logo, I powered it into the bootloader to find that "S-ON" was showing. I cried a little at that moment.
If I try to install any other ROM(stock, EvilEris, etc.), it does not work. And after a couple of attempts of trying to install CM again, now only getting to the skateboarding androids, I have no idea what to do.
Does anyone possibly have a solution to this? I'm at a complete loss not being able to actually boot the phone into the ROM.
Also, everytime I try to just throw a PB00IMG.ZIP on the root of the SD card, it says there's "No image!"
Thank you for any help,
-Kickore
Click to expand...
Click to collapse
Before you try the PB00IMG.zip, are you going into the Wipe menu and choosing the option "Wipe data/factory reset" before restarting the phone? If not, try starting in Recovery, do just that, and then try to restart. (Depending on the CM ROM you are installing, you may need to install a Google apps zip as well, if you have not already done so. However, it will boot without Google apps - you just will not have the market.)
This is what happens when I go to wipe/factory reset the phone.
I'm sorry I wasn't a bit more descriptive in my first post.
I have clockwork mod recovery 2.5.0.1.
...With S-On...
This picture shows why I can't love anything.
Since you have clockwork recovery, definitely do not try a PB00IMG.zip. There have been bricked phones from this.
See this post: http://forum.xda-developers.com/showpost.php?p=12131623&postcount=9
This may be a good idea. That line "Can't read MISC" - I wonder if you have some bad blocks on that partition (or others)? Anyway, read through that post I listed above, flash that zip file, and it will create a file on the SD card called "MTD_Inspect.txt". Let's see what that shows.
(I think that once we determine the state of flash storage, the best bet may be to flash the Flashback_21v2, which will return the phone to stock, unrooted, and then you can re-root using ScaryAlien's modified version of JCase's 1-click root app to get Amon_RA recovery on the phone. Getting S-OFF going forward may not be such a bad idea, but one step at a time.)
Listen to doogald, he's giving you some good advice!
doogald said:
Since you have clockwork recovery, definitely do not try a PB00IMG.zip. There have been bricked phones from this.
See this post: http://forum.xda-developers.com/showpost.php?p=12131623&postcount=9
This may be a good idea. That line "Can't read MISC" - I wonder if you have some bad blocks on that partition (or others)? Anyway, read through that post I listed above, flash that zip file, and it will create a file on the SD card called "MTD_Inspect.txt". Let's see what that shows.
(I think that once we determine the state of flash storage, the best bet may be to flash the Flashback_21v2, which will return the phone to stock, unrooted, and then you can re-root using ScaryAlien's modified version of JCase's 1-click root app to get Amon_RA recovery on the phone. Getting S-OFF going forward may not be such a bad idea, but one step at a time.)
Click to expand...
Click to collapse
Sorry it took a minute.
Here's what the MTD inspect gave me.
Code:
Eris MTD Partition Status Report Generated on Fri May 18 22:11:36 UTC 2012
PARTITION DEVICE_NAME SIZE(Bytes) BAD_BLOCKS #_E-BLKS ECC_FAIL ECC_CORR BBT_BLOCKS
misc /dev/mtd/mtd0 655360 0 5 0 0 0
recovery /dev/mtd/mtd1 5242880 0 40 0 0 0
boot /dev/mtd/mtd2 2621440 20 20 0 0 0
system /dev/mtd/mtd3 178257920 1350 1360 0 0 0
cache /dev/mtd/mtd4 136314880 9 1040 18 0 0
userdata /dev/mtd/mtd5 167247872 1 1276 0 0 0
#################################### misc PARTITION ###################################
Partition Symbolic Name: misc
Partition (character-special) Device: /dev/mtd/mtd0
Partition Total Size: 655360
Partition EraseBlock Size: 131072
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...
#################################### recovery PARTITION ###################################
Partition Symbolic Name: recovery
Partition (character-special) Device: /dev/mtd/mtd1
Partition Total Size: 5242880
Partition EraseBlock Size: 131072
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...
#################################### boot PARTITION ###################################
Partition Symbolic Name: boot
Partition (character-special) Device: /dev/mtd/mtd2
Partition Total Size: 2621440
Partition EraseBlock Size: 131072
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 20
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...
ECC: 1 uncorrectable bitflip(s) at offset 0x00000000
ECC: 1 uncorrectable bitflip(s) at offset 0x00000800
#################################### system PARTITION ###################################
Partition Symbolic Name: system
Partition (character-special) Device: /dev/mtd/mtd3
Partition Total Size: 178257920
Partition EraseBlock Size: 131072
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 1350
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...
ECC: 1 uncorrectable bitflip(s) at offset 0x00000000
ECC: 1 uncorrectable bitflip(s) at offset 0x00000800
#################################### cache PARTITION ###################################
Partition Symbolic Name: cache
Partition (character-special) Device: /dev/mtd/mtd4
Partition Total Size: 136314880
Partition EraseBlock Size: 131072
ECC failed: 18
ECC corrected: 0
Number of bad blocks: 9
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...
ECC: 1 uncorrectable bitflip(s) at offset 0x00000000
ECC: 1 uncorrectable bitflip(s) at offset 0x00000800
#################################### userdata PARTITION ###################################
Partition Symbolic Name: userdata
Partition (character-special) Device: /dev/mtd/mtd5
Partition Total Size: 167247872
Partition EraseBlock Size: 131072
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 1
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 0
Dumping data starting at 0x00000000 and ending at 0x00001000...
Apparently, I have a few.
Ok, the next step is probably to try what is in this post: http://forum.xda-developers.com/showpost.php?p=11651122&postcount=21
That post mentions that you should download a decent ROM, but I think that you are already there.
Just a quick note: you should also read the warning in bright red here: http://forum.xda-developers.com/showpost.php?p=11652502&postcount=40
Never mind, I'll quote it:
ErisMTDNuke_v0.9.zip IS EXTREMELY DANGEROUS AND SHOULD NOT BE USED WILLY-NILLY. IT'S ONLY USE IS FOR DESPERATE, LAST-RESORT MEASURES - CLOCKWORK "SOFT BRICKINGS" WHERE PARTITION CORRUPTION IS EVIDENT.
Click to expand...
Click to collapse
At this point, please understand that your phone is bricked and it may not come back. Let's see what the ErisMTDNuke does, though.
I mentioned earlier the thought of unrooting by flashing Flashback and then re-rooting with JCase's 1-click app. That's still a possibility, too. That will at least replace the Clockwork Recovery with stock Recovery. However, the other way is to flash the CM7 ROM that you were going to flash anyway and replace the recovery using the app GScript Lite.
Flashback can be downloaded from here: http://forum.xda-developers.com/showthread.php?t=792026
You can download the one without the radio, if that's what you want to do.
Anyway, let's see what ErisMTDNuke does. Good luck.
Dear doogald,
You are the coolest person on the internet. You have saved my phone by referencing forum posts made years ago that I totally couldn't figure out by myself.
Thank you very much.
I'm happy to announce that my phone has completed it's boot into stock, and I can now drag down my lock screen and activate my phone on the Verizon network.
I'll take to Jcase's one-click app tomorrow.
Thank you again,
-Kickore
P.s. Seriously, the coolest person on the internet ever.
Wow, that's awesome. Thanks redirected to bftb0, who did all of that work.
The way to install Amon_RA is here: http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
You should be able to use Scenario 5 in the first post (the JCase 1-click app method) that ScaryAlien mentions that it works with stock or stock-based ROMs like xtrSENSE. Just remember that 1-click works like this:
- allow third party app installs in settings->applications
- install the app (you may need the free app Astro File Manager to actually install by opening the .apk file in that app and choosing to install the app)
- run the 1-click app
- shut down and restart the phone - don't restart in recovery; restart as if you were going to make a phone call
- shut down and restart in Recovery by holding VolUp while booting
At some point I'll also post what you'd need to do to get the S-OFF engineering bootloader on, which will allow you to fastboot flash to recover any future problems (which, knock wood, will not happen...)
I attempted Jcase's app. It did give me Amon_RA's Recovery. It did not give me S-Off though, which I'm assuming is why you mentioned the engineering bootloader in your last post.
On a side note, I decided to experiment with something that wasn't clockwork mod, and found that I can flash custom ROMs with this Recovery. I also backed up my stock one this time, JUST IN CASE!
Well, it worked and I'm running GSB v4.5!
Still, I really appreciate it regardless of who originally found/wrote the documentation on how to do it. I'm a user with like 5 posts due to everything being figured out usually, and you're still helping instead of "GOOGLE IT."
So thank you.
kickore said:
I attempted Jcase's app. It did give me Amon_RA's Recovery. It did not give me S-Off though, which I'm assuming is why you mentioned the engineering bootloader in your last post.
Click to expand...
Click to collapse
Which version of the bootloader do you have? It will either be 1.46.0000, 1.47.0000, or 1.49.0000. (The method to get the 1.49.2000 S-OFF depends on which you have now, IIRC.)
I currently have the 1.47.0000.
kickore said:
I currently have the 1.47.0000.
Click to expand...
Click to collapse
Ok. I am away for the weekend, but will try to get some detailed instructions ASAP. The generalized instructions, though (and it's quite a few steps, sorry to say):
- get a copy of the root PB00IMG.zip file onto the SD card
- get a copy of Flashback (with radio) onto the SD card
- get a copy of ScaryAlien's version of JCase's 1-click root app on the SD card (which I belive you have)
- Nandroid backup when you have now
- start in HBOOT and let the phone run the root PB00IMG.zip (it should detect and ask you to flash it automatically). This gives you 1.49.2000 S-OFF with an old version of the Eris ROM
- * Run the JCase root app (this gets you Amon_RA Recovery back)
- Flash Flashback with radio (this gets you the updated radio back - the root PB00IMG.zip file will flash an older version of the radio)
- Run the JCase root app again to root the phone
- Restart in Recovery and Nandroid Restore GSB
- restart and you'll be back where you were with S-OFF
- (Important) Erase the PB00IMG.zip file from the SD card (or rename it or move it into a folder).
(I may have missed a step - this is off the top of my head. Also, the step with * may be wrong - I think that the root ROM is Android 1.5 and JCase's root app may not run. I don't recall - I'll need to check on that one...)
There is no need! I figured it out from what you said. I'm not really that new at this whole rooting process... But I'm not a programmer and would not have been able to do anything otherwise. I really do appreciate your help.
Thank you so very much!
-Kickore
Edit:
As a suggestion, perhaps making a new guide for anyone who comes to this forum can easily get the files which are now dead links. As well as follow a comprehensive guide on the rooting process.
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
My phone is rooted using Kingoroot its was all running smooth until i update my phone now its stuck on boot logo i really need SWIPE KONNCET PLUS STOCK FIRMWARE Please help me please :crying: :crying:
Zaroonok said:
My phone is rooted using Kingoroot its was all running smooth until i update my phone now its stuck on boot logo i really need SWIPE KONNCET PLUS STOCK FIRMWARE Please help me please :crying: :crying:
Click to expand...
Click to collapse
What android version where you at and what did it upgrade to? Also, try booting into recovery and erasing all data.
i had tried everything i had wipe cache it and hard reset it too but still nothing work for me i just need a stock firmware of that mobile (Mobile name is swipe konnect plus ) and my phone android version is 5.1 lollipop please help me :crying:
what recovery is installed?
Need stock rom and custom recovery
Hey pls give me swipe konnect plus stock rom and custom recovery
aksthecount said:
Hey pls give me swipe konnect plus stock rom and custom recovery
Click to expand...
Click to collapse
That is unfortunately not how it works here...
swipe konnect plus error on inatalling cm12.1
I port a cm 12.1 for swipe konnect plus mt6580 when I flash cm with twrp 3.0.1 I am getting error like this.
Installing zip file '/sdcard/files/CyanoGenMod 12.1.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.
/file_contexts: line 262 has invalid file type ubject_r:wmtWifi_device:s0/cache/dalvik-cache(/.*)?
|========================|
| CM12.1 r36 March BUILD |
| For Micromax A106 |
| BY MANAN VALLECHA |
| ---thanks from heart-- |
|Vijay , Ranjan , Vivek |
|Source - Rohan Taneja |
|========================|
minzip: Extracted 3 file(s)
could not detect filesystem for /dev/block/mmcblk0p5, assuming ext4
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
mount: failed to mount /dev/block/mmcblk0p5 at /system: Invalid argument
unmount of /system failed; no such volume
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
Creating filesystem with parameters:
Size: 262144
Block size: 4096
Blocks per group: 32768
Inodes per group: 16
Inode size: 256
Journal blocks: 1024
Label:
Transparent compression: none
Blocks: 64
Block groups: 1
Reserved block group size: 7
error: ext4_allocate_best_fit_partial: failed to allocate 973 blocks, out of space?
format: make_ext4fs failed (1) on /dev/block/mmcblk0p5could not detect filesystem for /dev/block/mmcblk0p5, assuming ext4
mount: failed to mount /dev/block/mmcblk0p5 at /system: Invalid argument
minzip: Extracted 1493 file(s)
ApplyParsedPerms: removexattr of /system/xposed.prop to 0 failed: Operation not supported on transport endpointscript aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '/sdcard/files/CyanoGenMod 12.1.zip'
What to do pls help me pls........pls.......
aksthecount said:
I port a cm 12.1 for swipe konnect plus mt6580 when I flash cm with twrp 3.0.1 I am getting error like this.
Installing zip file '/sdcard/files/CyanoGenMod 12.1.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.
/file_contexts: line 262 has invalid file type ubject_r:wmtWifi_device:s0/cache/dalvik-cache(/.*)?
|========================|
| CM12.1 r36 March BUILD |
| For Micromax A106 |
| BY MANAN VALLECHA |
| ---thanks from heart-- |
|Vijay , Ranjan , Vivek |
|Source - Rohan Taneja |
|========================|
minzip: Extracted 3 file(s)
could not detect filesystem for /dev/block/mmcblk0p5, assuming ext4
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
mount: failed to mount /dev/block/mmcblk0p5 at /system: Invalid argument
unmount of /system failed; no such volume
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
Creating filesystem with parameters:
Size: 262144
Block size: 4096
Blocks per group: 32768
Inodes per group: 16
Inode size: 256
Journal blocks: 1024
Label:
Transparent compression: none
Blocks: 64
Block groups: 1
Reserved block group size: 7
error: ext4_allocate_best_fit_partial: failed to allocate 973 blocks, out of space?
format: make_ext4fs failed (1) on /dev/block/mmcblk0p5could not detect filesystem for /dev/block/mmcblk0p5, assuming ext4
mount: failed to mount /dev/block/mmcblk0p5 at /system: Invalid argument
minzip: Extracted 1493 file(s)
ApplyParsedPerms: removexattr of /system/xposed.prop to 0 failed: Operation not supported on transport endpointscript aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '/sdcard/files/CyanoGenMod 12.1.zip'
What to do pls help me pls........pls.......
Click to expand...
Click to collapse
What'd you use to port the ROM? Android kitchen or yourself? What kernel do you use?
I port it myself with XDA guide
I use custom ROM kernal 3.4.x and copy my kernal file uevent.tc and zimage file my kernal very is 3.10.72+
---------- Post added at 03:56 PM ---------- Previous post was at 03:53 PM ----------
It says unable to mount dev/block/mmcblk05/at system
---------- Post added at 04:01 PM ---------- Previous post was at 03:56 PM ----------
What does that mean
Hey, RAZERDAHACKER pls hlp me pls,pls,.......
Stock firmware for swipe konnect plus
aksthecount said:
Hey pls give me swipe konnect plus stock rom and custom recovery
Click to expand...
Click to collapse
Hello , if you really want the stock firmware then reply of this message . I will tell you where you can find the STOCK firmware for this device. But for sharing link of another Website i need permission from this XDA team. If they allow me then i can post here the link of the STOCK firmware.
Thank you .. and waiting for your reply.
sorry for late mess yaa give me the link
aksthecount said:
sorry for late mess yaa give me the link
Click to expand...
Click to collapse
tap on the quoted thread below to view the full answer
x.ak**** said:
like all my comments above to encourage me to help you.
Okay so first of all i will let you know why a phone gets bricked-
>corrupted rom
>some system files got deleted
>rooting
>modding
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
my case
i always keep two phones with me like one for my experiments and one as a backup. In this case i'll be talking about my lyf wind 3 that got bricked.
>actually i was trying to install twrp onto that phone but first i had to root it, and due to the upgraded android security, i wasn't able to do via kingoroot so i tried i-root and it did the job but instead of kingo-superuser i got some ****ty superuser so i tried granting permission to the actual superuser and while doing so i accidentally double rooted my phone (first with i-root and then with kingoroot), which was kinda stupid, so it just deleted some system files and my phone wouldn't boot after that. It just got stuck on the boot logo.
Click to expand...
Click to collapse
x.ak**** said:
tap on the quoted thread below to view the full answer
Click to expand...
Click to collapse
My case was that I flash cm 12 on my swipe konnect plus n was working fine but was reddish the common bug of cyanogenmod
and it can be fixed no matter how many I change file to clear bug so I just lost hope then I restore my stock via twrp n then the mobile was lagging to much so then I thought that it must be coz that twrp didn't restore my stock properly so search on Google swipe konnect plus firmware n I got the site on firmwarefile.com there was three stock room for swipe konnect plus so I download all of them n when I flash one of them it got brick then I flash another but sp flash tool giving me error "dram enable failed"
So I googled it n found that if we flash wrong preloader it hard brick your device that means the firmware for swipe konnect plus on the website r all wrong firmware n also check the build.prop of it was written the same model but I don't know what is happening I just want to abuse whoever upload swipe konnect plus firmware coz it brick my device pls if anyone is reading this pls pls pls pls help me to I just want preloader.bin file for my device if anyone anyone or your frnd is using swipe konnect plus pls pls pls pls contact me on my email [email protected]
---------- Post added at 09:29 PM ---------- Previous post was at 09:21 PM ----------
Zaroonok said:
My phone is rooted using Kingoroot its was all running smooth until i update my phone now its stuck on boot logo i really need SWIPE KONNCET PLUS STOCK FIRMWARE Please help me please :crying: :crying:
Click to expand...
Click to collapse
Hey do u still have swipe konnect plus reply me pls