I have an issue after flashing Aerom: Unfortunately I forgot to untick preloader when I flashed the rom. Installation went fine but device is not detected anymore by preloader driver. I tried different windows PCs without success. Flashing with SP Tools is not possible.
Bootloader (and ADB) mode working. Fastboot detects the device (in device manager it is listed as HTC Dream) In developer settings ADB and oem unlock are Activated. If I try to unlock boot loader via "fastboot oem unlock", I cannot select "Yes" (Volume up) on the device, only "No" (Volume Down)....not rooted, no custom recovery
How can I recover the right preloader or install custom recovery?
alohahe3000 said:
I have an issue after flashing Aerom: Unfortunately I forgot to untick preloader when I flashed the rom. Installation went fine but device is not detected anymore by preloader driver. I tried different windows PCs without success. Flashing with SP Tools is not possible.
Bootloader (and ADB) mode working. Fastboot detects the device (in device manager it is listed as HTC Dream) In developer settings ADB and oem unlock are Activated. If I try to unlock boot loader via "fastboot oem unlock", I cannot select "Yes" (Volume up) on the device, only "No" (Volume Down)....not rooted, no custom recovery
How can I recover the right preloader or install custom recovery?
Click to expand...
Click to collapse
Having just gone through the joy of unbricking my new P9000, after I didn't untick preloader when flashing, I've learned more today about using "meta-mode" with a MediaTek phone than I ever wanted to!
This is what debricked my phone. I wonder if this is of use to you? I make no claims it won't brick your device, so please read up on using this mode beforehand!!
Have Device Manager open to see what's going on with drivers
In SP Tools, load a stock ROM and tick *just* the Preloader. Hit Download.
Then hold down *only* the Volume + key (keep it pressed!) and plug the phone in. This bypasses the higher functions of the phone's memory and loads a basic driver - Mediatek USB VCOM will appear in the Device Manager under Ports. Keep Vol + pressed and it will flash the Preloader part of the memory.
With the Preloader flashed, the other parts of the phone (such as recovery) should be flashable, as hopefully the preloader driver will now load.
Brilliant, it´s working now. Thanks a lot.
[Solved] Bricked -Brom Protocol Error- during flashing recovery with SP Flash Tool
tldr; Doing nothing fixed my phone
In my case, I received a "Brom Protocol Error" during the flashing of a recovery with SP Flash Tools. Phone was bricked, didn't turn on anymore.
When connecting to my pc, I would see "USB VCom Driver" be active but whatever I tried, SP Flash Tools would never start flashing again. The phone also never activated the "USB preloader Driver". Trying to get to meta-mode with connecting USB while pressing Volume+ didn't work either.
Solution worked out to be : Let the phone drain its battery. Over a few days I had removed the back cover and had been watching YouTube-movies about shorting test-points, the phone laying on my desk not charging. Right before I desoldered the battery I connected the phone again and pfew : It went to "USB Preloader Driver" and I could flash again
Connect to P9000, YES
Was completely lost on how to flash a new ROM to the phone. Have used SP Flash many times before. Without knowing the +Volume trick was completely lost. Wasted weeks on this. Thank you alohahe3000.
nephster said:
Having just gone through the joy of unbricking my new P9000, after I didn't untick preloader when flashing, I've learned more today about using "meta-mode" with a MediaTek phone than I ever wanted to!
This is what debricked my phone. I wonder if this is of use to you? I make no claims it won't brick your device, so please read up on using this mode beforehand!!
Have Device Manager open to see what's going on with drivers
In SP Tools, load a stock ROM and tick *just* the Preloader. Hit Download.
Then hold down *only* the Volume + key (keep it pressed!) and plug the phone in. This bypasses the higher functions of the phone's memory and loads a basic driver - Mediatek USB VCOM will appear in the Device Manager under Ports. Keep Vol + pressed and it will flash the Preloader part of the memory.
With the Preloader flashed, the other parts of the phone (such as recovery) should be flashable, as hopefully the preloader driver will now load.
Click to expand...
Click to collapse
Didn't appear
nephster said:
Having just gone through the joy of unbricking my new P9000, after I didn't untick preloader when flashing, I've learned more today about using "meta-mode" with a MediaTek phone than I ever wanted to!
This is what debricked my phone. I wonder if this is of use to you? I make no claims it won't brick your device, so please read up on using this mode beforehand!!
Have Device Manager open to see what's going on with drivers
In SP Tools, load a stock ROM and tick *just* the Preloader. Hit Download.
Then hold down *only* the Volume + key (keep it pressed!) and plug the phone in. This bypasses the higher functions of the phone's memory and loads a basic driver - Mediatek USB VCOM will appear in the Device Manager under Ports. Keep Vol + pressed and it will flash the Preloader part of the memory.
With the Preloader flashed, the other parts of the phone (such as recovery) should be flashable, as hopefully the preloader driver will now load.
Click to expand...
Click to collapse
Mediatek USB VCOM didn't appear. Instead, "unkown device" appeared under "other devices". Can someone help me because I'm about to finish flashing my Tablet and it's Nextbook 7 Premium. Thanks a lot!
nephster said:
Having just gone through the joy of unbricking my new P9000, after I didn't untick preloader when flashing, I've learned more today about using "meta-mode" with a MediaTek phone than I ever wanted to!
This is what debricked my phone. I wonder if this is of use to you? I make no claims it won't brick your device, so please read up on using this mode beforehand!!
Have Device Manager open to see what's going on with drivers
In SP Tools, load a stock ROM and tick *just* the Preloader. Hit Download.
Then hold down *only* the Volume + key (keep it pressed!) and plug the phone in. This bypasses the higher functions of the phone's memory and loads a basic driver - Mediatek USB VCOM will appear in the Device Manager under Ports. Keep Vol + pressed and it will flash the Preloader part of the memory.
With the Preloader flashed, the other parts of the phone (such as recovery) should be flashable, as hopefully the preloader driver will now load.
Click to expand...
Click to collapse
I know this was a LONG time ago, but after spending two days trying so many things to save my p9000 this finally did it. Thank you VERY much!
Wonderful I only had the Elephone a few days, mine had a very temperamental SIM slot and I couldn't get NFC to work for anything useful. A shame, as it had lots of potential, I thought. Glad you are getting your money's worth out of your one!
Related
PLEASE! I need to load a new ROM into my MT6575 phone using Smart Phone Flash tool.
I've installed the Mediatek drivers on 4 different computers in my house (Vista, Window 7, Windows 7 64bit, Windows 8) and I cant get ANY of them to work!!
When I look under Ports (COM and LPT) in Device Manager, I ALWAYS get: This device cannot start. (Code 10)
WHAT is going on!! I've wasted so much time with this problem.
johnnysnavely said:
PLEASE! I need to load a new ROM into my MT6575 phone using Smart Phone Flash tool.
I've installed the Mediatek drivers on 4 different computers in my house (Vista, Window 7, Windows 7 64bit, Windows 8) and I cant get ANY of them to work!!
When I look under Ports (COM and LPT) in Device Manager, I ALWAYS get: This device cannot start. (Code 10)
WHAT is going on!! I've wasted so much time with this problem.
Click to expand...
Click to collapse
your not the only one with this problem i have it too with same mt6575 someone help please
Need to uninstall device and reinstall drivers
If you google, "Code 10", you will find that on a Windows system it is an error code generated by the Device Manager "because it can not start a device". In a nut shell, the most likely cause for this is because the device was not properly installed with the right drivers.
If you are running Windows, you can try to use the attached file called USBReview to see what device that is as you know it is your phone. Basically, with this program you can remove all the old drivers and start all the driver installation again.
Try to find your phone either here on xda, on the web or contact your phone's manufacturer - you need drivers!!!
Good luck, Mr. Phelps.
johnnysnavely said:
PLEASE! I need to load a new ROM into my MT6575 phone using Smart Phone Flash tool.
I've installed the Mediatek drivers on 4 different computers in my house (Vista, Window 7, Windows 7 64bit, Windows 8) and I cant get ANY of them to work!!
When I look under Ports (COM and LPT) in Device Manager, I ALWAYS get: This device cannot start. (Code 10)
WHAT is going on!! I've wasted so much time with this problem.
Click to expand...
Click to collapse
ronbo76 said:
If you google, "Code 10", you will find that on a Windows system it is an error code generated by the Device Manager "because it can not start a device". In a nut shell, the most likely cause for this is because the device was not properly installed with the right drivers.
If you are running Windows, you can try to use the attached file called USBReview to see what device that is as you know it is your phone. Basically, with this program you can remove all the old drivers and start all the driver installation again.
Try to find your phone either here on xda, on the web or contact your phone's manufacturer - you need drivers!!!
Good luck, Mr. Phelps.
Click to expand...
Click to collapse
Your USB program does give a lot of information I have never seen before, but I still haven't been able to figure out how to get the driver to load.
thanks, John
I'm having the same problem installing the MT6575 USB VCOM drivers. Is there a workaround to get this installed? I"m using WIN 6 64bit
johnnysnavely said:
PLEASE! I need to load a new ROM into my MT6575 phone using Smart Phone Flash tool.
I've installed the Mediatek drivers on 4 different computers in my house (Vista, Window 7, Windows 7 64bit, Windows 8) and I cant get ANY of them to work!!
When I look under Ports (COM and LPT) in Device Manager, I ALWAYS get: This device cannot start. (Code 10)
WHAT is going on!! I've wasted so much time with this problem.
Click to expand...
Click to collapse
This is what worked for me after lot of experimenting and searching:
- get MTK6575 drivers (for instance from Bruno Martins where he writes about flashing mtk6575 - google: MT6575 flashing tutorial bruno
- Start c/windows/system32/hdwwiz.exe (as admin)
- Click next
- Manually select hardware
- List all devices
- Select the driver (for example usb2ser_Win764.inf)
- from the List select "MediaTek Preloader USB VCOM Port"
(or you can install other drivers from the list if Preloader is not enough..)
On another computer I solved it by installing whole Android SDK, checked my android system and installed updated for SDK (approx. 2 GB) and it installed correct drivers automatically.
Also you can experiment with using another usb port..
Please write here if it helped.
ivy13 said:
This is what worked for me after lot of experimenting and searching:
- get MTK6575 drivers (for instance from Bruno Martins where he writes about flashing mtk6575 - google: MT6575 flashing tutorial bruno
- Start c/windows/system32/hdwwiz.exe (as admin)
- Click next
- Manually select hardware
- List all devices
- Select the driver (for example usb2ser_Win764.inf)
- from the List select "MediaTek Preloader USB VCOM Port"
(or you can install other drivers from the list if Preloader is not enough..)
On another computer I solved it by installing whole Android SDK, checked my android system and installed updated for SDK (approx. 2 GB) and it installed correct drivers automatically.
Also you can experiment with using another usb port..
Please write here if it helped.
Click to expand...
Click to collapse
Tried your first method but still get Code 10 error. Could not understand your second method. Please help. Me device is Qmobile Noir A2
hye.. any progress? am having the same issue.. just for MTK6575 com port driver
Just made my Amoi N820 work
So happy
You get Code 10 becouse your windows couldn't recognize the driver but that's irrelevant becouse flashing will work
No solution?
Any solution on this problem?
I've this china mt6575 galaxy s3 clone and got rooted using CF Root.Got ADB composite driver successfully installed in my pc (using win7 32-bit).When I install preloader usb vcom driver, i'm also facing this 'code 10' issue.Until now I can't install CWM in my phone.(the Flash Tool cannot detect my device).i try to install/push CWM using Terminal Emulator but nothing seems to change .when reboot into recovery mode the same stock recovery appear.Any help please?
orion~X said:
Any solution on this problem?
I've this china mt6575 galaxy s3 clone and got rooted using CF Root.Got ADB composite driver successfully installed in my pc (using win7 32-bit).When I install preloader usb vcom driver, i'm also facing this 'code 10' issue.Until now I can't install CWM in my phone.(the Flash Tool cannot detect my device).i try to install/push CWM using Terminal Emulator but nothing seems to change .when reboot into recovery mode the same stock recovery appear.Any help please?
Click to expand...
Click to collapse
i have thet problem to.
is ther solution?
I HAVE SOLUTION FOR THIS PROBLEM!!
Just ignore the error Code 10! Start the SPFlashtool and load the scatterfile, click on download and connect your switch off Phone with the computer. It will work fine.
Having the Same Problem
I understand I can ignore it and it works on that part, however I'm trying to root my phone now and it's not recognising that I have attached a device to the computer. Please need help to solve the problem. Have the drivers but can't get it without code 10
Hi.
me test for me not work.
iphone 4s.
plz help me.
hihi2u2 said:
I understand I can ignore it and it works on that part, however I'm trying to root my phone now and it's not recognising that I have attached a device to the computer. Please need help to solve the problem. Have the drivers but can't get it without code 10
Click to expand...
Click to collapse
Did you ever get this problem solved as I have the same issue with an MTK 6592 chip based phone?
I have the same problem too.
Installation of Media Tek preloaded drivers gives me Code 10 error.
Has anyone found the solution?
my phone is totally dead without power now after I tried to flash with SP Flash tool using correct ROM. I noticed in device manager that there is a CODE 10 error in mediatek preloader usb driver.. is this the culprit? my phone can no longer be detected now in SPFlash or MTK Droid tools... so hopeless... this is a brandnew phone I bought to be given as gift to my cousin...
I did it! I did it! I did it!
The solution is... we need not MediaTek USB VCOM (Android) (USB\VID_0BB4&PID_0005&MI_02), but PreLoader USB VCOM Port (USB\Vid_0e8d&Pid_2000) !
I have MTK6582 (KingSing S2), the host - WinXPx64.
It looks like my phone (and, maybe, other MTK devices too) have several engineering modes.
I have spent several hours trying to get working VID_0BB4&PID_0005&MI_02, which is exposed, if device is turned on while holding VOL- pressed. In this mode some strange factory mode with nonfunctional menu items is displayed on the screen. But to activate mode with Vid_0e8d&Pid_2000 some trickery is necessary.
Sometimes this USB interface starts repeatedly to appear and disappear every half-second in infinitive loop. I had such situation once, when connected turned off phone to USB cable with battery removed.
I just literally catched MT65xx Preloader by double clicking on it in windows device manager and pressing "install drivers" in it's properties. I have used Driver_Auto_Installer_v1.1236.00\SmartPhoneDriver\x64\Infs\usbvcom.inf from http://spflashtool.com/download/Driver_Auto_Installer_v1.1236.00.zip. DriverVer = 12/24/2011, 2.0000.0.0
After clicking "Read Back" in Flash Tool this insane loop stopped and program started to function as intended.
This interface could also appear once and for very short moment, if turned off phone (with battery inserted) is just connected to host. Also it could be seen again, if power button is pressed. If "Download" or "Read Back" is not pressed in advance in Flash Tool, than boot will continue after smaller than a second pause (if device is functional).
I don't know if running Install.bat (from archive I have given above) is necessary. It didn't installed driver when Vid_0e8d&Pid_2000 wasn't active, but, I guess, running it during short blinks would give the same effect.
Also, I don't know, if advice given in comment#6 in this thread four years ago would work. Maybe, the fault was in older version of driver (DriverVer=05/30/2011,1.1123.0).
Another reason could be that necessary USB interface disappears before windows manages to install driver for it for the first time. Possibly, only if "catched" in device manager, user could manually assign driver to it.
I've been struggling with my UMI Rome for days. It has/had the black screen problem, sometimes won't enter recovery mode, sometimes wouldn't allow charge, sometimes works just fine (yesterday). Last night i mistakenly cut off power during a battery recharge. -- today it has all the above problems (bricked) so I am trying doing a flashing again using the tutorials and tools on the Tehnotone.com site. Sintetix's reply above helps me at least have a better clue on what is going on. Wish me luck! BTW, I am using a Dell Windows 10 pc. (Results to be reported here.)
Sintetix said:
The solution is... we need not MediaTek USB VCOM (Android) (USB\VID_0BB4&PID_0005&MI_02), but PreLoader USB VCOM Port (USB\Vid_0e8d&Pid_2000) !
I have MTK6582 (KingSing S2), the host - WinXPx64.
It looks like my phone (and, maybe, other MTK devices too) have several engineering modes.
I have spent several hours trying to get working VID_0BB4&PID_0005&MI_02, which is exposed, if device is turned on while holding VOL- pressed. In this mode some strange factory mode with nonfunctional menu items is displayed on the screen. But to activate mode with Vid_0e8d&Pid_2000 some trickery is necessary.
Sometimes this USB interface starts repeatedly to appear and disappear every half-second in infinitive loop. I had such situation once, when connected turned off phone to USB cable with battery removed.
I just literally catched MT65xx Preloader by double clicking on it in windows device manager and pressing "install drivers" in it's properties. I have used Driver_Auto_Installer_v1.1236.00\SmartPhoneDriver\x64\Infs\usbvcom.inf from http://spflashtool.com/download/Driver_Auto_Installer_v1.1236.00.zip. DriverVer = 12/24/2011, 2.0000.0.0
After clicking "Read Back" in Flash Tool this insane loop stopped and program started to function as intended.
This interface could also appear once and for very short moment, if turned off phone (with battery inserted) is just connected to host. Also it could be seen again, if power button is pressed. If "Download" or "Read Back" is not pressed in advance in Flash Tool, than boot will continue after smaller than a second pause (if device is functional).
I don't know if running Install.bat (from archive I have given above) is necessary. It didn't installed driver when Vid_0e8d&Pid_2000 wasn't active, but, I guess, running it during short blinks would give the same effect.
Also, I don't know, if advice given in comment#6 in this thread four years ago would work. Maybe, the fault was in older version of driver (DriverVer=05/30/2011,1.1123.0).
Another reason could be that necessary USB interface disappears before windows manages to install driver for it for the first time. Possibly, only if "catched" in device manager, user could manually assign driver to it.
Click to expand...
Click to collapse
I tried what you said. It wouldn't install properly. It kept saying error (code 10) and showed in device management with a caution sign every time I installed the driver. I disabled the forced driver signature thingamabop but it still does it. I guess I'm screwed. Has anyone else fixed this?
I have a motorola motostart (xt390) and wish to unlock bootloader, root, etc. Nevertless, I just can't get into fastboot mode.
Powering up with VOL Down it access the recovery mode. The same for VOL UP+DOWN.
When i try powering up with VOL UP pressed the device simply don't power up.
Is it a malfunctioning device or some roms for this hardware simply have mysteriuos ways to enter fastboot?
The ROM is a brazilian retail, Gingerbread (2.3.6) version MAUI.11AMD.W11.37.SP.V9.F4.P1, build: ARGONM_W_07.15.04R_D.
Please! Help!
Nobody? hehehe
I have found a clue: if I plug the device without batery and hol VOL_UP the windows detect, and install the drivers, to a "MTK USB Port (COM X)". If I release the VOL_UP the USB port gets disconected.
Someone know what I can do with a MTK port?
erlyneto said:
I have found a clue: if I plug the device without batery and hol VOL_UP the windows detect, and install the drivers, to a "MTK USB Port (COM X)". If I release the VOL_UP the USB port gets disconected.
Someone know what I can do with a MTK port?
Click to expand...
Click to collapse
I think that's the same as download mode for when you have to flash it with SPFT. That's how I get spft to recognize my O+8.75.
xshinta9 said:
I think that's the same as download mode for when you have to flash it with SPFT. That's how I get spft to recognize my O+8.75.
Click to expand...
Click to collapse
Sorry by my ignorance, but SPFT is a software?
I find the SPFT that you mentioned. But, as far as I could understand the software, it is used to flash or dump rom from MTK based phones.
But there are problems:
1)XT390 appears to be based on MTK6*** phones, but is not the same, so, the roms should not work in it, right?
2)I can't use this tool to send commands to the device (like fastboot mode on other Motorola android phones), so i can't get my device id to unlock the bootloader in the morotola web site...
Do you know anything about that software, its roms and XT390? There are any ways to open a command line utility on it?
Hi bro, unfortunately I have zero knowledge on it thus far. 'am figuring out how to unlock my phone's bootloader as well, (it's a local-based chinese phone as well that's marketed under a different name)
Hi, i bought power 2, phone not open and noting happen when press power or vol+ - together + power, or ....try everything
Bricked when try flash twrp recovery. later i try flash rom again, my computer see phone when phone is closed. can not open already. But now my computer not see the phone:A request for the USB device descriptor failed.
What can i do, and sorry for my english
This phone can't be bricked (mostly). You can easily restore the stock firmware, just download stock rom from official site, extract it. And use sp flash tool not the one that comes with the official rom. Open sp flash tool.
Load scatter file from official rom, you can leave the DA file for all mtk phones that comes with stock rom or use the one in sp flash tool (just leave it as it is) in the user interface of sp flash tool.
Make sure it says "download only" from the drop box. Click download then connect the phone to your computer. Flashing will start and should take about 1 minute and 30 seconds to finish.
If flashing doesn't start. Make sure you have vcom drivers installed. (Also for flashing to start, phone must be turned off obviously, but since you have semi brick, you don't have to worry about that).
Rebel_X said:
This phone can't be bricked (mostly). You can easily restore the stock firmware, just download stock rom from official site, extract it. And use sp flash tool not the one that comes with the official rom. Open sp flash tool.
Load scatter file from official rom, you can leave the DA file for all mtk phones that comes with stock rom or use the one in sp flash tool (just leave it as it is) in the user interface of sp flash tool.
Make sure it says "download only" from the drop box. Click download then connect the phone to your computer. Flashing will start and should take about 1 minute and 30 seconds to finish.
If flashing doesn't start. Make sure you have vcom drivers installed. (Also for flashing to start, phone must be turned off obviously, but since you have semi brick, you don't have to worry about that).
Click to expand...
Click to collapse
Vdcom drivers already installed but not using. becouse computer does not see phone.
Unknown usb device . A request for the USB device descriptor failed. (code 43)
if i solve this, maybe i can flash rom
Rebel_X said:
This phone can't be bricked (mostly). You can easily restore the stock firmware, just download stock rom from official site, extract it. And use sp flash tool not the one that comes with the official rom. Open sp flash tool.
Load scatter file from official rom, you can leave the DA file for all mtk phones that comes with stock rom or use the one in sp flash tool (just leave it as it is) in the user interface of sp flash tool.
Make sure it says "download only" from the drop box. Click download then connect the phone to your computer. Flashing will start and should take about 1 minute and 30 seconds to finish.
If flashing doesn't start. Make sure you have vcom drivers installed. (Also for flashing to start, phone must be turned off obviously, but since you have semi brick, you don't have to worry about that).
Click to expand...
Click to collapse
My phone opened, but computer cannot see storage.i think phone's usb ports damaged. i can flash rom with sp flash tool only.
fastboot and recovery not working. i cant make root too. what can i do i dont know. recovery cant open, writing "no command".
faysoft said:
My phone opened, but computer cannot see storage.i think phone's usb ports damaged. i can flash rom with sp flash tool only.
fastboot and recovery not working. i cant make root too. what can i do i dont know. recovery cant open, writing "no command".
Click to expand...
Click to collapse
Go to developer mode menu (if you don't have it, tap on "build number" in "about phone" from settings, seven times and it will be activated). Then change how your USB acts when connected with computer.
If you can't, just use ES File explorer to send files between your computer and phone in FTP or SMB mode over WiFi.
Have the same problam.
The pc recognize the vcom device but only for 2-3 secconds and then disaper, then i get an error with sp flashtool.
Phone isnt tured on. At all.
I also have the same problem.
Is anyone has success with unbricking Power II in such case?
pacmancoder said:
I also have the same problem.
Is anyone has success with unbricking Power II in such case?
Click to expand...
Click to collapse
I do not know if it is late. I had the same problem with another phone. I was solved as follows:
1. Unplug the usb cable from the computer
2. Power off the phone
3. Press download on sp flash tool
4. Holding vol+ and power, plug the usb cable on the computer.
Hi,
can anyone provide me with nvram /nvdata backup please of Ulephone power 2?
I have probably correct IMEI, valid MAC fo Wifi/BT ...
It looks like my serial number changed to 123456789ABCDEF and I have no idea how to change it to original because MAUI (?) stucked on get kernel
I can find original box with correct serial and IMEis on stick
The only one problem with mobile is I am not able connect to mobile network - registration SIM to mobile network always fail.
and at MTK engineer I have only Bluetooth, FM Receiver, Wifi, Wifi CTIA, Wifi Display
I have nothing like Radio, CDS etc ...
OEM unlocked, TWRP, rooted
Some information probably lost when flashing
And of course another problem :
except GPS and proximity, all sensors does not work - G sensor, acceleration, magnetic sensor, compass . Probably configuration data is located at nvdata
i tried flash 5MB file nvdata.bin from different MTK 675x device, but nothings change
I tried flash 33 MB nvdata.img from same MTK 675x device, but I lost IMEI and nothing solved
This is why I need 33 MB NVDATA.IMG from another functional Ulephone power 2
I can change IMEI at MTK then ...
I had to flash , because phone was unusable - it stucked mostly on obtaining IP address wifi
after a while, phone disconnected from wifi and cant find any wifi or if find, then cant connect because of some security issue , after restart all was OK ...
Thanks
I have a thl knight 2, I tried to flash twrp and it's stuck in a bootloop. I can't connect trough adb, fastboot but I saw some ports in device manager. I downloaded mediatek drivers. As far as I know when I connect the phone it should be detected by the droid tools or sp flash tool but it isn't. All the drivers pop up, I tried setting them to mediatek DA USB VCOM (Android), Mediatek USB VCOM (android) and Mediatek PreLoader USB VCOM (Android) but still it doesn't find the phone. I can't use recovery and can't enter fastboot. My volume up key used to lower the volume instead so maybe they are both mapped to volume down? I have a orange state message on the android logo about not trusting my phone. It would have been better to just let the chinese government get my personal information than trying to mess with forces I don't comprehend! If anyone reads this and is willing to help me I will be forever in your debt.
Maybe if I brick it altogether I will have more chance than it just getting to the android logo.
maduri said:
Maybe if I brick it altogether I will have more chance than it just getting to the android logo.
Click to expand...
Click to collapse
Where did you get the mentioned twrp recovery?
I did use Maui Meta tool in the past to restore IMEIs on slitely older MTK devices, but My current phone is based on MTK6768 with secure boot, needed the IMEIs to be written after flashing firmware. I can use SP flash tool with "sec boot" utility to flash ROM successfully, But unable to connect to Maui Meta tool. I have Modem meta tool Version 10.2044, after launching the program as an admin, it is doing the following:
1. Clicking "connect" and plugging the cable to phone in turned off state: windows make a hardware connect sound, a new port appear in device manager, followed by a disconnect sound after 1 second, that hardware disappear and phone boot-up in offline charging mode or to the welcome/lock screen. The "meta tool" remain at looking for device connection.
2. Holding the Volume down while plugging the Cable in, do the exact same - "meta Tool" remain in waiting for connection.
3. Holding Volume Up: it connect, then disconnect and went to Stock recovery - "meta tool" remain in waiting state.
4. Holding Power+Volume up: Windows continue making connect and disconnect sounds again and again and the Port under device manager keep coming in and out. Phone boots up as soon as I leave the buttons. "meta Tool" remain in waiting for connection, or sometime move to "getting Kernel Port" and get stuck at it.
5. Holding both volume buttons: do the exact same as point Number 4 above.
6. Holding both volumes+power buttons: do the exact same as point number 4 above.
Definitely, all MTK drivers are installed and working because I can use SP flash tool in conjunction with secBoot utility without any problem. I tried other similar tools like “SN writer” and “read and write tool v1.3” and faced almost same behaviour. It means my device is not going into Meta mode properly with these tools. Please contribute in helping me with your valuable suggestion, as I’m not being able to use this device due to cellular network unavailability.
You need to use Preloader Mode not MTK mode, look at Com Port driver, try boot device to normal mode and make power off then hold up and connect USB must get preloader device if get mtk USB port only not work, see mtk preloader to enter META mode
MA7MOD_GSM said:
You need to use Preloader Mode not MTK mode, look at Com Port driver, try boot device to normal mode and make power off then hold up and connect USB must get preloader device if get mtk USB port only not work, see mtk preloader to enter META mode
Click to expand...
Click to collapse
bro. he literally said preloader comes, but disconnects, + it gets stuck on getting kernel on sn flash tool.
I tried sn flash tool, it got stuck, I tried aftersalestool, it does not stuck, but it says:error code 6 get kernel port.
What do i do? I need to fix my IMEI very badly!
Abdullah5490 said:
I did use Maui Meta tool in the past to restore IMEIs on slitely older MTK devices, but My current phone is based on MTK6768 with secure boot, needed the IMEIs to be written after flashing firmware. I can use SP flash tool with "sec boot" utility to flash ROM successfully, But unable to connect to Maui Meta tool. I have Modem meta tool Version 10.2044, after launching the program as an admin, it is doing the following:
1. Clicking "connect" and plugging the cable to phone in turned off state: windows make a hardware connect sound, a new port appear in device manager, followed by a disconnect sound after 1 second, that hardware disappear and phone boot-up in offline charging mode or to the welcome/lock screen. The "meta tool" remain at looking for device connection.
2. Holding the Volume down while plugging the Cable in, do the exact same - "meta Tool" remain in waiting for connection.
3. Holding Volume Up: it connect, then disconnect and went to Stock recovery - "meta tool" remain in waiting state.
4. Holding Power+Volume up: Windows continue making connect and disconnect sounds again and again and the Port under device manager keep coming in and out. Phone boots up as soon as I leave the buttons. "meta Tool" remain in waiting for connection, or sometime move to "getting Kernel Port" and get stuck at it.
5. Holding both volume buttons: do the exact same as point Number 4 above.
6. Holding both volumes+power buttons: do the exact same as point number 4 above.
Definitely, all MTK drivers are installed and working because I can use SP flash tool in conjunction with secBoot utility without any problem. I tried other similar tools like “SN writer” and “read and write tool v1.3” and faced almost same behaviour. It means my device is not going into Meta mode properly with these tools. Please contribute in helping me with your valuable suggestion, as I’m not being able to use this device due to cellular network unavailability.
Click to expand...
Click to collapse
I have this same issue where my device can't get detected by any IMEI writer as itneeds to be in meta mode. Do you have any success on this ?
K!r!to26 said:
I have this same issue where my device can't get detected by any IMEI writer as itneeds to be in meta mode. Do you have any success on this ?
Click to expand...
Click to collapse
I also got the same Issue, But it gives a kernel error, Idk, what error it is, and what's the fix, The Local Tech Repair shop did the restoration, but gave me the mobile without IMEI, so, I am stuck, I am also afraid to re flash the stock rom, because I dont know what the hell they did, Maybe they did some kernel change, or the kernel is the same as the wrong one? Idk, Maybe I would say, Reflash your mobile, and check it.
Having the same-ish issue on redmi note 8 pro. any progress?
Abdullah5490 said:
I did use Maui Meta tool in the past to restore IMEIs on slitely older MTK devices, but My current phone is based on MTK6768 with secure boot, needed the IMEIs to be written after flashing firmware. I can use SP flash tool with "sec boot" utility to flash ROM successfully, But unable to connect to Maui Meta tool. I have Modem meta tool Version 10.2044, after launching the program as an admin, it is doing the following:
1. Clicking "connect" and plugging the cable to phone in turned off state: windows make a hardware connect sound, a new port appear in device manager, followed by a disconnect sound after 1 second, that hardware disappear and phone boot-up in offline charging mode or to the welcome/lock screen. The "meta tool" remain at looking for device connection.
2. Holding the Volume down while plugging the Cable in, do the exact same - "meta Tool" remain in waiting for connection.
3. Holding Volume Up: it connect, then disconnect and went to Stock recovery - "meta tool" remain in waiting state.
4. Holding Power+Volume up: Windows continue making connect and disconnect sounds again and again and the Port under device manager keep coming in and out. Phone boots up as soon as I leave the buttons. "meta Tool" remain in waiting for connection, or sometime move to "getting Kernel Port" and get stuck at it.
5. Holding both volume buttons: do the exact same as point Number 4 above.
6. Holding both volumes+power buttons: do the exact same as point number 4 above.
Definitely, all MTK drivers are installed and working because I can use SP flash tool in conjunction with secBoot utility without any problem. I tried other similar tools like “SN writer” and “read and write tool v1.3” and faced almost same behaviour. It means my device is not going into Meta mode properly with these tools. Please contribute in helping me with your valuable suggestion, as I’m not being able to use this device due to cellular network unavailability.
Click to expand...
Click to collapse
Ok Fixed this Problem: https://forum.xda-developers.com/t/...ote-7-x690-x690b-x690c.4592491/#post-88605287
View this thread, Explained in detail.