Hi,
I have screwed with my smartphone (a Lenovo A760)...
I want to install a new rom and decided to erase everything.
I goes into clockworkmod / storage and format each point like /system, /boot...something, etc.
Of course, my phone won't boot anymore.
Is there a way to re-install a bootloader and a rom?
Thank you so much for helping me and sorry for my english, I speak french.
Cheers
Go here and read the whole thread.
adb devices
iZLeeP said:
Go here and read the whole thread.
Click to expand...
Click to collapse
Hi,
I've just read the 27 pages of this post, but there's no answer to my question.
ADB can't find any devices.
When I connect the phone with USB, Windows detects an unknown device, I try to install QC_Dload_driver.zip found in The lenove a706 thread.
Now Windows detects a "Lenovo HS-USB QDLoader 9008 (COM16)"
ADB can't attached my device.
My gsm is turned off and no manip like volume+ + on/off works, it stays off
What can I do?
Thank you
zzztetsuozzz said:
Hi,
I've just read the 27 pages of this post, but there's no answer to my question.
ADB can't find any devices.
When I connect the phone with USB, Windows detects an unknown device, I try to install QC_Dload_driver.zip found in The lenove a706 thread.
Now Windows detects a "Lenovo HS-USB QDLoader 9008 (COM16)"
ADB can't attached my device.
My gsm is turned off and no manip like volume+ + on/off works, it stays off
What can I do?
Thank you
Click to expand...
Click to collapse
You need to have an insecure boot image. Unpack your boot image with either of these tools: michfood (for windows) or bgcngm (for linux/cygwin). Add the following lines in the default.prop of ramdisk folder
Code:
ro.secure=0
ro.debuggable=1
persist.service.adb.enable=1
Then repack your boot image.
iZLeeP said:
You need to have an insecure boot image. Unpack your boot image with either of these tools: michfood (for windows) or bgcngm (for linux/cygwin). Add the following lines in the default.prop of ramdisk folder
Code:
ro.secure=0
ro.debuggable=1
persist.service.adb.enable=1
Then repack your boot image.
Click to expand...
Click to collapse
Thank you for helping me.
Do you know how can I inject the new boot.img?
ADB won't detect my device.
When I run adb devices, I receive an empty list
When I run adb usb or anything it says : error device not found
My Windows 7 detect my GSM as a COM port (Lenovo HS-USB QDLoader 9008 (COM17)) after install QC_Dload_driver.
One more, thank you
zzztetsuozzz said:
Thank you for helping me.
Do you know how can I inject the new boot.img?
ADB won't detect my device.
When I run adb devices, I receive an empty list
When I run adb usb or anything it says : error device not found
My Windows 7 detect my GSM as a COM port (Lenovo HS-USB QDLoader 9008 (COM17)) after install QC_Dload_driver.
One more, thank you
Click to expand...
Click to collapse
You need to flash it via SPFT, download links are here and on how to use that tool. It's the most important tool for any MTK devices.
But you need to find the correct scatter.txt file for your device to be able to use SPFT and flash the modded boot.img, otherwise, SPFT won't work properly.
EDIT: Why not just look for a flashable stock rom for your phone? Since you already have CWM/custom recovery, you can just flash that rom and your phone will be up and running.
iZLeeP said:
You need to flash it via SPFT, download links are here and on how to use that tool. It's the most important tool for any MTK devices.
But you need to find the correct scatter.txt file for your device to be able to use SPFT and flash the modded boot.img, otherwise, SPFT won't work properly.
EDIT: Why not just look for a flashable stock rom for your phone? Since you already have CWM/custom recovery, you can just flash that rom and your phone will be up and running.
Click to expand...
Click to collapse
My phone is not a Mediatek device.
It's an Qualcomm MSM8225Q Quad Core 1.2GHz
Do you know if I can use SPFT for those Qualcomm CPU?
Thank you for the time you spend to answer
zzztetsuozzz said:
My phone is not a Mediatek device.
It's an Qualcomm MSM8225Q Quad Core 1.2GHz
Do you know if I can use SPFT for those Qualcomm CPU?
Thank you for the time you spend to answer
Click to expand...
Click to collapse
I see, nope, you can't use SPFT. It's only for MTK devices.
have the same
anyone came up with a solution?
Related
My Archos 50d Helium have got brick after I flash TRWP recovery (maybe wrong version for my phone). Now it can't get into logo, recovery mode, fastboot mode. It can be realized via PC by Qualcomm HS-USB Diagnostics 9006 Drivers. There is any method to recover it? Thanks so much!
Ps: Sorry about my bad English!
Today I found a method to fix it. I guess it bricked due to TWRP format wrong to SYS_BOOT partition on my device (my fault ).
I need a SYS_BOOT.IMG or some thing like that on that partition to unbrick it.
PLS help me!
I'm not sure about Helium 50d... but you should check NeedRom anyway.
They provide their files in .pac format, so you kinda have to use their software (it's free and I didn't see any issues) to find the file location inside. Navigate to the location and it should have the .img file at that location. It basically extracts it into a temp directory and you just have to go find it.
Once you've done that then it's a case of using ADB or Fastboot to flash it over. Not sure if you can use the program itself, it's possible. Unfortunately, it's buggy on Linux so...
Hello all, i recently picked up a ulefone armor 2s and i was attempting to root it and i have made a mistake and now i don't know what to do as the phone is in a bricked state at the moment.
I followed the guide here
https://forum.xda-developers.com/android/development/root-ulefone-armor-2-easy-rooting-t3780055
and have got nothing as TWRP did not load on to the device properly and i am stuck in a boot loop. i am thinking that somehow i made a big mistake and deleted the recovery somehow and i am unsure on how to load a recovery back on.. I have rooted phones before so i have a basic understanding of ow it works but i dont know how to fix this...
Please Help and thank you for helping
-B
Try using pc.. if its still detected by the system..
If yes check the processor of your ulephone if its mediatek or qualcomm. If its MTK use sp flash tools else use qualcomm flash tools.
Even if the bootloader is missing, its the preloader that will be there. And flash tools are the way they can make use of preloader. Make sure you have proper drivers installed in your system.
If you have a working recovery, install it via flash tools so the device can rise from the dead..
abhinavp649 said:
Try using pc.. if its still detected by the system..
If yes check the processor of your ulephone if its mediatek or qualcomm. If its MTK use sp flash tools else use qualcomm flash tools.
Even if the bootloader is missing, its the preloader that will be there. And flash tools are the way they can make use of preloader. Make sure you have proper drivers installed in your system.
If you have a working recovery, install it via flash tools so the device can rise from the dead..
Click to expand...
Click to collapse
Thank you for this, I got the device back up and running... But I'm missing a bootloader now. Any thoughts on how to flash it?
Hello friends,
I am following this guide here to try to root my WP7:
http://androidbiits.com/root-oukitel-wp1-wp2-wp7-easily/
Everything works fine, except for the very last step, when I am supposed to flash the patched .img.
I issue the command
fastboot flash boot magisk_patched.img
and all I am getting is "Waiting for device".
The screen remains in "FASTBOOT mode..." and nothing else happens.
What am I doing wrong? I would appreciate some help, please.
Thank you.
Did you use the MTK USB-drivers?
jwoegerbauer said:
Did you use the MTK USB-drivers?
Click to expand...
Click to collapse
Hi, thanks for the reply. I already have the MTK USB_All_v1.0.8 driver installed as my previous phone was also MKT based.
I can see Windows installing different types of drivers when i connect my phone, so I assumed I was alright.
Perhaps you or anyone else can link for me the correct MKT USB drivers to use? Googling I found different links that seem to be different.
I also tried adb from my Mac too, same result: nothing seems to happen.
Thanks!
@fabioganga
For phones with Mediatek MT65xx chips it exists the so-called Mediatek MT65xx USB VCOM driver which claims that fastboot problems no longer occur.
Look inside here.
jwoegerbauer said:
@fabioganga
For phones with Mediatek MT65xx chips it exists the so-called Mediatek MT65xx USB VCOM driver which claims that fastboot problems no longer occur.
Look inside here.
Click to expand...
Click to collapse
Thanks @jwoegerbauer for the quick reply, much appreciated. As far as I ma maware the processor is a 6779, but the page refers to MT65xx drivers. Are they the same drivers?
No joy at all with Windows, not even with the drivers the article mentioned features.
I tried again with my Mac instead, installing adbd and fastboot there.
I am finally getting the phone to respond,
howver, the bootlaoader in my case was unlocked, so I first had to type
fastboot flashing unlock (warning! it deletes all data!) and confirm it with volume UP.
Then, after the device reboots to fastboot, I can finally type
fastboot flash boot magisk_patched.img
and it flashes correctly.
Hello!
I need to downgrade Android 10 to Android 9 on my Oppo F11 Pro. I've flashed many roms till now on other devices. This one is a bit *cough*
I have the .ozip file of the Android 9 rom, need to flash.
Default recovery mode of ColorOS doesnt work ofc, doesnt support downgrading.
After converting .ozip to .zip and extracting the files, SP Flash Tool or such tools arent able to get the files somehow They dont load it up, even not the scatter files.
So I think I should first unlock the bootloader, which I've been trying to today.
Doing the "adb devices" doesnt list my device, guess I need the drivers.
Downloaded drivers but they are in .inf format, which Ive been unable to install (with my "search the internet and do it" ways.
"The inf file you selected does not support this method of installation". And thru administrator cmd, its Installation failed.
Im so confused with those drivers Idk which ones to install.
One driver I've pasted on hastebin as.. hastebin[dot]com/abopesexej.shell
Couls someone pls help me out? Im hitting the wall atm
Neon111 said:
Doing the "adb devices" doesnt list my device, guess I need the drivers.
Downloaded drivers but they are in .inf format, which Ive been unable to install (with my "search the internet and do it" ways.
"The inf file you selected does not support this method of installation". And thru administrator cmd, its Installation failed.
Im so confused with those drivers Idk which ones to install.
One driver I've pasted on hastebin as.. hastebin[dot]com/abopesexej.shell
Couls someone pls help me out? Im hitting the wall atm
Click to expand...
Click to collapse
Don't mix up USB-driver and ADB-driver and/or Fastboot-driver: totally different drivers.
A USB-driver is a file that allows an USB hardware device to communicate with the operating system of a computer. This driver is implemented in all operating systems by default.
ADB-driver and/or Fastboot-driver is a “bridge” for Android developers / hackers to work out bugs in their Android applications and/or modify existing Android OS. This is done by connecting an Android device that runs the software through a PC, and feeding appropriate commands in its terminal.
Don't use any ADB-driver and/or Fastboot-driver as they are hundreds of times published on the WEB - and even here on XDA. Only make use of those drivers officially offered by your device's OEM/Carrier.
Comment withdrawn by author.
(When "adb devices" shows the device serial)
When i try to do "adb reboot bootloader",
The phone reboots and says
"The serial is not matched
fastboot_unlock_verify fail"
What should I do? :u
And not being able to use fastboot.. I cant find related drivers on the internet for that purpose.. I downloaded and installed what I could (fastboot commands not working.. shows <waiting for device> )
Neon111 said:
(When "adb devices" shows the device serial)
When i try to do "adb reboot bootloader",
The phone reboots and says
"The serial is not matched
fastboot_unlock_verify fail"
What should I do? :u
Click to expand...
Click to collapse
Generally speaking, the serial number as reported by ADB will be different to Fastboot as determined by:
Manufacturer
Make and model of device in question
Android version
Fastboot, on the other hand, since there's no ADB loaded, instead, uses a rudimentary USB protocol tied in with Android's boot-loader, the serial number will be different.
EDIT:
Neon111 said:
And not being able to use fastboot.. I cant find related drivers on the internet for that purpose.. I downloaded and installed what I could (fastboot commands not working.. shows <waiting for device> )
Click to expand...
Click to collapse
Your Oppo F11 Pro is based on Mediatek chipset. IMO you instead of Fastboot driver have to make use of Oppo F11 Pro Mediatek driver - a specialized version of general Fastboot driver - what is compatible with SP Flash Tool, MTK Flash Tool, SP MDT Tool and SN Write Tool.
DL: https://gsmusbdriver.com/oppo-f11-pro
jwoegerbauer said:
Your Oppo F11 Pro is based on Mediatek chipset. IMO you instead of Fastboot driver have to make use of Oppo F11 Pro Mediatek driver - a specialized version of general Fastboot driver - what is compatible with SP Flash Tool, MTK Flash Tool, SP MDT Tool and SN Write Tool.
DL: https://gsmusbdriver.com/oppo-f11-pro
Click to expand...
Click to collapse
But I do not have flash files related to the listed programs..
Everywhere I could find only an .ozip file, which I turned into a .zip from a program I found on here. The zip when extracted gave me all the .img files and scatter.txt, but the scatter.txt doesnt load up in SP Flash Tool and the like.
Neon111 said:
But I do not have flash files related to the listed programs..
Everywhere I could find only an .ozip file, which I turned into a .zip from a program I found on here. The zip when extracted gave me all the .img files and scatter.txt, but the scatter.txt doesnt load up in SP Flash Tool and the like.
Click to expand...
Click to collapse
Were you able to unlock your bootloader? I found various tutorials of extracting boot image from the ozip files. But Veterans are saying oppo doesn't let people unlock bootloader.
i bricked My Alcatel 916a and pls i need a stock rom for 916a-2EAVCO1-S50 and the branding is "Claro Colombia" and how flash the stock rom and drivers pls need help
Pachof said:
i bricked My Alcatel 916a and pls i need a stock rom for 916a-2EAVCO1-S50 and the branding is "Claro Colombia" and how flash the stock rom and drivers pls need help
Click to expand...
Click to collapse
Can you access fastboot or bootloader? Have you installed any custom recovery image before it happened?
I have packaged the firmware, flash tool and the drivers in the zip file below.
Install Mediatek Drivers First.
Then Restart your computer.
Open Device Manager and then switch off the device and connect it to your computer and see if the device is detected in PORTS section of device manager as MTK Preloader if not then press and hold both volume keys and then connect it to computer and see if the device is detected.
Open SP Flash Tool load the scatter firmware and click on flash.
Download firmware.
Ohdude said:
Can you access fastboot or bootloader? Have you installed any custom recovery image before it happened?
Click to expand...
Click to collapse
no i dont have access to fastboot or bootloader
mvikrant97 said:
I have packaged the firmware, flash tool and the drivers in the zip file below.
Install Mediatek Drivers First.
Then Restart your computer.
Open Device Manager and then switch off the device and connect it to your computer and see if the device is detected in PORTS section of device manager as MTK Preloader if not then press and hold both volume keys and then connect it to computer and see if the device is detected.
Open SP Flash Tool load the scatter firmware and click on flash.
Download firmware.
Click to expand...
Click to collapse
i tested and get a error "Storage type mismatch, scrater storage type is HW_STORAGE_NAND target storage type is HW_STORAGE_NONE"