Database Users

booting failed with the 4.3 update using NRT wug soft ... help

HI dudes,
it seems i screwed up ...
I was in 4.2.2 and I wanted to go to 4.3 (my tab was rooted and unlock)
I decided to use "back to stock" from the wug software (with the 4.3 file) and now
I've got "booting error"
START: booting failed
RECOVERY : booting failed
bootloader : I've got the android character
what can i do now ?
thanks

You've erased your ROM and recovery before the failed flash. You can describe in more detail on the status of your bootloader?

well ... yes ...
booloader version 4.23
lock state unlocked
fastboo mode
product name tilapia

So your bootloader is fine. You can just reinstall all the stock images with fastboot.

Username invalid said:
So your bootloader is fine. You can just reinstall all the stock images with fastboot.
Click to expand...
Click to collapse
Ouf ...
DO you have a tutorial ?
Can I try with Nexus root kit with "back to stock" 4.2.2 (and what to choose in current status ? normal or soft bricked ?)
thanks anyway.

alucard_xs said:
Ouf ...
DO you have a tutorial ?
Can I try with Nexus root kit with "back to stock" 4.2.2 (and what to choose in current status ? normal or soft bricked ?)
thanks anyway.
Click to expand...
Click to collapse
Download stock package.
Unzip contents to C:\Program Files\WugFresh Development\data.
Open toolkit > Advanced Utilities > Launch CMD > "flash-all.bat" will restore your device to 4.3 stock.

thanks but do I have to use the 4.3 stock or the 4.2.2 stock like I was before the failed flash ?

You can flash any version you want (4.1.2, 4.2.2, 4.3).

Thanks a lot.
last question :
what kind of model should i use in the configuration ?
4.3 or 4.2.2 ? is it important ?

That will flash all the images. You can flash each image individually.
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
---------- Post added at 06:08 AM ---------- Previous post was at 06:07 AM ----------
alucard_xs said:
Thanks a lot.
last question :
what kind of model should i use in the configuration ?
4.3 or 4.2.2 ? is it important ?
Click to expand...
Click to collapse
As I said, it is entirely up to you on which Jelly Bean version you want.

Okay, I did what you tell me and it seems to be okay right now !
What a relief !!
Thanks again for your help !!!!!

That's good.

Flash a original firmware to your tablet
Sent from my LG-P700 using xda app-developers app

Username invalid said:
That's good.
Click to expand...
Click to collapse
im having trouble with the steps you have suggested .. when i try the command "flash-all.bat" it says command not recognized ..

funkme021 said:
im having trouble with the steps you have suggested .. when i try the command "flash-all.bat" it says command not recognized ..
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need to extract everything in the stock image package including "flash-all.bat" to your ADB/Fastboot folder.
https://www.youtube.com/watch?v=foLQCNxroHw

Username invalid said:
You need to extract everything in the stock image package including "flash-all.bat" to your ADB/Fastboot folder.
https://www.youtube.com/watch?v=foLQCNxroHw
Click to expand...
Click to collapse
it appears that i need to have an updated bootloader ... i currently have 4.18 and it says the update requires 4.23 ... but when i tried to flash the 4.23 bootloader it says that it sends it to the device just fine but i get the failed message when it tries to write the bootloader ... giving me this message FAILED <remote: invalid Partition Name.> ... <FRUSTRATED> lol ... also i appreciate all your help

UPDATE
ok i finally got it .. i just went and downloaded the factory images for jdq39 (the image that used the bootloader v. 4.18) installed that and then let the tablet update itself... thats what i call a crash course in fastboot lol .. learned the hard way but i think i somewhat understand it now

[GUIDE][HOW-TO] Update your bootloader

XT1063 - XT1064 - XT1068 - XT1069
Disclaimer
Code:
Your warranty is (probably) not void since these
are the official images. Backup, always!!!
I am not responsible for bricked devices, dead SD cards,
you getting fired because the alarm app failed,
thermonuclear war, or anything else.
YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device,
I will laugh at you. Hard. A lot.
New version 10/10/16
Get your Model number by opening back cover and looking at the sticker
Download the correct folder for your device: Google Drive | Mega
Shutdown your Phone
Boot into bootloader ( Hold volume - and power for 5 seconds and then release)
Connect phone to a pc with fastboot installed
Open a cmd / terminal window
Change the directory to the one where you saved the device specific files you downloaded
Type/copy
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Hit the Thanks! button (right bottom corner of this post)
Please read Q&A before asking a question
Thanks: luca020400 and LuK1337 and skaveelicious

