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
HI Guys,
I flashed the Lollipop 5.0.1 CHN firmware and rooted the phone to install the Google apps, then when the India Firmware came i tried to flash that via Odin, it failed. and bricked the phone, could get into download mode but all firmware i've tried fails.
i tried numerous thing to a point where i can now only get CWM- recovery or TWRP open recovery on the phone, and then it allows me to get back into download mode with swver A3, but Odin still fails almost immediately.
help would be much appreciated
regards
Brendan
Vergil069 said:
HI Guys,
I flashed the Lollipop 5.0.1 CHN firmware and rooted the phone to install the Google apps, then when the India Firmware came i tried to flash that via Odin, it failed. and bricked the phone, could get into download mode but all firmware i've tried fails.
i tried numerous thing to a point where i can now only get CWM- recovery or TWRP open recovery on the phone, and then it allows me to get back into download mode with swver A3, but Odin still fails almost immediately.
help would be much appreciated
regards
Brendan
Click to expand...
Click to collapse
So this means you can into Download Mode which is quite a good thing.
Now what you do is download the particular Kies for S4 from the OEM site and connect it when your phone is in Download or that wierd Yellow Triangle with the sign to connect to PC, and then kies will try to save ur phone.
came accross this http://forum.xda-developers.com/showthread.php?t=2269941
Odin completed success fully, but now phone just hangs just after it askes to select the OS language ps. i used the lollipop india rom with the pit in the mentioned post
install a custom recovery using odin like philztouch and do a full wipe to install new rom
will i need a new PIT file?, after full wipe just Odin and lollipop 5.0.1 as normal?
Hello all,
Today I updated a custom ROM on my rooted Phone (android 7) . In the aroma installer i select no root. After a good restart i though i root my Phone true Odin. I was thinking it went all good till it was stuck on te Galaxy s7 edge black screen. I couldnt do nothing. After that i was thinking to flash to stock. Every time i try to flash true Odin it give me fail.
Please help me.
Best regards Sidi
Hi there, I have same issue, have s7 edge sm-G935F stuck at logo. I downloaded 2 different firmware from z3x box(shell) and if keep failing when using odin (latest) and also getting error when using Samsung tool.Also I can't get in the phone menu to check the baseband..can only get model from download model.any advice to this?
Same issue as well on my sm-g985v Verizon variant
Flashed an update to work out minor lagging bugs and soft bricked my S7. Can access bootloader and recovery. Beyond that, the phone gets there but with black screen and it is sputtering off and on. Tried reflashing stock firmware with odin, and its not taking. Running into a permission error while trying to write the image. Anyone here have any ideas?
sidi adam said:
Hello all,
Today I updated a custom ROM on my rooted Phone (android 7) . In the aroma installer i select no root. After a good restart i though i root my Phone true Odin. I was thinking it went all good till it was stuck on te Galaxy s7 edge black screen. I couldnt do nothing. After that i was thinking to flash to stock. Every time i try to flash true Odin it give me fail.
Please help me.
Best regards Sidi
Click to expand...
Click to collapse
Is this a 935F? Where did you download the orginal firmware from and what version of Odin u use?
When I root my phone I always use the steps from this thread.
http://forum.xda-developers.com/s7-e...0-0-0-t3334084
Have never run into issues.
Flash twrp trough Odin first, let the phone start
Boot into TWRP, format phone with the options you have to type YES, then install dm-verity force encryption disabler
Now restart TWRP
Then flash the Supersu file from the thread.
Now restart phone
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Feyaad said:
Hi there, I have same issue, have s7 edge sm-G935F stuck at logo. I downloaded 2 different firmware from z3x box(shell) and if keep failing when using odin (latest) and also getting error when using Samsung tool.Also I can't get in the phone menu to check the baseband..can only get model from download model.any advice to this?
Click to expand...
Click to collapse
Download orginal firmware fro sammobile, unpack and flash with Odin 3.12.3.
Download the firmware from your area, the one that comes with your phone.
Use the right regional code and everything when you download firmware.
Also, have you guys flashed the right bootloader and modem beforehand?
LyLu said:
Is this a 935F? Where did you download the orginal firmware from and what version of Odin u use?
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Download orginal firmware fro sammobile, unpack and flash with Odin 3.12.3.
Download the firmware from your area, the one that comes with your phone.
Use the right regional code and everything when you download firmware.
When I root my phone I always use the steps from this thread.
http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
Have never run into issues.
Flash twrp trough Odin first, let the phone start
Boot into TWRP, format phone with the options you have to type YES, then install dm-verity force encryption disabler
Now restart TWRP
Then flash the Supersu file from the thread.
Now restart phone
Click to expand...
Click to collapse
Hello,
Thanks for your message. I tried everything you said exept that i used odin 3.12.5
But still the black screen...
sidi adam said:
Hello,
Thanks for your message. I tried everything you said exept that i used odin 3.12.5
But still the black screen...
Click to expand...
Click to collapse
What rom you tried to flash?
Are you on the right bootloader and modem?
Well I have the Odin latest version already..but I can't know which is the correct baseband or county..only the model I know when it's in download mode..
sidi adam said:
Hello all,
Today I updated a custom ROM on my rooted Phone (android 7) . In the aroma installer i select no root. After a good restart i though i root my Phone true Odin. I was thinking it went all good till it was stuck on te Galaxy s7 edge black screen. I couldnt do nothing. After that i was thinking to flash to stock. Every time i try to flash true Odin it give me fail.
Please help me.
Best regards Sidi
Click to expand...
Click to collapse
So you flashed a beta firmware, the name of which you don't feel is necessary information.
OK. Shame I hate popcorn. How about INFORMATION instead?!
LyLu said:
Is this a 935F? Where did you download the orginal firmware from and what version of Odin u use?
When I root my phone I always use the steps from this thread.
http://forum.xda-developers.com/s7-e...0-0-0-t3334084
Have never run into issues.
Flash twrp trough Odin first, let the phone start
Boot into TWRP, format phone with the options you have to type YES, then install dm-verity force encryption disabler
Now restart TWRP
Then flash the Supersu file from the thread.
Now restart phone
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Download orginal firmware fro sammobile, unpack and flash with Odin 3.12.3.
Download the firmware from your area, the one that comes with your phone.
Use the right regional code and everything when you download firmware.
Also, have you guys flashed the right bootloader and modem beforehand?
Click to expand...
Click to collapse
It was my understanding it was already in the package. Questioning that one now. Where do i look for that? And thank you for responding back. Downloading your first suggestions as i type this...
I have downloaded two non branded firmware for the Netherlands from samdroid. I had unpacked the zip and flashed the files. For the csc selection I put the one named home csc
Moodruid said:
It was my understanding it was already in the package. Questioning that one now. Where do i look for that? And thank you for responding back. Downloading your first suggestions as i type this...
Click to expand...
Click to collapse
When downloading original firmware there should be 4 files when unzip.
1 for each of the options in Odin, without the last one named home.
Some of the custom roms comes with bootloader and modem, but NOT ALL.
Most times you have to flash the right bootloader and modem in Odin beforehand to get the phone to boot.
Im unsure of what has happened because I have never run into issues myself.
If you can not get the phone to boot with firmware from Sammobile and Odin flash I am out of options.
If I do experience a problem like this I would:
-install bootloader and modem according to the custom rom used. Try and flash these with odin more than ones, if not working.
-if no recovery, try flash recovery again
-try flash another custom rom then another custom rom
-return to stock firmware downloaded trough Sammobile
If none of these options work im out of things to do, sorry
The times I have experienced phone stuck on Samsung logo, it has been because of bootloader and/or modem.
Flashing the right ones have always fixed the problem.
That said, I have never experienced problems with returning to stock firmware trough Odin, maybe one time.
And this time my firmware download was corrupted.
---------- Post added at 06:13 AM ---------- Previous post was at 06:00 AM ----------
sidi adam said:
I have downloaded two non branded firmware for the Netherlands from samdroid. I had unpacked the zip and flashed the files. For the csc selection I put the one named home csc
Click to expand...
Click to collapse
This is wrong, you should use the file named only CSC.
Home_CSC, is to keep your setup on phone as is.
I also remember that you have to remove the meta data directory, and then repack firmware or the install will stop.
And this is also NOT a good option if you use another firmware than the original on phone.
Installing firmware with Odin, always use BL, AP, CP and CSC.
Try this and forget about the Home_CSC.
I don't have anymore info, sorry
Thank you very much. I will try it. I will let you know.
Gentlemen, my appreciations and thanks. Was able to finally get the stock firmware to grab. After more time disecting the problem i learned about and was able to uncover the maintenance boot screen. There it had the option to do usb debug . Once i hit that, next flash finished fully. It must of reser in the dev options after the initial root. Damn, i was sweating balls for a bit thinking i must of hard bricked it somehow. I will take it throufh the toot process later today glitch free i imagine. Thanks again for assisting,
Moodruid said:
Gentlemen, my appreciations and thanks. Was able to finally get the stock firmware to grab. After more time disecting the problem i learned about and was able to uncover the maintenance boot screen. There it had the option to do usb debug . Once i hit that, next flash finished fully. It must of reser in the dev options after the initial root. Damn, i was sweating balls for a bit thinking i must of hard bricked it somehow. I will take it throufh the toot process later today glitch free i imagine. Thanks again for assisting,
Click to expand...
Click to collapse
Usb debugging should always be turned ON when flashing..........!
Tis is like common knowledge in here.
Anyway glad things work
LyLu said:
Usb debugging should always be turned ON when flashing..........!
Tis is like common knowledge in here.
Anyway glad things work
Click to expand...
Click to collapse
How will you get to turn on USB debugging when the phone can only booth into download model?
Feyaad said:
How will you get to turn on USB debugging when the phone can only booth into download model?
Click to expand...
Click to collapse
Buy pressing and holding power and volume down key, until you get to the screen.
Same procedure as download mode, but without the big button
LyLu said:
Buy pressing and holding power and volume down key, until you get to the screen.
Same procedure as download mode, but without the big button
Click to expand...
Click to collapse
OK great..will try it..thank you
luly said:
Is this a 935F? Where did you download the orginal firmware from and what version of Odin u use?
When I root my phone I always use the steps from this thread.
http://forum.xda-developers.com/s7-e...0-0-0-t3334084
Have never run into issues.
Flash twrp trough Odin first, let the phone start
Boot into TWRP, format phone with the options you have to type YES, then install dm-verity force encryption disabler
Now restart TWRP
Then flash the Supersu file from the thread.
Now restart phone
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Download orginal firmware fro sammobile, unpack and flash with Odin 3.12.3.
Download the firmware from your area, the one that comes with your phone.
Use the right regional code and everything when you download firmware.
Also, have you guys flashed the right bootloader and modem beforehand?
Click to expand...
Click to collapse
Even this thread is old:
Thank you so much, bricked my phone unknowingly flashing custom recovery using a defektive usb port struggling to get it working again. This worked like a charm.
Don´t understand why the orthers did struggle with that method.
Hi,
I cant seem to find anything related directly to the S8 and not sure if all mobiles are the same..
I had Android 8 on my S8 and needed to downgrade to 7 to try something, I did that but after it completed I had a messy settings menu where parts were duplicated or showing the wrong sub-heading.
I've read on the forums about this and it says re-flash with CSC and AP to fix.
When I try to re-flash it gets stuck on "Set Partition" in Odin.
I read to fix this you need to enable the "re-partition" option in Odin, I have tried this and it still does not work.
I have also tried full flash or AP, CSC, BL and CP and it's still getting stuck.
Tried on two different PC's (just in case) - same result on both.
The phone still boots and works, but it feels like something is wrong.
Can someone advise on how to completely re-flash the phone? The videos I've watched so far don't seem to run into this issue.
Any help would be awesome
Update: Using odin 3.13 gives this error: <ID:0/005> Can't open the specified file. (Line: 1892)
I've tried it with SamFirm and Sammobile FW.
EDIT - Finally fixed it, flashed G950FXXU1AQDG to the handset, wiping and re-partitioning the phone, after setup an OTA update was pushed for 8.0.
In case anyone else has the same issue, I used Sammobile for the FW and Odin 3.12 to flash.
Yesterday I tried root my S8 (SM-G950FD) and I made the mistake of not allowing system modifications before flashing because I misinterpreted a guide. I flashed the no-verity zip and Magisk. The phone booted successfully and magisk was installed. Then I went to reboot into recovery to change some TWRP settings IE: Brightness. Then my phone said "Only officially released binaries are allowed to be flashed." That left me unable to boot my phone and also made it unable to boot into recovery. The only thing I can boot my phone into is download mode. I've tried flashing some stock roms that are 7.0 to remove the prenormal lock but they failed. I happened to make a TWRP backup before flashing but I can't use TWRP because of the official binary stuff. I'm wondering if I use the nand erase all option if that will let me flash the 7.0 stock roms then boot into TWRP and restore my backup or if they is way to convert the backup into something that Odin can flash. Does anybody know any confirmed methods to solve my problem?
Unbrick-me said:
Yesterday I tried root my S8 (SM-G950FD) and I made the mistake of not allowing system modifications before flashing because I misinterpreted a guide. I flashed the no-verity zip and Magisk. The phone booted successfully and magisk was installed. Then I went to reboot into recovery to change some TWRP settings IE: Brightness. Then my phone said "Only officially released binaries are allowed to be flashed." That left me unable to boot my phone and also made it unable to boot into recovery. The only thing I can boot my phone into is download mode. I've tried flashing some stock roms that are 7.0 to remove the prenormal lock but they failed. I happened to make a TWRP backup before flashing but I can't use TWRP because of the official binary stuff. I'm wondering if I use the nand erase all option if that will let me flash the 7.0 stock roms then boot into TWRP and restore my backup or if they is way to convert the backup into something that Odin can flash. Does anybody know any confirmed methods to solve my problem?
Click to expand...
Click to collapse
You will need to flash the same or higher version of Android to fix official binary error. Use default settings in Odin.
You cannot.flash earlier versions of Android if your bootloader is lower than what is on your phone ( 5th number from right of firmware name ). If in doubt flash the latest version.
Then I went to reboot
Click to expand...
Click to collapse
And i same problems "Only officially released binaries are allowed to be flashed"
---------- Post added at 10:31 PM ---------- Previous post was at 10:30 PM ----------
Then I went to reboot
Click to expand...
Click to collapse
And i same problems "Only officially released binaries are allowed to be flashed"
spawnlives said:
You will need to flash the same or higher version of Android to fix official binary error. Use default settings in Odin.
You cannot.flash earlier versions of Android if your bootloader is lower than what is on your phone ( 5th number from right of firmware name ). If in doubt flash the latest version.
Click to expand...
Click to collapse
Ok so in few minutes from now the rom will be finished downloading. When that is done what version of Odin should I use and what files should place in Odin. I know this may seem stupid to ask but I'm not going to let myself make anymore stupid decisions after not installing the rmm bypass.
Quick Update, the rom finished downloading. I wasn't able to flash it. It gave me the error that the Bootloader had: 4 and the binary had 3... I was able to flash cp by itself tho and that set the system status to samsung official but the binary status is still custom. That made it so my phone only booted into a "Update failed screen use smart switch" screen ( I've tried smart switch before it doesn't detect my device). I can still get it back into recovery and flash old cps to get it to turn off without bootlooping into the smart switch screen. I'm wondering if I flash csc to factory reset if that will help at all. Guys what do I do??
Excuse my language but I ****ING DID IT!!! I don't know this worked but I am going to roughly call my process. So flashing the stock rom initially failed. I flashed then CP which for some reason always works and then AP which began but failed. This set the binary text to "Samsung Official", system status was still ****ed as custom. So I restored the cp and ap(?) from the crgb oreo files posted here. Then I flashed cp that passed, then csc which passed and then tried AP. After some time... It passed. The phone rebooted. The official binary bull**** was gone from the bootscreen and the phone booted into recovery. It installed some sys update stuff up to 30$ then erased some things which took awhile. Then the phone booted into initial setup and I now have ACCESS TO MY PHONE AGAIN!!!
For anyone interested in what FW I flashed PM me.