Database Users

[Q] Note 3 stuck in some weird "Factory Mode" No lock screen

Hi Guys!
Sorry, I couldnt find any problem similar to mine regarding note 3.
Device: N900W8 Canadian (Rogers)
TLDR: After flashing a rom a second time (First time was perfect) phone says its in factory mode and now stock lockscreen doesnt work at all no matter what settings. In factory mode wifi is one of the settings it says isnt suppose to work but it does work, and Im extra confused.
Steps leading to the problem:
- Rooted using cf auto root
- twrp to backup entire stock rooted rom
- flashed Darthstalker v6
- phone works flawlessly, except with gps issues which I suspected was not a rom issue
- decided to test it out anyways, tried to restore my stock rooted backup but for some reason failed (Honestly have no idea why)
- flashed Darthstalker v6 again, complete clean install to see if GPS fixes itself
Phone now boots up normally, but on first boot up it showed a short popup that disappears shortly saying something like this
"Factory mode is ON, in this mode some settings such as wifi may not work blah blah blah"
Thing is, it does work, so far the only difference that I see from this mode is that I cant have a lock screen no matter what setting I put on it. Right now forced to use an alternative lockscreen (Go locker).
Just flashed Jedi Elite v5 yesterday, same issue as above, but everything else is working fine...
Thanks for the help guys!

I suspect it is and EFS thing, but I dont know what that is.
I used root explorer to look in the folder and nothing seems to be inside (Even when selecting to view hidden files and folders)
Unfortunately since my original stock root backup did not work I have no way of restoring the original. If you think this is the issue can someone point me in the right direction to get my EFS folder proper? Currently I only see Backup/restore options. Not the full EFS folder that I think I might need.

Two more things I noticed
- 4 way reboot doesnt work, it just turns off the phone
- when playing youtube "An error occurred" appears for maybe 10 seconds and disappears. Video is playing in the background so its pretty annoying.

Download this file by firasusman and flash thru recovery. Don't know if the lockscreen will come back but if it doesn't reinstall whichever rom you have right now to fix the broken file.

Black screen after factory reset

so... my phone suddenly wouldn't accept my password anymore to unlock. i tried a couple of things, like deleting the files lockscreen files using TWRP to bypass that... but then it got stuck in a "android is booting" screen and everytime i tried to change my PIN, it would crash.
So i went to TWRP and wanted to reflash my ROM (I was using Resurrection Remix), but then I couldn't decrypt the data because ... the password again wouldn't work. so I finally decided to use sideload to try to flash everything again and it works, but the problem is that even after the factory reset, the phone will boot up but there won't be any images. You can hear the jingle play when you first turn on any android phone... but it's all black.
edit: I've tried flashing two different roms: RR & Lineage OS, both will boot up, but same problem.
I haven't been able to back anything up because... well the OS wouldn't boot up and my TWRP was being wonky and I can't restore anything...
Anyone have any ideas of how to fix this? I feel like i could use the format data and start from scratch... and make it work but then I assume that would wipe my titanium backups, which I haven't been able to extract out. so if anyone has any guidance on how to do that, that would be great. I've tried to use adb to extract stuff out but it hasn't worked and now I can't even do it anymore because I don't have usb debugging on.

nova_vo1 said:
so... my phone suddenly wouldn't accept my password anymore to unlock. i tried a couple of things, like deleting the files lockscreen files using TWRP to bypass that... but then it got stuck in a "android is booting" screen and everytime i tried to change my PIN, it would crash.
So i went to TWRP and wanted to reflash my ROM (I was using Resurrection Remix), but then I couldn't decrypt the data because ... the password again wouldn't work. so I finally decided to use sideload to try to flash everything again and it works, but the problem is that even after the factory reset, the phone will boot up but there won't be any images. You can hear the jingle play when you first turn on any android phone... but it's all black.
edit: I've tried flashing two different roms: RR & Lineage OS, both will boot up, but same problem.
I haven't been able to back anything up because... well the OS wouldn't boot up and my TWRP was being wonky and I can't restore anything...
Anyone have any ideas of how to fix this? I feel like i could use the format data and start from scratch... and make it work but then I assume that would wipe my titanium backups, which I haven't been able to extract out. so if anyone has any guidance on how to do that, that would be great. I've tried to use adb to extract stuff out but it hasn't worked and now I can't even do it anymore because I don't have usb debugging on.
Click to expand...
Click to collapse
have you try to re-flash your TWRP? maybe re-flasing your TWRP will work, also maybe installing the original rom will work, and then you can try to flash whatever rom you desire
as i know doing a factory reset from the TWRP delete all of your files, i mean everything. so i don't think that you still have the backup files

Flash the Official recovery of the oneplus 5 and then install OOS by adb into thé recovery.

PIN changed, can't get in now

