Related
Hi
I am in a dilemma guys.... my nexus 5 is fully updated to 4.4.2 and i got it from the retailer already updated to 4.4.2.
Now, the problem is that any apk e.g. youtube, maps etc. that require my location aint functioning at all.
YOUTUBE CANT EVEN SIGN ME IN DAMN IT!!!.....
Also when i click any clip to watch, it just keeps on loading for ever and never plays JACK!!!
I am so frustrated & i am sure others have the same problem.
Btw, i am right now, located in kuwait wich is a country in the middle east (for those who would like to know).
LTE is fully functional, supported & working just fine because i have the international variant.
On a side note: i rooted my device and installed cwm but the problem persisted from the initial device boot up.
Questions:
A: Could someone help me pls??
B: Would downgrading my 4.4.2 to 4.4 or flashing a custom rom fix the issue??
fixed the problem with cm11 but google now not working
grinzlo said:
Hi
I am in a dilemma guys.... my nexus 5 is fully updated to 4.4.2 and i got it from the retailer already updated to 4.4.2.
Now, the problem is that any apk e.g. youtube, maps etc. that require my location aint functioning at all.
YOUTUBE CANT EVEN SIGN ME IN DAMN IT!!!.....
Also when i click any clip to watch, it just keeps on loading for ever and never plays JACK!!!
I am so frustrated & i am sure others have the same problem.
Btw, i am right now, located in kuwait wich is a country in the middle east (for those who would like to know).
LTE is fully functional, supported & working just fine because i have the international variant.
On a side note: i rooted my device and installed cwm but the problem persisted from the initial device boot up.
Questions:
A: Could someone help me pls??
B: Would downgrading my 4.4.2 to 4.4 or flashing a custom rom fix the issue??
Click to expand...
Click to collapse
hey guys i managed to fix the problem by flashing cm11 but i cant get the google now to work with my voice..... is there something i can do to fix this ? my cm version is based on 4.4... should i wait for the stable 4.4.2 version?
Is google supported or allowed in your country? If location is disabled then you wont get those things.
Hi guys,
My girlfriend purchased a brand new Xperia Z3 D6653 not too long ago (about 2 months ago?). I flashed the 5.1.1 pre-rooted firmware for her and it's working fine and all but it does a random reboot every day or so, at random times, with random applications.
I have tried 2 different pre-rooted 5.1.1 firmwares already (yes, the correct model D6653 as well) and it still does it. The System Incident reports don't really say much (in fact you only see details about when it crashed, nothing else), and it seems like Google Play Services is the only thing mentioned in the Application Report.
The same thing also happened (more frequently) when she was on the 5.0 pre-rooted firmware. I'm not sure why, I haven't unlocked the bootloader or anything, it's just stock pre-rooted ROM, that's it. I haven't flashed any other ROMs other than the official pre-rooted ones.
Furthermore, before I flashed the 5.0 and 5.1 firmware for her, the phone came with Android 4.4.4. She used it for a month and reported several crashes as well, so that's with the original factory firmware, unrooted, unmodified etc.
She doesn't run any dodgy or random apps, she's just a typical girl that use Facebook and texting, that's pretty much it. I've done a lot of research on this issue and it seems to be quite common, however there isn't really a solution to this. The same apps she currently use never caused any issues on her older phones.
Also in case anyone asks, the only reason I flashed the pre-rooted 5.1.1 firmware for her is because it makes it easier for me to manage her phone (with Teamviewer, you can remote into the phone as long as it's rooted). Also, I get to backup her phone and do tests etc, makes it easier for me.
Also, I'm not using any custom kernels or overclocking the CPU etc. Everything is just stock but rooted.
Could this be caused by a hardware fault in the phone? I'm not sure what else I can do and would appreciate some suggestions.
Nobody have this issue??
Well, how about you try to flash a full, clean, stock ROM, don't root it, don't install any unnecessary app and see where it goes? If the issue persists, try getting a logcat from the phone and we can take a look at it. If it works fine after returning to stock, there might be a problem with the ROM or some apps you are using.
If it really is Gapps that are causing all the trouble, go to APKMirror and download the latest apps available (Play Services, etc) and see where it goes.
As mentioned already, prior to flashing anything, my girlfriend was running a completely stock, factory version of the phone. It came with Android 4.4.
I could flash a completely stock 5.1 ROM but was hoping that someone would share their experiences or a potential solution to this, considering this is quite commonly asked. I would also like to avoid doing this if possible, because if I were to go back to rooting the device, I'd have to downgrade to v4.4 pre-rooted, then flash to 5.1 rooted with custom recovery. It's just a lot of work for a simple testing that could be answered by others if possible.
Anyway, she didn't have any apps installed other than Facebook and Whatsapp, that's it. I might test with GAPPS and see how it goes, but I thought I'd ask here in case someone knows it's definitely a hardware issue or something else.
i would definitely give a pure stock 5.1.1 a go. I used to get the random reboots on the previous versions but i no longer have such issue.. Make sure you do a clean wipe and do it a few times.
Hi all, it's been a while but I thought I'd post an update and share what I've found/learned so far....
Basically, I'm still getting the frequent random reboots. I've tried reflashing the ROM and also tested out the latest .232 pre-rooted stock ROM, still getting the same issue. I've noticed that other than Google Play Services, sometimes Gapps will crash as well. But most of the time, there's nothing reported in the system or application crash logs. I've tested with everything running as stock, no additional apps installed. I then decided to flash the Minimal GAPPS 5.1.x and that sort of made the phone a bit more stable, but still reboots randomly every now and then.
Later on, I decided to try a custom ROM that still works on a locked bootloader. I found this here:
http://forum.xda-developers.com/z3/development/d6603-23-1-1-28-t3102271
The chef has provided a .232 firmware for you to flash in recovery, as well as the ROM base for the D6603 model. Mine is a D6653, but luckily the chef has also provided a D6653 patch for you to flash as well. I've flashed the ROM like so:
1. Wipe everything except my external microSD in TWRP. So basically, wipe system, data, cache, dalvik, internal storage etc.
2. Install .232 firmware.
3. Install v10.5
4. Install v12.0
5. Install D6653 v5 patch
It boots up fine but after using it for a while, I still get the random reboots. What's interesting is that I've also tried without flashing the D6653 patch, which essentially means I'm running just the D6603 base ROM on my D6653. It works, but still crashes as well. I just found it quite surprising that a D6653 could run a D6603 ROM, but it does make sense considering the main differences is just the baseband/frequencies.
Anyway, I later on decided to flash the pure 5.1.1 stock ROM, still getting the crash. Again, everything is tested on pure stock, no additional apps etc installed.
I'm starting to think perhaps this is a hardware issue on my phone?? I noticed that sometimes, my screen will show a bit of tearing and then it'll crash not long after. BUT, I also know that as soon as gapps or google play services crash, the phone will crash not long after as well.....
In fact, I later on used Titanium Backup to convert Google Play Services from a System to a User app, the phone will just boot into the lockscreen and then restart every time. This is a bit ridiculous because I've done this several times on other phones before and they never had such an issue. Of course, I'm not saying I always run Google Play Services as a User app, but that was just for testing and I honestly don't think it should cause a bootloop just because of that. I've also cleared dalvik and cache by the way, so it doesn't make sense that the phone boots into the lockscreen and then just restarts randomly.
I haven't tried uninstalling Google Play Services completely, but at this point I'm back to square one as I've exhausted pretty much all my options and it's been a complete waste of time. I'm beginning to hate this phone more and more. The only thing left is to unlock bootloader and play with other custom ROMs. But yeah, flashing the .232 firmware didn't fix it, AND flashing pure stock 5.1.1 Android didn't fix it either...
Just wondering if others have the same issue and any ideas what could be causing it? If I provide some Logcat logs, would someone be kind enough to look into this for me?
Update:
I'm still getting the random reboots and I think it's very likely to be hardware related. But sometimes also a bit related to software, specifically with Google Play services. I've had more time to test out a few things since my last update, they are as follows:
- Tested complete stock 4.4 ROM without root. Still crashes every now and then, but not as much compared to 5.0 and 6.0 (doesn't matter if it's stock or custom ROM).
- Finally gave in and unlocked bootloader (backed up my DRM keys of course). I thought perhaps that the stock Sony roms (and even the stock-based Sony custom roms) have issues for some reason. They are all the same base, so I thought I'd do a fair test by trying a completely different based rom, such as AOSP. I've used CM 1.2.1 nightly here:
forum.xda-developers.com/z3/development/rom-cyanogenmod-12-nightlies-xperia-z3-t3010201/page117
And yes, I know that nightly have bugs, but the nightly build as of 2016-03-03 seemed pretty stable according to most users. I've tried various other AOSP based roms and stock based Sony roms (for unlocked bootloaders) and they all produce crashes.
I've flashed custom kernels as well and updated my recovery to TWRP 3.0, but all the same results. On all of the custom ROMs I've flashed, the only thing I've done was setup my Google account (so I have my contacts and Gmail) and that was it. No other apps installed. I wanted to limit the environment down to just the stock setup of the ROM itself, as this helps me rule out any potential bugs caused by 3rd party apps.
Having done all of the above and still resulting in crashes, it's safe to assume that this is most likely unrelated to the software, but hardware. I've noticed that sometimes when I scroll a page too fast and move it up and down with my thumb, the screen will freeze and restart.
However, sometimes I will get crashes related to Google Play Services. Anything that relies on Google Play Services will crash randomly. If you re-open the apps, it just crashes again. If you force stop the app and open it, still crashes. The ONLY fix is to restart the phone. I have tried flashing different GaPPs, starting with the pico and nano versions, as well as the ones recommended by the ROM chefs. Still the same result.
So the conclusion is, I haven't really gotten anywhere with this annoying issue. There's definitely an issue with the phone somewhere, maybe a bit of software related, but mostly hardware.
I have googled, dug deep through XDA, went round in circles flashing modems, roms, kernels, everything i can (including stock rom), but I cannot seem to fix my note II. It is a T889 T-Mobile version, rooted, and flashed with TWRP 3.0.2.x I am running Revolution Remix 6.0.1 Marshmallow, and for the life of me I cannot figure out why I can't make calls. I attempt to make a call and i get no dial tone, however the call does connect and go through, but nor I or the person on the other end can hear anything at all. I have ran multiple system information checks and I have a valid IMEI, which is the original IMEI, i do not have a CSC code if that means anything, I have no access to any USSD codes, however I do have full SMS/MMS/Data (even hotspot) services. This phone was updated to the COH4 4.3 OTA before root, and TWRP flash. I have had zero issues flashing any rom for this device, GAPPS flashes fine, SuperSU and so on. I would very much like to be able to regain the ability to make calls so if anyone could help me that would be fabulous. Thanks!
Xenocide21 said:
I have googled, dug deep through XDA, went round in circles flashing modems, roms, kernels, everything i can (including stock rom), but I cannot seem to fix my note II. It is a T889 T-Mobile version, rooted, and flashed with TWRP 3.0.2.x I am running Revolution Remix 6.0.1 Marshmallow, and for the life of me I cannot figure out why I can't make calls. I attempt to make a call and i get no dial tone, however the call does connect and go through, but nor I or the person on the other end can hear anything at all. I have ran multiple system information checks and I have a valid IMEI, which is the original IMEI, i do not have a CSC code if that means anything, I have no access to any USSD codes, however I do have full SMS/MMS/Data (even hotspot) services. This phone was updated to the COH4 4.3 OTA before root, and TWRP flash. I have had zero issues flashing any rom for this device, GAPPS flashes fine, SuperSU and so on. I would very much like to be able to regain the ability to make calls so if anyone could help me that would be fabulous. Thanks!
Click to expand...
Click to collapse
as a side note, my USB port has taken a ****, so the only fix that i can do currently has to be done on the phone itself.
Hi !
This kind of problems can be basically solved in the rom thread you are using it , the developer can help when you post logs as well
Have you tried to flash to stock in order to exclude a hardware issue ?
Cheers !
*SOLVED: see reply*
The ROM I used before was LineageOS [10.0] and used a custom ROM with Android 9 before that. Needed to unlock my phone, and couldn't do that on Lineage, and had troubles flashing firmware with Odin, so I ended up using FrankensteinS6. The Stock kernel seems to let me input the NCK, and unlock the phone. So that's luckily finally over.
For about 4 days now I've been formatting phone and trying again and again. FrankensteinS6 works, some other 6.0/7.0 ROMs work. But LineageOS now enters a bootloop, and Pixel Experience (9.0 and 10.0) and Evolution X 10.0 don't detect the SIM. The ones that don't detect SIM also show no IMEI, which was worrying at first because I though I lost a partition.
Possibly related, the ROM of Pixel Experience Android 10.0 for G920W8 will not install because (paraphrasing) "This device is zeroflte, this file is for zerofltecan, zeroflte***, zeroflte***" claiming that my phone isn't one of those models. I got this S6 from Bell Canada, and I still have even the sticker that says it is a G920W8, not G920F. However, the Pixel Experience ROM for G920F flashes fine (sans the main problem).
I don't know the exact LineageOS ROM I used before, but I've tried all of their 10.0 releases, tried redownloading, and I get the bootloop every time. I see some info online of flashing modem firmware, but... I don't even know where to start with that. As I mentioned at the start, Odin is crapping out. I couldn't flash firmware with it, because it would reject the phone right after I started flashing. Anything I could do within TWRP would be great. I moved it back to FrankensteinS6 for my sanity, I started doing this Sunday and I'm starting to repeat steps over and over hoping that it just solves itself.
I tried to keep this straightforward, and I'm sure I did a bad job. I can extrapolate on what I have attempted. Please tell me what I have to do to get an android 10 ROM working on this old beauty again.
I do not have all the solutions. As per my tests with my SM-G920W8. I have managed to find ROMS and try them out. I have only seen Nougat 7.0 ROMS to work almost flawlessly. NOT 7.1.2, important, 7.0 only.
I have also tested some Pie and v10 ROMS like Pixel Experience. The ROMS boot nicely but since I do not use a SIM card to call as I use SIP phone numbers and require WiFi. But that left asside, I came upon serious camera issues no matter what I try. Up to now, SamStock ROM is pretty much the best Stock ROM I found but I always need to run the Magisk UNINSTALLER before re-installing the latest Magisk version..
As for Kernels, well, Anything that is oriented with Lineage OS, I've had camera issues even with Nougat v7.0. So basically, the only ROMS I found good, as of today, for now, are stock ROMS v7.0. But, to do your tests, Even if you have a 920F ROM, you can download a 920W8 kernel as long as you download a kernel which supports your installed Android version. Also make sure to download the proper Stock or AOSP kernel (AOSP for LineageOS). There's not many but there's a few ones that work properly.
Another option is to download an AOSP ROM that works for W8 phones, unzip the file and grab the boot file inside corresponding to the W8 or T-Mobile version. You simply unzip your real ROM you want top install, replace the boot file for the one you got and rezip it. This made my phone boot properly for some F version ROMS but again, not without issues. That's why, I really suggest v7.0 Srock ROMS. I hope this helps you a bit. Again, you can have your own tests and other users may have other answers, but this is based off over 30 bootloops in my case of trying to mod a ROM for the W8 model. It's not easy to find a good one for Canada, I admit!!!
I flashed TWRP years ago, and I found out that I had a G920F version flashed. I don't know why Lineage allowed me to use SIM before, but rectifying this issue seems to made the SIM work in newer versions.
I don't know what the S6's predisposition to having crashing cameras is, but I have avoided this in the past by using custom camera apps, like Open Camera. This has saved me every time.
As for the boot loops... I think another thing that helped is that "format data" doesn't wipe the OS. When you are in recovery, having issues with bootloops in various ROMs, try advanced wipe, and wipe the system. It didn't fix right away, but the time I got Pixel Experience 10 up and running that was the trick.
Hello,
I own a motorola one vision and would like to flash LineageOS 20 on the device. I am creating this thread to know the experiences of people who did something similar. I would like to know if there is any issues with a custom ROM on this device [calling issues, or similar]. I would also like to know if there is a way to revert back to the stock ROM in case I screw up something. I have read several threads about this device but I would like to confirm it again and be provided with some pointers of what I could expect with a custom ROM on this device and how I could revert back to the stock ROM in case I screw something up.
Thanks in advance
nsg650 said:
Hello,
I own a motorola one vision and would like to flash LineageOS 20 on the device. I am creating this thread to know the experiences of people who did something similar. I would like to know if there is any issues with a custom ROM on this device [calling issues, or similar]. I would also like to know if there is a way to revert back to the stock ROM in case I screw up something. I have read several threads about this device but I would like to confirm it again and be provided with some pointers of what I could expect with a custom ROM on this device and how I could revert back to the stock ROM in case I screw something up.
Thanks in advance
Click to expand...
Click to collapse
I have been using lineageos since last year. I have used lineageos19 and am currently using lineageos20. The user experience is quite good. Everything works fine including calling except the hotspot. Hotspot does work but you have to keep tapping on the toggle to enable the hotspot or you can just restart the phone that's the temporary fix for the hotspot issue. The developer might fix the issue in the future updates. Other than that I didn't find any issue with the ROM and also it doesn't pass the safety net so you have to root your phone and install magisk to bypass safety net so that you can use your banking apps.
There are two versions official and unofficial. Official gets update every week and unofficial one is with the pixel features and google apps. It gets monthly updates.
If anything goes wrong you can install the official software called lenovo rescue and smart assistant on your pc and connect your phone with usb to pc. It can recover your phone to the original android 11 stock ROM.
Ryukrryts said:
I have been using lineageos since last year. I have used lineageos19 and am currently using lineageos20. The user experience is quite good. Everything works fine including calling except the hotspot. Hotspot does work but you have to keep tapping on the toggle to enable the hotspot or you can just restart the phone that's the temporary fix for the hotspot issue. The developer might fix the issue in the future updates. Other than that I didn't find any issue with the ROM and also it doesn't pass the safety net so you have to root your phone and install magisk to bypass safety net so that you can use your banking apps.
There are two versions official and unofficial. Official gets update every week and unofficial one is with the pixel features and google apps. It gets monthly updates.
If anything goes wrong you can install the official software called lenovo rescue and smart assistant on your pc and connect your phone with usb to pc. It can recover your phone to the original android 11 stock ROM.
Click to expand...
Click to collapse
Hey! Sorry for checking after this long. I don't plan on using any banking apps so it will be fine for me. I already got my unlock code and just have to unlock the device and flash LineageOS. I will do that after backing it up. Thank you for your sharing your experience !!!