yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] HB72K:
ROM STOCK

gamming

[MENTION=5193140]Nonta72[/MENTION] could you please update the index post?

en esta ocasión quiero compartir les su ROM stock, gamer, tiene las siguientes caracteristicas.

Deodex

Tweaks

Busybox.

Swap 480 mb

zipalling, para mejor gestión de RAM.

Flashen la ROM luego, el super user y después el activador.

Gracias a Neri de Lenfet por proporcionarme el kernel y la tabla de particones del Y635

rom

https://mega.nz/#!m0lFxQjA!jpeJbvXLLIhPawj6b3O2cucgFzcrOffnGmV-en8ZALc

;)

Root

https://mega.nz/#!zwVgCYSC!ZVf0l500caEnqDtjZidsOfQXTRD1bSUMbRhq_ErSme4 :fingers-crossed:

Swap

https://mega.nz/#!7wdwWTSA!uIUzbL-bppVlsSldSr8XzUniwcIRn5w0dl1JUByZqLE :good:

＃ Instalación:

#opcional Hacer un backup con el (TWRP de preferencia) ó CWM.

——— ☆ Instructions for installing a ROM ☆ —————————————

(TWRP)

1. Restart the phone in recovery mode (Power and Volume +)

2. Select Wipe option

3. Choose Advanced Wipe

