Related
Hi everyone, long time reader, first time poster.
First of all, i want to let you all know how i appreciate all the hard work you guys do on here. i was able to get all the info i needed to get my ATT n7105 back to stock after running CM 10.2 for the last year on it.
Back on topic...i have an S4 i337 running 4.3 MK2. when i first flashed it, for the longest time i couldnt figure out why i couldnt get signal or wifi, and found out needed to flash the MK2 modem firmware also (thanks for the info on that also). now the issue i am having is that now the phone has no sound at all, tried playing music, recieving a call (which makes the phone go total bonkers too), or even the beep it makes when adjusting the volume. I have tried searching for info on sound issues, but that was one thing i was unsuccessful with.
when i first got the phone, it had 4.2.2 (not sure of the firmware) and wanted to unlock it to use any carrier rather than just ATT. the only way of unlocking it, rather than getting an unlock code, was to go into service mode, and navigate through some menus, but i read that with 4.2.2, i could not, so i done an /ota update, which brought me straight to 4.4.3. after the unpdate, tried doing the service mode again, and had no luck, so tried downgrading to 43].3, than went to hell trying to get it working, untill coming across these forums, and got it working again with 4.3 MK2, but as mentioned, with no sound.
Any advice on what to try?
Thanks in advance.
RTyper56 said:
Hi everyone, long time reader, first time poster.
First of all, i want to let you all know how i appreciate all the hard work you guys do on here. i was able to get all the info i needed to get my ATT n7105 back to stock after running CM 10.2 for the last year on it.
Back on topic...i have an S4 i337 running 4.3 MK2. when i first flashed it, for the longest time i couldnt figure out why i couldnt get signal or wifi, and found out needed to flash the MK2 modem firmware also (thanks for the info on that also). now the issue i am having is that now the phone has no sound at all, tried playing music, recieving a call (which makes the phone go total bonkers too), or even the beep it makes when adjusting the volume. I have tried searching for info on sound issues, but that was one thing i was unsuccessful with.
when i first got the phone, it had 4.2.2 (not sure of the firmware) and wanted to unlock it to use any carrier rather than just ATT. the only way of unlocking it, rather than getting an unlock code, was to go into service mode, and navigate through some menus, but i read that with 4.2.2, i could not, so i done an /ota update, which brought me straight to 4.4.3. after the unpdate, tried doing the service mode again, and had no luck, so tried downgrading to 43].3, than went to hell trying to get it working, untill coming across these forums, and got it working again with 4.3 MK2, but as mentioned, with no sound.
Any advice on what to try?
Thanks in advance.
Click to expand...
Click to collapse
You don't have sound or the ability to call because your bootloader and non-hlos don't match. You can get sound by flashing the NB1 or NC1 modems(including non-hlos.bin) but that will break your wifi which can be fixed by using bypasslkm.
Sure, ill give that a try.
What if i were to update it to 4.4.3? any certain modems required there?
muniz_ri said:
You don't have sound or the ability to call because your bootloader and non-hlos don't match. You can get sound by flashing the NB1 or NC1 modems(including non-hlos.bin) but that will break your wifi which can be fixed by using bypasslkm.
Click to expand...
Click to collapse
Whenever i tried flashing NB1 or NC1, i get an error saying "signature verification failed, then later on give an error "unknown path \sdcard1" after wiping data, then reboots. and when the phone rebooted, it goes through the first time setup after a wipe, and then checking the modem, and its still NK2.
I really would like to get it to the current version.
RTyper56 said:
Whenever i tried flashing NB1 or NC1, i get an error saying "signature verification failed, then later on give an error "unknown path \sdcard1" after wiping data, then reboots. and when the phone rebooted, it goes through the first time setup after a wipe, and then checking the modem, and its still NK2.
I really would like to get it to the current version.
Click to expand...
Click to collapse
Follow these instructions to get to Stock, Rooted NC1: http://forum.xda-developers.com/showpost.php?p=52167774&postcount=3
muniz_ri said:
Follow these instructions to get to Stock, Rooted NC1: http://forum.xda-developers.com/showpost.php?p=52167774&postcount=3
Click to expand...
Click to collapse
Awesome! thank you very much
With the instructions you provided, i was able to get my i337 in working order.
your assistance is greatly apreciated
Sorry if this belongs in the stupid question thread, I just have no idea what went wrong, or why I'm still having problems. I've had my S4 for a while now, and it's been rooted pretty much the entire time. I wasn't aware of the auto update when I first got the phone, so before I had a chance to root it, I was updated from MLD to MK2. This wasn't a problem because SafeRoot had recently been released. I was never really concerned with voiding my warranty, and up until recently, never had. I later upgraded to NB1/NC1 to test out some of the KitKat ROMs.
I've flashed dozens of different ROMs, and several different recovery apps. The worst thing to come from my tinkering was the "Custom" logo on boot. Never tripped Knox, never soft-bricked, etc... Until recently.
I was browsing around the
[INDEX]All things AT&T MK2, NB1, and NC1 (including ROMs) thread and found a few ROMs I hadn't tried before. I don't remember specifically which ROM it was, but it definitely had an Aroma installer. During the installation there was a warning that my warranty would be void. Having been warned about voiding my warranty in virtually every ROM thread, I didn't really think much of it. I did my usual flashing of the ROM, flashed the NC1 modules, then SuperSU 2.0 just in case. I've performed the same steps numerous times. Unfortunately this time when I rebooted, everything went haywire.
I got the unauthorized software message, Knox had been tripped, and I'm pretty sure I had the yellow triangle, along with everything else that comes with a semi-brick.
I don't remember all of the details because it's been a couple of weeks now, but I used Odin to get back to NB1 stock, and since then I've had trouble with sending/receiving texts, and sometimes calls. It's really strange because there is no indication that it's stopped sending or receiving. I have to reboot the phone several times per day in order to get the signal back. I know that when I originally restored to stock, I used the NB1 stock file for Odin, then flashed the NC1 update, rooted and installed ShoStock. I kept having data/mms connectivity problems, but wifi was never an issue, so I thought it may have been the NC1 modules or something. I've tried several different variations of ROMs, modules, APN settings, etc. but even with a full return to stock, I'm still losing the ability to send/receive texts at seemingly random times.
I guess my question is, could I have flashed a modem or something in Aroma that is still sticking around somehow, even after using Odin to get back to stock? One of the ROMs I flashed was for the i9505, and it seemed to run fine, the phone was identified as an i9505, but adjusting the APN settings allowed it to work properly on AT&T. IIRC, that was the ROM I was using prior to the issues (Echoe).
I'm currently on the stock NB1 ROM and haven't taken the OTA update yet because it didn't seem to help the last time. I have no idea if anyone here has any insight into why this is so sporadic, but it's driving me nuts so I'm asking for help before I toss it out the window My apologies if I've left out some info. I'll be happy to provide any details I can. I'm just at work and having to type this up in a bit of a hurry. Thanks for reading, and any suggestions you all may have.
EDIT: FULL STORY BELOW. SKIP TO SECOND REPLY FOR UPDATE!
900A, AT&T, WAS 4.4.4. I rooted my phone with towelroot by downgrading via ODIN then reflashing 4.4.4. I've had the phone for a year and wanted to experiment with some custom roms--specifically Twi5ted Lollipop. The version I found last night was V3. Anyways I followed the instructions of installing safestrap then attempting to create a partition to host the mod. Every time I tried to boot the partition I would wait 12 minutes with nothing but a black screen (I presume a bootloop.) After reading some posts here I found it requires a clean flash--not a dirty flash. So I used safestrap to backup, then I wiped it and installed the mod. Nothing--still black screen. I then attempted to restore the backup I saved--fails every time.
At this point being the noob I am, I started to get very concerned. I went into advanced wipe and for some reason selected 'system' and wiped it. After a reboot, it shows the Samsung logo, goes blank, vibrates then goes back to the Samsung logo. I went into the standard bootloader and attempted to restore to factory settings but there is nothing to restore of course cause I wiped everything.
I'm currently at work bored as heck cause my phone is wiped. I can still go into download mode thankfully. Should I have no problems flashing stock via ODIN when I get home on my lunch break? Which stock firmware should I flash for this phone?
Thanks!
Unfortunately my lunch break brought me no good news. I downloaded stock found here: http://forum.xda-developers.com/showthread.php?t=2714455
After I flashed all the files (Except BL) when it boots, it get's to the Samsung logo--freezes halfway through then goes blank with the blue LED light on. I waited 10 minutes just to see what it does with no luck.
Another thing I found was weird-why when I boot does it still say 'Custom' when I flashed the stock firmware?
I really hope I don't have to drop $650 on a new phone Any help would be incredibly appreciated. Thanks guys!
DETAILED INFO: KOT49H. 6900AUCU1ANCE
MODEL: SM-6900A UD
FCC ID : A3LSMG900A
GALAXY S5 AT&T
why didn't you also flash the bootloader?
mike-y said:
why didn't you also flash the bootloader?
Click to expand...
Click to collapse
AT&T bootloader is locked right? Regardless I tried flashing the bootloader as a last resort and ODIN failed. Figured it just confirmed what everyone else said that it's locked.
Is there a specific way I need to flash the files? Like one at a time?
Do I need to restore factory settings/delete cache THEN flash each? or vice versa?
Am I basically screwed since I have AT&T?
:crying::crying::crying::crying:
FIXED!
After flashing 4.4.2 several times and trying different things, I came across this thread which finally brought my phone back to life. Thanks XDA!!!
http://forum.xda-developers.com/att...w-to-unbrick-flash-to-stocknce-g900a-t3077652
I have a Verizon GS5 that has been towelrooted on 4.4.4 for close to 2 years. It's worked ok, but I've started seeing various issues that required a factory reset. Since I'm back to no settings, I was thinking updating the OS would be a good idea. I would like to move to either Lollipop or Mashmallow but it looks like the latter may be a problem with my phone (CID 11 and Verizon) while keeping Knox 0x0.
I'm having a problem following the guide that I've found here:
https://www.androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
bkenobi69 said:
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
Click to expand...
Click to collapse
Try to dial *#0808# in the stock phone application.
You should see a menu with several options.
Select "MTP+ADB" under USB settings and press "OK".
Then you'll be able to connect your phone via MTP or ADB to your PC.
If there's no menu, then (assuming you're rooted) open a good file browser (ES, Root Explorer or something) and open the file /efs/carrier/HiddenMenu (it's a simple text file) and replace OFF with ON there.
Save the changes and reboot the phone.
Now the menu should be operational.
Unfortunately, I already tried to update to 6.0.1 so this very helpful info is a little to late.
I followed all directions on the linked page above but didn't get things working. I repeated 2 or 3 times now and I'm clearly missing something. I can get through installing busybox, but then when I reset, it hangs at the samsung screen and just vibrates 3 times repeatedly. I'm going to have to figure this out tonight as I don't really have a backup phone.
bkenobi69 said:
Unfortunately, I already tried to update to 6.0.1 so this very helpful info is a little to late.
I followed all directions on the linked page above but didn't get things working. I repeated 2 or 3 times now and I'm clearly missing something. I can get through installing busybox, but then when I reset, it hangs at the samsung screen and just vibrates 3 times repeatedly. I'm going to have to figure this out tonight as I don't really have a backup phone.
Click to expand...
Click to collapse
Currently root is impossible for MM on G900V CID11.
Impossible means you cannot gain it now, most likely it's forever.
There's no internet site which can help.
You must choose: root on LP or unrooted MM.
You must decide if you want a stock ROM or something (TW-based) else too.
It's a good idea to flash and use a stock firmware for the time while you're thinking.
Interesting... I guess I must have been reading things wrong because I thought I could go to MM with root. I'll try going to Lollipop then but first I'm going to just flash back to JB 4.4.4.
I downloaded 4.4.4 from Samsung and was going to write it with Odin, but it says FAIL when I try to flash. I suspect I just tripped Knox...
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
I'll look around to find a guide, but if you have a suggestion, I'd certainly listen!
bkenobi69 said:
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
Click to expand...
Click to collapse
This means that you've upgraded your phone's firmware while experimenting.
Now you cannot directly flash 4.4.4 with Odin, you're limited to 5.0 (BOK3) and above.
Ok. I'll read the guides on the head of this list and see if I can find the right information.
FWIW, I was following the same how-to that most of the stickies point to and say is safe. I wonder how I got to a position that I'm in now when I did the same as recommended. Painiac's thread points to the same thing I did:
https://forum.xda-developers.com/ve...al/guide-painiacs-essential-guide-to-t3319848
I think I may have tried to flash a MM stock rom though when it got into a boot loop. I suspect that would be the issue.
Bootloop is not a problem in this case.
Just reboot to the recovery and perform a factory reset from there.
The phone will boot but the first boot will take 10-15 min.
bkenobi69 said:
I have a Verizon GS5 that has been towelrooted on 4.4.4 for close to 2 years. It's worked ok, but I've started seeing various issues that required a factory reset. Since I'm back to no settings, I was thinking updating the OS would be a good idea. I would like to move to either Lollipop or Mashmallow but it looks like the latter may be a problem with my phone (CID 11 and Verizon) while keeping Knox 0x0.
I'm having a problem following the guide that I've found here:
https://www.androidinfotech.com/2016/07/root-samsung-galaxy-s5-sm-g900v-verizon.html
The issue is that I can't get the phone to connect to my PC for Kies or ODIN. It fails to load the MTP driver for my GS5 but works fine with my wife's GS5. Hers is stock Lollipop or Marshmallow and mine is still on JB but is rooted.
I guess what I'm wondering is what my options are. Should I remove root so that I can hopefully connect to the PC to transfer the files over and updating? Or, is there something else I should try first? I haven't worked on many phones and I'm a little nervous about doing something irreversible at this point. I don't know that I need Knox at 0x0, but since I can't get back if I trip it, I'd rather not trip it.
Click to expand...
Click to collapse
Marshmallow can not be rooted on CID 11 devices. The Samsung drivers are found here: https://www.samsung.com/us/support/owners/product/galaxy-s5-verizon You can follow the 5.0 root guide here: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529 to downgrade to 5.0. If you want to downgrade past that to a version lower than 5.0, you will still have to follow that guide then follow the instructions here (I recommend you to follow the root guide for 5.0 above then skip steps 1 and 2 on this page): https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858 . You can find stock firmwares here: https://forum.xda-developers.com/showthread.php?t=2784880 (stock firmware, kernel, and modem files) and if you get bootlooped or bricked, just reflash the combination file from the root guide. If you want to root 4.4.4, follow the downgrade method using all of the NK2 files but the flash the NGC kernel, run through the setup, then use towelroot and flash the NK2 kernel after that. If you ever get stuck on the red Verizon screen, just pop the battery out and reboot.
That's about all anyone can do and a run down of everything.
Thank you for posting specific guides. I'll go back to step 1 and try again. The primary issue I have at this point isn't reading the guide and following directions, its finding the right guide to reduce the number of images I need to download. I'm on 1.5mbps DSL so d/l a 2GB file takes most of a day. I have several that don't appear useful at this point which means I've lost several days.
bkenobi69 said:
Thank you for posting specific guides. I'll go back to step 1 and try again. The primary issue I have at this point isn't reading the guide and following directions, its finding the right guide to reduce the number of images I need to download. I'm on 1.5mbps DSL so d/l a 2GB file takes most of a day. I have several that don't appear useful at this point which means I've lost several days.
Click to expand...
Click to collapse
Understandable, I can't believe it is 2018 and we still haven't invented a way to compress 1.7GB into 1.7MB archives to make life easy on low connections. How is battery life on 4.4.4 and which update of 4.4.4 are you on? I've been having an issue with my phone dropping a percent every 2 minutes on 5.0/6.0. It would be nice find a version to root along with excellent battery life.
The reason I was looking at updating was due to battery issues. I had the phone for around a week before I rooted it (a couple years ago). After rooting, I started seeing immediate battery issues. My wife has the same unrooted phone (currently on MM) and has never had the type of issues I have. I figured the issue was likely a bad kernel and was thinking I'd just update to something newer (LL or MM) to help. I assume a new battery would help since mine is 1-2 years old, but I swapped with my wife's phone and she still gets lots better performance. Once I get this back up, I'll probably buy a new battery for each phone.
So it appears that I must have upgraded the bootloader to a point where towelroot no longer works as was previously suggested. I believe then that I need to follow the second guide to be able to downgrade to a rootable Lollipop version:
https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858
I am downloading the PB1 rom and lolliroot and need to also get a system restore, kernel, and modem. As I said, my connection is terrible so it would be great if someone could suggest which version of restore I should go with. I was going to install Lollipop in the end (that was the original goal). I figured I'd just get OC4 since it's likely to have the least bugs and best performance. If that is a mistake and I should go with an earlier version of LL PLEASE throw it out there!
Ok, I tethered to my wife's phone and am burning her data (shhhh, don't tell her).
I grabbed all of the OC4 files, the PB1 rom, and lolliroot. I think I have everything I need so long as OC4 is a good place to end up.
bkenobi69 said:
The reason I was looking at updating was due to battery issues. I had the phone for around a week before I rooted it (a couple years ago). After rooting, I started seeing immediate battery issues. My wife has the same unrooted phone (currently on MM) and has never had the type of issues I have. I figured the issue was likely a bad kernel and was thinking I'd just update to something newer (LL or MM) to help. I assume a new battery would help since mine is 1-2 years old, but I swapped with my wife's phone and she still gets lots better performance. Once I get this back up, I'll probably buy a new battery for each phone.
So it appears that I must have upgraded the bootloader to a point where towelroot no longer works as was previously suggested. I believe then that I need to follow the second guide to be able to downgrade to a rootable Lollipop version:
https://forum.xda-developers.com/ve.../guide-downgrade-to-kk-nk2-ncg-mm-lp-t3686858
I am downloading the PB1 rom and lolliroot and need to also get a system restore, kernel, and modem. As I said, my connection is terrible so it would be great if someone could suggest which version of restore I should go with. I was going to install Lollipop in the end (that was the original goal). I figured I'd just get OC4 since it's likely to have the least bugs and best performance. If that is a mistake and I should go with an earlier version of LL PLEASE throw it out there!
Click to expand...
Click to collapse
Here are some files (that I been hunting for about an hour for). Just gonna reference this for future use and anyone who comes across this thread. http://rootjunkysdl.com/files/?dir=Galaxy S5
Nice find!
I have the phone up and running on stock PB1 currently. I'm going to let it sit to see what the battery is like prior to rooting. While I haven't gotten it hooked back up to my account yet nor do I have it rooted, I feel pretty confident now that I'm on the right track. Thanks!
Just to finish out this topic, I have not successfully completed attaining root on 5.0. I flashed PB1 to the phone and then followed this guide for installing KingRoot:
https://androidforums.com/threads/root-question.1120150/
I got the lolliroot files from here:
https://www.androidfilehost.com/?fid=312968873555011514
Thanks to all who offered help!
Qyuck question... I've got my phone working well bow, but there's one issue with apps I'm not sure how to address. I want to use Verizon Visual Voicemail but I can't find it on the Play store. I disabled updates so I wouldn't get the marshmallow update and break root. but, with updates turned off, VVM won't get pushed. Any suggestions?
I've got a verizon galaxy note 3, sm-n900v. I've tried lineage 17.1 and now havok (android 10 versions) twice each and it's always the same problem. I get voice and data going for the first week or so then it just stops working. I have no idea what's going on. It has lasted as long as two or three weeks but it always ends up the same. Then I have to flash stock lollipop (OF1) with odin to get my service back. Then I can go through the process, re-root, re-unlock bootloader, re-flash TWRP, re-install ROM and then the service works for another week. I'm still quite new at this, so I have no idea what's happening or how to prevent it. Any help is greatly appreciated.
Verizon forum ??