Database Develop

[REF] [ROM] aosp 2.3.2 .img's for crespo (Nexus S) *UPDATED 2/3/11*

Here are the 2.3.2 .img's compiled from aosp source for crespo (Nexus S)
We don't have a pure 2.3 ROM compiled from aosp source yet, so I decided build one, and here are the .img's from my build.
These can be used to restore Nexus S back to aosp, or flash all images for a pure aosp experience.
HOWEVER: These are NOT the official Google factory images for Nexus S, only compiled from source.
Attached are: system.img boot.img recovery.img userdata.img
Installation:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
All images being provided work 100%, as I have it installed on my nexus S currently and flashed via fastboot.
disclaimer: WARNING! I am in no way shape or form responsible for ANY DAMAGE you may do to your phone. I am simply providing the files, however you decide to flash on your own, not me.
These images also do not contain any proprietary apps such as the Google apps (Maps, Market, Gmail, etc)
Clear? ok then, proceed to download
system .img link: http://www.mediafire.com/file/k2jopya0o416m8j/system.img
others are attached below.
UPDATE: these .img's are for 2.3.2
Attached bcm4329.ko module to fix wifi for users who flashed my boot.img on a non-aosp ROM (push to /system/modules)

2.3.2 OTA package
Here is the 2.3.2 ota update package for those of you who don't like/wanna use fastboot for whatever reason.
Rename as update.zip, place on sdcard and flash as usual.
http://www.mediafire.com/file/fl1nxdpleitd392/2.3.2_full_crespo-ota-eng-signed.zip
WARNING! This ota update package is fully stock, has NO ROOT or Google proprietary applications, and will revert you to the stock recovery.
Google Applications archive can be found here: http://goo-inside.me/gapps/
Atached below are the files needed to manually root: SuperUser.apk, su, busybox.
Code:
adb push SuperUser.apk /system/app
adb push su /system/xbin
adb push busybox /system/xbin
chmod 6775 /system/xbin/su
chmod 6775 /system/xbin/busybox
adb shell reboot
If terminal doesn't let you remount in adb you may have to do it through the phone. Place all root files on sdcard:
Code:
mount -o rw,remount /dev/block/mmcblk0p2 /system
cp /sdcard/SuperUser.apk /system/app/
cp /sdcard/su /system/xbin/
cp /sdcard/busybox /system/xbin/
chmod 6775 /system/xbin/su
chmod 6775 /system/xbin/busybox
Reboot with a battery pull.

reserved again. You Never know

Thanks alot I've been looking for the stock recovery img
Sent from my Nexus S using Tapatalk

brian6685 said:
Thanks alot I've been looking for the stock recovery img
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
The recovery image from this post sadly still does not allow to flash the update from Google.
Getting signature verification error and yes i reverted back to the boot.img posted here as well.
EDIT: the boot.img here is also breaking wifi.
thanks for the effort though

clubtech said:
The recovery image from this post sadly still does not allow to flash the update from Google.
Getting signature verification error and yes i reverted back to the boot.img posted here as well.
EDIT: the boot.img here is also breaking wifi.
thanks for the effort though
Click to expand...
Click to collapse
Why wouldn't the ota work if you were using the stock recovery? That's weird
Sent from my Nexus S using Tapatalk

clubtech said:
The recovery image from this post sadly still does not allow to flash the update from Google.
Getting signature verification error and yes i reverted back to the boot.img posted here as well.
EDIT: the boot.img here is also breaking wifi.
thanks for the effort though
Click to expand...
Click to collapse
??? I flashed everything before posting and all was working perfect. I flashed all .img's though, maybe wifi broke for having a different system image and different wifi modules than aosp.. I just flashed paul's rom and reverted to stock recovery.img without a hitch with the one I posted.

brian6685 said:
Why wouldn't the ota work if you were using the stock recovery? That's weird
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
That's because it is not really stock recovery, it is a recovery built from source.
I guess it does not have google's signature.

Do you know of anywhere I can get the stock recovery? Or does fastboot oem lock bring back stock recovery?
Sent from my Nexus S using Tapatalk

jroid said:
??? I flashed everything before posting and all was working perfect. I flashed all .img's though, maybe wifi broke for having a different system image and different wifi modules than aosp.. I just flashed paul's rom and reverted to stock recovery.img without a hitch with the one I posted.
Click to expand...
Click to collapse
I can install your recovery, no problem. but i am not able to use the update.zip from Google with your stock recovery (signature verification failed).
I also tried with you stock recovery and boot.img - same issue.
When i booted the device with you stock recovery + boot.img but my original (stock) system.img - wifi could not start.

clubtech said:
When i booted the device with you stock recovery + boot.img but my original (stock) system.img - wifi could not start.
Click to expand...
Click to collapse
That's probably where the problem lies. I flashed all .img's including my system.img and wifi worked perfectly

Does this include gapps?

Anderdroid said:
Does this include gapps?
Click to expand...
Click to collapse
no, they're aosp images built from source.

clubtech said:
When i booted the device with you stock recovery + boot.img but my original (stock) system.img - wifi could not start.
Click to expand...
Click to collapse
Issue fixed. Please see the OP.

Hi jroid,
I tried to compile the 2.3.1 sources from AOSP today and ran into hundrets of warnings (no errors though so I might be OK). I did some coding for linux before but have no experience building Android from source. Can you provide the steps required to build?
As far as I can tell my environment is setup properly: I did a fresk Debian 64bit, JDK 6 and all the packages listed on sources.android.com - even if the information listed there is outdated. I installed Eclipse as well but didn't use it so far because I want to get the unchanged AOSP build correctly first.
To build I ran env_setup.sh, then lunch and picked crespo, then make... that's where I'm stuck right now.
I want to get the base build correctly before starting any changes. I'd love to get this setup in a way that allows me to test the build in the emulator first and then flash to the NS... Not sure if that's the best way or using fastboot boot instead of flash to see if it's working properly directly on the device (all new to me, sorry if these are dumb questions).
I searched the forum and the wiki but didn't find general or NS specific documentation for AOSP builds...

ToSa2 said:
Hi jroid,
I tried to compile the 2.3.1 sources from AOSP today and ran into hundrets of warnings (no errors though so I might be OK). I did some coding for linux before but have no experience building Android from source. Can you provide the steps required to build?
As far as I can tell my environment is setup properly: I did a fresk Debian 64bit, JDK 6 and all the packages listed on sources.android.com - even if the information listed there is outdated. I installed Eclipse as well but didn't use it so far because I want to get the unchanged AOSP build correctly first.
To build I ran env_setup.sh, then lunch and picked crespo, then make... that's where I'm stuck right now.
I want to get the base build correctly before starting any changes. I'd love to get this setup in a way that allows me to test the build in the emulator first and then flash to the NS... Not sure if that's the best way or using fastboot boot instead of flash to see if it's working properly directly on the device (all new to me, sorry if these are dumb questions).
I searched the forum and the wiki but didn't find general or NS specific documentation for AOSP builds...
Click to expand...
Click to collapse
I'm away from my laptop right now, but get adb installed first. Repo sync then cd to /crespo and run extract-files.sh
.Build env_setup.sh
Lunch full_crespo-userdebug
Make
Warnings should be fine, I got them too and it compiled perfectly. If you get errors, u will know. The compile with stop
Sent from my Nexus S

Thanks!
I did the extract-files.sh now which I missed before - running make over night so I'll see tomorrow if I get any errors...
Any advice how to test minimizing the risk (emulator / fastboot boot)?

ToSa2 said:
Thanks!
I did the extract-files.sh now which I missed before - running make over night so I'll see tomorrow if I get any errors...
Any advice how to test minimizing the risk (emulator / fastboot boot)?
Click to expand...
Click to collapse
yea you can use the fastboot boot command to test. I personally just flashed all the images through fastboot and it booted fine. aosp 2.3.1 (which I compiled) is in my experience FASTER and more smooth than the stock rom that shipped with the NS. Call audio quality is MUCH more rich robust than it is on the factory builds. have no idea why but it is

Since the Google apps aren't included, I'm guessing they all may be downloaded/installed from the Market... is that correct?
Thanks,

jankyboy said:
Since the Google apps aren't included, I'm guessing they all may be downloaded/installed from the Market... is that correct?
Thanks,
Click to expand...
Click to collapse
no, not all. Only some, but this doesn't even include the market so you couldn't even do that. I'm compiling from source again and probably release an AOSP rom in a day or 2, maybe even today..

Xposed Installer destroyed my Toshiba AT300SE rooted

I installed Xposed Installer (v2.6.1) on my rooted Toshiba AT300SE (Excite 10 SE) with AOSP JB on it.
After installation device rebooted and now stuck on boot loop.
Any suggestion to get out of this.

Restore the backup that you should have made before installing the Xposed framework, or flash the Xposed disabler zip from recovery. Or read the FAQ.
Sent from my C6603 using Tapatalk

kingvortex said:
Restore the backup that you should have made before installing the Xposed framework, or flash the Xposed disabler zip from recovery. Or read the FAQ.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
i'll try this

kingvortex said:
Restore the backup that you should have made before installing the Xposed framework, or flash the Xposed disabler zip from recovery. Or read the FAQ.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Seems that disabler zip did not work.
Any other brilliant ideas................

Rooks said:
Seems that disabler zip did not work.
Any other brilliant ideas................
Click to expand...
Click to collapse
Yes, plenty, but your sarcasm precludes me from sharing them with you.
Read the FAQ and/or other pinned threads in this section.
I won't reply in this thread again. Have a good day.
Sent from my C6603 using Tapatalk

kingvortex said:
Yes, plenty, but your sarcasm precludes me from sharing them with you.
Read the FAQ and/or other pinned threads in this section.
I won't reply in this thread again. Have a good day.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Well it's nice to share something.
.
.
.
.
.
.
.
If it's helpful for someone.

Rooks said:
Well it's nice to share something.
.
.
.
.
.
.
.
If it's helpful for someone.
Click to expand...
Click to collapse
Sadly, not many people around here possess a crystal ball to determine what may be helpful to you on advance. If it didn't help you, just say so politely.
If the Xposed disabler zip didn't work, you probably want to make sure it flashed correctly. You can also use adb to disable the Xposed framework if that still doesn't work out for you.

Rooks said:
Seems that disabler zip did not work.
Any other brilliant ideas................
Click to expand...
Click to collapse
Only brilliant idea here was flashing something before backing up your rom.
Sent from my Nexus 5 using Tapatalk

GermainZ said:
Sadly, not many people around here possess a crystal ball to determine what may be helpful to you on advance. If it didn't help you, just say so politely.
If the Xposed disabler zip didn't work, you probably want to make sure it flashed correctly. You can also use adb to disable the Xposed framework if that still doesn't work out for you.
Click to expand...
Click to collapse
I did not mean to be rude or ANY disrespect.
So guys, PLEASE point me to right direction so that i can bring back my device.

rovo89 said:
In case you get into a boot loop:
First, try using the safemode by pressing any hardware key repeatedly. You can find a short explanation how it works here.
If that doesn't work, you can flash the attached Xposed-Disabler-Recovery.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053

rovo89 said:
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Click to expand...
Click to collapse
Where can i find disabler zip file?
I downloaded some files from web (all around 1.2kb in size) and all these have only one folder "meta-inf", nothing else.

Rooks said:
Where can i find disabler zip file?
Click to expand...
Click to collapse
From the linked post:
If that doesn't work, you can flash the attached Xposed-Disabler-Recovery.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Click to expand...
Click to collapse
Rooks said:
I downloaded some files from web (all around 1.2kb in size) and all these have only one folder "meta-inf", nothing else.
Click to expand...
Click to collapse
Assuming it doesn't work for one reason or the other, you can do this (also from the linked post):
The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Click to expand...
Click to collapse

GermainZ said:
From the linked post:
Assuming it doesn't work for one reason or the other, you can do this (also from the linked post):
Click to expand...
Click to collapse
Yes i've tried three different files, all failed to install.
Guess i've no choice left except adb.

Rooks said:
Yes i've tried three different files, all failed to install.
Guess i've no choice left except adb.
Click to expand...
Click to collapse
You may also want to grab a logcat of the boot loop (also using adb), BTW. That way, the issue might actually be identified and possibly resolved in the future.

Rooks said:
Yes i've tried three different files, all failed to install.
Click to expand...
Click to collapse
You should mainly try the one attached to the other thread... But it will only work on a custom recovery (CWM/TWRP). Not sure, but yours looks more like a stock recovery.
Also, did you try pressing a key many times as written in my quote?

Rooks said:
Where can i find disabler zip file?
I downloaded some file from web (all around 1.2kb in size) and all these have only one folder "meta-inf", nothing else.
Click to expand...
Click to collapse
Uninstaller performs only one move operation (or a copy operation plus delete operation) which is being performed on the files which already exist in the device. No need of involving external files, so the only dir in the zip is the one containg updater-binary file ie. META-INF. binary can be a simple, single-liner shell script which triggers basic shell command performing required, trivial operation. As most custom recoveries accept unsigned zips so signing it is not really required, resulting flashable woulď be a zip file containing singłe no more than 100bytes long file placed in a an empty subdir.
12kb size of such a zip shall be considered as a nothing that you should worry about then.
Probably u are running stock recovery which cąnnot flash zips signeď by anyone except a producer. It is also possible that the screenshots come from the older custom recovery, afair primer builds of cwm-based recoveries looked very similiar to stock ones. In thąt case the only reason of failure that I may think of is the fact that earlier versions of cwm did not neccessary provide a possibility to flash unsigned zips; didn't check but maybe uninstaller zip created by the installer is not signed (which I didnt check so I might be wrong; modern recoveries are flashing zips with no signature without any problems by default but less popular devices might be forced to use a version compiled by someone once ąnd never maintained = the only available). You may want to check if there is any option in your CWM that will enablę flashing such a zips and if it isnt possible, sign the zips on your own using any key, even a test one included to signapk.jar.

