Develop Bugs

Strange Boot Loop With NO CWM Recovery

I've got a T-Mobile Note 3 that I picked it up on launch day last Thursday at a T-mobile store. I proceeded to root the phone with Odin, then restore via Titanium Backup and then fix the backup with "restorecon -R -v /data". Life has been great until last night. Initially I got a circle with a line through it instead of the mobile signal and my cellular link would not connect, but my wifi was fine. When the problem was sill occurring this morning I figured it was an odd cellular problem and rebooted the phone this morning when it persisted. Now the phone is rebooting a few minutes after it completes booting.
It will boot normally, then I'll unlock the phone and get my window manager (Holo)...then I'll get the error "Process system isn't responding. Do you want to close it?". Then I get the error "Unfortunately, Favorite Apps has stopped." Regardless whether I interact with those error messages the phone then reboots a minute later. I have *not* done a restore from CWM ever and the phone doesn't seem to have suffered any physical damage.
The things I've tried include:
*) power down, remove sdcard, then reboot
*) power down, remove sim card, then reboot
*) power down, remove sim card, remove sdcard, then reboot
*) clear cache, then reboot
*) clear dalvik-cache, then reboot
*) clear dalvik-cache and cache, then reboot
*) clear dalvik-cache, clean cache, then wipe to factory, then reboot
In all the above scenarios nothing has changed. The phone reboots after it completes booting.
In the past, I've rooted and flashed on a G1, a G2, and an S3. I've bricked my S3 that had to be repaired via JTAG. This reboot problem with my Note 3 is completely unlike any of the things I've seen with previous phones.
I've read through some of the other threads about reboot loops, but all the threads I've read were caused by a CWM restore and have no solution yet.
Does anyone know the cause of this and what could fix it?

digitalfiend said:
I've got a T-Mobile Note 3 that I picked it up on launch day last Thursday at a T-mobile store. I proceeded to root the phone with Odin, then restore via Titanium Backup and then fix the backup with "restorecon -R -v /data". Life has been great until last night. Initially I got a circle with a line through it instead of the mobile signal and my cellular link would not connect, but my wifi was fine. When the problem was sill occurring this morning I figured it was an odd cellular problem and rebooted the phone this morning when it persisted. Now the phone is rebooting a few minutes after it completes booting.
It will boot normally, then I'll unlock the phone and get my window manager (Holo)...then I'll get the error "Process system isn't responding. Do you want to close it?". Then I get the error "Unfortunately, Favorite Apps has stopped." Regardless whether I interact with those error messages the phone then reboots a minute later. I have *not* done a restore from CWM ever and the phone doesn't seem to have suffered any physical damage.
The things I've tried include:
*) power down, remove sdcard, then reboot
*) power down, remove sim card, then reboot
*) power down, remove sim card, remove sdcard, then reboot
*) clear cache, then reboot
*) clear dalvik-cache, then reboot
*) clear dalvik-cache and cache, then reboot
*) clear dalvik-cache, clean cache, then wipe to factory, then reboot
In all the above scenarios nothing has changed. The phone reboots after it completes booting.
In the past, I've rooted and flashed on a G1, a G2, and an S3. I've bricked my S3 that had to be repaired via JTAG. This reboot problem with my Note 3 is completely unlike any of the things I've seen with previous phones.
I've read through some of the other threads about reboot loops, but all the threads I've read were caused by a CWM restore and have no solution yet.
Does anyone know the cause of this and what could fix it?
Click to expand...
Click to collapse
I would just Odin to stock and restart. I'm guessing some app your restored form another phone did it.

YellowGTO said:
I would just Odin to stock and restart. I'm guessing some app your restored form another phone did it.
Click to expand...
Click to collapse
I don't believe it was an app that was restored because the restore had run perfectly for 5 full days. I completed the restore last Thursday...that's what makes this so unusual.
Do you know where to get the stock zips to use with Odin?

digitalfiend said:
I don't believe it was an app that was restored because the restore had run perfectly for 5 full days. I completed the restore last Thursday...that's what makes this so unusual.
Do you know where to get the stock zips to use with Odin?
Click to expand...
Click to collapse
There's some stock Odin tar files in the Android development forum. Download and flash using Odin. Once it reboots, remove battery and manually boot into stock recovery and do a factory reset/wipe. Reboot and it should work.
Sent from my SGH-T889

jmerlos said:
There's some stock Odin tar files in the Android development forum. Download and flash using Odin. Once it reboots, remove battery and manually boot into stock recovery and do a factory reset/wipe. Reboot and it should work.
Sent from my SGH-T889
Click to expand...
Click to collapse
It looks as if the stock tar in zip format (N900TUVUBMI7_N900TTMBBMI7_TMB.zip) can be downloaded from either of these links:
http://forum.xda-developers.com/showthread.php?t=2465764 (faster download link)
http://forum.xda-developers.com/showthread.php?t=2468275 (slow download link)
I just finished downloading from the first link and after extracting the zip file I have these files:
N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_HOME.tar.md5
SS_DL.dll
This seems like an obvious thing, but want to ask because of how odd this problem is: Do I simply flash the "N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_HOME.tar.md5" file the same way that I flashed the CWM through Odin?

Yes, but IIRC, just uncheck reboot, reboot manually into recovery, then wipe, factory reset, etc. Pull your battery, reboot. Check the TWRP thread, it has exact directions.
sgh-TWEAKED-889©

