[DEV][ROM][24.7.] CyanogenMod 10.1 (Android 4.2.2)

[Guest killadroid]

try cm10.2 but don't expect it to be faster than gb.or u can try cm9 if u just want speed and good battery backup & not interested in latest features

[Guest schmatzler]

Thanks Konstat, your codebase helped me a lot in porting CM10.1 and 10.2 to my ZTE Tureis. I'm using this ROM also on a Base Lutea that is lying around here. Excellent work! :)

[Guest De@n]

Hello guys i was just close to brick my blade for good so i`m not feeling like testing again a lot of Roms so I`m asking for your help. Between cm10, this one and cm10.2 which is the most stable and best fit for daily use and also which one has best performance, also are these better than GB ROMS ? I am currently on stock 2.2.2 gen 2 windows upgraded blade.

Thx in advance

Flashing anything above CM10 is kinda pointless for the Blade.

[Guest Roy Fokker]

I've used all versions of CM 10 extensively and now CM 11, and it's by FAR the fastest and most usable on CM 11. It's not even a contest. Sure, it's still buggy and incomplete, but pointless? Hell no.

[Guest szpilasty]

+1

[Guest vgran]

Thanks for this!

[Guest toojunk]

Guys, I'm having issues with Endomondo, Sport tracker and similar programs. The installation ends with ''not installed'' error.Anyone with a solution to this problem?

 

[Guest Wajid Hussain]

Great!
Thankyou Very Much...

[Guest citakis]

I installed this rom to my blade, (which is my loyal companion for 3.5 years) instead of "CyanogenMod 10.2 - KonstaKANG" because I didn't want to repartission my blade's filesystem.

After 2 days of usage I was surprised by its speed. I was expecting it to be quite laggy but everything runs smooth enough. Everything is working so far flawlessly and I am hoping to be able to keep it.

I would like to thank KonstaT for his excellent work and for keeping my phone alive   :D

[Guest eriksahin]

in my opinion this is the best ROM  thanks KonstaT awesome! 

[Guest yunden]

I feel the same.

[Guest p42blade]

<edited>

 

G+ crashing in adreno driver?

As others have found G+ crashes on both these 10.1 and 11.0 roms; however I looked at the tombstones for 10.1 and found that the crash seems to pretty

reliable be in the adreno 200 egl drivers - where do the graphics drivers come from for these ROM images?   Is this just an old broken driver or a

mismatch with the kernel, or is it just G+ doing something that's broken in these drivers? Is there another version to try?

Given it's in the adreno driver, I don't think this is a G+ not supporting the CPU or anything like that (the latest G+ app was working on CM7 on my device

anyway prior to the upgrade):

 

Having said that; my edit is because I found some more tombstones, and those tombstones are newer CPU issues - there are crashes in netjni.so that are SIGILL's and they are the use of cbz/cbnz instructions

that are new in v6t2 which the blade doesn't have.

So the question then is why G+ installations are using v6t2 even on a device that's not declaring v6t2; I suspec there are multiple builds and that the android v4's are assuming v6t2 at least.

Other than finding a way to download the G+ for Android 2.x I can't see an easy solution.

(A non-easy solution would be to emulate cbz/cbnz).

 

pid: 2526, tid: 2526, name: droid.apps.plus  >>> com.google.android.apps.plus <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 25ffbff6
    r0 40422281  r1 003327d0  r2 00000000  r3 40421a37
    r4 00332738  r5 00331540  r6 25ffbff7  r7 00165160
    r8 52f874d4  r9 4ba429a4  sl 4ba4298c  fp becc36a4
    ip 40433d28  sp becc3608  lr 52e26bb9  pc 25ffbff6  cpsr 000e0030
    d0  7149f2ca7149f2ca  d1  444820007149f2ca
    d2  4930000041300000  d3  bc0a42cc000b0000
    d4  3f8000003f800000  d5  3f80000000000000
    d6  4afc3cd000000000  d7  7149f2ca3f000000
    d8  0000000000000000  d9  0000000000000000
    d10 0000000000000000  d11 0000000000000000
    d12 0000000000000000  d13 0000000000000000
    d14 0000000000000000  d15 0000000000000000
    scr 20000010

