Recently I've been experiencing problems trying to listen to online radios through mpv in Termux and Terminal Emulator. It used to work before.
It runs the command, plays for less then a second because I can hear something, then it stops and gives me the segmentation fault.
My phone is an Xperia Z C6603, rooted with stock rom, debloated to the bone by myself, locked bootloader -> no recovery.
I've tried hard reset and reflashed the phone twice with Sony software repair, but i still get the error.
I've read here and on other websites that an fsck must be performed, but:
- i don't have a recovery so I cannot unmount the partitions
- I don't know which partition to fsck: I get a TON of lines when I type su -c mount
Could someone please help me?
EDIT: I've managed to install TeamWin dualxzrecovery. Now what?
Related
Hi,
I'm having issues with my device (Cherry Mobile Flare S [Q360]). I tried to re-partition the device to give the internal store more space. But it seems that I used the wrong apk. (stupid me used Mt657xRepartition instead of MT6582Repartition ). After reboot, problems began to arise, As the title says, I'm stuck on boot screen. I am able to use TWRP but all it shows is that it is unable to mount anything (except for the External-SD). ADP sideload fails as well. I tried installing a Clean stock rom for my phone but it fails. Factory Reset / Wipe / Advance Wipe fails. Fastboot flash fails as well since it cant access the partitions. ADP is unable to detect device (Due to ADP sideload is failing) .
Is there anything that can be done to resolve this issue? Already check different treads and tried different methods. But none matches the issue i have. Still, I might be missing something.
Thanks in advance.
Hi, If this thread is in the wrong forum,please move it.
I have a rooted Xperia Neo V (2.3.4 gingerbread). I started to do some changes to build.prop. I mistakenly changed the SDK version to 16 (although the original was 10 I think) and restarted. upon restarting,Google play and SuperUser crashed. I tried to launch some other apps but they crashed too. I could install ICS apps but they crashed as well.. only some small apps work including the stock apps. Now I can't reverse the change because whenever I open build.prop editor, it asks for root but SU crashes denying it..I tried factory reset,Unrooting and rooting again but same problem..I tried adb pull/push and successfully got the file but I can't send it back because the system is read/write protected or something...to change the read/write thing I need Su permission which I already can't get..I tried installing CWM recovery but now when the phone reboots a blue light flashes for some time and if I press a button(e.g volume down) the phone is stuck there until I take the battery out.The phone only boots up successfully If I don't touch it while it is booting up.
I have a backup of build.prop that I made with Romtoolbox.
What should I do now? Need some help.
Bump?
Help is needed Guys!
Seriously nobody on Xda forums can help me?
Wow. Nobody can help me here?(Bump)
this place is dead
I have an obscure cheap offbrand phone and have been trying to root it for 3 years to which I at last managed to root it with Kingroot, which up to recently, didnt used to work by rooting it (nothing did). So I have root access, its a step in the right direction but ultimately I'm trying to flash a custom rom like cyangwin.
The problem is 2 things, my phones bootloader is weird, its like its been stripped of everything and does absolutely nothing. Fastboot tools finds it but all attempts at any kind of interaction just cause it to hang with "..." indefinitely. Anytime I fastboot I almost always have to take battery out and re-insert it as theres no way of leaving fastboot.
The other problem is I deleted all the garbage apps that came with my phone which caused Google services like playstore to crash so I decided to reformat and re-root my phone but the recovery didn't recover my phone, it only formatted 2 folders /data and something else so I now have a stable phone but is void of all Google services including play-store but all the garabage apps are still missing so thats a plus. Also the recovery left all my setup and configuration as-is like wifi passwords which I found odd for a factory reset.
I adb installed several root apps like RomToolkit and am just trying to figure out what to do now and how to proceed from here. I have a rooted phone, is stable, void of all garbage apps and google apps, services, and the like including playstore. I want to flash a rom and have no fastboot to work with. Any help as to where I can go from here? Is there no way I can just brute force it since I have root filesystem access? Maybe replace fastboot with one that works as expected?
[email protected],
just bought myself an Ulefone T1 from aliexpress and I am wondering if there is any lineageos development out there for this phone? Is anybody planning to develop for this?
cheers
JohnnyT
Stay tunned. The phone is new and development will yet. Dont worry is a great phone and Ulefone is better than yesterday.
https://www.needrom.com/category/ulefone/t1-ulefone/
It will hardly receive official updates, let alone custom ROMs (same fate as the 96% of MediaTek devices out there).
any update . i just bought this phone from banggood. my asus zenfone 3 wifi is failing. so needed something to fill the gap
Finally received my t1 after 11 weeks of waiting!!
Everything works fine apart from the battery usage which is a round 10% per hour on standby with no usage!!
FOLLOW-UP
Following lots of research found that Whatsapp was still trying to verify the phone thru SMS and was draining the battery. Uninstalled and re-installed Whatsapp and verified by manually entering SMS pin.
Now appears to running okay at just over 2% per hour battery drain with bluetooth and GPS set on.
i think i got a thud. reboots when connected to 5g wifi and sometimes when doing stuff on the phone. what a POS phone. never again ulefone!
I am very happy with my T1. High performance, loads of RAM and storage in a decent looking dual SIM package for a very reasonable price tag. First official OTA update yesterday. Also there are rumors about 8.0 upgrade till end of the year.
JohnnyT
Alicklee said:
i think i got a thud. reboots when connected to 5g wifi and sometimes when doing stuff on the phone. what a POS phone. never again ulefone!
Click to expand...
Click to collapse
Mine does occasional reboot. I think its when my mail app is in 'recent apps'. When I clear recent apps. The phone seems more stable, but it's early days.
If anyone finds a fix, please post to the group.
I had my first ota update so that was a plus although it didn't solve the rebooting or activate the 'so called' second camera.
Pickles871 said:
Mine does occasional reboot. I think its when my mail app is in 'recent apps'. When I clear recent apps. The phone seems more stable, but it's early days.
If anyone finds a fix, please post to the group.
I had my first ota update so that was a plus although it didn't solve the rebooting or activate the 'so called' second camera.
Click to expand...
Click to collapse
Do you have yours rooted and your bootloader unlocked? I am getting the update prompt but being unlocked and rooted I'm not sure it will take the update. Some phones tend to brick. Also all of a sudden I am having an issue with "android process.media has stopped" Can't figure out what's causing it but since it started the device has become quite laggy
Mine is not rooted. Its still as out of the box. I have rooted previous phones but find that some of the apps I want to use won't run on rooted phones, like certain banking apps. I don't know if the restarts are an Android 7.0 symptom or hardware/software based. There are so many different views on this it's almost impossible to figure out the causes. For me I keep trying different app and phone settings in the hope that something eventually solves the issue. Maybe a future firmware update will sort it. I live in hope (but don't hold your breath). More likely a new phone will be acquired at some point!
by any chance any of you have gps problems in waze or maps????
Pickles871 said:
Mine is not rooted. Its still as out of the box. I have rooted previous phones but find that some of the apps I want to use won't run on rooted phones, like certain banking apps. I don't know if the restarts are an Android 7.0 symptom or hardware/software based. There are so many different views on this it's almost impossible to figure out the causes. For me I keep trying different app and phone settings in the hope that something eventually solves the issue. Maybe a future firmware update will sort it. I live in hope (but don't hold your breath). More likely a new phone will be acquired at some point!
Click to expand...
Click to collapse
you need to proper root with magisk. and only use magisk, not other super user apps.
with magisk hide you can cheat banking apps or any app thinking the phone is not rooted.
nieXas said:
you need to proper root with magisk. and only use magisk, not other super user apps.
with magisk hide you can cheat banking apps or any app thinking the phone is not rooted.
Click to expand...
Click to collapse
Thats useful to know. Many thanks
Made Lineage 14.1 work on my Ulefone T1 (adb shell hacked)
Hi everyone,
i've been digging around for the last few weeks on my T1 and now i've finally made it boot. I dont know exactly what is working and what not but i can tell WLAN is NOT working for now! The kernel repo at my github was not working so i used the stock one. You may download it as well as the TWRP recovery i made alongside the ROM. But you need to wipe /data partition so all user data is lost in the process. Also while TWRP needs a reboot after wiping /data step 2 & 3 may need to be repeated once. For now i was not able to flash and boot the recovery (working on it) but it can be booted into as follows (when booted into the stock system):
UPDATE: Made it work - it's booting without hacking via ADB-Shell. The parts marked --- obsolete --- are not needed any more.
1.) Disable OEM-Lock in Developer-Options (google if necessary how to do that)
2.) Reboot and keep the upper volume button button pressed until it booted into recovery. If the "no command" screen is displayed, press the power and upper volume button together once again and you shuld reside in the stock recovery. Use it to reboot into fastboot (bootloader).
3.) In fastboot mode, while beeing in the same folder as the downloaded files, type the following:
Code:
fastboot boot recovery.img
4.) Wait for TWRP to boot up and enter the following (within the same folder):
Code:
adb push lineage-14.1-*-UNOFFICIAL-t1.zip /sdcard/
5.) Finally you may flash the Lineage zip file in TWRP (if you have wiped your /data partition at least i needed to)
----------------------------------- obsolete -----------------------------------
6.) Let it reboot into system and while displaying the Linage bootanimation (for now) i had to execute a few commands on adb shell. So, with adb installed, you need to enter the following commands in a common linux/windows shell:
adb shell /vendor/bin/nvram_daemon &
adb shell /system/bin/nvram_proximity &
adb shell /vendor/bin/nvram_agent_binder &
adb shell /system/bin/agoldnvram &
adb shell /system/bin/audioserver &
Click to expand...
Click to collapse
I'm not sure if they are all needed but afterwards my T1 bootet up correcty (more or less). Unfortunately a few drivers are missing as it seems while WLAN is not working for now.
http://d0ndroid.janeiskla.de/lineage-14.1-20180928-UNOFFICIAL-t1.zip
and the recovery
http://d0ndroid.janeiskla.de/recovery.img.
----------------------------------- obsolete -----------------------------------
After fixing another few things the only remaining things i found not working are fingerprint & RIL but I'm looking into that right now. The current builds will always be uploaded to:
http://d0ndroid.janeiskla.de/
The sources i used besides the default Lineage ones are on github:
https://github.com/d0n?tab=repositories
Have fun! And let me know if you make progress on your own
Greez,
d0n
Hi d0n22, are you still working with this rom?
Hi, My Mi A3 keeps restarting. If i stay a while without using the phone it simply restarts and expects sim code to start again. The result is that ithou knowing i'm contantly with the phone shut down. Anyone can help? Thanks
You need to provide a bit more information than that.
Have you flashed anything at all to the device (magisk, twrp, ROM, any kind of mod)
Is it completely stock?
If so it sounds like a software issue and reflashing the stock rom with mi flash tools may help
garylawwd said:
You need to provide a bit more information than that.
Have you flashed anything at all to the device (magisk, twrp, ROM, any kind of mod)
Is it completely stock?
If so it sounds like a software issue and reflashing the stock rom with mi flash tools may help
Click to expand...
Click to collapse
Hi, thanks for the prompt reply. Yes, is just stock ROM. Android 9 plus november security patch. Already did a factory reset and the problem remains. The only uncommon thig i've noticed was an android.process.acore error which i today tried to solve by seaching solutions online. Thanks
jcoelho111 said:
Hi, thanks for the prompt reply. Yes, is just stock ROM. Android 9 plus november security patch. Already did a factory reset and the problem remains. The only uncommon thig i've noticed was an android.process.acore error which i today tried to solve by seaching solutions online. Thanks
Click to expand...
Click to collapse
That's an issue with your contacts and nothing to do with random reboots which may indicate that the update to November sec patch might have caused this issue. Something may have happened when you updated and caused some files to get messed up somehow which is why a factory reset won't work.
That's why it still hasn't fixed the android.process.acore error or the random reboots
As I said in my previous post, reflash the latest rom with mi flash tools and that issue may very well get fixed.
garylawwd said:
That's an issue with your contacts and nothing to do with random reboots which may indicate that the update to November sec patch might have caused this issue. Something may have happened when you updated and caused some files to get messed up somehow which is why a factory reset won't work.
That's why it still hasn't fixed the android.process.acore error or the random reboots
As I said in my previous post, reflash the latest rom with mi flash tools and that issue may very well get fixed.
Click to expand...
Click to collapse
ok. thanks once again
wipe format cache data everything internal storage too( it will delete ALL ypur photos,videos etc.) flash stock rom or any custom rom . i hope it will be solved
jcoelho111 said:
Hi, My Mi A3 keeps restarting. If i stay a while without using the phone it simply restarts and expects sim code to start again. The result is that ithou knowing i'm contantly with the phone shut down. Anyone can help? Thanks
Click to expand...
Click to collapse
How often does it happen? You could try connecting your phone to a PC and keep running "adb logcat" to catch the crash. Also try capturing logcat right after a reboot, it might contain some useful info about the crash.
With root you could get additional info:
Kernel Log:
adb shell su -c dmesg > dmesg.log
Last_kmsg:
adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log
sasukeob said:
wipe format cache data everything internal storage too( it will delete ALL ypur photos,videos etc.) flash stock rom or any custom rom . i hope it will be solved
Click to expand...
Click to collapse
thanks
_mysiak_ said:
How often does it happen? You could try connecting your phone to a PC and keep running "adb logcat" to catch the crash. Also try capturing logcat right after a reboot, it might contain some useful info about the crash.
With root you could get additional info:
Kernel Log:
adb shell su -c dmesg > dmesg.log
Last_kmsg:
adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log
Click to expand...
Click to collapse
thanks
I got the same problem...How do I reflash the latest rom with mi flash tools?
any one tried with Miflash till now? please update your feed back here
---------- Post added at 12:45 PM ---------- Previous post was at 12:28 PM ----------
@garylawwd
A3 have ufs memory and all ufs have different configuration than emmc partitions need to set active partition if you will not set active partition the phone will boot looping or hang on logo and make restarts
Click to expand...
Click to collapse
do you think any problem with this file system (Mi update team is not that dumb) but simply asking
in my case it restarts with boot loops , auto formates it self if you connect charging wire (with erasing mentioned for 15seconds) and fails to restar for 3 time and bootups with welcome language selection screen!
Ended up here because my Mi A3 is becoming increasingly unstable. It rebooted three times around lunch time. I've just installed the May 2020 update and it's already restarted once already
I'm going to have to consider returning it - my mobile is my main business phone too so can't have this level of instability and hassle Sadly a very black mark against Xiaomi. I've recommended their phones to several friends and clients because they were great phones.
Hmm... whilst typing this message it's just restarted again...