I've been trying to fix one of my Lenovo K3notes which was bricked after bad flashing. It now won't respond at all.
There are several tutorials about this. But some aspects of them puzzle me.
The method seems to be to enter meta mode, flash the preloader from a stock rom, then flash the whole stock rom separately.
To get into metamode, you have to connect to a Windows computer and check the device manager.
After that, you flash the preloader.
Here are my questions:
1) I use a Linux (Ubuntu) computer, but can have access to a Windows computer if necessary. But it would be good to know how to do this on my own computer. Why is Windows necessary?
2) I don't understand the method to get into Metamode. After finding the phone in the Windows device manager, you are supposed to unplug the phone and start SPflahs. I would have guessed that you would then leave metamode. Is that right?
3) why do you have to flash preloader and stock rom separately? Am I missing some vital step?
4) The tutos mention VCom drivers. Are these the same as the general drivers for the Lenovo phone, are are they specific to this metamode procedure? I have already flashed this phone before with Spflahs, both on my (ubuntu) and my wife's (Windows 7) computers, so drivers are already installed and working for general flashing. Do I need different drivers for preloader?
Thanks
Related
I try to install newest custom rom supernova 4 infinity and message is above:
Formatting SYSTEM:....
Formatting CACHE:....
Formatting DATADATA:....
Formatting DATA:....
Deleting files...
Copying files...
e:failure at line 17 :
copy_dir PACKAGE:system SYSTEM:
installation aborted
now my phone is bricked (Expensive stone) because my usb debugging is off and the odin do not recornize my captivate in downloading mode!!
What i can do now? How i fix debugging ON that i can flash my phone again to stock etc..
USB debugging has nothing to do with it.
you need to get ODIN to recognize your phone. sounds like driver problems
I install odin drivers for captivate 32bit and my windows 7 don't recognize my phone, also odin do not recognize.. i test Downloading Mode.. Is usb debugging off or on with Downloading Mode?
also sdk manager installed with google samsung drivers..
Anybody else that having this recognize issues with windows 7? what to do that recognize are working
In CWM, check to see if you have the option to Root. If you do, apply Root and try flashing the rom again.
I had similar issues with 2 roms with similar errors and I had to apply root in CWM and re-flash and it went trough fine.
energy83 said:
I install odin drivers for captivate 32bit and my windows 7 don't recognize my phone, also odin do not recognize.. i test Downloading Mode.. Is usb debugging off or on with Downloading Mode?
also sdk manager installed with google samsung drivers..
Anybody else that having this recognize issues with windows 7? what to do that recognize are working
Click to expand...
Click to collapse
USB DEBUGGING HAS NOTHING TO DO WITH DOWNLOAD MODE!
usb debugging only has an effect if you are ALREADY booted or currently BOOTING beyond the splash screen. it doesnt matter for download mode...period.
Elisha said:
In CWM, check to see if you have the option to Root. If you do, apply Root and try flashing the rom again.
I had similar issues with 2 roms with similar errors and I had to apply root in CWM and re-flash and it went trough fine.
Click to expand...
Click to collapse
this is one of the most ridiculous things i have read today. root also only applies to the OS....from within recovery or download mode, you arent in the OS...so root doesnt mean SH** within recovery
Pirateghost said:
this is one of the most ridiculous things i have read today. root also only applies to the OS....from within recovery or download mode, you arent in the OS...so root doesnt mean SH** within recovery
Click to expand...
Click to collapse
Don't be a dip****,. I was stating my experience.
From stock 2.1 I could not install Continuum v4 in recovery and got a similar error for E:/
I had to flash a SpeedMod based kernel in recovery and root first before the rom would go all the way trough to flash properly!
It only happens to certain roms...other roms can just flash in recovery from stock no problem without rooting first.
Elisha said:
Don't be a dip****,. I was stating my experience.
From stock 2.1 I could not install Continuum v4 in recovery and got a similar error for E:/
I had to flash a SpeedMod based kernel in recovery and root first before the rom would go all the way trough to flash properly!
It only happens to certain roms...other roms can just flash in recovery from stock no problem without rooting first.
Click to expand...
Click to collapse
This statement thus proves you have no idea what you are talking about. When you understand how a Rom flash works, then you can come back to the discussion. In the meantime, try reading an update-script or 2
Sent from my HTC Vision using Tapatalk
energy83 said:
I install odin drivers for captivate 32bit and my windows 7 don't recognize my phone, also odin do not recognize.. i test Downloading Mode.. Is usb debugging off or on with Downloading Mode?
also sdk manager installed with google samsung drivers..
Anybody else that having this recognize issues with windows 7? what to do that recognize are working
Click to expand...
Click to collapse
You said that you installed the 32 bit drivers for windows 7? Unless you are running a netbook or installed Win 7 on an older computer you probably need the 64 bit drivers. Most newer laptops these days are 64 bit OS. You can check by right clicking on "my computer" and selecting properties. It will say whether you are running 32 or 64 bit.
I also recommend downloading kies (samsung sync software). You can get it off the Samsung website under downloads. Once it's installed and opened, under tools, you can select install drivers. Go through that process and then close kies (make sure it isn't still running in your system tray), open odin and try to connect in download mode again. Don't forget basic troubleshooting like trying a different USB port if the first one doesn't work the first time.......
Hello,
I was recently trying to load a stock rom on my LG540 and the process was interrupted because of a power failure. But the phone luckily booted into "download mode". I want to reflash using the procedures discussed in various posts on bricked phones, but my computer can no longer recognize the phone. The KDZ updater reports "Phone not Found". The correct drivers are installed and I am running windows 7 home edition.
Any thoughts as to how to get the computer recognize the phone?
Thanks, MN
maybe using "Run as administrator"
Try installing these drivers, they helped me when I first used KDZ. The links are from a hungarian site.
http://www.4shared.com/file/Zx52g1kl/Optimus_GT540_pc_sync.html
I think the bootloader is corrupted, it's basically "bricked", but not fully
Drivers must be the issue. Try uninstalling LG driver, reinstall it or use Windows Update to install drivers.
Bricked GT540
Maybe you can use LGDP2 ??
I'm trying to unbrick a Lenovo K3 Note. Mediatek USB appears in device manager on Windows PC, but SP flash can't see the phone to flash preloader. The drivers are OK, because I have already flashed similar phones on the same PC.
I have also tried on the Linux PC. which I regularly use for flashing.
Any ideas?
Thanks.
Hi all,
I have OP3T that just not recognized by my PC. I also have another OP3 that connects just fine to this PC. I tried dev menu and USB debug+ MTP, tried to wipe cache, install a new stock ROM downloaded from OP website, also installed the drivers in the PC.
device manager not shown anything when I connect the phone (no MTP device or Android device) and tried several cables and also another PC.
the phone was rooted until the last update (last December) and now I want to install custom ROM and I can't!
I think you want to fastboot flash a recovery?
What OS? Fastboot devices returns null?
yes, so I can install custom ROM eventually. my PC runs win 10 64X and right now my phone has stock android 8.0 (OOS).
what happens that when I connect my phone to the computer there is nothing going on- no now device in device manager and not a new driver pops, so I just can't flash recovery.
is there's an option to flash recovery without using the PC?
Saninisson said:
what happens that when I connect my phone to the computer there is nothing going on- no now device in device manager and not a new driver pops, so I just can't flash recovery.
Click to expand...
Click to collapse
No generic MTP or Android device at all? On either PC, trying different ports (I know you said you tried multiple cables - which is good trouble shooting)? And no pop-up on the phone, allowing you to select MTP (move files, or whatever it says)?
If that I the case, I tend to think the USB port is damaged.
Saninisson said:
is there's an option to flash recovery without using the PC?
Click to expand...
Click to collapse
I've seen some folks package TWRP into a bootloader-flashable zip on other devices, but haven't seen anything like that on the 3T.
More importantly, I'd say it's very risky modding the phone with custom recovery and flashing a ROM, without having fastboot and adb tools available. You can get stuck in a real bad jam doing this, with tools to recover the device. I don't recommend it.
Yes I tried it all but there is no indication besides the device is charging while connected to the USB port.
OP support say that this might be the case, but I don't know if I want to replace it since my screen is cracked and it will brake it as soon as I open the phone
I recently had these issues with Windows not having the correct drivers even after installing the oneplus drivers
Since I could not easily find these solutions I thought I should share them here so that it may be easier to find for anyone who needs it
The first problem is OnePlus 6T not showing in MSM Tool and showing in device manager as QUSB_BULK_CID:xxxx_SN:xxxxxxxx
The solution I found here https://forum.xda-developers.com/t/guide-unlock-verizon-oneplus-8-5g-uw-in2019-bootloader.4409377/
is this :
Enter EDL mode with adb reboot edl or by powering the phone off and holding both volume up and down while connecting it to a PC
Next Open device manager and if you see "QUSB_BULK_CID:xxxx_SN:xxxxxxxx"
try to update the driver, it will not find one but choose the option to search Windows Update
It should open your settings to the Windows update page
You can open this manually and you should see the option to View Optional Updates
select “Qualcomm Incorporated - Ports - 3/25/2016 12:00:00 AM - 2.1.2.2” and install it.
This should install the correct driver, replacing “QUSB_BULK_CID:xxxx_SN:xxxxxxxx” with "Qualcomm HS-USB QDLoader 9008" in device manager
After this I thought I had solved my problems but then the OP6T was not showing in fastboot
I eventually found my solution here https://forum.xda-developers.com/t/...ng-up-in-fastboot-mode-windows-10-11.4194491/
The issue is because of OnePlus having unsigned drivers and windows refusing to use them unless you disable driver signature enforcement
I recommend following the linked guide for this problem as the solution is identical for the 6T as well as the 8T, I couldn't write it any better and I wouldn't want to just copy their guide
But it essentially is as simple as disable driver signature enforcement and install the correct drivers with device manager so your device will show in fastboot
FireRattus said:
I recently had these issues with Windows not having the correct drivers even after installing the oneplus drivers
Since I could not easily find these solutions I thought I should share them here so that it may be easier to find for anyone who needs it
The first problem is OnePlus 6T not showing in MSM Tool and showing in device manager as QUSB_BULK_CID:xxxx_SN:xxxxxxxx
The solution I found here https://forum.xda-developers.com/t/guide-unlock-verizon-oneplus-8-5g-uw-in2019-bootloader.4409377/
is this :
Enter EDL mode with adb reboot edl or by powering the phone off and holding both volume up and down while connecting it to a PC
Next Open device manager and if you see "QUSB_BULK_CID:xxxx_SN:xxxxxxxx"
try to update the driver, it will not find one but choose the option to search Windows Update
It should open your settings to the Windows update page
You can open this manually and you should see the option to View Optional Updates
select “Qualcomm Incorporated - Ports - 3/25/2016 12:00:00 AM - 2.1.2.2” and install it.
This should install the correct driver, replacing “QUSB_BULK_CID:xxxx_SN:xxxxxxxx” with "Qualcomm HS-USB QDLoader 9008" in device manager
After this I thought I had solved my problems but then the OP6T was not showing in fastboot
I eventually found my solution here https://forum.xda-developers.com/t/...ng-up-in-fastboot-mode-windows-10-11.4194491/
The issue is because of OnePlus having unsigned drivers and windows refusing to use them unless you disable driver signature enforcement
I recommend following the linked guide for this problem as the solution is identical for the 6T as well as the 8T, I couldn't write it any better and I wouldn't want to just copy their guide
But it essentially is as simple as disable driver signature enforcement and install the correct drivers with device manager so your device will show in fastboot
Click to expand...
Click to collapse
Per chance, would you know if this would also apply to the OnePlus One on Linux? I recently tried to gain root access but no matter what I did, I could not get the device to show up in fastboot or as an ADB device, for that matter. I tried both USB 2.0 ports and 3.0 ports, to no avail. It's obviously not my daily driver (based on release dates, etc.) so it's not a big deal but at the same time, I don't want to root my daily driver as it has enough trouble on stock OS as it is (Google Pixel 6 Pro). I don't need to go rooting it and introducing a whole new world of hurt, thus, the desire to root my recently resuscitated OnePlus One (I got it stuck in a boot loop one or maybe even two years ago but it wasn't my daily driver then, either and just kind of a tinker device, one of a couple at that. So rather than put in the minimal amount of effort to fix it, I just tossed in a drawer until a future need demanded that I give it the time and attention necessary, which happened to occur the other night. All went super smoothly until I hit this particular roadblock alluded to above while trying to gain root using Bacon Root Toolkit. Admittedly, I haven't tried going the old-fashioned route of gaining root but mostly because I couldn't get my computer to recognize that the device was connected to it, so that was no more an option than was going the easy route with BRT.)
Edited to mention that I successfully got it out of the boot loop by flashing cm12 and that booted up no problem. I also have TWRP installed, which actually may need updating as it was the version originally installed however many years ago prior to getting it stuck in the boot loop and subsequently getting the junk drawer treatment for 1-2 years but to my knowledge that would not cause the device to not be recognized as a fastboot/ADB device...
QneEyedJack said:
Per chance, would you know if this would also apply to the OnePlus One on Linux? I recently tried to gain root access but no matter what I did, I could not get the device to show up in fastboot or as an ADB device, for that matter. I tried both USB 2.0 ports and 3.0 ports, to no avail.
Click to expand...
Click to collapse
I am not exactly sure about this but I recommend you try what is suggested here if you haven't https://technastic.com/oneplus-usb-drivers-windows-mac-linux/
sudo apt-get install android-tools-adb android-tools-fastboot
QneEyedJack said:
Edited to mention that I successfully got it out of the boot loop by flashing cm12 and that booted up no problem. I also have TWRP installed, which actually may need updating as it was the version originally installed however many years ago prior to getting it stuck in the boot loop and subsequently getting the junk drawer treatment for 1-2 years but to my knowledge that would not cause the device to not be recognized as a fastboot/ADB device...
Click to expand...
Click to collapse
to my knowledge the recovery you have installed should not effect your device being recognized in fastboot mode
You should probably update your recovery to the latest official twrp imo