Note 4 SM-N910F can't decrypt storage?? - Galaxy Note 4 Q&A, Help & Troubleshooting

I wrote the title like this because else it would be much more. This is only one of many problems im currently having with my note 4. And im pretty sure its no duplicate because i only found single problems of all the problems i listed below but not all together...
I can't boot the phone (no rom installed) anymore.
I can't flash any ROM because i get many errors saying "Can't mount /system" or /data or /cache or anything really. It can't even mount my external sd card so i cant even install a ROM from my sd card with twrp. The rom i'm trying to install is the stock rom i used 6 months ago to flash but now its not working anymore so i downloaded some newer ones but with odin i only get errors saying i cant write to the phone and it fails everytime when writing the system img. Maybe because it cant mount anything?
I tried to change the filesystem with TWRP to something other than ext4 but that didnt work because it needs to mount many things.... Also it says /system is 0MB /data is 0MB and so on...
I can't wipe or format it because i get the error "Can't mount blabla" like 10 times+.
I flashed TWRP because I couln't falsh anything else.
I can only boot into bootloader/fastboot and recovery mode
I maybe found a solution but for that i need fastboot to work. I think it can't find or mount anything because it is encrypted but it can't decrypt the filesystem? This reddit post says: /r/Nexus6P/comments/3qnzz0/twrp_unable_to_mount_data/ -> "fastboot format userdata" should fix it.
I have all drivers installed and adb works and everything is fine but when i enter fastboot/download mode and connect it to my pc via usb then my pc reconigzes it as "SAMSUNGS Mobile USB Modem" ???? My other phone in fastboot mode is instantly recognized as such.... My note 4 is completly empty. it only has the twrp i think because i cant see anything. no files...
I think this is what i should fix but maybe im missing something and theres an easier solution to this? I really need help for this. i tried everything i found for 2 days straight. Im sitting infront of that stupid phone like 10hours today and still cant fix it.
I can connect it with adb and used commands there. Can this or anything be done with adb? Or only possible with fastboot? Really any help would be much appreciated! Hope you understand me
My Phone is a Samsung Galaxy Note 4 SM-N910F trltexx o2 germany. If that helps in any way...
Thanks if you read it to this point.

I'm still in need of help for this... please

bump...

EDIT:
 @.slowdown
What's the Odin's error?
Did you try to:
Download SamFirm_v0.3.6.zip
Extract it and run SamFirm.exe
In "Model" write "SM-N910F"
In "Region" write "VIA" for 02 Germany or "DBT" for Germany
Click download and you'll get latest samsung firmware for your phone.
Extract the downloaded .zip file and you'll get a .tar.md5 file.
Download Odin3_v3.10.7
Reboot your phone in download mode (power+home+volumedown) and press volumeup to continue
Run Odin3_v3.10.7.exe
Connect your phone to pc via usb cable
On Odin you should see "<ID:whatever> Added!!"
Click on "AP" and select the .tar.md5 file mentioned before.
Click start.
Once done the phone will reboot and you should be back on stock samsung firmware.

finally someone who answered me. thanks.
I tried what you said and this is what i got.
this is what i get in odin:
<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> 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> FAIL! (Write)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The FAIL!(Write) message is what i was talking about in my OP.

.slowdown said:
finally someone who answered me. thanks.
I tried what you said and this is what i got.
this is what i get in odin:
The FAIL!(Write) message is what i was talking about in my OP.
Click to expand...
Click to collapse
Try adding a pit file in odin. May this thread can help you.
You can find it here

_mone said:
Try adding a pit file in odin. May this thread can help you.
You can find it here
Click to expand...
Click to collapse
thanks for the reply.
I downloaded the pit file and did what the thread said. the odin message was this:
<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> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
so everything seems alright. then after the odin message "PASS!" it rebooted and did "installing system update" and then booted into recovery mode.
this is what my stock android recovery now shows me:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
normaly i got this bunch of cant mounts on my twrp but it seems to be the same on the stock recovery.
well then i continued with the thread and navigated to the wipe data/factory reset. once i pressed ok the screen went black instantly and the only thing i could do is remove the battery after 10 mins or so doing nothing...
i really dont know what the problem for this can be
EDIT: oh yea i forgot to say that after removing the battery and inserting it again, when i hold the power button on the top left it says recovery booting for ~3 secs and then it turns black again and i need to remove the battery again. And when i go into the recovery mode it does the "installing system update" again with the animated android logo. then it turns black again... All this happend after my phone got an samstung system update and now it can't seem to update anything or i dont know

bump

hmm

.slowdown said:
hmm
Click to expand...
Click to collapse
anyone?

A final soution would be, including losing ALL your Data to connect the phone to your PC with Samsung Kies. Then resetting it via kies.

