I was wondering are there any ROMs I can flash using twrp recovery installed?
For .img file roms make sure to use fastboot because that's the best for flashing .img system files. Make sure to extract it if the file is compressed. Other ones should be flashed with TWRP. Always use fastboot unless the instructions say to do otherwise. Use TWRP to flash GApps and some system addons, and that's it.
Related
Hi, here is the situation. I got one half-broken Desire.
Fully formatted, s-off,cwm 5.0.2.0 with broken volume up and down keys.
So, when I get into the bootloader I can't get into the recovery to flash zip.
Anyone has some rooted image with boot.img, system.img data.img so I can flash it via fastboot?
Thanks.
You can flash .zip ROM through fastboot : http://forum.xda-developers.com/wik...id#Android_Flashing_Guide_.28with_fastboot.29
I think you can also flash rom from Rom Manager
byglet said:
You can flash .zip ROM through fastboot : http://forum.xda-developers.com/wik...id#Android_Flashing_Guide_.28with_fastboot.29
I think you can also flash rom from Rom Manager
Click to expand...
Click to collapse
Thanks didn't know that... But pretty much useless since community roms don't contain android-info.txt file and some other related stuff.
However, I've figured out that after flashing boot.img via fastboot, it shows itself up in adb devices command so I managed to get into recovery by adb reboot recovery and flashed.
The recovery images all over this site seem really sketchy, but roms often come with great recovery and updates. I can flash the rom's boot.img during the update, but I also see that fastboot has a flash to recovery option. Is it OK to flash the boot.img to recovery or do I have to somehow extract recovery out of the boot.img? If I do a flash to recovery does that make TWRP permanent or can it still be overwritten by flashing new roms?
bananabytes said:
The recovery images all over this site seem really sketchy, but roms often come with great recovery and updates. I can flash the rom's boot.img during the update, but I also see that fastboot has a flash to recovery option. Is it OK to flash the boot.img to recovery or do I have to somehow extract recovery out of the boot.img? If I do a flash to recovery does that make TWRP permanent or can it still be overwritten by flashing new roms?
Click to expand...
Click to collapse
Get twrp from here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/twrp-3-0-1-amami-t3350827 and flash with Rash for non-stock roms. For stock roms, net's xzdr is best - http://nut.xperia-files.com/
If a rom has a recovery included, it will probably overwrite your recovery. For best staying power, make sure you use real recovery - http://forum.xda-developers.com/son...ral/bootloader-devices-real-recovery-t3117568 but even then you might still have to reflash your img, depending on the rom you install.
levone1 said:
Get twrp from here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/twrp-3-0-1-amami-t3350827 and flash with Rash for non-stock roms. For stock roms, net's xzdr is best - http://nut.xperia-files.com/
If a rom has a recovery included, it will probably overwrite your recovery. For best staying power, make sure you use real recovery - http://forum.xda-developers.com/son...ral/bootloader-devices-real-recovery-t3117568 but even then you might still have to reflash your img, depending on the rom you install.
Click to expand...
Click to collapse
Thank you so much. I had the latest TWRP from the AICP rom but it was within the boot image and I couldn't seem to find a plain TWRP image that wasn't on some sketchy thread.
Also I was unaware that my firmware was out of date. When I was installing a rom I saw a number that related to the latest firmware so I assumed I had it. I was confused why using flashboot to flash to recovery wasn't working. It looks like the recovery image was always within the boot image and was getting wiped out with roms that didn't include a recovery image in there (AH HEM PARANOID ANDROID). It seems that I was able to flash the img to the special recovery now and I don't think it's getting wiped out. Thanks very much.
So I wanted to install a CM ver on my mother's Redmi 1s and first thing I have to do is root the device right?
<image>
I have tried downloading several SuperSU.zip from multiple sources, including here at xda forums and the miui forums, to no avail.
Every single attempt has been a failure using the Stock Recovery that comes with the phone.
Fine then, I'll just use a custom recovery. I then connected the phone to my laptop via USB and used the sdk I downloaded.
After typing this line >>adb reboot bootloader, the phone booted into a screen with the fastboot bunny, all normal yes?
Then I typed >>fastboot oem unlock, but the image below doesn't show up on the phone
<image>
Instead, the command prompt just shows a few lines of the process completing
<image>
I continued to enter>>fastboot flash recovery customrecovery.img into cmd with the custom recovery image IN the platform-tools folder in sdk. Cmd again shows a few lines saying that the process completed.
<image>
However the phone still stays on the screen with the fastboot bunny, even after rebooting and then entering recovery mode, it is still the stock one. I have searched everywhere on how to root this phone but they just showed to install the SuperSU.zip using the stock recovery or the sdk method. If anyone could just help me solve this issue that would be great. If you need more information that I can provide regarding the issue feel free to ask. Thanks in advance !
P.s. Due to xda preventing me from posting outside links since I have not met the threshold, anyone who needs the pictures can message me privately.
Edit: Ah yes, I should also mention that I have tried using the stock Updater app to install the SuperSU.zip as well but that doesn't work. Also, I have tried using King Root and Kingo Root as the easy way, same thing.
Find the TWRP image for our device. I don't prefer the fastboot method; flashing TWRP and then the SuperSU zip is a whole lot more convenient as you don't need a computer.
NightRaven49 said:
Find the TWRP image for our device. I don't prefer the fastboot method; flashing TWRP and then the SuperSU zip is a whole lot more convenient as you don't need a computer.
Click to expand...
Click to collapse
But doesn't flashing TWRP without PC (with an app) requires the phone to be rooted to begin with? Or is there any workaround method?
Then use Philz recovery. There's a sticky in the general section that provides a link to such a guide using Philz. After rooting you can flash TWRP.
NightRaven49 said:
Then use Philz recovery. There's a sticky in the general section that provides a link to such a guide using Philz. After rooting you can flash TWRP.
Click to expand...
Click to collapse
Nope, still doesn't work. Tried using the stock recovery to install update.zip and also flashing the .img via sdk, both doesn't work. I'm again out of options.
before do this backup your device
you can install custom recovery with official fastboot rom.
download any official fastboot rom for your device (stable or beta does not matter)
download twrp .img file for your device
rename your recovery image file to "recovery.img"
extract the fastboot rom
go to "images" folder in extracted fastboot rom
overwrite recovery.img file with your downloaded file
flash the fastboot rom with mi flash.
wait for the installation to complete
setup your device
turn off your device and go to custom twrp recovery.
after that you can install supersu or any custom rom via twrp.
I hope you have checked this post
http://en.miui.com/thread-104048-1-1.html
For me..I started with a zip file containing the custom recovery (TWRP) it was named as Update.zip I got it from a tutorial I googled (noob, I know)...and I flashed it using stock recovery (Redmi 1s don't have locked bootloaders, I guess) and then I had Custom recovery installed..I made a backup of MIUI (it was unrooted, stock) and then flashed the CM 12.1( it was the latest then). Then there was no looking back.
Hi.
I have a really complicated problem
So I'm on the Galaxy J2 Core and I've managed to make a TWRP recovery rom for the device.
So TWRP touch isn't responding, so I made a CWM recovery rom after trying a few different versions of TWRP.
The problem is, CWM can only use zip files, when all the custom roms I download are .img.
I can't use fastboot as it doesn't detect my device ("waiting for any device...") although adb does, and I haven't been able to find a working fix.
How would I go about converting the .img file to a .zip, fixing TWRP's touch problem or using fastboot???
This is kinda my last resort so any help would be appreciated
Hi all,
I have recently shifted from Samsung A52S to Onpelus 9 PRO.
I'm now a bit confused about flashing method....
I mean :
on Samsung devices, you have to use ODIN ( that is a Fastboot replacement tool ) in order to flash the TWRP and then, on TWRP, you can freely flash any new custom ROM or any other img files, by simply press "INSTALL" button instad of ADB sideload commands.
If I well understood, in order to flash this custom ROM, I have to do that through Fastboot commands before and through TWRP ADB sideload commands after......
My question is : may I flash boot.img / vendor_boot.img / dtbo.img and ROM zip directly through TWRP "INSTALL" button instead ???
If not, can someone kindly explain which is the reason why ?
Sorry for this noob question but I'm doing my first step into Oneplus and I don't want to do a mess.....
Many thanks for the help !
I personally been wanting to know why we no longer can simply flash custom roms via TWRP like we use to. I do believe its got to do with the way the A/B partition works however that does not really answers why we can't just flash via TWRP. Unfortunately, I have not been able to find the answer so I am interested too on why we can't simply flash custom roms in TWRP and have to resort in sideloading or via fastboot. I would think flashing via a zip in TWRP will have less user errors compare to using a command line to do your flashing.
Saying that, I have been flashing via fastboot since I got this phone and even though its a longer process, it only takes a few more minutes.
twrp is not even fully adapted for android 12 or 13 (but who needs twrp anymore?)
I prefer to flash via fastbootd
(is less work for me)
best way is the magisk install
ChrisFeiveel84 said:
twrp is not even fully adapted for android 12 or 13 (but who needs twrp anymore?)
Click to expand...
Click to collapse
twrp is still the only way to backup the whole rom
it exist a non official version for 12/13
TWRP is the best tool to recover files when the OS does not boot. Since there is no ROM or kernel out there that recommend or uses TWRP for flashing. There is little reason to use TWRP unless is for file recovery. This is in respective to OP 9.