I have been trying to flash Clockwork Mod Recovery through fastboot, but it's not working. I boot into the bootloader (Power + Vol Dwn), and then into the second bootloader menu (Vol Dwn instead of Vol Up when prompted to go into recovery). When I get the 3 icons (Android Cold Boot, Fastboot USB Protocol, Wipe), I select Fastboot, and the tab displays "Starting Fastboot USB Download Protocol" but nothing happens from here. Is there a problem with the bootloader? Is there a way to replace the bootloader or the fastboot protocol?
gaxiolafm said:
I have been trying to flash Clockwork Mod Recovery through fastboot, but it's not working. I boot into the bootloader (Power + Vol Dwn), and then into the second bootloader menu (Vol Dwn instead of Vol Up when prompted to go into recovery). When I get the 3 icons (Android Cold Boot, Fastboot USB Protocol, Wipe), I select Fastboot, and the tab displays "Starting Fastboot USB Download Protocol" but nothing happens from here. Is there a problem with the bootloader? Is there a way to replace the bootloader or the fastboot protocol?
Click to expand...
Click to collapse
It was saying the same for me too,but just go ahead and flash...it will work just fine.
Pretoriano80 said:
It was saying the same for me too,but just go ahead and flash...it will work just fine.
Click to expand...
Click to collapse
I've tried like 10 times, twice I left it plugged in for about 4 hours, and nothing flashed. When I put "fastboot -i...." in the command prompt, I get "<waiting for device>" and nothing happens, and I can't type anything else.
gaxiolafm said:
I've tried like 10 times, twice I left it plugged in for about 4 hours, and nothing flashed. When I put "fastboot -i...." in the command prompt, I get "<waiting for device>" and nothing happens, and I can't type anything else.
Click to expand...
Click to collapse
Oh,check if the drivers are installed corectly.Some users reported the same issue like yours in the CWM recovery thread and some of them managed to fix it,have a look in that thread.
Pretoriano80 said:
Oh,check if the drivers are installed corectly.Some users reported the same issue like yours in the CWM recovery thread and some of them managed to fix it,have a look in that thread.
Click to expand...
Click to collapse
I've tried everything in that thread. The command window still hangs at <waiting for device>
I downloaded drivers from 4 different places, still nothing. I just flashed the .30 update downloaded directly from Asus, and ran the Debugfs root method again, still nothing. At least now I don't have TWRP! I will just wait until there is another method for flashing CWM, since I'm not seeing any official ROMs I want to flash at the time, anyway.
Thanks for taking the time to reply.
I have also been trying to flash CWM as a custom recovery on my TF700t. I have never done this before so please bear with me. I unlocked my device, turned on usb debugging, plugged it into the computer, on the computer I have fastboot installed and I have 6.0.4.7-NonTouch.img in the fastboot folder. I held down power and volume down until I saw RCK, Android, Wipe Data, and in the top left in tiny print it says starting fastboot USB download protocol. I then opened my command prompt and typed in "cd C:/Fastboot" and it brought up fastboot but when I type "Fastboot devices" to check if I am connected it does not give my serial number but it also does not say device not found. when I check my computers devices it says that I have an unspecified device named fastboot connected with all the drivers up to date. And so I typed in "fastboot -i 0x0B05 flash recovery 6.0.4.7-NonTouch.img" and it says it is sending "Recovery" eleven thousand ish KB but it never actually finishes. Am I doing something wrong that it is not recognizing my device properly? Please Help. Thanks in advance.
Titanium318 said:
I have also been trying to flash CWM as a custom recovery on my TF700t. I have never done this before so please bear with me. I unlocked my device, turned on usb debugging, plugged it into the computer, on the computer I have fastboot installed and I have 6.0.4.7-NonTouch.img in the fastboot folder. I held down power and volume down until I saw RCK, Android, Wipe Data, and in the top left in tiny print it says starting fastboot USB download protocol. I then opened my command prompt and typed in "cd C:/Fastboot" and it brought up fastboot but when I type "Fastboot devices" to check if I am connected it does not give my serial number but it also does not say device not found. when I check my computers devices it says that I have an unspecified device named fastboot connected with all the drivers up to date. And so I typed in "fastboot -i 0x0B05 flash recovery 6.0.4.7-NonTouch.img" and it says it is sending "Recovery" eleven thousand ish KB but it never actually finishes. Am I doing something wrong that it is not recognizing my device properly? Please Help. Thanks in advance.
Click to expand...
Click to collapse
Sounds like you don't have the right drivers installed on your PC. With it connected to the PC in fastboot open your device manager - what does it say - any transformer or adb devices with yellow question marks?
sbdags said:
Sounds like you don't have the right drivers installed on your PC. With it connected to the PC in fastboot open your device manager - what does it say - any transformer or adb devices with yellow question marks?
Click to expand...
Click to collapse
I re installed fastboot and it recognized my device. I then typed"fastboot -i 0x0b05 flash recovery 6.0.4.7-NonTouch.img" it said "sending 'recovery' (11796 KB)..." then "OKAY [3.523s]" then "writing 'recovery'..." then "OKAY [2.493s]" then "finished. Total time: 6.016s" I then typed "fastboot -i 0x0b05 reboot" and it said "rebooting..." then "finished. total time: 0.548s" When it said this my tablet did not reboot it froze (instead of a green flashing square around RCK it just showed a solid green square) so eventually I just held down the power button till it restarted and booted into fastboot then selected RCK. it showed a little android with his front open and a spinning triangle and said updating then it showed the android flat on his back said error and a triangle with an exclamation point inside. Should I retry sending the recovery?
---------- Post added at 09:25 PM ---------- Previous post was at 09:12 PM ----------
Titanium318 said:
I re installed fastboot and it recognized my device. I then typed"fastboot -i 0x0b05 flash recovery 6.0.4.7-NonTouch.img" it said "sending 'recovery' (11796 KB)..." then "OKAY [3.523s]" then "writing 'recovery'..." then "OKAY [2.493s]" then "finished. Total time: 6.016s" I then typed "fastboot -i 0x0b05 reboot" and it said "rebooting..." then "finished. total time: 0.548s" When it said this my tablet did not reboot it froze (instead of a green flashing square around RCK it just showed a solid green square) so eventually I just held down the power button till it restarted and booted into fastboot then selected RCK. it showed a little android with his front open and a spinning triangle and said updating then it showed the android flat on his back said error and a triangle with an exclamation point inside. Should I retry sending the recovery?
Click to expand...
Click to collapse
I believe its the original cable but I bought my tablet used. I double checked all my connections. And I used a different port. After trying again I realized that the tablet is actually freezing when I send the recovery before I even try to reboot. Do I need to root my device or is it possible to have a custom recovery unrooted?
Titanium318 said:
I re installed fastboot and it recognized my device. I then typed"fastboot -i 0x0b05 flash recovery 6.0.4.7-NonTouch.img" it said "sending 'recovery' (11796 KB)..." then "OKAY [3.523s]" then "writing 'recovery'..." then "OKAY [2.493s]" then "finished. Total time: 6.016s" I then typed "fastboot -i 0x0b05 reboot" and it said "rebooting..." then "finished. total time: 0.548s" When it said this my tablet did not reboot it froze (instead of a green flashing square around RCK it just showed a solid green square) so eventually I just held down the power button till it restarted and booted into fastboot then selected RCK. it showed a little android with his front open and a spinning triangle and said updating then it showed the android flat on his back said error and a triangle with an exclamation point inside. Should I retry sending the recovery?
---------- Post added at 09:25 PM ---------- Previous post was at 09:12 PM ----------
I believe its the original cable but I bought my tablet used. I double checked all my connections. And I used a different port. After trying again I realized that the tablet is actually freezing when I send the recovery before I even try to reboot. Do I need to root my device or is it possible to have a custom recovery unrooted?
Click to expand...
Click to collapse
Rooting won't help here. You have unlocked it first right?
sbdags said:
Rooting won't help here. You have unlocked it first right?
Click to expand...
Click to collapse
Yes I unlocked it using the asus unlocker tool
Titanium318 said:
Yes I unlocked it using the asus unlocker tool
Click to expand...
Click to collapse
I tried a touch version and also a flashable zip both locked up my tablet the same as before. While my tablet is frozen after attempting to send the recovery I re-entered fastboot devices and it replied "????????????? fastboot" What does this mean?
Titanium318 said:
I re installed fastboot and it recognized my device. I then typed"fastboot -i 0x0b05 flash recovery 6.0.4.7-NonTouch.img" it said "sending 'recovery' (11796 KB)..."
Click to expand...
Click to collapse
11.7 MB? Where did you get this recovery?
_that said:
11.7 MB? Where did you get this recovery?
Click to expand...
Click to collapse
This is where I downloaded CWM: http://d-h.st/YLd. So I switched and tried TWRP and it sent to my device and it did not freeze this time. It showed a blue loading bar at the bottom. I rebooted and opened RCK and TWRP opened successfully. I then Told my system to backup to my removable SD card. After it finished I tapped the reboot system button that came up. I opted not to root my device by installing superSU. I then downloaded Cromi-x to my tablet from here: http://forum.xda-developers.com/showthread.php?t=2425383 choosing the deodex option. Ithen followed the rest of the instructions and everything works great Thank you so much for your help!
Titanium318 said:
This is where I downloaded CWM: http://d-h.st/YLd.
Click to expand...
Click to collapse
Did you really expect a recovery for the Nexus 5 to run on the TF700?
Flashing stuff for different devices can just not work, as in your case, or it can turn your tablet into an expensive paperweight. Consider yourself lucky.
Related
I try this -> [ROM]ASU-JellyBean-Hydro 1.4.6-(8/29) Project melted butter smooooth
I have problem.
I use "COMING FROM ICS BOOTLOADER OR MY PREVIOUS ROM "
All ok, and when call this in cmd "fastboot -i 0x0b05 flash recovery"
get error "error: neither -p product specified nor ANDROID_PRODUCT_OUT set"
And i can't go to CWM, it show andoid with !
Then i use "fastboot -i 0x0B05 flash recovery twrp.blob"
Now only snow ASUS logo and i cant use power + volume down. Only show assus logo. I cant reboot.
Please Help
hi !
no fastboot mod ?
when you plug your tablet on usb, does your pc recognize ?
Hi,
Unfortunately not. Nothing happens. Just asus logo. After a long hold Power button, the screen goes off and then after 10 seconds the logo appears without pressing power button.
So logo stand until the battery runs out.
Is there any way to go back to ICS?
Image is in attachment.
Thanks in advance.
I have the same problem and I found any solution at his time . I hope someone can help us
Did you by any chance try to wipe the data in the bootloader menu?
We haven't any access to bootloader menu
I tried wipe the data, since I did not get into the cold boot (power + volume).
So, this is happening to me since I did wipe the data.
All the time is asus logo, and so until the battery died.
When recharge the battery, all the same thing happening.
EDIT:
I've tried various combinations of buttons. I just noticed that when you hold all three buttons at the same time (vol up, vol down and power), windows show "Unknown device".
It also happened to me when I had problems with the drivers. I guess I'm close decision. Are they now need special drivers for this?
I successfully installed the driver.
As you can see in the picture.
The devices is "Android ADB Interface"
But when I run the following command "fastboot -i 0x0B05 flash recovery twrp.blob" just standing "< waiting for device >" .
To do this -> hold all three buttons at the same time (vol up, vol down and power).
Does anyone know what to do next?
Regards.
I dont think your properly connected. Try reinstalling drivers and check to see if your connected by "adp devices" or "fastboot devices".
Sent from my VS840 4G using xda premium
I had similiar issue, when battery died i recharged and got back into fastboot. Do uhave fastboot option at all? Try a differebpnt computer ive screwed up my usb on 1 device before. Had to recover computer to get access to device again.
Sent from unbricked tf300t.
My mistake,
It is the APX driver for NvFlash, not for fastboot.
The problem is that it has not yet appeared NvFlash for tf300.
Nothing else left but to wait for it to appear.
akicay said:
I successfully installed the driver.
As you can see in the picture.
The devices is "Android ADB Interface"
But when I run the following command "fastboot -i 0x0B05 flash recovery twrp.blob" just standing "< waiting for device >" .
To do this -> hold all three buttons at the same time (vol up, vol down and power).
Does anyone know what to do next?
Regards.
Click to expand...
Click to collapse
you almost have it right. the proper command is (fastboot -i 0x0B05 flash recovery recovery.img ) without the parentheses. check out AllAboutAndroid's video on how to do this just use whatever recovery you want here is the link http://www.youtube.com/watch?feature=player_embedded&v=zSTf6ZY4NGo i hope this helps you guys out
p.s. if it works please do not forget to thank him
hey guys i had a similar problem and this thread tells you how i fixed it
http://forum.xda-developers.com/showthread.php?t=1857719
robgee789 said:
hey guys i had a similar problem and this thread tells you how i fixed it
http://forum.xda-developers.com/showthread.php?t=1857719
Click to expand...
Click to collapse
We don't have fastboot. We are in APX mode. We need an NvFlash solution.
sorry mate my mistake (that will teach me to read while half asleep lol)
Happened to me too. I'm hoping that ASUS will fix it for a reasonable price. Otherwise I'm just going to get a Nexus 7.
Hello.
Earlier today I wanted to try a new JB rom to replace ICS so I transfered it into SD card and tried to reboot into recovery.
Instead of getting to recovery, I got stuck in fastboot mode, so I'm assuming recovery has been damaged.
After a whole afternoon of researching this forum I tried for several times this tutorial in order to install a recovery and afterwards a ROM (http://forum.xda-developers.com/showthread.php?t=1088046) and similar ones in both Mac OS X and Windows 7 (tried both USB 2.0 and USB 3.0 so its not a problem from USB) and I didn't succeed at all.
When I am using Windows 7, when I use "fastboot erase recovery", I keep receiving this message "waiting device". If I write "fastboot devices", I don't get results.
When using Mac OS X, I can get via command line to the folder "platform-tools" where fastboot is located but if I write "fastboot erase recovery" or something, it says "command not found". I've read it could be because I have to set fastboot as an environmental variable, but I having trouble setting it (Mac OS Lion).
Thank you so much for reading. Please help me!!! Any clues would be really appreciated!
-----
UPDATE: I finally managed to communicate with the device.
I used the following commands from this tutorial http://androidforums.com/optimus-m-all-things-root/382525-guide-get-out-fastboot-mode-2.html
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot flash recovery
The problem is, now I'm stuck at LG Logo, can't access fastboot... Please help, I think it's even worse now.
boot rom, pull out battery and boot normal, it does or not? if it does use terminal emulator or adb push to install custom recovery, adb will work in fastboot if you had checked android debugging
http://forum.xda-developers.com/showthread.php?t=1007244
http://forum.xda-developers.com/showthread.php?t=1146566
grigtm said:
boot rom, pull out battery and boot normal, it does or not? if it does use terminal emulator or adb push to install custom recovery, adb will work in fastboot if you had checked android debugging
http://forum.xda-developers.com/showthread.php?t=1007244
http://forum.xda-developers.com/showthread.php?t=1146566
Click to expand...
Click to collapse
I don't understand what you mean by boot rom. Every time I turn on the phone, (normal or as POWER+HOME+VOL DOWN) it goes into fastboot. When I pull out the battery, and power again it goes again into fastboot...
techdani said:
I don't understand what you mean by boot rom. Every time I turn on the phone, (normal or as POWER+HOME+VOL DOWN) it goes into fastboot. When I pull out the battery, and power again it goes again into fastboot...
Click to expand...
Click to collapse
ok, read here http://forum.xda-developers.com/showthread.php?t=1088046 do exactly what says in this thread
Hi Guys, newbie here.
After installing a custom rom on my desire s a while back I have been edging towards doing the same on my Huawei ascend mate.
I have read the excelent posts in the developer forum but was not allowed to post there.
I have tried to flash twrp from joe.stones thread but maybe using a recovery installer from within android was not too smart.
My mate is now in a boot loop.
I have tried to get access using fastboot on linux but whatever I try, it keeps "waiting for device".
I've tried using power+volume up, power+volume up and volume down, tried the same buttons with usb attached and with an UPDATE.APP(both 221 and the 907 version) in dload on the sdcard
I have googled so much my head starts to spin...
Is there anything I can try?
partial succes, there is some communication!
I missed this thread:
http://forum.xda-developers.com/showthread.php?t=2682979
When passing a command like "fastboot flash recovery recovery.img" as root in terminal I get <waiting for device>
- Then connect via usb
- I/you then have to hold volume DOWN+ power to get a responce and I did!
Still not booting up but very nice to have the phone talking again!
Now trying some other fastboot stuff, but very gently....!
Done!
SvenHee said:
I missed this thread:
http://forum.xda-developers.com/showthread.php?t=2682979
When passing a command like "fastboot flash recovery recovery.img" as root in terminal I get <waiting for device>
- Then connect via usb
- I/you then have to hold volume DOWN+ power to get a responce and I did!
Still not booting up but very nice to have the phone talking again!
Now trying some other fastboot stuff, but very gently....!
Click to expand...
Click to collapse
In above thread is mentioned that you can extract files, boot.img and recovery.img, from the original UPDATE.APP that was used on your phone, in my case 907.
After flashing as mentioned the phone booted up again without any change!
Note
I used xubuntu linux 14.04, adb and fastboot utilities can be installed from the software center. Phone drivers are either not needed or were included in the install.
I used the extractor tool mentioned in the thread above in a virtual machine to extract the files from the UPDATE.APP
Hello there. I am writing here because my tablet which i didn't use for a long long (lend it to my grandma) time caught my attention. I wanted to install some custom rom and recovery but when i go to bootloader, I can see 4 things to choose and when i choose RCK or USB the device stops working. Adb works perfectly fine but fastboot not at all. Im attaching photos of what it looks like and all system info You may need in order to help me. On boot logo it says that the device is unlocked.
Also, Happy Easter
Deviss said:
Hello there. I am writing here because my tablet which i didn't use for a long long (lend it to my grandma) time caught my attention. I wanted to install some custom rom and recovery but when i go to bootloader, I can see 4 things to choose and when i choose RCK or USB the device stops working. Adb works perfectly fine but fastboot not at all. Im attaching photos of what it looks like and all system info You may need in order to help me. On boot logo it says that the device is unlocked.
Also, Happy Easter
Click to expand...
Click to collapse
First of all you should get your tablet on the last Asus update on Android 4.2 Jell Bean. That means you must download the latest Asus firmware for TF 300T from here:
https://www.asus.com/Tablets/ASUS_Transformer_Pad_TF300T/HelpDesk_BIOS/
Generally you may install it manually. After download unzip the zip file once. Then copy the "blob" file into the intern memory of your tablet. After rebooting the device the firmware is gonna to being installed automatically. This might be the first and most important step to prepare your device for flashing a custom rom of your choice.
Thanks for response,but after rebooting the device with blob file inserted, system launched normally and no updates procceded :/
Edit: now that I think of that, it looks like i don't have recovery because when i enter it from bootloader all i see is red triangle with "dead robot"
Deviss said:
Thanks for response,but after rebooting the device with blob file inserted, system launched normally and no updates procceded :/
Click to expand...
Click to collapse
Go ahead and try to flash the blob file.
If you don't have, you need „Minimal ADB and Fastboot“, download it from the Internet. The USB driver must be installed on your PC.
Install "Minimal ADB and Fastboot". Then put the blob file in your fastboot folder. Open cmd on your PC as administrator and type: "-i 0x0B05 flash staging blob" without " ".
Let it run. It seems that nothing happens. The whole thing can take up to 20 Minutes, so just stay calm and wait till it’s finished.
Well that's not gonna happen since as i stated in the topic i don't have access to the fastboot option(USB Icon in bootloader). when i pick the option from bootloader it just freezes and and stays like that frever untill i manually pinch the reset button with a needle, also the device is not listed in the command "fastboot devices". I will try running fastboot flash overnight, maybe then it will work...
Deviss said:
Well that's not gonna happen since as i stated in the topic i don't have access to the fastboot option(USB Icon in bootloader). when i pick the option from bootloader it just freezes and and stays like that frever untill i manually pinch the reset button with a needle, also the device is not listed in the command "fastboot devices". I will try running fastboot flash overnight, maybe then it will work...
Click to expand...
Click to collapse
I'm sorry, but I cannot understand what you are doing with the icons.
When you start your device with "power on" and "volume down" together you will reach the fastboot modus automatically shown at your third screenshot. That's it!
There is no need to touch any icon. Keep in mind never ever use the wipe icon. In that case your device gets bricked harshly.
Sorry, can not find any threads her on this
New Oukitel WP2 Android 8
Unlocked bootloader using ADB
ran "fastboot flash recovery WP2.img" and computer said finished
'phone said OK!
Tried "fastboot recovery" BUT all the 'phone will display is ==> fastboot mode in micro writing bottome left of screen
Tried volume up/power - nothing volume down/power - after warning about unlocked bootloader
bot into STANDARD Android 8 boot menu.
Having unlocked many Samsung 'phones, this is confusing me!
Also, after this how do you actually root the 'phone (or is twrp the root kit) as super SU reports
unrooted telephone.
Any clues gratefully accepted
Thanks
John
JR44 said:
Sorry, can not find any threads her on this
New Oukitel WP2 Android 8
Unlocked bootloader using ADB
ran "fastboot flash recovery WP2.img" and computer said finished
'phone said OK!
Tried "fastboot recovery" BUT all the 'phone will display is ==> fastboot mode in micro writing bottome left of screen
Tried volume up/power - nothing volume down/power - after warning about unlocked bootloader
bot into STANDARD Android 8 boot menu.
Having unlocked many Samsung 'phones, this is confusing me!
Also, after this how do you actually root the 'phone (or is twrp the root kit) as super SU reports
unrooted telephone.
Any clues gratefully accepted
Thanks
John
Click to expand...
Click to collapse
After fastboot flashing TWRP, type the command below.
adb reboot recovery
Sent from my SM-S767VL using Tapatalk
Thanks for reply but ONLY boots into the stock android 8 recovery and will not boot into twrp
tried various methods and each time adp says flashed recovery (tried it with different names recovery.img twrp.img etc)
and shows data transferred on 'phone screen.
BUT your suggestion and all those on the various websites but will still not boot into the custome recovery
and although I am used to working on Samsung 'phones, this one beats me! Eveb fulll factory reset 3 times!
TWRP is recovery-20181231-0237.img from multiple sites.
I do not know how to find if the recovery has actually been installed or something is stopping it running.
Just tried again in case:-
ANDROID RECOVERY
OUKITEL /WP2/WP2
8.0.0/o00623/1532584305
user/release-keys
use vol.....
hen usual list+-
reboot system now
reboot to bootloader
etc etc
no TWRP
'Phone does show "strange condition - unlocked bootloader - device can not be trusted" on each boot,
so everything else seems fine.
Spent 5 hours on this! Was going to use super su but could use magisk instead IF I can get to the
recovery stage!
rgds
JR44 said:
Sorry, can not find any threads her on this
New Oukitel WP2 Android 8
Unlocked bootloader using ADB
ran "fastboot flash recovery WP2.img" and computer said finished
'phone said OK!
Tried "fastboot recovery" BUT all the 'phone will display is ==> fastboot mode in micro writing bottome left of screen
Tried volume up/power - nothing volume down/power - after warning about unlocked bootloader
bot into STANDARD Android 8 boot menu.
Having unlocked many Samsung 'phones, this is confusing me!
Also, after this how do you actually root the 'phone (or is twrp the root kit) as super SU reports
unrooted telephone.
Any clues gratefully accepted
Thanks
John
Click to expand...
Click to collapse
JR44 said:
Thanks for reply but ONLY boots into the stock android 8 recovery and will not boot into twrp
tried various methods and each time adp says flashed recovery (tried it with different names recovery.img twrp.img etc)
and shows data transferred on 'phone screen.
BUT your suggestion and all those on the various websites but will still not boot into the custome recovery
and although I am used to working on Samsung 'phones, this one beats me! Eveb fulll factory reset 3 times!
TWRP is recovery-20181231-0237.img from multiple sites.
I do not know how to find if the recovery has actually been installed or something is stopping it running.
Just tried again in case:-
ANDROID RECOVERY
OUKITEL /WP2/WP2
8.0.0/o00623/1532584305
user/release-keys
use vol.....
hen usual list+-
reboot system now
reboot to bootloader
etc etc
no TWRP
'Phone does show "strange condition - unlocked bootloader - device can not be trusted" on each boot,
so everything else seems fine.
Spent 5 hours on this! Was going to use super su but could use magisk instead IF I can get to the
recovery stage!
rgds
Click to expand...
Click to collapse
After flashing TWRP, you can't let the device boot to any other mode, you have to boot directly to recovery. If you allow the device to boot into any mode other than recovery, it will revert back to stock recovery. The only way to keep TWRP is to boot directly into TWRP immediately after flashing.
Try this, flash the TWRP file using the fastboot flash recovery (name of file) command. Then, after it flashes, try using this command:
fastboot boot recovery (name of your specific file)
This may allow you to boot into TWRP and keep TWRP recovery so that you can boot into it at any time after that.
Sent from my SM-S767VL using Tapatalk
Thanks for reply but does not work...
WP2 has already had bootloader unlocked developer options and adb commands, including an automatic wipe of 'phone.
Then without touching anything else, the follwoing have been entered from a clean boot of 'phone and Win7. twrp.img file is named "recovery.img" in same directory as adb etc (C:\ for testing)
twrp file is "recovery.img" in same directory as adb etc (C:\ for testing)
twrp file is "recovery.img" in same directory as adb etc (C:\ for testing)
issue command> adb reboot bootloader
computer response OK
'phone shows "fastboot" in miniscule text
issue command> "fastboot flash recovery recovery.img"
computer says> "target reported max download size 134217728 bytes"
then
"sending 'recovery' (15010kb)"
then
"OKAY [0.65 seconds}"
then
"writing 'recovery'..."
then
"finished. total time 1.06 s"
'phone says "transmission ok then a checksum"
after a wait
issue command> "fastboot boot recovery.img"
computer says "downloading 'boot.img'"
then
"OKAY 0.64 s"
then
"booting....."
then OKAY 0.47s"
then
"finished"
'Phone boots into normal logo then to a NORMAL STARTUP - NOT to any bootloader
argh!!!
adb devices returnes OUKIWP2000015176
Any clues as to what is wrong or what I am missing!
cheers
John
UK
JR44 said:
Thanks for reply but does not work...
WP2 has already had bootloader unlocked developer options and adb commands, including an automatic wipe of 'phone.
Then without touching anything else, the follwoing have been entered from a clean boot of 'phone and Win7. twrp.img file is named "recovery.img" in same directory as adb etc (C:\ for testing)
twrp file is "recovery.img" in same directory as adb etc (C:\ for testing)
twrp file is "recovery.img" in same directory as adb etc (C:\ for testing)
issue command> adb reboot bootloader
computer response OK
'phone shows "fastboot" in miniscule text
issue command> "fastboot flash recovery recovery.img"
computer says> "target reported max download size 134217728 bytes"
then
"sending 'recovery' (15010kb)"
then
"OKAY [0.65 seconds}"
then
"writing 'recovery'..."
then
"finished. total time 1.06 s"
'phone says "transmission ok then a checksum"
after a wait
issue command> "fastboot boot recovery.img"
computer says "downloading 'boot.img'"
then
"OKAY 0.64 s"
then
"booting....."
then OKAY 0.47s"
then
"finished"
'Phone boots into normal logo then to a NORMAL STARTUP - NOT to any bootloader
argh!!!
adb devices returnes OUKIWP2000015176
Any clues as to what is wrong or what I am missing!
cheers
John
UK
Click to expand...
Click to collapse
I don't know, I'll keep looking, if I find anything useful, I'll post it.
Sent from my SM-S767VL using Tapatalk
Still not working
If anyone else is reading this post I am still unable to flash the twrp recovery
downloaded from http://www.mediafire.com/file/cp6cw164fse2bpa/Oukitel_WP2_twrp.rar/file
Every time I try the flash commands it looks like it has sent to device - only takes 0.5 seconds and
'phone says received.
Unable to boot into recovery twrp - always comes back with stock android 8 recovery OR an error
message about can not open.
Any more suggestions please as annoying! OR is there adifferent twrp recovery out there I can
]use with Odin? or Magiisk?
Many thanks
john
JR44 said:
If anyone else is reading this post I am still unable to flash the twrp recovery
downloaded from http://www.mediafire.com/file/cp6cw164fse2bpa/Oukitel_WP2_twrp.rar/file
Every time I try the flash commands it looks like it has sent to device - only takes 0.5 seconds and
'phone says received.
Unable to boot into recovery twrp - always comes back with stock android 8 recovery OR an error
message about can not open.
Any more suggestions please as annoying! OR is there adifferent twrp recovery out there I can
]use with Odin? or Magiisk?
Many thanks
john
Click to expand...
Click to collapse
Odin is for Samsung devices only. You can't use Odin on your device.
Sent from my SM-S767VL using Tapatalk