Related
I got a Nexus 4 today. It is currently on 4.3. I've rooted the phone and installed TWRP recovery. I tried flashing the 4.4 zip and I get a failed message. I can't figure out why. Can someone help?
Yes.
Don't even bother trying to figure out why. You just got the phone. Flash the factory images for 4.4.2.
Not sure why you would get a phone and root it / modify it first, instead of just updating.
But anyways. Your bootloader is already unlocked. Flash factory images. Reroot and do whatever you want after.
albundy2010 said:
Yes.
Don't even bother trying to figure out why. You just got the phone. Flash the factory images for 4.4.2.
Not sure why you would get a phone and root it / modify it first, instead of just updating.
But anyways. Your bootloader is already unlocked. Flash factory images. Reroot and do whatever you want after.
Click to expand...
Click to collapse
It wouldn't update. I thought about doing that first but it said the update was "waiting to download". Where can I get the factory image to 4.4.2?
ILowry282 said:
It wouldn't update. I thought about doing that first but it said the update was "waiting to download". Where can I get the factory image to 4.4.2?
Click to expand...
Click to collapse
The "factory image" from google is a tgz file. Not a zip file. WTF?
Factory images are flashed with fastboot, not a custom recovery or stock recovery.
Extract that file. Take everything that comes out and put it in your directory that has fastboot in it.
Put the phone in fastboot..... Run the flashall. Bat
That will wipe everything off the phone and put stock on it. If you don't want it to wipe your data ( not sure why you wouldn't since you just got it and probably don't have all your junk on it...) you can edit that script by removing the - w part in it.
It's very simple.
albundy2010 said:
Factory images are flashed with fastboot, not a custom recovery or stock recovery.
Extract that file. Take everything that comes out and put it in your directory that has fastboot in it.
Put the phone in fastboot..... Run the flashall. Bat
That will wipe everything off the phone and put stock on it. If you don't want it to wipe your data ( not sure why you wouldn't since you just got it and probably don't have all your junk on it...) you can edit that script by removing the - w part in it.
It's very simple.
Click to expand...
Click to collapse
Haha! Simple maybe for you. What exact commands to I type in terminal (I have a mac)? I know all commands need to start with ./fastboot-mac
ILowry282 said:
The "factory image" from google is a tgz file. Not a zip file. WTF?
Click to expand...
Click to collapse
Unzip the file with 7zip. Run the flash -all file. Let it do its magic.
Sent from my Nexus 4 using Tapatalk
badboy47 said:
Unzip the file with 7zip. Run the flash -all file. Let it do its magic.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I get a text file.
It's a script which is text. If it doesn't run automatically in terminal or bash ( whatever the hell they call it these days on osx) then make it run with it
As long as your fastboot file itself is there it will run.
I think you need to be completely stock (other than unlocked bootloader) to receive OTA updates.
I was on CM10.2 and needed to return the phone to stock. I flashed back to stock 4.3 and was able to update to 4.4.2 with no problems.
Hi,
I Need help .
I have nexus 4 with stock ROM and stock recovery.
Two days after OTA update to Lollipop, the phone got stuck on boot-loop.
The problem is that on the phone i have a very important voice recording of a cop that says he will lie in court.
The court time is coming and i need that recording!
Everywhere i looked, no one has an idea how to recover a boot-loop'ed phone.
The 2 options that people recommended are:
1. RE-Flash the ROM.
Maybe it wont delete the files.
2. Wipe everything and hope that the file is recoverable with one of the software's.
A. What do you recommend?
B. Did someone try any of the recovering software's with any luck of actually recovering?
Your bootloader is locked, correct?
ashyossi said:
Hi,
I Need help .
I have nexus 4 with stock ROM and stock recovery.
Two days after OTA update to Lollipop, the phone got stuck on boot-loop.
The problem is that on the phone i have a very important voice recording of a cop that says he will lie in court.
The court time is coming and i need that recording!
Everywhere i looked, no one has an idea how to recover a boot-loop'ed phone.
The 2 options that people recommended are:
1. RE-Flash the ROM.
Maybe it wont delete the files.
2. Wipe everything and hope that the file is recoverable with one of the software's.
A. What do you recommend?
B. Did someone try any of the recovering software's with any luck of actually recovering?
Click to expand...
Click to collapse
If your bootloader is unlocked you can try flashing TWRP recovery which has a built in file manager and mtp function to copy files to computer. You can also try to "dirty flash" another lollipop rom which will not wipe the data, but may not work.
Yeah, this is the only option, however, this can only happen if his bootloader is unlocked
lolcakes203 said:
Yeah, this is the only option, however, this can only happen if his bootloader is unlocked
Click to expand...
Click to collapse
unfortunately, the bootloader is locked.
what are the chances that "Dirty Flash" wont delete the files?
and what rom should i flash? the same build or maybe try to flash kitkat insted...?
ashyossi said:
unfortunately, the bootloader is locked.
what are the chances that "Dirty Flash" wont delete the files?
and what rom should i flash? the same build or maybe try to flash kitkat insted...?
Click to expand...
Click to collapse
Unfortunately, as far as I know you can't flash any Rom's while your bootloader is locked. You need either fastboot or a custom recovery to flash a custom ROM and both need an unlocked bootloader.
theminikiller said:
Unfortunately, as far as I know you can't flash any Rom's while your bootloader is locked. You need either fastboot or a custom recovery to flash a custom ROM and both need an unlocked bootloader.
Click to expand...
Click to collapse
and flushing the same STOCK rom that i got as OTA should work or does it only work with custom ROM's?
i've looked again.
seems that the bootloader is unlocked!
so, should i flash a TWRP recovery?
ashyossi said:
i've looked again.
seems that the bootloader is unlocked!
so, should i flash a TWRP recovery?
Click to expand...
Click to collapse
Yes, after you've flashed twrp you should be able to access your files from a computer if you're booted in recovery.
soooooo.....
i flashed the TWRP Recovery.
very easy. no errors.
and it shows as the storage is completely empty! as if someone in all this time wiped everything...
so now, what recovery software do you know/used/heard of?
ashyossi said:
soooooo.....
i flashed the TWRP Recovery.
very easy. no errors.
and it shows as the storage is completely empty! as if someone in all this time wiped everything...
so now, what recovery software do you know/used/heard of?
Click to expand...
Click to collapse
When the storage is completely empty, are you booted in recovery, the bootloader or just trying to boot normally? When you say it's empty, do you actually see the device on your computer? If so, is it completely empty with no folders or files or anything, or just stock stuff?
Can you check mount and make sure all the storage volumes are mounted? It's usually blank when they are all manually unmounted.
I am unlocked and unrooted. I had previously upgraded to MM, but ran into some major problems after setting my SD card as internal, and ended up having to use the stock Lollipop tool. So, now i am running stock Lollipop and have received the OTA update. I try running it and it enters the stock recovery ok, the progress bar starts, then after a couple of minutes, i get the dead Andy icon and a quick 'Error' message. It reboots me back to Lollipop and tells me there is an update available and i can try (and fail) again if i want.
A few notes on things i tried to work around this issue (rather than solve it):
1) I have a nandroid i took while in Lollipop, I had it on my PC and i moved it to my sd card but TWRP can't see my SD Card still (E failure to mount SD card). I tried look for solutions to this, but nothing i found worked.
2) so i tried taking the stock MM ROM and moving it to my internal storage and flash that through TWRP, but I couldn't get it to appear in TWRP for selection. I tried look for solutions to this, but nothing i found worked.
3) I took my SD card out completely out, then tried taking the OTA update. Same result: "Error" then reboot.
So, any ideas on how i can get some info on what is causing the failure? Any thoughts on what i can try to resolve this?
chuck-fu said:
I am unlocked and unrooted. I had previously upgraded to MM, but ran into some major problems after setting my SD card as internal, and ended up having to use the stock Lollipop tool. So, now i am running stock Lollipop and have received the OTA update. I try running it and it enters the stock recovery ok, the progress bar starts, then after a couple of minutes, i get the dead Andy icon and a quick 'Error' message. It reboots me back to Lollipop and tells me there is an update available and i can try (and fail) again if i want.
A few notes on things i tried to work around this issue (rather than solve it):
1) I have a nandroid i took while in Lollipop, I had it on my PC and i moved it to my sd card but TWRP can't see my SD Card still (E failure to mount SD card). I tried look for solutions to this, but nothing i found worked.
2) so i tried taking the stock MM ROM and moving it to my internal storage and flash that through TWRP, but I couldn't get it to appear in TWRP for selection. I tried look for solutions to this, but nothing i found worked.
3) I took my SD card out completely out, then tried taking the OTA update. Same result: "Error" then reboot.
So, any ideas on how i can get some info on what is causing the failure? Any thoughts on what i can try to resolve this?
Click to expand...
Click to collapse
I was in the exact same predicament last night, for different reasons though. No matter what I did, I kept getting that same error. I gave up and just flash one of the Roms from this thread since it includes the kernel, radio and stuff http://forum.xda-developers.com/showthread.php?t=3262242.
Sent from my XT1575 using Tapatalk
I had the same issue when i downgraded to LP. There a file you need to flash if you downgraded from MM to LP. I'll post back as soon as I find it.
Sent from my XT1575 using Tapatalk
I have same issue like you guys. I want to root my Moto, and my Wi-Fi won't working. So I downgraded to LL using Restore-To-Stock-Tool and try to upgrade to MM unfortunatelly it isn't work. From OTA I received error, and from recovery also upgrade didn't work? Any ideas how to solve existing problem?
bulsara said:
I had the same issue when i downgraded to LP. There a file you need to flash if you downgraded from MM to LP. I'll post back as soon as I find it.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
That would be great- looking forward to trying out that file.
After running the restore to stock tool you need to flash a file named hlnos in the tools folder.
Sent from my Moto XPE
JoeNeckbone said:
After running the restore to stock tool you need to flash a file named hlnos in the tools folder.
Sent from my Moto XPE
Click to expand...
Click to collapse
I want to make sure i understand the exact files you're referring to. Are you talking about this restore to stock tool?
http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905
If so, I don't see a 'tools' folder in this zip file. So, i am obviously looking in the wrong place. Note: I do remember flashing an additional file at some point after my downgrade. I believe I flashed it when i learned that my wifi didn't work after downgrading to LP. So, if my wifi is now working, it MAY be possible that i already flashed the file you are referring to (though i can't remember what the name of that one was)
chuck-fu said:
I want to make sure i understand the exact files you're referring to. Are you talking about this restore to stock tool?
http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905
If so, I don't see a 'tools' folder in this zip file. So, i am obviously looking in the wrong place. Note: I do remember flashing an additional file at some point after my downgrade. I believe I flashed it when i learned that my wifi didn't work after downgrading to LP. So, if my wifi is now working, it MAY be possible that i already flashed the file you are referring to (though i can't remember what the name of that one was)
Click to expand...
Click to collapse
I'm a little confused, if your trying to go back to lollipop that is the correct modem file, I haven't tried it myself, but I read there should be a tools folder with a hlnos file. If still trying mm then here is the mm modem file.
http://forum.xda-developers.com/showthread.php?p=63574299
Edit: you should verify the md5 for all the files you are using, might have a bad download.
Edit 2: just downloaded the restore zip and took a look, there is no tools folder but filename is
NON-HLOS.bin for lollipop modem.
Sent from my Moto XPE
Sorry for the delay, this is the correct file you need to download NON-HLOS.bin. You can grab it from the link below and only need to flash that file. Hope this helps!
http://thunderztech.com/download-stock-android-6-0-marshmallow-for-moto-x-stylepure-edition-xt1575/
I am in the same issue, but I have the XT1572. Any thoughts?
bulsara said:
Sorry for the delay, this is the correct file you need to download NON-HLOS.bin. You can grab it from the link below and only need to flash that file. Hope this helps!
http://thunderztech.com/download-stock-android-6-0-marshmallow-for-moto-x-stylepure-edition-xt1575/
Click to expand...
Click to collapse
Thanks for trying to help, but that was the file I had originally flashed. I did try again and no luck still.
I just tried again to manually flash the MM ROM and still can't do it. I keep getting the error: "E:Cannot restore System -- mounted read only. " from TWRP. Looking around it seems like i'm sort of stuck. Other phone owners have had to resort to using ruu and restoring directly from their PC. I've done this in the past with my HTC M7, but don't know if things are different (or even applicable) with the MotoXPE, so i need to do some searching around.
If anyone has any thoughts on how to best install a ROM directly from my PC, please share your thoughts. I think this is sideloading, right? I've sideloaded files before, but never ROMs (expect for maybe when i did it with my old M7)
chuck-fu said:
Thanks for trying to help, but that was the file I had originally flashed. I did try again and no luck still.
I just tried again to manually flash the MM ROM and still can't do it. I keep getting the error: "E:Cannot restore System -- mounted read only. " from TWRP. Looking around it seems like i'm sort of stuck. Other phone owners have had to resort to using ruu and restoring directly from their PC. I've done this in the past with my HTC M7, but don't know if things are different (or even applicable) with the MotoXPE, so i need to do some searching around.
If anyone has any thoughts on how to best install a ROM directly from my PC, please share your thoughts. I think this is sideloading, right? I've sideloaded files before, but never ROMs (expect for maybe when i did it with my old M7)
Click to expand...
Click to collapse
Are you rooted and have custom recovery on your device?
Sent from my XT1575 using Tapatalk
bulsara said:
Are you rooted and have custom recovery on your device?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I'm not rooted, but i do have TWRP 2.8.7.1-clark on the device.
chuck-fu said:
I'm not rooted, but i do have TWRP 2.8.7.1-clark on the device.
Click to expand...
Click to collapse
You need to make sure you are on factory recovery.
1. downgrade again to moto 5.1 with stock recovery
2. from stock recovery factory reset your device
3. reboot bootloader and then flash the file again.
that should solve your issue.
chuck-fu said:
I'm not rooted, but i do have TWRP 2.8.7.1-clark on the device.
Click to expand...
Click to collapse
In twrp, settings, mount, is system checked or not checked? I checked mine and it is off by default and I don't switch it when flashing.
Sent from my Moto XPE
bulsara said:
You need to make sure you are on factory recovery.
1. downgrade again to moto 5.1 with stock recovery
2. from stock recovery factory reset your device
3. reboot bootloader and then flash the file again.
that should solve your issue.
Click to expand...
Click to collapse
I tried that with the same issue as the op to no avail, ended up going with one of the stock roms. Have another issue but I'll be making a new thread with that.
Sent from my XT1575 using Tapatalk
bulsara said:
You need to make sure you are on factory recovery.
1. downgrade again to moto 5.1 with stock recovery
2. from stock recovery factory reset your device
3. reboot bootloader and then flash the file again.
that should solve your issue.
Click to expand...
Click to collapse
Thanks for the advice. I'll try that here. Just to be sure, for step 1, I assume you mean to use this tool, correct: (http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905)
Or did you downgrade to moto 5.1 using a different method?
bulsara said:
You need to make sure you are on factory recovery.
1. downgrade again to moto 5.1 with stock recovery
2. from stock recovery factory reset your device
3. reboot bootloader and then flash the file again.
that should solve your issue.
Click to expand...
Click to collapse
Also- when you say: "3. reboot bootloader and then flash the file again." Are you suggesting that i should flash my stock MM Rom at that point? If so, just to be clear, i'll need to flash TWRP recovery again, move the MM ROM over, then flash it from inside TWRP, correct?
Or are you saying something different?
Edit: Well, I went ahead and loaded TWRP back on and tried restoring the stock MM Rom. Once again, i got the E: Failure to Mount error when trying to restore (interestingly, i can backup the existing ROM without issue). So, i went ahead and just booted up in hopes that i'd now be able to accept the OTA rom. I just downloaded it, and with stock recover in place, got the same Error and Dead Andy screen.
One note: When i first loaded TWRP, it asks if i want to leave things Read Only and receive OTAs or allow it to be writable. I think in the past i allowed it to be writable (which would've explain the OTA failures of the past), so this time I left it Read Only figuring that would fix my issue. No luck. It still failed.
Any additional ideas would be most welcome. I'm out of ideas here.
JoeNeckbone said:
In twrp, settings, mount, is system checked or not checked? I checked mine and it is off by default and I don't switch it when flashing.
Sent from my Moto XPE
Click to expand...
Click to collapse
Just checked this and system is not checked. I don't think i've ever changed it either.
Issue resolved-
I never figured out how to get around the Error during OTA install, but i did get on MM. I case this somehow helps anyone, here's what i ended up doing.
1) Used the Restore to 511 stock tool (non-rooted)
2) booted into 511 and set things up
3) reformatted my SD card for use (it had previously been set up to be used as internal storage when i had MM working a couple of weeks ago)
4) flashed TWRP 5.1.1
5) rooted using install of SU zip file (rather than TWRP's "do you want to root this device"
6) Rebooted? (maybe i did this. don't remember)
7) Loaded the stock MM rom onto my SD card
8) Went back into TWRP and made my internal partition writeable (Note: i initially tried to say yes to when TWRP asked me if i wanted to root, but this prevented the device from booting after i restored the MM Rom (in the next step), so i just said no to that. If i decide to root later, i will do so by installing SU from zip.
9) Restored the stock MM rom from the SD card
Now up and running on MM. Will not allow my SD card to be used as internal- which is what started this mess.
Currently don't seem to have wifi working. I had this issue when i downgraded to 5.1.1 and needed to flash the NON-HLOS.bin file. I am trying to find out if i need to do the same here.
Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.
tele_jas said:
Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.
Click to expand...
Click to collapse
Yes you can via Rczrider 's TWRP backup
tele_jas said:
Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.
Click to expand...
Click to collapse
XblackdemonX said:
Yes you can via Rczrider 's TWRP backup
Click to expand...
Click to collapse
Yeah, it looks like @tenfar updated their tool to use the stock files from my untouched B20: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
rczrider said:
Yeah, it looks like @tenfar updated their tool to use the stock files from my untouched B20: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Click to expand...
Click to collapse
if someone can make a guide on HOW-TO (Steps + FIles + Images needed) i can give it a shot...
just send me a PM if you know the HOW-TO :good:
Mmmmm, noone yet?.... I guess I'll start gathering info.
One thing I wanna make sure flashing @tenfar boot. Img = need Data wipe right?
DrakenFX said:
Mmmmm, noone yet?.... I guess I'll start gathering info.
One thing I wanna make sure flashing @tenfar boot. Img = need Data wipe right?
Click to expand...
Click to collapse
I've been flashing custom ROM's for several years, but I've bricked one too many phones over the years "not knowing" the correct way to do certain things... So I started this thread to see what those steps were because I'm too scared to attempt it myself. :silly:
So, I know I'd appreciate your efforts in this!
tele_jas said:
I've been flashing custom ROM's for several years, but I've bricked one too many phones over the years "not knowing" the correct way to do certain things... So I started this thread to see what those steps were because I'm too scared to attempt it myself. :silly:
So, I know I'd appreciate your efforts in this!
Click to expand...
Click to collapse
I'm curious too and I wanna give it shot,
P. S. Any way to use terminal or adb to pull the partition list with their Extension?
Like for sample. " ext4 system /dev/block/sde13 " or something similar with extension?
Has anyone got a step-by-step for this yet? I searched, but don't see a "Back to Stock" thread
tele_jas said:
Has anyone got a step-by-step for this yet? I searched, but don't see a "Back to Stock" thread
Click to expand...
Click to collapse
i created a Thread for users who have run into the No Boot issues and those problems , so i can gather more info of the causes of their problems but nobody had reply yet,
just waiting so i can test things and get back to Stock B20 with Root + TWRP and lock bootloader
It is still not clear where the unlock bootloader state is recorder. I have checked a couple of partitions but they are identical to locked B20 (aboot, devinfo were my prime suspects)
So assuming that this is not a permanent thing for the bootloader state and can be reversed, steps would be something like this
1. lock bootloader
2a. flash Stock B20 image and signed(tenfars) TWRP via axon7root
3. Reboot in TWRP (read only mode), full factory wipe (wipe plus /data format), flash original system image via twrp, wipe data again
4. turn off phone, don't reboot (no system start)
5. flash stock recovery via axon7root
6. Reboot to Stock Recovery direct (do not boot)
7. Factory reset from stock recovery
8. Reboot
But there are a few unknowns yet, even with stock system, boot and recovery we still have stuck loops unless using modded boot. My guess is that TWRP mods /system on exit, that's why i put read only mode but not sure if you can restore it if it's not rw. Since it's image to device it should work, RW is for mounting partition
And big one is if unlock state is permanent or not, not sure anyone tried yet
peramikic said:
It is still not clear where the unlock bootloader state is recorder. I have checked a couple of partitions but they are identical to locked B20 (aboot, devinfo were my prime suspects)
So assuming that this is not a permanent thing for the bootloader state and can be reversed, steps would be something like this
1. lock bootloader
2a. flash Stock B20 image and signed(tenfars) TWRP via axon7root
3. Reboot in TWRP (read only mode), full factory wipe (wipe plus /data format), flash original system image via twrp, wipe data again
4. turn off phone, don't reboot (no system start)
5. flash stock recovery via axon7root
6. Reboot to Stock Recovery direct (do not boot)
7. Factory reset from stock recovery
8. Reboot
But there are a few unknowns yet, even with stock system, boot and recovery we still have stuck loops unless using modded boot. My guess is that TWRP mods /system on exit, that's why i put read only mode but not sure if you can restore it if it's not rw. Since it's image to device it should work, RW is for mounting partition
And big one is if unlock state is permanent or not, not sure anyone tried yet
Click to expand...
Click to collapse
those steps were the same i was planning to do plus flashing something else, but seems like i may be not doing the other flashing file now......well still gathering more info and will see.
P.S. Thanks for the info. @peramikic
DrakenFX said:
i created a Thread for users who have run into the No Boot issues and those problems , so i can gather more info of the causes of their problems but nobody had reply yet,
just waiting so i can test things and get back to Stock B20 with Root + TWRP and lock bootloader
Click to expand...
Click to collapse
Gottcha.... I was just curious, because I'm starting to have a few random issues (reboots, apps opening without tapping them, google voice commands not working like they did just a few days ago) I'd like to get back to stock and maybe start over. Of course, I didn't make a backup up until after I flashed SuperSU and my apps downloaded so I have no "stock" TWRP backup. **But, this all could be "theme" related too, since I'm running a dark theme that isn't quite compatible with the A7 yet.
I may try removing the theme and let it run a day or two and see how it does?
I have twrp installed on a T-mobile h918 lg v20. I ended up selling my v20 to my grandpa. It works fine, but he tried to take an ota and it got stuck in a twrp bootloop. I reflashed twrp recovery and the phone is working fine again, but it still wants to install the OTA.
I realize once I install the stock recovery.img it will be impossible to get twrp again, but my grandpa will be using the phone for the next few years, and I'd rather it be able to get system updates.
Does anyone have a stock recovery.img for the tmobile LG V20? I'd like the one from the 10q build if possible (that's what the phone is currently running), but I don't know how often the recovery.img actually gets updated so an older/newer stock recovery.img might work as well.
I understand I can use a whole kdz to flash the whole thing to stock, but the rest of the phone is already stock, and I'd rather not risk losing installed apps and stuff or making them unstable. I just want to flash the stock recovery.img in twrp.
Thanks in advance!
I can't post it for you today, but if you can wait till tomorrow, I will send you a link.
steven_computer_guy said:
I have twrp installed on a T-mobile h918 lg v20. I ended up selling my v20 to my grandpa. It works fine, but he tried to take an ota and it got stuck in a twrp bootloop. I reflashed twrp recovery and the phone is working fine again, but it still wants to install the OTA.
I realize once I install the stock recovery.img it will be impossible to get twrp again, but my grandpa will be using the phone for the next few years, and I'd rather it be able to get system updates.
Does anyone have a stock recovery.img for the tmobile LG V20? I'd like the one from the 10q build if possible (that's what the phone is currently running), but I don't know how often the recovery.img actually gets updated so an older/newer stock recovery.img might work as well.
I understand I can use a whole kdz to flash the whole thing to stock, but the rest of the phone is already stock, and I'd rather not risk losing installed apps and stuff or making them unstable. I just want to flash the stock recovery.img in twrp.
Thanks in advance!
Click to expand...
Click to collapse
If you don't want to wait you can just extract it yourself from stock rom
Thanks! I extracted a rom zip I found on xda but it has a recoverybak.bin, can I just rename the .bin file to an img file? I also downloaded the kdz and attempted to extract it, I tried the ext2 partition tool for Windows but I wasn't able to extract it. If someone could tell me how to extract the kdz that works too. Thank you so much both of you for the quick responses!
runningnak3d said:
I can't post it for you today, but if you can wait till tomorrow, I will send you a link.
Click to expand...
Click to collapse
That would be awesome! I can totally wait for a day or two. I will be awaiting your link. Thank you!
Still_living714 said:
If you don't want to wait you can just extract it yourself from stock rom
Click to expand...
Click to collapse
I am having difficulty extracting the kdz. Any tips?
steven_computer_guy said:
I am having difficulty extracting the kdz. Any tips?
Click to expand...
Click to collapse
Check pm
Ended up flashing the whole KDZ because I couldn't obtain the img file. Thanks to everyone who tried to help out. Everything is good now.