Database Users

4G FIX after doing a radio update

Hey everyone,
After I did the radio update (after doing the full root) my 4g was really messed up. The 4g would just not stay on and kept going out and then coming back every few secs. I tried reflashing the radio and yes I also formatted the cache right after and going back to the old radio. Then I tired going back to stock and it was fixed but when I did the full root again without the radio update after, well the 4g was back to crap. I even tried a custom rom after the root and still no go. So after doing many tests I found out that the firmware for the wifi is different from stock and full root. I found this out by going to ##DEBUG# then WiMAX Engineering...The full root had 20100401 (im guessing its the date of the firmware) and the stock had 20100423. So after more testing this is what worked for me.
1. I took the image file from the first part of the root (PC36IMG.zip)
2. Then I extracted android-info.txt and wimax_25043_R04.img
3. After that I made a new zip file with those two file from above and named the zip "PC36IMG" (without the quotes).
4. Then I put the PC36IMG.zip on the root of the SD card of the evo.
5. Then I booted up to the bootloader (u know the screen with the androids skating). Then I did the update and reboot.
After that my 4g was working without getting droped every 5 secs
If someone else tries this please let me know so I know that I didn't just get lucky.
P.S. IM NOT RESPONSIBLE IF ANYTHING BAD HAPPENS (it shouldn't but hey **** happens lol)
Enjoy your 4G back!

kck33 said:
Hey everyone,
After I did the radio update (after doing the full root) my 4g was really messed up. The 4g would just not stay on and kept going out and then coming back every few secs. I tried reflashing the radio and yes I also formatted the cache right after and going back to the old radio. Then I tired going back to stock and it was fixed but when I did the full root again without the radio update after, well the 4g was back to crap. I even tried a custom rom after the root and still no go. So after doing many tests I found out that the firmware for the wifi is different from stock and full root. I found this out by going to ##DEBUG# then WiMAX Engineering...The full root had 20100401 (im guessing its the date of the firmware) and the stock had 20100423. So after more testing this is what worked for me.
1. I took the image file from the first part of the root (PC36IMG.zip)
2. Then I extracted android-info.txt and wimax_25043_R04.img
3. After that I made a new zip file with those two file from above and named the zip "PC36IMG" (without the quotes).
4. Then I put the PC36IMG.zip on the root of the SD card of the evo.
5. Then I booted up to the bootloader (u know the screen with the androids skating). Then I did the update and reboot.
After that my 4g was working without getting droped every 5 secs
If someone else tries this please let me know so I know that I didn't just get lucky.
P.S. IM NOT RESPONSIBLE IF ANYTHING BAD HAPPENS (it shouldn't but hey **** happens lol)
Enjoy your 4G back!
Click to expand...
Click to collapse
I have the same problem, but...this is a hell of a first post. Anybody wanna test this out.

If someone can post the files, I can test it. I'm at work right now and can't download files that big w/o being flagged.

you mind posting the update zip you created?

clubtech said:
I don't think it has anything to do with the ROM.
If when you are connected to 4G you can access the internet, only suddenly 4G it drops for no reason and switch to 3G and then reconnects to 4G and goes on and on, below is the solution. if when you are connected to 4G you can not access the internet at all, the below wont fix it for you and it is probably a problem with your rom.
You will need your msl code to fix this, loop up in the forums to to obtain your msl code from Sprint:
hit ##DATA# > Edit mode.
Put in your msl code
Chose WIMAX
Scroll down to Wimax_Idle_Sleep
Change the value from 10 to 300.
Click menu, commit changes and restart the phone.
This fixed it for me and i never drop 4g (when in good coverage) again.
Basically Sprint has some STUPID setting that tells 4g to go into "sleep mode" of no data is passed on the 4g connection after 10 seconds which is essentially disconnecting 4g.
The problem is it goes into sleep mode (disconnecting), but then rescans and look for a 4G signal > reconnects to 4g and if no data will be passed in 10sec it will do the same again in an endless loop.
10sec to put a connection into sleep mode is really low so change it to 300sec.
Click to expand...
Click to collapse
This sounds like the same issue. I wonder if that file sets the sleep time? Just a guess. I had the same problem and this fixed it.
Here is the thread where I found it.
http://forum.xda-developers.com/showthread.php?t=704845&highlight=4g+sleep

Oh for me the wimax idle sleep time was always 10 even with the 20100401 firmware. The only thing that seemed different was the wimax scan attempt time. In 20100401 firmware it was 120 and in 20100423 firmware it was 1. So when I tried to change it in the older firmware it said I can only do 5 - 300. So I tried 5 and still no fix. The 4g still drops in and out. Here is file I used.

Tried your .zip. Not good. 4G is stuck on scanning and won't connect. I'll see if going back to the stock radio will fix it.

Oh that didn't even happen to me but I was already on the old radio. Try the old radio and remember to clear the cache. If it gets stuck then go to ##DATA# and check your wimax settings. Let me know how it goes.

Ran back through the Simpleroot process and got 4G back. Whew.

Nice! I wish I knew exactly what causes this problem but hey if it gets fixed then I don't care so much lol

is this zip already modified??

All that zip has is the wimax radio file to flash it but the file is old now. If your already on the latest radio then i would not use it because it may cause problems.

im stuck in "scanning"

You may need to reflash the radios and wimix. Are you on 2.2?

im on original 2.1 update1
I have the newest baseband tho... 2.12.00.07.28
I flashed this zip and phone is acting a little goofy
3G is in and out also!!

is it possible i may have to reflash the original RUU and start from there??

Why don't you try 2.2 maybe it will work after that.

after i just installed that zip im now getting DATA call failures error code 67.

Yea that should fix it or see if there is 2.2 RUU file out. Sorry I'm not home so my responds are very slow lol.

[Q] Loosing HSPA on root - no sim card

Hey guys,
after replying to several other threads i decided to make this a thread on it's own.
i tried to root my nexus 7 3G - "nakasig" with the two toolkits. also i tried it manually pushing the root stuff via adb.
when on stock + unlocked bootloader i have normal 3g connection but after the root it just says "no sim card". still i can search for networks but it doesnt let me connect to them. its as if the sim slot would lose its drivers or something. any ideas on that?
I'd be really happy if any of you would help me, im out of options i suppose...
cheers,
mo

Same problem here. Any news on that?

Here is a quick solution to your problem: STOP USING TOOLKITS!
The process is ridiculously simply. By using these automated tools, you're just asking for problems. And when one occurs, you have no idea how to troubleshoot it.
I wouldn't be surprised if the toolkit you used doesn't support the 3G model and probably broke the 3G capabilities.
1) Unlock bootloader if it hasn't already been done.
2) Flash custom recovery of your choice (make sure it's capable of supporting 4.2 multi-user)
3) Put an "su" flashable zip on sdcard.
4) Go into custom recovery and flash it.
5) Reboot
Voila. Done.