Warrior1975 said:
Yes, but IIRC, just uncheck reboot, reboot manually into recovery, then wipe, factory reset, etc. Pull your battery, reboot. Check the TWRP thread, it has exact directions.
sgh-TWEAKED-889©
Click to expand...
Click to collapse
Got it, thank you! Here's what I'm referencing for the Odin options:
http://forum.xda-developers.com/showpost.php?p=46110842&postcount=2
I'll flash this and update the thread.

Good luck bro!!
sgh-TWEAKED-889©

Ok, I flashed with Odin then once it completed I got the "PASS!" status in Odin. I shut down Odin, pulled the battery from the Note 3, then allowed the phone to boot. There was a "booting recovery" message in blue at the top of the screen before the phone booted, then it booted to the "samsung logo", then the animated circular logo, then the white screen with the "T-Mobile 4G LTE" logo, then rebooted. The second boot, it did the same thing but stayed on the "T-Mobile 4G LTE" screen for many minutes...then it seemed as if it was completing it's reboot because I got the notification bar with the time and the circle with the line through it for the cell signal strength. I got the same error when the phone seemed to have completed booting, then a reboot. Now it's back to the same place it started in it's rebooting cycle.
This makes absolutely no sense at all. If I'd have done a CWM restore then I could understand that...but there's no reason for this that I can see. The phone acts as if it was knocked off of the T-Mobile network and now it finishes it's booting cycle long enough to be rebooted.
So now I have a useless Note 3. I'm game for taking the phone back to the T-Mobile store and requesting that they replace the phone, which they probably would, but I have no guarantee that this wouldn't happen again. I'm open to suggestions as long as they don't cause me to brick my phone completely.

I finished installing TWRP and darthrom successfully. However, after the darthrom finishes booting I have the exact same problem with the phone rebooting that the stock ROM had.
I'm back to square one.
I'm open to suggestions.

There are a lot of people having boot loop problems even without root though they are spread out among various sub forums. Try this thread for example:
http://forum.xda-developers.com/show....php?t=2467005[Q] Reboot cycle after restart help
Sent from my SAMSUNG-SGH-I317

Dumbo53 said:
There are a lot of people having boot loop problems even without root though they are spread out among various sub forums. Try this thread for example:
http://forum.xda-developers.com/show....php?t=2467005[Q] Reboot cycle after restart help
Sent from my SAMSUNG-SGH-I317
Click to expand...
Click to collapse
I saw a couple threads last night when I was searching around on the web about other models of phones with SIM socket and SIM card issues. I'm beginning to think that my issue is hardware-related, and not software. I did another wipe last night based on this thread's post: http://forum.xda-developers.com/showpost.php?p=46157872&postcount=6&nocache=1&z=7848000959493220
Instead of simply wiping, I formatted /data/, then wiped, then I flashed on the stock ROM, then flashed on the darth rom. I got slightly different results once the phone was done with it's firstboot - it kept giving me the error that a new SIM card had been installed and the phone needed to be rebooted. This causes me to suspect the physical hardware of my Note 3 or the SIM card. I have ruled out the SIM card because I've been using it in my old G2 since this started, via an adapter for the G2's SIM socket, and it's been fine. I'm planning on taking the phone to T-Mobile today and seeing what they can sort out with either a SIM exchange or phone exchange.

The note 3 misbehaved the same way while in the T-Mobile store. They swapped the phone out under warranty after asking only the basic questions and trying a factory reset. The same SIM card in the new note 3 works fine.

I'm on the same boat. Got my Note 3 this morning, rooted an hour ago with CMW, made backup and flashed Stock ROM from Jovy. Result: bootloop. Restore backup and still on bootloop. DLing the Odin stock .tar to see if it helps. Any more suggestions?
Edit: After flashing with Odin the stock tar from Sammy all it's good...at least for now.

Wally72 said:
I'm on the same boat. Got my Note 3 this morning, rooted an hour ago with CMW, made backup and flashed Stock ROM from Jovy. Result: bootloop. Restore backup and still on bootloop. DLing the Odin stock .tar to see if it helps. Any more suggestions?
Edit: After flashing with Odin the stock tar from Sammy all it's good...at least for now.
Click to expand...
Click to collapse
How far into the booting process would you get before the phone rebooted?

digitalfiend said:
How far into the booting process would you get before the phone rebooted?
Click to expand...
Click to collapse
Never passed Samsung! In my case, flashing the .tar with Odin from Samfirmware fixed my issue. I think imma wait for a more stable recovery.
Sent from my SM-N900T using Tapatalk now Free

Wally72 said:
Never passed Samsung! In my case, flashing the .tar with Odin from Samfirmware fixed my issue.
Click to expand...
Click to collapse
Interesting...it sounds like you had the boot loop that many others have had...it's cool to hear that you got it fixed. I think my problem was hardware-based since the phone completed it's boot process and *then* had issues. Luckily T-Mobile was there for me and helped out.
Wally72 said:
I think imma wait for a more stable recovery.
Click to expand...
Click to collapse
I know what you mean as far as waiting for a stable recovery. If it's any help, I've decided to stay far away from the recovery restore and simply use Titanium backup to do restores. It's more work than a nandroid recovery, but it reliably does it's job well for me.

