Go back to stock room from Rooted phone - LG G8 Questions & Answers

dear guy please kindly help me, i just bought phone in cheap price from Tao Bao china website and it was a rooted phone with android 10. i want you guy help to back to stock rom because it can't use some bank app in country.
best regard

cheachandarin said:
dear guy please kindly help me, i just bought phone in cheap price from Tao Bao china website and it was a rooted phone with android 10. i want you guy help to back to stock rom because it can't use some bank app in country.
best regard
Click to expand...
Click to collapse
But isn't the phone already on a stock rom? But that it's rooted? Or is it running an aftermarket rom like Lineage? Look in settings, software version to find out.
You can relock the boot-loader, but before trying to do that, you have to be running 100% stock, no modifications to the rom whatsoever. I've done that but have only attempted it after using lgup to flash a complete stock rom.
To re-lock it you have to use the engineering abl and qfil to flash it, then go directly to fastboot, re-lock, then use fastboot one last time to flash the original abl back.
look in the guides section to get an idea of how to do above.

AsItLies said:
But isn't the phone already on a stock rom? But that it's rooted? Or is it running an aftermarket rom like Lineage? Look in settings, software version to find out.
You can relock the boot-loader, but before trying to do that, you have to be running 100% stock, no modifications to the rom whatsoever. I've done that but have only attempted it after using lgup to flash a complete stock rom.
To re-lock it you have to use the engineering abl and qfil to flash it, then go directly to fastboot, re-lock, then use fastboot one last time to flash the original abl back.
look in the guides section to get an idea of how to do above.
Click to expand...
Click to collapse
it was stock LG android 10 but i didn't know to check it if it was modifications if you know how to check it please kindly help me out.

cheachandarin said:
it was stock LG android 10 but i didn't know to check it if it was modifications if you know how to check it please kindly help me out.
Click to expand...
Click to collapse
I don't think there's an easy way to determine that, at least not be 100% positive of it. What I would do is a factory reset first, but that doesn't guarantee everything will then be 100% stock.
If you're not comfortable trying to re-lock bl after that, then use lgup to flash the stock firmware. That would be my preferable way to do it.
There are, in the guides section, threads on how to do these things. Good luck. But lesson learned though right? Don't buy a phone with unlocked boot loader if you want to use banking apps and have no use for root. Hopefully it will turn out to be a good learning experience though.

Thank for you replying. I thoughts this Android 10 on this phone was modified, it wasn't recognized on LGUP. Next time I should avoid for rooted phone

cheachandarin said:
Thank for you replying. I thoughts this Android 10 on this phone was modified, it wasn't recognized on LGUP. Next time I should avoid for rooted phone
Click to expand...
Click to collapse
Here the photo of it

cheachandarin said:
Here the photo of it
Click to expand...
Click to collapse
Looks to me like you don't have lgup / drivers setup properly. So I'd guess you've never had lgup setup for any other lg phone before? And your error isn't because of the software on the phone, but because of the setup?
Look in the guides forum and you'll find some that show how to setup and use lgup. It's a bit complicated because different versions have different purposes, but it looks to me your device is running basic US Cellular rom, and there's really nothing you can do with root that would make that 'unrecognizable' by lgup.

Related

Roms for AT&T V495?

