Related
Hello,
i have the same issue as described in the thread below and shown in this video ==> https://vid.me/NGc5
== > http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=41205&extra=page=1&page=1
i have been suffering from same issue since the .90 update, i tried flashing the 1.1GB file using adb which didn't solve the issue along with the yesterday update
anyone having the same problem?
i want to flash the older .63 version, but using adb it says that it can't flash older version than the current version , anyone can help with that ?
@Asus_USA
any info please
I downgraded the rom to a version from July, yet the same issue persist
Seems like a member mentioned somewhere else that the. 90 update might have broken some hardware using code that is not reversible
Waiting for any feedback from Asus
Sent from my GT-N7000 using Tapatalk
That's actually a screen or onboard video issue.... I see this on laptops all the time
Frankenberrie said:
That's actually a screen or onboard video issue.... I see this on laptops all the time
Click to expand...
Click to collapse
the weird thing that it only happened after the .90 update and several users are reporting it
And some software works fine, like whatsapp where the screen is normal while inside it
Sent from my GT-N7000 using Tapatalk
more users are reporting the same issue on the zentalk forum, good luck all avoiding this
no one else here on the forum suffering from the same issue ? any ideas for troubleshooting or solving ?
@ASUS_Khang
can you please confirm that this is a software issue that will be solved through an update and not a hardware failure ?
AhmadOkda said:
no one else here on the forum suffering from the same issue ? any ideas for troubleshooting or solving ?
Click to expand...
Click to collapse
I am also having this SAME issue ! I have unlocked my bootloader, root access, and flashed the 2.40.97 update again, I tried downgrading, it won't let me install and lower update over an higher one. and I can't get twrp recrovery to stay after the flash, it always goes back to the stock recovery. Also I know whats causing the problem. it's the Auss / powered by intel animated screen , First you have the Asus splash screen, Then the Animated Asus / Intel animation Then the boot animation screen. after unocking my bootloader, and changing the boot animation. I can tell you for sure, the Asus / Intel animation that is causing the issue !. I don't know where this animation is stored on the phone, if anyone knows. maybe we can restore of get rid of it. Anyway my phone is pretty much useless right now, can't use the keypad on the call screen, and can't even see the bottom half of the phone, IT's NOT a hardware problem. like some people have said. it's that dam Asus / Intel animation at starup.
I tried downgrading (using fastboot and abd) to every available firmware and nothing solved this problem
IMHO I think that the 90 upgrade triggered a bug while flashing boot partition
Sent from my GT-N7000 using Tapatalk
UPDATE.. I was able to install cm-12.1-20151011-UNOFFICIAL-Z00A.zip 2015-10-11 01:29 Using Windroid UIniversal Android toolkit. and it worked. and TWRP also the recovery.
Unlocked bootloader, rooted phone, installwd TWRP. Flashed boot, droidboot, with WW. 2.12.40.09 Z00A Then installed cm-12.1-20151011-UNOFFICIAL-Z00A.zip 2015-10-11 01:29 . The screen problem IS still there ! \ Anyone else have any ideas ? ~ Travis
My phone (ZE551ML) developed the same issue. When flashing back to stock didn't work, I sent it in for an warranty RMA. A part was replaced and the phone sent immediately back. Not a word to me about the unlocked bootloader. Just make sure if you send it in, that you state you did flash attempt flashing to stock, and make sure the phone is as close to stock as you can get. Factory reset the phone and go.
I tried last week 3 times I got an RMA & then an advanced RMA and i'm getting the run around from them. they even had the hold of 344.00 on my checkings account to the advanced RMA and then THEY canceled the RMA and everytime I talked to them 3 different customer support people then said " sorry we're updating our systems call back tomorrow. " I got told that 3 times and I've called 4 times. the phone is pretty much useless at the moment.
If they send the phone back to you, the part that was replaced on mine is "90AZ00A1-M02610". Dunno if you can get that part yourself and have it repaired by a third party, but other than that I wouldn't know what to do in your situation.
ArmchairWizard said:
If they send the phone back to you, the part that was replaced on mine is "90AZ00A1-M02610". Dunno if you can get that part yourself and have it repaired by a third party, but other than that I wouldn't know what to do in your situation.
Click to expand...
Click to collapse
...This is the Hardware model# of the whole device, not just a part inside , buy a new phone and you have this yourself !
At least for those in Canada, here a short review for my "advanced replacement" experience:
I used the Chat on their website to get a RMA#, then got a confirmation email with a sort of howto. They mentioned to use Fedex or UPS to send the defective device in and noted not to long to wait to do this otherwise the hold on my creditcard... you know! So i sent the package 3 days later with UPS, cost me a bit over CA$60 with insurance and tracking.
Just the other day i got email from Purolator (a Canada only parcel service) to print a return sticker. No one from ASUS mentioned this to me - $60 wasted
The replacement phone came also with Purolator, ASUS emailed me a tracking# but NOT wich carrier they used. Cost me a few hours and a couple phone calls to find out and re-route the package to my workplace.
ASUS did not use a original case, just a folded carton as they stated the replacement would be a new device. In case i decide to sell the phone i don't have original carton
Start to install all my usual App's etc. found that the phone does not receive any GPS signals, so it seems i changed a not usable screen into a not working GPS
For me, this was my last ASUS for a very long time!
Finally got my Advanced RMA going. can't wait to get a working phone, as soon as I do. Going root & unlock bootloader and install CM 12.1 I'm DONE with ASUS's bloatware ! ~ T
I am having the same problem. I have gotten my screen to work, but it still glitches. Is the only solution to send it in?
jeisenhart34 said:
I am having the same problem. I have gotten my screen to work, but it still glitches. Is the only solution to send it in?
Click to expand...
Click to collapse
I think so, I tried to fix it, flash with 2.20.40.97 Four times now, the problem is still there, rooted, unlocked bootloader, and installed CM 12.1 thinking it would get rid of the problem, it didn't. I think the problem is in the boot partition now. I also flashed the splash screen, and the boot animation. the problem is still there, EVEN after returning this phone back to stock to RMA it. the problem is still there.
Rattraps123 said:
I think so, I tried to fix it, flash with 2.20.40.97 Four times now, the problem is still there, rooted, unlocked bootloader, and installed CM 12.1 thinking it would get rid of the problem, it didn't. I think the problem is in the boot partition now. I also flashed the splash screen, and the boot animation. the problem is still there, EVEN after returning this phone back to stock to RMA it. the problem is still there.
Click to expand...
Click to collapse
I contacted Asus and I have to send my phone in. If you haven't dropped your phone, Asus will overnight you a new one for $25. I dropped my phone so they will repair it free of charge if the damage from the drop isn't what caused the issue. Otherwise I'm going to have to pay.
Hi everyone. I really get creazy. After flash vendor image by using flashify my nexus 5x continue to bootloop even after a factory reset with nexus root toolkit. It's stuck after the google logo then restart.
TWRP does it start.
If I try to install cm 13 it's stuck in google logo.
http://forum.xda-developers.com/nexus-5x/help/nexus-5x-stuck-google-screen-wont-boot-t3457981
http://forum.xda-developers.com/nexus-5x/help/nexus-5x-bricked-solutions-t3464569
According to Google, its a hardware issue.
jaeisber said:
http://forum.xda-developers.com/nexu...-boot-t3457981
http://forum.xda-developers.com/nexu...tions-t3464569
According to Google, its a hardware issue.
Click to expand...
Click to collapse
Why you say that? The recovery start, there's no way to fix this problem?
mr.banana said:
Why you say that? The recovery start, there's no way to fix this problem?
Click to expand...
Click to collapse
I said that because that is what a Google employee communicated out in the URL referenced in those other posts I linked to. Even though you can boot in to recovery, the system will still not start after reflashing 7 or even going back to 6.0.1. You may get it online for a short period of time as some have reported, but within a day or so it usually reverts back to the bootloop. Only known fix at this point is a warranty replacement.
jaeisber said:
I said that because that is what a Google employee communicated out in the URL referenced in those other posts I linked to. Even though you can boot in to recovery, the system will still not start after reflashing 7 or even going back to 6.0.1. You may get it online for a short period of time as some have reported, but within a day or so it usually reverts back to the bootloop. Only known fix at this point is a warranty replacement.
Click to expand...
Click to collapse
The link you post doesn't go..
mr.banana said:
The link you post doesn't go..
Click to expand...
Click to collapse
fixed links in my original post.
jaeisber said:
fixed links in my original post.
Click to expand...
Click to collapse
Thank you for the answer... good times those of the nexus 5..
jaeisber said:
I said that because that is what a Google employee communicated out in the URL referenced in those other posts I linked to. Even though you can boot in to recovery, the system will still not start after reflashing 7 or even going back to 6.0.1. You may get it online for a short period of time as some have reported, but within a day or so it usually reverts back to the bootloop. Only known fix at this point is a warranty replacement.
Click to expand...
Click to collapse
Just because SOME bootloops are hardware issues that doesn't mean ALL bootloops are hardware issues.
In particular if you have never flashed anything other than letting OTAs run and don't have unlocked bootloader, then it is more than likely hardware issue.
However if you have bootloader unlocked and have been flashing stuff, the chances that this is not hardware issue increase tremendously.
You seem to be posting on every single bootloop thread that this is a hardware issue based on taking a post from a google representative and applying it out of context.
sfhub said:
Just because SOME bootloops are hardware issues that doesn't mean ALL bootloops are hardware issues.
In particular if you have never flashed anything other than letting OTAs run and don't have unlocked bootloader, then it is more than likely hardware issue.
However if you have bootloader unlocked and have been flashing stuff, the chances that this is not hardware issue increase tremendously.
You seem to be posting on every single bootloop thread that this is a hardware issue based on taking a post from a google representative and applying it out of context.
Click to expand...
Click to collapse
I arrived at this conclusion because I have tried several things ...
sometimes my oneplus 3 restart without reason, i have installed the oxygenOS 3.2.7 do someone else have this issue , its just me or? ill post a battery log also.
its really annoying and dunno what do =/
My congrats for the great autonomy ?
The info you've sent are not enough to analyze your reboot issues.
1) Have you rooted your device?
2) If yes, are you running SuperSU, Kingroot, Phh's Superuser? What version?
3) What the apps that are getting root permissions?
4) Are you using Xposed? What version (e.g. v86.6 systemless with Magisk v8, the v86 stock)?
5) Have you tweaked or replaced the stock kernel?
Simone98RC said:
My congrats for the great autonomy
The info you've sent are not enough to analyze your reboot issues.
1) Have you rooted your device?
2) If yes, are you running SuperSU, Kingroot, Phh's Superuser? What version?
3) What the apps that are getting root permissions?
4) Are you using Xposed? What version (e.g. v86.6 systemless with Magisk v8, the v86 stock)?
5) Have you tweaked or replaced the stock kernel?
Click to expand...
Click to collapse
everything is stock, still new of android so and ty
athais said:
everything is stock, still new of android so and ty
Click to expand...
Click to collapse
Much strange.
I'm having an heavily modded OP3 with OOS v3.2.7, never encountered instability.
You should try factory reset asap, there's nothing you may do, since device is completely stock and works for most users.
I can't give you more help, sorry ?
Simone98RC said:
Much strange.
I'm having an heavily modded OP3 with OOS v3.2.7, never encountered instability.
You should try factory reset asap, there's nothing you may do, since device is completely stock and works for most users.
I can't give you more help, sorry ?
Click to expand...
Click to collapse
do you think an update could resolve the issue? in case i could wait an OTA update and if dont fix this issue try a factory reset
athais said:
do you think an update could resolve the issue? in case i could wait an OTA update and if dont fix this issue try a factory reset
Click to expand...
Click to collapse
Not, because OOS is working well for most users, so there is no "fix reboot issues" in any todo list.
Go with factory reset, when you find the needed time.
If problems still persist, contact OnePlus and explain the issue.
I think that some upgrade maybe the cause of your troubles, due to massive change of stuff that the end-users can never see.
You know that Samsung updates often make device slower or keep crashing some system app?
Why excluding that OnePlus have done (involuntary) the same?
Updates are not always guarantee of stability, especially with firmware different than Google stock.
Simone98RC said:
Not, because OOS is working well for most users, so there is no "fix reboot issues" in any todo list.
Go with factory reset, when you find the needed time.
If problems still persist, contact OnePlus and explain the issue.
I think that some upgrade maybe the cause of your troubles, due to massive change of stuff that the end-users can never see.
You know that Samsung updates often make device slower or keep crashing some system app?
Why excluding that OnePlus have done (involuntary) the same?
Updates are not always guarantee of stability, especially with firmware different than Google stock.
Click to expand...
Click to collapse
thank you for all yours advice man, i came up with , waiting next OTA, then try factory reset, and if not solve this issue well, OP support is the way suppose , thank you again !
btw just asking in developer options i saw suspension mode active, can be this that cause truble ?
Flash another room
Seems to be an issue with OOS, I had the same problem, and flashed MIUI 8 and had 0 reboots. But when I flashed Fredoom OS based on OOS 3.2.7 my phone kept rebooting.
athais said:
sometimes my oneplus 3 restart without reason, i have installed the oxygenOS 3.2.7 do someone else have this issue , its just me or? ill post a battery log also.
its really annoying and dunno what do =/
Click to expand...
Click to collapse
Are you using a case? I had a cheap eBay clear case on my phone and it wasn't moulded properly over the power button, there was no indent on the inside for the button to sit in so it used to turn off in my pocket and back on later and produced battery graphs similar to yours.
Hope this is a help.
athais said:
thank you for all yours advice man, i came up with , waiting next OTA, then try factory reset, and if not solve this issue well, OP support is the way suppose , thank you again !
btw just asking in developer options i saw suspension mode active, can be this that cause truble ?
Click to expand...
Click to collapse
Did your problem solved? I am having same problem.
I have the same problem. I am currently on 3.2.8 and also had this problem on beta 9. Few days ago it happened in front of me, the phone was on the desk nothing running in the background. That was kind of the soft reboot, didn't triggered my locked sim, (my sim card is locked needs to enter PIN when phone startup) and after that I checked Settings=>About Phone=>Status, the uptime didn't affected too, seemed nothing was happened. I think this also happened to some other people but they just didn't realize it.
Karthi91 said:
Did your problem solved? I am having same problem.
Click to expand...
Click to collapse
Are you running the latest 3.2.8 and if yes have you tried a factory reset?
Sent from my OnePlus3 using XDA Labs
bonham1988 said:
Are you running the latest 3.2.8 and if yes have you tried a factory reset?
Click to expand...
Click to collapse
Yes.. I'm on 3.2.8 and did factory rest also. No use
---------- Post added at 06:35 AM ---------- Previous post was at 06:32 AM ----------
athais said:
sometimes my oneplus 3 restart without reason, i have installed the oxygenOS 3.2.7 do someone else have this issue , its just me or? ill post a battery log also.
its really annoying and dunno what do =/
Click to expand...
Click to collapse
Same for me. Is your problem solved? Please help me. It is really annoying. I have Pin setup for restart so when boot happens in night, if no input for pin phone stays off.
Can this be related to SIM carrier:Radio drivers?
I dont think so.. Because i havent changed Sim
Karthi91 said:
I dont think so.. Because i havent changed Sim
Click to expand...
Click to collapse
Try using non 4G/LTE SIMS.
I am facing the same problem.
My device is at service center.
Day one:No reboots.I asked them to put some SIM & then check.
I did that after reading your post. No luck. Are they replacing it? How many days since it is in service center?
Facing problem from last 2 weeks.
I submitted once last week.They clean flashed older rom.Worked fine for one day,then reboots started again.
Then this technician had remote session and flashed the rom OnePlus3_16_A.17_161118(OOS 3.2.8):Reboot frequency went too high.
Had to go to Service center for diagnose. 2 days now.No proper response from them.
I had the same issue from several days now, wiped cache, did factory reset, wiped data, nothing worked, I read somewhere that let battery drain down to 0 and then full charge removes electricity or static from the phone, and that may cause random reboots, gonna try that
Belyakovni said:
I had the same issue from several days now, wiped cache, did factory reset, wiped data, nothing worked, I read somewhere that let battery drain down to 0 and then full charge removes electricity or static from the phone, and that may cause random reboots, gonna try that
Click to expand...
Click to collapse
Seriously? That sounds like one of those hilarious Microsoft Answers sort of posts! Running the battery down will not get rid of "electricity or static from the phone", apart from anything else the battery protection circuit would not allow the battery to drop to zero volts as it's not good for li-on batteries.
The Oneplus 3 seems to like to soft restart, mine sometimes decides to do it 3-4 times a night (rarely during the day) and then is fine for awhile. Tell tale sign is the battery graph showing large gaps in the usage pattern. I would suggest that there is an inherent firmware issue judging by the number of people reporting the same issue on a number of different forums.
Hello. Yesterday, I uploaded my Nexus 5X to Android 8 - official updated as appeared on my mobile´s screen. After completing the update and rebooting, I saw this message "can't load android system data corrupted". I have tried the adb sideload following the instructions at google´s developers site. It seemed that the configuration was correct, but when rebooting, same problem.
I´d appreciate if anyone can help me out. I would like to mostly recover my photos on the phone.
Thanks.
This happened to me today as well, though I have been running 8.0 since the end of August. By looking around, I came to the conclusion that its the bootloop of death problem. I think Google changed something in Oreo how the system uses the processor and thats why it happened now. I tried using the boot image which disables the 2 BIG cores, but that didnt work either. Right now I think that my phone is gone, and I am mad, because I cant even backup the data that was on there. You could try following these instructions: https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Maybe it will help you.
koostamas said:
This happened to me today as well, though I have been running 8.0 since the end of August. By looking around, I came to the conclusion that its the bootloop of death problem. I think Google changed something in Oreo how the system uses the processor and thats why it happened now. I tried using the boot image which disables the 2 BIG cores, but that didnt work either. Right now I think that my phone is gone, and I am mad, because I cant even backup the data that was on there. You could try following these instructions: https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Maybe it will help you.
Click to expand...
Click to collapse
Thanks, I am not so sure if I would know how to do that. Seems a little bit risky. Thanks for your reply.
Hi everyone,
I have an issue with my wife's OP3 that is driving me nuts.
Her phone runs stock OS without any changes but with an unlocked bootloader (just to be on the safe side i like to have an unlocked bootloader on all our devices).
I'm not sure if its related but I'm including it anyways she was playing a game on her phone and then she received a call and she answered it and tried to switch the call to speakerphone and the phone started rebooting right after booting the OS after 2-5 sec i would say "factory data reset" (see attached screenshot) and would reboot to the recovery.
then i would boot the phone again and the issue repeats itself.
so i used fastboot boot twrp.img to boot a recovery image and run a nadroid backup to a USB OTG just in case the phone is really hosed or whatnot.
I downloaded stock zip from oneplus's site and flashed it again from TWRP just to make sure its not some funky issue that happened to the os.
I even factory reset the phone from stock recovery and the issue would happen on the new phone setup wizard.
after a bunch of fiddling around I've flashed LineageOS 16 nightly and the phone boots normally and is fully usable but when i try to make or receive a call the phone app freezes and then crashes also sound doesn't seem to work when i try to play videos from youtube for example.
Any ideas what is the issue and how i can resolve it ?
thanks a bunch !!
-DM
the_mentor said:
Hi everyone,
I have an issue with my wife's OP3 that is driving me nuts.
Her phone runs stock OS without any changes but with an unlocked bootloader (just to be on the safe side i like to have an unlocked bootloader on all our devices).
I'm not sure if its related but I'm including it anyways she was playing a game on her phone and then she received a call and she answered it and tried to switch the call to speakerphone and the phone started rebooting right after booting the OS after 2-5 sec i would say "factory data reset" (see attached screenshot) and would reboot to the recovery.
then i would boot the phone again and the issue repeats itself.
so i used fastboot boot twrp.img to boot a recovery image and run a nadroid backup to a USB OTG just in case the phone is really hosed or whatnot.
I downloaded stock zip from oneplus's site and flashed it again from TWRP just to make sure its not some funky issue that happened to the os.
I even factory reset the phone from stock recovery and the issue would happen on the new phone setup wizard.
after a bunch of fiddling around I've flashed LineageOS 16 nightly and the phone boots normally and is fully usable but when i try to make or receive a call the phone app freezes and then crashes also sound doesn't seem to work when i try to play videos from youtube for example.
Any ideas what is the issue and how i can resolve it ?
thanks a bunch !!
-DM
Click to expand...
Click to collapse
Take a backup of your personal files and then wipe system, data, internal storage and both caches. Then flash OOS 5.0.8 and without adding any apps, check the calling function. If it still happens, then most likely a hardware issue.
tnsmani said:
Take a backup of your personal files and then wipe system, data, internal storage and both caches. Then flash OOS 5.0.8 and without adding any apps, check the calling function. If it still happens, then most likely a hardware issue.
Click to expand...
Click to collapse
If it's a hardware problem which part should I replace?
I already ordered a battery before this issue started and I was planning on replacing it once it gets here maybe I can replace one of the parts in order to resolve this issue
the_mentor said:
If it's a hardware problem which part should I replace?
I already ordered a battery before this issue started and I was planning on replacing it once it gets here maybe I can replace one of the parts in order to resolve this issue
Click to expand...
Click to collapse
You will need to replace the main board if the issue persist.
Same problem here
Hello mate, I've got the exact same problem with my wife's OP3. What did you do eventually? Did you find out? Please help. Thanks
New geek said:
Hello mate, I've got the exact same problem with my wife's OP3. What did you do eventually? Did you find out? Please help. Thanks
Click to expand...
Click to collapse
Hmmm quite strange that you're having the same issue.
I didnt find a solution yet i gave her a temp replace phone that we had in a drawer somewhere.
Did your wife do anything out of the ordinary when it happened? are you having the same issue that LOS works but stock rom shows factory reset?
thanks.
-DM.
the_mentor said:
Hi everyone,
I have an issue with my wife's OP3 that is driving me nuts.
Her phone runs stock OS without any changes but with an unlocked bootloader (just to be on the safe side i like to have an unlocked bootloader on all our devices).
I'm not sure if its related but I'm including it anyways she was playing a game on her phone and then she received a call and she answered it and tried to switch the call to speakerphone and the phone started rebooting right after booting the OS after 2-5 sec i would say "factory data reset" (see attached screenshot) and would reboot to the recovery.
then i would boot the phone again and the issue repeats itself.
so i used fastboot boot twrp.img to boot a recovery image and run a nadroid backup to a USB OTG just in case the phone is really hosed or whatnot.
I downloaded stock zip from oneplus's site and flashed it again from TWRP just to make sure its not some funky issue that happened to the os.
I even factory reset the phone from stock recovery and the issue would happen on the new phone setup wizard.
after a bunch of fiddling around I've flashed LineageOS 16 nightly and the phone boots normally and is fully usable but when i try to make or receive a call the phone app freezes and then crashes also sound doesn't seem to work when i try to play videos from youtube for example.
Any ideas what is the issue and how i can resolve it ?
thanks a bunch !!
-DM
Click to expand...
Click to collapse
try using msm v3.0 tool fixes most problems not hardware though
the_mentor said:
Hmmm quite strange that you're having the same issue.
I didnt find a solution yet i gave her a temp replace phone that we had in a drawer somewhere.
Did your wife do anything out of the ordinary when it happened? are you having the same issue that LOS works but stock rom shows factory reset?
thanks.
-DM.
Click to expand...
Click to collapse
No, She did not do anything out of the ordinary. But weirdly I have exactly the same things happening. Lineage works but no sound. Everything else factory resets. I have tried quite a few ROM'swithout any luck. So far the only ROM which worked for some time(1day) was 6.0.1 . I have spent quite a long time on this flashing various ROM and dont know what to do now.
New geek said:
No, She did not do anything out of the ordinary. But weirdly I have exactly the same things happening. Lineage works but no sound. Everything else factory resets. I have tried quite a few ROM'swithout any luck. So far the only ROM which worked for some time(1day) was 6.0.1 . I have spent quite a long time on this flashing various ROM and dont know what to do now.
Click to expand...
Click to collapse
Update: @ireaper4592 might have a point here. I have gone one level up and I tried msm v3.0 tool, thus doing a complete reinstall including firmware. The factory resetting stopped but the sound was not working (I thought that it could be the ROM and the security patches). So I updated to the latest ROM available from Oneplus and evrything has been working since. I did this last night so not sure how long this is going to stay like that. I will give it some time and update later. Wife is using it now!
what you will need to do is download the oneplus 3 recovery tool and put the phone into qualcolm mode and restore the phone that way. here is a link https://www.androidexplained.com/oneplus-3-unbrick-return-stock/
New geek said:
Update: @ireaper4592 might have a point here. I have gone one level up and I tried msm v3.0 tool, thus doing a complete reinstall including firmware. The factory resetting stopped but the sound was not working (I thought that it could be the ROM and the security patches). So I updated to the latest ROM available from Oneplus and evrything has been working since. I did this last night so not sure how long this is going to stay like that. I will give it some time and update later. Wife is using it now!
Click to expand...
Click to collapse
its really good to know.
did you have to wipe the internal storage for this process to work ?
Do you have a guide that you've used to get this working?
Thanks in advanced.
-DM
the_mentor said:
its really good to know.
did you have to wipe the internal storage for this process to work ?
Do you have a guide that you've used to get this working?
Thanks in advanced.
-DM
Click to expand...
Click to collapse
That tool/procedure will reset your phone. So you will lose everything on the phone. Take a backup beforehand.
The link posted in the post above yours contains the guide as well as the tools. It also has links to the original guide here on XDA.
tnsmani said:
That tool/procedure will reset your phone. So you will lose everything on the phone. Take a backup beforehand.
The link posted in the post above yours contains the guide as well as the tools. It also has links to the original guide here on XDA.
Click to expand...
Click to collapse
I cant believe it i was sure this was a hardware issue which ended up being a software one that the MSM tool fixed.
When I have a few minutes to spare i'll write a full post on how I ended up resolving it with step by step instructions and how I did it without any dataloss.
Thank you for all your help!
-DM
the_mentor said:
I cant believe it i was sure this was a hardware issue which ended up being a software one that the MSM tool fixed.
When I have a few minutes to spare i'll write a full post on how I ended up resolving it with step by step instructions and how I did it without any dataloss.
Thank you for all your help!
-DM
Click to expand...
Click to collapse
Please share the guide as I am also suffering with same problem.
Still not working
the_mentor said:
I cant believe it i was sure this was a hardware issue which ended up being a software one that the MSM tool fixed.
When I have a few minutes to spare i'll write a full post on how I ended up resolving it with step by step instructions and how I did it without any dataloss.
Thank you for all your help!
-DM
Click to expand...
Click to collapse
I was about to update here with good news but wife's phone went back to restart loop the next day. I am not sure but probably triggered by her installing whatsapp and facebook. I put the phone away because I have already spend quite a lot of time behind this. Is your's still going? Please list the step by step procedure. Thanks
download from here https://mega.nz/#!zsdnkCDA!UyJRwbJK6kHTDpmesBYao0knaOTwbgu4dSiokV1XLYU then turn off phone run tool,connect phone with volume up pressed,should have a com in the list if so just click start thats it and wait for it to turn green or device restart