GermainZ said:
You may also want to grab a logcat of the boot loop (also using adb), BTW. That way, the issue might actually be identified and possibly resolved in the future.
Click to expand...
Click to collapse
I'll try to get logcat for this issue.
rovo89 said:
You should mainly try the one attached to the other thread... But it will only work on a custom recovery (CWM/TWRP). Not sure, but yours looks more like a stock recovery.
Also, did you try pressing a key many times as written in my quote?
Click to expand...
Click to collapse
Yes, it's the stock recovery and i've tried several times with hardware keys but safe mode did not work in my scenario.
esgie said:
Uninstaller performs only one move operation (or a copy operation plus delete operation) which is being performed on the files which already exist in the device. No need of involving external files, so the only dir in the zip is the one containg updater-binary file ie. META-INF. binary can be a simple, single-liner shell script which triggers basic shell command performing required, trivial operation. As most custom recoveries accept unsigned zips so signing it is not really required, resulting flashable woulď be a zip file containing singłe no more than 100bytes long file placed in a an empty subdir.
12kb size of such a zip shall be considered as a nothing that you should worry about then.
Probably u are running stock recovery which cąnnot flash zips signeď by anyone except a producer. It is also possible that the screenshots come from the older custom recovery, afair primer builds of cwm-based recoveries looked very similiar to stock ones. In thąt case the only reason of failure that I may think of is the fact that earlier versions of cwm did not neccessary provide a possibility to flash unsigned zips; didn't check but maybe uninstaller zip created by the installer is not signed (which I didnt check so I might be wrong; modern recoveries are flashing zips with no signature without any problems by default but less popular devices might be forced to use a version compiled by someone once ąnd never maintained = the only available). You may want to check if there is any option in your CWM that will enablę flashing such a zips and if it isnt possible, sign the zips on your own using any key, even a test one included to signapk.jar.
Click to expand...
Click to collapse
I've tried three different file with different sizes (143kb, 121kb and 145kb), all these files include the same script ("updater-script" file) by Tungswenty.
ui_print("");
ui_print("");
ui_print("------------------------");
ui_print(" Xposed disabler tool ");
ui_print(" by Tungswenty ");
ui_print("------------------------");
ui_print("");
ui_print("Mounting system partition");
ifelse(!is_mounted("/system"),
run_program("/sbin/busybox", "mount", "/system"));
assert(is_mounted("/system"));
ifelse(run_program("/system/bin/sh", "-c", "test -f /system/bin/app_process.orig") == 0,
(
ui_print("Restoring the original app_process file");
assert(run_program("/sbin/busybox", "cp", "-a", "/system/bin/app_process.orig", "/system/bin/app_process"));
set_perm(0, 2000, 0755, "/system/bin/app_process");
ui_print("Restore complete.");
ui_print("You should now be able to boot normally and remove all traces of Xposed from within the Installer app.");
),
(
ui_print("No backup found for app_process, nothing to be performed!");
));
ui_print("");
ui_print("Done.");
ui_print("");
Click to expand...
Click to collapse

Rooks said:
Yes, it's the stock recovery
Click to expand...
Click to collapse
Then you can stop trying any flashable zips, they won't work on stock recovery.
If you can install a custom recovery, that should help. Or flashing only the /system partition of your ROM again. Or check if you can execute "adb shell id" and post the result (should show whether you get root access in recovery to perform the steps manually).

rovo89 said:
Then you can stop trying any flashable zips, they won't work on stock recovery.
If you can install a custom recovery, that should help. Or flashing only the /system partition of your ROM again. Or check if you can execute "adb shell id" and post the result (should show whether you get root access in recovery to perform the steps manually).
Click to expand...
Click to collapse
I've stock rom and recovery, there is no custom rom or recovery available for my device (Toshiba Excite 10 SE aka AT300SE).
So with stock rom and recovery it won't accept any zips and i can't format system partition with stock recovery. And about adb, i don't know where to start. In recovery there is an option to push a file through adb but when i connect my device while this option, my pc does not recognize the device, neither i can update the adb drivers.

Rooks said:
I installed Xposed Installer (v2.6.1) on my rooted Toshiba AT300SE (Excite 10 SE) with AOSP JB on it.
After installation device rebooted and now stuck on boot loop.
Any suggestion to get out of this.
Click to expand...
Click to collapse
HOW YOU ROOT...???!!!
PLEASE TELL ME
I CANT FIND IN WEB....
Give me a links if you can ....
THANKS

TWRP, System writing, Supersu, Impossible?

I have had my fair share of problems modifying android before but I have never had a phone flat out lie to me and say an operation was successful and actually nothing happened at all.
Have had my nexus 6 for a year or so now. Have had minor issues rooting / modifying marshmallow in the past but I figured out it was all caused by the system partition having basically 0 free space. Made a huge mistake and installed to the latest 7.0 OTA. Wanted to simply enable tethering and edit the thermal config to not shut cores down. Should be as simple as pulling the files, editing them, pushing them back to the phone in twrp with the system partition mounted and thats the end of it right? Wrong.
First of all twrp 3.0.2 refuses to let me touch the system partition without some giant prompt about how its going to make itself stick and offer to root the phone. Simple enough I have seen it in previous versions I say yes as usual except twrp proceedes to immediately spew a bunch of superuser files that do nothing throughout the system partition without asking me if I want root. Dumb but whatever. I mount /system as read write and I go edit and replace my two files like usual (build.prop and thermal config). No matter if I ADB push or use twrps built in file manager it claims the file replacement is successful. Reboot into android and not only have both files not been touched (Verified by adb pull) but the recovery gets overwritten with the factory recovery anyways. (NEVER had issues with twrp sticking on marshmallow. Now after every reboot it gets wiped out)
Second of all if I select yes to twrp mounting system as writable and it does its spewing as I mentioned before then installing SuperSU instantly causes the phone to not boot. Rewrite the boot.img to factory and it boots fine OR Rewrite the clean factory system image and the SuperSU boot works fine. But modifying /system with twrp and then running supersu at the same time is a no go. TWRP is obviously doing something stupid to system that pisses off supersu so undoing twrps mess or uninstalling supersu makes it bootable again.
I dont even want root! Everyone is claiming you need to run "settings put global tether_dun_required 0" as root along with adding the usual "net.tethering.noprovisioning=true" in the build.prop to get native tethering working again! On 6.X only the build.prop edit was needed to get it working.
So long story short. I just want native tethering to work and to tweak my /system/etc/thermal-engine-shamu.conf . Is there anyone here who has done this successfully on nougat? I feel like its all twrps fault but im far too tired and frustrated to try another version tonight.

