yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] zelendel:
Yes i'm still sending it in.. the phone will only charge when turned off ..keep seeing the USB Host Mode error message too.. i'm beginning to see that it's a very common issue with the M7

Thanks again, i'll let the thread die out[/QUOTE]

I will close it but you will most likely find that if you had to change it then it is most likely a knock off device and when you take it to the repair center they wont touch it.
[LG Optimus G Pro] khurrambhatti:
I brought Korean LG G Pro F240S. I noted its IMEI number, written on the sticker on the back of the battery and verify it with System's IMEI (from Phone Information) and found that both are different :eek:

IMEI on the Sticker start from 35503xxx

IMEI from System start from 0135200xxx

Please somebody tell me is there something wrong with my mobile, or it is a usual case with others too .. :confused: ?????

By the way 0135200xxx is AT&T IMEI number. Where as it is a Korean set.
[LG Optimus G Pro] khan.orak:
Did you buy a used phone? If so, it might have been stolen and then the IMEI must have been changed by the thief.
[LG Optimus G Pro] khurrambhatti:
Used :eek:

What should I do now...... Revert to the original imei(if possible) OR use at&t e980 Rom OR use F240S Rom
[LG Optimus G Pro] khan.orak:
Continue using this one. It's not your fault that you got this changed IMEI but be careful in future. Never buy phones without box and match IMEIs. These phones get blocked with stock IMEI as they are reported to authorities.

Edit: Your phone is 240S. You should use 240S ROMs.
[LG Optimus G Pro] khurrambhatti:
Thanks Khan....
[Nexus 5 Q&A, Help & Troubleshooting] basavel:
Hi guys,

After flashing LP update 5.1 I`m in trouble with my 32GB Nexus 5 :(

I got the error msg " E: can`t mount / cache " ( the same for system e.t.c). (before I did this I was on Custom ROM with Exposed framework installed.)

So I tryed to re-flash LP factory img (LMY47D) using fastboot command (via ADB SDK platform-tools) manually one by one according guides I found on xda.

I did it many times but the result was still the same - appears just green "android man" with rotating cube (10-15 min) and than it reboots itself and starts over again.

So I tryed to flash older factory image the same way (KTU48P) and I succeed to boot my phone but instead of 32 GB (normally available ~26GB) of my storage space there is only 12GB available now.

I thing there iscorupted partition but don`t know what to do next :crying::( - how to restore it or format it ???

When I try to do that via Recovery I cant mount those partitions so I can`t format them...

