I was on Unofficial CM13 by SultanXDA!
For further update it requires OOS 3.1.3 Firmware, so I flashed OOS 3.1.3 pure!
It comes with its stock recovery i.e. I need to flash TWRP for same!
I had drivers and minimal adb-n-fastboot installed already and also $adb devices detects my device!
So, when i connect device with fastboot mode to flash TWRP it detects my Android bootloder device (according to device manager | win10) but
Code:
fastboot device
<waiting for device>
doesn't work and stuck there only!
If you can boot into OS could root with KingRoot and flash recovery with app like Rashr or Flashify.
Are you tried this process with other versions of Windows (lower than window 10)?
Windows 10 have some drivers problem.
Is your opx boot?
If Android Emulator program (Bluestack, Andy etc) is installed on your computer, you should remove it. And try again...
yuv93 said:
Are you tried this process with other versions of Windows (lower than window 10)?
Windows 10 have some drivers problem.
Is your opx boot?
Click to expand...
Click to collapse
Although I'm not the OP I had the same problem.
Used my older Laptop with Win7 and I was able to find my opx in fastboot mode thanks for saving my life <3
Nagesh_Noddy said:
I was on Unofficial CM13 by SultanXDA!
For further update it requires OOS 3.1.3 Firmware, so I flashed OOS 3.1.3 pure!
It comes with its stock recovery i.e. I need to flash TWRP for same!
I had drivers and minimal adb-n-fastboot installed already and also $adb devices detects my device!
So, when i connect device with fastboot mode to flash TWRP it detects my Android bootloder device (according to device manager | win10) but
doesn't work and stuck there only!
Click to expand...
Click to collapse
had the same on ubuntu, my solution may also work for your problem .. run the console as admin and see if it detects your device! if not you probably need to install oneplus drivers
regards,
OD
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...
Hello!
I know this must be a stupid question but couldn't find the solution!
I was trying to unlock the bootloader but it looks like the phone is not recognized by the system (adb devices find it correctly but when I give the "fastboot flashing unlock" command, it will wait for the device indefinitely).
The phone is not recognized in Control Panel -> System -> Devices (it has the yellow triangle warning) so I tried installing the official Xiaomi USB Drivers (downloaded xiaomi_usb_drivers.rar from the official xiaomi website) but it would not succeed.
So what drivers should I install? And where to find them?
Thank you
DBuffon said:
Hello!
I know this must be a stupid question but couldn't find the solution!
I was trying to unlock the bootloader but it looks like the phone is not recognized by the system (adb devices find it correctly but when I give the "fastboot flashing unlock" command, it will wait for the device indefinitely).
The phone is not recognized in Control Panel -> System -> Devices (it has the yellow triangle warning) so I tried installing the official Xiaomi USB Drivers (downloaded xiaomi_usb_drivers.rar from the official xiaomi website) but it would not succeed.
So what drivers should I install? And where to find them?
Thank you
Click to expand...
Click to collapse
Download pdanet for windows
It'll automatically install drivers
Connect your device in fastboot mode and install pdanet in your pc
Thanks. Do you mean "PdaNet for Android" by JuneFabrics?
DBuffon said:
Thanks. Do you mean "PdaNet for Android" by JuneFabrics?
Click to expand...
Click to collapse
For windows
Rajendran Rasa said:
For windows
Click to expand...
Click to collapse
Can you point me to it? I've googled but there are different things and softwares named pdanet, so I'm not sure which one is the correct one.
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.
Hello!
I need to downgrade Android 10 to Android 9 on my Oppo F11 Pro. I've flashed many roms till now on other devices. This one is a bit *cough*
I have the .ozip file of the Android 9 rom, need to flash.
Default recovery mode of ColorOS doesnt work ofc, doesnt support downgrading.
After converting .ozip to .zip and extracting the files, SP Flash Tool or such tools arent able to get the files somehow They dont load it up, even not the scatter files.
So I think I should first unlock the bootloader, which I've been trying to today.
Doing the "adb devices" doesnt list my device, guess I need the drivers.
Downloaded drivers but they are in .inf format, which Ive been unable to install (with my "search the internet and do it" ways.
"The inf file you selected does not support this method of installation". And thru administrator cmd, its Installation failed.
Im so confused with those drivers Idk which ones to install.
One driver I've pasted on hastebin as.. hastebin[dot]com/abopesexej.shell
Couls someone pls help me out? Im hitting the wall atm
Neon111 said:
Doing the "adb devices" doesnt list my device, guess I need the drivers.
Downloaded drivers but they are in .inf format, which Ive been unable to install (with my "search the internet and do it" ways.
"The inf file you selected does not support this method of installation". And thru administrator cmd, its Installation failed.
Im so confused with those drivers Idk which ones to install.
One driver I've pasted on hastebin as.. hastebin[dot]com/abopesexej.shell
Couls someone pls help me out? Im hitting the wall atm
Click to expand...
Click to collapse
Don't mix up USB-driver and ADB-driver and/or Fastboot-driver: totally different drivers.
A USB-driver is a file that allows an USB hardware device to communicate with the operating system of a computer. This driver is implemented in all operating systems by default.
ADB-driver and/or Fastboot-driver is a “bridge” for Android developers / hackers to work out bugs in their Android applications and/or modify existing Android OS. This is done by connecting an Android device that runs the software through a PC, and feeding appropriate commands in its terminal.
Don't use any ADB-driver and/or Fastboot-driver as they are hundreds of times published on the WEB - and even here on XDA. Only make use of those drivers officially offered by your device's OEM/Carrier.
Comment withdrawn by author.
(When "adb devices" shows the device serial)
When i try to do "adb reboot bootloader",
The phone reboots and says
"The serial is not matched
fastboot_unlock_verify fail"
What should I do? :u
And not being able to use fastboot.. I cant find related drivers on the internet for that purpose.. I downloaded and installed what I could (fastboot commands not working.. shows <waiting for device> )
Neon111 said:
(When "adb devices" shows the device serial)
When i try to do "adb reboot bootloader",
The phone reboots and says
"The serial is not matched
fastboot_unlock_verify fail"
What should I do? :u
Click to expand...
Click to collapse
Generally speaking, the serial number as reported by ADB will be different to Fastboot as determined by:
Manufacturer
Make and model of device in question
Android version
Fastboot, on the other hand, since there's no ADB loaded, instead, uses a rudimentary USB protocol tied in with Android's boot-loader, the serial number will be different.
EDIT:
Neon111 said:
And not being able to use fastboot.. I cant find related drivers on the internet for that purpose.. I downloaded and installed what I could (fastboot commands not working.. shows <waiting for device> )
Click to expand...
Click to collapse
Your Oppo F11 Pro is based on Mediatek chipset. IMO you instead of Fastboot driver have to make use of Oppo F11 Pro Mediatek driver - a specialized version of general Fastboot driver - what is compatible with SP Flash Tool, MTK Flash Tool, SP MDT Tool and SN Write Tool.
DL: https://gsmusbdriver.com/oppo-f11-pro
jwoegerbauer said:
Your Oppo F11 Pro is based on Mediatek chipset. IMO you instead of Fastboot driver have to make use of Oppo F11 Pro Mediatek driver - a specialized version of general Fastboot driver - what is compatible with SP Flash Tool, MTK Flash Tool, SP MDT Tool and SN Write Tool.
DL: https://gsmusbdriver.com/oppo-f11-pro
Click to expand...
Click to collapse
But I do not have flash files related to the listed programs..
Everywhere I could find only an .ozip file, which I turned into a .zip from a program I found on here. The zip when extracted gave me all the .img files and scatter.txt, but the scatter.txt doesnt load up in SP Flash Tool and the like.
Neon111 said:
But I do not have flash files related to the listed programs..
Everywhere I could find only an .ozip file, which I turned into a .zip from a program I found on here. The zip when extracted gave me all the .img files and scatter.txt, but the scatter.txt doesnt load up in SP Flash Tool and the like.
Click to expand...
Click to collapse
Were you able to unlock your bootloader? I found various tutorials of extracting boot image from the ozip files. But Veterans are saying oppo doesn't let people unlock bootloader.