Develop Bugs

[DEV][WIP] Recovery of IMEI/Baseband of Sprint Galaxy Note 2

Please Note: No other method listed in the GN2, GS3 forums work for this particular problem. I, as well as a few others have had this happen when flashing different ROMs. I have no idea what causes it but I do have an idea as to how to fix it. I just can't because what I need seems to be disabled in the phone.
Also, I did make a backup of my EFS and a restore does not fix this particular problem.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
Problem #3:
And probably the biggest problem: ADB does not recognize the phone. ADB debugging is enabled on the phone in Developer Options but the icon on the notification button doesn't appear. Nor does ADB recognize the phone in recovery. So therefor I cannot transfer files this way either. "nvbackup/nvrestore" can not be used because of this either.
The following methods have all been tried and have failed. Yes, I know what I am doing,
http://forum.xda-developers.com/showthread.php?t=1867442
http://forum.xda-developers.com/showthread.php?t=1852255
http://forum.gsmhosting.com/vbb/f606/tutorial-galaxy-s3-backup-restore-imei-without-root-1513909/

I fell victim to #1 the IMEI wipeout I had to take my phone back for a replacement
Sent from my SPH-L900 using xda premium

Me too. ..
Sent from my MASSIVE Galaxy Note® II...*

mackentosh said:
I fell victim to #1 the IMEI wipeout I had to take my phone back for a replacement
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
but how did it happened ? can u please explain steps what u did that wiped yr imei?

t3project said:
Please Note: No other method listed in the GN2, GS3 forums work for this particular problem. I, as well as a few others have had this happen when flashing different ROMs. I have no idea what causes it but I do have an idea as to how to fix it. I just can't because what I need seems to be disabled in the phone.
Also, I did make a backup of my EFS and a restore does not fix this particular problem.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
Problem #3:
And probably the biggest problem: ADB does not recognize the phone. ADB debugging is enabled on the phone in Developer Options but the icon on the notification button doesn't appear. Nor does ADB recognize the phone in recovery. So therefor I cannot transfer files this way either. "nvbackup/nvrestore" can not be used because of this either.
The following methods have all been tried and have failed. Yes, I know what I am doing,
http://forum.xda-developers.com/showthread.php?t=1867442
http://forum.xda-developers.com/showthread.php?t=1852255
http://forum.gsmhosting.com/vbb/f606/tutorial-galaxy-s3-backup-restore-imei-without-root-1513909/
Click to expand...
Click to collapse
i got the same problem with tmobile ver the problem is the partition i did tried to repartition in odin with gt-7100 pit file it did not work
can you see your storge and see your internal sd space
sorry for my english

An fyi when u get ur baseband back 3g will not work. I was able to get mine all back and working but I was always on 1x. T3 hit me up in gtalk.
Sent from my SPH-L900 using Tapatalk 2

gotojanoo said:
but how did it happened ? can u please explain steps what u did that wiped yr imei?
Click to expand...
Click to collapse
Well I was testing a rom for someone, I wont tell which rom but he said it was the "in call recorder" he added. He's got it fixed now but it did wipe everything. I managed to restore it back to stock with no root but it bricked after that. Now I see why carriers dont like to unlock bootloaders cause of people bricking their phone and taking them back
Sent from my SPH-L900 using xda premium

t3project said:
Please Note: No other method listed in the GN2, GS3 forums work for this particular problem. I, as well as a few others have had this happen when flashing different ROMs. I have no idea what causes it but I do have an idea as to how to fix it. I just can't because what I need seems to be disabled in the phone.
Also, I did make a backup of my EFS and a restore does not fix this particular problem.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
Problem #3:
And probably the biggest problem: ADB does not recognize the phone. ADB debugging is enabled on the phone in Developer Options but the icon on the notification button doesn't appear. Nor does ADB recognize the phone in recovery. So therefor I cannot transfer files this way either. "nvbackup/nvrestore" can not be used because of this either.
The following methods have all been tried and have failed. Yes, I know what I am doing,
http://forum.xda-developers.com/showthread.php?t=1867442
http://forum.xda-developers.com/showthread.php?t=1852255
http://forum.gsmhosting.com/vbb/f606/tutorial-galaxy-s3-backup-restore-imei-without-root-1513909/
Click to expand...
Click to collapse
You care to clarify which ROM you flashed in particular caused this to happen so that we don't replicate your problem? I want to assume it's your own ROM but just want to make sure.

mackentosh said:
Well I was testing a rom for someone, I wont tell which rom but he said it was the "in call recorder" he added. He's got it fixed now but it did wipe everything. I managed to restore it back to stock with no root but it bricked after that. Now I see why carriers dont like to unlock bootloaders cause of people bricking their phone and taking them back
Click to expand...
Click to collapse
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?

ffolkes said:
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
Click to expand...
Click to collapse
i did flash the s3 rom and after that i lost everythng my phone i need to know how to restor the orgenal sd card cuz im looking with rootexplore it sdcard0
when i go to setting storge it only show 266mb used and 0.00 avilabel any body can help please

