Develop Bugs

Interim ClockworkMod Touch Recovery for the HTC One X (+stock download)

Hi folks!
Until such time as an official ClockworkMod recovery is available, I have created an interim (non official) ClockworkMod Touch release. Please note that the One X doesn't seem to enable access to USB when booted as recovery (proven by flashing the recovery partition with the insecure boot), so you will not be able to use ADB etc. at this time.
INSTALL AND USE AT YOUR OWN RISK!
Your bootloader must be unlocked via htcdev.com to install this.
To use, either flash via fastboot ('fastboot flash recovery r1-modaco-recovery-clockwork-touch-endeavoru.img') or boot directly ('fastboot boot r1-modaco-recovery-clockwork-touch-endeavoru.img').
MOD EDIT: warning!!! old recovery with charging issues and NO USB Mount use latest recovery from here or TWRP
I have also uploaded the stock recovery should you wish to flash it (e.g. for OTA).
Enjoy!
DOWNLOAD - MD5: f47ebe81400c00ddefc0499d2a18b9fd
DOWNLOAD - MD5: 4af6f2b658d2e13f72e928a72fcde9cd
P
PS If you find this useful, details on how to donate should you wish to do so are available in the MoDaCo topic.

You are the man!
What works actually?

I did a backup and restore, I imagine most of the functions should work. The lack of USB (and therefore ADB) is annoying (i'm investigating), but that aside you should do all the stuff you need to.
Obviously it's a quick hack-up so use with care!
P

paulobrien said:
I did a backup and restore, I imagine most of the functions should work. The lack of USB (and therefore ADB) is annoying (i'm investigating), but that aside you should do all the stuff you need to.
Obviously it's a quick hack-up so use with care!
P
Click to expand...
Click to collapse
Awesome news. Anything on s-off yet ?
Sent from my HTC One X using xda premium

paulobrien said:
I did a backup and restore, I imagine most of the functions should work.
Click to expand...
Click to collapse
that is the most important thing to know

Stock recovery download added should you wish to revert.
P

Thanks Paul, that sounds really good!
The best would be if the Revolutionary team would now release the S-OFF tool which supports our device..

paulobrien said:
I did a backup and restore, I imagine most of the functions should work. The lack of USB (and therefore ADB) is annoying (i'm investigating), but that aside you should do all the stuff you need to.
Obviously it's a quick hack-up so use with care!
P
Click to expand...
Click to collapse
hey Paul in the ICS kernel there is a difference in the USB gadget... so there is different way to activate ADB... i will get to work on it...
but i need the mkbootimg parameters to repack the zImage and ramdisk...
BTW i will be working on my own version of touch recovery
here is a video of it workign on another of my supported devices...

Yeah, it's not that - a fully working boot image that's OK in boot mode doesn't give you USB in recovery mode. Very odd.
P

paulobrien said:
Yeah, it's not that - a fully working boot image that's OK in boot mode doesn't give you USB in recovery mode. Very odd.
P
Click to expand...
Click to collapse
hmmm let me have a go at it... right now i am struggling with a pathetic net connection as my main internet line is down...
can u give me the complete mkbootimg repack command?

DooMLoRD said:
hmmm let me have a go at it... right now i am struggling with a pathetic net connection as my main internet line is down...
can u give me the complete mkbootimg repack command?
Click to expand...
Click to collapse
Blank command line, base 0x10000000, pagesize 0x800. I don't use mkbootimg directly as it's all scripted up.
P

paulobrien said:
Blank command line, base 0x10000000, pagesize 0x800. I don't use mkbootimg directly as it's all scripted up.
P
Click to expand...
Click to collapse
thanks i will give it a shot... i work with kernels so i prefer using mkbootimg directly

Thanks Paul .
Ps I really liked your last review on the oneX

Paul,
link for signed recovery (the second one) doesn't works ...

paulobrien said:
Blank command line, base 0x10000000, pagesize 0x800. I don't use mkbootimg directly as it's all scripted up.
P
Click to expand...
Click to collapse
hey paul i finally got it working... but there is a correction..
pagesize has to be specified to 2048
then it boots atleast for me

2048 = 0x800 hex!
P

paulobrien said:
2048 = 0x800 hex!
P
Click to expand...
Click to collapse
ya i know but the mkbootimg binaries i tried didnt accept pagesize in HEX

quick query paul, as of now we need to fastboot flash boot.img to gain root as for some reason we cannot fastboot boot a boot img.
if we can fastboot boot a recovery image can we then install a prerooted rom using the booted recovery without needing to unlock the bootloader

bagofcrap24 said:
quick query paul, as of now we need to fastboot flash boot.img to gain root as for some reason we cannot fastboot boot a boot img.
if we can fastboot boot a recovery image can we then install a prerooted rom using the booted recovery without needing to unlock the bootloader
Click to expand...
Click to collapse
for fastboot boot bootloader needs to be unlocked

DooMLoRD said:
for fastboot boot bootloader needs to be unlocked
Click to expand...
Click to collapse
ah well suppose it was worth asking, didnt know that.
Coming from a nexus one "fastboot oem unlock" was the first thing that i did with it so never new it needed to be unlocked to boot, thought it was only to flash

[UPDATE][Recovery][Untested]DON'T USE - - CWM Recovery from CM Unnofficial Port

DON'T INSTALL THIS (MANUALLY OR FLASHING)!! Stickman got a bootloop after manual write of the recovery
I just builded a test version with the CWM builder, here is the download link: http://jenkins.cyanogenmod.com/job/recovery/35056/
Personally, i would try the inputrecovery.img cause it has the same size as the original recovery
Good luck
Stickman89 said:
I've built CWM from CM sources. Haven't tried it as of yet though.
Flash at your OWN risk. I will not take responsibility for any actions taken by the user in combination with the provided file... By downloading this image your accepting full liability for any issues that should arise as a result of undergoing ANY flashing/modding on YOUR device.
Click to expand...
Click to collapse
All the credits go to Stickman89 | Thank you for the port​
Thank him here: http://forum.xda-developers.com/showthread.php?p=44545580​
HOW TO FLASH
-Connect your device in MTP mode
-Enable USB Debuggin
-Open a terminal and navigate to recovery.img's location
-adb reboot-bootloader
-fastboot flash recovery recovery.img
-fastboot reboot
-Done!
To boot into recovery: adb reboot-recovery​
This recovery haven't been tested, we don't know acurately if it work (or if the bootloader is fully unlocked), flashing this can BRICK your phone

FYI...
Code:
adb reboot recovery
This will allow you to boot into the stock recovery before you've even flashed a thing. The bootloader is the screen with the static Huawei Logo, therefore I'm pretty certain that this is going to have a very little outcome of disaster since we could still get back into bootloader and/or boot into the ROM.
In any case we perform the below to create a backup recovery.img before doing anything like so:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/sdcard/BackupRecovery.img
Before beginning first we need to obtain the dumped "BackupRecovery.img" located on your sdcard as can be seen from the above command.
Copy it onto your machine where your fastboot binaries coincide. Then should you need to restore, you'd need to perform the below:
Code:
adb reboot bootloader
Code:
fastboot flash recovery BackupRecovery.img
Code:
fastboot reboot

If I try just to boot it:
Code:
$ sudo fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.310s]
booting...
FAILED (remote: invalid command)
finished. total time: 0.311s

Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recove
y recovery.img
target reported max download size of 838860800 bytes
sending 'recovery' (6816 KB)...
OKAY [ 0.194s]
writing 'recovery'...
[B]FAILED (remote: flash failure, ErrNo:2)[/B]
finished. total time: 0.200s
Yeah our bootloader sucks, I tried... No harm caused whatsoever.
Best Regards,
s89

I'm going to try flashing it through stock recovery as an update.zip.

Try a flash all, flash origial B107 boot, efi, modem and after that, recovery. When i get my laptop, i'll explain it better
Sent from my HUAWEI P6-U06 using xda app-developers app

Stickman89 said:
I'm going to try flashing it through stock recovery as an update.zip.
Click to expand...
Click to collapse
How's work? . We are nervous and excited. Thank champion.

Stickman and me are searching an alternative method to get the recovery in a secondary partition, keep reading this forum for more info
Sent from my HUAWEI P6-U06 using xda app-developers app

For now I urge all people to not flash the provided recovery.img for the time being whilst we are investigating a safer alternative for implementing CWM for our device. Please be patient in the meantime, thankyou.

Added a version builded with CWM, inputrecovery.img have the same size of the original recovery so it should work, as usual, flash etc etc at our own risk

Haven't seen any updates on this, does it work?

It won't work until huawei release a tool to sign the UPDATE.APP.
I'm sorry
Sent from my HUAWEI P6-U06 using xda app-developers app

S34Qu4K3 said:
It won't work until huawei release a tool to sign the UPDATE.APP.
I'm sorry
Sent from my HUAWEI P6-U06 using xda app-developers app
Click to expand...
Click to collapse
Understandable, thanks for the reply. Makes me want to see this and just get device that's fully unlocked with 3rd party ROM support. =(

S34Qu4K3 said:
flashing this can BRICK your phone
Click to expand...
Click to collapse
so why u putting it here u mento ..

Yeah, if it's not working don't upload it here. When you make something that's working, upload, everyone who is developing here must upload only working 100 % stuff, not unstable stuff that can brick people's phones.

HUAWEIAscendP6 said:
Yeah, if it's not working don't upload it here. When you make something that's working, upload, everyone who is developing here must upload only working 100 % stuff, not unstable stuff that can brick people's phones.
Click to expand...
Click to collapse
You're wrong, we need those devs, who contribute.
With our Phone we have the Problem, that we only can flash unsigned things on B118CN.
So we can only start real developing with this Firmware.
Or at least a other firmware without signing-check.
Users must read before they flash something. Everything with isn't functioning correctly (at this point) shows visible that it can brick our device.
Without testing-builds there will be no working builds!

raolleel said:
You're wrong, we need those devs, who contribute.
With our Phone we have the Problem, that we only can flash unsigned things on B118CN.
So we can only start real developing with this Firmware.
Or at least a other firmware without signing-check.
Users must read before they flash something. Everything with isn't functioning correctly (at this point) shows visible that it can brick our device.
Without testing-builds there will be no working builds!
Click to expand...
Click to collapse
Maybe devs should do tests on their own phones.

HUAWEIAscendP6 said:
Maybe devs should do test on their own phones.
Click to expand...
Click to collapse
I don't know why you are so mean, and you don't understand testing builds.
Even if a build doesn't work, even if there are bugs we should contribute our builds.
The community can help to erase the bugs, everyone can contribute to those projects.
Keep in mind building Roms, Kernels, Mods isn't easy, it needs very much time and concentration.
We don't get any money, we all do this to contribute to the community.
Devs help each other, to erase bugs.
Not everyone can test the builds, maybe they don't have the phone, maybe their phone is in rapair or something.
People like you are those, who should think before they post.
You get our stuff for fee. So say thank you, and don't comment on them, cause there are not bugfree.

HUAWEIAscendP6 said:
Maybe devs should do test on their own phones.
Click to expand...
Click to collapse
We do Test things prior to uploading and sharing, BUT we can't control what the user (the rest of the community) will do with what we share. If you utilize wrong commands to flash a kernel, recovery or whatever then it will not be Developer's fault. That's the reason for the big bold warning at the beginning of each development thread.
And last for not least, The developer is not FORCING you to test something that can brick your phone, it is up to you and it'll be your responsability if the phone bricks.
I've seen your posts, and most of the time you keep complaining about the phone, about a ROM, a recovery etc... If you don't like it sell it and if this or that doesn't work for you don't use it.
Just my 2 cents...

jimbo77 said:
We do Test things prior to uploading and sharing, BUT we can't control what the user (the rest of the community) will do with what we share. If you utilize wrong commands to flash a kernel, recovery or whatever then it will not be Developer's fault. That's the reason for the big bold warning at the beginning of each development thread.
And last for not least, The developer is not FORCING you to test something that can brick your phone, it is up to you and it'll be your responsability if the phone bricks.
I've seen your posts, and most of the time you keep complaining about the phone, about a ROM, a recovery etc... If you don't like it sell it and if this or that doesn't work for you don't use it.
Just my 2 cents...
Click to expand...
Click to collapse
I don't know what posts you saw, but show me one post in which I complain about the phone.

[RECOVERY-TEST] CWM Recovery v6.0.3.7 [Update 29/09/2013] !

Hello to everyone !
ClockWorkMod Recovery v6.0.3.7 - English language !!!​
About :
- based on CyanogenMod 10.1 ( android 4.2.2 ! )
- you can install custom rom, wipe cache , dalvik-cache , data/factory reset, backup & go on ... !
- mount external storage on USB is not work on this release ;
- you can boot in recovery by pressing Volume-up or Volume-down after you'll see the led red blinked !
Change log :
Renamed CWM-based Recovery to ClockworkMod Recovery !
setting properly fonts for 720p device !
Downloads :
CWM Recovery v6.0.3.7 -> update_cwm6037.zip md5 : 3799816bf728a4a1c9a684a087055fdd !
Installation :
copy update.zip on your external sdcard !
go to CWM Recovery 6.0.3.6 or CWM Touch Recovery ;
install zip -> choose zip from external sdcard ;
go to update_cwm6037.zip -> Yes , install "update_cwm6037.zip" !
reboot system now -> choose No or +++ Go Back +++ !!!
Known Bugs :
can not mount /sdcard aka internal storage !
can not restore backup !
This recovery is not Touch recovery !
Get in this CWM Recovery by pressing a few times on Volume-Up or Volume-Down after the led red blinked !!!
This CWM Recovery will not affect your device, because it will not rewrites the recovery partition !!!
If your device not boot into CWM-based Recovery , or you do not see the red led blinked - please send me by PM ( instead pastebin ) this files : /cache/chargemon/chargemon.log & /cache/chargemon/chargemon.log.old ! Thanks !
--- since this is the test release - may contain bugs - I'll hope to solve on the next updates ---​
regards,
Surdu Petru

ClockWorkMod Recovery v6.0.3.6 - English language !!!​
Downloads :
CWM-based Recovery v6.0.3.6 -> update.zip md5 :e86b1c9b78861e3fe17aeac152635c4a
Installation :
you need alraedy installed CWM Touch Recovery !
copy update.zip on your device ;
go to CWM Touch Recovery ;
go to install zip and choose "update.zip" !
reboot & enjoy !!!
regards,
Surdu Petru

Why not touch i had nice touch b4 .. oochh how do i get it back ?

Is backup (and restore) fully working? I want to try some of the newer roms but dont want to give up my b106.
Sent from my HUAWEI P6-U06 using Tapatalk 4

How is it possible that I have two recoveries that i can enter in? first is this one pressing vol buttons then second is recovery touch from app

GalaxySIIII said:
How is it possible that I have two recoveries that i can enter in? first is this one pressing vol buttons then second is recovery touch from app
Click to expand...
Click to collapse
Yes, you can use the both recovery...take a look in OP!
Good luck !

surdu_petru said:
Yes, you can use the both recovery...take a look in OP!
Good luck !
Click to expand...
Click to collapse
touch is way better..
edit : why when i try update zip from internal storage it says no files and i cant go even back in cwm i have to hold long pwr button press? it is same in both your ant that touch ..

ZeroWingUK said:
Is backup (and restore) fully working? I want to try some of the newer roms but dont want to give up my b106.
Sent from my HUAWEI P6-U06 using Tapatalk 4
Click to expand...
Click to collapse
Hi!
I tried to install a custom ROM and than I maked a backup successfully!
I not tested yet restory ... I'm a little busy now . I'll back soon ...
Also I'll make a tut for how you can uninstall this recovery!

surdu_petru said:
Hi!
I tried to install a custom ROM and than I maked a backup successfully!
I not tested yet restory ... I'm a little busy now . I'll back soon ...
Also I'll make a tut for how you can uninstall this recovery!
Click to expand...
Click to collapse
I've updated ramdisk with the touch recovery branch, I will add it here but use at your own risk. Feel free to add it against your thread if you wish surdu_petru.
Since this is using a similar method to our previous I don't see how any harm could come from it.

Stickman89 said:
I've updated ramdisk with the touch recovery branch, I will add it here but use at your own risk. Feel free to add it against your thread if you wish surdu_petru.
Since this is using a similar method to our previous I don't see how any harm could come from it.
Best Regards,
s89
Click to expand...
Click to collapse
Hi!
Thanks, I'll update my OP soon !
Good luck !

Update details !
Sorry for my OP info " - first, this is my first custom recovery made by me !!! " ! wrong
This recovery was my first custom recovery !
- but it is also true, because is the first recovery for this device !

Stickman89 said:
I've updated ramdisk with the touch recovery branch, I will add it here but use at your own risk. Feel free to add it against your thread if you wish surdu_petru.
Since this is using a similar method to our previous I don't see how any harm could come from it.
Click to expand...
Click to collapse
Whoops added wrong files, it's actually non-touch recovery... Correcting to Touch Recovery.

surdu_petru said:
Hi!
Thanks, I'll update my OP soon !
Good luck !
Click to expand...
Click to collapse
Corrected, it can now run Touch Recovery I've just installed and tested. Everything appears to be working. Including Backup.

When rebooting from CWM Touch Recovery Bootloader Version ensure you select no when prompted - No, Yes and Go back. If you select yes it wipes the scripts required for this method to run meaning you will need to redo the CWM installation again. However option "No" retains those required files even on reboot from CWM.

@surdu_petru - We need to collaborate our efforts with xda member kholk you can follow his progress to implement kexec support here for the Honor 2 which has near identical HW to us.
I messaged kholk already and received a swift response via PM stating that work is still in the early stages and when further information and progress has been made he'd like to join efforts with myself in order to yield the same for the P6.
In the meantime your nifty boot script allowing boot-time user intervention in order to access recovery has taken the frustrating part of developing for our device away.
You might have noticed I have added your development with my amended Touch Recovery update to my existing thread here. I have credited you along with a link back here in order to rightfully state ownership of your findings and work. If there are any issues don't hesitate to PM me and I will happily take down any links of concern.

Stickman89 said:
@surdu_petru - We need to collaborate our efforts with xda member kholk you can follow his progress to implement kexec support here for the Honor 2 which has near identical HW to us.
I messaged kholk already and received a swift response via PM stating that work is still in the early stages and when further information and progress has been made he'd like to join efforts with myself in order to yield the same for the P6.
In the meantime your nifty boot script allowing boot-time user intervention in order to access recovery has taken the frustrating part of developing for our device away.
You might have noticed I have added your development with my amended Touch Recovery update to my existing thread here. I have credited you along with a link back here in order to rightfully state ownership of your findings and work. If there are any issues don't hesitate to PM me and I will happily take down any links of concern.
Click to expand...
Click to collapse
Hello!
Thank you very much !
If we can run kexec kernel on our device is equal with : we can run CyanogenMod on our device!
Also he made kexec kernel on Motorola Droid RAZR locked boot loader...!!!
I have this device expressed for development...so I'll do all for running on our device AOSP based ROMs!
Good luck and have a nice day! :highfive:

surdu_petru said:
Yes, you can use the both recovery...take a look in OP!
Good luck !
Click to expand...
Click to collapse
how to uninstall that your non touch now? i dont want it i have touch ..

GalaxySIIII said:
how to uninstall that your non touch now? i dont want it i have touch ..
Click to expand...
Click to collapse
Hi!
Please remove from your device :
- /system/bin/recovery.sh & /system/bin/recovery.tar !
( you can do it by using any explorer with root support ! )
Good luck !

surdu_petru said:
Hi!
Please remove from your device :
- /system/bin/recovery.sh & /system/bin/recovery.tar !
( you can do it by using any explorer with root support ! )
Good luck !
Click to expand...
Click to collapse
ok thanx

surdu_petru said:
Hi!
Please remove from your device :
- /system/bin/recovery.sh & /system/bin/recovery.tar !
( you can do it by using any explorer with root support ! )
Good luck !
Click to expand...
Click to collapse
but it returns the original android recovery or CWM Touch? thx

[guide][how to] cwm 6.0.4.5

Hi!
I've created this thread for share a guide for use the CWM 6.0.4.5 for falsh the CM11 becuase this recovery has an issue that display always a blue screen but it works.
Part 1
-Download cm-11-gio.zip
-Boot to recovery 6.0.4.5, press
PHP:
Vol. down -> Home -> Vol. down -> Vol. down -> Home
You'll enter "Install zip from sideload"
Part 2
-Download adb 1.0.31. Connect your phone to PC via usb. Launch adb and type
Code:
adb devices
-you'll get this
Code:
12346789 sideload
-Every things go good so now type
Code:
adb sideload c:\cm-11-gio.zip
-wait 5-6 min for the rom to be copied to phone abd flashed
Part 3 The end
-After the flashing press on the phone
PHP:
back -> back -> vol. down -> vol.down -> Home -> vol. down -> Home
-You've full wiped the phone
-Press
PHP:
now back -> back -> Home
Reboot to system
Wait for the rom to boot up
Enjoy!
A big thanks to @belyava for this guide

DiavoloPowa said:
Hi!
I've created this thread for share a guide for use the CWM 6.0.4.5 for falsh the CM11 becuase this recovery has an issue that display always a blue screen but it works.
Part 1
-Download cm-11-gio.zip
-Boot to recovery 6.0.4.5, press
PHP:
Vol. down -> Home -> Vol. down -> Vol. down -> Home
You'll enter "Install zip from sideload"
Part 2
-Download adb 1.0.31. Connect your phone to PC via usb. Launch adb and type
Code:
adb devices
-you'll get this
Code:
12346789 sideload
-Every things go good so now type
Code:
adb sideload c:\cm-11-gio.zip
-wait 5-6 min for the rom to be copied to phone abd flashed
Part 3 The end
-After the flashing press on the phone
PHP:
back -> back -> vol. down -> vol.down -> Home -> vol. down -> Home
-You've full wiped the phone
-Press
PHP:
now back -> back -> Home
Reboot to system
Wait for the rom to boot up
Enjoy!
A big thanks to @belyava for this guide
Click to expand...
Click to collapse
Sorry dude, but don't think this guide belongs in this section, although it's really useful for everyone owning vietnamese Gio!

Well, hello there. I'm confused about how to install CM11 on Gio. Reading page by page on CM11 thread and also CWM 6.0.4.5 thread I saw many people have bluescreen on recovery and got stuck when revert back to stock. That happens on Gio with Vietnamese and Chinese build factory. I have my Gio on Indonesia, on the back I can see 'Dibuat Di Korea Selatan' which mean in english is 'Made In South Korea'. So, if I install the CWM 6.0.4.5, I don't have any bluescreen on recovery? I'm affraid to bricking my Gio, mine already hardbrick 2 times and its painful :|

saldymhmd said:
Well, hello there. I'm confused about how to install CM11 on Gio. Reading page by page on CM11 thread and also CWM 6.0.4.5 thread I saw many people have bluescreen on recovery and got stuck when revert back to stock. That happens on Gio with Vietnamese and Chinese build factory. I have my Gio on Indonesia, on the back I can see 'Dibuat Di Korea Selatan' which mean in english is 'Made In South Korea'. So, if I install the CWM 6.0.4.5, I don't have any bluescreen on recovery? I'm affraid to bricking my Gio, mine already hardbrick 2 times and its painful :|
Click to expand...
Click to collapse
My Gio is also made in South Korea and it got bluescreen with CWM 6.0.4.5. I need to blind flash the CM11 rom.
In case anything goes wrong, you can simply odin the recovery (cwm-5.0.2.7-ext4only-odin.tar.md5) to the Gio and recover the previous backup.
http://forum.xda-developers.com/showpost.php?p=49031142&postcount=91

saldymhmd said:
Well, hello there. I'm confused about how to install CM11 on Gio. Reading page by page on CM11 thread and also CWM 6.0.4.5 thread I saw many people have bluescreen on recovery and got stuck when revert back to stock. That happens on Gio with Vietnamese and Chinese build factory. I have my Gio on Indonesia, on the back I can see 'Dibuat Di Korea Selatan' which mean in english is 'Made In South Korea'. So, if I install the CWM 6.0.4.5, I don't have any bluescreen on recovery? I'm affraid to bricking my Gio, mine already hardbrick 2 times and its painful :|
Click to expand...
Click to collapse
bro you are lucky, mine is said "Dibuat di Vietnam" so mine is Vietnamese, yes I got bluescreen and kitkat working

Just use 6.0.3.2...
Sent from my GT-S5660 using xda app-developers app

emyaz said:
Just use 6.0.3.2...
Sent from my GT-S5660 using xda app-developers app
Click to expand...
Click to collapse
CWM 6.0.3.2 can install CM11?

saldymhmd said:
CWM 6.0.3.2 can install CM11?
Click to expand...
Click to collapse
Yes, I installed cm11 with 6.0.3.2 by mmb team and it worked... also I read (not sure if it's true) that cm11 was made to work with 6.0.3.2
Sent from my GT-S5660 using xda app-developers app

emyaz said:
Yes, I installed cm11 with 6.0.3.2 by mmb team and it worked... also I read (not sure if it's true) that cm11 was made to work with 6.0.3.2
Sent from my GT-S5660 using xda app-developers app
Click to expand...
Click to collapse
Can someone else confirm that CWM 6.0.3.2 can flash CM11 ?
Sent from my GT-S5660 using Tapatalk 2

Gyovany96 said:
Can someone else confirm that CWM 6.0.3.2 can flash CM11 ?
Sent from my GT-S5660 using Tapatalk 2
Click to expand...
Click to collapse
I confirm CWM 6.0.3.2 canNOT flash CM11 for my GIO.

Then maybe @emyaz has phone made in korea/china ( or this doesn't matter ? )How can he flash CM11 with CWM 6.0.3.2 ?
Sent from my GT-S5660 using Tapatalk 2

i cant install cm11 with CWM 6.0.3.2 mmb but can with the sideload way,but only with the cwm 6.0.4.5

devrieshh said:
i cant install cm11 neither with CWM 6.0.3.2 mmb but can with the sideload way.
Click to expand...
Click to collapse
I can't use sideload because I am using Win 8.1 and I can't risk a brick because Odin doesn't work too on Win 8.1

Gyovany96 said:
I can't use sideload because I am using Win 8.1 and I can't risk a brick because Odin doesn't work too on Win 8.1
Click to expand...
Click to collapse
,you can install cwm 6.0.4.5 and use adb only problem is you will be stucked with cm11 unless you are able to flash with adb other cwm(is possible see general forum somewere)
.

@Gyovany96
I don't think that I have a Korean/Chinese model. I live in Germany so I think it's a European model. Where can I look to see if it's Korean/Chinese or not?
And it's maybe important to know that I didn't flashed the cwm 6.0.3.2 with the old recovery. I did it with the terminal emulator and the command "flash_image".

emyaz said:
@Gyovany96
I don't think that I have a Korean/Chinese model. I live in Germany so I think it's a European model. Where can I look to see if it's Korean/Chinese or not?
And it's maybe important to know that I didn't flashed the cwm 6.0.3.2 with the old recovery. I did it with the terminal emulator and the command "flash_image".
Click to expand...
Click to collapse
Pull the battery out and read "Made in Vietnam/Korea/China"

emyaz said:
@Gyovany96
I don't think that I have a Korean/Chinese model. I live in Germany so I think it's a European model. Where can I look to see if it's Korean/Chinese or not?
And it's maybe important to know that I didn't flashed the cwm 6.0.3.2 with the old recovery. I did it with the terminal emulator and the command "flash_image".
Click to expand...
Click to collapse
Please advise the command you use to flash the Rom. Also any command can flash recovery via terminal emulator?
Thanks!

Open terminal emulator.
'su'
'flash_image recovery /path/to/recovery/ recovery.img'
That's it... it worked on my phone with cm7...
(You can get the 'recovery.img' file by extracting the zip file)

Gyovany96 said:
I can't use sideload because I am using Win 8.1 and I can't risk a brick because Odin doesn't work too on Win 8.1
Click to expand...
Click to collapse
Try Heimdall
http://forum.xda-developers.com/showthread.php?t=755265
http://glassechidna.com.au/heimdall/

doppelhelix said:
Try Heimdall
http://forum.xda-developers.com/showthread.php?t=755265
http://glassechidna.com.au/heimdall/
Click to expand...
Click to collapse
does heimdall already support the gio,i dont think so

TWRP RECOVERY in to FOTA PARTITION GUIDE (XPERIA S)

Flash TWRP to FOTA Partition(SONY XPERIA S).(Terminal Command Method)I will not responsible if you do something wrong to yor device
You can flash TWRP into fota partition if your kernel supports to flash it.(Ask the developer if support is available or not,To know more about Fota Partition Read here.).if yes then follow procedure.
1. You must have to root your ROM first.
2. Download TWRP.img (is the recovery file) from TWRP website.Place the downloaded twrp.img in sdcard. (Don’t place it under any folder.just copy to sdcard.if the downloaded file name is something else then rename it to twrp.img).
3. Now goto playstore and install terminal emulator app to your phone.
4. Now open terminal emulator app and type
su (and press enter key.it will ask for root permission.GRANT it) then type
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p11
(and press enter keyr.be careful while you writing the above commands.)
Finished.Now you have successfully flashed twrp recovery into fotapartition.Reboot your phone and when you see pink led just tap Volume UP key to enter to recovery.
Rom Flash Procedure
METHOD 2:
First extract boot.img and recovery.img from rom.zip and copy both to SD card root folder
1. Flash twrp recovery image like you flash kernel/boot.img(by flash tool or by fastboot method).
2. Enter to recovery.
Then follow the image by the numbers written in the image.Swipe to flash.
Then do the same for boot.img but choose boot. Img from SD card and boot(partition) in image 4. Swipe to flash and done.

Sir, Could you please help me.
I have CWM recovery installed on Xperia SL and is running Layers ROM Cm11 based.
But I am thinking of switching to a new rom as the earlier one was very laggy. ([ROM][XS][5.1.1][LMY48P] OneOfaKind 22/09/2015 | UberTC 4.9 | Layers | Aroma Addon)
Could you tell me what shall I do with regards to:
1. Making the build.script change to make it compatible with Xperia SL
2. Do I need a TWRP recovery ? How will it go alongwith the CWM recovery which I already have installed and running pretty well ?
Thanks !

C0D3FR34K said:
Sir, Could you please help me.
I have CWM recovery installed on Xperia SL and is running Layers ROM Cm11 based.
But I am thinking of switching to a new rom as the earlier one was very laggy. ([ROM][XS][5.1.1][LMY48P] OneOfaKind 22/09/2015 | UberTC 4.9 | Layers | Aroma Addon)
Could you tell me what shall I do with regards to:
1. Making the build.script change to make it compatible with Xperia SL
2. Do I need a TWRP recovery ? How will it go alongwith the CWM recovery which I already have installed and running pretty well ?
Thanks !
Click to expand...
Click to collapse
First thing I am not sir..I am also like you...I have just shares my experience to which will help new comers in simple words.
As of your point 1 you have to make change to support on SL...
And about recovery.try to flash with cwm first if not succeed then flash twrp 2.8.4.1 or above and flash the rom.

nageswarswain said:
First thing I am not sir..I am also like you...I have just shares my experience to which will help new comers in simple words.
As of your point 1 you have to make change to support on SL...
And about recovery.try to flash with cwm first if not succeed then flash twrp 2.8.4.1 or above and flash the rom.
Click to expand...
Click to collapse
Problem is I am not able to find support for Xperia SL
The difference between Xperia S and SL is just 1.5GHz and 1.7GHz CPU respectively.. but support for the latter is sh!t

C0D3FR34K said:
Problem is I am not able to find support for Xperia SL
The difference between Xperia S and SL is just 1.5GHz and 1.7GHz CPU respectively.. but support for the latter is sh!t
Click to expand...
Click to collapse
As said by You, the difference is just in frequency, and none in hardware. So what ever applies to XS will apply to XSL.

Mirhawk said:
As said by You, the difference is just in frequency, and none in hardware. So what ever applies to XS will apply to XSL.
Click to expand...
Click to collapse
Thanks ! I have installed TWRP latest build using fastboot !

nageswarswain said:
First thing I am not sir..I am also like you...I have just shares my experience to which will help new comers in simple words.
As of your point 1 you have to make change to support on SL...
And about recovery.try to flash with cwm first if not succeed then flash twrp 2.8.4.1 or above and flash the rom.
Click to expand...
Click to collapse
This is tantamount to spam but plz plz help me !!!
I was resizing the my 2GB partition but I am stuck now in the middle !!
I got stuck in step 10
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
/sdcard #
Click to expand...
Click to collapse
Followed the instructions on this thread :
http://forum.xda-developers.com/xperia-s/s-development/tutorial-increase-data-partition-t2821058

C0D3FR34K said:
This is tantamount to spam but plz plz help me !!!
I was resizing the my 2GB partition but I am stuck now in the middle !!
I got stuck in step 10
Followed the instructions on this thread :
http://forum.xda-developers.com/xperia-s/s-development/tutorial-increase-data-partition-t2821058
Click to expand...
Click to collapse
I saw now that you have solved your problem. And this time also @mirhl is present there to help..good guy mirhl.

Hello, i am using DooMKernel which comes with a preinstalled TWRP v2.5.0.0 now i am trying to update it to the latest version via Terminal or Fastboot but it doesn't work version stays the same. Does anyone know what could be the problem?

Torroan said:
Hello, i am using DooMKernel which comes with a preinstalled TWRP v2.5.0.0 now i am trying to update it to the latest version via Terminal or Fastboot but it doesn't work version stays the same. Does anyone know what could be the problem?
Click to expand...
Click to collapse
Here is a link which will give you mickybart's recovery and kernel of nAOSO b26.but before flashing this first copy the rom to your phone because u can't boot the device after flashing it.so flash this and reboot to recovery and flash the rom you want.
Link.
https://mega.nz/#!SZ9DXZgZ!tzugmlsOMum3cZYXyTh69lDDlhGfGjV-Fw2VKvaYdK8

Thanks, in case i want to keep my current stock ROM there is no problem whatsoever is there? I mean i can just install the Kernel and i'll be good to go?

Torroan said:
Thanks, in case i want to keep my current stock ROM there is no problem whatsoever is there? I mean i can just install the Kernel and i'll be good to go?
Click to expand...
Click to collapse
Take backup of the current rom before flashing the other file.then do as I said

TWRP... thanks!

Thanks
Thanks for the guide really appreciate !!

BTW - only mine recovery dont show temperature? my soft is oneofakind and newest twrp recovery in FOTA via dd command.

I installed twrp 2.8.7 using this and my phone got stuck in a boot loop
I am on uCyan b04.

guruAhtasham said:
I installed twrp 2.8.7 using this and my phone got stuck in a boot loop
I am on uCyan b04.
Click to expand...
Click to collapse
Flash ucyan b04 kernel only on fastboot and try to reboot...

nageswarswain said:
Flash ucyan b04 kernel only on fastboot and try to reboot...
Click to expand...
Click to collapse
Thanks for the reply but it didn't work
have to do a clean flash again to make it boot.