Related
Hello! I have a problem which I don't know how to fix, so I need some help! I'm running stock android 4.4 (20a) and have flashed CWM through Flashify, but every time I try to boot into recovery, I get this message:
"Secure booting error
Error: Boot Certification Verify!"
Recovery worked in android 4.2 (11g), but I messed my phone up, and flashed the latest .kdz-file for my phone. It was after that the recovery-problem appeard.
I've read some places about people with D802 who has this problem, but the fixes they've got only works for D802 and D800. So, how can I fix my F320S? I guess there are more people with the korean version who has stumbled upon this problem, so if you got a fix, please post it!
Excuse my typos if there are any!
Thank you!
LG G2 F320S
Put phone in download mode, and flash the stock KDZ.
If you cannot do this, then you are hard bricked. I had an LG Optimus G which I got a Secure Boot Error after flashing a compatible ROM using TWRP, and although it could get into download mode, it would never be seen as a COM Port in the computer again to it couldn't be seen by the Flash Tools software to restore KDZ.
But it is a stock image I've flashed... What causes the problem!?
Edit: I tried to put it in Download-mode, but the secure-boot error apeard there too... But the phone can't be bricked, as it's booting to Android and everything works...
Would this fix it if the developer made a version based on my aboot?
http://forum.xda-developers.com/showthread.php?t=2500441
Edit no.2: I pressed the wrong button-combination, so yes, I was able to access Download-mode, and it works like a charm!
Send with my LG G2 F320S!
Secure Boot Error D802
2minuutes said:
But it is a stock image I've flashed... What causes the problem!?
Edit: I tried to put it in Download-mode, but the secure-boot error apeard there too... But the phone can't be bricked, as it's booting to Android and everything works...
Would this fix it if the developer made a version based on my aboot?
http://forum.xda-developers.com/showthread.php?t=2500441
Edit no.2: I pressed the wrong button-combination, so yes, I was able to access Download-mode, and it works like a charm!
Send with my LG G2 F320S!
Click to expand...
Click to collapse
Did you ever fix this, and how? I just stumbled on to the same problem the same way. I've got a D802 international. Recovery is corrupted with the same error as yours. That was nonsense about being bricked above. I hate that when people give wrong info. Any help definitely appreciated.
notanymore said:
Did you ever fix this, and how? I just stumbled on to the same problem the same way. I've got a D802 international. Recovery is corrupted with the same error as yours. That was nonsense about being bricked above. I hate that when people give wrong info. Any help definitely appreciated.
Click to expand...
Click to collapse
I did not, but I've read a place where devs managed to roll back just the bootloader and in that way access recovery!
Secure Boot Error D802
2minuutes said:
I did not, but I've read a place where devs managed to roll back just the bootloader and in that way access recovery!
Click to expand...
Click to collapse
I'm wondering what happens if I do a factory reset? Trying to get up the nerve to do it. If not then I think the next best option is to wait for 4.4.3 or higher.
notanymore said:
I'm wondering what happens if I do a factory reset? Trying to get up the nerve to do it. If not then I think the next best option is to wait for 4.4.3 or higher.
Click to expand...
Click to collapse
I don't think a reset will fix it as it's not fixing any corrupt data. The problem lays in the bootloader. It's not able to boot into the recovery installed as if it was an earlier build. It looks like this is what you are looking for to be able to install a recovery the right way. I haven't tried it yet, tho.
Secure Boot Error D802
2minuutes said:
I don't think a reset will fix it as it's not fixing any corrupt data. The problem lays in the bootloader. It's not able to boot into the recovery installed as if it was an earlier build. It looks like this is what you are looking for to be able to install a recovery the right way. I haven't tried it yet, tho.
Click to expand...
Click to collapse
Ok thanks!
Secure Boot Error D802
2minuutes said:
I don't think a reset will fix it as it's not fixing any corrupt data. The problem lays in the bootloader. It's not able to boot into the recovery installed as if it was an earlier build. It looks like this is what you are looking for to be able to install a recovery the right way. I haven't tried it yet, tho.
Click to expand...
Click to collapse
It worked! I took the plunge and it worked immediately. I've got TWRP. I already had root so did not have to use the iroot. I just ran the autorec.apk and problem solved.
Dear sir
My lg f320L and in this phone i have cloudyG2_3.3 version
i wana flash my phone F320L30D
when i flashd 2 % it stop
i have security error in my phole
please HELP
sorry my english poor
PLEASE READ EVERYTHING FOR BETTER UNDERSTANDING
Hey fellow LG Owner(s) I am writing this asking for some help. I know that majority of LG Phones use the same software and flashing tools regarding taking your phone back to stock. I currently own an LG G Flex (LS995 Sprint Variant) and I managed to soft brick my phone. I have posted this same message over at the LG G Flex Threads but so far I have gotten no one to provide me some sort of solution on how to un-brick or factory reset my phone.
The status of my phone before it got bricked was it had Root (IOROOT method), Busy-Box (by Jrummy), Build.Prop was edited to display as a Nexus 5, and boot-loader locked along with no custom recovery. If you’re wondering why my boot-loader was locked and why there wasn’t any type of custom recovery was due to the sad fact that Developers are having a hard time on cracking it.
Now to explain on how I soft bricked my phone. I was changing my font style by using a tool called ROM Toolbox (by Jrummy). I managed to change my font once and I attempted to change it a second time, since I was looking for something that displayed it wider and bolder. So as I applied install on the new font I got an automatic reboot.
The reboot consisted of the normal LG Logo display, followed by a black screen and staying as a black screen. On the upper left of my phone the notification indicator was flashing multiple colors (red, white, blue etc). This is the current state of my phone, black screen with a multicolor notification.
My attempts to fix:
- Simple reboot of the phone ((fail))
- Let the phones battery drain out then charge for a few minutes and restart ((fail))
- Managed to get into STOCK recovery and perform clean partition ((fail)
- Managed to get into STOCK recovery and apply factory reset ((fail))
- I got into some weird mode which also gave me the option to apply factory reset ((fail))
- I followed this tutorial (LG Flash Tool) on how to revert back to stock (by hyelton) ((fail))
Link to tutorial: http://forum.xda-developers.com/showthread.php?t=2644083
The tutorial by hyelton was almost successful to reverting back to stock firmware until I got to the last step (Number 6). The error that occurred by using the LG Flash Tool was when the tool attempted to flash the stock firmware it gave me a Download FAIL!! “Device Model is different“ notification (Images below). I did this tutorial at least seven times and I got no luck. Every single time that I attempted to do this I kept getting the same notification. I have now ran out if ideas on what to do.
My theory, I believe that by changing my build prop to display as a nexus 5 is the reason why I keep getting this fail notification. On the phone it-self when I put it into download mode it even displays as a Nexus 5 (Images below).
I was wondering since it’s possible to get into STOCK RECOVERY, I saw that it had an option for “ADB SIDELOAD” is it possible to push something thru ADB??? Any type of help is greatly appreciated and thanked. Please do not get upset that you see this in multiple LG threads, I am just trying to find a solution to UNBRICK this very expensive phone that I bought and I cannot afford to just use it as a paper weight. THANK YOU AND GOD BLESS
Here is a Link to all my files regarding STOCK tot,dll,lg flash tools,aboot, buildprop, lg usb drivers and adb drivers that are for my phone
Link: https://drive.google.com/folderview?id=0B1D8UNLjuTB6TWpCQ1pJME5qWk0&usp=sharing
i hope these files help anyone that are attempting to help me put my phone back to stock
Alright yall, I am almost official screwed. I purchased this phone about a month ago from Best Buy and they stated that I am out of there 15 day window so I cannot exchange or replace for the same phone. I then went to Sprint on whom I have phone insurance for and they stated that they cannot do anything and that I have to go to one of their Sprint repair stores. I went to one of the repair stores and the gentlemen that assisted me plugged my phone to his computer and immediately knew that my phone was rooted. So from there I played the dumb blonde card acting like I don’t know what he’s talking about and from there he directed me to call LG and see what they can do. So now the current status is I filed a repair request and now I am awaiting a reply from LG. Does anyone have any suggestion???
**SOLUTION** hey yall i got the solution to my problem and it was simply by downloading this universal custom .dll from
http://forum.xda-developers.com/show....php?t=2663369
and i managed to flash back to stock recovery using this guide. instead using the dll on the the guide i used the custom one.
*GUIDE BACK TO STOCK*
http://forum.xda-developers.com/show....php?t=2644083
BUMP
well not sure about g flex but for my g2 I had same problem when flashing back to stock it kept saying wrong firmware finally I found I downloaded an updated firmware and so did not match error, try downloading and flashing the firmware the phone came with but not updated, in my case my phone came with d80010d and I was trying to flash updated d80010o, downloaded d80010d and all went fine, not sure if it's the same for you I too changed my phone model in build.prop and my phone went into fastboot mode on restart. Hope it saves u too.
Sent from my LG-D800 using xda app-developers app
can you link me to where I can find the dll you are using?
XxZombiePikachu said:
can you link me to where I can find the dll you are using?
Click to expand...
Click to collapse
its the second oneeeeeeee
http://storagecow.eu/index.php?dir=Xda/LG+G+Flex/Stock/Sprint+LS995/
lingarajug said:
well not sure about g flex but for my g2 I had same problem when flashing back to stock it kept saying wrong firmware finally I found I downloaded an updated firmware and so did not match error, try downloading and flashing the firmware the phone came with but not updated, in my case my phone came with d80010d and I was trying to flash updated d80010o, downloaded d80010d and all went fine, not sure if it's the same for you I too changed my phone model in build.prop and my phone went into fastboot mode on restart. Hope it saves u too.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
thanks for your response but unfortunately there is only one firmware for the sprint flex at the current moment.
christiam.coronado said:
its the second oneeeeeeee
http://storagecow.eu/index.php?dir=Xda/LG+G+Flex/Stock/Sprint+LS995/
Click to expand...
Click to collapse
ok then try this modified dll hopefully it will work https://www.dropbox.com/s/akcn2b3skv9h4pa/LGLS995_20140116_LGFLASHv151.dll
please do so at your own risk
XxZombiePikachu said:
ok then try this modified dll hopefully it will work https://www.dropbox.com/s/akcn2b3skv9h4pa/LGLS995_20140116_LGFLASHv151.dll
please do so at your own risk
Click to expand...
Click to collapse
same results "device model is different" didnt work. Im willing to try anything. please shoot me some more of your modifications
christiam.coronado said:
same results "device model is different" didnt work. Im willing to try anything. please shoot me some more of your modifications
Click to expand...
Click to collapse
ill see what else I can try I am basically just trying to find out which are all the parts of the dll that check the device which is kind of difficult especially since yours is no longer a part of the g family ill keep looking when I finish the next one I'll let you know
XxZombiePikachu said:
ill see what else I can try I am basically just trying to find out which are all the parts of the dll that check the device which is kind of difficult especially since yours is no longer a part of the g family ill keep looking when I finish the next one I'll let you know
Click to expand...
Click to collapse
wow thanks i greatly appreciate your help. i am open to trial and error and whatever you can think of i will try.
christiam.coronado said:
wow thanks i greatly appreciate your help. i am open to trial and error and whatever you can think of i will try.
Click to expand...
Click to collapse
what did you add to your build prop to make it think it was a nexus 5?
XxZombiePikachu said:
what did you add to your build prop to make it think it was a nexus 5?
Click to expand...
Click to collapse
all that i did to the build prop was change the model to Nexus 5. luckily i have copied my original build prop to my computer. here is the ling to my google drive which i have saved my original build prop
https://drive.google.com/file/d/0B1D8UNLjuTB6UVBGZnhIaWEwNjg/edit?usp=sharing
XxZombiePikachu said:
what did you add to your build prop to make it think it was a nexus 5?
Click to expand...
Click to collapse
attached below is an image of what my original build prop looked like with its original model as ro.product.model = LG-LS995
the LG-LS995 was the part that i replaced with Nexus 5
Why not try to restore your default build prop
Sent from my LT25i using xda app-developers app
harrymason37 said:
Why not try to restore your default build prop
Sent from my LT25i using xda app-developers app
Click to expand...
Click to collapse
how remember that my bootloader is still locked and this model does not have a custom recovery. but i am able to access the stock recovery with an option to ADB SIDELOAD. I got word from a DEV stating that:
"Factory recovery won't let you adb sideload a package without a LG verified updater script so it won't work." (by XDA justinswidebody)
but if he is incorrect i wouldn't mind attempting trial and error. what do you think???
okay so I tried a different approach I grabbed a d820(nexus 5 model) dll and replaced everything inside with info from the ls995 dll hopefully this works heres the link https://www.dropbox.com/s/kh9ns4gzw3i4gq3/d820_ls995.dll
XxZombiePikachu said:
okay so I tried a different approach I grabbed a d820(nexus 5 model) dll and replaced everything inside with info from the ls995 dll hopefully this works heres the link https://www.dropbox.com/s/kh9ns4gzw3i4gq3/d820_ls995.dll
Click to expand...
Click to collapse
ok ill try it out give me a minute
XxZombiePikachu said:
okay so I tried a different approach I grabbed a d820(nexus 5 model) dll and replaced everything inside with info from the ls995 dll hopefully this works heres the link https://www.dropbox.com/s/kh9ns4gzw3i4gq3/d820_ls995.dll
Click to expand...
Click to collapse
no didnt load onto the lgflashtool. these are the notification that i got, images are below
-Failed to load factory s/w
-Failed PreviousLoad ()
christiam.coronado said:
no didnt load onto the lgflashtool. these are the notification that i got, images are below
-Failed to load factory s/w
-Failed PreviousLoad ()
Click to expand...
Click to collapse
what's the version of your flash tool
edit: after some reading to flash nexus tots you need lg flash tool 1.8
re-edit: I believe that the dll needs to be modified so that it accepts the device as a nexus 5 but once it's done flashing it needs to make the device and ls995 again, but for now it's 1am and I need to be up early later so I'll work on something later, also just some extra information on ther stuff: as for flashing the build prop if you can manage to make it into a flashable update.zip(which also places it in corresponding directory) which is also signed and you can sideload it should flash or just give an error, and another thing that could work with above method is flashing a corrupted kernel which will throw your phone into fastboot mode and with correct files and commands you can repartition the entire device to stock(this one is very dangerous/risky would not recommend it)
XxZombiePikachu said:
what's the version of your flash tool
Click to expand...
Click to collapse
Setup_LGFlashTool_1.6.01.0529
its on my drive should i downgrade??? https://drive.google.com/file/d/0B1D8UNLjuTB6ekthOGRVMWE3ejA/edit?usp=sharing
So I'm really into Android developing, I'm always flashing and installing etc, but I got a problem now.
Phone information
LG G2 D802
Rooted
TWRP Recovery 2.7.0.0
Was running 4.4.2, found a kdz file on the internet and flashed it (no regular update from my phone)
What happenedI actually did something stupid, I received an application update from the LG Download Center (or whatever it's called) on my phone and clicked on it. I was planning on flashing Android 4.4.2 again because my firmware was not stable, and I thought this update could help me.
But no, after it finished downloading, I automatically booted into recovery.
What I didSo I tried to reboot and enter my OS, but unfortunately, I was stuck in recovery.
I did everything I could, wiping (Dalvik) cache, factory reset, flashed a new rom, restored Nandroid backup, but no, every time I booted, I got back into recovery again.
I only saw 1 option left, booting into download mode and flashing a new firmware.
I found the Netherlands 16GB kdz file for Android 4.4.2 (because I had a French one first), the one I was looking for.
Looked all over the internet, and all guides pointed me to this guide.
Tried it, but I got multiple errors, one of them was that my phone was not connected while I was at 15% of the flash process.
What happenedAfter that first flashing process, I booted up, but got a Security Error. After the Security Error was showing for 5 seconds, my phone shut down. This is happening every time I try to boot up.
I couldn't access my recovery anymore, nothing. Edit: I can access my recovery right now, and I tried this, but when I boot up I get the Security Error again.
The big problem right now is the Security Error! How do I bypass that?
So can someone please help me out!
Several phones/tablets of mine bricked and I always found a way to get out of it, but not this time, unfortunately...
Have you tried this
Sent from LG-G2 D800 on AEONFLEX 4.4.2
XxZombiePikachu said:
Have you tried this
Sent from LG-G2 D800 on AEONFLEX 4.4.2
Click to expand...
Click to collapse
Yes, I actually have. Didn't mention it, but after I did that I booted and got an LG logo and below it was a text that said 'Security Error' After like 5 seconds the security error goes away and my phone shuts down. I can only enter download mode right now.
I'll edit my first post with this info.
Thanks for the help though!
Edit: I find a way to access my recovery again because at first I couldn't but I figured out that the code in the thread you linked was a bit different than the code I entered at first.
So I used the code you gave me, but now I get the Security Error again!
Hi mate, just like you i downloaded that damn OTA today and messed up my phone, but in my case was because i had totally forgotten it was rooted and had custom recovery installed :silly::silly::silly::silly:
I followed this tutorial to fix the boot secure error http://forum.xda-developers.com/showthread.php?t=2582142 and it worked like a charm except for download mode wasn't working at all.
After doing some research i found this post http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html and got download mode (apparently) working again but Windows didn't recognize it at all so i couldn't use it to flash the .kdz stock firmware.
In the end i just flashed a custom aosp rom and got my phone back to life but the download mode issue it's still there and it's bothering me quite a lot.
Any suggestion is welcome.
EDIT: Don't download the recovery from the post, instead look for the latest version (2.7.0.0) because the one posted there (2.6.3.2) might corrupt your partitions
evilruck said:
Hi mate, just like you i downloaded that damn OTA today and messed up my phone, but in my case was because i had totally forgotten it was rooted and had custom recovery installed :silly::silly::silly::silly:
I followed this tutorial to fix the boot secure error http://forum.xda-developers.com/showthread.php?t=2582142 and it worked like a charm except for download mode wasn't working at all.
After doing some research i found this post http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html and got download mode (apparently) working again but Windows didn't recognize it at all so i couldn't use it to flash the .kdz stock firmware.
In the end i just flashed a custom aosp rom and got my phone back to life but the download mode issue it's still there and it's bothering me quite a lot.
Any suggestion is welcome.
EDIT: Don't download the recovery from the post, instead look for the latest version (2.7.0.0) because the one posted there (2.6.3.2) might corrupt your partitions
Click to expand...
Click to collapse
Thanks! But does my internal storage get whiped? Will all my pictures etc. be gone?
And the first thred removes the security error right? And after that I can just boot into recovery mode (I can boot in recovery btw) and flash a new rom? Just wanted to know this so I don't go through all that trouble for nothing
Edit: You know I can enter both download and recovery mode right?
Ibrahim9999 said:
Thanks! But does my internal storage get whiped? Will all my pictures etc. be gone?
And the first thred removes the security error right? And after that I can just boot into recovery mode (I can boot in recovery btw) and flash a new rom? Just wanted to know this so I don't go through all that trouble for nothing
Edit: You know I can enter both download and recovery mode right?
Click to expand...
Click to collapse
Nope internal SD remains intact, basically what you'll be doing is pushing the right files into the system partitions and yes, in theory you should be able to flash a new rom.
Even if you can boot into recovery you should do it if you're getting that error, and after that you can just push a ROM file to flash (i'll assume you know how to do it) and btw let me know if you decide to flash a stock based rom instead of an aosp like i did.
Good luck with that :good:
evilruck said:
Nope internal SD remains intact, basically what you'll be doing is pushing the right files into the system partitions and yes, in theory you should be able to flash a new rom.
Even if you can boot into recovery you should do it if you're getting that error, and after that you can just push a ROM file to flash (i'll assume you know how to do it) and btw let me know if you decide to flash a stock based rom instead of an aosp like i did.
Good luck with that :good:
Click to expand...
Click to collapse
Thanks man! I'm probably going to save money because of you, awesome!
Ibrahim9999 said:
Thanks man! I'm probably going to save money because of you, awesome!
Click to expand...
Click to collapse
I hope so!
Let me know if you fix the thing :laugh:
evilruck said:
I hope so!
Let me know if you fix the thing :laugh:
Click to expand...
Click to collapse
I just managed to fix it! Thank you so much man!
Can someone help me plz I got flashily got CWM instead of the TWRP and got and lg update it updated and now it's stuck in recovery mode it won't go into download mode it only goes to recovery mode and my computer won't recognize my phone so if any one knows how to fix it can you plz help me out
my pc don't recognize the lg g2 in download mode!
i installed the drivers and the USB is connected but the pc don;t even say that the device is connected . and nothing in device manager at all
Perhaps you might consider sending it in to lg if you still have warranty. But I'd you don't, there are services on eBay/ Craigslist that can help you.
Sent from my LG-D800 using XDA Free mobile app
This used to be easy.
After 8 hours yesterday I think I managed to root the phone. CWM/TWRP will not install. At all, under any method. Rom manager, goo manager, I now get this stupid message that says that "an application attempted to access something unauthorized and has been blocked" over and over.
Just trying to flash CM11 rom. Guess I need to learn how to sideload or something? I physically can't get my phone to recovery mode other than the stock Android, which does not have the "flash zip from sdcard" option.
For the love of god help me. My phone stopped working around 2 pm yesterday and I seriously can't believe I'm about to be going into day 2 of this, so rather than drive myself crazy i'm going to wait for help
bump please help should be simple
Hi,
Please, don't panic! Panic is your worst enemy . First, give a good read here: http://forum.xda-developers.com/showthread.php?t=2419762. Then try again . It's very likely Knox is blocking your TWRP/CWM installation, that's why you receive this message.
All the best,
~Lord
XxLordxX said:
Hi,
Please, don't panic! Panic is your worst enemy . First, give a good read here: http://forum.xda-developers.com/showthread.php?t=2419762. Then try again . It's very likely Knox is blocking your TWRP/CWM installation, that's why you receive this message.
All the best,
~Lord
Click to expand...
Click to collapse
thanks
knox is disabled
root is gained
su is installed
rom manager and goo manager installed
when i downloaded the CM rom from goo manager and try to install it, the phone restarts in download mode and just sits there...
Damani311 said:
thanks
knox is disabled
root is gained
su is installed
rom manager and goo manager installed
when i downloaded the CM rom from goo manager and try to install it, the phone restarts in download mode and just sits there...
Click to expand...
Click to collapse
Hi,
You need to flash the recovery via Odin . After flashing the recovery via Odin you'll be able to flash the ROM normally .
All the best,
~Lord
XxLordxX said:
Hi,
You need to flash the recovery via Odin . After flashing the recovery via Odin you'll be able to flash the ROM normally .
All the best,
~Lord
Click to expand...
Click to collapse
tried flashing four different CWM tars, all are failing.
XxLordxX said:
Hi,
You need to flash the recovery via Odin . After flashing the recovery via Odin you'll be able to flash the ROM normally .
All the best,
~Lord
Click to expand...
Click to collapse
tried flashing four different CWM tars, all are failing.
also trying to flash TWRP
its just all failing on the install
Hi,
Please post your installation issue on the Galaxy S4 Help Thread there might be someone better than me to help you there. Also are you sure you're flashing the right files and using the right method? Did you try another USB Cable? Did you try another Odin version? It all can contribute to the fail.
~Lord
XxLordxX said:
Hi,
Please post your installation issue on the Galaxy S4 Help Thread there might be someone better than me to help you there. Also are you sure you're flashing the right files and using the right method? Did you try another USB Cable? Did you try another Odin version? It all can contribute to the fail.
~Lord
Click to expand...
Click to collapse
its the official samsung cable. and yes i tried others
tried other versions of odin as well
and different versions of both twrp and cwm
its crazy i tells ya xD
If it fails to flash true Odin, then you are doing something wrong.
- Different pc
- Reinstall drivers
- Different cable
- Different usb port
- Make sure kies is not running in the background
What are you running? Windows 8? Try a windows 7 pc.
Post the details of the error you are getting.
Also when the flash goes succesfull, but you still don't have a custom recovery, then uncheck auto-reboot.
can someone please link me to a guaranteed working version of a flashable recovery for odin ?
I know its a lot to ask but I've actually gone through almost that entire list you listed
tried diff cables
no kies runnning
on windows 7
drivers been installed twice
maybe i should try the other port, but in case that doesnt work can anyone just link me? sorry i've just never had this much problems with this, must be b/c of the new security knox update or w/e in oct of last year. Last June I did all this in about 15 minutes....
I had the same trouble with the knox crap yesterday, the only way I could get it rooted and/or with custom recovery was to use the Cyanogen windows installer, then when CM booted I then rebooted into recovery and installed a different rom from there. :good:
dwarfer66 said:
I had the same trouble with the knox crap yesterday, the only way I could get it rooted and/or with custom recovery was to use the Cyanogen windows installer, then when CM booted I then rebooted into recovery and installed a different rom from there. :good:
Click to expand...
Click to collapse
that's crazy
so where do i find this windows installer? i'm just trying to put CM on there so I suppose this would work
Hi i know youve already said said its officail cable but im saying try another different s4 cable. Because when i was installing recovery or anything it wouldnt let me (i thought i had original white s4 cable) but then i got my dads cable (hes gt s4) and it worked instantly. These fake cables are at large and its very very difficult to tell if its original.
Also like previous guy said using a different computer/laptop also helps i know because ive flashed my phones since day 1.
GL and plz let me know if u managed to fix it another way as its always good to try new options when others fail.
189cutter said:
Hi i know youve already said said its officail cable but im saying try another different s4 cable. Because when i was installing recovery or anything it wouldnt let me (i thought i had original white s4 cable) but then i got my dads cable (hes gt s4) and it worked instantly. These fake cables are at large and its very very difficult to tell if its original.
Also like previous guy said using a different computer/laptop also helps i know because ive flashed my phones since day 1.
GL and plz let me know if u managed to fix it another way as its always good to try new options when others fail.
Click to expand...
Click to collapse
alright it'd be awesome if someone can post a link to the files the work, for sure.
CM windows installer
CWM odin tar file
TWRP odin tar file
Damani311 said:
alright it'd be awesome if someone can post a link to the files the work, for sure.
CM windows installer
CWM odin tar file
TWRP odin tar file
Click to expand...
Click to collapse
http://www.cyanogenmod.org/ then click the start button and follow the instructions.
It will get you to download the installer (or http://dist01.slc.cyngn.com/CMInstaller.msi?t=1403660099360) the click it to run, It may download an update for itself, then it will download recovery, operating system, gapps, then start to install everything. About 300mb altogether.
That way you don't need the tar files, just search on this sight for flashable from recovery for the recovery files you want. (I use the touch versions myself).
dwarfer66 said:
http://www.cyanogenmod.org/ then click the start button and follow the instructions.
It will get you to download the installer (or http://dist01.slc.cyngn.com/CMInstaller.msi?t=1403660099360) the click it to run, It may download an update for itself, then it will download recovery, operating system, gapps, then start to install everything. About 300mb altogether.
That way you don't need the tar files, just search on this sight for flashable from recovery for the recovery files you want. (I use the touch versions myself).
Click to expand...
Click to collapse
thanks, but naturally this would be too easy
says: "not supported on your device"
a freaking S4 AT&T! what the ****?
From what I've read AT&T have locked bootloaders. Glad I have an unlocked Australian version!
Yeah so if anyone can still find a way to help me that'd be awesome. Wasted two days already and rather not be stuck with stock
Damani311 said:
Yeah so if anyone can still find a way to help me that'd be awesome. Wasted two days already and rather not be stuck with stock
Click to expand...
Click to collapse
So do you have an AT&T phone? If you do, you are in the wrong section of the forum.
I want to take a poll, and this will be for T-Mobile variants ONLY. Being that the thread has people from all different carriers posting results, i think it's rather confusing to anyone reading along trying to decide whether or not to give it a shot.
So, have you successfully rooted/TWRP'd your TMOBILE variant LGv20?
thatisandwas said:
I want to take a poll, and this will be for T-Mobile variants ONLY. Being that the thread has people from all different carriers posting results, i think it's rather confusing to anyone reading along trying to decide whether or not to give it a shot.
So, have you successfully rooted/TWRP'd your TMOBILE variant LGv20?
Click to expand...
Click to collapse
Yes I have. Full root access with working TWRP and supersu. No issues as of yet but I've not tried anything other than TB.
I got it rooted with twrp be warned though my other lg I flashed a file and now bootloop
bambam126 said:
I got it rooted with twrp be warned though my other lg I flashed a file and now bootloop
Click to expand...
Click to collapse
what file?
czerdrill said:
what file?
Click to expand...
Click to collapse
Build prop edit and google assistant..: /
bambam126 said:
Build prop edit and google assistant..: /
Click to expand...
Click to collapse
Ah ok, i thought i saw someone say earlier the google assistant thing worked for them, but they might have manually edited the build prop.
czerdrill said:
Ah ok, i thought i saw someone say earlier the google assistant thing worked for them, but they might have manually edited the build prop.
Click to expand...
Click to collapse
Yeah maybe I'm trying to get out this loop
bambam126 said:
Yeah maybe I'm trying to get out this loop
Click to expand...
Click to collapse
You're not going to get out of it without restoring your backup or manually placing the normal build prop inside recovery
jthrasher47 said:
You're not going to get out of it without restoring your backup or manually placing the normal build prop inside recovery
Click to expand...
Click to collapse
I can't restore I did a factory wipe and didnt work I'm on lg support tool but upgrade recovery says no items to fix and lgup sees phone as unknown but my non looping v20 it sees just fine
Idk what to do lg mobile support tool gives me up but says no items to fix
You did not do a backup in twrp before flashing your file? You may have to exchange your phone you should always make a backup especially with things this new
Unlocked and rooted with no problems. I flashed a systemless hosts file for ad away in twrp and everything was fine. For assistant, I manually edited the build.prop file and restarted, which worked great. I almost feel guilty as to how easy this whole process has been.
jthrasher47 said:
You did not do a backup in twrp before flashing your file? You may have to exchange your phone you should always make a backup especially with things this new
Click to expand...
Click to collapse
what can i do with that backup I cant get into twrp...
Full root,twrp,l speed... Loving it
Sent from my LG-H918 using XDA-Developers mobile app
kibmikey1 said:
Unlocked and rooted with no problems. I flashed a systemless hosts file for ad away in twrp and everything was fine. For assistant, I manually edited the build.prop file and restarted, which worked great. I almost feel guilty as to how easy this whole process has been.
Click to expand...
Click to collapse
LOL wanna make a video? I'm gonna do it tonight, i am just nervous.
AT&T Tried Yet ?
bambam126 said:
I can't restore I did a factory wipe and didnt work I'm on lg support tool but upgrade recovery says no items to fix and lgup sees phone as unknown but my non looping v20 it sees just fine
Idk what to do lg mobile support tool gives me up but says no items to fix
Click to expand...
Click to collapse
I assume the build prop edit changes the device name. Therefore lg up won't recognize it. You will need a custom .dl file with the name edited. At least that is what used to happen back in the day when I was working with these phones. There used to be a program that made it possible to edit the .dl file.
justinswidebody said:
I assume the build prop edit changes the device name. Therefore lg up won't recognize it. You will need a custom .dl file with the name edited. At least that is what used to happen back in the day when I was working with these phones. There used to be a program that made it possible to edit the .dl file.
Click to expand...
Click to collapse
LG sees it as the v20 but can't do anything cause no software updates or whatever
bambam126 said:
LG sees it as the v20 but can't do anything cause no software updates or whatever
Click to expand...
Click to collapse
Have you tried to fast boot flash the stock system img
---------- Post added at 05:36 PM ---------- Previous post was at 05:33 PM ----------
bambam126 said:
LG sees it as the v20 but can't do anything cause no software updates or whatever
Click to expand...
Click to collapse
If that doesn't work, you should be able to put the system IMG on SD card and DD command it
justinswidebody said:
Have you tried to fast boot flash the stock system img
Click to expand...
Click to collapse
What's the command I tried something it says remote command failed or something
bambam126 said:
What's the command I tried something it says remote command failed or something
Click to expand...
Click to collapse
When in fast boot type fastboot flash system then drag the image in the command prompt