Related
Got this post from the Cyanogenmod forum.
Credit goes to roalex, wjsturgis3.
I have the 3.22.20.17 radio with 1.33.2010 SPL. I downloaded this ROM: http://forum.xda-developers.com/showpost.php?p=10797510&postcount=54
Here is the updater-script I used(renamed as .txt so I could upload it). I edited it with notepad++. I used 7-zip to replace the file in the update.zip and used "Update.zip 2.0 Modifier/Creator" http://forum.xda-developers.com/showthread.php?t=717437 to sign it.
Here is the edited part of the update-script file:
assert(getprop("ro.product.device") == "trout" || getprop("ro.build.product") == "trout" || getprop("ro.product.board") == "trout" ||
getprop("ro.product.device") == "sapphire" || getprop("ro.build.product") == "sapphire" || getprop("ro.product.board") == "sapphire");
This is for a Magic 32A with the old 3.22 radio only NOT the new 6.35 radio.
I also have HBOOT-1.33.2010
Here is the already "modified" ROM:
http://rapidshare.com/files/444692762/update-cm-7.0.0-DS-32B_2708.zip
MD5 1AE2FA880C3764425F2926D7E8864AEB
The kernel http://droidbasement.com/db-blog/
I hope this is the correct one:
http://droidbasement.com/g1/kernels/ram/2635/20/boot-cm_2635.10_ds_32a-oc-uv-xtra-ram-fp-011611.zip
Method:
1. Nandroid
2. Superwipe
3. reboot to recovery
4. flash ROM
5. flash kernel
6. boot system
Click to expand...
Click to collapse
No guarantee that this will work or even brick your device.
Just installed it without any problems.
Seems to lag heavily, could be related with current ongoing sync (market...).
As far as I see:
- GPS working
- Market working (use it to install missing gapps)
set cpu to 614
-> Linpack (1.2.1): 3.4
There is a new version out
Please have look here:
http://forum.cyanogenmod.com/topic/...dreamsapphire/page__view__findpost__p__133308
I have not had the time to post more info. Please see for yourself - just wanted to inform you...
good work..... thx for sharing....
working
Everything seems to run nicely so far (sensors, gps, cam, vid, market, ...). Just graphics seems to be laggy... maybe someone has a solution for this?
I even could keep my settings and apps2sd, was coming from
[Rom][32b] - [32a][3.22] CM6 - FroyoRedux Mod v2.0 (10/25/2010)
I did this:
nandroid backup
wipe cache partition
wipe dalvik cache
wipe battery stats
flash rom
flash kernel
reboot (5 mins)
restore adw settings
finally GB & cyanogenmod
gonna wait for a beta... good work to whoever made it though
Market doesn't work... I don't why? hmm
All apps of google don't work... I can't log-in
Bolerro said:
Market doesn't work... I don't why? hmm
All apps of google don't work... I can't log-in
Click to expand...
Click to collapse
have you superwiped?
market is working for me without any problem...
shadow_empire1 said:
have you superwiped?
market is working for me without any problem...
Click to expand...
Click to collapse
What you mean superwiped? Did I miss something?
Ah, I found... SuperWipe, right..
wouldn't gingerbread be better with new radio for 32a?
tass0s said:
wouldn't gingerbread be better with new radio for 32a?
Click to expand...
Click to collapse
GO look at another ROM, giant_rider for example http://forum.xda-developers.com/showthread.php?t=921273
Currently camera and gmail don't work.
32B. Now. kthxbai
thegangsta said:
Just graphics seems to be laggy... maybe someone has a solution for this?
Click to expand...
Click to collapse
What exactly do you mean with that? Do you mean window animations and transitions, or also scrolling through lists etc.? Which launcher did you try? Please share some more details....
Thx
Graphics Problem
ATeam-MrT said:
What exactly do you mean with that? Do you mean window animations and transitions, or also scrolling through lists etc.? Which launcher did you try? Please share some more details....
Thx
Click to expand...
Click to collapse
Sorry for being so unspecific.
I am using ADW Launcher 1.3.6 System. But I don't think only the launcher is the problem, it may be more of a system problem (maybe kernel related?). In neocore i get 8.5fps and the graphics are not fully shown (I don't see the robot, just see dust and explosions), and all the games that use graphics have a really slow framerate (but they run normally, no sound glitches or anything like that, so the system is responsive). Also every graphics effect in the launcher is "slow", but I turned the animations off and now the system is usable and stable.
I appreciate your help.
Cheers
I agree that the overall system performance is really bad :-/
I switched back to latest nightly CM6.1 (cm_dream_sapphire_full-307-gingerbreadmodid242), where performance is good and everything else is working...
(waiting for daily nightly cm7 for 32A...)
I'm currently using Ezterry's Gingerbread with the same pershot kernel, and I have 47fps in neocore (cpu max is 576) so I don't think it is related to the kernel. I guess must be some issue with open gl in CM7... Hopefully Wes Garner is already looking at Ezterry's git repo to find the required changes
shadow_empire1 said:
I agree that the overall system performance is really bad :-/
I switched back to latest nightly CM6.1 (cm_dream_sapphire_full-307-gingerbreadmodid242), where performance is good and everything else is working...
(waiting for daily nightly cm7 for 32A...)
Click to expand...
Click to collapse
Same here....
ATeam-MrT said:
I'm currently using Ezterry's Gingerbread with the same pershot kernel, and I have 47fps in neocore (cpu max is 576) so I don't think it is related to the kernel. I guess must be some issue with open gl in CM7... Hopefully Wes Garner is already looking at Ezterry's git repo to find the required changes
Click to expand...
Click to collapse
Can you direct me to where I can get your setup?? Thanks.
Everything ok in this ROM: No DiS, no FC, battery about 48h without charging... Faster GPS and WiFi... But too much lags :/ It is fine, ok, but telephone thinking too slow...
After 2.5 days of testing I can say that is the best 2.3 for Sapphire
I'm waiting for the next version! Thx!
any news about beta version or full version?
marc003 said:
any news about beta version or full version?
Click to expand...
Click to collapse
+1
// HtcMagic_CM6.1.0_TapatalkPRO.
marc003 said:
any news about beta version or full version?
Click to expand...
Click to collapse
+1 :d
Hey everyone. This is a CyanogenMod 9 build for the U8150.
Working:
WiFi
Touchscreen - for Melfas and Synaptics
Smooth UI
Graphics
Booting
Bluetooth
RIL i.e. Phone and mobile network reception
Mobile data - 2G and 3G
Keyboard in landscape
USB Tethering
WiFi Tethering - with external apps
Camera
Audio
Not working:
Live Wallpapers - will pretty much never happen since we don't have a GPU
Hardware Video Decoding - without Qualcomm's help will pretty much never happen
Video recording - not much work
If you like my work and want to give a small amount of money for me please click the "Donate to me" button under my username. Otherwise I would be grateful if you can click the "Thanks" button on the bottom right of this post. Thanks
Bug reports - https://github.com/tilal6991/android_device_huawei_u8150/issues
Device repository - https://github.com/ColdFusionX/android_device_huawei_u8150
Kernel source - https://github.com/CommonFusionX/huawei-kernel-msm7x25
FLASH THIS RECOVERY BEORE FLASHING THE ROM - Thanks to alanorth http://www.mediafire.com/?bpjbc93xb7izits
FLASH ORDER:
1. ROM
2. Wipe Data
3. Boot into ROM
4. Reboot into recovery
5. GAPPS
Download:
23/05/2012 Nightly - download
GAPPS - market etc - download
Changelog:
03/12/2011:
Initial release
24/12/2011:
Fix Audio
Fix Mobile data
Make graphics smoother
Sync with CM repos
Notification power widgets
28/12/2012:
Fixed loads of stuff
29/01/2012 - WiFi Fix:
Fixed WiFi
13/02/2012
Properly fixed WiFi
Fixed Phone crash
Fixed keyboard
Multiple other graphical errors
23/05/2012
Pretty much fixed everything apart from what's on the broken list
The biggest update for a ROM you'll pretty much ever see.
Completely update to CM9 repos - includes Theming
coool, looking forward to it
Nice... hope I can enjoy it soon..^_^
Sent from my U8150 using XDA App
cool
Cool eagerly waiting
Sent from my U8150 using XDA App
Excellent Tital!Keep up the Nice Work
every thing else don't work....cool looks like its built for my phone . i just droped my ideos and the digitizer is cracked .........cryingggggggggggggggggggg
and its not available in my country...
but suprisingly the top portion of the touch screen is still working and the hardware buttons are still working....so.....in short i need a rom that can be totally controlled by the d-pad / harware buttons................
can you help ..plzzzzzz
lol i suggest you get yourself a new phone
kriaz said:
every thing else don't work....cool looks like its built for my phone . i just droped my ideos and the digitizer is cracked .........cryingggggggggggggggggggg
and its not available in my country...
but suprisingly the top portion of the touch screen is still working and the hardware buttons are still working....so.....in short i need a rom that can be totally controlled by the d-pad / harware buttons................
can you help ..plzzzzzz
Click to expand...
Click to collapse
CyanogenMod 9
Good Job Tilal..nice work..
Can't wait to see
great waiting from mexico
wonderful
i want it
good luck
if you need i can be a beta tester
RIL is now working and graphics have been improved.
However mobile data is still not working but will be fixed.
tilal6991 said:
RIL is now working and graphics have been improved.
However mobile data is still not working but will be fixed.
Click to expand...
Click to collapse
Good
Still can't fix ril yet in my rom :'(
Great news! Keep up the good work!
what is RIL?
Giogts said:
what is RIL?
Click to expand...
Click to collapse
Radio Interface Layer. It's basically the part that is responsible for phones calls, text messages, mobile internet etc.
I can't flash your last update.
This is the error message:
Installing update...
assert failed: getprop("ro.product.device") == "u8150" || getprop("ro.build.product") == =u8150"
E:Error in /sdcard/cm_u8150-ota-eng-lalit.zip
(Status 7)
Installation aborted
What's wrong?
sette7nani said:
I can't flash your last update.
This is the error message:
Installing update...
assert failed: getprop("ro.product.device") == "u8150" || getprop("ro.build.product") == =u8150"
E:Error in /sdcard/cm_u8150-ota-eng-lalit.zip
(Status 7)
Installation aborted
What's wrong?
Click to expand...
Click to collapse
I think ... You are not using CWM v5.0.2.7?
Ryunosuke_Aozora said:
I think ... You are not using CWM v5.0.2.7?
Click to expand...
Click to collapse
Latest CWM for huawei ideos 8150 is 3.0.2.4
edit : downloaded again zip file....same error
sette7nani said:
Latest CWM for huawei ideos 8150 is 3.0.2.4
Click to expand...
Click to collapse
aorth has been build 5.0.2.7!
http://forum.xda-developers.com/showpost.php?p=19619557&postcount=2987
What is this?
Well, when I stopped working on the QSD8K (Bravo, BravoC and Nexus One) CM(9/10) Ports, I did make a promise that I would make some support for the CDMA (BravoC) users that would enable them to use some of the other existing ICS/Jellybean ports for the Desire. This seams to be needed as developers in this section has abandoned any CDMA support a long time ago. So here it is. A CDMA Support Package which should be able to be flashed on top of any HTC Desire GSM ICS/Jellybean ROM that will enable support for HTC Desire CDMA.
What does it contain?
CDMA ICS/Jellybean Kernel forked from Evervolv
Key Layout files
Libraries for lights, gps, sensors and RIL
Firmware
Permissions needed for CDMA to replace GSM
CDMA APN Configurations
How to use
Download an GSM ICS/Jellybean ROM for HTC Desire
Extract the ZIP and remove the line
Code:
assert(getprop("ro.product.device") == "bravo" || getprop("ro.build.product") == "bravo");
from META-INF/com/google/android/updater-script if it exists, or simply change 'bravo' to 'bravoc' (Otherwise install will fail as you do not have a Bravo but a BravoC)
Repack and flash the ROM
Now flash either ICS or Jellybean Support Package
Well, reboot an hope that it works
Download
Version JB-1.2 from Mediafire.com or Sourceforge.net
Version ICS-1.0 from Mediafire.com or Sourceforge.net
Additional Downloads
Repacked ROM and Support Package by @inb22
Note
I do not have this device, so I cannot promise that it will work. I did however release a supporting ROM for this device for about a year and this package is build based on that. If it does not work, then write in this thread and we can make it work together. Just remember that a logcat helps a lot.
Sep 24, 2013
With some help from @grad_devil and he's CDMA device, we got the package to boot. A big thanks for he's time helping me test the changes needed.
Sep 24, 2013
Added Support Package for ICS based ROM's
Changelog
JB-1.2
-----
* Some small changes to the defconfig (Kernel config)
* Changed some vendor files
* Fixed some bugs in the installers build.prop update script
Click to expand...
Click to collapse
You absolute beast, you. My dev phone can finally HOLO on latest
Any possibility of a USB host driver on this, though?
-----------------------------
Reporting in: ParanoidAndroid/PIE is currently at a blank screen (surprisingly not HTC). May be the boot logo is messed up. Will give it some time and report back. Rebooting produces no change... will try an AOSP rom. Factory reset + dalvik cleared, will retry.
Same scenario for this ROM: http://forum.xda-developers.com/showthread.php?t=2070704
Odp: [KERNEL/MOD] BravoC Jellybean Support Package
OP was asking for logcat's if something goes wrong, just saying.
Sent from my HTC Desire using xda premium
"short" logcat: http://pastebin.com/AMQSLaG8
"long" logcat: http://pastebin.com/vf9byPpF
Looks like a bootloop, but hell, what do I know?
dwegiel said:
"short" logcat: http://pastebin.com/AMQSLaG8
"long" logcat: http://pastebin.com/vf9byPpF
Looks like a bootloop, but hell, what do I know?
Click to expand...
Click to collapse
I am already working on this issue, but thanks
Hopefully I will have something new uploaded in a short while
New update is out, this has been tested by @grad_devil hwo did manage to get it to boot Evervolv JellyBean
We still need someone to test the Telephony Service, but other than that it seams to be working just fine.
Edit:
I have also added an ICS Support Package that should work with most ICS Based ROM's for the GSM Desire. Note however that this has not been tested yet, but it has been build based on the Jellybean testing of the JB-1.2 version
assert(getprop("ro.product.device") == "bravo" || getprop("ro.build.product") == "bra
Hello! at me it doesn't turn out to begin in any way installation after removal of a line of assert (getprop ("ro.product.device") == "bravo" || getprop ("ro.build.product") == "bravo");
thus installation doesn't happen on any disks! ! !
there is also any solution of a problem?
forgive my English.
*klim* said:
Hello! at me it doesn't turn out to begin in any way installation after removal of a line of assert (getprop ("ro.product.device") == "bravo" || getprop ("ro.build.product") == "bravo");
thus installation doesn't happen on any disks! ! !
there is also any solution of a problem?
forgive my English.
Click to expand...
Click to collapse
Solution is RIGHT IN THE POST. Edit updater-script to say bravoc instead of bravo or delete the line...
---------- Post added at 02:28 AM ---------- Previous post was at 02:26 AM ----------
Thanks for the update will test on CM VJ 10.1 and report back.
BOOTSCREEN!!!
"Welcome
Just a sec..."
Wifi functional, phone not, but not needed for me
Will check the scenario for ParanoidAndroid now. Same case, all functional except for phone.
Also, sign me up for beta testing if you can.
dwegiel said:
Solution is RIGHT IN THE POST. Edit updater-script to say bravoc instead of bravo or delete the line...
---------- Post added at 02:28 AM ---------- Previous post was at 02:26 AM ----------
Thanks for the update will test on CM VJ 10.1 and report back.
BOOTSCREEN!!!
"Welcome
Just a sec..."
Wifi functional, phone not, but not needed for me
Will check the scenario for ParanoidAndroid now. Same case, all functional except for phone.
Also, sign me up for beta testing if you can.
Click to expand...
Click to collapse
Are we talking about 3G connection or the phone in general? What about sound?
Sent from my GT-I9300 using xda premium
dk_zero-cool said:
Are we talking about 3G connection or the phone in general? What about sound?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Sound is functional, and the radio is completely crashed, CM VJ believes it has no sim card, PA doesn't know what is going on. So no radio at all, acts like airplane mode.
dwegiel said:
Sound is functional, and the radio is completely crashed, CM VJ believes it has no sim card, PA doesn't know what is going on. So no radio at all, acts like airplane mode.
Click to expand...
Click to collapse
Okay. Well at least we are close. Could you try the ICS version on an ICS Rom? The diffs between those will help me narrow down the possible issues.
Sent from my GT-I9300 using xda premium
Oh 6 disks already I tried, on one installation after change of a line of bravo on bravoC didn't go... in what problem?
dk_zero-cool said:
Okay. Well at least we are close. Could you try the ICS version on an ICS Rom? The diffs between those will help me narrow down the possible issues.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Sure, can do. Will report back on the 4.0.4 ROM with fixed camera
Good job! Does it support JB 4.2.2?
Sent from my Nexus 7 using xda app-developers app
gnokiar said:
Good job! Does it support JB 4.2.2?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
4.0.x, 4.1.x and 4.2.x
Sent from my GT-I9300 using xda premium
dk_zero-cool said:
4.0.x, 4.1.x and 4.2.x
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Tks
Sent from my Nexus 7 using xda app-developers app
dk_zero-cool said:
4.0.x, 4.1.x and 4.2.x
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Do you know which GSM JB 4.1.x rom can be flashed? I have tried VJ and Evervolv, but can not booted.
Sent from my Nexus 7 using xda app-developers app
Hi, DK!
Thank you for your concern for us, CDMA Desire users.
I installed several GSM Roms with your packages. Not one of them is not working fully.
1. VJ Jelly Bean 4.2.2 v5.2 -
Mobile Network - not working
Calls - working, when mobile network switch is off. Notification icon is empty
3G/Data - not working
Wifi - working
WifI Tether - not tested
Bluetooth - not working and the switch is not active
GPS - working
Sound - working
USB - working
Camera - working, but requires restart application
Notification - artifacts remain on the screen after dropping
2. Evervolv Turba 3.3.0p1 Jelly Bean 4.2.2
Mobile Network - not working
Calls - working, when mobile network switch is off. Notification icon is empty
3G/Data - not working
Wifi - working
WifI Tether - not tested
Bluetooth - not working and the switch is not active
GPS - working
Sound - working
USB - working
Camera - working,
Notification - working
3. Marius.a ICS 4.0.4 with good video recording v3.5
Mobile Network - not working
Calls - working, when mobile network switch is off. Notification icon is empty
3G/Data - not working and the switch is not active
Wifi - not working and the switch is not active
WifI Tether - not tested
Bluetooth - working
GPS - working
Sound - working
USB - working
Camera - working,
I don't know how you'd go about it but the issue of radio is seriously it. After that, it's a perfect support package!! Also, i just noticed your thread says september when it should say february or march
dk, what help/logs do you need from me to help you out in getting the radio working? Thanks
Anyone running this ROM?
http://www.drdevs.com/devs/teamliquid/Nightly/HTC One M8 (2014) Verizon/
Downloading, I will be if it works. If it doesn't there's always nandroid.
Edit: The answer is no, the latest version posted there doesn't flash at all, just fails.
Dang I loved liquid on my t-bolt... still run it on my kids phones liquidsmooth 3.2 on both
toby1064 said:
Downloading, I will be if it works. If it doesn't there's always nandroid.
Edit: The answer is no, the latest version posted there doesn't flash at all, just fails.
Click to expand...
Click to collapse
Did you try with both TWRP and CWR?
andybones said:
Did you try with both TWRP and CWR?
Click to expand...
Click to collapse
It's only CWM flashable, I tried with twrp and it failed
Sent from my HTC6525LVW using Tapatalk
That build 16 april mic audio doesn't work . they have newer builds but no public link.
Sent from my HTC One VZW using Tapatalk 4
New Nightly out for Liquidsmooth build date 20140505 its a Unified build, it still don't flash with TWRP it said "Error Executing Updater Binary". Can anyone tell me what to edit in order to get it to flash?
http://www.drdevs.com/devs/teamliquid/Nightly/HTC One M8 (2014) Unified/
krazie1 said:
New Nightly out for Liquidsmooth build date 20140505 its a Unified build, it still don't flash with TWRP it said Error Executing Updater Binary. Can anyone tell me what to edit in order to get it to flash?
http://www.drdevs.com/devs/teamliquid/Nightly/HTC One M8 (2014) Unified/
Click to expand...
Click to collapse
sure pal.. im @ work so the file location you will have to find.
your looking for a file called updater-script. should be in meta-beta > google > updater-script. open it and remove the asserts at the very top or simply add in our m8 verizon
kwkw480 said:
sure pal.. im @ work so the file location you will have to find.
your looking for a file called updater-script. should be in meta-beta > google > updater-script. open it and remove the asserts at the very top or simply add in our m8 verizon
Click to expand...
Click to collapse
Ok so just remove all this right?
assert(getprop("ro.product.device") == "m8" || getprop("ro.build.product") == "m8" ||
getprop("ro.product.device") == "m8wl" || getprop("ro.build.product") == "m8wl" ||
getprop("ro.product.device") == "m8wlv" || getprop("ro.build.product") == "m8wlv" ||
getprop("ro.product.device") == "m8vzw" || getprop("ro.build.product") == "m8vzw" ||
getprop("ro.product.device") == "m8whl" || getprop("ro.build.product") == "m8whl" ||
getprop("ro.product.device") == "m8spr" || getprop("ro.build.product") == "m8spr");
then try to reflash.
krazie1 said:
New Nightly out for Liquidsmooth build date 20140505 its a Unified build, it still don't flash with TWRP it said "Error Executing Updater Binary". Can anyone tell me what to edit in order to get it to flash?
http://www.drdevs.com/devs/teamliquid/Nightly/HTC One M8 (2014) Unified/
Click to expand...
Click to collapse
Thank you for the link. Why not switch recoveries if TWRP gives issues? I've NEVER had an issue with CWM
Sent from my HTC6525LVW using XDA Free mobile app
krazie1 said:
Ok so just remove all this right?
assert(getprop("ro.product.device") == "m8" || getprop("ro.build.product") == "m8" ||
getprop("ro.product.device") == "m8wl" || getprop("ro.build.product") == "m8wl" ||
getprop("ro.product.device") == "m8wlv" || getprop("ro.build.product") == "m8wlv" ||
getprop("ro.product.device") == "m8vzw" || getprop("ro.build.product") == "m8vzw" ||
getprop("ro.product.device") == "m8whl" || getprop("ro.build.product") == "m8whl" ||
getprop("ro.product.device") == "m8spr" || getprop("ro.build.product") == "m8spr");
then try to reflash.
Click to expand...
Click to collapse
Yes thats it
and its not a twrp issue is just the asserts are missing our verison
kwkw480 said:
Yes thats it
and its not a twrp issue is just the asserts are missing our verison
Click to expand...
Click to collapse
It was a No Go, the error is coming from the Updater Binary
kwkw480 said:
Yes thats it
and its not a twrp issue is just the asserts are missing our verison
Click to expand...
Click to collapse
It works perfect with CWM without messing with the asserts.
Sent from my One M8 using xda app-developers app
richii0207 said:
It works perfect with CWM without messing with the asserts.
Sent from my One M8 using xda app-developers app
Click to expand...
Click to collapse
Thats good to hear, CM is going to be adding TWRP support in their next build so all the other AOSP roms will have the fix as well. I would use CWM but I don't like that the backups are too huge and you can't get to them (to save to computer) without using root explorer and transferring to Ext SD Card.
Has anyone flashed the latest liquidsmooth, I have but only am only Roaming. I get no 3G or 4G....
Yup. Couldn't get Wi-Fi to turn on... On a clean install, twice. Didn't really try anything else.. just restored my Bonestock back up.
krazie1 said:
It was a No Go, the error is coming from the Updater Binary
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=QW1znjDLe-k
there you go bud .. now you owe me a report back on whats broken on this rom im on CM11 and if it not running as smooth or if some more things are broken i dont want to switch yet
oh nevermind i see you got it to flash but that vid should help you out for the future .. good luck man
Has anyone tried the latest nightly? http://www.drdevs.com/devs/teamliquid/Nightly/HTC One M8 (2014) Unified/
millerd79 said:
Has anyone tried the latest nightly? http://www.drdevs.com/devs/teamliquid/Nightly/HTC One M8 (2014) Unified/
Click to expand...
Click to collapse
I have and it's now flashable via TWRP with data working but it has bugs still:
+no in call audio
+ffc is broken
+headphone jack broken
+low res mms
Sent from my HTC6525LVW using Tapatalk
Thanks you....you saved me from wasting an hour of my life.....Now back to GTA5
krazie1 said:
I have and it's now flashable via TWRP with data working but it has bugs still:
+no in call audio
+ffc is broken
+headphone jack broken
+low res mms
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Hello Everyone,
First of all, I don't want to earn credits to making this guide on how to install CM 11 on Xperia E3 (d2203) I'm just translating the tutorial made by #moiremoi
Warning: This modification of your phone state will remove the warranty. Moiremoi, FXPTeam, xda developpers staff or even myself will decline any responsability on possibles issues you could get by using this ROM, flashing or any method used from this tutorial.
REVIEW:
This ROM is an unofficial CM11 ROM created from the FXP Team. It is stable and final (this mean that there would not be any update anymore)
Its is 4.4.4 based
SCREENSHOTS:
HOW TO INSTALL:
Requirements:
Sony Xperia E3 d2203 (i don't tested other versions so idk if it works or not)
Unlocked bootloader
CWM or Teamwin Recovery
Rooted android 4.4.4 firmware 18.5.C.0.19
Better do a recovery of your phone state before doing any modification
Things to download:
CM 11 ROM : http://uploaded.net/f/zx9n6h/
GAPPS : https://www.androidfilehost.com/?fid=95916177934553399 (please take these for CM11 or Android 4.4.4)
Updater-Script: http://www.mediafire.com/file/400vsdcaasc9619/updater-script (modified "Updater-script" to avoid ''Leo'' error)
How to do:
- First of all, open the CM11 archive without unzipin it and navigate to "META-INF/com/google/android" and replace the existing "updater-script" file to the one required (link to download required file just over there)
- Copy and paste the CM11 + gapps zip to your SD card (just place it to sd, do not make it in any folder to retrieve it faster)
- Turn you phone on (or reboot it) and press many times the Vol + and Vol - at the booting sony screen to go on recovery mode
- Navigate into the menu and choose Wipe cache/data (if you forget to do a wipe, you just can forget to install the ROM)
- Then;
install zip from sdcard >> choose zip from sdcard >> (select ROM .zip) >> Yes
install zip from sdcard >> choose zip from sdcard >> (select GAPPS .zip ) >> Yes
Now, you just have to wait untill finish and choose reboot now
BUGLIST:
No NFC
Not really listed as bug but I find the audio power a bit lowered compared to Stock
Time of the phone battery charge (from 0 to 100%) a bit longer (it can depend on which usb you use too, maybe not a bug)
Camera, audio and every other sony related things are 100% WORKING
I will not help you if you occurs any type of errors, I installed this ROM and its working, If you don't know how to... just go ahead
Thanks and credits to:
FXP team for the ROM
Moiremoi for the modified updater script which is making the rom working and tutorial (on another website)
Myself for testing, editing and for screenshots.
(If I forgot someone please tell it to me through MP)
Have fun and enjoy your new CM11 ROM !
Regards,
Exerath
Well, this changes many...
So the error was only in updater-script?? How? I see you added these lines, but they shouldn't take any effect.
Code:
getprop("ro.product.device") == "leo" ||
getprop("ro.build.product") == "leo" ||
In build.prop on D2203, there isn't ANY ro.product.device value
When there is a bad value, updater-script stops installing, but when there isn't any value, it fallsback (assumes a virtual value) to leo, am I right?
Why the hell is just our device so different , we don't even have last_kmsg where it is supposed to be
Vynikal said:
Well, this changes many...
So the error was only in updater-script?? How? I see you added these lines, but they shouldn't take any effect.
Code:
getprop("ro.product.device") == "leo" ||
getprop("ro.build.product") == "leo" ||
In build.prop on D2203, there isn't ANY ro.product.device value
When there is a bad value, updater-script stops installing, but when there isn't any value, it fallsback (assumes a virtual value) to leo, am I right?
Why the hell is just our device so different , we don't even have last_kmsg where it is supposed to be
Click to expand...
Click to collapse
Can i do this process for d2212 xperia e3 model
jayesp0411 said:
Can i do this process for d2212 xperia e3 model
Click to expand...
Click to collapse
porting in progress.
no network.
D2212
---------- Post added at 09:06 PM ---------- Previous post was at 09:03 PM ----------
Vynikal said:
Well, this changes many...
So the error was only in updater-script?? How? I see you added these lines, but they shouldn't take any effect.
Code:
getprop("ro.product.device") == "leo" ||
getprop("ro.build.product") == "leo" ||
In build.prop on D2203, there isn't ANY ro.product.device value
When there is a bad value, updater-script stops installing, but when there isn't any value, it fallsback (assumes a virtual value) to leo, am I right?
Why the hell is just our device so different , we don't even have last_kmsg where it is supposed to be
Click to expand...
Click to collapse
i downloaded cm11 from fxp and flashed it without editing updater-script it failed than i wipe data and cache then flashed it worked.
i was using my own latest cwm with fixed resolution.
(i have tested it with ported kernel)
device is leo bug was because old cwm was made for leo new fixed resolution is for flamingo.
so no bug,s
vinay said:
porting in progress.
no network.
D2212
---------- Post added at 09:06 PM ---------- Previous post was at 09:03 PM ----------
i downloaded cm11 from fxp and flashed it without editing updater-script it failed than i wipe data and cache then flashed it worked.
i was using my own latest cwm with fixed resolution.
(i have tested it with ported kernel)
device is leo bug was because old cwm was made for leo new fixed resolution is for flamingo.
so no bug,s
Click to expand...
Click to collapse
I seen that you did a lot of great work for the E3, now I am just curious to know if you (or someone else reading this) can make the volume of CM11 a bit louder (aka stronger)
I reflashed stock 4.4.2 with Viper4Android on my E3 and the sound is drastically higher as with CM11+Viper4Android (On 4.4.4 xLoud is missing too, idk why, I tought it were a stock official firmware ??)
I checked every setting about sound but I don't see any error, could it be the sony XLoud thing (absent on CM11) which could make this issue with lower powered sound?
Searching on Google to ''install or flash xLoud" but no hope atm, I found nothing working (a lot of error flashing .zip but none working) :/
This is known on almost all devices. The volume is always lower on AOSP ROMs than on stock. Xloud isn't easy to add, only very good themers are able to include it. You have to understand Xloud is proprietary and not open-sourced.
Trust me, it was truly a shock, when I heard silent speakers of my old LWW with CM just installed
Vynikal said:
This is known on almost all devices. The volume is always lower on AOSP ROMs than on stock. Xloud isn't easy to add, only very good themers are able to include it. You have to understand Xloud is proprietary and not open-sourced.
Trust me, it was truly a shock, when I heard silent speakers of my old LWW with CM just installed
Click to expand...
Click to collapse
Volume was higher with cm 10 on my xperia J as on Stock, on AOSP we have the possibility to disable audio security imposed from governments, on stock not, that's why I asked
Thanks Exerath for thé translation !
you guy,s are lucky.
i am thinking why did i bought this dual variiant even if rom get ported to non lte dual sim still gona need porting for second sim support.
never gonna buy non lte or dual sim again.
even tho there is no lte in my area.
all i get is no baseband.
vinay said:
you guy,s are lucky.
i am thinking why did i bought this dual variiant even if rom get ported to non lte dual sim still gona need porting for second sim support.
never gonna buy non lte or dual sim again.
even tho there is no lte in my area.
all i get is no baseband.
Click to expand...
Click to collapse
Why not release it for d2202? Network might work for us
Finally updated to 4.4.4 xD
hell_lock said:
Why not release it for d2202? Network might work for us
Finally updated to 4.4.4 xD
Click to expand...
Click to collapse
Well uday tested it.
No network on d2202 even. I will upload it in free time.
problem is with ril.
(and before flashing cm11 if your wifi is off then it won't turn on. That's what i found. And i gave up. i can't fix ril tried replacing libril.so, refrences_ril.so and one more lib i forgot name. And tried thousands of combination of stock and cm11)
(i am not experienced in porting uploading kernel soon on this thread.)
Sent from my D2212 using XDA Free mobile app
D2202,d2212 support.
Port moved here => http://forum.xda-developers.com/xperia-e3/general/d2203-testers-cm11-t3179189
vinay said:
@Exerath can you give a link to this post on OP so other,s can find it easily.
STEPS
* DOWNLOAD boot.zip attached below.
* flash cm11 then flash this boot.img inside boot.zip.
it will work on d2202 and d2212
BUG,s
NO RIL NO BASRBAND (mean no network)
who is gonna fix bug,s => probably not me.
warning make sure your wifi is on before flashing cm11 or you can,t turn on after flashing cm11.
Click to expand...
Click to collapse
I will but not today, it is late and Im freaking ko
btw: If we flash your kernel, install hudge game and go back to normal, it would be working ? or not ?
Exerath said:
I will but not today, it is late and Im freaking ko
btw: If we flash your kernel, install hudge game and go back to normal, it would be working ? or not ?
Click to expand...
Click to collapse
Nope this is a just port kernel for d2202 and d2212.
Sent from my D2212 using XDA Free mobile app
Can i flash this on d2212 if yes what are the bugs????
Plz provide direct download link
Sent from my Moto G 2014 using XDA Premium 4 mobile app
amritmalviya said:
Can i flash this on d2212 if yes what are the bugs????
Plz provide direct download link
Sent from my Moto G 2014 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
just see two posts up thare is written everything.
Exerath said:
I will but not today, it is late and Im freaking ko
btw: If we flash your kernel, install hudge game and go back to normal, it would be working ? or not ?
Click to expand...
Click to collapse
no ril working then what is use of flashing cm11
Sent from my Moto G 2014 using XDA Premium 4 mobile app
amritmalviya said:
no ril working then what is use of flashing cm11
Sent from my Moto G 2014 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ril problem is just in d2212 and d2202 so other,s are enjoying it with ril.
back button and menu not work, how to solve?
entony80 said:
back button and menu not work, how to solve?
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------
easy solution.
use a hammer to press back button with full force.
-------------------------------------------------------------------------------------------
hard solution
try re flashing whole rom and wipe data/cache
--------------------------------------------------------------------------------------------