Related
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.
So i have a stock sprint note 3 that had 4.4.4 on it.
I attempted to install twrp/cwm through odin, but it failed and now i'm stuck in the failed firmware update loop.
I have tried installing older versions of the stock firmware, seems like i'm stuck looking for a 4.4.4 which seems kinda hard to find right now.
What are my other options, my friend is looking for the serial numbers to see if i can just use keis to recover.
k0ncept said:
So i have a stock sprint note 3 that had 4.4.4 on it.
I attempted to install twrp/cwm through odin, but it failed and now i'm stuck in the failed firmware update loop.
I have tried installing older versions of the stock firmware, seems like i'm stuck looking for a 4.4.4 which seems kinda hard to find right now.
What are my other options, my friend is looking for the serial numbers to see if i can just use keis to recover.
Click to expand...
Click to collapse
Although your thread will probably be moved to the Q&A section, you stated you are able to install older versions...... take it back into DL mode and Odin 4.4.4. There are several threads you can download the NK4 Firmware from including the Sammobile site.
SM-N900P Spint (cdma) 2014 December 4.4.4 N900PVPUDNK4 N900PSPTDNK4
shadowcliffs Thread in the General Section
.
k0ncept said:
So i have a stock sprint note 3 that had 4.4.4 on it.
I attempted to install twrp/cwm through odin, but it failed and now i'm stuck in the failed firmware update loop.
I have tried installing older versions of the stock firmware, seems like i'm stuck looking for a 4.4.4 which seems kinda hard to find right now.
What are my other options, my friend is looking for the serial numbers to see if i can just use keis to recover.
Click to expand...
Click to collapse
Honestly it sounds like you're making this more difficult than it really is.
All you need is;
NK4 .tar
SU
&
TWRP
So i'm fairly new to this the last phone i did was my vz s4 (and it went off with less bumps).
I'm stuck in the boot load loop. I can't flash any ROM on it right now, i think i'm trying to find the right 4.4.4 rom. Any place with good rom support would help. sammobile is far too slow on downloads...also there are a few 4.4.4 roms by now.
So the phone was purchased in early Nov 2014, already on a 4.4.4.
I dl'd odin and a TWRP, foolishly didn't make sure 4.4.4 could be flashed in the same way. Odin marked it as failed and when i re-start the phone it runs into the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
The phone can get into download mode just fine (cannot boot)...tho i have no idea what to flash onto it now.
k0ncept said:
So the phone was purchased in early Nov 2014, already on a 4.4.4.
I dl'd odin and a TWRP, foolishly didn't make sure 4.4.4 could be flashed in the same way. Odin marked it as failed and when i re-start the phone it runs into the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
The phone can get into download mode just fine (cannot boot)...tho i have no idea what to flash onto it now.
Click to expand...
Click to collapse
As Nickitt stated, don't make it more than it is. If you can get into DL mode then you are not fully bricked which is good. You need to flash an " Official 4.4.4 Firmware " to get you out of this situation, whether it be a slow download or not. I provided a link in my original first response of several uploads of 4.4.4 that you could possibly use that were uploaded by member shadowcliffs in his same thread/post. After you have flashed the official firmware and gone through the initial setup once again with the stock firmware, get the phone back into DL Mode and flash TWRP or Philz CWM recovery via ODIN. Once you have your custom recovery loaded, flash the Custom Rom of your choice.
Hey dark,
thanks for the quick and very very useful response. i wish i hit this up way sooner i did find those links after hours of searching through garbage. i've been downloading a few 4.4.4 images for the last 2hours. Hopefully this will help me! sadly those are the same slow connections i've scene. damn 50kb/sec so sad haha
I'll keep the board posted. but mostly bump that og thread
Damn, fails on the nk4 image and the nh7.
fails on the same spot system.img.ext4
any other suggestions board? please?
make sure your using the hltespr version of either TWRP or philz recovery, if its not working on TWRP switch to philiz. Could also be a bad download - re-download and flash again
Why don't you just use TWRP Manager to install TWRP after you root?
Sent from my GALAXY Note 3 via Tapatalk
not being able to root was the problem
FIXED my issues!!
Never use vmware and Mac to run heimdall or Odin... They should more prominently tell you that.
Thank you board for the concern
problem solved
Thanks for updating that you fixed the problem and what it was. It sounded like you were doing everything correctly. i was getting concerned that it wasn't working. I don't use mac, but if i did i would have been very grateful for that knowledge. thanks for the update. too often someone fixes the problem and just quits posting on the thread.:good:
k0ncept said:
FIXED my issues!!
Never use vmware and Mac to run heimdall or Odin... They should more prominently tell you that.
Thank you board for the concern
Click to expand...
Click to collapse
Parallels is a better option imo as far as v-machines are concerned but anything after Mountain lion doesn't work well. The newest mac osx doesn't work at all with Heimdall. It won't download the pit file. If your running mavricks you can try using a program called winebottle
How to Run Odin On Mac: http://youtu.be/j7fpouzMSsk also jOdin is another desktop tool to use. jOdin is a early stage online flashing tool with limited capabilities at this time.Beings its a online flashing tool. I would make sure to have a good internet connection or you could run into trouble im guessing. All in all I think its a good idea I just hope this project keeps going.
JOdin - Using Odin on a Mac: http://youtu.be/MiPRXq207Ug
It's only right jag.
Goat, thanks for the additional information. I hope there are improved options for the mac and Linux one day
k0ncept said:
It's only right jag.
Goat, thanks for the additional information. I hope there are improved options for the mac and Linux one day
Click to expand...
Click to collapse
Me too bro, me too!
Hello all, how are things? Well I hope.
I know there is a thread somewhere here that is what I need but in my search I seem to be confusing myself and finding more uncertainty than answers.(Not by fault of the forums, it's probably on my part)
Anyway, what I have right now:
Galaxy Note 3, Sprint, Rooted.
Software: N900PVPUDNK4
Hardware: N900P.12
Model: SM-900P
Android: 4.4.4
Baseband: N900PVPNK4
Kernal: 3.4.0
Stock ROM, no TWRP/CWM, tripped Knox(don't care). Used Odin and AutoCF when I rooted it, but that was long enough ago that I can't remember specifics. It was easy though.
Now what I'd like is to upgrade to Lollipop. Preferably stock ROM, and remain free from TWRP/CWM. If it is necessary, TWRP is preferred as that is what I used on my previous phone and am familiar with it some-what.
From searching this and other forums I 'think' the same Odin/AutoCF method works to gain root. Is this correct? Is there a stock ROM already rooted that can be flashed with ODin, or would I need to flash unrooted lollipop, then re-root?
I've been searching but I'm seeing a lot of posts, links, guides, some of which predate the N3 5.0 release so I'm not sure if they are still valid.
Thank you for any advice, help.
you'll need to flash the unrooted tar (with odin) to get to lollipop cleanly
then use cfautoroot to root (also with odin)
then I would flash twrp (again with odin) So you could flash in the future.
first this
http://forum.xda-developers.com/showthread.php?t=3095540
(ROM)(ODIN)OC5 stcock firmware tar
and then this to root
http://forum.xda-developers.com/showthread.php?p=60658516
Instructions for flashing ANY custom/stock Lollipop via recovery
Kingdazy, thank you! Didn't have time over the holiday weekend, but got around to it the other day. Perfect, well, almost. I did install TWRP. Only snag was that when reflashing the stock lollipop ROM TWRP hangs when it installs modem. I let it sit a while before rebooting and everything is working. Interesting... But it works..
Thank you again.
cmacdara said:
Kingdazy, thank you! Didn't have time over the holiday weekend, but got around to it the other day. Perfect, well, almost. I did install TWRP. Only snag was that when reflashing the stock lollipop ROM TWRP hangs when it installs modem. I let it sit a while before rebooting and everything is working. Interesting... But it works..
Thank you again.
Click to expand...
Click to collapse
sorry my response post was so short, little detail. (had family issues at the time, and you seemed competent enough to read, follow directions. ?)
glad you got around to it! the process seems daunting to read, but once you do it, it's like boom-boom-boom super easy.
it was more a pain in the ass to get my stuff restored more than anything...
enjoy!
trying to find a flashable nc5 file or higher while currently running on the old rooted mj4 with twrp. Trying to preserve my data that way I don't do to do a full reset. If anyone has a file that'll flash via zip from the twrp recovery, i'd greatly appreciate it. That and I don't really know what the proper steps are to do a proper update. Lots of info here, though it's usually starting off with something else and I'm confused.
Nothing, really? :-/
rcflyer40t said:
Nothing, really? :-/
Click to expand...
Click to collapse
I think I found something here http://www.rwilco12.com/downloads.p...msung Galaxy Note 3 (SM-N900P)/Stock ROMs/NC5 there is a nodata restore verison 2.11gb that I think is flashable through a recovery I need to download it first and I'm trying to contact Rwilco12 to ask him if it is falshable .
Woohoo! Hoping it is. Thank you Jim! I've been trying to find something newer as well in case it's btr.
Have you seen this going to NH7? Usable?
http://forum.xda-developers.com/showthread.php?t=2712205
And this
http://forum.xda-developers.com/note-3-sprint/help/question-upgrading-to-nc5-t2911173
rcflyer40t said:
Woohoo! Hoping it is. Thank you Jim! I've been trying to find something newer as well in case it's btr.
Have you seen this going to NH7? Usable?
http://forum.xda-developers.com/showthread.php?t=2712205
And this
http://forum.xda-developers.com/note-3-sprint/help/question-upgrading-to-nc5-t2911173
Click to expand...
Click to collapse
Basically they would both work but you lose all your data. Anytime you Odin flash a stock OS (rom) it takes you back to bone stock and removes all your data ( i.e. pics, music, apps, and texts ect. . . ) like when you just bought the phone.
So what we are trying to do is find a flashable stock version or as close to stock as possible that can be flashed through your custom recovery where you can choose what to wipe and what to save. In this case your NOT going to wipe data, just wipe cache, dalvik-cache, and system do a dirty flash and try to save your personal data.
Let me see if I can find a copy of NH7.
OK checked out NC5 from Rwilco12 took an hour to download and it was not a useable version, will keep looking.
I am not able to find anything, your best bet at this point is to make a choice to stay where you are rooted mj4 or upgrade by going back to stock.
If you upgrade, to save your data connect the device to your PC. Copy and paste the DCIM, download, music, and video files to the desktop of your PC. Write down your apps on some paper, you will find you need a different version of your apps to run on the upgraded OS anyway so you will have to get them from the play store. Then go to my rom flashing basics and follow the instructions and get the link to Sammobile. This way you can download the version of the OS to your desktop you want Sammobile has them all. Make sure when you Odin flash the OS, you need to give it time to boot up !
It takes 3-5 min to boot the first time and ( sometimes it doesn't boot up DON'T PANIC ) this is normal. If it is caught in a boot loop just pull the battery, reinstall battery boot into download mode and Odin flash the OS again. It will boot the second time. Even if it boots the first time stop, boot into download mode and Odin flash the OS again.
You should always Odin flash a stock OS (rom) TWICE so you get a good clean install. Then install the right version of TWRP for the stock OS you have installed, then root and install your personal data back in the device ( connect device to PC and copy and paste data back in internal storage ).
jimzweb1 said:
I am not able to find anything, your best bet at this point is to make a choice to stay where you are rooted mj4 or upgrade by going back to stock.
If you upgrade, to save your data connect the device to your PC. Copy and paste the DCIM, download, music, and video files to the desktop of your PC. Write down your apps on some paper, you will find you need a different version of your apps to run on the upgraded OS anyway so you will have to get them from the play store. Then go to my rom flashing basics and follow the instructions and get the link to Sammobile. This way you can download the version of the OS to your desktop you want Sammobile has them all. Make sure when you Odin flash the OS, you need to give it time to boot up !
It takes 3-5 min to boot the first time and ( sometimes it doesn't boot up DON'T PANIC ) this is normal. If it is caught in a boot loop just pull the battery, reinstall battery boot into download mode and Odin flash the OS again. It will boot the second time. Even if it boots the first time stop, boot into download mode and Odin flash the OS again.
You should always Odin flash a stock OS (rom) TWICE so you get a good clean install. Then install the right version of TWRP for the stock OS you have installed, then root and install your personal data back in the device ( connect device to PC and copy and paste data back in internal storage ).
Click to expand...
Click to collapse
Looking at your thread of "basics", it says twrp won't work. is that still current, or does it work now?
My understanding is if I want to go to the lastest OS (NC5 or NH7), download it, flash it, then flash it again and pretty much be done? Curious do I still get the hotspot mod back? (as I currently have it with rooted mj4)
gotta go back and find either of those two versions as rooted...
Can you check on your phone if you can download and install Hexo+ from the googleplay store? That's where I'm getting at. If it works under your 4.4.2 nc5 then maybe I don't need to go any higher unless I experience issues, then I'll upgrade again.
Thanks.
rcflyer40t said:
Looking at your thread of "basics", it says twrp won't work. is that still current, or does it work now?
My understanding is if I want to go to the lastest OS (NC5 or NH7), download it, flash it, then flash it again and pretty much be done? Curious do I still get the hotspot mod back? (as I currently have it with rooted mj4)
gotta go back and find either of those two versions as rooted...
Can you check on your phone if you can download and install Hexo+ from the googleplay store? That's where I'm getting at. If it works under your 4.4.2 nc5 then maybe I don't need to go any higher unless I experience issues, then I'll upgrade again.
Thanks.
Click to expand...
Click to collapse
Ok TWRP or Philz CWM will work for both NC5 or NH7 just make sure you have the right version i.e. (the version for mj4 you have now, will not work for NH7). What mod are you using to run the Hotspot? I'm sure you can get the hotspot working with the same mod on both NC5 and NH7 just a newer version once you get the new OS rooted.
I'm running 4.4.4 NK4 I downloaded Hexo+ and it opened no problem.
jimzweb1 said:
Ok TWRP or Philz CWM will work for both NC5 or NH7 just make sure you have the right version i.e. (the version for mj4 you have now, will not work for NH7). What mod are you using to run the Hotspot? I'm sure you can get the hotspot working with the same mod on both NC5 and NH7 just a newer version once you get the new OS rooted.
I'm running 4.4.4 NK4 I downloaded Hexo+ and it opened no problem.
Click to expand...
Click to collapse
awesome good to know.
.... geez, sadly I can't remember how or what I used for the mod. brain cells way too invested in other things that I can't remember. hahahaha damn it. oh fml...
In regards to the right version, I need the .zip file, not the img or img.tar, correct?
You said your os was running smooth and no issues, same with battery consumption (nk4)?
got the NK4 file downloaded, but I'm confused as I didn't find the rooted version on your page. I read "rooting the phone" section under towelroot, am I correct in that the towelroot apk will root the stock NK4 file I've just downloaded from http://forum.xda-developers.com/showthread.php?t=2522638?
This was how I did the hotspot mod... Will this get wiped out? I'm assuming yes.
http://forum.xda-developers.com/showthread.php?t=2505850
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!