Database Info

[Q] Crazy Boot Loop *help*

This morning my Nexus 5 decided to die. It's stuck in a boot loop. I've never rooted, or done anything crazy to my phone. Haven't even downloaded an app in a few days, maybe a week or more. I am running stock 4.4.2.
My morning started just right. My alarm on my phone went off letting me know it was time to go to work. Then after I got ready, I picked up my phone and checked emails, facebook, instagram, you know.. normal things I do every day. I put it in my pocket and proceeded to get into my vehicle to drive to work. I then checked the time. All of the sudden after I press the power button to see, it turned off. I then went to turn it back on by holding the button. It showed "Google" then turned off. That's when I knew I was in trouble. It then began... The boot loop of death. This thing sometimes gets to the four Google colors, then shuts off..but this is rare. I can't even do the whole volume down + power deal. I can.. but I can't make a selection because the phone restarts.
WHAT AM I EVER TO DO.
I tried the hard reset with the two buttons, obviously as I stated above, that doesn't work. I tried downloading this to see, but turns out you need to access the bootloader. I cannot do this either.
My question is, do I send it in for warranty work, or is there some magical way to fix this?

Well,
Even if there was a way to repair, I would not keep a phone that had this kind of problem. I think, you should call Google and ask them for a RMA.
While they send you the new Nexus 5, you can try to repair the old one (if anybody is able to provide you a "fix"). If you're able to repair it : great, backup your data and use the new phone (and send the old one to google, like you would do for a RMA).

The power button has record of getting stuck on its contacts. Some have fixed it by hitting the phone against a table. Obviously not recommended
and as it's an internal hardware fault, Google will replace it. .

Might be a stupid question, but are you sure it has battery? Maybe plug it in for an hour and try again.

Lokke9191 said:
Might be a stupid question, but are you sure it has battery? Maybe plug it in for an hour and try again.
Click to expand...
Click to collapse
Yes, it was fully charged.
GUGUITOMTG4 said:
The power button has record of getting stuck on its contacts. Some have fixed it by hitting the phone against a table. Obviously not recommended
and as it's an internal hardware fault, Google will replace it. .
Click to expand...
Click to collapse
This actually makes so much sense. I know sometimes when locking or unlocking, the screen would flash. So this, I believe may be the problem. I didn't even think about that.
Charlus97 said:
Well,
Even if there was a way to repair, I would not keep a phone that had this kind of problem. I think, you should call Google and ask them for a RMA.
While they send you the new Nexus 5, you can try to repair the old one (if anybody is able to provide you a "fix"). If you're able to repair it : great, backup your data and use the new phone (and send the old one to google, like you would do for a RMA).
Click to expand...
Click to collapse
Google is usually pretty good with their RMA process, except they make you pay up front. But looks like I'll have to do what I gotta do.
Thanks everyone!

The blue light of death... No screen no safemode no boot

I've had my Samsung up and running for about a week now , did the two most recent updates . Today is the first time I experienced some serious problems . It started with a fingerprint scanner not working delivering an error message that read "fingerprint scanner has stopped working restart phone if this repeats" so after my second time of dealing with this there I restarted the phone . P at this point in time is when the blue light was lit up and has stayed lit up since I restarted it, this has been about an hour. I've tried every option on the recovery menu except factory restore. When I turn the phone on safe mode or not it goes straight to a black screen with the blue light continuously lit up . When I turn the phone off the light never turns off . I've tried hooking it up to the charger and doing all of the same steps above and still no luck. I have not installed any unknown apps other than ones on the play store and haven't had time to even explore rooting or ROMS yet. Seems to me like a brick by the stock software don't know if anybody else's experiences but I don't know what to do . Maybe someone can shed some light before I consider doing a factory restore , if that will even work.. I think this thing is bunked.
Edit~ I also tried pressing both volume buttons the power button and the home button all at once and it took me to a blue screen with the android logo and Galaxy written on the bottom . Nothing for a few seconds then it's says erasing and reboots....still a black screen and a solid blue light.

