Database Users

Q: uninstalling TWRP without going back to stock completely?

Hi,
I have an LG G2 D802 and already installed TWRP 2.6.3.4 for installing zip-files. But now there is an update (only browser, but 4.4 shouldn't be that far away), but without stock recovery it's impossible to install it I know the way how to get back to stock completely, but I don't want to go back to stock every time there is an update, installing all of them and then reinstall TWRP. I think on CWM the problem is the same, but i don't want to miss the camera tweak and splitwindow, so I need an custom recovery for the zip-files:crying: Is there any way to get the stock recovery back without installing complete stock or at least a possibility, to only "boot" the custom recovery when I'm back on stock, like on Nexus devices, and only use it for the flashing and then lose it on the next reboot?

You should be able to push stock recovery via adb or even flashify ( I prefer adb tho). What build number do you have?
Sent from chdhsheh fhhdud

simon_lefisch said:
You should be able to push stock recovery via adb or even flashify ( I prefer adb tho). What build number do you have?
Sent from chdhsheh fhhdud
Click to expand...
Click to collapse
I have D80210a-EUR-XX. But where can I find the stock recovery? And btw: what was the adb command for flashing? With my Nexus 4 I only used the ToolKit, because I was never able to use adb through the normal Win7 cmd, only through the toolkit...

most likely, but cannot confirm it, you ooen a stock kdz, and try flashing the kernel .img thats inside, I am not sure
anyone confirm it works that way
Sent from my LG-D802 using xda app-developers app

for all I know, the kernel doesn't contain any recovery... but I will test it tomorrow, when I downloaded the kdz if you could say me how to open a kdz-file.

Artim_96 said:
I have D80210a-EUR-XX. But where can I find the stock recovery? And btw: what was the adb command for flashing? With my Nexus 4 I only used the ToolKit, because I was never able to use adb through the normal Win7 cmd, only through the toolkit...
Click to expand...
Click to collapse
here is a link to D802 recovery.img file i found, however its for the 10B build. you should be ok as i dont think the recovery has changed much from 10A to 10B, however i cannot confirm this. use this at your own risk, unless someone can confirm this will recovery will work.

simon_lefisch said:
here is a link to D802 recovery.img file i found, however its for the 10B build. you should be ok as i dont think the recovery has changed much from 10A to 10B, however i cannot confirm this. use this at your own risk, unless someone can confirm this will recovery will work.
Click to expand...
Click to collapse
If it's not working, I have a backup of the current. but I will test it tomorrow, then I have more time. But thanks for the quick answers.

Flashing the 10B recovery image worked well. But installing the update I only get an error so I go back to stock now.
I saw that flashify can flash zip files. Does it flash them itself or does it also need a custom recovery to flash them with it and flashify is only some sort of automtatisation? Then I could use this when I'm back on stock 10A (there seems to be no 10B for my device).

Artim_96 said:
Flashing the 10B recovery image worked well. But installing the update I only get an error so I go back to stock now.
I saw that flashify can flash zip files. Does it flash them itself or does it also need a custom recovery to flash them with it and flashify is only some sort of automtatisation? Then I could use this when I'm back on stock 10A (there seems to be no 10B for my device).
Click to expand...
Click to collapse
I've had similar problem, i think I just installed the KDZ file trough the way they showing: http://forum.xda-developers.com/showthread.php?t=2432476
It just erased the rooy and TWRP, and all of the apps and settings did not change, its like a repach.

at least it should be. but I can't take the last step. "By turning off, Holding down power and Vol Down until it comes up on the screen." doesn't works, there only starts the normal software, and that's the old one. And unpacking the kdz file with 7zip or Peazip also don't work. Peazip can do ist, but I have to find out how to let it extract it. After installing it, there is another file with the same name, but it's an .cab file with password. If I boot over widgetsoid into recovery (I think this is what the manual means) there is only a little droid with a read sign. How to get further?
EDIT: found out how to come into that menu. It wants to make a hard reset so I make an backup first.

Finally I was able to install the complete new software version (D80210e-EUR-XX) over the LG PC Suite. The file downloaded from the manual seemed to be corrupted or so as it only caused an unpacking error in the programm.
Does anybody knows a way how to flash a zip without a custom rom? Flash Gordon seems to not work.

[Q] Why is this so hard to install recovery!

Greetings,
First I'm sorry if this isn't the right thread for this, I'll gladly delete and change threads if need be.
Second, I just got an LG G2 (Verizon) today. It's great but I want more so I rooted it, confirmed that it's rooted. But that's all I can do. I can't install a recovery app on here to save my life. I tried downloading the VZW recovery img and pushing that with the loki_flash but I got two errors mainly.
Input file is not a valid loki image and Loki aboot does not match device. I'm trying to run either TWRP or CWM, anything really so I can flash a custom ROM on this bad boy.
If the image is not a valid loki image I'm assuming I don't have the right pair of files? (loki/recovery) and if the aboot image doesn't match the device I'm assuming that I don't have the right loki? Are these correct assumptions or am I making an ass out of just me???
My phone is rooted, ROM Manager says I have both TWRP AND CWM on my phone but if I try to boot into recovery via ROM Manager or adb I get a black screen and nothing more.
Does anyone have ANY insight at all into how I can go about the next step?

paryguy said:
Greetings,
First I'm sorry if this isn't the right thread for this, I'll gladly delete and change threads if need be.
Second, I just got an LG G2 (Verizon) today. It's great but I want more so I rooted it, confirmed that it's rooted. But that's all I can do. I can't install a recovery app on here to save my life. I tried downloading the VZW recovery img and pushing that with the loki_flash but I got two errors mainly.
Input file is not a valid loki image and Loki aboot does not match device. I'm trying to run either TWRP or CWM, anything really so I can flash a custom ROM on this bad boy.
If the image is not a valid loki image I'm assuming I don't have the right pair of files? (loki/recovery) and if the aboot image doesn't match the device I'm assuming that I don't have the right loki? Are these correct assumptions or am I making an ass out of just me???
My phone is rooted, ROM Manager says I have both TWRP AND CWM on my phone but if I try to boot into recovery via ROM Manager or adb I get a black screen and nothing more.
Does anyone have ANY insight at all into how I can go about the next step?
Click to expand...
Click to collapse
Sorry didn't mean to hit the thanks button.
What build are you on (11A,12B? What recovery image are you using (ie, from what thread)?
Sent from chdhsheh fhhdud

TWRP
Follow the install instructions for TWRP 2.6.3.2. Then after you've confirmed you can boot the OS from the recovery, place the 2.6.3.3 on the root of your SD. Reboot into recovery and flash 2.6.3.3. Reboot into recovery again and you'll be good to go.
Version 2.6.3.2 won't flash 4.4 ROMs but 2.6.3.3 will flash 4.2 (I'm assuming), 4.3, and 4.4.

Download FreeGee app from the play store and install TWRP recovery from it. It was the only way I could install it on my LG G2.

So many
simon_lefisch said:
Sorry didn't mean to hit the thanks button.
What build are you on (11A,12B? What recovery image are you using (ie, from what thread)?
Sent from chdhsheh fhhdud
Click to expand...
Click to collapse
I followed many tutorials last night including this one.
(I am too new to post links in a message.) The link I was going to post was from howtorootmobiledotcom
I downloaded any version of TWRP I could, there were only 2, one img of each version and one zip. I used the loki from the zip that came with it as well but still no go.

paryguy said:
I followed many tutorials last night including this one.
(I am too new to post links in a message.) The link I was going to post was from howtorootmobiledotcom
I downloaded any version of TWRP I could, there were only 2, one img of each version and one zip. I used the loki from the zip that came with it as well but still no go.
Click to expand...
Click to collapse
What build number are you on?
Sent from chdhsheh fhhdud

vnrse Theologisch
simon_lefisch said:
What build number are you on?
Sent from chdhsheh fhhdud
Click to expand...
Click to collapse
I used RussGJohnson solution and it worked in a matter of seconds. Now I'm stuck though. I wiped everything and can boot into TWRP but I have no ability to sideload anything. I have all the latest LG drivers, even the lastest android sdk drivers, nothing is working. If I boot up normally the LG logo comes up and just sits there.
I can boot into recovery using the whole volume down + power button combo but then when I go to sideload my computer isn't seeing the device. I'm on a Win 8 machine using the stock cable. I've tried both USB 2 and 3 ports

It's done
Using RussGJohnson's suggestion worked great.
The issue I had with being unable to sideload a ROM wasn't resolved but I just used my Mac to do it instead. That worked just fine. Win8 couldn't recognize the device while in recovery. Go figure.

free gee very fast

Use Flashify u n00b.

Need help, urgent

Hi, I have a D806 G2 and I have a big problem.
After an error modifying my build.prop I was left with a broken phone. It wouldn't boot to the os.
I was rooted and with TWRP so I restarded and tried to revert to the old build.prop (that's the only backup I had) and it didn't work.
I followed the tutorials to go back to stock (I had done it once before to update my phone while rooted, but that time the phone was working fine).
Well, to my surprise, given that I only had recovery or download mode, the process started but failed with an error.
Now, I don't have a System, meaning that my system folder is empty so I really don't have an os in the phone, and all procedures to flash a rom, fail.
I have tried flashtools and everyother tool but nothing, can't put a rom in the phone.
Now I'm kinda desperated because It is too expensive for me to loose the phone (things in Argentina are far too expensive) and when I put it in download mode it clearly says ROOTED so I will have a problem with guaranty.
Please, someone give me a hand!!

MasterTB said:
Hi, I have a D806 G2 and I have a big problem.
After an error modifying my build.prop I was left with a broken phone. It wouldn't boot to the os.
I was rooted and with TWRP so I restarded and tried to revert to the old build.prop (that's the only backup I had) and it didn't work.
I followed the tutorials to go back to stock (I had done it once before to update my phone while rooted, but that time the phone was working fine).
Well, to my surprise, given that I only had recovery or download mode, the process started but failed with an error.
Now, I don't have a System, meaning that my system folder is empty so I really don't have an os in the phone, and all procedures to flash a rom, fail.
I have tried flashtools and everyother tool but nothing, can't put a rom in the phone.
Now I'm kinda desperated because It is too expensive for me to loose the phone (things in Argentina are far too expensive) and when I put it in download mode it clearly says ROOTED so I will have a problem with guaranty.
Please, someone give me a hand!!
Click to expand...
Click to collapse
Can you still get to TWRP (recovery)? Which version of TWRP are you using? Do you still have the zip file of the ROM you're on?
Sent from my LG-D800 using Tapatalk

Jank4AU said:
Can you still get to TWRP (recovery)? Which version of TWRP are you using? Do you still have the zip file of the ROM you're on?
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Sorry was too crazy to post most data.
No I don't have a backup of my rom, but I got a backup from another phone and it doesn't work
Gladly I could use a USB OTG to copy Carbon and Gapps to the phone and I could install that so the phone is working now.
The problem is going back to stock because I would need a backup of a D806 rom and I don't have one.
I'm on TWRP 2.6.3.4 and it's working fine now. Thank you very much.,

Very simple and very lucky you still can access download mode. Just using flashtools to flash TOT again then its all go back to original stock.

cccho said:
Very simple and very lucky you still can access download mode. Just using flashtools to flash TOT again then its all go back to original stock.
Click to expand...
Click to collapse
what is TOT? i need this to back stock rom

cccho said:
Very simple and very lucky you still can access download mode. Just using flashtools to flash TOT again then its all go back to original stock.
Click to expand...
Click to collapse
I would if I could, but my IMEI reads 0, hence no luck with LG software.
Luckily I could boot the phone to an AOSP rom (copied via USB OTG to my phone -I still have recovery-)
So, I have an AOSP rom, I can get a backup of a similar rom to my stock rom -from a user in another forum- and I can install that backup (foing it ATM)
BUT, my IMEI is 0 so LG software doesn't fully recognize my rom and drivers don't fully install
HELP??

nicogarcia1229 said:
what is TOT? i need this to back stock rom
Click to expand...
Click to collapse
Read this and do more seach.
http://forum.xda-developers.com/showthread.php?t=2541030

[HowTo][Temporary] Fix stuck at Boot from Downgrading Android 4.4.4 to 4.4.2

If you Softbricked your phone and are stucked at the Google Unlocked Logo you're right here... the major point of this is to unbrick the phone and not to set it in derivation condition and btw.... unbrick flashing etc at your own risk
Download:
https://drive.google.com/file/d/0B6IdzeLKSZoGX1NzZTlmNVdKeWM/edit?usp=sharing
THIS IS THE GERMAN STOCK ROM MOTOROLA XT1032! IT'S REPORTED THAT THERE COULD BE NO GSM SIGNAL & WIFI!!!!
Hey Guys,
i dont know if this is posted somehere here at the MotoG XDA section....
I tried the MotoG GPe Rom and received an OTA Update to Android 4.4.4 and installed it. After reverting to Motorola stock rom or GPe 4.4.2 the phone stucks in the boot logo and won't boot up anymore.
So here's is MY fix for the problem and i hope i can help some... it's a temporal fix right now to unbrick the half-bricked MotoG for further development
1. Restart Phone in Bootloader
Power + Volume down to enter the bootloader mode and flash the GPe Recovery as *.img file from Philz with fastboot command​
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
2. Enter the Recovery Mode
Enter the recovery mode with selecting "Recovery" and hit the volume up to enter it.
In recovery mode you will get some error messages like in the attached phote below. To fix these messages:​
Mounts and Storage --> hit "format /cache" and "format /data and /data/media (/sdcard)"
Click to expand...
Click to collapse
3. Push CWM Backup to /sdcard
You have to push a cwm Backup to the /sdcard to restore it later
Download my package with adb and cwm backup and unzip it wherever you want after the extraction and double click at "111 push cwm files to sdcard.bat" to push all need files to tranfer them to the sdcard​
adb push boot.img /sdcard/clockworkmod/backup/2014/boot.img
adb push cache.context /sdcard/clockworkmod/backup/2014/cache.context
adb push cache.ext4.tar /sdcard/clockworkmod/backup/2014/cache.ext4.tar
adb push cache.ext4.tar.a /sdcard/clockworkmod/backup/2014/cache.ext4.tar.a
adb push data.context /sdcard/clockworkmod/backup/2014/data.context
adb push data.f2fs.tar /sdcard/clockworkmod/backup/2014/data.f2fs.tar
adb push data.f2fs.tar.a /sdcard/clockworkmod/backup/2014/data.f2fs.tar.a
adb push nandroid.md5 /sdcard/clockworkmod/backup/2014/nandroid.md5
adb push recovery.img /sdcard/clockworkmod/backup/2014/recovery.img
adb push recovery.log /sdcard/clockworkmod/backup/2014/recovery.log
adb push system.context /sdcard/clockworkmod/backup/2014/system.context
adb push system.ext4.tar /sdcard/clockworkmod/backup/2014/system.ext4.tar
adb push system.ext4.tar.a /sdcard/clockworkmod/backup/2014/system.ext4.tar.a
Click to expand...
Click to collapse
4. Restore CWM Backup
Restore the CWM backup from "Restore from /sdcard" select the 2014 folder and confirm... after sucessful restoring you are able to boot up your MotoG​
I hope this worked as a temporal fix Feedback or critics are welcome!!!!

fl4m3y said:
Download link will follow in 1 or 2 hours... it's still uploading to my gdrive
Hey Guys,
i dont know if this is posted somehere here at the MotoG XDA section....
I tried the MotoG GPe Rom and received an OTA Update to Android 4.4.4 and installed it. After reverting to Motorola stock rom or GPe 4.4.2 the phone stucks in the boot logo and won't boot up anymore.
So here's is MY fix for the problem and i hope i can help some... it's a temporal fix right now to unbrick the half-bricked MotoG for further development
1. Restart Phone in Bootloader
Power + Volume down to enter the bootloader mode and flash the GPe Recovery as *.img file from Philz with fastboot command​
2. Enter the Recovery Mode
Enter the recovery mode with selecting "Recovery" and hit the volume up to enter it.
In recovery mode you will get some error messages like in the attached phote below. To fix these messages:​
3. Push CWM Backup to /sdcard
You have to push a cwm Backup to the /sdcard to restore it later
Download my package with adb and cwm backup and unzip it wherever you want after the extraction and double click at "111 push cwm files to sdcard.bat" to push all need files to tranfer them to the sdcard​
4. Restore CWM Backup
Restore the CWM backup from "Restore from /sdcard" select the 2014 folder and confirm... after sucessful restoring you are able to boot up your MotoG​
I hope this worked as a temporal fix Feedback or critics are welcome!!!!
Click to expand...
Click to collapse
I haven't had the need to try this but I think its good I'm going to stick with CWM for a while until the update for non GPE devices is out or android L..
Sent from my Moto G using XDA Free mobile app

will have a link

Waiting the downlod link :good:

cecoicov said:
will have a link
Click to expand...
Click to collapse
borimol said:
Waiting the downlod link :good:
Click to expand...
Click to collapse
Download Link is online...

Phone works, but does not recognize the SIM card and no WIFI

cecoicov said:
Phone works, but does not recognize the SIM card and no WIFI
Click to expand...
Click to collapse
Can you now flash official 4.4.2 stock (non GPE)?

cecoicov said:
Phone works, but does not recognize the SIM card and no WIFI
Click to expand...
Click to collapse
works fine for me
borimol said:
Can you now flash official 4.4.2 stock (non GPE)?
Click to expand...
Click to collapse
no... flashing with fastboot wont work until we get the GPe Factory Image (I hope) or another fix... this is a "work around" but the problem isn't fixed

after flash with official stock 4.4.2 (non GPE) does phone not start again

cecoicov said:
after flash with official stock 4.4.2 (non GPE) does phone not start again
Click to expand...
Click to collapse
Fastboot flashes doesn't work until there is a real fix... if the stuck on boot logo persist just follw my tutorial to unbrick the phone

Ок, thanks for the help but I guess I will seek another solution

cecoicov said:
Phone works, but does not recognize the SIM card and no WIFI
Click to expand...
Click to collapse
Same issue occurred to me, the IMEI paste seems to be gone rendering the phone useless for (data) network usage. There's no way to restore the IMEI at the moment.

ok this worked for me
started cyanogenmod????????
i could not test wifi or network
but off course i am dumb, and had to try to restore a nandroid backup of gep 4.4.4, i did and phone ask for password (because of encryption of file system), then i tried again to recover using this method and did not worked, used adb gpe 4.4.2, then again this method and nothing
what the hell
firts time could recover, now it wont recover anymore, stays on google logo lol
--------------
some time latter i managed to boot it again
it started stock android in german?'
i believe there is no signal

maurocds said:
some time latter i managed to boot it again
it started stock android in german?'
i believe there is no signal
Click to expand...
Click to collapse
It's the open german version without any provider stuff... i cant upload th english version because i cant flash via fastboot. the only possibility is to install an english custom rom via cwm. therfore you need to replace the GPe CWM recovery to normal philz recovery because of the filesystem

fl4m3y said:
It's the open german version without any provider stuff... i cant upload th english version because i cant flash via fastboot. the only possibility is to install an english custom rom via cwm. therfore you need to replace the GPe CWM recovery to normal philz recovery because of the filesystem
Click to expand...
Click to collapse
hey man, i sent you a PM, read it fast
-----------
ok i booted my phone again after flashing this, then flashing gpe, then this again lol
you have to be patient while pushing the data, it takes a lot, then after that, you must disable md5 on recovery or else it will fail, then you can restore cwm fine and boot
firmware is stock 442 german, but you can change into english
thanks, no matter what i tried i never could boot
at least the phone work,
have to test more about signal stuff

Due to some personal information (google account) i was forced to deactivate the public access to the file.... password changed of my account and now it should be fine
so download is activated again

Hey,
I´ve been using GPE 4.4.4 recently too and I wanted to go back to German retail 4.4.2. in order to try to catch an OTA. It´s quite easy to do, just beware of one thing. You have to RETAIN the partition table (gpt.bin) from GPE. Do not flash gpt.bin from the target firmware - 4.4.2 in this case, just avoid the step "fastboot flash partition gpt.bin". If you did it already, you can try following: extract gpt.bin from GPE 4.4.4 OTA zip and copy it and replace gpt.bin in your 4.4.2 firmware folder and then flash it using standard procedure.
Also maybe the same thing applies to logo.bin, but of this one I´m not sure. I avoided to flash it too just in case. Now I´m on fully working German retail 4.4.2. No OTA yet, though, but that´s another story.

anyone has the gpt.bin from the GPe 4.4.4????
I want to flash via fastboot the GPe 4.4.2 Version and after the OTA Update to 4.4.4
and btw... thank you for the hint!!!!

View attachment gpt.7z
fl4m3y said:
anyone has the gpt.bin from the gpe 4.4.4????
I want to flash via fastboot the gpe 4.4.2 version and after the ota update to 4.4.4
and btw... Thank you for the hint!!!!
Click to expand...
Click to collapse
from ota gpe 444

drfr said:
Hey,
I´ve been using GPE 4.4.4 recently too and I wanted to go back to German retail 4.4.2. in order to try to catch an OTA. It´s quite easy to do, just beware of one thing. You have to RETAIN the partition table (gpt.bin) from GPE. Do not flash gpt.bin from the target firmware - 4.4.2 in this case, just avoid the step "fastboot flash partition gpt.bin". If you did it already, you can try following: extract gpt.bin from GPE 4.4.4 OTA zip and copy it and replace gpt.bin in your 4.4.2 firmware folder and then flash it using standard procedure.
Also maybe the same thing applies to logo.bin, but of this one I´m not sure. I avoided to flash it too just in case. Now I´m on fully working German retail 4.4.2. No OTA yet, though, but that´s another story.
Click to expand...
Click to collapse
THIS DID NOT WORK FOR ME
I AM ON 4.4.4 gpe
AND JUST WANTED TO TEST
so i put the 4.4.4 ota gpt.bin in the stock 4.4.2 image , and the stock gpe 4.4.2, and both flashes were stuck on logo, did not booted,

Stock Recovery .img

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.