Develop Bugs

I accidentally wiped the system and now there is no OS installed. Am I screwed?

I was trying to install superzen but I accidentally wiped the OS. Am I screwed? Is there anything I can do, or is this looking like I bricked the phone?

http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Go there and look at section 3.2. MAKE ABSOLUTELY SURE that you grab the correct firmware for your device (WW or CN, 550 or 551). As far as I can tell, unless you made a NANDROID backup in custom recovery prior to wiping system, this would be your only way back to working order.
Are you currently unable to get back to a custom recovery? Can you not just successfully flash superzen now?

Level99 said:
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Go there and look at section 3.2. MAKE ABSOLUTELY SURE that you grab the correct firmware for your device (WW or CN, 550 or 551). As far as I can tell, unless you made a NANDROID backup in custom recovery prior to wiping system, this would be your only way back to working order.
Are you currently unable to get back to a custom recovery? Can you not just successfully flash superzen now?
Click to expand...
Click to collapse
Thanks for the reply, it seems that my computer can't recognize my phone through adb, i can get into recovery, but my phone is just not recognizable. I should mention that it was earlier, and I installed supersu with cwm tethered.
EDIT: I can't use fastboot for twrp.img, it says I don't have permission and now I can't even access recovery because I'm stuck in a bootloop.

UPDATE: Ok so fastboot recognized the phone but I do not have permission to load twrp.img

Have you got this sorted now?

timbernot said:
Have you got this sorted now?
Click to expand...
Click to collapse
no, every time I try to flash twerp with fastboot, I get this error
"writing recovery failed <remote: permission denied>"
EDIT: HOLY HELL GUYS I FIXED IT! It turns out, my usb cord didn't work for some reason, tried another one and it works fine. Doing adb sideload right now.

venom55520 said:
no, every time I try to flash twerp with fastboot, I get this error
"writing recovery failed <remote: permission denied>"
EDIT: HOLY HELL GUYS I FIXED IT! It turns out, my usb cord didn't work for some reason, tried another one and it works fine. Doing adb sideload right now.
Click to expand...
Click to collapse
YaY !:good:

Completely wiped my phone, can't get stock ROM unto it...

I wiped the internal storage on my phone by mistake and now my phone has no OS or ROM to flash it back on. I tried to sideload with TWRP but the feature wouldn't start. I flashed the stock recovery and tried to sideload it there but I get an "error: protocol fault (no status)"... I tried to mount storage on TWRP but that feature didn't seem to work on it either. It's a good thing that I still have my OnePlus One to use, but I would appreciate your help!!
Sent from my A0001 using Tapatalk

I had the same issue the first time I tried to add side load the stock rom, I tried it again and it worked. my suggestion is to try the side load again. Make sure your using the full rom zip.

k.s.deviate said:
I had the same issue the first time I tried to add side load the stock rom, I tried it again and it worked. my suggestion is to try the side load again. Make sure your using the full rom zip.
Click to expand...
Click to collapse
I tried like a thousand times on both stock and TWRP to no avail. When I reflashed TWRP and tried to sideload one last time it told me that I needed ADB version 1.0.32 which is what I should have because I installed the "15 seconds ADB Installer v1.4.3" from the stickied guide here on the OP3 forums... Anyway, I got access to the TWRP folder and the internal storage by just being in the TWRP recovery, not sure if it was always like that, but I just dragged and dropped the ROM and other flashables onto the phone... lol Maybe I was freaking out too much to notice, but why would anyone sideload anything if you could just drag and drop stuff while in TWRP and just flash? Maybe reflashing TWRP fixed something or I was using an older beta OP3 version before, I re-downloaded everything.
Sent from my A0001 using Tapatalk

I screwed up when I tried to update to 3.2.0 OOS. I were rooted so the installtion failed and I restored a corrupt backup with TWRP that resulted in a stuck boot logo.
I did this too fix this. boot into fastboot (if you still can) then make sure its connection properly. "fastboot devices". Then in your ADB folder place a TWRP.img and type "fastboot boot twrp.img" wait like 10 seconds, it will seem like it doesn't work but if you are a functional TWRP img it should boot up just fine. Select allowed modifications and then you can also access storage. There is a post on the oneplus forums where you can download signed full zips of the ROMS. download any of them. I will past in the post if I can find it later. Not home atm. Just copy the .zip onto the phone and then do a factory reset and flash the full rom and then reboot should work just fine. You don't need too flash TWRP just boot it if you still wanna keep stock recovery.

