Develop Bugs

Accidentally wiped everything in TWRP, "no OS installed" - what are my options?

Accidentally wiped everything in TWRP, "no OS installed" - what are my options?
I rooted my tablet last night and everything went fine, and the next step way to install a custom ROM. So I was attempting to move my download of CleanROM onto my external SD...but I forgot that I have no external SD card! I went into TWRP and wiped internal storage thinking it would be there, and now I get a message saying "No OS Installed are you sure you want to reboot?" whenever i try to exit TWRP.
I am assuming my only option at this point would be to ODIN back to stock? If anyone could tell me exactly how to do this, step by step (and specifically which files I need & where to get them) it would be greatly appreciated because my tablet is a $600 paperweight at this point and I am not too familiar with ODIN.
I also read some things about using something called "ADB" to load a ROM onto the tablet, but again I am not familiar with this at all and I would need to know specifically how to do this. I tried to figure it out with Google but all the instructions seemed too device-specific.

RTbar said:
I rooted my tablet last night and everything went fine, and the next step way to install a custom ROM. So I was attempting to move my download of CleanROM onto my external SD...but I forgot that I have no external SD card! I went into TWRP and wiped internal storage thinking it would be there, and now I get a message saying "No OS Installed are you sure you want to reboot?" whenever i try to exit TWRP.
I am assuming my only option at this point would be to ODIN back to stock? If anyone could tell me exactly how to do this, step by step (and specifically which files I need & where to get them) it would be greatly appreciated because my tablet is a $600 paperweight at this point and I am not too familiar with ODIN.
I also read some things about using something called "ADB" to load a ROM onto the tablet, but again I am not familiar with this at all and I would need to know specifically how to do this. I tried to figure it out with Google but all the instructions seemed too device-specific.
Click to expand...
Click to collapse
Steps to follow :
1. Extract the attached odin 3.09.
2. Download your region rom from here http://samsung-updates.com/device/?id=SM-P600 or if you are looking for US firmware then from here http://www.sammobile.com/firmwares/1/?model=SM-P600&pcode=XAR#firmware.
3. Unzip your firmware.
4. Go into download mode by pressing power + volume down, then volume up.
5. Connect your phone to your PC/Laptop until the com port on the left hand side turns blue.
6. Place your extracted rom in the "AP" bar.
7. Hit "Start"
8. Wait till installation is complete .
You should be good to go .

Thank you so much. Before i go ahead and do this, could you clarify one thing for me? On the firmwares page, it does not specify which one would be for the WiFi, American version which is what I have. Do you know which one i should choose? It does not specify "2014" edition anywhere so i just want to make sure i pick the right one, thanks

RTbar said:
Thank you so much. Before i go ahead and do this, could you clarify one thing for me? On the firmwares page, it does not specify which one would be for the WiFi, American version which is what I have. Do you know which one i should choose? It does not specify "2014" edition anywhere so i just want to make sure i pick the right one, thanks
Click to expand...
Click to collapse
These are all for the 2014 edition, just choose the latest build date Nov. MK1 for the US

RTbar said:
Thank you so much. Before i go ahead and do this, could you clarify one thing for me? On the firmwares page, it does not specify which one would be for the WiFi, American version which is what I have. Do you know which one i should choose? It does not specify "2014" edition anywhere so i just want to make sure i pick the right one, thanks
Click to expand...
Click to collapse
The firmware for USA is Cellular South http://terafile.co/574648641665/P600UEUBMK1_P600XARBMK1_XAR.zip

I think a small couple of small files in "data/media", which holds mostly unimportant stuff, must not get deleted or it's bricktime. Like when i once formatted "data" on my old tablet.

I had this same problem, however I fixed it using adb sideload. You can install it from here. First go to advanced in TWRP and click the ADB option. Then you just need to open cmd, change your directory to where the ROM zip is, then write "adb sideload test.zip" where the quotes are removed and test is the name of your zip which should be something like "CleanROM-2.0-R2.zip"

Thanks for all the help. I was able to get back to stock using Odin and am now rooted running CleanROM. I'll be using that ADB info in the future for sure too.

Dealing with the same issue!
I did this too but this was my result. Note 4 Sprint.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Whats going on?

Fractality said:
I did this too but this was my result. Note 4 Sprint.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Whats going on?
Click to expand...
Click to collapse
It was be not Your model's firmware.
Try appropriate or exclude all except: bootloader, recovery, system & cache

stslam said:
It was be not Your model's firmware.
Try appropriate or exclude all except: bootloader, recovery, system & cache
Click to expand...
Click to collapse
Same thing is happening with me. How I can edit it ?
I tried Winzip and 7Zip but there are errors in Odin...

I'm facing a similar issue but my device is Moto G5s Plus.
The problem I'm facing is that I accidently wiped out the mobile's system completely, and now it does not even have an "internal storage" partition at all (since it shows 0 MB). Hence, I cannot even transfer any files to my mobile because my computer does show the phone detected but no "internal storage exists".
Please help me out..

asim.sidz said:
I'm facing a similar issue but my device is Moto G5s Plus.
The problem I'm facing is that I accidently wiped out the mobile's system completely, and now it does not even have an "internal storage" partition at all (since it shows 0 MB). Hence, I cannot even transfer any files to my mobile because my computer does show the phone detected but no "internal storage exists".
Please help me out..
Click to expand...
Click to collapse
If you have TWRP installed you may be able to flash a custom rom through OTG...
Otherwise you may be in the toilet...

hello ,I have galaxy note 2 Korea version ,model SHV-E250S build no KOT49H.E250SKSUKOH4 ,i try to update lineage os ,but unfortunately formatted OS ,now ohone showing no OS installed ,can someone help ,where to get sock rom for this model. i tried too many roms via TWRP & odin ,but error occured & solution is not there,plz help

Samsung a600fn
I did the same thing now it says no is installed and I don't know what firmware to install because I don't know the name of the file please help

Need guidance
Please tell me somebody still reads this.
So I recently got this tablet. Deleted everything.
Now it says no os installed.
I tried the odin suggestion. But odin keeps crashing on me.
Tried to install a hyperdrive zip though twrp. Just reboots.
It also says no super su installed.
Help. I haven't done this years and have no clue

BoomDiggy said:
Please tell me somebody still reads this.
So I recently got this tablet. Deleted everything.
Now it says no os installed.
I tried the odin suggestion. But odin keeps crashing on me.
Tried to install a hyperdrive zip though twrp. Just reboots.
It also says no super su installed.
Help. I haven't done this years and have no clue
Click to expand...
Click to collapse
I would try a different version of Odin Also make sure you have the correct tablet ROM, try getting yourself back to stock before other ROMS.

