Hello,
I have an unsuccessful firmware update.
First flashed the last stock rom, cf-autoroot. After it I try to flash the CWM, and this is the end,
Now there is no boot loader, no recovery. I see the "Firmware update encountered an issue...".
The knox is 0x1, Writeprotect enabled.
The only thing is working on the phone is the download mode, but every attempt to flash in Odin fails. (aboot.mng..Fail)
I tried to flash another bootloaders, repartition with pit file, but not works...
Done it on other PC, usb ports...
Now I know what was the wrong with the installation, but I need a solution for this situation.
Please, help me...
You will have to flash through ODIN Kit Kat. You cant come back to 4.3 or 4.2.2 if ya flashed android 4.4.2 and u updated the bootloader. Select one android 4.4.2 firmware in SamMobile for you and update ur phone :highfive:
Thanks for the reply...
The last firmware I flashed was 4.3, and I cannot reflash it.
But I will try a Kit Kat, which one is good for me? I have an unlocked phone and my country (Hungary) does not have it yet.
Can I flash it with knox 0x1?
Thanks for the advice, the phone is working now....
The whole story:
- the phone had 4.3 custom ROM before.
- I flashed the new version with 4.4.2: new recovery, modem and ROM.
- From here I had no sound. I tried to flash everything 3 times, an no sound.
- I searched for this, threre were many good advice, I tried some and the phone not booted.
- Downloaded the latest Samsung firmware (I9505XXUEMKF_I9505OXXEMK3_I9505XXUEMKF), flashed and no sound.
- extracted the modem.bin, flashed, and flashad the ROM again, sound is good, I was very happy.
- CF-autoroot, I saw it was working
- Flashed the CWM recovery, Fail in Odin and...no boot, no recovery, only download mode.
- Flashing the original downloaded firmware (I9505XXUEMKF_I9505OXXEMK3_I9505XXUEMKF) is failed. I don't understand, it is not downgrade...
- Flashing a new Kit Kat (I9505XXUFNB9_I9505EURFNB1_I9505XXUFNB9) was successful.
How can I use a custom ROM again?
I am afraid, if I make an error, cannot flash again the same, I have to wait a new one?
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)
Phone: Samsung Galaxy S4 ATT I337UCUAMDL
Model Number in settings on 4.4 ROM = GT-I9505G
As the title says, I installed dandroid's newest 4.4 ROM from WICKED v5 4.2.2 and lost root. So I attempted to update my CWM Recovery from Odus 1x to the newest using Odin which failed do to write protected I suppose all though others says that doesnt effect their installs.
Where I'm at:
Cannot boot into recovery, says booting recovery the just reboots and enters Dandroid's ROM w/o root.
I'm now lost and have been reading the forums for hours. Currently downloading STOCK Samsung firmware for my device I337UCUAMDL_I337ATTAMDL_ATT.zip
CASUAL failed.
What do I need to do to get back to WORKING custom recovery w/ rooted dandriod 4.4 kitkat rom. Should I use Odin and flash stock rom then motochopper to root and try to reinstall working CWM recovery?
Please advise best course of action. My phone had been working properly with every ROM I tried before update to 4.4 ROM and attempted CWM recovery update (thinking that would fix my root issue). Thanks all!
If you have a nandroid, and I hope you do, just restore that in your custom recovery. If you don't, then you're going to have to return to stock with odin
Tried motochopper on the phone as it sits and it fails as well.
I have a stock backup but the problem is I no longer have access to any recovery. Guess I'm just gonna have to flash the stock firmware with Odin when its finished downloading and start over.
Just finished Odin flash back to samsung factory firmware. Phone stuck at att world logo on bootup, still can't access recovery. Any ideas?
GSXRspike said:
Just finished Odin flash back to samsung factory firmware. Phone stuck at att world logo on bootup, still can't access recovery. Any ideas?
Click to expand...
Click to collapse
If you flashed Odin successfully you can get into recovery.
Finally got into recovery it rebooted 3 times but just holding the req. buttons finally got me in.
Back on factory firmware and rooted w/ cwm recovery all back in place properly worrking.
I would like to use the Dandroid 4.4 ROM with this device. When I install am I going to lose root again and if so, how I do I get it back on this device since the model in the settings is going to change from I337 to I9505G after installing this ROM?
Figured it all out last night, re-flashed Dandroid's latest ROM which still caused me to loose root, then flashed SuperSU 1.51 instead of 1.80 and regained root. All is right in the world now.
GSXRspike said:
Figured it all out last night, re-flashed Dandroid's latest ROM which still caused me to loose root, then flashed SuperSU 1.51 instead of 1.80 and regained root. All is right in the world now.
Click to expand...
Click to collapse
Hey, if you dont mind me asking where did you get the 1.51 zip to flash? I'm having a similar issues with same ROM where i lost root but have recovery access.
Thanks
Update: Found the file. Flashed it. Root is back. Have you let market update it automatically? If so did you lose root afterwords?
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
Hello there. So, this is my actual situation: I have a galaxy s4 on stock Lollipop. Due a few issues, I decided to try to downgrade to kitkat I flashed via Odin a stock kk fw, but unluckyly I Haven't considered Knox bootloader, and now the phone stucks in bootloop. I tried to enter recovery, but it doesn't even work.
Is there any way to save it? Actually, I'm downloading stock lollipop firmware to flash it from Odin. Could it work ?
Thanks everyone will give help
Yes, flash the latest stock ROM in Odin to get the phone back to stock.