rickyx32 said:
I wiped the internal storage on my phone by mistake and now my phone has no OS or ROM to flash it back on. I tried to sideload with TWRP but the feature wouldn't start. I flashed the stock recovery and tried to sideload it there but I get an "error: protocol fault (no status)"... I tried to mount storage on TWRP but that feature didn't seem to work on it either. It's a good thing that I still have my OnePlus One to use, but I would appreciate your help!!
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Bro don't worry.
All you gotta do is to download a stock image.
Boot into fastboot.
Then use a toolkit like this one.
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Then use his toolkit to download and boot in twrp.
Now copy paste a full signed zip onto the phone by connecting it to your PC .
http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870
Do a system and cache clean.
Flash the zip and make it boot before rooting it.
Done..!!

Joyo-rocker said:
Bro don't worry.
All you gotta do is to download a stock image.
Boot into fastboot.
Then use a toolkit like this one.
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Then use his toolkit to download and boot in twrp.
Now copy paste a full signed zip onto the phone by connecting it to your PC .
http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870
Do a system and cache clean.
Flash the zip and make it boot before rooting it.
Done..!!
Click to expand...
Click to collapse
It worked bro thanks I was having data issues too before and now it all just works.
Sent from my ONEPLUS A3000 using Tapatalk

rickyx32 said:
It worked bro thanks I was having data issues too before and now it all just works.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
No prob bro...!

Can't boot into recovery after cm14.1 nightly official

So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers

Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get

JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?

JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk

I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.

Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.

Thanks a lot guys, that did the trick, and done with flashify

JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk

Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.

Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!

HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.

GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...

m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time

http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me

JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me

This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!

gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..

After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.

Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse

Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life

I installed 7.1.1 by mistake. What now? Help

I bought my 5X in October and came here to root my phone and be able to use the ElementalX and the Advanced Interactive Governor tweaks.
Everything was working fine and my phone really performed outstandingly.
Then I saw the OTA 7.1.1. popping up. I didn't allow it until I installed it by mistake yesterday...
Now I'm stuck with google asking me to lock the bootloader.
I can access the bootloader. I get a lot of options.
I can access the recovery mode and it gets me to RecoveryProject 3.0.2-2 by Teamwin.
I already have the Android platform tools on my desktop and it's working.
From there I have 2 questions :
1. Is there a way to not wipe all the contents on my phone? I didn't get the chance to backup all the data on it.
2. After that how can I get my phone working with the latest android version as I was before, unrooted and running with EX Kernel Manager.
Thanks for your help.

1. try installing the supersu zip from the recovery
2.EX Kernel Manager cannot work without root. so you need to root your device

Thanks a lot for you answer!
1. So by installing SuperSu zip from the recovery I would be able to backup my phone data?
2. I meant rooted sorry. So my phone is already rooted and I'm fine with staying that way.

Enzoli said:
Thanks a lot for you answer!
1. So by installing SuperSu zip from the recovery I would be able to backup my phone data?
Click to expand...
Click to collapse
yes
you can actually backup you device from TWRP recovery.
flash the supersu zip and you will boot normally without any data lose

Insane! thanks a lot.
One more noob question. I got the latest superSu zip.
How can I flash it from the recovery?
How can i transfer it to the phone?

Ok I almost got it.
My only question left is how can I transfer the SuperSu zip file onto my phone since I don't have access to anything else than Bootloader and TWRP

Enzoli said:
Ok I almost got it.
My only question left is how can I transfer the SuperSu zip file onto my phone since I don't have access to anything else than Bootloader and TWRP
Click to expand...
Click to collapse
adb sideload from twrp

OK guys thanks. When I use adb sideload in twrp advanced menu it gets stuck on "Starting ADB sideload feature... "
And when I type ADB devices on the command prompt it does not show my device but if I'm just in the menu before sideload it does find my device and says the serial number + recovery.
What am I doing wrong?
Thanks for helping.

You should be able to transfer files while being in recovery using MTP mode.

How do I use MTP mode? Sorry what does that mean. Can't find an explanation on the internet.
I've looked at all the options in the menu but can't find such a option.
I really feel stupid.

Ok guys I transfered SuperSu to my phone using adb push.
I flashed my phone with SuperSu but when i reboot my phone, it still tells me I need to lock my bootloader.
What shall I do now?

I keep going to the Googl screen with the little locker and then I reach the No Command screen.
The phone won't boot into Android no more. Guys please help I'm desperate. Is my phone dead?

Ok so I guess my phone is now in bootloop.
Still anyone willing to help?

