Database Develop

[Q] DS7 Unstable keeps crashing

Hello All,
I'm fairly certain there isn't another thread asking this question, if I overlooked it I apologize in advance. Now to the point, I have a dell streak 7 and I have been having some stability issues with it for about the last week. What was happening is I was running Android 2.2.2 and my system would crash randomly eventually it wouldn't start back up. I tried doing a factory restore several times this didn't work so I re-flashed to restore the original file system and I installed the T-mobile system by mistake. I played around with this for a little bit and every thing seemed fine. So I decided to upgrade to 3.2 honeycomb, I flashed the DS7 did all of the set up steps and started reading about rooting the device (I didn't start any of the steps). While it was sitting next to me in sleep mode I noticed it just randomly reset itself and started booting up. I looked around in it and nothing seemed to be changed, so I powered it off and powered it back on to see if it would freeze up and crash again. it didn't so I put it back in sleep mode and kept reading. then the side lights came on and it froze up. I was able to get it to boot by going into recovery mode and then selecting boot normally. So my question is, is this some sort of hardware issue or something that I am doing wrong? I don't think it's hardware but I could be mistaken. Also, has anyone else had an issue like this and if so is there a known fix? I am going to try re-flashing to the original file system again and replace the restore .img and see if this helps. Also, I'm not sure if my DS7 is the mobile version or wifi only version. I entered the service tag at DELL's website and it said I had the mobile version, however it didn't have the t-mobile start up animation before I flashed it the first time and in the sim card slot there is a black piece of plastic or card (IDK which) lodged in there and it wont come out. Any help or advice on this would be greatly appreciated .
Thanks in advance-Woulfenstien
OK I'm pretty sure i got it solved. what I did was I re-flashed everything. I re-flashed the boot.img, the system.img, and the recovery.img using fastboot and then i re-flashed whole system with nvflash. It's been a couple of hrs. and this has seemed to work so far. I upgraded back to 3.2 honeycomb and rooted the device with no problems so far. If any other issues arise I will post them here along with what i did to fix it. I would also like to thank everyone on this forum who has posted the tutorials, it was a huge help I wouldn't have been able to fix my DS7 with out all of your help.
Thanks again-Woulfenstien

[Q] Sprint HTC One reboot issue

I got a Sprint HTC One last week, rooted it, s-offed it and flashed several ROMs on it.
My problem is that in every ROM I've tested, the phone reboots after a couple of minutes.
Here are the ROMs I've tried so far:
- CLEAN ROM SPR 2.5
- CM-10.1-20130714-NIGHTLY-m7spr
- MIUI_m7wls_signed_07042013
- Slim-m7spr-4.2.2.build.7-OFFICIAL
- Sprint_HTC_One_1.29.651.10_Stock_Deodexed
- Sprint_HTC_One_1.29.651.10_Stock_Odexed_05.17.13
- Stock_w_Goodies_One_1.06
- viperROM_One_v1.1.0
I'm using TWRP 2.5, advanced wiping: dalvik, cache, data, system before flashing the ROM.
Does anyone have sugestions?

Hi bro...
There's another thread talking about that:
http://forum.xda-developers.com/showthread.php?t=2344478

alexyomar said:
Hi bro...
There's another thread talking about that:
http://forum.xda-developers.com/showthread.php?t=2344478
Click to expand...
Click to collapse
I guess that's a slightly different problem then mine.
My phone is S-OFF already and I've wiped and flashed almost every single ROM out there and the phone reboots (doesn't shutdown) every 2 minutes...
After I read some other similar issues, I'm guessing I'll have to use a RUU tool to fix the problem. The other problem is that I only have Mac and Linux...

I've read a post advising to copy the ROM file to the root of the phone's internal storage in order to do a proper flash.
Since I was always flashing the roms directly from an external usb thumb drive, I thougt it was a good idea.
I copied Android Revolution 2.5 to the phone's memory, wiped everything and flashed it. Installation whas OK so I rebooted. When selecting the wi-fi network on the initial setup I received a message saying "avoiding poor signal network" even thoug my router was about 10ft from me. After finishing the initial setup I rebooted the phone and then it got stuck hard.
Even when pressing the power button for over 20 second it didn't shut down. Now I'm waiting for the battery to die so I can see what happens on the next boot.
Again, if someone can help me on this situation, I'll appreciate it...

