I will be releasing 6.0.1.1 soon, and it will have some fomratting changes
6.0.1.1 doesnt actually have anything terribly important
6.0.1.1 doesnt actually have anything terribly important
[Recovery]Clockwork Mod 6.0.1.2
- Thread starter TheManii
- Start date
-
- Tags
- development
Updated to 6.0.1.1, includes changes to formatting code for future roms.
Streak 5
Please forgive me if this question was asked before.
I have streak 5 and I am running ICS 4.0.4_r2.1 now, in the Gapps package, it says it will require Clockwork Mod 6.0 or other.
So, is this compatible with ICS 4.0.4_r2.1? I am also going to test Longhorn 2.9.1 would this be compatible with it too?
Is everyone making new roms now compatible with CWM 6.0.1.1?
I did not want to flash this and then mess everything I have on the phone for no reason, I like to ask first, and I did search this thread and could not find a clear statement regarding Streak 5. Thanks,
Please forgive me if this question was asked before.
I have streak 5 and I am running ICS 4.0.4_r2.1 now, in the Gapps package, it says it will require Clockwork Mod 6.0 or other.
So, is this compatible with ICS 4.0.4_r2.1? I am also going to test Longhorn 2.9.1 would this be compatible with it too?
Is everyone making new roms now compatible with CWM 6.0.1.1?
I did not want to flash this and then mess everything I have on the phone for no reason, I like to ask first, and I did search this thread and could not find a clear statement regarding Streak 5. Thanks,
This is for the S7, the one you want is for the S5.
I tested it with AOSP/ICS and it seems to work, I havnt done thourgh testing yet though.
There is still a streakmod specific gapps if you still wish to use it.
I tested it with AOSP/ICS and it seems to work, I havnt done thourgh testing yet though.
There is still a streakmod specific gapps if you still wish to use it.
How long should it take to flash this? I noticed it a bit larger that some of the other CWM images, but shouldn't it be fairly quick to flash? Mine sits on sending for a few minutes.
Nevermind. I see that I had my phone plugged in to the PC too. <-- dummy.
Nevermind. I see that I had my phone plugged in to the PC too. <-- dummy.
Last edited:
If anyone can tell me why these errors occur and how to fix it:
This issue was introduced in
Add minizip tool. · 4e734a3 · CyanogenMod/android_bootable_recovery · GitHub:
It's some sort of issue in zlib, and until someone can tell me how to fix/workaround it, I cant build newer versions of CWM for any device.
Code:
prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: out/target/product/streak7/obj/STATIC_LIBRARIES/libminizip_intermediates/libminizip.a(minizip.o): in function check_exist_file:bootable/recovery/utilities/../../../external/zlib/contrib/minizip/minizip.c:158: error: undefined reference to 'fopen64'
prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: out/target/product/streak7/obj/STATIC_LIBRARIES/libminizip_intermediates/libminizip.a(minizip.o): in function isLargeFile:bootable/recovery/utilities/../../../external/zlib/contrib/minizip/minizip.c:228: error: undefined reference to 'fopen64'
prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: out/target/product/streak7/obj/STATIC_LIBRARIES/libminizip_intermediates/libminizip.a(minizip.o): in function isLargeFile:bootable/recovery/utilities/../../../external/zlib/contrib/minizip/minizip.c:232: error: undefined reference to 'fseeko64'
prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: out/target/product/streak7/obj/STATIC_LIBRARIES/libminizip_intermediates/libminizip.a(minizip.o): in function isLargeFile:bootable/recovery/utilities/../../../external/zlib/contrib/minizip/minizip.c:233: error: undefined reference to 'ftello64'
prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: out/target/product/streak7/obj/STATIC_LIBRARIES/libminizip_intermediates/libminizip.a(minizip.o): in function getFileCrc:bootable/recovery/utilities/../../../external/zlib/contrib/minizip/minizip.c:189: error: undefined reference to 'fopen64'
prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: out/target/product/streak7/obj/STATIC_LIBRARIES/libminizip_intermediates/libminizip.a(minizip.o): in function minizip_main:bootable/recovery/utilities/../../../external/zlib/contrib/minizip/minizip.c:463: error: undefined reference to 'fopen64'
prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: out/target/product/streak7/obj/STATIC_LIBRARIES/libbusybox_intermediates/libbusybox.a(mktemp.o): in function mktemp_main:external/busybox/debianutils/mktemp.c:94: warning: warning: tempnam() possibly used unsafely; consider using mkstemp()
collect2: ld returned 1 exit status
make: *** [out/target/product/streak7/obj/EXECUTABLES/recovery_intermediates/LINKED/recovery] Error 1Add minizip tool. · 4e734a3 · CyanogenMod/android_bootable_recovery · GitHub:
It's some sort of issue in zlib, and until someone can tell me how to fix/workaround it, I cant build newer versions of CWM for any device.
I've seen that, and that's not it.
It did lead me to what I was missing:
minizip: fix up erroneous fopen64 usage. · fe301a9 · CyanogenMod/android_external_zlib · GitHub:
Seems that the commit isnt being propagated back to the CM9 branch, the fix was included in CM91/ICS
Looks like I'll have to migrate my stuff to CM91 eventually
As a note: I will not be migrating over to JB for the purposes of building CWM any time soon, it requires (slight) syntax changes and a new update-binary.
I dont expect them to be backwords or forwards compatable, so until there's enough changes in CWM/JB to warrent it, we'll be sticking with CWM/ICS for until then.
Currently CWM/JB is only a single revision ahead of CWM/ICS, it will fall further and further behind as work ramps up on CM10.
Do you have any opinion on it giveen?
What the difference mainly will mean are incompatable update scripts/binaries.
Edit: actually come to think of it: I would strongly prefer staying on CWM/ICS as it would also affect my S5/S10/V builds
Edit2: TWRP/JB is still in development, so we dont have a choice.
It did lead me to what I was missing:
minizip: fix up erroneous fopen64 usage. · fe301a9 · CyanogenMod/android_external_zlib · GitHub:
Seems that the commit isnt being propagated back to the CM9 branch, the fix was included in CM91/ICS
Looks like I'll have to migrate my stuff to CM91 eventually
As a note: I will not be migrating over to JB for the purposes of building CWM any time soon, it requires (slight) syntax changes and a new update-binary.
I dont expect them to be backwords or forwards compatable, so until there's enough changes in CWM/JB to warrent it, we'll be sticking with CWM/ICS for until then.
Currently CWM/JB is only a single revision ahead of CWM/ICS, it will fall further and further behind as work ramps up on CM10.
Do you have any opinion on it giveen?
What the difference mainly will mean are incompatable update scripts/binaries.
Edit: actually come to think of it: I would strongly prefer staying on CWM/ICS as it would also affect my S5/S10/V builds
Edit2: TWRP/JB is still in development, so we dont have a choice.
Last edited:
Easiest thing to do is to just create a new directory and build from there.
Like I have to CM10 builds now, one for TWRP and one for CM10, that way my commits to each don't affect one or the other.
Like I have to CM10 builds now, one for TWRP and one for CM10, that way my commits to each don't affect one or the other.
Does this update support new internal SD cards 8&16 GB?
I did upgrade mine to 16GB and having very slow sluggish performance using Ics ROM.
I will try to do some experiments with the SD format ext4 and see if any improvement.
Edit:
sorry I meant to put this in the DS5
Sent from my SAMSUNG-SGH-I717 using xda premium
I did upgrade mine to 16GB and having very slow sluggish performance using Ics ROM.
I will try to do some experiments with the SD format ext4 and see if any improvement.
Edit:
sorry I meant to put this in the DS5
Sent from my SAMSUNG-SGH-I717 using xda premium
Last edited:
cant download files Clockwork mod recovery.img "connection was reset", any others links for this.
The server appears to be having a problem that started today.
I'm not sure if it's up at http://mirror2.streakdroid.com/manii/ or not.. That server has on/off DNS issues but changing your DNS to Google's 8.8.8 or 8.8.4, I understand works. Here's how to do that: https://developers.google.com/speed/public-dns/docs/using.
Last edited:
TheManii dev-host site is better to use now
Sent from my Nexus 7 using Tapatalk 2
Sent from my Nexus 7 using Tapatalk 2
Recovery will not flash
I'm simply trying to update to stock honeycomb (or higher). I'm happy to root if necessary as long as cellular data work. When I try flashing an updated stock recovery or even try to flash CWM via fastboot I get an error that says
Looks like this on the command prompt
Not sure why I would be having partition issues when I just did a full NVFlash last night.
Any help would be much appreciated.
Oh and when I try to update via settings > software update I get this
I'm simply trying to update to stock honeycomb (or higher). I'm happy to root if necessary as long as cellular data work. When I try flashing an updated stock recovery or even try to flash CWM via fastboot I get an error that says
Looks like this on the tablet:
Looks like this on the command prompt
Not sure why I would be having partition issues when I just did a full NVFlash last night.
Any help would be much appreciated.
Oh and when I try to update via settings > software update I get this
Looks like this when I go to update it:
Is the version in the 1st/3rd picture correct?
If you really are on 336, that's a froyo rom
I do have S7f-3.0.2.0.img which was supposed to be for stock 3xx bootloaders.
But I definitely cant provide support on it as
If you really are on 336, that's a froyo rom
You must upgrade to 5xx/honeycomb to be able to use normal versions.
I do have S7f-3.0.2.0.img which was supposed to be for stock 3xx bootloaders.
But I definitely cant provide support on it as
- I've never used my s7 with a 3xx rom
- I dont have my s7 handy/dont use it anymore
New posts
-
[ROM][OTA][UNOFFICIAL] AOSiP Pie- Latest: magnamentis
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone