Hi everyone, I hope this is in the right place and wonder if anyone knows how to solve this.
I've been following a video on youtube to attempt to downgrade from Android 10 to Android 8 on an LG G7 (G710EM). I've got the phone in download mode, the firmware downloaded and have the LGUP_Common.dll file from the one used in the youtube video. However when I go to flash the firmware it gets to 4% and then comes up with error code 0x81000304 and then something like failed to load gpt from device.
I've tried different common dlls but none of them seem to make a difference. Not sure what else to do. The phone is not rooted nor have I unlocked the bootloader or anything like that.
Any ideas anyone has on how to get past this error in LGUP would be greatly appreciated, or if anyone knows any other way to flash without LGUP.
Thanks in advance.
Although you posted on the Q7 forums ill tell you this, LG Phones are a hell to downgrade. I did my Q7 a few years back. I tried probably 10 different DLLs and i found some modified software that did not even have english language. Just out of morbid curiosity ill try to find the software but my advice is that just when you think you did everything you could, keep searching for another way.
Related
Hey guy's,
Hopefully This is in the right place. Please assist in anyway you possibly can. This phone is not a brick, but it might aswell be. I have tried literally every kind of reset unbrick guide I can find for the past 2 months, and nothing works.
From what I can tell it is a driver issue, but even installing the meta mediatek preloader, and drivers does not seem to work. I have tried a fresh install of windows 8.1, windows 7, and xp. nothing works. I can not install the adb drivers for this device, because the phone will not even boot into recover. Recovery is corupted or something. I do have an mtkdroidtools backup, but can not flash it with sp flash because it always gives the error "THIS IS A SECURE BASEBAND CHIP PLEASE LOAD AUTHENICATION FILE". I've worked with kirito9 which was a big help in understanding a few things, but we could not get it sorted. I will stop talking now, and post something useful.
BTW:mobile upgrade tool s does not work either. I get terminal read failure.
As of now im on windows 8.1 with drivers installed. I have posted a couple of videos to show whats going on. Hopefully they will help. I can post some logs, but I honestly dont know which ones you would want, I have a lot of them, and have tried so many things I dont know where to begin again. In the zip file there is 2 videos, and the original mtk.log.
I forgot to mention that, this all started when I wanted to root, and install a custom recovery. I believe I used the guide on here but cant remember seeing as it was a while ago. Also the phone does not vibrate at all. Like I said I have a backup, but I dont remember much about it I dont know how reliable it is, and if I read back with sp flash or not. I believe I had to right? idk. thanks in advance.
https://drive.google.com/file/d/0B_DyVUIoGhqBSXlhbkNhdVNCR1k/view?usp=sharing
Wow I cant believe nobody has run into this problem. That or you guy's are just busy which I totally understand.. I'm just really frustrated. I think I am going to try to return it to t-mobile. You gotta know when your defeated, and this is it. This phone has been a nightmare.... I just hate giving up. I broke it, and I wanted to fix it.
Anyway if this was in the wrong lace to post please let me know. thanks.
I called t-mobile, and told them it didnt work. They asked the normal questions, and agreed to replace it. The guy said they are going to check it out to verify condition. Once they play with it enough to power it on they will see the flash error.
Is this something to worry about? also, is there a way to make sure it doesnt power on? I know thats shady, I just cant afford the deductible right now seeing as i'm out of work at the moment.
TireIron431 said:
I called t-mobile, and told them it didnt work. They asked the normal questions, and agreed to replace it. The guy said they are going to check it out to verify condition. Once they play with it enough to power it on they will see the flash error.
Is this something to worry about? also, is there a way to make sure it doesnt power on? I know thats shady, I just cant afford the deductible right now seeing as i'm out of work at the moment.
Click to expand...
Click to collapse
Hey man, I cant really help with unbricking it. Mediatek chips are not my strong point but i just wanted to say logically if the recovery is corrputed and the rom is corrupted and the bootloader is not playing ball then unless the chips have a write counter/modification check then you should be okay I reckon.
Good luck though
I still have it because I wanted to at least make it boot ok, but to no avail. I got the replacement and made a good back up with mtk droid, but I still get the error.
The phone is an Identical copy of my last one, and still no go. I even tried to flash it with the new phone, I get the same error. so I guess im a monkey, and cant do it right. If it's doing the same thing with the new phone as it is with the bricked one, than its me right?
I did notice that I cant create a scatter file with the create scatter button(its greyed out) I can only make one through the firmware.info.
This is the phone info from both phones.
Hardware : MT6581
Model : ALCATEL ONE TOUCH 4037T
Build number : ALPS.KK1.MP1.V2.10
Build date UTC : 20140918-073410
Android v : 4.4.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V34.P13, 2014/09/18 15:26
Kernel v : 3.4.67 ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP Mon Sep 8 10:47:59 CST 2014
Uboot build v : ----- should be root shell
LCD Driver IC : 0-nt35512_dsi_vdo_tdt_lcm_drv
From what I have read this is actually a 6572 chip. Is this correct? I was just thinking that maybe droid tools wasn't reading it right, or backing it up right. Droid tools creats a 6582 scatter file, but my phone says 6581, and I saw 6572. Which one is it? I cant find or make a 6581, so I do not know what to do. I have tried both phones with all of the different drivers, with the different scatters, and I always get error 5000 secure baseband chip.
Hello TireIron, in these moments I am passing through the same despair that you suffered with your telephone, I have done the same steps exactly than for the ones that you passed, although with less results, not even I have been able to find the scatter of the device to use sp flash tool.I have done the same steps you passed for, although with less results, not even I have been able to find the scatter of the device to use sp flash tool.
I don't know, if at the end you could solve the problem and recovering the telephone, if so, what solution did you find? I would thank you for if you shared the solution.
Thanks from the start.
danymt87 said:
Hello TireIron, in these moments I am passing through the same despair that you suffered with your telephone, I have done the same steps exactly than for the ones that you passed, although with less results, not even I have been able to find the scatter of the device to use sp flash tool.I have done the same steps you passed for, although with less results, not even I have been able to find the scatter of the device to use sp flash tool.
I don't know, if at the end you could solve the problem and recovering the telephone, if so, what solution did you find? I would thank you for if you shared the solution.
Thanks from the start.
Click to expand...
Click to collapse
Your issue is you flashed with the secure bootloader still active, as to why your having issues flashing it back... I've been searching around for a Custom Recovery/ROM, I'll check back in if I find anything on Disabling the Secure Bootloader, as I see it your not going to be able to restore (even to STOCK) without Unlocking the Bootloader/ And/Or Reactivating it upon re-flash.... So far no luck on finding a way to disable it, but just started a couple hours ago....
Mike
UPDATE:
ok Upon more searching it appears at the moment you need an NCK BOX...
https://www.google.com/search?q=unl...-8#newwindow=1&q=disable+secure+boot+on+4037t
http://www.ebay.vn/mo-ta-san-pham-281534386171.html
Hello,
I have an LG G3 AS990 (Ntelos). I would like to root and flash a different ROM, but am having trouble finding my variant as Ntelos is a smaller carrier. Does anyone have any advice on compatibility between any other variants? Any advice would be greatly appreciated.
Thank you
I've continued to search, but haven't found anything. Just hoping someone may have some information.
Same Boat
Snakemanc6 said:
I've continued to search, but haven't found anything. Just hoping someone may have some information.
Click to expand...
Click to collapse
I've been researching this as well. You could try finding the beta version of CM for Sprint's LS990. I would try it just for the fun of it, but I'm nervous that I don't have the stock rom for AS990 to revert back to. I have my system backed up, but I'm not comfortable enough to rely on that to save my phone if I brick it trying to install CM.
Bump. I have the same problem here, except that mine got pushed an OTA patch that prevents stump and others. So far no firmware I have found is compatible with this device to even downgrade in order to root in the first place. If anyone has succeeded with as990 NTelos please help.
Bumping the necro in hopes of support. XD my software says as99020a but the writing on the back under the cover says us990... So I'm not sure what I'm supposed to do especially since I can't even find a place to download the firmware for manual updates.. Etc. :-[ Damn ntelos
AS990 Recovery?
Has anyone found a recovery that works with the AS990?
I have an option
I've posted a way to use TWRP and ROMs for the LS990 on the LG G3 subreddit, I need 10 helpful posts before I can post it here because I have a few xda posts and downloads linked.
AS990 experience
Hi all,
I have tried different roms on my as990 (Carolina West Wireless) by using the method on reddit (HERE) and everything works just a few things to keep in mind
To get your sim to work on a custom rom you may need to change the build.prop ro.build.target_operator=, and ro.afwdata.LGfeatureset=
Take note of these settings before you try to reflash the phone. If you change one, change both if applicable.
Remember to backup your old build.prop
Backup all apns before you start using method found (HERE)
Backup build.prop
Oh and did I mention backup build.prop
The restore files can be found (HERE) and use the guide found (HERE) replacing the files mentioned with the ones in the post. If you use this method to restore you phone, the build.prop from the reddit post will not work so use the old build.prop that I'm sure by now you have backed up or you will have to get the custom .dll file elsewhere to restore.
For all who have taken the ota update, the restore method works for that too
Your carrier files are automatically restored if you use the firmware in the above post. That is to say they were for me but if anyone else test this
no guarantees but it did work flawlessly for me.
Also I am currently working on a recovery for AS990 if anyone has any ideas feel free to chime in
A couple of side notes
The method by tybskinner may also work if you flash to US990 as well, but I have not tried this yet. To do so you would need the custom .dll or the build.prop for US990
Users have reported that SIM unlock is possible by changing the the build.prop ro.build.target_operator= to global or open however I have not tried this yet
If anyone has a method to change the PRL on the device please let me know I have tried several options but no method I have tried will allow the PRL to stick
P.S. not trying to steal your thunder tybskinner just making it easier for people to find the links
Thanks for the info guys. At this point I'm having issues just trying to root the thing. Lost root with Lollipop, and for some reason I cant seem to regain it. Oh well. The price you often pay for having a smaller carrier (I actually work for nTelos, so its my work provided device).
Thanks again. I hope you guys are able to get yours setup the way you like. :good:
Snakemanc6 said:
Thanks for the info guys. At this point I'm having issues just trying to root the thing. Lost root with Lollipop, and for some reason I cant seem to regain it. Oh well. The price you often pay for having a smaller carrier (I actually work for nTelos, so its my work provided device).
Thanks again. I hope you guys are able to get yours setup the way you like. :good:
Click to expand...
Click to collapse
Currently there is no root method for the AS990 device on the newest ROM however if you follow the guide posted you can downgrade to the previous version and go from there.
Have a look here...I found a way around the whole super secure as990 crap
http://forum.xda-developers.com/lg-g3/help/how-to-as990-custom-recovery-roms-t3216133
It may seem like a bit much but it works like a champ!
HI
bobo040 said:
bump. I have the same problem here, except that mine got pushed an ota patch that prevents stump and others. So far no firmware i have found is compatible with this device to even downgrade in order to root in the first place. If anyone has succeeded with as990 ntelos please help.
Click to expand...
Click to collapse
you need to download iroot on your computer then connect your phone on the portable usb outlet make shure your phone is debbugged then open iroot it will read your phone wait wor a while and you are golden
yorimoto1987 said:
you need to download iroot on your computer then connect your phone on the portable usb outlet make shure your phone is debbugged then open iroot it will read your phone wait wor a while and you are golden
Click to expand...
Click to collapse
You can still use the method in this post to downgrade.
hi need help
thjubeck said:
Hi all,
I have tried different roms on my as990 (Carolina West Wireless) by using the method on reddit (HERE) and everything works just a few things to keep in mind
To get your sim to work on a custom rom you may need to change the build.prop ro.build.target_operator=, and ro.afwdata.LGfeatureset=
Take note of these settings before you try to reflash the phone. If you change one, change both if applicable.
Remember to backup your old build.prop
Backup all apns before you start using method found (HERE)
Backup build.prop
Oh and did I mention backup build.prop
The restore files can be found (HERE) and use the guide found (HERE) replacing the files mentioned with the ones in the post. If you use this method to restore you phone, the build.prop from the reddit post will not work so use the old build.prop that I'm sure by now you have backed up or you will have to get the custom .dll file elsewhere to restore.
For all who have taken the ota update, the restore method works for that too
Your carrier files are automatically restored if you use the firmware in the above post. That is to say they were for me but if anyone else test this
no guarantees but it did work flawlessly for me.
Also I am currently working on a recovery for AS990 if anyone has any ideas feel free to chime in
A couple of side notes
The method by tybskinner may also work if you flash to US990 as well, but I have not tried this yet. To do so you would need the custom .dll or the build.prop for US990
Users have reported that SIM unlock is possible by changing the the build.prop ro.build.target_operator= to global or open however I have not tried this yet
If anyone has a method to change the PRL on the device please let me know I have tried several options but no method I have tried will allow the PRL to stick
P.S. not trying to steal your thunder tybskinner just making it easier for people to find the links
Click to expand...
Click to collapse
Iam actually stuck in the in blue screen and a red number 2 factory status everytime i turn on my phone it says miniOS icant actually find any stock firmware for my lg g3 as990 it really does sucks doe becouse i had a lot of stuff in my phone that really needed but if you can help i will be really regretful ive been trying for a weak now
yorimoto1987 said:
Iam actually stuck in the in blue screen and a red number 2 factory status everytime i turn on my phone it says miniOS icant actually find any stock firmware for my lg g3 as990 it really does sucks doe becouse i had a lot of stuff in my phone that really needed but if you can help i will be really regretful ive been trying for a weak now
Click to expand...
Click to collapse
You need to hold the power button and press normal boot
The as990 stock rom is http://forum.xda-developers.com/lg-g3/general/lg-g3-as990-firmware-as99010a-t3183928
Hi,
I am pretty much a complete novice with this rooting and unrooting business but I decided to do a spot of research to try and gain a certain level of understanding before jumping on XDA.
I have recently brought a LG G4 and updated it to 6.0 Marshmallow through the LG Bridge and seems to be working fine.
However after doing some digging around I would like to unroot the phone install Xposed to have the capability to install some decent modules.
From what I understand though if anything goes wrong you would require the correct KDZ file to revert the phone back to stock, this is wherein my problem lies as I cant find the correct file.
I have looked at some of the links provided within certain KDZ tutorials on xda but without any success. I believe I can use another file in times of need but I would like the correct carrier KDZ encase of a warranty claim.
Does anyone have an idea or maybe can suggest other sites?
The strange thing is though after watching a video tutorial on how to unroot the guy goes to ([devtester.ro/projects/lg-firmwares/) and searches for his required file but when on the website I can clearly see the file I need is there but I don't seem to be able to find it when I search. I will say though that the video is old (last summer) but does anyone know if the files are deleted and added regularly on there?
Phone - LG-H815
KDZ Required - VDF (UK)
Any help would be much appreciated
Ross
Yes, I screwed up. Here's what happened:
>New Razr 5g aquired
>Rooted it first thing with magisk (TWRP was just temporarily booted iirc, not installed)
>No customROM, no other system modifications
>Used it only for a few weeks to play around, no magisk modules or mods installed (root was used pretty much just for AFWall+)
>Decided to sell it again (though the device itself is epic, android just isn't my thing if no real root is available)
>Reset the device through android settings
>In order to get rid of message at boot, re-locked the bootloader with normal single fastboot command
And that's basically it. Instead of Booting it now just displays "No operating system found". There also seems to be no recovery installed anymore.
I've tried everything google/XDA offered (not much, sadly). I've downloaded the stockROM firmware aswell (couldn't find one with the exact same build date but one shortly after and shortly before for the same model and channel/region/etc. - both didn't work, permission error due to locked bootloader).
The only thing I found that might help is EDL mode. I've tried forcing it (https://forum.xda-developers.com/t/...nbrick-your-moto.3042687/page-8#post-84347359) and everything else I could find, but no success.
I would very very very much appreciate any help. (P.S.: Should I try contacting Motorola? I bought the device from a private party so no going to the store option)
@sd_shadow mentioned an "EDL cable" in a thread. Googling brought me here: https://android.stackexchange.com/questions/221973/enter-edl-mode-in-motorola-devices
Does the method from the answer there really work, and is it worth a try? Anything else I need to be aware of before trying it?
Edit: Looking around a bit more about EDL, it seems I need special drivers. If anyone could hint me in that direction that'd be nice. Unless there's a better method, of course. I'm currently on Linux but I fear I might have to setup a Windows machine for this in order to install neccessary drivers/tools..
techHatesMe said:
@sd_shadow mentioned an "EDL cable" in a thread. Googling brought me here: https://android.stackexchange.com/questions/221973/enter-edl-mode-in-motorola-devices
Does the method from the answer there really work, and is it worth a try? Anything else I need to be aware of before trying it?
Edit: Looking around a bit more about EDL, it seems I need special drivers. If anyone could hint me in that direction that'd be nice. Unless there's a better method, of course. I'm currently on Linux but I fear I might have to setup a Windows machine for this in order to install neccessary drivers/tools..
Click to expand...
Click to collapse
Give this a try.This link has the mobile driver,and the firmware needed to recover it.
How to unbrick Motorola Razr 5G (Smith) 9008 EDL - ROM-Provider
step by step guide to unbrick Motorola Razr 5G by using the QCOM 9008 EDL Mod, tested method to fix hang on logo, bootloop, software bug
romprovider.com
techHatesMe said:
@sd_shadow mentioned an "EDL cable" in a thread. Googling brought me here: https://android.stackexchange.com/questions/221973/enter-edl-mode-in-motorola-devices
Does the method from the answer there really work, and is it worth a try? Anything else I need to be aware of before trying it?
Edit: Looking around a bit more about EDL, it seems I need special drivers. If anyone could hint me in that direction that'd be nice. Unless there's a better method, of course. I'm currently on Linux but I fear I might have to setup a Windows machine for this in order to install neccessary drivers/tools..
Click to expand...
Click to collapse
How did you go with this?
I have the same problem what happens??
Hello!
I'm hearing that LG G7 T-Mobile version is apparently unrootable. Is this true?
If so, is there any way I can use LG update software (like LGUP or that other one) on PC to flash the global version?
I came across a YouTube video of a guy doing just that. Has anyone done this before? Was it successful? Failure?
I would really appreciate some help on this. I don't want to brick my phone by doing something idiotic simply cz I saw someone doing it on YouTube.
Thank you.
Almost having the same issue. I just want to flash any ROM instead of T-Mobile's. The CPU's architecture apparently is the same as every other variation, so there's hope.
I just wanted to add my voice here, hoping for a capable hand's help.