Hi All
Successfully got my RN3 stuck on MI logo, so no boot. Having tried many suggestions, the nearest I got to fixing it was with MIFlash. I believe I've connected the right file paths and on 'flash' I got this response...any thoughts please?
I was using: kenzo_global_images_V8.0.1.0.LHOMIDG_20160805.0000.29_5.1_global_5e65360aff
[000015F8]CreateManagedObject(1392): Unspecified error(0x80131604)
[000015F8]GetFactoryObject(1436): Unspecified error(0x80131604)
[000015F8]CreateManagedObject(1392): An attempt was made to load a program with an incorrect format.(0x8007000b)
[000015F8]GetFactoryObject(1436): An attempt was made to load a program with an incorrect format.(0x8007000b)
[000015F8]GetFactoryObject(1457): The specified service does not exist.(0x800704db)
[000015F8]GetSearchPath(1512): The specified service does not exist.(0x800704db)
[000015F8]StartFlash(13): The parameter is incorrect.(0x80070057)
[00001404]YPVSLBORPZEE5DZ9 0.00 execute E:\Users\Trev555\Downloads\kenzo\kenzo\flash_all.bat
[00001404]YPVSLBORPZEE5DZ9 0.03
[00001404]YPVSLBORPZEE5DZ9 0.03 $fastboot -s YPVSLBORPZEE5DZ9 getvar product 2>&1 | findstr /r /c:"^product: *kenzo" || echo Missmatching image and device
[00001404]YPVSLBORPZEE5DZ9 0.30 Missmatching image and device
[00001404]YPVSLBORPZEE5DZ9 0.30
[00001404]YPVSLBORPZEE5DZ9 0.30 $fastboot -s YPVSLBORPZEE5DZ9 getvar product 2>&1 | findstr /r /c:"^product: *kenzo" || exit /B 1
[00001404]YPVSLBORPZEE5DZ9 0.36
[00001404]CScriptReport:oWork(433): Unspecified error(0xffffffff)
[00001404]GetFactoryObject(1457): The specified service does not exist.(0x800704db)
[00001404]SaveFlashResult(1478): The specified service does not exist.(0x800704db)
........thanks in advance for any useful advice
What is your OS? Make sure it's 64 bit..
Did you installed all the driver/requirements correctly?.. You flash it via fastboot or EDL?
The model checking parameter is returning error. Check if you have Mediatek / Snapdragon model of Redmi Note 3.
Thanks for your reply
To offer more information I'm on Windows 8.1 x 64. The error (posted earlier) was when the phone was in Fastboot mode.
In device manager the only thing to note is Android Bootloader Interface but nothing shown in 'other devices'.
When in recovery mode I see Android ADB interface but nothing shown in 'other devices'.
When I type cmd/adb devices the i/d comes up with the word 'sideload' alongside. This I don't understand.
I hope this may give you some ideas Thanks.
I meant to say my phone is running on snapdragon.
Related
The Android device in question is a Micromax A87(a relatively unknown brand in global market but I hope that should'nt matter).
In Ubuntu, I have double checked the udev rules. They all look perfect. (I cross checked using another phone too). The USB debug mode doesn't show up no matter what. And I have the adb_usb.ini in the right place. I have tried running all possible combinations of running
adb, adb start-server as root. But
Code:
adb devices
shows no devices at all.
However, with the USB debugging option enabled on phone, it worked on Win7 after windows installed a Common handset driver.
Now the interesting part.
If I go back to Ubuntu without disconnecting the cable and do
Code:
$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[B]1234567890ABCDEF[/B] device
The product id is 1234567890ABCDEF and I am able to see it and everthing works fine!!
But the moment I disconnect the USB cable, its gone.
So I guess it's not the development machine that is at fault. The device seems to be setting a property while in Windows which stays latched till the usb connection goes off.
What could be a way to get this to work? (Besides developing on Windows :silly: )
Btw the
Code:
/data/property/persist.service.adb.enable
is 1 too.
What is your computer setup? Are you using a Windows machine, with Ubuntu in a vm? Dual-boot? Other?
My setup:
Dual boot.
Ubuntu 12.04 and Windows 7.
Ok, how about if you plug in the USB with the computer's power off, then boot into Ubuntu?
i have the clone of this phone. mine is Mito A78.
lsusb command shows it as 1c9e:9e08
so idVendor =1c9e and idProduct = 9e08
for now, what you say (plugin to windows and reboot to ubuntu without unplug the phone) is the solution.
i will see if lsusb output still the same.
okay, have checked on windows pc, it should be switched to idVendor =1c9e and idProduct = 9e18
anyway, what you say is a clue that the solution may be around usb_modeswitch and modem manager
further search on usb_modeswitch 1c9e 9e08 found the solution here: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=3&t=1351
have tried, but not yet switched to idVendor =1c9e and idProduct = 9e18
have to find the correct rules on /etc/usb_modeswitch.d/1c9e:9e08
Code:
########################################################
# Mito A78
DefaultVendor=0x1c9e
DefaultProduct=0x9e08
TargetVendor=0x1c9e
TargetProduct=0x9e18
SierraMode=1
CheckSuccess=20
NoDriverLoading=1
found it.
after writing the rules, insert
Code:
# Mito A78
ATTR{idVendor}=="1c9e", ATTR{idProduct}=="9e08", RUN+="usb_modeswitch '%b/%k'"
to /lib/udev/rules.d/40-usb_modeswitch.rules
i than have to run
Code:
sudo usb_modeswitch -v 0x1c9e -p 0x9e08 -S -R -W
and then the phone switched to idVendor =1c9e and idProduct = 9e18 and adb can access the phone.
:good: :good: :good:
I-mobile IQ 5.1 has same issue, but adb still can't see device
The usb_modeswitch is exactly the same for this phone (same usb vid/pid). However adb still doesn't find the phone under Windows and Ubuntu. lsusb shows the product id switch did work and it all looks right.
Under windows it spins up a cdrom device from the phone so you can install the windows drivers (this lives as an *.iso file under /system); after the driver install, you get the adb device in device manager and two com ports,with all devices having a pid of 9e18 (original 9e08). However adb does not see the device!
I recon there is something wrong on the phone side. This is a very new phone (only release about 5 days ago), so I suspect this is one of the early release bugs...
Since I don't even have a custom recovery for it (CWM, etc) I can even backup my phone and try and do a factory reset.
Looks like a low level USB issue
Switched on tracing on adbd on the phone side. Looks like a phone/usb low level issue:
Code:
--- adb starting (pid 14270) ---
system/core/adb/adb.c::main():Handling main()
system/core/adb/adb.c::adb_main():Local port disabled
system/core/adb/usb_linux_client.c::usb_init():failed to open /dev/android_adb_enable
system/core/adb/usb_linux_client.c::usb_init():[ usb_init - starting thread ]
system/core/adb/adb.c::adb_main():adb_main(): pre init_jdwp()
system/core/adb/jdwp_service.c::jdwp_control_init():jdwp control socket started (5)
system/core/adb/adb.c::adb_main():adb_main(): post init_jdwp()
system/core/adb/adb.c::adb_main():Event loop starting
system/core/adb/usb_linux_client.c::usb_open_thread():[ usb_thread - opening device ]
system/core/adb/usb_linux_client.c::usb_open_thread():[ opening device succeeded ]
system/core/adb/usb_linux_client.c::usb_open_thread():[ usb_thread - registering device ]
system/core/adb/transport.c::register_usb_transport():transport: 0x11364a0 init'ing for usb_handle 0x1136410 (sn='')
system/core/adb/transport_usb.c::init_usb_transport():transport: usb
system/core/adb/transport.c::register_transport():transport: (null) registered
system/core/adb/transport.c::transport_registration_func():transport: (null) (10,11) starting
system/core/adb/transport.c::output_thread():(null): starting transport output thread on fd 11, SYNC online (2)
system/core/adb/transport.c::dump_packet():fd=11: to remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/transport.c::transport_socket_events():transport_socket_events(fd=10, events=0001,...)
system/core/adb/transport.c::dump_packet():fd=10: from remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/adb.c::handle_packet():handle_packet() SYNC
system/core/adb/transport.c::dump_packet():fd=10: to remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/transport.c::output_thread():(null): data pump started
system/core/adb/usb_linux_client.c::usb_read():about to read (fd=9, len=24)
system/core/adb/transport.c::input_thread():(null): starting transport input thread, reading from fd 11
system/core/adb/transport.c::dump_packet():fd=11: from remote: [SYNC] arg0=1 arg1=2 (len=0)
system/core/adb/transport.c::input_thread():(null): transport SYNC online
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 11279 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 11325 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 11818 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13994 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13951 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13913 to jdwp process list
system/core/adb/jdwp_service.c::jdwp_process_event():Adding pid 13856 to jdwp process list
system/core/adb/usb_linux_client.c::usb_read():ERROR: fd = 9, n = -1, errno = 5 (I/O error)
system/core/adb/transport_usb.c::remote_read():remote usb: read terminated (message)
system/core/adb/transport.c::output_thread():(null): remote read failed for transport
system/core/adb/transport.c::output_thread():(null): SYNC offline for transport
system/core/adb/transport.c::dump_packet():fd=11: to remote: [SYNC] arg0=0 arg1=0 (len=0)
system/core/adb/transport.c::output_thread():(null): transport output thread is exiting
system/core/adb/usb_linux_client.c::usb_kick():usb_kick
---------- Post added at 04:31 AM ---------- Previous post was at 04:27 AM ----------
I also tried the Chainfire adbd insecure and its exactly the same in the debugging.
Now working on win7 64!
Followed this link and managed to get it working. The PID value was set to 9e18. In essence the andriod usb driver was missing (install via the andriod.bat andriod package manager).
Also works in virtualbox winxp vm on Linux (ubuntu 12.10; actually Mint 14). Just mapped in my win7 64 partition to get access to the andriod sdk/usb driver.
Now that I know its not a handset issue, can return to trying to get the Linux side working.
Now working under Linux!
You need the vendor id in adb_usb.ini:
Code:
cat ~/.android/adb_usb.ini
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1c9e
If you will run adb as root, make sure you also create the file for root too.
Tip: You will be logged into the phone as the 'shell' user. Try and 'su -' to get root access, and then click on your su dialog on the phone to grant access.
Final issue is that plugging in the device should do the switch automatically; I will update you on that when I have that fixed.
udev sorted on ubuntu
Ok, we are rocking on udev on ubuntu 12.10. Seems like udev doesn't like ATTR keywords, although ATTRS makes everything burst into life (man page says ATTR is useable). Steps that worked for me:
Code:
# cp /lib/udev/rules.d/40-usb_modeswitch.rules /etc/udev/rules.d/usb_modeswitch.rules
# vi /etc/udev/rules.d/usb_modeswitch.rules
Add the following entry near the bottom under the last entry:
Code:
# I-Mobile IQ5.1
ATTRS{idVendor}=="1c9e", ATTRS{idProduct}=="9e08", RUN+="usb_modeswitch '%b/%k'"
Create /etc/usb_modeswitch.d/1c9e:9e08 as described earlier by jurban.
Unplug the phone. Plug it in. Do an lsusb. Firstly shows up as dev 1c9e:9e08. Enter lsusb again. Shows up as 1c9e:9e18. Now adb will show the device as jurban shows above. All good to go!
Hi, I am having issues with a Huawei modem E173u-1 on my tablet Archos 101 g9 8gb
driver not found.
Can you help me, pls?
USB_ModeSwitch log from Wed Apr 09 17:50:44 PKT 2014
Raw args from udev: 1-1/1-1:1.0
Using top device dir /sys/bus/usb/devices/1-1
----------------
USB values from sysfs:
manufacturer HUAWEI
product HUAWEI Mobile
serial
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/12d1.14fe
! matched. Reading config data
devList 1:
config: TargetVendor set to 12d1
config: TargetProduct set to 1506
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Logger is: /system/bin/log
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 2 -v 12d1 -p 14fe -f $cB
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.4 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x12d1
DefaultProduct= 0x14fe
TargetVendor= 0x12d1
TargetProduct= 0x1506
TargetClass= not set
TargetProductList=""
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="55534243123456780000000000000011062000000100000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 001/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 12d1:14fe
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)
USB description data (for identification)
-------------------------
Manufacturer: HUAWEI
Product: HUAWEI Mobile
Serial No.: not provided
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Could not reset endpoint (probably harmless): -34
Resetting message endpoint 0x01
Could not reset endpoint (probably harmless): -6
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Waiting for device file system (1 sec.) ...
Waiting for device file system (2 sec.) ...
Waiting for device file system (3 sec.) ...
Waiting for device file system (4 sec.) ...
Waiting for device file system (5 sec.) ...
Waiting for device file system (6 sec.) ...
Waiting for device file system (7 sec.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 12d1:1506 (HUAWEI: HUAWEI Mobile)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0 yet
Module loader is /sbin/insmod
Trying to find and install main driver module "option"
Trying to find module "option"
Loading support module /lib/modules/usb_wwan.ko
Error: insmod: cannot insert '/lib/modules/usb_wwan.ko': Invalid module format (-1): Exec
format error
Loading main driver module "option"
Error: insmod: cannot insert '/lib/modules/option.ko': Invalid module format (-1): Exec
format error
Falling back to "usbserial"
Module "usb_serial" not found, can't do more here
Driver binding seems to have failed
All done, exiting
please answer!!!
i'm solved the problem by replacing the nucleus
Hello..
Which fastboot rom is correct for my mido Device.. i downloaded Both Stable and Developer version both giving mismatched image error..
tried flashing from mi flash tool, flashed in 1sec issue..
Please help , how am i suppose to flash stock rom via fastboot or miflash tool..
My bootloader is already unlocked..
is their any proper guide or youtube video or something and proper download link. i am sure i downloaded the right file but don't know why getting these errors..
My Phone is Redmi Note 4 (mido) , currently on STable Global Version
Thanks..
Got my mi approval for unlock today and I got same problem as yours... here's what I did:
1. Be sure you have downloaded correct ROM (I'm using mido_global_images_V8.2.10.0.MCFMIDL_20170602.0000.00_6.0_global)
2. edit your *.bat files in your ROM folder, probably these:
flash_all.bat
flash_all_except_storage.bat
flash_all_lock.bat
flash_all_lock_crc.bat
flash_factory.bat
3. comment out the first 2 lines in those files (product check related):
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || echo Missmatching image and device
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || exit /B 1
save those files
4. open up your MiFlash and try flashing again.
Oh by the way, if you're planning to use TWRP, use the one for Redmi Note 4 with MTK (Nikel), you won't be able to use official twrp-mido image.
Here's the reference:
https://forum.xda-developers.com/redmi-note-4/help/flashing-twrp-redmi-note-4x-failure-t3615871
good luck
For anyone still looking for help on this:
There can be issues with flashing (and possibly even unlocking etc. in some cases) on Ryzen powered computers. I've been troubleshooting for a pretty long time on this issue and one of the mods on the Xiaomi Community discord server (unofficial) told me to try on an Intel powered computer
To my surprise, firing up Xiaomi ADB Fastboot tools on an Intel laptop worked and the recovery image flashed
If you just happen to be on a Ryzen processor, give Intel one a shot (nothing against AMD by the way, been using it for a while now. Except for some issues with the graphics drivers, but that's a different story)
One more note: This happened on a tulip (Redmi Note 6 Pro) in my case. I've flashed a fastboot ROM on raphael (Redmi K20 Pro / Mi 9T Pro) succesfully on my Ryzen powered PC before. This might not be always the case.
Thanks for reading and hope this can help at least someone as it definitely saved my ass from EDL flashing
Hello..
i have redmi note 4 and i am installing stock rom but it says that rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || echo Missmatching image and device
Now waht i do
can you please explain me.
pls
Thanks
Thanx
ezraimanuel said:
Got my mi approval for unlock today and I got same problem as yours... here's what I did:
1. Be sure you have downloaded correct ROM (I'm using mido_global_images_V8.2.10.0.MCFMIDL_20170602.0000.00_6.0_global)
2. edit your *.bat files in your ROM folder, probably these:
flash_all.bat
flash_all_except_storage.bat
flash_all_lock.bat
flash_all_lock_crc.bat
flash_factory.bat
3. comment out the first 2 lines in those files (product check related):
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || echo Missmatching image and device
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || exit /B 1
save those files
4. open up your MiFlash and try flashing again.
Oh by the way, if you're planning to use TWRP, use the one for Redmi Note 4 with MTK (Nikel), you won't be able to use official twrp-mido image.
Here's the reference:
https://forum.xda-developers.com/redmi-note-4/help/flashing-twrp-redmi-note-4x-failure-t3615871
good luck
Click to expand...
Click to collapse
It worked. Thanks !!
ezraimanuel said:
Got my mi approval for unlock today and I got same problem as yours... here's what I did:
1. Be sure you have downloaded correct ROM (I'm using mido_global_images_V8.2.10.0.MCFMIDL_20170602.0000.00_6.0_global)
2. edit your *.bat files in your ROM folder, probably these:
flash_all.bat
flash_all_except_storage.bat
flash_all_lock.bat
flash_all_lock_crc.bat
flash_factory.bat
3. comment out the first 2 lines in those files (product check related):
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || echo Missmatching image and device
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || exit /B 1
save those files
4. open up your MiFlash and try flashing again.
Oh by the way, if you're planning to use TWRP, use the one for Redmi Note 4 with MTK (Nikel), you won't be able to use official twrp-mido image.
Here's the reference:
https://forum.xda-developers.com/redmi-note-4/help/flashing-twrp-redmi-note-4x-failure-t3615871
good luck
Click to expand...
Click to collapse
Worked for me. Thank you!! Truly thought I bricked my phone.
Beast gamer said:
Hello..
i have redmi note 4 and i am installing stock rom but it says that rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || echo Missmatching image and device
Now waht i do
can you please explain me.
pls
Thanks
Click to expand...
Click to collapse
Had this problem, outcommented the variantchecks (in the flash_all_except_data.bat and other 3 bat files). Now Miflash prompts not this but subsequent [] problem :
$for /F "tokens=2 delims=: "%in (fastboot -s [MY 7 char-DEVICENO.] getvar anti 2>&1
Probably I am apart from your problem, as Fastboot commands give no responds: for e.g.
fastboot getvar boot-mode, answer is:
< waiting for any device >
Only "success" I had:
fastboot reboot
but still in bootloop
Any help appreciated, I am a beginner...
ezraimanuel said:
Got my mi approval for unlock today and I got same problem as yours... here's what I did:
1. Be sure you have downloaded correct ROM (I'm using mido_global_images_V8.2.10.0.MCFMIDL_20170602.0000.00_6.0_global)
2. edit your *.bat files in your ROM folder, probably these:
flash_all.bat
flash_all_except_storage.bat
flash_all_lock.bat
flash_all_lock_crc.bat
flash_factory.bat
3. comment out the first 2 lines in those files (product check related):
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || echo Missmatching image and device
rem fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *mido" || exit /B 1
save those files
4. open up your MiFlash and try flashing again.
Oh by the way, if you're planning to use TWRP, use the one for Redmi Note 4 with MTK (Nikel), you won't be able to use official twrp-mido image.
Here's the reference:
https://forum.xda-developers.com/redmi-note-4/help/flashing-twrp-redmi-note-4x-failure-t3615871
good luck
Click to expand...
Click to collapse
I didn't understand no -3 point????
i am flashing redmi note 5 and i am also getting mismatch error. i tried the following method but now it is displaying 'flash xbl error' and partition table doesn't exist.
any help will be highly appreciated
Shadow505 said:
For anyone still looking for help on this:
There can be issues with flashing (and possibly even unlocking etc. in some cases) on Ryzen powered computers. I've been troubleshooting for a pretty long time on this issue and one of the mods on the Xiaomi Community discord server (unofficial) told me to try on an Intel powered computer
To my surprise, firing up Xiaomi ADB Fastboot tools on an Intel laptop worked and the recovery image flashed
If you just happen to be on a Ryzen processor, give Intel one a shot (nothing against AMD by the way, been using it for a while now. Except for some issues with the graphics drivers, but that's a different story)
One more note: This happened on a tulip (Redmi Note 6 Pro) in my case. I've flashed a fastboot ROM on raphael (Redmi K20 Pro / Mi 9T Pro) succesfully on my Ryzen powered PC before. This might not be always the case.
Thanks for reading and hope this can help at least someone as it definitely saved my ass from EDL flashing
Click to expand...
Click to collapse
I created an account on xda just to thank you.
this really saved my phone, I have been spending well over 12 hours trying to get this fixed
It worked as soon as i switched over to my intel powered laptop
THANK YOU
Shadow505 said:
For anyone still looking for help on this:
There can be issues with flashing (and possibly even unlocking etc. in some cases) on Ryzen powered computers. I've been troubleshooting for a pretty long time on this issue and one of the mods on the Xiaomi Community discord server (unofficial) told me to try on an Intel powered computer
To my surprise, firing up Xiaomi ADB Fastboot tools on an Intel laptop worked and the recovery image flashed
If you just happen to be on a Ryzen processor, give Intel one a shot (nothing against AMD by the way, been using it for a while now. Except for some issues with the graphics drivers, but that's a different story)
One more note: This happened on a tulip (Redmi Note 6 Pro) in my case. I've flashed a fastboot ROM on raphael (Redmi K20 Pro / Mi 9T Pro) succesfully on my Ryzen powered PC before. This might not be always the case.
Thanks for reading and hope this can help at least someone as it definitely saved my ass from EDL flashing
Click to expand...
Click to collapse
I have my ryzen and this is the solution after few hour struggling with this error. Thank a bunch!
Yep, I've just been struggling to install stock 'n' lock via miflash, and it turned out the problem was my Ryzen CPU. Have dug out an old intel laptop, which doesn't connect to wifi, the battery is dead, and half the screen isn't viewable, but it does manage to install firmware via miflash. Thanks so much for this thread, which probably saved me several hours of fiddling.
I have a fairly odd device, 22" acer aa3-600 (x86 intel not ARM), and it doesn't support adb or fastboot over usb (wtf right?) but does support adb and fastboot over ethernet. I can connect fine via tcp during adb, but with little sign networking is even working on the bootloader screen i can't seem to communicate during fastboot, meaning i can't unlock the bootloader. Incredibly frustrating.
There is *one* piece that makes me think networking is enabled, which is what keeps me going at this point
This pdf mentions pinging the device and then -t pinging it (page 5 second table under fastboot) - https://01.org/sites/default/files/documentation/android_4.x_build_image_guide.pdf , which works.
i couldn't believe it when his ip was set as the same that my AIO *says* it will set for usb debugging (it doesn't), and after i set my pc to the same ip as his and connected directly i could ping! i was shocked, and this alone keeps me going.
Anyone have any thoughts?
Most of the resources i can find are official or formal release doc stuff, see below.
https://sourceforge.net/p/android-x86/system_core/ci/nougat-x86/tree/fastboot/fastboot_protocol.txt
and other bits in the release doc for x86 - https://sourceforge.net/p/android-x86/system_core/ci/nougat-x86/tree/fastboot/ - like this list of commands
https://android.googlesource.com/platform/system/core/+/master/fastboot/README.md
Code:
> fprintf(stderr,
/* 1234567890123456789012345678901234567890123456789012345678901234567890123456 */
"usage: fastboot [ <option> ] <command>\n"
"\n"
"commands:\n"
" update <filename> Reflash device from update.zip.\n"
" Sets the flashed slot as active.\n"
" flashall Flash boot, system, vendor, and --\n"
" if found -- recovery. If the device\n"
" supports slots, the slot that has\n"
" been flashed to is set as active.\n"
" Secondary images may be flashed to\n"
" an inactive slot.\n"
" flash <partition> [ <filename> ] Write a file to a flash partition.\n"
" flashing lock Locks the device. Prevents flashing.\n"
" flashing unlock Unlocks the device. Allows flashing\n"
" any partition except\n"
" bootloader-related partitions.\n"
" flashing lock_critical Prevents flashing bootloader-related\n"
" partitions.\n"
" flashing unlock_critical Enables flashing bootloader-related\n"
" partitions.\n"
" flashing get_unlock_ability Queries bootloader to see if the\n"
" device is unlocked.\n"
" flashing get_unlock_bootloader_nonce Queries the bootloader to get the\n"
" unlock nonce.\n"
" flashing unlock_bootloader <request> Issue unlock bootloader using request.\n"
" flashing lock_bootloader Locks the bootloader to prevent\n"
" bootloader version rollback.\n"
" erase <partition> Erase a flash partition.\n"
" format[:[<fs type>][:[<size>]] <partition>\n"
" Format a flash partition. Can\n"
" override the fs type and/or size\n"
" the bootloader reports.\n"
" getvar <variable> Display a bootloader variable.\n"
" set_active <slot> Sets the active slot. If slots are\n"
" not supported, this does nothing.\n"
" boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.\n"
" flash:raw boot <kernel> [ <ramdisk> [ <second> ] ]\n"
" Create bootimage and flash it.\n"
" devices [-l] List all connected devices [with\n"
" device paths].\n"
" continue Continue with autoboot.\n"
" reboot [bootloader] Reboot device [into bootloader].\n"
" reboot-bootloader Reboot device into bootloader.\n"
" help Show this help message.\n"
"\n"
"options:\n"
" -w Erase userdata and cache (and format\n"
" if supported by partition type).\n"
" -u Do not erase partition before\n"
" formatting.\n"
" -s <specific device> Specify a device. For USB, provide either\n"
" a serial number or path to device port.\n"
" For ethernet, provide an address in the\n"
" form <protocol>:<hostname>[:port] where\n"
" <protocol> is either tcp or udp.\n"
" -p <product> Specify product name.\n"
" -c <cmdline> Override kernel commandline.\n"
" -i <vendor id> Specify a custom USB vendor id.\n"
" -b, --base <base_addr> Specify a custom kernel base\n"
" address (default: 0x10000000).\n"
" --kernel-offset Specify a custom kernel offset.\n"
" (default: 0x00008000)\n"
" --ramdisk-offset Specify a custom ramdisk offset.\n"
" (default: 0x01000000)\n"
" --tags-offset Specify a custom tags offset.\n"
" (default: 0x00000100)\n"
" -n, --page-size <page size> Specify the nand page size\n"
" (default: 2048).\n"
" -S <size>[K|M|G] Automatically sparse files greater\n"
" than 'size'. 0 to disable.\n"
" --slot <slot> Specify slot name to be used if the\n"
" device supports slots. All operations\n"
" on partitions that support slots will\n"
" be done on the slot specified.\n"
" 'all' can be given to refer to all slots.\n"
" 'other' can be given to refer to a\n"
" non-current slot. If this flag is not\n"
" used, slotted partitions will default\n"
" to the current active slot.\n"
" -a, --set-active[=<slot>] Sets the active slot. If no slot is\n"
" provided, this will default to the value\n"
" given by --slot. If slots are not\n"
" supported, this sets the current slot\n"
" to be active. This will run after all\n"
" non-reboot commands.\n"
" --skip-secondary Will not flash secondary slots when\n"
" performing a flashall or update. This\n"
" will preserve data on other slots.\n"
#if !defined(_WIN32)
" --wipe-and-use-fbe On devices which support it,\n"
" erase userdata and cache, and\n"
" enable file-based encryption\n"
#endif
" --unbuffered Do not buffer input or output.\n"
" --version Display version.\n"
" -h, --help show this message.\n"
I know you can use udp too - https://github.com/aosp-mirror/platform_system_core/commit/4601c978cad8b69e15ed63664ebb5dcf6aaf21b3
https://supportforums.cisco.com/t5/...oritizing-udp-over-tcp-using-qos/td-p/2379534
but i am having enough trouble as is. That said, if anyone thinks this is the best option please let me know.
I am also open to any other option out there. I have the droidboot bootloader on my desktop, not that i know what to do with it. Or should i try to unlock it some other way? Could i somehow enable fastboot over usb even though my device doesn't support it? An app maybe? Bootloader screen is looking for installer.cmd file, maybe that? What is that?
Any help would be seriously appreciated
I have the Acer Iconia A1-830, which also utilizes the droidboot bootloader but fastboot works fine (with some minor tweaks, you can even use adb!). Can you try to run adb reboot fastboot when in adb mode and see what that does? Good luck
I can boot in to adb and fastboot fine, i just can't run any commands in fastboot through usb.
i'll try to be more succinct, as i still need some help if possible
I can ping my device in fastboot if i set host to 192.168.42.1 and my pc to 192.168.43.2, as outline in the pdf above, but that's it. No other fastboot commands register with the device. I can only use ethernet, per the device, and need some idea of what i need to do to be able to send fastboot commands.
Anyone? Pretty pretty please??
phishphish said:
i'll try to be more succinct, as i still need some help if possible
I can ping my device in fastboot if i set host to 192.168.42.1 and my pc to 192.168.43.2, as outline in the pdf above, but that's it. No other fastboot commands register with the device. I can only use ethernet, per the device, and need some idea of what i need to do to be able to send fastboot commands.
Anyone? Pretty pretty please??
Click to expand...
Click to collapse
I want to try and help you, however I don't have all the time in the world. What is it that you are trying to do with the device? Flash a rom or unbrick? Or is it just a "I wanna see if it's working" thing?
i can't seem to communicate during fastboot, meaning i can't unlock the bootloader.
Click to expand...
Click to collapse
I'm not asking specifically just you, but yeah, thanks
Good day,
I need advice. I have a Mi 10 and until recently I had V12.0.6.0.QJBEUXM on Android 10, my phone offered me an update to android 11 V12.2.4.0.RJBEUXM. Some things stopped working so I then found out according to Google that this is a beta version (I probably had my updates enabled, my stupidity) anyway when I wanted to get V12.0.6.0.QJBEUXM back to my phone so I'm stuck on the fastboot screen. I had the bootloader locked, but when I found out that it was a beta version, I unlocked the bootloader and wanted to load back the previous version with android 10 via flash, but the flash tool throws me one error after another, first "sparecrclist error" and then " missmatching image and device "which is bull**** because I have a 100% correct version. I have the bootloader unlocked, but I can't flash any rom on it beacuse mi flast tool throw erros. Can you advise what to do with it?
Solution to Miflash crclist error / failed.
1: Download OFFICIAL MIUI ROM and unzip this ROM to any folder.
2: Open this folder , you'll find 3 files named "flash_all.bat""flash_all_except_storage.bat""flash_all_lock.bat" , create a copy and back them up to another folder for safe.
3: Open and edit the file according to your needs (for example , you need to edit flash_all.bat if you want your phone leaves no files.), Find the listed code:
fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @ECHO "Flash sparsecrclist error" && exit /B 1
Add "REM"before the two lines , like this:
REM fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
REM fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @ECHO "Flash sparsecrclist error" && exit /B 1
Save and exit after this done.
4: Launch Miflash , flash this ROM like usual
if it shows "FAILED" after flash complete and your phone exit fastboot and go dark , congratulations ! you have successfully flashed this ROM !I can't send a connection, just look at it
Problem solved, i have to flash twrp and install Xiaomi.eu rom then via twrp flash global rom with android 10 a then reset and flash via mi flash and lock bootloader.