Hey guys.
I have had my turbo for a little over a year. I was rooted with Moforoot running CF's roms. I unlocked when sunshine released support for our device and I have ran CM 12.1, then CM 13. My phone bricked when CM13 came out through the CM updater and I was able to fix it. I have fixed every issue that I have come across so far (with the help of this community), but this one has me stumped.
I unlocked my dads turbo with sunshine, and flashed CM13. Everything flashed as it shouldve, and it was running fine, except no voice calls. I reflashed the radio, set the FSG ID, and changed the network type to CDMA/LTE auto-PRL and it wouldnt connect. I started over and did a clean install, and its bootlooping. I can power off and get into the BL and then recovery. What can I flash to get the phone back in working order? This is my dads phone, so im trying to get it working ASAP. I found the fxz files for this phone, but I dont know if I can flash them without screwing up the bootloader unlock. I also found a package that was posted here that will flash everything to stock except recovery. Can I flash that?
Suggestions anyone?
Related
Ok so heres the situation. I was running a Stock custom rom but was on 4.4 and was getting constant update notifications. so i decided to installed the updated 4.4.2 version of my custom rom. BTW my phone is a verizon locked bootloader phone. anyways i tried the workaround for retail phones and i ended up totally screwing my phone up. everything is wiped and i cant get anywhere but the fastboot screen. I have tried the Moto X toolbox but that fails and so does every other script i have tried. I thought that this would be my saving grace http://forum.xda-developers.com/mot...ty-windows-t2597625/post49119224#post49119224. but it looks like there server host is down so i cant download it. I have tried everything on both a Windows 8 with USB 3.0 and a Windows 7 with USB 2.0. both failed. My device only shows up at Fastboot ghost S in devices, i downloaded the PDAnet drivers but that didnt help. I can see the Fastboot in RSDlite though but the flash fails everytime. I keep getting "Partition (Boot) security version downgraded" and yes im using stock Verizon Roms.
baile508 said:
Ok so heres the situation. I was running a Stock custom rom but was on 4.4 and was getting constant update notifications. so i decided to installed the updated 4.4.2 version of my custom rom. BTW my phone is a verizon locked bootloader phone. anyways i tried the workaround for retail phones and i ended up totally screwing my phone up. everything is wiped and i cant get anywhere but the fastboot screen. I have tried the Moto X toolbox but that fails and so does every other script i have tried. I thought that this would be my saving grace http://forum.xda-developers.com/mot...ty-windows-t2597625/post49119224#post49119224. but it looks like there server host is down so i cant download it. I have tried everything on both a Windows 8 with USB 3.0 and a Windows 7 with USB 2.0. both failed. My device only shows up at Fastboot ghost S in devices, i downloaded the PDAnet drivers but that didnt help. I can see the Fastboot in RSDlite though but the flash fails everytime. I keep getting "Partition (Boot) security version downgraded" and yes im using stock Verizon Roms.
Click to expand...
Click to collapse
If you can get into Fastboot and RSDlite you should be able to install the 4.4.2 Verizon files from http://sbf.droid-developers.org/phone.php?device=0
I figured it out, my problem was that i was trying to flash 4.4 and not 4.4.2. got it unbricked but now it looks like i lost my root and my safestrap... :/
baile508 said:
I figured it out, my problem was that i was trying to flash 4.4 and not 4.4.2. got it unbricked but now it looks like i lost my root and my safestrap... :/
Click to expand...
Click to collapse
Yes, if you used RSDLite to flash you will loose root, etc.
But taking the OTA 4.4.2, you could have kept root, BUT would have lost write protect disable making root pretty useless (since any changes to /system or other protected folders would not survive power off/on)
I have a question. Last night I went to about phone and check for an update and there it was 5.01 I selected to install it then it said it was going to restart and then banner went away and the phone never restarted. I tried checking for update again and its not there anymore plus my phone is at 5.0 . I was wondering if anyone has experienced this and what the solution was. Also If I where to update it manually will that mess anything up with my updates of were I get it from now. So for example my phone is from Motorola where does it get its updates from same place as Google play store? So I ask this because I think the people who post the updates they are for Google play edition and I don't want to turn my phone into Google play edition if its different from the Motorola version.
Thanks,
You're not alone. Several threads on this in general forum and Q&A. Consensus so far is hang tight and the update should resurface.
Sent from my Nexus 6 using XDA Free mobile app
Factory image is still on Google website. Grab it there.
bluh5d said:
I have a question. Last night I went to about phone and check for an update and there it was 5.01 I selected to install it then it said it was going to restart and then banner went away and the phone never restarted. I tried checking for update again and its not there anymore plus my phone is at 5.0 . I was wondering if anyone has experienced this and what the solution was. Also If I where to update it manually will that mess anything up with my updates of were I get it from now. So for example my phone is from Motorola where does it get its updates from same place as Google play store? So I ask this because I think the people who post the updates they are for Google play edition and I don't want to turn my phone into Google play edition if its different from the Motorola version.
Thanks,
Click to expand...
Click to collapse
Same thing happened here, I assumed it was due to me having unlocked bootloader & custom recovery. So I just manually flashed the factory image update using ADB. Easy peasy. You can do the same.
Cheers
If I manually flash the image will it change where my future otas come from ? Like doesnt a motorola nexus 6 updates come from a different server than a google play nexus 6 ?
Same thing for me, except I was waiting to be able to charge up my phone before installing. By the time I got to a charger it was gone. I'll probably just wait for it to resurface.
Same same here. Fully stock. Is the common theme for people experiencing this that they are on VZW? I am. Tmo bought phone with VZW sim.
Fyi, rebooting and charging havent helped.
I know i can manually update, but I'm hoping to confirm that the OTA process still works correctly with my stock phone running on VZW.
Its not only VZW.. I'm T-Mobile and the same happened
SirRastusBear said:
Same thing happened here, I assumed it was due to me having unlocked bootloader & custom recovery. So I just manually flashed the factory image update using ADB. Easy peasy. You can do the same.
Cheers
Click to expand...
Click to collapse
Did you flash the 5.0.1 completely (all partitions), or did you just flash system.img to get the 5.0.1 update? I'm trying to figure out the easiest way to get from 5.0 to 5.0.1 since I'm (stock) rooted and have thus modified the system partition, so can't do the OTA.
mlevin said:
Did you flash the 5.0.1 completely (all partitions), or did you just flash system.img to get the 5.0.1 update? I'm trying to figure out the easiest way to get from 5.0 to 5.0.1 since I'm (stock) rooted and have thus modified the system partition, so can't do the OTA.
Click to expand...
Click to collapse
Flashed each separately.
Flash bootloader image
Reboot bootloader (important)
Flash radio image
Flash recovery image
Flash boot image
Flash system image (takes a while)
Flash userdata image ONLY if you want to wipe your own data
Reboot when done
Flash custom recovery
Install SuperSU from custom recovery
Reboot
Profit
Cheers
Those like me who don't want to manually flash.. I just got off the phone with Google, and apparently within 24-48 hours the update will be available again for those devices affected by this hiccup. I'll wait.
So just to summarize what I've done so far, I have a Moto G (2014) which has been updated to Lollipop through normal means. I started off following this guide: http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818/page12
The guide then lead me to this one, as my model is XT1064, a Moto G from Windmobile. I had no issues unlocking my bootloader. http://forum.xda-developers.com/moto-g-2014/development/xt1064-lollipop-root-t2938051
With the guide above, after I flashed that file, my wifi would not turn on. Every time I pressed the toggle, it would immediately switch back to off. I then flashed the TWRP Recovery, and used that to finally root my device with SuperSU.
I checked my root, and my device is confirmed to be rooted, but the wifi is still not working. I looked around a little, and found this: http://forum.xda-developers.com/moto-g-2014/general/guide-lollipop-xt1064-north-edition-t2955076
The problem with the guide above is that its for a phone that was kitkat, while my phone is already lollipop. The guide does mention the wireless issue though, so I was thinking of trying out the steps outlined in that guide, also using that file (though that file is for 4.4).
Would this work? Or is the safer bet finding an 5.0.1 stock rom, and flashing back to that?
Edit: I found a link to a 5.0.2 stock rom (which is the version my phone currently is) I think downloading that and using that to fix the modem files is the better thing to do. (link: http://www.filefactory.com/file/53c1pepzp9cp/RETCA_XT1064_5.0.2_LXB22.99-24.2_cid14_CFC.xml.zip)
Thanks for all and any help.
I recommend flashing the stock images, that will almost certainly fix your issue with Wifi.
Ok, first off, let me say what a idiot I am! I've been unlocked, s-off, and rooted since the day I got this phone and for the most part been running BadBoyz Rom. It had gotten a little bogged down and I thought I would go ahead and put a fresh flash of this ROM on the phone a couple days ago, I was tired and somehow erased everything on the phone and couldn't get ADB Sideload to copy anything onto it and I was out of time and a little panicky so I went to the the Sprint store and talked to a tech who didn't hassle me at all about it and he was able to load a stock ROM for me, in the process he also updated the Hboot of my phone (at a minimum). Currently it has hboot of 1.61, Radio 1.01.20.1225, DSP 3.51.202740718, OS 6.23.651.7. Phone is still unlocked and S-Off so I flashed twrp recovery and then tried to flash supersu. When I tried to flash the supersu I got a message about the cache? Could'nt mount cache or something like that but then it appeared to work? So, when I restarted phone and checked for Root, it tole me the same old binaries not loaded, this is a problem message? Started with Twrp 2.84 now I have 2.87 thinking that was the problem but it's not I don't think. Also tried a few different versions of supersu too. Help!!!
I read advice somewhere on the forum about just flashing a rom since you have twrp? I almost did that but twrp gave me a warning that this might not be compatible so I stopped. Could this work?
Hi all, I was running a CM ROM on my Droid Turbo and recently flashed back to stock using a backup I created with TWRP, because I was tired of not having GPS capabilities.
Now that I’m running stock (still rooted), I’ve been getting a notification to do an OTA update. When I allow the update to install, it restarts my phone and sends me straight to the TWRP recovery and does nothing else. Rebooting gets me stuck in a loop where it keeps sending me to recovery. Clearing out my cache got me out of the loop but after a day or so, the annoying install message comes back.
I noticed an error message when I looked at the log screen in TWRP. As best I can transcribe it, it says:
Package expects build fingerprint of motorola/quark_verizon/quark:5.1/SU4TL-44/44:user/release-keys or Motorola/quark…. ; this device has Motorola/omni_quark/quark:5.1.1/LYZ28E/1:eng/test-keys
Does anyone have any idea what’s going on with my phone – why I can’t take the OTA? Any advice on how to fix the problem or get this stupid upgrade notification to go away? The notification takes over the device every time you unlock the screen so it’s driving me crazy.
Thanks in advance for any help!
I think you need stock recovery and bootloader.
GPS issues have long been solved, using the "clear modem" file. You sent back to stock for nothing.
If you really want SUTL-49 there's plenty of downloads to manually flash it. You don't need the OTA.
Thanks for the replies. I think I'm going to stick with stock now. Have been enjoying the Motorola features like the hands-free driving thing and I wasn't seeing any advantage running CM anymore. Can I flash SUTL-49 using TWRP or do I have to hook to a PC and use ADB?
shinydiamond said:
Thanks for the replies. I think I'm going to stick with stock now. Have been enjoying the Motorola features like the hands-free driving thing and I wasn't seeing any advantage running CM anymore. Can I flash SUTL-49 using TWRP or do I have to hook to a PC and use ADB?
Click to expand...
Click to collapse
You can flash it with TWRP from here:
http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
Thank you!