4. Choose Dalvik Cache, cache, data (#opcional internal storage, system (I use only when I gave bootloop))

5. Swipe to wipe

6. Go Back and choose Install zip from SD External, select the file you downloaded in your SD and installation will begin, vibrate after installation, then give you reboot system.

wait up to 5 minutes until the cell starts with the system properly

7. Let the rom is properly seated about 10 minutes and restart again

CWM RECOVERY:

1. Restart the phone in recovery mode (Power and Volume +)

2. Select Wipe Data / Factory Reset option

3. Select Wipe Cache Partition

4. Select Advanced, and then Wipe Dalvik Cache

5. Go Back and choose Install zip from SD Card, choose the file you downloaded in your SD and installation will begin

wait up to 5 minutes until the cell starts with the system properly

6. Let the rom is properly seated about 10 minutes and restart again

(TWRP)

1. Reiniciar el celular en modo recovery (Encendido y Volumen +)

2. Elegir la opción Wipe

3. Elegir Advanced Wipe

4. Elegir Dalvik Cache, cache, data (#opcional internal storage, system( solo lo utilizo cuando me dio bootloop ))

5. Swipe to wipe

6. Go Back y elegir Install .zip from External SD, elegir el archivo que descargaron en su SD y la instalación comenzará, vibrara al terminar la instalacion, despues le dan reboot system.

esperen máximo 5 minutos hasta que su celular inicie con el sistema correctamente

7. Dejen que la rom se asiente correctamente unos 10 minutos y vuelvan a reiniciar

CWM RECOVERY:

1. Reiniciar el celular en modo recovery (Encendido y Volumen +)

2. Elegir la opción Wipe Data/Factory Reset

3. Elegir Wipe Cache Partition

4. Elegir Advanced, y luego Wipe Dalvik Cache

5. Go Back y elegir Install .zip from SD Card, elegir el archivo que descargaron en su SD y la instalación comenzará

esperen máximo 5 minutos hasta que su celular inicie con el sistema correctamente

6. Dejen que la rom se asiente correctamente unos 10 minutos y vuelvan a reiniciar
[Miscellaneous Android Development] desalesouche:
cm-12.1 test for Y635-L01

hi all. thanks to nonta feed back and test and energy, i could compile booting cm12.1 for y635 device.

according nonta, only camera is not working. i hope you, Y635 users and devs can fix the problem.

i can't do more that what i did cos i don't own device. i only have G620s-L01.

here is the link for test.

http://www.mediafire.com/download/da1yahmr5z4e75g/cm-12.1-20160115-Y635test2-g620s.zip

here is kernel 3.10.49 sources https://github.com/desteam/android_kernel_huawei_msm8916/commits/Y635

i will push change to device tree soon but it is really minor change like correcting lcd density and resolution, adding asserts : see attached screenshots

please feed back only here in that thread. don't pm me.
[Miscellaneous Android Development] desalesouche:
Y635-L03 support added

new build http://www.mediafire.com/download/kk3pz05jpkp31pd/cm-12.1-20160118-Y635-L01-L03-g620s.zip

let me know if there is some progress with cam
[Miscellaneous Android Development] Nonta72:
I'm testing now.

I will give you results on Hangouts.

Edit:

Tested but "Can't connect to camera" error always occur. Camera icon is still invisible!

I have also found a new bug in all of the cm12.1 builds that boot on Y635 (even surdu's builds for G620S): Calls can't be hang up! If you make call, you need to reboot (or soft reboot) to end the call :(
[Miscellaneous Android Development] Nonta72:
Camera problem

I have made logcat and dmesg of CyanogenMod 12.1 ROM and stock rom!

I compared them (somehow) and find out something very WEIRD!

The dmesg of CM12.1 states that the S5K4E1 failed to start! I didn't find any mention of S5K5E2 which is our camera sensor module. It does see the front camera but fails to start it though. I think it makes sense because the front camera depends on the rear one; so if rear one isn't detected, the front one can't probably start even if it's detected.

<3>[275, mm-qcamera-daem][ 13.754314] msm_sensor_match_id: [COLOR="Red"]s5k4e1_foxconn_dc0301a[/COLOR]: read id failed
<3>[275, mm-qcamera-daem][ 30.544443] msm_sensor_match_id: [COLOR="red"]ov2680_ofilm_fe16[/COLOR]: read id failed

I have also found this line in the logcat but there is no mention of either the S5K5E2 or the S5K4E1 !

01-01 10:40:19.549 E/mm-camera-sensor( 275): sensor_init_probe:347 camera_module_name:ov2680_ofilm_fe16

Note: Many of these lines are in the dmesg!

The dmesg of stock rom shows this:

<3>[307, mm-qcamera-daem][ 6.330921] [COLOR="DarkGreen"]s5k5e2_foxconn_hc0806[/COLOR] probe succeeded
<3>[307, mm-qcamera-daem][ 6.655225] [COLOR="darkgreen"]ov2680_byd_bm2920b[/COLOR] probe succeeded

The stock rom logcat doesn't contain any mention of S5K5E2 or OV2680

Note: I didn't find more than one of each lines in the dmesg :)

Here are all logs:

- CM-12.1 logs:

Dmesg

Logcat

- Stock ROM (EMUI 3.0 - Android 4.4.4)

Stock ROM Dmesg

Stock ROM logcat (not the entire because it exceeds 512kbs)
[Miscellaneous Android Development] Nonta72:
New update! Camera LED Flash now works !!!

After many attempts with [MENTION=4479868]desalesouche[/MENTION] we are almost done with camera. The LED Flash now works with torch apps but camera still doesn't work.

We replaced libmmcamera2_sensor_modules.so and aftet that, some progress has been made!

In fact, using the 'libmmcamera2_sensor_modules.so' from stock rom makes LED Flash work! And this is what dmesg states now regarding the camera sensors:

<3>[276, mm-qcamera-daem][ 6.401282] [COLOR="Green"]s5k5e2_foxconn_hc0806[/COLOR] probe succeeded

But the front camera sensor still fails to start:

<3>[276, mm-qcamera-daem][ 6.752924] [COLOR="Red"]ov2680_byd_bm2920b[/COLOR] power up failed

What logcat says now regarding the sensor:

01-01 13:27:51.409 E/mm-camera-sensor( 276): af_actuator_init:629 name = s5k5e2_foxconn_hc0806
01-01 13:27:51.409 E/mm-camera-sensor( 276): actuator_load_lib:542 name=s5k5e2_foxconn_hc0806, mode=camera
01-01 13:27:51.409 E/mm-camera-sensor( 276): actuator_load_lib:564 library libactuator_s5k5e2_foxconn_hc0806.so successfully loaded, idx=0
01-01 13:27:51.409 E/mm-camera-sensor( 276): actuator_load_lib:588 library libactuator_s5k5e2_foxconn_hc0806_camera.so successfully loaded, idx=0
01-01 13:27:51.409 E/mm-camera-sensor( 276): actuator_load_lib:542 name=s5k5e2_foxconn_hc0806, mode=camcorder
01-01 13:27:51.409 E/mm-camera-sensor( 276): actuator_load_lib:588 library libactuator_s5k5e2_foxconn_hc0806_camcorder.so successfully loaded, idx=1

If we replace just the 'libmmcamera2-sensor-modules.so" dmesg says that powering the s5k5e2 failed too and it makes sense because the cm12.1 rom we are testing doesn't come with any s5k5e2 lib! Thus, the sensor can't be powered on. After adding the missing s5k5e2 libs to the rom, the dmesg shows that the camera is successfully loaded. 13 Modules related to the s5k5e2 were missing; we added them.

The same way, we added the missing ov2680 missing files but for some reasons, it still can't start.

THE STOCK CAMERA STOPPED DISAPPEARING FROM LAUNCHER TOO !

The full DMESG: http://pastebin.com/gdYccNR5

The whole LOGCAT: http://pastebin.com/gdYccNR5

Here's a video:

https://www.youtube.com/watch?v=bl-4vmtX8sE

Keep visiting, Good things here soon; promised!
[Miscellaneous Android Development] desalesouche:
about calls can't be hang up problem.

here is solution. add it to op.

Baseband required in order to fix Dialer issue :

Flash 1° or 2°

1° g7-l01_modem.zip - 25.01 MB

2° 4xqwt_lp_modem.zip

you will find zip file at following link

http://xdaforums.com/showpost.php?p=62902848&postcount=273
[Miscellaneous Android Development] Nonta72:
Thanks man!

The second file fixed this issue. 1st one gives No Signal.

Added to Op!
[Miscellaneous Android Development] Nonta72:
New !!! Front Camera now works!

I managed to get front camera to work somehow :D

I used CyanogenMod Camera Next from this post http://xdaforums.com/moto-g/themes-apps/apps-cyanogen-camera-gallery-t3187041

After launching the app, you need to quickly click on the switch camera button to switch to selfie mode before the camera force close lol
[Miscellaneous Android Development] Nonta72:
New ROM, Flyme OS Android 5.1.1

I have a new ROM for you guys, still have camera bug.

Flyme OS 4.5.4R for G620S (work on Y635).

>>> REAR CAMERA DOES NOT WORK. FRONT CAMERA WORKS AND TAKES PICTURES BUT PICTURES BECOME ALL BLACK <<<

Installation:​

1) Download the ROM from here Mega (551.4 MB)

2) Download the Patch from here Mega (12.7 MB)

> The patch contains camera libs to prevent camera apps from disappearing and also make front camera work. If you want to take photos with front camera, please try Camera Next from my previous post because integrated camera will start to force close after one use. So you need to reset its data in settings. The patch also contains a custom boot.img and a build.prop. Both files must be used only with this rom.

3) Put both in your sdcard, reboot to recovery and flash ROM then the patch.

4) Reboot and Enjoy :D

Note: First boot can take up to 10 minutes! Be patient.

Screenshots:​

Credits:​

- [MENTION=2335078]surdu_petru[/MENTION]

- [MENTION=4479868]desalesouche[/MENTION]

- haohao3344

- GLokin666 @ HTCMania

Source: HTCMania
[Miscellaneous Android Development] surdu_petru:
Yep, very good - you are not far away to activate the camera :o

First, you should keep all libraries and also ( system/bin/mm-qcamera-daemon) related camera from your stock rom, and not from cm-12.0 for G620S !

After you already repalced all libraries, please provide logcat after you try to enable camera !

If camera cannot be detected/open , please go into your device , and let me to know what you can see after this command :

> adb shell
$ su
# mm-qcamera-daemon

Thanks !
[Miscellaneous Android Development] Nonta72:
Hi,

Nice to see you here :D

About keeping camera libs, I have already copied everything with "actuator", "chromatix" and "mmcamera" from stock/vendor/lib to cm-12.1/vendor/lib. I can't just directly use the entire 'lib' folder from stock/vendor; else, I will get bootloop.

Anyways, here's the results from the command:

root@y635:/ # mm-qcamera-daemon
mm-qcamera-daemon
WARNING: linker: libmmcamera_imglib.so: unused DT entry: type 0x6ffffffe arg 0x2050
WARNING: linker: libmmcamera_imglib.so: unused DT entry: type 0x6fffffff arg 0x1
root@y635:/ #

Here are both newest logcat and dmesg:

- newest_logcat.log

- newest_dmesg.log

I know, the logcat is from Flyme OS; but the camera behave just the same way in every cm-12.1 rom and Flyme OS is based on cyanogenmod if I'm not wrong. The problem exist with all kernels: yours, desalesouche's builds and mines aswell.
[Miscellaneous Android Development] surdu_petru:
You shouldn't post here the whole logcat. You can upload only the lines related camera from logcat ... and you must try to open camera while you take logcat.