mackentosh said:
Well I was testing a rom for someone, I wont tell which rom but he said it was the "in call recorder" he added. He's got it fixed now but it did wipe everything. I managed to restore it back to stock with no root but it bricked after that. Now I see why carriers dont like to unlock bootloaders cause of people bricking their phone and taking them back
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Which ROM had the "In Call Recorder"? I've been looking for a replacement to that functionality after dropping HTC/ Qualcomm with the 2WCR patch on the kernel. ..
Sent from my SPH-L900 using xda app-developers app

You cant flash a s3 rom the partitions are different. Even the partitions forbthe international note 2. Tmo. Att. Verizon and sprint note 2 are different.
Try flashing the stock tar from sex tape or viper boy. This should fix those issues. Then update the phones prl. Profile. Software. And firmware. And see if u have 3g and everything else.
Then start over.
Sent from my SPH-L900 using Tapatalk 2

ffolkes said:
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
Click to expand...
Click to collapse
it wasnt a rogue rom. it was two seperate private roms that were never released to the public
there is a very simple fix to this, i've fixed 2 phones this morning already with it. i'll post it up in a few

gotojanoo said:
but how did it happened ? can u please explain steps what u did that wiped yr imei?
Click to expand...
Click to collapse
it didnt actually wipe our imei. it repartitioned the phone.

t3project said:
it wasnt a rogue rom. it was two seperate private roms that were never released to the public
there is a very simple fix to this, i've fixed 2 phones this morning already with it. i'll post it up in a few
Click to expand...
Click to collapse
Good to know it wasn't released here publicly. Happy to hear you found a solution to the problem too.

dc13 said:
You cant flash a s3 rom the partitions are different. Even the partitions forbthe international note 2. Tmo. Att. Verizon and sprint note 2 are different.
Try flashing the stock tar from sex tape or viper boy. This should fix those issues. Then update the phones prl. Profile. Software. And firmware. And see if u have 3g and everything else.
Then start over.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Try this.

ffolkes said:
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
Click to expand...
Click to collapse
I said I was testing a rom which means I was the only person he released it to at the time. I dont want to reveal the rom or the dev because I dont want any negativity towards him he's a great dev and your probably running his rom right now. So dont worry there isnt a rogue rom floating around
Sent from my SPH-L900 using xda premium

t3project said:
it wasnt a rogue rom. It was two seperate private roms that were never released to the public
there is a very simple fix to this, i've fixed 2 phones this morning already with it. I'll post it up in a few
Click to expand...
Click to collapse
whats the fix cuz im going thru this problem right now ...i cant get any service (radios)
EDIT: NVM I JUST FLASHED TO STOCK RECOVERY THEN FLASHED STOCK LJ1 THRU ODIN AND ALL IS WELL NOW

mccurt29 said:
whats the fix cuz im going thru this problem right now ...i cant get any service (radios)
EDIT: NVM I JUST FLASHED TO STOCK RECOVERY THEN FLASHED STOCK LJ1 THRU ODIN AND ALL IS WELL NOW
Click to expand...
Click to collapse
simple, wasnt it? lol..................

mackentosh said:
I said I was testing a rom which means I was the only person he released it to at the time. I dont want to reveal the rom or the dev because I dont want any negativity towards him he's a great dev and your probably running his rom right now. So dont worry there isnt a rogue rom floating around
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Was it mine? I can tell you that if any of the previous stuff happened to you, it wasn't from the ROM. Could have been a bad download, coinsidence, etc. The ROM flash wouldn't have caused it.
Sent from my SPH-L900 using Tapatalk 2

[Q] PLEASE HELP! LG G3 Bricked?

So, on Thursday I picked up an LG G3 from Verizon. I was absolutely loving it. But like most people, I wanted custom ROM's and roots and all the fun stuff you can do with android phones. I rooted my device the day I got it with IORoot. Everything is working fine at this point.
After this, i wanted a custom ROM. I found that there wasn't many for my specific model, but i did see the Sphinx G3 Neo ROM. I payed no attention to what variant it was for and loaded it up on my phone. At first, everything was working perfectly and it was butter smooth. But then I noticed whatever messaging app I tried to use would not work. I did a factory reset and then did the same process to load Sphinx on my G3. This time, messages were working, however, mobile data was not. I finally had enough of this and decided to return to the stock ROM. I found all of the stock files and was attempting to use the TOT method. I put the phone in download mode (which it won't come out of btw) and tried to start flashing. I then realized what I had done and saw that my device was reading something like D855. So when I downloaded the Verizon files it wont work. But will I be able to fix this? Have any of you had this problem before? This phone is brand new and I cannot replace it at this point. I would really appreciate it if someone could help me out.

Hi,
So sad to hear that. Have you tried TOT files from this thread?
I hope your imei is intact.

