Develop Bugs

[Q] Unique Situation ATT Galaxy Note 2 Help

Ok, this is my first post so forgive if this is in the wrong section...
I have a friend's Galaxy Note 2 ATT that was stuck on the Galaxy Note 2 Boot screen, and it wouldn't go any further.
Because I work for Samsung at the Samsung Experience Shop, I tried running it through our smart reflash tool
-----> This didn't work because it would fully download it onto the phone, but when it got to the Android with the thing spinning in its chest, it would stop and ALWAYS freeze halfway.
Next step I tried doing was going through Samsung Kies and downloading the stock OS and load that, but the same Android with the spinning thing in its chest would show up and it would freeze.
Due to this guy being my friend I told him I would try anything to get his phone to work again (root, to custom recovery, to custom rom)
My steps so far:
1. I have successfully rooted my device via ODIN 1.85 by using CF-Auto-Root
2. Afterwards, I loaded on a custom recovery via ODIN 1.85 which now is philz_touch_6.07.9
Here is my problem now, I've tried searching everywhere and I can't really find the answer...
Whenever I try to side load a rom through ADB through Android tools (its in the right directory and everything because it transfers over), I keep getting an error message "E: Error in /tmp/update.zip (status 7) Installation Aborted."
Now before I get that error I get stuff like getprop("ro.product.device")==t0lte" ||getprop("ro.build.product").... etc. and it goes on and on.
So far the ROMs that I have tried were Cyanogenmod 10.1 and the Pacman Rom, and yes, both are for the correct device like the model name/number match up. And now how I said I thought I rooted the device, whenever I try to reboot into recovery via Philztouch, it says at the top Root Access is missing. Root device, and I click yes. When it reboots into recovery and I want to turn the phone off again, it still says Root Access is missing.
I am open for anything really. My friend just wants his phone to work again. and I've literally exhausted all of my ideas as I keep running into the same issue.
What am I doing wrong? and is something like this possible to fix? Or is my friend SOL?
Thanks for all the help. It's much appreciated.

Your recovery is outdated. Status 7 error.
I use TWRP from the original development section.

rangercaptain said:
Your recovery is outdated. Status 7 error.
I use TWRP from the original development section.
Click to expand...
Click to collapse
+1 to this^^^^^
Look here»»» http://forum.xda-developers.com/showthread.php?t=1981198
And why not give him something stock instead of a CM Rom??[emoji37]
Plenty of stock 4.3 Rom's in the development section...
Sent from my SAMSUNG-SGH-I317 using Tapatalk

Good advice ^^^^ for your friend.

Ok, thanks for the direct response. I've downloaded the latest TWRP recovery and when I try to push it through ODIN, I still have PhilZ Touch 6..? Sorry, I feel like I'm skipping something simple...
according to a guide, I have to make sure when I'm pushing a custom recovery through ODIN I have to leave Auto Reboot and F. Reset Time UNCHECKED. I made sure they were, and for some reason after it says PASS and thread successful 1 failed 0. When I disconnect the phone and turn it back on into recovery mode, I still has PhilZ Touch...

Use your recovery to flash TWRP. There's a zip version and an odin version.

Ok, I got stock recovery on there just by redoing the CF-Auto Root package through ODIN.
I figured well I can apply the ROM the adb through the stock recovery...
It was going well until I got this error. The last line before the error stated:
"Veryfying update package..."
Error:
E: failed to verify whole-file signature
E: signature verification failed
is that due to the fact that i'm using stock recovery?
In the mean time since that didn't work I'm going to flash TWRP and hopefully that fixes the issue.
I'm kinda just documenting my steps here in case anyone wants to follow and chime in if i'm doing something wrong.
Thanks for the help guys!
************3AM EDIT*****************
Ok so I managed to get TWRP 2.7 on the device as I needed the ability to adb sideload the update.zip to the phone since I can't boot into the phone's OS whatsoever.
This is the error I'm receiving now:
Checking for MD5 file...
Skipping Md5 check: no MD5 file found.
then it restarts and I'm stuck at the Samsung GALAXY Note II screen... what's my next step..? Find a different ROM?
**********Another Edit**************
It has just come to me, I shouldn't have to adb sideload the update.zip or the custom rom... even though I can't get into the phones OS and can't copy and paste to the root of the device. Can't I just copy and paste it to a micro SD card and mount that, and then apply the update from there? And as far as those errors I had earlier, I'm still not sure why I received them...
Again, thanks for all the help

