Related
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..
Hi,
Could anybody tell me which are the bare minimum sources needed to compile a working cyoanogenmod 9 kernel boot.img?
I'm currently trying to compile one on my own but I can't afford to download the whole CM9 source due to the internet contract i have.
Thanks
Nobody? Ok then... May someone please copy and paste their makefile inside the root directory of his Android tree? (the one from wich they issue the command "make -j4 out/target/product/galaxysmtd/boot.img").
Maybe you could try cloning the android_build project and the teamhacksung buildscript project as well. Then adjust the buildscripts to point to the correct toolchain directory...
Boot.img contains the kernel. Therefore you need the kernel sources since at cm9 the kernel is build while compiling cm. You can find that sources at github (in project kernel_samsung_aries or something). You need to put this directory to your root directory of your android build system (there you have the device dir, frameworks, vendor etc). Rename it into kernel/samsung/aries. Then you should be able to build. It has worked like this for i9001, and it should also for i9000
You could also look at the kernel source of semaphore/devil. They use their own build script which does not require the full cm9 source, but only the kernel source. I made an adapted version of their scripts to build my own kernel...
Verstuurd van mijn GT-I9000
I think he already has:
__Pol__ said:
Nobody? "make -j4 out/target/product/galaxysmtd/boot.img"
Click to expand...
Click to collapse
Thanks everybody!
Sorry if the first two posts misled you.
I already have the kernel source. What I need are some instructions in order to build the boot.img from them. I can't download the whole source branch because I'm on a data diet .
Also a copy paste of the main make file is accepted.
I think this could help you:
http://forum.xda-developers.com/showthread.php?p=28096022
It's again for i9001 (sorry, but I own one ), but should also work
I think this could help you:
http://forum.xda-developers.com/show...php?p=28096022
It's again for i9001 (sorry, but I own one ), but should also work
Click to expand...
Click to collapse
Thanks. I've already tried the split_bootimg.pl but it did not work. According to sbuild.sh from semaphore kernel what i need to do is just "cp bzImage boot.img". I had already done it before but my phone did not boot up. It showed the bootloader logo but then nothing so something is wrong with the initramfs. Is the one included with the kernel sources correct or am I missing something?
So you can build the kernel? And just copying the kernel image to boot.img won't work. As you can see in the splitted boot.img from arco or anyone else, there are some other things needed.
I think you need to split it, replace the kernel image (zImage I thinl) and put all files again together (including the other files from the working boot.img).
No warranty on that, but that's what I understood
hahnjo said:
So you can build the kernel? And just copying the kernel image to boot.img won't work. As you can see in the splitted boot.img from arco or anyone else, there are some other things needed.
I think you need to split it, replace the kernel image (zImage I thinl) and put all files again together (including the other files from the working boot.img).
No warranty on that, but that's what I understood
Click to expand...
Click to collapse
Actually I can't split the boot.img because split_bootimg.pl does not work. The problem is in the initramfs and that is why I was asking for some advice about the sources needed. The auto-generated initramfs does not work.
__Pol__ said:
Actually I can't split the boot.img because split_bootimg.pl does not work. The problem is in the initramfs and that is why I was asking for some advice about the sources needed. The auto-generated initramfs does not work.
Click to expand...
Click to collapse
When I tried it, it worked... Are you sure that you have Pearl installed. Which OS do you use?
How do you generate initramfs?
I'm running Debian wheezy, pearl is installed. The script says it has not found android magic. The initramfs is automatically generated by the kernel source. I fear some files are missing here: https://github.com/CyanogenMod/android_kernel_samsung_aries
Do I need to get *bootimg from here?
https://github.com/CyanogenMod/android_device_samsung_aries-common
If yes how do I use these 2 scripts?
Sorry they're not two scripts but a script and a make file. From where does that makefile obtain the variables?
For splitting, did you use a running boot.img, e.g. from CM9 for your device?
You have two possibilities for building a running boot.img:
1) It is builded if you compile CM or AOSP or another ROM from Source (therefore you would need the complete sources)
2) You only build the Kernel and put it in an existing boot.img (for your phone of course) by just replacing the kernel.
For second you need to split an existing boot.img
Hi
Sent from my GT-S5830 using xda app-developers app
hahnjo said:
For splitting, did you use a running boot.img, e.g. from CM9 for your device?
You have two possibilities for building a running boot.img:
1) It is builded if you compile CM or AOSP or another ROM from Source (therefore you would need the complete sources)
2) You only build the Kernel and put it in an existing boot.img (for your phone of course) by just replacing the kernel.
For second you need to split an existing boot.img
Click to expand...
Click to collapse
Well, actually there's a third method. I need the initramfs source, the kernel source and the recovery source. After building I need to pack them together. Until yesterday I had only the sources for kernel and initramfs (?). Now I'll head for some sources for the recovery but I still need the main makefile (inside the Android directory) to know what commands I have to issue.
Sorry guys if I stil can't explain my problem to you. I really appreciate your patience and your helpful tips though.
You could look at devil/semaphore, as they use a complete initramfs, including recovery (both have a slightly different implementation).
Verstuurd van mijn GT-I9000
kasper_h said:
You could look at devil/semaphore, as they use a complete initramfs, including recovery (both have a slightly different implementation).
Verstuurd van mijn GT-I9000
Click to expand...
Click to collapse
Yep! I had a look there and I understood I was missing the recovery. Semaphore uses a custom amde initramfs and recovery whith load of scripts I don't need. I downloaded the CWM source from cyanogenmod git. There is only an Android.mk that obviously won't work. The question still remains: has anybody here downloaded the whole cyanogenmod source? If yes, may they post the makefile here please?
I have the whole CM sources, CM7 and CM9. Atm I can't access them because I'm on travel. I will return next week, maybe then.
Though, I think that it is impossible to extract the needed Makefiles. The Main-Makefile includes another makefile, but from then on several files are included which include again files. I stopped trying to understand it after the first 3 files...
I'm trying to build https://github.com/oneplusoss. I've generated vendor blobs from 3.5.4 full ota zip, because it can't work to access /system via adb pull on user builds (would need a rooted user-debug build in order to fetch all blobs). You can find the final blob collection here: https://github.com/nvertigo/android_vendor_oneplus_oneplus3T
I have massive issues to get device/qcom/hammerhead-kernel (2Mbit with consistent connectionmdrops), so I <remove-project .... /> that one, since that's prebuild kernels for hammerhead. Do I need some dtds from that git?
The build process runs fine (build.sh -c, as well as make, as well as make otaimage). But I can't get it boot far enough (with boot.img-nosecure) to get any logs: it starts with the oneplus-logo (not the three dot animation) the capacitive buttons show their lights, went off again and after about 10 s the device reboots to recovery. Any way I flash the source build rom (fastboot flash or flashing the ota-package via twrp shows the same results.
Sadly neither boot.img nor boot.img-nosecure give me a /proc/last_kmsg...
Any ideas are appriciated. Thanx in advance.
An other question: does the capacitive buttons light indicating extracting ramdisk? That would match my obsevation, that they are switched on longer on twrp boot, then on system boot, since recovery ramdisk is larger.
If someone wonders, why I are trying this: it's not for engancing features, but for two reasons: because the source is there, and because I'm an oldschool gentoo dickhead: what hasn't run through my compiler shouldn't be on my device (also some kind of chain of trust... ).
Been there, done that, have the t-shirt:
finally I got oss to boot: problem was missing f2fs support for data in fstab. It's running fine and srable.
I naivly thought, it's the source of oos - but it's not: it's plain aosp without any custumation (besides it's running on 3t and some codeaurora parts). No file manager, no capacitive buttons, no no-disturb-button-support, really insane AAPT comfiguration (elements and onscreen-buttons [as stated: no capacitive buttons availible]mare that large, that it feels like an htc magic on steroids).
But: it's a working codebase.
For me the most important finding is the camera used on oss: it's codeauroras snapdragon camera. I pulled the apk and 4 libs, and it's working on oos. If anybody is interested, I can make a flashable zip. Since I'm no photographer, I'm not the one to judge the quality and playing with manual options. The snapshots with default settings are as good (or as bad - YMMV) as with oos stock cam.
I Thing they need to put more features in one plus 3 OS cause there is lil bit heavy smartphone so they need to do more additions
harshsharma9619 said:
I Thing they need to put more features in one plus 3 OS cause there is lil bit heavy smartphone so they need to do more additions
Click to expand...
Click to collapse
Watch out to not confuse oos (oxygenos: proprietary closed source with quitemsome features; i.e. capacitive buttons) with oss (OnePlusOpenSourceSoftware: castrated aosp without anything).
For more features: I'm looking very forward to lineageos, when M kernelsources are published by oneplus.
SnapdragonCamera for OxygenOS
Packaged:
https://forum.xda-developers.com/oneplus-3t/themes/apk-snapdragoncamera-codeaurora-build-t3533687
nvertigo67 said:
I've generated vendor blobs from 3.5.4 full ota zip, because it can't work to access /system via adb pull on user builds ...
Click to expand...
Click to collapse
How do you extract the files from the OTA zip? Of course I know how to unzip a file but I mean how to get the actual files out of the image files. Can this be done with basic Linux Tools?
freepenguin84 said:
How do you extract the files from the OTA zip? Of course I know how to unzip a file but I mean how to get the actual files out of the image files. Can this be done with basic Linux Tools?
Click to expand...
Click to collapse
unpack the rom (you need unpackbootimage - either from your dist, or from android sdk); unpack system.new.dat (sdat2img.py - from your dist, or search with google, don't know if this is in sdk); mount system.img somewhere; edit pull_library.sh from adb pull to cp.
This pull_library.sh is for oss from end of february, you have to edit the current one and - of course - have to change the source of the cp command to meet your local paths:
https://github.com/nvertigo/local_manifest/blob/oneplus/oneplus3t_N/pull_library.sh
Whatever I do, my custom build kernels fail to boot. There's the ZUK logo very briefly, then device drops to bootloader screen. I'm out of ideas what I'm doing wrong, maybe someone here can give me a hint. :good:
I've tried with current AEX kernel git snapshot and also stock kernel sources. Building using the AEX_defconfig goes ok, I have Image.gz, replace it in previously extracted "stock" boot image and use mkbootimg.py to rebuild the new image. Offsets etc. are all correct (I think), like this: (from AEX)
Code:
kernel=kernel
ramdisk=ramdisk
page_size=4096
kernel_size=9101281
ramdisk_size=2671109
base_addr=0x80000000
kernel_offset=0x00008000
ramdisk_offset=0x01000000
tags_offset=0x00000100
cmd_line='androidboot.hardware=qcom ehci-hcd.park=3 lpm_levels.sleep_disabled=1 [email protected] buildvariant=userdebug'
board=""
format=gzip
But the damn new image won't boot, like described above. There has to be something (probably very stupid) I'm missing...
If I replace my own Image.gz with the originally extracted one and mkboot and so on, it's ok. So I guess it has something to do with my kernel build and/or environment. Are there any subsequent steps needed to do with the compiled kernel Image.gz? Or is it just my kernel config which is wrong? But I'm using the AEX defconfig (n7x-caf_z2_row_defconfig, to be exactly) so this should be fine, no?
Ok, I've got it. I had forgottten (=didn't know about at all) to append the device tree blob (arch\arm64\boot\dts\qcom\msm8996-v3-pmi8996-mtp.dtb) to kernel zImage... Simply cat'ing these together works!
Goodluck bro.
void23 said:
Ok, I've got it. I had forgottten (=didn't know about at all) to append the device tree blob (arch\arm64\boot\dts\qcom\msm8996-v3-pmi8996-mtp.dtb) to kernel zImage... Simply cat'ing these together works!
Click to expand...
Click to collapse
please explain .. what exactly i need to do with that file..
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?