You must be running an old version of TWRP. Update to the latest, as the latest no longer offers to root your device for you. The version of superuser included was ancient and caused the device to bootloop.
As to TWRP being overwritten Android 7.0 I believe does that on a stock system. If I recall, there is a script that needs to be modified to prevent it.

Strephon Alkhalikoi said:
You must be running an old version of TWRP. Update to the latest, as the latest no longer offers to root your device for you. The version of superuser included was ancient and caused the device to bootloop.
As to TWRP being overwritten Android 7.0 I believe does that on a stock system. If I recall, there is a script that needs to be modified to prevent it.
Click to expand...
Click to collapse
It's stated in the op he's using twrp 3.0.2.

Didgeridoohan said:
It's stated in the op he's using twrp 3.0.2.
Click to expand...
Click to collapse
I misread his post then. I wonder if perhaps he is running TWRP via fastboot instead of installing it.

Flashing recovery using "fastboot flash recovery XXX.img"

Magisk Installing OTA on Pixel XL 1

Hi,
I own a Pixel XL 128GB, running 8.0.0 October FW. I have installed Magisk 14.3 beta 1437. Almost everything works, except for:
1. When installing Magisk using Magisk's internal installer it always downloads MAgisk 14.0 and tries to install this old, outdated version. Is this a bug?
2. I can't install OTAs, tried following john's installing instructions...
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
My steps were:
* Install stock boot loader - Magisk almost immediately confirms that it has installed the stock boot image. That's a bit surprising, I don't see any flashing dialog like when installing Magisk. Bug?
* trying to update using the internal OTA fails. It takes very long and suddenly stops.
Any idea what went wrong?

niko26 said:
Hi,
I own a Pixel XL 128GB, running 8.0.0 October FW. I have installed Magisk 14.3 beta 1437. Almost everything works, except for:
1. When installing Magisk using Magisk's internal installer it always downloads MAgisk 14.0 and tries to install this old, outdated version. Is this a bug?
2. I can't install OTAs, tried following john's installing instructions...
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
My steps were:
* Install stock boot loader - Magisk almost immediately confirms that it has installed the stock boot image. That's a bit surprising, I don't see any flashing dialog like when installing Magisk. Bug?
* trying to update using the internal OTA fails. It takes very long and suddenly stops.
Any idea what went wrong?
Click to expand...
Click to collapse
1. If you wan't the current beta to install, you need to change to the beta update channel in the Manager settings.
2. You've probably done something that messes with important partitions (/system, /vendor, etc). It's enough to just mount the partition rw to destroy the ability to update through OTA.
Restoring the stock boot image through the Manager is instantaneous...

Hi @Didgeridoohan,
thank you very much for the quick answers!
Didgeridoohan said:
1. If you wan't the current beta to install, you need to change to the beta update channel in the Manager settings.
Click to expand...
Click to collapse
Thanks - I didn't know that.
2. You've probably done something that messes with important partitions (/system, /vendor, etc). It's enough to just mount the partition rw to destroy the ability to update through OTA.
Click to expand...
Click to collapse
Hm, how do I find out what has been messed on /system, and/or /vendor?
Does installing and using AdAway tamper with /system or /vendor?
So reflashing the stock boot image is not sufficent, correct?
And most important.. how do I fix this?

niko26 said:
Hi @Didgeridoohan,
thank you very much for the quick answers!
Thanks - I didn't know that.
Hm, how do I find out what has been messed on /system, and/or /vendor?
Does installing and using AdAway tamper with /system or /vendor?
So reflashing the stock boot image is not sufficent, correct?
And most important.. how do I fix this?
Click to expand...
Click to collapse
If you let AdAway directly write to /system/etc/hosts, then yes, you have a compromised system partition. If you're using Magisk Systemless Hosts you should be fine though. Do you have TWRP installed? That'd be an issue as well...
If you want to make sure that you can update through OTA in the future, clean flash a factory image (you can leave data intact) and then make sure not to touch /system or /vendor at all.

* DELETED *

Didgeridoohan said:
If you let AdAway directly write to /system/etc/hosts, then yes, you have a compromised system partition. If you're using Magisk Systemless Hosts you should be fine though.
Click to expand...
Click to collapse
Yeah, I've been using Magisk's systemless hosts-file.
. Do you have TWRP installed? That'd be an issue as well...
Click to expand...
Click to collapse
TWRP has not been installed permanently.
If you want to make sure that you can update through OTA in the future, clean flash a factory image (you can leave data intact) and then make sure not to touch /system or /vendor at all.
Click to expand...
Click to collapse
There aren't a lot of apps I am granting root. One of them is Titanium Backup. It may have tampered the fs.
Is there any kind of diff against the original folders which I can run to find out what has been tampered to possibly identify which app is causing the issues?
One of the main reasons for installing Magisk was because I was tired of flashing the entire system when updates have been released.
I never couldn't get Flashfire working properly when it comes to install updates / OTAs.