digitalfiend said:
Interesting...it sounds like you had the boot loop that many others have had...it's cool to hear that you got it fixed. I think my problem was hardware-based since the phone completed it's boot process and *then* had issues. Luckily T-Mobile was there for me and helped out.
I know what you mean as far as waiting for a stable recovery. If it's any help, I've decided to stay far away from the recovery restore and simply use Titanium backup to do restores. It's more work than a nandroid recovery, but it reliably does it's job well for me.
Click to expand...
Click to collapse
Well...I'm doing a lot of reading. I can't stand this "stock look" and me, every time I root a phone, I always do my own modifications within the ROM I choose to flash. SystemUI and apk's. I only change the .png's, therefore, getting the visual look I want/like. Always done it with certain ROMs/Themes. I downloaded Jovy's stock ROM and made the visual changes I wanted. I flashed and got into that bootloop scenario. Restore backup with CWM provided by Zedomax and made it worse. I think the problem is recovery (at least from what I've read). In this case, CWM been less unstable than TWRP. I f you read a bit around, must ppl if not all, had the "dead bootloop" issue with TWRP. I haven't read from anybody yet having the "dead bootloop" with CWM. Ppl with CWM that flashed their backup and got that bootloop, fixed it flashing back to stock, where ppl that had TWRP have tried to flash back to stock and their phones never boot completely
Again...imma wait a little more for good reports as far as recovery goes!

Bigbiff has a file he uploaded, it may be a fix for the bootlooping issue. You'd be the first to try at this point. It's linked below, but the entire thread is in the OG development of tmobile.
http://forum.xda-developers.com/showthread.php?p=46379854
sgh-TWEAKED-889©

I've never seen so many issues with a brand new flagship phone before. Makes me think it wasn't tested fully before release. I mean all these problems!
Even though I returned my N3 after I tried restoring and getting bootloop of death, I feel this model is really flawed. Hearing new things everyday.

[Q] Rooted 4.3 OTA soft-bricked, wouldn't load any apps

So basically I did this:
http://forum.xda-developers.com/showthread.php?t=2538991
But unfortunately, I hadn't realized that the mobile hotspot was sealed up in that update. So I looked it up, and saw that someone had recommended this:
http://forum.xda-developers.com/showthread.php?p=48326067
So I went into TWRP and installed it. But that didn't work. When I booted back up EVERY app was crashing immediately except the stock Samsung apps (Messaging, Email, etc.). I tried to reverse it with the original framework-res.apk but when I did, the phone would get stuck at the AT&T logo (which was silent). I went back and forth a few times (when I applied that tethering mod, the phone would boot; when I tried to reverse it, it wouldn't), then did a factory reset in TWRP. After that, the phone booted, but the Setup Wizard would crash. So I did a Nandroid restore in TWRP and now the phone hangs at the AT&T logo no matter what I do.
My question is, what can I do now? I have a replacement device coming through warranty just in case, but it would be much better to just fix this one. However, I want to be certain and not HARD brick the phone...

I have never been able to restore a stock 4.3 nandroid without everything crashing. I have always had to go back into recovery and wipe data/factory reset and wipe cache and dalvik cache then reboot and go through the whole setup process again. If that doesn't work you could try installing the stock debloat ROM from this thread. That's what I am running and it works great. http://forum.xda-developers.com/showthread.php?t=2540998
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Iantuition said:
So basically I did this:
http://forum.xda-developers.com/showthread.php?t=2538991
But unfortunately, I hadn't realized that the mobile hotspot was sealed up in that update. So I looked it up, and saw that someone had recommended this:
http://forum.xda-developers.com/showthread.php?p=48326067
So I went into TWRP and installed it. But that didn't work. When I booted back up EVERY app was crashing immediately except the stock Samsung apps (Messaging, Email, etc.). I tried to reverse it with the original framework-res.apk but when I did, the phone would get stuck at the AT&T logo (which was silent). I went back and forth a few times (when I applied that tethering mod, the phone would boot; when I tried to reverse it, it wouldn't), then did a factory reset in TWRP. After that, the phone booted, but the Setup Wizard would crash. So I did a Nandroid restore in TWRP and now the phone hangs at the AT&T logo no matter what I do.
My question is, what can I do now? I have a replacement device coming through warranty just in case, but it would be much better to just fix this one. However, I want to be certain and not HARD brick the phone...
Click to expand...
Click to collapse
if you can get back to twrp , clear everything then flash the official correct file that yu want then see if that works...restore your apps/data after a clean refresh for your phone
remember panicking and being paranoid with flashing/rooting is not a a good idea, always rethink what you did wrong, let the phone cool down, research know what you re doing then fix it
dont rush, cuz rushing leads to bricks (learned from experience from day 1 with root)

bellifritz said:
I have never been able to restore a stock 4.3 nandroid without everything crashing. I have always had to go back into recovery and wipe data/factory reset and wipe cache and dalvik cache then reboot and go through the whole setup process again. If that doesn't work you could try installing the stock debloat ROM from this thread. That's what I am running and it works great. http://forum.xda-developers.com/showthread.php?t=2540998
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
How'd you do that? Just the regular factory reset? Cause the setup wizard wouldn't even run after that.
winosxbuntu said:
if you can get back to twrp , clear everything then flash the official correct file that yu want then see if that works...restore your apps/data after a clean refresh for your phone
remember panicking and being paranoid with flashing/rooting is not a a good idea, always rethink what you did wrong, let the phone cool down, research know what you re doing then fix it
dont rush, cuz rushing leads to bricks (learned from experience from day 1 with root)
Click to expand...
Click to collapse
Okay. Which official file though? and should I clear the system and boot partitions too?