stysupreme said:
A final soution would be, including losing ALL your Data to connect the phone to your PC with Samsung Kies. Then resetting it via kies.
Click to expand...
Click to collapse
I already Tried that and Kies found that a phone is connected but it couldnt recognize it. Reinstalled drivers also. But tomorrow im trying it again because i cant remember if i tried everything with Kies. Maybe also on another Computer. Thanks for the tip and what exactly do i need to install for Kies to work? Samsung driver and Kies APP? Or did i miss something
EDIT: i tried it and it just cant detect my phone... maybe its because the phone can only boot into recovery with many errors on the phone as shown on the pictures.... i really dont know what to do. is there a way to manually detect the phone by hand?

Try using a different USB cable. The PC has to recognize the phone. Sometimes cables break. They charge but can't be used for data. Kies app and the latest drivera should be enough.

stysupreme said:
Try using a different USB cable. The PC has to recognize the phone. Sometimes cables break. They charge but can't be used for data. Kies app and the latest drivera should be enough.
Click to expand...
Click to collapse
didnt work either... my other phone can read the data just fine. i think i cant save the note 4 anymore....

.slowdown said:
didnt work either... my other phone can read the data just fine. i think i cant save the note 4 anymore....
Click to expand...
Click to collapse
Did you found any solution? I have the same problem...

Related

[GUIDE] How To Restore A Stuck Samsung Galaxy SI, SII and SIII

Restoring A Stuck Samsung Galaxy SI, SII and SIII​
Is your phone stuck like this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then read on! If not, this may only be useful for those who want to go back to the original Samsung Firmware.
Introduction
Too many people are getting stuck on the Samsung logo so I decided to make a tutorial on how to
get yourself off it. It is a simple tutoiral and noob friendly, but it will take time and patience because
the stock firmware is not just 300mb but can go into 1GB and more. This should on Samsung
Galaxy SI, SII, SIII. They are all tested and working, you may experiment on other phones if you
wish and you have no other choice. Read on for the downloads and instructions.
Downloads
Odin v3.07 - Click Here
Your Firmware - Find Here
Instructions
1. Go here and select your phone and its correct version's official firmware here: http://samsung-updates.com/latest-firmware/
2. Download Odin v3.07
3. Turn phone off completely and put it into download mode (Down Volume, Home Button and Power Button together).
4. After downloading the official firmware extract it and open Odin.
5. Select Auto Boot and F. Reset and put that .md5 file in the PDA section. NOTE: There should be COM: (PORT NUMB) in the first box.
6. Click Start and wait. If it succeeded then it will say PASS in green.
NOTE: This has worked for me and other people have confirmed it working for them after testing.
But if something more happens to your phone, I am not responsible.
Good luck.
Will be attaching more tutorials soon.
Sent from my GT-I9300 using xda premium
This is just a stock firmware flash via Odin as per multiple guides on the forum .
Its not getting off a stuck logo its re flashing full firmware in many cases a factory reset should be the first step or a reflash through recovery of the custom rom .
Multiple exact same guides in my view only confuse noobs .
jje
JJEgan said:
This is just a stock firmware flash via Odin as per multiple guides on the forum .
Its not getting off a stuck logo its re flashing full firmware in many cases a factory reset should be the first step or a reflash through recovery of the custom rom .
Multiple exact same guides in my view only confuse noobs .
jje
Click to expand...
Click to collapse
Got me off stuck on a logo.
Sent from my GT-I9300 using xda premium
AndroidPlant said:
Got me off stuck on a logo.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
A wipe data often fixes that too, if you have custom recovery,a dalvik/cache wipe could potentially fix it.
A re-flash of the Rom could fix it
.....indeed many things "could" fix it........I know your intentions are good, but could you refrain from posting links to this thread every time a problem comes up, because often the solution is much easier
There doesn't seem to be any i9300 firmwares on that site.
Hi, im doing everything as it says but gives me this
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-m0-m0xx-gti9300.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
please help me
Try different USB cables and USB ports. Try flashing the latest stock ROM from sammobile.com.
help plz
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGOF1_I9300OXXGOF1_I9300XXUGNB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Cant pass this part.
audit13 said:
Try different USB cables and USB ports. Try flashing the latest stock ROM from sammobile.com.
Click to expand...
Click to collapse
Yes, i've already done that still nothing.
Could it be hardware related issue?
You confirmed the model # in download mode? It fails with the original Samsung usb cables too?

[Q] Whiped OS, cant get back.

