Database Info

boorloader woes jb4.2.1

Hi
Having problems flashing from stock TF300T JB4.2.1
I started by downloading the asus bootloader unlocker.
Im not sure if the bootloader unlocker wored properly or not.
Then I reboot tablet using Vol DN + PWR
I boot into a bootloader and it says starting fastboot usb downloading protocol
I have 3x icon choices
[RCk] ... [Android] ... [WipeData]
There is no USB mode.
According to the guides I have to select usb mode.
What has gone wrong?
Thanks
Mike

in 4.2.1 bootloader menu usb mode (fastboot access) is enablet by default, when you are in this menu, just use command fastboot devices and check if device is visible.

kiwijunglist said:
Hi
Having problems flashing from stock TF300T JB4.2.1
I started by downloading the asus bootloader unlocker.
Im not sure if the bootloader unlocker wored properly or not.
Then I reboot tablet using Vol DN + PWR
I boot into a bootloader and it says starting fastboot usb downloading protocol
I have 3x icon choices
[RCk] ... [Android] ... [WipeData]
There is no USB mode.
According to the guides I have to select usb mode.
What has gone wrong?
Thanks
Mike
Click to expand...
Click to collapse
Make sure the guide and ROM you are installing is for your bootloader and not the previous version.

misiekantos253 said:
in 4.2.1 bootloader menu usb mode (fastboot access) is enablet by default, when you are in this menu, just use command fastboot devices and check if device is visible.
Click to expand...
Click to collapse
Code:
C:\adk\platform-tools>fastboot devices
015d2578364c200f fastboot
I tried to unsucessfully flash twrp for 4.2 for TF300
Code:
C:\adk\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
< waiting for device >
sending 'recovery' (8078 KB)...
OKAY [ 2.890s]
writing 'recovery'...
[B]FAILED (remote: (InvalidState))[/B]
finished. total time: 5.550s

kiwijunglist said:
Code:
C:\adk\platform-tools>fastboot devices
015d2578364c200f fastboot
I tried to unsucessfully flash twrp for 4.2 for TF300
Code:
C:\adk\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
< waiting for device >
sending 'recovery' (8078 KB)...
OKAY [ 2.890s]
writing 'recovery'...
[B]FAILED (remote: (InvalidState))[/B]
finished. total time: 5.550s
Click to expand...
Click to collapse
I got this error early on on a different PC than I use now. It turned out to be the USB port on my PC that I was using. I moved from a front port to one on the motherboard in the back and it flashed successfully. I know others have had cables that caused the error so try a different cable as well.

pastorbob62 said:
I got this error early on on a different PC than I use now. It turned out to be the USB port on my PC that I was using. I moved from a front port to one on the motherboard in the back and it flashed successfully. I know others have had cables that caused the error so try a different cable as well.
Click to expand...
Click to collapse
Error related to the bootloader not being unlocked, i have gotten a bit further now.
I now can run TWRP recovery, so I'm doing a full backup to internal storage.
I guess after that I should copy that onto my PC.
What is the next step after that, is it safe to now start flashing roms.
If I flash a 4.3 or 4.4 rom, can I go back to 4.2?

kiwijunglist said:
Error related to the bootloader not being unlocked, i have gotten a bit further now.
I now can run TWRP recovery, so I'm doing a full backup to internal storage.
I guess after that I should copy that onto my PC.
What is the next step after that, is it safe to now start flashing roms.
If I flash a 4.3 or 4.4 rom, can I go back to 4.2?
Click to expand...
Click to collapse
Glad you solved the problem. :good:
Making a TWRP backup is good but I suggest making a Flatline - NVFlash backup to be sure you have a way back if you brick your tablet. It is time consuming but well worth the effort. Here is a link to that procedure - http://forum.xda-developers.com/showthread.php?t=2455922.
Several considerations before you flash a custom ROM. Be sure you have the correct bootloader and recovery version for the ROM you are flashing. As far as returning to 4.2 after moving to 4.4 I believe there are a couple of ways but haven't done that myself.
All of the threads with custom ROM's have very clear prerequisites and steps to follow for each particular scenario. Also, there are hundreds of posts in the Q&A and Development forums with excellent advice and cautions. DO YOUR RESEARCH! I know from experience that rushing into it can be a disaster and without having a thorough understanding of the steps involved and the potential pitfalls, you will wind up with a bricked device. I bricked a smart phone about a year ago just because I didn't take the time to do the research. It's a hard lesson to learn that way so take the time to research, research, research, especially if you are going to try different versions and different ROM's. In the end it will be time well spent.
Good luck my friend!

