Hey, what's up. So, here's the problem.
1. I flashed Void, I didn't like.
2. I flashed the stock rom (froyo 2.2).
3. now airplane mode in "settings > wireless and network settings" won't turn off.
I've tried taking the battery out for 10 seconds and putting it back again to no avail.
Help please!!!! Now I can't make any calls or anything cuz I've got no connection anywhere!!
Reflash the stock ROM
Sent from my LG-P500 using XDA Premium App running miks CM7, quadrant 2100, over clocked at 787
wipe all. try to flash devoid its 2.2 but a lot better.
How did you flash stock ROM? By creating a KDZip(stockrom.zip) and then flashing it? Anyway try to wipe dalvik-cache via Recovery.
1. I've flashed the stock twice
2. I don't wanna go for another ROM at this stage. Getting an error when restoring, and not being able to restore, a nandroid backup is what landed me in this mess, and I'm not sure what other misleading information about Romming I've been fed.
3. Nah, I flashed the stock .DZ.
4. Would my service provider be able to format and reinstall android, or will I be looking at getting a new phone?? Cuz that would suck.
antiother said:
1. I've flashed the stock twice
2. I don't wanna go for another ROM at this stage. Getting an error when restoring, and not being able to restore, a nandroid backup is what landed me in this mess, and I'm not sure what other misleading information about Romming I've been fed.
3. Nah, I flashed the stock .DZ.
4. Would my service provider be able to format and reinstall android, or will I be looking at getting a new phone?? Cuz that would suck.
Click to expand...
Click to collapse
Well, if you keep restoring messed-up/corrupt/broken settings etc., no wonder flashing does not help. Wipe everything and flash a stock ROM, do not restore any broken mess. That is what your provider would do anyway, so no need to waste money.
doktornotor said:
Well, if you keep restoring messed-up/corrupt/broken settings etc., no wonder flashing does not help. Wipe everything and flash a stock ROM, do not restore any broken mess. That is what your provider would do anyway, so no need to waste money.
Click to expand...
Click to collapse
I did flash shiny ROMs located on this forum over here. I spoke to LG and I have to call them back in a couple. They're gonna get the same phone and we're gonna walk the problem together.
Like 20 minutes or something later..
Yeah, so they said they don't know and I should take it to an MTN outlet. They're not very helpful on Sundays I think.. Gonna take it in tomorrow then
Oh yeah, and i would still like to know..
..if my service provider would be able to restore original Froyo 2.2.0 or if I should consider forking out for a new phone?? .. Or if by any chance LG could restore Froyo bearing in mind that I've flashed 2.2.1 stock and the phone has been un-rooted, or if they'll say hard luck??
Well, as I already said. You still have lingering junk there. Flight mode is not some miracle, it is simply a profile with WiFi/BT/2G+3G turned off. (What can be turned on in flight mode is set in an sqlite DB, so it is even possible to override it).
So, no matter what you have flashed or not, you did that incorrectly. Being unable to switch flight mode on/off does not come out of nowhere.
There is absolutely no need to buy a new phone, your problem is a software one, not a faulty HW. (For questions what LG will or will not do, ask them, not here.)
doktornotor said:
Well, as I already said. You still have lingering junk there. Flight mode is not some miracle, it is simply a profile with WiFi/BT/2G+3G turned off. (What can be turned on in flight mode is set in an sqlite DB, so it is even possible to override it).
So, no matter what you have flashed or not, you did that incorrectly. Being unable to switch flight mode on/off does not come out of nowhere.
There is absolutely no need to buy a new phone, your problem is a software one, not a faulty HW. (For questions what LG will or will not do, ask them, not here.)
Click to expand...
Click to collapse
Thanks ^_^ You obviously know more about this than me, so how do you suggest I proceed if I wish to get back to stock Froyo like it was when I got the phone?? Should I take the phone in to service provider or something??
antiother said:
how do you suggest I proceed if I wish to get back to stock Froyo like it was when I got the phone?? Should I take the phone in to service provider or something??
Click to expand...
Click to collapse
Well, if you are unable to restore the original ROM properly, then take it somewhere where they can. Does not necessarily have to be your service provider, any authorized LG service can do that, plus lots of unauthorized shops can do it as well (warranty is a different issue here, though.)
Anyway, before you take the phone somewhere - if you flashed something from the thread you mentioned, you probably have 2.2.0 or 2.2.1. Have you tried using LG PC Suite to upgrade the phone to latest version (should be 2.2.2 pretty much regardless the operator/country). Might get you proper flash as well.
Also, CWM recovery has Wipe All option which wipes everything except for recovery.
Thanks so much ^_^ I got a 2.2.1 *.DZ. I don't have the energy to struggle with that anymore so I it took to my service provider and the guy there ordered me a new phone. Awesome of him hey!! At the end of the day, phones were actually made to call, TXT, and tweet with, so I'm through flashing. Time for me to throw in the towel and show it some love just the way it is!!
doktornotor said:
Well, if you are unable to restore the original ROM properly, then take it somewhere where they can. Does not necessarily have to be your service provider, any authorized LG service can do that, plus lots of unauthorized shops can do it as well (warranty is a different issue here, though.)
Anyway, before you take the phone somewhere - if you flashed something from the thread you mentioned, you probably have 2.2.0 or 2.2.1. Have you tried using LG PC Suite to upgrade the phone to latest version (should be 2.2.2 pretty much regardless the operator/country). Might get you proper flash as well.
Also, CWM recovery has Wipe All option which wipes everything except for recovery.
Click to expand...
Click to collapse
Oh yeah, and I tried upgrading to 2.2.2.. No luck, it said I had the latest version already at 2.2.1. Doesn't make any sense right. And that's from the official LG updater thinggy.. Hey, how do I mark this thread as SOLVED??
doktornotor said:
Well, if you are unable to restore the original ROM properly, then take it somewhere where they can. Does not necessarily have to be your service provider, any authorized LG service can do that, plus lots of unauthorized shops can do it as well (warranty is a different issue here, though.)
Anyway, before you take the phone somewhere - if you flashed something from the thread you mentioned, you probably have 2.2.0 or 2.2.1. Have you tried using LG PC Suite to upgrade the phone to latest version (should be 2.2.2 pretty much regardless the operator/country). Might get you proper flash as well.
Also, CWM recovery has Wipe All option which wipes everything except for recovery.
Click to expand...
Click to collapse
Related
I tried to flash a kernel to my samsung showcase, but it didn't work. it wouldn't even go to boot logo. i have gotten it to boot now but everything keeps crashing every few seconds and it says verizon, but i have ntelos. I cant get any 3g or data. I have ClockWorkMod installed on it. PLEASE HELP.
jdp123321 said:
I tried to flash a kernel to my samsung showcase, but it didn't work. it wouldn't even go to boot logo. i have gotten it to boot now but everything keeps crashing every few seconds and it says verizon, but i have ntelos. I cant get any 3g or data. I have ClockWorkMod installed on it. PLEASE HELP.
Click to expand...
Click to collapse
If you have clockworkmod installed on it, boot into cwm and wipe data/cache/dalvik and flash a different showcase kernel that you know works. Do you have a functioning showcase kernel already on your sd card?
You flashed a Verizon Fascinate kernel onto a Telus Showcase. Good job.
Dude I did the same thing my advice and what worked for me is flash the cell south showcase rom. Root your phone get rid of all cell south Apps make it look stock take it back get a new one that's if your in your 60 or 90 days i forget what it is as far as I know there's no roms For are showcase yet. If they give u **** just say u talked to customer service and samsung and u told them your phone seemed really slow and u noticed a few apps always running that shouldn't be even after you killed them like screen capture service and a few others and they told u it's probably a phone defect and should take it back and pick the rep that's looks like they want to go home they only want sells and will get you out as quick as possible. I hope all works out well for you I know how it is I'm on frog and payed 450..... but it should
Got my cell south Rom from some dudes in a irc chat room #samsung-mesmerize they helped me out a lot and if your willing to dump your Rom when u get a new phone they will make you a Rom for your phone
Electrodeath0 said:
You flashed a Verizon Fascinate kernel onto a Telus Showcase. Good job.
Click to expand...
Click to collapse
Telus doesn't use the Showcase. They use a GSM version of the Fascinate. The Showcase is a CDMA phone that is like a twin to the Verizon Fascinate and the US Cellular Mesmerize.
Another Fascinating post by my XDA app...
big_c said:
Dude I did the same thing my advice and what worked for me is flash the cell south showcase rom. Root your phone get rid of all cell south Apps make it look stock take it back get a new one that's if your in your 60 or 90 days i forget what it is as far as I know there's no roms For are showcase yet. If they give u **** just say u talked to customer service and samsung and u told them your phone seemed really slow and u noticed a few apps always running that shouldn't be even after you killed them like screen capture service and a few others and they told u it's probably a phone defect and should take it back and pick the rep that's looks like they want to go home they only want sells and will get you out as quick as possible. I hope all works out well for you I know how it is I'm on frog and payed 450..... but it should
Got my cell south Rom from some dudes in a irc chat room #samsung-mesmerize they helped me out a lot and if your willing to dump your Rom when u get a new phone they will make you a Rom for your phone
Click to expand...
Click to collapse
how do i flash cell south rom? I cant even boot into my phone now and if i mount my sd card from cwm it doesnt show up on pc. The only things i can go into are cwm, download mode, and recovery mode.
Use Odin in download mode go to the irc chat I told u adout and ask for the rom that's were I got mine the helped every step of the way ask for bakedtator I told him about you these are good guys they saved my ass http://webchat.freenode.net/ just make a nickname by putting it in the box like u already have one the channel is #samsung-mesmerize just like that put the #
jmcintire said:
Telus doesn't use the Showcase. They use a GSM version of the Fascinate. The Showcase is a CDMA phone that is like a twin to the Verizon Fascinate and the US Cellular Mesmerize.
Another Fascinating post by my XDA app...
Click to expand...
Click to collapse
Slow down there buddy I'm on a showcase sch i500 cdma right now n-telos does have it they started selling it around may 1st its not gsm n-telos is cdma a little different then the cell south found out the hard way
Same problem here. Found directions to install Cyanogen 7.1 on a Samsung Showcase as it listed it to be compatible. Downloaded ClockworkMod Recovery and installed it using Heimdall Suite 1.1.1. Used CWM to then install the Cyanogen 7.1 rom and Google apps rom as well. All seemed good except for when it booted it listed my carrier as Cellular South. My carrier is actually Ntelos.
Needless to say the only thing that initially worked were voice calls and the web for some reason. Text messaging was broken(a big one with me).
I tried to *228 to see if that would maybe program the phone for the proper settings but it did not work.
So I thought that because I had backed up my phone with CWM I could just revert back to my old image and all would be well. The restore function did not work. Rebooting into CWM from the ROM manager I was able to initiate the restore. All seemed well and it notified me it had restored. When I rebooted my phone however it was frozen at the Samsung logo. I rebooted into CWM and cleared my cache and did the factory reset only to find that after a reboot it just loads straight to CWM.
Now I basically have a useless phone. I can reinstall Cyanogen but I no longer have signal for service. It also seems hit or miss as to if it installs with no problems. Sometimes it will install and the default widgets will show errors loading. The google apps will not install sometimes even though they show confirmed through CWM. I can reboot the phone from ROM manager into CWM and it will perform the restore just the same as the first time without any problems but the phone will not boot back up to the stock ROM. If I try to boot straight to CWM using Volume+Home+Power it will not perform the restore. It goes through small part
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system
That's as far as I get.
I'm basically stuck in this vicious cycle with no end in site. I've tried researching til my eyes hurt to find a solution to my problem. I can't find a stock ROM anywhere. Obviously the combination of a small carrier and a small audience for this model phone yields little along the lines of widespread support. So I've came here to the XDA Developers board in hopes that someone will be able to help me.
OK, Heres the scenario, This is a replacement T-959 vibrant, sent from either TMO or Samsung, really not sure! My 1st phone never had any issues with modding, and always cooperated! Until I used KIES to update one day and It bricked, because of primary and SBL corruptions. [I know!!, found out 5 mins too late about using KIES] Anyway, since Ive had this replacement phone its done nothing but fight me from the start, never has acted right I think and I feel there's something wrong HW wise with it. My problem with it now, is it wont accept any other custom ROM I try to install, and only works with either 2.1 or 2.2 stock OEM ROM's. Meaning, Anything else ROM wise, It wont go past the last part of boot sequence, and just keeps looping, and does it over and over again! Ive tried all of Simple Honeys, Toxic 8's Roms, and each time it goes thru the loading successfully, and then starts it boot-up, but every single Flash Ive done, ROM wise, it hangs up and loops at the very last part of booting up. Ive come to realize now, it isn't the ROMS, but the phone " I THINK" Each time I tried a Custom ROM install, I started with stock fresh JFD install, and wiped and cleared out everything before starting another ROM install, but with each attempt that I try to go past anything other than Froyo stock, It does this boot loop problem at the final part!! It seems like who ever sent it to me, did something to the phone to prevent this. Modding it I mean. like right now I'm on Eugenes Froyo, with the 2E RECOVERY, It was working fine, until I upgraded the Eugenes kernel, which is suppose to work with this ROM, technically the phone still runs, but as soon as I did this, I now cant get into the two drives as mass storage to tranfer files, says insert disk, like as if its a CD Rom drive, WTF!! And like I said, this phone wont accept any other ROMS now, past stock Eclair or Froyo OEM and kernels as well. I don't understand what the problem is, My guess is they flashed something to prevent modding or its just a corrupted HW issue, anybody ever seen this before. I wish I had just JTAG'd my first phone with Josh over at Mobile Tech, and saved myself all this heartbreak and frustration, but its too late for that now! So anyway, I need to determine for sure if this phones screwed, HW wise or if there is SW to get this phone straighten out, to where it'll work right like my first one used to, and begin to accept custom ROM's like it should be able to do!! I'm at my last end with this phone, and I'm desperate to get a solid reason/answer for whats happening here, because Ive followed all the instructions and standard procedures to insure that all the attempted installs of the ROMS I mentioned go correctly. And its boiling down to either HW issues or a SW issue they created before they shipped it to me, or last but least hopefully a SW fix here, that can get the HW/phone to act right again, and maybe salvage this phone, otherwise I'm thinking I need to buy another brand new phone and hope for the best. I just don't want to be stuck and limited with Froyo stock, for the rest of my time using this phone, I want my freedom to choose again, like I had before, and also It ran so much better than OEM anyways!
Go back to stock using the sticky on the q&a then root using that same methOd and when you flash a custom room make sure you wipe dalvik and cache and delete user data
Sent from my SGH-T959 using XDA App
Quote" Go back to stock using the sticky on the q&a then root using that same methOd and when you flash a custom room make sure you wipe dalvik and cache and delete user data"
If you had picked up on it in my post, have already done this dozens of times!! Oh and BTW, when at JFD = 2.1 Eclair, it wont allow the 2 drives access to in Cabled USB mass storage, and therefore unable to CWM flash with zips, then I must go to 2.2 Froyo next to be able to get past that problem, but again when I go from there to any custom ROM, it fails to boot at the very end, and starts its looping. Again, the 1st phone I had, never ever, behaved like this!! Same phone but, different dates of manufacturing and also this one came from either Samsung or TMO in Plano,TX where that's all, they do is send out phones for replacement, and this one wasn't in a original box, something they worked on, grabbed off the shelf, and sent to me!! Its just a shame that 99% of all the ROMS are in zipped form, instead of TAR files, at least then I could've tried flashing some of them from, Eclair to see if that made a difference, but when they are zipped, you must use CWM recovery to flash, and thus again presents another problem as far as what I'm going thru here!
Got any thing else, Idea wise, that actually hasn't been tried yet, that makes sense??
OK, Ive made some progress, It seems for whatever stupid reason, that unlocking my phone, [jailbreaking] was the culprit of this phones renegade behavior, I simply restored it back to a locked status as a TMO provider, and Wholla, the phones now acting right!! And I have been able to get it to the ROM I wanted and flash a better kernel as well with 0 defects!!! And then I jailbroke it again, and its working flawlessly.
Personally I don't understand why that had a bearing on its behavior, but nun the less it did. And has cause me a few extra wrinkles around my eyes in stress trying to figure this out by myself, especially when all the suggestions and procedures I did was for nothing, until this phone was restored to a locked condition again!!
Go figure Right???? Grrrrrrrrrrrrr!!!! Anyway I hope mentioning this will prevent someone else in losing their hair or sanity!!
hello i think we have the problem, i also have openline my vibrant to be able to use here in our country.. i have 2.1 eclair, i just want to know what 2.2 ROM did you used coz you've said that it's ok to upgrade it to 2.2, but not other ROM, where did you get it.. can you pm me the link
thanks
Ok, so I have a rooted photon with cm 7.2 and sprint wasn't able to get it activated. ESN is fine and they inputed everything, but when I tried to do the ##yada yada thing nothing happens. It's supposed to let me put in a password. Does it need to be put back to stock then activated?
Yes you have to put it back to stock first.
Call me tomorrow after 9 am. I work for Sprint I may ne able to activate it for you. Pm me for my number.
Sent from my PC36100 using XDA Premium App
Joshhayes801 said:
Yes you have to put it back to stock first.
Click to expand...
Click to collapse
PM Sent Miguel, thanks. I can get a stock rom from here right Josh? I guess that will unroot it too. I did do a nandroid backup, so I can just re-root it and run that. Darn, that's what I get for not reading enough. I just assumed it was no biggie to activate any phone.
Edit:
I forgot I already had rdslite and had to un root it before. I accidentally soft bricked it when I first got it so i'm returning it to stock then I'll call back. I'll give you a call Miguel if I can't get it working, but once stock it should be fine, thank you.
jeffrimerman said:
PM Sent Miguel, thanks. I can get a stock rom from here right Josh? I guess that will unroot it too. I did do a nandroid backup, so I can just re-root it and run that. Darn, that's what I get for not reading enough. I just assumed it was no biggie to activate any phone.
Edit:
I forgot I already had rdslite and had to un root it before. I accidentally soft bricked it when I first got it so i'm returning it to stock then I'll call back. I'll give you a call Miguel if I can't get it working, but once stock it should be fine, thank you.
Click to expand...
Click to collapse
I don't have a photon so I wouldn't know but I am sure you can easily find a stock ROM. I just know I have tried to activate a few different phones that had custom ROMS and they would never activate until they were back to stock.
Sent from my Nexus S 4G using xda premium
Joshhayes801 said:
Yes you have to put it back to stock first.
Click to expand...
Click to collapse
OMG i'm stuck in a boot loop=(.. I ran RSD lite and put or attempted to put 198 on twice and still in boot loop. Any idea what I need to do now to get it out of boot loop?
Factory reset with hardware keys, Link Here. Then try to SBF, AKAIK your supposed to full wipe everything before trying to SBF. If thats a no go then try a different .SBF file of a different version, may have been a bad download or the such. And incase you didnt know, RSDLite is supposed to come back with a failure at the end, its normal. And FWIW, I think you could have gone back to a Nandroid of a stock rom to get it to activate. Dont quote me there but im pretty sure, know for a fact you can update prl and all that when unlocked and on stock rom so you should also be able to activate id assume.
Joshhayes801 said:
I don't have a photon so I wouldn't know but I am sure you can easily find a stock ROM. I just know I have tried to activate a few different phones that had custom ROMS and they would never activate until they were back to stock.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I'm going to flash a stock rom, but can I leave it unlocked? I unlocked it and put CWM back on so I can flash a stock rom and I think I should be ok. I'll give that a try first.
Edit: wwhhheeeww, ok so I just wiped data and dalvik and rebooted and the sbf file I was rsd ing came up. So it's totally stock, but with unlocked bootloader and with CWM. Rom is stock so I should be able to activate it unless the unlocked bootloader is a problem.
The only sprint phone that im aware of being able to be activated with CM is the NS4G. This is because sprint pushes a carrier profile from the network to your phone, which is what tells the phone it's allowed to use the network, and CM cannot receive nor retrieve the profile, hence why it wont activate. The reason CM works on our phones is because we already have the profile on it prior to flashing CM, its activated so it doesn't need to receive a new profile. This process doesn't work in reverse (flash CM then activate phone).
With all that said, the short story is you need to be stock or stock based custom ROM prior to activating a sprint phone unless it's NS4G. After activating and the phone handshaking with the network, flash away.
thanks
KSmithInNY said:
The only sprint phone that im aware of being able to be activated with CM is the NS4G. This is because sprint pushes a carrier profile from the network to your phone, which is what tells the phone it's allowed to use the network, and CM cannot receive nor retrieve the profile, hence why it wont activate. The reason CM works on our phones is because we already have the profile on it prior to flashing CM, its activated so it doesn't need to receive a new profile. This process doesn't work in reverse (flash CM then activate phone).
With all that said, the short story is you need to be stock or stock based custom ROM prior to activating a sprint phone unless it's NS4G. After activating and the phone handshaking with the network, flash away.
Click to expand...
Click to collapse
Thank you for that great explanation
I should be able to load up my backup right? I did it with CWM just before I put it back to stock. I haven't done the root but since I have unlocked bootloader and CMW I should be good to go right?
KSmithInNY said:
The only sprint phone that im aware of being able to be activated with CM is the NS4G. This is because sprint pushes a carrier profile from the network to your phone, which is what tells the phone it's allowed to use the network, and CM cannot receive nor retrieve the profile, hence why it wont activate. The reason CM works on our phones is because we already have the profile on it prior to flashing CM, its activated so it doesn't need to receive a new profile. This process doesn't work in reverse (flash CM then activate phone).
With all that said, the short story is you need to be stock or stock based custom ROM prior to activating a sprint phone unless it's NS4G. After activating and the phone handshaking with the network, flash away.
Click to expand...
Click to collapse
i work for sprint and havent heard it put better. i have dealt with quite a few custs that wanted to activate on diff roms and always told em it couldnt be done but never could explain why... thanks for info there!
Wow! I need some help. I've acquired a Samsung Galaxy Note (i717, I believe) that shows all the signs of being healthy (appearance, touch screen, etc.) but persistently slows down at the ATT opening splash screen, begins to load Android, dies and reboots. Whatever variant rooted ROM I received it with (sluggish and unreliable) I have written over and now I can't get any farther than the Android settings screen. Therefore I do not know the exact version nor can I begin to set it up (wifi, etc.).
That's the 'presenting problem', so let me explain what I've done to this point (about 25 hrs. worth!). I have reloaded latest version of CWM (runs great) and then Padawan JB . . . same symptoms. I have loaded the ATT JB and ICS via the latest Odin successfully . . . with same symptoms. I have loaded TWRP (touch screen is snappy and works as it should) and Padawan JB again . . . with same symptoms. I have wiped caches before, after, and in between till I'm blue in the face, each time with the same symptoms. Most recently I have done a hard reset to native/factory settings . . . with no change! I've tried to scour the XDA (and any other sites) trouble shooting articles and seem to have come to a dead end.
Here's a couple things that I'm wondering: because I can't get deep enough into Android to check out the model number, could the phone be something other than an ATT model? At the top of the front face it simply says 'Samsung', not ATT at top and Samsung at bottom like my previous ATT Note. Right after boot I persistently get an ATT splash screen which would lead me to believe that it is ATT. Is there some other way to find model, say in TWRP? Do I need a phone specific version of Android? Second, everything seems to be working fine physically (i.e., no hardware problems). Could this thing have gotten a virus in an earlier life that's preventing the ROM from working right? I've not been able to get far enough to register it with my cell provider (second party, not ATT). Must you be up and running with the cell service to correctly load and use the ROM (wouldn't think so)? And if so, how without Android working? I've been using and playing with computers for 25 years, but I'm fairly new to the Android system (but learning fast!) Any help would sure be appreciated. I'd really like to resurrect this baby. I loved my first Note (till it fell off the car and disappeared).
pstrulm said:
Wow! I need some help. I've acquired a Samsung Galaxy Note (i717, I believe) that shows all the signs of being healthy (appearance, touch screen, etc.) but persistently slows down at the ATT opening splash screen, begins to load Android, dies and reboots. Whatever variant rooted ROM I received it with (sluggish and unreliable) I have written over and now I can't get any farther than the Android settings screen. Therefore I do not know the exact version nor can I begin to set it up (wifi, etc.).
That's the 'presenting problem', so let me explain what I've done to this point (about 25 hrs. worth!). I have reloaded latest version of CWM (runs great) and then Padawan JB . . . same symptoms. I have loaded the ATT JB and ICS via the latest Odin successfully . . . with same symptoms. I have loaded TWRP (touch screen is snappy and works as it should) and Padawan JB again . . . with same symptoms. I have wiped caches before, after, and in between till I'm blue in the face, each time with the same symptoms. Most recently I have done a hard reset to native/factory settings . . . with no change! I've tried to scour the XDA (and any other sites) trouble shooting articles and seem to have come to a dead end.
Here's a couple things that I'm wondering: because I can't get deep enough into Android to check out the model number, could the phone be something other than an ATT model? At the top of the front face it simply says 'Samsung', not ATT at top and Samsung at bottom like my previous ATT Note. Right after boot I persistently get an ATT splash screen which would lead me to believe that it is ATT. Is there some other way to find model, say in TWRP? Do I need a phone specific version of Android? Second, everything seems to be working fine physically (i.e., no hardware problems). Could this thing have gotten a virus in an earlier life that's preventing the ROM from working right? I've not been able to get far enough to register it with my cell provider (second party, not ATT). Must you be up and running with the cell service to correctly load and use the ROM (wouldn't think so)? And if so, how without Android working? I've been using and playing with computers for 25 years, but I'm fairly new to the Android system (but learning fast!) Any help would sure be appreciated. I'd really like to resurrect this baby. I loved my first Note (till it fell off the car and disappeared).
Click to expand...
Click to collapse
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory reset in between.
fbauto1 said:
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory
I would reflash cwm thru odin after that I would flash the latest TWRP 2.5. Then you can flash whatever. If padawan is givin u problems try something else like AOSP or AOKP. Padawan is TW based. JaimeD builds are pretty sweet.
sent from my GalaxySuperNote running OC Padawan JB
Click to expand...
Click to collapse
androidmechanic said:
fbauto1 said:
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory
I would reflash cwm thru odin after that I would flash the latest TWRP 2.5. Then you can flash whatever. If padawan is givin u problems try something else like AOSP or AOKP. Padawan is TW based. JaimeD builds are pretty sweet.
sent from my GalaxySuperNote running OC Padawan JB
Click to expand...
Click to collapse
If you want TWRP, flash TWRP. No need to flash CWM
Click to expand...
Click to collapse
AT&T Phones have a [logo}AT&T] on the top-center!!
But if you are in doubt, use kies to do a full recovery-restore [WILL ERASE EVERYTHING ON YOUR DEVICE].
See post #4 on this thread.
fbauto1 said:
androidmechanic said:
If you want TWRP, flash TWRP. No need to flash CWM
Click to expand...
Click to collapse
If you go thru Odin you would have cwm first. With the problems talked about, I would go back factory stock then re-root with Odin. Then thru cwm, flash twrp or whatever floats your boat.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
androidmechanic said:
If you go thru Odin you would have cwm first. With the problems talked about, I would go back factory stock then re-root with Odin. Then thru cwm, flash twrp or whatever floats your boat.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
fbauto1 said:
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
Click to expand...
Click to collapse
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
fbauto1 said:
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
Click to expand...
Click to collapse
androidmechanic said:
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
you are both actually correct, however, I am looking at PSTRULM's stats. if he is anything like me when I started, the more simple and less complication involved in the process, the more he may understand.
ANDROIDMECHANIC is stating the most basic and beginner way to do this and understand simply. after doing this a few times as I did, the basic mechanics of the process will become more fluent.
then he can make his own decisions as to methods which might be easier for him, without confusing.
I am sure you both are a huge help to everyone and I thank members such as yourself for your efforts. ME, I prefer baby steps, cause I know I can really EFF things up if I get confused
androidmechanic said:
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Just a reminder.. when flashing through Odin, make sure it's an ODIN-flashable tarball, i.e., you can't flash a recovery-type zip through Odin and vice versa.
This is a Backup of the PH1 ROM's system and modem partitions. This is a Pre-Rooted ROM with the SD Card write permissions fix. This is different from my other post in those two differences.
You will need a custom recovery to install this ROM. (http://forum.xda-developers.com/note...lipop-t3089382)
Always perform the appropriate backups and other steps just in case something messes up. If you are on Lollipop, you should be able to just flash and go without any data loss (except custom system apps), but no promises.
Extract the folder (ES File Explorer or 7 Zipper) to "extsdcard/TWRP/backups/[serial number]" then boot into recovery and restore the image. The easiest way to get this folder is to simply perform a backup first, then unzip this folder next to the one for the backup you just created.
I didn't factory reset prior to this backup because it's just system partitions, so let me know if there's anything weird.
https://drive.google.com/open?id=0B2iEgzRTFjrQa2JEbE1DSE9qNHM
Here's the Odin ROM:
http://forum.xda-developers.com/note-3-sprint/general/rom-odin-ph1-update-t3463178/page1
Here's my non-rooted TWRP ROM:
http://forum.xda-developers.com/not...stom-recovery-rom-stock-rooted-t3449321/page1
Still 5.0 this is probably just a security update
RDF
http://device.sprintpcs.com/Samsung/SM-N900P-SPRINT/PH1.rdf
evilvoice said:
Still 5.0 this is probably just a security update
RDF
http://device.sprintpcs.com/Samsung/SM-N900P-SPRINT/PH1.rdf
Click to expand...
Click to collapse
Yep, just a security update most likely. Looks like some of the stock (Sprint) apps may have been updated as well . The update file was only about 190 megabytes if I remember correctly.
Quick question on updating modem & firmware.. I'm stock rooted ok2, and i dont have this update yet. I am working toward flashing the newly released and highly anticipated DL Modded N5N7 v4 which requires the PH1 updated firmware.
Do I need to ODIN flash the update files from the other PHI ROM thread or can I just do a full wipe and flash this backup with TWRP?
Thanks in advance.
Sent from my SM-N900P using XDA Labs
MeAtKeRtN said:
Quick question on updating modem & firmware.. I'm stock rooted ok2, and i dont have this update yet. I am working toward flashing the newly released and highly anticipated DL Modded N5N7 v4 which requires the PH1 updated firmware.
Do I need to ODIN flash the update files from the other PHI ROM thread or can I just do a full wipe and flash this backup with TWRP?
Thanks in advance.
Sent from my SM-N900P using XDA Labs
Click to expand...
Click to collapse
You can just flash the rom you want and keep your current bootloader/modem. But it's always suggested to keep current with any bootloader/modem, that the OP mentioned. That way if there is a issue with the install, it wouldn't be that.
Sent from my Nexus s using XDA-Developers mobile app
jhunt75 said:
You can just flash the rom you want and keep your current bootloader/modem. But it's always suggested to keep current with any bootloader/modem, that the OP mentioned. That way if there is a issue with the install, it wouldn't be that.
Sent from my Nexus s using XDA-Developers mobile app
Click to expand...
Click to collapse
The preferable answer would have been 'NO' or 'I'M NOT SURE' as a direct answer to my very specific question... as I now have a phone that doesn't make phone calls.
MeAtKeRtN said:
The preferable answer would have been 'NO' or 'I'M NOT SURE' as a direct answer to my very specific question... as I now have a phone that doesn't make phone calls.
Click to expand...
Click to collapse
Hey, I've seen you in a few threads and figured I ask before I made the same mistake. I'm looking to upgrade to DL Modded N5N7 v4 like yourself. I have a exploding Note 7 still and I'm anticipating being blacklisted at some point. As crazy as it sounds I like my Note 3's snappiness and everything else over the 7. My issue is my Note 7 radio gets 4g in my job and my Note 3 radio is 3g or spotty. I'm sure my modem and baseband is outdated and may help being updated
I'm on a older Moars Rom Baseband Nk4 android version 4.4.2. Did you figure out where things went bad. I was thinking of following these instructions http://forum.xda-developers.com/note-3-sprint/general/rom-odin-ph1-update-t3463178 don't want to mess this up.
What did you use and what should you have used?
Thanks
Lyvewire said:
Hey, I've seen you in a few threads and figured I ask before I made the same mistake. I'm looking to upgrade to DL Modded N5N7 v4 like yourself. I have a exploding Note 7 still and I'm anticipating being blacklisted at some point. As crazy as it sounds I like my Note 3's snappiness and everything else over the 7. My issue is my Note 7 radio gets 4g in my job and my Note 3 radio is 3g or spotty. I'm sure my modem and baseband is outdated and may help being updated
I'm on a older Moars Rom Baseband Nk4 android version 4.4.2. Did you figure out where things went bad. I was thinking of following these instructions http://forum.xda-developers.com/note-3-sprint/general/rom-odin-ph1-update-t3463178 don't want to mess this up.
What did you use and what should you have used?
Thanks
Click to expand...
Click to collapse
My mistake was following bad advice and flashing the TWRP Backup of PH1 in the OP of this thread instead of ODIN flashing the full ROM-ODIN-PH1- Update- t3463178.
I was able to get TWRP to restore my backup to OK2. From there I did a full wipe 3x and ODIN flashed the full PH1 update, immediately rooted with CFautoroot and reinstalled TWRP 2.8.7.0.
From there I followed the OP instructions in the DL Modded N5N7 thread which require the ROM, Kernel Cleaner, MVNO Buzbee2, Sprint VVM, and I installed the DL MM UIX Kernel.
The ROM and kernel are both really well put together except my mobile network connection to Sprint has been intermittent... the phone was stuck roaming and was connecting in spurts with Verizon, sprint, or the network was unavailable.
I just dirty flashed the Rom, Kernel, and MVNO fix an hour or so ago and the APNs seem to be sticking now. We'll see.
I have three Note 3's and each has its own quirky 'personality'- not especially playing nicely with most of the Port ROMs available these days. Hope this answers your questions and helps someone else trying to keep their Note 3 thriving.
MeAtKeRtN said:
The preferable answer would have been 'NO' or 'I'M NOT SURE' as a direct answer to my very specific question... as I now have a phone that doesn't make phone calls.
Click to expand...
Click to collapse
I am not trying to start any trouble, but from reading your comment it seems you are suggesting I gave you bad or wrong advice. So I want to explain myself just in case it was a misunderstanding. All roms are capable of being flashed with older bootloaders and modems. But the proper thing to do, is to always be up to date with all bootloader/modem files. This way you will not run into any problems. Now I didn't mention anything about flashing the OP'S twrp backup method. I figured you may have been experienced enough to flash these BL/modem files from a source like sammobile. Then proceed to flash your rom of choice. As you experienced you lost your signal. It may have been a few reasons why this happen. 1. The way the OP mentioned to flash wasn't meant for your phone. Every phone response differently. 2. The rom for whatever reason can only be used if you dirty flashed over your current system. This will not be the only time you may have to do it this way. So instead of being sarcastic with your reply, maybe try and ask the one who is helping you to explain themselves more. We are all here to help each other, and by no means was my response to your question was meant to harm your phone.
Sent from my SM-N920C using XDA-Developers mobile app
jhunt75 said:
I am not trying to start any trouble, but from reading your comment it seems you are suggesting I gave you bad or wrong advice. So I want to explain myself just in case it was a misunderstanding. All roms are capable of being flashed with older bootloaders and modems. But the proper thing to do, is to always be up to date with all bootloader/modem files. This way you will not run into any problems. Now I didn't mention anything about flashing the OP'S twrp backup method. I figured you may have been experienced enough to flash these BL/modem files from a source like sammobile. Then proceed to flash your rom of choice. As you experienced you lost your signal. It may have been a few reasons why this happen. 1. The way the OP mentioned to flash wasn't meant for your phone. Every phone response differently. 2. The rom for whatever reason can only be used if you dirty flashed over your current system. This will not be the only time you may have to do it this way. So instead of being sarcastic with your reply, maybe try and ask the one who is helping you to explain themselves more. We are all here to help each other, and by no means was my response to your question was meant to harm your phone.
Click to expand...
Click to collapse
No misunderstanding here... I asked a specific either/or question directly related to the thread topic (twrp custom recovery version) and you either misunderstood my question or decided it required an answer other than a 'yes or no' As a result of your longwinded answer, I lost several hours working through how to get a signal back on my phone. Was pretty annoying.
MeAtKeRtN said:
No misunderstanding here... I asked a specific either/or question directly related to the thread topic (twrp custom recovery version) and you either misunderstood my question or decided it required an answer other than a 'yes or no' As a result of your longwinded answer, I lost several hours working through how to get a signal back on my phone. Was pretty annoying.
Click to expand...
Click to collapse
I never knew giving someone detailed information was a problem. It's funny how I never had an issue with the install, but you did. It seems you lack enough experience to realize a few things. But I will make it a point to never help you again. Whether that's to long-winded or not for you, oh well.
Sent from my SM-N920S using XDA-Developers mobile app
MeAtKeRtN said:
No misunderstanding here... I asked a specific either/or question directly related to the thread topic (twrp custom recovery version) and you either misunderstood my question or decided it required an answer other than a 'yes or no' As a result of your longwinded answer, I lost several hours working through how to get a signal back on my phone. Was pretty annoying.
Click to expand...
Click to collapse
Did you get it all figured out?
I did get it figured out. Wasn't much more than an unnecessary inconvenience that someone else might be able to avoid.
Ok, so something weird...
Im running KK4.4.2 with the NC5 baseband on Sprint.
I upgraded my TWRP to 2.780 to flash the recovery both first time 'dirty flashing' and the 2nd time doing a facory wipe.
I removed the battery after the flash.
When I reboot, the phone stays on the Yellow Sprint screen and the LED pusles blue slowly. So far been doing it for 15 mintues.
What am I missing?
Dave
Unidave199 said:
Ok, so something weird...
Im running KK4.4.2 with the NC5 baseband on Sprint.
I upgraded my TWRP to 2.780 to flash the recovery both first time 'dirty flashing' and the 2nd time doing a facory wipe.
I removed the battery after the flash.
When I reboot, the phone stays on the Yellow Sprint screen and the LED pusles blue slowly. So far been doing it for 15 mintues.
What am I missing?
Dave
Click to expand...
Click to collapse
Give it 30 minutes? It seriously takes a long time. Are you sure you want to upgrade to lollipop? In just asking because you've been on Kit Kat long after support for lollipop or this phone has long stopped. I'd suggest downloading the latest Odin and flashing that instead, unless there is something here you wanted? I'm rooted on PL1 and have no issues other than my phone being as old as it is and how many times it's been flashed.
evilvoice said:
Give it 30 minutes? It seriously takes a long time. Are you sure you want to upgrade to lollipop? In just asking because you've been on Kit Kat long after support for lollipop or this phone has long stopped. I'd suggest downloading the latest Odin and flashing that instead, unless there is something here you wanted? I'm rooted on PL1 and have no issues other than my phone being as old as it is and how many times it's been flashed.
Click to expand...
Click to collapse
30 minutes? Woah that is a long time. Ok I will give it a try sometime when I go to bed.
I am mainly trying to get the PL1 update and not mess with Odin if I can get around it. I would like to try and port the Darklord Marshmellow ROM and take advantage of built in google assistant
So I thought I would try them. And always get back if I need to but wanted to keep the PL1 modem updates.
I only have one problem with one other phone user... She doesnt always get my texts and I dont always get hers. I dont know if others arent getting them and just dont know but my 1 friend I text a lot so she notices when there is a gap.
Anyways. Just feeling out how I can maximize this phone's performance. NO plans on changing phones anytime soon.
Unidave199 said:
30 minutes? Woah that is a long time. Ok I will give it a try sometime when I go to bed.
I am mainly trying to get the PL1 update and not mess with Odin if I can get around it. I would like to try and port the Darklord Marshmellow ROM and take advantage of built in google assistant
So I thought I would try them. And always get back if I need to but wanted to keep the PL1 modem updates.
I only have one problem with one other phone user... She doesnt always get my texts and I dont always get hers. I dont know if others arent getting them and just dont know but my 1 friend I text a lot so she notices when there is a gap.
Anyways. Just feeling out how I can maximize this phone's performance. NO plans on changing phones anytime soon.
Click to expand...
Click to collapse
I still use my note 3. Granted not for main phone as I switched to iPhone, but I use it every day. I don't really know the hesitation of using Odin, but to each their own. If you did decide to use Odin, I'd flash the ROM, boot it, go to download mode again, flash TWRP, boot recovery (so it sticks and doesn't go back to stock recovery), flash SuperSU, done. You're rooted on PL1. Hopefully you have already backed up your text messages and other various things to either SDCard or something else. I'm not sure if that survives whether you wipe and flash clean or Odin. Depending on provider, that could be your issue with text messages. If you're with Sprint, check that you are on latest PRL. If not, make sure APN settings are correct.
If you're only looking for Assistant, I had it running on stock PL1. XDA did a blog post about enabling it in Lollipop, so once you upgrade, check it out. I couldn't stay on Marshmallow. Being that these are ports and not specifically built for our phone, I ran into issue with every single ROM either not being able to place calls, text (MMS actually), or wireless/data not working. No matter what I changed APN to, I would always have issues. Some do not. I just can't recommend a port when they haven't worked for me. Some roms have been abandoned, which meant if I found one that I could at least handle, it was so outdated that it was unusable (issues had arisen and the developer had moved on so they weren't being fixed). By handling a rom, I mean that after I upgraded to iPhone, I only needed wireless to work (to connect to hotspot) and it not go into a boot loop or crash all the time (some do). Those roms I have no idea if calls or text work because I wasn't using that. A lot have issues with wireless working.
One more thing you can try is to do a flash, wait about 30 minutes. If it still doesn't boot, pull the battery and reboot into recovery. Wipe data and cache and reboot again. It should boot. It'll still take a long time. Make sure you wait the 30 minutes before pulling the battery (it should have finished upgrading your system by then). Do note that first boot from now on will take forever no matter if it's a port or stock. Lollipop and higher take a long time to upgrade. I've only had 1 or 2 roms take around 5 minutes and that's because they were minimalist and without Google apps. The phone does get a little warm and uses a lot of battery, so I'd keep it plugged in.
Please report back if you got it to work and how. Like I said, I still use mine. I still visit this forum every day even though I've had an s5 and an s7 edge. I love this phone. I need to get mine replaced because I've worn it out: broken charger port so I have to make sure the cable is plugged in a certain way and I can't touch the phone while charging, side molding is broken off in places, some of my partitions can't be changed which means the memory is failing (not even Odin flashes correctly anymore let alone custom roms). But, it still keeps on ticking.
evilvoice said:
I still use my note 3. Granted not for main phone as I switched to iPhone, but I use it every day. I don't really know the hesitation of using Odin, but to each their own. If you did decide to use Odin, I'd flash the ROM, boot it, go to download mode again, flash TWRP, boot recovery (so it sticks and doesn't go back to stock recovery), flash SuperSU, done. You're rooted on PL1. Hopefully you have already backed up your text messages and other various things to either SDCard or something else. I'm not sure if that survives whether you wipe and flash clean or Odin. Depending on provider, that could be your issue with text messages. If you're with Sprint, check that you are on latest PRL. If not, make sure APN settings are correct.
If you're only looking for Assistant, I had it running on stock PL1. XDA did a blog post about enabling it in Lollipop, so once you upgrade, check it out. I couldn't stay on Marshmallow. Being that these are ports and not specifically built for our phone, I ran into issue with every single ROM either not being able to place calls, text (MMS actually), or wireless/data not working. No matter what I changed APN to, I would always have issues. Some do not. I just can't recommend a port when they haven't worked for me. Some roms have been abandoned, which meant if I found one that I could at least handle, it was so outdated that it was unusable (issues had arisen and the developer had moved on so they weren't being fixed). By handling a rom, I mean that after I upgraded to iPhone, I only needed wireless to work (to connect to hotspot) and it not go into a boot loop or crash all the time (some do). Those roms I have no idea if calls or text work because I wasn't using that. A lot have issues with wireless working.
One more thing you can try is to do a flash, wait about 30 minutes. If it still doesn't boot, pull the battery and reboot into recovery. Wipe data and cache and reboot again. It should boot. It'll still take a long time. Make sure you wait the 30 minutes before pulling the battery (it should have finished upgrading your system by then). Do note that first boot from now on will take forever no matter if it's a port or stock. Lollipop and higher take a long time to upgrade. I've only had 1 or 2 roms take around 5 minutes and that's because they were minimalist and without Google apps. The phone does get a little warm and uses a lot of battery, so I'd keep it plugged in.
Please report back if you got it to work and how. Like I said, I still use mine. I still visit this forum every day even though I've had an s5 and an s7 edge. I love this phone. I need to get mine replaced because I've worn it out: broken charger port so I have to make sure the cable is plugged in a certain way and I can't touch the phone while charging, side molding is broken off in places, some of my partitions can't be changed which means the memory is failing (not even Odin flashes correctly anymore let alone custom roms). But, it still keeps on ticking.
Click to expand...
Click to collapse
Come back to Android! We miss you!!!!
Yes I am backed up and also have a Titanium Backup of everything so I am pretty much covered... I have even backed up the backups to my PC!
You have much wisdom in what you are saying. I thought I would play around with some other ROM's and see what the potential is.
I hear good things about the Darklord Reborn by Midevil and JCorderno so thought I would investigate.
I am not opposed to using Odin, but I was at work, and no access to a computer so wanted to see if I could do the upgrade 'on the fly' since I am already rooted and with recovery.
Man, waiting 30 minutes for a phone to boot sounds like a anxiety attack waiting to happen! But still wanna give it a try.
As to your USB port. Have you thought of going wireless charging? I did and haven't looked back! You can get a wireless charging back and a case that will fit at...
for the charging back
https://smile.amazon.com/Samsung-Ga...=8-2&keywords=samsung+note+3+wireless+charger
for the case
https://smile.amazon.com/gp/product/B00F3KP156/ref=oh_aui_search_detailpage?ie=UTF8&psc=1
Clone Wars....
Just wanted to put out a big THANKS for this.. I broke my Note 3 after 2,433 days (long story) but had bought a stock spare on Ebay last year... Making the switch now, but your PH1 Flashable update is making it super easy!
To let everyone who needs to use this nowdays... you will need to Flash an older TWRP (I used 2.7.8) in order to allow the Modem partition to be overwritten. Then you can flash up to 3.x to load a Android 10 based rom.