In fact, I didn't use any Toolkit (I want to control everything on my own, and am not afraid of using the console/adb).
Here are the steps, I did:
1. Unlock bootloader (fastboot oem unlock)
2. Boot custom recovery (fastboot boot [recovery.img])
3. Mount /system in recovery
4. adb shell -> put su in /system/bin -> put Superuser.apk in /system/app (and chmodded su to 06755, Superuser to 0644)
5. restarted, no 3G available
The problematic step could be the second, I used the "recovery-clockwork-touch-6.0.1.0-grouper.img", which is not specially for the N7-3G (called nakasig). Is there a better recovery Image?
I didn't want to flash the recovery, so I just booted into it. Could this be the problem?
Best regards

kroegerama said:
In fact, I didn't use any Toolkit (I want to control everything on my own, and am not afraid of using the console/adb).
Here are the steps, I did:
1. Unlock bootloader (fastboot oem unlock)
2. Boot custom recovery (fastboot boot [recovery.img])
3. Mount /system in recovery
4. adb shell -> put su in /system/bin -> put Superuser.apk in /system/app (and chmodded su to 06755, Superuser to 0644)
5. restarted, no 3G available
The problematic step could be the second, I used the "recovery-clockwork-touch-6.0.1.0-grouper.img", which is not specially for the N7-3G (called nakasig). Is there a better recovery Image?
I didn't want to flash the recovery, so I just booted into it. Could this be the problem?
Best regards
Click to expand...
Click to collapse
I had issues on my 16GB unit with that version of CWM on 4.1.2. I ended up using the 'beta' version 6.0.1.5 - it''s on XDA somewhere. When I got my N7 3G, I used the latest version of TWRP, and it works great.
But, based on what you are saying, none of that should even matter. In your case, you're not actually flashing a SU zip, you're manually installing it yourself (I did the same thing). So as long as you are able to mount /system and modify it's contents, which you obviously did, that's fine. The only thing I did differently was install su into /system/xbin, but /system/bin should be fine too.
Does 'su' and the SuperUser app work? If so, then that means your modification was successful.
Assuming that's all you did, I can't think of any reason why that would have broken 3G support. Is everything else 100% stock? If you flashed a custom kernel, it probably won't support 3G. The only one that I know of that DOES work is faux123's beta version.
Can you describe your issue a little more? Does the tablet display signal strength but just not get data? I'm assuming you disabled wifi to test, right?