Are there any working ROMs or even recovery for the G Pad F 8 (V495)?
Sent from my Nexus 6 using XDA Free mobile app
Not at this moment. We need more people to be interested in such.
Fortunately, there's a recovery for the V496 (T-Mobile variant).
We need testing for the v495.
Look here.. Make sure to back up your exisiting recovery. Then flash this. If it works, make sure to reply here or at the other thread. If not, still let us know.
In the event we ever get roms, you wont be able to flash anything for a specific device that isn't v496. Atleast until someone rebuilds the recovery for your device.
In any event. I would like you to contact me so that I can walk you through a dump of all of your devices partitions, except the personal ones.
eriklion said:
Not at this moment. We need more people to be interested in such.
Fortunately, there's a recovery for the V496 (T-Mobile variant).
We need testing for the v495.
Look here.. Make sure to back up your exisiting recovery. Then flash this. If it works, make sure to reply here or at the other thread. If not, still let us know.
In the event we ever get roms, you wont be able to flash anything for a specific device that isn't v496. Atleast until someone rebuilds the recovery for your device.
In any event. I would like you to contact me so that I can walk you through a dump of all of your devices partitions, except the personal ones.
Click to expand...
Click to collapse
i have att v495 if u ever want me to try something
v495
terpin32 said:
i have att v495 if u ever want me to try something
Click to expand...
Click to collapse
i guess it is a start, as there has been no info on these tablets. i have one and really like it, but it would be nice to get rid of all the att bloatware. i have it unlocked and am using defense mobile for carrier but i cannot use it to tether or hotspot. looking forward to more info.
I have this device for US Cellular. I would really love to install CM rom on it. From my understanding the two problems are the locked bootloader that prevent us from installing a rom, and also there being no ROMs that support our version.
BossRoyce said:
I have this device for US Cellular. I would really love to install CM rom on it. From my understanding the two problems are the locked bootloader that prevent us from installing a rom, and also there being no ROMs that support our version.
Click to expand...
Click to collapse
Specifically, a locked bootloader also makes it either impossible or extremely difficult to have root, too, which of course is a prerequisite for installing anything custom.
Also to mention that you can root it with Kingroot but there is a good chance it will also brick it. I have v495 sitting here waiting for a proper KDZ.
I keep searching everyday hoping I see a KDZ pop up. Nothing as of yet. I just bought an nVidia K1 Shield to use in place of this thing for now. Maybe one day I will get it back working.
King root 4.6.2 will give you root on marshmallow but only till you reboot.. Would be happy to help out in the cause.
walk through
mpencexda said:
King root 4.6.2 will give you root on marshmallow but only till you reboot.. Would be happy to help out in the cause.
Click to expand...
Click to collapse
Can you walk me through what would be needed to get that root up? I tried it yesterday and it kept failing. I am trying to recovery data lost when a user profile was deleted. Many of those recovery apps need it and I would be eternally grateful
my device is alos bricked
badvs3vil said:
Also to mention that you can root it with Kingroot but there is a good chance it will also brick it. I have v495 sitting here waiting for a proper KDZ.
I keep searching everyday hoping I see a KDZ pop up. Nothing as of yet. I just bought an nVidia K1 Shield to use in place of this thing for now. Maybe one day I will get it back working.
Click to expand...
Click to collapse
waiting for the proper firmware for making my tablet working. If you got one, an you help me in that please
LG V495
Hello!
After unsuccessful firmware, I had the same problem as badvs3vil https://forum.xda-developers.com/showpost.php?p=67942420&postcount=29 blurred / damaged video screen.
I was flashing firmware from LG V490 using LGFlashTool2014.
As a result, immediately after the end of the firmware, stripes appeared on the tablet screen, and nothing was visible :crying:
There are sounds of charging, the tablet responds to touch.
Please help restore the tablet!
You can install LG-AK495 to fix it.
sanchezchu said:
You can install LG-AK495 to fix it.
Click to expand...
Click to collapse
How can i do this? Do you have detailed instructions?
It turned out to solve the problem with a distorted image on the screen. Here I downloaded the firmware:
LG G Pad F 8.0 UK495 Stock ROM Firmware (Flash File)
Download the official LG G Pad F 8.0 UK495 Stock ROM Firmware (Flash File) for your device. We also provide Stock ROM for other LG devices.
lgstockrom.com
LG_G_Pad_F_8.0_UK495_LGUK495_UK49520c_00_0718
After installation, the image is normal!!
So, I guess there's no custom roms for this thing, huh? That's a shame. The thing is super slow and running Android 6 with AT&T bloatware
MultiKoopa said:
So, I guess there's no custom roms for this thing, huh? That's a shame. The thing is super slow and running Android 6 with AT&T bloatware
Click to expand...
Click to collapse
Looks like it. I found this tablet sitting in my drawer and thought I'd flash some AOSP or similar custom ROM, but not happening.

help phone wont boot into recovery and system after using blankflash

