Database Develop

[Q] Can't send/receive calls or texts after screwing with PRL

Running Beanstalk.
Have been having intermittent issues with mobile data, so I'm sadly familiar with toggling Airplane mode, changing the CMDA subscription, rebooting, etc. in order to jog mobile data into working again. Lately have been having a weird, sporadic problem with people I call only hearing static on my end, so I chatted with Sprint, got to the point where they suggest typing the code to reset/update PRLs into the dialer, and bailed.
Then, in my infinite wisdom decided to try flashing a Sense ROM, proceeding with the manual PRL update/reset, and then wiping and restoring my Beanstalk nandroid.
Now I can't make or receive calls or texts at all, no matter what I do. Have tried all the old toggles. Have tried a complete reflash of Beanstalk. I'm beginning to worry I seriously borked something up.
Is anyone familiar with this kind of situation? Did I screw up, and if so, how bad? Any solutions anyone can think of? I'd be most grateful for any and all help. Thanks guys.

Reinstalling ROM from scratch and if that doesn't work then running ARU.

EPayne123 said:
Reinstalling ROM from scratch and if that doesn't work then running ARU.
Click to expand...
Click to collapse
What's ARU? I did try reinstalling the ROM from scratch and it didn't fix it.

thedodus said:
What's ARU? I did try reinstalling the ROM from scratch and it didn't fix it.
Click to expand...
Click to collapse
Okay here is what you can do, there is an app floating around these forums that can allow you to manually write the prl, find that, and then use a stock prl for sprint. I believe this post will help:
http://forum.xda-developers.com/showthread.php?t=2296167
Let me know if that helps.
Oh and also yeah flashing a different rom wouldnt help because they do not contain any of that information, in fact i think all the carrier information is stored in a different partition for this exact reason -so they cant be easily overwritten.

I build the Beanstalk here and haven't come across that issue yet. Do you have a backup of your original stock ROM? You need to get back to straight stock, like out of the box stock. From there, you can update your prls or anything else OTA-style, check your functionality, then redownload the Beanstalk ROM from here, do a full wipe(no internal data), install the fresh DL, Gapps, fix permissions(PhilzTouch 6.0.3.3 only), and reboot. Should be good to go and should only need to toggle airplane for reboots and occasionally for the wifi. Let me know how it goes, either here, on the BS thread or by PM. Good luck....
If you have no original back up(after getting back to straight stock, MAKE ONE), then use Bigdaddy619s threads on getting back to stock. After that, then follow the steps above.
You should always make an original back up of stock directly after rooting and unlocking. ALWAYS

BMP7777 said:
I build the Beanstalk here and haven't come across that issue yet. Do you have a backup of your original stock ROM? You need to get back to straight stock, like out of the box stock. From there, you can update your prls or anything else OTA-style, check your functionality, then redownload the Beanstalk ROM from here, do a full wipe(no internal data), install the fresh DL, Gapps, fix permissions(PhilzTouch 6.0.3.3 only), and reboot. Should be good to go and should only need to toggle airplane for reboots and occasionally for the wifi. Let me know how it goes, either here, on the BS thread or by PM. Good luck....
If you have no original back up(after getting back to straight stock, MAKE ONE), then use Bigdaddy619s threads on getting back to stock. After that, then follow the steps above.
You should always make an original back up of stock directly after rooting and unlocking. ALWAYS
Click to expand...
Click to collapse
Thanks, both of you.
BMP - Beanstalk rules - it's definitely my fault. If I have a back-up made just after getting S-OFF, would that work?
matinm90 - thanks for the info...that explains exactly what the problem I'm having is.
I'll try these solutions out and post back. Thanks again guys.

Yes, it should as long as everything worked then. Driving right now. Try it and let me know. When I get home I'll help however I can.
Sent from my One using XDA Premium 4 mobile app

