Related
So, I was using my phone at a mall. I stepped into a store and I noticed I had no more LTE. The signal was weak, so I thought it was just the building. So I got to a stronger area and restarted the phone, and still no data. I tried restarting several times and I tried selecting different APNs (I'm running 7/15 nightly of CM13). Eventually, I took the sim card out of my wife's iPhone 6S and the LTE worked fine. My sim card worked OK in here phone as well. But once I put mine back in, I have no data (not even 2g or 3g). I thought it was just my sim card, but then I can't understand why it works in my wife's iPhone 6S. Any ideas? I'm updating to the latest nightly of CM13.
ambig88 said:
So, I was using my phone at a mall. I stepped into a store and I noticed I had no more LTE. The signal was weak, so I thought it was just the building. So I got to a stronger area and restarted the phone, and still no data. I tried restarting several times and I tried selecting different APNs (I'm running 7/15 nightly of CM13). Eventually, I took the sim card out of my wife's iPhone 6S and the LTE worked fine. My sim card worked OK in here phone as well. But once I put mine back in, I have no data (not even 2g or 3g). I thought it was just my sim card, but then I can't understand why it works in my wife's iPhone 6S. Any ideas? I'm updating to the latest nightly of CM13.
Click to expand...
Click to collapse
My suggestion is to start fresh by fastboot flashing the latest 6.0.1 factory images. Verify that your mobile data/LTE are working. Then, install TWRP. I would also download a fresh copy if the CM13 ROM and verify the md5 is correct. Flash CM13 again and see if you have LTE again. If you don't have LTE after flashing CM13 again we know it is something that has changed in the ROM.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
My suggestion is to start fresh by fastboot flashing the latest 6.0.1 factory images. Verify that your mobile data/LTE are working. Then, install TWRP. I would also download a fresh copy if the CM13 ROM and verify the md5 is correct. Flash CM13 again and see if you have LTE again. If you don't have LTE after flashing CM13 again we know it is something that has changed in the ROM.
Click to expand...
Click to collapse
I think you're right. I'm going to have to do this. I got a new SIM card from Verizon and data was fine. Then once I went to work and entered into my office, which has a poor signal, I wasn't able to get data back (can still call and send/receive texts). It makes no sense as to why it won't reconnect after a reboot, but I guess this is the only option.
Yeah I agree. Fastboot flash the factory images to give yourself a fresh start. Confirm that everything is working on a fully stock build. Then root, recovery and flash. I would try a different ROM that is not CM based to see how your voice and data works. Let us know how it goes that way others in the forum who may run into this issue can read about what was performed on your device and know what to do to help themselves. Good luck.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Yeah I agree. Fastboot flash the factory images to give yourself a fresh start. Confirm that everything is working on a fully stock build. Then root, recovery and flash. I would try a different ROM that is not CM based to see how your voice and data works. Let us know how it goes that way others in the forum who may run into this issue can read about what was performed on your device and know what to do to help themselves. Good luck.
Click to expand...
Click to collapse
So I flashed the factory images back onto my phone and I got data back. I guess there is a strange bug in the latest nightly of CM13. Of course, I haven't been able to go to an area where I have poor reception. Now I have to find a ROM that offers the LiveDisplay feature CM13 offered. I like my screen to be a bit colder than what Huawei calibrates their displays to.
ambig88 said:
So I flashed the factory images back onto my phone and I got data back. I guess there is a strange bug in the latest nightly of CM13. Of course, I haven't been able to go to an area where I have poor reception. Now I have to find a ROM that offers the LiveDisplay feature CM13 offered. I like my screen to be a bit colder than what Huawei calibrates their displays to.
Click to expand...
Click to collapse
I knew there was something in the CM13 based ROM's that was causing you to lose data. Also, If you use a custom kernel like Elemental or Elite you can control the screen colors and make it how you like it. Give Pure Nexus a try. It's a super nice ROM. The dev is awesome. He does great work. Maybe give Chroma a shot. Also, you could try Resurrection Remix. It's a CM based ROM but it may not give you the data issues. It's worth a try. Lemme know what works. Good job on getting the factory images flashed and getting data back too.
Sent from my Nexus 6 using XDA-Developers mobile app
It appears that a couple of people tried flashing the Pixel 2 XL system.img onto the Essential PH-1, and was able to boot it, and have (almost) everything working:
https://forum.xda-developers.com/es...ashed-img-pixel-2-xl-opm2-171026-006-t3805921
This didn't used to be the case when the PH-1 was on 8.0. The people there mentioned that they went directly from having official Essential 8.1 June firmware installed and just flashing the Pixel system.img. All it took from that point on was a data wipe and it (allegedly) booted (almost) flawlessly. Some folks there also mentioned that Pixel 2's Android P DP3 system.img booted successfully as well.
@phhusson thoughts?
It boots the same right after oreo or P. There is no mobile data, so no calls or text. I fixed the camera, which was the other bug. I tried flashing my phones vendor images and modem over top of this and it still doesnt fix it. Must be in the system some place. I may try to swap out some lib, or hw files. Then maybe look at the build prop
i have done thins as well...boots flawlessly but as stated, no service or wifi for me...how was the camera fixed?
BakedTator said:
i have done thins as well...boots flawlessly but as stated, no service or wifi for me...how was the camera fixed?
Click to expand...
Click to collapse
I kept a folder of all camera related lib files from our Android p stock, then after booting this, i just used trial and error till i got the camera working. I am certain i could replicate but until we fix the no service probs i stopped messing with it. Just wasnt worth it. I moved on to flashing as many treble gsi's as i could. They all work mostly except for play store issues.
it also works on the Leeco Pro 3 X7272/720
Everything works. Except for call sound
tsongming said:
it also works on the Leeco Pro 3 X7272/720
Everything works. Except for call sound
Click to expand...
Click to collapse
Flash Pixel2XL's A/B system.img to A-only LePro3 directly???
qqzwc said:
Flash Pixel2XL's A/B system.img to A-only LePro3 directly???
Click to expand...
Click to collapse
System A only
However, unless this file has been updated you are better off following the GSI instructions in my signature.
or here: https://forum.xda-developers.com/le...nstall-gsi-t3843142/post77636477#post77636477
Which one do you guys recommend the most?
I'm on stock Oreo (soak 4) and I'm curious about PE.
What can you guys tell me about it?
Pixel Experience!! Because it gives you some pixel like features. And I've noticed that stock ROMs usually have problems with Root!! When I had rooted my device the camera had stopped working. I tried everything but the only way to get it to work was uninstalling magisk!
S4xk said:
Pixel Experience!! Because it gives you some pixel like features. And I've noticed that stock ROMs usually have problems with Root!! When I had rooted my device the camera had stopped working. I tried everything but the only way to get it to work was uninstalling magisk!
Click to expand...
Click to collapse
But how am I getting sure that don't ruin my IMEI or persist in the process of trying Pixel Experience?
eder5jga said:
But how am I getting sure that don't ruin my IMEI or persist in the process of trying Pixel Experience?
Click to expand...
Click to collapse
Just make sure you backup those partitions on TWRP preferably on an external drive for safekeeping. Or if you loose them there's a guide here on xda that allows you to restore it but you'll end up getting your internal storage wiped in the process. I'd rather advice you to backup system, data( if you want ), persist, efs, and maybe even oem (for when you use treble ROMs in future).
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.
Greetings.
Due to events beyond my control, I had to give up my Pixel 3 XL (packing it as I type this)
Until funds become available, I decided to bring the Nexus 6P - with pre-mature battery shutdown issue - back to duty. I have new battery, lens cover, etc. waiting in the wings so it may become my primary whip after all. That is "if" I can undo whatever mistake I made tonight (knocking on wood).
The 6P was unlocked already before being retired (Idon't know if it matters or not). Stock image (I think it was 8.1) with security update from December 2018 I think.
Here's what I think I did tonight that lead to the current situation:
1. installed TWRP 3.3.1
2. along the way wiped one too many partitions - my stupidity
3. thanks to TWRP for warning me that there was no OS so went back, found USB-A to USB-C adapter, copied "PixelExperience_angler-10.0-20191113-2124-OFFICIAL," and used TWRP's "Install" option
First problem is that I noticed in the text log within TWRP that the vendor image was missing
Second problem, or perhaps because of above, after restarting the 6P it never gets out of the welcome screen of Android 10
Third problem, again may be related to #2 in the things I did tonight, when I reboot into TWRP recovery, first thing it does ask is "Mount, Decrypt Data" and "Enter Password" to which I don't know the password. If I select "Cancel" I get to TWRP main menu but I can see that "Internal Storage" is now at 0MB.
I know I did wrong here but is there any way to recover? Since it doesn't boot into Android 10 (just stuck at welcome screen, I guess using ADB on laptop, if it helps, is out of question? Can I fix this through TWRP?
Thank you for any help/advice.
UPDATE: Reading some more threads on XDA & decided to try Lineage. At one point seems to have things working following the directions but the SIM card was not recognized.
Thinking of trying again with Lineage but maybe with Lineage16 instead of 17. But what is the best stable ROM that is plain Android but perhaps based with up-to-date security patching?
Thank you!
ur2punk said:
UPDATE: Reading some more threads on XDA & decided to try Lineage. At one point seems to have things working following the directions but the SIM card was not recognized.
Thinking of trying again with Lineage but maybe with Lineage16 instead of 17. But what is the best stable ROM that is plain Android but perhaps based with up-to-date security patching?
Thank you!
Click to expand...
Click to collapse
I've been running aicp for the past few months, which is 9.0 they still put out weeklies with security updates. Not sure how long they plan on supporting 9.0 though
Lawlrus said:
I've been running aicp for the past few months, which is 9.0 they still put out weeklies with security updates. Not sure how long they plan on supporting 9.0 though
Click to expand...
Click to collapse
Thank you. Because the SIM was not recognized, I was going to restore to the last Android. I may just try the aicp ROM first.
ur2punk said:
Thank you. Because the SIM was not recognized, I was going to restore to the last Android. I may just try the aicp ROM first.
Click to expand...
Click to collapse
Yeah I haven't noticed any issues with Sim with this device. You said you had it on a shelf for a while though, if it was before the last update the device got, DEC of 2018 did you DL the ota a d make sure the radio was up to date ?
ur2punk said:
Thank you. Because the SIM was not recognized, I was going to restore to the last Android. I may just try the aicp ROM first.
Click to expand...
Click to collapse
I had this SIM card issue when I was trying to flash RR, tried twice with same results. Came across a post once about a bug and it said to remove all screen locks, low and behold it worked... weird
redshirt110 said:
I had this SIM card issue when I was trying to flash RR, tried twice with same results. Came across a post once about a bug and it said to remove all screen locks, low and behold it worked... weird
Click to expand...
Click to collapse
Ah yeah, I've seen that before no idea why people have to do that. I've never had my Sim stop working because of a screen lock. I never looked onto why it happens. I always chaulked it up to a not a US problem because most of the people that posted about it seemed to be from a different country lol.
Update!
I thought it would be a good idea for me to try this routine of wipe & install the Android 8.1 again to get myself comfortable with the process. Long story short, I did exactly that:
(- Bootloader was already unlocked)
- TWRP
- flashed/installed Dec 2018 OTA images/zip
- Installed Magisk
Everything seemed to be working fine when I found out ,while on road, that Google Maps don't work after 5 seconds or so (the navigation part). Read up & they suggested safe mode so I did that. Happy to report that it works so it is not the GPS antenna as some had reported. Whew.
Is there any particular image I need to reflash to see if that was the problem? Or should I just reinstall again? At least I'm getting more comfortable with the various commands - LOL.
Thank you!