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..
This is my first guide so if I left something out please tell me.
I do not take any credit for any of this work. I just read in a thread how another user did it. I tried it and it worked.
This isn't nessassarily the right way to do this but this is what I did, and all don't from my nexus 7.
I've only tried it on slimkat. I'm going to be testing more ROMs today.
Thanks to
Legolas93
Slimroms.net
ryanrudolf
Things you will need:
A file explorer (I use solid explorer)
Zip app to extract and compress ( included in solid explorer)
Modified TWRP recovery from this post.
1. Download the latest weekly build of Slimkat. http://slimroms.net and extract the zip file to a folder.
2. Next either download the last build from legolass of slimkat here and extract it to its own folder or download attached boot.IMG and updater-script. (Only 2 files that I found that needed to be updated.)
3. If you just decided to download the attached files, extract the archive and inside you will find 2 files. Copy boot.IMG into the root of latest slimkat that you already extracted, overwriting when prompted. Next copy updater-script to./META-INF/Com/Google/android. overwriting when prompted.
If you didn't download the files from the post and choose to do this manually. Just follow above directions and get the files from the latest slimkat f2fs. Same directories.
4. Now its time to zip up the archive so we can flash it. Zip the files so the root of the archive is the same as the one you extracted. Meta-inf, system, Boot.IMG and file_contexts.
5. Flash in twrp.
B]List of working roms.[/B]
Liquid Smooth
Slimkat
CyanogenMod (with method below)
Tested but not fully working.
Paranoid
Method for CM By ryanrudolf
CM Nightly with All-F2FS (Unofficial Method)
1. download latest CM nightly (here is link for CM Nightly already modified for ALL-F2FS http://d-h.st/9By )
2. download faux025 kernel.zip
3. open CM nightly zipfile, extract the boot.img
4. open faux025 zipfile, extract the zImage
5. unpack the boot.img in step3
6. replace the zImage in step5 with faux025 zImage (step4)
7. replace fstab.grouper with this one -
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/APP /system f2fs ro,noatime,nosuid,nodev,discard,nodiratime,inline_ xattr,errors=recover wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xat tr,errors=recover wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xat tr,errors=recover wait,nonremovable,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/devices/platform/tegra-ehci auto vfat defaults voldmanaged=usbdisk:auto
8. repack boot.img. place it back in the CM nightly zipfile
9. on the CM nightly zipfile, edit updater script and look for these 3 lines -
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
replace it with
run_program("/sbin/busybox", "mount", "/system");
and these lines too -
format("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "0", "/system");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
replace with -
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/sdhci-tegra.3/by-name/APP");
run_program("/sbin/busybox", "mount", "/system");
10. save the updater script and put it back to the zipfile. CM nightly zipfile is complete and ready for flashing.
11. flash modded twrp with f2fs support. also download the formatpartitions.zip (credits to legolas http://forum.xda-developers.com/show....php?t=2678140)
12. boot to the modified twrp, flash the formatpartitions.zip. reboot back to recovery
13. flash the modified CM nightly zipfile
14. flash gapps.zip (i use slimroms minimal gapps)
15. Wipe > Format Data > yes
16. reboot
17. enjoy!
NOTE - everything is CM ramdisk, except for the fstab.grouper. If I use the original CM fstab.grouper and just edit to f2fs, it does not work.
Credits -
Legolas for the modified TWRP with F2FS
Faux for faux025 kernel with F2FS support
CM for the CM Nightlies
SlimRoms for the minimal gapps
[
Thanks again. I will give this a try very soon. Glad someone figured out what these devs are doing. I hope others will come in here and share even more information. :good:
EDIT: So, you managed to do all of this on your device? Wow nice work.
SkOrPn said:
Thanks again. I will give this a try very soon. Glad someone figured out what these devs are doing. I hope others will come in here and share even more information. :good:
EDIT: So, you managed to do all of this on your device? Wow nice work.
Click to expand...
Click to collapse
Ryanrudolf in the all f2fs slimkat thread said what files he changed. I just followed his direction.
And yes I did all this from my n7.
No problem I'm glad I could contribute.
Sent from my Nexus 7 using XDA Premium HD app
Any ROMs u want me to test? I'm about to try paranoid 4.2 beta 2 (latest)
For all the other ROMs I'm going to remove the slimroms text that scrolls in twrp when installing. I'll update the op with unbranded updater file so they can try it on other ROMs and not get confused lol.
Sent from my Nexus 7 using XDA Premium HD app
ronedogg said:
Any ROMs u want me to test? I'm about to try paranoid 4.2 beta 2 (latest)
For all the other ROMs I'm going to remove the slimroms text that scrolls in twrp when installing. I'll update the op with unbranded updater file so they can try it on other ROMs and not get confused lol.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah that would have been great, but the dev on my preferred ROM is already working himself to figure it out. I'm probably going to be testing his latest build here soon. I just want to know what you guys did so that next week, when I want to try another ROM I will have a larger menu to choose from
If you want to mess around and test several ROM's I suggest you try AOSPAL SaberDroid in your list. There will be a new build here soon, maybe today I think.
Hi there,
since i like cyanogenmod, i tried to apply your 'patch' to a cm build. (i just replaced some rows in the updater-script and replaced boot.img in the zip file)
It worked, since the rom booted up but it costantly throws 'Unfortunately, the process com.android.phone has stopped'...
I (hardly) managed to enable developer settings, adb and check mount command output (just to be sure that system, data and cache were mounted in f2fs) and they actually are f2fs.
I guess that com.android.phone message is a kernel related issue.
carlo93 said:
Hi there,
since i like cyanogenmod, i tried to apply your 'patch' to a cm build.
It worked, since the rom booted up but it costantly throws 'Unfortunately, the process com.android.phone has stopped'...
I (hardly) managed to enable developer settings, adb and check mount command output (just to be sure that system, data and cache were mounted in f2fs) and they actually are f2fs.
I guess that com.android.phone message is a kernel related issue (i replaced boot.img with the one you attached).
Click to expand...
Click to collapse
That is a known issue with CM, not this mod. I get that same FC when I use CM11. Its not there on Slim, or Omni or AOSPAL, using the same mod.
carlo93 said:
Hi there,
since i like cyanogenmod, i tried to apply your 'patch' to a cm build.
It worked, since the rom booted up but it costantly throws 'Unfortunately, the process com.android.phone has stopped'...
I (hardly) managed to enable developer settings, adb and check mount command output (just to be sure that system, data and cache were mounted in f2fs) and they actually are f2fs.
I guess that com.android.phone message is a kernel related issue (i replaced boot.img with the one you attached).
Click to expand...
Click to collapse
Hmmm. I tried paranoid and got the same result but was keyboard throwing up error....
In the all f2fs slimkat thread another user said he tried cyanogen as well and got same error. Maybe this is just for slimkat, I thought we might have gotten lucky.
I'm going to try to compare the updater scripts for cm and pa with the slimkat script. See if there is something obvious we can change.
Actually I take that back, I never tried straight PA, just modified versions of it. I only get that message with CM11.
SkOrPn said:
Actually I take that back, I never tried straight PA, just modified versions of it. I only get that message with CM11.
Click to expand...
Click to collapse
looking at comparing files now.
in cm latest nightly there is a line of code refering to f2fs already.
symlink("../bin/fsck.f2fs", "/system/bin/dump.f2fs");
not sure what that is.
im gonna upload a updated version of the script for cm. Using notepad ++ and compare plugin, should have something shortly that i can test.
Just tried this with the latest liquid smooth build, works fine so far. no fc and running really smoothly
PatrickMac said:
Just tried this with the latest liquid smooth build, works fine so far. no fc and running really smoothly
Click to expand...
Click to collapse
sweet!. im going to update the OP with working roms.
Thanks for testing
Just a suggestion, I would rename the thread to
[Guide] Converting ANY ROM to All-F2FS Partitions - Working ROM list Included!
SkOrPn said:
Just a suggestion, I would rename the thread to
[Guide] Converting ANY ROM to All-F2FS Partitions - Working ROM list Included!
Click to expand...
Click to collapse
it wont let me rename the title
2 failed attempts at editing the updater script on paranoid.
onto 3rd attempt.......
after some testing I got paranoid to install. but when i install gapps package all kinds of errors get thrown up....
waaay over my head there. ill try again later tonight see what I can come up with. i might be close... I might be waaay off.
maybe someone will see this thread and give me some pointers.
ronedogg said:
after some testing I got paranoid to install. but when i install gapps package all kinds of errors get thrown up....
waaay over my head there. ill try again later tonight see what I can come up with. i might be close... I might be waaay off.
maybe someone will see this thread and give me some pointers.
Click to expand...
Click to collapse
Haha, that's how I felt the weekend before last when I spent 20 straight hours trying to figure this out.
I have seen a few people ask for this so i'm going to try and edit the SlimRoms SlimBean 4.3.1 version of there rom to see if i can get this working on 4.3.1 Jelly Bean Roms.
I have already edited the fstab file in the SlimBean 4.3.1 kernel/boot.img and have already edited the updater script now just doing a backup of important stuff and going to give it a try
CptKlink said:
I have seen a few people ask for this so i'm going to try and edit the SlimRoms SlimBean 4.3.1 version of there rom to see if i can get this working on 4.3.1 Jelly Bean Roms.
I have already edited the fstab file in the SlimBean 4.3.1 kernel/boot.img and have already edited the updater script now just doing a backup of important stuff and going to give it a try
Click to expand...
Click to collapse
Good luck. :good:
carlo93 said:
Hi there,
since i like cyanogenmod, i tried to apply your 'patch' to a cm build. (i just replaced some rows in the updater-script and replaced boot.img in the zip file)
It worked, since the rom booted up but it costantly throws 'Unfortunately, the process com.android.phone has stopped'...
I (hardly) managed to enable developer settings, adb and check mount command output (just to be sure that system, data and cache were mounted in f2fs) and they actually are f2fs.
I guess that com.android.phone message is a kernel related issue.
Click to expand...
Click to collapse
same i got that error too on the latest nightly of CM.
will try more on weekend
Sent from my C6503 using Tapatalk
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
I've spent about 6 hours on this
I just can't upgrade beyond 10.2
I did it by instructions,
flashed stock 4.1.2 using odin, rooted it, tried temp cwmp 4.0.6.8 to flash any rom beyond 10.2 and it just doesn't work
tried diferent kernels, CoCore Kernel, twrp, cm11 old/new, omnirom, cm12, and overall it always fails with set_metadata_recursive, or more correct ApplyParsedPerms: lsetfilecon of /system/lost+found to ubject_r:system_file:s0 failed: Operation not supported on transport endpoint
tried formating /system /data/ /cache /preload dalvik cache...
googling the reason behind this is that recovery is too old for cm11, so I should use either twrp or cwm higher than 4.0.4.5, which I both tried
I'm lost? how come nobody has this problem?
I'm currently on 10.2 with cwm 4.0.4.6, tried upgrading to oldest cm11 I could find (cm-11-20140104-UNOFFICIAL-janice.zip) thinking this could help but no avail
0
down vote
favorite
I've been trying to install cyanogen 12.1 on my Moto X 2013.
Followed all the steps mentioned in the official Cyanogen Mod Wiki (Allowed to include the link only after 10 posts)
Flew through the steps however, the final flash of ROM fails.
Here are the logs.
Installing '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghos
t_att,ghost_rcica,xt1060,ghost_verizon; this device is .
This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcic
a,xt1060,ghost_verizon; this device is .
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'
Error flashing zip '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'
Looking at the bold face logs, my hunch is the TWRP isn't able to recognize my device's model XT1052.
Is this what's happening here? If no, what seems to be going wrong?
How do I fix this?
[email protected] said:
0
down vote
favorite
I've been trying to install cyanogen 12.1 on my Moto X 2013.
Followed all the steps mentioned in the official Cyanogen Mod Wiki (Allowed to include the link only after 10 posts)
Flew through the steps however, the final flash of ROM fails.
Here are the logs.
Installing '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghos
t_att,ghost_rcica,xt1060,ghost_verizon; this device is .
This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcic
a,xt1060,ghost_verizon; this device is .
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'
Error flashing zip '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'
Looking at the bold face logs, my hunch is the TWRP isn't able to recognize my device's model XT1052.
Is this what's happening here? If no, what seems to be going wrong?
How do I fix this?
Click to expand...
Click to collapse
Which version of TWRP are you using? Try 3.x, some of the older ones aren't working correctly.
Or alternatively, edit the "updater_script" in the ROM zip (META-INF/com/google/android), and delete the first line, starting with "assert(getprop.."
rumkugel13 said:
Which version of TWRP are you using? Try 3.x, some of the older ones aren't working correctly.
Or alternatively, edit the "updater_script" in the ROM zip (META-INF/com/google/android), and delete the first line, starting with "assert(getprop.."
Click to expand...
Click to collapse
Been using twrp-2.8.7.0-ghost
twep 3.x.x isn't released for Moto X 2013 (Ghost) yet. I tried using twrp-3.0.0.0-victaria built for Moto X 2014(Victaria), however, the phone never booted into recovery.
Also tried out removing the first line from the updater script which checks for models just as you suggested.
The flash still fails. This time with barely any logs
just says Error occurred while.. Fail
Double checked the versions(of everything) but it still isn't working.
I've had simular issue . download twrp 2.6.3.1 ... worked for me and many others
Polishpolisher said:
I've had simular issue . download twrp 2.6.3.1 ... worked for me and many others
Click to expand...
Click to collapse
Didn't work out for me. Flash just fails without any useful logs
You've probably applied compression when you've changed the updste script. It should be Store only, try again, because the error you were getting is exactly from the get prop in the first line.
[email protected] said:
0
down vote
favorite
I've been trying to install cyanogen 12.1 on my Moto X 2013.
Followed all the steps mentioned in the official Cyanogen Mod Wiki (Allowed to include the link only after 10 posts)
Flew through the steps however, the final flash of ROM fails.
Here are the logs.
Installing '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
script aborted: This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghos
t_att,ghost_rcica,xt1060,ghost_verizon; this device is .
This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcic
a,xt1060,ghost_verizon; this device is .
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'
Error flashing zip '/sdcard/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip'
Looking at the bold face logs, my hunch is the TWRP isn't able to recognize my device's model XT1052.
Is this what's happening here? If no, what seems to be going wrong?
How do I fix this?
Click to expand...
Click to collapse
First i installed cm-12.1-20150901-SNAPSHOT-YOG4PAO237-ghost.zip then i flashed CM Recovery cm-12.1-20150901-SNAPSHOT-YOG4PAO237-ghost-recovery.img then i updated the CM by the CM Updater inside the settings and it worked great !!
Hi,
I had same issue.
My Moto X 2013 had still Android 4.4.2 as I rooded it.
Then I tried to flash CM12.1 with instuctions from wiki.cyanogenmod.org and failed with same error message as [email protected]
I tried several things mentioned here and from other forums but failed.
At least the hint from Polishpolisher was working. Many many thanks!
Found twrp-2.6.3.1-ghost-4.4.img at rootjunkysdl.com.
Herewith install of cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip was possible.
Had the same issue..
Here's what you do..
Extract the cm 12.1 file and file update script file in there ( look for it it's in there in Android or Google folder ) then delete the first line in the script " JUST THE FIRST LINE "
And voilà
Enjoy CM 12.1
I've had the same problem. The solution for me was to install the rom stock using the RSD. Then I installed the latest official version of TWRP and had no problems.