Database Info

Sideloading CWM recovery by <fastboot boot> ?

Hi buddy,
My o3d is a stock (unflashed) one. It can enter fastboot mode mainly by this method. (I have tried different methods, like the wkpark one, but finally I have succeeded with that, and with the wkparks fastboot loader tool. Anyway, I can make my way to that white LG logo fastboot place ) And when I do fastboot devices it returns my serial number. (So I am sure it is in fastboot mode.) But when I want to boot a custom recovery from PC, by the command fastboot boot recovery-clockwork-6.0.1.9-p920.img, the command prompt gives the following messages:
Code:
creating boot image...
creating boot image - 5484544 bytes
downloading 'boot.img'...
OKAY [ 2.770s]
booting...
OKAY [ -0.000s]
finished. total time: 2.790s
Seems alright. But my o3d stays still on that white LG logo. It obviously didnt boot. If I now try fastboot devices again, it gives ??? instead of the serial number:
Code:
???????????? fastboot
I have tried using recovery-clockwork-6.0.1.9-p920.img and recovery-clockwork-touch-6.0.1.9-p920.img downloaded from this page, and also the cm-7.2.0-p920 boot.img downloaded from this page. But all give the same result .
I would like to try the custom recovery, by fastboot boot recovery.img, before really flashing into my o3d, by fastboot flash recovery recovery.img .
Any clues?
Thanks so much!
midnite

I thing that you cant fasboot boot, don't work here. Something is mentioned before in some thread by wkpark.
Sent from my LG-SU760 using xda app-developers app

iodak said:
I thing that you cant fasboot boot, don't work here. Something is mentioned before in some thread by wkpark.
Sent from my LG-SU760 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply.
There are really so less resources talking about fastboot boot over the internet. Could you give me some hints where can I use fastboot boot?
Thanks!!

Re: Sideloading CWM recovery by <fastboot boot> ?
Try doing Fastboot Reboot after
Sent from my LG-P920 using xda app-developers app

JunDavis said:
Try doing Fastboot Reboot after
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply!
I have tried fastboot reboot and fastboot reboot-bootloader after. But the phone screen turns off and stays off.
---
fastboot reboot after fastboot boot recovery.img
Code:
C:\>fastboot devices
0911234567898019 fastboot
C:\>fastboot boot recovery-clockwork-6.0.1.9-p920.img
creating boot image...
creating boot image - 5484544 bytes
downloading 'boot.img'...
OKAY [ 2.740s]
booting...
OKAY [ -0.000s]
finished. total time: 2.740s
C:\>fastboot reboot
rebooting...
finished. total time: 112.290s
C:\>
At the same time, phone screen turns off, and screen remains off.
---
fastboot reboot-bootloader after fastboot boot recovery.img
Code:
C:\>fastboot devices
0911234567898019 fastboot
C:\>fastboot boot recovery-clockwork-6.0.1.9-p920.img
creating boot image...
creating boot image - 5484544 bytes
downloading 'boot.img'...
OKAY [ 2.810s]
booting...
OKAY [ 0.000s]
finished. total time: 2.820s
C:\>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 107.260s
C:\>
At the same time, phone screen turns off, and screen remains off.
---
I also tried only fastboot reboot and fastboot reboot-bootloader, without fastboot boot recovery.img:
Code:
C:\>fastboot devices
0911234567898019 fastboot
C:\>fastboot reboot
rebooting...
finished. total time: 0.010s
C:\>
Phone screen turns off at the same time, and back on to charging screen. It is not really booting into the system.
---
Code:
C:\>fastboot devices
0911234567898019 fastboot
C:\>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
C:\>
Screen turns off, like the first two trials.
---
What do those behaviours mean?
Thanks a lot!!
midnite

