Database Info

inception: Hands-off auto-configuration tools for android

Inception is a set of tools for auto configuring android devices. You can do the following:
Include any apps to be (pre)installed
Remove any stock apps
Root the device
Install busybox
Configure Wifi networks
Generate all device settings
Patch APKs
Replace Kernel, and/or ramdisk data in both boot and recovery imgs
Place your adb keys, configure USB debugging
You specify all this in a JSON config file. And then inception creates the following depending on what you specify in your configuration:
OTA Update Package that applies all your changes once installed
Modified recovery img
Modified boot img
Cache img that bundles the update package and instructs android to install it once in recovery
Odin flashable tar.md5
With the right configuration, you can also generate auto-root update packages, or update packages that just install busybox, or both.
Code:
incept autoroot --code samsung.degaswifi
or
Code:
incept busybox --code samsung.degaswifi
Or out of a stock recovery img:
Code:
incept autoroot --code inception.device --recovery /path/to/recovery.img
Inception does not create a full system image or compile roms. It bundles only the required changes in an Android update package and generates an update script which applies those changes. This results in update packages that are substantially smaller than when flashing a whole ROM.
As an output example, I posted this Samsung SM-T230 auto-root package, and another Samsung SM-T113 auto-root package that were both generated using inception.
Full source code for inception and installation instructions are available here: https://github.com/tgalal/inception
Please post feedback/questions/problems here
XDA:DevDB Information
inception, Tool/Utility for all devices (see above for details)
Contributors
tgalal
Source Code: https://github.com/tgalal/inception
Version Information
Status: Testing
Created 2015-06-11
Last Updated 2015-06-11

i have a file %USERPROFILE%\.android\adbkey.pub in windows, how to incept into /data/misc/adb/adb_keys with odin? (Samsung Galaxy Tab 3 Lite SM-T113)
where exactly place the key? is this a JSON config file?
Code:
{
"update": {
"adb": {
"__make__": true,
"keys": [
"PUBLIC_KEY_DATA_1",
"PUBLIC_KEY_DATA_2"
]
}
}
}
edit: found the README.md but it is a lot of information. can you please post minimal steps how to create a tar.md5 from adbkey.pub?
1. install linux
2. add packages (requirements)
3. download and install inception (at this point it fails with exit 1 older version of dulwich)
4. incept bootstrap?
5. pass the adbkey.pup to json?
6. incept make?
7. generate odin package??
8. ... ?

[TWRP][ONEPLUS X] Update for encryption

Hello everyone !
I am new to the world of Android (former Windows Phone user) and begin to explore the ins and outs of this marvelous device
I got a OnePlus X recently and decided to root it.
I Installed TWRP for recovery 2.8.7.0 [1] and installed SuperSU and it worked like a charm.
I then crypted the device and began to have fun w/ it !
Now, the new version of OxygenOS (2.1.3 with SD Card support!) is out and I would like to upgrade my phone. But My instance of TWRP does not support encryption[2]. TWRP (j50036 indeed) released a patch for it but it is not yet implemented for OnePlus X obviously.
Code:
~ # twrp decrypt 002932839239230
Attempting to decrypt data partition via command line.
E:No crypto support was compiled into this build.
I tried to install it through ADB side load without success, and via TWRP without data.
Code:
~ # twrp install /external_sd/uc.zip
E:Unable to mount '/data'
command is: 'decrypt' and there is no value
E:No password provided.
Done processing script file
Can someone explain me how to upgrade my firmware ? Or is it possible to rebuild TWRP for OnePlus X ? I don't have enough posts to get into these dev topics...
Thank you !
[1]: http://forum.xda-developers.com/one...ry-twrp-2-8-7-0-touch-recovery-t3252840/page1
[2] : http://forum.xda-developers.com/shi...recovery-twrp-2-8-7-0-touch-recovery-t3257172

(Android 11:) Can't install February security patch

Hi everybody,
Right after upgrading my Moto G Pro to Android 11 (SOFIAP_AO_EEA_RPR31.Q4U_20_26_2), I wanted to install the February security patch and received the following message:
Package verification failed
The update package being download is not compatible with the current software version on the device.
Click to expand...
Click to collapse
I wanted to apply the same procedure for OTA updates on my rooted phone that was working under Android 10 (cf. this posting).
Anyone has an idea how to solve this?
Thanks in advance for your help!

today i receive february security patch (RPRS31.Q4U-20-28 (chanell: reteu)), install & root via this method without problem, also before upgrade from A10 to A11 work with same method...
sure you restore stock boot image via magisk manager (step 3) ? your error message look exactly as without restored stock boot...

