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)
Related
Hi everyone,
I hope someone can help me with this problem. Basically I was updating my phone to mk2 BTU via kies and it failed. Kies stopped recognising the phone and it kept going in to stock recovery.
I tried manually flashing stock mk2 via odin but I kept getting the same result.
Then I got fed up and I rooted (cf auto root) and installed TWRP and my phone booted in to a rooted mk2. My knox is now triggered which is a bit annoying but at least it works now.
The problem is if I try to flash stock rom via odin it still does the same thing boots in to stock recovery and then I have to root and install twrp again. I blame all this on KIES!
Does anyone know how to fix this?
Thanks
Any ideas anyone?
evo6 said:
...
The problem is if I try to flash stock rom via odin it still does the same thing boots in to stock recovery and then I have to root and install twrp again. I blame all this on KIES!
Does anyone know how to fix this?
Thanks
Click to expand...
Click to collapse
Not clear here - by stock rom do you mean stock MK2 ROM (unrooted, same CSC as the rooted one that works)?
Have you also tried in Kies the special "emergency recovery mode" (under tools)?
xclub_101 said:
Not clear here - by stock rom do you mean stock MK2 ROM (unrooted, same CSC as the rooted one that works)?
Have you also tried in Kies the special "emergency recovery mode" (under tools)?
Click to expand...
Click to collapse
Hi,
Yes thats right MK2 stock unrooted and same CSC. I tried KIES the first time with emergency recovery but it kept saying device unsupported, that's when i rooted it and installed TWRP and it worked. I don't understand it.
Hey guys
I have a Hong Kong Note 3 N9005. Yesterday I flashed the 4.4.2 sammobile update to my phone using ODIN 3.09. I had auto reboot and f.reset ticked. The ROM was put in AP and I hit start. Then I received the error Invalid ext4 Image. Turns out that Hong Kong versions of the N3 cannot install European ROMs. Since then I have not been able to boot my device into android. I just loop into download mode telling me it detected a firmware update. Kies was no help.
The update DID update the bootloader, so now I cannot go back to stock ROM. I have tried a few things. I tried flashing the stock Hong Kong ROM MK1, it fails. So i found a guy that fixed a similar problem buy removing the aboot.mbn file and repacking the ROM. Tried that too and the ROM flashes but it leaves me in a bootloop. Phone turns on says booting recovery then restarts. I also tried cf-root in an effort to flash another ROM still not working. I cannot get into recovery mode no matter what I do.
It seems I have run out of ideas and am reaching out for help.
Robbbie said:
Hey guys
I have a Hong Kong Note 3 N9005. Yesterday I flashed the 4.4.2 sammobile update to my phone using ODIN 3.09. I had auto reboot and f.reset ticked. The ROM was put in AP and I hit start. Then I received the error Invalid ext4 Image. Turns out that Hong Kong versions of the N3 cannot install European ROMs. Since then I have not been able to boot my device into android. I just loop into download mode telling me it detected a firmware update. Kies was no help.
The update DID update the bootloader, so now I cannot go back to stock ROM. I have tried a few things. I tried flashing the stock Hong Kong ROM MK1, it fails. So i found a guy that fixed a similar problem buy removing the aboot.mbn file and repacking the ROM. Tried that too and the ROM flashes but it leaves me in a bootloop. Phone turns on says booting recovery then restarts. I also tried cf-root in an effort to flash another ROM still not working. I cannot get into recovery mode no matter what I do.
It seems I have run out of ideas and am reaching out for help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2507403 flash this with cwm or twrp should work
jaythenut said:
http://forum.xda-developers.com/showthread.php?t=2507403 flash this with cwm or twrp should work
Click to expand...
Click to collapse
Hello thanks for replying.
Only problem is I cannot get into cwm or twrp. Any advice on what I can do to try to get CWM or twrp working? I can flash with ODIN. But with the CWM I tried it still just boot loops and does not allow me to get into recovery.
Thank in advanced.
Robbbie said:
Hey guys
I have a Hong Kong Note 3 N9005. Yesterday I flashed the 4.4.2 sammobile update to my phone using ODIN 3.09. I had auto reboot and f.reset ticked. The ROM was put in AP and I hit start. Then I received the error Invalid ext4 Image. Turns out that Hong Kong versions of the N3 cannot install European ROMs. Since then I have not been able to boot my device into android. I just loop into download mode telling me it detected a firmware update. Kies was no help.
The update DID update the bootloader, so now I cannot go back to stock ROM. I have tried a few things. I tried flashing the stock Hong Kong ROM MK1, it fails. So i found a guy that fixed a similar problem buy removing the aboot.mbn file and repacking the ROM. Tried that too and the ROM flashes but it leaves me in a bootloop. Phone turns on says booting recovery then restarts. I also tried cf-root in an effort to flash another ROM still not working. I cannot get into recovery mode no matter what I do.
It seems I have run out of ideas and am reaching out for help.
Click to expand...
Click to collapse
Same Issue here. I tried to install the 4.4.2 N9005XXUENA6_N9005OXXENA5_N9005XXUENA2 update on my Note 3 via odin 3.09.
Got an ext4 update failed error.
After this, the phone's bricked and is stuck on the Kies Recovery Screen. I tried to go into recovery mode in Kies, but it says this model does not have initialization.
I tried installing a 4.3 N9005XXUDMK3_N9005TNLDMK1_N9005XXUDMK2, but again failed. Download mode shows SW REV CHECK FAIL : [aboot] Fused 3 > Binary 2
Can someone please guide me to unbrick my phone?
I don't know what ROM I was on initially. It was the stock ROM that came with the phone.
I dont have CWM and TWRM installed.
Robbbie said:
Hey guys
I have a Hong Kong Note 3 N9005. Yesterday I flashed the 4.4.2 sammobile update to my phone using ODIN 3.09. I had auto reboot and f.reset ticked. The ROM was put in AP and I hit start. Then I received the error Invalid ext4 Image. Turns out that Hong Kong versions of the N3 cannot install European ROMs. Since then I have not been able to boot my device into android. I just loop into download mode telling me it detected a firmware update. Kies was no help.
The update DID update the bootloader, so now I cannot go back to stock ROM. I have tried a few things. I tried flashing the stock Hong Kong ROM MK1, it fails. So i found a guy that fixed a similar problem buy removing the aboot.mbn file and repacking the ROM. Tried that too and the ROM flashes but it leaves me in a bootloop. Phone turns on says booting recovery then restarts. I also tried cf-root in an effort to flash another ROM still not working. I cannot get into recovery mode no matter what I do.
It seems I have run out of ideas and am reaching out for help.
Click to expand...
Click to collapse
Got this response from MrAndroid12 in another thread I'd started:
"This is not a brick at all. Just add a .pit file and restart the upgrade via Odin again.
You should be fine."
I don't know how to add a .pit file though.
I am certain the bootloops are because it flashed the new bootloader. I think your best option is to wait for a dev like indie to release Omega V7 and try to flash that through Odin.
Or if you can extract the different partitions from the original thread you can try push them one by one with Odin.
hallydamaster said:
I am certain the bootloops are because it flashed the new bootloader. I think your best option is to wait for a dev like indie to release Omega V7 and try to flash that through Odin.
Or if you can extract the different partitions from the original thread you can try push them one by one with Odin.
Click to expand...
Click to collapse
It is the bootloader yes. But it NEEDS the bootloader to be able to boot in to KitKat. And there is no downgrading once you've installed the new BL.
Best option is to re-flash via ODIN again and not wait 2 weeks for a Dev to modify a custom ROM...
Solution
Here is the solution:
http://forum.xda-developers.com/showpost.php?p=49426283&postcount=14
m1ndst0rm said:
Here is the solution:
http://forum.xda-developers.com/showpost.php?p=49426283&postcount=14
Click to expand...
Click to collapse
Works thanks
Sent from my SM-N9005 using XDA Premium 4 mobile app
I have rooted my Samsung Note 3 with a custom rom running Jellybean 4.3 with clockwork mod recovery. I have tripped knox due to rooting it. When Kitkat came out March 17th 2014, I wanted to upgrade and go back to official firmware with Kitkat to try it out. Since I have rooted my phone to run viper4android audio kernel I am unable to do an official OTA or Kies update. That said I went about downloading the new Bell Canada Note 3 firmware 4.4.2. I was told to flash a Jellybean Bell Firmware first before flashing the Kitkat version to avoid boot loops or other problems. Trying to do so with Odin in download mode ended in failure just trying to flash jellybean stock. Didnt get that far really. It showed a fail in the Note 3 screen to this effect in read this message (sw rev check fail : sbl1 fused 2 binary 1) . Odin didnt load like I am usually use to seeing by unzipping the firmware into a folder and adding it to the PDA field. After I loaded the .tar file (md5) file into pda it checked it and then told me its finished successfully but the next line it said CS Fail. After hitting start it said fail instantly in the odin window and on the Note 3 I did see a bar showing me the progress of install for 1 second until odin told me of the fail. Now my Note is in download mode and can't get past this problem to get it running again! Please any help would be greatfull to getting me past this problem and onto Kitkat or even back to Jellybean. Any other questions you may have I will supply you the info.
Thanks
Nervous Android user!
weston109 said:
I have rooted my Samsung Note 3 with a custom rom running Jellybean 4.3 with clockwork mod recovery. I have tripped knox due to rooting it. When Kitkat came out March 17th 2014, I wanted to upgrade and go back to official firmware with Kitkat to try it out. Since I have rooted my phone to run viper4android audio kernel I am unable to do an official OTA or Kies update. That said I went about downloading the new Bell Canada Note 3 firmware 4.4.2. I was told to flash a Jellybean Bell Firmware first before flashing the Kitkat version to avoid boot loops or other problems. Trying to do so with Odin in download mode ended in failure just trying to flash jellybean stock. Didnt get that far really. It showed a fail in the Note 3 screen to this effect in read this message (sw rev check fail : sbl1 fused 2 binary 1) . Odin didnt load like I am usually use to seeing by unzipping the firmware into a folder and adding it to the PDA field. After I loaded the .tar file (md5) file into pda it checked it and then told me its finished successfully but the next line it said CS Fail. After hitting start it said fail instantly in the odin window and on the Note 3 I did see a bar showing me the progress of install for 1 second until odin told me of the fail. Now my Note is in download mode and can't get past this problem to get it running again! Please any help would be greatfull to getting me past this problem and onto Kitkat or even back to Jellybean. Any other questions you may have I will supply you the info.
Thanks
Nervous Android user!
Click to expand...
Click to collapse
you cant flash back to 4.3 when you on 4.4.2 and did you succeed when flashing 4.4.2?
Flashing
hhai2pth said:
you cant flash back to 4.3 when you on 4.4.2 and did you succeed when flashing 4.4.2?
Click to expand...
Click to collapse
I havent been able to do anything. I was on Jellybean 4.3.2 custom rom with a custom recovery and tried to flash it back to a stock version of Jellybean before the update to Kitkat. I didnt get that far to even try flashing Kitkat because flashing Jellybean Canadian stock rom was unsuccessful with the errors I mentioned in my earlier post. Now I am stuck in download mode and unable to flash using odin.
weston109 said:
I havent been able to do anything. I was on Jellybean 4.3.2 custom rom with a custom recovery and tried to flash it back to a stock version of Jellybean before the update to Kitkat. I didnt get that far to even try flashing Kitkat because flashing Jellybean Canadian stock rom was unsuccessful with the errors I mentioned in my earlier post. Now I am stuck in download mode and unable to flash using odin.
Click to expand...
Click to collapse
I think you can power if off by pressing the power button for a few seconds. And then flash a custom recovery, reboot and flash a Kit Kat custom rom via Odin or Custom recovery. Hope it helps.
weston109 said:
I havent been able to do anything. I was on Jellybean 4.3.2 custom rom with a custom recovery and tried to flash it back to a stock version of Jellybean before the update to Kitkat. I didnt get that far to even try flashing Kitkat because flashing Jellybean Canadian stock rom was unsuccessful with the errors I mentioned in my earlier post. Now I am stuck in download mode and unable to flash using odin.
Click to expand...
Click to collapse
Knox was tripped. You said it yourself. Go and read up on Knox.
The answer will be very clear afterwards. It's quite clear to me.
Also, don't take this the wrong way.... but you probably should not have done any of this my friend. Your skill level makes this obvious.
I suggest not getting a Samsung phone next time as Knox is hard to get around (it's possible, I was rooted on 4.3 and I am now on 4.4.2 stock flashed with Odin and Knox is still 0x0).
weston109 said:
I havent been able to do anything. I was on Jellybean 4.3.2 custom rom with a custom recovery and tried to flash it back to a stock version of Jellybean before the update to Kitkat. I didnt get that far to even try flashing Kitkat because flashing Jellybean Canadian stock rom was unsuccessful with the errors I mentioned in my earlier post. Now I am stuck in download mode and unable to flash using odin.
Click to expand...
Click to collapse
what's the CSC of your phone? you should try the one newer vesion of 4.3 cause if it's an older firmware it refused flash
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.
Hello. Today I installed on my notes 3 SM-N9005 lollipop 5.0 version Poland but I found them a few problems: the first is that the vibration of the keyboard does not work. I found two of the slowdowns in the task manager. Now if I want to return to kitkat I can do fleshando firmware via Odin? ??
+1
I asked the same question with no accurate answer, i found a thread on how to downgrade from leaked ver. Of lolipop and not the official one and i won't risk trying this method, what I'm asking for is it possible to downgrade to official kitkat using odin specially that i have ticked update bootloader button when i flashed official Lolipop.
Will this work or we are risking our mobiles for a brick?
Appreciate if someone answered us with a proven record.
Regards,
however I have seen videos on youtube that have made the downgrade from 4.4.2 to 4.3 fleshando only the firmaware dacendo and then wipe data / cache. I think the same procedure also applies to switch lollipop kitkat.
It's safe to downgrade using odin. I did it myself from the leaked and the official release (both of them with the bootloader updated). In case odin complains about size just check my last posts and use the PIT file I provided.
Sent from my SM-N9005
Hi,
I have downgraded from the Polish Lollipop without using a PIT file - successfully. You will need to carry out a data wipe and factory reset, but it worked fine.
I couldn't... flashing ENC2 with Odin gave me size error, flashing with PIT solved that, but my IMEI and Baseband were gone. I gave up at that point, flashed Lolipop again and am back to normal now.
azidhaka said:
I couldn't... flashing ENC2 with Odin gave me size error, flashing with PIT solved that, but my IMEI and Baseband were gone. I gave up at that point, flashed Lolipop again and am back to normal now.
Click to expand...
Click to collapse
it just happens to me .... it would be nice to someone who really knows solve this problem make a tutorial on how to return to kk
Download N9005XXUGNK2 from sammobile and flash with odin, after the flash complete do a factory reset via recovery or your phone wont boot and will be stucked in samsung logo