Iantuition said:
How'd you do that? Just the regular factory reset? Cause the setup wizard wouldn't even run after that.
Okay. Which official file though? and should I clear the system and boot partitions too?
Click to expand...
Click to collapse
try this two links, everything on flashing 4.3 stock/rooting and fix http://forum.xda-developers.com/showthread.php?t=2540998
http://forum.xda-developers.com/showpost.php?p=46804338
either one will work
AND dont clear everything just cache/dalvik/format system/ factory reset BUT follow the instructions given for that rom to avoid any problems

winosxbuntu said:
try this two links, everything on flashing 4.3 stock/rooting and fix http://forum.xda-developers.com/showthread.php?t=2540998
http://forum.xda-developers.com/showpost.php?p=46804338
either one will work
AND dont clear everything just cache/dalvik/format system/ factory reset BUT follow the instructions given for that rom to avoid any problems
Click to expand...
Click to collapse
Okay so I just leave boot alone. Let us pray, LOL. And sorry if I've sounded like a supernoob but I'm trying to be REALLY careful.

Iantuition said:
How'd you do that? Just the regular factory reset? Cause the setup wizard wouldn't even run after that.
Hit the power button to make the screen go to sleep. Hit the power button again to wake it up. Nothing should be crashing while you are on the lock screen so just hold the power button until the power menu appears and select power off. Once it powers off hold the volume up, home button and power button until you see the blue words in the upper left corner of the screen I believe it says loading recovery. Release the power button but continue holding the other 2 buttons until recovery loads. Now wipe data, cache and under advanced wipe dalvik cache. Reboot and everything should quit crashing but you will have to setup your account and apps again. That is the only way that I can get stock touchwiz 4.3 nandroids to work.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse

Iantuition said:
Okay so I just leave boot alone. Let us pray, LOL. And sorry if I've sounded like a supernoob but I'm trying to be REALLY careful.
Click to expand...
Click to collapse
it will work, i agree with what bell said. unless its hard bricked then no worries just keep calm and fix the damn phone

Bootloop LG G2 Sprint

Hello everyone thanks for checking out my post for assistance.
I was running the OpTimuS 2.2 yesterday when my phone jumped into a boot-loop. The phone will be on for about 20-40 seconds then reboot. During that time I have no service and when I update the profile I get a message that I don't have any service. I can get into recovery and Download mode. I tried to just wipe and install the rom again. That process resulted in the same boot loop. I have a back up but that was done before the "spark" update and I didn't want to restore that because I know there will be an issue with the radio. I downloaded the stock rooted rom but the phone will not stay on long enough to transfer the file and when I try and load via recovery it will not allow me to transfer the file. (never shows up on computer I might be doing that wrong) I then attempted to bring the phone back to stock following this process http://www.rwilco12.com/forum/showthread.php?tid=96 but when I get down to step 13 the program will not respond anymore. I am going a friends house to try on a different computer but I wanted to get this out there just in case that has the same result.
Thanks again for any info that you could provide.

