Develop Bugs

4.1.2 Update Issues (Jelly Bean)

So I believe I updated to the latest firmware update the other day for 4.1.2. The issue im having is when I go to the about device option and click software update it shows "continue update" greyed out so im not able to click. When I click "check for updates" I always get the same message " software update interrupted". I have tried to run this update on wifi and 4g both unsuccessful. I have attempted to factory reset my phone ...no go. Can some please suggest anything that will resolve this issue i'm having.
Model # SGH-I317
Version 4.1.2
Baseband Version I317UCAMC3
Build JZO54K.I317UCAMC3

Try manually setting the time on your phone ahead by 24 to 48 hours. This may trigger the phone to complete the update. Are you running complete stock firmware? That includes android OS, kernel, modem, and recovery.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

Zen Arcade said:
Try manually setting the time on your phone ahead by 24 to 48 hours. This may trigger the phone to complete the update. Are you running complete stock firmware? That includes android OS, kernel, modem, and recovery.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried it already and was unsuccessful it just goes through the same motions like its going to update, and I receive the same message. Im running stock firmware.

ljsmith87 said:
I tried it already and was unsuccessful it just goes through the same motions like its going to update, and I receive the same message. Im running stock firmware.
Click to expand...
Click to collapse
From Settings>>About Device do baseband and build still show as MC3? Is kernel dated something prior to August 2013 (I think MC3 was April 2013)? (can you post a screenie?)
Have you made any customizations to your phone - i.e. build.prop tweaks, debloating, freezing of apps, removal of system apps, anything else that might have modified the /system partition? Any of this would cause the OTA process to abort and stall like you have seen.

Zen Arcade said:
From Settings>>About Device do baseband and build still show as MC3? Is kernel dated something prior to August 2013 (I think MC3 was April 2013)? (can you post a screenie?)
Have you made any customizations to your phone - i.e. build.prop tweaks, debloating, freezing of apps, removal of system apps, anything else that might have modified the /system partition? Any of this would cause the OTA process to abort and stall like you have seen.
Click to expand...
Click to collapse
Here is a screen shot.
I haven't made in any customizations. I did have the s4 voice.apk installed at some point in time, but I uninstalled it. its possible I could have deleted a system app unintentionally, but I don't recall doing so.

Are you using a stock 3e recovery ??
If not. ...the device will not update. ..as a stock recovery is required. ..g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

ljsmith87 said:
Here is a screen shot.
I haven't made in any customizations. I did have the s4 voice.apk installed at some point in time, but I uninstalled it. its possible I could have deleted a system app unintentionally, but I don't recall doing so.
Click to expand...
Click to collapse
If you are running the stock recovery, try downloading the CWM package I posted here - http://forum.xda-developers.com/showthread.php?t=2449972
Download to your PC and copy to your internal sdcard (the one that shows up as "phone"). Power off phone then boot recovery via home+vol up+power
Then use the side load option to run the CWM zip. If all goes well and your system partition is pure this will update your system, kernel, and modem to MH3. Upon phone boot, your recovery will update to MH3.
gregsarg said:
Are you using a stock 3e recovery ??
If not. ...the device will not update. ..as a stock recovery is required. ..g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Fair point - if you are running a custom recovery, follow the steps above, but run the CWM zip file as you would any other CWM zip from a custom recovery... but from your prior responses, I'm guessing you are running stock recovery and the update process just got confused somewhere... perhaps because one of the stock apps was deleted.
Pay attention when the CWM zip is running.. if it fails you will get an error message showing the file it fails on. I may be able to help you further from there - assuming it's only a file or two that has an issue.

4.1.2 Update Issues Jelly Bean (RESOLVED)
ljsmith87 said:
So I believe I updated to the latest firmware update the other day for 4.1.2. The issue im having is when I go to the about device option and click software update it shows "continue update" greyed out so im not able to click. When I click "check for updates" I always get the same message " software update interrupted". I have tried to run this update on wifi and 4g both unsuccessful. I have attempted to factory reset my phone ...no go. Can some please suggest anything that will resolve this issue i'm having.
Model # SGH-I317
Version 4.1.2
Baseband Version I317UCAMC3
Build JZO54K.I317UCAMC3
Click to expand...
Click to collapse
So after months and months of trying to update my phone to I317UCAMH3 I finally got my phone to update to what is now 4.3. Like many of you I tried everything I know how to such as:
-Reverting my phone to 4.1.1 and updating to 4.12 on Kies. same issue
-Resetting the flash counter after performing a data wipe....same issue
-Master reset....same issue
-Going to the Samsung service center and receiving the dumbest answer ever they told me my "cookies" preventing my phone from updating. (biggest idiots ever LOL)
So I was finally able to resolve this issue and receive my updates by switch my wife's sim card from her S3 to my phone and it worked like a charm. So my recommendation is if your having this issue it's more than likely occurring because of a faulty sim card and if you are unable to switch with another phone then go to the ATT store and they will give you a free one. Please let me know if this works for you.

