Related
Hi all,
Since Sunday I try to solve the hard brick of my Moto G XT1032. I was on a rom GPE in 4.4.4 (EU) and by making the MAJ Lollipop during the sunday, the tel reboot on the logo Motorola and nothing more.
I tested severals tutos on XDA and many french websites, as:
Http: // forum.xda-developers.com / showthread.php? T=2633272
http: // forum.xda-developers.com/moto-g/help/mo to-g-hard-brick-lollipop-t2998124
And a lot of the others...but nothing!
Well, I said myself it doesn't matter because mototool repair the tel with no problems, as usual. But not, many errors when I try of downgrade in 4.4.2 or in 4.4.4 with it. I tried to flash (cache/ system / data / Dalvik) with CWM and TWRP with one tens of versions all in all and impossible to make no anything to put back. I tried to install many rom's, always the same.
I have errors as " remote failure ", impossible of mount the partitions system/cache, hab check failed and more more more, i don't remember the other's errors...
I cannot copy files (like a rom) via ADB to the tel in mode bootloader and I don't know what to do anymore of the whole...
If you have an idea, I am interested because there I think that except the SAV ... i'am in bull***t. :silly:
Thanks to all of your help and good week!
(sorry for my poor english)
Try manually flashing a stock 4.4.4 ROM , not a 4.4.2 ROM, for your phone. You may not be able to flash motoboot if the bootloader on your phone is newer than the bootloader you are trying to flash.
audit13 said:
Try manually flashing a stock 4.4.4 ROM , not a 4.4.2 ROM, for your phone. You may not be able to flash motoboot if the bootloader on your phone is newer than the bootloader you are trying to flash.
Click to expand...
Click to collapse
I try but the problem it's adb, because it's impossible to synchronize my phone with it.
When i try "adb reboot-bootloader" in a shell, i have the error "device not found".
And it's impossible to continue the tutorial :
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
What is the solution for this?
adb reboot bootloader works if your phone is booted and you have debugging enabled.
ADB commands don't work when the phone is in fastboot mode.
Put your phone into fastboot mode, connect it to your computer, type in "fastboot devices" and your's phone serial # should appear on screen.
audit13 said:
adb reboot bootloader works if your phone is booted and you have debugging enabled.
ADB commands don't work when the phone is in fastboot mode.
Put your phone into fastboot mode, connect it to your computer, type in "fastboot devices" and your's phone serial # should appear on screen.
Click to expand...
Click to collapse
OK. I have a phone serial who appear on screen (with the command "fastboot devices"), but with the command "adb devices", i have no serial, so no devices attached...
EDIT : Into TWRP Recovery, i have the adb serial too
ok, now it's good I the phone turn on a retail rom 4.4.4.
For all those who have experienced the problem (a GPE 4.4.2 update to 4.4.4 and 5.0.1), the procedure is "simple".
Install adb+fastboot and copy the rom into the folder.
Fisrt, put your phone into bootloader mode and check the command 'fastboot devices"; you must have a serial into the shell. Boot on the TWRP recovery (2.7.1.1) and type the command into the shell "adb devices"; again, you must have a serial. If it's OK, format cache/system/data/dalvik and reboot the phone into the bootloader.
In my case, i use the rom RETAIL-FR_4.4.4 OTA.
Code:
fastboot flash partition gpt.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot erase cache
fastboot erase userdata
fastboot reboot
IF this does not work , it is still possible to achieve a different manipulation .
Take CWM recovery (Philz Touch for example) and try to push a rom with adb.
@+
You can't use adb commands when the phone is in fastboot mode. THis is why adb devices returns nothing.
Glad you got it working.
Hi all.
If you are here, then you have likely experienced issues with custom ROMs not detecting SIM, or you are still experiencing this issue.
I have a XT1562 UK Single-SIM model and have had this problem with EVERY ROM I have tried and it was getting so frustrating.
Over the last few weeks, I have flashed custom ROMs based on CM13 and all have presented the SIM not detected issue. A simple fix was to pop-out the SIM module and reinsert - more often than never, the SIM was detected. Then I would restart (as is often the case with a custom setup) and alas, the SIM was not detectable.
After trying various suggestions from developers, nothing was working until I happened to flash a dualSIM firmware and I haven't looked back. I can now flash EVERY CM13-based ROM with successful SIM detection BUT it takes a few extra steps to get to that stage.
Here are the things you need:
This firmware
This fix
A custom ROM of your choice (Highly recommend crDroid or Temasek)
GAPPS of your choice - I would recommend this
TWRP
Okay - the solution (confirmed working and reliable):
1. Unpack the Firmware into it's own folder
2. Copy across the files to Fastboot folder
3. Restart phone into bootloader (power off first then hold power and volume down)
4. In the Fastboot folder hold shift and right click.
5. Select "open command window here"
6. Connect phone via USB to computer and in command window enter the following commands 1 by 1 making sure "[okay]" is displayed each time:
if nothing happens on screen, then simply use your volume keys on the phone to restart the bootloader
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
7. Once completed restart phone and setup as normal.
8. When setup is complete, restart phone into bootloader.
9. Flash TWRP
10. Restart phone into recovery
11. in TWRP, factory reset then flash ROM and GAPPS and DualSIMFix
12. Restart phone and setup. If SIM shows not detected, press "skip" and it should detect after WiFi setup.
Voila! You can now confidently flash ANY CM13-based custom ROM with the added assurance of SIM detection. IF, however, you flash a ROM and SIM is NOT detected, then simply reflash the DualSIMFix.
If this solution works for you, please give credit where it's due - thank me using the thumbs-up icon below AND vote in the poll at the head of this thread
So, you want to say, that i need to flash stock DS ROM
and after that i'll can flash any custom CM13 based ROM and SIM will be detected?
perfectsense72 said:
So, you want to say, that i need to flash stock DS ROM
and after that i'll can flash any custom CM13 based ROM and SIM will be detected?
Click to expand...
Click to collapse
It has worked for me and I have tried everything that has been recommended. Just by determined trial-and-error I have found my solution.
Just to reiterate
and my intention is to generate enough interest to further assist developers of the CM13 custom ROMs.
Click to expand...
Click to collapse
Can you write a sequence of actions? What nuances?
perfectsense72 said:
Can you write a sequence of actions? What nuances?
Click to expand...
Click to collapse
I fastboot flashed XT1562_LUX_RETASIA_DS_6.0_MPD24.65-18.1 (here ); flashed ROM; flashed GAPPS and then flashed DualSIMFix (from here)
I've tested reboots and SIM is detected each time.
I am assuming you know how to flash a stock image - if not let me know.
I am assuming you know how to flash a stock image - if not let me know
Click to expand...
Click to collapse
From PC by fastboot in stock recovery mode, right?
Did you perform any wipe between flashing stocj ROM and flashing CM13 based ROM?
perfectsense72 said:
From PC by fastboot in stock recovery mode, right?
Did you perform any wipe between flashing stocj ROM and flashing CM13 based ROM?
Click to expand...
Click to collapse
Follow this:
1. Unpack the Firmware into it's own folder
2. Copy across the files to Fastboot folder
3. Restart phone into bootloader (power off first then hold power and volume down)
4. In the Fastboot folder hold shift and right click.
5. Select "open command window here"
6. Connect phone via USB to computer and in command window enter the following commands 1 by 1 making sure "[okay]" is displayed each time:
if nothing happens on screen, then simply use your volume keys on the phone to restart the bootloader
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
7. Once completed restart phone and setup as normal.
8. When setup is complete, restart phone into bootloader.
9. Flash TWRP
10. Restart phone into recovery
11. in TWRP, factory reset then flash ROM and GAPPS and DualSIMFix
12. Restart phone and setup. If SIM shows not detected, press "skip" and it should detect after WiFi setup.
13. Enjoy - but please let me know if not quite right.
@perfectsense72 - once you are able to confirm fully working, then I'll amend the OP to reflect necessary details for successful detection, etc. Thanks for trying this.
Thank you, i'll try tomorrow.
I can't confirm your problems with single sim modem.
I have german single sim and had problems after flashing french dual sim stock image and then flash cm13 roms.
Sometimes the boot was fine with detected sim and sometimes without detected sim and with random reboots of the device.
After flashing back a single sim stock and completly boot the stock then flash again crdroid no problems appeared again. All fine with detected sim on every boot.
For now I'm using Pac-ROM (LP) and have no problem, I'll try CrDroid soon and I'll let you know.
Jeso said:
Sometimes the boot was fine with detected sim and sometimes without detected sim and with random reboots of the device.
Click to expand...
Click to collapse
This is what I'm aiming to avoid for those with issues such as this. Every firmware flash produced an error on flashing bootloader. The only one to not present me with the error is the 18.1 DS retasia.
This has, I believe, been the key to my issues as well as other users. I can flash any official firmware and use it perfectly well, it's just the custom MM ROMs that are problematic.
moozer said:
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Does it lock the bootloader?
(Sorry for noob question)
axxx007xxxz said:
Does it lock the bootloader?
(Sorry for noob question)
Click to expand...
Click to collapse
No - this just re-introduces the stock bootloader for the firmware
So, it's working. Flash Unoficial CM13 after stock DS asian and no problem, both simcards a detected.
Thanks, moozer.
perfectsense72 said:
So, it's working. Flash Unoficial CM13 after stock DS asian and no problem, both simcards a detected.
Thanks, moozer.
Click to expand...
Click to collapse
You're welcome. Checked rebooting the phone? SIM remains?
You can now flash custom ROMs to your heart's content. No need to fart around with firmware flashes. All that you need to check is SIM detection on setup and if necessary flash the SIMfix.
^^
Yes, SIM remains after reboot, everything is OK
Thanks a lot! Worked perfectly for me aswell. Currently running ResurrectionRemix and I've had no problems with the sim card since.
Hi, this is my first time making a post, ok here's the thing, a couple of days ago my phone run out of battery, when i come back to charge the phone, this just get stuck in the Motorola logo and don´t turn on, i never make nothing like root or flashing roms, the phone os was all stock Android 5.1; so i look in the internet for possible cause and i find that it was a bootloop, i try to get in to the fastboot flash mode to make a reset with the factory option but just get directly to the motorola logo and dont do nothing, so a try with the recovery option and gets in to the android system recovery <3e> and try the wipe data/factory reset but doesn´t work. I try even via computer using the minimal adb and fastboot to erase the cache and the userdata with the commands and doesn't work, still appearing the motorola logo. so i found that i have to install the original rom again but first ill have to unlock the bootloader for my device, so i did it, i unlock the bootloader and now appear <Device is UNLOCKED. Status Code: 3> and now appear the poster WARNING BOOTLOADER UNLOCKED instead of the motorola logo; then i search for the stock rom for my device and i find this one XT1040_PEREGRINE_RETBR_5.1_LPB23.13-8_cid12_CFC.xml.zip (i know that my device is peregrine because i remember saw it before in the settings but not remeber the hole name), so i make the installation with adb tools like the post say and make this commands:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
when its over i press fastboot reboot, but then appears again the WARNING BOOTLOADER UNLOCKED poster, i try to make it again, bus still appearing, i try more than 10 times, but still appearing.
sorry if the post is too large but i try to explain everything so you guys can help me because im desesperate with this, thanks.
HanSolo97 said:
Hi, this is my first time making a post, ok here's the thing, a couple of days ago my phone run out of battery, when i come back to charge the phone, this just get stuck in the Motorola logo and don´t turn on, i never make nothing like root or flashing roms, the phone os was all stock Android 5.1; so i look in the internet for possible cause and i find that it was a bootloop, i try to get in to the fastboot flash mode to make a reset with the factory option but just get directly to the motorola logo and dont do nothing, so a try with the recovery option and gets in to the android system recovery <3e> and try the wipe data/factory reset but doesn´t work. I try even via computer using the minimal adb and fastboot to erase the cache and the userdata with the commands and doesn't work, still appearing the motorola logo. so i found that i have to install the original rom again but first ill have to unlock the bootloader for my device, so i did it, i unlock the bootloader and now appear <Device is UNLOCKED. Status Code: 3> and now appear the poster WARNING BOOTLOADER UNLOCKED instead of the motorola logo; then i search for the stock rom for my device and i find this one XT1040_PEREGRINE_RETBR_5.1_LPB23.13-8_cid12_CFC.xml.zip (i know that my device is peregrine because i remember saw it before in the settings but not remeber the hole name), so i make the installation with adb tools like the post say and make this commands:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
when its over i press fastboot reboot, but then appears again the WARNING BOOTLOADER UNLOCKED poster, i try to make it again, bus still appearing, i try more than 10 times, but still appearing.
sorry if the post is too large but i try to explain everything so you guys can help me because im desesperate with this, thanks.
Click to expand...
Click to collapse
If your goal is to re-lock the bootloader: try the command: fastboot oem lock
However, I don't see that solving your problem and may compromise your ability to restore to stock. Instead check this link and follow the install directions EXACTLY:
http://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
eg. for Canada choose: XT1040 (Note: for Rogers/Fido - confirmed)
Retail Canada 5.1 ROM (Untouched) (531mb) [Download]
i.e., you want the untouched version for your specific region.
Good luck. S
This started happening since today morning. The phone doesn't charge or get detected when connecting to a computer.
I tried wiping everything and clean installing different roms and kernels, but nothing helped.
For some reason, the phone is charging when in the Bootloader screen though. What should I do?
Windows 10? Install this
Huh?
Let me clarify, it was working properly until last night, and I have Windows 10.
I'm currently forced to charge using the bootloader screen as the phone refuses to charge otherwise - not while fully switched off, and also not when switched on.
The computer and the phone don't even detect that anything is connected when I plug in the USB. (The cable is okay, I'm using the same cable to charge my phone on the bootloader screen)
Wait... It charges in the bootloader (or while off I assume) but not when booted into the OS? Is this device stock? What have you tried, wipe cache, factory reset, etc?
Sent from my MotoG3 using Tapatalk
acejavelin said:
Wait... It charges in the bootloader (or while off I assume) but not when booted into the OS? Is this device stock? What have you tried, wipe cache, factory reset, etc?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
No it's not stock.
I've tried everything. Full wipe and flashed various roms and kernels. No avail. :/
Check for lint build up in the plug on the phone and try a different cable... I know it sounds wrong but once the phone is booted it does some simple communication to the source, that may not be working.
Sent from my MotoG3 using Tapatalk
I forgot to mention something.
The battery icon in the notification bar is permanently stuck showing charging even though the phone actually isn't being charged (and the battery screen in Settings also show 'Not charging').
acejavelin said:
Check for lint build up in the plug on the phone and try a different cable... I know it sounds wrong but once the phone is booted it does some simple communication to the source, that may not be working.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
This didn't work, sorry.
So, it only seems to charge when connected the PC in bootloader mode. It doesn't charge otherwise - not with any charger, and not while being switched on. wth.
Nvm, I'll try removing the lint.
FalKoopa said:
No it's not stock.
I've tried everything. Full wipe and flashed various roms and kernels. No avail. :/
Click to expand...
Click to collapse
Did you try to install stock rom or only custom roms?
Acetyloaceton said:
Did you try to install stock rom or only custom roms?
Click to expand...
Click to collapse
Only custom roms. I'm admittedly a bit scared to try installing the stock rom as it might get bricked.
EDIT: Btw, cleaning it didn't work. I suppose I have no option but to give it for repairs.
If I were you, I would try to do this. Dont be scared. If you have the newest marshmallow partition and bootloader then flash factory images without these two. You can also skip logo if you want to keep disabled unlocked bootloader information.
fastboot oem fb_mode_set
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Wait 5-10 minutes and done
Acetyloaceton said:
If I were you, I would try to do this. Dont be scared. If you have the newest marshmallow partition and bootloader then flash factory images without these two. You can also skip logo if you want to keep disabled unlocked bootloader information.
fastboot oem fb_mode_set
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Wait 5-10 minutes and done
Click to expand...
Click to collapse
Where will I get these files?
Here you go
And if I remember correctly you have an xt1550 right? I have flashed factory image of 6.0.1 with no problems on my xt1550, just to assure.
Check in device manager & devices and printers, if something pops up when phone is connected in bootloader mode. If a device with yellow triangle shows up, you can install drivers (pointing to driver inf file) to and subsequently fastboot flash stock.
Broadcasted from Zeta Reticuli
I think if you flash partition and bootloader then it also should work. Brick issue only appears when you are trying to do downgrade from marshmallow to lollipop and you flash older partition (you should always have the newest one).
Gravemind2015 said:
And if I remember correctly you have an xt1550 right? I have flashed factory image of 6.0.1 with no problems on my xt1550, just to assure.
Check in device manager & devices and printers, if something pops up when phone is connected in bootloader mode. If a device with yellow triangle shows up, you can install drivers (pointing to driver inf file) to and subsequently fastboot flash stock.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Alright. I'm going to flash it then. Downloading it will take a while...
I don't remember ever updating the bootloader though..
@Acetyloaceton
So, I tried to flash the stock recovery.img
I got this.....
target reported max download size of 268435456 bytes
sending 'stock' (16484 KB)...
OKAY [ 0.571s]
writing 'stock'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.598s
Nevermind, I managed to flash everything and all went well, but now the phone is in a bootloop between bootloader unlocked screen and the Erasing screen.
FalKoopa said:
Nevermind, I managed to flash everything and all went well, but now the phone is in a bootloop between bootloader unlocked screen and the Erasing screen.
Click to expand...
Click to collapse
Have you tried factory resetting via stock recovery? I mean power off>power+vol. Down>bootloader>recovery. If still can't boot then after factory resetting try flashing firmware again.
Broadcasted from Zeta Reticuli
Hi Friends I Own Lava Iris 406Q,
Someone here gave me stock firmware of my device i used to flash by device with "c230wLAVA_fastboot_flash_all.bat" file provided by him in the firmware folder in a single click. But yesterday i wrongly clicked on"EraseAll.bat" command which have following instructions;-
@ECHO on
@ECHO Please switch to fastboot mode
@ECHO If the system started, run adb reboot-bootloader
adb reboot bootloader
fastboot erase modem
fastboot erase sbl1
fastboot erase sdi
fastboot erase aboot
fastboot erase rpm
fastboot erase boot
fastboot erase tz
fastboot erase system
fastboot erase cache
fastboot erase recovery
fastboot erase splash
fastboot erase usbmsc
fastboot erase userdata
fastboot erase misc
fastboot reboot
pause"Now my device isn't vibrating on pressing the power key, not showing anything its like in a switch off state. PC and adb are not recognizing it but windows recognize it as QHSUSH_BULK only, on using QFIL am unable to flash it with error message as "unable to switch it to Emergency Download Mode".
Is the repair possible to my device by these ordinary softwares like QPST, QFIL Or Any Other Softwares ???? Or am i missing some firmware components? Can Service centres repair my device?? How much it will cost?
If someone knows how to repair the device effectively, please respond.. Or just reply with whether my device is repairable or not.
Thanks
What phone do u have ??
bsaptarsi669 said:
What phone do u have ??
Click to expand...
Click to collapse
OP said "Lava Iris 406Q"
Lava Iris 406Q - Full phone specifications
www.gsmarena.com