thedodus said:
Thanks, both of you.
BMP - Beanstalk rules - it's definitely my fault. If I have a back-up made just after getting S-OFF, would that work?
matinm90 - thanks for the info...that explains exactly what the problem I'm having is.
I'll try these solutions out and post back. Thanks again guys.
Click to expand...
Click to collapse
Your welcome and yeah it should defintely work, just make sure you use the right prl

Worked!
I think what I'd originally goofed was not immediately rebooting after the prl update, since the Sprint lady didn't mention that step (or maybe I didn't hear her). This time I immediately rebooted and data came back, and then I was able to flash BeanStalk and stay functional.
Many thanks to both of you!

thedodus said:
Worked!
I think what I'd originally goofed was not immediately rebooting after the prl update, since the Sprint lady didn't mention that step (or maybe I didn't hear her). This time I immediately rebooted and data came back, and then I was able to flash BeanStalk and stay functional.
Many thanks to both of you!
Click to expand...
Click to collapse
More than welcome. Glad you're up and running.:highfive:

thedodus said:
Worked!
I think what I'd originally goofed was not immediately rebooting after the prl update, since the Sprint lady didn't mention that step (or maybe I didn't hear her). This time I immediately rebooted and data came back, and then I was able to flash BeanStalk and stay functional.
Many thanks to both of you!
Click to expand...
Click to collapse
Your welcome glad you got everything straightened out
Sent from my HTCONE using Tapatalk

[Q] Need Help! Tried rooting my Note 3 for the first time and now very inoperable

To start this off im going to say that i am very new to Android devices, ive owned my Note 3 (The AT&T SM-N900A one) for nearly three weeks now spending time researching on rooting and the methods, etc. Well i just tried to and didnt quite have much success.
I followed this guide and its steps very thoroughly. http://forum.xda-developers.com/showthread.php?t=2559715
Yet it all ended with it booting up looking like new but nearly every 3 seconds errors appear about processes crashing and trying to stop, for example "Unfortunately, Direct pen input has stopped."
After that failure i went ahead and tried to undo it which probably wasnt a good idea, i followed this tutorial: http://www.droidviews.com/how-to-unbrick-att-galaxy-note-3-sm-n900a/.
I ended up at the exact same place, same error over and over. Does anyone know how to fix this?
Thank you.
(I apologize if this had been brought up before i went searching but found nothing that was a solution to my problem.)

baileynapier said:
To start this off im going to say that i am very new to Android devices, ive owned my Note 3 (The AT&T SM-N900A one) for nearly three weeks now spending time researching on rooting and the methods, etc. Well i just tried to and didnt quite have much success.
I followed this guide and its steps very thoroughly. http://forum.xda-developers.com/showthread.php?t=2559715
Yet it all ended with it booting up looking like new but nearly every 3 seconds errors appear about processes crashing and trying to stop, for example "Unfortunately, Direct pen input has stopped."
After that failure i went ahead and tried to undo it which probably wasnt a good idea, i followed this tutorial: http://www.droidviews.com/how-to-unbrick-att-galaxy-note-3-sm-n900a/.
I ended up at the exact same place, same error over and over. Does anyone know how to fix this?
Thank you.
(I apologize if this had been brought up before i went searching but found nothing that was a solution to my problem.)
Click to expand...
Click to collapse
Have you performed a factory data reset since the last attempt?

440bro said:
Have you performed a factory data reset since the last attempt?
Click to expand...
Click to collapse
Yes i have,a few times, it just then reboots with the setup and that error still occurring.

baileynapier said:
Yes i have,a few times, it just then reboots with the setup and that error still occurring.
Click to expand...
Click to collapse
That error is a bugger to get rid of, if you even can. i had this happen and had to return my device to the store. BUT that was before we had a working back to stock MJ5 solution.
http://forum.xda-developers.com/showthread.php?t=2559715
If you were on MJ5 this will get you back to out of the box stock with or without Root, its up to you.
i have used this twice and has worked smoothly both times, just make sure you download the files needed and follow the steps.

the2rrell said:
That error is a bugger to get rid of, if you even can. i had this happen and had to return my device to the store. BUT that was before we had a working back to stock MJ5 solution.
http://forum.xda-developers.com/showthread.php?t=2559715
If you were on MJ5 this will get you back to out of the box stock with or without Root, its up to you.
i have used this twice and has worked smoothly both times, just make sure you download the files needed and follow the steps.
Click to expand...
Click to collapse
That is the method OP used to get root....
OP, you should have used Kingo... Now you will have to redo that whole process just to restore back to stock. You had a bad flash or a bad download.
Sent from my SM-N9005A using XDA Premium 4 mobile app

28248965 286a
the2rrell said:
That error is a bugger to get rid of, if you even can. i had this happen and had to return my device to the store. BUT that was before we had a working back to stock MJ5 solution.
http://forum.xda-developers.com/showthread.php?t=2559715
If you were on MJ5 this will get you back to out of the box stock with or without Root, its up to you.
i have used this twice and has worked smoothly both times, just make sure you download the files needed and follow the steps.
Click to expand...
Click to collapse
That was the method that originally got me into this situation and i just tried it again step by step and i am still having the issue.
One thing that has caught my eye is that this was my devices information before ever trying any rooting process or anything:
MODEL NUMBER: SAMSUNG-SN-N900A
ANDROID VERSION: 4.3 (Jelly Bean)
BASEBAND VERSION: N900AUCUBNB4
KERNEL INFO -
3.4.0-1625098
se.i[email protected] #1
Mon Feb 10 21:13:28 KST 2014
BUILD NUMBER: JSS15J.N900AUCUBNB4
SELINUX STATUS: Enforcing
Is there any possible way to get it back to being a BNB4 device like the information above?

graydiggy said:
That is the method OP used to get root....
OP, you should have used Kingo... Now you will have to redo that whole process just to restore back to stock. You had a bad flash or a bad download.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
tis the reason i directed him back to that thread. i know they are working on a easier odin flash to return to stock in another thread. dont know why he was using that to get root, but he will now need to use it to get booting back to normal again.
anyway, apologies for not being more clear.
so to sum it all up, redownload the files in case you got a bad one and repeat the process my good sir.

the2rrell said:
tis the reason i directed him back to that thread. i know they are working on a easier odin flash to return to stock in another thread. dont know why he was using that to get root, but he will now need to use it to get booting back to normal again.
anyway, apologies for not being more clear.
so to sum it all up, redownload the files in case you got a bad one and repeat the process my good sir.
Click to expand...
Click to collapse
Okay, thank you guys very much but its back to functioning properly! :victory:
Now am i just trying to accomplish a root, but that doesnt seem to be working, after i put the root de la vega files onto the sdcard SuperSU never installs upon restart, why is it not auto-installing like it seems to be expressed as in the tutorial?
EDIT: Okay guys, nevermind about the root, i just used Kingo.

baileynapier said:
Okay, thank you guys very much but its back to functioning properly! :victory:
Now am i just trying to accomplish a root, but that doesnt seem to be working, after i put the root de la vega files onto the sdcard SuperSU never installs upon restart, why is it not auto-installing like it seems to be expressed as in the tutorial?
Click to expand...
Click to collapse
use kingo 1.1.8 it is a lot easier

baileynapier said:
ive owned my Note 3 (The AT&T SM-N900A one) for nearly three weeks now spending time researching on rooting and the methods, etc.
Click to expand...
Click to collapse
How did you NOT find Kingo right away?
What kind of research did you do for 3 weeks? lol
Well, I'm glad you're good to go now. The devs on this site are exceptional and you are lucky to have them. (me too).

baileynapier said:
Okay, thank you guys very much but its back to functioning properly! :victory:
Now am i just trying to accomplish a root, but that doesnt seem to be working, after i put the root de la vega files onto the sdcard SuperSU never installs upon restart, why is it not auto-installing like it seems to be expressed as in the tutorial?
EDIT: Okay guys, nevermind about the root, i just used Kingo.
Click to expand...
Click to collapse
So how did you get it back functioning properly? I am at the same point. I bricked my N3 screwing around with getting Face Unlock to work. So I followed the steps of Restore for MJ5 post, and immediately upon the final boot into setup, the Direct Pen Input error started, and makes the device useless. What fixed yours?

Re-download all the files and retry. Also, verify the size. I think you may have a corrupt file somewhere.

And factory reset after installing a ROM, even if it's the same ROM you had. Any ROM, on any phone, not just this one. Different ROMs store data in different locations, and if a ROM picks up the data from a previous ROM, that may bot be the data it wants, so it causes things to crash.

Ok thanks for the replies. I actually tried a factory reset after seeing the error, but it didn't help at all. And I did run a checksum on the only file that displayed a number, when I originally downloaded the files. But as would be expected, after all simple efforts to fix the issue failed, I started fresh on a whole different PC, downloaded all of the files again, used a different USB cable, and installed everything all over again. And low and behold, the second time was a total success. I can't explain what made the difference, and the checksum result showed an accurate download both times. But this is the nature of the beast isn't it?
Thanks,

Successful Unroot Options

I am returning my phone back to stock so I can trade it in. I found a few threads on here that have ways to unroot but some seem questionable. Can anyone point me in the right direction to unroot an official Kit Kat updated device?
Thanks

Assuming you have supersu, uninstall all of your apps that have root access (for safestrap, busybox, etc make sure to uninstall the in-app stuff first), i would reboot here but that may not be necessary...then open up supersu and choose "full unroot". Then factory reset and double check status is official ☺
If you get a custom screen after that try rerooting then full unroot with supersu again
Edit: I stand corrected - flashing NC2 with Odin is easiest

Yeah I have su. So before I do this should I restore my stock rom I have backed up via safestrap? I am currently running dynamic kat 5.0

You can also reinstall factory firmware with Odin, then factory reset.
http://forum.xda-developers.com/showthread.php?t=2703006

Awesome, I will give that a try when my upgrade is closer. Thank you

440bro said:
You can also reinstall factory firmware with Odin, then factory reset.
http://forum.xda-developers.com/showthread.php?t=2703006
Click to expand...
Click to collapse
konaman said:
Awesome, I will give that a try when my upgrade is closer. Thank you
Click to expand...
Click to collapse
Yea @440bro 's suggestion is way easier since Odin removes all of that! unroot with SuperSU does work but it's a long way around for just returning to stock

please help
440bro said:
You can also reinstall factory firmware with Odin, then factory reset.
http://forum.xda-developers.com/showthread.php?t=2703006[/QUOTE
]I have similar situation except I have an iMac running OS X Mavericks. Could anyone tell me if it's possible to unroot my AT&T Note 3 to stock ROM to sell? I installed stock custom rom using safestrap but when I reboot or turn device on, I get a safestrap enabled cartoon thing asking to continue or recover. I don't think people will want to buy phone if they saw this sick looking robot thing when they switch it on. Please help...Phone too big for my hands. Thank you
Click to expand...
Click to collapse

braddy66 said:
440bro said:
You can also reinstall factory firmware with Odin, then factory reset.
http://forum.xda-developers.com/showthread.php?t=2703006[/QUOTE
]I have similar situation except I have an iMac running OS X Mavericks. Could anyone tell me if it's possible to unroot my AT&T Note 3 to stock ROM to sell? I installed stock custom rom using safestrap but when I reboot or turn device on, I get a safestrap enabled cartoon thing asking to continue or recover. I don't think people will want to buy phone if they saw this sick looking robot thing when they switch it on. Please help...Phone too big for my hands. Thank you
Click to expand...
Click to collapse
Did you backup stock rom before you flashed the custom rom in safestrap? if yes, reflash your backup in safestrap then the steps in post #2 should work. If no, I'm really not sure how going through that unroot process with SuperSU while still on a custom rom would work out...Odin is much easier and more reliable so if there's any way you can get to a PC you might want to go that route.
Also if you're selling online you might find some people who do want to buy a rooted Note 3...I sold a phone on swappa a few months ago and there were people looking specifically for rooted phones. The 'cartoon thing' is safestrap and is exactly what you want to see when you turn on a rooted AT&T Note 3
Click to expand...
Click to collapse

thank you
braddy66 said:
440bro said:
You can also reinstall factory firmware with Odin, then factory reset.
http://forum.xda-developers.com/showthread.php?t=2703006[/QUOTE
]I have similar situation except I have an iMac running OS X Mavericks. Could anyone tell me if it's possible to unroot my AT&T Note 3 to stock ROM to sell? I installed stock custom rom using safestrap but when I reboot or turn device on, I get a safestrap enabled cartoon thing asking to continue or recover. I don't think people will want to buy phone if they saw this sick looking robot thing when they switch it on. Please help...Phone too big for my hands. Thank you
Click to expand...
Click to collapse
brisinger08 said:
braddy66 said:
Did you backup stock rom before you flashed the custom rom in safestrap? if yes, reflash your backup in safestrap then the steps in post #2 should work. If no, I'm really not sure how going through that unroot process with SuperSU while still on a custom rom would work out...Odin is much easier and more reliable so if there's any way you can get to a PC you might want to go that route.
Also if you're selling online you might find some people who do want to buy a rooted Note 3...I sold a phone on swappa a few months ago and there were people looking specifically for rooted phones. The 'cartoon thing' is safestrap and is exactly what you want to see when you turn on a rooted AT&T Note 3
Click to expand...
Click to collapse
Thanks for your feel good message...made my day. I thought I backed up stock rom however being an obviously root virgin...When I went to factory reset, everything was gone except for my ugly cartoony friend. Luckily I am able to read in small doses so I was able to do whatever it was I did to get her running factory...still rooted and unlocked. When you mentioned that people on swappa might be interested in a rooted device WITH my lonely friend at startup? I felt all fuzzy. I will post an ad on swappa later today in your honor my mysterious phoneguardian angel. Thanks again.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Looks like I'll need to go the long route to unroot. I have a Mac book and I can't find Odin for it