Hey everyone,
I got this problem, today i wanted to whipe my phone... But i failed and also whiped the OS... So i was stuck on samsung logo.. After i got into download mode i tried to flash the standard unbranded S4 called:I9505XXUFNC4_I9505PHNFNC1_PHN
After i tried to flash that as PDA with ODIN v3.04, it says it failed..
What to do now?
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNC4_I9505PHNFNC1_I9505XXUFNC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I used the official cable ...
Any options?
EDIT:
Now when i boot the phone it only says:
Firmware upgrade encountered an issue.Please select recoverymode in Kies & try again.
Tunestwo said:
Hey everyone,
I got this problem, today i wanted to whipe my phone... But i failed and also whiped the OS... So i was stuck on samsung logo.. After i got into download mode i tried to flash the standard unbranded S4 called:I9505XXUFNC4_I9505PHNFNC1_PHN
After i tried to flash that as PDA with ODIN v3.04, it says it failed..
What to do now?
I used the official cable ...
Any options?
EDIT:
Now when i boot the phone it only says:
Firmware upgrade encountered an issue.Please select recoverymode in Kies & try again.
Click to expand...
Click to collapse
just repeat procedure, change odin version, change usb port, change usb cable....
samersh72 said:
just repeat procedure, change odin version, change usb port, change usb cable....
Click to expand...
Click to collapse
no effect so far.... T.T
Try it on another pc
Or
Download another firmware
I had the same issue yesterday phone stoipped working got andropid.phone errors and phone would not make or take calls when go to dialer kept crashing and black screen tried wiping/factory reset and still had same issue on djembey stock pre root
I decided to then download stock EE firmware latest 4.4.2 this then failed and phone after this would not even boot up only thing I could manage to do now was to put into download mode would no longer even go into recovery mode either
I tried flashing about 4times and ODIN kept on failing tried with Odin 1.85, 3.04 3.07
FED up I read somewhere to try diff cable ( like that will make a diff I thought)
YESSSSS it flashed and now I have a working phone
After using, diffrent pc's, diffrent cables, and diffrent usb ports...
it worked... Jezus i love you guys!

[Q] Bricked Galaxy Tab 4 7.0 Stuck in Odin