Does 'su' and the SuperUser app work? If so, then that means your modification was successful.
Click to expand...
Click to collapse
Yes, they did. For example, I could install AdAway, which was able to change the hosts-file.
Assuming that's all you did, I can't think of any reason why that would have broken 3G support. Is everything else 100% stock? If you flashed a custom kernel, it probably won't support 3G. The only one that I know of that DOES work is faux123's beta version.
Click to expand...
Click to collapse
I didn't change anything. Just did the steps I described earlier...
Can you describe your issue a little more? Does the tablet display signal strength but just not get data? I'm assuming you disabled wifi to test, right?
Click to expand...
Click to collapse
Sure, I disabled WIFI. The signal strength display has all 4 bars (full reception), but no "H" or "3G" is displayed and also the bars are grey and not blue.
The weird thing is, that if I check "Use only 2G-Networks", I get blue bars with "G" and can access the internet...

kroegerama said:
Yes, they did. For example, I could install AdAway, which was able to change the hosts-file.
I didn't change anything. Just did the steps I described earlier...
Sure, I disabled WIFI. The signal strength display has all 4 bars (full reception), but no "H" or "3G" is displayed and also the bars are grey and not blue.
The weird thing is, that if I check "Use only 2G-Networks", I get blue bars with "G" and can access the internet...
Click to expand...
Click to collapse
Hrmmm....
I had the exact same issue (gray bars, no Internet), but it was because I flashed a non-3G compatible kernel. Once I replaced that, it started working properly again. I assume it worked fine prior to rooting, correct?
I still can't think of any reason why adding the su binary and SuperUser application would cause any issues with 3G connectivity. The two things have nothing to do with each other. Especially since you did it manually (which eliminates the possibility of some overzealous flashable zip. Hell, you didn't even flash a custom recovery but booted off it of it from your PC.
Have you tried rebooting since, to see if that cleared things up?
Just for the sake of eliminating them as a variable, why don't you try removing su and superuser.apk and see if that fixes it. I doubt it will, but it's worth a short.
The only other thing I can think of is for you to try reflashing the full 4.2 image (sans userdata) and see if that fixes the problem. Something else might have gotten broken and that should fix it.

Well, actually I don't know, if HSPA worked before rooting, because it was the first thing I did with my new N7
I rebooted a thousand times, toggled Airplane-Mode another thousand times and nothing helped. Now, I have reverted everything completely to stock:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-tilapia-4.13.img
fastboot reboot-bootloader
fastboot flash radio radio-tilapia-1231_0.10.0_1021.img
fastboot reboot-bootloader
fastboot -w update image-nakasig-jop40c.zip
After that i locked the bootloader (oem lock). And guess what? I still can't get HSPA connection
I checked the SIM card in my Smartphone (N4 btw) and it worked fine, so it can't be the problem.
Do you think, I have to send my N7 back, because it has a hardware-error?

kroegerama said:
Well, actually I don't know, if HSPA worked before rooting, because it was the first thing I did with my new N7
I rebooted a thousand times, toggled Airplane-Mode another thousand times and nothing helped. Now, I have reverted everything completely to stock:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-tilapia-4.13.img
fastboot reboot-bootloader
fastboot flash radio radio-tilapia-1231_0.10.0_1021.img
fastboot reboot-bootloader
fastboot -w update image-nakasig-jop40c.zip
After that i locked the bootloader (oem lock). And guess what? I still can't get HSPA connection
I checked the SIM card in my Smartphone (N4 btw) and it worked fine, so it can't be the problem.
Do you think, I have to send my N7 back, because it has a hardware-error?
Click to expand...
Click to collapse
Since you did that full flash (include the -w which wipes userdata), your N7 is completely back to stock.
There is definitely a possibility of a hardware issue, but before we assume that, there's one other possibility that comes to mind since you said you didn't know if it worked before.
What type of SIM card are you using? Is it the AT&T one that it came with? If so, did you activate it? If you did activate it, did you activate it through the tablet? When you turned off wifi, did it popup with a notification about logging into the AT&T network? If you activated it on the tablet, did you complete the whole process and receive the SMS and email?
And finally, the one thing that comes to mind as the possible problem if you are using that AT&T SIM card and it was activated:
What APN are you using? Mine came with two. The default is the one you use to register the SIM and activate it. The second APN is the normal usage one. After my activation, I was still on the registration APN and had to manually switch to the other one. If that is the case for you, and you are still on the registration APN, that could explain the issue. Try changing it to the other one and see if that fixes it.

