Related
Hi there
i wiped data to install a new rom. But i wiped the recovery and also the rom so now i only see the bootloader
i see bootloader version 4.18
fastboot mode in red
lock state unlocked
The problem is : my computer won't recognize the n7 though ADB
when i try driver test with nexus root toolkit it says adb device was not found
Si now i'm stuck and i can't install any rom or recovery to boot in
please anybody help
adin59 said:
Hi there
i wiped data to install a new rom. But i wiped the recovery and also the rom so now i only see the bootloader
i see bootloader version 4.18
fastboot mode in red
lock state unlocked
The problem is : my computer won't recognize the n7 though ADB
when i try driver test with nexus root toolkit it says adb device was not found
Si now i'm stuck and i can't install any rom or recovery to boot in
please anybody help
Click to expand...
Click to collapse
Somehow i managed to install a rom. It's Fixed
adin59 said:
Somehow i managed to install a rom. It's Fixed
Click to expand...
Click to collapse
I hate to bring this thread back to life but, how did you manage to do it? I am in the exact same situation but bootloader 4.23. Did you manage to install the ROM through Nexus Root? Or platform tools?
Any help is appreciated.
I am attempting to flash the factory image. Found here. http://forum.xda-developers.com/showthread.php?t=1907796
ADB devices does not list my device and Nexus Root tool says not found. Not sure what else to do at this point.
kktvr4 said:
I hate to bring this thread back to life but, how did you manage to do it? I am in the exact same situation but bootloader 4.23. Did you manage to install the ROM through Nexus Root? Or platform tools?
Any help is appreciated.
I am attempting to flash the factory image. Found here. http://forum.xda-developers.com/showthread.php?t=1907796
ADB devices does not list my device and Nexus Root tool says not found. Not sure what else to do at this point.
Click to expand...
Click to collapse
"
I'm assuming you're in the bootloader while trying to do this. ADB stands for "Android Debug Bridge". The bootloader really has nothing to do with the Android operating system, thus ADB isn't running. You need to use fastboot commands. Try "fastboot devices".
korockinout13 said:
"
I'm assuming you're in the bootloader while trying to do this. ADB stands for "Android Debug Bridge". The bootloader really has nothing to do with the Android operating system, thus ADB isn't running. You need to use fastboot commands. Try "fastboot devices".
Click to expand...
Click to collapse
Thank you very much, that worked for me. :good:
Hi...
This is the tutorial to root any Moto G
To root any Moto G, three basic steps need to be followed... you can either do them manually or use a tool do them for you. It is advised to follow them manually so that if there's some bug in the tool you don't get into any trouble.
CAUTION - You will lose all data and files so better back them up.
For Google Play edition devices, the process is same and only the recovery.img file is different. For GPe CWM Advanced Edition recovery go here https://goo.im/devs/philz_touch/CWM_Advanced_Edition/ and select falcon_gpe and download the latest one.
For AT&T and Verizon models don't do anything written above. Just download the Towelroot app. Its a one click root app and doesn't require a PC. Itis trustworthy but is not guaranteed to work but you must give it a try since it won't do any harm and claims of never bricking a phone. Please reply with the result and your android and kernel version.It will probably not work on phones build after June 3 but you can give it a try. You can download it from the website https://towelroot.com
The three steps are :-
1) UNLOCKING THE BOOTLOADER
2) FLASHING CUSTOM RECOVERY
3) INSTALLING SuperSu.zip FILE THROUGH RECOVERY. (SuperSu is acknowledge as the best app to give superuser and root rights)
UNLOCKING THE BOOT LOADER - The instructions to unlock the boot loader are given in the official Motorola website here https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a . Don't be scared by their warnings.
UPDATE - There currently seems to be an issue with unlocking the bootloader on devices running 4.4.4 though it works for 4.4.2. The issue is with Motorola and is that, the unlock code given by the company is showing an error. They are fixing it and it may take some time though you can give it a try as it won't do any harm. Or you can downgrade the boot loader to 4.4.2 and then unlock it.
As confirmed by the Motorola agent, the problem of unlocking bootloader on 4.4.4 has been fixed
FLASHING CUSTOM RECOVERY :-
To flash a custom recovery, you need these things
1) PC and a USB data cable
2) Android SDK ( developer.android.com/sdk/index.html ) For flashing recovery only SDK is needed but it's your wish if you want to download the ADT bundle. After downloading and unzipping the sdk , open the SDK manager and download only the platform tools for this.. rest is your wish..... and separately download ADB tools and fastboot and extract them minimal-adb-and-fastboot.software.informer.com/1.1/
3) Recovery.img file - You can either use CWM foum.xda-developers.com/showthread.php?t=2563599 or CWM advanced editionforum.xda-developers.com/showthread.php?t=2639583 or TWRP forum.xda-developers.com/showthread.php?t=2561757. EDIT - If your phone had come pre installed with 4.4.4 then use only CWM Advanced Edition. CWM Advanced Edition doesn't make backup on XT1033
4) Motorola drivers https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97326/p/30,6720,9050
5) Enable USB Debugging mode in your phone by going to Settings-About Phone and then tap the build number until you get the toast 'You are a developer'. Now go to Settings again and you will see a new Developer Options there. Go there and enable USB debugging.
6) Have at least 25% of charge on your phone.
After getting all these things:-
1) Download the recovery.img file to your PC and copy paste it to android SDK/platform tools folder.
2) Boot your phone to fastboot mode by first switching it off and holding the volume down and power button for 3 seconds.
3) When in fastboot mode, connect your phone to pc, go to the platform tools folder, there pres shifft and right mouse click simultaneously and select 'open command prompt window here'.
4) In the command window enter
Code:
fastboot devices
If it shows a number and fastboot then we are good..
5) Then enter
Code:
fastboot flash recovery recovery.img
( where in recovery.img the recovery is the name of your recovery file. Example if the name of recovery file is ABC then enter fastboot flash recovery ABC.img)
5) Press enter and if the command prompt window displays the message okay then the recovery is successfully flashed.
6) Now just boot your phone to recovery mode through fastboot mode by following the on screen instructions and in recovery mode select Reboot System Now to reboot your phone normally.
(see attached images below for screenshots)
INSTALLING SuperSu
To install SuperSu :-
1) Download SuperSu zip file download.chainfire.eu/452/SuperSU/ and transfer it to your phone
2) Reboot to recovery via fastboot.
3) Select install zip and select choose from SD card.
4) Locate the file and install it.
5) Now reboot your phone.
YUP.. YOU ROOTED YOUR PHONE!
Download any root checker app from the Play Store to check whether your phone is rooted or not.
If you get into any trouble, please contact and don't forget to hit thanks if it helped
Consider rating the thread by going to the option 'rate thread' which is located above the thread on the right side. You can also participate in the poll
I have a huawei p6 but I'm absolutely not satisfied with that and I bought a moto g for my girlfriend and that is awesome.
The only thing why I haven't bought the g for myself as well is the rooting. That time I didn't find an easy way to root it.
If it is a working method than I will buy the 4g verson with sd card support
Sent from my HUAWEI P6-U06 using XDA Free mobile app
sisqoboy said:
I have a huawei p6 but I'm absolutely not satisfied with that and I bought a moto g for my girlfriend and that is awesome.
The only thing why I haven't bought the g for myself as well is the rooting. That time I didn't find an easy way to root it.
If it is a working method than I will buy the 4g verson with sd card support
Sent from my HUAWEI P6-U06 using XDA Free mobile app
Click to expand...
Click to collapse
Yup dude...this works for sure..!
I also added screenshots.. check them out.
Meuuks13 said:
Yup dude...this works for sure..!
Click to expand...
Click to collapse
Does this work with the latest bootloader on 4.4.4? Im still stock but i wanna root it so much
Thanks
motocruiser said:
Does this work with the latest bootloader on 4.4.4? Im still stock but i wanna root it so much
Thanks
Click to expand...
Click to collapse
I looked into it just now... Currently there's an issue with Motorola with unlocking the bootloader when on 4.4.4...As people say, the unlock code given my Motorola is showing an error... You can still try it.. maybe it's even fixed by now.. Even if it fails there wouldn't be any harm.. Though the unlocking works fine with 4.4.2... You can revert back to 4.4.2, unlock the bootloader and then update to 4.4.4... The thing will be same as you will lose all data and files when unlocking the bootloader and so in reverting to 4.4.2.....(Remember, only unlocking doesn't mean you won't recieve updates, you won't receive updates only if you flash a custom recovery.)
EDIT - I added it to the OP. Thanks for bringing it to attention.
And does this work for Verizon model
Sent from my XT1028 using XDA Premium 4 mobile app
xrilex said:
And does this work for Verizon model
Sent from my XT1028 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You have Verizon I see. The only you will probably face is unlocking the bootloader.. Oh, wait first let me laugh... lol...OK....At one point of time you couldn't unlock the bootloaders for AT&T and Verizon and then we were blessed by the 'one click root' app by the famous hacker geohot called TowelRoot. This app claims to root all the AT&T and Verizon devices with just a click. You don't even need a PC. Just download the app and in the app chick 'make it rain'. Though this is not guaranteed to work but must give a try as it won't do any harm but there's a chance of bricking the phone but you can easily recover from a soft brick by flashing the stock firmware.
Towelroot - https://towelroot.com/
P.S. - Please reply if you tried this and if it didn't work reply with your android version and kernel version. Well reply with your android version and kernel version anyway.
Edit- I added it to the OP
Meuuks13 said:
I looked into it just now... Currently there's an issue with Motorola with unlocking the bootloader when on 4.4.4...As people say, the unlock code given my Motorola is showing an error... You can still try it.. maybe it's even fixed by now.. Even if it fails there wouldn't be any harm.. Though the unlocking works fine with 4.4.2... You can revert back to 4.4.2, unlock the bootloader and then update to 4.4.4... The thing will be same as you will lose all data and files when unlocking the bootloader and so in reverting to 4.4.2.....(Remember, only unlocking doesn't mean you won't recieve updates, you won't receive updates only if you flash a custom recovery.)
EDIT - I added it to the OP. Thanks for bringing it to attention.
Click to expand...
Click to collapse
thanks for your help dude but i heared that if you flash back to 4.4.2 your bootloader is still the latest so its still unlockable...
i have found a fix on a motorola customer forum for this problem, but when i flash this testdrive motoboot image file it goes wrong and i cant fix it by my self
motocruiser said:
thanks for your help dude but i heared that if you flash back to 4.4.2 your bootloader is still the latest so its still unlockable...
i have found a fix on a motorola customer forum for this problem, but when i flash this testdrive motoboot image file it goes wrong and i cant fix it by my self
Click to expand...
Click to collapse
Sorry I didn't know that. Downgrading the bootloader is a very risky process.
What did you exactly do?
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
t.lou91 said:
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
Click to expand...
Click to collapse
Please tell which android version your phone came preinstalled with and what recovery you used.
Also when you reboot to recovery, after the blank screen do you see the android logo lying down with a red triangle?
t.lou91 said:
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
Click to expand...
Click to collapse
Please tell your phone's android version and the recovery you used and what did you enter at the command prompt?
Meuuks13 said:
Sorry I didn't know that. Downgrading the bootloader is a very risky process.
What did you exactly do?
Click to expand...
Click to collapse
Well it doesnt go wrong like you think so my phone is actually not bricked.
But the command window says that the operation failed so i think something is wrong with this testdrive image from the moto forum.
thanks
motocruiser said:
Well it doesnt go wrong like you think so my phone is actually not bricked.
But the command window says that the operation failed so i think something is wrong with this testdrive image from the moto forum.
thanks
Click to expand...
Click to collapse
Testdrive image?
Meuuks13 said:
Testdrive image?
Click to expand...
Click to collapse
Yeah they say, if you on 4.4.4 and want to unlock your bootloader you have to flash the motoboot_testdrive.img file wich downgrades the bootloader to i think it was called 40.15 or so after that you have to unlock your bootloader and then flash the motoboot 4.4.4 stock image so that you have the actual one but for me it failed while i try to flash this testdrive image
motocruiser said:
Yeah they say, if you on 4.4.4 and want to unlock your bootloader you have to flash the motoboot_testdrive.img file wich downgrades the bootloader to i think it was called 40.15 or so after that you have to unlock your bootloader and then flash the motoboot 4.4.4 stock image so that you have the actual one but for me it failed while i try to flash this testdrive image
Click to expand...
Click to collapse
So basically you want to downgrade the bootloader and then unlock it?
Well if you are on KitKat you can downgrade the bootloader by flashing 4.3 , then unlocking the bootloader and then updating to KitKat
Thanks for the guide. I've already recommended it to someone who was having problems.
jselene said:
Thanks for the guide. I've already recommended it to someone who was having problems.
Click to expand...
Click to collapse
Cool.
Thanks Meuuks13. This worked well.
Also, I've found that you can remove the "unlocked bootloader warning message" shown on boot-up by following the method in the Moto X forum:
http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566
JDCGW said:
Thanks Meuuks13. This worked well.
Also, I've found that you can remove the "unlocked bootloader warning message" shown on boot-up by following the method in the Moto X forum:
http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566
Click to expand...
Click to collapse
I got something wayyyy better than that!
I let you remove that sign and use the pics given here forum.xda-developers.com/moto-g/themes-apps/shareboot-logos-t2875147 or you can give me the pic you want and I will make it in such a way that you can use it.
Hi there,
I tried to update my Moto G4 Plus and I think I made some big mistakes..
I can only start into Bootloader with the following text shown below:
AP Fastboot Flash Mode (Secure)
BL: B0.0E (sha-4986429, 2016-104-13 14:23:47)
Baseband: [bla] ATHENE_EMEA_DSDS_CUST
Product/Variant: athene_16mp XT1642 16GB P2A
Serial Number: [bla]
CPU: MSM8952
eMMC: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000007
DRAM: 2GB SAMSUNG LP3 DIE=8GB M5=01 M6=05 M7=00 M8=5f
Console [NULL]: null
Battery OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
Click to expand...
Click to collapse
- No TWRP or other Recovery
- No OS
- No Fastboot connection to my Win10 64bit anymore (
I think the problem is the "AP Fastboot Flash Mode (Secure)" Mode.
Any ideas how to solve it?!
thanks alot anyway
The AP Fastboot Flash mode(secure) seems okay to me. However it is highly possible that your drivers aren't installed on the phone. So in this case try to first connect the phone to the computer and see if it get's detected or not, and then you should manually install the fastboot USB driver. Download the driver zip from Google's repository and extract it, later choose the .inf file and then the Android Bootloader Interface.
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
PS: This driver and the fastboot adb binaries are completely different thing. fastboot won't work unless you have this USB driver.
Thank you. When I connect my phone, I get the message on my phone "USB Connected" and in the windows device manager there comes an Android Device "Motorola ADB Interface" (official Lenovo driver). I also tried to install the *.inf file (downloaded it as you told), but there is no difference.
I tried the "blankflash" https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But I get the same message in cmd as always. < waiting for device > I dont know what to do..
edit: I got the message when I tried the blankflash.bat. Now I tried to install TWRP with fastboot and it worked!
Tanks alot!
Now, I want to install the lastest stock ROM. In the meantime I downloaded this version "ATHENE_NPJS25.93-14-8".
Do I have to install anything else like a boot.img? I made a full wipe..
Can I use the ElementalX Kernel?
stefanhanz said:
Thank you. When I connect my phone, I get the message on my phone "USB Connected" and in the windows device manager there comes an Android Device "Motorola ADB Interface" (official Lenovo driver). I also tried to install the *.inf file (downloaded it as you told), but there is no difference.
I tried the "blankflash" https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But I get the same message in cmd as always. < waiting for device > I dont know what to do..
edit: I got the message when I tried the blankflash.bat. Now I tried to install TWRP with fastboot and it worked!
Tanks alot!
Now, I want to install the lastest stock ROM. In the meantime I downloaded this version "ATHENE_NPJS25.93-14-8".
Do I have to install anything else like a boot.img? I made a full wipe..
Can I use the ElementalX Kernel?
Click to expand...
Click to collapse
The latest stock ROM is the NPJS25.93-14-10 (Sept 2017 security patch) build https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
You'll have to flash the stock ROM in fastboot, which would wipe TWRP off your device again. You cannot properly flash stock firmware in TWRP (only can flash the system in TWRP).
Once you've flashed the stock ROM and TWRP, you can use ElementalX, I'm using the 1.0.4 stock version on the NPJS25.93-14-10 build with magisk 13.3 (to root) and it's running stably on my XT1642.
Thank you! Now its working as it should with the newest updates!
Thread can be closed. Thanks
stefanhanz said:
Thank you! Now its working as it should with the newest updates!
Thread can be closed. Thanks
Click to expand...
Click to collapse
Hello Friend
I would like to know if you can explain how to fix it is that the same happens to me the ap fastboot flash mode * secure * because before I had already used the blanckflash to revive it because first soo turned on the white led
sersrendon said:
Hello Friend
I would like to know if you can explain how to fix it is that the same happens to me the ap fastboot flash mode * secure * because before I had already used the blanckflash to revive it because first soo turned on the white led
Click to expand...
Click to collapse
Does anyone know what happened?
I updated the rom appeared this message.
Cell Phone: Moto g 4
Please help me :crying: :crying:
Imagens:
h t t p s:/ /goo.gl/nupYsT
h t t p s:/ /goo.gl/G8KNNV
Rog Ballester said:
Does anyone know what happened?
I updated the rom appeared this message.
Cell Phone: Moto g 4
Please help me :crying: :crying:
Imagens:
h t t p s:/ /goo.gl/nupYsT
h t t p s:/ /goo.gl/G8KNNV
Click to expand...
Click to collapse
Looks like you've used the blankflash and your device is in the temporary bootloader, waiting for a stock firmware flash to repair.
You could flash the latest December 2017 stock firmware here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
You do not have to use the OEM lock commands whilst flashing. Also, be aware this flashing procedure will erase your device. As always, if this works please do not flash older stock firmwares if you can, else you may hard brick again.
echo92 said:
Looks like you've used the blankflash and your device is in the temporary bootloader, waiting for a stock firmware flash to repair.
You could flash the latest December 2017 stock firmware here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
You do not have to use the OEM lock commands whilst flashing. Also, be aware this flashing procedure will erase your device. As always, if this works please do not flash older stock firmwares if you can, else you may hard brick again.
Click to expand...
Click to collapse
Não estou conseguindo, de uma olhada nessas imagens por favor
https: / /goo.gl/nupYsT
https: / /goo.gl/G8KNNV
Rog Ballester said:
Não estou conseguindo, de uma olhada nessas imagens por favor
https: / /goo.gl/nupYsT
https: / /goo.gl/G8KNNV
Click to expand...
Click to collapse
1) please post in English in these forums.
2) the images load up okay, you may require a Facebook account to access after removing the spaces in the link.
3) again, from what I see in the pictures, it appears your device has been flashed with a temporary bootloader and requires a full firmware flash. The above stock ROM should work with XT1626 devices, you may wish to check the stock ROM thread to confirm.
Edit: here are a couple of reports suggesting the ROM works on XT1626 devices. https://forum.xda-developers.com/showpost.php?p=75139620&postcount=538 https://forum.xda-developers.com/showpost.php?p=75263192&postcount=573
echo92 said:
1) please post in English in these forums.
2) the images load up okay, you may require a Facebook account to access after removing the spaces in the link.
3) again, from what I see in the pictures, it appears your device has been flashed with a temporary bootloader and requires a full firmware flash. The above stock ROM should work with XT1626 devices, you may wish to check the stock ROM thread to confirm.
Edit: here are a couple of reports suggesting the ROM works on XT1626 devices. https://forum.xda-developers.com/showpost.php?p=75139620&postcount=538 https://forum.xda-developers.com/showpost.php?p=75263192&postcount=573
Click to expand...
Click to collapse
When I pass the firmware flash, it comes back on the same screen
Gets stuck
:crying::crying:
Rog Ballester said:
When I pass the firmware flash, it comes back on the same screen
Gets stuck
:crying::crying:
Click to expand...
Click to collapse
Can I ask how you're flashing the firmware?
Have you got your device connected to your computer via USB?
Does your device show on your computer, and do you have the stock ROM downloaded and extracted to your ADB folder?
When you flash, do you see [okay] after each command?
I'd like to see a copy of the flashing output if possible please
echo92 said:
Can I ask how you're flashing the firmware?
Have you got your device connected to your computer via USB?
Does your device show on your computer, and do you have the stock ROM downloaded and extracted to your ADB folder?
When you flash, do you see [okay] after each command?
I'd like to see a copy of the flashing output if possible please
Click to expand...
Click to collapse
Yes, I have the room files.
Yes, my computer recognizes
I had the bootloader unlocked, I went to update and it caught
please look at the pictures:
https://goo.gl/q7AHhL
https://goo.gl/QstpTS
https://goo.gl/JSz8r2
Rog Ballester said:
Yes, I have the room files.
Yes, my computer recognizes
I had the bootloader unlocked, I went to update and it caught
please look at the pictures:
https://goo.gl/q7AHhL
https://goo.gl/QstpTS
https://goo.gl/JSz8r2
Click to expand...
Click to collapse
Okay, what about the rest of the flashing output, from starting with the fastboot flash partition gpt... command? I only see the end of the commands with fastboot OEM lock and fastboot reboot, where's the important section?
Also, you may wish to replace the NPJS25.93-14-8 stock ROM you have with the NPJS25.93-14-13 stock ROM if you see pre flash validation or security downgrade errors.
echo92 said:
Okay, what about the rest of the flashing output, from starting with the fastboot flash partition gpt... command? I only see the end of the commands with fastboot OEM lock and fastboot reboot, where's the important section?
Also, you may wish to replace the NPJS25.93-14-8 stock ROM you have with the NPJS25.93-14-13 stock ROM if you see pre flash validation or security downgrade errors.
Click to expand...
Click to collapse
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
Do you believe you can recover your cell phone?
Rog Ballester said:
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
Do you believe you can recover your cell phone?
Click to expand...
Click to collapse
I saw security downgrade errors, suggesting the stock ROM you are trying to flash is too old. Pre flash validation errors indicate the same thing, your downloaded stock ROM is not new enough to repair your device.
Please download the newest NPJS25.93-14-13 stock ROM as linked previously, delete the old stock ROM you have and replace with the newer stock ROM. Then try again. With a locked bootloader, especially, this is crucial. The bootloaders will block any attempts to flash old firmware if locked, hence why your device is still not working.
I've not bricked my phone, this process has been shown to work for others though. In some cases, flashing newer firmware than what you had could work. You have the June 2017 build, the NPJS25.93-14-13 build is December 2017.
echo92 said:
I saw security downgrade errors, suggesting the stock ROM you are trying to flash is too old. Pre flash validation errors indicate the same thing, your downloaded stock ROM is not new enough to repair your device.
Please download the newest NPJS25.93-14-13 stock ROM as linked previously, delete the old stock ROM you have and replace with the newer stock ROM. Then try again. With a locked bootloader, especially, this is crucial. The bootloaders will block any attempts to flash old firmware if locked, hence why your device is still not working.
I've not bricked my phone, this process has been shown to work for others though. In some cases, flashing newer firmware than what you had could work. You have the June 2017 build, the NPJS25.93-14-13 build is December 2017.
Click to expand...
Click to collapse
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
I wanted to thank you from the bottom of my heart. I got it sorted. Thank you so much for helping me. :good::fingers-crossed:
Rog Ballester said:
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
I wanted to thank you from the bottom of my heart. I got it sorted. Thank you so much for helping me. :good::fingers-crossed:
Click to expand...
Click to collapse
You're welcome
Please, in future, avoid downgrading your stock firmware if you can. If you do downgrade stock firmware, avoid OTA updates. Custom ROMs do not appear to matter in this regard.
I do not know if blankflashes will keep working as Motorola keeps updating the stock firmware. We may eventually need a new blankflash. Blankflashes are also rare as Motorola does not formally release them (luckily, we have a working one). So, do not rely on a blankflash to always bail you out of trouble.
stefanhanz said:
Thank you. When I connect my phone, I get the message on my phone "USB Connected" and in the windows device manager there comes an Android Device "Motorola ADB Interface" (official Lenovo driver). I also tried to install the *.inf file (downloaded it as you told), but there is no difference.
I tried the "blankflash" https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But I get the same message in cmd as always. < waiting for device > I dont know what to do..
edit: I got the message when I tried the blankflash.bat. Now I tried to install TWRP with fastboot and it worked!
Tanks alot!
Now, I want to install the lastest stock ROM. In the meantime I downloaded this version "ATHENE_NPJS25.93-14-8".
Do I have to install anything else like a boot.img? I made a full wipe..
Can I use the ElementalX Kernel?
Click to expand...
Click to collapse
How did you installed twrp can you help me out please i am stuck on ap fastboot flash mode (secure)
with no rom and no recovery can you please help me? how will i get out of this situation? Please!
ILLUSORYINK said:
How did you installed twrp can you help me out please i am stuck on ap fastboot flash mode (secure)
with no rom and no recovery can you please help me? how will i get out of this situation? Please!
Click to expand...
Click to collapse
How did you get into this state in the first place?
I see from your other post you installed AICP, so you must have TWRP on your device already?
If you need to re-flash TWRP, then boot your device to the bootloader.
Connect your device to your computer, preferably with the original USB cable.
Open the ADB terminal on your computer, and ensure you have the TWRP flashable image on your computer, in your ADB folder.
In the ADB terminal, type 'fastboot devices' without quotes, ensure you get a serial number response from your device.
If you get a response, then type 'fastboot flash recovery <name of TWRP image>' without quotes, where the <name of TWRP image> is the TWRP image file name as on your computer. Ensure the file name is the same, taking into account file name extensions.
You should have flashed TWRP to your recovery partition on your device - use the volume keys on your device to select 'Recovery' then press the power button to boot to recovery. You should be booting to TWRP recovery.
In there, you should be able to copy a custom ROM and flash that within TWRP. Alternatively, you could download a fastboot stock ROM and flash that within fastboot (not TWRP) to restore your device, but ensure it's the correct and latest stock ROM for your device.
I have Moto g5 plus xt 1686 Indian variant.I hadn't unlocked my bootloader. The device was working but suddenly one day it got bricked dont know why but it boots only in fastboot mode that to with no information.The only error i am able to verify is "failed to validate boot image"
After trying for around 1 week i have tried these things
1. Used rsd lite earlier it wasnot able to identify my device in windows 10 machine but in windows 7 machine its able to do that but unable to flash the device
2. tried to flash using adb commands but they are also not working
Since i tried to unlock the bootloader through the guide of motorola website then also i am not able to do that and get this error "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
Please help ....
Anubhav074 said:
I have Moto g5 plus xt 1686 Indian variant.I hadn't unlocked my bootloader. The device was working but suddenly one day it got bricked dont know why but it boots only in fastboot mode that to with no information.The only error i am able to verify is "failed to validate boot image"
After trying for around 1 week i have tried these things
1. Used rsd lite earlier it wasnot able to identify my device in windows 10 machine but in windows 7 machine its able to do that but unable to flash the device
2. tried to flash using adb commands but they are also not working
Since i tried to unlock the bootloader through the guide of motorola website then also i am not able to do that and get this error "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
Please help ....
Click to expand...
Click to collapse
You need to install fastboot in pc and then flash the device to make it work.
You can prefer this thread
https://forum.xda-developers.com/g5...-flash-stock-romfactory-t3691396/post74221633
Anubhav074 said:
I have Moto g5 plus xt 1686 Indian variant.I hadn't unlocked my bootloader. The device was working but suddenly one day it got bricked dont know why but it boots only in fastboot mode that to with no information.The only error i am able to verify is "failed to validate boot image"
After trying for around 1 week i have tried these things
1. Used rsd lite earlier it wasnot able to identify my device in windows 10 machine but in windows 7 machine its able to do that but unable to flash the device
2. tried to flash using adb commands but they are also not working
Since i tried to unlock the bootloader through the guide of motorola website then also i am not able to do that and get this error "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
Please help ....
Click to expand...
Click to collapse
You cannot unlock bootloader anymore. So try flashing normally. If your hardware is not damaged then you might me able to make it work.
debdeep98 said:
You cannot unlock bootloader anymore. So try flashing normally. If your hardware is not damaged then you might me able to make it work.
Click to expand...
Click to collapse
Since it is booting into fastboot mode i dont think its damaged.But the problem is its my first time for flashing so i dont know very much about it.
What i know is that , i installed adb in my system ,and then through command prompt i tried to detect my device But its not getting detected.So if you can please provide me a brief guide for flashing phone.
Anubhav074 said:
Since it is booting into fastboot mode i dont think its damaged.But the problem is its my first time for flashing so i dont know very much about it.
What i know is that , i installed adb in my system ,and then through command prompt i tried to detect my device But its not getting detected.So if you can please provide me a brief guide for flashing phone.
Click to expand...
Click to collapse
K.. install adb(https://www.androidfilehost.com/?fid=745425885120698566 ). If you had installed moto assistant then you'll have the drivers. If not then google motorola drivers and install them(http://www.motorola.com/getmdmwin ).
Once it's done. Open the folder where adb is installed.
Hold shift and right click>open command promt here.
At this point boot into the bootloader on your phone (fastboot mode).
On cmd type fastboot devices.
If your device is detected then it will show on screen.
If you get to this part.
Start flashing thru fastboot.
Get the files from google( or https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL)
Instructions to flash are in xda.
If you get failed to flash: security version downgrade then you're probably flashing an older firmware. Download the latest.
If you get failed to flash: preflash validation failed then there's not much you can do. Or atleast i don't know a solution to that.
its not detecting my device
Actually the problem is that it is not detecting my device when i give this command, although i have installed device drivers and adb also....This is is the problem
Anubhav074 said:
Actually the problem is that it is not detecting my device when i give this command, although i have installed device drivers and adb also....This is is the problem
Click to expand...
Click to collapse
Did you lenovo moto smart assistant to flash the device, you can try that as it will flash the device for you.
riyan65 said:
Did you lenovo moto smart assistant to flash the device, you can try that as it will flash the device for you.
Click to expand...
Click to collapse
yeah i tried that but when it is not verifying my phone when i select id (which is xt 1686) it says that phone can not be verified try again.i have tried every given id but it is refusing to accept my device.
Anubhav074 said:
Since it is booting into fastboot mode i dont think its damaged.But the problem is its my first time for flashing so i dont know very much about it.
What i know is that , i installed adb in my system ,and then through command prompt i tried to detect my device But its not getting detected.So if you can please provide me a brief guide for flashing phone.
Click to expand...
Click to collapse
Here's a guide to flash stock firmware.
Try the linked Mini ADB & Fastboot, if your device isn't recognised try to connect it to another usb port or use another usb cable.
Are you sure that you're in fastboot mode when you type the commands?
Read the guide carefully.
You need:
Latest signed stock firmware:
Europe (RETEU):
https://drive.google.com/file/d/13WuhoogtAdoincAyTwCLvRj0d-Z9kL0P/view?usp=sharing
India (RETIN):
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
US (RETUS):
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
flashallO.bat:
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
Motorola drivers:
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view?usp=sharing
Mini ADB & Fastboot
https://drive.google.com/file/d/1lLYfimKN1U5CJ9cfpTCkhtMiuG8EfXBZ/view?usp=sharing
1) Download the 8.1.0_OPS28.85-17-6-2 Indian firmware (it's the last one for the Moto G5+ (potter).
2) Install Mini ADB & Fastboot (best place is the root directory of C:/ or how the partition/hard drive is named where your OS resists), not in program files or another folder.
3) Extract the firmware to that ADB & Fastboot folder.
4) Download my "flashallO.bat" and move it to that folder too.It removes the need for you to manually flash all partitions, just double-click it and it'll run all the commands for you.
5) Download and install Motorola device drivers.The program is called "Motorola Device Manager".
6) Reboot your phone to the bootloader. To do this, turn it off, then hold down the power and volume down buttons until you see a bugdroid undergoing open-heart surgery.
7) Connect the phone to your PC with your USB cable. Type
Code:
fastboot devices
to check if your device is connected. A serial number should be shown.
8) Run the flashallO.bat script. (Caution: This will wipe your device completely!) It will take some time to flash, just be patient and don't worry.
NOTE: If the command window appears for a brief moment then disappears, device drivers may not be installed. Ask again then.
9) Once the command window closes, it should have completed the flashing process and you are safe to press the power key on the phone to start Android. Just make sure that the text near the buttons reads "START".
Sent from my Moto G5 Plus using XDA Labs
Followed your guide this time my device is getting detected and when typed command adb devices its giving some number also but the image you provided is not flashing it.Dont know why please help
Anubhav074 said:
Followed your guide this time my device is getting detected and when typed command adb devices its giving some number also but the image you provided is not flashing it.Dont know why please help
Click to expand...
Click to collapse
You're always talking about ADB commands, it's Fastboot that you have to use, it's described above how you get there.
What image do you mean when you say it's not flashing?
The guide is complete, read it carefully.
You have to download a zip file, in your case the Indian (RETIN) variant:
XT1686_POTTER_RETIN_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unpack it to fastboot folder, use the flashallO.bat to flash the firmware.
Please clarify what image you're talking about and if you do the fastboot flash like described above please provide the recovery.log , you can do that in TWRP->advanced->copy log, if TWRP is installed.
Try to flash the firmware and immediately after that grab a log and attach it here.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
You're always talking about ADB commands, it's Fastboot that you have to use, it's described above how you get there.
What image do you mean when you say it's not flashing?
The guide is complete, read it carefully.
You have to download a zip file, in your case the Indian (RETIN) variant:
XT1686_POTTER_RETIN_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unpack it to fastboot folder, use the flashallO.bat to flash the firmware.
Please clarify what image you're talking about and if you do the fastboot flash like described above please provide the recovery.log, you can do that in TWRP->advanced->copy log, it will be stored in your internal storage.
Try to flash the firmware and immediately after that grab the log (with TWRP file manager) and attach it here.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Sry it's fastboot not adb .But the image i am trying to use is indian(retin) as you provided.And i followed all steps as they were given.
But i dont know how to get log files.
Also i would like to mention that this is my first time trying flashing a phone and as per my knowledge we have to install twrp recovery which i haven't done.its a normal phone with locked oem.
So please guide me how to get log files.
Anubhav074 said:
Sry it's fastboot not adb .But the image i am trying to use is indian(retin) as you provided.And i followed all steps as they were given.
But i dont know how to get log files.
Also i would like to mention that this is my first time trying flashing a phone and as per my knowledge we have to install twrp recovery which i haven't done.its a normal phone with locked oem.
So please guide me how to get log files.
Click to expand...
Click to collapse
You don't need logs. Your phone is locked so you cannot flash twrp. Only thing you can do is flash using fastboot commands. Just download the firmware.. extract. Put all of those files in the adb folder and run the flashall.bat or individual commands like fastboot flash recovery recovery.img which ever you feel is easier for you.
Anubhav074 said:
Sry it's fastboot not adb .But the image i am trying to use is indian(retin) as you provided.And i followed all steps as they were given.
But i dont know how to get log files.
Also i would like to mention that this is my first time trying flashing a phone and as per my knowledge we have to install twrp recovery which i haven't done.its a normal phone with locked oem.
So please guide me how to get log files.
Click to expand...
Click to collapse
debdeep98 said:
You don't need logs. Your phone is locked so you cannot flash twrp. Only thing you can do is flash using fastboot commands. Just download the firmware.. extract. Put all of those files in the adb folder and run the flashall.bat or individual commands like fastboot flash recovery recovery.img which ever you feel is easier for you.
Click to expand...
Click to collapse
That´s what I´ve said. If you would have TWRP you would be able to send a recovery.log but all you want to do is to flash a signed fastboot firmware. That´s possible without TWRP or unlocked bootloader, just by fastboot. Unzip the indian firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
into your Mini ADB & Fastboot folder, place the flashallO.bat there too and double-click it, everything in fastboot mode as described before.
What happens when you do that? Are the commands executed in the command window of your Windows PC?
Can you make a screenshot of it? The guide I posted has everything you need in it, you have to tell me what happens when you try to flash the unzipped firmware.
Just to be clear, the firmware and everything has to be on your PC, not your moble device!
i tried to take screen shot of it but was unable to do it but was successful in copying the complete commands log in text file so here it is
View attachment batch.txt
Anubhav074 said:
i tried to take screen shot of it but was unable to do it but was successful in copying the complete commands log in text file so here it is
Click to expand...
Click to collapse
Ok, that doesn't look to good.
The whole process is failing right at the start when the device is trying to build the partition table.
Have you tried different USB cables and ports?
Imo there are only two possible solutions:
Your device isn't working with fastboot correctly or its a hardware failure, the eMMC (the internal SD) may be corrupted. As your device is locked and hasn't been modded in any way this is the most plausible scenario also because it crashed out of the blue.
The only thing you can try yet is to use a different ADB and Fastboot tool, this one for example:
Minimal ADB & Fastboot:
https://drive.google.com/file/d/10NEzpxKpYWfq-HdK42ctwoEnCg-BfsRQ/view?usp=drivesdk
If all that changing of ports, cables and tools doesn't help you have to bring your device to a service center, they will most probably change the motherboard which isn't a cheap repair so if your device isn't under guarantee anymore you have to consider it it's worth the money.
Good luck!
Sent from my Moto G5 Plus using XDA Labs
So i tried with different fastboot software which you provided but i get the same errors .On phone when these commands run i get these messages failed to validate bootloader image and some thing called piv is also not able to be validated.
So i think its the end of my testing journey. Now can you please tell me how much chances are there for software issue. And is there any thing else i could.Any way i got to learn so many things through this but if is there anything left. Or should i go to service center
Anubhav074 said:
So i tried with different fastboot software which you provided but i get the same errors .On phone when these commands run i get these messages failed to validate bootloader image and some thing called piv is also not able to be validated.
So i think its the end of my testing journey. Now can you please tell me how much chances are there for software issue. And is there any thing else i could.Any way i got to learn so many things through this but if is there anything left. Or should i go to service center
Click to expand...
Click to collapse
I think you've done everything that's possible.
The device wasn't rooted,modded,unlocked or something.
It showed the failure out of the blue.
You tried different fastboot tools, cables, ports and the correct firmware.
I asked someone with more knowledge about your log and the whole case and he is thinking the same as I do.
So the chance for a software problem is really small. I told you everything I know, maybe a service center has more options for software checks but as far as I know they use the good old Lenovo Motorola Software Assistant.
So I would recommend to go there and ask (before they do anything) what you have to pay if your eMMC is broken. Here in Germany they always change the whole motherboard, the costs are about the half of the price you paid for the device here.
If your still under guarantee it's a different story.
I'm sorry, I told you everything I know and I flashed my Moto G5+ several times.
My opinion is that the device has a hardware failure and visiting the service center is the only thing you could do now.
I really would like to give you better news.
Sent from my Moto G5 Plus using XDA Labs
Hi, please help.
I have factory unlocked Moto G5 plus. I never did anyrhing to. All factory.
Recently its stuck in bootloop.
I really want to save all my pictures and texts.
Please help
Thanks
phone crazy said:
Hi, please help.
I have factory unlocked Moto G5 plus. I never did anyrhing to. All factory.
Recently its stuck in bootloop.
I really want to save all my pictures and texts.
Please help
Thanks
Click to expand...
Click to collapse
Read this thread. You can flash signed Motorola firmware like discribed. If you don't want to lose your data you can try to omit the "erase user data" command. Just delete it out of the flashallO.bat.
https://forum.xda-developers.com/g5...ked-stuck-fastboot-mode-t3996599/post80792213
Sent from my Moto G5 Plus using XDA Labs
UPDATE:
I successfully unlocked the bootloader, flashed twrp, rooted, updated kernel and roms, tweaking gpu cpu for performance in pubg etc, greenify, flashify, power nap everything.
xposed framework take you in bootloop for this device.
now i am on kernel mk2000, superv20 rom, h91810u, 7 nougat.
if in future anyone feels any problem i am always here.
remember: linus is your friend for this device, and windows 10 suck.
and
sudo $(which fastboot) did miracles for me....
old post:
Hello everyone.
i am new here and i am sorry in advance if i did something wrong. i will come directly to the point.
model number: LG V20 T-MOBILE VERSION, H91820H, NON USA, Currently on oreo android 8.
we are not talking about any kind of roms kernels roots or anything here. just a simple question. " can this model's boot loader be unlocked ? like ever ? or not "
cause i have tried everything, when i say everything i mean everything. followed several posts on internet videos on you tube posts on XDA, tried using multiple PCs, multiple data cables, multiple drivers but for some reason i don't know what, this model's boot loader cannot be unlocked.
THE ERROR:
<WAITING FOR DEVICE> till eternity.
what i have done till now ?
1. lg drivers installed.
2. adb drivers installed with adb fastboot files.
3. updating legacy android adb interface driver, done.
4. went in to boot loader then connected the data cable and updated driver, done.
5. usb debugging oem unlock options activated, done.
6. restarted pc multiple times to update drivers, done.
we all know all it takes is 3 easy commands to unlock bootlaoder
adb reboot bootloader
fastboot oem unlock
fastboot reboot
but in my case i always stuck at 2nd command. waiting for device is shown and nothing happens.
then i ran command, adb devices>> it shows
List of devices attached
adb server is out of date. killing...
* daemon started successfully *
LGH9182bfc6bdc device
next i put the command, fastboot devices and nothing is shown i just go to the next line... c:\adb>
so this is for sure that my device is not connected to the fastboot.
now my only question is, can this device bootloader unlock or not ? so that i stop pushing my limits.
any help will be appreciated.
regards.
X_BlackBurn_X said:
Hello everyone.
i am new here and i am sorry in advance if i did something wrong. i will come directly to the point.
model number: LG V20 T-MOBILE VERSION, H91820H, NON USA, Currently on oreo android 8.
we are not talking about any kind of roms kernels roots or anything here. just a simple question. " can this model's boot loader be unlocked ? like ever ? or not "
cause i have tried everything, when i say everything i mean everything. followed several posts on internet videos on you tube posts on XDA, tried using multiple PCs, multiple data cables, multiple drivers but for some reason i don't know what, this model's boot loader cannot be unlocked.
THE ERROR:
<WAITING FOR DEVICE> till eternity.
what i have done till now ?
1. lg drivers installed.
2. adb drivers installed with adb fastboot files.
3. updating legacy android adb interface driver, done.
4. went in to boot loader then connected the data cable and updated driver, done.
5. usb debugging oem unlock options activated, done.
6. restarted pc multiple times to update drivers, done.
we all know all it takes is 3 easy commands to unlock bootlaoder
adb reboot bootloader
fastboot oem unlock
fastboot reboot
but in my case i always stuck at 2nd command. waiting for device is shown and nothing happens.
then i ran command, adb devices>> it shows
List of devices attached
adb server is out of date. killing...
* daemon started successfully *
LGH9182bfc6bdc device
next i put the command, fastboot devices and nothing is shown i just go to the next line... c:\adb>
so this is for sure that my device is not connected to the fastboot.
now my only question is, can this device bootloader unlock or not ? so that i stop pushing my limits.
any help will be appreciated.
regards.
Click to expand...
Click to collapse
Are you following this > https://r.tapatalk.com/shareLink/to...3&share_fid=3793&share_type=t&link_source=app
[ROOT] - lafsploit - H918 (any version up to and including 20h) - now n00b friendly
Sent from my HD1907 using Tapatalk
Thanks for thanks for replying on a short notice I have seen this post there is no reason to follow any of the post because the very first stage is to unlock the bootloader but as I cannot unlock the bootloader there is no point in following any of the posts my problem is what ever way I follow I am unable to to unlock the bootloader in fact what I can see is whenever I try to type in command ADB devices IC e my phone but when I type fastboot devices nothing happens it's like my phone is not in the fastboot that is why why I cannot unlock the bootloader I have tried every possible step mentioned on the internet and on various forums I also go through some videos on YouTube those guys follow the same steps and unlock their bootloader but my device cannot unlock for some reason so if you lovely people can help me out and figure out what exactly I am doing wrong as I have followed every step of unlocking the bootloader I've installed all the drivers I have updated all the drivers I have done exactly e all three steps which has been asked but still no luck thank you
clsA said:
Are you following this > https://r.tapatalk.com/shareLink/to...3&share_fid=3793&share_type=t&link_source=app
[ROOT] - lafsploit - H918 (any version up to and including 20h) - now n00b friendly
Sent from my HD1907 using Tapatalk
Click to expand...
Click to collapse
To be very precise after following the first step while unlocking the bootloader in the second step when we type fast boot devices it should show some hexadecimal numbers and it should confirm us that our device is in the fastboot mode but in my case whenever I type this command nothing happens that means my device is not recognised to go in the bootloader this is the main problem there is no point in following any of the posts if you cannot complete the very first stage of unlocking your bootloader if you can figure out what exactly is the problem I will be thankful to you because I have followed every step possible I've updated every ADB drivers LG drivers but nothing is helping out as even before starting the procedure of unlocking the bootloader my device is not going in the fast boot also I noticed one thing when I try to go inside the bootloader screen before that in my device manager it is shown as composit device but after that I think it gets disconnected fastboot oem unlock cannot work as it gives a message of waiting for the device after going are using the command ADB reboot bootloader so my problem is the command fastboot oem unlock is pretty useless as it waits for the device and it's stuck there forever please help me out if you can I will be thankful to you regards
X_BlackBurn_X said:
To be very precise after following the first step while unlocking the bootloader in the second step when we type fast boot devices it should show some hexadecimal numbers and it should confirm us that our device is in the fastboot mode but in my case whenever I type this command nothing happens that means my device is not recognised to go in the bootloader this is the main problem there is no point in following any of the posts if you cannot complete the very first stage of unlocking your bootloader if you can figure out what exactly is the problem I will be thankful to you because I have followed every step possible I've updated every ADB drivers LG drivers but nothing is helping out as even before starting the procedure of unlocking the bootloader my device is not going in the fast boot also I noticed one thing when I try to go inside the bootloader screen before that in my device manager it is shown as composit device but after that I think it gets disconnected fastboot oem unlock cannot work as it gives a message of waiting for the device after going are using the command ADB reboot bootloader so my problem is the command fastboot oem unlock is pretty useless as it waits for the device and it's stuck there forever please help me out if you can I will be thankful to you regards
Click to expand...
Click to collapse
Did you downgrade to software version H91810P? Because that should be the first thing you have to do to get everything else to work afterwards.
C D said:
Did you downgrade to software version H91810P? Because that should be the first thing you have to do to get everything else to work afterwards.
Click to expand...
Click to collapse
Thanks for the reply.
Can you please clear me one thing. To downgrade from h91820h to h91810p you need to unlock bootloader if i am not wrong. And in that case we will be back to square 1.
Its not about installing custom rom kernel recovery root or anything. Its only about unlocking the bootloader which i cannot do.
I hope you understand my pain.
I just want to unlock my bootloader thats it.
It used only 3 commands.
1. Adb devices - shows my device.
2. Fastboot devices - no fastboot device found.
This is the problem. When you cannot find any fastboot device even updating driver by going inside the bootloader the entire mission gets failed.
I cant find any solution for this. I dont know for what reason my device cannot be listed in fastboot mode.
X_BlackBurn_X said:
Thanks for the reply.
Can you please clear me one thing. To downgrade from h91820h to h91810p you need to unlock bootloader if i am not wrong. And in that case we will be back to square 1.
Its not about installing custom rom kernel recovery root or anything. Its only about unlocking the bootloader which i cannot do.
I hope you understand my pain.
I just want to unlock my bootloader thats it.
It used only 3 commands.
1. Adb devices - shows my device.
2. Fastboot devices - no fastboot device found.
This is the problem. When you cannot find any fastboot device even updating driver by going inside the bootloader the entire mission gets failed.
I cant find any solution for this. I dont know for what reason my device cannot be listed in fastboot mode.
Click to expand...
Click to collapse
fastboot doesn't work when the phone is booted up
adb reboot bootloader
followed by fastboot devices
Note: flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP
Example:
D:\fastboot>adb devices
List of devices attached
LGUS99740047103 device
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot oem device-id
...
(bootloader) ----------------------------------
(bootloader) Device-ID
(bootloader) F3D7DE171C893D55082EAE38270125EF
(bootloader) DA7CB3E78B1DB5709A2CA8********
(bootloader) ----------------------------------
OKAY [ 0.060s]
finished. total time: 0.060s
D:\fastboot>fastboot reboot
rebooting...
finished. total time: 0.008s
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot getvar unlocked
unlocked: no
finished. total time: 0.003s
Click to expand...
Click to collapse
X_BlackBurn_X said:
Thanks for the reply.
Can you please clear me one thing. To downgrade from h91820h to h91810p you need to unlock bootloader if i am not wrong. And in that case we will be back to square 1.
Its not about installing custom rom kernel recovery root or anything. Its only about unlocking the bootloader which i cannot do.
I hope you understand my pain.
I just want to unlock my bootloader thats it.
It used only 3 commands.
1. Adb devices - shows my device.
2. Fastboot devices - no fastboot device found.
This is the problem. When you cannot find any fastboot device even updating driver by going inside the bootloader the entire mission gets failed.
I cant find any solution for this. I dont know for what reason my device cannot be listed in fastboot mode.
Click to expand...
Click to collapse
As clsA said, flashing firmware does not require an unlocked bootloader.
Look at parts 1 and 2 of the other step by step guide here:
https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
clsA said:
fastboot doesn't work when the phone is booted up
adb reboot bootloader
followed by fastboot devices
Note: flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP
Example:
Click to expand...
Click to collapse
Thanks for the solution. May be this is it. All the time i have been doing it wrong.
Solution : flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP.
I will downgrade from 20h to 10p now and will give you feedback on this soon. Thanks a ton for showing a noob like me the right direction to work.
X_BlackBurn_X said:
Thanks for the solution. May be this is it. All the time i have been doing it wrong.
Solution : flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP.
I will downgrade from 20h to 10p now and will give you feedback on this soon. Thanks a ton for showing a noob like me the right direction to work.
Click to expand...
Click to collapse
No problem the link @C D posted above seems to have all the working links for you
clsA said:
No problem the link @C D posted above seems to have all the working links for you
Click to expand...
Click to collapse
well we have a new problem now.
lgup error 0x2bc invalid command response code = 0x80000202 at 4 percent while flashing.
did i just brick my phone now ? as it says dont unplug until you are done and we have been getting same error again and again.
used the provided kdz file flashing as an upgrade.
ok so the new problem is... may be i was trying to flash h91810p naugaut on to a oreo h91820h
and if i am not wrong at this stage i messed up pretty bad my phone is stuck in donwload mode wont boot up and i need to flash back 20h again to get out of this mess. can anyone hlp me ....
i just wanna know h91810p downgrading from 91820h is possible or not ? cause one is naugaut and one is oreo.
UPDATE:
i was flashing wrong h91810p thats why it was showing error. on another website i got the file compatible to my phone t mobile version and flash was successful.
now i am on h91810p software version andriod 7.
problem UPDATE:
i still cant unlock bootloader. same problem as before downgrading from h91820h.
adb devices shows device.
adb reboot bootloader
fastboot devices gives no result.
phone cannot enter in fastboot mode. the problem still remains the same even after changing the software.
kindly help guys
clsA said:
fastboot doesn't work when the phone is booted up
adb reboot bootloader
followed by fastboot devices
Note: flashing the 10p kdz does not require the bootloader be unlocked
it requires you have patched LGUP
Example:
Click to expand...
Click to collapse
hello clsA
"
D:\fastboot>adb devices
List of devices attached
LGUS99740047103 device
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot oem device-id
after this it only says waitng for device"
now i am on h91810p as i was instructed. can you please help.
its all happening the same way it was happening when was on h91820h.
fastboot devices cannot be found.
once it reboots in bootloader then it should detect a fastboot device but it doesnot and adb is also lost there.
kindly help.
NEW UPDATE:
my lg v20 now on software h91810p is actually a T MOBILE version. and when i researched more about it i found out T MOBILE deliberately locks the boot loader of many devices and its unlockable.
possible work around can be if the software version installed on your phone can some how be an international version of your ROM, then only you can unlock the bootloader else none of your commands will work. now i am trying to flash this phone using an international ROM version if i succeed i will update. but according to my knowledge flashing other roms other than t mobile ones will definitely give errors in LGUP.
X_BlackBurn_X said:
NEW UPDATE:
my lg v20 now on software h91810p is actually a T MOBILE version. and when i researched more about it i found out T MOBILE deliberately locks the boot loader of many devices and its unlockable.
possible work around can be if the software version installed on your phone can some how be an international version of your ROM, then only you can unlock the bootloader else none of your commands will work. now i am trying to flash this phone using an international ROM version if i succeed i will update. but according to my knowledge flashing other roms other than t mobile ones will definitely give errors in LGUP.
Click to expand...
Click to collapse
Do not flash another model's firmware onto the H918! Doing so will permanently brick your phone. The H918 in particular is incompatible with all other variants' software. Also, flashing H918 firmware onto any other model will also brick that phone.
C D said:
Do not flash another model's firmware onto the H918! Doing so will permanently brick your phone. The H918 in particular is incompatible with all other variants' software. Also, flashing H918 firmware onto any other model will also brick that phone.
Click to expand...
Click to collapse
hello
thanks for the reply.
i know we cannot flash any other phones firmware on to this model.
i was thinking of flashing specifically lg v20 h91810p international stock firmware, one is t mobile and one is international stock rom of same model.
cause t mobile is not allowing me to unlock the bootloader but an international stock rom will.
i have seen people doing on t mobile on youtube videos i dont know how they are doing it.
my problem is :
" as in message sent to various senior on this topic"
LG V20 H91810P, T MOBILE BOOTLOADER CANNOT BE UNLOCKED
HELLO
can you please help me out on a quest to unlock my bootloader of lg v20 h91810p. i have downgraded from h91820h to h91810p and still all the adb commands fail to make my phone go in to fastboot mode. i just cannot enter in fastboot mode,
adb devices shows my device
|but fastboot devices in bootloader mode doesnot show my device at all.
updated all the drivers used multiple pcs usb ports but no luck at all.,
what am i possibly doing wrong can you please help me out? i will be thankful to you.
on a side note i think t mobile has lockedd my bootloader so that i canoot unlock it,
regards
X_BlackBurn_X said:
hello
thanks for the reply.
i know we cannot flash any other phones firmware on to this model.
i was thinking of flashing specifically lg v20 h91810p international stock firmware, one is t mobile and one is international stock rom of same model.
cause t mobile is not allowing me to unlock the bootloader but an international stock rom will.
i have seen people doing on t mobile on youtube videos i dont know how they are doing it.
my problem is :
" as in message sent to various senior on this topic"
LG V20 H91810P, T MOBILE BOOTLOADER CANNOT BE UNLOCKED
HELLO
can you please help me out on a quest to unlock my bootloader of lg v20 h91810p. i have downgraded from h91820h to h91810p and still all the adb commands fail to make my phone go in to fastboot mode. i just cannot enter in fastboot mode,
adb devices shows my device
|but fastboot devices in bootloader mode doesnot show my device at all.
updated all the drivers used multiple pcs usb ports but no luck at all.,
what am i possibly doing wrong can you please help me out? i will be thankful to you.
on a side note i think t mobile has lockedd my bootloader so that i canoot unlock it,
regards
Click to expand...
Click to collapse
Did you make the Linux USB boot stick
Are you following the guide at all?
PART 3: CREATING A BOOTABLE LINUX USB USING FWUL
DOWNLOAD FWUL_v2.7_x86_64_15GB.zip FROM THE LINK BELOW AND EXTRACT THE IMAGE FILE SOMEWHERE IN YOUR PC.
https://androidfilehost.com/?w=files&flid=214529
DOWNLOAD RUFUS FROM BELOW AND INSTALL
https://rufus.akeo.ie/
INSERT A PEN DRIVE IN YOUR PC AND RUN RUFUS.
INSIDE RUFUS SELECT THE IMAGE FILE AND SELECT START (AFTER SELECTING START SELECT DD MODE IN THE DIALOGUE BOX) TO CREATE A BOOTABLE PEN DRIVE (WARNING: THIS WOULD FORMAT YOUR PEN DRIVE)
NOW YOU SHOULD BOOT YOUR PC FROM THE BOOTABLE USB STICK WHICH YOU HAVE JUST CREATED
THIS WOULD MAKE YOUR PC RUN LINUX OS
TYPE PASSWORD AS linux AND ENTER
Sent from my HD1907 using Tapatalk
clsA said:
Did you make the Linux USB boot stick
Are you following the guide at all?
PART 3: CREATING A BOOTABLE LINUX USB USING FWUL
DOWNLOAD FWUL_v2.7_x86_64_15GB.zip FROM THE LINK BELOW AND EXTRACT THE IMAGE FILE SOMEWHERE IN YOUR PC.
https://androidfilehost.com/?w=files&flid=214529
DOWNLOAD RUFUS FROM BELOW AND INSTALL
https://rufus.akeo.ie/
INSERT A PEN DRIVE IN YOUR PC AND RUN RUFUS.
INSIDE RUFUS SELECT THE IMAGE FILE AND SELECT START (AFTER SELECTING START SELECT DD MODE IN THE DIALOGUE BOX) TO CREATE A BOOTABLE PEN DRIVE (WARNING: THIS WOULD FORMAT YOUR PEN DRIVE)
NOW YOU SHOULD BOOT YOUR PC FROM THE BOOTABLE USB STICK WHICH YOU HAVE JUST CREATED
THIS WOULD MAKE YOUR PC RUN LINUX OS
TYPE PASSWORD AS linux AND ENTER
Sent from my HD1907 using Tapatalk
Click to expand...
Click to collapse
thanks again for the showing me the right direction. i was talking about unlocking the bootloader in step 1.
i will go through your links and try to study this.
just one more question.
does this method unlocks the bootloader ?
if yes please reply yes i will be thankful to you.
i will follow this step now.
regards
X_BlackBurn_X said:
hello clsA
"
D:\fastboot>adb devices
List of devices attached
LGUS99740047103 device
D:\fastboot>adb reboot bootloader
D:\fastboot>fastboot oem device-id
after this it only says waitng for device"
now i am on h91810p as i was instructed. can you please help.
its all happening the same way it was happening when was on h91820h.
fastboot devices cannot be found.
once it reboots in bootloader then it should detect a fastboot device but it doesnot and adb is also lost there.
kindly help.
Click to expand...
Click to collapse
Why does adb show your device as a 997 which is the Sprint variant
Sent from my LG-H910 using XDA Labs