Related
With the ongoing issues surrounding lost IMEI's and lost phone functionality due to a lost IMEI. It may be in all of our interests to backup the NV Data to our phones. I have provided in this thread information on how to do so. Hope it helps =)
http://forum.xda-developers.com/showthread.php?t=1801997
DX
Thanks for the guide. I got as far as starting the backup in QPST, but got an error.
SPC given could not unlock the phone. The phone will not respond for 10 seconds.
Guess I need to try on an insecure kernel, but can't find one for our phone. The two that used to be on samsung-updates.com are dead links as of right now.
I got the same SPC lock error.
I believe that is because you need the MSL. This should work for you phone credit to shiftr182 for this guide.
http://forum.xda-developers.com/showthread.php?t=1745888
DX
Peoplearmy said:
I believe that is because you need the MSL. This should work for you phone credit to shiftr182 for this guide.
http://forum.xda-developers.com/showthread.php?t=1745888
DX
Click to expand...
Click to collapse
Thanks. Got a little further. It starts the backup, but now fails at 16% with "Roaming Lists could not be read."
Tried on both stock and insecure kernel. Tried PRL/Profile update + reboot for kicks, no change. Not sure what else to try, googling doesn't help.
edit: Do you know of anyone on Verizon that has successfully backed up? I checked their forum and they only have a guide for doing the IMEI injection. I'm assuming the 7 successful Verizon restores you have listed in your original thread are restores by injection and not from a backup?
Philosuffer said:
Thanks. Got a little further. It starts the backup, but now fails at 16% with "Roaming Lists could not be read."
Tried on both stock and insecure kernel. Tried PRL/Profile update + reboot for kicks, no change. Not sure what else to try, googling doesn't help.
edit: Do you know of anyone on Verizon that has successfully backed up? I checked their forum and they only have a guide for doing the IMEI injection. I'm assuming the 7 successful Verizon restores you have listed in your original thread are restores by injection and not from a backup?
Click to expand...
Click to collapse
That is correct 6 were through injection 1 was through a backup. There are however plenty of Verizon folks who were able to do the backup without any problems. They also however didn't need their MSIL and were able to use the default spc of 000000. I will have to dig a bit deeper for Sprint. I prefer us all safe and not just 3 carriers. Thank you for your efforts
DX
Are there any reports of this happening to sprint users? Jw
Sent from my SGH-I747 using Tapatalk 2
did anyone try...
The option in mskips toolkit. Cant say wheather it works(as I haven't had to restore it) but it does a efs backup now. I know the imei isn't there anymore (don't know that I necessarily believe that) but don't hurt to try.
---------- Post added at 11:48 AM ---------- Previous post was at 11:44 AM ----------
bgolden84 said:
Are there any reports of this happening to sprint users? Jw
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Haven't seen any with this phone. Have seen cases on other sprint phones tho, so I'd definitely say it can
Backup work for me with the default 000000, but that being said the only way i was able to get my MSL was an app "Get My MSL" from google play
this guilde didn't work for me http://forum.xda-developers.com/showthread.php?t=1745888
credit goes to hofs1 for post in guilde above
with "Get My MSL" if it doesn't work at first for you do these steps
1. run get my MSL app
2. hit home button to not close app
3. go to dialer type ##DATA#
4. select edit
5. type any code
6. rerun get my MSL app
you should be gtg
spyderdreams said:
Backup work for me with the default 000000, but that being said the only way i was able to get my MSL was an app "Get My MSL" from google play
this guilde didn't work for me http://forum.xda-developers.com/show....php?t=1745888
with "Get My MSL" if it doesnt work at first for you do these steps
1. run get my MSL app
2. hit home button to not close app
3. go to dialer type ##DATA#
4. select edit
5. type any code
6. rerun get my MSL app
you should be gtg
Click to expand...
Click to collapse
How exactly did that guide "not work for you" but your repeating the the instructions almost to a T here? Dont get it
billard412 said:
How exactly did that guide "not work for you" but your repeating the the instructions almost to a T here? Dont get it
Click to expand...
Click to collapse
getprop ril.MSL in terminal and / or adding /system/bin/msl and running getprop ril.MSL is not the same thing as downloading an app from the market
I am not going to go into anymore in detail about this for you cause we will be getting off topic
edit: ok found hofs1 post further in thanks "hofs1"
If "get my msl" fails to return a number ho to the dialer an ##3282# select edit and enter any Number. Press home and run get my msl again.
Sent from my SPH-L710 using xda app-developers app
ooxcfhxoo said:
If "get my msl" fails to return a number ho to the dialer an ##3282# select edit and enter any Number. Press home and run get my msl again.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
It worked perfectly for me!
Sent from my SPH-L710 using xda premium
Philosuffer said:
Thanks. Got a little further. It starts the backup, but now fails at 16% with "Roaming Lists could not be
Click to expand...
Click to collapse
I realize this is the Sprint forum and I have a US Cellular phone my Google search landed me here. I am getting this exact message and was wondering if you have been able to get past this and get a complete backup of your IMEI. If so could you describe how you did it hopefully the info would be helpful for us USCC users.
Sent from my SCH-R530U using Tapatalk 2
how are people loosing their imei in the first place
Roaming Lists could not be read.
I put in my correct MSL. Is there a fix for this?
When attempting to do the AWS mod I get:
Could not Communicate in Diagnostic Mode
I now have a bricked modem due to some sort of lock. I'll flash a modem and see what happens.
I flashed a ROM and my ICCID is now listed as "unknown". Any fix for that?
Sent from my SPH-L710 using xda app-developers app
I have a SPRINT SPH-L710 (Galaxy S3) with stock Rom and it is NOT rooted.
I have not lost my IMEI i just want to make a regular backup.
I have followed the directions in the first post perfeclyt and i can see my phone in backup section and under Port (it shows my phone)
I enter my SPC and hit "Start Button" to start backup procedure and it unlocks phone and starts to read phone and backing up.
it makes it to 47% every time and says
Status = Memory Backup Failed
Errors = Received an invalid command from the phone
thanks
just wanted to add i have now rooted phone and installed CWM and it still does same exact thing
Hello,
I used to be able to get my MSL by doing ##DATA# in dialer, entering 6 random digits then doing getprop ril.MSL in connect bot, but this no longer works after 4.1.2 update.. I even wiped my phone and rooted with CWM and tried it again.. no luck.. I have googled the crap out of this trying to see if there is a way to get msl from CWM recovery but I cannot find anything..
Help would be appreciated!
Lord
Sprint GS3
lordinfamous666 said:
Hello,
I used to be able to get my MSL by doing ##DATA# in dialer, entering 6 random digits then doing getprop ril.MSL in connect bot, but this no longer works after 4.1.2 update.. I even wiped my phone and rooted with CWM and tried it again.. no luck.. I have googled the crap out of this trying to see if there is a way to get msl from CWM recovery but I cannot find anything..
Help would be appreciated!
Lord
Sprint GS3
Click to expand...
Click to collapse
I believe this belongs in the Questions forum instead of the General section. Anyways, to answer your question, use aLogcat.
1. Open up dialer, enter ##3282#
2. Open aLogcat
3. Menu > Clear log
4. Hold home button, go back to EPST Menu
5. Enter random 6 numbers into MSL field
6. Go back to aLogcat
7. Locate the line that says "MSL Code="
8. Write down those digits and store them somewhere they will not be lost
Android Attack said:
I believe this belongs in the Questions forum instead of the General section. Anyways, to answer your question, use aLogcat.
1. Open up dialer, enter ##3282#
2. Open aLogcat
3. Menu > Clear log
4. Hold home button, go back to EPST Menu
5. Enter random 6 numbers into MSL field
6. Go back to aLogcat
7. Locate the line that says "MSL Code="
8. Write down those digits and store them somewhere they will not be lost
Click to expand...
Click to collapse
Thanks, I tried this 5 times following exactly what you said and there is no msl line anywhere in the alogcat list.. even searched for it
ive tried the same thing and no luck. it was working before the update. though it was just me. none of the previous ways work now.
I'm having this problem too. I was thinking of flashing a 4.0.4 rom after backing up and get my MSL then restore from my backup. That should work right?
Sent from my SPH-L710 using xda premium
Let me help y'all out http://forum.xda-developers.com/showthread.php?t=2159054
Sent from my SPH-L710 using Tapatalk 2
auau465121 said:
Let me help y'all out http://forum.xda-developers.com/showthread.php?t=2159054
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
That seems good, but it doesn't say anything about MSL. Will it still work on getting MSL?
Sent from my SPH-L710 using xda premium
Humzaman said:
That seems good, but it doesn't say anything about MSL. Will it still work on getting MSL?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I just installed the .zip file in CWM and rebooted and i still am in the exact same boat
lordinfamous666 said:
I just installed the .zip file in CWM and rebooted and i still am in the exact same boat
Click to expand...
Click to collapse
Yup I tried it too. Nothing changed...
Sent from my SPH-L710 using xda premium
I was lost at hello??????
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for you cooperation
Friendly Neighborhood Moderator
Thanks!
Bumping for anyone who has an idea now that thread is in the right place! I still have had no luck.
lordinfamous666 said:
Thanks!
Bumping for anyone who has an idea now that thread is in the right place! I still have had no luck.
Click to expand...
Click to collapse
Same here
Sent from my SPH-L710 using xda premium
Use terminal emulator instesd of connect bot. Works fine for me on 4.1.2 on the note 2 which is pretty close to the same base firmware just different add ons
You can also get it by starting an online activation on sprint.com and then once you enter your esn/imei it will bring up the master reset and provisioning info and your MSL will be in the instructions list, write it down and close out the page
I like to break stuff!
-EViL-KoNCEPTz- said:
Use terminal emulator instesd of connect bot. Works fine for me on 4.1.2 on the note 2 which is pretty close to the same base firmware just different add ons
You can also get it by starting an online activation on sprint.com and then once you enter your esn/imei it will bring up the master reset and provisioning info and your MSL will be in the instructions list, write it down and close out the page
I like to break stuff!
Click to expand...
Click to collapse
Already tried terminal Emulator, that did not work either and trying to activate phone on sprint.com gave me an incorrect number message... I KNOW i was typing the right number... I ended up just calling Sprint, telling them that I had work done for poor signal issues with a tech and I did a full wipe of my device so I need my MSL to repeat the steps that the tech gave me.. they handed the MSL right over no problem and this time I saved it in my email...
I would recommended spending 10 minutes on the phone with Sprint instead of loading a 4.1.1 or older ROM.. save yourself some time.
lordinfamous666 said:
Already tried terminal Emulator, that did not work either and trying to activate phone on sprint.com gave me an incorrect number message... I KNOW i was typing the right number... I ended up just calling Sprint, telling them that I had work done for poor signal issues with a tech and I did a full wipe of my device so I need my MSL to repeat the steps that the tech gave me.. they handed the MSL right over no problem and this time I saved it in my email...
I would recommended spending 10 minutes on the phone with Sprint instead of loading a 4.1.1 or older ROM.. save yourself some time.
Click to expand...
Click to collapse
That's great. What exactly should I say to them though?
Sent from my SPH-L710 using xda premium
Humzaman said:
That's great. What exactly should I say to them though?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
All you gotta do is call support and say I need my MSL. If they ask why, say "because it's mine and I'd like to keep it in my records and lost the ome I wrote down when I activated my phone"
I like to break stuff!
http://forum.xda-developers.com/showthread.php?p=38416225
I had this same problem. The solution is to downgrade rom to ics low ship as referenced in URL. Once on the rom use the suggested get my msl app technique. Works flawlessly.
Sent from my SPH-L710 using Tapatalk 2
There's several methods because I myself had the same problem using 4.1.2 but i wrote down my msl code when i downflashed to 4.1.1
All you need to do really is the methods mentioned above BUT you'll need to do this.
Wipe cache dalvik 2x. Reboot device.
Download and install android terminal emulator from play store.
Open it
go to the dialer and press ##3282#
Edit.
type 000000 or any random number.
Go back to Android Terminal Emulator via Task Manager.
then type this.
Code:
su
getprop ril.MSL
if no number shows. go back to the MSL code screen
retype 000000
let the phone reboot due to typing in the wrong msl too many times.
Go back to dialer and ##3282#
Type in 000000
then redo getprop ril.MSL in the terminal.
You then should be able to get the MSL number.
I've tried it on 4.0.4 and 4.1.1 - LG8 and LJ7 and i've gotten the MSL number but it
didn't work for me on MA4/MA6 leaked and MB1 official OTA.
bump this up because i am too looking to get my MSL from my build MD4 (4.1.2)?
Hey everyone I've been searching the whole entire internet and xda to find out what I need to do exactly to get back LTE. I lost my IMEI after upgrading Cyanogenmod NIghtly without backup of efs folder. I was able to get the IMEI injected manually with NV writer/reader so I can connect to edge but only edge network 2g mode. What do I need or install or do to get back lte. The thread that people point to others that ive searched is deleted thanks
Try a touchwiz stock Rom, then:
Dial: *#197328640#, then select the numbers from the menu in the order: 11865.
Then from the dial pad:
Dial *#2263#
Select WCDMA
Select Wcdma all
Back (or go back to the dial pad again and dial *#2263#)
Select LTE
Select LTE all
Back (or go back to the dial pad again and dial *#2263#)
Select Automatic
Back key on the phone
Reboot
See what happens.
anything evewsfu
shortydoggg said:
Try a touchwiz stock Rom, then:
Dial: *#197328640#, then select the numbers from the menu in the order: 11865.
Then from the dial pad:
Dial *#2263#
Select WCDMA
Select Wcdma all
Back (or go back to the dial pad again and dial *#2263#)
Select LTE
Select LTE all
Back (or go back to the dial pad again and dial *#2263#)
Select Automatic
Back key on the phone
Reboot
See what happens.
Click to expand...
Click to collapse
thanks alot man
I had the same issue, this method didn't work for me.
So far I haven't seen a for sure fix . I tried everything uprooting back to stock , every method , even put the s3 in the factory box for 4months lmao . For real I have been beside my self not a noob my imei went , then reinjected. Still lost , there is post somewhere that a guy does fix them but have to ship it off .. hopefully there got to be a way dude . Good luck
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
ebubbastew said:
So far I haven't seen a for sure fix . I tried everything uprooting back to stock , every method , even put the s3 in the factory box for 4months lmao . For real I have been beside my self not a noob my imei went , then reinjected. Still lost , there is post somewhere that a guy does fix them but have to ship it off .. hopefully there got to be a way dude . Good luck
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I'm in the same boat. I managed to inject the IMEI, but can't get to 4G. After I reboot, I start out on LTE and get knocked back to EDGE within five minutes. Also, Samsung KIES does not recognize the firmware (even after I restore to a stock system).
I thought playing with the CSC to ensure that it matches the rest of the software might have an impact, but I get an error when I try the CSC changer software.
t.s.eliot said:
I'm in the same boat. I managed to inject the IMEI, but can't get to 4G. After I reboot, I start out on LTE and get knocked back to EDGE within five minutes. Also, Samsung KIES does not recognize the firmware (even after I restore to a stock system).
I thought playing with the CSC to ensure that it matches the rest of the software might have an impact, but I get an error when I try the CSC changer software.
Click to expand...
Click to collapse
I'm having the same problem as you. Were you able to find a solution???
shortydoggg said:
Try a touchwiz stock Rom, then:
Dial: *#197328640#, then select the numbers from the menu in the order: 11865.
Then from the dial pad:
Dial *#2263#
Select WCDMA
Select Wcdma all
Back (or go back to the dial pad again and dial *#2263#)
Select LTE
Select LTE all
Back (or go back to the dial pad again and dial *#2263#)
Select Automatic
Back key on the phone
Reboot
See what happens.
Click to expand...
Click to collapse
damn I was hoping this would fix my issue - but it didn't. Been stuck on edge for 3 days now. At first I lost my imei number, but was able to inject it back into the phone - now I can't get away from edge network. I want my 4G back lol
http://forum.xda-developers.com/showthread.php?t=2374063
Sent from my SAMSUNG-SGH-I747 using xda premium
No one comments on this person's suggestion.
The solution
Guys here is the solution (attached)
inject this items using NV reader/writer
was perfect for me
umar4u said:
Guys here is the solution (attached)
inject this items using NV reader/writer
was perfect for me
Click to expand...
Click to collapse
I failed to inject it to my device.
This worked.
umar4u said:
Guys here is the solution (attached)
inject this items using NV reader/writer
was perfect for me
Click to expand...
Click to collapse
umar4u, I can't thank you enough. I have been paying AT&T for 2 months for a phone that didn't even work as a phone. This fixed it. Download his file and refer to the video in this post to inject his file.
http://forum.xda-developers.com/showthread.php?t=1804117
This just saved my day... Thanks!
Although it says it failed on 3 things, it works!
Life Saver!!!
Everyone, this works!!!
umar4u said:
Guys here is the solution (attached)
inject this items using NV reader/writer
was perfect for me
Click to expand...
Click to collapse
Thank you so much! This is great! It worked! I tried every other possible fix and no avail. Then i came across this and boom! Thanks again! :victory:
you can try entering this menu * # * # 4636 # * # * into the first option on the telephony information and down to where it says set preferred network type and change it to LTE / GSM / CDMA auto (PRL)
umar4u said:
Guys here is the solution (attached)
inject this items using NV reader/writer
was perfect for me
Click to expand...
Click to collapse
Thank you for the solution Umar, but how did you figure out that these are the only NV Items needed? BTW, are you who I think you are?
maxqas said:
Thank you for the solution Umar, but how did you figure out that these are the only NV Items needed? BTW, are you who I think you are?
Click to expand...
Click to collapse
You are welcome. i found this file on internet, someone posted it. Basically it is NV items for 3g or 4g, I think.
And I don't know who you think I am.
Nice to see this worked for people.
---------- Post added at 01:14 AM ---------- Previous post was at 01:05 AM ----------
RayZhang said:
I failed to inject it to my device.
Click to expand...
Click to collapse
Hove you done this:
Connect phone to computer.
In Stock Dialer, enter *#7284#
A PhoneUtil Menu Should open
Press Qualcomm USB Settings button
select RMNET + DM + MODEM and press OK.
Open Device Manager and expand "Ports"
Note the COM Port # listed next to "Samsung Mobile USB Serial Port (COM#)
Ensure both boxes in Top bar are checked.
Click Connect in the Top Bar
Later you can write NV items
dont forget to Go back into the PhoneUtil menu and switch back to MTP + ADB
Thanks!
umar4u said:
Guys here is the solution (attached)
inject this items using NV reader/writer
was perfect for me
Click to expand...
Click to collapse
I registered just to say Thanks!!
I was trying different methods for hours, and this worked perfectly for me.
I searched for weeks for a solution!!! Thank you so much!! *___*
Hey everyone.
Been a LONG time since I have been on XDA. Got the new Note 5 and decided to customize my Note 4. I downloaded TWRP (Latest from their site) for my Sprint Note 4 and something strange has happened.
After flashing through Odin, my screen touches are off by 3/4" on part of the screen... Meaning, On the top 1/3 of the screen, my touches act normal but on the bottom 2/3, they are "off" as in, when I touch, the input registers about 3/4 of an inch lower than where I am touching.
I have tried redownloading and reflashing TWRP and also tried the latest CWM Recovery. I was able to get Hybrid 3.0 Rom to flash and after booting up, during initial setup, it's still the same way. Meaning when I touch the "2" on the keyboard, it registers the letter "z".
UPDATE*** (Video https://youtu.be/MtU9qoIZooM )
After fidling and getting the ROM to launch, I notice I can use my SPen just fine. Going to take video and post what is happening. Here are a few pics of the screen touch turned on in Developer mode. As you can see in the images below, with my finger, the touches are further off the lower I get on the screen but fine with the SPen.
Video
https://youtu.be/MtU9qoIZooM
thermus said:
Hey everyone.
Been a LONG time since I have been on XDA. Got the new Note 5 and decided to customize my Note 4. I downloaded TWRP (Latest from their site) for my Sprint Note 4 and something strange has happened.
After flashing through Odin, my screen touches are off by 3/4" on part of the screen... Meaning, On the top 1/3 of the screen, my touches act normal but on the bottom 2/3, they are "off" as in, when I touch, the input registers about 3/4 of an inch lower than where I am touching.
I have tried redownloading and reflashing TWRP and also tried the latest CWM Recovery. I was able to get Hybrid 3.0 Rom to flash and after booting up, during initial setup, it's still the same way. Meaning when I touch the "2" on the keyboard, it registers the letter "z".
UPDATE*** (Video https://youtu.be/MtU9qoIZooM )
After fidling and getting the ROM to launch, I notice I can use my SPen just fine. Going to take video and post what is happening. Here are a few pics of the screen touch turned on in Developer mode. As you can see in the images below, with my finger, the touches are further off the lower I get on the screen but fine with the SPen.
Click to expand...
Click to collapse
Heard of this before and it was due to flashing wrong recovery for your device. Maybe try going back to complete stock unrooted with official tar.
Will give that a try. That's the one thing I didn't try.
it happened to me, dial *#2663# and update the tsp fw update (general), it eventually fixed the issue for me although i had to do it frequently for at least a month until the phone forgot about it
sr.bond said:
it happened to me, dial *#2663# and update the tsp fw update (general), it eventually fixed the issue for me although i had to do it frequently for at least a month until the phone forgot about it
Click to expand...
Click to collapse
HELL YES!!!!!!! I was just coming back to report that the flashing to stock do NOT fix it. Your recommendation work beautifully! THANK YOU!!!!:laugh:
Anyone have ideas? I have the US Cellular variant and this exact problem after flashing TWRP except that *#2663# doesn't do anything... I've seen someone do it in a video and nothing happens when I hit the last pound. Is it different for USC?
For anyone wondering I had to root, enable hidden menu via editing the file at efs/carrier/hiddenmenu, once I did that the *#2663# worked and I was able to perform the update. Touchscreen works fine now.
I am having the same Issue
I am not a noob been doing this for awhile but the other day I had grabbed the wrong TWRP recovery for my Note 4 I grabbed the Note 4 edge and now my screen is out of whack and I cant used the *#2663# code to bring up the TSP FW so.... any help would be appreciated
I have tried flashing different ROMS, Kernels to get back to stock that didnt work, I have tried Galaxy tools but I cant find how to bring up the TSP menu I have tried flipping the recoveries and wiping and formatting to no avail, so Need some help if possible
SysEng1967 said:
I am not a noob been doing this for awhile but the other day I had grabbed the wrong TWRP recovery for my Note 4 I grabbed the Note 4 edge and now my screen is out of whack and I cant used the *#2663# code to bring up the TSP FW so.... any help would be appreciated
I have tried flashing different ROMS, Kernels to get back to stock that didnt work, I have tried Galaxy tools but I cant find how to bring up the TSP menu I have tried flipping the recoveries and wiping and formatting to no avail, so Need some help if possible
Click to expand...
Click to collapse
Sometimes the first step is restore full stock tar and then try the dialer code.
http://forum.xda-developers.com/showthread.php?p=63868221
Sent from my SM-N910P using Tapatalk
Stock Tar
samep said:
Sometimes the first step is restore full stock tar and then try the dialer code.
http://forum.xda-developers.com/showthread.php?p=63868221
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have been trying the stock Tar but anything "stock" seems to boot loop tried wiping everything then tried wiping davlik and cache after ROM flash
I have been also trying to get the *#2663# menu to come up edited build.props and created /efs/carrier/HiddenMenu but I can never get the tsp menu it works great on my Note II and thats jellybomb ROM version 21 and if I dial *#2663# bam instant TSP menu
SysEng1967 said:
I have been trying the stock Tar but anything "stock" seems to boot loop tried wiping everything then tried wiping davlik and cache after ROM flash
I have been also trying to get the *#2663# menu to come up edited build.props and created /efs/carrier/HiddenMenu but I can never get the tsp menu it works great on my Note II and thats jellybomb ROM version 21 and if I dial *#2663# bam instant TSP menu
Click to expand...
Click to collapse
When you goto download mode, does your phone's display show reactivation lock enabled or disabled?
Even if it is enabled, you should be able to successfully flash the stock tar that matches your bootloader (should be the last full update your phone completed- I wouldn't say bootloops count as successful upgrade or downgrade of bootloader). You would then need to let it auto reboot and sign in with original Google account password during the setup wizard.
If your reactivation lock is disabled, pay close attention to what you're flashing and watch Odin log for issues. If you can boot to stock recovery, factory reset and try Odin again.
Edit: what stock tar are you trying you flash? Most likely, you still won't succeed in downgrading the bootloader to lower security bootloader once you update to OE1 or higher.
Sent from my SM-N910P using Tapatalk
Thanks that ROM worked
samep said:
When you goto download mode, does your phone's display show reactivation lock enabled or disabled?
Even if it is enabled, you should be able to successfully flash the stock tar that matches your bootloader (should be the last full update your phone completed- I wouldn't say bootloops count as successful upgrade or downgrade of bootloader). You would then need to let it auto reboot and sign in with original Google account password during the setup wizard.
If your reactivation lock is disabled, pay close attention to what you're flashing and watch Odin log for issues. If you can boot to stock recovery, factory reset and try Odin again.
Edit: what stock tar are you trying you flash? Most likely, you still won't succeed in downgrading the bootloader to lower security bootloader once you update to OE1 or higher.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you the ROM helped me fix my issue and now I am back to good
sr.bond said:
it happened to me, dial *#2663# and update the tsp fw update (general), it eventually fixed the issue for me although i had to do it frequently for at least a month until the phone forgot about it
Click to expand...
Click to collapse
:good:
Total awesomeness!!! This worked perfectly. Thank you for sharing with the community!
The *#2663# is like sugar......Thank you veeeeeeeeryyyyyyy much
Thanks a lot for *#2663# !!! Even after 8 years I need the Gallaxy Note 4, because its one of the last Phones with easy changeable batteries.
Recently i've done a firmware change, after that, my phone began to behave weird, it seems like the touchscreen is uncalibrated or something like that, when i press somewhere my phone choose another:crying:
Elielnew said:
Recently i've done a firmware change, after that, my phone began to behave weird, it seems like the touchscreen is uncalibrated or something like that, when i press somewhere my phone choose another:crying:
Click to expand...
Click to collapse
Verify the firmware you installed is for your phone and verify md5.
If not, get the right stock tar, verify md5, flash in Odin and goto dialer and enter and select this with S-Pen for accuracy: *#2663# and then tap TSP FW update (General).
If unsure what happened, I'd suggest you redo all the steps anyway.
Sent from my SM-N910P using Tapatalk
You updated twrp. With the note edge recovery. Touch screens off by like a 1/4 inch right..... Flash right recovery and do above update firmware. It will fix it.
Sent from my 0x1 Note 4...... I love tep
kaos420 said:
You updated twrp. With the note edge recovery. Touch screens off by like a 1/4 inch right..... Flash right recovery and do above update firmware. It will fix it.
Sent from my 0x1 Note 4...... I love tep
Click to expand...
Click to collapse
Please describe for action.
Kronk442190344 said:
Please describe for action.
Click to expand...
Click to collapse
Read the thread
Sent from my 0x1 Note 4...... I love tep