usvi525 said:
Hello everyone thanks for checking out my post for assistance.
I was running the OpTimuS 2.2 yesterday when my phone jumped into a boot-loop. The phone will be on for about 20-40 seconds then reboot. During that time I have no service and when I update the profile I get a message that I don't have any service. I can get into recovery and Download mode. I tried to just wipe and install the rom again. That process resulted in the same boot loop. I have a back up but that was done before the "spark" update and I didn't want to restore that because I know there will be an issue with the radio. I downloaded the stock rooted rom but the phone will not stay on long enough to transfer the file and when I try and load via recovery it will not allow me to transfer the file. (never shows up on computer I might be doing that wrong) I then attempted to bring the phone back to stock following this process http://www.rwilco12.com/forum/showthread.php?tid=96 but when I get down to step 13 the program will not respond anymore. I am going a friends house to try on a different computer but I wanted to get this out there just in case that has the same result.
Thanks again for any info that you could provide.
Click to expand...
Click to collapse
Flashing back to stock won't work, I had the same thing happened.......it's the EFS Partition (http://forum.xda-developers.com/showthread.php?t=2451390) If you made a EFS Partition Backup, then flashing that will be your best hope.....I didn't make a backup so I went to sprint cuz I have insurance and they are ordering me a new phone

Shadow_God said:
Flashing back to stock won't work, I had the same thing happened.......it's the EFS Partition (http://forum.xda-developers.com/showthread.php?t=2451390) If you made a EFS Partition Backup, then flashing that will be your best hope.....I didn't make a backup so I went to sprint cuz I have insurance and they are ordering me a new phone
Click to expand...
Click to collapse
They replaced it even though your phone was rooted?

Try installing an updated modem for your variant from this thread. It's worth a try.
http://forum.xda-developers.com/showthread.php?t=2451426
If you get it working, definitely make an EFS backup right away.

usvi525 said:
They replaced it even though your phone was rooted?
Click to expand...
Click to collapse
I used the LGFlashTool to bring it back to stock unrooted.......but my phone had no sevice and rebooted every couple minutes, plus the touchscreen wasn't working either.....I told them I took the Spark update and thats when it happened, he said they had alot of issue with touchscreen stopped working and rebooting issue with the spark update......so they didn't look at it long...lol
I have tried back to stock numbers of times....installing modems....restoring my backups....nothing would get it to work, so I gave up and went to sprint...lol

On the rom you were using, have you tried enabling airplane mode to prevent reboots? You could try to get a stock-based flashable zip on the device if possible.

alone-together said:
Try installing an updated modem for your variant from this thread. It's worth a try.
http://forum.xda-developers.com/showthread.php?t=2451426
If you get it working, definitely make an EFS backup right away.
Click to expand...
Click to collapse
Thanks for the option. I was able to install the radio but the issue remains.

usvi525 said:
Thanks for the option. I was able to install the radio but the issue remains.
Click to expand...
Click to collapse
Have we ruled out the possibility to flash a stock ROM in TWRP? If by any chance you have a USB OTG cable, you could try to connect a flash drive with another ROM.

This is my last ditch effort. Small back story: I somehow wiped EVERYTHING on my G2. EFS partition, ESN, data, SIM info., everything with dialer codes. All of my network information reads "unknown". I tried many methods from here on the forums to get this data back and it turns out I have lost my EFS partition- DNA for the network? I sent it to LG to get it fixed, having done a hard reset and leaving no trace of root. They sent it back without even asking and did no repairs. The note said "board bent". WTF?? How does the user bend the main board, especially when I never opened it? They voided my warranty and ripped off my IMEI/MEID sticker from the back of the phone.
Anyways, I am here with a brick. No network still. Here is what I have done:
1) .tot method to ZVC. Several more times... once to ZV7 where I lost touch capability. Luckily saved my arse with a micro->usb cable and a mouse.
2) attempted to root with ioroot25. Failed because the phone WILL NOT find recovery mode. adb, voldown+pwr then again from power off, and apps are unable to force the phone into recovery mode. I assume it is possible that my recovery mode is deleted?
3) Would have tried all of these "rewrite your efs/imei/etc" things but I can't do any without root. Can't root without recovery, can I?
4) Spent the last two weeks scouring the internet for a fix and going back to my Epic 4G temporarily.
Please help me, has anyone seen this before? Can anyone help me fix it? I am to the point where I would pay to have it fixed. Any experts out there? XDA has yet to let me down... I just need to know if I can fix it or if it is a brick so I can go searching for an old Sprint GS3.
Thanks all,
baublitz

[q] frequent frustrating data drops on htc one m7

