Develop Bugs

[Q] stuck on "formatting /data"

I was on a clean full wipe Omega v19 ROM and flashed omegadroid's "Project_Note3_mod_PackageV2" but the new Note3 apps were not stable enough.
I found another developer playing with Note3 features and in my endless wisdom I decided to flash "Note_3_features_for_Note_2_MK4_v2_(E-Team)" on top of the existing mess :good:...... 320 apps were updated and optimized.
After the reboot I'm now stuck on Samsung Logo (waited 30+ mins).
When I enter recovery mode CWM 6.0.3.1 I get stuck on "formatting /data" while trying a full wipe.
Only battery removal gets me out of it
I've been googling and reading on XDA, there are many tips and hints but no solution.
- restore EFS? (I have of course a backup from sometime last year)
- reroot?
- reflash CWM?
- flash stock ROM (fear of getting a Knox bootloader stops me here...)
- flash custom ROM again (without doing a full wipe?)
please help... I don't want to make things worse . I have access to recovery mode and bootloader mode, but not sure on the order in which to do things now...
EDIT: I tried a "wipe cache" in recovery and a then new install with the same custom ROM "Omega v19 again. Everything seems fine in the beginning. As soon as it starts installing it stays at "Installing 0%". After about a minute a reboot and then stuck on Samsung logo again.

dXsL said:
I was on a clean full wipe Omega v19 ROM and flashed omegadroid's "Project_Note3_mod_PackageV2" but the new Note3 apps were not stable enough.
I found another developer playing with Note3 features and in my endless wisdom I decided to flash "Note_3_features_for_Note_2_MK4_v2_(E-Team)" on top of the existing mess :good:...... 320 apps were updated and optimized.
After the reboot I'm now stuck on Samsung Logo (waited 30+ mins).
When I enter recovery mode CWM 6.0.3.1 I get stuck on "formatting /data" while trying a full wipe.
Only battery removal gets me out of it
I've been googling and reading on XDA, there are many tips and hints but no solution.
- restore EFS? (I have of course a backup from sometime last year)
- reroot?
- reflash CWM?
- flash stock ROM (fear of getting a Knox bootloader stops me here...)
- flash custom ROM again (without doing a full wipe?)
please help... I don't want to make things worse . I have access to recovery mode and bootloader mode, but not sure on the order in which to do things now...
Click to expand...
Click to collapse
change your recovery to 5.15.0 all be fine,flash via odin and try a fresh install but before that just try to wipe data after changing recovery

shhbz said:
change your recovery to 5.15.0 all be fine,flash via odin and try a fresh install but before that just try to wipe data after changing recovery
Click to expand...
Click to collapse
No luck finding ClockWorkMod 5.15.0... Do you perhaps mean TWRP or PhilZ?

dXsL said:
No luck finding ClockWorkMod 5.15.0... Do you perhaps mean TWRP or PhilZ?
Click to expand...
Click to collapse
philz here http://d-h.st/users/philz_touch/?fld_id=16053#files