I got a notification for system update. When I rebooted, my tablet started up in TWRP. The update finished (I don't Know if it was successful or not). After I rebooted into system, my usual PIN is not working, do I can't get access. I'm away from home and away from my PC for a couple of weeks, so I'm limited in what I can do.
Does anybody know how to get a PIN to work? Looks like TWRP has been replaced with regular recovery on partition 1, but I have TWRP on partition 2 also. Is there a way to get into TWRP on partition 2 without a desktop PC?

I have the same problem, after the system update yesterday my old pin does not work anymore. What could I do?

So, before you updated, was your tablet rooted? Did the update use TWRP or the stock recovery? Did you have a pin set before the update?

before the update I use PIN and fingerprint reader, device was not rooted.
The update was offered by the device and ran normally.
Now my PIN does not work anymore. I do not have an "ok" button
when entering the PIN and I do not remember if there was one before?

My pin was reset after I updated, but I thought it was because I had replaced the stock recovery with TWRP. I've heard that there's a bug in TWRP that can mess up your pin. Now it looks like the pin problem is happening with stock updates, too. I'm surprised that other people haven't reported it.
If you had TWRP installed and you were able to boot into it, there's a way that you can use the TWRP file manager to delete the pin lock files. In your case, you will probably have to do what I ended up doing. I copied into Huawei eRecover and reset the tablet. That means it was wiped and I had to restore my apps and settings. You could try to get in touch with Huawei support first and see if they have a solution, since it appears that a stock update caused the problem. Please post back again if you find a solution.

Stuck at boot screen animation... was working fine!

I'm not sure what happened with my US Axon 7. I was getting it ready to give to my son, and now it won't boot. Even with a full wipe (including system) and reinstall of the OS. It tries to boot, but just sits at the Google animation forever.
Here is basically the steps of what happened during the wipe/install of the unofficial RR Oreo build:
- Wiped everything
- Flashed the B32+B10 bootstack (A2017X_BootStack_B32+B10.zip)
- Flashed the latest (at the time) unofficial RR Oreo build (RR-O-v6.0.0-20180511-axon7-Unofficial.zip)
- Flashed opengapps micro (open_gapps-arm64-8.1-micro-20180512.zip)
- Flashed Magisk 16.0 (Magisk-v16.0.zip)
- Booted up and setup the phone for his google account
- Rebooted multiple times during setup
- Installed TiBu and froze the apps I normally freeze for the kids.... things they don't need
- Rebooted one final time and got stuck on the boot screen
- Re-performed steps above (minus setup... because I still can't get it to boot)
The best I can figure is that I froze something I shouldn't have... but a wipe and reinstall should have fixed that. I don't understand why it wouldn't. I've even wiped system.
I'm going to see if I saved a backup somewhere, as it's not on the phone. I can still get into recovery and such, which is good.

Flapjack said:
I'm not sure what happened with my US Axon 7. I was getting it ready to give to my son, and now it won't boot. Even with a full wipe (including system) and reinstall of the OS. It tries to boot, but just sits at the Google animation forever.
Here is basically the steps of what happened during the wipe/install of the unofficial RR Oreo build:
- Wiped everything
- Flashed the B32+B10 bootstack (A2017X_BootStack_B32+B10.zip)
- Flashed the latest (at the time) unofficial RR Oreo build (RR-O-v6.0.0-20180511-axon7-Unofficial.zip)
- Flashed opengapps micro (open_gapps-arm64-8.1-micro-20180512.zip)
- Flashed Magisk 16.0 (Magisk-v16.0.zip)
- Booted up and setup the phone for his google account
- Rebooted multiple times during setup
- Installed TiBu and froze the apps I normally freeze for the kids.... things they don't need
- Rebooted one final time and got stuck on the boot screen
- Re-performed steps above (minus setup... because I still can't get it to boot)
The best I can figure is that I froze something I shouldn't have... but a wipe and reinstall should have fixed that. I don't understand why it wouldn't. I've even wiped system.
I'm going to see if I saved a backup somewhere, as it's not on the phone. I can still get into recovery and such, which is good.
Click to expand...
Click to collapse
Which apps do you freeze? If you froze some Google apps you can just use the pico package and avoid having to use TiBU entirely
You're saying that after doing the whole installation you set up the ROM, but after you freeze apps with titanium and reboot the phone refuses to boot?

Choose an username... said:
Which apps do you freeze? If you froze some Google apps you can just use the pico package and avoid having to use TiBU entirely
Click to expand...
Click to collapse
I don't remember exactly... nothing I haven't frozen on their phones before.
You're saying that after doing the whole installation you set up the ROM, but after you freeze apps with titanium and reboot the phone refuses to boot?
Click to expand...
Click to collapse
It seems to be that way. I had already installed Magisk, but it's not like I installed Xposed or anything "dangerous" to the operation of the phone. The only thing I can think of is I froze something that kept it from booting. But if that's the case, why wouldn't reinstalling the ROM fix it? Wouldn't that fix anything I changed/froze?

Flapjack said:
I don't remember exactly... nothing I haven't frozen on their phones before.
It seems to be that way. I had already installed Magisk, but it's not like I installed Xposed or anything "dangerous" to the operation of the phone. The only thing I can think of is I froze something that kept it from booting. But if that's the case, why wouldn't reinstalling the ROM fix it? Wouldn't that fix anything I changed/froze?
Click to expand...
Click to collapse
well, if you wiped and installed everything again it should work...

Something must have been wrong with the ROM itself. I don't get it, since it worked fine the first install. I installed AOSP instead and it booted right up. I'm going to take a full backup, freeze the things I normally freeze, then see what happens.

I was having a very similar issue while trying to move to exactly the same ROM. My problem was that I was accidentally encrypting the phone (I didn't realize that this is what the "require pin at startup" prompt was doing). If TWRP is asking you to put in a pin number every time you boot into recovery, then your phone is encrypted. RR ROM (or at least the most common version of it) does not support encryption, so it will refuse to boot.
To get rid of encryption, you have to select the "format data" option in the wipe menu. You can't just wipe the usual partitions.
I can't be certain that this is your issue, but hopefully it helps.

beokabatukaba said:
I was having a very similar issue while trying to move to exactly the same ROM. My problem was that I was accidentally encrypting the phone (I didn't realize that this is what the "require pin at startup" prompt was doing). If TWRP is asking you to put in a pin number every time you boot into recovery, then your phone is encrypted. RR ROM (or at least the most common version of it) does not support encryption, so it will refuse to boot.
To get rid of encryption, you have to select the "format data" option in the wipe menu. You can't just wipe the usual partitions.
I can't be certain that this is your issue, but hopefully it helps.
Click to expand...
Click to collapse
Not similar at all. In your case the ROM would boot fine, but it woupd fail to load your data, so it asks for a password that not necessarily exists. In his case the ROM never gets to boot

Choose an username... said:
Not similar at all. In your case the ROM would boot fine, but it woupd fail to load your data, so it asks for a password that not necessarily exists. In his case the ROM never gets to boot
Click to expand...
Click to collapse
You misunderstand. I could only boot RR once, and if I accidentally encrypted the device during setup or afterward, the next time I tried to restart, it would be stuck on the boot screen. All subsequent reinstalls also got stuck on the boot animation since I wasn't removing encryption even if I wiped data, system, cache, etc. Moving to AEX allowed me to boot with encryption, and it was at that point that I realized my mistake. That sounds precisely like what is happening to flapjack, except that the cause may or may not be the same since he got through multiple boots the first time and presumably had already setup a pin/password on one of the first boots.
Immediately after the pin is setup should be when it asks if you want to require the pin on startup (aka if you want to encrypt), so if he opted to do that after setting everything up rather than on the very first boot, he may have exactly the same issue I had.

HELP: Encryption Unsuccessful TB-X104F

I i had to reflash the firmware the correct one TB-X104F_S000024_180930_ROW_DCC. Anyway it wasn't booting at all before i flashed. Now it boots, shows the logo etc and constantly says Encryption unsuccessful!, so i reset it and factory reset it but nothing changes.
I have no idea where else to go, bootloader is locked and all i can do is flash the firmware. Would there be a way to remove this from the files within the firmware?. It seems like android is there in the background but i can't get away from that encryption unsuccessful screen!
Sorry if none of this makes sense.

Yo. I got the same tablet bro. Been trying to figure out a custom recovery for her. A stock ROM would be great to have and I haven't been able to find one anywhere. Might I inquire as to where you found yours? It would be a huge relief to know I can fix it if I break it lol.

encryption
If you download the Lenovo MOTO smart assistant from Lenovo support it has a resque option. I also used that to root my tb-x104f. It downloads the original everything and if you take the boot image from the file it downloads and replace it in one that has been modified from magisk it will rescue it and you will have root also thatd what I did with mine

same problem here, reflashed with stock rom. and not resloved

frankieuk said:
I i had to reflash the firmware the correct one TB-X104F_S000024_180930_ROW_DCC. Anyway it wasn't booting at all before i flashed. Now it boots, shows the logo etc and constantly says Encryption unsuccessful!, so i reset it and factory reset it but nothing changes.
I have no idea where else to go, bootloader is locked and all i can do is flash the firmware. Would there be a way to remove this from the files within the firmware?. It seems like android is there in the background but i can't get away from that encryption unsuccessful screen!
Sorry if none of this makes sense.
Click to expand...
Click to collapse
Did you fix this issue?
I am having the same problem.
Thanks

Same problem here (my error reads "Decryption unsuccesful", but I think it's the same as yours).
After a few tries, I believe that it is a problem with the internet connection. After the factory reset, if I skip the wifi connection step, it starts normally. And it is completely usable. I can load pdf documents or apks by the usb from a computer and it runs correctly. But whenever I try to set the wifi connection, it updates something and it causes the tablet that the next time I turn it off, I find the error on the picture when turning on. It asks for a password and no matter which password you enter, then it delivers this message.
In resume, right now it is a completely functional tablet if you NEVER connect it to the internet and load anything you need via usb or bluetooth.
I tried to reset it with Lenovo Smart Assistant, but the result is the same.
I am looking for custom roms to try if it's something about the stock rom, but I haven't found any. Can anyone reccomend me a rom for Lenovo E10 X104F 2GB?

Solution: (Worked for me)
Format Data as F2FS in TWRP. (Advanced Wipe)
Then reboot and wait.