Related
Guys here is my problem. I tried to upgrade my Samsung N7105 to 4.3 via OTA and it got stucked on bootloop.
I tried to access recovery mode but it fails, only download mode.
What i did is I downloaded the official 4.3 firmware at SamMobile and flashed it with Odin 3.09
Based on Odin it is successful but im still stuck on bootloop and recovery mode cannot still be accessed.
Tried to root it also and installed CWM to recover. I was able to to access CWM
so i restored factory setting, wipe cache and dalvik cache but still the phone bootloops.
Any suggestions on how to resolve my problem?
iamjerbergerber said:
Guys here is my problem. I tried to upgrade my Samsung N7105 to 4.3 via OTA and it got stucked on bootloop.
I tried to access recovery mode but it fails, only download mode.
What i did is I downloaded the official 4.3 firmware at SamMobile and flashed it with Odin 3.09
Based on Odin it is successful but im still stuck on bootloop and recovery mode cannot still be accessed.
Tried to root it also and installed CWM to recover. I was able to to access CWM
so i restored factory setting, wipe cache and dalvik cache but still the phone bootloops.
Any suggestions on how to resolve my problem?
Click to expand...
Click to collapse
just to add, i think i tripped the knox warrant void. its value is now 1 what this means?
Simply flash philz v5.00.5 and it should solve it, here's the link: http://link.tapatalk.com/api/click?...rs.com&subid=c157297d1a1ff043255bfb18530caaa2
Hope it works
With Regards,
Overdub
Sent from my Galaxy Note II using Tapatalk
OverDub said:
Simply flash philz v5.00.5 and it should solve it, here's the link: http://link.tapatalk.com/api/click?...rs.com&subid=c157297d1a1ff043255bfb18530caaa2
Hope it works
With Regards,
Overdub
Sent from my Galaxy Note II using Tapatalk
Click to expand...
Click to collapse
Was able to access custom recovery upon flashing. conducted wipe data / factory reset and wipe dalvik cache but still bootlooping was experienced. Is my phone dead already and needs replacement?
After flashing the philz, try flashing a custom ROM and see if u will unstuck from the bootloop, try cm 10.2, it's very light and mostly bug free
Sent from my GT-N7100 using xda app-developers app
OverDub said:
After flashing the philz, try flashing a custom ROM and see if u will unstuck from the bootloop, try cm 10.2, it's very light and mostly bug free
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Now working cm10.2 but now my next problem is there is no signal. it appeared that imei value is null. how do i repair this? thanks!
By the way after successfully running on cm10.2 I tried to reflash again with stock firmware. bootloop again. i think i will be stuckon using custom roms for now. The only thing I need to address is the no mobile signal problem.
OK so the bootloop problem is done and don't worry there are a lot of amazing custom roms that are based on the stock one and even better features like the note 3 features, as for the imei, please tell me you did an nfs backup if you do, there are a lot of ways you can restore your nfs backup, if you don't have an nfs backup, I don't know what to do.
With Regards,
Overdub
Sent from my GT-N7100 using xda app-developers app
Not very clued up on losing baseband but it happened to me once when I used a different revovery version to restore a back up. Dr Ketan has written a guide on restoring baseband, he will be able to fix it
Sent from my GT-N7105 using XDA Premium 4 mobile app
Please keep us updated and if it is fixed hopefully, please show us what you did.
With Regards,
Overdub
Sent from my GT-N7100 using xda app-developers app
Still not working
OverDub said:
Please keep us updated and if it is fixed hopefully, please show us what you did.
With Regards,
Overdub
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Sorry was on vacation for a long time. I wasn't able to update this thread.
Problem right now is I forgot to back the EFS so when I flashed CM 10.2
There is no baseband and IMEI is null. Tried to flash n7105 modem but still it still doesn't work
Have read that I should flash stock firmware to fix baseband and IMEI but 4.3 firmwares makes my phone go on bootloop.
Should I wait for 4.4 update? I want my phone to make it usable again.
My phone right now is useless and works like an itouch hahaha
Any suggestions???
Need expert advise
iamjerbergerber said:
Sorry was on vacation for a long time. I wasn't able to update this thread.
Problem right now is I forgot to back the EFS so when I flashed CM 10.2
There is no baseband and IMEI is null. Tried to flash n7105 modem but still it still doesn't work
Have read that I should flash stock firmware to fix baseband and IMEI but 4.3 firmwares makes my phone go on bootloop.
Should I wait for 4.4 update? I want my phone to make it usable again.
My phone right now is useless and works like an itouch hahaha
Any suggestions???
Need expert advise
Click to expand...
Click to collapse
You may try Hurricane modem changer and experiment with various modem versions. It's a longshot but it may help. Try finding very old modem version and flash that.
Hurricane Modem Changer is that an application?
Where to get it? Also, will it there be a possibility that when I flash Official 4.4 kitkat (when released) on my n7105.
Bandwidth and IMEI will be restored? I'm leaning towards to come back to touch wiz though many of you guys might say that a custom rom might be better.
For one thing, the problem in my n7105 started when i upgraded to 4.3 via OTA
iamjerbergerber said:
Hurricane Modem Changer is that an application?
Where to get it? Also, will it there be a possibility that when I flash Official 4.4 kitkat (when released) on my n7105.
Bandwidth and IMEI will be restored? I'm leaning towards to come back to touch wiz though many of you guys might say that a custom rom might be better.
For one thing, the problem in my n7105 started when i upgraded to 4.3 via OTA
Click to expand...
Click to collapse
Look HERE. One of the downloads is Hurricane Modem Changer.
mat9v said:
Look HERE. One of the downloads is Hurricane Modem Changer.
Click to expand...
Click to collapse
Thanks will try. Aside from this. Where can I find old modem?
Will hurricane modem changer work if I used ditto note 3 rom?
iamjerbergerber said:
Thanks will try. Aside from this. Where can I find old modem?
Will hurricane modem changer work if I used ditto note 3 rom?
Click to expand...
Click to collapse
Hurricane contains some older modems along with new ones and yes it will work if you used DN3.
mat9v said:
Hurricane contains some older modems along with new ones and yes it will work if you used DN3.
Click to expand...
Click to collapse
Is the hurricane modem changer link you provided will work on n7105? tried to flash it but aroma installer tells its for n7100 international version
iamjerbergerber said:
Is the hurricane modem changer link you provided will work on n7105? tried to flash it but aroma installer tells its for n7100 international version
Click to expand...
Click to collapse
No, it's for N7100 only - the modems are completely different (3G vs LTE).
Please read the original post carefully before flashing, if the HC was not protected you could have lost network functions completely.
mat9v said:
No, it's for N7100 only - the modems are completely different (3G vs LTE).
Please read the original post carefully before flashing, if the HC was not protected you could have lost network functions completely.
Click to expand...
Click to collapse
Im using an n7105 model. Guess this will not work. Any other suggestions?
From what I understand, the quickest solution is to flash stock firmwares however, i'm quite disappointed that
almost all 4.3 firmwares from sam mobile doesn't work in my phone (always bootlooping)
A technician told me that I should wait for the 4.4 kitkat release, since it might work for my phone.
Now my problem is, I need to have the phone operational. so im willing to flash custom roms for the meantime
but the baseband problem is really testing my patience. hehe
iamjerbergerber said:
Im using an n7105 model. Guess this will not work. Any other suggestions?
From what I understand, the quickest solution is to flash stock firmwares however, i'm quite disappointed that
almost all 4.3 firmwares from sam mobile doesn't work in my phone (always bootlooping)
A technician told me that I should wait for the 4.4 kitkat release, since it might work for my phone.
Now my problem is, I need to have the phone operational. so im willing to flash custom roms for the meantime
but the baseband problem is really testing my patience. hehe
Click to expand...
Click to collapse
It's pretty strange really as stock firmwares are a complete set of bootloader/modem/system that should in theory work perfectly well together without any incompatibility problems. Have you ever tried to install one of them without sdcard and/or simcard installed, maybe you have some leftovers from previous system (Android secure directory) that causes bootloops, also did you completely clean internal sdcard prior to flashing, it may create the same problems as external sdcard.
mat9v said:
It's pretty strange really as stock firmwares are a complete set of bootloader/modem/system that should in theory work perfectly well together without any incompatibility problems. Have you ever tried to install one of them without sdcard and/or simcard installed, maybe you have some leftovers from previous system (Android secure directory) that causes bootloops, also did you completely clean internal sdcard prior to flashing, it may create the same problems as external sdcard.
Click to expand...
Click to collapse
im not sure if i cleaned the internal sdcard prior to flashing.
It started with the OTA update that failed then I tried to flash stock firmware via odin
do i have to do a pre-requisite before flashing it again? so you are suggesting to remove the simcard and external sd card prior to flashing?
I am having a weird issue with my S4 running any Rom past 4.2. When I make a call, the signal indicator changes to the circle with a line through it. The call stays connected, but no data transfer is possible. Any attempt to access the internet results in an error. But the call stays connected just fine. Once I end the call the signal eventually comes back and I can use the phone as normal. If I try to make a call before the signal comes back I get an error (even though I was just on the phone). Rebooting the phone seems to make the signal come back faster.
Any 4.2 rom does not have this issue.
Anyone have any ideas?
What baseband are you running?
Sent from my SGH-M919 using XDA Premium 4 mobile app
kriptik210 said:
what baseband are you running?
Sent from my sgh-m919 using xda premium 4 mobile app
Click to expand...
Click to collapse
m919uvuamdl
timekillerj said:
m919uvuamdl
Click to expand...
Click to collapse
You need to update it
Sent from my SGH-M919 using Tapatalk
Yeah, just found that I need M919UVUFNB4 apparently. Will try that and report back. Thanks.
Here is a good DL link if you have any problems.
http://www.androidfilehost.com/?fid=23329332407579299
Just ODIN from PC twice and you are good
Sent from my SGH-M919 using XDA Premium 4 mobile app
Somehow the new baseband has made things MUCH worse. The phone is completely unusable now. It is EXTREMELY laggy. no sounds from screen touches at all. It didn't even do the t-mobile jingle on boot. When I try to make a phone call, the other phone rings before the S4 leaves the "dialing" screen. Talking doesn't work, no voice gets through in either direction. I would never expect this from a modem flash.
I can confirm on the about screen the new baseband is M919UVUFNB4
I tried wiping the phone, thinking somehow it needed to "start fresh" with the new modem. That did not help. Then I tried reflashing Fenny's 4.4.2 Stock ROM (same rom I was running before). Nothing helps.
What the heck is going on?!?
timekillerj said:
Somehow the new baseband has made things MUCH worse. The phone is completely unusable now. It is EXTREMELY laggy. no sounds from screen touches at all. It didn't even do the t-mobile jingle on boot. When I try to make a phone call, the other phone rings before the S4 leaves the "dialing" screen. Talking doesn't work, no voice gets through in either direction. I would never expect this from a modem flash.
I can confirm on the about screen the new baseband is M919UVUFNB4
I tried wiping the phone, thinking somehow it needed to "start fresh" with the new modem. That did not help. Then I tried reflashing Fenny's 4.4.2 Stock ROM (same rom I was running before). Nothing helps.
What the heck is going on?!?
Click to expand...
Click to collapse
What all did you do?
Sent from my SGH-M919 using XDA Premium 4 mobile app
timekillerj said:
Somehow the new baseband has made things MUCH worse. The phone is completely unusable now. It is EXTREMELY laggy. no sounds from screen touches at all. It didn't even do the t-mobile jingle on boot. When I try to make a phone call, the other phone rings before the S4 leaves the "dialing" screen. Talking doesn't work, no voice gets through in either direction. I would never expect this from a modem flash.
I can confirm on the about screen the new baseband is M919UVUFNB4
I tried wiping the phone, thinking somehow it needed to "start fresh" with the new modem. That did not help. Then I tried reflashing Fenny's 4.4.2 Stock ROM (same rom I was running before). Nothing helps.
What the heck is going on?!?
Click to expand...
Click to collapse
Sounds like you installed the NB4 LTE modem as well. (NON-HLOS) i think is the name. You only need to instal the actual modem as the LTE modem will do exactly what you are experiencing
elesbb said:
Sounds like you installed the NB4 LTE modem as well. (NON-HLOS) i think is the name. You only need to instal the actual modem as the LTE modem will do exactly what you are experiencing
Click to expand...
Click to collapse
You are exactly right. The modem tarball I downloaded had both, so I flashed both (woops!). I just finally got myself sorted out. Had to flash back to factory 4.2, re-root, install TWRP, re-flash 4.4.2, then flash the modem.bin (several times before it took). But! All my problems are resolved.
Thanks for the help guys.
timekillerj said:
You are exactly right. The modem tarball I downloaded had both, so I flashed both (woops!). I just finally got myself sorted out. Had to flash back to factory 4.2, re-root, install TWRP, re-flash 4.4.2, then flash the modem.bin (several times before it took). But! All my problems are resolved.
Thanks for the help guys.
Click to expand...
Click to collapse
If you don't mind can you share which modem ad rom you flash?
How's battery and signal compared to 4.2.2 with MDL modem?
Thanks.
Sent from my SGH-M919 using Tapatalk 2
vlad2277 said:
If you don't mind can you share which modem ad rom you flash?
How's battery and signal compared to 4.2.2 with MDL modem?
Thanks.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Flashed the modem previously linked in this thread, and Fenny's 4.4.2 stock rooted rom. Can't really compare battery/signal because I just flashed it, and it's my wife's phone. She got it when I got the S5
Hi xda, I hope your Friday is going well.
EDIT: My calling problem was not fixed. I reflashed 4.4.2 NB4 Modem (twice to make sure it stuck) and the calling still does not work. Did something just completely fry when I had CM11 on this thing? Any ideas anybody? I don't even hear a dial tone if I am the one dialing out, the call still goes through though.
Everything below was my original post which has been resolved, didn't want to start a new thread though.
-----------------------------------------------------------------------------------------
TL;DR: My T-Mobile Samsung Galaxy S 4 (SGH-M919) is unable to boot stock rom, and I am unable to enter recovery. I get seandroid messages trying to do either. Fortunately, the phone can enter download mode. What do I need to do or flash to get this phone booting again? Thank you in advance for taking the time to read and help out.
Below is the long story with details:
1. The phone was given to me running stock Android/TouchWiz. Unfortunately, I do not know what version but I assume it was whatever was the latest version as of late April.
2. I rooted the phone using Odin and CF Auto Root.
3. I created a backup of this newly rooted stock rom.
4. I flashed Cyanogenmod 11
5. After a while I discovered that I could answer calls but I could not hear nor be heard during the call.
6. I restored to the stock rom using the backup I made in step 3.
7. The calling issue continued, so I figured I would just unroot and go back to like-new factory settings. This way I could take the phone in to be repaired or whatever.
8. Following this thread: http://forum.xda-developers.com/showthread.php?t=2336392, I attempted to flash k0nane's UVUAMDL Official Tar
9. Odin got stuck connecting to my device, I believe it was because I did not run Odin as admin. I pulled the battery and repeated this step while running Odin as admin.
10. The flash was successful, however during the phone's first boot it got stuck on the T-Mobile splash screen for about 30 minutes or so. I pulled the battery again.
11. Anytime I put the battery back in the phone, it will attempt to boot and hang at the T-Mobile screen, I believe this is a boot loop?
Looking online, people suggest going into recovery and wiping but I cannot enter recovery. I just get the seandroid not enforcing messages. I'm very hesitant to keep looking through the forums and trying things because I feel like I'm on the edge of bricking the phone if I haven't already.
I don't think the flash was successful because it wouldn't give you those messages, and you would need to flash either 4.3 or 4.4.2 not 4.2.2 (MDL) Try flashing a newer firmware version.. If it was updated to the newest then I would try 4.4.2
Sent from my SGH-M919 using Tapatalk
serio22 said:
I don't think the flash was successful because it wouldn't give you those messages, and you would need to flash either 4.3 or 4.4.2 not 4.2.2 (MDL) Try flashing a newer firmware version.. If it was updated to the newest then I would try 4.4.2
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Ok so I flashed the wrong rom then. I hate to ask but where could I find a 4.4.2 stock rom? I just found a rom I believe will work but the file is titled "M919UVUFNB4_M919TMBFNB4_TMB" not sure if this is 4.4.2 or newer?
You download the stock 4.4.2 ROM from sammobile:
http://www.sammobile.com/firmwares/
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
You download the stock 4.4.2 ROM from sammobile:
[link removed]
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is where I obtained the rom above that I wasn't sure was the newest.
I flashed this rom and everything worked, thank you both.
Any ideas on what happened with the phone call issue? My friend that gave me the phone said it was working just fine when she had it, so I assume somehow the rooting or CM11 screwed something up? Weirdly, calling through WiFi works just fine.
THVRSDAY said:
This is where I obtained the rom above that I wasn't sure was the newest.
I flashed this rom and everything worked, thank you both.
Any ideas on what happened with the phone call issue? My friend that gave me the phone said it was working just fine when she had it, so I assume somehow the rooting or CM11 screwed something up? Weirdly, calling through WiFi works just fine.
Click to expand...
Click to collapse
The only thing that can foul up your phone like that would be a bad cm flash or preflash, it's super important to read and read again, check the thread for support from members and resolutions to problems before you consider the build for your phone. Ask questions and double check everything before you take the plunge.
I assume that the calling problem is fixed, a corrupt modem may cause that and re flashing the modem will correct this.
Pp.
sent from my bluetooth controlled toaster that also takes pictures.
PanchoPlanet said:
The only thing that can foul up your phone like that would be a bad cm flash or preflash, it's super important to read and read again, check the thread for support from members and resolutions to problems before you consider the build for your phone. Ask questions and double check everything before you take the plunge.
I assume that the calling problem is fixed, a corrupt modem may cause that and re flashing the modem will correct this.
Pp.
sent from my bluetooth controlled toaster that also takes pictures.
Click to expand...
Click to collapse
The calling problem was not fixed. I reflashed 4.4.2 NB4 Modem (twice to make sure it stuck) and the calling still does not work. Did something just completely fry when I had CM11 on this thing? Any ideas anybody?
THVRSDAY said:
The calling problem was not fixed. I reflashed 4.4.2 NB4 Modem (twice to make sure it stuck) and the calling still does not work. Did something just completely fry when I had CM11 on this thing? Any ideas anybody?
Click to expand...
Click to collapse
Did you flash the NB4 firmware twice? Firmware, not modem
Sent from my SGH-M919 using Tapatalk
serio22 said:
Did you flash the NB4 firmware twice? Firmware, not modem
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
No, I only flashed the NB4 modem bin found here: http://forum.xda-developers.com/showthread.php?t=2678774. I need to flash the whole NB4 tar twice as well?
THVRSDAY said:
No, I only flashed the NB4 modem bin found here: http://forum.xda-developers.com/showthread.php?t=2678774. I need to flash the whole NB4 tar twice as well?
Click to expand...
Click to collapse
Well modem didn't work so try the firmware
Sent from my SGH-M919 using Tapatalk
serio22 said:
Well modem didn't work so try the firmware
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I flashed the NB4 tar from sammobile twice, calls still not working. I feel like I'm not flashing the correct thing or something.
Using the Android System Info app, every entry has something in it except for Radio. It just says "Radio: unknown". Does this have anything to do with anything?
THVRSDAY said:
I flashed the NB4 tar from sammobile twice, calls still not working. I feel like I'm not flashing the correct thing or something.
Using the Android System Info app, every entry has something in it except for Radio. It just says "Radio: unknown". Does this have anything to do with anything?
Click to expand...
Click to collapse
That is a problem.. How did you get this device?
Sent from my SGH-M919 using Tapatalk
serio22 said:
That is a problem.. How did you get this device?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
My friend gave the phone to me. She got an S5 and didn't want to bother with selling this S4 so she just gave it to me. It was completely pure and stock, with calls working. Something screwed up during the CM11 flash I guess.
WiFi calls still work, everything works except calls.
Maybe I'm doing something wrong? I flashed the sammobile NB4 tar twice via PDA in Odin as usual. For the modem, I flashed the modem bin via Phone in Odin twice. Thank you for your help, by the way.
New term for CM, "complicated maneuver" ,.
Reflashing firmware may do it. Can't hurt either.
Pp.
Sent from my SGH-M919 using XDA Premium 4 mobile app
THVRSDAY said:
My friend gave the phone to me. She got an S5 and didn't want to bother with selling this S4 so she just gave it to me. It was completely pure and stock, with calls working. Something screwed up during the CM11 flash I guess.
WiFi calls still work, everything works except calls.
Maybe I'm doing something wrong? I flashed the sammobile NB4 tar twice via PDA in Odin as usual. For the modem, I flashed the modem bin via Phone in Odin twice. Thank you for your help, by the way.
Click to expand...
Click to collapse
I think something definitely went wrong.. Try flashing this firmware, it flashes better for most people http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip after that, factory reset and if that still doesn't work then you have a bigger problem.. Good luck!
Sent from my SGH-M919 using Tapatalk
serio22 said:
I think something definitely went wrong.. Try flashing this firmware, it flashes better for most people http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip after that, factory reset and if that still doesn't work then you have a bigger problem.. Good luck!
Click to expand...
Click to collapse
I flashed both Fenny's firmware and a baseband he also provided. Did both twice, and calls are still not working.
I was doing some research on this whole "Radio: Unknown" thing and I started seeing threads talking about flashes corrupting the phone's EFS partition. I never made a backup of mine, so I have nothing to restore to. Is it possible that I could use someone else's EFS backup and then use it to restore my phone's EFS partition? Does it work like that?
THVRSDAY said:
I flashed both Fenny's firmware and a baseband he also provided. Did both twice, and calls are still not working.
I was doing some research on this whole "Radio: Unknown" thing and I started seeing threads talking about flashes corrupting the phone's EFS partition. I never made a backup of mine, so I have nothing to restore to. Is it possible that I could use someone else's EFS backup and then use it to restore my phone's EFS partition? Does it work like that?
Click to expand...
Click to collapse
No it will not work, this is device specific afaik.. Like I said earlier, I recommend you call T-Mobile for a replacement
Sent from my SGH-M919 using Tapatalk
Flashing modems and such with a custom rom installed often fails. Did you try doing a restore to full stock using Odin?
It sounds like the phoen has Android 4.4 on it already so you will need to flash the full 4.4 package (can't go back to 4.3 or 4.2)
Try and, boot hte phoen without modifying it, and see if calls work then.
The EFS thing is about the IMEI number. Does your device show an IMEI number in settings? If it does, your EFS isn't the problem. If it doesn't....well then yeah. Problem is pretty much narrowed down.
Skipjacks said:
Flashing modems and such with a custom rom installed often fails. Did you try doing a restore to full stock using Odin?
It sounds like the phoen has Android 4.4 on it already so you will need to flash the full 4.4 package (can't go back to 4.3 or 4.2)
Try and, boot hte phoen without modifying it, and see if calls work then.
The EFS thing is about the IMEI number. Does your device show an IMEI number in settings? If it does, your EFS isn't the problem. If it doesn't....well then yeah. Problem is pretty much narrowed down.
Click to expand...
Click to collapse
I have restored the phone to full stock and have been using it that way since I started this thread. Everything is just like fresh from the factory (except for the knox counter being tripped obviously). Calls still didn't work. An IMEI number still shows up the phone's settings. Using WiFi calling hasn't been that bad at all, but I'm screwed in the case of a real emergency with this thing.
I am not at home right now, and won't be for the next few days as I am out of town. However yesterday I noticed that the GPS does not lock anymore. I already restored the EFS backup I had from before but to no avail. Is there a way to get GPS working again? Some threads say to flash stock. Others told me it's impossible to fix it. I desperately need it as I am not familiar with the area and it's very inconvenient to not have working GPS. You never know when you might need it.
geokilla said:
I am not at home right now, and won't be for the next few days as I am out of town. However yesterday I noticed that the GPS does not lock anymore. I already restored the EFS backup I had from before but to no avail. Is there a way to get GPS working again? Some threads say to flash stock. Others told me it's impossible to fix it. I desperately need it as I am not familiar with the area and it's very inconvenient to not have working GPS. You never know when you might need it.
Click to expand...
Click to collapse
Flash stock based rom first, get a gps lock, then restore your backup. What rom are you using btw?
grunch21 said:
Flash stock based rom first, get a gps lock, then restore your backup. What rom are you using btw?
Click to expand...
Click to collapse
Carbon ROM created by me and @mathsz.
What do you mean by restore the backup? The EFS backup I made was made in Carbon ROM.
I just realized that i have the same problem (Carbon too)...i saw in the e970 topics that some guys had the same problem, they fixed with FREEGEE, option RESTORE EFS, i had restore but havent tried it yeat, because im at the office building...i think this will work
It didnt work
Hello ! I have solved the gps fix ! I had to install/flash the original rom...now i have the gps working.
Enviado do meu LG-E975 através de Tapatalk
toybxb said:
Hello ! I have solved the gps fix ! I had to install/flash the original rom...now i have the gps working.
Click to expand...
Click to collapse
You just KDZ back to stock JB? Or flashed one of the CWM ones out there?
geokilla said:
You just KDZ back to stock JB? Or flashed one of the CWM ones out there?
Click to expand...
Click to collapse
I did whit the LG software KDZ update...lost root and bootloader unlock. i think i will stay whit original rom but with root...
geokilla said:
Carbon ROM created by me and @mathsz.
What do you mean by restore the backup? The EFS backup I made was made in Carbon ROM.
Click to expand...
Click to collapse
toybxb said:
I did whit the LG software KDZ update...lost root and bootloader unlock. i think i will stay whit original rom but with root...
Click to expand...
Click to collapse
It'd be easier if you could find a stock based rom for your model (E971?) rather than using KDZ. Get GPS lock, then restore your ROM if you want. Though in your case i think it's safer to use stock rom for a while since GPS issue is known bug for gee/b based ROMs.
grunch21 said:
It'd be easier if you could find a stock based rom for your model (E971?) rather than using KDZ. Get GPS lock, then restore your ROM if you want. Though in your case i think it's safer to use stock rom for a while since GPS issue is known bug for gee/b based ROMs.
Click to expand...
Click to collapse
Mine is e975
I was using Carbon Rom since january...and never got any problem with gps, but now...had to return to stock.
Since I didn't see anyone pull the modem and kernel from the last stagefright update in Sept., thought I'd do it for the few of us that still have this old device.
T889UVUCOH4 Modem: http://www.mediafire.com/download/85es0yrteawo879/T889UVUCOH4_Modem_9_28_15.zip
T889UVUCOH4 Kernel: http://www.mediafire.com/download/w6wdyb3fut6t8c6/T889UVUCOH4_Kernel-9_28_15.zip
Was there an OTA for T-Mobile? I'm currently on a AOSP Rom.
Sent from my SM-N910T using Tapatalk
James62370 said:
Was there an OTA for T-Mobile? I'm currently on a AOSP Rom.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Yeah, but you need to be on a stock ROM to get the OTA, or you can download the whole ROM from sammobile.com. It's a security fix for stagefright. I just wanted to try the new modem and see if it made any difference. I won't be able to test the kernel, since I switch back and forth between a 4.4.4 TW ROM and 5.1 CM ROM.
Appreciate the info, have you notice better signal with the new radio?
James62370 said:
Appreciate the info, have you notice better signal with the new radio?
Click to expand...
Click to collapse
Maybe a little better signal (?), but basically the same. Haven't been on it real long, I'll have to see if the standby improves after I've been on it a while.
kozmo21 said:
since I switch back and forth between a 4.4.4 TW ROM and 5.1 CM ROM.
Click to expand...
Click to collapse
Are you dual booting? Is it possible?
Warning, don't flash this modem. I did and it killed my baseband. I tried flashing 3 other roms which wouldn't even finish booting to my phone before I finally realized it and flashed my original modem back and all was working again.
xamindar said:
Warning, don't flash this modem. I did and it killed my baseband. I tried flashing 3 other roms which wouldn't even finish booting to my phone before I finally realized it and flashed my original modem back and all was working again.
Click to expand...
Click to collapse
yikes.. ok thanks. I was going to do this today. I'll wait
xamindar said:
Warning, don't flash this modem. I did and it killed my baseband. I tried flashing 3 other roms which wouldn't even finish booting to my phone before I finally realized it and flashed my original modem back and all was working again.
Click to expand...
Click to collapse
Working fine on mine. Did you maybe get a bad download? You could maybe try downloading again?
Which modem did you go back to?
Flashed fine and so far no issues. Previous user might have a bad download or different device.
Flashed via TWRP today.. I had no service after reboot but did another restart and it was working.
Don't know if its any better than the previous modem version but will give it a try. thx
Working great here no issues
With old bootloader md1 4.1.2 with ROMofTHRONESv1.0
Sent from my SGH-T889 using XDA Premium 4 mobile app
My wife's note 2 got this OTA and now the phone won't even turn on....:crying:
tsiah said:
My wife's note 2 got this OTA and now the phone won't even turn on....:crying:
Click to expand...
Click to collapse
You caused the problem when you altered the stock ROM. From your thread about it here (http://forum.xda-developers.com/note-2-tmobile/help/recent-tmo-ota-update-bricked-wifes-t3245890), you said "Had her note 2 with stock 4.3, Rooted it last year to titanium backup and uninstall a couple bloatware apps. " This is what caused your problem. It was no longer a stock ROM when you remove apps. I know it doesn't seem like it would be a big deal, but it is, and you found out unfortunately
kozmo21 said:
You caused the problem when you altered the stock ROM. From your thread about it here (http://forum.xda-developers.com/note-2-tmobile/help/recent-tmo-ota-update-bricked-wifes-t3245890), you said "Had her note 2 with stock 4.3, Rooted it last year to titanium backup and uninstall a couple bloatware apps. " This is what caused your problem. It was no longer a stock ROM when you remove apps. I know it doesn't seem like it would be a big deal, but it is, and you found out unfortunately
Click to expand...
Click to collapse
That's kinda what I was thinking had happened.
I suppose I shouldn't blame the OTA. I just noticed someone else had issues with it too.
so to the people that actually flashed this new modem and kernel, is it working better than previous iterations?
question:
I flashed the C0H4 modem on note 2 (nameless lollipop rom) seems ok...
DO I have to also flash the Kernel ? is there an advantage to flashing the kernel? thx
Hello! Thanks for this! I flashed this over TWRP 2.8.7.1, and wiping my dalvik cache. My phone's originally T889UVALK8 (16gb SGH-T889 t0ltetmo) and the signal drops but after flashing this (C0H4) the signal greatly improved, although I'm having some signal instability since I'm supposed to have full bars because my house is just in line of sight, 2km from the tower. Also I think I'll do a clean install of another custom ROM since I'm using the CM12.1 t0lte nightly, and maybe this affects my signal (I know I'm stupid for doing it but it works).
Welp. After rebooting, the phone lost signal again. I have to do a wipe of dalvik cache to restore my signal. I guess I'll try using another ROM instead.
Upodate: I may be experiencing hardware issues. I have yet to flash back to stock since my phone's signal drops. I can't flash the firmware because it says 'zip signature verification failed.'
kozmo21 said:
Working fine on mine.
Click to expand...
Click to collapse
BUT, "yours" seems to be a completely different phone! It says Galaxy Note 4, SM-N910C...
What's up with that?!
AuralArch said:
BUT, "yours" seems to be a completely different phone! It says Galaxy Note 4, SM-N910C...
What's up with that?!
Click to expand...
Click to collapse
It's just the ROM I flashed that makes it say that. That ROM is in my signature... DN4