backtrace:
    #00  pc 25ffbff6  <unknown>
    #01  pc 00002bb7  /system/lib/egl/eglsubAndroid.so
    #02  pc 00018160  /system/lib/egl/libEGL_adreno200.so (eglFreeSurface+88)
Surface+260)                 /lib/egl/libEGL_adreno200.so (qeglDrvAPI_eglDestroy--More-- (0% of 166684 bytes)
    #04  pc 00005418  /system/lib/egl/libEGL_adreno200.so (eglDestroySurface+16)
    #05  pc 0000eaa7  /system/lib/libEGL.so (eglDestroySurface+66)
    #06  pc 00049af9  /system/lib/libandroid_runtime.so
    #07  pc 0001e890  /system/lib/libdvm.so (dvmPlatformInvoke+112)
*, JValue*, Method const*, Thread*)+394).so (dvmCallJNIMethod(unsigned int const--More-- (0% of 166684 bytes)
    #09  pc 00027ca0  /system/lib/libdvm.so
, JValue*)+176)              /lib/libdvm.so (dvmInterpret(Thread*, Method const*--More-- (1% of 166684 bytes)
st*, ArrayObject*, ArrayObject*, ClassObject*, bool)+358)hod(Object*, Method con--More-- (1% of 166684 bytes)
 

snip

 

stack:
t::perform(int, std::__va_list)+42)m/lib/libgui.so (android::SurfaceTextureClien--More-- (1% of 166684 bytes)
t::cancelBuffer(ANativeWindowBuffer*, int)+136).so (android::SurfaceTextureClien--More-- (1% of 166684 bytes)
         becc35d0  00000080
         becc35d4  003318f8
         becc35d8  40063000  /system/lib/libc.so
         becc35dc  003327f0
         becc35e0  00000002
         becc35e4  00000000
         becc35e8  00165160
         becc35ec  00332738
         becc35f0  00331540
         becc35f4  00000000
         becc35f8  00165160
t::hook_cancelBuffer_DEPRECATED(ANativeWindow*, ANativeWindowBuffer*)+18)reClien--More-- (1% of 166684 bytes)
         becc3600  df0027ad
         becc3604  00000000
    #00  becc3608  00332650
         ........  ........
    #01  becc3608  00332650
         becc360c  00165160
         becc3610  00332870
+92)                         /system/lib/egl/libEGL_adreno200.so (eglFreeSurface--More-- (2% of 166684 bytes)
    #02  becc3618  00332650
         becc361c  52f874d4  /system/lib/egl/libEGL_adreno200.so
         becc3620  00332870
         becc3624  00165160
         becc3628  becc3690  [stack]
DestroySurface+264)          /system/lib/egl/libEGL_adreno200.so (qeglDrvAPI_egl--More-- (2% of 166684 bytes)
    #03  becc3630  becc3660  [stack]
         becc3634  404776cc  /system/lib/libEGL.so
         becc3638  00000001
         becc363c  becc3664  [stack]
         becc3640  003328b0
         becc3644  40478cac
         becc3648  003328b0
         becc364c  003328b0
         becc3650  00000001
ace+20)                      /system/lib/egl/libEGL_adreno200.so (eglDestroySurf--More-- (2% of 166684 bytes)
    #04  becc3658  40478cac
         becc365c  40443aa9  /system/lib/libEGL.so (eglDestroySurface+68)
    #05  becc3660  404776a8  /system/lib/libEGL.so
         becc3664  003328b0
         becc3668  00012f48
         becc366c  00000000
         becc3670  91400021
         becc3674  40156afd  /system/lib/libandroid_runtime.so
    #06  becc3678  91400021
         becc367c  4bab6550  /dev/ashmem/dalvik-LinearAlloc (deleted)
         becc3680  40156aa1  /system/lib/libandroid_runtime.so
         becc3684  00000007
         becc3688  4ba429ac
         becc368c  4075c894  /system/lib/libdvm.so (dvmPlatformInvoke+116)
    #07  becc3690  00012f48
         becc3694  00000001
         becc3698  4075ca00  /system/lib/libdvm.so
         becc369c  00000006
         becc36a0  becc3b8c  [stack]
t const*, JValue*, Method const*, Thread*)+398).so (dvmCallJNIMethod(unsigned in--More-- (3% of 166684 bytes)


 

Edited May 4, 2014 by p42blade

[Guest Schwedenbitter]

Here's a fresh ClockWorkMod build with working adb sideload (extremely nice and useful feature for some of us).

recovery-clockwork-6.0.2.7-blade-sideload.zip

http://d-h.st/ViG

md5:e409ec9fe6267394ee272748bb1c2031

recovery.img

md5:6e0623a388d2229f8dcc66817337fa92

 

[EDIT]

Never mind. I just figured out, the download links just works fine. Sorry for that.

But my second question stand, just in case I could need it in the future.

[/EDIT]

 

Can someone reup one of these files again, please?

I used TPT Helper to change /system partition to 160 MB, which was enought for 4.2. But now I'd like to test Android 4.4.2 with my Blade.Unhappily it needs a /system partition with at least 180 MB. So I wanted to use TPT Helper again. The only problem is, it comes with an old CWM recovery 5.0.2.0. This can't handle the newer backups, due to the compression used by CWM 6.0.2.7. This would make it impossible for me to go back to my old system.

 

So my plan would be to use 1) TPT Helper to change partitions, 2) change CWM back to 6.0.2.7 and 3) try the new ROM. If it fails I need to go back to my old ROM, without having an old backup.

 