Re: Sideloading CWM recovery by <fastboot boot> ?
midnite_ said:
Hi buddy,
My o3d is a stock (unflashed) one. It can enter fastboot mode mainly by this method. (I have tried different methods, like the wkpark one, but finally I have succeeded with that, and with the wkparks fastboot loader tool. Anyway, I can make my way to that white LG logo fastboot place ) And when I do fastboot devices it returns my serial number. (So I am sure it is in fastboot mode.) But when I want to boot a custom recovery from PC, by the command fastboot boot recovery-clockwork-6.0.1.9-p920.img, the command prompt gives the following messages:
Code:
creating boot image...
creating boot image - 5484544 bytes
downloading 'boot.img'...
OKAY [ 2.770s]
booting...
OKAY [ -0.000s]
finished. total time: 2.790s
Seems alright. But my o3d stays still on that white LG logo. It obviously didnt boot. If I now try fastboot devices again, it gives ??? instead of the serial number:
Code:
???????????? fastboot
I have tried using recovery-clockwork-6.0.1.9-p920.img and recovery-clockwork-touch-6.0.1.9-p920.img downloaded from this page, and also the cm-7.2.0-p920 boot.img downloaded from this page. But all give the same result .
I would like to try the custom recovery, by fastboot boot recovery.img, before really flashing into my o3d, by fastboot flash recovery recovery.img .
Any clues?
Thanks so much!
midnite
Click to expand...
Click to collapse
Why all the hastle u can just flash it and when u wanna use stock recovery just flash it using the tool provided in the dark lestat unbricking thread ...Its simple ..btw dont use the latest cwm its kinda slow just use the provided in the dark lestats thread. ... http://forum.xda-developers.com/showthread.php?t=1540163
Sent from my LG-P920 using xda premium

[Script][Linux/Windows_7/8][TF700T][Firmware][Bootloader][Stock_Rom]

This is for users that would like to upgrade, downgrade from an older, newer bootloader... It will also unbirck a soft bricked 700.. All you need is fastboot installed on your Linux machine and the tablet to be able to boot into fastboot mode......
This will wipe all your data, ALL OF IT.....
This is a very easy script to run from Linux Terminal......Download the zip (MAKE SURE YOU GET THE CORRECT SKU) in the download tab at the top of the page...Extract once...Open a terminal from that directory...Than boot your tablet into fastboot mode (bootloader screen) and type just to verify your PC can see your tablet
Code:
fastboot devices
If you get an output like this your ready to run the script!!!!!
OUTPUT
Code:
[email protected] ~/Asus_tf700t_US_firmware_v10.6.1.14.10 $ fastboot devices
015d2bbce2501405 fastboot
Notice that Im in the directory of the unzipped download folder
Run the Script
Code:
./flash-all.sh
here is my output of the process so everbody is aware of what is going to happen and the amount of time it will take
OUTPUT
Code:
[email protected] ~/Asus_tf700t_US_firmware_v10.6.1.14.10 $ ./flash-all.sh
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 3.008s]
finished. total time: 3.008s
erasing 'recovery'...
OKAY [ 1.998s]
finished. total time: 1.998s
erasing 'boot'...
OKAY [ 0.536s]
finished. total time: 0.536s
erasing 'misc'...
OKAY [ 1.601s]
finished. total time: 1.601s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.953s]
finished. total time: 1.953s
erasing 'system'...
OKAY [ 1.685s]
sending 'system' (800927 KB)...
OKAY [132.489s]
writing 'system'...
OKAY [179.141s]
finished. total time: 313.315s
rebooting...
finished. total time: 0.020s
XDA:DevDB Information
[Script][Linux/Windows_7/8][TF700T][Firmware][Bootloader][Stock_Rom], a Tool/Utility for the Asus Transformer TF700
Contributors
lj50036, sbdags
Version Information
Status: Testing
Created 2014-02-12
Last Updated 2014-02-12

Windows 7/8 Only
sbdags said:
Here is the equivalent windows.bat file. NOTE this only works in Windows 7 or 8 as XP / Vista don't have the timeout command.
Copy to notepad and save as flash-all.bat in the same folder as fastboot.exe and the cwm.img file. Note you will also need a boot.blob from lj50036 to flash system.....
Alternatively unzip the attached to do the same. (Still need the source of boot.blob @lj50036) This will flash cwm 6.0.4.6 which is the latest touch version as of today:
Code:
Echo Press Control-C to quit or any key to continue!
Pause > Nul
fastboot erase system
timeout 5
fastboot erase recovery
timeout 5
fastboot erase boot
timeout 5
fastboot erase misc
timeout 5
fastboot erase cache
timeout 5
fastboot -i 0x0B05 flash system boot.blob
timeout 5
fastboot -i 0x0B05 reboot-bootloader
timeout 20
fastboot -i 0x0B05 flash recovery cwm.img
timeout 5
Echo Done - Press any key to reboot
Pause > Nul
fastboot -i 0x0B05 reboot
Click to expand...
Click to collapse
Thx sbdags for this Windows version.. For the less fortunate Windows users.... JK
Look at sbdags post for the Flash-All.zip

Reserved

Issues
Code:
#!/bin/sh
# Copyright 2012 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
fastboot erase system
sleep 5
fastboot erase recovery
sleep 5
fastboot erase boot
sleep 5
fastboot erase misc
sleep 5
fastboot erase cache
sleep 5
fastboot -i 0x0B05 flash system boot.blob
sleep 5
fastboot -i 0x0B05 reboot
Works great, but if I try to add a recovery and make the script look like this
Code:
#!/bin/sh
# Copyright 2012 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
fastboot erase system
sleep 5
fastboot erase recovery
sleep 5
fastboot erase boot
sleep 5
fastboot erase misc
sleep 5
fastboot erase cache
sleep 5
fastboot -i 0x0B05 flash system boot.blob
sleep 5
fastboot -i 0x0B05 reboot-bootloader
sleep 10
fastboot -i 0x0B05 flash recovery cwm.img
sleep 5
fastboot -i 0x0B05 reboot
I get a infinite reboot..... Can I not do it like that???
Any help with this would be great thx all.....

Try sleep 20 or 30
Just saw you got it fixed

Feedbck
sbdags said:
Try sleep 20 or 30
Click to expand...
Click to collapse
YES!!!! sleep 20 worked like a charm.. A little more testing and I will post with recovery..... LOL... Thx for the help!!!!!

sbdags said:
Try sleep 20 or 30
---------- Post added at 07:22 PM ---------- Previous post was at 07:20 PM ----------
Why are you flashing boot.blob to system? Does your boot blob contain system? Don't you mean staging?
Click to expand...
Click to collapse
The boot.blob is really the stock firmware from asus that I renamed boot.blob....The script did not like to run it as just blob, It would hang in flashing.....Should I do something different???

lj50036 said:
YES!!!! sleep 20 worked like a charm.. A little more testing and I will post with recovery..... LOL... Thx for the help!!!!!
Click to expand...
Click to collapse
Tell you what if you do the Linux I'll do the Windows version

Sweet
sbdags said:
Tell you what if you do the Linux I'll do the Windows version
Click to expand...
Click to collapse
That sounds great!!!! Let me know if there is anything I can do.....Thx for your help lj

Here is the equivalent windows.bat file. NOTE this only works in Windows 7 or 8 as XP / Vista don't have the timeout command.
Copy to notepad and save as flash-all.bat in the same folder as fastboot.exe and the cwm.img file. Note you will also need a boot.blob from lj50036 to flash system.....
Alternatively unzip the attached to do the same. (Still need the source of boot.blob @lj50036) This will flash cwm 6.0.4.6 which is the latest touch version as of today:
Code:
Echo Press Control-C to quit or any key to continue!
Pause > Nul
fastboot erase system
timeout 5
fastboot erase recovery
timeout 5
fastboot erase boot
timeout 5
fastboot erase misc
timeout 5
fastboot erase cache
timeout 5
fastboot -i 0x0B05 flash system boot.blob
timeout 5
fastboot -i 0x0B05 reboot-bootloader
timeout 20
fastboot -i 0x0B05 flash recovery cwm.img
timeout 5
Echo Done - Press any key to reboot
Pause > Nul
fastboot -i 0x0B05 reboot

Good evening gentlemen.
fastboot = Vol down + Pwr right?
I can not get into fastboot.
I am trying to recover my soft bricked tf700.
I am currently on TWRP 2.2.1.4 [i know] and can not get anywhere but the recovery screen.
anything I try I get:
E: failed to mount /system, /data, /cache, etc.
Any ideas on why this could be would be greatly appreciated.

C.patrick said:
Good evening gentlemen.
fastboot = Vol down + Pwr right?
I can not get into fastboot.
I am trying to recover my soft bricked tf700.
I am currently on TWRP 2.2.1.4 [i know] and can not get anywhere but the recovery screen.
anything I try I get:
E: failed to mount /system, /data, /cache, etc.
Any ideas on why this could be would be greatly appreciated.
Click to expand...
Click to collapse
Yes thats how you get to fastboot.. I assume you have used fastboot before..In recovery try this in recovery
Code:
adb devices
Let me know the outcome of that... Thx lj

lj50036 said:
Yes thats how you get to fastboot.. I assume you have used fastboot before..In recovery try this in recovery
Code:
adb devices
Let me know the outcome of that... Thx lj
Click to expand...
Click to collapse
Thanks for the reply!
/ # adb devices
got a
E: failed to mount /data (no such file or directory)
when under root

C.patrick said:
Good evening gentlemen.
fastboot = Vol down + Pwr right?
I can not get into fastboot.
I am trying to recover my soft bricked tf700.
I am currently on TWRP 2.2.1.4 [i know] and can not get anywhere but the recovery screen.
anything I try I get:
E: failed to mount /system, /data, /cache, etc.
Any ideas on why this could be would be greatly appreciated.
Click to expand...
Click to collapse
How did you get into this situation? Have you tried to wipe data from the bootloader menu, do a factory reset from Android, or "boot to recovery" from Android before? Any of these together with a non-working recovery (such as yours) are a recipe for a brick.
If you have a current bootloader and an old recovery, the recovery can't access your internal storage, so it cannot reset the "boot to recovery" flag set by one of the above operations.
For a possible fix, read this thread: http://forum.xda-developers.com/showthread.php?t=2437376

Hey there,
do I need an unlocked bootloader for this or is it a way to flash cwm without unlocked bootloaders? I am asking because I got my pad back from rma repair and I'm not able to unlock my bootloader now. But I have contacted the support to register my mac adress. But maybe your script is helpful in my situation?

pestbeule said:
do I need an unlocked bootloader for this
Click to expand...
Click to collapse
Yes.
pestbeule said:
or is it a way to flash cwm without unlocked bootloaders? I am asking because I got my pad back from rma repair and I'm not able to unlock my bootloader now. But I have contacted the support to register my mac adress. But maybe your script is helpful in my situation?
Click to expand...
Click to collapse
Unfortunately there is no way to install recoveries or kernels not signed by Asus with a locked bootloader. Good luck with Asus support, hope your request reaches the right person.