When I did it via SDK - fastboot erase user data it takes veeery long time with no result :(

Could you pls help me how to format whole storage space ( all partitions ) and return back to stock rom with full 32GB space available ???

Thanks
[Nexus 5 Q&A, Help & Troubleshooting] shoeseat:
Have you tried this guide http://xdaforums.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

There is a "32 GB phone now shows 16GB?" section.
[Nexus 5 Q&A, Help & Troubleshooting] basavel:
Yes, that was one of the first think I tried.

--> I can`t clear cache & factory reset via stock recovery. Error msg -- "E: Unable to mount `/cache` "

--> Unfortunatelly fastboot erase userdata stucked ( it takes aleady 2 hours it started to erase the data and format the partition ) - do you thing it can freeze or it just can`t mount the data so it`s in loop ?

Any othe idea please , please ?
[Nexus 5 Q&A, Help & Troubleshooting] shoeseat:
Have u tried to unmount cache partition from recovery?
[Nexus 5 Q&A, Help & Troubleshooting] basavel:
I can`t unmount it because it`s not mounted ...

When I tried to Wipe cache partition these errors appears :

E: Can`t mount /cache/recovery/log
E: Can`t open /cache/recovery/log
E: Can`t mount /cache/recovery/last_log
E: Can`t open /cache/recovery/last_log
E: Can`t mount /cache/recovery/last_install
E: Can`t open /cache/recovery/last_install
E: Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc
(I/O error)

:(
[Nexus 5 Q&A, Help & Troubleshooting] joegestes:
Did you try

fastboot erase cache

fastboot flash cache cache.img

fastboot erase system

fastboot flash system system.img
[Nexus 5 Q&A, Help & Troubleshooting] basavel:
Yes

fastboot erase/flash system was OK, but fastboot erase/flash cache got stucked

So after 2.5 hrs witnout any results I unplug the cord and start over again -- the same results :(
[Nexus 5 Q&A, Help & Troubleshooting] joegestes:
Maybe this will help

http://xdaforums.com/google-nexus-5/general/howto-repairing-corrupted-data-partition-t2577447

---------- Post added at 09:04 AM ---------- Previous post was at 08:47 AM ----------

Did you Wipe data/factory data reset after successful flash?

That will probably fix your 32=16 problem.
[Nexus 5 Q&A, Help & Troubleshooting] basavel:
I tryed this tutorial :

http://xdaforums.com/showthread.php?t=1284196

Thanks God it`s not "fried".

So I tryed this

mke2fs /dev/block/mmcblk0p27

(than reboot recovery)

... but still the same result :(

Than I tried to start over again from stock img flashing so :

fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system

fastboot flash bootloader
fastboot reboot-bootloader

fastboot flash radio
fastboot reboot-bootloader

fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase userdata
fastboot flash userdata userdata.img

... it got stucked on erasing user data :( so I had to unplug the cord, restart bootloader

When I re-start the device appears "swireling" dodts (the boot animation) but no step forward, still booting....

When I tried to boot in recovery - dead android with red "!" appeared

Any other ideas what to do esle ?

Should I flash CWM or TWRP rec. instead ??

How this can be fixed ??

PLEASE !!!!:crying::crying::crying:
[Nexus 5 Q&A, Help & Troubleshooting] joegestes:
If you are getting an android sign with a red triangle it is normal for stock recovery.

You must tap volume up/down and the power button all together to get to the recovery menu.

Don't hold them in. Just tap all together at the same time and let go. It takes a couple tries but it works.

You'll then get a menu that will let you wipe data/factory reset.

use volume up/down to scroll to "wipe data/factory reset" then power button to select.

looks something like this

try it and reply back the result.
[Nexus 5 Q&A, Help & Troubleshooting] basavel:
Thanks man, I manage to boot under recovery mode.

After wipe data/factory reset system shows msg:

-- Wiping data...
Formating /data ...
E: failed to mount /cache (invalid argument)
Formating /cache ...
E: failed to mount /cache (invalid argument)
E: Can`t mount /cache/recovery/log
E: Can`t open /cache/recovery/log
E: failed to mount /cache (invalid argument)
E: Can`t mount /cache/recovery/last_log
E: Can`t open /cache/recovery/last_log
E: failed to mount /cache (invalid argument)
E: Can`t mount /cache/recovery/last_install
E: Can`t open /cache/recovery/last_install
Data wipe complete

So I tried to wipe cache as well and it shows up this:

-- Wiping cache...
Formating /data ...
E: failed to mount /cache (invalid argument)
Formating /cache ...
E: failed to mount /cache (invalid argument)
E: Can`t mount /cache/recovery/log
E: Can`t open /cache/recovery/log
E: failed to mount /cache (invalid argument)
E: Can`t mount /cache/recovery/last_log
E: Can`t open /cache/recovery/last_log
E: failed to mount /cache (invalid argument)
E: Can`t mount /cache/recovery/last_install
E: Can`t open /cache/recovery/last_install
E: Failed closing /dev/block/platform/msm_sdcc.1/by-name/mis
(I/O error)
E: failed to mount /cache (invalid argument)

I have no clue how to fix this :( can you help me pls ??
[Nexus 5 Q&A, Help & Troubleshooting] joegestes:
I would go to fatsboot and try to erase partitions and re flash again. see what happens.

If your data partition fails again we can try adb shell to repair your data partition.
[Nexus 5 Q&A, Help & Troubleshooting] basavel:
I tried but again got stucked on erasing userdata...

I start research again and search for solution around partitions and I found this ( exactly my problem)

http://androidforums.com/threads/unable-to-mount-cache-while-doing-factory-reset.901188/

and solution for this was posted here on xda

http://xdaforums.com/google-nexus-5/help/lost-cache-partition-fixed-t2949752#post58720690

this link helps me to get back to 32GB storage space (in fact ~ 26GB but doesn`t matter)

[The problem was exactlly the same missing EXT2 partition on cache partition (27)]

But error msg Can`t mount `/cache` still appears :( So I was not able to flash stock img LP 5.1 but I manage to flash 4.4.4 KTU84Q

It boots us and works like charm, but... ... still can`t mount/erase cache so it`s not fully solved yet but at least I can switch on/off the system now.

Can U pls help me with this mounting / partition problem ???

can it be fixed by stock OTA from KTU84Q to 5.0.1 and than the same to 5.1 ?
[Nexus 5 Q&A, Help & Troubleshooting] gefilus:
I had like 2 years ago similar problem with htc sensation but i fixed it by formating ir with ext2 and the reformated catch with ext4. Try to find something inside sensation forume
[Nexus 5 Q&A, Help & Troubleshooting] joegestes:
Ok. So you are now successfully running 4.4.4 KTU84Q.

What happens now if you try flashing the stock cache.img of 4.4.4 KTU84Q:

fastboot erase cache

fastboot flash cache cache.img

Also, you could try and see what happens if you flash LP 5.01 lrx22c instead of 5.1 and do factory reset immediately after flash.
[Nexus 5 Q&A, Help & Troubleshooting] basavel:
Even I manage to boot under KTU84Q the partition is still "lost" - means internal storage is ~26GB thats OK; but the error msg E: Can`t mount /cache bla bla bla still stays.

Actually I have these partitions :

C:\android-sdk-windows\platform-tools>adb shell parted -s /dev/block/mmcblk0 pri
nt
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Model: MMC SEM32G (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB ext2 fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 1267MB 1074MB ext4 system
26 1267MB 1298MB 31.5MB crypto
27 1298MB 2032MB 734MB cache
28 2032MB 31.3GB 29.2GB ext4 userdata
29 31.3GB 31.3GB 5632B grow

So after I run this

1.1) adb shell

1.2) mkfs.ext2 /dev/block/mmcblk0p27

1.3) exit

It formats the cache partition (p27) to ext2 but after install of stock KTU84Q it`s back - UNFORMATED :( with no possibility to mount

What am I doing wrong ? :( :crying:
[Nexus 5 Q&A, Help & Troubleshooting] joegestes:
My guess is it needs to be formatted to ext4 not ext2.

KTU84Q probably can not recognize ext2.

Heres what mine looks like.

Number Start End Size File system Name Flags

1 524kB 67.6MB 67.1MB fat16 modem

2 67.6MB 68.7MB 1049kB sbl1

3 68.7MB 69.2MB 524kB rpm

4 69.2MB 69.7MB 524kB tz

5 69.7MB 70.3MB 524kB sdi

6 70.3MB 70.8MB 524kB aboot

7 70.8MB 72.9MB 2097kB pad

8 72.9MB 73.9MB 1049kB sbl1b

9 73.9MB 74.4MB 524kB tzb

10 74.4MB 75.0MB 524kB rpmb

11 75.0MB 75.5MB 524kB abootb

12 75.5MB 78.6MB 3146kB modemst1

13 78.6MB 81.8MB 3146kB modemst2

14 81.8MB 82.3MB 524kB metadata

15 82.3MB 99.1MB 16.8MB misc

16 99.1MB 116MB 16.8MB ext4 persist

17 116MB 119MB 3146kB imgdata

18 119MB 142MB 23.1MB laf

19 142MB 165MB 23.1MB boot

20 165MB 188MB 23.1MB recovery

21 188MB 191MB 3146kB fsg

22 191MB 192MB 524kB fsc

23 192MB 192MB 524kB ssd

24 192MB 193MB 524kB DDR

25 193MB 1267MB 1074MB ext4 system

26 1267MB 1298MB 31.5MB crypto

27 1298MB 2032MB 734MB ext4 cache

28 2032MB 31.3GB 29.2GB ext4 userdata

29 31.3GB 31.3GB 5632B grow

Again it looks like cache should be formatted ext4

Compare line 22 and line 27.

My line22 fsc is not formatted. Yours is formatted ext2

My line 27 cache is formatted ext4. Yours is not.

That is the problem.

Here is the list of partition locations

[/code]

179 0 30535680 mmcblk0

179 1 65536 mmcblk0p1

179 2 1024 mmcblk0p2

179 3 512 mmcblk0p3

179 4 512 mmcblk0p4

179 5 512 mmcblk0p5

179 6 512 mmcblk0p6

179 7 2048 mmcblk0p7

179 8 1024 mmcblk0p8

179 9 512 mmcblk0p9

179 10 512 mmcblk0p10

179 11 512 mmcblk0p11

179 12 3072 mmcblk0p12

179 13 3072 mmcblk0p13

179 14 512 mmcblk0p14

179 15 16384 mmcblk0p15

179 16 16384 mmcblk0p16

179 17 3072 mmcblk0p17

179 18 22528 mmcblk0p18

179 19 22528 mmcblk0p19

179 20 22528 mmcblk0p20

179 21 3072 mmcblk0p21

179 22 512 mmcblk0p22

179 23 512 mmcblk0p23

179 24 512 mmcblk0p24

179 25 1048576 mmcblk0p25

179 26 30720 mmcblk0p26

179 27 716800 mmcblk0p27

179 28 28551146 mmcblk0p28

179 29 5 mmcblk0p29

179 32 4096 mmcblk0rpmb

~ #

[/code]
[Nexus 5 Q&A, Help & Troubleshooting] basavel:
Finally I got to the stage where the ext2 partition stays ( do not disappear) after next flash.

How I did it - format the partition to ext2 than manually flash KTU84Q

fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img

Than let the system update itself to 5.0.1 LRX22C

Now the erroe msg is gone (E: Can`t mount /cache) but agree those messed up partitions must be fixed.

The question is how ?

- should I install TWRP rec. and let it fix it when the cache partition is mountable now ?

- or should it fix it via ADB SHELL ? (and how ? mkfs.ext4 /dev/block/mmcblk0p27 ? )

- and how to erase line 22 in order to have in unformated ?

--- > or should I try to flash custom ROM over this ? - I don`t think so:rolleyes:

Could you pls help with this ?

!!!THANKS!!!
[Nexus 5 Q&A, Help & Troubleshooting] joegestes:
If it was me, the

first

thing I would do is flash TWRP. Second, make a full backup using TWRP backup function, then save/transfer a copy of that backup to my PC.

That way, moving forward id' have an easy way to restore the device back to it's presently functioning Lollypop state.

After that I might try the ADB shell command from TWRP you mentioned mkfs.ext4 /dev/block/mmcblk0p27 and see if that manages to re formats cache to ext4.

I've never tried this, and don't have much experience with parted, so I cant say if it will work. So proceed at your own risk.

As far as fsc( I think it means file save clean)partition goes. I honestly don't know but Ill try to find out.

Meanwhile, hopefully someone else with some mad partition skillz will chime in.:laugh:
[Nexus 5 Q&A, Help & Troubleshooting] basavel:
TWRP coruupted all I did before - it tryed to repair broken partitions with f2fs but they are gone :( now

So I am 2 steps back

C:\android-sdk-windows\platform-tools>adb shell parted -s /dev/block/mmcblk0 pri
nt
Model: MMC SEM32G (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB ext2 fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 1267MB 1074MB ext4 system
26 1267MB 1298MB 31.5MB crypto
27 1298MB 2032MB 734MB cache
28 2032MB 31.3GB 29.2GB ext4 userdata
29 31.3GB 31.3GB 5632B grow

I can create only ext2 partition thanks to - mkfs.ext2 /dev/block/mmcblk0p27

The same code string with ext4 i.o ext2 is not working

MSG:

~ # mkfs.ext4 /dev/block/mmcblk0p27

mkfs.ext4 /dev/block/mmcblk0p27

/sbin/sh: mkfs.ext4: not found

:(:(:(
[Nexus 5 Q&A, Help & Troubleshooting] joegestes:
[/COLOR]

Simply flashing TWRP made your phone unusable and corrupted ? (I think NO)

Were you able to boot into TWRP recovery after you flashed it?

Did you make a backup

before

trying ti fix anything?

Why would you use f2fs? It is a completely different file system!
[Nexus 5 Q&A, Help & Troubleshooting] joegestes:
Look here

http://xdaforums.com/android/apps-games/app-uapm-universal-android-partition-t2976587
[Nexus 5 Q&A, Help & Troubleshooting] basavel:
The install of TWRP and booting into TWRP is OK.

But immediatelly when I start back up, system is automatically trying to mount cache - and error msg appears (E: Unable to mount / cache)

Will try the app what you posted in your last post and let you know ;)

BIG THANKS FOR YOUR PATIENCE AND HELP !!!
[Nexus 5 Q&A, Help & Troubleshooting] joegestes:
No problem. But not sure I helped much.

Maybe read this thread, it might help

http://xdaforums.com/google-nexus-5/help/help-nexus-5-bricked-clearing-cache-t2564509

---------- Post added at 04:42 PM ---------- Previous post was at 04:01 PM ----------

Also this might work to get your partition format back to ext4

https://play.google.com/store/apps/details?id=ext.recovery.control
[Galaxy Note 3 Q&A, Help & Troubleshooting] jd_allys:
I recently purchased NOTE 3 32 GB LTE from Qatar. Its having Hongkong firmware n9005zhuenf1 4.4.2

I want to flash it with N9005XXUGNJ2_N9005OJVGNH2_XSI. Is it possible? When I am trying it with Odin. Its getting failed.Pls check the attachment it will show about phone details.

I want to root my device too please help

Thanks Buddies

Is there any Android 5.0 firmware fully functional for my device?
[Xolo Q1010i] QA Bot:
Q&A for [TUTORIAL] Unbrick xolo Q1010i

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [TUTORIAL] Unbrick xolo Q1010i. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Xolo Q1010i] pratikghawade:
Phone not detected

Firstly, having issue with the driver auto installer. When I double-click install.bat, do not support win NT earlier version appears in the cmd prompt.

Secondly, my pc is not able to detect my phone.

Is there any way to unbrick a hard bricked q1010i? Please suggest ASAP.:(
[Xolo Q1010i] nrkumar93:
Phone Hard bricked by CHAINFIRE

I got an 89MB OTA update for Xolo Q1010i. I didn't remember that I had previously installed Chainfire App.

My phone got bricked and started bootlooping getting stuck at XOLO logo. Even though I installed working drivers for windows my phone gets switched on and starts bootlooping once I connect it to PC. The device disappears within seconds from Device manager before I could take any action from SP Tools.

I also tried sideloading using adb and it returns installation aborted after sideloading Stock ROM. Also I am not able to go into adb shell as it returns error:closed. I have only stock recovery installed.

Please help. I can PAYPAL anyone who gives working solution :D
[Xolo Q1010i] nishantgupta107:
i would suggest to charge your phone for about 2-4 hrs and then try switching it on....

if xolo logo displays or anything on the screen...

go for a clean pc with not a single mobile driver installed (or uninstall every single one of em whichever suits you).

install the necessary drivers and then try flashing the stock rom jb/kk (your choice).

if your phone doesn't switch on or no display change...then if your phone is under warranty..play dumb and give to service center else...try it after some day...that's all i can help.
[Xolo Q1010i] nrkumar93:
No it is not under warranty.. :( I will try doing your method. But I dont understand what difference it makes.
[Xolo Q1010i] nishantgupta107:
worked for me...thought might work for you too.
[Xolo Q1010i] vatsaluniyal:
clicking on isntall.bat it is showing do not support win NT earlier system please help. I'm currently using windows 8.1

---------- Post added at 10:38 AM ---------- Previous post was at 10:26 AM ----------

clicking on isntall.bat it is showing do not support win NT earlier system please help. I'm currently using windows 8.1
[Xolo Q1010i] bruce14357:
Phone inst even recognizing device i have all driver installed
[Xolo Q1010i] irfanhrr:
How can flash stock rom via twrp?

Any flashble stock zip here-??
[Android One (First-Generation) Cross-Device Genera] vyshnav raj:
Official Lollipop Back up from Karbon Sparkle V for Indian users​

PREREQUISITES

Unlocked Bootloader

Rooted Stock Rom (optional)

Philz touch recovery

Stock 4.4.4

ANDROID ONE(any)

PROCEDURE

Create folder clockworkmod/backup inside ext sdcard

Extract the downloaded zip(The required files are inside[2015-03-11.18.37.43_LMY47I]this folder ).

Boot into recovery and do a full wipe,go to backup and restore.

Scroll down and select misc nandroid backup settings and uncheck md5 check sum .

Then go back then select custom restore from external sdcard in backup and restore option.

Uncheck all options select only system and boot.img.

Now select start now and click boot.img.

Process will start wait for it to complete.

&

Now reboot to system.

Taste the Lollipop in your androidone device.

Downloads​

Stock 5.1 (indian)​

ENJOY

Bugs​

Dialer Animation (lag)

SCREENSHOT​

Press thanks if i helped.

Thanks prspuri9 for the file,awsome job man.
[Android One (First-Generation) Cross-Device Genera] Avijitmodi:
Is the official update available for micromax canvas a1?

Can i check and install the update via my carrier network?I have good 3g data connection...
[Android One (First-Generation) Cross-Device Genera] Dynaguy:
clockworkmod/backup showing no files found
[Android One (First-Generation) Cross-Device Genera] vyshnav raj:
When i contacted androidone customer care they said that all androidone devices will be updated on or before 23rd march.:good:
[Android One (First-Generation) Cross-Device Genera] vyshnav raj:
You should extract the rar file to clockworkmod/backup.
[Android One (First-Generation) Cross-Device Genera] Dynaguy:
first i extracted and copied the folder to backup, is that ok?
[Android One (First-Generation) Cross-Device Genera] itsmuhammedmuneer:
Have u got official OTA? When? Which was your google play services version before update to lollipop..? Also post some screenshot too...

Thanks in advance
[Android One (First-Generation) Cross-Device Genera] Avijitmodi:
Should i restore the backup using philz recovery?
[Android One (First-Generation) Cross-Device Genera] poush:
Working fine till now

Working fine till now
[Android One (First-Generation) Cross-Device Genera] rahuld324:
fake

i think its not official update from google..may be its indonesian or phillipines one
[Android One (First-Generation) Cross-Device Genera] itsmuhammedmuneer:
Have u installed the uploaded rom above? any problem with camera flash?