Accidentally flashed a file to root that was for KitKat (Im on Lollipop)

So I accidentaly flashed the wrong root file thus making my systemui continuously crash. Any suggestions as to what I can do?

shahrukhraza said:
So I accidentaly flashed the wrong root file thus making my systemui continuously crash. Any suggestions as to what I can do?
Click to expand...
Click to collapse
Stock recovery or TWRP?
Are you looking to undo what you did without having to do a complete wipe, or are you open to more drastic solutions? Because you can always run the toolkit to reset to complete stock by flashing the stock images over your current system. But that would of course perform a complete wipe.

Paddington said:
Stock recovery or TWRP?
Are you looking to undo what you did without having to do a complete wipe, or are you open to more drastic solutions? Because you can always run the toolkit to reset to complete stock by flashing the stock images over your current system. But that would of course perform a complete wipe.
Click to expand...
Click to collapse
I dont really mind a complete wipe. And are you referring to this toolkit? http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3048099
if not could you please tell me which one?
And to clarify, I followed this tutorial: https://www.youtube.com/watch?v=_fPIYhzWlnw . The file that I flashed to attempt to root is in the description of that.

shahrukhraza said:
I dont really mind a complete wipe. And are you referring to this toolkit? http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3048099
if not could you please tell me which one?
And to clarify, I followed this tutorial: https://www.youtube.com/watch?v=_fPIYhzWlnw . The file that I flashed to attempt to root is in the description of that.
Click to expand...
Click to collapse
I actually used this one: http://forum.xda-developers.com/moto-x-2014/development/tool-moto-x-pure-edition-recovery-t2897819 when I was messed around, but I would imagine either would work. When I needed to return to unrooted stock, I believe that toolkit returned me to 4.4.4 unrooted stock, then I just ran the 5.0 OTA once the phone booted up.
The toolkit you referenced is the one I used to unlock the bootloader, flash TWRP, and root my phone. As long as you can get to recovery or fastboot, either toolkit should work to return you to stock. BUT I caution you, I have a pure edition, and these toolkits were made for the pure edition. If you do not have a pure edition, you'll want to read the disclaimers/instructions/other posts to make sure it will work on your phone.