No, I'm not at AT&T. Actually, I don't live in the US at all, I'm in Germany.
But I double-checked my APN-Settings and they seem to be set correctly. Also the SIM card is activated, as I'm able to use it in my Smartphone...
I've got one question, though: In the drop-down quick-settings pane, do you have a panel with your carrier name on it?
My Nexus 4 has one, but the Nexus 7 doesn't...

kroegerama said:
No, I'm not at AT&T. Actually, I don't live in the US at all, I'm in Germany.
But I double-checked my APN-Settings and they seem to be set correctly. Also the SIM card is activated, as I'm able to use it in my Smartphone...
I've got one question, though: In the drop-down quick-settings pane, do you have a panel with your carrier name on it?
My Nexus 4 has one, but the Nexus 7 doesn't...
Click to expand...
Click to collapse
Ah, well that eliminates my possible explanation.
No, I do not see that carrier name in either drop down. However, the carrier name should be on the bottom of the lock screen.
Are you 100% sure that the carrier in question will support the N7? I ask, because apparently people are having issues with T-Mobile SIM cards in the US. They work perfectly fine in a phone and/or other device, but when they put them in the N7 - nothing. Sounds like a similar issue. It seems like T-Mobile is blocking the N7 IMEIs from using standard voice or data packages.
I think the only real way to tell whether it's a hardware issue or not is if you have a friend with an N7 3G that you could try the SIM card in. That, or try buying some cheap prepaid one that you can use for a day or so.
But with what your saying, I'm thinking it very well might be a hardware issue for you.

Just to clarify:
- Which carrier is your SIM card from?
- Do you get 3G with that SIM in a smartphone? If so, which smartphone?

- My SIM is from "O2 - DE" (O2 Germany)
- Yes, I get 3G in a smartphone. It's a Nexus 4.
Are you 100% sure that the carrier in question will support the N7? I ask, because apparently people are having issues with T-Mobile SIM cards in the US. They work perfectly fine in a phone and/or other device, but when they put them in the N7 - nothing. Sounds like a similar issue. It seems like T-Mobile is blocking the N7 IMEIs from using standard voice or data packages.
Click to expand...
Click to collapse
Well, I'm not really sure, if my carrier blocks Tablets. I asked google, but no one else reported Tablet-blocking in the o2-network. But to be sure, I will test a friend's SIM card from vodafone tomorrow in my N7.
Sadly, I can't test my SIM in another N7-3G, because I don't know anyone who owns one.

So just to be sure, you are using the same APN settings on the N7 that you have in your Nexus 4?
Another thought - I have heard that with some European MVNOs, and even primary carriers that share networks with other providers, sometimes Android considers you to be roaming. Have you tried enabling data roaming just to see?
And when 2G-only is disabled, have you tried going into the mobile networks list to scan and ensure you are connected to the right network?

cmstlist said:
So just to be sure, you are using the same APN settings on the N7 that you have in your Nexus 4?
Click to expand...
Click to collapse
Yes, I used the correct settings in both devices...
cmstlist said:
Another thought - I have heard that with some European MVNOs, and even primary carriers that share networks with other providers, sometimes Android considers you to be roaming. Have you tried enabling data roaming just to see?
Click to expand...
Click to collapse
I enabled data roaming, but that also didn't help.
cmstlist said:
And when 2G-only is disabled, have you tried going into the mobile networks list to scan and ensure you are connected to the right network?
Click to expand...
Click to collapse
When I tap on the scan-button, it loads a few seconds and then says "Fehler bei der Netzwerksuche" (translated: "error while searching for networks")

kroegerama said:
When I tap on the scan-button, it loads a few seconds and then says "Fehler bei der Netzwerksuche" (translated: "error while searching for networks")
Click to expand...
Click to collapse
Yeah Android tends to do that a lot. Usually if that happens I toggle airplane mode off and on, and then try the list again. Sometimes it takes ten minutes of trying to finally get a successful scan for networks that lists all the carriers it can see.
Sent from my Galaxy Nexus using Tapatalk 2

Ok, I was now able to get to the carrier list and manually selected the correct one. But that didn't help either.
When the other SIM card, which I will test tomorrow, also doesn't get 3G access, I will send the device back to google and hope, they replace it for me...

Ok, seems like my N7 has a defect. I will call google to ask for a replacement N7...

kroegerama said:
Ok, seems like my N7 has a defect. I will call google to ask for a replacement N7...
Click to expand...
Click to collapse
Glad to hear you finally got confirmation. Based on your troubleshooting, that was looking more and more likely. I'm sure Google will replace it for you properly.

I just called google and they will send me a new N7. And when the new one arrives, I have to put my defect one in the box and send it back. That's very customer-friendly. So I can use the N7 (without 3G) until I get the new one