so i was flashing a nougat 7.0 update on moto z play and then all of a sudden my phone wouldnt even power on the screen was all black so i decided to use blank flash. Blank flash did take me to the bootloader but even when trying to boot to recovery and system it wont work.
help plz.
Jaderalves said:
In Device Manager how is it listed? Fastboot Android S
Click to expand...
Click to collapse
what do you mean
Jaderalves said:
In Device Manager how is it listed? Fastboot Android S
Click to expand...
Click to collapse
is their any ways for me to access recovery and my device because at the moment I'm just stuck on the fast boot screen if so please tell me btw thanks for replying.
ahmed12389 said:
is their any ways for me to access recovery and my device because at the moment I'm just stuck on the fast boot screen if so please tell me btw thanks for replying.
Click to expand...
Click to collapse
Do you see the device listed in Windows?
Flashqueen said:
Do you see the device listed in Windows?
Click to expand...
Click to collapse
yes I can see it
Flashqueen said:
Do you see the device listed in Windows?
Click to expand...
Click to collapse
what do you suggest I do
ahmed12389 said:
what do you suggest I do
Click to expand...
Click to collapse
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
echo92 said:
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
Click to expand...
Click to collapse
Yes I have flashed stock firmware on my device I remember downgrading to marshmallow then updating back to nougat then my device fully shut down it was all black. After this incident, i did what you would normally do and that was to use blank flash to at least get the bootloader back, as I did get the bootloader I could not use the boot options such as recovery mode. so I am basically stuck on the bootloader and can do nothing. My device is an addison XT1635-02 and before I flashed nougat ota I had the marshmallow December security update.
echo92 said:
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
Click to expand...
Click to collapse
I also believe my device is hard bricked as I cant access boot options at all it just keeps boot looping once I try to access a boot option. also is it normal for my bootloader to say that my software status is modified because I think after you flash blank flash your software status modified. finally, I have been trying to flash stock firmware but for some reason, gpt and bootloader.img always fail to flash. Thanks for the reply I hope you can help.
echo92 said:
Have you flashed the stock ROM onto your device? What bootloader version or stock ROM build did you have before you flashed the stock 7.0 build and took the update?
Downgrading to older stock firmware and then attempting to update is generally what caused that hard brick. If you can let us know what device/territory you had, we can try to point you to the right firmware to flash.
Click to expand...
Click to collapse
this is a dumb question but do you think that it is possible to get out of a hard brick without sending it to a moto service center.
ahmed12389 said:
this is a dumb question but do you think that it is possible to get out of a hard brick without sending it to a moto service center.
Click to expand...
Click to collapse
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
ok the thing is I am certain I used the wrong blank flash zip therefore meaning that I flashed the wrong things this is probably why I'm boot looping do you have any idea how to revert the changes of blank flash so I can flash the propper blank flash. Is their even any blank flash for Moto z play anyways
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
I was flashing the July security patch stock firmware and it's giving me these errors
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
if i flash that stock frimware it takes straight to 7.1.1 is that correct
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
is blank flash universal and works for all version and models for Motorola phone or is their specific ones because if their is I might have used the wrong one
ahmed12389 said:
is blank flash universal and works for all version and models for Motorola phone or is their specific ones because if their is I might have used the wrong one
Click to expand...
Click to collapse
As far as I know, blankflashes are CPU specific, and may also be device specific, though we've had some success using a Moto Z2 play blankflash to rescue Moto Z Play devices that are hard bricked. There's some more info here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page19 and here https://forum.xda-developers.com/showpost.php?p=73474192&postcount=249
Which blank flash did you use? Also, which July security patch firmware are you flashing? sounds like your need 7.0 or 7.1.1 firmware to proceed. That firmware link would take you up to 7.1.1, yes, but I would advise not to downgrade in future.
Also, please edit your posts rather than making new replies. I understand you're wanting to get your device fixed without paying a lot of money to fix it, give us time to respond.
echo92 said:
Should be possible, there's a thread here on how to help repair your bootloader, which has a link for some updated firmware for you to try : https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page33
I would recommend confirming it's for your device. You are likely getting the errors you mentioned as the bootloader and GPT are perhaps to old for your repaired bootloader and so are not accepted. Which blank flash did you use to repair your device? I'd just like to check you've used the correct blankflash before proceeding. Also, which GPT/bootloader were you trying to flash that gave you the errors?
I think the service centre could charge you up to 70-80 % of the original cost for a new motherboard if this can't be resolved.
Click to expand...
Click to collapse
I just checked its all good i was using the right one. it appears that if you use blank flash, in general, it will modify your software status. I will flash that stock rom I just hope it would work and yes i was flashing the july marshmallow 6.0.1 update and it had no effect on my phone what so ever lets hope this 7.1.1 does. also sorry for all these replies I am in desperate need for my phone and I'm not thinking straight
ahmed12389 said:
I just checked its all good i was using the right one. it appears that if you use blank flash, in general, it will modify your software status. I will flash that stock rom I just hope it would work and yes i was flashing the july marshmallow 6.0.1 update and it had no effect on my phone what so ever lets hope this 7.1.1 does. also sorry for all these replies I am in desperate need for my phone and I'm not thinking straight
Click to expand...
Click to collapse
If your device was ever on stock Nougat (7.0 or 7.1.1), then flashing that marshmallow ROM won't likely work in repairing your bootloader. You need a firmware that is the same or newer than the latest firmware your device had. Downgrading stock firmware does not usually downgrade your bootloader, hence the corruption and need to have same or newer firmware to repair. Your bootloader would otherwise reject old firmware via preflash validation errors.
Hopefully the 7.1.1 firmware will help fix things. You will lose data however in the process of flashing your device, so hopefully you have backups.
echo92 said:
As far as I know, blankflashes are CPU specific, and may also be device specific, though we've had some success using a Moto Z2 play blankflash to rescue Moto Z Play devices that are hard bricked. There's some more info here https://forum.xda-developers.com/moto-z-play/how-to/guide-unbrick-moto-z-play-t3618492/page19 and here https://forum.xda-developers.com/showpost.php?p=73474192&postcount=249
Which blank flash did you use? Also, which July security patch firmware are you flashing? sounds like your need 7.0 or 7.1.1 firmware to proceed. That firmware link would take you up to 7.1.1, yes, but I would advise not to downgrade in future.
Also, please edit your posts rather than making new replies. I understand you're wanting to get your device fixed without paying a lot of money to fix it, give us time to respond.
Click to expand...
Click to collapse
oh my freaking god you fixed it!!! you are literraly my idol thanks to you i dont need to take it to service from now on I'm never flashing again. but thank you very much you fixed my phone you absolute legend.
ahmed12389 said:
what do you mean
Click to expand...
Click to collapse
how is it recognized by the PC in device manager?

