Database Users

[RESOLVED] How do I restore factory Rom (from Revolution HD 3.0.1 on TF101)?

I am running the Revolution HD rom, this is how I purchased my TF101 from a friend, and I want to restore the factory rom so I can get ICS and the update for the battery issue until mike gets it implemented into Revolution.
How can I do this?
Thanks!

-edit- nevermind, I didn't notice you were running revolution.

If you want to flash back to stock, go to the ASUS Support site and download the 9.2.1.11 firmware for your device.
Unzip it 1 time (there is a zip file within the zip) so it will still have a zip.
Put the file on a microSD or the internal /sdcard/ directory depending on your version of CWM and where it can read.
Boot to CWM.
Install zip.
Choose the zip you downloaded.
Now you will be back to stock unrooted with stock recovery.
Then you will need to check for updates and grab the latest update from ASUS OTA.
If you want to root again you will need to vipermod option 1 to get root access.

Ah, thank you Fred! I did exactly that and it failed but it was the zip within a zip that killed me!

The update is actually failing with the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
Any ideas?

gbatt said:
The update is actually failing with the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
Here's exactly what I did to go from Revolution HD 3.0.1 back to stock Asus ICS 9.2.1.11
1. Download the firmware from Asus website. The file name was US_epaduser9_2_1_11UpdateLauncher.zip. You unzip this. You get US_epad-user-9.2.1.11.zip. You put US_epad-user-9.2.1.11.zip on your microSD card.
2. Boot into CWM
3. Factory reset
4. Clear Cache
5. Clear dalvik cache
6. Mount & Storage - format /system
7. Mount & Storage - format /cache
8. Power off(from CWM menu, might be under advanced, I forgot)
9. Boot into CWM.
10. Install zip from sdcard. Choose US_epad-user-9.2.1.11.zip on your microSD.
11. Reboot after flashing is complete.
12. You should now be on Asus stock ICS with stock recovery.
13. I didn't add any of my google accounts during the initial setup because I wanted to do it after I do the 9.2.1.17 update.
14. Shut off and do a cold boot.
Worked perfectly fine for me.
What didn't work was, I was not getting the 9.2.1.17 update afterwards.
So I rooted using Vipermod, installed CWM, and manually flashed the update through CWM. I had to re-root after the update. Simply ran Vipermod again.
Been 2+ days, and it's super stable with great battery life. Not a single random reboot or crash.

gbatt said:
The update is actually failing with the following error:
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
You probably have a custom recovery that doesn't mount the staging partition. You can mount it manually through adb in recovery "mount /dev/block/mccblk0p4 /staging" or flash a repackaged stock rom. At this point, you will probably have a stock system, but not the boot.img, bootloader, or recovery. The blob will flash the those parts, including the recovery, so you will be unrooted with a stock recovery.
sent from my cyanogen(mod) vision

gee one said:
You probably have a custom recovery that doesn't mount the staging partition. You can mount it manually through adb in recovery "mount /dev/block/mccblk0p4 /staging" or flash a repackaged stock rom. At this point, you will probably have a stock system, but not the boot.img, bootloader, or recovery. The blob will flash the those parts, including the recovery, so you will be unrooted with a stock recovery.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Ya, its ClockworkMod Recovery v3.1.0.1.
I tried Horndroids steps above and its still the same error.
I'm sorry but how do I "mount manually through adb"?
Ive only ever used clockworkMod

gbatt said:
Ya, its ClockworkMod Recovery v3.1.0.1.
I tried Horndroids steps above and its still the same error.
I'm sorry but how do I "mount manually through adb"?
Ive only ever used clockworkMod
Click to expand...
Click to collapse
I am pretty sure my CWM Recovery was 3.1.0.1 too.
Try replacing your CWM with Rogue XM Recovery http://forum.xda-developers.com/showthread.php?t=1446019

Awesome! That worked great. Thanks Horndroid!

[Q] Rooted, booting, no recovery.

