Working in another thread, have gotten the bootloader unlocked but it's the 10.4.2.18 version. I need to find out if there's a version of TWRP that will work with that bootloader or if there is a way to flash the JB TWRP 2.5 and updated bootloader from a windows 10 system pushing it with fastboot commands. It might be easier to start by flashing a TWRP that will work with bootloader 10.4.2.18, flash that then using that TWRP update the bootloader and TWRP.
NP
Related
Guys Now i had unlocked Bootloader officially
so, Now I wanted To Flash TWRP recovery
Now i am Gloable ROm V7.1.8.0
So my question Is
1) should i need to flash modified BOOT image or sholud I flash Directly TWRP
2) Should I flash LAtest TWRP recovery or cofface Twrp !!
THANKS
There's answers around here use search.
First time flashing twrp with fastboot you need to flash a modified boot image as well.
Either TWRP version would be fine.
Guys what is the difference between Twrp official and Twrp coffance !!
2) now I am on v7.2.5.0 so should I flash modified boot image to flash Twrp !!
Where I can get those image
im now official unlock bootloader. so which one twrp i need use? even i official bootloader im still need patching universal boot img?
Hello, I need help with my OPX.
I cannot enter Android or recovery, only Fastboot. Also, Fastboot on my PC can detect my device, but ADB cannot.
I had CM 13 and TWRP 3.0.2.0 installed on it, and now I was going to install LineageOS 14.1. I was first going to update TWRP to 3.0.3.0 because I thougt why not. I installed the new version with TWRPs image flashing and then it rebooted itself to Android. Then I was going to enter recovery again to install Lineage, the problem was that I couldn't even start the recovery. So now I tried to install TWRP with Fastboot, but it told me that the bootloader was locked which I thought was strange since I had unlocked it before.
So I tried to unlock the bootloader with Fastboot using "fastboot oem unlock" which it reported that it did and now I couldn't even enter Android.
But when I use "fastboot oem device-info", it says false to both unlocked and tampered and I still couldn't flash or boot into a recovery with Fastboot.
So now I can only boot into Fastboot Mode.
EDIT 2: Never mind, I fixed it with https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Can I remove this thread somehow?
You needed to flash OOS3 ROM or system partion before flashing 3.0.3 and Lineage
Yepp, I noticed. Found out later that it was because of the older bootloader. I had no idea about that before.
Hello
I recently bought a new device (lollipop version) and I've rooted it successfully so I decided to flash a custom recovery because I want to back up my OS before I start flashing xposed framework.
So I searched the net for a custom recovery for my device (Infinix hot 3 x554) and I found one, then I flashed the custom recovery using mobileuncle root and I reboot into recovery and nothing changed my stock recovery was still there, then after booting my device I flashed the custom recovery again using flashify and I reboot into recovery my phone just booted normally instead if taking me to recovery mode, now my stock recovery isn't there anymore, please I need assistant on how to fix this.
My device: Infinix Hot 3 x554
Version: 5.1
Kernel Version: 3.10.72+
Build Number: x554-W90918-A2-L-20160607
I used kingroot to root the device.
Thank you
It seems your recovery partition restores itself or there are specific scripts in your boot.img which restores stock recovery when detects modified recovery. You must install it via fastboot.
Obtain fastboot and run this command (You can have it with Android SDK or you can find it in Google too.).
Code:
fastboot flash recovery *filename*.img
But you have to be sure you have proper drivers for your device.
Okay, but I did some little research about how to flash recovery and I saw something about unlocking bootloader, so could it be because I haven't unlocked my bootloader that's why it didn't work?
Spadex said:
Okay, but I did some little research about how to flash recovery and I saw something about unlocking bootloader, so could it be because I haven't unlocked my bootloader that's why it didn't work?
Click to expand...
Click to collapse
Yes. You need to unlock bootloader before flashing custom recovery. Locked bootloader prevents modify stock partition.
Ashwinrg said:
Yes. You need to unlock bootloader before flashing custom recovery. Locked bootloader prevents modify stock partition.
Click to expand...
Click to collapse
So after I unlock the bootloader, should I use flashify to flash the custom recovery or I should just use PC to flash it
Spadex said:
So after I unlock the bootloader, should I use flashify to flash the custom recovery or I should just use PC to flash it
Click to expand...
Click to collapse
Use fastboot command to flash recovery.img
sachin n said:
Use fastboot command to flash recovery.img
Click to expand...
Click to collapse
Okay thanks for your time.
I flashed MIUI global stable rom on my rn4 snapdragon using twrp and bootloader was relocked. it is normal? It is safe to flash any rom with locked bl using twrp? can i unlock bl with mi unlock without xiaomi permission if unlocked officially first time?
system twrp and fastboot works normally and now i have custom rom restored from nandroid backup
Are you sure your bootloader got relocked?? Please check it through fastboot oem device-info command.
popek069 said:
I flashed MIUI global stable rom on my rn4 snapdragon using twrp and bootloader was relocked. it is normal? It is safe to flash any rom with locked bl using twrp? can i unlock bl with mi unlock without xiaomi permission if unlocked officially first time?
system twrp and fastboot works normally and now i have custom rom restored from nandroid backup
Click to expand...
Click to collapse
what do you mean about bootloader getting re locked? global builds only remove the custom recovery and dont lock the bootloader i guess.