I decided to get my girlfriend a Verizon SCH-I545 to replace her T-Mobile Galaxy S3. It was working great on our T-Mobile service. Then I saw online that Verizon had released lollipop on their S4, so I figured I would plug the phone into Kies and update it from 4.4.2 to 5.0.1. I updated it overnight. When she went to use it in the morning, everything worked great, except it wouldn't send a text message. T-Mobile and Samsung support said that it is because T-Mobile hasn't released their lollipop rom for the S4 yet. I figured the best thing to do would be to roll back the firmware. Having done some rooting and custom roms on my old galaxy S2 Epic 4g Touch, I felt like I knew exactly what to do. I downloaded multiple ROMs and tried to install them through ODIN and through stock recovery. Nothing took. Finally after trying about 10 things, I soft bricked the phone. I can still get into download (ODIN) mode, but I can't get into stock recovery anymore. When I try to go into stock recovery it gives me this message: "Software Update Failed" "Your device didn't update successfully. Use the Verizon Software Repair Assistant on a computer to repair your device and complete the update." But, while the phone was still able to boot into android, the phone installed the Verizon Software Repair Assistant. I attempted to use it to rollback to 4.4.2 and the Assistant told me that it couldn't do anything to repair 5.0.1.
What I need to accomplish is either getting the phone back to 4.4.2 or 5.0.1 with text messaging working by any means necessary. Before I soft bricked the phone, I was hoping to avoid changing from stock recovery, but at this point I'm willing to do whatever I need to. For compatibility reasons, I hoped to try to keep her on a stock rom. If anyone knows of a rom with no bugs and a close to stock experience, I'll gladly set her up any way you guys think I should.
Thank you in advance for your assistance. I apologize for being "long winded" but I wanted to try and give as much detail as possible.
Still looking for any help I can get in resolving these issues.
You can't flash custom recovery for anything newer than 4.3 you will just jack up your phone trying.
Is both Talk & Data working??? SMS might be just improper APN settings. Google the APN for T-Mobile and that should fix it.
Since you installed 5.0.1 over Kies you are kind of stuck cause that would have updated the baseband and you can't have anything older than the baseband version.
Try installing this over Odin:
https://www.androidfilehost.com/?fid=23991606952596145
If you have Odin 3.09 or 3.10 choose AP to load the file. Make sure its unzipped too.
google luck!
somewhat resolved
I'm no longer soft bricked. I just got that back up and going. However the phone will still not send text messages. From what I've found, this only happens on 4g LTE. But, data, incoming texts, phone calls, mms, and everything else has been working just fine.
Yeah, you can curse Verizon for this. They lock down everything. A lot of people are flashing the Verizon version of Lollipop which screws their phone. I would show you a fix for that, but you need root, and OC1 doesn't have it yet. No fix for this because you can't Odin back and there is no root.
if you look at the link i posted its a version of Lollipop that lets you flash back to KitKat. It only works if you never installed lollipop. Unfortunately for me my phone wont read my sim card anymore its pretty much just a small tablet.
cwa82 said:
if you look at the link i posted its a version of Lollipop that lets you flash back to KitKat. It only works if you never installed lollipop. Unfortunately for me my phone wont read my sim card anymore its pretty much just a small tablet.
Click to expand...
Click to collapse
Sadly I had upgraded to lollipop, which is what created my problems to begin with. If I had never updated, text messages would've always worked, and ib never would have soft bricked the phone trying to roll back to kit-kat. I'm just glad I got the soft brick fixed, now I just have to wait for a fix on the text messaging.
bigg6987 said:
Sadly I had upgraded to lollipop, which is what created my problems to begin with. If I had never updated, text messages would've always worked, and ib never would have soft bricked the phone trying to roll back to kit-kat. I'm just glad I got the soft brick fixed, now I just have to wait for a fix on the text messaging.
Click to expand...
Click to collapse
You might be better off just buying her a different phone and selling that one.
Related
I'm trying to get my note back to original stock GB so I can ota upgrade to ICS.
I did a complete 'backup' of the original rom before I started messing around, and now, no matter what I do, I can't get that backup to reinstall on the phone.
I've done a lot of searching around, and found many threads about getting notes back to AT&T stock, and am very wary about doing that.
I've also found a few threads about getting back to original bell stock firmware etc, but whenever I run the files through odin, I get wierd errors (some with chinese writing), and just get frustrated.
I liked a few of the custom rom's I found, but the crazy thing, is the spen gestures (specifically the double-tap with button down for quick memos) are just too important to be without. I got the phone for work, and thought those where neat 'features'. Well.. seems I can't live without them.
But NOTHING I can find helps. I've tried methods listed on rootgalaxynote.com to unroot and get back to stock, and everything looks fine till I try either ota updating or kies updating. The phone simply isn't recognized in kies, and the ota update says nothing is available. and I know it IS available, cause I did the upgrade just after it was released, before I did all this custom rom stuff.
I'm start to get at my wits end. I simply want my original stock firmware etc. back on the phone, upgraded to ICS, and then I can just forget about everything else.
Is there anyone that can help?
P.S. if you know of any links I may have overlooked, please just post them. Believe me when I say I've spent well over a week just browsing the forums and google, doing searches etc. Its entirely possible it's something obvious that I just didn't see... with my 3 older kids and a newborn, I'm getting almost zero sleep, and am constantly frazzled. I sometimes don't even realize my wife is talking to me (on the worse days).
Anyways, thanks for anyone's help.
Ragnarkov said:
I'm trying to get my note back to original stock GB so I can ota upgrade to ICS.
I did a complete 'backup' of the original rom before I started messing around, and now, no matter what I do, I can't get that backup to reinstall on the phone.
I've done a lot of searching around, and found many threads about getting notes back to AT&T stock, and am very wary about doing that.
I've also found a few threads about getting back to original bell stock firmware etc, but whenever I run the files through odin, I get wierd errors (some with chinese writing), and just get frustrated.
I liked a few of the custom rom's I found, but the crazy thing, is the spen gestures (specifically the double-tap with button down for quick memos) are just too important to be without. I got the phone for work, and thought those where neat 'features'. Well.. seems I can't live without them.
But NOTHING I can find helps. I've tried methods listed on rootgalaxynote.com to unroot and get back to stock, and everything looks fine till I try either ota updating or kies updating. The phone simply isn't recognized in kies, and the ota update says nothing is available. and I know it IS available, cause I did the upgrade just after it was released, before I did all this custom rom stuff.
I'm start to get at my wits end. I simply want my original stock firmware etc. back on the phone, upgraded to ICS, and then I can just forget about everything else.
Is there anyone that can help?
P.S. if you know of any links I may have overlooked, please just post them. Believe me when I say I've spent well over a week just browsing the forums and google, doing searches etc. Its entirely possible it's something obvious that I just didn't see... with my 3 older kids and a newborn, I'm getting almost zero sleep, and am constantly frazzled. I sometimes don't even realize my wife is talking to me (on the worse days).
Anyways, thanks for anyone's help.
Click to expand...
Click to collapse
If I'm you I would continue with a custom rom. GNote replaces what you want. You can always install a TW based ROM. What I do is have Gnote as a shortcut on my homescreen. With Gnote I can still write with my Spen. Personally, I'd never use a NON-JB Paranoid ROM. ICS has melted over the summer! Being able to tweak my DPI settings is very important for me for each app. The default DPI and screen layouts are too fricken big, ie; status bar and icons. My eyes are still fine so I don't everything humongous on my screen.
Make sure you have Odin3 v1.85 on your pc. Download the Bell ICS ROM from here:
http://www.hotfile.com/dl/163095548/c1447e9/I717MUGLF4_I717MBMCLF4_BMC.zip.html
Unzip it on your pc. Restart your phone to Download Mode (Hold "Volume Down" and "Power" to start your phone). Once in download mode connect to your pc and start Odin. Put the ROM.MD5 file in the PDA slot that you just unzipped and update away.
This will give you the Bell ICS stock ROM. Better than the OTA when it comes to rooting it. If you have been reading for a week then I am sure you know what that means.
SOLVED
Thanks for the tips/suggestions.
I did a little more reading, and came to this thread:
http://forum.xda-developers.com/showthread.php?t=1599127
Flashed the kernal/system/recover like it said, and still a nogo. So then I figured wth, lets flash modem too.
BAM. booted it back, and its currently snagging the ota update.
So now that I have the methods and files to get back to stock, I am no longer worried too much about the future. I did have paranoid 2.0 for a while, and was loving it, but the simple idea of doubletapping while in ANY app to get a quick memo was still missing. Maybe after a bit I'll be hating the touchwiz ui yet again, and need a change. But at least I know now how to get back to stock.
Go figure. The thread itself looks vaguely familiar from earlier in the week, but I for some reason must have skipped it. I just got off a nice nap my wife let me have, and HEY... i figured it out. Guess 'sleep' is actually kinda important
Modem is the most important part for having you phone recognized properly for the OTA update. Link I gave you would have given you the update.
I have been trying to update my S4 (vruame7) to the latest. I'm willing to lose root. The issue I'm having though is one that NOBODY seems to have mentioned anywhere: It started where I couldn't update over the air as the update fails. So I tried to update it with Kies on my mac but the program says I need more memory on my phone even though I already have it. This prompted me to unroot my phone and do the update again, but the issue is still there. So I tried booting into recovery and that worked. I decided then to reboot my phone and add CWM touch via ROM toolbox Pro. It said it worked fine, but now I cannot boot into the recovery mode. It just goes straight into ODIN mode and it won't prompt me to confirm it or not. I get into a very soft boot loop if I try and reboot though Rom Toolbox Pro to go into the recovery. I will land in ODIN and then unless I tell the phone manually to go into ODIN and then NOT proceed than it will be in a soft boot loop. So far I've tried unrooting and using Kies, Rooting and trying to load CWM onto my phone and failing, causing OTA to not be able to even start installing, and I've yet tried to go into safe mode and try to reset my phone that way. I might have to do that. if anyone has any other ideas I am open to that.
Your on me7 so you half to use safestrap that's the on way you can have a recover...... You probably half to Odin your phone back to me7 for the update to work. You can't use cwm or twrp on me7, unless u have safetrap installed and the its a version of twrp in it
hyperdrive powered s4
ebsk8er06 said:
Your on me7 so you half to use safestrap that's the on way you can have a recover...... You probably half to Odin your phone back to me7 for the update to work. You can't use cwm or twrp on me7, unless u have safetrap installed and the its a version of twrp in it
hyperdrive powered s4
Click to expand...
Click to collapse
Thanks. I've got safestrap installed sucessfully (it was so easy), and I'm now trying to install the update by wiping my phone and then doing it. I'll see if that works.
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
beez1717 said:
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
Click to expand...
Click to collapse
Heimdall is like odin but its mac.compatible
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Use oden or Heimdall (guess its a Mac thing) to flash back to stock and then you can take the update. You haven't bricked yet but it sounds like you are getting close so be careful.
beez1717 said:
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
Click to expand...
Click to collapse
Sounds like you did a full wipe on non safe side "stock rom" of safestrap so your gonna have to flash a whole factory image cause it all gone the whole os
So after working for hoursx and hours, of working at it, I finally found http://sonofgeektalk.wordpress.com/2013/06/13/heimdall-on-a-mac/ <-- that webpage and it helped walk me through using Helmdall and it worked after much fiddling and discovering that I had to plug in my phone AFTER it got into odin but BEFORE I confirmed I wanted to be in odin. I then had to not wipe the phone clean but just do the install with the right files. It worked and I'm so happy. Now to see if I can update the darn phone. Don't know if I can or not but hey, I've got my phone back up and running and that's a GOOD thing.
I don't care about root as much as I care about getting the latest software if it provides enhancements I like, or security features I want. I think that root is fun, but it can be a pain in the butt as I just saw. Now that I know how to do the whole shtick, I should be able to do a lot more with my phone. I remember when I had to learn the ins and outs of my old Xperia Play. Horrible battery life and sub-par graphics chip but an awesome phone that had an awesome utility that could do just about anything with the phone with minimal work.
Looks like the system is updating itself just fine using OTA. What a LONG workaround I had to do. Thank you all for helping me teach myself a lot more about my phone
I'm having trouble trying to update as well. I unrooted and did a factory reset but the update still fails. What should I be trying?
Sent from my SCH-I545 using xda app-developers app
beez1717 said:
So after working for hoursx and hours, of working at it, I finally found http://sonofgeektalk.wordpress.com/2013/06/13/heimdall-on-a-mac/ <-- that webpage and it helped walk me through using Helmdall and it worked after much fiddling and discovering that I had to plug in my phone AFTER it got into odin but BEFORE I confirmed I wanted to be in odin. I then had to not wipe the phone clean but just do the install with the right files. It worked and I'm so happy. Now to see if I can update the darn phone. Don't know if I can or not but hey, I've got my phone back up and running and that's a GOOD thing.
I don't care about root as much as I care about getting the latest software if it provides enhancements I like, or security features I want. I think that root is fun, but it can be a pain in the butt as I just saw. Now that I know how to do the whole shtick, I should be able to do a lot more with my phone. I remember when I had to learn the ins and outs of my old Xperia Play. Horrible battery life and sub-par graphics chip but an awesome phone that had an awesome utility that could do just about anything with the phone with minimal work.
Click to expand...
Click to collapse
I think the problem here was that you tried to take an official update AFTER you messed with your phone... you should take this as a lesson to always flash back to stock before trying any 'official' updates, or better yet just have some patience for the updated files to show up here on the forums so you don't have to deal with OTAs at all. I don't really see the big rush to get the newest MI1 update anyway, it really doesn't provide any huge benefits at all and plus will possibly void your warranty through that stupid Knox thing if you try to root.
One thing I've learned is use patients dont jump the gun and if your not sure before you do something look here cause someone has already screwed up so the right way will be here somewhere and video will be on youtube!!
I have a Galaxy S4 from AT&T. I got it a few months ago, rooted it a few weeks after I got it. Randomly about a week ago, when I would make or receive a phone call, I could not hear the phone ringing, couldn't hear the person talking and they couldn't hear me. The only two ways I found it would work is if I booted into safe mode or I was connected to my cars bluetooth. I have no idea what caused it and I haven't messed with anything (like installing apps or changing settings) anywhere around the time it happened. I did many factory resets and hard key resets but nothing fixed it. I saw I had an OTA update so I did that (which I now realize was a big no-no -_-).
Since I did the OTA update while still rooted, that seems to have messed up my root. I seem to be both rooted and not rooted. So in trying to fix my first problem, I created the second problem. To solve both of these, I've been trying to install a fresh stock ROM onto the phone (to nothing but failure). I was trying to remove the root and put it back to stock incase I had to send it in for repairs. I found a few guides/posts from other people who did the OTA update while rooted but I couldn't seem to get it to work. It mostly consisted of re-rooting the phone, then un-rooting it but I could never get the phone to actually show that it was rooted.
(I just tested the phone part of my phone to see if it was working. Called it, and I could hear and be heard fine. Hung up, waited a few minutes and tried again and it didnt work at all. Both times were while it has been turned on for several minutes).
Does anyone know how I can get back to as close to stock as I can get so I can at least get the actual calling part of my phone fixed? Either see if something to do with the rooting is causing the problem or at least let me send it in to get it fixed, then I'll re-root it later.
Phone: AT&T Galaxy S4
Baseband: I337UCUAMF3 <I know the MF3 isn't good for rooting now
Model: Samsung SGH-I337
Android version: 4.2.2
Device Status: Custom
Thanks for any help!
Update: Managed to get rooted again, using this method: http://forum.xda-developers.com/showthread.php?t=2387577. Calling still doesn't work, and (forgot to mention this before) oddly, if I push numbers on the number pad on my phone, you can hear the tones on the phone I'm connected to. Just can't hear me.
steven2k7 said:
I have a Galaxy S4 from AT&T. I got it a few months ago, rooted it a few weeks after I got it. Randomly about a week ago, when I would make or receive a phone call, I could not hear the phone ringing, couldn't hear the person talking and they couldn't hear me. The only two ways I found it would work is if I booted into safe mode or I was connected to my cars bluetooth. I have no idea what caused it and I haven't messed with anything (like installing apps or changing settings) anywhere around the time it happened. I did many factory resets and hard key resets but nothing fixed it. I saw I had an OTA update so I did that (which I now realize was a big no-no -_-).
Since I did the OTA update while still rooted, that seems to have messed up my root. I seem to be both rooted and not rooted. So in trying to fix my first problem, I created the second problem. To solve both of these, I've been trying to install a fresh stock ROM onto the phone (to nothing but failure). I was trying to remove the root and put it back to stock incase I had to send it in for repairs. I found a few guides/posts from other people who did the OTA update while rooted but I couldn't seem to get it to work. It mostly consisted of re-rooting the phone, then un-rooting it but I could never get the phone to actually show that it was rooted.
(I just tested the phone part of my phone to see if it was working. Called it, and I could hear and be heard fine. Hung up, waited a few minutes and tried again and it didnt work at all. Both times were while it has been turned on for several minutes).
Does anyone know how I can get back to as close to stock as I can get so I can at least get the actual calling part of my phone fixed? Either see if something to do with the rooting is causing the problem or at least let me send it in to get it fixed, then I'll re-root it later.
Phone: AT&T Galaxy S4
Baseband: I337UCUAMF3 <I know the MF3 isn't good for rooting now
Model: Samsung SGH-I337
Android version: 4.2.2
Device Status: Custom
Thanks for any help!
Update: Managed to get rooted again, using this method: http://forum.xda-developers.com/showthread.php?t=2387577. Calling still doesn't work, and (forgot to mention this before) oddly, if I push numbers on the number pad on my phone, you can hear the tones on the phone I'm connected to. Just can't hear me.
Click to expand...
Click to collapse
bro best solution for yu is to FLASH THE STOCK FIRMWARE THROUGH ODIN AND DEN ROOT UR DEVICE..
IT WILL SOLVE UR PHONE CALL PROBLEMS TOO
siva aggzz said:
bro best solution for yu is to FLASH THE STOCK FIRMWARE THROUGH ODIN AND DEN ROOT UR DEVICE..
IT WILL SOLVE UR PHONE CALL PROBLEMS TOO
Click to expand...
Click to collapse
I've been trying to flash the stock firmware, or at least I think its the stock firmware I need for it. Odin keeps giving me an "aboot" then "fail" errors as soon as I start the flashing process. Since I upgraded the software, is it even possible to install an older version of it back on?
steven2k7 said:
I've been trying to flash the stock firmware, or at least I think its the stock firmware I need for it. Odin keeps giving me an "aboot" then "fail" errors as soon as I start the flashing process. Since I upgraded the software, is it even possible to install an older version of it back on?
Click to expand...
Click to collapse
yup...if yu have nandroid backup den restore it with cwm/twrp... and if not
den flashing stock firmware is the only solution for yu to solve ur problem
siva aggzz said:
yup...if yu have nandroid backup den restore it with cwm/twrp... and if not
den flashing stock firmware is the only solution for yu to solve ur problem
Click to expand...
Click to collapse
Will I be able to flash the stock firmware after doing the OTA update? My baseband version is I337UCUAMF3 and the only ROM versions I can find are I337UCUAMDL and I337UCUAMDB.
steven2k7 said:
will i be able to flash the stock firmware after doing the ota update? My baseband version is i337ucuamf3 and the only rom versions i can find are i337ucuamdl and i337ucuamdb.
Click to expand...
Click to collapse
yup yu can ...stock rom can b flshed at any tym yu want except wen the mobile has hard bricked
hit thanks rather then typing bro
siva aggzz said:
yup yu can ...stock rom can b flshed at any tym yu want except wen the mobile has hard bricked
hit thanks rather then typing bro
Click to expand...
Click to collapse
Is there a version or a download you recommend I use? I have I337UCUAMDB that is a .tar.md5 file, but when I use Odin to flash it, it gives an Aboot warning then fail about 2 seconds after I start it. How can I fix that? Do I need to be rooted or not before I flash an update, or does it matter?
steven2k7 said:
I have a Galaxy S4 from AT&T. I got it a few months ago, rooted it a few weeks after I got it. Randomly about a week ago, when I would make or receive a phone call, I could not hear the phone ringing, couldn't hear the person talking and they couldn't hear me. The only two ways I found it would work is if I booted into safe mode or I was connected to my cars bluetooth. I have no idea what caused it and I haven't messed with anything (like installing apps or changing settings) anywhere around the time it happened. I did many factory resets and hard key resets but nothing fixed it. I saw I had an OTA update so I did that (which I now realize was a big no-no -_-).
Since I did the OTA update while still rooted, that seems to have messed up my root. I seem to be both rooted and not rooted. So in trying to fix my first problem, I created the second problem. To solve both of these, I've been trying to install a fresh stock ROM onto the phone (to nothing but failure). I was trying to remove the root and put it back to stock incase I had to send it in for repairs. I found a few guides/posts from other people who did the OTA update while rooted but I couldn't seem to get it to work. It mostly consisted of re-rooting the phone, then un-rooting it but I could never get the phone to actually show that it was rooted.
(I just tested the phone part of my phone to see if it was working. Called it, and I could hear and be heard fine. Hung up, waited a few minutes and tried again and it didnt work at all. Both times were while it has been turned on for several minutes).
Does anyone know how I can get back to as close to stock as I can get so I can at least get the actual calling part of my phone fixed? Either see if something to do with the rooting is causing the problem or at least let me send it in to get it fixed, then I'll re-root it later.
Phone: AT&T Galaxy S4
Baseband: I337UCUAMF3 <I know the MF3 isn't good for rooting now
Model: Samsung SGH-I337
Android version: 4.2.2
Device Status: Custom
Thanks for any help!
Update: Managed to get rooted again, using this method: http://forum.xda-developers.com/showthread.php?t=2387577. Calling still doesn't work, and (forgot to mention this before) oddly, if I push numbers on the number pad on my phone, you can hear the tones on the phone I'm connected to. Just can't hear me.
Click to expand...
Click to collapse
No u dnt need to b rooted bro for flashing stock rom...
siva aggzz said:
No u dnt need to b rooted bro for flashing stock rom...
Click to expand...
Click to collapse
I can't get the stock roms to flash. I've tried I337UCUAMDB and I337UCUAMDL, used different USB ports and different computers and they all fail right away. Do you know where I can find a I337UCUAMF3 rom?
steven2k7 said:
I can't get the stock roms to flash. I've tried I337UCUAMDB and I337UCUAMDL, used different USB ports and different computers and they all fail right away. Do you know where I can find a I337UCUAMF3 rom?
Click to expand...
Click to collapse
Did you Tried the official Samsung firmware site?
http://www.sammobile.com/firmwares/
Fantassy123 said:
Did you Tried the official Samsung firmware site?
http://www.sammobile.com/firmwares/
Click to expand...
Click to collapse
Yeah, its not listed there, just two older ones that I can't get to work on my device.
Edit: Just realized my device isn't showing that its custom now. When I boot, I have the normal 'Samsung Galaxy S4' splash screen and in about device, the secure boot status is Samsung. I think I got that somehow with GooManager. Still rooted though as far as I can tell. Tested the phone calling again and seems it only works when my S4 is on speaker phone. I may try and just call samsung tomorrow and see if they will ship me a new one.
Well, I solved the problem. Kinda. I called AT&T warranty support (1-800-801-1101), talked to a guy and ran him through everything I've done. He tried a few things on his end, asked around to see if anyone else had heard of a similar problem (no one had), and they are sending me a replacement and I send the old one back.
I got the S4 back when it first came out, and messed around with some CM ROMs and other custom ROMs that worked fairly well. The big killers for me though were bluetooth audio not working, not being able to use headphone microphones, and the proximity sensor being all weird. So I reverted to stock but kept root, and eventually upgraded to MJ7 while keeping root. When I boot I still get the 'Samsung Custom' bootscreen.
I've never been happy with Touchwiz, and have all of the Samsung features turned off. The stock messaging app is really the thing that bugs the hell out of me, since it takes forever to get messages (sometimes up to an hour, while Handcent will get them right away), and I love my Nexus 7 experience. I'd really like to get as close to a 'Google' phone as possible, but I'm currently stuck on Verizon.
I've tried using GooManager to download the recovery managers again, but it's having problems with 404 errors downloading the scripts. I tried ROM Manager and it says it installs ClockworkMod (6.0.44 in fact), but it refuses to boot into recovery mode. Most of the tools I'm finding are not for MJ7, so I'm kind of hesitant to solutions that aren't for my current version. Since I can't make any backups without being able to boot into a proper recovery mode, that's another kind of notch against using most of the guides.
I don't mind the actual process of doing the work, I'm just not sure where to go from here. What are my options?
dragonmantank said:
I got the S4 back when it first came out, and messed around with some CM ROMs and other custom ROMs that worked fairly well. The big killers for me though were bluetooth audio not working, not being able to use headphone microphones, and the proximity sensor being all weird. So I reverted to stock but kept root, and eventually upgraded to MJ7 while keeping root. When I boot I still get the 'Samsung Custom' bootscreen.
I've never been happy with Touchwiz, and have all of the Samsung features turned off. The stock messaging app is really the thing that bugs the hell out of me, since it takes forever to get messages (sometimes up to an hour, while Handcent will get them right away), and I love my Nexus 7 experience. I'd really like to get as close to a 'Google' phone as possible, but I'm currently stuck on Verizon.
I've tried using GooManager to download the recovery managers again, but it's having problems with 404 errors downloading the scripts. I tried ROM Manager and it says it installs ClockworkMod (6.0.44 in fact), but it refuses to boot into recovery mode. Most of the tools I'm finding are not for MJ7, so I'm kind of hesitant to solutions that aren't for my current version. Since I can't make any backups without being able to boot into a proper recovery mode, that's another kind of notch against using most of the guides.
I don't mind the actual process of doing the work, I'm just not sure where to go from here. What are my options?
Click to expand...
Click to collapse
Well unfortunately for you you're on MJ7 which means your only options right now are rooting and Xposed. Other than that though, there's really nothing else you can do at the moment. If you were on ME7 or MI1 still you could at least run Safestrap, but even then you would be limited to Touchwiz based roms. Unless you're willing to go on the hunt for an MDK S4 you'll just have to deal with your limited options for now. Oh and before you ask, there is absolutely no way to revert back to earlier firmwares. Once you update, you're stuck.
Crawshayi said:
Well unfortunately for you you're on MJ7 which means your only options right now are rooting and Xposed. Other than that though, there's really nothing else you can do at the moment. If you were on ME7 or MI1 still you could at least run Safestrap, but even then you would be limited to Touchwiz based roms. Unless you're willing to go on the hunt for an MDK S4 you'll just have to deal with your limited options for now. Oh and before you ask, there is absolutely no way to revert back to earlier firmwares. Once you update, you're stuck.
Click to expand...
Click to collapse
Yeah, I know I couldn't revert the firmware to something earlier. Is it possible to revert to stock even? At this point I think I just want to revert it and sell this phone off and get something else. I don't care about KNOX status, just getting it back to stock so that whomever buys it won't keep getting security notifications.
dragonmantank said:
Yeah, I know I couldn't revert the firmware to something earlier. Is it possible to revert to stock even? At this point I think I just want to revert it and sell this phone off and get something else. I don't care about KNOX status, just getting it back to stock so that whomever buys it won't keep getting security notifications.
Click to expand...
Click to collapse
Yes I believe it's possible, I found this thread that gives you an Odin image to flash: http://forum.xda-developers.com/showthread.php?t=2507217
The security notification was actually fixed and supposedly an update was pushed out, but maybe yours didn't grab the update properly? I'm not sure, but that Odin image should get you back to factory stock. If I were you I would get an HTC One if you can live with not having a removable battery and sd card.
Awesome, thank you very much.
I'm re-flashing today take it back. I'll have a look at the HTC One, since it wasn't out when I got my S4. I know that (at the time) the S4 was the only Android phone I had found, with the One a close second but not available. I would really love a Google phone, but I get the feeling that will probably never happen on VZW.
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.