[ROOTING] Ulefone Be Touch 2 with TWRP recovery

Hi Folks,
Disclosure: No responsibility taken or accepted in any form if the following process failed.
As forum rules prevented me from posting links try to understand how to find referred files.
1. Prepare a PC with Windows 7 installed and the automatic Windows driver update lookup function possibly disabled.
2. Download BETA-SuperSU-v2.49.zip (appr. 4 MB, from chainfire eu and copy it to the phone's SD card or to an external micro SD card.
3. Download the latest stock ROM and flash tool packed together (e.g. 'Be-Touch-2_150702_s7yler.zip') from needrom com . Search for ulefone-be-touch-2.
4. Download TWRP recovery image file from needrom com . Search for be-touch-2-twrp-2-8-7-0.
Extract the rar archive and rename recoverye.img to recovery.img
5. Extract 'Be-Touch-2_150702_s7yler.zip' and replace the recovery.img file in the "Be-Touch-2_150702_s7yler\One Key Flashing(Be Touch 2_150702)\software" folder with the one from the TWRP archive (see point 2).
6. Install the MTK chipset driver (it works on Win7 only at the present time):
- Navigate to the "Be-Touch-2_150702_s7yler\One Key Flashing(Be Touch 2_150702)\Driver Auto Installer" folder.
- Open a Command Window to see what happens on the command line.
- Run Install.bat with real Administrator priviledges (in most cases Run as Administrator may not be enough - refer to UAC).
- Wait until the driver installation is finished. You will see on the screen if the drivers were installed successfully (e.g. "Driver install done").
7. Flashing ROM
Notes:
- Flashing ROM will wipe all your data. If you have not done a backup before you will permanently lose your data!
- The doc file containing pictures included in the zip file can also be followed.
- Do NOT format your phone with the flashing tool, that can result in lost IMEI.
- For anvanced users: the flash_tool.exe in the Smart Phone Flash Tool package can also be used only to flash recovery.img using an enclosed scatter.txt file.
a/ Open the Be-Touch-2_150702_s7yler\One Key Flashing folder and run SP_Facility_DL_Tool.exe
b/ Turn off the phone, take out the battery, press the Scan button in the SP_DownLoad window then connect your phone to the PC via USB.
c/ After the text "N/A+COM(x)" appears on the left hand side of the window disconnect your phone, reinsert the battery, press the Start button and reconnect your phone via the USB cable.
d/ Wait until the flashing utility finishes updating the phone (e.g. the process bar shows 100 % on yellow background and "DL OK" can be read to the left of the process bar).
8. After flashing, enter the TWRP custom recovery: press vol up + power to boot for a few seconds then install BETA-SuperSU-v2.49.zip from your (external) SD card.
9. You are done with rooting.

Fastboot
litokraz said:
- Flashing ROM will wipe all your data if you have not done a backup before!
- The doc file containing pictures included in the zip file can also be followed.
- Do NOT format your phone with the flashing tool, that can result in lost IMEI.
- For anvanced users: the flash_tool.exe in the Smart Phone Flash Tool package can also be used only to flash recovery.img using an enclosed scatter.txt file.
Click to expand...
Click to collapse
Again, for advanced users: You can also use fastboot (get it elsewhere) to flash just the TWRP recovery without wiping the rest of the phone: (e.g. "fastboot.exe flash recovery recovery-betouch2.img"), then use it to install supersu. You can also then flash the stock recovery back over it if you wish. Works like a charm.

marblemunkey said:
Again, for advanced users: You can also use fastboot (get it elsewhere) to flash just the TWRP recovery without wiping the rest of the phone: (e.g. "fastboot.exe flash recovery recovery-betouch2.img"), then use it to install supersu. You can also then flash the stock recovery back over it if you wish. Works like a charm.
Click to expand...
Click to collapse
Yes you are right. The method I described above also updates to the latest(?) Ulefone ROM as of 02-07-2015.
Even you can flash a Carlive recovery (tried and works) based on the downloadable from the "Ulefone Be Touch 2, 5.5 Inch Full HD, Metal Frame, MT6752 64-bit, 3050mAh Battery" thread Post #76. Carlive (originated from CWM) lacks the annoying splash screen which is included in TWRP.

UPDATE: Never mind, I got it. WooHoo
Guys, how do I get to Fastboot mode on my BE Touch 2? I tried power + volume down, yet it takes me to chinese menu I do not understand.
Odesláno z mého Be Touch 2 pomocí Tapatalk

Thank you Litakraz .... Good job done ... works like charm ..well explained

marblemunkey said:
Again, for advanced users: You can also use fastboot (get it elsewhere) to flash just the TWRP recovery without wiping the rest of the phone: (e.g. "fastboot.exe flash recovery recovery-betouch2.img"), then use it to install supersu. You can also then flash the stock recovery back over it if you wish. Works like a charm.
Click to expand...
Click to collapse
Hi, i have one Be Touch 2 and i can't find the fastboot mode in my recovery mode ( chinese recovery )
here is a screenshot of a similar recovery mode i got
youtu.be/RwpUyc7ig5w
Can you explain how to enter in Fastboot mode please ?
Thanks
Sorry for my bad english
UPDATE : I finally tried the command "adb reboot bootloader"
and after this I was able to flash recovery.img with fastboot (fastboot flash recovery recovery.img)
but i still can't boot on TWRP (still chinese bootloader)
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (13540 KB)...
OKAY [ 0.458s]
writing 'recovery'...
OKAY [ 0.207s]
finished. total time: 0.665s
UPDATE 2 :
My bad, to enter in TWRP mode reboot the phone using POWER+VOL UP
worked like a charm with the recovery img from needrom , thanks !
PS : /!\ AVOID TO UPDATE YOUR DEVICE OR YOU WILL BE BLOCKED ON THE ULEFONE LOGO !!! /!\

dkpiit said:
Hi, i have one Be Touch 2 and i can't find the fastboot mode in my recovery mode ( chinese recovery )
here is a screenshot of a similar recovery mode i got
youtu.be/RwpUyc7ig5w
Can you explain how to enter in Fastboot mode please ?
Thanks
Sorry for my bad english
UPDATE : I finally tried the command "adb reboot bootloader"
and after this I was able to flash recovery.img with fastboot (fastboot flash recovery recovery.img)
but i still can't boot on TWRP (still chinese bootloader)
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (13540 KB)...
OKAY [ 0.458s]
writing 'recovery'...
OKAY [ 0.207s]
finished. total time: 0.665s
UPDATE 2 :
My bad, to enter in TWRP mode reboot the phone using POWER+VOL UP
worked like a charm with the recovery img from needrom , thanks !
Click to expand...
Click to collapse
Tried that method, always get stuck in <waiting for device> !!!
Any advice ???

Heshamvido said:
Tried that method, always get stuck in <waiting for device> !!!
Any advice ???
Click to expand...
Click to collapse
Yes, just download and install adbdriver[DOT]com/downloads/

Thanks to the OP for the guide. I am now rooted & the phone is working perfectly.
Now just waiting for cyanogenmod to be released for it & I'll be a happy man.

Is there a way to root the Ulefone be touch one which is compatible with the last firmware ? (15/08/11)
The solution given by @Pasi_K don't work with the update

Darkstar2r1 said:
Is there a way to root the Ulefone be touch one which is compatible with the last firmware ? (15/08/11)
The solution given by @Pasi_K don't work with the update
Click to expand...
Click to collapse
I am curious on that too! Did you get it running?
I will try a different recovery.... hope that works.

hi guys..
anyone has NVRAM for this device..? it is black screen now but it is working..

Bricked XT925

Hi all, first post here.
I have a bricked XT925 which I'm trying to recover.
It will go into fastboot and I can access it with ADB/Fastboot/mFastbootv2/RazorHDToolkit5.0/RSD lite etc, but none of these will write a new recovery to flash.
I was able to unlock the bootloader using the Motorola website and the phone will talk to the PC software, but it's as though the internal flash memory is trashed.
In fact lots of commands to the flash result in a "fastboot max download size 30mb" error.
Can anyone help?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-2.8.6.0-xt925.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (9154 KB)...
OKAY [ 0.730s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.871s
Click to expand...
Click to collapse

I would start with obtaining a clean working flash of the official ROM, before trying to flash anything custom.
Just a guess, but if you went to the unlock website after the phone was soft-bricked, the bootloader may still be locked. I assume that the phone needs a full working OS to receive and implement the unlock signal from Motorola. Since it hasn't booted the OS since it was bricked, it hasn't had a chance to do so.

I would start with obtaining a clean working flash of the official ROM, before trying to flash anything custom.
Click to expand...
Click to collapse
Would that I could. All the links I've found so far are dead.
I have another XT925 in working order, anyone know how to extract the image from it?
Just a guess, but if you went to the unlock website after the phone was soft-bricked, the bootloader may still be locked. I assume that the phone needs a full working OS to receive and implement the unlock signal from Motorola. Since it hasn't booted the OS since it was bricked, it hasn't had a chance to do so.
Click to expand...
Click to collapse
I think the Bootloader error messages are to be expected, everything I've since read suggests I should ignore them.

ddichiera said:
Would that I could. All the links I've found so far are dead.
I have another XT925 in working order, anyone know how to extract the image from it?
I think the Bootloader error messages are to be expected, everything I've since read suggests I should ignore them.
Click to expand...
Click to collapse
I have one of the old Canadian leaked KK stock sbf (I was using it to see if I could bring anything to my AHD). I can post it to my GDrive and post the link this afternoon.

palmbeach05 said:
I have one of the old Canadian leaked KK stock sbf (I was using it to see if I could bring anything to my AHD). I can post it to my GDrive and post the link this afternoon.
Click to expand...
Click to collapse
Any image would be welcome, GDrive is fine.

ddichiera said:
Any image would be welcome, GDrive is fine.
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B52pkPIFU2dRWFRXOU9UQlhHZ3c

Thanks for that, unfortunately my situation has become worse.
Whilst the phone was connected and in fastboot mode, I deleted the ADB driver in Device Manager and now the PC, or more specifically ADB and Fastboot wont talk to the phone. Grrrrr.
Oh, and the other handset has decided to die as well.
One thing at a time. Anyone know how to restore the driver/get-the-phone-talking-to-ADB/Fastboot again?

Huawei P8 (L09) bricked TWRP no OS

I tried to do reset my phone for battery issues. The thing is that it seems i don't have operating system now and i can't flash the phone because TWRP is the only loader and it doesn't recognizes the update app. Any idea to install at least a custom rom via TWRP or any way to unbrick the phone? Thanks. Any other detail you need please ask me. It is the first time i need help to fix a phone.

icemann1908 said:
I tried to do reset my phone for battery issues. The thing is that it seems i don't have operating system now and i can't flash the phone because TWRP is the only loader and it doesn't recognizes the update app. Any idea to install at least a custom rom via TWRP or any way to unbrick the phone? Thanks. Any other detail you need please ask me. It is the first time i need help to fix a phone.
Click to expand...
Click to collapse
If you know the version of the rom, simply download that version stock rom and then extract from it the recovery using Huawei extractor tool and flash that recovery using adb. After that put the stock rom in a dload folder and put it on your sdcard or internal memory after that turnoff the device hold power and vol up and vol down at the same to make the flash process start and flash the stock rom. Sorry I am on the road and quite busy otherwise I would have written a detailed guide. But if you Google what I suggested you will find the tools needed to make it work. If still you can't manage to make it work let me know. After 2 days I would be around a pc to write a better guide.
Sent from my Nexus 6P using XDA-Developers mobile app

Rashad83 said:
If you know the version of the rom, simply download that version stock rom and then extract from it the recovery using Huawei extractor tool and flash that recovery using adb. After that put the stock rom in a dload folder and put it on your sdcard or internal memory after that turnoff the device hold power and vol up and vol down at the same to make the flash process start and flash the stock rom. Sorry I am on the road and quite busy otherwise I would have written a detailed guide. But if you Google what I suggested you will find the tools needed to make it work. If still you can't manage to make it work let me know. After 2 days I would be around a pc to write a better guide.
Goood Afternoon,
I have the same problem but i tried what you said and when i try to flash my device i would get:
C:\Users\Ebonique\Downloads\fastboot>fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (28228 KB)...
OKAY [ 0.640s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.648s
C:\Users\Ebonique\Downloads\fastboot>
And Honestly i do not know what to do. Any suggestions?
Click to expand...
Click to collapse

ebbytay said:
Rashad83 said:
If you know the version of the rom, simply download that version stock rom and then extract from it the recovery using Huawei extractor tool and flash that recovery using adb. After that put the stock rom in a dload folder and put it on your sdcard or internal memory after that turnoff the device hold power and vol up and vol down at the same to make the flash process start and flash the stock rom. Sorry I am on the road and quite busy otherwise I would have written a detailed guide. But if you Google what I suggested you will find the tools needed to make it work. If still you can't manage to make it work let me know. After 2 days I would be around a pc to write a better guide.
Goood Afternoon,
I have the same problem but i tried what you said and when i try to flash my device i would get:
C:\Users\Ebonique\Downloads\fastboot>fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (28228 KB)...
OKAY [ 0.640s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.648s
C:\Users\Ebonique\Downloads\fastboot>
And Honestly i do not know what to do. Any suggestions?
Click to expand...
Click to collapse
You need to make sure your bootloader is unlocked otherwise it won't work. If your bootloader is indeed unlocked then it could be a PC communication issue try to reinstall drivers of the phone, even better try it on another PC/Laptop with a fresh install of drivers and applications needed.
Click to expand...
Click to collapse

Rashad83 said:
ebbytay said:
You need to make sure your bootloader is unlocked otherwise it won't work. If your bootloader is indeed unlocked then it could be a PC communication issue try to reinstall drivers of the phone, even better try it on another PC/Laptop with a fresh install of drivers and applications needed.
Click to expand...
Click to collapse
My bootloader is unlocked
I have tried to install the usb drivers but im not sure if i am currently installing them correctly.
When i type enter fastboot devices i get:
C:\Users\Ebonique\Downloads\fastboot>fastboot devices
S7M0215B19000640 fastboot
C:\Users\Ebonique\Downloads\fastboot>
but when i enter adb devices i get:
C:\Users\Ebonique\Downloads\fastboot>adb devices
List of devices attached
C:\Users\Ebonique\Downloads\fastboot>
Is there any possibility that you can walk me through installation of the devices? I have a Huawei Gra-L09 (P8)
Click to expand...
Click to collapse

ebbytay said:
Rashad83 said:
My bootloader is unlocked
I have tried to install the usb drivers but im not sure if i am currently installing them correctly.
When i type enter fastboot devices i get:
C:\Users\Ebonique\Downloads\fastboot>fastboot devices
S7M0215B19000640 fastboot
C:\Users\Ebonique\Downloads\fastboot>
but when i enter adb devices i get:
C:\Users\Ebonique\Downloads\fastboot>adb devices
List of devices attached
C:\Users\Ebonique\Downloads\fastboot>
Is there any possibility that you can walk me through installation of the devices? I have a Huawei Gra-L09 (P8)
Click to expand...
Click to collapse
That's normal, in order to see your device using adb commands it needs to be turned on and working properly also the developer mode needs to be enabled in order to see your device code serial number so in other words it's not possible at your current situation.
Regarding the device drivers just connect the device to the PC and let it auto install the drivers needed make sure Hisuite package is installed before that.
The only commands you can use at your current case with the phone in bootloader mode is only fastboot commands. So just try to flash the stock recovery like before and hopefully it will work out. If it does try to flash the same stock rom using the dload method. I cannot at the Moment give you a step by step I am really sorry but if you google the things you need you will find it easily.
Edit:
Similar issue maybe it can help you.
http://forum.xda-developers.com/showpost.php?p=68037081&postcount=304
Click to expand...
Click to collapse

Rashad83 said:
ebbytay said:
That's normal, in order to see your device using adb commands it needs to be turned on and working properly also the developer mode needs to be enabled in order to see your device code serial number so in other words it's not possible at your current situation.
Regarding the device drivers just connect the device to the PC and let it auto install the drivers needed make sure Hisuite package is installed before that.
The only commands you can use at your current case with the phone in bootloader mode is only fastboot commands. So just try to flash the stock recovery like before and hopefully it will work out. If it does try to flash the same stock rom using the dload method. I cannot at the Moment give you a step by step I am really sorry but if you google the things you need you will find it easily.
Edit:
Similar issue maybe it can help you.
http://forum.xda-developers.com/showpost.php?p=68037081&postcount=304
Click to expand...
Click to collapse
Thank you very much for the link it actually helped me and I was able to fix my phone.
I had no clue which stock version my phone came with so I downloaded all and then use the dload method. The phone was able to update to its original form.
I Really appreciate all of your responses, thank you once again.
Click to expand...
Click to collapse

ebbytay said:
Rashad83 said:
Thank you very much for the link it actually helped me and I was able to fix my phone.
I had no clue which stock version my phone came with so I downloaded all and then use the dload method. The phone was able to update to its original form.
I Really appreciate all of your responses, thank you once again.
Click to expand...
Click to collapse
You're welcome. Good luck.
Click to expand...
Click to collapse

Bootloop on Motorola Moto G4 Play (Verizon) XT1609

I would like to recover the ROM on this Android this device it keeps bootlooping I tryed to Root the Device and I did a factory reset on it after I did a root... I thought everything was going find and it started to keep reloading the logo (Moto)...
I basically tried everything to recover the ROM on it using the following programs...
ADB Setup
MFastBoot (Error Message with Bootloader)
it seems to be locked device I can't seem to unlock the device... I seen someone that you don't have to have it unlock it to install TWRP or something....
Am all new to this stuff and I just got my phone I did not want anything happen to this phone for important use I would like to get this phone back up and running again...
Thanks

Moto G4 Play XT1609 Bootloop after rooting
travisbrown9201 said:
I would like to recover the ROM on this Android this device it keeps bootlooping I tryed to Root the Device and I did a factory reset on it after I did a root... I thought everything was going find and it started to keep reloading the logo (Moto)...
I basically tried everything to recover the ROM on it using the following programs...
ADB Setup
MFastBoot (Error Message with Bootloader)
it seems to be locked device I can't seem to unlock the device... I seen someone that you don't have to have it unlock it to install TWRP or something....
Am all new to this stuff and I just got my phone I did not want anything happen to this phone for important use I would like to get this phone back up and running again...
Thanks
Click to expand...
Click to collapse
Am in the same boat. My Verizon Moto G4 Play XT1609 Bootloops after rooting and restarting. I have tried all else including repairing via Verizon Upgrade Assistant tool with no success (Ugrade Assistant tool detected my phone, flashed latest firmware and cleared user data only for the phone to resume bootloop :crying.
I had to try Upgrade Assistant tool since this model does not qualified for bootloader unlocking ("fastboot getvar all" returned cid: 0x0002)
I trust that all hope is not lost, having confidence someone would turn up something somehow :laugh:
So, any help would be appreciated.

Re-run autoinitroot and then follow the instructions to unroot, thats all!

conquesoextra said:
Re-run autoinitroot and then follow the instructions to unroot, thats all!
Click to expand...
Click to collapse
Thanks too much! you just saved my Motorola!

bullracing said:
Thanks too much! you just saved my Motorola!
Click to expand...
Click to collapse
Hi,
I asked a related question in https://forum.xda-developers.com/g4-play/help on 4/9 and have yet to receive any responses. I didn't see this question before. It looks like a very similar situation to mine.
My XT1609 also is bootlooping and the bootloader also is locked, so I assume that this is why I'm getting "Preflash validation failed" errors when I try to download stock images to it. I found harpia_vzw_oem_vzw_user_7.1.1_NPI26.48-38_48_release-keys-cid2_vzw.tar.gz through this site and have been attempting to use Linux/fastboot to download images from the tar. I am able to download and reflash one of the images, logo.img, but I get the prevalidation errors for everything else I've tried.
I'm not familiar with mfastboot or autoinitroot. Can someone tell me where I can get these and how to use them? Should I just need to use autoinitroot to fix the bootlooping or does this somehow allow me to flash images to the phone?
Thanks!

thalwegz said:
Hi,
I asked a related question in https://forum.xda-developers.com/g4-play/help on 4/9 and have yet to receive any responses. I didn't see this question before. It looks like a very similar situation to mine.
My XT1609 also is bootlooping and the bootloader also is locked, so I assume that this is why I'm getting "Preflash validation failed" errors when I try to download stock images to it. I found harpia_vzw_oem_vzw_user_7.1.1_NPI26.48-38_48_release-keys-cid2_vzw.tar.gz through this site and have been attempting to use Linux/fastboot to download images from the tar. I am able to download and reflash one of the images, logo.img, but I get the prevalidation errors for everything else I've tried.
I'm not familiar with mfastboot or autoinitroot. Can someone tell me where I can get these and how to use them? Should I just need to use autoinitroot to fix the bootlooping or does this somehow allow me to flash images to the phone?
Thanks!
Click to expand...
Click to collapse
Hi, again
I was able to download the autoinitroot package from http://downloads.codefi.re/autoprime/Motorola/autoinitroot/XT1609 and extract and run the Linux version of the script. Here's what happened:
2102d sudo ./auto#initroot.linux.sh
#initroot and cve-2016-10277 by https://twitter.com/roeehay
magisk by https://twitter.com/topjohnwu
auto#initroot by https://twitter.com/@utoprime
.
..
...
....to uninstall auto#initroot, press <any> key within 3 seconds
...
..
.
-start auto#initroot
-send fastboot oem config fsg-id a initrd=0x91000000,2064196
...
FAILED (remote failure)
finished. total time: 0.017s
-send fastboot flash initroot xt1609_harpia_vzw_mpis24.241-2.35-1-17.initroot
target max-download-size: 256MB
sending 'initroot' (19531 KB)...
OKAY [ 24.421s]
writing 'initroot'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 24.431s
-send fastboot continue
resuming boot...
OKAY [ 0.097s]
finished. total time: 0.097s
-finish moto boot
I have Android 7.1.1 installed on my phone, the stock Verizon OTA version. Could there be an incompatibility between this initroot image and the other software on the phone?
Thanks