Develop Bugs

[Q] n7100 bricked? Ok dl mode, no recovery

Hello,
I have seen my note2 die in front of my eyes :/ reading a whatsapp the screen turned weird and shutdown, never to live again I fear.
I guess nand corruption? Infact was freezing and rebooting every now and then.
Model is n7100 international version (got it from an italian provider), rooted with samsung galaxy note 2 toolkit.
My flash counter is 1 and I read custom everywhere in the download mode. I'd give this to service centre but I guess I can't like this, right?
Any way of resetting flash counter from download mode? tried stock recovery and rom to no avail
So I can only enter download mode correctly and flash, no booting as stuck at samsung's glowing logo.
Results: tried flashing cwm (tried several versions from the main thread on xda http://forum.xda-developers.com/showthread.php?t=2000138) flashes OK, but does not work entering recovery (I try invoking recovery by turning the phone on, having volume up and home button pressed) but the phone hangs in a loop.
My aim is to: access mounts (extract data from sdcard0, internal), wipe it/delete everything, flash stock rom and recovery.
I can only flash recovery image successfully, the original sammobile rom for n7100 will pass md5 correctly but won't flash in the end
BTW all flashes require a double md5 check and a double pressure of start to go on...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMC3_N7100ITVDMB1_N7100XXDLK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Added!!
<OSM> All threads completed. (succeed 0 / failed 0)
[here I press start again]
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMC3_N7100ITVDMB1_N7100XXDLK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> sboot.bin
<ID:0/013> NAND Write Start!!
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<ID:0/013> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
OTHER try with other sam.updates rom for my device = success in flashing, not in booting.
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDLL4_N7100VFGDLL2_N7100BUDLL1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> boot.img
<ID:0/013> NAND Write Start!!
<ID:0/013> recovery.img
<ID:0/013> system.img
<ID:0/013> modem.bin
<ID:0/013> cache.img
<ID:0/013> hidden.img
<ID:0/013> RQT_CLOSE !!
<ID:0/013> RES OK !!
<ID:0/013> Completed..
<ID:0/013> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/013> Removed!!
I asked krollontrack about data recovery but they do not offer the service on cell phones as results are flaky.
My flash counter is 1 and I read custom everywhere in the download mode. I'd give this to service centre but I guess I can't like this, right?

#G# said:
Hello,
I have seen my note2 die in front of my eyes :/ reading a whatsapp the screen turned weird and shutdown, never to live again I fear.
I guess nand corruption? Infact was freezing and rebooting every now and then.
Model is n7100 international version (got it from an italian provider), rooted with samsung galaxy note 2 toolkit.
So I can only enter download mode correctly and flash, no booting as stuck at samsung's glowing logo.
Results: tried flashing cwm (tried several versions from the main thread on xda http://forum.xda-developers.com/showthread.php?t=2000138) flashes OK, but does not work entering recovery (I try invoking recovery by turning the phone on, having volume up and home button pressed) but the phone hangs in a loop.
My aim is to: access mounts (extract data from sdcard0, internal), wipe it/delete everything, flash stock rom and recovery.
I can only flash recovery image successfully, the original sammobile rom for n7100 will pass md5 correctly but won't flash in the end
BTW all flashes require a double md5 check and a double pressure of start to go on...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMC3_N7100ITVDMB1_N7100XXDLK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Added!!
<OSM> All threads completed. (succeed 0 / failed 0)
[here I press start again]
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMC3_N7100ITVDMB1_N7100XXDLK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> sboot.bin
<ID:0/013> NAND Write Start!!
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<ID:0/013> Added!!
<OSM> All threads completed. (succeed 0 / failed 1
I asked krollontrack about data recovery but they do not offer the service on cell phones as results are flaky.
My flash counter is 1 and I read custom everywhere in the download mode. I'd give this to service centre but I guess I can't like this, right?
Click to expand...
Click to collapse
Just tell Service Center sudden death. They might replaced it for you. I try before.

could it have been cos of your nickname resembling reality?
88sexylady said:
Just tell Service Center sudden death. They might replaced it for you. I try before.
Click to expand...
Click to collapse
Aha! I am thinking about trying, maybe I should send a sexy lady to they guy at the front desk to gain the same attention
Hadn't even thought about flash counters...
Infact if it was possible I'd like to reset flash count from download mode, or... make it so the screen actually stays off )
G

I had this with my SGS 3.
I tried to flash a different framework and got boot loop. Tried flashing a stock rom with odin and once it restarted it would boot loop again and odin would say fail.
I flashed cf root kernel with odin to get CWM and then used Zoots wipe script (mega wipe) to bring it back to bare bones. Then took out the battery and put it back in and 3 button into download mode and then flashed the stock rom again... This time it booted up. There is always hope as long as you can get download mode my friend
Sent from my GT-N7100 using xda premium

and again
and again.
turned off at 2% battery to replace the battery with the spare one.
Waited for full shutdown etc -> boot loop. Shut! Had twrt recovery and could copy data over to the sd (just a couple of things I was missing from the latest backup).
Why? No understanding. Did not dig (formatting dalvik I also accidentally formatted /system and data (...)), yet I am surprised: twice in 12 months.
Great phone for the rest.
Odin showed no mercy for a while... then magically worked, stock sammobile rom.
4.3 rocks and it still records phonecalls, major thing on the main phone for me.

What kind of brick is this?

I've unbricked phones before and even messed with dead EFS partitions and lived to tell the tale, but I cannot for the life of me figure this one out.
Somebody gave me a S4 Mini (GT-I9190) that was bootlooping. I got it into download mode and ODIN flashed a firmware without any problems. When it reboots, it says "Recovery Booting" for a few seconds, then turns off and bootloops again. Download mode continues to work, have flashed many other firmwares, but always the same thing. It just will not boot into recovery.
Tried CWM, TWRP and Philz (all found from various threads on this forum) and all of them seem to flash properly on Odin, but recovery will just not work. I even got a PIT file and repartitioned, to no avail. NAND Erase All with PIT and firmware too makes no difference.
I cannot try the debrick.img advice because the phone is not hardbricked. As far as I can tell, the issue is that the recovery partition is completely borked. But trying to search for ways to restore the recovery partition keeps taking me to the same old threads about how to access recovery mode using buttons and nothing about how to rebuild it!
Any thoughts? Any suggestions on where I should look too are appreciated.
Oh and yeah. to complicate matters a little, I have no idea what firmware version was on it before it died. Samsung Kies tries to initialize with a XSG firmware, so thats the one I downloaded from sammobile. And nope, firmware initialization thru kies also makes no difference at all.

Did you try stock recovery?

As far as I know, it was stock recovery when I got it. Wouldn't boot, so tried the rest. Flashing stock firmware did not make any difference, so don't think stock recovery works either. Have not tried extracting stock recovery from the odin tar and flashing directly though.

karthikrr said:
As far as I know, it was stock recovery when I got it. Wouldn't boot, so tried the rest. Flashing stock firmware did not make any difference, so don't think stock recovery works either. Have not tried extracting stock recovery from the odin tar and flashing directly though.
Click to expand...
Click to collapse
Its been a long time but i would like to know if you were able to fix it, i got exacctly the same problem and i have tried to flash everything on odin they seem to flash ok but booting to recovery i get "no command| error and the phone just reboot, see my odin log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I9195XXUCNJ6_CL3093013_QB2749460_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_I9195XXUCNJ6_CL3093013_QB2749460_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_YER_I9195YERCNJ3_CL3081440_QB2781319_REV01_user_low_ship_MULTI_CERT_.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I9195XXUCNJ6_CL3093013_QB2749460_REV01_user_low_ship_MULTI_CERT_.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl1.mbn
<ID:0/008> sbl2.mbn
<ID:0/008> sbl3.mbn
<ID:0/008> rpm.mbn
<ID:0/008> tz.mbn
<ID:0/008> boot.img
<ID:0/008> persdata.img.ext4
<ID:0/008> persist.img.ext4
<ID:0/008> recovery.img
<ID:0/008> system.img.ext4
<ID:0/008> NON-HLOS.bin
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008> Receive Response from boot-loader
<ID:0/008> cache.img.ext4
<ID:0/008> hidden.img.ext4
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!

Bootloop. NO root, NO custom os, 100% stock

Hey guys,
I'm kinda lost here, I bought this phone a few months ago on a black friday sale in the US.
A few weeks it started bootlooping (the 'preboot logo' kept flashing) it got worse and worse. Remember, I never tried to root, install a custom recovery/OS, nothing!
The only way to get it out of the bootloop was to do a factory reset or sometimes a clear dalvik. But it got worse and worse, and booting into recovery was getting harder and harder...
5 factory resets further, and dozens of dalvik clears, it it bootlooping again!! And it is now impossible to boot into recovery, only download mode.
So I reinstalled the os through odin using these files: https://forum.xda-developers.com/at.../nougat-odin-files-g928a-g928at4eqc6-t3596180
When that didn't work, I used these files: https://forum.xda-developers.com/at...odin-files-g928a-g928aucs4cqa1-build-t3576469
Same bootloop, and still impossible to boot into recovery via power+vol up+home.
You might ask, why don't you repair it under warranty?
Well, I live in france and samsung france refuses to even touch an american device!
Ps: here are the options I had ticked in odin:
1st time: F reset and re-partition
2nd flash: NAND erase, F reset and re-partition
3rd flash: bootloader update, NAND erase, F reset and re-partition
Here is a log, md5 checks included, in case you wonder:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1207)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> param.bin
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> userdata.img
<ID:0/006> modem.bin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006> Receive Response from boot-loader
<ID:0/006> cache.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I would greatly appreciate your help as I'm lost,
Many thanks in advance,
nxss4

I hope you receive a solution to this problem, I'm currently having the same problem and it literally appeared overnight.

massively stuck( no os)

my a3 was having issues, and after a few mistakes i ended up with no os on the phone, TWRP is installed.
Ive tried countless times to flash a stock ROM using odin and im just about ready to pull my hair out.
heres whats on my screen when in download mode:
current binary: samsung official
system status: custom
FRP lock: off
secure download : enabled
CCIC: S2MU004
warranty void: 1 (0x030c)
RP SWREV : B5 K3 S3
this is all the stuff from ODIN:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1401)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 4287 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> param.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and when i try to flash the error on my phone is SW REV. CHECKFAIL (BOOTLOADER) DEVICE 5 BINARY 4
if anyone could help me i would greatly appreciate it, thanks in advance.

Your firmware which you trying installing is latest oreo firmware with all latest secury patches? I had similar issue when my a3 had installed oreo with all updates and i was trying to install older oreo firmware and odin failed everytime. Then i decided to download latest oreo firmware and latest firmware flashed without any issues.

Try latest firmware it will work and donot play with pit just flash firmware bl cp ap and simple scs instead of home scs
---------- Post added at 03:19 PM ---------- Previous post was at 03:14 PM ----------
Try latest firmware it will work and donot play with pit just flash firmware bl cp ap and simple scs instead of home scs

pls help, is my s9 only soft bricked or unsolvable

i got twrp on there and magisk but couldnt log in to my samsung and google accounts, an i read startin odin i had to log out first from them, which i did so i thought i might have missed something so i did it all over and now its bricked.
it started out with getting black screen with a tiny red text that i needed official rom or something like that. and it got that if i tried booting regularly or even trying to boot twrp.
so i currently can only get into download mode and it wont let me flash new twrp or official firmware. i tried flashing recovery, bootloader and other things separate and the all fail so i'm able to enter download mode but cant do anything with odin.
this is my latest odin log, it just stops and i get the error on my phone in red text looking pretty much the same, only thing that seem to change is if it says bootloader or system etc.. the odin log saying it failed doesnt show up until i unplug or exit, and i waited a few hours the first time so i knew it was a done deal before aborting it
i'll add picture of how my download mode looked as it fails and another how it looks if i try starting the phone in any other way, it tells me to use emergency recovery in smart switch for pc but when doing that my phone isnt showing up so i can't do that neither. and that screen only showed up after i tried flashing the new firmware.
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> 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.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 6557 M
<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> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> up_param.bin
<ID:0/004> cm.bin
<ID:0/004> keystorage.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
i got a G960F/DS and restoring it in the beginning i always had an old 2018-2019 security patch running android 9, not sure exact which firmware but the fw zip i tried flashing was called G960FXXU2CRLI_G960FOXM2CRLI_DBT
if that makes any difference. i tried finding something something in a similar time frame as my original one which is why i chose that one.
so please help me solve this

Fixed by @hainguyenthao
Thank you so much

Same issue on my side
JimZiii said:
Fixed by @hainguyenthao
Thank you so much
Click to expand...
Click to collapse
Can you tell me how you have fixed that issue?
Rgds
Bob