I would even appreciate, if someone could tell my how to save the old one from the phone. I know there is a procedure to flash a recovery.img to the phone with the Terminal Emulator. Unfortunately I forgot the command for this operation. As far as I remember it was something with "flash ...". I could imagine, that there would be comparable command/procedure to save the image from phone to my sdcard... So if you know more then me, don't hesitate to tell me, how it works.

 

Thanks, Alex

Edited June 1, 2014 by Schwedenbitter

[Guest dreis911]

[EDIT]

Never mind. I just figured out, the download links just works fine. Sorry for that.

But my second question stand, just in case I could need it in the future.

[/EDIT]

 

Can someone reup one of these files again, please?

I used TPT Helper to change /system partition to 160 MB, which was enought for 4.2. But now I'd like to test Android 4.4.2 with my Blade.Unhappily it needs a /system partition with at least 180 MB. So I wanted to use TPT Helper again. The only problem is, it comes with an old CWM recovery 5.0.2.0. This can't handle the newer backups, due to the compression used by CWM 6.0.2.7. This would make it impossible for me to go back to my old system.

 

So my plan would be to use 1) TPT Helper to change partitions, 2) change CWM back to 6.0.2.7 and 3) try the new ROM. If it fails I need to go back to my old ROM, without having an old backup.

 

I would even appreciate, if someone could tell my how to save the old one from the phone. I know there is a procedure to flash a recovery.img to the phone with the Terminal Emulator. Unfortunately I forgot the command for this operation. As far as I remember it was something with "flash ...". I could imagine, that there would be comparable command/procedure to save the image from phone to my sdcard... So if you know more then me, don't hesitate to tell me, how it works.

 

Thanks, Alex

If you want to backup your ROM enter the Recovery > Backup & Restore > backup

[Guest Schwedenbitter]

If you want to backup your ROM enter the Recovery > Backup & Restore > backup

This seems to be a missunderstanding:

I know how to backup the phone and with it the ROM. I want to backup up the recovery itself.

[Guest dreis911]

This seems to be a missunderstanding:

I know how to backup the phone and with it the ROM. I want to backup up the recovery itself.

Ups. Sorry if I misunderstood you.

So, you want to backup the "backuper"? ...  /boot + /recovery + /system + /data + /cache?

 

If that is what you want... then it's just what I told you before! ... and it's called a NANDROID!

it's done by the Recovery and it does a self-backup.

 

If it's not that... then I don't understand you. You'll have to be more precise on what you want.

[Guest Schwedenbitter]

Thank you for your answer.

 

I quoted the post by KonstaT on purpose.

I'm just looking for a procedure to save the current ClockWorkMod recovery in a file like recovery.img. The partitions/folders /boot, /system, /data, /cache are saved by the backup itself. There's no need to save it with another method. The only missing thing would be /recovery. But I was hardly looking for something like this without success. I couldn't find a partiton/folder named /recovery.

