Is there a way I can get the NE9 stuff without wiring in & using Odin ?
Or is that kind of the way since the bootloader is still locked flashing via recovery won't work ?
I flashed Beans's NE9 rom which was apparently a mistake since the Baseband still says NCG
Related
Hello guys, I'm trying to unlock my sprint S4 to use with metroPCS....I got the phone from a friend of mine because he switched to iphone. The phone is currently running the cm11 archerom rom with NAE baseband
What I've done so far was
- followed the international sim unlock guide and was able to downgrade my modem from NAE to MDC via odin running cm11.
- I couldn't get the phone to go into Diag mode to use the s4 unlocker program...I tried using scripts (Aosp script for diag mode) but the phone would not get recognized on my computer ( running windows 8) so the S4 unlock flasher couldn't detect the device.
- I tried to odin the phone back to stock samsung twz so that I could get into diag mode easier. I flashed stock MF9 rooted touchwiz rom via odin but it failed everytime. I was trying to flash the mdc baseband after so that I could use to unlocker program.
- The phone soft-bricked after that but I was able to fix it by flashing a custom recovery but my phone audio went out with DSPmanager crashing and music, audio not playing.
-I resolved that problem by flashing back the NAE modem, now everything is back to where I started from, I'm not sure where to go from now
What I might do next is, try to use cwm to flash back to stock samsung twz rom but I'm not sure which rom to flash in order for me to unlock my S4....
What do you guys think? Thanks for reading!
Odin full NAE. You cannot downgrade the bootloaders thus why you were not able to successfully Odin MF9 because you have a Knox boot loader.
I tried flashing the full NAE ROM via Odin....it almost went pass "system.IMG.ext4" in Odin and then it failed on write nand...
I flashed recorevry and now /data is not mounting. I flashed the achrom c11 ROM again but its not booting now, its stuck on the android screen (soft-bricked.)
What should I do next? Thanks for your help BTW
I know this is counter intuitive to most people, they usually want to stick with the older bootloader without that KNOX crap.
I want the newest bootloader so I can run the current kernel for 4.4.2, right now my phone is stuck on the MG1 bootloader, which can't run the kernel for this version and I don't have WIFI.
I tried flashing numerous times with ODIN for factory firmware from sammobile. I have an I337M from Canada (Rogers/Bell/Telus)
I can't get OTA to get working again because it thinks I'm on modified system etc, bootloader, even I reflashed everything...
Have you tried a data factory reset from within stock recovery?
BriEE said:
I know this is counter intuitive to most people, they usually want to stick with the older bootloader without that KNOX crap.
I want the newest bootloader so I can run the current kernel for 4.4.2, right now my phone is stuck on the MG1 bootloader, which can't run the kernel for this version and I don't have WIFI.
I tried flashing numerous times with ODIN for factory firmware from sammobile. I have an I337M from Canada (Rogers/Bell/Telus)
I can't get OTA to get working again because it thinks I'm on modified system etc, bootloader, even I reflashed everything...
Click to expand...
Click to collapse
Check here, http://forum.xda-developers.com/showthread.php?t=2269304
Remember your on a I337M, your bootloader is unlocked. Do NOT flash any US-based AT&T firmwares or your end up with a normal locked I337. What version are you trying to flash in Odin? Flashing the MG1 firmware should work, what errors is Odin producing?
Ok so I did a idiotic thing... Did towel root on stock 4.4.2 G900VVRU1ANCG then before installing supersu or anything accidentally ran OTA (G900VVRU1ANE9)
Now phone keeps looping and installing updates...
It tries to boot normally then says booting recovery at top then starts installing updates again...
What to do now?
toy4x4xda said:
Ok so I did a idiotic thing... Did towel root on stock 4.4.2 G900VVRU1ANCG then before installing supersu or anything accidentally ran OTA (G900VVRU1ANE9)
Now phone keeps looping and installing updates...
It tries to boot normally then says booting recovery at top then starts installing updates again...
What to do now?
Click to expand...
Click to collapse
boot into download mode and reflash NCG. if that doesn't work because of the partially installed NE9 try flashing NE9 in Odin
Will I think I have it somewhat fixed... Just downloaded stock NCG and then extracted the system.img.ext4 and followed the guide from skipsoft using their toolkit to make the system.img.ext4 odin flashable.
Flashed only the NCG system.img back to phone and that worked.
Now phone is operational and all apps etc still there but I have build and kernel NCG but baseband is NE9
So now if I root on build NCG then try to OTA to NE9 how do I avoid boot loop this time? Will Supersu allow me to OTA and is there a method to keep root? ( I know how to flash the kernels and re-root --- I'd like to just keep root if possible.)
toy4x4xda said:
Will I think I have it somewhat fixed... Just downloaded stock NCG and then extracted the system.img.ext4 and followed the guide from skipsoft using their toolkit to make the system.img.ext4 odin flashable.
Flashed only the NCG system.img back to phone and that worked.
Now phone is operational and all apps etc still there but I have build and kernel NCG but baseband is NE9
So now if I root on build NCG then try to OTA to NE9 how do I avoid boot loop this time? Will Supersu allow me to OTA and is there a method to keep root? ( I know how to flash the kernels and re-root --- I'd like to just keep root if possible.)
Click to expand...
Click to collapse
flash the full NE9 in Odin, then flash the NCG kernel, root, then flash the NE9 kernel.
see this thread http://forum.xda-developers.com/verizon-galaxy-s5/general/how-to-root-g900vvru1ane9-t2836201
toy4x4xda said:
Will I think I have it somewhat fixed... Just downloaded stock NCG and then extracted the system.img.ext4 and followed the guide from skipsoft using their toolkit to make the system.img.ext4 odin flashable.
Flashed only the NCG system.img back to phone and that worked.
Now phone is operational and all apps etc still there but I have build and kernel NCG but baseband is NE9
So now if I root on build NCG then try to OTA to NE9 how do I avoid boot loop this time? Will Supersu allow me to OTA and is there a method to keep root? ( I know how to flash the kernels and re-root --- I'd like to just keep root if possible.)
Click to expand...
Click to collapse
lmao.. you did all that for no reason.. all the odin roms, kernels and modems are all available already..
You flashed ne9 kernel/rom so you need to flash ne9 modem/baseband..
For future reference, its easier to start on ncg root install ss.. then flash rom.zip of choice and flash the odin firmware for it.. its real easy and u can go from ncg to nk for example without worrying about an ota
I'm trying to attempt to update to Lollipop via the method on this forum.
However my phone bricked and I had to factory reset all the way to NCG.
However after I installed NHA, the baseband version continues to say NHA, despite me flashing NI2 and NK2 right after.
Is there a problem or is this normal?
Any ideas?
Try reflashing the corresponding Firmware via Odin for the current Build you are on. The Firmware, not just the Kernel.
You can find Firmware files in the Odin back to stock thread.
http://forum.xda-developers.com/showthread.php?t=2784880
I hit on UPDATE on the phone for an OTA update but it only says UNABLE TO CONNECT AT&T SERVER. When I bought it, it had 5.0.1 (I337UCUGOC3) out of the box. Searching on internet says that is bootloader locked (so I cant do anything).
- Can I Update to I337UCUGOK2 and bootloader will be unlocked (I mean, will I be able to do it)?
- Does anyone know where can I grab I337UCUGOK2 for offline install and is it ODIN safe to update it (remember I have I337UCUGOC3 bootloader locked)?
please help
Once the bootloader is locked, it will always be locked until someone finds a way to unlock it. Updating the bootloader will not allow it to be unlocked.
cybercuate said:
I hit on UPDATE on the phone for an OTA update but it only says UNABLE TO CONNECT AT&T SERVER. When I bought it, it had 5.0.1 (I337UCUGOC3) out of the box. Searching on internet says that is bootloader locked (so I cant do anything).
- Can I Update to I337UCUGOK2 and bootloader will be unlocked (I mean, will I be able to do it)?
- Does anyone know where can I grab I337UCUGOK2 for offline install and is it ODIN safe to update it (remember I have I337UCUGOC3 bootloader locked)?
please help
Click to expand...
Click to collapse
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.
help... I want to RMA it
sway8966 said:
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.
Click to expand...
Click to collapse
Everywhere says I need a kitkat rom as base.
My s4 came with 5.0.1 with OC3 and bootloader locked out of the box. I tried some post where says I can flash TWRP and CWM but my phone stucked on bootloops. Then I managed to get back to stock rom and now when I want to turn it on it says " SAMSUNG (and lower on the screen) Custom"
Camera began to fail and I want to return it as RMA but I was looking to reset the flash counter but every post I read is that OC3 bootloader locked users are just doomed.
Do you know a method that I can do for reset that counter?
Camera dont focus anymore and I tried all the posts about safemode, etc.
cybercuate said:
Everywhere says I need a kitkat rom as base.
My s4 came with 5.0.1 with OC3 and bootloader locked out of the box. I tried some post where says I can flash TWRP and CWM but my phone stucked on bootloops. Then I managed to get back to stock rom and now when I want to turn it on it says " SAMSUNG (and lower on the screen) Custom"
Camera began to fail and I want to return it as RMA but I was looking to reset the flash counter but every post I read is that OC3 bootloader locked users are just doomed.
Do you know a method that I can do for reset that counter?
Camera dont focus anymore and I tried all the posts about safemode, etc.
Click to expand...
Click to collapse
Flashing TWRP and CWM is for the AT&T S4 with older bootloader (MDL, MDB). After that two firmware versions the bootloader is locked.
For AT&T S4 the last full firmware released is NB1. After that they released incremental updates via OTA. That is why you need kitkat (NB1) as base.
For NB1, Muniz uploaded two firmwares. One is the stock and the other is rootable stock. Try the stock one and see you still have the custom symbol.
To reset the counter, there is an app calls Triangle away by Chainfire. However, it does not work on AT&T S4 with locked bootloader.
Trying Odin-Stock NB1
sway8966 said:
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.
Click to expand...
Click to collapse
sway8966 said:
Flashing TWRP and CWM is for the AT&T S4 with older bootloader (MDL, MDB). After that two firmware versions the bootloader is locked.
For AT&T S4 the last full firmware released is NB1. After that they released incremental updates via OTA. That is why you need kitkat (NB1) as base.
For NB1, Muniz uploaded two firmwares. One is the stock and the other is rootable stock. Try the stock one and see you still have the custom symbol.
To reset the counter, there is an app calls Triangle away by Chainfire. However, it does not work on AT&T S4 with locked bootloader.
Click to expand...
Click to collapse
Thanks. I'll try Odin it with the stock rom from your link. I'll post news here when it finish flashing
1st part - Success
I'm on 4.4.2 NB1, flash counter back to normal but still bootloader locked
Now I have to go back to OC3 to RMA it.
OTA does nothing, smartswitch shows no updates neither kies.
I'll have to Odin it back to OC3
Can I have some help?
And Success. I'm back on stock OC3 no root.
time to RMA
- camera still doesn't focus
- boot screen is back to normal but when in odin mode the counter shows 0x1
- sometimes shows "sim card could not be detected" or similar messages and force me to restart the phone (just happend 2 times until now, never happend before)
I followed this thread
http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
Post 2
Thanks to sway8966