Develop Bugs

[REQUEST] AT&T LG K20 (LG-M255) root method

This is my 4th LG phone but this is giving me problems even unlocking the bootloader. Any help would be appreciated.

Is this of any help?
https://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-k20-plus-t3616248

Professor Woland said:
Is this of any help?
https://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-k20-plus-t3616248
Click to expand...
Click to collapse
I wish. At&t has the bootloader locked down. All the other steps will probably work. Twrp would have to be built for M255. Thanks for the response.

So, you don't have "allow device to be OEM unlocked" option in developer options?

Professor Woland said:
So, you don't have "allow device to be OEM unlocked" option in developer options?
Click to expand...
Click to collapse
I do. Tried enabling, but still trying to get a grip on it.
Update: still can't enter fastboot mode. It just reboots like normal.

Can't I run the oem unlock command while in download mode?

mikefeFe said:
Can't I run the oem unlock command while in download mode?
Click to expand...
Click to collapse
No.

pvineeth97 said:
No.
Click to expand...
Click to collapse
Any way you know to unlock bootloader?

mikefeFe said:
Any way you know to unlock bootloader?
Click to expand...
Click to collapse
Maybe bootloader patching might work. Will look into it later.

pvineeth97 said:
Maybe bootloader patching might work. Will look into it later.
Click to expand...
Click to collapse
I appreciate your help. If you need anything from my phone, just let me know.

Did you ever have any success unlocking the phone?
I am trying to do the same thing and running into the same problems.

please help us!
---------- Post added at 01:55 PM ---------- Previous post was at 01:51 PM ----------
hope someone with a kind hearted intellectual brain will make this happen ? please help us damn it

jamers14 said:
Did you ever have any success unlocking the phone?
I am trying to do the same thing and running into the same problems.
Click to expand...
Click to collapse
Nothing yet. I am waiting to hear something from @pvineeth97 on the issue. I'll contact him and see where we stand. ?

mikefeFe said:
Nothing yet. I am waiting to hear something from @pvineeth97 on the issue. I'll contact him and see where we stand.
Click to expand...
Click to collapse
You guys have Android 7.0?

pvineeth97 said:
You guys have Android 7.0?
Click to expand...
Click to collapse
Yep & thank you MikeFefe!

Did anyone ever find a solution to this?

diazi said:
Did anyone ever find a solution to this?
Click to expand...
Click to collapse
Not as of yet. Sorry.

Hey all, just got this phone, I had originally "done some research" when I was at the att store, and found root instructions for the lg k20 PLUS (missed that plus part). So I bought the phone and now im finding out there's currently no root method, which means, as usual, I have to at least try. I warn you, I'm no fulltime dev, so don't get too excited, im the kind of guy that still needs plenty of help with this stuff, but I'm setting up a dev environment and digging in.
My question right now is, has anyone been able to access the bootloader? I read thru the k20plus root topic a bit and they say to use
#adb reboot bootloader#
or hold VOLDOWN and plug usb while powered off.
Nothing seems to bring me to a bootloader.
#adb reboot bootloader#
reboots the device and I assume it tries to boot the bootloader and fails, because windows chirps as if it's been disconnected, then my device proceeds to boot up normally.
Holding VOLDOWN and plugging the usb makes the phone show a splash screen momentarily and then switch to the powered off charging screen.
Has anybody been able to access the bootloader?
-BMFC

Still waiting here too. ??

What u mean with "bootloader" are fastboot.
To get into download-mode hold Vol+ & plug-in usb
Fastboot may for u arivable but u have to wipe ur recovery partition first.
Then reboot into recovery...but wait !
It's look like freeze..plug-in usb and hit on ur PC "fastboot device"
Welcome !

Help [hardbricked device] urgent need of help asap