Flashed Verizon RUU, cellular radios, GPS, and camera now broken

Hey all,
So, a little backstory: I got this HTC 10 from Sprint not too long ago, and little did I know that I would be stuck with Sprint unless I reflash the phone firmware. (after research, asking HTC and Sprint, I received misinformation from reps stating that the phone would work on Verizon with just a carrier unlock issued over the air). Moral of the story: don't rely on customer service :silly:.
Fast forward to now, and I have rooted (temporarily to run Sunshine), S-OFF'd (using Sunshine), changed the CID (for Verizon), and flashed the newest Verizon RUU that developer Dottat kindly posted here.
That worked, full LTE, but then whenever the camera or GPS were accessed by any application, the phone would freeze with a black screen (though it seemed something was still running in the background, as notification sounds would still play, and I could exit by pressing the home button and waiting about a minute). After this, I tried flashing the Viper ROM just for kicks, but then the cellular radios only functioned with 3G coverage (no LTE in a coverage area), and GPS was still broken (the camera issue was fixed with this flash for some reason).
Unfortunately (or maybe not), I am pretty sure /system has been wiped multiple times. I also ran
Code:
htc_fastboot erase modemst1
htc_fastboot erase modemst2
after each install of a new ROM, then performed a factory reset from recovery (just a factory reset, nothing more).
Now I went ahead and used an official ROM from HTC's website in an attempt just to get full functionality working on any carrier. I flashed the USA unlocked variant (and changed the CID to BS_US001. MID is still 2PS650000), but now I am experiencing more missing functionality. The camera and GPS are still missing, and now the SIM card is not detected (when entering the access point names dialog, a message pops up stating that there is no SIM, or SIM error when I am using an activated AT&T SIM). When I enter the test menu (*#*#4636#*#*) and select any option for network mode other than what is default (LTE/CDMA), the new option won't 'stick' (it returns to default after a few seconds).
This sounds to me like there is stale firmware on the device from a previous flash, or that the firmware for these core peripherals is corrupt. Is there a way I can get these devices working again? Or am I now stuck with a bricked device ? I do still have a backup I took of what was installed stock by Sprint (all except for /data...but I don't need that partition, right?)
EDIT: Mods, I am terribly sorry! I meant to post this in HTC 10 Q&A. I don't see a way to delete a thread, so hopefully we can move it.

MrFarquad said:
Hey all,
So, a little backstory: I got this HTC 10 from Sprint not too long ago, and little did I know that I would be stuck with Sprint unless I reflash the phone firmware. (after research, asking HTC and Sprint, I received misinformation from reps stating that the phone would work on Verizon with just a carrier unlock issued over the air). Moral of the story: don't rely on customer service :silly:.
Fast forward to now, and I have rooted (temporarily to run Sunshine), S-OFF'd (using Sunshine), changed the CID (for Verizon), and flashed the newest Verizon RUU that developer Dottat kindly posted here.
That worked, full LTE, but then whenever the camera or GPS were accessed by any application, the phone would freeze with a black screen (though it seemed something was still running in the background, as notification sounds would still play, and I could exit by pressing the home button and waiting about a minute). After this, I tried flashing the Viper ROM just for kicks, but then the cellular radios only functioned with 3G coverage (no LTE in a coverage area), and GPS was still broken (the camera issue was fixed with this flash for some reason).
Unfortunately (or maybe not), I am pretty sure /system has been wiped multiple times. I also ran
Code:
htc_fastboot erase modemst1
htc_fastboot erase modemst2
after each install of a new ROM, then performed a factory reset from recovery (just a factory reset, nothing more).
Now I went ahead and used an official ROM from HTC's website in an attempt just to get full functionality working on any carrier. I flashed the USA unlocked variant (and changed the CID to BS_US001. MID is still 2PS650000), but now I am experiencing more missing functionality. The camera and GPS are still missing, and now the SIM card is not detected (when entering the access point names dialog, a message pops up stating that there is no SIM, or SIM error when I am using an activated AT&T SIM). When I enter the test menu (*#*#4636#*#*) and select any option for network mode other than what is default (LTE/CDMA), the new option won't 'stick' (it returns to default after a few seconds).
This sounds to me like there is stale firmware on the device from a previous flash, or that the firmware for these core peripherals is corrupt. Is there a way I can get these devices working again? Or am I now stuck with a bricked device ? I do still have a backup I took of what was installed stock by Sprint (all except for /data...but I don't need that partition, right?)
EDIT: Mods, I am terribly sorry! I meant to post this in HTC 10 Q&A. I don't see a way to delete a thread, so hopefully we can move it.
Click to expand...
Click to collapse
A MOD should move it soon.
I am not the best here, but hopefully can be of some help.
I would just superCID, save a step for flashing RUU's.
So, when you flash the Verizon RUU, does camera work?
(if you RUU and only have 3g, wipe the modems to get 4g back)

If your trying to use the phone on Verizon I would do the following:
1) Change your CID to Super, 11111111
2) Flash the US Unlocked RUU, http://www.htc.com/us/support/rom-downloads.html#unlocked
3) After it fully boots, reboot into the bootloader & flash the Verizon radio, http://forum.xda-developers.com/verizon-htc-10/how-to/vzw-how-to-unlocked-model-vzw-t3376743
4) Make sure the Preferred Network is set to Global, Settings>Mobile data>Preferred Network
5) Get to the secret menu *#*#4636#*#*, and set the preferred network type to "CDMA/EvDO/GSM/WCDMA/LTE Auto"
I use a Verizon model with the US Unlocked firmware. As far as custom ROMs, some work with Verizon's network and some don't. I'm sure theres a workaround but I've stuck with the US Unlocked firmware, and just use Xposed for any tweaks/mods.
If your trying to use it on AT&T and the radio from the US unlocked RUU should work.