So do "adb logcat > log.txt" and right now please try to open camera for few times .... In this way you will be able to see into logcat all issues about camera.

Thanks !
[Miscellaneous Android Development] Nonta72:
Well, I don't know if I did right, but I procceeded as you said. Here's what I found related to camera error.

E/mm-camera( 324): isp_hw_find_primary_cid:304 error cannot find primary sensor format

E/mm-camera( 324): ispif_proc_streamoff: error: No streams to be stopped

E/mm-camera( 324): ispif_proc_streamoff: ISPIF_CFG error = -1

E/mm-camera-img( 324): faceproc_save_album:794] Error No album

E/CAM_Util( 6224): Show fatal error dialog

E/mm-camera-sensor( 324): af_actuator_set_params:439 failed rc -1

E/mm-camera-sensor( 324): actuator_process:1094 failed rc -1

E/mm-camera-sensor( 324): module_sensor_stream_on:2426 sensor_failure : ACTUATOR_SET_PARAMETERS failed

E/mm-camera-sensor( 324): module_sensor_module_process_event:3471 failed

E/mm-camera-intf( 258): mm_stream_streamon: ioctl VIDIOC_STREAMON failed: rc=-1

E/mm-camera-intf( 258): mm_channel_start: start stream failed at idx(1)

E/mm-camera-sensor( 324): port_sensor_port_process_event:1230 failed

E/mm-camera-img( 324): faceproc_comp_eng_destroy: Album save failed -1

E/CAM2PORT_AndCamAgntImp( 6224): java.lang.RuntimeException: startPreview failed

E/CAM_CameraActivity( 6224): java.lang.RuntimeException: startPreview failed

W/PackageManager( 3269): Failure retrieving resources for com.android.camera2: Resource ID #0x0

E/mm-camera( 324): Fail,cpphw=0xb7af6558, hw_params=0xb7c31cc8, chromatix_ptr=0x0, trigger=0xb7b4fc88

E/mm-camera( 324): Fail,cpphw=0xb7af6558, hw_params=0xb7c31cc8, chromatix_ptr=0x0, trigger=0xb7b4fc88

E/mm-camera-sensor( 324): af_actuator_set_params:439 failed rc -1

E/mm-camera-sensor( 324): actuator_process:1094 failed rc -1

E/mm-camera-intf( 258): mm_stream_unreg_buf: fd=58, VIDIOC_REQBUFS failed, rc=-1

E/mm-camera( 324): c2d_hardware_process_streamoff:208: failed

E/mm-camera( 324): c2d_module_handle_streamoff_event:1496: hw streamoff failed

E/mm-camera( 324): cpp_hardware_process_streamoff:648: failed

E/mm-camera( 324): cpp_module_handle_streamoff_event:2096: hw streamoff failed

E/mm-camera( 324): Fail,cpphw=0xb7af6558, hw_params=0xb7c30438, chromatix_ptr=0x0, trigger=0xb7b88968

E/mm-camera( 324): Fail,cpphw=0xb7af6558, hw_params=0xb7c30438, chromatix_ptr=0x0, trigger=0xb7b88968

W/PackageManager( 6224): Failure retrieving resources for com.android.gallery3d: Resource ID #0x0

W/CameraBase( 6224): Camera service died!

Full log (ONLY CAMERA RELATED LINES AS YOU SUGGESTED) => camera_log.txt
[Miscellaneous Android Development] surdu_petru:
Ok, I saw some issues with actuator : "MAX_ACTUATOR_REGION is exceeded." - so, this function "msm_actuator_set_param" from this : "../kernel/huawei/msm8916/drivers/media/platform/msm/camera_v2/sensor/actuator/msm_actuator.c" , cannot set correct parameters for actuator - because return -EFAULT

