Database Info

Ran "Fix Permissions" in TWRP - Everything is missing

I can see my SDcard in Recovery and I can copy stuff off via MTP from recovery...
But after I ran Fix Permissions I rebooted. The system hung on the boot animation so I force power off.
I figured the permissions got screwed up for some reason so I decided to just reflash the system.img from fastboot.
So, I did that and rebooted.
On boot it didn't hang but it acted like I was setting up a brand new phone. I finally got to the desktop and while all my apps are installed still, everything is missing. I can't see anything on the sdcard and stuff seems generally screwed up. If I go in to the settings and look at storage it still showes I have 20-something gb's used up.
Ugh... I don't know what to do... sort of panic'ing right now.
Anyone got any ideas?
edit: something is royally hosed up. Even if I boot up in and go to es file explorer and try and create a new folder on my new "blank" sdcard space it gives a failed to create folder error. I think the fix permissions option royally screwed things up. Not sure if there is any coming back from this one

Read the /sdcard sticky in general

Thanks rootSU.
Yeah, something is definitely funky between current recoveries and Lollipop.
What I found out last night:
-I cut my losses and decided to hard wipe everything. I was able to DOWNLOAD files off my phone from TWRP 2.8.1.0
-I wiped, reflashed, got the half storage issue, flashed stock recovery, factory reset, all better
-Booted Lollipop, signed in, it autoinstalled my ~130 apps (this took a long time)
-I still had all my "sdcard" files I'd downloaded. My phone wasn't recognizing in windows mtp while booted in Lollipop so I decided to copy files BACK over in TWRP
-Copied over my 16gb worth of files in TWRP (this took a very long time). Once copied over it looked good in recovery and windows mtp
-Rebooted back in to Lollipop
-All of the files I had copied over in Recovery to my phone were unreadable. Folders were showing up as "?" icons in ES File Explorer. So, all that time I'd spent copying files over from recovery was ****.
-Went back to recovery, could see files again in TWRP. Since Lollipop couldn't read them, I decided I had to just delete them from recovery and just copy them over WIFI
-Deleted in recovery, booted back to Lollipop, copied over via wifi (took >2 hours to copy over wifi)
So... in summary, TWRP + Lollipop are definitely NOT playing nice together.
It was DEFINITELY the "Fix Permission" function that totally screwed me.
And the kicker...
I was running it because on every boot I'd see the "Android is Upgrading" message flash up for a couple seconds. I googled it and someone had recommended the fix permission function.
And it's still doing it now. I now believe it is caused by the current root method from chainfire and will have to live with it until it is fixed I guess.
Sigh.... what an incredibly long night.

And just discovered that the current TWRP folder on my phone is in this messed up state.
TWRP created this folder and it can only be viewed in recovery.
Even a root shell can't get in to it from ADB in Lollipop:
Code:
[email protected]:/sdcard # cd TWRP
cd TWRP
tmp-mksh: cd: /sdcard/TWRP: Permission denied
{
"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"
}

Yeah, I also have problems. Due to habit, I used "Fix Permissions" in TWRP - caused bootloop. Luckily i had just made a TWRP Backup, so I wiped the phone and restore it - worked fine again.
Guess I have to stay away from the feature until a fix.

I rooted my n5 lollipop.... But some rooted apps fail to get root access...like es file manager (root exp)...xmodgames...etc
In es it says failed test...and xmod shows device is not rooted
Sent from my Nexus 5 using XDA Free mobile app

Redux90 said:
Yeah, I also have problems. Due to habit, I used "Fix Permissions" in TWRP - caused bootloop. Luckily i had just made a TWRP Backup, so I wiped the phone and restore it - worked fine again.
Guess I have to stay away from the feature until a fix.
Click to expand...
Click to collapse
Yup, something is broken. I found out the hard way
myliferockkss said:
I rooted my n5 lollipop.... But some rooted apps fail to get root access...like es file manager (root exp)...xmodgames...etc
In es it says failed test...and xmod shows device is not rooted
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
This is completely unrelated to the topic of this thread. It's a known issue. Apps need to update how they're calling su.

GldRush98 said:
Yup, something is broken. I found out the hard way
This is completely unrelated to the topic of this thread. It's a known issue. Apps need to update how they're calling su.
Click to expand...
Click to collapse
Okay sorry boss *noob here*
Sent from my Nexus 5 using XDA Free mobile app

I too am in the same boat, I was able to restore to a previous backup but there are issues with some apps and my storage is messed up.
GldRush98 - I was a bit confused by your post, may you please clarify
I am thinking of copying my files over to me desktop via MTP in windows. Wiping and re-flashing. Then, I plan on copying over the files - Is this what gave you issues? or was it just the TWRP folder.
or would this idea work: Wipe, re-flash then restore a backup (before i fixed permissions)?
Thank you for your input

manny.m said:
I too am in the same boat, I was able to restore to a previous backup but there are issues with some apps and my storage is messed up.
GldRush98 - I was a bit confused by your post, may you please clarify
I am thinking of copying my files over to me desktop via MTP in windows. Wiping and re-flashing. Then, I plan on copying over the files - Is this what gave you issues? or was it just the TWRP folder.
or would this idea work: Wipe, re-flash then restore a backup (before i fixed permissions)?
Thank you for your input
Click to expand...
Click to collapse
If you copy files back in android it should be fine. Don't use adb or TWRP MTP. See my first post

Thank you for the quick response! I have been away from these forums for a while now and I'm not able to located the said sticky under General. One more question, besides abd or TWRP MTP what other options would I have?
Thanks again!!

