Related
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
So i have both the short story with some important explanation and the long story on what I've already tried.
Short story
So my dad bought a oneplus one 16GB from someone and the phone has a bootloop when you try the boot into the system.
I tried to unlock the bootloader, but it runned the command and it just reboots to recovery and the bootloader is still locked.
Also the tamperflag is true so that means that the bootloader has already been unlocked and is relocked.
I can't also boot from a custom recovery image because the bootloader is locked (I think it can with CM11S).
Rom: I guess it is CM12S (with the blinking Cyanogen logo at startup).
Recovery: probably the recovery from CM12S (Cyanogen recovery as text and it is a touch recovery).
Long story
So I am going to tell you my story.
My dad bought an oneplus one (16GB) from someone that had a boot loop at startup.
When he told me that I just thought that it was going to be pretty easy to fix: unlock bootloader, flash custom recovery and install a custom rom.
Now, it didn’t roll out as we both expected.
When I unlocked the bootloader it told me after 10 seconds that it was OK.
Pretty weird was that it took so long.
After some research I found that you need to reboot from the rom with adb and that you then can unlock the bootloader. On all my other devices I did that, but now I couldn’t because I wasn’t able to boot inside the rom.
After I “successfully” unlocked the bootloader I did the command “fastboot oem device-info” and it told me that the bootloader was still locked but it was tampered.
I tried after that to boot from a TWRP recovery image but i wasn't able to because the bootloader was locked.
After some research I came at a post on the oneplus forum with a guy that approximately had the same issue except that I can still go into recovery.
I founded this post.
And I first wanted to see if I couldn’t go into recovery and sideload a zip that is signed. That was signed in this thread.
As it expected because I didn’t had a custom recovery it didn’t worked and also I used this tool for adb and fastboot.
I didn’t give up by that one so easily so I tried it with this to sideload the files and I renamed it this time to update.zip. Again as expected an error but this time it was another error.
There came a bunch of errors on the phone especially cache errors and one that said that I had an outdated ADB (at least version 1.0.32).
Weirdly enough I had version 1.0.32 .
And now it tried the trick they told me here.
From the thread for windows 7 and 8 here.
I first did this without “erasing the bootloader”.
I tried this both on windows 8.1 and on windows xp with both administrator rights and I switched between 3 cables each time.
As you see in the attached zip, I correctly installed the driver, this was also the fact for the pc with windows xp.
I also verified the files but there were some that failed (also in the pictures).
It flashes the file 8974_msimage.mbn and then the phone shuts down. I tried this at least three times for each computer.
Then I founded this thread.
And tried this also and exactly the same problem as with color.
Then I tried the same with erasing the bootloader and it had the same issue and I couldn’t erase the bootloader doing to that my partition table doesn’t exist(also in the pictures).
The only thing that I only think that I can do is with a flash tool that uses also the above method but I don’t find any with that I know how to use it.
Any help is appreciated.
Ps: I attached a zip file with some pictures to make it more clear and understandable and i am also dutch, so sorry if my English is bad.
ninjawulf98 said:
So I am going to tell you my story.
My dad bought an oneplus one (16GB) from someone that had a boot loop at startup.
When he told me that I just thought that it was going to be pretty easy to fix: unlock bootloader, flash custom recovery and install a custom rom.
Now, it didn’t roll out as we both expected.
When I unlocked the bootloader it told me after 10 seconds that it was OK.
Pretty weird was that it took so long.
After some research I found that you need to reboot from the rom with adb and that you then can unlock the bootloader. On all my other devices I did that, but now I couldn’t because I wasn’t able to boot inside the rom.
After I “successfully” unlocked the bootloader I did the command “fastboot oem get-lockstate” and it told me that the bootloader was locked but it was tampered.
Sadly enough when I typed the command now it takes forever to answer, after more than 10 minutes it still displays that it is waiting.
After some research I came at a post on the oneplus forum with a guy that approximately had the same issue except that I can still go into recovery.
I founded this post.
And I first wanted to see if I couldn’t go into recovery and sideload a zip that is signed. That was signed in this thread.
As it expected because I didn’t had a custom recovery it didn’t worked and also I used this tool for adb and fastboot.
I didn’t give up by that one so easily so I tried it with this to sideload the files and I renamed it this time to update.zip. Again as expected an error but this time it was another error.
There came a bunch of errors on the phone especially cache errors and one that said that I had an outdated ADB (at least version 1.0.32).
Weirdly enough I had version 1.0.32 .
And now it tried the trick they told me here.
From the thread for windows 7 and 8 here.
I first did this without “erasing the bootloader”.
I tried this both on windows 8.1 and on windows xp with both administrator rights and I switched between 3 cables each time.
As you see in the attached zip, I correctly installed the driver, this was also the fact for the pc with windows xp.
I also verified the files but there were some that failed (also in the pictures).
It flashes the file 8974_msimage.mbn and then the phone shuts down. I tried this at least three times for each computer.
Then I founded this thread.
And tried this also and exactly the same problem as with color.
Then I tried the same with erasing the bootloader and it had the same issue and I couldn’t erase the bootloader doing to that my partition table doesn’t exist(also in the pictures).
The only thing that I only think that I can do is with a flash tool that uses also the above method but I don’t find any with that I know how to use it.
Any help is appreciated.
Ps: I attached a zip file with some pictures to make it more clear and understandable and i am also dutch, so sorry if my English is bad.
Click to expand...
Click to collapse
Are you able to enter fastboot mode now?
Bobbi lim said:
Are you able to enter fastboot mode now?
Click to expand...
Click to collapse
Yes, i can also enter stock recovery but i am unable to boot from custom recovery through fastboot. Because the bootloader is locked.
ninjawulf98 said:
Yes, i can also enter stock recovery but i am unable to boot from custom recovery through fastboot. Because the bootloader is locked.
Click to expand...
Click to collapse
Have you tried "fastboot oem unlock" in fastboot mode?
Sent from my Nexus 7 using Tapatalk
Bobbi lim said:
Have you tried "fastboot oem unlock" in fastboot mode?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes, after - + 10 seconds it says ok and it reboots the phone to the stock recovery.
When i try to flash twrp it just fails because my bootloader is locked.
ninjawulf98 said:
Yes, after - + 10 seconds it says ok and it reboots the phone to the stock recovery.
When i try to flash twrp it just fails because my bootloader is locked.
Click to expand...
Click to collapse
Which stock recovery is it? ColorOS? CM? Or OxygenOS?
I had a similar issue when I tried to unlock mine when I first got my OPO
Sent from my Nexus 7 using Tapatalk
My dad bought the phone from someone and the only thing i can see is cyanogen recovery. At boot i have a blinking cyanogen text. Probably it was already unlocked because the tamper flag is tampered.
ninjawulf98 said:
My dad bought the phone from someone and the only thing i can see is cyanogen recovery. At boot i have a blinking cyanogen text. Probably it was already unlocked because the tamper flag is tampered.
Click to expand...
Click to collapse
Maybe my previous post was a bit confusing but it is still locked, i meant that the previous owner locked it and then relocked it.
Can you tell us the exact copy/paste and output of below command :
fastboot oem device-info
Regards
Girish Sharma
GirishSharma said:
Can you tell us the exact copy/paste and output of below command :
fastboot oem device-info
Regards
Girish Sharma
Click to expand...
Click to collapse
I've got the following:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle rechten voorbehouden.
C:\Windows\System32>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Windows\System32>
I am not sure but, what if you paste the output of fastboot oem unlock from the adb folder, I.e just try to run the command from that directory in which fastboot.exe present. Just paste the output as you done previously.
Regards
Girish Sharma
GirishSharma said:
I am not sure but, what if you paste the output of fastboot oem unlock from the adb folder, I.e just try to run the command from that directory in which fastboot.exe present. Just paste the output as you done previously.
Regards
Girish Sharma
Click to expand...
Click to collapse
Then i've got the following:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
866878f3 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 10.112s]
finished. total time: 10.114s
C:\Program Files (x86)\Minimal ADB and Fastboot>
And when i do the command: "fastboot oem device-info" again.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.010s]
finished. total time: 0.011s
C:\Program Files (x86)\Minimal ADB and Fastboot>
ninjawulf98 said:
Then i've got the following:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
866878f3 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 10.112s]
finished. total time: 10.114s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
I don't know if this is an issue but i have both the adb and fastboot tools installed from here and the adb, fastboot and drivers here .
Since I am not an android expert, so I shall wait with you to see other member replies. Between if you can check this link too:https://forums.oneplus.net/threads/stuck-in-fastboot-with-locked-boot-loader.104446/page-2
Regards
Girish Sharma
GirishSharma said:
Since I am not an android expert, so I shall wait with you to see other member replies. Between if you can check this link too:https://forums.oneplus.net/threads/stuck-in-fastboot-with-locked-boot-loader.104446/page-2
Regards
Girish Sharma
Click to expand...
Click to collapse
I already founded that thread and did the solution that worked for him and another solution that a guy a few posts above him mentioned. Sadly enough without any results.
Anyway, thanks for the help and all the effort you did!
I just am going to mention it here before I will do it, to avoid to make the situation more worse then it already is.
So you can enter qualcomm hsloader (connect the phone to the pc, press 5-10 seconds volume up + power, screen remains dark).
And there are two tools (which have both the same base) here and here .
Now, when I follow the guide for both tools, always when it flashes the first file (8974_msimage.mbn), after flashing the phone shuts down.
And yes, I gave it administrator rights and the drivers are properly installed.
I tried it also on windows xp (completly clean test computer, yes I have a lot of them )
Now I saw on the oneplus forum a post .
And when I tried the command "fastboot erase bootloader" it gave me the following output:
C:\Windows\System32>fastboot erase bootloader
erasing 'bootloader'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.006s
Well if I try this with the command to erase the kernel partition "fastboot erase boot" I think.
Well might this then work, so that the device after flashing the first file doesn't shutdown?
Again I just want to mention it here before I make the situation more worse then it already is.
ninjawulf98 said:
I just am going to mention it here before I will do it, to avoid to make the situation more worse then it already is.
So you can enter qualcomm hsloader (connect the phone to the pc, press 5-10 seconds volume up + power, screen remains dark).
And there are two tools (which have both the same base) here and here .
Now, when I follow the guide for both tools, always when it flashes the first file (8974_msimage.mbn), after flashing the phone shuts down.
And yes, I gave it administrator rights and the drivers are properly installed.
I tried it also on windows xp (completly clean test computer, yes I have a lot of them )
Now I saw on the oneplus forum a post .
And when I tried the command "fastboot erase bootloader" it gave me the following output:
C:\Windows\System32>fastboot erase bootloader
erasing 'bootloader'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.006s
Well if I try this with the command to erase the kernel partition "fastboot erase boot" I think.
Well might this then work, so that the device after flashing the first file doesn't shutdown?
Again I just want to mention it here before I make the situation more worse then it already is.
Click to expand...
Click to collapse
Now actually i think that the partition bootloader doesn't exists but boot does (which I think containts the bootloader and the kernel).
After waiting very unpationtly -+ 24 hours I tried it.
Sadly enough again without success.
CMD copy:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle rechten voorbehouden.
C:\Windows\System32>fastboot devices
866878f3 fastboot
C:\Windows\System32>fastboot erase boot
erasing 'boot'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.057s
C:\Windows\System32>
Fried emmc. Sell it for junk.
Sent from my SM-G920T
Hi,
I am stuck with a similar issue. Only the way I landed in this situation is slightly different.
Without unlocking the bootloader (I just forgot to do that!), I ran the below command.
Code:
fastboot format cache
It erased the cache but failed to write to it because the device is still locked.
On rebooting, the device was stuck overnight on the "Cyanogen" display screen.
I forcibly powered it off using the power button.
Then I fastbooted it.
Then from the command prompt I tried to run a few commands - see output below
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.031s]
finished. total time: 0.031s
And then this -
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot unlock oem
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
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 bootlo
ader
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
and this -
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
...
That's it. For some reason,"fastboot unlock oem" takes me to fastboot help and "fastboot flashing unlock" just goes in a long endless wait.
Any way out?
Thanks,
Deepak Gupta
Deep.G said:
Hi,
I am stuck with a similar issue. Only the way I landed in this situation is slightly different.
Without unlocking the bootloader (I just forgot to do that!), I ran the below command.
Code:
fastboot format cache
It erased the cache but failed to write to it because the device is still locked.
On rebooting, the device was stuck overnight on the "Cyanogen" display screen.
I forcibly powered it off using the power button.
Then I fastbooted it.
Then from the command prompt I tried to run a few commands - see output below
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.031s]
finished. total time: 0.031s
And then this -
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot unlock oem
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
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 bootlo
ader
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
and this -
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
...
That's it. For some reason,"fastboot unlock oem" takes me to fastboot help and "fastboot flashing unlock" just goes in a long endless wait.
Any way out?
Thanks,
Deepak Gupta
Click to expand...
Click to collapse
The command for unlocking the bootloader is "fastboot oem unlock" not "fastboot unlock oem".
Also sometimes when you type a commando that isn't recognised by the phone it can take forever.
So, I think that the commando "fastboot flashing unlock" doesn't exist.
Anyway I think I know now for sure that the previous owner erased and/or formatted the cache.
Hi all,
I have a 6045i variant of the idol3. I have successfully unlocked the bootloader and have been trying now to flash TWRP. Then I will install a custom ROM and SU to hopefully end the lagfest.
However, no matter which TWRP I try (2.8.7.0 or 3.0.0-1) it isn't sticking. I've followed the appropriate threads here using adb fastboot to flash the recoveries but when I try to get to recovery it goes to the stock version.
I'm running the latest stock firmware: 5.0.2-7SRN-UEN0
Here's the output of the adb session.
Code:
C:\adb>fastboot -i 0x1bbb devices
cc22eea2 fastboot
C:\adb>fastboot -i 0x1bbb oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Boot cpus: androidboot.earlyboot_cpus=3,4,5,6,7
(bootloader) Big core max freq:
(bootloader) Small core max freq:
OKAY [ 0.028s]
finished. total time: 0.029s
C:\adb>fastboot -i 0x1bbb flash recovery twrp-3.0.0-1-idol3.img
target reported max download size of 268435456 bytes
sending 'recovery' (23880 KB)...
OKAY [ 0.803s]
writing 'recovery'...
OKAY [ 2.207s]
finished. total time: 3.014s
C:\adb>fastboot -i 0x1bbb reboot
rebooting...
finished. total time: 0.003s
When I invoke recovery (either thru adb or power on/volume up) it loads into stock 3e recovery.
Any tips to get past this? I've done a fair amount of searching for similar issues here but haven't ran into any help.
thanks,
try this:
if youflash the TWRP recovery then turn off the phone and right go to recovery (volume up+power).
If you can go t oTWRP recovery and after reboot yo uwill get the stock one again, then there is a stratup script which replaces the custom recovery with the stock one, on every startup.
You have then to flash the twrp recovry, right boot into it and using the file manager inside TWRP to find the script and delete it.
mikehd1959 said:
Hi all,
I have a 6045i variant of the idol3. I have successfully unlocked the bootloader and have been trying now to flash TWRP. Then I will install a custom ROM and SU to hopefully end the lagfest.
However, no matter which TWRP I try (2.8.7.0 or 3.0.0-1) it isn't sticking. I've followed the appropriate threads here using adb fastboot to flash the recoveries but when I try to get to recovery it goes to the stock version.
I'm running the latest stock firmware: 5.0.2-7SRN-UEN0
Here's the output of the adb session.
Code:
C:\adb>fastboot -i 0x1bbb devices
cc22eea2 fastboot
C:\adb>fastboot -i 0x1bbb oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Boot cpus: androidboot.earlyboot_cpus=3,4,5,6,7
(bootloader) Big core max freq:
(bootloader) Small core max freq:
OKAY [ 0.028s]
finished. total time: 0.029s
C:\adb>fastboot -i 0x1bbb flash recovery twrp-3.0.0-1-idol3.img
target reported max download size of 268435456 bytes
sending 'recovery' (23880 KB)...
OKAY [ 0.803s]
writing 'recovery'...
OKAY [ 2.207s]
finished. total time: 3.014s
C:\adb>fastboot -i 0x1bbb reboot
rebooting...
finished. total time: 0.003s
When I invoke recovery (either thru adb or power on/volume up) it loads into stock 3e recovery.
Any tips to get past this? I've done a fair amount of searching for similar issues here but haven't ran into any help.
thanks,
Click to expand...
Click to collapse
You can just try like this
Connect to Pc with usb
Open Adb And Fastboot
Enable Debugging on Device
type "adb reboot bootloader"
Then write"fastboot -i 0x1bbb flash recovery twrp-3.0.0-1-idol3.img"
and then"fastboot -i 0x1bbb boot twrp-3.0.0-1.img"-wait 2s and Automaticily Device will boot to TWRP recovery so you can flash what do you want
Alek Dev said:
You can just try like this
Connect to Pc with usb
Open Adb And Fastboot
Enable Debugging on Device
type "adb reboot bootloader"
Then write"fastboot -i 0x1bbb flash recovery twrp-3.0.0-1-idol3.img"
and then"fastboot -i 0x1bbb boot twrp-3.0.0-1.img"-wait 2s and Automaticily Device will boot to TWRP recovery so you can flash what do you want
Click to expand...
Click to collapse
Thanks. That's what I just stumbled into as well. I've gotten into TWRP and was able to reboot in TWRP back into TWRP recovery. So now I'm trying reboot to system from TWRP. I'll then reboot to recovery to see if TWRP has stuck.
While in TWRP I used the terminal to find the init scripts. Here's the list:
Code:
init
init.qcom.usb.sh
init.rc
init.recovery.qcom.rc
init.recovery.qcom.usb.rc
When I executed a ls -lh to see timestamps, they were all some default 1969 year. So I didn't muck with anything with init.
Just completed my first boot into the OS. I shut it down fully then restarted with power on + Vol Up and it went straight to TWRP.
So the trick was to do the flash recovery then boot the image as you suggested.
Is this typical for this device? I've never encountered this on other phones (S3 for example).
mikehd1959 said:
Thanks. That's what I just stumbled into as well. I've gotten into TWRP and was able to reboot in TWRP back into TWRP recovery. So now I'm trying reboot to system from TWRP. I'll then reboot to recovery to see if TWRP has stuck.
While in TWRP I used the terminal to find the init scripts. Here's the list:
Code:
init
init.qcom.usb.sh
init.rc
init.recovery.qcom.rc
init.recovery.qcom.usb.rc
When I executed a ls -lh to see timestamps, they were all some default 1969 year. So I didn't muck with anything with init.
Just completed my first boot into the OS. I shut it down fully then restarted with power on + Vol Up and it went straight to TWRP.
So the trick was to do the flash recovery then boot the image as you suggested.
Is this typical for this device? I've never encountered this on other phones (S3 for example).
Click to expand...
Click to collapse
so the trick was been to flash the TWRP recovery and then aumotacilly go to Recovery...and if you want to restart phone...just reboot it .you no need to flash boot
Alek Dev said:
so the trick was been to flash the TWRP recovery and then aumotacilly go to Recovery...and if you want to restart phone...just reboot it .you no need to flash boot
Click to expand...
Click to collapse
Except that didn't work for me. It would consistently go to stock recovery no matter how I tried to exit adb. If I rebooted to recovery in adb the stock recovery would launch. If I plain rebooted to OS and then shut down and restart (power on + Vol Up) it would go to stock recovery. It was only when I did the commands as listed above would it at last go to TWRP and persist across reboots.
mikehd1959 said:
Except that didn't work for me. It would consistently go to stock recovery no matter how I tried to exit adb. If I rebooted to recovery in adb the stock recovery would launch. If I plain rebooted to OS and then shut down and restart (power on + Vol Up) it would go to stock recovery. It was only when I did the commands as listed above would it at last go to TWRP and persist across reboots.
Click to expand...
Click to collapse
So use the commands to go to Twrp..you can try to lock the bootloader and try again to unlock and then flash Twrp..
Edit:So it can be the problem with the system
Alek Dev said:
So use the commands to go to Twrp..you can try to lock the bootloader and try again to unlock and then flash Twrp..
Edit:So it can be the problem with the system
Click to expand...
Click to collapse
No need to do as you describe. It is now working correctly. When I go to recovery, it launches TWRP as expected. Issue closed.
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…
So somehow I seemed to have bricked my Pixel 3 XL. I've bootet into fastboot and ahve enabled OEM unlock beforehand in the dev options. Also the screen tells me "Device state: unlocked" after I ran
Code:
fastboot flashing unlock
.
But now no matter what I do I end up with a black screen. Can't boot into my OS and can't boot into recovery. I also can't flash a factory ROM or temp boot into TWRP. I also can't flash anything.
Code:
fastboot boot twrp-3.2.3-4-crosshatch.img
downloading 'boot.img'...
OKAY [ 0.396s]
booting...
FAILED (remote: Error calling AvbLoadAndVerifyBootImages Load Error)
finished. total time: 0.765s
Code:
fastboot flash recovery twrp-3.2.3-4-crosshatch.img
target reported max download size of 268435456 bytes
sending 'recovery' (65536 KB)...
OKAY [ 0.392s]
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
finished. total time: 0.758s
Code:
fastboot flashing unlock
...
(bootloader) Device already unlocked
OKAY [ 0.318s]
finished. total time: 0.318s
Do you have the latest sdk platform tools?
jd1639 said:
Do you have the latest sdk platform tools?
Click to expand...
Click to collapse
afaik I don't have them at all. Never needed them for my Fairphone 2. I am running Ubuntu 18.04.
Ignore..
IronDude said:
afaik I don't have them at all. Never needed them for my Fairphone 2. I am running Ubuntu 18.04.
Click to expand...
Click to collapse
I'm not very familiar with Linux. The latest firmware is compressed with a newer compression method which older versions of fastboot don't handle. What do you get if you run the command fastboot --version? The latest is 28.0.1
sliding_billy said:
Have you tried to get into stock recovery from fastboot? I don't see a screen grab of that. Use key combo to get to bootloader, and then select recovery from fastboot to get to the no command screen and power +volume down to get to recovery options.
Also, did you get a prompt that unlocking the BL would results in a factory reset and did you do one?
Click to expand...
Click to collapse
Yes tried all that. When I chood recovery Mode from the menu I get a black screen. A reboot via fastboot into recovery is not possible afaik.
Code:
fastboot --version
fastboot version 1:7.0.0+r33-2
This is the latest version according to Ubuntu.
IronDude said:
Yes tried all that. When I chood recovery Mode from the menu I get a black screen. A reboot via fastboot into recovery is not possible afaik.
Code:
fastboot --version
fastboot version 1:7.0.0+r33-2
This is the latest version according to Ubuntu.
Click to expand...
Click to collapse
All right, looks like Linux is a little different than windows. See if these help, https://developer.android.com/studio/releases/platform-tools.
jd1639 said:
All right, looks like Linux is a little different than windows. See if these help, https://developer.android.com/studio/releases/platform-tools.
Click to expand...
Click to collapse
Same results
IronDude said:
So somehow I seemed to have bricked my Pixel 3 XL. I've bootet into fastboot and ahve enabled OEM unlock beforehand in the dev options. Also the screen tells me "Device state: unlocked" after I ran
Code:
fastboot flashing unlock
.
But now no matter what I do I end up with a black screen. Can't boot into my OS and can't boot into recovery. I also can't flash a factory ROM or temp boot into TWRP. I also can't flash anything.
Code:
fastboot boot twrp-3.2.3-4-crosshatch.img
downloading 'boot.img'...
OKAY [ 0.396s]
booting...
FAILED (remote: Error calling AvbLoadAndVerifyBootImages Load Error)
finished. total time: 0.765s
Code:
fastboot flash recovery twrp-3.2.3-4-crosshatch.img
target reported max download size of 268435456 bytes
sending 'recovery' (65536 KB)...
OKAY [ 0.392s]
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
finished. total time: 0.758s
Code:
fastboot flashing unlock
...
(bootloader) Device already unlocked
OKAY [ 0.318s]
finished. total time: 0.318s
Click to expand...
Click to collapse
IronDude said:
Yes tried all that. When I chood recovery Mode from the menu I get a black screen. A reboot via fastboot into recovery is not possible afaik.
Code:
fastboot --version
fastboot version 1:7.0.0+r33-2
This is the latest version according to Ubuntu.
Click to expand...
Click to collapse
You are right about recovery>fastboot. That is why I "deleted" my comment. Maybe starting back over might help. Were you running BL unlocked already? Did you have TWRP installed? Had you been using the same computer /cable/port to execute commands before?
IronDude said:
Same results
Click to expand...
Click to collapse
Try flashing the factory image again. Just use the flash all .sh file.
jd1639 said:
Try flashing the factory image again. Just use the flash all .sh file.
Click to expand...
Click to collapse
Doesn't work:
Code:
./flash-all.sh
fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html
Code:
fastboot --version
fastboot version 28.0.1-4986621
Installed as /usr/local/sbin/platform-tools/fastboot
Ok the flash all is just broken but it can be forced to do its job simply by deleting the following lines:
Code:
#if ! grep -q partition-exists $(which fastboot); then
# echo "fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html"
# exit 1
#fi
I didn't delete them but just made them a comment. Then it worked.
IronDude said:
Ok the flash all is just broken but it can be forced to do its job simply by deleting the following lines:
Code:
#if ! grep -q partition-exists $(which fastboot); then
# echo "fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html"
# exit 1
#fi
I didn't delete them but just made them a comment. Then it worked.
Click to expand...
Click to collapse
Glad it worked out.
sliding_billy said:
Glad it worked out.
Click to expand...
Click to collapse
Me too mate! Was quite a heart attack moment.
IronDude said:
Me too mate! Was quite a heart attack moment.
Click to expand...
Click to collapse
Sounds good, glad you got it working again!