I installed minimal_adb_fastboot_v1.1.3_setup.exe after that i used
fastboot device command but stuck on waiting Device. what should i do??
Hi guys,
I am trying to flash the OEM info as its currently on according to DC unlocker:
Found Phone : VNS-L11
Model : Huawei HiSilicon Kirin Android phone
IMEI : 860921031654789
Firmware : VNS-C900B161
SIM Lock status : unlocked
my phone about device screen displays:
Model: HUAWEI VNS-L31
BUILD : VNS-L31C432B161
EMUI 4.1.1
ANDROID 6.0
I have downgraded to MM B161 thinking this will help and has factory reset my phone during the process but no luck.
I get a boot-loader unlocked warning since i was on nougat, and unable to lock or unlock the boot-loader when i try.
when trying to flash TWRP recovery i get: FAILED (remote: image verification error)
OEM UNLOCK is enabled and so is DEBUGGING
any ideas, really be great to get this fixed finally
Try to download again TWRP the use the command:
fastboot flash recovery twrp.img
Hello, after long time of googling, I found this website describing how to put both models of 2017 into fastboot mode
http://nv-tegra.nvidia.com/gitweb/?p=manifest/android/binary.git;a=blob_plain;f=README_NEW_SHIELD;hb=rel-24-uda-r1-partner
No thanks needed
Hi,
I just got this phone and tried to root it, but accidentally flashed the factory boot.img for the 4XL, and not the 4.
I am now stuck in Fastboot Mode and I am not able to get into recovery mode either.
I've tried downloading the correct Pixel 4's boot.img and flashing that, but to no avail.
Any help is appreciated as I am quite the noob.
The Fastboot screen reads:
Product revision: flame MP1.0(NA)
Bootloader version: c2f2-0.2-594065
Baseband version: g8150-00041-191016-B-5945070
Serial number: 9B161FFAZ0029R
Secure boot: PRODUCTION
NOS production: yes
DRAM 6GB Micron LPDDR4X
UFS: 64GB SKHyinx
Device state: unlocked
Boot slot: b
Enter reason: error boot prepare
Nevermind, I figured it out. I ran flash-all.bat
Hi all,
I have a Moto G5 Plus (dual sim, European version) that was on stock Android 8. I wanted to revive this old phone and use it for experimenting.
I unlocked the bootloader, installed TWRP recovery and then installed the unofficial Lineage OS 17.1 (here from xda: [ROM][UNOFFICIAL][10.0][POTTER] LineageOS 17.1).
I then proceeded to get root installed using no-verity and magisk.
I now have a boot loop that loads Lineage but then restarts into TWRP recovery.
It's been a really long time since I fooled around with bootloaders, recoveries and alternative roms (been using a Samsung S8 for several years now on stock rom).
So I am unsure how to proceed. What do you recommend that I do?
I would like to have a rooted Android 10 on the Moto G5 Plus, preferably without a bootloop
Update 1:
Using this thread I have been able to revert to stock Android 8.1 ROM: https://forum.xda-developers.com/showthread.php?t=2542219
But I would be interested to know which Android 10 ROM would be recommended for the Moto G5 Plus?
PartisanEntity said:
Hi all,
I have a Moto G5 Plus (dual sim, European version) that was on stock Android 8. I wanted to revive this old phone and use it for experimenting.
I unlocked the bootloader, installed TWRP recovery and then installed the unofficial Lineage OS 17.1 (here from xda: [ROM][UNOFFICIAL][10.0][POTTER] LineageOS 17.1).
I then proceeded to get root installed using no-verity and magisk.
I now have a boot loop that loads Lineage but then restarts into TWRP recovery.
It's been a really long time since I fooled around with bootloaders, recoveries and alternative roms (been using a Samsung S8 for several years now on stock rom).
So I am unsure how to proceed. What do you recommend that I do?
I would like to have a rooted Android 10 on the Moto G5 Plus, preferably without a bootloop
Update 1:
Using this thread I have been able to revert to stock Android 8.1 ROM: https://forum.xda-developers.com/showthread.php?t=2542219
But I would be interested to know which Android 10 ROM would be recommended for the Moto G5 Plus?
Click to expand...
Click to collapse
Problem; the procedure you followed is for a Moto G, and not a G5 Plus. If you used Moto G firmware on your Moto G5+, you may have induced more problems.
Moto g5+ firmwares are located at https://mirrors.lolinet.com/firmware/moto/potter/official/ Proper firmware for the Moto G5+ depends on your model and what country you are operating in.
potter - Moto G5 Plus = firmware
XT1680(LATAM/Argentina/Chile,2GB) {LATAM; Latin America}
XT1681(LATAM/Colombia/Mexico,2GB)
XT1683(Brazil,DS,DTV,2GB)
XT1684(Europe,3GB)
XT1685(Australia/NewZealand/Europe,3GB)
XT1686(India,3/4GB)
XT1687(USA,2GB/4GB)
{AMX, America Movil Mexico}{owns Claro}
{ATTMX; AT&T Mexico}
{AMZ; Amazon)
{RETAPAC; Retail Pacific; Australia, New Zealand}
{RETAR; Retail Argentina}
{RETBR; Retail Brazil}
{RETEU; Retail European Union)
{RETGB; Retail Great Britian}
{RETIN; Retail India}
{RETLA; Retail Latin America}
{RETMX; Retail Mexico}
{RETUS; Retail Unitied States}
{TEF, Telefonica S A.}
{TEFBR; Telefonica Brazil}
{TEFCO; Telefonica Columbia}
{TEFES; Telefonica European Sector}
{TEFMX; Telefonica Mexico}
Since your in Europe, your firmware group is probally RETEU, RETGB, or TEFES. You need to locate your model number of the phone, maybe a XT1684 or XT1685 and find the model number under the proper directory of firmware. I would download the latest, usually has 8.1.0_OPS28.85-17-6-2 in the firmware name and the lastest date. Extract the software and fastboot it.
For the 8.10_OPS28.85-17-6-2 firmwares the fastboot commands are:
Fastboot flash partition gpt.bin
Fastboot flash bootloader bootloader.img
Fastboot flash modem NON-HLOS.bin
Fastboot flash fsg fsg.mbn
Fastboot flash dsp adspso.bin
Fastboot flash logo logo.bin
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Fastboot flash system system.img_sparsechunk.2
Fastboot flash system system.img_sparsechunk.3
Fastboot flash system system.img_sparsechunk.4
Fastboot flash system system.img_sparsechunk.5
Fastboot flash system system.img_sparsechunk.6
Fastboot flash system system.img_sparsechunk.7
Fastboot flash system system.img_sparsechunk.8
Fastboot flash oem oem.img
Fastboot erase cache
Fastboot erase userdata
Fastboot erase DDR
Fastboot reboot
Again, this may not work because if the Moto G firmware you flashed on to the Moto G5+.....
Also, did LineageOS work on the phone before flashing Magisk and/or no-verity ?
Hi, thank you for your help.
Yes Lineage OS did work. Was it Magisk or no-verity that caused the bootloop?
So, I went to the proper stock ROM, and then I installed the Pixel Experience: https://download.pixelexperience.org/potter - so far nice and stable.
What is the commended/cleanest/safest way to get root?
PartisanEntity said:
Hi, thank you for your help.
Yes Lineage OS did work. Was it Magisk or no-verity that caused the bootloop?
So, I went to the proper stock ROM, and then I installed the Pixel Experience: https://download.pixelexperience.org/potter - so far nice and stable.
What is the commended/cleanest/safest way to get root?
Click to expand...
Click to collapse
Sorry to not reply earlier - was tied up with election recounts -----
Do not know what caused the boot loop. The proper way to install is to install LineagrOS first, boot LineageOS and make sure it comes up, Then go back to recovery/TWRP and install Magisk and the reboot to system and check LineageOS to make sure it came up. Then look in your apps and see if you have the Magisk icon. On the no-verity, I had a couple that did not work, I was turned on to Disable_Dm-Verity_ForcedEncrypt_02.04.2019.zip at
https://androidfilehost.com/?fid=11410963190603877244 (by WolfCity - thanks)
which worked for me. Use the procedure at paragraph 13 (my procedure that I listed
a PDF, its at http://s000.tinyupload.com/?file_id=...86655137330218 ) to install the program to decrypt the file system. Then reboot the phone and verify the phone is un-encrypted (it will say "Encrypt Phone" instead of Phone Encrypted). Then you will have to reboot back to recovery and reinstall Magisk again (its because when the file system was decrypted the memory was formatted/overwrited). Then boot back to system and verify Magisk is in your icons again. If you have Magisk, you should have root. You can verify root by either programs that check it root or open a terminal window and type in SU and Magisk will pop up a window asking if you want to give the program root access.
Hope that helped.