My asus transformer tf101 is rooted, booting akop second latest just great.
Something broke recovery though. If I try and boot into recovery I get the EEPad logo and nothing else, it just sits there. I let it sit for 9 hours, no change.
If I hit power off -> reboot -> recovery and let it boot, it sits there. If I shut it down, boot it with volume down pressed and let it go into recovery (either automatic or volume up) it hangs also. If I tell it to boot, it's just fine though. I would like to upgrade my image, or even try changing to CM9 but I can't get into recovery to install a different image...
How do I re-install/fix recovery?

Use the recoveryinstaller app here: http://forum.xda-developers.com/showthread.php?t=1346180&highlight=recovery+installer you should still have root access on AOKP.

Recovery Installer
Did that too. Did that just now again. No change. EEE Pad just staring at me.

Then there's probably a problem with your bootloader, see my splash screen guide here, part of it involves unpacking the blob from official OTA's. You want to download the latest OTA from ASUS for Your Region. unzip it twice and there should be a file called blob, use blobtools from rayman86 (attached in my thread too) to unpack the blob. It will then split into several smaller blobs. You want the blob.ebt file. Copy only that then place on your Tf, rename it to blob with no extension again.
Then flash using the staging partition:
Originally Posted by gee one
to flash using the staging partition- you need either terminal or adb access.
the commands are:
su
dd if=/your/blob/here of=/dev/block/mmcblk0p4 # the last chars are zero pee four
reboot
Use adb or file manager or magic to save your blob somewhere on your transformer.
As it reboots, you should see a blue progress bar to indicate that it is flashing. It will reboot again and should work if you were VERY CAREFUL.

No Love
I got the blob.EBT on my transformer in /mnt/sdcard/Download, did the dd which ran without error. I rebooted, no blue bar, just the EEEPad splash as normal.

Hmm, is your Ro.Secure set to 0? that's about all I can think of right now, or you can run the same command with a CWM blob.SOS recovery and see if it does something. :/

Recovery
I'm not sure what Ro.Secure is.
I did the other thread rewrites of mmcblk0p3 and when I reboot it boots normally. I then redid the write of blob.EBT to mmcblk0p4 and rebooted. It rebooted normally but no blue bar and I still can't get into recovery.

Is it still hanging on the ASUS screen or is it booting normally then?
Ro.secure is a write security of /system/ files. If you have a custom kernel (ex. guevors) it isn't an issue, but stock might be.

Recovery
I'm running AOKP build 35 currently, not stock.
It will boot normally, but if I try to go into recovery (vol-down) then I get the EEE Pad splash and it just sits there.

Take a version of CWM's zip and run the command to flash the SOS blob in the recovery partition (simaler process to flashing EBT) also install SuperSU from market, and update superuser binary, using that try recovery installer again making sure to give it su.
It's really strange.. Did you use ROM manager?

Yes, I did use RomManager, it used to work well but I'm getting the feeling it's fallen aside?
Should I just take the "recovery-clockwork-touch-5.8.1.8-tf101-repack" or "cwm_recovery-5504_roach-tf101-r2" and the double-unzip, find the EBT as I did with the Asus firmware or do you have a link?
And thank you very much for your assistance, it is GREATLY appreciated.
Robert

Yes, so many people were having issues I actually posted a warning in the general thread.
Yes, the same process, but I don't think you should need to unpack with blobtools, just flash the blob as is, since it should be just the SOS partition anyway.
If you need external SD support, use Rouge XM's version instead, it reads from internal and external. Otherwise one of the two you mentioned (internal only).

Do I when you say flash, you mean dd to mmcblk0p4? Inside the recovery-clockwork-touch repack there is a "recoveryblob". Just dd that file?
Sorry for the stupid questions but I really dont' want a brick.

Dd that file, the recovery blob, but RESEARCH FIRST (looking up now) what mmcblk to use. I'm almost certain it's not P4 but a different one, just look around for the recovery partition section.
Edit: Turns out I was wrong, you do dd block 4, just looked at the updaterscript of RougeXM recovery.
Code:
ui_print("[AnyKernel Updater by Koush]");
ui_print("Rogue XM Recovery 1.3.0 (CWM-based Recovery v5.0.2.7)");
ui_print("Built for the Asus Transformer TF101");
set_progress(1.000000);
ui_print(" ");
ui_print("Extracting dd...");
package_extract_dir("recovery", "/tmp");
set_perm(0, 0, 0777, "/tmp/dd");
ui_print(" ");
ui_print("Extracting new recovery blob...");
package_extract_file("recoveryblob", "/tmp/recoveryblob");
ui_print(" ");
ui_print("Flashing new recovery blob...");
run_program("/sbin/busybox", "dd", "if=/tmp/recoveryblob", "of=/dev/block/mmcblk0p4");
ui_print(" ");
ui_print("Cleaning up...");
delete("/tmp/recoveryblob");

