Database Users

[Q] GT-i9505 cant return to stock

Well first off i'm going to have to make some apologies, i am a noob and i have made some very noobish mistakes i hope you will be kind forgive my stupidity and possibly even fix my mistakes.
I will try and provide as much information as i can hopefully that will help.
I have a S4 GT-I9505 which has been rooted with custom roms pretty much since the day i had it, very stupidly i didn't make a backup of my my phone while it was on stock (yup stupid i know). after going through many roms i settled on Omega 4.3 after some time i noticed apps like PVZ 2 wouldn't run on the device so i decided i would return to stock 4.3 and see if they worked then.
I looked in to a few guides for how to unroot the S4 and after following them i failed, each firmware i tried failed (possibly i tried the wrong ones) firmwares i have tried
BTU-I9505XXUDMH8-20130904171444
XEF-I9505XXUEMKF-20131130113349
GT-I9505-BTU-I9505XXUAMDM
I9505XXUEMK8_I9505O2UEMK1_O2U
One firmware i tried that did take then wouldn't turn on the wifi it remained grey. after some time i decided just to restore my backup of omega 4.3 since then my phone crashes when i try to make calls the screen turns black vibrates and remains black until it crashes to desktop or i turn the phone off. deciding i must have messed up quite badly i have spent the last 3 days reading XDA topics and posts trying to find a fix but nothing seems to work. i found this topic which seems to resolve the issue http://forum.xda-developers.com/showthread.php?t=2443020 after downloading a firmware ending in "H8" (BTU-I9505XXUDMH8-20130904171444) and trying to use it in odin (3.09 3.07 and 1.3) i get this error
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
i have checked kies is disabled via task manger, run odin in admin mode and tried multiple versions of odin i am at a loss
i have also noticed that my phone says this on boot.
"kernel is not seandroid enforcing"
"set warranty bit kernel"
i looked in to it to find out it doesn't seem to be a linked issue but hey the more information the better right.
I am very much at your mercy any help you can offer would be much appreciated

Ur latest firmware available is HERE
U need flash it with Odin 3.09 and I think all will go ok. Anyway if u have problems with ur WIFI is maybe u still having wrong MODEM. U will have to flash "new" modem then. How?
1. The correct modem for the new firmware is HERE
2. Steps for flash it
- Use Odin v3.09
- Untick Autoreboot
- Flash modem
- Reboot manually into Download Mode using (Vol Down plus Home button combi)
- Flash Modem once more
- Once done, unplug then reboot device manually.
- If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
3. If u still without wifi, try this wifi fix
- Open in Odin as PHONE!!
- WiFi FIX: HERE

thanks
thank you very much
I had to install the firmware twice and wipe a few times but it worked you are my personal hero.
thank you for your time and help have a great day

[Q] problems with repair centre

hey guys just after a bit of advice. i have had issues with my g900I overheating back in December so i sent it away for repair but they said they couldnt replicate the fault and it must have been a third party app causing the problem.
so it carried on fine only overheating a few times up until the end of last month when it decided to die on me all together it froze on me so i took out the battery and turned it on again only to find that its stuck in a boot loop did a factory reset same thing cleared the cache still no luck. sent it away for repair.
now its important to say at this point that i have not altered this phone in any way what so ever no root no custom firmware only system update back in November that was done through the phone. i even notice that when i accidentally put it into odin mode ( used wrong volume button when trying to wipe cache) that the nox counter was 0x0 and firmware state was official .
so i get a phone call from the store telling me that the service guys have come back saying that my warranty is void because unofficial firmware was installed on the phone.
what do i do? did i void the warranty by wiping the cache?
im sure i could probably fix the phone if it really came to it by rooting and installing lollipop or something but its covered under warranty because i know i haven't tampered with it. i was going to as i have rooted other phones in the past but for some reason something was holding me back this time.

Fight for your right, tell them I did not install any unofficial firmware
Also ask how did they found it's not official firmware
Sent from my SM-G900H using XDA Free mobile app

I would insist that you had not installed anything other than official firmware and that you want proof that unofficial firmware has been installed with full details. Wiping the cache should not void warranty. - they often recommend it to resolve problems before sending it off for repair. Threaten to take the issue to the ombudsman or whatever authority oversees this area. If you're in Australia I'd refer it to the ABC TV program The Checkout if they continue to be obstinate. I'd be standing my ground on this.

ok so both the store and samsung are refusing to do anything about it they both told us to take it to court because they would win anyway. will not be buying from harvey norman again or buying a samsung product again.
so im trying to see if i can fix it myself i have downloaded the file i need to upgrade to lollipop and have flashed with odin but its still stuck in a boot loop what else can i try

jezcullen09 said:
ok so both the store and samsung are refusing to do anything about it they both told us to take it to court because they would win anyway. will not be buying from harvey norman again or buying a samsung product again.
so im trying to see if i can fix it myself i have downloaded the file i need to upgrade to lollipop and have flashed with odin but its still stuck in a boot loop what else can i try
Click to expand...
Click to collapse
Since warranty is void anyway download TWRP recovery latest one and flash it in odin. Then entery recovery by press power +home+ volume up when the phone is off (it will take 4-5 seconds to enter recovery and you will get seandroid is not enforcing something error) just wait recovery will boot up there go to wipe > advanced wipe > wipe cache, dalvik > internal storage, data & system. then come back and hit "format data" type yes. then hit where it says swipe to factory reset. After this take out the battery and enter odin mode when the phone is off by holding power + menu and volume down button . Flash a stockfirmware downloaded from Sammobile. Formating and the other steps that i have mentioned before flashing stock firmware will most likely solve your problem
NOTE : USE ODIN 3.10 (its here on xda google it , dont download from any other source)
Report back if it worked.

