Develop Bugs

Help! Phone not bricked, but won't boot.

Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?

Try flashing the stock tar in odin if nothing else works.

DroidGnome said:
Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?
Click to expand...
Click to collapse
Just flash the stock tar ur downloading in Odin. Ur fine even if you managed to Bork recovery as long as u can still get into dl mode ur ok

I've haven't seen this problem on the Sprint variant yet but it definitly sounds like it's fixable
Like others have pointed out, since you can get into Download mode fine flash the Stock Odin tar file found here
When you boot up I would consider doing a data wipe (Factory Reset option in Settings>Back up and reset) but that's up to you

Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure

DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium

DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
Ya Ive seen some build.prop changes mess things up. Luckily you could get back up.
Fun feeling huh! lol

fergie716 said:
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store

DroidGnome said:
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store
Click to expand...
Click to collapse
Glad to hear you're up and running again!!
Best excuse ever to Sprint is when I woke up it was like that haha

Sudden Boot Loops - I'm Lost

I've been using my Galaxy Nexus for a month or so, with the official JB ROM (JR30C or whatever, deodexed and rooted) and today I opened Gmail.
That's it. I opened GMail, switched accounts, and my phone has been bootlooping ever since.
I wiped everything in CWM multiple times and reflashed it, and I can't get the phone to do anything else.
Any clues?

Do you have a working nandroid? Have you tried flashing a different ROM?
Allons-y

Xfanatic said:
Do you have a working nandroid? Have you tried flashing a different ROM?
Allons-y
Click to expand...
Click to collapse
I do not have a working NANDROID. I wasn't sure about the Internet policies at work, but it looks like I can at least make it on here, I'm not sure I'll be able to download another ROM.
I'm confused though, I mean I know it would help to try as many options as possible (to fix it) - but this ROM has been working for weeks. And the phone died randomly, not due to a recent file change or a botched program. The only boot loops I've experienced before were on the Nexus One, and it was always due to a buggy/bad flash or a corrupted ROM download - this one just developed epilepsy on its own...

Here's my plan, since these are the only things I can manage to download due to restrictions on Internet usage at work.
Factory 4.1.1 takju image from here : https://developers.google.com/android/nexus/images#takju
Modified ODIN software here: http://forum.xda-developers.com/showthread.php?t=1586807
ODIN won't rewrite my bootloader, recovery, or userdata, since I already OEM unlocked, but will reflash a stock image.
EDIT: ODIN won't do anything with my device. Trying this ROM instead:
http://forum.xda-developers.com/showthread.php?t=1801664 was using bigxie OTA before.

is your (sd)storage recognized? thus is a similar symptom to when the stirage goes bad.

Hook the phone up to adb, boot it, and let logcat run. Maybe that will turn something up.
Sent from my Galaxy Nexus using Tapatalk 2

simms22 said:
is your (sd)storage recognized? thus is a similar symptom to when the stirage goes bad.
Click to expand...
Click to collapse
Hmm, you know, I'm not able to find the option to mount to USB in CWM...and just in case I forgot where that is, when I plug it in, I get the "hardware failed" noise from Windows and not the usual friendly "plug in" sound.
infazzdar said:
Hook the phone up to adb, boot it, and let logcat run. Maybe that will turn something up.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm at work, and I only have my work computer. Group/secpolicy won't allow me to install anything, no admin rights, etc.
Would it even do anything? The phone barely makes it through one second of the boot animation before it loops.

sheik124 said:
Hmm, you know, I'm not able to find the option to mount to USB in CWM...and just in case I forgot where that is, when I plug it in, I get the "hardware failed" noise from Windows and not the usual friendly "plug in" sound.
Click to expand...
Click to collapse
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.

Zepius said:
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Click to expand...
Click to collapse
Oy. Then how do I get another ROM on here? fastboot/adb?

sheik124 said:
Oy. Then how do I get another ROM on here? fastboot/adb?
Click to expand...
Click to collapse
Adb push.
Sent from my Galaxy Nexus using Tapatalk 2

Zepius said:
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Click to expand...
Click to collapse
sheik124 said:
Oy. Then how do I get another ROM on here? fastboot/adb?
Click to expand...
Click to collapse
Got more than one additional ROM on there via adb/recovery - my clue that CWM hasn't actually been able to do anything since the phone start looping is I'm still getting my custom boot animation.
I'm using the toolkit to reflash a stock image now. What a mess.
Even reflashing a stock image via fastboot did nothing. WTF happened to my phone? Won't stay on long enough to get a logcat

