Related
Hi All,
I am trying to bypass the google activation. downgraded to RC29 .I typed this in the device with no sim card <enter>setprop persist.service.adb.enable 1<enter>. but when i connect my device using usb port . i see this in the syslogs
usb 1-1.1: new high speed USB device using ehci_hcd and address 29
[ 4611.770659] usb 1-1.1: device descriptor read/64, error -71
[ 4611.958338] usb 1-1.1: device descriptor read/64, error -71
[ 4612.133841] usb 1-1.1: new high speed USB device using ehci_hcd and address 30
[ 4612.217770] usb 1-1.1: device descriptor read/64, error -71
[ 4612.405259] usb 1-1.1: device descriptor read/64, error -71
[ 4612.581176] usb 1-1.1: new high speed USB device using ehci_hcd and address 31
[ 4612.996080] usb 1-1.1: device not accepting address 31, error -71
[ 4613.067744] usb 1-1.1: new high speed USB device using ehci_hcd and address 32
[ 4613.482836] usb 1-1.1: device not accepting address 32, error -71
[ 4613.483094] hub 1-1:1.0: unable to enumerate USB device on port 1
and when i did lsusb htc dream is not listed . please tell me what is wrong with the device. Thanks in Advance.
note: <enter>reboot<enter> worked
do you have adb drivers installed? when did you do lsusb? normally to check you open cmd and go to sdk/platform-tools directory and type 'adb devices'
using ubuntu
ldrifta said:
do you have adb drivers installed? when did you do lsusb? normally to check you open cmd and go to sdk/platform-tools directory and type 'adb devices'
Click to expand...
Click to collapse
Hi
I am using ubuntu 10.10 , so i assumed that usb drivers come with the distro.
adb devices
list nothing even when the device is connected.
Thanks
go here... http://developer.android.com/sdk/index.html
and do some reading... should help you get started
Most likely your phone's vendor and device keys need to be added to the udev rules.
Sent from my Gingerbread on Dream using XDA App
usb cable issue
Sorry guys its my bad, i was using a micro usb cable instead of the usb connector that came with G1. now i am able to connected to the device using adb shell. Sorry again. Thanks to all
so much,but,the next is good
i use a regular micro usb cable and it works fine... but some may be different in some as o cant garuntee anything
Hi,
my TouchPad seems to be in a boot loop, or bootloader is corrupt, dunno.
I am using linux, btw.
This happend:
I did install CM7 since after the first alpha release and upgraded each release without a hassle. I had both OS parallel for a long time dual booting regulary, but using Android more and more often.
Since Christmas then I havent even been in WebOs.
Two weeks ago, I started WebOS again, and got a message to update my software.
I clicked yes.
Then it took an hour or so and the Pad rebooted ..... and got stuck - never came up again since then.
It just stays a bit where the round HP sign comes up, and reboot after a minute or so.
here is the dmesg:
Code:
[37240.196350] usb 2-1.3: new high-speed USB device number 8 using ehci_hcd
[37240.317306] usb 2-1.3: New USB device found, idVendor=0830, idProduct=8070
[37240.317318] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[37240.317325] usb 2-1.3: Product: Palm
[37240.317330] usb 2-1.3: Manufacturer: bootie
[37522.496211] usb 2-1.3: USB disconnect, device number 8
[37552.413914] usb 2-1.3: new high-speed USB device number 9 using ehci_hcd
[37552.534865] usb 2-1.3: New USB device found, idVendor=0830, idProduct=8070
[37552.534877] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[37552.534884] usb 2-1.3: Product: Palm
[37552.534889] usb 2-1.3: Manufacturer: bootie
[37579.309737] usb 2-1.3: USB disconnect, device number 9
I tried a hard reset, and same same happens again:
It resets, the hp logo shows up, then after a minute it reboots again.
So after this I tried to use memboot. but I can't get even into usb mode!
Holding Volume up + Power does exactly nothing! Novacom doesn't recognize my TouchPad.
Holding Volume down + Home + Power does nothing as well - despite throwing this into dmesg:
Code:
[37197.120415] usb 2-1.3: new high-speed USB device number 7 using ehci_hcd
[37197.240971] usb 2-1.3: New USB device found, idVendor=05c6, idProduct=9008
[37197.240977] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[37197.240981] usb 2-1.3: Product: QHSUSB_DLOAD
[37197.240984] usb 2-1.3: Manufacturer: Qualcomm CDMA Technologies MSM
[37197.241877] qcserial 2-1.3:1.0: Qualcomm USB modem converter detected
[37197.242395] usb 2-1.3: Qualcomm USB modem converter now attached to ttyUSB0
[37238.172562] usb 2-1.3: USB disconnect, device number 7
[37238.173155] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[37238.173359] qcserial 2-1.3:1.0: device disconnected
btw, webdoctor certainly doesnt recognize my device, neither in linux nor in windows 7 - nonetheless it shows up in explorer as palm device without device drivers installed (yes I did install novacom drivers in Windows as well as in linux).
What to do now? Any hints?
Do the reset again then when it starts to reset hold volume up only.
hopefully that should be you in webos recovery.
Then you can try to flash moboot again because the update does break moboot.
thanks....
had to do it three times, then it worked out!! maybe my vol key is lose?
Anyway, you made my week!! :-D
Q&A for [UNBRICK][BETA] HTC Unbricking Project
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Help!!!!!
Help!
[email protected]:~/Загрузки$ sudo ./revive.sh
HTC Unbricking Project M7_UL 0.6beta
Detecting bricked device..
Device can't be found, check connections. Aborting
[email protected]:~/Загрузки$
demice84 said:
Help!
[email protected]:~/Загрузки$ sudo ./revive.sh
HTC Unbricking Project M7_UL 0.6beta
Detecting bricked device..
Device can't be found, check connections. Aborting
[email protected]:~/Загрузки$
Click to expand...
Click to collapse
Did you follow the procedure notes in Post #3?
Are you using a USB 2 port?
Can you change cables or ports?
majmoz said:
Did you follow the procedure notes in Post #3?
Are you using a USB 2 port?
Can you change cables or ports?
Click to expand...
Click to collapse
Yes everything corresponds
I entered watch -n ,1 lsusb:
Bus 002 Device 048: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 034: ID 24ae:2001
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 064e:a101 Suyin Corp. Acer CrystalEye Webcam
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
I entered sudo dmesg -c:
[12438.236833] usb 2-4: USB disconnect, device number 48
[12438.237222] zte_ev ttyUSB0: zte_ev converter now disconnected from ttyUSB0
[12438.237260] zte_ev 2-4:1.0: device disconnected
[12441.688302] usb 2-3: new high-speed USB device number 49 using ehci-pci
[12441.832849] usb 2-3: New USB device found, idVendor=05c6, idProduct=f006
[12441.832861] usb 2-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[12441.845421] hid-generic 0003:05C6:F006.00EB: hiddev0,hidraw2: USB HID v1.11 Device [HID 05c6:f006] on usb-0000:00:1d.7-3/input0
[12455.098456] usb 2-3: USB disconnect, device number 49
[12455.368161] usb 2-3: new high-speed USB device number 50 using ehci-pci
[12455.500812] usb 2-3: New USB device found, idVendor=05c6, idProduct=9008
[12455.500816] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[12455.500819] usb 2-3: Product: QHSUSB_DLOAD
[12455.500822] usb 2-3: Manufacturer: Qualcomm CDMA Technologies MSM
[12455.501114] zte_ev 2-3:1.0: zte_ev converter detected
[12455.501236] usb 2-3: zte_ev converter now attached to ttyUSB0
[12485.284801] usb 2-3: USB disconnect, device number 50
[12485.285165] zte_ev ttyUSB0: zte_ev converter now disconnected from ttyUSB0
[12485.285201] zte_ev 2-3:1.0: device disconnected
[12487.488074] usb 2-4: new high-speed USB device number 51 using ehci-pci
[12487.633912] usb 2-4: New USB device found, idVendor=05c6, idProduct=f006
[12487.633925] usb 2-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[12487.646404] hid-generic 0003:05C6:F006.00EC: hiddev0,hidraw2: USB HID v1.11 Device [HID 05c6:f006] on usb-0000:00:1d.7-4/input0
[12500.978946] usb 2-4: USB disconnect, device number 51
[12501.248160] usb 2-4: new high-speed USB device number 52 using ehci-pci
[12501.381149] usb 2-4: New USB device found, idVendor=05c6, idProduct=9008
[12501.381162] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[12501.381170] usb 2-4: Product: QHSUSB_DLOAD
[12501.381177] usb 2-4: Manufacturer: Qualcomm CDMA Technologies MSM
[12501.381735] zte_ev 2-4:1.0: zte_ev converter detected
[12501.382362] usb 2-4: zte_ev converter now attached to ttyUSB0
demice84 said:
Yes everything corresponds
Click to expand...
Click to collapse
Did you check the MD5 of the 32bit HTC One download?
Code:
MD5: [B]c9b8c0ea1700edfda1d69a2491e59aa5[/B]
Are you using the 32bit Linux? It was reported in the thread that 64bit was causing issues.
If you haven't already, I would go back and re-read the the first three post to make sure I didn't forget something. Then, I would read the last eight to ten pages of the thread to see if someone else had a similar experience.
@dexter93 can you help demice84, I just don't have the experience with your process. Thanks!
htc one m7 qususb_dload
i tried the method with Ubuntu 12.04 32 bit system and the device is not detected at all
although i tried to boot up the phone with my hand
kindly advice
Solved
Hi,
I was having the wifi not turning on issue. My phone was rooted so no warranty. Therefore, I started flashing all sort of different roms, both stock as well as custom ones (I understand a little bit of it) and all was ok. Then I flashed the Developer Edition and my phone was completely bricked. No LED, no charging not turning on nothing. I searched all over and everyone is saying: Dead no solution only Jtag or HTC can solve it. I kept on thinking...but somehow my computer still recognizes the phone so something must be possible. So I didnt give up and kept searching. Then I found your post. I run your file and yes...it worked. My phone came back alive! So thank you so much. I am not able to donate at this moment, but did want to let you know that your mehtod worked for me!
Wifi problem still exists, ie will not turn on. But other than that I have a working phone again.
Thanks and all the best.
Successful unbricking
I just want to post and say a mega thank you dexter93 for this process. It unbricked my HTC one M7 without any issues.
FF
Bricked htc one m7
hello can any one help me here?
the unbrick script doesnt detect it
[email protected]:~/Downloads$ sudo ./revive.sh
HTC Unbricking Project M7_UL 0.6beta
Detecting bricked device..
Device can't be found, check connections. Aborting
[email protected]:~/Downloads$ lsusb
Bus 001 Device 006: ID 055d:3021 Samsung Electro-Mechanics Co.
Bus 001 Device 021: ID 05c6:f006 Qualcomm, Inc.
Bus 001 Device 003: ID 0951:1607 Kingston Technology DataTraveler 100
Bus 001 Device 002: ID 0bda:8172 Realtek Semiconductor Corp. RTL8191SU 802.11n WLAN Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 1c4f:0003 SiGma Micro HID controller
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 046d:c311 Logitech, Inc. Y-UF49 [Internet Pro Keyboard]
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[email protected]:~/Downloads$
the brick happened when i installed cyanogenmod one click installer... it booted up correctlt then it received 2 updates ... the second one the phone never turned on or charged again
when i do a dmesg command in terminal i get many logs like this.... the phone connects and disconnects from the pc just like it does in a windows pc
evice [HID 05c6:f006] on usb-0000:00:1d.7-6/input0
[ 1007.938761] usb 1-6: USB disconnect, device number 69
[ 1008.328074] usb 1-6: new high-speed USB device number 70 using ehci-pci
[ 1008.473962] usb 1-6: New USB device found, idVendor=05c6, idProduct=f006
[ 1008.473973] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1008.486244] hid-generic 0003:05C6:F006.0043: hiddev0,hidraw3: USB HID v1.11 Device [HID 05c6:f006] on usb-0000:00:1d.7-6/input0
[ 1011.857415] usb 1-6: USB disconnect, device number 70
[ 1012.244093] usb 1-6: new high-speed USB device number 71 using ehci-pci
[ 1012.389460] usb 1-6: New USB device found, idVendor=05c6, idProduct=f006
[ 1012.389471] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1012.401894] hid-generic 0003:05C6:F006.0044: hiddev0,hidraw3: USB HID v1.11 Device [HID 05c6:f006] on usb-0000:00:1d.7-6/input0
[email protected]:~/Downloads$
Hope you can help me please
I have this issue what can i do plz help
Help please!
i think bricked my HTC One 801n (M7_UL)
Ubuntu (14.10) terminal writes the dmesg command.
[5955.455843] usb 1-3: USB disconnect, device number 3
[5958.773671] usb 1-2: new high speed USB device using ehci-pci Number 4
[5958.912343] usb 1-2: New USB device found, idVendor = 0bb4, idProduct = 0ff0
[5958.912356] usb 1-2: New USB device strings: Mfr = 1, Product = 2, serialNumber = 3
[5958.912363] usb 1-2: Product: Android 1.0
[5958.912369] usb 1-2: Manufacturer: htc, Inc.
[5958.912374] usb 1-2: serialNumber: SH35SW905694
my phone is completely different show than the others. Works with fastboot, but not the recovery. Bloom in red text below, Active cmdline overflow! (1028 Bytes). The project can be improved with this phone? If so, how? Volume down + power button does not work. Volume up + power button either. only the Bootloader comes into fastboot and nothing else. Recovery had flash. It does not work. Any other ideas? I would be grateful! Sorry for the rough speech, but I can not speak English. I use a translator!
szoszi said:
i think bricked my HTC One 801n (M7_UL)
Ubuntu (14.10) terminal writes the dmesg command.
[5955.455843] usb 1-3: USB disconnect, device number 3
[5958.773671] usb 1-2: new high speed USB device using ehci-pci Number 4
[5958.912343] usb 1-2: New USB device found, idVendor = 0bb4, idProduct = 0ff0
[5958.912356] usb 1-2: New USB device strings: Mfr = 1, Product = 2, serialNumber = 3
[5958.912363] usb 1-2: Product: Android 1.0
[5958.912369] usb 1-2: Manufacturer: htc, Inc.
[5958.912374] usb 1-2: serialNumber: SH35SW905694
my phone is completely different show than the others. Works with fastboot, but not the recovery. Bloom in red text below, Active cmdline overflow! (1028 Bytes). The project can be improved with this phone? If so, how? Volume down + power button does not work. Volume up + power button either. only the Bootloader comes into fastboot and nothing else. Recovery had flash. It does not work. Any other ideas? I would be grateful! Sorry for the rough speech, but I can not speak English. I use a translator!
Click to expand...
Click to collapse
Try here >> http://forum.xda-developers.com/sho...ighlight=active+cmdline+overflow#post52367879
Thanks
Thanks!
thanks a lot for this. Worked like a charm. After upgrading my firmware from 1.29.1540.17 to 5.11.1540.9 I was stuck in this mode where the phone wouldn't power up. This tool helped me bring it back to life. Thanks!!
help a poor noob
hei i'm pretty new on Ubuntu and i would ask if someone could have some spare time to help this poor noob i've created the live usb with ubuntu but ... as i said i'm new and ubuntu beats me Thank you
Problems extracting tar files
Guys, I am having problems extracting the emmc_recover_v4a1.tar.gz. Im running ubuntu-14.04.1-desktop-amd64
janfar said:
Guys, I am having problems extracting the emmc_recover_v4a1.tar.gz. Im running ubuntu-14.04.1-desktop-amd64
Click to expand...
Click to collapse
In the same directory, type the following in your terminal emulator.
Code:
/path/to/files $ tar -xzvf emmc*
Edit: note to type what follows the $ above, your shell should show the working path and a $ sign for user accounts and a # if you're signed in as root (same as on Android).
If you get an error you probably need to redownload (e.g. CRC error). You can check the md5 of the download using the md5sum command to confirm if the download is good/bad.
genseng said:
In the same directory, type the following in your terminal emulator.
Code:
/path/to/files $ tar -xzvf emmc*
Edit: note to type what follows the $ above, your shell should show the working path and a $ sign for user accounts and a # if you're signed in as root (same as on Android).
If you get an error you probably need to redownload (e.g. CRC error). You can check the md5 of the download using the md5sum command to confirm if the download is good/bad.
Click to expand...
Click to collapse
I have tried all the codes available. I dont know if is an issue with the download as I am having to download it on a windows 7 machine and then transfer it to the Ubuntu machine using a pendrive. Ubuntu machine does not have internet.
janfar said:
I have tried all the codes available...
Click to expand...
Click to collapse
You lost me...
Ubuntu will have the md5sum program built in. After transferring the file to the Ubuntu system, generate an md5sum and compare it to the one on the download page. If it matches then it worked.
genseng said:
You lost me...
Ubuntu will have the md5sum program built in. After transferring the file to the Ubuntu system, generate an md5sum and compare it to the one on the download page. If it matches then it worked.
Click to expand...
Click to collapse
Lol... i meant I tried all the untarring codes I could find on the internet including the one you asked me to try.
I will try to md5sum and see if it gives the right value. How do I run that code?
So I managed to run the md5sum and the number does not match what is on the DL page.
Hi
I was trying to unlock bootloader of my honor 3c (H30-U10) via SP Flash Tools. When I was connecting my phone without battery to PC via USB after clicking "Download" Button, the device kept vibrating and the connection got disconnected and connected every 3 seconds. The Screen was off during all of this process.
Here is my SP Flash Tool log:
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 2000
device pid = 2000
com portName is: /dev/ttyACM0
Total wait time = -1467879144.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
COM port is open. Trying to sync with the target...
Failed to Connect DA: S_BROM_DOWNLOAD_DA_FAIL
Disconnect!
BROM Exception! ( BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (2004)
[H/W] Fail to download DA to baseband chip's internal SRAM!
[HINT]:
1. There's an cable communication problem between FlashTool and BootROM.
2. Target might be shutdown unexpectedly or target lost power supply.
[ACTION]
1. Try again.
2. Proceed H/W checking in download cable and target side com port.
3. Monitor if power-drop occured in target side.)((ConnectDA,../../../flashtool/Conn/Connection.cpp,127))
and this is my dmesg log:
Code:
[ 3440.213018] usb 1-1.2: new high-speed USB device number 55 using ehci-pci
[ 3440.307101] usb 1-1.2: New USB device found, idVendor=0e8d, idProduct=2000
[ 3440.307104] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3440.307105] usb 1-1.2: Product: MT65xx Preloader
[ 3440.307106] usb 1-1.2: Manufacturer: MediaTek
[ 3440.369300] cdc_acm 1-1.2:1.1: ttyACM1: USB ACM device
[ 3443.146921] usb 1-1.2: USB disconnect, device number 55
[ 3560.113932] usb 1-1.2: new high-speed USB device number 56 using ehci-pci
[ 3560.209002] usb 1-1.2: New USB device found, idVendor=0e8d, idProduct=2000
[ 3560.209005] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3560.209007] usb 1-1.2: Product: MT65xx Preloader
[ 3560.209008] usb 1-1.2: Manufacturer: MediaTek
[ 3560.271453] cdc_acm 1-1.2:1.1: ttyACM0: USB ACM device
[ 3563.563312] usb 1-1.2: USB disconnect, device number 56.
.
.
.
[ 3589.764652] usb 1-1.2: new high-speed USB device number 62 using ehci-pci
[ 3589.859355] usb 1-1.2: New USB device found, idVendor=0e8d, idProduct=2000
[ 3589.859359] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3589.859361] usb 1-1.2: Product: MT65xx Preloader
[ 3589.859363] usb 1-1.2: Manufacturer: MediaTek
[ 3589.921646] cdc_acm 1-1.2:1.1: ttyACM0: USB ACM device
[ 3590.138898] usb 1-1.2: USB disconnect, device number 62
I also tried this with windows with all drivers installed, but I got the exact same result.
After a bunch of tries, now my phone doesn't even turns on. When I press power button with battery inserted, It vibrates every 20 seconds and the screen is always off, too. Connecting it to computer makes the same behavior described above.
So… Is there any way to make it fix? Since I can not access to fastboot mode and SP Flash Tools is not working either?
danialbehzadi said:
Hi
I was trying to unlock bootloader of my honor 3c (H30-U10) via SP Flash Tools. When I was connecting my phone without battery to PC via USB after clicking "Download" Button, the device kept vibrating and the connection got disconnected and connected every 3 seconds. The Screen was off during all of this process.
Here is my SP Flash Tool log:
and this is my dmesg log:
I also tried this with windows with all drivers installed, but I got the exact same result.
After a bunch of tries, now my phone doesn't even turns on. When I press power button with battery inserted, It vibrates every 20 seconds and the screen is always off, too. Connecting it to computer makes the same behavior described above.
Soâ?¦ Is there any way to make it fix? Since I can not access to fastboot mode and SP Flash Tools is not working either?
Click to expand...
Click to collapse
Do adb recognize your phone?!
Not at all. I took my device to Huawei center and they told me it's dead. So, I bought a new phone.
DON'T BY FROM HUAWEI!
danialbehzadi said:
Not at all. I took my device to Huawei center and they told me it's dead. So, I bought a new phone.
DON'T BY FROM HUAWEI!
Click to expand...
Click to collapse
Ahhh too bad :/
The same thing happened to my Samsung , i overcharged it via an unstable source, and the power IC was damaged, if i slid the battery in it would just keep vibrating and flash light turned on, it costed me PKR Rs.1200(USD.12$) to repair it......
Try SP Flashtool again, but with your battery in. Flashing recovery might be your best bet
Fixed your device?
hassanjavaid8181 said:
Fixed your device?
Click to expand...
Click to collapse
No. Threw it away!
danialbehzadi said:
No. Threw it away!
Click to expand...
Click to collapse
thats another way to fix issue
Unfortunately, I deleted all partitions with 'bkerler/mtkclient' for trying to remove MI Account Verification.
Now the phone looks dead, no turning on, no fastboot mode, linux and windows don't see the phone at all.
Question : is now the TRASH the only remaining way or there is still a chance to rescue it ????
Greets
Oh.
Were you doing this on a Linux or Windows box?
Can you see in USB 0e8d/0003 or 0e8d/2000?
Hi, thanks for your help !
I operated in ubuntu 22.04 - software mtkclient 2.0 (github bkerler/mtkclient)
under ubuntu 22.04 now with command 'adb devices' none devices comes displayed,
under windows 10 os if I attach the phone via usb, the sysytem it ring in and out in loop for a plugged devices but no memory comes out to be used for storing files,
It seems really tuff this time, I am not optimistic !
Yes, I see many, probably for each partitions I deleted ?
Result with command lsusb :
Code:
lsusb
Bus 003 Device 081: ID 0e8d:0003 MediaTek Inc. MT6227 phone
Then with command dmesg | grep usb :
Code:
sudo dmesg | grep usb
...........
[ 1197.853581] usb 3-2: USB disconnect, device number 12
[ 1198.700237] usb 3-2: new high-speed USB device number 13 using xhci_hcd
[ 1198.848490] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1198.848497] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1203.368234] usb 3-2: USB disconnect, device number 13
[ 1204.932401] usb 3-2: new high-speed USB device number 14 using xhci_hcd
[ 1205.080695] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1205.080700] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1209.603143] usb 3-2: USB disconnect, device number 14
[ 1211.172537] usb 3-2: new high-speed USB device number 15 using xhci_hcd
[ 1211.320794] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1211.320800] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1215.837599] usb 3-2: USB disconnect, device number 15
[ 1217.400686] usb 3-2: new high-speed USB device number 16 using xhci_hcd
[ 1217.548976] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1217.548983] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1222.071995] usb 3-2: USB disconnect, device number 16
[ 1223.636870] usb 3-2: new high-speed USB device number 17 using xhci_hcd
[ 1223.785130] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1223.785136] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1228.306519] usb 3-2: USB disconnect, device number 17
[ 1229.869015] usb 3-2: new high-speed USB device number 18 using xhci_hcd
[ 1230.017275] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1230.017281] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1234.540893] usb 3-2: USB disconnect, device number 18
[ 1236.993149] usb 3-2: new high-speed USB device number 20 using xhci_hcd
[ 1237.141447] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1237.141453] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1240.775464] usb 3-2: USB disconnect, device number 20
[ 1242.337280] usb 3-2: new high-speed USB device number 21 using xhci_hcd
[ 1242.485596] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1242.485603] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1247.009965] usb 3-2: USB disconnect, device number 21
[ 1283.686113] usb 3-2: new high-speed USB device number 22 using xhci_hcd
[ 1283.834401] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1283.834407] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1284.416216] usb 3-2: USB disconnect, device number 22
[ 1285.978136] usb 3-2: new high-speed USB device number 24 using xhci_hcd
[ 1286.130454] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1286.130461] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1290.650196] usb 3-2: USB disconnect, device number 24
[ 1292.214284] usb 3-2: new high-speed USB device number 25 using xhci_hcd
[ 1292.362624] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1292.362629] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1296.884820] usb 3-2: USB disconnect, device number 25
[ 1298.450407] usb 3-2: new high-speed USB device number 26 using xhci_hcd
[ 1298.598753] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1298.598759] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1303.119685] usb 3-2: USB disconnect, device number 26
[ 1304.682518] usb 3-2: new high-speed USB device number 27 using xhci_hcd
[ 1304.830755] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1304.830762] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1309.354308] usb 3-2: USB disconnect, device number 27
[ 1310.918632] usb 3-2: new high-speed USB device number 28 using xhci_hcd
[ 1311.066960] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1311.066966] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1315.588837] usb 3-2: USB disconnect, device number 28
[ 1317.150735] usb 3-2: new high-speed USB device number 29 using xhci_hcd
[ 1317.299028] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1317.299034] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1321.822984] usb 3-2: USB disconnect, device number 29
[ 1344.423165] usb 3-2: new high-speed USB device number 30 using xhci_hcd
[ 1344.571498] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1344.571504] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1346.759523] usb 3-2: USB disconnect, device number 30
[ 1348.323227] usb 3-2: new high-speed USB device number 31 using xhci_hcd
[ 1348.471517] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1348.471524] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1352.993785] usb 3-2: USB disconnect, device number 31
[ 1354.555334] usb 3-2: new high-speed USB device number 32 using xhci_hcd
[ 1354.703604] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1354.703610] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1359.227829] usb 3-2: USB disconnect, device number 32
[ 1360.791422] usb 3-2: new high-speed USB device number 33 using xhci_hcd
[ 1360.939739] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1360.939745] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1365.462473] usb 3-2: USB disconnect, device number 33
[ 1367.031486] usb 3-2: new high-speed USB device number 34 using xhci_hcd
[ 1367.179797] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1367.179803] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1371.696458] usb 3-2: USB disconnect, device number 34
[ 1373.263582] usb 3-2: new high-speed USB device number 35 using xhci_hcd
[ 1373.411750] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1373.411752] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1377.930929] usb 3-2: USB disconnect, device number 35
[ 1379.511623] usb 3-2: new high-speed USB device number 36 using xhci_hcd
[ 1379.663980] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1379.663987] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1384.165640] usb 3-2: USB disconnect, device number 36
[ 1385.727770] usb 3-2: new high-speed USB device number 37 using xhci_hcd
[ 1385.880075] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1385.880080] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1390.400420] usb 3-2: USB disconnect, device number 37
[ 1391.967823] usb 3-2: new high-speed USB device number 38 using xhci_hcd
[ 1392.116001] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1392.116009] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1396.634523] usb 3-2: USB disconnect, device number 38
[ 1398.203924] usb 3-2: new high-speed USB device number 39 using xhci_hcd
[ 1398.356032] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1398.356035] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1402.868909] usb 3-2: USB disconnect, device number 39
[ 1404.432001] usb 3-2: new high-speed USB device number 40 using xhci_hcd
[ 1404.580140] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1404.580146] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1409.103339] usb 3-2: USB disconnect, device number 40
[ 1410.668091] usb 3-2: new high-speed USB device number 41 using xhci_hcd
[ 1410.816364] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1410.816369] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1415.337144] usb 3-2: USB disconnect, device number 41
[ 1416.900174] usb 3-2: new high-speed USB device number 42 using xhci_hcd
[ 1417.052290] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1417.052293] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1421.571611] usb 3-2: USB disconnect, device number 42
[ 1423.144205] usb 3-2: new high-speed USB device number 43 using xhci_hcd
[ 1423.296392] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1423.296399] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1427.805727] usb 3-2: USB disconnect, device number 43
[ 1429.372281] usb 3-2: new high-speed USB device number 44 using xhci_hcd
[ 1429.524540] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1429.524543] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1434.039545] usb 3-2: USB disconnect, device number 44
[ 1435.612359] usb 3-2: new high-speed USB device number 45 using xhci_hcd
[ 1435.761558] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1435.761562] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1440.273671] usb 3-2: USB disconnect, device number 45
[ 1441.848416] usb 3-2: new high-speed USB device number 46 using xhci_hcd
[ 1442.000604] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1442.000610] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1446.507555] usb 3-2: USB disconnect, device number 46
[ 1448.076511] usb 3-2: new high-speed USB device number 47 using xhci_hcd
[ 1448.224754] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1448.224757] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1452.742524] usb 3-2: USB disconnect, device number 47
[ 1454.304590] usb 3-2: new high-speed USB device number 48 using xhci_hcd
[ 1454.456747] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1454.456751] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
No, you're seeing one device thrashing.
If you're lucky you can catch it with MTK and write something.
(Sorry, I'm better with EDL than MTK. But I did just pull a boot with MTK.)
wich software can I use for this last try ?
magisk ?
mtkclient it seems to doesn't see the phone because adb see nothing.
Your software suggestion for this last try ?
thanks anyway
It can be that, actually the system recognize my device as MT6227 (before the trouble was appearing as MT6768/MT6769), and in this case, mtkclient don't recognize my device just because in its folder there is no such mt6227_payload.bin ???
Is there exist a mt6227_payload.bin ??? Is this a possible way ?
No, you're mixing up everything.
This is all MediaTek, nothing to do with ADB, fastboot or Magisk.
MediaTek has two bootloader modes, you're in one of them,
Your SoC is Mediatek MT6769Z. There is no specifice payload for MT6769.
If it's close enough to the MT6768, there is mt6768_payload.bin
Sorry, I don't know a lot.
I moved to windows 10, and there I had a fantastic discover, mtkclient there it's working.
Replaced Firmware and Vendor files downloaded from Original site : https://xiaomifirmwareupdater.com/archive/miui/merlin/
I did simply by 'write partition' command and then selecting then the VENDOR and FIRMWARE folders and let the app doing automatic replacement, it has completed !
Now I don't know how to move forward because the phone still doesn't turn on and in linux 'adb devices' not still recognize the device
I use to flash ROM with XIAOMI-TOOL MIFLASH for-Linux-by-IceMan, a great and easy program, but linux still doesn't give me access to the phone.
So the only way is in windows 10, wich App do you suggest me to use here ?
Is there a way to flash the ROM via mtkclient or the only way is SP Flash Tool ?
Thanks for your support
It will always have an option for rescue.
You need to flash the rom again using sp flash tool.
Just it.
in SP Flash Tool seems to be very tricky :
> I connect to MTKClient and let the device be recognized and connected
> then move to SP Flash tool, choice the UART COM Port I see recognized under MediaTek Port_V1633 (COM3 or 4)
But when I press download, I wait and get ERROR CODE :
ERROR : STATUS_ERR (0xC0010001)
or
ERROR : STATUS_BROM_CMD_STARTCMD_FAIL (0xC0060001)
where am i wrong ?
For what I see, I guess is a driver issue :
Considering to flash ROM via SPFlash Toll with support of MTKClient for auth bypass, wich USB Driver is required ? :
USBdk (required for MTKClient)
MediaTek SP Driver, LibUSB-Win32 are these required ???
Starting without auth-bypass trough MTKClient, with the only SP Flash Tool, I see the usb DEVICE (COM) switch on and off all the time...
need help
Is it possible ... , after installing a rom_engeneered, fixing NVram with modem-meta, replace original IMEI, and at least flashing an original_rom, ... to see android-desktop working back and skipping from that disgusting boot-loop-recovery ??
This question comes because I was able to fix this, but don't know how I did.
And now after so many test I did, some mistakes came, and I got back to 'zero-point', zero-zero-point (zio-cann!!!), and don't find the way back !!
want to see android's icons again ... boot-loop is bad !
heelllllllllll (ppppp)