Then you say just told me before ... it's called NANDROID. Even this I was hardly looking in your post yesterday. It has just one sentence without NANDROID. And it's not what I'm looking for, too. This just make a backup without rebooting in recovery mode or a recovery image in boot itself. But I want a recovery image. I'm just looking to backup it ...

 

[EDIT1]

I just tried NANDROID on my old ZTE Skate. It saves a recovery.img, which looks good. But the saved recovery.img is 5.242.880 Bytes, whereas the uses recovery.img I flashed to this phone about 2 years ago ist just 4.536.320 Bytes. So I'm still not sure, if I really can rely on this image file...

[/EDIT1]

 

[EDIT2]

On my Linux system I make backups using the "dd" command. I hardly remember using a command like "flash" or something to save the old recovery.img to the phone. The "dd" command ist quite simple to invert with the switches if= and of=. This is what I'm looking for.

[/EDIT2]

Edited June 2, 2014 by Schwedenbitter

[Guest dreis911]

Thank you for your answer.

 

I quoted the post by KonstaT on purpose.

I'm just looking for a procedure to save the current ClockWorkMod recovery in a file like recovery.img. The partitions/folders /boot, /system, /data, /cache are saved by the backup itself. There's no need to save it with another method. The only missing thing would be /recovery. But I was hardly looking for something like this without success. I couldn't find a partiton/folder named /recovery.

Then you say just told me before ... it's called NANDROID. Even this I was hardly looking in your post yesterday. It has just one sentence without NANDROID. And it's not what I'm looking for, too. This just make a backup without rebooting in recovery mode or a recovery image in boot itself. But I want a recovery image. I'm just looking to backup it ...

 

[EDIT1]

I just tried NANDROID on my old ZTE Skate. It saves a recovery.img, which looks good. But the saved recovery.img is 5.242.880 Bytes, whereas the uses recovery.img I flashed to this phone about 2 years ago ist just 4.536.320 Bytes. So I'm still not sure, if I really can rely on this image file...

[/EDIT1]

 

[EDIT2]

On my Linux system I make backups using the "dd" command. I hardly remember using a command like "flash" or something to save the old recovery.img to the phone. The "dd" command ist quite simple to invert with the switches if= and of=. This is what I'm looking for.

[/EDIT2]

The reason why the original Recovery.img was smaller is that it was compiled as a program, so it has the size of the code it occupies.

The reason why your backup Recovery.img has 5MB is because the /recovery partition is that size!!!

When you call the Recovery on PowerUp, the program installed in your phone that runs is the Recovery itself, but this Recovery doesn't know it's own size.

So when it does the backup, it backs up ALL the /recovery partition so it doesn't miss anything. And it does the same with the /boot partition.

I don't know if I made myself clear...

[Guest tb1337]

this rom working on blade G V955 ?

[Guest dexta]

Can someone send me tutorial how to root this phone?
I need it for my sister, she have Zte Blade (Fashion TV)

If someone can send me valid link or say me how to root this phone, I will be gratefull.. I want to install this custom rom...

[Guest szpilasty]

http://www.modaco.com/index.php?/topic/335781-22/Apr-[GUIDE]-How-to-Install-a-Custom-ROM-on-the-ZTE-u-v880-or-[GEN2]-device#entry1649086

z4root - application

[Guest vazee00]

Hy!

 

I need a little help. After the digitizer replace touch screen work with only 2.3 rom, all 4.x touch screen is unresponsive.

Does anyone have any ideas?

 

Thanks!

• 0

•  Back to top
•  Quote
•  MultiQuote
•  Edit
•  Report

[Guest killadroid]

..

Edited July 26, 2014 by killadroid

[Guest janjevac]

Download link doesn't work!!! Can you someone upload it somewhere else so I can download? THX

[Guest theopan]

Nice ROM, works very well, cellular and wifi signals are better than stock ROM, but I have to point three things:

1) Google voice search doesn't work (crashes immediately)

2) Battery is drained a lot faster than with stock ROM (less than 15-20 hours autonomy with the exact same usage compared to 2,5 days with the stock one).

3) Bluetooth shows a difficulty to connect with some headsets and even after you manage to pair the devices, sometimes connection easily fails.

I can live with 1 and 3 but I am afraid that I will have to go back to stock due to number 2...

Edited October 29, 2014 by theopan