Related
Ok so i bought a phone from a guy on craigslist a couple months ago and everything was fine its a sprint lg g2 that was running a tmobile rom he said never had an issue with it.. today i was working on my motorcycle and i must have hit system update in my pocket :/ well i have been trying to fix this phone for about 8 hrs now and im not having much luck.. first i tried to flash a new rom but couldnt get the drivers to be recognized by any computer i tried.. so i resorted to the flash tool and thinking i had a sprint g2 i downloaded the stock sprint .tot and dll. files the flash tool thinks my phone is a d801at so i downloaded the appropriate files and flashed again and it worked flawlessly i thought now the phone just force shuts down and reboots and if you lock the screen it reboots i have tried flashing it again and again and also preforming a factory reset from the phone im lost and dont know what to do if you could lead me to water i will drink lol but im lost and dont even know where to begin please help as i need my phone
someone please help...
if the build.prop was edited to make it think it was a different phone other then the sprint lg g2, you would have to fix the build.prop then re use the flash tool and tot it back to sprint stuff. You may have to flash a zip in recovery (if you have custom recovery), to fix the build prop. Make sure you have the latest drivers installed on the computer and try different usb ports and cords as well if the drivers aren't installing.
jcwxguy said:
if the build.prop was edited to make it think it was a different phone other then the sprint lg g2, you would have to fix the build.prop then re use the flash tool and tot it back to sprint stuff. You may have to flash a zip in recovery (if you have custom recovery), to fix the build prop. Make sure you have the latest drivers installed on the computer and try different usb ports and cords as well if the drivers aren't installing.
Click to expand...
Click to collapse
I have the drivers installed now i dont really know how to edit the build prop but could probably figure it out but the problem is i dont have a custom recovery and I only have a maximum of 45 sec to root and install one lol If i press to many buttons on my phone it reboots or says error
brickedg2 said:
I have the drivers installed now i dont really know how to edit the build prop but could probably figure it out but the problem is i dont have a custom recovery and I only have a maximum of 45 sec to root and install one lol If i press to many buttons on my phone it reboots or says error
Click to expand...
Click to collapse
Post your issue on this thread. XxZombiePikachu is real helpful there. http://forum.xda-developers.com/showthread.php?t=2692223
Sent from my XDABBEB VS98024A v1.2.1 using XDA free mobile app
You had a Rom called "Justin's Rom" on it. Many people had this issue. Take your SIM card out, go back to stock using the flash tool, root with auto rec, then flash cloudystock.it works for tmobile out of the box.
http://forum.xda-developers.com/showthread.php?t=2661866
Also read my post
http://forum.xda-developers.com/showthread.php?t=2729370
Hello everyone
So, this is my problem here, I got my G4 last week, rooted it to debloat, followed the instructions I found here on XDA, and it was working as a charm.
The problem came when I wanted to change the (micro) SD card to another phone, I took the back cover off, took out the SD card, and a warning message about the SD card might be damaged came on screen.
So I turned off the G4, after I was ready to put back the SD, tried to power on the phone again and the error message appeared.
"Security Error, Auth Fail #9" and then it just won't boot.
Hope anyone can help me.
I was on stock Telcel Firmware, had rebooted the phone several times before with no issues so far.
Never mind, I just reflashed stock firmware found
here: http://devtester.ro/projects/lg-firmwares/
then followed this steps
Tutorial: http://devtester.ro/projects/lg-firmwares/install.php
So, after a clean flash, it booted again, as Iv'e had it for just one week, nothing was lost.
Hope this helps anyone else facing this strange problem.
By the way, if anyone know something about the possible cause for this malfunction, I woud really appreciate you sharing info.
Cheers!
i Have had the same problem i was woundering if you could please walk me through the steps on how you fixed yours.
I recently just bought a new LG G Stylo with MetroPCS. this is my first time being with android so i took it upon my self to root the phone and see what all i could do with it. Everything worked fine for a couple of days then i tried to reset my phone and when it tried to come back on the lg logo cane up and it said Authentication fail #9. I try to factory reset the phone but it goes back to the same screen. I can not put the phone in download mode and my computer does not detect that there is a phone there. If there is anyone who can help me please it will be greatly appreciated.
joyousfrank said:
Never mind, I just reflashed stock firmware found
here: http://devtester.ro/projects/lg-firmwares/
then followed this steps
Tutorial: http://devtester.ro/projects/lg-firmwares/install.php
So, after a clean flash, it booted again, as Iv'e had it for just one week, nothing was lost.
Hope this helps anyone else facing this strange problem.
By the way, if anyone know something about the possible cause for this malfunction, I woud really appreciate you sharing info.
Cheers!
Click to expand...
Click to collapse
How can be LG G4 H815P be rooted, have read many tutorials, but no one is for the variant "P" (Telcel).
Thanks!!!
Hello!
Well, I found out the source of the problem on "error 9".
As it happened again a couple days after posting the thread.
In my case, when I uninstalled LG apps, such as music and video apks, "error 9" would come up on next boot.
Follow the tutorials, the most important thing is to have the right version of SW to your phone.
Also, I had to download LG bridge, then a pop-up came telling that drivers for the phone should be updated, I just accepted the update and then my phone was detected on my PC .
If you encounter a problem, please provide me a little more info (with caps if possible).
Hope to help you.
Enviado desde mi LG-H815P
@joyousfrank. I've just been de-bloating my phone and managed to get a Security Error problem and was hoping to use this method to get the thing live again. Trouble is that Google is blocking the LGFlashtool download link. Any chance you have another link or could maybe upload a copy of the tool somewhere? Cheers
joyousfrank said:
Hello!
Well, I found out the source of the problem on "error 9".
As it happened again a couple days after posting the thread.
In my case, when I uninstalled LG apps, such as music and video apks, "error 9" would come up on next boot.
Follow the tutorials, the most important thing is to have the right version of SW to your phone.
Enviado desde mi LG-H815P
Click to expand...
Click to collapse
Hi, my version of the G4 is H815P too (CLARO BR), and I want to know wich tutorials you're referring to and if you encounter a method to surpass this issue when trying to remove/debloat the phone...
wadken1 said:
@joyousfrank. I've just been de-bloating my phone and managed to get a Security Error problem and was hoping to use this method to get the thing live again. Trouble is that Google is blocking the LGFlashtool download link. Any chance you have another link or could maybe upload a copy of the tool somewhere? Cheers
Click to expand...
Click to collapse
Sorry I couldn't help you, but it's great to know that you have solved your problem.
depechemodem said:
How can be LG G4 H815P be rooted, have read many tutorials, but no one is for the variant "P" (Telcel).
Thanks!!!
Click to expand...
Click to collapse
I used this thread as a guide
http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
(Follow the steps for International H815 10c Version)
This is the rooted image I used http://forum.xda-developers.com/g4/...on-root-lg-t3164765/post62251256#post62251256
After you download it just unzip it, and rename the .img file to "system.rooted.H81510c-EU"
The file must be system.rooted.H81510c-EU.img
Hope to help.
Cheers!
hralm said:
Hi, my version of the G4 is H815P too (CLARO BR), and I want to know wich tutorials you're referring to and if you encounter a method to surpass this issue when trying to remove/debloat the phone...
Click to expand...
Click to collapse
Hello!
The first thing to do, is to find the right SW foy your phone model (and carrier) as I read some problems when flashing other different than stock.
Look up here http://devtester.ro/projects/lg-firmwares/download.php there's where I found the SW for Telcel. Just input your IMEI on that page and it will give you a download link.
Then, follow this steps http://devtester.ro/projects/lg-firmwares/install.php
It's important to tell you that my phone wasn't detected by my PC until I downloaded LG Bridge as it comes with the latest drivers, so I recommend you to do this if you face the "not-detecting phone PC".
And for last, I suppose that there should be thread with a list of safe to uninstall apps (this is my first LG so not totally sure).
As there's enough room for apps on the phone, I just ended freezing annoying apps with Link2SD to avoid having the "Authentcation Error #9" problem.
Hope to help you, cheers!
FLASHGOTHOPS said:
i Have had the same problem i was woundering if you could please walk me through the steps on how you fixed yours.
I recently just bought a new LG G Stylo with MetroPCS. this is my first time being with android so i took it upon my self to root the phone and see what all i could do with it. Everything worked fine for a couple of days then i tried to reset my phone and when it tried to come back on the lg logo cane up and it said Authentication fail #9. I try to factory reset the phone but it goes back to the same screen. I can not put the phone in download mode and my computer does not detect that there is a phone there. If there is anyone who can help me please it will be greatly appreciated.
Click to expand...
Click to collapse
Hope it's not too late.
The first thing to do, is to find the right SW foy your phone model (and carrier) as I read some problems when flashing other different than stock. (This is important as I've only done this with G4, so you're going to do the search for the right SW)
You can look up here http://devtester.ro/projects/lg-firmwares/download.php there's where I found the SW for H815P (Telcel). Just input your IMEI on that page and hopely it will give you a download link.
Then, follow this steps http://devtester.ro/projects/lg-firmwares/install.php
It's important to tell you that my phone wasn't detected by my PC until I downloaded LG Bridge as it comes with the latest drivers, so I recommend you to do this if you face the "not-detecting phone PC".
Cheers!
My phone is running the BOG5 5.0.1 software and it is a retail edition.
I recieved a notification on my device prompting me that a new update is available (finally! 5.1.1!) I tap "download now", the download eventually finishes and it proceeds to install.
My phone boots into recovery, "installing update" and very shortly after I see the droid triage error and below it says "error!" and then my phone reboots. When I unlock my phone it says, "Sorry, there was a problem updating your SAMSUNG SM-N910V. No changes were made."
I looked under software update in settings and it says "software not updated to N910VVRU2BOK3" and the error code is 410.
I also notice that when I go into recovery it says "dm-verity verification failed...."
I looked in Kies to see if the update was available there, and of course it wasn't. And I can't find the ROM anywhere as of yet to flash with ODIN.
I would appreciate all of the help I can get.
Thank you.
traceestarr said:
My phone is running the BOG5 5.0.1 software and it is a retail edition.
I recieved a notification on my device prompting me that a new update is available (finally! 5.1.1!) I tap "download now", the download eventually finishes and it proceeds to install.
My phone boots into recovery, "installing update" and very shortly after I see the droid triage error and below it says "error!" and then my phone reboots. When I unlock my phone it says, "Sorry, there was a problem updating your SAMSUNG SM-N910V. No changes were made."
I looked under software update in settings and it says "software not updated to N910VVRU2BOK3" and the error code is 410.
I also notice that when I go into recovery it says "dm-verity verification failed...."
I looked in Kies to see if the update was available there, and of course it wasn't. And I can't find the ROM anywhere as of yet to flash with ODIN.
I would appreciate all of the help I can get.
Thank you.
Click to expand...
Click to collapse
I'm having the exact same issue and symptoms, have you made any progress with this? If I find a solution I'll share here too. I've tried Kies and VZW Software Upgrade Assistant, neither finds the update, but I can get it on my retail VZ Note 4, just won't successfully install.
Keiller said:
I'm having the exact same issue and symptoms, have you made any progress with this? If I find a solution I'll share here too. I've tried Kies and VZW Software Upgrade Assistant, neither finds the update, but I can get it on my retail VZ Note 4, just won't successfully install.
Click to expand...
Click to collapse
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
traceestarr said:
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
Click to expand...
Click to collapse
I have similar issue ,i don't have a update yet showing on my device so i await for it to show up. Please let us know if flashing it makes the difference.
traceestarr said:
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
Click to expand...
Click to collapse
Sounds like something worth trying, I'll watch for an update on how it goes for you. Thanks!
I have found a solution (albeit requires a full wipe, which is worth having 5.1.1 for me)
Firstly, I attempted flashing the "stock restore" file in odin and resulted in an error, I then tried the full firmware instead (mind you for BOG5, if you're having problems on your current version I'd suggest using your current build) with success, proceed with a data wipe in recovery and noticed that the "dm-verity verification failed...." message is now gone and now that bottom area of the screen has information about applying Multi-CSC.
Restart the phone, set up as normal and go straight for the software update. My phone downloaded and installed the update perfectly! For safety just boot into recovery and do a full wipe again, and there you have it!
The stock firmwares for RETAIL SM-N910V are here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
traceestarr said:
I have found a solution (albeit requires a full wipe, which is worth having 5.1.1 for me)
Firstly, I attempted flashing the "stock restore" file in odin and resulted in an error, I then tried the full firmware instead (mind you for BOG5, if you're having problems on your current version I'd suggest using your current build) with success, proceed with a data wipe in recovery and noticed that the "dm-verity verification failed...." message is now gone and now that bottom area of the screen has information about applying Multi-CSC.
Restart the phone, set up as normal and go straight for the software update. My phone downloaded and installed the update perfectly! For safety just boot into recovery and do a full wipe again, and there you have it!
The stock firmwares for RETAIL SM-N910V are here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
Click to expand...
Click to collapse
Thank you for reporting back with what worked for you. I've tried following the same steps you took, but after flashing the full BOG5 firmware and doing a data wipe and then doing basic setup on my phone, the OTA is still failing, Error Code: 404. I'll try again, but so far no success. Still stuck on the buggy 5.0.1, the version where you can't flash back to 4.4.4....
Keiller said:
Thank you for reporting back with what worked for you. I've tried following the same steps you took, but after flashing the full BOG5 firmware and doing a data wipe and then doing basic setup on my phone, the OTA is still failing, Error Code: 404. I'll try again, but so far no success. Still stuck on the buggy 5.0.1, the version where you can't flash back to 4.4.4....
Click to expand...
Click to collapse
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
traceestarr said:
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
Click to expand...
Click to collapse
You're right, I thought I had seen that message earlier in the week while trying to get the OTA for 5.1.1 to work, but I didn't write it down. Your description of symptoms matched mine so well I figured it had to be the same issue or something so similar that running through the same process would work for me too.
I may take the phone into Verizon to show them the update fail and see if they are willing to do anything for me....
Glad you got yours up and running, but I am just a little bit jealous
Keiller said:
You're right, I thought I had seen that message earlier in the week while trying to get the OTA for 5.1.1 to work, but I didn't write it down. Your description of symptoms matched mine so well I figured it had to be the same issue or something so similar that running through the same process would work for me too.
I may take the phone into Verizon to show them the update fail and see if they are willing to do anything for me....
Glad you got yours up and running, but I am just a little bit jealous
Click to expand...
Click to collapse
I've found that most times the OTA update fails prior to rebooting to install the update and I get the 404 error I reported earlier. However, when it does make it to the point of doing the OTA update after reboot, after that fails, I get the same 410 error you reported, see attached, and I also the dm-verity fail message in recovery. Then after using Odin to install BOG5, the verity fail disappears, replaced by a Multi-CSC message, I do a complete data wipe/factory reset, set up my basic google account and try the OTA, which fails every time. But once the dm-verity fail is gone, I can try doing an update from external storage, which I've tried with the BOK3 5.1.1 zip file posted here: http://forum.xda-developers.com/not...id-5-1-1-according-to-website-t3290683/page20 However, this still fails to load.
At this point I'm pretty convinced that I some other issue with my phone. I found elsewhere that someone was able to take their phone into Best Buy and have them flash the 5.1.1 update for them via Kies. That is probably my next step.
But I wanted to share what I've tried in case anyone else is experiencing the same dead end or in the off chance that someone has found a solution.
Sure would love to see the full 5.1.1 BOK3 tar.md5 sometime before Marshmallow hits, pretty sure using Odin to install the update that way would work....
traceestarr said:
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
Click to expand...
Click to collapse
The full OTA for 5.1.1 was posted and I was able to update using Odin, following the instructions on this post: http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
Just wanted to update this post with the solution which finally worked for me.
this is the error message i get when trying to flash the stock rom onto my lg g4. i bought a phone that had the google account locked out, so i figured i could get around that somehow. when i got to the part where the settings needed accessed in the vision menu, it was greyed out, so i did some more research. this led me to the lg flash tool i used today.
i went to this forum and downloaded all the items needed and installed the drivers, then put the phone into download mode and opened the tool as an administrator. i browsed to the file leaving it at cdma, diag, 33000. i hit cse flash to wipe it and it verified the phone connection. then it said connection to server reset. please try again later and made me exit. i tried again, then this time it it got to upgrading sw and went to 5%, then counted 6, 7, 8, and 9, and then said upgrade stopped due to an error. i have a log if that would help, it looks like it is having trouble extracting the file. i got the US99110c_03.kdz because that is my model of phone, but also tried an 815 in case it was a bad file. any suggestions are much appreciated.
looks like i have figured out what happened. finally, i got a tool started which gave me a thorough error message. it said the new rom was older than the one already there. now, the one dated 28 aug 15 is the newest one i can find anywhere. any ideas where i can find it?
sfzombie13 said:
looks like i have figured out what happened. finally, i got a tool started which gave me a thorough error message. it said the new rom was older than the one already there. now, the one dated 28 aug 15 is the newest one i can find anywhere. any ideas where i can find it?
Click to expand...
Click to collapse
Hey bud, did you ever figure out the issue? I'm having the same problem and can't get it working again. Same exact issue as you. https://forum.xda-developers.com/tm...bootlooped-t3654568/post73357821#post73357821
Hi
I have a Samsung Galaxy S9 (SM-G960F) Exynos, branded under Australian Optus and have been trying to load the latest Lineage Rom onto it but have ran into a multitude of issues. I'm going to list all of the things I've done and the Errors I've recieved
Developer Tools Enabled -> OEM Unlock Enabled (Forced Wipe) -> Developer Tools Enabled -> OEM Already Enabled -> USB Debugging Enabled -> ADB Tools installed and enabled (Computer trusted)
From Heimdall I tried flashing Lineages own bootloader from their website. I ended up getting the error "Failed to Receive Session End Confirmation"
My phone would also display the message "Only Official Released Binaries Are Allowed To Be Flashed"
I was also told RMM State played a part in this and if it was Prenormal, it wouldn't work. I went to check and sure enough, my phones RMM State was Prenormal
Despite this, I tried sideloading the packages anyway because I was told that just because it said that message, didn't mean it failed. Those ended up also failing, telling me the installation was aborted because of a validity error
From there, I was told to use Odin. That failed. I ended up switching to TWRPs bootloader instead and that also failed
After that I tried Flashing the Stock Android 10 Rom but that didn't solve any of the issues
I also tried downgrading to Android 8 Oreo to see if I could load everything from there but got the error SW REV CK FAIL
Dr Ketons Guide did not work as I was unable to Flash TWRP so I couldn't follow that route
I have the no Verity File downloaded but no way to apply it. Same with Magisk and Magisk Manager
Does anyone know what I can possibly do to try and get these things loaded onto my phone. I really would like to get them working as my main sim card is Vodafone so I'm unable to use it with this phone. Flashing the Stock unbranded XSA rom didn't seem to fix this issue either. The phone isn't under any contract or warranty, however I have no idea if its locked or unlocked.
Thanks
if you are in the prenormal state that means you can't modify your phone for like a week, just wait for the time. then it should work
by reading what you did, I didn't see anything wrong. it's just the prenormal thing that you have to wait for 7 days
edit: also forgot to mention if you failed to modify the phone after the prenormal state ends, you might need another 7 days to be able to modify your phone again
B1nz said:
if you are in the prenormal state that means you can't modify your phone for like a week, just wait for the time. then it should work
by reading what you did, I didn't see anything wrong. it's just the prenormal thing that you have to wait for 7 days
edit: also forgot to mention if you failed to modify the phone after the prenormal state ends, you might need another 7 days to be able to modify your phone again
Click to expand...
Click to collapse
So I waited 7 Days and its still prenormal. What should I do now. I tried flashing anyway to see if it was just a visual thing but it still failed. The phone was on for the whole 7 days.
CrashSpyro said:
So I waited 7 Days and its still prenormal. What should I do now. I tried flashing anyway to see if it was just a visual thing but it still failed. The phone was on for the whole 7 days.
Click to expand...
Click to collapse
I don't know it will work or not, have you try to flash the lastest stock firmware, do the initial first android setup (just skip everything), once you finish the setup go to download mode then try to flash the twrp through odin.
I used that method everytime I failed at flashing new rom. Hope it's also works for you, since my phone is also came from Australia
B1nz said:
I don't know it will work or not, have you try to flash the lastest stock firmware, do the initial first android setup (just skip everything), once you finish the setup go to download mode then try to flash the twrp through odin.
I used that method everytime I failed at flashing new rom. Hope it's also works for you, since my phone is also came from Australia
Click to expand...
Click to collapse
Unfortunately I have already tried that and it ended up not working