Database Develop

[Q] wifi error and incorrect username

Hello all,
i have a motorola droid 3 for about 4 months. and since january, the wifi can't turned on, it says error. i already tried to switch the network, pull off battery, use a wifi recovery app, and even install another rom, but nothing works. i also have problems in social application as there is incorrect password problem. i already tried all the solution i can found, but same like the wifi problem, nothing works.
i can't go to verizon because i bought the phone online.
can anyone helped me for those problems?
there are leaked version rom (902 and 905), are those rom can fix my problems?
thank you for all your help
ps : for moderator, if this thread want to be merged or moved, please do. i still don't really know where to post. thanks

I'd try to SBF to stock, if it still doesn't work on no wifi at all then it sounds like hardware failure

is this how to do sbf flash?
http://forum.xda-developers.com/showthread.php?t=1255198
i already tried psouza4's 890 update script (forgot the link) a couple weeks ago and still not worked

If you're on .890 i'd just use this:
http://forum.xda-developers.com/showthread.php?t=1339816
file mirror:
http://dl.dropbox.com/u/61707107/Ve...izon+DROID+3+OTA+5.6.890+to+phone_psouza4.zip

ok..i'm gonna try it tonight.
thanks for the link and mirror

good job
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

already use the link above. and the result is...the wifi still error
and for the social application problem, i need a few days to check it. usually it shows incorrect password or username after 3 days.
any other solution guys??

zeigk said:
already use the link above. and the result is...the wifi still error
and for the social application problem, i need a few days to check it. usually it shows incorrect password or username after 3 days.
any other solution guys??
Click to expand...
Click to collapse
Well if you flashed to stock with SBF, how could it be a software issue? I haven't had the problem, ever. *knocks on wood*.
I'd try some other wifi connections

i can't try other wi-fi because mine just won't turned on. even though i already change places to different wi-fi area, but my wi-fi still won't turned on.

zeigk said:
i can't try other wi-fi because mine just won't turned on. even though i already change places to different wi-fi area, but my wi-fi still won't turned on.
Click to expand...
Click to collapse
Oh..right. My sisters galaxy ace has that same problem. Sometimes rebooting fixes it for her sometimes it doesn't . I don't know what you could try.. Perhaps you could flash one of the newer OTAs with kernel/baseband changes, but might be risky

Yeah...i actually want to flash with 905 ota leak, hope it can fix my wifi problem. But i'm gonna wait a while for it becoming official (hope it soon)
Sent from my DROID3 using XDA App

It's already 3 days. When i want to add social account, it says incorrect username again.
Anyone have any idea on fixing the problem?
Sent from my DROID3 using XDA App

[HELP] Weird / Random Nexus 6 crashes (see images)

So i've been facing this issue on the Nexus 6 for a long time now. It was there even when i was running stock.
Current state : Rooted, Chroma ROM 5.0.2
Issue count (daily) : 4-5 times
The problem : Random crashes. There is nothing specific that seems to trigger it. Dont know whether this is a memory leak issue or not.
When the devices crashes / freezes, a glitch distortion appears on screen, rendering all keys except power useless. A forced restart is the only way to get back.
Please follow the images for better understanding :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Questions :
1) Is this a common issue?
2) Should i relock the device and get it exchanged?
3) If i cant exchange it, what should i do?
Thanks.

Thats never happened to me on stock or CM12....
I would contact who ever you bought it from motorola, google , or a carrier and get it replaces you have the year warranty and the pictures you took can be your proof? ...

same issue
I have same issues friend, from the first day. Now i flash latest 5.1 and testing. if i have it again i'll return my device

After testing lollipop 5.1 muy phone freeze again with same distorsión on screen. Its a fresh flash from factory images. I think i RMA because i dont know what cause this

I had the same issues, it happened randomly usually while using the camera or texting with Textra. I was using Liquid Smooth.
I flashed the latest Rebased version of Liquid Smooth and havent had a crash in over a week now. Hope this helps.

Thanks friend, im going to try líquid smooth

mistermoha said:
Thanks friend, im going to try líquid smooth
Click to expand...
Click to collapse
Did it work for you? Crashes have lessened on my chroma 5.0.1 flash but still not sure about whether the issue is fixed or not. Hell, i dont even know what this is :crying:

Wrong Colors

Hello there!
i'm observing a irritating display/color problem on my Xperia Z1(Screenshot, yes these pink things aren't supposed to be there and they don't change their position in the picture(!) if i flip the device. According to the background they also appear in green, blue and red; they change only positions if i change the overall portion of green color in the settings).
How the problem occured: A few days ago my girlfirend droped my phone and the glas broke. (touchscreen was also defect nothing more; still controlable via mouse) Instead of repairing it myself i gave it to an repairer (insured event). I got it back with a working touch but i noticed this colorproblem very soon. The repairer said it could possibly be the mod. So i flashed back to a 5.1 stock rom and the color problem was gone. But when i flashed the phone back to Cyanogenmod i've got the same problem again. Is this because of the "nightly" status or did something go wrong in the garage? The Problem is only visible on the screen. If i broadcast the screen to a pc or send a picture with "broken" colors e.g. via whatsapp it is free from these scratches.
I would have no Problem with flashing back to c11 but is it save? (stagefright) And is there meanwhile a fix for the slowly/sometimes not starting camera?
Any help would be appreciated!
best regards
Tilas
PS: Sorry I can't find the "manage attachments"-button and it seems like resizing in bbcode is not supported..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

yep,thats a busted screen alright and not a software problem.I guess you need to get it replaced...again.

If it is a broken screen then why is it working fine with a stock rom? The repairer already replaced it. But it didn't help. Maybe low quality screens? I already tried some changes in dpi with no luck. The original worked fine even with cm12.1 until i gave it away.

Your replacement screen may be a cheap knock off from china or somewhere .so it might work fine with the stock firmware but have problems with CM's screen drivers! .
PS: Did you do a full wipe and flash with a new rom or did you restore one of your old backups? Try to do a full wipe and flash the latest CM nightly.

From cm12.1 i used flashtool and xperifirm to find the newest stock rom for my device and flashed it. I made use of the wipe-options in flashtool. After that, with a working stock rom, i downloaded the newest cyanogenmod rom for my device to my pc and flashed the boot.img via cmd and fastboot and installed the new cm12.1 in the recovery (after wiping data and cache) via adb sideload. That broad up the colorproblem again.
Today i did the same but flashed the last cm11 snapshot. -> works fine.
Maybe i should try a cm12.1 nightly from a date before i took it to the repairer. I'm pretty sure that it worked until i gave it away and he had no option to apply a update himself due to the active lock. But i remember that some settings were changed the day i got it back e.g. the root-access was deactivated wich caused problems for some apps.

BetterBatteryStats - no stats have been collected yet

I am running BetterBatteryStats on Android version 4.4.2. Phone model is InFocus M512
I have been using Better BatteryStats successfully for a long time.
Starting from last update (I think) I get the message "no stats have been collected yet" on the main screen of the app, under Summary. This occurs irrespective of whether I select Boot or Unplugged.
I believe this is due to the new Sensors item. When I select Sensors instead of Summary I get the same message. However if I select any other item in the list, I get valid data.
Additional data: my phone is obviously rooted. BBS is installed as a system app.
I tried to find a way to have BBS ignore the sensors in the settings, but couldn't find a way to do that. I obviously tried to reinstall the app, to no avail.
Please advise.
Thanks,
Beni Falk

I have been getting this for kernel wakelocks - none log anymore

Since last update the problem has been resolved on my phone.

I've been getting this for kernel wakelocks as well. I'm on latest 2.2.2.0 donate version. Device details in sig. Ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sizzled with Bacon

I've been having this issue as well.
Pixel 2, Magisk, Snoke Kernel.
Worked for a while and now nothing.
Think it's android 8.1 related?

Diesel_Jeremiah said:
I've been having this issue as well.
Pixel 2, Magisk, Snoke Kernel.
Worked for a while and now nothing.
Think it's android 8.1 related?
Click to expand...
Click to collapse
Just started for me as well. Running OnePlus 5t Oreo Beta 1 with Magisk. Was working without a hitch and suddenly stopped. Tried AppSystemizer on Magisk for BBS, but no luck.

Diesel_Jeremiah said:
I've been having this issue as well.
Pixel 2, Magisk, Snoke Kernel.
Worked for a while and now nothing.
Think it's android 8.1 related?
Click to expand...
Click to collapse
Having the same issue as well. Pixel 2 XL, Magisk, Stock 8.1.

kaped31 said:
Having the same issue as well. Pixel 2 XL, Magisk, Stock 8.1.
Click to expand...
Click to collapse
Same here with Pixel 2 XL, Stock 8.1, unrooted but granted all the necessary permissions through ADB
edit: installed 2.3-214beta and all's good

redrivera said:
Same here with Pixel 2 XL, Stock 8.1, unrooted but granted all the necessary permissions through ADB
edit: installed 2.3-214beta and all's good
Click to expand...
Click to collapse
You're right. Works with 2.3-214beta

Where do I get the beta releases from?

This still happens to me,
No work around?

Kusie said:
Where do I get the beta releases from?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=1179809
Check post #2 right above the QR code

Thanks! It worked! :good:

hi I have this problem too version
Version 2.6-382 (99)​
unroot but grant permission from ADB. whjat should I do

Same problem here. Same version 2.6-382

Delete

From Mi 9T Pro Global to K20 Pro Indian ROM Issue.

Unlocked bootloader, downloaded indian rom used last mi flash tool.
got this error after finish flashing and device remail dead for a few minutes then accepted to boot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after setup rom i noticed that screen if went to sleep, it never wake up again, i had to force restart device every time to be able to work with screen normally.
downloaded last package over current from the three dots in top right of screen in system updater, install it then factory reset.
but still the same issue.
it was working without problems till i flashed indian rom..
any suggestions??

This is why I have not unlocked and installed a custom ROM on my device. And sorry, I don't know how to help you. May be revert to your original global ROM?

ntmalol said:
This is why I have not unlocked and installed a custom ROM on my device. And sorry, I don't know how to help you. May be revert to your original global ROM?
Click to expand...
Click to collapse
disabled anti flicker and it worked perfectly.

NaAZoOR said:
Unlocked bootloader, downloaded indian rom used last mi flash tool.
got this error after finish flashing and device remail dead for a few minutes then accepted to boot
after setup rom i noticed that screen if went to sleep, it never wake up again, i had to force restart device every time to be able to work with screen normally.
downloaded last package over current from the three dots in top right of screen in system updater, install it then factory reset.
but still the same issue.
it was working without problems till i flashed indian rom..
any suggestions??
Click to expand...
Click to collapse
I tried to flash on my unlocked k20 pro premium edition..... Indian global rom didn't even started on fastboot instead an error came with mismatch image...

Edit the flash_all.bat file search and rename raphaelin to raphael, repeat.
Save then you are good to go