Similar Issues
I have an AT&T Note 2 and is unlocked as I moved to Canada. My new carrier is Telus and until recently, around the same time as the KitKat, my great reception went bad. I've confirmed that it is not a hardware issue and appears to be related to updating my phone. For whatever reason I can't update the software on my phone. Kies is of no use and I don't have access to an AT&T sim card to try the new solution. I've tried the hard reset.
I've never rooted the phone and recently reset the phone to resolve the issues. Does anyone have any suggestions?
The version on my phone is I317UCAMA4 and 4.1.2.

weldingguy said:
I have an AT&T Note 2 and is unlocked as I moved to Canada. My new carrier is Telus and until recently, around the same time as the KitKat, my great reception went bad. I've confirmed that it is not a hardware issue and appears to be related to updating my phone. For whatever reason I can't update the software on my phone. Kies is of no use and I don't have access to an AT&T sim card to try the new solution. I've tried the hard reset.
I've never rooted the phone and recently reset the phone to resolve the issues. Does anyone have any suggestions?
The version on my phone is I317UCAMA4 and 4.1.2.
Click to expand...
Click to collapse
Not sure what the same time as KitKat means...
But you can try this. Updates to 4.3 and modem.
http://forum.xda-developers.com/showthread.php?t=2589891
It does not change the bootloader.

Update from PI3 to official Nougat.

I've seen some posts about updates to official Nougat failing, so I decided to upload the update.zip to get to Nougat. I'd like to note that I didn't update using the update.zip method, so let me know if anyone runs into any issues. Hopefully this helps you guys out.
1) Make sure you are on official NON-ROOTED PI3. Also, make sure you enable any disabled packages.
2) Create a folder on your SD card named fota.
3) Download this zip and rename it to update.zip, then put it in the fota folder you created.
4) Turn off the phone and boot into recovery-volume up+home+power at the same time.
5) Wait a minute for the dead android to go away and recovery finally boots, then select update from SD card. Select the update.zip.
Here is the Odin files for PI3 for those that need it. G930VVRU4API3

Testing now
---------- Post added at 11:51 PM ---------- Previous post was at 11:17 PM ----------
Still not working. Didn't get the log though, but there was a mounting error and then I believe I saw something status 7. Not sure what else is wrong.

Are you on PI3?

CVertigo1 said:
Are you on PI3?
Click to expand...
Click to collapse
I am.

Download "Phone Info *Samsung*" from the PlayStore. Open it up and upload a screenshot of the firmware page.

CVertigo1 said:
Download "Phone Info *Samsung*" from the PlayStore. Open it up and upload a screenshot of the firmware page.
Click to expand...
Click to collapse
Thank you for your help.

Everything appears to be in order. Is your SD card encrypted? I recall that being an issue with the beta builds.

CVertigo1 said:
Everything appears to be in order. Is your SD card encrypted? I recall that being an issue with the beta builds.
Click to expand...
Click to collapse
It is not

The best advice I have is to Odin all four PI3 files, but not Home_CSC. It will give you the cleanest install and take everything else out of the equation. I'd backup everything with Smart Switch first, then restore it all after updating.

CVertigo1 said:
I've seen some posts about updates to official Nougat failing, so I decided to upload the update.zip to get to Nougat. I'd like to note that I didn't update using the update.zip method, so let me know if anyone runs into any issues. Hopefully this helps you guys out.
1) Make sure you are on official NON-ROOTED PI3. Also, make sure you enable any disabled packages.
2) Create a folder on your SD card named fota.
3) Download this zip and rename it to update.zip, then put it in the fota folder you created.
4) Turn off the phone and boot into recovery-volume up+home+power at the same time.
5) Wait a minute for the dead android to go away and recovery finally boots, then select update from SD card. Select the update.zip.
Click to expand...
Click to collapse
What if you are on PKC? You think it will still work?