Adb won't work if USB debugging wasn't enabled.
In TWRP you can disable md5 checking.
And you don't unzip the zip file.

Thanks for the reply. ADB didn't work because, in fact, since I haven't been able to turn the phone on, I know USB debugging isn't turned on.
And as far as having the MD5 check, it is unchecked.
I received a success message. However, when I try to boot the phone it still gets stuck at the Samsung Galaxy Note II screen.
******Edit******
Ok ended up using a different ROM, I think PacMan rom? It seemed to work until it got to extracting system files and then the phone sits for a couple minutes, screen turns black. And when I try to wake the screen, only the back and menu buttons come up...
Another thing, even though I've already rooted my device using CF-Auto-Root, When I reboot my device with TWRP I go to reboot and then recovery. Then it warns me saying no OS bla bla bla, and then it says it notices that my phone isn't rooted? And that SuperSU isn't on the device. It asks to install it by swiping. I swipe it starts to install, phone reboots. When I reboot it again, it still tells me that the phone isn't rooted. And with the phone not being rooted, I'm coming to the conclusion why I'm having trouble trying to flash Roms.. Is this a possibility?

Why are you using ADB? just drop the .zip for the ROM you wish to flash onto a micro SD card, and flash from within the TWRP. Don't try to extract the .zip whatsoever.

Note 2 softbricked, TWRP recovery says (system/data/EFS/usb/data etc...) cant mount!

Hi guys,
New to XDA, I have a Note 2 which was getting a bit sluggish but worked fine, I rooted and custom flashed TWRP and saved a NANDROID BACKUP using TWRP to SDCARD and kept that on the desktop for safe keeping.
The phone worked fine after that for some time, Now spontaneously I woke up in the morning with the phone stuck on the samsung logo screen, so i knew it was softbricked but i cant understand how that happened.
First thing i tried apart from multiple restarts, removing battery etc, was then boot into custom recovery TWRP and try and restore from SDCARD nandroid backup. But it says EVERYTHING CAN'T be mounted!
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
E: Unable to find partition size for '/modem'
E: Primary block device '/dev/block/mmcb1k0p16' for mount point '/data' is not present!
unable to mount '/data', EFS, System, cache and so forth.....
The phone was sincerely working fine and this happened seemingly randomly while asleep. Phone hadnt dropped and was connected to charger, and prior to this was restarted several times with no issues.
I have been looking at endless articles, I changed to CWM, TWRP, Philz and Stock Recovery and ALL OF THEM are unable to mount. So this does NOT seem to be a problem in the recovery. I used TWRP 2.8.0.1 for my Note 2 as well as 2.7.0.1. So I have a perfect NANDROID RESTORE on my SDCARD and DESKTOP to fix this but no way of mounting it to recovery?
Odin works fine and each time i flashed the recovery it would work fine. Is there some way of fixing it with ODIN?
Any input here would be greatly appreciated, and hopefully this helps someone else with the exact same issue.
Cheers.

the9kill said:
Hi guys,
New to XDA, I have a Note 2 which was getting a bit sluggish but worked fine, I rooted and custom flashed TWRP and saved a NANDROID BACKUP using TWRP to SDCARD and kept that on the desktop for safe keeping.
The phone worked fine after that for some time, Now spontaneously I woke up in the morning with the phone stuck on the samsung logo screen, so i knew it was softbricked but i cant understand how that happened.
First thing i tried apart from multiple restarts, removing battery etc, was then boot into custom recovery TWRP and try and restore from SDCARD nandroid backup. But it says EVERYTHING CAN'T be mounted!
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
E: Unable to find partition size for '/modem'
E: Primary block device '/dev/block/mmcb1k0p16' for mount point '/data' is not present!
unable to mount '/data', EFS, System, cache and so forth.....
The phone was sincerely working fine and this happened seemingly randomly while asleep. Phone hadnt dropped and was connected to charger, and prior to this was restarted several times with no issues.
I have been looking at endless articles, I changed to CWM, TWRP, Philz and Stock Recovery and ALL OF THEM are unable to mount. So this does NOT seem to be a problem in the recovery. I used TWRP 2.8.0.1 for my Note 2 as well as 2.7.0.1. So I have a perfect NANDROID RESTORE on my SDCARD and DESKTOP to fix this but no way of mounting it to recovery?
Odin works fine and each time i flashed the recovery it would work fine. Is there some way of fixing it with ODIN?
Any input here would be greatly appreciated, and hopefully this helps someone else with the exact same issue.
Cheers.
Click to expand...
Click to collapse
It is possible that your Nandroid Backup is corrupt. It happens. Also, as you tried everything, I think you should flash fresh stock rom via odin.
Press thumps up if you found this suggestion helpful.
Sent from my GT-N7100 using Tapatalk

