On some ROMS I noticed that they require certain bootloaders and modems and they need to be flashed by ODIN while others do not. I am confused as to why that is, i thought flashing a ROM via a custom recovery like TWRP would handle that for you.
At the moment, I am on Vision X's 5.0 lollipop ROM, and I want to get onto stock 5.1.1. So far I'm reading this post: http://forum.xda-developers.com/tmo.../compilation-s5-g900t-stock-firmware-t3042400
It looks like i need to flash 3 things, bootloader, modem and the rom via ODIN.
I am unclear as to where modems, bootloaders and roms go on ODIN. aka, what is BL, AP, CP, and CSC
I also plan on maybe trying out a CM ROM like this: http://forum.xda-developers.com/galaxy-s5/unified-development/rom-ressurrection-remix-mm-t3275340
From what I'm reading there the t-mobile samsung galaxy s5 is KLTE? So thats the version I would download, and then flash through a custom recovery?
Sorry for the barrage of questions, I am somewhat new to this device, and all the ROM posts I see seem to expect a level of understanding I don't have yet. Please go easy on me
uLose said:
On some ROMS I noticed that they require certain bootloaders and modems and they need to be flashed by ODIN while others do not. I am confused as to why that is, i thought flashing a ROM via a custom recovery like TWRP would handle that for you.
At the moment, I am on Vision X's 5.0 lollipop ROM, and I want to get onto stock 5.1.1. So far I'm reading this post: http://forum.xda-developers.com/tmo.../compilation-s5-g900t-stock-firmware-t3042400
It looks like i need to flash 3 things, bootloader, modem and the rom via ODIN.
I am unclear as to where modems, bootloaders and roms go on ODIN. aka, what is BL, AP, CP, and CSC
I also plan on maybe trying out a CM ROM like this: http://forum.xda-developers.com/galaxy-s5/unified-development/rom-ressurrection-remix-mm-t3275340
From what I'm reading there the t-mobile samsung galaxy s5 is KLTE? So thats the version I would download, and then flash through a custom recovery?
Sorry for the barrage of questions, I am somewhat new to this device, and all the ROM posts I see seem to expect a level of understanding I don't have yet. Please go easy on me
Click to expand...
Click to collapse
Hello,
Some custom roms are made to load after the base rom has been loaded. I assume this is because the developers use the base architecture to build the rom on. Also some custom roms dont include bootloaders and modems.
Furthermore twrp as of lately may have issues flashing modems and bootloaders that are included in roms, and this is why odin could be used to flash bootloaders and modems. Also when flashing a bootloader you might need to completely power down the device then power up into download mode. failure to do so could result in the flash not taking. Bootloader files would go into the BL slot while the rom would go into the ap slot. You should always check you current version after flashing to confirm that the flash actually took. you could do so with the samsung info app in the play store. I would also check that your Odin is up to date if your going to 5.1.1. Hope this helps a little.
destructionj said:
Hello,
Some custom roms are made to load after the base rom has been loaded. I assume this is because the developers use the base architecture to build the rom on. Also some custom roms dont include bootloaders and modems.
Furthermore twrp as of lately may have issues flashing modems and bootloaders that are included in roms, and this is why odin could be used to flash bootloaders and modems. Also when flashing a bootloader you might need to completely power down the device then power up into download mode. failure to do so could result in the flash not taking. Bootloader files would go into the BL slot while the rom would go into the ap slot. You should always check you current version after flashing to confirm that the flash actually took. you could do so with the samsung info app in the play store. I would also check that your Odin is up to date if your going to 5.1.1. Hope this helps a little.
Click to expand...
Click to collapse
I see. So bootloaders -> BL, roms -> AP, but what slot to modems go? Also, should I flash all three at once, or is it better to do each one at a time?
Thanks for your help!
uLose said:
I see. So bootloaders -> BL, roms -> AP, but what slot to modems go? Also, should I flash all three at once, or is it better to do each one at a time?
Thanks for your help!
Click to expand...
Click to collapse
you can grab the stuff you need here if your looking for the OJ4 stock rooted rom.
http://forum.xda-developers.com/tmo...o-update-to-g900tof6-5-1-1-pc-t3141404/page36
That modem file worked when loaded into the ap slot.
An alternitive would be to grab the full rom thats for odin. If you odin the full rom(1 file) then it should update the boot loader and modem. you would then be on a stock unrooted rom and would have to root the device yourself if you wanted root.
http://forum.xda-developers.com/tmo.../compilation-s5-g900t-stock-firmware-t3042400
I used the app (*Phone INFO ★Samsung★) to chek all 3 and make sure there correct. it will tell you under the FIRMWARE info tab.
http://forum.xda-developers.com/showpost.php?p=64154819&postcount=361
OR if your already rooted, you can simply follow the FlashFire method in the 1st link on page one as this claims to have better results for roms that include modems. If not then you odin them in afterwords with the files in the above 1st link. again thats if you want to go with OJ4 (newest as of this post).
Related
Ok, so as usual I'm a noob in android and got the GS2 as my first.
So I read a lot of stuff in this forum with the search function and came to learn about odin, pit files, modem, csc, pda and some other stuff, and I feel that I can soon do my rooting process however there are some things that I still do not understand and a little help would be appreciated
1 - So, there are kernels and there are ROMs, from what I understood ROM = firmware and that contains a whole new system, so does flashing a ROM also flashes a MODEM file?
2 - I'm from Brazil and so is my GS2, therefore I believe my MODEM file has configs to my country, so if I flash a ROM that'll screw my MODEM file too?
3 - how can I get a right MODEM file?
4 - I read about the ROM kitchen, and from my understanding you can create your own ROM, is there something available for GS2 too?
5 - Are there good ROMs for GS2 already? Or just kernels to get root?
6 - Is Odin used just in the rooting process of the S series?
Thanks!
Pauloxzak said:
Ok, so as usual I'm a noob in android and got the GS2 as my first.
So I read a lot of stuff in this forum with the search function and came to learn about odin, pit files, modem, csc, pda and some other stuff, and I feel that I can soon do my rooting process however there are some things that I still do not understand and a little help would be appreciated
1 - So, there are kernels and there are ROMs, from what I understood ROM = firmware and that contains a whole new system, so does flashing a ROM also flashes a MODEM file?
Full rom yes custom rom probably but depends whats been put in the rom .
2 - I'm from Brazil and so is my GS2, therefore I believe my MODEM file has configs to my country, so if I flash a ROM that'll screw my MODEM file too?
3 - how can I get a right MODEM file?
Stock rom unzip remove rom flash via Odin as Phone .
Stock Roms .and csc
http://forum.xda-developers.com/showthread.php?t=1075278
4 - I read about the ROM kitchen, and from my understanding you can create your own ROM, is there something available for GS2 too?
WAIT not long now .
5 - Are there good ROMs for GS2 already?
Plenty of roms but not a great deal of difference from stock as regards performance yet .
Or just kernels to get root?
kernels and also Kernels to root .
All in dev section .
6 - Is Odin used just in the rooting process of the S series?
Yes to flash the kernel with root and CWM .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
jje
Click to expand...
Click to collapse
Thanks for the info!
so, should I add the modem and csc files compatible with my country every time I flash a new rom?
Also, I read about killing all Kies processes to start with the rooting, that refers to the kies in the phone os the kies in pc?
Does installing Kies in pc already gives me all drivers? (I discovered just now that there are a Kies for PC )
Pauloxzak said:
Thanks for the info!
so, should I add the modem and csc files compatible with my country every time I flash a new rom?
Full rom yes but i would check first if rom has them inside as if not old will remain ,
Also, I read about killing all Kies processes to start with the rooting, that refers to the kies in the phone os the kies in pc?
Kies on the PC when connecting via ODIN .
Does installing Kies in pc already gives me all drivers? (I discovered just now that there are a Kies for PC :
Should give you the USB drivers required by Odin .
jje
Click to expand...
Click to collapse
My stats: Fairly comfortable with computer and other forms of tech, but have only recently began diving into the Android system. I have limited development/programming experience, however, I'm not a novice or noob to it but definitely not advanced. Importantly for those willing to help I understand most terminology and can follow instructions. Thanks in advance.
Phone Stats: AT&T Samsung Galaxy Note SGH-i717
Android Version: 2.3.6 (Gingerbread)
Baseband Version: i717UCLF6
Kernel Version: 2.6.35.11
Build number: GINGERBREAD.UCLA1
Root Access: Yes
Stock Rom: Unsure, bought online.
Carrier/Service Provider: Straight Talk (U.S.) Phone was previously used on the AT&T network exclusively, and done so with an AT&T provided SIM card. After I purchased it, I ordered a new SIM card from Straight Talk (U.S.) and reprogrammed the APN settings under their instruction in order for my phone service to work correctly, and have had no problems with that.
I can't stand being on Gingerbread any longer. I guess, since my phone is an AT&T phone but I'm using it through Straight Talk I can't get any of the OTA updates. I've tried downloading the OTA's several times, both, prior to and post Root access without success in either case.
So here are my questions:
1. Am I doing something incorrectly which might be keeping me from getting OTA updates? Please remember, I've tried downloading the OTA's several times both with and without Root Access and the conclusion is the same each time: "No Updates Available At This Time. Your Phone Appears To Be Up To Date. Try Again In 24hrs."
2. Is my only option at this point to manually update to a newer firmware? If so, should I update to a newer STOCK version or a custom ROM version?
3. If a manual update is the option, after reading my above outline of my own experience with the Android system, what would be way to go? Simple, not overly complex yet doesn't assume the user is either a complete moron or can write code in his sleep. I've checked into a couple of options. Rom Manager seems like it would be a nice route to go, but in the Recovery Setup portion I basically get told I can't use that application because my specific device isn't supported.
I checked out GooManager and, unless it's just me, it seems like it's an app that likes to do all the work without telling you what it's doing exactly, but when it does ask me or tell me information, I'm not always sure how to answer or react to it's warnings.
Plus, I've noticed that sometimes when downloading a ROM, sometimes I have to "flash" the gapps myself and other times I don't.
4. Is it easier to download everything separately and apply them one by one, for example the ROM then gapps then Kernal...etc? Or look for something that has it all in one package?
I have a laptop in which I can download/transfer programs and apps between it and my Note so download space and internet access isn't a problem.
Also, it most likely isn't information that is going to help in anyway, but I live in Oklahoma, United States of America.
Thanks for all the feedback...UnluckyOnion
I'm not answering these in any specific order,
As I kinda just sped read thru most of it...
Since you're rooted, or know how to, goomanager is superior to Rom manager.
It supports this device and has a current version of twrp to install, instead of an outdated cwm.
Just use it to install recovery, then boot your device into recovery and use that. Not the app. You'll be provided with much more information and this is the preferred way of flashing.
Official Updates are always "manual" either with a less than user friendly program called kies, or with a less annoying way (which you may be familiar with seeing as you've rooted) ODIN. Both pc programs used with the phone in download mode connected with usb cable.
Gapps are only needed to flash separately with an aosp based Rom as it's against Google's T.o.S. to include them in am entirely aftermarket compiled firmware, however if it's a Modified version of a stock based Rom (in this case TouchWiz) they can be, and thusly are, included within.
Official or custom is up to you really.
If official..just grab the .tar and flash it with Odin.
If custom, obtain a custom recovery either the way i mentioned above or downloading a .tar of twrp and use Odin to flash that.
Once you have a custom recovery, you'll simply be able to flash a Rom from there.
Roms include a kernel, if you want to use a different one than what is included, that would be flashed after the Rom.
After flashing you'll have to input your carriers apn settings in again.
studacris said:
I'm not answering these in any specific order,
As I kinda just sped read thru most of it...
Since you're rooted, or know how to, goomanager is superior to Rom manager.
It supports this device and has a current version of twrp to install, instead of an outdated cwm.
Just use it to install recovery, then boot your device into recovery and use that. Not the app. You'll be provided with much more information and this is the preferred way of flashing.
Official Updates are always "manual" either with a less than user friendly program called kies, or with a less annoying way (which you may be familiar with seeing as you've rooted) ODIN. Both pc programs used with the phone in download mode connected with usb cable.
Gapps are only needed to flash separately with an aosp based Rom as it's against Google's T.o.S. to include them in am entirely aftermarket compiled firmware, however if it's a Modified version of a stock based Rom (in this case TouchWiz) they can be, and thusly are, included within.
Official or custom is up to you really.
If official..just grab the .tar and flash it with Odin.
If custom, obtain a custom recovery either the way i mentioned above or downloading a .tar of twrp and use Odin to flash that.
Once you have a custom recovery, you'll simply be able to flash a Rom from there.
Roms include a kernel, if you want to use a different one than what is included, that would be flashed after the Rom.
After flashing you'll have to input your carriers apn settings in again.
Click to expand...
Click to collapse
Thanks for all the information and help...more importantly, thanks for taking the time. I have ODIN on my laptop and have always used it when needed but I saw a highly rated and positively commented Mobile version of ODIN in the Play Store that claims you can do everything from the convenience of your phone which sounds appealing, however it's kinda pricey, especially if it doesn't work. Would you recommend the mobile version or PC version? Also, I have been doing a lot of ROM and Root research as of late, and wondered something...Why so many different Galaxy Note's? It seems as though I have the least popular version with the most popular being from the Galaxy Note "N" series, specifically the N7000. If I download and use an application that says it's meant for the Galaxy Note N7000 and I use it on my Galaxy Note SGH-i717, what will happen? Nothing, something, brick, work perfectly, etc...?
The N series is not carrier branded and sold internationally, so naturally it's more popular compared to a north American variant.
DO NOT FLASH ANYTHING FOR THE N7000
IT WILL BRICK YOUR PHONE.
The international version has a different cpu, gpu and antenna, for north American LTE bands to work those key components needed to be different.
So I say again just to stress:
DO NOT FLASH ANYTHING FOR THE N7000
IT WILL BRICK YOUR PHONE.
As for Odin, you're either going to flashing a stock firmware, or if you choose a custom Rom, you'll only need Odin once to flash TWRP. Then all the rest will be done in recovery on the phone itself. No need for it after you've either manually updated to the latest stock rom, or flashed a recovery for use of custom roms
So... imo mobile Odin, though being nifty, is a bit pricey for how little you'll need it, whereas it's free on pc.
I don't think mobile Odin is even available for the i717. It's not listed in supported devices.
I tried installing mobile odin and it's not supported
Thanks for the reply. And an even bigger Thanks for downloading the app and checking. I admire sacrificing your own work just to help me out. So what about yourself? Would you suggest, advise or heed caution to anymore of my questions?
By the way, what are you two running?
As long as you read the op of threads and all other important posts that follow BEFORE ever touching your phone, I'd say try a custom Rom...if you decide you don't like any of them, you can Odin flash the stock jellybean firmware at any point.
I myself am running unofficial aokp compiled and posted by a fellow team member BlownFuze.
Oh yeah, how's it running? Nice and stable or crawling with bugs? Any key selling points?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
I'm on the stock 4.1.2 release and rooted.
Everything works, no bugs, but battery sucks. Even after removing and freezing useless processes a stock rom will never be as light and battery friendly as a custom rom.
I just upgraded to the same version. Planned on rooting over weekend. Any success since your last post? Do you nave preferred Root method?
Thanks
Unlucky Orion
Use Odin to flash twrp
Newest version of twrp "should" Sr that you're not rooted and ask if you would like to do so within recovery before booting back into the os.
If not, there's links to an su.zip to flash in twrp for root.
studacris said:
Use Odin to flash twrp
Newest version of twrp "should" Sr that you're not rooted and ask if you would like to do so within recovery before booting back into the os.
If not, there's links to an su.zip to flash in twrp for root.
Click to expand...
Click to collapse
Hey man, thanks, it worked like a charm. I appreciate the help from both you.
Hi all,
I am a newbie and don't know much. So please bear with me.
I was trying to root my Galaxy S5(SM-G900H) by using the tutorial given on http://forum.xda-developers.com/showthread.php?t=2696537 but the process did not go as planned as keep struck on recovery.img on odin3.10 so I googled and found that changing USB port will help so I take out the battery changed the port and try again but this time I soft-bricked the phone as odin struck on cache.img and now when i try to start my phone I get Firmware upgrade encountered. So now I again googled and found about unified toolkit and install it on my windows 10 ,now when i choose option 6 (i.e. flash stock boot image to your device) it says waiting for usb debugging to be enabled ,now I remember I turn USB debugging on but it is still struck here. Now what should I do? My parents gave this phone just a week ago and I am in deep trouble.
P.S.-I am only able go into the download mode not recovery mode.
Boot into Download Mode and use Odin to install the original firmware. Might require a factory reset after if still bootlooping. Here is a link to 6.0.1 from Sri Lanka https://mega.nz/#!YMAFhR4a!pZmf7OEWgzDzET1FLGsAOQ5XyVlvE8y4pJfB8KDNbMI . Any region firmware should work for the F model. If you want your specific one then check sammobile.com. I just linked to the other because it is a much faster download.
Problem encountred while installing original firmware
I tried to use Odin to install original firmware , I started the process but Odin got struck on sboot.bin (Also I read somewhere that whole process does not take more than 10 minutes). So please help me.
Which firmware did you try?
You might be able to use Kies to recover your device as well.
es0tericcha0s said:
Which firmware did you try?
You might be able to use Kies to recover your device as well.
Click to expand...
Click to collapse
I downloaded it from http://www.teamandroiders.com/samsung-galaxy-s5-sm-g900h-stock-rom-firmware/ with PDA: I9500XXUBOL2. I want to know one more thing as I am in India so should I use INU or INS?
ratcoder said:
I downloaded it from http://www.teamandroiders.com/samsung-galaxy-s5-sm-g900h-stock-rom-firmware/ with PDA: I9500XXUBOL2. I want to know one more thing as I am in India so should I use INU or INS?
Click to expand...
Click to collapse
Oh geez...no wonder it isn't working. i9500 = S4. Really gotta be careful with that kind of thing.
INU is for unlocked from the factory
INS is for phones from a carrier
Either one should work. As mentioned, with the G900h, any firmware should work that is for that model, no matter the region. Use the one I posted and change the language or grab the one for India from sammobile.com though it'll take an hour or 2.
Edit: I see that it was just mislabeled as i9500, but the download says g900h after all.
Were you on 5.1.1 or 5.0 before you started this process?
es0tericcha0s said:
Oh geez...no wonder it isn't working. i9500 = S4. Really gotta be careful with that kind of thing.
INU is for unlocked from the factory
INS is for phones from a carrier
Either one should work. As mentioned, with the G900h, any firmware should work that is for that model, no matter the region. Use the one I posted and change the language or grab the one for India from sammobile.com though it'll take an hour or 2.
Edit: I see that it was just mislabeled as i9500, but the download says g900h after all.
Were you on 5.1.1 or 5.0 before you started this process?
Click to expand...
Click to collapse
Well I downloaded another one from http://firmwarefile.com/samsung-sm-g900h the second one, before it all started I was on 5.0 and the link you give does not work anymore. Anyway I tried with the firmware with upper link. And Odin is struck with sboot.bin for more than an hour. And have no idea what's going on? So what should I do?
Also someone suggested to use Pit. Should I use it?
No, don't use the pit. Try the newer firmware for 6.0
es0tericcha0s said:
No, don't use the pit. Try the newer firmware for 6.0
Click to expand...
Click to collapse
So I downloaded the 3rd link from http://firmwarefile.com/samsung-sm-g900h for newer version and try Odin 11.2 with it. I try two times to flash the firmware first time it struck on sboot.bin and second time it just showed fails(I used Odin with administrative rights this time) .Please see the attached images. Please tell me what should I do now. I want to repair it ASAP.
Not sure. This is pretty standard stuff. Have used Odin 1000 times and haven't had that much trouble with it. Sorry.
es0tericcha0s said:
Not sure. This is pretty standard stuff. Have used Odin 1000 times and haven't had that much trouble with it. Sorry.
Click to expand...
Click to collapse
I think I should mention that the firmware I used was INS not INU and if you have a genuine link for version 6 for INU with fast download speed, please share it (different than sammobile because it has only fast speed only for premium users). Should I use PIT or try something else than Odin. Anything that might help please tell me. I have got this phone just a week ago and my parents are not gonna give me a new one so please help me.
I keep encountering sboot.bin error ,maybe there is a way to resolve it?
I'd just try to load TWRP and a custom rom at this point.
es0tericcha0s said:
I'd just try to load TWRP and a custom rom at this point.
Click to expand...
Click to collapse
Actually I have no idea what TWRP is so any link or anything that can help without ruining the situtation.
http://forum.xda-developers.com/galaxy-s5/development/rom-t3224562
es0tericcha0s said:
http://forum.xda-developers.com/galaxy-s5/development/rom-t3224562
Click to expand...
Click to collapse
I want to know one more thing on the above link there is a custom firmware and there is a custom ROM with bootloader and all. So should I flash custom firmware or use the instructions given on thread to flash custom ROM?
The custom rom does not include bootloader and modem. You will need to flash via Odin if you were not on the same firmware as the software is based off of. I would flash them anyway, to be safe. You can skip the root part as it is not need. Follow the instruction in post 2 for stock rom users minus the root part. Make sure to boot directly back into TWRP recovery before it attempts to boot. You can load rom on SD card and any additional add-ons you want. Plenty of youtube guides on how to use Odin to flash TWRP and such.
es0tericcha0s said:
The custom rom does not include bootloader and modem. You will need to flash via Odin if you were not on the same firmware as the software is based off of. I would flash them anyway, to be safe. You can skip the root part as it is not need. Follow the instruction in post 2 for stock rom users minus the root part. Make sure to boot directly back into TWRP recovery before it attempts to boot. You can load rom on SD card and any additional add-ons you want. Plenty of youtube guides on how to use Odin to flash TWRP and such.
Click to expand...
Click to collapse
Finally seen some progress, thank you very much. I successfully flashed TWRP recovery, but I got a couple of questions. Firstly I should flash ROM from recovery mode and then go to download mode to flash boot-loader and Modem files right? Should I flash ROM from SD card? And if this custom ROM causes problem is there a way to get to stock ROM? And is this custom ROM rooted or I have to root it via CF-Auto root or try anything else?
Rom might work without bootloader and modem. Just depends on your previous firmware. I would try and flash it though as it was recommended. Rom flash from SD card or internal. Either way should work. You will be able to go back to stock if you can find a firmware that works. It is already rooted.
es0tericcha0s said:
Rom might work without bootloader and modem. Just depends on your previous firmware. I would try and flash it though as it was recommended. Rom flash from SD card or internal. Either way should work. You will be able to go back to stock if you can find a firmware that works. It is already rooted.
Click to expand...
Click to collapse
Thank you very much.phone is working again with custom ROM.just one more thing if I upgrade from custom ROM what will happen?
:good::highfive::victory:
It should work to reflash the original firmware through Odin. Just get the one that matches your baseband version.
This is the Odin ROM for the PL1 update. Requires the the use of Odin, computer, and USB cable to use. This is the stock ROM pulled from Samsung Kies3. I've flashed it inside Odin, and it upgraded my device without wiping contents, but I cannot promise the same result for everyone.
To (re)root, follow this:
https://forum.xda-developers.com/note-3-sprint/general/how-to-root-note-3-lollipop-t3089382/page2
The file:
https://drive.google.com/file/d/0B2iEgzRTFjrQdlhNSlg5bkE4WVE/view?usp=drivesdk
So what does the PL1 update get you? Does it improve the radio modem operations? Is it just so it will work with Nougat?
It's a security update, that's all. Note 3 is done with OS upgrades. 5.0 will be the last official
Sent from my SAMSUNG-SM-G935A using Tapatalk
Hya there..
I have been following all your posts about flashing the PL1 update through either Odin or TWRP. I am familiar with both, but wanted to ask for insight on my particular setup.
Model SM 900P (Sprint)
Im still on 4.4.2 Kitkat Killer and has been doing well but looking to upgrade if I can find a good ROM.
I am still on baseband version NC5
Kernel 3.4.0 BeastMode
I figure I would be smart to flash the Baseband and Modem to the PL1 but would of course like to keep root and keep my TWRP recovery.
Ultimately I would like to flash the DarkLord ROM or even Resurrection Remix ROM for the Note 3 on CDMA (Sprint)
This is my daily driver, and cannot afford to frag my phone so I want to be sure I make the best choices.
If I follow your posts I would do best to downlowad your TWRP Stock Pre Root zip file, and simply "recover' the file as if I was doing any normal TWRP recovery. This would then put me back to Stock Lollipop and upgrade my Modem and Baseband and get me the latest security updates (well fairly recent anyways).
In lieu of that, I can ODIN the PL1 file offered by you and this would in effect 'factory reset' my phone as if I just bought it from Sprint (well you know what I mean) and would re install all my apps etc (through Titanium Backup etc).
From there I can try Resurrection or DarkLord Mod's and load them like any ROM install?
Thanks for double checking my train of thought...
Dave
Thanks! This helped me out.
@Unidave199 -
Use ODIN to push Greaper88's PL1 file to your phone. (now you are updated.) (I just used it, it works.)
Use ODIN to push a recovery to your phone like TWRP
Find yourself a ROM you like (Darklord's is good.)
Flash ROM via TWRP (Read the ROM's OP's entire instructions for flashing.)
Final step....Enjoy!
2manyhobbies said:
Thanks! This helped me out.
@Unidave199 -
Use ODIN to push Greaper88's PL1 file to your phone. (now you are updated.) (I just used it, it works.)
Use ODIN to push a recovery to your phone like TWRP
Find yourself a ROM you like (Darklord's is good.)
Flash ROM via TWRP (Read the ROM's OP's entire instructions for flashing.)
Final step....Enjoy!
Click to expand...
Click to collapse
I hope this is the right thread for this...
Pardon my ignorance here, it's been a few years since I frequented this forum, or even XDA...
Is this what I want to use to get back to total stock, unrooted for resale?
(I've been rocking the Note 3 since it came out, FINALLY upgraded to something newer, and want to sell this to a sprint user.)
Yes it is
Just use the "CSC" file and not the "HOME_CSC." This should completely reset the device and clear user data.
So, I cobbled together a (custom-recovery) flashable NC4 stock ROM.
I'm interested to find out whether it is possible to boot it successfully from later bootloader firmware - e.g. NK1, OB6, or OF1
(I'm still on NC4 bl and not planning on upgrading near term. It boots on NC4 bl but that's pretty obvious lol)
[size=+2]Q: Why would this be useful?
A: to provide a means for upgrading bootloader firmware without starting from scratch.[/size]
For instance, there are folks on OB6 firmware that would like to use a custom ROM that will only work on OF1 firmware. They can certainly start from scratch (backup and unload the entire device); an alternative would be to:
- Make a backup of an existing rooted ROM (that more than likely has a custom or modified boot image so is not bootable when the bootloader gets re-locked) using the currently-installed custom recovery (which will also be non-bootable under re-lock).
- Restore a (debloated) pure stock ROM w/ Samsung kernel. Root it with Towelroot (does not touch boot image)
- Flash replacement bootloader only in Odin. Locked bootloader = no custom recovery... but with a rooted stock ROM already in place with an unmodified stock kernel it can be immediately unlocked.
NC4 is easily rooted with Towelroot-v3 "on device". No need for PC drivers, online rooting tools with a separate PC, etc (e.g. as with Yemen rooting methods on OB6, OF1)
This approach in principle saves the need to backup everything up in the /sdcard - but you have to know in advance that the NC4 stock kernel and ROM can successfully be booted with later bootloaders.
So anyway, that's what I'm asking for help testing with - folks that are: (a) unlocked and (b) on NK1, OB6 or OF1 bootloader willing to try flashing a debloated NC4 Stock ROM using their existing custom recovery, and see if it boots, roots, and if root survives a single boot cycle.
Contact me via this thread or PM; I'll provide the flashable NC4 and the Towelroot .apk
.
my n900v came with 5.0 Of1 but i rooted, unlocked BL. installed twrp and flashfired NC4 tar minus recovery
runs smooth.I hate lollipop.lol
only bug is wifi password resets everytime i reboot
im curious as to why i have trouble running certain nc2/nc4 roms..some want to bootloop/freeze
baja,biggins,and objective rom
kernel issue maybe? or BL version
btw. i am rooted via towelroot v3
hotrod85z said:
my n900v came with 5.0 Of1 but i rooted, unlocked BL. installed twrp and flashfired NC4 tar minus recovery
runs smooth.I hate lollipop.lol
Click to expand...
Click to collapse
Thank you for posting that, very useful/helpful information to know.
Does Flashfire understand the Samsung "sparse" image format of the system.img.ext4 file inside the Stock (Odin) .md5 tarfile blob? Or maybe somebody else packaged up a "flashable .zip" of NC4?
hotrod85z said:
only bug is wifi password resets everytime i reboot
Click to expand...
Click to collapse
in /system/build.prop, set ro.securestorage.support=false and reboot. You might also want to set ro.config.tima=0 as well.
I suspect that mixing and matching Samsung kernels with bootloader versions breaks something in the TrustZone, and so secure containers and other sort-of-obscure security functions no longer work as the TZ smells something fishy. I am using a rooted PL1 rom on NC4 bl and it would spontaneously reboot (infrequently) until I made the above changes - it's been rock stable for about 4 days now. Why this works I can't really say - it's a "generation skipping" bootloader and stock rom combination - N* bootloader and P* ROM *
hotrod85z said:
im curious as to why i have trouble running certain nc2/nc4 roms..some want to bootloop/freeze
baja,biggins,and objective rom
kernel issue maybe? or BL version
btw. i am rooted via towelroot v3
Click to expand...
Click to collapse
all of the above or none of the above LOL
There are definitely some mysteries here, and I don't claim to fully understand the interdependence of the TZ (== bootloader firmware), the TIMA and RTKP stuff in the kernel, and the cross-communication between kernel and TZ via the qseecom service daemon (which is in the ROM in /system/bin) much less how the APIs of all these interfaces might have changed between major releases.
You could check those two build.prop settings in those ROMs for starters though. I suspect that if the TZ smells something fishy (e.g. a kernel TIMA to TZ info mismatch), a variety of secure credential services in the TZ stop working. It is possible that "ro.securestorage.support" is a toggle that attempts to use TZ services when it is set to "true", and so anything in the ROM which builds on it breaks because the TZ is refusing to play on an otherwise "stock" ROM variant.
FWIW I got the AryaMod (S7Edge MM port) + phantom kernel running on NC4 bl + OF1 modem for a full 24 hours after I disabled the qseecom service daemon. It ran long enough that I had customized the whole thing as a daily driver with all my apps, verified that all sensors & radios worked, made test calls, etc. Rebooted it and the kernel started getting reset by a "Modem Reset". Even weirder was that despite the use of the OF1 "modem" firmware, the kernel was reporting a bunch of RIL "unknown ioctl's". Strikes me as odd that the whole thing could run that long with so many different things happening, and then the "modem" is unhappy - even though other folks are using the ROM with OF1 bl + OF1 radio/modem firmware. (As if the "modem" isn't really the source of the problem, even though that's what initiates the device reset).
.
i initially tried flashing NC4 full tar via ODIN. but even bl unlocked. i got FAIL. flashfire worked!
very curious as to whether a custom n900v kernel would boot my 4.4.2 custom roms..its either that or the BL isnt compatible with non-touchwiz roms....
most of the kernel/modem/firmware links on here are 404 error dead links.. would be nice to see an up to date sticky. ill flash anything as long as i dont end up in JTAG mode with a brick.lol
ive played with verizon s5 atnt s2,galaxy capitivate,atrix 4g and many other phones
the s2 is still by far the fastest Smoothest phone on cm7..the newer the phones..the newer the OS..the bigger the resourse hogs"ram" im a minimalist...
even after flashing NC4 official full tar..im still showing OF1 baseband under settings
@hotrod85z
FWIW I posted a bunch of recovery-flashable stock ROMs here.
There is also a link in that thread to a complete set of (Odin flashable) modems for NC4, NJ6, NK1, OB6, OF1, and PL1 if that is of interest to you.
Maybe I wasn't paying attention, but I could swear that on at least one occasion or two when I performed an Odin modem flash, it didn't "stick", despite no complaints on the handset screen or in Odin - the next boot showed the (prior) baseband version, not what I flashed. Its a bit of a mystery to me; but for now I've resolved to make sure that after the Odin session is complete, I wait 30 seconds or so, then remove the USB cable, and then pull the battery rather than try to restart the device by holding buttons down. It is possible that those events occurred when I soft-restarted the phone, but I'm not sure. For now I'm just trying to always flash and restart with exactly the same method to avoid different behaviors from creeping in.
PS I have no idea if those ROM flashables are compatible with Flashfire. They might be, but I've never tested it, and as they are not pre-rooted I'm not going to suggest it for fear that somebody with a rooted but locked (bootloader) phone will try using flashfire and then end up with a phone that needs a full Odin re-install. Appearances are that each version of the bootloader restricts the Samsung signing verification to only the matching kernel version - you can't even boot a Signed samsung kernel on a locked phone if it is a different version than the bootloader's version.
Hello all I have a emmc exploit note 3 I'm using here and I wanted to flash different radios for the us carrier note 3's and I first tried to use flash fire to try to update the modem, but even that didn't stick, cause I don't readily have a pc available, I wasn't ballsy enough to flash a different carrier modem, since I checked the odin screen and saw that instead of a bootloader unlock, its in developer mode and I didn't want a brick, so overall my question is, do I need a unlocked bootloader to flash different modems and do I need odin tovdo it or will some sort of mobile odin or something do it? Thanks mates and happy flashing.
Dlind said:
Hello all I have a emmc exploit note 3 I'm using here and I wanted to flash different radios for the us carrier note 3's and I first tried to use flash fire to try to update the modem, but even that didn't stick, cause I don't readily have a pc available, I wasn't ballsy enough to flash a different carrier modem, since I checked the odin screen and saw that instead of a bootloader unlock, its in developer mode and I didn't want a brick, so overall my question is, do I need a unlocked bootloader to flash different modems and do I need odin tovdo it or will some sort of mobile odin or something do it? Thanks mates and happy flashing.
Click to expand...
Click to collapse
Well, your question is way off topic for this thread.
But since nobody is in here anyways, I guess I'll answer the parts that I am able to.
The modems that I posted over in that other thread were meant to be flashed in Odin using a PC. You can use either the AP slot or CP slot. Note that the very first post says - in big bold blue letters "Odin-flashable Modems".
Not flashfire. It never said anything about flashfire.
Is there such a thing as MobileOdin? If there is, I know nothing about it and certainly have never tested anything with it. So I don't know and am not going to speculate.
You said something confusing here:
Dlind said:
I checked the odin screen and saw that instead of a bootloader unlock, its in developer mode
Click to expand...
Click to collapse
If it says "MODE: Developer" you have an unlocked bootloader. Which is exactly the same thing as a Developer Edition phone.
If you were to use a PC with Odin and you flashed a FULL Stock firmware flash, yes it would overwrite the unlocked bootloader and indeed re-lock the phone. If you were able to re-root that (stock) ROM, you could perform the unlocking procedure again to unlock it.
On the other hand, those Odin-flashable modem packages do not contain the bootloader firmware, so if you were to use Odin on a PC to flash just those modem images, your bootloader would not get re-locked - the unlocked bootloader is still there, untouched.
When the carriers issue an OTA update, many times (perhaps most of the time) they contain a modem update (NON-HLOS.bin and modem.bin). So it is obvious that they are able to be flashed **somehow** right on the phone, without using Odin from the PC or an "Odin app" at all.
BUT that happens using a combination of the STOCK recovery and the bootloader itself during the reboot following the actions taken by the STOCK recovery. (My guess is that the recovery simply "stages" it into place, and sets some flags so that the bootloader knows that it is supposed to evaluate the crypto signatures of the file blobs that the recovery put into place and it is actually the bootloader that does the flashing. That's really not a whole lot different than what happens when you transfer files from Odin to the phone - the "Odin/Download" mode is just one of the personalities of the bootloader. (Odin is actually a rather dumb program - it's the bootloader on the phone that gets to decide whether a flash happens. It does that by carefully examining the file blob that gets transferred, e.g. crypto signature checks)
My guess is that you would be able to flash STOCK modem packages from Odin (using a PC) independent of whether the bootloader is locked or unlocked. But as I said: "guess".
I don't have a second phone to test with, so I would have to flash completely back to stock and lock my bootloader to be able to test that hypothesis. That's a big jobs because of all the crap I have to backup and restore to my phone.
Frankly, if you don't have access to a PC, and you really need your device to keep working, I would advise you to stop screwing around with it, simply because you don't have good tools available to fix it if a disaster occurs.
PS. I've never once noticed anything different between various radio firmwares on ANY device I've ever owned.
bftb0 said:
Well, your question is way off topic for this thread.
But since nobody is in here anyways, I guess I'll answer the parts that I am able to.
The modems that I posted over in that other thread were meant to be flashed in Odin using a PC. You can use either the AP slot or CP slot. Note that the very first post says - in big bold blue letters "Odin-flashable Modems".
Not flashfire. It never said anything about flashfire.
Is there such a thing as MobileOdin? If there is, I know nothing about it and certainly have never tested anything with it. So I don't know and am not going to speculate.
You said something confusing here:
If it says "MODE: Developer" you have an unlocked bootloader. Which is exactly the same thing as a Developer Edition phone.
If you were to use a PC with Odin and you flashed a FULL Stock firmware flash, yes it would overwrite the unlocked bootloader and indeed re-lock the phone. If you were able to re-root that (stock) ROM, you could perform the unlocking procedure again to unlock it.
On the other hand, those Odin-flashable modem packages do not contain the bootloader firmware, so if you were to use Odin on a PC to flash just those modem images, your bootloader would not get re-locked - the unlocked bootloader is still there, untouched.
When the carriers issue an OTA update, many times (perhaps most of the time) they contain a modem update (NON-HLOS.bin and modem.bin). So it is obvious that they are able to be flashed **somehow** right on the phone, without using Odin from the PC or an "Odin app" at all.
BUT that happens using a combination of the STOCK recovery and the bootloader itself during the reboot following the actions taken by the STOCK recovery. (My guess is that the recovery simply "stages" it into place, and sets some flags so that the bootloader knows that it is supposed to evaluate the crypto signatures of the file blobs that the recovery put into place and it is actually the bootloader that does the flashing. That's really not a whole lot different than what happens when you transfer files from Odin to the phone - the "Odin/Download" mode is just one of the personalities of the bootloader. (Odin is actually a rather dumb program - it's the bootloader on the phone that gets to decide whether a flash happens. It does that by carefully examining the file blob that gets transferred, e.g. crypto signature checks)
My guess is that you would be able to flash STOCK modem packages from Odin (using a PC) independent of whether the bootloader is locked or unlocked. But as I said: "guess".
I don't have a second phone to test with, so I would have to flash completely back to stock and lock my bootloader to be able to test that hypothesis. That's a big jobs because of all the crap I have to backup and restore to my phone.
Frankly, if you don't have access to a PC, and you really need your device to keep working, I would advise you to stop screwing around with it, simply because you don't have good tools available to fix it if a disaster occurs.
PS. I've never once noticed anything different between various radio firmwares on ANY device I've ever owned.
Click to expand...
Click to collapse
Thanks SOOOOOO MUCH for your input I kinda had a feeling that the idea was risky at first and I don't know a whole lot about odin and I wish Samsung could have created something much easier to use, but thanks for answering the wayyyyy off topic question, I'm gonna smash that thanks button, I'm also going to take the advise on not cross flashing different modems, its just to risky. You answered all my questions so thanks, Also I want to say thank you for your continued work on this phone is by normal terms "old" now but in reality its still an amazing phone with the right custom software, and happy flashing!