Having a problem... I have an S5 Dev Edition for VZW and I'm having radio problems. I had a rescue .tar that would bring me back to stock, rooted NCG, which was the only ROM i was able to get a cellular signal. Since upgrading to NK2 stock firmware (aboot.mbn deleted after i backed up my aboot) I have not been able to obtain a 4G signal (3G only) on ANY ROM. I want to downgrade BACK to my NCG rescue file and start over, but when I flash it now, it hangs at the Samsung splash screen. Is there something special I'm supposed to know (or do) in order to downgrade from NK2 to NCG? I'm ready to go ahead and flash a stock .tar (since I've got a backup of my unlocked aboot) but this is my last ditch effort to avoid that. PLEASE HELP!
Related
Hello,
This is will be my first XDA post ever since I always fix the most "brickiest" problems with all the Android based devices I have ever owned but not this time.
My Galaxy S4 has been updated to the latest MJA OTA (with successful CF root) and I have attempted to re-mod the hotspot service but this caused the annoying knox message to show. When attempting to restore the JAR and ODEX files, I think I have either overwritten the files in the incorrect order (ODEX -> JAR) and the phone rebooted as FX was trying to do that. So services.odex got corrupted and it was time for my to ODIN flash the MDC full stock rom as that USED to be my solution until Samsung's brand new knox protected bootloader. ODIN is not an option for me now, since the bootloader will prevent me flashing things like the pit, aboot and probably most of the other files inside the tarball. I can flash custom recovery and the MDC kernel successfully and that's about it. With custom recovery I have flashed rooted MF8 for the base operating system, and they applied the rooted MJA rom on top. The phone shows the S4 branding but then it reboots; It cannot boot into the operating system. I do not know the condition of the flash counter atm since I cannot check that in TriangleAway but it will stay "Official" under download mode, I think. I also do not know the versions of the firmware installed either in case something from MDC tar had an succession in replace some of the partitions. I am pretty sure the kernel however is still at MDC while I managed to install the system image of the MJA stock rom.
So my question is, what can I do bring back the working MJA stock rom image (/system and kernel) using TWRP recovery? Else I will have to go to Sprint and saying that the update from OTA has bricked my phone and that I have no idea how phones work.
Thank you.
45553543 450
Sorry, I forgot to add that I know that once you have MJA flashed, you cannot downgrade back unless of course someone figured out how to disable all the bootloader security but I really do not see that happening.
Fixed my own problem. Downloaded the official MJA stock tar.md5 rom from sammobile and flashed it, and managed to restore all my data using Titanium backup. This thread can be now closed.
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 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
Hello all!
I've had a family member brick their Verizon S5 because they thought they were being smart and now I've been given the task of fixing it. The S5 was on the stock PF4 build previously (no root and no unlocked bootloader) and then had the stock OC4 tar from SamMobile flashed onto it via Odin which obviously bricked it. Furthermore they flashed the PD1 stock tar on top of that thinking that being on the same Android version would fix the problem so right now I have a phone with PD1 firmware but a PF4 bootloader. The phone currently will boot to the setup menu but has a continuous stream of error messages that makes the phone unusable (if I were able to get it into MTP transfer mode I could potentially have Kies 3 fix this).
Unfortunately, SamMobile doesn't have the PF4 tar file online yet and I don't have a spare Verizon S5 to exploit Kies with to get the tar file (I was able to get an encrypted version of the PF4 build using Kies 3's feature that pre-downloads the most recent firmware automatically but it lacks any file extensions and I've no clue how to make it usable).
I know that people have access to the stock components of PF4 like flashable tars for the modem and bootloader and even a flashable zip for custom recoveries of the entire stock PF4 build so I was wondering if anyone could help me out with getting a stock PF4 tar file (if not I will just have to wait till SamMobile puts up the file).
Any help would be greatly appreciated!
Edit: Found the firmware via Samsung-Updates and fixed the phone so help no longer needed
Closed at OP's request.
I recently picked up 2 edges a Verizon and ATT variant, I flashed the Verizon phone succesfully to G935U with this firmware http://i.imgur.com/JuIeA6g.jpg
(The 4-file link in Step 2 https://forum.xda-developers.com/ve...de-flashing-sm-935u-firmware-verizon-t3415145 )
Since that went smoothly I decided to run Odin and flash that firmware onto the ATT Edge, ( original FW is g935aucs4apk1 )
It didn't work, I recall that it got stuck at Setup Connection. So I rebooted the phone and it took me into Recovery mode, where all the CHECKS failed. So the ROM has effectively been wiped; leaving me with just the Recovery menu and DOWNLOAD screens.
Is there any way of getting my self out of this?
Fixed it. Ended up clicking Re-partition and Flash Bootloader in Odin then flashing 4-files from the T-Mobile Nougat firmware using the PrinceComsy 3.12 Odin
Not my ideal way to do this, i'm sure I've lost root potential, but I have a working phone! (w/ No xposed )
borealis17 said:
Fixed it. Ended up clicking Re-partition and Flash Bootloader in Odin then flashing 4-files from the T-Mobile Nougat firmware using the PrinceComsy 3.12 Odin
Not my ideal way to do this, i'm sure I've lost root potential, but I have a working phone! (w/ No xposed )
Click to expand...
Click to collapse
As long as you are still on bootloader 4 (and you are, since to my knowledge there isn't a higher version) you can still root your device and return it to MM if necessary. It may take some effort, but it's doable.