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..
Related
INTRODUCING TWEEZERMOD INSTALLER
Not for the new bootloader. Make sure you are on the old bootloader.
There are two ways to use Tweezermod now!
-Desktop Version
-Cordless version (Directly from the Kindle itself!)
**WARNING**
YOU MUST HAVE ROOT ALREADY ON YOUR KINDLE FIRE 2
Just because this does not require a fastboot cable, does not mean you should not have one! Please know that there is always a chance for things to go wrong when you modify your device, and the only sure-fire way to fix things is with a fastboot cable!
Info
Tweezermod installer is an application including freedom-boot.img and TWRP for KF2. It runs a script.sh written by me, and derived from my desktop script, which was in turn derived from my method of getting CM10.1 on my own KF2 without a fastboot cable.
This package will automatically install the freedom-boot bootimage and TWRP recovery built by Hashcode.
I have tested this myself multiple times, and it is based on the method that I used the first time I installed CM10.1 prerelease on my KF2.
Installation
Desktop
Instructions:
Download
Unzip
Run the runme.sh or .bat depending on your operating system
Profit
Download:MOD EDIT LINK REMOVED
Cordless (APK)
Instructions:
Download
Install on your KF2
Open Tweezermod Installer
Press install
Grant su access
Profit
Download:MOD EDITcom.powerpoint45.FMKilo-2.apk - 10.48 MB
MD5:add2c3cb1aa1e80dfa0644ea06207a0d
If all goes well, you will see a switch from the orange Kindle Fire bootlogo to a blue one with a menu at the bottom!
Additional Info
This method uses dd to write the recovery and boot partitions, so no fastboot driver needed on windows.
If necessary, you may need to grant superuser access to adb. (You will see the superuser popup on your Kindle)
Some linux users may need to run the .sh as root.
Roms
You may have done everything here successfully at this point, BUT you will still need to choose and install a ROM. Here are the two out so far to choose from. Both have guides with them on how to install.
Powerpoint45's MooRom (With SGT7!)
Hashcode's CM10.1 Base ROM
Disclaimer:
This package comes with no warranty, nor do you have the right to sue me or my affiliates because something went wrong, and you have a brick.
If you modify this script, and you end up with a brick, I will advise everyone not to help you with your idiocy.
You are welcome to reproduce this package in its entirety, not in bits and pieces.
I did not make nor do I own the rights to the kernel or the recovery in the package.
Support:
Support for this package is offered 25/8 (whenever I'm online) either on this thread, or better yet, on freenode irc #kf2-dev
For in thread support that requires the output of the script, please use pastebin.com to post the output, and post a link to it here.
Credits:
Hashcode -- CM10.1 for KF2, Freedom-Boot, TWRP for KF2
Powerpoint45 -- Tablet UI rom for kf2, Primary tester for Hashcode, wrote and compiled tweezermod installer
FMKilo -- Figured out how to get to fastboot without a cable, Wrote cableless script, script for tweezermod installer(I commissioned him)
Special Thanks:
MisterSir69 -- Alerted me to the brick created by Desktop Script V1
DiscoGecko -- discovered the problem with and helped fix Desktop Script V4 on windows
iytrix -- Did this fancy pants layout for all the info stuff
FAQ:
Q: Why the name Tweezermod?
A: Tweezermod is a reference to the first fastboot cable I used. it was just an opened up cable, with a wire spliced into pin one. I used a pair of tweezers to contact pin 4, the one that sends the device into fastboot. Pin 4 is ironic because issuing the command idme bootmode 4 from an elevated terminal or adb shell will send the device into fastboot mode upon reboot. The only way to get out of fastboot after this is by issuing the command, fastboot -i 0x1949 oem idme bootmode 1, which reboots to system upon fastboot -i 0x1949 reboot(perhaps it is ironic in the opposite way).
The name Tweezermod is ironic in the fact that you never go to fastboot whilst installing cm by the use of the .apk or the Desktop Script.
Old Versions
Old versions are only included so you can examine them and see what exactly was changed. Please always use the current version linked in the first post.
Desktop Script
V1:BRICK WARNING DO NOT USE!
MD5: fa65668bd268d48ca1c0e563fdf07169
V2:KF2CM10.zip - 10.30 MB
MD5:4156e28006386b6c96c9190abf071b80
V3:KF2CM10.zip - 11.23 MB
MD5:25a01c57280af427091924ebe365d0ef
V4:KF2CM10.zip - 11.23 MB
MD5:e3d5aecfa2f563ded5e7bcbd3b132a7e
V5:KF2CM10.zip - 11.23 MB
MD5:c1b7703ffe1b15eeac70bbfb265646ae
V6:KF2CM10.zip - 11.24 MB
MD5:aa2b4da68fcb6f8e77ef5fc391ef30ca
Tweezermod Installer
V1:AlienBox (2).apk - 10.45 MB
MD5:ead9d23cd12e877c267adf19c243d3ae
V2:Tweezermod_Installer.apk
MD5sum: 4f2f6c805e4d28476b409a8b30fe16ca
V3:Tweezermod_Installer2.apk - 10.47 MB
MD5:1e7b518f0ad0c9d4c133cc2acd388d23
V4:com.powerpoint45.FMKilo-2.apk - 10.48 MB
MD5:add2c3cb1aa1e80dfa0644ea06207a0d
Changelog
Desktop Script
V1: Bricks(if you don't want them, throw them through my window, I can fix it...)
V2: No longer tries to create stack using adb shell, stack is now included in the archive.
V3: Adb now included for those of you who did not modify your $PATH. Also added @echo off to .bat and rearranged archive
V4: Removes install-recovery.sh and recovery image in the system partition of the stock rom.
V5: Fixed for windows. No update for linux users.
V6: Added new freedom-boot.img, now with fastboot in secondary bootloader. No need for -i 0x1949 flag.
Tweezermod Installer
V1: Actually works, in launcher, it is named Main Activity launch and grant access.
V2: Tweezermod Installer. Install this apk on your kindle fire2 press install and no profit from a system rom that won't delete twrp, secondary bootloader, and a fully functional twrp. (Roms not included.) APK by powerpoint45, script inside by me.
V3: Fixed the directory issue within V2, should work now.
V4:Added new freedom-boot.img, now with fastboot in secondary bootloader. No need for -i 0x1949 flag.
This package will be updated if any changes are made to the freedom-boot or TWRP recovery by Hashcode.
I AM OFFICIALLY DONE TRYING TO HELP ANYONE WHO USES KFU ON THEIR KF2, DO THE RESEARCH FIRST, THEN ATTEMPT THE MOD.
Downloaded this and ran the runme, Now im in bootloop. Screen just keeps flashing Kindle Fire.
Reserved
same thing! just stuck in bootloop! How do I fix this?
grantpatrickfarrell said:
same thing! just stuck in bootloop! How do I fix this?
Click to expand...
Click to collapse
the same way he did.
Just purchased a fast boot cable. Needed it anyways. Hopefully by time it comes all the bugs will be worked out.
fmkilo said:
the same way he did.
Click to expand...
Click to collapse
grantpatrickfarrell said:
Just purchased a fast boot cable. Needed it anyways. Hopefully by time it comes all the bugs will be worked out.
Click to expand...
Click to collapse
If you ordered one from SkOrPn, it should be there within the week, if you ordered one from hong kong, expect it within the month
i got this to work, but i had to run the script multiple times to finally boot into recovery. the first time i ran it the bootloader just said "booting..." forever and never booted into recovery. the second time i ran it, it booted right into recovery, but when i loaded .zips to flash and tried to boot back into recovery i just got "booting..." forever again, so i ran the script a third time and was able to boot into recovery to flash a new rom. either way, it works and you're awesome. thanks a lot.
755 said:
i got this to work, but i had to run the script multiple times to finally boot into recovery. the first time i ran it the bootloader just said "booting..." forever and never booted into recovery. the second time i ran it, it booted right into recovery, but when i loaded .zips to flash and tried to boot back into recovery i just got "booting..." forever again, so i ran the script a third time and was able to boot into recovery to flash a new rom. either way, it works and you're awesome. thanks a lot.
Click to expand...
Click to collapse
Hashcode is addressing the issues with the booting into the twrp
fmkilo said:
Hashcode is addressing the issues with the booting into the twrp
Click to expand...
Click to collapse
Awesome.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Good news some questions first do i need root from the start i have a fresh new kindle and i just need standard cable and the programme and new rom seems to root is a bit harder than my mobiles
Sent from my GT-I9100 using xda app-developers app
dannyling said:
Good news some questions first do i need root from the start i have a fresh new kindle and i just need standard cable and the programme and new rom seems to root is a bit harder than my mobiles
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
you need to use the root with restore method and the qemu root method to root this device first, then come back here.
fmkilo said:
Hashcode is addressing the issues with the booting into the twrp
Click to expand...
Click to collapse
turns out, most of the problems with booting into twrp were actually people letting their devices boot stock os, without anyone realizing that there was an install-recovery.sh that would break twrp. This has been fixed in the latest version of computer one click and also tweezermod_installer.apk
fmkilo said:
turns out, most of the problems with booting into twrp were actually people letting their devices boot stock os, without anyone realizing that there was an install-recovery.sh that would break twrp. This has been fixed in the latest version of computer one click and also tweezermod_installer.apk
Click to expand...
Click to collapse
Great, so how do I know it worked and how do I boot into recovery?
Does terminal emulator work to get to twrp?
Su
Reboot recovery
Installed the apk and ran it, but nothing seems to be changed..when i su reboot recovery it doesnt boot into twrp..
What about hd
Hondologe said:
Installed the apk and ran it, but nothing seems to be changed..when i su reboot recovery it doesnt boot into twrp..
Click to expand...
Click to collapse
Does you get an orange or blue kindle fire logo when you boot.?
Edit: Just tried this myself. Not tried installing the recovery or modded boot before, and I'm not seeing a blue kindle fire logo.
The latest apk doesn't seem to work yet.
Sent using my Jelly Atrix.
restlessrob said:
What about hd
Click to expand...
Click to collapse
I mean does this work on kindle fire hd
Welcome to Lollipop
Clean install with custom recovery (TWRP) (recommended)
Download the following files:
aosp_mako-ota-eng.5.0.zip or aosp_mako-ota-eng-preroot.5.0.zip (if you want to have root*) (mirrors, thanks to dorqus)
* In case you have already downloaded aosp_mako-ota-eng.5.0.zip you can also flash aosp_mako-boot-root.5.0.zip to prepare for root
optional: BETA-SuperSU-v2.19.zip
defcon-L-gapps-v2.zip
Recommended: Backup your apps:
Code:
adb backup -apk -obb -all -system
Recommend: Backup your internal storage (see FAQ below for the reason). Either copy all files in Explorer or use adb:
Code:
adb pull /sdcard/
Boot to recovery
Recommend: Factory reset. Warning: All your apps and app data will be deleted! Make sure you have a backup!
Recommend: Format/wipe internal storage (see FAQ below for the reason). Warning: All your files will be deleted! Make sure you have a backup!
Format/wipe system
Unmount system
Install aosp_mako-ota-eng.5.0.zip (or aosp_mako-ota-eng-preroot.5.0.zip)
Install gapps-lp-20141105-signed.zip
Optional: Install BETA-SuperSU-v2.19.zip
Reboot
Have a break and don't panic! The first boot can take 5 to 10 minutes
Optional: Recover from backup:
Code:
adb restore backup.ab
Optional: Copy your files back to internal storage
Clean install with fastboot
You won't have GApps this way ...
WARNING: If you flash userdata.img, all your data will be gone! Even the files on internal storage!
Download the images
boot.img or boot-root.img (prepared for root, you still have to install SuperSU somehow...)
system.img
Optionalrecovery.img
Optional, should be empty: cache.img
Optional, should be empty: userdata.img
Boot to bootloader
Flash
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
FAQ
Oh no, all my files are lost!!!
or
Why should I wipe internal storage?
5.0 uses a much stricter SELinux policy than most 4.4 ROMs do. Normally the first boot should migrate all the things (and it did for me, but only the first time). If not, you are no longer able to see your internal storage (aka SD card). E.g. Camera says: Please enter an SD card. To fix that problem you have to either wipe the internal storage and let Android recreate the file structure. (You can before still access the /sdcard in TWRP for a backup with adb). Or you can fix the SELinux context with the following command (in recovery):
Code:
adb shell
IFS="
"
for i in `find /data/media`; do chcon u:object_r:media_rw_data_file:s0 "$i"; done
Is this the official update from Google?
No, this is an AOSP build from the latest Lollipop sources.
Do I need to be on stock 4.4.4 before flashing?
No, but you should consider doing a factory reset otherwise.
Can I do a dirty upgrade?
Yes, you can. But you might spend a lot of time in fixing F/Cs...
Can this ROM be rooted?
Yes, just flash aosp_mako-ota-eng-preroot.5.0.zip (or aosp_mako-boot-root.5.0.zip) and BETA-SuperSU-v2.19.zip
Known issues
General:
No access to internal storage, even not with adb or as root. Seems like SELinux is misconfigured. See FAQ for solution
Due to incomplete GApps:
WLAN/mobile based location isn't working
No face unlock (libs missing) works with new gapps
calendar sync provider missing works with new gapps
How to build
This ROM is build with the original Google sources:
Code:
repo init -u https://android.googlesource.com/platform/manifest -b android-5.0.0_r2
See https://source.android.com/source/building.html for build instructions.
Binary blobs are taken from https://developers.google.com/android/nexus/blobs-preview.
The kernel is the default precompiled kernel provided by Google (can be found in device/lge/mako-kernel/kernel).
To prepare for root, you have to remove the seclabel line from system/core/rootdir/init.rc:
Code:
service flash_recovery /system/bin/install-recovery.sh
class main
seclabel u:r:install_recovery:s0
oneshot
C-o-M said:
Welcome to Lollipop
Download: https://drive.google.com/file/d/0B10l7w-7w3boRzlmT1pxSFF5YlU/view?usp=sharing
We don't have 5.0 gapps yet, so I flashed pa-gapps-modular-mini-4.4.4-20140930 (after removing the version check in updater-script). Works great so far.
I'm running a dirty upgrade from 4.4.4, no issues so far. Just format /system, flash ota.zip and gapps, wipe cache and enjoy.
Click to expand...
Click to collapse
I guess this requires me to be running stock 4.4.4 before flashing.
Could you post the system.img , userdata.img , cache.img , boot.img and recovery.img so I could flash it via fastboot.
Thanks
Amazing work!!
can you upload modified pa gapps??
or any instruction to modify it?
Good job!
trasteando...
is this from google ?
richardyusan said:
is this from google ?
Click to expand...
Click to collapse
all ROM's are from Google's base dude
maybe what you really mean is from stock L image?
is this rooted guys?
Is this official aosp build and can I clean flash?
Please explain how to root tris ROM?!
C-o-M said:
Welcome to Lollipop
Download: https://drive.google.com/file/d/0B10l7w-7w3boRzlmT1pxSFF5YlU/view?usp=sharing
We don't have 5.0 gapps yet, so I flashed pa-gapps-modular-mini-4.4.4-20140930 (after removing the version check in updater-script). Works great so far.
I'm running a dirty upgrade from 4.4.4, no issues so far. Just format /system, flash ota.zip and gapps, wipe cache and enjoy.
Click to expand...
Click to collapse
dirty flash from stock 4.4.4 ?
also can you provide a link to working gapps
great job , waiting issues from other
groovepeppy said:
all ROM's are from Google's base dude
maybe what you really mean is from stock L image?
Click to expand...
Click to collapse
lol you don't say
we know every android build is from google
is this official from google or not?
richardyusan said:
lol you don't say
we know every android build is from google
is this official from google or not?
Click to expand...
Click to collapse
It's in the topic dude.
AOSP not OTA
Bladyle said:
It's in the topic dude.
AOSP not OTA
Click to expand...
Click to collapse
What he means is this proper aosp fully working 100% and has latest kernel and everything?
SRun said:
What he means is this proper aosp fully working 100% and has latest kernel and everything?
Click to expand...
Click to collapse
it will be 100% working when we have OTA or after some time with AOSP when developers fix all the missing binaries, libraries, bugs and etc.
SRun said:
What he means is this proper aosp fully working 100% and has latest kernel and everything?
Click to expand...
Click to collapse
i think we should install the rom and experience
Bugs? Root? Smooth? Please post bugs and stuff
I'm returning to stock 4.4.4 as I type this, and then I will do a clean flash of this 5.0 AOSP build and see how I go. Shall report back here upon completion.
richardyusan said:
lol you don't say
we know every android build is from google
is this official from google or not?
Click to expand...
Click to collapse
understood "sam"
that's why i wrote "maybe what you really mean is from stock L image?"
how to i disable the version check to install gapps?
anyway to get the official launcher? the one in this rom looks like 4.4 stock
can someone please upload the stock "install-recovery.sh"?
It's located in /system/etc.
I forgot to backup it, while rooting the device.
I need it for the OTA updates.
thanks
@vel_tins
Do not flash the ota if you are rooted, you might get bootloop. Full unroot your device before attempting to update. Anyhow, the ota will most likely fail since you already modified your system partition. Your best option is to unroot your device and capture the ota link, modify the ota updater-script and remove the lines that are showing "unexpected contents" errors. The original "install-recovery.sh" is still there, supersu renamed it to something like "/system/etc/install-recovery_original.sh". Keep in mind, you might loose your custom recovery if you renamed it back to "install-recovery.sh".
Well, OTA was a pain in the a**.
Because I had no stock "install-recovery.sh", I've edited the updater-script and removed all the matching entries.
Executed a full un-root.
Tried to flash the modified update.zip via TWRP, but failed because TWRP couldn't mount partitions with this name scheme:
Code:
"/dev/block/platform/[B]7824900.sdhci/by-name/system[/B]", "/system",
(will investigate later, any ideas?)
Because too lazy to modify the updater-script again,
I've booted into fastboot and loaded my "modded" stock recovery, which accepts also self-signed .zips.
Flashing worked well, but on reboot, I got a nice bootloop because of the formerly installed Xposed framework.
Had to restore from a Nandroid Backup and after reboot, I removed Xposed completely.
Eventually, I was able to flash the OTA and got back a working device...
Gosh...
^^
??
vel_tins said:
Well, OTA was a pain in the a**.
Because I had no stock "install-recovery.sh", I've edited the updater-script and removed all the matching entries.
Executed a full un-root.
Tried to flash the modified update.zip via TWRP, but failed because TWRP couldn't mount partitions with this name scheme:
Code:
"/dev/block/platform/[B]7824900.sdhci/by-name/system[/B]", "/system",
(will investigate later, any ideas?)
Because too lazy to modify the updater-script again,
I've booted into fastboot and loaded my "modded" stock recovery, which accepts also self-signed .zips.
Flashing worked well, but on reboot, I got a nice bootloop because of the formerly installed Xposed framework.
Had to restore from a Nandroid Backup and after reboot, I removed Xposed completely.
Eventually, I was able to flash the OTA and got back a working device...
Gosh...
Click to expand...
Click to collapse
If you still have the original OTA zip, can you please post it for future reference?
As for TWRP mounting /dev/block/platform/7824900.sdhci/by-name/system, what error message did you get? Try running "ls -l /dev/block/platform/7824900.sdhci/by-name/" in both normal Android and TWRP, then compare the results.
pawitp said:
If you still have the original OTA zip, can you please post it for future reference?
Click to expand...
Click to collapse
No problem
pawitp said:
As for TWRP mounting /dev/block/platform/7824900.sdhci/by-name/system, what error message did you get? Try running "ls -l /dev/block/platform/7824900.sdhci/by-name/" in both normal Android and TWRP, then compare the results.
Click to expand...
Click to collapse
Stock and Cyanogen recovery are working with this partition naming scheme.
But in TWRP, I get the following error message:
Code:
ls: /dev/block/platform/7824900.sdhci/by-name: No such file or directory
For TWRP I have to use the following syntax in recovery.fstab:
Code:
/cache ext4 /dev/block/mmcblk0p29
/system ext4 /dev/block/mmcblk0p25
/data ext4 /dev/block/mmcblk0p31 length=-16384
.........etc.
vel_tins said:
No problem
Stock and Cyanogen recovery are working with this partition naming scheme.
But in TWRP, I get the following error message:
Code:
ls: /dev/block/platform/7824900.sdhci/by-name: No such file or directory
For TWRP I have to use the following syntax in recovery.fstab:
Code:
/cache ext4 /dev/block/mmcblk0p29
/system ext4 /dev/block/mmcblk0p25
/data ext4 /dev/block/mmcblk0p31 length=-16384
.........etc.
Click to expand...
Click to collapse
On TWRP, try running "find /dev/block/platform" and see if anything is created there.
The directory should have been populated by init. See https://android.googlesource.com/pl...0ab94b7d5a888f0b6920b156e5c6a075fa0741a^!/#F0.
That code should also be in TWRP, but something might have prevented it from working properly on this device. You might find some clues in dmesg or TWRP's logs.
Well, eventually I've got it.
In TWRP, the naming is a little bit different from stock or Cyanogen recovery.
I had to change:
Code:
/dev/block/platform/[COLOR="Red"]7824900.sdhci[/COLOR]/by-name/cache <--- STOCK
to
/dev/block/platform/[COLOR="Blue"]soc.0[/COLOR]/by-name/cache <--- TWRP
However, the "/dev/block/mmcblk0p" naming worked also in TWRP, so this was only a minor issue.
vel_tins said:
Well, eventually I've got it.
In TWRP, the naming is a little bit different from stock or Cyanogen recovery.
I had to change:
Code:
/dev/block/platform/[COLOR="Red"]7824900.sdhci[/COLOR]/by-name/cache <--- STOCK
to
/dev/block/platform/[COLOR="Blue"]soc.0[/COLOR]/by-name/cache <--- TWRP
However, the "/dev/block/mmcblk0p" naming worked also in TWRP, so this was only a minor issue.
Click to expand...
Click to collapse
IMO, you should fix TWRP so that it has the same naming convention. Otherwise OTA packages using the "stock" naming convention can't be flashed on TWRP.
Personally, I prefer the "by-name" mapping rather than the "/dev/block/mmcblk0p" because it is harder to make mistakes if you use a name. With numbers, if a wrong number is typed, then you might end up flashing the wrong partition and bricking the device.
EDIT: It might have something to do with the "system/core" repository you've used to build your recovery. Which Android tree did you use to build Cyanogen Recovery and which one did you use to build TWRP?
vel_tins said:
Well, OTA was a pain in the a**.
Because I had no stock "install-recovery.sh", I've edited the updater-script and removed all the matching entries.
Executed a full un-root.
Tried to flash the modified update.zip via TWRP, but failed because TWRP couldn't mount partitions with this name scheme:
Code:
"/dev/block/platform/[B]7824900.sdhci/by-name/system[/B]", "/system",
(will investigate later, any ideas?)
Because too lazy to modify the updater-script again,
I've booted into fastboot and loaded my "modded" stock recovery, which accepts also self-signed .zips.
Flashing worked well, but on reboot, I got a nice bootloop because of the formerly installed Xposed framework.
Had to restore from a Nandroid Backup and after reboot, I removed Xposed completely.
Eventually, I was able to flash the OTA and got back a working device...
Gosh...
Click to expand...
Click to collapse
Hi sir ,
Please share to us , how you do this , because I have status 7. Install-recovery.sh problem
I have stock recovery , and I'm only make a root for my device by kingroot .
Please share update.zip file and tel me how to make ota update
pawitp said:
IMO, you should fix TWRP so that it has the same naming convention. Otherwise OTA packages using the "stock" naming convention can't be flashed on TWRP.
Click to expand...
Click to collapse
Exactly this is the point...
pawitp said:
EDIT: It might have something to do with the "system/core" repository you've used to build your recovery. Which Android tree did you use to build Cyanogen Recovery and which one did you use to build TWRP?
Click to expand...
Click to collapse
I have to correct myself, Cyanogen has exactly the same problem.
I've used the latest CM 12.1 and Omnirom source trees to build TWRP, but with the same result.
TWRP/Cyanogen only detects "soc.0" instead of "7824900.sdhci" and that will break compatibility with OTA packages (Until you patch "updater-script").
So how you made this ota update after all ?
theeteempire said:
So how you made this ota update after all ?
Click to expand...
Click to collapse
OTA doesn't work with rooted devices.
Do a full un-root and try again.
vel_tins said:
OTA doesn't work with rooted devices.
Do a full un-root and try again.
Click to expand...
Click to collapse
I did it , full unroot , I couldn't update even that with full-unroot , I used kingroot for root ,
Also error status 7 , install-recovery. Sh shown on the update after full-unroot my device !!!
can you help me please !!!!!
theeteempire said:
....I used kingroot for root ,
Also error status 7 , install-recovery. Sh shown on the update after full-unroot my device...
Click to expand...
Click to collapse
I would strongly suggest, to open an new thread, because I guess a lot more people will or had run into these issues.
I don't know what Kingsoft (never used it) has modified/replaced, so in your case I would search for a stock "install-recovery.sh" and replace the modified.
Everything else would be too complicated. (You have read my post on the first page).
vel_tins said:
I would strongly suggest, to open an new thread, because I guess a lot more people will or had run into these issues.
I don't know what Kingsoft (never used it) has modified/replaced, so in your case I would search for a stock "install-recovery.sh" and replace the modified.
Everything else would be too complicated. (You have read my post on the first page).
Click to expand...
Click to collapse
So I need the stock install-recovery. Sh ,.
Are you have it ?
vel_tins said:
Exactly this is the point...
I have to correct myself, Cyanogen has exactly the same problem.
I've used the latest CM 12.1 and Omnirom source trees to build TWRP, but with the same result.
TWRP/Cyanogen only detects "soc.0" instead of "7824900.sdhci" and that will break compatibility with OTA packages (Until you patch "updater-script").
Click to expand...
Click to collapse
This is just a guess. Try adding "TARGET_PLATFORM_DEVICE_BASE := /devices/soc.0/" to BoardConfig.mk.
If you know C, you might want to try mucking around in system/core/init/devices.c and see why it's behaving that way.
pawitp said:
This is just a guess. Try adding "TARGET_PLATFORM_DEVICE_BASE := /devices/soc.0/" to BoardConfig.mk.
.....
Click to expand...
Click to collapse
Seems to work, thanks!
PS: A google search for "TARGET_PLATFORM_DEVICE_BASE" threw only six results, so it doesn't seem to be a very popular flag.
vel_tins said:
Seems to work, thanks!
PS: A google search for "TARGET_PLATFORM_DEVICE_BASE" threw only six results, so it doesn't seem to be a very popular flag.
Click to expand...
Click to collapse
From my experience, you can't rely too much on Google for ROM development. I've found the flag by reading the source file I've previously mentioned.
Sent from my Nexus 4 using XDA Free mobile app
All CM13 and RR releases we have so far are using pretty old China Dev MIUI v.6.6.30 as base not even listed on Xiaomi Downloads anymore. This as some of us know is the cause of all bugs we've had with these custom ROMs and were fixed by replacing vendor files from newer MIUI versions. On top of that some helium users cannot reboot to recovery from Android, phone doesn't power off... things like that... which most likely is due to using the wrong hydrogen kernel in this builds. Some users including me are experiencing no data going thru on good connection... Not gonna even mention VoLTE etc. So we still have bugs...
The vendor files and kernel that comes from MIUI as base are the main part that makes the hardware working flawlessly with the Android OS. These files are proprietary files with closed code, we can't change them so we have to rely on whatever Xiaomi do to optimize device performance. But we can choose which version to use and that is my goal here... Test and find the best set that works with custom ROMs.
Here we go... I have been testing the latest Global MIUI as base for two days now and so far haven't seen any issues at all. That doesn't mean no bugs... More time and testing is needed. But at least they are not any worst than what we are using now.
The common sense and logic is(fixed bugs proved that) vendor files and kernel from latest stable Global MIUI for the particular device should have more bug fixes and optimizations for the world out of China(I hope)... So using the best of my knowledge I compiled these two sets for:
HYDROGEN:
Based on latest Mi Max official Global MIUI v.8.0.1 (miui_MIMAXGlobal_V8.0.1.0.MBCMIDG_3657fef420_6.0.zip)
Download: vendor-base801MG_update-HYDROGEN.zip
HELIUM:
Based on latest Mi Max Prime official Global MIUI v.8.0.3 (miui_MIMAX652Global_V8.0.3.0.MBDMIDG_2da4c7e9db_6.0.zip)
Download: vendor-base803MG_update-HELIUM.zip
These packages are not recovery flashable zips!!! Keep reading for install instructions!
The install will get all vendor proprietary files I know of, firmware and kernel properly updated for the device code. Let's hope we get the better and latest from Xiaomi...
INSTALL INSTRUCTIONS:
MAKE TWRP BACKUP OF SYSTEM AND BOOT PARTITIONS BEFORE ANYTHING TO REVERS CHANGES IF YOU NEED TO!!!
The installation process is a little bit involving due to replacing the kernel in the actual installed boot.img in your device. I can't supply universal updated boot.img because they might be different from one release to another. I want to update what you already have. Did my best to make it user-friendly as I can without coding special app or something. Thanks to this guy whoever he is for the boot.img tools https://github.com/xiaolu/mkbootimg_tools.
Follow the steps and you should be fine:
1. Download the appropriate zip for your device code and unzip it to the root of your internal storage. You should end up with /sdcard/vendor_update folder;
2. Open your favorite terminal emulator app and execute the following commands one at a time pressing ENTER after each line:
Code:
su
hit ENTER
Code:
cp /sdcard/vendor_update/vendor-updater.sh /data/local/tmp/
hit ENTER
Code:
chmod 777 /data/local/tmp/vendor-updater.sh
hit ENTER
Code:
sh /data/local/tmp/vendor-updater.sh
hit ENTER
Alternatively you can USB connect your phone to computer and run the same commands from adb shell.
For HYDROGEN users:
That's all you have to do. The script will update your kernel and automatically will reboot phone to recovery and update vendor files so save your work before running the commands!
For HELIUM users:
Due to that can't reboot recovery bug you have to reboot manually by holding POWER and VOLUME+ buttons or fastboot method... The vendor zip will be flashed automatically and phone reboots back to system. If not, install /sdcard/vendor_update/vendor_update-HELIUM.zip manually and that's it.
Simple stuff if you decide to test these packages...
To verify update you should see kernel and baseband versions in About Phone changed like in the attached hydrogen screenshot. I can't test helium so they might be a little different. Check WiFi also... If you can turn it on and works all is good...
Helium users see if you can reboot to recovery from Advanced Power Menu, check if you can Power OFF your phone etc... the usual bugs.
Let see if these updates change anything for good or bad.
Happy testing!:good:
EDIT: Looks like 3G bug is still present in latest MIUI modem files. Flash CM_3G_fix.zip and keep the rest of the update if 3G bug is back.
Thanks a lot.
You are welcome!
Please guys lets not quote the whole OP... It takes so much screen...
No success
Maybe my fault on terminal.
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
JulianJenner said:
No success
Maybe my fault on terminal.
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
Click to expand...
Click to collapse
Maybe not... Give me a mnute...
That's what happens when you code unix script on windows and forget to convert it.
@JulianJenner
EDIT: FIXED(i think)...Try now and let me know it works or not!? Helium feedback appreciated...
I'm enthusiastic.
But I do not understand it.
I did what you said.
I used a terminal emulator from Play Store I just copied your text.
JulianJenner said:
I'm enthusiastic.
But I do not understand it.
I did what you said.
I used a terminal emulator from Play Store I just copied your text.
Click to expand...
Click to collapse
Did you redownload the fixed zip? Do you have the "/sdcard/vendor_update" folder with the files in it?
Make sure you copy text line by line hitting ENTER after each one!!! That's 4 lines... su... cp... chmod... sh...
Hydrogen works for me... Can't test helium unfortunately...
Terminal running successfully.
Phone reboot.
But my BB and Kernel version did not changed...
Yours Mon Aug 29
Mine Wed Jun 29
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
JulianJenner said:
No. I will download again. A.S.A.P.
---------- Post added at 11:18 PM ---------- Previous post was at 11:01 PM ----------
Working.
It was my fault.
"...line by line hitting ENTER after each one..."
Firstly I did not understand it.
I pressed Enter after at the end once...
Click to expand...
Click to collapse
Phew... I thought I screwed up again...
Run this in terminal emulator:
Code:
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
Upload /sdcard/boot.img somewhere... I will update kernel and you will flash it... Let see if version changes. Maybe Xiaomi haven't updated helium kernel yet!? But it is definitely different from the hydrogen latest one byte by byte...
Baseband was probably already updated if you are running ajsmsg78's RR.
I did.
Upload...
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
JulianJenner said:
I did.
And now?
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
Click to expand...
Click to collapse
Go to sdcard and you will find boot.img in there, upload it somewhere and give me the link...
Ok. I see. Upload.
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
JulianJenner said:
Ok. I see. Upload.
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
Click to expand...
Click to collapse
Just checked helium kernel with hex editor and the date is Fri Sep 2 23:22:31 CST...
Have no idea why it didn't update since script did not throw any error, right? Did the phone reboot to recovery and flashed the vendor zip?
Mister-Master! There is: http://www.mediafire.com/file/62bqqlrajr76kz6/boot.img
Did the phone reboot to recovery and flashed the vendor zip?
Click to expand...
Click to collapse
NOPE!
OK. I think solved.
Ran script again in adb shell.
And when phone try to reboot recovery.
Stopped it.
Reboot in Fastboot mode.
Type 'fastboot boot recovery.img'
Phone booted in TWRP
And your update installed successfully.
Thanks a lot!
JulianJenner said:
Mister-Master! There is: http://www.mediafire.com/file/62bqqlrajr76kz6/boot.img
NOPE!
Where is this vendor zip ( okay, I find it. vendor_update-HELIUM.zip)? Can I flash it from TWRP?
I have stock recovery, I used TWRP from Fastboot mode 'fastboot boot recovery.img' command...
Click to expand...
Click to collapse
Yes you can but first kernel has to get updated or wifi won't work.
And thats not the point... I want to see why script did not do the job but I will debug it with someone else...
Here is updated kernel link removed
Download it to /sdcard/boot_updated.img and run this in terminal:
Code:
su
hit enter
Code:
dd if=/sdcard/boot_updated.img of=/dev/block/bootdevice/by-name/boot
hit enter
After that reboot to recovery and flash that vendor_update-HELIUM.zip
Post versions, please...
OK. I think solved by myself.
Ran script again in adb shell.
And when phone tried to reboot recovery.
I stopped it with buttons.
Reboot in Fastboot mode with buttons.
Type 'fastboot boot recovery.img'
Phone booted in TWRP
And your update installed successfully.
Thanks a lot!
JulianJenner said:
Mister-Master! There is: http://www.mediafire.com/file/62bqqlrajr76kz6/boot.img
NOPE!
OK. I think solved.
Ran script again in adb shell.
And when phone try to reboot recovery.
Stopped it.
Reboot in Fastboot mode.
Type 'fastboot boot recovery.img'
Phone booted in TWRP
And your update installed successfully.
Thanks a lot!
Click to expand...
Click to collapse
Aaah, I got it... that can't reboot recovery bug for helium ... I will change script to not boot automatically and let helium users boot to TWRP manually and it will flash vendor zip automatically. Didn't get that bug under consideration.
Thank you for opening my eyes Hate when I can't test things...
This is mine, helium, seems it has been success, I use the one you posted at the first.
@nijel8... your work is a hard work!
I am proud to be working with you.
laolang_cool said:
This is mine, helium, seems it has been success, I use the one you posted at the first.
Click to expand...
Click to collapse
Great...:good: Seems like you don't suffer from hydrogen kernel.
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?