niko26 said:
Yeah, I've been using Magisk's systemless hosts-file.
TWRP has not been installed permanently.
There aren't a lot of apps I am granting root. One of them is Titanium Backup. It may have tampered the fs.
Is there any kind of diff against the original folders which I can run to find out what has been tampered to possibly identify which app is causing the issues?
One of the main reasons for installing Magisk was because I was tired of flashing the entire system when updates have been released.
I never couldn't get Flashfire working properly when it comes to install updates / OTAs.
Click to expand...
Click to collapse
Since the OTA can check for a tampered system, I'm sure there's a way to check. Question is if it's worth the effort.
Any app that has root access can be the culprit... Could also be that you let TWRP mount system rw or something similar. Really hard to say...

Didgeridoohan said:
Since the OTA can check for a tampered system, I'm sure there's a way to check. Question is if it's worth the effort.
Any app that has root access can be the culprit... Could also be that you let TWRP mount system rw or something similar. Really hard to say...
Click to expand...
Click to collapse
Does TWRP mount system as rw by default? Because all I really do is.. boot to TWRP, flash the Magisk's zip. That's it. Nothing else.
Is there any other way I can install OTAs without using a computer with USB (and keeping root of course )?
As said... I never could FlashFire to work correctly. The documentation leaves a lot of questions open - BTW.. props to the Magisk's docs - much better.

niko26 said:
Does TWRP mount system as rw by default? Because all I really do is.. boot to TWRP, flash the Magisk's zip. That's it. Nothing else.
Is there any other way I can install OTAs without using a computer with USB (and keeping root of course )?
As said... I never could FlashFire to work correctly. The documentation leaves a lot of questions open - BTW.. props to the Magisk's docs - much better.
Click to expand...
Click to collapse
TWRP doesn't mount system as rw unless you let it.
I've never used Flashfire and haven't updated through OTA since, 2014-ish. :laugh: I'm mainly going on theoretical knowledge here... On my Nexus I used fastboot to flash the factory image (until I switched to ROM flashing in TWRP) and now I just flash the full update package that OnePlus provides in TWRP.
For a while there I also flashed the system.img and boot.img files in TWRP. If that months security update only had anything to do with those files it was just a matter of downloading the factory image and unpack those two files and flash them directly in TWRP. No computer needed (unless there was an update to the bootloader and/or radio). No idea if this is viable on a Pixel...
My main use for Magisk is that all my system modifications are still there after I update my phone. Drastically cuts down on the time it takes to set my phone up after an update.

Didgeridoohan said:
I've never used Flashfire and haven't updated through OTA since, 2014-ish. :laugh: I'm mainly going on theoretical knowledge here... On my Nexus I used fastboot to flash the factory image (until I switched to ROM flashing in TWRP) and now I just flash the full update package that OnePlus provides in TWRP.
Click to expand...
Click to collapse
I've tried installing TWRP permanently, but the moment I have installed an official patch, it got wiped - and I haven't found any docs how to prevent that.
My main use for Magisk is that all my system modifications are still there after I update my phone. Drastically cuts down on the time it takes to set my phone up after an update.
Click to expand...
Click to collapse
What settings are you referring to?

niko26 said:
I've tried installing TWRP permanently, but the moment I have installed an official patch, it got wiped - and I haven't found any docs how to prevent that.
Click to expand...
Click to collapse
After updating, you probably need to boot straight to TWRP and reflash root. If you boot directly to the OS, it'll automatically replace TWRP with the stock recovery.
What settings are you referring to?
Click to expand...
Click to collapse
I like to change screen density, debloat system apps, install Viper4Android, install boot scripts (LiveBoot, etc) and a bunch of other things. With Magisk, as long as I don't wipe /data, all of that will still be intact after a system update. And even if I wipe data I can restore a backup of the Magisk image or just flash the module zips in TWRP. Takes seconds rather than half an hour like it could prior to Magisk.

Didgeridoohan said:
After updating, you probably need to boot straight to TWRP and reflash root. If you boot directly to the OS, it'll automatically replace TWRP with the stock recovery.
Click to expand...
Click to collapse
Well, TWRP is gone after an update - I can't boot into it.
[/quote]I like to change screen density, debloat system apps, install Viper4Android, install boot scripts (LiveBoot, etc) and a bunch of other things. With Magisk, as long as I don't wipe /data, all of that will still be intact after a system update. And even if I wipe data I can restore a backup of the Magisk image or just flash the module zips in TWRP. Takes seconds rather than half an hour like it could prior to Magisk.[/QUOTE]
Hm, I am not sure if I get you right. If it is about apps, I use Titanium Backup to recover my old apps+settings.

