Related
Sharing my experience with the leaked I317UCUBMJ4 Firmware for AT&T Samsung Galaxy Note II. I compiled all info here from my reseach. Most of the information is available on the internet. I have not built, uploaded, modified or developed any of these apps. Just sharing with the community what worked for me. pieces of these of info also available in fragments in xda developers and other web sites. Some parts of the processes requires you to install paid apps that has worked for me. If you know similar free or paid apps that can do the same job feel free to use them. I am basically showing here what worked for me.
First Goal: Downloading the ROM and Rooting the device.
Attention: This update will flash your boot loader, Recovery, system, data, basically everything in your note 2 ( will void your warranty too) and install stock I317UCUBMJ4 except the external sd card. Also Samsung KNOX will be part of your system. Good news is it can be removed easily with Super su app.
Step 1: Download and install the the file named : I317UCUBMJ4_OneClick.zip
This rom has an executable ODIN built-in so it is a no brainer. Just put your phone to download mode (while your phone is turned off, press home+ volume down and power button) and install the necessary drivers to your pc
mega.co.nz/#!alo3HAZC!L8nSwjeElTwJP2hTcsWQu2cjh8hQCpuNaccpX2__ph4
MD5: 170372B98BD00151856EF5E22A1DA4E3
SH1: 32487EF4D9A80DBD0A7FF9EC6B1D991736EF0DBE
CRC32 : 5D2A5F9F
Step 2: Follow the instructions in this page for rooting your device:
wccftech.com/root-galaxy-note-2-on-android-4-3-ucubmk6
Step 3: Login to your play store account and download rom toolbox pro and update super su binaries. Super su will ask you whether you want normal or twrp/cwm for update just choose normal. It will also ask you whether you want to remove the Samsung KNOX. just disable it. If super su hangs while disabling knox or updating binaries just quit the app and re-do the process. Restart your phone.
Second Goal: Encrypting your device without unrooting it and changing your encryption password without changing your screen lock password.
Note: Android doesnt allow you to encrypt your device without unrooing it so here is the trick to achieve it.
Step 2: Download and install xposed installer (and update it from the inside of the app), busy box free, and wanam xposed from play store.
Step 3: Launch wanam exposed, tap security hacks, check "Fake system Status" This step will fake the android encryption module that rom is "not rooted", Hit back button on your phone and reboot your phone.
Step 4: Go to system settings tap "More" tab, tap security, tap encrypt device and fiollow the instructions word by word.
Step 5: At this point I am assuming that you have followed the encryption instructions and encryped your device successfully. Reboot your device and you will realize that android doesn't give you the option to change the encryption and lock screen password individually. So it automatically sets your lockscreen password as your encryption password. If you change your lockscreen password your encryption changes and becomes the same paswword.
Step six: Launch rom toolbox pro or your terminal app (I used rom toolbox pro so I don't know whether other apps would work or not) Scroll down and tap terminal emulator. type "su" without the quotes and hit enter. type "vdc cryptfs changepw newpass" without the quotes and hit enter.The word "newpass" SHOULD BE REPLACED with whatever your encryption password is. Reboot phone and test your password. Make sure you remember your password exactly, otherwise it'll be impossible to access your phone, so pay attention to what you are typing as password or else you'll have to factory reset and redo from start. So be calm and take your time with this critical step.
Now you'll see the lock screen and encryption password are different. Purpose of this goal is to help the user to encrypt their phone with a long password and use a shorter one for the lock screen since you probably don't want to type 20 characters to unlock your screen each time.
Goal Three: Enabling the hotspot:
This ROM has a broken tethering hotspot app so You don't need steps just install WIFI Tether Router from play store. Leave all settings untouched (except changing the user name and password of course) it'll do all automatically.
Extra info: As a personal choice I installed TWRM recovery by using rom toolbox pro, like I stated before this flash also installs stock recovery. So, Launch it, tap on rom installer, slide screen right and tap on flash recovery. TWRP is all the way on the top and install it (my personal choice)
I was excited to see this post, thanks for doing some ground work.
I tried with a ucucne5 firmware from here and followed your instructions but it didn't work. Ill try with an MJ4 firmware next if i can.
thanks again for post:good:
PS your link to mega for the MJ4 firmware doesnt work, has a space in it.
Guys,
my OP3 is bootloader unlocked, rooted and encryption switched off.
Standard system was OOS 3.1.2. I installed the update to 3.2.1 via TWRP zip and found some bugs, so I decided to use the [ROM] [6.0.1] Unofficial CyanogenMod 13
from Grarak. Did a full wipe installed and all is ok. Now comes the strange thing:
I wanted to restore the original backup and it worked. When I rebooted, the system asks me for the SIM card sim and then the system says:
"for the new start of the device you need to enter the pin"
The ony pin I ever used for the card and not knowingly for the device doesn't work.
Neitehr 0000 nor 1234 works. Which means I can't restore the nand backup.
Does anyone have an idea what this behaviour is and how to work around?
That is normal before doing a Nandroid u have to delete the pin, there exist a way around it deleting ur pin keys in trwp, its listed on this site somewhere
Bradl79 said:
That is normal before doing a Nandroid u have to delete the pin, there exist a way around it deleting ur pin keys in trwp, its listed on this site somewhere
Click to expand...
Click to collapse
found the thread. but unfortunately didn't find the corresponding workaround. can you remember where this was?
OK found it in the OnePlus 3 Forum.
This works:
HOW TO FIX
------------------------
Simply boot into TWRP and enter your PIN (if you've set one) to decrypt the stroage. If you don't have TWRP (for whatever reason) you can do so via ADB too but ONLY if you've connected your phone to your PC beforehand and also accepted it's fingerprint on the phone itself.
Delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find):
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Reboot the phone and (if you've set a PIN) enter it to decrypt the storage one more time. After that you can simply unlock your phone with a swipe.
Go into Settings > Security and set your preferred unlock method again, Android will ask you if you want to set a boot-time code too. Select whatever you want here, it's a nice security addition but can be annoying sometimes.
Enjoy your phone again!
ihobahobby said:
found the thread. but unfortunately didn't find the corresponding workaround. can you remember where this was?
OK found it in the OnePlus 3 Forum.
This works:
HOW TO FIX
------------------------
Simply boot into TWRP and enter your PIN (if you've set one) to decrypt the stroage. If you don't have TWRP (for whatever reason) you can do so via ADB too but ONLY if you've connected your phone to your PC beforehand and also accepted it's fingerprint on the phone itself.
Delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find):
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Reboot the phone and (if you've set a PIN) enter it to decrypt the storage one more time. After that you can simply unlock your phone with a swipe.
Go into Settings > Security and set your preferred unlock method again, Android will ask you if you want to set a boot-time code too. Select whatever you want here, it's a nice security addition but can be annoying sometimes.
Enjoy your phone again!
Click to expand...
Click to collapse
Thanks for sharing I wasn't aware and had to wipe my phone twice.
ihobahobby said:
found the thread. but unfortunately didn't find the corresponding workaround. can you remember where this was?
OK found it in the OnePlus 3 Forum.
This works:
HOW TO FIX
------------------------
Simply boot into TWRP and enter your PIN (if you've set one) to decrypt the stroage. If you don't have TWRP (for whatever reason) you can do so via ADB too but ONLY if you've connected your phone to your PC beforehand and also accepted it's fingerprint on the phone itself.
Delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find):
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Reboot the phone and (if you've set a PIN) enter it to decrypt the storage one more time. After that you can simply unlock your phone with a swipe.
Go into Settings > Security and set your preferred unlock method again, Android will ask you if you want to set a boot-time code too. Select whatever you want here, it's a nice security addition but can be annoying sometimes.
Enjoy your phone again!
Click to expand...
Click to collapse
Where in twrp do I have to enter the pincode ? After I choose to restore ? Is that all or do have to delete the files also when I have twrp ?
magnum73 said:
Where in twrp do I have to enter the pincode ? After I choose to restore ? Is that all or do have to delete the files also when I have twrp ?
Click to expand...
Click to collapse
Good question. I did also look for the pin entry, but haven't found. Was also not necessary maybe because I had switched off encyption earlier. I just deleted the namend files (which were for me only the locksetting files).
After that rebooted to system and everything works fine. Once you did that, better create a new backup without the fingerprint installed and you're safe next time.
Can u back it up and then do a restore from ur nandroid and restore files, I use multi fingerprints and have my gf on there also I hate resetting things up
I know this is what I need to do. I just can't find these files anywhere. Guess I have to start from scratch.
?
ihobahobby said:
found the thread. but unfortunately didn't find the corresponding workaround. can you remember where this was?
OK found it in the OnePlus 3 Forum.
This works:
HOW TO FIX
------------------------
Simply boot into TWRP and enter your PIN (if you've set one) to decrypt the stroage. If you don't have TWRP (for whatever reason) you can do so via ADB too but ONLY if you've connected your phone to your PC beforehand and also accepted it's fingerprint on the phone itself.
Delete (or rename) the following files inside /data/system (note that probably not all of them exist for you, simply delete those you can find):
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Reboot the phone and (if you've set a PIN) enter it to decrypt the storage one more time. After that you can simply unlock your phone with a swipe.
Go into Settings > Security and set your preferred unlock method again, Android will ask you if you want to set a boot-time code too. Select whatever you want here, it's a nice security addition but can be annoying sometimes.
Enjoy your phone again!
Click to expand...
Click to collapse
THANK YOU SO MUCH! I just got stuck between ROMs and used my nandroid backup but could not get past the lock screen.
So i was on Lineage OS on my op3 when i changed my pattern from 3x3 to 4x4, it asked me a question to ask for the pattern on boot so i enabled it.After some time i wanted to revert back to stock but after i flashed the rom again at boot a pattern window popped up but there was no option for 4x4 only 3x3 so i went back to Lineage and tried to change the pattern back to 3x3 (Even tried to remove it).But the pattern on boot did not change.I even flashed a different custom os(Ressurection Remix) in hope of changing the pattern but got no success.So my question is basically what else to do?
noob_siddhant said:
So i was on Lineage OS on my op3 when i changed my pattern from 3x3 to 4x4, it asked me a question to ask for the pattern on boot so i enabled it.After some time i wanted to revert back to stock but after i flashed the rom again at boot a pattern window popped up but there was no option for 4x4 only 3x3 so i went back to Lineage and tried to change the pattern back to 3x3 (Even tried to remove it).But the pattern on boot did not change.I even flashed a different custom os(Ressurection Remix) in hope of changing the pattern but got no success.So my question is basically what else to do?
Click to expand...
Click to collapse
You will need to go into twrps file manager and delete the lockscreen settings which are stored in data/system the files are gatekeeper.password.key , gatekeeper.pattern.key , locksettings.db , locksettings.db-shm , locksettings.db-wal once you have deleted each of those files just reboot and there will be no security login at all , if I've been helpful please leave a thumbs up on my post I truly appreciate it....
Xceeder said:
You will need to go into twrps file manager and delete the lockscreen settings which are stored in data/system the files are gatekeeper.password.key , gatekeeper.pattern.key , locksettings.db , locksettings.db-shm , locksettings.db-wal once you have deleted each of those files just reboot and there will be no security login at all , if I've been helpful please leave a thumbs up on my post I truly appreciate it....
Click to expand...
Click to collapse
I deleted all the files still nothing happened only the pattern after boot is gone
noob_siddhant said:
I deleted all the files still nothing happened only the pattern after boot is gone
Click to expand...
Click to collapse
It sounds like a feature that was on lineage OS are you sure you checked all the settings for a 4x4 grid as deleting the files I posted basically resets your login details so you can start again , I'm out of ideas buddy but I'll keep my eyes open for a similar issue and if I find the solution I'll msg you back as soon as possible ....
P.s you might of enabled a 4x4 grid by changing the LCD density or DPI ...
Hi there!
So, anybody who updated to android 10 knows about the annoying suggestions appearing in settings, which at the moment can't be dismissed or swiped away. Clearing the data of Settings Suggestions app can "fix" the issue momentarily but it'll come back again. Seems like the issue is about suggestions.xml file (/data/data/com.android.settings.intelligence/shared_prefs/suggestions.xml) not updating the boolean values correctly.
Examples:
Code:
<boolean name="com.android.settings/com.android.settings.wallpaper.StyleSuggestionActivity_is_dismissed" value="false" />
Code:
<boolean name="com.android.settings/com.android.settings.wallpaper.WallpaperSuggestionActivity_is_dismissed" value="false" />
The above lines must be changed from "false" to "true" in order for the suggestions to be dismissed but root is required to access and edit the suggestions.xml file i mentioned above. However, i managed to discover a rootless way of doing that by creating an adb data only backup of Settings Suggestions app. I used adb backup extractor to extract the backup file and edit suggestions.xml, restored the edited backup file via adb restore and the suggestions were gone. I've tried the method twice just to be sure and it's working.
I'm attaching the zip containing the edited backup file that you guys can restore using "adb restore data.ab" command.
NOTE: The restore process won't work on old adb drivers so make sure you use the latest platform tools before trying.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Sapper Morton said:
Could you also include a backup of this boolean?
Code:
<boolean name="com.google.android.gm/com.google.android.gm.setup.AccountSetupFinalGmailSuggestions_is_dismissed" value="true" />
Click to expand...
Click to collapse
There you go!
Can you please explain step by step how to do this? Do I have to download a certain app or connect my phone into a pc/laptop?
THEGEEK2015 said:
Can you please explain step by step how to do this? Do I have to download a certain app or connect my phone into a pc/laptop?
Click to expand...
Click to collapse
1 - Make sure you have the latest adb drivers.
2 - Extract the attached zip and put "data.ab" in the same folder were the adb executable is.
3 - Enable usb debugging in your device
4 - Connect the device and execute "adb restore data.ab" in adb
eltonb said:
1 - Make sure you have the latest adb drivers.
2 - Extract the attached zip and put "data.ab" in the same folder were the adb executable is.
3 - Enable usb debugging in your device
4 - Connect the device and execute "adb restore data.ab" in adb
Click to expand...
Click to collapse
I'm afraid that by replacing our data.ad with the one provided by you, will cost the loss of our app data.
Is there a toolkit to help us edit data.ad?
jolas said:
I'm afraid that by replacing our data.ad with the one provided by you, will cost the loss of our app data.
Is there a toolkit to help us edit data.ad?
Click to expand...
Click to collapse
As u can notice, the backup is a mere 2 kb file. It's a backup of only the Settings Suggestions app data, which is responsible for the suggestions in settings. However, if u are not comfortable using my backup, adb backup extractor is the tool you need....
Just wanna clarify if this needs root or not
Bro, Thanks a lot for your work and even big thanks for sharing! I have one more bug that I saw only a few people mentioning. I have sent it to Xiaomi also but there's no response. So here is the deal. I see the font and display size as 'big' on the lockscreen, when I have kept settings of both to 'small'. I have to go to settings and do some back n forth to get the uniform results. It turns back after I restart the device. Do you know or could you please find any solution to it? Thanks again!
@amnher Nope, only adb
@tejas1903 In my case, when i change the display size, certain elements like the power menu revert back to their original size after locking the phone (lock screen isn't affected though). I noticed it only happens when i use fingerprint unlock, which means getting rid of the fingerprints and keeping pin/password/pattern only as a method of unlocking fixes the issue in my case. I don't know if we are affected by the same bug, you can test it by removing the fingerprint and see for yourself. It's a pitty, when the first android 10 update came i thought the suggestion bug would be fixed by the 2nd update, yet here we are on the 4th one. Xiaomi really takes it's time in fixing the bugs however i still hope for a future bug free release....
eltonb said:
@amnher Nope, only adb
@tejas1903 In my case, when i change the display size, certain elements like the power menu revert back to their original size after locking the phone (lock screen isn't affected though). I noticed it only happens when i use fingerprint unlock, which means getting rid of the fingerprints and keeping pin/password/pattern only as a method of unlocking fixes the issue in my case. I don't know if we are affected by the same bug, you can test it by removing the fingerprint and see for yourself. It's a pitty, when the first android 10 update came i thought the suggestion bug would be fixed by the 2nd update, yet here we are on the 4th one. Xiaomi really takes it's time in fixing the bugs however i still hope for a future bug free release....
Click to expand...
Click to collapse
Okay will try.. and Thanks again!
New suggestion appeared today "Set Night Light Schedule".
OP updated.
eltonb said:
@amnher Nope, only adb
@tejas1903 In my case, when i change the display size, certain elements like the power menu revert back to their original size after locking the phone (lock screen isn't affected though). I noticed it only happens when i use fingerprint unlock, which means getting rid of the fingerprints and keeping pin/password/pattern only as a method of unlocking fixes the issue in my case. I don't know if we are affected by the same bug, you can test it by removing the fingerprint and see for yourself. It's a pitty, when the first android 10 update came i thought the suggestion bug would be fixed by the 2nd update, yet here we are on the 4th one. Xiaomi really takes it's time in fixing the bugs however i still hope for a future bug free release....
Click to expand...
Click to collapse
1. So if i disable adb it will stay?
2. And I suppose factory reset will revert?
amnher said:
1. So if i disable adb it will stay?
2. And I suppose factory reset will revert?
Click to expand...
Click to collapse
1. Yes
2. Yes
Can u make any guide, how to read your backup file? i dont like to restore your backup!
[GS] said:
Can u make any guide, how to read your backup file? i dont like to restore your backup!
Click to expand...
Click to collapse
ADB Backup Extractor is a tool that's used to pack and unpack adb backups.
thanks for your work, but new suggestion appears: on body detection
its like if you turn off one thing another opens
but thanks for your help
gamernayeem said:
thanks for your work, but new suggestion appears: on body detection
its like if you turn off one thing another opens
but thanks for your help
Click to expand...
Click to collapse
I'll keep the backup file updated with any new suggestion that appears until Xiaomi fixes it, if they do. I haven't encountered this one yet, which means i don't know the corresponding boolean to add to the suggestions.xml. If you manage to find it you can post it right here. If you can't, you can also post a data backup of your Settings Suggestions app using the following command (and i'll find it myself):
adb backup -f data.ab -noapk com.android.settings.intelligence
eltonb said:
I haven't encountered this one yet, which means i don't know the corresponding boolean to add to the suggestions.xml. If you manage to find it you can post it right here. If you can't, you can also post a data backup of your Settings Suggestions app using the following command (and i'll find it myself):
adb backup -f data.ab -noapk com.android.settings.intelligence
Click to expand...
Click to collapse
It should be this line:
Code:
<boolean name="com.google.android.gms/com.google.android.gms.trustagent.discovery.OnbodyPromotionActivity_is_dismissed" value="true" />
Btw, thank you very much, this is also a problem for Mi A2 since the android 10 update and your workaround worked great for me too.
birdflesh said:
It should be this line:
Code:
<boolean name="com.google.android.gms/com.google.android.gms.trustagent.discovery.OnbodyPromotionActivity_is_dismissed" value="true" />
Btw, thank you very much, this is also a problem for Mi A2 since the android 10 update and your workaround worked great for me too.
Click to expand...
Click to collapse
You're welcome! Mi A3, Mi A2, Mi A2 Lite and some other Nokia phones seem to have this issue. Thanks for posting the On Body Detection boolean, however since my "suggestions.xml" has no such line and i added it manually, i don't know if it'll work.... So, i'm attaching a test backup file which @gamernayeem or anyone who has the On Body Detection suggestion can try and see if it works. I'll update the OP then
Thanks man, i use your ideea to mi A2lite with andro Q, with same problem. I have a question: in the process of unpacking you use linux or just windows?
Hello. I'm on the last Android 11 Pixel Experience for my Redmi Note 8 Pro. I wanted to change my language to English so I went to the settings and I sawa this weird option "English one" I think, but the English was in zalgo text like E̶̮͗n̴̮̈́g̷̟̚l̵̳̂ȉ̶̙s̷̟͘h̵͈̎. I had no idea what this option is so I decided to try, and my phone screen turned black. I rebooted it and now it's stuck on the boot animation.
I have ADB shell access via both TWRP recovery and also during the booting animation. I run this during the animation:
Code:
C:\Users\Kotlinist>adb shell getprop persist.sys.locale
en-XA
The language is en-XA apparently. How can I go back to en-US?
If that helps I do have magisk installed but apparently I don't have root access for ADB turned on, because it gets stuck when I run 'adb shell' then 'su root', and there's still only the boot animation on my phone. All the solutions that I found required root in ADB. Can something be done? In TWRP perhaps?
Where are the language settings stored? Can I edit this file manually in TWRP?
Thanks in advance!
Alright, I manually edited /data/property/persistent_properties in TWRP to edit the en-XA into en-US. It wasn't enough, the phone booted but I couldn't unlock my screen stil (UI or whatever kept crashing every few seconds).
So I edited /data/system/users/0/settings_system.xml
inside there was this line:
Code:
<setting id="24885" name="system_locales" value="en-XA,pl-PL" package="android" defaultValue="en-XA,pl-PL" defaultSysSet="true" preserve_in_restore="true" />
I edited the two 'en-XA' to 'en-US' here. Rebooted. Phone's working. Hopefully this helps someone!
en-XA,sounds like a very alien-y language.
Definitely same issue on the latest Havoc-OS for my OnePlus 6t. Dude you saved my ass man ! Your exploring and sharing is much appreciated.
Thanks you a lot!