Hi guys,
So I major noob screwed up after spending 2 years on iOS and coming back and thinking I remembered how to flash!
I've got an A9 from Taiwan and it's the htc_hiaeuhl 1.10.709.7 version.
I wanted to flash the phone with a UK/Euro ruu but I've accidentally erased the system.
I've managed to find the original ruu but I just can't fastboot flash the system.img as it keeps returning the "cannot load system.img: not enough space" error.
Bootloader's unlocked, got TWRP installed, and I get the "No OS Installed!" message so it's definitely all gone. Also I get "E: Unable to mount '/system' and it looks like there's nothing left on the phone, no folders or anything :-/
Device is still S-on, so I think I'm kinda screwed.
Any ideas how I can get the system.img back on at least? Preferably a different RUU that has English UK as an option?
Thanks and apologies for the noobity -_-
i_maq said:
Hi guys,
So I major noob screwed up after spending 2 years on iOS and coming back and thinking I remembered how to flash!
I've got an A9 from Taiwan and it's the htc_hiaeuhl 1.10.709.7 version.
I wanted to flash the phone with a UK/Euro ruu but I've accidentally erased the system.
I've managed to find the original ruu but I just can't fastboot flash the system.img as it keeps returning the "cannot load system.img: not enough space" error.
Bootloader's unlocked, got TWRP installed, and I get the "No OS Installed!" message so it's definitely all gone. Also I get "E: Unable to mount '/system' and it looks like there's nothing left on the phone, no folders or anything :-/
Device is still S-on, so I think I'm kinda screwed.
Any ideas how I can get the system.img back on at least? Preferably a different RUU that has English UK as an option?
Thanks and apologies for the noobity -_-
Click to expand...
Click to collapse
If you are using windows operating system then also installed HTC Sync Manager.
You can find the adb tool in this position.
C: \ Program Files (x86) \ HTC \ HTC Sync Manager \ HTC Sync
Install the new version of HTC Sync Manager to use HTC Sync adb tool to try again flash system.img
nenebear said:
If you are using windows operating system then also installed HTC Sync Manager.
You can find the adb tool in this position.
C: \ Program Files (x86) \ HTC \ HTC Sync Manager \ HTC Sync
Install the new version of HTC Sync Manager to use HTC Sync adb tool to try again flash system.img
Click to expand...
Click to collapse
I've got the new version installed, how do I use the ADB function from there? I'm assuming you mean a specific function from the program and not just the usual ADB push the rom to the phone?
Update: HTC Sync keeps crashing and closing itself :-/
i_maq said:
I've got the new version installed, how do I use the ADB function from there? I'm assuming you mean a specific function from the program and not just the usual ADB push the rom to the phone?
Update: HTC Sync keeps crashing and closing itself :-/
Click to expand...
Click to collapse
I think he's just assuming you don't know how to find adb... yes it comes with the sync manager. Same one as the one in the sdk at C:\Users\(username)\AppData\Local\Android\android-sdk\platform-tools. No special function. I think fastboot flash system (system.img) is your only option. or find a /system backup if you have twrp working.
gunnarrrrr said:
I think he's just assuming you don't know how to find adb... yes it comes with the sync manager. Same one as the one in the sdk at C:\Users\(username)\AppData\Local\Android\android-sdk\platform-tools. No special function. I think fastboot flash system (system.img) is your only option. or find a /system backup if you have twrp working.
Click to expand...
Click to collapse
Yeah I've tried to adb push the rom, I've tried fastboot flashing the system.img, I've tried official HTC RUU.exe's but I can't find the one that matches my device so I'm getting error 155 and 153, I relocked my bootloader but RUU's don't work.
TWRP doesn't restore backups because I can't push the system.img as it says I don't have enough space. Basically nothing I've read up on seems to be working.
The main issue is that I can't flash system.img as it keeps giving me the "cannot load system.img: not enough space" error in cmd:
{
"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"
}
If I can JUST get the system flashed back, I can at least boot up the phone and try and S-off, but I'm stuck with no system at the moment so it bootloops to the bootloader.
i_maq said:
Yeah I've tried to adb push the rom, I've tried fastboot flashing the system.img, I've tried official HTC RUU.exe's but I can't find the one that matches my device so I'm getting error 155 and 153, I relocked my bootloader but RUU's don't work.
TWRP doesn't restore backups because I can't push the system.img as it says I don't have enough space. Basically nothing I've read up on seems to be working.
The main issue is that I can't flash system.img as it keeps giving me the "cannot load system.img: not enough space" error in cmd:
If I can JUST get the system flashed back, I can at least boot up the phone and try and S-off, but I'm stuck with no system at the moment so it bootloops to the bootloader.
Click to expand...
Click to collapse
Try this RUU http://dl3.htc.com/application/RUU_HIA_AERO_UL_M60_SENSE7GP_ATT_NA_Gen_Unlock_1.12.617.6.exe
gunnarrrrr said:
Try this RUU http://dl3.htc.com/application/RUU_HIA_AERO_UL_M60_SENSE7GP_ATT_NA_Gen_Unlock_1.12.617.6.exe
Click to expand...
Click to collapse
Thanks, already tried that one, I get Error 132 as it's for 1.12.616.7 devices and my device is the htc_hiaeuhl 1.10.709.7 version.
i_maq said:
I've got the new version installed, how do I use the ADB function from there? I'm assuming you mean a specific function from the program and not just the usual ADB push the rom to the phone?
Update: HTC Sync keeps crashing and closing itself :-/
Click to expand...
Click to collapse
What we need is htc sync folder within fastboot.exe & htc_fastboot.lib. You can also copy the folder to HTC Sync out as adb tool.
Code:
D:\HTC_A9_1.10.709.7_Images_OTA>adb reboot download
D:\HTC_A9_1.10.709.7_Images_OTA>fastboot erase system
htc_fastboot v3.0.9.2 (2015-05-29)
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.594s]
finished. total time: 0.594s
htc_fastboot finished. total time: 0.669s
D:\HTC_A9_1.10.709.7_Images_OTA>fastboot erase boot
htc_fastboot v3.0.9.2 (2015-05-29)
erasing 'boot'...
OKAY [ 0.031s]
finished. total time: 0.031s
htc_fastboot finished. total time: 0.133s
D:\HTC_A9_1.10.709.7_Images_OTA>fastboot erase recovery
htc_fastboot v3.0.9.2 (2015-05-29)
erasing 'recovery'...
OKAY [ 0.032s]
finished. total time: 0.032s
htc_fastboot finished. total time: 0.106s
D:\HTC_A9_1.10.709.7_Images_OTA>fastboot flash system system.img
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 800000000 bytes
erasing 'system'...
OKAY [ 0.037s]
sending sparse 'system' (769349 KB)...
OKAY [ 45.440s]
writing 'system'...
(bootloader) HOSD CL#635503
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 24.290s]
sending sparse 'system' (778039 KB)...
OKAY [ 46.052s]
writing 'system'...
(bootloader) HOSD CL#635503
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 24.160s]
sending sparse 'system' (781045 KB)...
OKAY [ 46.380s]
writing 'system'...
(bootloader) HOSD CL#635503
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 25.153s]
sending sparse 'system' (643812 KB)...
OKAY [ 38.497s]
writing 'system'...
(bootloader) HOSD CL#635503
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 21.155s]
finished. total time: 271.165s
htc_fastboot finished. total time: 275.494s
D:\HTC_A9_1.10.709.7_Images_OTA>fastboot flash boot boot.img
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 798000000 bytes
sending 'boot' (45797 KB)...
OKAY [ 3.700s]
writing 'boot'...
(bootloader) HOSD CL#635503
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.345s]
finished. total time: 7.046s
htc_fastboot finished. total time: 7.170s
D:\HTC_A9_1.10.709.7_Images_OTA>fastboot flash recovery recovery.img
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 800000000 bytes
sending 'recovery' (47227 KB)...
OKAY [ 3.592s]
writing 'recovery'...
(bootloader) HOSD CL#635503
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.190s]
finished. total time: 6.782s
htc_fastboot finished. total time: 6.990s
Download mode -- factory reset or recovery mode -- wipe data/factory reset
Reboot into android can receive OTA to 1.10.709.9 & 1.27.709.5
nenebear said:
What we need is htc sync folder within fastboot.exe & htc_fastboot.lib. You can also copy the folder to HTC Sync out as adb tool.
Code:
D:\HTC_A9_1.10.709.7_Images_OTA>adb reboot download
D:\HTC_A9_1.10.709.7_Images_OTA>fastboot erase system
htc_fastboot v3.0.9.2 (2015-05-29)
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.594s]
finished. total time: 0.594s
htc_fastboot finished. total time: 0.669s
D:\HTC_A9_1.10.709.7_Images_OTA>fastboot erase boot
htc_fastboot v3.0.9.2 (2015-05-29)
erasing 'boot'...
OKAY [ 0.031s]
finished. total time: 0.031s
htc_fastboot finished. total time: 0.133s
D:\HTC_A9_1.10.709.7_Images_OTA>fastboot erase recovery
htc_fastboot v3.0.9.2 (2015-05-29)
erasing 'recovery'...
OKAY [ 0.032s]
finished. total time: 0.032s
htc_fastboot finished. total time: 0.106s
D:\HTC_A9_1.10.709.7_Images_OTA>fastboot flash system system.img
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 800000000 bytes
erasing 'system'...
OKAY [ 0.037s]
sending sparse 'system' (769349 KB)...
OKAY [ 45.440s]
writing 'system'...
(bootloader) HOSD CL#635503
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 24.290s]
sending sparse 'system' (778039 KB)...
OKAY [ 46.052s]
writing 'system'...
(bootloader) HOSD CL#635503
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 24.160s]
sending sparse 'system' (781045 KB)...
OKAY [ 46.380s]
writing 'system'...
(bootloader) HOSD CL#635503
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 25.153s]
sending sparse 'system' (643812 KB)...
OKAY [ 38.497s]
writing 'system'...
(bootloader) HOSD CL#635503
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 21.155s]
finished. total time: 271.165s
htc_fastboot finished. total time: 275.494s
D:\HTC_A9_1.10.709.7_Images_OTA>fastboot flash boot boot.img
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 798000000 bytes
sending 'boot' (45797 KB)...
OKAY [ 3.700s]
writing 'boot'...
(bootloader) HOSD CL#635503
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.345s]
finished. total time: 7.046s
htc_fastboot finished. total time: 7.170s
D:\HTC_A9_1.10.709.7_Images_OTA>fastboot flash recovery recovery.img
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 800000000 bytes
sending 'recovery' (47227 KB)...
OKAY [ 3.592s]
writing 'recovery'...
(bootloader) HOSD CL#635503
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.190s]
finished. total time: 6.782s
htc_fastboot finished. total time: 6.990s
Download mode -- factory reset or recovery mode -- wipe data/factory reset
Reboot into android can receive OTA to 1.10.709.9 & 1.27.709.5
Click to expand...
Click to collapse
You sir, are an absolute genius! It worked! I'm back in
Now my next challenge is flashing a UK rom, I've got the file from this thread: http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
And I'd like to flash this version:
H3G UK
modelid: 2PQ910000
cidnum: H3G__001
cidnum: H3G__G04
cidnum: H3G__106
cidnum: H3G__003
Is there any way I can extract the system.img and boot from that and use the htcfastboot to flash it straight to the device? Or do I need to s-off first and then install via recovery?
i_maq said:
You sir, are an absolute genius! It worked! I'm back in
Now my next challenge is flashing a UK rom, I've got the file from this thread: http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
And I'd like to flash this version:
H3G UK
modelid: 2PQ910000
cidnum: H3G__001
cidnum: H3G__G04
cidnum: H3G__106
cidnum: H3G__003
Is there any way I can extract the system.img and boot from that and use the htcfastboot to flash it straight to the device? Or do I need to s-off first and then install via recovery?
Click to expand...
Click to collapse
HIA_AERO_UHL_hTC_Asia_TW HTC A9u is an international version.If you want to flash RUU.zip elsewhere.You need to s-off first and modify the CID 11111111
Because you are in Taiwan to buy HTC A9. I will try to help you sort out the H3G UK 1.10.771.8 images.
nenebear said:
HIA_AERO_UHL_hTC_Asia_TW HTC A9u is an international version.If you want to flash RUU.zip elsewhere.You need to s-off first and modify the CID 11111111
Because you are in Taiwan to buy HTC A9. I will try to help you sort out the H3G UK 1.10.771.8 images.
Click to expand...
Click to collapse
I'm in the UK, I bought the Taiwan version from eBay. I appreciate that. I can't even get s-off at the moment to root.
i_maq said:
I'm in the UK, I bought the Taiwan version from eBay. I appreciate that. I can't even get s-off at the moment to root.
Click to expand...
Click to collapse
It does not matter as it was a beautiful mistake!
download : HTC_A9_H3G_UK_1.10.771.8_Images_OTA.rar
Share to people in need do not need to ask me.
i_maq said:
I'm in the UK, I bought the Taiwan version from eBay. I appreciate that. I can't even get s-off at the moment to root.
Click to expand...
Click to collapse
You have to root first, then s-off.
nenebear said:
It does not matter as it was a beautiful mistake!
download : HTC_A9_H3G_UK_1.10.771.8_Images_OTA.rar
Share to people in need do not need to ask me.
Click to expand...
Click to collapse
Ah man you're a legend! Thanks so much, that's worked!
Similar problem on Xperia Z5 E6683
I tried factory reset my E6683, but overdid it (in TWRP) and wiped out all of the data.
There is no OS currently, I cannot reflash the stock RU.ftf using Flashtools. Only fastboot is left as an option. I have extracted system.sin (2.1 GB!) but flashtools just hanged while flashing it in fastboot mode. Then I switched to ADB, renamed sin to img and got similar error message: cannot load 'system.img'. I have only AdbWinUsbApi.dll and AdbWinApi.dll with fastboot.exe and adb.exe.
Do I miss other files?
I would greatly appreciate your advice!
efrecska
Are you aware that this is an HTC One A9 forum?
Στάλθηκε από το HTC One A9 μου χρησιμοποιώντας Tapatalk
efrecska said:
I tried factory reset my E6683, but overdid it (in TWRP) and wiped out all of the data.
There is no OS currently, I cannot reflash the stock RU.ftf using Flashtools. Only fastboot is left as an option. I have extracted system.sin (2.1 GB!) but flashtools just hanged while flashing it in fastboot mode. Then I switched to ADB, renamed sin to img and got similar error message: cannot load 'system.img'. I have only AdbWinUsbApi.dll and AdbWinApi.dll with fastboot.exe and adb.exe.
Do I miss other files?
I would greatly appreciate your advice!
efrecska
Click to expand...
Click to collapse
Hey buddy, this is the HTC One A9 forum so you might not be able to find the exact solution for your phone, might have better luck getting the specific files you need in the Z5 Forums here: http://forum.xda-developers.com/xperia-z5
I was about to throw my A9u in the garbage. Thank god I saw this post 1st. One of the best step by step write up. Got my device up and running again. Two BIG THUMBS up
nenebear said:
It does not matter as it was a beautiful mistake!
download : HTC_A9_H3G_UK_1.10.771.8_Images_OTA.rar
Share to people in need do not need to ask me.
Click to expand...
Click to collapse
So if i'm in the US and want to flash this one, How can I do that? HTC USA Unlocked 1.57.617.32 I also have the One A9u
nenebear said:
What we need is htc sync folder within fastboot.exe & htc_fastboot.lib. You can also copy the folder to HTC Sync out as adb tool.
Code:
D:\HTC_A9_1.10.709.7_Images_OTA>adb reboot download
D:\HTC_A9_1.10.709.7_Images_OTA>fastboot erase system
htc_fastboot v3.0.9.2 (2015-05-29)
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.594s]
finished. total time: 0.594s
htc_fastboot finished. total time: 0.669s
D:\HTC_A9_1.10.709.7_Images_OTA>fastboot erase boot
htc_fastboot v3.0.9.2 (2015-05-29)
erasing 'boot'...
OKAY [ 0.031s]
finished. total time: 0.031s
htc_fastboot finished. total time: 0.133s
D:\HTC_A9_1.10.709.7_Images_OTA>fastboot erase recovery
htc_fastboot v3.0.9.2 (2015-05-29)
erasing 'recovery'...
OKAY [ 0.032s]
finished. total time: 0.032s
htc_fastboot finished. total time: 0.106s
D:\HTC_A9_1.10.709.7_Images_OTA>fastboot flash system system.img
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 800000000 bytes
erasing 'system'...
OKAY [ 0.037s]
sending sparse 'system' (769349 KB)...
OKAY [ 45.440s]
writing 'system'...
(bootloader) HOSD CL#635503
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 24.290s]
sending sparse 'system' (778039 KB)...
OKAY [ 46.052s]
writing 'system'...
(bootloader) HOSD CL#635503
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 24.160s]
sending sparse 'system' (781045 KB)...
OKAY [ 46.380s]
writing 'system'...
(bootloader) HOSD CL#635503
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 25.153s]
sending sparse 'system' (643812 KB)...
OKAY [ 38.497s]
writing 'system'...
(bootloader) HOSD CL#635503
(bootloader) [email protected]
(bootloader) s[email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 21.155s]
finished. total time: 271.165s
htc_fastboot finished. total time: 275.494s
D:\HTC_A9_1.10.709.7_Images_OTA>fastboot flash boot boot.img
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 798000000 bytes
sending 'boot' (45797 KB)...
OKAY [ 3.700s]
writing 'boot'...
(bootloader) HOSD CL#635503
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.345s]
finished. total time: 7.046s
htc_fastboot finished. total time: 7.170s
D:\HTC_A9_1.10.709.7_Images_OTA>fastboot flash recovery recovery.img
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 800000000 bytes
sending 'recovery' (47227 KB)...
OKAY [ 3.592s]
writing 'recovery'...
(bootloader) HOSD CL#635503
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.190s]
finished. total time: 6.782s
htc_fastboot finished. total time: 6.990s
Download mode -- factory reset or recovery mode -- wipe data/factory reset
Reboot into android can receive OTA to 1.10.709.9 & 1.27.709.5
Click to expand...
Click to collapse
Hi, Could you please explain I would achieve this?? My phone updated to 6.01 marshmallow and now the wifi module is missing and the battery percentage is at 4000%, I was told i should reflash my device but I can't find a ruu file for it, do you know how I can do this. Im in Canada and my phone is from Taiwan. 1.56.709.70
Thank you
Related
Requirements :
ADB Drivers
Fastboot
Moto G Stock Firmware
Downlaods :
ADB & Fastboot Setup - https://drive.google.com/file/d/0BxE4PACUiwQqVkxCOTJBZ29WNnc/view?usp=sharing
Unbrick Zip - https://drive.google.com/file/d/0BxE4PACUiwQqN0xvOGpJMUg5MVU/view?usp=sharing
CWM Touch Recovery - https://drive.google.com/file/d/0BxE4PACUiwQqbXFpU25Eb3lIWkE/view?usp=sharing
PAC-MAN ROM with GApps - http://forum.xda-developers.com/showthread.php?t=2667834
Credits : Firmware Team
CWM
Carlos Spitzer
If your phone doesn't turn on after the battery dies, then keep the power button pressed till you see the battery icon. Always connect to a wall charger if the battery is dead after the phone is hard bricked.
Method :
To Enter Fastboot :
1) When your phone is turned off, press the power key and volume down button for around 5-10 seconds and let it go.
2) Connect your phone to your pc via usb.
3) Install the setup provided in the link and press "y" in the window.
To Flash Firmware :
3) Extract the zip which contains a batch file "unbrick.bat", 5.0.2 Firmware & Fastboot.
4) Run the batch file "unbrick.bat"
If your phone is still stuck in a bootloop, I would recommend you to first flash the CWM Recovery using fastboot.
Then, you can sideload a ROM (I used PAC-MAN) using ADB. Then just flash the ROM in CWM. If you need stock, then follow the above steps after successfully booting into PAC-MAN ROM. I have provided all the links above.
That's it, you are done!
The Only Worked Tutorial
this is the only worked tutorial for me. i have tried many tutorials it seems not workin at all.luvd it:good:
I'm glad it worked
Sent from my XT1033 using XDA Free mobile app
Major problems with my XT1033
Hello, please help. I have tried to follow your instructions to unbrick my Moto G XT1033 but I just get the message in the Command Prompt that fastboot is not recognised.
I think my phone was accidently disconnected from the pc when I was trying to flash back to stock firmware from CM11. Since then the phone will not shut down & only shows 0% battery when connected to the mains. It only charges the battery when connected to the PC. I can get to the fastboot screen (please see attached images) & as can be seen the phone confirms usb is connected but the phone is not recognised by the PC. Please help. I have tried all other methods without any success.
Regards
Brian
You did it for me
:good:
Eventually I managed to get fastboot recognised & followed your instructions even though the first few commands seemed to FAIL I continued and I now have a fully working Moto G XT1033
THANK YOU
THANK YOU
THANK YOU
YOU ARE THE BEST. I SHOULD HAVE TRIED YOUR INSTRUCTIONS FIRST BECAUSE I WAS SO DISAPPOINTED I COULDN'T UNBRICK MY MOTO G I BOUGHT A 2ND GEN MOTO G.
Kind Regards
Brian
I need a help, I am using PA and I can't get gps lock.
could anybody upload/send me NON-HLOS.bin from 4.4.4 stock image?
I lived in third world country so...... it will be a pain in the a** to download the full stock image.
edit: Got it
bfc9999 said:
:good:
Eventually I managed to get fastboot recognised & followed your instructions even though the first few commands seemed to FAIL I continued and I now have a fully working Moto G XT1033
THANK YOU
THANK YOU
THANK YOU
YOU ARE THE BEST. I SHOULD HAVE TRIED YOUR INSTRUCTIONS FIRST BECAUSE I WAS SO DISAPPOINTED I COULDN'T UNBRICK MY MOTO G I BOUGHT A 2ND GEN MOTO G.
Kind Regards
Brian
Click to expand...
Click to collapse
Never lose hope
Great Tutorial. But I had Network issue and that's why i flashed it.
It was not fixed.
But reset works fine.
Clicked Thanks
please help
:crying::crying::crying::crying::crying::crying::crying::crying:
preflash validation failed....please help....ive followed the tutorial correctly but i still end up in a bootloop.........u r my only hope
C:\Users\DRAVYA\Desktop\stock>echo
ECHO is on.
C:\Users\DRAVYA\Desktop\stock>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.297s
C:\Users\DRAVYA\Desktop\stock>fastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1940 KB)...
OKAY [ 0.094s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.359s
C:\Users\DRAVYA\Desktop\stock>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (619 KB)...
OKAY [ 0.063s]
writing 'logo'...
OKAY [ 0.031s]
finished. total time: 0.094s
C:\Users\DRAVYA\Desktop\stock>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.379s]
writing 'boot'...
OKAY [ 0.666s]
finished. total time: 1.045s
C:\Users\DRAVYA\Desktop\stock>echo
ECHO is on.
C:\Users\DRAVYA\Desktop\stock>echo
ECHO is on.
C:\Users\DRAVYA\Desktop\stock>echo
ECHO is on.
C:\Users\DRAVYA\Desktop\stock>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.378s]
writing 'recovery'...
OKAY [ 0.618s]
finished. total time: 0.996s
C:\Users\DRAVYA\Desktop\stock>echo
ECHO is on.
C:\Users\DRAVYA\Desktop\stock>echo
ECHO is on.
C:\Users\DRAVYA\Desktop\stock>echo
ECHO is on.
C:\Users\DRAVYA\Desktop\stock>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.031s]
sending 'system' (262142 KB)...
OKAY [ 8.476s]
writing 'system'...
OKAY [ 8.609s]
finished. total time: 17.117s
C:\Users\DRAVYA\Desktop\stock>fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.047s]
sending 'system' (237949 KB)...
OKAY [ 7.706s]
writing 'system'...
OKAY [ 7.076s]
finished. total time: 14.829s
C:\Users\DRAVYA\Desktop\stock>fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.047s]
sending 'system' (243326 KB)...
OKAY [ 7.856s]
writing 'system'...
OKAY [ 16.026s]
finished. total time: 23.929s
C:\Users\DRAVYA\Desktop\stock>echo
ECHO is on.
C:\Users\DRAVYA\Desktop\stock>echo
ECHO is on.
C:\Users\DRAVYA\Desktop\stock>echo
ECHO is on.
C:\Users\DRAVYA\Desktop\stock>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (47476 KB)...
OKAY [ 1.584s]
writing 'modem'...
OKAY [ 0.772s]
finished. total time: 2.356s
C:\Users\DRAVYA\Desktop\stock>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.047s]
finished. total time: 0.063s
C:\Users\DRAVYA\Desktop\stock>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.047s]
finished. total time: 0.063s
C:\Users\DRAVYA\Desktop\stock>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (102 KB)...
OKAY [ 0.047s]
writing 'fsg'...
OKAY [ 3.179s]
finished. total time: 3.242s
C:\Users\DRAVYA\Desktop\stock>echo
ECHO is on.
C:\Users\DRAVYA\Desktop\stock>echo
ECHO is on.
C:\Users\DRAVYA\Desktop\stock>echo
ECHO is on.
C:\Users\DRAVYA\Desktop\stock>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Users\DRAVYA\Desktop\stock>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.063s]
finished. total time: 0.063s
C:\Users\DRAVYA\Desktop\stock>echo
ECHO is on.
C:\Users\DRAVYA\Desktop\stock>fastboot reboot
rebooting...
finished. total time: -0.000s
C:\Users\DRAVYA\Desktop\stock>
facing a problem ....please help
D:\Moto G\failsafe>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.328s
I'm updating this thread with Lollipop 5.0.2 firmware and a batch file.
I have made changes to OP to include Lollipop Firmware and to make it easier. Hope it solves your issue.
my phone's dead
no bootloader,
no logo,
nothing
Hi I'm tryin to follow this thread after the other unbrick and restore posts didn't help.
Moto G XT1033 booting to the android logo with a traingle on top of it. Recovery doesn't work and the adb window states waiting for device although I have tried many adb drivers along with moto drivers and mfast and rdlite among other things.
Win 10, Unlocked bootloaded with no recovery and no USB debugging enabled.
Any help would e highly appreciated
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x5
(bootloader) emmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA93301I18
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: EA25A8020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Apr 1 0:38:33 UTC 1959"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_asia_ds/falcon_umt
(bootloader) ro.build.fingerprint[1]: sds:5.1/LPB23.13-56/55:user/releas
(bootloader) ro.build.fingerprint[2]: e-keys
(bootloader) ro.build.version.full[0]: Blur_Version.221.21.56.falcon_umt
(bootloader) ro.build.version.full[1]: sds.AsiaRetail.en.03
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband: MSM8626BP_1032.3116.98.00R EMEA_DSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld32) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Mon Aug 17 10:37:16 CDT 2015
(bootloader) sdi.git: git=MBM-NG-V41.1A-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.1A-0-g199f3c5
(bootloader) rpm.git: git=MBM-NG-V41.1A-0-g8b7736e
(bootloader) tz.git: git=MBM-NG-V41.1A-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.316s
C:\Program Files\Minimal ADB and Fastboot>
---------- Post added at 04:28 PM ---------- Previous post was at 04:27 PM ----------
my device only stuck motorola bootloader unlock
Hey
i kill my phone.. :/
:crying:
HELP!
anything work for me..
i try reflash 4.4.3, 4.4.2, 4.3, and nothing change,
try all modes and read all posts( like http://forum.xda-developers.com/showthread.php?t=2542219)
recive ok from all flash on fastboot
see :
Code:
C:\Users\Hans\Desktop\443>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.097s]
writing 'partition'...
[B](bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...[/B]
OKAY [ 0.390s]
finished. total time: 0.490s
C:\Users\Hans\Desktop\443>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.171s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.136s]
finished. total time: 1.308s
C:\Users\Hans\Desktop\443>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (1060 KB)...
OKAY [ 0.139s]
writing 'logo'...
OKAY [ 0.076s]
finished. total time: 0.218s
C:\Users\Hans\Desktop\443>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.435s]
writing 'boot'...
OKAY [ 0.662s]
finished. total time: 1.101s
C:\Users\Hans\Desktop\443>mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.432s]
writing 'recovery'...
OKAY [ 0.661s]
finished. total time: 15.360s
C:\Users\Hans\Desktop\443>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (249247 KB)...
OKAY [ 8.308s]
writing 'system'...
OKAY [ 8.400s]
finished. total time: 16.710s
C:\Users\Hans\Desktop\443>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (250602 KB)...
OKAY [ 8.332s]
writing 'system'...
OKAY [ 7.630s]
finished. total time: 15.965s
C:\Users\Hans\Desktop\443>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (248370 KB)...
OKAY [ 8.268s]
writing 'system'...
OKAY [ 15.916s]
finished. total time: 24.186s
C:\Users\Hans\Desktop\443>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (47152 KB)...
OKAY [ 1.612s]
writing 'modem'...
OKAY [ 0.787s]
finished. total time: 2.401s
C:\Users\Hans\Desktop\443>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.012s]
finished. total time: 0.013s
C:\Users\Hans\Desktop\443>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.036s]
finished. total time: 0.037s
C:\Users\Hans\Desktop\443>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.086s]
writing 'fsg'...
OKAY [ 3.173s]
finished. total time: 3.261s
C:\Users\Hans\Desktop\443>mfastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\Users\Hans\Desktop\443>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 0.046s]
finished. total time: 0.047s
C:\Users\Hans\Desktop\443>pause
Pressione qualquer tecla para continuar. . .
my custom bootlogo stay after flash stock (the stock "M" or "boounlock warning" dont apear!!??)
my bronked recovery stay after fash stock or TWRP / CWM philz, i try all versions
and on first boot i revice infinite FC
on next boot it stuck on infinity bootlogo (my custom boot logo)
can not enter on recovery, i try everyone
and every time it return a black screen
and i stay recive vibration feedback on touch.
i really disaponted because the bootlogo/recovery dont change..
fastboot dont write nothing on my phone!?
i try format some partition but not work..
i think my sd card or/and partitions was break, like 'bad disk'
it say "RAW" dont format
please see:
Code:
C:\androidsdk\sdk\platform-tools>fastboot devices
[B]0425016712 fastboot[/B]
[B]C:\androidsdk\sdk\platform-tools>fastboot format all
Formatting is not supported for filesystem with type ''.[/B]
[B]
C:\androidsdk\sdk\platform-tools>fastboot format recovery
Formatting is not supported for filesystem with type 'raw
C:\androidsdk\sdk\platform-tools>fastboot format userdata
Formatting is not supported for filesystem with type 'raw'.
C:\androidsdk\sdk\platform-tools>fastboot format cache
Formatting is not supported for filesystem with type 'raw'.[/B]
C:\androidsdk\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4111
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x5
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: 0425016712
(bootloader) cid: 0x000C
(bootloader) channelid: 0x00
(bootloader) uid: 997643020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jul 3 10:11:24 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retbr_ds/falcon_um
(bootloader) ro.build.fingerprint[1]: tsds:4.4.3/KXB21.14-L1.32/30:user/
(bootloader) ro.build.fingerprint[2]: release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.32.falcon_umt
(bootloader) ro.build.version.full[1]: sds.Brasil.en.BR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g6095065 ([email protected]
(bootloader) kernel.version[1]: ilclbld54) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri May 30 13:52:19 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.11-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.11-0-gcff5797
(bootloader) rpm.git: git=MBM-NG-V41.11-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.11-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.11-0-g7d46a5a
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.202s
C:\androidsdk\sdk\platform-tools>
ps: i dont hide no one information..
my device have a blank IMEI and blank other strings!?
i try flash various recovery, but no one work
see:
Code:
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.711.img
target reported max download size of 536870912 bytes
sending 'recovery' (7692 KB)...
OKAY [ 0.272s]
writing 'recovery'...
OKAY [ 0.150s]
finished. total time: 0.423s
C:\androidsdk\sdk\platform-tools>
it say ok, but on try go on recovery i stuck on black screen a
and every click on screen return a vibration for me.
i need long click (10seg) on power button to go away
and try again another version's.
:/
--------------------------------------------------------------------
same on 2.7.0.0:
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.70.img
target reported max download size of 536870912 bytes
sending 'recovery' (7912 KB)...
OKAY [ 0.284s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 0.440s
black screen and every click on screen return a vibration.
---------------------------------------------------------------------
same on 2.6.3.3
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.63.img
target reported max download size of 536870912 bytes
sending 'recovery' (8678 KB)...
OKAY [ 0.307s]
writing 'recovery'...
OKAY [ 0.197s]
finished. total time: 0.506s
black screen and every click on screen return a vibration.
-------------------------------------------------------------------------
See:
[B]C:\androidsdk\sdk\platform-tools>fastboot format recovery
Formatting is not supported for filesystem with type 'raw'.[/B]
i really think fastboot dont write anything on my device..
bootlogo.img and recovery.img
dont change and i flash it 1000x with OK report.
-------------------------------------------------------------
Someone can help me!?
Please..
Sorry for bad english, i'm br..
see, my partitions change to RAW system..
and i cant format or write on then.
fastboot say OK
but my custom logo or recovery d'nt change..
see this log:
Code:
C:\Users\Hans\Desktop\443>[B]mfastboot oem unlock
...
[U](bootloader) Device already unlocked![/U]
FAILED (remote failure)
finished. total time: 0.022s[/B]
C:\Users\Hans\Desktop\443>[B][U]mfastboot erase all[/U]
erasing 'all'...
(bootloader) erasing modemst1 ...
(bootloader) erasing modemst2 ...
(bootloader) erasing hob ...
(bootloader) erasing dhob ...
(bootloader) erasing fsg ...
(bootloader) erasing fsc ...
(bootloader) erasing clogo ...
(bootloader) erasing cache ...
(bootloader) erasing userdata ...[/B]
OKAY [ 4.730s]
finished. total time: 4.731s
C:\Users\Hans\Desktop\443>mfastboot format all
formatting 'all' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.005s
C:\Users\Hans\Desktop\443>[B][U]mfastboot -w[/U][/B]
erasing 'userdata'...
OKAY [ 0.024s]
formatting 'userdata' partition...
[B][U]Erase successful, but not automatically formatting.
File system type raw not supported.[/U][/B]
OKAY [ 0.006s]
erasing 'cache'...
OKAY [ 0.021s]
formatting 'cache' partition...
[B][U]Erase successful, but not automatically formatting.
File system type raw not supported.[/U][/B]
OKAY [ 0.016s]
finished. total time: 0.069s
C:\Users\Hans\Desktop\443>[U][B]mfastboot format recovery
formatting 'recovery' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.005s[/B][/U]
-----------------------------------------------------------------------------------------
try flash gpt.bin for another firmware verison (4.3 and 4.4.2)
i recive error 'version downgrade for': on
'gpi_primary' 'tz' and 'boot'
and ok for other;
but nothing change, my custom bootloader and a bronken recovery stay.
see log:
Code:
C:\Users\Hans\Desktop\442>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.019s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.350s
C:\Users\Hans\Desktop\442>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1940 KB)...
OKAY [ 0.097s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.389s
C:\Users\Hans\Desktop\442>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (619 KB)...
OKAY [ 0.068s]
writing 'logo'...
OKAY [ 0.058s]
finished. total time: 0.128s
C:\Users\Hans\Desktop\442>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.387s]
writing 'boot'...
OKAY [ 0.679s]
finished. total time: 1.070s
C:\Users\Hans\Desktop\442>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.393s]
writing 'recovery'...
OKAY [ 0.657s]
finished. total time: 1.056s
C:\Users\Hans\Desktop\442>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (258095 KB)...
OKAY [ 8.431s]
writing 'system'...
OKAY [ 8.693s]
finished. total time: 17.125s
C:\Users\Hans\Desktop\442>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (242056 KB)...
OKAY [ 7.906s]
writing 'system'...
OKAY [ 7.115s]
finished. total time: 15.022s
C:\Users\Hans\Desktop\442>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (218977 KB)...
OKAY [ 7.154s]
writing 'system'...
OKAY [ 16.186s]
finished. total time: 23.343s
C:\Users\Hans\Desktop\442>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (47476 KB)...
OKAY [ 1.593s]
writing 'modem'...
OKAY [ 0.792s]
finished. total time: 2.388s
C:\Users\Hans\Desktop\442>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.012s]
finished. total time: 0.013s
C:\Users\Hans\Desktop\442>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Users\Hans\Desktop\442>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.089s]
writing 'fsg'...
OKAY [ 3.179s]
finished. total time: 3.269s
C:\Users\Hans\Desktop\442>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Hans\Desktop\442>mfastboot reboot
rebooting...
4.4.3 and recoverys install perfect on mfastboot
but not change anything..
see log on first post.
--------------------------------------------------------------
RSD Lite, in adm mode dont show me device and get error on start.
"the phone failed to switch to fastboot mode"
see:
{
"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"
}
----------------------------------------------------------
mfastbooot definitely not write anything on my device
i try flash 4.4.3 sigle sim, it say ok on all mfastboot
but nothing change,
recovery stay break and my customlogo too..
i recive milion FC on firstrun (but can see two sim icons on bar)
atomatic rebot stay on infinite logoboot
black recovery, with vibration on touch.
:/
My Chinese phone has a problem like that (can't flash through adb and recovery gave errors) I formatted it using the flash tool I had for that phone and than flashed the ROM I needed I don't know why Motorola hasn't provided any flash tool with this phone. There must be a command through adb that can format all the partitions and than flash.someone on XDA also fixed that problem by flashing liquidsmooth ROM.
Don't worry bro it will surely get fixed !!
Sent from my Moto G using Tapatalk
i cant send adb commands..
or acess recovery for it..
fastboot only..
and i really think fastboot dont write none because nothing change,
recovery or bootlogo, dont restore, like i get before.. : Rolleyes:
again, sorry for poor english, im br.
hansdepaula said:
i cant send adb commands..
or acess recovery for it..
fastboot only..
and i really think fastboot dont write none because nothing change,
recovery or bootlogo, dont restore, like i get before.. : Rolleyes:
again, sorry for poor english, im br.
Click to expand...
Click to collapse
Get a list of the mount points of your phone and than just format system,boot,data and cache partition after using the command "fastboot OEM format". Than flash everything through fastboot again or flash a recovery than flash using that recovery.
Just try flashing a ROM through recovery because you can specify the mount points in the script.
what comand i send to get a 'list of the' mount or partitions 'points'
this is a list of commands:
Code:
C:\androidsdk\sdk\platform-tools>fastboot help
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, and if found,
recovery, tos
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\androidsdk\sdk\platform-tools>
i use '-w' and 'format' and it say my partitions is RAW type, and can't format... :/
i try; see:
Code:
C:\Users\Hans\Desktop\443>mfastboot erase all
erasing 'all'...
(bootloader) erasing modemst1 ...
(bootloader) erasing modemst2 ...
(bootloader) erasing hob ...
(bootloader) erasing dhob ...
(bootloader) erasing fsg ...
(bootloader) erasing fsc ...
(bootloader) erasing clogo ...
(bootloader) erasing cache ...
(bootloader) erasing userdata ...
OKAY [ 4.737s]
finished. total time: 4.737s
C:\Users\Hans\Desktop\443>mfastboot format all
formatting 'all' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.005s
C:\Users\Hans\Desktop\443>mfastboot format system
formatting 'system' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.006s
C:\Users\Hans\Desktop\443>mfastboot format recovery
formatting 'recovery' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.006s
C:\Users\Hans\Desktop\443>mfastboot format logo
formatting 'logo' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.005s
C:\Users\Hans\Desktop\443>mfastboot format clogo
formatting 'clogo' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.007s
C:\Users\Hans\Desktop\443>mfastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.005s
C:\Users\Hans\Desktop\443>mfastboot format userdata
formatting 'userdata' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.005s
C:\Users\Hans\Desktop\443>
all raw!
and fastboot dont write nothing :/
hansdepaula said:
what comand i send to get a 'list of the' mount or partitions 'points'
this is a list of commands:
Code:
C:\androidsdk\sdk\platform-tools>fastboot help
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, and if found,
recovery, tos
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\androidsdk\sdk\platform-tools>
i use '-w' and 'format' and it say my partitions is RAW type, and can't format... :/
i try; see:
Code:
C:\Users\Hans\Desktop\443>mfastboot erase all
erasing 'all'...
(bootloader) erasing modemst1 ...
(bootloader) erasing modemst2 ...
(bootloader) erasing hob ...
(bootloader) erasing dhob ...
(bootloader) erasing fsg ...
(bootloader) erasing fsc ...
(bootloader) erasing clogo ...
(bootloader) erasing cache ...
(bootloader) erasing userdata ...
OKAY [ 4.737s]
finished. total time: 4.737s
C:\Users\Hans\Desktop\443>mfastboot format all
formatting 'all' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.005s
C:\Users\Hans\Desktop\443>mfastboot format system
formatting 'system' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.006s
C:\Users\Hans\Desktop\443>mfastboot format recovery
formatting 'recovery' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.006s
C:\Users\Hans\Desktop\443>mfastboot format logo
formatting 'logo' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.005s
C:\Users\Hans\Desktop\443>mfastboot format clogo
formatting 'clogo' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.007s
C:\Users\Hans\Desktop\443>mfastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.005s
C:\Users\Hans\Desktop\443>mfastboot format userdata
formatting 'userdata' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.005s
C:\Users\Hans\Desktop\443>
all raw!
and fastboot dont write nothing :/
Click to expand...
Click to collapse
Can you open recovery? are you able to flash recovery?
I restored my stock firmware without any problems on my moto g.
I had a cmw backup and there was no problem in restoring.
The problem you have specified occurs when you flash a rom or something in the wrong partition(other mount point)
You must have downloaded the wrong file i suppose but i am sure it can be fixed , you just need to contact someone who knows about this more
i not can enter in recovery..
fastboot dnt write nothing..
nothing change on my phone..
my recovery stay black and my custom logo stay,
and i try flash more that 15 versions of stock's firmware
and all versions of recoverys
nothing change..
my device say on layout of bootloader
"AP Fastboot Flash Mode (s)
41.11 (sha=7d46a5a, 20014-05-25 09:28:38)
CPU: MSM8226 CS
eMMc: 16gb Samdisk RV=06 PV=07 TY=17
DRAM: 1024MB Samsung S4 SDRAM DIE=4GB
Battery OK
Device is UNLOCKED. Status Code: 3
Transfer Mode: USB Connected"
i try use one blankscript but 'downgrade' mensage stay show on my device and log:
Code:
if you want to broke your bootloader push one key
Pressione qualquer tecla para continuar. . .
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.016s]
writing 'fsg'...
OKAY [ 3.141s]
finished. total time: 3.172s
target max-sparse-size: 256MB
sending 'rpm' (200 KB)...
OKAY [ 0.016s]
writing 'rpm'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.312s
target max-sparse-size: 256MB
sending 'sbl1' (264 KB)...
OKAY [ 0.047s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.078s
target max-sparse-size: 256MB
sending 'sdi' (32 KB)...
OKAY [ 0.047s]
writing 'sdi'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.328s
target max-sparse-size: 256MB
sending 'tz' (400 KB)...
OKAY [ 0.078s]
writing 'tz'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.406s
Bootloader broken YAY!
Pressione qualquer tecla para continuar. . .
i cant try another options like 'qualcomm_boot_tool' because it dont show my device:
Code:
from Boss442 to XDA
< waiting for device >
fastboot dont write nothing on my phone..
everything stay like before flash,
cutombootlogo and breakrecovery dont change..
getvar show a CMkenel.. (first post)
:/
if try use another version of firmware it say 'downgrade failed'..
on 4.4.3 firmware everithing say OK
but dont change nothing..
what i can do?
some one can help, give me a idea or option?
hansdepaula said:
i try use one blankscript but 'downgrade' mensage stay show on my device and log:
Code:
if you want to broke your bootloader push one key
Pressione qualquer tecla para continuar. . .
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.016s]
writing 'fsg'...
OKAY [ 3.141s]
finished. total time: 3.172s
target max-sparse-size: 256MB
sending 'rpm' (200 KB)...
OKAY [ 0.016s]
writing 'rpm'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.312s
target max-sparse-size: 256MB
sending 'sbl1' (264 KB)...
OKAY [ 0.047s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.078s
target max-sparse-size: 256MB
sending 'sdi' (32 KB)...
OKAY [ 0.047s]
writing 'sdi'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.328s
target max-sparse-size: 256MB
sending 'tz' (400 KB)...
OKAY [ 0.078s]
writing 'tz'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.406s
Bootloader broken YAY!
Pressione qualquer tecla para continuar. . .
i cant try another options like 'qualcomm_boot_tool' because it dont show my device:
Code:
from Boss442 to XDA
< waiting for device >
fastboot dont write nothing on my phone..
everything stay like before flash,
cutombootlogo and breakrecovery dont change..
getvar show a CMkenel.. (first post)
:/
if try use another version of firmware it say 'downgrade failed'..
on 4.4.3 firmware everithing say OK
but dont change nothing..
what i can do?
some one can help, give me a idea or option?
Click to expand...
Click to collapse
you would probably have to wait for some time untill someone figures out a fix, many people are having this problem so its very likely to get fixed . Stay tuned and dont worry
thanks for attention Shlok..
you really give me a hope..
see people and thread's with 'same' problem..
read suposed fixes also, but then consistes on enter in recovery mode.
or flash gpi.bin / recovery.img
and can not do it..
think my fastboot as corrupted..
and then cant write nothing.. :/
more logs, maybe help:
Code:
C:\Users\Hans\Desktop\443>mfastboot erase system
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.018s]
finished. total time: 0.019s
C:\Users\Hans\Desktop\443>mfastboot erase recovery
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.049s]
finished. total time: 0.051s
C:\Users\Hans\Desktop\443>mfastboot erase boot
erasing 'boot'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.038s]
finished. total time: 0.039s
C:\Users\Hans\Desktop\443>mfastboot erase logo
erasing 'logo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.031s
C:\Users\Hans\Desktop\443>mfastboot erase modem
erasing 'modem'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.013s
C:\Users\Hans\Desktop\443>
yeah
i have unlocked phone..
my cid say '0x0000C', on getvar all (first post)
my hopes die..
i really hope if i as the 4.4.4 firmware i will can revive my device..
but at some minutes i try flash parts of 4.4.4 ota (Blur_Version.210.12.32.falcon_umtsds.Brasil.en.BR) version for my device..
in zip i take the files:
Code:
gpt.bin
fsg.mbn
rpm.mbn
sbl1.mbn
sbl1_8226.mbn
sdi.mbn
tz.mbn
files..
and try, with sucess flash then using a bat script like:
Code:
mfastboot flash partition gpt.bin
mfastboot flash fsg fsg.mbn
mfastboot flash rpm rpm.mbn
mfastboot flash sdi sdi.mbn
mfastboot flash sbl1 sbl1_8226.mbn
mfastboot flash tz tz.mbn
i recive ok for all (no one 'downgrade' msg)
but nothing change again..
i also try flash the logo.bin and recovery.img for 4.4.3 before this comands..
try also custonsrecoverys.img and logo.bin
try another variations of this, and other fastboot flash's..
and nothing change again..
i really think my fastboot as corrupted, i try use @Boos442 tools, http://forum.xda-developers.com/showthread.php?p=53921401.
but i dont have a qualcomm drivers for my device (VID_05C6&PID_9025)
:/
i'll stay waiting for something..
someone have a idea about what i can try do..?
today, before waste my day sheaching..
i have see me device on ADB
but, it say "unathorized", and my device stay on bootlogoloop
see:
Code:
C:\Users\Hans\Desktop\443>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\Hans\Desktop\443>adb devices
List of devices attached
0425016712 unauthorized
C:\Users\Hans\Desktop\443>adb shell
error: device unauthorized. Please check the confirmation dialog on your device.
C:\Users\Hans\Desktop\443>adb kill-server
C:\Users\Hans\Desktop\443>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\Hans\Desktop\443>adb devices
List of devices attached
0425016712 unauthorized
C:\Users\Hans\Desktop\443>
"error: device unauthorized. Please check the confirmation dialog on your device."
i cant see dialog, my device stay in bootloop.. :/
have a some comand i can use in unauthorized mode?
What does "fastboot devices" say?
fastboot show me device like charm..
Code:
C:\androidsdk\sdk\platform-tools>fastboot devices
0425016712 fastboot
see all logs, and getvar all on first post.
all fastboot flash report OK..
but nothing change on phone, recovery say OK on flash but before restart o direct click on recovery mode, then dont work..
same on logo.bin, say OK on fastboot but on restart i stay see a custombootlogo i use before bricked..
i try format some partition but not work..
i think my sd card/eMMC or/and partitions was break, like 'bad disk'
fastboot say "RAW" dont format..
please, waste a time for read my first and other posts, i put some important logs, and all posts have moreover ..
maybe you can help me, or give me a good idea.
Hello,
I've you resolved your problem ? I have exactly the same problem, fastboot say ok for all command, but do nothing in reality
4.3 kernel is not compatible with latest Bootloader. If you update to 4.4.4 via OTA update or firmware image - you cannot boot 4.3 ever again.
lost101 said:
4.3 kernel is not compatible with latest Bootloader. If you update to 4.4.4 via OTA update or firmware image - you cannot boot 4.3 ever again.
Click to expand...
Click to collapse
Yes, but we can't flash anything.
For me, I have a 4.4.4 GPE, only access to Fastboot. Fastboot flash say OK to all commands but do nothing (no recovery, no new logo... nothing).
the tools for refresh or corrupt then bootloader doesn't work to...
Are you using fastboot or mfastboot? What commands have you used? Do the 'flash system system.img' commands actually match the filenames of the firmware you have downloaded?
lost101 said:
Are you using fastboot or mfastboot? What commands have you used? Do the 'flash system system.img' commands actually match the filenames of the firmware you have downloaded?
Click to expand...
Click to collapse
fastboot and mfastboot, nothing append with all of then.
The getvar all :
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA89003W34
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: 8145E5010F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jun 26 13: 1:29 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_gpe/falcon_umts:4.
(bootloader) ro.build.fingerprint[1]: 4.4/KTU84P.M003/18:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g8a4c884-00003-g3f2
(bootloader) kernel.version[1]: 1e91 ([email protected]) (gcc version 4.7 (GCC
(bootloader) kernel.version[2]: ) ) #1 SMP PREEMPT Thu Jun 19 14:53:29 P
(bootloader) kernel.version[3]: DT 2014
(bootloader) sdi.git: git=MBM-NG-V41.13-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.13-0-g683cb0c
(bootloader) rpm.git: git=MBM-NG-V41.13-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.13-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.13-0-g7dc8e78
(bootloader) qe: qe 2/1
(bootloader) ro.carrier: unknown
I have download the KTU84P (4.4.4 GPE) firmware.
Lauch this commands (fastboot and mfastboot, and with & without the reboot-bootloader line) :
Code:
fastboot.exe flash partition gpt.bin
fastboot.exe flash motoboot motoboot.img
fastboot.exe reboot-bootloader
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot.exe flash fsg fsg.mbn
fastboot.exe erase cache
fastboot.exe erase userdata
On screen device, in purple, only this error :
Code:
hab check failed for boot
hab check failed for recovery
The dos output :
D:\moto\4.4.4 GPE KTU84P>fastboot.exe flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.059s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.374s]
finished. total time: 0.435s
D:\moto\4.4.4 GPE KTU84P>fastboot.exe flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.132s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.128s]
finished. total time: 1.262s
D:\moto\4.4.4 GPE KTU84P>fastboot.exe reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
D:\moto\4.4.4 GPE KTU84P>fastboot.exe flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (70 KB)...
OKAY [ 0.096s]
writing 'logo'...
OKAY [ 0.037s]
finished. total time: 0.135s
D:\moto\4.4.4 GPE KTU84P>fastboot.exe flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.339s]
writing 'boot'...
OKAY [ 0.646s]
finished. total time: 0.988s
D:\moto\4.4.4 GPE KTU84P>fastboot.exe flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.349s]
writing 'recovery'...
OKAY [ 0.667s]
finished. total time: 1.019s
D:\moto\4.4.4 GPE KTU84P>fastboot.exe flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.036s]
sending 'system' (255843 KB)...
OKAY [ 8.045s]
writing 'system'...
(bootloader) WARNING: System partition size is 0x34800000
(bootloader) Only multiples of 0x1000000 allowed for write-protection
(bootloader) Write protect will not be enabled
OKAY [ 8.557s]
finished. total time: 16.642s
D:\moto\4.4.4 GPE KTU84P>fastboot.exe flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.032s]
sending 'system' (245954 KB)...
OKAY [ 7.759s]
writing 'system'...
(bootloader) WARNING: System partition size is 0x34800000
(bootloader) Only multiples of 0x1000000 allowed for write-protection
(bootloader) Write protect will not be enabled
OKAY [ 7.534s]
finished. total time: 15.327s
D:\moto\4.4.4 GPE KTU84P>fastboot.exe flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.050s]
sending 'system' (235703 KB)...
OKAY [ 7.421s]
writing 'system'...
(bootloader) WARNING: System partition size is 0x34800000
(bootloader) Only multiples of 0x1000000 allowed for write-protection
(bootloader) Write protect will not be enabled
OKAY [ 11.098s]
finished. total time: 18.573s
D:\moto\4.4.4 GPE KTU84P>fastboot.exe flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (47152 KB)...
OKAY [ 1.526s]
writing 'modem'...
OKAY [ 0.793s]
finished. total time: 2.321s
D:\moto\4.4.4 GPE KTU84P>fastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.055s]
finished. total time: 0.056s
D:\moto\4.4.4 GPE KTU84P>fastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.055s]
finished. total time: 0.056s
D:\moto\4.4.4 GPE KTU84P>fastboot.exe flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (717 KB)...
OKAY [ 0.114s]
writing 'fsg'...
OKAY [ 3.197s]
finished. total time: 3.315s
D:\moto\4.4.4 GPE KTU84P>fastboot.exe erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.055s]
finished. total time: 0.056s
D:\moto\4.4.4 GPE KTU84P>fastboot.exe erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.065s]
finished. total time: 0.066s
D:\moto\4.4.4 GPE KTU84P>pause
Appuyez sur une touche pour continuer...
After reboot, the "warning unlock" logo still display and bootloop with this picture. Can't reboot to any recovery (stock, CWM, TWRP...)
If I'm using a 4.4.4 non-GPE, I'have the error "image is too large" on device screen
If I'm using any 4.4.3/4.4.2/4.3 I've got the error for downgrade Tz, boot etc... (it's normal, downgrade is not possible)
I also trying to refresh the bootloader with OTA 4.4.4 GPE files
Code:
mfastboot flash partition gpt.bin
mfastboot flash tz tz.mbn
mfastboot flash rpm rpm.mbn
mfastboot flash sdi sdi.mbn
mfastboot flash aboot emmc_appsboot.mbn
mfastboot flash sbl1 sbl1_8226.mbn
mfastboot flash fsg fsg.mbn
If I'm trying to format boot/recovery partition :
Code:
D:\moto>mfastboot.exe format boot
formatting 'boot' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.003s
The mfastboot.exe oem fb_mode_set :
Code:
FAILED (remote failure)
finished. total time: 0.006s
A friend of mine bricked his Moto G 2013 and, after many attempts on fixing it, I was unable to get it to work in any way.
The problem:
Classic boot loop: It gets stuck on "unlocked bootloader" screen on startup.
Why don't you just flash the stock rom directly from fastboot?
I did try to flash it many times, but it simply doesn't work.
No FAILED status is shown on fastboot flashing, but it simply doesn't install.
Why don't you flash a custom rom from a custom recovery?
Installing a custom recovery flashing also don't work even without showing any error on installation.
I was able to boot from twrp.img directly from fastboot, but it gives an error on any rom I try to flash from it.
Wiping from it did not help either.
The solution:
I have no clue. :crying:
Interesting,
What device is it? (XT10**) --> edit: I didn't see it was in subject, so xt1033
What os is you're computer running? (And what method did you use to install adb&fastboot)
Make sure you have recent adb and fastboot builds
If you are on Linux, you only need to make sure android-tools-adb and android-tools-fastboot are properly installed and updated (and that the udev rules allow to access the device)
If not I can't help you with the os specific part
I would retry to flash 41.1A bootloader first, and then try again to flash twrp 3.0.2 + CM13 + micro gapps
matmutant said:
Interesting,
What device is it? (XT10**) --> edit: I didn't see it was in subject, so xt1033
What os is you're computer running? (And what method did you use to install adb&fastboot)
Make sure you have recent adb and fastboot builds
If you are on Linux, you only need to make sure android-tools-adb and android-tools-fastboot are properly installed and updated (and that the udev rules allow to access the device)
If not I can't help you with the os specific part
I would retry to flash 41.1A bootloader first, and then try again to flash twrp 3.0.2 + CM13 + micro gapps
Click to expand...
Click to collapse
I'm on a windows 7 x64 machine.
Installed minimal adb&fastoot v1.1.3 via .exe installer... I don't really remember from where I have downloaded it, got it months ago, trying to unbrick my hard bricked moto G 2014.
Tried your method reflashing bootloader 41.1A found here:
41.1A
It also returned no error upon installation, perhaps, no luck on installing twrp again.
Tried flashing stock again:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.050s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.350s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash motoboot motoboot
.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.130s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.410s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1060 KB)...
OKAY [ 0.120s]
writing 'logo'...
OKAY [ 0.080s]
finished. total time: 0.210s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.430s]
writing 'boot'...
OKAY [ 0.610s]
finished. total time: 1.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.430s]
writing 'recovery'...
OKAY [ 0.610s]
finished. total time: 1.040s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.040s]
sending 'system' (249379 KB)...
OKAY [ 8.242s]
writing 'system'...
OKAY [ 8.129s]
finished. total time: 16.411s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.050s]
sending 'system' (252566 KB)...
OKAY [ 8.329s]
writing 'system'...
OKAY [ 7.401s]
finished. total time: 15.780s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.2
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.060s]
sending 'system' (249711 KB)...
OKAY [ 8.219s]
writing 'system'...
OKAY [ 15.926s]
finished. total time: 24.205s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bi
n
target reported max download size of 536870912 bytes
sending 'modem' (47152 KB)...
OKAY [ 1.600s]
writing 'modem'...
OKAY [ 0.760s]
finished. total time: 2.360s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.050s]
finished. total time: 0.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.060s]
finished. total time: 0.060s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (102 KB)...
OKAY [ 0.100s]
writing 'fsg'...
OKAY [ 3.185s]
finished. total time: 3.285s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.060s]
finished. total time: 0.060s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.070s]
finished. total time: 0.070s
Now i'm getting "fails" on the beggining.
lhtrevisan said:
I'm on a windows 7 x64 machine.
Installed minimal adb&fastoot v1.1.3 via .exe installer... I don't really remember from where I have downloaded it, got it months ago, trying to unbrick my hard bricked moto G 2014.
Tried your method reflashing bootloader 41.1A found here:
41.1A
It also returned no error upon installation, perhaps, no luck on installing twrp again.
Tried flashing stock again:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.050s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.350s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash motoboot motoboot
.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.130s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.410s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1060 KB)...
OKAY [ 0.120s]
writing 'logo'...
OKAY [ 0.080s]
finished. total time: 0.210s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.430s]
writing 'boot'...
OKAY [ 0.610s]
finished. total time: 1.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.430s]
writing 'recovery'...
OKAY [ 0.610s]
finished. total time: 1.040s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.040s]
sending 'system' (249379 KB)...
OKAY [ 8.242s]
writing 'system'...
OKAY [ 8.129s]
finished. total time: 16.411s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.050s]
sending 'system' (252566 KB)...
OKAY [ 8.329s]
writing 'system'...
OKAY [ 7.401s]
finished. total time: 15.780s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.2
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.060s]
sending 'system' (249711 KB)...
OKAY [ 8.219s]
writing 'system'...
OKAY [ 15.926s]
finished. total time: 24.205s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bi
n
target reported max download size of 536870912 bytes
sending 'modem' (47152 KB)...
OKAY [ 1.600s]
writing 'modem'...
OKAY [ 0.760s]
finished. total time: 2.360s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.050s]
finished. total time: 0.050s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.060s]
finished. total time: 0.060s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (102 KB)...
OKAY [ 0.100s]
writing 'fsg'...
OKAY [ 3.185s]
finished. total time: 3.285s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.060s]
finished. total time: 0.060s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.070s]
finished. total time: 0.070s
Now i'm getting "fails" on the beggining.
Click to expand...
Click to collapse
This make me think you would need to flash a 5.1 gpt.bin (that you can find in an official zip for your XT1033 device), and then retry to update the bootloader
Though I should work, "sh*t happens" sometime (I am currently failing to update a Peregrine from JB to CM13 xD
Got gpt.bin from "official" untouched 5.1 update... same error when trying to flash it.
lhtrevisan said:
Got gpt.bin from "official" untouched 5.1 update... same error when trying to flash it.
Click to expand...
Click to collapse
what does "fastboot getvar version-bootloader" outputs?
and "getvar all" too btw"
matmutant said:
what does "fastboot getvar version-bootloader" outputs?
and "getvar all" too btw"
Click to expand...
Click to collapse
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar version-bootloader"
version-bootloader: 411A
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x5
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: T099706POH
(bootloader) cid: 0x000C
(bootloader) channelid: 0x00
(bootloader) uid: 50AA5E040F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jul 9 4: 2:45 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retbr_ds/falcon_um
(bootloader) ro.build.fingerprint[1]: tsds:5.1/LPBS23.13-56-2/2:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.221.201.2.falcon_umt
(bootloader) ro.build.version.full[1]: sds.Brasil.en.BR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld27) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Feb 26 07:13:58 CST 2016
(bootloader) sdi.git: git=MBM-NG-V41.1A-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.1A-0-g199f3c5
(bootloader) rpm.git: git=MBM-NG-V41.1A-0-g8b7736e
(bootloader) tz.git: git=MBM-NG-V41.1A-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.060s
When you succeded to boot TWRP (using fastboot), did you try to flash an official 5.1 retail build?
---------- Post added at 22:39 ---------- Previous post was at 22:27 ----------
Did you have a llok at this thread too?
I didn't have time to read it thoroughly but the guy might had a similar problem?
http://forum.xda-developers.com/moto-g/help/c-spire-xt1031-moto-g-bootloader-t3156173
matmutant said:
When you succeded to boot TWRP (using fastboot), did you try to flash an official 5.1 retail build?
---------- Post added at 22:39 ---------- Previous post was at 22:27 ----------
Did you have a llok at this thread too?
I didn't have time to read it thoroughly but the guy might had a similar problem?
http://forum.xda-developers.com/moto-g/help/c-spire-xt1031-moto-g-bootloader-t3156173
Click to expand...
Click to collapse
No, I didn't try that, as I'm not able to send any archive to the cell phone in order to be able to install that from twrp.
The error I mentioned on first post was at "pushing" the rom into the cell phone... I think it's because adb is not able to find my device ("adb devices -l" returns no results).
Also, twrp mounts the cell phone as an removable drive, perhaps, it freezes if I try to save directly with Ctrl+C and Ctrl+V.
lhtrevisan said:
No, I didn't try that, as I'm not able to send any archive to the cell phone in order to be able to install that from twrp.
The error I mentioned on first post was at "pushing" the rom into the cell phone... I think it's because adb is not able to find my device ("adb devices -l" returns no results).
Also, twrp mounts the cell phone as an removable drive, perhaps, it freezes if I try to save directly with Ctrl+C and Ctrl+V.
Click to expand...
Click to collapse
So you have a TWRP installed on the device???? (which one?)
If so, use and OTG flashdrive, you might succeed from there
matmutant said:
So you have a TWRP installed on the device???? (which one?)
If so, use and OTG flashdrive, you might succeed from there
Click to expand...
Click to collapse
No, i don't have it installed... I use it booting from fastboot with "fastboot boot recovery.img" where recovery.img is twrp image renamed.
Edit: Also I don't have an OTG cable. :/
lhtrevisan said:
No, i don't have it installed... I use it booting from fastboot with "fastboot boot recovery.img" where recovery.img is twrp image renamed.
Edit: Also I don't have an OTG cable. :/
Click to expand...
Click to collapse
try to find one
That would be interesting to try to boot from the recovery (via fastboot), unplug, plug OTG w/ a 5.1 stock rom zip and try to flash
matmutant said:
try to find one
That would be interesting to try to boot from the recovery (via fastboot), unplug, plug OTG w/ a 5.1 stock rom zip and try to flash
Click to expand...
Click to collapse
I gave up on that... Returned it to my friend earlier today. Thank you very much for the effort on helping me.
Is there any way of closing the thread here?
[Failed]
lhtrevisan said:
I gave up on that... Returned it to my friend earlier today. Thank you very much for the effort on helping me.
Is there any way of closing the thread here?
Click to expand...
Click to collapse
You're welcome!
I am really sorry I couldn't help you more,
Maybe your friend can try the last option him/herself ?
I don't think you can close the thread yourself, but let's keep it open if someone ever wants to add something one day
How to revert back to normal from gpe
Sent from my Redmi 3S using XDA-Developers mobile app
lhtrevisan said:
A friend of mine bricked his Moto G 2013 and, after many attempts on fixing it, I was unable to get it to work in any way.
The problem:
Classic boot loop: It gets stuck on "unlocked bootloader" screen on startup.
Why don't you just flash the stock rom directly from fastboot?
I did try to flash it many times, but it simply doesn't work.
No FAILED status is shown on fastboot flashing, but it simply doesn't install.
Why don't you flash a custom rom from a custom recovery?
Installing a custom recovery flashing also don't work even without showing any error on installation.
I was able to boot from twrp.img directly from fastboot, but it gives an error on any rom I try to flash from it.
Wiping from it did not help either.
The solution:
I have no clue. :crying:
Click to expand...
Click to collapse
May be, check your android version matches TWRP recovery version
Hello Everyone,
So my tablet randomly had issues when I woke up a couple of days ago, it will sit at the nvidia splash\boot screen and never get past that. When I try to boot into recovery with power + volume down I will get to the recovery screen. When I choose recovery it will show the android laying down with the red exclamation and say no command under it. This also happens when I flash just the recovery image as well.
I found quite a few people with issues similar to mine, but I keep getting a fail to write error.
I followed this guide http://developer.download.nvidia.com/mobile/shield/ROM/ST8/5_1_0/HowTo-Flash-Recovery-Image.txt and keep getting a write failed error, I tried both the 5.1 and 5.2 images. The output of the command prompt is below.
C:\Program Files\Android\platform-tools-latest-windows\platform-tools>fastboot flash recovery nv-recovery-st-wx-na-wf-5.1.0\recovery.img
target reported max download size of 100663296 bytes
sending 'recovery' (10284 KB)...
OKAY [ 0.446s]
writing 'recovery'...
OKAY [ 2.663s]
finished. total time: 3.118s
C:\Program Files\Android\platform-tools-latest-windows\platform-tools>fastboot flash boot nv-recovery-st-wx-na-wf-5.1.0\boot.img
target reported max download size of 100663296 bytes
sending 'boot' (6992 KB)...
OKAY [ 0.308s]
writing 'boot'...
OKAY [ 0.252s]
finished. total time: 0.564s
C:\Program Files\Android\platform-tools-latest-windows\platform-tools>fastboot flash system nv-recovery-st-wx-na-wf-5.1.0\system.img
target reported max download size of 100663296 bytes
erasing 'system'...
OKAY [ 30.087s]
sending sparse 'system' 1/13 (98301 KB)...
OKAY [ 4.340s]
writing 'system' 1/13...
FAILED (remote: (FileWriteFailed))
finished. total time: 44.493s
C:\Program Files\Android\platform-tools-latest-windows\platform-tools>
I also tried running the flash-all.bat as well, cmd output is below
C:\Program Files\Android\platform-tools-latest-windows\platform-tools>flash-all.bat
target reported max download size of 100663296 bytes
sending 'recovery' (10286 KB)...
OKAY [ 0.446s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 10.518s
target didn't report max-download-size
sending 'boot' (6996 KB)...
FAILED (command write failed (No error))
finished. total time: 0.013s
target reported max download size of 100663296 bytes
erasing 'system'...
OKAY [ 5.042s]
sending sparse 'system' 1/13 (98301 KB)...
OKAY [ 4.367s]
writing 'system' 1/13...
FAILED (remote: (FileWriteFailed))
finished. total time: 19.479s
target didn't report max-download-size
sending 'userdata' (4784 KB)...
FAILED (command write failed (Not enough space))
finished. total time: 0.015s
target reported max download size of 100663296 bytes
sending 'staging' (18041 KB)...
OKAY [ 0.765s]
writing 'staging'...
FAILED (remote: (FileWriteFailed))
finished. total time: 10.837s
Press any key to exit...
So does anyone have any more Ideas I could try? Is my device broken? I found some people mentioning that maybe my flash storage chip is bad.
Thank you
Edit: Does anyone know if this is the correct size for it to be reporting on the "target reported max download size of 100663296 bytes" That seems really small like only 100 Mb.
I had the same issue with the dead android, turns out i was using an older version of TWRP, check that first.
Habbz said:
I had the same issue with the dead android, turns out i was using an older version of TWRP, check that first.
Click to expand...
Click to collapse
Sweet thank you I will check that out right now. I will post an update on what happens.
--edit actually I am not using TWRP I thought you were referring to adb/fastboot for some reason.
Also does anyone know if there a way to run diagnostics to see if my internal storage is fried it keeps failing to write so it might be that unfortunately.
I did not find much with a search I might not be using the correct terms. when I do fastboot getvar recovery, all, or anything for that mater it stays
Code:
D:\Downloads\nv-recovery-st-wx-na-wf-5.2.0>fastboot getvar recovery
getvar:recovery FAILED (command write failed (Unknown error))
finished. total time: 5.008s
snukkums said:
Sweet thank you I will check that out right now. I will post an update on what happens.
--edit actually I am not using TWRP I thought you were referring to adb/fastboot for some reason.
Also does anyone know if there a way to run diagnostics to see if my internal storage is fried it keeps failing to write so it might be that unfortunately.
I did not find much with a search I might not be using the correct terms. when I do fastboot getvar recovery, all, or anything for that mater it stays
Code:
D:\Downloads\nv-recovery-st-wx-na-wf-5.2.0>fastboot getvar recovery
getvar:recovery FAILED (command write failed (Unknown error))
finished. total time: 5.008s
Click to expand...
Click to collapse
actually I got it to work with getvar it will now display everything I rebooted it into fastboot mode.
This is the output to it:
Code:
D:\Shield tablet\nv-recovery-st-wx-na-wf-5.0.0>fastboot getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version-mts: 0
(bootloader) version: 0.4
(bootloader) serialno: 1740DF2052000000014FE0100
(bootloader) mid: 001
(bootloader) product: ShieldTablet
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) max-download-size: 0x06000000
(bootloader) off-mode-charge: yes
(bootloader) partition-size:bootloader:
(bootloader) partition-type:bootloader: basic
(bootloader) partition-size:recovery: 0x0000000001000000
(bootloader) partition-type:recovery: basic
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-type:boot: basic
(bootloader) partition-size:dtb: 0x0000000000400000
(bootloader) partition-type:dtb: basic
(bootloader) partition-size:system: 0x0000000050000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x0000000040000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x0000000311600000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 15.286s
Hi Friends!
The phone was loaded 2Q4DIMG_OCEAN_M_DUGL_O80_SENSE90GP_HTC_Europe_1.10 .401.23_Radio_8998-002772-1711021849_release_516987_signed_2_4.zip
After that was OTA update OTA_OCEAN_M_DUGL_O80_SENSE90GP_HTC_Europe_1.24.401.2-1.10.401.23_release_518892adqx6qggc3k03xlt.zip flashed via recovery from SD
I removed some preinstalled app like twitter and remove keyboard (use another keyboard). After restart I cant enter the password
I try to flash system.img from 2Q4DIMG_OCEAN_M_DUGL_O80_SENSE90GP_HTC_Europe_1.10 .401.23_Radio_8998-002772-1711021849_release_516987_signed_2_4.zip
C:\adb>fastboot flash system system.img
target reported max download size of 2399200000 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.300s]
sending sparse 'system' 1/2 (2314957 KB)...
FAILED (remote: unknown command)
finished. total time: 1.594s
After that try to restore RUU from SD, but have Errors:
19 RU_MAIN_VER_FAIL os-versionin android-info missing or ....
How to repair phone?
Or may be someone have system backup from TWRP after last OTA update
command
Code:
fastboot flash -S 1G system system.img
nenebear said:
command
Code:
fastboot flash -S 1G system system.img
Click to expand...
Click to collapse
Thanks, but
Code:
C:\adb>fastboot flash -S 1G system system.img
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.138s]
sending sparse 'system' 1/4 (1048573 KB)...
OKAY [ 33.176s]
writing 'system' 1/4...
(bootloader) HOSD CL#1010171
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 83.318s]
sending sparse 'system' 2/4 (1048153 KB)...
OKAY [ 33.496s]
writing 'system' 2/4...
(bootloader) HOSD CL#1010171
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 83.291s]
sending sparse 'system' 3/4 (1040948 KB)...
OKAY [ 33.344s]
writing 'system' 3/4...
(bootloader) HOSD CL#1010171
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 83.798s]
sending sparse 'system' 4/4 (141184 KB)...
OKAY [ 5.413s]
writing 'system' 4/4...
(bootloader) HOSD CL#1010171
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 12.264s]
finished. total time: 368.259s
C:\adb>
The system.img has successfully flashed. But after the restart of the phone, the white inscription of the HTC on a black background and at the bottom powered by the android. Nothing happens, even a bootloop
sm_vl said:
The system.img has successfully flashed. But after the restart of the phone, the white inscription of the HTC on a black background and at the bottom powered by the android. Nothing happens, even a bootloop
Click to expand...
Click to collapse
You need flash boot image.
You are a great man!
Note: I have patched boot from Magisk. After succesfull flash system image I try to flash boot.img (37 942 578 Bytes) from version 1.24.401.2 , but no effect
After that I flashed boot.img (37 934 386 Bytes) from version 1.10.401.23 and phone strated!!! Wauuuu )))
Thank YOU
P.S. via recovery menu install OTA update