OK I tried many things in despair and now I cannot enter the recovery mode anymore. It just gets stuck on the teamwin screen.
Guess it's time to buy a new phone.

So miracle I could enter the recovery.
Now I don't know where to go. I would like to be able to enter normal android but my phone will keep on showing android screen with little lock and the end on the No command screen. Endlessly.

Ok. THread can be closed. I managed to flash a factory image. Lost all my data but I got a working phone so I guess it's not to bad.

...

Enzoli said:
Ok. THread can be closed. I managed to flash a factory image. Lost all my data but I got a working phone so I guess it's not to bad.
Click to expand...
Click to collapse
If you ever need help on updating your software to the latest Android version, follow my guide as a reference:
https://forum.xda-developers.com/showthread.php?t=3206930
Sent from my Nexus 5X using Tapatalk

FingerPrint and themes not working

I was on nougat on my L21_hw_eu before i tried to upgrade manualy to oreo. i tried the twrp and terminal method and my phone started upgading. It failed at 72% saying "update verification failed". I lost my stock rom and bricked my phone.
Then i manualy flashed different Update.app images and was able to unbrick my phone .
I tried lineage OS and stock oreo.
Problems are:
1: I cant factory reset my phone using stock recovery it fails at 24%
2: FingerPrint Sensor won't work except for gestures (in Stock oreo. works in LineageOs)
3: Themes dont work
4: Flash light don't work
4: CAMERA is not responding. in both roms
in lineageOs everything works perfectly except Camera.
Please provide me details for what am i doing wrong..

iu.khan53 said:
I was on nougat on my L21_hw_eu before i tried to upgrade manualy to oreo. i tried the twrp and terminal method and my phone started upgading. It failed at 72% saying "update verification failed". I lost my stock rom and bricked my phone.
Then i manualy flashed different Update.app images and was able to unbrick my phone .
I tried lineage OS and stock oreo.
Problems are:
1: I cant factory reset my phone using stock recovery it fails at 24%
2: FingerPrint Sensor won't work except for gestures (in Stock oreo. works in LineageOs)
3: Themes dont work
4: Flash light don't work
4: CAMERA is not responding. in both roms
in lineageOs everything works perfectly except Camera.
Please provide me details for what am i doing wrong..
Click to expand...
Click to collapse
If you only have extracted images flashed from update.app, then you do not have the full rom installed.
You should run either hurupdater of HWOTA again to get full emui8 installed.

mrmazak said:
If you only have extracted images flashed from update.app, then you do not have the full rom installed.
You should run either hurupdater of HWOTA again to get full emui8 installed.
Click to expand...
Click to collapse
I suspected that too...
Now my TWRP hangs at initial screen. i m using p20lite.img twrp
other TWRP works but they dont have adb enabled
is there a way i could flash through fastboot?

iu.khan53 said:
I suspected that too...
Now my TWRP hangs at initial screen. i m using p20lite.img twrp
other TWRP works but they dont have adb enabled
is there a way i could flash through fastboot?
Click to expand...
Click to collapse
no,
dont adb though.

mrmazak said:
no,
dont adb though.
Click to expand...
Click to collapse
HuRUpdater keeps loading on initial screen and
HWota Fails after installing no check recovery.
screenshot attached..

iu.khan53 said:
HuRUpdater keeps loading on initial screen and
HWota Fails after installing no check recovery.
screenshot attached..
Click to expand...
Click to collapse
Is that v3.1 . I pulled that version because of error 2 messages.
Check the guide and download again. File name should be. ...
NVM, I just put the download link here.
https://www.androidfilehost.com/?fid=746163614322268008

mrmazak said:
Is that v3.1 . I pulled that version because of error 2 messages.
Check the guide and download again. File name should be. ...
NVM, I just put the download link here.
https://www.androidfilehost.com/?fid=746163614322268008
Click to expand...
Click to collapse
Hwota was successful with the newer version but after rebooting update failed at 0%

iu.khan53 said:
Hwota was successful with the newer version but after rebooting update failed at 0%
Click to expand...
Click to collapse
Please screenshot the twrp screen before reboot.

mrmazak said:
Please screenshot the twrp screen before reboot.
Click to expand...
Click to collapse
i flashed different images from UPDATE.APP manually through fastboot and twrp.. I was succesfull and fingerprint was working but camera was still not working so i stupidity flashed DTS.IMG, ODM.img, and ERECOVERY_KERNEL.img through twrp and when i rebooted. there was completely black screen and nothing was working. fastboot only recognizes device and i m able to send commands . i wanted to flash other dts,odm and ERECOVERY_KERNEL.img through fastboot but it says "remote command not allowed". there is absolutely no life in phone. i think it is hard bricked. is there a way to get device back?? or else i m completely F****D.