shhbz said:
philz here http://d-h.st/users/philz_touch/?fld_id=16053#files
Click to expand...
Click to collapse
Flashed PhilZ Touch 6 (CWM base version v6.0.4.5).
new recovery starts fine. same result though: stuck on "Formatting /data"
funny thing though with PhilZ: while "stuck on formatting /data" the screen and bottom icons react when I press them (light up and short vibration, mobil is therefore not really "stuck").
after about a minute: reboot, and then stuck on Samsung logo.
EDIT: From recovery menu, trying a "format /data" (if I can't wipe it, perhaps it needs a clean format). Following text appears:
E. unknown volume for path [/sd-ext]
E. unknown volume for path [/sd-ext]
Formatting /data...
and after a minute, again a reboot and stuck on Samsung logo.
stuck again...

You should try Philz 5.x, I also had problems with 6.x

dalanik said:
You should try Philz 5.x, I also had problems with 6.x
Click to expand...
Click to collapse
tnx. flashed PhilZ 5.15.0 (combining post 2 and 6, apologies to shhbz for not pickling up on the version number)
result is the same: again stuck on "formatting /data"
and about a minute later a reboot followed by the samsung logo.
also removed SD and SIM card in an attempt to solve the problem. no difference whatsoever.
EDIT: system information from PhilZ:
System size: 2016 MB
Free: 1984 MB
Data Size: 10709MB
Free: 6091 MB
SDCard Size: -1 MB
Free: -1 MB
Surely the "-1 MB" is not good...

I managed to start my phone again, but I have not really been able to find the reason. This is what I did: (hope it can help others)
In an attempt to get things working again, I flashed a totally different ROM.
" [N7100 MK4][1Dec]Dr.Ketan's Custom ROM V6 Deodexed|Prerooted|Note3 Fs"
(http://forum.xda-developers.com/showthread.php?t=2472270)
Of course without a "full wipe" in recovery (since this does not work, see post #1), and I only performed a "wipe cache". Installation went fine. My phone was before stuck at the first Samsung logo at the top of the screen with model number "GT-N7100". After a few seconds, the boot animation started (blue Samsung logo in the middle of the screen and "breathing" blue LED).
My Note2 starts again after more than a day of nothing! There are some crashes which is the result of changing ROM/ without full wipe. So I tried a factory reset from within this ROM. After reboot it entered recovery mode and presented the choice to "fix root", which I answered "No" (as far as I know, answering "yes" results in a lost root). Now wait SEVERAL MINUTES when presented with the Samsung boot animation (blue samsung logo with breathing LED), and you should get the familar "welcome" screen where you select langage etc.

SOLVED
problem is solved with help from this thread and a LOT og googling and reading in the community. thank you!!
Flashing Dr. Ketan's ROM and performing a "Settings/Backup and Restore/Factory reset" from hos ROM did the trick.
I am still unsure why the "/data" failed. It seemed to mount fine, but format or wipe got stuck.
To test, I then tried (of course) a reboot to recovery: "wipe cache" worked fine, and "full wipe" now also works fine. Seems that his ROM restored the structure (partition layout?) of the internal memory.:good: Now I have to install it again

On omega 19 also. Same problem. Fixed by flashing philz touch by odin.
My problem started when I tried to install a diferent rom...same stuff suck on formatting. After a few mins it would restart in recovery by itself. I tried to install TWRP but it went into "recovery bootloop" it started the TWRP blue image and it just kept turning of and on.
I also reseted settings from inside the rom.
Sent from my GT-N7100 using XDA Premium 4 mobile app

dXsL said:
problem is solved with help from this thread and a LOT og googling and reading in the community. thank you!!
Flashing Dr. Ketan's ROM and performing a "Settings/Backup and Restore/Factory reset" from hos ROM did the trick.
I am still unsure why the "/data" failed. It seemed to mount fine, but format or wipe got stuck.
To test, I then tried (of course) a reboot to recovery: "wipe cache" worked fine, and "full wipe" now also works fine. Seems that his ROM restored the structure (partition layout?) of the internal memory.:good: Now I have to install it again
Click to expand...
Click to collapse
read install instruction for phoenix linked to signature and see if android hd wipe does the job and what about the option to data/factory to clean install a rom

Got it thanks..
---------- Post added at 02:52 PM ---------- Previous post was at 02:02 PM ----------
I have done as shhbz said ... it didnt help ...any other solution .. i have the same problem because in the systeminfo it shows the same number i.e sdcard = -1
Also i have the problem that i cannot install as my installer stuck after 3 to 4 next buttons .... some times 3 and sometimes 5 not any particular next button...

msarmad said:
Also i have the problem that i cannot install as my installer stuck after 3 to 4 next buttons .... some times 3 and sometimes 5 not any particular next button...
Click to expand...
Click to collapse
have seen that many times. I could never figure that out. I tried going through the menus quickly, I tried going slowly. No difference. Remove battery and try again and again and again, and sometimes you get to the end and it starts installation. Does not make sense but works. It must be an internal Aroma thing. It is only during pre-installation this can happen, as soon as the actual installation starts it will continue.

dXsL said:
have seen that many times. I could never figure that out. I tried going through the menus quickly, I tried going slowly. No difference. Remove battery and try again and again and again, and sometimes you get to the end and it starts installation. Does not make sense but works. It must be an internal Aroma thing. It is only during pre-installation this can happen, as soon as the actual installation starts it will continue.
Click to expand...
Click to collapse
I have sorted it this problem by using philz_touch_5.15.0-n7100.tar.md5.Otherwise i have same issue before.. after this at least this problem is sorted out now.
though i am still not able to boot after successful installation. Stuck at boot logo. (i have indian 4.3 original knox boot loader ****)

NEED HELP - Bricked phone?

Hi!
Some days ago my phone is suddenly died.
Now it is in bootloop, I cannot enter in recovery mode but I can enter in Odin mode.
I tried to flash from odin different recovery (CWP, TWRP). The installation was successful, but after reboot I still cannot enter in recovery mode.
Can anybody help me?
Phone never rooted or flashed.
GT-I9195 LTE - European (Italy)
Original firmware, original rom, always updated.
Code:
CURRENT BINARY: Samsung Official
SYSTEM STATYS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 2
WRITE PROTECTION: Enable
Thank you,
Daniele

Same here. I didn´t find any solution. Did you?

Can anybody help me? I still have this damn problem

shady9090 said:
Can anybody help me? I still have this damn problem
Click to expand...
Click to collapse
As you are still on stock and the custom recovery has not flashed your best bet is probably to use Kies (not that I've ever done this, but that is my understanding for your situation)
There are many tutorials, this one looks good
http://forums.androidcentral.com/am...amsung-emergency-recovering-samsung-kies.html

recovery problem
IronRoo said:
As you are still on stock and the custom recovery has not flashed your best bet is probably to use Kies (not that I've ever done this, but that is my understanding for your situation)
I have a similar problem.
I have a bricked and then debricked GT 9190.
I have download mode but no recovery menu coming up when I booted to recovery. I tried flashing several custom recoveries without luck. Odin completes custom recovery flash and then reboots into recovery, where I see the same stock recovery screen without a menu (so there are no wipe cache, system etc.) but only the error codes below and the dead android.
I tried flashing an unroot image, which succeeded. I tried flashing through Heimdall and succeded. I tried adb and cmd but it does not detect device.
I also tried flashing 4 different stock roms for my country (TUR). 2 of them had 4 files and the other two one single file. I tried flashing a Russian version too. It flashed without problem but the recovery error persists. I have been looking for a solution for days now and I am stuck, without any light.
The error code in stock recovery:
manuel mode
appling multi csc
applying the cscs code tur
failed to compare 'system/csc/common/system/lib/libom.so' 'system/lib/libom.so'
(no data available)
E: failed to mount /cache
(invalid argument)
can't mount 'cache/' invalid argument
E: failed to mount /cache
(invalid argument)
E: can't mount cache/recovery/last_recovery
Any help will be appreciated.
Click to expand...
Click to collapse

Canercan said:
Odin completes custom recovery flash and then reboots into recovery, where I see the same stock recovery screen without a menu (so there are no wipe cache, system etc.) but only the error codes below and the dead android.
Click to expand...
Click to collapse
I think it means recovery started but without a command. When you are In recovery screen press vol up (or maybe hold power button in then press vol up, not sure of exact combo)
edit: google recovery "no command"

IronRoo said:
I think it means recovery started but without a command. When you are In recovery screen press vol up (or maybe hold power button in then press vol up, not sure of exact combo)
edit: google recovery "no command"
Click to expand...
Click to collapse
Hi,
Thanks for your reply.
I tried all combinations with the buttons in the recovery menu. No luck.
It is also hard to try because it reboots after a few seconds of going to recovery screen. (with the error codes above.)
Also when I get into download mode it says Current Binary: Samsung Official and System Status: Official.
Even if I flash root file through ODIN.
I am also checking your advise no command on google. But did not come up with anything working yet.
Any other ideas?

Canercan said:
Hi,
Thanks for your reply.
I tried all combinations with the buttons in the recovery menu. No luck.
It is also hard to try because it reboots after a few seconds of going to recovery screen. (with the error codes above.)
Also when I get into download mode it says Current Binary: Samsung Official and System Status: Official.
Even if I flash root file through ODIN.
I am also checking your advise no command on google. But did not come up with anything working yet.
Any other ideas?
Click to expand...
Click to collapse
Oh, it's rebooting. An unusual error but I think it is either corrupted memory or memory hardware issue.
If it was my phone I'd try flashing a pit file for your phone/country csc followed by a full stock rom (NOT the single file).
Else send for jtag if you think it's not hardware issue

IronRoo said:
Oh, it's rebooting. An unusual error but I think it is either corrupted memory or memory hardware issue.
If it was my phone I'd try flashing a pit file for your phone/country csc followed by a full stock rom (NOT the single file).
Else send for jtag if you think it's not hardware issue
Click to expand...
Click to collapse
Hi,
I contacted Samsung today and learnt that I have a month of warranty for it!
They said it was a mainboard issue, so they took it within warranty.
I hope they can do it in a couple of weeks,before I visit another country..
Thanks for your support.

Same thing happened to me today randomly... Black screen on anything, boots only into download mode with no problem, 4 years out of warranty I guess XD...

S4 mini i9195 US with no recovery, cant flash it via odin!

hello guys, im having a problem with a s4 mini, i dont have a recovery, a friend gave it to me with this problem.
I can get download mode but when i try to flash TWRP or CWM i get the OK signs in odin but it doesnt get into recovery, well it gets to recovery but it says "no command" (sin comando, in spanish).
It used to have jellybean and updated itself to kitkat, it never had a custom rom.
This is what the screen in download mode shows:
ODIN MODE
PRODUCT NAME : GT-I9195
CURRENT BINARY: samsung official
SYSTEM STATUS: Official
KNOX KERNEL LOCK : 0x0
KNOX WARRANTY VOID : 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER RP SWREV: 2
WRITE PROTECTION ENABLE
I tried lot of things, but my last resort is to ask, if you have anything to help i appreciate!

maybe should try stock rom next with odin.

S3miniFin said:
maybe should try stock rom next with odin.
Click to expand...
Click to collapse
Already tried many stock firmwares for i9195 , when odins flashes it, it reboots to recovery and it says "NO COMMAND" ( Sin comandos ) then reboots and starts again with that.

Did you get this fixed mate. I'm pulling my hair out with the same problem. My son messed up a perfectly good phone that I had used for 3 years, and the toerag won't tell me what he did. (apparently he was texting when it when down) Tried various version of stock ROM and I get get diddly squat. ODIN fails to write the firmware and I get aboot on the phone screen. Current problem is stuck on Bootloop. Might just throw the thing away and buy a new one. Would like to fix it though....I'd be eternally grateful for any advice....Thnx

Capokhatpin,
Your son didn't do anything to your phone ! It's just faulty hardware and common problem to Samsung S4 Mini ...
And until now there are dozens of phones that are broken and there is still no solution for that problem.
So, leave the kid alone ...
Cheers !

I have the similar problem at my i9195 - at booting directly to recovery after "successful" flash of cwm over odin or heimdall, the stock recovery appears again without any change...
So did I understand it correctly that there is no chance to fix it?

lupus92 said:
I have the similar problem at my i9195 - at booting directly to recovery after "successful" flash of cwm over odin or heimdall, the stock recovery appears again without any change...
So did I understand it correctly that there is no chance to fix it?
Click to expand...
Click to collapse
No I think you have different problem, are you flashing cwm recovery 2x? You need to flash it once then boot immediately back into download & flash it a 2nd time. If you only do it once or you do a normal boot between flashes it will not work, start again.

2x? Hmh, i tried it (both odin and heimdall), but it doesn't work either (also 3x or 4x)... again just stock recovery.
The story behind it: An update from stock rom failed, and after it it stuck at boot logo. When starting recovery, error messages that mounting /system failed appear. So I decided to try to flash CM on it -> first custom recovery. I tried the CM recovery, CWM recovery, Twrp.... No success. In Odin mode it says "Current Binary: Samsung Official" and "System Status: Official".
Any ideas how to fix it?

lupus92 said:
2x? Hmh, i tried it (both odin and heimdall), but it doesn't work either (also 3x or 4x)... again just stock recovery.
The story behind it: An update from stock rom failed, and after it it stuck at boot logo. When starting recovery, error messages that mounting /system failed appear. So I decided to try to flash CM on it -> first custom recovery. I tried the CM recovery, CWM recovery, Twrp.... No success. In Odin mode it says "Current Binary: Samsung Official" and "System Status: Official".
Any ideas how to fix it?
Click to expand...
Click to collapse
I couldn't do it, i threw it away, just give the kid a slap, don't keep trying, you deserve better.
God**** phone.

IronRoo said:
No I think you have different problem, are you flashing cwm recovery 2x? You need to flash it once then boot immediately back into download & flash it a 2nd time. If you only do it once or you do a normal boot between flashes it will not work, start again.
Click to expand...
Click to collapse
So, I tried also to flash the stock ROM by booting it with „debrick“ image from SD card and flashing from „download mode“ went good, but after reboot it was same and I couldn't boot into „recovery“ with message „No command....“ or something like that. And You write that I have to flash only CWM or other TWRP recovery and then twice in the row. Is that correct ?
Sent from my GT-N7000 using XDA-Developers mobile app

Boombastical said:
So, I tried also to flash the stock ROM by booting it with â??debrickâ?? image from SD card and flashing from â??download modeâ?? went good, but after reboot it was same and I couldn't boot into â??recoveryâ?? with message â??No command....â?? or something like that. And You write that I have to flash only CWM or other TWRP recovery and then twice in the row. Is that correct ?
Click to expand...
Click to collapse
No, sorry I misunderstood @lupus92 original situation.

Boombastical said:
So, I tried also to flash the stock ROM by booting it with �¢??debrick�¢?? image from SD card and flashing from �¢??download mode�¢?? went good, but after reboot it was same and I couldn't boot into �¢??recovery�¢?? with message �¢??No command....�¢?? or something like that. And You write that I have to flash only CWM or other TWRP recovery and then twice in the row. Is that correct ?
Click to expand...
Click to collapse
jobs done so back to xda.
I have wondered if in situations like the above where nothing seems to work if a nand erase in Odin would help, but I've never seen it mentioned here on the S4 Mini forum. Is there a reason?
I've not researched it or tried it, but have seen it done on other forums (maybe the S4????). You have to use the full original stock firmware that originally came with your phone at the SAME TIME (else it will brick) I think and have a back up of your imei (though it should rebuild?). I'm not even sure if it deletes ALL partitions or leaves some ..... might be worth looking into it. @lupus92

IronRoo said:
jobs done so back to xda.
I have wondered if in situations like the above where nothing seems to work if a nand erase in Odin would help, but I've never seen it mentioned here on the S4 Mini forum. Is there a reason?
I've not researched it or tried it, but have seen it done on other forums (maybe the S4????). You have to use the full original stock firmware that originally came with your phone at the SAME TIME (else it will brick) I think and have a back up of your imei (though it should rebuild?). I'm not even sure if it deletes ALL partitions or leaves some ..... might be worth looking into it. @lupus92
Click to expand...
Click to collapse
I have here an S4 Mini and when I boot it with SD Card and 'debrick' image on it, it always fail to write to nand but it allow me to go to 'download mode' and to flash original stock ROM but after succesful flashing and reboot it still have no acces to recovery...
Does flashing only any custom recovery would help ?
Any idea ?
Sent from my GT-N7000 using XDA-Developers mobile app

Boombastical said:
I have here an S4 Mini and when I boot it with SD Card and 'debrick' image on it, it always fail to write to nand but it allow me to go to 'download mode' and to flash original stock ROM but after succesful flashing and reboot it still have no acces to recovery...
Does flashing only any custom recovery would help ?
Any idea ?
Click to expand...
Click to collapse
I don't think another recovery will help, but I'm no expert about this sort of thing. I would say it's worth a try through.
If that doesn't work and you are at the point of throwing your phone away, I wonder if it's worth giving the "nand erase all" command a try as it has been shown to fix write permissions (though I'm not sure if this is your problem) and other major issues software issues. But as it deletes the entire nand memory so you need to be very careful & know exactly what will hapen. You need a backup of your efs/imei (I'd use 2 methods just to be sure as have just read someone couldn't restore it from some app),( can you boot into system?) Also you must use a FULL stock ROM with pit file etc to rebuild partitions.
For example the guy below with a regular S4 seems to be in similar situation, though for different reason, he was able to recover using nand erase all. But our phone is different of course!
Also have read one case where guy had to flash stock with nand erase all ticked then had to immediately reflash stock again without erase ticked.
http://forum.xda-developers.com/galaxy-s4/help/help-nand-erase-t2863345
--–-------------------------------------
edit; Also another S4 thread they have flashed bootloaders to fix write access to partitions,
http://forum.xda-developers.com/showthread.php?t=1840030
&
http://www.androidauthority.com/galaxy-s3-i535-unbrick-soft-brick-125413/

IronRoo said:
I don't think another recovery will help, but I'm no expert about this sort of thing. I would say it's worth a try through.
If that doesn't work and you are at the point of throwing your phone away, I wonder if it's worth giving the "nand erase all" command a try as it has been shown to fix write permissions (though I'm not sure if this is your problem) and other major issues software issues. But as it deletes the entire nand memory so you need to be very careful & know exactly what will hapen. You need a backup of your efs/imei (I'd use 2 methods just to be sure as have just read someone couldn't restore it from some app),( can you boot into system?) Also you must use a FULL stock ROM with pit file etc to rebuild partitions.
For example the guy below with a regular S4 seems to be in similar situation, though for different reason, he was able to recover using nand erase all. But our phone is different of course!
Also have read one case where guy had to flash stock with nand erase all ticked then had to immediately reflash stock again without erase ticked.
http://forum.xda-developers.com/galaxy-s4/help/help-nand-erase-t2863345
--–-------------------------------------
edit; Also another S4 thread they have flashed bootloaders to fix write access to partitions,
http://forum.xda-developers.com/showthread.php?t=1840030
&
http://www.androidauthority.com/galaxy-s3-i535-unbrick-soft-brick-125413/
Click to expand...
Click to collapse
Thanks for sharing your thoutghs, but unfortunately I can't boot anymore to 'Download mode'. [emoji45] It can be still booted by 'Debrick' image from SD card but nothing more then that. From there I can't go anywhere further. Without SD Card it doesn't give signs of life except if it is attached via USB it shows as QHSUSB_DLOAD...
I have no time now to play with the phone, but I will try in the weekend again to come to 'Download mode' and to flash again recovery or to erase flash nand cause I have already EFS back up somewhere on my external HD and then we will see what will happened. Thanks again and cheers !
Edit: I can't flash anything thru 'Debrick image' via Odin 3.09. It always give error: Faild to write mmc nand... It can't erase nand nor boot to 'Download mode' ... So I'm clueless at the moment... It looks as the nand is damaged and it can't be accessed anymore... Sadly, I think this S4 Mini will be ended as spare phone for parts only for my girlfriend phone... That's it... If someone have more ideas about it I can still try it... Cheers !
Sent from my GT-N7000 using XDA-Developers mobile app

GT-N7105 bootloops Samsung logo

Trying to fix a friend's GT-N7105. At the moment it just bootloops the Samsung bootloader screen (which shows the model number GT-N7105).
I can boot it into download mode just fine. On download mode it just says that both the "Current Binary" and "System Status" are "Custom".
I've tried flashing the stock ROM for the phone (the latest for the Optus version) with Odin. I've also tried doing a firmware restore through Kies 2. Both of these complete fine, but the phone continues bootlooping the Samsung logo.
I've tried directly flashing the newest bootloader with Odin, and I've tried flashing a custom recovery with Odin. I've tried flashing the stock firmware with the device's PIT file and re-partition selected. Nothing seems to change how the phone behaves. I can't boot into recovery mode (it just continues the Samsung logo bootlooping).
The emmc doesn't seem busted, since it happily downloads the full system.img when flashing. Odin/Kies finish flashing without errors, so I'm stumped. Any ideas?

Passa91 said:
Trying to fix a friend's GT-N7105. At the moment it just bootloops the Samsung bootloader screen (which shows the model number GT-N7105).
I can boot it into download mode just fine. On download mode it just says that both the "Current Binary" and "System Status" are "Custom".
I've tried flashing the stock ROM for the phone (the latest for the Optus version) with Odin. I've also tried doing a firmware restore through Kies 2. Both of these complete fine, but the phone continues bootlooping the Samsung logo.
I've tried directly flashing the newest bootloader with Odin, and I've tried flashing a custom recovery with Odin. I've tried flashing the stock firmware with the device's PIT file and re-partition selected. Nothing seems to change how the phone behaves. I can't boot into recovery mode (it just continues the Samsung logo bootlooping).
The emmc doesn't seem busted, since it happily downloads the full system.img when flashing. Odin/Kies finish flashing without errors, so I'm stumped. Any ideas?
Click to expand...
Click to collapse
Make sure that you have pressed power + volume up + home button to boot into recovery (maybe you have known already)
And try to format everything: data, system, cache,...Wipe everything. There should be some adb commands to do it without recovery. After that reflash stock ROM again to see if it work.

@Passa91
 @ginga133
I can access to recovery mod from odin !
I confirm when I flash this file (BTW it is recovery & cash fix file made by chainfire ) , via odin my phone reboot into stock recovery !!
you can try it At your own risk
here ( in recovery) you can do what you need (delete cash / data..... reboot)
my PC win10 pro 64bit, odin v3.11.1
my phone N7100 twrp 3.0.2.0 , stock kernel , custom rom......
kindly check attached pictures
at last I hope it will help
Regards

xcorona said:
@Passa91
@ginga133
I can access to recovery mod from odin !
I confirm when I flash this file (BTW it is recovery & cash fix file made by chainfire ) , via odin my phone reboot into stock recovery !!
you can try it At your own risk
here ( in recovery) you can do what you need (delete cash / data..... reboot)
my PC win10 pro 64bit, odin v3.11.1
my phone N7100 twrp 3.0.2.0 , stock kernel , custom rom......
kindly check attached pictures
at last I hope it will help
Regards
Click to expand...
Click to collapse
Thanks for that. This seems to be for the N7100. I tried flashing that file both as is and when replacing the included recovery with one appropriate for the N7105. Still just boots back to the bootloader (looping, same as before). Certainly didn't make anything worse.
If I leave it alone, sometimes it randomly makes it to the animated Samsung logo, where it plays the boot sound (dun dun dun duuun dun), but then this animation loops forever (I have tried leaving it overnight).

Passa91 said:
Thanks for that. This seems to be for the N7100. I tried flashing that file both as is and when replacing the included recovery with one appropriate for the N7105. Still just boots back to the bootloader (looping, same as before). Certainly didn't make anything worse.
If I leave it alone, sometimes it randomly makes it to the animated Samsung logo, where it plays the boot sound (dun dun dun duuun dun), but then this animation loops forever (I have tried leaving it overnight).
Click to expand...
Click to collapse
sorry to hear that
i think N7105 differs from N7100 {modem & kernel (boot*img ) }afaik, I cannot confirm
anyhow I did not find an alert from the developer regarding this matter (N7105/N7100) in his post
https://forum.xda-developers.com/showthread.php?t=1932327
at last thanks for reporting your results
Regards

xcorona said:
@Passa91
@ginga133
I can access to recovery mod from odin !
I confirm when I flash this file (BTW it is recovery & cash fix file made by chainfire ) , via odin my phone reboot into stock recovery !!
you can try it At your own risk
here ( in recovery) you can do what you need (delete cash / data..... reboot)
my PC win10 pro 64bit, odin v3.11.1
my phone N7100 twrp 3.0.2.0 , stock kernel , custom rom......
kindly check attached pictures
at last I hope it will help
Regards
Click to expand...
Click to collapse
I've flashed the file, but still having the same bootloop problem. It is ok, I have ordered a new motherboard now. Thanks for the input.

galaxy note 4 SM-N910P won't flash any ROm file

HI Please i have this ERROR ON mY N910p it wont flash any custom or stock firmware i don't know what to do . my Note 4 can't boot in to recovery mode. it boots at times and goes off after but in the download mode it boots well and it show the error in the images on Odin and on my phones screen ..i have tried soo many tricks but yet it didn't work .i'm confuse please some one should help me get back my N910p to Life please

If you're trying to flash a ROM from the stock recovery, that could be one of your issues. You would need to have a custom recovery like TWRP in order to flash from recovery.
As for using ODIN to flash a stock ROM, make sure you have the correct drivers installed to your computer before attempting to flash anything. Make sure you are choosing the correct slot in ODIN to load your .tar file as well. I've never seen eMMC errors in download mode before but that doesn't look good. I'm not that knowledgeable about Android phones yet to be able to troubleshoot very many issues.

johnwiz said:
HI Please i have this ERROR ON mY N910p it wont flash any custom or stock firmware i don't know what to do . my Note 4 can't boot in to recovery mode. it boots at times and goes off after but in the download mode it boots well and it show the error in the images on Odin and on my phones screen ..i have tried soo many tricks but yet it didn't work .i'm confuse please some one should help me get back my N910p to Life please
Click to expand...
Click to collapse
Flash this QI5 firmware it will flash without errors because as i can see "fuse 5 binary 4" means you are on QI5 BL/BB so you cannot flash older firmware because its locked bootloader/baseband.
Must do factory reset from stock recovery after finish flashing.
https://androidfilehost.com/?fid=674106145207497529

Trex888 said:
Flash this QI5 firmware it will flash without errors because as i can see "fuse 5 binary 4" means you are on QI5 BL/BB so you cannot flash older firmware because its locked bootloader/baseband.
Must do factory reset from stock recovery after finish flashing.
https://androidfilehost.com/?fid=674106145207497529
Click to expand...
Click to collapse
First of all thanks for your reply.. I just flashed the QI5 firmware but the phone is rebooting in to recovery Mode without sucess .. it is just going to recovery and after some fewer second it goes off and on again .. i have tried to install the QE1 but it cant flash it gives me the error on the image below..please assist me solve this problem...Thanks in advance
i taught it was a mother board problem but now that it has flashed the Qi5 firmware i have a Hope ..Help me please

Psilocelium said:
If you're trying to flash a ROM from the stock recovery, that could be one of your issues. You would need to have a custom recovery like TWRP in order to flash from recovery.
As for using ODIN to flash a stock ROM, make sure you have the correct drivers installed to your computer before attempting to flash anything. Make sure you are choosing the correct slot in ODIN to load your .tar file as well. I've never seen eMMC errors in download mode before but that doesn't look good. I'm not that knowledgeable about Android phones yet to be able to troubleshoot very many issues.
Click to expand...
Click to collapse
thanks for your reply .. yes it is the correct firmware ..i saw in one post that it is due to the fact that i have updated to a firme with E-fuse protection ..i just flashed the Qi5 firmware but it bootloops .. it can't start corectly ...its just rebooting and the phone goes off after some secondes ..im confuse but i have Hope ..help me thanks

Did you flash the QI5 firmware and then do a factory reset right away from stock recovery like Trex888 said to do?
So it bootloops and then powers off completely by itself after a few seconds?

johnwiz said:
First of all thanks for your reply.. I just flashed the QI5 firmware but the phone is rebooting in to recovery Mode without sucess .. it is just going to recovery and after some fewer second it goes off and on again .. i have tried to install the QE1 but it cant flash it gives me the error on the image below..please assist me solve this problem...Thanks in advance
i taught it was a mother board problem but now that it has flashed the Qi5 firmware i have a Hope ..Help me please
Click to expand...
Click to collapse
Do a wipe data factory reset & wipe cache then reboot system.
If that doesn't work then follow this steps and be patient.
1,downloaf twrp recovery for n910p
2 open odin options and uncheck autoreboot (MUST USE ODIN 3.10 OR HIGHER)
3 choose AP TAB and choose twrp
4,connect device to pc in download mode
5,hit start
6,once twrp flashed remove battery and insert again
7,boot into twrp by 3 button combo
8,go to wipe/advance wipe/choose (dalvic cache+data+system+cache+internal storage) you have to wipe 7 times .
9,now go to odin again and choose AP and choose QI5 firmware.
10,go to odin options and check on "nand eraseall" & "re partition"
11,connect device in download mode & hit start.
Once flashed go to stock recovery and do factory reset.
12,Reboot and wait 10 to 15 min.
Done
TWRP LINK
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar

Trex888 said:
Do a wipe data factory reset & wipe cache then reboot system.
If that doesn't work then follow this steps and be patient.
1,downloaf twrp recovery for n910p
2 open odin options and uncheck autoreboot (MUST USE ODIN 3.10 OR HIGHER)
3 choose AP TAB and choose twrp
4,connect device to pc in download mode
5,hit start
6,once twrp flashed remove battery and insert again
7,boot into twrp by 3 button combo
8,go to wipe/advance wipe/choose (dalvic cache+data+system+cache+internal storage) you have to wipe 7 times .
9,now go to odin again and choose AP and choose QI5 firmware.
10,go to odin options and check on "nand eraseall" & "re partition"
11,connect device in download mode & hit start.
Once flashed go to stock recovery and do factory reset.
12,Reboot and wait 10 to 15 min.
Done
TWRP LINK
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Click to expand...
Click to collapse
THanks ... i will do that right Now and will tell you the result

for anyone not new to rooting , unbricking, stock flashing , twrp , etc ive had this very same problem after nights of screaming and confusion cause i KNOW im doing everything correct .. exact problems as lots have had here .. i replaced my cord with a cheap gas station android cord and borrowed a friends battery that was only a few days old .. and everything worked as it should .. moral of this story .. i assumed my hardware was fine cause independently both worked fine .. but for whatever reason it just wasnt good enough to flash stock FW problem solved .. it only took me a month to come to this amazing discovery (-_-) hope this helps someone ...... SM-N910P