Related
Hi, i am stuck in bootloop after flashing a kernel over TH ICS. I can't seem to find a right ClockworkMod Recovery where I can either restore my nandroid backups (i am getting md5 checksum failed) or where i can flash the rom again. i am getting assert failed: getprop("ro.product.device") == "galaxys" whenever i try to do that.
so far i tried to flash cm7-galaxys-initial-kernel.tar with odin, but i cant get into clockworkmod recovery with that one. that i think i tried darkys recovery FixRecovery.tar, but thats where almost nothing works, no nandroid restore and no flashing of new roms.
can someone point me to the right directions? i am missing my phone :-(
haha thx
Reflash to stock with odin. Download the stock rom you want. Use 512 pit file and check repartition.
Sent from my GT-I9000 using Tapatalk
Hi, this is my first post on XDA and after watching the "Noob" video I will be wary here, haha
So, I needed to update my IDEOS u8800 to 2.3.*, I googled if the hardware could support it and it said yes, but the software isn't official.
I did some research and found I had to root the phone, I did so successfully, it was quite fun honestly.
It now had SuperUser but it was still the same version so I googled some more and found out about ROMs.
From what I could gather you can upgrade your android version if you "Flash" a correct ROM (If your hardware supports it ),
Then I downloaded and installed CWM v 5.0.2.7 and backed up the whole phone using MyBackup and Titanium Backup, that worked well, but when I tried to Flash a ROM, thats when the problems began...
So I downloaded the ROM and moved it to my SD card, like the many tutorials said, then I fully shut down my phone and held the Power and VOL+ buttons and entered CWM recovery, I formated the /data and /cache by using the "- wipe data/factory reset" option on the first screen (Not sure if that formated "/dalvik") and "- wipe cache partition", after that I went into the menu "- install zip from sdcard" then "- choose zip from sdcard" and selected the .zip file that was the ROM I downloaded, then I got an error, I will post the whole log...
Log:
"CWM-based Recovery v5.0.2.7
-- Installing: /sdcard/oxygen2.3.2-u8800.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "u8800" \\ getprop("ro.build.device") == "u8800" || getpropro.product.board") == "u8800
E:Error in /sdcard/oxygen2.3.2-u8800.zip
(Status 7)
Installation aborted."
I have had a little bit of time in Java and from what I can tell, the ROM doesn't say its compatible with the device, the build of the device or the board, which I think refers to the motherboard.
Also, the phone won't boot past the "IDEOS" icon, I think the current ROM is broke, now, atleast
I would like a way to get it to boot again at Android version 2.2
I would love a way to make it boot again and upgrade the Android version to 2.3 (Or higher, if its compatible, I doubt it is although)
Resources:
-Quote from "wwwDOTgsmarenaDOTcom/huawei_u8800_ideos_x5-3596.php"
--"OS Android OS, v2.2 (Froyo), upgradable to v2.3 (Gingerbread)"
-Ask for any files or more information and ill try to get 'em for you!
Thanks for your time!
-UltraFireFX
Are you using CWM 5.0.2.7 with 12900 baseband?
I am pretty sure I am using that version of CWM but no idea at all on the baseband I could find out if you pointed me in the right dirrection.
Just remembered my friend has an IDEOS u8800 just like mine, but working, its rooted but nothing more, would that help?
Okay, just found on my friends phone that the baseband is 129005, going to check what baseband CWM...
UltraFireFX said:
Okay, just found on my friends phone that the baseband is 129005, going to check what baseband CWM...
Click to expand...
Click to collapse
You must use 5.0.2.6 recovery for 12900 baseband
where is a download link for that?
Will any ROM for u8800 work and can I update my phone by doing so??
Thanks SOOO MUCH
Can anyone upload a modified M6 that supports all-f2fs? thanks!
joefso said:
Can anyone upload a modified M6 that supports all-f2fs? thanks!
Click to expand...
Click to collapse
U can convert yourself easily using Nabendu's script
pancham7 said:
U can convert yourself easily using Nabendu's script
Click to expand...
Click to collapse
no his script is not working for cyanogenmod
joefso said:
Can anyone upload a modified M6 that supports all-f2fs? thanks!
Click to expand...
Click to collapse
As per the how-to from here
Change the following from the updater script
Code:
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system"); mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
to:
Code:
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/msm_sdcc.1/by-name/system"); run_program("/sbin/busybox", "mount", "/system");
and then flash one of jolinard's kernel shown in his sig, maybe the modded ak kernel for example.
Provided you've already formatted data and all before and you were on a f2fs rom.
Moon2 said:
As per the how-to from here
Change the following from the updater script
Code:
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system"); mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
to:
Code:
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/msm_sdcc.1/by-name/system"); run_program("/sbin/busybox", "mount", "/system");
and then flash one of jolinard's kernel shown in his sig, maybe the modded ak kernel for example.
Provided you've already formatted data and all before and you were on a f2fs rom.
Click to expand...
Click to collapse
Hi yes, I tested that work arround and the boot.img provided in the thread by Konstantinos is not working ( untested ) . NABENDU1 updated his script but his patch is not working, also reported by other users
joefso said:
Hi yes, I tested that work arround and the boot.img provided in the thread by Konstantinos is not working ( untested ) . NABENDU1 updated his script but his patch is not working, also reported by other users
Click to expand...
Click to collapse
No, do not use the boot.img, only change the updater script then install the kernel, skip out on the img file.
Tested on latest cm11 nightly with "AK.237.EXODUS.MAKO.CM-F2FS-auto.zip" kernel.
I just skimmed through it but I believe jolinard's kernel automatically updates the fstab in the boot.img depending on the system partition format. And with you changing the updater script to format to f2fs rather than ext4, the fstab will be changed for f2fs rather than ext4 when you flash the kernel straight after.
Also works on "Nexus 5 Experience - CM11 Based" rom
Moon2 said:
No, do not use the boot.img, only change the updater script then install the kernel, skip out on the img file.
Tested on latest cm11 nightly with "AK.237.EXODUS.MAKO.CM-F2FS-auto.zip" kernel.
I just skimmed through it but I believe jolinard's kernel automatically updates the fstab in the boot.img depending on the system partition format. And with you changing the updater script to format to f2fs rather than ext4, the fstab will be changed for f2fs rather than ext4 when you flash the kernel straight after.
Also works on "Nexus 5 Experience - CM11 Based" rom
Click to expand...
Click to collapse
Yes that works but /data get´s mounted as ext4 according to diskinfo (yes wiped data after flashking AK). I did this installation after I flashed stock, rooted etc.. . I tried this twice to make sure I did not make a mistake. If I go into TWRP and format data again the device gets stuck at the google logo
joefso said:
Yes that works but /data get´s mounted as ext4 according to diskinfo (yes wiped data after flashking AK). I did this installation after I flashed stock, rooted etc.. . I tried this twice to make sure I did not make a mistake. If I go into TWRP and format data again the device gets stuck at the google logo
Click to expand...
Click to collapse
Mounts as f2fs for me - see attachments. Did your twrp install have a red back button?
Moon2 said:
Mounts as f2fs for me - see attachments. Did your twrp install have a red back button?
Click to expand...
Click to collapse
Hmm, strange. Yes it does, going to try again
joefso said:
Hmm, strange. Yes it does, going to try again
Click to expand...
Click to collapse
Install one of the working f2fs roms as normal and check diskinfo for system and data and upload the pics here then give me a few mins, I'm uploading a cm build.
Do it exactly as I say and don't make any changes to the method.
joefso said:
Hmm, strange. Yes it does, going to try again
Click to expand...
Click to collapse
First, make sure that your data is already f2fs using another rom - don't need to do this, but just in case you'll know if you've done something wrong first.
I've tested this again and again and it works fine - no fcs and definitely changes to f2fs. I've attached diskinfo details for /system and userdata partitions for a clean install.
Assuming you've already formatted data to f2fs and installed the required twrp as per here.
Do not restart until you've finished
1) Install cm build from here:
2) Install gapps - Optional ( leave any other zips you want to install for after you've verified this works)
3) Install attached ak kernel (It's the latest ak kernel modified by jolinard)
4) Restart
I've tried this a few times just to confirm for you and it definitely works, so if it doesn't recheck your steps from the start.
joefso said:
Yes that works but /data get´s mounted as ext4 according to diskinfo (yes wiped data after flashking AK). I did this installation after I flashed stock, rooted etc.. . I tried this twice to make sure I did not make a mistake. If I go into TWRP and format data again the device gets stuck at the google logo
Click to expand...
Click to collapse
Wiping data after flashing ak kernel - doesn't matter - after you've formatted data once you don't ever need to do it again when you're switching between f2fs roms.
Follow the steps I've mentioned in previous post. If it still doesn't work, list all the steps you've done - don't miss anything out.
Moon2 said:
First, make sure that your data is already f2fs using another rom - don't need to do this, but just in case you'll know if you've done something wrong first.
I've tested this again and again and it works fine - no fcs and definitely changes to f2fs. I've attached diskinfo details for /system and userdata partitions for a clean install.
Assuming you've already formatted data to f2fs and installed the required twrp as per here.
Do not restart until you've finished
1) Install cm build from here:
2) Install gapps - Optional ( leave any other zips you want to install for after you've verified this works)
3) Install attached ak kernel (It's the latest ak kernel modified by jolinard)
4) Restart
I've tried this a few times just to confirm for you and it definitely works, so if it doesn't recheck your steps from the start.
Click to expand...
Click to collapse
I will be home in a few hours and will report the results. I never flashed a AOSP all f2fs before installing CM (during this installation), before I tried slimwork and PA which worked like a charm
joefso said:
I will be home in a few hours and will report the results. I never flashed a AOSP all f2fs before installing CM (during this installation), before I tried slimwork and PA which worked like a charm
Click to expand...
Click to collapse
I've mentioned that you don't need to do that at all, I just want to confirm that it changed to f2fs when you flashed other roms.
Moon2 said:
I've mentioned that you don't need to do that at all, I just want to confirm that it changed to f2fs when you flashed other roms.
Click to expand...
Click to collapse
With Slim everything goes fine, but as soon as I flash the uploaded CM or my own modified M6 it gets stuck at boot, flashed AK kernel after flashing the rom
joefso said:
With Slim everything goes fine, but as soon as I flash the uploaded CM or my own modified M6 it gets stuck at boot, flashed AK kernel after flashing the rom
Click to expand...
Click to collapse
List your steps straight after you installed slim and went to twrp, mention every step you took in a list, don't miss anything out.
Got it working, appearently after I hit factory reset and formated data it worked
thanks for the support!
Noob question: anyone have a full tutorial on how to flash phone to f2fs? I wanna convert my phone and use a rom with f2fs, but I don't want to make any mistakes.
Sent from my 1961 XP-755
---------- Post added at 02:07 PM ---------- Previous post was at 02:06 PM ----------
joefso said:
Got it working, appearently after I hit factory reset and formated data it worked
thanks for the support!
Click to expand...
Click to collapse
What app are you using?
Sent from my 1961 XP-755
TheKnux said:
Noob question: anyone have a full tutorial on how to flash phone to f2fs? I wanna convert my phone and use a rom with f2fs, but I don't want to make any mistakes.
Sent from my 1961 XP-755
---------- Post added at 02:07 PM ---------- Previous post was at 02:06 PM ----------
ps. np joe.
What app are you using?
Sent from my 1961 XP-755
Click to expand...
Click to collapse
Follow the steps here: http://forum.xda-developers.com/nexus-4/orig-development/recovery-rom-kernel-f2fs-05-04-14-t2706825
It's not an app, it's in twrp recovery, he forgot to do factory reset and format before installing the rom.
The only kernels that are working with CM 11 are AK and hellsdoctor atm. Booting the other f2fs kernels will cause the device to get stuck at boot
Updated with steps to go to CM11-S update XNP44S
These days I was on 33R, rooted, with Xposed Framework installed, and lots of modules configured, including one that adds more col/lines to the Google Now launcher grid. Until now, each OTA was a pain, because although it flashed fine, I had to reinstall Xposed and I always had trouble with the launcher loosing its config (during the first boot, the grid was back to the default grid, and after reinstalling Xposed, I had to also restore a TiBu backup of Google Search to have my launcher setup again)... a pain.
This time, to go to 38R I took a different approach.
First, prepare in your /sdcard the following files:
cm-11.0-XNPH33R-bacon-signed.zip: Full XNPH33R factory image (flashable in recovery)
cm-bacon-3628510d76-to-ac1ccf7921-signed.zip: XNPH38R OTA zip. (link taken from here, thanks jaggyjags)
XNP44S update cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
SuperSU-v2.02.zip Flashable SuperSu zip (source, thanks Chainfire)
Xposed-Installer-Recovery.zip: zip that installs Xposed framework (you can generate it from Xposed Installer, or directly download this one)
With that, and assuming you already have a custom recovery installed (I used TWRP 2.7.1.1), this I what I did:
Reboot into Recovery (Vol-Down & Power)
Click Install
Select 1rst zip: cm-11.0-XNPH33R-bacon-signed.zip, but don't flash it yet
Add a zip: cm-bacon-3628510d76-to-ac1ccf7921-signed.zip (XPN38R)
Add a zip: cm-bacon-ac1ccf7921-to-5fa8c79c0b-XNPH44S-signed.zip
Add a zip: SuperSU-v2.02.zip
Add a zip: Xposed-Installer-Recovery.zip
(Optional) If you have a custom kernel zip that you know is compatible with XNP38R, you can also add it here
Swipe to confirm flash, this will actually flash all the previous zips, in order
Check to wipe Dalvik-cache/Cache
Reboot to system
Wait a couple of minute while your OPO boots to XNP38R: You've successfully flashed the OTA while preserving root, Xposed,...
Hope that helped
Enjoy XNP38R!
Edit: The method above should work if you are running CM11-S. The factory cm-11.0-XNPH33R-bacon-signed.zip does some verification on the already installed rom (for some reason, I really don't see the point).
If you have a different rom, or if it's a CM11-S rom but somehow resigned by different key, this above will fail. The update-script runs a script called otasigcheck.sh that looks into the installed rom files and checks the key that signed the /system/app/HTMLViewer.apk against the one in the OTA).
The error is: "Can't install this package on top of incompatible data. Please try another package or run a factory reset". (More details in comment #16)
In that case you should start doing the following:
Download and extract the XNP33R fastboot factory image
Boot into fastboot mode (Vol-Up & Power)
Connect your OPO to your computer (USB)
Run: fastboot flash boot boot.img
Then: fastboot flash system system.img
Then: fastboot reboot (will reboot the phone into Android)
Reboot into Recovery (Vol-Down & Power)
It should now be fine to continue from step 4 of the steps above.
If you need help with installing fastboot on your computer, please go here.
You don't need to do a wipe? I'm also struggling getting 38R
Hey if Im already on 33r do I have to flash it? Im currently on 33r rooted and when I try to flash 38r it gives me an error
Waynesta said:
Hey if Im already on 33r do I have to flash it? Im currently on 33r rooted and when I try to flash 38r it gives me an error
Click to expand...
Click to collapse
Yes you need to reflash it. It will put your phone in the state where you can then correctly flash 38R OTA.
Sent from my OnePlus One using Tapatalk Pro
rhaces said:
You don't need to do a wipe? I'm also struggling getting 38R
Click to expand...
Click to collapse
You don't need to do a wipe data, if you come from CM11-S. If you come from a different rom, you probably need to.
Sent from my OnePlus One using Tapatalk Pro
stupid question:
what is the framework xposed?
psxsnake said:
stupid question:
what is the framework xposed?
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Transmitted via Bacon
This is not working for me. I get Error executing updater binary in zip when flashing 33R zip
EDIT: I don't know why but I tried the option "Fix premissions" in the recovery and now it works and flashed without error.
don't wor for me or error flash or error mount ft why?
i had vanir rom
Great post. Thanks.
Can I wipe all data anyway so I can start with a fresh install of the update?
famonaco said:
don't wor for me or error flash or error mount ft why?
i had vanir rom
Click to expand...
Click to collapse
What recovery are you using? What is the error you get exactly? Can you maybe post a photo?
Sent from my OnePlus One using Tapatalk Pro
jairusz said:
Can I wipe all data anyway so I can start with a fresh install of the update?
Click to expand...
Click to collapse
Yes of course. It's not necessary though, I did so because I didn't want to wipe all data.
Sent from my OnePlus One using Tapatalk Pro
Same issue I get when trying to install the 38R by itself, described here http://forum.xda-developers.com/oneplus-one/help/apply-ota-stock-root-franco-23r-twrp-t2900311, "Can't install this package on top of incompatible data. Please try another package or run a factory reset"
CyberT3 said:
This is not working for me. I get Error executing updater binary in zip when flashing 33R zip
EDIT: I don't know why but I tried the option "Fix premissions" in the recovery and now it works and flashed without error.
Click to expand...
Click to collapse
update TWRP to 2.8.01
"Can't install this package on top of incompatible data"
rhaces said:
Same issue I get when trying to install the 38R by itself, described here http://forum.xda-developers.com/oneplus-one/help/apply-ota-stock-root-franco-23r-twrp-t2900311, "Can't install this package on top of incompatible data. Please try another package or run a factory reset"
Click to expand...
Click to collapse
TL;DR: I've updated the OP with an alternative method that should work for those getting this error .
Actually, for some obscure reason I don't know, the zip factory image for XNP33R does a verification on one file that is in /data (/data/system/packages.xml), looking for the certificate that signed a specific package from the installed rom (/system/app/HTMLViewer.apk). If the certificate isn't the same one that is bundled in the factory image, it won't flash and throw the error you got. If you scroll to the right you'll see the error is from the sha1_check on line 6:
Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data");
package_extract_file("system/bin/otasigcheck.sh", "/tmp/otasigcheck.sh");
package_extract_file("META-INF/org/cyanogenmod/releasekey", "/tmp/releasekey");
set_metadata("/tmp/otasigcheck.sh", "uid", 0, "gid", 0, "mode", 0755);
run_program("/tmp/otasigcheck.sh");
sha1_check(read_file("/tmp/releasekey"),"7241e92725436afc79389d4fc2333a2aa8c20230") && abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
unmount("/data");
Here we can see the content of otasigcheck.sh:
Code:
#!/sbin/sh
# Validate that the incoming OTA is compatible with an already-installed
# system
if [ -f /data/system/packages.xml -a -f /tmp/releasekey ]; then
relCert=$(grep -A3 'package name="com.android.htmlviewer"' /data/system/packages.xml | grep "cert index" | head -n 1 | sed -e 's|.*"\([[:digit:]][[:digit:]]*\)".*|\1|g')
grep "cert index=\"$relCert\"" /data/system/packages.xml | grep -q `cat /tmp/releasekey`
if [ $? -ne 0 ]; then
echo "You have an installed system that isn't signed with this build's key, aborting..."
# Edify doesn't abort on non-zero executions, so let's trash the key and use sha1sum instead
echo "INVALID" > /tmp/releasekey
exit 1
fi
fi
exit 0
I don't really see the whole point in doing that, as the next line will actually format system, so why care about what was there before anyway?
Code:
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
I've updated the OP with an alternative method that should work for those getting this error .
I really don't know what is going on with my phone but that didn't help anyways. I flashed boot and system from 33R in fastboot, went back into TWRP and installed the full 38R and still same issue. I tried every combination (including flash boot, syste, then in TWRP install 33R again) and nothing.
Finally what I did was fastboot flash boot system and recovery, boot into system, apply the OTA from the system and now that worked. Booted into 38R and everything worked ok, so went back to fastboot, flashed TWRP again, went into TWRP and installed supersu and franco 24r and now things seem to be ok.
Thanks for all the help
rhaces said:
I really don't know what is going on with my phone but that didn't help anyways. I flashed boot and system from 33R in fastboot, went back into TWRP and installed the full 38R and still same issue. I tried every combination (including flash boot, syste, then in TWRP install 33R again) and nothing.
Finally what I did was fastboot flash boot system and recovery, boot into system, apply the OTA from the system and now that worked. Booted into 38R and everything worked ok, so went back to fastboot, flashed TWRP again, went into TWRP and installed supersu and franco 24r and now things seem to be ok.
Thanks for all the help
Click to expand...
Click to collapse
I've modified my alternative instructions in OP, that should fix that (for others) : after fastboot system and boot it seems you need to reboot into Android (what you did). That makes sense actually as it will recompute the xml file that is also checked by the OTA. Then reboot back to TWRP.
I still wonder why it was falling though. You were on cm11-s right? What could have make the htmlviewer file have a different signature? Any idea? (did you apply any modification on top of CM11-S besides root, kernel, Xposed ?)
Sent from my OnePlus One using Tapatalk Pro
Option 1 worked fine on my rooted but otherwise unaltered OnePlus One. Thanks for the guide!
I get an error on the Xposed-installer but everything else goes well. If I remember it was a directory error message...
Envoyé de mon A0001 en utilisant Tapatalk
You need to modify the update-script
Before
Code:
show_progress(0.900000, 0);
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
ui_print("Verifying the updated system image...");
if range_sha1("/dev/block/platform/msm_sdcc.1/by-name/system", "48,0,32770,32857,32859,33341,65535,65536,65538,66020,98303,98304,98306,98393,98395,98877,131071,131072,131074,131556,163839,163840,163842,163929,163931,164413,196607,196608,196610,197092,220718,229376,229378,229465,229467,229949,262143,262144,262146,294912,294914,295001,295003,295485,327679,327680,327682,328164,338943") == "f5720ee3320d52b5e8213ca94faa6699e8c99b66" then
if range_sha1("/dev/block/platform/msm_sdcc.1/by-name/system", "52,32770,32857,32859,33341,65535,65536,65538,66020,98303,98304,98306,98393,98395,98877,131071,131072,131074,131556,163839,163840,163842,163929,163931,164413,196607,196608,196610,197092,220718,221230,228864,229376,229378,229465,229467,229949,262143,262144,262146,262658,294400,294912,294914,295001,295003,295485,327679,327680,327682,328164,338943,338944") == "7a05221a9c1e18b636151a6f8706186d47ffd822" then
ui_print("Verified the updated system image.");
else
abort("system partition has unexpected non-zero contents after OTA update");
endif;
else
abort("system partition has unexpected contents after OTA update");
endif;
ui_print("Patching boot image...");
show_progress(0.100000, 10);
apply_patch("EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:6739968:8e1118d962e47aa0beb2d2307769688777299dd9:7454720:a191039790b0c388719c2e573ecfc8178e8a4ba2",
"-", a191039790b0c388719c2e573ecfc8178e8a4ba2, 7454720,
8e1118d962e47aa0beb2d2307769688777299dd9, package_extract_file("patch/boot.img.p"));
ui_print("Writing radio image...");
set_progress(1.000000);
After
Code:
show_progress(0.900000, 0);
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
ui_print("Patching boot image...");
show_progress(0.100000, 10);
apply_patch("EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:6739968:8e1118d962e47aa0beb2d2307769688777299dd9:7454720:a191039790b0c388719c2e573ecfc8178e8a4ba2",
"-", a191039790b0c388719c2e573ecfc8178e8a4ba2, 7454720,
8e1118d962e47aa0beb2d2307769688777299dd9, package_extract_file("patch/boot.img.p"));
set_progress(1.000000);
Open OTA .zip on PC, open meta-inf/com/google/adndroid/update-script
Replace everything with my script from "after"
Now you can:
1. Do a factory reset
2. Flash cm-12.1-YOG7DAS2K1
3. Flash cm-bacon-cee4e8702d-to-e36dd78050
4. Dont think about recovery or smth else
P.S. I am using SuperSU 2.67 in Systemless mode
Anyone tried this?
Can someone please do this and provide us the zip file to flash in TWRP...?
CraZY_BoY^ said:
You need to modify the update-script
Before
Code:
show_progress(0.900000, 0);
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
ui_print("Verifying the updated system image...");
if range_sha1("/dev/block/platform/msm_sdcc.1/by-name/system", "48,0,32770,32857,32859,33341,65535,65536,65538,66020,98303,98304,98306,98393,98395,98877,131071,131072,131074,131556,163839,163840,163842,163929,163931,164413,196607,196608,196610,197092,220718,229376,229378,229465,229467,229949,262143,262144,262146,294912,294914,295001,295003,295485,327679,327680,327682,328164,338943") == "f5720ee3320d52b5e8213ca94faa6699e8c99b66" then
if range_sha1("/dev/block/platform/msm_sdcc.1/by-name/system", "52,32770,32857,32859,33341,65535,65536,65538,66020,98303,98304,98306,98393,98395,98877,131071,131072,131074,131556,163839,163840,163842,163929,163931,164413,196607,196608,196610,197092,220718,221230,228864,229376,229378,229465,229467,229949,262143,262144,262146,262658,294400,294912,294914,295001,295003,295485,327679,327680,327682,328164,338943,338944") == "7a05221a9c1e18b636151a6f8706186d47ffd822" then
ui_print("Verified the updated system image.");
else
abort("system partition has unexpected non-zero contents after OTA update");
endif;
else
abort("system partition has unexpected contents after OTA update");
endif;
ui_print("Patching boot image...");
show_progress(0.100000, 10);
apply_patch("EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:6739968:8e1118d962e47aa0beb2d2307769688777299dd9:7454720:a191039790b0c388719c2e573ecfc8178e8a4ba2",
"-", a191039790b0c388719c2e573ecfc8178e8a4ba2, 7454720,
8e1118d962e47aa0beb2d2307769688777299dd9, package_extract_file("patch/boot.img.p"));
ui_print("Writing radio image...");
set_progress(1.000000);
After
Code:
show_progress(0.900000, 0);
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
ui_print("Patching boot image...");
show_progress(0.100000, 10);
apply_patch("EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot:6739968:8e1118d962e47aa0beb2d2307769688777299dd9:7454720:a191039790b0c388719c2e573ecfc8178e8a4ba2",
"-", a191039790b0c388719c2e573ecfc8178e8a4ba2, 7454720,
8e1118d962e47aa0beb2d2307769688777299dd9, package_extract_file("patch/boot.img.p"));
set_progress(1.000000);
Open OTA .zip on PC, open meta-inf/com/google/adndroid/update-script
Replace everything with my script from "after"
Now you can:
1. Do a factory reset
2. Flash cm-12.1-YOG7DAS2K1
3. Flash cm-bacon-cee4e8702d-to-e36dd78050
4. Dont think about recovery or smth else
P.S. I am using SuperSU 2.67 in Systemless mode
Click to expand...
Click to collapse
Can you give us meta-inf already modified , I try all your step but didn't work :/
Thanks in advance
I did exactly this and it flashed OK but with an warning at the end: "unable to mount /system". After that i can't reboot, it just keep booting back to recovery. I tried both TWRP 3.0.1 and the unofficial 2.8.6.0.6 version.
elemti said:
I did exactly this and it flashed OK but with an warning at the end: "unable to mount /system". After that i can't reboot, it just keep booting back to recovery. I tried both TWRP 3.0.1 and the unofficial 2.8.6.0.6 version.
Click to expand...
Click to collapse
When i have problems like this with system, simple "wipe system" helps 100%. So, wipe and then flash both zips
fafa77140 said:
Can you give us meta-inf already modified , I try all your step but didn't work :/
Thanks in advance
Click to expand...
Click to collapse
Ok, but check advice from above, maybe it will help you
CraZY_BoY^ said:
When i have problems like this with system, simple "wipe system" helps 100%. So, wipe and then flash both zips
Ok, but check advice from above, maybe it will help you
Click to expand...
Click to collapse
Yes I saw but was already on , only when flashed OxygenOs mod for photos stay in bootloop :/
Installed successfully... Running good...Phone feels too hot
Sent from my A0001 using Tapatalk
Just followed your guide. Wiped everything (internal storage too) flashed 12.1 with twrp then flashed ota with your meta-inf with twrp (both zip flashed via otg). Everything is ok. Great! Thank you!!
Just one question: can i flash supersu from twrp to get root?
Inviato dal mio A0001 utilizzando Tapatalk
IronJacob said:
Just followed your guide. Wiped everything (internal storage too) flashed 12.1 with twrp then flashed ota with your meta-inf with twrp (both zip flashed via otg). Everything is ok. Great! Thank you!!
Just one question: can i flash supersu from twrp to get root?
Inviato dal mio A0001 utilizzando Tapatalk
Click to expand...
Click to collapse
Yes, i used 2.67 version (systemless)
Tried prerooted boot.img, but it doesnt work for me...
is this normal? . Writing Cyanogen mod ready and i'm waiting 5 minutes to turn it on . WTF ?
CraZY_BoY^ said:
When i have problems like this with system, simple "wipe system" helps 100%. So, wipe and then flash both zips
Ok, but check advice from above, maybe it will help you
Click to expand...
Click to collapse
thanks, wipe system works for me
I modified the updater script as per OP but i got error "Package expects build fingerprint of oneplus/bacon/A0001:5.1.1/LMY48Y/YOG7DAS2K1:user/release-keys or oneplus/bacon/A0001:6.0.1/MMB29V" . Then I used the META-INF zip from the attachment, and it flashed fine. The device is at the boot logo since about 15 minutes now. I hope it does boot.
c4cyro said:
I modified the updater script as per OP but i got error "Package expects build fingerprint of oneplus/bacon/A0001:5.1.1/LMY48Y/YOG7DAS2K1:user/release-keys or oneplus/bacon/A0001:6.0.1/MMB29V" . Then I used the META-INF zip from the attachment, and it flashed fine. The device is at the boot logo since about 15 minutes now. I hope it does boot.
Click to expand...
Click to collapse
So did this work? I'm getting the same Fingerprint issue.
I simply flash COS13 by
1) flash cm-12.1-YOG7DAS2K1-bacon-signed.zip via twrp,
2)flash cm-12.1-YOG7DAS2K1-bacon recovery
https://mega.nz/#!NEBm0JoI!-PbfS3tT5Jpkt6dduG3KpEroGv2FcNqpkZBc0WrkbDA
via twrp and reboot into cos recovery,then boot into system
3) download INCREMENTAL/Update OTA zip,
4) reboot into cos recovery and updated to COS 13.
drmuruga said:
I simply flash COS13 by
1) flash cm-12.1-YOG7DAS2K1-bacon-signed.zip via twrp,
2)flash cm-12.1-YOG7DAS2K1-bacon recovery
via twrp and reboot into cos recovery,then boot into system
3) download INCREMENTAL/Update OTA zip,
4) reboot into cos recovery and updated to COS 13.
Click to expand...
Click to collapse
i have this problem too and can't resolve it. roll back to 12.1
xmoo said:
So did this work? I'm getting the same Fingerprint issue.
Click to expand...
Click to collapse
yes. i wiped and flashed both zips again, and when twrp asked to install root i selcted 'do no install', then it worked.
update TWRP to last version and all is cool . Thanks
@CraZY_BoY^ Isubstituted the original meta inf with your modified one but when I flash it on twrp 2.8.7.0 it show this error
albi97x said:
@CraZY_BoY^ Isubstituted the original meta inf with your modified one but when I flash it on twrp 2.8.7.0 it show this error
Click to expand...
Click to collapse
so, try lastest twrp
Or flash full zip from Android development forum