Wondering if this is just me having problems with these updates and keeping root. My first phone I only had for a couple of months. I was rooted on NF6 and updated to BNG3 through Mobile Odin pro, after which VoLTE disappeared and WiFi calling just stays grayed out on "enabling". Completely wiped the phone, re-installed stock software and still could not get these options to work or enable. T-Mobile replaced the phone.
I now have another phone, rooted and was on NF6 and was worried about updating to BNG3 due to what happened on my first phone. I got an update notice about BNG4 and decided to download the full .tar and update through Mobile Odin pro and then flash the firmware via PC Odin. Did that and now I cannot use WiFi calling again and VoLTE is gone from call settings once again.
Is anyone else having this issue, or does it seem like I am doing something wrong? Any help or responses would be helpful before I go back to T-Mobile again.
..
You are right, my initial information was not very detailed. I was writing in a hurry at the time. I did not notice these problems as I was out of state on business and calling over WiFi was not needed. I only use it at home as signal is not the greatest, and that is when I noticed the issue and from reading I could not find an issue relating to mine.
When I have updated, I have not cleared cache or so forth. I just used Mobile Odin with the stock .tar to get the latest update and inject root/superuser and that is pretty much it. I have after the fact, done a factory reset and PC Odin back to a stock state (no root, etc) and this has not fixed my issue with WiFi calling. I have seen other threads in regards to WiFi calling, however I have not seen anything that refers to my issue at hand after updating in the manner that I have.
Can you actually do a full backup while running a stock ROM? I have used other custom recoveries on other phones and completed backups that way but not on a stock rooted phone.
..
Cleared cache as recommended through recovery (no change). Used PC Odin to revert back to the stock .tar the phone came with (ANE6), as well as not having root. Also no change with the problem, still cannot use Wifi calling.
Something very interesting just happened. I got a notice from T-Mobile about an update after restoring to ANE6 and I let it download and now I'm on BNG3 and Wifi calling is working, just no root right now. I can take care of that later.
Thanks for you time with trying to help and giving good information.
legendindisguise said:
Cleared cache as recommended through recovery (no change). Used PC Odin to revert back to the stock .tar the phone came with (ANE6), as well as not having root. Also no change with the problem, still cannot use Wifi calling.
Something very interesting just happened. I got a notice from T-Mobile about an update after restoring to ANE6 and I let it download and now I'm on BNG3 and Wifi calling is working, just no root right now. I can take care of that later.
Thanks for you time with trying to help and giving good information.
Click to expand...
Click to collapse
It definitely seems like a problem with mobile odin pro.
How exactly have you gone about the update process with mobile Odin?
What I would do is simply follow the threads on here that explain in details what you need to do to update and keep root. The flashing process is what is preventing you from using those features. Something is definitely not being flashed properly and carrying over from the update.
elesbb said:
It definitely seems like a problem with mobile odin pro.
How exactly have you gone about the update process with mobile Odin?
What I would do is simply follow the threads on here that explain in details what you need to do to update and keep root. The flashing process is what is preventing you from using those features. Something is definitely not being flashed properly and carrying over from the update.
Click to expand...
Click to collapse
These are the steps that I went by: I used this method when going from NE6 to NF6 (worked great). When I did these same steps trying to update to NG3 or NG4 is when I had problems.
Download the NF6 Full Stock TAR
Extract the single *.tar.md5 file from the downloaded ZIP in step 1
Copy this extracted file (G900TUVU1BNF6_G900TTMB1BNF6_G900TUVU1BNF6_HOME.ta r.md5) to your sdcard (I used my external sdcard)
Throw down the $4.99 and purchase Chainfire's Mobile ODIN Pro from Play Store (link)
Open Mobile ODIN PRO and click 'OK' to the warning about bootloaders and grant it root access when prompted
Scroll down to 'Open file ...' and click it.
Here I was prompted for either 'Internal SD-card' or 'External SD-card'. Select which ever location you copied the TAR to in step 3
Now select the actual folder and file for the location of the TAR you copiend in step 3
You'll be presented with the list of partitions your TAR contains. Click 'OK'
Leave all partitions as-is and be sure to check/tick both 'Enable EverRoot' and 'Inject Superuser (SuperSU)'
Optionally, you may also check to wipe Dalvik and/or data & cache. <-- Not required, but I checked 'Wipe Dalvik cache' because it's harmless.
Click 'Flash firmware'
legendindisguise said:
These are the steps that I went by: I used this method when going from NE6 to NF6 (worked great). When I did these same steps trying to update to NG3 or NG4 is when I had problems.
Download the NF6 Full Stock TAR
Extract the single *.tar.md5 file from the downloaded ZIP in step 1
Copy this extracted file (G900TUVU1BNF6_G900TTMB1BNF6_G900TUVU1BNF6_HOME.ta r.md5) to your sdcard (I used my external sdcard)
Throw down the $4.99 and purchase Chainfire's Mobile ODIN Pro from Play Store (link)
Open Mobile ODIN PRO and click 'OK' to the warning about bootloaders and grant it root access when prompted
Scroll down to 'Open file ...' and click it.
Here I was prompted for either 'Internal SD-card' or 'External SD-card'. Select which ever location you copied the TAR to in step 3
Now select the actual folder and file for the location of the TAR you copiend in step 3
You'll be presented with the list of partitions your TAR contains. Click 'OK'
Leave all partitions as-is and be sure to check/tick both 'Enable EverRoot' and 'Inject Superuser (SuperSU)'
Optionally, you may also check to wipe Dalvik and/or data & cache. <-- Not required, but I checked 'Wipe Dalvik cache' because it's harmless.
Click 'Flash firmware'
Click to expand...
Click to collapse
I think that's right. It definitely seems like something isn't being flashed properly though preventing you from using WiFi calling. After you update, what does your baseband version say?
elesbb said:
I think that's right. It definitely seems like something isn't being flashed properly though preventing you from using WiFi calling. After you update, what does your baseband version say?
Click to expand...
Click to collapse
I'm not 100% right now, I believe that when I was using Mobile Odin to do the updates, the baseband was staying the same. On my last attempts I used Mobile Odin to update versions and then used PC Odin to update the firmware as so everything was the same.
The phone is working now since I restored back to NE6 and it connected with T-Mobile to do OTA updates and now on NG4. I might just use CF Auto Root and not worry about Knox.
legendindisguise said:
I'm not 100% right now, I believe that when I was using Mobile Odin to do the updates, the baseband was staying the same. On my last attempts I used Mobile Odin to update versions and then used PC Odin to update the firmware as so everything was the same.
The phone is working now since I restored back to NE6 and it connected with T-Mobile to do OTA updates and now on NG4. I might just use CF Auto Root and not worry about Knox.
Click to expand...
Click to collapse
You can flash just the modem using the PC Odin. I think that is why you weren't able to use WiFi calling and such when upgrading with just mobile odin.
elesbb said:
You can flash just the modem using the PC Odin. I think that is why you weren't able to use WiFi calling and such when upgrading with just mobile odin.
Click to expand...
Click to collapse
I understand that. But wouldn't PC Odin the firmware include the modem when flashing? I will try just doing the modem next and see how it goes. Thanks for the advice.
legendindisguise said:
I understand that. But wouldn't PC Odin the firmware include the modem when flashing? I will try just doing the modem next and see how it goes. Thanks for the advice.
Click to expand...
Click to collapse
It does include the modem, however, they don't always get applied. I know you need to boot to stock recovery after flashing the modem, and the recovery does something, then you can reboot and it should be applied. But I am 99 percent confident that is why those things weren't working for you.
elesbb said:
It does include the modem, however, they don't always get applied. I know you need to boot to stock recovery after flashing the modem, and the recovery does something, then you can reboot and it should be applied. But I am 99 percent confident that is why those things weren't working for you.
Click to expand...
Click to collapse
Cool, thanks for the info and help. I will try flashing tonight and see how it goes and report back.
I appreciate both of you trying to help. I do try to read as much as possible before posting and cluttering the forums, but I could not figure this one out.
Cheers
elesbb said:
It does include the modem, however, they don't always get applied. I know you need to boot to stock recovery after flashing the modem, and the recovery does something, then you can reboot and it should be applied. But I am 99 percent confident that is why those things weren't working for you.
Click to expand...
Click to collapse
THANK YOU! That was the issue. Flashing the modem individually and now everything is working as it should. I owe you a beer my friend.
Thanks again.
legendindisguise said:
THANK YOU! That was the issue. Flashing the modem individually and now everything is working as it should. I owe you a beer my friend.
Thanks again.
Click to expand...
Click to collapse
I don't drink, but I will definitely take a starbucks or Cinnabon xD Haha glad you got it all resolved! That's what xda is for my friend
heya Legend,
I just had the same thing happen to me today when i ran pc odin to upgrade to NH5. I previously was stock rooted with NG3 and everything worked fine. Ran the firmware, rebooted to download and then installed bootloader. wifi calling was sitting at Greyed out saying enabling. never would turn on. installed TWRP 2.8 to wipe cache and dalvik and also ran a fix permissions. at that point phone wouldnt reboot, sat at Galaxy s5 splash screen. pulled battery, went back and tried to wipe again. still hung at splash. so i downgraded back to NG3 doing firmware, then bootloader. now phone boots fine but wifi calling still will not turn on. Which sucks because i just got my personal Cellspot up and runnin yesterday.
Can you tell me exactly what you did to get your wifi calling running again? or anyone else have any ideas/thoughts?
Thanks in advance
erider
erider said:
heya Legend,
I just had the same thing happen to me today when i ran pc odin to upgrade to NH5. I previously was stock rooted with NG3 and everything worked fine. Ran the firmware, rebooted to download and then installed bootloader. wifi calling was sitting at Greyed out saying enabling. never would turn on. installed TWRP 2.8 to wipe cache and dalvik and also ran a fix permissions. at that point phone wouldnt reboot, sat at Galaxy s5 splash screen. pulled battery, went back and tried to wipe again. still hung at splash. so i downgraded back to NG3 doing firmware, then bootloader. now phone boots fine but wifi calling still will not turn on. Which sucks because i just got my personal Cellspot up and runnin yesterday.
Can you tell me exactly what you did to get your wifi calling running again? or anyone else have any ideas/thoughts?
Thanks in advance
erider
Click to expand...
Click to collapse
I used PC Odin to just install the modem. Technically the firmware flash should load the modem but it didn't work for me.
This is what was recommended to me and it fixed the problem.
Damn, that did not work for me. tried flashing a few different modems too.
legendindisguise said:
I used PC Odin to just install the modem. Technically the firmware flash should load the modem but it didn't work for me.
This is what was recommended to me and it fixed the problem.
Click to expand...
Click to collapse
erider said:
Damn, that did not work for me. tried flashing a few different modems too.
Click to expand...
Click to collapse
When you flashed the modems are you sure they actually installed? A lot of people are having problems with getting modems to stick when flashed. You have to pull the battery for several seconds before you boot into download mode then flash the modem, and after it boot go to your about device screen to make sure you have the new modem.
gspears said:
When you flashed the modems are you sure they actually installed? A lot of people are having problems with getting modems to stick when flashed. You have to pull the battery for several seconds before you boot into download mode then flash the modem, and after it boot go to your about device screen to make sure you have the new modem.
Click to expand...
Click to collapse
Yeah i got into the habit of pulling battery every time i've flashed modems on this phone just for that reason. :/
Related
Hi Guys,
Sorry to bother you with this, but I'm out of ideas...
I decided to root my i9100 using this guide9.
As I was doing this, the recovery rom would reboot when using the volume buttons to navigate (only on the first "page") - This was easily worked around by using the touchscreen, but now I'm wondering if this was the start of my issues...
I applied the SU busy box installer, and got root. I installed rom manager, and noticed that it seemed to lock up when doing certain things. I put this down to CWM saying there was no official mod for the i9100.
The next day I decided to try and install a CM10.1 nightly, so I took a backup, wiped cache and data, and applied the rom and gapps.
When I rebooted, the phone wouldn't finished booting, it just sat at the initial logo screen.
After that, I tried following this recovery guide but the odin flash failed at around 80% (I retried and the same happened again).
Since then I've had difficulty getting in to recovery mode. I've tried flashing various stock roms with odin, and trying to restore with Kies.
In Kies I get as far as it conencting to the phone in download mode, but it pops up a "notice" in a foreign language - presumably Korean (and I can't copy the text to even attempt a google translation).
I tried flashing Siyah-s2-v5.0.1 to get a different recovery - that seemed to have a garbled progress bar, before hanging when I tried to wipe /data again.
When I use odin to flash a stock rom - is it supposed to restore absolutely everything? I'm not sure how I'm still getting problems if this is the case. Any ideas on what to try next?
(The current stock rom I'm try ing to use is this one)
Let me know if I'm missing any info, and thanks in advance for any help.
Using rom manager would have been the start of your problems-not the temp cwm recovery in the rooting guide.
If you can boot into download mode then I would download LP7 stock rom, disable kies and flash that with Odin.
{go back to your iphone since you are an android noob}
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Silly Billy said:
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Click to expand...
Click to collapse
I9100 right?
Try this:
- Download this ROM.
- Kies installed? uninstall it, re install it. Close it all up with Task manager (3 or 4 applications running).
- Flash ROM via Odin (CSC, MODEM, PHONE).
- If that doesn't fly, try another usb port & usb cable. Another PC would also be recommended.
- Repeat the process.
- Still no luck? try flashing a previous siyah version.
- No go? repeat all the above.
- Let us know how you did.
gastonw;37017081- Download this ROM.[/QUOTE said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
As a matter of interest, how far did you go with Phistachios repair guide.
{go back to your iphone since you are an android noob}
Silly Billy said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
Focus on getting a ROM to boot.
That ROM will install stock recovery.
gastonw said:
Let us know how you did.
Click to expand...
Click to collapse
For some reason, I can't get Odin to flash that rom - it just hands for a while at the start of data.img, before saying "Complete(Write) operation failed."
There a .pit file in the archive, although the link says not to repartition (so I didn't).
Some roms seem to get written, some don't, I'm not sure why...
theunderling said:
As a matter of interest, how far did you go with Phistachios repair guide.
Click to expand...
Click to collapse
Odin failed about 80% through flashing (step 4, after taking the ICS steps). I tried flashing the kernel afterwards, which flashed, but didn't help with my boot issues.
gastonw said:
Focus on getting a ROM to boot.
That ROM will install stock recovery.
Click to expand...
Click to collapse
Of course, I was just trying to get a better understanding of how things work - I'd settle for anything booting right now.
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
theunderling said:
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
Click to expand...
Click to collapse
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
gastonw said:
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
Click to expand...
Click to collapse
I guess I'll keep at it then.
I'd tried another cable with kies shut down. Just tried a different machine, and flashed the ROM you suggested with heimdall. It flashed without complaining (unlike odin), but I'm still getting a boot loop.
Looking at the initial recovery guide I was following - I suspect that I might've flashed the bootloader (the guide shows in bold which file goes in which box, so I probably loaded them all). Maybe this is the source of my troubles...
I also noticed that heimdall can pull data from the phone too - if I can pull and mount these, am I likely to find any useful log files?
For completeness (and anyone else who finds themselves with the same issue): It seems I hit the EMMC brick bug, which rendered some of my EMMC storage unusable.
This helpful chap came up with a workaround to partition around the dead space. (Please read the post carefully and make sure this really is your problem before flashing!)
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Sent from the little guy
gastonw said:
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Click to expand...
Click to collapse
Yes, that's right. IIRC, I flashed a working recovery with Odin, then did most of the work from adb shell.
I got my device back to life for the most part. I get the occasional hang but haven't investigated much (have since bought a Nexus 4, so not using the S2 so much).
Just thought I'd share for the next poor soul who has the same problem
I'm trying to return to stock on my Verizon Note 2. I'm currently on AOKP 4.2.2 and have TWRP. I tried to use the Odin method shown by Adam but my phone is not being seen via USB. I've tried to uninstall all drivers and reinstall. Tried again by using Kies as suggested by many.
Can I return to stock just by using TWRP? Are there steps or a walk through on how to do this? Links? I'm thinking I could go into TWRP, wipe the cache, delvik cache, and then factory reset. Then install, "flash" a update.zip and return to stock. Would this work or get stuck?
Also, not sure where to get the update.zip I'd need. I have the OTA stock downloaded from Adam tutorial...not the "alternate" but it's only one file. Would I just zip that, rename to update.zip and try to flash?
Please help!! Again I'm unable to do this through usb plug in so I really need another route.
Thank you in advance for any help!
Do not try renaming the file and flashing. Nothing good will come of that.
Not sure if you looked through this thread, but this might have different info for you.
http://forum.xda-developers.com/showthread.php?p=35265728
BoostedB18C said:
Do not try renaming the file and flashing. Nothing good will come of that.
Not sure if you looked through this thread, but this might have different info for you.
http://forum.xda-developers.com/showthread.php?p=35265728
Click to expand...
Click to collapse
I read through that one too. Tried all of that. ODIN will not work. My phone is not being detected through USB. Again i've tried all the reinstalls of the drivers etc.... Tried different original cords. nothing.
I need a way to return to stock through my device. Maybe load to the external sd and flash. Can this be done?
Not sure what file to flash though.
If odin isn't seeing your phone then something isnt installed properly. Probably drivers. Im not too sure about it because the only time I used odin was when I first rooted and I haven't touched it since.
The only option I have heard of for doing it from the phone is mobile odin. I dont know much about it, never tried it. Here's the link for it
This is the free lite version that requires more work on your part
http://forum.xda-developers.com/showthread.php?p=19375402
This is the paid version from the play store and is supposed to be much simpler
https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro
hidden-one said:
I'm trying to return to stock on my Verizon Note 2. I'm currently on AOKP 4.2.2 and have TWRP. I tried to use the Odin method shown by Adam but my phone is not being seen via USB. I've tried to uninstall all drivers and reinstall. Tried again by using Kies as suggested by many.
Can I return to stock just by using TWRP? Are there steps or a walk through on how to do this? Links? I'm thinking I could go into TWRP, wipe the cache, delvik cache, and then factory reset. Then install, "flash" a update.zip and return to stock. Would this work or get stuck?
Also, not sure where to get the update.zip I'd need. I have the OTA stock downloaded from Adam tutorial...not the "alternate" but it's only one file. Would I just zip that, rename to update.zip and try to flash?
Please help!! Again I'm unable to do this through usb plug in so I really need another route.
Thank you in advance for any help!
Click to expand...
Click to collapse
Are u sure usb debugging is on?, or try going back to a tw rom before using odin, i also read that kies has to be removed from comuter, and phone before trying this, i had problem originally, manually installed drivers, and went to device manager and checked operation, you also have to be in odin mode on phone( power,home,down at same time, as that way it is in download mode.
Sent from my SCH-I605 using XDA Premium HD app
Chance77 said:
Are u sure usb debugging is on?, or try going back to a tw rom before using odin, i also read that kies has to be removed from comuter, and phone before trying this, i had problem originally, manually installed drivers, and went to device manager and checked operation, you also have to be in odin mode on phone( power,home,down at same time, as that way it is in download mode.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
Tried all of this as well. I installed kies and tried that route as some were saying the drivers may work through that method. They didn't so I tried uninstalling. I was in DL "odin" mode when trying to run odin also.
Just curious, why are you trying to go back to stock?
BoostedB18C said:
Just curious, why are you trying to go back to stock?
Click to expand...
Click to collapse
My phone was a trade off for a iPhone 5.. Best move ever but the last owner had somewhat messed up the phone modding it. I did a full wipe and the previous owner had never done any backups. I wanted to start fresh. All that being said I wanted to start back fresh at stock and then do any modding that I preferred from a new state.
I just flashed MeanBean after reading back through the posts to my question. I realized I had not tried using odin while on a TW based ROM.
I'll see if this helps.
BoostedB18C said:
If odin isn't seeing your phone then something isnt installed properly. Probably drivers. Im not too sure about it because the only time I used odin was when I first rooted and I haven't touched it since.
Click to expand...
Click to collapse
I too am having issues with my Note II not being recognized by Odin on my PC. I know my drivers are installed and I have a good connection with my USB cable/port since when I plug in my phone when powered on, I can see the phone and card just fine. However, when going into Download mode and running Odin 3.07, Odin isn't seeing my phone.
I discovered this while looking into another situation from another thread. While I'm not currently attempting to return to stock and aren't overly concerned about returning to stock since I could probably do it with Mobile Odin if push comes to shove. I am concerned, however, that if I'm unable to use MO and my phone isn't being recognized by Odin from my PC then I might be up the proverbial creek with a paddle.
BoostedB18C said:
If odin isn't seeing your phone then something isnt installed properly. Probably drivers. Im not too sure about it because the only time I used odin was when I first rooted and I haven't touched it since.
The only option I have heard of for doing it from the phone is mobile odin. I dont know much about it, never tried it. Here's the link for it
This is the free lite version that requires more work on your part
http://forum.xda-developers.com/showthread.php?p=19375402
This is the paid version from the play store and is supposed to be much simpler
https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro
Click to expand...
Click to collapse
Mobile Odin Pro did the trick. It incorporated root saver so I didn't loose root when I returned to stock. Great advice!! Now I can start fresh and not have to worry about the mess I had from the trade.
Thanks again!
hidden-one said:
Mobile Odin Pro did the trick. It incorporated root saver so I didn't loose root when I returned to stock. Great advice!! Now I can start fresh and not have to worry about the mess I had from the trade.
Thanks again!
Click to expand...
Click to collapse
Glad it worked. And as an added bonus now I know if I do ever have problems and dont feel like spending the time to figure it out, I can just use mobile odin.
So, I was on 4.1.2 (running CM 11), and I downloaded the toltevzw_mj9_official_firmware1.tar.md5 and Odin 3.07.
I loaded the toltevzw_mj9_official_firmware1.tar.md5 into the PDA section of ODIN, and booted into download mode.
I ran Odin, and it seemed to work--restarted, Odin said it was successful, but now I have no cellular service and my Baseband Version is "unknown".
I've tried this multiple times, with different computers and different cords. I even flashed back to stock to get the modem back, then tried again. Same result.
Am I using ODIN wrong? Can anyone help me? Please? I have searched these forums, but every thread I found was unhelpful.
Thank you.
beans3660 said:
So, I was on 4.1.2 (running CM 11), and I downloaded the toltevzw_mj9_official_firmware1.tar.md5 and Odin 3.07.
I loaded the toltevzw_mj9_official_firmware1.tar.md5 into the PDA section of ODIN, and booted into download mode.
I ran Odin, and it seemed to work--restarted, Odin said it was successful, but now I have no cellular service and my Baseband Version is "unknown".
I've tried this multiple times, with different computers and different cords. I even flashed back to stock to get the modem back, then tried again. Same result.
Am I using ODIN wrong? Can anyone help me? Please? I have searched these forums, but every thread I found was unhelpful.
Thank you.
Click to expand...
Click to collapse
What I have found to help me and not run into this issue is flash back to stock, and re-root using the causal tool. Then I would install the lastest CWM or TWRP, install 4.3TW rom, boot up, reboot back into download mode, run odin package of the firmware (make sure you have a good md5, a bad download can affect it accepting the upgraded firmware), then wipe data,cache, dalvik and reboot. Then once rebooted confirm your modem was accepted and working, then get a GPS lock, then upgrade to CM11 if thats what you prefer.
bigmike35 said:
What I have found to help me and not run into this issue is flash back to stock, and re-root using the causal tool. Then I would install the lastest CWM or TWRP, install 4.3TW rom, boot up, reboot back into download mode, run odin package of the firmware (make sure you have a good md5, a bad download can affect it accepting the upgraded firmware), then wipe data,cache, dalvik and reboot. Then once rebooted confirm your modem was accepted and working, then get a GPS lock, then upgrade to CM11 if thats what you prefer.
Click to expand...
Click to collapse
So I did most of this, installed Alliance Rom. Now, ODIN won't recognize my device when it is in download mode. It will recognize it when I boot up normally, however. Yet, as soon as I boot into download mode, nothing.
Why is this such a pain in the ass for me? I haven't seen anyone have this much trouble.
beans3660 said:
So I did most of this, installed Alliance Rom. Now, ODIN won't recognize my device when it is in download mode. It will recognize it when I boot up normally, however. Yet, as soon as I boot into download mode, nothing.
Why is this such a pain in the ass for me? I haven't seen anyone have this much trouble.
Click to expand...
Click to collapse
That is a common problem, no worries man.
You need to go into device manager and delete/uninstall the casual/Samsung driver. Look under android development, then droid style, a sticky thread which shows you to delete driver. When you do that, that should do the trick for you!
Thank you bigmike35, so much. Everything you said worked.
To anyone else with this problem, try installing a 4.3 rom first before the mJ9. I wasted hours and hours by not doing this.
beans3660 said:
Thank you bigmike35, so much. Everything you said worked.
To anyone else with this problem, try installing a 4.3 rom first before the mJ9. I wasted hours and hours by not doing this.
Click to expand...
Click to collapse
Can you post a Link to this 4.3 Rom? or even the Rom name? thanks
[Q&A] [ROM|NH7|KitKat|4.4.4] Galaxy Note fre3 Hybrid De[Odex] v2.2 -BeastMode Kernel-
Q&A for [ROM|NH7|KitKat|4.4.4] Galaxy Note fre3 Hybrid De[Odex] v2.2 -BeastMode Kernel-
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Lte issues
So I went back to 2.17 and the lte started working again. I even tried to install 2.2 like a new rom and it still gives me a dns error. So idk what to do. As a FYI I have gone to cdma and not lte and on 3g it works well but lte doesn't kick for some reason. I hope people on sprint can let me know of it works for them in there area. I am in nyc in Queens and it doesn't work anywhere in Queens but when I went back to 2.17 it worked like a charm.
My home Wifi connects and reconnects fine when I leave and come back home, but whenever I reboot I have to manually connect. The password is remembered, it just doesn't auto connect on boot. Is this a ROM problem or a known problem with 4.4.4? Either way, is there a fix for it?
Random Bootloops
First off, I truly appreciate all the work you do! Thanks!
I did a complete wipe of everything on my phone and installed the new rom, but I now also am having the same LTE issue listed above, alongside an extremely annoying boot loop which will happen randomly. The only way I've been able to fix it is by clearing my cache & dalvik multiple times and by fixing permissions in TWRP. If I can help in any way, please let me know. I'd hate to have to downgrade, because I love NH7.
sk8in.skyline said:
So I went back to 2.17 and the lte started working again. I even tried to install 2.2 like a new rom and it still gives me a dns error. So idk what to do. As a FYI I have gone to cdma and not lte and on 3g it works well but lte doesn't kick for some reason. I hope people on sprint can let me know of it works for them in there area. I am in nyc in Queens and it doesn't work anywhere in Queens but when I went back to 2.17 it worked like a charm.
Click to expand...
Click to collapse
zaphodx42 said:
First off, I truly appreciate all the work you do! Thanks!
I did a complete wipe of everything on my phone and installed the new rom, but I now also am having the same LTE issue listed above, alongside an extremely annoying boot loop which will happen randomly. The only way I've been able to fix it is by clearing my cache & dalvik multiple times and by fixing permissions in TWRP. If I can help in any way, please let me know. I'd hate to have to downgrade, because I love NH7.
Click to expand...
Click to collapse
Are you on the latest modem? NH7? and if so, have you updated profile/prl?
JimSmith94 said:
My home Wifi connects and reconnects fine when I leave and come back home, but whenever I reboot I have to manually connect. The password is remembered, it just doesn't auto connect on boot. Is this a ROM problem or a known problem with 4.4.4? Either way, is there a fix for it?
Click to expand...
Click to collapse
Hmm.......have you tried long pressing the connection to make sure 'auto join' is checked?
freeza said:
Hmm.......have you tried long pressing the connection to make sure 'auto join' is checked?
Click to expand...
Click to collapse
Yes, auto join is checked and it does reconnect if I leave home and come back. I just unchecked and rechecked it and rebooted. No difference, it still makes me manually connect the first time.
2.21 update hangs at splash screen
The 2.21 update hangs at the Sammy Splash screen for me
lte continued
freeza said:
Are you on the latest modem? NH7? and if so, have you updated profile/prl?
Hmm.......have you tried long pressing the connection to make sure 'auto join' is checked?
Click to expand...
Click to collapse
Yea I tried updating the profile and the pre my coma works and I get lte but it isn't connecting keeps giving me the lte logo but when I go check a website it gives me a dns error . It's only on 2.2 and 2.2.1 on 2.17 no issues
---------- Post added at 03:00 AM ---------- Previous post was at 02:29 AM ----------
Please post how to do that
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
Spark icon tweak please tell us more[email protected]
I'll post here so i don't clog up the main thread anymore.
The ROM is fully functional but i cannot send MMS messages (pictures or group text)
I updated to NH7, build number and bootloader updated to NH7
Installed 2.2
Updated to 2.21
Tried updating baseband but i cannot get it to stick but the phone functions fine minus the MMS.
Updated PRL, Profile
I'm not sure what's left to try.
itisagoodname said:
I'll post here so i don't clog up the main thread anymore.
The ROM is fully functional but i cannot send MMS messages (pictures or group text)
I updated to NH7, build number and bootloader updated to NH7
Installed 2.2
Updated to 2.21
Tried updating baseband but i cannot get it to stick but the phone functions fine minus the MMS.
Updated PRL, Profile
I'm not sure what's left to try.
Click to expand...
Click to collapse
How did you update to NH7? Whether or not you used NH7 Odin Tar or Freeza's flashable zip, you need to enter download mode from phone being completely powered off or it will not stick.
You cannot enter download mode simply by rebooting into it from running OS and have the update stick.
Sent from my SM-N900P using Tapatalk 2
rpenrod23 said:
How did you update to NH7? Whether or use NH7 Odin Tar or Freeza's flashable zip, you need to enter download mode from phone being completely powered off or it will not stick.
You cannot enter download mode simply by rebooting into it from running OS and have the update stick.
Sent from my SM-N900P using Tapatalk 2
Click to expand...
Click to collapse
Fully powered off, Odin 3.07 NH7 TAR from here: (http://forum.xda-developers.com/showthread.php?t=2522638)
Booted up okay, build number was NH7 and i loaded up stock recovery which read NH7. Baseband and software version never read NH7 though.
Used Odin and rooted with CF
Booted and checked SU
Used Odin to install TWRP
Installed ROM
camera does not record neither chrome or oem
Hi, I love this rom but video recording does not work and always says failed, any suggestions?
itisagoodname said:
Fully powered off, Odin 3.07 NH7 TAR from here: (http://forum.xda-developers.com/showthread.php?t=2522638)
Booted up okay, build number was NH7 and i loaded up stock recovery which read NH7. Baseband and software version never read NH7 though.
Used Odin and rooted with CF
Booted and checked SU
Used Odin to install TWRP
Installed ROM
Click to expand...
Click to collapse
After you Odin the Tar, immediately boot into stock recovery and do a factory reset.
Then boot into OS.
If that doesn't work, I would check MD5 of Tar d/l.
If that doesn't work, I'm out of ideas for you but maybe somebody else can chime in for you.
Good luck! :thumbup:
Sent from my SM-N900P using Tapatalk 2
rpenrod23 said:
After you Odin the Tar, immediately boot into stock recovery and do a factory reset.
Then boot into OS.
If that doesn't work, I would check MD5 of Tar d/l.
If that doesn't work, I'm out of ideas for you but maybe somebody else can chime in for you.
Good luck! :thumbup:
Sent from my SM-N900P using Tapatalk 2
Click to expand...
Click to collapse
Thank you, i'll try this as soon as i get home, i found one more source to try. Should this load the NH7 baseband as well or does that still need to be flashed separately?
itisagoodname said:
Thank you, i'll try this as soon as i get home, i found one more source to try. Should this load the NH7 baseband as well or does that still need to be flashed separately?
Click to expand...
Click to collapse
NH7 tar includes modem so no need
Sent from my SM-N900P using Tapatalk 2
Posted in the other thread but forgot here. Issue resolved. It looks like my Odin 3.07 did not like the tar file and did not flash the modem, only the system.
I used 3.09 which i found posted here as well as a link to a different tar file (ended up being the same tar file).
Flashed with 3.09 and it loaded perfectly.
install
I tried to install this Rom, but for some reason it boot looped on me. I installed it how I have done all the Roms.
1. advanced wipe everything except sd card
2. formatted data
3. rebooted back in recovery
4. Flashed Rom
That is the correct way right?
Help with install?
Are there instructions for installing this from stock 4.4? I've tried installing from recovery and it fails.
juts said:
Are there instructions for installing this from stock 4.4? I've tried installing from recovery and it fails.
Click to expand...
Click to collapse
What recovery are you using?
If WIFI calling disappears in settings
I've found that the WIFI calling disappears in settings and is not usable even though the icon shows at the top. Thanks to the tip about setting the call button in the call log from Dalek_Caan post #2306:
"And csc edit is in features.xml
<CscFeature_Contact_EnableCallButtonInList>TRUE</CscFeature_Contact_EnableCallButtonInList>"
I checked and the features.xml file had been renamed to features.xml.bak and a new features.xml was in place with most the settings removed. I renamed the files to have the original in place and rebooted. The WIFI calling was back and all the other settings. Just an observation that drove me a little nuts for a while. This only happened with the roar kernel I had no problems when running the calm kernel.
"Firmware Upgrade Encountered an Issue" "Device not responding" Samsung Kies
I tried to flash an Android 5.0 ROM earlier, and my phone was only booting to the stock recovery (Safestrap was installed but I did a factory reset). Now, if the phone was turned off by removing the battery, it won't turn on when I hold the power button, or attempt to go into download/recovery mode. Nothing happens. If I plug it in, I can use whatever button combinations as normal. However, I don't think I can get to recovery mode. Both volume down/power and volume down/power/home enter download mode to the phone. I tried to flash a stock ROM in Odin, but it failed. Otherwise, it shows a screen that says " Firmware Upgrade encountered an issue. Please select recovery mode in kies and try again" And when I open kies, it just says "connecting" for an extremely long time until it eventually says "Device not responding" and I can't do anything. What do I have to do to fix this? I can't find anything for this phone that has had this problem or knows how to fix it. I've tried a few different things so far but flashing nothing in odin has worked. Any help is appreciated, thanks in advance.
Bumping for others to hopefully see... I've still made no progress and am in the same situation and simply can't find what I need to do.
What build were you on before you started? What file are you trying to flash with Odin?
Jmick363 said:
I tried to flash an Android 5.0 ROM earlier, and my phone was only booting to the stock recovery (Safestrap was installed but I did a factory reset). Now, if the phone was turned off by removing the battery, it won't turn on when I hold the power button, or attempt to go into download/recovery mode. Nothing happens. If I plug it in, I can use whatever button combinations as normal. However, I don't think I can get to recovery mode. Both volume down/power and volume down/power/home enter download mode to the phone. I tried to flash a stock ROM in Odin, but it failed. Otherwise, it shows a screen that says " Firmware Upgrade encountered an issue. Please select recovery mode in kies and try again" And when I open kies, it just says "connecting" for an extremely long time until it eventually says "Device not responding" and I can't do anything. What do I have to do to fix this? I can't find anything for this phone that has had this problem or knows how to fix it. I've tried a few different things so far but flashing nothing in odin has worked. Any help is appreciated, thanks in advance.
Click to expand...
Click to collapse
Here's the issue: since you have safestrap installed that means you're on the new bootloader. We cannot install anything other than TW based roms from nothing newer than nc5 base. If you can get into download mode, you'll need to flash the full wipe nc5 tar file through Odin. That will get you back on stock and you can re-root from there.
Hightower24 said:
Here's the issue: since you have safestrap installed that means you're on the new bootloader. We cannot install anything other than TW based roms from nothing newer than nc5 base. If you can get into download mode, you'll need to flash the full wipe nc5 tar file through Odin. That will get you back on stock and you can re-root from there.
Click to expand...
Click to collapse
Crap. You're right. I completely forgot about that last night. I was getting frustrated with Hyperdrive because when I was trying to install version 20, the WiFi would never work no matter which modules.zip I flashed.
I got fed up and just wanted to flash something else and I did this without even thinking about it... I can get the phone into download mode, but when I try to flash this in odin, it fails.
I saw someone with the same screen as me with a Note 2 and someone said something about flashing a PIT file or something like that? I think I'm going to look into that next, hopefully I can find some useful links.
riker147 said:
What build were you on before you started? What file are you trying to flash with Odin?
Click to expand...
Click to collapse
Sorry I didn't see this post at first. The file I'm using in Odin is mentioned in the above post. Before I had done anything, I was successfully using Hyperdrive 17.something. I did a factory reset, flashed the Hyperdrive 20 rom, flashed the modules.zip (I used like 3 or 4 different ones and none of them got WiFi to work) and rebooted and let the phone sit for 10 minutes, and when I would try to toggle WiFi, it wouldn't work. To make things worse, every time, when I rebooted, SafeStrap wouldn't load. So I had to go back to the ROM and install Towelroot and root the phone again, then install safestrap and install the recovery again and then I could boot to it. But I could never get the WiFi to work a single time.
Jmick363 said:
Sorry I didn't see this post at first. The file I'm using in Odin is mentioned in the above post. Before I had done anything, I was successfully using Hyperdrive 17.something. I did a factory reset, flashed the Hyperdrive 20 rom, flashed the modules.zip (I used like 3 or 4 different ones and none of them got WiFi to work) and rebooted and let the phone sit for 10 minutes, and when I would try to toggle WiFi, it wouldn't work. To make things worse, every time, when I rebooted, SafeStrap wouldn't load. So I had to go back to the ROM and install Towelroot and root the phone again, then install safestrap and install the recovery again and then I could boot to it. But I could never get the WiFi to work a single time.
Click to expand...
Click to collapse
Use this wifi fix module. It works best for me:
https://www.androidfilehost.com/?fid=23487008491963696
Hightower24 said:
Use this wifi fix module. It works best for me:
https://www.androidfilehost.com/?fid=23487008491963696
Click to expand...
Click to collapse
Thanks for this, but right now I need to be more concerned with actually getting to Safestrap... or stock touchwiz for that matter. Hopefully this will work if I manage to fix the phone.
Jmick363 said:
Thanks for this, but right now I need to be more concerned with actually getting to Safestrap... or stock touchwiz for that matter. Hopefully this will work if I manage to fix the phone.
Click to expand...
Click to collapse
My bad. Here's a link to the tar files. I suggest using the full wipe nc5:
http://forum.xda-developers.com/showthread.php?t=2735172
Hightower24 said:
My bad. Here's a link to the tar files. I suggest using the full wipe nc5:
http://forum.xda-developers.com/showthread.php?t=2735172
Click to expand...
Click to collapse
Using the Full Wipe method on that link, I was able to resolve the problem and at least get back to a working phone. From here I'll use towelroot to root and install safestrap and then install hyperdrive 20 with those modules you linked. To be more specific for anyone reading years from now with the same problem as me, I used odin 1.85 (though many versions work) with the pit file provided from that link with "re=partition, auto reboot and f. reset time" checked in the options. At first, I was having some trouble, but I think it was because the phone had low battery. I plugged it in for a bit, booted it up, and am setting it up right now. Thanks for the help everyone, it's much appreciated. I very much hope that the modules you linked work for me, because if they don't, I have no idea what ROM to use.
I was reading a thread last night where someone listed all of the ROMS working with SafeStrap, but it was from like 2 years ago and almost all of the ROMs had been abandoned.... Is there a more updated list of options? Or just something to look for to make sure a ROM will work right away?
Jmick363 said:
Using the Full Wipe method on that link, I was able to resolve the problem and at least get back to a working phone. From here I'll use towelroot to root and install safestrap and then install hyperdrive 20 with those modules you linked. To be more specific for anyone reading years from now with the same problem as me, I used odin 1.85 (though many versions work) with the pit file provided from that link with "re=partition, auto reboot and f. reset time" checked in the options. At first, I was having some trouble, but I think it was because the phone had low battery. I plugged it in for a bit, booted it up, and am setting it up right now. Thanks for the help everyone, it's much appreciated. I very much hope that the modules you linked work for me, because if they don't, I have no idea what ROM to use.
I was reading a thread last night where someone listed all of the ROMS working with SafeStrap, but it was from like 2 years ago and almost all of the ROMs had been abandoned.... Is there a more updated list of options? Or just something to look for to make sure a ROM will work right away?
Click to expand...
Click to collapse
Hyperdrive and echoerom seem to be the most talked about. I'm running echoe v39.1
Hightower24 said:
Hyperdrive and echoerom seem to be the most talked about. I'm running echoe v39.1
Click to expand...
Click to collapse
So right now things aren't going as smoothly as I would've hoped.... The first time I flashed Hyperdrive and then that modules zip you linked, and the phone got stuck on the Samsung custom screen in some sort of loop. I reset it with odin and just the PDA from the link from before, and I then installed towelroot and safestrap again then flashed hyperdrive and modules and now I'm stuck on the hyperdrive red screen... It's just the boot animation and nothing else. When I take out the battery, the power button does nothing if the phone is not plugged in. When I plug the phone in and hold down the power button, it just shows an empty battery with a loading icon in the middle. I can't do anything else.... I'm going to reset it again now and maybe try installing this echoe rom.... Are you talking about this?
Jmick363 said:
I'm going to reset it again now and maybe try installing this echoe rom.... Are you talking about this?
Click to expand...
Click to collapse
Hightower24 said:
Hyperdrive and echoerom seem to be the most talked about. I'm running echoe v39.1
Click to expand...
Click to collapse
With EchoeRom, where do I find the signal bar fix? Is the wifi fix the thing you linked already? or is it separate from modules zip?
Jmick363 said:
With EchoeRom, where do I find the signal bar fix? Is the wifi fix the thing you linked already? or is it separate from modules zip?
Click to expand...
Click to collapse
Sorry! I had started this reply earlier in the morning then got busy with work. The link for the signal bar fix is in the OP from the forum you found by jds. It's down by the link for v26. I sent you the wifi fix that works for me. If you're going to use v39.1, you will need jrkruse's nk2 patch found here:
http://forum.xda-developers.com/showthread.php?t=2674280
The echoe site is here:
http://echoerom.com/roms/echoefull/s4/i9505/
Flash in this order:
Rom
Nk2 patch (not needed for v29/29.1)
Signal bar fix
WiFi fix
Updated supersu.zip (optional)
Be sure to verify the md5 of the downloads. Good luck!
Hightower24 said:
Sorry! I had started this reply earlier in the morning then got busy with work. The link for the signal bar fix is in the OP from the forum you found by jds. It's down by the link for v26. I sent you the wifi fix that works for me. If you're going to use v39.1, you will need jrkruse's nk2 patch found here:
http://forum.xda-developers.com/showthread.php?t=2674280
The echoe site is here:
http://echoerom.com/roms/echoefull/s4/i9505/
Flash in this order:
Rom
Nk2 patch (not needed for v29/29.1)
Signal bar fix
WiFi fix
Updated supersu.zip (optional)
Be sure to verify the md5 of the downloads. Good luck!
Click to expand...
Click to collapse
No need to apologize!! Your job isn't to monitor me, and I can't thank you enough for all the help. I'm going to give this a shot at some point today, hopefully it'll work. I'll comment back in the thread whatever happens... As you can probably tell, I typically have horrible luck with these things.
So I have had the same issue as the OP after trying to flash to a 5.0 ROM, but my issue is still ongoing, as when I try to flash the stock ROM from this link I get the error that it failed in Odin.
madhavok09 said:
So I have had the same issue as the OP after trying to flash to a 5.0 ROM, but my issue is still ongoing, as when I try to flash the stock ROM from this link I get the error that it failed in Odin.
Click to expand...
Click to collapse
Are you flashing the full wipe? Good download? Check MD5? Using the cable that came with the phone? Try a different USB port?
Sent from my NCC-1701 using Tapatalk.
riker147 said:
Are you flashing the full wipe? Good download? Check MD5? Using the cable that came with the phone? Try a different USB port?
Sent from my NCC-1701 using Tapatalk.
Click to expand...
Click to collapse
Well the OP said he did the wipe with that link I listed, and I would assume it's a good link. I am flashing the full wipe with the PIT file, using the cable that came with the phone, and I have tried using a different USB port. I have tried 3 different MD5 files as well and still have had no luck.
Edit (2:13 PM Eastern): Had the wrong file after some digging, and got the NC5 instead of the MK2. Phone is booting normally. Thanks for the help.