VeriLG said:
So, on Thursday I picked up an LG G3 from Verizon. I was absolutely loving it. But like most people, I wanted custom ROM's and roots and all the fun stuff you can do with android phones. I rooted my device the day I got it with IORoot. Everything is working fine at this point.
After this, i wanted a custom ROM. I found that there wasn't many for my specific model, but i did see the Sphinx G3 Neo ROM. I payed no attention to what variant it was for and loaded it up on my phone. At first, everything was working perfectly and it was butter smooth. But then I noticed whatever messaging app I tried to use would not work. I did a factory reset and then did the same process to load Sphinx on my G3. This time, messages were working, however, mobile data was not. I finally had enough of this and decided to return to the stock ROM. I found all of the stock files and was attempting to use the TOT method. I put the phone in download mode (which it won't come out of btw) and tried to start flashing. I then realized what I had done and saw that my device was reading something like D855. So when I downloaded the Verizon files it wont work. But will I be able to fix this? Have any of you had this problem before? This phone is brand new and I cannot replace it at this point. I would really appreciate it if someone could help me out.
Click to expand...
Click to collapse
I don't it is bricked per say. I do believe that the only way to solve the problem will be to do as you were trying, return it to stock with .tot files, you just need to find some information which I did see in the threads somewhere with regards to getting out of download mode.
Once you get that done and flash back to stock, then you can root again, I would suggest using Stump root, and the unlock the bootloader with Bump, and this would be a good time to make a backup with the recovery TWRP.
Be calm and read as much as possible, I hope you sort it out. Good luck.
Sent from my LG-D855 using Tapatalk

hierarchy666 said:
Hi,
So sad to hear that. Have you tried TOT files from this thread?
I hope your imei is intact.
Click to expand...
Click to collapse
Just started the download hoping for different results.
BioVolt said:
I don't it is bricked per say. I do believe that the only way to solve the problem will be to do as you were trying, return it to stock with .tot files, you just need to find some information which I did see in the threads somewhere with regards to getting out of download mode.
Once you get that done and flash back to stock, then you can root again, I would suggest using Stump root, and the unlock the bootloader with Bump, and this would be a good time to make a backup with the recovery TWRP.
Be calm and read as much as possible, I hope you sort it out. Good luck.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
I have not found ANY information regarding being stuck in download mode. Not asking for you to go digging, but if happen to find a thread about that I would be pleased if you sent it my way. I have attached some screenshots for you to see the error I'm getting.

VeriLG said:
Just started the download hoping for different results.
I have not found ANY information regarding being stuck in download mode. Not asking for you to go digging, but if happen to find a thread about that I would be pleased if you sent it my way. I have attached some screenshots for you to see the error I'm getting.
Click to expand...
Click to collapse
Can you confirm that you are using a USB 2 port and not a USB 3? Just in case...
Sent from my LG-D855 using Tapatalk
---------- Post added at 10:39 AM ---------- Previous post was at 10:30 AM ----------
Also another question, what modes are you able to boot into when holding down etc the right combination of keys?
Or does it always boot into download mode no matter what?
Sent from my LG-D855 using Tapatalk
---------- Post added at 10:42 AM ---------- Previous post was at 10:39 AM ----------
And finally, have you tried using the LG pc suite?
Please note I have not had any of these problems and so I am only offering suggestions of various things I have read while owning a G3, just makes me sad to see posts like this... Really hope you manage to get it working again... Afterall, we finally have unlocked bootloader!
Sent from my LG-D855 using Tapatalk

Went and picked up another G3 today. Thanks everyone.

VeriLG said:
Went and picked up another G3 today. Thanks everyone.
Click to expand...
Click to collapse
Probably best not to flash something again... like ever

Vivasanti said:
Probably best not to flash something again... like ever
Click to expand...
Click to collapse
Nah, just gotta pay more attention to what I'm doing. Plus, bump just came out.

I take 6 hours to find solution, must use another dll "LGUP_8974.dll"
This one let .tot file take control and don't check phone model, if someone have the same issues this can help

Stock S6 Edge ODIN flashable firmware?

Does anyone have a stock firmware of their S6 Edge T-Moible? that's ODIN flashable. I bricked my S6 trying to root it and had the KNOX security on. Now it just boot loop.

Jjgh

Refer to this how-to article and read the 'Note' that is posted.
http://jtechd.net/2015/04/how-to-root-samsung-galaxy-s6-galaxy-s6-edge-downloads/

Protomize said:
Does anyone have a stock firmware of their S6 Edge T-Moible? that's ODIN flashable. I bricked my S6 trying to root it and had the KNOX security on. Now it just boot loop.
Click to expand...
Click to collapse
Did you try and flash the S6 file (non-edge file) to root your phone? For many that corrects what looks to be a bricked phone.

