Database Users

JB Update file (for devs to verify)

Ok guys I managed to identify a file in /root/cache that was downloaded when downloading the firmware straight from the tablet. The file is named "dlpkgfile" and its about 230Mbs, hopefully this can help some ppl. I don't recommend you use this file if you aren't a dev, since I don't know if it can do something bad to your tablet. I have no knowledge of this type of thing, just trying to give a helping hand....
Anyways I uploaded it to my dropbox, so please only devs download it for now I don't want to get a lot of traffic in my dropbox and be shutdown or something lol
My dropbox public link was taken down due to excessive traffic, there are a couple of mirrors around the thread.

I hope someone can verify this soon. I would love to be able to update since my Tablet failed the update :/

Isn't there a way to DL into my own dropbox from yours? That should (at least in my mind) not count as downloads right?
Either way I'm waiting for someone much braver than I to grab this and explain how to flash it. By that time I'm sure it'll be rehosted somewhere else

Just wait till it gets posted on Asus's site, that's what I'll be doing...
Sent from my Transformer Pad TF300T using xda app-developers app

Pretty sure you can just rename it to *.zip and flash it through the recovery.
All the files from the folder patch need to lose their .p suffix and go in /system before you flash it.

need the doctors around

sparky28000 said:
Pretty sure you can just rename it to *.zip and flash it through the recovery.
All the files from the folder patch need to lose their .p suffix and go in /system before you flash it.
Click to expand...
Click to collapse
did that and it did open in 7zip

kindrudekid said:
did that and it did open in 7zip
Click to expand...
Click to collapse
You flashed it?
Sent from my ADR6425LVW using Tapatalk 2

aostl said:
You flashed it?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
It looks like it's the update file
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just wondering if this method: http://forum.xda-developers.com/showthread.php?t=1668173 would still work to root.

Looks like an update.zip package with a blob inside. Should be recovery flashable...
Still recommend flashing over the latest ICS US base.

it does not flash you get status error 7

Probably just a buildprop error. What ROM did you try flashing from?

tysj said:
Probably just a buildprop error. What ROM did you try flashing from?
Click to expand...
Click to collapse
stock

This should help ppl force the update coming from US firmware I think: http://forum.xda-developers.com/showthread.php?t=1803090
You need almost an intact /system to flash this.
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.3.30-20120604:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "asus/US_epad/EeePad:4.1.1/JRO03C/US_epad-10.4.2.9-20120809:user/release-keys");
assert(getprop("ro.product.device") == "EeePad" ||
getprop("ro.build.product") == "EeePad");
Click to expand...
Click to collapse
This is a diff patch update.zip.

Whatever you do DO NOT flash the blob from the dlpkgfile on a WW tf300. This will leave you with an us bootloader and for some reason I can't seem boot into the recovery after flashing. And I cannot flash any blob because it says the blob has an invalid signature.
Pretty much stuck here right now... I think I'll have to wait until jb is on the asus website.

How did you flash the blob alone?
Which firmware did you come from?

xaueious said:
How did you flash the blob alone?
Which firmware did you come from?
Click to expand...
Click to collapse
Flashed the blob via fastboot (fastboot -i 0x0B05 flash boot blob) I didn't think it would flash a whole new bootloader. And I came from WW 9.4.3.30. I can't reflash the old bootloader because fastboot doesn't want to actually flash it even though it says everything went okay.

sparky28000 said:
Flashed the blob via fastboot I didn't think it would flash a whole new bootloader. And I came from WW 9.4.3.30.
Click to expand...
Click to collapse
Well I think I'll be fine. I converted my WW to US 9.4.3.30 and am now flashing the dlpkgfile using the method I linked to.
I am not bootloader unlocked.
Quick glance at update-script seems to indicate that it shouldn't remove root from a rooted device running 9.4.3.30, but I'm not sure what's in the blob.