1alemao said:
I've read a post advising to copy the ROM file to the root of the phone's internal storage in order to do a proper flash.
Since I was always flashing the roms directly from an external usb thumb drive, I thougt it was a good idea.
I copied Android Revolution 2.5 to the phone's memory, wiped everything and flashed it. Installation whas OK so I rebooted. When selecting the wi-fi network on the initial setup I received a message saying "avoiding poor signal network" even thoug my router was about 10ft from me. After finishing the initial setup I rebooted the phone and then it got stuck hard.
Even when pressing the power button for over 20 second it didn't shut down. Now I'm waiting for the battery to die so I can see what happens on the next boot.
Again, if someone can help me on this situation, I'll appreciate it...
Click to expand...
Click to collapse
press the buttons while holding phone under a bright light and it will reboot, if that rom was a 4.2.2 rom from the intl. forum you're going to have to ruu it.

Aldo101t said:
press the buttons while holding phone under a bright light and it will reboot, if that rom was a 4.2.2 rom from the intl. forum you're going to have to ruu it.
Click to expand...
Click to collapse
This!
Sent from my HTCONE using xda app-developers app

I've only used Sprint ROMs but still got those freaking reboots. Only by using RUU (provided by viperboy) I managed to solve the reboot issue.
Now I'm waiting for a software SIM Unlock solution, since I'm in Brazil an cannot unlock it OTA.
I'll post an update here as soon as I have a solution...

T mobile note 4 restart, and power issues

I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.

Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
-Vatsal

Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
sounds like the same software issue I had. Idk what happened but the internal memory failed on my note 4. Have you experienced constant freeze ups? also have you gone into download mode with an error that says "mmc_failed can't boot"? It was something along the lines of that.

Re:
alfadog77 said:
sounds like the same software issue I had. Idk what happened but the internal memory failed on my note 4. Have you experienced constant freeze ups? also have you gone into download mode with an error that says "mmc_failed can't boot"? It was something along the lines of that.
Click to expand...
Click to collapse
Yes I have those same issues. I am getting a new phone but I have to give this one to someone else and I need it in good shape to give it to them. Do I need to just buy a replacement or is there any way I can get it fixed?

Enalay527 said:
Yes I have those same issues. I am getting a new phone but I have to give this one to someone else and I need it in good shape to give it to them. Do I need to just buy a replacement or is there any way I can get it fixed?
Click to expand...
Click to collapse
Have you tried to update to the latest firmware? DOK2 fixes a lot of issues including the memory leak.
Sent from my SM-N910T using Tapatalk

aaldiar said:
Have you tried to update to the latest firmware? DOK2 fixes a lot of issues including the memory leak.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I updated it ota then on Samsung kies with the latest firmware. Everything works fine except the power off issues.

I think this is a common 5.0.1 issue, same thing started happening to me after update. Gotta wait for update or back to 4.4.4.

Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
I would recommend downloading the full DOK2 firmware. You can find it in the below linked thread. Make sure you use the newest version of ODIN to flash it 3.10.7.
It should give the phone aq complete clean install of the firmware. Kies sometimes can be janky. It you are going to get rid of the phone the best is to do a full ODIN flash.
http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858

I been having the same issues ...even with full firmware flashed DOK2....I get internal memory failure. Hope someone finds a fix. Have to pull out battery, sim cards, and spen, then press all the buttons, thennnnn....put everything back to boot up. Power button won't work, and reboot won't reboot. It Just turns off. Sucks...I love this phone. Right now it's acting ok...occasionally I get freezes and major lag. Someone please help!

notufatjesus said:
I been having the same issues ...even with full firmware flashed DOK2....I get internal memory failure. Hope someone finds a fix. Have to pull out battery, sim cards, and spen, then press all the buttons, thennnnn....put everything back to boot up. Power button won't work, and reboot won't reboot. It Just turns off. Sucks...I love this phone. Right now it's acting ok...occasionally I get freezes and major lag. Someone please help!
Click to expand...
Click to collapse
I had this problem too except it got really really laggy and would constantly reboot anytime I tried to do anything. Best I could figure out was it was a problem with the internal sd. Called TMO tech support, told them I did factory reset, tried it without the sd card, blah blah blah. I said it's a hardware issue that is beyond my control and I don't feel like I should have to pay for it. They said well it sounds like you already did the work for us. I guess it was still under warranty but I got a new phone the next day and no problems since. Hopefully whatever was wrong they have fixed the issue by now but so far so good.
Definitely mention the mmc read fail error or whatever it says. All it cost me was a $5 charge. Give em a call.