Q & A
Q: Could you make a video because I don't understand the guide?
A: No, there won't be a video because if you don't understand the guide you will most likely harm your device.
Q: Can I flash kk roms on lp bootloader?
A: Yes, but the other way around only works with stock (based) roms.
Q: Do I need to unlock the bootloader?
A: No, if you only update the bootloader you don't need to unlock, if you want twrp or such a thing this is required.
Q: I have no signal, how to fix it?
A: http://forum.xda-developers.com/showpost.php?p=60740579&postcount=183
Q: I have a XT1063 and no signal, how do I restore it?
A: Use these files: https://mega.co.nz/#!QFonVR4J!dhNw1kwj9GBc5vh14s-SLw3VeCa34IboIQlAZ13Fjq8
Q: My bootloader is 4882 or higher do I need to update?
A: No, this guide makes your bootloader 4882, ( downgrading is impossible ) so you are good
Q: I got success every time, but I am still on the old bootloader, what went wrong?
A: You need admin rights for these commands since fastboot otherwise won't recognize the device with correct permissions. On windows run cmd as admin, on linux use sudo in front of all lines.
Q: Something is not working, were do I find my country specific files?
A: This has all official firmware, you can find the right one for you and use the files from that zip. Sadly the server is very slow. Now faster mirror

gregor160300 said:
Mine for Q & A if any
Click to expand...
Click to collapse
AFH files are up

As I've said here, be cautious when doing this to a brazilian XT1068 (not sure if it's the same for XT1069).

Does updating to official UK lp ota with locked boot loader automatically update it to lp once unlocked or do I still need to run this?

daviss101 said:
Does updating to official UK lp ota with locked boot loader automatically update it to lp once unlocked or do I still need to run this?
Click to expand...
Click to collapse
If you have bootloader from december then it is updated already.

Thanks
Sent from my Moto G 2014

Thanks for your work i have done all the steps but it wont work for me.........

luca020400 said:
AFH files are up
Click to expand...
Click to collapse
Thanks! I am not going to hit the button

Sosa88 said:
Thanks for your work i have done all the steps but it wont work for me.........
Click to expand...
Click to collapse
Can you please be more specific in what doesnt work and what the error is so I can help you

@gregor160300 i think it's not Bootloader related.... because i can flash ACIP without error.
But when i try to flash PAC or the latest CM nightly there comes "Error updater binary in zip"...... I'm using the latest twrp.

Sosa88 said:
@gregor160300 i think it's not Bootloader related.... because i can flash ACIP without error.
But when i try to flash PAC or the latest CM nightly there comes "Error updater binary in zip"...... I'm using the latest twrp.
Click to expand...
Click to collapse
For as far as I know it is indeed not bootloader related, I had the same error on my old device and still dont know how to fix it, sorry.

Sosa88 said:
@gregor160300 i think it's not Bootloader related.... because i can flash ACIP without error.
But when i try to flash PAC or the latest CM nightly there comes "Error updater binary in zip"...... I'm using the latest twrp.
Click to expand...
Click to collapse
gregor160300 said:
For as far as I know it is indeed not bootloader related, I had the same error on my old device and still dont know how to fix it, sorry.
Click to expand...
Click to collapse
Yes , this is due boot loader.
Gregor open the updater-script ( cm & pac ) and you will find why