Ok so i was just rooting when my phone decides to die during so commands in adb. :crying:
Now i cant turn on the phone or boot into fastboot or bootloader. everytime i plug it in the charging light just flashes. Also my computer recognises the device as qualcomm hs-usb qdloader 9008 . ive read around the internet and ive found two methods. blank flash and qfil. issue is those tutorials were made for the moto g5 plus. I have searched around the internet and im beginnign to lose hope now. Can someone tell me how to fix this or give me the right blankflash version.
much appreciated

Im sorry that i cant post a useful reply for your problem that you cant even boot into fastboot / hardbricked phone.
The following link is for all those that are stuck in fastboot mode / boot loop.
This post says its for indian version, but i have EU version (1676) and it worked for me to get back my phone as it was when bought:
https://forum.xda-developers.com/g5-plus/how-to/lock-bootloader-moto-g5-plus-indian-t3638835

Kim Il said:
Im sorry that i cant post a useful reply for your problem that you cant even boot into fastboot / hardbricked phone.
The following link is for all those that are stuck in fastboot mode / boot loop.
This post says its for indian version, but i have EU version (1676) and it worked for me to get back my phone as it was when bought:
https://forum.xda-developers.com/g5-plus/how-to/lock-bootloader-moto-g5-plus-indian-t3638835
Click to expand...
Click to collapse
Thanks but unfortunately still cant access bootloader or fastboot to do so :/

rajibahmed said:
Thanks but unfortunately still cant access bootloader or fastboot to do so :/
Click to expand...
Click to collapse
if you cant access bootloader take it to a repair shop - you need specialist software and hardware to re-image your phone
how on earth did you do that - you do know to root this device its just a simple zip flashing in recovery mode - no fancy commands or anything required once you have unlocked the bootloader via the very easy to follow guide on the moto unlock bootloader website

TheFixItMan said:
if you cant access bootloader take it to a repair shop - you need specialist software and hardware to re-image your phone
how on earth did you do that - you do know to root this device its just a simple zip flashing in recovery mode - no fancy commands or anything required once you have unlocked the bootloader via the very easy to follow guide on the moto unlock bootloader website
Click to expand...
Click to collapse
Its a long story. Basically i rooted it successfully but one of my favourite apps (snapchat) wasnt letting me sign in because i was rooted. I tried everything to mkae it work. Eventually i tried to unroot sign in and reroot to make it work. At that moment something went terribly wrong idk what but now im hardbricked.

rajibahmed said:
Its a long story. Basically i rooted it successfully but one of my favourite apps (snapchat) wasnt letting me sign in because i was rooted. I tried everything to mkae it work. Eventually i tried to unroot sign in and reroot to make it work. At that moment something went terribly wrong idk what but now im hardbricked.
Click to expand...
Click to collapse
If you are using LineageOS all you had to do was just go into dev settings switch root to disable & restart the phone
If you used magisk just use the magisk uninstaller then reflash the kernel
I don't understand why you touched the bootloader partition

TheFixItMan said:
If you are using LineageOS all you had to do was just go into dev settings switch root to disable & restart the phone
If you used magisk just use the magisk uninstaller then reflash the kernel
I don't understand why you touched the bootloader partition
Click to expand...
Click to collapse
I dunno y either. Luckily I had insurance on it so now I got a new device

Although even though I'm sorted it think we need a way to fix hardbricked devices because the Moto g5plus and g4s have fixes but I haven't found any that work for Cedric devices

rajibahmed said:
Although even though I'm sorted it think we need a way to fix hardbricked devices because the Moto g5plus and g4s have fixes but I haven't found any that work for Cedric devices
Click to expand...
Click to collapse
How did u fix

infixremix said:
How did u fix
Click to expand...
Click to collapse
I had insurance so I just replaced the whole device

rajibahmed said:
I had insurance so I just replaced the whole device
Click to expand...
Click to collapse
Wtf insurance covers it ?

infixremix said:
Wtf insurance covers it ?
Click to expand...
Click to collapse
Ish. I had Argos insurance and they basically take any dead device. Plus they don't check if it's been tampered with . I just said it didn't turn on

