I recently purchased a Galaxy Note 4 on EBAY running stock firmware and activated it on my cellular network with no issues. The phone works fine i.e calls, texts, other functions. I am however faced with a Wi-Fi issue. If I ever power off my phone and turn it back on, the Wi-Fi fails to automatically connect. I have to manually reconnect and every time I do so I get a message that says" the phone in in factory mode and wifi is now turning off, change to user mode, "This message does not stay for too long on the screen. I used ODIN to redo the stock firmware. It was during this process that i noticed the messages (mention below) in recovery mode.
E: failed to mount /efs (invalid argument)
dm-verity verification failed...
I still went ahead and re flashed the stock firmware assuming it would fix all issues, but it did not. Not sure if this phone was rooted at sometime or not. Any help would be much appreciated.
I have used ODIN to flash stick US Cellualr ROM, but problem still exists.
4dloveofgod said:
I recently purchased a Galaxy Note 4 on EBAY running stock firmware and activated it on my cellular network with no issues. The phone works fine i.e calls, texts, other functions. I am however faced with a Wi-Fi issue. If I ever power off my phone and turn it back on, the Wi-Fi fails to automatically connect. I have to manually reconnect and every time I do so I get a message that says" the phone in in factory mode and wifi is now turning off, change to user mode, "This message does not stay for too long on the screen. I used ODIN to redo the stock firmware. It was during this process that i noticed the messages (mention below) in recovery mode.
E: failed to mount /efs (invalid argument)
dm-verity verification failed...
I still went ahead and re flashed the stock firmware assuming it would fix all issues, but it did not. Not sure if this phone was rooted at sometime or not. Any help would be much appreciated.
I have used ODIN to flash stick US Cellualr ROM, but problem still exists.
Click to expand...
Click to collapse
Whats your model number shows in download odin mode ?
4dloveofgod said:
I recently purchased a Galaxy Note 4 on EBAY running stock firmware and activated it on my cellular network with no issues. The phone works fine i.e calls, texts, other functions. I am however faced with a Wi-Fi issue. If I ever power off my phone and turn it back on, the Wi-Fi fails to automatically connect. I have to manually reconnect and every time I do so I get a message that says" the phone in in factory mode and wifi is now turning off, change to user mode, "This message does not stay for too long on the screen. I used ODIN to redo the stock firmware. It was during this process that i noticed the messages (mention below) in recovery mode.
E: failed to mount /efs (invalid argument)
dm-verity verification failed...
I still went ahead and re flashed the stock firmware assuming it would fix all issues, but it did not. Not sure if this phone was rooted at sometime or not. Any help would be much appreciated.
I have used ODIN to flash stick US Cellualr ROM, but problem still exists.
Click to expand...
Click to collapse
Did you have a back uo of your efs files? That contains your imei which if its corrupted is very hard to revive.... and by the sounds of it yours could be corrupted.
Can you get into the phone now will it boot?
Note 4 (US Cellular) model N910R4
callumbr1 said:
Did you have a back uo of your efs files? That contains your imei which if its corrupted is very hard to revive.... and by the sounds of it yours could be corrupted.
Can you get into the phone now will it boot?
Click to expand...
Click to collapse
I am able to use the phone and have also used it on the cellular network, was wondering how I could resolve the mentioned issue. The phone must have been rooted at some point and it wasn't done by me, so I do not have a back up of the efs folder.
4dloveofgod said:
I am able to use the phone and have also used it on the cellular network, was wondering how I could resolve the mentioned issue. The phone must have been rooted at some point and it wasn't done by me, so I do not have a back up of the efs folder.
Click to expand...
Click to collapse
As long as the phone works thats good. Just boot to twrp and back up efs folder just incase. As for your issue i would of thought flashing stock would of fixed it. Have you wiped dalvik and cache?
Try to Make a full backup then flash a stock firmware with pit file of your exactly device
Related
Kitkat 4.4.2 is now available on Galaxy S III mini (ATT) G730A.
Just came through ATT OTA update today, but was officially released on 8/27/14
From ATT:
"Update summary
On August 27, 2014, AT&T and Samsung released a software update for the Samsung Galaxy S III mini (SM-G730A). This software package updates the OS to Android 4.4.2 (Kit Kat). The update file is 700 MB, and is available for download via Wi-Fi only."
Official new versions:
Android version: 4.4.2
Baseband version: G730AUCUBNG3
Build number: KOT49H.G730AUCUBNG3
Official Link (replace "[dot]" with "."). Sorry for being a newb....
www[dot]att[dot]com/esupport/softwareUpdateArticle.jsp?sid=KB424695
Hopefully saferoot or some other method will work with this update. :fingers-crossed:
I saw a software update being download through my phone which was killing my battery. I called Samsung to see what was going on.
I'm pretty sure I weirded out the Samsung rep on the phone because I was ECSTATIC when she said "well, it looks like you should actually be running 4.4.2"
jakitgt said:
Kitkat 4.4.2 is now available on Galaxy S III mini (ATT) G730A.
Just came through ATT OTA update today, but was officially released on 8/27/14
From ATT:
"Update summary
On August 27, 2014, AT&T and Samsung released a software update for the Samsung Galaxy S III mini (SM-G730A). This software package updates the OS to Android 4.4.2 (Kit Kat). The update file is 700 MB, and is available for download via Wi-Fi only."
Official new versions:
Android version: 4.4.2
Baseband version: G730AUCUBNG3
Build number: KOT49H.G730AUCUBNG3
Official Link (replace "[dot]" with "."). Sorry for being a newb....
www[dot]att[dot]com/esupport/softwareUpdateArticle.jsp?sid=KB424695
Click to expand...
Click to collapse
In S3 Mini I8190 want!
None of the root procedures that worked for 4.2.2 will work for 4.4.2 :crying:
rdk2k said:
None of the root procedures that worked for 4.2.2 will work for 4.4.2 :crying:
Click to expand...
Click to collapse
Root needs to be figured out asap then haha! Just glad they kept their word and finally updated it though! :good::laugh::highfive:
My heart broken Maybe GT-I8190 ? porting etc.
MehmetAliCan said:
My heart broken Maybe GT-I8190 ? porting etc.
Click to expand...
Click to collapse
If I would have known - I would have tried to capture the OTA update...
Don't Apply Update to an Encrypted Phone!!!!
I made what I think is a fatal error in applying this update...two errors, actually...
1. Didn't have contacts, texts, various docs, etc stored on internal memory backed up to the could, external computer, etc
2. Applied update before decrypting the phone (I keep it encrypted for security reasons obviously but this may have just bitten me in the butt)
So here's happened when I applied the update. First, there was no warning not to apply it to an encrypted phone (found this out from an AT&T Device Support Center technician, who also told me the update was pushed direct by Samsung and not AT&T and really did try to help me out of this jam). I selected yes to apply the update, then it prompted me for my password 2 or 3 times at it went thru the update/reboot process. No problem, right? Well when it appeared to have completed, it went back to the lock screen on bootup, I typed in my password, the green "android crypto unlock" image came on, then...nothing. screen went black and phone locked up. Restarted several times and same thing happened. Restarted in safe mode and same thing happened. Tried hooking up to my computer and accessing thru Windows and Samsung Kies...nothing. Phone connects to computer, but it isn't recognized and no access (neither before nor after typing password into phone). Went into the phone's system recovery mode and rebooted from there and same thing happened - get to unlock screen, type password, and locks. In the phone's system recovery screen, I get the following at the bottom of the screen:
#MANUAL MODE#
-- Appling Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC.
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_log.txt
I have not yet done a "wipe data/factory reset" nor had AT&T wipe and reset the phone at their Device Service Center as I really really really need to recover some data that is now locked on the phone and I can't seem to get past the encryption even with password as it appears the encryption corrupted the OS update installation. Neither 3 hrs with a very helpful AT&T tech nor an hour on the phone with Samsung tech was able to get me into the phone to at least recover data. If i can just recover the data, at that point I have no problem doing a factory reset (and taking a harsh lesson learned) and rebuilding the phone. But I want to exhaust all possible options at data recovery before I go that route, and any help any of you out there can provide would be greatly appreciated. Maybe a way to extract an image of the phone's internal storage to a computer and then decrypt that image to extract the data? Maybe a way to remotely decrypt the phone's internal storage over USB connected to a computer and then extract data that way?
I asked both Samsung and AT&T if they had an FTP site or something where I could download the update to a microSD card and try re-applying the update from external storage (which at least in theory would preserve user data during the update) in the system recovery boot module but both said they couldn't do it. Which I think is BS, since that 700MB file has to come from somewhere. I'm guessing they only want the update distributed via OTA or Kies not as a separate installer package that could be easily shared.
That's about it. I'm really hoping someone can help me out of this jam, but am prepared for the worst - data loss and associated harsh lessons learned. Thanks for listening and I hope no one else out there makes the same mistake I did.
Rob
Trying to Odin back to 4.2.2 results in an error and soft bricks the phone. At least my phone is still under warranty and there are no signs of me moding the phone, so i'll be shipping it to Samsung tomorrow.
2317
Can someone please put the firmware on mega or firedrive or something im not getting the update. and SamMobile has old firmware www[dot]sammobile[dot]com/firmwares/3/?download=22911
hkjr said:
If I would have known - I would have tried to capture the OTA update...
Click to expand...
Click to collapse
If you want to go through the trouble, can you Odin back to 4.2 and grab the 4.4.2 OTA update again?
KaneVanguard said:
Can someone please put the firmware on mega or firedrive or something im not getting the update. and SamMobile has old firmware www[dot]sammobile[dot]com/firmwares/3/?download=22911
Click to expand...
Click to collapse
OTA update is downloading a zip file called /data/fota/2400258.cfg, I'll try to capture it. Hoping it doesn't delete it before I can get to it
It's the same filename as the OTA updates for other S 4.4.2 devices but I would guess not the same contents.
I have the 4.4.2 update in place but need to root my device to get rid of all the bloatware again. Anyone finding any success with root apps?
maybe towelroot?
djdevin said:
maybe towelroot?
Click to expand...
Click to collapse
Tried that one. It says my model is not currently supported.
Boo. I know towelroot is configurable, maybe another modstring will work.
Anyways here's the OTA update
https://mega.co.nz/#!r1lxzISZ!5KD71NdDu8Lj96G2mXFlbk75tQgzAZg7FEyHMEkajgA
Warning, none of the below worked for me and I had to restore
I assume this is the install process
Download OTA file
Change 2400258.cfg name to update.zip
Connect your phone to your PC and then move the update.zip file to the phone's /cache
Disconnect the phone from PC, power off the phone and then boot it in Recovery Mode.
Select the ‘Apply Update.zip’ from cache
OR
Apply update from adb
Then adb sideload 2400258.cfg from your computer
Wait until the install process is complete and then reboot your phone in normal mode.
Same as http://www.android.gs/flash-official-android-4-4-2-kk-update-for-att-galaxy-s4/ except with a different file.
rob.rossi97 said:
I made what I think is a fatal error in applying this update...two errors, actually...
1. Didn't have contacts, texts, various docs, etc stored on internal memory backed up to the could, external computer, etc
2. Applied update before decrypting the phone (I keep it encrypted for security reasons obviously but this may have just bitten me in the butt)
So here's happened when I applied the update. First, there was no warning not to apply it to an encrypted phone (found this out from an AT&T Device Support Center technician, who also told me the update was pushed direct by Samsung and not AT&T and really did try to help me out of this jam). I selected yes to apply the update, then it prompted me for my password 2 or 3 times at it went thru the update/reboot process. No problem, right? Well when it appeared to have completed, it went back to the lock screen on bootup, I typed in my password, the green "android crypto unlock" image came on, then...nothing. screen went black and phone locked up. Restarted several times and same thing happened. Restarted in safe mode and same thing happened. Tried hooking up to my computer and accessing thru Windows and Samsung Kies...nothing. Phone connects to computer, but it isn't recognized and no access (neither before nor after typing password into phone). Went into the phone's system recovery mode and rebooted from there and same thing happened - get to unlock screen, type password, and locks. In the phone's system recovery screen, I get the following at the bottom of the screen:
#MANUAL MODE#
-- Appling Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC.
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_log.txt
I have not yet done a "wipe data/factory reset" nor had AT&T wipe and reset the phone at their Device Service Center as I really really really need to recover some data that is now locked on the phone and I can't seem to get past the encryption even with password as it appears the encryption corrupted the OS update installation. Neither 3 hrs with a very helpful AT&T tech nor an hour on the phone with Samsung tech was able to get me into the phone to at least recover data. If i can just recover the data, at that point I have no problem doing a factory reset (and taking a harsh lesson learned) and rebuilding the phone. But I want to exhaust all possible options at data recovery before I go that route, and any help any of you out there can provide would be greatly appreciated. Maybe a way to extract an image of the phone's internal storage to a computer and then decrypt that image to extract the data? Maybe a way to remotely decrypt the phone's internal storage over USB connected to a computer and then extract data that way?
I asked both Samsung and AT&T if they had an FTP site or something where I could download the update to a microSD card and try re-applying the update from external storage (which at least in theory would preserve user data during the update) in the system recovery boot module but both said they couldn't do it. Which I think is BS, since that 700MB file has to come from somewhere. I'm guessing they only want the update distributed via OTA or Kies not as a separate installer package that could be easily shared.
That's about it. I'm really hoping someone can help me out of this jam, but am prepared for the worst - data loss and associated harsh lessons learned. Thanks for listening and I hope no one else out there makes the same mistake I did.
Rob
Click to expand...
Click to collapse
Too late. Think I just bricked it too, OTA update failed so it probably wasn't just you.
Correction: I was able to get back to 4.2.2, I used PDA instead of Phone in ODIN. My guess is that the bootloader has to be flashed first before reverting to 4.2.2. However I did a clean wipe many times before so I'm not sure if it did that, in your case it would not be preferred.
I'm seriously sick over this bootloader BS, enough to never buy a Samsung electronic device ever again. Or deal with AT&T in any capacity ever again.
@SamsungSupport gave me a pretty good "we don't care" conversation: https://twitter.com/SamsungSupport/status/507252356657184768
djdevin said:
Too late. Think I just bricked it too, OTA update failed so it probably wasn't just you.
Correction: I was able to get back to 4.2.2, I used PDA instead of Phone in ODIN. My guess is that the bootloader has to be flashed first before reverting to 4.2.2. However I did a clean wipe many times before so I'm not sure if it did that, in your case it would not be preferred.
I'm seriously sick over this bootloader BS, enough to never buy a Samsung electronic device ever again. Or deal with AT&T in any capacity ever again.
@SamsungSupport gave me a pretty good "we don't care" conversation: https://twitter.com/SamsungSupport/status/507252356657184768
Click to expand...
Click to collapse
How did you manage that? I stupidly tried to downgrade with Odin and have a soft-brick on my hands. I've tried everything I can think of. I wish SamMobile had the 4.4.2 firmware.
Update made the phone slower and laggy. Someone needs to find a working root method
I got an error saying Unfortunately context service stopped working. I couldn't click anything so i restarted my phone. Got stuck on a samsung logo loop. Used odin to restore a stock firmware that i downloaded from here. https://forum.xda-developers.com/sa...on5s-sm-g550t-sm-g550t1-stuck-custom-t3647988 . But now i get a "No SIM card l no network connection" when the screen is locked. Under SIM status everything is "not available", and under IMEI everything is unknown.
Edit: I took 2 steps then it worked. not sure if the first one helped.
1) Deleted my EFS file by going to twrp > mount >tick efs> advanced file manager> then delete the whole folder then reboot. (this didnt fix my problem)
2) go to odin use the files from the link above and only used the CP file. REBOOT, FIXED.
Can I delete this post or should I leave it up thank you!
Please leave it up
Hi Guys
This is my first post on xda even after using these forums for years. But today I cant find a solution on here or anywhere for that fact, and was literally hoping that I've missed something somewhere.
So to start. I have a Samsung Galaxy J5 Prime (SM-G570F). The other day I was flashing a custom rom when something went wrong during the flashing process and left me with a bricked device. Now I did do a full backup before flashing as I've learned the hard way how important this is. During the flashing it also asked me for a full wipe and to backup the EFS. Even though I did do all the backups and wiped everything< I've ticked both boxes and proceeded with the installation. Everything seemed fine but on 99.9% it froze. Not wanting to do anything I left it until it rebooted the phone by itself, where I was greeted with the download/flash screen. Didn't even give the warning about installing custom software and asked to continue. It just booted straight to the download screen. Tried getting back into recovery only to be greeted with download screen. No matter what I did it just kept booting into download mode. So I then re-flashed TWRP. Getting into the recovery I was able to mount EFS, System, Data, etc. Bu all showed 0mb of 0mb available. I then went to restore everything only to find that the SD Card was also wiped by the process. Thinking that maybe the recovery isn't reading everything correctly, I found the SD Card empty in windows also. No call me names or whatever, (I know my own stupidity) but I never backed up my backups on my PC. So I just proceeded flashing stock firmware as to start from scratch. Everything went as planned until the device got reset by odin. I was greeted with a screen saying "installing system update", but as soon as it reach 32% it changes to "erasing" and then "error" with the "DRK Missing" error. Then it boots to recovery where an error message is saying "unable to mount: EFS (Device or Recourse busy). I cleared cache and did a factory reset and it booted the system (Though mount error still appears in recovery even in custom TWRP/CWM recoveries also). Now I have a 00000..... IMEI number and no network connection. I've spent the last week on the web trying to find a solution with no luck. I'm tired AF because I didn't sleep trying to solve this. I tried flashing stock and custom roms, recovery's, boot-loaders, modems. Tried different software's like Samsung Tool, IMEI repair tool, Strings of adb commands, xposed modules, apps, terminals, etc. I even flashed factory binaries with no luck as to how to change it back.
So in short.
My EFS got wiped.
I lost my IMEI.
I don't have any backups.
Been awake for a week searching for solutions with no luck.
So please if anyone knows of a way to change the IMEI, please help me. I know It's illegal to change IMEI (though not in my country). But I down't want to change it for all the wrong reasons. I just want to change it back to the original found on the back of the phone and on the box. This can't do any harm can it? Please I just want my phone back please!
Full phone info with current firmware:
Samsung Galaxy J5 Prime (SM-G570F)
Android version - Nougat 7.0
Baseband version - G570FXXU1BQI6
Stock Firmware
No Root
No custom recovery
(Basically I just flashed everything back to stock to start over and try solving this)
Please help guys
I am in the same problem
Did you able to overcome from this problem, if yes please tell me the solution please!
I also have same issue.plz tell me what to do.
P01Z0N-T0N1C said:
Hi Guys
This is my first post on xda even after using these forums for years. But today I cant find a solution on here or anywhere for that fact, and was literally hoping that I've missed something somewhere.
So to start. I have a Samsung Galaxy J5 Prime (SM-G570F). The other day I was flashing a custom rom when something went wrong during the flashing process and left me with a bricked device. Now I did do a full backup before flashing as I've learned the hard way how important this is. During the flashing it also asked me for a full wipe and to backup the EFS. Even though I did do all the backups and wiped everything< I've ticked both boxes and proceeded with the installation. Everything seemed fine but on 99.9% it froze. Not wanting to do anything I left it until it rebooted the phone by itself, where I was greeted with the download/flash screen. Didn't even give the warning about installing custom software and asked to continue. It just booted straight to the download screen. Tried getting back into recovery only to be greeted with download screen. No matter what I did it just kept booting into download mode. So I then re-flashed TWRP. Getting into the recovery I was able to mount EFS, System, Data, etc. Bu all showed 0mb of 0mb available. I then went to restore everything only to find that the SD Card was also wiped by the process. Thinking that maybe the recovery isn't reading everything correctly, I found the SD Card empty in windows also. No call me names or whatever, (I know my own stupidity) but I never backed up my backups on my PC. So I just proceeded flashing stock firmware as to start from scratch. Everything went as planned until the device got reset by odin. I was greeted with a screen saying "installing system update", but as soon as it reach 32% it changes to "erasing" and then "error" with the "DRK Missing" error. Then it boots to recovery where an error message is saying "unable to mount: EFS (Device or Recourse busy). I cleared cache and did a factory reset and it booted the system (Though mount error still appears in recovery even in custom TWRP/CWM recoveries also). Now I have a 00000..... IMEI number and no network connection. I've spent the last week on the web trying to find a solution with no luck. I'm tired AF because I didn't sleep trying to solve this. I tried flashing stock and custom roms, recovery's, boot-loaders, modems. Tried different software's like Samsung Tool, IMEI repair tool, Strings of adb commands, xposed modules, apps, terminals, etc. I even flashed factory binaries with no luck as to how to change it back.
So in short.
My EFS got wiped.
I lost my IMEI.
I don't have any backups.
Been awake for a week searching for solutions with no luck.
So please if anyone knows of a way to change the IMEI, please help me. I know It's illegal to change IMEI (though not in my country). But I down't want to change it for all the wrong reasons. I just want to change it back to the original found on the back of the phone and on the box. This can't do any harm can it? Please I just want my phone back please!
Full phone info with current firmware:
Samsung Galaxy J5 Prime (SM-G570F)
Android version - Nougat 7.0
Baseband version - G570FXXU1BQI6
Stock Firmware
No Root
No custom recovery
(Basically I just flashed everything back to stock to start over and try solving this)
Please help guys
Click to expand...
Click to collapse
If this problem is still open, then on Your Phone box is writen imei, or take battery out and under serial number there will be your imei, root your device and use IMEI changer grant root access and type your imei in it, after that reboot and your imei should pop up! I had same issue and this steps made my day! THIS WORKS ONLY ON YOUR IMEI, YOU CAN'T CRACK, STEAL IMEI By this method, don't believe those Dumb ****'s from YouTube!
May I help You!
P01Z0N-T0N1C said:
Hi Guys
This is my first post on xda even after using these forums for years. But today I cant find a solution on here or anywhere for that fact, and was literally hoping that I've missed something somewhere.
So to start. I have a Samsung Galaxy J5 Prime (SM-G570F). The other day I was flashing a custom rom when something went wrong during the flashing process and left me with a bricked device. Now I did do a full backup before flashing as I've learned the hard way how important this is. During the flashing it also asked me for a full wipe and to backup the EFS. Even though I did do all the backups and wiped everything< I've ticked both boxes and proceeded with the installation. Everything seemed fine but on 99.9% it froze. Not wanting to do anything I left it until it rebooted the phone by itself, where I was greeted with the download/flash screen. Didn't even give the warning about installing custom software and asked to continue. It just booted straight to the download screen. Tried getting back into recovery only to be greeted with download screen. No matter what I did it just kept booting into download mode. So I then re-flashed TWRP. Getting into the recovery I was able to mount EFS, System, Data, etc. Bu all showed 0mb of 0mb available. I then went to restore everything only to find that the SD Card was also wiped by the process. Thinking that maybe the recovery isn't reading everything correctly, I found the SD Card empty in windows also. No call me names or whatever, (I know my own stupidity) but I never backed up my backups on my PC. So I just proceeded flashing stock firmware as to start from scratch. Everything went as planned until the device got reset by odin. I was greeted with a screen saying "installing system update", but as soon as it reach 32% it changes to "erasing" and then "error" with the "DRK Missing" error. Then it boots to recovery where an error message is saying "unable to mount: EFS (Device or Recourse busy). I cleared cache and did a factory reset and it booted the system (Though mount error still appears in recovery even in custom TWRP/CWM recoveries also). Now I have a 00000..... IMEI number and no network connection. I've spent the last week on the web trying to find a solution with no luck. I'm tired AF because I didn't sleep trying to solve this. I tried flashing stock and custom roms, recovery's, boot-loaders, modems. Tried different software's like Samsung Tool, IMEI repair tool, Strings of adb commands, xposed modules, apps, terminals, etc. I even flashed factory binaries with no luck as to how to change it back.
So in short.
My EFS got wiped.
I lost my IMEI.
I don't have any backups.
Been awake for a week searching for solutions with no luck.
So please if anyone knows of a way to change the IMEI, please help me. I know It's illegal to change IMEI (though not in my country). But I down't want to change it for all the wrong reasons. I just want to change it back to the original found on the back of the phone and on the box. This can't do any harm can it? Please I just want my phone back please!
Full phone info with current firmware:
Samsung Galaxy J5 Prime (SM-G570F)
Android version - Nougat 7.0
Baseband version - G570FXXU1BQI6
Stock Firmware
No Root
No custom recovery
(Basically I just flashed everything back to stock to start over and try solving this)
Please help guys
Click to expand...
Click to collapse
As i Read Your Post
So I realized that You are Also facing a problem Like me and now Mine is Solved
Just dont upgrade Your Mobile and Downgrade to android 6.0.1
and try to flash someone else efs and then it wil give u ur own imei and u will be hapy
Thanks
My note 4, randomly crashed, running completely stock.
Began bootlooping and hasn't stopped.
Have downloaded firmwares from Samsung-Firmware . org, as SamMobile will literally not allow me to download anything for free??
No firmware has worked on the device, Have tried numerous PDA versions as I am unsure which the phone originally is.
The first firmware gave the error "dm-verity verification failed" in the recovery menu.
Have wiped cache and data.
Note: This is actually the second N910F which had corrupted itself and stopped working.
Help! :angel:
Do you want to recover some data from it?
If Not than you can try factory reset from Recovery menu.
Other than that it might be memory corrupted or your battery.
Try to change the battery.
a602820922 said:
Do you want to recover some data from it?
If Not than you can try factory reset from Recovery menu.
Other than that it might be memory corrupted or your battery.
Try to change the battery.
Click to expand...
Click to collapse
No data to recover, have tried factory reset from recovery menu, sure will try another battery.
a602820922 said:
Do you want to recover some data from it?
If Not than you can try factory reset from Recovery menu.
Other than that it might be memory corrupted or your battery.
Try to change the battery.
Click to expand...
Click to collapse
New battery: Allowed the phone to boot past the first "Samsung Note 4" screen to : "Samsung" logo, but the phone made a loud beep/screech.
If you want to reflash the Stock ROM search for a version on https://updato.com
I just reflashed mine (g910f) even twice as I had an Infini-Boot, too. After cleaning Dalvik/Cache and formatting data, taking out the battery, after some time it suddenly displayed that it's going to setup apps and it works since then ...
So maybe just be patient.
TheEnda619 said:
My note 4, randomly crashed, running completely stock.
Began bootlooping and hasn't stopped.
Have downloaded firmwares from Samsung-Firmware . org, as SamMobile will literally not allow me to download anything for free??
No firmware has worked on the device, Have tried numerous PDA versions as I am unsure which the phone originally is.
The first firmware gave the error "dm-verity verification failed" in the recovery menu.
Have wiped cache and data.
Note: This is actually the second N910F which had corrupted itself and stopped working.
Help! :angel:
Click to expand...
Click to collapse
to get the latest stock rom for your device, free and fast
look what you have to do:
download this (windows ) application and install it on your windows pc.
This is the aplication that will allow you to search and download the latest stock rom for your phone.
It connect to Samsung servers and in very little time you will have a new stock rom on your pc.
choose samfirm 3.06
extract it on a folder on your PC and run samfirm.exe
in the opening menu type
SM-N910F(or T/V/W etc your phones model)
REGION..... xxx (your region code)
these 2 you can find in a sticker under your battery if you open the phone and take off the battery
tick '' BINARY NATURE''
(If you dont tick BINARY...'' you will get the whole stock rom in one file xxxx.tar.md5 to flash it in the oding using the AP tab)
CHECK UPDATES>DOWNLOAD
THIS WAY YOU WILL GET THE LATEST STOCK ROM FOR YOUR PHONE/REGION
Binary nature means the rom split in 4 files
1. BL- bootloader
2.AP - rom
3. CP - modem
4. CSC - Customer support code(region/country)
This is what a stock rom is consist of
this kind of rom is also called REPAIR ROM, because you can use it to repair your phone.
If you look in odin you will find exactly these 4 entries.
So you can put each in the appropriate box and flash them all and so have a stock rom.
push start
Wait until rom flashes and phone reboots.
Hopefully it will solve your problem and everything will go as we all wish to.
BUT, from what you are describing, i am afraid for 2 things:
1. Your battery is almost dead, thats the good scenario .
With 20 $ you will solve it.
So new battery, new rom> problem solved, or
2. You are starting to have the emmc failure on your phone.
Thats a tough one.
Lets hope its not the case.
Just in case
https://forum.xda-developers.com/note-4/help/note-4-freezing-restarting-t3348821
https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
good luck my friend
Hey guys, I done goofed. Big time. And I'm aware of that.
I was an a 9.0 rom (can't remember which one unfortunately) and my stupid ass tried to flash a 8.0 official firmware via odin to get back to stock.
Yes, exactly.
Obviously odin didn't even try to flash anything but got immediately stuck with error messages. One was "can't open the specified file (line 1892) and other times it just got stuck at "setupconnection".
I tried 2 different roms (one from samfirmware and another one from that one little download tool you can use), tried extracting the PIT file and flash everything with that, but it never flashed anything completely.
Also tried 2 different PC's and different cables, since that's always the first answer people get. And I was using ODIN 3.12 as well as 3.13.
Even though odin didn't do anything my phone wouldn't boot anymore.
Interestingly enough I can still boot into TWRP just fine.
The only issue is that TWRP can't access internal memory anymore. For instance, when I try to factory reset an wipe, I get a ton of error messages about how none of the paths could be mounted (failed to mount '/data' (invalid argument). Size is shown as 0mb.
I tried flashing a 9.0 rom from here, and aroma didn't show any error mesasges whatsoever. But upon reboot it got stuck and after 2 hours I just unplugged the cable and let it die.
When plugging it into my PC while running TWRP, the external SD card pops up as a USB drive, but the phone doesn't show up as phone.
When I tried doing that last week it didn't show any drives, no internal and no external.
Sooo... completely bricked even though I can access TWRP?
Help would be much appreciated because I'm at a loss here.
TIA
I had a similar issue. However, after a comprehensive check done by an authorized dealer, they found a hardware issue.
robotov said:
I had a similar issue. However, after a comprehensive check done by an authorized dealer, they found a hardware issue.
Click to expand...
Click to collapse
You think it's plausible that software caused a hardware failure?
hoeni said:
Hey guys, I done goofed. Big time. And I'm aware of that.
I was an a 9.0 rom (can't remember which one unfortunately) and my stupid ass tried to flash a 8.0 official firmware via odin to get back to stock.
Yes, exactly.
Obviously odin didn't even try to flash anything but got immediately stuck with error messages. One was "can't open the specified file (line 1892) and other times it just got stuck at "setupconnection".
I tried 2 different roms (one from samfirmware and another one from that one little download tool you can use), tried extracting the PIT file and flash everything with that, but it never flashed anything completely.
Also tried 2 different PC's and different cables, since that's always the first answer people get. And I was using ODIN 3.12 as well as 3.13.
Even though odin didn't do anything my phone wouldn't boot anymore.
Interestingly enough I can still boot into TWRP just fine.
The only issue is that TWRP can't access internal memory anymore. For instance, when I try to factory reset an wipe, I get a ton of error messages about how none of the paths could be mounted (failed to mount '/data' (invalid argument). Size is shown as 0mb.
I tried flashing a 9.0 rom from here, and aroma didn't show any error mesasges whatsoever. But upon reboot it got stuck and after 2 hours I just unplugged the cable and let it die.
When plugging it into my PC while running TWRP, the external SD card pops up as a USB drive, but the phone doesn't show up as phone.
When I tried doing that last week it didn't show any drives, no internal and no external.
Sooo... completely bricked even though I can access TWRP?
Help would be much appreciated because I'm at a loss here.
TIA
Click to expand...
Click to collapse
Go into Twrp and Wipe > Format Data and type Yes. This should remove encryption from your internal storage and you should be able to flash any custom rom.
For any reason if this doesn't work, you'll need a stock firmware with latest bootloader and modem version than which is currently on your device otherwise odin will just show error. The best way is to download latest firmware (october patch) for your model regardless of country and flash that via odin. Tick nand erase in odin.
Going back to android 8 from android 9 is not stupid .
I have even gone back to android 8 from android 10 since android 10 destroyed my partitions.
If your PC doesn't show Internal Storage. Go to Mount and tick system and try again.
Which firmware for S7 edge already has October patches?
Thanks.
musmax said:
Which firmware for S7 edge already has October patches?
Thanks.
Click to expand...
Click to collapse
If you have a G935F
https://www.sammobile.com/samsung/g...e/SM-G935F/VIR/download/G935FXXS6ESI4/296136/