mattkilla420 said:
I've had my Samsung up and running for about a week now , did the two most recent updates . Today is the first time I experienced some serious problems . It started with a fingerprint scanner not working delivering an error message that read "fingerprint scanner has stopped working restart phone if this repeats" so after my second time of dealing with this there I restarted the phone . P at this point in time is when the blue light was lit up and has stayed lit up since I restarted it, this has been about an hour. I've tried every option on the recovery menu except factory restore. When I turn the phone on safe mode or not it goes straight to a black screen with the blue light continuously lit up . When I turn the phone off the light never turns off . I've tried hooking it up to the charger and doing all of the same steps above and still no luck. I have not installed any unknown apps other than ones on the play store and haven't had time to even explore rooting or ROMS yet. Seems to me like a brick by the stock software don't know if anybody else's experiences but I don't know what to do . Maybe someone can shed some light before I consider doing a factory restore , if that will even work.. I think this thing is bunked.
Edit~ I also tried pressing both volume buttons the power button and the home button all at once and it took me to a blue screen with the android logo and Galaxy written on the bottom . Nothing for a few seconds then it's says erasing and reboots....still a black screen and a solid blue light.
Click to expand...
Click to collapse
What firmware are you on? If you've taken the most recent updates, don't worry about rooting. Probably won't happen at least for a while. If you have a warranty, I would use it. If you get a new phone, don't take any updates if you might want to root.
If you want to keep this phone you should try the factory reset or the emergency recovery in SamsungSwitch.

Tulsadiver said:
What firmware are you on? If you've taken the most recent updates, don't worry about rooting. Probably won't happen at least for a while. If you have a warranty, I would use it. If you get a new phone, don't take any updates if you might want to root.
If you want to keep this phone you should try the factory reset or the emergency recovery in SamsungSwitch.
Click to expand...
Click to collapse
I'm not sure which firmware was on it, I did not pay attention before I took the update. I do know I have taken 2 updates in the last week since I received the phone.
I took the phone to a Verizon store and of course, seemed like going backwards. The rep tried all the same things I had tried and ended up calling a customer service rep to help him figure out what to do. Because the phone was purchased online my business' HR lady had to order another one online( which they replaced for free). Not sure what the problem ended up being but I know personally the most recent update BRICKED the phone.
New phone is up and running and thank you about the advice to not update if I prefer root. I love the stock ROM so I was really only going to root to de-bloat alot of the stock apps that are repetitive (i.e. messaging, messages, and Hangouts) .
So as of now no known fix to this blue light of death, except get a new one.

mattkilla420 said:
I'm not sure which firmware was on it, I did not pay attention before I took the update. I do know I have taken 2 updates in the last week since I received the phone.
I took the phone to a Verizon store and of course, seemed like going backwards. The rep tried all the same things I had tried and ended up calling a customer service rep to help him figure out what to do. Because the phone was purchased online my business' HR lady had to order another one online( which they replaced for free). Not sure what the problem ended up being but I know personally the most recent update BRICKED the phone.
New phone is up and running and thank you about the advice to not update if I prefer root. I love the stock ROM so I was really only going to root to de-bloat alot of the stock apps that are repetitive (i.e. messaging, messages, and Hangouts) .
So as of now no known fix to this blue light of death, except get a new one.
Click to expand...
Click to collapse
Check out your firmware in settings, about phone. If your build ends in OC3 or OE2, it can be rooted.
Glad you were able to get a new phone.

OC3!!???
Sent from my SM-G920V using Tapatalk

mattkilla420 said:
OC3!!
Sent from my SM-G920V using Tapatalk
Click to expand...
Click to collapse
Good for you! Pingpong is so easy you can be rooted in less than a minute.

Screen doesn't work after new start

I got the following issue which has been confirmed by Samsung Service desk to be occur more often:
After power down (switching of) and start-up the screen stays blind//black. Phone seems to work (LED and sound notifications). Attaching to PC with USB phone is recognized as normal. Hard reset via power and volume down bottom (and home button) seems to work but still screen stays blind. Phone is now on its way for repair. Will keep updated once I got news.
Anyone else here has same problem? Cures? Root-cause?

no one?

I had the problem 4 months ago.
The screen went black a few times but always goes up after 10 minutes of pressing vol down + power button. But after a lot of time doing that, it finally went absolutely black like yours, and yes the phone was working cause I could hear my ringtone, see the led blinking and it vibrated sometimes.
Then they repaired it free of charge even if my knox was 0x1. I don't know if the issue is root related or not. I was rooted and on SuperMan Rom.

Hi thanks, for the reply. Mine is 100% original and being repaired currently. Not sure yet what the cause is but will share it once I got the feedback.
Cheers,
Steven

Update 28/11/2016: According to repair-shop it's the motherboard. Anyone else had issues like this?