rajibahmed said:
Ish. I had Argos insurance and they basically take any dead device. Plus they don't check if it's been tampered with . I just said it didn't turn on
Click to expand...
Click to collapse
Motorola warranty takes hardbricked dvices with locked bootlloadder?

CypherPotato said:
Motorola warranty takes hardbricked dvices with locked bootlloadder?
Click to expand...
Click to collapse
How the hell did u hradbrick ur device without an unlocked bootloader. And idk I think that after you start tampering with the os and system it kills ur warranty. You'll have to chat with someone at Motorola

Is it even possible to unbrick a locked bootloader Redmi note 5 pro in 2020?

i have literally searched everywhere and tried the methods but to no avail. There are some old methods but they dont work anymore.
i cant access recovery but i can access fastboot but since my bootloader is locked, i guess thats no use.
1. Official flash wont work because not a authorised mi account (if someone have this, please for love of god help a brother out).
2.Tried the famous anti test https://www.youtube.com/watch?v=Pf_pPCGkldI&app=desktop but stuck at "ACK count dont match" and i guess others have this issue too. Do anyone know what this error mean in first place?
service center guys is waiting to rip off money with new motherboard but there must be someone somewhere who have good knowledge about and tweak something to make it work.
tl;dr: please provide a working unbricking method for RN5pro (working in 2020)

Hey bro as u can access fastboot mode, can u unlock ur bootloader via unlock tool?

binarygod1299 said:
i have literally searched everywhere and tried the methods but to no avail. There are some old methods but they dont work anymore.
i cant access recovery but i can access fastboot but since my bootloader is locked, i guess thats no use.
1. Official flash wont work because not a authorised mi account (if someone have this, please for love of god help a brother out).
2.Tried the famous anti test
&app=desktop but stuck at "ACK count dont match" and i guess others have this issue too. Do anyone know what this error mean in first place?
service center guys is waiting to rip off money with new motherboard but there must be someone somewhere who have good knowledge about and tweak something to make it work.
tl;dr: please provide a working unbricking method for RN5pro (working in 2020)
Click to expand...
Click to collapse
Bro i also need this solution , please help me ??
---------- Post added at 09:07 AM ---------- Previous post was at 09:06 AM ----------
Sidgup1998 said:
Hey bro as u can access fastboot mode, can u unlock ur bootloader via unlock tool?
Click to expand...
Click to collapse
I can't because for this we should enable usb debugging and oem unlock from the settings , but how we can do that if mobile is stuck at mi logo ??

udaymaurya said:
Bro i also need this solution , please help me ??
---------- Post added at 09:07 AM ---------- Previous post was at 09:06 AM ----------
I can't because for this we should enable usb debugging and oem unlock from the settings , but how we can do that if mobile is stuck at mi logo ??
Click to expand...
Click to collapse
Actually i didn't do anything u mentioned to unlock my bootloader, u can give it a try

Sidgup1998 said:
Hey bro as u can access fastboot mode, can u unlock ur bootloader via unlock tool?
Click to expand...
Click to collapse
No, you cant do that. You need to set in developler settings first but since the phone is stuck, you can't do it which means you can't unlock bootloader now using miunlock. if this was possible, we wont be whacking brains in edl n stuffs.
source: i have tried it already n didnt work.

binarygod1299 said:
No, you cant do that. You need to set in developler settings first but since the phone is stuck, you can't do it which means you can't unlock bootloader now using miunlock. if this was possible, we wont be whacking brains in edl n stuffs.
source: i have tried it already n didnt work.
Click to expand...
Click to collapse
Good luck

Download latest MIUI fastboot ROM and flash it
simple.. and use anti test patch.. search on xda.
Good luck.

drnightshadow said:
Download latest MIUI fastboot ROM and flash it
simple.. and use anti test patch.. search on xda.
Good luck.
Click to expand...
Click to collapse
neither the anti test rom nor the anti test patch is working now. it used to work before. ppl getting the "ack count dnt match error" or simply other error. maybe xiaomi patched something .

