Hello,
Recently I have been running AOSP rom on the LG G2, I tried to recently apply the 4.4.2 update via the ripped LG Gpro in android developement. However to my own stupidity I did not follow instructions correctly already being on 4.4.2. The rom flashed however not correctly, with exsesive over heating and no sim connection as well as many other bugs. I have tried to re-instal custom recovery but cannot due to the 4.4.2 update. I then tried to flash a Kdz file via lg software to downgrade back to 4.2.2 but it will not flash as it connects and states that I already have the most up to date software even after adding the 4.2.2 file.
The phone is stuck on the custom rom, it is now rooted via the normal method, unable to instal a custom recovery and have had no look re-flashing a stock or another rom via software.
Overall goal is to get back to stock, and take it from there. Can anyone surgest any alternative methods to re-flash standard rom or instal a custom recovery to then apply a different rom.
Other information, phone switches on and can connect to a pc and recognised. No issues to this style of use but not able to be used a phone.
Any information would be great,
Thanks,
Jordan
Looks like we now must use the offline method described here
http:// forum.xda-developers.com/showthread.php?t=2625044
LG software update has blocked downgrade path using the Flash Tool. If you're on T-Mo you MUST flash back to 80110c, NOT g.
Related
Hello people. I have to ask one question about my LG L5 E610.
My L5 E610 has stock 4.1.2 baseband 20G, most updated to date, I updated via KDZ updater.
I already rooted and installed custom ROM on three differents phones, ZTE and Samsung, never had any problems, so I can say that I have some experiences, but in case of samsung, for use warranty, is needed to install everything stock and reset flash counter, so I wonder if my E610 will be needed the same procedures ?
I'm thinking of installing CM10.2 on my LG L5 E610, I believe one day I will do this, but then I need to know how to install back EVERYTHING STOCK IN CASE OF WARRANTY, but never found tutorial about it, never heard if LG has flash counter, but I bet doesn't have.
anyone can tell me if it's possible or explain me how to install stock ROM, stock Recovery and stock Kernel after customizate everything on E610 ?
Never heard about flash counter.
For returning all to stock (as far as i know) you must have 2 kdz
1: v10d_downgrade , made by someone in 4pda, search it over internet. Its special because it wipes out everything, others kdz just flash up system and that's it, if you already have a bootloop or have a custom rom that may be not compatible with stock, normal kdz wont boot at all.
2: your OFFICIAL stock kdz for your VERSION (e610/e612/e612g/f, etc) get it from here
In case you want to return to stock, boot in download mode (hold vol - / + while connecting usb cable until vibrate) and flash it up. Flash v10d... let it boot (it'll be in russian lol) and then flash your normal kdz (by booting in download mode again)
Then, you can try anything you want (pls, don't mess with swap partition, 2 phones are almost hard-bricked while playing with that and it couldn't flash kdz either!)
Good Luck!
just use the kdz updater
Sent from my LG-P700 using xda app-developers app
raul338 said:
Never heard about flash counter.
Good Luck!
Click to expand...
Click to collapse
it's thing from Samsung, if users flash the custom rom, the phone will show how much custom ROM was flashed, it can be consulted in warranty that the phone has already flashed and the warranty will be voided. but there does exist methods to do reset flash counter, but I guess only Samsung phones do have it.
but what happens if I have everything custom and then flash the normal KDZ like 20g baseband ? Will be bricked ? and can be unbricked ?
the flash counter can be removed by triangle
Sent from my LG-P700 using xda app-developers app
my phone has root, free bootloader and with custom ROM and CWM.
KDZ updater won't work on Windows 8.1, installed msxml and put compatibility/administrator and no luck.
is there another way to flash downgrade v10 ?
RenatoNismo said:
my phone has root, free bootloader and with custom ROM and CWM.
KDZ updater won't work on Windows 8.1, installed msxml and put compatibility/administrator and no luck.
is there another way to flash downgrade v10 ?
Click to expand...
Click to collapse
kdz working on window 8. let try again. check your drivers installed
kien_vip said:
kdz working on window 8. let try again. check your drivers installed
Click to expand...
Click to collapse
anyway, yesterday I downloaded KDZ and it worked and flashed rom my phone.
maybe I got very recent KDZ or I have update 1 of Windows 8.1
Hi everyone,
I am having issues with this phone of mine. Here is a background of it:
My phone is rooted and is running rayglobe rom. I tried updating the update that it gave me and made me stuck in bootloop.
Now I downloaded another rom, which I don't remember since this happened december 2013. after flashing, it does not boot and does not make me go to TWRP anymore. Now I tried using download mode to restore my phone. but eveytime I try to flash (using the 2 methods I saw in the thread), either it hangs at 49% or the other one does not start flashing because it says I have inconsistent dll? I downloaded a D802 stock rom and tried flashing via download mode and it says that I have different model (F380K). Now I tried downloading a dll and F380K stock rom, but won't allow me because it says that my phone is D802. But when I go to download mode it is korean and it says F380K.
I think I have flashed a korean rom before which made this incident happen, but do you have any idea how I can restore this?
Thank you all in advance.
If this was me, I would do a factory reset.
sounds like you should go back to stock firmware.
http://forum.xda-developers.com/showthread.php?t=2432476
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=xxxxxxxxxxxxxxxxxx<YOUR IMEI NO.
First check what exactly phone model in Internet Browser. Then download TOT and flash back to stock.
xaneybert said:
Hi everyone,
I am having issues with this phone of mine. Here is a background of it:
My phone is rooted and is running rayglobe rom. I tried updating the update that it gave me and made me stuck in bootloop.
Now I downloaded another rom, which I don't remember since this happened december 2013. after flashing, it does not boot and does not make me go to TWRP anymore. Now I tried using download mode to restore my phone. but eveytime I try to flash (using the 2 methods I saw in the thread), either it hangs at 49% or the other one does not start flashing because it says I have inconsistent dll? I downloaded a D802 stock rom and tried flashing via download mode and it says that I have different model (F380K). Now I tried downloading a dll and F380K stock rom, but won't allow me because it says that my phone is D802. But when I go to download mode it is korean and it says F380K.
I think I have flashed a korean rom before which made this incident happen, but do you have any idea how I can restore this?
Thank you all in advance.
Click to expand...
Click to collapse
I faced similar problem with D800. I had the correct dll and the firmware but it failed saying my phone model was different (I think its because I tried the "upgrade recovery" option on the LG PC software by selecting a different model).
My phone was passing the LG screen and stuck at android boot screen.
What I did:
Pushed a kitkat based rom for D800 to sdcard using adb on Linux (on windows adb failed to recognise the device).
Then adb reboot recovery and flashed the rom.
Then I was able to flash the factory image.
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
DarthVayda said:
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
Click to expand...
Click to collapse
If you don't mind losing your user data (back up anything you want from internal storage) just flash the MK2 full ODIN. Otherwise, there is a thread somewhere with just the MF3 recovery image and if you have root you could use an app to manually flash that (don't remember the app).
DeadlySin9 said:
If you don't mind losing your user data (back up anything you want from internal storage) just flash the MK2 full ODIN. Otherwise, there is a thread somewhere with just the MF3 recovery image and if you have root you could use an app to manually flash that (don't remember the app).
Click to expand...
Click to collapse
The app is flashify
Sent from my Nexus 5 using XDA Free mobile app
Possible to restore stock recovery?
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
I would flash in Odin the stock mf3 tar file, but out will wipe the device. All his apps and data. If you can find the mf3 recovery image file you could try to flash that in flashify, if you're rooted
Edit, found this. I didn't download the file but I'm guessing it's a .img file. You could flash that in flashify or use the dd command
Sent from my Nexus 5 using XDA Free mobile app
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
In addition to the above post from jd, the CM installer will not work on our device as our bootloader is locked. There is no way to run any AOSP based ROM once your phone is on MF3 firmware or higher.
DarthVayda said:
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
Click to expand...
Click to collapse
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
Here is the MF3 stock recovery, flash in PDA slot in Odin(AP in Odin v3.09+): https://mega.co.nz/#!klcz1B4J!BVAno0CcaJ7aXc9tHgUtpQ0vy_NF5ceh7RogLR6JBTU
muniz_ri said:
Here is the MF3 stock recovery, flash in PDA slot in Odin(AP in Odin v3.09+): https://mega.co.nz/#!klcz1B4J!BVAno0CcaJ7aXc9tHgUtpQ0vy_NF5ceh7RogLR6JBTU
Click to expand...
Click to collapse
Thanks to everyone for all the information, and thank you especially for sharing the link. I am staying with my parents short-term in a very rural area with awful internet and I was dreading downloading the 2+GB stock firmware file just to get recovery back. This is perfect. Thanks again!
Hey folks. I'm finding a lot of threads from 2 years ago and unfortunately they aren't much help with my device. I've inherited this phone, and my goal is to upgrade to CM12. Unfortunately I'm dealing with AT&T's locked bootloader and other issues.
I'm currently on Android 4.4.4, Baseband I337UCUFNJ4. I've managed to get root access using the Odin method of flashing NC1 then back to NJ4, root is working., but I've been unable to flash an updated Recovery. I've tried everything except for the Safestrap method, which last I read wouldn't work for installing Cyanogenmod. Using Odin, I've tried to flash CWM Recovery after converting the .img to a .tar.md5 (Odin failed to transfer this), I've tried using ROM Manager to install Recovery (claimed to work, but actually did nothing), then also used Flashify and Rashr to flash, which seemed to get further, but upon reboot the phone gave an error about software not authorized by AT&T.
I've done way too much googling this weekend and trying all sorts of things that haven't worked, from all sorts of threads from 2013 and 2014, does anyone have a reliable method that works if I'm already on 4.4.4, or am I still out of luck with this device? There is no SIM in the phone right now, but I may want to use it as a phone later if I can upgrade to CM12.
You're pretty much stuck. Only ROMs you can flash are AT&T official stock ROMs for the S4, or ROMs that are specifically safestrap-compatible. No other recovery will work, either.
That being said, if you're interested in lollipop, there's a stock, deodexed lollipop ROM for our phone that is safestrap-compatible on here called Goldeneye v53 that I enjoy.
Sent from my SGH-I337 using Tapatalk
I'm in the same situation as you, I ended up using safestrap with Pure Nexus http://forum.xda-developers.com/galaxy-s4-att/development/rom-google-edition-s4-t2837239
Closest I could get to a desirable phone without original Samsung FW. Good luck
Hmmm. What I'm wondering at this point is how does the bootloader get onto the device originally? Can't a working bootloader from another model S4 be flashed in place of the AT&T one?
I would imagine that there must be some software that can be used to fully wipe the phone, repartition the memory, write a new bootloader, etc. If a phone were hard bricked, it would seem that there would be a way that Samsung or some carrier can use to get the phone working again.
I have been trying to upgrade my 4.4.2 s4 I337 to 6.0 marshmellow and am having many problems. Also I am EXTREMELY new to anything android or flashing or anything like this at all, I learned everything I know just today.
I rooted my phone using the towelroot method because it was the easiest for my phone. I am also using safestrap recovery because I think my phone is bootloader locked? I was having a lot of problems trying to install twrp so I just assumed it was that. I'm using usb debugging and I am using the 6.0 pico gapps.
I have tried multiple roms using safestrap and making sure that the rom is specifically for my phone, at&t and I337 but each time the rom shows it was successful and I reboot it goes to recovery booting and says I don't have an OS and I have to recover back to stock firmware using odin, beccause I did a full wipe before each install of the roms.
If there is any other info I might have missed or have anything to help me I would greatly appreciated it, and again I basically have no idea what I am doing and am just going off of trial and error and googling what every term means. Thank you
Edit: My bootloader is NB1 if that matters also.
Edit: Doing a little more searching is it even possible for me to get 6.0 with my phone?
The bootloader on your phone is locked and cannot run any custom ROMs unless it is a rom that is based on a stock Samsung ROM; therefore, a 6.0 ROM or higher is not possible. Also, Lineage, RR, etc. is not possible.
audit13 said:
The bootloader on your phone is locked and cannot run any custom ROMs unless it is a rom that is based on a stock Samsung ROM; therefore, a 6.0 ROM or higher is not possible. Also, Lineage, RR, etc. is not possible.
Click to expand...
Click to collapse
Thank you for the reply! After a lot more researching and doing very stupid stuff (it was all for fun and learning mostly anyway) I did brick my phone saying firmware upgrade encountered an issue I can only get to download mode I tried flashing the original firmware I had using the stock 4.4 nb1 file but that is also now failing in odin, do you have any suggestions that could work?
Edit: I tried flashing to mk2 and thats how it bricked, but shouldn't I be able to go back to my stock firmware even if I bricked my phone like this? Both the towelrootable stock nb1 4.4 and the normal stock nb1 4.4 isnt working when I try to flash them in odin
You should flash the same or newer ROM to the phone. Even though the phone says it encountered an error, you can still flash the phone with Odin with this message in the screen.
Hopefully, this thread will help: https://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
audit13 said:
You should flash the same or newer ROM to the phone. Even though the phone says it encountered an error, you can still flash the phone with Odin with this message in the screen.
Hopefully, this thread will help: https://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
Click to expand...
Click to collapse
I'm probably jinxing it by typing while its still working but I switched my usb cable and so far it hasn't failed when before it would fail immediatly, thank you for all the help!
Only the MDL bootloader can run non touchwiz ROMs. All other bootloaders can only run touch wiz based ROMs.