I have the same problem, and it only happen when I update the phone to newest firwame, DOK2.
When I use COG1 firwame it very fast and easy use. but when I update DOK2 over Odin, I few very lag and usually restart the phone when I run a big application, then It can't restart after, just turn off.
And after that, can't turn on the phone. I had remove pin in 10s, pull in and it power on normal.
Sometime I turn on the power and the phone go into download mode with notice "mmc_fail can't boot".
Now I just only want to download my phone to old firwame, COG2 and use it normal, but the new firwame with new bootloader don't allow to download old bootloader. So sad
anyone can't show me how to download to COG2 firwame, Please....

tony yayo said:
I had this problem too except it got really really laggy and would constantly reboot anytime I tried to do anything. Best I could figure out was it was a problem with the internal sd. Called TMO tech support, told them I did factory reset, tried it without the sd card, blah blah blah. I said it's a hardware issue that is beyond my control and I don't feel like I should have to pay for it. They said well it sounds like you already did the work for us. I guess it was still under warranty but I got a new phone the next day and no problems since. Hopefully whatever was wrong they have fixed the issue by now but so far so good.
Definitely mention the mmc read fail error or whatever it says. All it cost me was a $5 charge. Give em a call.
Click to expand...
Click to collapse
Hello there, I'm having the same exact issue lately, phone is a Year old, and I think its failing, One question though!
Was your phone ever rooted? mine is, but I flashed the Stock DOK2, so its official with NO root now, but I think the Device status is CUSTOM not official, Also KNOX has tripped while rooting, would T Mobile honor a replacement? At least its on the Official OS with NO Root now.
Please enlighten me

Willy318is said:
Hello there, I'm having the same exact issue lately, phone is a Year old, and I think its failing, One question though!
Was your phone ever rooted? mine is, but I flashed the Stock DOK2, so its official with NO root now, but I think the Device status is CUSTOM not official, Also KNOX has tripped while rooting, would T Mobile honor a replacement? At least its on the Official OS with NO Root now.
Please enlighten me
Click to expand...
Click to collapse
Not really sure. Mine was never rooted. I've heard of plenty of people sending their rooted phones in with no problem.

thiennvbk said:
I have the same problem, and it only happen when I update the phone to newest firwame, DOK2.
When I use COG1 firwame it very fast and easy use. but when I update DOK2 over Odin, I few very lag and usually restart the phone when I run a big application, then It can't restart after, just turn off.
And after that, can't turn on the phone. I had remove pin in 10s, pull in and it power on normal.
Sometime I turn on the power and the phone go into download mode with notice "mmc_fail can't boot".
Now I just only want to download my phone to old firwame, COG2 and use it normal, but the new firwame with new bootloader don't allow to download old bootloader. So sad
anyone can't show me how to download to COG2 firwame, Please....
Click to expand...
Click to collapse
Make sure you are using the ODIN version 3.10.7 if you are using an older version of may be what caused the issue.
If you did use the newest Odin, then I would factory reset your device, but into twrp and wipe everything but external SD Card, boot back into download mode and flash the firmware again. Most likely a few files for messed up during your Odin flash and it messed up the process. Also make sure you are using the USB cord that came with the device.

I found the fix for this mmc_failed. Making a new thread for this.
---------- Post added at 06:11 AM ---------- Previous post was at 05:38 AM ----------
http://forum.xda-developers.com/showthread.php?t=3277144
Here's is the fix. Don't forget to hit Thanks button

New phone, bricked within 15 minutes!

Hey there fellow OP 3T owners,
I just received my brand new OP 3T and after painstakingly going through the Android / Google setup options, only then could I update the OS.
But it didn't. It bricked my phone within a minute of updating. Buttons and the screen are totally unresponsive.
When connected to my desktop PC, my OP 3T is not recognized. The phone is brand new and was in use only 15-20 minutes before I went for the official software update provided to me by OnePlus.
I just went and opened a service ticket to RMA the phone, though I hope I can somehow avoid this by unbricking the phone.
I don't mind losing all my data, but I hope I will be able to unbrick my phone without going through 12+ steps and using half a dozen unverified 3rd party firmware files?
I just want the official OS back, as I'm content already with Nova Launcher...
*edit* I solved the problem by using the official build OnePlus 3T OxygenOS 4.0.2, "Minimal ADB and Fastboot", the deletion of all other ADB drivers in the Device Manager (such as "LeMobile Android Device" > Android ADB Recovery interface), one restart and otherwise lots of unnerving, long button presses on my OP3T.
Conclusion: This is not what I expected how my first experience with OP would go !!

https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try out this unbrick process, I've bricked my phone twice (put into bootloop into twrp), this put me back to stock and up and running again.

If you can get to fastboot or recovery, you are not bricked.

