Samsung Galaxy J370f SIM stopped working after custom ROM and Kernel - Samsung Galaxy J7 (2017) Questions & Answers

I wanted to change my phones SELinux status to permissive. I've tried everything, but it just wasn't working. After some deliberation i downloaded this https://forum.xda-developers.com/galaxy-j7-2017/development/rom-godness-one-ui-t3936809 Custom rom. Don't get me wrong, it works great, but SELinux is still Enforcing on paper which doesn't work with the app. After that failed, i flashed this https://forum.xda-developers.com/galaxy-j7-2017/development/kernel-refined-kernel-v2-5-t3731176 Kernel. My phone booted, I opened settings and there it was. Permissive. I was happy for a very short while since I noticed that my SIM card wasn't working. I've removed it, moved it to different slots and nothing is happening, can't access the SIM menu either. I've tried installing a stock Sboot with Odin, but it always says fail (i don't really get this process). Any suggestions?

https://forum.xda-developers.com/galaxy-j7-2017/help/sim-issues-bootloader-t3960740
In short, custom kernels aren't compatible with new bootloaders (SIM issues) and you can't downgrade them. We'll have to wait until someone looks into it.
You need to install the latest stock ROM.

Related

Problems flashing last stock rom

Hello world, I have a problem with my phone, I'm gonna try to explain it exactly.
I had the 4.4 android version for almost two years, until yesterday (yep, I've been so lazy that I didn't touch my phone for that time). I was tired of being unupdated, so I took my phone and I connected it to the PC via USB. I downloaded the last spanish available version 'Spain (PHE) PDA. G900FXXU1CPEM CSC. G900FPHE1CPE3' because I'm from there, I did the essential wipes and I flashed it via Odin, and that was all. After that the phone wasn't working good (I don't remember exactly what happened after that) so I reflashed it again then I flashed both files: BL_G900FXXU1CPF3.tar.md5 & CP_G900FXXU1CPE8.tar.md5 because I thought I had to upload too the modem and the bootloader. After that the phone wasn't working well neither. I think I reflashed the last stock rom then a combo modem/bootloader I downloaded from the Phoenix ROM, then I flashed Chainfire's autoroot and last TWRP. When I restarted everything looked fine except the yellow message on top at the intro "SET WARRANTY BIT: KERNEL". I read about and the phone run every time, so I thought I had to be used to it, that's all. When I started to clean bloatware I deleted some apps (nothing special, just bloatware) and I removed every KNOX app, because I don't care about it, first day I got the phone I set KNOX to 1 because I didn't know about it and now I don't have any warranty anymore plus everytime I have a problem I solve it myself or with your help.
Now the phone is stuck at the boot, with the SET WARRANTY BIT: KERNEL" and it doesn't go further. Can you please help me to flash the last rom, the one I told you, with its proper bootloader, modem, etc? I just want a clean PHE 6.0.1 stock rom for the moment (rooted and with TWRP too, of course). Thank you.
Try flash rom with odin first(ap),after bl and cp(bootloader and modem (latest from the alexndr 's thread where he upload the latest one )after that when it finish if you stuck at samsung boot animation for long time try boot in recovery and do a factory reset and format cache.

Samsung galaxy note prime TWRP Blackscreen (textnow phone)

I installed TWRP bootloader onto my OEM Unlocked Samsung Galaxy Core Prime G360P Via Odin, and afterwords attempted to boot into Bootloader.
Upon doing so the phones screen goes black, and it acts like its turned off. My computer can't detect it with ADB, and I can't boot it back on without removing the battery and then inserting it again, after which it boots normally.
So yes my phone is working, but I need to get the bootloader working, I don't even have the normal android one right now because of this odd bug, i have rooted phones and tablets before both via Kingroot, and ADB depending on the needs of the device, and have some slight experience with it but limited technical knowledge, i have found seemingly similar problems but all said to solve via ADB, which doesnt really work as my ADB cant detect my phone when it is in this dead state it goes into instead of bootloader.
I would like a fix that will allow me to have TWRP installed, nothing that requires root as i have attempted all one-click rooters and none work for my phone, and i cannot install a custom OS as I am on textnow wireless and getting it to work with one is the biggest pain on earth (plus my calling would become sh^te without the custom textnow rom calling)
So basically i need to fix the bootloader without installing a new OS altogether, without deleting any of my inbuilt apps, and without factory resetting as I cant get to the bootloader to factory reset anyway, honestly i just need a way to get TWRP to work. If the answer involves another way of rooting my phone via Odin (yes i can still get to the odin downloader) and then running a root requiring app to fix my recovery thats fine but i dont know how to do that or what it would entail
im using: twrp-3.0.2-0-cprimeltemtr
Textnow wireless uses a custom os that is slightly modified from the default, I don't know what that entails but i know that affects what fixes may/may not work so i am mentioning it
before i get the same answers i have tried:
redownloading TWRP and flashing the new copy instead in case of corrupted image
removing the battery after flashing and then booting directly into bootloader so as to stop it restoring anything
I have tried flashing other recoverys, however upon doing so found that when i tried to boot into the bootloader it would then boot to Odin instead and give me an error saying it was unable to boot normally, so i reflashed the TWRP one and it gave me the same blackscreen once again.
Any advice would be very helpfull, im at my wits end and id like to be able to recover my phone should it have problems later, id much prefer i not get stuck
Software Version: G360PVPS2APE2
Hardware Version: G360P .03
Model #:SM-G360P
Android Version : 4.4.4
Android Security Patch Level: 2016-06-01
Kernel Version:2.10.28-675169
Build #: TNG360PVPS2APE2
SOLVED
http://forum.xda-developers.com/gal...ime-sm-g360p-root-t3217885/page2#post70113291
I found something that worked highly reccomend this autoinstaller for Odin
Search the forums for stock rooted deodexed sm-g360p, thats the TWRP that I use ... almost to much. The rom is also alot more susceptible to root,mods,and tweaks. The rom is sprint, boosts a sprint partner. Its helped me get the 4glte i couldnt pickup with the boost. But definitely find that post. Twrp isn't official to our variant(that i know yet) but it works the same tho a lil dated.

Bootloader Status, OTA and gapps

Hi.
Can some one help check my Elephone S7 (4G-64GB) bootloader status? I've tried the code and some apps, but the code doesn't work and the apps some don't work while others say "unknown" .
On another subject, stock rom related:
- After installing twrp and the latest stock rom, does OTA still work? I think it should since it's the same rom just a different recovery, but I would like confirmation.
- I don't know why but on my Elephone S7 the google startup wizard doesn't start. I even got the wizard apk, but it installs and doesn't run. So I'm thinking... (maybe I shouldn't ) can we install open gapps using twrp without any problems?
Thanks!

Need Instructions to avoid almost bricking again

Hi guys. I very narrowly (somehow) managed to recover from almost bricking my phone.
I successfully S-Off'd my phone, and previously successfully installed TWRP. I tried to install this ROM:
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
When I tried the to flash the ZIP for firmware and for the ROM, the firmware wouldn't install. I tried some other stuff and basically almost bricked my phone. Some how got it to suddenly start being able to use the htc_fastboot commands (????????) and was able to start installing the zip for stock... but it ran an error, I ran it again and it froze... then I forced my phone to reboot and somehow I'm back to having a stock system. No clue what I did.
My question is, can I take a software update on my phone normally (to 7.0) , and then install just that ROM? Or so I need to flash the firmware separately with a command line command? I just don't want to give myself another heart attack tonight. Current firmware version is 1.82.605.6, not rooted, don't believe my recovery is TWRP right now (but I know how to install that one).
I'm just looking for root access and the ability to remove pre-installed Verizon crap (VZW Messager, My Verizon, etc). Thanks guys.
CritKlepka said:
Hi guys. I very narrowly (somehow) managed to recover from almost bricking my phone.
I successfully S-Off'd my phone, and previously successfully installed TWRP. I tried to install this ROM:
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
When I tried the to flash the ZIP for firmware and for the ROM, the firmware wouldn't install. I tried some other stuff and basically almost bricked my phone. Some how got it to suddenly start being able to use the htc_fastboot commands (????????) and was able to start installing the zip for stock... but it ran an error, I ran it again and it froze... then I forced my phone to reboot and somehow I'm back to having a stock system. No clue what I did.
My question is, can I take a software update on my phone normally (to 7.0) , and then install just that ROM? Or so I need to flash the firmware separately with a command line command? I just don't want to give myself another heart attack tonight. Current firmware version is 1.82.605.6, not rooted, don't believe my recovery is TWRP right now (but I know how to install that one).
I'm just looking for root access and the ability to remove pre-installed Verizon crap (VZW Messager, My Verizon, etc). Thanks guys.
Click to expand...
Click to collapse
I recommend you install this one instead:
https://forum.xda-developers.com/ve...m-1-85-605-9-aroma-root-root-debloat-t3529732
Follow instructions in OP...or:
1)fastboot flash FW w/o Boot w/ TWRP (htc_fastboot oem rebootRUU, fastboot flash zip...)
2)htc_fastboot reboot-bootloader
3) Finally, go into recovery-- backup and flash ROM (choose root w/ Magisk and debloat)
Thanks, I figured out why it wasn't working before. Used official TWRP, thats why it wasn't working. Wouldn't have thought that'd made that much of a difference.
New problem though; something I really would like to use the Google versions of contacts and dialers. Trying to flash those just made my phone app unusable. So I turned to LineageOS but it REFUSES to boot. Hangs on their little vertical line with a moving circle. Found out AOSP roms don't like VZW firmware? Flashed global firmware, updated through WiFi as much as possible, and then ran into issues with radio, even though I flashed the VZW one. So I reverted those changes, am going through with what you said above to have a working phone (after not having one all day), but any advice on getting Google dialer and contacts? I'd like to use LineageOS but I couldn't get it work at all.
CritKlepka said:
Thanks, I figured out why it wasn't working before. Used official TWRP, thats why it wasn't working. Wouldn't have thought that'd made that much of a difference.
New problem though; something I really would like to use the Google versions of contacts and dialers. Trying to flash those just made my phone app unusable. So I turned to LineageOS but it REFUSES to boot. Hangs on their little vertical line with a moving circle. Found out AOSP roms don't like VZW firmware? Flashed global firmware, updated through WiFi as much as possible, and then ran into issues with radio, even though I flashed the VZW one. So I reverted those changes, am going through with what you said above to have a working phone (after not having one all day), but any advice on getting Google dialer and contacts? I'd like to use LineageOS but I couldn't get it work at all.
Click to expand...
Click to collapse
You've got to read OPs, search threads, etc. Some ROMs work w/ our phone, and some do not. Check out the latest versions of ice and leedroid. Your most likely want to grab the SVN versions is the official versions may not yet support Verizon N firmware
Antny6 said:
You've got to read OPs, search threads, etc. Some ROMs work w/ our phone, and some do not. Check out the latest versions of ice and leedroid. Your most likely want to grab the SVN versions is the official versions may not yet support Verizon N firmware
Click to expand...
Click to collapse
I have been doing a lot of searching, but I've found so many different, conflicting sources of information. For example, one website told me to install LineageOS, was to be on latest Verizon OTA and just normally flash it; that obviously didn't work.
So from what I can see, our choices are Viper, Ice, LeeDroid, NuSense and the one you linked. I'm going to try out LeeDroid... out of curiousity, is there any reason, for example, LeeDroid or Ice haven't posted in this Verizon section with links to their ROMs?
*Edit Two* Dialer wouldn't work out of the "box" so to speak, so I had to go to Phone settings at the bottom, there is a menu called Calling Accounts. Had to go there and tap Receive Incoming Calls... why is that disabled in the first place..? But that seems to be an issue going even as far back as the Nexus 5. But that's how you find the option in the HTC 10 for anyone who comes across this issue too...
Not sure why your having issues with the flashing. Are you doing a full wipe? Not just factory reset. Going from stock to lineage requires a complete format of internal SD card. On the stock roms, most will ask if you are still on marshmallow firmware & are working fine. Again, we need more info on what firmware version your on, version of twrp& how your wiping your device. Most AOSP roms work, but no advanced calling
LOS ROMs will work without issue IF you have flashed the US unlocked firmware at some point in time. This is the only information that we have found from a VzW device with LOS booting and VzW device without. We started a thread awhile ago and is the only known method we currently know of to get LOS booting. Also works for Sprint users.
https://forum.xda-developers.com/verizon-htc-10/how-to/how-to-cm-booting-vzw-vzw-firmware-t3500900

SM-G928W8 kernel is not seandroid enforcing and won't detect sim card

Recently I've gotten a new s6 edge+ and of course wanted to get rid of the stock ROM, I've done this with my old s7 but I must have done something wrong because on boot up it says "kernel is not seandroid enforcing". It still boots up and twrp works fine as far as I can tell. I forgot to unlock the bootloader but seeing as how it still works I don't think that's the issue. I've installed RR nougat ROM and installed magisk but now it won't detect any sim card. I'm thinking of trying to flash the stock firmware back and re doing everything but I'm not sure what region to use because it was initially Rogers locked but I unlocked it for bell. Anything else I should try first seeing as it will take about 5 hours to download the stock firmware?
The sim card is the only immediate issue at the moment so help with that would be great.
Edit: The sim card is not the issue, it works just fine in my s7 so it has to be an issue with the ROM right?

Categories

Resources