Related
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.
So as I was en route to completing a full flash of my Droid X onto Cricket I couldn't get my web working. Two things I hadn't done were my autosh files and my NVRAM from whiterabbit.org I got my NVRAM file from whiterabbit and wrote it to the phone. it wrote. I restarted the phone and everytime it starts it goes to 1x , then up to 3g, then restarts. everytime. Just enough time to allow me to put it into airplane mode so that I can try to fix it. I didn't backup my NVram sadly so if anyone has a backup please send it my direction. It would be greatly appreciated. this is fixable since i can access my phone still.
-Update today-
Not sure if it means anything but i went into QPST and switched my Mobile IP behavior from mob+simp f/back to simple ip only and it and now it doesnt constantly restart i switched it to mobile ip only, same result, but data still isnt working yet. switching back to mob+simp f/back makes it restart it seems.n
Also noticed that when I turn on my wifi and I switch it to simple IP only it still puts me in a reset loop.
furikazashi said:
So as I was en route to completing a full flash of my Droid X onto Cricket I couldn't get my web working. Two things I hadn't done were my autosh files and my NVRAM from whiterabbit.org I got my NVRAM file from whiterabbit and wrote it to the phone. it wrote. I restarted the phone and everytime it starts it goes to 1x , then up to 3g, then restarts. everytime. Just enough time to allow me to put it into airplane mode so that I can try to fix it. I didn't backup my NVram sadly so if anyone has a backup please send it my direction. It would be greatly appreciated. this is fixable since i can access my phone still.
-Update today-
Not sure if it means anything but i went into QPST and switched my Mobile IP behavior from mob+simp f/back to simple ip only and it and now it doesnt constantly restart i switched it to mobile ip only, same result, but data still isnt working yet. switching back to mob+simp f/back makes it restart it seems.n
Also noticed that when I turn on my wifi and I switch it to simple IP only it still puts me in a reset loop.
Click to expand...
Click to collapse
Did you also write the PRL to the phone after writing the NVRAM? Your PRL should be version 49027. mob+simp f/back will need to be enabled.
If you want to start over, you can SBF to .340 or use the maderstcok zip .340 and your DX will be up to date and fully stock.
I've used bootstrap and rom manager to go back to stock before altering web so that isn't an issue anymore. I've stopped trying the nvram. Everytime I enter the proxy info fully inthe phone manually the phone does the 1x 3g then reset loop. Im guessing something is forcing a reset but can't figure it out. I went into test mode once to force 1x only and keep out 3g but alas it still looped. Ideas? Im also installing log cat to see if maybe a log.can tell me why the phone soft resets during the.loop
Sent from my DROIDX using XDA App
Im using prl 49027. I've narrowed it down to possible glitch. Upon entering the info for the proxy manually it goes into 1x then 3g then reader loop. Ivebeen using a stock backup to revert to prior tweaking so I can keep trying to figure this out if u have a exact method u use im all ears. Or just ideas. Im running out lol
Also one more thing, ive just entered in the proxy information manually via the cell phone and the phone hasnt given me a boot loop like it used to, still the internet isnt working yet so im going to go into QPST and see if just changing the mobile IP setting throws me into the loop again...EDIT: it sends me into a soft restart loop since its on mob+simp f/back again... catlog didnt show anything that i can see sadly. the soft restart forces the log to stop and doesnt show why it did.switched it back to mobile ip only and stopped the reboot cycle but no data at all ugh...
EDIT: used my backup again after the reboot cycle issue , found out that after i end up using a NVRAM i get the boot loop again...so in other words i unfortunately have to factory reset because i used the NVRAM addon, one thing i noticed was it updated 11 things, not 12. not sure why. moving on..
furikazashi said:
Im using prl 49027. I've narrowed it down to possible glitch. Upon entering the info for the proxy manually it goes into 1x then 3g then reader loop. Ivebeen using a stock backup to revert to prior tweaking so I can keep trying to figure this out if u have a exact method u use im all ears. Or just ideas. Im running out lol
Also one more thing, ive just entered in the proxy information manually via the cell phone and the phone hasnt given me a boot loop like it used to, still the internet isnt working yet so im going to go into QPST and see if just changing the mobile IP setting throws me into the loop again...EDIT: it sends me into a soft restart loop since its on mob+simp f/back again... catlog didnt show anything that i can see sadly. the soft restart forces the log to stop and doesnt show why it did.switched it back to mobile ip only and stopped the reboot cycle but no data at all ugh...
EDIT: used my backup again after the reboot cycle issue , found out that after i end up using a NVRAM i get the boot loop again...so in other words i unfortunately have to factory reset because i used the NVRAM addon, one thing i noticed was it updated 11 things, not 12. not sure why. moving on..
Click to expand...
Click to collapse
So you did this in QPST:
-----NV items from http://www.whiterabbit.org/android (you must generate this uniquely for your phone, go to the link enter [email protected] replace x's with your 10 digit phone number, make sure 2.7 is selected and download the file)
----Now go to the Memory tab. Under NV Items click Write. Browse and select
the NV Item file you generated earlier. Once its done it will say 12 NV
Items were successfully written to the phone
-----I used the PRL attached to do the OTA. (CricketEVDO_38515.prl). I had to put .zip at the end to upload it, so just rename it to CricketEVDO_38515.prl.
-----Now go to the Other tab. Under PRL click Write and browse to the destination you saved the attached file.
Let me know if this helps at all.
I sent NV items from the whiterabbit but this time it updated 12 items, not sure why it did 11 the first time. i also updated the prl to 38515 still no internet though, going into pst to see if the mobile ip behavior is the way its supposed to, update in a sec
UPDATE: phone was set to mobile ip only switched back to mob + simp f/back. and VOILA. 4:28am two weeks later and BAM internet and voice I will be writing a tutorial basing what ive learned into a stable 99% success rate for flashing droid x to cricket, ive only seen a handful out there and im sure i can hepl someone the way everyne has assisted me. thank you everyone. also just upgraded to 49027 prl for 3g and works great not enough 1x coverage where i live sadly.
Hi everyone,
Just switched to 3 Mobile UK from Virgin with my Droid Pro and having a very random issue ... I cant make any calls. I can receive calls, write sms, receive sms, use the internet - the whole lot, but I am just not able to make any calls whatsoever! What happens is that when I dial, you can see the seconds counting up sometimes, but there is no sound whatsoever. I popped the SIM into my old HTC and that works just fine. I was wondering what the issue was for that?? I am trying to force the phone to stay on 3G only as I feel that, even though I have UMTS only selected in settings, it wants to make calls using 2G which 3 (being an all-3G network) obviously doesnt support. Any ideas of what the issue could be?? I started playing around in the hidden ##program menu but there is no option to play around with GSM settings, only pointless CDMA/EV-DO stuff ...
Anyone got an idea? I should say that I am running the latest OTA Gingerbread ..
P.S. It also crashes when trying to make a call .. just FYI
Why dont you flash back to Froyo 3.8.7 and see if the updated Radio image from Gingerbread has not spoilt anything in the phone?.
But be careful and do not do the mistake I did. First go to recovery, restore froyo backup and then flash sbf. That should have you booting in less than 10mins. If you do not restore froyo through recovery then RSD will not recognize your phone. Even if it does it will not flash the SBF.
All the best. Report back.
I think that 3 have an agreement with some competitive carriers to use their networks when a 3g signal is not avaialble. Maybe you phone sees this as roaming. It's a long shot but try turning roaming on. You never know.
Sent from my GT-P7500 using XDA App
I just really wish there were some more options to play around with the basebands on the Droid Pro ... now I have resorted to doing a factory reset and starting fresh, and now the damn thing cant even get any signal whatsoever ... When looking for available networks i am only able to find the normal 2G networks (Orange, voda, O2 and T-Mo).
Right ... so using Recovery, u mean the mode you enter using the update.zip?
chaihg said:
Why dont you flash back to Froyo 3.8.7 and see if the updated Radio image from Gingerbread has not spoilt anything in the phone?.
But be careful and do not do the mistake I did. First go to recovery, restore froyo backup and then flash sbf. That should have you booting in less than 10mins. If you do not restore froyo through recovery then RSD will not recognize your phone. Even if it does it will not flash the SBF.
All the best. Report back.
Click to expand...
Click to collapse
P.S.: There is so many ways of doing this .. could you point me to a guide that worked for you? Also, could you go into detail when you mean to restore the froyo backup. When flashing the updates I didnt make any backups if thats what you mean. The Recovery mode also only shows a few options like wiping cache, data, applying update and so on ...
vivid22 said:
P.S.: There is so many ways of doing this .. could you point me to a guide that worked for you? Also, could you go into detail when you mean to restore the froyo backup. When flashing the updates I didnt make any backups if thats what you mean. The Recovery mode also only shows a few options like wiping cache, data, applying update and so on ...
Click to expand...
Click to collapse
What i meant was to restore a nandroid backup from ClockworkMod. It is the droid bootstrap you install. You go into that restore froyo backup and then pull battery. Then click RSD on your computer load sbf and connect your phone by holding volume key to enter bootloader. Once this happens the sbf will flash then you can easily boot to froyo. If there is a problem in booting then just pull battery again and enter stock recovery by holding keys R+M and powering the phone and do a data wipe. Let me know how this works.
If these dont work then we can try to flash radio images from other motorola phones. I remember flashing an India radio image for my defy when I came to India and then going back to europe radio image when I went back to europe. It should work however that will be a last option.
Hey.. well I guess 3 just wont work with that phone, the limited settings for GSM/UMTS make it virtually impossibile for force 3G calling and disable 2G. I am switching back to T-Mo where I know it will work...
What happened was, that due to my extensive modifications to ##program settings, rooting and some GSM apps I was running, my phone decided to pack up yesterday morning and give me the red M of evil -- so I went thru the whole process of sbf flashing and now I am back on a 3.8.7, after updating from 2.26.2. Maybe you can explain just for better understanding what the benefits are of doing the restore thru bootstrap as you explained?
I sent my Xoom off for 4G upgrade and received it. Moto in its infinite wisdom sent me a new Xoom. So naturally, I started my Xoom and 3G/4G failed because I had a new MEID. Motor provided this new Xoom without syncing up with Verizon. So Verizon didn't have my MEID synced to my new 4G card. This explains the connectivity issues I had OOB.
I wish I new that before I went about a variety of flashing that failed in one way or the other. I did eventually get things to run with 3g/4g, and here s what I did.
1. Flash HRI66
2. Do a hard reset from Settings/Privacy
3. Reboot and fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img (http://forum.xda-developers.com/showthread.php?t=1074979)
4. Reboot into CWM and flash Android-HC-3.2.2-Stock+Rooted-1.1-SOLARNZ.zip (http://forum.xda-developers.com/showthread.php?t=1242524)
5. Flash HLK75C (http://dl.dropbox.com/u/22648028/HLK75Csystemboot.7z password is "AceXMachine" without the quotes)
Upon reboot both my WIFI and 3G/4G were restored.
When you reboot you should get prompted for HLK75D which is the market.
Peace, Happiness & Joy
I just saw this thread right before I was about to possibly enter a boot loop by trying something stupid. Thanks for posting! I will have to try this out tomorrow on my 3G XOOM.
Just FYI, Short/y posted the update for HLK75D HERE in case anyone wants to manually update.
So excited to read your post. Figured the system and boot images were the missing pieces to getting my problem solved. Unfortunately so far I have not seen any cellular data activity since getting up to HLK75D. It has been about an hour since rebooted and tried to activate.
I must still be missing a piece to the puzzle. When I look at a screen shot from droidlife under "About tablet" I see under Baseband version "CDMA_N_03.1A.54P ltedc_u_05.19.00". On my Xoom I only have the CDMA radio listed but everything else is the same. I also do not have any LTE settings under Mobile networks like I know I should based on the insert I got in the box back from Moto. This makes me think somehow I managed to corrupt the radios but I certainly never did that on purpose. Any idea how I can get the right radios to flash too?
---------- Post added at 06:02 PM ---------- Previous post was at 05:47 PM ----------
So excited to read your post. Figured the system and boot images were the missing pieces to getting my problem solved. Unfortunately so far I have not seen any cellular data activity since getting up to HLK75D. It has been about an hour since rebooted and tried to activate.
I must still be missing a piece to the puzzle. When I look at a screen shot from droidlife under "About tablet" I see under Baseband version "CDMA_N_03.1A.54P ltedc_u_05.19.00". On my Xoom I only have the CDMA radio listed but everything else is the same. I also do not have any LTE settings under Mobile networks like I know I should based on the insert I got in the box back from Moto. This makes me think somehow I managed to corrupt the radios but I certainly never did that on purpose. Any idea how I can get the right radios to flash too?
I have the same exact issue. Even bricked my xoom trying to resolve this, but fortunately I was able to unbrick it.
I did exactly the very same thing. Thanks Ace! Worked very well for me.
SemperAndroid said:
5. Flash HLK75C [/QUOTE
When you say "Flash", what should I be typing at the end of my command line
C:\Program Files (x86)\Android\android-sdk\platform-tools>?
Click to expand...
Click to collapse
Tinninches said:
SemperAndroid said:
5. Flash HLK75C
Click to expand...
Click to collapse
When you say "Flash", what should I be typing at the end of my command line
C:\Program Files (x86)\Android\android-sdk\platform-tools>?
Click to expand...
Click to collapse
The file downloads as a .7z I've tried to compress it and flash it from CWM off my external SD Card. I've tried flashing the two files individually. I've tried fastbooting them.
Could you possibly go into a bit more depth as to what you did in step 5?
SemperAndroid said:
I sent my Xoom off for 4G upgrade and received it. Moto in its infinite wisdom sent me a new Xoom. So naturally, I started my Xoom and 3G/4G failed because I had a new MEID. Motor provided this new Xoom without syncing up with Verizon. So Verizon didn't have my MEID synced to my new 4G card. This explains the connectivity issues I had OOB.
Click to expand...
Click to collapse
This was really annoying. The MEID Verizon had was a digit missing and didn't have my SIM card identified. I actually started to think the the new hardware wasn't hooked up correctly inside and was about to send it back in before I check the Verizon website.
SemperAndroid said:
I sent my Xoom off for 4G upgrade and received it. Moto in its infinite wisdom sent me a new Xoom. So naturally, I started my Xoom and 3G/4G failed because I had a new MEID. Motor provided this new Xoom without syncing up with Verizon. So Verizon didn't have my MEID synced to my new 4G card. This explains the connectivity issues I had OOB.
I wish I new that before I went about a variety of flashing that failed in one way or the other. I did eventually get things to run with 3g/4g, and here s what I did.
1. Flash HRI66
2. Do a hard reset from Settings/Privacy
3. Reboot and fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img (http://forum.xda-developers.com/showthread.php?t=1074979)
4. Reboot into CWM and flash Android-HC-3.2.2-Stock+Rooted-1.1-SOLARNZ.zip (http://forum.xda-developers.com/showthread.php?t=1242524)
5. Flash HLK75C (http://dl.dropbox.com/u/22648028/HLK75Csystemboot.7z password is "AceXMachine" without the quotes)
Upon reboot both my WIFI and 3G/4G were restored.
When you reboot you should get prompted for HLK75D which is the market.
Peace, Happiness & Joy
Click to expand...
Click to collapse
I followed these steps and everything seems to be working. I can't verify 4G works since it's not available here yet, but 3G works fine. However, my Build Number still shows HLK75C. I thought something might have went bad with the HLK75D reboot/install (battery was low) so I reflashed the 75C boot & system thinking it would reprompt for the update. It didn't. Check for updates says I'm up to date. Anyone else have this issue? Does the Build Number not change after the update?
This actually did not work for me. These were the steps I did exactly:
1) Flashed to HRI66.
2) Booted up and skipped verification and setting up a Google account. Did a hard reset through the settings.
3) Upon reboot, I flashed the Tiamat recovery image.
4) Upon reboot, I entered the CWM and flashed Solarnz's 3.2.2 image. Unfortunately, when I use the 1.1 version from his thread, I get an error telling me that it was "bad", so I had to use the original version that he posted. (This might be why it didn't work, I'm not sure.)
5) Upon reboot, I flashed the HLK75C images in Fastboot.
I loaded up and I was on 3.2.2 just fine, with the HLK75C build, but my kernel didn't have the "LTC" part in it like it did when I received it from Verizon. I still have full bars but no 3G/4G connectivity. Wi-Fi works fine.
When I take out my SIM card, I obviously lose all the bars.
[EDIT] I noticed in another thread that someone brought up the question whether people with connectivity problems were wiping the cache and davlik every time they flashed. Is that something I should be doing in CWM after flashing anything? Yeah, I'm kind of new and dumb to this. [/EDIT]
Cannot Activate on Verizon after 4G Upgrade
When I first got my Xoom back and booted it up, it imediately stuck at the logo screen and said Failed to boot LNX 0x0004 in red text and then a line below it said Starting RSD Mode 2. I tried rebooting several times but it always went to the same place. I did the HRI39 sbf and got it back up and running, then performed these steps.
1. Flash HRI66
2. Do a hard reset from Settings/Privacy
3. Reboot and fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img (http://forum.xda-developers.com/show....php?t=1074979)
4. Reboot into CWM and flash Android-HC-3.2.2-Stock+Rooted-1.1-SOLARNZ.zip (http://forum.xda-developers.com/show....php?t=1242524)
5. Flash HLK75C (http://dl.dropbox.com/u/22648028/HLK75Csystemboot.7z password is "AceXMachine" without the quotes)
I now have my Xoom on HLK95D as it should be and can connect to WiFi just fine but it does not acknowledge that the Xoom has 4G and will not activate with Verizon through 3G either. If I go into settings, About Tablet and Status, my Xoom shows Network: Unknown, Mobile network type: Unknown, MDN: Unknown, MIN: Unknown and MEID: Unknown.
I am wondering if I happened to be an unlucky one who got a bad 4G card. My understanding is that the new 4G card not only adds 4G but also replaces the built in 3G Radio chip. I did check my MEID # before I loaded the ROM that supports the 4G card and it did show my original MEID # for my Xoom but once I load a ROM that has the drivers for the 4G card, they disappear. Any thoughts
dlundy said:
I followed these steps and everything seems to be working. I can't verify 4G works since it's not available here yet, but 3G works fine. However, my Build Number still shows HLK75C. I thought something might have went bad with the HLK75D reboot/install (battery was low) so I reflashed the 75C boot & system thinking it would reprompt for the update. It didn't. Check for updates says I'm up to date. Anyone else have this issue? Does the Build Number not change after the update?
Click to expand...
Click to collapse
Figured out my issue with the 75D update. It was not installing automatically due to CWM reccovery. I had to pull the update from the \cache folder and install it manually through CWM. Of course, it overwrote recovery and killed root so I had to reflash CWM and reroot with the universal root zip, but it is now on HLK75D and working properly. I still can't test 4G, but 3G is working.
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.