ceomaverick said:
It is possible that your Nandroid Backup is corrupt. It happens. Also, as you tried everything, I think you should flash fresh stock rom via odin.
Press thumps up if you found this suggestion helpful.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Hi ceomaverick,
Thanks for replying so fast, I may have not explained clearly but, the NANDROID BACKUP should be fine, its on the SD but cant be seen by any of the Recoverys (TWRP,CWM,stock,Philz) because nothing is able to MOUNT. So whether or not the nandroid backup is corrupt doesnt matter because we cant use it yet, as first problem is mounting to use the custom recovery restore.
Thanks for the suggestion about the Stock ROM , I have been downloading that for the past few hours! (XME-N7100XXUFNI4-20141020155451.zip) haha! That is what I will try next via Odin, just not sure how to do it safely. I will try and google and article for re-flashing stock rom via odin to make sure i tick all the correct boxes. If anything works will be back to update.
Cheers
P.s If anyone is interested in looking for this phones Stock ROM I found it here:
samsung-updates.com/device/?id=GT-N7100 (Select the one for your country/region)

the9kill said:
Hi ceomaverick,
Thanks for replying so fast, I may have not explained clearly but, the NANDROID BACKUP should be fine, its on the SD but cant be seen by any of the Recoverys (TWRP,CWM,stock,Philz) because nothing is able to MOUNT. So whether or not the nandroid backup is corrupt doesnt matter because we cant use it yet, as first problem is mounting to use the custom recovery restore.
Thanks for the suggestion about the Stock ROM , I have been downloading that for the past few hours! (XME-N7100XXUFNI4-20141020155451.zip) haha! That is what I will try next via Odin, just not sure how to do it safely. I will try and google and article for re-flashing stock rom via odin to make sure i tick all the correct boxes. If anything works will be back to update.
Cheers
Click to expand...
Click to collapse
Well, no hassle really. ODIN 3.09 does a great job. Just dump your file in AP tab and start after MD5 is verified. You should be fine. Welcome.
Sent from my GT-N7100 using Tapatalk

ceomaverick said:
Well, no hassle really. ODIN 3.09 does a great job. Just dump your file in AP tab and start after MD5 is verified. You should be fine. Welcome.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Bad news, Odin failed halfway through. Was able to boot back into download mode thankfully. But after rebooting again, seems the phone is now HardBricked. Meaning it wont even turn on.
Not sure what options are left now (if any). Anyone know what to do with a Note 2 hardbrick (apart from use it as an expensive door wedge).
Cheers

the9kill said:
Bad news, Odin failed halfway through. Was able to boot back into download mode thankfully. But after rebooting again, seems the phone is now HardBricked. Meaning it wont even turn on.
Not sure what options are left now (if any). Anyone know what to do with a Note 2 hardbrick (apart from use it as an expensive door wedge).
Cheers
Click to expand...
Click to collapse
This should not happen unless the cable or the usb ports are faulty. ( or if u have not followed the instructions correctly )
Anyway,
Can u still go to download mode? If yes, try a different cable and flash.
If no, use a USB jig to revive your phone. Ebay has them in plenty. With this you might get into download mode.
Also, are u flashing the correct firmware?
I have flashed custom ROMs n number of times without a single instance of failure.
Best of luck.
Sent from my GT-N7100 using Tapatalk