Will my H812 have less problems on lollipop?

This phone was given to me with marshmellow and im having the issue of not being able to update google play service among other things. the other issues im having might be the effect of the google play service. i just wanted to know if its worth attempting the downgrade on lollipop
shatheone said:
This phone was given to me with marshmellow and im having the issue of not being able to update google play service among other things. the other issues im having might be the effect of the google play service. i just wanted to know if its worth attempting the downgrade on lollipop
Click to expand...
Click to collapse
Depending on the underlying issue, you may still encounter the Play Services issue on Lollipop as you have on Marshmallow.
First, see if you can work the issue out on your current system.
- Delete cache and Data on Play Services.
- reset app preferences and reset default apps in the menu in the Apps folder in Settings.
- delete your Google account and re-install it.
- use LGUP-NEW to reinstall your Marshmallow rom (H81220). Check out this site for some H812 stock roms:
https://lg-firmwares.com/lg-h812-firmwares/
scroll down to the firmwares list and install the correct stock kdz - carrier and version
You can downgrade to Lollipop (H81210) using LGUP-NEW - frankly I haven't noticed a lot of difference between them but does have the current advantage of being rootable. Some members report better battery life but you will lose some security updates.
sdembiske said:
Depending on the underlying issue, you may still encounter the Play Services issue on Lollipop as you have on Marshmallow.
First, see if you can work the issue out on your current system.
- Delete cache and Data on Play Services.
- reset app preferences and reset default apps in the menu in the Apps folder in Settings.
- delete your Google account and re-install it.
- use LGUP-NEW to reinstall your Marshmallow rom (H81220). Check out this site for some H812 stock roms:
https://lg-firmwares.com/lg-h812-firmwares/
scroll down to the firmwares list and install the correct stock kdz - carrier and version
You can downgrade to Lollipop (H81210) using LGUP-NEW - frankly I haven't noticed a lot of difference between them but does have the current advantage of being rootable. Some members report better battery life but you will lose some security updates.
Click to expand...
Click to collapse
thanks for the reply, i actually did all of those things, including a factory reset. i will try to reinstall using lg up, maybe something in the stock image got corrupted? i learned that even if my phone boot loops, it wont be repaired as the serial number is out of range. so i might hold on to it until theres a good custom available
shatheone said:
thanks for the reply, i actually did all of those things, including a factory reset. i will try to reinstall using lg up, maybe something in the stock image got corrupted? i learned that even if my phone boot loops, it wont be repaired as the serial number is out of range. so i might hold on to it until theres a good custom available
Click to expand...
Click to collapse
Yes, very possible that something got corrupted. Definitely try a re-install of your stock kdz with LGUP-NEW.
If you haven't checked out steadfasterX's bootloader unlock thread, you will have to in order to install any custom rom with some assurance of success:
https://forum.xda-developers.com/g4/general/bl-unlock-unlock-bootloader-proof-t3648288
You might as well get started now as it won't be long before he publishes. You will have to install his SALT program and create a backup before proceeding to unlock your bootloader preparatory to installing any custom rom:
https://forum.xda-developers.com/g4/general/tool-salt-lg-revolution-t3717864
sdembiske said:
Yes, very possible that something got corrupted. Definitely try a re-install of your stock kdz with LGUP-NEW.
If you haven't checked out steadfasterX's bootloader unlock thread, you will have to in order to install any custom rom with some assurance of success:
https://forum.xda-developers.com/g4/general/bl-unlock-unlock-bootloader-proof-t3648288
You might as well get started now as it won't be long before he publishes. You will have to install his SALT program and create a backup before proceeding to unlock your bootloader preparatory to installing any custom rom:
https://forum.xda-developers.com/g4/general/tool-salt-lg-revolution-t3717864
Click to expand...
Click to collapse
i couldnt get LG up to recognize my phone even after taking out the battery, so ill have to find another usb cable and try that. i see two different kdzs for my software version so ill have to research the correct one. and im not planning one unlocking the bootloader until theres a better way. id sell it before risking a brick
shatheone said:
i couldnt get LG up to recognize my phone even after taking out the battery, so ill have to find another usb cable and try that. i see two different kdzs for my software version so ill have to research the correct one. and im not planning one unlocking the bootloader until theres a better way. id sell it before risking a brick
Click to expand...
Click to collapse
IF, you'd actually read steadfasterX's thread and in particular his latest update (last page on the thread, currently) ... you would realize there had already been a proof of a successful unlock of an H812. I suspect your phone has been screwed up by somebody who didn't know what they were doing in the first place. No one has done more work in this area and had more successes than steadfasterX - good luck for waiting for a better way or getting much trying to sell it - check ebay and see the prices - LOL.
sdembiske said:
IF, you'd actually read steadfasterX's thread and in particular his latest update (last page on the thread, currently) ... you would realize there had already been a proof of a successful unlock of an H812. I suspect your phone has been screwed up by somebody who didn't know what they were doing in the first place. No one has done more work in this area and had more successes than steadfasterX - good luck for waiting for a better way or getting much trying to sell it - check ebay and see the prices - LOL.
Click to expand...
Click to collapse
i didnt mean any disrespect, but the process is still in alpha state. this is my only phone currently so i dont want to risk bricking it. i have no reason for unlocking bootloader when there isnt enough rom support to justify doing so
shatheone said:
i didnt mean any disrespect, but the process is still in alpha state. this is my only phone currently so i dont want to risk bricking it. i have no reason for unlocking bootloader when there isnt enough rom support to justify doing so
Click to expand...
Click to collapse
The risk of bricking your phone has been minimized with steadfasterX's process - he has had a couple of successful unlocks of an H812 now and when he publishes it for the public, the risk will be minimized as much as it can be in any unlock case.
With respect to your phone not being recognized by LGUP-NEW. Make sure you have installed the LGMobileDriver_WHQL_Ver_4.2.0 available for download from the US LG site - the Windows driver will give you problems.
sdembiske said:
The risk of bricking your phone has been minimized with steadfasterX's process - he has had a couple of successful unlocks of an H812 now and when he publishes it for the public, the risk will be minimized as much as it can be in any unlock case.
With respect to your phone not being recognized by LGUP-NEW. Make sure you have installed the LGMobileDriver_WHQL_Ver_4.2.0 available for download from the US LG site - the Windows driver will give you problems.
Click to expand...
Click to collapse
well i wouldnt care doing it if there was more rom support, i dont see a point in unlocking at this point. if im missing a benefit of unlocking right now, enlighten me. and thats the driver i already have installed
shatheone said:
well i wouldnt care doing it if there was more rom support, i dont see a point in unlocking at this point. if im missing a benefit of unlocking right now, enlighten me. and thats the driver i already have installed
Click to expand...
Click to collapse
One benefit might be fixing your screwed up phone. Still didn't read the OP I guess as you were advised to in steadfasterX's bootloader unlock thread. Here's an idea ... before making summary judgements with little or no knowledge, perhaps you should check with the member that is sited in the "proof" for the H812 and post your questions there for the Roms he has tried. My understanding was that he was on Lineage for Nougat - the most popular downloaded custom rom for .... are you ready ... the H815/H811 - here's an idea ... why don't you check out ALL the roms that are for the H815/H811 in the Android Development section ... hmm ... really?
sdembiske said:
One benefit might be fixing your screwed up phone. Still didn't read the OP I guess as you were advised to in steadfasterX's bootloader unlock thread. Here's an idea ... before making summary judgements with little or no knowledge, perhaps you should check with the member that is sited in the "proof" for the H812 and post your questions there for the Roms he has tried. My understanding was that he was on Lineage for Nougat - the most popular downloaded custom rom for .... are you ready ... the H815/H811 - here's an idea ... why don't you check out ALL the roms that are for the H815/H811 in the Android Development section ... hmm ... really?
Click to expand...
Click to collapse
if you took 10 seconds, you would see i actually posed in that thread. and all they did was direct me to the OP which says nothing about lineageos working for h812, or that the h815/ or h811 roms work for this variant. all it says is that i can flash nougat based roms. so the thread isnt too helpful, im not sure why you think it is.
shatheone said:
i didnt mean any disrespect, but the process is still in alpha state. this is my only phone currently so i dont want to risk bricking it. i have no reason for unlocking bootloader when there isnt enough rom support to justify doing so
Click to expand...
Click to collapse
Hey man, i'm agreeing with you for most of this...
I'm also not going to risk anything until 10 H812 users have successfully unlocked bootloader and flashed a custom rom (one thats intended for h815 or h811) with steadfasterx's method. Maybe you can flash H815 custom roms once the bootloader is unlocked... but just to be safe, let's flash other stock carrier firmwares in the meantime...... in the end no matter what anyone says, its your phone at risk...
Member TheLatios381 and I were asking same question here:https://forum.xda-developers.com/g4...10-q2-2017-t3567402/post75742903#post75742903 because no answer to our question on steadfasterx's thread...

