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.
Related
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
When trying to go from d3rp ZVC to UltraPop ZVG, I flashed a "Boot fix" zip by Agimax that flashed a new aboot, boot, laf, modem, and recovery image to be able to flash a ZVG rom without tot back to stock. Then I flashed the ZVG radio, then the ROM. Ended up with LG logo boot loop. It won't boot past that. So, I rebooted to recovery. Recovery works, and I can use adb. I can't flash anything but the ZVG rom, unfortunately. Any other rom I try to flash gives an assert failed error about loki.sh.
Since I have access to adb shell, and can copy files over to the internal storage by way of mtp or adb push.. Would I be able to fix this by copying over the ZVC aboot, boot, laf, modem and recovery (or maybe omit the recovery so I can still get back to TWRP )? Or would this cause and unrecoverable brick?
Also, Download mode isn't an option. No matter what I do, the phone will not enter download mode to tot back to stock.
Basically, looking at this thread for unbricking a real hard-bricked G2, all I really need to do is flash aboot, boot and laf for stock then I should have download mode back, right? I need to know for sure before I end up putting it in a state where a motherboard replacement is the only option.
agentfusion said:
When trying to go from d3rp ZVC to UltraPop ZVG, I flashed a "Boot fix" zip by Agimax that flashed a new aboot, boot, laf, modem, and recovery image to be able to flash a ZVG rom without tot back to stock. Then I flashed the ZVG radio, then the ROM. Ended up with LG logo boot loop. It won't boot past that. So, I rebooted to recovery. Recovery works, and I can use adb. I can't flash anything but the ZVG rom, unfortunately. Any other rom I try to flash gives an assert failed error about loki.sh.
Since I have access to adb shell, and can copy files over to the internal storage by way of mtp or adb push.. Would I be able to fix this by copying over the ZVC aboot, boot, laf, modem and recovery (or maybe omit the recovery so I can still get back to TWRP )? Or would this cause and unrecoverable brick?
Also, Download mode isn't an option. No matter what I do, the phone will not enter download mode to tot back to stock.
Basically, looking at this thread for unbricking a real hard-bricked G2, all I really need to do is flash aboot, boot and laf for stock then I should have download mode back, right? I need to know for sure before I end up putting it in a state where a motherboard replacement is the only option.
Click to expand...
Click to collapse
Since you have adb, push the partitions from the KitKat auto-rec apk for the device you have. What really breaks it is the firmware. And any other ROM you have the wrong partitions loaded to work.
secret.animal said:
Since you have adb, push the partitions from the KitKat auto-rec apk for the device you have. What really breaks it is the firmware. And any other ROM you have the wrong partitions loaded to work.
Click to expand...
Click to collapse
I just grabbed aboot, boot, and laf and copied them and used dd to flash in adb shell (dd if=aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot repeated for each img, changine aboot to boot in the img and /dev path.)
After that i was able to boot into download mode and flash tot back to stock. Unfortunately, something went wrong and i lost my esn,msid,meid dec,etc and my msl is now 000000. No efs backup (thought i backed it up to my pc, but i backed up EVERYTHING else.) So i'm heading to sprint today to see if they can fix it, or if I'll need to play ignorant and use my repair plan for a new one.
Thanks though!
Hi. Im new to rooting and on the attempt to install lineageos, i got stock in full wipe.
First i unlocked my bootloader and then installed twrp. everything went well so far, but in twrp i made the mistake of doing a full wpe. now i dont know how to boot into custom recovery, if it even still exists on my phone. i also tried the lg flash tool, but i always get the connection to server error. would be really gratefull if someone would help me out. thxs
so... you don't tried enter to recovery via key-combo? (Vol Down+Power).
If you can enter to Download Mode, try to flash a KDZ with LGUP.
I can't flash kdz because lgup not recognized the device because i flashed a old marshmallow system on my lg4 with v30 port ..any help
fijuu said:
Hi. Im new to rooting and on the attempt to install lineageos, i got stock in full wipe.
First i unlocked my bootloader and then installed twrp. everything went well so far, but in twrp i made the mistake of doing a full wpe. now i dont know how to boot into custom recovery, if it even still exists on my phone. i also tried the lg flash tool, but i always get the connection to server error. would be really gratefull if someone would help me out. thxs
Click to expand...
Click to collapse
ebusuhejbi said:
I can't flash kdz because lgup not recognized the device because i flashed a old marshmallow system on my lg4 with v30 port ..any help
Click to expand...
Click to collapse
Try connecting to your phone in Android SDK/Platform Tools.
Type adb reboot recovery and see if it will boot into TWRP. If it works, you have choices to restore a backup or flash a new rom.
If it doesn't boot into TWRP, make sure your TWRP recovery.img is in the same folder and try re-installing by typing fastboot flash recovery TWRP.img (using the file name of your TWRP image).
solved
sdembiske said:
Try connecting to your phone in Android SDK/Platform Tools.
Type adb reboot recovery and see if it will boot into TWRP. If it works, you have choices to restore a backup or flash a new rom.
If it doesn't boot into TWRP, make sure your TWRP recovery.img is in the same folder and try re-installing by typing fastboot flash recovery TWRP.img (using the file name of your TWRP image).
Click to expand...
Click to collapse
Thanks a lot. i finally got it done with the lg bridge software.
So I tried to flash SuperSU and Magisk and somehow I messed up in a way that doesn't let my device boot regularly and only to fastboot. I can still access recovery but I can't flash OxygenOS 5, which I already had, unless I do a full hardbrick reinstallation with the unbrick tool (editing the script file for the error 7 method did not work). Is my nandroid corrupt? Is there a way to salvage my apps and other data in the nandroid file?
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.