static int32_t msm_actuator_set_param(struct msm_actuator_ctrl_t *a_ctrl,

struct msm_actuator_set_info_t *set_info) {

struct reg_settings_t *init_settings = NULL;

int32_t rc = -EFAULT;

uint16_t i = 0;

struct msm_camera_cci_client *cci_client = NULL;

CDBG("Enter\n");

for (i = 0; i < ARRAY_SIZE(actuators); i++) {

if (set_info->actuator_params.act_type ==

actuators->act_type) {

a_ctrl->func_tbl = &actuators->func_tbl;

rc = 0;

}

}

if (rc < 0) {

pr_err("Actuator function table not found\n");

return rc;

}

if (set_info->af_tuning_params.total_steps

> MAX_ACTUATOR_AF_TOTAL_STEPS) {

pr_err("Max actuator totalsteps exceeded = %d\n",

set_info->af_tuning_params.total_steps);

return -EFAULT;

}

if (set_info->af_tuning_params.region_size

> MAX_ACTUATOR_REGION) {

pr_err("MAX_ACTUATOR_REGION is exceeded.\n");

return -EFAULT;

}

*************

At this point, only a stock kernel from your device can help us - we need to make some comparisons, because I think something is missing compared to your stock kernel for your device.

So, if you have a stock Huawei kernel for your Y635 device, please push it without modification on your github - when I'll have some free time, I'll try to take a look ( maybe I can help more ) . Thanks !

On the other hand, why you not try to compile only for your device, without adding in the kernel other devices, so you can rename g620s_defconfig to y635_defconfig and disable all support for other devices, you should let only "CONFIG_SUPPORT_Y635 = y" - then edit Makefile from ... ../kernel/huawei/msm8916/arch/arm/boot/dts/qcom/ !

Also you can take a look here about camera blobs, my advice is to remove all dependency related camera from cm-12.1, and than you can add back from your device - in your device may be more or fewer libraries, so should not be mixed with the cm-12.1 for G620S !
[Miscellaneous Android Development] Nonta72:
That really makes sense! In you cm11 builds, I could fix camera by using stock zImage with cm11 ramdisk then replacing the vendor/lib folder of that rom with stock one :D But stock kernel can't be used in cm12.1

Sure, I will push it; it will be ready tomorrow.

Well, we just used your kernel source with some little modifications. I will try what you suggested.

We've already did so...Somehow. But we added missing libraries especially related to s5k5e2 and ov2680. I also created a test vendor blob with only y635; but I was running into some weird errors during compiling process.

Anyways, see this commit here on github
[Miscellaneous Android Development] Ksawery:
I've reflashed the CM-12.1 with kernel 3.10.49 rom in my phone.

Now I have the camera icon in the drawer and the AudioFX works fine but light and proximity sensors are still not working ( they worked fine in Kitkat).

It's very strange. Any idea to fix it?
[Miscellaneous Android Development] Nonta72:
If they don't work

Just live with it ;)
[Miscellaneous Android Development] Ksawery:
Yeah, but I can't stay stopped and I retried several times (a lot... with same results) and I tried another rom also.

The result was the phone stayed in "Android Starting, Finishing Boot" and if I rebooted Android it showed me "Unfortunately System UI has Stopped".

I also reinstalled the recovery...

At the end I restored my backup.

Now I have the phone like when I started, more or less, but I lost some things and I can't connect to Pc. The phone shows me "USB is now disconnected".

I think this is due to a drivers issue.

I think I will try to reflash the CM-12.1 with kernel 3.10.49 rom. I will keep my fingers crossed.

My question is: Do you think all these problems were caused by a recovery failure?
[Miscellaneous Android Development] Zenzfum000:
Try a KitKat rom and see if problems persists
[Miscellaneous Android Development] Nonta72:
I am not sure
[Miscellaneous Android Development] Ksawery:
I've tried the CM-11 by surdu petru for G620S (Kitkat) rom. Now I can connect to PC fine and the camera/lantern are working but the rotation fails sometimes :eek:.

The proximity sensor and light sensor don't seem to work :silly:

This is crazy, guys!
[Miscellaneous Android Development] Zenzfum000:
Then if you still have hardware problems, if u try stock rom and results doesn't changes, buy a new phone
[Miscellaneous Android Development] Nonta72:
Hahaahhhhh

Nailed it :D
[Miscellaneous Android Development] Ksawery:
I will end by trying it but this will be my last option. I still believe this is a software issue. The phone worked fine with stock rom and only began to show problems with custom roms.

Thanks guys! I will post results if I make it work.
[Miscellaneous Android Development] Zenzfum000:
Anyone know how to remap buttons for our device? Home and menù in cm 12.1 are really strange :confused:
[Miscellaneous Android Development] mujahidsx2:
Does anyone have the first stock rom version ?
[Miscellaneous Android Development] Zenzfum000:
What do you mean with first version? My phone was born with 4.4.4, idk if there were older versions. Anyway, search on Google, he's your friend [emoji6]

Sent from Peiteddu's hands
[Miscellaneous Android Development] Ksawery:
You can find the stock rom at: consumer.huawei.com.

