Related
this is what I had to do on Linux Mint 12 but should work with most ubuntu based distros
1: download twrp
2: if you dont already have it then you need to download the linux fastboot binary, extract the .zip and place the extracted file in your androidsdk/platform-tools directory
2: place the file you downloaded from TWRP into your androidsdk/platform-tools directory
3: connect your fire to your computer and disable mass storage mode
4: open a terminal and cd to your androidsdk/platform-tools directory and enter the following commands pressing enter after each line
Code:
./adb shell
su
idme bootmode 4002
then back out of the adb shell by
Code:
exit
exit
then
Code:
./adb reboot
after it reboots to the "Kindle Fire" boot screen its time to flash the recovery
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
once flashed and it installs and boots to the "firefirefire" screen (screen with the yellow sign and text that says "press power for recovery" you have to change the boot mode back out of fastboot
Code:
sudo ./fastboot oem idme bootmode 4000
sudo ./fastboot reboot
it should reboot to the "firefirefire" screen, to enter recovery press and hold the power button until it turns from green to orange then let go. You should boot into TWRP and be able to make your first backup.
from now on if you dont want to go into recovery then just let it sit and it will boot normally
Thanks to all the Teamwin members, agrabren for the port, pyrostic for testing, pokey9000 for the "FireFireFire" bootloader, and I am sure there are more but I dont know who you are so thank you.
if you can donate to these guys please do becuase without them we would just have an e-reader.
I am not responsable for any damage that YOU may cause buy following these directions.
not sure where i went wrong. i followed every step, it flashed, im stuck at the yellow triangle guessing im in fastboot.
i do fastboot oem bootmode 4000 and it gets stuck at waiting for devices.
issue the command with sudo
Nevermind, wasn't using ./ when I was issuing commands. As usual, need to pay better attention.
Thanks OP. Sweet.
My Fire got stuck at the splash screen after issuing the command idme bootmode 4002 and it won't load up. I can't get adb to recognize it anymore. Any advice?
abiezer said:
My Fire got stuck at the splash screen after issuing the command idme bootmode 4002 and it won't load up. I can't get adb to recognize it anymore. Any advice?
Click to expand...
Click to collapse
adb wont recogonize it after you change the boot mode thats where you issue the fastboot commands
smirkis said:
not sure where i went wrong. i followed every step, it flashed, im stuck at the yellow triangle guessing im in fastboot.
i do fastboot oem bootmode 4000 and it gets stuck at waiting for devices.
Click to expand...
Click to collapse
Download this file and place it in the folder your fastboot is located in: http://techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img
do the following
open a command window where fastboot is located:
Step 1:
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
if your window says "waiting for device" then reboot your device. if it boots into TWRP 2.0 then you are set move to Step 3. if it still says "waiting for device" close the window and then then open a command window where fastboot is located and do step 2.
Step 2:
Code:
fastboot -i 0x18d1 boot twrp-blaze-2.0.0RC0.img
if your window says "waiting for device" then reboot your device. if it boots into TWRP 2.0 then you are set move to Step 3. If it is still not doing anything, this is where my knowledge is no good anymore, and you should consult someone else.
TWRP should be showing on your screen. Close your old fastboot window and open a new command window where ADB is located. Proceed to Step 3.
Step 3:
Code:
adb shell
idme bootmode 4000
reboot
your device should reboot, and if you had problems with Step 3 try the following from your ADB command window
Code:
su
adb kill-server
adb start-server
adb devices
your device should be listed. If so try Step 3 again.
hope this helps or at least puts you in the right direction.
After executing fastboot, I get the following and the device stays on "Kindle Fire" splash screen. Any ideas?
Code:
$ ./fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
creating boot image...
creating boot image - 10240 bytes
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.006s]
booting...
OKAY [ 0.003s]
finished. total time: 0.009s
craftyguy said:
After executing fastboot, I get the following and the device stays on "Kindle Fire" splash screen. Any ideas?
Code:
$ ./fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
creating boot image...
creating boot image - 10240 bytes
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.006s]
booting...
OKAY [ 0.003s]
finished. total time: 0.009s
Click to expand...
Click to collapse
Sounds like you are in fastboot, but I would expect to see the yellow triangle logo and not the Kindle Fire one. Anyway, try to see if running the following works:
Code:
./fastboot oem idme bootmode 4000
./fastboot reboot
sl0ttedpig said:
Sounds like you are in fastboot, but I would expect to see the yellow triangle logo and not the Kindle Fire one. Anyway, try to see if running the following works:
Code:
./fastboot oem idme bootmode 4000
./fastboot reboot
Click to expand...
Click to collapse
Tried setting bootmode with fastboot, but it just sits there at "< waiting for device> ". Tried rebooting Kindle but fastboot is still hanging up there.
EDIT: Ok, had to pass "-i 0x1949" to fastboot. Got the device back, going to try it all over again
craftyguy said:
Tried setting bootmode with fastboot, but it just sits there at "< waiting for device> ". Tried rebooting Kindle but fastboot is still hanging up there.
Click to expand...
Click to collapse
what os is on ur computer? sounds like a driver issue.
Sent from my HTC Glacier using xda premium
smirkis said:
what os is on ur computer? sounds like a driver issue.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I'm on Fedora 16 x86_64. I did all of the adb interactions on a Windows 7 system, however it looks like adb isn't set up correctly on this Fedora box I'm on now. I have (what I think at least) the udev rules set for Kindle Fire. Looks like I have some more reading to do!
EDIT: adb up and running. For anyone who has this issue, add "0x1949" to ~/.android/adb_usb.ini, and restart adb!
---------- Post added at 12:15 PM ---------- Previous post was at 11:32 AM ----------
Alright, my week-old Kindle Fire does not agree with this procedure. The twrp image does not seem to be flashing at all (fastboot returns after .009s and device never reboots to recovery)
try rebooting manually n see if u get fastbot.
Sent from my HTC Glacier using xda premium
craftyguy said:
I'm on Fedora 16 x86_64. I did all of the adb interactions on a Windows 7 system, however it looks like adb isn't set up correctly on this Fedora box I'm on now. I have (what I think at least) the udev rules set for Kindle Fire. Looks like I have some more reading to do!
EDIT: adb up and running. For anyone who has this issue, add "0x1949" to ~/.android/adb_usb.ini, and restart adb!
---------- Post added at 12:15 PM ---------- Previous post was at 11:32 AM ----------
Alright, my week-old Kindle Fire does not agree with this procedure. The twrp image does not seem to be flashing at all (fastboot returns after .009s and device never reboots to recovery)
Click to expand...
Click to collapse
woot for fedora! anyway, i set things up via /etc/udev/rules.d/51-android.rules and at first I had this...
SUBSYSTEM=="usb", SYSFS{idVendor}=="1949", MODE="0666"
and everything was cool. but after flashing twrp, i noticed there was firefirefire 1.0 out where previously i had flashed .9 so i thought id update I went to update and after putting the device in fastboot mode, it rebooted to the bootloader where fastboot wasnt recognizing the device started digging around and found windows users having driver issues and thought to myself... we dont have drivers BUT we do have rules!! added this line to the udev rules
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
and everything working as it should again
I'm trying to change the kernel (with DooMKernel) on my Arc.
I installed the ADB drivers (at least I hope ), in fact, when I plug in my arc in my device manager I can read:
-Android phone
->Android ADB Interface
So, when i tryed with fastboot.exe -i 0x0fce getvar version command, it's ok, I get a response back.
With fastboot flash boot boot.img, I get the "waiting for device"
What's the problem??
try type fastboot flash boot boot.img
But that won't flash the kernel...
Sent from my LT15i using XDA Premium App
beranchoi said:
try type fastboot flash boot boot.img
Click to expand...
Click to collapse
I get the same result!!
Flo95 said:
But that won't flash the kernel...
Sent from my LT15i using XDA Premium App
Click to expand...
Click to collapse
Sorry... I'm confused
Fastboot boot boot boot.img just boots the kernel but doesn't flash it.
Sent from my iPad 2 using Tapatalk
Is your boot loader unlocked ??
Flo95 said:
Fastboot boot boot boot.img just boots the kernel but doesn't flash it.
Click to expand...
Click to collapse
So, what's right command??
KingWickedd said:
Is your boot loader unlocked ??
Click to expand...
Click to collapse
yes, it's!! In my phone, open the dialler and enter *#*#7378423#*#* to access the service menu, and he says bootloader unlocked!!
fastboot flash boot boot.img is right
Sent from my iPad 2 using Tapatalk
Flo95 said:
fastboot flash boot boot.img is right
Click to expand...
Click to collapse
Even with this command, the result is the same!!
ssl3vin said:
Even with this command, the result is the same!!
Click to expand...
Click to collapse
did you try
Code:
fastboot -i 0xfce flash boot boot.img
?
drcyber said:
did you try
Code:
fastboot -i 0xfce flash boot boot.img
?
Click to expand...
Click to collapse
THANKSSSSS
yes, it works!!
use this https://rs639l3.rapidshare.com/#!do...r|6525|R~3AB292D7A53EFF1EE7A8A05879380BA4|0|0.
All drivers is on this file .
extract file and open the file" fastboot_with_Android_USB_file" ,so press shift and clic right bouton from mouse on the file fastboot, in the menu shoose "open the window command here".
The sreen CMD automaticly is opening .so you can write fastboot flash boot boot.img.
Amivieu said:
use this https://rs639l3.rapidshare.com/#!do...r|6525|R~3AB292D7A53EFF1EE7A8A05879380BA4|0|0.
All drivers is on this file .
extract file and open the file" fastboot_with_Android_USB_file" ,so press shift and clic right bouton from mouse on the file fastboot, in the menu shoose "open the window command here".
The sreen CMD automaticly is opening .so you can write fastboot flash boot boot.img.
Click to expand...
Click to collapse
Sorry, but the DRIVERS ARE OK, my phone is recognized as ADB interface!!!
but when I enter with fastboot flash boot boot.img, he show the message "waiting for device".
Instead with the command fastboot -i 0xfce flash boot boot.img it's works perfectly
drcyber said:
did you try
Code:
fastboot -i 0xfce flash boot boot.img
?
Click to expand...
Click to collapse
What does the -i 0xfce do? Because it works!
Daanmannetje said:
What does the -i 0xfce do? Because it works!
Click to expand...
Click to collapse
how does it work,this is what i get when i copy-past that line:
"""C:\Documents and Settings\Dedaj\Desktop\Xperia Arc\Xperia Tools\fastboot\fastboo
t>fastboot -i 0xfce flash boot boot.img
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
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
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
C:\Documents and Settings\Dedaj\Desktop\Xperia Arc\Xperia Tools\fastboot\fastboo
t>""""
so what i'm doing wrong!
EDIT:
Fixed
I got the same problem. I'm using Windows 8 and I got "waiting for device" error. I tried to write "-i 0xfce" but it didn't work. How can I fix this ?
---------- Post added at 01:56 PM ---------- Previous post was at 01:54 PM ----------
And I also ran "cmd" as administrator but it did not work too.
im having the exact same problem
welocan said:
I got the same problem. I'm using Windows 8 and I got "waiting for device" error. I tried to write "-i 0xfce" but it didn't work. How can I fix this ?
---------- Post added at 01:56 PM ---------- Previous post was at 01:54 PM ----------
And I also ran "cmd" as administrator but it did not work too.
Click to expand...
Click to collapse
im having the exact same problem we should make this more big so everyone can see it
APPLEMYASS said:
we should make this more big so everyone can see it
Click to expand...
Click to collapse
Or just Google fastboot Windows 8 and do some reading.
Check this
When the command window opens type 'fastboot devices'
What happens? what do you get?
Make sure u hv enabled USB debugging from Settings-> Development.
Hit thanks if I helped u...
Sent from my Xperia Arc using xda app-developers app
This should work:
If you have fff installed:
Copy the tools folder from KFU to your local disk.
Now power off your Kindle Fire all the way.(all doing)
Then open command prompt and type:
cd c:\tools
fastboot
fastboot getvar store
(now you should see <waiting for device>)
Now power on your Kindle. Now in cmd it should say finished and the time it took.(wating for device..... naver finishe)
Now copy TWRP to your local disk
Then type:
fastboot flash recovery c:\openrecovery-twrp-blaze-2.2.0.img(openrecovery-twrp-blaze certainly in to tool,)
fastboot oem idme bootmode 4000
fastboot reboot
Now as it boots up use your power button to boot into recovery and it should boot into TWRP.
naver ending wating for device~~~~~~~~~~~
cd c:\tools(recovery certainly into c
fastboot
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
(driver re-installing many times ,certainly driver install,well showing driver numbers)
don`t end ,naver ending~~~~~~~~~~wating for device
i wanna be korean keyboard,not needs markeet
You just said something that might be your problem because of how different korean characters are in your alphabet maybe just simply changing your computers language to english to complete the process will help
hello everyone
My htc desire hd after a restore unsuccessful system got white screen with just the logo and no longer goes out from there. What to do?
thank you!
excuse my bad english
Your bootloader is stuck
how do I see if he is stuck or not?
is there any way to fix this?
Do you understand adb and fastboot commands? Did u try pulling battery, waiting then powering it on by holding power and volume down to boot to a menu screen?
---------- Post added at 07:55 PM ---------- Previous post was at 07:53 PM ----------
Is your device rooted?unlocked boot loader.. S off? Need more details. Do u have a custom recovery on it?
yes i can go
***UNLOCKED***
ACE PVT SHIP S-ON RL
HBOOT -2.00.029
Microp -0438
Radio - 26.14.04.28_M
eMMC-boot
Recovery?
yes I can still access recovery
i have the clockworkmod recovery v 5.8.0.0 installed in the phone
What ROM were u running when this issue started?
---------- Post added at 09:32 PM ---------- Previous post was at 09:30 PM ----------
You're using an old recovery of cwm. The newer cwm 6.0.4 is recommended. Install that recovery
marknoll said:
What ROM were u running when this issue started?
---------- Post added at 09:32 PM ---------- Previous post was at 09:30 PM ----------
You're using an old recovery of cwm. The newer cwm 6.0.4 is recommended. Install that recovery
Click to expand...
Click to collapse
how do I install cwm 6.0.4?
The ROM has ace_PAC_JB_4.2.2-v22.3.0_20130520-064722.zip
Download cwm 6.0.4 on cwm website...put that file in your fast boot folder...open a cmd prompt in that folder and type fastboot devices. See if PC sees it. A serial number should appear. That means fb recognizes your device. Then fastboot flash recovery "then the recovery name" hit enter. This must all be done on the boot loader screen.
---------- Post added at 10:24 PM ---------- Previous post was at 10:23 PM ----------
P.s. make sure that a ".zip" is at end of recovery name.
---------- Post added at 10:25 PM ---------- Previous post was at 10:24 PM ----------
When successfully flashing recovery, type fastboot reboot recovery. Should bring you there
marknoll said:
Download cwm 6.0.4 on cwm website...put that file in your fast boot folder...open a cmd prompt in that folder and type fastboot devices. See if PC sees it. A serial number should appear. That means fb recognizes your device. Then fastboot flash recovery "then the recovery name" hit enter. This must all be done on the boot loader screen.
---------- Post added at 10:24 PM ---------- Previous post was at 10:23 PM ----------
P.s. make sure that a ".zip" is at end of recovery name.
---------- Post added at 10:25 PM ---------- Previous post was at 10:24 PM ----------
When successfully flashing recovery, type fastboot reboot recovery. Should bring you there
Click to expand...
Click to collapse
cwm site does not have the 6.0.4 version for desire hd
sorry but I do not understand any of this
when I type fastboot devices nothing appears
Thats cuz u probably don't have fastboot drivers installed.
---------- Post added at 01:30 AM ---------- Previous post was at 01:26 AM ----------
https://www.clockworkmod.com/rommanager
marknoll said:
Thats cuz u probably don't have fastboot drivers installed.
---------- Post added at 01:30 AM ---------- Previous post was at 01:26 AM ----------
https://www.clockworkmod.com/rommanager
Click to expand...
Click to collapse
how do I install them?
excuse this inconvenience for you
Put your phone in bootloader mode then plug in PC, PC should automatically install them. If not, download min adb and fastboot program
---------- Post added at 11:58 AM ---------- Previous post was at 11:56 AM ----------
http://forum.xda-developers.com/showthread.php?t=2317790
---------- Post added at 12:07 PM ---------- Previous post was at 11:58 AM ----------
Sara Pinto said:
cwm site does not have the 6.0.4 version for desire hd
sorry but I do not understand any of this
when I type fastboot devices nothing appears
Click to expand...
Click to collapse
Sorry. I meant 5.8.1
---------- Post added at 12:11 PM ---------- Previous post was at 12:07 PM ----------
If the touch recovery doesn't work for ya,try the 5.0.2
marknoll said:
Put your phone in bootloader mode then plug in PC, PC should automatically install them. If not, download min adb and fastboot program
---------- Post added at 11:58 AM ---------- Previous post was at 11:56 AM ----------
http://forum.xda-developers.com/showthread.php?t=2317790
---------- Post added at 12:07 PM ---------- Previous post was at 11:58 AM ----------
Sorry. I meant 5.8.1
---------- Post added at 12:11 PM ---------- Previous post was at 12:07 PM ----------
If the touch recovery doesn't work for ya,try the 5.0.2
Click to expand...
Click to collapse
what am I doing wrong?
HT0CPRX08729 fastboot - This mean that my pc recognizes my phone?
C:\Users\Sara\Desktop\recovery-clockwork-touch-5.8.1.5-saga>c:\windows\system32\
cmd.exe
Microsoft Windows [Versão 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Todos os direitos reservados.
C:\Users\Sara\Desktop\recovery-clockwork-touch-5.8.1.5-saga>fastboot devices
HT0CPRX08729 fastboot
C:\Users\Sara\Desktop\recovery-clockwork-touch-5.8.1.5-saga>fastboot flash recov
ery recovery-clockwork-touch-5.8.1.5-saga
error: cannot load 'recovery-clockwork-touch-5.8.1.5-saga'
C:\Users\Sara\Desktop\recovery-clockwork-touch-5.8.1.5-saga>fastboot flash recov
ery recovery-clockwork-touch-5.8.1.5-saga.img
sending 'recovery' (3518 KB)... OKAY [ 0.657s]
writing 'recovery'... OKAY [ 0.520s]
finished. total time: 1.177s
C:\Users\Sara\Desktop\recovery-clockwork-touch-5.8.1.5-saga>fastboot reboot reco
very
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
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
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-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
-n <page size> specify the nand page size. default:
2048
C:\Users\Sara\Desktop\recovery-clockwork-touch-5.8.1.5-saga>
Yes. It sees your phone. Try the 5.0.2. Ur doing it right
marknoll said:
Yes. It sees your phone. Try the 5.0.2. Ur doing it right
Click to expand...
Click to collapse
Microsoft Windows [Versão 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Todos os direitos reservados.
C:\Program Files\Minimal ADB and Fastboot>fastboot devices
HT0CPRX08729 fastboot
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery-clock
work-touch-5.8.1.5-ace.img
sending 'recovery' (3554 KB)...
OKAY [ 0.602s]
writing 'recovery'...
OKAY [ 0.511s]
finished. total time: 1.117s
C:\Program Files\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.402s
C:\Program Files\Minimal ADB and Fastboot
I tried it but the phone continues with the white screen and the HTC logo and does not come from there
No. Flash the 5.0.2. Touch don't seem to work.
marknoll said:
No. Flash the 5.0.2. Touch don't seem to work.
Click to expand...
Click to collapse
Microsoft Windows [Versão 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Todos os direitos reservados.
C:\Program Files\Minimal ADB and Fastboot>fastboot devices
HT0CPRX08729 fastboot
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery-clock
work-5.0.2.0-ace.img
sending 'recovery' (3624 KB)...
OKAY [ 0.606s]
writing 'recovery'...
OKAY [ 0.537s]
finished. total time: 1.151s
C:\Program Files\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.401s
C:\Program Files\Minimal ADB and Fastboot>
My phone continues with the white screen and the HTC logo and does not come from there
U have to fastboot reboot recovery
---------- Post added at 04:36 PM ---------- Previous post was at 04:35 PM ----------
Doing that cmd just puts device in a loop
---------- Post added at 04:39 PM ---------- Previous post was at 04:36 PM ----------
OK. With phone powered down...hold power and volume down button til it boots to boot loader. Tell me what u see
hello everyone
My pixel 2xl just only boot on bootloader after erase system_a and bla bla. just follow instruction. but when flash the flash-all.bat seem like postive. but the result shown not a same baseband (something like that)
so now my phone only can open bootloader. if trying open recovery in bootloader it will repeat to bootloader back.
just hope someone can help me. my fault cause take it easy as like others smartphone to root.
maybe cause the erase system. all the partition is empty ?
this all quarantine fault :crying:
please helpppp
:crying::crying::crying::crying::crying::crying::crying::crying::crying:
syeikh52 said:
hello everyone
My pixel 2xl just only boot on bootloader after erase system_a and bla bla. just follow instruction. but when flash the flash-all.bat seem like postive. but the result shown not a same baseband (something like that)
so now my phone only can open bootloader. if trying open recovery in bootloader it will repeat to bootloader back.
just hope someone can help me. my fault cause take it easy as like others smartphone to root.
maybe cause the erase system. all the partition is empty ?
this all quarantine fault :crying:
please helpppp
:crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Why would you erase the system? Were you trying to flash another ROM or something?
---------- Post added at 11:05 AM ---------- Previous post was at 11:03 AM ----------
You'll most likely need to re-flash a stock image.
https://developers.google.com/android/images
Fastboot flash your bootloader, radio then vendor on both slots then try again.
Ragarianok said:
Why would you erase the system? Were you trying to flash another ROM or something?
---------- Post added at 11:05 AM ---------- Previous post was at 11:03 AM ----------
You'll most likely need to re-flash a stock image.
https://developers.google.com/android/images
Click to expand...
Click to collapse
hm. im just follow instruction from
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
everything okay but its failed in the step F
now it only can open bootloader.
and my bootloader version change from TMZ30 to TMZ10n
Edmontonchef said:
Fastboot flash your bootloader, radio then vendor on both slots then try again.
Click to expand...
Click to collapse
did you have the instruction or link ?
i will make the problem more hardly :crying::crying::crying:
syeikh52 said:
did you have the instruction or link ?
i will make the problem more hardly :crying::crying::crying:
Click to expand...
Click to collapse
Make sure adb and fastboot are installed
Download and extract taimen factory image
Double click to open
Extract the taimen folder found in the factory image. That has the vendor image
Open terminal and type adb devices to make sure you have adb connected. Boot to bootloader
Here's the commands, after the command hit space then drag and drop the image hit enter.
Fastboot flash bootloader_a (bootloader)
Reboot bootloader
Same command but with _b
Then radio and vendor same way rebooting bootloader after each flash
Now you can use that taimen folder you extracted. Drag and drop same as images
Fastboot update (taimen folder)
It'll take a few minutes to do it's thing
---------- Post added at 02:57 AM ---------- Previous post was at 02:53 AM ----------
ABC ezio has some better instructions
https://forum.xda-developers.com/cu...ive/rom-builders-collective-t2861778/page2324
Edmontonchef said:
Make sure adb and fastboot are installed
Download and extract taimen factory image
Double click to open
Extract the taimen folder found in the factory image. That has the vendor image
Open terminal and type adb devices to make sure you have adb connected. Boot to bootloader
Here's the commands, after the command hit space then drag and drop the image hit enter.
Fastboot flash bootloader_a (bootloader)
Reboot bootloader
Same command but with _b
Then radio and vendor same way rebooting bootloader after each flash
Now you can use that taimen folder you extracted. Drag and drop same as images
Fastboot update (taimen folder)
It'll take a few minutes to do it's thing
---------- Post added at 02:57 AM ---------- Previous post was at 02:53 AM ----------
ABC ezio has some better instructions
https://forum.xda-developers.com/cu...ive/rom-builders-collective-t2861778/page2324
Click to expand...
Click to collapse
already follow but failed
C:\Users\LEGION\Desktop\repair\taimen-opd1.170816.010>fastboot flash bootloader_a C:\Users\LEGION\Desktop\repair\taimen-opd1.170816.010\image-taimen-opd1.170816.010\vendor.img
Sending 'bootloader_a' (349408 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
:crying::crying::crying::crying::crying:
Sorry for slow replying.
btw before im using andriod 10. but im downloading a 8.0.0 (OPD1.170816.010, Sep 2017)
erkk
im using standard cmd. should i open as admin ?
Edmontonchef said:
Make sure adb and fastboot are installed
Download and extract taimen factory image
Double click to open
Extract the taimen folder found in the factory image. That has the vendor image
Open terminal and type adb devices to make sure you have adb connected. Boot to bootloader
Here's the commands, after the command hit space then drag and drop the image hit enter.
Fastboot flash bootloader_a (bootloader)
Reboot bootloader
Same command but with _b
Then radio and vendor same way rebooting bootloader after each flash
Now you can use that taimen folder you extracted. Drag and drop same as images
Fastboot update (taimen folder)
It'll take a few minutes to do it's thing
---------- Post added at 02:57 AM ---------- Previous post was at 02:53 AM ----------
ABC ezio has some better instructions
https://forum.xda-developers.com/cu...ive/rom-builders-collective-t2861778/page2324
Click to expand...
Click to collapse
Thanks bro idk why
but im just changing the port ti 2.0
before using C to C
then using C to A still problem
now using C to A but using usb hub because this LEGION gaming laptop All usb 3.0
:crying::crying::crying:
now just wanna try to install TWRP
Download twrp.IMG
Fastboot boot (twrp.img)
Go to settings and disable screen timeout and the swipe to install twrp app. Don't need it.
You can flash a stock ota on twrp.
Put whatever you need on a type c thumb drive (stock ota, twrp installer zip, roms) and mount it in twrp.
Just keep in mind if you are going backwards, you'll have to format data.