ceomaverick said:
This should not happen unless the cable or the usb ports are faulty. ( or if u have not followed the instructions correctly )
Anyway,
Can u still go to download mode? If yes, try a different cable and flash.
If no, use a USB jig to revive your phone. Ebay has them in plenty. With this you might get into download mode.
Also, are u flashing the correct firmware?
I have flashed custom ROMs n number of times without a single instance of failure.
Best of luck.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Hi again,
Yes, I can fully appreciate why you would say that, from what I see ODIN is very straight forward and unless you do something totally (silly), like jiggle the cable or do something midway it should not hardbrick. Therefore it makes sense you suggesting the cable is faulty, but it seemed to copy over 32GB of data seemlessly in one go. Although i will change the cable as a precaution as there is a slight cut.
When I say hardbricked, I mean hardbricked as in no recovery and no download mode, and no display whatsoever no matter what you do.
[UPDATE] Okay, the strangest thing happened. After a whole day of charging the phone, sometimes trying it on for luck, hoping something would happen. I went to the doctors and came back, and oddly enough the screen had life!!! Yes, this gets bizarre, I repeat a clearly hardbricked phone resurrected back to life with a screen showing ("A firmware upgrade encountered an error, please retry with kies") or something like that, so overjoyed with this sign of life I carefully put it into download mode and its now waiting.... But before I try Odin again, I think I will take a leaf from Ceomavericks suggestion and get a brand new cable from another samsung phone and use that this time.
By the way Ceomaverick, last time i just tried to flash to stock rom using AP, and kept autorebook and Ftime checked.
This time I am seeing on a thread to do the following, please advise (given that my TWRP doesnt mount anything at all).
It says do this: from: http://forum.xda-developers.com/showpost.php?p=43760271&postcount=22
Open ODIN, and check Re-Partition, Nand Erase All, Auto Reboot and F. Reset Time. Uncheck all other boxes. Click the PIT button and select the PIT file appropriate for your device (16GB or 32GB). Click the PDA file and choose the Stock Rom you downloaded. Press start and wait.
File Type: rar PIT_t03g_0907_16GB.rar - [Click for QR Code] (899 Bytes, 84 views)
File Type: zip BOOTLOADER_N7100.zip - [Click for QR Code] (1.03 MB, 75 views)
click start.
If everything goes well, the process should succeed and the phone should reboot. Don't wait for the phone to boot into android. Immediatly boot into recovery, factory reset the phone and wipe cache. Reboot to Android.
Now, if everything worked well, your phone should boot into Android. And then sort out the sleep of death issue.
I think I will wait for some feedback before doing this and just enjoy that my phone is mysteriously back in download mode, perhaps a hardware issue......
Another thread reading http://www.theandroidsoul.com/unbrick-restore-samsung-galaxy-note-2-gt-n7100/
Cheers

UPDATE:
Now that we are back to softbrick, I tried download mode and ODIN again, this time it fails right near the end. Last time it failed somewhere in the middle. So it seems to randomly fail and this is with the brand new USB Sony PS4 Cable. I ditched the worn out samsung cable because of the first fail. So twice its failed, but at different points. If it doesnt hardbrick again this time I suppose I will keep repeating till it passes.
For now just a straight rom flash, not sure if i should repartition with the before mentioned PIT Files and bootloader etc. Wont do that unless im told.
Thanks
Attached (Fail Image)

the9kill said:
UPDATE:
Now that we are back to softbrick, I tried download mode and ODIN again, this time it fails right near the end. Last time it failed somewhere in the middle. So it seems to randomly fail and this is with the brand new USB Sony PS4 Cable. I ditched the worn out samsung cable because of the first fail. So twice its failed, but at different points. If it doesnt hardbrick again this time I suppose I will keep repeating till it passes.
For now just a straight rom flash, not sure if i should repartition with the before mentioned PIT Files and bootloader etc. Wont do that unless im told.
Thanks
Attached (Fail Image)
Click to expand...
Click to collapse
Good news is you can visit download mode.
Ok. Alternative.
Download Philz recovery latest version. Flash it via ODIN. If it succeeds, u can flash a touchwiz rom
If that fails, then your partition table is corrupt (asumming thr r no hardware issues. )
Download firmware from different region for your note 2. India maybe. And flash them. May be this might do the trick.
If all above fails, it has to b a hardware issue.
Sent from my GT-N7100 using Tapatalk