rootSU said:
If you copy files back in android it should be fine. Don't use adb or TWRP MTP. See my first post
Click to expand...
Click to collapse
Yup, this is correct.

In my haste I totally misread rootSU's post. I got all my stuff out with Windows MTP, flashed the factory images and now I'm good!
Thanks again!

Same issue on nexus4.
I wasn't able to create a file/folder on the phone.
Tried fix permission and bootloop happened.
I don't want to re-wipe everything, maybe a only rom flash from twrp will help me?

mcgyver83 said:
Same issue on nexus4.
I wasn't able to create a file/folder on the phone.
Tried fix permission and bootloop happened.
I don't want to re-wipe everything, maybe a only rom flash from twrp will help me?
Click to expand...
Click to collapse
You can try the restorecon command from a terminal if you can get back in to Android.
Code:
su
restorecon -FR /data/media/0
reboot
I've seen others post that it is a potential fix.

Thank you man,I flashaed again the stock rom with data wipe.
I lost all my files but now all is working.
Many thanks

Hi guys, I have the same problem. Is there a solution to fix it, with full wipe? I can use just Odin because I can't get anywhere in the phone. I'm now trying stock room so hopefully it will work. If someone know the correct way to get working phone again let me know.
Thanks

Hello Everyone,
I fell victim to this issue and am a total noob when it comes to this. I was actually trying to remove the root and flash back to the stock software and accidentally ran the fix permissions expecting it to fix an issue that was arising. I have a ROM to restore but TWRP wont pick it up and I cannot seem to locate the proper directory folder. I already backed up all my data previously to starting and am ok with wiping everything but pretty much at this point I am at a loss.
If someone could help me out my email is [email protected]

I know it too late for you, but that is one feature I stay well away from. Never use it if you are reading this. Took me days to sort my phone out.

Ulefone Power 3 - TWRP 3.2.1-0 & Root (SuperSU)

This is a thread for the rooting and install of TWRP for the Uefone Power 3
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
TWRP 3.2.1-0: https://drive.google.com/file/d/1cLqcDrun5f6h1BHjUFfXDdlhwEWwM-49/view?usp=sharing
SuperSU: https://drive.google.com/file/d/1sZwahrodGJmYWzaIohxEETeIAabCOPfb/view?usp=sharing
Steps to install TWRP and SuperSU
Copy the above SuperSU to your SDCard.
First of all, you will be required to unlock your bootloader.
There is an option for this under Developer Options in the settings menu. Activate this.
Also activate USB Debugging. This makes this a whole lot easier.
Now, open a terminal, if on Linux, or command prompt if on windows, and enter the following:
Code:
adb reboot bootloader
Code:
fasboot oem unlock
Follow the onscreen instructions to unloack your bootloader. THIS WILL WIPE YOUR DEVICE!!!
Once this is complete, it will go back to the fastboot screen.
Now, from within your terminal/command prompt, navigate to the folder where you have downloaded the above recovery.img to.
Enter the following command once there:
Code:
fastboot flash recovery recovery.img
This will flash TWRP to your device, overwriting the stock recovery.
Once this is complete, there will be a screen telling you how long it took etc. Now you need to hold down your volume up button, and power button. Keep holding these untill you reach the menu for recovery, fastboot or normal mode.
Select Recovery.
This will boot into TWRP for the first time. when you get there, you will be prompted with a screen asking for a password. Cancel this.
WHAT EVER YOU DO, DO NOT FORMAT DATA LIKE IT ASKS YOU!"" YOU WILL LOSE TWRP!!!
Your then presented with the main TWRP screen, go ahead and tap on Install. Next, hit Select Storage, and select Storage 1. This is your SDCard.
Now flash SuperSU.
When this is installed, reboot to your main system, and update the SuperSu binary.
Now proceed to reboot back to recovery, how ever you wish.
Once in recovery, go into Wipe, and hit Format Data, this will wipe your phone again, but youve just done this anyway so it doesnt matter
Now flash SuperSU again, just to be safe, the same way as above.
Reboot to your system, and your done!
You will have to go through the setup of the whole android system again, but its worth it your now rooted and have TWRP to install the Custom ROMs that will be coming shortly
Have Fun!

Reserved

wow, that was quick thank you
will try it now and update as soon as it's done!

alright, so i tried to flash super su, but i never get to access the storage partitions (i think they are not mounted).
so i tried to factory reset / wipe the phone to get rid of the encryption, but i still cant select storage 1 from the menu.
here some more detail:
- i have already had the bootloader unlocked
{
"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"
}
- then i come to this screen when twrp starts, and select "swipe to allow modifications"
- then i press install and want to select "storage 1", this however doesnt work. (due to encryption?)
- i tried to mount it, but cant even mark it active. just gets gray for half a second and then nothing
- tried to do a wipe via twrp as well, with no success
any ideas?

tbst1337 said:
alright, so i tried to flash super su, but i never get to access the storage partitions (i think they are not mounted).
so i tried to factory reset / wipe the phone to get rid of the encryption, but i still cant select storage 1 from the menu.
here some more detail:
- i have already had the bootloader unlocked
- then i come to this screen when twrp starts, and select "swipe to allow modifications"
- then i press install and want to select "storage 1", this however doesnt work. (due to encryption?)
- i tried to mount it, but cant even mark it active. just gets gray for half a second and then nothing
- tried to do a wipe via twrp as well, with no success
any ideas?
Click to expand...
Click to collapse
Your third screenshot - what's the last option, under Microsd?
Also, when going through install, can u see "external SD"?