binarygod1299 said:
neither the anti test rom nor the anti test patch is working now. it used to work before. ppl getting the "ack count dnt match error" or simply other error. maybe xiaomi patched something .
Click to expand...
Click to collapse
No no, if you get ack error you just need to power cycle the phone (hold power button for 20-30 sec).
Really easy just need to be patient and retry.
Trust me I done it last week on my friends phone.
Just don't give up.. take a break and try it again. I done it in 3rd try. And use patched firehouse file on original MIUI fastboot rom.
Good luck!

drnightshadow said:
No no, if you get ack error you just need to power cycle the phone (hold power button for 20-30 sec).
Really easy just need to be patient and retry.
Trust me I done it last week on my friends phone.
Just don't give up.. take a break and try it again. I done it in 3rd try. And use patched firehouse file on original MIUI fastboot rom.
Good luck!
Click to expand...
Click to collapse
may i ask which ph model did u fix?
also which version of mi flash di you use? di you open case n did test point method?

binarygod1299 said:
may i ask which ph model did u fix?
also which version of mi flash di you use? di you open case n did test point method?
Click to expand...
Click to collapse
1. It was global model
2. mi flash 2018
3. Not needed, as i could access to fastboot.

binarygod1299 said:
may i ask which ph model did u fix?
also which version of mi flash di you use? di you open case n did test point method?
Click to expand...
Click to collapse
I don't know if this help, I unlocked many Xiaomi devices and it usually takes a lot of wait time but I bought a RN5 Pro from second hand and when I tried to unlock it through Mi-Unlock Tool it did it instantly so it looks like Xiaomi don't care anymore for bothering on old devices, just in case you didn't try it previously.
Also it may help some screenshot as possible of your issue from the Mi Flash tool, I always used the Mi Flash tool Pro for unbrick purposes https://xiaomifirmware.com/downloads/miflashpro/ Have present that a device in this state is highly unresponsive so you have to try it a lot of times to get it working again changing always some things around.

Unlocked a Note 3 bricked like that back in the day using the EDL mode with MiFlash. Just a tip, don't know whether that'll work here.
Another tip: Don't buy any more Xiaomi devices.

Limetak said:
Unlocked a Note 3 bricked like that back in the day using the EDL mode with MiFlash. Just a tip, don't know whether that'll work here.
Another tip: Don't buy any more Xiaomi devices.
Click to expand...
Click to collapse
Yeahh Xiaomi's edl authentication is bull****.
Locked edl flashing (which they thought was a security measure) but they bundle miui with full of crap and data miners.

binarygod1299 said:
neither the anti test rom nor the anti test patch is working now. it used to work before. ppl getting the "ack count dnt match error" or simply other error. maybe xiaomi patched something .
Click to expand...
Click to collapse
did you manage to solve it? I am in your same condition! I can go to fastboot mode, edl but cannot flash anything neither with QFIL or MIFLASH same error ACK COUNT DONT MATCH Or Sahara Server connection! I am really desperate and disappointed!

supermike23 said:
did you manage to solve it? I am in your same condition! I can go to fastboot mode, edl but cannot flash anything neither with QFIL or MIFLASH same error ACK COUNT DONT MATCH Or Sahara Server connection! I am really desperate and disappointed!
Click to expand...
Click to collapse
Did you disconnect battery?? If not, do it and try again.
And try even with disconnect battery and try EDL.
Good luck!

drnightshadow said:
Did you disconnect battery?? If not, do it and try again.
And try even with disconnect battery and try EDL.
Good luck!
Click to expand...
Click to collapse
Yes I tried everything even miflash pro and miflash 2018, miflash 2017 and flashing old rom both global or china mode with or without the new ssd660.elf files or patchprogram etc. I tried with connected battery and no battery in EDL mode and nothing is working just error of ACK COUNT COULDN'T MATCH cannot flash anything even with QFIL di qualcomm such a shame for Xiaomi! I think EMMC is corrupted then. Can't think of any other reason!
How did you solve the issue now in 2021?
What did you do?
Was the phone only able to go to fastboot and edl mode or also recovery? Cause mine only MI LOGO, fastboot and EDL mode with locked bootloader and EDL mode only via test point with open back cover!
Thanks