andybones said:
A MOD should move it soon.
I am not the best here, but hopefully can be of some help.
I would just superCID, save a step for flashing RUU's.
So, when you flash the Verizon RUU, does camera work?
(if you RUU and only have 3g, wipe the modems to get 4g back)
Click to expand...
Click to collapse
Used to be a guy around here we could trust to help.
Sent from my HTC6545LVW using Tapatalk

Need some help getting back into things, thanks!

Hey all! I have made the switch to a Nexus 6P about a year ago, so I am quite rusty with the S5 and how to do things with it. I recently sold an S5 on swappa, and I am attempting to help that user get it back to stock. I would have done this before selling, but we thought the process would have been more simple.
To quote the user I am assisting at the moment "... I crossed into canada a few days ago, phone worked good with international plan. cross back to US and keep getting weird "not registered on network" messages and have 0 connectivity to my Verizon phone network. Tried new sim card, verizon store says the issue is because it is rooted etc (doubt they know what they are talking about)....But figured i'd do a clean install etc and see what happens. Followed instructions for Odin. From what i read it sounds like I need the OA 8 Lollipop retail tar..phone model number is SM-G900V. Keep getting "NAND Write Start!! FAIL! (Auth)" in Odin. Tried multiple USB cables and other random tips I found online. Any advice? Am I using the wrong stock tar?"
What can I/we do to resolve this issue? I have searched xda, but I am totally lost with the S5 to be honest. Things have changed so much since I used the phone that I have no idea where to start. It was on Alliance ROM before I shipped it. It has the Toshiba eMMC (or whichever doesn't have bootloader unlock).
Again, thanks in advance guys!

Some more info about the phone, I'm the buyer.
Still running Alliance. I do have an IMEI # (some sites say that could be an issue).
Model/Phone name is Samsung Galaxy S5 SM-G900V
Baseband Version is G900VVRU2BOK3
Kernel Version: 3.4.0 [email protected] #1
Tue Nov 17 20:06:51 KST 2015
Build number: AllianceROM_VZW_V10_G900V_XXU1BOH4
Knox version 2.3
Exact message I get is "out of service area" when i make a call. then a "mobile network not available" message will pop up after.

miketon907 said:
Some more info about the phone, I'm the buyer.
Still running Alliance. I do have an IMEI # (some sites say that could be an issue).
Model/Phone name is Samsung Galaxy S5 SM-G900V
Baseband Version is G900VVRU2BOK3
Kernel Version: 3.4.0 [email protected] #1
Tue Nov 17 20:06:51 KST 2015
Build number: AllianceROM_VZW_V10_G900V_XXU1BOH4
Knox version 2.3
Exact message I get is "out of service area" when i make a call. then a "mobile network not available" message will pop up after.
Click to expand...
Click to collapse
Silly question, but have you tried pulling the battery, and Sim, let it sit for a sec, then power on to see if you have service? Might just need to reset the prl. Never been to Canada with the phone so idk what's going on ha.
Could also check the data settings to make sure it's set to CDMA+LTE instead of global or whatever other options it has. You haven't flashed a new radio file, have you? @miketon907

tr4nqui1i7y said:
Silly question, but have you tried pulling the battery, and Sim, let it sit for a sec, then power on to see if you have service? Might just need to reset the prl. Never been to Canada with the phone so idk what's going on ha.
Could also check the data settings to make sure it's set to CDMA+LTE instead of global or whatever other options it has. You haven't flashed a new radio file, have you? @miketon907
Click to expand...
Click to collapse
Pulled battery out and sim. No service fix. If I turn phone on with sim card out, it will say "no sim card". back sim card back in, no net work connection....It is set to CDMA+LTE. No, I have not flashed a radio file.

miketon907 said:
Pulled battery out and sim. No service fix. If I turn phone on with sim card out, it will say "no sim card". back sim card back in, no net work connection....It is set to CDMA+LTE. No, I have not flashed a radio file.
Click to expand...
Click to collapse
Ok, just trying to rule things out.
You activated the SIM in the US and used it before going to Canada, right?

Yep. so Sim card A which I got after buying the phone was working good. I went to Canada and used same sim card on international plan, went back to US and suddenly phone loses mobile connection and has no service as soon as I cross US border. went to Verizon for sim card B, sim card B does not work either.

miketon907 said:
Yep. so Sim card A which I got after buying the phone was working good. I went to Canada and used same sim card on international plan, went back to US and suddenly phone loses mobile connection and has no service as soon as I cross US border. went to Verizon for sim card B, sim card B does not work either.
Click to expand...
Click to collapse
You could try just doing a factory reset on recovery if you haven't already. Instead of starting from stock. Just wipe the data partition. If you wipe the system partition it won't have anything to boot into

oh. Well i'll try that later tonight. Report back around 11pm est. thanks!

tr4nqui1i7y said:
You could try just doing a factory reset on recovery if you haven't already. Instead of starting from stock. Just wipe the data partition. If you wipe the system partition it won't have anything to boot into
Click to expand...
Click to collapse
ok did that. (wipedata/factory reset->wipe cache partition). still have alliance-safestrap etc on the phone. sim card still giving weird messages.

miketon907 said:
ok did that. (wipedata/factory reset->wipe cache partition). still have alliance-safestrap etc on the phone. sim card still giving weird messages.
Click to expand...
Click to collapse
Still the same messages?

yes, same messages.

miketon907 said:
yes, same messages.
Click to expand...
Click to collapse
Try flashing one of the modems on this page. It should reset the radio to have service again. I'd do it without the sim card in. Boot once, you obviously won't have service since there isn't a sim. Then turn off the device, insert the SIM and reboot.
I am looking into the write fail now just in case you can't even flash a modem file.
Also, you downloaded the samsung drivers, correct?
EDIT: I found an old thread that might help you troubleshoot odin - http://forums.androidcentral.com/sa...hacks/391849-galaxy-s5-odin-failing-root.html
EDIT 2: You might just have to switch to a different tar file. This user states that they used the same stock version as the one they were currently on. I'd give that a shot first. Then check to make sure "block reactivation" in security settings isn't checked. The exact directions that should get you going are from a user on that page, as follows;
"chainfire xda quote op-Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
New to Samsung? Unfamiliar with Odin? Think all the above is a hassle? Get used to it. It's very simple, and us Samsung folk use Odin (or Mobile ODIN ) for everything! It's so very very convenient once you get used to it. Notice the 30 second comment above? For experienced users, the entire process indeed takes only 30 seconds!" - Dale Borrelli
Final note. Try the tar for the android version you are currently on first, then go up to the version you'd like to be on.
Edit: @miketon907 any luck yet?

yes, thanks a lot. flashing the modem worked. have service now again.

No Service with Sim Card Inserted

A few days I woke up with no service on the Nexus 6p. This was a few days after updating to the latest oreo build. Sim card seems detected because when I take it out another message shows up "No SIM card - No service", and when I put it back it only shows "No service". Tried putting the card in a Nexus 5X and it works fine.
Tried the following with nothing working so far:
- Switching 2G/3G/LTE and rebooting in between.
- *#*#4636#*#* and turning off the radio, switching between the different options of GSM/LTE/etc...
- Restoring a working nandroid backup
- Reflashing different ROMs
- Factory reset
- Factory reset then flashing ROMs
- Wiping cache and dalvik
- efs fix in twrp
Hardware version ANGLER-VN2
IMEI shows up under IMEI information tab but not under SIM Status tab, there it shows not available.
I live in Ontario Canada, carrier is Freedom mobile.
So now I'm stuck, tried calling google and hwawei and they won't do an RMA because my warranty is expired.
Anyone has any ideas to try?
Thanks in advance.

Not that this is going to help, but this has GOT to be an Oreo issue, myself as well as at least 4 others that I have seen has been getting the No service, or No Sim, mine did the No Sim, then started bootlooping.
---------- Post added at 07:36 AM ---------- Previous post was at 07:06 AM ----------
https://www.theandroidsoul.com/fix-...d-wifibluetooth-issues-restoring-twrp-backup/

No this has nothing to do with O.
Which version phone do you have? H1511 or H1512?
What country are you in now?
What is your carrier? If MVNO state that.
Are your IMEI and phone numbers showing up in settings?
Everyone, please put the most basic information in your profile like where you live, which carrier you are currently on, and maybe even which variant of your phone.

I updated the first post with more info. How do I tell if I have H1511 or H1512? I bought it from the google store in Canada.

More information is good. Please update your XDA profile so the next person trying to help can check there first. You can find the device variant by booting to bootloader (not recovery) and using the vol toggle to navigate to "Barcodes". IMEI should show up there too. Date of manufacture, Serial #, etc. I think you should have started a normal thead, not Q/A, BUT your IMEI and a lot of other information should be showing up under SIM info. That's a problem. Second, you say you did the EFS fix in TWRP. Can you explain how you did this? Did you use one of YOUR OWN TWRP backups which contained the modemst1,modemst2 and restored ONLY those two partitions to your device? Did you receive any confirmation or error? Have you tried using a SIM from a Rogers or Telus in your phone to see if the SIM info shows up?

Thanks for the help, I'll update my profile with this info as well.
in the bootloader the IMEI shows up along with the rest of the info. It's a H1511 device.
The EFS fix is by following this: https://www.theandroidsoul.com/fix-empty-imei-corrupted-efs-no-sim-unknown-baseband-wifibluetooth-issues-restoring-twrp-backup/
is modemst1 and 2 contained in the twrp backup? and if so how do I restore it? in restore options there's system, data, vendor and boot only. I guess it's an option in the backup that I haven't selected?
I tried another SIM also from freedom and it didn't work. I don't have a Rogers or other SIM to try currently.

Right, so if you didn't ever select the EFS partitions when using TWRP Backup, you never backed them up so under Restore they don't show up (so you can't use that method). You can however use TWRP terminal or fastboot to wipe those and reboot. I would be sure to try at least one SIM from either Rogers or Telus. If that doesn't work, then wipe the EFS partitions and let them rebuild (hopefully).

Definitely Oreo issue. Google messed with something and it broke data for many people. I have been troubleshooting this for the last week (Verizon, US, fully stock 6P) and finally found a thread where a Google rep acknowledged the problem and said it was high priority for a fix.

I wish you luck with that one @LucJoe. This has been happening for the past 2 years from MM, N, and now O...and XDA is full of threads (just look). So you just go ahead and wait for Google to fix it for you, LOL. - Not a new issue related to O.

Never happened to me before updating. The data issues manifest differently across different carriers but for some reason Oreo likes to play it safe and disconnect data. I have not been able to get LTE for more than a couple seconds, but will get slow unstable 3G occasionally. Google confirmed the issue here: https://productforums.google.com/forum/#!msg/phone-by-google/kw3ZcXd1BVs/7HYuANdoAgAJ

A recent success using terminal from TWRP (or the OS if you are rooted). You can also use fastboot to do the same thing using the commands in the article posted in this Q/A (method 2). Good luck! See thread here.

This seems like it's a different issue described in that thread. I'm not running out of data, there's no service and no connection of at all to any network.

I did find that and try it before posting here. It did nothing to fix the problem. It did say that something was copied over '4 MB copied, at 14.3 MB/s' something like that but nothing changed.

I also have the same issue. Have tried everything including going back to stock 7.1.2 & locking the bootloader. Nothing seems to work. Interestingly, when i pull up the hidden phone diagnostic menu, it shows all cell measurement info which means that the antenna is receiving signals but the phone somehow is not registered on the network?

I can wipe those partitions with fastboot but is it safe? I have never used TWRP and my problems started after updating to Oreo. Is there a chance the official OTA could corrupt those partitions?

@LucJoe- That fix is not for you. That is for users who have no IMEI or phone number under About Phone>>SIM info. Your issue (as I understand it) is a weak and intermittent signal that keeps disconnecting LTE and sounds like a carrier or SIM issue. Why not go get a new SIM provisioned for your phone. That or pop somebody else's SIM in your phone and see if you get a different outcome.

Yes that was my first thought as well. I got a new SIM, then another one. So 3 SIMs now with the same result. I've been on the phone with so many techs from Verizon/Total Wireless and none of them have any answers. If I put the same SIMs into a Moto E4 I picked up for testing, it works fine. But the 6P immediately disconnects from LTE then bounces between 3G/1X.
My next test is to try a SIM from a different network I guess... maybe Verizon is blocking my 6P. Or maybe my LTE radio is damaged somehow.

So I did this using TWRP but wasn't sure if it actually went through or not. I did it now through adb from pc and also fastboot and it says permission denied. Any idea how to bypass that?