ukhellfire666 said:
Your third screenshot - what's the last option, under Microsd?
Also, when going through install, can u see "external SD"?
Click to expand...
Click to collapse
the last one is USB OTG, also showing 0MB - i actually tried flashing supersu through the usb as well, with no luck
i can see external_sd but there dont seem do be ANY contents
do you think it is the encryption? because everything shows 0MB in brackets
EDIT:
i just thought what the hell i try again to flash it via usb. havent changed anything but suddenly SUCCESS
appreciate your time thanks

tbst1337 said:
the last one is USB OTG, also showing 0MB - i actually tried flashing supersu through the usb as well, with no luck
i can see external_sd but there dont seem do be ANY contents
do you think it is the encryption? because everything shows 0MB in brackets
EDIT:
i just thought what the hell i try again to flash it via usb. havent changed anything but suddenly SUCCESS
appreciate your time thanks
Click to expand...
Click to collapse
So what did you do differently? If you can explain a bit more, I'll change/add it to the guide. Maybe as a second option or something...?

ukhellfire666 said:
So what did you do differently? If you can explain a bit more, I'll change/add it to the guide. Maybe as a second option or something...?
Click to expand...
Click to collapse
i just booted again into twrp and suddenly my 4gb usb was showing up as the only thing not 0mb, so the usb otg partition was mounted. from there on i just pressed install and located the zip file on the usb drive. had some errors. below some pics i took with my old phone:

tbst1337 said:
i just booted again into twrp and suddenly my 4gb usb was showing up as the only thing not 0mb, so the usb otg partition was mounted. from there on i just pressed install and located the zip file on the usb drive. had some errors. below some pics i took with my old phone:
Click to expand...
Click to collapse
Ahhh brilliant! I don't suppose u found that he sdcard was mounted too did you?
Have the errors gone now your rooted? The rest of the guide should still count...?

ukhellfire666 said:
Ahhh brilliant! I don't suppose u found that he sdcard was mounted too did you?
Have the errors gone now your rooted? The rest of the guide should still count...?
Click to expand...
Click to collapse
yes i am indeed rooted!
everything else, including internal storage was 0mb as well. usb otg was literally the only one.
i have not gone back into recovery since, but rebooted several times and also used root apps (adaway). everything seems to work great and the rest of the guide still counts!
in total, everything seems stable until now :good: my goal is to not touch twrp anymore until android 8.1 will be released

tbst1337 said:
yes i am indeed rooted!
everything else, including internal storage was 0mb as well. usb otg was literally the only one.
i have not gone back into recovery since, but rebooted several times and also used root apps (adaway). everything seems to work great and the rest of the guide still counts!
in total, everything seems stable until now :good: my goal is to not touch twrp anymore until android 8.1 will be released
Click to expand...
Click to collapse
The official 8.1 update with overwrite TWRP.
I am now working on a cm14.1 build. As im having to use a prebuikt kernel, this is as far as I can go.
As soon as I have a beta ROM I'll upload.
Don't suppose you could boot to recovery and just double check that everything is as it should be? Put my mind at ease, make sure it works for you, as it does for me...

ukhellfire666 said:
The official 8.1 update with overwrite TWRP.
I am now working on a cm14.1 build. As im having to use a prebuikt kernel, this is as far as I can go.
As soon as I have a beta ROM I'll upload.
Don't suppose you could boot to recovery and just double check that everything is as it should be? Put my mind at ease, make sure it works for you, as it does for me...
Click to expand...
Click to collapse
sure man, maybe joining me on discord would make this process faster https://discord.gg/jPZqn4

Hi.
Thank you for twrp.
I am trying to use SuperSu with SuHide, i wipe data with this twrp to be able to install supersu in BINDSBIN mode to /data but data partition stay unencrypted to be mountable with thw twrp.
How to encrypt it back with own known password keeping supersu and suhide working?
TWRP has no option to reformat with password, no way to get origin password for stock recovery formated partition.
Any idea?

MioCZ said:
Hi.
Thank you for twrp.
I am trying to use SuperSu with SuHide, if i wipe data with this twrp to be able to install in BINDSBIN mode to /data but data partition stay unencrypted.
How to encrypt it back with keep supersu and suhide working?
TWRP has no option to reformat with password, no way to get origin password for stock recovery formated partition.
Any idea?
Click to expand...
Click to collapse
No idea I'm afraid. Sorry.

I used encryption in system Setup, i works, but with unknown password stored somewhere in nvdata partition. I am worry about loose root after OTA update and without pasword for twrp no way to get again to data partition.

I'm thinking of buying this phone. It's great to see that root already seems to work and that there might be a CM/LineageOS Rom soon. Root and custom recovery is crucial so one reason less to not buy it.
Are you guys happy with it in general? Does the dual camera work with bokeh and shoot good photos with low lag required to capture playing kids? Good value?

I can not install Snap Chat
Thank you ukhellfire666
The recovery was successfully installed
My question:
is there any idea to fully remove superSu to install snapchat
A full system backup has been taken.

DaF1974 said:
I'm thinking of buying this phone. It's great to see that root already seems to work and that there might be a CM/LineageOS Rom soon. Root and custom recovery is crucial so one reason less to not buy it.
Are you guys happy with it in general? Does the dual camera work with bokeh and shoot good photos with low lag required to capture playing kids? Good value?
Click to expand...
Click to collapse
good day to you.
in general i am happy with it, but the camera really blows. it is - without a doubt - the worst camera i had since my LG VX-5200. iphone 6s and galaxy s6 have way better cameras.
i am really frustrated, because they advertised the 4 cameras ..." " heavily, but they really suck. maybe it's just with the stock app and another app would make it better (but somehow i doubt that)
tomorrow i will go on holiday and was stoked that the phone arrived before, so i could take it with me to take pictures etc. seems like i will need to get the old digital camera out....

