Hi, I have a droid turbo that is driving me crazy, when the phone took the update to marshamallow, after a couple of weeks the wifi and signal had lost, sometimes when I restarted it or doing factory reset the networks worked, but always going to the same situation. I reflashed the stock 6.0.1 with rsd lite, it worked, but for a couple of days so I thought it was the motherboard, then I bought another one ($40 dollars) from a cracked screen turbo. That motherboard had 5.1.1 so it worked fine for a couple of days until the OTA came again and installed, it worked fine but a few days later the phone showed the same problems. I dont know what to do, I cant downgrade because the locked bootloader ( and sunshine is to expensive for me $25 dollars is to much in Mexico) and is the second motherboard !!! what is happening??? Please help me
U should have sunshined your device and installed a custom Rom/ modified stock with new kernel, because now being unrooted with a half-bricked device means there is pretty much nothing that can be done to fix that software issue
Einheit-101 said:
U should have sunshined your device and installed a custom Rom/ modified stock with new kernel, because now being unrooted with a half-bricked device means there is pretty much nothing that can be done to fix that software issue
Click to expand...
Click to collapse
but why this error is just happening to me? I dont find another users with 6.0.1 having the same issue, I repeat, I have 2 motherboards with the same problems that's to weird :/
I dont know man. Idk what you did or did not.
Related
Ok Kinda long but want to cover everything:
So I rooted my htc one m8 (sprint) about 6 months ago I have twrp recovery and I flashed android revolution 8. A few months later I installed android revolution 11 no problems with it what so ever. A cpl days ago I tried to flash android revolution 22 but had no luck just kept boot looping and I lost everything on my phone after some research It seems I wouldnt be able to go to kit kat 4.4.4 without going back to stock rom so I relocked my bootloader ran rom utility updater and flashed it back to stock and reset up my phone tried to flash over to android revolution again after unlocking bootloader and all that good stuff still did not work so just decided to go back to stick 4.4.4 kept bootloader locked and didn't re root my phone didn't see much of a need to at this point could only seem to use stock but anyway after a day or so of phone running just fine well today it wont connect to my mobile network or wifi (can't make or receive phone calls can't send or receive texts and am unabke to get any internet on my phone wont even connect to wif) I have even restored the phone from original back-up that I had also tried 2 other back-ups of stock roms the phone is pretty much just an mp3 player at this point sprint said everything was fine on their end nothing they can do all the icons are there for 4g and wifi and such the phone shows me its connected to sprint shows signal strength and all that so I don't know whats wrong and don't think htc will help me since I rooted it hopefully some one here can i'm
well I must be screwed if over 300 views on my post and not reply well that's what I get I guess
As far as I know ARHD is not Sprint compatible so you probably messed up your partitions.
RUU will fix it.
Only flash roms that are in the Sprint section.
Apart from compatibility off ARHD to Sprint M8 ... There is also that dreaded HTC service pack that was released on 11th Dec which screwed the network n Wi-Fi on my phone (stock Rom)
First time itty happened due to auto update install via play store and started working after I did multiple attempts at cache delete through TWRP
2nd time even after researching and knowing the service pack was the culprit I thought I should try...ending up with factory reset...so do check it
If you too had that service pack installed
Btw even htc acknowledges the sh#@ this update is causing to the phones and wants to collect more data... I don't know if anything else can be called a legit rip off or not...
BD619 said:
As far as I know ARHD is not Sprint compatible so you probably messed up your partitions.
RUU will fix it.
Only flash roms that are in the Sprint section.
Click to expand...
Click to collapse
I used ruu after I tried to flash it and messed everything up and everything worked fine after a cpl days of it working is when it started to have the networking issues I used ruu several times after and it didn't work still is there a different version I need?
Hi everyone, I really need some help with this otherwise my sp c5303 is scrap...
From the beggining, I buy a xperia sp on the three network in the uk but it accepted any sim
Unlocked bootloader, no problem
Flashed loads of ROMs with no issues.
Settled on stock deodexed ROMs. Had a happy phone.
Tried to update to the latest maybe 6 months ago, had a bad flash, bootloop.
Then wiped and reflashed previous set up.
Problem is, now the phone doesn't recognise my sim, its relocked the boot loader, simlock is all set to [] 0.
And that really sucks.
I have root access still, but no recovery.
Eventually I have regained access to recoveries and custom ROMs won't accept my sim either... Otheriwse works perfect
The phone is flawless, I have even taken it to be repaired physiccaly there's no faults but it won't accept any simcard. I have trawled the forums and nothing looks promising.
I have been using a moto g for a few months but its... Annoying, and the screens shattered. And it has problems with loudspeaker turning off and on rapidly...
The thing I am wondering is, could it be that the ftf file I used was from another country? Because I can't find one from the uk to try, although I expect that will only really change the default language choice.
Anything else I can try before I give up?
Please tell me its something achievable!
Thank you.
pictures
Here's some photos of the issue just so you have all the information
Hello!
For some reason my board got fried so I took it to the warranty and they sent me to a place to drop off my phone. They changed it for free (great) but they also rooted my phone and left me a 4.1 ROM instead of the stock 4.2 as I had. I'm now having troubles regarding charging it (it's not detecting the cable correctly sometimes and think it's still plugged?) and it was fine before. So I'd like to see if it's a software issue before having to drop it off at the warranty for another full month.
OTA updates are not working obviously and Kies recognized my firmware as "up to date".
I don't want my phone rooted (I refused to do it right from the beginning) and I want my phone to be able to update normally.
Is there any way I can unroot my phone and leave it in the same condition I got my phone in originally? Stock ROM and all. I was happy with it.
Thanks a lot!
All needs to be Stock for unrooted phone.
Did they flash you a Stock/Custom Rom with a Stock kernel?
What does the phone info say ?
Are any root apps left in the menu? When yes, which ones?
To put in in a nutshell your aim is now to assure getting a stock Rom+Kernel and then unroot it with a Unroot App. Usually works like a charm
Oh, and if you want to switch back to 4.2 you can get the according Stock Rom either here by searching for your (exact) phone model or try novafusion.pl if its an old Samsung Galaxy.
TheDogWithoutFear said:
Hello!
For some reason my board got fried so I took it to the warranty and they sent me to a place to drop off my phone. They changed it for free (great) but they also rooted my phone and left me a 4.1 ROM instead of the stock 4.2 as I had. I'm now having troubles regarding charging it (it's not detecting the cable correctly sometimes and think it's still plugged?) and it was fine before. So I'd like to see if it's a software issue before having to drop it off at the warranty for another full month.
OTA updates are not working obviously and Kies recognized my firmware as "up to date".
I don't want my phone rooted (I refused to do it right from the beginning) and I want my phone to be able to update normally.
Is there any way I can unroot my phone and leave it in the same condition I got my phone in originally? Stock ROM and all. I was happy with it.
Thanks a lot!
Click to expand...
Click to collapse
Hello, I recently bought a Moto X (XT1097) on Android 6.0 version and as soon as it arrived at my house, I unlocked the bootloader, installed a custom kernel,rooted the device and then I installed the Xposed Framework, following the steps of this post: http://forum.xda-developers.com/moto-x-2014/general/ota-android-marshmallow-6-0-final-t3248315
Everything went well, but in the end of the next day of usage I noticed that my battery drained really fast ending up at 0%. When I charged and turned on my device , I simply couldn't turn on my WiFi.
Curiously it also happened with my old phone, a Nexus 5. And to solve the problem with both of them I flashed a Stock version of the Android ROM.
I really want to know what I had done wrong. Currently I am using my Moto X with just the bootloader unlocked, nothing more but I really miss using root. Do you guys have any idea what to do? I don't want to root my phone and that problem happen again... It's a pain in the ass to start all over from a data wipe lol
Hello all. I am from the UK and recently purchased a sprint model phone. I wanted to remove handsfree activation. In order to do that i need a root. I rooted 5.1.1 with kernel SpaceX-Kernel-v0.1_N920P(official).tar and all seemed ok. Then i noticed that you could root marshmallow. I followed a tutorial on youtube and flashed two files through twrp no-verify-opt-encrypt.zip and SuperSU zip. I rebooted the phone and now i have a persistent problem. After around 15-30 seconds my phone shuts off and reboots itself. I have tried reflashing stock roms and the problem still persists. I have no idea if i have broken the phone as its usable until it shuts off . I went into the about phone section and it tells me the baseband and software versions are unknown aswell. Is there anyway to recover this?
Let the battery die completely and then it will work fine again afterwards
954wrecker said:
Let the battery die completely and then it will work fine again afterwards
Click to expand...
Click to collapse
This has solved the issue. Many thanks ! :laugh: