Database Users

After Update No-wifi!?

Hello, today I got my Amazon Kindle Fire! After starting an connecting to my Wifi network, I made an update, wich was available! But after installing the update I can´t find any Wifi-network! Also tried the factory reset, but didn´t work!
Can anybody help me? Is it possible to downgrade or something else??
Thx Chris

masterc1111 said:
Hello, today I got my Amazon Kindle Fire! After starting an connecting to my Wifi network, I made an update, wich was available! But after installing the update I can´t find any Wifi-network! Also tried the factory reset, but didn´t work!
Can anybody help me? Is it possible to downgrade or something else??
Thx Chris
Click to expand...
Click to collapse
Try contacting tech support they might have something for you to flash. And if they do, you should post the files and process here. Unfortunately without solid kernel, or recovery information there's little we can do.
Sent from my SPH-D710 using xda premium

Hopefully, cause I don´t want send it back

After chatting with Amazon, the problem wasn´t solved! But I looked a bit more on the Amazon Homepage and found where I can download the Software Update to 6.1:
Download Link
And here is the instruction:
http://www.amazon.com/gp/help/customer/display.html/ref=hp_k6_updatesi?nodeId=200790620
I will try it now and report what happends!

I think you already have that don't you?
When I got my KF, it immediately before I did anything updated to that version.
Code:
Current Version 6.1_user_2017120

Yes I have the one but I´ll try to run the update again manuelly, or do you think t wont work?

Masterc, didn't you say in another thread that you are in Austria?
You should mention that here if it is the case as it might affect the responses you get.

Yes thats true, but Wifi worked before I downloaded and installed the update! It also showed my name... the Amazon support told me it should work abroad..
I tried to install the update again, but it didn´t solve the problem.

So after playing around a while, the network pops up (yeahh) but when I enter the (right) passwort it always shows:
Error in conncection
unable to connect to selected access point. Please check the password you have provided
the kindle found my hotspot from my galaxy note (without password) and it connected just one time for arround 10 seconds..
Now I can´t connect again... quite intressting
Hopefully it is not the hardware - but I don´t think so otherwise I couldn´t download the update.

Jiayu S3 PIN Locked by Kinguser app

First of all, I may be posting this in the wrong section. But I desperately need your help on this.
I got a Jiayu S3, and couldn't not try to flash a custom rom on it, so I tried with "Pure AOSP V1 TF".
All went well, untill i found this app which was included with the rom, "Kinguser" (should be Superuser, i believe), which game me the option to toggle root.
At first and only time I opened this Kinguser app, option root was active. I did deactivate it, and reactivated immediately after.
As soon as i reactivated root, the privacy pin screen showed up.
I didn't set any PIN on my phone, so at first i thought it could be something like 1111 or 0000. Tried 5 times and it made me wait 30 seconds. Then tried another 3-4 times.
Here began the real mess: "forgot pin" (or psw) didn't show up, but at the time i didn't even know about that recovery option.
I didn't know what to do, so I just thought that a factory reset would certainly solve the problem, how couldn't it? Well, wiped everything, but PIN lock screen didn't go away.
So, wiping everything, I also deleted my gmail account from the phone, and I lost the possibility to lock phone and give it a new password (Android Device Manager). Too bad at the time I didn't know about this recovery option as well...
Now I'm out of ideas. I think I've tried every method I could find with a search of "Smartphone PIN locked". Tried with resets, plugins, deleting files with adb..
How do I unlock my phone?
little update: after a factory reset, for 2-3 seconds, it shows the default initial screen, but it doesn't last more that and i just can't do anything.
Now i managed to bring back the stock rom, but with that i lost the twrp recovery, and i can't find a way to make pc recognize the phone to reflash it.
It seems it's going worse instead of better...

I had just bought this Jiayu S3 and planned to bring it on holidays on wednesday, but i'm starting to think i won't be able to fix it before then

Did you have any resolution to this problem. I am currently sitting in the exact same boat. Did the factory reset, pass code screen still there, I didn't set a pass code. Basically hands tied, can't update firmware, guessing i'll have to get a new phone, but hoping maybe you found a miracle cure! ha! - Thanks for any guidance. - Arden (Seattle, WA)

Just flash another rom (stock/original) and start over.

How have you done that?
Can you help please?
I tried factory reset (volume plus+ power button), hard reset (volume- plus power button), update, and nothing works; I also went to two different specialized stores and they failed to find a way to reinstall the original Android version or a recent one.
Comparing the files with the factory version installed in the phone, the phone report identified three changes:
- a new file: /system/priv-app/7mK0T6e8Z5.apk
- the lost of a file: /system/app/com.android.fallen.apk
- and a modified file: /system/bin/debuggerd

AzulFogo said:
How have you done that?
Can you help please?
Click to expand...
Click to collapse
To flash firmware you can use SP Flash Tool on a windows or linux computer (not sure about macosx). You have to decide which firmware you want (which one do you have now?). The 'official' firmwares can be found on needrom. SP Flash Tool can be found there as well. There are 2 popular LP firmwares built by Jiayu resellers in Europe (Xtreme from Spain and Jiayu.de from Germany). Guides on how to flash are often present at the place where you find the firmware.

Dior DNA said:
To flash firmware you can use SP Flash Tool on a windows or linux computer (not sure about macosx). You have to decide which firmware you want (which one do you have now?). The 'official' firmwares can be found on needrom. SP Flash Tool can be found there as well. There are 2 popular LP firmwares built by Jiayu resellers in Europe (Xtreme from Spain and Jiayu.de from Germany). Guides on how to flash are often present at the place where you find the firmware.
Click to expand...
Click to collapse
Thank you!
I found "Xtreme from Spain":
needrom.com/download/rom-xtreme-rom-tf/
I found the "SP Flash Tool":
needrom.com/download/sp-flash-tool-v5-1424-00/
but it is for Linux... can you send me the link of the windows version?
And I could not found the "Jiayu.de from Germany": can you send the link?
Also, can you recommend some good manual for dummies?
Thanks again for your patient and help!

latest sp flash tools is 5.1532
search needrom with "5.1532" will leed you to the download page
no link allowed here, so ...
for beta 10 from jiyau.de, search google with "jiyau.de Lollipop 5.1.1 - Beta 10 (14.10.2015)".
it will leeds you to the rom.
Good hunting
tuto sp flash tool
https://youtu.be/ztI8sc8MUNo

AzulFogo said:
Thank you!
I found "Xtreme from Spain":
needrom.com/download/rom-xtreme-rom-tf/
I found the "SP Flash Tool":
needrom.com/download/sp-flash-tool-v5-1424-00/
but it is for Linux... can you send me the link of the windows version?
And I could not found the "Jiayu.de from Germany": can you send the link?
Also, can you recommend some good manual for dummies?
Thanks again for your patient and help!
Click to expand...
Click to collapse
see jaunedoeuf's answers
I would like to add: if you come from KK and go to LP, you must use firmware upgrade to update/adjust internal SD partition layout. Good Luck! if you succeed, and are happy with firmware, consider voting @ http://forum.xda-developers.com/android/general/firmware-jiayu-s3-t3212184 (almost 100 votes)

First, thank you for your great help!
With your suggestions, I managed to install Lolipop in my Jiayu S3S (upgraded from Kit Kat) - Xtreme ROM TF (JiayuS3-5.1Extreme1.1SP.zip).
However the problem remain... the phone still is asking for a PIN (that I never had put there, in first place)...
What should I do now?

you could try factory reset and are you sure its the phone asking for pin and not the sim card

Collection of potential camera fixes for Nougat (Black screen, crashes) - Suggestions

Hi all,
I finally managed to get a Nougat ROM running on my device - except for the camera. It keeps showing a black screen (closes and pops up in intervals of about 1s). I of course searched the forum but it looked like noone has really managed to find a reliable solution. First some background for my device: VNS-L31 (Dual Sim) which was running on fully stock/fully working C432B160 firmware (no root, locked bootloader, after factory reset) and then upgraded to Nougat C432B370 using FirmwareFinder (FullOTA-MF-PV). Installation worked fine, everything running as expected except for the camera - as said. I exactly followed the steps outlined in this thread here: https://forum.xda-developers.com/hu...android-7-emui-5-0-vns-l-cb360-links-t3565117
Factory resetting after upgrading doesn't solve the issue. After upgrading to B370, I also updated to C432B388 - but to no avail. What I find a little strange is this: Connecting the device to the computer and investigating the device info correctly shows build/device/manufacturer etc. However, in build.prop it shows information about the NRD90M test-keys release with generic_a15 device. Could this hint at some issue? Also, checking the device info with
Code:
*#*#2846579#*#*
shows this: Manufacture information: NEMO_L21E_VB. I actually expected something with "L31" there - but well, I also don't really know what this specific thing stands for.
Now, here are certain things I came across when looking for solutions:
Suggestion by @Meticulus: https://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I tried the suggestion by Meticulus, but unfortunately it didn't work. Does there exist a modification for newer builds that might work? (I just don't understand why that should help - to me it looks moreorless like restarting the camera).
Some fix in build.prop mentioned by @danielegta : https://forum.xda-developers.com/showpost.php?p=72280947&postcount=7
I have absolutely no idea what the build.prop modification is supposed to be. Can anyone elaborate?
A TWRP related fix: http://www.htcmania.com/showpost.php?p=25093316&postcount=31
A bit afraid to try the TWRP fix by BadWolf. It seems to be for B328 builds... So I am a bit unsure whether I should try it on newer build. According to members in the German android-hilfe.de forum, it once solved these issues, but as said for older builds.
Edit: I tried the fix on B370 but it has no effect.
Use the fix in #3, but reflash system.img if the fix doesn't help: https://forum.xda-developers.com/showpost.php?p=70069246&postcount=26
Unfortunately this also didn't work for me
Use TWRP-flashable .zip files as given in this thread here: https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932
I tried this today, but unfortunately it ends up in the same state as I was when upgrading B160 -> B370 using Firmware Finder. Everything except for the camera works.
Edit: I notice that in TWRP there are always errors about not being able to mount /data and /cust. Is this normal or does it hint at some error/malfunction when updating via flashable zip?
Use TWRP-flashable .zip as in #5 but instead of flashing the two .zip without restarting the device, first flash update.zip, then restart phone, flash Nougat TWRP, flash update_data_full_VNS_Lxx_xx_xx.zip as described in this post: https://forum.xda-developers.com/showpost.php?p=70704697&postcount=7
Tried this in the following way: stock MM -> unlock bootloader and flash TWRP -> flash update.zip -> flash Nougat TWRP -> flash update_data_. Doesn't help. Also I cannot confirm what I read somewhere here on xda (some user mentioned that his camera was working when he only flashed the update.zip - this is not true for me).
Other things I tried for uprading the OS that are not necessarily meant to fix the camera issue, but might:
Use B336 as intermediate step: B160 => B336 => B370 (=> B388) as suggested by @vozilo here: https://forum.xda-developers.com/huawei-p9lite/how-to/how-to-b388-nougat-maybe-b381-guide-t3612072
Unfortunately this does not solve the issue. The camera doesn't work in any of the versions flashed after B160.
Go from B160 direcly to B388: didn't help
Does anyone know of something else that might help or could someone maybe comment on the "known" fixes, especially if there might be some changes that could be done to commands/build.prop or even local.prop that eventually help?
Thank you very much,
theluk

_theluk_ said:
Hi all,
I finally managed to get a Nougat ROM running on my device - except for the camera. It keeps showing a black screen (closes and pops up in intervals of about 1s). I of course searched the forum but it looked like noone has really managed to find a solution. First some background for my device: VNS-L31 (Dual Sim) which was running on fully stock/fully working C432B160 firmware and then upgraded to Nougat C432B370 using FirmwareFinder. Installation worked fine, everything running as expected except for the camera as said. I exactly followed the steps outlined in this thread here: https://forum.xda-developers.com/hu...android-7-emui-5-0-vns-l-cb360-links-t3565117
Factory resetting doesn't solve the issue. Afterwards, I also updated to C432B388 to no avail. What I find a little strange is this: Connecting the device to the computer and investigating the device info correctly shows build/device/manufacturer etc. However, in build.prop it shows information about the NRD90M test-keys release with generic_a15 device. Also, checking the device info with shows this: Manufacture information: NEMO_L21E_VB. I actually expected something with "L31" there - but well, I also don't really know what this specific thing stands for.
Now, here are certain things I came across when looking for solutions:
Suggestion by Meticulus: https://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I tried the suggestion by Meticulus, but unfortunately it didn't work. Does there exist a modification for newer builds that might work? (I just don't understand why that should help - to me it looks moreorless like restarting the camera).
Some fix in build.prop: https://forum.xda-developers.com/showpost.php?p=72280947&postcount=7
I have absolutely no idea what the build.prop modification is supposed to be. Can anyone elaborate?
A TWRP related fix: http://www.htcmania.com/showpost.php?p=25093316&postcount=31
A bit afraid to try the TWRP fix by BadWolf. It seems to be for B328 builds... So I am a bit unsure whether I should try it on newer build. According to members in the German android-hilfe.de forum, it once solved these issues, but as said for older builds.
Does anyone know of something that might help or could someone maybe comment on the "known" fixes?
Thank you very much,
theluk
Click to expand...
Click to collapse
I had the same problem, and i fixed it by (un)rooting and (un)rooting again