system files
Most of the setting you mentioned are messing with the system files. "debloating" or removing and system applications with titanium backup will fail a system check with OTA update. You can freeze the apps i believe.
I changing the screen density and boot scripts. These are all system files locations.
I have had an ota work be re-installing the system apps from titanium backup and reverting all the other changes when it was failing before. Think this was back on android 6.0 though.
Didgeridoohan said:
After updating, you probably need to boot straight to TWRP and reflash root. If you boot directly to the OS, it'll automatically replace TWRP with the stock recovery.
I like to change screen density, debloat system apps, install Viper4Android, install boot scripts (LiveBoot, etc) and a bunch of other things. With Magisk, as long as I don't wipe /data, all of that will still be intact after a system update. And even if I wipe data I can restore a backup of the Magisk image or just flash the module zips in TWRP. Takes seconds rather than half an hour like it could prior to Magisk.
Click to expand...
Click to collapse

automattic said:
Most of the setting you mentioned are messing with the system files. "debloating" or removing and system applications with titanium backup will fail a system check with OTA update. You can freeze the apps i believe.
I changing the screen density and boot scripts. These are all system files locations.
I have had an ota work be re-installing the system apps from titanium backup and reverting all the other changes when it was failing before. Think this was back on android 6.0 though.
Click to expand...
Click to collapse
Since all of the things I mentioned are done with Magisk, none of them will cause an OTA to fail...
Reinstalling system apps will not work, since nowadays an OTA will fail just by mounting /system as rw.

Hi guys, trying to install latest OTA patch for Pixel 2. I am assuming process would be the same. I tried to follow the guide but hit the bump immediately. I can't see "Restore Stock Boot" when pressing uninstall. But there is restore images option. Hitting it does nothing, I receive the message that there are no backups. Where does the backup go so I can put the original file for it to be reinstalled?

[UNOFFICIAL][Recovery][Stock][tissot] TWRP 3.2.1-0 for Mi A1 (New installer)

What?
A TWRP bootable-image and installer ZIP for stock-based ROM's (i.e. not LOS 15.1) and maybe others (untested).
Based on:
Latest TWRP build provided by @pl_blaze
The official TWRP installation script for Pixel 2 by Dees_Troy (will install to both slots automatically - more resilient than the other TWRP script)
The IMG uses official kernel 8.1.10 so might be flashable (not tested!)
Not compatible with LineageOS 15.1 because it uses some custom update API that isn't in this TWRP. I considered using the LOS 15.1 TWRP build in this, but it's not compatible with stock encryption (it always thinks the passcode is wrong).
Full credits to @pl_blaze and Dees_Troy for this. I just packaged up something new and wrote clear instructions.
Why?
The old TWRP thread is not maintained and people keep asking/reporting the same questions/problems. I will try to keep this up to date as long as necessary. This is also a more robust installation script, using magiskboot binary to unpack/repack the boot image.
How?
Uninstall Magisk first if you have it installed, just to be safe. Or reflash stock boot.img. (Might not be necessary - a dirty flash worked OK for me but YMMV).
Fastboot boot (hotboot) any existing working TWRP image. Don't worry about working encryption/data, we only need kernel access. For example...
Code:
fastboot boot oreo_3.2.2_recovery.img
... which can be downloaded from Google Drive here (thanks to whoever shared this, I think it's a pl_blaze reshare).
Download attachment ZIP installer and flash in hot-booted TWRP (it will flash to both slots)
Reboot to Recovery and (re-)flash Magisk, if you use it.
Profit

@pl_blaze brother always thank you for the contributions that you do without coming to the light .and thanks for you @op to post working twrp for stock

this twrp will work on 7.1.2 ? i'm now on aex rom

Thanks @CosmicDan for starting this thread. I started to implement @pl_blaze changes into the official TWRP but I've been failing miserably (I'm a noob). Can you provide sources for the images?
I can't trust binaries floating all over the internet if it's not from a reliable dev. If you've compiled it yourself I'll give a try.

I reshare this twrp img on Telegram group,I tested it, works without problem
Flash of permaent twrp not tested by me
It's a good twrp!

CosmicDan said:
What?
A TWRP bootable-image and installer ZIP for stock-based ROM's (i.e. not LOS 15.1) and maybe others (untested).
Based on:
Latest TWRP build provided by @pl_blaze
The official TWRP installation script for Pixel 2 by Dees_Troy (will install to both slots automatically - more resilient than the other TWRP script)
The IMG uses official kernel 8.1.10 so might be flashable (not tested!)
Not compatible with LineageOS 15.1 because it uses some custom update API that isn't in this TWRP. I considered using the LOS 15.1 TWRP build in this, but it's not compatible with stock encryption (it always thinks the passcode is wrong).
Full credits to @pl_blaze and Dees_Troy for this. I just packaged up something new and wrote clear instructions.
Why?
The old TWRP thread is not maintained and people keep asking/reporting the same questions/problems. I will try to keep this up to date as long as necessary. This is also a more robust installation script, using magiskboot binary to unpack/repack the boot image.
How?
Uninstall Magisk first if you have it installed, just to be safe. Or reflash stock boot.img. (Might not be necessary - a dirty flash worked OK for me but YMMV).
Fastboot boot (hotboot) any existing working TWRP image. Don't worry about working encryption/data, we only need kernel access. For example...
Code:
fastboot boot oreo_3.2.2_recovery.img
... which can be downloaded from Google Drive here (thanks to whoever shared this, I think it's a pl_blaze reshare).
Download attachment ZIP installer and flash in hot-booted TWRP (it will flash to both slots)
Reboot to Recovery and (re-)flash Magisk, if you use it.
Profit
Click to expand...
Click to collapse
what does mean "hot boot", sorry am novice, Not even he could boot boot recovery from Minimal ADB and fastboot ,,, What am I doing wrong?
View attachment 4438212

teacapan said:
Fastboot boot (hotboot) anwhat does mean "hot boot", sorry am novice, Not even he could boot boot recovery from Minimal ADB and fastboot ,,, What am I doing wrong?
Click to expand...
Click to collapse
Hot boot means you are not flashing the recovery image just running it temporarily. Stock boot image is untouched in this process.
Run
fastboot devices
To check whether your device is connected.

alkesh95 said:
Hot boot means you are not flashing the recovery image just running it temporarily. Stock boot image is untouched in this process.
Run
fastboot devices
To check whether your device is connected.
Click to expand...
Click to collapse
thanks for reply, if you look at the screenshot it looks I am connected, the point is that it does not load the file, it does not find it, so if it does not start in recovery I can not do anything I'm stuck.

teacapan said:
thanks for reply, if you look at the screenshot it looks I am connected, the point is that it does not load the file, it does not find it, so if it does not start in recovery I can not do anything I'm stuck.
Click to expand...
Click to collapse
Did you put your recovery into the fastboot forder?
Did you unpack the zip ?
Also check if the name of recovery image is the same

It's possible to make password for twrp

DELETED.

lef7er1s said:
Did you put your recovery into the fastboot forder?
Did you unpack the zip ?
Also check if the name of recovery image is the same
Click to expand...
Click to collapse
1-yes
2-yes
3-yes
Anyway thanks for try help me.

Yeah well, I'm still stuck where, some help would be very appreciated.
View attachment 4438552
View attachment 4438553

Polluktus said:
this twrp will work on 7.1.2 ? i'm now on aex rom
Click to expand...
Click to collapse
Not sure, I've only tested on stock Oreo. Try and and let us know!
atttoush said:
Thanks @CosmicDan for starting this thread. I started to implement @pl_blaze changes into the official TWRP but I've been failing miserably (I'm a noob). Can you provide sources for the images?
I can't trust binaries floating all over the internet if it's not from a reliable dev. If you've compiled it yourself I'll give a try.
Click to expand...
Click to collapse
Indeed, no I have not compiled it myself - just ripped from pl_blaze.
I have a Oreo source repo cloned now for other reasons, but I might try and compile TWRP myself. Although it's been a couple years since I've tried to compile device-specific stuff from an AOSP tree so I don't know how long that will take.
teacapan said:
thanks for reply, if you look at the screenshot it looks I am connected, the point is that it does not load the file, it does not find it, so if it does not start in recovery I can not do anything I'm stuck.
Click to expand...
Click to collapse
Sounds like you just need to learn more about how to use console tools. You need to make sure the "fastboot boot filename.img" command will have a "filename.img" that matches the img filename in the current directory. This is just an example - substitute "filename.img" for the real filename. Use the CD command to change directory to where the img is.

teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
View attachment 4438552
View attachment 4438553
Click to expand...
Click to collapse
Try renaming the img file to something simpler like oreo_twrp.img
Edit: ah yes, the file you are pointing to has to be in the same directory where you opened cmd window, as cosmicdan stated above

CosmicDan said:
Indeed, no I have not compiled it myself - just ripped from pl_blaze.
I have a Oreo source repo cloned now for other reasons, but I might try and compile TWRP myself. Although it's been a couple years since I've tried to compile device-specific stuff from an AOSP tree so I don't know how long that will take.
Click to expand...
Click to collapse
Glad you open this thread. I'll wait for your compiled version to give it a try
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
Click to expand...
Click to collapse
I don't know man, these adb and fastboot binaries look old (2014?). Try to get recent ones. And repeat the process.

silv3rfox said:
Glad you open this thread. I'll wait for your compiled version to give it a try
I don't know man, these adb and fastboot binaries look old (2014?). Try to get recent ones. And repeat the process.
Click to expand...
Click to collapse
Thanks, i will.

teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
Click to expand...
Click to collapse
Before flashing recovery
CD C:\Users\YOUR_USERNAME\Desktop\Adb

teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
Click to expand...
Click to collapse
The name of the file is ending with .img, delete ending " .img ", see below that patched_boot without .img in the end

Thanks for this. I checked out the differences between this and the flashable zip I was using (twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester) and found this:
Code:
# write the new boot image to boot block
write_boot() {
print "Writing new boot image to memory..."
cd "$tmp"
if $use_dd; then
dd if=boot-new-a.img of="$boot_block"_a
[ $? = 0 ] || abort "Failed to write boot image A! You may need to restore your boot partition"
dd if=boot-new-b.img of="$boot_block"_b
[ $? = 0 ] || abort "Failed to write boot image B! You may need to restore your boot partition"
else
flash_image "$boot_block" boot-new.img
fi
[ $? = 0 ] || abort "Failed to write boot image! You may need to restore your boot partition"
}
This also flashes it into boot_a and boot_b correct?
What other differences does this have over that?