I'm having the same problem as this guy:
http://forum.xda-developers.com/showthread.php?t=1827685&page=2
I just got finished trying to flash 4.1.1 using ODIN. It still shows me the custom animation from bigxie's ROM (which has supposedly since been overwritten 2-4x times).
Screw you Samsung...this phone is a month old, I flashed -once- to rooted Jelly Bean, and the phone dies when I open the GMail app.
EDIT: WTF - I write screw you Samsung, it boots to the Welcome screen! Just long enough for me to see that my files aren't on it anymore, then it bootloops again. And again. Now it's re-stuck in a bootloop.
And now I'm at the homescreen. I can't rely on this thing like this...is my flash dying or something?

Nobody?
It worked long enough for me to re-enter all of my different Google account information and now it's dead again. Now it only flashes the boot animation for a split second for bootlooping.

I'm thinking of a hardware defect.
Beamed from my Grouper

Mach3.2 said:
I'm thinking of a hardware defect.
Beamed from my Grouper
Click to expand...
Click to collapse
Mee too. As you can see from my signature, I gave up and bought a One S yesterday night from Craigslist. Feels like a true successor to the Desire / N1. It's nice to finally have an AMOLED screen that actually seems color calibrated after the ugly mess that was my RAZR and my less than perfect GNex. It's a damn shame how much more painless flashing a recovery was on this thing.
Sent from my HTC VLE_U using xda app-developers app

For all the flashers here for the T989

The whole process is pretty simple on what I have done. I will explain my situation here and my question that has got be baffled.
So it all started about two weeks ago, where I was flashing LiquidSmooth on my phone. I had a Touch-type CWM. It isn't mega old but it's pretty old for CWM, I haven't updated in a while (as i've seen there are updates to recent ones).
Anywho, I did a complete wipe, used the darkside wipe, alongside with the darkside cache wipe.
I think this was my fault, so please correct me anyone if I am wrong here. I accidentally hit "reboot phone" instead of "reboot bootloader"
I got a permabrick from this whole ordeal. It was a permabrick because It said QHSUSB_DLOAD in the device manager, looking this up further confirmed my reasoning. I didn't want to jtag because that invovles removing the phone to pieces and soldering on wires etc. etc.
So I resorted to send it out to Samsung.
All is well when it came back. I made sure this time the whole phone was setup properly.
So I use Odin install for CWM and SU was installed via CWM. I install an older version of CWM (non-touch, i believe 1st revision as i've posted in one of the threads).
I kept stock ROM, everything was working okay and suddenly, KERPLUNK, it went back into permanent brick after I deleted cache partition, dalvik cache, and battery cache wipe. I didn't do fix permissions or anything, just hit reboot afterwards.
This is a super head scratcher here..... Anyone know where I went wrong?
Any insight here is greatly appreciated! :good:
P.S. I am now sending in my phone TWICE to Samsung for repairs.

If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it

LoopDoGG79 said:
If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it
Click to expand...
Click to collapse
I finally jumped in the water and flashed twrp! Yay!
Sent from my SAMSUNG-SGH-T989 using xda premium

All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium

rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
great call on that I had to educate a few users that the d2tmo is not for our phone but indeed the S3. Good catch on your part and it sounds like user error as well

LoopDoGG79 said:
If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it
Click to expand...
Click to collapse
Could you please educate me with a link referring to what TWRP is? Sorry, i'm still fairly new to the scene and all i've ever been educated upon is CWM.
suaverc118 said:
I finally jumped in the water and flashed twrp! Yay!
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Nice! What is TWRP and how is it like?
rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I've flashed the hercules ROM. I know this for sure because Liquidsmooth was working, it was extremely glitchy (playing games gave me pixelated actions sometimes, and using something like gameCIH/Game Guardian was unworkable). So i decided to ditch it and was getting ready to flash Jedi Mind Trick.
After the whole hard bricking ordeal, I decided to stick to stock rom, and even on that, I just flashed CWM and SU ONLY. Rebooted, and deleted the cache's (like i've posted to you) with absolutely no success. It baffled me that I bricked the phone AGAIN too!
playya said:
great call on that I had to educate a few users that the d2tmo is not for our phone but indeed the S3. Good catch on your part and it sounds like user error as well
Click to expand...
Click to collapse
Yes..... there is something wrong, i feel it is a user error also, but i'm very unsure where to even start
Once again, all of your insight is well appreciated! I just do not want to hardbrick my phone AGAIN and have to send it to Samsung. I am not allowed to even think of a replacement because this was a b-day present a year or two ago from my fiance.