Could you please elaborate a little bit more on what you exactly did? Because for me I was fully stock (including locked bootloader) when upgrading from B160 to B370. Right after the upgrade finished I did a factory reset and the problem already appeared. Are you suggesting to root, unroot and root again? I mean I can try, but I don't see why this could help, so please let me know if I got your point correctly

_theluk_ said:
Could you please elaborate a little bit more on what you exactly did? Because for me I was fully stock (including locked bootloader) when upgrading from B160 to B370. Right after the upgrade finished I did a factory reset and the problem already appeared. Are you suggesting to root, unroot and root again? I mean I can try, but I don't see why this could help, so please let me know if I got your point correctly
Click to expand...
Click to collapse
Ok so usually u should upgrade like 160>b336>b370... The problem might be that you missed a step, not sure though. Try to factory reset first, then go back to b160 and to b336 and then to b370

Unfortunately your suggestion didn't work for me. But it also looks like FF didn't "send" all of the update package to the updater. I chose the 1.6GB FullOTA-MF-PV for B336 but in the system updater it only downloaded 1.2GB. I suspect the data update wasn't downloaded which surely caused issues. Will have to try that again, I guess

_theluk_ said:
Unfortunately your suggestion didn't work for me. But it also looks like FF didn't "send" all of the update package to the updater. I chose the 1.6GB FullOTA-MF-PV for B336 but in the system updater it only downloaded 1.2GB. I suspect the data update wasn't downloaded which surely caused issues. Will have to try that again, I guess
Click to expand...
Click to collapse
try updating through the stock updater

mjz2cool said:
try updating through the stock updater
Click to expand...
Click to collapse
Unfortunately the stock updater doesn't show any updates. So I have to enforce this by using the proxy method provided in Firmware Finder. As I understood this is the "fully" official way of updating, since it does use the "system update" feature provided inside settings of the phone. I will try it again later today to see what could've gone wrong. Maybe I'll just try one of the other B336 firmwares that are listed as FullOTA in FF.

Major update to OP - including new stuff and new information about what I tried. Any other suggestions? I am out of ideas for now and will probably have to live with MM until Huawei has solved this issue

After a suggestion to try VNS-L21 firmware I did, after flashing the corresponding oeminfo. And indeed this worked nicely. Upgrading to Nougat B370 worked and camera is working as well.

_theluk_ said:
after flashing the corresponding oeminfo
Click to expand...
Click to collapse
Hello,
Sorry but I'm a noob, can you explain to me what do you mean by "flashing the corresponding oeminfo" ? Does it mean you had to somehow "trick" your phone so it believes it's L21 instead of L31 or something ?
I have the same problem on the phone of my girlfriend (although I don't recall it's a dual sim one), I'd really like to solve this.
Thank you

_theluk_ said:
...
Suggestion by @Meticulus: https://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I tried the suggestion by Meticulus, but unfortunately it didn't work. Does there exist a modification for newer builds that might work? (I just don't understand why that should help - to me it looks moreorless like restarting the camera).
...
Click to expand...
Click to collapse
Ah, one of number of my statements taken out of context. When I worked on CM13, initially only the P9 Lite was supported. After a NEMO user tested this, which was proof of concept that the nemo camera could work on my p9 lite ROM, I added support for NEMO in my AOSP ROMs. So, the reason this helped was that it restarted the camera to work with NEMO and not VENUS, for which it was originally started.
As for your problem, Developer Options -> Take Bug Report ->FULL and post?

