I have searched the internet for an answer to my problem to no avail. The reason I can not find a solution is that I'm either slow or there is not yet a solution. Had to get that out there. OK here is the issue: I of course have a sprint note 4. I installed twrp and CM 12 official on the third of march. Last night I was up late, bored , and out of my mind. I decided that I wanted to try xposed framework. That went well. Installed a few modules such as Pandora patcher, flat colors, hex clock, call recording for cm, and finally gravity box for LP. Everything was fine after making changes in every module except gravitybox. After I had rebooted my phone to finalize the changes made in GB I had no service. So its recognizing that I'm with sprint and I have service for just a sec when I turn on and off the phone/ airplane mode, but just goes back to emergency calls only. I realize I shouldn't have messed with GB or any other mudules on my note with LP. Things I have tried: I installing the xposed Disabler in twrp, undoing all the changes I made in all of the modules then uninstalling them, restoring my earlier back up, reflashing the stock firmware( although this time it was LP stock), tried to change my network settings(but they are greyed out), and patting my tummy while I rub my head. Please help a brother out. Any help or suggestions would be greatly appreciated. Thank you in advance.
Have u tried ##72786# in dialpad or updating prl and profile on a touchwiz rom then flash cm again but my thoughts on cm are garbage but thats on u
The suggestion above is the first thing you need to try. Second thing is if you have never taken the Lollipop update via ota or odin flash the stock BOB7 rom tar, then that could very well cause issues running Lollipop on KK firmware/modem. You must take the Lollipop update by one of the two methods I just mentioned then you can flash the CM based Lollipop rom and you should be fine in the radio/connectivity department. If you don't or haven't done this already then expect problems. Good luck.
Related
I was running latest paranoid android and I wiped cache/dalvic cache after flashing Cerberus in recovery and when the phone booted up it was asking me to Activate (sprint service) my phone. I've never seen this with flashing roms and was wondering if this is a known issue with flashing roms on the S3 or something that can randomly occur from time to time.
Anyone have experience with this before? I had been running Paranoid Android for less than 24 hours but initially didn't have any problems whatsoever.
Itll do that sometimes depending on the rom. Usually does it after a factory reset and installing a cm based rom. Its just asking you to add your google account... you should be fine
sent from my thumbs
youdoofus said:
Itll do that sometimes depending on the rom. Usually does it after a factory reset and installing a cm based rom. Its just asking you to add your google account... you should be fine
sent from my thumbs
Click to expand...
Click to collapse
This didn't have anything to do with my Google account. I guess I should have been more specific, I mean that my phone is deactivated on Sprint's network as in I can't make phone calls and all the info is missing in about phone. Phone number, PRL and such. I am flashing back to stock right now and hope this fixes it. Will probably give paranoid another go but this doesn't sound like a common issue because I haven't been able to find anything by searching.
When you get back to stock it'll probably reactivate itself. If not (although you can do this regardless just in case), ##72786# in the dialer should set you straight. If I'm not mistaken the screen you're referring to should be gone when you boot stock regardless. Its a bug. Doesn't work for a sprint phone but still buried in the rom
Ahhh... could try manually flashing your modem after the install too
sent from my thumbs
billard412 said:
When you get back to stock it'll probably reactivate itself. If not (although you can do this regardless just in case), ##72786# in the dialer should set you straight. If I'm not mistaken the screen you're referring to should be gone when you boot stock regardless. Its a bug. Doesn't work for a sprint phone but still buried in the rom
Click to expand...
Click to collapse
Soon as I flashed the stock rom it tried to activate and initially failed and prompted me to reboot. Second attempt it was successful and then I immediately flashed back to PA and it is working. Going to give it another shot and keep the stock rom on my sd card this time in case I get stuck in a pinch.
I jumped the gun, phone activated fine but signal drops in and out randomly and will not connect to 3g. Just reflashed to stock again and everything seemed fine but signal was still back in and out. Checked under status and PRL read "0" tried updating to no avail so did the dialer code and it did the activation and all is right in the world again, or at least for the moment.
Just trying to figure out why when I flash Paranoid all my settings just disappear
*edit*
Just flashed back to PA this third time after fully making sure that the phone was working and had 3G data and all was right with the world (my phone). Will update if it goes South again but as of right now the phone is behaving properly. Maybe it just wasn't working right the first time and I didn't notice since I was on wifi. Only thing that keeps me from thinking that is I didn't get the Activation message until 12 hours or so after I had flashed and had been using the phone. /shrug
I still think flashing a modem in recovery after installing PA would yield a poisitve result
sent from my thumbs
youdoofus said:
I still think flashing a modem in recovery after installing PA would yield a poisitve result
sent from my thumbs
Click to expand...
Click to collapse
how do you flash a modem? I am new to this and this is also a problem that I am having with the same rom. I tried searching for a fix and this is where i landed.
Thank you,
and sorry if i am breaking forum rules
Can anyone help with this. I have a sprint note 4 that I rooted and was working great, but wanted the stock 5.0.2 upgrade. Used odin to install stock 4.4.4 and remove root. Worked fine phone took the 5.0.2 upgrade. Rerooted and installed wifi tether router but could not get it to work, found it is not working on 5.0.2, dam. Used odin once again to return to stock 4.4.4, rooted, installed wifi tether, everything works with one problem. When turning the screen on I now have a severe lag between the button push and the screen light up.
I odined back for other issues and still had problems. .even a backup was not working... i wiped everything, all data etc, 2 times then went back to nie....then took the otas back to lollipop. .now everything works fine except i still hate the colors
Sent from my SM-N910P using Tapatalk
Fixed, it was a bad sd card had nothing to do with the dowgrade.
Good to hear you found your problem. However if it's tethering that's keeping you away from Lollipop then you can put that to rest because you can easily enable wifi/usb tethering without the need for a third part app like tether router (which i have payed for as well). If you expect to stay on the factory rom/firmware then Lollipop would be a wise choice due to the new ART (android runtime) and it's overall effeciency compared to KK . It has a lot of benefits and other than the stock colors, there's no reason you shouldn't update to Lollipop. Do a little searching here in the Sprint Note 4 forum and you'll find a few easy ways to enable the built-in tethering.
Thanks for the info, did exactly that, found galaxy tools would provide the tether
Downgrade help
Hey
I need some help downgrading my phone from LP 5.02 OE1 update
I have no service and need to re unlock
What files did you use?
Can you send me a link. Odin fail with everything
badgal said:
Hey
I need some help downgrading my phone from LP 5.02 OE1 update
I have no service and need to re unlock
What files did you use?
Can you send me a link. Odin fail with everything
Click to expand...
Click to collapse
You are SOL for now. Cant downgrade rom OE1, but a new OTA is about to come out, I'd sit tight until then. or...Many people flash Noterized Rom. Try flashing that and continue your troubleshooting.
Stuck
Here is my screen
Hi folks. Admitted Noob here asking for help.
[backstory]
After many years resistance I finally decided to get a phone. Freedompop's free plan was enough to push me over the fence. Found a nice S3 (L710VPUDOH1) on ebay and bought it. Everything was fine...except the stock rom had so much crap in it I was about to have a seizure. Back in the day I had put CM on a nookcolor so I thought that was the way to go. I consulted with a friend who assured me that CM played nicely with freedompop so down the rabbit hole I went.
[the first sign of trouble]
Installing CM went fine. Odin. Heimdall. I installed the latest clockwork mod touch recovery (6.0.4.5). Then I installed the latest CM snapshot (cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2spr.zip) and the appropriate gapps. Worked great. Nice and fast, good configuration options, no bloat....but it couldn't connect up to the 3g/4g network. Freedompop worked as long as WiFi was on and would not otherwise. Crap. What's the point of a cell phone if I have to have a WiFi hotspot???
Some googling revealed that the APNs were wrong so I tried that route. I was able to get LTE working but never got 3G. I live out in the boonies, so 3G is kinda important. Also found that CM breaks Sprint's PRL auto update which doesn't seem too happy.
[^H^H^H^H^H]
So, I decided to go back to the factory ROM and see how FP worked as I dutifully made a backup before installing CM. Now the SHTF. When I restore from backup in CWM (followed by a factory wipe data and cache to avoid the boot loop) the ROM cannot connect to Sprint's network. Doesn't know its IEMI or much of anything. It does connect up to wifi, log into my google account, get my paid apps, etc....but still no phone.
I installed Kies and attempted to restore/upgrade firmware (non-emergency mode). Kies got to about 66% and said there was an unexpected error. I'm guessing it didn't like the custom recovery and just plain quit on me. Was worried that I'd made a brick but alas I could still get to download mode. </bullet dodged>
I would like to put the phone back to stock (including recovery) but I have no factory recovery image. Does anyone have a recovery image for L710VPUDOH1? Alternatively, is there any harm in flashing the full ND8 onto the phone even though it had OH1 running before? I seem to remember reading things about bricking phones when trying to downgrade....which is in effect what I would be doing.
Any other suggestions about how to get back to stock would be most appreciated.
TIA
You can flash nd8. Nj2 is newer though. I don't think anyone has captured the oh1 tar yet. The only thing you should not do is flash anything before nd8 (pre Knox) like mk3 or older. Which is jellybean anyways so....
Hope this helps.
Yes, thank you; that was exactly what I needed to know.
I have a working phone at the moment so stock is not necessary required. For others that may be interested I flashed in Wicked X 8.2. From there the phone once again knew its IMEI and I was able to carrier reset and get it activated with Freedom Pop.
I've done a lot of digging through the forum and can't find an answer, so forgive me if this is an already-answered question.
I have a T-mobile S4 with a camera stuck on the classic "updating camera firmware" error message with black screen. If I open Snapchat the front facing camera will work, but with a slight delay in projection.
Here's the thing...this has happened on two separate phones now and on both of them it happened about 48 hours after I signed into the phone with my google account. Is it possible there is some kind of malware attached to my google account?
In the newest phone I have done a clean full wipe using TWRP, then Odin-flashed a full firmware package I found here on xda (recovery, OS, modem, kernel). Cache wipe and factory reset immediately after rebooting from Odin mode. Still have problem.
Have switched out known good cameras from other phones, and the phone I'm working on was functioning perfectly until I signed into it with my account. Totally stumped here, and really need some assistance.
Phone is:
M919 logic board in I337 body
Kitkat 4.4.4
Baseband: M919UVUFNH7
Kernel: 3.4.9-6281449, [email protected] #1
Build: KTU84P.M919UVUFOK3
Security software version: MDF v1.0 release 3, VPN v1.4 release 2
If anybody's got some ideas, please let me know!
Ok, no answers yet but plenty of views, so either this is an extremely rare issue that no one knows a solution for, or it's a ridiculously stupid question that everyone knows the answer to. I'm going to try and keep a log of what I'm doing with this phone in case any other rookies need assistance in the future.
So far I've flashed three different versions of stock Kitkat onto the phone....OH3, OK3 and NH7. When I flash OK3 my build number doesn't match my baseband (baseband reads NH7)...not sure what's going on there. Also, if I flash OK3 I lose my wifi....do not have this problem with other versions of firmware. Each flash is done after a full clean wipe with TWRP.
I found a thread that mentions an almost identical camera issue being caused on an M919 that was flashed with Nottache Xposed framework for AT&T phones. The OP said they could fix the issue by wiping the framework off the phone. Since my M919 motherboard is installed in an I337 body, I'm wondering if this is something related to a compatibility issue between T-Mobile and AT&T components. Best lead I've got so far.
Two posts have mentioned a fix. One says he opened Google Edition Camera Photosphere and his problem went away. He was running a different machine than mine so I haven't tried this yet, but I'm doubtful. The other user said they have only been able to solve the cam issue by installing a stock modded kernel by @jovy23. All the links I've found to this kernel are dead now, so no dice there.
I'm gonna put my M919 motherboard into an M919 body, wipe and flash stock rom again and see if somehow that does anything.
As a side note, I started getting "SIM not inserted" errors just before I began flashing different roms, and since the initial flash I've lost my SIM completely. So now I've got no camera, no SIM card being read, and sometimes losing wifi. I need this phone for work, so this is kind of sh*tty.
You cant downgrade once youve updated to OK3. The order would have to have been NH7, OH3 then OK3. It seems like mabey its not flashing correctly. Try a different odin program 3.04 3.07 3.09 are good ones. Flash it twice, untick auto reboot and manually power off and back into download mode and flash again. Dont use adv reboot menu to boot into download or it may not flash correctly. If that doesnt work I'm not sure what else to try. Good Luck
Ok, latest update for future readers...
It seems that lordodin912 is right when he says that flashing to OK3 means you can't flash backwards to a previous baseband/build. I hadn't seen that info anywhere so I didn't know about it. I'm not sure how to go about finding this kind of info on the forum but it would have been nice to know ahead of time. Anyhow...thank you for that information lordodin.
Here's where I'm at now:
-I was originally on NH7 with the camera error and sim card error. Flashed NH7 full stock after doing a full wipe and still had problems.
-Flashed OK3 full stock after full wipe and still had the problems, and also lost wifi capabilites (as in the phone wouldn't turn on wifi at all). At this point the baseband read as NH7 but the build read as OK3. I don't know why.
-Tried flashing OH3 after that (didn't know any better) and it wouldn't take. At this point wifi capabilites returned but still no cam and not reading sim card.
-Flashed OK3 again and wifi returned but still no cam and no sim. A couple hours later I powered the phone off and then back on, and Samsung then notified me of OTA updates. This update notification hadn't appeared before I manually rebooted the phone. I took the updates and now have wifi, sim card is being read, and my camera appears to be functioning properly as well. About 20 minutes or so after the updates are applied, the sim card error returned and told me to restart the phone. I did so and now the phone is reading the sim card again.
Right now my best guess is that when I was on NH7 I had accidentally made some app and update settings changes that prevented me from receiving some of the important OTA updates connected to camera and sim functioning, and this caused incompatibility between certain parts of the firmware that had been updated and others that had not. Trying to flash OH3 failed to solve the issue because I had already flashed OK3 before that and you can't go backwards from OK3. I don't know why the initial OK3 flash failed to fix anything, but I'm guessing the flash just didn't take as well as I thought it did. Flashing OK3 twice in a row seems to have done the trick, I presume because it reset and updated everything so that all firmware was compatible with itself.
I don't know how this could have happened (I try to be very careful about what I freeze and uninstall), but it's the most likely culprit because after flashing the latest firmware manually (twice) and allowing OTA updates my phone returns to proper function. Why OK3 didn't work correctly at first is beyond me....I don't see why it should have taken a few hours or a second reboot for OK3 to begin offering updates but whatever.
I'm doubtful that the camera will continue to work after the next 48 hours, but we'll see. I'll report back in with what happens after a few days go by.
Leaving an update here as I said I would.
For two months the phone has been functioning properly. Camera, sim and wifi have all been good. About one week ago my camera started acting glitchy again and then stopped working. The problem is the same as before- upon opening camera app the screen is black with a message saying "updating camera firmware", then nothing happens. This occurred around the same time I started using google hangouts frequently...don't know if that is related to the issue or not.
Yesterday the phone began showing the error message about sim card not being read, and then today it stopped reading the card altogether.
I repeated the same procedure that seemed to fix these problems two months ago and it hasn't done the trick. Full clean wipe of phone using TWRP, then installation of Chainfire's Autoroot, then flashed OK3 stock firmware twice with battery pulls between installations. Factory reset immediately after install of stock ROM. When connecting to wifi, no OTA updates appear. Camera not functioning, sim card not being read.
Phone shows baseband and build number are matching. I have no ****ing idea what the problem is with this phone. Beyond frustrated.
Anyhow, I'll keep updates going as long as I am working with this thing, maybe it'll help someone later. Anyone knows anything that could help, feel free to chime in.
I'm looking for an S7E/N5 hybrid with mostly everything working. Coming from a N3, this would be a Dark Lord ROM with fingerprint and NFC.
I started with a stock BPA1 phone which I unlocked/rooted. I wanted to upgrade to a true 6.0.1 ROM which meant upgrading firmware. I started with Odin flashing a tar.md5 of the CPD1 firmware - bad idea. It failed and messed up the bootloader. So broke phone.
I was able to Odin the stock BPA1_BPA1 and the BPA1_CPD1 firmwares. In each case though, it was very hard to obtain root. If it rebooted or locked up for any reason, I had to go back and reflash the stock firmware, wipe and reinstall kingoroot. Otherwise I was stuck in a bootloop with DL Mode saying I was locked. This is what lead me to fix it. I noticed after the first flash of samsung_unlock_n4-fix (root took that time and no crashes) it would bootloop. I went into DL Mode to reflash firmware but it finally showed Developer Mode. I gave it a shot and flashed twrp without issue. Instead of having to install the n4-fix twice or go through multiple roots, turns out that it took just took once to reclaim Dev Mode.
(I had been thinking that Dev Mode was wiped out with aboot when flashing the stock BPA1. Guess not)
So the bootloop I figured was due to a kernel issue. With Dev Mode, I Odin flashed TWRP. I formatted my sdcard and put a kernel on it, using twrp to flash it. And tada, working phone. This worked on both the BPA1_BPA1 and the BPA1_CPD1. So I was able to load the 6.0.1 firmware. It took so long to do this though that I didn't get a chance to try more than a few roms.
From a brief visit to these ROMs, I am still looking for something that has everything:
From T-Mobile:
Maximum OvrDrive 6.0.1 MM v.8 - Great ROM but I didn't have wifi afterloading it. I'm sure I was missing something to get it to work but I realized this was not an S7E port either.
Maximum OvrDrive S7 v3.7 - It's a 5.1.1. ROM and works well but is missing AOD, fingerprint and most importantly hotspot.
General forum:
Dr.Ketan 6.1.1 - could not get this to load. It bootlooped after flashing the M5 rom (910g?), kernel, datafix and supersu as per instructon. Will revisit.
Verizon forum:
Kyubi Note 5 Port - One of the first ROM I tried and it is amazing. This is a very stable ROM with almost all the bells and whistles. I wouldn't even look at another ROM except it doesn't offer AOD and a few minor tweaks (haven't figured out how to skin my status bar clock for example). I posted in the thread a fix for MMS btw. It's a 5.1.1 ROM of course and lacks in a few ways.
I'm still looking for a perfect ROM for me. Will update the list as I try them.
I flashed the Noble ROM yesterday. So far, so good.
If you get time this rom by @aukhan and the Emotriod team is great. It's a pure note 4 with edge features, but I can't remember if mobile hotspot works or not. I'm using the Nameless Rom at the moment and really enjoying it as well. On the Nameless Rom mobile hot spot works, I'll check to see if fingerprint works, everything else as far know works well. One more option is Kurama Rom, I got it to boot with data/mobile/wifi, but to be honest I didn't stick with it too long because as soon as I got it set up, the Emotriod Rom caught my eye and I just had to have it.
douger1957 said:
I flashed the Noble ROM yesterday. So far, so good.
Click to expand...
Click to collapse
Hahaha....I've been on Noble for a few weeks now, and just flashed hsbadrs cm13 7.17. release for a change. Noble is a beautiful rom, and I themed it with Marshmallow dark theme from the Samsung theme store. CM13 is just slightly more fluid, and used to be my favorite, Noble is by far the most stable s7 port on my phone.
Sent from my SM-N910V using XDA-Developers mobile app
Dr Ketan rom you need to flash rom then m5 fix right away let it boot (can take up to 11 minutes no longer average 5-6) dont sign into anything ( google, samsung, etc.) then go back into recovery and flash louforgiveno's data fix for your bootloader and ketan rom. then reboot. It has to be a clean flash in my experience. It will take about 5 minutes to get data signal but it comes. The roaming indicator off text stays on lock screen it does not mean you are roaming though (check in about device), there is a way to get rid of it but i didn't doesnt bother me.
Does anyone know if there is a way to add Wifi calling to any of the N910F roms?
UPDATE: I went back to Ketans Rom but on the BPA1 bl and it works very nicely. I had to utilize my MMS fix to get the native app to send mms. I'm currently working on finding an Xposed framework that boots. Neither Wanam mod's or the stock seem to fit. Ketens is so far the most kitted out N5/S7E rom I've seen, with even a cobbled together version of AOD. Anyone have any luck with Xposed running the H Vitamin kernel? I'm thinking of switching to some other kernel to see how it works.
kevintm78 said:
If you get time this rom by @aukhan and the Emotriod team is great. It's a pure note 4 with edge features, but I can't remember if mobile hotspot works or not. I'm using the Nameless Rom at the moment and really enjoying it as well. On the Nameless Rom mobile hot spot works, I'll check to see if fingerprint works, everything else as far know works well. One more option is Kurama Rom, I got it to boot with data/mobile/wifi, but to be honest I didn't stick with it too long because as soon as I got it set up, the Emotriod Rom caught my eye and I just had to have it.
Click to expand...
Click to collapse
Just curious what kernel and data fix are you using with the emotroid rom. I have tried Lous MMs fix v4 and also the 3b version but MMS is all not working properly.
Is there anything wrong with the mm bootloader? Seems like a lot of ppl Including me is having trouble flashing roms on it. So we Convert back to the lollipop bootloader... How can we get roms to work on the mm bootloader. I can't find any reason to this.