Okay so this escalated quickly.
So here I am being my dumb self , I try to flash TWRP. That goes fine and then I try to wipe my data. After that I reboot it and as its turning on it foes black on the boot animation. and now I cant even get into freaking recovery mode. I dont know what I did but im pretty sure I messed up bad. I need some serious help now and anything is appreciated.

Paddington said:
I actually used this one: http://forum.xda-developers.com/moto-x-2014/development/tool-moto-x-pure-edition-recovery-t2897819 when I was messed around, but I would imagine either would work. When I needed to return to unrooted stock, I believe that toolkit returned me to 4.4.4 unrooted stock, then I just ran the 5.0 OTA once the phone booted up.
The toolkit you referenced is the one I used to unlock the bootloader, flash TWRP, and root my phone. As long as you can get to recovery or fastboot, either toolkit should work to return you to stock. BUT I caution you, I have a pure edition, and these toolkits were made for the pure edition. If you do not have a pure edition, you'll want to read the disclaimers/instructions/other posts to make sure it will work on your phone.
Click to expand...
Click to collapse
Yessir thanks for replying. However I now have a whole new problem. Do you have any suggestions for that? It is the post above^

shahrukhraza said:
Okay so this escalated quickly.
So here I am being my dumb self , I try to flash TWRP. That goes fine and then I try to wipe my data. After that I reboot it and as its turning on it foes black on the boot animation. and now I cant even get into freaking recovery mode. I dont know what I did but im pretty sure I messed up bad. I need some serious help now and anything is appreciated.
Click to expand...
Click to collapse
Hey thats an easy fix just load into the boatloader and reflash the rom through mfastboot
edit: you should be able to get all the files you need from his website http://forum.xda-developers.com/moto-x-2014/general/ota-pure-edition-lollipop-5-0-t2932625

