[Q] Stuck between two "handicapped" results of flashing PA through diff. recoveri
http://forum.xda-developers.com/show....php?t=2020336 This is where i got all the zip which i flashed (radio, bootloader, PA ROM, and GApps)
So there are two problems I have noticed after flashing my nexus with paranoid android.
The biggest one is that my phone cannot get any cellular service. The phone just shows No Service, and when i tried to set mobile network manually it told me to insert sim and restart while already having a sim card in the phone. I tried removing and inserting it again to no avail.
The second one is that I can't use my camera, it opens the app for like half a second then it shows "Can't connect to camera" and quit abruptly.
Everything works just fine when I flashed the backup stock ROM, including the mobile data and camera
UPDATE :
I tried using TWRP instead as the recovery that I use to flash the exact same 4 zip files (radio, bootloader, PA ROM, and GApps, all from the official PA account on XDA developer). It indeed solved the No Service problem, it now has fully functioning HSDPA connectivity, but then two problems emerged.
The first being the unavailability of keyboards. The phone would just show the microphone icon for voice typing and no keyboard is found in settings.
The second problem being there is no Camera app, so I can't decide whether the "Can't connect to camera" issue is solved.
So I am stuck in between two "handicapped" results of flashing PA through different recoveries. (keep in mind that I used the same exact 4 zip files to flash)
1. I can flash it through Clockwork Recovery but then the phone wouldn't recognize the SIM card although everything else would work perfectly.
2.I can flash it through TWRP and the phone would have perfect mobile connectivity, but then the phone would have no keyboard showing up and no Camera app. I had assumed this would be an easier problem to solve by googling, but it seems like this problem is rather unique/specific.
Is there a way i can install the keyboard and camera by itself?
Remember that there is no keyboard so I really can't type in anything including signing in on the Play Store. I attempted installing Google Keyboard through the desktop play store, but since the one on my phone isn't connected to my Google account, the download won't start on the phone.
wolverine060 said:
http://forum.xda-developers.com/show....php?t=2020336 This is where i got all the zip which i flashed (radio, bootloader, PA ROM, and GApps)
So there are two problems I have noticed after flashing my nexus with paranoid android.
The biggest one is that my phone cannot get any cellular service. The phone just shows No Service, and when i tried to set mobile network manually it told me to insert sim and restart while already having a sim card in the phone. I tried removing and inserting it again to no avail.
The second one is that I can't use my camera, it opens the app for like half a second then it shows "Can't connect to camera" and quit abruptly.
Everything works just fine when I flashed the backup stock ROM, including the mobile data and camera
UPDATE :
I tried using TWRP instead as the recovery that I use to flash the exact same 4 zip files (radio, bootloader, PA ROM, and GApps, all from the official PA account on XDA developer). It indeed solved the No Service problem, it now has fully functioning HSDPA connectivity, but then two problems emerged.
The first being the unavailability of keyboards. The phone would just show the microphone icon for voice typing and no keyboard is found in settings.
The second problem being there is no Camera app, so I can't decide whether the "Can't connect to camera" issue is solved.
So I am stuck in between two "handicapped" results of flashing PA through different recoveries. (keep in mind that I used the same exact 4 zip files to flash)
1. I can flash it through Clockwork Recovery but then the phone wouldn't recognize the SIM card although everything else would work perfectly.
2.I can flash it through TWRP and the phone would have perfect mobile connectivity, but then the phone would have no keyboard showing up and no Camera app. I had assumed this would be an easier problem to solve by googling, but it seems like this problem is rather unique/specific.
Is there a way i can install the keyboard and camera by itself?
Remember that there is no keyboard so I really can't type in anything including signing in on the Play Store. I attempted installing Google Keyboard through the desktop play store, but since the one on my phone isn't connected to my Google account, the download won't start on the phone.
Click to expand...
Click to collapse
Have you tried re downloading the zips again? maybe one is corrupt? make sure you do a full wipe before flashing ( also do advanced wipe and wipe all except sdcard and usb)
You could also try Wugs root tool kit, http://www.wugfresh.com/ im pretty sure it has a feature to allow you to push apps to your system,
Hello,
I recently rooted my sgs4 gt-i9505 to the goolge edition using a YoTube tutorial on how to do so. Everything worked fine at the start but when I tried to install the PAC man rom, it jus stayed in the loading screen.
I restarted and tried rebooting but to no avail. I went back into the recovery mode and wiped the phone (divlac, cashes and system) then I reinstalled the google rom to find my wifi was not working. I tried the same process again, wipe- reinstall. Now I can't receive calls, the wifi doesn't work, home button only works on double tap, pull down status bar works but nothing in displayed.
My question is, does anyone have any ideas on how I would return my device to normal or know a full proof recovery and rom I can use that will correct these problems.
I am in the UK if that makes any difference.
Thanks for all and any help.
Matt
Matt.graham said:
Hello,
I recently rooted my sgs4 gt-i9505 to the goolge edition using a YoTube tutorial on how to do so. Everything worked fine at the start but when I tried to install the PAC man rom, it jus stayed in the loading screen.
I restarted and tried rebooting but to no avail. I went back into the recovery mode and wiped the phone (divlac, cashes and system) then I reinstalled the google rom to find my wifi was not working. I tried the same process again, wipe- reinstall. Now I can't receive calls, the wifi doesn't work, home button only works on double tap, pull down status bar works but nothing in displayed.
My question is, does anyone have any ideas on how I would return my device to normal or know a full proof recovery and rom I can use that will correct these problems.
I am in the UK if that makes any difference.
Thanks for all and any help.
Matt
Click to expand...
Click to collapse
You could try to go back to stock and check if everything still works there.
Did you flash the correct modem/baseband for the ROM / your carrier? There is a thread in general for all the modems. Chances are with a KitKat ROM you need to update your modem. Read that thread and give it a go. The file is about 15mb and takes a minute to flash in Odin. Failing that go back to stock.
Nothing in status bar: that's what it looks like in stock, you can use 2 fingers for the quick settins. Installl WANAM XPOSED fromwork for more tweaks and options!!
Home button double tap: that's the way it works on the google edition, that's just it. BUT wanam xposed can change this with the Gravity Box module!! You could try the Echoe 2.2 kitkat rom it has xposed pre-installed.
Keep in mind things look blanker and less functional as you no longer have samsung touchwiz which adds a LOT of stuff to the stock experience!
One more thing: ALWAYS make a nandroid backup before flashing ANYTHING at all, you never know when you will need it. Backup the nandroid to your PC also just in case, things go missing/ get deleted! T
XDA,
Received my phone (vs980) and immediately rooted and installed ROM on it. I have gone through multiple ROMs with the same result in that everything works great except for the phone app. I can navigate through contacts and dial fine, but when I execute the call, the screen goes black for about 10 seconds (can still see the status bar) then finally gets to the "call in progress" screen where it immediately ends the call. Phone will not even recognize inbound calls and sends them to voicemail after about a second or two of ringing. I am currently on resurrection remix v5.1.1 but was previously on C-rom v6.5 (also tested 6.4 with same result). Unfortunately I can't say I made a call on stock before rooting/ROMming so I don't know if it's a persistent issue. I have tried clean wipe of data/system/cache/dalvik cache, and have cleared the app data for the phone and dialer apps as well to no avail. Baseband version is vs98012b. Should I try wiping internal storage as well? My next step is to return to stock and test there but that seems like a more labor intensive process that could be avoided if I'm missing something else. Could this be a possible hardware issue? All help is appreciated.
B
Hello,
I have a very strange problem:
On my galaxy S4 I9505 android version 4.3 if there is a video player available then the app goes stuck, the apps:
- Youtube
- Facebook (app and browser)
- Browser
The videoscreen stays black and the app goes stuck for a while, the video will never play.
The other similair problem if someone call me or if I want to call someone the phone got stuck as well.
I already tried:
- wipe data and cache / factory settings
- wipe full data to install new rom in philz touch recovery
- Install new rom (4.4 and custom 5.0 lollipop)
The problem remains..
Everything else works perfect but this are 2 important thing what needs to work.
Someone have a Idea?
Important to report: I was on custom lollipop and I downgrade it with the downgrade files on this topic because 4.3 has mirrorlink support for my new car.
http://forum.xda-developers.com/showthread.php?t=2792516&highlight=downgrade
That problems appears when you try to downgrade your device. Reflash stock android 4.4.2 and your problems will be gone :highfive:
Thanks! Tried a few times to flash it back to this stock rom and 4 times failed! Used differtent versions of odin. 3.09, 3.07, 3.04 and some older one 1.85 or something.
I stopped for a half hour (Phone turned off half hour) tried it again and it worked. Very strange but it works.
Thanks very much!
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.