Looking to mod, but really confused

In km looking to root, install twrp and flash aftermarket roms AMD custom kernels, but am extremely confused. I already bricked one sm-g960u. Now that I have my new phone, I don't want to screw this one up and have to go back to my S5.
My replacement came fully updated to latest android 10, no OEM unlock option in developers options. Phone is a sprint locked S9 on Boost Mobile. Not sure if it helps.
Any help would be awesome. I attached some pics of system info to better help anyone guide me correctly to my desired goal (or as close as I can get).
Thanks in advance for your time and any help provided.
The~Skater~187 said:
In km looking to root, install twrp and flash aftermarket roms AMD custom kernels, but am extremely confused. I already bricked one sm-g960u. Now that I have my new phone, I don't want to screw this one up and have to go back to my S5.
My replacement came fully updated to latest android 10, no OEM unlock option in developers options. Phone is a sprint locked S9 on Boost Mobile. Not sure if it helps.
Any help would be awesome. I attached some pics of system info to better help anyone guide me correctly to my desired goal (or as close as I can get).
Thanks in advance for your time and any help provided.
Click to expand...
Click to collapse
You have a locked bootloader. If you want Roms and twrp you need a different device.
TheMadScientist said:
You have a locked bootloader. If you want Roms and twrp you need a different device.
Click to expand...
Click to collapse
I thought I had read that root and twrp was still possible?
Sent from my SM-G960U using Tapatalk
The~Skater~187 said:
I thought I had read that root and twrp was still possible?
Sent from my SM-G960U using Tapatalk
Click to expand...
Click to collapse
Root is possible on 8.0 only. No twrp. 80 % charge limit. If you look down in the snap dragon threads b section. You can find ir