ceomaverick said:
Good news is you can visit download mode.
Ok. Alternative.
Download Philz recovery latest version. Flash it via ODIN. If it succeeds, u can flash a touchwiz rom
If that fails, then your partition table is corrupt (asumming thr r no hardware issues. )
Download firmware from different region for your note 2. India maybe. And flash them. May be this might do the trick.
If all above fails, it has to b a hardware issue.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Hi ceomaverick!
Just going to highlight what you said with a few questions please.
"Good news is you can visit download mode. " - Yes, and once I tried to flash it for the second time it got hardbricked round 2. So somehow me flashing it gives it a seemingly temporary hardbrick. That was some hours ago and still no way to turn it on or get any sign of life, just like yesterday before it miraculously came to life again. Which since it has happened once I am guessing it will come back to life again as i followed the exact same procedure as before but Odin failed much later on into the process rather than halfway through.
"Download Philz recovery latest version. Flash it via ODIN. If it succeeds, u can flash a touchwiz rom" - Okay I had Philz before I will reflash it when it comes up and i suppose search for a note 2 touchwiz rom. Philz as before wont be able to mount anything though, even sim card. As i did this prior none of them, TWRP, Philz or CWM can mount anything. So even if i have the ROM file i wont be able to use it on SD if the SD doesnt mount, but i can try it through Odin?
"If that fails, then your partition table is corrupt (asumming thr r no hardware issues. )" - I suspect this is the case hence not mounting, so do I use that PIT file and select Re-Partition in Odin to resolve that?
"Download firmware from different region for your note 2. India maybe. And flash them. May be this might do the trick." - Good idea, while the hardbrick is waiting to resurrect (LOL), I will start a download.
"If all above fails, it has to b a hardware issue. " - Again something I suspect, from forum could be this dreaded eMMC "insane samsung chip" problem which is as far as i know a 16gb internal SD? If so, perhaps there is a way to put in a 16gb SD and edit boot to mount from there as internal instead from the eMMC? Sorry if thats way out there, but i read something like this once.
Appreciate the help, waiting for it to spring back into life

the9kill said:
Hi ceomaverick!
Just going to highlight what you said with a few questions please.
"Good news is you can visit download mode. " - Yes, and once I tried to flash it for the second time it got hardbricked round 2. So somehow me flashing it gives it a seemingly temporary hardbrick. That was some hours ago and still no way to turn it on or get any sign of life, just like yesterday before it miraculously came to life again. Which since it has happened once I am guessing it will come back to life again as i followed the exact same procedure as before but Odin failed much later on into the process rather than halfway through.
"Download Philz recovery latest version. Flash it via ODIN. If it succeeds, u can flash a touchwiz rom" - Okay I had Philz before I will reflash it when it comes up and i suppose search for a note 2 touchwiz rom. Philz as before wont be able to mount anything though, even sim card. As i did this prior none of them, TWRP, Philz or CWM can mount anything. So even if i have the ROM file i wont be able to use it on SD if the SD doesnt mount, but i can try it through Odin?
"If that fails, then your partition table is corrupt (asumming thr r no hardware issues. )" - I suspect this is the case hence not mounting, so do I use that PIT file and select Re-Partition in Odin to resolve that?
"Download firmware from different region for your note 2. India maybe. And flash them. May be this might do the trick." - Good idea, while the hardbrick is waiting to resurrect (LOL), I will start a download.
"If all above fails, it has to b a hardware issue. " - Again something I suspect, from forum could be this dreaded eMMC "insane samsung chip" problem which is as far as i know a 16gb internal SD? If so, perhaps there is a way to put in a 16gb SD and edit boot to mount from there as internal instead from the eMMC? Sorry if thats way out there, but i read something like this once.
Appreciate the help, waiting for it to spring back into life
Click to expand...
Click to collapse
If the firmware from other region fails, then find pit file for 16gb to flash. If that too fails, I think your phone needs hardware repair.
Sent from my GT-N7100 using Tapatalk

Frozen at "Galaxy Note II".

My daughter's note 2, which looks to be in perfect condition, was running dirty unicorn. She messages me in a panic because the phone turned off on her, and wouldn't reboot.
I could get into recovery, but many of the options like factory reset wouldn't work. Reformatting /cache gives an error with ext4 and can't write, and at the bottom of some of the screens is an error about unable to access some log files in the /cache directory. Going to install zip to reinstall dirty unicorn doesn't seem to do anything, it can't find any files.
Wipe system gives errors like "format_volume: make_extf4fs failed on /dev/block/mmcblk0p12". It can't mount /data, just gives an error.
I tried reflashing the stock mj4 via odin, which ran successfully, but didn't resolve anything.
Tried using KIES 2.6, which did go into download mode and said it downloaded a bunch of stuff and then flashed the phone, but it's still stuck at the bootloader.
I tried flashing a bootloader, but am unclear of how to flash the param file if necessary (does it go in bootloader? PDA? what slot in odin?).
I need some ideas. Maybe the flash has died on it, and it's unrecoverable, but it's in such perfect shape that I hate to just toss it.
I have recover 6.0.4.3 (CWM) installed, and can still get into it. But upon loading recovery, it gives me errors like "Can't mount /cache/recovery/command", "Can't open /cache/recovery/last_log", etc.
Any help appreciated.