Steven13 said:
Update 28/11/2016: According to repair-shop it's the motherboard. Anyone else had issues like this?
Click to expand...
Click to collapse
When I had this issue, they told it was an issue with the motherboard and the lcd panel and they changed both according to the reparation report.

Steven13 said:
Update 28/11/2016: According to repair-shop it's the motherboard. Anyone else had issues like this?
Click to expand...
Click to collapse
Not personally, but have read another one member at least, here having the same problem

Update 6-12: I'll get my phone returned this week. Apperently a faulty motherboard was the cause of this error. Samsung and it's official repair center where negatively in the news this week on a Dutch consumer program. Reason is not having enough OLED replacement screens so consumers are "forced" to buy a new one. [in Dutch: http://kassa.vara.nl/nieuws/reactie...eprocedure-van-beeldschermen-van-smartphones].

SOD (sleep of death)

I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?

60puc said:
I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?
Click to expand...
Click to collapse
This has happened to me before.What I simply did was replace the display.

Mr.Ak said:
This has happened to me before.What I simply did was replace the display.
Click to expand...
Click to collapse
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.

60puc said:
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.
Click to expand...
Click to collapse
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.

Mr.Ak said:
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.
Click to expand...
Click to collapse
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.

60puc said:
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.
Click to expand...
Click to collapse
As I already said,the same issue happened to me after I changed my display.I asked for replacement and replaced that damaged display,boom! I don't know what's so hard in it for you to understand.

Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.

60puc said:
Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.
Click to expand...
Click to collapse
Aliexpress?

Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.

60puc said:
Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.
Click to expand...
Click to collapse
Get ready with a lot of proofs tho'!

to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?

Gab_echelon said:
to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?
Click to expand...
Click to collapse
See previous page,I've already explained what is the cause of the issue.

I just finished replacing my screen, been waiting for my broken antenna cable and volume button flex to arrive. Everything works except the damn SOD i never had with my old screen. Tried turning off the proximity sensor check and still a no go. The screen turns on fine initially and trying to wake it instantly works all the time, but if I leave it off for any longer than 5 sec probably it won't respond to anything - power button, volume button, double tap and plugging in the usb cable connected to a power source.
Does this sound more like a governor issue? The rom installed is lineageOS (just updated to 10-30 release). Looking up my purchase log to open a dispute...
tested it again, repeated lock/unlocks puts it into the SOD state, doesn't even take 2 sec to do it...
oh wow, it does this even in the twrp recovery. I have wiped cache and dalvik cache just for the hell of it but doubt that was the real cause...

Gab_echelon said:
works everything but not touch
Click to expand...
Click to collapse
we've got a reverse situation. touch, buttons, sounds, modem works, but not screen (if you lock/unlock it 10-20 times it can raise again without reboot.
Buratei said:
it does this even in the twrp recovery.
Click to expand...
Click to collapse
i've got the first SOD in twrp mode. it doesn't matter, but at first - no troubles were with that. and now it works so so at home. and if i use it outdoor it becomes very often, but at home it seems that it works ok, just only seems, because if i want - i can do some manipulations (use camera, lock/unlock it etc) and the SOD appears again. but custom os executes SOD more frequently. i think it can be real overvoltage, like people says.
there are many posts here and everyone advices not effective solutions (flash stock, modem, fw ...) at first it helped me, but now i know there is no way, i can just try but ...
long time ago i owned an old tablet iconbit matrix - it has just the similar issue. it boots, but if you go to a sleep mode - it didn't wake up every time. it lights works ok inside, but no image. i had two displays and if i used one in a custom rom it worked ok, but not another one. stock rom works ok with every display. the solution was a display driver, like at windows OS.
cause of developers bugs, it was a little different (not stock-based) and some revisions of display works ok, others aren't.
so, i think it can be fixed, but the solution for me - change a display like the first reply says. Ali seller read this topic and posted me this in a few days after i started this topic:
Your dispute has been processed and the money will back to you in 7~10 working days.
so could you give us a positive feedback, please?
Best regards.
so, i'll order another one, no trouble, i hope this will help me to enjoy my oneplus.

60puc said:
so could you give us a positive feedback, please?
Best regards.
Click to expand...
Click to collapse
They always ask for positive feedback in exchange for refund/replacement.Bastards,aren't they? @evronetwork
For the sake of other people that'll read your feedback and make their decisions upon it,don't do it! Just complain this bribery to aliexpress staff ffs!

well I wish I bought from aliepxress... I bought mine from ebay to pinch some pennies, and because I was waiting on other replacement parts (which were only needed due to damage occurred during a screen replacement op) to ge here I am way over the protection period. aw shiiiiit, I guess you live and learn
gotta tell you though, the screen is a bit wacky in other ways too. the capacitive buttons do light up but not completely (kinda dark in the corners) and the colors look a bit off. hopefully the seller would honor the refund/return request...
EDIT: whoa... kinda hard to believe, but I messed around with battery profile just for the hell of it and by some pure luck discovered that the "performance" profile (second one from the far right) works just fine and wakes the screen every time. The "balanced" profile and everything below that gives me an insta-death. go figure!
EDIT2: guess I spoke too soon. it sure as hell looked like fixed, but it came back after a while. maybe it is just more sporadic than I thought...

No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg

60puc said:
No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg
Click to expand...
Click to collapse
What happened to getting a new display?

I use this one, because it works ok, but only at home. As a home tablet. At the street it fails every time.
I can reboot it if it doesn't wake up. But it wakes up often, so i don't want to order new one now. I want to check my mainboard to be sure, that it is dispaly problem

a bit late, but thought I should update on the situation... all working fine after a (yet another) LCD replacement. Much better color balance to boot, points to QC problems at the supplier's end. If I ever have to do this again, I am definitely going to inspect the new LCD as soon as I receive I receive it.

Phone hangs and switches off automatically

Hi , got this phone 3 days back and have observed that the phone hangs and switches off automatically. This has happened while viewing photos in the gallery or clicking a photo and the last time it was while changing brightness. Any clue why is it behaving this way?

bhavik_kk said:
Hi , got this phone 3 days back and have observed that the phone hangs and switches off automatically. This has happened while viewing photos in the gallery or clicking a photo and the last time it was while changing brightness. Any clue why is it behaving this way?
Click to expand...
Click to collapse
Didn't you mess with anything in Developer options?

_jis_ said:
Didn't you mess with anything in Developer options?
Click to expand...
Click to collapse
No. Infact i haven't even unlocked the developer options.

bhavik_kk said:
No. Infact i haven't even unlocked the developer options.
Click to expand...
Click to collapse
Did you activated some gestures? Settings / Advanced / Gestures...
If not then do factory reset, if it doesn't help then RMA.

Double tap to wake up and finger print gesture are the only 2 things which are turned on.

Then do factory reset, if it doesn't help then RMA.

It is happening with me as well. It switches off and then goes into a bootloop for 5 mins before it starts. I talked to the customer care and they sent a technician but all he did was reset the phone. The problem didn't go. So I filed a replacement for the product. What I could deduce from this (might be wrong) is that this issue has something related to the loose battery(watch Jerryrigeverything's teardown vid) placement gone wrong in Zenfone 6. Either way, if I didn't misunderstand your issue then maybe you should also get your varient replaced.