xaueious said:
Well I think I'll be fine. I converted my WW to US 9.4.3.30 and am now flashing the dlpkgfile using the method I linked to.
I am not bootloader unlocked.
Click to expand...
Click to collapse
I hope so.
---------- Post added at 08:45 PM ---------- Previous post was at 08:43 PM ----------
xaueious said:
Well I think I'll be fine. I converted my WW to US 9.4.3.30 and am now flashing the dlpkgfile using the method I linked to.
I am not bootloader unlocked.
Quick glance at update-script seems to indicate that it shouldn't remove root from a rooted device running 9.4.3.30, but I'm not sure what's in the blob.
Click to expand...
Click to collapse
The blob contains a boot.img, recovery.img and bootloader.img.

I already have an US bootloader. I think converting from WW to US did that.
The update.zip does not change /system/bin/su

[HOWTO] Force US10.4.2.9 Jellybean Update on Any Variant - Locked/Unlocked

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have a Canadian ASUS TF300 purchased from Futureshop. It shipped with WW firmware, and I updated OTA to WW9.4.3.30 before starting this.
I have lost root in the process. But I wasn't keep on keeping it in the first place. I kept all my apps and am now on US10.4.2.9 Jellybean Android 4.1.1. Maybe someone can chip in on how to keep root.
My device is NOT unlocked. Following this procedure requires that you root your device temporarily.
You will end up with JB with one modified binary (su, but with safe system permissions as a result of the rooting process).
This method is very time consuming (1-2 hours), so I don't recommend it for everyone. You need knowledge of ADB to proceed with this.
How To Flash (Unlocked/locked Device)
1) Convert to US9.4.3.30 using the blob:
Download US9.4.3.30 from the ASUS download page here: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+TF300T
Open the firmware download package with 7zip or similar, and extract 'blob'.
2) Copy blob into your internal memory (/sdcard/). I used adb push to do this
3) Continue following 'Method 2' from here: http://forum.xda-developers.com/showthread.php?t=1622628
(You probably want to clean up the symlink after you finish this method)
You are now on the stock US9.4.3.30 firmware
4) Perform the official upgrade to the US10.4.2.9 firmware manually
Download US10.4.2.9 from Asus: http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
Remove any external storage media attached to the device before proceeding.
The downloaded file is to be placed in the root directory of the internal storage (/sdcard). Reboot to install if the prompt to install doesn't come up right away.
(instructions by Bolandk. not tested by me.)
FROM THIS POINT FORWARD, THE INSTRUCTIONS BELOW ARE OBSOLETE AND ARE KEPT HERE FOR FUTURE REFERENCE ONLY
4) Root the firmware using the DebugFS method: http://forum.xda-developers.com/showthread.php?t=1706588
IF YOU WANT TO KEEP ROOT, FOLLOW THIS: http://forum.xda-developers.com/showthread.php?t=1840504
5) Use this method to force the FOTA update (dlpkgfile)
Download dlpkgfile from this thread:
http://forum.xda-developers.com/showthread.php?t=1840397
Follow this: http://forum.xda-developers.com/showthread.php?t=1803090
The difference is that our device does not vibrate. You want to hit 'vol up' right when your device shows any text, and this is within 5 seconds of you pressing the voldown+power combination. If you miss this, you need to recopy 'command' back into /cache/recovery.
6) The update process will start automatically. This takes 20 minutes to complete.
Region conversion instructions
Since ASUS has posted the Jellybean updates for a while now, I thought I'd update this post with instructions to change to another region.
To region convert, you need to download the firmware for the target region. Ideally you want the version you are currently on. I think you may end up losing root in the process, but I don't know a way around that at the moment.
You do not have to be bootloader unlocked to do this.
Extract the xxxUpdateLauncher.zip into the root directory of a microSD card formatted to FAT/FAT32. Then rename the file as EP201_768_SDUPDATE.zip. Reboot into the bootloader (vol - and power), and select the first option (left most square) when the menu comes up. The firmware update will start automatically in this mode.
I converted back from a US to a WW build without wiping using this method.

