Related
The new MG1 firmware updates the modem, provides stability, adds apps2sd, removes smearing and other goodies. Here are a few methods to obtaining the latest update if you are rooted.
I take no responsibility if anything adverse happens to your device. Be sure to thank the OP's of the corresponding threads!
1) Download the new firmware .tar file and flash it from ODIN and re-root, or flash with Mobile ODIN and use everRoot option. You will still need to install a custom recovery again either way. Firmware can be found here: http://forum.xda-developers.com/showthread.php?t=2269304
2) Resort to stock ROM, remove root and see if device status shows "official" and try the "check for updates" under about phone to try for the OTA. Having a custom recovery may prevent this from working.
3) Try these methods for getting back to device status "official" to attempt the OTA: http://forum.xda-developers.com/showthread.php?t=2296014
Again having a custom recovery may prevent any of those methods from working.
4) If all you want is the new MG1 modem/radio see here: http://forum.xda-developers.com/showthread.php?p=43899220
5) If all you want is the ROM here is the latest MG1 firmware as a flashable zip via custom recovery. This does not include the modem however. http://forum.xda-developers.com/showthread.php?t=2375180
NOTE: MG1 removes root. Motochopper Exploit does not seem to root MG1 as of now so use CF-AutoRoot which is confirmed working: http://forum.xda-developers.com/showthread.php?t=2293800
I have Rogers 1337M rooted stock with TWRP 2.6. Can i update OTA (from the about phone menu)?
serkan5000 said:
I have Rogers 1337M rooted stock with TWRP 2.6. Can i update OTA (from the about phone menu)?
Click to expand...
Click to collapse
Probably not, if your device status in about menu says "custom" instead of "official". You have a few options:
1) Download the new firmware .tar file and flash it from ODIN and re-root, or flash with Mobile ODIN and use everRoot option. You will still need to install a custom recovery again after either way. Firmware can be found here: http://forum.xda-developers.com/showthread.php?t=2269304
2) Resort to stock ROM, remove root and see if device status shows "official" and try the "check for updates" under about phone to try for the OTA. Having a custom recovery may prevent this from working.
3) Try these methods for getting back to device status "official" to attempt the OTA: http://forum.xda-developers.com/showthread.php?t=2296014
Again having a custom recovery may prevent any of those methods from working.
4) If all you want is the new modem from the latest MG1 firmware then sit tight as someone is trying to extract just that as a flashable .tar as of this post.
blyndfyre said:
Probably not, if your device status in about menu says "custom" instead of "official". You have a few options:
1) Download the new firmware .tar file and flash it from ODIN and re-root, or flash with Mobile ODIN and use everRoot option. You will still need to install a custom recovery again after either way. Firmware can be found here: http://forum.xda-developers.com/showthread.php?t=2269304
2) Resort to stock ROM, remove root and see if device status shows "official" and try the "check for updates" under about phone to try for the OTA. Having a custom recovery may prevent this from working.
3) Try these methods for getting back to device status "official" to attempt the OTA: http://forum.xda-developers.com/showthread.php?t=2296014
Again having a custom recovery may prevent any of those methods from working.
4) If all you want is the new modem from the latest MG1 firmware then sit tight as someone is trying to extract just that as a flashable .tar as of this post.
Click to expand...
Click to collapse
Thanks! I tried step 3 (didn't work, probably cause of custom recovery like you said). In the process of DLing the new tar file (step 1). Do I have to clean install (wipe everything) when I update using the .tar file on mobile ODIN? I have a nandroid and tibu backups just in case.
serkan5000 said:
Thanks! I tried step 3 (didn't work, probably cause of custom recovery like you said). In the process of DLing the new tar file (step 1). Do I have to clean install (wipe everything) when I update using the .tar file on mobile ODIN? I have a nandroid and tibu backups just in case.
Click to expand...
Click to collapse
You do not have to wipe anything, however the process of flashing the stock firmware .tar will remove your custom recovery and restore the stock recovery. You will also loose root unless you use the everRoot option.
You can always re-root using CF-AutoRoot if you use ODIN or if the everRoot option of Mobile Odin doesn't work. Check here for CF-AutoRoot:
http://forum.xda-developers.com/showthread.php?t=2293800
After you have root you can then restore your Titanium Backup
Lastly you will have to re-install your custom recovery.
NOTE: In your case you are looking for the Rogers latest stock ROM you could just flash this ROM from Ib4STID directly from custom recovery, however it does not contain the updated modem. Find that ROM here:
http://forum.xda-developers.com/showthread.php?p=43870256#post43870256
blyndfyre said:
You do not have to wipe anything, however the process of flashing the stock firmware .tar will remove your custom recovery and restore the stock recovery. You will also loose root unless you use the everRoot option.
You can always re-root using CF-AutoRoot if you use ODIN or if the everRoot option of Mobile Odin doesn't work. Check here for CF-AutoRoot:
http://forum.xda-developers.com/showthread.php?t=2293800
After you have root you can then restore your Titanium Backup
Lastly you will have to re-install your custom recovery.
NOTE: In your case you are looking for the Rogers latest stock ROM you could just flash this ROM from Ib4STID directly from custom recovery, however it does not contain the updated modem. Find that ROM here:
http://forum.xda-developers.com/showthread.php?p=43870256#post43870256
Click to expand...
Click to collapse
The modem will probably help with lte speeds and reception, so I'll stick to the .tar on the official firmwares page!
I have a rogers I337M running Omega v9 (an i9505 rom based on MGA) with Adam Kernel 1.5 (an i9505 custom kernel also MGA). My phone still has the original MDJ modem/baseband. I would like a flashable MG1 modem, recovery based zip or mobile/odin flashable or whatever.
trueking7 said:
I have a rogers I337M running Omega v9 (an i9505 rom based on MGA) with Adam Kernel 1.5 (an i9505 custom kernel also MGA). My phone still has the original MDJ modem/baseband. I would like a flashable MG1 modem, recovery based zip or mobile/odin flashable or whatever.
Click to expand...
Click to collapse
I will post a link to one here as soon as possible. It will probably be a .tar ODIN/mobileODIN flashable file.
Installed newest firmware .tar file using Odin (didn't have to reinstall apps!), flashed CF Auto Root, installed custom recovery and phone is back in action!
serkan5000 said:
Installed newest firmware .tar file using Odin (didn't have to reinstall apps!), flashed CF Auto Root, installed custom recovery and phone is back in action!
Click to expand...
Click to collapse
Glad to hear it! Now let's hope this new modem provides better signal and faster LTE speeds. :good:
I would like to know if anyone thinks there will be a problem if I do the following:
1) Use ODIN to flash the new MG1 firmware (rom/kernel/modem)
2) Use ODIN to flash custom recovery (TWRP)
3) Use TWRP to restore my backup including custom rom/kernel
I would just wait for the modem but I am impatient....
trueking7 said:
I would like to know if anyone thinks there will be a problem if I do the following:
1) Use ODIN to flash the new MG1 firmware (rom/kernel/modem)
2) Use ODIN to flash custom recovery (TWRP)
3) Use TWRP to restore my backup including custom rom/kernel
I would just wait for the modem but I am impatient....
Click to expand...
Click to collapse
That will be fine. I just get TWRP from Play store via GooManager but flashing is fine too.
I think before Odin the twrp you need to root it first.....
Sent from my SGH-I337M using xda premium
hlucky said:
I think before Odin the twrp you need to root it first.....
Sent from my SGH-I337M using xda premium
Click to expand...
Click to collapse
Nope. I did exactly as stated. It worked perfectly. I did speedtest on wifi + lte, all is well =)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Galaxy S4 running Omega v9 with Adam kernel 1.5 : good :
trueking7 said:
Nope. I did exactly as stated. It worked perfectly. I did speedtest on wifi + lte, all is well =)
Sent from my Galaxy S4 running Omega v9 with Adam kernel 1.5 : good :
Click to expand...
Click to collapse
Ok then,
Luc
Has anyone tried mobile Odin option I have downloaded Telus and bell and want to keep root which one has less carrier bloat
Kjc99 said:
Has anyone tried mobile Odin option I have downloaded Telus and bell and want to keep root which one has less carrier bloat
Click to expand...
Click to collapse
Telus had only one bloat app and no boot animation.
Sent from my SGH-I337M using xda premium
serkan5000 said:
Installed newest firmware .tar file using Odin (didn't have to reinstall apps!), flashed CF Auto Root, installed custom recovery and phone is back in action!
Click to expand...
Click to collapse
Did you flash CF-Root right after the MG1 flash? or did you Flash MG1 reboot the phone and then flash CF-Root?
kiru said:
Did you flash CF-Root right after the MG1 flash? or did you Flash MG1 reboot the phone and then flash CF-Root?
Click to expand...
Click to collapse
I prefer to use Mobile Odin Pro, which allows you to inject root during the flash. That's what I did with this firmware.
If you use ODIN on PC I would personally let it reboot, set up the phone as usual and then follow CF-AutoRoot procedure.
blyndfyre said:
I prefer to use Mobile Odin Pro, which allows you to inject root during the flash. That's what I did with this firmware.
If you use ODIN on PC I would personally let it reboot, set up the phone as usual and then follow CF-AutoRoot procedure.
Click to expand...
Click to collapse
for some reason mobile odin pro never worked on this canadian phone for me properly. notified chainfire but without response or fix.
always fails to flash csc propperly. worked wonders in the past on other galaxies and probably still does for international but now i just avoid it because of this.
can you check with root explorer whether you even have csc propper folder after using mobile odin on canadian model?
Hi Everyone,
I hope this thread qualifies for the General section. I think it's certainly more than a Q & A question.
In short, my goal is to upgrade to the official Canadian NC1 (4.4.2) release without updating to the Knox-enabled bootloader (I'm currently on MG1 which doesn't have the Knox Warranty Void counter). This is to be completed with the intention of staying as close to stock as possible. I've come up with this strategy in my head during the past few days and was hoping that someone could review for soundness. If this works out, I'm also hoping that this helps others that are looking for something similar.
Prerequisites
Rooted MG1 (or MDJ)
Custom recovery
Heimdall working
Steps
Boot into recovery create a full backup of all partitions
Download NC1 TAR (http://www.sammobile.com/firmwares/3/?download=26591)
Extract system.img.ext4 from TAR
Flash system.img.ext4 with Heimdall
Code:
heimdall flash --SYSTEM "C:\path\to\system.img.ext4" --no-reboot
As we cannot use the stock NC1 kernel (from what I've learned, the new kernel doesn't work with the old non-Knox bootloader), flash a custom kernel. According to this custom ROM based on NC1, Wanam's Adam Kernel from the international section appears to work well. As a bonus, it looks like the kernel package also includes SuperSU and the su binary. So, flash the custom kernel in the custom recovery (which should still be intact as we haven't played with the recovery partition)
Wipe cache and dalvik
Reboot and hope for this best
Note: nothing else from the NC1 package is being flashed, just the system (and not the radio, NON-HLOS, etc)
I'd love to hear what everyone thinks. Are there missing steps? Am I setting myself up for a brick/nightmare scenario?
Thanks!
Hi there. I have i337m with fido. I didnt have to go to this route to obtain nc1. Im still on mg1 bootloader. I was at nc1 rom earlier but now using skyfall nbe rom.
Not to disregard your guide but here are the steps i took which is easier i think for most people.
Download ib4stid mapleleaf nc1 rom.
Download tmo kt kernel.
Download nc1 modem. Dont need nonholos. Just modem.bin
Download Odin 3.09 if you dony have it yet.
Go to download mode. Open odin. Connect usb. Untick auto reboot. Put modem.bin on CP. Flash. Disconnect. Reboot straight to download mode again. Flash modem again. Reboot to cwm.
Flash rom and kernel.
Reboot and ur done.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from i337m GS4
j_r17ca said:
Hi there. I have i337m with fido. I didnt have to go to this route to obtain nc1. Im still on mg1 bootloader. I was at nc1 rom earlier but now using skyfall nbe rom.
Not to disregard your guide but here are the steps i took which is easier i think for most people.
Download ib4stid mapleleaf nc1 rom.
Download tmo kt kernel.
Download nc1 modem. Dont need nonholos. Just modem.bin
Download Odin 3.09 if you dony have it yet.
Go to download mode. Open odin. Connect usb. Untick auto reboot. Put modem.bin on CP. Flash. Disconnect. Reboot straight to download mode again. Flash modem again. Reboot to cwm.
Flash rom and kernel.
Reboot and ur done.
...
Sent from i337m GS4
Click to expand...
Click to collapse
Thanks for posting but your ROM (Skyfall, I think) is custom. This means that it has been modified and changed from the stock Samsung ROM. If I am correct (and I'm still waiting for confirmation), the process I documented should give you a near-stock NC1 experience (sans the kernel).
theSpam said:
Thanks for posting but your ROM (Skyfall, I think) is custom. This means that it has been modified and changed from the stock Samsung ROM. If I am correct (and I'm still waiting for confirmation), the process I documented should give you a near-stock NC1 experience (sans the kernel).
Click to expand...
Click to collapse
Yes it does. I was using visionx nc1 stock version before i flash skyfall. Your process is very good. It was not specified at the OP that if anyone want a stock rom this is the process of doing it. Sorry bud
Sent from i337m GS4
j_r17ca said:
Hi there. I have i337m with fido. I didnt have to go to this route to obtain nc1. Im still on mg1 bootloader. I was at nc1 rom earlier but now using skyfall nbe rom.
Not to disregard your guide but here are the steps i took which is easier i think for most people.
Download ib4stid mapleleaf nc1 rom.
Download tmo kt kernel.
Download nc1 modem. Dont need nonholos. Just modem.bin
Download Odin 3.09 if you dony have it yet.
Go to download mode. Open odin. Connect usb. Untick auto reboot. Put modem.bin on CP. Flash. Disconnect. Reboot straight to download mode again. Flash modem again. Reboot to cwm.
Flash rom and kernel.
Reboot and ur done.
Sent from i337m GS4
Click to expand...
Click to collapse
I have the same phone on the Aio network. Do I need both the tmobile kernel and the nc1 modem. Or can I just flash the modem?
I'm trying to work thought some odd issues. Random slowness and freezing, camera fails on opening.
What network are you two on?
j_r17ca said:
Hi there. I have i337m with fido. I didnt have to go to this route to obtain nc1. Im still on mg1 bootloader. I was at nc1 rom earlier but now using skyfall nbe rom.
Not to disregard your guide but here are the steps i took which is easier i think for most people.
Download ib4stid mapleleaf nc1 rom.
Download tmo kt kernel.
Download nc1 modem. Dont need nonholos. Just modem.bin
Download Odin 3.09 if you dony have it yet.
Go to download mode. Open odin. Connect usb. Untick auto reboot. Put modem.bin on CP. Flash. Disconnect. Reboot straight to download mode again. Flash modem again. Reboot to cwm.
Flash rom and kernel.
Reboot and ur done.
Sent from i337m GS4
Click to expand...
Click to collapse
Why does one have to install a different MODEM and KERNEL on top of the MAPLE ROM, when the Maple ROM is already built for the i337m?
Total S4 noob, please help, thx!!!!:silly:
Because modem is not included in the rom. Ktkernel is just my recommendation. Ive beed using his kernel since i started using galaxy phone. Modem is rewuired if you are going to flash 4.3 or 4.4 rom or you will have problems with data drops and Signal loss.
Sent from i337m GS4
Ktkernel doesn't exist for 4.4 TW ROM only for 4.3 TW or ASOP. Or am i missing something?
klau1 said:
Ktkernel doesn't exist for 4.4 TW ROM only for 4.3 TW or ASOP. Or am i missing something?
Click to expand...
Click to collapse
Yes it does. At&t tmo and international. Im using the one in tmo section.
Sent from i337m GS4
j_r17ca said:
Because modem is not included in the rom. Ktkernel is just my recommendation. Ive beed using his kernel since i started using galaxy phone. Modem is rewuired if you are going to flash 4.3 or 4.4 rom or you will have problems with data drops and Signal loss.
Sent from i337m GS4
Click to expand...
Click to collapse
Maple runs perfectly fine as is with the new NC1 modem, also if you want to get rid of the samsung apps, check the add on section there is a zip for that....
worked flawlessly
Thank youS @j_r17ca for the alternative steps and @theSpam for raising the issue and for providing the clever workflow.
i had been struggling with getting signal when flashing kk roms on my then MG1 baseband on my i337m, and now it is perfect
Worked great here too. Stronger signals as well.
j_r17ca said:
Hi there. I have i337m with fido. I didnt have to go to this route to obtain nc1. Im still on mg1 bootloader. I was at nc1 rom earlier but now using skyfall nbe rom.
Not to disregard your guide but here are the steps i took which is easier i think for most people.
Download ib4stid mapleleaf nc1 rom.
Download tmo kt kernel.
Download nc1 modem. Dont need nonholos. Just modem.bin
Download Odin 3.09 if you dony have it yet.
Go to download mode. Open odin. Connect usb. Untick auto reboot. Put modem.bin on CP. Flash. Disconnect. Reboot straight to download mode again. Flash modem again. Reboot to cwm.
Flash rom and kernel.
Reboot and ur done.
Sent from i337m GS4
Click to expand...
Click to collapse
I'd like to mark this for my stock rom/MG1/4.2.2, thanks
http://www.android.gs/galaxy-tab-3-8-0-wi-fi-android-4-4-2-ota-update-available-for-installation/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Warning!!!
Locked boot-loader, once you flash this update you cant downgrade (at Present)
Rom has no knox counter ( warranty Bit) or binary counter.
Rom used to downgrades was T310XXUAMF1_T310OXXAMF1_HOME.tar
Another safe way of trying this rom without fear, is flashing it with mobile odin,mobile odin does not flash boot-loaders so you are safe to downgrade etc.
you may find that you WiFi does not work when rom flashed with mobile odin, that means that the older boot loader is not compatible with the new rom.
Update 1
Once You flash the rom the device will reboot several times, because my previous rom was customized i had to perform a hard reset.
this rom has some kind of KNOX according to superuser
The rom also adds a new entry to download mode AP SWREV: A1
How to root?
download Cf-auto-root from here and flash it via odin then go to google play and install superuser from chainfire, launch it and update normally.
UPDATE 2...
Rom has a watered down version of knox but no common KNOX entrie in download mode.
Q:Can i install a custom recovery is this rom?
A: YES.
what we really want to know is does this update have the locked bootloader? If so, then you may possibly forever be stuck with touchwiz and stock based ROMs..
DigitalMD said:
what we really want to know is does this update have the locked bootloader? If so, then you will forever be stuck with touchwiz and stock based ROMs..
Click to expand...
Click to collapse
how could we find out? try to downgrade to 4.2 via odin or simply flash custom rom see?
HavokbyName said:
how could we find out? try to downgrade to 4.2 via odin or simply flash custom rom see?
Click to expand...
Click to collapse
Yes you could but be cautioned, that could lead to a bricked device. I'm not sure what a safe test would be.
DigitalMD said:
Yes you could but be cautioned, that could lead to a bricked device. I'm not sure what a safe test would be.
Click to expand...
Click to collapse
try flashing custom rom maybe through custom recovery, or does that have same risks?
I will try to downgrade and see what happens.
Warning!!!
Locked boot-loader, once you flash this update you cant downgrade (at Present)
Rom has no knox counter ( warranty Bit) or binary counter.
Rom used to downgrades was T310XXUAMF1_T310OXXAMF1_HOME.tar
Another safe way of trying this rom without fear, is flashing it with mobile odin,mobile odin does not flash boot-loaders so you are safe to downgrade etc.
you may find that you WiFi does not work when rom flashed with mobile odin, that means that the older boot loader is not compatible with the new rom.
Q:Can i install a custom recovery is this rom?
A: YES.
If I'm rooted, can I just install regular? No custom recovery. Just stock everything except rooted.
Sent from my XT1031 using XDA Free mobile app
Any views to get this ROM for 3G version of Galaxy Tab 3 8.0 ?
faria said:
Warning!!!
Locked boot-loader, once you flash this update you cant downgrade (at Present)
Rom has no knox counter ( warranty Bit) or binary counter.
Rom used to downgrades was T310XXUAMF1_T310OXXAMF1_HOME.tar
Another safe way of trying this rom without fear, is flashing it with mobile odin,mobile odin does not flash boot-loaders so you are safe to downgrade etc.
you may find that you WiFi does not work when rom flashed with mobile odin, that means that the older boot loader is not compatible with the new rom.
Q:Can i install a custom recovery is this rom?
A: YES.
Click to expand...
Click to collapse
did you brick your device in the process or did it just fail flashing & error out, or did it work but only flash 4.2 system leaving new bootloader intact?
so with this finding, just to be clear on this, no custom roms can be used for those who upgraded with new bootloader?
would it be possible to restore 4.2 rom backup of only system.img in custom recovery or will it not boot?
sorry for lots of q's
thebestiam said:
If I'm rooted, can I just install regular? No custom recovery. Just stock everything except rooted.
Sent from my XT1031 using XDA Free mobile app
Click to expand...
Click to collapse
Yes.
HavokbyName said:
did you brick your device in the process or did it just fail flashing & error out, or did it work but only flash 4.2 system leaving new bootloader intact?
so with this finding, just to be clear on this, no custom roms can be used for those who upgraded with new bootloader?
would it be possible to restore 4.2 rom backup of only system.img in custom recovery or will it not boot?
sorry for lots of q's
Click to expand...
Click to collapse
Yes I got what is called a semi brick when trying to downgrade the rom when flashing the bootloader partition. This is easily remedied by going into download mode and flashing kit kat.
The good news is once you got the new bootloader installed, it will be virtually impossible to brick your device by conventional means.
Yes, locked bootloader means you can't have custom kernels, but you can have customs recoveries and roms.
In theory yes, but as far as I know only bootloader above 4.3 are compatible with kit kat rom, it may work but you may find that certain drivers will nor work, like loss of wi-Fi may occur. I Know this from my experiences with the note 2 and s4.
abramq said:
Any views to get this ROM for 3G version of Galaxy Tab 3 8.0 ?
Click to expand...
Click to collapse
As far as I know, the 3g version of this rom has been out for several weeks acording the the interwebs.
faria said:
As far as I know, the 3g version of this rom has been out for several weeks acording the the interwebs.
Click to expand...
Click to collapse
Unfortunately no Sir
We have only 4.2.2
Hope Samsung will no forget about us...
abramq said:
Unfortunately no Sir
We have only 4.2.2
Hope Samsung will no forget about us...
Click to expand...
Click to collapse
http://www.android.gs/flash-officia...xuana1-firmware-for-samsung-galaxy-tab-3-8-0/
Yes I have just downloaded KITKAT 4.4.2 for my GALAXY Tab3 8.0 LTE SM-T315
Country: Baltic
PDA: T315XWUANA1
From sammobile
Link here
Sorry this link is still 4.2.2 jellybean link removed
UPDATE
@faria
ok, just restoring 4.2 system.img from twrp backup doesn't work, doesn't boot, blank screen after initial samsung logo, didn't try restoring 4.2 boot.img with it though, thought that had something to do with bootloader but reading up it doesn't appear to, so if i restored that as well maybe it would boot?
flashing custom roms like cm11.0 is still possible as you say & seems to work just fine using this new bootloader, even shows blackhawk kernel in settings/about, should this be possible as its custom kernel?
i didn't have to do anything at all different than when i was on 4.2, just flash custom rom through recovery as normal
no new entries in odin/download mode info screen, all lines still the same
now i don't feel so bad upgrading
@HavokbyName
Please download Device info from the playstore byjphilli85, run it and post your kernel version an boot-loader version.
I would not be suprised if we can also flash custom kernels to the tab as the Knox version the device have seems to be a watered down version.
Thanks for the feedback.
faria said:
http://www.android.gs/flash-officia...xuana1-firmware-for-samsung-galaxy-tab-3-8-0/
Click to expand...
Click to collapse
No, this is for T315 model (LTE). This is not the same as T311 (3G).
Anyway thanks for your reply!
faria said:
@HavokbyName
Please download Device info from the playstore byjphilli85, run it and post your kernel version an boot-loader version.
I would not be suprised if we can also flash custom kernels to the tab as the Knox version the device have seems to be a watered down version.
Thanks for the feedback.
Click to expand...
Click to collapse
here, running latest cm build to date:
Hello all, been running various roms on my wife's s3 for some time now but haven't been in for a while. The current one is having some issues but I am not familiar with this d2vzw-d2lte switch that has happened recently or how it affects my ROM prospects for her phone.
Current setup is rooted with I3VRBLK3 baseband and VRUCML1 Build.
I've looked around but am still confused about how to update to current base and build but retain root properly. Any links or help would be greatly appreciated!
n2imagination said:
Hello all, been running various roms on my wife's s3 for some time now but haven't been in for a while. The current one is having some issues but I am not familiar with this d2vzw-d2lte switch that has happened recently or how it affects my ROM prospects for her phone.
Current setup is rooted with I3VRBLK3 baseband and VRUCML1 Build.
I've looked around but am still confused about how to update to current base and build but retain root properly. Any links or help would be greatly appreciated!
Click to expand...
Click to collapse
D2lte is for AOSP roms. Just want to be clear, are you seeking to use AOSP or TouchWiz? TouchWiz roms use either "d2vzw" or "Sch-i535" model name.
AOSP roms go by "d2vzw" or "d2lte." AOSP has moved to "d2lte" since about May, so most if not all AOSP roms that are still being updated should be found under "d2lte" model name now. They are named "d2lte" because the zip has consolidated d2tmo, d2att, d2spr, d2vzw (4 big US carriers) and several other smaller carriers into one zip. We all flash the same zip and the zip installs the proper files per carrier.
So, what do you want to update specifically?
SlimSnoopOS said:
D2lte is for AOSP roms. Just want to be clear, are you seeking to use AOSP or TouchWiz? TouchWiz roms use either "d2vzw" or "Sch-i535" model name.
AOSP roms go by "d2vzw" or "d2lte." AOSP has moved to "d2lte" since about May, so most if not all AOSP roms that are still being updated should be found under "d2lte" model name now. They are named "d2lte" because the zip has consolidated d2tmo, d2att, d2spr, d2vzw (4 big US carriers) and several other smaller carriers into one zip. We all flash the same zip and the zip installs the proper files per carrier.
So, what do you want to update specifically?
Click to expand...
Click to collapse
I guess my confusion comes from the fact that I wanted to update to a 4.4 AOSP rom but read that I needed to upgrade baseband which would lock me into always being on 4.4 roms in future and if not done correctly could lose root. Maybe I am reading too much into it?
n2imagination said:
I guess my confusion comes from the fact that I wanted to update to a 4.4 AOSP rom but read that I needed to upgrade baseband which would lock me into always being on 4.4 roms in future and if not done correctly could lose root. Maybe I am reading too much into it?
Click to expand...
Click to collapse
You are misinterpreting. The latest firmware that we can safely install and keep our unlocked bootloader is VRBMF1. The firmware includes about 7 partitions which Invisiblek outlines here and he provides a synopsis that is very well put. His links have been done for some time btw.
VRBMF1 firmware + VRUCML1 modem, VRBMF1 firmware, or VRBMB1 firmware are the only combos that anyone should really be using with an unlocked bootloader.
I'm in a similar position here, as I've not even touched the software on my phone for months. I'm not even sure how to determine my current Kernel and modem versions. Here's what I'm running:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have recently started having some issues with the phone and would like to upgrade to from CM10.2 nightly to CM11 M7. I'm okay to do a full wipe and whatever else is required. I'm also confused about the exact steps here. Do I need to download and install the firmware first, then update the modem, and THEN finally the rom?
All the links I go to warn me in big red letters about bricks and locked bootloaders. Is there any step by step guide for people going form 10.2 nightlies on a d2vzw to a cm11 release on d2lte? Thanks!
spanyam said:
I'm in a similar position here, as I've not even touched the software on my phone for months. I'm not even sure how to determine my current Kernel and modem versions. Here's what I'm running:
I have recently started having some issues with the phone and would like to upgrade to from CM10.2 nightly to CM11 M7. I'm okay to do a full wipe and whatever else is required. I'm also confused about the exact steps here. Do I need to download and install the firmware first, then update the modem, and THEN finally the rom?
All the links I go to warn me in big red letters about bricks and locked bootloaders. Is there any step by step guide for people going form 10.2 nightlies on a d2vzw to a cm11 release on d2lte? Thanks!
Click to expand...
Click to collapse
That firmware is super old, you're going to have to do some digging to find recent firmware. Then follow these steps.
1) update your recovery to the latest cwm, twrp, or philz.
2) find the whole MF1 firmware package, and preferably an ML1 modem (not the firmware). Download both
3) download the cyanogen rom you want to flash, a recent kernel is included in that download. No need to manually update.
4) open your recovery. Then factory reset, wipe cache, wipe dalvik cache, then format system.
5) flash your rom, followed by your gapps, followed by the MF1 firmware, followed by the ML1 modem only (not the firmware). Order on this is important.
6) if you have duplicate data, you need to eventually format your internal SD card, but it may not be necessary. You should backup anything you want to keep first.
All the warning red text everywhere is for people on the 4.3 firmware which is ML1 firmware and above. You have the LF2 firmware which is about 2 years old. You should actually be looking at all the old guides linked in the original sticky thread.
Just don't accept an OTA on a stock rom and you have nothing to worry about. It really doesn't matter when you flash the firmware, just make sure you go MF1 to ML1 modem, if you go the opposite way you'll erase the ML1 modem.
Just so you know, flashing radios does not require a wipe so you can do it anytime you want. Do it first or do it last, or do it after you boot up the rom so you don't forget something. That's what I do if I'm flashing a bunch of stuff at once.
MF1 Firmware -- http://www.androidfilehost.com/?fid=23329332407591785
ML1 Modem -- http://www.androidfilehost.com/?fid=23329332407591786
BadUsername said:
That firmware is super old, you're going to have to do some digging to find recent firmware. Then follow these steps.
1) update your recovery to the latest cwm, twrp, or philz.
2) find the whole MF1 firmware package, and preferably an ML1 modem (not the firmware). Download both
3) download the cyanogen rom you want to flash, a recent kernel is included in that download. No need to manually update.
4) open your recovery. Then factory reset, wipe cache, wipe dalvik cache, then format system.
5) flash your rom, followed by your gapps, followed by the MF1 firmware, followed by the ML1 modem only (not the firmware). Order on this is important.
6) if you have duplicate data, you need to eventually format your internal SD card, but it may not be necessary. You should backup anything you want to keep first.
All the warning red text everywhere is for people on the 4.3 firmware which is ML1 firmware and above. You have the LF2 firmware which is about 2 years old. You should actually be looking at all the old guides linked in the original sticky thread.
Just don't accept an OTA on a stock rom and you have nothing to worry about. It really doesn't matter when you flash the firmware, just make sure you go MF1 to ML1 modem, if you go the opposite way you'll erase the ML1 modem.
Just so you know, flashing radios does not require a wipe so you can do it anytime you want. Do it first or do it last, or do it after you boot up the rom so you don't forget something. That's what I do if I'm flashing a bunch of stuff at once.
Click to expand...
Click to collapse
Thanks so much for the info. I am bookmarking this for later use. Considering that I might have to format the SD card, I will hold off on doing this till I get a new phone later this summer (2 years is up already). Once I have a newer primary phone, I'll play to my heart's content with the old GS3.
Need help with rooting G920I with the following detail including firmware version details, etc.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tried CF-Auto Root but Odin messed it up somehow, phone got stuck on the emergency mode option and smart switch or kies could not help. I also tripped the knox flag but no luck with rooting still. Can someone please help with procedure to root G920I
I have the same problem, need help with this
I think cf autoroot doesn't work with that version of firmware. I read somewhere that you have to flash both modem and bootloader from older fw version.
There's is a thread talking about bootloader of g920i
Sent from my SM-G920I using Tapatalk
Fix
I had the same problem with the 920i dol5 firmware, here is the fix I did
I downloaded an older firmware from Sam mobiles. I believe I got the doj6 firmware which was just before dol5
Then I flashed that firmware through odin and I was able to flash twrp without getting stuck in boot loop and I was able to flash roms and kernels without any problem
I have tried many methods but this is the only one which works the best
chubutnet said:
I think cf autoroot doesn't work with that version of firmware. I read somewhere that you have to flash both modem and bootloader from older fw version.
There's is a thread talking about bootloader of g920i
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
Do you have a link or a fix related to the bootloader issue with G920I?
Udabanga said:
I had the same problem with the 920i dol5 firmware, here is the fix I did
I downloaded an older firmware from Sam mobiles. I believe I got the doj6 firmware which was just before dol5
Then I flashed that firmware through odin and I was able to flash twrp without getting stuck in boot loop and I was able to flash roms and kernels without any problem
I have tried many methods but this is the only one which works the best
Click to expand...
Click to collapse
So you flashed TWRP directly after DOJ6 using odin? How did you achieve root access then? Need help mate. If you can provide links as well it will be a great help!
pranav148 said:
So you flashed TWRP directly after DOJ6 using odin? How did you achieve root access then? Need help mate. If you can provide links as well it will be a great help!
Click to expand...
Click to collapse
I downloaded twrp 3.0.0 from from the official twrp site: https://twrp.me/devices/samsunggalaxys6.html
And yes flash TWRP through through odin after getting DOJ6 firmware and then flashed XtreStoLite rom(through twrp fyi)which gave instant root. You can also twrp flashable uni-kernel to get root access on stock firmware
Unikernel: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
Flashing CF-autoroot may most probbably work after flashing DOJ6 firmware but I didn't try it.However flashing cf-root or anything with dol5 firmware is certainly going to result in a boot loop, so that is why I recommend to flash older DOJ6 firmware or waiting for the latest MM firmware(this is what I planned to do but MM is still not available after waiting for almost 3 months)
920i roms ???
Udabanga said:
I downloaded twrp 3.0.0 from from the official twrp site: https://twrp.me/devices/samsunggalaxys6.html
And yes flash TWRP through through odin after getting DOJ6 firmware and then flashed XtreStoLite rom(through twrp fyi)which gave instant root. You can also twrp flashable uni-kernel to get root access on stock firmware
Unikernel: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
Flashing CF-autoroot may most probbably work after flashing DOJ6 firmware but I didn't try it.However flashing cf-root or anything with dol5 firmware is certainly going to result in a boot loop, so that is why I recommend to flash older DOJ6 firmware or waiting for the latest MM firmware(this is what I planned to do but MM is still not available after waiting for almost 3 months)
Click to expand...
Click to collapse
can u pls tell me which custom roms i can flash over my indian s6 (920i) ??? becoz i have seen almost every rom is developed for international variant (920F) !!
Abrar123 said:
can u pls tell me which custom roms i can flash over my indian s6 (920i) ??? becoz i have seen almost every rom is developed for international variant (920F) !!
Click to expand...
Click to collapse
check here, new version of this rom the developer explain how to root and all the bootloader thing
http://forum.xda-developers.com/gal...onprojectrom-v1-0-g920i-28-aug-t3188919/page8
pranav148 said:
Need help with rooting G920I with the following detail including firmware version details, etc.
tried CF-Auto Root but Odin messed it up somehow, phone got stuck on the emergency mode option and smart switch or kies could not help. I also tripped the knox flag but no luck with rooting still. Can someone please help with procedure to root G920I
Click to expand...
Click to collapse
Do not try CF-Autoroot, it doesn't work, so solution, please head over to sammobile and download rom which has a baseband version of "G920IDVU3DOK9", at sammobile you can see this (PDA), download this rom and install it using ODIN, once you are done, again come back to XDA forum and download unikernel "S6_UniKernel_v8-0002-ODIN" (link - http://forum.xda-developers.com/gal...d-development/kernel-stockmod-kernel-t3100395), download the one which says ODIN flashable, now once you are done, go back to download mode and flash it using ODIN, once it finishes the installation, you are good to go, while booting the device, one the top left corner you would see a message saying kernel is not seandroid enforcing, no worries, your device will boot up, this is it, your S6 is rooted, please be noted that this works for Indian version phone (SM-G920I), I am not sure with other models, hope this helps, feel free to question if any help needed.
i was on dol5 firmware and followed this guide:
http://forum.xda-developers.com/galaxy-s6/general/galaxy-s6-root-5-1-1-variants-t3147074
It got me into endless bootloop, so i flashed SBOOT_SM-G920I_OJ6 with ODIN phone is up and rooted......