Bootloader
luca020400 said:
Yes , this is due boot loader.
Gregor open the updater-script ( cm & pac ) and you will find why
Click to expand...
Click to collapse
Now I found the line I think: assert(getprop("ro.bootloader") == "0x4882" || abort("This package supports bootloader(s): 0x4882; this device has bootloader " + getprop("ro.bootloader") + "."); don't know how to fix it but you might want to try one of the stock recovery tools with your correct firmware and then install twrp again.

gregor160300 said:
Now I found the line I think: assert(getprop("ro.bootloader") == "0x4882" || abort("This package supports bootloader(s): 0x4882; this device has bootloader " + getprop("ro.bootloader") + "."); don't know how to fix it but you might want to try one of the stock recovery tools with your correct firmware and then install twrp again.
Click to expand...
Click to collapse
Fix --> Update bootloader

@luca020400 i think that my phone is on the latest Bootloader......
Tell how can i upgrade that fu** Bootloader ?

Sosa88 said:
@luca020400 i think that my phone is on the latest Bootloader......
Tell how can i upgrade that fu** Bootloader
Click to expand...
Click to collapse
Pc with adb installed
adb shell "getprop ro.bootloader"
Tell me the output

allowed me to flash CM12 nightlies!!
Thank you very much!
Updating xt1064 bootloader finally allowed me to flash cm12 nightlies.
I had been getting binary update error in TWRP.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@luca020400 thats it...

Sosa88 said:
@luca020400 thats it...
Click to expand...
Click to collapse
You should be able to flash cm12 :/
Reflash recovery

Update to 5.1.1 without loosing data

Hello together,
these were the steps to update to 5.1.1 (LMY47X) from 5.0.1 (LRX22C).
It was working for me - without loosing data.
Notes:
OTA didn't work cause of having custom recovery / root.
Maybe it was also in another thread here - but I didn't saw it
It work for me (WIFI-Version) - but might kill your device :crying:
from post #4: In case you using fastboot no very often - look here for more details: http://forum.xda-developers.com/showpost.php?p=60697487&postcount=26 - Thanks the.teejster
Steps
Make sure you have working fastboot on your PC
Download Factory Image and unzip it
Also unzip the included image-volantis-lmy47x.zip
Boot your Nexus 9 into fastboot (Shutdown device; Hold Vol-UP + Power on)
Flash bootloader & reboot
Code:
fastboot flash bootloader bootloader-flounder-3.44.1.0123.img
fastboot reboot-bootloader
Erase everthing but data partition
Code:
fastboot erase system
fastboot erase recovery
fastboot erase cache
fastboot erase boot
fastboot erase vendor
Flash the file (found in the unpacked image-volantis*zip)
Code:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
Reboot device
Optional: Root it again.
Download CF-Autoroot
Use the root-Scripts
Hope it helps and works for you.

One question. I am rooted and have twrp recovery. I this case : Why should we update recovery?

Alternatively, you could remove the "-w" flag from the flash-all.sh script and run it without losing data

A few key prerequisite items are missing in the OP..
I wrote up a similar "how to" over here :
http://forum.xda-developers.com/showpost.php?p=60697487&postcount=26

Hello,
I always upgraded android manually flashing while in fastboot.
Lastly i upgraded to 5.0.2 flawless, then yesterday i download 5.1.1 image and flashed as usual, to not lose data, bootloader/system/boot.
Now everytime i boot my tablet i get this error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And lot of apps force close (gmail opens, but when i try to open a mail fc, eurosport same, opens but when i reada news fc, and many other)while others works flawless.
I tried wiping everything, also userdata, but problem not solved.
What can i do?
I read here that someone when upgrade android also erase "vendor", it's the only thing i didnt do, but i never did it.
Please help, finally with 5.1.1 this device flies but now i can't use it!
Thanks.

What about Vendor and recovery ?
Please see my instructions linked about 2 posts up. Follow those exactly and you shouldn't lose any data and the upgrade should be fine.
Sayan1987 said:
Hello,
Lastly i upgraded to 5.0.2 flawless, then yesterday i download 5.1.1 image and flashed as usual, to not lose data, bootloader/system/boot.
Now everytime i boot my tablet i get this error
Click to expand...
Click to collapse

Sayan1987 said:
Hello,
I always upgraded android manually flashing while in fastboot.
Lastly i upgraded to 5.0.2 flawless, then yesterday i download 5.1.1 image and flashed as usual, to not lose data, bootloader/system/boot.
Now everytime i boot my tablet i get this error
And lot of apps force close (gmail opens, but when i try to open a mail fc, eurosport same, opens but when i reada news fc, and many other)while others works flawless.
I tried wiping everything, also userdata, but problem not solved.
What can i do?
I read here that someone when upgrade android also erase "vendor", it's the only thing i didnt do, but i never did it.
Please help, finally with 5.1.1 this device flies but now i can't use it!
Thanks.
Click to expand...
Click to collapse
try fastboot flash vendor vendor.img
For the fc you are experiencing, it is possibly due to the modified ART in 5.1.1 or you check if you have the latest Android Webview

I just thought I would throw this out here in case anyone needs or wants to know...
You do not need to flash the bootloader to upgrade from 5.0.2 to 5.1.1, I can not tell you if this will work coming from 5.0.1
Also after first boot and you flash twrp, you can boot to recovery then immediately reboot back to system. Twrp will install su for you. You'll just need to update the su apk in the market. No need to mess with any kind of su zip anymore.
That's all I have to add to an already great guide.

the.teejster said:
What about Vendor and recovery ?
Please see my instructions linked about 2 posts up. Follow those exactly and you shouldn't lose any data and the upgrade should be fine.
Click to expand...
Click to collapse
laill said:
try fastboot flash vendor vendor.img
For the fc you are experiencing, it is possibly due to the modified ART in 5.1.1 or you check if you have the latest Android Webview
Click to expand...
Click to collapse
Thanks guys flashing vendor fixed everything!!

All the forced closes, heat problems, May I ask are you really stock? No such problems here
Verstuurd vanaf mijn HIGHWAY SIGNS met Tapatalk

[Q] nexus 7 (2012) tablet, soft bricked, can't flash images, failed, unknown error

i have a Nexus 2012 7inch tablet (Wifi) that is soft bricked. (stuck at the perpetual moving colored dots screen).
when my tablet was still under warranty in 2013 it did have it's motherboard replaced when it wouldn't even turn on. now the problem is different, at least i can power it on and get into the bootloader. since the lollipop update it had been getting progressively laggy before finally 'crashing' and bootlooping.
i've tried the following:
1) first i attempted the tutorial located here: http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
i managed to wipe the device but not flash the images to the device.
2) then i used this tutorial http://forum.xda-developers.com/showthread.php?t=2588979 to install the adb drivers.
3) i have now used Wugs to attempt flash stock + unroot. everything seems to work until it gets to "sending 'system'" then it gives "FAILED <data transfer failure <Unknown error>>, also same error for sending 'userdata'and post-flash factory reset. same Unknown error.
i am also not sure which google images to use. i have tried nakasi 4.3 (JWR66Y), 4.4.4 (KTU84P), and 5.1.1 (LMY47V), and "any build" options.
so i'm not sure if it could be a driver issue or how to fix it further. fastboot seems to recognize the tablet while adb does not. i did not have it set in debugging mode.
i've attached the screen from Wugs...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