I did the same thing the OP had done, referring to enabling KNOX prior to rooting, and none of anyone's suggestions through the past multiple days have worked. Enabling "KNOX" under the "Security"
settings is a big no-no, or so it seems from the few that have done it. Might be worth somebody making a thread just letting people know NOT to do that if they don't wish for an expensive brick until a stock ODIN tar surfaces. It makes the phone bootloop and useless even when using the regular S6 autoroot tar. It's also interesting how nobody answered the OP's actually question, though. "Is there an actual stock ODIN tar for this phone yet?" I would like to know the same, even though my own research has come up negatory thus far. Focus on the dude's question rather than waste time with other suggestion(s) which they likely already know haven't worked.

Ker~Man said:
I did the same thing the OP had done, referring to enabling KNOX prior to rooting, and none of anyone's suggestions through the past multiple days have worked. Enabling "KNOX" under the "Security"
settings is a big no-no, or so it seems from the few that have done it. Might be worth somebody making a thread just letting people know NOT to do that if they don't wish for an expensive brick until a stock ODIN tar surfaces. It makes the phone bootloop and useless even when using the regular S6 autoroot tar. It's also interesting how nobody answered the OP's actually question, though. "Is there an actual stock ODIN tar for this phone yet?" I would like to know the same, even though my own research has come up negatory thus far. Focus on the dude's question rather than waste time with other suggestion(s) which they likely already know haven't worked.
Click to expand...
Click to collapse
Why would you enable KNOX when you are trying to root a phone tho ?

Ker~Man said:
I did the same thing the OP had done, referring to enabling KNOX prior to rooting, and none of anyone's suggestions through the past multiple days have worked. Enabling "KNOX" under the "Security"
settings is a big no-no, or so it seems from the few that have done it. Might be worth somebody making a thread just letting people know NOT to do that if they don't wish for an expensive brick until a stock ODIN tar surfaces. It makes the phone bootloop and useless even when using the regular S6 autoroot tar. It's also interesting how nobody answered the OP's actually question, though. "Is there an actual stock ODIN tar for this phone yet?" I would like to know the same, even though my own research has come up negatory thus far. Focus on the dude's question rather than waste time with other suggestion(s) which they likely already know haven't worked.
Click to expand...
Click to collapse
Hey, I fixed it it. Watch this: https://www.youtube.com/watch?v=qCh0QuEwAgY

Protomize said:
Hey, I fixed it it. Watch this: https://www.youtube.com/watch?v=qCh0QuEwAgY
Click to expand...
Click to collapse
Thank You soooooooo much. that actually worked. thank you thank you thank you.

Thank you all for this. I would also like to know if this deletes all the user data/apps/contacts as well? I'm trying to restore the phone to stock so I can return it but as others have said with the root performed I am unable to hard reset/restore to factory so I am looking for a work around. Thanks in advance.

Yes, it deletes all user data, but the phone will have root.

samanbabah said:
Thank You soooooooo much. that actually worked. thank you thank you thank you.
Click to expand...
Click to collapse
Glad it was able to work.

So when rooting a T-Mo Edge first time, we should use the std S6 (SM-G920T) autoroot file, and not the file listed for the edge?

SykesAT said:
So when rooting a T-Mo Edge first time, we should use the std S6 (SM-G920T) autoroot file, and not the file listed for the edge?
Click to expand...
Click to collapse
yes you use the G920T but that will mess up your recovery, so be aware.

After using galaxy s6 cf auto root file restore your recovery by following this:
http://zidroid.com/download-t-mobile-galaxy-s6-edge-g925t-stock-recovery

Zi.Droid said:
After using galaxy s6 cf auto root file restore your recovery by following this:
zidroid. com/download-t-mobile-galaxy-s6-edge-g925t-stock-recovery
Click to expand...
Click to collapse
I want to thank you for at least getting me back to a recovery mode screen that is readable and starts with the normal icon, that says updating system. I still need to wait for the stock SM-G925T firmware file for the S6 Edge to get back to a working phone. Deleting knox files as I stated in a few threads here is a big no no for now. Just get that bootloop on startup and this has nothing to do with rooting. Is the deleted files. Samsung support confirmed this too. I did try the factory reset which basically wiped the phone of info, which is no big deal. Plenty of backups. Just need the darn tar file for this model. I'm sure it will be out soon.
BTW, I was having issues getting on to any web link site Sammobile.
http://www.hidebux.com/unblock/sammobile.com
Uses a private web proxy to access. Open link, click on unblock and you are in :good:

Docmjldds said:
I still need to wait for the stock SM-G925T firmware file for the S6 Edge to get back to a working phone... Just need the darn tar file for this model. I'm sure it will be out soon.
Click to expand...
Click to collapse
You are still unable to get Kies to work? Did you watch my Video and follow those steps? If you are still having trouble, let me know. Might be a driver issue or something.