Hello everyone! Its been a while since my rooting days(HTC ONE) and I'm a bit if not very rusty . I recently bought a Galaxy Tab 4 7.0. I attempted a root process through Odin and of course...it failed. Now I am stuck in the download mode and no matter what combination of buttons I use it returns there. I tried to see if I can get the original firmware through samfirmware.com for t230NU but to no avail. Any suggestions? I'd really appreciate it as I need the tablet. :fingers-crossed:
[email protected] said:
Hello everyone! Its been a while since my rooting days(HTC ONE) and I'm a bit if not very rusty . I recently bought a Galaxy Tab 4 7.0. I attempted a root process through Odin and of course...it failed. Now I am stuck in the download mode and no matter what combination of buttons I use it returns there. I tried to see if I can get the original firmware through samfirmware.com for t230NU but to no avail. Any suggestions? I'd really appreciate it as I need the tablet. :fingers-crossed:
Click to expand...
Click to collapse
stock firmware
http://forum.xda-developers.com/showthread.php?t=2778374
root
http://forum.xda-developers.com/showpost.php?p=53020637&postcount=87
Android Terminal Emulator cant find mrw
ShinySide said:
stock firmware
http://forum.xda-developers.com/showthread.php?t=2778374
root
http://forum.xda-developers.com/showpost.php?p=53020637&postcount=87
Click to expand...
Click to collapse
Thank you ShinySide for all your help! I was able to root successfully however when I try to replace vroot with Superuser with the terminal its unable to find the mrw file. I did extract and place the folder to the internal storage. I tried putting the file on the sdcard and that did not work either. What i ended up doing was downloading Superuser from the playstore. Will this have the same effect and will it update the binary correctly? My last question is-My Tab4 is says its a model T230NU but when i registered it n Samsung it shows SM-T230NZWAXAR...will the stock firmware conflict since the build is T230NUUEUOANE2?
Sorry for all the newb questions. I'm so glad I was able to unbrick my device and root though...Thank you so much!
[email protected] said:
Thank you ShinySide for all your help! I was able to root successfully however when I try to replace vroot with Superuser with the terminal its unable to find the mrw file. I did extract and place the folder to the internal storage. I tried putting the file on the sdcard and that did not work either. What i ended up doing was downloading Superuser from the playstore. Will this have the same effect and will it update the binary correctly? My last question is-My Tab4 is says its a model T230NU but when i registered it n Samsung it shows SM-T230NZWAXAR...will the stock firmware conflict since the build is T230NUUEUOANE2?
Sorry for all the newb questions. I'm so glad I was able to unbrick my device and root though...Thank you so much!
Click to expand...
Click to collapse
Post the exact terminal output. You shouldnt have any issue
Theres 2 model numbers. One for the white one for the black. Your tab 4 is SM-T230NZWAXAR which is the white one. SM-T230NYKAXAR is the blacks model number. It doesnt matter which you have its the same firmware. Samsung is just reading your full model number,
hi, iam the same problem, just 3 days ago my tab 4 7" (white) was stuck in a blacl screen with a yellow triangle, said: firmware upgrade encountered an issue, please select recovery mode in kies & try again.
The problem here is i cant enter in DOWNLOAD mode, in other tutorials said, for cellphones, that i need to put over the battery, but, in a tablet, how can i do this? i download a firmware from sammobile, my model number said SM-T230NU , i cant find the american version (i purchase this in radioshack USA) but i downlod the mexican version of Telcel, but nothing, OdIn always find an error, watch:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230NUUEU0ANE2_T230NUXAC0ANE2_HOME.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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> loke_1st.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> loke_2nd.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
THIS IS ANOTHER try:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230XXU0ANE6_T230OXX0ANE2_T230XXU0ANE6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> timh.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
please i need help.
and about the post of ShinySide (http://forum.xda-developers.com/showthread.php?t=2778374 ) what is the diference about NE2 firmware and ND9 firm?
nismo87 said:
hi, iam the same problem, just 3 days ago my tab 4 7" (white) was stuck in a blacl screen with a yellow triangle, said: firmware upgrade encountered an issue, please select recovery mode in kies & try again.
The problem here is i cant enter in DOWNLOAD mode, in other tutorials said, for cellphones, that i need to put over the battery, but, in a tablet, how can i do this? i download a firmware from sammobile, my model number said SM-T230NU , i cant find the american version (i purchase this in radioshack USA) but i downlod the mexican version of Telcel, but nothing, OdIn always find an error, watch:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230NUUEU0ANE2_T230NUXAC0ANE2_HOME.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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> loke_1st.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> loke_2nd.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
THIS IS ANOTHER try:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230XXU0ANE6_T230OXX0ANE2_T230XXU0ANE6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> timh.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
please i need help.
and about the post of ShinySide (http://forum.xda-developers.com/showthread.php?t=2778374 ) what is the diference about NE2 firmware and ND9 firm?
Click to expand...
Click to collapse
Your problem is you are trying to flash the wrong firmware. Youre trying to flash a firmware meant for data/service enabled tabs. Check my first post in this thread. Flash one of those.
Just bug/kernel fixes.
btw if youre seeing that message, you are in download mode.
Cant find mrw file
ShinySide said:
Post the exact terminal output. You shouldnt have any issue
Theres 2 model numbers. One for the white one for the black. Your tab 4 is SM-T230NZWAXAR which is the white one. SM-T230NYKAXAR is the blacks model number. It doesnt matter which you have its the same firmware. Samsung is just reading your full model number,
Click to expand...
Click to collapse
i have tried several times and still the same result. I get this message and then the tablet reboots. The Superuser app I downloaded from the Playstore did update the binary and all. However i would like to know what I did wrong for future reference with the mrw file. Thanks!
ShinySide said:
Your problem is you are trying to flash the wrong firmware. Youre trying to flash a firmware meant for data/service enabled tabs. Check my first post in this thread. Flash one of those.
Just bug/kernel fixes.
btw if youre seeing that message, you are in download mode.
Click to expand...
Click to collapse
thanks for the answer, but, excuse about my question, in u`r post about the firmwares, i just download this: Latest Firmware Version Download NE2, (the first link posted) but said me the same message in odin, (FAIL) i dont know if the options in ODIN are bad, i choose auto rebot and F.Reset Time.
or, need i erase the termination md5 with only .tar?
[email protected] said:
i have tried several times and still the same result. I get this message and then the tablet reboots. The Superuser app I downloaded from the Playstore did update the binary and all. However i would like to know what I did wrong for future reference with the mrw file. Thanks!
Click to expand...
Click to collapse
Do a search for each of those file names and give me the exact file names and locations. Someone else mentioned on another thread they had to ediit the script because they were a little different for some reason for them.
nismo87 said:
thanks for the answer, but, excuse about my question, in u`r post about the firmwares, i just download this: Latest Firmware Version Download NE2, (the first link posted) but said me the same message in odin, (FAIL) i dont know if the options in ODIN are bad, i choose auto rebot and F.Reset Time.
or, need i erase the termination md5 with only .tar?
Click to expand...
Click to collapse
Na those options wouldnt matter. That first time you flashed, loke_1st.bin flashed successfully then loke_2nd.bin failed. You might need to find a pit file for the tab 4 7inch and re-partition the device. Only one tho.... to get the pitfile you need hiemdall and hiemdall isnt compatible with the tab 4. least not yet. I saw a post a while ago for creating a pitfile on a device. Let me see if I can find it and see if itll work on my tab and create one and Ill post it if I can find it and create one
Okay this is all i can find. Just one issue...I have straight linux and no windows on my pc so I cant use or try to use it to get the pit, so 2 options if you want to try repartitioning it, try using this tool in download mode or find someone with windows willing to try to get the pitfile from their device
http://forum.xda-developers.com/galaxy-s2/orig-development/tool-updated-09-06-14-efs-professional-t1308546
ShinySide said:
Na those options wouldnt matter. That first time you flashed, loke_1st.bin flashed successfully then loke_2nd.bin failed. You might need to find a pit file for the tab 4 7inch and re-partition the device. Only one tho.... to get the pitfile you need hiemdall and hiemdall isnt compatible with the tab 4. least not yet. I saw a post a while ago for creating a pitfile on a device. Let me see if I can find it and see if itll work on my tab and create one and Ill post it if I can find it and create one
Click to expand...
Click to collapse
OK, thanks for the support, i will considering make a donation for this $$
so, in conclusion, iam really ina hole with this issue, no? i dont know how i can get brick in this form my tablet, only 3 weeks with it and is stuck...
i dont know much about this and samsung devices, but, need i another file apart of the firmware? the Pit file?
nismo87 said:
OK, thanks for the support, i will considering make a donation for this $$
so, in conclusion, iam really ina hole with this issue, no? i dont know how i can get brick in this form my tablet, only 3 weeks with it and is stuck...
i dont know much about this and samsung devices, but, need i another file apart of the firmware? the Pit file?
Click to expand...
Click to collapse
Check my previous post. I had just edited while you were responding Haha I have the donation link up because some people asked if I had one when I was compiling Carbon for s4's. I never accept them tho so its just there for "show" Ahaha
Its just one file. Contains all the partition block sizes, names, etc etc and willl delete everything and repartition the devices partitions, etc etc
Im guessing the loke bins are the bootloader. And since one flashed for you, it might be failing at a check point.
ShinySide said:
Check my previous post. I had just edited while you were responding Haha I have the donation link up because some people asked if I had one when I was compiling Carbon for s4's. I never accept them tho so its just there for "show" Ahaha
Its just one file. Contains all the partition block sizes, names, etc etc and willl delete everything and repartition the devices partitions, etc etc
Im guessing the loke bins are the bootloader. And since one flashed for you, it might be failing at a check point.
Click to expand...
Click to collapse
Hi again Shinyside,
today was a great day for my tablet jeje, its ALIVE again¡¡¡¡¡¡
what i made?
Just desinstall KIES, and reboot the Pc, install again the drivers for samsung, after, download again the Original firmware from your Link ( chrome://mega/content/secure.html#!I49V3YZB!LkqiYAvZF0dyL0YMbVMGlGWIhn7BQbFi84z4CIFQhKw
i downoad again because, sometimes in large files, the download is corrupted for X reason, unzip this in desktop (i dont know if this is good or not).
the next step was plug to charge for 1 hrs the tab 4, with the black screen turn on, Open Odin 3.07 , wait 2 minutes and upload the ND5 file previous downloaded, plug the TAB 4 in the Pc with (this is important) the OEM cable, i was plugin with other micro usb in the past attempted, so, just when Odin finish to charge 100% the firmware, just press START and wait a couple of minutes, the tablet autoreboot and now is alive.
but... i dont know but when my tab turn on again, all apps, pictures,etc was there so, i dont know if my tablet only was bricked temporarily or not completely bricked..... i dont know, only know that i have a tab again and thanks Shinyside for all support.
So, your link about donation is working or not? i want to invite u a beer, minimum :silly:
i want leave the Odin record about this, if anybody have the same problem:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230NUUEU0ANE2_T230NUXAC0ANE2_HOME.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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> loke_1st.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> loke_2nd.bin
<ID:0/003> param.lfs
<ID:0/003> DTim.Primary
<ID:0/003> DTim.Recovery
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> NVM.img
<ID:0/003> cache.img
nismo87 said:
Hi again Shinyside,
today was a great day for my tablet jeje, its ALIVE again¡¡¡¡¡¡
what i made?
Just desinstall KIES, and reboot the Pc, install again the drivers for samsung, after, download again the Original firmware from your Link ( chrome://mega/content/secure.html#!I49V3YZB!LkqiYAvZF0dyL0YMbVMGlGWIhn7BQbFi84z4CIFQhKw
i downoad again because, sometimes in large files, the download is corrupted for X reason, unzip this in desktop (i dont know if this is good or not).
the next step was plug to charge for 1 hrs the tab 4, with the black screen turn on, Open Odin 3.07 , wait 2 minutes and upload the ND5 file previous downloaded, plug the TAB 4 in the Pc with (this is important) the OEM cable, i was plugin with other micro usb in the past attempted, so, just when Odin finish to charge 100% the firmware, just press START and wait a couple of minutes, the tablet autoreboot and now is alive.
but... i dont know but when my tab turn on again, all apps, pictures,etc was there so, i dont know if my tablet only was bricked temporarily or not completely bricked..... i dont know, only know that i have a tab again and thanks Shinyside for all support.
So, your link about donation is working or not? i want to invite u a beer, minimum :silly:
i want leave the Odin record about this, if anybody have the same problem:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230NUUEU0ANE2_T230NUXAC0ANE2_HOME.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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> loke_1st.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> loke_2nd.bin
<ID:0/003> param.lfs
<ID:0/003> DTim.Primary
<ID:0/003> DTim.Recovery
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> NVM.img
<ID:0/003> cache.img
Click to expand...
Click to collapse
Sweet good deal man. Glad you got iit back up and running. I didn't even think about the cable. We an issue with using some different usb cables on the s4 too. But glad you got it back up and running. And yeah it works
the next step is, how to root my tab 4......
nismo87 said:
the next step is, how to root my tab 4......
Click to expand...
Click to collapse
Check post 2
ShinySide said:
Check post 2
Click to expand...
Click to collapse
Hope this is ok area to post this in. I am having a problem with Tab 4 T230NU wifi only. I am trying to get to download mode to flash with Odin, but I can not? It flashes on with screen. "Firmware Upgrade encountered an error an issue. Please select recovery mode in Kies & try again. " It just flashes then turns back on... I tried holding home and volume up. Home and volume down. home and volume up and down in the middle. I tried volume up, volume down. I have charged this for quite a while also, few hours. I also have a Jig that works with the s3 to go to download mode, that did not work.
I think if I can get to download mode I can get working again, but have not been able to get to that. Any help please? Thank you in advance.
jaredlappa said:
Hope this is ok area to post this in. I am having a problem with Tab 4 T230NU wifi only. I am trying to get to download mode to flash with Odin, but I can not? It flashes on with screen. "Firmware Upgrade encountered an error an issue. Please select recovery mode in Kies & try again. " It just flashes then turns back on... I tried holding home and volume up. Home and volume down. home and volume up and down in the middle. I tried volume up, volume down. I have charged this for quite a while also, few hours. I also have a Jig that works with the s3 to go to download mode, that did not work.
I think if I can get to download mode I can get working again, but have not been able to get to that. Any help please? Thank you in advance.
Click to expand...
Click to collapse
You are in download mode
Help!
Okay so I've been trying to root my Galaxy Tab 4 and everything I attempt fails, its stuck on ODIN mode and I cant seem to root it, recover it or anything. I need help
Devon S said:
Okay so I've been trying to root my Galaxy Tab 4 and everything I attempt fails, its stuck on ODIN mode and I cant seem to root it, recover it or anything. I need help
Click to expand...
Click to collapse
D,
while in odin reflash your custom recovery for your device with auto/restart checked.
odin will remain stuck in that mode until it restarts after successfully flashing an image.
m
This worked for me I was in soft brick I don't know if this will for you
1.download Odin v3
2.download twrp (sm-t230)
3.connect your tab to your PC and turn it on (make sure you have drivers installed)
4.you should see ADDED! ON ODIN (if you don't see it you probably didn't install the drivers correctly) click PDA and select the twrp rar file 5.wait for it to flash it (your tab may or may not reboot wait for Odin to say done or succeeded)
6.download a stock ROM for your tab
7.move the stock ROM onto a SD card
8.put SD card into tablet and mount it
9.tap install and look for the stock ROM
10.you may need to clear dalvik cache and/or data
I hope it helped. Pm me if you need help were to get the drivers and the stock ROM I'll be glad to help!
Sent from my SM-T230 using XDA Free mobile app

I think I rooted too much?

I have a Note 4 SM-N910G that used to run on 5.1.1.
It kept bugging me for an update through OTA but couldn't cuz It was rooted
so I skimmed over the procedure and used TWRP and flashed my phone to CM13. Which ended up worse than before.
Sooo I flashed the stock rom for 6.1.1 using Odin aaand it was still laggy and now shuts down on its own.
Long story short, I re-rooted a couple of times. 30-ish. Aaaand now anything I flash my phone with keeps failing.
I know. I know. I'm an idiot.
It can still boot with VOL Down + Power button + Home though.
When I do the volume up procedure I get a "firmware upgrade encountered an issue".
Am I screwed or is there still hope?
Don't give up mate, Your phone is just laggy, not hard bricked. There is no 6.1.1 stock rom for note 4, we just got 6.0.1!!! I have flashed (rom, mods, recovery, etc) thousands of times in my note 4 and your issue may not have caused because of rooting or flashing. As u have already tried mm stock, Try to flash 5.1.1 unmodified stock rom with odin. Check the battery too, Once my friend's Note 2 had boot loop just because of the faulty battery, in live power(battery removed after samsung logo with charger plugged) it booted without a issue.
I'm having exactly the same issue, nothing I flash be it stock or rom is stable any more. Lags, then shuts off. Sometimes reboots on it's own, other times it needs the battery pulling. Nothing I have tried works
scorpienez said:
Don't give up mate, Your phone is just laggy, not hard bricked. There is no 6.1.1 stock rom for note 4, we just got 6.0.1!!! I have flashed (rom, mods, recovery, etc) thousands of times in my note 4 and your issue may not have caused because of rooting or flashing. As u have already tried mm stock, Try to flash 5.1.1 unmodified stock rom with odin. Check the battery too, Once my friend's Note 2 had boot loop just because of the faulty battery, in live power(battery removed after samsung logo with charger plugged) it booted without a issue.
Click to expand...
Click to collapse
So I left it without the battery on for a couple of hours and tried to flash the stock rom and it failed again. But halfway through though!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910GDTU1COL3_N910GVAU1COL3_N910GDTU1COL3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Write)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
akeemcab26 said:
So I left it without the battery on for a couple of hours and tried to flash the stock rom and it failed again. But halfway through though!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910GDTU1COL3_N910GVAU1COL3_N910GDTU1COL3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Write)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Use Kies to recover your phone. Choose firmware upgrade & initialisation and enter your full model number (for example SM-N910F) & serial number.
akeemcab26 said:
So I left it without the battery on for a couple of hours and tried to flash the stock rom and it failed again. But halfway through though!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910GDTU1COL3_N910GVAU1COL3_N910GDTU1COL3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Write)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
See if you have checked repartition. uncheck it if it is checked(Uncheck this just before you are about to click on start) and flash again.
sanjaydev said:
See if you have checked repartition. uncheck it if it is checked(Uncheck this just before you are about to click on start) and flash again.
Click to expand...
Click to collapse
It's always unchecked though. Still the same result. Messes up at system.img.ext4
houstie said:
Use Kies to recover your phone. Choose firmware upgrade & initialisation and enter your full model number (for example SM-N910F) & serial number.
Click to expand...
Click to collapse
Kies 1? 2? or 3?
I'm using 3 btw.
Whenever I choose firmware upgrade & initialization it hangs when I search for my phone's model.
Ooookay. It said I needed a PIT File. I got one scouring the internet and did a flash.
I got this.
<ID:0/004> 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/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Write)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Now I read somewhere that I need to enable something in my android to make the system.img.ext4 not fail.
But how can I enable that option if I can't even finish flashing? :|
If I boot it normally, I get firmware upgrade encountered and issue.
Rafa5e5t6yf said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
all I'm seeing are broken links :\
akeemcab26 said:
Kies 1? 2? or 3?
I'm using 3 btw.
Whenever I choose firmware upgrade & initialization it hangs when I search for my phone's model.
Click to expand...
Click to collapse
Kies 3. Make sure you use capital letters when entering your phone model.
houstie said:
Kies 3. Make sure you use capital letters when entering your phone model.
Click to expand...
Click to collapse
I enter the phone model, SM-N910G, click ok, and says do not remove usb connection.
after the preparation for the update finishes Kies 3 just turns black and nothing in it can be clicked.
My phone's firmware is now 6.0.1
The errors I get are
system.img.ext4 fail
rpm.mbn fail
firmware encountered an issue
mmc read failed to boot normal
either of the 4 show up after flashing.
tried flashing with the PIT file + the stock firmware, PIT file only, firmware only,
system.img.ext4 fails. Always does. But last night I tried it again and it went halfway through! But still failed.
Here You go,
1. Use Odin v3.10, go to PIT tab and select your device specific pit file first.
2. Click AP on the right side and select the latest firmware .tar.md5 file.
3. Go to options tab and select Auto-reboot, clear nand partition, re-partition, F.reset time & bootloader update as you need to format emmc (nand).
4. Flash the device, wait for it to complete and give it 5 mins to boot.
5. Once rebooted you may get stuck at samsung logo, dont worry, just go to stock recovery by pulling battery and holding down volup+home+power and perform a factory reset and clear cache.
6. Might take upto 5mins, but works like a charm.
akeemcab26 said:
I tried flashing with the PIT file + the stock firmware, PIT file only, firmware only,
system.img.ext4 fails. Always does. But last night I tried it again and it went halfway through! But still failed.
Click to expand...
Click to collapse
Use this PIT file I extracted from latest 6.0.1 binary stock rom.
vighneshpillai90 said:
Here You go,
1. Use Odin v3.10, go to PIT tab and select your device specific pit file first.
2. Click AP on the right side and select the latest firmware .tar.md5 file.
3. Go to options tab and select Auto-reboot, clear nand partition, re-partition, F.reset time & bootloader update as you need to format emmc (nand).
4. Flash the device, wait for it to complete and give it 5 mins to boot.
5. Once rebooted you may get stuck at samsung logo, dont worry, just go to stock recovery by pulling battery and holding down volup+home+power and perform a factory reset and clear cache.
6. Might take upto 5mins, but works like a charm.
Click to expand...
Click to collapse
Thanks for the reply!
I used the PIT file you gave me and used
N910GDTU1DPD4_N910GODD1DPB5_N910GDDU1DPB4_HOME.tar and
N910GDTU1DPD4_N910GODD1DPB5_N910GDDU1DPB4_HOME.tar
but both still gave me the system.img.ext4 fail
I checked
auto reboot,
repartition,
f. reset time,
nand erase all
and phone bootloader update on the third try
but still failed and gave me a new error written in blue or grey not sure but it was something like
odin failed to write.
edit: I can now boot to android recovery!
but at the very bottom it says
supported api: 3
dm-verity verification failed...
E: failed to mount /system (invalid argument)
Still hoping someone could help me!

