Ready to sell this phone... tried everything I know how to try... Dev Edition Verizon S5, CAN'T UPGRADE from stock NCG. The most I can do it root... any ROM I flash is nonfunctional on Verizon's network with NO SIGNAL. Replaced SIM, flashed modems, etc etc... I think I'm just not sure how to do it with a dev edition... seriously feel like I'm missing a step. Would like to start from scratch. Does anyone have a stock image of a G900V Dev Edition I could work from, since I'm starting to think the one I've been working from is somehow the incorrect version. Thanks!
http://www.sammobile.com/firmwares/
type g900v in search bar
DSA said:
http://www.sammobile.com/firmwares/
type g900v in search bar
Click to expand...
Click to collapse
I would but I'm trying to avoid locking the bootloader, if possible. Didn't intend on having a developer device, but now that I do, I'd like to try to maintain it's use as one. Bought this phone on swappa, seller didn't give any indication that it was a developer device. Now I'm concerned he did something to it prior to selling that is causing me difficulties. I don't think I should be having these network difficulties, but there could very well be something I'm supposed to be doing with the modem that I'm just unaware of. I figure if I can get back to the way this phone was when it was new (when the original seller bought it) I'd at least have a clean slate to work with.
gatorhater73 said:
I would but I'm trying to avoid locking the bootloader, if possible. Didn't intend on having a developer device, but now that I do, I'd like to try to maintain it's use as one. Bought this phone on swappa, seller didn't give any indication that it was a developer device. Now I'm concerned he did something to it prior to selling that is causing me difficulties. I don't think I should be having these network difficulties, but there could very well be something I'm supposed to be doing with the modem that I'm just unaware of. I figure if I can get back to the way this phone was when it was new (when the original seller bought it) I'd at least have a clean slate to work with.
Click to expand...
Click to collapse
Anything usable in here?
http://www.galaxys5update.com/galaxy-s5-stock-firmware/
kprice8 said:
Anything usable in here?
http://www.galaxys5update.com/galaxy-s5-stock-firmware/
Click to expand...
Click to collapse
I don't think so, but thanks... I think that's the same device firmware that the retail version comes with, which will lock my bootloader. I've actually considered just flashing it anyway and saying the hell with an unlocked bootloader, since I didn't really intend to have one to begin with and apparently there's nothing I can do with it, anyway (none of the unified builds work on my device, anyway) but this is a last-ditch effort to preserve it if i can, and I'm hoping some dev will be willing to help me diagnose my problem.
gatorhater73 said:
I don't think so, but thanks... I think that's the same device firmware that the retail version comes with, which will lock my bootloader. I've actually considered just flashing it anyway and saying the hell with an unlocked bootloader, since I didn't really intend to have one to begin with and apparently there's nothing I can do with it, anyway (none of the unified builds work on my device, anyway) but this is a last-ditch effort to preserve it if i can, and I'm hoping some dev will be willing to help me diagnose my problem.
Click to expand...
Click to collapse
It's not like there's a ton of development going on for Dev edition. I'm loving the retail version of the phone just rooted and running some Xposed. Like it so much, I went out and got one for the wife too and I paid full retail for both to keep my old unlimited data plan. Hers I just left out of the box stock. Will be interested to see how Lolipop looks when it drops to her phone. Sure hope we keep root with Lolipop, I use the heck out of my hotspot, to the tune of about 70gb/mo ...
gatorhater73 said:
I don't think so, but thanks... I think that's the same device firmware that the retail version comes with, which will lock my bootloader. I've actually considered just flashing it anyway and saying the hell with an unlocked bootloader, since I didn't really intend to have one to begin with and apparently there's nothing I can do with it, anyway (none of the unified builds work on my device, anyway) but this is a last-ditch effort to preserve it if i can, and I'm hoping some dev will be willing to help me diagnose my problem.
Click to expand...
Click to collapse
I'm far from a developer, but this may help. I also bought the phone without realizing what it was I was getting into and had similar problems flashing the Optimal rom on my dev edition s5. I could flash but phone would hang on the activation screen with no signal. I eventually succeeded. As near as I can recall this is what I did:
I dirty flashed Beantown 4.4.4 rom (twrp) over my 4.4.2 stock firmware. then flashed n12 firmware (included stock kernel, and modem) from dev edition make an update .tar thread (odin) (http://forum.xda-developers.com/showpost.php?p=56604757&postcount=2). I did a factory reset after flashing. Switched to art. Flashed optimal with clean reset, but did not flash kernel. Later flashed koontsez 4.4.4 kernel. Still running Optimal
Good luck.
JOrkin said:
I'm far from a developer, but this may help. I also bought the phone without realizing what it was I was getting into and had similar problems flashing the Optimal rom on my dev edition s5. I could flash but phone would hang on the activation screen with no signal. I eventually succeeded. As near as I can recall this is what I did:
I dirty flashed Beantown 4.4.4 rom (twrp) over my 4.4.2 stock firmware. then flashed n12 firmware (included stock kernel, and modem) from dev edition make an update .tar thread (odin) (http://forum.xda-developers.com/showpost.php?p=56604757&postcount=2). I did a factory reset after flashing. Switched to art. Flashed optimal with clean reset, but did not flash kernel. Later flashed koontsez 4.4.4 kernel. Still running Optimal
Good luck.
Click to expand...
Click to collapse
Had marginal success using this method... Have been able to maintain a 3G signal, but no LTE after first boot. Rather, when I first booted, I had LTE and thought I was good, but since my first reboot, I can only get 3G and nothing I do can get it back so far.
JOrkin said:
I'm far from a developer, but this may help. I also bought the phone without realizing what it was I was getting into and had similar problems flashing the Optimal rom on my dev edition s5. I could flash but phone would hang on the activation screen with no signal. I eventually succeeded. As near as I can recall this is what I did:
I dirty flashed Beantown 4.4.4 rom (twrp) over my 4.4.2 stock firmware. then flashed n12 firmware (included stock kernel, and modem) from dev edition make an update .tar thread (odin) (http://forum.xda-developers.com/showpost.php?p=56604757&postcount=2). I did a factory reset after flashing. Switched to art. Flashed optimal with clean reset, but did not flash kernel. Later flashed koontsez 4.4.4 kernel. Still running Optimal
Good luck.
Click to expand...
Click to collapse
This happened after I flashed the update.tar (with aboot.mbn removed) and I have note gotten LTE back. Is there something I can do with my aboot.bak that I'm missing?
Related
Hi all,
First of all I'm sorry if this isn't the right place for this thread, it just seems like the related threads are in this forum.
First of all I have the international unbranded version of the note three (SM-N9005), which I rooted in order to use VPN. I did this using the chainfire method which of course tripped the knox flag, I'm not griping about that because I don't really care about the warranty, just giving facts.
This then prevents the phone from checking for updates properly saying "device has been modified" or something like that.
I'm on three ireland and they very recently switched on 4g/lte network support but you need to accept an ota update to enable it. Therein lies my problem, I can't accept an ota update.
I would have no problem unrooting to accept an update, but that doesn't reset the knox flag and my phone will still show up as modified and considering the amount of effort I would have to go through to unroot just to end up on the same situation as I'm in already is not worth it.
I have tried the viaero 4g toggle app but this just gives a black screen for me. I also tried the persist.radio.lteon.xml fix but I couldn't find that file to change the setting. These solutions suggested here http://forum.xda-developers.com/showthread.php?t=2468624&page=2
So my questions:
Is there any way to flash some sort of firmware unofficially to give lte support?
If I flashed a custom rom would that give me lte support? Or do I need to flash the official 3 Ireland lte firmware first?
If that will work, can anyone recommend a rom to install?
Finally has anyone managed to get themselves out of a similar situation yet?
Hope somebody can help,
Thanks for reading
Barry
bazzertron said:
Hi all,
First of all I'm sorry if this isn't the right place for this thread, it just seems like the related threads are in this forum.
First of all I have the international unbranded version of the note three (SM-N9005), which I rooted in order to use VPN. I did this using the chainfire method which of course tripped the knox flag, I'm not griping about that because I don't really care about the warranty, just giving facts.
This then prevents the phone from checking for updates properly saying "device has been modified" or something like that.
I'm on three ireland and they very recently switched on 4g/lte network support but you need to accept an ota update to enable it. Therein lies my problem, I can't accept an ota update.
I would have no problem unrooting to accept an update, but that doesn't reset the knox flag and my phone will still show up as modified and considering the amount of effort I would have to go through to unroot just to end up on the same situation as I'm in already is not worth it.
I have tried the viaero 4g toggle app but this just gives a black screen for me. I also tried the persist.radio.lteon.xml fix but I couldn't find that file to change the setting. These solutions suggested here http://forum.xda-developers.com/showthread.php?t=2468624&page=2
So my questions:
Is there any way to flash some sort of firmware unofficially to give lte support?
If I flashed a custom rom would that give me lte support? Or do I need to flash the official 3 Ireland lte firmware first?
If that will work, can anyone recommend a rom to install?
Finally has anyone managed to get themselves out of a similar situation yet?
Hope somebody can help,
Thanks for reading
Barry
Click to expand...
Click to collapse
If you reflash back to complete Stock your status will show Official, also you can try a custom ROM, ALL of them are capable of getting LTE by default. I have no issues with them.
radicalisto said:
If you reflash back to complete Stock your status will show Official, also you can try a custom ROM, ALL of them are capable of getting LTE by default. I have no issues with them.
Click to expand...
Click to collapse
Thanks for the quick reply radicalisto, to be honest I'm ready to move away from touchwiz so a custom ROM sounds like a good solution to me. Choosing one is the conundrum. Are any of them more stable/full featured than the rest? I would appreciate any advice about a ROM to choose.
Well to be honest, custom ROMs are trial and error, but the new Kitkat ROMs are awesome, I personally tried them all and have settled on one (won't say which cause it may sway you haha) - however these are TW based ROMs.
If you are on 4.3 still and fancy CM11 -- Two ROMs you should try are temasek's CM11 + Yank555's kernel (amazing pal) - Or ProBAM with Yank555's kernel (Just as good as temasek's) both are packed with great features, awesome battery life and generally just great. However you may or may not know, CM doesn't support SPen functions, you'd have to use GMDSPen or another alternative.
EDIT: Little side note, again not sure if you are aware.. if you flash Kitkat 4.4.2 your bootloader upgrades so you cannot use CM, as it runs on 4.3's bootloader, there is no downgrade option either currently.
Not that I'm so concerned about the CM bootloader using 4.3, but would I be safe in assuming that the CM team will have to eventually switch to the 4.4 bootloader?
radicalisto said:
Well to be honest, custom ROMs are trial and error, but the new Kitkat ROMs are awesome, I personally tried them all and have settled on one (won't say which cause it may sway you haha) - however these are TW based ROMs.
Click to expand...
Click to collapse
Well you're allowed to tell me as I was asking to be swayed...
I'm thinking I'm going to try x-note first as it seems to be the most popular and I'm guessing it's that way for a reason.
Yeah CM team are working on it now from what I have read, I'm using X-Note V.8 with CivZ KatEngine 2.0 kernel
Purchased my S4 at launch, only rooted it and never really got around to tweaking it much. It has slowed down a bit so now is the time.
I'm on MDL, stock 4.2.2, and rooted with TWRP 2.5.0.2 On to the questions/clarifications, hopefully these aren't egregious. I know the info is out there but for actually finding specific information, the xda forums are a bit overwhelming and sometimes conflicting...
1) Recovery - Latest/preferred recovery for the s4 (on MDL) with auto-loki baked in? Are any of the latest versions of TWRP/CWM dangerous/incompatible or can I just install the latest/greatest with ROM Installers and go from there?
2) Modem - Flashing an updated modem, regardless of ROM/OS # should not break anything and/or lock down the bootloader any more so than it already is at MDL, correct? Updating the baseband will have no effect on the build # and thus loki is still and option (versus safestrap)? Preferred modem at this time? (ATT, SF Bay Area)
3) ROMS - Any ROM, followed by loki patch or flashed via an auto-loki capable recovery should be fine, correct? Is a ROM specifically built for safestrap applications and thus would not work with MDL, or are ROMs noted as being safestrap ready just able to be used via safestrap, but loki as well?
4) Hard to keep track of all the ROMs and the builds and branches etc - Can anyone point me in the right direction of either a) the latest stock touch-wiz 4.4.4 ROM that can be flashed over MDL without essentially updating past MDL? b) the best/most recent pure google (Play Store S4 Edition) ROM, same story with not breaking MDL?
Again, I apologize I am sure the info is all buried in here somewhere, it just gets to a point where pointed questions rather than multiple 500+ post threads are hopefully less likely to brick my phone. Ideally I just want to get on the latest software (and enable screen casting, for one). Assuming it comes quick enough, once I get this process down I will probably make the jump to 5.0 when it is ready, anticipate a couple months? Who knows.
Thanks, much appreciated.
Norcalz71 said:
Purchased my S4 at launch, only rooted it and never really got around to tweaking it much. It has slowed down a bit so now is the time.
I'm on MDL, stock 4.2.2, and rooted with TWRP 2.5.0.2 On to the questions/clarifications, hopefully these aren't egregious. I know the info is out there but for actually finding specific information, the xda forums are a bit overwhelming and sometimes conflicting...
1) Recovery - Latest/preferred recovery for the s4 (on MDL) with auto-loki baked in? Are any of the latest versions of TWRP/CWM dangerous/incompatible or can I just install the latest/greatest with ROM Installers and go from there?
2) Modem - Flashing an updated modem, regardless of ROM/OS # should not break anything and/or lock down the bootloader any more so than it already is at MDL, correct? Updating the baseband will have no effect on the build # and thus loki is still and option (versus safestrap)? Preferred modem at this time? (ATT, SF Bay Area)
3) ROMS - Any ROM, followed by loki patch or flashed via an auto-loki capable recovery should be fine, correct? Is a ROM specifically built for safestrap applications and thus would not work with MDL, or are ROMs noted as being safestrap ready just able to be used via safestrap, but loki as well?
4) Hard to keep track of all the ROMs and the builds and branches etc - Can anyone point me in the right direction of either a) the latest stock touch-wiz 4.4.4 ROM that can be flashed over MDL without essentially updating past MDL? b) the best/most recent pure google (Play Store S4 Edition) ROM, same story with not breaking MDL?
Again, I apologize I am sure the info is all buried in here somewhere, it just gets to a point where pointed questions rather than multiple 500+ post threads are hopefully less likely to brick my phone. Ideally I just want to get on the latest software (and enable screen casting, for one). Assuming it comes quick enough, once I get this process down I will probably make the jump to 5.0 when it is ready, anticipate a couple months? Who knows.
Thanks, much appreciated.
Click to expand...
Click to collapse
I will try to help with a few of these questions, but others I am not familiar with very much. On that note DO NOT update your bootloader!!! It will be locked down further and Loki will NOT WORK. And you could NOT flash any kernels with safestrap. So with safestrap ONLY the stock kernel can be used. Now on to your questions...
1) I am using TWRP 8.1 if I remember correctly. You can find it in the Original Android Development section. It does NOT Auto Loki, so keep the loki-doki flashable zip on your sdcard OR use Roms that already have/use the boot.Loki kernels like ShoStock-i 8.1
2) Modem flashing will NOT lock anything up further as far as the bootloader. You can flash ANY or ALL of them from my modem thread. See which works BEST FOR YOU in YOUR AREA. I am in So Cal and the best for me has been either MDL. But I have and do test ALL of them. You can always flash back to whichever one works best for you.
3.) Like I said I use ShoStock-i 8.1 because it has and does EVERYTHING I need my phone to do and does it without any issues. I have NOT tried to use a Safestrap modified ROM so I have very little experience with that. Normally most devs will have two separate versions, one for safestrap compatible and one for us without safestrap. ShoStock-i is already built with Loki in the kernel so you do not NEED to flash Loki-Doki patch.
4) there are NO Touchwiz 4.4.4 Stock Roms for ATT yet. But I did try out one of the Touchwiz 4.4.4 T-Mobile based Roms and it worked perfectly. You can either get it from the ATT forums and I believe it is already lokified, or get it from the T-Mobile forum and make sure to flash Loki-Doki patch before booting up phone after flashing the ROM. Again the will NOT update your bootloader past your MDL bootloader, so you are good as you are with no worries. By the way on ShoStock-i 8.1 the screen casting to Chromecast works PERFECTLY without having to flash any other .apk's or mess with ANYTHING
This is the exact same boat I'm in. Trying to track down the answers as well. Will keep an eye here as well to watch for answers.
awesome reply thanks RockRatt, that just about covers it. I will maybe give the ShoStock ROM a go and see how I like it. As long as all the normal features are working fine, I should be good.
One last thing I forgot - Odin. I have the stock odin firmware files from when my phone was new (The MDL package). As long as I dont update the bootloader, I should be able to Odin back to the brand new in box state should something go awry or not dig the other ROMs, correct?
Thanks again,
Norcalz71 said:
awesome reply thanks RockRatt, that just about covers it. I will maybe give the ShoStock ROM a go and see how I like it. As long as all the normal features are working fine, I should be good.
One last thing I forgot - Odin. I have the stock odin firmware files from when my phone was new (The MDL package). As long as I dont update the bootloader, I should be able to Odin back to the brand new in box state should something go awry or not dig the other ROMs, correct?
Thanks again,
Click to expand...
Click to collapse
Yep. Just don't update the bootloader...So no flashing newer firmware that contains the bootloader files. Most if not all custom Roms do not have the bootloader files in them. So no problem flashing back to MDL stock if the need never arises. I still in fact have the original MDB bootloader installed that came with the phone before the MDL firmware update.
Hello.
Ever since I bought a Galaxy Nexus and found XDA, my life changed. Without noticing I got infected a virus: addiction to Android.
My Nexus got outdated quickly and now is pretty done and I need a new toy. 3,5 years later I finally got some spare money to buy a new phone. Since here in Portugal the minimum wage is around 500€ and top flagship phones cost around 700€ (and there's no affordable contract to get something cheaper and still nice), I had to wait until now to get a used Note 3 for 300€.
I love the phone's design and above all the specs. There's no other phone with 3GB RAM and Snap 800 for this price and I always liked big sized phones.
Well, I write too much unnecessary info... I need to stop
Let's get down to the point. I will get the phone tomorrow!!
TL;DR
How do I check the bootloader version? I want to flash TWRP right away and maybe install a Note4/5 port or something stock Android, do I need to be careful with the bootloader?
I know from other phones (i.e LG G2) that any custom rom uses KK bootloader and the stock roms use their respective version bootloader. Is this also true for the Note?
Also, which version of TWRP should I flash? Does it depend on the stock rom version that I have?
Checking if the device has 2.3x GB of available RAM, if Odin and Recovery have their stock aspect and if the S-Pen works is enough to ensure that the Note I'm getting is truly original?
Well, that's all. I'm sorry if I'm asking the same questions everyone does. I'm used to Nexus so I'm afraid of bricking the Note with dumb moves. That's why I am taking my time to read every important thread and asking here some doubts that went into my mind while doing the required reading. I have no warranty (no box nor invoice) so I can't afford to mess up with the new babe
Cheers!
This app!
diogofd8 said:
Hello.
Ever since I bought a Galaxy Nexus and found XDA, my life changed. Without noticing I got infected a virus: addiction to Android.
My Nexus got outdated quickly and now is pretty done and I need a new toy. 3,5 years later I finally got some spare money to buy a new phone. Since here in Portugal the minimum wage is around 500€ and top flagship phones cost around 700€ (and there's no affordable contract to get something cheaper and still nice), I had to wait until now to get a used Note 3 for 300€.
I love the phone's design and above all the specs. There's no other phone with 3GB RAM and Snap 800 for this price and I always liked big sized phones.
Well, I write too much unnecessary info... I need to stop
Let's get down to the point. I will get the phone tomorrow!!
TL;DR
How do I check the bootloader version? I want to flash TWRP right away and maybe install a Note4/5 port or something stock Android, do I need to be careful with the bootloader?
I know from other phones (i.e LG G2) that any custom rom uses KK bootloader and the stock roms use their respective version bootloader. Is this also true for the Note?
Also, which version of TWRP should I flash? Does it depend on the stock rom version that I have?
Checking if the device has 2.3x GB of available RAM, if Odin and Recovery have their stock aspect and if the S-Pen works is enough to ensure that the Note I'm getting is truly original?
Well, that's all. I'm sorry if I'm asking the same questions everyone does. I'm used to Nexus so I'm afraid of bricking the Note with dumb moves. That's why I am taking my time to read every important thread and asking here some doubts that went into my mind while doing the required reading. I have no warranty (no box nor invoice) so I can't afford to mess up with the new babe
Cheers!
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en
this app will help you confirm your phone.
then you can proceed flashing twrp and supersu, things are so easy for N9005
and Welcome Aboard
Install phone info samsung from playstore. It could tell a lot about your phone.
To make it easy as long as the phone is running with android version 4.4.2 and above you should use twrp 4.4. If 4.3 use the right one for 4.3.
Sent from my SM-G925F
White Note3 do you have? There are several versions made by Samsung.
Regardless of the bootloader on the phone, I recommend using the latest TWRP as the latest TWRP can be used to flash all ROMs and zip files. Find your device from here: https://twrp.me/Devices/
Before moving to custom ROMs, I also recommend installing the latest bootlloader and ROM.
Not sure if your phone still has warranty but if it does, I would not change the ROM or root because doing either may trip the knox counter and void the warranty.
nijom said:
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en
this app will help you confirm your phone.
then you can proceed flashing twrp and supersu, things are so easy for N9005
and Welcome Aboard
Click to expand...
Click to collapse
Thanks! I will keep the link in my favorites and install the app when I get the chance to test things.
Rosli59564 said:
Install phone info samsung from playstore. It could tell a lot about your phone.
To make it easy as long as the phone is running with android version 4.4.2 and above you should use twrp 4.4. If 4.3 use the right one for 4.3.
Sent from my SM-G925F
Click to expand...
Click to collapse
Thanks! I'm pretty sure it has 4.4.x or lollipop. Should I update to any of those versions (just in case it comes with 4.3) first and then install TWRP?
audit13 said:
White Note3 do you have? There are several versions made by Samsung.
Regardless of the bootloader on the phone, I recommend using the latest TWRP as the latest TWRP can be used to flash all ROMs and zip files. Find your device from here: https://twrp.me/Devices/
Before moving to custom ROMs, I also recommend installing the latest bootlloader and ROM.
Not sure if your phone still has warranty but if it does, I would not change the ROM or root because doing either may trip the knox counter and void the warranty.
Click to expand...
Click to collapse
The phone doesn't come with box nor invoice so I don't have any warranty xd
What is the number or version of the latest bootloader?
What is the model # of the phone? There is the n-900t, n9005, n-900w8, etc.
N9005, it's the european unlocked version
The model # is important when asking questions because the AT&T version of the note 3 has a locked bootloader so it's more complicated to flash custom recovery and to get root.
If you want to run custom ROMs, I recommend upgrading to the latest modem and bootloader, install a custom recovery, back up your stock ROM, and try some custom ROMs to see which one you like.
Look for the tar version of TWRP for your phone from here: https://twrp.me/Devices/
You can flash TWRP with Odin.
audit13 said:
The model # is important when asking questions because the AT&T version of the note 3 has a locked bootloader so it's more complicated to flash custom recovery and to get root.
If you want to run custom ROMs, I recommend upgrading to the latest modem and bootloader, install a custom recovery, back up your stock ROM, and try some custom ROMs to see which one you like.
Look for the tar version of TWRP for your phone from here: https://twrp.me/Devices/
You can flash TWRP with Odin.
Click to expand...
Click to collapse
I'll get the phone tomorrow!!!!!
So, by upgrading to the latest official rom avaiable I'll have the most recent modem and bootloader, right?
Do I need to follow the order you mentioned: modem->bootloader->recovery->backup->croms or can I flash TWRP, backup every partition, flash most recent modem and bootloader (not sure if I can flash a bootloader) and then install croms?
No, only flashing a newer custom ROM won't update your Bootloader and Modem. You will need to flash those files separately via Odin. Then you can flash the custom ROM you want. The order is simple. Get a custom recovery first, TWRP. Then update your Modem and Bootloader. Then wipe the device from TWRP (full wipe, take backup beforehand if you need) and flash the custom ROM of your choice.
Safest way to upgrade the modem and bootloader is via ota update on a completely stock unrooted rom with stock recovery. After the phone is running the latest rom, then start with customization.
audit13 said:
Safest way to upgrade the modem and bootloader is via ota update on a completely stock unrooted rom with stock recovery. After the phone is running the latest rom, then start with customization.
Click to expand...
Click to collapse
I have the phone and managed to update it to 5.0 -> n9005xxugboa1
Is it the latest version or should I update it to another one?
BOD2 appears to be the latest according to sammobile.com: http://www.sammobile.com/firmwares/database/SM-N9005/
audit13 said:
BOD2 appears to be the latest according to sammobile.com: http://www.sammobile.com/firmwares/database/SM-N9005/
Click to expand...
Click to collapse
I'm from Portugal but the phone is unlocked (no carrier) and they only have firmware for carrier notes... Which one should I download and flash?
Also... with a G2 I flashed a .kdz file (official rom) and ended up with a bricked phone (later fixed via warranty), but I have no warranty in this phone, how can I make sure that the file is safe?
Just check for software updates from your phone.
audit13 said:
Just check for software updates from your phone.
Click to expand...
Click to collapse
It says the phone is already at the latest version. I've cleaned framework services and checked again but got the same result.
Try removing the SIM card and moving the date ahead by two days, then try again.
audit13 said:
Try removing the SIM card and moving the date ahead by two days, then try again.
Click to expand...
Click to collapse
Done that, no update avaiable. Connected to Kies3, no update avaiable.
Is it really in a old version? It's 5.0. Do I really need the latest version to start flashing a recovery?
Also, can I use the recovery without flashing it? I want to check if it works nicely before flashing if it is possible. TWRP can be used to flash any rom right? I'm interested in trying darklord first.
Yes, you can flash recovery without updating. I suggested updating because the update probably deals with the stage fright bug.
I have read a fair amount here, but I'm not getting entirely relevant info and am hoping for some help.
I THINK I have finally found the place for stock roms. sammobile.com???
Now a bit of background.
I bought this phone used a few days ago. When I had a look, it is already rooted, which I'm fine with.
It is running 4.4.2. I'd like to upgrade to 5.0.x. Gotta friend with the same model. That's what he recommends.
I can live with 4.4.2 if I have to, meaning if I can't upgrade.
Since this is new (to me) I can live with losing all user data. Only thing is my wifi password is long and random and a pain to type in, but that is about all I'll suffer.
I had removed some apps using debloater, mostly just to see, but have since restored them. Then tried to update, got the message, which essentially says "you've got a custom rom. No updates for you".
I know the phone is unlocked, but not sure if factory or by unlock code. Does it matter, and if so, how can I tell?
I know the previous owner had a fido sim, and I noticed some bell apps on here. If I've read correctly, that doesn't guarantee this was originally a bell phone. Is there any way I can tell? Right now I have no sim. I can shove in an old speakout sim that is deactivated.
So anyway
Model number SGH-I337M
Android Version 4.4.2
Baseband version I337MVLUFNI2
Kernel Version
3.4.0-2767305
[email protected] #1
Mon Sep 29 13:01:35 KST 2014
Build Number
KOT49H.I337MVLUFNI2
SE for Android Status
Enforcing SEPF_SHG-I337M_4.4.2_0032
Wed Oct 15 17:04:13 2014
Secure Boot status
Type: Samsung
I've downloaded ODIN, but not a ROM yet, since I'm not positive who's I should use.
Also, I had gone thru the guide to enable AWS. That seems to work, as it would take the sim at the wind kiosk. I'd like to keep that, but if I have to redo it, that is fine.
I trust it is not a good idea to upgrade to a "stock" 5.0.x by just flashing roms?
Thx for any help.
ok, another question. I just registered at sammobile, but they don't seem to have roms for the S4??? Are they hidden somewhere? Where can I get stock roms, if not there? Thx
Nevermind. You have to type in the device name. It just isn't on the pulldown list.
Another question you might find stupid.
If I update to (for example) the Bell Roms, do I have to have a valid Bell sim in order to do an update?
Well maybe 2 stupid questions.
I still have to use triangle away for flashing back to 4.4.2 don't I? I read somewhere that they (meaning Samsung) expected the count to be > 0 at some point but I don't remember at what version, and I can't seem to find it again.
So what do you guys do? Flash it a couple of times to get the count right?
If the phone is sim unlocked, it should remain permanently unlocked regardless of whether you flash custom or stock ROMs.
The easiest way to get to stock LP would be to flash the stock LP rom via Odin from here: http://www.sammobile.com/firmwares/database/SGH-I337M/
Before the first boot with the LP ROM, the phon should be factoru reset via stock recovery.
Doesn't really matter whether you flash Bell, Rogers, or Telus. The hardware used by all 3 carriers is the same. The only difference would be in the apps that are installed with each stock ROM.
audit13 said:
If the phone is sim unlocked, it should remain permanently unlocked regardless of whether you flash custom or stock ROMs.
The easiest way to get to stock LP would be to flash the stock LP rom via Odin from here: http://www.sammobile.com/firmwares/database/SGH-I337M/
Before the first boot with the LP ROM, the phon should be factoru reset via stock recovery.
Doesn't really matter whether you flash Bell, Rogers, or Telus. The hardware used by all 3 carriers is the same. The only difference would be in the apps that are installed with each stock ROM.
Click to expand...
Click to collapse
Thx. that should get me started anyway.
scott1256ca said:
Thx. that should get me started anyway.
Click to expand...
Click to collapse
I think I have reflashed properly. I'm downloading the update (probably to 5.0.1??) via phone now, but I noticed after I started that I have the warning triangle. So maybe the update will not install when it is done. I'll know in a couple of hours I guess.
So I should have run triangle away BEFORE the reflash? Or are you no longer supposed to run that? Or is there some android version after which you are no longer supposed to use it?
Thx
Well, phone seems to have updated to 5.0.1, which is what I wanted. With the update, the warning triangle is gone also.
So thanks again for your help. I guess I'll be on to other things here.
Hello everybody,
I have a Moto x play running CM 13. I followed the process listed somewhere in this forum and successfully installed cm 13.
Bad news is my laptop got stolen at uni. I had installed Motorola drivers and all that stuff in there, so now I'm wondering if I can go through this process without that laptop. I hope I can.
I only have the cellphone and I would like to return it to its original firmware so I can sell it.
Is there a safe way to do this without "bricking" my phone? I'm not very well versed in these processes and managed to install cm13 only because the procedure was very clear. I hope you guys can help me!
The original carrier is Iusacell (Mexico), although the cellphone itself is unlocked and takes any Sim.
thanks in advance!
gabrsmn said:
Hello everybody,
I have a Moto x play running CM 13. I followed the process listed somewhere in this forum and successfully installed cm 13.
Bad news is my laptop got stolen at uni. I had installed Motorola drivers and all that stuff in there, so now I'm wondering if I can go through this process without that laptop. I hope I can.
I only have the cellphone and I would like to return it to its original firmware so I can sell it.
Is there a safe way to do this without "bricking" my phone? I'm not very well versed in these processes and managed to install cm13 only because the procedure was very clear. I hope you guys can help me!
The original carrier is Iusacell (Mexico), although the cellphone itself is unlocked and takes any Sim.
thanks in advance!
Click to expand...
Click to collapse
to flash original firmware without PC you can use Chainfire's Flashfirehttp://forum.xda-developers.com/general/paid-software/flashfire-t3075433, however - it's still kinda experimental, needs some knowlege, and I'm not really sure if it supports our device. Reading through its thread may give you some clues. This will not revert your phone to out-of-the-box condition - that would take relocking your bootloader and PC is needed to do so (warranty will be still voided anyway). So maybe just try flashing some stock ROM in TWRP. The procedure will be the same as flashing CM.
minimale_ldz said:
to flash original firmware without PC you can use Chainfire's Flashfirehttp://forum.xda-developers.com/general/paid-software/flashfire-t3075433, however - it's still kinda experimental, needs some knowlege, and I'm not really sure if it supports our device. Reading through its thread may give you some clues. This will not revert your phone to out-of-the-box condition - that would take relocking your bootloader and PC is needed to do so (warranty will be still voided anyway). So maybe just try flashing some stock ROM in TWRP. The procedure will be the same as flashing CM.
Click to expand...
Click to collapse
I feel more comfortable with the second option. I found this github with MXP ROMs for my country and carrier: https://github.com/motoxplay/stock
I honestly can't remember if I had it at the beginning with Android 5 or 6. What happens if I flash Android 6 and it originally was 5? I suppose I should make a backup "nandroid" first.
BTW, can the bootloader be locked again via a new PC?
gabrsmn said:
I feel more comfortable with the second option. I found this github with MXP ROMs for my country and carrier: https://github.com/motoxplay/stock
I honestly can't remember if I had it at the beginning with Android 5 or 6. What happens if I flash Android 6 and it originally was 5? I suppose I should make a backup "nandroid" first.
BTW, can the bootloader be locked again via a new PC?
Click to expand...
Click to collapse
Flashing newer firmware won't break anything, it's a normal update. Worse thing would be if you tried to flash Lollipop over Marshmallow.
Making backup is always a good idea, do mind however, that flashing full stock firmware means overwriting your TWRP with stock recovery. Also, be aware the files you linked are actually firmware and not TWRP flashable zips.
And yes, you should be able to relock bootloader with original firmware.