Here I present you my toolkit for flashing TWRP and rooing Redmi Y2/S2/YSL.
Requirements
1. PC
2. Fastboot Drivers
3. Unlocked Bootloader (Guide)
4. Flashing TWRP Toolkit
5. Magisk flashable file
Steps for Flashing TWRP
1. Download the file. Link given in the end of the threads.
2. Boot your device into Fastboot mode (in power off state press power button + volume down button).
3. Connect your device from pc.
4. Now open the downloaded folder and run the file "Flash.bat".
5. Then press any key to continue.
6. Now your phone will automatically boot into TWRP.
7. Now you have sucessfully flashed Twrp.8. Before rebooting your device do flash lazyflasher-no-verity-opt-encrypt.zip.
Note :-
* If you don't flash Lazy Flasher then the Custom recovery will be replaced with stock recovery in next Boot.
Steps for Rooting
1. Download and place the Magisk zip fiile into your device.
2. Boot your device into TWRP Recovery (in power off state press power button + volume up button).
3. Select the option of 'Install' and then locate the directory where you have placed the Magisk file and select it.
4. After selecting the file, swipe the arrow loacted at the bottom.
5. When the flashing is completed click on 'Reboot System'.
6. After the phone has booted successfully install magisk apk.
Congrats you have rooted your device !!
Note :-
* This is Exclusively for Redmi Y2/S2/YSL and if you try this on any other device probably you may be bricking your device!!
* I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
* First boot may take upto 15-20 mins. So don't panic.
Links :-
* TWRP Toolkit - Click here
* Lazy Flasher - Click here
* Magisk - Click here
will try this as soon i am able to unlock my bootloader, thanks!
(i hate xiaomi for locking the device for 1 month....!! )
Flashing LF ends in endless boot. No loop but endles bootscreen 1,2,3 dots endlessly! Any ideas ?
So I got stuck on Bootscreen.
I flashed MIUI with TWRP and was back on stockrom with stockrecovery.
Then I booted TWRP temporarely with ADB. (adb command: fastboot boot twrp.img )
Now I installed Magisk and I am happy now
Just DON´T install TWRP. Boot it temporarely !
I used MIUI from here: https://www.theandroidsoul.com/download-miui-10/
Screen asking for PASSWORD.
The TWRP screen asks for password. Default password does not work and after format data the files are not displayed. Same case in clicking cancel.
use xiaomi eu roms they dont ask twrp password
twrp password
Twrp asks for password. What kind of password is this? How to use twrp without the password? How to use this twrp?
Has anybody got rooted redmi s2 finally?
In particular, with stock rom?
finally yes
When TWIRP asks for password nothing helps. The only thing I could do is to wipe ALL THE PARTITIONS except for external SD card, of course. Yes , you loose everything on your phone. Now, you flash the ROM you want (I flashed the stock ROM). After that, you flash the Magisk file. It is important not to reboot in between. After rebooting you have the new system installed. After initial configuration, you have to manually install the Magisk Manager apk.
P.S. the Lazy thing is not needed. TWRP persists.
Want mbn file of unlock bootloader redmi y2
i need emmc_appsboot.mbn file of unlocked Redmi y2(s2) 's bootloader.
If someone has unlocked y2 then please send me the file.
This TWRP for Custom ROM, and if you flash on RI MIUI will not work with any method as well. Especially if you Flash LazyFlaser will certainly be bootloop (stuck on logo)
sumit17 said:
i need emmc_appsboot.mbn file of unlocked Redmi y2(s2) 's bootloader.
If someone has unlocked y2 then please send me the file.
Click to expand...
Click to collapse
for bypass UBL you can try this
Pass : firmware firmware27
danigp75 said:
for bypass UBL you can try this
Pass : firmware firmware27
Click to expand...
Click to collapse
It will bypass only or unlock it too?
sumit17 said:
It will bypass only or unlock it too?
Click to expand...
Click to collapse
unlock too
danigp75 said:
unlock too
Click to expand...
Click to collapse
Bro it is unable to detect my device. But adb commans are recognizing my device and Mi Unlock tool also detect my device.
But this Soft is not able to detect my device. Giving me error
sumit17 said:
Bro it is unable to detect my device. But adb commans are recognizing my device and Mi Unlock tool also detect my device.
But this Soft is not able to detect my device. Giving me error
Click to expand...
Click to collapse
to be able to use this application you must enter EDL mode or "TEST POINT". After devices are detected 9008 on PC, proceed with running the application. Don't forget to enter the "firmware27" password.
Hopefully it can help for UBL redmi YSL without having an official UBL.
danigp75 said:
to be able to use this application you must enter EDL mode or "TEST POINT". After devices are detected 9008 on PC, proceed with running the application. Don't forget to enter the "firmware27" password.
Hopefully it can help for UBL redmi YSL without having an official UBL.
Click to expand...
Click to collapse
For test points i have to dissemble my device. Lol, If you can give me emmc_appsboot.Mbn from unlocked device then it may can help me.
Skyfire1 said:
So I got stuck on Bootscreen.
I flashed MIUI with TWRP and was back on stockrom with stockrecovery.
Then I booted TWRP temporarely with ADB. (adb command: fastboot boot twrp.img )
Now I installed Magisk and I am happy now
Just DON´T install TWRP. Boot it temporarely !
I used MIUI from here: https://www.theandroidsoul.com/download-miui-10/
Click to expand...
Click to collapse
from where did you downloaded the ROM ?
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
shiva sandeep said:
use xiaomi eu roms they dont ask twrp password
Click to expand...
Click to collapse
Where can I download the EU roms ?
---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------
Novikovmex said:
When TWIRP asks for password nothing helps. The only thing I could do is to wipe ALL THE PARTITIONS except for external SD card, of course. Yes , you loose everything on your phone. Now, you flash the ROM you want (I flashed the stock ROM). After that, you flash the Magisk file. It is important not to reboot in between. After rebooting you have the new system installed. After initial configuration, you have to manually install the Magisk Manager apk.
P.S. the Lazy thing is not needed. TWRP persists.
Click to expand...
Click to collapse
from where did you download the rom ?
Israelleite said:
from where did you downloaded the ROM ?
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
Where can I download the EU roms ?
---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------
from where did you download the rom ?
Click to expand...
Click to collapse
From the official Xiaomi site
Israelleite said:
from where did you downloaded the ROM ?
Click to expand...
Click to collapse
The link is in the quote in the line above your question. Or am I misunderstanding you ?
https://www.theandroidsoul.com/download-miui-10/
It is about midpage, the last in the list of phones, just above the section where it says
"How to install the MIUI 10 update"
Related
Hi All,
You guys must be thinking why i'm sharing this recovery when we already have Official TWRP Recovery
actually this Recovery is Lil bit modified (One of my friend Found it somewhere)
via this Recovery you guys will able to Flash any MIUI Rom without Modifying/Patching Boot.img (I tested it my self)(i flashed miui global stable 7.2.3 and global dev 6.4.28)no patched boot.img required
Note:- I'm Not responsible for any kind Of damage caused to your device
Orignal Link => https://drive.google.com/file/d/0B6zD6Bewl4FmQVJGVVBOdzRmT2M/view
Password to the zip :- www.cofface.com
Instructions to flash
download the zip file (link provided)
extract The TWRP recovery.img (password given)
and flash it via flashify or Fastboot
Fastboot Command "Fastboot flash recovery "image-name.img"
yoo done
BUG:- Its not a major bug its not even a bug(i'm just considering it as a bug) but kinda annoying once you flash this recovery this recovery will change your device name from KENZO to CM_KENZO(this not gonna affect anything) but if you will try flash AOSP v4 or anyother AOSP build that verifies the Product name will give some errors
that "This build is for kenzo devices not for Cm_kenzo device"
Solution :- Open the zip in winrar and edit the updater script just change the Kenzo word with CM_Kenzo and it will work (alot of work to do right)
Another solution (this one is better i guess)
when ever you wanna flash MIUi official firmware flash this reocvery via Flashify.
flash the miui rom...
boot it up again flash the official TWRP recovery(so that you will able to flash other roms)
WARNING:- Dont flash miui rom via official TWRP recovery it will not boot untill you flash the Modify boot.img
Update
Bug fixed ===> "This build is for kenzo devices not for Cm_kenzo device"==>No Error now
Link(bug fixed) => https://drive.google.com/open?id=0B5bSNUUrjm6JQjFhUEkzZXZ2bkk
Credits
Developer :- Cofface
Source :- http://www.miui.com/thread-3941604-1-1.html (orignal thread)
Special Thanks to @Rajdip for solving the bug
pls hit thanks if you guys found it helpful
what about the emmc_appsboot file ? should be remove from official rom ?
What is the zip password?? Can you share some screen shot
Anands3 said:
What is the zip password?? Can you share some screen shot
Click to expand...
Click to collapse
read my post zip password is already provided
wawan20 said:
what about the emmc_appsboot file ? should be remove from official rom ?
Click to expand...
Click to collapse
if your device is unlocked officially then No need to remove EMMC_appsboot file
but if your device is unlocked unofficially then yeah you have to dlt that file otherwise it will relock
Please add credits and source links
Rajdip said:
Please add credits and source links
Click to expand...
Click to collapse
I should have added the credit and sources link
But the thing is Idk who developed this recovery.
one of my friend provided me the link and he just found it randomly
i have only this info
Ashish0077 said:
I should have added the credit and sources link
But the thing is Idk who developed this recovery.
one of my friend provided me the link and he just found it randomly
i have only this info
Click to expand...
Click to collapse
Here's the source http://www.miui.com/thread-3941604-1-1.html
and those who are wondering, It works I tested.
---------- Post added at 05:07 PM ---------- Previous post was at 04:43 PM ----------
Okay I edited cafface TWRP, no more "This build is for kenzo devices not for Cm_kenzo device" error here it is https://drive.google.com/open?id=0B5bSNUUrjm6JQjFhUEkzZXZ2bkk
Rajdip said:
Here's the source http://www.miui.com/thread-3941604-1-1.html
and those who are wondering, It works I tested.
---------- Post added at 05:07 PM ---------- Previous post was at 04:43 PM ----------
Okay I edited cafface TWRP, no more "This build is for kenzo devices not for Cm_kenzo device" error here it is https://drive.google.com/open?id=0B5bSNUUrjm6JQjFhUEkzZXZ2bkk
Click to expand...
Click to collapse
Thanx Alot Bro.....and dude its "COFFACE" not "Cafface" and did you tested your build?? if yes i will add your link in the post and will give you credits
Credits Gives
Ashish0077 said:
Thanx Alot Bro.....and dude its "COFFACE" not "Cafface" and did you tested your build?? if yes i will add your link in the post and will give you credits
Credits Gives
Click to expand...
Click to collapse
Yeah I tested my build.. thanks
will this fix the unofficial bootloader unlock hard brick scenario? since now the phone should boot even if the bootloader gets relocked
Nice work, i will test it. Thx.
Wysłane z mojego Redmi Note 3 przy użyciu Tapatalka
Seems to work, but TWRP is in Chinese?
I used Cofface's abd + fastboot files and replaced cofface_recovery_twrp_kenzo.img with the fixed TWRP.img provided by Rajdip. I get some prompt from what I can tell, but since everything is in Chinese I don't know what to click. I'll try to find a solution and post it here.
Update (Solved):
I still don't know what the first screen message was about, but you can get into the normal TWRP menu by swiping the slider to the right. After that click the second from the bottom button on the right to get into settings. Press the globe-symbol on the upper tab bar. From there you can choose the language you want TWRP to be in.
Update #2:
Works like a charm for me. Just installed SuperSU as well. I'm on Redmi Note 3 SnapDragon with Global Developer ROM 6.4.14 (MIUI7), officially unlocked bootloader. Thank you very much for posting OP!
Immortal68 said:
Seems to work, but TWRP is in Chinese?
I used Cofface's abd + fastboot files and replaced cofface_recovery_twrp_kenzo.img with the fixed TWRP.img provided by Rajdip. I get some prompt from what I can tell, but since everything is in Chinese I don't know what to click. I'll try to find a solution and post it here.
Update (Solved):
I still don't know what the first screen message was about, but you can get into the normal TWRP menu by swiping the slider to the right. After that click the second from the bottom button on the right to get into settings. Press the globe-symbol on the upper tab bar. From there you can choose the language you want TWRP to be in.
Update #2:
Works like a charm for me. Just installed SuperSU as well. I'm on Redmi Note 3 SnapDragon with Global Developer ROM 6.4.14 (MIUI7), officially unlocked bootloader. Thank you very much for posting OP!
Click to expand...
Click to collapse
The first prompt that appears is whether you would like to make TWRP modify system files or keep it read only. In simple words, if you swiping to the right Mi recovery wont replace TWRP when MIUI roms are flashed. If anyone didnt swipe right on the first prompt, just goto mount and unselect the read-only option.
Rajdip said:
The first prompt that appears is whether you would like to make TWRP modify system files or keep it read only. In simple words, if you swiping to the right Mi recovery wont replace TWRP when MIUI roms are flashed. If anyone didnt swipe right on the first prompt, just goto mount and unselect the read-only option.
Click to expand...
Click to collapse
Nice to know. TWRP asked the same thing (again apparently) when I rebooted from menu to system. It also provided the option to install SuperSU (or rather install the SuperSU Installer - whatever that was worth). I'm confirmed rooted now and recovery is still TWRP after many reboots. :good:
But is 3.0.0.0
I don't understand that
meangreenie said:
will this fix the unofficial bootloader unlock hard brick scenario? since now the phone should boot even if the bootloader gets relocked
Click to expand...
Click to collapse
No it will not fix that.... actually the thing Is When we unlock Bootloader with Official method it will not get relock while flashing any rom(via recovery)(miflash can still do that) in unofficial Method we replaces the emmc file with the modified one(and when we flash any official rom this file get replaced as this one is modified and (update. Zip/miuirom.zip) does not verify that emmc and relocks the boot loader....
What This recovery does is...
Miui roms inculde some recovery verification On The first boot
Which means it will replace twrp with the stock miui recovery which will cause bootloop...
For this we need to flash the patched/modified boot.img
But This recovery is Lil modified (it auto patches the boot.img and and our recovery does not get replaced and yoo thats how this recovery successfully flashes miui without a patched boot.img
Immortal68 said:
Seems to work, but TWRP is in Chinese?
I used Cofface's abd + fastboot files and replaced cofface_recovery_twrp_kenzo.img with the fixed TWRP.img provided by Rajdip. I get some prompt from what I can tell, but since everything is in Chinese I don't know what to click. I'll try to find a solution and post it here.
Update (Solved):
I still don't know what the first screen message was about, but you can get into the normal TWRP menu by swiping the slider to the right. After that click the second from the bottom button on the right to get into settings. Press the globe-symbol on the upper tab bar. From there you can choose the language you want TWRP to be in.
Update #2:
Works like a charm for me. Just installed SuperSU as well. I'm on Redmi Note 3 SnapDragon with Global Developer ROM 6.4.14 (MIUI7), officially unlocked bootloader. Thank you very much for posting OP!
Click to expand...
Click to collapse
Mine was in english Only on first Boot too?? But yeah i didnt use fastboot to flash was not in mood to turn on my pc.... I flashed it vai flashify and it the recoverg was in english by default and ymyou can flash it via twrp itself..
Anyways Thnx For Reporting This and giving solution
jujusito said:
But is 3.0.0.0
I don't understand that
Click to expand...
Click to collapse
Does that really matter?? Actually i dint face any problem with this recovery and atleast we can flash Miui roms without patching Boot?? And what you dont uderstand??
Its just an old version of twrp as iwas unablefound any updated one
As soon as i get it i will update here...
can I flash this recovery in current TWRP?
Sent from my kenzo using Tapatalk
Warning: i am not responsible for anything that happens to your device. Do this flashing at your own risk,if the process is done incorrectly then it may brick your device and your device warranty will be void after unlocking the bootloader.
The bootloader of lenovo vibe x3 can be unlocked on stock mashmallow. this process will not work in lollipop stock rom. so update your phone to mashmallow.
Now i suppose all of you know about adb,fastboot,twrp,etc.
so i start explaining the process:
Firstly backup all your important data in your pc
2.Now download all the files mentioned in downloads below
3.Now unlock your phone and enable developers options(how to unlock developers option is mentioned below).
4.Then enable oem unlocking and android debugging.(you should have your phone drivers installed in your pc.)
5.Now open the adb folder which you have installed from the downloads
6.Shift+right click to start a command prompt in adb folder
7.Then first check if your device has enabled the adb or not by typing this command: adb devices
8.Then type: adb reboot bootloader(lenovo logo appears on the phone screen).now your device is in fastboot mode.
9.Then run the fastboot command: fastboot oem unlock-go.
10.Displays turn off. That's all you have unlocked the bootloader.
11.Then type: fastboot reboot (and it will restart your device)
12.Now after the device turn on open the twrp zip and extract it.
13.In twrp folder you will find Flash-TWRP ( this command is used to flash the twrp recovery permanetly)and Run-TWRP(this command is used to flash the twrp recovery temporarly only for one boot up).
14.As you click either of the above file the process of flashing is starts and if the twrp is flashed successfully then your device will boot up in twrp recovery.
15.Once the twrp is booted up, it will ask for permission to change the system access, click the read only or you got into a bootloop.
16.Once the above process is done then go to install option and flash the twrp3.0.2 file, which you should have copied in your phone memory.
17.Once the img. is flashed restart your device in recovery mode(twrp menu->reboot->recovery)
18.It will take some time to restart into recovery, but it will surely restart.
19.Now the device is restarted in twrp3.0.2 but the initial language is chinese, but you an change it, to change the twrp language see screen shots
https://drive.google.com/file/d/0B0UFTLtCIxamZG1qcDcxV3U3LTQ/view?usp=sharing
https://drive.google.com/file/d/0B0UFTLtCIxamVENjNWRyUmt2S3c/view?usp=sharing
20.That's all guys you have successfully flashed the twrp 3.0.2 in your lenovo vibe x3.
21.Now if you want to get your device rooted then, just flash the super su file and your device will get root permissions.
Developers options unlocking:
Go to about phone
2.Find build number.
3.Multiple tap on it(approx 7 times.)
4.Developers option is unlocked in setting above the about phone option.
NOTE: After flashing the twrp2.8.7.7, when you boot it first time select the read only option otherwise your device will surely stuck in bootloop, due to secure boot of device.
If you want any help, then you can comment below
Hit like and thanks button if this post helps you.
Downloads
adb and fastboot:http://https://drive.google.com/file/d/0B0UFTLtCIxamLVFWT1RaU1NPZUU/view?usp=sharing
twrp2.8.7.7:http://https://drive.google.com/file/d/0B0UFTLtCIxamcWd3eVJ1dUxwTW8/view?usp=sharing
twrp3.0.2:https://drive.google.com/file/d/0B0UFTLtCIxamM1VoajVmejZqWFU/view?usp=sharing
supersu:https://drive.google.com/file/d/0B0UFTLtCIxamRWpsOTlsQWI0c2c/view?usp=sharing
The above downloads are collected from different sources. I am not the one who created it.
"lenovo vibe x3(all models)" - That's not true. it's only for Vibe X3C40.
Vibe X3C50 model don't have OEM Unlock option in developer menu available, so you can't enable it in this model. And no description how to enable it.
vibe x3 lite
vibe x3 lite as welll?
thank you
xmexme said:
"lenovo vibe x3(all models)" - That's not true. it's only for Vibe X3C40.
Vibe X3C50 model don't have OEM Unlock option in developer menu available, so you can't enable it in this model. And no description how to enable it.
Click to expand...
Click to collapse
mnfaceira said:
vibe x3 lite as welll?
thank you
Click to expand...
Click to collapse
Its depend which model you have EU or Chinese. If chnese then probably no.
If you can enable oem unlock in development option in your model then this metod will work for you.
mnfaceira said:
vibe x3 lite as welll?
thank you
Click to expand...
Click to collapse
vibe x3 lite is totally different model. It is a mtk device and vibe x3 is a qualcomm device. so i dont think it work on that. The twrp are all different for different phones. so the twrp wont work on vibe x3 lite.
xmexme said:
"lenovo vibe x3(all models)" - That's not true. it's only for Vibe X3C40.
Vibe X3C50 model don't have OEM Unlock option in developer menu available, so you can't enable it in this model. And no description how to enable it.
Click to expand...
Click to collapse
i have tried this method on x3a40(indain version). and the bootloader is already unlocked in chinese version. If it is locked then you can flash the x3a40 stock rom then unlock it with this method. it will work
Data
Will this wipe the data?
srikarss said:
Will this wipe the data?
Click to expand...
Click to collapse
no data will not be wiped in unlocking bootloader, unless you wipe the data yourself.
Can't OEM unlock
I try your method until fastboot oem unlock-go, display still on but everything in command say ok. Can't install TWRP. Please help Thank.
PrinceMSak said:
I try your method until fastboot oem unlock-go, display still on but everything in command say ok. Can't install TWRP. Please help Thank.
Click to expand...
Click to collapse
Which file have you run flash twrp.bat or run twrp.bat??
flash twrp after finish it's reboot to normal not recovery
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
After run Flash TWRP it's boot to normal not recovery
PrinceMSak said:
flash twrp after finish it's reboot to normal not recovery
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
After run Flash TWRP it's boot to normal not recovery
Click to expand...
Click to collapse
First place the twrp folder in phone memory(or memo card). Then Instead of flash twrp.bat, try run twrp.bat it will boot your phone in twrp, after getting into twrp select read-only option, then open install and go into twrp folder in memory, you will find your twrp img file select it, then flash it in recovery partition and its done your recovery is flashed permanently. Reboot your phone in recovery to check it.
Still can't use TWRP
I try new method but still not working, when reboot to recovery still on lenovo recovery not twrp. In my opinion oem unlock is not working because when i send command the display is still on not off.
PrinceMSak said:
I try new method but still not working, when reboot to recovery still on lenovo recovery not twrp. In my opinion oem unlock is not working because when i send command the display is still on not off.
Click to expand...
Click to collapse
You are having marshmallow as stock right?
TWRP OK Now
I fix't now by use twrp flash supersu 2.79 first then use second method to flash inside phone. Working now. my phone is stock 6.01 maybe chinese build. Thank for quick response.
PrinceMSak said:
I fix't now by use twrp flash supersu 2.79 first then use second method to flash inside phone. Working now. my phone is stock 6.01 maybe chinese build. Thank for quick response.
Click to expand...
Click to collapse
No problem
This procedure work on Lenovo VIBE X3 K51c78 with android 5.1 ROM VIBEUI_V2.9_1616_5.1340.1_ST_K51c78?
I have several problems with this device and I try update de ROM throught recovery mode but is not allowed, when it will start install (appear 0%), appear a X symbol in red.
So I need update the ROM but the device don't allow, anyone can help me?
r_m_f_f said:
This procedure work on Lenovo VIBE X3 K51c78 with android 5.1 ROM VIBEUI_V2.9_1616_5.1340.1_ST_K51c78?
I have several problems with this device and I try update de ROM throught recovery mode but is not allowed, when it will start install (appear 0%), appear a X symbol in red.
So I need update the ROM but the device don't allow, anyone can help me?
Click to expand...
Click to collapse
No this process only work with stock marshmallow, so you have to update your phone to marshmallow then, only you can unlock your bootloader and install twrp.
tarun yadvendu said:
No this process only work with stock marshmallow, so you have to update your phone to marshmallow then, only you can unlock your bootloader and install twrp.
Click to expand...
Click to collapse
thanks tarun yadvendu.
the question is how I can update my phone to stock marshmallow? When I try update it dont allow.
r_m_f_f said:
thanks tarun yadvendu.
the question is how I can update my phone to stock marshmallow? When I try update it dont allow.
Click to expand...
Click to collapse
Download the qfil zip rom and install it with qfil software. Follow this link for installing stock rom using qfil, select s217 rom file for marshmallow https://forum.xda-developers.com/android/development/rom-lenovo-vibe-x3-row-x3a40-stock-t3328461
Phone Details:
Sony Xperia Z2 D6503 running Android 6.0.1
Boot loader unlocked
TWRP installed
Magisk v12.0
Had the phone rooted but un-rooted via SU and then re-flashed default os using Sony Companion and unlocked the boot loader
When i flash Magisk via TWRP it says its successful but when i go to reboot it won't boot up
Has anyone experienced this before or have successfully installed Magisk on Xperia Z2 that can help me out?
same problem here. can anyone recommend a solution ?
Same here.. Finally recovered my device flashing stock...
https://forum.xda-developers.com/lg-g5/development/stock-h850-20d-eu-rom-flashable-zips-t3592762
Before Magisk installs anything on your device, it will create a boot image backup in /data/stock_boot_<sha1>.img.gz
If anything goes wrong (e.g. bootloop), you can either use the uninstaller (recommended) or decompress the backup and manually restore your boot image
It should ALWAYS bring your device back to life (suppose you have a custom recovery that can decrypt your /data)
Click to expand...
Click to collapse
Source: Main Thread
TatesMan said:
Source: Main Thread
Click to expand...
Click to collapse
How to install the unistaller while the phone is in bootloop and i can't access recovery
deathlove70 said:
How to install the unistaller while the phone is in bootloop and i can't access recovery
Click to expand...
Click to collapse
If you can't access recovery you've got bigger issues than getting a bootloop from flashing Magisk. Can you access the bootloader to fastboot flash or boot a recovery image?
Didgeridoohan said:
If you can't access recovery you've got bigger issues than getting a bootloop from flashing Magisk. Can you access the bootloader to fastboot flash or boot a recovery image?
Click to expand...
Click to collapse
i can access flash mode and fast bootmode in flash tool. it says the phone is connected
deathlove70 said:
How to install the unistaller while the phone is in bootloop and i can't access recovery
Click to expand...
Click to collapse
try to boot using 'power+ volume down' to boot into recovery, if that didnt work then you have to boot into fastboot then flash the recovery from there
deathlove70 said:
i can access flash mode and fast bootmode in flash tool. it says the phone is connected
Click to expand...
Click to collapse
Cool. Then you should be good to go. If you don't know how to proceed from here, you should go to your device's forum for help.
can you make it simple and tell me what t do ?
what files should i flash ?
i have sony xperia Z2
---------- Post added at 11:16 PM ---------- Previous post was at 11:14 PM ----------
TatesMan said:
try to boot using 'power+ volume down' to boot into recovery, if that didnt work then you have to boot into fastboot then flash the recovery from there
Click to expand...
Click to collapse
boot via power+volume down didn't work. what's the file to flash ?
deathlove70 said:
can you make it simple and tell me what t do ?
what files should i flash ?
i have sony xperia Z2
---------- Post added at 11:16 PM ---------- Previous post was at 11:14 PM ----------
boot via power+volume down didn't work. what's the file to flash ?
Click to expand...
Click to collapse
best advice is to head to your device's forum and check for guides there on how to flash custom recovery (twrp) there.
Connect your phone with pc, go into fastboot mode and type on fastboot
Code:
fastboot boot recovery
Or try a simple ways with power button with volume -/+ or both just try it
i recovered the phone but lost the root and can't root my phone. i am on marshmallow stock firmware
Hi, today i saw a notification of magisk saying there's a new version aviable, i clicked and i selected the automatic update option, after done, i rebooted my phone, but now it is blocked in a loop witouth showing screen, what can i do?
I have a xiaomi mi 9 but it does not pass the logo of home, it stays there, I do not have the bootloader unlocked so I wanted to know another way to flash it
If flashing is no option for you, you might have to send it in for warranty.
Try XiaoMiTool v2
Same problem here; and this tool says fastboot unbrick is not supported yet ... So even though I can flash different twrp builds, it wont get out of reboot to fastboot and no recovery works
futiless said:
Same problem here; and this tool says fastboot unbrick is not supported yet ... So even though I can flash different twrp builds, it wont get out of reboot to fastboot and no recovery works
Click to expand...
Click to collapse
Did you've tried this lr team twrp:
http://files.mi-room.ru/files/twrp/cepheus/3.3.1-0601/recovery.img
And after flashing twrp, directly with volume up and power reboot in twrp?
Search for vbmeta.img file for mi 9 and flash it
What worked is cepheus_global_images_9.6.27_20190627.0000.00_9.0_global_d1aa19c208 ; then MANUAL usage of flash_all.bat ; then I was able to boot... I think (and don't take my word for it !!) what this is, is encryption lockout. Most XiaomiFlash offical tools were practically useless for the Mi 9 and only finding that exact build (which I figured out wasn't an upgrade like the others with no flash_all.bat, actually ran and it flashed stock and booted me to pincode decryption. After than I was able to use twrp-3.3.1-35-cepheus.img, and get TWRP ... granted it wiped everything. But I booting twrp-3.3.1-35-cepheus also asked for my decrypt key. I think the other TWRP's that don't ask for this while I am encrypted actually corrupted this data... (again maybe i'm wrong) but all in all ... I had a couple hours of slowly building up stress.. cause every recovery I flashed rebooted direct to fastboot. And i'm still not sure why..
Everyone needs to make sure that you can see your full file directory tree before utilizing TWRP commands as if the TWRP install doesn't detect decryption it doesn't discriminate and just overwright and corrupts files... THIS IS WHAT IT SEEMS AT LEAST ...
ALSO big word of warning Global users have to play it safe as it seems our variants is not the one the devs are releasing for ATM. and most things you attempt to flash will cause problems. (AGAIN just my 2 cents not to be taken as fact.) Just a warning... that is it...
---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
emprazol said:
Search for vbmeta.img file for mi 9 and flash it
Click to expand...
Click to collapse
OK what is that file updating over ?
link to the rom you used to fix fastboot brick?? please
I have 9008, can you help me?
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:
[I]#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* 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 recovery
* 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.
*
*/[/I]
I’d recommend to read everything in this post, if you care about your expensive phone.
Let’s start with the installation process
If you already unlocked your bootloader, start with step 3.
If you are already rooted, start with step 4.
If you already installed a previous version of TWRP, start with step 4.
If you already have TWRP installed and just want to root, start with step 5.
First you need to unlock your bootloader. You can do so by enabling developer settings first, enable oem unlocking, then shut down your phone, hold volume up and down at the same time and while holding them plugin your charger. Your phone now should show a green screen with instructions to unlock the bootloader. Just follow them and after the unlocking your data should get wiped. After that your device will boot up and land in setup screen. Do not setup anything, just skip as much as possible, because your phone will get wiped again. Enable developer settings and make sure oem unlocking is greyed out and enabled. (If it does not show up, connect to a network first!)
Now you need to overwrite vbmeta partition, so you can flash third party partitions. Download vbmeta.tar then go into download mode on your device. Put vbmeta.tar to AP in Odin, click start. This should finish pretty quickly, so pay attention when your device reboots, because you need to boot into recovery (Hold power and volume up after the screen turns black). When booted into recovery, wipe your data and reboot normally into system. Now you can setup your phone as usual and make sure oem unlocking is still greyed out and enabled!
Time to flash recovery. Download (link is at the end of this post) the latest version as zip and extract it. You should end up with one single file named recovery.img. Pack it as tar with 7zip or any other compression tool you prefer. This packed tar file should only contain recovery.img and nothing else, also make sure the name is still recovery.img, otherwise Odin will refuse to flash it. In Odin put the tar file in AP and simply hit start. Congrats you now have TWRP installed!
(Optional) You might have lost root access by flash TWRP if you followed this standard guide for rooting. If you did lose it and want to gain root access again (you can also root your device with this method, even when you never rooted your device), download the latest Magisk Manager from the canary channel and install the apk to your phone.
If you are on stock:
Push the recovery.img file you just download for TWRP to your phone. Open Magisk Manager and hit install and patch a file. Select recovery.img and Magisk should start the patching process. Once Magisk is done, boot into TWRP. Backup your boot partition first and afterwards go into install and then hit install image on the bottom right of the screen. Select /sdcard/Download/magisk_patched.img and install it to boot. Now reboot and Magisk should work. If you run into issues after this, go into TWRP and restore the boot partition you backed up previously.
If you are on an AOSP based rom:
Reboot to TWRP. Create a backup with boot partition. Reboot back to system, then open Magisk and hit install and patch a file. Locate the TWRP backup folder and look up your backup you just created. Select boot.emmc.win for patching. Once Magisk is done, reboot back to TWRP. Go into install and then hit install image on the bottom right of the screen. Select /sdcard/Download/magisk_patched.img and install it to boot. Now reboot and Magisk should work. If you run into issues after this, go into TWRP and restore the boot partition you backed up previously.
So that was the easy part. The hard part is to completely read these following points!
Encryption/Decryption
Decryption works on this TWRP release, but only partially. That means you have to open the Settings Application first on your phone and disable a feature called strong protection. You can find it in Settings->Biometrics and security>Other security settings. It doesn’t matter when you disable it. Flash TWRP first and disable it, fine. Disable it and flash TWRP afterwards, fine. Never disable it, also fine, TWRP just fails to decrypt your data, but won’t do any harm. When this feature gets turned off, the device will generate a key which doesn't require any authentication for decryption, currently only this allows TWRP to decrypt the data partition successfully. This only applies to stock roms though, if you are using an AOSP based rom, then you don't have to do any of this.
Disabling decryption
Disabling decryption will create many problems. First TWRP will refuse to unmount system partition and thus you might run into problems flashing various zips. So I advise you to not disable decryption. If you still want to disable it you have to open terminal in TWRP and type in "stop servicemanager" everytime you want to unmount the system partition.
Backup and Restore
Because of encryption it's more complicated to backup your data partition.
If you want to backup data you have to make sure TWRP successfully decrypted your internal storage, otherwise you will run into problems backing up.
Restoring is even more complicated. Every time you set up a rom, new crypto keys will be generated and you can't backup these. That means if you want to restore data you have to restore the whole rom first excluding data. Format data partition completely, boot it up, then go back to TWRP and restore data. You will lose your internal storage, so I'd recommend you move important stuff to external storage.
Developers specific details
Sources
https://github.com/Grarak/android_device_samsung_a70q-twrp
https://github.com/Grarak/android_device_samsung_a70q
https://github.com/Grarak/android_bootable_recovery-1
Recovery image size
For some reason the ramdisk has a size limit, so I used LZMA compression to get its size down as much as possible.
During kernel compilation you will run into a DTC error. Apparently Samsung didn’t bother to update their DTC source in the kernel and you have to use their precompiled binary. I edited my kernel sources to automatically use their dtc binary.
Credits
Device tree of Redmi Note 7 Pro (https://github.com/TeamWin/android_device_xiaomi_violet). Helped a lot!
Topjohnwu for the detailed installation guide (https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root)
TWRP Galaxy S10 thread for describing System-as-root pretty well
(https://forum.xda-developers.com/ga...ecovery-twrp-3-3-0-galaxy-s10-exynos-t3924856)
Downloads
https://github.com/Grarak/android_device_samsung_a70q-twrp/releases (Also changelog)
Note The download is a zip file, unpack it and you will get the recovery image. To flash it in Odin pack it as tar with 7zip or a compression tool of your liking.
reserved
nice work, I'll buy the phone in this 2 days to start some works.
Thanks bro ?
Screenshot please
thanks alot ! development can start on this phone ! (i confirm twrp work)
BK☑️ said:
thanks alot ! development can start on this phone ! (i confirm twrp work)
Click to expand...
Click to collapse
Which version do you have?
devilhunter47 said:
Which version do you have?
Click to expand...
Click to collapse
TWRP version is 3.3.1
actual firmware is A705FNXXU3ASG6_A705FNOXM3ASG6_BTU (july security patch) (United kingdom)
prev. firmware was A705FNXXU1ASE4_A705FNOXM1ASE4_XEF (may security patch) (France)
edit 1 : the ui freeze completly when phone is booted up , had to flash all back
i'm going to flash A705FNXXU1ASD1_A705FNOXM1ASD1_BTU (april security patch) (United kingdom) and see if it boot correctly...
edit 2 : cant flash previous firmware due to 'security reasons' ,i flashed back stock recovery, it doesnt freeze anymore, i guess we will have to wait for a custom kernel
cant you use this to flash GSI images and then use magisk? or does that not bypass the boot image problem?
MTP
Grarak said:
FAQ
When TWRP can't work with Magisk, then what's the point of this?
TWRP can work with Magisk, if the firmware you have is compatible. (Read first post).
But yes, right now there are no reasons to have TWRP installed, but you have to start development somewhere and having a working custom recovery is a pretty good first step.
Click to expand...
Click to collapse
MTP doesnt work in this build
edit: it work in this build thanks
---------- Post added at 09:38 PM ---------- Previous post was at 09:30 PM ----------
kristiansja said:
cant you use this to flash GSI images and then use magisk? or does that not bypass the boot image problem?
Click to expand...
Click to collapse
i dont think this build is made for treble roms, so probably not
BK said:
MTP doesnt work in this build
Click to expand...
Click to collapse
Uploaded the wrong version. Fixed
Grarak said:
Uploaded the wrong version. Fixed
Click to expand...
Click to collapse
lemme check
---------- Post added at 09:57 PM ---------- Previous post was at 09:52 PM ----------
BK said:
lemme check
Click to expand...
Click to collapse
edit : it work now thanks!
Thanks dev! Astonished at the progress you've made despite Sammy's carelessness
BK☑️ said:
lemme check
---------- Post added at 09:57 PM ---------- Previous post was at 09:52 PM ----------
edit : it work now thanks!
Click to expand...
Click to collapse
With July security patch?
Okay, so can anybody else see if system or system images backup crashes TWRP?
FriendlyNeighborhoodShane said:
Okay, so can anybody else see if system or system images backup crashes TWRP?
Click to expand...
Click to collapse
yep , i tried backups yesterday but twrp crash when backing up system.img
---------- Post added at 09:04 AM ---------- Previous post was at 09:01 AM ----------
devilhunter47 said:
With July security patch?
Click to expand...
Click to collapse
i was refering to MTP , the link been fixed, MTP work now , but phone crash after boot up , or just wont boot at all, i were also stuck in prenormal RMM, thats why it wouldnt boot
Grarak said:
FAQ
twrp reboot itself when transfering files and freeze forever , have to flash whole firmware again everytime
Click to expand...
Click to collapse
Kernel source A70Q
Grarak said:
FAQ
When TWRP can't work with Magisk, then what's the point of this?
TWRP can work with Magisk, if the firmware you have is compatible. (Read first post).
But yes, right now there are no reasons to have TWRP installed, but you have to start development somewhere and having a working custom recovery is a pretty good first step.
Click to expand...
Click to collapse
i found kernel sources from there https://github.com/Qiangong2/android_kernel_samsung_a70q , is this the source you worked with?
BK said:
Grarak said:
FAQ
twrp reboot itself when transfering files and freeze forever , have to flash whole firmware again everytime
Click to expand...
Click to collapse
Seems to be a kernel problem. Probably have to wait for Samsung to update their sources.
BK said:
i found kernel sources from there https://github.com/Qiangong2/android_kernel_samsung_a70q , is this the source you worked with?
Click to expand...
Click to collapse
No
Click to expand...
Click to collapse
Grarak said:
FAQ
When TWRP can't work with Magisk, then what's the point of this?
TWRP can work with Magisk, if the firmware you have is compatible. (Read first post).
But yes, right now there are no reasons to have TWRP installed, but you have to start development somewhere and having a working custom recovery is a pretty good first step.
Click to expand...
Click to collapse
i contacted the guys from Samsung Opensource Center for kernel and platform source release, ill see what they say...
How to install TWRP can anyone tell step by step....