Crsdr37 said:
What if you are on PKC? You think it will still work?
Click to expand...
Click to collapse
Im on pkc also

Probably not, but you are welcome to try. If it doesn't work, then flash back to PI3 and update from there.

Also if you use package disabler pro like most of us. Ensure you go back into there and enable all bloatware you can re-disable after the update goes through

Crsdr37 said:
Also if you use package disabler pro like most of us. Ensure you go back into there and enable all bloatware you can re-disable after the update goes through
Click to expand...
Click to collapse
I already put this in the steps, but I guarantee a lot of people will forget to follow it lol.

I got mine updated. Here's what I did.
I reluctantly used the Verizon software repair tool to "repair" the OS. It took quite a while but did reload everything. After that I just took the OTA and it seemed to work fine. I would imagine that Odin would have worked too.

I'm on a VZ Galaxy S7, PI3 firmware on Boom Mobile (VZ MVNO). Tried OTA update, Samsung Smart Switch and Verizon Software Upgrade. All 3 are showing that my firmware is up-to-date on version 6.0.1 PI3. Have they just not rolled it out to everyone?
Is my only option to use the procedure on here?

mogulman01 said:
I'm on a VZ Galaxy S7, PI3 firmware on Boom Mobile (VZ MVNO). Tried OTA update, Samsung Smart Switch and Verizon Software Upgrade. All 3 are showing that my firmware is up-to-date on version 6.0.1 PI3. Have they just not rolled it out to everyone?
Is my only option to use the procedure on here?
Click to expand...
Click to collapse
Updated using the process from OP, worked fine.

I was on PI3 firmware and I kept checking without getting the new software from yesterday. Just now I connect my phone to the PC and open up Smart Switch, it tells me the new update is available.

I was having this same problem. I couldn't get my phone to take the OTA even after unrooting and I had to end up using Odin and flashing that BL file as well as the other three that you normally flash. give that a go if you're still having problems!

Upgraded directly from PKC (beta) using SamFirm to download and flash new verizon firmware via odin. Worked great. Didn't have to downgrade back to pe1.

Having trouble with the service.

My problem started some months ago, when a friend tried to root my phone, he told me that he rooted it but every app that checks for root told me that it wasn't rooted and i couldn't use apps that needed root also, the downside to all this is that i couldn't use apps that do not allow root, like the banking app, or Pokemon Go, but i used the phone like that for some months until last week when i decided to try and fix it. I thought that if i flash a stock firmware everything should be fine and the phone should be as new. On the phone, it says that the model is SM-N910F(behind the battery), in the settings it also said SM-N910F, so i tried flashing a rom for this model at first and it kept failing with me not knowing why. After trying different thing and googleing some time, i finally noticed that in "Fast Download", it says that the phone's model is SM-N910P, so i started searching about this, i didn;t understand why there were 2 different models on my phone, then i found out about searching my IMEI on imei.info, so i tried it and here it was SM-N910C, i had no idea what all this meant, but at this time i already got stuck into bootloop. Eventually, i found this thread: https://forum.xda-developers.com/note-4/help/help-sm-n910f-sm-n910p-bootloader-t3299285 and did what cam_bob22 said, it worked, i finally flashed the firmware on my phone and it worked, i could use the bank app, pokemon go, everything was fine except the fact that i couldn't select or change my mobile operator, when going to mobile networks, the mobile operators options was greyed out and couldn't be pressed(i want to mention that i did have service and that data worked but the internet would work only in roaming and i couldn't get 4G). So i tried updating the software from 5.1.1 to 6.0.1 like it was said in the instructions and hopping that this update would fix the issue, but unfortunately for me after the update i somehow lost service completely, the signal sign was in the shape of a triangle with no bars, and the mobile operators setting was exactly as before.
So far i tried going back to 5.1.1 but besides the Hands Free activation that i can't make to go away, i still can't use the mobile operators setting and my data only works with roaming activated and doesn't get 4g. One thing that i forgot to mention is that the IMEI with the 5.1.1 firmware was of a samasung Galaxy S5 not a note 4, i checked it on imei.info.
I was wondering if there is any way for me to go back to the OS i had before my friend tried to root my phone, when it said in the settings that it was SM-N910F and everything worked as it should have.
Thank you for reading and i really hope someone can help me.