iu.khan53 said:
i flashed different images from UPDATE.APP manually through fastboot and twrp.. I was succesfull and fingerprint was working but camera was still not working so i stupidity flashed DTS.IMG, ODM.img, and ERECOVERY_KERNEL.img through twrp and when i rebooted. there was completely black screen and nothing was working. fastboot only recognizes device and i m able to send commands . i wanted to flash other dts,odm and ERECOVERY_KERNEL.img through fastboot but it says "remote command not allowed". there is absolutely no life in phone. i think it is hard bricked. is there a way to get device back?? or else i m completely F****D.
Click to expand...
Click to collapse
You are well past anything I. Have dealt with.

mrmazak said:
You are well past anything I. Have dealt with.
Click to expand...
Click to collapse
well i will try to repair it with sigma device. I heard it can flash anything on to device through fastboot. I will try that otherwise i have to give it to huawei service centre and pray they accept to repair it.

iu.khan53 said:
well i will try to repair it with sigma device. I heard it can flash anything on to device through fastboot. I will try that otherwise i have to give it to huawei service centre and pray they accept to repair it.
Click to expand...
Click to collapse
can not explain it, but I have seen that camra not working problem, and the blank black screenfixed by flashing the vendor partiton. The bad part about that is, i do not think it flashes with fastboot.

mrmazak said:
can not explain it, but I have seen that camra not working problem, and the blank black screenfixed by flashing the vendor partiton. The bad part about that is, i do not think it flashes with fastboot.
Click to expand...
Click to collapse
i took the phone to local repair shop they flashed naugat on it and were unsuccesfull(naugat cant be flashed on oreo) but i am again at fastboot with situation similar to this thread.
https://forum.xda-developers.com/mate-9/help/please-help-bootloop-error-func-14-1-t3724685

iu.khan53 said:
i took the phone to local repair shop they flashed naugat on it and were unsuccesfull(naugat cant be flashed on oreo) but i am again at fastboot with situation similar to this thread.
https://forum.xda-developers.com/mate-9/help/please-help-bootloop-error-func-14-1-t3724685
Click to expand...
Click to collapse
As far as I know (which is not that far). You need three images to be correct for recovery to load on oreo based device.
1. recovery_ramdisk.img
2. kernel.img
3. recovery_vbmeta
try to flash those in fastboot first. and see if they complete without error.
then if they do flash, try to boot into recovery. (try with stock first-- can try TWRP after if this works)

mrmazak said:
As far as I know (which is not that far). You need three images to be correct for recovery to load on oreo based device.
1. recovery_ramdisk.img
2. kernel.img
3. recovery_vbmeta
try to flash those in fastboot first. and see if they complete without error.
then if they do flash, try to boot into recovery. (try with stock first-- can try TWRP after if this works)
Click to expand...
Click to collapse
i cant flash ramdisk images. ithink i m on naugat now because i am able to flash succesfully recovery.img and boot.img in recovery and boot partitions. but cant flash ramdisk and kernel.
and what is iom3 image. error do i need to flash something for that?
and also hifi image error when upgrading through dload method

iu.khan53 said:
i cant flash ramdisk images. ithink i m on naugat now because i am able to flash succesfully recovery.img and boot.img in recovery and boot partitions. but cant flash ramdisk and kernel.
and what is iom3 image. error do i need to flash something for that?
and also hifi image error when upgrading through dload method
Click to expand...
Click to collapse
oh, well let me get together some nougat suggestions

mrmazak said:
oh, well let me get together some nougat suggestions
Click to expand...
Click to collapse
i have sent phone to the service center. waiting for their response now. They told me if they were unable to repair the phone then i will get a new one. lets hope for the best.

iu.khan53 said:
i have sent phone to the service center. waiting for their response now. They told me if they were unable to repair the phone then i will get a new one. lets hope for the best.
Click to expand...
Click to collapse
That sounds good

mrmazak said:
That sounds good
Click to expand...
Click to collapse
Received call today they were unable to repair it. They said they will get me a new one as soon as new stock arrives.

mrmazak said:
That sounds good
Click to expand...
Click to collapse
Recieved new phone today. Works like a charm. but again stuck on naugat. i will wait for official upgrade this time
Edit:
Got upgrade to oreo today. Love the new UI.