dork997 said:
Since warranty is void anyway download TWRP recovery latest one and flash it in odin. Then entery recovery by press power +home+ volume up when the phone is off (it will take 4-5 seconds to enter recovery and you will get seandroid is not enforcing something error) just wait recovery will boot up there go to wipe > advanced wipe > wipe cache, dalvik > internal storage, data & system. then come back and hit "format data" type yes. then hit where it says swipe to factory reset. After this take out the battery and enter odin mode when the phone is off by holding power + menu and volume down button . Flash a stockfirmware downloaded from Sammobile. Formating and the other steps that i have mentioned before flashing stock firmware will most likely solve your problem
NOTE : USE ODIN 3.10 (its here on xda google it , dont download from any other source)
Report back if it worked.
Click to expand...
Click to collapse
hi thanks for your sugestions but its still happening after i install twrp i do what you say then flash latest stock rom for my device whixh is this (G900IDVU1BOE1_G900ITNZ1BOD2_G900IDVU1BOD2_HOME.tar.md5) once its finished the phone reboots i then get the image of the android on its back with its belly open the bar fills to half way then the device reboots gets past the spark screen and stays on the samsung logo.
im just trying to download kitkat now but from a different site as for some reason sammobile doesnt have the GALAXY S5 SM-(G900I) on there page now. i have also tried installing XtreStoLite_ROM_v2.2_LP_XXU1BOD3 but same thing it tells me its installed but then wont boot??????????????????
not sure what else to try not sure if its worth mentioning but have flashed that xtrestolite several times now and knox counter is still at 0x1

Okay then you have to try a pit file along with the recovery a pit file basically repartions the phone and is flashed with stockfirmware. I dont knw how exact procedure but its also done with Odin maybe senior members can help

dork997 said:
Okay then you have to try a pit file along with the recovery a pit file basically repartions the phone and is flashed with stockfirmware. I dont knw how exact procedure but its also done with Odin maybe senior members can help
Click to expand...
Click to collapse
i found a pit file but i keep getting a fail
<ID:0/004> Removed!!
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1005)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
when i reboot i get this
KERNeL IS NOT SEANDROID ENFORCING
set warrenty bit : kernel
this is after flashing cm-12 its starts to boot then krashes again.
if i use stock rom then i get past the spark logo which sometimes has a real distorted picture then i get the samsung logo (sometimes with sound) and if im real lucky i get to a point where its trying to install apps gets to about 70 of 170 or something like that only had that a couple of times so not sure on exact wording

Did you ask them how they found out your phone had been "tampered" with?

Akalsemann said:
Did you ask them how they found out your phone had been "tampered" with?
Click to expand...
Click to collapse
They just looked at the knox counter im pretty convinced its a hardware problem from the overheating i really have no clue how i could have voided the warranty i have never rooted and the only updates i have done are with kies apart from what im doing now of course

Ok so a bit of an update.
I have tried flashing several different custom roms with no luck
I have flashed both stock 5.0 and 4.4.2 and I have tried stock with twrp with all the advance wipe as well as different kernels.
Once I started playing around with the kernels I was able to get stock 4.4.2 (g900idvu1ank1) with chronickernel-kk...klte v1.5 it would boot up fine then crash once I tried to install from play store.
From there I was able to flash the stock rom 4.4.2 (ank1) but not 5.0 when ever I try to update I get stuck in the boot loop. However I can successfully run 4.4.2 install backups from keis but as soon as I put my SIM card or my wife's SIM card in the phone crashes and gets stuck in a boot loop until the sim is removed.
What else can I try is this just a glorified MP3 player now

Ok so a bit of an update.
I have tried flashing several different custom roms with no luck
I have flashed both stock 5.0 and 4.4.2 and I have tried stock with twrp with all the advance wipe as well as different kernels.
Once I started playing around with the kernels I was able to get stock 4.4.2 (g900idvu1ank1) with chronickernel-kk...klte v1.5 it would boot up fine then crash once I tried to install from play store.
From there I was able to flash the stock rom 4.4.2 (ank1) but not 5.0 when ever I try to update I get stuck in the boot loop. However I can successfully run 4.4.2 install backups from keis but as soon as I put my SIM card or my wife's SIM card in the phone crashes and gets stuck in a boot loop until the sim is removed.
What else can I try is this just a glorified MP3 player now

Anyone have any idea

so after several months and several phone calls to samsungs head office here in nz they have finally agreed to fix my phone at no charge they will be replacing the main board so im hoping that will remove the tripped knox counter. :victory:

Did I brick my phone following instructions on apps to freeze?

I'm freaking a little here, so pardon me. Battery life on my phone (even with new batter(ies) got terrible (less than 16 hrs) so I looked through a post at http://forum.xda-developers.com/showthread.php?t=2483927 for apps I could freeze , froze them and rebooted. Now my phone gets to the big white V over the word VERIZON on a red field and just freezes there. When the phone started before, when the Samsung "Galaxy Note 3" logo came up, it said something afterwords - I don't remember the wording, but it started right after I rooted. It had something to do with the rooting. Anyway, apparently something I froze had to do with the proper operation of the rooting. So now I think I need to start the phone in some kind of "safe mode" and undo what I'd frozen. I just have no idea at all how to do that. I managed to get it into safe mode once, but it only stayed there a few minutes and then went right back to the endless V. I haven't been able to get it back into safe mode. It doesn't respond to the keys after I power it up - although I CAN get it into recovery mode. When it was in safe mode though, it showed no menus or icons and being that it didn't respond to the keys, I couldn't access any apps. I'd even be more than happy to just flash back to defaults (unrooted) but I have no idea how to do that either. I've got no phone right now - and I have another 2 years to pay on a piece of crap I can't even use.
This is a rooted Note 3. I don't remember what method I used to root it - I didn't know they were so different, but I know towelroot was installed. Any help would be VERY much appreciated.

