Database Users

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

Oops-a-daisy (flashed wrong version of stock rom)

I wanted to root my Galaxy Note 4 (SM-N910F UK carrier H3G) so I could use the mirroring option in Airdroid.
Long story short, I'm severely disabled so wanted full access to my phone whilst on my pc, without struggling to get my phone all the time. (SWTOR Security Key is one of the many reasons for wanting to not have to grab my phone every time I need to do something on it)
(I can't put phone where it's easily accessible whilst on pc, because of the board I use for keyboard and mouse rested across the arms of my chair)
I THOUGHT I had it sussed, as I had successfully rooted and booted my S3, S4 and Note 2, 3 and 8.0 devices.
However, I didn't read the fine print when using CF-autoroot in that it doesn't work on 5.1.1 atm. Or something along those lines...
Anyway, with my usual eagerness and impatience to do geeky/nerdy deeds, I ended up with my phone in a constant boot loop no matter what I tried.
I scoured the Internet for 3 hours, trying to find the original stock rom for my device and was livid that my usual Google-Fu was failing miserably.
I found one, so I thought, installed the kernel, (couldn't find stock kernel either) installed SuperSU, installed Twprs or whatever it is, (excuse my lack of knowledge please) then installed this "stock" rom.
Turns out it possibly IS the H3G network's Stock Note 4 (SM-N910F) ROM. IF I lived in Italy.
I still would like root access on my phone, but I would like to try and get stock rom back, or something EXCEPTIONALLY similar.
Please, again, excuse my apparent thickness... (and I'm not talking sliced bread here) is it the kernel where rooting takes place, the ROM, or do both have to be involved in the adaptation?
I know very very little about Linux and kernels etc.
I hope that I have described my predicament clearly, and that when one has picked oneself up off the floor from rolling around with much merriment, one (anyone) is able to assist with my screw up.
Best wishes,
(Applebogies for waffling on more than the meat content of a Belgian Blue, (I'm not talking Blue Waffle, but of four legged animals that chew the cud)
(Applebogies also for mentioning The Waffle of Blue-ness in more than one sense of the word, if it makes you Google it and you only just ate and you've never seen it before)
(Finally, applebogies for my rotten and feeble attempts humour, please try to cut through my crap and get to the point ofwhat my conundrum actually is)

So basically in a nutshell, you've bricked your phone? I do know that when I flashed stock ROM the other day, I had to pull the battery, boot into recovery (vol up + home + power) and wipe data/factory reset and wipe cache too. Then it booted just fine try that.

you can find different stock roms for your phone at sammobile (google it) download the firmware from there and flash it with odin. Watch youtube videos on how to flash firmware with odin. its simple

See if you can boot the phone into Download Mode via volume up+home+power. If it boots into download mode that means its not hard bricked. If it doesnt boot into DL the first time you try, do a battery pull for 15-20 seconds, then try again. If that doesnt work, then check your specific device versions forum for an unbrick method, and check for a general unbrick that can be used for all N4's.
If it does boot into download mode, download the stock firmware for your specific N4, flash it via Odin, (instructions are generally included in the thread where you find the stock ROM download) and you should be good to go after that.
Edit: SamMobile does indeed have a firmware for your specific device. Do a google search for sammobile, go to that site, and input SM-N910F into the device search bar. That will take you to a page with a list of firmwares. Theres a list box where you can select your country, that includes country and carrier combinations. Yours will be listed as United Kingdom (H3G)(H3G). Select firmware with PDA version N910FXXU1COJ3.

Not sure why you all think my phone is bricked, I am on it now?
I am however, currently running the Italian version of 3 mobile rom. Looks like asrah has solved that problem though xD
To shorten my previous post:
Where does root happen, on kernel or rom?
Ie - can I have stock rom but still have root access on my phone?
Thank you to asrah for finding my rom.
Thanks all and a very Merry Christmas!

Zenfone 5 LTE (T00P) Erroneous Behaviour

Hey guys,
Long time user of XDA here, but first time poster in this forum. I would like to request help for my mother's Asus Zenfone 5 LTE (model number T00P), which has recently began to function in a way to makes it unsuitable as a daily driver. The phone is slightly over 2 years old, running stock 4.4.2, build number KOT49H.WW_Phone-11.4.6.94-20141218044000274_201406050026. I am unsure about the circumstances in which the following behaviour started.
Half the time when it boots, it immediately shows a lot of core apps FC-ing, like com.android.phone and com.android.systemui, along with another one buried, which is the KeyGuardTestActivity FC. Other times, it boots normally, but some apps do not work properly: the Phone app fails to launch as Contacts FC, Settings FC when trying to access the All tab under Applications, the file manager FC. With SIM card inserted, mobile connectivity is also a hit and miss. Holding the power button causes the phone to do a soft reboot, rather than bring up the power menu. I cannot gain ADB authorisation as SystemUI also FCs when trying to come up with the RSA authorisation message. Much of these issues render the phone pretty much unusable.
Up till this point, the phone has remained unrooted and untouched, XDA-wise, and can boot in recovery and CSC modes. However, there was a system update that was found in the stock updater, but could not be installed due to Status 7 (framework-res.apk has unexpected contents). After that failed update, there was no change to the phone, and the updater no longer works.
I have since rooted the phone with Kingroot, but freezing the keyguard produces more issues. I am at a loss at this juncture, as I am trying my best to save the phone short of a data wipe. I am very sure a data wipe would solve the issues, but many backup apps simply FC, as I would also like to backup data to shift to a new phone.
Are there any ways to help? Thanks in advance for any answers.

Never heard an XDA member let their devices remaining​ stock after 2 years. The best choice for you is flash another rom, Stable android 5.1 to 7.1
No need to root to unlock bootloader and flash TWRP. More details you can research around here.
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/

Redaki said:
Never heard an XDA member let their devices remaining​ stock after 2 years. The best choice for you is flash another rom, Stable android 5.1 to 7.1
No need to root to unlock bootloader and flash TWRP. More details you can research around here.
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/
Click to expand...
Click to collapse
I don't think there are custom rom available for zenfone 5 LTE model .So that gives no choice but to stay on stock rom.
---------- Post added at 07:12 AM ---------- Previous post was at 07:10 AM ----------
NightRaven49 said:
Hey guys,
Long time user of XDA here, but first time poster in this forum. I would like to request help for my mother's Asus Zenfone 5 LTE (model number T00P), which has recently began to function in a way to makes it unsuitable as a daily driver. The phone is slightly over 2 years old, running stock 4.4.2, build number KOT49H.WW_Phone-11.4.6.94-20141218044000274_201406050026. I am unsure about the circumstances in which the following behaviour started.
Half the time when it boots, it immediately shows a lot of core apps FC-ing, like com.android.phone and com.android.systemui, along with another one buried, which is the KeyGuardTestActivity FC. Other times, it boots normally, but some apps do not work properly: the Phone app fails to launch as Contacts FC, Settings FC when trying to access the All tab under Applications, the file manager FC. With SIM card inserted, mobile connectivity is also a hit and miss. Holding the power button causes the phone to do a soft reboot, rather than bring up the power menu. I cannot gain ADB authorisation as SystemUI also FCs when trying to come up with the RSA authorisation message. Much of these issues render the phone pretty much unusable.
Up till this point, the phone has remained unrooted and untouched, XDA-wise, and can boot in recovery and CSC modes. However, there was a system update that was found in the stock updater, but could not be installed due to Status 7 (framework-res.apk has unexpected contents). After that failed update, there was no change to the phone, and the updater no longer works.
I have since rooted the phone with Kingroot, but freezing the keyguard produces more issues. I am at a loss at this juncture, as I am trying my best to save the phone short of a data wipe. I am very sure a data wipe would solve the issues, but many backup apps simply FC, as I would also like to backup data to shift to a new phone.
Are there any ways to help? Thanks in advance for any answers.
Click to expand...
Click to collapse
Well i don't have LTE model ... But i would suggest you to upgrade to latest android version provided by Asus for your model and see if the problem persisit ....

Redaki said:
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/
Click to expand...
Click to collapse
Like I said in the OP, I cannot authenticate ADB as SystemUI crashes upon generating the notification for verification.
Boomshiva said:
Well i don't have LTE model ... But i would suggest you to upgrade to latest android version provided by Asus for your model and see if the problem persisit ....
Click to expand...
Click to collapse
Again, in the OP, I've mentioned the Updater does not work.
Are there any other solutions?

Redaki said:
Never heard an XDA member let their devices remaining​ stock after 2 years. The best choice for you is flash another rom, Stable android 5.1 to 7.1
No need to root to unlock bootloader and flash TWRP. More details you can research around here.
If you don't want loss data, use adb command to copy it to your lap or pc. Or here: http://www.droidviews.com/push-pull-files-android-using-adb-commands/
Click to expand...
Click to collapse
Yes, but there is no custom rom for zenfone 5 lte. maybe neither custom recovery or root.

Sorry i didn't read your post carefully. Did you try to unlock bootloader ? I think it will be the same as the Intel model. Try fastboot and then fastboot OEM unlock, or flash some ifwi file like Intel model.
Then if bootloader is unlocked, flash TWRP and u will have ADB.

Need help downgrading stock Oreo to MM or Nougat (with locked bootloader)

Edit: I worked out my issues, I'll leave this here in case others have similar trouble:
I needed to manually add in the RAW F53XX files from the github (https://github.com/Androxyde/devices/tree/master/F53XX), this allowed Flashtool to correctly detect the type of phone and apply the fsc. I was then able to flash my desired firmware, I chose the 6.0.1 release for Journalists to begin with as a test. This confirmed my suspicion that it was a software update issue causing the proximity sensor to malfunction (stuck on) and also fixed up the FACTORY STARTUP SERVICE-POWER OFF bug and the Warrantytimeservice permanent notification. I can now look at updating to later versions of Android and find the latest version before I have issues again.
---
tl;dr - I need a guide that actually works on downgrading the F5321 to a specific stock Android version with a locked bootloader.
I recently received a new, old stock version of the X Compact (F5321) that appears to be a HK variant as it started up with the Chinese language selected.
It was initially stock Android 6.0.1 with no apparent problems. After OTA updating all the way through to 7.1.x and onward to the latest 8.0, I now receive the "FACTORY STARTUP SERVICE" problem. Even if I'm quick enough to disable the service for the service flag, the proximity sensor does not work as well after updating, making phone calls impossible. I believe the issue is all related to software, not hardware. I want to downgrade to 6.x and go from there before I have to send it back for another replacement.
I'm having trouble with getting Flashtool to correctly detect and identify the firmware files that I want to flash. I want a completely stock version of Android, so keeping the bootloader locked is fine for me.
After downloading the firmware that I want to try, XperiFirm will close and Flashtool will successfully build the FTF. After clicking the lightning bolt > flashmode > the firmware list is blank.
I'm using Flashtool 0.9.26 (I have tried older versions as well with the same problems) with driver signature enforcement disabled and correct drivers installed to detect the phone.
The last time I used Flashtool was to flash my older Z5 Compact, I didn't have any issues then and it was all done within 10 minutes. I've already spent more than 5 hours on this phone and would appreciate any help.

I seem to have the exact same problem with a Hong Kong-sourced X Compact. I am familiar with Flashtool, and have used it for basic flashing of firmware. This time, however, I am experiencing the dreaded "FACTORY STARTUP SERVICE" problem. Was wondering if Flashtool could be used to circumvent the problem. I simply want the USA Android 8.0 firmware on the phone. I am not familiar with the various options that Flashtool offers. I note that you mention a specific script(?) that can be installed. Do you have any advice? Thanks

pseudonym58 said:
I seem to have the exact same problem with a Hong Kong-sourced X Compact. I am familiar with Flashtool, and have used it for basic flashing of firmware. This time, however, I am experiencing the dreaded "FACTORY STARTUP SERVICE" problem. Was wondering if Flashtool could be used to circumvent the problem. I simply want the USA Android 8.0 firmware on the phone. I am not familiar with the various options that Flashtool offers. I note that you mention a specific script(?) that can be installed. Do you have any advice? Thanks
Click to expand...
Click to collapse
The "FACTORY STARTUP SERVICE" and to a lesser extent, "Warrantytimeservice" problems surface only in the later version of Android. The only way I could remove them was by staying on 6.0.x only. Anything higher, and the problems show up again. It seems to be a byproduct of upgrading the HK variant that wasn't designed to actually be software upgraded - you won't be able to have the US 8.x firmware on the phone.
Sorry to say, but you'll be stuck on 6.0.x if you want a usable phone. I should mention that I was never able to maintain a newer firmware on that particular phone.
I've since sent the Compact X back (it was meant to be a gift) and replaced it with a Samsung A20.

h
I'm using SO-O2J and a sim card not docomo. Use the "Repair" in Xperia Companion and it auto flash Android 7.0

..

PioneerSeeker said:
Try different region's roms on www.xperiablog.net and I hope you'll be successful to find nougat or oreo at last for your phone.
Remember xperia devices do not need to unlock bootloader for downgrade...
Click to expand...
Click to collapse
Thanks; I was able to obtain an X Compact originally for the UK market, and was able to successfully flash the US Oreo firmware. All seems to be in order.

some basic questions on sm-t235 re: root/custom rom/custom recovery

Hi,
the other day a friend gave me her old Samsung tab 4 7.0 (SM-T235). It's in its default state, running Android 5.1.1 stock ROM with all the most recent (5 year old) updates. "KNOX" appears to be ok, afaik.
This is my first Samsung device, up to the date I had experience with HTC Desire, Sony Xperia (2x) and OnePlus devices. I unlocked / rooted and installed custom ROMs on all of them.
Done quite a bit of googling and playing around with my "new" Samsung to see where it's different compared to my other devices. But there still are some blank spots, and there doesn't seem to be too much information out there regarding that specific tab 4 device. Before I start messing around I'd love to have some input from experienced Samsung users in regards to custom recoveries and ROMs, and possibly rooting. If there are comprehensive guides etc. out there that I simply didn't find don't hesitate to give me some hints:
First of all it appears to me that this device is going under the codename "degas". Correct? (meanwhile confirmed)
I hooked up the device to my PC, made sure that adb found it alright, then called "adb reboot recovery". That worked nicely, got me into Samsung recovery
Next I again tried to connect through ADB to the device still being in recovery, but that didn't work. To be expected?
Still in recovery I chose the "boot to bootloader" option, but that got me back into system instead.
So from system I again connected to adb then called "adb reboot bootloader". Device booted alright, but again it just rebooted into system.
>> Is there really no way to get into bootloader?
Trying to find out what has to be done in order to flash a custom ROM (rooted or not): from what I get, and unlike my other devices, I do not have to unlock the device / bootloader to begin with. It looks as if it was sufficient to boot into what they call "download mode", then hook up the device to my PC where ODIN is waiting already. Following this thread (and others) it then is sufficient to just flash TWRP from ODIN, boot to recovery and then do what is usually done here (like flash custom ROM, flash Gapps and possibly Magisk etc.). Is there something else / important I should know / observe?
Speaking about TWRP and Custom ROMs: TWRP.me lists that device on their site. So has anyone here flashed latest TWRP (3.6.2_x)? Or should I rather start with an older version like the one listed here, then possibly upgrade from there?
In regards to Custom ROMs I basically just found this LOS 16 thread (which is the same linked in the previous "TWRP" bullet). I assume that's it, or does anyone know about a newer android version (which I didn't find so far)? There seems to be lots of activity around "matisse" and "millet", but apparently those aren't the right devices, right?
Back to recovery: I see that in stock recovery there is an option to "wipe data/factory reset": should I do that before flashing TWRP from ODIN, or is it sufficient to wipe everything once I booted into TWRP?
I'm aware that I'll lose "Knox" as soon as I flash a different ROM / Recovery. As I don't want to use the tab 4 in some critical "BYOD" area I don't care (neither do I care about warranty, that's long gone anyways). But just to be sure: is it true that I'll lose "Knox" access?
In case I would decide to "go back" to stock ROM one day, how would I proceed then? Would ODIN still work so that I can flash latest stock ROM? Would Knox then be restored, or is that a thing of the past once I leave the stock ROM path?
Again: if you think I've done a bad job searching for answers don't hesitate to let me know but please be so kind then to hint the phrases I should look for ("SM-T235" really doesn't bring up that much valuable info)
Thanks and cheers
Update 2022-08-03: meanwhile I realized that the device is connected to my PC through generic drivers. Would it help to install specific Samsung drivers although both ADB and ODIN are acknowledging the device? Or can I just neglect that?

Since no answers came in I dared to just try. Meanwhile I'm running the device on LOS 16 with TWRP 3.5.2_9. Then flashed MindTheGapps (arm/Android 9 flavour)The switch wasn't as easy as I expected for some reason not obvious to me (somehow I couldn't get into TWRP after flashing it through ODIN. Then after the ~25th attempt it suddenly worked). Meanwhile I installed the official Samsung drivers, and maybe that helped, in combination with other adjustments I lost trace of...
I'll answer some of the above questions, for anyone who's interested:
#3: while in recovery (TWRP 3.5.2, as it is now) I still cannot access the device through adb. But I have access from windows' file explorer, so at least I can exchange files while being in recovery. Strange thing, this is the only one of my devices that behaves this way. The other day I'll try again from a Linux machine. maybe that works...
#4/5/6: boot to bootloader still doesn't work no matter what I try - devices always boots back into system
#7: Once I managed to get into TWRP the rest was a breeze
#8: I tried TWRP 3.6.0_9-0 which worked but on every boot into recovery it shows first a red notice that recovery was not enforcing SEAndroid. The notice then turns into blue and a second later TWRP logo shows up. This dowsn't happen with TWRP 3.5.2_9, so I stay there for the time being. Then I felt lucky and installed TWRP 3.6.2_9 image from running TWRP recovery, then rebooted. That again showed the red "not enforcing" message - and got stuck there. Solution was to get back into "Download mode" then re-flash TWRP 3.5.2 through ODIN.
Conclusion TWRP 3.6.2 is not fit to be used on that device (no, I didn't try 3.6.1...)
#9: since there aren't any more security updates released by google for A9 ROMs it would really be great to be able to upgrade to an A10 or even A11 ROM... anyone ever tried to use a "matisse" or "millet" ROM?
#10: I decided to use that - wiping everything that was on the device then doing a factory reset as well before flashing LOS 16. Then after first boot into LOS 16 a strange thing happened: when I made a basic setting (in regards to location services" the device told me that in a previous version I had decided to NOT allow google to use those services: after all that wiping and factory resetting: how could the device know that? By that time I had not yet logged myself into Google. Very mysterious!
#11/12: I guess I know the answer: I'm out of "Knox" now once and forever. And apparently ODIN is still working and recognizing the device.
Cheers!