Deleted
Reserved
It's possible to force downgrade bootloader from 5.0 to 4.4.4, or better to 4.4.2 with this method in working devices, not bricked ones?
@Falcon G my phone still not booting on bootloader
i think this guide not work on new bootloader android 5.0
Always get it http://forum.xda-developers.com/showpost.php?p=57312495&postcount=22
dadme said:
It's possible to force downgrade bootloader from 5.0 to 4.4.4, or better to 4.4.2 with this method in working devices, not bricked ones?
Click to expand...
Click to collapse
No You shouldn't even try it you may permanently brick your device.
Sandivisi said:
@Falcon G my phone still not booting on bootloader
i think this guide not work on new bootloader android 5.0
Click to expand...
Click to collapse
It will work on 5.0 if you see qhsusb_bulk when you plug in your phone
Falcon G said:
It will work on 5.0 if you see qhsusb_bulk when you plug in your phone
Click to expand...
Click to collapse
look this pic, i follow your guide. this right?
see pic again,
and this after i run blankflash.bat
Code:
# MSM8626
[config 0x801]
programmer=programmer_8626.mbn
singleimage=singleimage_8626.bin
[config 0x805]
programmer=programmer_8926.mbn
singleimage=singleimage_8926.bin
[diag error.0x010B0C0D]
count=2
message="blank-flash:sdl-transfer-image:sdl-hello:error reading packet"
last-seen="Mon Dec 08 13:03:37 2014, SE Asia Standard Time"
first-seen="Mon Dec 08 12:29:14 2014, SE Asia Standard Time"
chip=MSM8226
chip.sn=0x306CBE3
chip.id=0x800
chip.rev=0
chip.sv-sbl=0
qboot.version=2.4
hostname=SANDY-PC
[diag blank-flash]
fail=3
pass=0
yield=0.00%
dphu=100.00
[diag error.0x010B0C13]
count=1
message="blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame"
last-seen="Mon Dec 08 13:04:29 2014, SE Asia Standard Time"
first-seen="Mon Dec 08 13:04:29 2014, SE Asia Standard Time"
chip=MSM8226
chip.sn=0x306CBE3
chip.id=0x800
chip.rev=0
chip.sv-sbl=0
qboot.version=2.4
hostname=SANDY-PC
Sandivisi said:
see pic again,
and this after i run blankflash.bat
Code:
# MSM8626
[config 0x801]
programmer=programmer_8626.mbn
singleimage=singleimage_8626.bin
[config 0x805]
programmer=programmer_8926.mbn
singleimage=singleimage_8926.bin
[diag error.0x010B0C0D]
count=2
message="blank-flash:sdl-transfer-image:sdl-hello:error reading packet"
last-seen="Mon Dec 08 13:03:37 2014, SE Asia Standard Time"
first-seen="Mon Dec 08 12:29:14 2014, SE Asia Standard Time"
chip=MSM8226
chip.sn=0x306CBE3
chip.id=0x800
chip.rev=0
chip.sv-sbl=0
qboot.version=2.4
hostname=SANDY-PC
[diag blank-flash]
fail=3
pass=0
yield=0.00%
dphu=100.00
[diag error.0x010B0C13]
count=1
message="blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame"
last-seen="Mon Dec 08 13:04:29 2014, SE Asia Standard Time"
first-seen="Mon Dec 08 13:04:29 2014, SE Asia Standard Time"
chip=MSM8226
chip.sn=0x306CBE3
chip.id=0x800
chip.rev=0
chip.sv-sbl=0
qboot.version=2.4
hostname=SANDY-PC
Click to expand...
Click to collapse
I have the same problem. I installed brazilian soak test, then set 4.4.2 and updated on OTA to 4.4.4, during installation my device is dead. Now in Task Manager Qualcomm HS-USB QDLoader 9008. Probably i think need this utility for 5.0 bootloader, MBM-CL or qboot, i do not know....
MadL1fe said:
I have the same problem. I installed brazilian soak test, then set 4.4.2 and updated on OTA to 4.4.4, during installation my device is dead. Now in Task Manager Qualcomm HS-USB QDLoader 9008. Probably i think need this utility for 5.0 bootloader, MBM-CL or qboot, i do not know....
Click to expand...
Click to collapse
maybe i give up now, because no dev or someone cant help us!
i will bought my moto g to service center motorola, tommorrow maybe
hope my device get back.
Sandivisi said:
see pic again,
and this after i run blankflash.bat
Code:
# MSM8626
[config 0x801]
programmer=programmer_8626.mbn
singleimage=singleimage_8626.bin
[config 0x805]
programmer=programmer_8926.mbn
singleimage=singleimage_8926.bin
[diag error.0x010B0C0D]
count=2
message="blank-flash:sdl-transfer-image:sdl-hello:error reading packet"
last-seen="Mon Dec 08 13:03:37 2014, SE Asia Standard Time"
first-seen="Mon Dec 08 12:29:14 2014, SE Asia Standard Time"
chip=MSM8226
chip.sn=0x306CBE3
chip.id=0x800
chip.rev=0
chip.sv-sbl=0
qboot.version=2.4
hostname=SANDY-PC
[diag blank-flash]
fail=3
pass=0
yield=0.00%
dphu=100.00
[diag error.0x010B0C13]
count=1
message="blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame"
last-seen="Mon Dec 08 13:04:29 2014, SE Asia Standard Time"
first-seen="Mon Dec 08 13:04:29 2014, SE Asia Standard Time"
chip=MSM8226
chip.sn=0x306CBE3
chip.id=0x800
chip.rev=0
chip.sv-sbl=0
qboot.version=2.4
hostname=SANDY-PC
Click to expand...
Click to collapse
Hi is this the XT1033 you are running blankflash on?
Have you unzipped all the files to a folder.
Also have you tried switching the usb cable with a different one.
Sandivisi said:
maybe i give up now, because no dev or someone cant help us!
i will bought my moto g to service center motorola, tommorrow maybe
hope my device get back.
Click to expand...
Click to collapse
In my country no motorola...
Falcon G said:
Hi is this the XT1033 you are running blankflash on?
Have you unzipped all the files to a folder.
Also have you tried switching the usb cable with a different one.
Click to expand...
Click to collapse
yes, it is on XT-1033
yes, iam also unzipped all the files to a folderbut still no work
i tired all switching the usb cable but still get some problem
I think, this guide not work on new bootloader until someone get MBM-CI from Android 5 or someone create singleimage
MadL1fe said:
In my country no motorola...
Click to expand...
Click to collapse
so just wait until someone can help us
Falcon G said:
Hi is this the XT1033 you are running blankflash on?
Have you unzipped all the files to a folder.
Also have you tried switching the usb cable with a different one.
Click to expand...
Click to collapse
Are you sure this is contains the 5.0 bootloader image or 4.4.4?
These errors the ppl get if they tried to install the OTA to 4.4.4 from 4.4.2 are due to bootloader downgrade which ofc doesnt work.Now they need the 5.0 bootloader to blankflash it and get the devices working.
Can you confirm which version you're offering in the OP?
liveroy said:
Are you sure this is contains the 5.0 bootloader image or 4.4.4?
These errors the ppl get if they tried to install the OTA to 4.4.4 from 4.4.2 are due to bootloader downgrade which ofc doesnt work.Now they need the 5.0 bootloader to blankflash it and get the devices working.
Can you confirm which version you're offering in the OP?
Click to expand...
Click to collapse
Yes it works with 5.0 boot loader (41.3 or something)
Sent from my XT1031 using Tapatalk
Falcon G said:
Yes it works with 5.0 boot loader (41.3 or something)
Sent from my XT1031 using Tapatalk
Click to expand...
Click to collapse
Nope.
OKAY [ 1.815s]
identifying device
...serial = 0x23EC8AD
...chip-id = 0x800 (MSM8226)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.007s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.003s]
validating files
OKAY [ 0.026s]
switching to download mode
OKAY [ 0.001s]
greeting device for image downloading
OKAY [ 0.002s]
sending programmer
OKAY [ 0.011s]
flashing singleimage
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet)
My bootloader v 0x4816.
i have just updated to lollipop based on 1064 firware.
i got 1068.
Is my bootloader for lollipop
It don't work, please advice.... http://forum.xda-developers.com/moto-g/help/dead-moto-g-xt1032-lollipop-downgrade-t2966996
This works to a small degree. It fixes the brick part and gets to boot-loader, but that's as far as it'll go. It'll give either a "Permission Denied" or a "Preflash Validation Failed" or a "Remote Failure" for every and any file you try to flash or boot into afterwards, be it in fastboot or mfastboot.
Code:
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot devices
a0918259 fastboot
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot flash bootl
oader motoboot.img
target max-sparse-size: 256MB
sending 'bootloader' (1953 KB)...
OKAY [ 0.100s]
writing 'bootloader'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.127s
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot flash parti
tion gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.023s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.367s
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>fastboot boot recover
y.img
downloading 'boot.img'...
OKAY [ 0.339s]
booting...
FAILED (remote failure)
finished. total time: 0.343s
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot boot recove
ry.img
downloading 'boot.img'...
OKAY [ 0.342s]
booting...
FAILED (remote failure)
finished. total time: 0.346s
VictoriousShooter said:
This works to a small degree. It fixes the brick part and gets to boot-loader, but that's as far as it'll go. It'll give either a "Permission Denied" or a "Preflash Validation Failed" or a "Remote Failure" for every and any file you try to flash or boot into afterwards, be it in fastboot or mfastboot.
Code:
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot devices
a0918259 fastboot
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot flash bootl
oader motoboot.img
target max-sparse-size: 256MB
sending 'bootloader' (1953 KB)...
OKAY [ 0.100s]
writing 'bootloader'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.127s
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot flash parti
tion gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.023s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.367s
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>fastboot boot recover
y.img
downloading 'boot.img'...
OKAY [ 0.339s]
booting...
FAILED (remote failure)
finished. total time: 0.343s
C:\Users\Ian\Desktop\RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml\
RETAIL-BR-DS_4.4.4_KXB21.14-L1.40_38_cid12_CFC_1FF_SVC.xml>mfastboot boot recove
ry.img
downloading 'boot.img'...
OKAY [ 0.342s]
booting...
FAILED (remote failure)
finished. total time: 0.346s
Click to expand...
Click to collapse
man u atleast got to fastboot but we are still stuck on blank screen...btw did u flash the lollipop ota? wer u on 4.4.4 bootloader or 5.0 bootloadeR?
Related
My N7 "2012" kept freezing, so I put it in bootloader and tried to do a recovery mode reset to stock. It froze during the process.
Now, the only thing I can do is get it into bootloader mode manually by holding the buttons. It frezes if I choose any of the options from the bootloader screen including restarting the bootloader from the bootloader screen without holding power and volume.
I have tried the Nexus Root Toolkit a bunch of times with the "flash stock + unroot (soft bricked)" feature, testing different factory builds and the best results are below:
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 2.526s]
finished. total time: 2.526s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.200s]
finished. total time: 0.200s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.015s]
finished. total time: 0.015s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.015s]
finished. total time: 0.015s
sending 'bootloader' (2100 KB)...
OKAY [ 0.264s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.402s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.021s
< waiting for device >
PLEASE HELP! Keep in mind that I am a newb to messing with this stuff.
I have read forums and tried things that people suggested to others in similar situations, but I am pretty lost at this point. Keep in mind that my device is almost certainly wiped and definitely will not boot the OS.
Is your N7 the Wi-Fi or the 3G variant?
What was the name of the factory image you were trying to flash?
brad3626 said:
My N7 "2012" kept freezing, so I put it in bootloader and tried to do a recovery mode reset to stock. It froze during the process.
Now, the only thing I can do is get it into bootloader mode manually by holding the buttons. It frezes if I choose any of the options from the bootloader screen including restarting the bootloader from the bootloader screen without holding power and volume.
I have tried the Nexus Root Toolkit a bunch of times with the "flash stock + unroot (soft bricked)" feature, testing different factory builds and the best results are below:
PLEASE HELP! Keep in mind that I am a newb to messing with this stuff.
I have read forums and tried things that people suggested to others in similar situations, but I am pretty lost at this point. Keep in mind that my device is almost certainly wiped and definitely will not boot the OS.
Click to expand...
Click to collapse
After doing a bit of research, I've found out that there is a BAD version of the N7 2012 bootloader 4.23 floating around. The unsettling thing is that it's being supplied with a couple of the factory images that come straight from from the Google android devolpers page online. Anyway to make a long story short, I would try flashing the working version of the bootloader first off, then go from there with a factory reset. You can download the the working bootloader (bootloader-grouper-4.23.img) HERE --> h t t p : / / g o o . g l / q A D S A z (sorry about the spaces in the url, I'm new to the forum and can't post links yet, just delete the spaces)
BTW, its the same bootloader for N7 wifi OR 3G. md5 = df53028033c9eccf4fe5ba7bc198ce24
Here's how to install using fastboot:
1. Reboot To Your Bootloader On You Nexus 7 (Power off power button and volume down until you see bootloader screen)
2. Connect Your Nexus 7 To Your Computer
3. Open Up Command Prompt or terminal window (not sure if you are using windows/mac/linux)
4. CD to where you downloaded bootloader-grouper-4.23.img
5. Then type:
fastboot devices (to see if your N7 is connected correctly)
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
Then try the factory reset again.
If you don't have fastboot installed your computer you need it. Makes flashing your N7 a breeze... lock/unlock, custom recovery installs, going back to factory stock, all much more easy with fastboot.
You can get it from the android devolper site, h t t p : / / g o o . g l / 2 q p r for windows/mac/linux. All you need is the SDK tools, not the ADT bundle.
adomol said:
After doing a bit of research, I've found out that there is a BAD version of the N7 2012 bootloader 4.23 floating around. The unsettling thing is that it's being supplied with a couple of the factory images that come straight from from the Google android devolpers page online. Anyway to make a long story short, I would try flashing the working version of the bootloader first off, then go from there with a factory reset. You can download the the working bootloader (bootloader-grouper-4.23.img) HERE --> h t t p : / / g o o . g l / q A D S A z (sorry about the spaces in the url, I'm new to the forum and can't post links yet, just delete the spaces)
BTW, its the same bootloader for N7 wifi OR 3G. md5 = df53028033c9eccf4fe5ba7bc198ce24
Here's how to install using fastboot:
1. Reboot To Your Bootloader On You Nexus 7 (Power off power button and volume down until you see bootloader screen)
2. Connect Your Nexus 7 To Your Computer
3. Open Up Command Prompt or terminal window (not sure if you are using windows/mac/linux)
4. CD to where you downloaded bootloader-grouper-4.23.img
5. Then type:
fastboot devices (to see if your N7 is connected correctly)
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
Then try the factory reset again.
If you don't have fastboot installed your computer you need it. Makes flashing your N7 a breeze... lock/unlock, custom recovery installs, going back to factory stock, all much more easy with fastboot.
You can get it from the android devolper site, h t t p : / / g o o . g l / 2 q p r for windows/mac/linux. All you need is the SDK tools, not the ADT bundle.
Click to expand...
Click to collapse
Thank you for the help, unfortunately, it did not work.
I followed the instructions above, but the Nexus displayed "neither up nor cac partitions found" over and over
While cmd displayed:
C:\Users\Brad>fastboot devices
XXX fastboot
C:\Users\Brad>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.281s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.213s
C:\Users\Brad>fastboot devices
XXX fastboot
C:\Users\Brad>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.205s
Erovia said:
Is your N7 the Wi-Fi or the 3G variant?
What was the name of the factory image you were trying to flash?
Click to expand...
Click to collapse
Wi-Fi
I have tried every one that the NRT offered.
Just read this guide and download the latest factory image from here.
Good luck.
Erovia said:
Just read this guide and download the latest factory image from here.
Good luck.
Click to expand...
Click to collapse
I read that guide.
But that guide seems to be written with the assumption that the device can boot into the OS
No ADB device is found because I can only boot into bootloader.
That part is only for the driver installation. You can skip to the "Extract the Factory Image" part and follow it from there.
Erovia said:
That part is only for the driver installation. You can skip to the "Extract the Factory Image" part and follow it from there.
Click to expand...
Click to collapse
Following from "Extract the Factory Image" part, this is what I am getting:
C:\Users\Brad>cd \Users\brad\AppData\Local\Android\android-sdk\platform-tools
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot devices
XXX fastboot
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>adb reboot-bootlo
ader
error: device not found
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot oem unlo
ck
...
FAILED (command write failed (Unknown error))
finished. total time: 0.590s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase bo
ot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase ca
che
erasing 'cache'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase re
covery
erasing 'recovery'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.022s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase sy
stem
erasing 'system'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase us
erdata
erasing 'userdata'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.018s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot flash bo
otloader bootloader-grouper-4.23.img
error: cannot load 'bootloader-grouper-4.23.img': Invalid argument
On the bootloader screen is your bootloader shown as "locked" or "unlocked" ?
Erovia said:
On the bootloader screen is your bootloader shown as "locked" or "unlocked" ?
Click to expand...
Click to collapse
lock state - unlocked
What's the output of fastboot -w update image-nakasi-kot49h.zip ?
Erovia said:
What's the output of fastboot -w update image-nakasi-kot49h.zip ?
Click to expand...
Click to collapse
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot -w updat
e image-nakasi-kot49h.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
error: out of memory
I have no idea what this "out of memory" error is. If I were you I would restart my computer, run fastboot from a cmd opened as Admin and try out different usb ports.
Erovia said:
I have no idea what this "out of memory" error is. If I were you I would restart my computer, run fastboot from a cmd opened as Admin and try out different usb ports.
Click to expand...
Click to collapse
I restarted, ran cmd as admin and tried every USB port and got this as the result each time:
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot -w updat
e image-nakasi-kot49h.zip
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: XXX
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4992 KB)...
OKAY [ 5.460s]
writing 'boot'...
FAILED (remote: (FileWriteFailed))
finished. total time: 8.518s
The Nexus was frozen at this point and had to be manually forced to restart bootloader.
Do you have a valid warranty for the N7? I'm asking because it seems that your N7's internal memory got corrupted. I might not be right, but that's my best guess.
Erovia said:
Do you have a valid warranty for the N7? I'm asking because it seems that your N7's internal memory got corrupted. I might not be right, but that's my best guess.
Click to expand...
Click to collapse
Thanks for your help
I bought it 13 months ago (perfect timing, coincidentally, right?), so if I could find the receipt I would still be screwed.
I would still try to send it to Asus or Google. Maybe they repair it for a reasonable price.
(But if you plan to do that try to relock you bootloader with fastboot oem lock)
Erovia said:
I would still try to send it to Asus or Google. Maybe they repair it for a reasonable price.
(But if you plan to do that try to relock you bootloader with fastboot oem lock)
Click to expand...
Click to collapse
fastboot oem lock
...
(bootloader) Bootloader is locked now.
OKAY [ 36.032s]
finished. total time: 36.032s
But then the N7 freezes and after manually restarting in bootloader it is still unlocked.
Then send is as it is. You can't do any more about it.
Good luck.
** View the making of moto downgrade tool at https://youtu.be/xaJKx9Vqdjc ***
Please like and subscribe to my youtube channel to encourage me to create more tools for the members of xda ! I really really appreciate it
Moto Downgrade Tool is a tool that I have quickly created to SAFELY downgrade android marshmallow to android lollipop on the XT1541 model.
You need Python 3.5 installed to run this program !!
make sure your phone is plugged into your pc and in fastboot mode when you start the tool.
INSTALL MOTO DRIVERS BEFORE USING THE TOOL !!!!
ADB and Fastboot is included in the downgrade tool.
Please comment if you have any issues ! This tool has been tested a few times by myself on my phone. , so it is guaranteed to be able to function correctly !
XDA:DevDB Information
Moto Downgrade Utility, Tool/Utility for the Moto G 2015
Contributors
therealduff1
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2016-03-02
Last Updated 2016-03-02
Keep going on Master!
Sorry for the off topic questions
I'm searching a Rom with multi window feature + floating windows apps like last Sammy's roms for XT1541 do you know any?
Currently using last Resurrection Remix from Vatsal that have multi window but not floating windows
One off topic more:
I have XT1541 European version obtained in Spain but I'm using it in Argentina and my mobile connection (4g) its very slow
I have to change the modem or something else?
Thanks a lot mate!
Enviado desde mi XT1541 mediante Tapatalk
fedez said:
Keep going on Master!
Sorry for the off topic questions
I'm searching a Rom with multi window feature + floating windows apps like last Sammy's roms for XT1541 do you know any?
Currently using last Resurrection Remix from Vatsal that have multi window but not floating windows
One off topic more:
I have XT1541 European version obtained in Spain but I'm using it in Argentina and my mobile connection (4g) its very slow
I have to change the modem or something else?
Thanks a lot mate!
Enviado desde mi XT1541 mediante Tapatalk
Click to expand...
Click to collapse
No need to be sorry for off topic questions !
About the rom , i am not to sure about finding a rom with floating windows , but i would like that aswell !
Also , about using a european device in a different location, this is probably due to different network bands. I would NOT reccomend you flash another models modem, as this could hard brick your phone .
I foyu have any other questions, dont hesitate to ask !
I want to downgrade from stock mm(not rooted) to LP, possible?
arun356y said:
I want to downgrade from stock mm(not rooted) to LP, possible?
Click to expand...
Click to collapse
Using my tool , yes ! . Remember not to accept ota tho
How are you doing the downgrade without having the bootloader unlocked???
Also, is this flashing EVERYTHING, including the bootloader and partition table, or is this just a tool to perform the "normal" downgrade of flashing a factory firmware image and skipping gpt.bin and bootloader.img?
therealduff1 said:
Using my tool , yes ! . Remember not to accept ota tho
Click to expand...
Click to collapse
not to accept ota, why? if in future I want to update then?
acejavelin said:
How are you doing the downgrade without having the bootloader unlocked???
Also, is this flashing EVERYTHING, including the bootloader and partition table, or is this just a tool to perform the "normal" downgrade of flashing a factory firmware image and skipping gpt.bin and bootloader.img?
Click to expand...
Click to collapse
This tool flashes SIGNED images, which means it does not need bootloader unlock. Also , it skips gpt.bin and bootloader.img . It is a normal downgrade, but i made this tool for people who dont want to risk bricking their phones typing the wrong command or accidentally flashing gpt.bin or bootloader.img
therealduff1 said:
This tool flashes SIGNED images, which means it does not need bootloader unlock. Also , it skips gpt.bin and bootloader.img . It is a normal downgrade, but i made this tool for people who dont want to risk bricking their phones typing the wrong command or accidentally flashing gpt.bin or bootloader.img
Click to expand...
Click to collapse
So if I use fastboot and flash a lp I just need to skip those 2 files right?
Downgrading from Rooted Stock MM
I have the XT1541 rooted on stock MM, can i downgrade to stock lollipop without bricking the phone ?
I also flashed the squid kernel r15b (latest)
BurningKoala said:
So if I use fastboot and flash a lp I just need to skip those 2 files right?
Click to expand...
Click to collapse
No need to use fastboot if you trust my programming . but yes , skip gpt.bin and bootloader.IMG and you will be fine my program automatically does that
Hello does my xt1541 need to be unlocked and rooted for this tool to work and downgrade from mm to lollipop?
Agiofws said:
Hello does my xt1541 need to be unlocked and rooted for this tool to work and downgrade from mm to lollipop?
Click to expand...
Click to collapse
No root needed !
Luigi_Manga said:
Ok then, I'll try tonight, does this work whit every rom despite the different number of sparsechunks?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Yes it should work perfectly
Didn't work, still on the crappy 6.0
Partition table has been skipped!
Bootloader has been skipped!
target reported max download size of 268435456 bytes
sending 'logo' (917 KB)...
OKAY [ 0.040s]
writing 'logo'...
OKAY [ 0.071s]
finished. total time: 0.114s
boot logo has been flashed
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.649s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.183s
boot.img has been flashed
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.651s]
writing 'recovery'...
OKAY [ 0.961s]
finished. total time: 1.616s
Stock lollipop recovery has now been flashed
target reported max download size of 268435456 bytes
sending 'system' (262140 KB)...
OKAY [ 10.071s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.515s
System part 1 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (262143 KB)...
OKAY [ 10.079s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.124s
System part 2 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (232632 KB)...
OKAY [ 8.988s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.060s
System part 3 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (233355 KB)...
OKAY [ 8.971s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.014s
System part 4 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (257122 KB)...
OKAY [ 9.884s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.927s
System part 5 has been flashed
target reported max download size of 268435456 bytes
sending 'system' (236089 KB)...
OKAY [ 9.090s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.124s
System part 7 has been flashed
system partitions successfully flashed
target reported max download size of 268435456 bytes
sending 'modem' (36940 KB)...
OKAY [ 1.423s]
writing 'modem'...
OKAY [ 0.994s]
finished. total time: 2.423s
Flashed Mobile Data Connection Chip Data
erasing 'modemst1'...
OKAY [ 0.019s]
finished. total time: 0.021s
erasing 'modemst2'...
OKAY [ 0.014s]
finished. total time: 0.015s
Old data erased
target reported max download size of 268435456 bytes
sending 'fsg' (2031 KB)...
OKAY [ 0.083s]
writing 'fsg'...
OKAY [ 0.083s]
finished. total time: 0.169s
Flashed FSG
erasing 'cache'...
OKAY [ 0.019s]
finished. total time: 0.021s
cache erased
erasing 'userdata'...
OKAY [ 0.199s]
finished. total time: 0.201s
userdata partition formatted
rebooting...
finished. total time: 0.006s
flash finished
***PLEASE READ BELOW***
YOU MUST NOT ACCEPT ANY OTA UPDATES ON YOUR PHONE WHILE IT IS RUNNING LOLLIPOP
OR YOU ARE RISKING A HARD BRICK DUE TO UPGRADING THE BOOTLOADER WHICH IS AT A DI
FFERENT VERSION
THAN EXPECTED
and thats all !
enjoy lollipop again!
Press any key to continue . . .
Click to expand...
Click to collapse
Sorry for the noob question but does the bootloader have to be unlocked?
BurningKoala said:
Didn't work, still on the crappy 6.0
Click to expand...
Click to collapse
Agiofws said:
Sorry for the noob question but does the bootloader have to be unlocked?
Click to expand...
Click to collapse
Downgrade using fastboot it's not possible without unlocked bootloader, that's why I think it didn't work.
coolizard said:
Downgrade using fastboot it's not possible without unlocked bootloader, that's why I think it didn't work.
Click to expand...
Click to collapse
I flashed mine using a locked bootloader
BurningKoala said:
Didn't work, still on the crappy 6.0
Click to expand...
Click to collapse
Ok right , this is a problem with the image, not my program . Are you flashing the correct image for your phone ?
therealduff1 said:
Ok right , this is a problem with the image, not my program . Are you flashing the correct image for your phone ?
Click to expand...
Click to collapse
Yes, I flashed the xt1541 vodafone EU that was on my phone (now I'm on vodafone 6.0), did you think that it's better I flash the no brand eu version?
edit: same errors with the retail eu
HI,
i used this method to root my moto x style (xt1572) indian
after that
wifi stopped working....its like it stuck in off mode.....doesnt turn on
i did some researching n found that it had to do somthing with modem file
downloaded firmware from this link
http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
i flashed only the modem file but didnt worked
i tried to completely flash stock firmware
got this error
mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.364s
tried to do with locking bootloader
got this error
Please fully flash the signed build before locking phone
pls help
thnx
First install drivers and fastboot file and this get bootloader mod and then press volume up to bootloader logo and connect your dives into PC and use fastboot commands in the firmware software in the development don't forget USB debugging on and OEM unlock on and start
Sent from my XT1575 using XDA Free mobile app
[email protected] said:
HI,
i used this method to root my moto x style (xt1572) indian
after that
wifi stopped working....its like it stuck in off mode.....doesnt turn on
i did some researching n found that it had to do somthing with modem file
downloaded firmware from this link
http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
i flashed only the modem file but didnt worked
i tried to completely flash stock firmware
got this error
mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.364s
tried to do with locking bootloader
got this error
Please fully flash the signed build before locking phone
pls help
thnx
Click to expand...
Click to collapse
Hi, I'm getting that as well, I think it's because I got the february update OTA, which changed partitions. Now I just skip flashing gpt bin and go with the rest. It flashes fine and then I install the OTA February update.
[email protected] said:
HI,
i used this method to root my moto x style (xt1572) indian
after that
wifi stopped working....its like it stuck in off mode.....doesnt turn on
i did some researching n found that it had to do somthing with modem file
downloaded firmware from this link
http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
i flashed only the modem file but didnt worked
i tried to completely flash stock firmware
got this error
mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.364s
tried to do with locking bootloader
got this error
Please fully flash the signed build before locking phone
pls help
thnx
Click to expand...
Click to collapse
Download this firmware : http://firmware.center/firmware/Mot...S24.49-18-3_cid12_subsidy-DEFAULT_CFC.xml.zip
If you have root with systemless flashing boot.img, then wifi will not work, you need flash original boot and you will not be root, actual solution for rooting, is for europe roms.
OFFICIAL Build MOTO G 2014,XT1068 Marshmallow 6.0 Stock ROM Indian version
Install stock Marshmallow XT1068 by just a single click.
Downloads:
https://drive.google.com/open?id=0B1DHXoau_BBLQ0huYnF4amNuNk0 [Easy Installer]
https://drive.google.com/open?id=0B1DHXoau_BBLS0NBeENMZDJaa28 [Instructions to Install]
Instructions to Install:
Please follow the readme.txt file attached.
What's Working:
Everything!
What's Not Working:
You tell me!
Version Information:
Build Number : MPB24.65-34
System Version : 24.41.34 titan retaildsds.retaildsdsall.en.03 retin
ROM OS Version: 6.0 Marshmallow
Based On: Stock Motorola OS
Status: Stable
Thanks:
Motorola
Lenovo
Special thanks to @reefuge for his easy installer batch file
IF YOU THINK I HELPED YOU PLEASE PRESS THE THANKS BUTTON THAT WON'T COST YOU A THING
Image is too large messgae
Hi,
I followed the steps provided in the readme doc and when I run the EASY INSTALLER.bat file and select option 1, I am consistently seeing 'Image is too large' on my phone screen when in AP Fastboot Flash Mode. If after waiting for this process I exit using option 6 and attempt to reboot my phone then my phone always boots into AP Fastboot Flash Mode with the following message:
Fastboot Reason: Fall-through from normal boot mode
How do I get my phone to boot? I take it the images failed to write and the phone no longer has a ROM to use, is this correct? Any help would be much appreciated.
My installer.bat output is as follows when selecting option 1:
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option : 1
RETURNING TO STOCK ROM - FLASH
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Preflash validati
FAILED (remote failure)
finished. total time: 0.125s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)..
OKAY [ 0.125s]
writing 'motoboot'...
(bootloader) Motoboot: Preflas
(bootloader) Preflash validati
FAILED (remote failure)
finished. total time: 0.187s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.094s]
writing 'logo'...
OKAY [ 0.094s]
finished. total time: 0.187s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.374s]
finished. total time: 0.780s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB).
OKAY [ 0.421s]
writing 'recovery'...
(bootloader) Image size exeede
(bootloader) image size exceed
(bootloader) Failed to flash p
FAILED (remote failure)
finished. total time: 0.484s
FLASHING SYSTEM IMAGE IN MULTI
target max-sparse-size: 256MB
sending 'system' (257467 KB)..
OKAY [ 8.410s]
writing 'system'...
OKAY [ 8.932s]
finished. total time: 17.342s
target max-sparse-size: 256MB
sending 'system' (255482 KB)..
OKAY [ 8.289s]
writing 'system'...
OKAY [ 9.417s]
finished. total time: 17.722s
target max-sparse-size: 256MB
sending 'system' (257534 KB)..
OKAY [ 8.394s]
writing 'system'...
OKAY [ 7.904s]
finished. total time: 16.298s
target max-sparse-size: 256MB
sending 'system' (244425 KB)..
OKAY [ 7.879s]
writing 'system'...
(bootloader) Invalid sparse im
(bootloader) Failed to flash s
FAILED (remote failure)
finished. total time: 10.388s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (50136 KB)...
OKAY [ 1.677s]
writing 'modem'...
OKAY [ 1.468s]
finished. total time: 3.145s
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
erasing 'modemst2'...
OKAY [ 0.047s]
finished. total time: 0.047s
target max-sparse-size: 256MB
sending 'fsg' (652 KB)...
OKAY [ 0.109s]
writing 'fsg'...
OKAY [ 5.651s]
finished. total time: 5.760s
ERASING CACHE ......
erasing 'cache'...
OKAY [ 0.366s]
finished. total time: 0.366s
Check your model no.
And if it is correct:
DOWNGRADING from Custom ROM or HIGHER version of STOCK ROM OPTIONS 5,1,3,5,4,6
sanketmsonar said:
Check your model no.
And if it is correct:
DOWNGRADING from Custom ROM or HIGHER version of STOCK ROM OPTIONS 5,1,3,5,4,6
Click to expand...
Click to collapse
Sorry but this sortware is for which country? Is it compatible with UK DS ?
garyben60 said:
Sorry but this sortware is for which country? Is it compatible with UK DS ?
Click to expand...
Click to collapse
Only for Indian device
Please answer
if i flash to stock rom..the twrp will get delete..? the phone will turn back to unrooted..? should i wipe all the cache and system files before installing this rom?
thanks in advance..:good:
iajinkya said:
if i flash to stock rom..the twrp will get delete..? the phone will turn back to unrooted..? should i wipe all the cache and system files before installing this rom?
thanks in advance..:good:
Click to expand...
Click to collapse
TWRP will get replaced by stock recovery and phone will get unrooted,you can wipe cache and system before installing
sanketmsonar said:
TWRP will get replaced by stock recovery and phone will get unrooted,you can wipe cache and system before installing
Click to expand...
Click to collapse
thanks..bro..:good:
when installing this file will it also upgrade my bootloader version from v48.83 to 48.86??
Help devs WiFi won't turn on there is no persist folder in root need to a WiFi fix
Try clean flashing
akashbhosale said:
Help devs WiFi won't turn on there is no persist folder in root need to a WiFi fix
Click to expand...
Click to collapse
Try clean flashing again...
1) Install TWRP recovery
2)Go to wipe > advance wipe > dalvik, cache, system, data
3)Turn off phone > Go to recovery mode (hold volume down + power)
4)Connect to PC with proper drivers installed
5) Run the installer again
Hope this fixes...waiting for your reply
Cheers
I have locked bootloader with stock marshmallow. Can I use this method to reinstall marshmallow
koboji said:
I have locked bootloader with stock marshmallow. Can I use this method to reinstall marshmallow
Click to expand...
Click to collapse
For the safer side you should unlock the bootloader because the bootloader itself is a firmware which is OS dependent and some bootloader versions wont work for 6.0.
go to http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818
Dont worry its just 10 mins work.. Happy flashing dude
Click Thanks if it helped
upgrading from custom rom 4.4.4 to 6.0
sanketmsonar said:
Only for Indian device
Click to expand...
Click to collapse
i also want to upgrade my moto g2014 from custom rom 4.4.4 to 6.0 marshmallow, will there be any kind of problem or my mobile will get dead during this process? pls help, my handset is an indian device.
Hi. I have MotoG2 XT 1068 in India. I want to know how to get VoLTE and 4G from Reliance Jio on my MotoG2. Please let em know any ROM which will work for this. Thanks
clive48 said:
Hi. I have MotoG2 XT 1068 in India. I want to know how to get VoLTE and 4G from Reliance Jio on my MotoG2. Please let em know any ROM which will work for this. Thanks
Click to expand...
Click to collapse
An XT1068 doesn't support 4g/LTE.
Send with my Moto G4 Plus with CM13 (XT1642) using Tapatalk!
I m on turbo rom MM 6.0.1 and want to flash stock MM but without relocking bootloader so which steps i have to follow and more querry will my touch bug problem resolved after flashing this rom bcoz for last 2 month i have encountered with this touch problem before that my Stock MM works flawlessly
Sent from my Moto G 2014 using Tapatalk
chandan kumar_92 said:
I m on turbo rom MM 6.0.1 and want to flash stock MM but without relocking bootloader so which steps i have to follow and more querry will my touch bug problem resolved after flashing this rom bcoz for last 2 month i have encountered with this touch problem before that my Stock MM works flawlessly
Click to expand...
Click to collapse
I am on stock MM and touch problem is killing me.I even installed lollipop but no benefit. Now i am gonna try some custom roms
koboji said:
I am on stock MM and touch problem is killing me.I even installed lollipop but no benefit. Now i am gonna try some custom roms
Click to expand...
Click to collapse
I have same problem bro after trying lots of custom ROM now I am on cm 13 and it eliminated my touch latency issue try it...
A biiiiiiiiiiiiiiiiiiiiiiig Thanks
I had trouble with "No Service" with brazilian version.
You made my device restored to normal situation.
Thanks a TON.
I can not unbricked my phone using old methods , I need new bootloader for February security patch updated device.
Same here I am also need 2018 Feb NPJS25.93.14-15. please help
Moto g4 Bricked said:
Same here I am also need 2018 Feb NPJS25.93.14-15. please help
Click to expand...
Click to collapse
Is your phone showing fastboot menu?
Have you tried the blankflash from this guide here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
I have tried blank flash.
the problem is when flash partition from ATHENE_NPJS25.93-14-13_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
, I got error message:
>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.091s
I am not sure if ATHENE_NPJS25.93-14-15 will work, and I can not found it.
echo92 said:
Have you tried the blankflash from this guide here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Click to expand...
Click to collapse
I have found ATHENE_NPJS25.93-14-15 here, but I am not able to test it now.
Can Anyone test it and report progress?
https://drive.google.com/file/d/1J31aHAQ7wAY2Qqy1U-9m8VtugD2XUtiw/view
llaalways said:
I have tried blank flash.
the problem is when flash partition from ATHENE_NPJS25.93-14-13_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
, I got error message:
>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.091s
I am not sure if ATHENE_NPJS25.93-14-15 will work, and I can not found it.
Click to expand...
Click to collapse
my phone is rescued.
llaalways said:
I have found ATHENE_NPJS25.93-14-15 here, but I am not able to test it now.
Can Anyone test it and report progress?
https://drive.google.com/file/d/1J31aHAQ7wAY2Qqy1U-9m8VtugD2XUtiw/view
Click to expand...
Click to collapse