Disabling FRP with 8.0 image

Hello everyone,
Im in a bit of a pickle and hope someone here can help?
bought a g930p off second hand site, but when got home to fire it up there was the google reset protection on it (FRP), thought no hassle ill just wipe the phone and why not updated it to the latest while at it, so grabbed the latest files (8.0) and flashed the lot with odin, silly me thought this would just clear the phone totally including the FRP, anyway back to stage one of a phone that i cant use,
what ive tried:
z3x tool (asks to start adb, have adb started from platform tools dose nothing)
tried downgrading to 6 to try the OTG cable trick, wont let me downgrade
ive tried a few methods on here as well, but none seem to work anymore, so dose anyone know how to get past this with 8.0 installed ?
Thank you

Also i see there is a twrp for the Exynos version, is there version for the Qualcomm (g930p) version and would that help removing the FRP ?

Guess i should follow up on this, I ended up taking it to a phone repair shop, i asked how he did it and he didn't want to tell me.
So i guess this post is for anyone searching for a solution, wont find it in this thread sorry.

speaker_ said:
Guess i should follow up on this, I ended up taking it to a phone repair shop, i asked how he did it and he didn't want to tell me.
So i guess this post is for anyone searching for a solution, wont find it in this thread sorry.
Click to expand...
Click to collapse
Well what they do is flash a modified SBOOT or Aboot file with adb enabled (because when you're on the setup assistant thats not enabled; you have to go to Developer Settings and blablabla and offcourse that's impossible at this time) then use Z3x to disable frp.... other method used is flashing combination firmwares (these are special FW that are used by the Samsung Engineers that comes with ADB and other usefull things for debugging, but make the phone unusable for everything else) and then the same thing using Z3x or Octopus Box; but I really don't know if theres a Combination FW for Bootloader 8.

Can't actually fix the OS of my Moto G6

Hi.
First of all, I want to let you know I'm just new to this page, so I'm so sorry if I make any mistakes within creating the post.
As you've read in the title, I can't fix the OS of this phone. I bought it used, and apparently it didn't have any OS (I thought it was because there was a flashing attempt, which went wrong). One day, I just looked for Android 9 and I installed it. The phone started working, and so I started using it. There were some problems with the phone though. First of all, at random moments, it started lagging and just re-starting. The other problem I had was the bootloader message, saying that I didn't have an official OS.
Today, I tried to uninstall all of /system. I read a lot of information, I watched a lot of videos and I started doing so. Basically, what I wanted to do is delete all in /system so I could install a clean ROM from my computer. Problem is, I have "flashing_locked" flag. I also downgraded it to Android 8, and I think it made it worse. Now, I don't even have internet connection (or what is called /persist), which also means I'm stuck in the setup screen. There's no way I have now to enter developer mode, nor activating usb debugging. Just wondering, is there any tips I could get from you guys to fix all this problem?
Thanks a lot.
Edit: I also think there's some "residual" data from those flashing attempts, Android 8 and also Android 9. I'm not sure if that has something to do.
Edit 2: I also requested a Unique Key from the Motorola official page, which didn't lead me to anywhere. Although I used "fastboot oem unlock <key>", it didn't work to me.

s9kii_ said:
Problem is, I have "flashing_locked" flag.
Click to expand...
Click to collapse
I'm wondering how you managed to downgrade the device from Android 9 to 8 with a locked bootloader?? that's very strange... To fix the known issue of broken wifi/mobile connection (as a result of the downgrade) it's recommended to revert back to Android 9.
So, you did the downgrade from 9 to 8. But now you can't finish the setup wizard to activate OEM unlocking? Please tell me, at which point it has been deactivated?? It doesn't make any sense...
Try the Lenovo Motorola Smart Assistant tool. It'll fix the issue.
s9kii_ said:
I also think there's some "residual" data
Click to expand...
Click to collapse
I think not. Flashing a firmware means copying image files to a specific partition. Each image file got its own partition table. There will be no data left.