stargirl29 said:
i have a Nexus 2012 7inch tablet (Wifi) that is soft bricked. (stuck at the perpetual moving colored dots screen).
when my tablet was still under warranty in 2013 it did have it's motherboard replaced when it wouldn't even turn on. now the problem is different, at least i can power it on and get into the bootloader. since the lollipop update it had been getting progressively laggy before finally 'crashing' and bootlooping.
i've tried the following:
1) first i attempted the tutorial located here: http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
i managed to wipe the device but not flash the images to the device.
2) then i used this tutorial http://forum.xda-developers.com/showthread.php?t=2588979 to install the adb drivers.
3) i have now used Wugs to attempt flash stock + unroot. everything seems to work until it gets to "sending 'system'" then it gives "FAILED <data transfer failure <Unknown error>>, also same error for sending 'userdata'and post-flash factory reset. same Unknown error.
i am also not sure which google images to use. i have tried nakasi 4.3 (JWR66Y), 4.4.4 (KTU84P), and 5.1.1 (LMY47V), and "any build" options.
so i'm not sure if it could be a driver issue or how to fix it further. fastboot seems to recognize the tablet while adb does not. i did not have it set in debugging mode.
i've attached the screen from Wugs...
Click to expand...
Click to collapse
Try flashing the images individually with fastboot. That's how I always do it. Be sure your platform tools are up to date as well.

fastboot
Evolution_Tech said:
Try flashing the images individually with fastboot. That's how I always do it. Be sure your platform tools are up to date as well.
Click to expand...
Click to collapse
i'm not really sure how to do that.

stargirl29 said:
i'm not really sure how to do that.
Click to expand...
Click to collapse
Download and unzip the factory image. Unzip two times until you have all the images. I.E. bootloader, radio, boot, system, recovery, userdata, cache.
Put them where fastboot can find them. I.E. platform tools folder.
Hopefully you know how to use fastboot.
Start by flashing bootloader.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot bootloader
Then flash the rest.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot format cache
fastboot flash cache cache.img
fastboot reboot

fastboot
Evolution_Tech said:
Download and unzip the factory image. Unzip two times until you have all the images. I.E. bootloader, radio, boot, system, recovery, userdata, cache.
Put them where fastboot can find them. I.E. platform tools folder.
Hopefully you know how to use fastboot.
Start by flashing bootloader.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot bootloader
Then flash the rest.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot format cache
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
no i do not know how to use fastboot. but what you posted sounds exactly like the tutorial that i followed in step #1 that i mentioned above. i did the tutorial again last night and was able to flash the images this time, but it's still stuck in bootloop on startup.