SuperSport said:
You are still unable to get Kies to work? Did you watch my Video and follow those steps? If you are still having trouble, let me know. Might be a driver issue or something.
Click to expand...
Click to collapse
ok...doing video. asks for my serial number. It's not the IME. Can't get to about phone settings. Tmobile has no clue how to find my serial number. Calling Samsung if they can match my IME. Maybe you can pm me a number for the Edge.
---------- Post added at 08:53 PM ---------- Previous post was at 08:02 PM ----------
SuperSport said:
You are still unable to get Kies to work? Did you watch my Video and follow those steps? If you are still having trouble, let me know. Might be a driver issue or something.
Click to expand...
Click to collapse
I want to publically thank you for your superb and timely help. What's funny is I'm on a MAC desktop and the Kies Mac version would not connect to my phone even though I have the drivers already on the computer. I use Parallels to boot to a Windows 8 virtual setup. Kies gave me the unsupported device message I think, but after going to the tools menu and following the instructions on the video, all went well. The only nit pick is I believe the Kies program called it the recovery mode to boot into, but they used the correct button combo to actually be in download mode for this to work.
Anyways....much thanks and for all those waiting for stock firmware for the Edge to magically appear, which I'm sure it will eventually, this method works. Word of advice to all.....go into your settings and about device and write down your serial number since it's required when inputting the model number. TMobile and Samsung incorrectly kept telling me the serial number is the same as the IME. IT'S NOT. And that number is NOT on the box labeling either. So without the serial number of your device KIES won't work for this firmware restore. A simple thank you to the person that know, for helping me with that aspect.

Docmjldds said:
I want to publically thank you for your superb and timely help.
Click to expand...
Click to collapse
Thank you for this, and thank you for letting others know about the correct serial number used.
For anyone in the same situation, you CAN borrow a serial number from another device to get the download started just as Docmjldds and I did here. I gave him mine, and the download proceeded as normal. After the phone is flashed, it still retains the correct factory serial that came with your phone.

SuperSport said:
Thank you for this, and thank you for letting others know about the correct serial number used.
For anyone in the same situation, you CAN borrow a serial number from another device to get the download started just as Docmjldds and I did here. I gave him mine, and the download proceeded as normal. After the phone is flashed, it still retains the correct factory serial that came with your phone.
Click to expand...
Click to collapse
You can also get the serial number from download mode. When you first boot into dl mode and you get the warning page press the home button and the IMEI and SN (serial number) are both there with a bar code.

jamcar said:
You can also get the serial number from download mode. When you first boot into dl mode and you get the warning page press the home button and the IMEI and SN (serial number) are both there with a bar code.
Click to expand...
Click to collapse
Great Tip! Thank you for this. I did run into that when I was messing around, but totally forgot about it. Just updated my Video to include this info with a thanks to you.

I think i've bricked my phone

I have what I thought was a n910f so a root was possible but when in download mode it shows up as a n910a which I didnt notice. I used kingroot which also showed my phone as a n910f and when my phone rebooted it said return it to at&t because it was running unauthorised software. I was running 4.4.4 does anyone have any information of how I can fix it please?

SamBrears said:
I have what I thought was a n910f so a root was possible but when in download mode it shows up as a n910a which I didnt notice. I used kingroot which also showed my phone as a n910f and when my phone rebooted it said return it to at&t because it was running unauthorised software. I was running 4.4.4 does anyone have any information of how I can fix it please?
Click to expand...
Click to collapse
i'm in the same boat, used kingroot and then my phone started freaking out. turned it off and back on, got that "return to att" message.
I'm currently using Samsung Kies to return it to stock

masterhaides said:
i'm in the same boat, used kingroot and then my phone started freaking out. turned it off and back on, got that "return to att" message.
I'm currently using Samsung Kies to return it to stock
Click to expand...
Click to collapse
Ok, so the samsung kies did not fix my Note 4 (SM-N910A).
I did find this:
http://androidromupdate.com/att-galaxy-note-4-sm-n910a-stock-firmware
downloaded the 5.1.1 package which contains, not just the AP file, but the BL, CP, and the CSC... ALL 4 Must be flashed with Odin 3.09, at the same time.
My phone is now working again.

Did anyone fix their phone yet?

masterhaides said:
Ok, so the samsung kies did not fix my Note 4 (SM-N910A).
I did find this:
http://androidromupdate.com/att-galaxy-note-4-sm-n910a-stock-firmware
downloaded the 5.1.1 package which contains, not just the AP file, but the BL, CP, and the CSC... ALL 4 Must be flashed with Odin 3.09.
My phone is not working again.
Click to expand...
Click to collapse
Read this whole thread. http://forum.xda-developers.com/showthread.php?t=3335880
Sent from my SM-N910T using Tapatalk

Jumped in the Same Boat
Hi, I'm in the soft-brick syndrome.
This is my first go at rooting my phone (SM-N910A) - at least i was smart enough to try it after i upgraded
anyhoo, i researched and read. i installed my usb drivers, odin, and downloaded the suggested firmware. i couldn't talk between my computer and phone; so, i tried kingroot - big mistake. it failed in the middle and now i'm getting a startup error that says secure fail: kernel, then the blah, blah, blah go to AT&T store blah blah blah.... error.
i finally was able to reinstall the usb drivers and believe that odin can talk to my phone, but i receive a fail message when i try to install the firmware.
what to do? please help.