Steve01351 said:
I'm freaking a little here, so pardon me. Battery life on my phone (even with new batter(ies) got terrible (less than 16 hrs) so I looked through a post at http://forum.xda-developers.com/showthread.php?t=2483927 for apps I could freeze , froze them and rebooted. Now my phone gets to the big white V over the word VERIZON on a red field and just freezes there. When the phone started before, when the Samsung "Galaxy Note 3" logo came up, it said something afterwords - I don't remember the wording, but it started right after I rooted. It had something to do with the rooting. Anyway, apparently something I froze had to do with the proper operation of the rooting. So now I think I need to start the phone in some kind of "safe mode" and undo what I'd frozen. I just have no idea at all how to do that. I managed to get it into safe mode once, but it only stayed there a few minutes and then went right back to the endless V. I haven't been able to get it back into safe mode. It doesn't respond to the keys after I power it up - although I CAN get it into recovery mode. When it was in safe mode though, it showed no menus or icons and being that it didn't respond to the keys, I couldn't access any apps. I'd even be more than happy to just flash back to defaults (unrooted) but I have no idea how to do that either. I've got no phone right now - and I have another 2 years to pay on a piece of crap I can't even use.
This is a rooted Note 3. I don't remember what method I used to root it - I didn't know they were so different, but I know towelroot was installed. Any help would be VERY much appreciated.
Click to expand...
Click to collapse
Is it 900v?
Don't listen to the safe to remove threads. Happened to me too old note 1 days when I was on tw.
Go to sammobile dot com
Search for firmware for your model or carrier. Flash with odin. Search yt fir how to use odin or XDA it. You simply start with flash.
I think Verizon has the ? bootloader. You may find it hard to reroot. And you should for the sake of root flash the oldest firmware from sammobile. Just to be sure you can reroot if there is a method.

kenny1991 said:
Is it 900v?
Don't listen to the safe to remove threads. Happened to me too old note 1 days when I was on tw.
Go to sammobile dot com
Search for firmware for your model or carrier. Flash with odin. Search yt fir how to use odin or XDA it. You simply start with flash.
I think Verizon has the bootloader. You may find it hard to reroot. And you should for the sake of root flash the oldest firmware from sammobile. Just to be sure you can reroot if there is a method.
Click to expand...
Click to collapse
So I downloaded the oldest firmware Sammobile had for my Note (4.3). I downloaded Odin. The suggested version for 4.3 was Odin 3.9, so that's what I tried. I downloaded and installed the latest Samsung USB drivers. Then I started Odin and followed This guide: http://www.droidviews.com/install-stock-firmware-on-samsung-galaxy-devices-using-odin/ . I did it 3 times. Each time it failed. The info in the message box was:
aboot.mbn
FAIL! (Auth)
Complete (Write) Operation failed.
All threads completed. (Succeed 0 / failed 1)
Did I miss something?

Steve01351 said:
So I downloaded the oldest firmware Sammobile had for my Note (4.3). I downloaded Odin. The suggested version for 4.3 was Odin 3.9, so that's what I tried. I downloaded and installed the latest Samsung USB drivers. Then I started Odin and followed This guide: http://www.droidviews.com/install-stock-firmware-on-samsung-galaxy-devices-using-odin/ . I did it 3 times. Each time it failed. The info in the message box was:
aboot.mbn
FAIL! (Auth)
Complete (Write) Operation failed.
All threads completed. (Succeed 0 / failed 1)
Did I miss something?
Click to expand...
Click to collapse
Also, the phone now says (on the download/Odin mode screen) in red letters
SW REV CHECK FAIL : [aboot]Fused 3 Binary 2

Steve01351 said:
Also, the phone now says (on the download/Odin mode screen) in red letters
SW REV CHECK FAIL : [aboot]Fused 3 Binary 2
Click to expand...
Click to collapse
So, as a last resort I decided to give the ROM for 5.0 a shot with Odin. It actually worked. My phone now starts. Sort of. I mean bluetooth starts (at least according to my Galaxy tablet and Galaxy Gear watch), but I have no desktop on the phone or way of accessing any of my apps. I have no clue. I've got a menu bar across the top, but the settings menu doesn't respond. Looks like a trip to the Verizon store is in order.

Steve01351 said:
So, as a last resort I decided to give the ROM for 5.0 a shot with Odin. It actually worked. My phone now starts. Sort of. I mean bluetooth starts (at least according to my Galaxy tablet and Galaxy Gear watch), but I have no desktop on the phone or way of accessing any of my apps. I have no clue. I've got a menu bar across the top, but the settings menu doesn't respond. Looks like a trip to the Verizon store is in order.
Click to expand...
Click to collapse
Damn. As a very very last resort, I decided to try a factory reset. Doing one and choosing during it to import my old apps and settings resulted in the same no desktop. Doing a factory reset again but choosing to "set up as a new phone" gives me a desktop. And Android 5.0. Go figure. Now I gotta download and set up all my apps again - pair it with my tablet and Gear, but at least it's working. I don't have to buy another phone. Thank Odin.

Steve01351 said:
Damn. As a very very last resort, I decided to try a factory reset. Doing one and choosing during it to import my old apps and settings resulted in the same no desktop. Doing a factory reset again but choosing to "set up as a new phone" gives me a desktop. And Android 5.0. Go figure. Now I gotta download and set up all my apps again - pair it with my tablet and Gear, but at least it's working. I don't have to buy another phone. Thank Odin.
Click to expand...
Click to collapse
Lol.
Some times you have to backup data. But you almost have to reinstall apps from play store with such issues you had.

kenny1991 said:
Lol.
Some times you have to backup data. But you almost have to reinstall apps from play store with such issues you had.
Click to expand...
Click to collapse
I'm actually not that upset. I WAS getting worse and worse battery life. All I really lost was time and a few pictures I hadn't backed up on my computer, but I had backups of all my music, ringtones and my contacts were saved, so it's not bad. Except for that god-awful light blue background color in the menus.

Odin flash failure on SM-G950W soft-bricked S8