stargirl29 said:
no i do not know how to use fastboot. but what you posted sounds exactly like the tutorial that i followed in step #1 that i mentioned above. i did the tutorial again last night and was able to flash the images this time, but it's still stuck in bootloop on startup.
Click to expand...
Click to collapse
Factory reset from recovery.

Evolution_Tech said:
Factory reset from recovery.
Click to expand...
Click to collapse
if you mean this, https://support.google.com/nexus/answer/4596836?hl=en
yes. that was the first thing i did. and always the first thing i try before using any toolkits or manual repairs.
i ran Wugs again today and FINALLY got it back to the sign in screen to setup the tablet. everything was going great. then i got back into the bootloader to lock the oem. and when it restarted i'm still getting the "optimizing apps x of 99" which is annoying but it seems my tablet is at least usable for now.

Sorry to say your in the same boat as a large number of people. These devices just up and died. Take a look around for #Nexus7Bricked
Google forums will also confirm this. At this time you have a nice paperweight. I've tried all the things you have (and spent probably 10 hours over a few months) and it still won't come up.

fixed it!
vipthomps said:
Sorry to say your in the same boat as a large number of people. These devices just up and died. Take a look around for #Nexus7Bricked
Google forums will also confirm this. At this time you have a nice paperweight. I've tried all the things you have (and spent probably 10 hours over a few months) and it still won't come up.
Click to expand...
Click to collapse
i fixed it with Wugs yesterday, finally! after 5 days of trying.

this aint a phone.. Its Spawn from the darkest most vile debths of confusion!

First off i am not a noob. kinda.
the story:
I received this phone its a xt1625 prime variant (i think) already booting straight into boot loader (no system, recovery, bpmode, qmode)
just right into boot loader. So i figured it just needs flashed lets hit xda, get knowledge. it is now going on 6 months of off and on trying to flash this evil entity. this boot loader on here is like herpes, you cannot get rid of it (so i have heard). I have attempted every tutorial, downloaded every rom, twrp, firmware, etc possible to even imagine. Even tried all this in windows. ubuntu, etc. by every firmware i mean every link from here firmware.center/firmware/Motorola/Moto G4 (plus), add your own http, for every variant. and yet this boot loader remains. Even put it under a magnet from a 12' sub woofer over night. Taken the battery out for a week, overloading the chip with a car battery, nothing, the evil thing remains.
so my question is did i miss anything? also does anyone know the name and address of whomever wrote the coding for the gpt.bin,oem.img,modem,boot.img?
i'd like to have a chat with them personally.
oh and just for the record motorola will gladly replace the $159 dollar phone for $125 dollars, but have no idea how to fix it.
some of the firmware AMZ_NPJS25.93-14-7 through 14-10 will flash all the way then reboot into boot loader like nothing happened.
no blur or ota updates will flash/sideload stating that they are looking for athene and not athene_amz. yet no retail athene firmware will flash just athene_amz. absolutely no Mp firmware at all just Npjs. but only 7,8,10. which does nothing as i said before.

Can you post the get var info for this device please?
1) boot the device to bootloader
2) connect to your computer via USB
3) in the ADB terminal, type 'fastboot getvar all' without quotes and post the output here please, should be a list of device variables
Up to you if you wish to blank out the imei.

Have you unlocked your bootloader first?

motorola will not unlock the bootloader, which led me to believe its a prime.

i will do the getvar when i am home from work tonight.

and. thanks for responding

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

http://tinypic.com/r/qz554x/9

https://drive.google.com/file/d/1eF_el1N2Ve_APninuzEqvOlTSG1kSXCE/view?usp=drivesdk

those are getvar results.. or sad attempts at displaying them.

Thanks for the getvar log. According to the log:
The bootloader is locked (OEM_locked secure state), so no flashing any old ROMs. Also expected from devices with Amazon firmware, Motorola unlock keys won't work. G4 XT1625 as you mentioned
Unfortunately, the device is flashed with the latest NPJ25.93-14.7 US firmware for Amazon devices. Unfortunately we don't have access to that firmware (not been leaked on firmware.center or the Motorola Firmware Team on Android File Host), and because of the above locked bootloader, other firmware will be rejected as you've discovered. Therefore, you likely will have to wait for a leak of NPJ25.93-14.7 or later Amazon firmware for another try.
Can I ask what you mean by the device booting straight to bootloader - do you mean that powering on you'll only get the bootloader, and attempts to boot to recovery/start just send you back to the bootloader?