@robert11arad
There is no way to go back unless he made a backup. Which is why you should always do this before you flash anything.
I'm not sure if this will help but you could try flashing a international custom Rom after you have correct firmware. But if your phone is a Sprint version, you'll have to use a special data fix and kernel.
What firmware did you end up using to flash? Was it Sprint? If so, and you use gsm service, try flashing my Gsm stock Rom for Sprint phones. It's in post 2.
https://forum.xda-developers.com/no...t/05-15-17-debloated-deodexed-rooted-t3607029
You'll first need to be on current marshmallow firmware. So flash firmware with Odin first, then install Twrp with Odin. Then install Rom with Twrp.

aaron74 said:
@robert11arad
There is no way to go back unless he made a backup. Which is why you should always do this before you flash anything.
I'm not sure if this will help but you could try flashing a international custom Rom after you have correct firmware. But if your phone is a Sprint version, you'll have to use a special data fix and kernel.
What firmware did you end up using to flash? Was it Sprint? If so, and you use gsm service, try flashing my Gsm stock Rom for Sprint phones. It's in post 2.
https://forum.xda-developers.com/no...t/05-15-17-debloated-deodexed-rooted-t3607029
You'll first need to be on current marshmallow firmware. So flash firmware with Odin first, then install Twrp with Odin. Then install Rom with Twrp.
Click to expand...
Click to collapse
Thank you for the reply, i wanted to say that with the Sprint firmware i used, after doing all the updates it unlocked the mobile operators option, but it couldn't find any.

robert11arad said:
Thank you for the reply, i wanted to say that with the Sprint firmware i used, after doing all the updates it unlocked the mobile operators option, but it couldn't find any.
Click to expand...
Click to collapse
Oh ok. So do you have service?

