Related
Hello everyone,
I'm writing in the hopes of receiving some guidance re: a small "challenge" a friend issued to me. As you can probably guess, the half of the story that involves my friend's actions on the tablet are word-of-mouth, seeing as the device was given to me in a totally bricked state. Hope you'll be able to assist me somehow!
After using his Galaxy Tab P7500R for some time, the battery stopped charging. He supposedly tried a complete wipe and system restore (for which he was unable to guarantee a successful conclusion), and then the machine ran out of whatever juice had been left behind during the last successful charging cycle, and turned off completely, showing no signs of life whatsoever.
This is where I come in - I was given the "expensive ornament", accompanied by the words "have fun, I've already bought another one".
Symptoms are the following:
1) Powering the device on doesn't work. While the device is connected to the house power grid, there are no indicators of the device doing anything.
2) Connecting the device to a USB port on my laptop, and holding the power button, after 15 seconds my PC signals a device being disconnected via sound, and that disconnection sound is almost immediately followed by a couple, rapid, "halved" 'device connected' sounds. On the other hand, while the device is connected to a USB port on the laptop, if I hold the power button together with volume+, all I hear every 15 or so seconds is the "Device disconnected" sound.
3) After using USBDeview to remove a driver named APX, and after reconnecting the device to the computer via USB (sometimes this requires holding the power button, sometimes all it takes is a reconnection), I will hear a full "device connected" sound; then, an "installing driver" window will open, for the APX driver, which, after looking for the appropriate driver via Windows Update, will give me an error message ("no driver found") on the "unable to install device drivers" window.
4) Opening the device (out of warranty for over a year), and utilizing some testing tools have shown that power does reach as far as the motherboard, and that the batteries are somewhat charged at the moment.
Any ideas?
Thanks in advance for your help!
Lightside
[UPDATE 1]: I successfully installed the NVIDIA USB Boot-Recovery drivers for mobile devices. The tablet is now detected as being connected to my laptop, sounds and everything.
Following some instructions I was able to find on these forums, I tried installing NVFlash, and running the --bl bootloader.bin --go, receiving a "Rcm version 0X4 - Command send failed (usb write failed)" message.
From what I gathered, this is evidence of a locked bootloader. I wasn't able to find any posts dealing specifically with a bricked device that is only recognized in APX mode, and how to unlock the bootloader in such cases. Is there a guide available by any chance?
Update 2 :
I've extracted the battery, but I seem to be unable to remove the residual charge, as the device shows up (APX) as connected, as soon as I plug in my USB cable.
Anyone? :/
Up?
Hello all,
I have a rooted Micromax A58 which was perfectly working. I did a full nandroid backup of it 2 days ago. On yesterday, I was moving some system app (google maps, play store etc) to SD with some software) so that I could increase the internal memory and install some other softwares. But, unfortunately, after that modification, the phone stopped working properly (it was stucking up when the BOLT logo was reached). So, I started it in recovery and do a wipe cache and factory reset. After that, the phone is always going to Factory Mode.
Then I tried to Flash the Stock ROM using Flash Tool but was unsuccessful multiple times. After the scatter file selected, when I clicked the 'Download' (or even firmware upgrade), all time time, the phone was disconnecting/reconnecting every now and then and nothing happened after (even though I already installed the Vcom and PdaNet driver in the PC). So, I had to quit. I am attaching herewith the logs of the Flash Tool lastly tried.
Now, when I am starting the phone power button, nothing is happening.. NOTHING but black screen...
I am a bit worried.. your help very much appreciated. Please let me know for any information needed. Thanks.
'No com port detected' error
I tried another time and the problem still there.. When in SP Flash Tool, I select scatter file, click 'Download' and connect the phone to PC, the process doesn't progress further. So, I have to finally click 'Stop' to quit. In the logs, it shows--
"No com port detected.."
Attaching the trace logs file herewith.
Please advice how to resolve the issue.. I am totally stuck now. Thanks.
Androhelp said:
Hello all,
I have a rooted Micromax A58 which was perfectly working. I did a full nandroid backup of it 2 days ago. On yesterday, I was moving some system app (google maps, play store etc) to SD with some software) so that I could increase the internal memory and install some other softwares. But, unfortunately, after that modification, the phone stopped working properly (it was stucking up when the BOLT logo was reached). So, I started it in recovery and do a wipe cache and factory reset. After that, the phone is always going to Factory Mode.
Then I tried to Flash the Stock ROM using Flash Tool but was unsuccessful multiple times. After the scatter file selected, when I clicked the 'Download' (or even firmware upgrade), all time time, the phone was disconnecting/reconnecting every now and then and nothing happened after (even though I already installed the Vcom and PdaNet driver in the PC). So, I had to quit. I am attaching herewith the logs of the Flash Tool lastly tried.
Now, when I am starting the phone power button, nothing is happening.. NOTHING but black screen...
I am a bit worried.. your help very much appreciated. Please let me know for any information needed. Thanks.
Click to expand...
Click to collapse
Try changing the ports, Cable etc or better off try on a different computer .
Port/Cable/PC change didn't help
kapil_dheer said:
Try changing the ports, Cable etc or better off try on a different computer .
Click to expand...
Click to collapse
Hello Kapil,
Thanks for the response. Yesterday I tried with separate laptop, but the same problem was there. Today, I tried with the different USB port.. but didn't help.
It seems that the driver can not recognize the device and when I connect the phone, it is just in a loop of disconnecting/re-connecting. Please advice further. Thanks.
Only option now seems is Service Centre.
The guys are pretty dumb. I've tested samsung motorola etc.....they don't even know what root is.
Maybe they'll be unable to identify what you tried to do.
You can give any reason for it not functioning.
Good luck.
kapil_dheer said:
Only option now seems is Service Centre.
The guys are pretty dumb. I've tested samsung motorola etc.....they don't even know what root is.
Maybe they'll be unable to identify what you tried to do.
You can give any reason for it not functioning.
Good luck.
Click to expand...
Click to collapse
Thank you Kapil for the advice. As Micromax service centre is not having a good reputation regarding these, so I would go for that option as the last resort.
Before that, can I please ask the other members for giving further advice if there is any option to try with.. Thanks for your help.
Managed to get phone reconized in PC usb-pls help further
Androhelp said:
Thank you Kapil for the advice. As Micromax service centre is not having a good reputation regarding these, so I would go for that option as the last resort.
Before that, can I please ask the other members for giving further advice if there is any option to try with.. Thanks for your help.
Click to expand...
Click to collapse
I have managed to get the phone recognized by PC usb now. But, when I try try the SP Flash utility to either Format or Download or Firmware update etc, it is throwing error like below--
09/16/2014 09:56:32.640 FlashTool[2212][3912][D]: APCore::Connection::ConnectDA(): Failed to Connect DA: S_FT_ENABLE_DRAM_FAIL(..\QT_FlashTool_Refactor\Conn\Connection.cpp,126)
09/16/2014 09:56:38.140 FlashTool[2212][3912][D]: BackgroundWorker::run(): BROM Exception! ( BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032)
[EMI] Enable DRAM Failed!
[HINT]:
Please check your load matches to your target which is to be downloaded.)((APCore::Connection::ConnectDA,..\QT_FlashTool_Refactor\Conn\Connection.cpp,127))(..\QT_FlashTool_Refactor\UI\src\BackgroundWorker.cpp,94)
09/16/2014 09:56:58.765 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device Removed.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,483)
09/16/2014 09:56:59.750 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device plug in.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,478)
09/16/2014 09:57:33.828 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device Removed.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,483)
09/16/2014 09:57:34.812 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device plug in.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,478)
09/16/2014 09:58:08.890 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device Removed.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,483)
09/16/2014 09:58:10.375 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device plug in.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,478)
I tried the above multiple times but everytime same error as above.
When tried to connect the phone (without battery) it is disconnect/reconnect in an endless loop.
When try to connect with battery, the disconnect/reconnect loop is gone (i.e.-stable) but sometime it can not identity phone ('Unknown Device').
Also tried to press volume down button along with battery inside, but showing 'Unknown Device' and Flash tool getting hanged.
I used the Stock Rom downloaded from xda site for my phone detailed below---
Android 4.2.2
Model Micromax A58
BaseBand version- MOLY.WR8.W1315.MD.WG.MP.V1.P11 2013/09/04 15:51
Kernel 3.4.5 [email protected] #1
Build Number Micromax A58_T09
I also have the good nandroid backup (if it could be of any use) but phone is dead now. Confused how to go forward. Please help.
Download in SP Flash Tool successful
Androhelp said:
I have managed to get the phone recognized by PC usb now. But, when I try try the SP Flash utility to either Format or Download or Firmware update etc, it is throwing error like below--
09/16/2014 09:56:32.640 FlashTool[2212][3912][D]: APCore::Connection::ConnectDA(): Failed to Connect DA: S_FT_ENABLE_DRAM_FAIL(..\QT_FlashTool_Refactor\Conn\Connection.cpp,126)
09/16/2014 09:56:38.140 FlashTool[2212][3912][D]: BackgroundWorker::run(): BROM Exception! ( BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032)
[EMI] Enable DRAM Failed!
[HINT]:
Please check your load matches to your target which is to be downloaded.)((APCore::Connection::ConnectDA,..\QT_FlashTool_Refactor\Conn\Connection.cpp,127))(..\QT_FlashTool_Refactor\UI\src\BackgroundWorker.cpp,94)
09/16/2014 09:56:58.765 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device Removed.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,483)
09/16/2014 09:56:59.750 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device plug in.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,478)
09/16/2014 09:57:33.828 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device Removed.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,483)
09/16/2014 09:57:34.812 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device plug in.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,478)
09/16/2014 09:58:08.890 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device Removed.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,483)
09/16/2014 09:58:10.375 FlashTool[2212][2708][D]: OptionDialog::winEvent(): USB Device plug in.(..\QT_FlashTool_Refactor\UI\src\OptionDialog.cpp,478)
I tried the above multiple times but everytime same error as above.
When tried to connect the phone (without battery) it is disconnect/reconnect in an endless loop.
When try to connect with battery, the disconnect/reconnect loop is gone (i.e.-stable) but sometime it can not identity phone ('Unknown Device').
Also tried to press volume down button along with battery inside, but showing 'Unknown Device' and Flash tool getting hanged.
I used the Stock Rom downloaded from xda site for my phone detailed below---
Android 4.2.2
Model Micromax A58
BaseBand version- MOLY.WR8.W1315.MD.WG.MP.V1.P11 2013/09/04 15:51
Kernel 3.4.5 [email protected] #1
Build Number Micromax A58_T09
I also have the good nandroid backup (if it could be of any use) but phone is dead now. Confused how to go forward. Please help.
Click to expand...
Click to collapse
In the meanwhile, when trying to resolve the issue, I tried the following steps and after that, I lastly managed to 'download' the Stock ROM successfully in my phone (using the Windows XP OS)--
1) As I was always getting the SP Flash Tool error 4032 for last couple of days and which was clearly describing 'please check your load matches your target which is to be downloaded', so was investigating the root cause in details. Upon searching in the internet, I downloaded multiple version of Stock ROMs for my Micromax A58 model from different sources to give a try. When trying to 'Download' (in SP Flash Tool), the 'T_09' ROM (link given by 'alanvmathew') in the below mentioned URL worked for me.
http://forum.xda-developers.com/showthread.php?t=2610046&page=2
It is to be noted from the link that Micromax A58 model have 2 different Stock ROMs (i.e.- 'T_07' and 'T_09') which info I was missing all the time.
2) After identifying the scatter file in the SP Flash Tool and clicking the 'Download' option, I inserted battery in the phone and pressing the 'Power + Volume down' button, connected the device into the PC USB. Upon connected, the 'DA USB VCOM PORT' driver automatically installed and the 'Download' started and flashing of ROM went smooth. Finally, it ended up with green 'Download OK' message. Also attaching the snapshots herewith.
Will check the mobile and its performance further and revert back accordingly.
Hi... I'm trying to be as concise and as detailed as possible here:
OK.. I'm trying to flash this ulefone S8 Pro with the STOCK ROM from the ulefone website. I'm using Debian Linux and the SP Flash Tool 5.1804.00 for Linux. I've disabled modemmanager (no conflict there) and I'm able to see from the logs that the device is recognised.
The device itself had it's stock boot.img flashed with a patched version (MagiskManager)and the boot loader has been unlocked - and all was working fine... someone decided to mess about deleting files from /system and the phone refused to boot.
So.... I took the device back and flashed boot, recovery and cache from the stock image using fastboot - all fine... then when it came to system.img - I found out that system-sign.img from the stock ROM wouldn't flash via fastboot - I got an error saying something along the lines of:
Code:
"Invalid sparse file format at header magi error: write_sparse_skip_chunk: ([I]I forget the size[/I]) is not a multiple of the block size 4096"
So, after a bit of googling - I was going to try the SparseConverter tool.. but this seemed to not like the system-sign.img and so I gave up on that idea..
Then I realize I probably need to be using the SP Flash tool - so.. I boot back into Linux and here's what happens.. When the phone is turned on.. I can hold power on + volume up to get the little menu (flashboot, recovery or normal boot) and it ignores this... it goes right to Recovery with "NO COMMAND" - no combination of button pushing does a thing... it will sit at no command, occasionally flashing the screen. When i plug it in.. and don't touch it.. same thing.. straight to no command.. when I turn it on (not plugged in) it does the same thing... when connecting to PC and SP Flash... I hit DOWNLOAD in SP FLASH and then with phone off (battery in) I connect it to the the PC and i get the red bar to 100% and then:
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:1c.3/0000:05:00.0/usb1/1-2
[email protected]/devices/pci0000:00/0000:00:1c.3/0000:05:00.0/usb1/1-2/1-2:1.0
[email protected]/devices/pci0000:00/0000:00:1c.3/0000:05:00.0/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:1c.3/0000:05:00.0/usb1/1-2/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 = -1522456507.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
COM port is open. Trying to sync with the target...
Failed to Connect DA: S_BROM_DOWNLOAD_DA_FAIL
Disconnect!
BROM Exception! ( 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,146))
I've tried all USB ports. Various cables etc etc.. I've tried connecting with phone off and no battery (same thing - same output) - with the battery, without battery and putting battery in after connecting.. taking battery out and putting back in, pushing volume buttons on connecting USB... i've done it all.. same error all the time...
I'm almost to the point where I throw in the towel here... but I thought someone might have some clue or idea what to do now.
Any help appreciated.
Oh yeah.. lastly... dmesg | grep usb gives the following
Code:
[13640.521933] usb 1-2: New USB device found, idVendor=0e8d, idProduct=2000
[13640.521940] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[13640.521945] usb 1-2: Product: MT65xx Preloader
[13640.521949] usb 1-2: Manufacturer: MediaTek
[13643.171638] usb 1-2: USB disconnect, device number 13
[email protected]:~/Downloads$
found out how to unbrick!
OK!! SO... After a LOT of messing about I finally figured this out. What I did was start SP FLASH TOOL and put it in DOWNLOAD mode and then hit the DOWNLOAD button. I then connected the USB lead to my phone but NOT the PC (with the battery in the phone and the phone powered off) THEN I held down the volume up and volume down buttons together and kept holding them... I plugged the USB into the PC and kept holding the volume buttons... lo and behold it worked. I was too scared to let go of the volume buttons, so I just held them until the process had completed.
Hold volume down button when you plug usb lead in and hold until it starts flashing rom!
Also to enter recovery menu, press power + volume up when the command not found message appears.
Checkout guide video https://mega.nz/#F!MqYHCKDS!dqw4xFPs6ZnWI3fH21ZFLA
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.
Device is Infinix Note 11S Helio G96
I was using mtkclient and it was working fine
While it was on the connecting process ( idk correctly what it does at first while connecting)
usb cable was accidentally disconnected
i found the same issue here
How to exit from BROM Mode on Oppo A15 (CPH2185)?
I'm trying to clone the phone disk by using https://github.com/bkerler/mtkclient. It's working flawlessly using the command mtk rf, but I terminate the program using Ctrl+C because I need to clean my pc drive first. I don't think this would cause...
forum.xda-developers.com
he explained it better
i also can't access the battery
help
xx