SN-j500FN not booting into twrp recovery

Hello
I want to jump on the Cyanogenmod train and i installed a custom recovery. However when i try to boot my device into recovery i get this weird screen that keeps getting darker. Pictures below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does anyone know how to fix this and what is causing this problem?
bcoudi said:
Hello
I want to jump on the Cyanogenmod train and i installed a custom recovery. However when i try to boot my device into recovery i get this weird screen that keeps getting darker. Pictures below.
Does anyone know how to fix this and what is causing this problem?
Click to expand...
Click to collapse
U will have the wrong twrp buddy
bcoudi said:
Hello
I want to jump on the Cyanogenmod train and i installed a custom recovery. However when i try to boot my device into recovery i get this weird screen that keeps getting darker. Pictures below.
Does anyone know how to fix this and what is causing this problem?
Click to expand...
Click to collapse
Cm12.1 built from source(based on 5.1.1) or cm13 ported (based on 6.0.1) ?
If cm12.1 built from source:
1) Are you on 5.1.1 Lollipop?
2) Did you flash correct TWRP recovery? http://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3468844
If cm13 ported:
1) Are you on 6.0.1 Marshmallow?
2) Did you flash correct TWRP recovery? http://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j500f-t3416960
The recovery is fixed, i can acces it now. Wich cyanogenmod versions are you guys using?
bcoudi said:
The recovery is fixed, i can acces it now. Wich cyanogenmod versions are you guys using?
Click to expand...
Click to collapse
Cm12.1 is working flawless.
Cm12.1 thread: http://forum.xda-developers.com/gal...m-cyanogenmod-12-1-samsung-galaxy-j5-t3468830 . Some people experienced random reboots with latest release, so if you experience too, then do this:
1) Download this zip: http://forum.xda-developers.com/showpost.php?p=69375277&postcount=334 . Ignore that is for J500H, it worked for my J500FN.
2) Open the zip and remove build.prop from system folder.
3) Now flash the zip in TWRP recovery and reboot.
4) Open build.prop from /system/ with some editor and add following lines at the end of it:
Code:
# GPS
persist.gps.qc_nlp_in_use=1
persist.loc.nlp_name=com.qualcomm.location
ro.qc.sdk.izat.premium_enabled=0
ro.qc.sdk.izat.service_mask=0x0
ro.gps.agps_provider=1
ro.pip.gated=0
5) Reboot and you are done.
CREDITS: @akasharif for this fix.
If you wonder why there isn't a new release with fix included, it's because Nick and Ganesh are working on cm13.
Personally I did this right after I flashed latest cm release and I didn't have any problem.
So i basically bricked my phone when messing with it. I tried to flash the stock rom trough odin but it doesn't work. I think its because i need to enable usb-debugging but i can't because i can't acces my phone. Anyone knows how i can fix this?
this is the message i get trough odin:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> J500FNXXS1APE5_J500FNVFG1APC4_J500FNXXS1APE4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> boot.img
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Ext4)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
bcoudi said:
So i basically bricked my phone when messing with it. I tried to flash the stock rom trough odin but it doesn't work. I think its because i need to enable usb-debugging but i can't because i can't acces my phone. Anyone knows how i can fix this?
this is the message i get trough odin:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> J500FNXXS1APE5_J500FNVFG1APC4_J500FNXXS1APE4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> boot.img
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Ext4)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You don't need to enable usb debug to flash stock rom as far as I know.
I got same problem when i tried to install first Marshmallow update, it was failing at hidden.omg.ext4.
Try this: https://www.youtube.com/watch?v=2uTHilnRsWw. Credits to @pacower for sharing that video. Also try to use newer Odin version (I used 3.09 or so all the time though).
Thanks! i've found the video and i can boot my android device again.
bcoudi said:
Thanks! i've found the video and i can boot my android device again.
Click to expand...
Click to collapse
Nice one
2 things, no need for 2 archiving programs. 7zip is more than capable of extracting tar archives, right click and select extract. No need to rename to md5.

Categories

Resources