mrcpu said:
My daughter's note 2, which looks to be in perfect condition, was running dirty unicorn. She messages me in a panic because the phone turned off on her, and wouldn't reboot.
I could get into recovery, but many of the options like factory reset wouldn't work. Reformatting /cache gives an error with ext4 and can't write, and at the bottom of some of the screens is an error about unable to access some log files in the /cache directory. Going to install zip to reinstall dirty unicorn doesn't seem to do anything, it can't find any files.
Wipe system gives errors like "format_volume: make_extf4fs failed on /dev/block/mmcblk0p12". It can't mount /data, just gives an error.
I tried reflashing the stock mj4 via odin, which ran successfully, but didn't resolve anything.
Tried using KIES 2.6, which did go into download mode and said it downloaded a bunch of stuff and then flashed the phone, but it's still stuck at the bootloader.
I tried flashing a bootloader, but am unclear of how to flash the param file if necessary (does it go in bootloader? PDA? what slot in odin?).
I need some ideas. Maybe the flash has died on it, and it's unrecoverable, but it's in such perfect shape that I hate to just toss it.
I have recover 6.0.4.3 (CWM) installed, and can still get into it. But upon loading recovery, it gives me errors like "Can't mount /cache/recovery/command", "Can't open /cache/recovery/last_log", etc.
Any help appreciated.
Click to expand...
Click to collapse
The other weird thing is that I used odin 3.06 to flash twrp 2.8.5, or at least attempt to, download processed, device reset, but recovery is still CWM 6.0.4.3. WTH?

Ok check this thread where I just helped fix a note 2, simular to your situation ok.
Plenty of links in there for you. Keep in mind everything in this thread I'm sending you too it's for the AT&T i317 ok.
http://forum.xda-developers.com/showthread.php?p=59000961
Which I'm sure that is what you have, posting your problem in the Att q&a thread.

Bajanman said:
Ok check this thread where I just helped fix a note 2, simular to your situation ok.
Plenty of links in there for you. Keep in mind everything in this thread I'm sending you too it's for the AT&T i317 ok.
http://forum.xda-developers.com/showthread.php?p=59000961
Which I'm sure that is what you have, posting your problem in the Att q&a thread.
Click to expand...
Click to collapse
Correct, it is an AT&T. I have tried the options in that thread, but I swear, nothing I flash actually "sticks". I've used odin 3.06, put the files in PDA, plugged it in in download mode, the progress bar appears on both odin and the phone, it resets, it reboots, and nada. Hung.
I can't even flash a replacement recovery, nothing "sticks". I've used KIES to flash, it tells me it's successful, but I still have CWM 6.0.4.3. I've tried the original 4.1.1, NJ1 (rooted), I've tried flashing a bootloader, then tried the one with the param file attached, I downloaded a pit file, followed the directions on that page with the Re-partition option, and I still can't get anywhere with it.
If I cold even just get a different recovery installed, just so that I *know*, my odin is OK, then I'd feel better about making progress.
I've tried to flash philz_touch 6.48.4, openrecovery-twrp-2.8.5 through odin, and I can't even get the CWM recovery replaced. Odin reports success, reboots the device, frozen.
I swear, if this was one of my servers at work, I'd figured the NSA has hacked the firmware to just discard writes and report back success.
I'm not crystal clear in ODIN how to flash bootloaders, on one hand, presumably, the "bootloader" button, but one guide shows the bootloader file being put in PDA, so who knows. I may have ended up with a bootloader mismatch, but I thought flashing the latest stock recoveries.
FWIW, the phone was running Dirty Unicorn, although I'm unsure of specifically which version, she's had it for a while.
Thanks for any help.