You say that it is bricked again. Do you mean by that, that you cannot get into recovery?
Sent from my SAMSUNG-SGH-T989 using xda premium

XxGoKoUxX said:
Could you please educate me with a link referring to what TWRP is? Sorry, i'm still fairly new to the scene and all i've ever been educated upon is CWM.
Nice! What is TWRP and how is it like?
I've flashed the hercules ROM. I know this for sure because Liquidsmooth was working, it was extremely glitchy (playing games gave me pixelated actions sometimes, and using something like gameCIH/Game Guardian was unworkable). So i decided to ditch it and was getting ready to flash Jedi Mind Trick.
After the whole hard bricking ordeal, I decided to stick to stock rom, and even on that, I just flashed CWM and SU ONLY. Rebooted, and deleted the cache's (like i've posted to you) with absolutely no success. It baffled me that I bricked the phone AGAIN too!
Yes..... there is something wrong, i feel it is a user error also, but i'm very unsure where to even start
Once again, all of your insight is well appreciated! I just do not want to hardbrick my phone AGAIN and have to send it to Samsung. I am not allowed to even think of a replacement because this was a b-day present a year or two ago from my fiance.
Click to expand...
Click to collapse
Flash this in recovery, reboot recovery, and you will have TWRP!!
TWRP 2.3.1.1

DM_Sledge said:
You say that it is bricked again. Do you mean by that, that you cannot get into recovery?
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yes, it is perma-bricked, meaning the only method of fixing the brick is jtagg'ing
Upon plugging it into device manager, I get the prompt "QHSUSB_DLOAD" and phone doesn't even boot on no matter what combinations I make.
LoopDoGG79 said:
Flash this in recovery, reboot recovery, and you will have TWRP!!
TWRP 2.3.1.1
Click to expand...
Click to collapse
Thank you LoopDo, I will do this after I get my phone home again.

I have this phone, and none of the steps you listed would brick the device. Even with no ROM on the phone, you should still be able to get into recovery.
Is there something you aren't telling us?
Sent from my Galaxy Nexus using xda premium

Nope, wouldn't be a reason why I would lie because then the problem will never be resolved.... I'm kind of nervous on reflashing ONE more time after the phone comes home again....
The phone has been fixed once AGAIN, and it is in the process of being shipped back to me.
Phone will be home Wednesday and I will give it ONE more try
Wish me luck!
P.S. my PC has been glitchy lately, so that MAY or MAY NOT contribute to the permabrick, then again the brick doesn't happen until I flash stuff via CWM.
P.S.S. I've since re-installed Win 7 again, it hasn't been glitchy since

XxGoKoUxX said:
Nope, wouldn't be a reason why I would lie because then the problem will never be resolved.... I'm kind of nervous on reflashing ONE more time after the phone comes home again....
The phone has been fixed once AGAIN, and it is in the process of being shipped back to me.
Phone will be home Wednesday and I will give it ONE more try
Wish me luck!
P.S. my PC has been glitchy lately, so that MAY or MAY NOT contribute to the permabrick, then again the brick doesn't happen until I flash stuff via CWM.
P.S.S. I've since re-installed Win 7 again, it hasn't been glitchy since
Click to expand...
Click to collapse
You most likely flashed the Wrong Liquidsmooth ROM (incompatible Kernel), and it hard bricked the phone. It happened to me the same way, and I had to send it in for JTAG.

I have bricked my phone installing the Liquidsmooth ROM too. I downloaded the wrong ROM, though. The thread should have a big ****in warning to double check the ROM you are about to download, otherwise your phone is a toast. There were more people who bricked their phones by installing the Liquidsmooth.
Well, I got it back from the warranty and the phone looks good. Installed that Liquidsmooth again and played for a day. Tried other JB ROMs. Most of them are OK in terms of battery life and smoothness, but there is something wrong with the signal. People always say my voice isn't clear. I got tired of all this BS and testing new ROMs and went to back to ICS and won't look back, not anytime.
Don't use darkside scripts, btw. You don't need that anymore.