how would one go about formatting a phone like a hard drive just totally wipe it. Start new i am guessing it couldn't be that easy or every one would.

yes no attempt to start at all. everything leads back to fastboot mode.

its like the other partitions are not even there.

@Saul-66 as echo92 has previously said there is no latest stock images available to flash on your Amazon device,
but i have a little experiment to test,
you can try flashing older firmware but with latest gpt and Bootloader,
Also keep in mind if it boots, don't take OTA, it will brick again your device.
For safety, i will go steps by steps after confirmation of result.
First clean adb/fastboot folder if you have extracted any firmware in it, keep adb/fastboot files, or extract again in new folder, (Just for clean work and confusion)
Get OTA Update zip of September patch for Amazon device from here: https://forum.xda-developers.com/moto-g4-plus/how-to/amazon-prime-ads-moto-g4-september-t3703034
Take gpt.bin and Bootloader.img from that zip. (Delete remaining) put in adb/fastboot folder.
For now, use gpt and Bootloader commands only:
- fastboot flash partition gpt.bin
- fastboot flash bootloader bootloader.img
Tell us if those are getting flashed ?
Put screenshot of command prompt screen.
Then i will tell you next thing to go..

echo92 said:
Thanks for the getvar log. According to the log:
The bootloader is locked (OEM_locked secure state), so no flashing any old ROMs. Also expected from devices with Amazon firmware, Motorola unlock keys won't work. G4 XT1625 as you mentioned
Unfortunately, the device is flashed with the latest NPJ25.93-14.7 US firmware for Amazon devices. Unfortunately we don't have access to that firmware (not been leaked on firmware.center or the Motorola Firmware Team on Android File Host), and because of the above locked bootloader, other firmware will be rejected as you've discovered. Therefore, you likely will have to wait for a leak of NPJ25.93-14.7 or later Amazon firmware for another try.
Can I ask what you mean by the device booting straight to bootloader - do you mean that powering on you'll only get the bootloader, and attempts to boot to recovery/start just send you back to the bootloader?
Click to expand...
Click to collapse
Well if nothing else at least part of the mystery is solved. thank you for the light at the end of the tunnel!

____Mdd said:
@Saul-66 as echo92 has previously said there is no latest stock images available to flash on your Amazon device,
but i have a little experiment to test,
you can try flashing older firmware but with latest gpt and Bootloader,
Also keep in mind if it boots, don't take OTA, it will brick again your device.
For safety, i will go steps by steps after confirmation of result.
First clean adb/fastboot folder if you have extracted any firmware in it, keep adb/fastboot files, or extract again in new folder, (Just for clean work and confusion)
Get OTA Update zip of September patch for Amazon device from here: https://forum.xda-developers.com/moto-g4-plus/how-to/amazon-prime-ads-moto-g4-september-t3703034
Take gpt.bin and Bootloader.img from that zip. (Delete remaining) put in adb/fastboot folder.
For now, use gpt and Bootloader commands only:
- fastboot flash partition gpt.bin
- fastboot flash bootloader bootloader.img
Tell us if those are getting flashed ?
Put screenshot of command prompt screen.
Then i will tell you next thing to go..
Click to expand...
Click to collapse
There is no bootloader.img in Blur_Version.25.231.5.athene_amz.amz.en.US.zip
so i would have to probably take it out of ATHENE_AMZ_NPJ25.93-14.5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml ?
Edit: they both say BL:B1.06 so should be the same in theory.

Saul-66 said:
There is no bootloader.img in Blur_Version.25.231.5.athene_amz.amz.en.US.zip
so i would have to probably take it out of ATHENE_AMZ_NPJ25.93-14.5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml ?
Click to expand...
Click to collapse
In above post, you said, mystery is solved!
Then there is no need of those files right ? Or i didn't get it?
(Additionally: Bootloader wasn't updated in September patch, so it may be not included in that zip.)

____Mdd said:
In above post, you said, mystery is solved!
Then there is no need of those files right ? Or i didn't get it?
(Additionally: Bootloader wasn't updated in September patch, so it may be not included in that zip.)
Click to expand...
Click to collapse
part of the mystery is solved. tis what i said.