After my last post in this thread, i had uninstall a gallery app by SB studios(available on play store) and since then the problem has stopped. I have a replacement date till 7th July....will wait till 6th and in case the problem occurs even once, ill put up a replacement request.

Siddharth13 said:
It is happening with me as well. It switches off and then goes into a bootloop for 5 mins before it starts. I talked to the customer care and they sent a technician but all he did was reset the phone. The problem didn't go. So I filed a replacement for the product. What I could deduce from this (might be wrong) is that this issue has something related to the loose battery(watch Jerryrigeverything's teardown vid) placement gone wrong in Zenfone 6. Either way, if I didn't misunderstand your issue then maybe you should also get your varient replaced.
Click to expand...
Click to collapse
Just chiming in, I don't see how a loose battery will cause the phone to hang up and reboot. A loose battery will be a fire hazard. A loose battery connector could short circuit the phone and/or make the phone loose power instantly.
I suggest you reset your phone again and if the problem persists get a replacement. Don't wait for the last day, you'll have to convince the CSR to accept the RMA.

Already place a replacement request. I received a call from flipkart today noon, asking me to start the phone in safe mode and see if the problem persist, do a factory reset. Wierd part was the phone even hung when i was in safe mode. I have informed flipkart abt the current state of the phone and they are sending some technician to my residential place check the phone.

@bhavik_kk That's good to hear, keep us apprised!

