I'll start with some background. Currently I'm in China studying for three weeks, but before I left home I encrypted the internal storage on my phone. This worked fine for a week, however two days ago the encryption password stopped working. I had installed a dual-sim adapter so I could use two sim-cards, however this somehow also changed the encryption password (possibly because Kaspersky Internet Security was installed).
So I tried numerous passwords and eventually the automatic factory reset kicked in. I thought this would be fine as there was no important data on the phone (it had been backed up and reset before I left for China), but because I had TWRP installed the recovery could not mount the encrypted data partition in order to wipe it. This meant that the attempts remaining counter for the encryption password entered negative numbers. I loaded the latest recovery and tried again to no avail, so decided to try and load the latest stock firmware (VAU-I9506XXUDOL1-20160222141114) using Odin.
Odin also failed because of a size mismatch between the new and existing hidden.img.ext4 partitions, which I imagine is the encrypted data partition, and now I'm left with a message saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I've tried Kies several times but it fails to recognise the phone and gets stuck saying "Connecting...".
Here's the log from Odin;
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<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> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<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)
The phone itself says;
Volume size is too big 24576 < 512000
ODIN : Invalid ext4 image
I tried Odin numerous times but always get the same result. I then searched for a way to solve the size mismatch and discovered that a TIP file may be what I'm looking for, however after scouring the internet I can't find any for the i9506. Would a TIP file solve my problem? Does anyone know how I could go about finding one for VAU-I9506XXUDOL1-20160222141114? I've also thought about removing hidden.img.ext4 from the archive and trying to flash again, but I'm afraid of doing even more damage.
Thanks in advance for any help/advice offered, I'm at my wits end with this and I'm really hoping I haven't bricked my phone.
The problems is that you are looking for some TIP file, but you actually need a PIT file. It needs to be specific to the internal storage size.
GDReaper said:
The problems is that you are looking for some TIP file, but you actually need a PIT file. It needs to be specific to the internal storage size.
Click to expand...
Click to collapse
Thanks GDReaper, does the file also need to be specific to the firmware or will any i9506 PIT file work if the internal storage size is correct? So far I can find quite a few for the i9500/i9505 but none for the i9506
Zyaz said:
Thanks GDReaper, does the file also need to be specific to the firmware or will any i9506 PIT file work if the internal storage size is correct? So far I can find quite a few for the i9500/i9505 but none for the i9506
Click to expand...
Click to collapse
Don't think it needs to be firmware specific.
The PIT file can be extracted from the phones
Here you can find how to do it. But you need someone with an I9506 with the same internal storage size as yours.
You could even extract it from yours, probably, but it requires the phone to be operational.
Related
Allo,
I finally found the ROM for Galaxy S4 SGH-I337M and the CF auto root.
ROM file : I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_HOME.tar.md5 (Virgin mobile, lollipop 5.0.1)
CF Root : CF-Auto-Root-jfltecan-jfltevl-sghi337m.tar.md5
The problem is that ODIN transfers the image to the phone but fails at the very last bytes. It says added, fails, removed.
Odin 3.09 is used, autorebbot and F.Reset are ticked. Nothing else.
What am I doing wrong???? What is required to have a sucessful upload?
Need help, phone is bricked.
I just flashed this file with odin 3.04, no problems except I had to flash it twice to change baseband, and my carrier is fido, so I had to change csc. I have seen recommendations here to use that version of Odin with this particular model, never failed me. Also, I use my original Samsung cable for Odin flashes, seen posts that cheap cables make a difference. and make sure you have all the correct drivers installed. I can't help other then that, sorry, limited knowledge myself, but the search button is your friend, all kinds of answers on the forums.
pcote_xda said:
Allo,
I finally found the ROM for Galaxy S4 SGH-I337M and the CF auto root.
ROM file : I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_HOME.tar.md5 (Virgin mobile, lollipop 5.0.1)
CF Root : CF-Auto-Root-jfltecan-jfltevl-sghi337m.tar.md5
The problem is that ODIN transfers the image to the phone but fails at the very last bytes. It says added, fails, removed.
Odin 3.09 is used, autorebbot and F.Reset are ticked. Nothing else.
What am I doing wrong???? What is required to have a sucessful upload?
Need help, phone is bricked.
Click to expand...
Click to collapse
99% of all Odin errors are solved by the following:
- Different usb port
- Different cable
Allo,
I followed the instructions provided by JesterDoobie and I took note of the advise provided by Lennyz1988.
It works my friends, thank you for your support. At the end, I had to use a Samsung genuine cable to reach a complete and successful upload of the ROM.
With a third party cable, it would transfer but at the end (99% completed) it would indicate in red FAILS and the ODIN messages were:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<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> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> modem.bin
<ID:0/003> NON-HLOS.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
With the procedure and Samsung cable = home run.
Help!
I attempted to follow through with this: http://www.cultofandroid.com/53963/save-galaxy-note-3-failed-kitkat-update-odin-tip/
But its failing currently:
UDC Start
ERASING USERDATA PARTITION..
ODIN : invalid ext4 image
Click to expand...
Click to collapse
I've tried 3 different images (I'm NZ based), tried 2 different pit files also. I don't know what do to do next, since it keeps failing the same error message.
mp3geek said:
Help!
I attempted to follow through with this: http://www.cultofandroid.com/53963/save-galaxy-note-3-failed-kitkat-update-odin-tip/
But its failing currently:
I've tried 3 different images (I'm NZ based), tried 2 different pit files also. I don't know what do to do next, since it keeps failing the same error message.
Click to expand...
Click to collapse
Are you using a branded phone (vodafone) or unlocked one? Coz, i think, you are flashing wrong firmware for your device.
Its an unlocked N9005 (LTE)
As far as I know the ROMs which are for 16 gigs devices won't get flashed on 32 gigs devices and vice versa, so you probably need to find a ROM which will match your device's size.
This is a 32G device
The Roms I've attempted (and failed) to flash:
N9005XXUEND3_N9005VNZENC1_N9005XXUENC2_HOME.tar.md5
N9005XXUGNG1_N9005VNZGNG1_N9005XXUGNG1_HOME.tar.md5
N9005XXUGNG1_N9005XSAGNG1_N9005XXUGNG1_HOME.tar.md5
N9005XXUEND3_N9005NZCENF2_N9005XXUENC2_HOME.tar.md5
N9005XXUGNK1_N9005VAUGNK1_N9005XXUGNK1_HOME.tar.md5
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1100)..
<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)
Is there a ROM (any) that I can I can flash via ODIN which includes a bootloader such as CMW? If I install CMW by itself, it'll be successful. But It'll go through a boot loop.
Maybe a screwed up the bootloader of the SM-9005?
Try a newer base, those are really old ones! Try OF3! Can't say of which country, as I don't know which are for which sized devices! I am not sure at all, but I think ROMs for UK devices are pretty popular, so I guess those might work.
You can simply flash the deodexed OF3 which comes as a zip package from here, http://forum.xda-developers.com/galaxy-note-3/development/rom-qs-n9005-lp-t3037655
It's basically a stock ROM with few added features and deodexed. If you don't want deodexed then you can try flashing a pre made ROM from alexandar's topic, it's same as stock ROM with even less features from the previously mentioned one. I am suggesting you these because it's better to flash a ROM which will work straight after download rather than trial and error method of sammobile ROMs.
I don't think you can flash "QS-N9005-LP-FINAL-OH3.zip" in ODIN, doesn't show up
mp3geek said:
Help!
I attempted to follow through with this: http://www.cultofandroid.com/53963/save-galaxy-note-3-failed-kitkat-update-odin-tip/
But its failing currently:
I've tried 3 different images (I'm NZ based), tried 2 different pit files also. I don't know what do to do next, since it keeps failing the same error message.
Click to expand...
Click to collapse
Rename .tar.md5 rom in .zip and extract all images from it.Delete hidden.img file then compress everything with forum.xda-developers.com/showthread.php?t=2446269 then flash every tar separatly.
mp3geek said:
I don't think you can flash "QS-N9005-LP-FINAL-OH3.zip" in ODIN, doesn't show up
Click to expand...
Click to collapse
Course you can't! You need to flash it from a custom recovery, TWRP for example.
Argh still not wanting to do it I thought grabbing N9005ZSUGOH3_N9005OZSGOH3_N9005ZSUGOH3_HOME.tar.md5 (matching the other 2 versions) would maybe help
Code:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1100)..
<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> rpm.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> sdi.mbn
<ID:0/005> tz.mbn
<ID:0/005> aboot.mbn
<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> cache.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)
Should I touch any additonal ODIN options such as Phone EFS Clear, or Phone Bootloader Update, or Nand Erase All?
You don't need to touch anything. I always flash only the PDA (AP), that's enough! Don't know what's going on here, but I am pretty sure it is because of the size issue.
Actually I got a new error message "Volume Size is too big 614400 < 712704
(Note this a 32GB) What should I do to get space? I happy to wipe the internal storage at this stage, just not sure how
Both up volume and down volume (with power/menu give me ODIN modes currently), a bit slight different
Down volume goes into download mode (Odin mode), and up volume goes to recovery mode. Both are quite different actually.
If you are willing to do a wipe then do it properly. Flash the custom recovery first, TWRP. Then go to Advanced Wipe and wipe everything (except external SD), but BEWARE, this will wipe EVERYTHING. You won't even have any ROM installed. So until you plan to flash a ROM basically you will have a brick. Do take backup of your needed stuffs before wiping, photos, musics etc. in your PC and use Titanium for apps' backup if you will so.
Then try to flash through Odin again (have you found same country's firmware matching your device? I mean I have a device which was assembled in UAE, so all the UAE ROMs work, so check that). If Odin still fails, then have that zip ROM (OF3) downloaded beforehand. I am repeating once again, if you do what I said above it will erase everything from your phone, so please be informed about that before proceeding further.
I flashed twrp-2.8.7.0-hlte-4.4.img.tar, which according to ODIN, it was successful. but when I reboot (volume up/menu/power). Says "Recovery is booting.." but shows nothing.
Okay, got in into it.
Advanced Wipe? Tick everything in TWM? and Format data?
Thanks heaps for the support
Weird! Take the battery out for 10 seconds, re-insert, then press Volume Up and Power only simultaneously (No need to press Menu), it should boot right into TWRP.
Sent from my SM-N9005 using Tapatalk
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)
Hi,
Recently my phone autoupdated to marshmalow, and since then it keeps freezing and crashing. I read somewhere that the final fix to this is to reflash the firmware, so I tried and since then odin gives me an error message and the phone wont start.
I am quite new to all this, but I followed instructions from many different youtube tutorials and other online tutorials. ODIN keeps giving me a write error.
I am using different versions of odin, different usb ports and even different cables with the same end result. ODIN flash ends with error.
My note 4 has reactivation lock off, and never been rooted before. It is a UK N910F model and usually on Three mobile.
I really hope someone can help as I have struggled with this for past 2-3 days with no luck.
Here is the details from odin.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910FXXU1DPE1_N910FEVR1DPE1_N910FXXU1DPB1_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> SingleDownload.
<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! (Ext4)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
firstly odin cache whatever is given to it first then after success it attempts to flash , so either you had a successful attempt once or you entered boot loop prior to using odin .
second what you have here can be one of two things (assuming that you are quite positive about your phone version and downloaded the right firmware to it because if you are not then this might explain why you ended up with a boot loop) , where either your phone is operator locked ( in this case the firmware must be provided by the service provider ) or the usb cable is damaged ( i know you said you tried different ones , but trust me they can all be damaged , try finding a fresh one on a friend )
cheers
Odin kept failing at the hidden.img.tar.ext4 file so i googled, and found that extracting the hidden file and then flashing that file separately in odin may work. I tried that and worked!
Phew!
night-mayor said:
firstly odin cache whatever is given to it first then after success it attempts to flash , so either you had a successful attempt once or you entered boot loop prior to using odin .
Thanks form your input and help
second what you have here can be one of two things (assuming that you are quite positive about your phone version and downloaded the right firmware to it because if you are not then this might explain why you ended up with a boot loop) , where either your phone is operator locked ( in this case the firmware must be provided by the service provider ) or the usb cable is damaged ( i know you said you tried different ones , but trust me they can all be damaged , try finding a fresh one on a friend )
cheers
Click to expand...
Click to collapse