Related
Hello guys.
I have successfully ported TWRP 3.0.0-0 for our Smart Prime 6.
It's 100% working !!
There are NO BUGS !! :good:
DOWNLOAD
NEW LINK: DOWNLOAD
________________________________________
How to install
Via app:
1) Download TWRP 3.0.0-0 from the link above and place it on internal storage of your phone.
2) Download Flashify app from Google Play Store.
3) Open Flashify app.
4) Grant root permissions.
5) Click "Recovery image" and then click "Choose a file"
6) Navigate to the folder where you placed TWRP 3.0.0-0 and choose the .IMG file.
7) Press "Yup!" button and wait.
8) After a while the phone will require reboot. So click "reboot" button.
9) Phone will reboot and automatically boot into TWRP, so you can press reboot to system.
10) Enjoy!
Special thanks to Oneb1t for modded .fstab file! :highfive:
edit: you can use Flashfire app too instead of Flashify, but it's not recommended, because the latest version of the Flashfire app is not flashing properly.
Brilliant! Thank you so much! Do you know any custom ROM what is better than the factory ROM?
There is no custom ROM for this phone yet.
But I'm trying to make LITE ROM.
Adreno306™ said:
There is no custom ROM for this phone yet.
But I'm trying to make LITE ROM.
Click to expand...
Click to collapse
Do you think it's easier/possible to adapt a ROM from a similar device like say, the Alcatel
Pop 2 (5) Premium ? I don't know if there's any ROM for that phone tho, but since it's branded as Alcatel you might get more support from the community here than by using Vodafone's name.
Hello, Demonlord6.
I have tried to make a stock flashable ROM via dumping the system folder and the boot.img file, but without success.
It does not boot properly.. when I tried to flash it without dalvik/system wipe everything was as before.
When I tried to wipe /system and dalvik first and then flash the ROM, it causes bootloop.
So now I'm trying to fix this issue..
I don't know where the problem is.
So when this issue will be solved I will try to build a ROM from Alcatel phones with same specs.
Adreno306™ said:
Hello, Demonlord6.
I have tried to make a stock flashable ROM via dumping the system folder and the boot.img file, but without success.
It does not boot properly.. when I tried to flash it without dalvik/system wipe everything was as before.
When I tried to wipe /system and dalvik first and then flash the ROM, it causes bootloop.
So now I'm trying to fix this issue..
I don't know where the problem is.
So when this issue will be solved I will try to build a ROM from Alcatel phones with same specs.
Click to expand...
Click to collapse
Hey, Andreno306
I don't know much about Rom's in that level of expertise I'm afraid :/ but I did some digging and came across this simple tutorial on XDA:
http://forum.xda-developers.com/showthread.php?t=2387941
I imagine it does not work for every single device out there, at least not with modifying stuff after, but it might be a good starting point I think, in fact I would try to actually make one myself had I a working PC currently at home. But even if I did I had no way of testing it because this is currently my daily driver phone.
Just wanted to say that I'm also very interested in getting a slim ROM for this device. I can't offer any expertise I'm afraid! Just wanted to show that there are people interested in your project.
:highfive:
Stock Kernel
Thanks, it works great.
This is little off-topic but does anyone has the stock kernel, i flashed NeoKernel but it is not that good and i forgot to make a backup do can anyone please link me to the stock kernel?
vojta_horanek said:
Thanks, it works great.
This is little off-topic but does anyone has the stock kernel, i flashed NeoKernel but it is not that good and i forgot to make a backup do can anyone please link me to the stock kernel?
Click to expand...
Click to collapse
I have one
https://mega.nz/#!tMJD3B4T!f6m2ELYCVupqGCcN2aGbkrNzEqijLu7au-7usEfeVL0
But I recommend to restore it with the flashify app, because that's how the backup was made.
If, for some reason, you don't/can't restore it, then you can always try Sugar on the PC which basically restores everything to factory settings (recovery, kernel, etc, it all gets reset)
Demonlord6 said:
I have one
But I recommend to restore it with the flashify app, because that's how the backup was made.
If, for some reason, you don't/can't restore it, then you can always try Sugar on the PC which basically restores everything to factory settings (recovery, kernel, etc, it all gets reset)
Click to expand...
Click to collapse
Restored and my phone keeps turning off after boot(once i saw the turn off screen, other times it just vibrates at boot screen), isnt it the wrong file? (flashed wia flashify)
I was able to restore the boot from TWRP (lucky i made a backup this time)
vojta_horanek said:
Restored and my phone keeps turning off after boot(once i saw the turn off screen, other times it just vibrates at boot screen), isnt it the wrong file? (flashed wia flashify)
I was able to restore the boot from TWRP (lucky i made a backup this time)
Click to expand...
Click to collapse
Sorry there about the bootloop but glad u could restore it from TWRP, maybe it was because we have different ROM versions ?
Demonlord6 said:
Sorry there about the bootloop but glad u could restore it from TWRP, maybe it was because we have different ROM versions ?
Click to expand...
Click to collapse
I got this one: http://www.needrom.com/download/vodafone-smart-prime-6-vf-895n-debloatedclean-stock/#
vojta_horanek said:
I got this one: http://www.needrom.com/download/vodafone-smart-prime-6-vf-895n-debloatedclean-stock/#
Click to expand...
Click to collapse
Yeap, that's not the same version as my ROM, mine is not 130FNN etc. Maybe that's why it didn't work
Enviado do meu GT-S5280 através de Tapatalk
Sorry for the stupid question but... does it works on Smart Prime 7 too?
Has anyone installed that linked ROM? It seems to be what we are looking for... a slim debloated rom.
I presume we need to be rooted, install this TWRP, then flash that ROM?
It mentions unlocking the bootloader, I dont think I've seen any info anywhere about unlocking the bootloader.
Can anyone give a quick lowdown on all the steps required to install that ROM please?
Hi everyone, I discovered that Elephone Trunk and Smart Prime 6 have (almost) identical specs: https://www.devicespecifications.com...ison/c584481c6
So it would be great to "port" (or build ?) the official Nougat-OmniROM for Trunk to VF-895N: http://dl.omnirom.org/trunk/
Last but not least, here's official Vodafone Smart Prime 6 sources: Vodafone_Smart_prime_6_20150413.tar.xz
TWRP for vodafone smart max 4 990N (coolpad 8890u).
I tried this recovery image for vodafone smart max 4 990N (coolpad 8890u).
The phone is in a bootloop state. I think i have usb debugging enabled already.
So, in fastboot mode i can see the device in my pc in adb fastboot cmd.
Im trying to ''fastboot boot recovery.img" but it stops in ''booting..''.
Dont know whats the problem but for sure i can not find a specific twrp image for this device.
If i enter fastboot oem device-info it says ''(bootloader) Device unlocked: true''.
Any ideas ?
hi i was wondering if you could share how you did this or if you can make one for the Vodafone smart n9 (VFD720) it would help a lot of people out looking for this
Needed to root a Vodafone Smart Prime 6 (VF 895N) (got it from a friend because it became unresponsive from all the updated google play stuff ) to get linux-deploy running. Just wanted to leave a big thank you here for Adreno306 for his TRWP 3.0.0-0. it did the job very well!
Only the procedure to get it installed differed quite a bit for me, since Flashify is no longer available.
I wanted to preserve boot and just flash trwp to recover, what worked quite well.
The first thing I did was to boot the phone manually in recovery mode (Power+Vol up) and reset it to factory settings from there. It takes a little while. Then follow the setup, go to phone settings, enable developer mode and set usb debugging. If "unlock oem" is not available there, reboot into recovery again, set unlock there and reboot into bootloader.
The prerequisites are adb and fastboot, both must work. Means adb devices and fastboot devices must show the phone. What can make problems under win10 as it sometimes does not detect the phone in bootloader mode. An actual google usb driver is needed, as provided by google.
For me adb worked well, but when rebooted into bootloader with adb reboot bootloader, fastboot didnt detect the phone. With the phone still connected, the windows device manager showed an unknown device with and exclamation mark (!). Right click, install driver, select driver manually, select driver from device list, mark all devices (first entry) and click "disk", then point to the usb driver director and select "ADB fastboot driver". ( A more comprehensive description is available here )
Once adb and fastboot detect the device, it is time to prepare it. Boot to system (normal operation) first. Make sure that the TRWP 3.0.0-0.img is renamed to trwp.img and then
adb reboot bootloader
fastboot devices
fastboot oem unlock
fastboot boot trwp.img
Now the phone should show the trwp menu, set it up to root the phone and install SuperSU. Reboot into bootloader and
fastboot flash recovery trwp.img
fastboot reboot
Verify with adb reboot recovery, you should see trwp now. Reboot to system.
Now finally go into the app selector, start SuperSU, and root the phone. SuperSu uses trwp recovery mode to install its image and root is done.
Again, big thanks for providing the TRWP image!
Adreno306™ said:
Hello guys.
I have successfully ported TWRP 3.0.0-0 for our Smart Prime 6.
It's 100% working !!
There are NO BUGS !! :good:
DOWNLOAD
NEW LINK: DOWNLOAD
________________________________________
How to install
Via app:
1) Download TWRP 3.0.0-0 from the link above and place it on internal storage of your phone.
2) Download Flashify app from Google Play Store.
3) Open Flashify app.
4) Grant root permissions.
5) Click "Recovery image" and then click "Choose a file"
6) Navigate to the folder where you placed TWRP 3.0.0-0 and choose the .IMG file.
7) Press "Yup!" button and wait.
8) After a while the phone will require reboot. So click "reboot" button.
9) Phone will reboot and automatically boot into TWRP, so you can press reboot to system.
10) Enjoy!
Special thanks to Oneb1t for modded .fstab file! :highfive:
edit: you can use Flashfire app too instead of Flashify, but it's not recommended, because the latest version of the Flashfire app is not flashing properly.
Click to expand...
Click to collapse
Hi, I would like to try your tutorial but I can't root this phone (which is an important step in the tutorial), is there any way someone could help me??
Thanks
Hi guys,
First, English isn't my first language so, sorry if it hurts your eyes :/
Second, I'm new to TWRP / root etc... (since yesterday) and I don't fully understand the exact meening of all words like flash / rom etc...
So: I'm actually blocked in the "Your device can't be checked for corruption. Please lock the bootloader". Apparently it's a normal screen now, when we boot we always see this. OK ( at least that's what I read)
My volume keys aren't doing anything and I can't access my phone anymore.
I can access TWRP if I want.
Thx for responding :good:
Adb & fastboot still recognize your device ?
If yes flash twrp as recovery with fastboot and boot into it with fastboot.
coremania said:
Adb & fastboot still recognize your device ?
If yes flash twrp as recovery with fastboot and boot into it with fastboot.
Click to expand...
Click to collapse
How can I know if ADB recognize my phone?
I can access TWRP so I don't need to flash it again ? Is there a difference between just flash TWRP and flash TWRP with fastboot ?
Sry, my bad, i miss read that you can access twrp, sry, I thought you can't, what happens if you flash a rom, which twrp is installed, what were your steps that you end stuck on bootloader message ?
Edit: if your issue is that you don't know how to start flashing, read the Los thread and follow the op.
Instructions:
1. Install the Universal bootloader and your model specific modem.Failure to do so will not allow flashing the ROM!
2. Update recovery [Recommended -> Official TWRP for Axon7
3. Factory reset if coming from another ROM.
4. Install ROM
5. Install GApps (optionally) [Recommended -> Open GApps (arm64) (7.1) 2017-02-01 or Newer
Download all files from the thread and put them on to your microsdcard, if your twrp is up to date you don't have to do this again. Flash the zip files in the order of the instructions, just press install at twrp and choose the zips, you can add multiple and flash them together.
Man, trust me, I'm not a lazy man and all I want is to have my phone back even if it's stock
I don't understand what you're trying to make me do, sincerely
If you can give me a link where I can have a guide steps by steps or make this guide for me that would be the best thing of my day...
... I really need to wait wtf
update: I wipe all my phone data
I no longer have TWRP installed but the "basic" android recovery
(with those option when you start it:
Reboot system now
reboot to bootloader
apply update from adb
.
.
.
Power OFF)
I'm such a **** wtf
I really don't know your issue, except you seem not to read enough. What guide you want ? How I flash a custom rom to my phone ? How to use twrp ?Why you unlocked your bootloader ? How did you manage to have the stock recovery back ?
I have to guess what you want and what you already did . If you need a guide, here are severals in the guide section.
https://forum.xda-developers.com/axon-7/how-to
TheGreatNarchy said:
... I really need to wait wtf
update: I wipe all my phone data
I no longer have TWRP installed but the "basic" android recovery
(with those option when you start it:
Reboot system now
reboot to bootloader
apply update from adb
.
.
.
Power OFF)
I'm such a **** wtf
Click to expand...
Click to collapse
So you are stuck with stock recovery and not TWRP? If so I would find a guide to "flash" or install TWRP in what is called EDL mode.
If you can do that, you then need to:
boot directly into TWRP and wipe dalvik, system, data, and cache.
Then install universal boot loader and modem for your device. (A2017G)
Next install latest TWRP img found on https://TWRP.me
And lastly reboot into recovery again and install Rom (version of Android you want to try) and any other modifications you want (kernel, gapps, magisk, etc.)
If you have any questions don't be afraid to ask. Good luck!
JTruj1ll0923 said:
So you are stuck with stock recovery and not TWRP? If so I would find a guide to "flash" or install TWRP in what is called EDL mode.
If you can do that, you then need to:
boot directly into TWRP and wipe dalvik, system, data, and cache.
Then install universal boot loader and modem for your device. (A2017G)
Next install latest TWRP img found on https://TWRP.me
And lastly reboot into recovery again and install Rom (version of Android you want to try) and any other modifications you want (kernel, gapps, magisk, etc.)
If you have any questions don't be afraid to ask. Good luck!
Click to expand...
Click to collapse
What? You can flash the ROM after flashing the universal bootloader, then also flash TWRP via itself, and you'll stay on the latest...
Rebooting without a ROM is bad. just bad. even rebooting to recovery. that's how i got my dfu brick
Choose an username... said:
What? You can flash the ROM after flashing the universal bootloader, then also flash TWRP via itself, and you'll stay on the latest...
Rebooting without a ROM is bad. just bad. even rebooting to recovery. that's how i got my dfu brick
Click to expand...
Click to collapse
I am not 100% sure what you are saying. But yeah, sure. Flash the Rom after the universal bootloader and modem. Then flash twrp. Then reboot.
If you think that is better for OP then that works. I haven't ever had the problem of rebooting to recovery without a rom installed but you're right that it probably is safer.
I only suggested that because the TWRP that comes with the real old universal bootloader on LOS thread is also very old. So, flashing a rom with the new version I thought would be best to avoid errors. Thanks!
JTruj1ll0923 said:
I am not 100% sure what you are saying. But yeah, sure. Flash the Rom after the universal bootloader and modem. Then flash twrp. Then reboot.
If you think that is better for OP then that works. I haven't ever had the problem of rebooting to recovery without a rom installed but you're right that it probably is safer.
I only suggested that because the TWRP that comes with the real old universal bootloader on LOS thread is also very old. So, flashing a rom with the new version I thought would be best to avoid errors. Thanks!
Click to expand...
Click to collapse
The thing is, after you flash the universal bootloader, the TWRP on the sd gets replaced. but the TWRP that you are using is loaded in RAM. So even if you install a TWRP version you'll stay in the version you flashed before until you reboot. If you install the universal bootloader and then install the TWRP img you'll keep everything as-is on the next reboot. I discourage rebooting without a system especially on a G because any interruption might lock the phone in DFU. On an a2017U that wouldn't be a problem because the phone boots into edl if any software error is present
We have the first port and root for this highly unpopular BLU phone.
BLU DASH M 2 - Carliv Touch Recovery 6.6.1 aka CTRI have managed to replace the stock recovery and still keep the stock system since there are no customs roms at the moment. The recovery doesn't require you to be rooted but rooting is possible after flashing or booting this rom. Don't fall for the fake Dash files on youtube, I have downloaded them all and they are copies of similar phones and don't work.. This one is ported over from the D070Q by Carliv.
It will not flash a full custom rom but will flash ZIPs so you can root, recover, flash partitions and hopefully pave the way for a TWRP . I do have a TWRP ported over to the BLU Dash M 2 but the touch doesn't work so you can't pass the first swipe screen.
DOWNLOAD from uploadfiles.io @ https://ufile.io/8oc6k
Instructions
- Make sure to backup any important files, this will wipe your data pics, vids, etc..
- Enable OEM unlock under developer options and power down phone
- Boot to stock recovery by holding PWR + VOL UP
- In recovery choose "Reboot to Bootloader" ( aka fastboot )
- You should now be at a blank screen with Fastboot mode: at the bottom
Open your terminal and type the following code, obviously replacing your paths with the correct ones.
fasboot devices < --- will return a serial number or something to indicate connection is OK
fastboot oem unlock <--- will prompt your phone screen to accept unlock request, chose VOL Up to accept and make sure it says "Unlock pass" at the bottom
For testing only
fastboot -c "lge.kcal=0|0|0|x" boot CTR_6.6.1_BLU_DASH_M2_D090U.img
For permanent flash
fastboot flash recovery CTR_6.6.1_BLU_DASH_M2_D090U.img
Don't power down, instead boot in the same recovery
fastboot -c "lge.kcal=0|0|0|x" boot CTR_6.6.1_BLU_DASH_M2_D090U.img
Inside CTR select Wipe cache, Dalvik cache, Userdata / Data.
Select Reboot Phone from CTR menu and when asked to patch , Select " NO "
On first reboot it will reboot twice, then boot the stock system as if it was a factory reset.
This now paves the way for root with Magisk. See my post after this for rooting Blu Dash M2.
Enjoy !
RESERVED
Hey Thank you, got it working. Had to alter it a bit though. Had to select "Yes" for the fix as mine was restoring the old recovery.
Also when I followed your method, the system was not mounting the internal storage.
So I didn't wipe the data and used "Yes" when rebooting and the recovery is good.
I'll be looking out for the root constructions.
Great tutorial though.
73Hn said:
Hey Thank you, got it working. Had to alter it a bit though. Had to select "Yes" for the fix as mine was restoring the old recovery.
Also when I followed your method, the system was not mounting the internal storage.
So I didn't wipe the data and used "Yes" when rebooting and the recovery is good.
I'll be looking out for the root constructions.
Great tutorial though.
Click to expand...
Click to collapse
That will not work for root because Magisk needs the original boot rom. I'm sure it worked for you and that's a good start but wiping the partitions in order does work as well, I probably just left something out or got the order wrong. It's important we don't use CTR to patch because then Magisk complains about boot img being aleady patched and doesn't work.
Anyway you get the idea, it took me a few tries as well but in the end I managed to keep all 3 features intact, the stock rom + CTR + root. If you need to start again you don't need the full rom or sp flash, just flashing system.img to sytem partition works to restore everything.
I'm hoping to find the source code to the kernel and make a TWRP with touch working but the CTR is the only thing we have so far. It does flash zips just not full operating systems. It also flashes boot and recovery partitions.
Thanks, I can restore and try again. Do you have the tutorial for the magisk to root?
73Hn said:
Thanks, I can restore and try again. Do you have the tutorial for the magisk to root?
Click to expand...
Click to collapse
I think most can figure out Magisk from here, the real hurdle was the lack of a recovery because the stock rom doesn't allow Magisk to be flashed.
Thanks, I already started checking in on it... I'll update here once I get through.
How to Root Blu Dash M 2 with Magisk
I have managed to root the stock system using Magisk. The stock recovery will not let you do this, as usual ignore the garbage on youtube and personal blogs, they're giving false info and fake files. This method works and I'm the first user who ported CTR 6.6 to allow for this.
DOWNLOAD Magisk from developer https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
FOLLOW THE ABOVE POST to replace stock recovery with CTR 6.6
Instructions
- Follow first post to install CTR 6.6 recovery and reboot a couple of times to make sure it stuck.
- Enable OEM unlock under developer options and power down phone
- Boot to new CT 6.6 recovery by pressing PWR + VOL UP
- In recovery choose "Install Zip" and choose the "Magisk.zip" from your /SDCARD
Magisk installer will launch and if you did everything right, complete without errors.
- Select Reboot Phone from CTR menu and when asked to patch , Select " NO "
Phone should now reboot twice and have Magisk installed. I have verified root by deleting protected files like default.prop and gave Root Explorer permanent root access. If something doesn't work just find the right sequence. I believe it was flash system, flash recovery. wipe partitions. flash magisk
Enjoy !
The only thing left do now is find the Blu kernel source code for the M2 so a working TWRP can be compiled from scratch, then any MT6580 rom should be flashable.
Perfectly... Got it working using your same method after reinstalling the firmware... only difference was.
After installing recovery and booting into it, I then installed Magisk via adb sideload.
Confirmed root works.
Thank you very much for your patience and assistance
graciaaas
romish said:
How to Root Blu Dash M 2 with Magisk
I have managed to root the stock system using Magisk. The stock recovery will not let you do this, as usual ignore the garbage on youtube and personal blogs, they're giving false info and fake files. This method works and I'm the first user who ported CTR 6.6 to allow for this.
DOWNLOAD Magisk from developer https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
FOLLOW THE ABOVE POST to replace stock recovery with CTR 6.6
Instructions
- Follow first post to install CTR 6.6 recovery and reboot a couple of times to make sure it stuck.
- Enable OEM unlock under developer options and power down phone
- Boot to new CT 6.6 recovery by pressing PWR + VOL UP
- In recovery choose "Install Zip" and choose the "Magisk.zip" from your /SDCARD
Magisk installer will launch and if you did everything right, complete without errors.
- Select Reboot Phone from CTR menu and when asked to patch , Select " NO "
Phone should now reboot twice and have Magisk installed. I have verified root by deleting protected files like default.prop and gave Root Explorer permanent root access. If something doesn't work just find the right sequence. I believe it was flash system, flash recovery. wipe partitions. flash magisk
Enjoy !
Click to expand...
Click to collapse
Thank you very much! You do not know how much I needed to be root! I thought that this device was impossible to root. I really am very grateful. Friend was asking me if you could adapt the custom Slimrom rom for this device? because all the storage of this one takes the system, it would be of great help for all the users of this phone, I do not know if you can or are interested, but I thank you in advance
romish said:
We have the first port and root for this highly unpopular BLU phone.
DOWNLOAD from uploadfiles.io @ https://ufile.io/bj9kk
Enjoy !
Click to expand...
Click to collapse
Hi, can you provide a download link that doesn't require you to get a premium account to access the file. It's against XDA rules.
kirito9 said:
Hi, can you provide a download link that doesn't require you to get a premium account to access the file. It's against XDA rules.
Click to expand...
Click to collapse
It is not premium, the file just expired so the site will keep it on line for a fee. I'll upload it again.
romish said:
It is not premium, the file just expired so the site will keep it on line for a fee. I'll upload it again.
Click to expand...
Click to collapse
Try this one.. if the host tries to replace it with the original let us know and one of the others who have the file will re upload it to another host. I don't feel like signing up anywhere so that is why I use this host.
https://ufile.io/8oc6k
https://ufile.io/8oc6k
https://ufile.io/8oc6k
kevoncrush said:
Thank you very much! You do not know how much I needed to be root! I thought that this device was impossible to root. I really am very grateful. Friend was asking me if you could adapt the custom Slimrom rom for this device? because all the storage of this one takes the system, it would be of great help for all the users of this phone, I do not know if you can or are interested, but I thank you in advance
Click to expand...
Click to collapse
All 'ya 'all are welcome . Unfortunately I can't go any further because there is no source for the kernel so TWRP won't work because there is no touch to get past the first screen. Otherwise if it. did slim rom would flash without any problems, its just these older recoveries don't support a few things that TWRP has to make flashing full roms successful. If someone has source files for the BLU Dash M2 let me know.
I'll just let you guys know, I managed to make a pretty good custom rom with root only by deleteing everything but the core OS. I don't recommend this for everyone but I did get rid of just about everything and made this 6.0 more like 4.4 .. I got it to the point where even the phone and SMS didn't work and the google framework was deleted, then slowly began adding my approved versions of apps. Now its totally de googled but again I realize this isn't for everyone. I just wanted a small rom with camera ad GPS and those are working fine for me.
Custom recovery link taken down again
Could someone please upload the custom recovery again?
[Port] [Recovery] BLU DASH M 2
I tried to fast boot as peryour instructions but I get the error: cannot load ' ctr_6.6.1 etc. :crying:
Please try this link, if you have a better locarion to store it please do so and reshare as this link is only valid for 2 days.
ctr_6.6.1_blu_dash_m2_d090u.img
---------- Post added at 05:08 AM ---------- Previous post was at 05:01 AM ----------
If that recovery does not work, try this one. I have two of different sizes and can't remember which one i used.
recovery.img
Download link
Please repost the download link
I am not responsible for your bricked phone or pigeon poo on your toupe. Do at your own risk.
Stop flashing TWRP !!!!!!! Uninstall magisk before OTA !!!!!!!
If you try to OTA when you have modified your recovery you will likely brick.
If you have magisk OTA will fail.
Fix: Boot to fastboot and see my mini-guide:
https://forum.xda-developers.com/mo...ed-special-case-attempt-t3812530#post77011361
(hiding magisk makes no difference - it will fail - you must temp boot to TWRP and flash uninstall it.)
- thanks @echo92
- - -
I used to flash TWRP as a matter of course. I don't any more after i bricked my phone. Fortunately I could boot to fastboot and created that mini-guide. Fortunately that fixed it. I know there are some that cannot boot to fastboot and I have no solution.
- - - - -
Now, whenever I need TWRP, I boot to it instead (thanks!!! @jceballos )
Code:
fastboot boot twrpimagename.img
That will boot your phone to TWRP and then you can do what you want.
On a 7 bootloader system
1 i will flash magisk 16.0, boot to ROM, tap magisk and let it update magisk mgr - and then I have root for whatever root stuff I need.
When I am done with that and want to eg play PoGo, I again temp boot to TWRP, and flash the latest magisk uninstaller. PoGo then plays fine.
On a 8 bootloader system I will use @rafikowy 's method
https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
BUT I do the temp boot to TWRP first INSTEAD OF THE FLASH TO TWRP - then the rest of the stuff in that post. - read all of that post - there's a bootloop fix which I often need.
- - - - -
ALSO, my opinion is that you should NEVER lock/relock the bootloader of your phone. There is nothing to be gained and you will likely never be able to unlock it - no more mods - ever.
Would the direct boot work with a locked bootloader?
mantin36 said:
Would the direct boot work with a locked bootloader?
Click to expand...
Click to collapse
by the phrase "direct boot" I am guessing you mean "fastboot boot recovery.img"
Let's think this through...
Okay, suppose that works and you are now looking at TWRP (or whatever) on your bootloader locked phone.
Then what would you do?
I suppose you would try to flash a custom ROM and gapps etc and boot to it.
Even if that worked perfectly, and I have no idea if it would, How would you bail yourself out of a problem.
The new guides would be useless to you because your bootloader is locked.
You couldn't change from 7 to 8 or back. You would be totally stuck, imho.
So I would never suggest you try something like that, but I would advise only do it if you are totally willing to throw your phone away.
I'd just use it to root my phone to install v4a and then uninstall root, because I don't really need for anything else at the moment
mantin36 said:
I'd just use it to root my phone to install v4a and then uninstall root, because I don't really need for anything else at the moment
Click to expand...
Click to collapse
Again, my advice - DON'T.
Unlock your bl.
I unlocked the boadloader then I locked
Can I unlock it again ?
Will be any problems?
a) locking it gains nothing.
b) don't know - you'd have to try it.
c) don't know.
Hey
So my bootloader unlock wait time is coming up tomorrow, but this forum is not giving me much hope as all I can see is problems with TWRP constantly being replaced with the stock recovery and general incompatibility (recovery loops or bootloader loops), no one seems to know which of the 10,000 versions of TWRP and OrangeFox (????) recovery to use.
Can anyone clarify what the situation is with Xiaomi Mi 9T or is this phone doomed and its just worth throwing on eBay (a phone without custom recovery and root is absolutely worthless to me).
Thanks a plenty!
Hi!
"TWRP constantly being replaced with the stock recovery"
=> That's nothing to do about Android version: It's a Xiaomi/MIUI boot protection feature. Some TWRP flash a modified VBMeta image, at first TWRP boot, to disable this protection.
- What you can do:
1) Download latest OrangeFox and put ZIP file in phone storage
2) Download latest Official TWRP, flash it via fastboot then hold "Power" and "Vol+" buttons (both) until TWRP is booted
3) Select OrangeFox ZIP file in TWRP and flash it (phone will automatically restart to OrangeFox Recovery).
4) Done! You can now flash latest Magisk version. ^^
Micdu70 said:
Hi!
"TWRP constantly being replaced with the stock recovery"
=> That's nothing to do about Android version: It's a Xiaomi/MIUI boot protection feature. Some TWRP flash a modified VBMeta image, at first TWRP boot, to disable this protection.
- What you can do:
1) Download latest OrangeFox and put ZIP file in phone storage
2) Download latest Official TWRP, flash it via fastboot then hold "Power" and "Vol+" buttons (both) until TWRP is booted
3) Select OrangeFox ZIP file in TWRP and flash it (phone will automatically restart to OrangeFox Recovery).
4) Done! You can now flash latest Magisk version. ^^
Click to expand...
Click to collapse
Hey there. Thanks for this. Do I need to flash the VBMeta file also when I follow this? Would you mind sending a link to the latest official stuff, just wanna make sure I got the right things!
Annie the Eagle said:
Hey there. Thanks for this. Do I need to flash the VBMeta file also when I follow this? Would you mind sending a link to the latest official stuff, just wanna make sure I got the right things!
Click to expand...
Click to collapse
You normally don't need to flash VBMeta file.
- Official TWRP => https://dl.twrp.me/davinci/
- Latest OrangeFox (actually "R10.1_1" because "R10.1_2" is a broken version) => https://files.orangefox.tech/OrangeFox-Stable/davinci/
EDIT: Flash "R10.1_1" version over bad "R10.1_2" version if you already downloaded/flashed via my previous MEGA link.
Annie the Eagle said:
Hey
So my bootloader unlock wait time is coming up tomorrow, but this forum is not giving me much hope as all I can see is problems with TWRP constantly being replaced with the stock recovery and general incompatibility (recovery loops or bootloader loops), no one seems to know which of the 10,000 versions of TWRP and OrangeFox (????) recovery to use.
Can anyone clarify what the situation is with Xiaomi Mi 9T or is this phone doomed and its just worth throwing on eBay (a phone without custom recovery and root is absolutely worthless to me).
Thanks a plenty!
Click to expand...
Click to collapse
Sorry but this is not teally true - or maybe it's the case for custom roms and/or custom twrps
Using (not alone, you can find several peopke reporting the same):
-QFJEUXM 11m0.4.0 (Global, Stable,v Android 10)
-Official TWRP 3.3.1-0-davinci
Just flash that twrp through fastboot, do not wipe or fornat anything (vbmeta, internal storage, whatever), you will not loose anything and everything will work
And the same holds if twrp is replaced by orangefox (since recently, using R10.1_2)
Eg, when booting to twrp, you will enter your pin/password you use in system for unlocking the screen - and twrp will recognize and work with your encrypted Internal memory (so again, without formatting data, wiping vbmeta or whatever)
However, if you want to use some custom roms whose installation requires to format or wipe something, and/ot to use some custom twrps, that's another story (but not a problem in miui or in the official twrp)