Hi,
I am running CYanogenMod 13.0-20360525 UNOFFICIAL tritevzw
Baseband N910VVRU2CPJ2
Build Number: ANdroid 6.0.1 MOB30JN910VVRU2BPA1
Whenever I go into settings and click on "Security" I get a popup box that says"
"Unfortunately Settings has stopped"
To try to fix this I have gone into recovery and wiped dalvik and caches.
Thanks for any help!
plainbum said:
Hi,
I am running CYanogenMod 13.0-20360525 UNOFFICIAL tritevzw
Baseband N910VVRU2CPJ2
Build Number: ANdroid 6.0.1 MOB30JN910VVRU2BPA1
Whenever I go into settings and click on "Security" I get a popup box that says"
"Unfortunately Settings has stopped"
To try to fix this I have gone into recovery and wiped dalvik and caches.
Thanks for any help!
Click to expand...
Click to collapse
What build of CM13 did you flash? Your build number says BPA1, but it should be saying CPF3.
quinciebee said:
What build of CM13 did you flash? Your build number says BPA1, but it should be saying CPF3.
Click to expand...
Click to collapse
Hi quinciebee, thanks fo ryour reply.
I was on ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 and firmware BPA1
Then I wanted to try out Hsbadr's new 7.1.1 Nougat Rom and it required new CPJ2 firmware so I odin'd it in.
I TWRP backed up my ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 build I have been running for months.
Then flashed his newest "EmotionOS" But could not get 4G LTE to work so I restored my 6.0 backup since I cant function on 3G only and no one in these forums was able to help me.
Hope that wasn't too confusing
Oh by the way, I am doing this on a Developer Edition Note 4 on Verizon
When I flashed CPJ2 firmware I used a partial build as explained here:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
He quotes:
Quote:
"If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial fimware via Odin to upgrade:
N910VVRU2CPJ2_PartialFirmware_DevEd.tar.md5.7z
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CPJ2."
plainbum said:
Hi quinciebee, thanks fo ryour reply.
I was on ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 and firmware BPA1
Then I wanted to try out Hsbadr's new 7.1.1 Nougat Rom and it required new CPJ2 firmware so I odin'd it in.
I TWRP backed up my ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 build I have been running for months.
Then flashed his newest "EmotionOS" But could not get 4G LTE to work so I restored my 6.0 backup since I cant function on 3G only and no one in these forums was able to help me.
Hope that wasn't too confusing
Oh by the way, I am doing this on a Developer Edition Note 4 on Verizon
When I flashed CPJ2 firmware I used a partial build as explained here:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
He quotes:
Quote:
"If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial fimware via Odin to upgrade:
N910VVRU2CPJ2_PartialFirmware_DevEd.tar.md5.7z
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CPJ2."
Click to expand...
Click to collapse
How did you flash CM13, and did you flash the 09/19 build?
quinciebee said:
How did you flash CM13, and did you flash the 09/19 build?
Click to expand...
Click to collapse
The build date is May 25 2016
Here is a list of roms of that ilk
https://forum.xda-developers.com/devdb/project/?id=12650#downloads
plainbum said:
The build date is May 25 2016
Here is a list of roms of that ilk
https://forum.xda-developers.com/devdb/project/?id=12650#downloads
Click to expand...
Click to collapse
Then I think that's the problem, you'll have to clean flash the 09/19 build.
Delete
quinciebee said:
Then I think that's the problem, you'll have to clean flash the 09/19 build.
Click to expand...
Click to collapse
I flashed to 09/19 build the phone would not boot. I kept getting a rapid glow behind the Blue android mascot.
I then tried to odin the BOG5 firmware and I got errors . rebooted the phone and it wouldnt boot.
Now just bootloops to the samsung screen,
It's borked.
I think I lost Dev Edition and the best I can do is start from scratch?
Not sure where to go now.
plainbum said:
I flashed to 09/19 build the phone would not boot. I kept getting a rapid glow behind the Blue android mascot.
I then tried to odin the BOG5 firmware and I got errors . rebooted the phone and it wouldnt boot.
Now just bootloops to the samsung screen,
It's borked.
I think I lost Dev Edition and the best I can do is start from scratch?
Not sure where to go now.
Click to expand...
Click to collapse
Is the BOG5 firmware stock? If so, you shouldn't have flashed it. If you still have TWRP and root, take these steps to clean flash to CM13.
1. Boot to TWRP, wipe all but your External Storage (SD Card)
2. Flash CM13 09/19 zip
3. Flash the boot image from CM13 07/24
(Click on install image, select the boot.img file, you will then see two choices: boot and recovery, select boot only, then swipe to flash.)
4. Flash gapps and SuperSU zip
5. Reboot
The rapid blinking was happening because you need the boot image from 07/24 in order for the rom to load properly. I'd post the boot image for you, but it exceeds the file size limit. To get the boot image, download the CM13 07/24 build, unzip the file, and extract the boot.img file to your SD card, along with everything else that you want to flash. Let me know if you need me to provide more details on any of the steps.
I can't even get into twrp.
All I can do is get into "Download mode"
I have started a new thread looking for help here:
https://forum.xda-developers.com/no...p-screwed-vzw-dev-ed-software-update-t3530282
plainbum said:
I can't even get into twrp.
All I can do is get into "Download mode"
I have started a new thread looking for help here:
https://forum.xda-developers.com/no...p-screwed-vzw-dev-ed-software-update-t3530282
Click to expand...
Click to collapse
What do you see when you try to boot into recovery?
Hi quinciebee,
I posted this before I borked my phone, before you started helping me.
How I got here was I was trying to upgrade the firmware so I could them flash The ne 7.1.1 "EmotionOS"
I was following the instruction here:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
Specifically where is says:
"If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial fimware via Odin to upgrade:
N910VVRU2CPJ2_PartialFirmware_DevEd.tar.md5.7z
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CPJ2."
It flashed fine and then I installed the EmotionOS and all went well but I could NOT get 4G LTE to work, only 3G.
So I abandoned it and reflashed a backup of the CM 13 I was running since May 25.
I was good on cm13 but I got errors when I was in settings and tried to go into "Security"
Im all god now and I will be trying to get back to 6.0 and then 7.1.1 after my house guests leave.
The phone is running fine in 5.1.1.
THanks again!
Related
This firmware is for Sprint Galaxy S6 [G920P] phones ONLY
This will not damage any of your stored files or app settings
WARNING! Do not unplug your phone once you have started
Samsung Sprint Galaxy S6 BOL1 Android 5.1.1 Stock Rom
Download Firmware
https://www.dropbox.com/s/n0p0rmi2d873h1d/G920PVPU3BOL1_SPT3BOL1_SPR_Sprint_USA_5.1.1.zip?dl=0
Alternate Firmware Download Mirror
https://www.androidfilehost.com/?fid=24052804347838029
Alternate Firmware Download Mirror
https://www.androidfilehost.com/?fid=24345424848486725
Download Odin
http://odindownload.com/SamsungOdin/#.Vr3P1_IrKJI
1. Put your phone in download mode by turning it off,
Press and hold Volume Down+Power+Home Button
And then pressing Volume Up: Continue
Phone should then say Downloading...
Do not turn off target
2. Unzip Odin.exe to your desktop
Open Odin
After connecting your phone while in download mode to your desktop
Odin should say Added!
Leave the options alone
*DO NOT SELECT REPARTITION!
3. Unzip the G920PVP firmware
Using Odin click AP and select the firmware .tar file
Click Start
Wait a few moments until Odin says SUCCESS!:highfive:
DONE! Then your phone should reboot and you'll see the Android icon/Boot Logo sequence
Check your phone for any updates while you are on this fresh new install to be on the latest firmware
BONUS! In case you get stuck in download mode
Hold Volume Up+Down Home+Power buttons
Your phone should exit and reboot
Thank you for this! Very much appreciated.
You're welcome, new firmware mirror up
Thanks for this thread. I have MM stock, but the hotspot now requires a reboot to get it working. Can I use this method to flash back to Lollipop? I saw a thread saying you cannot flash anything older than 5.1.1. That was an older thread, and basically he was told he can't flash 5.0.2 back on his S6 because he already had 5.1.1.
badkarmah187 said:
Thanks for this thread. I have MM stock, but the hotspot now requires a reboot to get it working. Can I use this method to flash back to Lollipop? I saw a thread saying you cannot flash anything older than 5.1.1. That was an older thread, and basically he was told he can't flash 5.0.2 back on his S6 because he already had 5.1.1.
Click to expand...
Click to collapse
Hotspot should be fixed in my next ROM
badkarmah187 said:
Thanks for this thread. I have MM stock, but the hotspot now requires a reboot to get it working. Can I use this method to flash back to Lollipop? I saw a thread saying you cannot flash anything older than 5.1.1. That was an older thread, and basically he was told he can't flash 5.0.2 back on his S6 because he already had 5.1.1.
Click to expand...
Click to collapse
Well, I flashed my stock Note 5 rom over to the MM leak and now I'm stuck with it till the official release is out and I can flash back to stock and receive the latest official updates as they come out.
What happened was I wiped the drive and then flashed the lower # official roms and all it did was bootloop or just wouldn't flash the version at all and would just give me an error while trying to flash.
probleme
mykehdoom said:
Thank you for this! Very much appreciated.
Click to expand...
Click to collapse
my phone stiil blocked on recovery mode after mm 8.0 download with dm-verity verification failed. Chek drk first i can try this ?
I flashed backed to 5.1.1, I left my phone sitting with wifi enabled, sprint downloaded the 6.0.1 update and gave me no choice but to install it again. I had no way to back out of it. I put 5.1.1 on my phone twice today and it keeps sending me to MM. Is there a way to flash back to 5.1.1 and disable OTA without rooting the phone..? if not then you really can't go back because Sprint will force the update to your phone.
i guess there should be an option in setting/update for you to uncheck the "update".
racimrl said:
my phone stiil blocked on recovery mode after mm 8.0 download with dm-verity verification failed. Chek drk first i can try this ?
Click to expand...
Click to collapse
The DRK error means that someone changed your phone's IMEI but did it improperly. Now the phone will not even turn on past the Samsung screen. I run phone a business and offer a service to fix it - PM me if interested
MindTrix said:
I flashed backed to 5.1.1, I left my phone sitting with wifi enabled, sprint downloaded the 6.0.1 update and gave me no choice but to install it again. I had no way to back out of it. I put 5.1.1 on my phone twice today and it keeps sending me to MM. Is there a way to flash back to 5.1.1 and disable OTA without rooting the phone..? if not then you really can't go back because Sprint will force the update to your phone.
Click to expand...
Click to collapse
wait a minute... you can roll back a stock unrooted rom without having to root??
I need tether. I have to have tether. They forced the Marshmallow update without my permission. Complete BS. Now I have no tether.
jerry43812 said:
wait a minute... you can roll back a stock unrooted rom without having to root??
I need tether. I have to have tether. They forced the Marshmallow update without my permission. Complete BS. Now I have no tether.
Click to expand...
Click to collapse
Rolling back is as simple as using ODIN and flash the stock rom, I rooted 6.0.1 and its starting to grow on me but I can flash back to stock 5.1.1 even if I was not rooted, I only root because like you I need tether and so far this was the only way on 6.0.1 MM
Man oh man, I thought I broke my charging port the day after I rooted. I was about to cry myself to sleep for the next 2 months.
Going to MM
Should I use this to go back to stock and then take the OTA to get to the latest firmware? Or would it be a better idea to download the current firmware from Sammobile?
guitarpager said:
Should I use this to go back to stock and then take the OTA to get to the latest firmware? Or would it be a better idea to download the current firmware from Sammobile?
Click to expand...
Click to collapse
Don't go the SAMMOBILE page, I have linked to a much faster site: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
hey guys i am from india and i have been using unlocked sprint s6 from a month and everything was perfect till i flashed the marshmallow firmware , i have lost the sim signal ,, need help plz.. anybody know how to get back the signal....
dksahil said:
hey guys i am from india and i have been using unlocked sprint s6 from a month and everything was perfect till i flashed the marshmallow firmware , i have lost the sim signal ,, need help plz.. anybody know how to get back the signal....
Click to expand...
Click to collapse
This guide should help you: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
I can't say if it actually works as I live in the US and my phone is not unlocked, but it seems to have helped others.
Here a link for the latest stock TAR files: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
Tried to use this file and it says "SW REV CHECK FAIL. DEVICE 4 BINARY 3"
Xabring said:
Tried to use this file and it says "SW REV CHECK FAIL. DEVICE 4 BINARY 3"
Click to expand...
Click to collapse
This is a very old thread. That error means that your phone has updated to a software version of 6 or 7 and you can't revert back to 5.
Xabring said:
Tried to use this file and it says "SW REV CHECK FAIL. DEVICE 4 BINARY 3"
Click to expand...
Click to collapse
koop1955 said:
This is a very old thread. That error means that your phone has updated to a software version of 6 or 7 and you can't revert back to 5.
Click to expand...
Click to collapse
More accurately, it means that your bootloader version is 4, and you can't flash anything lower.
But no, you can't go back to Android 5
I loaded CM-13.0 nightly and have Been updating as the updates come but when I go to make a call it takes forever to go through and start ringing and sometimes it r just hangs up. The data keeps going from LTE to nothing and no SIM . I can't get mms either. Can someone tell me what to do.thanks.
Sent from my SGH-T999 using Tapatalk
HUCCG said:
I loaded CM-13.0 nightly and have Been updating as the updates come but when I go to make a call it takes forever to go through and start ringing and sometimes it r just hangs up. The data keeps going from LTE to nothing and no SIM . I can't get mms either. Can someone tell me what to do.thanks.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Same thing is happening to me. I've tried using OctOs M and now I am on PacRom 6.0.1 and I am having the same "No sim card" error. I can text and call, but no Data whatsoever.
Have you tried changing your APN settings for your network on your phone?
wmzed said:
Same thing is happening to me. I've tried using OctOs M and now I am on PacRom 6.0.1 and I am having the same "No sim card" error. I can text and call, but no Data whatsoever.
Have you tried changing your APN settings for your network on your phone?
Click to expand...
Click to collapse
are you on the latest baseband for your phone?
ratchetrizzo said:
are you on the latest baseband for your phone?
Click to expand...
Click to collapse
My stock OS Is 4.1.2 and is running Baseband UVAMB7. Do I need to go for the higher updates for the LTE to work?
wmzed said:
My stock OS Is 4.1.2 and is running Baseband UVAMB7. Do I need to go for the higher updates for the LTE to work?
Click to expand...
Click to collapse
I think you need to be on UVUBOH1.
https://forum.xda-developers.com/showthread.php?t=1949687 has the list of FW and it looks like you are using a super super old baseband.
ratchetrizzo said:
I think you need to be on UVUBOH1.
https://forum.xda-developers.com/showthread.php?t=1949687 has the list of FW and it looks like you are using a super super old baseband.
Click to expand...
Click to collapse
Do I need to use ODIN for this? I tried installing UVUBOH1 with TWRP, but I get an error when I installing it:
"could not find 'META-INF/com/google/android/update-binary' in the zip file"
wmzed said:
Do I need to use ODIN for this? I tried installing UVUBOH1 with TWRP, but I get an error when I installing it:
"could not find 'META-INF/com/google/android/update-binary' in the zip file"
Click to expand...
Click to collapse
Yes, download https://www.androidfilehost.com/?fid=24052804347821137
NOTE, if you click on "UVUBOH1" and not the androidfilehost link in the FW thread, it links you to the wrong FW and you'll flash UVUBNC1! Make sure you click the androidfilehost link underneath UVUB0H1.
Then flash it with odin.
Afterwards let it reboot and upgrade, then odin TWRP back and either restore a nandroid or flash the rom of your choosing
Oh also, if you're still on 4.1 and on a touchwiz rom, you may want to factory unlock it before you upgrade.. Just because you can. Follow the unlock thread on here
ratchetrizzo said:
Yes, download https://www.androidfilehost.com/?fid=24052804347821137
NOTE, if you click on "UVUBOH1" and not the androidfilehost link in the FW thread, it links you to the wrong FW and you'll flash UVUBNC1! Make sure you click the androidfilehost link underneath UVUB0H1.
Then flash it with odin.
Afterwards let it reboot and upgrade, then odin TWRP back and either restore a nandroid or flash the rom of your choosing
Oh also, if you're still on 4.1 and on a touchwiz rom, you may want to factory unlock it before you upgrade.. Just because you can. Follow the unlock thread on here
Click to expand...
Click to collapse
Thank you so much! I will try this out soon and respond with the results! And I had already unlocked my device :. I had to root and use the RegionLock app to unlock it, as the *#197328640# menu option did not work for me.
wmzed said:
Thank you so much! I will try this out soon and respond with the results! And I had already unlocked my device :. I had to root and use the RegionLock app to unlock it, as the *#197328640# menu option did not work for me.
Click to expand...
Click to collapse
how did you make out?
ratchetrizzo said:
how did you make out?
Click to expand...
Click to collapse
Was quite a bit of trouble at first . I managed to download and flash the software. flashed TWRP via odin.
Then through TWRP, I rooted by using the Knox remover zip (as i was on official 4.3, my service signal did shoot up to normal again!). Installed SuperSU.
Now when I try to flash any ROM via TWRP it gives errors such as "Status 7", or error reading MD5 when I try to backup software.
wmzed said:
Was quite a bit of trouble at first . I managed to download and flash the software. flashed TWRP via odin.
Then through TWRP, I rooted by using the Knox remover zip (as i was on official 4.3, my service signal did shoot up to normal again!). Installed SuperSU.
Now when I try to flash any ROM via TWRP it gives errors such as "Status 7", or error reading MD5 when I try to backup software.
Click to expand...
Click to collapse
Make sure twrp is up to date for d2tmo, and make sure the rom you are flashing is 4.3 or later. I'm pretty sure that once you're on the latest 4.3 rom you can't flash anything lower
ratchetrizzo said:
Make sure twrp is up to date for d2tmo, and make sure the rom you are flashing is 4.3 or later. I'm pretty sure that once you're on the latest 4.3 rom you can't flash anything lower
Click to expand...
Click to collapse
Got the latest TWRP running, but still the same issue trying to flash OctOS M, PACROM 5.0.1, etc.
wmzed said:
Got the latest TWRP running, but still the same issue trying to flash OctOS M, PACROM 5.0.1, etc.
Click to expand...
Click to collapse
That's strange, I'm using 3.0.2.0 and the latest 999L baseband and I haven't had any issues with flashing.
I'm Using the MM pac rom but I've tried CM14.1 nightly builds with no problem
ratchetrizzo said:
That's strange, I'm using 3.0.2.0 and the latest 999L baseband and I haven't had any issues with flashing.
I'm Using the MM pac rom but I've tried CM14.1 nightly builds with no problem
Click to expand...
Click to collapse
I have finally managed to figure it out. You need to completely format the entire ROM currently installed from your phone. Once that is done, you can add any ROM to install properly. I'm running well on OctOS-N 3/17/2017 build.
Thanks all for your help.
Hi everyone, I have spent the past few hours searching for a similar problem but I can't quite figure it out and some help would be greatly appreciated!
As the title stated, I am on 6.0.1 and the unofficial CM13 with my baseband version being N910VVRU2CPF3. What I want to do is upgrade to hsbadr's 7.1.1 EmotionOS. In the Emotion thread it says that ROM Firmware Required: N910VVRS2CPL1. I am wondering what I do to get to that firmware.
Following this: https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
It says that
If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial firmware via Odin to upgrade:
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRS2CPL1.
Click to expand...
Click to collapse
I think that applies to me but it's only a partial firmware and that confuses me. Also, I don't know when to flash Emotion as well as the GApps (I'm assuming I'll have TWRP installed)
Sorry if this is all easy stuff but I'm relatively new to more complex android systems and all help would be greatly appreciated!
NinjaChachi said:
Hi everyone, I have spent the past few hours searching for a similar problem but I can't quite figure it out and some help would be greatly appreciated!
As the title stated, I am on 6.0.1 and the unofficial CM13 with my baseband version being N910VVRU2CPF3. What I want to do is upgrade to hsbadr's 7.1.1 EmotionOS. In the Emotion thread it says that ROM Firmware Required: N910VVRS2CPL1. I am wondering what I do to get to that firmware.
Following this: https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
It says that
I think that applies to me but it's only a partial firmware and that confuses me. Also, I don't know when to flash Emotion as well as the GApps (I'm assuming I'll have TWRP installed)
Sorry if this is all easy stuff but I'm relatively new to more complex android systems and all help would be greatly appreciated!
Click to expand...
Click to collapse
Is your phone a dev, or retail converted dev? Boot into downloading to see if it says Mode: Developer, in grey.
It does say Mode: Developer but I'm like 99% I had to convert it to that in the rooting process. I followed the guide on these forums to upgrade from stock 5.1.1 to CM13.
ziggy71 said:
Is your phone a dev, or retail converted dev? Boot into downloading to see if it says Mode: Developer, in grey.
Click to expand...
Click to collapse
It does say Mode: Developer but I'm like 99% I had to convert it to that in the rooting process. I followed the guide on these forums to upgrade from stock 5.1.1 to CM13.
NinjaChachi said:
It does say Mode: Developer but I'm like 99% I had to convert it to that in the rooting process. I followed the guide on these forums to upgrade from stock 5.1.1 to CM13.
Click to expand...
Click to collapse
You need to have upgraded from 5.1.1 to 6.0.1 and rooted that as well. Since you're on CM13, I'm assuming that you did that, so then all you need to do is flash the CPL1 partial firmware provided by hsbadr in the above post, full wipe, then clean flash EmotionOS. The firmware is partial because it only changes the base firmware, as long as you're on rooted 6.0.1 Marshmallow to begin with, you should be fine.
quinciebee said:
You need to have upgraded from 5.1.1 to 6.0.1 and rooted that as well. Since you're on CM13, I'm assuming that you did that, so then all you need to do is flash the CPL1 partial firmware provided by hsbadr in the above post, full wipe, then clean flash EmotionOS. The firmware is partial because it only changes the base firmware, as long as you're on rooted 6.0.1 Marshmallow to begin with, you should be fine.
Click to expand...
Click to collapse
Flash CPL1 and EmotionOS via TWRP? I am on rooted 6.0.1 btw
NinjaChachi said:
Flash CPL1 and EmotionOS via TWRP? I am on rooted 6.0.1 btw
Click to expand...
Click to collapse
Flash CPL1 via Odin, then clean flash EmotionOS via TWRP.
quinciebee said:
Flash CPL1 via Odin, then clean flash EmotionOS via TWRP.
Click to expand...
Click to collapse
Ok sweet! So the CPL1 partial firmware won't remove TWRP or anything?
NinjaChachi said:
Ok sweet! So the CPL1 partial firmware won't remove TWRP or anything?
Click to expand...
Click to collapse
Nope.
I have spent the past 2 days trying to get a new cfw installed on my phone that didnt have many bugs. I settled with the cyanogenmod13 and read that it was good for a daily driver. At first i installed the wrong gapps and would make the keyboard crash, but now that i figured that out i need help with getting the rom to recognize the sim card. I tryed reflashing with twrp 2.8.6.0 because i read that it would flash the modem correctly, but still no luck. i'm fairly new to flashing and have only done it 3 times in the past. So now i made an account here to ask for help.
Thanks in advance to all the help i get here.
Is the phone running the latest bootloader and modem? You can compare the versions in the phone to sammobile.com.
audit13 said:
Is the phone running the latest bootloader and modem? You can compare the versions in the phone to sammobile.com.
Click to expand...
Click to collapse
Thanks for your rely, Im not 100% sure what you mean by modem as im fairly new to this whole business. I will go to the website to see what i can find. Where can i see that information about the modem i am currently running?
I recommend matching the bootloader and modem version to each other.
You can download the Samsung Phone Info app from the Play Store to learn about the phone.
audit13 said:
I recommend matching the bootloader and modem version to each other.
You can download the Samsung Phone Info app from the Play Store to learn about the phone.
Click to expand...
Click to collapse
Ok I did some research and learned that the modem is the baseband number that shows in the about phone section. This is currently unknown or my guess non existant and that is why the phone says that the sim card is not inserted.
I also learned that i can use ODIN to flash the modem/baseband directly without the need to reflash the whole rom.
I dont know where to find the file online for the modem that matches the rom. I have spent a while looking around and have seen older posts of people saying that they have experienced the same issues after flashing cm13 on n9005 Note 3.
Here is what i am running on my phone:
- Cyanogenmod Version: 13-20151031-UNOFFICIAL-hlte (maybe there is a newer version to this somewhere that has this issue fixed)
- Baseband: Unknown
- Kernal Version: [email protected] #5
- Build Number: 1
-hlte-userdebug 6.0 MRA58K 2127f69904 test-keys
What do you think? And thanks for you help so far. :good:
The simplesting may be this: update TWRP to the latest version. You can flash the img file from TWRP.
Once TWRP has been updated, create a nandroid backup of the existing ROM.
Download the latest ROM from sammobile.com and flash the whole ROM. This is the simplest and safest option IMHO.
After flashing the stock ROM and making sure the sim is recognized and IMEI is correct, use Odin to flash the latest tar version of TWRP , boot into TWRP, restore backup, test your sim.
audit13 said:
The simplesting may be this: update TWRP to the latest version. You can flash the img file from TWRP.
Once TWRP has been updated, create a nandroid backup of the existing ROM.
Download the latest ROM from sammobile.com and flash the whole ROM. This is the simplest and safest option IMHO.
After flashing the stock ROM and making sure the sim is recognized and IMEI is correct, use Odin to flash the latest tar version of TWRP , boot into TWRP, restore backup, test your sim.
Click to expand...
Click to collapse
Ok I will give it a go and let you know what Happens, it will take a while because Here in Ecuador i Have very slow internet. I have to leave the files downloading over night.
Thanks for you help
Wouldnt I be able to flash the modem with odin as long as it matches the phone model? or will that cause problems?
Good luck. I hope it works for your phone.
audit13 said:
The simplesting may be this: update TWRP to the latest version. You can flash the img file from TWRP.
Once TWRP has been updated, create a nandroid backup of the existing ROM.
Download the latest ROM from sammobile.com and flash the whole ROM. This is the simplest and safest option IMHO.
After flashing the stock ROM and making sure the sim is recognized and IMEI is correct, use Odin to flash the latest tar version of TWRP , boot into TWRP, restore backup, test your sim.
Click to expand...
Click to collapse
Tempestelf2 said:
Ok I will give it a go and let you know what Happens, it will take a while because Here in Ecuador i Have very slow internet. I have to leave the files downloading over night.
Thanks for you help
Click to expand...
Click to collapse
Updating to the latest version of TWRP is a bad idea. If you update to version 3.0+ you can't install ROM's that use the AROMA installer. The newer versions of TWRP do not support it. The best version I've found is 2.7.8.0 to be able to handle any flashing.
The biggest problem is the sim card in my opinion.
audit13 said:
The biggest problem is the sim card in my opinion.
Click to expand...
Click to collapse
The sim card works fine in Ecuador, I have used it before flashing to cm13. I found the website of the ones who made the build and noticed that the version that I have downloaded is 1.33 from Oct 31, 2015 and that their latest updates on the channel log is version 12. I will download and flash latest build and she if the issue is fixed.
I was referring to the card bot being recognized in CM, not on a stock ROM. Thanks.
I'm wondering if anyone has attempted to install a Marshmallow custom ROM or stock RUU over the Nougat firmware with any success.
I'm doubtful, but perhaps it's possible with S-On. Thanks!
the nougat firmware is not downcompatible with marshmallow roms.
only way would be to s-off, downgrade firmware then, flash the marshmallow rom.
be aware to pick a full firmware though and no incremental one...we've seen a handful people doing this and that ends in a hardbrick.
j to the 4n said:
the nougat firmware is not downcompatible with marshmallow roms.
only way would be to s-off, downgrade firmware then, flash the marshmallow rom.
be aware to pick a full firmware though and no incremental one...we've seen a handful people doing this and that ends in a hardbrick.
Click to expand...
Click to collapse
When I then eventually update ViperROM from Marshmallow to Nougat, will I have to perform a full wipe - or can the update be directly applied?
Trying to plan ahead, thanks a bunch j4n.
fullydeveloped said:
When I then eventually update ViperROM from Marshmallow to Nougat, will I have to perform a full wipe - or can the update be directly applied?
Trying to plan ahead, thanks a bunch j4n.
Click to expand...
Click to collapse
well, that sounds like that you are still on marshmallow firmware + rom.
That would mean, you could flash the nougat rom and revert back to the marshmallow one anytime. Just ensure you flash latets TWRP before and backup your data, including sdcard..in case something goes wrong with encryption.
the nougat rom can be dirty flashed.
you know what the difference between firmware and rom is, right?
j to the 4n said:
well, that sounds like that you are still on marshmallow firmware + rom.
That would mean, you could flash the nougat rom and revert back to the marshmallow one anytime. Just ensure you flash latets TWRP before and backup your data, including sdcard..in case something goes wrong with encryption.
the nougat rom can be dirty flashed.
you know what the difference between firmware and rom is, right?
Click to expand...
Click to collapse
Thanks, apologies for the confusion. I'm on Nougat, but am planning to downgrade for xposed - then eventually update back up to Nougat once there's a stable release. I asked about dirty flashing since I'm less likely to full wipe for 7.0 after many months of customizing
j to the 4n said:
the nougat firmware is not downcompatible with marshmallow roms.
only way would be to s-off, downgrade firmware then, flash the marshmallow rom.
be aware to pick a full firmware though and no incremental one...we've seen a handful people doing this and that ends in a hardbrick.
Click to expand...
Click to collapse
Has anyone downgraded the Firmware and succeeded? I hard bricked mine twice, first was trying to downgrade it with a full stock firmware from OTA and 2nd time it died when i accidentally picked and flashed a wrong Marshmallow aboot trying to get rid of Hidden Red text which made me believe flashing a Marshmallow aboot while on Nougat hardbricks the Phone. It died at the stage where it should restart so we can run fastboot flash zip Firmware_xx.zip command the 2nd time. It goes black, doesn't turn on, a PC doesn't recognize it, doesn't show if charging. Was lucky HTC took care of the problem.
emrug said:
Has anyone downgraded the Firmware and succeeded? I hard bricked mine twice, first was trying to downgrade it with a full stock firmware from OTA and 2nd time it died when i accidentally picked and flashed a wrong Marshmallow aboot trying to get rid of Hidden Red text which made me believe flashing a Marshmallow aboot while on Nougat hardbricks the Phone. It died at the stage where it should restart so we can run fastboot flash zip Firmware_xx.zip command the 2nd time. It goes black, doesn't turn on, a PC doesn't recognize it, doesn't show if charging. Was lucky HTC took care of the problem.
Click to expand...
Click to collapse
thats what I said. The firmware in an ota is NOT a full firmware, its a incremental one.
You need a full firmware package like its provided in @Sneakyghost 's threads, with those lots of downgraded already.
j to the 4n said:
thats what I said. The firmware in an ota is NOT a full firmware, its a incremental one.
You need a full firmware package like its provided in @Sneakyghost 's threads, with those lots of downgraded already.
Click to expand...
Click to collapse
Great!! Now i get it, well explained. Thanks :highfive: