Steps taken:
Bought Zenfone 5 (A500_KL).
It comes with all sh**ty Asus apps, so I decided to upgrade to Android 5.0 (Lollipop) and Root (to remove all Asus sh*t later).
OS upgrade went fine.
I used official downloads (URL: asus. com / Phone / ZenFone_5_A500KL / HelpDesk_Download).
(IMG = s24 .postimg .org /c8sogdq85 /Screenshot_2015_09_02_13_57_06.jpg)
When trying to Root phone (using this tutorial: ibtimes. co.uk / how-root-zenfone-5-android-5-0-lollipop-v3-23-40-52-one-click-tool-1505424)
(IMG = s14 .postimg .org /6gs8oglfl /Untitled.jpg
Error:
Code:
'
'
' Connect your device with your computer and prepare to ROOT
'
' !!! DO NOT DISCONNECT USB CABLE WHILE ROOTING !!!
'
'
Press any key to continue . . .
'
'
' Rooting, please be patient ..
'
'
target reported max download size of 661651456 bytes
sending '/system/bin/resize2fs' (6 KB)...
OKAY [ 0.006s]
writing '/system/bin/resize2fs'...
FAILED (remote: Security device, flash function is disabled.)
finished. total time: 0.015s
target reported max download size of 661651456 bytes
sending '/system/bin/tune2fs' (1386 KB)...
OKAY [ 0.048s]
writing '/system/bin/tune2fs'...
FAILED (remote: Security device, flash function is disabled.)
finished. total time: 0.069s
target reported max download size of 661651456 bytes
sending '/system/bin/partlink' (2940 KB)...
OKAY [ 0.098s]
writing '/system/bin/partlink'...
FAILED (remote: Security device, flash function is disabled.)
finished. total time: 0.123s
...
FAILED (status read failed (Too many links))
finished. total time: 170.146s
< waiting for device >
Search on Google (and in this forum) yields nothing useful.
Anybody can help with the issue please?
Dima Gusyatiner said:
Steps taken:
...
Search on Google (and in this forum) yields nothing useful.
Anybody can help with the issue please?
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
I'm sorry to hear about your trouble (locked bootloader?). We cannot provide technical support nor can other members reply to your posts here on XDA Assist and here is no forum specifically for the Zenfone 5 (A500_KL). at this time but you may want to ask your question with all relevant details in the friendly general Android Q&A, Help & Troubleshooting forum at http://forum.xda-developers.com/android/help. That's a good place to start where members familiar with your device might be able to advise you. I also see a number of references to your model from a site search at http://forum.xda-developers.com/sitesearch.php?q=Zenfone 5 (A500_KL) which might be worth reviewing.
Good luck!
Related
SOLVED: http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851/post57916281#post57916281
The story goes, I was trying to flash CM11S after trying out the Oneplus One Lollipop Alpha. Part way through the process the command line was waiting for the device to reboot into fastboot and it never did.
Command Prompt Log:
Code:
target reported max download size of 536870912 bytes
sending 'modem' (56369 KB)...
OKAY [ 1.770s]
writing 'modem'...
OKAY [ 0.844s]
finished. total time: 2.613s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.004s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.016s
sending 'dbi' (11 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.003s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.005s
sending 'aboot' (376 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.004s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 3.521s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.009s]
writing 'rpm'...
OKAY [ 0.028s]
finished. total time: 0.037s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ 0.012s]
writing 'tz'...
OKAY [ 0.015s]
finished. total time: 0.028s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.007s
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.305s]
writing 'LOGO'...
OKAY [ 0.162s]
finished. total time: 0.468s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
< waiting for device >
Now the device is entirely unresponsive aside from a vibration when I hold down the volume and power keys. Screen stays black too and my computer will not detect my device. The Device is recognized by MSM8974 Downloader as well, but every time I select it to repair it it fails. The device also happens to be recognized by QPST Configuration software.
MSM8974 Downloader Log
Code:
8974_msimage.mbn: OK
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_backup0_64G.bin: OK
gpt_main0.bin: OK
gpt_main0_64G.bin: OK
userdata.img: FAILED
userdata_64G.img: FAILED
rawprogram0.xml: OK
rawprogram0_64G.xml: OK
NON-HLOS.bin: OK
MPRG8974.mbn: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
boot.img: FAILED
cache.img: OK
persist.img: FAILED
recovery.img: FAILED
system.img: FAILED
More Information:
Storage Capacity: 64GB
PC OS: Windows 8.1
Windows Driver Signature Verification Status: OFF
Device Drivers: PDANet Android Drivers, manually installed Oneplus One Drivers (from OPPO), ColorOS Drivers, and all the standard Google and Universal drivers.
Hello.
Same problem here. I just tried to reflash another roll since i was trying to rollback from Lollipop alpha. I did some changes in TWRP and after reboot my device did not start at all. There is only a vibration when I try to turn it on. Charging is also disabled. Screen is blank and unresponsive. Both recovery and bootloader dont work. I tried to turn my opo while connected to PC and I can hear that system found a new device. But there is no popup window, just the sound. Even after unplugging the sound can be heard.
Check this post for a solution :
https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
start from "HERE IS THE SOLUTION"
TheManDroid said:
Check this post for a solution :
https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
start from "HERE IS THE SOLUTION"
Click to expand...
Click to collapse
Been there done that. Nothing came of it, hence my logs posted above. Also I wouldn't be posting about it if I had found a solution
of course I'm recognizing your status as a senior member but was just giving you something to try since the image from the ColorOS.zip seem to work for some people and it has the required drivers for the MSM8974 downloader. but, to help everyone learn something about what you've tried :
- what factory image were you trying to use with the MSM8974 downloader?
- Is your OPO 64GB or 16GB?
- Which driver's version are you using?
I have the same problem. I suspect it's due to the differences in the partition tables between the ROMs. For example, the logo.bin for the CM11S image is around 9MB, whereas it is 512KB in the OnePlus ROM.
Hope we can get this fixed.
TheManDroid said:
of course I'm recognizing your status as a senior member but was just giving you something to try since the image from the ColorOS.zip seem to work for some people and it has the required drivers for the MSM8974 downloader. but, to help everyone learn something about what you've tried :
- what factory image were you trying to use with the MSM8974 downloader?
- Is your OPO 64GB or 16GB?
- Which driver's version are you using?
Click to expand...
Click to collapse
Sorry if I came off harsh in my previous post. That was not my intention. As for senior member, it means nothing other than I have been here a while (around the block so to speak), and I am very glad your willing to offer assistance (we need more people like you in fact), I just was noting that the thread had stated logs from the source you had mentioned. Now to answer your questions (I'll post this in the OP as well):
- You can see in the logs posted above what is missing in my partitions and what partitions are missing in general.
- 64GB
- I have tried using the PDANet drivers, manually installed Oneplus One Drivers (from OPPO), ColorOS Drivers, and all the standard Google and Universal drivers. I will also note that I am on Windows 8.1 (Driver Signature Verification turned off).
I have a locked bootloader Moto G XT 1033. I'm unable to restore stock firmware.
Bellow is the response of after the fast boot
C:\l>fastboot flash partition fsg.mbn>fastboot flash partition fsg.mbn
target reported max download size of 536870912 bytes
sending 'partition' (102 KB)...
OKAY [ 0.099s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.144s
C:\>fastboot oem lock begin
(bootloader) Ready to flash signed images
OKAY [ 2.832s]
finished. total time: 2.832s
C:\>fastboot flash partition fsg.mbn
target reported max download size of 536870912 bytes
sending 'partition' (102 KB)...
OKAY [ 0.100s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.124s
I have stock firmware.
Hi
Thanks for writing to us at XDA Assist. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your specific device forum here (bookmark/subscribe this):
Moto G
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
Moto G Q&A, Help & Troubleshooting
Good luck!
You may have better luck if you unlock the bootloader.
The fastboot oem lock command isn't going to really help since your bootloader is already locked.
The line "(bootloader) Preflash validation failed" tells me the bootloader on your phone is newer than the bootloader your are trying to load or your are trying to load an incorrect bootloader onto your phone.
I haven't change any part of the Boot loader. I found a solution for this.
I used adb command to flash lollipop. Its working fine now.
Thanks for your valuable replay.
Sorry for the delay.
Sent from my HM NOTE 1LTE using xda premium
Don't lock the bootloader first ...flash stock formaware seperately and let the device boot(we can lock bootloader later)
5.0.2 is recommended
Thanks
I tried after unlocking the bootloader.
-Janardhan TS
C:\adb>fastboot flash recovery twrp-3.0.2-0-alpha2-fastboot-marlin.img
target reported max download size of 536870912 bytes
sending 'recovery' (25552 KB)...
OKAY [ 1.357s]
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED (remote: partition [recovery] doesn't exist)
finished. total time: 1.466s
I had TWRP Alpha 2 on the device. While installing Pure Nexus i wiped device thru TWRP and the Rom failed to install sending me into Bootloop.
I have returned to stock then took OTA to Jan update. Tried multiple times, usb ports, og cable. At a loss!!
Hello and welcome to Assist
Please register an account and post in the help section for your device here
https://forum.xda-developers.com/pixel-xl/help
or in the [Q&A] Noob -Friendly Q&A Help Thread - Ask Your Questions Here! thread
Good luck
I am a newbie to Android and I would like to get help about how to root my P10 Plus. I would need to find a detailed guide with download links. My device is huawei P10 Plus 128 GB Android 7.0 EMUI version 5.1 VKY-L29C185B124, I have enabled the developer mode and enabled the "USB Debugging" and "OEM Unblocking". I have found a few topics about how to root it, and tried to follow what it says, after I get my phone in fastboot and try to install the ".img", I get the following error:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (32034 KB)...
OKAY [ 0.684s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.692s
Thanks in advance and sorry for my bad English, my newbieness, and if this was posted in the wrong forums section.
Hello, I got a google pixel 1 stuck in fastboot, power button is not working just cicling through commands like start, restart bootloader, recovery mode, power off. Flashshing stock rom not working... android 7.1 wich is in inside this phone, android 8, android 10 nothing all of those nothing. Every flash is giving me that error. I used "flash-all.bat" inside the google factory image folder... Drivers are installed and working... Fastboot devices recognise it, Fastboot reboot reboot's the device in fastboot mode.... Device is locked and I can't unlock it... Can somebody help me please ? Thank you so much !!!
target reported max download size of 536870912 bytes
sending 'bootloader' (32380 KB)...
OKAY [ 0.769s]
writing 'bootloader'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.869s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.016s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (57240 KB)...
OKAY [ 1.335s]
writing 'radio'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.432s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.015s
< waiting for device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
failed to allocate 1622564756 bytes
error: update package missing system.img
Press any key to exit...
SAMPPLE said:
...
Click to expand...
Click to collapse
THREAD CLOSED as duplicate of https://forum.xda-developers.com/pixel/help/google-pixel-1-stuck-fastboot-t4048859.
Please use the report function in future to have a moderator to move a wrongly placed thread instead of creating a new thread.
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
Click to expand...
Click to collapse