k3dar7 said:
today i receive february security patch (RPRS31.Q4U-20-28 (chanell: reteu)), install & root via this method without problem, also before upgrade from A10 to A11 work with same method...
sure you restore stock boot image via magisk manager (step 3) ? your error message look exactly as without restored stock boot...
Click to expand...
Click to collapse
Thank you for your reply! Yes, I did uninstall Magisk with "restore images" ("Restoration done!" toast appears on the screen) - but still the problem persists and I receive the error message when I try to update...
Any other idea what could block my OTA update?

You have disabled SmartUpdates? (step 2)
Try:
1. Install Magisk again to CurrentSlot
MagiskManager/Magisk-Install/DirectInstall
2. Disable Wifi and MobileData
3. Reboot
4. MagiskManager/UnstallMagisk/RestoreImages
5. Enable Wifi and/or MobileData
6 . initialize manualy OTA search:
(Android)Settings/System/SystemUpdate
This steps maybe to not have Magisk installed when OTA is inicialized. Not know if help

k3dar7 said:
You have disabled SmartUpdates? (step 2)
Try:
1. Install Magisk again to CurrentSlot
MagiskManager/Magisk-Install/DirectInstall
2. Disable Wifi and MobileData
3. Reboot
4. MagiskManager/UnstallMagisk/RestoreImages
5. Enable Wifi and/or MobileData
6 . initialize manualy OTA search:
(Android)Settings/System/SystemUpdate
This steps maybe to not have Magisk installed when OTA is inicialized. Not know if help
Click to expand...
Click to collapse
Thank you so much!
Yes, "Smart Updates" are disabled.
I tried what you suggested - unfortunately, same error message on step 6...