ewalk4866 said:
Hey thats an easy fix just load into the boatloader and reflash the rom through mfastboot
edit: you should be able to get all the files you need from his website http://forum.xda-developers.com/moto-x-2014/general/ota-pure-edition-lollipop-5-0-t2932625
Click to expand...
Click to collapse
Bootloader as in vol. down + power button right? Thats not working too. I also tried other combinations to no luck. And before it was turning on but now its not even booting to the boot animation. Thanks for the link though, if it does magically boot into the bootloader then i'll know what to do at least.
Edit: Okay so theres the charging animation, so thats a start, I guess. Still no luck on the bootloader tho.

Okay got it into bootloader mode!
Now before I do any other stupid thing can somebody just confirm one thing for me? On Graffix's website, this is the img I should flash through mfastboot right
Lollipop 5.0 22.21.11 FULL IMAGE PACKAGE Zip
Just a confirmation because I dont really trust my judgement. Thanks again everybody

shahrukhraza said:
Okay got it into bootloader mode!
Now before I do any other stupid thing can somebody just confirm one thing for me? On Graffix's website, this is the img I should flash through mfastboot right
Lollipop 5.0 22.21.11 FULL IMAGE PACKAGE Zip
Just a confirmation because I dont really trust my judgement. Thanks again everybody
Click to expand...
Click to collapse
Yes that's right remember you only have to flash system