ACK COUNT COULDN'T MATCH this warning is linked to a synchronization attempt between programming Computer and interface controller the data transfer rate needs to be HIGHER than normal USB serial link transfer rate it seems.

arpit.exe said:
ACK COUNT COULDN'T MATCH this warning is linked to a synchronization attempt between programming Computer and interface controller the data transfer rate needs to be HIGHER than normal USB serial link transfer rate it seems.
Click to expand...
Click to collapse
the bootloader needs to be unlocked first remember the WHYRED is an android device all android devices are based on linux kernel the flashing computer OS must have a core ADB support and linux terminal and a linux kernel to complete the job

I need help i tried flashing fastboot ROM with MIUI tool and now its stuck in bootloop also cant access bootloader

Question Blackscreen after flashing FW

hello people, I have a black screen after flashing the FW and can't get out of it.
Battery is fully charged
Pressing key combinations doesn't help.
when the mobile phone is connected to the pc, there is a brief message that a device has been connected to the pc.
please urgently for help
thx

neroes said:
Pressing key combinations doesn't help.
Click to expand...
Click to collapse
Fastboot mode not working?

NOSS8 said:
Fastboot mode not working?
Click to expand...
Click to collapse
No ... pressing VOL+down dosnt work
fastboot devices
negativ

neroes said:
No ... pressing VOL+down dosnt work
fastboot devices
negativ
Click to expand...
Click to collapse
I sent you a PM

So just a Black Screen? No Recovery or Fastboot?
You might have to flash a ROM via EDL Mode... The unfortunate thing though is that it will cost you money, unless you still have Warranty...
You said your PC briefly says that your phone got connected. In Device Manager, does it say "Qualcomm 9008" ? That would indicate that your phones' SOC detected that the Bootloader isn't working, and so, instead booted into the EDL Mode (Emergency DownLoad Mode), which is a read-only Mode inside the SOC itself.

cyanGalaxy said:
So just a Black Screen? No Recovery or Fastboot?
You might have to flash a ROM via EDL Mode... The unfortunate thing though is that it will cost you money, unless you still have Warranty...
You said your PC briefly says that your phone got connected. In Device Manager, does it say "Qualcomm 9008" ? That would indicate that your phones' SOC detected that the Bootloader isn't working, and so, instead booted into the EDL Mode (Emergency DownLoad Mode), which is a read-only Mode inside the SOC itself.
Click to expand...
Click to collapse
is now fixed, yes was in EDL mode.
it's a shame that I didn't know about the guarantee... the phone is only 6 months old... now I've paid $25 to "unlock" it

neroes said:
is now fixed, yes was in EDL mode.
it's a shame that I didn't know about the guarantee... the phone is only 6 months old... now I've paid $25 to "unlock" it
Click to expand...
Click to collapse
Sorry about that.
What did you do to make that happen? From which FW to which FW did you upgrade to?

cyanGalaxy said:
Sorry about that.
What did you do to make that happen? From which FW to which FW did you upgrade to?
Click to expand...
Click to collapse
My mistake was to listen to someone else and downgrade the firmware

neroes said:
My mistake was to listen to someone else and downgrade the firmware
Click to expand...
Click to collapse
that is weird because noting shoould happen when you change firmware.did you use twrp or adb sideload via recovery?

neroes said:
My mistake was to listen to someone else and downgrade the firmware
Click to expand...
Click to collapse
Downgrading is not a problem if the instructions are followed correctly.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
This is why it is important to give as much detail as possible when asking a question.
If you had specified that the phone was less than 6 months old, I would have directed you to the warranty as suggested by CyanGalaxie.
Currently the guarantees are under contracted by Xiaomi and the returns are very bad (loss of the phone, broken screen, long delays, etc.).
In your case you got your phone back in 15 minutes, maybe it's better that way.

