Hello All,
I have a Samsung Note 3 9005 LTE International Edition. It was working fine till I decided to move from 4.3 to 4.4.2.
This is what I did to upgrade my phone.
1. Flash bootloader (as this is needed to move to 4.4.2)
2. Flash latest CWM as per instructions (n9005-cwm-recovery-6.0.4.6-kitkat(0113))
3. Flash a custom rom, started wtih Sweet ROM (after doing full wipe)
After booting I noticed that my phone was repeatedly getting stuck, especially when opening the dailer... If anyone would call me they would hear the phone ringing but on my phone the screen would be black! A few minutes later I would get a missed call notification... Trying to unlock the phone by swiping would randomly cause the phone to hang! In short, the phone had become unusable!
Then I spent many hours on this wonderful forum to see if I had something wrong. I read somewhere that it is advised to flash a Stock 4.4.2 ROM before attemping to flash a custom ROM. Therefore I tried the following
a. Downloaded and flashed a stock 4.4.2 ROM via Odin (N9005XXUENA6_N9005OXXENA5_XEO)
Tested the phone and same issue was persisting. So I did the additional steps:
b. Flash CF Autoroot (CF-Auto-Root-hlte-hltexx-smn9005)
c. Flash latest CWM as per instructions
Test and again same issue. So did the following
d. Wipe data / factory reset / wipe dalvik etc. etc.
e. Flash Custom ROM
I have tried flashing every ROM on this forum for the N9005 but have faced the same issue.
I really really need some help. My phone is unusable. Technically it "works" but hangs again and again and again. I did read on google that 4.4.2 had dialer issues but this is going beyond that. I don't know what to do.
Any help would be greatly appreciated.
Regards,
- Harris
Is it by any chance a Nordic region phone? (NEE) --- If so, I believe @nex7er has solved this issue with NEE region -- Not sure where he has posted the results, but he's the guy you need find.
EDIT: -- Grab yourself a PIT file for just in case -- then in CWM, format your data in /system then reflash your ROM again. - Your PIT file will be handy if you need to redo your partitions due to a corruption somewhere along the line.
radicalisto said:
Is it by any chance a Nordic region phone? (NEE) --- If so, I believe @nex7er has solved this issue with NEE region -- Not sure where he has posted the results, but he's the guy you need find.
EDIT: -- Grab yourself a PIT file for just in case -- then in CWM, format your data in /system then reflash your ROM again. - Your PIT file will be handy if you need to redo your partitions due to a corruption somewhere along the line.
Click to expand...
Click to collapse
It isn't NEE! So that hope is gone
I have tried formatting /system as well but nothing!
iqsoft said:
It isn't NEE! So that hope is gone
I have tried formatting /system as well but nothing!
Click to expand...
Click to collapse
Last thing I can think of is a total wipe out, ODIN tick NAND erase, then with your PIT file, reflash back to complete stock...I have never done this, so you will need to read up to be 100% sure on the method, but if that doesn't fix it, then I am all out of ideas
radicalisto said:
Last thing I can think of is a total wipe out, ODIN tick NAND erase, then with your PIT file, reflash back to complete stock...I have never done this, so you will need to read up to be 100% sure on the method, but if that doesn't fix it, then I am all out of ideas
Click to expand...
Click to collapse
A noob question, where do I get the PIT from? And any guide on how to do NAND erase as this sounds risky
I know that feeling...
Unfortunatly the samething happened to me, tried every flash file and method on this forum but nothing resolved my issue.
Did you also notice that your phone wouldnt make a sound?
Maybe also that the latest 4.4.2. baseband wouldnt stick when you flashed it?
This seems to be becoming more and more common, I would seriosluy recommend not touching 4.4.2 until its official on your carrier.
You could always wait for your carrier to release the update officially and try again, mine is back in the box! :crying:
Maybe we can collate the information into a warning thread?
iqsoft said:
A noob question, where do I get the PIT from? And any guide on how to do NAND erase as this sounds risky
Click to expand...
Click to collapse
You'll have to have a look around, normally I'd find the link and post but I Hard Bricked myself this morning so trying to fix it
JimmyVD said:
I know that feeling...
Unfortunatly the samething happened to me, tried every flash file and method on this forum but nothing resolved my issue.
Did you also notice that your phone wouldnt make a sound?
Maybe also that the latest 4.4.2. baseband wouldnt stick when you flashed it?
This seems to be becoming more and more common, I would seriosluy recommend not touching 4.4.2 until its official on your carrier.
You could always wait for your carrier to release the update officially and try again, mine is back in the box! :crying:
Maybe we can collate the information into a warning thread?
Click to expand...
Click to collapse
Hmm, you had no joy at all then after everything?
---------------- This KK update and the Note 3 are becoming a bit of a ballache for sure...
JimmyVD said:
I know that feeling...
Unfortunatly the samething happened to me, tried every flash file and method on this forum but nothing resolved my issue.
Did you also notice that your phone wouldnt make a sound?
Maybe also that the latest 4.4.2. baseband wouldnt stick when you flashed it?
This seems to be becoming more and more common, I would seriosluy recommend not touching 4.4.2 until its official on your carrier.
You could always wait for your carrier to release the update officially and try again, mine is back in the box! :crying:
Maybe we can collate the information into a warning thread?
Click to expand...
Click to collapse
Yes that is correct, no sound at all! And the baseband would be reset every time I flashed!
This is a total disaster, now I have to get another phone till there is a fix for this!!!
- Harris
iqsoft said:
Yes that is correct, no sound at all! And the baseband would be reset every time I flashed!
This is a total disaster, now I have to get another phone till there is a fix for this!!!
- Harris
Click to expand...
Click to collapse
You could always try the PIT file from the leaked OXX firmware, re-partition/nand erase via ODIN etc see if it works... That is literally last chance saloon though I am afraid.. Well until Official region FW for you comes out..
I don't know about you guys but I'm just as interested in finding out why this happened to me when the flash was successful for so many other people as what I can do to fix it.
I think I'll swerve the nand erase option as it's already pretty much ruined, and I don't really fancy a 600 quid paper weight.
I'll keep an eye on this thread, if we find a resolution we should make an announcement.
JimmyVD said:
I don't know about you guys but I'm just as interested in finding out why this happened to me when the flash was successful for so many other people as what I can do to fix it.
I think I'll swerve the nand erase option as it's already pretty much ruined, and I don't really fancy a 600 quid paper weight.
I'll keep an eye on this thread, if we find a resolution we should make an announcement.
Click to expand...
Click to collapse
Have you nand erased already? how did it go? what did you do for exactly? PM me please.
When you flashed the stock KITKAT and added the file to AP did you tick "Phone Bootloader Update" ? and check your imei if its empty
radicalisto said:
You'll have to have a look around, normally I'd find the link and post but I Hard Bricked myself this morning so trying to fix it
Click to expand...
Click to collapse
Hardbrick eh?
Try the sd card boot.
http://forum.xda-developers.com/showthread.php?t=2531224
This btw
hit 'thanks' if i helped you
SM-N9005 0x0 X-Note7 ML2
XDA Developers 4 premium app
flashare 4.4.2 in caso di errori
flashare pit file
erase nand
bl
ap
cp
csc
con N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX
in caso di loop e blocco scritta samsung flashare solo cp e csc
il mio e andato ok pero dispiace non poter flashare al momento cm11
meawww said:
When you flashed the stock KITKAT and added the file to AP did you tick "Phone Bootloader Update" ? and check your imei if its empty
Click to expand...
Click to collapse
Yup did that, phone has an IMEI, infact it does technicall "recieve" calls, though the screen goes blank and nothing is displayed! So the radio is working in theory!!!
same problem here after stock 4.4.2 followed by custom kitkat-rom
-no sound
-hangs during unlock procedure
-hangs during all modifications that are linked to audio (i.e. speaker on/off settings / audio players / ringtone-settings etc...)
---------- Post added at 08:05 PM ---------- Previous post was at 07:46 PM ----------
ok gentlemen,
i just tried flashing stock 4.4.2 the 3rd time and now all is fine again.
sound problem is gone and no hangs anymore.
i am not sure what is different, but i try to describe what might have went wrong before
-during odin flash i recognised that phone stuck because it was connedcted to old usb 1.1port. So i unplugged (i thought it was hardbicked anyway, so nothing to loose)
-without restart phone i plugged into correct usb2 hub and startet over with odin-flash of stock 4.4.2
-after odin flash i did not unplug phone during reset, but was waiting for compete reboot after procedure
et voila, it works
here is the odin-log. i have marked the part where i unplugged the phone...
<ID:0/021> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N9005XXUENA6_340325_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/021> Odin v.3 engine (ID:21)..
<ID:0/021> File analysis..
<ID:0/021> SetupConnection..
<ID:0/021> Initialzation..
<ID:0/021> Set PIT file..
<ID:0/021> DO NOT TURN OFF TARGET!!
<ID:0/021> Get PIT for mapping..
<ID:0/021> Firmware update start..
<ID:0/021> SingleDownload.
<ID:0/021> aboot.mbn
<ID:0/021> __XmitData_Write
<ID:0/021> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/021> Removed!!
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/022> Added!!
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Set PIT file..
<ID:0/022> DO NOT TURN OFF TARGET!!
<ID:0/022> Get PIT for mapping..
<ID:0/022> Firmware update start..
<ID:0/022> SingleDownload.
<ID:0/022> aboot.mbn
<ID:0/022> NAND Write Start!!
<ID:0/022> sbl1.mbn
<ID:0/022> rpm.mbn
<ID:0/022> tz.mbn
<ID:0/022> sdi.mbn
<ID:0/022> NON-HLOS.bin
<ID:0/022> boot.img
<ID:0/022> recovery.img
<ID:0/022> system.img.ext4
<ID:0/022> userdata.img.ext4
<ID:0/022> persist.img.ext4
<ID:0/022> modem.bin
<ID:0/022> Transmission Complete..
<ID:0/022> Now Writing.. Please wait about 2 minutes
<ID:0/022> Receive Response from boot-loader
<ID:0/022> cache.img.ext4
<ID:0/022> hidden.img.ext4
<ID:0/022> RQT_CLOSE !!
<ID:0/022> RES OK !!
<ID:0/022> Removed!!
<ID:0/022> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/020> Added!!
I know this is more nonsense, thant rocket-science. But it did the job unexpecetly good.
So, maybe this helps somebody to overcome the problem.
Same problem for me. Being excited about new trends really pays off, especially on our Note 3. I guess, we'll have to wait for a fix on this. Hopefully, a solution will come soon.
---------- Post added at 03:31 AM ---------- Previous post was at 03:07 AM ----------
fredofuchs said:
same problem here after stock 4.4.2 followed by custom kitkat-rom
-no sound
-hangs during unlock procedure
-hangs during all modifications that are linked to audio (i.e. speaker on/off settings / audio players / ringtone-settings etc...)
---------- Post added at 08:05 PM ---------- Previous post was at 07:46 PM ----------
ok gentlemen,
i just tried flashing stock 4.4.2 the 3rd time and now all is fine again.
sound problem is gone and no hangs anymore.
i am not sure what is different, but i try to describe what might have went wrong before
-during odin flash i recognised that phone stuck because it was connedcted to old usb 1.1port. So i unplugged (i thought it was hardbicked anyway, so nothing to loose)
-without restart phone i plugged into correct usb2 hub and startet over with odin-flash of stock 4.4.2
-after odin flash i did not unplug phone during reset, but was waiting for compete reboot after procedure
et voila, it works
here is the odin-log. i have marked the part where i unplugged the phone...
<ID:0/021> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N9005XXUENA6_340325_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/021> Odin v.3 engine (ID:21)..
<ID:0/021> File analysis..
<ID:0/021> SetupConnection..
<ID:0/021> Initialzation..
<ID:0/021> Set PIT file..
<ID:0/021> DO NOT TURN OFF TARGET!!
<ID:0/021> Get PIT for mapping..
<ID:0/021> Firmware update start..
<ID:0/021> SingleDownload.
<ID:0/021> aboot.mbn
<ID:0/021> __XmitData_Write
<ID:0/021> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/021> Removed!!
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/022> Added!!
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Set PIT file..
<ID:0/022> DO NOT TURN OFF TARGET!!
<ID:0/022> Get PIT for mapping..
<ID:0/022> Firmware update start..
<ID:0/022> SingleDownload.
<ID:0/022> aboot.mbn
<ID:0/022> NAND Write Start!!
<ID:0/022> sbl1.mbn
<ID:0/022> rpm.mbn
<ID:0/022> tz.mbn
<ID:0/022> sdi.mbn
<ID:0/022> NON-HLOS.bin
<ID:0/022> boot.img
<ID:0/022> recovery.img
<ID:0/022> system.img.ext4
<ID:0/022> userdata.img.ext4
<ID:0/022> persist.img.ext4
<ID:0/022> modem.bin
<ID:0/022> Transmission Complete..
<ID:0/022> Now Writing.. Please wait about 2 minutes
<ID:0/022> Receive Response from boot-loader
<ID:0/022> cache.img.ext4
<ID:0/022> hidden.img.ext4
<ID:0/022> RQT_CLOSE !!
<ID:0/022> RES OK !!
<ID:0/022> Removed!!
<ID:0/022> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/020> Added!!
I know this is more nonsense, thant rocket-science. But it did the job unexpecetly good.
So, maybe this helps somebody to overcome the problem.
Click to expand...
Click to collapse
I tried that but Odin seems to always Fail. Did you close your Odin after unplugging your USB? What's the model number of your unit anyway? Hopefully I can have a workaround like that too. *cross fingers*
i did not close odin after unplug the device. just unplugged and plugged-in to another usb-port. then hit "start" in odin.
I am using SM N9005 (DBT)
--> make sure " phone bootloader update" is ticked in odin.
#update #2
just flashed echoe-rom and all keeps running smoothly. no problems anymore.
So at least this is a good sign that the mentioned issue is not a deadly issue
Fixed
Hi All,
My phone is working perfectly now. I have identified the issue:
a. Do NOT ever flash only the bootloader. Flash the stock 4.4.2 ROM instead
b. If you happen to flash the bootloader, then you will need to ensure that you flash the kernel that comes with the stock 4.4.2 ROM. The baseband should be N9005XXUENA2 and Kernel 3.4.0-340325.
its all fixed at my end. Flashing the stock 4.4.2 has fixed it.
Thanks to all those who helped.
- Harris
fredofuchs said:
same problem here after stock 4.4.2 followed by custom kitkat-rom
-no sound
-hangs during unlock procedure
-hangs during all modifications that are linked to audio (i.e. speaker on/off settings / audio players / ringtone-settings etc...)
Click to expand...
Click to collapse
Exact same issue here. Problem with anything to do with sound after flashing a custom rom after flashing 4.4 booatloader
Please let me know if a fix is found as Im stuck with an 800 dollar paperweight and using an iphone 4 !!
Related
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
'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..
Hello. I tried to get back to official stock rom so I flashed my Galaxy S4 I-9505 with I9505XXUFNB8_I9505BTUFNB3_BTU and a pit file. the flashing starts but it suddenly stops and now my phone is bricked. PLEASE HELP!!! how do i get back to my official stock rom now?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNB8_I9505BTUFNB3_I9505XXUFNB8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
A little reading goes a long way
http://forum.xda-developers.com/showthread.php?t=2265477
DSA said:
A little reading goes a long way
http://forum.xda-developers.com/showthread.php?t=2265477
Click to expand...
Click to collapse
I have followed this guide, any idea where might have I gone wrong?Because I have absolutely no clue I've flashed my device before but never had such issues.
ashekin.nahid said:
I have followed this guide, any idea where might have I gone wrong?Because I have absolutely no clue I've flashed my device before but never had such issues.
Click to expand...
Click to collapse
This happend coz you are trying to downgrade your device. Try to flash the latest firmware (only the firmware coz you don't need .pit file atm) for your device and you will see how it works ok
I have a similar problem, having tried with both I9505XXUHOJ2_I9505YXYHOK1_I9505XXUHOJ2_HOME.tar.md5 and I9505XXUHOJ2_I9505BTUHOJ1_I9505XXUHOJ2_HOME.tar.md5 (and not using a PIT file). I have tried multiple times, but I always get to the Samsung boot animation (white SAMSUNG, with a few animated blue stars moving away and fading - repeat) but it never gets any further - stuck. Any ideas please?
fjuniper said:
I have a similar problem, having tried with both I9505XXUHOJ2_I9505YXYHOK1_I9505XXUHOJ2_HOME.tar.md5 and I9505XXUHOJ2_I9505BTUHOJ1_I9505XXUHOJ2_HOME.tar.md5 (and not using a PIT file). I have tried multiple times, but I always get to the Samsung boot animation (white SAMSUNG, with a few animated blue stars moving away and fading - repeat) but it never gets any further - stuck. Any ideas please?
Click to expand...
Click to collapse
Did you wipe everything before flashing?
And are you sure it's the right rom for your phone? There was somebody who thought his phone was an I9500 (because that's what was written on the sticker under the battery) but it was actually an I9505.
GDReaper said:
Did you wipe everything before flashing?
And are you sure it's the right rom for your phone? There was somebody who thought his phone was an I9500 (because that's what was written on the sticker under the battery) but it was actually an I9505.
Click to expand...
Click to collapse
Yes, I wiped in TWRP before flashing the file in ODIN - ART / System / Data / Internal Storage / Cache. Not sure whether you mean that I should have, or shouldn't have!
Yes, it is a UK S4 i9505.
fjuniper said:
Yes, I wiped in TWRP before flashing the file in ODIN - ART / System / Data / Internal Storage / Cache. Not sure whether you mean that I should have, or shouldn't have!
Yes, it is a UK S4 i9505.
Click to expand...
Click to collapse
Why is there an md5 extension to the tar files? Firmwares should only have tar as extension as far as I know.
GDReaper said:
Why is there an md5 extension to the tar files? Firmwares should only have tar as extension as far as I know.
Click to expand...
Click to collapse
That is what was in the zip files from http://www.sammobile.com/firmwares/database/GT-I9505/
Exactly as I pasted in the earlier post. Both files of about 2.5GB. ODIN seemed fine with it and took them in the AP slot (ODIN 3.1.0.7). The Open filter includes *.md5, *.tar, *.smd etc.
I've recently updated to 5.1.1 thru OTA update. Running fine for a few days but now phone keeps random rebooting and frequent crashes or hangs. Suspecting it may have been due to firmware.
Had did a factory reset and wiping of cache partition but issue persists.
So over here I'm trying to downgrade my firmware. But odin shows this:
<ID:0/003> Added!!
<ID:0/003> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MK2_Full_Odin_Tar.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on my phone, it shows:
[1]eMMC write fail: ABOOT
Please advise me what should I do? Really appreciate it because the frequent crashes are really frustrating. Thanks in advance!
jengkhit said:
I've recently updated to 5.1.1 thru OTA update. Running fine for a few days but now phone keeps random rebooting and frequent crashes or hangs. Suspecting it may have been due to firmware.
Had did a factory reset and wiping of cache partition but issue persists.
So over here I'm trying to downgrade my firmware. But odin shows this:
<ID:0/003> Added!!
<ID:0/003> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MK2_Full_Odin_Tar.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on my phone, it shows:
[1]eMMC write fail: ABOOT
Please advise me what should I do? Really appreciate it because the frequent crashes are really frustrating. Thanks in advance!
Click to expand...
Click to collapse
if your phone is upgraded COJ5, you can not to downgrade of it. there is no way ,I am trying almost two weeks .and you can find two titles about this
mudur1998 said:
if your phone is upgraded COJ5, you can not to downgrade of it. there is no way ,I am trying almost two weeks .and you can find two titles about this
Click to expand...
Click to collapse
Then there is no other way to work around? The constant crashing and freezing is driving me nuts.
Download the official rom from samfirmware and reflash it via odin with option Nand Erase Alll
GrippingSphere said:
Download the official rom from samfirmware and reflash it via odin with option Nand Erase Alll
Click to expand...
Click to collapse
Have you ever done this or heard of anyone doing it successfully? Everything I've read over the past 5 years is that will make a phone FUBAR'd.
dicksteele said:
Have you ever done this or heard of anyone doing it successfully? Everything I've read over the past 5 years is that will make a phone FUBAR'd.
Click to expand...
Click to collapse
I've done it multiple times on my phone. Flashing with Nand Erase All option is just erasing everything on your internal sd card, so all your previously installed programs and scripts that may conflict with the new rom will be erased.
It will not affect your EFS or your IMEI.
You just have to save all your important files to your external sd card first.
GrippingSphere said:
I've done it multiple times on my phone. Flashing with Nand Erase All option is just erasing everything on your internal sd card, so all your previously installed programs and scripts that may conflict with the new rom will be erased.
It will not affect your EFS or your IMEI.
You just have to save all your important files to your external sd card first.
Click to expand...
Click to collapse
Interesting..... Have you done it with the COJ5 bootloader? And flashed to a 5.0.1 bootloader?
I understand what you are saying.
I've read some more about it this afternoon. Only a few articles suggested doing it. But they suggesting backing up /efs.
Not sure how /efs survives a internal sdcard erase.
I would think all partitions would be torched.
GrippingSphere said:
I've done it multiple times on my phone. Flashing with Nand Erase All option is just erasing everything on your internal sd card, so all your previously installed programs and scripts that may conflict with the new rom will be erased.
It will not affect your EFS or your IMEI.
You just have to save all your important files to your external sd card first.
Click to expand...
Click to collapse
yes,before COJ5 it could be done,did you try this method(I have tried several times and several stock roms from sammobile)after COJ5,if you did not ,I strongly advice you ,do not try it ,if your phone is still on any other firmware except COJ5
I'm sorry for the confusion. My original post is actually in response to jengkhit's post when he mentioned that he is experiencing frequent crashes after updating via OTA. I recommend flashing the official rom via odin but the same 5.1.1 rom or later, not to a lower rom version like 5.0.1. I know that one cannot flash to a lower rom version once upgraded to the latest 5.1.1.
GrippingSphere said:
I'm sorry for the confusion. My original post is actually in response to jengkhit's post when he mentioned that he is experiencing frequent crashes after updating via OTA. I recommend flashing the official rom via odin but the same 5.1.1 rom or later, not to a lower rom version like 5.0.1. I know that one cannot flash to a lower rom version once upgraded to the latest 5.1.1.
Click to expand...
Click to collapse
Hey GrippingSphere, thanks for your reply. I was busy over the weekend so no time to see this thread. I'm still facing the same issues. Now my phone often can't boot up. When it boots, often goes to Odin mode with mmc_read failed. Then I have to do soft reset multiple times before getting it to boot. I figured out the only way to prevent hanging/rebooting is to continuously run music/video player. Is this software or hardware issue?
Anyway, I tried to flash same version firmware to overwrite but also encountered the same problem in Odin. What might be the issue? And now my binary is custom although firmware is official.
My warranty already expired so I'm really praying I can fix this if it is software related.
Thanks again, anyone, who can help or encountered similar issues.
I can only think of reflashing your official rom then factory reset as the possible solutions to your phone problem. If these doesn't work then it might be a hardware problem already.
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)