Related
Bootloop Sony logo
oook, this was my first time that i tried to flash a rom with twro ... aaaand i messed all up.
i rooted my phone 2 days ago with kingroot then i used the [XZDualRecovery] to get twrp on my phone.
then i made a backup and wiped cache, dalvik cache, system and data ... then flashed a cyanogen mod
the only problem is that flashing cm put my phone on a bootloop on sony logo (not led neither vibration) and i can't enter the recovery neither flashmode.
sorry for the bad english
XDarkira said:
oook, this was my first time that i tried to flash a rom with twro ... aaaand i messed all up.
i rooted my phone 2 days ago with kingroot then i used the [XZDualRecovery] to get twrp on my phone.
then i made a backup and wiped cache, dalvik cache, system and data ... then flashed a cyanogen mod
the only problem is that flashing cm put my phone on a bootloop on sony logo (not led neither vibration) and i can't enter the recovery neither flashmode.
sorry for the bad english
Click to expand...
Click to collapse
Unlocked or locked bl? Do you know why it failed? Wrong device for ROM, or...?
levone1 said:
Unlocked or locked bl? Do you know why it failed? Wrong device for ROM, or...?
Click to expand...
Click to collapse
bootloader unlocked with the official method (i can't link it but the one from developer sony mobile)
... and it didn't fail it says that concluded succesfully then he asked to be rooted 'cause it wasn't (... i was ) and for a brain fart i swiped for start the rooting sequence (i guess i don't remember exactly)
edit:
while installing cm i couldn't install gapps ...
XDarkira said:
bootloader unlocked with the official method (i can't link it but the one from developer sony mobile)
... and it didn't fail it says that concluded succesfully then he asked to be rooted 'cause it wasn't (... i was ) and for a brain fart i swiped for start the rooting sequence (i guess i don't remember exactly)
edit:
while installing cm i couldn't install gapps ...
Click to expand...
Click to collapse
Can you get fastboot mode?
levone1 said:
Can you get fastboot mode?
Click to expand...
Click to collapse
i'm an idiot, yap it enter in fastboot
XDarkira said:
i'm an idiot, yap it enter in fastboot
Click to expand...
Click to collapse
You can use fastboot on PC, if adb installed, to flash kernel and recovery IMG, then boot into recovery, and flash new ROM or restore backup. I have Z1c, so don't have any files for you, but easy to find in forums.
levone1 said:
You can use fastboot on PC, if adb installed, to flash kernel and recovery IMG, then boot into recovery, and flash new ROM or restore backup. I have Z1c, so don't have any files for you, but easy to find in forums.
Click to expand...
Click to collapse
thank you, that was very usefull
ok, probably i messed up even more:
i wiped evrything from the phone (... again) and re failed to flash (yaeh, i'm so lucky/dumb)
now it stop before the Sony logo and simply stay with the black screen i can still enter fastboot mode but neither Emma Sony flashtool can reconize it ... but fastboot devices from cmd reconize it
XDarkira said:
ok, probably i messed up even more:
i wiped evrything from the phone (... again) and re failed to flash (yaeh, i'm so lucky/dumb)
now it stop before the Sony logo and simply stay with the black screen i can still enter fastboot mode but neither Emma Sony flashtool can reconize it ... but fastboot devices from cmd reconize it
Click to expand...
Click to collapse
Download a ROM file, (try a prf if no luck with CM), copy it onto sdcard, put sdcard in phone, download a CM boot.img to computer, (get it from a ROM zip file), and a twrp recovery.img. fastboot the 2 imgs, boot recovery, and flash ROM. Do you know why Roms aren't working? Are you using right files for your phone?
levone1 said:
Download a ROM file, (try a prf if no luck with CM), copy it onto sdcard, put sdcard in phone, download a CM boot.img to computer, (get it from a ROM zip file), and a twrp recovery.img. fastboot the 2 imgs, boot recovery, and flash ROM. Do you know why Roms aren't working? Are you using right files for your phone?
Click to expand...
Click to collapse
before i do something stupid again ..
i have to follow this step?
1) Download a ROM
2) Put it in the microSD
3) Download latest nightly form the official page of xperia z1c on cyanogenmod.org (can't link the page)
4) exctract the boot.img from the zip
5) download a twrp recovery.img
6) put them in the fastboot folder
7) open a cmd in that folder
8) fastboot boot [cm_boot filename].img
9) fastboot recovery [twrp_recovery filename].img
then reboot in twrp and flash from there?
XDarkira said:
before i do something stupid again ..
i have to follow this step?
1) Download a ROM
2) Put it in the microSD
3) Download latest nightly form the official page of xperia z1c on cyanogenmod.org (can't link the page)
4) exctract the boot.img from the zip
5) download a twrp recovery.img
6) put them in the fastboot folder
7) open a cmd in that folder
8) fastboot boot [cm_boot filename].img
9) fastboot recovery [twrp_recovery filename].img
then reboot in twrp and flash from there?
Click to expand...
Click to collapse
That's right, but I think I see where your problem might be, (unless it's just a typo). Your commands should be: for boot, 'fastboot flash boot (name of file).img; and for recovery, 'fastboot flash recovery (name of file).img.
Try again with that. There's some good files in this thread - a http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-stock-5-1-ub-t3203247
(Sorry, for some reason I thought you had a Z1. I would have linked it sooner).
levone1 said:
That's right, but I think I see where your problem might be, (unless it's just a typo). Your commands should be: for boot, 'fastboot flash boot (name of file).img; and for recovery, 'fastboot flash recovery (name of file).img.
Try again with that. There's some good files in this thread - a http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-stock-5-1-ub-t3203247
(Sorry, for some reason I thought you had a Z1. I would have linked it sooner).
Click to expand...
Click to collapse
it wasn't a typo ... thank you
ok, thank you ... i get back to twrp so now i can flash a rom throught it ... do you have a link on a good one? or a stock unbanded?
XDarkira said:
ok, thank you ... i get back to twrp so now i can flash a rom throught it ... do you have a link on a good one? or a stock unbanded?
Click to expand...
Click to collapse
I prefer to start from scratch, but I have tried some custom stock- based Roms. Of those, I would recommend anything by Munjeni, (he has a few KK and one LP ROM in the Dev forum), or DstrikerZ1. CM based Roms are great for customization and smoothness, but tend to be worse on battery, and very iffy with Xposed.
I am trying to install TWRP on my swift.
I have installed android sdk and google drivers. Windows 10 adb and fastboot dont see the swift.
ABD shows no devices listed
Fastboot shows "8bce440" when "fastboot devices" is run
fastboot -i 0x2970 erase recovery sits at "waiting for any devices"
I have uninstalled sdk twice. Restarted laptop. Tried two different usb cables.
I am stumped. Any help guys.
You did the unlock bootloader bit in settings?
ReneX10 said:
You did the unlock bootloader bit in settings?
Click to expand...
Click to collapse
Hi cheers for replying.
Yeah I've unlocked bootloader in settings.
not sure what I'm not seeing.
GigahurtzUK said:
Hi cheers for replying.
Yeah I've unlocked bootloader in settings.
not sure what I'm not seeing.
Click to expand...
Click to collapse
Love to help more, but I've always used linux to fastboot.
Pretty sure with my swift the erase cmd didn't work for me, but the flash sudo fastboot -i 0x2970 flash recovery '/home/XXXX/Downloads/crackling-t0x1.img' did
Have you tested fastboot with any other devices? just as an experiment
ReneX10 said:
Love to help more, but I've always used linux to fastboot.
Pretty sure with my swift the erase cmd didn't work for me, but the flash sudo fastboot -i 0x2970 flash recovery '/home/XXXX/Downloads/crackling-t0x1.img' did
Have you tested fastboot with any other devices? just as an experiment
Click to expand...
Click to collapse
No other devices to test with.
I will have to try linux then. I just need a usb to make a linux live usb
Cheers
GigahurtzUK said:
I am trying to install TWRP on my swift.
I have installed android sdk and google drivers. Windows 10 adb and fastboot dont see the swift.
ABD shows no devices listed
Fastboot shows "8bce440" when "fastboot devices" is run
fastboot -i 0x2970 erase recovery sits at "waiting for any devices"
I have uninstalled sdk twice. Restarted laptop. Tried two different usb cables.
I am stumped. Any help guys.
Click to expand...
Click to collapse
If you see the device when command "fastboot devices" is used,
just enter "fastboot erase recovery" without the -i parameter.
This worked for me.
Is this the norm when changing recovery.img?
M_Kay said:
If you see the device when command "fastboot devices" is used,
just enter "fastboot erase recovery" without the -i parameter.
This worked for me.
Click to expand...
Click to collapse
i have cm-13.0-20160127-NIGHTLY-crackling-recovery.img installed, should i do the erase? i just flash it using TWRP 2.8.7.1, it is working when i install the cm13.0 but i couldn't install gapp - just hang. Is this the norm when changing the recovery? also can i revert back to the previous recovery img?
noob2016 said:
i have cm-13.0-20160127-NIGHTLY-crackling-recovery.img installed, should i do the erase? i just flash it using TWRP 2.8.7.1, it is working when i install the cm13.0 but i couldn't install gapp - just hang. Is this the norm when changing the recovery? also can i revert back to the previous recovery img?
Click to expand...
Click to collapse
I would replace the nightly recovery with the TWRP recovery img, because it has more options and you can backup your whole system.
So yes erase it and flash TWRP .8.7.1 recovery.
Are you stuck in a bootloop?
If you have intalled TWRP recovery boot into it and under option Wipe format the system and data folder (carefull your data will be lost!!!) . After that flash the nighthly rom again without gapps and check if you can boot.
Thanks for the fast reply and help
M_Kay said:
I would replace the nightly recovery with the TWRP recovery img, because it has more options and you can backup your whole system.
So yes erase it and flash TWRP .8.7.1 recovery.
Are you stuck in a bootloop?
If you have intalled TWRP recovery boot into it and under option Wipe format the system and data folder (carefull your data will be lost!!!) . After that flash the nighthly rom again without gapps and check if you can boot.
Click to expand...
Click to collapse
1st thanks for fast reply and help
im not in bootloop, thank goodness!
I'm currently in TWRP, when the recovery was in CM the gapp-arm64-aroma-5.1 it installed flawlessly following the cm12.1 flash but after the update 13.0 the gapp can't be installed even reverting back to 12.1 and using the same files. I did wipe all prior to change of rom also match it (i.e. cm13.0 to gapp 6.0).
Maybe this will solve it. I will try to erase recovery and re-install TWRP
i will report back after. Thanks
Works
Thanks it worked on pico gapp but not in aroma
followed the erase command and install TWRP again.
Many thanks
TWRP not working in Aroma Gapp need fix
In the previous post, i was able to install twrp but i found out on many trial and error that open gapp aroma/full doesn't work both on cm12.1 and cm13.0 using TWRP. Also cm13.0 recovery will not work with open gapp aroma/full.
What works: (haven't tried all version)
On TWRP - i was able to use arm64-pico-6.0 on cm13.0 20160130
On CM Recovery - arm64-aroma-5.1 on cm12.1 20160107
This is based on my experience with the HELP of the awesome people in the forum. I just want to let you know and maybe it will be useful to other noobs like me
noob2016 said:
In the previous post, i was able to install twrp but i found out on many trial and error that open gapp aroma/full doesn't work both on cm12.1 and cm13.0 using TWRP. Also cm13.0 recovery will not work with open gapp aroma/full.
What works: (haven't tried all version)
On TWRP - i was able to use arm64-pico-6.0 on cm13.0 20160130
On CM Recovery - arm64-aroma-5.1 on cm12.1 20160107
This is based on my experience with the HELP of the awesome people in the forum. I just want to let you know and maybe it will be useful to other noobs like me
Click to expand...
Click to collapse
This TWRP works wioth aroma gapps
https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRP
Thanks
robin0800 said:
This TWRP works wioth aroma gapps
https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRP
Click to expand...
Click to collapse
Thanks for the info and fast reply.
Will this work on Wileyfox Swift? i currently have TWRP 2.8.7.1 size 24.4mb but the link above is in 2.8.7.0 size 15.1mb
noob2016 said:
Thanks for the info and fast reply.
Will this work on Wileyfox Swift? i currently have TWRP 2.8.7.1 size 24.4mb but the link above is in 2.8.7.0 size 15.1mb
Click to expand...
Click to collapse
Works well on mine both for AROMA and cryogenmod nightly updates and to install c-apps for cm13 unoficial
I will try
robin0800 said:
Works well on mine both for AROMA and cryogenmod nightly updates and to install c-apps for cm13 unoficial
Click to expand...
Click to collapse
Thanks for the reply and also on my other post.
Since this is for swift, i will try to install but sadly i have given it back already. It was just here for the upgrade and when i got the chance to get hold of it again i will definitely try and report back.
Many thanks.
Following the various instructions for both TWRP and CM recoveries provide the same frustrating result: I'm getting a black screen when I reboot into recovery.
Everything seemed to go ok on the flashing using ADB but then when replacing the battery and vol-down +power to reboot into recovery I'm greeted with nothing.
Subsequent reboots into recovery from the OS reinstate the Cyanogen recovery.
What am I doing wrong?
Thanks
msiviter said:
Following the various instructions for both TWRP and CM recoveries provide the same frustrating result: I'm getting a black screen when I reboot into recovery.
Everything seemed to go ok on the flashing using ADB but then when replacing the battery and vol-down +power to reboot into recovery I'm greeted with nothing.
Subsequent reboots into recovery from the OS reinstate the Cyanogen recovery.
What am I doing wrong?
Thanks
Click to expand...
Click to collapse
The easy way
Install recovery in bootloader mode with fastboot flash recovery "the name of your recovery"
Hold volume down
issue this command fastboot reboot
when phone restarts you can release volume down the phone should now boot to your new recovery
Note TWP version 3.0.0 is out https://www.androidfilehost.com/?w=files&flid=48495
robin0800 said:
The easy way
Install recovery in bootloader mode with fastboot flash recovery "the name of your recovery"
Hold volume down
issue this command fastboot reboot
when phone restarts you can release volume down the phone should now boot to your new recovery
Note TWP version 3.0.0 is out https://www.androidfilehost.com/?w=files&flid=48495
Click to expand...
Click to collapse
I think it was a windows 10 problem, I gave it all another try this morning firstly using the WinDroid Universal Android Toolkit to Unlock Bootloader and flash TWRP . I then rebooted into recovery and hey presto TWRP. Flashing CM13 nightly and pico gapps was then childsplay.
Any ideas why google play didnt offer to auto restore all my apps? Thats a bit of a pain.
Otherwise very pleased, phone seems a bit more responsive using CM13 than CyanogenOS. I tried to format my SD to use as internal storage too but i couldnt see them separately afterwards to free up device storage so I reverted back.
Thanks for trying to help.
Yey!!!
robin0800 said:
Note TWP version 3.0.0 is out https://www.androidfilehost.com/?w=files&flid=48495
Click to expand...
Click to collapse
Confirmed!!! It works... i used TWRP 3.0. Works on both aroma and pico. Thanks so much!!!!
Got stuck in a TWRP loop after installation. Regardless which reboot option I choose, always TWRP 3.0.0 comes up. No idea what I did wrong but for me it is of more interest how to get rid of it. Accessible external SD contains cm14-zip and also Stock 6.0.1. Installed CM14 multiple times, but has no impact on what comes up after selecting reboot/reboot recovery/reboot fastboot - it is always TWRP. Tried it also via adb sideload from within TWRP, no change of behaviour. Same when I tried to install stock rom.
Bootloader issue? How to get it back? I have 2 further Swifts available so I can dump several necessary partitions from them, but I need to know which tools are required, since I usually deal with MTK-based androids. Backup of userdata and sdcards is available, so if a reset to stock is necessary, this is not a problem from that point of view - if I only would have the info, how to get back a working bootloader.
Even though I love this recovery, it is obviously annoying ... Any help appreciated. Tnx in advance!
Edit: Fixed. I removed the battery for several hours and without battery with plugged in USB cable (not the WF one, I have tons of them lying arround here) I was able to reboot to normal fastboot. From then on it was strraightforward:
checked OEM lock status via fastboot command on PC
flashed newest TWRP
rebooted to TWRP
installed Stock ROM to get all partitions reinitialized correctly
rebooted to OS - YEAH, the swift lives again
Rebooted to recovery
Installed CM14 and OpenGApps Nano (ARM, not ARM64, since it produces an error)
Reboot to OS - YEAH, here we are.
Team Win Recovery Project for Xperia M5
NOTE : This recovery for only bootloader unlocked M5s! Doesn't work with locked bootloader.
Installation :
for Lollipop users :
1- Root your device with this https://goo.gl/F512NR or this https://goo.gl/NADp3S)
for Marshmallow users :
1- Install this kernel (optional) (https://goo.gl/nBWatu)
After the first step, continuous steps same for all users.
2- Go to the /system and delete recovery-from-boot.p with any file manager that has a root privilege.
3- Enable USB debugging and connect the phone to PC.
4- Open cmd and enter these codes:
Hollyss(SingleSim)
Code:
adb reboot bootloader
fastboot flash fotakernel twrp-3.1.1-0-hollyss.img
fastboot reboot
Hollyds(DualSim)
Code:
adb reboot bootloader
fastboot flash fotakernel twrp-3.1.1-0-hollyds.img
fastboot reboot
Bugs :
- USB-OTG not working
- Cache partition has some troubles, it is not wipeable
Workaround for cache:
-In TWRP click settings and enable "Use rm -rf instead of formatting"
Download :
Hollyss-20170910-SingleSim
https://www.androidfilehost.com/?fid=673368273298984560
Hollyds-20170910-DualSim
https://www.androidfilehost.com/?fid=889764386195928556
TRXteam Members :
- @ByBlaCk
- @krkshalill
- @TheShadow35
Changelog :
Code:
2016-12-9 :
-Fix the device name and codename
-Fix Otg(Needs test)
2016-09-22:
- Added M5 Dual support.
2016-09-15:
- MTP issues fixed
- Minor bug fixes
2016-09-14:
- Updated to TWRP 3.0.2-2
- SD Card now working
2016-09-13:
- Initial release
I can't flash it, 30.1.A.1.55 is not supported.
Although i have it rooted & unlocked the bootloader.
Nvm foundnew firmware; flashing now.
Limi96 said:
I can't flash it, 30.1.A.1.55 is not supported.
Although i have it rooted & unlocked the bootloader.
Nvm foundnew firmware; flashing now.
Click to expand...
Click to collapse
@Limi96
Sorry bro, I forgot adding installation for Lollipop Now I'm adding :good:
TRXteam said:
you must flash marsmallow rom and try again
Click to expand...
Click to collapse
Will post results when i come back home, i just flashed 30.2.A.0.100 going out now.
Added installation for Lollipop users.
http:\\i.imgur . com\8x0L2Zd.png
I now have a working TWRP thx!
Downloaded new firmware using xPirifirm flashtool 30.2.A.0.100 single sim, cda was 1300-3365.
Flashed new firmware using flashtool; E5603_30.2.A.0.100_1300-3365_R2B.
Booted up device, hard reset it because it looped then it loaded apps and i did the tutorial.
Flashed kernel using flashtool; boot_m5_ss_30.2.A.0.100_nodmv_su_drmfix.
Flashed twrp-3.0.2-2-holly using flashtool.
So far no complaints if i find any bugs i will inform!
i was looking for otg-usb issue for M5 and i stumble upon this page...big thanks to TRXteam for providing the recovery!!
By the way why is the otg not working...?
Limi96 said:
http:\\i.imgur . com\8x0L2Zd.png
I now have a working TWRP thx!
Downloaded new firmware using xPirifirm flashtool 30.2.A.0.100 single sim, cda was 1300-3365.
Flashed new firmware using flashtool; E5603_30.2.A.0.100_1300-3365_R2B.
Booted up device, hard reset it because it looped then it loaded apps and i did the tutorial.
Flashed kernel using flashtool; boot_m5_ss_30.2.A.0.100_nodmv_su_drmfix.
Flashed twrp-3.0.2-2-holly using flashtool.
So far no complaints if i find any bugs i will inform!
Click to expand...
Click to collapse
Thanks you reply:good:
ataraxist said:
i was looking for otg-usb issue for M5 and i stumble upon this page...big thanks to TRXteam for providing the recovery!!
By the way why is the otg not working...?
Click to expand...
Click to collapse
My Team look it and cant fix otg,but work ıt.Thanks you reply:good:
When I write the commands do I need to put my M5 in fastboot mode? Or plug the device in normal mode?
Thanks.
ginowoo said:
When I write the commands do I need to put my M5 in fastboot mode? Or plug the device in normal mode?
Thanks.
Click to expand...
Click to collapse
ıf your M5 in normal mode write this command
adb devices
adb reboot bootloader
fastboot flash fotakernel twrp-3.0.2-2-holly-20160915.img
fastboot reboot
ıf your M5 in fastboot mode write this command
fastboot flash fotakernel twrp-3.0.2-2-holly-20160915.img
fastboot reboot
how to boot into recovery after that?
warboss said:
how to boot into recovery after that?
Click to expand...
Click to collapse
Hold volume down when powering device up.
i realised that after using this recovery, the phone was recognised as Redmi_Note_2 in TWRP and windows pc? the recovery was modified from Redmi?
ataraxist said:
i realised that after using this recovery, the phone was recognised as Redmi_Note_2 in TWRP and windows pc? the recovery was modified from Redmi?
Click to expand...
Click to collapse
Yes,same sources from redmi
TRXteam said:
Yes,same sources from redmi
Click to expand...
Click to collapse
your english is ok!
So it cannot be modified to "Xperia_T2Ultra"?
I am on MM stock rom. If i do not need root, do it need to flash the kernel? Can i straight away flash this fotakernel for recovery?
"for Marshmallow users :
1- You're install this kernel first for root. (https://goo.gl/nBWatu)
After the first step, continuous steps same for all users."
ataraxist said:
I am on MM stock rom. If i do not need root, do it need to flash the kernel? Can i straight away flash this fotakernel for recovery?
"for Marshmallow users :
1- You're install this kernel first for root.
After the first step, continuous steps same for all users."
Click to expand...
Click to collapse
You need to unlock your bootloader
Yup.. Already unlocked bl.
Sent from my E5653 using XDA-Developers mobile app
Sorry if this has been posted but is it possible to switch to a custom ROM when running Android 10 (v11.0.4.0)?
If you have adb installed on your pc you only need these 2 for twrp, there might be a newer versions but they work fine for me.
img: (to boot from adb)
https://drive.google.com/open?id=1AwtLrERrSEql-ihhiAWPUh6DoXSWhZb9
zip: (to flash in twrp)
https://drive.google.com/open?id=1whcfSqbcNjmqXdnysu25KVX9PyX4mb-P
andraslate said:
If you have adb installed on your pc you only need these 2 for twrp, there might be a newer versions but they work fine for me.
img: (to boot from adb)
https://drive.google.com/open?id=1AwtLrERrSEql-ihhiAWPUh6DoXSWhZb9
zip: (to flash in twrp)
https://drive.google.com/open?id=1whcfSqbcNjmqXdnysu25KVX9PyX4mb-P
Click to expand...
Click to collapse
So should I just use MiFlash to boot each image file individually? Then I assume once TWRP is in I can flash as usual?
RensoreK said:
So should I just use MiFlash to boot each image file individually? Then I assume once TWRP is in I can flash as usual?
Click to expand...
Click to collapse
Never used MIflash so I don't know how that works. I thought it's only to install stock rom, but I might be wrong. Use ADB to install custom ROMs
With the img file you can boot to twrp with ADB command. Then after installing a custom rom use the zip file to flash it .
I am unable to find any adaptable guide anywhere. Tried using XiaomiTools v2 and was unable to flash because my device (even though has a Mi account created) cannot be linked to my device, I have no where to link it on AndroidOne Global version on Android 10. No clue how you guys are doing this. I've flashed phones since Blackberry models here on XDA and this is the only device instructions are halfed.
RensoreK said:
I am unable to find any adaptable guide anywhere. Tried using XiaomiTools v2 and was unable to flash because my device (even though has a Mi account created) cannot be linked to my device, I have no where to link it on AndroidOne Global version on Android 10. No clue how you guys are doing this. I've flashed phones since Blackberry models here on XDA and this is the only device instructions are halfed.
Click to expand...
Click to collapse
find dee_stroy twrp img one. use adb (platfom-tool), then turn off your device and make it go to bootloader state (fastboot). on platform-tool open cmd. (just type on folder path cmd) then type fastboot boot (the name twrp).img and you are set to go. if you wanted to install twrp permanently, after u boot twrp via bootloader, copy the twrp zip to your device and install it. the procedure is all; the same for every rom tho. nothing has changed
Can anybody help me installing this?? .. I had twrp before I installed havoc is 3.6 (android 10) but i didnt install twrp now I can't install twrp please anybody help me
Autokiddo said:
Can anybody help me installing this?? .. I had twrp before I installed havoc is 3.6 (android 10) but i didnt install twrp now I can't install twrp please anybody help me
Click to expand...
Click to collapse
fastboot boot trwp.img
Use TWRP to install twrp.zip
If you were rooted...
fastboot boot patched.img
Use Magisk manager to install (direct)
install twrp
hi, could someone kindly give me a step by step guide to install the twrp recovery?
i have the build QKQ1.191002.002.V11.0.10.0QDLMIXM.
thank you.
InsectWarfare said:
hi, could someone kindly give me a step by step guide to install the twrp recovery?
i have the build QKQ1.191002.002.V11.0.10.0QDLMIXM.
thank you.
Click to expand...
Click to collapse
Nothing?
Inviato dal mio Mi A2 Lite utilizzando Tapatalk
InsectWarfare said:
hi, could someone kindly give me a step by step guide to install the twrp recovery?
i have the build QKQ1.191002.002.V11.0.10.0QDLMIXM.
thank you.
Click to expand...
Click to collapse
This has been documented elsewhere...
The short version is
1) fastboot boot twrp.img
2) adb push twrp-installer.zip /sdcard
3) use TWRP to install the zip
If you also want Magisk you have to install that again. Flash from TWRP or follow the usual process.
I have downloaded the image from GitHub 3 days before the creator removed it so it's basically like archiving it. Works on MIUI 14
Install steps are:
1. download the twrp.img from MikaelaNeia
2. Connect your phone to PC and boot to fastboot and flash the twrp.img file as boot <fastboot flash boot twrp.img>
3. boot to recovery <fastboot reboot recovery> and copy your stock boot.img from firmware to your device.
4. Flash the stock boot img and don't reboot yet.
5. copy your twrp.img to your device and go to Advanced ----> Install recovery ramdisk and tap on twrp.img
6. install it and reboot to system.
That's it
If you were rooted, you have to root again by flashing magisk apk
touch doesn't work, just like the twrp 3.6.0
itayalush said:
touch doesn't work, just like the twrp 3.6.0
Click to expand...
Click to collapse
It did for me at least maybe region issue
itayalush said:
touch doesn't work, just like the twrp 3.6.0
Click to expand...
Click to collapse
I also yesterday built another version with more up to date device tree if you want I'll send it to you
Stephanizgo said:
I also yesterday built another version with more up to date device tree if you want I'll send it to you
Click to expand...
Click to collapse
ok pls send it
Stephanizgo said:
It did for me at least maybe region issue
Click to expand...
Click to collapse
I'm from Israel so does it not work here or something?
itayalush said:
I'm from Israel so does it not work here or something?
Click to expand...
Click to collapse
On eu firmware it works correctly
itayalush said:
ok pls send it
Click to expand...
Click to collapse
The image
May I ask what MIUI version you have