This issue is mostly present on AOSP 4.3> ROMs. It occurs randomly and if I look in the logcat it says "WifiStateMachine: Failed to load driver". Then, when I try to turn wifi on nothing happens. The slider goes to the right but stays grey. And if i go out and then back to settings the slider is back to the off position again. In the logcat it just says "Turning on wifi: True" or something but nothing happens since the drivers failed to load.
Anyone who knows what's causing this? I have tried different modems, ROMs, old and knox bootloader but it seems to be coming back.
InvisibleBow said:
This issue is mostly present on AOSP 4.3> ROMs. It occurs randomly and if I look in the logcat it says "WifiStateMachine: Failed to load driver". Then, when I try to turn wifi on nothing happens. The slider goes to the right but stays grey. And if i go out and then back to settings the slider is back to the off position again. In the logcat it just says "Turning on wifi: True" or something but nothing happens since the drivers failed to load.
Anyone who knows what's causing this? I have tried different modems, ROMs, old and knox bootloader but it seems to be coming back.
Click to expand...
Click to collapse
I got the same error after installing cm-13.0, have you figured it out how to rectify this?
Some ROMs require the phone to be using the latest bootloader and modem which means the phone may be running a modem and bootloader that are outdated.
Related
I too have a focus that is stuck in a loop at the Samsung logo. I bought it like that thinking I might be able to resurrect it as another toy. I have had lots of experience with Samsung, HTC and Sony droid phones, this would be the first WP.
It is a I917R on Rogers, there is no hardware revision under battery. I am assuming it is V1.3 as I have only seen software for the that version posted. I do not know how the phone got to its present state. They just said it happened during normal use?
I can get to both download mode and factory reset. I have flashed the stock rogers files without errors, but I never get the screen connecting to pc. The phone just restarts after successfully flashing, only to reboot continuously. I have been able to install MAGLDR and flashed every v1.3 ROM i could download. All without errors, just the same outcome they all just keep displaying Samung logo and then reboot. Only thing I noticed is that when I flash MAGLDR and custom ROMs it takes the phone longer to reboot.
I never get the connect to pc if I hold camera and power, nor do I ever get that screen when I flash a ROM.
Not sure if situation is similar... I am puzzled?
Your situation is very similar with other folks' here, unfortunately. It's not clear what causes it and there's no solution as of yet. For some, re-flashing worked. For others, a new battery. Most are stuck on loop...
When you connect the phone to USB when in download mode, what do you get?
When I boot to download mode I can flash Rom with WP7. I get to the yellow triangle download mode and flashes ok, no errors. Just noticed that it never goes to connect to pc mode.
Same with when I format, no connect to pc mode.
Nothing I try seems to help.
blackangel21 said:
When I boot to download mode I can flash Rom with WP7. I get to the yellow triangle download mode and flashes ok, no errors. Just noticed that it never goes to connect to pc mode.
Same with when I format, no connect to pc mode.
Nothing I try seems to help.
Click to expand...
Click to collapse
I see. What messages do you get when you connect the phone to the PC via USB, in either mode?
No messages, just shows up as Samsung USB composite device, Samsung mobile modem and Samsung mobile modem diagnostic serial port in download mode.
In magldr it shows up add Microsoft USB sync.
The only thing I forgot to mention was that when I flash with WP7 it finished without error in 90 seconds, but on the phone it says it will take 10 minutes.
Not sure what more I can add...
You could try different downloaders. Please see this thread for 7.41 downloader, maybe that helps?
Tried both, same outcome... No errors, just keeps rebooting... No Connect to PC message.
Im having the same problem. And i can see many other people who are having the same issue also. So i think its time to dump those phones, not worth a penny. The one i have in here was actually working, i followed all the directions in order to flash it. And still the phone got stuck into that bootloop. Its ridiculous from what i can see. I think ive read once you put that SDmini in it the phone will use it for the OS. But the one i had was working actually without it, i could turn it off as many times as i wanted and nothing happened. But if i tried a factory reset data would stay and diagnosis mode wasnt working. So i decided to flash it. Big, huge mistake! Hope you have better luck than i did. Because im dumping this one....
Same problem here, ive checked a couple of threads and no solution so far
I have just received a s4 with a really confusing problem . When you power the phone on normally it displays a weird semi solid green screen but when you boot into download mode everything displays perfectly. Also while phone is off if you connect charger it displays the battery icon perfectly. Phone is 100% stock dont know what rom/baseband version was installed. Green screen also in recovery mode. Phone does not have usb debugging enabled nor is it rooted. Can anyone help?
Download Mode says
ODIN MODE
PRODUCT NAME SCH-I545
CURRENT BINARY Samsung Official
SYSTEM STATUS Official
KNOX KERNEL LOCK 0x0
KNOX WARRANTY VOID 0x0
CSB-CONFIG-LSB 0x30
WRITE PROTECTION Enable
eMMC BURST MODE enabled
If you're able to get into download mode, download the latest stock firmware and install it to see if that corrects the problem. There should be a link for the stock firmware in the Verizon Galaxy S4 forums, along with other aids that may be of use to you. Installing the firmware is a must, because it will either correct the problem you're having, or it will reveal the problem to be deeper, and likely hardware related.
In the unlikely event that the stock firmware is not available on the forums, you can get a copy from either sammobile.com or samsung-updates.com.
I dont know what version was previously installed I tried flashing twrp via odin it comes back as failed because of a auth error. I think the bootloader may be locked if it isnt I dont want to upgrade only to learn bootloader was previously unlocked and I just locked it up by updating. It seems to me if this is a hardware related problem I would think the phone would be green screen in download mode and while charger plugged in? Any suggestions on which android version to try first?
You clearly didn't read my previous post. That pisses me off, because now I'm having to repeat myself when I should NEVER have to.
If you want to brick the S4, then continue doing what you were doing. Otherwise, pay attention, because at no point did I ever mention downloading and installing TWRP. I did however mention downloading and installing the STOCK Verizon S4 ROM from the Verizon S4 forums. You will use Odin to install the ROM. If the Verizon S4 forums do not have a link to the stock Verizon S4 ROM, you are to download the latest copy of the ROM from either sammobile.com or samsung-updates.com. It doesn't matter one whit what was on there before, because by installing the stock ROM you were supposed to have downloaded, you will have the S4 at a known starting point so you can truly diagnose the problems it may have.
AT&T and Verizon bootloaders are locked, thus you cannot just install a recovery and expect it to work. Installing a stock ROM however will work since all the components are verified by Verizon. In installing the stock Verizon S4 ROM through Odin, you will make sure you are using a proper cable, do not have the S4 connected through a hub, will make sure the Samsung USB drivers are installed (available at Samsung's website), and either do not have Kies installed, or have Kies disabled.
Sorry I have flashed the latest official verizon firmware and odin said pass, everything went perfect. Phone restarted and again hazy green screen returned. Still cannot veiw anything in recovery or normal mode, safe mode does not help either. Download mode and battery charging still show up perfectly fine. Any help would be greatly appriciated.
It's hard to think of this as a hardware issue, but I believe you have one. As strange as it may seem, the issue is not with the screen itself, but the GPU.
Using Windows equivalents, Download Mode is "Safe Mode with Command Prompt" while Safe Mode is just like Windows' "Safe Mode". "Safe Mode with Command Prompt" dumps you to the command line, i.e. DOS. It doesn't need a GUI so it doesn't have drivers loaded to support it. "Safe Mode" has a GUI so it has to load drivers to support that.
On the S4 the concept is similar, only the drivers are called "libraries". Download mode doesn't use a GUI as it's part of the bootloader, so it doesn't need the GPU, thus it doesn't need the GPU library. This is why download mode functions. The other modes all have a GUI, which requires the GPU and a library for the GPU loaded. Since the GPU has failed you get the green screen instead of what you should see. The library itself isn't the culprit because if it were, loading a new ROM as you had would have fixed the problem. The screen isn't the culprit because the screen works correctly in download mode. If it were the screen, the green would appear in Download Mode as well as the other modes. Therefore the GPU is most likely the problem.
Unfortunately, that means a new motherboard, on top of trying to remove the glass for replacement.
PROBLEM ALMOST FIXED!!.. Well kind of, i seperated the broken glass from the screen and placed the phone in the freezer. An hour or so later i pulled the phone back out of the freezer and switched it on everything worked perfect i switched on usb debugging and rooted the phone using towelroot and safestrapped it. when i updated supersu i had to reboot the phone and then again green screen i also noticed the phone had gotten really hot. I tried the freezer trick again and the phone turned on like normal no green screen. Does anyone know what maybe causing this issue???
Thank you very much for all the help and info you have given me i really do appriciate it
Bad GPU, as previously stated, though there are two other possibilities I can think of. The first is that GPU has a bad connection to the motherboard that manifests when heated. Or else the motherboard has a stress fracture that manifests when heated. The latter has happened with other devices but is not common. A solder reflow of the GPU could cure the former problem.
Before I give the reflow a shot I wanted to mention another piece to this puzzle. When the phone is working fine as long as the screens backlight is on the phone will display everything correctly as soon as it turns off and you turn it back on green screen. It doesn't matter if you wait two minutes or 20 minutes. Dont know if thathelps narrow down culprit
It doesn't narrow things down any.
the solution
you need to change your battery than you install the firmware using odin than you download antivirus. :good:
So apparently, I went home and usually put my phone into my desk.
While I took it from my pocket, I noticed the hardware buttons were lit but no display, I removed the battery to restart, during the week, frozen screen were occurring a dozen times when playing Clash, that though I didn't mind I just said to myself I will reflash the rom in the weekend.
But up to now,
It won't turn on, recovery mode or anything also doesn't work
It wont charge
Tried a new battery but still no luck
I think PC reads it but SPFT wont
Any suggestion on how I can revive my phone?
Attached is the error I get from SPFT
I don't own the A120 anymore. That is almost similar to this, as you might know.
Anyway, as nobody has answered your question, I will try to help as much as I can.
Does it give you a haptic feedback(vibration) when you try to power on the device?
Are you saying that it won't turn on completely?
If it is being detected on the computer and not on SPFT, you might want to check with the drivers you have. Do you have the MTK VCOM drivers installed? (I'm not really sure about the name, but it was something like that).
And try flashing the Stock ROM with SPFT with your battery removed from the phone.
Download the drivers.
Connect your phone without the battery and keep your device manager open, if it shows a device with a yellow exclamation mark beside it, right click and click on properties. You will have to do this quickly.
Once that is done, go to driver tab on the properties window. Select Update Driver. Browse my computer and enter the location of your downloaded and unzipped drivers.
(You might get a digital signature error or something similar. I'll tell you how to bypass that in the end. If you get that, go to the end, follow those steps and then come back and do all the steps after the downloading part.)
If the drivers are successfully installed, then unplug your device, run the SPFT and load the Scatter file of the Stock ROM.
Now select Download only and start the download, it will wait for you to connect the phone.
Plug in your phone without the battery. This should initialize the download process.
Now wait for the flash to be completed and if it is successful, take out your phone and boot it. If it boots up, congratulations.
If it does not, flash the same ROM the same way another time and check, if it is still not working, try with Firmware upgrade mode, twice. It should work in those tries.
Digital Signature Error bypassing.
I know only one method which works on Windows 8 and above(Tested).
Hold the Shift key while pressing Reboot.(Yes, you have to reboot your PC)
Once there is a blue screen with options, you should see "Troubleshoot". Select that.
Then Advanced Options and then Start Up settings. Then press Restart.
This will show you a menu with a lot of options. Select the option number which says "Disable Driver Signature Enforcement".
This will log you into the PC normally, but now, you can go back and do all the steps again and you won't get an error.
Cheers!
If this still doesn't help you, let me know on what happens so I can try to get you back your phone. Hope this helps.
WalterWh1te said:
I don't own the A120 anymore. That is almost similar to this, as you might know.
Anyway, as nobody has answered your question, I will try to help as much as I can.
Does it give you a haptic feedback(vibration) when you try to power on the device?
Are you saying that it won't turn on completely?
If it is being detected on the computer and not on SPFT, you might want to check with the drivers you have. Do you have the MTK VCOM drivers installed? (I'm not really sure about the name, but it was something like that).
And try flashing the Stock ROM with SPFT with your battery removed from the phone.
Download the drivers.
Connect your phone without the battery and keep your device manager open, if it shows a device with a yellow exclamation mark beside it, right click and click on properties. You will have to do this quickly.
Once that is done, go to driver tab on the properties window. Select Update Driver. Browse my computer and enter the location of your downloaded and unzipped drivers.
(You might get a digital signature error or something similar. I'll tell you how to bypass that in the end. If you get that, go to the end, follow those steps and then come back and do all the steps after the downloading part.)
If the drivers are successfully installed, then unplug your device, run the SPFT and load the Scatter file of the Stock ROM.
Now select Download only and start the download, it will wait for you to connect the phone.
Plug in your phone without the battery. This should initialize the download process.
Now wait for the flash to be completed and if it is successful, take out your phone and boot it. If it boots up, congratulations.
If it does not, flash the same ROM the same way another time and check, if it is still not working, try with Firmware upgrade mode, twice. It should work in those tries.
Digital Signature Error bypassing.
I know only one method which works on Windows 8 and above(Tested).
Hold the Shift key while pressing Reboot.(Yes, you have to reboot your PC)
Once there is a blue screen with options, you should see "Troubleshoot". Select that.
Then Advanced Options and then Start Up settings. Then press Restart.
This will show you a menu with a lot of options. Select the option number which says "Disable Driver Signature Enforcement".
This will log you into the PC normally, but now, you can go back and do all the steps again and you won't get an error.
Cheers!
If this still doesn't help you, let me know on what happens so I can try to get you back your phone. Hope this helps.
Click to expand...
Click to collapse
Thanks bro, but I already gave up and bought a new one because I badly need an android device for my mini accounts in CoC. Haha but I am till trying to revive my Rio during my free time, this has been my phone for 1 1/2 year..
Yes I am aware that Rio is rebranded A120, I also asked from CM12.1 and AOSP LP Wiko Rainbow threads and some suggested help. Tried all that but still same errors.
No, there's no response of any kind including vibration when turning on. Hmn, as per the drivers, I've been using Tinno Driver since the jelly bean era of this phone, no problems or whatsoever from jb to kk to lp using that driver, so I thought there would be no problems. Still no luck in getting success. Using different versions of SPFT, using sp flashable Rio jb, kk, MMX A120 jb, kk, Wiko kk,lp stock roms, still no luck. Tried every port and cord. And I am using the Win7 64bit, I also resorted to MTK drivers, both the preloader and Da. Still.. No luck. Haha. I also tried, download only, format all+download, and firmware upgrade option with every possible combination from above but no success..
Thanks for your answer btw!
My Axon 7 Mini developed an odd issue today. Normal use, then it rebooted and shows the Axon screen for ages, before then showing an error message stating that Telephone has stopped. Click okay and it says System UI stopped. Then back to telephone, and an endless loop until it reboots (presumably a watchdog somewhere). The same happens in safe mode.
No changes from the ZTE stock - this is running 6.0.1. I didn't enable USB debugging before, and I can't now as I can't get any kind of functional UI. Booting into recovery mode is possible, but without USB debugging enabled, I can't do much there. I've tried clearing the cache from the recovery mode, but that made no difference.
Does anyone have any suggestions as to what might have gone wrong? And / or, how I can pull the files off the device?
Thanks,
Allan
Have you tried a factory reset?
Possibly use one of the stock firmware files found in the development section to upgrade to nougat?
Yup - was hoping to avoid that, but I've just done that and it works after a reset.
Thanks for your reply!
Hello guys, I have this weird A3000-H problem.
So the tablet boots normally, it loads in one particular state every time, like it's booting an image. After a while or if you try to do something, running a program, uninstalling, changing settings it's starts the cascade of pretty much "every has stopped working" and it's like that until you restart it and it's all over the same again.
So far I've tried everything I could scour from the internet, XDA forums included.
• I've tried to flash new stock rom 4.2.2, then I tried the 4.4.2 from Hesham.
If I use an older, version 3 SP Flash Tools it gives me this error at the end:
imgur com a5oKTLw.png
If I use version 5+ of SP Flash Tools it gives me an "OK" download or upgrade, but when I disconnect and turn on the tablet it's in it's same previous state, it didn't change anything.
• I tried full format - it did absolutely nothing despite SPFT giving me the okay
SPFT memory test returns this error : .imgur com / jbSUwV5.png
• I tried writing memories - nothing changes despite getting on OK message.
• I tried to fastboot CWM - I can't make the tablet to enter the mode, it just restarts and boots in it's previous state.
• I've tried to connect it to PC and delete folders manually, despite windows saying the folders are deleted and not showing them anymore, as soon as I reconnect the tablet again they show up as they were. It's like the on board memory is locked to writing anything on it.
• Of course I tried manually resetting to factory settings, uninstalling software from the tablet and so on, but that just makes the errors of "stopped working" to pop and restart to same condition.
I would appreciate any help at this point, I'm about to give up on it.
P.S.: I can't post whole links yet so I had to improvise a bit.