The technician from Flipkart.com visited and all he did was a hard reset ....and said the issue will be resolved and left. The phone still switches off suddenly and take atleast 30-45 mins to turn on....as it goes into bootloop..aur the phone screen just simply flickers. I can't even place another return request on the flipkart website and it pops up an error, 'somethin went wrong'... Worst experience with flipkart. #Asus India....please help me with this.

I have the same problem too. It happened after the latest update three days ago. It happened twice while I exit playing clash royale and repeatedly after I exit the camera APP. The phone will turn off and Bootloop after displaying the Asus logo. It will boot normally if I hold down the volume down and power keys together ( Don't ask me why... )
I did a factory reset and after first time setup it just shut down and refuseD to boot at all this time.
I'll have to take it to the local service center later.

Me was also facing that issue and still sometime phone hangs and only black screen, then i have to hard restart the phone.
Hope Asus will come provide update to fix it.

This phone is a joke! It is starting to look as bad as the Samsung Galaxy Fold. Way too many issues need to be resolved. Asus rushed it out in an attempt to compete and they are falling on their faces hard. Don't believe me...just do the research on the many, many issues.

bhavik_kk said:
Hi , got this phone 3 days back and have observed that the phone hangs and switches off automatically. This has happened while viewing photos in the gallery or clicking a photo and the last time it was while changing brightness. Any clue why is it behaving this way?
Click to expand...
Click to collapse
Siddharth13 said:
It is happening with me as well. It switches off and then goes into a bootloop for 5 mins before it starts. I talked to the customer care and they sent a technician but all he did was reset the phone. The problem didn't go. So I filed a replacement for the product. What I could deduce from this (might be wrong) is that this issue has something related to the loose battery(watch Jerryrigeverything's teardown vid) placement gone wrong in Zenfone 6. Either way, if I didn't misunderstand your issue then maybe you should also get your varient replaced.
Click to expand...
Click to collapse
kwongwt said:
I have the same problem too. It happened after the latest update three days ago. It happened twice while I exit playing clash royale and repeatedly after I exit the camera APP. The phone will turn off and Bootloop after displaying the Asus logo. It will boot normally if I hold down the volume down and power keys together ( Don't ask me why... )
I did a factory reset and after first time setup it just shut down and refuseD to boot at all this time.
I'll have to take it to the local service center later.
Click to expand...
Click to collapse
mohitgarg7 said:
Me was also facing that issue and still sometime phone hangs and only black screen, then i have to hard restart the phone.
Hope Asus will come provide update to fix it.
Click to expand...
Click to collapse
Are you all from India?
Do you have the same mobile operator or not?
How old is your SIM card?
Are you using VoLTE?

bhavik_kk said:
The technician from Flipkart.com visited and all he did was a hard reset ....and said the issue will be resolved and left. The phone still switches off suddenly and take atleast 30-45 mins to turn on....as it goes into bootloop..aur the phone screen just simply flickers. I can't even place another return request on the flipkart website and it pops up an error, 'somethin went wrong'... Worst experience with flipkart. #Asus India....please help me with this.
Click to expand...
Click to collapse
Just call the customer service again (take the number from the website). You'll again get frustrated while explaining a new person the whole problem all over again. They'll send the technician again (hopefully the same one). Just tell him that the reset didn't work (or record a video of the bootloop) and he'll approve the replacement. It worked for me (got the replacement) and hopefully will work for you too.

_jis_ said:
Are you all from India?
Do you have the same mobile operator or not?
How old is your SIM card?
Are you using VoLTE?
Click to expand...
Click to collapse
I am from Hobg Kong. My phone was functioning well before the latest update last week.
Its funny when I took my phone to the service center it has rebooted by itself (I tried for an hour earlier but the phone has refused to boot no matter how I tried) and everything seens to be fine. Luckily I have recorded a video of the malfunction earlier at home to prove my case !

kwongwt said:
I am from Hobg Kong. My phone was functioning well before the latest update last week.
Click to expand...
Click to collapse
What version was functioning well for you?
What version broke your phone?
Did you use VoLTE prior to boot loop?

_jis_ said:
What version was functioning well for you?
What version broke your phone?
Did you use VoLTE prior to boot loop?
Click to expand...
Click to collapse
My phone is not with me so I cannot tell you exactly which version it was. As I said, it was Ok before the latest upgrade a few days ago. I have been using volte since day one. I doubt it caused the problem because when reboot happened, I was at home using WiFi.