please help.. this n7100 note2 32GB always keeps rebooting.
I have tried several ways but non worked..
i have flashed stock ROM and customs ROM also..
even flashed cmw and philz kernals too and cleard delvic cache and done factory resets too before any flash and after it even..
even tried stock ROM with pit file and repartition ticked ,, ???
when i go to recovery mode it says e: failed to mount /efs (Invalid argument)..
but even if efs is gone i just want this phone to get boot up and open successfully...
all flash were successful even from odin or recovery..
only problems is it always keep rebooting on samsung logo??
any idea guys??
try
Try to reset the triangle and install with odin the stock recovery and stock rom, bring it back to samsung and say that the phone keeps rebooting
PS: and say you didnt root the phone if it works they will send the phone to samsung and you will get it back with new version on my sgs3 works
game66master said:
Try to reset the triangle and install with odin the stock recovery and stock rom, bring it back to samsung and say that the phone keeps rebooting
PS: and say you didnt root the phone if it works they will send the phone to samsung and you will get it back with new version on my sgs3 works
Click to expand...
Click to collapse
first clarify if this is note 2 or n7000 ?
aukhan said:
first clarify if this is note 2 or n7000 ?
Click to expand...
Click to collapse
note2 n7100.....
You didn't install a non compatible app like LBE Privacy Guard?
Hello Everyone.
I hope someone can help me with this issue. Recently I've been using the tiagra (tigra)ROM as a daily driver for my n7100. Yesterday my phone died because of low battery. I charged it and try to turn it on and stay on the samsung logo. I am able to enter recovery and download mode with no problems and even flash custom roms but when the phone reboots its the same thing, stays on the same logo.
I tried flashing stock rom with ODIN and its the same thing, I even flashed emergency firmware recovery with KIES and does the same thing. I noticed that when I go to stock recovery shows error: E: failed to mount /efs (Invalid argument). So I started looking for this error in particular, unfotunately I do not have a back up of my EFS folder as an IMG file as many threads online suggest to have in order to fix this.
Also with a custom recovery (CWM) shows: Error mounting /efs!.(clearly seems to be an issue with this particular folder) Is there anyway to solve this issue or to restore the EFS folder without having a back up IMG EFS folder file..(I mean no one does this back up, cause no one ever expects for this to happen right?)
Any help will be greatly appreciated.
Was this ever resolved for you?
Sent from my SPH-L900 using XDA Free mobile app
I posted a quick guide 5 mins ago should work for you. :thumbup:
Sent from AT&T SM-G900A running Dynamic Kat 3.0, Safestrap Latest.
I have searched all over the last few hours for a solution to this issue and yet it mystifies me.. I was running Mr robinson's rooted stock and my phone ran out of battery while at the store, when I got home it refused to boot up.. I have tried several ODIN formats, tried kies... When I get in stock or custom recovery it will fail to mount EFS partition Invalid argument.. Even after a full ODIN flash! Now the good thing is, I have fresh backups and even direct and recent full system and direct file backups of both my efs.tar.gz file and a 20mb file which I believe is the EFS partition... Yes nothing I mean nothing works, At this point if someone is willing and able to help me, you will be my eternal hero!
Thanks in advance for any assistance
Try the very earliest Odin tar available for your device. Do a factory reset then Odin (vice versa would work as well). If you are on the 4.3 bootloader flash the 4.3 Odin after if odin states that the flash failed. Does your battery charge?
Coug76 said:
Try the very earliest Odin tar available for your device. Do a factory reset then Odin (vice versa would work as well). If you are on the 4.3 bootloader flash the 4.3 Odin after if odin states that the flash failed. Does your battery charge?
Click to expand...
Click to collapse
I am on the 4.3 boot loader as my battery turns straight on when plugged in as well as Knox flagged in download mode.. I have flashed stock 4.3 with Odin several times and it completes the procedure no problem.. I have yet to try and flash an older stock rom but that was because I was under the believe there were compatability issues once I made the leap to the 4.3 bootloader. I really think this has to do with the ever present /efs cannot mount illegal argument in recovery issue.. Just cause that seems to be the one difference.. Thanks for your help!
UVALJ1 is my suggestion. I've had success with it recovering jacked up file systems 2x.
Coug76 said:
UVALJ1 is my suggestion. I've had success with it recovering jacked up file systems 2x.
Click to expand...
Click to collapse
Ok I will try and report back.
DarkMattr said:
Ok I will try and report back.
Click to expand...
Click to collapse
No such luck, it still freezes at the last screen before it would normally boot into android, which is now a samsung screen(which shows the process completed successfully). I did note that I AM able to plug my phone in while it's off without it autostarting up and let it charge without booting, which I thought had something to do with which bootloader I am on. Again the only constant is this EFS issue.. I'm praying for some expertise in the area
Hi all,
I've looked through several of the existing threads on the Note 8 and I've not gotten anywhere yet. I had the device happily rooted and working for months and then, stupid me, I used ROM manager to flash a new ROM this morning and on boot, it's stuck on the logo.
I CAN get to the recovery menu, but reset to factory default does nothing. I have wiped the cache from recovery and then tried to factory reset again; still stuck on logo at boot.
I can also get to download mode and have tried using KIES 2.6 (since KIES 3 is for Android 4.4.2 and up) and every time I try to do the update firmware/recovery, it starts, stops and says 'there is a problem with the download file' and then it quits.
I have tried using ODIN 3.7 and a few different recovery files but although it will say 'passed', on reboot, it's stuck on the logo.
Can someone help me, please? This is the only tablet I own and I really need it to not be a door stop
:crying:
not bricked yet, maybe. for now, try to download latest firmware from sammobile.com for n5110 and use odin to flash it.
about the factory reset of course it would still boot loop, you are trying to factory reset a bootlooped rom so it doesnt matter. you should flash a new zip through recovery.
Mr.201 said:
not bricked yet, maybe. for now, try to download latest firmware from sammobile.com for n5110 and use odin to flash it.
about the factory reset of course it would still boot loop, you are trying to factory reset a bootlooped rom so it doesnt matter. you should flash a new zip through recovery.
Click to expand...
Click to collapse
Hi Mr.201,
Thank you for the suggestion. Question, when you say download the latest firmware, will it matter if I don't use the original? I ask because I've been trying to find the original firmware (stock) and while I've found many sites with GT-N5110 FW's, they are all coded for other countries; I can't seem to find one for US. So, if I use a newer firmware, will that work?
I can still get to recovery mode and download mode. I don't know if USB debugging is on, though, which I hope won't matter at this point. I can't remember if it was on when it died on me.
I appreciate your advice! Hopefully, I can get this thing going again. That would certainly make me a happy camper!
For some reason, the US version is labelled as "Cellular South" but in general, any 5110 rom will work, although there are some quirks with wifi frequencies between the North American and European roms.
My Note 8 got stuck in a boot loop. It was rooted/custom recovery/custom ROM. I tried some of things you did, and nothing worked. I ended up downloading and installing the ODIN one click recovery/un-rooted stock image from this thread:
http://forum.xda-developers.com/showthread.php?t=2773712
This restores everything to stock (including the recovery). After flashing, it was still stuck in the boot loop. I booted into the factory recovery, and did a data wipe. After doing that, my note is working now. So ... doing this might be worth a try.
May I make a suggestion when flashing firmware... If you are flashing to something notreviously installed on the device. First flash with philz recovery and perform a full wipe for flashing new ROM. This way everything is clean for your flash to work properly.
A factory reset is not going to work as well for the new flash to take.
hello guys, im having a problem with a s4 mini, i dont have a recovery, a friend gave it to me with this problem.
I can get download mode but when i try to flash TWRP or CWM i get the OK signs in odin but it doesnt get into recovery, well it gets to recovery but it says "no command" (sin comando, in spanish).
It used to have jellybean and updated itself to kitkat, it never had a custom rom.
This is what the screen in download mode shows:
ODIN MODE
PRODUCT NAME : GT-I9195
CURRENT BINARY: samsung official
SYSTEM STATUS: Official
KNOX KERNEL LOCK : 0x0
KNOX WARRANTY VOID : 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER RP SWREV: 2
WRITE PROTECTION ENABLE
I tried lot of things, but my last resort is to ask, if you have anything to help i appreciate!
maybe should try stock rom next with odin.
S3miniFin said:
maybe should try stock rom next with odin.
Click to expand...
Click to collapse
Already tried many stock firmwares for i9195 , when odins flashes it, it reboots to recovery and it says "NO COMMAND" ( Sin comandos ) then reboots and starts again with that.
Did you get this fixed mate. I'm pulling my hair out with the same problem. My son messed up a perfectly good phone that I had used for 3 years, and the toerag won't tell me what he did. (apparently he was texting when it when down) Tried various version of stock ROM and I get get diddly squat. ODIN fails to write the firmware and I get aboot on the phone screen. Current problem is stuck on Bootloop. Might just throw the thing away and buy a new one. Would like to fix it though....I'd be eternally grateful for any advice....Thnx
Capokhatpin,
Your son didn't do anything to your phone ! It's just faulty hardware and common problem to Samsung S4 Mini ...
And until now there are dozens of phones that are broken and there is still no solution for that problem.
So, leave the kid alone ...
Cheers !
I have the similar problem at my i9195 - at booting directly to recovery after "successful" flash of cwm over odin or heimdall, the stock recovery appears again without any change...
So did I understand it correctly that there is no chance to fix it?
lupus92 said:
I have the similar problem at my i9195 - at booting directly to recovery after "successful" flash of cwm over odin or heimdall, the stock recovery appears again without any change...
So did I understand it correctly that there is no chance to fix it?
Click to expand...
Click to collapse
No I think you have different problem, are you flashing cwm recovery 2x? You need to flash it once then boot immediately back into download & flash it a 2nd time. If you only do it once or you do a normal boot between flashes it will not work, start again.
2x? Hmh, i tried it (both odin and heimdall), but it doesn't work either (also 3x or 4x)... again just stock recovery.
The story behind it: An update from stock rom failed, and after it it stuck at boot logo. When starting recovery, error messages that mounting /system failed appear. So I decided to try to flash CM on it -> first custom recovery. I tried the CM recovery, CWM recovery, Twrp.... No success. In Odin mode it says "Current Binary: Samsung Official" and "System Status: Official".
Any ideas how to fix it?
lupus92 said:
2x? Hmh, i tried it (both odin and heimdall), but it doesn't work either (also 3x or 4x)... again just stock recovery.
The story behind it: An update from stock rom failed, and after it it stuck at boot logo. When starting recovery, error messages that mounting /system failed appear. So I decided to try to flash CM on it -> first custom recovery. I tried the CM recovery, CWM recovery, Twrp.... No success. In Odin mode it says "Current Binary: Samsung Official" and "System Status: Official".
Any ideas how to fix it?
Click to expand...
Click to collapse
I couldn't do it, i threw it away, just give the kid a slap, don't keep trying, you deserve better.
God**** phone.
IronRoo said:
No I think you have different problem, are you flashing cwm recovery 2x? You need to flash it once then boot immediately back into download & flash it a 2nd time. If you only do it once or you do a normal boot between flashes it will not work, start again.
Click to expand...
Click to collapse
So, I tried also to flash the stock ROM by booting it with „debrick“ image from SD card and flashing from „download mode“ went good, but after reboot it was same and I couldn't boot into „recovery“ with message „No command....“ or something like that. And You write that I have to flash only CWM or other TWRP recovery and then twice in the row. Is that correct ?
Sent from my GT-N7000 using XDA-Developers mobile app
Boombastical said:
So, I tried also to flash the stock ROM by booting it with â??debrickâ?? image from SD card and flashing from â??download modeâ?? went good, but after reboot it was same and I couldn't boot into â??recoveryâ?? with message â??No command....â?? or something like that. And You write that I have to flash only CWM or other TWRP recovery and then twice in the row. Is that correct ?
Click to expand...
Click to collapse
No, sorry I misunderstood @lupus92 original situation.
Boombastical said:
So, I tried also to flash the stock ROM by booting it with �¢??debrick�¢?? image from SD card and flashing from �¢??download mode�¢?? went good, but after reboot it was same and I couldn't boot into �¢??recovery�¢?? with message �¢??No command....�¢?? or something like that. And You write that I have to flash only CWM or other TWRP recovery and then twice in the row. Is that correct ?
Click to expand...
Click to collapse
jobs done so back to xda.
I have wondered if in situations like the above where nothing seems to work if a nand erase in Odin would help, but I've never seen it mentioned here on the S4 Mini forum. Is there a reason?
I've not researched it or tried it, but have seen it done on other forums (maybe the S4????). You have to use the full original stock firmware that originally came with your phone at the SAME TIME (else it will brick) I think and have a back up of your imei (though it should rebuild?). I'm not even sure if it deletes ALL partitions or leaves some ..... might be worth looking into it. @lupus92
IronRoo said:
jobs done so back to xda.
I have wondered if in situations like the above where nothing seems to work if a nand erase in Odin would help, but I've never seen it mentioned here on the S4 Mini forum. Is there a reason?
I've not researched it or tried it, but have seen it done on other forums (maybe the S4????). You have to use the full original stock firmware that originally came with your phone at the SAME TIME (else it will brick) I think and have a back up of your imei (though it should rebuild?). I'm not even sure if it deletes ALL partitions or leaves some ..... might be worth looking into it. @lupus92
Click to expand...
Click to collapse
I have here an S4 Mini and when I boot it with SD Card and 'debrick' image on it, it always fail to write to nand but it allow me to go to 'download mode' and to flash original stock ROM but after succesful flashing and reboot it still have no acces to recovery...
Does flashing only any custom recovery would help ?
Any idea ?
Sent from my GT-N7000 using XDA-Developers mobile app
Boombastical said:
I have here an S4 Mini and when I boot it with SD Card and 'debrick' image on it, it always fail to write to nand but it allow me to go to 'download mode' and to flash original stock ROM but after succesful flashing and reboot it still have no acces to recovery...
Does flashing only any custom recovery would help ?
Any idea ?
Click to expand...
Click to collapse
I don't think another recovery will help, but I'm no expert about this sort of thing. I would say it's worth a try through.
If that doesn't work and you are at the point of throwing your phone away, I wonder if it's worth giving the "nand erase all" command a try as it has been shown to fix write permissions (though I'm not sure if this is your problem) and other major issues software issues. But as it deletes the entire nand memory so you need to be very careful & know exactly what will hapen. You need a backup of your efs/imei (I'd use 2 methods just to be sure as have just read someone couldn't restore it from some app),( can you boot into system?) Also you must use a FULL stock ROM with pit file etc to rebuild partitions.
For example the guy below with a regular S4 seems to be in similar situation, though for different reason, he was able to recover using nand erase all. But our phone is different of course!
Also have read one case where guy had to flash stock with nand erase all ticked then had to immediately reflash stock again without erase ticked.
http://forum.xda-developers.com/galaxy-s4/help/help-nand-erase-t2863345
--–-------------------------------------
edit; Also another S4 thread they have flashed bootloaders to fix write access to partitions,
http://forum.xda-developers.com/showthread.php?t=1840030
&
http://www.androidauthority.com/galaxy-s3-i535-unbrick-soft-brick-125413/
IronRoo said:
I don't think another recovery will help, but I'm no expert about this sort of thing. I would say it's worth a try through.
If that doesn't work and you are at the point of throwing your phone away, I wonder if it's worth giving the "nand erase all" command a try as it has been shown to fix write permissions (though I'm not sure if this is your problem) and other major issues software issues. But as it deletes the entire nand memory so you need to be very careful & know exactly what will hapen. You need a backup of your efs/imei (I'd use 2 methods just to be sure as have just read someone couldn't restore it from some app),( can you boot into system?) Also you must use a FULL stock ROM with pit file etc to rebuild partitions.
For example the guy below with a regular S4 seems to be in similar situation, though for different reason, he was able to recover using nand erase all. But our phone is different of course!
Also have read one case where guy had to flash stock with nand erase all ticked then had to immediately reflash stock again without erase ticked.
http://forum.xda-developers.com/galaxy-s4/help/help-nand-erase-t2863345
--–-------------------------------------
edit; Also another S4 thread they have flashed bootloaders to fix write access to partitions,
http://forum.xda-developers.com/showthread.php?t=1840030
&
http://www.androidauthority.com/galaxy-s3-i535-unbrick-soft-brick-125413/
Click to expand...
Click to collapse
Thanks for sharing your thoutghs, but unfortunately I can't boot anymore to 'Download mode'. [emoji45] It can be still booted by 'Debrick' image from SD card but nothing more then that. From there I can't go anywhere further. Without SD Card it doesn't give signs of life except if it is attached via USB it shows as QHSUSB_DLOAD...
I have no time now to play with the phone, but I will try in the weekend again to come to 'Download mode' and to flash again recovery or to erase flash nand cause I have already EFS back up somewhere on my external HD and then we will see what will happened. Thanks again and cheers !
Edit: I can't flash anything thru 'Debrick image' via Odin 3.09. It always give error: Faild to write mmc nand... It can't erase nand nor boot to 'Download mode' ... So I'm clueless at the moment... It looks as the nand is damaged and it can't be accessed anymore... Sadly, I think this S4 Mini will be ended as spare phone for parts only for my girlfriend phone... That's it... If someone have more ideas about it I can still try it... Cheers !
Sent from my GT-N7000 using XDA-Developers mobile app