I still don't understand what blocks the OTA update on my device:
My current Android 11 was flashed with the Rescue and Smart Assistant (LMSA) after a full wipe.
I re-flashed the original boot.img (to completely unroot).
I re-flashed the original recovery.img on both partitions.
I deleted the cache of "Motorola Update Services".
...Now I'm running out of ideas how to get rid of the "Package verification failed" message...
This should be the relevant extract from logcat:
Code:
02-28 19:38:45.512 1580 1580 E update_engine: [ERROR:delta_performer.cc(1205)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
02-28 19:38:45.515 1580 1580 E update_engine: [ERROR:delta_performer.cc(1210)] Expected: sha256|hex = 63B6A76F2009E796A2A1F3F6A70957DB12E2146A6929A659505F9EC5BCA16A53
02-28 19:38:45.518 1580 1580 E update_engine: [ERROR:delta_performer.cc(1213)] Calculated: sha256|hex = 6FE9E5AF9EC26F47B555E7088A8BED085C49BE551AAB5C584D140232F02D6C68
02-28 19:38:45.525 1580 1580 E update_engine: [ERROR:delta_performer.cc(1224)] Operation source (offset:size) in blocks: 0:2,4:1,43:2,161:56
02-28 19:38:45.527 1080 1218 E qdmetadata: paramType 2048 not supported
02-28 19:38:45.534 1580 1580 W update_engine: [WARNING:mount_history.cc(66)] Device was remounted R/W 46 times. Last remount happened on 1970-10-12 05:15:10.000 UTC.
02-28 19:38:45.544 8783 9015 D OtaApp : UpdaterEngHelper:verifyPayloadMetadata:isVerifySuccessful=false

I still have android 10. The Feb security patch worked on my phone fine. You may be trying to install a 10 patch onto an 11 system.

nethunter error E:not enough free space on /system

I'm on stock oos 10.3.11(Rooted and have twrp 3.5.2). Today I decided to install nethunter 2021.2 on my device.
since my last try with 2021.1 was a failure Installation was complete and finished but was stuck with bootloop last time.
But this time, I stuck on installation itself. I'm getting not enough free space on /system error during the installation.
I googled for like 2 hours and found only one article about this issue but that article was about lineage os.
solution from that article is moving pre-installed apps from ‘/system/app/’ to ‘/sdcard/Documents/’ temporarily.
So i tried to move some pre installed apps using the command it provided but it's not working and little bit out dated it seems. so i tried the help function in terminal but i don't know which options i should be using in order to do that operation. I don't want to brick my device. So, if anyone know how to fix this issue, please help me out here.
nethunter dl link: https://images.kali.org/nethunter/nethunter-2021.2-oneplus6-oos-ten-kalifs-full.zip
solution for lineage os link: https://www.zerodaysnoop.com/how-to/how-to-install-nethunter-lite-part-2/

Amudhan501 said:
I'm on stock oos 10.3.11(Rooted and have twrp 3.5.2). Today I decided to install nethunter 2021.2 on my device.
since my last try with 2021.1 was a failure Installation was complete and finished but was stuck with bootloop last time.
But this time, I stuck on installation itself. I'm getting not enough free space on /system error during the installation.
I googled for like 2 hours and found only one article about this issue but that article was about lineage os.
solution from that article is moving pre-installed apps from ‘/system/app/’ to ‘/sdcard/Documents/’ temporarily.
So i tried to move some pre installed apps using the command it provided but it's not working and little bit out dated it seems. so i tried the help function in terminal but i don't know which options i should be using in order to do that operation. I don't want to brick my device. So, if anyone know how to fix this issue, please help me out here.
nethunter dl link: https://images.kali.org/nethunter/nethunter-2021.2-oneplus6-oos-ten-kalifs-full.zip
solution for lineage os link: https://www.zerodaysnoop.com/how-to/how-to-install-nethunter-lite-part-2/
Click to expand...
Click to collapse
Im getting the exact same issue with my stock OOS 10.2.12. I was able to successfully disable dm-verity and force encryption. When I got to the step of installing nethunter I ended up with
"Error: Not enough space on /system to continue!
Aborting...
Cleaning Up...
Failed to install Kali Nethunter!
Updater process ended with ERROR: 1 Error installing zip file usbstorage/Download/nethunter-2021.2-oneplus6-oos-ten-kalifs-full.zip"

I am getting the same issue on a OnePlus 6T, OOS 10.3.12
The steps I follow to install are:
Wipe data
Flash stock ROM
Flash TWRP Installer Zip
Reboot into TWRP
Flash force-decrypt
Flash magisk
I verify with Root Checker that I do indeed have root
I also verify that force-decrypt works by:
Mount vendor
cat /vendor/etc/fstab.* | grep force
No output - suggesting decryption is successful
I am using the official Oneplus 6 Kali image from:
Get Kali | Kali Linux
Home of Kali Linux, an Advanced Penetration Testing Linux distribution used for Penetration Testing, Ethical Hacking and network security assessments.
www.kali.org
Any advice on how to fix this?
Thank you!

Hey guys,
try this
for me this works!

5K1PP3R said:
Hey guys,
try this
for me this works!
Click to expand...
Click to collapse
I tried that but it didn't work. Im not really in the mood to try the other method. I'm just going to get another phone to do it with because Im using this one for some personal stuff I dont want deleted anyway. Great post though, should help someone out for sure.

So heres the steps I used to get Nethunter up and running.
Tmobile 6T user converted to International. (So for all of you running 6, skip the next paragraph and start at Unlock bootloader).
Started fresh with a msm firehose, went back to android 9. Updated to whatever the version you had to download first to get to 10. 9.0.17 I believe. Then after that I upgraded to the very last 10 version. 10.3.12.
Unlock bootloader.
After that I install magisk, pull the payload from the 10.3.12 firmware and pull my boot.img. Patch it.
Boot into TWRP, flash the magisk boot img. Boot into OOS
Now heres the part where everyone (myself included) messes up. Install nethunter via magisk, and not via TWRP. There's just something messed up with how the storage size of system is being reported to the nethunter install script. I've had plenty of space and the script say theres not enough space 0mb free.
Installing via magisk worked just fine as far as app support goes. I haven't checked functionality beyond an apt upgrade and booting into KeX so I havent put it through its paces yet.
Edit: You can also disable system updates afterwards by running:
Code:
adb shell pm disable-user --user 0 com.oneplus.opbackup

i have had the problem o when trying to flash nethunter through twrp it always ending in error not enough space blah blah it was doing my head in but i found a solution so fdroid goto an app called smart flasher and flash it through that it will install after rebooting

Building Lineage OS 18 using an older device tree gives me errors

I am trying to build Lineage OS 18, using the Device Tree and Kernel for Lineage OS 17. When I try to run brunch avicii I get:
error: vendor/qcom/opensource/interfaces/capabilityconfigstore/1.0/Android.bp:3:1: failed to find variation "linux_glibc" for module "[email protected]" needed by "[email protected]" error: vendor/qcom/opensource/interfaces/capabilityconfigstore/1.0/Android.bp:3:1: failed to find variation "windows" for module "[email protected]" needed by "[email protected]" 14:32:43 soong bootstrap failed with: exit status 1
I also tried build Lineage OS 17 for the device, got the same error. I also tried building Lineage OS 18 for the Google Pixel 5, but the device was built without any errors, any ideas?