SlimJ87D said:
If you can get to fastboot or recovery, you are not bricked.
Click to expand...
Click to collapse
I don't know what that is? I just care about how to be able to recover.
Right now I managed to restart, but it only shows the OP logo and the "powered by android" signage, both in white...

Mine did the same thing after 3 weeks. Couldn't get it to turn on. Sent it back to Oneplus on an RMA, turned out the motherboard was bad. Once I got it back, there hasn't been an issue. Working great now. That might be the your problem.

My phone doesn't turn on at all now meanwhile. I managed to install that Qualcomm driver somehow, but it went downhill from there fast!

I have the exact problem the OP has while trying to upgrade the OS, 100% stock. I downloaded the OTA and tried to install the new OS, but it froze seconds into installing it. Just would not go forward. "ADB devices" doesn't recognize the phone. Was able to get into fastboot but bootloader and firmware are both blank. I did a factory reset, but still nothing. I can see the OnePlus logo when I turn the phone on but that's it. Is there anyway I can push something to the phone to make it work again? Thanks.
https://goo.gl/photos/fCNGtautw2uiEeyq6

The biggest issue I have right now with unbricking my phone is, that I simply do not have "USB debugging" activated, nor anything else, as I never even had the chance to do so, as I unfortunately applied the update right away after my first startup.

Thank you.
Haunt3r said:
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try out this unbrick process, I've bricked my phone twice (put into bootloop into twrp), this put me back to stock and up and running again.
Click to expand...
Click to collapse
I tried the link you provided and it worked like a charm. I had exactly the same problem as the OP with the phone freezing while doing an OTA update and the ToolKit provided was able to unbrick my phone.
After unbricking the phone, I was able to upgrade the ROM to 7 using OTA with oneplus3toxygen_28_170114, download size was 1434MB.
Thanks.

Warranty..?

Hamiltoe said:
Warranty..?
Click to expand...
Click to collapse
What's it matter? OnePlus customer service is abysmal. The worst customer service I've ever experienced.

[support] OP3T will not turn on at all after flashing OOS Beta 9 after a soft-brick

Hello everyone. I updated my rooted OP3T (with TWRP installed for recovery) to OOS 4.0.1(I think? I know for sure it was 4.0.x) a week or so ago using a VPN as I live in the US and today I got the new update for whatever version that was about 30 mb, and after I rebooted I got stuck booting into TWRP so I followed the guide linked underneath here and got up to step 12 (flashing beta 9) and after swiping to restart my phone will not turn on in any way, shape, or form. Whenever I plug it in/unplug it from my computer I'll still get the Win10 device connected/disconnected sound and if I hold the power button for long enough while it's plugged in I'll get another device connected sound or disconnected, usually followed by the opposite sound. There doesn't seem to be a pattern to the sounds, but if anyone knows what's happening I really need help with this as it's the only phone I was able to afford and if it's bricked I don't know if I have the money for another one. Thanks
https://forum.xda-developers.com/showpost.php?p=70102813&postcount=5

Lol no wonder your phone doesn't work anymore. You flashed the beta to the OP 3 onto your 3T. Use this to fix your phone.
Edit: Sorry if this was of use to some people when it was deleted.

Just Passing By said:
Lol no wonder your phone doesn't work anymore. You flashed the beta to the OP 3 onto your 3T. Use this to fix your phone.
Click to expand...
Click to collapse
I tried to use that thread, but my phone wouldn't show up underneath Unknown Devices, in fact unknown devices would never come up at all. my pc is still in test mode from this :/

Don't worry if it doesn't appear under unknown devices. Just use the tool. A lot of what the instructions say is unnecessary. Just make sure that when you plug in your phone that one of the ports becomes "active" (I haven't had to use this tool in months, so I'm not sure exactly what it's supposed to say exactly) and press the start button.
Edit: Sorry if this was of use to some people when it was deleted.

ok. I 'll download the tool and get back to you after trying it.
edit:that worked! you are my new favorite person.
thank you so much )))))))))

Deleted

WAIT
Just Passing By said:
Deleted
Click to expand...
Click to collapse
WHY IS THIS DELETED? IM having the same problem what did you do please save me as well

Sounds like you flashed the wrong version of Oneplus 3 firmware to your phone. Do you have a 3 or a 3t? If you flash the incorrect one you will get exactly the unbootable state you describe. In that case you will have to use Qualcomm MSM Downloader tool to flash back the correct ROM and firmware partitions to get it running again. Just download the correct MSM recovery package for your phone and follow the instructions in the thread.