alshyib said:
Thank you ukhellfire666
The recovery was successfully installed
My question:
is there any idea to fully remove superSu to install snapchat
A full system backup has been taken.
Click to expand...
Click to collapse
Is possible to flash un-supersu package. Is somewhere in SuperSu topic. Or you can flash clean ROM / your backups (boot.img, recoovery.img, system.img).
Because this i have used supersu in BINDSBIN mode and suhide. So i have hiden su, locked bootloader, working OTA and all root sensitive apps.

bootloop
Hello, I followed the instructions but my phone bootloop on twrp, it does not start the system can you help me please?
---------- Post added at 02:23 AM ---------- Previous post was at 02:21 AM ----------
Hello, I followed the instructions but my phone bootloop on twrp, it does not start the system can you help me please?

[GUIDE][SAMSUNG] Unlock Forgotten Private Mode PiN/Password/Pattern

Hello xda,
Today I'll guide you how to Unlock/Recover your data in private mode if you forgot it's authentication.
Before proceeding: I'm not responsible for any damage to your device or data.
Pre-Requirements:
1. Rooted Device (If you have enough knowledge of adb, you may go with adb instead of root)
2. Root Explorer installed.
Let's Get Started:
1. In your Device, when you try to turn on 'Private Mode' , What does it ask for?
a. If it asks for pattern , Download this file
b. If it asks for PIN (Only numeric keys shown), Download this file
c. If it asks for Password, Download this file​If you are not sure what to download, download all 3 files given above.
2. Copy the downloaded file(s) to your phone.
3. Open 'Root Explorer' , Navigate to data/system/
4. Copy the file(s) downloaded from above in this directory (data/system/) , If it asks, Tap 'Replace'
5. Long Press the file you just pasted here, Tap 'Permissions' Check only 'Read' and 'Write' of Owner. So that it looks like this:
{
"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"
}
Tap 'Ok'.
6. Reboot Device.
7. Un-Root your phone. [This is not compulsory but some phones cause problems if you don't unroot]. Thanks to iderayoub for useful point.
8. When it reboots, try to turn on 'Private Mode', Enter PIN: 1234 / Password: xda123 , Pattern: See this Image
Now, you may change the PIN/Password/Pattern anytime. ___________________ [Try to Smash the Thanks Button Below :fingers-crossed:]

It works!
For reference, the contents of that /data/system/personalpin.key file should be:
FA6C0E1B2B0581C2F359B8923F2FA7164B21CC7E
I had to really reboot and close Gallery before my "Private" Album came back, but it eventually did.
Thanks!

cd1207 said:
It works!
For reference, the contents of that /data/system/personalpin.key file should be:
FA6C0E1B2B0581C2F359B8923F2FA7164B21CC7E
I had to really reboot and close Gallery before my "Private" Album came back, but it eventually did.
Thanks!
Click to expand...
Click to collapse
Glad to hear that, BTW, Was it necessary to close the gallery after rebooting?
I mean, Just a reboot was not enough to bring the Private Mode back?

Can you provide instructions for ADB please?
Also, doesn't rooting the phone trip Knox, which disables private mode? Would this method still work if rooting disables private mode?
Which rooting method would you recommend that does not factory reset / wipe data?
Will this work on G935V with Android 6.0.1?
Please respond with whatever you know, even if you don't know all the answers to all these questions, thanks in advance!

AGorrila said:
Can you provide instructions for ADB please?
Click to expand...
Click to collapse
Google it: "How to push files using adb". So, You just need to push your relevant file (i.e. PIN/Pattern/Password) to /data/system.
AGorrila said:
Also, doesn't rooting the phone trip Knox, which disables private mode? Would this method still work if rooting disables private mode?
Click to expand...
Click to collapse
I can't say a word as I never had a Knox-powered phone and never tried it. So If going to root, Proceed on your own risk.
(If you ask about my opinion, I don't think that you will lose your data which is in Private Mode).
AGorrila said:
Which rooting method would you recommend that does not factory reset / wipe data?
Will this work on G935V with Android 6.0.1?
Click to expand...
Click to collapse
Here is the page where you can download the rooting files for your device: (Only for G935V). This method doesn't factory reset / wipe data. I've tried it 50+ times. If you don't know how to use these files. Google it "How to root using AutoRoot". Good Day!

pattern
hi
the pattern does not work for s7 edge plz help me.

elhamfarnad said:
hi
the pattern does not work for s7 edge plz help me.
Click to expand...
Click to collapse
The pattern is exactly as shown in the picture here. https://drive.google.com/open?id=13YQlte3oAjxl1VAYBqBF6XcfYXGYw0L_
Did you copy exactly the personalpattern.key file and pasted it in data/system/ as mentioned?
P.S. Don't forget to reboot after placing the file in data/system/.

reboot
i did but what do u mean by reboot i just turn if off and then on.

elhamfarnad said:
i did but what do u mean by reboot i just turn if off and then on.
Click to expand...
Click to collapse
Press and Hold power button. Select Restart. Confirm

elhamfarnad said:
hi
the pattern does not work for s7 edge plz help me.
Click to expand...
Click to collapse
Did it work or not?

Sasmsung s5 neo adb enabling by boot.img/Pattern forgot
Hey I already asked this on another thread but this might help me better:
Hi I am locked out of my galaxy s5 neo because of my stupidness. (guess what happend...) While changing the pattern I received a call and answered it. I then talk to the person for about 5 min. I leave my phone for 30 mins then I comeback and forgot my pattern. So far usb debugging is not on and oem is locked. A way to get in my phone would be to enable bluetooth since I have a trusted device that I can unlock my phone with. Something I also tried is taking the boot.img of my device and manually enabling the adb by editing default.prop in ramdisk. Only problem is when I repack it, it is detected as a custom binary wich is weird because it's the original one for my device. Anyway out of ideas, and I can't upload twrp or any custom rom either (unless there's a bypass that I don't know). Thx in advance.
Send from my browser since my phone is locked otherwise my phone is a Samsung Galaxy S5 Neo (SM-G903W/Canada) with stock android 7.0.

TheScreamerBoy2301 said:
Hey I already asked this on another thread but this might help me better:
Hi I am locked out of my galaxy s5 neo because of my stupidness. (guess what happend...) While changing the pattern I received a call and answered it. I then talk to the person for about 5 min. I leave my phone for 30 mins then I comeback and forgot my pattern. So far usb debugging is not on and oem is locked. A way to get in my phone would be to enable bluetooth since I have a trusted device that I can unlock my phone with. Something I also tried is taking the boot.img of my device and manually enabling the adb by editing default.prop in ramdisk. Only problem is when I repack it, it is detected as a custom binary wich is weird because it's the original one for my device. Anyway out of ideas, and I can't upload twrp or any custom rom either (unless there's a bypass that I don't know). Thx in advance.
Send from my browser since my phone is locked otherwise my phone is a Samsung Galaxy S5 Neo (SM-G903W/Canada) with stock android 7.0.
Click to expand...
Click to collapse
So, The point is: You don't want to lose your data, otherwise you'd just have resetted it. Right?
If yes, You can copy your data using adb pull command If you have authorised any computer in usb debugging. And then Reset it?

zubair1836 said:
So, The point is: You don't want to lose your data, otherwise you'd just have resetted it. Right?
If yes, You can copy your data using adb pull command If you have authorised any computer in usb debugging. And then Reset it?
Click to expand...
Click to collapse
yes but usb debugging is disabled.

TheScreamerBoy2301 said:
yes but usb debugging is disabled.
Click to expand...
Click to collapse
Well, I don't think if there's a way to unlock the phone without losing data.
If you find one, Enlighten me too

Couldn't manage
zubair1836 said:
Hello xda,
Today I'll guide you how to Unlock/Recover your data in private mode if you forgot it's authentication.
Before proceeding: I'm not responsible for any damage to your device or data.
Pre-Requirements:
1. Rooted Device (If you have enough knowledge of adb, you may go with adb instead of root)
2. Root Explorer installed.
Let's Get Started:
1. In your Device, when you try to turn on 'Private Mode' , What does it ask for?
a. If it asks for pattern , Download this file
b. If it asks for PIN (Only numeric keys shown), Download this file
c. If it asks for Password, Download this file​If you are not sure what to download, download all 3 files given above.
2. Copy the downloaded file(s) to your phone.
3. Open 'Root Explorer' , Navigate to data/system/
4. Copy the file(s) downloaded from above in this directory (data/system/) , If it asks, Tap 'Replace'
5. Long Press the file you just pasted here, Tap 'Permissions' Check only 'Read' and 'Write' of Owner. So that it looks like this:
View attachment 4435791
Tap 'Ok'.
6. Reboot Device. (We're all set)
7. When it reboots, try to turn on 'Private Mode', Enter PIN: 1234 / Password: xda123 , Pattern: See this Image
Now, you may change the PIN/Password/Pattern anytime. ___________________ [Try to Smash the Thanks Button Below :fingers-crossed:]
Click to expand...
Click to collapse
Hi was asking password
I did what exactly you mentioned but no result
S7 edge
Oreo 8.0
Rooted phone

ebayusuff said:
Hi was asking password
I did what exactly you mentioned but no result
S7 edge
Oreo 8.0
Rooted phone
Click to expand...
Click to collapse
Thanks for reporting!
1. Please don't quote such a long post, Simply "Reply".
2. Some other users of S7 have reported it not to be working for them, As I don't have S7 , I'll try to test this on someone's phone if he agrees.
It will take a maximum of 1 week.
Then I'll update. Now it's up to you if you can wait.

Ok
Thank you. Waiting you.

Private mode failed to turn on
Galaxy S7 edge cannot access private mode. It allows me to enter the correct pattern and then says,"Failed to turn on private mode. Try again"
As I said before İ forgot password then backed up with titanium and deleted private mode. Then tried to restore with app only choice. Titanium couldn't manage to restore. Restarted phone. Then it started to work, remembered forgetten password then changed it to pattern. As far as I remember I managed to enter to the private mode once or twice. But now gives this error. I think no way except to resetting phone.

+1 but with PIN
ebayusuff said:
Private mode failed to turn on
Galaxy S7 edge cannot access private mode. It allows me to enter the correct pattern and then says,"Failed to turn on private mode. Try again"
As I said before İ forgot password then backed up with titanium and deleted private mode. Then tried to restore with app only choice. Titanium couldn't manage to restore. Restarted phone. Then it started to work, remembered forgetten password then changed it to pattern. As far as I remember I managed to enter to the private mode once or twice. But now gives this error. I think no way except to resetting phone.
Click to expand...
Click to collapse

Rename File in Android 7.x.x
I was try your way but doesn't work so in android 7.xx and may be higher you must remove all locksettings.db in /data/system and then rename getkeeper.password.key for password getkeeper.pin.key for pin and getkeeper.pattern.key for pattern.
REBOOT NEED
after reboot and open private mode or even applock mode(remove applock.key) you must force stop Gallery!
Note:before proceed remove all getkeeper.xxx.key files in /data/system

Pioneer XDP-300R Digital Audio Player - Root, TWRP Recovery, and Mods

{
"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"
}
I've been successful at porting over TWRP (Team Win Recovery Project) Recovery to the Pioneer XDP-300R Digital Audio Player! The recovery can be flashed directly over the stock recovery using Fastboot, or you can temporarily boot into it using fastboot.
First off, TWRP, replaces the stock recovery and allows users to backup and restore system, data, boot and other partitions on their player onto their storage or sdcards. It also can install superuser (root) access if you want that feature to allow editing and modifying of the system folder. That opens the door for additional mods.
You can also install Magisk, which is a systemless root feature that is a little safer since it does not touch your system folder, but instead patches the bootloader and then creates a layer above system that stores the mods and changes within the Magisk system in.
First off, I made system image, bootloader and recovery images of the stock 300R prior to going into this full swing. I had already rooted my device using Kingoroot but this is no longer needed and is much more safe now.
So you'll want to get the recovery first.
https://drive.google.com/open?id=1diqQ8LE-yG4b-WZFB_OPcQp2rDUp9BbV
The link in my google drive will take you to a folder where I have backups of my images. The TWRP recovery is located in the Recovery folder, along with the stock Recovery image.
Tools Needed:
Android USB drivers for ADB and Fastboot
ADB and Fastboot
Terminal or Command Prompt
Some basic knowledge on how to use these tools
Pre-Installation:
In android, go to Settings, and turn on Developer Mode. To do this, click Settings, then Device Information, then scroll to Build Number. Tap this several times until you unlock Developer Options.
Now, go back to the Settings Menu and go to the new Developer Options menu. Check the OEM Unlocking option to allow the bootloader to be unlocked.
Installation of TWRP:
1. Download the TWRP image and place it in the same folder as ADB/Fastboot tools.
2. Open a terminal or cmd prompt window and go to the folder in (1)
Code:
EXAMPLE: cd /android
3. Turn off the 300R. Then hold next track (the button closest to SD slots) and press power and let go while holding the next track button. A Penguin will appear on screen. Then let go, and plug device into computer.
4. In terminal, check to see if fastboot works.
Code:
fastboot devices
5. If it does not show a device, check your drivers! If you see a device, let's go forward!
6. Now we will install the recovery.
First we need to unlock bootloader:
Code:
fastboot oem unlock
If you are nervous, and want to verify it works, you can do a temporary test by typing the command:
Code:
fastboot boot TWRP-XDP-300R.img
This will boot directly into the TWRP recovery and will go away when you restart. But you can see if it works this way and mounts each folder correctly.
If you're ready to take the plunge, use this command:
Code:
fastboot flash recovery TWRP-XDP-300R.img
7. Once it flashes, you can always reboot into recovery by powering off. Then holding PREV TRACK (button closest to power) and power on. It'll show the penguin, and then load recovery soon after.
8. Once you see the TWRP screen youre good to go! I recommend making a System, Data, and Boot backup immediately so you have it ready. I also have the stock recovery in the folder for backup purposes too!
Root Access
When you exit TWRP, you have the option of installing SuperUser (root) access. You're welcome to install or decline it. I recommend using Magisk at this point, by looking up Magisk Manager and loading that onto your device. It'll also provide root access along with other goodies like Xposed, some adblocking stuff, and if you like, Viper4Android, and other mods.
To first start the process of Magisk, you need to unlock the bootloader. Go into Fastboot mode again on the phone, as described above, and go to command prompt:
Code:
fastboot oem unlock
This command will unlock the bootloader. In the future, you can lock it by replacing unlock with lock: fastboot oem lock
Magisk only installs correctly when you use the magisk zip file that can be downloading through Magisk Manager. This zip file needs to be flashed in TWRP Recovery. Once you do that, it'll patch the bootloader and allow Magisk to work correctly. You can verify by opening Magisk Manager in Android, and seeing if it is activated.
Once activate, you can click the menu on the left side of the Manager app, and click DOWNLOADS to find a list of modules available for use. Not all are compatible with the older Android Lollipop that is on XDP-300R, so be careful of that.
Magisk Modules
Some modules I use are:
Xposed Framework - another modding system - see below
LKT - tweaks to the kernel for battery management
Magisk Manager for Recovery Mode - Recovery command line manager (seems buggy)
SafeMode4Magisk - Boots into safe mode for disabling bad modules
Swap Torpedo - Optimizes Swap files for RAM management
Youtube Vanced - Themes and removes ads from Youtube
Greenify - adds additional features to Greenify app
Xposed Framework (now systemless using Magisk!)
Some modules I use are:
Amplify - Standalone app that needs Xposed for disabling or reducing amount of system wakelocks and alarms which greatly save battery life
Greenify - Standalone app that hibernates unused apps to save battery life and uses Xposed for additional features
Youtube AdAway - Removes ads from Youtube
BUILD.PROP MODS
The Drive Link at the top of this page has my modified build.prop in it. You can replace your existing build.prop with this if you want. Make sure you make a backup just in case!
Diverting sound away from Android OS to the DAC:
Open up BUILD.PROP in /System in your android device and look for PCM Offload
There are two lines there, that start with audio.offload...
Remove the Hash in front of each of them if they are present and that's it!
it should read:
Code:
#PCM offload
audio.offload.pcm.16bit.enable=true
audio.offload.pcm.24bit.enable=true
Also verify that this is enabled:
Code:
av.offload.enable=true

Hi ! Thank your for your work ! There are a version for the XDP-100R please ?
(sorry for my bad english)

HI, I'm thankful for your development. But is there any chances to reflash the firmware if something goes wrong?

A few days ago on my xdp300r part of the system spilled out and actually are system applications. Nothing can be installed on it, is there any possibility of restoring the original state? Restarting and recovery mode unfortunately did not help.

Thanks alot. I needed this so bad. A long time after I bought XDP300R I can only dare to use superSU to get root access and that's it. And now xposed and magisk are possible, Thank you soo much.

Hi thanks. I managed it fine. I used su as majisk would not install. Luckily I followed your advice and made a backup(I don't usually bother). I installed your build.prop and the pioneer would not boot. I have restored using twrp and changed my own build.prop so alright now. Thanks.

HI GUYS.
I am trying to unlock my 300R.
When I execute 'fastboot oem unlock' I got DENIED message.
I am stuck. Is there any hope for my player?
Daniel

gavroche33 said:
HI GUYS.
I am trying to unlock my 300R.
When I execute 'fastboot oem unlock' I got DENIED message.
I am stuck. Is there any hope for my player?
Daniel
Click to expand...
Click to collapse
have you enabled the OEM unlock in the developer setting?

I do not have option like that. My player was cleared from data, but it is still locked. I cannot OEM unlock it
Any other way?
Daniel

Grazie mille per il tuo lavoro

gavroche33 said:
I do not have option like that. My player was cleared from data, but it is still locked. I cannot OEM unlock it
Any other way?
Daniel
Click to expand...
Click to collapse
Go to setting, to Device Information, to Build Number. Tap 7 times. You get Developer Options
Back up go to Developer Iptions, select OEM Unlocking.
Re-do OEM unlocking as described in OP

Hi,
I tried to follow this tutorial but my device is not show I checked the drivers!
But still the same, is it possible to had any help ?

Since we already have an open bootloader, is there a chance to make a newer android, I propose version 9 because in newer ones you lose the ability to play some formats, it would certainly give a second life for this model

Dear XDA forum readers/members,
I have an issue with my Pioneer XDP-300R. At this stage I can only boot into it with the TWRP (TWRP-XDP-300R.img) image provided in the first post. I also have downloaded the recovery files, including the (stock?) system image (system-noxposed.img).
When I try to flash the same image from within TWRP, I can only select the "boot" or "recovery" partitions. In this screen, there is no option to boot towards a "system" partition.
If I boot from a ZIP file containing the system-noxposed.img file, I obtain either a different error which complains about a META-INF and binary not found? , or I obtain an error which (of course) writes there is too little space to write a system image in a boot or recovery partition.
My question(s) is/are: Is there any method to flash a system image towards the system partition from within TWRP, and/or how to solve the "unknown chunk type" error?
Any help would be greatly appreciated.
EDIT: The issue has been solved, but there is another problem now. When the device would not boot TWRP anymore (as in: froze at TWRP logo) I decided to look at the partitions (with dd): Now, I had made the mistake of overwriting the very first boot partition, and now the device will not power up anymore. By all means and purposes, he is hard bricked now If there is anyone who would like to help, I'd be very grateful, assuming there are still options left.
Greetings from a new member in need of help

Development [RECOVERY][UNOFFICIAL][EXPERIMENTAL][ALPHA] TWRP for Galaxy A22 5G SM-A226B

{
"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"
}
It took me sometime, but I can now share with you a TWRP with basic functionality. You of course flash at your own risk. I am not responsible for lost warranty, lost data or any other damage to your device.
This Build of TWRP is based on:​
Firmware: A226BXXU4AVB1(Android 11) and A226BXXU4BVF7(Android 12)
TWRP-11 minimal manifest or TWRP-12.1 minimal manifest
Device Tree
Kernel source
Working:​
flash of zips
fastbootd
flashing of GSI images (via fastbootd)
MTP
Not working:​
Probably a lot of stuff ...
What you need:​
Unlocked bootloader.
Odin3 v3.13.1
android platform-tools and device driver.
adb and fastboot
Magisk or GSI depending on what you want to do.
Patience, the device can be very tricky to get to download mode.
How to flash:​Be advised that this build is a work in progress and is not ready as a daily driver. Only flash if you know what you are doing.
Spoiler
First read all points below, without doing anything. Warning, you will lose all your data!
If you are on Android 11 firmware download v1.01.2-alpha if you are on Android 12 firmware download the recovery.tar from here.
You start off in Odin, put recovery.tar in AP slot and the vbmeta_disabled_R.tar in the USERDATA slot, uncheck auto-reboot.
After the flash is completed hold down power + volume down, instantly after device goes Black screen press and hold power + vol up to boot to TWRP
if you didn't get to TWRP, you have to flash again.
In TWRP, go to Advanced → terminal.
Type multidisabler two times.
Now go to Wipe → Format Data (not wipe) → and type yes.
You can boot to system now.
Hot to install Magisk:​
Spoiler
Method 1, Micro-SDCard​
Download Magisk from here, rename the file from .apk to .zip
Save the file to a Mico-SDCard
Reboot the phone to TWRP.
Go to Install → Select Storage → Micro-SDCard. In the file system, choose Magisk-vXX.X.zip and swipe to confirm flash.
You can now Reboot to System
Method 2, sideload​
Download Magisk onto your PC from here, rename the file from .apk to .zip.
Reboot the Phone into TWRP. Go to Advanced → ADB Sideload → Swipe to start Sideload.
On your PC, type in a Terminal adb sideload Magisk-v24.3.zip
You can now Reboot to System. adb reboot system
How to install GSI:​
Spoiler
Go to Wipe → Format Data (not wipe) → and type yes.
Now reboot to fastboot.
Connect the phone to your pc and startup a terminal of your choice.
In the terminal type fastboot flash system name-of-your-gsi-iamge.img (it has to be a .img file, extract .img.xz files do not just rename them).
You should now be good to go and can reboot to system.
Thanks and credits to:
cheese-ass
akhil99
TeamWin

How to get TWRP log files:​recovery.log
adb pull /tmp/recovery.log
OR
Advanced -> Copy Log -> Swipe to copy log to default storage
dmesg
adb shell dmesg > dmesg.log
OR
Advanced -> Copy Log -> check "Include kernel log" -> Swipe to copy log to default storage
logcat
adb logcat -d > logcat.txt
OR
Advanced -> Copy Log -> check "Include Logcat" -> Swipe to copy log to default storage

Changelog​v2.00.1-alpha​
bump firmware and touchscreen drivers to A226BXXU4BVF7 and TWRP to TWRP-12.1
v1.02.2-alpha​
added drivers for himax touch screens.
v1.02.1-alpha​
added drivers for novatek touch screens.
v1.01.2-alpha​
added patch with improved multidisabler
v1.01.1-alpha​
update multidisabler
v1.01.0-alpha​
fix permission for mkbootimg
v1.00.0-alpha​
Initial Release

This has been tested, right? If it does work, I'll probably try it out when I have free time, which might be in a few days.

Yes, it runs on my A22 5G.

Could-Chaplain said:
Yes, it runs on my A22 5G.
Click to expand...
Click to collapse
It worked. But I didn't read your post carefully and now I have to format data :/
Edit: Ran multidisabler twice. On the second time, it said that /system was an invalid argument
Edit2: Trying to mount partitions don't work, like trying to make a backup or using the file manager. Speaking of backups, I didn't format data because I really don't want to, and it rebooted safely (Thank god), so now I'm making a backup of apps I should have made a week ago.

Edit: Ran multidisabler twice. On the second time, it said that /system was an invalid argument
Click to expand...
Click to collapse
It's the same for me, but no issues so far.
Edit2: Trying to mount partitions don't work, like trying to make a backup or using the file manager. Speaking of backups, I didn't format data because I really don't want to, and it rebooted safely (Thank god), so now I'm making a backup of apps I should have made a week ago.
Click to expand...
Click to collapse
That will be because you didn't format data. If I find sometime, I will try to reproduce that. Thank you, for testing.
Edit: Backups should work fine if you uncheck data?

Is the A226BZH3AUL1 suitable？

a0963655966 said:
Is the A226BZH3AUL1 suitable？
Click to expand...
Click to collapse
If your device is a SM-A226B you should be fine. But as always, flash at your own risk.

Works great! Thanks! Keep up the good work!
Any idea why adb shell doesn't work? For the same reason why /data isn't mountable?

Thank you! Going to test asap.

lebigmac said:
Works great! Thanks! Keep up the good work!
Any idea why adb shell doesn't work? For the same reason why /data isn't mountable?
Click to expand...
Click to collapse
/data is most likely not mountable because you didn't run multidisabler twice and formatted data? ADB shell works fine for me, check in device manager that it shows up as ADB Interface.

Tested working, but haven't succeeded flashing a gsi yet, phone reboots and then goes to blank black screen, and ideas?

koosman911 said:
Tested working, but haven't succeeded flashing a gsi yet, phone reboots and then goes to blank black screen, and ideas?
Click to expand...
Click to collapse
Honestly, it could be everything. Just go over How to flash again. But this time without vbemta and multidisabler. Then continue as described in How to flash GSI. Please let me know if that works for you.
I recommend Pixel Experience.

Could-Chaplain said:
Honestly, it could be everything. Just go over How to flash again. But this time without vbemta and multidisabler. Then continue as described in How to flash GSI. Please let me know if that works for you.
I recommend Pixel Experience.
Click to expand...
Click to collapse
Are you using pixel experience on your device currently?

koosman911 said:
Are you using pixel experience on your device currently?
Click to expand...
Click to collapse
Yes and no, currently I am working on TWRP and there for flash the stock Rom quite frequently. But I do plan to use Pixel Experience. The only thing that does not work is NFC. But that seems to be the case with all the GSI I could find, as they are all based on phh.

Hey Guys, I did some work on the TWRP recovery. It's now more reliable, I highly recommend the update. You will find the download link and updated instructions at the top.

Thank you sir, updated recovery works perfectly on two separate phones so far, I've flashed a few gsi's and they work as far as they are able to obviously each gsi might have its own issues, the two phones I have don't have Nfc so I can't help to test that sadly. We appreciate the hard work.

koosman911 said:
Thank you sir, updated recovery works perfectly on two separate phones so far, I've flashed a few gsi's and they work as far as they are able to obviously each gsi might have its own issues, the two phones I have don't have Nfc so I can't help to test that sadly. We appreciate the hard work.
Click to expand...
Click to collapse
Thank you. What other phones despite the A22 5G are you using the recovery with?
Edit: Ahhh, you mean, you have nothing to test NFC with?

The model of a22 5G available in my country does not have nfc.