Seek between the different languages...
[Miscellaneous Android Development] mujahidsx2:
You guys got me wrong... I mean GK-Stock rom... which is called gaming rom also
[Miscellaneous Android Development] Zenzfum000:
No these two roms are differenti, anyway, you can find them @ gr2huaweiy635.blogspot.it

Sent from Peiteddu's hands
[Miscellaneous Android Development] mujahidsx2:
Link doesn't work bro
[Miscellaneous Android Development] Zenzfum000:
http://gr2huaweiy635.blogspot.it/?m=1

Sent from Peiteddu's hands
[Miscellaneous Android Development] desalesouche:
Y635 test

Hi all, i need new kernel with new feature, to be tested. done for Y635 ( all variants) fastboot it on the cm-12.1 rom done for Y635 by myself or you can try to fastboot on others Lollipop rom done for y635 from the device tree i did... Please give feed back.

link: http://www.mediafire.com/download/dvb384d9fk5lkvc/gputest-boot.img

added cpu and gpu oc feature, frandom and more...

that kernel now is common/same for Y635 and y550.

so if some y635 developpers wanna help please write me
[Miscellaneous Android Development] Ksawery:
I think I find the origin of all my problems: the Philz Touch recovery.

I changed to TWRP and now all seems to work fine (except the sensors...).
[Miscellaneous Android Development] Zenzfum000:
I should flash this img with

fastboot flash boot boot.img on cm 12.1?

Sent from Peiteddu's hands
[Miscellaneous Android Development] desalesouche:
yes i think so, may be with sudo if permission problem
[Miscellaneous Android Development] Zenzfum000:
Sent from the mailman

---------- Post added at 04:35 PM ---------- Previous post was at 04:32 PM ----------

Sent from the mailman
[Miscellaneous Android Development] desalesouche:
well done man. so that kernel have gpu and cpu overclock and underclock i have another kernel with compass fix and some more optimization use kernel adiutor apk to set cpu and gpu gov etc... please feed back

edit : link new boot.img http://www.mediafire.com/download/59u81u79z8xc1w6/compass-boot.img

rename it boot.img ans fastboot it. thanks
[Miscellaneous Android Development] Zenzfum000:
In latest kernel all is working fine and the performances are increased

Sent from the mailman
[Miscellaneous Android Development] desalesouche:
I will soon upgrade kernel to latest linux : 3.10.101
[Miscellaneous Android Development] Zenzfum000:
Is possible to add dt2w? Or do u think it will cause problems?

Sent from the mailman
[Miscellaneous Android Development] desalesouche:
May be , i don't know yet i need someone to compile cm-12.1 rom for huawei Y635, my pc is not stable at the moment.
[Miscellaneous Android Development] Nonta72:
I'm still here (monitoring).

I can compile ... I will need to redownload the whole sources from scratch again :rolleyes:
[Miscellaneous Android Development] desalesouche:
can you try to use these sources please? these one seems to work on Y635 and also Y550 devices, thank you.

https://github.com/DemoniacTeam/andr...-/tree/cm-12.1

https://github.com/DemoniacTeam/andr...-/tree/cm-12.1

https://github.com/desteam/android_k...8916/tree/Y635

may be it is needed to add in init support for all Y550 variant?
[Miscellaneous Android Development] Nonta72:
Sure ...
[Miscellaneous Android Development] Zenzfum000:
https://github.com/DemoniacTeam/

Sent from the mailman
[Miscellaneous Android Development] desalesouche:
cm-12.1 update test

Hi all i am uploading a cm-12.1 update, i need a y635 testor L01-L03
[Miscellaneous Android Development] TheMichalos:
Im ready.
[Miscellaneous Android Development] Zenzfum000:
Me too

Sent from Peiteddu's hands
[Miscellaneous Android Development] desalesouche:
Y635-L02 stock build.prop

Please all Y635-L02 stock build.prop is needed to add support. thank you
[Miscellaneous Android Development] Zenzfum000:
I can only provide l21 tomorrow

Sent from Peiteddu's hands
[Miscellaneous Android Development] TheMichalos:
Can get it today. Wait 30-40 mins. Downloading and extracting firmware.
[Miscellaneous Android Development] desalesouche:
thanks. L21 or L02?
[Miscellaneous Android Development] TheMichalos:
L02
[Miscellaneous Android Development] desalesouche:
Y635 test

hi all does that recovery is ok for Y635? it works on y550.