So I'm satisfied that it really worked within half an hour to "unlock" my cell phone again instead of sending it in etc.
I just tried to downgrade via sideload. that led to the EDL
All in all I'm glad that my cell phone is working again ... I'm just annoyed because I've been playing around with all sorts of cell phones for over 10 years and I couldn't figure it out myself

neroes said:
So I'm satisfied that it really worked within half an hour to "unlock" my cell phone again instead of sending it in etc.
I just tried to downgrade via sideload. that led to the EDL
All in all I'm glad that my cell phone is working again ... I'm just annoyed because I've been playing around with all sorts of cell phones for over 10 years and I couldn't figure it out myself
Click to expand...
Click to collapse
The best way to downgrade is to use Miflash or the bat file (Fastboot rom)included in the rom folder to avoid ARB.
Phones have since changed, notably with dynamic and A/B partitions.

If you were trying to downgrade/upgrade the FW due to requirement/recommendation by your Custom ROM, you can simply flash the FW inside TWRP/OrangeFox.

cyanGalaxy said:
If you were trying to downgrade/upgrade the FW due to requirement/recommendation by your Custom ROM, you can simply flash the FW inside TWRP/OrangeFox.
Click to expand...
Click to collapse
This method to have the right firmware for for example an aosp rom does not always work sometimes it is necessary to flash the full rom.
For a version change on a stock rom use fastboot roms which contain all the imgs.

Yeah, stupid anti-rollback thing. Threads like these make me wish someone already unlocks the EDL flashing. I heard developers need some source code or something for it, I'm not sure. But that needs to happen ASAP.
It's totally evil to keep EDL restricted.

user0u said:
Yeah, stupid anti-rollback thing. Threads like these makes me wish someone already unlocks the EDL flashing. I heard developers need some source code or something for it, I'm not sure. But that needs to happen ASAP.
It's totally evil to keep EDL restricted.
Click to expand...
Click to collapse
For ARB okay but for EDL mode it's just a matter of security, you lose or your phone is stolen and just flash in edl mode and the phone is yours, no.
Then the guy will only be able to flash AOSP roms as he will be blocked by the Xiaomi account.
Note that this only concerns Qualcomm Socs,Mediatek are more less secure.

@NOSS8 We are modders and tinkerers here man. We were doing just fine before these restrictions. These restrictions have been added less for "security" and more to take control away from the end users anyway.

user0u said:
@NOSS8 We are modders and tinkerers here man. We were doing just fine before these restrictions. These restrictions have been added less for "security" and more to take control away from the end users anyway.
Click to expand...
Click to collapse
Not everyone is like you or me, there are thieves and crooks,otherwise we would be in a perfect world.

user0u said:
Yeah, stupid anti-rollback thing. Threads like these make me wish someone already unlocks the EDL flashing. I heard developers need some source code or something for it, I'm not sure. But that needs to happen ASAP.
It's totally evil to keep EDL restricted.
Click to expand...
Click to collapse
There are patched Firehose files (for QPST) on the internet (apparently circumvents the required Account authorisation). I can't provide a link, but you can google it.
But I'm not sure if those work, because I couldn't find one for Poco F3, and so I too had to pay 25$
It's very annoying that people buy into these pseudo-security lies we're getting fed so often (especially Apple Users). People don't realise this is not about protecting consumers, but simply for lé money. It has always been about the money.
Xiaomi locked the EDL Mode, because people kept buying their phones from China and import them to EU/USA, flash software with GMS and sell them here.
And locking EDL Mode causes more people to pay for Xiaomi Service Centres. xddd
I wish people would just have a healthy amount of criticism and not fanboy for any company, except for Valve. Valve is cool. Valve is love

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!