Question hard/soft bricked

I tried downgrading my Moto G30 from Android 12 to Android 11 using an available stock ROM I found on the internet. At first, I faced some problems and a soft brick, but finally, I was able to flash and boot it correctly. Then, knowing that the ROM flashed was "stock," I decided to relock the bootloader, which was a mistake. After rebooting, I got the message "No valid operating system could be found. The device will not boot."
I spent the whole day trying to figure out how to get it working again. The main problem here is that I relocked the bootloader and can't get to the OS again to enable the option in developer settings to re-unlock it and flash another ROM. I tried using RSA (LMSA) to restore it, but it refuses, and I think it gets the same error that won't let me flash anything to the phone.
During my research, I found that one possible solution is to boot in EDL mode and flash everything again, but I don't want to open my phone and do weird things to get into that mode. Hopefully, there's another solution or another way to get into EDL.
If you have any information that could help me solve this, please comment.
I had the same problem with mine. The thing is, i tried to flash a blank-flash image but it wont go. I think its to early to downgrade your Moto G30, but you can try to flash the stock image in EDL Mode by opening your Motorola. Also you might need to send it to Motorola. Sorry
In the image you have the EDL Test Point you must brick.
But also you can try
fastboot reboot edl
Click to expand...
Click to collapse
or
reboot edl
Click to expand...
Click to collapse
U_ShowcaseDev said:
But also you can try
or
Click to expand...
Click to collapse
I've already tried several combinations of that command with no success.
aldoo9 said:
I've already tried several combinations of that command with no success.
Click to expand...
Click to collapse
Sorry I think your Motorola is Dead.
U_ShowcaseDev said:
I had the same problem with mine. The thing is, i tried to flash a blank-flash image but it wont go. I think its to early to downgrade your Moto G30, but you can try to flash the stock image in EDL Mode by opening your Motorola. Also you might need to send it to Motorola. Sorry
In the image you have the EDL Test Point you must brick.
Click to expand...
Click to collapse
Hello again! Do you know how to flash the stock rom in EDL mode? I've found some tutorials but the files required are not available in the stock rom files to do so.
aldoo9 said:
Hello again! Do you know how to flash the stock rom in EDL mode? I've found some tutorials but the files required are not available in the stock rom files to do so.
Click to expand...
Click to collapse
Please send me a Link.
aldoo9 said:
Hello again! Do you know how to flash the stock rom in EDL mode? I've found some tutorials but the files required are not available in the stock rom files to do so.
Click to expand...
Click to collapse
Don't you need to just blankflash it in EDL?
And yes you most likely need to open it.
For the Blankflash you need to download Lenovo Rescue and Smart Assistant (since lenovo produces moto phones). What this does it installs the correct drivers for your phone.
And the files can be found here : https://mirrors.lolinet.com/firmware/motorola/caprip/blankflash/
Good luck and as always, do your own research!
Edit: https://forum.xda-developers.com/t/hard-brick-moto-g30.4397117/page-2 this thread has more info.
KAN7A said:
Don't you need to just blankflash it in EDL?
And yes you most likely need to open it.
For the Blankflash you need to download Lenovo Rescue and Smart Assistant (since lenovo produces moto phones). What this does it installs the correct drivers for your phone.
And the files can be found here : https://mirrors.lolinet.com/firmware/motorola/caprip/blankflash/
Good luck and as always, do your own research!
Edit: https://forum.xda-developers.com/t/hard-brick-moto-g30.4397117/page-2 this thread has more info.
Click to expand...
Click to collapse
I tried one, but it doesn't work. The Bootloader keeps locked.
U_ShowcaseDev said:
I tried one, but it doesn't work. The Bootloader keeps locked.
Click to expand...
Click to collapse
Isn't the point to flash the stock ROM, not to unlock the bootloader?
Yes, you right. But how???
KAN7A said:
Isn't the point to flash the stock ROM, not to unlock the bootloader?
Click to expand...
Click to collapse
I saw, that you can flash a .xml Stock Firmware FIle. But i dont find anyone that work...
U_ShowcaseDev said:
I saw, that you can flash a .xml Stock Firmware FIle. But i dont find anyone that work...
Click to expand...
Click to collapse
I think you can flash with Lenovo Rescue and Smart Assistant or manually, the XML is to flash automatically, you can flash manually each image.
If you cant maybe there is an error along the way.
I might look into this later. I would lock my bootloader to test but i dont have a backup.
KAN7A said:
I think you can flash with Lenovo Rescue and Smart Assistant or manually, the XML is to flash automatically, you can flash manually each image.
If you cant maybe there is an error along the way.
I might look into this later. I would lock my bootloader to test but i dont have a backup.
Click to expand...
Click to collapse
That can be the end to your phone. But, if you have a test phone that would be excellent.
KAN7A said:
I think you can flash with Lenovo Rescue and Smart Assistant or manually, the XML is to flash automatically, you can flash manually each image.
If you cant maybe there is an error along the way.
I might look into this later. I would lock my bootloader to test but i dont have a backup.
Click to expand...
Click to collapse
Lenove RSA doesn't work. I tried it. When the Bootloader is unlocked it work. When the Bootloader is locked it wont work.
U_ShowcaseDev said:
Lenove RSA doesn't work. I tried it. When the Bootloader is unlocked it work. When the Bootloader is locked it wont work.
Click to expand...
Click to collapse
I dont have a test device right now so i cant test myself, anything I say might be wrong.
This might be a complete brick because of the downgrade from what I've read.
There is little info on the forum about this issue so I don't want to make wrong suggestions until i can test.
Yes, unfortunately, there is still little information about the Moto G30. But I hope that there will be more information and solutions in the future.
U_ShowcaseDev said:
Yes, unfortunately, there is still little information about the Moto G30. But I hope that there will be more information and solutions in the future.
Click to expand...
Click to collapse
Maybe you can help me with some info i am interested in.
1.You have booted into EDL using Short Pin method
2.You have used blankflash successfully
3.Then you try to flash manually and got Permission Denied?
For both Android 11 Stock ROM and Android 12 Stock Rom?
EDIT: Is the back of the phone glued? Or just clamps so you can put it back with no glue?
Since i want to test this soon hopefully.
KAN7A said:
Maybe you can help me with some info i am interested in.
1.You have booted into EDL using Short Pin method
2.You have used blankflash successfully
3.Then you try to flash manually and got Permission Denied?
For both Android 11 Stock ROM and Android 12 Stock Rom?
EDIT: Is the back of the phone glued? Or just clamps so you can put it back with no glue?
Since i want to test this soon hopefully.
Click to expand...
Click to collapse
1. Yes
2. I used a blankflash successfully.
3. Then in fastboot tried to flash the android 11 stock and after it failed the android 12 stock image. Also i tried the RSA varient. Both will not work.
The back is clicked in place. There are two stickers on the phone. Two white ones, One on the top left corner and one on the bottom of the phone.
But careful when you open the back. The screws are well screwed and the cap over the motherboard is slightly stuck. Maybe this will help you: Dissasembly Moto G30 YouTube
@U_ShowcaseDev Thank you so much! This is exactly what i wanted to know!

Categories

Resources