Hi guys,
I'm having a serious problem here.
I searched for the solution on the internet, but I didn't find anything useful...
I need to factory reset my Samsung Galaxy Note 3 (SM-N9005) because of some issues (all of a sudden phone just switch to "kernel panic" mode, and then I have to reboot it by removing battery).
I cannot factory reset it !!!
I tried this:
- Settings -> General -> Backup and Reset -> Factory data reset
* after this the phone restarts and says "Recovery Booting..." and hangs on this
- Then I removed the battery and tried rebooting the phone, but it stil hung on "Recovery booting..." (I didn't hold Home + Vol. Up + Power; just Power)
- Then I removed the battery, pressed Vol. Down + Home + Power, and after the warning showed up I clicked Vol down (for cancel the custum OS installation) and then the phone reboots normally and I still have all my files
- Same thing happens if I turn off the phone and hold Vol. Up + Home + Power
- Same thing happens if I enter "su + Enter" and then "reboot recovery" into Android terminal emulator
- I even tried factory reset via dial codes, but this doesn't seem to work out (nothing happens)... Codes: *#7780#, *2767*3855#, #*#7780#*#, *2767*2878#
I have Jelly Bean 4.3
The phone was rooted via KingoApp
Kies says this: "Current firmware version: PDA:MHL / PHONE:MHK / CSC:MHL (BTU)"
I cannot go to "Firmware upgrade and initialization" on Kies, because it throws an error "'SM-N9005' does not support initializing."
I'm using stock ROM.
Phone is rooted.
I don't have CWM recovery (just a stock recovery that came with phone).
I even followed steps explained here: http://www.youtube.com/watch?v=Uud0UK4thAI
This is how the thing looks on my phone (hangs on "Recovery Booting..." for 10 minutes): http://i.imgur.com/KzE3cST.jpg
Can anybody help me? How can I factory reset my note 3?
Odin? Or some other PC software...?
Tell me if you need more info...
Thanks in advance!
--
thetox2
thetox2 said:
...
I'm using stock ROM.
Phone is rooted.
I don't have CWM recovery (just a stock recovery that came with phone).
I even followed steps explained here: http://www.youtube.com/watch?v=Uud0UK4thAI
This is how the thing looks on my phone (hangs on "Recovery Booting..." for 10 minutes): http://i.imgur.com/KzE3cST.jpg
...
Click to expand...
Click to collapse
You were probably left with an invalid recovery from the kingo root - you probably need to write again in Odin the same stock full firmware that you currently have.
Stock rom
Hey!
Thank you for your reply!
Hmmmm... probably... I don't remember, but I think my rooting process didn't go smoothly, so I'll definetely flash it.
Just few more questions...
- Where can I obtain official stock rom (Jelly bean not KitKat)?
- Will my KNOX get triggered (i didn't trigger it by rooting)?
- Can you recommend me a good tutorial on how to flash Note 3? I don't want to mess it up, and there are a lots of tutorials ond XDA...
Thanks in advance?
thetox2 said:
Hey!
Thank you for your reply!
Hmmmm... probably... I don't remember, but I think my rooting process didn't go smoothly, so I'll definetely flash it.
Just few more questions...
- Where can I obtain official stock rom (Jelly bean not KitKat)?
- Will my KNOX get triggered (i didn't trigger it by rooting)?
- Can you recommend me a good tutorial on how to flash Note 3? I don't want to mess it up, and there are a lots of tutorials ond XDA...
Thanks in advance?
Click to expand...
Click to collapse
Stock rom for n9005 for jb is hard to find. U can google. There's always a site for wad u r looking for.
Knox won't be triggered if u flash ori firmware by odin, if ur knox still 0x0.
U can use odin pc to flash. Just put the tar on the ap/pda. And don't click repartition if u never flash with pit file.
Connect ur phone in download mode, make sure reactivation lock is off (I m not sure abt this, coz mine I always off it), wait till ur odin recognize the com port. Click start.
Quite a lot tutor in here and on google, all are the same. Nothing different.
Sent from N9005 Assassins v2
thetox2 said:
Hey!
Thank you for your reply!
Hmmmm... probably... I don't remember, but I think my rooting process didn't go smoothly, so I'll definetely flash it.
Just few more questions...
- Where can I obtain official stock rom (Jelly bean not KitKat)?
- Will my KNOX get triggered (i didn't trigger it by rooting)?
- Can you recommend me a good tutorial on how to flash Note 3? I don't want to mess it up, and there are a lots of tutorials ond XDA...
Thanks in advance?
Click to expand...
Click to collapse
If you quote the message to which you are replying that user will get notified and will be able to answer you back, if not it will only be a matter of luck.
To get YOUR official stock rom you need to search a site like
http://www.sammobile.com/firmwares/1/?model=SM-N9005&pcode=NEE#firmware
(replace in the last drop-down NEE with the country from where YOUR N9005 comes, eventually with the correct provider if it is coming from a specific carrier).
If you will use the exact same version of firmware that you currently had it should not trigger knox, however knox can be triggered when you try to downgrade or for certain phones when you write a firmware from the wrong country.
If you are not familiar with Odin search around for a tutorial on it, there are even video tutorials. Also if you are on a firmware BEFORE 4.3 MJ3 you should look into the threads on Universal Root De La Vega - IMHO a huge lot better than kingo for rooting.
xclub_101 said:
If you quote the message to which you are replying that user will get notified and will be able to answer you back, if not it will only be a matter of luck.
To get YOUR official stock rom you need to search a site like
http://www.sammobile.com/firmwares/1/?model=SM-N9005&pcode=NEE#firmware
(replace in the last drop-down NEE with the country from where YOUR N9005 comes, eventually with the correct provider if it is coming from a specific carrier).
If you will use the exact same version of firmware that you currently had it should not trigger knox, however knox can be triggered when you try to downgrade or for certain phones when you write a firmware from the wrong country.
If you are not familiar with Odin search around for a tutorial on it, there are even video tutorials. Also if you are on a firmware BEFORE 4.3 MJ3 you should look into the threads on Universal Root De La Vega - IMHO a huge lot better than kingo for rooting.
Click to expand...
Click to collapse
Thank you very much for the tip, for links and for your help!
I actually don't know where my phone came from xD It was a gift. Since I'm from Croatia and the phone was unlocked by default I assume the firmware N9005XXUBMJ1 will do the job. In my settings it says that Baseband version is N9005XXBUMHK but I can't find from wthich country is this (on the link you gave me is an option tu search for ROMs by PDA and other criteria, not just by model/country).
Anyways... Thank you so much!
antique_sonic said:
Stock rom for n9005 for jb is hard to find.
Knox won't be triggered if u flash ori firmware by odin, if ur knox still 0x0.
Sent from N9005 Assassins v2
Click to expand...
Click to collapse
Well... xclub_101 found the ROM and I found a bunch of stock ROMs here: http://samsung-updates.com/device/?id=SM-N9005
KNOX is still 0x0.
P.s. I just noticed that you're using Asassins ROM... It is based on KitKat. Do you have any issues with it regarding third party accessories (SPen, SCover, and all that Note3-ish stuff)?
And since I'm flashing... Can you recommend me a good custom ROM?
I found those, but I don't know which one to pick (I don't like bugs and the stock ROM was OK for me):
http://forum.xda-developers.com/showthread.php?t=2701444
http://www.droidviews.com/best-custom-roms-for-galaxy-note-3-sm-n9005/
http://forum.xda-developers.com/showthread.php?t=2470441
Thanks in advance
thetox2 said:
Well... xclub_101 found the ROM and I found a bunch of stock ROMs here: http://samsung-updates.com/device/?id=SM-N9005
KNOX is still 0x0.
P.s. I just noticed that you're using Asassins ROM... It is based on KitKat. Do you have any issues with it regarding third party accessories (SPen, SCover, and all that Note3-ish stuff)?
Click to expand...
Click to collapse
Yes I m using it now. I always change rom base on my mood. Xnote, crash, echoe, assassin, and my own.
Assassin so far I use got no problem for the past few days after installation. Only problem is I cannot remove 1 bloatware, chaton. No matter how I remove it, it still runs as a service.
thetox2 said:
And since I'm flashing... Can you recommend me a good custom ROM?
I found those, but I don't know which one to pick (I don't like bugs and the stock ROM was OK for me):
http://forum.xda-developers.com/showthread.php?t=2701444
http://www.droidviews.com/best-custom-roms-for-galaxy-note-3-sm-n9005/
http://forum.xda-developers.com/showthread.php?t=2470441
Thanks in advance
Click to expand...
Click to collapse
I no idea which one is the best. Just try it. No harm. But just take note, flashing custom rom will trigger ur knox.
And to know good battery based on ur usage, u have to try it for at least 3 full battery cycle, in my opinion.
Sent from N9005 Assassins v2
Stock recovery has also got wipe data/factory reset.Have u tried that?
Sent from my SM-N900 using XDA Premium 4 mobile app
thetox2 said:
Thank you very much for the tip, for links and for your help!
I actually don't know where my phone came from xD It was a gift. Since I'm from Croatia and the phone was unlocked by default I assume the firmware N9005XXUBMJ1 will do the job. In my settings it says that Baseband version is N9005XXBUMHK but I can't find from wthich country is this (on the link you gave me is an option tu search for ROMs by PDA and other criteria, not just by model/country).
Anyways... Thank you so much!
...
Click to expand...
Click to collapse
N9005XXBUMHK is more likely N9005XXUBMHK - see those threads:
http://forum.xda-developers.com/showthread.php?t=2474430
http://forum.xda-developers.com/showthread.php?t=2671149
If the original CSC was BTU and that was the original/test firmware for first generation of Note 3 devices I would rather suggest using BTU again, at a level around MI7 - that one can still be rooted with knox 0 in a very safe way using Universal Root De La Vega (as long as at the first boot you disable both normal updates and security updates).
xclub_101 said:
N9005XXBUMHK is more likely N9005XXUBMHK
Click to expand...
Click to collapse
Well, both BU and UB cannot be found on Firmware check on your link... :S
RISHI RAJ said:
Stock recovery has also got wipe data/factory reset.Have u tried that?
Click to expand...
Click to collapse
The problem is in my recovery. I cannot boot into recovery (probably recovery image is corrupted).
antique_sonic said:
Yes I m using it now. I always change rom base on my mood. Xnote, crash, echoe, assassin, and my own.
Assassin so far I use got no problem for the past few days after installation. Only problem is I cannot remove 1 bloatware, chaton. No matter how I remove it, it still runs as a service.
I no idea which one is the best. Just try it. No harm. But just take note, flashing custom rom will trigger ur knox.
And to know good battery based on ur usage, u have to try it for at least 3 full battery cycle, in my opinion.
Sent from N9005 Assassins v2
Click to expand...
Click to collapse
I'll probably go with the stock ROM for now. But eventually I'll switch to a custom ROM
Thanks guys!
HELP!!!!
HELP!!!
I downloaded a ROM.
I used Odin v3.07 to flash my phone.
I did EVERYTHING according the instrucrtions. Odin and my phone are saying that system.img.ext4 is wrong.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA7_N9005CROENA2_N9005XXUENA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> FAIL! (Ext4)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
I'm searching for the solution on these forums, but NOTHING seems to help. My phone is ruined
http://www.sammobile.com/forum/showthread.php?t=18352
http://forum.xda-developers.com/showthread.php?t=2662373
http://forum.gsmhosting.com/vbb/f777/samsung-note-3-flashing-error-n9005-1769257/
Can ANYBODY help me???
Bad download ? Did you check md5 ?
Sent from my N9005
help
Dejan Sathanas said:
Bad download ? Did you check md5 ?
Sent from my N9005
Click to expand...
Click to collapse
How to check md5?
I downloaded 3 ROMs -> 2 JellyBean ROMs (Same roms from different sources) and one KitKat ROM.
Can you help me?
There should be a md5 number from where you downloaded the rom. If so, check it with a md5 checker.
Are you on JB or KK ?
Sent from my N9005
Dejan Sathanas said:
There should be a md5 number from where you downloaded the rom. If so, check it with a md5 checker.
Are you on JB or KK ?
Sent from my N9005
Click to expand...
Click to collapse
I downloaded from here: http://www.sammobile.com/firmwares/3/?download=20392
I don't see MD5 hash anywhere.
I wanted to check it using this tuorial: http://forum.xda-developers.com/showthread.php?t=1135620, but no luck...
I was on JB, but currently I'm on nothing...
It says you should dl Odin 3.09, but you flashed with .07. It shouldn't really matter, but it's worth a try.
Did none of the 3 roms work ?
Sent from my N9005
---------- Post added at 09:47 PM ---------- Previous post was at 09:44 PM ----------
And if you tried to flash the KK rom, your bootloader might have been updated, so there's no going back to JB.
Sent from my N9005
No luck
Dejan Sathanas said:
It says you should dl Odin 3.09, but you flashed with .07. It shouldn't really matter, but it's worth a try.
Did none of the 3 roms work ?
Sent from my N9005
Click to expand...
Click to collapse
No. None of them worked!
I tried with Odin 3.09.
I also checked the Re-Partition tick and placed PIT file, like this guy on this post: http://forum.xda-developers.com/showpost.php?p=50642419&postcount=2 and on this post: http://forum.gsmhosting.com/vbb/f777/samsung-note-3-flashing-error-n9005-1769257/
Now it is saying:
Code:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Dejan Sathanas said:
---------- Post added at 09:47 PM ---------- Previous post was at 09:44 PM ----------
And if you tried to flash the KK rom, your bootloader might have been updated, so there's no going back to JB.
Sent from my N9005
Click to expand...
Click to collapse
Yeah... it did update. When I try flashing KK it does the same error as before:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA7_N9005CROENA2_N9005XXUENA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> FAIL! (Ext4)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also, the phone says: "Invalid ext4 image" or something like that...
I always gets stuck on hidden.img.ext4. What is that anyway?!?!
OK, so I flashed the device with KK FW: http://www.sammobile.com/firmwares/3/?download=27080
And I use .PIT files mentioned in the links above.
I flashed it with Odin v3.09
After flashing it got stuck on Samsung logo. I pulled out the battery and went into Recovery (it works now ) and performed factory reset and cache clear.
After that first boot was a bit slower.
And now the phone is up and running.
And here is the message output from Odin
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
Thank all of you VERY much!
Edited
Related
Hi there....
i rooted my Note 3 LTE SM-N9005 and had it flashed with bobcat rom 4.4. then i had dropped my phone and having some issues with screen. Now i need to flash it with custom rom. I hope I've done everything as per instructions to odin the phone using the default stock rom N9005XXUDMJ7_N9005TMNDMK1_N9005XXUDMJ7_HOME.tar (Bought the phone from Dubai, UAE; my friend's phone is with the same firmware which was bought in the very same outlet)
But when i try to unroot it, everything goes good till finally the left upper box turns red and says "FAIL!" following is the progress i do get during unroot process.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMJ7_N9005TMNDMK1_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> modem.bin
<ID:0/006> cache.img.ext4
<ID:0/006> hidden.img.ext4
<ID:0/006> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
I don't have an idea on what should have gone wrong here. Tried not less than 10times using different Odin versions too, but still the result was same.
Guys, Please give me hand to get my phone back to life. I cannot boot my phone now. another custom rom in my internal memory but cannot boot into recovery either. What should i do? is there any other way to unroot/unbrick my precious (for me) mobile.?
Thanks in advance for all your time and effort put to save my ass.
Am not sure but i think you get this error because you are trying to downgrade from 4.4.2 to 4.3 that not working anymore on samsung at least for the mean time.
Go to sammobile and download the official kitkat (poland) then flash it via Odin
Sent from my SM-N9005 using Tapatalk
Dahdoul said:
Am not sure but i think you get this error because you are trying to downgrade from 4.4.2 to 4.3 that not working anymore on samsung at least for the mean time.
Go to sammobile and download the official kitkat (poland) then flash it via Odin
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Thanks a lot for the instruction bro... going to download it... and will give the feedback when i try it...
thanks again.
mhrdeena said:
Thanks a lot for the instruction bro... going to download it... and will give the feedback when i try it...
thanks again.
Click to expand...
Click to collapse
No problem ? and make sure you download the unbranded firmware (Poland XEO)
check this thread
http://forum.xda-developers.com/showthread.php?t=2610444
Sent from my SM-N9005 using Tapatalk
delega cattrit
Dahdoul said:
No problem ? and make sure you download the unbranded firmware (Poland XEO)
check this thread
http://forum.xda-developers.com/showthread.php?t=2610444
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
yeah,I've selected the same. but seems like terrafile.co, the file hosting website is under maintenance right now. I will have to wait till they resume back to normal.
mhrdeena said:
yeah,I've selected the same. but seems like terrafile.co, the file hosting website is under maintenance right now. I will have to wait till they resume back to normal.
Click to expand...
Click to collapse
MEGA Link for you
Hey everyone - long time reader first time poster.
I'm having an issue with my SM-N9005. I had rooted it, and was running OmegaRom V21 (i think). I am now trying to flash it back to stock 4.4.2 XSA firmware and am receiving a FAIL! message in Odin 3.07 after HIDDEN is displayed.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENE3_N9005XSAENE1_N9005XXUENE3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> modem.bin
<ID:0/006> cache.img.ext4
<ID:0/006> hidden.img.ext4
<ID:0/006> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
I have been able to successfully flash to the leaked Polish 4.4.2 firmware using ODIN 3.09 and extracted .pit file, but when i try and then reflash the STOCK XSA firmware it is showing FAILED! again...
Any suggestions?
Cheers
James
is the omega rom 4.4.4 or is it 4.4.2
Powerplayer1025 said:
is the omega rom 4.4.4 or is it 4.4.2
Click to expand...
Click to collapse
It was 4.4.2
hmm you might have a bad chord or you might need to run odin as admin or you might have a bad download
---------- Post added at 08:11 AM ---------- Previous post was at 08:09 AM ----------
did you try to turn your phone all the way off leave the phone off for 15 seconds then boot into download mode and flash it. or are you putting the file in the wrong spot
Powerplayer1025 said:
hmm you might have a bad chord or you might need to run odin as admin or you might have a bad download
Click to expand...
Click to collapse
i have tried all those things. i'm able to flash with the leaked Polish 4.4.2 firmware.. and have downloaded the firmware a few times, from SamMobile and other mirrors. The leaked Polish firmware is the only way i can get into the phone, otherwise it displays emergency firmware recovery messages, but isn't detected in Kies...
I'm really confused actually lol
try a different odin maybe sometimes that seems to help the problem. maybe even reboot the laptop
iamjamoo said:
Hey everyone - long time reader first time poster.
I'm having an issue with my SM-N9005. I had rooted it, and was running OmegaRom V21 (i think). I am now trying to flash it back to stock 4.4.2 XSA firmware and am receiving a FAIL! message in Odin 3.07 after HIDDEN is displayed.
...
I have been able to successfully flash to the leaked Polish 4.4.2 firmware using ODIN 3.09 and extracted .pit file, but when i try and then reflash the STOCK XSA firmware it is showing FAILED! again...
Any suggestions?
Cheers
James
Click to expand...
Click to collapse
I have a feeling your partitioning scheme is indeed different - what specific model was the N9005 originally? You might need to first install the oldest 4.4.2 you find for that original model.
xclub_101 said:
I have a feeling your partitioning scheme is indeed different - what specific model was the N9005 originally? You might need to first install the oldest 4.4.2 you find for that original model.
Click to expand...
Click to collapse
hmm it was an Australian model, i thought it would be an issue with partitioning so i tried to use the pit file from the polish firmware and flash the xsa firmware but that also failed..
so the oldest 4.4.2 you think? I'll give that a go
'm on the Sprint Galaxy S4 SPH-L720. I've spent about 10 hours on this - reading and following posts and trying different flashes with no luck. I was on the Pac Man Rom (with CW MOD 11): pac_jflte-dev-20140831.zip (I believe in my phone it showed KitKat 4.4.4) . I was having issues with reception, getting voicemails, and battery, so I wanted to revert to Stock Rom (I think I tried mk2), and ran into problems. I've been trying to flash NAE (and use the NAE pit file) with different versions of Odin, different USB jacks, etc but with no luck. The error messages I get in Odin are:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
And my phone says in red:
Start {224,1440}
Secure Check Fail: PIT
SV rev. check fail : fused : 5 Binary : 4
Click to expand...
Click to collapse
The NAE i'm flashing is: L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5
I really appreciate any help anyone can offer.
You aren't flashing the correct file. Did you upgrade to the latest OTA NG2 update recently?
I think you was flash wrong combination of flashable.. Maybe..
Again. Check your flashable..
daniel4653 said:
You aren't flashing the correct file. Did you upgrade to the latest OTA NG2 update recently?
Click to expand...
Click to collapse
Thank you for your replies. Daniel4653, I didn't do any OTA updates (I think because the phone was rooted, I couldn't, no?). What is the correct file to flash? I've downloaded a bunch:
SPR-L720VPUEMK2-20131212171424
SPR-L720VPUAMF9-20130626162512
SPR-L720VPUFNAE-20140224205519
L720VPUAMDC_L720SPTAMDC_SPR
I had used an older version of Philz Recovery (philz_touch_6.07.9-i9300.tar.md5) and when I tried a newer version (philz_touch_6.15.6-jflte.tar.md5), I was able to boot into Clockwork Mod. From there I was able to install a custom ROM again. Phew. Also, I know understand that a phone that has Knox installed (0x1) won't work with Odin anymore. See http://forum.xda-developers.com/showthread.php?t=2447832&page=7
After getting Cyanogenmod up and running, I realized that I have no sound, am not able to make calls and the battery drains very quickly. I found a link with someone that has a similar issue (but not on sprint) - I can't post links yet but if you google "No Sound After Updating And New Instalation Of Cm11" it's the first article.
It seems like it's an issue with my modem or boot loader (sorry I'm a noob and doing my best to understand everything - spent all day trying to get my phone working )? I tried flashing the MK2 modem only MK2-ModemOnly.tar.md5 with no luck. I get an error in ODIN.
I know it's a problem people are having with cyanogenmod. Could I install another rom like negalite wonder rom (ng2)?
Thank you.
garbage914 said:
After getting Cyanogenmod up and running, I realized that I have no sound, am not able to make calls and the battery drains very quickly. I found a link with someone that has a similar issue (but not on sprint) - I can't post links yet but if you google "No Sound After Updating And New Instalation Of Cm11" it's the first article.
It seems like it's an issue with my modem or boot loader (sorry I'm a noob and doing my best to understand everything - spent all day trying to get my phone working )? I tried flashing the MK2 modem only MK2-ModemOnly.tar.md5 with no luck. I get an error in ODIN.
I know it's a problem people are having with cyanogenmod. Could I install another rom like negalite wonder rom (ng2)?
Thank you.
Click to expand...
Click to collapse
If you can mount everything and wipe all in cwm (follow the steps) you can flashing another roms..
But make sure you can doing mount or etc..
[Problem] upgrading Note 3 N9005 to lollipop 5.0 FAIL using Odin 3.10
I've recently bought Galaxy Note 3 LTE which was on android 4.2.2 and I wanted to upgrade it to Lollipop 5.
So I followed the instructions for upgrading using Odin and everything went fine until hidden.img.ext4 where it fails.
here is the log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBOF1_N9005EVRGBOF1_N9005XXUGBOD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1006)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> FAIL! (Size)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
also worth mentioning, I forgot to enable USB Debugging because the tutorial page didn't mention it.
please help me go through this, I don't want to lose my new Note 3.
PIT file!!!
TrueMan500 said:
I've recently bought Galaxy Note 3 LTE which was on android 4.2.2 and I wanted to upgrade it to Lollipop 5.
So I followed the instructions for upgrading using Odin and everything went fine until hidden.img.ext4 where it fails.
here is the log:
also worth mentioning, I forgot to enable USB Debugging because the tutorial page didn't mention it.
please help me go through this, I don't want to lose my new Note 3.
Click to expand...
Click to collapse
add the ROM in ODIN
and also click PIT and select file (download from below URL) and tick Re-Partition.
Now Flash
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Try using Odin 3.07, unchecked everything except auto reboot and f.reset time. Don't check partition if you don't have a pit file.
Did you download the firmware from sammobile.com?
Does the phone still boot?
nijom said:
add the ROM in ODIN
and also click PIT and select file (download from below URL) and tick Re-Partition.
Now Flash
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Click to expand...
Click to collapse
worked great thanks!
audit13 said:
Try using Odin 3.07, unchecked everything except auto reboot and f.reset time. Don't check partition if you don't have a pit file.
Did you download the firmware from sammobile.com?
Does the phone still boot?
Click to expand...
Click to collapse
thanks for the fast replay! I already tried nijom solution and worked fine!
Odin Fail (Size)
nijom said:
add the ROM in ODIN
and also click PIT and select file (download from below URL) and tick Re-Partition.
Now Flash
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Click to expand...
Click to collapse
Hi, tried to flash N9005XXSGBQA3 - GALAXY Note3 SM-N9005 NZC New Zealand through Odin, and got a fail (size) error on a rooted International N9005. You suggest needing a PIT file to flash alongside this one.
Noob question I suspect, but are these generic or firmware specific?
Any help gratefully received
I've completely bricked my Samsung Galaxy J5.
I've rooted my device with Odin using CF Autoroot. That went fine.
Then I went on and tried to install TWRP recovery with Odin. This went fine. Then I wanted to install CM 12.1. This ****ed up my phone. I forgot to enable developer options and OEM unlocking. Apparently this is something new since Android 5.1. NOT A SINGLE TUTORIAL MENTIONED THIS!!!
So back to stock firmware. It took 1 hour (!) and like 9000 ads (had to disable Adblock) to download the stock firmware. If you don't want to see adds and download full speed. Samsung must be run by a bunch of lomperds. Holy ****.
It finally downloaded and it seemed to work. Untill at the end:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> J500FNXXU1APC4_J500FNVFG1APC4_J500FNXXU1APC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> sec.dat
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Error on the phone:
Code:
Volume Size is too big 143368 < 489600
ODIN: Invalid ext4 image
This appears to be a partition problem. So I tried to repartition with a random pit file I found on the internet (I guess Samsung really wants to loose customers). I got the next error:
Code:
Secure check fail: pit
Now I'm stuck. I can only get into download mode. Maybe I need a proper pit file?
Solution: Buy a real phone with linux support. Burn this one.
If you can get into download mode the phone is redoversble, did you ever make a nandroid backup that you can flash with Odin?
Sent from my SM-N910V using Tapatalk
---------- Post added at 08:04 PM ---------- Previous post was at 08:03 PM ----------
(Recoverable)
Sent from my SM-N910V using Tapatalk
I had the same problem once. I don't remember much but what I did was :
Go into download mode by pressing volume down and power and home button.
Go into Odin and flash the latest version of the stock rom (go to sammobile website to download it).
Now reroot the phone using the latest chainfire root files(available on chainfire website).
Flash twrp 3.0.0 or any better version. Version 3 works best on my j500f.
Also if you are still getting the pit file error, it may be because of the corrupt tar file you are using in Odin. So download the latest rom from sammobile. If you still get the error, try rebooting your computer to see if it helps.
Goodluck!
Sent from my SM-J500F using XDA-Developers mobile app
Thanks for your replies.
Go into Odin and flash the latest version of the stock rom (go to sammobile website to download it).
Click to expand...
Click to collapse
That is what I did. It gives me next error:
Code:
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
Rebooting didn't fix the problem.
I think it is related to the fact that there is something wrong with the partitioning. If only Samsung would provide the right files to fix this...
I should have known that this process would fail since I had to install WINDOWS in order to work with Odin. Wtf?
I've rooted several HTC phones before without any problem. This is complete nonsense.
Samsung made too many mistakes imho. I'm not gonna spend another afternoon figuring out that I cannot fix my phone. I'm gonna send this phone where it came from and I'll probably buy a phone that has proper support. Maybe a Nexus.
Samsung never again.
TheOnlyRealChosenOne said:
Thanks for your replies.
That is what I did. It gives me next error:
Code:
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
Rebooting didn't fix the problem.
I think it is related to the fact that there is something wrong with the partitioning. If only Samsung would provide the right files to fix this...
I should have known that this process would fail since I had to install WINDOWS in order to work with Odin. Wtf?
I've rooted several HTC phones before without any problem. This is complete nonsense.
Samsung made too many mistakes imho. I'm not gonna spend another afternoon figuring out that I cannot fix my phone. I'm gonna send this phone where it came from and I'll probably buy a phone that has proper support. Maybe a Nexus.
Samsung never again.
Click to expand...
Click to collapse
Did you buy a new phone? If no, i know the solution
H3XabyT3LV said:
Did you buy a new phone? If no, i know the solution
Click to expand...
Click to collapse
Yes. Bought the Nexus 5X.
But maybe it's a good idea the post the solution anyway. Some users might be helped by it.
TheOnlyRealChosenOne said:
Yes. Bought the Nexus 5X.
But maybe it's a good idea the post the solution anyway. Some users might be helped by it.
Click to expand...
Click to collapse
Refund it and follow my steps -
If you remember ur model number, its chance to unbrick it
1. Go to sammobile
2. Go to search ROMs
3. Type in ur phone model
4. A list should appear? Right?
5. Search the country where you live - if its not in the list choose the country that is close to yours.
6. Download & flash with odin
Sent from my SM-J500FN using XDA-Developers mobile app
H3XabyT3LV said:
Refund it and follow my steps -
If you remember ur model number, its chance to unbrick it
1. Go to sammobile
2. Go to search ROMs
3. Type in ur phone model
4. A list should appear? Right?
5. Search the country where you live - if its not in the list choose the country that is close to yours.
6. Download & flash with odin
Sent from my SM-J500FN using XDA-Developers mobile app
Click to expand...
Click to collapse
U even read brah?
So back to stock firmware. It took 1 hour (!) and like 9000 ads (had to disable Adblock) to download the stock firmware. If you don't want to see adds and download full speed. Samsung must be run by a bunch of lomperds. Holy ****.
It finally downloaded and it seemed to work. Untill at the end:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> J500FNXXU1APC4_J500FNVFG1APC4_J500FNXXU1APC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> hyp.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> sec.dat
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Error on the phone:
Code:
Volume Size is too big 143368 < 489600
ODIN: Invalid ext4 image
This appears to be a partition problem. So I tried to repartition with a random pit file I found on the internet (I guess Samsung really wants to loose customers). I got the next error:
Code:
Secure check fail: pit
Click to expand...
Click to collapse
TheOnlyRealChosenOne said:
U even read brah?
Click to expand...
Click to collapse
Dude, that is the fix for that hidden.ex4 stuff.
I had this problem myself, and I fixed it by this method. Not trying to be rude here.
Sent from my SM-J500FN using XDA-Developers mobile app
The fix will be easy , after flashing the whole firmware it will only fail once the whole process is done 99%
so the fix will be flash custom recovery (TWRP/CWM) since you already said yourself that you are going to root your phone.
then now you can now boot your phone.
FIX:Flash custom recovery after Flash failed firmware
Another will be : Recovery firmware using Smart Switch (Google it yourself)
Another will beIT partition for your Device
Thanks me for my own experimentation (Y)
can body slove this problem
alikashan said:
can body slove this problem
Click to expand...
Click to collapse
Did you even read the comments? Even the title of the thread says solved. Put on your glasses and start reading
garylawwd said:
Did you even read the comments? Even the title of the thread says solved. Put on your glasses and start reading
Click to expand...
Click to collapse
Nothing of this crap is working! I istalled twrp and rebooted to it! Deleted all except that one witch has IMEI info and then flashed via odin! Now? Phone works! I'm kinda dissapointed in Samsung! They are like Chinese broken goods from Craigslist! (No racism here)