xaueious said:
I have a Canadian ASUS TF300 purchased from Futureshop. It shipped with WW firmware, and I updated OTA to WW9.4.3.30 before starting this.
Good luck!
Click to expand...
Click to collapse
Do you know of a way to force downgrade from Jelly Bean to ICS 9.4.3.17? I don't have any root access and need to restore it.

This works good it took me a little over an hour
but you lose root and the ability to flash a custom recovery (CWM,TWRP)
Please correct me if I am wrong

I haven't tried it this way yet, but it seems a little easier if someone wanted to try it.
jvanassche said:
Alright, after some work, I finally got this to install on my unlocked device following these steps:
1) If not already on stock, wipe everything and reflash to stock .30 update and reinstall TWRP 2.2.1.3. Be sure to backup before wiping.
2) Download the zip from the OP, and extracted it to a folder on your hard drive.
3) Open META-INF\com\google\android\updater-script in Notepad.
4) Deleted line 3 and 4 of the file. The Line to be deleted should read assert(getprop("ro.product.device") == "EeePad" ||
getprop("ro.build.product") == "EeePad");
5) Create a new zip file containing all of the files you extracted in step 2, including the modified updater-script file, and copy to your device.
6) Reboot into TWRP
7) In TWRP, under mount section, ensure all four mount options are checked, and internal memory is checked at the bottom
8) Flash the zip file you copied in step 5.
9) Reboot, and enjoy your Jelly Beans.
Click to expand...
Click to collapse

Turbojugend said:
I haven't tried it this way yet, but it seems a little easier if someone wanted to try it.
Click to expand...
Click to collapse
Just attempted this but got "install fail"
Its my 1st time creating a zip file so maybe I goofed at it. Used 7zipper.
Sent from my Nexus S 4G using Tapatalk 2

I can confirm after slaving away at this method. It does work and I am now on Jelly Bean.

Zadeis said:
I can confirm after slaving away at this method. It does work and I am now on Jelly Bean.
Click to expand...
Click to collapse
You still have root or lost after flash the rom?

wonsanim said:
You still have root or lost after flash the rom?
Click to expand...
Click to collapse
You will lose root without a modified dlpkgfile update-script.

wonsanim said:
You still have root or lost after flash the rom?
Click to expand...
Click to collapse
Unfortunately, no. I used ota root keeper and everything only for it to not work in the end...

Zadeis said:
Unfortunately, no. I used ota root keeper and everything only for it to not work in the end...
Click to expand...
Click to collapse
I'm in the same boat. I backed up root with the OTA Rootkeeper, but after the upgrade, it it doesn't restore root.
I did read in another thread, that some people were successful in restoring root in JB with OTA Rootkeeper, but they had SuperSU installed. Of course, I came across that little tidbit right in the middle of the upgrade

Actually, i'll what I said back. I actually managed to restore my root. I'm not sure what I did differently, but I have thankfully have root again!

i was able to restore root too.

FYI, this worked for me with an unlocked bootloader.
Extremely happy right now. Thanks for this.

Works great with unlocked bootloader, thanks again.

Sorry but what is the point if you already unlocked bootloader/root/install custom recovery , and now you tried to flash back to stock to get OTA update ?
- You tried to root/ flash custom rom at first place, and now you back to stock to get OTA update and you can't root once you update to 4.1.1. More important, 3-4 peoples already get their tab bricked when they tried to flash CWM after Jelly bean update as they attempt to root their device again. And now they screw up cause they can get warranty from ASUS. Why don't you guys wait couple days when developers make a new custom roms based on official 4.1.1 updated so yous just easily flash through recovery. Just my 2 cents :highfive:

sorta works
It worked sort of.
My tf300 was already "unlocked"
But the instructions didnt work exactly.
Here is what I had to do:
1. Use TWRP recovery to install the ICS official rom from ASUS
2. Use the idcrysis method for rooting after initial setup (failed the first time but worked the second try after rebooting)
3. put the dlpk file on the root of the tablet from: http://forum.xda-developers.com/showthread.php?t=1840397
4. Root the firmware using the DebugFS method: http://forum.xda-developers.com/show....php?t=1706588
5. copy "dlpkgfile" into /cache/ directory
6. create the file called "command" under /cache/recovery/
7. write this statement in the file /cache/recovery/command (without qoutes) "--update_package=/cache/dlpkgfile"
Dunno why it didnt work for me the right way but this is how I got it to work. Not root doesnt work but I can live with that till I read about rooting Jelly Bean tomorrow when I wake up.
If anyone else has issues forcing the jelly bean update these steps I did worked. I am definetely NOT a programmer, just had to follow steps from multiple posts. I kind of wished I could relock the bootloader again. This was such a pain in the rear!

OTA and Fully Removied Moded Binary
xaueious said:
I have a Canadian ASUS TF300 purchased from Futureshop. It shipped with WW firmware, and I updated OTA to WW9.4.3.30 before starting this.
I have lost root in the process. But I wasn't keep on keeping it in the first place. I kept all my apps and am now on US10.4.2.9 Jellybean Android 4.1.1. Maybe someone can chip in on how to keep root.
My device is NOT unlocked. Following this procedure requires that you root your device temporarily.
You will end up with JB with one modified binary (su, but with safe system permissions as a result of the rooting process).
This method is very time consuming (1-2 hours), so I don't recommend it for everyone. You need knowledge of ADB to proceed with this.
How To Flash (Unlocked Device)
0) Download dlpkgfile from this thread:
http://forum.xda-developers.com/showthread.php?t=1840397
1) Convert to US9.4.3.30 using the blob:
Download US9.4.3.30 from the ASUS download page here: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+TF300T
Open the firmware download package with 7zip or similar, and extract 'blob'.
2) Copy blob into your internal memory (/sdcard/). I used adb push to do this
3) Continue following 'Method 2' from here: http://forum.xda-developers.com/showthread.php?t=1622628
(You probably want to clean up the symlink after you finish this method)
You are now on the stock US9.4.3.30 firmware
4) Root the firmware using the DebugFS method: http://forum.xda-developers.com/showthread.php?t=1706588
IF YOU WANT TO KEEP ROOT, FOLLOW THIS: http://forum.xda-developers.com/showthread.php?t=1840504
5) Use this method to force the FOTA update (dlpkgfile)
Follow this: http://forum.xda-developers.com/showthread.php?t=1803090
The difference is that our device does not vibrate. You want to hit 'vol up' right when your device shows any text, and this is within 5 seconds of you pressing the voldown+power combination. If you miss this, you need to recopy 'command' back into /cache/recovery.
6) The update process will start automatically. This takes 20 minutes to complete.
Good luck!
Edit:
If you are unlocked, you might as well wait for a repacked ROM.
Click to expand...
Click to collapse
I was wondering if you do a full reset, is the device OTA Eligible for future updates and are you able to remove the moded binary by doing a full reset.

does this have any side effects, eg no more ota or is the us version crippled because of patents?

OK....can someone confirm this for me.
I am stock,locked and rooted...my OTA failed due to some frozen apps.
So I would take the dlpkgfile and place it in /cache
I would then place the "command"file from the link in #5 and place that in c/cache/recovery
Then reboot into recovery and it should install on it's own?
Can anyone confirm this for me? Anyone locked have success with this process?
Also anyone have the dlpkgfile they can mirror...the original one generated too much traffic and is no longer available.

turdbogls said:
OK....can someone confirm this for me.
I am stock,locked and rooted...my OTA failed due to some frozen apps.
So I would take the dlpkgfile and place it in /cache
I would then place the "command"file from the link in #5 and place that in c/cache/recovery
Then reboot into recovery and it should install on it's own?
Can anyone confirm this for me? Anyone locked have success with this process?
Also anyone have the dlpkgfile they can mirror...the original one generated too much traffic and is no longer available.
Click to expand...
Click to collapse
dlpkgfile

Cant find Stock ROM download

Well recently I was trying to root my Mytouch 4g Slide and ACCORDING to this thread:
http://forum.xda-developers.com/showthread.php?t=1801106
All I had to do was flash the custom ROM as it would have the root already in there.
-6. ROOT YOUR DEVICE.-
Now that you have a custom recovery, you can flash custom ROMs. These custom ROMs are already rooted with Superuser and binary files.
NOTE: If you are S-ON, installing a custom ICS ROM will require an extra step in fastboot. You will have to extract the “boot.img” from the ROM and flash it with fastboot after installing the ROM in CWM recovery. More information from Limewirelord.
HOWEVER, if you want to root the STOCK ROM and/or continue to step 7 to achieve JuopunutBear S-OFF, you’ll have to root the device yourself. This is very simple. Download Superuser ZIP from androidsu.com/superuser. I can only recommend version 3.0.7 efgh because that is the only one I have tested, but newer versions may work.
Place the “Superuser-3.0.7-efgh-signed” on the ROOT of your SD card. Go to CWM Recovery and use “install zip from sdcard” to flash the Superuser zip. If installation aborts or fails the first time, try to flash the zip again until installation is complete. Reboot your phone and check in your apps to see if Superuser app is there. If so, congratulations, you have successfully rooted your stock MT4GS!
Click to expand...
Click to collapse
Which I did.
I was using this kids download tools to get the files I wanted. So I extracted the boot.img and used this tutorial to flash it for me.
THAN I ran a back up in clockwork. I haven't put the files on my SD card yet, I was just jumping ahead and was not prepared.
So I tried to go back to my phones regular state, but it is stuck on the "MyTouch 4G" splash pages, doesn't move what so ever.
I than grew worried about the phone, and thought I just bricked it or something. I am still able to get into Clockwork and do stuff in it. I tried to do a restore from my backup, didnt work. Tried wiping everything then do the backup, didnt work.
So I said, well maybe its because its a custom boot.img or something and it doesnt want to work? Luckily I had a old Mytouch 3G laying around so I could put stuff on my SD card.
So I put everything the kid provided from his mediafire folder and placed it into the root of my SD card. Switched over to the 4G and tried to install the packages.
The first was the ROM. At first it didnt work, it gave me an error:
Code:
assert failed: getprop("ro.product.device") == "glacier" || getprop("ro.build.product") == "glacier"
By googling the error, I come to this thread: http://forum.xda-developers.com/showthread.php?t=2250785
And a few posts down, a person writes this:
Step 1.Open the ROM.zip with winrar
Step 2.Found \META-INF\com\google\android\updater-script ,use Notepad open
Step 3.delete assert(getprop("ro.product.device") == "p880" ||
getprop("ro.build.product") == "p880");
Step 4.OK,safe
Click to expand...
Click to collapse
I followed those steps, and it did work. It "Installed" this time.
I followed the rest of the steps until it got to the last package. When installing "grapefruit" my phones display shut off, and then when it went back on, I was back at the beginning of Clockwork. So I went and tried to install it again, and this time it gives me a (Status 0) error, with no other information.
I assumed that it was already installed or something, and it was just saying it is already installed.
I tried to reboot back to normal and I am still stuck where it says "Mytouch 4g"
So now I am on this thread: http://forum.xda-developers.com/showthread.php?t=1844910
And there are the download links, I click on both of them to get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And now I am here. Cant find the download for this dang it file.
Anything helpful will be greatly appreciated.

Your in the wrong forum man, the slide is called doubleshot

[GUIDE] How to flash the COS 13 update. Even if you get the release keys error

Alright.
I had this problem for a while and I figured out how to flash the update without the need to factory reset or change the update script of the update file.
Even if you get the user/release-keys error message. EXAMPLE:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You have to be using the latest lollipop release before updating. That means you have to be on YOG7DAS2K1 before attempting.
This worked out for me. But it might not work for you. I do not believe it can destroy your phone and switch some satellites off, but still, not responsible if it did so.
Requirments:
You have to have TWRP now or you at least have ROOT and any flashing app like flashify.
Download COS 13 update file. here https://www.androidfilehost.com/?fid=24459283995316311
Download the latest CyanogenMod Recovery https://download.cyanogenmod.org/?device=bacon
Download the cm-12.1-YOG7DAS2K1 full ROM [url]https://www.androidfilehost.com/?fid=24369303960686198[/URL]
Guide:
Make sure the update cyanogen recovery option is checked in developer options.
Flash CyanogenMod Recovery downloaded before.
Reboot into it.
Use the update function in CyanogenMod Recovery and choose cm-12.1-YOG7DAS2K1 as the update file. It might take a while.
Now reboot to your phone. When booted and running, reboot to recovery.
Now you are running COS recovery. Update with the incremental.
That is it.
I hope this works out for you.
EXTRA: How to ROOT and have TWRP as a recovery:
Requirements:
A laptop.
Download TWRP and adb drivers on the laptop and the SuperSU and TWRP on your phone
Download Oneplus One TWRP Recovery [url]https://dl.twrp.me/bacon/twrp-3.0.2-0-bacon.img.html[/URL]
Get any adb divers. This one suffice [url]http://forum.xda-developers.com/google-nexus-5/development/adb-fb-apx-driver-universal-naked-t2513339[/URL]
Download the latest SuperSu [url]https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip[/URL]
Guide:
Reboot into bootloader: you can do this in many ways. A simple google search will show you how. Easiest way is to turn the phone off and hold the volume up and power long enough for the phone to boot into bootloader.
Connect your phone to your laptop
Run the adb: I assume you are using windows of course. First put the TWRP .img file in this folder. Hold shift and right click in the folder downloaded above. A 'Open command window here' option will be there. Click it and write in the window
Code:
fastboot boot twrp-3.0.2-0-bacon.img
. A hint: you can just write twrp and hit TAB, it will complete the filename. Or you can rename the downloaded file to just twrp.img
Check your phone, you will be running TWRP temporarily. You now have the option to ROOT only by flashing the SuperSU file downloaded on your phone. If you reboot now you will lose TWRP and get back to the official COS Recovery. If you want TWRP for good flash the TWRP file downloaded on your phone before.
I hope this is easy. It actually is. just follow it step by step.

If you could provide us the guide to root and come back to twrp I would be extremely happy

bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
fastboot flash latest twrp and flash SuperSU BETA
THANK the post if I deserve

bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
if you need a guide to root, this means you are not rooted, and if you are not rooted most probably you already have stock recovery, which means you can just install the OTA update without any issues.

bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
Added as requested. I hope you find it easy.

y2kkingboy said:
Added as requested. I hope you find it easy.
Click to expand...
Click to collapse
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).

bisio971 said:
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
Click to expand...
Click to collapse
Yeah. I mad a mistake there. Thank you and glad it helped.

If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?

thinleytsering9 said:
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
Click to expand...
Click to collapse
As I stated before you have to be on COS 12.1 YOG7DAS2K1. This method should not format your phone or remove any data as there is no factory reset step.
As for the link they are all over the place now. I used the official one. I'll link it for your convenience.

can anyone please pull the stock recovery from COS 13, not 12. I kinda screwed up while updating and now stuck in bootloop.
Update: The issue is resolved. The issue was because of SuperSu 2.46. Installing the latest TWRP and SuperSu 2.66 fixed it. Marshmallow is now rooted!

Thank you very much! After going back to stock and still not receiving the update for more than a week (well at least it felt like a week, Lol) I decided to flash a full COS 13 zip floating around. Instantly liked the new ROM but it had root/symlink issues only to be resolved when flashing a custom kernel it seems. Not what I really wanted so then I stumbled onto your thread and this technique worked 100%! I was on DAS2K1 (flashed thru a custom recovery) already and had several failed attempts flashing just the incremental outright (thru stock recovery)., but by flashing DAS2K1 thru stock recovery first as you suggest then the incremental seems to do the trick.

I did it all the steps, but my phone doesn't not start. After optimizing aplications I have bootloop at "cyanogen modready".
L.E. I think the problem was one of old aplications. After a clean install everything works.

This is the best thing Oneplus one i ever experience.COS13 give my Oneplus one a new breathe of life .This update better than crap lolipop.No Bug for me until now,only google play service need to update twice in play store,its auto reboot itself twice and wholla,super speed UX.The best thing i ever have.I apply update from CM-12-0-YNG1TAS17L Build LRX22G using this method and it works flawlessly
I don't need to factory reset or wipe cache .
I flash full stock ROM cm-12.1-YOG7DAS2K1 and apply update through CyanogenMod Recovery only and nothing else.
Now my oneplus one is rooted and TWRP install using ADB and its fly.All rooted apps is working together with Adaway.
Thanks Cyanogen team for make this 2 years old flagship killer a beast .
Only thing not satisfied is gone signal and wifi status (connectivity indicator ).I need to swipe down to see my transfer data working (what a bummer ).
Thanks so much for this magical guide (y2kkingboy) Yours truly Oneplus one diehard fan.

I was already on cm-12.1-YOG7DAS2K1, however rooted. So even if I had been offered the OTA it would have failed.
Your guide got me updated, first time with no problems.
6.0.1 is such an improvement on 5.1.1, I tried a couple of other 6.0 roms, however this has by far been the most stable and bug free.
Cheers for the tutorial!

u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file

#sychrome# said:
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.

InsaneNutter said:
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2522762

u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
I had tried this before and it did not work for me. Kept getting an error saying "the signature file was not a complete file" and therefore it didn't flash. But it may have been editing error on my part. This method works just fine and no need to give up your data either.

Having tried many other ways, I got it done with this instruction.
Thank you!

marxu said:
Having tried many other ways, I got it done with this instruction.
Thank you!
Click to expand...
Click to collapse
Glad I helped.

[Recovery][MI 8 SE] TWRP recovery 3.2.3 update 27th Dec by LR.Team/wzsx150

Xiaomi 8 SE *only*
** Update 1227 **
Original post:
http://www.miui.com/thread-15964692-1-1.html
Mirror:
https://drive.google.com/drive/folders/1IeCtb6vRO4CRe76s0BD_5TQiSnymPBTT
------------------------------------------------------------------------------------
2018.12.27 update content:
1. Update the problem of repairing the new version of rom into twrp
2018.12.17 update content:
1. Update to fix some oil can not get twrp problem, repeatedly restart into fastboot mode
2018.11.02:
1. Update support official Android 9 rom
2. Update and optimize some functions
3. Increase automatic The option to restart after the upgrade is completed. In the twrp setting, the default is automatic restart. Uncheck the box to not restart. It is convenient to perform some operations after the automatic upgrade to prevent the twrp from being overwritten, etc.
2018.9.28 update:
1. Add support to remove Dm checksum cancels the forced encryption function. The removal of the dm check function is mainly to prevent the card screen caused by the dm check and to prevent the official rec from covering the twrp.
Cancel the forced encryption function is used to permanently decrypt the data, you need to format the data, otherwise you can not enter the system, do not understand the machine is not recommended. Please be careful! !
2. Update the built-in magisk to 16.6, which is said to be the latest version of the card screen. The updated version will cause the card screen. At the same time fix the bug that the built-in magisk can't brush the module.
TWRP v3.2.3 2018.8.10 update:
1. Update to 3.2.3
2. Support new version official rom
3. Added signature boot and restore official rec and other functions
4. Built-in magisk 16.3, it is said that the high version will be card screen
5. Update the decryption data mechanism, theoretically decrypt the data more stable Some
---------------------------------------------------------------------------------------
v3.2.1 didn't work flashing treble GSI, anyone have any experience with this version?

how to update to this version

Can we resize the system, data and cache partitions with this version?

Lollipopx said:
how to update to this version
Click to expand...
Click to collapse
See q792602257's thread -
https://forum.xda-developers.com/mi-8/development/recovery-twrp-recovery-3-2-1-mi8se-t3813311
Or if you have TWRP already, just flash the new zip here from TWRP.

Hi! I don't read Chinese. Can you check if there's an update for Mi 8? Thanks!

samwise110712 said:
Hi! I don't read Chinese. Can you check if there's an update for Mi 8? Thanks!
Click to expand...
Click to collapse
Mirror：https://drive.google.com/file/d/17AhL4J4qTyfp6djM_CetU3Y-gpmyifel/view?usp=drivesdk
TWRP 3.2.3-0806 for mi 8

Everythings work fine but language is set to Chinese. Here's just the way i change to English. FYI.
https://www.hellpc.net/how-to-change-language-in-twrp-recovery-to-english/

When this thread will be moved to Mi 8 SE Forum?
---------- Post added at 04:09 PM ---------- Previous post was at 04:07 PM ----------
isn't there any guide on how to flash?

t.me/joinchat/AAAAAEyDBlEI7z1R7HsXZw

danielwright said:
See q792602257's thread -
https://forum.xda-developers.com/mi-8/development/recovery-twrp-recovery-3-2-1-mi8se-t3813311
Or if you have TWRP already, just flash the new zip here from TWRP.
Click to expand...
Click to collapse
Is that possible to ask the author to make one TWRP for Mi 8 EE(Ursa)??

wching02 said:
Is that possible to ask the author to make one TWRP for Mi 8 EE(Ursa)??
Click to expand...
Click to collapse
You can Use the TWRP from MI8 and then you only have to edit the updater script in the custom.rom.zip
0. Use "MI8 TWRP" on "MI8 Explorer Edition" and install custom ROM
1. open downloaded custom "rom.zip"
2. go to -> \xiaomi.eu_multi_MI8Explorer_V10.0.4.0.OEHCNFH_v10-8.1.zip\META-INF\com\google\android\
3. edit -> updater-script
4. change -> getprop("ro.product.device") == "ursa" to getprop("ro.product.device") == "dipper"
5. enjoy

I use this recovery to flash new rom but now i can't find rise to wake any rom i flash.
help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Someone could post last September build?

new one for Android pie support.
https://drive.google.com/drive/folders/1s_m4CImuiTVLLPIzZvhcgkTjhMzPn6so
Not test yet

blu33agl3 said:
new one for Android pie support.
https://drive.google.com/drive/folders/1s_m4CImuiTVLLPIzZvhcgkTjhMzPn6so
Not test yet
Click to expand...
Click to collapse
it worked, //fastboot boot & flash recovery
test on miui8.11.1(cn)

blu33agl3 said:
new one for Android pie support.
https://drive.google.com/drive/folders/1s_m4CImuiTVLLPIzZvhcgkTjhMzPn6so
Not test yet
Click to expand...
Click to collapse
Tested on 8.11.1 from MIUI.EU to install root, it works!thanks!:highfive:

blu33agl3 said:
new one for Android pie support.
Not test yet
Click to expand...
Click to collapse
I test it and its works perfect. I Like wzsxr150 work.

Please help...
Everytime i install TWRP im never able to boot a new rom... ive tried miui.eu and others because i want global but the phone is stuck on the roms screen loading but never starts... no bootloop though...
other than the recovery do u install anything else? any other steps?
ty

manucas said:
Please help...
Everytime i install TWRP im never able to boot a new rom... ive tried miui.eu and others because i want global but the phone is stuck on the roms screen loading but never starts... no bootloop though...
other than the recovery do u install anything else? any other steps?
ty
Click to expand...
Click to collapse
Did you run in twrp data wipe? This is required in the first installation for the xiaomi, eu version

blu33agl3 said:
new one for Android pie support.
https://drive.google.com/drive/folders/1s_m4CImuiTVLLPIzZvhcgkTjhMzPn6so
Not test yet
Click to expand...
Click to collapse
Thanks it works with xiaomi.eu_multi_MI8SE_8.11.1_v10-9
the only workin magisk with this is only up to 16.6 any up version above give bootloop