I originally posted this under the wrong thread so apologies for the duplication. It was pointed out to me that my original post was in the wrong spot.
I'm super new to all of this but have spent the last two days trying to educate myself on how to use Odin after my S8 soft-bricked on me two days ago. I'm running into an issue with Odin's flashing not working for some reason and I can't seem to find any trouble shooting guides that solve the problem and I'm wondering if I maybe have set it up incorrectly somehow.
I'm running an SM-G950W through a Telus carrier in Canada and pulled the firmware through Samfirm since Sammobile is down currently. I've got the phone in download mode and the appropriate files in the appropriate slots in Odin. I'm looking to flash it without losing the data for the time being, if I can, just so I can back it up since apparently my cloud service backup failed and I have some relatively important images on there (ie. my mother's funeral) that I'd like to not lose if I can help it. Once I've pulled those, I plan to do a factory reset and failing that, plan to return the phone to my provider.
Odin sets up the files ok, recognizes the phone, and allows me to start but then it just doesn't actually seem to work. It doesn't throw any error codes or anything it just gives me the following:
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
I've updated the Samsung USB drivers, I've tried multiple ports. I've cycled the phone. I installed and then shut down Kies (I had read suggestions on installing it to establish a connection with the device and the computer and then disabling it so it didn't conflict with Odin). I'm running Odin 3.12.3. I'm figuring I'll need to go back to an earlier firmware edition, once the sammobile servers are back up, maybe? Or is there some other suggestion I might try to figure this out.
I'll add I've not rooted or anything before. I hadn't done any sort of customization to my phone to trigger this. It started with random rebooting. Then multiple apps and functions started throwing errors repeatedly without break (made it impossible to type or use anything because it was so constant). The main one was cloud storage stopping working. Once I tracked that down and cleared the cache, it shifted to rebooting nonstop until it just stuck on the Samsung screen. Now that's the only screen it'll do unless I put it in recovery or download mode. I got it into safe mode once but it still rebooted itself which is what makes me think it's more than just an app issue or anything third party and will require a factory reset once I've retrieved the data I want to back up.
I appreciate any suggestions or help that can be provided.

I've now also tried the download mode cycle boot while starting Odin flash trick. While it didn't make Odin succeed, it did generate a slightly different Odin output:
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> apdp.mbn
<ID:0/005> msadp.mbn
<ID:0/005> persist.img.ext4
<ID:0/005> userdata.img.ext4
<ID:0/005> Home Binary Download
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Still no luck successfully flashing though.

I had a problem with my s8 when I flashed 950u to my 950w Odin was showing fail so I did some YouTube video search and found a modified Odin that helped.
http://https://androidfilehost.com/?fid=24686680535466915

Vanyl said:
I originally posted this under the wrong thread so apologies for the duplication. It was pointed out to me that my original post was in the wrong spot.
I'm super new to all of this but have spent the last two days trying to educate myself on how to use Odin after my S8 soft-bricked on me two days ago. I'm running into an issue with Odin's flashing not working for some reason and I can't seem to find any trouble shooting guides that solve the problem and I'm wondering if I maybe have set it up incorrectly somehow.
I'm running an SM-G950W through a Telus carrier in Canada and pulled the firmware through Samfirm since Sammobile is down currently. I've got the phone in download mode and the appropriate files in the appropriate slots in Odin. I'm looking to flash it without losing the data for the time being, if I can, just so I can back it up since apparently my cloud service backup failed and I have some relatively important images on there (ie. my mother's funeral) that I'd like to not lose if I can help it. Once I've pulled those, I plan to do a factory reset and failing that, plan to return the phone to my provider.
Odin sets up the files ok, recognizes the phone, and allows me to start but then it just doesn't actually seem to work. It doesn't throw any error codes or anything it just gives me the following:
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
I've updated the Samsung USB drivers, I've tried multiple ports. I've cycled the phone. I installed and then shut down Kies (I had read suggestions on installing it to establish a connection with the device and the computer and then disabling it so it didn't conflict with Odin). I'm running Odin 3.12.3. I'm figuring I'll need to go back to an earlier firmware edition, once the sammobile servers are back up, maybe? Or is there some other suggestion I might try to figure this out.
I'll add I've not rooted or anything before. I hadn't done any sort of customization to my phone to trigger this. It started with random rebooting. Then multiple apps and functions started throwing errors repeatedly without break (made it impossible to type or use anything because it was so constant). The main one was cloud storage stopping working. Once I tracked that down and cleared the cache, it shifted to rebooting nonstop until it just stuck on the Samsung screen. Now that's the only screen it'll do unless I put it in recovery or download mode. I got it into safe mode once but it still rebooted itself which is what makes me think it's more than just an app issue or anything third party and will require a factory reset once I've retrieved the data I want to back up.
I appreciate any suggestions or help that can be provided.
Click to expand...
Click to collapse
I think that the problem is your computer, maybe you should try with a different one.
Perhaps you could also try using third party applications that might help easily retrieve all the data from your device.
https://drfone.wondershare.com/drfone-app-for-android.html
http://7datarecovery.com/android-data-recovery/
Good luck.

Thanks @hemp_invader. I did try a new computer and the flash passed but my phone saw no change. I saw some of those programs and wasn't sure if they were... trustworthy?

Joshua Mr PC Repair said:
I had a problem with my s8 when I flashed 950u to my 950w Odin was showing fail so I did some YouTube video search and found a modified Odin that helped.
http://https://androidfilehost.com/?fid=24686680535466915
Click to expand...
Click to collapse
I got Odin to flash using a different computer but the phone is still unchanged in terms of being able to load in. I wasn't able to get that link to work though.

Vanyl said:
Thanks @hemp_invader. I did try a new computer and the flash passed but my phone saw no change. I saw some of those programs and wasn't sure if they were... trustworthy?
Click to expand...
Click to collapse
You're welcome. If there was no change on your phone, perhaps you already have the firmware you are trying to install. Are you on AQL5? If not, review the steps performed, maybe you missed something.
I have always been using their products to recover lost data, and never had one single problem.
I forgot about MobilEdit, which is more popular, you might want to check the forensics version for better results.
http://www.mobiledit.com/