Hi,
Thanks for the great script but I have a novel problem!
I am running Linux Mint 16. I am one of those stupid people that tried to flash a JB rom on my 9.4.5.30 bootloader. :crying:
So I thought this was the perfect tool for me! When I ran ./flash-all.sh here is what I got:
Code:
[email protected] ~/Desktop/Untitled Folder $ ./flash-all.sh
erasing 'system'...
OKAY [ 3.457s]
finished. total time: 3.457s
erasing 'recovery'...
OKAY [ 1.918s]
finished. total time: 1.918s
erasing 'boot'...
OKAY [ 0.495s]
finished. total time: 0.495s
erasing 'misc'...
OKAY [ 0.872s]
finished. total time: 0.872s
erasing 'cache'...
OKAY [ 2.149s]
finished. total time: 2.149s
sending 'system' (800927 KB)...
OKAY [134.175s]
writing 'system'...
FAILED (remote: ()
finished. total time: 134.662s
< waiting for device >
Meanwhile the tf700 in tiny red text says "failed to process command flash:system error(0x170003). In white text above there there are a few lines which I believe were from successful attempts to erase things. There is also a line directly above the scary read text stating "Signature Match".
Not sure where I went wrong. Any ideas?
Thanks for your time!

Feedback
LurkerRWO said:
Hi,
Thanks for the great script but I have a novel problem!
I am running Linux Mint 16. I am one of those stupid people that tried to flash a JB rom on my 9.4.5.30 bootloader. :crying:
So I thought this was the perfect tool for me! When I ran ./flash-all.sh here is what I got:
Code:
[email protected] ~/Desktop/Untitled Folder $ ./flash-all.sh
erasing 'system'...
OKAY [ 3.457s]
finished. total time: 3.457s
erasing 'recovery'...
OKAY [ 1.918s]
finished. total time: 1.918s
erasing 'boot'...
OKAY [ 0.495s]
finished. total time: 0.495s
erasing 'misc'...
OKAY [ 0.872s]
finished. total time: 0.872s
erasing 'cache'...
OKAY [ 2.149s]
finished. total time: 2.149s
sending 'system' (800927 KB)...
OKAY [134.175s]
writing 'system'...
FAILED (remote: ()
finished. total time: 134.662s
< waiting for device >
Meanwhile the tf700 in tiny red text says "failed to process command flash:system error(0x170003). In white text above there there are a few lines which I believe were from successful attempts to erase things. There is also a line directly above the scary read text stating "Signature Match".
Not sure where I went wrong. Any ideas?
Thanks for your time!
Click to expand...
Click to collapse
I may know what is going on.... Take the boot.blob file and move it to your home directory, the same directory that when you open your terminal window its there so an easy check of this is just open terminal and type
Code:
ls
This will give you a list of everything in that directory make sure your boot.blob is there... here is what it looks like on my PC also Mint 16
Code:
[email protected] ~ $ ls
android bin ccache crombix Downloads
[email protected] ~ $
Once you have done that, go to this forum on xda skip the nvflash stuff and start with the fastboot commands... Just enter them one at a time,
make sure you read between the inputs and outputs of the forum, there is good info in there... Let me know if I can help in the process.. Thx lj
http://forum.xda-developers.com/showthread.php?t=2538028

Hi again!
Thanks for the advice, I am in the process of doing what you said but already ran into a hiccup. When I ran 'fastboot -w' I get
Code:
athena torytop # fastboot -w
erasing 'userdata'...
OKAY [ 27.601s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
erasing 'cache'...
OKAY [ 1.428s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
finished. total time: 29.030s
Also, I wasn't able to run fastboot with sudo, it says command not found. So I ran sudo su and then proceeded per your advice minus the sudo commands. I will edit this post when I finish.
Edit: Failed with the same error, and I can't help but wonder if the failure to partition isn't related. This is not my own tablet, a friend gave it to me as it was bricked already, but I was able to get into recovery so took this on as a fun little project. So yeah, I have no clue what he did to brick it, maybe messed with partitions?

LurkerRWO said:
Hi again!
Thanks for the advice, I am in the process of doing what you said but already ran into a hiccup. When I ran 'fastboot -w' I get
Code:
athena torytop # fastboot -w
erasing 'userdata'...
OKAY [ 27.601s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
erasing 'cache'...
OKAY [ 1.428s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
finished. total time: 29.030s
Also, I wasn't able to run fastboot with sudo, it says command not found. So I ran sudo su and then proceeded per your advice minus the sudo commands. I will edit this post when I finish.
Click to expand...
Click to collapse
Skip it

Cannot access system to turn on developer mode

Hi I have been working all day trying to get my moto G up and running again.
The problem is that when I boot it shows the boot animations then boots to a blank screen with backlight on.
So far I have tried.
1. Going into the bootloader then into recovery by holding up for 10s then tapping power. From here I wiped back to factory settings. Then I tired to wipe cach partition. When I did this it said ERASING... then rebooted a second later.
It went back to the same black screen after I booted.
1. Flashing a new recovery. TWERP. The flashing process seemed to go ok ... .
target max-sparse-size: 256MB
sending 'recovery' (9488 KB)...
OKAY [ 0.318s]
writing 'recovery'...
OKAY [ 0.170s]
finished. total time: 0.488s
but when I checked I was still on stock recovery.
Then I went and used fastboot to erase recovery and tried flashing again and rebooted bootloader with fastboot reboot command. Still on stock recovery.
2. Then I tried sideloading falcon to this device it aborted.
3. I discovered the sideload boot recovery and when I was able to load TWERP into RAM and boot from there I thought I had it made.
I tried sideloading my ROM from here and got Error 7 I am on bootloader 4113 and I need to be on a newer on.
4. Flashed bootloader
First with getvar I was able to confirm I was on 13. I downloaded 41.19 and flashed that
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.095s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.099s]
but when I rebooted the bootloader with fastboot reboot, and did getvar again. I saw that I was still on 13.
This is only a short summary of the highlights of what I have tried with this phone today. Can anybody give me and idea how to proceed? I'm stuck fast here.
Then I tried simply booting into TWRP recovery with

And yes I unlocked the bootloader. I also tried flashing a stock ROM from here

I've seen similar reports like yours and no solution. It is supposed to be a hardware error. To confirm this, fastboot boot twrp.img and then run adb shell dmesg > dmesg.txt and post the file, maybe there are any clues in this kernel log.

_that said:
I've seen similar reports like yours and no solution. It is supposed to be a hardware error. To confirm this, fastboot boot twrp.img and then run adb shell dmesg > dmesg.txt and post the file, maybe there are any clues in this kernel log.
Click to expand...
Click to collapse
Sorry. I am not sure exactly how to do this. Would you be so nice as to post command here so that I can cut and paste into command line?

jonawald said:
Sorry. I am not sure exactly how to do this. Would you be so nice as to post command here so that I can cut and paste into command line?
Click to expand...
Click to collapse
You can literally cut and paste the commands from my post (if your twrp image is named "twrp.img"). Between fastboot and adb, wait for TWRP to start up.

_that said:
You can literally cut and paste the commands from my post (if your twrp image is named "twrp.img"). Between fastboot and adb, wait for TWRP to start up.
Click to expand...
Click to collapse
I tried this
adb-mac adb dmesg > dmesg.txt
and this
adb-mac adb shell dmesg > dmesg.txt
I am using a mac as you might guess from the -mac piece. When I try this I get
Android Debug Bridge version 1.0.32
Revision 760a64fe84b7-android
-a - directs adb to listen on all interfaces for a connection
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
etc.

[Help plz] Asus Me302kl Softbricked

Hi all
i have asus memo pad fd10, model: me302KL with soft bricked problem ( stuck at fastboot mode and show ERROR: invalid boot image )
i try to flash with fastboot flash recovery from image files but failed..
below are the message:
fastboot flash recovery recovery.img
sending 'recovery' (6002 KB)...
OKAY [ 0.188s]
writing 'recovery'...
FAILED (remote: Invalid input Image. Cannot flash before unlock)
finished. total time: 0.219s
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.188s]
booting...
FAILED (remote: Bootloader is locked)
finished. total time: 0.203s
i think bootloader is locked. How to unlock boot loader? i don't have any os to install apk and unlock/root the me302kl.
What should i do now? Please help and provide me any advice.
Many thanks !!

kit9 said:
Hi all
i have asus memo pad fd10, model: me302KL with soft bricked problem ( stuck at fastboot mode and show ERROR: invalid boot image )
i try to flash with fastboot flash recovery from image files but failed..
below are the message:
fastboot flash recovery recovery.img
sending 'recovery' (6002 KB)...
OKAY [ 0.188s]
writing 'recovery'...
FAILED (remote: Invalid input Image. Cannot flash before unlock)
finished. total time: 0.219s
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.188s]
booting...
FAILED (remote: Bootloader is locked)
finished. total time: 0.203s
i think bootloader is locked. How to unlock boot loader? i don't have any os to install apk and unlock/root the me302kl.
What should i do now? Please help and provide me any advice.
Many thanks !!
Click to expand...
Click to collapse
Try "fastboot oem unlock" first to unlock bootloader then try "fastboot flash recovery recovery.img" to flash recovery.

I tried fastboot oem unlock
It show no this command
Please help..thanks!

kit9 said:
I tried fastboot oem unlock
It show no this command
Please help..thanks!
Click to expand...
Click to collapse
Try these guide.
http://androtab.info/memopad/fastboot/

Thanks Ashwinrg, I tried your link, but it seems it can't unlock...
fastboot oem log
...
FAILED (remote: unknown command)
fastboot oem unlock61646
...
FAILED (remote: unknown command)
fastboot oem unlockD696E
...
FAILED (remote: unknown command)
Any other suggestion to unlock my Me302kl in bootloader ?
Thank you!

kit9 said:
Thanks Ashwinrg, I tried your link, but it seems it can't unlock...
fastboot oem log
...
FAILED (remote: unknown command)
fastboot oem unlock61646
...
FAILED (remote: unknown command)
fastboot oem unlockD696E
...
FAILED (remote: unknown command)
Any other suggestion to unlock my Me302kl in bootloader ?
Thank you!
Click to expand...
Click to collapse
Asus provide official way to unlock bootloader of your android. It is an app that want to install in your android and run.
As you can't install these app because you can't boot your android.
I am uploading these app that can help others.

Ashwinrg said:
Asus provide official way to unlock bootloader of your android. It is an app that want to install in your android and run.
As you can't install these app because you can't boot your android.
I am uploading these app that can help others.
Click to expand...
Click to collapse
Thanks, but i can't enter to the android system again...I can go to the fastboot mode only...
How could I install the apk and unlock my device?
Any one know how to use this apk in bootloader mode?
Thanks!

any one have solution / advice?
I could go to fastboot mode, any suggest to save from this Softbricked?
Thanks!

kit9 said:
Thanks, but i can't enter to the android system again...I can go to the fastboot mode only...
How could I install the apk and unlock my device?
Any one know how to use this apk in bootloader mode?
Thanks!
Click to expand...
Click to collapse
Download stock rom of your android and flash in fastboot mode.
32 gb variant
http://firmware-all.com/605-asus-memo-pad-fhd-10-me302kl-32gb-lte.html
16 gb variant
http://firmware-all.com/2171-asus-memo-pad-fhd-10-me302kl-16gb-lte.html
Download torrent file and download in torrent client.

Ashwinrg said:
Download stock rom of your android and flash in fastboot mode.
32 gb variant
http://firmware-all.com/605-asus-memo-pad-fhd-10-me302kl-32gb-lte.html
16 gb variant
http://firmware-all.com/2171-asus-memo-pad-fhd-10-me302kl-16gb-lte.html
Download torrent file and download in torrent client.
Click to expand...
Click to collapse
Thanks, i am downloading the file.
Do it have the instruction how to install it in fastboot mode?
thank you!

kit9 said:
Thanks, i am downloading the file.
Do it have the instruction how to install it in fastboot mode?
thank you!
Click to expand...
Click to collapse
May be Asus flash tool help you.
http://www.asuszenfoneblog.com/2015/01/how-to-use-asus-flash-tool-installer-for-zenfone.html

Ashwinrg said:
May be Asus flash tool help you.
http://www.asuszenfoneblog.com/2015/01/how-to-use-asus-flash-tool-installer-for-zenfone.html
Click to expand...
Click to collapse
Thanks first.
I am busy in this week, i will try if it could solve the lock bootloader . Thank you!

Hi all
I still can't get the bootloader to unlock..any suggestion to unlock the bootloader please..
are below information could help what is the command to unlock the bootloader??
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
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 [bootloader] reboot device, optionally into bootloader
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

Ashwinrg said:
May be Asus flash tool help you.
http://www.asuszenfoneblog.com/2015/01/how-to-use-asus-flash-tool-installer-for-zenfone.html
Click to expand...
Click to collapse
Let me report what I tried, do you know what is the problem?
I try this Asus flash tool, i can connect it from this tool.
However, I can't find my model ME302kl in this tool list.
I download the rom from asus website
https://www.asus.com/hk/Tablets/ASUS_MeMO_Pad_FHD_10_ME302KL/HelpDesk_Download/
I tried few other model(eg.Me103K) in the asus tool list since I can't find my model ME302kl in this tool list.
When press start to flash, it started to unzip the ROM and then show fail.
"Run flash image script failure(Not found the flash script file)
I thinks it is because I can't select correct model??
thank you!

Any one know how to save my soft bricked pad me302kl??
thanks!

push

Hi, I am on look out for nougat ROM for my phone.. searched everywhere on the internet.. Those with more insight can help me?

azoksky said:
Hi, I am on look out for nougat ROM for my phone.. searched everywhere on the internet.. Those with more insight can help me?
Click to expand...
Click to collapse
Download from below link
https://forum.xda-developers.com/android/general/rom-android-n-memopad-10-fhd-lte-t3466524

Ashwinrg said:
Download from below link
https://forum.xda-developers.com/android/general/rom-android-n-memopad-10-fhd-lte-t3466524
Click to expand...
Click to collapse
Thanks, Wil see that

Any one know how to save my pad??

Bootloop after installing an Factory Image for Android 9.0

Hi, i just bought a Google Pixel from Ebay an tried to install an factory image for Android 9 from the Google Website. After fastboot the flash-all.sh (ive got Ubuntu) it got stuck a on the bootscreen (The Google Logo flashes in an instance and the Screen goes black again). Unfortunally the device is locked again (bootloader ist locked), so adb is not working. fastboot works but when i install some other factory images from the google website the problem with the flashing bootscreen reappears.
Loading into bootloader works:
Product/Variant: sailfish-US-PVT
Serial Number FA72H0300560
CPU: MSM8996SG-AB 0x10001
UFS: 32 GB Samsung
DRAM:4096MB Hynix LPDDR4
Boot-slot: a
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
Could anyone help?
Thanks in advance.

Not sure but I think U can try booting into TWRP using "fastboot flash recovery twrp" command in CMD and than switch boot slot to b, my pixel is in the same situation - I can't boot into slot a and switching to b works
oh sry, the command is "fastboot boot path/to/twrp.img"

Thanks for your help, but it didn't work.
When I try to fastboot with following commands, it says:
sudo ./fastboot boot twrp-3.2.3-1-sailfish.img
Code:
Downloading 'boot.img' OKAY [ 0.785s]
booting (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 0.963s
sudo ./fastboot flash recovery twrp
Code:
fastboot: error: cannot load 'twrp': No such file or directory
I have Ubuntu with local platform-tools, so the commands look a little bit different...

Double-check the checksum of the downloaded file.
Open the flash-all.sh file in a text editor, and manually run each of the flash commands individually. See if any of them throw an error.
You might also try to install the OTA.

I tried the first command in the flash-all.sh with the same results:
sudo ./fastboot flash bootloader bootloader-sailfish-8996-012001-1808030001.img
Code:
Sending 'bootloader_a' (32384 KB) OKAY [ 0.951s]
Writing 'bootloader_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.189s
I will try out the OTA tomorrow. Does anyone know how to handle the payload.bin in to OTA.zip under a Linux-System?
ADB seems not be working. SO adb sideload ota_file.zip, like its mentioned on the google website seems to be also no option....

ArchArch said:
I tried the first command in the flash-all.sh with the same results:
sudo ./fastboot flash bootloader bootloader-sailfish-8996-012001-1808030001.img
Code:
Sending 'bootloader_a' (32384 KB) OKAY [ 0.951s]
Writing 'bootloader_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.189s
I will try out the OTA tomorrow. Does anyone know how to handle the payload.bin in to OTA.zip under a Linux-System?
ADB seems not be working. SO adb sideload ota_file.zip, like its mentioned on the google website seems to be also no option....
Click to expand...
Click to collapse
You need to re-unlock your bootloader first, then. Try fastboot flashing unlock .

No luck.
sudo ./fastboot flashing unlock
Code:
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.007s
sudo ./fastboot oem unlock
Code:
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.038s

ArchArch said:
sudo ./fastboot flash recovery twrp
Code:
fastboot: error: cannot load 'twrp': No such file or directory
I have Ubuntu with local platform-tools, so the commands look a little bit different...
Click to expand...
Click to collapse
Did U opened CMD from the folder in which the TWRP file is located? Just type in CMD: "fastboot boot", and after "boot" type "twr" and press TAB button, program will locate the file itself.

Levan_i said:
Did U opened CMD from the folder in which the TWRP file is located? Just type in CMD: "fastboot boot", and after "boot" type "twr" and press TAB button, program will locate the file itself.
Click to expand...
Click to collapse
He's using linux. The reason his flashes have been unsuccessful is because the bootloader is locked.

Tanks for your efforts so far...
Just for clarification: The initial plan was to root my device, according to the XDA-Guide for rooting an Pixel XL Android 9.0 (with the Files for my "Sailfish"-Pixel) https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866
First when I bought the Pixel the "OEM Unlock"-Option in the Developers-Menu was greyed out.
So i tried out, beneath some other guides, the XDA-Guide for unlocking a Verizon Pixel and it worked. https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
So I thought its an VerizonPixel, installed an Verizon Image from the Google Website, got always the message at bootup that an unlocked bootloader is some sort of threat, closed the Bootloader and the flashing bootscreen-problem began…