I'd like to say thank you for everyone's patience. All of your insight is more than helpful!
DroidDonX said:
You most likely flashed the Wrong Liquidsmooth ROM (incompatible Kernel), and it hard bricked the phone. It happened to me the same way, and I had to send it in for JTAG.
Click to expand...
Click to collapse
I might have, but the one i downloaded (which is still on the phone's memory card) is a hercules ROM. Either way on my second try there was a hard brick also, in return of which I had to resend it in. The second try was just simply: Odin---->CWM---->Root---->SU---->wipe cache partition+fix permissions+wipe dalvik cache via CWM (not the super scripts).
cipsaz said:
I have bricked my phone installing the Liquidsmooth ROM too. I downloaded the wrong ROM, though. The thread should have a big ****in warning to double check the ROM you are about to download, otherwise your phone is a toast. There were more people who bricked their phones by installing the Liquidsmooth.
Well, I got it back from the warranty and the phone looks good. Installed that Liquidsmooth again and played for a day. Tried other JB ROMs. Most of them are OK in terms of battery life and smoothness, but there is something wrong with the signal. People always say my voice isn't clear. I got tired of all this BS and testing new ROMs and went to back to ICS and won't look back, not anytime.
Don't use darkside scripts, btw. You don't need that anymore.
Click to expand...
Click to collapse
Thanks again for your insight I think i'm done with flashing for a little bit for now.... I kind of want as factory of a JB Rom as possible. :good:
If anyone has any idea where I can get that, please let me know as my Stock ICS is a bit laggy at times, with the facial recognition system, it lags even worse!

rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
that just happened to me today with liquid smooth. i had to unroot, flash stock, and start over. im pretty sure i got it from goo.im under hercules. unfortunate mislabeling? oh yeah, and if your phone shows anything other than nothing, youre not hard bricked. thats why its called Hercules, i think. ive been soft bricked so many times from dumb **** like. ****ing with the governors and all that **** cm gives you the option to do when there aint even a 1080p camera that works fully = / lol <3 Cm I Love Yew!! But yeah, odin will set you free!!!

Anyone have this issue?

So last night, I guess my phone was trying to download and install security update from samsung and failed. My battery died later cause it was low and after I recharged my phone and turned it on, my phone literally took a crap. Everything crashes even settings. Cant send a text out. Bluetooth wont turn on etc.
Now after I back up my photos somehow, what would be the best way to restore to keep root and CWM?
Settings-restore?
dl note 3 os then flash with CWM?
Thanks guys.

Hmmmm
steve45058 said:
So last night, I guess my phone was trying to download and install security update from samsung and failed. My battery died later cause it was low and after I recharged my phone and turned it on, my phone literally took a crap. Everything crashes even settings. Cant send a text out. Bluetooth wont turn on etc.
Now after I back up my photos somehow, what would be the best way to restore to keep root and CWM?
Settings-restore?
dl note 3 os then flash with CWM?
Thanks guys.
Click to expand...
Click to collapse
I did have a similar issue. My quick fix wasn't so quick though. I completely formatted, flashed stock ROM back, chainfire root, CWM to bootloader then you're free. I got my files from galaxynote3root.com
Sent From My Hyperdrive Note 3 SM-G900T

Jack Ketch said:
I did have a similar issue. My quick fix wasn't so quick though. I completely formatted, flashed stock ROM back, chainfire root, CWM to bootloader then you're free. I got my files from galaxynote3root.com
Sent From My Hyperdrive Note 3 SM-G900T
Click to expand...
Click to collapse
So its weird, after I let the phone stay on for like an hour, everything seems to load properly and nothing crashes. Planning on reformatting, but I am kind of worried on why this happened. I am on stock rom.

steve45058 said:
So its weird, after I let the phone stay on for like an hour, everything seems to load properly and nothing crashes. Planning on reformatting, but I am kind of worried on why this happened. I am on stock rom.
Click to expand...
Click to collapse
It's possible during your update critical files were missed do to power loss and were replaced on reboot? I unfortunately was not able to get passed the bootscreen to recovery or the system itself. So i was forced to divert back to stock firmware and start from the beggining. So if you run into any more issues you might start there. If you kept root all should be well i believe. :good:

Jack Ketch said:
It's possible during your update critical files were missed do to power loss and were replaced on reboot? I unfortunately was not able to get passed the bootscreen to recovery or the system itself. So i was forced to divert back to stock firmware and start from the beggining. So if you run into any more issues you might start there. If you kept root all should be well i believe. :good:
Click to expand...
Click to collapse
Well my phone didn't die when it was updating, the update failed well before that. I was just saying that after it did die and I turned it on, everything went downhill from there. Really weird

steve45058 said:
Well my phone didn't die when it was updating, the update failed well before that. I was just saying that after it did die and I turned it on, everything went downhill from there. Really weird
Click to expand...
Click to collapse
I have a backup of all my pictures on google + they give 15GO i have all my video and importants stuf backed up. When I have a problem with the phone hard reset and reinstall the rom. I use philz recovery is working like a charm to me

OP3 phone is un-usable please help!

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