Related
Hi all, hoping to get some advice in regards to a brick wall I've hit.
So background, my Galaxy S4 (i9505 running 4.2.2) has had ongoing USB recognition issues and thus I haven't been able to upgrade to a custom rom for a while. After following a couple of very detailed and useful guides on here, without success I had decided that it was likely one of two things:
A hardware problem (I have a third party charging port installed after the OEM stopped working)
Or when I was playing around with settings I derped and uninstalled the MTP application or some related core service.
So I left it for a while but today I decided to do something about it and discovered Mobile Odin (4.20), bought it and clean flashed SlimKat 4.4.4 (http%www%slimroms%net/index.php/downloads/dlsearch/viewcategory/1182-jflte). Took a while but the rom booted, really liked the look and I tried to install 3rd party apps and set up phone as usual but noticed that Google Play Store was missing. Manually installed V4.9 but it kept opening and closing so I uninstalled and the flashed the normal gapps and the AIO gapps through Mobile Odin (with and without clear cache), both processed OK but upon reboot none of apps ever installed.
So I decided to re-flash the SlimKat, I had to re download as I performed a factory restore in amongst things and had the original rom stored on internal. When I flashed inject root was checked as were all the other default options but upon reboot Mobile Odin is giving me "Could not detect device model" which after looking around basically means I lost root .
So my questions are: Without connecting via USB (because it's still not working) what are my options for flashing another rom or regaining root? Is there a way to get to stock 4.4.4 without USB?
Really appreciate any advice, currently the phone has network service and WiFi so in the mean time, without Google Play store it is just a significant inconvenience, but still operational.
Regards,
Marc
#Update
I don't know how but my root has been restored while I was playing around clearing app cache's etc. So now I have SlimKat 4.4.4 but unfortunately still no Google services/Store etc. When I manually install it, it has this issue where it automatically opens and then closes, so still working on fixing that. Again appreciate any input.
Hello, I've been flashing ROMs for a while now and I can't think of a way to regain root from within the ROM itself. How did you get root on your device in the first place to install mobile odin?
I have never used a play store application for any type of flashing, was never sure if it would be reliable or not. That being said, have you installed a custom recovery into your phone whilst you were playing around with it? If you did then you can fix this without fixing your USB connection.
However if you still have stock recovery, you probably need a USB connection to regain root. If that is the case, what have you actually tried to fix the USB problem?
lichking21st said:
Hello, I've been flashing ROMs for a while now and I can't think of a way to regain root from within the ROM itself. How did you get root on your device in the first place to install mobile odin?
I have never used a play store application for any type of flashing, was never sure if it would be reliable or not. That being said, have you installed a custom recovery into your phone whilst you were playing around with it? If you did then you can fix this without fixing your USB connection.
However if you still have stock recovery, you probably need a USB connection to regain root. If that is the case, what have you actually tried to fix the USB problem?
Click to expand...
Click to collapse
Hey @lichking21st. Mobile Odin is allegedly just odin without the need for USB. I have tried to fix the USB to no avail
Actually just about to update my original post, I don't know how but my root has been restored while I was playing around clearing app cache's etc. So now I have SlimKat but unfortunately still no Google services/Store etc. When I manually install it, it has this issue where it automatically opens and then closes, so still working on fixing that. Again appreciate any input.
Problems solved!
Clean flashed stock rom then clean flashed back to SlimKat. Google play and root carried over.
USB still not working have to put it down to a hardware issue now. Oh well, so happy
@MOD you can close this. Thanks again for the help LichKing
grinchenator said:
Problems solved!
Clean flashed stock rom then clean flashed back to SlimKat. Google play and root carried over.
USB still not working have to put it down to a hardware issue now. Oh well, so happy
@MOD you can close this. Thanks again for the help LichKing
Click to expand...
Click to collapse
Glad to see your problem is fixed, I would still advise you to get a custom recovery so you have some options if you really get stuck without root for next time. I recommend using TWRP but CWM works too.
Hi,
in my spare free time I compiled a new unofficial LineageOS 14.1 ROM on my beloved Phenom II system with ECC RAM and made it available to you for 90 days from
https://www.filefactory.com/file/5fqmz223n9gx/lineage-14.1-20170403-UNOFFICIAL-SonyLOS-kugo.zip
https://www.filefactory.com/file/121p40o8v8gb/lineage-14.1-20170403-UNOFFICIAL-SonyLOS-kugo.zip.md5sum
The ROM can be installed through a recovery like TWRP. I also applied some modifications, in particular:
- the SonyLOS kernel has been replaced with the Sony AOSP version which seemed to be more up to date
- using some 7.1 binaries of Sony AOSP instead of the 7.0 binaries used earlier enabling some more features (?)
- replaced the LineageOS camera with the Simple Camera app
- integrated Total Commander, Apollo music player v2, SELinux permission changer and Viper4Android apps since I need them
Consequently,
- patchlevel now is March 5th, 2017
- the fingerprint sensor now seems to be usable to unlock your device
- the FM radio works (however, you have to manually scan through the stations once because automatically finding the stations initially still does not seem to work completely)
- the selfie camera image no longer will be upside down (seemed to be an issue with the LineageOS camera app, also will work correctly with i.e. Focal if you prefer a sophisticated app instead of Simple Camera)
- I can now use Apollo again as I did on the Z1 compact with CM 12
- the bass boost and equalizer are back with Viper, you just need to invoke the SELinux changer on the rooted device and install the drivers initially through Viper itself
Thanks fly out to Sony AOSP, SonyLOS and the app providers. Feedback is also very welcome.
Regards,
jtk_de
@admin: Could we please move this thread and my previous one to the ROM section ? I'm still not allowed to post something there
Great to see you're still updating your ROM. Don't understand why you upload at filefactory (sloooow download) instead of androidfilehost for example. Will flash your ROM tomorrow.
- should I flash a stock ROM first or does it not matter which version I'm coming from
- what do I need the .md5sum file for?
- gapps are not included, right?
I tried to use androidfilehost but my uploads got interrupted so I had to stick with filefactory for now. You don't need to flash the stock ROM first, just wipe the system, cache etc. partitions in your recovery and flash the .zip.
The md5sum checksum file is there to ensure the ROM integrity and is not needed for the flash, however, TWRP optionally can read it and veryify that the ROM has been correctly downloaded and copied to your phone's storage. Gapps is not included since I use alternative apps, hence it must be installed separately.
Root access is integrated already and can be controlled via the developer settings. The only issue I experienced so far is that the volume cannot be altered yet during phone calls
I don't get viper4android to work. I install the drivers, reboot my device and then viper4android prompts me to install the drivers again. Am I doing something wrong?
Micka84 said:
I don't get viper4android to work. I install the drivers, reboot my device and then viper4android prompts me to install the drivers again. Am I doing something wrong?
Click to expand...
Click to collapse
You need to enable root first and start the SELinuxModeChanger installed with the ROM and set SELinux to "Permissive". Then the Viper drivers can be installed which can take quite long (a minute or so). If an Android dialog pops up because of this confirm that you would like to wait longer. Then reboot as indicated and enjoy the bass
That worked for me thank you
Hey,
many thanks for that ROM. Unfortunately i end up in a never ending boot animation. If i get in recovery (TWRP) and tell him to reboot, it tells me that no OS is installed. Any hints how this can be solved?
Thanks for any advice!
dreadavi said:
Hey,
many thanks for that ROM. Unfortunately i end up in a never ending boot animation. If i get in recovery (TWRP) and tell him to reboot, it tells me that no OS is installed. Any hints how this can be solved?
Thanks for any advice!
Click to expand...
Click to collapse
Hi!
I think there aren't any os on your device, thats wha twrp sad that... because, your systems encrypted. You could remove it. Try to flash again twrp from fastboot, than clear cache ( fastboot format cache ) and userdata ( fastboot format userdata ) from flashtools too. After that boot to twrp, than you could mount system, than flash the whole cm rom again. After that, i think it will boot correctly.
lba810701 said:
Hi!
I think there aren't any os on your device, thats wha twrp sad that... because, your systems encrypted. You could remove it. Try to flash again twrp from fastboot, than clear cache ( fastboot format cache ) and userdata ( fastboot format userdata ) from flashtools too. After that boot to twrp, than you could mount system, than flash the whole cm rom again. After that, i think it will boot correctly.
Click to expand...
Click to collapse
Thanks for the hint. Did what you said, but i cant mount system in recovery. It cant be selected in the list. Any other suggestions? Ok solved it. had to flash stock rom and boot.img before the steps you asked me to try. Thank you!
Thank you for putting this ROM together! There are the following problems on the OmniROM:
1. Incall speaker volume is not controllable
2. Slight incall echo on receiving side
3. Double tap to wake doesn't work
Is this still the case for your Lineage ROM?
avion540 said:
Thank you for putting this ROM together! There are the following problems on the OmniROM:
1. Incall speaker volume is not controllable
2. Slight incall echo on receiving side
3. Double tap to wake doesn't work
Is this still the case for your Lineage ROM?
Click to expand...
Click to collapse
1. Yes, the volume can't be changed during phonecalls
2. Didn't notice any echos so far
3. True
Could you try uploading to mega.nz? FileFactory is so slow
minimum Brightness
Hey!
i was just wondering if its possible to lower the minimal brightness a bit more. because minimal brightness is quite bright still. Im using this ROM for a few days now. Everything works pretty fine, but the battery life is a bit short for what i was expecting. If i dont use extreme battery saving mode its always around 24 hours. i barely do phone calls and i use it not very intensively... Highest Consumer is standby with 5%, which i think is wierd, isn´t it?
:good: Kudos. Everything seems to work well aside from the Bluetooth Audio cutting out after a few minutes. Overall I am really happy with it - happy enough that it's my daily driver.
Hi!
ROM will be better and better. Thanks.
Battery charging speed a bit slow, and if I'm using a mobil net, it's draining a little fast, plus in the evening, with wifi on, it goes down nearly 5%>. Camera is good. But, im using open cam software from google play. Fingerprint sensor working good, just a little hard to configure it. I'm using substratum theme engine, and i can theme most of the base and google apps. ( Except fingerprint sensor, with themed settings, the fingerprint setup screen cracked... but inthinknits theme problem ) And about bluethooth.. yes, it's dropping the connection after a few secs. But, if you left it, then reconnect automatically and just after that, it goes good. Until you turn it off. I used a sony sbh70 wireless headset with power amp.
And echo sound in calling. I can't hear echo, but other peoples in line, they sad it. They hear onselfs twice.. :/
If you would like it, maybe i can upload a logfile ( with matlog ) about the bluethooth problem.
Anyway, thanks foe thiese rom for our x compact.
It's good to see some other people are using the ROM and testing things that I can't test
According to my own experience battery lifetime is around 2-3 days when surfing via wi-fi, listening to music and calling from time to time. Battery charging with the Sony AC adapter coming with the phone is quite quick compared to the Z1C although the battery capacity is higher.
If I make another build I'll upload it to some faster provider though.
hello all,
give it some news there? Last entry April 2017.....
Hi all, are there some updates? I love Lineage OS
I'm wondering why there isn't an official build for the Xperia X Compact yet ? If I google "kugo lineageos" I get a hit for a stats page:
https://stats.lineageos.org/model/kugo
Which just says the page isn't rendered yet, but obviously someone has been devoting his/her time to the kugo. What could be the hold up? Same goes for the lack of other roms btw. It seems Sony is quite open towards the community but somehow this hasn't resulted in the overwhelming amount of roms I was hoping for ... It's quite underwhelming in fact. Could it be not enough (knowledgable) people own an Xperia X Compact ?
harryharryharry said:
It seems Sony is quite open towards the community but somehow this hasn't resulted in the overwhelming amount of roms I was hoping for ... It's quite underwhelming in fact. Could it be not enough (knowledgable) people own an Xperia X Compact ?
Click to expand...
Click to collapse
Sony gives us a sliver of what is needed for AOSP to run, camera, bluetooth, wifi, and radio band stuff all has to be manually made to work. The z3 line was the ONLY xperia line to ever get mainstream AOSP support from devs. If you bought your xperia thinking Sony's AOSP program was good you were sadly mistaken.
after booting deadman twrp 3.1.1 on los 16.1, touch of my phone is not working, even in twrp..
afte that I flash stock oreo via MI flash tool.. but no result, same problem, touch wrong.. like mad, ,
any fix there >???
please some one help me... plz
I think you should select clean flash again while flashing rom through mi flash tool!
Facing same problem, clean flash did not help. Please reply.
I had the same problem with a new Mi A1. After installing twrp and flashing LineageOS the touch screen didn't work correctly. When touching it, sometimes it would respond in the wrong spot. Most touches were unresponsive. Booting back to twrp had the same problem. When I flashed stock Oreo with MiFlash it still was broken.
I managed to fix it doing the following (files available on androidfilehost from a user named edwaine):
1. Download MiFlash2017-7-20-0.zip which seems to be the latest version
2. Download the latest official Nougat ROM (not Oreo)
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
3. Put the phone in fastboot mode by holding power + volume down
4. Did a "clean all and lock" with MiFlash 2017.7.20.0
After this my phone booted to a black screen for a few minutes and then showed the initial setup with a working touch screen. I believe the initial problem was caused by not properly upgrading to Oreo. I didn't even check the stock firmware when it arrived, because I didn't think there were any issues just flashing newer firmware. I will now try to upgrade properly.
I hope this helps someone.
Bro, how about upgrade to Oreo? Is the touch still fixed?
Fewome said:
I had the same problem with a new Mi A1. After installing twrp and flashing LineageOS the touch screen didn't work correctly. When touching it, sometimes it would respond in the wrong spot. Most touches were unresponsive. Booting back to twrp had the same problem. When I flashed stock Oreo with MiFlash it still was broken.
I managed to fix it doing the following (files available on androidfilehost from a user named edwaine):
1. Download MiFlash2017-7-20-0.zip which seems to be the latest version
2. Download the latest official Nougat ROM (not Oreo)
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
3. Put the phone in fastboot mode by holding power + volume down
4. Did a "clean all and lock" with MiFlash 2017.7.20.0
After this my phone booted to a black screen for a few minutes and then showed the initial setup with a working touch screen. I believe the initial problem was caused by not properly upgrading to Oreo. I didn't even check the stock firmware when it arrived, because I didn't think there were any issues just flashing newer firmware. I will now try to upgrade properly.
I hope this helps someone.
Click to expand...
Click to collapse
Faced the same problem. I played with the firmware and stopped working the touchscreen. This tip rolled back to 7.1,2 helped. The phone began to work.
I updated it after the initial configuration and connection to the network, the phone itself downloaded the update and installed it. Updated to 8.1.0.
Thank you so much for sharing!
Hi, touch, fingerprint and capacitive buttons stopped working after I installed Pixel experience ROM, I rolled back to 7.1.2 using Mi flash tool according to your suggestion (same versions of Miflash and ROM as suggested by you). Still the problem isnt solved, please help.
meet4300 said:
Hi, touch, fingerprint and capacitive buttons stopped working after I installed Pixel experience ROM, I rolled back to 7.1.2 using Mi flash tool according to your suggestion (same versions of Miflash and ROM as suggested by you). Still the problem isnt solved, please help.
Click to expand...
Click to collapse
same problem how did you solved it ?
As my phone was in warranty, I was able to get it solved by replacing motherboard. Booting older versions of TWRP can get the touch working, this is suggestion is still to be tested. Try your luck if you can sort it out. In Pixel experience rom, there is an option of double tap to wake. I think thats the reason this fuss is all about. I think due to a different manufacturer, maybe our screens won't support it.
For those who still did not get touch working after installing stock nougat just unlock bootloader and boot twrp 3.2.1 (strictly never flash it...just hot boot it..... it's the reason ur touch got malfunctioning...)and reboot voila!...ur touch is restored
I still can't seem to get it to work.
Tried nougat and two oreo version but the issue remains.
The touchscreen does work after I boot the device but does not work after it wennt to sleep/lock screen.
The screen does also not work inside twrp
i also tried to install a custom rom via adb shell and twrp but the zip fails (9.0 and lineage)
I hope someone could help me
diocore said:
I still can't seem to get it to work.
Tried nougat and two oreo version but the issue remains.
The touchscreen does work after I boot the device but does not work after it wennt to sleep/lock screen.
The screen does also not work inside twrp
i also tried to install a custom rom via adb shell and twrp but the zip fails (9.0 and lineage)
I hope someone could help me
Click to expand...
Click to collapse
Disable DT2W and voila, fixed.
I don't know what the problem is, but I know how to "fix" it.
diocore said:
I still can't seem to get it to work.
Tried nougat and two oreo version but the issue remains.
The touchscreen does work after I boot the device but does not work after it wennt to sleep/lock screen.
The screen does also not work inside twrp
i also tried to install a custom rom via adb shell and twrp but the zip fails (9.0 and lineage)
I hope someone could help me
Click to expand...
Click to collapse
Same problem. Did you make any progress?
leodoct said:
Same problem. Did you make any progress?
Click to expand...
Click to collapse
I'm in trouble too. Tried Nougat, but didn't work. Any other ideas?
Edit: now I can't reflash anything from Nougat. It just says "Device is locked"
mikla90 said:
I'm in trouble too. Tried Nougat, but didn't work. Any other ideas?
Edit: now I can't reflash anything from Nougat. It just says "Device is locked"
Click to expand...
Click to collapse
Well i found a solution for my case. The problem for me was the version of platform tools i used to lock-unlock boot-loader, boot the system and running any commands install HAL3 etc..
Every installation i did (firmwares, from nougat to oreo and last to pie) was executed with the platform tools latest windows version that boot.img had (14,888KB) size.
The version that my touch screen began to work again is the platform tools r.28.0.1.windows that had the boot.img (34,928KB) size.
When i booted the phone in fastboot mode, i opened platform tools r.28.0.1.windows and run the command "fastboot boot boot.img" the phone rebooted and the touch was working again I think that the boot.img file of this version is the correct to boot the phone normally.
Hope this helps....
fewome said:
i had the same problem with a new mi a1. After installing twrp and flashing lineageos the touch screen didn't work correctly. When touching it, sometimes it would respond in the wrong spot. Most touches were unresponsive. Booting back to twrp had the same problem. When i flashed stock oreo with miflash it still was broken.
I managed to fix it doing the following (files available on androidfilehost from a user named edwaine):
1. Download miflash2017-7-20-0.zip which seems to be the latest version
2. Download the latest official nougat rom (not oreo)
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
3. Put the phone in fastboot mode by holding power + volume down
4. Did a "clean all and lock" with miflash 2017.7.20.0
after this my phone booted to a black screen for a few minutes and then showed the initial setup with a working touch screen. I believe the initial problem was caused by not properly upgrading to oreo. I didn't even check the stock firmware when it arrived, because i didn't think there were any issues just flashing newer firmware. I will now try to upgrade properly.
I hope this helps someone.
Click to expand...
Click to collapse
thank you sooooo much dude u saved my ********ing assssss!
ash roxx said:
For those who still did not get touch working after installing stock nougat just unlock bootloader and boot twrp 3.2.1 (strictly never flash it...just hot boot it..... it's the reason ur touch got malfunctioning...)and reboot voila!...ur touch is restored
Click to expand...
Click to collapse
Thank You .. You are a lifesaver
:good:
Mi A1 touch responds somewhere on screen
Fewome said:
I had the same problem with a new Mi A1. After installing twrp and flashing LineageOS the touch screen didn't work correctly. When touching it, sometimes it would respond in the wrong spot. Most touches were unresponsive. Booting back to twrp had the same problem. When I flashed stock Oreo with MiFlash it still was broken.
I managed to fix it doing the following (files available on androidfilehost from a user named edwaine):
1. Download MiFlash2017-7-20-0.zip which seems to be the latest version
2. Download the latest official Nougat ROM (not Oreo)
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
3. Put the phone in fastboot mode by holding power + volume down
4. Did a "clean all and lock" with MiFlash 2017.7.20.0
After this my phone booted to a black screen for a few minutes and then showed the initial setup with a working touch screen. I believe the initial problem was caused by not properly upgrading to Oreo. I didn't even check the stock firmware when it arrived, because I didn't think there were any issues just flashing newer firmware. I will now try to upgrade properly.
I hope this helps someone.
Click to expand...
Click to collapse
packpunk said:
Bro, how about upgrade to Oreo? Is the touch still fixed?
Click to expand...
Click to collapse
Please let me know if someone have solution. PLZ PLZ PLZ
I flashed latest rom pie/ oreo/naughut...but no luck.
I also hotboot recovery start but still touch lagging.
Plesae let me know if there is any solution.
Dear Xda Members I have Problem with my MI A1
I downgrade it to 7.1
Aflter Flashing clean all and relock its with MI flasher tool, My touch Screen misbehave, I try nought and oreo firmware (above mentions also) but problem cant solve
Please help me
Thanks
[if you install this firmware and make clean and relock so you need to unlock bootloader for OTA update]
Thanks You very much Dear your solution is working well.
I downgrade my cell for some reson from pie, when I clean Install and relock I face touch problem, I try manay official firmware but all wrost,
Then I try your shearing mathod, LOL WoW Its worked, I install this firmware then OTA 8.1 and then OTA 9.0 and then AOSP Ex on my cell now its worked fine!
Fewome said:
I had the same problem with a new Mi A1. After installing twrp and flashing LineageOS the touch screen didn't work correctly. When touching it, sometimes it would respond in the wrong spot. Most touches were unresponsive. Booting back to twrp had the same problem. When I flashed stock Oreo with MiFlash it still was broken.
I managed to fix it doing the following (files available on androidfilehost from a user named edwaine):
1. Download MiFlash2017-7-20-0.zip which seems to be the latest version
2. Download the latest official Nougat ROM (not Oreo)
tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz
3. Put the phone in fastboot mode by holding power + volume down
4. Did a "clean all and lock" with MiFlash 2017.7.20.0
After this my phone booted to a black screen for a few minutes and then showed the initial setup with a working touch screen. I believe the initial problem was caused by not properly upgrading to Oreo. I didn't even check the stock firmware when it arrived, because I didn't think there were any issues just flashing newer firmware. I will now try to upgrade properly.
I hope this helps someone.
Click to expand...
Click to collapse
I have an SM-N900V (Note 3, Verizon variant, hltevzw).
Detailed timeline:
- I flashed it back to firmware OB6 using Odin 3.09.
- I rooted it using ArabicToolApp.
- I used this tool to unlock the bootloader
- I installed a build of LineageOS 14.1 for hlte
- It didn't recognize the SIM so I did a dirty flash of this build of LineageOS 15.1 for hltetmo on top (hltetmo actually has different hardware than hlte, and the correct one for SM-N900V)
- Messed around with the APNs until it recognized and connected to Verizon's network. I DO have functioning SMS and LTE data, but I have not tested phone calls yet
- Messed around some with SuperSU in system- and systemless-mode. Bricked my device more times than I could count, then unbricked over and over using SuperSU's impeccable installer. Messed around with this quite a bit
- Also messed around with Xposed some. The OS is too unstable to run Xposed Installer correctly, so I uninstalled it
- Removed SuperSU, installed Magisk. Phone now passes SafetyNet
So, my phone now runs 8.1 and a Lineage build from 9 days ago. Cool. But, if I was satisfied I wouldn't be making this post. There are multiple instances of the same kind of "app freeze" - App screen freezes, sometimes it'll go completely black. Interactivity doesn't work, obviously, the app is completely frozen. Hold Back to kill doesn't work (Application Killed toast shows, but nothing happens). ANR (when it comes up) Close doesn't work. Home button works and brings me away from the app, but it's still there. Swipe away in Overview doesn't actually kill the app. Even in App Info, Force Stop doesn't work. The app is forever frozen. Tapping the icon from the launcher no longer does anything, it doesn't even bring up the app. The app is permanently crashed and inaccessible until a reboot.
Issues:
- Sometimes when booting the phone will not recognize the SIM until a reboot. As in, "No SIM" message and everything
- Sometimes it will get stuck at boot, I have foxy-boot installed, so I can see the logs. I don't remember what it was all about, if it comes up again I'll update the post
- Google Chrome sometimes crashes when trying to download a file. I've gotten my phone to self-host before, but this issue always seems to come back, and when it does Google Chrome ALWAYS crashes when trying to download a file. App Freeze
- Netflix installs and logs in but freezes at the "can't connect to service (-9)" message. App Freeze
- Certain apps like NativeScript Playground get stuck at the splash screen. App Freeze
- Xposed Installer did this when opening the Settings, whether Xposed was installed or not. App Freeze
- F-Droid also sometimes crashes, although it's somewhat arbitrary, I can't reproduce it reliably. App Freeze
I have tried reflashing the ROM, flashing Xposed uninstaller, reinstalling Magisk, none of it seems to work. I have TWRP 3.3.0 so I can do pretty much anything that doesn't involve the SD card (the SD card is probably broken in hardware, it's so read-only that Android and TWRP both can't write to it at all, but they can both read the same half-broken filesystem).
I fear that this OS is just too unstable for the phone and there's nothing I can do. I sincerely hope this is not the case.
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
terminator911 said:
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
Click to expand...
Click to collapse
I did a clean installation of RR 6.0.0 (Android 8.1) and it works a lot better than LineageOS did, with even more configuration options. I really really hate Pie and its gesture-based gimmicks (Screw you Google for copying more of Apple's bad design decisions), so I assumed Oreo would be more stable, but the ROM I installed still has crashing apps. Google Chrome still won't download most things (I've gotten it to download before), trying to change the accent color crashes the 'LineageOS Settings' app, and F-Droid is seriously messed up, but most other things are stable, including the Verizon network which required no pesky APN setup.
I'm on the OB6 bootloader/modem, is that a problem? I doubt that would be an issue, but I can always back up and reflash via Odin. The cool thing is that I installed a patch to TWRP which backs up /data/media along with everything else, after installing the custom ROM. So, really, I can do anything and be perfectly fine. There's, AFAIK, no way to ruin the phone unless something exploits the eMMC brick bug.
If there's another ROM you'd recommend me install, I'd be happy to try it out. I would really like to have a stable OS on here, where Chrome will work and download files. I'd also love Camera2 API since the phone has the chip for it (Snapdragon 800), but none of the ROMs I have support it and there's been no discussion online other than some years-old threads with no answers. I know there have been some articles online listing Note 3 as a phone that'd support Camera2 API with a software update. Would updating the bootloader/modem do anything on that front?
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
terminator911 said:
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
Click to expand...
Click to collapse
Excuse me but custom ROMs don't have "the Samsung Internet browser". Additionally the modem shouldn't cause app crashes (if it does, correct me please).
I might try the Nougat ROM. Bluetooth calls don't matter to me, but stability does. I just kinda really like Oreo and all its customization options but it may be too new for this old phone from 2013. It still works as a phone though, Messages and phone calls work fine, so I may just deal with it.
I use Open Camera, and I've tried multiple Camera2 API enablers. The phone has a Qualcomm Snapdragon 800 and the necessary links (in hardware, between the camera/other things) to support Camera2, but nobody seems to have tried it. Probably because the Verizon Note 3 is really locked down, and can only be rooted on a special version of the samsung ROM, and can only be bootloader-unlocked via the eMMC brick bug... There are Magisk modules for Camera2 on Exynos-based devices, but none for the Verizon Note 3 AFAIK.
I just found out that RR 7 officially supports `hltetmo`, but RR 6 doesn't. That's kinda sad, I hate Pie, but I might try it...
I've had the SEPL stuff before, that's the one that can't be rooted. I suppose I didn't consider upgrading again after I unlocked my bootloader. I'll try SEPL1 firmware again, but with a custom ROM...
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
terminator911 said:
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
Click to expand...
Click to collapse
Yeah but, data and calling worked fine on the LineageOS and RR roms, so there's no reason to update the modem.
Besides, I flashed SEPL1 6 times using Odin (multiple times by flashing, rebooting directly into download mode and flashing it once more) and it doesn't want to update. Still on OB6. On the latest (official Pie) RR rom, data worked on first boot but doesn't work anymore (I'm going to mess around with the data settings until it works), but I have no reason to believe that my phone needs a modem update to function.
I did, many times, make calls to various phone numbers and they all worked flawlessly. SEPL1 is therefore not needed if that's all it does.
And I do know about all the Resurrection Remix versions: One is Nougat from their archive, one is the Oreo version I had installed just yesterday before flashing Pie, and the other one is Pie which is now officially supported.
I am currently working on getting RR7 to work, it's only crashed a few times, and I don't even remember what those times were (I think it was using the Back button in Overview/Recents at the same time as the Overview button?)
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
terminator911 said:
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
Click to expand...
Click to collapse
"pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot"
So...
- Reboot phone into Download mode
- Pull battery while in Download mode
- Flash thingy
- Reboot back into Download mode
- Flash thingy again
? That will be very difficult to do with my dodgy charging cable that doesn't like being repositioned...
I do that without pulling the battery, but I could try it with.
I'm downloading the full SEPL stock image to flash. Once that's done, I'll flash it, reflash TWRP, restore my backup, and see if the baseband has updated.
And no, never dirty flashed the ROM. Always completely wiped data, system, cache and everything. I always backup first. I currently have 3 backups: Lineage OS (before installing RR), RR6 (Oreo), and RR7 (right now before that stock image I'm going to flash).
My external SD card is nonfunctional and read-only with some trash files from the previous phone.
I flashed the stock SEPL ROM. Baseband still didn't change. Restored from backup, SIM now works. Network is detected, SMS and data both work reliably on all reboots.
I will mention that I did brick my phone by using Odin to erase the eMMC, but I fixed that from TWRP, and now everything works flawlessly. There are still some app crashes, but most things are very stable. Camera2 API still nonexistent, which is sad because I got used to it on my old phone, but I shouldn't hope for it.
Hi,
I have strange problem, used 9T come to me with wiped system (factory reset) but when MIUI loaded system i have notification "Android setup isn't responding". I can't accept it or anythink, configuration screen isn't loaded only black screen with status bar and navigation buttons. I can go to settings by the notifiaction bar, but after 10 seconds phone freezing and rebooting by itself.
I flash new system without errors, but it wont fix the problem
I had the same problem, I spent all the roms and the only one that worked was davinci_global_images_V10.3.5.0.PFJMIXM_20190528.0000.00_9.0_global_4222a49ff1
good that the phone is working again but now i'm facing other problems because i can't update the phone otherwise it goes back to loop and with this rom no sensor is working as a presence sensor, gyroscope and also problems with the front camera that is not it is working correctly.
crt-shadow said:
Hi,
I have strange problem, used 9T come to me with wiped system (factory reset) but when MIUI loaded system i have notification "Android setup isn't responding". I can't accept it or anythink, configuration screen isn't loaded only black screen with status bar and navigation buttons. I can go to settings by the notifiaction bar, but after 10 seconds phone freezing and rebooting by itself.
I flash new system without errors, but it wont fix the problem
Click to expand...
Click to collapse
crt-shadow said:
Hi,
I have strange problem, used 9T come to me with wiped system (factory reset) but when MIUI loaded system i have notification "Android setup isn't responding". I can't accept it or anythink, configuration screen isn't loaded only black screen with status bar and navigation buttons. I can go to settings by the notifiaction bar, but after 10 seconds phone freezing and rebooting by itself.
I flash new system without errors, but it wont fix the problem
Click to expand...
Click to collapse
i have the same problem do you have the solution right now? :<
Same problem here. I also can't turn on the wifi and sim cards aren't detected
crt-shadow said:
Hi,
I have strange problem, used 9T come to me with wiped system (factory reset) but when MIUI loaded system i have notification "Android setup isn't responding". I can't accept it or anythink, configuration screen isn't loaded only black screen with status bar and navigation buttons. I can go to settings by the notifiaction bar, but after 10 seconds phone freezing and rebooting by itself.
I flash new system without errors, but it wont fix the problem
Click to expand...
Click to collapse
same here, keep rebooting, u solved it?
Factory reset does not mean to Wipe System but Data.
Gyroscope and other sensors not working are the result of wiping Persist, Vendor and other partitions
Proper procedure to switch the ROM/install custom ROM requires:
- Format Data (option in TWRP, exactly as that "Format Data")
- Wipe Cache
- Do not Wipe any other partition !!!!!!!
- Flash your custom ROM
Unfortunately, there are noobs who don't know/understand, and they Wipe System, Vendor, Persist and who knows what other partitions they think off.
The result is the phone behaving as described
To recover, try flashing the TGZ stock ROM from Mi Flash (not just the ZIP ROM from TWRP).
Anyway, if Persist was wiped, you will never, ever recover DRM L1
zgfg said:
Factory reset does not mean to Wipe System but Data.
Gyroscope and other sensors not working are the result of wiping Persist, Vendor and other partitions
Proper procedure to switch the ROM/install custom ROM requires:
- Format Data (option in TWRP, exactly as that "Format Data")
- Wipe Cache
- Do not Wipe any other partition !!!!!!!
- Flash your custom ROM
Unfortunately, there are noobs who don't know/understand, and they Wipe System, Vendor, Persist and who knows what other partitions they think off.
The result is the phone behaving as described
To recover, try flashing the TGZ stock ROM from Mi Flash (not just the ZIP ROM from TWRP).
Anyway, if Persist was wiped, you will never, ever recover DRM L1
Click to expand...
Click to collapse
The same problem remains even after your method.
pranav1201 said:
The same problem remains even after your method.
Click to expand...
Click to collapse
What exact problem, with which ROM, what did you previously do with the phone?
Hello @zgfg
I'm having the same error as the OP with my Mi 8 (dipper).
I done goofed up, as I had the official 12.0.3.0 stock ROM installed, and then I wanted to go with the 12.5.2.0 EU ROM. I installed it no problem, but then in my infinite wisdom I tried to lock the bootloader via fastboot while having the EU ROM installed. Everything went to hell after that.
After that, I cannot make the phone work properly regardless of the ROM I try to install. With MIUI (both stock and EU), I cannot get the WiFi to work properly (Ino networks are shown), and the "Android Setup isn't responding" error does not let me finish the setup of the device. I also tried lineage, where I also cannot find any networks, so the setup pretty much stops there.
It is obvious I effed up something with lower-level files, I definitely just erased everything from TWRP at one point when I was panicing.
I tried flashing the stock ROM using Mi Flash as you said, but it did not work. Can you provide me a way of checking what is going wrong or a general way to fix this?
Fjolfrin said:
Hello @zgfg
I'm having the same error as the OP with my Mi 8 (dipper).
I done goofed up, as I had the official 12.0.3.0 stock ROM installed, and then I wanted to go with the 12.5.2.0 EU ROM. I installed it no problem, but then in my infinite wisdom I tried to lock the bootloader via fastboot while having the EU ROM installed. Everything went to hell after that.
After that, I cannot make the phone work properly regardless of the ROM I try to install. With MIUI (both stock and EU), I cannot get the WiFi to work properly (Ino networks are shown), and the "Android Setup isn't responding" error does not let me finish the setup of the device. I also tried lineage, where I also cannot find any networks, so the setup pretty much stops there.
It is obvious I effed up something with lower-level files, I definitely just erased everything from TWRP at one point when I was panicing.
I tried flashing the stock ROM using Mi Flash as you said, but it did not work. Can you provide me a way of checking what is going wrong or a general way to fix this?
Click to expand...
Click to collapse
Sorry, I would never go to relock BL while having the custom ROM (I thought it would instantly brick the phone)
Not sure could I help but I'm also curious:
- You relocked the Bootloader by fastboot oem lock or by fastboot flashing lock?
- It locked BL, did Factory reset but kept Xiaomi.eu ROM?
- After that you unlocked BL again (otherwise how would you continue flashing the other ROMs)?
- Did you then unlock BL by Mi Unlock tool or by fastboot flashing unlock?
- Did you then you flash Fastboot/tgz version of the stock MIUI?
And with that the phone does not work properly (network, etc)?
- What version of MIUI you flash, MIUI 12.1 (Global, EEA)?
- Did you try with CN 12.5.2.0, Fastboot/TGZ version (closest Fastboot MIUI version to your previous Xiaomi.eu)?
Un-gzip, unutar, find inside bat scripts (I think 3 of them) choose one that makes Factory reset but does not relock BL.
Edit the script to remove first 3-4 lines that check against downgrading (not having the script in front of me to tell you exactly but you will see when you open the script), and run the bat from Fastboot
zgfg said:
Sorry, I would never go to relock BL while having the custom ROM (I thought it would instantly brick the phone)
Not sure I could help but I'm also curious:
- You relocked the Bootloader by fastboot oem lock or by fastboot flashing lock?
- It locked BL, Factory reset but kept Xiaomi.eu ROM?
- After that you unlocked BL again (otherwise how would you flash the other ROMs)?
- You unlocked BL by Mi Unlock tool or by fastboot flashing unlock?
- Then you flashed Fastboot/tgz version of the stock MIUI?
And with that the phone does not work properly (network, etc)?
- What version of MIUI you tried to flash, MIUI 12.1 (Global, EEA)?
-Did you try with CN 12.5.2.0, Fastboot/TGZ version?
Un-gzip, unutar, find inside bat scripts (I think 3 of them) choose one that makes Factory reset but does not relock BL.
Edit the script to remove first 3-4 lines that check against downgrading (not having the script in front of me to tell you exactly but you will see when you open the script)
Click to expand...
Click to collapse
Thanks for the reply! Here we go:
1. By fastboot oem unlock.
2. I am not sure I remember. I think it could not boot at all.
3. Yes I unlocked it.
4. I have always used the Mi unlock tool to unlock the bootloader.
5. Yes I flashed it this way and it did not work. To be precise, I completely extracted the tgz, I opened Mi flash, selected the final extracted folder, and I flashed this way.
6. With Mi flash I have used the official rom, meaning 12.0.3.0 global (in case you did not read it, this is all for a Mi 8, I just found this thread and though to ask). When I install the EU rom, I use twrp.
7. No I haven’t tried Chinese roms, should I?
I have also tried directly running the bat scripts from the extracted folder as you said, but it didn’t work. Same thing.
Fjolfrin said:
Thanks for the reply! Here we go:
1. By fastboot oem unlock.
2. I am not sure I remember. I think it could not boot at all.
3. Yes I unlocked it.
4. I have always used the Mi unlock tool to unlock the bootloader.
5. Yes I flashed it this way and it did not work. To be precise, I completely extracted the tgz, I opened Mi flash, selected the final extracted folder, and I flashed this way.
6. With Mi flash I have used the official rom, meaning 12.0.3.0 global (in case you did not read it, this is all for a Mi 8, I just found this thread and though to ask). When I install the EU rom, I use twrp.
7. No I haven’t tried Chinese roms, should I?
I have also tried directly running the bat scripts from the extracted folder as you said, but it didn’t work. Same thing.
Click to expand...
Click to collapse
1) Should have been "lock", not "unlock"
7) If I understood correctly, you had Xiaomi.eu 12.5.2.
Hence I think you should try the closest MIUI version (Fastboot, not Recovery - Fastboot flashes more deeply), and that could only be CN 12.5.2 (Global, EEA are 12.0.3 for your device)
The best would be Fastboot version of Xiaomi.eu 12.5.2 but AFAIK, there is no such thing
Hence after the CN 12.5.2 try then (Recovery) Xiaomi.eu 12.5.2
zgfg said:
1) Should have been "lock", not "unlock"
7) If I understood correctly, you had Xiaomi.eu 12.5.2.
Hence I think you should try the closest MIUI version (Fastboot, not Recovery - Fastboot flashes more deeply), and that could only be CN 12.5.2 (Global, EEA are 12.0.3 for your device)
The best would be Fastboot version of Xiaomi.eu 12.5.2 but AFAIK, there is no such thing
Hence after the CN 12.5.2 try then (Recovery) Xiaomi.eu 12.5.2
Click to expand...
Click to collapse
1) Yeah lol, mistyped.
7) Ok! I’ll give it a try. I have an early wake tomorrow tho and I have already spent too much time for this, so it’ll be a while before I come back with news.
Thank you!
You can use MIUI Downloader:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
to easily locate the download link for eg your Fastboot CN 12.5.2 - screenshot
zgfg said:
You can use MIUI Downloader:
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
to easily locate the download link for eg your Fastboot CN 12.5.2 - screenshot
Click to expand...
Click to collapse
Good morning!
So I installed the china ROM (12.5.2.0 QEACNXM) using mi flash, and I'm having similar issues. I did not get the "android setup stopped working", however WiFi is still not responding as before, and I got two "Security stopped working" and "Settings stopped working" errors.
Edit: WiFi cannot actually be turned on at all.
Fjolfrin said:
Good morning!
So I installed the china ROM (12.5.2.0 QEACNXM) using mi flash, and I'm having similar issues. I did not get the "android setup stopped working", however WiFi is still not responding as before, and I got two "Security stopped working" and "Settings stopped working" errors.
Click to expand...
Click to collapse
Sorry, no other idea but that you try now again Xiaomi.eu 12.5, with Factory reset
zgfg said:
Sorry, no other idea but that you try now again Xiaomi.eu 12.5, with Factory reset
Click to expand...
Click to collapse
Got it, will try that, adn if it doesn't work I'll see whether I can do something else to fix this.
Anyway, thanks a lot!
Fjolfrin said:
Good morning!
So I installed the china ROM (12.5.2.0 QEACNXM) using mi flash, and I'm having similar issues. I did not get the "android setup stopped working", however WiFi is still not responding as before, and I got two "Security stopped working" and "Settings stopped working" errors.
Edit: WiFi cannot actually be turned on at all.
Click to expand...
Click to collapse
Btw, Bluetooth, NFC, GPS, do they work?
And first, not least, do SIM cards work (voice and mobile data)?
And did you try switching now from CN 12.5 back to Xiaomi.eu 12.5 (they are based on CN, but made to work internationally)
zgfg said:
Btw, Bluetooth, NFC, GPS, do they work?
And first, not least, do SIM cards work (voice and mobile data)?
And did you try switching now from CN 12.5 back to Xiaomi.eu 12.5 (they are based on CN, but made to work internationally)
Click to expand...
Click to collapse
I didn’t try these tbh, but I did go back to the 12.5 EU ROM.
This time I can get inside the phone normally, however Wi-Fi is still sketchy.
I managed to connect to a network, but manually, it still wont scan for network, and the connection is dropped after some minutes. I didn’t try gps, bt, or nfc, as I was trying to troubleshoot Wi-Fi, and this all came to a halt as the phone reboots on its own after 5-10 minutes of operation.