aaron74 said:
Oh ok. So do you have service?
Click to expand...
Click to collapse
No, the network operators is unlocked but there's still no service, when i try scanning for an operator it just stops with no message, and nothing happens.
I forgot to mention this, but before all this happened, I made a back-up of the phone with smart switch, is it possible to get back to how it was using that? And another thing is that when using the backup, it only restores music and photos, no contacts, no apps.(From what i've noticed so far)

robert11arad said:
No, the network operators is unlocked but there's still no service, when i try scanning for an operator it just stops with no message, and nothing happens.
I forgot to mention this, but before all this happened, I made a back-up of the phone with smart switch, is it possible to get back to how it was using that? And another thing is that when using the backup, it only restores music and photos, no contacts, no apps.(From what i've noticed so far)
Click to expand...
Click to collapse
You would have needed a system backup with twrp.
What country you in? What network you on? What firmware you on?

aaron74 said:
You would have needed a system backup with twrp.
What country you in? What network you on? What firmware you on?
Click to expand...
Click to collapse
I live in the UK, i'm on giffgaff and the firmware is N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5

robert11arad said:
I live in the UK, i'm on giffgaff and the firmware is N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5
Click to expand...
Click to collapse
Ok. About the best advice i can give is, because your on pure Sprint Rom, something is messing up with csc or something.
All i can suggest, is maybe try updating to QC1 with Odin and then try flashing my gsm Rom. Which is essentially just a tmobile rom.
And if that don't give you the function you you need. Then maybe try an international Rom.
It's hard to say what the last person did to the phone.

robert11arad said:
I live in the UK, i'm on giffgaff and the firmware is N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5
Click to expand...
Click to collapse
Also. You stated your phone first showed as a 910f. So maybe flashing a international F rom, will provide the correct csc settings for your phone to work. Only problem your gonna have, is because it's Sprint hardware, you'll have to pair the Rom with a kernel that'll work and some lib files for data.
I can help you by putting together some files to flash. But the main question would be, Do you want a stock note 4 Rom?
Also before any of this happened, do you know what firmware you were on? Marshmallow? Lollipop?

aaron74 said:
Also. You stated your phone first showed as a 910f. So maybe flashing a international F rom, will provide the correct csc settings for your phone to work. Only problem your gonna have, is because it's Sprint hardware, you'll have to pair the Rom with a kernel that'll work and some lib files for data.
I can help you by putting together some files to flash. But the main question would be, Do you want a stock note 4 Rom?
Also before any of this happened, do you know what firmware you were on? Marshmallow? Lollipop?
Click to expand...
Click to collapse
I would really appreciate if you helped me put the files together cause i have no idea how any of this works, i'm new. But i wanted to ask, is there any chance for thia to brick my phone?
When it had sm-n910f on it i couldn't update it after 5.1.1, when i pressed update it wouldn't do anything.
And yes, if possible i would like it to be a stock firmware, but if it is not possible i don't mind using something else as long as it works properly.
Thank you for all your help, i don't know what i would do otherwise.

robert11arad said:
I would really appreciate if you helped me put the files together cause i have no idea how any of this works, i'm new. But i wanted to ask, is there any chance for thia to brick my phone?
When it had sm-n910f on it i couldn't update it after 5.1.1, when i pressed update it wouldn't do anything.
And yes, if possible i would like it to be a stock firmware, but if it is not possible i don't mind using something else as long as it works properly.
Thank you for all your help, i don't know what i would do otherwise.
Click to expand...
Click to collapse
Well, first, let me state,about bricking device. I have to state that it's not impossible to brick. But after hundreds of flashes never had problem. These devices are hard to brick. What hard bricks a device is messing with boot loader and partitions that shouldn't be messed with, like trying to unlock lte bands. But just flashing roms is fine unless you flash a Rom not for your phone and it over writes wrong partition.
All snap Dragon note 4s have the same layout so all you need is correct kernel, csc, and some ril lib files to get data working.
Now, mine main worry is that the phone is still unlocked,because I don't know what possible changes were made to it.
But with all that being said,I'll move on. With another post.
---------- Post added at 05:52 PM ---------- Previous post was at 05:13 PM ----------
@robert11arad
Before we go too deep into this and upgrade and stuff. I'd like to just test a custom Rom on your phone and see what works.
So what firmware are you on right now?
5.01, 5.1.1, or 6.0.1?
I'm gonna take a guess and move on. You last stated you were on OG5 which it's 5.1.1. So if that's true, let's try the following.
First I'm gonna assume you already used Odin to flash that firmware. So now we need to flash Twrp. So download this on pc https://eu.dl.twrp.me/trlte/twrp-3.1.1-0-trlte.img.tar
1 . Put phone in download mode. Open Odin and plug in phone.
2. In Odin options make sure everything is unticked except Reset Flash Counter.
3. Now click on AP and select the Twrp file.
4. Flash it. Let it flash until it states it's completed. Once done. Unplug phone. Pull out battery. Put back in and boot to recovery by holding power+home+vol.up
5. Now you should have Twrp. Just reboot phone so we can continue to next post.

PM sent

@robert11arad
Ok, here you go. If your where we left off, you should be on stock QC1 and have Twrp installed.
Just download this file, boot into recovery, and install. This file will delete dalvick/cache, so phone will take a few minutes to boot up.
I actually recommend before flashing, you do a factory reset in recovery then install.
Anyhow here you go. Let me know if it fixes what your looking for. If not, my only others option is to install a custom n910f Rom. I'll gladly walk you through if need be. But try this first.

aaron74 said:
@robert11arad
Ok, here you go. If your where we left off, you should be on stock QC1 and have Twrp installed.
Just download this file, boot into recovery, and install. This file will delete dalvick/cache, so phone will take a few minutes to boot up.
I actually recommend before flashing, you do a factory reset in recovery then install.
Anyhow here you go. Let me know if it fixes what your looking for. If not, my only others option is to install a custom n910f Rom. I'll gladly walk you through if need be. But try this first.
Click to expand...
Click to collapse
Alright so i just tried it and when starting my phone, i can't even set it up because i keep getting a message that com.android.phone has stopped. After about half an hour of trying to start it, i finally managed to get to setting and to app manager, there i looked for com.android.phone and it was nowhere to be found. Apart from this i noticed a N with some signal bars where my phone signal should've been and i didn;t get the hands free activation anymore, but that's all...

robert11arad said:
Alright so i just tried it and when starting my phone, i can't even set it up because i keep getting a message that com.android.phone has stopped. After about half an hour of trying to start it, i finally managed to get to setting and to app manager, there i looked for com.android.phone and it was nowhere to be found. Apart from this i noticed a N with some signal bars where my phone signal should've been and i didn;t get the hands free activation anymore, but that's all...
Click to expand...
Click to collapse
Ok. I must have forgot something in csc. Sorry. I'll get back with you.

Problem: Bootloop and "software install failed"

Hello,
hopefully you can help me with my seemingly bricked Honor Pro 8 because of root and stock rom update procedures. I bought the phone with amazon and the package seemes to give me the information to have an EU-version of the phone.
The fastboot get-oem-information code or so also puts out the status of an European bootloader.
Regarding my working steps first of all the phone took the new update. Then I was successful in unlocking the bootloader, installing TWRP and rooting it by supersu.
But after that I was curious about the "Magisk" rooting abilities. Therefore I tried a superuser-unroot via script finding inside this forum following by flashing a extracted boot.img of an update.app file of a DUK-L09C432B130 update. After ending in a bootloop by trying the 1.30 beta version of magisk I was able to boot the normal android desktop after I uninstalled the beta version and having flashed the normal 1.20 version.
But then I tried to install 2 certain modules inside of magisk. In consequence the problem was to see the rebooted android not to load any icons. In the other side it put up the message of not having enough mobile disk memory after some minutes which couldn't be true in fact. So I tried a factory reset inside TWRP and also a full wipe. Disappointingly I haven't been successful in rebooting android once more.
Therefore I unseccessfully tried to flash the Full-OTA-MF stock rom of DUK-L09C432B130 in two versions and the L09-C432b120a via the EMUI-install mode by pressing vol+ and - and power buttons. To do that I prepared a SD card as a exfat format. But I just received the message of "software install failed" when reaching 5 %.
So I got to the frustrating point not to know what stock rom I can flash in another try or doing anything else. I would be very glad if U could help me in this desperating situation. :fingers-crossed:
Thanks and best regards.

Can you boot to erecovery?

adriansticoid said:
Can you boot to erecovery?
Click to expand...
Click to collapse
I can but it just puts out the message "Getting package info failed"

Filo83 said:
I can but it just puts out the message "Getting package info failed"
Click to expand...
Click to collapse
Please try another version of firmware.

adriansticoid said:
Please try another version of firmware.
Click to expand...
Click to collapse
That is my problem not to know which version to use because three dowloaded EU-versions weren't successful to install. It resulted in an error at 5 % of the 3-buttons-install mechanism.

Filo83 said:
Hello,
hopefully you can help me with my seemingly bricked Honor Pro 8 because of root and stock rom update procedures. I bought the phone with amazon and the package seemes to give me the information to have an EU-version of the phone.
The fastboot get-oem-information code or so also puts out the status of an European bootloader.
Regarding my working steps first of all the phone took the new update. Then I was successful in unlocking the bootloader, installing TWRP and rooting it by supersu.
But after that I was curious about the "Magisk" rooting abilities. Therefore I tried a superuser-unroot via script finding inside this forum following by flashing a extracted boot.img of an update.app file of a DUK-L09C432B130 update. After ending in a bootloop by trying the 1.30 beta version of magisk I was able to boot the normal android desktop after I uninstalled the beta version and having flashed the normal 1.20 version.
But then I tried to install 2 certain modules inside of magisk. In consequence the problem was to see the rebooted android not to load any icons. In the other side it put up the message of not having enough mobile disk memory after some minutes which couldn't be true in fact. So I tried a factory reset inside TWRP and also a full wipe. Disappointingly I haven't been successful in rebooting android once more.
Therefore I unseccessfully tried to flash the Full-OTA-MF stock rom of DUK-L09C432B130 in two versions and the L09-C432b120a via the EMUI-install mode by pressing vol+ and - and power buttons. To do that I prepared a SD card as a exfat format. But I just received the message of "software install failed" when reaching 5 %.
So I got to the frustrating point not to know what stock rom I can flash in another try or doing anything else. I would be very glad if U could help me in this desperating situation. :fingers-crossed:
Thanks and best regards.
Click to expand...
Click to collapse
you download the nocheck recoveries from my rebranding guide, download the corresponding firmware by morph (important!), flash both recovery images just like stated in the guide, boot into recovery mode like you would do to boot into twrp, do a factory reset, reboot and insert the microsd with the dload folder from extracted downloaded firmware and boot into force dload mode (vol+ and vol- and power) - the installation should start now and reset everything back to full stock.
Regards

Thank you very much OldDroid. You're my hero. It worked fine.
But to install the new 130-update the phone starts inside TWRP and ends with an "error 9" and the words "block image verify", "asserts failed". Could it be possible to perform the update by starting the forced update process by pressing the three hardware buttons on booting? And is it possible not to wipe the data and losing root by using a update?
Viele Grüße aus Berlin nach Berlin

Filo83 said:
Thank you very much OldDroid. You're my hero. It worked fine.
But to install the new 130-update the phone starts inside TWRP and ends with an "error 9" and the words "block image verify", "asserts failed". Could it be possible to perform the update by starting the forced update process by pressing the three hardware buttons on booting? And is it possible not to wipe the data and losing root by using a update?
Viele Grüße aus Berlin nach Berlin
Click to expand...
Click to collapse
OTA packages cannot be installed via twrp at the moment
you should use stock recovery for that!
Best regards
Grüße zurrück aus Berlin nach Berlin

Could you explain me a bit more please? Is it the standard system update ins the systems menu, here it wants to load the 2,9 GB file. Updating this way with the "no check recovery" resulted in an checking error at about 12 %.
Or could it be via recovery shortly after starting the phone? But there are no choices to choice. It just automaticely begins installing something stopping at 5 %.
Hope you can help one more please.

Filo83 said:
Could you explain me a bit more please? Is it the standard system update ins the systems menu, here it wants to load the 2,9 GB file. Updating this way with the "no check recovery" resulted in an checking error at about 12 %.
Or could it be via recovery shortly after starting the phone? But there are no choices to choice. It just automaticely begins installing something stopping at 5 %.
Hope you can help one more please.
Click to expand...
Click to collapse
soooo, if you flashed one of @-=MoRpH=- 's firmwares, your device is back to stock and the recoveries have been overwritten again! I don't recommend flashing OTA updates or other things through the NoCheck version as it is only intended for worst-case cenarios.

But could you tell me the single steps to update from Morph's DUK-L09C432B120 version to the newest version DUK-L09C432B130?
I only got errors to update the firmware DUK-L09C432B130 from the stock rom thread in this forum and the russian website mentioned there.

Filo83 said:
But could you tell me the single steps to update from Morph's DUK-L09C432B120 version to the newest version DUK-L09C432B130?
I only got errors to update the firmware DUK-L09C432B130 from the stock rom thread in this forum and the russian website mentioned there.
Click to expand...
Click to collapse
extract the firmware and flash manualy using fastboot

thilak devraj said:
extract the firmware and flash manualy using fastboot
Click to expand...
Click to collapse
That is just needed to be done as last resort. Better stick with dload.

adriansticoid said:
That is just needed to be done as last resort. Better stick with dload.
Click to expand...
Click to collapse
he said he got some errors doing dload, so this method works too

thilak devraj said:
he said he got some errors doing dload, so this method works too
Click to expand...
Click to collapse
He must find the right firmware first.

adriansticoid said:
He must find the right firmware first.
Click to expand...
Click to collapse
finding a firmware for huawei devices is a pain in the ass, you know

thilak devraj said:
finding a firmware for huawei devices is a pain in the ass, you know
Click to expand...
Click to collapse
That's why we have Firmware Finder.

adriansticoid said:
That's why we have Firmware Finder.
Click to expand...
Click to collapse
even in firmware finder, it will be difficult sometimes for sone devices

thilak devraj said:
even in firmware finder, it will be difficult sometimes for sone devices
Click to expand...
Click to collapse
Maybe. But they are constantly improving.

adriansticoid said:
Maybe. But they are constantly improving.
Click to expand...
Click to collapse
i appreciate the firmware finder, but sometimes, its just inappropriate

N910P - Please Help - Tried to root and failed No Bootloader found?

I'm really hoping someone can bail me out here before I...
I have made a mess of my new (to me) Note 4. I bought it as an Unlocked GSM. It arrived booting with a Sprint screen. I have Safelink BYOP service. When I switched from my Note2 to Note4, yesterday, an ATnT sim card was used to activate it with Tracfone. Everything seemed to work EXCEPT for MMS - I could not send nor receive pictures. I read -what I thought was- clear instructions here on the forum, I started downloading and attempting to root my phone, hoping that would solve the problem, since tech support had no answers.
I followed the instructions in this post - https://forum.xda-developers.com/note-4-sprint/help/rooting-sprint-note-4-pj1-t3495306 . Now the phone will only boot to download mode, or I can use the up volume button to get to the program to install, restore, etc. I have tried several times - with a couple of different .tar files. This last attempt - I tried to restore it - that also failed. My old eyes can not really see the tiny text but I did see in Odin3 that 1) No MDS found 2) Systemless mode Boot img support required 3) Boot Image Patcher Failed. When I attempt to install the SuperSU, from the thread, it gives me similar errors 1) NO MDS file found 2) (under Boot Image patcher it says FAILURE / Abort after extracting Ramdisk.
If anyone could help me out, I would be most grateful.

JadenEllis said:
I'm really hoping someone can bail me out here before I...
Click to expand...
Click to collapse
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!

Once you get phone back on stock. I'll show how to root!

Thank You
Thank you so much for the reply. I have downloaded the files you put in my post. I will attempt to do these things now, but I have a question. I stayed up fighting with the phone all night. I probably did some things I shouldn't have? I realized that I was getting stupid and quit, but I did (maybe) put some other stuff on the phone that night. Should I use the Clean or wipe function in TWRP before I do anything else???
Yes, I can boot to downloader or to TWRP. The phone (on its own) is now stuck trying to load with the Note 4 splash screen - but I can boot to either with the vol +/- buttons.

SamFirm did not work. It said Unable to fetch... please check data or enter manually.
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse

First - THANK YOU all for the assistance.
Yesterday, none of the suggestions were working, but I kept at it. I was finally able to install the most current Stock tar that I could find. This phone had updated to the most current version available for the phone - it had Marshmallow 6.01. NOW, the red and yellow tamper errors appear to be gone from the Note4 splash screen - BUT, it boots to Sprint Activation so it won't fully load to OS. I read a post about removing the Sprint Hands Free Activation, but it gives two ways of doing so. 1 requires having a rooted phone (I am assuming it is not rooted now?) and the other uses ADN Connect, and I am not sure what that is.
I'm not really sure what to do from here? Any assistance appreciated. Can I start from step 1 of the original post to install SuperSU now?
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse

Well, the sun is about to come up - again - but I think I got it! This has been a learning experience to say the least. I wasn't really planning a crash course in Android, but thank you to all who responded. And to :Samep too!

I think I get it
So, after a little rest I have a Note 4 with the most current stock tar. When I left it, at sun up, I had a slightly older stock version and rooted through TWRP 3.0.2.0 and rooted with the latest version of SuperSU. I spent a couple of few hours continuing to read and figure out how I would get it updates. If I could ask just a couple more questions??
If I put the TWRP 3.0.2.0 will the tamper warning come back to the flash screen?
Can I put TWRP on without rooting with SuperSU?
If not TWRP - is there a way to do a full backup without it? I REALLY want to get a good backup of what it has now - a fresh install of the latest 6.01 - and nothing else.
Thank you again.

JadenEllis said:
So, after a little rest I have a Note 4 with the most current stock tar. When I left it, at sun up, I had a slightly older stock version and rooted through TWRP 3.0.2.0 and rooted with the latest version of SuperSU. I spent a couple of few hours continuing to read and figure out how I would get it updates. If I could ask just a couple more questions??
If I put the TWRP 3.0.2.0 will the tamper warning come back to the flash screen?
Can I put TWRP on without rooting with SuperSU?
If not TWRP - is there a way to do a full backup without it? I REALLY want to get a good backup of what it has now - a fresh install of the latest 6.01 - and nothing else.
Thank you again.
Click to expand...
Click to collapse
Sorry bud. I'm so busy. Haven't been online since i message you. Glad you got it.

Rookie messed up..
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse
Thanks in advance i appreciate your time
Hello. I have similar issue as described here on this thread. I purchased an unlocked note 4 to run on cricket/att was working fine. Except lte. I tried to root an add nougat an ive screwed up. Somehow ended up in hidden menu. And chabged something made me have no service so i reset didnt work i factory reset data reset switched from global to cdma to lte. An nothing phone says 3g when its in activate your phone menu but does not work. Also it now says im on sprint network in about phone. Please help. Thanks again in advance.

meBn360 said:
Thanks in advance i appreciate your time
Hello. I have similar issue as described here on this thread. I purchased an unlocked note 4 to run on cricket/att was working fine. Except lte. I tried to root an add nougat an ive screwed up. Somehow ended up in hidden menu. And chabged something made me have no service so i reset didnt work i factory reset data reset switched from global to cdma to lte. An nothing phone says 3g when its in activate your phone menu but does not work. Also it now says im on sprint network in about phone. Please help. Thanks again in advance.
Click to expand...
Click to collapse
Sorry I don't get on here much lately. Just seen your post.
Without knowing exactly what you did. I'd say you lost your unlock. If you had an unlocked sprint phone. And tried nougat. I believe i remember that upgrading to nougat was messing up people's EFS partition. And that's where the unlock happens. Did you make a backup?
I always tell everyone, the most important thing you can do is have a full working backup of every partition.
Hope that sheds some light