Good evening,
I used the Search, I browsed through hundreds of thread pages and even googled and went through Youtube comments, but I wasn't able to find an answer.. How can I flash a ROM for the N910P (Sprint) on my N910F?
Trying to flash those Roms results in a Status 7 as you might know. I ran over some advice to modify the updater-script and remove the assert check in the first line, so I did it and for a moment it seemed to work.
The installation aborted at a later point of time, this time giving me a Status 1 message.
I went on to google that as well, but nothing helped.
Tried Philztouch and various TWRPs (older, newer, ifferent Note 4 twrps...) and at this point I'm desperate. Please help me
s6edge+ sm-g928v for root operation wrong write s6edge and now logo loop and on recovery :
Failed to mount '/preload
i have this f.w but with odin cant write
ALL_VZW_G928VVRU1AOGI_G928VVZW1AOGI_CL5337315_QB5784720_REV00_user_low_ship.tar
please help to revive this thx
firmware
Does anyone have the stock Firmware for this phone because i cant find it anywhere on the net and i know this is one of the only ways to bring it back from being bricked.
I am having similar issue.
I have Galaxy S6 Edge+ SMG9287 dual sim, the phone works perfect but when I am performing a hardware reset It shows:
E:failed to mount /preload (invalid argument)
But then says: Data wipe complete, and finish OK.
Is that something to be worry about?
Again, the phone works perfect.
Regards.
You could always just get a new one and claim it on your insurance if you pay for it may as well use it and sell yours for parts.
Hi all,
First of all sorry my English not that good,
and please read it to the end
few days ago I tried to downgrade from Lollipop 5.1.1 to Kitkat 4.4.4 which i found later it is something can't be done,
but back then processor failed and i get some things on Odin , it stops on sboot.bin and fail and my phone in download mode says : sw rev check fail device 2 binary 1
so as an android user i looked all arount the web and Xda forums and found a way to flash Kitkat with a way to avoid
sw rev check fail device 2 binary 1
which was to delete sboot.bin and modem and compress them to .tar again , and guys that was the dumbest thing i did,
My note won't start and says : FIrmware upgrade encountered an issue. please select recovery mode in kies and try again
so as usual I looked again and someone somewhere said "why don't you try PIT file"
so i tried and that work for me and WoW my note work again , and from then i I stopped all the Experiments at the poor Note 4.
but yesterday some App on my note (which require Root and I can't tell you what it is) do some weird stuff and reboot.
the devise work but this message appeared (com.google.process.gapps - unfortunately google play store has stopped) constantly, constantly and constantly ,and that is painful , so I backed up my files and wiped every thing and restart the devise but still getting the same message , so I tried flashing lollipop again but still getting the same error on download mode
sw rev check fail device 2 binary 1
so i used PIT file again but nothing worked
so you know the deal , I looked around and again someone somewhere said use CWM to deal with sw rev check fail device 2 binary 1
So i did , and get into recovery and I use every wipe option i did found,
and restart my note , and THIS IS THE END MY NOTE STUCK IN GALAXY NOTE 4 LOGO NO MATTER WHAT I DID
right now i am downloading Ukranian lollipop firmware but I don't think this will make a difference
Any help guys any solution to fix my phone , please i can't afford to pay to fix it
thank you in advance
UPDATE : My friend told my to root it again maybe it will work , but i just got the old recovery but still STUCK IN GALAXY NOTE 4 LOGO
So my device now working i just download this frimware
HERE
Ukranian one , and work like magic , I hope this thread work for someone else ,
If flashing the latest stock Samsung firmware back onto your device doesn't fix your problem. I would recommend taking it into a Samsung Service Center to see if they can fix it for you. If it's software based they will usually fix it for you free of charge.
DarkGuyver said:
If flashing the latest stock Samsung firmware back onto your device doesn't fix your problem. I would recommend taking it into a Samsung Service Center to see if they can fix it for you. If it's software based they will usually fix it for you free of charge.
Click to expand...
Click to collapse
Thank you for replay
So as I said I am downloading a newer one , and Hoping
And I can't take it to samsung because we don't have Service Center in Syria
GUYS THANK YOU FOR ALMOST NOTHING
no JK
So my device now working i just download this frimware
HERE
Ukranian one , and work like magic , I hope this thread work for someone else .
Glad that you managed to get your device fixed.
hello, i just bought a used note 4 (SM-N910F) today.
And when i went into the download mode to install latest stock firmware using Odin, i found that the product name is wrongly listed as SM-N910T3.
Eventhough the phone is shown as N910F on the box and in the settings menu too.
Anyways, i still went ahead and tried to put the latest firmware of n910f into it using odin and i got the error message - emmc write fail aboot.
I then came out of it and tried to factory reset it from the settings menu which then took me to the recovery menu for some reason instead and showed me various options including wipe factory data reset.
And below that i was getting this error message in red that "dm-verity verification failed"
I still went ahead and performed the wipe, during which i got the error message "e failed to mount/preload (no such file or directory".
After that i rebooted the phone and thankfully after waiting for 15+mins it booted up and seemed to have reset the phone.
But now I'm pretty sure the earlier owner messed up n installed the wrong firmware for it besides rooting it (as shown by the knox trip count).
So my question is, how do i install the correct firmware for it?
thanks for any help.. will be greatly appreciated.
A.Ahmed79 said:
hello, i just bought a used note 4 (SM-N910F) today.
And when i went into the download mode to install latest stock firmware using Odin, i found that the product name is wrongly listed as SM-N910T3.
Eventhough the phone is shown as N910F on the box and in the settings menu too.
Anyways, i still went ahead and tried to put the latest firmware of n910f into it using odin and i got the error message - emmc write fail aboot.
I then came out of it and tried to factory reset it from the settings menu which then took me to the recovery menu for some reason instead and showed me various options including wipe factory data reset.
And below that i was getting this error message in red that "dm-verity verification failed"
I still went ahead and performed the wipe, during which i got the error message "e failed to mount/preload (no such file or directory".
After that i rebooted the phone and thankfully after waiting for 15+mins it booted up and seemed to have reset the phone.
But now I'm pretty sure the earlier owner messed up n installed the wrong firmware for it besides rooting it (as shown by the knox trip count).
So my question is, how do i install the correct firmware for it?
thanks for any help.. will be greatly appreciated.
Click to expand...
Click to collapse
Your original model is SM-N910T3 thats Tmobile note 4 usa model not the N910F European model.
Your original.model is shown correct in download mode that's your motherboard model.
Probably its refurbished device with Modified software and box and sticker behind the battery just for looks like N910F international model because N910F has more value in market.
I personally had same experience before as you i bought N910F online and i found it was N910P sprint usa model in download mode.
Dont try to flash any N910F firmware your device may end up hard brick and completly useless
you can flash N910T3 firmware it will flash without errors.
Trex888 said:
Your original model is SM-N910T3 thats Tmobile note 4 usa model not the N910F European model.
Your original.model is shown correct in download mode that's your motherboard model.
Probably its refurbished device with Modified software just for looks like N910F international model because N910F has more value in market.
Dont try to flash any N910F firmware your device may end up hard brick and completly useless
you can flash N910T3 firmware it will flash without errors.
Click to expand...
Click to collapse
ok thanks alot, i'll try to download a N910T3 firmware and retry and update here again.
Someone gave me a note 4, but it's a Sprint device and I'm an at&t subscriber; I'd prefer to not have the Sprint garbage on here, but I have a business need to not run a rooted device.
Is there anything preventing me from running the at&t firmware on this? I get that LTE won't work since this doesn't have the necessary band support, but the hardware appears to be otherwise identical.
Im guessing it may not be that easy given the fact that the latest bootloader on the sm-n910p is a fused 5. There may be a way to flash a modified att firmware if you replace it with the 5DQ15 bootloader. I say "may be" as I can not tell you for certain. Also even if you are successful, you will not get LTE as the hardware is different. If you do not have the latest N910PVPU5DQI5 firmware, Im pretty sure you could sell it and buy an ATT Note 4. A lower version of the sm-n910p is very hard to find and most likely fetch a little higher price.
Yeah, I wasn't expecting LTE, I was just hoping for something that didn't have all the Sprint crap that doesn't work.
I think I'll just wait until I'm working again and get a S10 or Note 10 and retire this to the phone drawer.
mikeytsi said:
Yeah, I wasn't expecting LTE, I was just hoping for something that didn't have all the Sprint crap that doesn't work.
I think I'll just wait until I'm working again and get a S10 or Note 10 and retire this to the phone drawer.
Click to expand...
Click to collapse
Hello, If you decided or if anyone else has the same question, perhaps this is what your looking for.
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Well, this is likely moot now as the device has pretty well crashed and I haven't been able to recover it yet.
I'm using a note 3 at the moment, which isn't great as it's just a bit too old. I'm also borrowing a OnePlus 1, but I don't think that's going to work for me as it doesn't have an SD slot. I may just pick up an S6 since those are relatively cheap until I can upgrade to a 10.
I just noticrd your reply and I will post a reply later today, I hope I can help you bring back a working Note 4 .
Yeah, something's wrong with it on a pretty basic level now. I did briefly get it functioning again two days ago (after doing a bunch of factory resets and firmware reloads), but it started crashing again during build-out and it's been unusable ever since.
I did tease out a kernel panic at one point, here's what it threw:
Kernel Panic
Krait info
panic caller : mdm_subsys_powerup+0xf0/0x12c
panic msg : CP BOOT UP FAIL - NEED cP DUMP
Thread : mdm_helper_prox:759
pm8841_rev : 0x0
I'm using "N910PVPU5DQI5" which I pulled down from this very site.
That was the first thing that I thought when you posted. Ondin fail and that is due to the latest firmware update on n910p Sprint Note 4. The last update was a fused 5, version 4 and to my knowledge ATT firmware is a fused 4. Also called aboot. (aboot) . Aboot is always upward compatible but is not downwards compatible. Meaning, if you upgrade to a higher aboot as in your case fused 5 then you will not be able to dowmngrade back to a fused 4 aboot. When you gashed the ATT official firmware that had an lower aboot is the reason you bricked you device. The good new is I think I may have a solution to unbrick your device. I need to confirm a few details before I reply.
No, I'm still using the Sprint firmware, haven't tried the at&t one yet.
ok
---------- Post added at 03:41 AM ---------- Previous post was at 03:35 AM ----------
Was it a flash that caused a soft brick? How did this happen?
I was getting random perf issues, then it started randomly crashing and restarting, eventually getting to the point where it would no longer boot. That's when I started trying to reload the firmware to hopefully get it stable again. No such luck.
On a more entertaining note, I've managed to soft-brick the OnePlus 1 a friend loaned me trying to update it from cyanogenmod to Lineage 16 since there's apparently a build for it. I got TWRP , the image, and the google stuff installed but it just won't boot and ultimately restarts back to TWRP. I'll poke around the dedicated forum for that though.
https://forum.xda-developers.com/note-4-sprint/general/firmware-qi5-released-10-11-2017-t3686982
---------- Post added at 03:58 AM ---------- Previous post was at 03:55 AM ----------
mikeytsi said:
I was getting random perf issues, then it started randomly crashing and restarting, eventually getting to the point where it would no longer boot. That's when I started trying to reload the firmware to hopefully get it stable again. No such luck.
On a more entertaining note, I've managed to soft-brick the OnePlus 1 a friend loaned me trying to update it from cyanogenmod to Lineage 16 since there's apparently a build for it. I got TWRP , the image, and the google stuff installed but it just won't boot and ultimately restarts back to TWRP. I'll poke around the dedicated forum for that though.
Click to expand...
Click to collapse
Dam!!! From the frying pan to the fire. I feel fot yoy bro. .... Sorry to hear that... Entertaining maybe, frustrating is a definite. Ouch!!! &^//^#
Did you make a back up in TWRP before flashing lineage 16?
---------- Post added at 04:51 AM ---------- Previous post was at 03:58 AM ----------
Just to confirm, I understand that you did in fact wipe user data and did a full factory reset. Is this correct?
Sprint Note 4
1 . Try booting into safe mode and see if that helps. if not
2. Boot into stock recovery and wipe dalvik chache and perform a factory reset and I recommend to do this 3 or 4 times a row before you reboot. Then reboot your device. I sould also mention. while in stock recovery in start page read the notification at the bottom.
3. If the above dose not fix your device then flash 5DQ15 official factory firmware with Odin. Remind you to open develop option and enable adb beforehand.
I had an old Note 4 with similar issues as your describing. It was an emmc hardware failer. The only fix was a new motherboard.
Of course not.
Should be easy to recover though, I just need to find a utility so I can flash it.
For you Note 4. Use pc or laptop , proper drivers anf Odin software.
link for Odin download only. None of the official Tar firmwares in this link are compatible . I just want to be very clear that flashing any Tar in the link provided will end in Odin fail and a soft bricked device. Odin is the only thing you need to download. Hope this is of some help.
https://forum.xda-developers.com/note-4-sprint/general/stock-tar-odin-flashable-t3250864.
Yeah, I wiped it three times in fact, I read something about that in another thread.
It won't even boot to the point where you could try to get in to safe mode.
I've done several factory wipes before and it didn't seem to help, I'll that again and try reloading firmware again though and see what happens.
..... Recovery mode appears to be hanging on "Installing System Update" we'll see if it finishes.
Hmmm, I'm not seeing an ADB option. I'm using Odin v3.12 if that matters.
Finally got in to recovery.
dm-verify verification failed...
e:failed to mount /cache (invalid argument) - see several of these
e:Can't mount /cache/recovery/log
e:Can't open /cache/recovery/log
e:failed to mount /cache (invalid argument)
:can't mount /cache/recovery/last_log
can't open /cache/recovery/last_log
... /cache/recovery/last_install
..../cache
.../system
...last_locale
So, several errors.
DM-verify is one of the worst and it is also likely to include a DRK error . I have over 5 year experience with Sansung rooting and flashing, porting and........ Im a flash-a aholic and soft brick my devices many times. In all that time I only had one that I could not recover from. Yep DM-Verity fail(device mapper) and DRk (device root key) and Note 4. There are you tub videos and a good amont of information on the net. 4 files flashed via Odin. I had a rooted device and DM-verty involves security prodection as I had root the issue may have been woth su' binaries. However. as youare not rooted maybe flash factoy firmware in Odin will work for you.
You may have wondered why I suggested looking at the bottom screen in stock recovery. I answer is DM-verity.
In recovery at te top of first page is a knox counter. If its un-tripped reads 0x0 similar . If it has been tripped then a number will be visible as an indication 1x0 or 2x0 or similar.
I had to root the device to unlock platform so I could use it with the at&t sim. That was months ago and had no impact on running the stock firmware.