Related
Hi,
I recently updated my Z1c (rooted, Kingroot) using the Xperia Companion because I got annoyed by the constant update notification. After updating to Build 14.6.A.236, I re-rooted using Kingroot again, however, with a couple of issues:
-AdAway reports that it fails to replace the host-file to block ads despite having root authorization.
-Link2SD reports that the secondary partition on my SD card (which worked fine so far) was mounted after bootup, and gave me the choice between a fast reboot (which didn't solve it) and creating a new mount-script, which results in a "can't unmount /data/sdext2: Invalid argument mount: Operation not permitted" message.
Titanium Backup on the other hand works fine.
Unrelated to the Update I also noticed that the point on the screen where the touch was recognized would randomly jump around the width of where I touched the screen while charging, and only while charging.
I apologize for anything imcomprehensive my non-native English may have caused and thank you in advance for any help.
Kind regards,
Skysoarer
Skysoarer said:
Hi,
I recently updated my Z1c (rooted, Kingroot) using the Xperia Companion because I got annoyed by the constant update notification. After updating to Build 14.6.A.236, I re-rooted using Kingroot again, however, with a couple of issues:
-AdAway reports that it fails to replace the host-file to block ads despite having root authorization.
-Link2SD reports that the secondary partition on my SD card (which worked fine so far) was mounted after bootup, and gave me the choice between a fast reboot (which didn't solve it) and creating a new mount-script, which results in a "can't unmount /data/sdext2: Invalid argument mount: Operation not permitted" message.
Titanium Backup on the other hand works fine.
Unrelated to the Update I also noticed that the point on the screen where the touch was recognized would randomly jump around the width of where I touched the screen while charging, and only while charging.
I apologize for anything imcomprehensive my non-native English may have caused and thank you in advance for any help.
Kind regards,
Skysoarer
Click to expand...
Click to collapse
For the first 2, sounds like rw access, known to be an issue on newer lp builds. Flashing Nut's dual recovery usually takes care of it Also, check this - http://forum.xda-developers.com/showpost.php?p=67828175&postcount=1610 Also, try setting SELinux to permissive.
Other issue seems like random display bug. Might go away after reboot, or maybe cache wipe or something, not sure...
Alright, hello everyone,
I'm having a pretty weird issue here. I've flashed my DUK-L09 and the C432B183 EU Firmware, everything was running fine.
I couldn't make a backup of the /data/ partition though, someone told me to wipe the data to decrypt it, but nothing came good after this.
So I tried to flash back the old recovery image by extracting it, flashing it via fastboot, as I would normally do; enter the factory reset, run it.
Everything is good, it goes up to 100% pretty fast, less than 2 minutes. I then enter the setup wizard the NFC is acting weird. It keeps activating
and deactivating illogically. So, ignoring this issue, I kept up configuring the phone then once I'm logged in Google and sync'd, pops a Huawei ID
logging page really really fast then goes back to the EMUI menu at the beginning of the Setup, in an infinite loop.
Useful information to let you help me better:
- Many firmwares. Currently trying to flash back to B120a and NoCheck from OldDroid and Morph. (Edit: Didn't work)
- Phone unlocked, TWRP accessible.
- Getting a weird "Error 9" when trying to run Update.zip from TWRP.
- Sideload working, but not transferring anything.
- Cannot find any B182 or B130 stock firmware. Everything seems to be gone from Huawei's servers.
- The loading logo isn't Honor anymore but Android, for a reason I can't yet understand.
- Restoring a clean backup (without /data/, since I couldn't back it up) did not fix the problem.
- Trying to update with the 3 buttons do not work, even with the right firmware (C432B183) (Software install failed)
- Factory reset works with the right ROM, but gets me to the setup loop issue.
- The loop occurs when I am supposed to see the Huawei ID setup page. If I do not put any SIM card, or WiFi
I am prompted to choose which way to restore data; if I skip this step, it blinks and doesn't do anything.
- I tried to restore via WiFi (Google's cloud stored data from my account), but it does the same thing as mentioned
earlier. It blinks multiple times rapidly the "Huawei ID" setup page then goes back to the first Setup screen w/o
me being able to do anything about that.
I'll be glad if you knew the answer to this, because I'm all lost right now.
Greetings, Kameyuu.
UP !
After many tries and a LOT of hard work, and spent an entire night (was about to spend the second night on this), I found the culprit and now I know what the issue is, it sounds completely legitimate.
So here are the reason and the solution to this issue:
Actually, my CUST was somehow broken. I never flashed it back because no one told me to flash the CUST.img back. They told me to flash BOOT, SYSTEM, and RECOVERY only.
So, after I downloaded a software called HUAWEI Multi-Tool (From hwmt.ru) I noticed they were also asking for the CUST.img and USERDATA.img (<- this one was apparently optional)
So, trying my luck I flashed it. Did a factory reset, and all, it acted weird and failed, then I tried again and it succeeded. So, with all my hope I booted the phone to the system, started configuring... And it worked !
I was able to set up the phone. For a -yet- unknown reason, some apps look missing and the NFC is still blinking on and off repeatedly and randomly, but I'm investigating that.
If you have any question on the precise steps feel free to send me a PM or ask in the thread directly I'll be glad to sort your issue out.
[EDIT]
Sorry, double post I don't know why my message was posted twice. Feel free to delete this message @moderators
Hi
Since installing the December 2018 update to Android Pie last week my phone has become unusable. It freezes for 5-10s period all the time while using. Sometime, when it wakes back up again, there is a message on the lock screen that says 'you need to unlock using pattern after reboot' which makes me think the phone is crashing and rebooting itself while the screen stays frozen.
I have done a factory reset twice. In fact, directly after the December 2018 update, the phone got stuck in a boot loop and I had to factory reset then, as well.
Anyway I did some research on here and have run Androbench as people seem to be blaming poor write performance. See image.
Please - what can I do? Roll back to an earlier version of Android? The phone has worked perfectly for months until last week.
Many thanks.
you could try to reflash the latest pie rom with miflashtool. if you tick "flash all expect storage" you wont 't lose any data
download the latest rom from website, extract the image folder with contents inside and add this flashall.bat to the image folder contents, https://1drv.ms/u/s!AqlJY73bUA7rhokx5kWL6MAtXYDRTg . This will completely flash the whole phone without relocking the bootloader. I had exact same issue after using twrp to make a nand, its had something to do with accessing firmware while making backup, i think this will sort your phone out, dont use miflashtool its a total mess. Dont mess with flash order, ppl may say it doesnt matter what order its done, but it does matter. Instructions are, assuming you have adbtools, to use admin cmd prompt to the image folder and type flashall.bat, you need to add adb platformtools to windows system variables path.
Brilliant - thanks for the reply. What you suggest is probably on the limit of my skills and experience, so I have a few questions if that is OK:
boe323 said:
download the latest rom from website,
Click to expand...
Click to collapse
So, this? https://en.miui.com/download-354.html
boe323 said:
extract the image folder with contents inside and add this flashall.bat to the image folder contents, https://1drv.ms/u/s!AqlJY73bUA7rhokx5kWL6MAtXYDRTg .
Click to expand...
Click to collapse
I assume just copy & paste this file into the main folder?
boe323 said:
Instructions are, assuming you have adbtools, to use admin cmd prompt to the image folder and type flashall.bat, you need to add adb platformtools to windows system variables path.
Click to expand...
Click to collapse
Thanks, I will check that platform tools is in the system variables path. Maybe it will become clear, but I can't remember if the rom image needs to be stored on the phone or PC before I start?
Thanks
After fixing itself last time (with a factory reset), my phone's performance has gone absolutely again since the September update. It hangs constantly, takes 10 mins to turn on, and is generally unusable. Memory logs below.
This time nothing I have tried will fix it, I have tried: factory reset from bootloader, miflash to latest rom, using fastboot to flash latest rom, using the modified flash_all.bat from boe323 (thanks for your help last time).
Still the performance is dreadful.
Is there anything else I can try before I throw this phone away?
Thanks anyone for helping
Flash lastest stock (10.0.13.0) with no flash but use: fastboot oem edl , u can search in you tube how to do is easy
Hi, thanks for idea, I did this last night (new memory logs attached)
Still I get the same issues. system UI hangs and crashes basically make the device slow and unusable, especially in Chrome.
Any ideas on what I could do next?
Ideas gratefully received
Thanks
yeahdisk said:
Hi, thanks for idea, I did this last night (new memory logs attached)
Still I get the same issues. system UI hangs and crashes basically make the device slow and unusable, especially in Chrome.
Any ideas on what I could do next?
Ideas gratefully received
Thanks
Click to expand...
Click to collapse
If nothing helps , just use MiFlash , and don't use clear all , use clear all_lock.Relock your bootloader and test if everything is working ok. If it doesn't - then I hope you have warranty. Relocking and unlocking the bootloader is so easy , so you don't have to be worried about nothing. Then you will be sure , if the problem presists with totally stock firnware , then you have only one choice.
thanks - trying this now
Downloaded your app and tested it on my perfectly working device. No problems at all, no hangs, fluid, etc.
I attached the results.
If you flashed stock ROM and the speeds are that horrible... you should check if any apps are causing the hangs. Reboot in SafeMode and check the speeds. If the phone behaves normally in SafeMode, than something you installed/configured is causing the said problems.
The last solution would be... checking the NAND chip, I don't quite know if there are apps that could check the sectors in the NAND memory. Maybe you are experiencing a bad nand/multiple bad sectors slowing down everything... But from my knowledge this shouldn't be a problem in current technology, since Android has auto-trim and bad sectors should be ignored, not affecting performance.
From my experience August update fixed the problems and September brought a system speed-up. I feel the phone even more snappy now.
Thank you for this. My phone is fine in Safe Mode! I didn't think of this, as when I was relfashing the Rom I wasn't installing any additional apps - just the Androbench to check performance (always after checking that the problem was happening).
So, what to do? Does this mean that one of the Stock ROM apps? is causing the issue? How to fix?
Many thanks for your help
yeahdisk said:
Thank you for this. My phone is fine in Safe Mode! I didn't think of this, as when I was relfashing the Rom I wasn't installing any additional apps - just the Androbench to check performance (always after checking that the problem was happening).
So, what to do? Does this mean that one of the Stock ROM apps? is causing the issue? How to fix?
Many thanks for your help
Click to expand...
Click to collapse
Get an app like System Panel 2. Set it to monitor all apps/system activity and check where the hangs comes from. Maybe even AndroBench is the culprit in your case.
Anyway, get a system monitor app that can log all app activity individually and see which app has the most cpu usage and which app has the most disk usage.
But by the fact that your phone is running extremely slow after reflash, I suspect the back-up/restore system. Maybe it downloads some corrupt data and hangs the system. If that is the case, a new Google Account may fix the problem. Start fresh.
OMG I took the memory card out and everything is working fantastic again
yeahdisk said:
OMG I took the memory card out and everything is working fantastic again
Click to expand...
Click to collapse
If the SD was your problem, check out the solution I found here: https://forum.xda-developers.com/showpost.php?p=80172348&postcount=19
SOLVED - Update below.
Hey guys,
I have an S9 (SM-G960F) which appears to have auto-updated during the night and as a result will now not boot. I am making an assumption it was an update of some sort as when I checked the time on it at 1am it was fine, when I woke around 8.30am the phone was off and when powering it on I ran into the issue. To summarise, I power the device on, get the Samsung loading screen, then the black swipe pattern screen to decrypt the phone, followed by the padlock unlocking loading screen, then the phone reboots. Sometimes however, the device gets past the padlock loading screen and says it is optimising apps, which is then followed by a reboot, briefly says it is installing system update before landing me at the Android Recovery screen.
What I've tried:
- Soft reset
- Booting in safe mode (same result as booting normally)
- Clearing cache partition
- Clearing app data
- Lacking storage booting (the device was quite low on storage last time I checked)
Some other (maybe) useful info:
I haven't updated the phone for months, could be why it did an auto update.
I'm on EE in the UK but IIRC the phone is not locked to EE.
Android Recovery has the following info when I load into it
Code:
samsung/starltexx/starlte
9/PPR1.180610.011/G960FXXU2CSB9
(options to try again, erase app data, power off, view rescue log)
#Reboot Recovery Cause is [system_server:12259 RecoverySystemRescueParty]#
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
Viewing the rescue log presents me with a stacktrace , the top of which is
Code:
*** FATAL EXCEPTION IN SYSTEM PROCESS: main
java.lang.RuntimeException: Failed to create service com.android.server.job.JobSchedulerService: service constructor threw an exception
(followed by the rest of the stacktrace I can get a picture of if necessary)
My goal here is to recover the photos on the internal storage as they don't appear to be backed up to Google photos, nor Samsung's alternative - which is particularly painful cause I'm the one usually preaching backups.
Is there anyway to recover the OS to retrieve data, or pull the data off the device without wiping it? I'm open to any suggestions on how to do this, the main goal here is saving my photos, hence why I have avoided a factory reset from the Android Recovery menu.
Hope I've been clear enough, but let me know if I need to clarify anything. I would greatly appreciate any suggestions!
Thanks,
Matt
Hey guys,
After spending all day tearing my hair out with this I managed to fix it, so I guess this thread can be closed. For anyone who gets into a similar situation...
I attempted to solve this by flashing the current firmware using Odin and booting into "download mode", found a copy on sammobile.com. This didn't work, leaving me in the same situation, and as I felt I was running out of options I tried using the latest firmware for my device. I found a copy using a tool I found on these forums - Frija. Fired up Odin and download mode again, selected the AP/BL/CP/HOME_CSC (I understand using HOME_CSC is important so as not to cause a factory reset) and this worked! This left all of my files intact and as a bonus I'm also up-to-date with Android too. I'm backing up my photos as we speak as I would hate to be in this situation again!
Hope that can help someone in the future.
Cheers,
Matt
Which version of Odin did you use?
majormatt said:
Hey guys,
After spending all day tearing my hair out with this I managed to fix it, so I guess this thread can be closed. For anyone who gets into a similar situation...
I attempted to solve this by flashing the current firmware using Odin and booting into "download mode", found a copy on sammobile.com. This didn't work, leaving me in the same situation, and as I felt I was running out of options I tried using the latest firmware for my device. I found a copy using a tool I found on these forums - Frija. Fired up Odin and download mode again, selected the AP/BL/CP/HOME_CSC (I understand using HOME_CSC is important so as not to cause a factory reset) and this worked! This left all of my files intact and as a bonus I'm also up-to-date with Android too. I'm backing up my photos as we speak as I would hate to be in this situation again!
Hope that can help someone in the future.
Cheers,
Matt
Click to expand...
Click to collapse
I would really appreciate it if you post a YouTube tutorial on how to fix this. Because we are facing the same problem right now but I have no idea what solution you prescribed. Thank you and God bless.
I use Motorola Edge S, with LOS 19.1. From v20220709 and after, bluetooth cannot be connected any more.
I want to flash back to v20220618, but Motorola system disallow downgrading, even its rom is LOS.
Can anyone tell me how to modify the LOS.zip (e.g. the date in the files of metadata & metadata.pb, checksum, ......), so that I can cheat the system to allow flashing the earlier version, without causing damaging problem ?