Develop Bugs

[Q] *HELP!*T-Mobile Galaxy S II Network Problem

OK guys i'm a complete noob here at XDA (registered yesterday) but i'm getting really desperate and confused and since i've seen XDA is such a great community i thought i'd give it a shot...
My GSII had been running BeastMOD ROM II v3.0 for about a month now and it worked like a dream but about 3 days ago i turned off my phone and then turned it back on a minute later and I HAD NO NETWORK!! Now, that i recall i didn't do anything to cause this. I called t-mobile and went through all their troubleshooting, no luck. I flashed BeastMOD ROM II v4.2, no luck. Re-flashed BMOD 3.0, no luck. I noticed i don't get ping to my network, I have no IMEI number(i get null/null), and no baseband version(unknown). I'm really worried and hopefully you guys can help me some suggestions ASAP as i haven't had network in three days.

restore a back up of your stock if you still have it.

and this will only get me back to stock and not undo root or will it? will try

Here's what happens. I try to do my first stock ROM restore and it says
"Checking MD5 sums...
MD5 mismatch!" <--Whats wrong? I'm currently doing a restore on a backup three hours after that one which i'm not sure which one it is (maybe the first backup after i installed BMOD 3.0) but hopefully it will do something.

http://forum.xda-developers.com/showthread.php?t=1325036
http://forum.xda-developers.com/showthread.php?t=1433819
http://forum.xda-developers.com/showthread.php?t=1336915
read up, they are different phones but might have common factor
to fix i think:
http://forum.xda-developers.com/showthread.php?t=1462870

mrpagercao said:
http://forum.xda-developers.com/showthread.php?t=1325036
http://forum.xda-developers.com/showthread.php?t=1433819
http://forum.xda-developers.com/showthread.php?t=1336915
read up, they are different phones but might have common factor
to fix i think:
http://forum.xda-developers.com/showthread.php?t=1462870
Click to expand...
Click to collapse
Hey thanx for that last link but the freakin person that made that method just bailed on me after his method screwed with my phone. I have stock now but i have a problem where my phone keeps rebooting until it gets network and even after it finds network and gets its IMEI and Baseband version back, that "fix" doesn't let me use data and for some actions the phone says the SIM card is not ready or available. and when i turn off the phone and back on it keeps rebooting until it finds network like i said. I don't know what the EFS is but that could be something that is making the phone malfunction. Please! Someone help!

i had almost the same problem.
My IMEI is still there, but it just won't connect to any network! All of a sudden, I woke up and it wont connect!
I'm getting a replacement sent to me from tmobile. weird.

restoring efs with nvtools/qpst

hi guys, i flashed the lte modem on my phone and it seems that its wiped out my efs folders, ive been trying to restore my efs folder with nvtools and qpst, neither seems to work since somehow dm mode is not responding to them
any solns? ty in advance for any help
a couple of things:
ive already odin'd back to stock, no luck on restoring efs(perhaps im doing something wrong?) i dialed *#7284# and put it into the RNDIS+DM+MODEM mode, nvtools says phone failed to answer while QPST says that comm7(the samsung serial port) is not a phone
its pretty had to do this since the phone is rebooting itself every other minute

Questions and help issues go in Q&A
Thread moved
Thanks
FNM

