Related
Intro
This is a guide for people who want to make some modifications to config files, or other files, on System partition but do not want to root their phone or install custom recovery in order to keep OTAs and some apps, which don't play nicely with rooted phones, working. Examples of those config mods could be changing DPI or changing volume levels etc, which you would only do once and forget about it.
While root allows you to do those kinds of changes from within android, this methods would require a PC.
If you are familiar with temporary booting into a custom recovery, skip to step 5.
The usual i am not responsible for any of your actions / bricked phones disclaimer applies.
Prerequisites
- A working adb / fastboot environment. Please use Android SDK, if you installed your adb and fastboot using other tools, things might not work, so please just install SDK, install Google USB Driver from SDK manager, install Platform-Tools from SDK manager (should be installed by default) and then add your sdk platform-tools path to your PATH environment variable to have it available in cmd in every path.
- Unlocked bootloader
- TWRP image for you phone (.img) https://twrp.me/devices/huaweinexus6p.html
Follow the [GUIDE] Unlock/Root/Flash for Nexus 6P for that.
Instructions
Here is an example of modifying DPI. I prefer build.prop method of modifying DPI because using the adb wm density command usually caused some issues for me, but modifying via build.prop didn't.
1 - With you phone ON, connect it to the PC and make sure adb is working by running
Code:
adb devices
and making sure that device is listed
2 - Reboot into bootloader. and make sure fastboot is good to go too. Run commands one at a time:
Code:
adb reboot bootloader
fastboot devices
3 - Place your TWRP image file in some easily accessible folder, for the sake of this example i will use C:\Mods.
4 - Temporary boot into TWRP (we are not flashing it here at all).
Code:
fastboot boot c:\Mods\twrp-2.8.7.0-angler.img
Here is where things may not work. If you don't see your phone boot into TWRP then either your adb / fastboot environment not setup correctly (installed via a tool instead of SDK) or your img file is corrupt.
One thing that works for me when TWRP refuses to boot is to restart cmd and issue the command again this closes and reopens adb/fastboot daemon.
5 - Once TWRP is up on your phone it may display a warning saying "TWRP has detected an unmounted system partition". Swipe to allow modifications at the bottom. This screen may not come up at all.
6 - Go to Mount >>> Tick System >>> Make sure "Only Mount System Read Only" is unticked >>> Press Back button
7 - Back on your PC check if your device is listed
Code:
adb devices
8 - Pull the file you need to modify from system partition to your PC. Please note the direction of the slashes:
Code:
adb pull /system/build.prop c:/Mods
9 - Now you should see build.prop in your c:\Mods folder. Use Notepad++ or something like that to edit the file. Find the line with lcd_density= and change it's value to whatever you need and save the file.
10 - Push the file back to your phone:
Code:
adb push c:/Mods/build.prop /system
11 - Reboot
Code:
adb reboot
12 - Profit.
Hope this will help anyone who is looking to do some mods without installing custom recovery and rooting your phone.
Cheers.
Would this work for adding the tethering bypass line in the build prop?
Yes it will. What's the line again I was looking for it the other day and couldn't find it...
Works are per OP's original post, tested and boosted the headphone volume without a problem.
Headphone path is /system/etc/mixer_paths.xml
So as per OP's example to pull: adb pull /system/etc/mixer_paths.xml c:/Mods
push: adb push c:/Mods/mixer_paths.xml /system/etc
I'm using the OP's "Mods" folder to demonstrate the file path but this may vary on your PC.
Can I use this to push SuperSU / etc to my device without having to permanently flash TWRP?
skrowl said:
Can I use this to push SuperSU / etc to my device without having to permanently flash TWRP?
Click to expand...
Click to collapse
You can certainly push the files to system partition and they will retain there after reboot. So if you know which files have to be pushed for SuperSU then give that a go. It shouldn't break anything.
I haven't tried pushing SuperSU files to system partition before so I can't guarantee that OTAs will work after this. The only way to find out is to try it i guess...
Can you run nandroids?
not sure if it's allowed or not.. but with this can i push hosts file onto the phone as well for ad-blocking...?????
I will say thanks now and try it later. These are the type of tweaks I would like to make to my phone. Do you know if changing the DPI cause any stock applications to show up broken like they do on the Samsung phones?
NCguy said:
Can you run nandroids?
Click to expand...
Click to collapse
Im not sure what you mean?
rohit25 said:
not sure if it's allowed or not.. but with this can i push hosts file onto the phone as well for ad-blocking...?????
Click to expand...
Click to collapse
If it's on the system partition then I yes you can.
locolbd said:
I will say thanks now and try it later. These are the type of tweaks I would like to make to my phone. Do you know if changing the DPI cause any stock applications to show up broken like they do on the Samsung phones?
Click to expand...
Click to collapse
I've never had a problem with changing DPI using this method on a nexus phone if that helps.
denk said:
Im not sure what you mean?
Click to expand...
Click to collapse
Can you run nandroids backups from TWRP by just booting into it?
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
locolbd said:
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
Click to expand...
Click to collapse
I got this too when I flashed MOAB via adb sideload. I'm just wondering if the same warning appears with the adb push method. Also, the file's permissions don't need to be set after adb push?
My main concern is if Android Pay still works with the red triangle warning. Anyone?
FYI Flashing back to stock is no issue for me.
NCguy said:
Can you run nandroids backups from TWRP by just booting into it?
Click to expand...
Click to collapse
I think if you get the latest TWRP which supports decryption of data partition (where all your stuff is) you should be able to back it up.
Edit: backup works on nexus 5 with temporary TWRP boot. Sorry I'm still waiting for my 6p to arrive.
locolbd said:
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
Click to expand...
Click to collapse
Thanks for trying it out! Sometimes OTA notifications take a little while to come up after reboot. But based on the warning Im afraid that they might be disabled now. It looks like it runs some sort of a check on the system partition to verify its legitimacy. So modifying files would be fine on it using this method but looks like adding them won't work.
TWRP just released their recovery with decryption support so you can just follow the standard procedure or just temporary booting into TWRP and rooting from there which works as well.
denk said:
I think if you get the latest TWRP which supports decryption of data partition (where all your stuff is) you should be able to back it up.
Edit: backup works on nexus 5 with temporary TWRP boot. Sorry I'm still waiting for my 6p to arrive.
Click to expand...
Click to collapse
On your Nexus5 I assume you are also unrooted? And have you tried a Nandroid restore, booted TWRP, no root?
NCguy said:
On your Nexus5 I assume you are also unrooted? And have you tried a Nandroid restore, booted TWRP, no root?
Click to expand...
Click to collapse
Just ran a restore to test it for you. Works fine as well.
My N5 is unrooted.
.
denk said:
Just ran a restore to test it for you. Works fine as well.
My N5 is unrooted.
.
Click to expand...
Click to collapse
Thanks a lot for that. I didn't unlock the bootloader. Ugh. Time to start over. To me nandroids alone make it worth the effort.
OFFICAL TWRP RELEASED, this thread is no longer active. 3-30-2018
https://twrp.me/motorola/motorolamotox4.html
---
UNOFFICIAL BUILDS -- USE AT YOUR OWN RISK AND KNOW HOW TO GET YOURSELF OUT OF TROUBLE IF IT ARISES. I ASSUME NO RESPONSIBILITY FOR YOUR BROKEN THINGS.
UPDATED 01-11-2018
There are now 7.1 based and 8.0 based builds. Obviously, be careful to select the proper download. While I don't think flashing/booting the wrong one would permanently brick the device, let's not find out
For now I will not be attempting to make data decryption work. It is REQUIRED that you unencrypt your device by formatting userdata, so back up your stuff first.
IMPORTANT NOTES: TWRP for OREO is a bit of a pain as it currently requires manually editing your fstab. I have tried to automate this process, but it breaks stuff. So just be aware before you begin that it is a rather time consuming process.
If you make any change to your boot partition after flashing SuperSU, you will need to reflash it or you will get a bootloop.
8.0 OREO TWRP INSTALLATION:
OREO SEEMS VERY FINICKY AND DOES NOT LIKE CHANGES TO ITS FILESYSTEM -- BE PREPARED TO REFLASH STOCK.
0. FLASH OREO FACTORY IMAGE (may work otherwise, but we should be starting from fresh stock here)
1. Download FASTBOOT BOOTABLE TWRP for 8.0/OREO below
2. Download SuperSU 2.82 SR5 below
3. Move SuperSU to external SD or USB OTG
4. From bootloader, fasboot BOOT TWRP
5. Flash SuperSU (note: do not format /data now... not necessary and will cause errors on boot)
6. Reboot system
7. With any root file editor/text editor (Amaze, Total Commander, etc) open /system/vendor/etc/fstab.qcom as a text file for editing.
8. At the end of the /data partition entry, delete "fileencryption=ice" and replace it with "encryptable=footer".
9. Save fstab.qcom (and make sure it is actually saved properly!)
10. Reboot to bootloader and fasboot BOOT TWRP
11. Go to Wipe, hit the FORMAT DATA button, and type "yes" to format /data. This will erase your data, obviously:silly:
12. Reboot system (should now be unencrypted, verify in Settings>Security or by booting TWRP and checking /data with File Manager.
If you later choose to flash TWRP (not the bootable we used here!), you may need to flash SuperSU again to avoid bootloops.
7.1.1 NOUGAT TWRP INSTALLATION:
1. Download current TWRP for 7.1.1 build below
2. Download SuperSU 2.85 SR5 (https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
3. Move SuperSU to your external Micro SD card.
4. Fastboot flash the TWRP image.
5. Reboot to TWRP.
6. FORMAT data (not wipe...use the "FORMAT DATA" button and type "yes". OBVIOUSLY THIS WILL ERASE YOUR DATA)
7. Install SuperSU 2.85 SR5
8. Reboot to system (it WILL bootloop a couple times...don't panic!) and confirm that device is unencrypted by checking that SETTINGS>SECURITY>ENCRYPTION now prompts "encrypt" (don't do it).
DOWNLOADS:
TWRP FOR 7.1.1 (Nougat) DOWNLOAD: https://drive.google.com/open?id=1Et-AQgCNx7WDAwzihlI51euUa2ixKHEP
TWRP FOR 8.0 (Oreo) DOWNLOAD: https://drive.google.com/open?id=1WcVS_3rloF7jxPulj_jKxfsp3zy5pB5N
FASTBOOT BOOTABLE TWRP IMAGE (OREO BASED): https://drive.google.com/open?id=12ClviqtEjtflB63UQ1CZQNKEqkprBO0u **For temporary TWRP boot using "fastboot boot". Do not flash or you will be stuck in recovery!**
DEVICE TREE: https://github.com/mightysween/android_device_motorola_payton (NEEDS TO BE UPDATED WITH OREO BRANCH)
changelog:
BETA4
-reverted to 3.2.0 for current build (release candidate rebased to 3.2.1).
-fixed "format data" button
-finalized fstab for OTG/SD/INTERNAL mounting
-target is now UNENCRYPTED devices only (/data decrypt will not be fixed)
BETA3
-Rebased to TWRP 3.2.1
-USB OTG working
-all partitions mounting correctly
-considered working except for decrypt and MTP/ADB
BETA2
-fixed internal storage mount
BETA1
- updated source to TWRP 3.2.0
ALPHA3
- Fixed USB mounting (adb/mtp still nonfunctional) BROKEN IN BETA1
ALPHA2
- SD Card fixed
ALPHA1
- /system is now properly mounted.
- now plays nice with our working root method.
- ramdisk is patched to prevent first boot encryption once /data is decrypted (now requires flashable ZIP)
NOT WORKING:
adb/mtp/sideload
/data decryption (abandoned -- /data access requires unencryption)
CREDITS: @kraatus90 for kernel fix, @Chainfire for SuperSU, @jcadduono for no-verity-opt-encrypt scripts.
---
Thanks so much for all your work!
hi,
you said this is really unstable and could brick the device easily. however, you seem to be testing and experimenting with your device a lot, so i'd like to ask if you have any particual unbrick method that you use when something goes wrong.. like, a via fastboot flashable image or something simmilar...?
thanks for your work!
Thanks for you work. If you have any unbrick methods pls tell.appreciated your work ?
I am not going to provide step by step "unbrick" methods, because until the partitioning is properly set up, TWRP has potential access to things that can not be fixed.
Again, this is still highly experimental.
All that said, my entire process to protect any device remains the same: Have a backup for every partition you will be testing, make as few changes as possible at a time, test boot images before flashing (fastboot boot), and test restore methods frequently (flashing back to stock or backups), and don't do anything unless you are highly certain of the outcome.
By those standards, there is nothing to gain by installing TWRP right now, as its basic function (install/backup/restore) is not set up yet.
Found the BoardConfig flag to enable FBE (TW_INCLUDE_CRYPTO_FBE := true) but do not have the lib it is dependent on (libe4crypt) and I don't see it anywhere yet...
For reference (not sure this is most current, but it demonstrates the process)
https://github.com/nijel8/TWRP/commit/bd7492de28963b7e74e8e5d3f17ec9a5a287d9c3
I have confirmed that FBE support is present in the source, dependent on this missing module... so need to figure out where/how to enable it.
It is possible that this entire process is specific to only certain devices (i.e. Pixel, Nexus). If this is the case, we may be stuck at this point for awhile.
Obvious workaround is to not be encrypted to begin with -- but that isn't a "solution".
mightysween said:
It is possible that this entire process is specific to only certain devices (i.e. Pixel, Nexus). If this is the case, we may be stuck at this point for awhile.
Click to expand...
Click to collapse
This appears to be the case, unfortunately. Seems that the TWRP FBE support was built specifically for the Google implementation of FBE which was merged into kernel sources for Nexus and Pixel. Not even using the qseecomd I assumed it was... will remove on next build.
Info on FBE:
https://source.android.com/security/encryption/file-based
Will be testing options to disable forced encryption, and if necessary dm-verity...
Anyone who wants to dig through kernel for related flags and props, it would be greatly appreciated!
Hey, where did the big "format data" button go in TWRP? Is that optional on compile... can't find a flag for it...
Making good progress this morning.
Seem to have a build with properly decrypted /system, and working SD Card. I also have patched the boot.img to disable forced encryption on the first boot. But now, I can not find a safe way to fully format (not "wipe") the /data partition. As mentioned in the previous post, the "FORMAT DATA" button is missing. The fastboot command "fastboot format userdata" returns an error that it does not support RAW format.
Need to figure out why this is happening... and once I do, I believe I can reformat /data without encryption and then will have an almost fully working TWRP build. Obviously, the ideal solution would be to have TWRP work out of the gate with an encrypted /data, but until then this is going to be our best option.
Will post an updated test build in the OP soon.... needs further testing before I would recommend non-expert users to try it.
Getting very close now!
UPDATE: ADDED NEW BUILD TO OP
---
Also, just occurred to me that the ramdisk will need to be patched every time, so now that I have SD card support will be testing some of the existing flashable ZIPs out there that are designed specificially to prevent first-boot encryption and/or disable dm-verity.
---
mightysween said:
Hey, where did the big "format data" button go in TWRP? Is that optional on compile... can't find a flag for it...
Click to expand...
Click to collapse
This is really the only hold up... I changed the partition from 'Advanced Wipe", but as expected, it was still encrypted on boot as it doesn't actually format the footer where encryption is stored. I can't figure out where that darn "FORMAT DATA" button ran off to, and that is exactly what we need here.
mightysween said:
This is really the only hold up... I changed the partition from 'Advanced Wipe", but as expected, it was still encrypted on boot as it doesn't actually format the footer where encryption is stored. I can't figure out where that darn "FORMAT DATA" button ran off to, and that is exactly what we need here.
Click to expand...
Click to collapse
I don't know how to help except to say that using TWRP 3.1.0-MOD_1 with my XT1254 (DROID Turbo), when you go to wipe it has two buttons --- one on the left for Advanced Wipe and Format Data on the right.
johnjingle said:
I don't know how to help except to say that using TWRP 3.1.0-MOD_1 with my XT1254 (DROID Turbo), when you go to wipe it has two buttons --- one on the left for Advanced Wipe and Format Data on the right.
Click to expand...
Click to collapse
I have 3.1.1-0 (same version I am building here) on several other devices, and the button is there. It has to be triggered by something during compile, but I can't figure it out. Driving me nuts
Looking through TWRP source, and can find actions for every other button (wipe, backup, restore, install, etc) but not for format. Hmm.
I posted over on an old but semi-active TWRP flags thread, maybe someone will have some insight.
Wondering if I make a stock boot image without the encryption tag in fstab, and then wipe data and reboot... then flash my image. That may make it so the data partition is never encrypted in the first place and allow TWRP to work.
But that is an ugly, non-user friendly fix. Why can't we just format /data?
---
Final update for today... this seems to be a compile issue, which is a good thing. I tried to manually decrypt /data from the TWRP command line, and got this:
No crypto support was compiled into this build.
Click to expand...
Click to collapse
So, I must be missing something in boardconfig still... and maybe need to set up a small proprietary vendor folder with the necessary libs
mightysween said:
Final update for today... this seems to be a compile issue, which is a good thing. I tried to manually decrypt /data from the TWRP command line, and got this:
So, I must be missing something in boardconfig still... and maybe need to set up a small proprietary vendor folder with the necessary libs
Click to expand...
Click to collapse
Thanks for doing all of this! I wish I had the time and knowledge to help.
Had a few PM's checking on TWRP status, so an update.
The good news is that the X4 is using Qualcomm based decryption for /data... the bad news is that most if it seems to be closed source. This will take some time for me to figure out, but I have already made some progress by sifting through logs.
Right now, I am trying to find a device with similar decrypt scheme to have some more guidance on the process.
mightysween said:
Had a few PM's checking on TWRP status, so an update.
The good news is that the X4 is using Qualcomm based decryption for /data... the bad news is that most if it seems to be closed source. This will take some time for me to figure out, but I have already made some progress by sifting through logs.
Right now, I am trying to find a device with similar decrypt scheme to have some more guidance on the process.
Click to expand...
Click to collapse
dont know all about these things but maybe xiaomi mi a1 twrp can help as it is also using same a/b partition. and twrp is already there for it
vivek638 said:
dont know all about these things but maybe xiaomi mi a1 twrp can help as it is also using same a/b partition. and twrp is already there for it
Click to expand...
Click to collapse
Thanks, the Mi A1 is one of the devices I have been comparing to, and has been quite helpful.
mightysween said:
Thanks, the Mi A1 is one of the devices I have been comparing to, and has been quite helpful.
Click to expand...
Click to collapse
Keep searching. wish i could have helped but dont know anything about compiling n all..
I'm not much of a programmer, but I can look through the files. Is there anything in particular we're searching for?
I'm curious whether every miatoll device has the same situation, not just me. I can use any rom. But I had to format data each time I try to flash a new rom. Basically, I can't use the device in decrypted mode. Or can we ?
Glad you fixed your problem. You can't edit system or vendor partition because of the implementation of dynamic partitions in Android 10. Read more about dynamic partitions and you will understand.
LoadOP2 said:
Glad you fixed your problem. You can't edit system or vendor partition because of the implementation of dynamic partitions in Android 10. Read more about dynamic partitions and you will understand.
Click to expand...
Click to collapse
Ya, that's what I was thinking. But I successfully managed to modify files under system too.
I simply rooted RR with magisk patched boot method. Then used Mixplorer to remove some system files & vendor files, & I successfully did it.
But, currently this thread topic is my problem (right now) . I'm solving slowly problem by problem, until I'll get desired results.
Have to be rooted and give your file manager su permissions, load Magisk app, find the log and see where the .Magisk file is
Since Magisk app v8.0.0 the advanced settings/install options for dm-verity and forced encryption won't be available on most modern devices (see Advanced Settings/Install Options for details). The tools are still there and may be accessed through various means.
Keeping dm-verity and forced encryption:
If your device supports it, the app will auto-detect if your device is encrypted and if it’s recommended to keep dm-verity enabled and the “Preserve forced encryption” and “Preserve dm-verity” will then be enabled by default. If these options aren’t enabled, you can keep dm-verity and forced encryption by checking the options for this before installing a new version of Magisk through the app.
If you install through recovery (either for the first time or as an update) run one or both of the following commands in a terminal emulator or in your recovery's terminal before installing:
echo KEEPVERITY=true>>/cache/.magisk
echo KEEPFORCEENCRYPT=true>>/cache/.magisk
If you can't access /data (TWRP can't decrypt, etc) you can instead use either /data/.magisk or/system/.magisk, but please note that using /system/.magisk isn't systemless.
Some devices need to keep dm-verity enabled to work properly. One example is some Huawei devices that might otherwise experience weird behaviour or bootloops.
Disabling dm-verity and forced encryption:
If you on the other hand want to disable either dm-verity or forced encryption, you can go about it the same way as described above. If you're using the .magisk file method, just change KEEPVERITY and/or KEEPFORCEENCRYPT in the commands to false:
echo KEEPVERITY=false>>/data/.magisk
echo KEEPFORCEENCRYPT=false>>/data/.magisk
If you can't access /data (TWRP can't decrypt, etc) you can instead use either /cache/.magisk or/system/.magisk, but please note that using /system/.magisk isn't systemless.
If disabling verity through Magisk doesn't help, you can try the following command (provided that your device has a vbmeta.img):
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
think its from here: https://forum.hovatek.com/thread-32719.html
or
https://www.reddit.com/r/Magisk/comments/mvk9j9
*cough* Copy-pasta... *cough*
When citing a text it's customary to also give the source.
fixed my bad
mr_reaper said:
fixed my bad
Click to expand...
Click to collapse
He, he...
I guess you got it from that Reddit link, but look closer at the bottom of that post for the actual source (hint: look even closer at the URL).
Computer Tower: $1500
Monitor: $500
Mouse and Keyboard: $50
Internet Service: $50/month
Accidentally plagiarize one of the mods... Priceless.
LOL
oh ****, LMFAOOOO. my bad was just trying to help *shurgs*
Essentially copy/paste from the official TWRP for redfin thread, except I've made my own unofficial build for the Pixel 4a5G that in my own testing appears to be on feature parity with the official build for the Pixel 5! There are reports of the Pixel 5 build not working on devices with Android 12 and a PIN set at this time, so I advise against using this build if you've upgraded to Android 12 on your Pixel 4a5G and require having a PIN for your day to day.
I've decided I might as well try to maintain the device since no one else is doing so yet. I've pushed the trees I've modified to GitHub so y'all can keep track and maybe help out before I submit them for official status.
device/google/bramble: https://github.com/JoshuaDoes/twrp_device_google_bramble
device/google/redbull: https://github.com/JoshuaDoes/twrp_device_google_redbull
You can find the latest unofficial test build here: twrp-3.6.0_11-0.1-bramble.img
Boot it with `fastboot boot twrp-3.6.0_11-0.x-bramble.img`, decrypt your data if necessary, then install it permanently by navigating to `Advanced -> Flash Current TWRP`. Test by navigating to `Reboot -> Recovery` and you should reboot back into TWRP!
Changelog
11-0.1 (1/16/2022):
- Fix missing libion dependency, which appears to allow booting and installing TWRP if A12 is installed
11-0 (1/13/2022):
- Sync bramble with patches from redfin
You can find the historical builds here (but please don't use them): https://files.joshuadoes.com/TWRP/twrp-11/bramble/
Thank you it's so cool but update my pixel 4a 5g to A12
Stay an update too for it
I've ran into a `ErrorCode::kError` issue trying to install the latest official LineageOS 18.1 ZIP, but everything else appears to be working!
fastboot boot twrp-3.6.0_11-0-bramble.img
It sees partitions and super.
I hit compresson option and confirm/change name and it's backing up. adb appears to work (didnt check too into it). Just booted it and see if I can make a backup--AND I CAN. Good work @JoshuaDoes ! Good good job!
smokejumper76 said:
fastboot boot twrp-3.6.0_11-0-bramble.img
It sees partitions and super.
I hit compresson option and conirm/change name and it's backing up. adb appears to work (didnt check too into it). Just booted it and see if I can make a backup--AND I CAN. Good work @JoshuaDoes ! Good good job!
Click to expand...
Click to collapse
I did a successful data restore earlier today, just remember to disable your PIN first and then reboot immediately after the first boot following the restore
what if I just have no pin/password. just swipe to unlock? i did see a message in backup log 'sucessfully decrypt with default password'.
smokejumper76 said:
what if I just have no pin/password. just swipe to unlock? i did see a message in backup log 'sucessfully decrypt with default password'.
Click to expand...
Click to collapse
You're in the best case scenario then, just make sure you always disable PIN before restoring a backup so long as it gives you the warning to do so (I get the warning because I have a PIN, but you should just be free to restore as you please)
awesome. Only things I notice not there (and in no way complaining as its a WIP) is encryption option, and date seems to be stuck on 1970 and time way off despite changing time zone. But that's minor right now. The fact you got this going is no small feat. I am so glad I got a 4a5g (5/5a would have been fine too) and not a 6. You should put a donate link so we can buy you some coffee or weed or something, lol. Again great job. Feel free to hit me up if you need me to destroy my phone for you (testng). I got a dd backup, and now twrp backup so between all of that and the alfabet of partitions I should be able to restore from just about anything short of EDL crap out and I'm sure if that's not resolvable by now, it will only be a matter of time.
smokejumper76 said:
awesome. Only things I notice not there (and in no way complaining as its a WIP) is encryption option, and date seems to be stuck on 1970 and time way off despite changing time zone. But that's minor right now. The fact you got this going is no small feat. I am so glad I got a 4a5g (5/5a would have been fine too) and not a 6. You should put a donate link so we can buy you some coffee or weed or something, lol. Again great job. Feel free to hit me up if you need me to destroy my phone for you (testng). I got a dd backup, and now twrp backup so between all of that and the alfabet of partitions I should be able to restore from just about anything short of EDL crap out and I'm sure if that's not resolvable by now, it will only be a matter of time.
Click to expand...
Click to collapse
Encrypting backups? I didn't realize that was missing so I'll look into it too, but yeah the date is stuck which screws with file and backup times and I def need to fix that. XDA forbids me from putting a donation link in a post, however if you go to my profile and expand the info details about me it lists my PayPal email there and I'd super appreciate it! Because lemme tell ya, it took energy drinks and some good highs to do most of my Android work and thankfully this TWRP build only took me a few hours to tear into lmao. If you got a Discord I'm most active there as well as the Pixel 4a5G/5 Telegram (I can get a link to all if you've got them), and having extra testers for some of what I wanna do would be phenomenal as well! And we're Qualcomm, there's a flash tool out there somewhere for the worst of board states
Sorry for the wall of text lmao, I appreciate the kind words for sure and I'm likely gonna try maintaining this device officially for TWRP too
Hi ! Thank you for all your work. I was surprised when buying my Pixel 4a 5g when it came out that there was no Twrp because of Android 11. But coming from Xiaomi and Oneplus there were unofficial ones for Android 11 and 12.
When you can update it for A12 I have noob question. After flash the Twrp and boot it (with no pin) I can make a backup of all my Pixel. Copy it on my Pc and them do format data ? Or not necessary ? If I do format it them boot the Pixel and when it start check dev options, adb and reboot to Twrp Root (Magisk) and restore my data ? If not how to make a backup of my data.
Thanks
JoshuaDoes said:
Essentially copy/paste from the official TWRP for redfin thread, except I've made my own unofficial build for the Pixel 4a5G that in my own testing appears to be on feature parity with the official build for the Pixel 5! There are reports of the Pixel 5 build not working on devices with Android 12 and a PIN set at this time, so I advise against using this build if you've upgraded to Android 12 on your Pixel 4a5G and require having a PIN for your day to day.
I've decided I might as well try to maintain the device since no one else is doing so yet. I've pushed the trees I've modified to GitHub so y'all can keep track and maybe help out before I submit them for official status.
device/google/bramble: https://github.com/JoshuaDoes/twrp_device_google_bramble
device/google/redbull: https://github.com/JoshuaDoes/twrp_device_google_redbull
You can find the latest unofficial test build here: twrp-3.6.0_11-0.1-bramble.img
Boot it with `fastboot boot twrp-3.6.0_11-0.x-bramble.img`, decrypt your data if necessary, then install it permanently by navigating to `Advanced -> Flash Current TWRP`. Test by navigating to `Reboot -> Recovery` and you should reboot back into TWRP!
Changelog
11-0.1 (1/16/2022):
- Fix missing libion dependency, which appears to allow booting and installing TWRP if A12 is installed
11-0 (1/13/2022):
- Sync bramble with patches from redfin
You can find the historical builds here (but please don't use them): https://files.joshuadoes.com/TWRP/twrp-11/bramble/
Click to expand...
Click to collapse
Hello. Link is for ver. 0. Ver 0.1 returns 403 Forbidden. Can you please fix it?
Been waiting so long for this, thanks a bunch, i'm running lineageos 18.1 so i hope it will work (probably disable automatic updates flashing ?).
N34S said:
Hello. Link is for ver. 0. Ver 0.1 returns 403 Forbidden. Can you please fix it?
Click to expand...
Click to collapse
I fixed the link for v0.1!
J0kker said:
Been waiting so long for this, thanks a bunch, i'm running lineageos 18.1 so i hope it will work (probably disable automatic updates flashing ?).
Click to expand...
Click to collapse
Automatic OTAs will replace TWRP, so disable automatic OTAs and download them with the Updater app whenever you get a notification, then install using TWRP (/data/lineageos_updates) and check "Install TWRP after flashing" before swiping to install (or go to Advanced -> Install Current TWRP before rebooting). Easy as that!
But I may make a Magisk module to handle all this since Magisk has a survival script that works. It'd be a oneshot service that caches the latest copy of TWRP and installs it each boot, so you'd only have to deal with one update cycle that has Lineage Recovery installed.
Just wondering, i have a game that won't run when rooted (even with magisk hide), i somewhat managed to have lineageos rooted with magisk in slot b, and in slot a magisk installed but no root, so when i want to run the game i switch to slot A from twrp, now i have an update notification, i downloaded it, if i boot to twrp, select slot a, so that it will install update to slot b (rooted), that way it should keep my slot a unrooted, able to play my game right ?
New to this slot a/b i read a lot but still not sure about everything.
Anyway, thanks again for your work, and your answers, i missed twrp so much coming from oneplus 5 =)
Hi just installed the boot twrp img, worked great! Thank you for your great work. If you were to develop a module through Magisk would that enable the twrp to stick as a recovery and not lose root?
I wanted to say thank you again for building this.
Also, does anyone know if there is a way to exclude a folder (or folders) from TWRP backups? I had this great idea to go from mp3 to flac music when I got 128gb storage on my first pixel and...well...it's too big. Thanks again!
Hello,
I am trying to recover some data off of my 4a 5g with a broken display. It seems like my partitions are not mounting correctly.
This is what etc/fstab looks like:
Code:
/dev/block/dm-0 /system_root ext4 ro 0 0
/dev/block/dm-3 /system_ext ext4 ro 0 0
/dev/block/dm-4 /vendor ext4 ro 0 0
/dev/block/dm-2 /product ext4 ro 0 0
/dev/block/sda15 /metadata ext4 rw 0 0
/dev/block/sda19 /data f2fs rw 0 0
/auto0 vfat rw 0 0
/dev/block/sda2 /persist ext4 rw 0 0
This is what I get when trying to mount partitions:
Code:
bramble:/ # mount -a -v -t f2fs
try '/dev/block/sda19' type 'f2fs' on '/data'
mount: '/dev/block/sda19'->'/data': Invalid argument
My question is, am I doing something wrong here? I suspect data is not decrypted but I have no working display to verify whether I am actually entering the password when booting recovery. Also can anyone please walk me through how to properly enter the password using a USB keyboard
Sorry guys , got a new 4a5g and did a fresh Feb 2022 factory install both slots and this 11.0.1 will not boot. Fastboot tools are latest along with drivers and this recovery failed to flash or boot. Fastboot sent the file however in all cases failed to write into recovery partition. Tried all of the builds just in case. Never could get past writing to the recovery partition
Hi if you can access fastboot try the the android flash tool, I had the same issue and that worked for me