regarding your galaxy note4
SamBrears said:
I have what I thought was a n910f so a root was possible but when in download mode it shows up as a n910a which I didnt notice. I used kingroot which also showed my phone as a n910f and when my phone rebooted it said return it to at&t because it was running unauthorised software. I was running 4.4.4 does anyone have any information of how I can fix it please?
Click to expand...
Click to collapse
hello there just wondering if you ever found a solution to fixing your phone you see i did the same thing you did only i did it to my wifes phone shes pissed. i actualy did it to the n910a thought it was n910fand i got the same message saying go to at&t it shows a triangle and wont let me do anything i also used kingroot, so did we brick them or what do you think it is? please respond. [email protected]:crying:
---------- Post added at 09:54 AM ---------- Previous post was at 09:44 AM ----------
FredtheWhale said:
Hi, I'm in the soft-brick syndrome.
This is my first go at rooting my phone (SM-N910A) - at least i was smart enough to try it after i upgraded
anyhoo, i researched and read. i installed my usb drivers, odin, and downloaded the suggested firmware. i couldn't talk between my computer and phone; so, i tried kingroot - big mistake. it failed in the middle and now i'm getting a startup error that says secure fail: kernel, then the blah, blah, blah go to AT&T store blah blah blah.... error.
i finally was able to reinstall the usb drivers and believe that odin can talk to my phone, but i receive a fail message when i try to install the firmware.
what to do? please help.
Click to expand...
Click to collapse
hey pal im in the sameboat ,and like you i also made the fatal mistake of using kingroot. only cause i used it on SM-E700M and worked fine so i tried it on the note 4 and now i have no clue what to do next should i try to re root it again or maybe try to install the lolipop system it came with or do i try to upgrade or maybe try and install original firmware i can really use your advice what do you think?

no progress yet. i tried loading 5.1.1 and the original version (4.4.x ... whatever it was). both failed. i think that i might be approaching the issue incorrectly.
i think that i might have rooted the phone but tripped knox - when i startup i see in icon of a padlock that's open and it says custom underneath. but i get the error stating about non-standard software installed. i'm going to continue to research and see if i can figure out how to reset / remove knox.
i saw that there was someone who went back to ATT to have them reset the phone ... does anyone know whether they'll do it? at least i could have the phone at a "ready" state to try again ... after more research and prep. ;- )

not real progress, but...
i researched some more and feel as if i made some progress with odin3v1.85.
i followed directions from this article: How to Unroot / Unbrick Balaxy Note 4 (i found on the androidrootz site - sorry, i'm not allowed to post a url yet)
so, i'm still bricked, but this process was able to communicate with my phone and reported that flashing the firmware was successful.
incremental progress ... maybe ...

my solution
while i would have preferred to be able to figure it out, i couldn't.
i took the phone to AT&T today and they re-imaged it. all is clear and it's back to factory settings - no cost.

Typo fixed
Drew2873 said:
Did anyone fix their phone yet?
Click to expand...
Click to collapse
My second post has the fix for it. I don't know why it typo'd and said "not working" i meant to say "now working"
mine is working

did the same thing, bricked my sm-n910a gave the att message to bring it to them, all fixed via odin 3.0.9 download the stock firmware AP and BL check off in the little box bootloader update and clear EFS and it should work mines like new and didn't miss a beat, kingroot did root my phone 100% but bricked it to. whats the way around at&t locking the device up.

fastjohnson said:
did the same thing, bricked my sm-n910a gave the att message to bring it to them, all fixed via odin 3.0.9 download the stock firmware AP and BL check off in the little box bootloader update and clear EFS and it should work mines like new and didn't miss a beat, kingroot did root my phone 100% but bricked it to. whats the way around at&t locking the device up.
Click to expand...
Click to collapse
I took mine into the store. They reimaged it for free. No issue.

Where I live it's like 60 miles to a corp store. She's working mint now I'd like to bring the OS back to 4.4.4 and try it again.
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app

fastjohnson said:
Where I live it's like 60 miles to a corp store. She's working mint now I'd like to bring the OS back to 4.4.4 and try it again.
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
Click to expand...
Click to collapse
Unfortunatly, once you are on 5.1.1 there is no downgrading back to 4.4.4. Many have tried, non have suceeded. Am I saying it is impossible, I do not believe anything is impossible, but right now we do not have the right tools. Take care.

Yah. I tried had to reinstall the 5.1.1 firmware again. 17step procedure is a lil more than im capable of. Think the note 4 is getting sold. Moto x pure or another nexus. Thanks you guys on here it's where I got the firmware.
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app

THis really works!
fastjohnson said:
did the same thing, bricked my sm-n910a gave the att message to bring it to them, all fixed via odin 3.0.9 download the stock firmware AP and BL check off in the little box bootloader update and clear EFS and it should work mines like new and didn't miss a beat, kingroot did root my phone 100% but bricked it to. whats the way around at&t locking the device up.
Click to expand...
Click to collapse
Thank you for your input. After searching for literally a full day and trying several different things to no avail....yours was the one that unbricked my phone. Thank you....Thank you!

Yah I wouldn't try anymore to root, if theres a huge bounty and none of these smart cookies here on xda haven't got it yet. The 910a variant is unrootable perm root that is, the. Mobile version you can. Glad it helped and your up and running again.
Sent from my HTC6600LVW using XDA-Developers mobile app

Device State - locked

I know there are other threads regarding this but those included someone having TWRP already flashed and in this case I do not.
I sadly took a chance and bought a Nexus 5X off someone on Kijiji and it looks like I got got scammed.
I've own other Nexus phones in the past but was unaware of the OEM Lock on the latest devices and it is in a locked state and I do not know the google account to unlock it (as it wasn't my phone prior to this)
None of the fastboot/adb commands work as it is locked.
I just wanted to know if there was any other way I could fix this or if I have brick on my hands here. Any assistance would be amazing as this would mean I just blew my money away.
N