hemp_invader said:
You're welcome. If there was no change on your phone, perhaps you already have the firmware you are trying to install. Are you on AQL5? If not, review the steps performed, maybe you missed something.
I have always been using their products to recover lost data, and never had one single problem.
I forgot about MobilEdit, which is more popular, you might want to check the forensics version for better results.
http://www.mobiledit.com/
Click to expand...
Click to collapse
I'm on AQK7 which matches what's listed in recovery mode and the most recent firmware I could find.
I tried Android 7 data recovery but it couldn't find my phone. Dr. Fone sees my phone but the data extraction option only supports up to S6/S6 Edge, not S8. I downloaded the mobiledit forensic version but it requires being able to approve a code on the screen to gain access which I can't do since I can only enter Recovery and Download mode.

hemp_invader said:
You're welcome. If there was no change on your phone, perhaps you already have the firmware you are trying to install. Are you on AQL5? If not, review the steps performed, maybe you missed something.
I have always been using their products to recover lost data, and never had one single problem.
I forgot about MobilEdit, which is more popular, you might want to check the forensics version for better results.
http://www.mobiledit.com/
Click to expand...
Click to collapse
I've got mobiledit forensic express seeing the phone but it only sees it for a split second before the program loses the connection even though the phone screen remains on the load screen. I was able to hit next one time to see that it'll let me download the full data content of the phone but the connection isn't staying which is limiting me. I'm not sure how to trouble shoot that.
[Edit]: I waited it out and the connection finally stuck, I ran the full content extraction, and while it found 1 SIM card SMS and several of my contacts, it says it was unable to access my images, audio, video folders. Even using the file manager to browse the folders showed no results. It is suggesting rooting the phone but I'm not confident that won't void my contract/coverage so I'm guessing that my phone wiped my data already in its constant bootloop and this might be a lost cause. I'll run the extraction a couple more times but it's not looking hopeful.

Vanyl said:
I've got mobiledit forensic express seeing the phone but it only sees it for a split second before the program loses the connection even though the phone screen remains on the load screen. I was able to hit next one time to see that it'll let me download the full data content of the phone but the connection isn't staying which is limiting me. I'm not sure how to trouble shoot that.
[Edit]: I waited it out and the connection finally stuck, I ran the full content extraction, and while it found 1 SIM card SMS and several of my contacts, it says it was unable to access my images, audio, video folders. Even using the file manager to browse the folders showed no results. It is suggesting rooting the phone but I'm not confident that won't void my contract/coverage so I'm guessing that my phone wiped my data already in its constant bootloop and this might be a lost cause. I'll run the extraction a couple more times but it's not looking hopeful.
Click to expand...
Click to collapse
Rooting your phone will not void your warranty. You can flash a stock os at any time and nothing is changed. Knox is never incremented to 0x1 as 0x1 is impossible on the g950w. The whole "root trips Knox" thing is a myth and imo needs to be eradicated from our collective memory.

You could try flashing a factory test firmware first, worked for me but I have 950F.
G950U,W COMBINATION FA70 G950USQU1AQDB FACTORY MULTI CERT
G950U,W COMBINATION FA70 G950USQU1AQG3 FACTORY MULTI CERT
G950U,W COMBINATION FA70 G950USQU1AQI3 FACTORY MULTI CERT
G950U,W COMBINATION FA70 G950USQU1AQK1 FACTORY MULTI CERT
G950U,W COMBINATION FA70 G950USQU2AQK2 FACTORY MULTI CERT
Then after that flash every newer firmware in order of release (just in case).
Also make sure you have latest Odin (3.12.7) and don't tick any extra boxes like re-partition etc. Use correct files (BL,AP,CP,HOME_CSC)

Did you turn ON OEM Unlock in developer before you began? Also if you can get back into the phone get your data - flashing stock WILL lose your data. Your other choice is to use ADB to copy out the files. You could also put a MicroSD card in and then use Odin to flash the latest TWRP - hold down [Vol Up] + [Bixby] +[Power] as you press [Start] in Odin to make sure you get to TWRP.
Once you're in TWRP use File Manage (in Advanced) to find the pics and copy them over to the MicroSD.
Then you can continue with the Root/Build process

Please help me, I am SAD😭😭😭: It will not boot after installing Titanium Backup (root) to uninstall Samsung DM service

