Related
Hi,
I tried to upgrade my LG V30+ US998 to android Pie via TWRP but after the upgrade and system reboot the device got stuck in LG logo.
The download mode isn't working (device not being detected).
LGUP shows the device as "unknown" and adb is not detecting the device either.
I can't boot into TWRP anymore and flashing via LG flash tool 2014 fails (asks for server connection!).
I installed all the tools and LG mobile drivers on another computer and had no luck!
Do I have any chance of recovering my phone?
Samk80 said:
Hi,
I tried to upgrade my LG V30+ US998 to android Pie via TWRP but after the upgrade and system reboot the device got stuck in LG logo.
The download mode isn't working (device not being detected).
LGUP shows the device as "unknown" and adb is not detecting the device either.
I can't boot into TWRP anymore and flashing via LG flash tool 2014 fails (asks for server connection!).
I installed all the tools and LG mobile drivers on another computer and had no luck!
Do I have any chance of recovering my phone?
Click to expand...
Click to collapse
Why can't you boot to TWRP?
Use the hardware button dance, if you must.
__
Are you using the latest Dev Patched LGUP from the Pie KDZ threads? Uninstall any prior version and read the instructions carefully.
___
Your phone is not bricked. No one ever bricked their phone trying to update to Pie. Being stuck on logo is not bricked.
Tons of people get stuck on logo. So what? Then they re-flash 20h or whatever.
ChazzMatt said:
Why can't you boot to TWRP?
Use the hardware button dance, if you must.
__
Are you using the latest Dev Patched LGUP from the Pie KDZ threads? Uninstall any prior version and read the instructions carefully.
Click to expand...
Click to collapse
I teied the button dance and after i confirm the third Yes prompt device reboots to LG logo again.
I used both the pie patched LGUP and dev LGUP.
Samk80 said:
I teied the button dance and after i confirm the third Yes prompt device reboots to LG logo again.
I used both the pie patched LGUP and dev LGUP.
Click to expand...
Click to collapse
Reinstall LG Mobile drivers again.
Uninstall Dev Patched LGUP completely. Delete the folder from Programs/LG Electronics to make sure.
Re-install the Pie Dev Patched LGUP. Use the SetDev.bat in right click Administrator mode.
Then REBOOT the PC. You've installed two major PC components and Windows needs to process that.
Go into Download mode MANUALLY before opening LGUP. ONLY open LGUP from the desktop shortcut, not the folder icon.
ChazzMatt said:
Reinstall LG Mobile drivers again.
Uninstall Dev Patched LGUP completely. Delete the folder from Programs/LG Electronics to make sure.
Re-install the Pie Dev Patched LGUP. Use the SetDev.bat in right click Administrator mode.
Then REBOOT the PC. You've installed two major PC components and Windows needs to process that.
Go into Download mode MANUALLY before opening LGUP. ONLY open LGUP from the desktop shortcut, not the folder icon.
Click to expand...
Click to collapse
I tried every possible combination of the available apps.
Phone in download mode not recognized by the computer (tried on two computers).
If I connect the phone into the computer and open the LGUP it shows as "Unknown"
For some reason TWRP got wiped out after flashing Pie rom and I cannot boot into twrp to flash the old Ore rom.
I finally managed to fix my phone.
Below are the steps:
1- boot the phone im fastboot (connect to tbe computer via USB cable and press and hold both power and volume down until phone reboots then quickly release the power button and hold the volume down until the fastboot menu appears)
2- copy the twrp image into adb folder and rename to twrp.img
3- download and copy a working rom (in zip format) and paste into micro sd card and insert into phone
4- open the command prompt as administrator and navigate to adb folder then type the following commands in sequence
Adb devices
fastboot devices
fastboot flash recovery twrp.img
fastboot boot twrp.img
Now your phone will boot into twrp and you can install the Oreo zip rom into phone and enjoy using your LG phone again!
Thank you!
I've added this to the US998 Pie KDZ thread. That KDZ is very wonky. It's the only Pie people have problems flashing. Probably because LG has not yet released Open Market US998 and the one we are using is technically for U.S. Cellular US998.
I had no trouble flashing it myself -- on my backup V30+(former LS998) going straight from Nougat (never updated, it was my backup phone) to Pie through Dev Patched LGUP Refurbish mode. But lots of other people seem to have problems.
On my daily phone, I'm still on rooted stock Oreo with Magisk and Xposed mods.
Samk80 said:
I finally managed to fix my phone.
Below are the steps:
1- boot the phone im fastboot (connect to tbe computer via USB cable and press and hold both power and volume down until phone reboots then quickly release the power button and hold the volume down until the fastboot menu appears)
2- copy the twrp image into adb folder and rename to twrp.img
3- download and copy a working rom (in zip format) and paste into micro sd card and insert into phone
4- open the command prompt as administrator and navigate to adb folder then type the following commands in sequence
Adb devices
fastboot devices
fastboot flash recovery twrp.img
fastboot boot twrp.img
Now your phone will boot into twrp and you can install the Oreo zip rom into phone and enjoy using your LG phone again!
Click to expand...
Click to collapse
I think part of my problem was the Pie ROM.
I have the US998 UCL version and I've read that the LG only released the Pie update for LG V30 US998 model with the Buyer suffix (1CL, UCL, UCK) and US998Z (UCL) only. But I could be wrong!
Samk80 said:
I think part of my problem was the Pie ROM.
I have the US998 UCL version and I've read that the LG only released the Pie update for LG V30 US998 model with the Buyer suffix (1CL, UCL, UCK) and US998Z (UCL) only. But I could be wrong!
Click to expand...
Click to collapse
Right. LG has not yet released the Open Market USS98 KDZ yet. Theory is LG is waiting for the Sprint Pie KDZ to be accepted by Sprint. Open Market USS98 is the official North American carrier unlocked variant that needs to work with all carriers. So, Open Market US998 Pie KDZ (if ever released) will incorporate testing results from the long-delayed Sprint LS998 Pie KDZ (whenever it's finally released).
Samk80 said:
I finally managed to fix my phone.
Below are the steps:
1- boot the phone im fastboot (connect to tbe computer via USB cable and press and hold both power and volume down until phone reboots then quickly release the power button and hold the volume down until the fastboot menu appears)
2- copy the twrp image into adb folder and rename to twrp.img
3- download and copy a working rom (in zip format) and paste into micro sd card and insert into phone
4- open the command prompt as administrator and navigate to adb folder then type the following commands in sequence
Adb devices
fastboot devices
fastboot flash recovery twrp.img
fastboot boot twrp.img
Now your phone will boot into twrp and you can install the Oreo zip rom into phone and enjoy using your LG phone again!
Click to expand...
Click to collapse
Happy for you bro . knew it wasnt toast since its us998
Guys,
Without wasting any time coming direct to the point issue is that I want to install stock firmware in my MOTO G6. Since last 2-3 days I'm going through the below link but it's not working for me IDK why
https://forum.xda-developers.com/moto-g6/how-to/stock-firmware-moto-g6-t3792292
Also tried with RSD lite but that thing is not even showing or detecting my device.
My phone configuration:
Model- XT 1925-3
MOTO G6
64 GB
4 GB RAM
Please help (_/\_)
It sounds like your phone is not set up to all access via the USB port. You need to install motorola USB drivers; https://support.motorola.com/in/en/drivers
Then install Minimal ADB/Fastboot ; https://forum.xda-developers.com/showthread.php?t=2317790
Then have developer options enabled (setup/system/about phone - tap build number 7 times; then backup to developer options and turn on Android debugging/android debug bridge/USB debugging
Then to see if the computer is communicating with the phone, boot the phone into the fastboot flash mode (power off and then hold the power on button and the down volume button together); then issue the command in the adb/fastboot program command terminal window "fastboot devices". The phone should respond with the serial number of the phone and the text string "fastboot". When this happens, you know the phone is able to talk to the computer.
The link provided may or may not be for your phone. You can find all official motorola firmwares for the phone at;
Moto g6 {ali}
https://mirrors.lolinet.com/firmware/moto/ali/official/
moto g6 plus {evert}
https://mirrors.lolinet.com/firmware/moto/evert/official/
moto g6 play {aljeter}
https://mirrors.lolinet.com/firmware/moto/aljeter/official/
Its important that you use the correct firmware for your phone, by country, by carrier or retail version or you can brick the phone.
Then you can fastboot the firmware into the phone. You can also use RSD Lite once the phone is recognized under fastboot flash mode.
I would use https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714 , as it should find the correct firmware
I do not have the moto G6 - I use a moto g5+, but all the moto's are very similar
Hope that helps
HuNnEy said:
Guys,
Without wasting any time coming direct to the point issue is that I want to install stock firmware in my MOTO G6. Since last 2-3 days I'm going through the below link but it's not working for me IDK why
https://forum.xda-developers.com/moto-g6/how-to/stock-firmware-moto-g6-t3792292
Also tried with RSD lite but that thing is not even showing or detecting my device.
My phone configuration:
Model- XT 1925-3
MOTO G6
64 GB
4 GB RAM
Please help (_/\_)
Click to expand...
Click to collapse
RSD Lite doesn't work with windows 10 try 7
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Or LMSA
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my perry_f using XDA Labs
Nivead said:
It sounds like your phone is not set up to all access via the USB port. You need to install motorola USB drivers; https://support.motorola.com/in/en/drivers
Then install Minimal ADB/Fastboot ; https://forum.xda-developers.com/showthread.php?t=2317790
Then have developer options enabled (setup/system/about phone - tap build number 7 times; then backup to developer options and turn on Android debugging/android debug bridge/USB debugging
Then to see if the computer is communicating with the phone, boot the phone into the fastboot flash mode (power off and then hold the power on button and the down volume button together); then issue the command in the adb/fastboot program command terminal window "fastboot devices". The phone should respond with the serial number of the phone and the text string "fastboot". When this happens, you know the phone is able to talk to the computer.
The link provided may or may not be for your phone. You can find all official motorola firmwares for the phone at;
Moto g6 {ali}
https://mirrors.lolinet.com/firmware/moto/ali/official/
moto g6 plus {evert}
https://mirrors.lolinet.com/firmware/moto/evert/official/
moto g6 play {aljeter}
https://mirrors.lolinet.com/firmware/moto/aljeter/official/
Its important that you use the correct firmware for your phone, by country, by carrier or retail version or you can brick the phone.
Then you can fastboot the firmware into the phone. You can also use RSD Lite once the phone is recognized under fastboot flash mode.
I would use https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714 , as it should find the correct firmware
I do not have the moto G6 - I use a moto g5+, but all the moto's are very similar
Hope that helps
Click to expand...
Click to collapse
Thank you so much after so many tries this moto smart assistant finally worked for me
Thanks again :good: . Moderators can close the topic now :highfive:
This guide was made prior to there being a working custom recovery for this device. I highly recommend installing @afaneh92 TWRP in this thread and then simply flash magisk from recovery.
I purchased this phone a few days ago for around £120 - Bargain.
I have spent a few evenings trying to obtain root - and finally managed to achieve it with Magisk
Full data wipes are required during the process (please backup first)
Knox will trip but safetynet passes and google pay working once magisk hide enabled
Based on the Samsung specific guide provided on Magisk Github - with a few minor differences.
I have uploaded all of the tools and files used to my personal onedrive folder -
Make sure your device is on the latest firmware and download the zip
- I used SamFwTool version 1.21.0 to download the BTU Firmware for SM-A025G A025GXXU1AUA3
Install Magisk apk on your device.
Extract the AP _ tar.md5 from the downloaded firmware .zip using 7zip
Transfer the AP to your device and Patch it with Magisk , then copy back to your computer.
Enable OEM Unlock and Unlock the bootloader the instructions from magisk git are below, for those that need a reminder.
Spoiler: Unlocking Bootloader
Unlocking bootloader on modern Samsung devices have some caveats:
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader.
This will wipe your data and automatically reboot.
If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is greyed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
This is where we deviate from the magisk guide... as when I flashed the magisk patched AP along with the BL CP and CSC, you get a vbmeta error and it simply reboots to stock. Magisk seems to patch the vbmeta file and I tried replacing the vbmeta with the stock version from the firmware zip but that also was fruitless.
Extract the boot.img from magisk patched AP
Extract recovery.img.lz4 and vbmeta.img.lz4 from the stock (unpatched) AP file
7zip - create a new TAR, adding only those 3 files. Boot.tar will suffice for filename
Odin 3.14.4 - uncheck auto reboot and then Flash boot.tar in the AP section (CSC, HOME CSC, CP, BL not required - as the device and download are using the latest firmware)
The next part is essential and doing it wrong will again, result in no root....
I mistakenly pressed power up and it loaded fastboot... booting direct to recovery from fastboot again, results in no root.
Hold volume down and power to reboot...
As soon as the screen turns black indicating it is rebooting let go of volume down and hold power and volume up
Release power button when you see the android logo but continue to hold volume up
Release volume up when the unlocked bootloader warning appears
Tap the power button once to skip that warning
Stock recovery should now appear
Select wipe data / factory reset
Reboot system
Setup as usual and install the magisk apk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
. .
Update 10April2021: Since doing this quite a few times, I've actually had most success with Magisk 22.0 (I initially went with Canary - but stock is less hit and miss and if you do it exactly like the steps above you will get root.
Update:
Have just updated to magisk 22003 directly within magisk app - no issues to report so far
thank you so much for the guide, i found nothing from google
can i unroot after modify this device with magisk canary ??
Normanbayuaji said:
thank you so much for the guide, i found nothing from google
can i unroot after modify this device with magisk canary ??
Click to expand...
Click to collapse
No problem at all, It was the same position I was in so had to post as it was painful process - needed it documented for myself to follow in future too lol
yes - it's very easy to unroot directly in the magisk app
I successfully upgraded to the latest version 22004 from within the magisk app. No issues to report.
can this work on the tmobile version??
mines is a 025q
I am trying to use this same process on an SM-A025V (US Verizon) but I have ran into an issue. I was able to find and download firmware for my variant but I do not have the "oem unlock" option in my developer menu. Is this because I do not have the international version?
Flik93 said:
I am trying to use this same process on an SM-A025V (US Verizon) but I have ran into an issue. I was able to find and download firmware for my variant but I do not have the "oem unlock" option in my developer menu. Is this because I do not have the international version?
Click to expand...
Click to collapse
Seems like its carrier locked. You need to be able to unlock bootloader unfortunately
Ghet2 said:
can this work on the tmobile version??
Click to expand...
Click to collapse
Can you unlock your bootloader?
Dont kno i have t-mobile version and. I have it
Flik93 said:
I am trying to use this same process on an SM-A025V (US Verizon) but I have ran into an issue. I was able to find and download firmware for my variant but I do not have the "oem unlock" option in my developer menu. Is this because I do not have the international version?
Click to expand...
Click to collapse
CFKod said:
Seems like its carrier locked. You need to be able to unlock bootloader unfortunately
Click to expand...
Click to collapse
T-mobile isn't so would I be able to do this with t-mobile firmware . If it's available I don't kno
Well..
Ghet2 said:
Dont kno i have t-mobile version and. I have it
T-mobile isn't so would I be able to do this with t-mobile firmware . If it's available I don't kno
Click to expand...
Click to collapse
If you have oem unlock then you'll be able to do it...
CFKod said:
Well..
If you have oem unlock then you'll be able to do it...
Click to expand...
Click to collapse
Has to be a t-mobile firmware? or would this one work
Anything for a025u yes
CFKod said:
I purchased this phone a few days ago for around £120 - Bargain.
I have spent a few evenings trying to obtain root - and finally managed to achieve it with Magisk
Full data wipes are required during the process (please backup first)
Knox will trip but safetynet passes and google pay working once magisk hide enabled
Based on the Samsung specific guide provided on Magisk Github - with a few minor differences.
I have uploaded all of the tools and files used to my personal onedrive folder -
Make sure your device is on the latest firmware and download the zip
- I used SamFwTool version 1.21.0 to download the BTU Firmware for SM-A025G A025GXXU1AUA3
Install Magisk apk on your device.
Extract the AP _ tar.md5 from the downloaded firmware .zip using 7zip
Transfer the AP to your device and Patch it with Magisk , then copy back to your computer.
Enable OEM Unlock and Unlock the bootloader the instructions from magisk git are below, for those that need a reminder.
Spoiler: Unlocking Bootloader
Unlocking bootloader on modern Samsung devices have some caveats:
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader.
This will wipe your data and automatically reboot.
If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is greyed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
This is where we deviate from the magisk guide... as when I flashed the magisk patched AP along with the BL CP and CSC, you get a vbmeta error and it simply reboots to stock. Magisk seems to patch the vbmeta file and I tried replacing the vbmeta with the stock version from the firmware zip but that also was fruitless.
Extract the boot.img from magisk patched AP
Extract recovery.img.lz4 and vbmeta.img.lz4 from the stock (unpatched) AP file
7zip - create a new TAR, adding only those 3 files. Boot.tar will suffice for filename
Odin 3.14.4 - uncheck auto reboot and then Flash boot.tar in the AP section (CSC, HOME CSC, CP, BL not required - as the device and download are using the latest firmware)
The next part is essential and doing it wrong will again, result in no root....
Przez pomyłkę wcisnąłem zasilanie i załadowałem fastboot ... ponowne uruchomienie bezpośrednio do odzyskiwania z fastboot, nie daje roota.
Przytrzymaj głośność i włącz, aby ponownie uruchomić...
Gdy tylko ekran stanie się czarny, wskazując na ponowne uruchamianie, puść zmniejsz głośność i przytrzymaj zasilanie i zwiększ głośność
Zwolnij przycisk zasilania, gdy zobaczysz logo Androida, ale nadal zwiększaj głośność
Zwolnij głośność, gdy pojawi się ostrzeżenie o odblokowanym bootloaderze
Naciśnij raz przycisk zasilania, aby pominąć to ostrzeżenie
Odzyskiwanie zapasów powinno się teraz pojawić
Wybierz wyczyść dane / przywróć ustawienia fabryczne
Uruchom ponownie system
Skonfiguruj jak zwykle i zainstaluj aplikację magisk
View attachment 5241955. View attachment 5241957.View attachment 5241959
Aktualizacja 10 kwietnia 2021: Odkąd zrobiłem to kilka razy, w rzeczywistości odniosłem największy sukces z Magisk 22.0 (początkowo poszedłem z Canary – ale zapasy są mniej trafione i chybione, a jeśli zrobisz to dokładnie tak, jak powyższe kroki, dostaniesz root.
Click to expand...
Click to collapse
cześć5g
CFKod said:
I purchased this phone a few days ago for around £120 - Bargain.
I have spent a few evenings trying to obtain root - and finally managed to achieve it with Magisk
Full data wipes are required during the process (please backup first)
Knox will trip but safetynet passes and google pay working once magisk hide enabled
Based on the Samsung specific guide provided on Magisk Github - with a few minor differences.
I have uploaded all of the tools and files used to my personal onedrive folder -
Make sure your device is on the latest firmware and download the zip
- I used SamFwTool version 1.21.0 to download the BTU Firmware for SM-A025G A025GXXU1AUA3
Install Magisk apk on your device.
Extract the AP _ tar.md5 from the downloaded firmware .zip using 7zip
Transfer the AP to your device and Patch it with Magisk , then copy back to your computer.
Enable OEM Unlock and Unlock the bootloader the instructions from magisk git are below, for those that need a reminder.
Spoiler: Unlocking Bootloader
Unlocking bootloader on modern Samsung devices have some caveats:
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader.
This will wipe your data and automatically reboot.
If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is greyed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
This is where we deviate from the magisk guide... as when I flashed the magisk patched AP along with the BL CP and CSC, you get a vbmeta error and it simply reboots to stock. Magisk seems to patch the vbmeta file and I tried replacing the vbmeta with the stock version from the firmware zip but that also was fruitless.
Extract the boot.img from magisk patched AP
Extract recovery.img.lz4 and vbmeta.img.lz4 from the stock (unpatched) AP file
7zip - create a new TAR, adding only those 3 files. Boot.tar will suffice for filename
Odin 3.14.4 - uncheck auto reboot and then Flash boot.tar in the AP section (CSC, HOME CSC, CP, BL not required - as the device and download are using the latest firmware)
The next part is essential and doing it wrong will again, result in no root....
I mistakenly pressed power up and it loaded fastboot... booting direct to recovery from fastboot again, results in no root.
Hold volume down and power to reboot...
As soon as the screen turns black indicating it is rebooting let go of volume down and hold power and volume up
Release power button when you see the android logo but continue to hold volume up
Release volume up when the unlocked bootloader warning appears
Tap the power button once to skip that warning
Stock recovery should now appear
Select wipe data / factory reset
Reboot system
Setup as usual and install the magisk apk
View attachment 5241955. View attachment 5241957. View attachment 5241959
Update 10April2021: Since doing this quite a few times, I've actually had most success with Magisk 22.0 (I initially went with Canary - but stock is less hit and miss and if you do it exactly like the steps above you will get root.
Click to expand...
Click to collapse
Hi i have sm-a25g As I connect with vol plus vol minus I connect usb nothing happens but charging the battery as I hold other keys, e.g. power vol plus I release power I keep vol plus the phone jumps in fastboot mode. In download mode I can only enter from adb reboot download but bypass the bootloader lock window, the manual input combinations in download mode do not work for me. Do you have any idea and can I ask for help?
Hi, I have a problem with unlocking the bootloader in SM-A025G. I wrote a comment on you tube I got a contact from you whats upp. The problem is that after selecting oem unlock and connecting the turned off phone, holding vol plus vol minus and connect usb, there is only a charging mode and it should be a download mode with the selection of vol plus to unlock the bootloader. To flash firmware, the only way to go with adb reboot download but bypass the unlock board is the download mode. Phone with European distribution binary u2 android 11
[email protected] said:
cześć5g
Hi i have sm-a25g As I connect with vol plus vol minus I connect usb nothing happens but charging the battery as I hold other keys, e.g. power vol plus I release power I keep vol plus the phone jumps in fastboot mode. In download mode I can only enter from adb reboot download but bypass the bootloader lock window, the manual input combinations in download mode do not work for me. Do you have any idea and can I ask for help?
Click to expand...
Click to collapse
With device turned off but plugged into USB...
Power it back up
let go of power and hold volume up and volume down. and it will boot to the download mode screen.
[email protected] said:
Hi, I have a problem with unlocking the bootloader in SM-A025G. I wrote a comment on you tube I got a contact from you whats upp. The problem is that after selecting oem unlock and connecting the turned off phone, holding vol plus vol minus and connect usb, there is only a charging mode and it should be a download mode with the selection of vol plus to unlock the bootloader. To flash firmware, the only way to go with adb reboot download but bypass the unlock board is the download mode. Phone with European distribution binary u2 android 11
Click to expand...
Click to collapse
Sorry for late response.
Follow as per thread just posted
idk if this is news or not but im rooted on the boost variant of the sm-a025u. my question is now that im rooted can i flash the u1 (unlocked xaa) firmware to network unlock the device?
chrisdsj said:
idk if this is news or not but im rooted on the boost variant of the sm-a025u. my question is now that im rooted can i flash the u1 (unlocked xaa) firmware to network unlock the device?
Click to expand...
Click to collapse
How did u root it I have the metro version
Not sure regarding network unlock sorry.
Hello everyone..
I just got hands on LG V30+ carrier device from ntt docomo model number to be exact L-01K It's network unlocked and using adb debloat i have managed to get rid of almost docomo japan apps.
But i am stuck on android 9 pie. I tried to unlock bootloader official way but my device doesn't go for fastboot. I was wondering someone had this device and whether if it's possible to unlock and flash custom recovery..thank you
before you flash anything to your L-01k you need to backup the modem partitions with LG UP.
https://androidfilehost.com/?fid=11410963190603845019
for details about LGUP, go read here: https://forum.xda-developers.com/t/...-lgup-for-crossflashing.3780969/post-76510671
(Dump these partitions
-misc
-modem
-modemst1
-modemst2
-persist
-pstore
-recovery
If you have no backup of the modem, you will lose network and there's no firmware for the L-01k anywhere on the net to restore... ask me how I know..
see also
H930+ (L-01K) unlocked, but no carrier
I got me a V30+ 'Docomo' 128GB which had a japanese firmware installed and got recognized as a L-01K. I followed the WTF guide and successfully unlocked the bootloader after installing the H930 20r firmware, installed TWRP (and changed to 3.3.1...
forum.xda-developers.com
if you have backup your modem partitions please upload the files to some filehoster and share them here. I will try to restore my modem on my L-01k if I succeed Î will write a guide on how to unlock and root the L-01k and post it here.
relevant links:
Making modem.bin flashables for twrp
Starting this off by admitting that i fuxed up and failed to dump/backup my sprint stock files and such with the lgup dump option...luckily another member had the modem.bin file to hopefully fix my phone as i am stuck on 3g and cannot acces lte...
forum.xda-developers.com
[Guide] Getting H933/Any? Modem to work on a converted US998/H930.
A SOLUTION WAS DISCOVERED CLICK HERE TO ENJOY Hi Guys! So... I've no clue if my LTE connectivity is worse then before and since I'm scared of bricking my device by reverting back to the canadian firmware... I've got a canadian G6 so I...
forum.xda-developers.com
Hi,
Here is backup you required I done from my v30+. I used qfil to backup them you can also restore with qfil and your network will be back.
lg-v30-l01k.zip
drive.google.com
Just restore
modem
m1 > modemst1
m2 > modemst2
fsg
fsc
using qfil and lgv30 firehose elf file. go to partitions in qfil and restore each file.
Thanks
RomSlammer said:
before you flash anything to your L-01k you need to backup the modem partitions with LG UP.
https://androidfilehost.com/?fid=11410963190603845019
for details about LGUP, go read here: https://forum.xda-developers.com/t/...-lgup-for-crossflashing.3780969/post-76510671
(Dump these partitions
-misc
-modem
-modemst1
-modemst2
-persist
-pstore
-recovery
If you have no backup of the modem, you will lose network and there's no firmware for the L-01k anywhere on the net to restore... ask me how I know..
see also
H930+ (L-01K) unlocked, but no carrier
I got me a V30+ 'Docomo' 128GB which had a japanese firmware installed and got recognized as a L-01K. I followed the WTF guide and successfully unlocked the bootloader after installing the H930 20r firmware, installed TWRP (and changed to 3.3.1...
forum.xda-developers.com
if you have backup your modem partitions please upload the files to some filehoster and share them here. I will try to restore my modem on my L-01k if I succeed Î will write a guide on how to unlock and root the L-01k and post it here.
relevant links:
Making modem.bin flashables for twrp
Starting this off by admitting that i fuxed up and failed to dump/backup my sprint stock files and such with the lgup dump option...luckily another member had the modem.bin file to hopefully fix my phone as i am stuck on 3g and cannot acces lte...
forum.xda-developers.com
[Guide] Getting H933/Any? Modem to work on a converted US998/H930.
A SOLUTION WAS DISCOVERED CLICK HERE TO ENJOY Hi Guys! So... I've no clue if my LTE connectivity is worse then before and since I'm scared of bricking my device by reverting back to the canadian firmware... I've got a canadian G6 so I...
forum.xda-developers.com
Click to expand...
Click to collapse
Here is elf file if you dont have. You can go to qualcomm mode by plugging in usb cable in mobile and press volume - and power button and when black screen show keep pressing volume +. you also need to install qualcomm drivers to detect mobile in windows.
Thanks a lot for the files and advice! Will try to restore the modem now..
dont restore ftm i mentioned it by mistake.
I can't figure out how to flash the files back using QFIL. I was in download mode volup then connect USB, same as you do it with LGUP). But that didn't work. QFIL says "Download Failed switch to Emergency Download Mode".
I also tried flashing the modem.bin with TWRP (backup in TWRP, then replace modem.emmc.win with modem.bin and rename that accordingly, then restore backup in TWRP. But that did not work (SIM Card not recognized and no IMEI). Then I flashed back the original modem.emmc.win backup to fix sim card and IMEI.
I think I am missing the XML file for QFIL?
first install qualcomm drivers.
plug usb cable to pc and mobile. hold volume down and power button at same time and when black screen show on mobile keep pressing (don't hold) volume up without leaving other buttons.
when qualcomm mode is detected > run qfil and select port and than > select flat build and > elf file in programmer path and > select ufs storage type in bottom right.
then go to tools > partition manager and there you can find all the partitions first backup and than restore which i said before.
these backups will not work in twrp i think.
don't mix this with download mode in which we can go with just volume up and put cable in pc. if you don't know please google it first its qualcomm mode.
if you have fastboot try this command in fastboot:
fastboot reboot edl
if that works than just follow other steps. to quit this mode press volume down and power button for few seconds. in this mode screen just stay black and nothing will display on your screen.
OK found a youtube video on how to get into EDL 9008 mode:
- Connect the smartphone via USB to the computer.
- On the switched-on smartphone, hold VOL- and POWER
- As soon as the screen turns off, keep holding the VOL- and POWER buttons and simultaneously press VOL + quickly.
- The smartphone will have a black screen, and in the device manager on the PC will be "QUSB_BULK_CID: xxxx_SN: xxxxxxxx" or "Qualcomm HS-USB QDLoader 9008 (COM x)
OK, that worked for me (windows device manager reported "Qualcomm HS-USB QDLoader 9008) , but when I wanted to use the partition manager in QFIL i get the "Download Fail Sahara QSaharaServer Fail: Process Fail "
I'll try this now:
-downgrade to Nougat H930 KDZ ( H93010v_00_OPEN_EU_OP_1120.kdz)
in fastboot: (Using the modem.bin, modemst1.bin, modemst2.bin from L-01k QFIL dump)
fastboot erase modem (enter)
fastboot erase modemst1 (enter)
fastboot erase modemst2 (enter)
fastboot oem lock (enter)
fastboot flash modem modem.bin (enter)
fastboot flash modem modemst1.bin (enter)
fastboot flash modem modemst2.bin (enter)
EDIT: it didn't work
But at least I know now how to get into Download Mode from a Bootloop:
1. Connect USB to PC
2. press Vol+, Vol-, Power until the phone restarts with black screen
3. immediately release Vol- and Power and keep pressing Vol+
.. voila.. Download mode
did you add the v30 file in proggamer path in qfil which i provided and changed the storage type to ufs?
yes, I used that firehose V30 file and I verified that storage is set to UFS.
have you fixed it?
nope, but after flashing the modem with ADB and also trying the V300k Korean ROM, I have learned how to fix a near bricked V30 by using 9008 Qualcomm unbrick mode back to life .
I think the only way to fix this is if a L-01k KDZ is released or someone manages to root his L-01k without overwriting the modem and uploads his complete TWRP backup.
Thanks guys for ur help. It seems like no bootloader unlock for my LG L-01K. So modem backup didn't work. I'm so sorry to hear that. I wish i had rooted my device. But i can't even unlock the bootloader. I want to try custom roms so badly. I guess i have to stuck with android pie. Thanks again.
RomSlammer said:
nope, but after flashing the modem with ADB and also trying the V300k Korean ROM, I have learned how to fix a near bricked V30 by using 9008 Qualcomm unbrick mode back to life .
I think the only way to fix this is if a L-01k KDZ is released or someone manages to root his L-01k without overwriting the modem and uploads his complete TWRP backup.
Click to expand...
Click to collapse
do you have wifi working and your imei is not null?
wifi works, IMEI exists, says Sim card 1 is "PERM locked".
I'm on H93020d_00_OPEN_EU_OP_0326.kdz now.
The same Sim card works perfectly in my LG G8s
NamlaGeeX said:
Hello everyone..
I just got hands on LG V30+ carrier device from ntt docomo model number to be exact L-01K It's network unlocked and using adb debloat i have managed to get rid of almost docomo japan apps.
But i am stuck on android 9 pie. I tried to unlock bootloader official way but my device doesn't go for fastboot. I was wondering someone had this device and whether if it's possible to unlock and flash custom recovery..thank you
Click to expand...
Click to collapse
Debloat Japanese Apps like Docomo Contacts App from L01K V30+ ?
How did you do that using ADB ?
With or w/o Root ?
Can you or anyone explain ?
Hi guys sadly I completely softbricked my motorola X40 phone i'm a idiot.
I flashed to a wrong firmware file (edge 30 pro) and re-locked bootloader then found it phone doesn't properly boot anymore.
I can boot it in fastboot mode but flashing in normal fastboot mode doesn't work with locked bootloader and lenovo rescue tool can't help me either.
Edit: Weirdly I managed to boot it up and it shows as a "motorola edge 30 pro" and I can control my screen with a USB mouse.
But when I try to enable "OEM unlocking" in developer options the settings app just crashes.
But my problem stays the same, i'm still stuck with a locked bootloader
Is there any chance to trick this phone into EDL mode or any working blankflash?
Any suggestions? i'd appreciate it
jody2k said:
Hi guys sadly I completely softbricked my motorola X40 phone i'm a idiot.
I flashed to a wrong firmware file (edge 30 pro) and re-locked bootloader then found it phone doesn't properly boot anymore.
I can boot it in fastboot mode but flashing in normal fastboot mode doesn't work with locked bootloader and lenovo rescue tool can't help me either.
Edit: Weirdly I managed to boot it up and it shows as a "motorola edge 30 pro" and I can control my screen with a USB mouse.
But when I try to enable "OEM unlocking" in developer options the settings app just crashes.
But my problem stays the same, i'm still stuck with a locked bootloader
Is there any chance to trick this phone into EDL mode or any working blankflash?
Any suggestions? i'd appreciate it
Click to expand...
Click to collapse
It doesn't matter if the oem lock is on to flash the stock firmware.
You can directly flash the right firmware via fastboot. Lenovo rescue tool may not flash...
cascade128 said:
It doesn't matter if the oem lock is on to flash the stock firmware.
You can directly flash the right firmware via fastboot. Lenovo rescue tool may not flash...
Click to expand...
Click to collapse
Hi thanks for the response, how to flash directly stock firmware? which method should I use? This is what I get when I try to flash anything through adb (phone in fastboot mode) I added a screenshot from adb in windows and took a picture from my phone to show in which fastboot mode it shows.
Tried several things flashing directly from adb but it always says permission denied because of the bootloader lock, maybe i'm doing something wrong.
It's not adb, it's fastboot mode.
Where you are is right.
It will be in the mode in the screenshot of the device, that's right.
Use the one in the file i gave you.
Here are the guidelines.
01. Download the latest Firmware from lolinet
02. We extract the firmware.zip, open servicefile.xml and copy the contents into this website
03. Download the mfastboot.rar ADB i gave and put it in the rom folder you extracted.
04. We put the flashfile.bat we created (Step 02. Extract, open servicefile.xml and copy the content to this site) into the rom folder you extracted.
05. Reboot your phone into fastboot (adb reboot fastboot or press and hold Power + Volume Down)
06. Everything is ready, click on the ''flashfile.bat'' file.
07. Don't disconnect the phone until the update has finished.
cascade128 said:
It's not adb, it's fastboot mode.
Where you are is right.
It will be in the mode in the screenshot of the device, that's right.
Use the one in the file i gave you.
Here are the guidelines.
01. Download the latest Firmware from lolinet
02. We extract the firmware.zip, open servicefile.xml and copy the contents into this website
03. Download the mfastboot.rar ADB i gave and put it in the rom folder you extracted.
04. We put the flashfile.bat we created (Step 02. Extract, open servicefile.xml and copy the content to this site) into the rom folder you extracted.
05. Reboot your phone into fastboot (adb reboot fastboot or press and hold Power + Volume Down)
06. Everything is ready, click on the ''flashfile.bat'' file.
07. Don't disconnect the phone until the update has finished.
Click to expand...
Click to collapse
Hi thanks for helping me, I downloaded the right firmware, uploaded the servicefile.xml to the site you gave me and created the flashfile.bat. Pasted the flashfile.bat into the samen folder as the rom and also extracted the mfastboot.rar into the same rom folder.
Then clicked on the flashfile.bat but sadly I get the same error's (Permission Denied)
My phone is still in fastboot mode (right screenshot)
Any idea's?
jody2k said:
Hi thanks for helping me, I downloaded the right firmware, uploaded the servicefile.xml to the site you gave me and created the flashfile.bat. Pasted the flashfile.bat into the samen folder as the rom and also extracted the mfastboot.rar into the same rom folder.
Then clicked on the flashfile.bat but sadly I get the same error's (Permission Denied)
My phone is still in fastboot mode (right screenshot)
Any idea's?
Click to expand...
Click to collapse
Very interesting, it shouldn't give such an error. You are flashing Motorola signed images, you don't need the bootloader unlocked for this Sorry i can't be of more help, i hope you can recover your device...
cascade128 said:
Very interesting, it shouldn't give such an error. You are flashing Motorola signed images, you don't need the bootloader unlocked for this Sorry i can't be of more help, i hope you can recover your device...
Click to expand...
Click to collapse
Yea indeed well thanks anyway, my only hope left is a third party recovery tool that supports this phone in future.
I'll put the X40 in my closet until then and buy another new phone in the meanwhile don't have much of a choice lol.
Hello!
Did you try RSDLite tool to flash firmware?
thunderman75 said:
Hello!
Did you try RSDLite tool to flash firmware?
Click to expand...
Click to collapse
I tried but the issue is there that it doesn't detect the port / device on the RSDlite tool.
Meanwhile I can see in devicemanager in windows the phone is detected in ADB/fastboot mode but RSDlite tool needs some portmode to succeed, the tool says it doesn't detect my device. I can't seem to connect it with that port RSDlite tool needs, also tried general ADB drivers but didn't help either. I also saw in one topic to make it work with RSD tool you need to install the qualcomm drivers, but these drivers don't work with this phone in normal fastboot mode. In other words I can't seem to RSD tool recognise my phone on the needed port. I think this tool only works in EDL mode (+qualcomm driver) but my moto X40 doesn't yet support EDL mode I think.
https://androidmtk.com/use-rsd-lite-tool
=> I followwed this tutorial but @ Step nr.8 there isn't any port or device detected even when my phone is correctly in fastboot mode
I tried Generic ADB drivers and the official motorola USB drivers, both detected in devicemanager in windows but RSDtool lite didn't detect my phone.
jody2k said:
I tried but the issue is there that it doesn't detect the port / device on the RSDlite tool.
Meanwhile I can see in devicemanager in windows the phone is detected in ADB/fastboot mode but RSDlite tool needs some portmode to succeed, the tool says it doesn't detect my device. I can't seem to connect it with that port RSDlite tool needs, also tried general ADB drivers but didn't help either. I also saw in one topic to make it work with RSD tool you need to install the qualcomm drivers, but these drivers don't work fastboot mode. In other words I can't seem to RSD tool recognise my phone on the needed port. I think this tool only works in EDL mode (+qualcomm driver) but my moto X40 doesn't yet support EDL mode I think.
https://androidmtk.com/use-rsd-lite-tool
=> I followwed this tutorial but @ Step nr.8 there isn't any port or device detected even when my phone is correctly in fastboot mode
I tried Generic ADB drivers and the official motorola USB drivers, both detected in devicemanager in windows but RSDtool lite didn't detect my phone.
Click to expand...
Click to collapse
This looks promising:
Motorola Unbrick Tool: Unbrick any Moto Device via EDL Mode
In this comprehensive guide, we will show you the detailed steps to unbrick any Motorola device booted to EDL Mode using the Unbrick Tool.
droidwin.com
thunderman75 said:
This looks promising:
Motorola Unbrick Tool: Unbrick any Moto Device via EDL Mode
In this comprehensive guide, we will show you the detailed steps to unbrick any Motorola device booted to EDL Mode using the Unbrick Tool.
droidwin.com
Click to expand...
Click to collapse
Yeah let's hope my device model (X40) get's support soon
@mark332 Any idea's?
I have the same problem, because I did the same thing hahaha, I tried these methods and nothing was successful, I tried to use Lenovo's RSA, but it only installs the correct firmware and Fastboot, but when it comes to rescuing it just has a "Warning" message.
zequinhaBR said:
I have the same problem, because I did the same thing hahaha, I tried these methods and nothing was successful, I tried to use Lenovo's RSA, but it only installs the correct firmware and Fastboot, but when it comes to rescuing it just has a "Warning" message.View attachment 5872305
Click to expand...
Click to collapse
Guess we are in the same boat loll xp having indeed the exact same message. I think the RSA tool detects the right device but it checks for some sort of keys/verification and sees it isn't the right firmware so it stops flashing.
I have found out you can also enter recovery mode by selecting "recovery" in fastboot mode with the key buttons.
Then you need to press power button + down key for 3 seconds, then short the volume up key.
Youll get a other menu with also fastboot mode and adb sideload etc...
but again sadly neither fastboot or adb sideload did work for me
When I tried to flash the original firmware in sideload mode trough ADB it gives a"verification error"
In fastboot mode it says that it can't flash with locked device
I hope this info will be any useful for people stumble upon this topic in the future and maybe help to unbrick this phone.
jody2k said:
I tried but the issue is there that it doesn't detect the port / device on the RSDlite tool.
Meanwhile I can see in devicemanager in windows the phone is detected in ADB/fastboot mode but RSDlite tool needs some portmode to succeed, the tool says it doesn't detect my device. I can't seem to connect it with that port RSDlite tool needs, also tried general ADB drivers but didn't help either. I also saw in one topic to make it work with RSD tool you need to install the qualcomm drivers, but these drivers don't work with this phone in normal fastboot mode. In other words I can't seem to RSD tool recognise my phone on the needed port. I think this tool only works in EDL mode (+qualcomm driver) but my moto X40 doesn't yet support EDL mode I think.
https://androidmtk.com/use-rsd-lite-tool
=> I followwed this tutorial but @ Step nr.8 there isn't any port or device detected even when my phone is correctly in fastboot mode
I tried Generic ADB drivers and the official motorola USB drivers, both detected in devicemanager in windows but RSDtool lite didn't detect my phone.
Click to expand...
Click to collapse
New hope on horizont for your phone...Machine with Windows10(32-bit) and Moto USB drivers(32-bit).
Phone booted in fastboot mode and connected to PC,recognized instantly.
Screenshot of my Moto Edge 30 ultra connected to above mentioned PC.
Good luck!!!
thunderman75 said:
New hope on horizont for your phone...Machine with Windows10(32-bit) and Moto USB drivers(32-bit).
Phone booted in fastboot mode and connected to PC,recognized instantly.
Screenshot of my Moto Edge 30 ultra connected to above mentioned PC.
Good luck!!!
Click to expand...
Click to collapse
Hey man thanks for your response, sadly i'm on a 64bit windows 11 version. Would it be any different than the 64bit driver vs 32bit you think? Because have tried this several times can't get RSD lite detect my phone . In device manager it's detected first as "fastboot rtwo s" and when the moto 64bit driver is installed it's detected as "motorola ADB interface" so it's correctly detect by the system.
My phone is also in fastboot mode never the less RSD lite tool doesn't detect anything
Guess I could try to install windows 10 32bit i'll keep this updated
jody2k said:
Hey man thanks for your response, sadly i'm on a 64bit windows 11 version. Would it be any different than the 64bit driver from motorola you think? Because have tried this several times can't get RSD lite detect my phone . In device manager it's detected first as "fastboot rtwo s" and when the moto 64bit driver is installed it's detected as "motorola ADB interface" so it's correctly detect by the system.
Never the less RSD lite tool doesn't detect anything
On which mode is your edge 30 phone, fastboot or edl?
Click to expand...
Click to collapse
I also have 64 bit Win11 machine with RSD Lite installed and it can't detect phone.
But when I connect it to my old laptop(Win10-32 bit,RSD Lite) phone is detected instantly.
Try to find someone who has machine with 32 bit Windows and try to rescue your phone.
Tip from professionals: RSD Lite works best with older version of a 32 bit Windows...
thunderman75 said:
I also have 64 bit Win11 machine with RSD Lite installed and it can't detect phone.
But when I connect it to my old laptop(Win10-32 bit,RSD Lite) phone is detected instantly.
Try to find someone who has machine with 32 bit Windows and try to rescue your phone.
Tip from professionals: RSD Lite works best with older version of a 32 bit Windows...
Click to expand...
Click to collapse
Just tried on my older 32bit computer with windows 10 and installed the 32bit driver for motorola. Sadly the issue is the same, RSD lite doesn't detect the moto x40. Where did you download the driver?
Motorola USB Driver for Windows 32-Bit/64-Bit - Driver Market
Download now the latest and official Motorola USB Driver for Windows. We shared the latest Motorola USB Driver for Windows.
www.drivermarket.net
Reinstall driver and restart PC(mandatory),it should work then.
thunderman75 said:
Motorola USB Driver for Windows 32-Bit/64-Bit - Driver Market
Download now the latest and official Motorola USB Driver for Windows. We shared the latest Motorola USB Driver for Windows.
www.drivermarket.net
Reinstall driver and restart PC(mandatory),it should work then.
Click to expand...
Click to collapse
Tried that too several times but thanks for the suggestion anyways.
Took my time also this evening to reinstall a clean windows 32bit version, installed 32bit moto driver again from your link.
Reboot, nope
Same issue, RSD lite doesn't detect anything while the driver and device is recognized in device manager whatever I tried last 2 weeks.
I also opened the phone and searched on the motherboard for EDL test points, no avail too.
I think the RSD tool lite or the usb driver needs a update for this device or someone needs to find out how to get this phone into EDL mode. This can take months maybe years who knows lol
I just gave up and bought myself a new phone (xiaomi 13)