sniperIT said:
I know there are other threads regarding this but those included someone having TWRP already flashed and in this case I do not.
I sadly took a chance and bought a Nexus 5X off someone on Kijiji and it looks like I got got scammed.
I've own other Nexus phones in the past but was unaware of the OEM Lock on the latest devices and it is in a locked state and I do not know the google account to unlock it (as it wasn't my phone prior to this)
None of the fastboot/adb commands work as it is locked.
I just wanted to know if there was any other way I could fix this or if I have brick on my hands here. Any assistance would be amazing as this would mean I just blew my money away.
N
Click to expand...
Click to collapse
So you purchased a 5X that wasn't factory reset? Have you tried asking the previous owner for assistance? They might be able to remotely wipe the phone using Android Device Manager.

metpage said:
So you purchased a 5X that wasn't factory reset? Have you tried asking the previous owner for assistance? They might be able to remotely wipe the phone using Android Device Manager.
Click to expand...
Click to collapse
It was reset and required login of the previous account to unlock it. Unfortunately, the previous owner is nowhere to be found...
The build number is MHC19J and I've been told that I am screwed to unlock it.
Nick

sniperIT said:
It was reset and required login of the previous account to unlock it. Unfortunately, the previous owner is nowhere to be found...
The build number is MHC19J and I've been told that I am screwed to unlock it.
Nick
Click to expand...
Click to collapse
I would try and get your money back, chances are you could have brought a stolen phone.

Darke5tShad0w said:
I would try and get your money back, chances are you could have brought a stolen phone.
Click to expand...
Click to collapse
Sadly you may be right, but like any good thief he seems to be unreachable, so I unfortunately can't get the money back. I have checked the IMEI and it is clean so i should be able to activate it.
I just need a way to bypass the FRP (Factory Reset Protection). I've seen posts on this on XDA but they are for patches up to the March 1st Patch. I build I have is the March Patch and I can't seem to find any workarounds for this patch level.
In the event that someone has found a way please let me know as it would save me a lot of grief.
Thank you for your responses.
N

sniperIT said:
Sadly you may be right, but like any good thief he seems to be unreachable, so I unfortunately can't get the money back. I have checked the IMEI and it is clean so i should be able to activate it.
I just need a way to bypass the FRP (Factory Reset Protection). I've seen posts on this on XDA but they are for patches up to the March 1st Patch. I build I have is the March Patch and I can't seem to find any workarounds for this patch level.
In the event that someone has found a way please let me know as it would save me a lot of grief.
Thank you for your responses.
N
Click to expand...
Click to collapse
I don't know if will help, but the N preview may not include or may reset FRP. Usually OTAs only include the changed files but since the N preview was bricking locked phones, Google released full OTAs that contained everything. You could try flashing it with ADB while in the stock recovery.
Sent from my Nexus 5X using Tapatalk

PiousInquisitor said:
I don't know if will help, but the N preview may not include or may reset FRP. Usually OTAs only include the changed files but since the N preview was bricking locked phones, Google released full OTAs that contained everything. You could try flashing it with ADB while in the stock recovery.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I was thinking the same thing but I don't want to make the situation worse than it already is. I have seen vids from RootJunky showing that the N preview is bypassable and it can be done with a reset.
Will the OTA wipe all the data on the device?
Just to be clear are these the OTA's you are referring too? http://developer.android.com/preview/download-ota.html
Thank you for your advice.
N

sniperIT said:
I was thinking the same thing but I don't want to make the situation worse than it already is. I have seen vids from RootJunky showing that the N preview is bypassable and it can be done with a reset.
Will the OTA wipe all the data on the device?
Just to be clear are these the OTA's you are referring too? http://developer.android.com/preview/download-ota.html
Thank you for your advice.
N
Click to expand...
Click to collapse
Those are the files. That is what I would do.
Sent from my Nexus 5X using Tapatalk

PiousInquisitor said:
Those are the files. That is what I would do.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Ok thank you very much I am in the process, will update once it is complete.
N