Sorry that my Toolkit suggestion messed you up. I really thought that solution would work, not make it worse.

Paddington said:
Sorry that my Toolkit suggestion messed you up. I really thought that solution would work, not make it worse.
Click to expand...
Click to collapse
Toolkit are never really a good idea it just makes people lazy and not learn how to flash or fix problems on there own.

Paddington said:
Sorry that my Toolkit suggestion messed you up. I really thought that solution would work, not make it worse.
Click to expand...
Click to collapse
Nah man that didnt mess it up, some other stupid thing did it lol. Nothing on you, rather thanks for the help.

ewalk4866 said:
Toolkit are never really a good idea it just makes people lazy and not learn how to flash or fix problems on there own.
Click to expand...
Click to collapse
I agree that Toolkits can make you lazy and not learn how to fix things on your own, but when you need a quick fix and don't have time to figure out what is going wrong, it's always nice to just boot your phone into fastboot or recovery and fix things with a few keystrokes on your computer.

I got it to work guys! Thanks for all the help. It was much appreciated.

Does anyone here have the firmware for the E5 Play XT1921-3 T-Mobile variant?

To put a long story short, messed up my phone by incorrectly rooting, and wish to load up stock firmware so I can hopefully use my phone again. Anyone possibly root their devices and have a firmware backup? If anyone has the firmware for the XT1921-3 T-Mobile variant please come forward.