Just realized something.
If I hold down the power/vol down/home and boot into download mode, I get the little red "odin mode" at the top left, 4 lines of text about custom, etc, and then the green android icon.
If I boot into recovery, then use it to boot into download mode, the green android is there, but none of the text (odin mode, etc) is on the screen. Is this normal?

I have also been having some strangeness with my Telus Note II. Very similar symptoms to what you're describing. One morning I woke up to my phone stuck on the Samsung logo as the phone must have rebooted itself overnight. When I tried to reboot it would freeze at the same spot once again. I tried to go into recover (TWRP) and it wouldn't, and a subsequent reboot left me in a boot loop.
Nothing I tried would help. I couldn't get into TWRP. Using ODIN 3.07 I put on CWM and I was able to get into recovery now, but nothing in it worked. Finally I tried using ODIN to put on CF-Auto-Root-t0ltecan-t0ltevl-sghi317m and I was finally able to get into a recovery that allowed me to do a factory reset. Once I did that I was able to boot up the phone.
I then re-installed TWRP and restored a back up that I had, and everything was normal again. The phone was running great. However, sometime at night things get messed up again. The phone has either reboot itself, and get's stuck again. I then have to repeat this whole process. During the day, the phone runs amazing. It almost seems to run better than before. However at night, if I'm on battery it will get messed up again.
I hope this helps you. Good luck.

have you tried all this using the same computer and usb cable? i would try a different computer, port, usb and re download all files again. perhaps use a different version of odin. good luck:fingers-crossed:

It's the same computer and cable I do my Note 3, and kindle fire 8.9, and with a different cable my nook HD, so I'm skeptical that it's any of those pieces, but for the heckuvit, I will try a different one.

Note 2 GT N 7100 --Stuck on CWM 6.0.4.3
gizhola said:
I have also been having some strangeness with my Telus Note II. Very similar symptoms to what you're describing. One morning I woke up to my phone stuck on the Samsung logo as the phone must have rebooted itself overnight. When I tried to reboot it would freeze at the same spot once again. I tried to go into recover (TWRP) and it wouldn't, and a subsequent reboot left me in a boot loop.
Nothing I tried would help. I couldn't get into TWRP. Using ODIN 3.07 I put on CWM and I was able to get into recovery now, but nothing in it worked. Finally I tried using ODIN to put on CF-Auto-Root-t0ltecan-t0ltevl-sghi317m and I was finally able to get into a recovery that allowed me to do a factory reset. Once I did that I was able to boot up the phone.
I then re-installed TWRP and restored a back up that I had, and everything was normal again. The phone was running great. However, sometime at night things get messed up again. The phone has either reboot itself, and get's stuck again. I then have to repeat this whole process. During the day, the phone runs amazing. It almost seems to run better than before. However at night, if I'm on battery it will get messed up again.
I hope this helps you. Good luck.
Click to expand...
Click to collapse
Dear friends, sorry for my interference, i having CWM recovery v 6.0.4.3 on GT N7100, i used to flash omega ROM 4.3, everything went well until i got stuck on Samsung log and the phone did want restart, i decided to go on CWM recovery, stunned with this message
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Still I can go on download mode, I tried use odin to flash stock rom but failed it takes me always to CWM v 6.0.4.3 where it stuck and dont allow me to format or do any thing except my external sd1 that I tried to flash from but returned to same prob ( CWM v 6.0.43)
also I tried to flash tried twrp 2.8.0.4 but failed
the prob is my internal sd can't be mounted and whatever i do don't pass
I read in your post something about flashing auto root in odin or fix CWM root
can you help please Im stuck in CWM v 6.0.4.3

failed to mount /efs (stale NFS File Handle)

Hi, i need fix those error, the tablet just ask by install a upgrade via ota, but when the tablet restar the device does´t pass from the samsung logo and i get in the recovery and see the error "failed to mount /efs (stale NFS File Handle)" and i be search for a solution, thanks in advance.

Any customation like custom recovery?

User_99 said:
Any customation like custom recovery?
Click to expand...
Click to collapse
No, the tab never has been root or tuned with a diferent recovery. Thanks in advance for your help.

