Author edit: The phone's now fixed by flashing a stock rom using flashtool then re-rooting the phone ( the root permission is somehow lost when flashing)
OK so I have a big trouble here. My Xperia L wont boot after changing the fonts. All i did to my phone was changing the Roboto regular and bold to a custom TTF font using root browser to system/fonts and set the correct permissions the rebooted tje phone. I thought it wont do any harm because i did this thing multiple times to my phone and it always came up fine but this time no. Its stuck on boot screen (the flow thingy) and its just wont boot. I tried using ADB push to push the stock Roboto font but it didnt work. It says permission denied and I just cant proceed to restoring the font. Now Im running out of ideas, if someone can help me fix my phone please tell me because Im afraid that I can no lomger use the phone.
PS my phone is rooted and its using the stock rom and kernel. I havent unlocked the bootloader yet and I dont have any recovery installed
reflas tft, exclude all wipes and exclude everything except system
Just. A little note that I tried rebooting into recevery using adb reboot recovery, using wipe data factory reset the wiping cache and didnt work.
Tried
adb shell
data/xbin/su
Adb push Roboto-Regular.ttf
But didnt work. It says that the device not found. How can i fix this???? Pls help because my wife is now angry because I broke her phone.
Related
I recently changed back my build.prop to the original one that i backed up before. Then my device cannot boot anymore. It is stuck in the ASUS splash screen when i boot the device.
Then I flash the latest CWM recovery. But the latest version CWM cannot do anything like factory reset or flash zip.
After that, i tried to use the "wipe data" in the bootloader, it doesn't work either (still stuck in the splash screen).
And then i tried cold boot linux and it also doesn't work. Up to this point, I cannot find anyway to fix it.
However, I found that adb is somewhat working in CWM recovery. I tried "adb push build.prop /system/build.prop" (the build.prop is extracted from the US_epaduser_10_26_1_7_UpdateLauncher.zip package from ASUS official site), it doesn't work either.
I put the US_epaduser_10_26_1_7_UpdateLauncher.zip package from asus support site in sd card and tried to flash it by CWM recovery, it doesn't work either.
AFTER ALL THESE PROCEDURE, i think the system is corrupted because of some possible dirty wipe
IS THERE ANY WAY TO WIPE EVERYTHING AND RESET THE whOLE SYSTEM?
i feel like my device is completely dead... so i need help and solution asap
my device is unlocked, rooted, and updated to 10.26.1.7 android 4.3.
it is a US version.
btw i asked ASUS support and they said they would charge CAN$330 for fixing it (replacing the main board), which is.........
So is there any ways to fix it without sending it to asus repair ccenter?
I want to make sure that
1. The wipe data function in the bootloader works
2. Does wiping data in bootloader fix the build.prop problem
Or do anyone of you have any idea of solving tthis problem?
ANYWAY TO WIPE EVeRUTHING INCLUDES SYSTEM thROUGH BOOTLOADER?
sorry for my bad english
Have you tried to install Full Recovery Mode ?
First Enable USB Debugging and watch if your Device is correctly recognized on you Device Manager .
Search and install the software , for first use i suggest to search some Tutorials about this.
Then you can use the Full Recovery Mode and format / wipe cache and system .
So I’ve had my phone for about 3 weeks and from the get go I decided not to unlock the bootloader or root and just wanted to enjoy CM11S in its stock form. I downloaded and installed a bunch of CM11 themes and would constantly change them well once I changed the frost theme and ended up rebooting my phone the moment it booted into android I started getting spammed with unfortunately AudioFx has stopped errors and system UI crash.apk errors. I power my phone off as I am at work I reboot into the stock recovery and reluctantly did a factory reset and reboot thinking that it would relieve the problem. Upon that first initial reboot when you reach the cyanogens mod setup screen the audioFx errors return basically rendering the phone unusable. I found a method on android headlines to flash back to stock which I did through fastboot when I got home from work that do. I flashed the img files numerous times and I’m still greeted by the error upon reboot. My phone can’t be bricked because it actively lets me access fastboot and recovery…I even flashed twrp recovery and Cwm.img files through fastboot and successfully booted into recovery with no luck. My bootloader is locked so that basically stops me from flashing anything or mounting my internal storage in recovery. Every time I try to unlock the bootloader by fastboot oem unlock I get a counting second sequence on adb then nothing. Is there something I’m doing wrong I have rooted and unbricked tons of Android handsets. I love this handset Please help!!
I don't mean to be rude but please separate your text into different blocks (paragraphs). I'm getting very nauseous trying to understand what your problem is when I have to read 7-12 lines of text without any separation.
justinaquinnrambo said:
So I’ve had my phone for about 3 weeks and from the get go I decided not to unlock the bootloader or root and just wanted to enjoy CM11S in its stock form. I downloaded and installed a bunch of CM11 themes and would constantly change them well once I changed the frost theme and ended up rebooting my phone the moment it booted into android I started getting spammed with unfortunately AudioFx has stopped errors and system UI crash.apk errors. I power my phone off as I am at work I reboot into the stock recovery and reluctantly did a factory reset and reboot thinking that it would relieve the problem. Upon that first initial reboot when you reach the cyanogens mod setup screen the audioFx errors return basically rendering the phone unusable. I found a method on android headlines to flash back to stock which I did through fastboot when I got home from work that do. I flashed the img files numerous times and I’m still greeted by the error upon reboot. My phone can’t be bricked because it actively lets me access fastboot and recovery…I even flashed twrp recovery and Cwm.img files through fastboot and successfully booted into recovery with no luck. My bootloader is locked so that basically stops me from flashing anything or mounting my internal storage in recovery. Every time I try to unlock the bootloader by fastboot oem unlock I get a counting second sequence on adb then nothing. Is there something I’m doing wrong I have rooted and unbricked tons of Android handsets. I love this handset Please help!!
Click to expand...
Click to collapse
I'm also in the same boat.
In essence on bootup the phone gives a message that "AudioFX has stopped" on clicking the OK button the message appears within a second rendering the device unusable.
My first guess for me will be to remove the last installed app (which in this case was the Cerberus (cerberus_disguised-4.4.zip)
I flashed the version that integrates with the OS to prevent thieves being able to factory reset and remove protections.
**EDIT**
Okay it was an easy solve,
I removed via ADB , Volume+ which was causing the issue and will be moving instead to Viper4android
I had the same problem after changing some values in mixer_paths.xml and i follow this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and flash the phone.This guide will wipe your data,fotos,e.t.c.
You don't need to flash everything to fix the issue.
From the guide posted above, just download the factory image and ADB/fastboot tools, extract everything and flash system using "fastboot flash system system.img".
That restores the broken mixer_paths.xml in the /system/etc folder to the standard version. You don't even loose anything you installed or setup, as it's all on the data partition.
Btw, it's a very strange thing, that changing themes actually messes up a file which has nothing to do with themes, but is related to sound settings.
Dzhedaj said:
You don't need to flash everything to fix the issue.
From the guide posted above, just download the factory image and ADB/fastboot tools, extract everything and flash system using "fastboot flash system system.img".
That restores the broken mixer_paths.xml in the /system/etc folder to the standard version. You don't even loose anything you installed or setup, as it's all on the data partition.
Btw, it's a very strange thing, that changing themes actually messes up a file which has nothing to do with themes, but is related to sound settings.
Click to expand...
Click to collapse
How do you "fastboot flash system system.img" when you are in fast boot mode?
---------- Post added at 06:33 PM ---------- Previous post was at 06:13 PM ----------
Dzhedaj said:
You don't need to flash everything to fix the issue.
From the guide posted above, just download the factory image and ADB/fastboot tools, extract everything and flash system using "fastboot flash system system.img".
That restores the broken mixer_paths.xml in the /system/etc folder to the standard version. You don't even loose anything you installed or setup, as it's all on the data partition.
Btw, it's a very strange thing, that changing themes actually messes up a file which has nothing to do with themes, but is related to sound settings.
Click to expand...
Click to collapse
I'm a noob. Can you be more specific?
zoro25 said:
I'm also in the same boat.
In essence on bootup the phone gives a message that "AudioFX has stopped" on clicking the OK button the message appears within a second rendering the device unusable.
My first guess for me will be to remove the last installed app (which in this case was the Cerberus (cerberus_disguised-4.4.zip)
I flashed the version that integrates with the OS to prevent thieves being able to factory reset and remove protections.
**EDIT**
Okay it was an easy solve,
I removed via ADB , Volume+ which was causing the issue and will be moving instead to Viper4android
Click to expand...
Click to collapse
Would you be kind enough to tell me exactly what you put into the cmd screen to get volume+ removed? I'm having the exact same issue, and im pretty bad with adb. i've been looking for hours for a solution that works.
none of the previous methods work
has anyone gotten a method to work? i've tried every method above in this thread
edit:
except the adb command to remove the volume+ app because I don't have adb access while the phone is at the Cyanogen Welcome screen
You guys didn't search hard enough if you're still having this audiofx issue.
Here you go. Read my op carefully
http://forum.xda-developers.com/showthread.php?p=55488755
Dzhedaj said:
You don't need to flash everything to fix the issue.
From the guide posted above, just download the factory image and ADB/fastboot tools, extract everything and flash system using "fastboot flash system system.img".
That restores the broken mixer_paths.xml in the /system/etc folder to the standard version. You don't even loose anything you installed or setup, as it's all on the data partition.
Btw, it's a very strange thing, that changing themes actually messes up a file which has nothing to do with themes, but is related to sound settings.
Click to expand...
Click to collapse
Thank you so much! Your method is work!!!!!
I guess the audiofx FC loop may due to I have edited the file under system/etc for louder headset volume.....
Anyway, thanks again!
Here's the whole story:
I accidentally changed the file permission of the Permission folder, what happened was after rebooting other application suddenly stop working. So what I did
was factory reset the phone from the phone settings but the problem now is that the phone keeps rebooting over and over again. I did go to the recovery mode and factory reset and clear cache but the problem still persists. How can i fix this?? (
Phone specs:
Model : O+ 360
Ram: 1024mb
OS: Android Kitkat 4.4.2
Hi there
The thing is, when you modify your system file and it decides to cause issues. You can't fix it without the original file.
Factory resetting it will only make it worse as in this case you're now experiencing boot loops. Factory resetting will only revert the settings, remove installed apps, and user edited content.
However, it will not revert the changes you made to the system because it doesn't know what to revert back to.
In many cases, an easy fix can be attempted. This however varies on your device, you can install a different ROM using a custom recovery or... You can look for a factory image for your device and flash it (for those that have stock recoveries).
So I believe you should look around the net for a factory image for YOUR device.
Then flash it.
THANKS for the suggestion!! I'll try hard to look for that . I do have question what does "clear emmc" means?
Usually custom roms keeps the base from stock firmware rom.Well you can find any custom rom 4.2.2 for your model spec. extract from the zip your permission file and copy to your phone and then move it appropriate system folder and reboot .Don't forget to give permission file rw-r-r.
For all this procedure you must have Rooted phone.
DO NOT CLEAR EMMC!
Good luck
Sent from my SGH-317M using XDA Free mobile app
Can I use other O+ model cwm for my phone because i cant find a replacement . Sorry for being noob.
Well, you Can try this:
1.Go to recovery and check if there is "fix permissions" option.(maybe you will be Iucky)
2.Flash CWM recovery for your device and select "Fix permission"
3.You can go to recovery (stock) mode and fix permissions via adb (by using pc).
flashing an other recovery it's a bit risky
Sent from my SGH-317M using XDA Free mobile app
actually i press the clear emmc button once and nothing happens still the same.
my O+ 360 stock in BlackScreen After i Flash O+ 360 Rom , I Downloaded from Needrom.com ..
So, my tablet, which has root access is stuck in a bootloop. I cause this doing the following: along the way I change the build.prop file to change the device ID in order to be able to install an app. Everything worked fine. I made a backup of the origininal build.prop file. Sometime later I replaced the altered buil.prop file with the original build.prop file. I rebooted the tablet and now it is stuck in a bootloop. I don't have any custom recovery installed and the computer doesn't recognize my device. I already tried factory reset and wipe cache numerous times. Nothing works. Ideas?
XDA Visitor said:
So, my tablet, which has root access is stuck in a bootloop. I cause this doing the following: along the way I change the build.prop file to change the device ID in order to be able to install an app. Everything worked fine. I made a backup of the origininal build.prop file. Sometime later I replaced the altered buil.prop file with the original build.prop file. I rebooted the tablet and now it is stuck in a bootloop. I don't have any custom recovery installed and the computer doesn't recognize my device. I already tried factory reset and wipe cache numerous times. Nothing works. Ideas?
Click to expand...
Click to collapse
Hello, and welcome to XDA! You could try to flash a custom recovery through fastboot, wipe and flash a rom. For your computer to recognise your device, you need to install the corresponding drivers on your pc.
Good luck!
Recently i bought this device, i was able to root it using kingroot, yesterday i tried installing the xposed framework, since i didn't have custom recovery i saw a tutorial in youtube explaining how to install the framework without the need of custom recovery (it was a huge mistake), using a combo of busybox and the terminal emulator, the result was a bootloop, i am able to enter the factory recovery but even after wiping the data/cache to factory settings its still stuck on the bootloop. Since i dont have custom recovery i am kinda stuck and without pc at the moment its starting to seem like a lost case, the factory recovery as the option to enable adb, i found a tutorial online but i don't understand anything about batch files and it all seems kinda confusing to me. In the past i was able to unbrick my old phones using stock roms, using odin if i recall right, but since the device is fairly new i am unable to find a stock rom. My questions are,
can i use odin again using a 5.1.1 lollipop normal (rom)?
Is there an easier to follow tutorial on how to use the adb fuction?
Is there a way to instal cwm even in bootloop without the use of adb? Since wiping dalvik cache and fix permissions should fix the problem.