Got the blue line that time. Rebooted and used vol-down, there's recovery!
So I should go ahead and uninstall Rom Manager? How about GooManager? I like how it will keep me up to date on Roms since they can be a pain to find what's compatible and current but will just install by hand from now on.
Many thanks for the assistance, owe you a beer or two.

Uninstall rom manager, just get updates from threads manually, its worth the hassle
edit: thanks button xD

Can't boot after flash Android 4.4 with TWRP

I did with the help of this theard:
http://forum.xda-developers.com/showthread.php?t=2145848
Code:
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
Then I flash it with TWRP 2.6.3.0
After flashing I got this message:
Code:
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip "filename"
E: Error installing zip file 'filename'
I tried Dalvik/Cache wipe but it didn't help.
Now I can't boot into Android, it show GOOGLE and then blank screen
I can go to TWRP but when I try to use ADB sideload to connect with my computer, I get this message:
Code:
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip "inner.zip"
E: Error installing zip file 'inner.zip'
I don't have any rom in SDcard but the file "signed-occam-KRT16S-from-JWR66Y"
May anybody help me with this problem, please
In the worst case, where can I fix my phone with fee

Any changes to the /system partition or by rooting can cause OTA to fail. Flashing OTA is only recommended to a pure untouched stock rom.
Follow the guides in my signature to flash 4.4 without wiping your data.

mecatro said:
I did with the help of this theard:
http://forum.xda-developers.com/showthread.php?t=2145848
Code:
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
Then I flash it with TWRP 2.6.3.0
After flashing I got this message:
Code:
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip "filename"
E: Error installing zip file 'filename'
I tried Dalvik/Cache wipe but it didn't help.
Now I can't boot into Android, it show GOOGLE and then blank screen
I can go to TWRP but when I try to use ADB sideload to connect with my computer, I get this message:
Code:
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip "inner.zip"
E: Error installing zip file 'inner.zip'
I don't have any rom in SDcard but the file "signed-occam-KRT16S-from-JWR66Y"
May anybody help me with this problem, please
In the worst case, where can I fix my phone with fee
Click to expand...
Click to collapse
why dont you just search your issue and for fixes... Put your phone in recovery and use adb to push over a rom. I dont want to be the bad guy here but why flash an OTA zip if you are already rooted just flash a stock rom. So many of you make things so much harder for yourself than it has to be.
Sorry for bashing you but you also should always keep a nandroid on your phone. Do some research or try what I suggested and good luck but for future reference be mindful of what may happen if things go wrong

playya said:
why dont you just search your issue and for fixes... Put your phone in recovery and use adb to push over a rom. I dont want to be the bad guy here but why flash an OTA zip if you are already rooted just flash a stock rom. So many of you make things so much harder for yourself than it has to be.
Sorry for bashing you but you also should always keep a nandroid on your phone. Do some research or try what I suggested and good luck but for future reference be mindful of what may happen if things go wrong
Click to expand...
Click to collapse
I used OTA because I didn't want to reset my phone. I know it was stupid
I read some topic and they said my problem is TWRP 2.3.6 isn't compatible with android 4.4
(I should use CWM is).
I think now I have some think like android 4.4 in my phone but it can't boot
The problem now is I can go to recovery but can't usse adb to push a rom.
I tried some search but there was no help

eksasol said:
Any changes to the /system partition or by rooting can cause OTA to fail. Flashing OTA is only recommended to a pure untouched stock rom.
Follow the guides in my signature to flash 4.4 without wiping your data.
Click to expand...
Click to collapse
Thank you. I flash Google's ROM with fastboot and it's working now.

cyanogenmod M6 All-F2FS

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

[HOW TO] Clean route to XNP44S keeping Root + Xposed + Kernel (No wipe)

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