Okay so I've searched the forums and haven't found the answer to what I'm looking for quite yet. I'm not new to rooting, but new to the Galaxy Note 3. I just recently started getting prompted for the update to KK4.4.2 (I have the Verizon model and we all know how long they take to push out updates.) So I decided to flash the leaked de-oxed NC2 rom and after follow the instructions from here. I reboot and get stuck at a black screen. It boots no further and I have to pull the battery to get back to recovery.
Am I missing something, another step maybe? Is this an old process?
Any help would be appreciated. Thanks
Did you also flash the firmware package in odin?
<Note3>
LeftyGR said:
Did you also flash the firmware package in odin?
<Note3>
Click to expand...
Click to collapse
Yes I also flashed the firmware through Odin. Does it matter which version of Odin I used?
Odin doesn't matter.
Root 4.3
Install safe strap.
Now you can update to the rooted 4.4 through odin.
barrackOBAMA said:
Odin doesn't matter.
Root 4.3
Install safe strap.
Now you can update to the rooted 4.4 through odin.
Click to expand...
Click to collapse
Actually it looks as if this was caused by Odin 3.09. It doesn't seem to like the bootloader file for NC2 and for some reason doesn't load the entire boot portion of the file. Flashed with Odin 3.07 and booted no problem. Thanks for the input though.
Related
After flashing 4.3 leak on my I9500 using Odin 3.09, it doesn't boot up as it should, I have wiped data/cache, but to no avail. I even flashed the Russian official 4.3 firmware, but it just doesn't boot up as it should.
When I turn on the phone, the phone stops right after the "Galaxy S4 I9500," screen. I see a black screen right after that.
I tried to downgrade my phone using Odin 3.09, 3.07 and 3.04, but it keeps failing. My S4 shows "unsupported version," when I try to flash stock 4.2.2.
I am guessing this is probably happening because of the newer bootloader, the newer bootloader is making it impossible to downgrade to an older version.
exclaimed said:
After flashing 4.3 leak on my I9500 using Odin 3.09, it doesn't boot up as it should, I have wiped data/cache, but to no avail. I even flashed the Russian official 4.3 firmware, but it just doesn't boot up as it should.
When I turn on the phone, the phone stops right after the "Galaxy S4 I9500," screen. I see a black screen right after that.
I tried to downgrade my phone using Odin 3.09, 3.07 and 3.04, but it keeps failing. My S4 shows "unsupported version," when I try to flash stock 4.2.2.
I am guessing this is probably happening because of the newer bootloader, the newer bootloader is making it impossible to downgrade to an older version.
Click to expand...
Click to collapse
ok try this first use the cf root provided in the cf root thread and then dload the latest 4.2.2 http://samsung-updates.com/details/14135/Galaxy_S_4_Exynos_Octa/GT-I9500/XFE/I9500XXUBMH1.html from here and flash it see what happens
Solved.
The problem was that I didn't flash the stock rom that came with my phone. I flashed that and my phone was restored to its factory settings. However my imei was messed up, it was showing me 0049. I rooted, flashed twrp recovery and used twrp to restore from a backup and I got my imei back along with my data.
I will wait for 4.3 to become flashable and see how it goes then.
hypergamer1231 said:
ok try this first use the cf root provided in the cf root thread and then dload the latest 4.2.2 http://samsung-updates.com/details/14135/Galaxy_S_4_Exynos_Octa/GT-I9500/XFE/I9500XXUBMH1.html from here and flash it see what happens
Click to expand...
Click to collapse
Hi, I got back from version 4.2.2 to say. Thank you. But the 4.2.2 's what I want to install other versions (eg Russian version) still odin error. Is it possible to install other versions?
volkantipi said:
Hi, I got back from version 4.2.2 to say. Thank you. But the 4.2.2 's what I want to install other versions (eg Russian version) still odin error. Is it possible to install other versions?
Click to expand...
Click to collapse
i had this issue on my gs3 , try to move the odin md5 rom file and the odin folder to C: or my documents . maybe one of those directories where u have them right now are too large (odin has issues with long directories)
NOTE: AT&T variant. Phone is running 4.2.2 with MF3 baseband
So I'm helping a friend root his phone and run a custom ROM. The root went successfully (motochopper) and we installed SafeStrap and then we did a backup and wipe and then installed a 4.3 Google Play edition ROM (first mistake as we meant to download the 4.2 version)
I have the stock firmware zip for the phone and figured that that was the way to fix it, but I can't figure out how to get it to install. Through ADB it gives me an error after starting DAEMON. I converted the zip to a .tar and tried to use ODIN but ODIN stops working as soon as I tell it to run. I made sure I had the most current, correct drivers and am running ODIN3 v1.85. I thought maybe if I put it on the SD card I could install it though that method via the stock recovery but it says there is an invalid arguement.
What am I doing wrong?
Help
h_smith said:
NOTE: AT&T variant. Phone is running 4.2.2 with MF3 baseband
So I'm helping a friend root his phone and run a custom ROM. The root went successfully (motochopper) and we installed SafeStrap and then we did a backup and wipe and then installed a 4.3 Google Play edition ROM (first mistake as we meant to download the 4.2 version)
I have the stock firmware zip for the phone and figured that that was the way to fix it, but I can't figure out how to get it to install. Through ADB it gives me an error after starting DAEMON. I converted the zip to a .tar and tried to use ODIN but ODIN stops working as soon as I tell it to run. I made sure I had the most current, correct drivers and am running ODIN3 v1.85. I thought maybe if I put it on the SD card I could install it though that method via the stock recovery but it says there is an invalid arguement.
What am I doing wrong?
Help
Click to expand...
Click to collapse
What stock firmware zip do you have? You have to have the mf3 .tar.md5 file if you're trying to use odin
How does he have mf3 and motochopper works? It shouldn't. Also you have to have a custom recovery to flash the gpe rom and we don't. The closest thing we have is safestrap.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
HiTideBlastoise said:
How does he have mf3 and motochopper works? It shouldn't. Also you have to have a custom recovery to flash the gpe rom and we don't. The closest thing we have is safestrap.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure. I just used the first method I found and it worked. Then when it came to the recovery part that's when I found out about his baseband
jd1639 said:
What stock firmware zip do you have? You have to have the mf3 .tar.md5 file if you're trying to use odin
Click to expand...
Click to collapse
I'm on the SamMobile site trying to find the firmware and it says that they don't have it. I find that weird that such a popular model doesn't have the firmware needed to do this. I put in the correct model and country
EDIT: nevermind.
Hello everybody im in a little bit of a crisis.
I tried to update my modem to MK2 and I used odin to do so. It turns out that it failed for some reason.
After that whenever I boot my phone it gives me a black screen and says Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again.
After that I followed this youtube video right here: https://www.youtube.com/watch?v=G1jyZ5QafAQ and downloaded this file to go back to stock: http://downloadandroidfiles.org/download-l720vpuamdc_l720sptamdc_spr-zip/
But yet it still gave me a Fail in odin. Any help would be appreciated as I am Freaking out right now
Here is the message log directly from odin when it starts
Firmware update starts
aboot.mbn
NAND write start
Complete(Write) Operation Failed
I switched USB ports now Odin is saying there is no PIT partition
88exp88 said:
Hello everybody im in a little bit of a crisis.
I tried to update my modem to MK2 and I used odin to do so. It turns out that it failed for some reason.
After that whenever I boot my phone it gives me a black screen and says Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again.
After that I followed this youtube video right here: https://www.youtube.com/watch?v=G1jyZ5QafAQ and downloaded this file to go back to stock: http://downloadandroidfiles.org/download-l720vpuamdc_l720sptamdc_spr-zip/
But yet it still gave me a Fail in odin. Any help would be appreciated as I am Freaking out right now
Click to expand...
Click to collapse
If your on MJA/MK2 firmware (bootloader) you cannot go back to MDC (the file you showed).
Also did you run PC Odin 'As Administrator'?
You can find the link to the MK2 here.
leaderbuilder said:
If your on MJA/MK2 firmware (bootloader) you cannot go back to MDC (the file you showed).
Also did you run PC Odin 'As Administrator'?
You can find the link to the MK2 here.
Click to expand...
Click to collapse
I am on MDC bootloader. What I did was download the tar file from stockroms.net for MDC. And I ran the 3.07 odin as adimistrator and it worked. Thank you cause I think that it was me not clicking run as administrator. Another question: Is it worth upgrading to MK2 if I wanna root again or should I just keep MK2. I have the geeksquad warrenty from bestbuy so it shouldn't matter if it trips the knox flag because I give them rooted phones all the time.
88exp88 said:
I am on MDC bootloader. What I did was download the tar file from stockroms.net for MDC. And I ran the 3.07 odin as adimistrator and it worked. Thank you cause I think that it was me not clicking run as administrator. Another question: Is it worth upgrading to MK2 if I wanna root again or should I just keep MK2. I have the geeksquad warrenty from bestbuy so it shouldn't matter if it trips the knox flag because I give them rooted phones all the time.
Click to expand...
Click to collapse
I wouldn't update to the knox bootloader (take the OTA or flash the full .tar) but that's me, for now.
Since you're on the earlier bootloader you can still update to any number of ROMs that have the knox bootloader removed.
Also I would definitely update the modem firmware - Unknownforce has a thread for that here.
Spend some time and read and you'll find loads of stuff you can do.
Good luck.
leaderbuilder said:
I wouldn't update to the knox bootloader (take the OTA or flash the full .tar) but that's me, for now.
Since you're on the earlier bootloader you can still update to any number of ROMs that have the knox bootloader removed.
Also I would definitely update the modem firmware - Unknownforce has a thread for that here.
Spend some time and read and you'll find loads of stuff you can do.
Good luck.
Click to expand...
Click to collapse
So I can use the files http://forum.xda-developers.com/showthread.php?t=2338919 in odin to update. Also since I am on mdc could I just use the latest in odin or do I have to go incrementaly.
Sent from my SPH-L720 using xda app-developers app
If you truly are on MDC and did not trip the knox bootloader you can Odin back to stock MDC. That will wipe the phone completely, giving you an all MDC phone - bootloader, recovery (stock), kernel, modem and ROM.
But I would just jump to MF9. It was the last official without the Knox bootloader. You can grab that here.
This is the FULL system tar. All stock, kernel, recovery, ROM Modem.
Extract the .tar.md5 and place that in the PDA slot and that's it. Make sure you don't check 'repartition'!.
Then use CF-Autoroot to root and again be careful NOT to check anything like repartition etc.
Once rooted you can then open up supersu, update the binaries. Go to playstore and download GooManager. User that to install custom recovery and then you can flash away.
I do suggest you spend some time here reading a whole bunch. You'll learn a lot about these methods and how and what you can do.
Good luck.
leaderbuilder said:
If you truly are on MDC and did not trip the knox bootloader you can Odin back to stock MDC. That will wipe the phone completely, giving you an all MDC phone - bootloader, recovery (stock), kernel, modem and ROM.
But I would just jump to MF9. It was the last official without the Knox bootloader. You can grab that here.
This is the FULL system tar. All stock, kernel, recovery, ROM Modem.
Extract the .tar.md5 and place that in the PDA slot and that's it. Make sure you don't check 'repartition'!.
Then use CF-Autoroot to root and again be careful NOT to check anything like repartition etc.
Once rooted you can then open up supersu, update the binaries. Go to playstore and download GooManager. User that to install custom recovery and then you can flash away.
I do suggest you spend some time here reading a whole bunch. You'll learn a lot about these methods and how and what you can do.
Good luck.
Click to expand...
Click to collapse
Hey man, just wanted to say thanks for continuing your tradition of quality posting. It is responses like this that made the E4GT forums such a great place to be.
leaderbuilder said:
If you truly are on MDC and did not trip the knox bootloader you can Odin back to stock MDC. That will wipe the phone completely, giving you an all MDC phone - bootloader, recovery (stock), kernel, modem and ROM.
But I would just jump to MF9. It was the last official without the Knox bootloader. You can grab that here.
This is the FULL system tar. All stock, kernel, recovery, ROM Modem.
Extract the .tar.md5 and place that in the PDA slot and that's it. Make sure you don't check 'repartition'!.
Then use CF-Autoroot to root and again be careful NOT to check anything like repartition etc.
Once rooted you can then open up supersu, update the binaries. Go to playstore and download GooManager. User that to install custom recovery and then you can flash away.
I do suggest you spend some time here reading a whole bunch. You'll learn a lot about these methods and how and what you can do.
Good luck.
Click to expand...
Click to collapse
Ok I have upgraded to MF9 now should I use Unkown Forces links: http://forum.xda-developers.com/showthread.php?t=2338919 to upgrade the firmware and modem?
And when I try to root with CF auto root on MF9 it fails on complete write operation failed.
Strike that its all good
If you're on MF9 full rooted you can update your firmware/modem following Unknownforce's instructions.
HOWEVER PLEASE take heed about the MJA(MK2 too) Notes: ...
some people report better success with turning Auto Reboot and F. Reset Time unchecked. Do the same flash, but when you see PASS on Odin, unplug the phone and Hold the Power key for 10 seconds to reboot.
Click to expand...
Click to collapse
And read through the whole post not just the OP. Some people had to flash it a few times to get it to show up (in system info) properly - mainly because they didn't follow directions precisely and skipped the note part on MJA/MK2.
Since you're now on MF9 fully rooted (stock) you can install yourself a custom recovery (Philz or TWRP - the latest Philz;philz_touch_6.08.9-jfltespr, seems to be the most reliable for now) and flash some ROMs. Virtually all of the 4.3/4.4 ROMs require the MK2 modem so know that too.
One thing I would highly recommend is to spend some time reading through the sections to get a clearer understanding of how this device behaves vs others (HTC, Moto etc.). Every device has it's peculiarities and caveats and not paying attention to them could ruin you day.
i have a different problem. i think my sprint sph-l720 bricked because my screen is stuck on kernel is not seandroid enforcing and it also says set warrant bit: kernel. need help as soon as possible
Tonymontana2421 said:
i have a different problem. i think my sprint sph-l720 bricked because my screen is stuck on kernel is not seandroid enforcing and it also says set warrant bit: kernel. need help as soon as possible
Click to expand...
Click to collapse
People need to know the difference between soft bricked and hard bricked. Most say bricked and they mean soft. Hard is nearly impossible to get the phone back up and running. I have that same problem when I try to install a kernel. You need to reflash a ROM.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
People need to know the difference between soft bricked and hard bricked. Most say bricked and they mean soft. Hard is nearly impossible to get the phone back up and running. I have that same problem when I try to install a kernel. You need to reflash a ROM.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
can you tell me which rom i need to flash because i cant figure out what rom i need to use in odin
Hello guys, so i sold my AT&T Galaxy S4 to a friend an move up to Note 3.
After a couple of weeks he downloaded an app from Playstore and got into a Bootloop. I tol;d him i could help him as I have come through the same procedure again in the past.
I tried flashing the same rom the phone had by that time "I337UCUFMLD_OneClick" and i Got a FAIL.
Soon i realized the phone was bricked. I have been searhing for 5-6 hours today, tried to flash "ALL_ATT_I337UCUFNB1_I337ATTFNB1_505595_REV06_user_low_ship_MULTI_CERT.tar", all MK2 roms I Found here, and the only once which worked was flashing the "pit" file and flashing "I337_NC1_Stock_Recovery.tar". Now The phone has access to both Download & recovery mode but
i 'cant enable usb debugging cause i can't access the system.
If anyone has a clue, please help!
PS: Sry for the long description, can't post links.
You should be able to flash the all in one nb1 tar use Odin 3 v1.85 make sure you extract the rar and load the tar in the pda slot. Unless it's been updated to nc1 then you'll have to wait and hope someone releases a all in one for that.
Sent from my SGH-I337. And no we can't flash Aosp based ROMs with a locked bootloader!
dave5777 said:
You should be able to flash the all in one nb1 tar use Odin 3 v1.85 make sure you extract the rar and load the tar in the pda slot. Unless it's been updated to nc1 then you'll have to wait and hope someone releases a all in one for that.
Sent from my SGH-I337. And no we can't flash Aosp based ROMs with a locked bootloader!
Click to expand...
Click to collapse
Thanks for the quick responce!
Nope, i flashed only the stock recovery from NC1 cause it was the only one i could find
Att recently pushed the nc1 firmware if your friend unknowingly applied the nc1 update and it flashed a new bootloader then that would make the nb1 Odin fail. I think your best bet is going to the Samsung Rep at your local Best buy and they can flash the factory image.
Sent from my SGH-I337. And no we can't flash Aosp based ROMs with a locked bootloader!
dave5777 said:
Att recently pushed the nc1 firmware if your friend unknowingly applied the nc1 update and it flashed a new bootloader then that would make the nb1 Odin fail. I think your best bet is going to the Samsung Rep at your local Best buy and they can flash the factory image.
Sent from my SGH-I337. And no we can't flash Aosp based ROMs with a locked bootloader!
Click to expand...
Click to collapse
Thanks for the advice, we were about to after the weekend.
PS: I tried flashing using 1.85 ... reaches 90% of SYSTEM and fails...
dave5777 said:
Att recently pushed the nc1 firmware if your friend unknowingly applied the nc1 update and it flashed a new bootloader then that would make the nb1 Odin fail. I think your best bet is going to the Samsung Rep at your local Best buy and they can flash the factory image.
Sent from my SGH-I337. And no we can't flash Aosp based ROMs with a locked bootloader!
Click to expand...
Click to collapse
It has been reported that the NC1 update did not incriment the Q-fuse count in aboot. If this is true, it should be safe to Odin NB1 back onto a phone that took the NC1 update without it causing failure..
Solution
dave5777 said:
You should be able to flash the all in one nb1 tar use Odin 3 v1.85 ... !
Click to expand...
Click to collapse
After several tries i managed to flash it back to STOCK NB1 with no problem.
The only Problem some people may have is that if you try flashing with odin 3+ and then try 1.85, you will fail due to Windows instabilitty.
I recommend taking battary of the phone for 1 hour (may sound too much but worked for me) restart PC, and try flashing right away after your computer boots up!
I will propably make a guide out of this cause that brick was tricky as hell.
Thanks everyone for replying
PROBLEM SOLVED :good:
Everytime I try to boot into system, it freezes and then restarts. I just flashed lollipop OC4 rom through FlashFire? Help please
safwanz1 said:
Everytime I try to boot into system, it freezes and then restarts. I just flashed lollipop OC4 rom through FlashFire? Help please
Click to expand...
Click to collapse
Did you uninstall safestrap before you use flashfire?
Do you use the rooted lolli rom mentioned in the guide or the custom lolli rom. If you use custom lolli, is that rom mentioned that it is flashfire compatible?
I understand you are on NC1 bootloader so in order to OC4 working properly, OC4 bootloader need to be flashed via odin.
If you try everything and did not work, go back to NB1 and start from there. Use the NB1 firmware that I mentioned before.
sway8966 said:
Did you uninstall safestrap before you use flashfire?
Do you use the rooted lolli rom mentioned in the guide or the custom lolli rom. If you use custom lolli, is that rom mentioned that it is flashfire compatible?
I understand you are on NC1 bootloader so in order to OC4 working properly, OC4 bootloader need to be flashed via odin.
If you try everything and did not work, go back to NB1 and start from there. Use the NB1 firmware that I mentioned before.
Click to expand...
Click to collapse
So dude, when I went into download mode, everytime I tried to place that ALLAT&T file into the AP slot, it would cause Odin to freeze and not respond. Naturally, I got angry and decided to reboot into system and magically, I could use the OS again. Now I think I'm going to flash the bootloader like you said
safwanz1 said:
So dude, when I went into download mode, everytime I tried to place that ALLAT&T file into the AP slot, it would cause Odin to freeze and not respond. Naturally, I got angry and decided to reboot into system and magically, I could use the OS again. Now I think I'm going to flash the bootloader like you said
Click to expand...
Click to collapse
I am sure you did extract the .md5 from the .rar. The latest odin is Version 3.10.7 but I am using version 3.10.6 for that .md5 and it went well too. Try with different odin then.
sway8966 said:
Did you uninstall safestrap before you use flashfire?
Do you use the rooted lolli rom mentioned in the guide or the custom lolli rom. If you use custom lolli, is that rom mentioned that it is flashfire compatible?
I understand you are on NC1 bootloader so in order to OC4 working properly, OC4 bootloader need to be flashed via odin.
If you try everything and did not work, go back to NB1 and start from there. Use the NB1 firmware that I mentioned before.
Click to expand...
Click to collapse
sway8966 said:
I am sure you did extract the .md5 from the .rar. The latest odin is Version 3.10.7 but I am using version 3.10.6 for that .md5 and it went well too. Try with different odin then.
Click to expand...
Click to collapse
Right dude, I just flashed the NC1 flasher and then i tapped reboot, now it's been on the custom unlock screen for a few minutes, what should I do?
Now i rebooted the device and I cant get into system or safestrap.
safwanz1 said:
Right dude, I just flashed the NC1 flasher and then i tapped reboot, now it's been on the custom unlock screen for a few minutes, what should I do?
Now i rebooted the device and I cant get into system or safestrap.
Click to expand...
Click to collapse
Wow, NC1 flasher is to use safestrap in lollipop. It only flash the NC1 kernel.
Are you in Kitkat or lollipop. If you were in your lollipop you need to update your lollipop bootloader.
As I said before, if your phone went to softbrick just flash the NB1 firmware via odin.
I swear, you are a legend, an absolute god. The amount of help and experience you have given me, if only I could pay you (I'm 15, so I can't make a PayPal yet) Right now I'm on Albe95's Note 5 port rom.