j256 said:
To put a long story short, messed up my phone by incorrectly rooting, and wish to load up stock firmware so I can hopefully use my phone again. Anyone possibly root their devices and have a firmware backup? If anyone has the firmware for the XT1921-3 T-Mobile variant please come forward.
Click to expand...
Click to collapse
I just want to one-up this. I'm in need of an XT1921-3 boot partition image to fix an issue with my phone.

I tracked this down,thank Rootjunky! HE was doing a vid on recovering motorola devices,and linked to this user and i skipped you to the tmo firmware https://androidfilehost.com/?fid=5862345805528062419
Hopefully it's the right one,i'm used to Samsung naming

timjames474 said:
I tracked this down,thank Rootjunky! HE was doing a vid on recovering motorola devices,and linked to this user and i skipped you to the tmo firmware https://androidfilehost.com/?fid=5862345805528062419
Hopefully it's the right one,i'm used to Samsung naming
Click to expand...
Click to collapse
Thank you! I'll check it out. I also have a couple boot and system twrp backups that a couple of people have donated. I'll be going through them this weekend and will probably post them in a separate tmo thread

weakNPCdotCom said:
Thank you! I'll check it out. I also have a couple boot and system twrp backups that a couple of people have donated. I'll be going through them this weekend and will probably post them in a separate tmo thread
Click to expand...
Click to collapse
Glad i could (try) to point you in the right direction!

timjames474 said:
I tracked this down,thank Rootjunky! HE was doing a vid on recovering motorola devices,and linked to this user and i skipped you to the tmo firmware https://androidfilehost.com/?fid=5862345805528062419
Hopefully it's the right one,i'm used to Samsung naming
Click to expand...
Click to collapse
I have to thank you again. After getting my stock restored I was able to confirm the build number on this. It looks like a newer revision but its the same minor build number. I'll be testing it today. THANK YOU

weakNPCdotCom said:
I have to thank you again. After getting my stock restored I was able to confirm the build number on this. It looks like a newer revision but its the same minor build number. I'll be testing it today. THANK YOU
Click to expand...
Click to collapse
So,how'd testing go for you? Just popped by to check in. Hope your phone is still going well!

timjames474 said:
So,how'd testing go for you? Just popped by to check in. Hope your phone is still going well!
Click to expand...
Click to collapse
Perfect. Got the phone back to factory with everything working

weakNPCdotCom said:
Perfect. Got the phone back to factory with everything working
Click to expand...
Click to collapse
Hey there, I'm in this boat now and I was hoping you could tell me how you used the stock firmware to restore the phone? I'm pretty new to this and I was trying to root it and now I'm stuck in a boot loop.

chronometrist said:
Hey there, I'm in this boat now and I was hoping you could tell me how you used the stock firmware to restore the phone? I'm pretty new to this and I was trying to root it and now I'm stuck in a boot loop.
Click to expand...
Click to collapse
If you already have the 1921-3 zip, just follow the instructions in the restoration thread