I just got my verizon turbo xt1254 and have it unlocked, rooted and xposed installed, on SU4TL-44, and just put all my apps and data on it, then stupidly flashed the higher volume mod from this thread: http://forum.xda-developers.com/moto-maxx/development/motomaxx-volume-mod-t3019203 onto my phone. Now my phone has no sound at all from any source through the speaker. Headphones still work. Is there a way to fix this? Preferably without wiping my data or having to reroot and install xposed and all again?
Restore from backup, it's better from stock rom. I had a similar problem with another mod, i personally recommend viper4android, thats a good mod for the turbo, but it must be on compatible mode (using computerfreak excellent ROM)
Unfortunately I was an idiot and didn't make a backup. Lesson learned I guess. Would I be able to flash the pre rooted system image from this post http://www.theandroidsoul.com/update-droid-turbo-to-android-5-1-1-with-mofo-root-retained-yes-its-possible-now-81652/ and then just reinstall xposed? Or would that wipe my data partition also?
Have you tried just dirty flashing your current ROM?
I just got back into the game of flashing phones after being out for a tear it two, what us dirty flashing, and in on stock 5.1 just unlocked using sunshine and rooted and installed twrp.
rboutin2 said:
I just got back into the game of flashing phones after being out for a tear it two, what us dirty flashing, and in on stock 5.1 just unlocked using sunshine and rooted and installed twrp.
Click to expand...
Click to collapse
Dirty flashing is flashing the rom without wiping any cache or data. You should go ahead and make a backup in twrp now. Also install titanium backup and then make a backup of your apps and data. Copy. Both twrp and titanium backups to your pc so you can get back to them if need to. The twrp backup is not in the directory you might expect. I'd tell you but I don't remember off hand. If you search these forums it won't take you long to find.
After that you can flash a rom. The one you linked earlier was to get to 5.1 from 4.4 via mofo. If you want that one go to First Encounters thread. It will tell you what to download and how to flash it with twrp. You could also try Computerfreeks.
I don't know of a way to dirty flash what you are on, and guarantee that that you won't lose your apps/data. If you have your titanium backups it will be easier to restore. Still a pain but easier. You'll download titanium again, then restore your apps. That's better than downloading all of your apps again. If you haven't used titanium before, you need the pro version and should practice freezing, backing up and restoring before you flash any rom's.
To be honest, I'm not really THAT concerned with losing all my data. I still have it on my old droid maxx. I was just hoping for a way to fix my issue without losing it all if possible since I literally just out it all on there yesterday.
rboutin2 said:
I just got my verizon turbo xt1254 and have it unlocked, rooted and xposed installed, on SU4TL-44, and just put all my apps and data on it, then stupidly flashed the higher volume mod from this thread: http://forum.xda-developers.com/moto-maxx/development/motomaxx-volume-mod-t3019203 onto my phone. Now my phone has no sound at all from any source through the speaker. Headphones still work. Is there a way to fix this? Preferably without wiping my data or having to reroot and install xposed and all again?
Click to expand...
Click to collapse
The mod that you flashed replaced /system/etc/mixer_paths.xml. You don't have to wipe anything to fix this. Unzip the mixer_paths.xml file that I've attached to this post and place it in a convenient location on your phone. Then use a root browser to copy this file to /system/etc on your phone (replacing the file that is currently at that location). Then set the permissions of this file to rw-r--r--. It should be good after a reboot.
I just tried that and I still have no sound, and now when I try to play a song in Google music or watch something on YouTube, I just get an error. And still no sound at all. Could I get the 2bd mixer paths file from you also by chance?
rboutin2 said:
I just tried that and I still have no sound, and now when I try to play a song in Google music or watch something on YouTube, I just get an error. And still no sound at all. Could I get the 2bd mixer paths file from you also by chance?
Click to expand...
Click to collapse
I'm running Computerfreek's mod of SU4TL-44, and there is no such file. However, there is a mixer_paths_i2s.xml file.
I had assumed that CF had not made any mods to this file, but that might be incorrect. I'll try to find the file from a stock SU4TL-44 image and that should fix the problem.
But like I said before, the only thing that the Moto Maxx volume mod that you flashed did was replace mixer_paths.xml, so you should not need any other files if that's all you've done.
rboutin2 said:
I just tried that and I still have no sound, and now when I try to play a song in Google music or watch something on YouTube, I just get an error. And still no sound at all. Could I get the 2bd mixer paths file from you also by chance?
Click to expand...
Click to collapse
Here's a flashable zip of the stock, unmodified mixer_paths.xml from SU4TL-44, courtesy of Computerfreek. Simply flash with TWRP.
Yeah I had apparently tried to fix it by replacing that file earlier with a different one, plus also tried to manually fix it too. I now have it fixed. I had the permissions wrong. My sound is back and working now! Thanks billion!! Any chance you know what I need to change to make my sound louder? I don't know what line to edit. But I miss the loud volume of my droid maxx.
rboutin2 said:
Yeah I had apparently tried to fix it by replacing that file earlier with a different one, plus also tried to manually fix it too. I now have it fixed. I had the permissions wrong. My sound is back and working now! Thanks billion!! Any chance you know what I need to change to make my sound louder? I don't know what line to edit. But I miss the loud volume of my droid maxx.
Click to expand...
Click to collapse
Try flashing this: https://www.androidfilehost.com/?fid=24269982087009390
TheSt33v said:
Try flashing this: https://www.androidfilehost.com/?fid=24269982087009390
Click to expand...
Click to collapse
Volume is definitely louder, still not as good as my maxx but at least it's an improvement. I appreciate all your help!! My phone is now fully working again, and customized to my liking :victory:
rboutin2 said:
Volume is definitely louder, still not as good as my maxx but at least it's an improvement. I appreciate all your help!! My phone is now fully working again, and customized to my liking :victory:
Click to expand...
Click to collapse
Awesome! No problem. If you feel adventurous and want to go louder, you can increase the values of RX(1-7) Digital Volume and DEC(1-10) Volume. Be careful with that though. You can break your speakers if you go too high.
Related
So I just successfully rooted my lovely HTC One from Sprint. I've got TWRP 2.6.0.1 on it and all.
I'd REALLY like to get rid of all this garbage on my phone that I'm never going to use, however I also would like to keep it as close to stock as possible. I really enjoy Sense for the most part (minus quirks that I'm willing to live with, and BlinkFeed). I know how/can find out how to load a custom rom - I had CM7 on my HTC EVO 4G (1st Gen) and loved it. But I really don't want to be without Sense.
Can anyone make any suggestions as to what I should do/which rom I should use?
wolfbuck22 said:
So I just successfully rooted my lovely HTC One from Sprint. I've got TWRP 2.6.0.1 on it and all.
I'd REALLY like to get rid of all this garbage on my phone that I'm never going to use, however I also would like to keep it as close to stock as possible. I really enjoy Sense for the most part (minus quirks that I'm willing to live with, and BlinkFeed). I know how/can find out how to load a custom rom - I had CM7 on my HTC EVO 4G (1st Gen) and loved it. But I really don't want to be without Sense.
Can anyone make any suggestions as to what I should do/which rom I should use?
Click to expand...
Click to collapse
omj's stock rooted sounds like the rom for you
wranglerray said:
omj's stock rooted sounds like the rom for you
Click to expand...
Click to collapse
With a custom kernel. And greenify.
And a whole boat load of other mods you can only discover by spending time on these forums.
Stock with goodies
Sent from my One using XDA Premium 4 mobile app
wranglerray said:
omj's stock rooted sounds like the rom for you
Click to expand...
Click to collapse
Sorry, I'm overwhelmed at the wealth of knowledge here. Is there a link to the specific one you're talking about? Search didn't do me a ton of good. Though I suppose I could send the guy a message and inquire about his ROM.
Thank you for all your help guys!
Okay so I've decided that I want to try the OMJ ROM. Now here's where I am unsure of exactly how to do it. I see that certain ROMs require different methods. I can't just copy the ZIP to my internal storage and use TWRP to flash it, right? It has to be more complicated than that...
Also, I just went past the return window for the phone so I really cannot afford to brick it. I assume that there's next to no chance of the aforementioned tragedy befalling me providing I stick with the mainstream ROMs?
Most roms are in a flashable format i use the CM 10.2 nightly myself. from what i can tell as long as you can get into the bootloader your safe. I wiped my whole phone SD card and everything accidentally with TWRP one time. Ended up having to use sideload to get a CM rom installed again but i was never in danger of bricking. When flashing roms always remember to do a factory reset to wipe the cache and do an advanced wipe of the data and system. after the rom is installed it will ask you to wipe the cache again which is always nice to do.
cloppy said:
Most roms are in a flashable format i use the CM 10.2 nightly myself. from what i can tell as long as you can get into the bootloader your safe. I wiped my whole phone SD card and everything accidentally with TWRP one time. Ended up having to use sideload to get a CM rom installed again but i was never in danger of bricking. When flashing roms always remember to do a factory reset to wipe the cache and do an advanced wipe of the data and system. after the rom is installed it will ask you to wipe the cache again which is always nice to do.
Click to expand...
Click to collapse
Awesome! So what was I hearing about having to plug the phone into the computer to flash the boot.IMG file? Sorry, I'm just really overwhelmed with the new ways of doing things.
wolfbuck22 said:
Awesome! So what was I hearing about having to plug the phone into the computer to flash the boot.IMG file? Sorry, I'm just really overwhelmed with the new ways of doing things.
Click to expand...
Click to collapse
No worries, I am new to the unlocking scene too with this device . Those flashable zips will normally have the boot.img files included and when installing twrp will take care of it via the script inside the zip. if you open the zip file with winzip or something you should see that file on the root. TWRP or ClockworkMod recoveries make it really easy to install and backup roms.
flashing the boot.img i guess is for recovery purposes say if the system is in a boot loop. Or maybe if you upgrade the system only and didnt change boot img between two different roms. I personally never had to do this. After unlocking the device i used fastboot to replace the recovery and just do everything else inside the recovery.
cloppy said:
No worries, I am new to the unlocking scene too with this device . Those flashable zips will normally have the boot.img files included and when installing twrp will take care of it via the script inside the zip. if you open the zip file with winzip or something you should see that file on the root. TWRP or ClockworkMod recoveries make it really easy to install and backup roms.
flashing the boot.img i guess is for recovery purposes say if the system is in a boot loop. Or maybe if you upgrade the system only and didnt change boot img between two different roms. I personally never had to do this. After unlocking the device i used fastboot to replace the recovery and just do everything else inside the recovery.
Click to expand...
Click to collapse
Awesome! I guess it really is that easy! Thanks so much for all your help!
cloppy said:
No worries, I am new to the unlocking scene too with this device . Those flashable zips will normally have the boot.img files included and when installing twrp will take care of it via the script inside the zip. if you open the zip file with winzip or something you should see that file on the root. TWRP or ClockworkMod recoveries make it really easy to install and backup roms.
flashing the boot.img i guess is for recovery purposes say if the system is in a boot loop. Or maybe if you upgrade the system only and didnt change boot img between two different roms. I personally never had to do this. After unlocking the device i used fastboot to replace the recovery and just do everything else inside the recovery.
Click to expand...
Click to collapse
Alright, so I've got OMJ's rom running no problem. Love the new feel but what I'm wondering is...is there still a way to delete apps like Stocks and other crap I won't use? I can disable some but not all, and none am I able to uninstall completely.
Would it be something as simple as going into the OMJ ZIP file and removing the unwanted apk files and then re-flashing to that version?
wolfbuck22 said:
Alright, so I've got OMJ's rom running no problem. Love the new feel but what I'm wondering is...is there still a way to delete apps like Stocks and other crap I won't use? I can disable some but not all, and none am I able to uninstall completely.
Would it be something as simple as going into the OMJ ZIP file and removing the unwanted apk files and then re-flashing to that version?
Click to expand...
Click to collapse
I suppose that could be one way of doing it, but i dont think its necessary. if you are already rooted or can install root easy i would just install a Root file explorer. Browse to the /system/app folder i think it is and delete the APKs from there.
cloppy said:
I suppose that could be one way of doing it, but i dont think its necessary. if you are already rooted or can install root easy i would just install a Root file explorer. Browse to the /system/app folder i think it is and delete the APKs from there.
Click to expand...
Click to collapse
Yeah I tried that with ES explorer AND Root File Manager. ES would have an error, and Root File Manager would simply say it was deleted but it was never actually deleted. I think it has something to do with the security. I'm not really sure, haha! I'm used to being able to just openly delete apps from within Settings>Apps like the old days of my EVO 1st gen.
hmm interesting as long as the /system is mounted as r/w permissions you should be able to delete. well if you are planning on reflashing using the modify zip method im curious to know if that works.
wolfbuck22 said:
Yeah I tried that with ES explorer AND Root File Manager. ES would have an error, and Root File Manager would simply say it was deleted but it was never actually deleted. I think it has something to do with the security. I'm not really sure, haha! I'm used to being able to just openly delete apps from within Settings>Apps like the old days of my EVO 1st gen.
Click to expand...
Click to collapse
use Root explorer, and set it at r/w
also Titanium Backup will delete it for you too.
If I remember correctly there are a few apps in the play store that are specifically for getting rid of "bloatware".....maybe search bloatware removal, our uninstall bloatware something like that. Hopefully this helps!
Sent from my HTCONE using xda premium
Aldo101t said:
use Root explorer, and set it at r/w
also Titanium Backup will delete it for you too.
Click to expand...
Click to collapse
Well for whatever reason neither of those two suggestions worked. So I installed Root Browser and was finally able to get rid of some things.
Scratch that. Rebooted phone and the apps are back.
wolfbuck22 said:
Well for whatever reason neither of those two suggestions worked. So I installed Root Browser and was finally able to get rid of some things.
Scratch that. Rebooted phone and the apps are back.
Click to expand...
Click to collapse
ROMCleaner
bigdaddy619 said:
ROMCleaner
Click to expand...
Click to collapse
Thanks! I'm working on it now. I did not see an app called "ROM Cleaner" or "ROMCleaner" but I did find something called Rom Toolbox Lite that I'm going to attempt to use.
Will post back. I may look for the ROMCleaner on the net and just install it manually.
Edit: So I guess I showed my ignorance there. It appears ROM Cleaner is something offered through the forum. I'm unsure of how to use it so I'll take a look around.
wolfbuck22 said:
Thanks! I'm working on it now. I did not see an app called "ROM Cleaner" or "ROMCleaner" but I did find something called Rom Toolbox Lite that I'm going to attempt to use.
Will post back. I may look for the ROMCleaner on the net and just install it manually.
Edit: So I guess I showed my ignorance there. It appears ROM Cleaner is something offered through the forum. I'm unsure of how to use it so I'll take a look around.
Click to expand...
Click to collapse
ROMCleaner
It's very doubtful you will have success with Romtoolbox either once you reboot all the apps will return
Ok so I took the OTA lollipop update, rooted and the phone was rocking. Installed TWRP backed up including cache and boot. I did factory reset and restored from backup file and I couldn't get past the boot animation. I downloaded these files http://forum.xda-developers.com/mot...g-lxe22-39-6-pure-edition-stock-boot-t2940437 and ran these commands:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
Then, I lost the boot animation, only had the boot image. Then a lot of mfastboot stuff and I am back at on a fresh unrooted KK...... Any ideas wtf happened? Was it TWRP, restoring the cache or what? This is my fist no Sammy device so it's a learning experience.
I don't think twrp is working on moto x lollipop yet. They just released the lollipop compatible twrp for nexus not long ago. We should get a new twrp for lollipop soon.
Sent from my XT1095 using Tapatalk
dobbs3x said:
I don't think twrp is working on moto x lollipop yet. They just released the lollipop compatible twrp for nexus not long ago. We should get a new twrp for lollipop soon.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I am using TWRP 2.8.1.0 on my XT1095. Running 5.0 (.11 OTA). I've had no problems, at all.
TWRP has been horribly quirky for me on my Moto X. I can't even get it to boot into recovery half the time, among other things.
Sent from my iPhone 6 using Tapatalk
cam30era said:
I am using TWRP 2.8.1.0 on my XT1095. Running 5.0 (.11 OTA). I've had no problems, at all.
Click to expand...
Click to collapse
I also have twrp 2.8.1.0, but have you tried restoring lollipop backups with it? It will boot into twrp fine and flash zips etc. It just is not ready to to restores etc for lollipop.
dobbs3x said:
I also have twrp 2.8.1.0, but have you tried restoring lollipop backups with it? It will boot into twrp fine and flash zips etc. It just is not ready to to restores etc for lollipop.
Click to expand...
Click to collapse
Aahh. Good point. I've made a backup and flashed .zips. But have not tried to restore a backup. Thanks for the heads up.
I now know the restore of TWRP backups is what did it. I have successfully recreated the issue twice with the exact same results.
Interesting thread, what do you guys suggest one does if one wants to mess with things like DPI changer?
Currently what I have done is just:
- unlocked the bootloader via moto site.
- fastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
- installed/updated SuperSU via Playstore
- installed updated Binary via SuperSU
Back when I had the Nexus 5, I would change the DPI with DPI changer, but on some ROMs, flashing an updated GAPPS/etc would break the ROM, because of the DPI Changer... (I would just do a NAND restore/TWRP restore) How can I full-proof my current setup so that when I mess up I can always have something to fall back on?
From what I read above flashing TWRP is no ideal yet as NAND backups don't restore? is that right?
I'm just running stock Bootloader/Recovery right now, and I'm not sure how to fail-proof myself.
If I stick to default bootloader/recovery can I just flash default KitKat/Lollipop image to restore/fix any issues?
Lastly, on boot, that "Unlocked Bootloader" message comes up, it's not the worst, but from what I understand people flash a bootloader/recovery that removes that warning?
Thanks for help.
Shemploo said:
Interesting thread, what do you guys suggest one does if one wants to mess with things like DPI changer?
.
Click to expand...
Click to collapse
Edit build.prop :good:
TigerDNA said:
Edit build.prop :good:
Click to expand...
Click to collapse
I meant how to safely change things like DPI (Or settings that might break ROM), but yet protect yourself from breaking the ROM.
- Example was doing something like changing the DPI either via App or by editing build.prop
Shemploo said:
I meant how to safely change things like DPI (Or settings that might break ROM), but yet protect yourself from breaking the ROM.
- Example was doing something like changing the DPI either via App or by editing build.prop
Click to expand...
Click to collapse
Change dpi system wide just edit the build.prop. if you break something you learned something. Im sure you can hard brick but really what would to I want to mess with that would cause a hard brick, most likely nothing. Just play with it and if you kill it, learn from it and do something different next time.
The only way to do something's is sounding like you are wanting is to make your own ROM.
TigerDNA said:
Change dpi system wide just edit the build.prop. if you break something you learned something. Im sure you can hard brick but really what would to I want to mess with that would cause a hard brick, most likely nothing. Just play with it and if you kill it, learn from it and do something different next time.
The only way to do something's is sounding like you are wanting is to make your own ROM.
Click to expand...
Click to collapse
Maybe someday, but right now I do not have time to learn, and the few times I tried to learn to program was a long time ago and it did not go well.
I would certainty like to go into Android programming, but for my short time needs, I guess I'm wondering how, if anything.. one can do to have an easy fix to breaking the OS/ROM, since TWRP back-ups don't seem to work for this device right now.
What is hard brick?, can anything I mess up software wise be restored via flashing factory images?
Yes I know the title is a bit long, but there's no other way to say it.
After updating my rom to android revolution hd 84,I've encountered a small problem: I can't copy single files larger than 3-4MB to some of my root folders.
I discovered this when I tried to change my kernel and my phone restated. I thought it was incompatible but then it happened again when I tried to change my bootanimation.
Basically whenever I try to copy a single file larger than 3-4MB to some of my root folders, my phone auto-deletes it and restarts.
And yes, I've unlocked my bootloader, rooted my phone and I have busybox.
EDIT: Also forgot to mention, I'm using X-Plore as a file manager, and all root folders have a little purple circle on their corner. I can do whatever I want normally in those folders. However, most folders have a red circle and coincidentally, those are the folders which restart my phone and delete all files over 3-4MB that are put into them.
Does anyone have any ideas how to fix this?
Bump, has anyone got any ideas?
kik4444 said:
Bump, has anyone got any ideas?
Click to expand...
Click to collapse
sounds like the kernal to me, you seem to have write protection, have you tried changing the permissions on the folder your trying to write files too or even try another kernal.
I tried a lot of different permissions, nothing works. And since it's got write protection, I CAN'T change the kernel.
EDIT: also, not sure if it matters, but when I updated my rom to a newer version, I didn't wipe the userdata partition, since it's the same rom, just a newer version.
I was thinking of maybe making another nandroid backup, reinstalling the rom AND wiping the userdata partition to try if it fixed anything, and if nothing is fixed, I'll just restore the backup to before I reinstalled the rom.
kik4444 said:
I tried a lot of different permissions, nothing works. And since it's got write protection, I CAN'T change the kernel.
Click to expand...
Click to collapse
This shouldnt stop you from flashing another kernal in recovery, this only effects what you do when booted into the rom.
It's the same thing. Did you read my 1st post? I discovered this when trying to change my kernel, which I can only do through recovery. I use TWRP. I tried flashing a custom kernel and the phone just rebooted without any changes. Then later I tried flashing another bootanimation and the phone again rebooted with the default bootanimation. And it still does it when trying to manually change the bootanimation by replacing it with a file manager.
In conclusion, I get the same problem even in recovery.
kik4444 said:
It's the same thing. Did you read my 1st post? I discovered this when trying to change my kernel, which I can only do through recovery. I use TWRP. I tried flashing a custom kernel and the phone just rebooted without any changes. Then later I tried flashing another bootanimation and the phone again rebooted with the default bootanimation. And it still does it when trying to manually change the bootanimation by replacing it with a file manager.
In conclusion, I get the same problem even in recovery.
Click to expand...
Click to collapse
Of course I read your first post, just didnt quite understand the restart part, thought you meant it restarted itself out of your rom, I would try what you said, rather than a dirty flash, try with a clean slate after backing up, there maybe parts of your old modifications to the system in the data partition.
Also, I'm not sure it can technically be called "write protection", since I can copy\delete\move, etc files just fine, but I can't copy files above 3MB. And due to that I can't change my bootanimation and kernel. As for the bootanmation, I also tried changing it manually and still the same thing happens - my phone reboots and deletes the file I copied. Needless to say, the same thing happens even when trying to flash it with TWRP.
Ok, reinstalling rom, will report back with results.
Edit 1 - install complete, rebooting....
Edit 2 - doing the setup thing at the 1st startup
Conclusion - Strangely enough, doing a clean flash of my rom fixed everything. Weird. Well, guess now I have a lot of things to set up again.
Well, thx for everything, even if I managed to fix everything by myself in the end. Though, I'd still much appreciate it if anyone could tell me what the problem was so I can be ready for any similar problems I might have in the future.
kik4444 said:
Well, thx for everything, even if I managed to fix everything by myself in the end. Though, I'd still much appreciate it if anyone could tell me what the problem was so I can be ready for any similar problems I might have in the future.
Click to expand...
Click to collapse
Did you not read my last post ? Of course I read your first post, just didnt quite understand the restart part, thought you meant it restarted itself out of your rom, I would try what you said, rather than a dirty flash, try with a clean slate after backing up, THERE MAYBE PARTS OF YOUR OLD MODIFICATIONS TO THE SYSTEM IN THE DATA PARTITON.
I never dirty flash, and the reason, your problems, even if im switching to a newer version of the same rom.
So for some reason today, my phone restarted and now I can't call people or receive calls, if I do. My phone restarts. Also can't use Bluetooth or it also does the same and restarts what can cause this? My phone getting too hot and damaged the motherboard? When I installed a kernel it was corrupted? I really have no understanding what caused this. I had resurrection from on it. I updated it with a newer one and did a bootloop. So I put cyangemod on it and worked but noticed those huge issues. Thinking the ROM was corrupted I put rr back on it and had the exact same issues. Any help would mean everything to me
austtint said:
So for some reason today, my phone restarted and now I can't call people or receive calls, if I do. My phone restarts. Also can't use Bluetooth or it also does the same and restarts what can cause this? My phone getting too hot and damaged the motherboard? When I installed a kernel it was corrupted? I really have no understanding what caused this. I had resurrection from on it. I updated it with a newer one and did a bootloop. So I put cyangemod on it and worked but noticed those huge issues. Thinking the ROM was corrupted I put rr back on it and had the exact same issues. Any help would mean everything to me
Click to expand...
Click to collapse
Restore the stock rom using step 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684. Once you confirm that your phone is fixed, re-flash whatever rom/setup you want.
TheSt33v said:
Restore the stock rom using step 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684. Once you confirm that your phone is fixed, re-flash whatever rom/setup you want.
Click to expand...
Click to collapse
What he said. If you want to try and recover your data (DCIM folder, downloads, etc), edit out "%fastboot% erase userdata" from the .bat file. Chances are that if you had CM installed, the stock rom will be terribly buggy since the data partition won't be erased, but you can still connect to your PC and pull the files you want to save. Once you've recovered your files, you'll want to do a factory reset, which can be done using that command you edited out of the .bat file. If you'r on Mac OS or Linux, the commands are basically the same as what's in the .bat file, but the commands begin with ./fastboot. You'll need to have the fastboot executable in the same directory as where you've extracted the files from the xml.
Just a quick note, Moto has a notorious reputation of not playing nicely with CM. This is just my personal opinion, but after trying some of the non-stock options, I've settled firmly on the stock rom, as it seems to be the most stable. If you need tether, root, etc, you can flash TWRP after you've gotten the phone back up and running, and use TWRP to install root and flash my stock tether enabler patch.
austtint said:
So for some reason today, my phone restarted and now I can't call people or receive calls, if I do. My phone restarts. Also can't use Bluetooth or it also does the same and restarts what can cause this? My phone getting too hot and damaged the motherboard? When I installed a kernel it was corrupted? I really have no understanding what caused this. I had resurrection from on it. I updated it with a newer one and did a bootloop. So I put cyangemod on it and worked but noticed those huge issues. Thinking the ROM was corrupted I put rr back on it and had the exact same issues. Any help would mean everything to me
Click to expand...
Click to collapse
Have you tried to make a google caller as default caller app? Does your imei correct also?
Hi everyone, I bought an S20 FE a week ago (the 4G Snapdragon version SM-G780G), the first thing I did is to root it because I knew that if I wanted to do it in the future I had to delete all of my data because is part of the process when you unlock the bootloader and I just wanted to do it right away.
The thing is that, now that I'm fully using it, I'm experiencing some issues while watching videos, I'm not talking about a certain app, I'm talking about videos in general, if I want to watch videos on YouTube, Facebook, TikTok or directly on the browser I can't do it properly. What happens is that the video starts with no sound at all, at about 3 seconds after that the video just freezes and then the sound that didn't play for those 3 seconds now is playing (but the video is frozen), when the audio reaches the same point as the video then the video starts playing again but no sound at all, 3 seconds after that same process, video freezes then the audio starts playing and so on.
I've been searching but no luck, can you guys point me in the right direction?
I'd try flashing your stock rom again, download it fresh and make sure it's the correct one.
use a backup app and good file browser to save stuff you don't wanna lose.
if you didn't have this problem before and others aren't having it along with you maybe some data got corrupted for video codecs ?
did you root with TWRP or patching AP ?
if it's the latter did you use ADB pull to move it back to PC or just windows ?
Can you recommend me a good backup app? I've already setted up my phone and I don't wanna lose anything.
The thing is that the first thing I did is to root the phone so I don't know if the problem was there before.
I downloaded the stock ROM via Frija and the root was done via AP patch with Odin.
Thanks for answering.
kaliko1991 said:
Can you recommend me a good backup app? I've already setted up my phone and I don't wanna lose anything.
The thing is that the first thing I did is to root the phone so I don't know if the problem was there before.
I downloaded the stock ROM via Frija and the root was done via AP patch with Odin.
Thanks for answering.
Click to expand...
Click to collapse
how did you move the patched AP archive back to your computer ?
we're supposed to use ADB to pull the file from the phone. using the normal windows file manager via USB isn't recommend for huge files. one wrong bit of data can have caused your problem.
I use an app from F-Droid called OAndBackupX but it only backs up apps and app data not system settings. you could try backing up some system apps and their data...
or you'd need either TWRP or (if it still works) titanium backup.
Well, the tutorial that I followed didn't require me to pull a huge file from my phone, just a boot.img.lz4 file that weight about 26 MB, maybe that's where everything went wrong.
Also I didn't install the TWRP, do you recommend to do the process all over again with the TWRP method?
kaliko1991 said:
Well, the tutorial that I followed didn't require me to pull a huge file from my phone, just a boot.img.lz4 file that weight about 26 MB, maybe that's where everything went wrong.
Also I didn't install the TWRP, do you recommend to do the process all over again with the TWRP method?
Click to expand...
Click to collapse
if you wanna be sure it's probably for the best. guess you couldn't have gotten the repacking wrong because it flashed. I'd download the firmware again.
3mel said:
if you wanna be sure it's probably for the best. guess you couldn't have gotten the repacking wrong because it flashed. I'd download the firmware again.
Click to expand...
Click to collapse
Ok so I just finished doing that all over again from the very beginning but this time I did the TWRP process, looks good for the moment. Thank you for the feedback, if the problem comes back I'll keep everyone posted.