sniperIT said:
Ok thank you very much I am in the process, will update once it is complete.
N
Click to expand...
Click to collapse
Looks like it is still a no go. The FRP seems to still be in place and the reset idea didn't work.
I may need to see if i can get this phone completely blanked.
N

sniperIT said:
Looks like it is still a no go. The FRP seems to still be in place and the reset idea didn't work.
I may need to see if i can get this phone completely blanked.
N
Click to expand...
Click to collapse
I've got on last idea. Is it a 32 gig model?
Sent from my Nexus 5X using Tapatalk

PiousInquisitor said:
I've got on last idea. Is it a 32 gig model?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
16GB unfortunately.

sniperIT said:
16GB unfortunately.
Click to expand...
Click to collapse
Bummer. I was going to suggest THIS. But there isnt a 16 TOT file.
So you were able to successfully flash N from the stock recovery? And you simply couldnt get past the login screen? FRP is a *****. I had no idea what it was when I sold my Moto X Pure Edition last year. I ended up giving the guy I sold it to my password so he could unlock it. That was after about a day of searching for a workaround. Then my sis bought a G4 and when it arrived it was locked with FRP. We ended up finding a tool to wipe it out. Such a pain. Lol. Good luck finding a solution. Let us know if you get it working some other way.
---------- Post added at 10:41 PM ---------- Previous post was at 10:30 PM ----------
sniperIT said:
16GB unfortunately.
Click to expand...
Click to collapse
Have you tried this? EDIT: Looks like its been patched already...
https://www.youtube.com/watch?v=ocC7ruFCqOI

PiousInquisitor said:
Bummer. I was going to suggest THIS. But there isnt a 16 TOT file.
So you were able to successfully flash N from the stock recovery? And you simply couldnt get past the login screen? FRP is a *****. I had no idea what it was when I sold my Moto X Pure Edition last year. I ended up giving the guy I sold it to my password so he could unlock it. That was after about a day of searching for a workaround. Then my sis bought a G4 and when it arrived it was locked with FRP. We ended up finding a tool to wipe it out. Such a pain. Lol. Good luck finding a solution. Let us know if you get it working some other way.
---------- Post added at 10:41 PM ---------- Previous post was at 10:30 PM ----------
Have you tried this? EDIT: Looks like its been patched already...
https://www.youtube.com/watch?v=ocC7ruFCqOI
Click to expand...
Click to collapse
Man is it ever. The last thing I was thinking was that they say there is a 72 hour lock on this and I only first started the phone on Sat night. maybe I need to wait until tomorrow and see what happens.
I will check out the Youtube video.
Thank you for all your help once again.
N

sniperIT said:
Man is it ever. The last thing I was thinking was that they say there is a 72 hour lock on this and I only first started the phone on Sat night. maybe I need to wait until tomorrow and see what happens.
I will check out the Youtube video.
Thank you for all your help once again.
N
Click to expand...
Click to collapse
So were you able to reset the phone on N, like in the rootjunky video?
https://www.youtube.com/watch?v=nOymYg3lswI

PiousInquisitor said:
So were you able to reset the phone on N, like in the rootjunky video?
https://www.youtube.com/watch?v=nOymYg3lswI
Click to expand...
Click to collapse
I unfortunately don't have a sim to test with. The one in my current is a micro not a nano. I am going to contact a repair store tomorrow to see if they can assist and I will try it out.
Sorry yes I did exactly as he suggested and it didn't work.
It gives me the option during setup to setup like it was a new phone but then as soon as I connect to my WiFi it performs a check and states the same reset message.
Which is why I might be thinking that it is the 72 hour lock on and maybe it will go away once it is complete.
N

sniperIT said:
I unfortunately don't have a sim to test with. The one in my current is a micro not a nano. I am going to contact a repair store tomorrow to see if they can assist and I will try it out.
Sorry yes I did exactly as he suggested and it didn't work.
It gives me the option during setup to setup like it was a new phone but then as soon as I connect to my WiFi it performs a check and states the same reset message.
Which is why I might be thinking that it is the 72 hour lock on and maybe it will go away once it is complete.
N
Click to expand...
Click to collapse
I would try it again. If you factory reset from within android, it should disable FRP, including the need to wait 72 hrs.
I wouldn't bother with the repair shop. The latest and greatest info is going to be on the internet and probably from rootjunky.

PiousInquisitor said:
I would try it again. If you factory reset from within android, it should disable FRP, including the need to wait 72 hrs.
I wouldn't bother with the repair shop. The latest and greatest info is going to be on the internet and probably from rootjunky.
Click to expand...
Click to collapse
I tried several times with no luck.
It just seems like once it phones home to Google it blocks me.
I'm going to try to contact rootjunky directly

sniperIT said:
I tried several times with no luck.
It just seems like once it phones home to Google it blocks me.
I'm going to try to contact rootjunky directly
Click to expand...
Click to collapse
Bummer. Im out of ideas.

What message do you exactly get when trying to execute something via fastboot?