Hi all,
A few weeks ago I made a post about my completely stock/unrooted Note 4 going into a constant boot loop. I attempted to factory reset it through recovery with no luck. The data would wipe, but I would get an error that says "E: failed to mount/preload (no such file or directory)". I thought that this was the problem, but when I received my replacement from Tmo, I was just curious and went into recovery to factory reset it the same way, and I got the same error. The replacement works fine, and there's no issues with it but it was just really bizarre why I got the same error on two different phones. Is this a tmobile note 4 thing? Also, when I enter recovery mode for some reason it attempts to install an update, and then gives me an error before actually going into the recovery. I recorded a video of the process. This was on the note 4 that was having the boot loop issue, but it looks exactly the same on the replacement. I apologize for the sound/portrait mode. https://www.youtube.com/watch?v=LOHSJo-WgaM
Basically, I'm trying to decide if this is an issue where I should ask for another replacement (that will give me problems in the future), or if this is just a random bug that won't do any harm. I really would appreciate any suggestions because I have no idea what to do.
PsychDrummer said:
Hi all,
A few weeks ago I made a post about my completely stock/unrooted Note 4 going into a constant boot loop. I attempted to factory reset it through recovery with no luck. The data would wipe, but I would get an error that says "E: failed to mount/preload (no such file or directory)". I thought that this was the problem, but when I received my replacement from Tmo, I was just curious and went into recovery to factory reset it the same way, and I got the same error. The replacement works fine, and there's no issues with it but it was just really bizarre why I got the same error on two different phones. Is this a tmobile note 4 thing? Also, when I enter recovery mode for some reason it attempts to install an update, and then gives me an error before actually going into the recovery. I recorded a video of the process. This was on the note 4 that was having the boot loop issue, but it looks exactly the same on the replacement. I apologize for the sound/portrait mode. https://www.youtube.com/watch?v=LOHSJo-WgaM
Basically, I'm trying to decide if this is an issue where I should ask for another replacement (that will give me problems in the future), or if this is just a random bug that won't do any harm. I really would appreciate any suggestions because I have no idea what to do.
Click to expand...
Click to collapse
I am not sure on the Installing Update part but the "E: failed to mount/preload (no such file or directory)" is normal so don't worry about that.
chipworkz said:
I am not sure on the Installing Update part but the "E: failed to mount/preload (no such file or directory)" is normal so don't worry about that.
Click to expand...
Click to collapse
Thanks a lot. That's reassuring. Yeah, I'm not sure why the other problem is occurring.
Related
About 4 weeks ago I installed JPH on my Bell i9000 with a lag fix. It randomly froze while I was looking at it, I wasnt even interacting with it. Pulled the battery, booted passed the Galaxy S screen but stuck on black. Recovery had nothing to say, so I re-flashed a firmware on it, and then recovery would say: E: can't mount /dev/block/mmcblk0p1. I imagine this is due to the Lagfix changing the filesystem format, and then flashing a stock RFS rom ontop, but I had absolutely no choice. After a couple days of trying to fix it, I surrendered and sent it off to Bell for repair. Got it back almost 2 weeks later, they had to replace the board.
Now flash-forward to right now.
THE SAME GOD DAMN THING HAPPENED (except this time I almost flung myself off my balcony).
Substitute JPH with JPM. Rinse & Repeat.
I haven't sent it off to Bell yet...again..But I have a feeling I will have too.
Question 1: Any clue as to why these lag-fixed 2.2 builds randomly froze and were rendered unable to boot?
Question 2: I see these "unable to mount" threads popping up but with no success stories. Is there any way to fix this on my own? I remember searching up an article with a dude explaining how to format partitions by pushing tools to the phone via ADB but I never was able to get 'er done.
Thanks for reading my tragic novel
...urge to kill...RISING...
i have had absolutely no luck with the froyo roms on my bell sgs. first time (jpk) around i got the can't mount error (device busy), but somehow fluked saving it by just reflashing back to eclair. second time (jpm) i got massive data corruption (file names "*^@)#$") and eventually lost all my data and had to reflash back to eclair.
i'm not too sure what's going on, but i suspect the international/european froyo's are incompatible with the bell sgs. from what i've read, the captivate users are running the jh2 firmware (same as us?) so i might try again with tayutama's captivate firmware.
to answer your question though, i believe there is hope if it just says "device busy" and not "device not found". keep trying to reflash if it's "device busy" and use jh2. seemed to work for me and my buddy's phone.
wang1chung said:
i have had absolutely no luck with the froyo roms on my bell sgs. first time (jpk) around i got the can't mount error (device busy), but somehow fluked saving it by just reflashing back to eclair. second time (jpm) i got massive data corruption (file names "*^@)#$") and eventually lost all my data and had to reflash back to eclair.
i'm not too sure what's going on, but i suspect the international/european froyo's are incompatible with the bell sgs. from what i've read, the captivate users are running the jh2 firmware (same as us?) so i might try again with tayutama's captivate firmware.
to answer your question though, i believe there is hope if it just says "device busy" and not "device not found". keep trying to reflash if it's "device busy" and use jh2. seemed to work for me and my buddy's phone.
Click to expand...
Click to collapse
Thanks for the info!
Ya...adb says device not found....Deja vu..
Adb does see it while in Recovery though.
well, while searching, i have found people saying not to flash any captivate roms as the bell sgs is closer to the international version than the US captive version.
might have to wait for a bell specific firmware then since i know the international ones don't work well.
Jordiharrison said:
Question 1: Any clue as to why these lag-fixed 2.2 builds randomly froze and were rendered unable to boot?
Click to expand...
Click to collapse
It Happened to me and I had no lagfix installed. The phone was not even rooted.
Jordiharrison said:
Question 2: I see these "unable to mount" threads popping up but with no success stories. Is there any way to fix this on my own? I remember searching up an article with a dude explaining how to format partitions by pushing tools to the phone via ADB but I never was able to get 'er done.
Thanks for reading my tragic novel
...urge to kill...RISING...
Click to expand...
Click to collapse
It happened to me twice. The first time was about two weeks of getting it (not rooted, no lag fix). Bell just replaced it with a brand new one.
It happened again about two or three weeks later (no lag fix). Knowing my way around linux & embedded systems, I could confirm that the kernel was not able to mount the partitions on the internal flash (mmcblk0) and they even seemed to have disappeared. I was getting the same message "E: can't mount /dev/block/mmcblk0p1". I think it's a more fundamental issue and that the internal SDcard gets permanently corrupted.
They sent the second one for repair and after three weeks of pain & frustration with the Blackberry Bold they lent me, they sent me a replacement (probably refurbished!).
Sorry, but I think you will have to send it back!
Weirdest thing happens, I'll boot my DS7 and it's like if I just did a factory reset...every time. I'll customize my homescreens/gmail and what not, and do a normal reboot and it does a factory reset every time. I've read a few threads about similar topics and no one seems to know what's going on.
I've wiped data/cache/dalvik and fixed permissions, doesn't help. Re-install ROM, doesn't help.
I tried reflashing superuser.zip says installation aborted (bad). Same when I try to flash HC (yes, I'm still on Froyo).
Any clues ladies and genitals? Any help would be appreciated.
Sounds like you are experiencing the READ-ONLY bug that plagues this device. Hopefully it is still under warranty so that you can send it to Dell. Last summer I sent my Streak 7 to Dell. They repaired the read-only bug and had it back to my house in about 2 weeks.
Basically, what happens when your tablet goes into read-only mode... any updates, installs, customizing you do will be lost upon a reset... even though it appears like things are updating, they simply are not saved to the internal flash drive. Also, when it gets really bad some of the apps (along with the web browser) will start to get fatal errors.
That sounds about right, especially since even when I try to move a file from my netbook to the device (such as a new ROM to try to flash in CWM) it wont show up after I reboot either.
Don't think its under warranty anymore, dang.
Yes this is what happened to the one I got off Craigslist too the person I bought it from also changed his phone number instantly, so I got screwed but I'm in the process of getting a replacement or getting an extended warranty on it.
Sent from my Galaxy Nexus using XDA App
Hi
I recently tried to root my phone from this guide: devs-lab.com/root-samsung-galaxy-s7-s7-edge
I followed the instructions and flashed this file from ODIN:
Samsung_G930x_QC_Rooted_BOOT.TAR
The file transferred ok and when the phone started rebooting it just stopped with a fault message on the screen.
Now the phone is stucked and i can't get contact with Odin. Odin recognizes the phone on the port but i cant flash to the phone.
The only way i have a chance to install on the phone now is with SD-card, because i am able to get to the recovery mode.
But when i try to install new stockware i just get signature failed message.
Does anyone know how i can get out of this mess ? I know its possible to turn of the signature check, but i cant get any options like this in the menu ..... BTW the phone is a G930F
I would really appreciate all help !
Thanks
Tom
Tom-72 said:
Hi
I recently tried to root my phone from this guide: devs-lab.com/root-samsung-galaxy-s7-s7-edge
I followed the instructions and flashed this file from ODIN:
Samsung_G930x_QC_Rooted_BOOT.TAR
The file transferred ok and when the phone started rebooting it just stopped with a fault message on the screen.
Now the phone is stucked and i can't get contact with Odin. Odin recognizes the phone on the port but i cant flash to the phone.
The only way i have a chance to install on the phone now is with SD-card, because i am able to get to the recovery mode.
But when i try to install new stockware i just get signature failed message.
Does anyone know how i can get out of this mess ? I know its possible to turn of the signature check, but i cant get any options like this in the menu ..... BTW the phone is a G930F
I would really appreciate all help !
Thanks
Tom
Click to expand...
Click to collapse
Which fault message are you receiving?
Sent from my SM-G930P using Tapatalk
POWerSUrgeSW3 said:
Which fault message are you receiving?
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
Hi,
I dont remember exactly the fault message because my phone has been sent to service. But i will get it back in a couple of days. Then i will tell you the entire message. But is was something about kernel fault....
The service center says i have to replace the main board on the phone which cost almost the same as a new phone....
But i'm sure the main board is not broken...
Tom
Tom-72 said:
Hi,
I dont remember exactly the fault message because my phone has been sent to service. But i will get it back in a couple of days. Then i will tell you the entire message. But is was something about kernel fault....
The service center says i have to replace the main board on the phone which cost almost the same as a new phone....
But i'm sure the main board is not broken...
Tom
Click to expand...
Click to collapse
Blah that's never good. Though I don't always trust things HAVE to be replaced at the hardware level. But it is what it is. Hopefully when you get it back all will be working for you! Unless it was just a bad chip, failing at the same time you were trying to write the new files to memory?
Sent from my SM-G930P using Tapatalk
POWerSUrgeSW3 said:
Blah that's never good. Though I don't always trust things HAVE to be replaced at the hardware level. But it is what it is. Hopefully when you get it back all will be working for you! Unless it was just a bad chip, failing at the same time you were trying to write the new files to memory?
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
Well....
Actually i'm hoping to fix the phone withouth replacing the main board since it is so expencive.
So i asked them to return it withouth replacing. Because as long as i can get the phone in recovery mode its not broken. I just need to get pass Samsungs signature verification somehow... Then i can install new firmware...
Still hoping to get help. I will post the error message as soon as i get the phone back,
Thanks so far
Tom
Tom-72 said:
Well....
Actually i'm hoping to fix the phone withouth replacing the main board since it is so expencive.
So i asked them to return it withouth replacing. Because as long as i can get the phone in recovery mode its not broken. I just need to get pass Samsungs signature verification somehow... Then i can install new firmware...
Still hoping to get help. I will post the error message as soon as i get the phone back,
Thanks so far
Tom
Click to expand...
Click to collapse
I think I did the same thing when I first got the Phoenix, and did not research and do not turn the OEM Unlock feature on. I messed up things and through a lot of reflashing and panic searching, got mine to come back.
I since have seen others post issues that sound horrible but have been recoverable. We'll help you try to figure it out once you get the phone back.
Sent from my SM-G930P using Tapatalk
POWerSUrgeSW3 said:
I think I did the same thing when I first got the Phoenix, and did not research and do not turn the OEM Unlock feature on. I messed up things and through a lot of reflashing and panic searching, got mine to come back.
I since have seen others post issues that sound horrible but have been recoverable. We'll help you try to figure it out once you get the phone back.
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
Hi, i finally got my phone back.
Been trying different things like installing new firmware by using the SD-card. And also by using ADB, since the phone allows me to install software through ADB.
But no matter what i do the phone tells that signature verification failed.
I think one fault i did when installing the twrp custom recovery from ODIN i forgot to press the key combo and it started up with the original bootloader. Then it got stuck with the error screen i told you about.
I have uploaded a picture of the error message below.
If anyone knows how to get by the signature verification test then maby i could be able to install new firmware....
Thanks again, i will be grateful for any tips that could help me !
Best Regards
Tom
Tom-72 said:
Hi, i finally got my phone back.
Been trying different things like installing new firmware by using the SD-card. And also by using ADB, since the phone allows me to install software through ADB.
But no matter what i do the phone tells that signature verification failed.
I think one fault i did when installing the twrp custom recovery from ODIN i forgot to press the key combo and it started up with the original bootloader. Then it got stuck with the error screen i told you about.
I have uploaded a picture of the error message below.
If anyone knows how to get by the signature verification test then maby i could be able to install new firmware....
Thanks again, i will be grateful for any tips that could help me !
Best Regards
Tom
Click to expand...
Click to collapse
Good NEWS !!!!!
I managed to get the phone working again...
What i did was:
Holding the volume down, home and power button at the same time. When the phone went black i plugged in the USB cabel from the computer.
The error message came up 2 - 3 times but i kept holding the buttons.
Eventually it went into download mode and i used ODIN to flash the firmware...
I hope this could solve the problem also for others facing similar issues.
Thanks to BWolf56 who posted in a forum here. His tips fom 2011 .... helped me.
Regards
Tom
Tom-72 said:
Good NEWS !!!!!
I managed to get the phone working again...
What i did was:
Holding the volume down, home and power button at the same time. When the phone went black i plugged in the USB cabel from the computer.
The error message came up 2 - 3 times but i kept holding the buttons.
Eventually it went into download mode and i used ODIN to flash the firmware...
I hope this could solve the problem also for others facing similar issues.
Thanks to BWolf56 who posted in a forum here. His tips fom 2011 .... helped me.
Regards
Tom
Click to expand...
Click to collapse
Great to hear... Good luck from here on out!
This is a good sign not to listen to tech support. They don't know, or mess with this stuff, as much as us!
Happy flashing and hope no more scares from here on out...
Sent from my SM-G930P using Tapatalk
I don't see EQC1 on sammobile, anyone else see the 127 MB update?
I'm on EQB1.
Yup, I see it, 127.53mb on both of mine SM-N910T3 and
SM-N910T
I have it as well. Have you flashed yet?
I have it too. I'm not sure I want to flash, especially if it patches the ability to root my phone.
My phone also suffers from the SD card / reboot issue (the phone constantly boot loops when both an SD card and SIM card are in the phone). I wonder if this update will fix that?
I tried flashing it and it failed, I'm running a stock highly modified rom. I'll try reflashing the original stock unmodified rom when I get a chance tomorrow and apply the update. It looks like it's just security updates
Says "Various system improvements" for the QC1 update.
https://support.t-mobile.com/docs/DOC-28899
I updated to this version the other day, now I'm looking to root. Anyone know if the old root method still works? I may try myself in the next few days myself and find out.
I upgraded to it yesterday. Took about 30 minutes from start of install to finish. It updates the security to March 2017, has the new Google Play Store. Other than that I do not notice any other differences
Can i root after upgrade?
Does anyone know if this fixes the mmc_read failed issue along with its constant lagging/freezing problem?
febzz88 said:
Does anyone know if this fixes the mmc_read failed issue along with its constant lagging/freezing problem?
Click to expand...
Click to collapse
I'm pretty sure the mmc_read failure issue is failing hardware and no firmware release can fix this. My understanding is some Note4's had dodgy flash memory and will eventually fail. I had this happen to my note4 last year and got it changed out under warranty at a tmobile store. My phone had the constant lagging/freezing for about a month before it would just no longer boot, it wouldn't do anything other than a quick vibrate on power up, no boot screen of any type.
If you are getting mmc_read I would suggest you get the phone replaced ASAP, and make backups of everything you have on it that you want to keep. At some point it probably just wont power back on again. Hopefully you are still under a warranty and can get it swapped out.
d0ug said:
I'm pretty sure the mmc_read failure issue is failing hardware and no firmware release can fix this. My understanding is some Note4's had dodgy flash memory and will eventually fail. I had this happen to my note4 last year and got it changed out under warranty at a tmobile store. My phone had the constant lagging/freezing for about a month before it would just no longer boot, it wouldn't do anything other than a quick vibrate on power up, no boot screen of any type.
If you are getting mmc_read I would suggest you get the phone replaced ASAP, and make backups of everything you have on it that you want to keep. At some point it probably just wont power back on again. Hopefully you are still under a warranty and can get it swapped out.
Click to expand...
Click to collapse
Hi,
That's certainly is one possible scenario (hardware failing). But based on my extensive research too, many have said that this could be faulty firmware. I went to a Samsung Experience Center and talked with a guy there and he said that it's a known issue affecting many Galaxy Note 4 Sprint users a few months ago. Samsung in the end replaced/repaired the affected units free of charge.
In the past 2 months or so, more and more Galaxy Note 4 users started experiencing this issue. And so it could be that the firmware triggered the issue, and eventually damaged the hardware.
Since we don't really have a 100% certain answer (of course, Samsung will never tell us), I'm just trying to see if anyone has updated the phone to the latest firmware and could tell us if it fixed the issue.
Soooo..... Is this rootable or not?
sino8r said:
Soooo..... Is this rootable or not?
Click to expand...
Click to collapse
Try this https://forum.xda-developers.com/no...rom-n910t3uvu3eqc1-stock-rooted-odex-t3592242
I can't seem to get TWRP to work on this. I've tried several times with Odin, it appears to be successful, phone reboots, but then when I try to reboot into recovery there's no TWRP, only stock. Anyone else have this issue or any suggestions?
Edit: Tried something I remembered reading in another thread. I pulled the battery immediately after Odin successfully finished and the booted directly into recovery. It worked. I'm flashing pvsgh's rooted EQC1 and will report back if TWRP sticks
Edit 2: Success. Seems like pulling the battery after Odin/TWRP before the phone reboots did the trick
ok, thanks for the suggestion.
Anybody have a link for the firmware?
thecrunked said:
Anybody have a link for the firmware?
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...firmware-galaxy-note-4-n910tuvs2eqb1-t3569911
Can I autoroot with EQC1?
I tried auto root and got
RECORVERY IS NOT SEANDROID ENFORCING,
AM I screwed? I assume there's some way to get back to EQC1 and boot the phone. There has to be. But could I do it and keep the data. I was trying to get deleted photos back.
Hello.
I have a Galaxy Note 4 SM-N910T2. In january of this year i upgraded it to 6.0.1 (N910TUVU2EQI2) from 4.4.4(N910T2UVU2AOG1) using the SM-N910T firmware for the upgrade, everything was working perfectly but the day before yesterday i wanted to perform a wipe cache because the phone was being a bit laggy. after the wipe cache was perform and i hit the reboot, the recovery got stucked on Verifying DMhash tree. so after 30 minutes i took the battery out and powered on my phone, the problem is: The phone started to freeze, reset it self even the process system crashed. I read that downloading the Wake Lock power management helps and it did but i didn't want to use this app forever so i downgraded back to 4.4.4 it's original firmware, it does run better but now my phone reboots itself and it freezes just a little bit. Also i've got the Process system is not responding do you want to close it?
Things i've done so far:
1- Reflashed 4.4.4, 3 times, i've done wipes before reflashing and after. Nothing
2-Flashed TWRP wiped everything, repaired the file system, Flashed the stock again (4.4.4) nothing.
I'm not going back to 6.0.1.
Do i have to buy a new phone or maybe a new rom with a kernel will help ?
Pigoath said:
Hello.
I have a Galaxy Note 4 SM-N910T2. In january of this year i upgraded it to 6.0.1 (N910TUVU2EQI2) from 4.4.4(N910T2UVU2AOG1) using the SM-N910T firmware for the upgrade, everything was working perfectly but the day before yesterday i wanted to perform a wipe cache because the phone was being a bit laggy. after the wipe cache was perform and i hit the reboot, the recovery got stucked on Verifying DMhash tree. so after 30 minutes i took the battery out and powered on my phone, the problem is: The phone started to freeze, reset it self even the process system crashed. I read that downloading the Wake Lock power management helps and it did but i didn't want to use this app forever so i downgraded back to 4.4.4 it's original firmware, it does run better but now my phone reboots itself and it freezes just a little bit. Also i've got the Process system is not responding do you want to close it?
Things i've done so far:
1- Reflashed 4.4.4, 3 times, i've done wipes before reflashing and after. Nothing
2-Flashed TWRP wiped everything, repaired the file system, Flashed the stock again (4.4.4) nothing.
I'm not going back to 6.0.1.
Do i have to buy a new phone or maybe a new rom with a kernel will help ?
Click to expand...
Click to collapse
All i can say is your phone mmc chip is about to die soon or later you will get mmc_read failure message and your phone wont be able to boot into the system and you won'tbe able to flash anything.
My best suggestion is sell it ASAP.
Trex888 said:
All i can say is your phone mmc chip is about to die soon or later you will get mmc_read failure message and your phone wont be able to boot into the system and you won'tbe able to flash anything.
My best suggestion is sell it ASAP.
Click to expand...
Click to collapse
I came across the mmc_read failure before I realized it was happening and have been researching ways to at least verify there was nothing important on the device before retiring it to Samsung heaven.
Instead of useful advice, everyone seems to be spouting "sell it ASAP" as though it doesn't make you trash as a person to attempt selling it as any sort of working device. The inclusion of "ASAP" and lack of "with a disclaimer" tends to suggest they aren't recommending you actually tell anyone about the issue.
Good advice would be to back up everything you can now and begin looking for a new device. You could attempt to sell it for parts, but make sure to inform people of the situation. If it is that close to failure, chances are it will still be well within the 30 day return policy on most sites and they always favor the buyer. Your device is already ruined, but there is no reason to destroy your reputation with it.