louvass said:
I would try a different version of Odin Also make sure you have the correct tablet ROM, try getting yourself back to stock before other ROMS.
Click to expand...
Click to collapse
Yes, and run Odin as admin (I'm an active user)

louvass said:
I would try a different version of Odin Also make sure you have the correct tablet ROM, try getting yourself back to stock before other ROMS.
Click to expand...
Click to collapse
Ty for replying.
I think I have the correct firmware file from sammobile. EUR-P600XXSDRI1-20190117145157.zip
I also noticed that the tablet says that there is no root. But I have trwp.

i accidentali wiped everything in TWRP ON MY REALME 3 PRO... now stuck in bootloader with twrp working.....

No Pit partition Problem

Hi every one any help will be greatlly apreciated. First what happened we'll shut down and stuck at Galaxy Note II Screen and restarting itself until it stops frozen at the Galaxy Note II Screen. Was working fine for a couple months after my last flash froze some times but battery pull fixed it before. Now I can not get into CWM Recovery So I tried flashing factory rom with Odin I get this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried mutiple times tried F.Reset Time checked. Any Ideas guy's. wife's phone have to get it working if you know what I meen. Thank's for any help. Hope the nands not corupt. Had a International S3 I9300 with that problem. Would like to save this and not shell out the money for a MBoard.

kennethcolman said:
Hi every one any help will be greatlly apreciated. First what happened we'll shut down and stuck at Galaxy Note II Screen and restarting itself until it stops frozen at the Galaxy Note II Screen. Was working fine for a couple months after my last flash froze some times but battery pull fixed it before. Now I can not get into CWM Recovery So I tried flashing factory rom with Odin I get this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried mutiple times tried F.Reset Time checked. Any Ideas guy's. wife's phone have to get it working if you know what I meen. Thank's for any help. Hope the nands not corupt. Had a International S3 I9300 with that problem. Would like to save this and not shell out the money for a MBoard.
Click to expand...
Click to collapse
in download mode does it say n7100 in product code?
what you need to do if you will be using a pit file is use a factory emergency rom. sadly most the links are down.
i have a MJ9 Emergency rom from india which is 4.3. i will try upload it when i get home in 8 to 9 hours to mega.nz if that is ok.
what i have done is replaced the MJ9 bootloader with MJ5 in that firmware.
if you can't wait, you need a firmware that has BL,AP, CP and CSC all split so you can put them in all the boxes. if i get a chance at lunch i might try find a pre uploaded link for you. just remain calm and don't start flashing stuff randomly

I have searched and searched online and cant seem to nail down a solution to this issue.
My Download Screen displays:
ODIN MODE
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
I hope that my Note II is not bricked. I have tried 100's of times with stock, custom recovery's, CWM, I get some kind of error no matter what I do.
my Sammy just doesn't want to work with me.
I hope that we can put together a solution.

El_Nino9 said:
in download mode does it say n7100 in product code?
what you need to do if you will be using a pit file is use a factory emergency rom. sadly most the links are down.
i have a MJ9 Emergency rom from india which is 4.3. i will try upload it when i get home in 8 to 9 hours to mega.nz if that is ok.
what i have done is replaced the MJ9 bootloader with MJ5 in that firmware.
if you can't wait, you need a firmware that has BL,AP, CP and CSC all split so you can put them in all the boxes. if i get a chance at lunch i might try find a pre uploaded link for you. just remain calm and don't start flashing stuff randomly
Click to expand...
Click to collapse
Thanks I am very patient. Oh and yes it says GT-N7100 in product code under warranty bit: 1 binary:yes status: custom under binary download: Yes (6 counts)

Teckin said:
I have searched and searched online and cant seem to nail down a solution to this issue.
My Download Screen displays:
ODIN MODE
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
I hope that my Note II is not bricked. I have tried 100's of times with stock, custom recovery's, CWM, I get some kind of error no matter what I do.
my Sammy just doesn't want to work with me.
I hope that we can put together a solution.
Click to expand...
Click to collapse
kennethcolman said:
Thanks I am very patient. Oh and yes it says GT-N7100 in product code under warranty bit: 1 binary:yes status: custom under binary download: Yes (6 counts)
Click to expand...
Click to collapse
to both you guys:- what bootloader are you on/were you on? Kenneth I think you've taken your bootloader above MJ5 as you say your warranty bit is 1. you can't downgrade bootloader at all! flashing the MJ5 bootloader with the file I've uploaded won't help. you will only get FAIL in odin. you need to tell me which bootloader you've been to so I can try arrange a package for you if I can.
Teckin, I need you to answer the above too

El_Nino9 said:
to both you guys:- what bootloader are you on/were you on? Kenneth I think you've taken your bootloader above MJ5 as you say your warranty bit is 1. you can't downgrade bootloader at all! flashing the MJ5 bootloader with the file I've uploaded won't help. you will only get FAIL in odin. you need to tell me which bootloader you've been to so I can try arrange a package for you if I can.
Teckin, I need you to answer the above too
Click to expand...
Click to collapse
First off thanks for your help. Here's the deal I had this installed: DN3_v3.2_by_E-Team_(Vegeta_Edition) Thats a Jelly Bean for the past 2 month's so what ever bootloader works with that is what it had. I was tying to flash an OEM KK: BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar I figured we'll since I have this problem let me flash DN5 but in oder to do this I would have to upgrade my bootloader KK that's why I flashed this BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar Now I say again The problem was not a result of flashing. My wife was using Skype while on the DN3 and it froze she pushed the wake button once or twice it went black and then gave the reboot logo that I mentioned above. So then I proceeded to try to flash to fix and upgrade in the process. And it gave me the odin results above No PIT Partition

https://mega.co.nz/#!5ZlXFbrR!GoNuuuDwKrp3QG8X7p4eV5v5ViOZR51kXgTtcptkGBo
here's the file I've uploaded.
you may well still have taken the device to MJ5 only.
flash all files in here at the same time using odin. let me know how you get on?
I find this method works best for me:
phone is off, load odin, load all the files in, pit, bl, ap, cp, csc no messing around with any ticking other boxes. AP will probably cuase odin to crash for a few seconds when loading just let it do its thing.
then put phone into download mode( I put battery in hold down, menu and power) if the drivers have been installed using that port previous it finds the device in odin instantly and i start the process.
If your flash is successful but doesn't load rom, your data might need to be wiped. i mean if your device is has been stuck on a Samsung screen for 10 minutes after odin said everythings fine don't panic. take battery out, go into recovery (volume up+menu+power) and then wipe data. it should now load the rom.

El_Nino9 said:
https://mega.co.nz/#!5ZlXFbrR!GoNuuuDwKrp3QG8X7p4eV5v5ViOZR51kXgTtcptkGBo
here's the file I've uploaded.
you may well still have taken the device to MJ5 only.
flash all files in here at the same time using odin. let me know how you get on?
I find this method works best for me:
phone is off, load odin, load all the files in, pit, bl, ap, cp, csc no messing around with any ticking other boxes. AP will probably cuase odin to crash for a few seconds when loading just let it do its thing.
then put phone into download mode( I put battery in hold down, menu and power) if the drivers have been installed using that port previous it finds the device in odin instantly and i start the process.
If your flash is successful but doesn't load rom, your data might need to be wiped. i mean if your device is has been stuck on a Samsung screen for 10 minutes after odin said everythings fine don't panic. take battery out, go into recovery (volume up+menu+power) and then wipe data. it should now load the rom.
Click to expand...
Click to collapse
Thanks but no prize.
Download and tried it Failed
Odin Said this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.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> CP_N7100DDEMJ9_REV08_CL1423182.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_ODD_N7100ODDEMK1_2099172_REV04_user_low_ship.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_N7100XXUEMK4_2099172_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Do you think I should check erase nand I won't do it till some body who I trust tells me I should don't want things worse.

Ok so here is the deal on my GT-N7100. I bought it this way, but have not been able to flash it back to stock to start from scratch. so to answer your question, I have NO CLUE.
Seller told me that It would only boot into dl screen with usb...So I thought hmm I can re-flash it with stock software and move forward from that point.
Thank you all for the suggestions!

Teckin said:
Ok so here is the deal on my GT-N7100. I bought it this way, but have not been able to flash it back to stock to start from scratch. so to answer your question, I have NO CLUE.
Seller told me that It would only boot into dl screen with usb...So I thought hmm I can re-flash it with stock software and move forward from that point.
Thank you all for the suggestions!
Click to expand...
Click to collapse
you can try the above files if you want.
kennethcolman said:
Thanks but no prize.
Download and tried it Failed
Odin Said this:
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Do you think I should check erase nand I won't do it till some body who I trust tells me I should don't want things worse.
Click to expand...
Click to collapse
don't click erase.
mate i think you've flashed a new bootloader than MJ5 hence why it fails at that stage.
i am checking to see if i can get hold of a kitkat rom for you that's split to so you can flash pit.
i have never tried it with kitkat mate. plus i don't use odin to flash anymore. i use my octoplus box so files are in a .oct format
Sorry for delay in replying.
again i think youhave a newer bootlaoder if it shows warranty bit.

El_Nino9 said:
you can try the above files if you want.
don't click erase.
mate i think you've flashed a new bootloader than MJ5 hence why it fails at that stage.
i am checking to see if i can get hold of a kitkat rom for you that's split to so you can flash pit.
i have never tried it with kitkat mate. plus i don't use odin to flash anymore. i use my octoplus box so files are in a .oct format
Sorry for delay in replying.
again i think youhave a newer bootlaoder if it shows warranty bit.
Click to expand...
Click to collapse
I have a buddy who has a box would that be the safest rout?

kennethcolman said:
I have a buddy who has a box would that be the safest rout?
Click to expand...
Click to collapse
i dont think it makes a difference to be honest as i think it just uses the same type of way to push it.
i have a silly question to ask you.
what happens if you flash http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n7100//philz_touch_6.41.6-n7100.tar.md5
in ap only without pit ofcourse.
does odin allow you to do this?

El_Nino9 said:
i dont think it makes a difference to be honest as i think it just uses the same type of way to push it.
i have a silly question to ask you.
what happens if you flash http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n7100//philz_touch_6.41.6-n7100.tar.md5
in ap only without pit ofcourse.
does odin allow you to do this?
Click to expand...
Click to collapse
I believe I tried that same thing happened. Fail no pit partition

kennethcolman said:
I believe I tried that same thing happened. Fail no pit partition
Click to expand...
Click to collapse
what box has your mate got?
check this thread out if he has a z3x (wish i had got that instead of octoplus)
http://forum.xda-developers.com/galaxy-s3/general/samsung-s3-i9300-note2-n7100-i9500-s4-t2647558
i have found PIT_N7100XXUENA1_N7100OJVENA1_N7100XXUENA3_Taiwan_Android_4.3
which includes all the files an oct file. if your mate has another box he might be able to find something similar along the lines?

I tried that file as well. Still same issue. I did talk with a guy that does jtag services and he advised me that it's either the eMMC or motherboard issue. He wants to sell me a eMMC Flash service for $75.00. What do you guys think I should do....
---------- Post added at 10:32 PM ---------- Previous post was at 09:51 PM ----------
El_Nino9 said:
i dont think it makes a difference to be honest as i think it just uses the same type of way to push it.
i have a silly question to ask you.
what happens if you flash "goo.im/devs/philz_touch/CWM_Advanced_Edition/n7100//philz_touch_6.41.6-n7100.tar.md5"
in ap only without pit ofcourse.
does odin allow you to do this?
Click to expand...
Click to collapse
I will try this as well..

Did try that last file as well still no go...
Thank you all for your efforts.

El_Nino9 said:
what box has your mate got?
check this thread out if he has a z3x (wish i had got that instead of octoplus)
http://forum.xda-developers.com/galaxy-s3/general/samsung-s3-i9300-note2-n7100-i9500-s4-t2647558
i have found PIT_N7100XXUENA1_N7100OJVENA1_N7100XXUENA3_Taiwan_Android_4.3
which includes all the files an oct file. if your mate has another box he might be able to find something similar along the lines?
Click to expand...
Click to collapse
We're you able to find the KK files for the N7100 odin flashable? and a little off topic here but I have been dabbling with the idea of unlocking cells. I live in the Dominican Republic and cells here are mostly GSM wondering if you we're to purchase 3 box's to do the widest range of phones which 3 would you buy and from where? Sorry everybody for the off topic.

El_Nino9 said:
what box has your mate got?
check this thread out if he has a z3x (wish i had got that instead of octoplus)
http://forum.xda-developers.com/galaxy-s3/general/samsung-s3-i9300-note2-n7100-i9500-s4-t2647558
i have found PIT_N7100XXUENA1_N7100OJVENA1_N7100XXUENA3_Taiwan_Android_4.3
which includes all the files an oct file. if your mate has another box he might be able to find something similar along the lines?
Click to expand...
Click to collapse
I beleve I figured out why the Rescue Firmware you sent me didn't work. What I need is Android 4.3 MK9 Bootloader and Do you have this and if so can you upload it to me mega would be fine. Thanks Just like the other just MK9 Based with pit and etc. Thanks for all your earlier help I am pretty sure this wil work.

kennethcolman said:
I beleve I figured out why the Rescue Firmware you sent me didn't work. What I need is Android 4.3 MK9 Bootloader and Do you have this and if so can you upload it to me mega would be fine. Thanks Just like the other just MK9 Based with pit and etc. Thanks for all your earlier help I am pretty sure this wil work.
Click to expand...
Click to collapse
sorry for the lack of activity. deadlines for work have kept me away from here.
i have a MK4. i will send it to you now. i will hunt for MK9 in the mean time if MK4 fails. plus i'll answer your other question about boxes in few minutes.

Teckin said:
I tried that file as well. Still same issue. I did talk with a guy that does jtag services and he advised me that it's either the eMMC or motherboard issue. He wants to sell me a eMMC Flash service for $75.00. What do you guys think I should do....
---------- Post added at 10:32 PM ---------- Previous post was at 09:51 PM ----------
I will try this as well..
Click to expand...
Click to collapse
that's note a bad price for the service i'd say. they have to use a rework station to pull the emmc off and then reball the new one on. however i'd suggest you try flashing a new firmware on first. i will try to dig a new firmware out for you to try but if they keep failing then the only route is emmc and make sure they load a firmware below 4.3 knox free if you want custom roms again

[Q] Note 2 doesn't start anymore

Hi there,
I hope that somebody can help me.
My Galaxy Note 2 stopped working all of the sudden. It was running without any problems when it suddenly restarted without a reason. Since then it does not boot anymore, any attempt ends on the screen where it shows "Samsung Galaxy Note II GT-N7100". The only chance to switch it off after this is removing the battery. The phone was not rooted, it was running stock Android 4.3 before the crash.
Pressing Home and Volume-up during power-on doesn't show the menu so I'm not able to do a factory reset. Instead it shows the android robot and the text "Downloading... Do not turn off target!!"
I was hoping to have a chance to get a copy of the data of the internal memory so I followed the instructions to install the "Heimdall suite". When I start the phone in download mode (or what's left of it) I get the following responses to Heimdall commands:
Code:
C:\Note-2\Heimdall Suite>heimdall detect
Device detected
Code:
C:\Note-2\Heimdall Suite>heimdall print-pit
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
To make sure my setup is correct I've tested it with with a working Galaxy S3 which doesn't give me the error messages after the second command.
Is there any way to get access to the data that is stored on the internal memory?
The phone is still under warranty so if there is a way to get access I'd prefer one that doesn't void the warranty...
Thank you very much for any hint!
Regards -- Markus

Battery buy a new one... I had the same prob awhile back Connected to the charger it would fully boot but as soon as you pull the cable it will power off then be stuck at Samsung logo till you pull the battery.
I borrowed a battery to test and sure enough and then ordered one.
mjakobi said:
Hi there,
I hope that somebody can help me.
My Galaxy Note 2 stopped working all of the sudden. It was running without any problems when it suddenly restarted without a reason. Since then it does not boot anymore, any attempt ends on the screen where it shows "Samsung Galaxy Note II GT-N7100". The only chance to switch it off after this is removing the battery. The phone was not rooted, it was running stock Android 4.3 before the crash.
Pressing Home and Volume-up during power-on doesn't show the menu so I'm not able to do a factory reset. Instead it shows the android robot and the text "Downloading... Do not turn off target!!"
I was hoping to have a chance to get a copy of the data of the internal memory so I followed the instructions to install the "Heimdall suite". When I start the phone in download mode (or what's left of it) I get the following responses to Heimdall commands:
Code:
C:\Note-2\Heimdall Suite>heimdall detect
Device detected
Code:
C:\Note-2\Heimdall Suite>heimdall print-pit
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
To make sure my setup is correct I've tested it with with a working Galaxy S3 which doesn't give me the error messages after the second command.
Is there any way to get access to the data that is stored on the internal memory?
The phone is still under warranty so if there is a way to get access I'd prefer one that doesn't void the warranty...
Thank you very much for any hint!
Regards -- Markus
Click to expand...
Click to collapse

Joshua79 said:
Battery buy a new one... I had the same prob awhile back Connected to the charger it would fully boot but as soon as you pull the cable it will power off then be stuck at Samsung logo till you pull the battery.
Click to expand...
Click to collapse
Hi Joshua79,
thanks for your reply. The phone doesn't even if it's connected to the charger...
Any other hints?
Still looking for a way to access the internal storage of the phone...
Cheers -- Markus

hi,
i also have similar problem with my N7100.
phone stuck in Samsung GT-N7100 logo.
unable to go to Recovery Mode, but download mode OK.
tried to flash Stock Firmware with Odin, but failed
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNI4_N7100OLBFNI1_N7100DXUFNI1_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> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
tried to flash PhilZ Touch 6 Recovery, but failed. :crying:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.48.4-n7100.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> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tried swap battery with friends, friends phone work well with my battery, but mine still the same even with my friends battery.
from the log, it seem like Odin unable to write. anyone know whats the problem?
tried looking for help from [GUIDE][Troubleshoot a failed ODIN flash] and similiar problem also reported here, but seem like no solution :crying:
please help, I'm too broke to get new phone :crying:

mjakobi said:
Hi there,
I hope that somebody can help me.
My Galaxy Note 2 stopped working all of the sudden. It was running without any problems when it suddenly restarted without a reason. Since then it does not boot anymore, any attempt ends on the screen where it shows "Samsung Galaxy Note II GT-N7100". The only chance to switch it off after this is removing the battery. The phone was not rooted, it was running stock Android 4.3 before the crash.
Pressing Home and Volume-up during power-on doesn't show the menu so I'm not able to do a factory reset. Instead it shows the android robot and the text "Downloading... Do not turn off target!!"
I was hoping to have a chance to get a copy of the data of the internal memory so I followed the instructions to install the "Heimdall suite". When I start the phone in download mode (or what's left of it) I get the following responses to Heimdall commands:
Code:
C:\Note-2\Heimdall Suite>heimdall detect
Device detected
Code:
C:\Note-2\Heimdall Suite>heimdall print-pit
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
To make sure my setup is correct I've tested it with with a working Galaxy S3 which doesn't give me the error messages after the second command.
Is there any way to get access to the data that is stored on the internal memory?
The phone is still under warranty so if there is a way to get access I'd prefer one that doesn't void the warranty...
Thank you very much for any hint!
Regards -- Markus
Click to expand...
Click to collapse
It's been a long time since I dealt with a Note 2 (since mine broke), but I'll try to help.
That sounds like a corrupted .pit file. You'll have to research more on your own, but I think you'll have to flash a new .pit file, then flash the stock ROM.
P.S. If you have a warranty, why don't you use it? lol.
thongkh said:
hi,
i also have similar problem with my N7100.
phone stuck in Samsung GT-N7100 logo.
unable to go to Recovery Mode, but download mode OK.
tried to flash Stock Firmware with Odin, but failed
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNI4_N7100OLBFNI1_N7100DXUFNI1_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> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
tried to flash PhilZ Touch 6 Recovery, but failed. :crying:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.48.4-n7100.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> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tried swap battery with friends, friends phone work well with my battery, but mine still the same even with my friends battery.
from the log, it seem like Odin unable to write. anyone know whats the problem?
tried looking for help from [GUIDE][Troubleshoot a failed ODIN flash] and similiar problem also reported here, but seem like no solution :crying:
please help, I'm too broke to get new phone :crying:
Click to expand...
Click to collapse
Seems like a similar issue as the guy above. Your download isn't corrupted based on the successful MD5 check. I'll try and research more into your issue.
P.S. You rooted? Any modifications?
Just for you from a Find 7a
#stayparanoid from Singapore
Do click the "Thanks" button if I helped!

Irwenzhao said:
It's been a long time since I dealt with a Note 2 (since mine broke), but I'll try to help.
That sounds like a corrupted .pit file. You'll have to research more on your own, but I think you'll have to flash a new .pit file, then flash the stock ROM.
P.S. If you have a warranty, why don't you use it? lol.
Click to expand...
Click to collapse
Hello Irwenzhao,
thanks for replying.
I haven't rooted my phone yet and so I'm not familiar with flashing, so please excuse my questions. I've read pretty much about flashing in the last few days and (as far as I've understood) flashing things to my phone will erase my data from the phone.
My problem is that I've accidentally stored data on the internal memory instead of the external SD-card . SInce I didn't realize that before the crash there's some stuff on the phone I'd like to have back if this is possible.
Of course I will use the warranty to have the phone repaired but my data will most likely be gone from the phone when I get it back.
That's the reason why I'm trying to find out if there's a way to access the internal memory of my phone before having it repaired.
Cheers -- Markus

mjakobi said:
Hello Irwenzhao,
thanks for replying.
I haven't rooted my phone yet and so I'm not familiar with flashing, so please excuse my questions. I've read pretty much about flashing in the last few days and (as far as I've understood) flashing things to my phone will erase my data from the phone.
My problem is that I've accidentally stored data on the internal memory instead of the external SD-card . SInce I didn't realize that before the crash there's some stuff on the phone I'd like to have back if this is possible.
Of course I will use the warranty to have the phone repaired but my data will most likely be gone from the phone when I get it back.
That's the reason why I'm trying to find out if there's a way to access the internal memory of my phone before having it repaired.
Cheers -- Markus
Click to expand...
Click to collapse
Your data should be (probably) gone. I highly doubt the possibility that a method to access your internal storage exists. It could be just a bad motherboard. Just let the Samsung Service Centre folks do their job, nothing much you can do.
P.S. your files may already be gone. (unfortunately)
Just for you from a Find 7a
#stayparanoid from Singapore
Do click the "Thanks" button if I helped!

Irwenzhao said:
Your data should be (probably) gone. I highly doubt the possibility that a method to access your internal storage exists. It could be just a bad motherboard. Just let the Samsung Service Centre folks do their job, nothing much you can do.
P.S. your files may already be gone. (unfortunately)
Just for you from a Find 7a
#stayparanoid from Singapore
Do click the "Thanks" button if I helped!
Click to expand...
Click to collapse
I don't need my data, and my phone was not rooted. Stock kitkat firmware.
U mention is motherboard failure? My phone no longer got warranty cover. Pls tell me it's not hardware failure

thongkh said:
I don't need my data, and my phone was not rooted. Stock kitkat firmware.
U mention is motherboard failure? My phone no longer got warranty cover. Pls tell me it's not hardware failure
Click to expand...
Click to collapse
Have you tried updating via Kies?
Just for you from a Find 7a
#stayparanoid from Singapore
Do click the "Thanks" button if I helped!

Irwenzhao said:
Have you tried updating via Kies?
Just for you from a Find 7a
#stayparanoid from Singapore
Do click the "Thanks" button if I helped!
Click to expand...
Click to collapse
thanks for the reply.
tried with kies (v2.6.3.14074_11), its said device not responding :crying:
anymore suggestion?

thongkh said:
thanks for the reply.
tried with kies (v2.6.3.14074_11), its said device not responding :crying:
anymore suggestion?
Click to expand...
Click to collapse
What was your Android version before this happened?
Sent from a Nameless fellow licking Lollipop.
Singaporean Oppo Find 7a
Click that "Thanks" button if I helped you!

Irwenzhao said:
What was your Android version before this happened?
Sent from a Nameless fellow licking Lollipop.
Singaporean Oppo Find 7a
Click that "Thanks" button if I helped you!
Click to expand...
Click to collapse
didnt really checked, but should be kidkat

thongkh said:
didnt really checked, but should be kidkat
Click to expand...
Click to collapse
Not sure if you can flash a .pit file with Knox, but you can try. Search it up on Google.
Sent from a Nameless fellow licking Lollipop.
Singaporean Oppo Find 7a
Click that "Thanks" button if I helped you!

there is a pit file here for N7100 16gb
http://forum.xda-developers.com/showthread.php?t=1927983
extract it and flash in odin. that's the file i used when i messed up with my partition and my phone doesn't boot.

this is the exact problem we had last month with our note 2, working fine then bang.
I tried everything but was unable to revive the machine.
Samsung repaired the phone under warranty even though it was over two years old, a new mainboard was fitted as the emmc chip had failed.
Give them a call you have nothing to lose at this point, our phone was gone for a total of 3 working days.

Odin Fails with eMMC write fail error.

Hello everyone.
I just purchased a Sprint Note 4 (SM-n910P) that has Android 5.1.1 currently installed. While I know there is no current chainfire autoroot for this version of android, I was planning on downloading to 5.0.1 using the ROM file from SamMobile that I downloaded. So I enabled developer mode, enabled USB debugging, and used Odin to flash and downgrade to 5.0.1. I used vol down, Power, and Home to go into the Odin Mode on the phone, plugged it into a Windows 10 PC using Odin 3.10.6. Odin recognizes the com port and I load up the correct .tar.md5 file. I press start and immediately receive a FAIL inside of Odin. This is on the Odin screen:
<OSM> N910PVPU3BOF5_N910PSPT3BOF5_N910PVPU3BOF5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<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> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
While on the phone I receive the following:
SW REV CHECK FAIL : [about]Fused 4 > Binary 3
[1] eMMC write fail: ABOUT
Can anyone tell me what I am doing wrong? I am experienced at rooting and flashing roms on my HTC Evo 4G and my Note 2 which I've had for a combined 5+ years. I've tried Odin 3.07, 3.10, older Samsung USB Cable, newer USB cable. I have Kies installed with the latest USB drivers installed.
Is this an issue with my computer or with the phone itself? After it fails numerous times I'm able to reboot the phone back into the normal settings and continue using it as if nothing happened. CAN I downgrade this to 4.4.4 through 5.0.1 if I choose too? Or does 5.1.1 somehow magically prevent all of that from happening? Advice? Comments? Suggestions??
Thanks!

Downgrade !
bawalker said:
Hello everyone.
I just purchased a Sprint Note 4 (SM-n910P) that has Android 5.1.1 currently installed. While I know there is no current chainfire autoroot for this version of android, I was planning on downloading to 5.0.1 using the ROM file from SamMobile that I downloaded. So I enabled developer mode, enabled USB debugging, and used Odin to flash and downgrade to 5.0.1. I used vol down, Power, and Home to go into the Odin Mode on the phone, plugged it into a Windows 10 PC using Odin 3.10.6. Odin recognizes the com port and I load up the correct .tar.md5 file. I press start and immediately receive a FAIL inside of Odin. This is on the Odin screen:
<OSM> N910PVPU3BOF5_N910PSPT3BOF5_N910PVPU3BOF5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<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> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
While on the phone I receive the following:
SW REV CHECK FAIL : [about]Fused 4 > Binary 3
[1] eMMC write fail: ABOUT
Can anyone tell me what I am doing wrong? I am experienced at rooting and flashing roms on my HTC Evo 4G and my Note 2 which I've had for a combined 5+ years. I've tried Odin 3.07, 3.10, older Samsung USB Cable, newer USB cable. I have Kies installed with the latest USB drivers installed.
Is this an issue with my computer or with the phone itself? After it fails numerous times I'm able to reboot the phone back into the normal settings and continue using it as if nothing happened. CAN I downgrade this to 4.4.4 through 5.0.1 if I choose too? Or does 5.1.1 somehow magically prevent all of that from happening? Advice? Comments? Suggestions??
Thanks!
Click to expand...
Click to collapse
You cant downgrade when on android 5.1.1 og5, seems to be the trending thing nowadays, so if your on 5.1.1 your stuck, we have root, roms, and xposed is working. Good luck on your quest!

Iceburn1 said:
You cant downgrade when on android 5.1.1 og5, seems to be the trending thing nowadays, so if your on 5.1.1 your stuck, we have root, roms, and xposed is working. Good luck on your quest!
Click to expand...
Click to collapse
Well that just totally sucks. I was hoping to get down to 5.0.1 to use chainfire root. The Beastmode root kernel patch seems to have slowness and lag issues introduced after installing that kernel patch which I really wanted to avoid.
I used to do roms and such back earlier on in my smart phone days, but I've found Stock to be best, even with touchwhiz. When I root I just want root access, maybe twrp, but even that's not a requirement as the only things I use are wifi tether when on job sites and titanium backup to freeze things like knox, remove bloatware, etc. That's all I ever use root for. So I'm kinda bummed right now over not downgrading. What is Samsung thinking?!

@bawalker,
You'll need to use the correct root method found in post below. Also, refer to OP of that thread to understand the reasons; OG5 update blocked root at kernel level. And bootloader blocks downgrade to lower versions.
http://forum.xda-developers.com/showthread.php?p=62241991
Flash TWRP then try the Beastmode kernel and SuperSU zip in recovery with cache and dalvik-cache wipe. If it doesn't boot, you may need the OG5 stock tar and start over.
Sent from my SM-N910P using Tapatalk

samep said:
@bawalker,
You'll need to use the correct root method found in post below. Also, refer to OP of that thread to understand the reasons; OG5 update blocked root at kernel level. And bootloader blocks downgrade to lower versions.
http://forum.xda-developers.com/showthread.php?p=62241991
Flash TWRP then try the Beastmode kernel and SuperSU zip in recovery with cache and dalvik-cache wipe. If it doesn't boot, you may need the OG5 stock tar and start over.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks for that link, I read that last night in passing. I've also still be reading that those who do this root method and after adding the line to the bottom of the build.prop file still experience lag and in some cases, some complained it was severe. If I'm going to have performance issues with a phone I use for my business every day then I'm hesitant of even doing it. Esp after seeing that using Odin to put a 5.1.1 tar.md5 rom back on isn't working right.

Kernel+Rom
bawalker said:
Thanks for that link, I read that last night in passing. I've also still be reading that those who do this root method and after adding the line to the bottom of the build.prop file still experience lag and in some cases, some complained it was severe. If I'm going to have performance issues with a phone I use for my business every day then I'm hesitant of even doing it. Esp after seeing that using Odin to put a 5.1.1 tar.md5 rom back on isn't working right.
Click to expand...
Click to collapse
Im using stock rom Hybrid 3.0...http://forum.xda-developers.com/note-4-sprint/development/rom-t2956667....with emotion kernel.....http://emotroid.com/touchwiz-kernel/, use app called Synapse to control kernel, link is below emotion kernel to playstore. You said you liked stock, and this will give you that and the emotion kernel is great, no lag for me at all, use synapse to fine tune it.

I have n910f , i try to flash it but always get odin fails
Any solution to repair it

hbs131415 said:
I have n910f , i try to flash it but always get odin fails
Any solution to repair it
Click to expand...
Click to collapse
Lots of reasons for Odin to fail. Some can be easily remedied but others aren't so easy. Could you post the full Odin log and include the screenshot of phone display or describe fully as the OP did in post 1?
Sent from my SM-N910P using Tapatalk

samep said:
Lots of reasons for Odin to fail. Some can be easily remedied but others aren't so easy. Could you post the full Odin log and include the screenshot of phone display or describe fully as the OP did in post 1?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
<ID:0/028> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N910FXXU1ANK4_CL3311829_QB3005660_REV00_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> CP_N910FXXU1ANK4_REV00_CL_1795169.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_OXA_N910FOXA1ANK4_CL3311829_QB3005660_REV00_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_N910FXXU1ANK4_CL3311829_QB3005660_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/028> Odin engine v(ID:3.1005)..
<ID:0/028> File analysis..
<ID:0/028> SetupConnection..
<ID:0/028> Initialzation..
<ID:0/028> Set PIT file..
<ID:0/028> DO NOT TURN OFF TARGET!!
<ID:0/028> Get PIT for mapping..
<ID:0/028> Firmware update start..
<ID:0/028> SingleDownload.
<ID:0/028> aboot.mbn
<ID:0/028> NAND Write Start!!
<ID:0/028> sbl1.mbn
<ID:0/028> rpm.mbn
<ID:0/028> tz.mbn
<ID:0/028> sdi.mbn
<ID:0/028> NON-HLOS.bin
<ID:0/028> boot.img
<ID:0/028> FAIL! (Write)
<ID:0/028>
<ID:0/028> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

hbs131415 said:
<ID:0/028> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N910FXXU1ANK4_CL3311829_QB3005660_REV00_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> CP_N910FXXU1ANK4_REV00_CL_1795169.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_OXA_N910FOXA1ANK4_CL3311829_QB3005660_REV00_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_N910FXXU1ANK4_CL3311829_QB3005660_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/028> Odin engine v(ID:3.1005)..
<ID:0/028> File analysis..
<ID:0/028> SetupConnection..
<ID:0/028> Initialzation..
<ID:0/028> Set PIT file..
<ID:0/028> DO NOT TURN OFF TARGET!!
<ID:0/028> Get PIT for mapping..
<ID:0/028> Firmware update start..
<ID:0/028> SingleDownload.
<ID:0/028> aboot.mbn
<ID:0/028> NAND Write Start!!
<ID:0/028> sbl1.mbn
<ID:0/028> rpm.mbn
<ID:0/028> tz.mbn
<ID:0/028> sdi.mbn
<ID:0/028> NON-HLOS.bin
<ID:0/028> boot.img
<ID:0/028> FAIL! (Write)
<ID:0/028>
<ID:0/028> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
And what does your phone display indicate when you get this failure?
Just an observation, I think you're trying to Odin KitKat which may not be possible in Odin if you've updated to Lollipop 5.1 Other 5.0 stock tars attempted may also get blocked to downgrade of bootloader as well like my SM-N910P will. My phone won't get as far as yours did when Odin of KitKat or Android 5.0 stock tar is attempted so that may not be the issue; maybe you haven't had that phone upgraded beyond beyond Android 5.0 yet?
If you had updated to Android 5.1 or higher, you might consider trying a newer stock tar, 5.1 or higher.
They're may be a more logical reason given on your screen at time of failure.
Sent from my SM-N910P using Tapatalk

here the message in the phone
here screenshoot

samep said:
@bawalker,
You'll need to use the correct root method found in post below. Also, refer to OP of that thread to understand the reasons; OG5 update blocked root at kernel level. And bootloader blocks downgrade to lower versions.
http://forum.xda-developers.com/showthread.php?p=62241991
Flash TWRP then try the Beastmode kernel and SuperSU zip in recovery with cache and dalvik-cache wipe. If it doesn't boot, you may need the OG5 stock tar and start over.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Out of curiosity? Keep getting conflicting. Does this device have a bad hostory of emmc failures. I got one doing it. But this things seems to have loads of weird issues. I will get some logs together tonight when i get. Home. Im goi. To try to flash latest mm firmware tonight. When i try to start up anything other than dl mode. I get the connect to kies. The fiwmware update went wrong select emency recovery. Kies 3 doesnt work for this device or it says it dont. And i get a side by side configuration error when installing older odin. Got windows 10

hbs131415 said:
here the message in the phone
here screenshoot
Click to expand...
Click to collapse
That's not good but I'm still not sure if you can flash that KitKat stock tar or not.
If you've had updates greater than Android 5.0 on that phone, I'd suggest not trying to flash that anymore. If that applies, try the latest stock tar.
The eMMC write error could be component failure but I'm thinking it could also be refusing to downgrade the bootloader to a less secure one which would apply if the phone is currently on a higher bootloader. Could you get the bootloader version by running this app?
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
You can use Galaxy Tools if you have that. Of course that requires the phone to be booted. If you can post, a screenshot.
Something to consider: it's risky so do only after determining the proper stock tar fails even using Odin default settings. So If you continue to have the eMMC write error, the PIT can be found on Sammobile in the Note 4 PIT thread (posted at bottom of this post). In order to determine if flashing error or component failure, power down, pull battery for a minute or more, and first try the suggested tar with Odin defaults. If it fails with eMMC write error again, you can try to flash with repartition and PIT with "nand erase all" and stock tar loaded, all at same time. Important: Always have the right PIT loaded with repartition option checked. Don't forget the battery pull prior to download mode.
If the last step fails, you most likely have the a component failure. If it's just a boot issue, nand erase all sometimes causes that: try factory reset in stock recovery, pull battery and flash the tar again with Odin defaults.
Before beginning, first determine which stock tar to flash. I'd recommend latest if your bootloader is Android 5.1 or higher. The Sprint version started getting the updated bootloader before Android 5.1, so only the initial Lollipop release had the less secure bootloader.
Find PIT here:
http://www.sammobile.com/forum/showthread.php?p=137840
You can find recommended safe versions of Odin here:
http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
Sent from my SM-N910P using Tapatalk
---------- Post added at 11:10 AM ---------- Previous post was at 10:46 AM ----------
TheMadScientist420 said:
Out of curiosity? Keep getting conflicting. Does this device have a bad hostory of emmc failures. I got one doing it. But this things seems to have loads of weird issues. I will get some logs together tonight when i get. Home. Im goi. To try to flash latest mm firmware tonight. When i try to start up anything other than dl mode. I get the connect to kies. The fiwmware update went wrong select emency recovery. Kies 3 doesnt work for this device or it says it dont. And i get a side by side configuration error when installing older odin. Got windows 10
Click to expand...
Click to collapse
Maybe my reply above helps you?
IMO, the Note 4 does a lot of eMMC failures. Not scientific or statistical data comparisons but I'm seeing recommendations to get TEP (insurance) in close circles on my Sprint version, especially if sluggishness starts or trying to hold out until 2017 phones are available for upgrade.
Having the phone boot to download mode is an indicator of eMMC hardware failure. Some time ago, Samsung had an ongoing to-do list that included flash errors on Odin and OTA. I have a theory that it may discovered by updating phone but may just be hardware failure.
The suggested flash with PIT and repartition and nand erase all with stock tar loaded in AP slot is only a troubleshooting step to eliminate the possibility of a bad flash or update causing the initial error. It's been proven redundant many times and some feel attempting more flashes only worsens the severity. But it is ultimately severe failure at some point so use with appropriate caution. The many eMMC failures makes me weary of updates. Time to consider TEP; $0 deductible for hardware failure without losing an upgrade on line, if available.
Main board replacement or eMMC replacement is another alternative. The local uBreakItiFixIt quoted me $10 labor to replace main board with one that I'd have to obtain myself. I've seen certified used ones on eBay and Amazon.
Hopefully mine lasts. I plan to keep it but planning to upgrade my line in 2017.
Sent from my SM-N910P using Tapatalk

samep said:
That's not good but I'm still not sure if you can flash that KitKat stock tar or not.
If you've had updates greater than Android 5.0 on that phone, I'd suggest not trying to flash that anymore. If that applies, try the latest stock tar.
The eMMC write error could be component failure but I'm thinking it could also be refusing to downgrade the bootloader to a less secure one which would apply if the phone is currently on a higher bootloader. Could you get the bootloader version by running this app?
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
You can use Galaxy Tools if you have that. Of course that requires the phone to be booted. If you can post, a screenshot.
Something to consider: it's risky so do only after determining the proper stock tar fails even using Odin default settings. So If you continue to have the eMMC write error, the PIT can be found on Sammobile in the Note 4 PIT thread (posted at bottom of this post). In order to determine if flashing error or component failure, power down, pull battery for a minute or more, and first try the suggested tar with Odin defaults. If it fails with eMMC write error again, you can try to flash with repartition and PIT with "nand erase all" and stock tar loaded, all at same time. Important: Always have the right PIT loaded with repartition option checked. Don't forget the battery pull prior to download mode.
If the last step fails, you most likely have the a component failure. If it's just a boot issue, nand erase all sometimes causes that: try factory reset in stock recovery, pull battery and flash the tar again with Odin defaults.
Before beginning, first determine which stock tar to flash. I'd recommend latest if your bootloader is Android 5.1 or higher. The Sprint version started getting the updated bootloader before Android 5.1, so only the initial Lollipop release had the less secure bootloader.
Find PIT here:
http://www.sammobile.com/forum/showthread.php?p=137840
You can find recommended safe versions of Odin here:
http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
Sent from my SM-N910P using Tapatalk
---------- Post added at 11:10 AM ---------- Previous post was at 10:46 AM ----------
Maybe my reply above helps you?
IMO, the Note 4 does a lot of eMMC failures. Not scientific or statistical data comparisons but I'm seeing recommendations to get TEP (insurance) in close circles on my Sprint version, especially if sluggishness starts or trying to hold out until 2017 phones are available for upgrade.
Having the phone boot to download mode is an indicator of eMMC hardware failure. Some time ago, Samsung had an ongoing to-do list that included flash errors on Odin and OTA. I have a theory that it may discovered by updating phone but may just be hardware failure.
The suggested flash with PIT and repartition and nand erase all with stock tar loaded in AP slot is only a troubleshooting step to eliminate the possibility of a bad flash or update causing the initial error. It's been proven redundant many times and some feel attempting more flashes only worsens the severity. But it is ultimately severe failure at some point so use with appropriate caution. The many eMMC failures makes me weary of updates. Time to consider TEP; $0 deductible for hardware failure without losing an upgrade on line, if available.
Main board replacement or eMMC replacement is another alternative. The local uBreakItiFixIt quoted me $10 labor to replace main board with one that I'd have to obtain myself. I've seen certified used ones on eBay and Amazon.
Hopefully mine lasts. I plan to keep it but planning to upgrade my line in 2017.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you good sir. Both posts clarify well. Sometimes mine stips about where last posters is. Sometimes it flashes 1/4 of the system before failing. I obtained this device stuck in qloader mode and outa nowhere decided to work. I flashed a few files and all was great. Im thinking. Im flashing a older bl on the newer one hopefully. If not im not out nothing. Not a sprint customer so no innsurance.

TheMadScientist420 said:
Thank you good sir. Both posts clarify well. Sometimes mine stips about where last posters is. Sometimes it flashes 1/4 of the system before failing. I obtained this device stuck in qloader mode and outa nowhere decided to work. I flashed a few files and all was great. Im thinking. Im flashing a older bl on the newer one hopefully. If not im not out nothing. Not a sprint customer so no innsurance.
Click to expand...
Click to collapse
Makes me wonder if the issue with eMMC is cold solder joints?
I used to work in a manufacturing facility. It's rare to happen but unless tight solder wave standards are in place, failures could be more frequent. It happens with even the tightest standards.
Reflow the solder is the fix but have to be careful not to overheat or short electrodes.
Sent from my SM-N910P using Tapatalk

samep said:
Makes me wonder if the issue with eMMC is cold solder joints?
I used to work in a manufacturing facility. It's rare to happen but unless tight solder wave standards are in place, failures could be more frequent. It happens with even the tightest standards.
Reflow the solder is the fix but have to be careful not to overheat or short electrodes.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Same issue as lgg4 but with cores on the prossessor.
Mine keeps failing as a flash write failure makes it to system flashing then fails

TheMadScientist420 said:
Same issue as lgg4 but with cores on the prossessor.
Mine keeps failing as a flash write failure makes it to system flashing then fails
Click to expand...
Click to collapse
You get the eMMC write error each time?
If not, have you tried different USB cables and ports? Different Odin versions? I've seen some users revert to 3.10.6 or 3.10.7 for flash issues. You do have Samsung driver from Samsung support installed, right? Windows 10 doesn't seem to require run as administrator to flash successfully but you might try with and without it just in case.
I forgot to mention earlier that KIES may not work for rooted phones. There may be exceptions for users that started using it before they rooted but I get that inquiry for serial number that cannot doesn't satisfy the inquiry with valid number. I've seen the emergency recovery but never attempted to use it so I don't know if KIES is partially functional or not.
Sent from my SM-N910P using Tapatalk

samep said:
You get the eMMC write error each time?
If not, have you tried different USB cables and ports? Different Odin versions? I've seen some users revert to 3.10.6 or 3.10.7 for flash issues. You do have Samsung driver from Samsung support installed, right? Windows 10 doesn't seem to require run as administrator to flash successfully but you might try with and without it just in case.
I forgot to mention earlier that KIES may not work for rooted phones. There may be exceptions for users that started using it before they rooted but I get that inquiry for serial number that cannot doesn't satisfy the inquiry with valid number. I've seen the emergency recovery but never attempted to use it so I don't know if KIES is partially functional or not.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Mine just says flash write failure. Cant flash twrp cant mount. Tried a factory wipe in fact recovery. Failed cannot mount system. Exception error.
Odin said something while trying to flash twrp. Alongs the lines of no pit for mapping. When i flashed pit ot passes. It acts like the partition table is messed up

TheMadScientist420 said:
Mine just says flash write failure. Cant flash twrp cant mount. Tried a factory wipe in fact recovery. Failed cannot mount system. Exception error.
Odin said something while trying to flash twrp. Alongs the lines of no pit for mapping. When i flashed pit ot passes. It acts like the partition table is messed up
Click to expand...
Click to collapse
Did you try loading the PIT from Sammobile and a recent tar with options repartition and nand erase all? If the tar doesn't include PIT, you might consider PC1 stock tar from the stock tar thread in general forum. Check the md5 against zip before extracting the tar.md5
If you can reach recovery, factory reset. Then power down and pull battery prior to Odin.
Have you tried any of this with a new battery? Historically, from what you describe, you may have been on borrowed time with the functionality you had. All the above is a long shot because typically, updates should happen without error. If you can't flash and boot without error; that just isn't normal if you've taken the appropriate steps to ensure success. Sorry if that's the case.
Sent from my SM-N910P using Tapatalk

samep said:
Did you try loading the PIT from Sammobile and a recent tar with options repartition and nand erase all? If the tar doesn't include PIT, you might consider PC1 stock tar from the stock tar thread in general forum. Check the md5 against zip before extracting the tar.md5
If you can reach recovery, factory reset. Then power down and pull battery prior to Odin.
Have you tried any of this with a new battery? Historically, from what you describe, you may have been on borrowed time with the functionality you had. All the above is a long shot because typically, updates should happen without error. If you can't flash and boot without error; that just isn't normal if you've taken the appropriate steps to ensure success. Sorry if that's the case.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have tried most of that. This thing does have a weird battery issue. Its no loss to me. I got this thing cheap the other day. I keep getting failed to repartition errors. Which seems to come back to the fail to mount system.
I hate to buy a battery. I dont buy cheappies. Due to high failure quality rateS.
I used the pit from samobiles.
Even factory recovery will wip cache. But thats when i get the failed to mount system
new update so i flashed the developer firmware minus the system and data parts. so basicly modem and other partitions included in boot and that takes every time now it litrely fails when i try to flash something to the system partition. when i flash twrp i get failure says no pit for mapping.
even the pit files is failing says there is no pit partition
id say im donr now just saw a mmc read fail on device in dl mode

A320FL Recovery Bricked And Stuck On Bootloading

Hi everyone,
so here is the issue I'm facing with my A320FL.
Last week, after I had it all reinstalled properly, phone restarted and got stuck on FRP lock menu.
So I decided to wipe it all and reinstall with proper official ROM again.
I used Odin 3.13.3 launched as Administrator and latest Samsung Drivers.
I download latest official 8.0.0 ROM from SAMmobile.
I used the procedure with BL, AP, CP and CSC files (I don't mind losing all my data, I have backup) and all goes fine up to the green PASS! (I disabled Auto Reboot in Odin's Options just to take the screenshot):
https://ibb.co/HVrnxbw
then phone restarts, then goes with "installing updates" and quickly go up to 32%, then waits a bit: https://ibb.co/t392t7Q
then restarts again, then goes "Erasing" for a like 2 minutes: https://ibb.co/FJHMT7g
then restart again, and then the problem appears when phone gets stuck on following screen:
https://ibb.co/zHby4dx
I cannot go to recovery and wipe cache or data as I've seen on other posts to resolve this issue as recovery is blocked.
If I reboot the phone with 'Volume down + HOME + Power', I get to this screen: https://ibb.co/4RhJgJG
then if I press 'Volume Up" I have this screen: https://ibb.co/Wnh5Hv0
So I have "FRP lock: ON" at the top of the screen, and I cannot install TWRP or any custom recovery (Odin ends with a fail message if I try so): https://ibb.co/0qPLFL5
And phone shows "Custom Binary Blocked By FRP Lock": https://ibb.co/hsLdKjs
So I cannot boot into the ROM, go in Developer Options and Enable OEM unlock :/
And everytime I try to reinstall the official ROM, I get stuck on the "No Command" screen.
Any idea on how to go back to proper state?
Thanks

Just wait it out a bit. If it auto goes to recovery, it goes through that, well because the phone is kinda slow. Wait out the no command thing for 5 minutes, if it doesn't proceed that's a different issue

Thanks for your answer.
When I wait on the no command screen, the phone then reboots after like 3/4 minutes, and eventually goes back to that same screen again.
Thanks

Any chance of an update or something to try on that one please?
Thanks

Hi everyone,
any chance of a suggestion on my issue?
Is the phone bricked or have I a chance to recover it?
Thanks

mhaxor said:
Hi everyone,
any chance of a suggestion on my issue?
Is the phone bricked or have I a chance to recover it?
Thanks
Click to expand...
Click to collapse
I recomend trying to press power botton cupple of times while in recovery "No Command" mode.

RootingPro-18 said:
I recomend trying to press power botton cupple of times while in recovery "No Command" mode.
Click to expand...
Click to collapse
I tried that, and nothing happens.

Again I tried a few options, in different order, and so far the phone still looks briked.
Dunno if I'll be able to recover it anytime :/

mhaxor said:
Again I tried a few options, in different order, and so far the phone still looks briked.
Dunno if I'll be able to recover it anytime :/
Click to expand...
Click to collapse
Send me PM i will try to help you.?

@mhaxor: I have the same behaviour. Is it possible that you did the latest (September) stock firmware update before ? Boot loader updates and then no combination firmware flashing is possible.

cyberbix said:
@mhaxor: I have the same behaviour. Is it possible that you did the latest (September) stock firmware update before ? Boot loader updates and then no combination firmware flashing is possible.
Click to expand...
Click to collapse
Hey, I didn't install the september update, but I tried a few different stock ROM with ODIN from sammobile, one of them being with a build date of October 2019
https://www.sammobile.com/samsung/galaxy-a3/firmware/SM-A320FL/XEF/download/A320FLXXS5CSJ1/300636/
Regards

mhaxor said:
Hey, I didn't install the september update, but I tried a few different stock ROM with ODIN from sammobile, one of them being with a build date of October 2019
Click to expand...
Click to collapse
What does your bootloader state in download mode (B:?).
I guess 4, if so you have the same softbrick then me. Did you search for a combination firmware supporting Bootloader type 4 ?

I only see this screen when booting up the phone: https://ibb.co/hsLdKjs

mhaxor said:
I only see this screen when booting up the phone: https://ibb.co/hsLdKjs
Click to expand...
Click to collapse
Yes. What I thought. Your are on bootloader 4. Take a look at several threads here about a combination firmware that works with bootloader 4. There´s none at the moment.
I´ve exactly the same behaviour, none of the stock ROMs (and I tried many of them) was able to get the phone up again.
Bad luck, but at the moment your device is less or more bricked. Let me know if you are succesful, I´ll do the same and send you a PN.

mhaxor said:
I only see this screen when booting up the phone: https://ibb.co/hsLdKjs
Click to expand...
Click to collapse
Dude try bypassing FRP, i will try to search for some tools for you!

The only way I managed to bypass FRP lock was with unlocking the OEM in the device's settings in developper mode, then installing a new recovery.
But of course I can't access this now.

is it dead?
cyberbix said:
Yes. What I thought. Your are on bootloader 4. Take a look at several threads here about a combination firmware that works with bootloader 4. There´s none at the moment.
I´ve exactly the same behaviour, none of the stock ROMs (and I tried many of them) was able to get the phone up again.
Bad luck, but at the moment your device is less or more bricked. Let me know if you are succesful, I´ll do the same and send you a PN.
Click to expand...
Click to collapse
Edit: I was using the wrong version of (3.12) odin should have used version 3.13.
anyway you can shed some light on my issue as well? this was a friends phone (legit story), here in brazil these kids don't pay attention to what they are doing. they put google accounts on phones and fail to remember them nor do they care to. the device is showing similar symptoms. all I can really say is the device will only flash combination files, if I flash a firmware it only flashes the modem. when I got the device it was on bootloader 2 (b:2 firmware A320FLXXS2BRA9). then I ended up flashing a firmware that was b:3. after I did that the device will only go to factory binary, and like I mentioned before it wont flash the firmware just the modem.
on power up the device in the upper left conner says:
nad: passed
rpwb provisioned
in bootloader:
odin mode
download speed: fast
product name: sm-a320fl
current binary: Samsung official
system status: official
frp lock: on
secure download: enabled
ccic=
warrenty void: 0 (0x0000)
rp swrev: b:3 k:1 S:1
odin after flashing a firmware:
<ID:0/007> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
<ID:0/008> 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/008> Odin engine v(ID:3.1207)..
<ID:0/008> File analysis..
<ID:0/008> skip file list for home binary
<ID:0/008> sboot.bin.lz4
<ID:0/008> param.bin.lz4
<ID:0/008> cm.bin.lz4
<ID:0/008> boot.img.lz4
<ID:0/008> recovery.img.lz4
<ID:0/008> system.img.lz4
<ID:0/008> userdata.img.lz4
<ID:0/008> modem_debug.bin
<ID:0/008> cache.img.lz4
<ID:0/008> hidden.img.lz4
<ID:0/008> Home Binary Download
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> modem.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> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Removed!!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

@mhaxor: Are there any news on your bricked device ? Have you been successful finding a combination firmware that works with latest bootloader ?

Hello,
no further improvement, still stuck.
This is not my main phone so I can use the other one daily, but I'd still like to unbrick that A320FL.
Regards,

mhaxor said:
Hello,
no further improvement, still stuck.
This is not my main phone so I can use the other one daily, but I'd still like to unbrick that A320FL.
Regards,
Click to expand...
Click to collapse
Do You have telegram?