Post Reply

Null

OP Infinimint

18th March 2012, 09:51 AM   |  #11  
mahroze's Avatar
Senior Member
Flag Lahore
Thanks Meter: 6
 
193 posts
Join Date:Joined: Aug 2010
More
i did flashed it but it failed to boot into the new recovery i flashed it via adb had to re flash amon ra recovery
18th March 2012, 01:03 PM   |  #12  
Member
Thanks Meter: 7
 
58 posts
Join Date:Joined: Oct 2009
More
Quote:
Originally Posted by mahroze

i did flashed it but it failed to boot into the new recovery i flashed it via adb had to re flash amon ra recovery

I have the same problem
jianC
19th March 2012, 01:59 AM   |  #13  
Guest
Thanks Meter: 0
 
n/a posts
Only works for 32B Sapphire for some strange reason. I'm sure xillius and Infinimint are working on it and will post it soon
19th March 2012, 02:38 PM   |  #14  
ezterry's Avatar
Retired Recognized Developer
Flag Asheville, NC
Thanks Meter: 1,000
 
1,823 posts
Join Date:Joined: Jan 2010
Donate to Me
More
Quote:
Originally Posted by e334

Only works for 32B Sapphire for some strange reason. I'm sure xillius and Infinimint are working on it and will post it soon

Prob you just swap in my ezgb ebi0 kernel kernel for full dream/sapphire 32b support and not whatever was pulled by the cyanogen build tree.

Either by updating the build or just unpacking/repacking recovery.

(yes you want recovery with ebi0 even if your rom is 2708+, we will live without the extra ram in recovery.. and its safer ie. prevents bricks that would otherwise happen on some operations.)

That or use an older cm kernel.

Regardless recovery.img has a kernel included.. best to link to the source code per gpl.. may also want to link to busy box source. (The one in cm's tree is used for cwm)

Biggest question is there any issue with the yes no script of mine used in some install scripts with the new cwm.. since there have been complaints on other devices of not being able to get it to work.

Sent from my Galaxy Nexus using Tapatalk
The Following User Says Thank You to ezterry For This Useful Post: [ View ]
19th March 2012, 05:18 PM   |  #15  
Infinimint's Avatar
OP Senior Member
Flag Fredericksburg, VA
Thanks Meter: 297
 
652 posts
Join Date:Joined: Oct 2010
Donate to Me
More
Quote:
Originally Posted by ezterry

Prob you just swap in my ezgb ebi0 kernel kernel for full dream/sapphire 32b support and not whatever was pulled by the cyanogen build tree.

Either by updating the build or just unpacking/repacking recovery.

(yes you want recovery with ebi0 even if your rom is 2708+, we will live without the extra ram in recovery.. and its safer ie. prevents bricks that would otherwise happen on some operations.)

That or use an older cm kernel.

Regardless recovery.img has a kernel included.. best to link to the source code per gpl.. may also want to link to busy box source. (The one in cm's tree is used for cwm)

Biggest question is there any issue with the yes no script of mine used in some install scripts with the new cwm.. since there have been complaints on other devices of not being able to get it to work.

Sent from my Galaxy Nexus using Tapatalk

When I get home, I'll compile it using your kernel
As for yesno, I'll take a look as well.

Sent from my HTC Flyer P512 using Tapatalk
19th March 2012, 05:24 PM   |  #16  
xaueious's Avatar
Senior Member
Flag Toronto
Thanks Meter: 144
 
949 posts
Join Date:Joined: Dec 2009
Donate to Me
More
Thanks. Ported to 32A.


Using Amon-RA Sapphire 1.7.0G kernel

Thanks

Radio-3.22.26.17 tested okay
Attached Files
File Type: img recovery-cwm5-sapphire-32A-3.22.26.17.img - [Click for QR Code] (3.17 MB, 49 views)
Last edited by xaueious; 19th March 2012 at 05:47 PM.
The Following 2 Users Say Thank You to xaueious For This Useful Post: [ View ]
19th March 2012, 09:44 PM   |  #17  
Infinimint's Avatar
OP Senior Member
Flag Fredericksburg, VA
Thanks Meter: 297
 
652 posts
Join Date:Joined: Oct 2010
Donate to Me
More
Quote:
Originally Posted by xaueious

Thanks. Ported to 32A.


Using Amon-RA Sapphire 1.7.0G kernel

Thanks

Radio-3.22.26.17 tested okay

Nice , I'm going to try to support all the D/S phones. Until then, do you mind if I add it to the OP?

Sent from my HTC PH39100 using Tapatalk
20th March 2012, 01:35 AM   |  #18  
Member
Flag ShenZhen,GuangDong Province
Thanks Meter: 1
 
32 posts
Join Date:Joined: May 2009
something confuse me now.i once tried to flash this recovery with my dream,obviously it failed at last.but the strange thing was after that i cannot flash any recovery any more.it showed:

Code:
$ export PATH=/data/local/bin:$PATH
$ su
# flash_image recovery /sdcard/170.img
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
mtd: read error at 0x00080000 (Out of memory)
mtd: read error at 0x000a0000 (Out of memory)
mtd: read error at 0x000c0000 (Out of memory)
mtd: read error at 0x000e0000 (Out of memory)
mtd: read error at 0x00100000 (Out of memory)
mtd: read error at 0x00120000 (Out of memory)
mtd: read error at 0x00140000 (Out of memory)
mtd: read error at 0x00160000 (Out of memory)
why,sorry for that.....
jianC
20th March 2012, 02:51 AM   |  #19  
Guest
Thanks Meter: 0
 
n/a posts
Quote:
Originally Posted by WongHokZau

something confuse me now.i once tried to flash this recovery with my dream,obviously it failed at last.but the strange thing was after that i cannot flash any recovery any more.it showed:

Code:
$ export PATH=/data/local/bin:$PATH
$ su
# flash_image recovery /sdcard/170.img
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
mtd: read error at 0x00080000 (Out of memory)
mtd: read error at 0x000a0000 (Out of memory)
mtd: read error at 0x000c0000 (Out of memory)
mtd: read error at 0x000e0000 (Out of memory)
mtd: read error at 0x00100000 (Out of memory)
mtd: read error at 0x00120000 (Out of memory)
mtd: read error at 0x00140000 (Out of memory)
mtd: read error at 0x00160000 (Out of memory)
why,sorry for that.....

I had that strange error too. Did you have custom MTD when you flash the file?
20th March 2012, 03:02 AM   |  #20  
Account currently disabled
Thanks Meter: 36
 
119 posts
Join Date:Joined: Nov 2011
Quote:
Originally Posted by e334

I had that strange error too. Did you have custom MTD when you flash the file?

I don't see what custom MTD has to do with it

it says out of memory
could it be that the ram is full?

do you have adb?

try this

adb shell
Code:
free
stop zygote
free
flash_image recovery /sdcard/170.img
start zygote

The Following User Says Thank You to Scrip For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes