I flashed a ZVA radio to fix the issues with no audio on a ZVA rom and it keeps sending me to fastboot mode now.
Does anyone have the ZVC TWRP img that Auto-Rec flashes? Otherwise, I think I'm stuck with just fastboot until I can flash a recovery and restore my backup. Or flashtool, but i'd prefer not losing all of my data. I don't want to flash just any old TWRP img because I don't know that it won't brick my phone after the changes autorec made.
Never mind. I ripped out the images from autorec and flashed them, but unfortunately that doesn't allow me to flash the loki hack with it since I don't have adb access, so the TWRP image doesn't pass verification. Had to flashtool after all. Dangit.
so i managed to get my phone out of fastboot mode but i had wiped all partitions due to me trying to flash grola rom and pretty much destroyed my partitions so i flashed zv8 partitions and now just need to get system booting since i have stock recovery working i tried injecting twrp earlier but lead me back to fastboot so i had to go to stock recovery any suggestions guys? ive also tried lg flash tool but no luck on restore with .tot
I've had AOKP & TWRP installed for nearly 3 years. The phone started rebooting occasionally when I would go to manage apps and kill an app. It finally got hosed really good on the last reboot and it got stuck in a TWRP boot loop. I was able to use odin to reflash TWRP and after the initial flash I could get into TWRP recovery. Unfortunately I don't have any of the necessary image files on the sdcard. I then tried to flash a converted AOKP zip (now a tar converted with toolkit). I am not able to get either the toolkit or adb detect the device although I am able to flash with odin. I flashed the AOKP tar image with odin but now when it boot it stays on the Galaxy Note 2 screen and goes no further.
Now I can only get in download mode and since odin seems to be the only thing that is working for me my question is can I use it to flash AOKP and GAPPS (both of which I have on computer)? If so, what format does the AOKP file need to be? img, tar or what? Also can I convert the gapps zip file to a tar and use odin to flash it?
Much thanks in advance. I plan to purchase a new device soon but would like to get this working again as a backup.
Regards, ~metafizik
Use a stock/rooted .tar image to restore the device partition structure.
It contains the PIT for remapping...
Once a stock rooted rom is flashed and running...flash TWRP 2.8.6.0 via Odin...
Then create a nandroid backup to SD CARD..
You can then flash AOKP and GAPPS as .zip files...in TWRP
It's a bit more work....but you'll have a clean backup and a way back if trouble hits...along with fresh partitions...g
I recommend flashing back to stock, get the phone set up using stock, install TWRP, take a nandroid backup, and then flash a custom ROM.
Hi,
I've just bought a Nexus 5X and wanted to root it with systemless method for being able to get OTA in futur.
I've booted to TWRP to flash SuperSU zip but I've made the mistake to use the slider when TWRP ask if I want to keep the system as read only.
Is there an easy way to revert back without the reflashing the rom ?
And is there a way to boot to TWRP from android (if i keep the. .img on my phone) ?
Thank you
Sebacestmoi said:
Hi,
I've just bought a Nexus 5X and wanted to root it with systemless method for being able to get OTA in futur.
I've booted to TWRP to flash SuperSU zip but I've made the mistake to use the slider when TWRP ask if I want to keep the system as read only.
Is there an easy way to revert back without the reflashing the rom ?
And is there a way to boot to TWRP from android (if i keep the. .img on my phone) ?
Thank you
Click to expand...
Click to collapse
If you had TWRP touch your /system in R/W mode even if it made no changes, the system partition is tainted (there is meta-data that changed)
The only practical way to get back to untainted /system is to flash the stock system.img. The flashing is simple, but it might take a little time to download the factory image and extract the system.img.
I usually keep twrp in the recovery partition, probably chainfire has something to boot twrp directly. I do know that if you boot twrp over usb there is a problem where it doesn't accept your pin/pattern/pass to decrypt the user partition. I don't know if it suffers the same problem through other booting methods.
BTW even with systemless root, you cannot flash the differential OTA you receive over the air directly. You need to restore the stock boot.img before flashing the OTA.
The FULL OTA you get from the factory image website, on the other hand, can flash over anything, regardless of whether you have boot, system, or vendor modified.
Thank you for the clear answer
Sebacestmoi said:
Hi,
I've just bought a Nexus 5X and wanted to root it with systemless method for being able to get OTA in futur.
I've booted to TWRP to flash SuperSU zip but I've made the mistake to use the slider when TWRP ask if I want to keep the system as read only.
Is there an easy way to revert back without the reflashing the rom ?
And is there a way to boot to TWRP from android (if i keep the. .img on my phone) ?
Thank you
Click to expand...
Click to collapse
The command
Code:
[I]fastboot boot <img file name>[/I]
will boot twrp from your computer with out having to install it.
Hi so I was using resurrection remix but after finding my stock phone software NPP25.137-15 online I erased everything and flashed through fastboot it went perfectly and I re-locked my bootloader
but I decided to unlock my bootloader again so I could use magisk on stock firmware
my bootloader unlocked and phone still booted but my problem is with twrp
I powered off my phone
held power and volume down
connected my phone to pc while in bootloader
typed fastboot devices
typed fastboot flash recovery twrp.img
pressed power button on phone to reboot phone ( I didn't boot into recovery )
my Moto G5 XT1675 halts at phone can't be trusted ( bootloader is unlocked screen )
any idea why I can't flash twrp?
Because you haven't disabled dm verity on your device, you can't boot stock firmware with twrp while verity is still enabled, flash this: https://androidfilehost.com/?fid=673368273298927206
If it still doesn't boot, flash stock firmware again via fastboot, then flash twrp and boot DIRECTLY into twrp after it is finished installing, then trying flashing no-verity-opt-encrypt again.
Exanneon said:
Because you haven't disabled dm verity on your device, you can't boot stock firmware with twrp while verity is still enabled, flash this: https://androidfilehost.com/?fid=673368273298927206
If it still doesn't boot, flash stock firmware again via fastboot, then flash twrp and boot DIRECTLY into twrp after it is finished installing, then trying flashing no-verity-opt-encrypt again.
Click to expand...
Click to collapse
What exactly does this file do?
Also I flashed magisk which I knew modifies the boot image and the device booted perfectly with TWRP using the magisk modified boot image if that's anything interesting?
Pretty much I was working on a way to install stock firmware through twrp a few weeks ago so people would not have to use fastboot ( I know how to convert a phone backup to a flashable zip )
The flashable zip worked fine but it only booted using a modified boot file, could this be because it needs DM verity disabled?
Although twrp can restore the system image and what is on the internal storage, it will never be a fully functioning substitute for restoring stock firmware via fastboot, twrp can not run scripts that fastboot can, such as 'fastboot oem lock', I also believe that although it can restore bootloader.img and oem.img via a flashable zip, it would most likely cause the device to brick, so simply put; do not try to use twrp for what it's not meant for, twrp is a recovery for flashing zips, restoring only the system image and storage, flashing recoveries and reformatting partitions (which can be risky), just use fastboot for restoring stock firmware.
And yes, your device will boot with magisk installed as it serves the same purpose as no verity opt 5.1 and later versions, though it is usually recommended to disable dm verity before flashing magisk to stay on the safe side.
The flashable zip you installed on your device only booted with a modified boot file as it is not fully stock firmware, twrp is only capable of flashing some elements of stock firmware, this is why you can boot with dm verity still active after restoring with fastboot, again do not use twrp for restoring stock, use fastboot.
Exanneon said:
Although twrp can restore the system image and what is on the internal storage, it will never be a fully functioning substitute for restoring stock firmware via fastboot, twrp can not run scripts that fastboot can, such as 'fastboot oem lock', I also believe that although it can restore bootloader.img and oem.img via a flashable zip, it would most likely cause the device to brick, so simply put; do not try to use twrp for what it's not meant for, twrp is a recovery for flashing zips, restoring only the system image and storage, flashing recoveries and reformatting partitions (which can be risky), just use fastboot for restoring stock firmware.
And yes, your device will boot with magisk installed as it serves the same purpose as no verity opt 5.1 and later versions, though it is usually recommended to disable dm verity before flashing magisk to stay on the safe side.
The flashable zip you installed on your device only booted with a modified boot file as it is not fully stock firmware, twrp is only capable of flashing some elements of stock firmware, this is why you can boot with dm verity still active after restoring with fastboot, again do not use twrp for restoring stock, use fastboot.
Click to expand...
Click to collapse
it's not meant to be a substitute, and I know only fastboot can do OEM lock, flash partition files, modem files,etc, I've been testing my TWRP version for a while, the oem.img partition is not needed in the TWRP versionas the majority of custom roms for Moto G5 don't touch the oem partition and the oem.img file hasn't changed between the stock updates, the TWRP version is for people who want stock firmware but still want to keep twrp, flash magisk, etc, also because TWRP is a portable method and much faster flashing the system back than through fastboot flashing the system back, my twrp version is only meant to restore the system partition and a dm-verity disabled boot.img I wouldn't even think of flashing a bootloader through anything other than fastboot, I've tested a lot and have not bumped into any problems using TWRP that has caused me to use a computer, actually there has been no problems + I'm also testing on 3 other moto G5's all 3 which are also XT1675 models and same there no problems
Then your query has been resolved.
Exanneon said:
Then your query has been resolved.
Click to expand...
Click to collapse
yes, how do I go about closing this discussion well if you know how to?
Rename it to [closed], that's what many do.