Related
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
NVFlash backups, please do them before flashing anything below otherwise you will **** out of luck if you brick
Download:
cm-12-20150219-UNOFFICIAL-tf201.zip
cm-12-20150321-UNOFFICIAL-tf201.zip
cm-12.1-20150405-UNOFFICIAL-tf201.zip
cm-12.1-20150713-UNOFFICIAL-tf201.zip
Recovery:
recovery.img
Note that the touch buttons are really close together and there's no confirmation before you want to flash a zip sooooo... use the power keys if you are extra scared/careful.
In addition, the script output is impossible to see, which is kinda problematic.
XDA:DevDB Information
Cyanogenmod 12.1 Unofficial, ROM for the Asus Eee Pad Transformer Prime
Contributors
Namidairo, Androidroot, CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-02-15
Last Updated 2015-04-05
Hi. I see no download section. So do I use the current recovery or should I wait? Using twrp with f2fs.
Hi,
What's the differences with official cm12 for tf300t?
I tested tf300 official and had lots of problems and I would prefer not to have them again ?
hi, please upload f2fs recovery if this rom support f2fs.thank you!
Edit: all is good. I'm back on track.
Ahhhh. I used the one from cm11 topic. Big mistake. Now I'm getting android service icon flashing screen. Reboot is the same, can't access fastboot or bootloader or recovery, tablet is recognized by pc. Attached the picture of what is on my screen if anyone has an idea.
Just curious. Installed cm recovery, the rom and gapps (the smallest ones) and now waiting at Asus bootlogo. How long does the first boot take?
I have the same problem. My TF201 is stuck at the bootscreen with the Asus-logo.
What did I do:
- wiped cache
- factory reset
- flashed recovery.img from post #1
- flashed firmware from post #1
- reboot and stuck at Asus-logo
I can still reboot into the recovery.
Where did I go wrong?
Just flash the last cm11 with f2fs support to get the tablet working. No need to change recovery.
suhiSLO said:
Just flash the last cm11 with f2fs support to get the tablet working. No need to change recovery.
Click to expand...
Click to collapse
thx reply,
i listed the step as below. am i right?
1)download recovery_f2fs on cm11 section
2)use the code format mmcblk
mkfs.f2fs -t 0 /dev/block/mmcblk0p2
mkfs.f2fs -t 0 /dev/block/mmcblk0p8
Click to expand...
Click to collapse
3)install cm12
4)reboot
if i were wrong,may i know the step and compatible recovery download link?
suhiSLO said:
Just flash the last cm11 with f2fs support to get the tablet working. No need to change recovery.
Click to expand...
Click to collapse
Why should I flash CM11 (KitKat) when I want CM12 (Lollipop, that this thread is about)?
I used the software (recovery, firmware) that Namidairo posted in his first post in this thread.
GoldenAvatar said:
Why should I flash CM11 (KitKat) when I want CM12 (Lollipop, that this thread is about)?
I used the software (recovery, firmware) that Namidairo posted in his first post in this thread.
Click to expand...
Click to collapse
Just to make the tablet working until namidairo offers a solution. At least that's what I did.
---------- Post added at 04:41 PM ---------- Previous post was at 04:34 PM ----------
atoyu said:
thx reply,
i listed the step as below. am i right?
1)download recovery_f2fs on cm11 section
2)use the code format mmcblk
3)install cm12
4)reboot
if i were wrong,may i know the step and compatible recovery download link?
Click to expand...
Click to collapse
If you want to try to make cm12 work use the recovery from this topic. I replied to goldenavatars post.
when using recovery on this topic, it hold on asus boot screen......
any md5 for this file?
Did the install using TWRP 2.7.0.0 and also flashed the gapps-lp, On reboot screen stuck at the Asus logo and will not proceed. Is there a md5 available for the ROM zip file so I can do a check?
I am currently running namidairo's CM11 build on my TF201. Do I just flash the recovery and then this image to get lollipop?
Also was GAPPS work with this build?
Thanks.
Oops, SELinux chucks a fit about some of the vendor libs when I set it to enforcing.
This is why you actually test with the same kernel that you are deploying. (Reboot shenanigans meant the bootloader ignored my staging partition and didn't flash the new kernel, yay.)
Anyway, I'll pull the zip and upload one with it set to permissive for now (Which is a temporary fix, I'll fix up the sepolicies when I have time)
Edit: Up
Working. Thank you.
Namidairo said:
Oops, SELinux chucks a fit about some of the vendor libs when I set it to enforcing.
This is why you actually test with the same kernel that you are deploying. (Reboot shenanigans meant the bootloader ignored my staging partition and didn't flash the new kernel, yay.)
Anyway, I'll pull the zip and upload one with it set to permissive for now (Which is a temporary fix, I'll fix up the sepolicies when I have time)
Edit: Up
Click to expand...
Click to collapse
Can't wait to try this later tonight
Yup, same.
Missing superSU. So additional apk install needed. I tried to install zip version but it looks like it didn't stick.
suhiSLO said:
Missing superSU. So additional apk install needed. I tried to install zip version but it looks like it didn't stick.
Click to expand...
Click to collapse
Did you enable root in developer options?
New bootloader: boot to recovery enabled for select devices.
http://fxpblog.co/2015/05/01/finally-boot-to-recovery-enabled-in-special-bootloaders-from-sony.html
adfurgerson said:
New bootloader: boot to recovery enabled for select devices.
http://fxpblog.co/2015/05/01/finally-boot-to-recovery-enabled-in-special-bootloaders-from-sony.html
Click to expand...
Click to collapse
Zu is not included yet. This is what HTC has been doing for ages. Not sure why everyone does it this way...
There are two rules in life for being successful:
1. Never reveal everything you know;
2.
Sony has now made these available for a variety of Xperia devices, including the Rhine family (which the Z Ultra is). Excellent news! Thank you, Sony ❤
Would this new bootloader brick the Z Ultra GPE?
ZU is now supported but I tried flashing it today over stock 5.0.2. Foraging showed as successful but nothing happens when I try to boot into recovery. The phone just reboots normally
What benefits is thing going to offer over what we previously had? Trying to figure out if I should wait with anticipation or apathy.
fzurita said:
Would this new bootloader brick the Z Ultra GPE?
Click to expand...
Click to collapse
most likely it will brick your gpe. And you don't need this "new" boot loader, Gpe has all the features already. It's just Sony devices had the function removed.
This boot loader allows booting directly to recovery without having to go through the boot partition. GPE doesn't let you do that right?
halifage said:
ZU is now supported but I tried flashing it today over stock 5.0.2. Foraging showed as successful but nothing happens when I try to boot into recovery. The phone just reboots normally
Click to expand...
Click to collapse
I followed the directions and it said the device has no new updates. Where did you download the firmware? I have a C6806.
Thanks
alphahere said:
I followed the directions and it said the device has no new updates. Where did you download the firmware? I have a C6806.
Thanks
Click to expand...
Click to collapse
As far as I can tell, only c6833 is supported so far.
But if you wanna give it a try, head over to sonymobile.com/developer. you have to install the Sony flash tool for xperia devices.
when you open the flash tool and connect your device as instructed on the website, it will show all the available 'services' you can flash to your device.
Have you guys succeeded in booting to recovery? Coz I have flashed TWRP to recovery partition and it doesn't boot
Regards
Would be interesting if the GPe stock firmware can be flashed after this, since GPe and the normal ZU are more euqal than ever with that.
Anyone tried to flash stock GPE after this flash ?
Since a lot of you guys seem to not get into recovery after installing the new sony bootloader i might share how i succesfully did it...
I've installed the new Sony-Bootloader (or how Sony calls it "TA-Update") on my Z-Ultra (C6833)
After that i immediatly booted into fastboot and flashed twrp to the recovery partition (fastboot flash recovery FILENAME)
Succesfully booted into the twrp-recovery version i flashed
Device didn't got wiped, but cache partition did get wiped
But i was running twrp-recovery (but im pretty sure it wasn't the newst version) before on fotakernel, also i was running aicp-rom
Didn't do any experiments afterwards, but we'll see what happens after i flash a new rom
Hey guys.......i have zu c6802 which isn't supported in emma yet.....so is it possible for me to get this new bootloader???????
caspianprince said:
Hey guys.......i have zu c6802 which isn't supported in emma yet.....so is it possible for me to get this new bootloader???????
Click to expand...
Click to collapse
me too
alia5 said:
I've installed the new Sony-Bootloader (or how Sony calls it "TA-Update") on my Z-Ultra (C6833)
After that i immediatly booted into fastboot and flashed twrp to the recovery partition (fastboot flash recovery FILENAME)
Succesfully booted into the twrp-recovery version i flashed
Device didn't got wiped, but cache partition did get wiped
Click to expand...
Click to collapse
Didn't work for me. Did the same but it didn't boot to recovery, it booted up normally. I had twrp installed in FOTA, too.
I flashed in a virtual machine with Windows Vista since I wasn't able to get Emma running in my Windows 10 x64 Pro.
Sent from my Sony Xperia Z Ultra
Flashing stock 14.6.A.0.368 installed the recovery partition for me. (C6806, which Emma is still to provide me with the partition)
The trick is to actually find a recovery that is written to work in the recovery partition, Saatvik Shukla has posted a build of TWRP over in the developement forum which works. The "Official" version over at twrp.me doesn't
pTeronaut said:
Flashing stock 14.6.A.0.368 installed the recovery partition for me. (C6806, which Emma is still to provide me with the partition)
The trick is to actually find a recovery that is written to work in the recovery partition, Saatvik Shukla has posted a build of TWRP over in the developement forum which works. The "Official" version over at twrp.me doesn't
Click to expand...
Click to collapse
Thanks man, I searched for something like that but didn't found that. That explains why it didn't boot the recovery. I'll try that later.
EDIT: It works
Sent from my Sony Xperia Z Ultra
Installing the new Sony Bootloader and Recovery
THIS IS FOR ALREADY UNLOCKED DEVICES!
DO NOT TRY THIS ON A GPE!Since a lot of people seem to have problems keeping their recovery when flashing Lollipop-ROMs i decided to put up this little guide...
You can also Skip this whole guide, by just flashing the newest stock-FW at least once!
First off, as already said, this is for already unlocked devices. You can use this Guide until "Install Custom ROM", except the rooting part, for rooting use this, if you haven't already!
Don't do it if you don't atleast somewhat know what you are doing.
I am not responsible for bricked devices, or whatever you might end up with.
So, lets get started.
1. Download Sonys FlashTool "EMMA" and install it: http://developer.sonymobile.com/downloads/tool/flash-tool-for-xperia-devices/
In the .zip file from the FlashTool you'll find a File "customization.ini"
Copy this file to the installation directory of EMMA, usually "C:\Program Files (x86)\Sony Mobile\Emma"
If you don't copy that file, Emma will ask you for a login, don't create an account there, you will NEVER get any activation-email!
2. Open EMMA and boot your Phone into FlashMode (Power off your device -> Press and hold volume DOWN -> while pressing volume DOWN insert USB-Cable)
3. Emma should now recognize your device, but you have to select it manually tough. Select your EXACT model number. Again, I am not responsible for any bricked devices or whatever you end up with!
Now select the "(Open Devices) TA update" and click "Apply Service"
It should take a few seconds and should then display SUCCESS.
You can now close Emma
4. If you haven't already download FastBoot and Drivers: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
(Run as Administrator!)
5. Download the newest version of twrp and put it somewhere:
New Inoffcial twrp-3.0.0 build by me: http://forum.xda-developers.com/xperia-z-ultra/development/togari-twrp-recovery-3-0-0-t3314440
Old official versions: https://twrp.me/devices/sonyxperiazultra.html
6. Finally boot up you Phone in FastBoot-mode (Power off -> press and hold volume UP -> while pressing wolume UP insert USB-Cable
Your LED should now light up blue
Shift+Rightklick in the Folder where you have put TWRP recovery, and select "Open Commandprompt here"
Now write "fastboot flash recovery FILENAME_OF_TWRP_FILE"
You can now unplug your USB-Cable and boot into recovery and continue from there.
Your recovery will be permanent, meaning you won't loose it or replace with any other recovery that might come with your ROM.
I hope this was somewhat helpfull
Any one can flash this to C6806?
jacklau2000 said:
Any one can flash this to C6806?
Click to expand...
Click to collapse
You can try, just select your modelnumber in emma
If the "Open Devices (TA Update)" show up, you're fine. If not just don't do anything.
But do not try this on a GPE!
alia5 said:
You can try, just select your modelnumber in emma
If the "Open Devices (TA Update)" show up, you're fine. If not just don't do anything.
But do not try this on a GPE!
Click to expand...
Click to collapse
tried, but no luck. thanks.
It's really weird, I used emma, and installed their latest ta update. Now I can get into fastboot mode, all commands execute successfully, but the recovery never takes. The vol down + Power doesn't work, nor does 'adb reboot recovery'. Am I missing a step somewhere? This isn't my first android device, but from where I sit, it seems like something is up with my xzu.
If I try and install the 14.4* update through emma, it goes through the whole process, completes "successfully", then boots into 14.5. Something is clearly not working here.
The TA update only unlocks the ability to boot to recovery, it doesn't install one. And no, flashing official TWRP to recovery partition doesn't work, it must be compiled again to work on normal recovery partition and not in FOTAKernel, where it must be flashed to work.
Regards
teddy74eva said:
The TA update only unlocks the ability to boot to recovery, it doesn't install one. And no, flashing official TWRP to recovery partition doesn't work, it must be compiled again to work on normal recovery partition and not in FOTAKernel, where it must be flashed to work.
Regards
Click to expand...
Click to collapse
I´m on CM 11 M12 (looking forward to 12) + the new sony bootloader without any custom Kernel stuff.
Sadly, you are right. It´s not done with downloading twrp-2.8.5.0-togari.img and fastboot flash recovery yourfile.img.
The last offical TWRP release for Xperia Z Ultra is from february 2015, any chance they release an updated version for the new Sony bootloader?
Hermann1222 said:
I´m on CM 11 M12 (looking forward to 12) + the new sony bootloader without any custom Kernel stuff.
Sadly, you are right. It´s not done with downloading twrp-2.8.5.0-togari.img and fastboot flash recovery yourfile.img.
The last offical TWRP release for Xperia Z Ultra is from february 2015, any chance they release an updated version for the new Sony bootloader?
Click to expand...
Click to collapse
I will try to compile one because, you know, summer holidays and no school however I don't know if I will make it.
Regards
Is there any (wish for TWRP) recovery for togari, which use the new bootoader?
FYI:
My device is a brazilian c6843.
Emma recognizes the device automatically and indicates with an exclamation point that there is no services available to the unit.
In the case someone doesn't know, it's basically the c6833 with DTV 1seg. It's totally compatible with c6833 firmware, losing TV, of course.
You sir are the real hero! Thank you!
I have a xzu running cm12.1, and I have 2 quick questions for those with more knowledge than me
Is it possible to flash the new bootloder using the open source FlashTool?
If I have to use emma, is it possible to just apply the open device ta update *without* installing stock firmware first?
pbgapski said:
If I have to use emma, is it possible to just apply the open device ta update *without* installing stock firmware first?
Click to expand...
Click to collapse
You can totally do that, BUT, the newest stock firmware also has some firmware updates regarding nfc, also having the newest stock rom flashed at least once will be kind of a requirement to get everything properly working on marshmallow roms.
So I would say flash the newest stock rom at least once!
missing clues on new recovery partition
alia5 said:
You can totally do that, BUT, the newest stock firmware also has some firmware updates regarding nfc, also having the newest stock rom flashed at least once will be kind of a requirement to get everything properly working on marshmallow roms.
So I would say flash the newest stock rom at least once!
Click to expand...
Click to collapse
I followed your advice, but it seems I am missing a few clues.
My sirius was on cm12.1. I backedup and flashed D6543_23.4.A.1.232_1281-5466_R6C.ftf with flashtool on linux. I tried to use emma (several times) afterwards to check for any TA updates, but all I got was "no services matched this device" or something like that. Google tells me I am not the only one with this issue with emma
Then I used fastboot to install twrp 3 from twrp.me to recovery partition, but I could not access twrp.
I fastbooted recovery again with twrp 2.8.7, and this time I could enter twrp and reflashed CM.
Now I can access twrp using the button combinations while booting, but rebooting to recovery from CM leads to a bootloop. Has anyone experienced this as well?
So it seems I am still missing a few clues to using the recovery partition. Is any build of twrp supposed to work on both FOTAkernel and recovery partitions?
Is there a TWRP 3 build that works from 'coldboot to recovery' and 'cm reboot to recovery' with the new bootloader? Any pointers?
pbgapski said:
Now I can access twrp using the button combinations while booting, but rebooting to recovery from CM leads to a bootloop. Has anyone experienced this as well?
So it seems I am still missing a few clues to using the recovery partition. Is any build of twrp supposed to work on both FOTAkernel and recovery partitions?
Is there a TWRP 3 build that works from 'coldboot to recovery' and 'cm reboot to recovery' with the new bootloader? Any pointers?
Click to expand...
Click to collapse
Well, booting to recovery on separate partition from os, requires the rom to have a patch... the "new" mm-roms (when they finally hit aka. are ready to be shared in public) will have that, so no worry, just wait.
why it said my phone have no available service, i am on c6833
alia5 said:
Well, booting to recovery on separate partition from os, requires the rom to have a patch... the "new" mm-roms (when they finally hit aka. are ready to be shared in public) will have that, so no worry, just wait.
Click to expand...
Click to collapse
I have the same problem but not bootloop just stuck at starting apps screen,BTW did you have a TWRP scripts for flashing TWRP 3.0 into FOTAkernel
hi .. after this update can i relock my phone and restore drm functions?! or phone go to unlocked forever?!
pls help i need answer
erfanzz said:
pls help i need answer
Click to expand...
Click to collapse
Search the forums on how to backup TA partitions. I have mine but never tried to restore them
TWRP 3.0.2-0 for Xperia Z Ultra
Alternative: MusterMaxMueller's build with MultiROM support (requires a kexec hardboot patched kernel):
http://forum.xda-developers.com/showpost.php?p=67108468&postcount=89
Up-to-date TWRP with new looks and functional display/brightness settings.
Download:
http://forum.xda-developers.com/devdb/project/?id=13710#downloads
Built in an OmniROM tree, with TWRP commits currently up to and including this one.
To use, make sure you have installed the new bootloader by flashing the latest stock Sony ROM at least once.
Then, erase the recovery partition and flash TWRP using fastboot.
Code:
fastboot erase recovery
fastboot flash recovery twrp-3.0.2-0-togari.img
To enter recovery:
Switch off the phone
Hold Vol-Down & Power button simultaneously until the phone vibrates
Release the power button and keep holding Vol-Down until the Sony logo appears
Device sources:
https://github.com/olefb/device-sony-togari/commits/android-6.0
https://github.com/olefb/android_device_sony_rhine-common/tree/android-6.0-twrp
https://github.com/olefb/android_device_sony_common/tree/android-6.0-twrp
https://github.com/olefb/android_kernel_sony_msm/tree/android-6.0-f2fs (thanks, @MusterMaxMueller)
Thanks to all contributors to the Sony AOSP program, the FreeXperia team, and to OmniROM/TWRP
XDA:DevDB Information
TWRP Recovery for Xperia Z Ultra (togari), Tool/Utility for the Sony Xperia Z Ultra
Contributors
Triflot
Version Information
Status: Snapshot
Current Stable Version: 3.0.2-0
Created 2016-02-03
Last Updated 2016-05-31
How I can be sure my Z Ultra running new bootloader?
I have installed last rom 14.6.A.1.236 via flashtool
I tried to use the sony tool but I don't receive mail for activation. I use a gmail account
Obi-Wan said:
How I can be sure my Z Ultra running new bootloader?
I have installed last rom 14.6.A.1.236 via flashtool
I tried to use the sony tool but I don't receive mail for activation. I use a gmail account
Click to expand...
Click to collapse
You need to put the Customization.ini file in Emma's folder prior to running, as per the instructions. Then it won't need a login.
A full guide by alia5 here.
Obi-Wan said:
How I can be sure my Z Ultra running new bootloader?
I have installed last rom 14.6.A.1.236 via flashtool
I tried to use the sony tool but I don't receive mail for activation. I use a gmail account
Click to expand...
Click to collapse
You should already have the new recovery, it will have been installed/ partitioned when you first installed Stock 5.1.1. (The method described in the link above or even using Emma does not work on C6806 by the way.)
It does require an unlocked bootloader for it to be active though.
-------------------------------------------------------------
Doesn't work on my C6806, device just continues to boot the OS.
I have the recovery partition as I can access championswimmer's build of CWM or Saatvik Shukla's build of TWRP 2.8.5.0 if flashed into recovery. (and a build of TWRP-2.8.7.0 that I forgot that I had downloaded from somewhere in December)
Hi. Are you going to make a TWRP 3.0 build_?
fnldstntn said:
Hi. Are you going to make a TWRP 3.0 build_?
Click to expand...
Click to collapse
Thread updated with TWRP 3.0.0-0.
Enjoy.
Triflot said:
Thread updated with TWRP 3.0.0-0.
Enjoy.
Click to expand...
Click to collapse
Not working on C6806, keeps rebooting, your build of 2.8.7.0 didn't work either, that went straight to booting the OS.
C6866. Works good with sony new bootloader.
pTeronaut said:
Not working on C6806, keeps rebooting, your build of 2.8.7.0 didn't work either, that went straight to booting the OS.
Click to expand...
Click to collapse
If you have the new bootloader, you go into recovery differently.
Instructions are provided by sone here: http://developer.sonymobile.com/201...for-a-range-of-unlocked-xperia-devices-video/
alia5 said:
If you have the new bootloader, you go into recovery differently.
Instructions are provided by sone here: http://developer.sonymobile.com/201...for-a-range-of-unlocked-xperia-devices-video/
Click to expand...
Click to collapse
I know, I can flash into the recovery partition (and access) three different recoveries, See my previous post.
@pTeronaut sorry didn't read that
----
There is an "issue" with the fstab and recovery.init.rc script with this recovery.
I just built crDroid-mm, and the mountpoints of the "new" install scripts don't work with this build of twrp, since there is a missing symlink (github commit)
If any1s interested, i've gone ahead and also built twrp 3.0.0 for our togari
How can I check if I have new partition for recovery? I flashed with flashtool .216 firmware a month ago. Now I have gpe port with recovery in kernel. Is possible to have recovery in kernel (old recovery) and in the same time new recovery?
If You flashed/updated to newest fw at least once You have new bootloader with /recovery.
Sent using XT1562 - Resurrection Remix/Ultra Kernel
Uploaded a new version with the fixed symlink, as pointed out by @alia5.
Still no idea about the C6806, sorry.
Triflot said:
Uploaded a new version with the fixed symlink, as pointed out by @alia5.
Still no idea about the C6806, sorry.
Click to expand...
Click to collapse
Now we should have 2 identical twrp-3.0 versions here, oh well...
We figured it out... his (the(?))C6806 doesn't have the seperate recovery partition....
Shouldn't Fastboot flash recovery [image] result in an error if the partition isn't there?
pTeronaut said:
Shouldn't Fastboot flash recovery [image] result in an error if the partition isn't there?
Click to expand...
Click to collapse
In my experience, it flashes it to FOTAKernel, or just doesn't do anything without throwing any errors (rather stating it has flashed it succesfully)
alia5 said:
In my experience, it flashes it to FOTAKernel, or just doesn't do anything without throwing any errors (rather stating it has flashed it succesfully)
Click to expand...
Click to collapse
You can also use the Emma Bootloader and flash it into recovery via:
Code:
fastboot flash recovery FILENAME OF YOUR RECOVERY
fastboot reboot
But this way needs UB
PDesire said:
You can also use the Emma Bootloader and flash it into recovery via:
Code:
fastboot flash recovery FILENAME OF YOUR RECOVERY
fastboot reboot
But this way needs UB
Click to expand...
Click to collapse
Only on C6833 & C6802
Emma doesn't find any 'services' for C6806 (NA LTE ) & C6843 (Brazil with OTA TV) variants.
An update on my attempt to get TWRP 3.0.0.0 installed and working on my C6806.
My previous attempt was coming from flashing stock roms from 5.0 onwards using Flashtool or PC companion.
This time, I relocked the bootloader & flashed the FTF of 14.3.A.0.681 (4.4.2) and let my phone update itself all the way to 14.6.A.1.236, re-unlocked the bootloader, and tried to flash TWRP again.
This time I was successful, either Flashtool and/or PC companion cannot handle the repartitioning, or they mispartitioned my phone the last time around.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
BUG :
OTG
Lemme know
Install guide:
Boot :
Code:
fastboot boot <twrp.img>
Download: here
Contributors
imjyotiraditya
Thx to jjjhitel for his EROFS patch
Source Code: https://github.com/TeamWin/android_bootable_recovery
https://github.com/imjyotiraditya/device_xiaomi_odin-twrp
thanks and reserved
thanks and reserved
treid it this morning, and it looks and feels great so far.. no errors.
Would it be possible for somebody to post a guide for this, never installed it before?
jrvenge said:
Would it be possible for somebody to post a guide for this, never installed it before?
Click to expand...
Click to collapse
I'm not entirely sure what you mean tbh. Would you mind to explain?
imjyotiraditya said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
BUG :
OTG
Lemme know
Install guide:
Boot :
Code:
fastboot boot <twrp.img>
Download: here
Contributors
imjyotiraditya
Thx to jjjhitel for his EROFS patch
Source Code: https://github.com/TeamWin/android_bootable_recovery
https://github.com/imjyotiraditya/device_xiaomi_odin-twrp
Click to expand...
Click to collapse
Hey, i wanted to report a bug...
After i installed twrp permanently by advanced settings, i lost the touchscreen, after i rebooted into recovery.
SanHelios said:
Hey, i wanted to report a bug...
After i installed twrp permanently by advanced settings, i lost the touchscreen, after i rebooted into recovery.
Click to expand...
Click to collapse
how did u recover sir ? flashed original boot.img?
jrvenge said:
Would it be possible for somebody to post a guide for this, never installed it before?
Click to expand...
Click to collapse
as of now, no use of flashing twrp as there are no proper custom rom, but inorder to put this ur phone should be unlocked, to do that follow this guide https://forum.xda-developers.com/t/...to-eu-rom-and-root-guide-with-magisk.4338671/
vamsi209 said:
how did u recover sir ? flashed original boot.img?
Click to expand...
Click to collapse
Kinda... i booted the twrp-recovery bootimage by using
fastboot boot twrp.img
that brought me back to twrp and restored touchscreen-control. In twrp i formatted the device and completely wiped all partitions, so i would have a clean install. After all that was done i returned to bootloader and used the fastboot-image to clean-flash everything. I wanted to do this anyways, so no biggy.
It's still okay to use it, but installing it on the device as permanent recovery doesn't work as long as the touchscreen doesn't work at all.. but when this is fixed, go for it.
already did all of it...
vamsi209 said:
as of now, no use of flashing twrp as there are no proper custom rom, but inorder to put this ur phone should be unlocked, to do that follow this guide https://forum.xda-developers.com/t/...to-eu-rom-and-root-guide-with-magisk.4338671/
Click to expand...
Click to collapse
already did all of it...
SanHelios said:
Hey, i wanted to report a bug...
After i installed twrp permanently by advanced settings, i lost the touchscreen, after i rebooted into recovery.
Click to expand...
Click to collapse
Fixed!
Thanks for reporting..
vamsi209 said:
as of now, no use of flashing twrp as there are no proper custom rom, but inorder to put this ur phone should be unlocked, to do that follow this guide https://forum.xda-developers.com/t/...to-eu-rom-and-root-guide-with-magisk.4338671/
Click to expand...
Click to collapse
Phone is already unlocked as im running 21.9.28 lol
jrvenge said:
Phone is already unlocked as im running 21.9.28 lol
Click to expand...
Click to collapse
to just run this twrp, u can boot your device to bootloader, open terminal or powershell, and use command
fastboot boot twrp*.img
this will boot your twrp recovery,
as mentioned by @SanHelios there seems to be a small bug when u r flashing it permanently as recovery,
and the dev already got a fix for the same, he will mostly update the links tomorrow, i tested and it was working,
this is the file he provided, link, @SanHelios test this mate
download the above file,
use fastboot boot twrp*.img, and go to advance, and click on flash current twrp,
it will patch your boot.img file and flash the patched boot.img with twrp recovery
use volume up and power button combo to boot into twrp
imjyotiraditya said:
Fixed!
Thanks for reporting..
Click to expand...
Click to collapse
Thx for your awesome work, man..
I still dont get what it actually does lol
jrvenge said:
I still dont get what it actually does lol
Click to expand...
Click to collapse
You mean, the general function of TWRP?
yes
jrvenge said:
yes
Click to expand...
Click to collapse
TWRP is a well-rounded recovery for android-devices. There's a lot it can do, but basicly, you use it to flash/install software or images on your device. If there is a custom rom you wanna use, you flash it via TWRP, since the stock roms-recoveries only flash/install their associated roms. Apart from that, you can wipe or format your device, so it will be "clean" if you want to make a fresh installation.
In the past it was simple to install it, because devices were mostly A-only devices with a dedicated "recovery"-partition. To install it, the most common way was
- Boot into Fastboot mode, connect android via USB
- open computer CLI/Shell-window
- "fastboot flash recovery twrp.img" - Enter
The Mi Mix 4 is an A/B-Device, which means that the vital partitions are doubled and there's no "recovery"-partition anymore, since all recovery-functions are parked in a different partition. TWRP offers the ability to install itsself according to the A/B-Partitions-scheme and therefore becoming the new System-Recovery. Here the installation-steps are different.
- Boot into Fastboot mode, connect android via USB
- open computer CLI/shell-Windows
- "fastboot boot twrp.img" - Enter <- Starts the system using the image
- Touch Advanced
- Touch "Flash Current TWRP"
If a custom rom ever becomes available, there's certain routine you want to do...
backup vital information and files
format device
wipe all partitions
flash Firmware required
flash rom
flash Google Apps i.e. Open Gapps Project or NikGapps if available and desired
wipe dalvik-cache/cache/data
Enjoy