This question may contain some irrelevant information, but I wanted to give as much detail as possible. I can tell you basically everything I did to the phone from the factory state before I ran into the problem with not being able to boot. If it is too long to read, you could skim it and skip to "(now we are getting to the horrific part)" below.
I rooted my Samsung Galaxy Note 4 SM-N910P (Android 6.0.1) using the method described here:
[SM-N910*] CF-Auto-Root
Check your device model ! Settings -> About device -> Model number. See the third post for exact supported model numbers. If your device is a totally different model, it will not work (may even brick) ! CF-Root is the root for "rooting...
forum.xda-developers.com
It is not my main phone. It is a 2nd, used phone which I purchased recently, and it was apparently in factory state or factory-reset state when I removed it from the envelope. It had Android 6.0.1 on it. The phone does not have any SIM card in it, nor does it need one, as I was planning on using it as a tablet connected to WiFi. I rooted it. This was my first time rooting a phone, but I didn't have any problems. Everything was OK, root successful
I installed the following "SCR" app because I wanted to screen record with internal audio and simultaneously hear the internal audio through earphones (which was the reason I rooted the phone):
[APP][4.0+][ROOT] SCR Screen Recorder
Official SCR Screen Recorder thread Check out SCR Screen Recorder, the Android most comprehensive screencast recording app. SCR Screen Recorder supports all Android versions since 4.0 and utilizes the best encoding method available on each...
forum.xda-developers.com
But it did not work. Even though it was advertised as working with Android 6, the app would immediately crash after pressing the record button. It gave the SR135 error mentioned here:
[APP][4.0+][ROOT] SCR Screen Recorder
Official SCR Screen Recorder thread Check out SCR Screen Recorder, the Android most comprehensive screencast recording app. SCR Screen Recorder supports all Android versions since 4.0 and utilizes the best encoding method available on each...
forum.xda-developers.com
The SCR app did give a warning when I enabled internal audio from the settings menu, but I think that this is (probably?) not the source of my boot problems, because I had since rebooted the phone several times with no trouble. I don't think the internal audio plugin even installed; it seemed to just silently fail to initiate the installation. It wasn't until I installed Titanium Backup that I had trouble booting. I had stopped attempting to use SCR, and was planning on uninstalling it.
The next thing I tried was installing some APKs for the Samsung Game Launcher, because supposedly that app allows recording of internal audio. I got the APKs following these links:
Game launcher for Note 4 without Root
Samsung release s7 game launcher for s6 and note 5. Its also working with our note 4. Just downland Game launcher and game tools and install. Game launcher -...
forum.xda-developers.com
These earlier versions of the Samsung game APKs were not suitable because they did not allow me to add arbitrary apps to the launch menu (so that I could screen record). Something about a requirement to request to register the app as a game, and it would not go through. So I tried some later versions (the latest that I could find on APK mirror that were compatible with Android 6), and those did allow me to add arbitrary apps, but I had problems with these later versions crashing before I could actually launch anything.
So, following my inspiration in my quest to screen record with internal audio while also listening to internal audio, namely, this detailed reddit post,
https://www.reddit.com/r/AndroidQuestions/comments/81vhvm
I then proceeded to install RecMe screen recorder and its internal audio plugin (the latter requiring root, which I had):
RecMe Screen Recorder - Apps on Google Play
Screen Recording - No time limit, HD, with Audio, no Root required
play.google.com
Internal Audio Plugin (ROOT) - Apps on Google Play
Internal Audio Plugin app for mobZapp (Screen Stream Mirroring, RecMe, ...)
play.google.com
This was an improvement over Mobizen for Samsung, which I had tried on my other, unrooted phone, and which could record internal audio on Samsung devices but which could not also simultaneous allow the internal audio to play on earphones/speakers (you hear only silence when recording, but the audio is in the recorded MP4). RecMe with the plugin could actually play internal audio while also recording the internal audio, although the sound quality in the earbuds was poor, and it needed more testing.
I rebooted successfully after installing RecMe and the plugin, so I think it (probably?) did not cause my boot problems.
I was planning on doing some more testing with RecMe after installing AFWall+ to block RecMe from accessing the Internet for security purposes, but I never got to installing AFWall+, because this happened (now we are getting to the horrific part):
So this Note 4 phone, SM-N910P (Sprint), every time you boot it, it tries to go through this Hands Free automatic activation process to connect to the Sprint network that takes a long time (I think 5 retries, taking like 60+ seconds each). This isn't going to work because there's no SIM card (as I said, I'm using it as a tablet, I don't need cell service). So I go to the App Manager -> Show System Apps and then stop the Samsung DM Service. This stops the annoying automatic activation attempts, but I have to do it every time I boot.
So, to avoid doing this after every single boot, I followed the instructions here to first back up, and then uninstall, Samsung DM Service:
How to Delete & Manage Unused Apps on Android: 2 Easy Ways
This wikiHow teaches how to disable or remove apps from your Android device that cannot normally be uninstalled, which may require root access for your device. Open your Android's Settings. If your device is not rooted you'll only be able...
www.wikihow.com
Per the instructions, this required installing Titanium Backup (root needed):
Titanium Backup (root needed) - Apps on Google Play
EXTREMELY powerful tool. Backup ALL apps, Market links, remove bloatware & MORE!
play.google.com
When I installed the app, I granted root or superuser or whatever it's called to it, and it prompted me to also install "Titanium Backup Add-on," which I did.
Titanium Backup Technical FAQ | Titanium Track
www.titaniumtrack.com
Then I used Titanium Backup to (first) back up Samsung DM Service, and (second) uninstall Samsung DM Service. After that, I got some messages that said "Unfortunately the process com.samsung.syncservice has stopped." OK, I'll deal with that later, I thought. I proceeded to reboot the device, because I wanted to test and see if the annoying Hands Free automatic activation thing would be gone.
Now, when I try to boot the phone, it briefly says "installing system updates" (which doesn't make any sense because it should already be on the latest possible security patch [I checked] for Android 6.0.1 for this past-end-of-support-lifetime Note 4 phone — I forgot to mention earlier that I updated the Android security patch level before I did the root, and the Play store updated after I did the root [and I successfully rebooted — no boot problems until Titanium Backup]).
And then, no matter how many times I try, the phone always just boots to Android Recovery. It says samsung/trltespr/trltespr 6.0.1/MMB29M/N910PVPS4DQF1 at the top, and at the bottom it says "dm-verity verification failed". It does NOT explicitly say anything about failed "drk" which I saw mentioned in some Google search results.
I tried repeating the root steps which had earlier allowed me to successfully root the phone:
[SM-N910*] CF-Auto-Root
Check your device model ! Settings -> About device -> Model number. See the third post for exact supported model numbers. If your device is a totally different model, it will not work (may even brick) ! CF-Root is the root for "rooting...
forum.xda-developers.com
But no change. Same thing. Android Recovery. Tried reboot to system, to boot-loader, tried Wipe Cache, nothing works. Always boots into Android Recovery.
1) Can I fix this without doing factory reset?
2) Will factory reset fix this?
3) What did I do to provoke this? (so that I may avoid doing it again) It was caused by installing Titanium Backup? I thought this was a safe app? It has almost 400K reviews; I thought it was one of the most popular apps that require root? Or was it caused by uninstalling Samsung DM Service? Really? I did not think it was a super essential service; I had force-stopped it many times without any problems. (If so, in that case, how do I get rid of the annoying Hands Free Activation thing?)
4) Is it possible to access the filesystem (though USB?) to retrieve a screen shot? (The phone is not encrypted.) It's not a super big deal, but I made another Google account for this 2nd phone, and instead of memorizing the password, I took a screenshot of the random characters I had typed. I planned to learn it later. I know that was foolish, I guess, but I didn't think anything bad would happen. I had already successfully rooted the phone, and I didn't think I was doing anything super risky at this point. Literally all I did was install a few apps including Titanium Backup. And I uninstalled Samsung DM Service. Now I can't boot the phone. What is this horror?
[I am not an Android expert. I have used adb a few times, following other people's instructions. I don't have all the command memorized, I am not an expert, but I've used adb on my Oculus Quest (to change resolution) and also on my main phone that is unrooted (not on this rooted, boot-troubled one) in the course of installing Island on that other phone (it was never installed on this boot-troubled one). I don't even know if it's possible to use adb on a phone that cannot boot. But if you tell me adb commands I can paste them into the command window, assuming I am able to connect to an unbootable phone...]
If anyone can help me escape this horror, I will be forever grateful....

I think the phone is bricked. I tried factory reset and it is still always booting to recovery. This is my first time rooting. I didn't realize it was so easy to brick a phone. I never bricked a PC. I didn't think I did anything very risky. I didn't even try installing anything fancy like xposed or magisk — just an app from the Play Store. I thought people were just being dramatic when they talked about "bricked" phones....
Can someone tell me how to recover it with Odin3 v3.14.1.exe or Odin3 v3.14.1_3B_PatcheD.exe? I can still get to download mode on the phone.
What files do I download to recover a Note 4 SM-N910P?
Odin says "Changing the partition without unlocking will cause problems." Does the fact that I successfully rooted it using the "CF-Auto-Root" mean that it is unlocked?
I have the file twrp-3.6.0_9-0-trlte.img.
The SHA-256 hash is 2a5394313e1afe1c92576a5ceeba5cea462706bfc01e2da3d836fc381a119967.
Can I use this file to un-brick the phone?
Odin says:
Tips - How to download HOME binary
OLD model : Download one binary ".tar.md5"
NEW model : Download BL + AP + CP + HOME_CSC
There is also a button for USERDATA.
I don't know what any of this means — Which buttons do I press? When I used the "CF-Auto-Root" method I used a .tar.md5 file with an older version of Odin. For that, I used the AP button.
Or should I flash a stock Samsung ROM instead of twrp-3.6.0_9-0-trlte.img? Should I use the old version of Odin (Odin3-v3.10.6.exe) instead of Odin3 v3.14.1.exe or Odin3 v3.14.1_3B_PatcheD.exe?

Hey, you guys, can someone please help me? I am trying to fix this on my own without help, but I am not succeeding.
I followed the instructions here:
[Stock TAR][Full Restore] Odin flashable N910PVPS4DQB3_N910PSPT4DQB3_N910PVPS4DQB3
QB3 Marshmallow TAR: N910PVPS4DQB3_N910PSPT4DQB3_N910PVPS4DQB3_HOME.tar.md5.zip md5: e77d93930ec3c8593c18f0c3638ca726 Odin: Odin_3.12.4_4 -Download file, unzip file to extract full tar.md5 file -Load PC Odin (right-click on file, select "Run...
forum.xda-developers.com
to flash N910PVPS4DQB3_N910PSPT4DQB3_N910PVPS4DQB3_HOME.tar.md5
I thought this would work, because before it bricked I looked in my phone settings and recorded the following information in Notepad on my computer:
N910P.05
MMB29M.N910PVPS4DQB3
But Odin fails with error "FAIL! (Auth)". I will paste the log below.
Please help me...
Code:
<ID:0/014> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/014> Odin engine v(ID:3.1401)..
<ID:0/014> File analysis..
<ID:0/014> Total Binary size: 3634 M
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> NAND Write Start!!
<ID:0/014> SingleDownload.
<ID:0/014> aboot.mbn
<ID:0/014> sbl1.mbn
<ID:0/014> FAIL! (Auth)
<ID:0/014>
<ID:0/014> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

I noticed that it said on the download-mode screen:
SW REV CHECK FAIL : [aboot]Fused 5 > Binary 4
So I am going to try to find and flash N910PVPS4DQF1, which I think is a later version than N910PVPS4DQB3. I think either I or the aforementioned Auto-Root had updated from N910PVPS4DQB3 to N910PVPS4DQF1.
Does this sound like it will work to you? I hope so.
I hope I can find it — an authentic, malware-free original version.
And I PRAY that it works when I flash it.

It still fails with the same error message "SW REV CHECK FAIL : [aboot]Fused 5 > Binary 4", even though the firmware exactly matches what is shown on the recovery boot screen, N910PVPS4DQF1. Why does this happen? How the f. did my aboot get to such a high version number?
Is this site legit?
Download SM-N910P / GALAXY Note 4 SM-N910P XAS in Samfw - Samsung firmware download
SM-N910P / GALAXY Note 4 SM-N910P XAS samsung firmware download all model, lastest, fast update, completely free and fast speed in Samfw.com ✅
samfw.com
I guess I should try the most recent one from 2020, N910PVPU5DQI5? Or maybe the temporally penultimate one, N910PVPS4DQH1, which is from 2017-08-16? I don't remember having any updates from 2020 on this old Note 4 phone.

Hey,
I don't know if the website you posted is legit or not, but apparently, this one is:
Samsung firmware download - find All Official Android & Samsung Updates | updato.com
Are you looking for the official Samsung software to download? At updato.com, you'll find the latest Android device updates. Check on your own!
updato.com
Updato - largest online firmware archive, fast and totally free
[CENTER] [SIZE="4"]www.updato.com lets you download any firmware for your Samsung device, completely free with download speed restrictions. We offer an option for premium download speeds for a minimal cost. Visit the website -...
forum.xda-developers.com
To be honest, jumping from 2017 to a sudden 2020 update does look a bit fishy so wouldn't download anything from there.
Also, I don't have a Note 4 personally, so I don't exactly know how to root it, but when you open the page of the firmware you want on updato, it gives you instructions on how to flash it.. (tho it seems like you already know how to do that) - and the XAS (Sprint) carrier is already filtered.
After taking a look on the CF Autoroot website, it says that it's based on the build ID "MMB29M.N910PVPS4DQF1" for your SM-N910P.
So, yeah the ...F1 should be good, try this one:
Samsung firmware download - find All Official Android & Samsung Updates | updato.com
Are you looking for the official Samsung software to download? At updato.com, you'll find the latest Android device updates. Check on your own!
updato.com
Regarding TitaniumBackup - the app itself shouldn't be able to brick your phone and I'm pretty sure something got messed up after deleting / uninstalling the Samsung DM Services app.
Instead of deleting it, you should just try to freeze it with Titanium.
Hope that kinda helped and good luck.

crmbz said:
Regarding TitaniumBackup - the app itself shouldn't be able to brick your phone and I'm pretty sure something got messed up after deleting / uninstalling the Samsung DM Services app.
Instead of deleting it, you should just try to freeze it with Titanium.
Click to expand...
Click to collapse
Thanks for the reply. Yeah, I think you're right when you say it was caused by uninstalling the Samsung DM service. I was worried that the problem was caused by dm-verity blocking the boot, but I read somewhere that dm-verity does not block boot until Android 7. Android 6 will warn about corruption, but will not block booting, if I understand correctly. So the bootup process apparently actually needs the Samsung DM service for whatever reason.
I ended up getting the phone working by flashing N910PVPU5DQI5_N910PSPT5DQI5_N910PVPU5DQI5_HOME.tar.md5 from 2017, which can be found here under "PREREQUISITE" as well as other places. I inspected the other, supposedly-2020 archive, and the only difference is the modem.bin is N910PVPU5DTI1 (supposedly from 2020) instead of N910PVPU5DQI5 (2017). I don't think I need the new modem, as I'm not using cell service, but if I want to, I think I can install it later with the stand-alone file "MODEM_N910PVPU5DTI1_REV00_CL_2079268.tar.md5" using the CP (modem) slot in Odin, if I understand correctly.
I think the CF Auto Root is not very good. I tried the Mobi .firmware site for an updated version, but I had the problem described here. So instead of CF Auto Root, I used the method described in the link below to root the phone, which involves TWRP and SuperSU:
[Simple] Guide - How to root Note 4 Marshmallow (Qualcomm) [Similar for other models]
I have observed that some peoples are still confused about rooting marshmallow, So I am writing this just overall process, this is very obvious process for rooting and I have tried it on Note 4 Marshmallow and found working, this may work on...
forum.xda-developers.com
I had earlier found that guide in the Google search results for rooting, but as a newcomer I was turned away by technical jargon like "flash TWRP through Odin" that does not elucidate on what TWRP/Odin are or how to use them. But many days later, I now know what those words mean, and it is in fact very easy to "flash TWRP through Odin" once you know how to do it. (I think aspects of this website would work better as a wiki, so that people could add those details into the guide to improve it. The forums also have problems with information rot, like for example a link to release notes for SuperSU pointing to defunct Google+ (lol).)
Rooting it this way was much better, because when I soft-bricked my phone again by trying (again) to uninstall Samsumg DM Service with Titanium Backup (to confirm that that was what had caused the soft brick the first time), I was able to easily restore the system partition I had earlier backed up to SD card with TWRP. Doing it with TWRP backup/restore avoids the need to re-flash the stock firmware through Odin, and it also leaves installed apps (Titanium Backup, etc.) and data intact. If I had TWRP the first time I think I could have recovered that PNG image of my password from the filesystem and avoided orphaning a brand new Google account (but Google kindly allowed me to create another one). The stock recovery is really useless. The so-called "factory reset" didn't do anything for me.
The only other thing I could do is maybe install Magisk, but I'm not sure I really need Magisk — I just want to be able to run apps that require root, and I think SuperSU will be good enough for that. And the guide for installing Magisk goes over my head lol...
"if your device utilizes the A/B partition scheme" = I don't know
"If your device doesn’t have a boot ramdisk" = I don't know
So I think I will maybe avoid Magisk unless I find an easier-to-follow guide that is specifically written for my exact phone model.
Other than that, I just need to shut off the annoying Hands Free Activation that starts every time I reboot the phone. I will try to freeze the Samsung DM Service as you suggested, although it seems strange that that would work, because it seem like it would stop it from being available during boot in the same way that uninstall does. But I will try it. Now that I have TWRP and Odin and the stock firmware, I know that I can unbrick the phone if something goes wrong; I think it is unlikely to be permabricked, so I can safely experiment with more possible methods to shut down the Hand Free Activation . I think Titanium Backup requires the premium version for freezing, but I might be able to do the same thing for free with Island or Greenify or some other app.
So yeah, I'll try to freezing it. In the meantime, if anyone has any other ideas about how to stop the "Hands Free Activation" / Samsung DM Service from running after every boot, feel free to reply...

crmbz said:
Instead of deleting it, you should just try to freeze it with Titanium.
Click to expand...
Click to collapse
Yeah, your suggestion to freeze instead of uninstall definitely seems to have worked — thanks again.
I didn't want to pay for Titanium for something that wasn't guaranteed to work, so I installed Island, thinking I might be able to use that to freeze. I had to set it up manually because of some complaints about a modified system or custom OS preventing creation of a work profile, but I had done that before on my other phone to avoid some encryption requirement. (Island offered to automatically set itself up with root privileges, but it just crashed after I granted it such privilege 🫤 (Face with Diagonal Mouth emoji).) But I couldn't use Island to freeze apps in mainland without God Mode, and the instructions for setting up God Mode, unfortunately, went over my head (e.g., "Destroy Island space" = how?).
So what I did instead is use this adb command:
Code:
adb shell "su -c 'pm disable com.samsung.syncservice'"
Now when I look at Samsung DM Service in Titanium Backup, it shows the option "Defrost," meaning that it is frozen. So this adb command apparently does the same thing that the paid version of Titanium Backup will do for a fee.
And now the phone can reboot, and the Hands Free Activation doesn't show up. It's weird how the boot process freaks out about an uninstall, but is cool with disablement. Lesson learned: If I have an annoying system app, I should freeze it instead of uninstalling it.