Excuse me for my bad English. I am new on this Forum. Please help me, I have a big problem!
I can’t use Fastboot command, because ewery time I got the „Waiting for devices” error message
1) I have a Motorola Moto G4 phone (XT 1622, athene)
2) This mobile are not rooted.
3) I want to unlock my bootloader, after this I want to install TWRP, and after this I van root my mobile, for install the custom Lineage OS.
4) On my phone I activated at the Developper Otions the USB debugging, and OEM Unlocking.
5) I connected my phone to my PC, I used first time Windows 10. On this system my Moto G4 are identified: Motorola ADB interface. No problem with identification, no any yelow exclamation matrk, no unidentified device!
6) I have installed the correct ADB and Fastboot driver v.1.4.3 (link is made from this site)
7) I have installed the Motorola driver from the official Motorola site.
8) All ADB command work fine, for example adb devices, adb reboot bootloader, etc.
9) But no fastboot command work, when I tested the fastboot devices, I got the „Waiting for devices”. Of corse befor this, I rebooted my phone in fastboot mode! If I use any fastboot command, I got this error message.
10) I try to use the excellent tools (thank you for this): Universal Fastboot & ADB tool, latest version, but the situation in this case is the same, „Waiting for devices”.
11) Of corse I rebooted the PC after instalation of the drivers, the fastboot.exe is in the right paths, etc.
12) I have installed the Universal USB Driver with the Universal Fastboot & ADB tool, Install drivers button, PC rebooted after this.
13) I used Windows 10, Windows XP, and Ubuntu, and in all cases I got the „Waiting for devices”
14) Under Ubuntu I got this message, despite that on Ubuntu the ADB and Fastboot driver installations are cleare.
15) I tested all on many other PC.
16) Every time I connected my phone to the PC only on USB 2.0 port, I changed the USB port, and I changed the USB cable too.
17) I read hundred ot tutorilas on youtube, on differant Forums, but none of them helped.
18) I uninstalled or reinstalled a many timet he ADB and fastboot drivers (I tested a lot of drives from the net), and I installet a many times the official Motorola driver, and the Google universal USB driver, but nothing
Please tell me what can I do for solve this devil situation, Please help me! Thank you again!
Wrong section mate, this is the section for Leeco Le Max 2 and not Moto G4. You're better off posting there in the correct section.
Excuse me
GethPrime said:
Wrong section mate, this is the section for Leeco Le Max 2 and not Moto G4. You're better off posting there in the correct section.
Click to expand...
Click to collapse
Excuse me, I can't see where can I post this! Please help me, where is a link, where I can repost this, or please move this , to a right place. Thank you!
tuzo1960 said:
Excuse me, I can't see where can I post this! Please help me, where is a link, where I can repost this, or please move this , to a right place. Thank you!
Click to expand...
Click to collapse
Not hard to find:
https://forum.xda-developers.com/moto-g4
Thank you
popoyaya said:
Not hard to find:
https://forum.xda-developers.com/moto-g4
Click to expand...
Click to collapse
Thank you popoyaya.
Please somebody delete this wrong placed thread! Thank you!
Closed per OP request
Related
Hi,
the last days, I read a lot about flashing custom ROMs and wanted to do so with my HTC Legend. I'm not really new to flashing ROMs in general.I already flashed several other devices, but I'm stuck with unlocking the bootloader. My problem is, that the CMD is either reacting with "CommandError" or "waiting for device". I'm not able to get the token for unlocking the bootloader. Another problem is, that the SDK Manager won't start for me. So I just grabbed the 3 files out of the filesystem and tried it with them. Using HTCs recommended fastboot.exe doesn't change anything. I hope you can help me with a few details:
1. Do I have to install something else than HTC Sync? (I think, it already installed the driver, too)
2. Which connection mode should i choose, when connecting the legend? (recharging/hdd/htc sync/tethering)
3. Which version of the SDK should I use? Is it possible, that someone just gives me a zip with those 3 files?
I'm looking forward to your answers!
Regards
OdlG
SOLUTION:
The solution was a too old version. My phone had version 3.15.405.3.
First I updated to version 3.15.405.6 (found via google here at xda-dev).
Then I patched the new ROM I downloaded from htc-dev (step 0 at unlocking; must connect phone for that hint!) 3.30.0.0.
Then I could receive the token via CMD at a Windows 7 PC (Win8 PC still said "waiting for device", obviously because the driver wasn't installed correctly so the phone wasn't recognised in fastboot mode).
I followed the last steps rom htc-dev and now unlocked the bootloader
Click to expand...
Click to collapse
(pardon my english, it's not my mothertongue)
AW: Difficulties with unlocking the Bootloader
You should use charging mode and you have to activate usb debugging in settings
Sent from my HTC One using xda app-developers app
Thanks for the reply!
I already enbled USB Debugging, and now tried it in charging mode. I created a BAT-File with the following command:
cd C:\Android\
fastboot oem get_identifier_token
But it still says "waiting for device" Any suggestions?
Did you follow these instructions? especcially selecting "fastboot"?
http://www.htcdev.com/bootloader/unlock-instructions
if yes and it still didn't work i've no idea at the moment
I tried it once more:
I connected the phone, "fastboot usb" is written there. the cmd still writes "waiting for device". after a few seconds, the pc reports, that the usb device could not be recognised. then there is written "fastboot" instead of "fastboot usb", though the cable is still connected.
a few hours ago i also got a guide at htc dev, that i should install da RUU (what does it mean btw?). i downloaded the german vodafone version and tried to install it. I will try that once more, hopefully the unlock will be successful afterwards!
thanks for your advice!
EDIT:I'm using the following software btw.
Android SDK (adt-bundle-windows-x86_64-20130219)
Java RE 7 Update 17
HTC Sync (3.3.X or something like that)
The RUU installer is starting the setup without problems. It's rebooting the phone o install version 3.30 (hboot1.02). But when the Phone starts in the bootloader mode and displays "RUU", the PC is unable to detect the USB device and the setup fails caused by missing usb connection
Can I somehow influence the detection of the phone in fastboot/bootloader mode?
Normally it should be enough to install the HTC USB Drivers...
You can grab the newest for example from this thread: http://forum.xda-developers.com/showthread.php?t=2191279
The second what you need is an actual adb.exe, fastboot.exe, AdbWinApi.dll & AdbWinUsbApi.dll... grab it for example from here: http://d-h.st/RvD (Thanx to torxx (http://forum.xda-developers.com/member.php?u=3828647))
After u've installed the drivers and extracted the adb file do the folowing
Turn off your phone completly
Push Vol down & Power ...device will start
Navigate with vol+- to fastboot press power
connect with usb-cable (possible that windows will install drivers...wait till its complete)
now "fastboot usb" should be read in the display of your phone
open a shell (cmd)
navigate to your fastboot.exe
type: "fastboot oem get_identifier_token"
it seems, that my htc firmware is far too old (3.15.405.3). i installed all the stuff on my win7 laptop instead of win8 desktop pc and could install the RUU... at least untill the notification, that i needed to update the firmware first, and update hboot1.02 (3.30.0.0) afterwards. the big update is also 150MB, the small one only 5MB. i'll give it a try and report back here, if i am able to manage all the stuff^^
btw autoupdating via options doesn't work ("phone is up to date"). do i have to sign in via google to get a better result?
I managed to unlock the bootloader!
The solution was a too old version. My phone had version 3.15.405.3.
First I updated to version 3.15.405.6 (found via google here at xda-dev).
Then I patched the new ROM I downloaded from htc-dev (step 0 at unlocking; must connect phone for that hint!) 3.30.0.0.
Then I could receive the token via CMD at a Windows 7 PC (Win8 PC still said "waiting for device", obviously because the driver wasn't installed correctly so the phone wasn't recognised in fastboot mode).
I followed the last steps rom htc-dev and now unlocked the bootloader
now i will try the rest Thanks for the helpful hints!
AW: [solved] Difficulties with unlocking the Bootloader
Okay nice to hear that it now works:thumbup:
I would say... Have fun while flashing and trying new roms
Sent from my HTC One using xda app-developers app
esco27 said:
Okay nice to hear that it now works:thumbup:
I would say... Have fun while flashing and trying new roms
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Already flashed CM10.1 It's not as smooth as on my Ainol Aurora 2 Tablet, but the Legend hasn't got the power by far. But if you have a look at the specs, it is amazing, how good it runs on the legend
Thanks for all the help! That was definately worth it^^ I only have minor problems with my SIM-card up to now.
Hi!
First off let me say thanks to R_a_z_v_a_n for redirecting me and hope that I'll find my answer here ^^
So I Have this device called HP 7 VoiceTab 1321RA (not with Slate just HP 7 Voicetab), wanting to have a custom recovery then I tried to flash a CWM Custom Recovery for HP Slate 7 VoiceTab because I thought it was the same and ends up bricking my phone. It ends up in a bootloop which only shows HP sign for a few seconds and dead. But I managed to find out that I can access the recovery menu (or so I thought it is), but the options was choosing between Fastboot Mode, Normal Boot, Recovery Mode, and VART Mode.
I tried to enter Fastboot Mode before and tried to access it via PC but somehow I can't find the device by entering adb devices and fastboot devices. Anyways, I have downloaded a stock update.zip for it but not the original KitKat one which I get from the first time I bought it but rather the JB ones. I think by flashing this would help me recover the device but the only problem is I don't know which method should I use to Flash it. Since I don't have the Stock Recovery or ANY kind of recovery at all, I guess I'm stuck. And it won't start to the home page so I can't set the USB debugging options. Please guide me through this >.<
Thanks a lot!
Been fighting with it for 2 days now and still no result came.
So here's the update so far....
I tried on my other device in order to understand how my PC reads ADB and now I kinda gets it. But the problem is now can't get the device to enable USB Debugging because I can't access options at all.
Secondly, since I left it on for the night because charging seems to trigger the bootloop too, now I can't access the fastboot mode like I was last night. And it constantly repeating this sequence: [battery scene with the "charging battery" symbol] > [HP Powered by Android screen] repeated for 2-3 times > [low battery need charging screen] > repeat. And once I tried to connect to the PC, it goes to the same sequence too. When I tried to access the boot options (the screen which displays Fastboot Mode, Normal Boot, Recovery Mode, and UART Mode which I mention in Thread Starting post), it shows the low battery need charging scene and then repeating the same sequence as mentioned above.
I seem to figure out how to fix this but I still can't manage to access the fastboot mode yet. Will give update once I can try to.
Anyone can help me on this?
Thanks a lot!
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
I found my self in a deadlock!
PLEASE HELP :crying:
Could you unbrick yours
What service centre says about that problem i also ran in this problrm but i m trying to go to service centre for that
first off install drivers in your PC as admin
then use the official flashtool to flash ur stock firmware by entering fastboot or flashmode simple as that
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
Dude urs is a mtk device so sp flash tool should do the trick.... Just don't forget to install correct drivers....run both drivers and flash tool as admin..... Tell me when it's solved k
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
That is what im trying. To tell you urs is a mediatek device the official flashtool is sp flashtool
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
try to push the update.zip via adb sideload (Choose "update via ADB sideload" on recovery mode)using adb terminal on PC,as long as your tab can access the recovery mode.remember to backup all your data before u do it.
have a try it's 100% work on me
where I can download update.zip file? anyone can help?
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
can you explain how did you managed to charge the device??? please its a request......jst help me out :crying::crying:
I read much forum here, but I can't figure it out going to Indian or Chinese stock Rom...
Has the X829 an encrypted partition?
I read about TWRP update.zjp and recovery.zip
What is difference?
How to backup full system, so I can restore it when something go wrong?
Is there a clear guide for X829 for updating to Indian/Chinese Rom?
TWRP has a update/recovery zip, what does it does?
Must the x829 rooted for updating to Indian/Chinese Rom?
Thank you very much!
Bobenjanneke said:
How to backup full system, so I can restore it when something go wrong?
Is there a clear guide for X829 for updating to Indian/Chinese Rom?
Click to expand...
Click to collapse
Here
---------- Post added at 05:01 PM ---------- Previous post was at 05:00 PM ----------
Bobenjanneke said:
Must the x829 rooted for updating to Indian/Chinese Rom?
Click to expand...
Click to collapse
No.
Me was told, that the X820 only has to rename a Rom to update.zip?
The guide for the **X829** , do I have to follow it every time when updating, or only 1 time, and every next time is renaming to update.zip enough?
Bobenjanneke said:
Me was told, that the X820 only has to rename a Rom to update.zip?
The guide for the **X829** , do I have to follow it every time when updating, or only 1 time, and every next time is renaming to update.zip enough?
Click to expand...
Click to collapse
Whenever you going to update official rom manually, you need to rename it 'update.zip'.
X829, x820, x821 etc...all are same device.
Bobenjanneke said:
Me was told, that the X820 only has to rename a Rom to update.zip?
The guide for the **X829** , do I have to follow it every time when updating, or only 1 time, and every next time is renaming to update.zip enough?
Click to expand...
Click to collapse
No, only one time to move from Vendor rom (the one comes with phone ), then you can normally update it OTA or local.
Bobenjanneke said:
I read much forum here, but I can't figure it out going to Indian or Chinese stock Rom...
Has the X829 an encrypted partition?
I read about TWRP update.zjp and recovery.zip
What is difference?
How to backup full system, so I can restore it when something go wrong?
Is there a clear guide for X829 for updating to Indian/Chinese Rom?
TWRP has a update/recovery zip, what does it does?
Must the x829 rooted for updating to Indian/Chinese Rom?
Thank you very much!
Click to expand...
Click to collapse
I think install TWRP is the easiest way. I bought X829 few weeks ago, installed TWRP and backup the system that come with the phone and can flash any custom rom. I did try flashed Official Indian 5.8.019S, China 5.9.020S,5.9.023S. You can flash any official stock rom with TWRP I tested it worked fine.
I don't find much different between the roms except Chinese rom have some Chinese apps and don't have Google service/Player store but can download and install after rom is installed.
For backup normally there is system image in internal storage maybe it's the system/rom that come with the phone. I have not try to restore this system image though I not sure its only install the rom or wipe internal storage too.
---------- Post added at 05:29 AM ---------- Previous post was at 05:28 AM ----------
Note I installed TWRP 3.0.2 from official website. Try this one if other version don't work.
Hi,
I just started with ADB.
In "cmd", when I enter "ADB usb" it answers "null"..
When I enter "ADB devices" it answers "listof devices attached" with nothing else...
In ezplorer, is Le Max 2 showed under the hdd's...
Who can help?
-----------
I tried it, when plugging in the USB port, selecting "USB media device" and "charger only" with USB debugging checked on...
At me, ADB is installed automatically in C:\adb so I am working from that path....
Bobenjanneke said:
Hi,
I just started with ADB.
In "cmd", when I enter "ADB usb" it answers "null"..
When I enter "ADB devices" it answers "listof devices attached" with nothing else...
In ezplorer, is Le Max 2 showed under the hdd's...
Who can help?
-----------
I tried it, when plugging in the USB port, selecting "USB media device" and "charger only" with USB debugging checked on...
At me, ADB is installed automatically in C:\adb so I am working from that path....
Click to expand...
Click to collapse
it is Driver issue, go here and follow the instructions
AhmadSant said:
it is Driver issue, go here and follow the instructions
Click to expand...
Click to collapse
Thank you! That worked!
I only checked the "Google usb driver" , everything else I unchecked...
But when I run ADB usb, $adb_vendor_keys is not set...
ADB reboot bootloader gives same message, both are talking about ADB kill server?
When I command ADB kill server, and run ADB usb, it says
*Daemon not running, starting it etc etc"
I have Daemon tools installed, but is not active on the right bottom in the task bar....
ADB devices gives a number with "unauthorised"...
I think, I know myself the problem...
I only downloaded the software package, unchecked everything ( so also the mainpackage ) and installed only the extras/usb driver...
But know, it is 11pm, to late for me know....
X829 have problem phone not detect under Fastboot mode, Fix is in below link with description:
https://forum.xda-developers.com/showpost.php?p=72154309&postcount=72
So far I used your tips...
-adb kill-server
-adb start-server
-adb usb
->restarting in USB mode
-adb devices
->list of devices attached
-ADB reboot bootloader
->on theb phone "you have entered fastbootmode"
-Fastboot OEM device-info
-> waiting for device ( already an hour)
Ctrl-c
Fastboot OEM unlock
->waiting for device
It is still waiting......
Test TWRP Recovery before flashing internal
Hi,
After you install the drivers and Android Tools all starts to make sense
careful when flashing TWRP into the recovery partition, test with adb and the recovery reboot the file you have, I downloaded by mistake a lower version and all it did was show some lines like it was in a higher screen resolution after a while downloaded the latest and worked, flashed that one into recovery. This makes flashing anything again possible without connecting the phone to the pc other than to copy the file.
In my opinion the stock ROMs are heavy and make the phone work slower but if you want to stick to Official LeEco ROMs than I should advise the Chinese ROM, I've read it doesn't encrypt the Data mount points.
Make a backup of your current installation as mentioned in the link posted earlier, I'm not an expert also and am still learning stuff (forced by the low quality ROMs and the fact that it is an unofficial phone).
Lineage Nougat (new and tested in my phone) and Remix (from what I've heard) are pretty good and make phone light and working fast.
Don't Forget to install Google Apps afterwards (GApps as they call it).
There isn't really the need to rename the file to upgrade.zip just click the zip file and swipe to flash the new ROM.
I haven't rooted my phone, heard that Apps like Home Bank ones don't work so nvm that unless you need it but maybe in a few months you think otherwise, gain some experience first. It's not needed to do any of the things mentioned, only for changing Kernel settings and other stuff... I'm not there yet...
Tried Dolby Atmos from XDA but only one works, test it from the top and see if the app works. Install a Icon builder App to create the icon because it won't show in the settings like in the custom ROM. Other than that improves the sound quality.
Regards,
Pedro
Bobenjanneke said:
So far I used your tips...
-adb kill-server
-adb start-server
-adb usb
->restarting in USB mode
-adb devices
->list of devices attached
-ADB reboot bootloader
->on theb phone "you have entered fastbootmode"
-Fastboot OEM device-info
-> waiting for device ( already an hour)
Ctrl-c
Fastboot OEM unlock
->waiting for device
It is still waiting......
Click to expand...
Click to collapse
Repeat again but skip this one:
-Fastboot OEM device-info
Seems drivers are not loading
Hi,
After you connect the device it should start to work if the drivers are correct, this may take a while at first but I used the info cmd to check if it was working
adb reboot bootloader
(will reboot device into bootloader)
fastboot oem device-info
(should return an ID for you phone)
fastboot boot twrp-3.1.0-0-x2.img
(should start TWRP in the phone)
-- flashing only
fastboot flash recovery twrp-3.1.0-0-x2.img
(Make sure the last command worked correctly before flashing recovery, it doesn't have to be renamed to recovery.zip)
Install Android tools, after that the drivers should start to work. Let us know.
Regards,
Pedro
Thank you all for your help already!
Sorry for my next question, but i am really f*cked up...
Does someone has Skype or Whatsapp for instant help?
I deleted and reinstalling ASDK Manager.
The driver for Le Max 2 is older then Google USB driver, so I cant update the Google USB Driver...
Do I have to do Fastboot OEM unlock?
What is difference between "fastboot FLASH" and "fastboot BOOT"?
Thank you very much again!!!
Bobenjanneke said:
The driver for Le Max 2 is older then Google USB driver, so I cant update the Google USB Driver...
Do I have to do Fastboot OEM unlock?
What is difference between "fastboot FLASH" and "fastboot BOOT"?
Thank you very much again!!!
Click to expand...
Click to collapse
Hi,
Can't remember if the older drivers worked but I can test at home.
The phone should be unlocked already (x829) but you can issue the unlock cmd any time, it will say already unlocked or do it, but the phone needs to connect.
Did you allow USB debugging and did all the other steps they say in the forum? Switch on the phone to media option instead of just charging or it will not allow the connection.
fastboot boot twrp-3.1.0-0-x2.img
-- After the reboot with "adb reboot bootloader" cmd is successful if you issue this it will upload TWRP into the phone using adb and start it, I suggest to use this method at first.
the flash cmd will replace the recovery of the phone with TWRP Recovery, so everytime you enter recovery mode by pressing Vol. Up + Power it will go to TWRP TeamWin instead. Do a backup just in case of the phone using the "fastboot boot twrp-3.1.0-0-x2.img" cmd.
Let us know how it goes...
Regards,
Pedro.
My steps:
-Connected via Media Connection
-Allow USB debugging
-OEM unlocked
-Gave permission on phone screen
Installed ASDK from the guide R24.4.1 ( installed all checked boxes )
ADB start-server
ADB USB
ADB DEVICES
ADB REBOOT BOOTLOADER
and then it hang both on OEM DEVICE-INFO & OEM UNLOCK...
-------------------------
I am installing Universal ADB drivers, maybe that workx....
BTW, I am working with Windows7 64Bit Ultimate...
What was yours both OS?
Thank you very much!
I searched myself on Google, and tried some solutions, but nothing worked...
Installing the Universal ADB driver didn't bring any solution....
I read that after ADB REBOOT BOOTLOADER or FASTBOOT OEM UNLOCK, I have to press the volume up? I didn't read that in the guide ( and it didn't work even )...
I have an old laptop, which I can down/upgrade with XP SP3 or W10...
Hi,
I've had a problem to force fastboot to detect my XT1580 Kinzie.
I've searched all the internet and couldn't solve this.
After few days I stomped upon this post
It seems that first thing you should do even if ADB works for you (in my case it did) is:
1. Reboot the phone to fastboot
2. Open Device Manager
3. Check that there is your phone as "Fastboot Kinzie S" with exclamation mark or there is no "fastboot" anything there
4. If there is, you really need to hack Motorola Driver Installer (extract proper *.msi" while running it) to get driver properly installed.
Worked for me as a charm.
This post is for anyone having same problem. I hope it helps.
Help me
Please explain full procedure
Hello friends,
I am following this guide here to try to root my WP7:
http://androidbiits.com/root-oukitel-wp1-wp2-wp7-easily/
Everything works fine, except for the very last step, when I am supposed to flash the patched .img.
I issue the command
fastboot flash boot magisk_patched.img
and all I am getting is "Waiting for device".
The screen remains in "FASTBOOT mode..." and nothing else happens.
What am I doing wrong? I would appreciate some help, please.
Thank you.
Did you use the MTK USB-drivers?
jwoegerbauer said:
Did you use the MTK USB-drivers?
Click to expand...
Click to collapse
Hi, thanks for the reply. I already have the MTK USB_All_v1.0.8 driver installed as my previous phone was also MKT based.
I can see Windows installing different types of drivers when i connect my phone, so I assumed I was alright.
Perhaps you or anyone else can link for me the correct MKT USB drivers to use? Googling I found different links that seem to be different.
I also tried adb from my Mac too, same result: nothing seems to happen.
Thanks!
@fabioganga
For phones with Mediatek MT65xx chips it exists the so-called Mediatek MT65xx USB VCOM driver which claims that fastboot problems no longer occur.
Look inside here.
jwoegerbauer said:
@fabioganga
For phones with Mediatek MT65xx chips it exists the so-called Mediatek MT65xx USB VCOM driver which claims that fastboot problems no longer occur.
Look inside here.
Click to expand...
Click to collapse
Thanks @jwoegerbauer for the quick reply, much appreciated. As far as I ma maware the processor is a 6779, but the page refers to MT65xx drivers. Are they the same drivers?
No joy at all with Windows, not even with the drivers the article mentioned features.
I tried again with my Mac instead, installing adbd and fastboot there.
I am finally getting the phone to respond,
howver, the bootlaoader in my case was unlocked, so I first had to type
fastboot flashing unlock (warning! it deletes all data!) and confirm it with volume UP.
Then, after the device reboots to fastboot, I can finally type
fastboot flash boot magisk_patched.img
and it flashes correctly.