Database Users

[Q] Unable to connect to mobile data

I finally got superuser working by flashing Echoe Illusion, the full touch-wiz version with Android 4.3. At first it seemed like I had everything working but the next day when I left the house (no longer connected to home wifi) I quickly realized it was refusing to connect to mobile data. I also cannot send text messages, and likewise I can assume I can't get them either. I have tried flashing the nightly CM11 build and 3G connected although LTE did not. I wasn't in an area where I expected reliable LTE anyway so that's not even an issue at this point because I'd very much like to use this Echoe Illusion rom, or another Touch-wiz based one. I just can't go downloading a bunch of them because I have a severe restriction on data usage and have already downloaded Echoe Illusion AND multiple other things. If it matters, my baseband ends in MJA.
I have also attempted to flash different modems with Odin, although all of them failed completely to flash at all and at this point I have to honestly admit I don't know what I'm doing. This is most definitely not my first time rooting...I'm just used to HTC phones, the Evos in particular. Thanks in advance if anyone can help or provide useful tips!
oh and P.S. I can't go back to the stock firmware because I must have flashed an incorrect kernel, and it borked the phone. I only got it working again by flashing a separate rom (Echoe Illusion) and have since flashed other kernels with no ill effect. I had a nandroid backup of the stock rom before I borked it, but every time I try restoring it, it stops at the yellow Sprint screen and won't boot.

[Q] Camera light not working in AllianceROM

I can't seem to get the camera light to work at all with AllianceROM build 1. It won't flash in the camera app, and I've tried 3 different flashlight/torch apps and it none of them will light it. Any ideas?

Update
GuitarAudiologist said:
I can't seem to get the camera light to work at all with AllianceROM build 1. It won't flash in the camera app, and I've tried 3 different flashlight/torch apps and it none of them will light it. Any ideas?
Click to expand...
Click to collapse
It suddenly works again. I'm not sure what happened, but I restarted the phone a few times, booted to the stock ROM, and then booted AllianceROM again and now it works (for now). Possible bug?

GuitarAudiologist said:
It suddenly works again. I'm not sure what happened, but I restarted the phone a few times, booted to the stock ROM, and then booted AllianceROM again and now it works (for now). Possible bug?
Click to expand...
Click to collapse
There are many reported issues with rom slots in Safestrap. It is always recommended to flash on the stock slot. If you insist on running multiple roms I'd advice keeping your daily rom on the stock slot for the battery performance alone.

kinstre11 said:
There are many reported issues with rom slots in Safestrap. It is always recommended to flash on the stock slot. If you insist on running multiple roms I'd advice keeping your daily rom on the stock slot for the battery performance alone.
Click to expand...
Click to collapse
Thanks for the advice. I'm still scratching my head on this one though, as AllianceROM is currently in the stock slot.

I'm going to try out Jasmine ROM v1.8. Flashing it to the stock slot now (did a nandroid backup of AllianceROM and moved it to a ROM slot.) Maybe Jasmine ROM will be less quirky.

GuitarAudiologist said:
I'm going to try out Jasmine ROM v1.8. Flashing it to the stock slot now (did a nandroid backup of AllianceROM and moved it to a ROM slot.) Maybe Jasmine ROM will be less quirky.
Click to expand...
Click to collapse
There are some quirks to every rom but multiple flashing can leave residual things behind that screw with what is currently running.
I do this everytime I flash a new rom. If you don't know about this already you'll be surprised just how much is left behind after wiping the slot the normal way. You should still do both wipes. However be aware that even doing both of these multiple times there will still be some residuals left over.
The other thing I can recommend (but not all the time, warnings are in the OP) is a Odin restore. This will completely wipe and reset everything, there should be no residuals.
Good luck on Jasmine.

Not sure on your particular problem, since you said you were in fact on stock slot. But a few comments just in case it helps. I had problems with every single rom that I did NOT put on a freshly wiped stock slot. Any other slot always created problems. I also ran into many various issues when reinstalling my titanium backups. So the last install of Alliance that I made (the current rom that I'm using now, for the last couple of months), I kept it to a very minimum. I used titanium to reload my texts and maybe a few game apps (data only), that was all. I always use google to restore my contacts, emails, etc. And my pictures, ringtones, etc are always stored on my sd card. I know allot of people rely heavily on backups, but I usually have more problems than what its worth. Hell, up until the last couple of roms, I never even made backups. If I bricked a phone, I just wiped and started all over. And the same every time I switched roms. The only thing I lost was old texts and my progress on solitaire scores, lol.
As far as your specific problem. The only thing I would suggest is try thinking of any sort of settings or apps that might link the flashlight or torch feature with the camera. I don't use any other apps, but I know there are allot of alternative torch apps, and also ones that use the camera, like instagram, etc. The only experience I have with any related error is if I try to open the camera while the torch is on, it force closes the camera. Turn off the torch, reopen the camera, all is back to normal. I'm using the stock camera, and stock torch app...

[Q] Advice Please - Mobile Odin - Could not detect device model - USB not recognizing

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.

Refresher on world of custom ROM's

Hi all
I have a Samsung Galaxy S5 G900F, which when I got it 18 months ago was very eager to get involved in rooting and getting a custom ROM on it.
Fast forward to present day and the novelty has worn off, I haven't kept up to date with anything, and I am probably very out of date.
As such I would like to either update to the latest ROM or just flash the latest stock - I am not sure I really use much nowadays that even requires anything other than stock (used to play a lot with Tasker, sysadmin apps)
What has prompted this is of late my phone has been very laggy, crashing, sys apps hanging, etc. I also dropped my phone ages ago and occasionally the screen stops working (although still responsive) and I have to take the battery out to get it back (sometimes it reboots to a full screen of coloured static, and I have to repeat this several times). Now I know this seems like a hardware issue but at times the phone will not have been touched or moved and it'll do this, which makes me hope that maybe updating it will help.
I have a paid version of Omega Files Pro but apparently there has been no update for a very long time.
Hopefully you guys can help me get back up to date and on a level
Android Version: 5.0
Baseband version: G900FXXU1ANCE
Kernel Version: 3.4.0-Omega-1.0
Build Number: Omega V17 - XXU1POCF
I have PhilZ Recovery iirc.
Thanks in advance, if you need anymore info please say.

Install the rom from alxndr thread. Its a stock rom slightly optimized. It is the best for stability, performance and battery. There is only great reviews about it, it has a great community, and he updates it very frequently.
He has roms for either android 5 or android 6, which could can find in the second post of the thread.
If you choose to install android 6, you will have to update the bootloader and modem. They, as well as instructions, can be found in his thread.
http://forum.xda-developers.com/galaxy-s5/development/rom-ane4-kitkat-4-4-2-multi-csc-t2813628
To correct the issues, you will probably need to perform a full factory reset before installing the rom. Before anything, I recommend you to do a full rom backup (using your recovery). That way, if you forgot to backup something (like your taskers profiles), you can always go back.
Before doing the factory reset, you should backup your SMS, calls and apps. The easiest way to do it is by using the integrated backup tools in your S5 options : in the backup&restore sections, you will find a Samsung section that can backup messages and phone calls. There will also be a Google section where you can choose to backup your apps. If everything is set up correctly, once you will boot the new rom, you will be asked sequentially if you want to restore the samsung (Messges, call logs) and google (apps) data.

Thank you I'll have a read.

Need help getting LineageOS to be stable (15.1 UNOFFICIAL, hltevzw, TWRP 3.3.0)

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.