Has anyone else had an issue where the Samsung Camera App won't focus on Stock (Samsung) Roms? I don't have the problem with AOSP Roms...which is sooooooooooooo weird. Doesn't make any sense to me. I have tried NSeven Rom, Stock Rooted Rom (no mods), MODest Rom...they all have the same issue. However, the issue doesn't exist on LineageOS, EmotionOS, and I am sure it wont be a problem in Resurrection Rom either (haven't tried yet). I have tried to install a 3rd party Camera app and it does the same thing. Blurry and Wont Focus.
Balian67 said:
Has anyone else had an issue where the Samsung Camera App won't focus on Stock (Samsung) Roms? I don't have the problem with AOSP Roms...which is sooooooooooooo weird. Doesn't make any sense to me. I have tried NSeven Rom, Stock Rooted Rom (no mods), MODest Rom...they all have the same issue. However, the issue doesn't exist on LineageOS, EmotionOS, and I am sure it wont be a problem in Resurrection Rom either (haven't tried yet). I have tried to install a 3rd party Camera app and it does the same thing. Blurry and Wont Focus.
Click to expand...
Click to collapse
I've heard of kernels effecting camera before. What stock ROM are you on? And did you flash a custom kernel with it? If so, that might have something to do with it.
dhplap said:
I've heard of kernels effecting camera before. What stock ROM are you on? And did you flash a custom kernel with it? If so, that might have something to do with it.
Click to expand...
Click to collapse
I will just say that I started unmodded on the newest version released by Verizon (locked bootloader..etc). i did the rollback and unlocked the bootloader. Camera worked. EVERY TouchWiz Rom I flash has this issue. WITH the kernels included with the roms. I haven't flashed custom kernels yet. That is why I think this issue is weird. I just flashed Resurrection Rom which is AOSP and Camera focuses and works. I've never experienced this kind of weirdness before.
Balian67 said:
I will just say that I started unmodded on the newest version released by Verizon (locked bootloader..etc). i did the rollback and unlocked the bootloader. Camera worked. EVERY TouchWiz Rom I flash has this issue. WITH the kernels included with the roms. I haven't flashed custom kernels yet. That is why I think this issue is weird. I just flashed Resurrection Rom which is AOSP and Camera focuses and works. I've never experienced this kind of weirdness before.
Click to expand...
Click to collapse
So you're on the CPD1 bootloader?
dhplap said:
So you're on the CPD1 bootloader?
Click to expand...
Click to collapse
quite possible. When I boot into download mode it doesn't say. In settings/about phone it only shows baseband. Im sure there is a command but I am not sure what it is.
**EDIT** I found phone info on the playstore. I am on bootloader Version: N910VVRU2BPA1 PDA Version: N910VVRS2CQB2 Baseband Version: N910VVRS2CQC1
Balian67 said:
quite possible. When I boot into download mode it doesn't say. In settings/about phone it only shows baseband. Im sure there is a command but I am not sure what it is.
**EDIT** I found phone info on the playstore. I am on bootloader Version: N910VVRU2BPA1 PDA Version: N910VVRS2CQB2 Baseband Version: N910VVRS2CQC1
Click to expand...
Click to collapse
That's probably the problem, you're still on the lollipop bootloader. You need to upgrade to the CPD1 bootloader and unlock it again from this page https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144 that hsbadr supplied for us. Since you're already unlocked on BPA1 you'll only need to do it one more time. In the instruction section you can start at the second step though. Just remember, after you flash the N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 You're wifi won't work so you'll need to use data for rooting. After you complete all of the steps successfully you should be good to go and do another clean flash of the marshmallow ROM of your choice.
Just want to say I'm on PD1 with a stock rom and kernel and have had this same problem since I've gotten to Marshmellow last year. I've just kinda accepted it at this point.
dhplap said:
That's probably the problem, you're still on the lollipop bootloader. You need to upgrade to the CPD1 bootloader and unlock it again from this page https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144 that hsbadr supplied for us. Since you're already unlocked on BPA1 you'll only need to do it one more time. In the instruction section you can start at the second step though. Just remember, after you flash the N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 You're wifi won't work so you'll need to use data for rooting. After you complete all of the steps successfully you should be good to go and do another clean flash of the marshmallow ROM of your choice.
Click to expand...
Click to collapse
I will keep this in mind. I am currently on Resurrection Rom and I have ZERO issues. I don't want to mess with it. When I start to mess with stuff is when I spend 12 hours fixing something that should have only taken an hour to do to begin with. As the comment below you said...he has the same camera issue on CPD1
bagery77 said:
Just want to say I'm on PD1 with a stock rom and kernel and have had this same problem since I've gotten to Marshmellow last year. I've just kinda accepted it at this point.
Click to expand...
Click to collapse
It is literally the most weird issue I have had....It's usually the AOSP camera that is crashing...or crappy pictures...but ever since unlocking the bootloader the camera got blurry. I don't get it. Resurrection Rom has been killin it for me though. I love it. I might stay on it forever.
Balian67 said:
It is literally the most weird issue I have had....It's usually the AOSP camera that is crashing...or crappy pictures...but ever since unlocking the bootloader the camera got blurry. I don't get it. Resurrection Rom has been killin it for me though. I love it. I might stay on it forever.
Click to expand...
Click to collapse
I don't like shopping around too much these days. But the focus problem does clear up after several seconds. Always. So that's made it tolerable for me.
bagery77 said:
I don't like shopping around too much these days. But the focus problem does clear up after several seconds. Always. So that's made it tolerable for me.
Click to expand...
Click to collapse
It never cleared for me. I have sat on the camera for a minute tapping to focus...waiting...etc
Balian67 said:
It never cleared for me. I have sat on the camera for a minute tapping to focus...waiting...etc
Click to expand...
Click to collapse
Hmm, maybe Redemption/AOSP is your best bet. I just know it sucks to not have options still. Perhaps someone will pipe in with the magical fix. Good luck
I do agree with dhplap, you need to be on the Marshmellow bootloader if you're flashing stock Marshmellow roms. I can't remember all the stuff it breaks not having it, but I recall quite a few posts stating issues that were fixed by rerooting and updating the bootloader. Until they did that, they remained limited. AOSP Marshmellow seemed to work for them for some reason, however stock/Touchwiz "Marshmellow" broke stuff. Since you're on Lollipop bootloader, a stock Lollipop rom may remedy the camera issue for you.
bagery77 said:
Hmm, maybe Redemption/AOSP is your best bet. I just know it sucks to not have options still. Perhaps someone will pipe in with the magical fix. Good luck
I do agree with dhplap, you need to be on the Marshmellow bootloader if you're flashing stock Marshmellow roms. I can't remember all the stuff it breaks not having it, but I recall quite a few posts stating issues that were fixed by rerooting and updating the bootloader. Until they did that, they remained limited. AOSP Marshmellow seemed to work for them for some reason, however stock/Touchwiz "Marshmellow" broke stuff. Since you're on Lollipop bootloader, a stock Lollipop rom may remedy the camera issue for you.
Click to expand...
Click to collapse
I am so busy lol. I have 2 Sprint Note 4's that I am trying to root and I ran into ODIN/USB Driver issues. MAYBE I will worry about this next weekend haha. I will keep all this in mind. I will keep this post till then.
Thanks everyone.
I wanted to report that after I did all that stuff yall said, I restored my MODest Rom backup and the camera is now focusing. Maybe that will fix all the other issues with the other roms I tried using. I appreciate it Gents.
Related
My note 2 has always been stable on 4.1.1 stock and I debloated it myself. So when ever an update came out rather than risking my stable phone I would just flash the new baseband from it and keep 4.1.1, until tesh stopped updating his thread. Recently my screen cracked so I used my insurance for the first time. The new phone came with 4.3 and the knox bootloader plus the CMK7 baseband. I did a cwm backup on my cracked screen phone. Used odin to flash cwm onto the new phone, which did cause knox to show I did but who really cares since the phone is so far out of warranty anyway. Then loaded my cwm backup onto the new phone. What I ended up with is my nice stable phone with everything working plus the new baseband CMK7 stayed but the bootloader is still the new knox one. Everything is working just fine, so whats the big thing with everyone saying you cant go back from 4.3? I went from 4.3 to 4.1.1 just fine via cwm.
Cool story bro
Joe333x said:
My note 2 has always been stable on 4.1.1 stock and I debloated it myself. So when ever an update came out rather than risking my stable phone I would just flash the new baseband from it and keep 4.1.1, until tesh stopped updating his thread. Recently my screen cracked so I used my insurance for the first time. The new phone came with 4.3 and the knox bootloader plus the CMK7 baseband. I did a cwm backup on my cracked screen phone. Used odin to flash cwm onto the new phone, which did cause knox to show I did but who really cares since the phone is so far out of warranty anyway. Then loaded my cwm backup onto the new phone. What I ended up with is my nice stable phone with everything working plus the new baseband CMK7 stayed but the bootloader is still the new knox one. Everything is working just fine, so whats the big thing with everyone saying you cant go back from 4.3? I went from 4.3 to 4.1.1 just fine via cwm.
Click to expand...
Click to collapse
If you use PC Odin to go backwards there are uncomfortable results.
Hastily spouted for your befuddlement
Double0EK said:
Cool story bro
Click to expand...
Click to collapse
How many of your posts are worthless? All of them? You sir are whats wrong with xda. The fact that every one thinks you cant go backwards from 4.3 just got proven wrong as long as you do it with cwm and not odin apparently.
There are multiple threads regarding your cool story.
The issue people are having is not being able to downgrade to 4.1.x OS. Its the bootloader that people were discussing and when coming from a 4.3 bootloader is impossible to downgrade to the 4.1.x bootloader/s.
Maybe doing a search in the future will get you some answers about the whole 4.3 bootloader and downgrading that you're taking about.
Good luck to you..
Ok but like I said I have the 4.3 bootloader and a 4.1 rom with no issues using cwm. So there is no issue with having a 4.1.1 rom and the 4.3 bootloader. If you have nothing constructive to add then dont post anything.
I mostly Lurk on XDA, But you sir are a different kind of stupid.
Clearly you haven't played with 4.1 long enough to see what the issues are, Its been well known that you can return to a older rom.
but knox has issues by doing so.
Joe333x said:
Ok but like I said I have the 4.3 bootloader and a 4.1 rom with no issues using cwm. So there is no issue with having a 4.1.1 rom and the 4.3 bootloader. If you have nothing constructive to add then dont post anything.
Click to expand...
Click to collapse
smokeingit said:
I mostly Lurk on XDA, But you sir are a different kind of stupid.
Clearly you haven't played with 4.1 long enough to see what the issues are, Its been well known that you can return to a older rom.
but knox has issues by doing so.
Click to expand...
Click to collapse
Lol long enough? How about since release day when I bought it? My phone is stable as can be with no force closes completely self deblaoted, working wifi tether, bunch of xposed modules and everything is pefect. For the most part the OS that a phone releases with is typically the most stable, there are obviously exceptions but I have been doing this since the G1 days and as soon as you start getting flash happy is when you have issues. Only thing I update is the baseband/modem. Also dont name call over the Internet its childish but then again most people on here are typically teenagers. Could you elaborate on the issues knox should be causing me but isn't?
This topic has been mentioned many times, there's no room for the useless bickering going on in here.
Thread closed
Have a great day!
I have had several issues with the 4.4.2 OTA update on my I747 . The most annoying is the battery drain and "hot phone syndrome" which apparently is a bug related related to the camera daemon. Details can be found here http://tinyurl.com/KK-Batt
My goal is to throw 4.4.2 in the bit bucket and go back to stock 4.3 (when life was perfect), however I am leery of the older ROM's running on the newer NE4 bootloader and modem. I have done much reading on XDA for the past week (scortched eyeballs) but haven't found a 4.3 ROM that gives me any confidence ( they all state specifically to flash the MJB or MJ2 level firmware)
Has anyone sucessfully accomplished running 4.3 on the new NE4 bootloader / modem ?
I read a post from @DocHoliday77 that said this "should" be possible .....but I cannot afford a brick. The phone is my ISP, as I have no cable or DSL available , just a mediocre LTE signal from ATT (for which I am grateful)
I am considering this ROM http://forum.xda-developers.com/showthread.php?t=2504903
Thanks for any info or suggestions that you may have
You can flash any ROM you like as long as the ROM does not attempt to flash a new bootloader or modem.
The reason many ROMs require the 4.3 bootloader and modem is the fact that the ROM requires these two things to function properly.
audit13 said:
You can flash any ROM you like as long as the ROM does not attempt to flash a new bootloader or modem.
The reason many ROMs require the 4.3 bootloader and modem is the fact that the ROM requires these two things to function properly.
Click to expand...
Click to collapse
Thanks for the response audit13 , that all makes perfect sense ..... I was hoping maybe someone out there had suffered the same plight and tried this solution.
I read that the problem won't be corrected until android "L" (they attempted to fix it in 4.4.3 but failed). To me this is like Ebola for Android so I don't understand the lack of urgency by Google to correct it ??? Also, one would think a developer would have suffered this plague and been motivated to fix it.
This is not necessarily a Google problem. Samsung ROMs use Samsung kernels, not stock Google kernels.
Samsung is on 4.4.2 while custom ROMs are at 4.4.4.
audit13 said:
This is not necessarily a Google problem. Samsung ROMs use Samsung kernels, not stock Google kernels.
Samsung is on 4.4.2 while custom ROMs are at 4.4.4.
Click to expand...
Click to collapse
Yes but the problem exists in the Nexus line as well, looks like Sam inherited it in the source code. I have thought about trying a different kernel , but IDK if the problem is with the kernel or the daemon or a combination of both.
@audit13 since I am mostly a NOOB here maybe you can help me. I am about to try a custom ROM but am leery that they may mess with my bootloader and modem (NE4) is that possible or typical when you flash a ROM? or do they always state it if they do?
I was running the latest version of Liquid Smooth 4.4.4 and never experienced excessive battery drain or a hot phone on my Nexus 4. After a few days, I installed a custom kernel and my battery life improved but not by very much. Maybe I have been lucky with my Nexus 4. I tried Android L on my Nexus 4 for a while but didn't like the interface. Again, battery drain did not appear excessive on L.
I Don't have KK on my s3 as it is running 4.3 bootloader and modem with a custom ROM.
It is possible that a custom ROM will attempt to flash a bootloader or modem but I have never seen this happen other than a couple of ROMs for a Nexus 4. To ensure that a new bootloader/modem is not going to be flashed to your phone, make sure you look at the first few posts for instructions and warnings.
audit13 said:
I was running the latest version of Liquid Smooth 4.4.4 and never experienced excessive battery drain or a hot phone on my Nexus 4. After a few days, I installed a custom kernel and my battery life improved but not by very much. Maybe I have been lucky with my Nexus 4. I tried Android L on my Nexus 4 for a while but didn't like the interface. Again, battery drain did not appear excessive on L.
I Don't have KK on my s3 as it is running 4.3 bootloader and modem with a custom ROM.
It is possible that a custom ROM will attempt to flash a bootloader or modem but I have never seen this happen other than a couple of ROMs for a Nexus 4. To ensure that a new bootloader/modem is not going to be flashed to your phone, make sure you look at the first few posts for instructions and warnings.
Click to expand...
Click to collapse
Thanks for the feedback @audit13 much appreciated ...... I feel better now. I think I will try upgrading first since there has been no specific feedback on downgrading and my gut tells me it may not be the best idea SlimKat 4.4.4 looks interesting.
Hopefully you will not see a post from me in the future that starts with HELP !!!
I also have never seen a rom that flashes the bootloader or modem. Doing so would be a HUGE mistake!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
I also have never seen a rom that flashes the bootloader or modem. Doing so would be a HUGE mistake!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
@DocHoliday77 ....... Thanks Doc
After taking the APH1 update on my phone, I can no longer downgrade to PG5, and I also can't flash the PG9 U firmware. I don't know what Samsung/Verizon did, but it's ridiculous.
I'm now stuck on the APH1 firmware and can't get on the U firmware at all.
I haven't tried rooting, but there is no Odin firmware for APH1 yet, so I'm not going to try until there is, so that if I mess up my phone I can fix it.
FoxyDrew said:
After taking the APH1 update on my phone, I can no longer downgrade to PG5, and I also can't flash the PG9 U firmware. I don't know what Samsung/Verizon did, but it's ridiculous.
I'm now stuck on the APH1 firmware and can't get on the U firmware at all.
I haven't tried rooting, but there is no Odin firmware for APH1 yet, so I'm not going to try until there is, so that if I mess up my phone I can fix it.
Click to expand...
Click to collapse
It probably incremented the bootloader. I upgraded to it because I am just losing interest in root all together. Somebody will chime in with a more technical explanation.
DarkMidnight said:
It probably incremented the bootloader. I upgraded to it because I am just losing interest in root all together. Somebody will chime in with a more technical explanation.
Click to expand...
Click to collapse
Agreed. For some reason I just don't really care about rooting the S7. Maybe I've just rooted too many phones and lost interest.
nynativ said:
Agreed. For some reason I just don't really care about rooting the S7. Maybe I've just rooted too many phones and lost interest.
Click to expand...
Click to collapse
For me a lot of it is this is not the most conventional root, not very stable for me and battery life suffered a lot compared to stock, and flashing U firmware has not been very cooperative for me.
So thoughts.... I am on the latest U firmware on my 930V. Should I consider flashing back to the stock Verizon rom? Everything is working great. I do plan on jumping ship from Verizon in the next year or so. I am blown away at how well this phone runs stock and only flashed the U in preparation to take it to another carrier afterwards. Is this a bad idea?
Tried to live with root, but the battery and stability was horrible. Now, I am using the engboot to do any data back up or restore tasks in TiBU then flashing the AP again to unroot. Data is maintained, but now I have to live with ads. I use adguard, by it feel like it hurts battery life. Will try and quantify that soon.
Being able to count on my phone to make a call and hold a charge is too important to me. Rooting the phone to set it up after a reset saves me time. Unfortunately, rooting with our current method is too prohibitive for daily use.
nynativ said:
Agreed. For some reason I just don't really care about rooting the S7. Maybe I've just rooted too many phones and lost interest.
Click to expand...
Click to collapse
Same here.
I have a 930U that I use on Verizon. I use the 930V firmware because I like having visual Voicemail. I have rooted 3 different times and gone back to stock everytime. I suppose it because of the engineering kernel but root with the S7 is just not stable. The battery life sucks and you have to do so many things to fix the lag it has just become not worth it. Also the 2 latest updates from Verizon have been good on battery. I do like not having Verizon logos all over my phone.
nrage23 said:
I have a 930U that I use on Verizon. I use the 930V firmware because I like having visual Voicemail. I have rooted 3 different times and gone back to stock everytime. I suppose it because of the engineering kernel but root with the S7 is just not stable. The battery life sucks and you have to do so many things to fix the lag it has just become not worth it. Also the 2 latest updates from Verizon have been good on battery. I do like not having Verizon logos all over my phone.
Click to expand...
Click to collapse
Give stang5liter rom a whirl. Been on it since it was released and have no issues besides nearby devices not working for me.
craazy82013 said:
Give stang5liter rom a whirl. Been on it since it was released and have no issues besides nearby devices not working for me.
Click to expand...
Click to collapse
Been using the same ROM for almost a week with xposed and everything is fine. I feel great without seeing the ads again. haha! BTW, I didn't try the nearby devices so no comment on that.
I have the G930V and am running APH1 with root no problems. The lag was horrendous but after changing the CPU governor to "interactive" on BOTH CPU's (little and BIG) it's been running smooth. I'll run like this for a bit... but stang5liter looks like it will be my next move.
Has anyone with ph1 tried flashing another rom such as stang5litre?
dBunny said:
I have the G930V and am running APH1 with root no problems. The lag was horrendous but after changing the CPU governor to "interactive" on BOTH CPU's (little and BIG) it's been running smooth. I'll run like this for a bit... but stang5liter looks like it will be my next move.
Click to expand...
Click to collapse
So how did you root if you can't downgrade like the OP stated?
craazy82013 said:
Has anyone with ph1 tried flashing another rom such as stang5litre?
Click to expand...
Click to collapse
Yes it works just fine.
bart77 said:
So how did you root if you can't downgrade like the OP stated?
Click to expand...
Click to collapse
PH1 doesn't break root. You just can't downgrade to older firmware's or flash any U firmware's. PH1 is still completely rootable.
So you can't Odin flash back to a stock image if you get in trouble or want to unroot. I guess I'll stay on PG5 for now.
I'm not rooted now, but was able to disable system update notifications using
https://play.google.com/store/apps/details?id=com.hecorat.packagedisabler
By disabling:
System updates (com.samsung.sdm)
System updates (com.samsung.sdmviewer)
and securitylogagent
FoxyDrew said:
PH1 doesn't break root. You just can't downgrade to older firmware's or flash any U firmware's. PH1 is still completely rootable.
Click to expand...
Click to collapse
Thanks @FoxyDrew for clarifying that... and I agree.
I used the following GUIDE to root APH1 on my S7 Flat: http://forum.xda-developers.com/verizon-s7-edge/how-to/verizon-root-knox-t3410624
Im somewhat confused. Your saying you cant downgrade from ph1. Are you talking only with odin? Reason i ask is stang5litre rom is APE1. And as was stated a few posts up, this rom can be flashed on rooted APH1. Which would take you back to APE1. Therefor downgradable? Any help is appreciated.
craazy82013 said:
Im somewhat confused. Your saying you cant downgrade from ph1. Are you talking only with odin? Reason i ask is stang5litre rom is APE1. And as was stated a few posts up, this rom can be flashed on rooted APH1. Which would take you back to APE1. Therefor downgradable? Any help is appreciated.
Click to expand...
Click to collapse
Ph1 upgrades the boot image therefore you cannot Odin flash back to stock pe1 which is the older boot image.
You can still root and flash stang5litre which is the pe1 rom, but you still have the ph1 boot image.
Sent from my VS987 using XDA-Developers mobile app
bart77 said:
Ph1 upgrades the boot image therefore you cannot Odin flash back to stock pe1 which is the older boot image.
You can still root and flash stang5litre which is the pe1 rom, but you still have the ph1 boot image. So if something goes wrong, you have no means of recovery back to stock since there is no ph1 stock Odin image.
Sent from my VS987 using XDA-Developers mobile app
Click to expand...
Click to collapse
The ph1 image is available at this link (http://updato.com/firmware-archive-select-model?record=78F84FCD811E11E69B2DFA163EE8F90B). I have flashed with these files and they work perfect.
Seems bootloader was uograded to version 3. So may be possible to flash between tmo and vzw and vice versa. Both now have v3 bootloader.
Hi if anyone can help- I'm on the Verizon Samsung Galaxy Note 4 after 2 Note 7's and a Note 3 before that on Biggin's so I've sorta been out of the root game. I want to downgrade from 6.0.1 to 5.1.1. I am downloading the full firmware for the Note 4 from further back in this thread (N910VVRU2CPA1) and am currently on (N910VVRU2CPG2).
From what I understand, I need to do a factory reset, then go to Odin and flash the firmware. I have Odin 3.10.7 and am downloading the N910VVRU2CPA1 as we speak. I see 'hsbadr' firmwares in his thread and the PIT file TRLTE_USA_VZW.pit which I'm not sure is compatable pit file for the specific 5.1.1 firmware or the necessary pit file is included in the full firmware and can anyone tell me if these are the right steps?are these the right steps Any information would be greatly appreciated,
Thanks
@tjmethod by chance how did you process go, did you manage to root and unlock bootloader?
djisback said:
@tjmethod by chance how did you process go, did you manage to root and unlock bootloader?
Click to expand...
Click to collapse
I bought the phone already with 6.0.1 on it and read that you cannot unlock/ root it with mm on it and can only be done after downgrading to 5.1.1 so I haven't done anything yet
I'm in the same boat...Coming from a n7. Bought a n4 on eBay...It's got 601. Want to root...Guess we need to downgrade....Is it possible?
tjmethod said:
Hi if anyone can help- I'm on the Verizon Samsung Galaxy Note 4 after 2 Note 7's and a Note 3 before that on Biggin's so I've sorta been out of the root game. I want to downgrade from 6.0.1 to 5.1.1. I am downloading the full firmware for the Note 4 from further back in this thread (N910VVRU2CPA1) and am currently on (N910VVRU2CPG2).
From what I understand, I need to do a factory reset, then go to Odin and flash the firmware. I have Odin 3.10.7 and am downloading the N910VVRU2CPA1 as we speak. I see 'hsbadr' firmwares in his thread and the PIT file TRLTE_USA_VZW.pit which I'm not sure is compatable pit file for the specific 5.1.1 firmware or the necessary pit file is included in the full firmware and can anyone tell me if these are the right steps?are these the right steps Any information would be greatly appreciated,
Thanks
Click to expand...
Click to collapse
sudermatt said:
I'm in the same boat...Coming from a n7. Bought a n4 on eBay...It's got 601. Want to root...Guess we need to downgrade....Is it possible?
Click to expand...
Click to collapse
Before you can start rooting, you'll need to be on 5.1.1 BPA1. If you're currently on 6.0.1, just download the BPA1 firmware from Sammobile, factory reset on 6.0.1, then flash BPA1 stock via Odin.
quinciebee said:
Before you can start rooting, you'll need to be on 5.1.1 BPA1. If you're currently on 6.0.1, just download the BPA1 firmware from Sammobile, factory reset on 6.0.1, then flash BPA1 stock via Odin.
Click to expand...
Click to collapse
Hi thanks, I had called Samsung and talked to top tier tech support and was told that once the phone has been upgraded to 6.0.1., it cannot be downgraded. and that i need to search the rooting sites and try to find where someone has found a breach or workaround for unlocking the bootloader which will usually have a bounty but I dont know. top tier tech support has always been good. Do you think thats false it cannot be downgraded?
tjmethod said:
Hi thanks, I had called Samsung and talked to top tier tech support and was told that once the phone has been upgraded to 6.0.1., it cannot be downgraded. and that i need to search the rooting sites and try to find where someone has found a breach or workaround for unlocking the bootloader which will usually have a bounty but I dont know. top tier tech support has always been good. Do you think thats false it cannot be downgraded?
Click to expand...
Click to collapse
It's definitely false, when I rooted my phone, I downgraded from 6.0.1 to 5.1.1 without any issues.
quinciebee said:
It's definitely false, when I rooted my phone, I downgraded from 6.0.1 to 5.1.1 without any issues.
Click to expand...
Click to collapse
I will definately give it a go when I have the time, have you flashed a rom and if so which one, there must be some or some tweaks to get rid of the lag?
tjmethod said:
I will definately give it a go when I have the time, have you flashed a rom and if so which one, there must be some or some tweaks to get rid of the lag?
Click to expand...
Click to collapse
I'm currently using CM13 because of Xposed and overall stability, but there are newer roms out there.
quinciebee said:
I'm currently using CM13 because of Xposed and overall stability, but there are newer roms out there.
Click to expand...
Click to collapse
I am a little confused as to whether I've found the right firmwares but I've found the firmwares here:
https://forum.xda-developers.com/no...mware-firmware-kernel-modem-recovery-t2942937
If I am downgrading to 5.1.1. which this phone was obviously on before, I don't know what this phone was on since it currently is on the PL1 build which are not one of the two 6.0.1. builds on this page. I don't even know if that matters.. Anyway, the two 5.1.1. builds are PA1 and OK3. Do you know where any other firmwares out there that might show my current one and the previous build that it came from?
Thanks-
tjmethod said:
I am a little confused as to whether I've found the right firmwares but I've found the firmwares here:
https://forum.xda-developers.com/no...mware-firmware-kernel-modem-recovery-t2942937
If I am downgrading to 5.1.1. which this phone was obviously on before, I don't know what this phone was on since it currently is on the PL1 build which are not one of the two 6.0.1. builds on this page. I don't even know if that matters.. Anyway, the two 5.1.1. builds are PA1 and OK3. Do you know where any other firmwares out there that might show my current one and the previous build that it came from?
Thanks-
Click to expand...
Click to collapse
You want the PA1. It's really easy. Just sounds more complicated then it is. I am using the PaulPizz rom. It is very stable, good battery life, and spen and sview work. If you need any help, let me know.
ziggy71 said:
You want the PA1. It's really easy. Just sounds more complicated then it is. I am using the PaulPizz rom. It is very stable, good battery life, and spen and sview work. If you need any help, let me know.
Click to expand...
Click to collapse
Thanks bro I don't if I'll have time til this weekend to do this- Does this rom have tweaks to fix the aggravating galaxy lag? With a non rooted phone there's goin into recovery and deleting cache, DU speed and phone booster, cleaned but it's like they all have it- thanks again- lookin forward to rooting this damn thing
tjmethod said:
I am a little confused as to whether I've found the right firmwares but I've found the firmwares here:
https://forum.xda-developers.com/no...mware-firmware-kernel-modem-recovery-t2942937
If I am downgrading to 5.1.1. which this phone was obviously on before, I don't know what this phone was on since it currently is on the PL1 build which are not one of the two 6.0.1. builds on this page. I don't even know if that matters.. Anyway, the two 5.1.1. builds are PA1 and OK3. Do you know where any other firmwares out there that might show my current one and the previous build that it came from?
Thanks-
Click to expand...
Click to collapse
Yeah they're out there but that thread hasn't been updated recently. Basically the order after pf3 is pg2, pj2, and then cpl1. The one you want, if your planning on rooting, is bpa1. Also, as far as your question in the op about the pit file, it should really only be used if absolutely necessary. It's in case your partitions have been corrupted for some reason and you need to repartition your device.
Edit- I was going to link to those other firmwares but they are buried in the thread that your already looking in. Either way they aren't necessary for you to unlock your bootloader, you can go straight from cpl1 to bpa1.
kevintm78 said:
Yeah they're out there but that thread hasn't been updated recently. Basically the order after pf3 is pg2, pj2, and then cpl1. The one you want, if your planning on rooting, is bpa1. Also, as far as your question in the op about the pit file, it should really only be used if absolutely necessary. It's in case your partitions have been corrupted for some reason and you need to repartition your device.
Edit- I was going to link to those other firmwares but they are buried in the thread that your already looking in. Either way they aren't necessary for you to unlock your bootloader, you can go straight from cpl1 to bpa1.
Click to expand...
Click to collapse
Hey thanks for confirming all this. So all I need to download and install is the bpa1 firmware via Oden with the AP button I think- I've got a few different versions of Oden on my pc. It's been a while since I've flashed firmware on a phone but I remember it was easy. So just save my pictures, any files, etc. on the sd card, remove it, then do a factory reset or when I put the setting into usb download mode, and flash the firmware this will automatically factory reset the phone? Also earlier today Verizon has been trying to push an software upgrade. After I unlock the bootloader and install twrp then flash a rom, do I need to somehow disable the update notice. I remember having to do that once with another phone.
What rom are you on? Thanks again for the Info-
TJ
tjmethod said:
Hey thanks for confirming all this. So all I need to download and install is the bpa1 firmware via Oden with the AP button I think- I've got a few different versions of Oden on my pc. It's been a while since I've flashed firmware on a phone but I remember it was easy. So just save my pictures, any files, etc. on the sd card, remove it, then do a factory reset or when I put the setting into usb download mode, and flash the firmware this will automatically factory reset the phone? Also earlier today Verizon has been trying to push an software upgrade. After I unlock the bootloader and install twrp then flash a rom, do I need to somehow disable the update notice. I remember having to do that once with another phone.
What rom are you on? Thanks again for the Info-
TJ
Click to expand...
Click to collapse
Yeah that all sounds spot on. I would definitely do the factory reset before you start, but other than that your good. To block the updates, you can uninstall the SDM apps. There are 2 of those and you'll need root to remove them, but you can disable them without root with that debloater tool. The rom I'm currently using is kind of work in progress. I have a couple stock based roms in the dev section, one is stock_plus that has a stock feel with some mods added and the other is Modest Rom that is got some grace apps added and system ui mods. You can find them here and here if you want to check them out.
kevintm78 said:
Yeah that all sounds spot on. I would definitely do the factory reset before you start, but other than that your good. To block the updates, you can uninstall the SDM apps. There are 2 of those and you'll need root to remove them, but you can disable them without root with that debloater tool. The rom I'm currently using is kind of work in progress. I have a couple stock based roms in the dev section, one is stock_plus that has a stock feel with some mods added and the other is Modest Rom that is got some grace apps added and system ui mods. You can find them here and here if you want to check them out.
Click to expand...
Click to collapse
Awesome, I'm going to check those out but I forgot the biggest question of all... how to get rid of the Galaxy lag- is there a rom or tweak where this can be fixed since recovery cache delete and cleaning tools dont really do much?
Thanks again-
tjmethod said:
Awesome, I'm going to check those out but I forgot the biggest question of all... how to get rid of the Galaxy lag- is there a rom or tweak where this can be fixed since recovery cache delete and cleaning tools dont really do much?
Thanks again-
Click to expand...
Click to collapse
Custom kernels help a lot. The problem is it's kind of slim pickings for our specific model, but some of the international kernels work well too. Oscar kernel is made for the 910v so that's probably the most reliable but if your like me, I like to use a permissive kernel and Ram kernel is not a bad choice for that though it's not as feature rich.
kevintm78 said:
Custom kernels help a lot. The problem is it's kind of slim pickings for our specific model, but some of the international kernels work well too. Oscar kernel is made for the 910v so that's probably the most reliable but if your like me, I like to use a permissive kernel and Ram kernel is not a bad choice for that though it's not as feature rich.
Click to expand...
Click to collapse
I really dont know the difference... from what I remember a kernel is the layer between the software and the hardware- a key component of the os. I'm guessing the permissive ones can be used for different roms or firmware? You can probably tell I really don't that much about the root game. The last time I flashed a firmware was on my note 3 after I bricked it. Then rerooted and got on to biggins rom which was great ut I never understood or learned how to use xposed. Anyway, I downloaded Modest Rom, PJ2 _STOCK .tar and am downloading cpl1_tar but I know that once I flash bpa1 firmware which puts the phone back on 5.1.1. I see your roms are 6.0.1 roms, after I flash the bpa1, will the bootloader be unlocked? If so can I then just flash the cpla1_tar or is that not a full firmware? or use one of the two 6.0.1 firmwares from where I found the cpa1? Are the kernels different from 6.0.1 and 5.1.1 and where to find the downloads?? I appreciate the tips especially coming from a develpoer and i'm happy to make a donation- I'm not sure how?
Thanks again!
tjmethod said:
I really dont know the difference... from what I remember a kernel is the layer between the software and the hardware- a key component of the os. I'm guessing the permissive ones can be used for different roms or firmware? You can probably tell I really don't that much about the root game. The last time I flashed a firmware was on my note 3 after I bricked it. Then rerooted and got on to biggins rom which was great ut I never understood or learned how to use xposed. Anyway, I downloaded Modest Rom, PJ2 _STOCK .tar and am downloading cpl1_tar but I know that once I flash bpa1 firmware which puts the phone back on 5.1.1. I see your roms are 6.0.1 roms, after I flash the bpa1, will the bootloader be unlocked? If so can I then just flash the cpla1_tar or is that not a full firmware? or use one of the two 6.0.1 firmwares from where I found the cpa1? Are the kernels different from 6.0.1 and 5.1.1 and where to find the downloads?? I appreciate the tips especially coming from a develpoer and i'm happy to make a donation- I'm not sure how?
Thanks again!
Click to expand...
Click to collapse
Hey buddy, did you get it figured out? I broke my arm at work on Sunday and of course it's my right arm so I'm having some issues responding back on my note with one hand. I bet I've dropped this thing 20 times already.
kevintm78 said:
Hey buddy, did you get it figured out? I broke my arm at work on Sunday and of course it's my right arm so I'm having some issues responding back on my note with one hand. I bet I've dropped this thing 20 times already.
Click to expand...
Click to collapse
Oh man that sucks- hopefully they gave you some good pain meds. Anyway, I havent taken th plunge yet- once I get on to 5.1.1 then twrp, I want to go on to 6.0.1 but am unsure as to what point the bootloader is unlocked or exactly what to do to upgrade to 6.0.1 once I crack the bl. I just dont want to go through the dreaded set up everything twice.
hi!!
I have a HTC M8 dual sim, with a custom 7.1.2 ROM; I have not upgrade or install any other radio file than the stock.
It happens that when I get far away from my city, i lost all my signal. and in general it doesn't come back until I reboot the device (a soft restart works). and then I get signal again, but only for several minutes; then it all repeats.
from time to time it gets signal and stays like that, so I suspect that my device is not been able to get signal for the other operators of my country (here the cells are shared between the operators.. and I suppose that it works that way worldwide).
this is pretty annoying because I love to travel, and virtually do it without phone capability.
could it be that I have upgraded my phone that far from stock that the radio firmware got obsolete? or it may be a hardware problem?
tthanks ^^
xxopiumxx said:
could it be that I have upgraded my phone that far from stock that the radio firmware got obsolete? or it may be a hardware problem?
Click to expand...
Click to collapse
I don't know what you mean that the radio "got obsolete". Receptions issues may be possible with a custom ROM (which ROM?). But it's impossible to say whether the ROM is the issue or not, unless you go back to the stock ROM, and see if the problem persists.
redpoint73 said:
I don't know what you mean that the radio "got obsolete". Receptions issues may be possible with a custom ROM (which ROM?). But it's impossible to say whether the ROM is the issue or not, unless you go back to the stock ROM, and see if the problem persists.
Click to expand...
Click to collapse
I meant that the part of the hardware firmware that manage the modem, may be too outdated respect of the rom . i am just taking a guest.
until yesterday i was runing Lineage OS 14.1; but it had a horrible issue that after a call it kept in "hanging" until I restarted. so, i went back to CM13.
xxopiumxx said:
I meant that the part of the hardware firmware that manage the modem, may be too outdated respect of the rom . i am just taking a guest.
Click to expand...
Click to collapse
The firmware is stuck on Marshmallow, since HTC doesn't support this phone with updates anymore. All the ROMs will work with Marshmallow firmware, since there is no other firmware for it to work with for this device.
redpoint73 said:
The firmware is stuck on Marshmallow, since HTC doesn't support this phone with updates anymore. All the ROMs will work with Marshmallow firmware, since there is no other firmware for it to work with for this device.
Click to expand...
Click to collapse
good. so i wanted to know if this that you tell me could cause something like the mentioned issue; or if i should be looking into hardware ones.
xxopiumxx said:
good. so i wanted to know if this that you tell me could cause something like the mentioned issue; or if i should be looking into hardware ones.
Click to expand...
Click to collapse
Back to stock is probably your best bet, and see if the problem persists. Really not much else you can do, especially since I think Lineage or CM are the only custom ROMs for the dual sim?
If you do back to stock, and still have problem, it may be a hardware issue. Might be a network issue, as well.