Been there, sucks. For me to get out of the constant restarts I had to flash the lte modem again. Flash stock (odin) flashed cwm (odin), put the modem on my external sd card and flashed that.At least that way I could work on it a little. And below is basically what I did to finally get it to work. Hard to say all my steps as I was trying everything.
Well I dont really know how I got mine back to life, tried all the standard stuff from the threads,got my imei back but had no network,network type,service nothing helped. last resort I said whatever ill try anything now. Came across this
http://galaxynote2root.com/galaxy-n...3g4g-aws-bands-on-att-galaxy-note-2-sgh-i317/
whatever it did it restored everything (cold see carrier,network,etc)but corrupted imei, next i followed this guide
http://forum.xda-developers.com/showthread.php?t=1804117
If you need this is a complete no imei nv backup I used before flashing my imei with the generator
http://db.tt/4hunZ7qy
used the imei generator, then the writer (link on post does not work for the imei generator,so found it here
http://d-h.st/vVV
Wrote my imei back and presto, back in action. Fully functional again, including 4G
Like I said this was a last resort, but worked

AznDud333 said:
hi guys, i flashed the lte modem on my phone and it seems that its wiped out my efs folders, ive been trying to restore my efs folder with nvtools and qpst, neither seems to work since somehow dm mode is not responding to them
any solns? ty in advance for any help
a couple of things:
ive already odin'd back to stock, no luck on restoring efs(perhaps im doing something wrong?) i dialed *#7284# and put it into the RNDIS+DM+MODEM mode, nvtools says phone failed to answer while QPST says that comm7(the samsung serial port) is not a phone
its pretty had to do this since the phone is rebooting itself every other minute
Click to expand...
Click to collapse
Let me guess. You've git a Canadian phone
Sent from my Nexus 7 using Tapatalk 2

+1

got it fixed on friday, was so tired that i went to sleep
basically i followed someone's post on the forum(forgot name) and flashed the tmo modem, since the mct one always gave me the bootloop, then i enabled DM mode and finally got nv tools/qpst to recognize my phone, it appears that the issue was that the drivers does not recognize the new modems..
anyway, once i was done restoring nv, i flashed the tmo lte modem and paranoid android
now i have my imei back and i can use lte
although my bluetooth address still says unknown..not sure if normal

My bluetooth also says unavailable, I would think if you are not hooked up to bluetooth then it should say unavailable. Im to scared to flash the tmo lte modem again...

[Q] Lost IMEI now stuck in boot loop after ODIN to stock

Hello,
I'm having a lot of difficulty getting my Note II (SGH T889V) in working order . I'll try to explain the situation in an organized way. Thank you for your time and kind help!
Background
I have a Note 2 from Wind Mobile in Canada - SGH T889V. I got it 2.5 months ago. It was rooted, was running TWRP and I only loaded one ROM, flashed once, on it - 4.1.2 modified touchwiz ROM. Never once had an issue. The ROM was super stable and in great working order.
I got it unlocked about 2 weeks ago because I was visiting the states. When I got to the states, I put in a T-Mobile sim card which was working great for a few days. One afternoon during my vacation I was having slow data issues, so I thought to change the modem/radio from a Wind Mobile radio to a T-Mobile radio. That gave me 4G data speeds but killed my calls. So I tried to go back to the Wind Radio and that had my phone complaining that there was no SIM card. I went back to the T-Mobile radio and I got calling back but only 2G data.
My IMEI was corrupted - it showed up as zero. I left the T-Mobile radio on the phone when I got back. My home network wouldn't recognize me and thought I was still roaming.
Attempted Fixes
Tried a basic factory reset. Tried a different ROM. Tried wiping all internal data.
I got home and tried to flash to stock ROMs found on XDA for Wind Mobile phones. That didn't solve the issue. The IMEI remained null. The phone would reboot automatically every few minutes unless I turned Airplane Mode on. I figure the phone was looking for a signal and couldn't because of the IMEI problem.
So I looked around on the net and found a link about injecting the IMEI back using QPST (http://forum.xda-developers.com/showthread.php?t=1206275) but I couldn't get the program to detect my phone so I gave up and thought I could just get my binary count to 0 and stock and I'll just take it back for warranty.
I tried Triangle Away but I couldn't get the counter to go to 0 even with stock ROM and recovery. So I thought I would take it to a cell repair shop locally. I took it there and all they did was cause an issue on the phone to make it appear that KIES firmware upgrade failed so that it would be repaired under warranty. You would see a emergency firmware upgrade error the minute you turned the phone on. However, download mode still showed the custom binary count at 1, they didn't get it down to 0.
I spoke with my carrier and with Samsung anonymously, they said the counter would be an issue if I sent it in.
I came back home and tried doing the following, with the hopes of trying Triangle Away again:
1. Installed TWRP via ODIN and ran the restore on the backup I created in TWRP when I first got the phone. I restored everything including EFS. Phone boots to the stock samsung rom but it would restart automatically every few minutes. Even with Airplane mode on, it would still reboot on it's own.
The KIES error message doesn't appear anymore.
2. Went back to ODIN. It was getting stuck on SYSTEM in ODIN version 3.07 when flashing a stock rom. So I switched the USB port on my computer and used ODIN 3.04 then the flashes went through properly with no hang ups.
So I tried to flash a prerooted (http://forum.xda-developers.com/showthread.php?t=1975560&highlight=wind) stock ROM
and
also a basic stock ROM (http://forum.xda-developers.com/showthread.php?t=2061031), along with a stock recovery
Both just get stuck in a bootloop. I tried going to the stock recovery and wiping data, cache, factory reset several times. No luck - still boot loops. Wont go into the ROM.
I did not try "Re-partition" in ODIN. I'm not sure if that'll hard brick the device but maybe that way I can repair all of the partitions? - http://forum.xda-developers.com/showthread.php?t=860432&page=2
__________
Im hoping to get back into a prerooted ROM or stock ROM to try this Triangle Away Method - http://forum.xda-developers.com/showthread.php?t=2272966 to get the custom binary down to zero.
I tried to use the Triangle Away ODIN method but it doesnt go through in ODIN, it just gets stuck.
If I can get into the ROM without it boot looping or rebooting automatically- I think I can fix my IMEI like this person did - http://forum.xda-developers.com/showthread.php?t=2145967
Outcomes Im hoping for
To stop the bootlooping/ automatic reboots, then
1. To get the custom Binary count to 0 so I can send it back in for warranty to Samsung or my carrier, Wind Mobile. The binary says Samsung Official. - http://forum.xda-developers.com/showthread.php?t=2068156
or
2. To get the phone to working order so I can try this persons method - http://forum.xda-developers.com/showthread.php?t=2145967
The phone is still responding and it's still working with ODIN. It makes me think the issue is software or partition related and not hardware related per se. If it is hardware, I just want to get this phone back to Samsung but I need to unroot/clear the binary counter.
The phone has never been dropped or damaged physically. I've really babied the phone. This is my third Samsung Galaxy phone (I've had a Vibrant and S2x before this one.)
This has really ruined my week. I need my phone for work. I greatly appreciate any kind help or guidance. I know the collective genius here at XDA will be able to find a solution.
Thank you so much!

If you have flashed the tmobile modem you will now have to keep the tmobile one in order to get your phone to boot. Flashing a t889v modem will cause loops. Dont know of any way to get back to t889v modems.

Hey, don't worry, you aren't the first to experience this problem. Many users have reported that the T889V will bootloop with the T889V modem after flashing another modem. Many have also restored IMEI and service to their phones, so there is a solution. I don't have the specifics, but there are many threads about this problem with solutions. I have quickly searched for one and I believe it has everything you need to fix it.
http://forum.xda-developers.com/showthread.php?t=2119074&page=3

Byangmang said:
Hey, don't worry, you aren't the first to experience this problem. Many users have reported that the T889V will bootloop with the T889V modem after flashing another modem. Many have also restored IMEI and service to their phones, so there is a solution. I don't have the specifics, but there are many threads about this problem with solutions. I have quickly searched for one and I believe it has everything you need to fix it.
http://forum.xda-developers.com/showthread.php?t=2119074&page=3
Click to expand...
Click to collapse
Thank you. I'm going to give that a shot. I'll install CWM then install a T889 TMobile Radio to see if it boots.
I'll report back. Fingers crossed.

I had same issue... this is how I fixed it
http://forum.xda-developers.com/showthread.php?t=2274843

sniperess said:
I had same issue... this is how I fixed it
http://forum.xda-developers.com/showthread.php?t=2274843
Click to expand...
Click to collapse
Thank you all!
I got the boot loops to stop by flashing CWM recovery, then flashing a TMobile Radio.
From there, I followed the QPST instructions of installing a QCN file on the phone to reenable the AWS spectrum. Then I used the IMEI creator and NV Writer programs and I was back.
Data seems alright, getting alright speeds on Wind right now. I just found my bluetooth a little hard to hear in the car this morning.
So with this process, I should stick with a Tmobile radio from now on right? If I flash a Wind/ T889V modem it'll boot loop?
Have you guys noticed any signal or performance issues after restoring the phone this way? I'm wondering if it's worth the trouble to get the custom binary counter to clear and return this phone for warranty. Seems to be working for the most part so far.
Thank you so much again! I thought I was going to have to pay $100 to get it JTAGed.

Glad to here your back and running.
I have a t889v using it on telus, and since I am stuck on tmobile modem I get lower phone signal but never loose signal. On a plus I now get lte speeds.

First day back it seems good for the most part.
Only issue I had was Bluetooth in my car would cut out at a high rate of speed (when I was on the highway). It worked really well while I was on local roads but once I hit the highway I couldn't hear the other side at all pretty much. I had to put them on speaker to hear them. They could hear me really well, better than before when I was driving on local roads.
Never occurred in the past. Could it be a radio issue? Signal seemed okay and I was able to continue the conversation over the phone speaker on the highway.

lilroach said:
First day back it seems good for the most part.
Only issue I had was Bluetooth in my car would cut out at a high rate of speed (when I was on the highway). It worked really well while I was on local roads but once I hit the highway I couldn't hear the other side at all pretty much. I had to put them on speaker to hear them. They could hear me really well, better than before when I was driving on local roads.
Never occurred in the past. Could it be a radio issue? Signal seemed okay and I was able to continue the conversation over the phone speaker on the highway.
Click to expand...
Click to collapse
The bluetooth issue doesn't seem to be a problem anymore. Disappeared on it's own.

lilroach said:
The bluetooth issue doesn't seem to be a problem anymore. Disappeared on it's own.
Click to expand...
Click to collapse
I noticed I have serious data issues when the network goes into HSPA+ mode. I get really good data for a minute then it'll cut out totally for like an hour. I tried rebooting, tried battery pulling. It seems the T-Mobile radio doesn't interface well with Wind's HSPA+ . I had full bars but the internet wouldn't load. It was pretty non-functional for most of the day.
It works decently when it's not on HSPA+
Tried switching to a Wind modem, went into boot loops. Went back to T-Mobile radio. Should I try a different T-Mobile radio?

how to fix your T889v if you accidentally overwrite the radio
If you get stuck with no IMEI, in my case, flashed omnirom 4.4.1 t0ltetmo, which uses Tmobile radio... it killed the Wind Mobile radio... restoring form nandroid did not help.
solution:
flash omnirom t0lte (not t0ltetmo) and your problems are gone!
lilroach said:
I noticed I have serious data issues when the network goes into HSPA+ mode. I get really good data for a minute then it'll cut out totally for like an hour. I tried rebooting, tried battery pulling. It seems the T-Mobile radio doesn't interface well with Wind's HSPA+ . I had full bars but the internet wouldn't load. It was pretty non-functional for most of the day.
It works decently when it's not on HSPA+
Tried switching to a Wind modem, went into boot loops. Went back to T-Mobile radio. Should I try a different T-Mobile radio?
Click to expand...
Click to collapse

[Q] Phone Flashed to Page Plus Stuck on Boot Screen

Hello all,
I tried searching for a similar scenario but wasn't able to find anything so I thought I'd try posting here.
I purchased a flashed Sprint Samsung Galaxy S3 from ebay about 6 months ago. I'm assuming the phone is rooted, I had my number flashed with page plus service to the S3 without problem and it has worked fine since then. Apart from the initial flash to page plus by the ebay vendor I've used the phone daily without flashing anything else, just using apps from the store and basic daily functions like email, social media and camera use. Today while using the phone it randomly shut off. When starting up the phone again it gets stuck on the "Samsung" logo, it does not reboot either.
I know that a hard reset can fix this issue but the problem is I believe a hard reset might break the page plus flash and I'm afraid of losing the number I have on this phone. Has anyone experienced this problem with a phone flashed to page plus and has successfully fixed this? Or will I just have to buy a new phone to flash my page plus number to?

Write down your flashed page plus number to external paper and after hard reset flash it again using dfs software.
Or if you don't want to hard reset... Flash the tar file via Odin to repair the stuck boot then root it.
But i recommend to flash a new rooted ROM from recovery after wiping data/factory reset.. It will not wiping your flashed status.
Sent from my SPH-L720 using Tapatalk

update
Thanks for the reply, unfortunately I don't really flash on my own and didn't quite want to experiment just yet.
What I ended up doing was esn swapping the page Plus number I was using from the Sprint s3 to an htc rhyme that was also activated on page Plus in a hope of salavging my #. I then went ahead and factory reset the s3 and that fixed the stuck on boot problem.
My question is now this, would it be possible to esn swap the number back to the s3 and have it function on page plus once again. from what I can tell in the settings it still has the 65002 prl I believe is uses to flashthis model and my orginal phone number still appears in the s3 device settings (and 3g username aferrad) despite my swapping the number to the rhyme.
I would be happy to provide addtl info and appreciate any help you can offer.

[Q] [VERIZON] Repaired IMEI, Updated with OTA, Phone keeps roaming...

Really not sure what to do here, and I'm starting to get very frustrated, especially since I know exactly what the issue is and I can't find a solution... So here is everything I did up to this point in detail. I wanted to go back to stock for a while, but I remembered not being able to update at all last time I tried this. I used the LG Flash Tool to go back to 10b (I think? Earliest firmware out there) It started when my phone would tell me that "My Device was not registered yet" in the System Update settings. I did some Googling and found out it was because my IMEI number was blanked out (All zeroes), and I found a tutorial that was for the G2, but worked for the G3, to repair the IMEI. I first rooted with the LG One Click Root Tool when I got to Lollipop, used the IMEI that was under my battery, converted it to HEX and injected it into my phone with RF_NV_Manager, which was installed with QPST by Quallcom. After doing this, my IMEI was fixed, it matched the same IMEI that was under the battery on my phone, though I never texted or called anyone from there so I never noticed anything strange. I was able to update to the latest official Lollipop firmware, but then my phone started telling me I left the home network. Thinking it was just a glitch or something, because I had roaming issues before on stock, I switched to a custom ROM since that fixed it last time before I even knew that IMEI's existed. That didn't fix it at all. I was on LiquidSmooth Alpha and my phone will still go to roaming, and the way I would fix it was to piss around with the mobile network settings and change them back, then I would get 4G LTE for a few minutes, but I would NEVER be able to call or text. Since it was a discontinued ROM, I thought I just got unlucky, so I went to an official Nightly for CM12.1. At the moment I have LTE but no calling or texting... Then I found out that these issues tend to occur after IMEI fixes, so what do I do? Can anyone point me to a proper tutorial on how to fix this? After looking, I ended up downloading and installing something called EFS Professional 2.1 but now I'm even more confused...
EDIT: I tried going into ADB and inputting "adb reboot nvrestore" but that didn't fix it... The site said it's based on a backup that was automatically created when the phone was first built but that was on a completely different forum for a different phone. Going to try to flash back to stock KitKat.
EDIT: Alrighty! I'm getting somewhere! I flashed back to 10B with the Upgrade DL option, before I used Board DL. I can call and text now, as well as LTE, and OTA updates work, but I'm just going to root and go straight to the Nightly CM12.1 that I wanted to go to in the first place.
EDIT3: That seems to have done the trick. For people who have had issues with roaming after IMEI repairs, try flashing your stock TOT with the Upgrade DL option, then root and install your preferred ROM.