Hello All,
Due to my endless frustrations, this might be a long one so please bear with me!
So I purchased a Verizon Global HTC ONE M7 from the States, I am currently in Nigeria and the only thing that makes me sadder and more frustrated than the state of my phone right now is the incessant terror attacks in the country! Initially, almost everything worked fine when i popped in my new Etisalat sim card into the phone, except for the mobile hotspot (which just conveniently turns out to be the one of the top 3 most important features in a phone for me - probably the feature I use the most) this message kept popping up about how hotspot couldn't be used without a VZW sim, etc (also with the non-verizon sim warning when the phone boots up). I tried all I could, eventually deciding to flash a new ROM to clear out everything Verizon and start fresh.
Enter Viperone 6.2.0 - everything worked initially, but after a few weeks i noticed if I did anything like watch a youtube video or download something over a few MBs 90% of the time the data drops (no visible signs like changes from E to H or 3g or the likes, everything looks the same, just that the data stops), toggle mobile data on/off and data connection is back. It worsened and became more frequent over time. Upgraded to Viperone 6.2.1, no difference, so i figured its probably the viperone rom.
Enter Cyanogenmod - http://forum.xda-developers.com/ver...-oneplus-one-stock-rom-cm11s-verizon-t2857425 - and its the same exact issue from the beginning, so im guessing its not to do with the ROM at all (though there are one or two niggling issues with the ROM - cant change BBM display pic, etc)?! I've really tried to comb through the forum and see what makes sense that i could try without bugging y'all - I did a factory reset, wiped everything completely and its the same thing.
I've seen suggestions to similar issues like: flash stock recovery, update radio/firmware/kernel, flash back to custom recovery and some other things which are beginning to sound quite dangerous in my ignorance!! I did believe updating the firmware made sense but after digging deeper, i must honestly say i'm quite confused on what to do. what radio/firmware/kernel works with what software version, etc- most firmware that i've seen are 4.4.3 compatible, while this ROM is 4.4.4., some of them seem to be for stock ROMs only and a lot of other confusions.
So, I'm not gonna be a hero and brick my phone from trying to do what i do not understand, instead here i am, hat in hand, crying out for help after suffering for 3 months! Its really frustrating as, downloads break causing me to lose data, skype or MSLync calls always break and im beginning to look unprofessional to people! This is why I have decided to put up a post of my own specific to my case so i don't medicate for someone else's ailments. So please........ WHAT EXACTLY DO I DO??
PHONE DETAILS (typing it out as i've just realized on this ROM i can't take screenshots with Power+Home button combo anymore and can't be bothered at this point!!!)
ANDROID VERSION: 4.4.4
BASEBAND VERSION: 1.12.41.1112_2
KERNEL VERSION: 3.4.82-gfe09065; [email protected] #1; Wed oct 8 01:36:03 PDT 2014
BUILD DATE: SUN AUG 3 23:00:51 PDT 2014
BUILD NUMBER: CYANOGENMOD 11S v5 (Verizon)
SELinux status: Enforcing
Thanks

Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.

Can you flash stock recovery from Santod's firmware thread and do a factory reset? It could be a corrupt nv partition which would only be fixed by doing a factory reset via stock recovery. (If you must, make a nandroid of system and data in your recovery of choice so you can restore your data if you wish).

Uzephi said:
Can you flash stock recovery from Santod's firmware thread and do a factory reset? It could be a corrupt nv partition which would only be fixed by doing a factory reset via stock recovery. (If you must, make a nandroid of system and data in your recovery of choice so you can restore your data if you wish).
Click to expand...
Click to collapse
Thanks for the responses folks, i'll try out your suggestions and revert..

8100
brymaster5000 said:
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Click to expand...
Click to collapse
So.. i found time to get to this and decided to go with your suggestion of Santod's stock rom... and now, i think i've done the unthinkable!! After WIPING EVERYTHING "All partitions except SD!" as the instructions stated... i attempted to reboot into bootloader and got a message saying "no OS installed, are you sure you want to reboot"... that scared me a bit, but i thought surely, it must be part of the process! I proceed to reboot to bootloader to flash the firmware and i cant seem to do anything!!
Fastboot is stuck on " waiting for device" for everything i try.
Also, i rebooted back into recovery and attempted to install the stock rom: i get the error message "unable to open zip file"..
Have i destroyed my phone with my own hands, people? :crying:

Mr HaRR said:
So.. i found time to get to this and decided to go with your suggestion of Santod's stock rom... and now, i think i've done the unthinkable!! After WIPING EVERYTHING "All partitions except SD!" as the instructions stated... i attempted to reboot into bootloader and got a message saying "no OS installed, are you sure you want to reboot"... that scared me a bit, but i thought surely, it must be part of the process! I proceed to reboot to bootloader to flash the firmware and i cant seem to do anything!!
Fastboot is stuck on " waiting for device" for everything i try.
Also, i rebooted back into recovery and attempted to install the stock rom: i get the error message "unable to open zip file"..
Have i destroyed my phone with my own hands, people? :crying:
Click to expand...
Click to collapse
FALSE ALARM FOLKS!!! I decided to attempt flashing the CM11 rom i just uninstalled and it worked. Turns out its a known issue with the .zip file for that rom - i am now re-downloading from another mirror. Meanwhile the Fastboot thing was just a driver issue - though i'm surprised because i had all the drivers installed on the system and have used fastboot successfully - anyway i reinstalled the drivers and all was well with fastboot again.
NB: Don't get tired of me just yet please!

brymaster5000 said:
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Click to expand...
Click to collapse
hello!
Thanks for your ideas guys. I'm currently running Santod's stock rom (which is brilliant, i must say, i actually wanna stay on this rom) since friday - thought i'd give it the whole weekend and see how it goes.. BUT! i still get thoseconnection drops.. and frequently too.
Any other ideas on what the issue could be?

Mr HaRR said:
hello!
Thanks for your ideas guys. I'm currently running Santod's stock rom (which is brilliant, i must say, i actually wanna stay on this rom) since friday - thought i'd give it the whole weekend and see how it goes.. BUT! i still get thoseconnection drops.. and frequently too.
Any other ideas on what the issue could be?
Click to expand...
Click to collapse
If doing factory reset from stock recovery doesn't fix it, it is most likely a burned SIM. It has happened to me. (Average 150+ GB a month in data, so I burn em easily)
Sent from my HTC6500LVWBLU using XDA Free mobile app

Uz has it right, you need to flash a stock recovery and THEN do a factory reset, then reload your custom recovery and rom. I had the exact same issue before. Or you could flash an ruu file which would reset the partitions also.

ccarr313 said:
Uz has it right, you need to flash a stock recovery and THEN do a factory reset, then reload your custom recovery and rom. I had the exact same issue before. Or you could flash an ruu file which would reset the partitions also.
Click to expand...
Click to collapse
Hey folks, apologies for the touch and go nature of this thread - i just don't have a lot of free time on my hands and other reasons..
Anyhow, i think I want to try out ur suggestion of flashing an RUU - I noticed that im unable to actually enter recovery after flashing stock recovery from Santod's thread (i flashed the latest three recoveries). I can get to bootloader, but when i select recovery, the phone goes black for a few seconds and then i get the RED TRIANGLE WITH THE EXCLAMATION MARK INSIDE, obviously something's wrong, few seconds later the phone reboots itself into normal mode. I did do a factory reset from bootloader, but issue persists.
So now to the RUU flashing issue - could you suggest one for me to flash?
By the way though, isn't flashing an ruu gonna take me back to stock completely (as in back to S-ON, ETC..)?
Thanks a whole bunch - IM DETERMINED TO GET THIS TO WORK!!!

Mr HaRR said:
Hey folks, apologies for the touch and go nature of this thread - i just don't have a lot of free time on my hands and other reasons..
Anyhow, i think I want to try out ur suggestion of flashing an RUU - I noticed that im unable to actually enter recovery after flashing stock recovery from Santod's thread (i flashed the latest three recoveries). I can get to bootloader, but when i select recovery, the phone goes black for a few seconds and then i get the RED TRIANGLE WITH THE EXCLAMATION MARK INSIDE, obviously something's wrong, few seconds later the phone reboots itself into normal mode. I did do a factory reset from bootloader, but issue persists.
So now to the RUU flashing issue - could you suggest one for me to flash?
By the way though, isn't flashing an ruu gonna take me back to stock completely (as in back to S-ON, ETC..)?
Thanks a whole bunch - IM DETERMINED TO GET THIS TO WORK!!!
Click to expand...
Click to collapse
That is in fact stock recovery man. When you get the triangle press volume up and power at the same time. You will enter stock recovery.
Any of my ruu will run fine. You won't lose s-off or unlocked status. You flash them in boot loader fastboot mode.

dottat said:
That is in fact stock recovery man. When you get the triangle press volume up and power at the same time. You will enter stock recovery.
Any of my ruu will run fine. You won't lose s-off or unlocked status. You flash them in boot loader fastboot mode.
Click to expand...
Click to collapse
HA! and now i feel :silly: !!
Bless your soul! i'll give it a go shortly...

Sprint GS3 wifi not turning on

Hello. When my device was updated to KitKat, the WiFi stopped turning on. It doesn't fail to connect, it just will not turn on at all. I tried an app called "WiFi Fixer", which didn't work, but in the "Known Issues" section it said this was caused by the "Android framework not interacting with the WiFi driver" and said to flash a custom ROM.
I rooted, installed TWRP, and flashed CM 12.1 successfully. The WiFi still wouldn't turn on. I then decided it was probably a hardware issue that coincidentally showed itself at the same time as the update. So then, I installed Cheetah Mobile launcher, and one of their themes, and was resigned to not having WiFi.
I got bored with the CM theme, and installed the Dark Material theme. At this point the phone started acting buggy, not waking from wakelock, force closing, and randomly rebooting. So i then deleted cache and dalvick cache, and re-flashed from the CM 12.1 zip i had saved on my SD. The bugs would not stop, almost making my phone unusable. The only bright side of this was that my WiFi was turning on and working! I thought maybe the hardware problem had fixed itself somehow, but I still wanted to have a usable phone. I kept re-flashing from the existing CM 12.1 zip, the WiFi kept working, but the buggy behavior wouldn't go away.
I figured that maybe the CM 12.1 zip on my SD was corrupted, so I downloaded another copy from CyanogenMod, installed it on my SD, and erased the old copy. Then, I wiped everything and re-flashed with the new zip. The buggy behavior went away, but WiFi stopped working again! I'm thoroughly confused now.
If it's a hardware issue, why does it come and go with ROMs/ themes? I thought it may be a kernel issue, so I flashed Ktoonsez K747 kernel, which is working fine, but I still don't have WiFi. Did the themes I installed earlier change the kernel in some way to make my WiFi work temporarily? Is there a fix for this? Is it a known problem? I researched the forums but the only answers I found for similar problems were from earlier versions (2013) of Android/ CyanogenMod ROMs.
At this point, I'm willing to give anything a try, I've even opened the phone, inspected, un-plugged, and replugged the WiFi antenna. If it was a hardware issue, would I expect to see any damage, like a fried circuit or something? Is there any test to check if it's hardware vs. software?Can I buy a replacement antenna?
I'm pretty broke and can't afford a new phone, which is why I'm trying to resuscitate this one When it works, it's sufficient for my use.
Please help, I really want WiFi back! Thanks in advance for any advice.

Full odin back to stock. Best solution.
Get odin here at the bottom of the page. The firmware is there too. If you create a free account the download goes much faster.
Also, re flashing the same cm12.1 over and over won't help. Have you tried the newest nightly? After odin back to stock, if you want cm, use the latest.
If you don't have a pc, you can try flashfire, but I haven't tried it.

madbat99 said:
Full odin back to stock. Best solution.
Get odin... at the bottom of the page. The firmware is there too. If you create a free account the download goes much faster.
Also, re flashing the same cm12.1 over and over won't help. Have you tried the newest nightly? After odin back to stock, if you want cm, use the latest.
If you don't have a pc, you can try flashfire, but I haven't tried it.
Click to expand...
Click to collapse
Thanks, I'm downloading it now. Does it matter that this is an older build? I started with L710VPUDOH1, but this download is a previous version, L710VPUDNJ2.
I found this, which has the L710VPUDOH1 build in a zip...
Google > "L710VPUDOH1 opensource samsung" > first result (I'm too new on XDA to post outside links!)
within the zip is Kernel.tar and Platform. tar. which I have done nothing with, as I'm not sure if it's what I need. Do you think I should flash these? or just go with the NJ2 build?
Thank you for your insight, and taking the time to help me!

dieseldeeznutz said:
Thanks, I'm downloading it now. Does it matter that this is an older build? I started with L710VPUDOH1, but this download is a previous version, L710VPUDNJ2.
I found this, which has the L710VPUDOH1 build in a zip...
Google > "L710VPUDOH1 opensource samsung" > first result (I'm too new on XDA to post outside links!)
within the zip is Kernel.tar and Platform. tar. which I have done nothing with, as I'm not sure if it's what I need. Do you think I should flash these? or just go with the NJ2 build?
Thank you for your insight, and taking the time to help me!
Click to expand...
Click to collapse
No. For many reasons. First, its not the rom, its just the update. No one has made a flashable rom zip. Second, official updates won't flash in custom recovery and it would never flash because you're rooted.
So basically its not the full rom, its the official update zip, just a patch.
Gotta flash a .tar. Unless your on the triband model, nj2 should be fine

madbat99 said:
No. For many reasons. First, its not the rom, its just the update. No one has made a flashable rom zip. Second, official updates won't flash in custom recovery and it would never flash because you're rooted.
So basically its not the full rom, its the official update zip, just a patch.
Gotta flash a .tar. Unless your on the triband model, nj2 should be fine
Click to expand...
Click to collapse
Flashed back to stock, and updated to OH1 successfully, but still no wifi. It's greyed out and won't turn on
I would think it was a hardware problem, except that it all started when my phone updated to 4.4.2. I've found many others with this problem online, but no fixes. Can I flash back to 4.3? or can I flash a new modem/radio(?) file. I thought I saw one in my searches but can't seem to find it now
Thanks again

dieseldeeznutz said:
Flashed back to stock, and updated to OH1 successfully, but still no wifi. It's greyed out and won't turn on
I would think it was a hardware problem, except that it all started when my phone updated to 4.4.2. I've found many others with this problem online, but no fixes. Can I flash back to 4.3? or can I flash a new modem/radio(?) file. I thought I saw one in my searches but can't seem to find it now
Thanks again
Click to expand...
Click to collapse
No, do not try to flash 4.3. You will hard brick, and your phone will be a paperweight. Same thing if you try flashing any pre Knox modems/radios.
Are you flashing something else with this? It's something on your device if a tar flash in odin didn't fix it. Did you factory reset after odin?

madbat99 said:
No, do not try to flash 4.3. You will hard brick, and your phone will be a paperweight. Same thing if you try flashing any pre Knox modems/radios.
Are you flashing something else with this? It's something on your device if a tar flash in odin didn't fix it. Did you factory reset after odin?
Click to expand...
Click to collapse
Yes, I factory reset, cleared all caches, rebooted into safe mode, changed wifi settings in service mode... did an ancient Indian wifi fixing dance, spoke soothingly to it, then cursed at it :laugh: maybe it's a hardware problem with coincidental timing that's also happened the same exact way to other people

dieseldeeznutz said:
Yes, I factory reset, cleared all caches, rebooted into safe mode, changed wifi settings in service mode... did an ancient Indian wifi fixing dance, spoke soothingly to it, then cursed at it :laugh: maybe it's a hardware problem with coincidental timing that's also happened the same exact way to other people
Click to expand...
Click to collapse
Lmao, funny. I heard it happening to people a while back. Can't remember what caused or fixed it. Some fixed it with custom kernel but the kernel is waaay outdated now. But it was kt747 by ktoonsez. But its so old. What carrier are you on? Sprint, virgin Mobile, boost?

madbat99 said:
Lmao, funny. I heard it happening to people a while back. Can't remember what caused or fixed it. Some fixed it with custom kernel but the kernel is waaay outdated now. But it was kt747 by ktoonsez. But its so old. What carrier are you on? Sprint, virgin Mobile, boost?
Click to expand...
Click to collapse
I'm on Sprint.

this just happended to me the other night actually, did you find solution? Apparently just taking out the battery and resetting solved it for a lot of people, but not me. I will tell you what did work though! (keeps randomly doing it again but at least i can gfet it to work aghain even if only for a littlw bit)
First check with root explorer if you have this fike "data\misc\wifi\wpa_supplicant.conf "
I guess it has something to do withthis file, and your android not writing to the right spot, but i honestly have no idea so ill continue. what i did (i saw i didnt have the file either) i dialed *#0011# then hit menu, and then hit wifi, and turned off the bottom switch "wifi power save mode". I exited service menu tried wifi a couple times still same thing, so i went back into service menu and reenabled the switch, then i turned off the phone by pulliung out battery. I logged into my custom recovery and checked out the file explorer in twrp, and voila there that mysery file was! So i cleared dalvick and cache, rebooted into rom, (wicked x v8.2) and attempted wifi and it was working again. so take whatever conclusion youd like but im too tired to keep my eyes open at the moment and good luck, pissed me off cuz wifi was all i had no service, of course

skinnykinney said:
this just happended to me the other night actually, did you find solution? Apparently just taking out the battery and resetting solved it for a lot of people, but not me. I will tell you what did work though! (keeps randomly doing it again but at least i can gfet it to work aghain even if only for a littlw bit)
First check with root explorer if you have this fike "data\misc\wifi\wpa_supplicant.conf "
I guess it has something to do withthis file, and your android not writing to the right spot, but i honestly have no idea so ill continue. what i did (i saw i didnt have the file either) i dialed *#0011# then hit menu, and then hit wifi, and turned off the bottom switch "wifi power save mode". I exited service menu tried wifi a couple times still same thing, so i went back into service menu and reenabled the switch, then i turned off the phone by pulliung out battery. I logged into my custom recovery and checked out the file explorer in twrp, and voila there that mysery file was! So i cleared dalvick and cache, rebooted into rom, (wicked x v8.2) and attempted wifi and it was working again. so take whatever conclusion youd like but im too tired to keep my eyes open at the moment and good luck, pissed me off cuz wifi was all i had no service, of course
Click to expand...
Click to collapse
I have that file on my phone. So I understand, you originally didn't have that file, but after doing the steps you listed it magically appears, and then wifi works? I really wish I could get it to work. Also, you said it keeps happening... so the file keeps dissappearing on you? Thanks for the response.