Same Issue
No idea what my friend did with my unrooted and stock Samsung ROM. The device booted and got stuck into Samsung Logo and never went pass that.
On recovery, the Mount /EFS error showed up.
Tried flashing stock ROM via ODIN. (Reset Time and CLear EFS unchecked/checked). All method failed. As of now, for temporary measure, installed TWRP via ODIN and flashed CM13 nightly. Now the device works though IMEI default to 0049XXXX and SIM card not working. Except that all component of the device working. This is very basic and temporary measure.
Don't have the /EFS backup since the device was never rooted.
I'm still finding for a solution.
Samsung Service Centre says that Motherboard needs to be replaced which would cost INR 8,000/-. Thinking of using the diwali sale and exchange this device on the offer. This way EFS and an extra device headache will get over.

Can't flash unbranded Oreo ROM and "e: failed to find /misc partition" message after

Can't flash unbranded Oreo ROM and "e: failed to find /misc partition" message after
Hi guys, here's the deal.
I've bought this phone from an Argentina company called Claro, it has all typical bloatware from the carrier, apps, logo boot, ringtones, etc. So I've decided to flash my brand new Samsung Galaxy A5 2017 (SM-A520M) with the unbranded OREO ROM version from SamMobile, with the 4 files through Odin. Well, the thing's that I didn't know that because of the new security patchs (and for what I know), the OEM unlocked option was disabled it was impossible to flash. I mean Odin recognized it but the steps didn't even appear like always did. I've investigated a bit and I saw that OEM was disabled and because of that, I'll have to wait a week or so to unlock the feature. I've read that setting the date a week back I was able to activate it. And so I did, and it worked, so I thought... I've plugged the phone with Odin in Download Mode and I was determined to finally flash the new ROM. Long story short, it got stuck on SET PARTITION, which I think is the first message that pop-ups on Odin when flashing. So, I waited and waited but nothing happened, I saw that the whole process got stuck. The only thing I remember to read was NAND START WRITTING and nothing else.
After several minutes with no response I've unplugged my phone, and I press the power button. I saw the Samsung logo on loop, I almost died. I've read some forums about the issue but nothing certain, I guess this problem is kinda new. My concern was that when I went to Recovery Mode I saw the message below the options "e:/ failed to find misc/partition" that's when I really thought that it was a real problem and probably my phone was bricked forever. Luckily I made the factory reset and then it booted again. The phone is working great but, I'm very concerned about that message that appears on Recovery Mode, there's something wrong with that partition and for what I read and know about it there could be something missing from my phone that could be essential.
Thoughts? What can I do? I also downloaded Samsung Smart Switch to try to recover the firmware and install it to begin again but the option won't appear. My phone is detected, but I can't use the Emergency Recover with the original Firmware on Smart Switch. One more detail, the phone was bought from a company and it has the logo, ringtones and app from that company. Reason why there's no Oreo update yet with the company, so I have to wait but I really want the unbranded Oreo ROM.
What can I do? I really want Oreo unbranded but I don't know how to procced without screwing my phone. Thanks for reading, this is my first post in the forum.

Which Odin version have you used?

Ok i tell you u have to do to recover your phone and get oreo ?
1-u have to use new version of odin V13.3.1 (with LZ4 support )
2-Download any stock firmware oreo 8.0 from sammobile and flash it
Thats it
I case that not work with u so downlad combinition rom (factory binary rom ) and flash it
Wipe your phone then reflash stock rom oreo
It was very helpful for me

Reeii said:
Which Odin version have you used?
Click to expand...
Click to collapse
the latest version 3.13.1
ayman16 said:
Ok i tell you u have to do to recover your phone and get oreo
1-u have to use new version of odin V13.3.1 (with LZ4 support )
2-Download any stock firmware oreo 8.0 from sammobile and flash it
Thats it
I case that not work with u so downlad combinition rom (factory binary rom ) and flash it
Wipe your phone then reflash stock rom oreo
It was very helpful for me
Click to expand...
Click to collapse
No man, if it were that easy I wouldn't post anything. There's something that won't allow me to do it. It seems that because my phone is in "Pre-Normal" status on downlaod mode there's no chance to flash until it changes to "Normal," and for what I've read I have to wait one week. My question has to do with if is something serious the message "e: failed to find /misc partition" in download mode. What do I have to do from now on? Please read the whole post so you can understand my query. Thank you for your reply and intention to help. :good:

I have simmilar message, but i am not even rooted. "Failed to clear BCB message : failed to find misc partition."
There is nothing to worry about.