Related
Hi there, I've been browsing through the threads related to unbricking of the Nexus 6P stuck in qualcomm hs-usb qdloader 9008 mode, really desperate to get my device working again if even possible however I've tried for about four days now different ways and files and I've had no luck.
My bootloader is locked and no ADB etc managed to get my device showing as the 9008 port so I think it's stuck in EDL.
Following guides, this is the furthest I've yet to get (In screenshot)
Could anyone shed some light and some assistance please? what am I doing wrong!?
attempted to apply for heat some to the device then re flash ?
blackcell1 said:
attempted to apply for heat to the device then re flash ?
Click to expand...
Click to collapse
Sorry, I don't quite understand what you mean?
Clarkeofcurtis said:
Sorry, I don't quite understand what you mean?
Click to expand...
Click to collapse
Use a hairdryer to warm up the back of the phone.
Are you pulling my leg? Warm it up then reflash?
nah im not trying to make you destroy your phone, being rather serious with this method. i use it on a daily basis to solve phones that fail during restoring factory images. i wouldn't know how long to give it with a hair dryer as i have access to a heat gun/heat mats .
just think of it as a cheap mans re balling method
blackcell1 said:
nah im not trying to make you destroy your phone, being rather serious with this method. i use it on a daily basis to solve phones that fail during restoring factory images. i wouldn't know how long to give it with a hair dryer as i have access to a heat gun/heat mats .
just think of it as a cheap mans re balling method
Click to expand...
Click to collapse
Sorry haha, I'm a noob with most of this android stuff bar rooting and flashing a few devices prior! I shall give it a go now and get back to you - thank you for the advice
Clarkeofcurtis said:
Sorry haha, I'm a noob with most of this android stuff bar rooting and flashing a few devices prior! I shall give it a go now and get back to you - thank you for the advice
Click to expand...
Click to collapse
good luck, id give it a good couple of minutes on the highest setting, just so its a little hot to the touch. and attempt the flashing of the files when its still hot/warm.
blackcell1 said:
good luck, id give it a good couple of minutes on the highest setting, just so its a little hot to the touch. and attempt the flashing of the files when its still hot/warm.
Click to expand...
Click to collapse
thank you so much that worked, it has said flash successful, first time I got a google logo but now nothing, what would be my next step please?
if the bootloader is unlocked then you can directly flash the firmware. but if its not google "nexus ota" and then on your phone jump into the recovery and check the firmware model number and download the same ota and adb sideload it.
im not 100% sure on the next step as I've never had a nexus 6p with a dead bootloader. but thats what id do.
---------- Post added at 04:50 PM ---------- Previous post was at 04:49 PM ----------
but from my personal experience with having to heat a phone up to restore factory images, it kinda means the phone is nearing the end of its life and id start thinking about buying your next phone before it sh*ts the bed.
blackcell1 said:
if the bootloader is unlocked then you can directly flash the firmware. but if its not google "nexus ota" and then on your phone jump into the recovery and check the firmware model number and download the same ota and adb sideload it.
im not 100% sure on the next step as I've never had a nexus 6p with a dead bootloader. but thats what id do.
Click to expand...
Click to collapse
Thank you for the reply and continuing to help, after seeing the google logo just once I'm getting nothing again - I'm even more determined now though as It's been dead for 2 months so this is the furthest I've gotten - the application of heat is what did it for me and fixed the error I was getting, can't get into recovery now though holding power + down etc
Clarkeofcurtis said:
Thank you for the reply and continuing to help, after seeing the google logo just once I'm getting nothing again - I'm even more determined now though as It's been dead for 2 months so this is the furthest I've gotten - the application of heat is what did it for me and fixed the error I was getting, can't get into recovery now though holding power + down etc
Click to expand...
Click to collapse
yeah can you access the bootloader at all ? does it say that the bootloader is locked ? from trying to restore LG's it sometimes has to be re heated a few times, but yeah if you need to re heat it to get further into the phone then its pretty much a lost cause. the only reason i do it is to remove the data so we can resell the device.
blackcell1 said:
yeah can you access the bootloader at all ? does it say that the bootloader is locked ? from trying to restore LG's it sometimes has to be re heated a few times, but yeah if you need to re heat it to get further into the phone then its pretty much a lost cause. the only reason i do it is to remove the data so we can resell the device.
Click to expand...
Click to collapse
I can get into the andriod screen where you can select recovery and such, with the BL, Baseband product variation and such, where should I go from here?
Oh right, so even once restored to firmware, will it be useless do you think if I can even manage to?
Clarkeofcurtis said:
I can get into the andriod screen where you can select recovery and such, with the BL, Baseband product variation and such, where should I go from here?
Oh right, so even once restored to firmware, will it be useless do you think if I can even manage to?
Click to expand...
Click to collapse
Sorry if you can't access the recovery from the bootloader and its in locked state then your a member of the lovely group of BLOD (bootloader of death) if you hit recovery does it show a little android logo and sit there?
Sorry for the late reply
blackcell1 said:
Sorry if you can't access the recovery from the bootloader and its in locked state then your a member of the lovely group of BLOD (bootloader of death) if you hit recovery does it show a little android logo and sit there?
Sorry for the late reply
Click to expand...
Click to collapse
I believe so, I can just about get into the bootloader at the best of times and when I do I can select options but once proceeding to start said mode phone freezes so can't get into recovery mode :/
Thank you for your continuous help, only way i can get it into bootloader is by heating it up so does that mean for the device to ever work It'll need heat every time? looking like a spares and repairs listing on ebay
Clarkeofcurtis said:
I believe so, I can just about get into the bootloader at the best of times and when I do I can select options but once proceeding to start said mode phone freezes so can't get into recovery mode :/
Thank you for your continuous help, only way i can get it into bootloader is by heating it up so does that mean for the device to ever work It'll need heat every time? looking like a spares and repairs listing on ebay
Click to expand...
Click to collapse
Hello....
How did you manage to get in to EDL mode..? I'm really curious. With stock bootloader? Since you can't access recovery
Also what is exactly displayed in Windows device manager?
You are using an outdated QFil version... It is from 2014 àr 2015.
Do a google search with: QPST_2.7.453.0 . This version seem to be from 2016.
Use the first link from the result. I analysed the files with virustotal, those seem clean or malware...
Also when plugging your usb cord to your PC, does your phone vibrate? Or does the LED blink in red?
You may have to press power button when plugging the usb cord or press power button for a certain amount of time before you plug the usb cord. I'm not completly sure, but your phone may not be in the "proper" EDL state to accept the QFil flash.
Good luck... :good:
Is it possible to send me the guide you used? Thanks.
Clarkeofcurtis said:
Hi there, I've been browsing through the threads related to unbricking of the Nexus 6P stuck in qualcomm hs-usb qdloader 9008 mode, really desperate to get my device working again if even possible however I've tried for about four days now different ways and files and I've had no luck.
My bootloader is locked and no ADB etc managed to get my device showing as the 9008 port so I think it's stuck in EDL.
Following guides, this is the furthest I've yet to get (In screenshot)
Could anyone shed some light and some assistance please? what am I doing wrong!?
Click to expand...
Click to collapse
Hey there sorry for slow replies, will be back on my desktop in an hour I'll send you links for what I followed and such, I think the only reason my device was in EDL mode was due to a hardware fault? As my device is faulty indefinitely as I had to use a hairdryer to warm it up while flashing this then allowed it to enter firehose state which a lot of people seem to error with - after all my attempts and research I'm to velieve there's a fault with the phone itself the only way I could get it to even power up was applying heat to it after removing the back panel
As blackcell said deballing or something? Worked a treat!
Furthest I've managed to get now is into my boot loader however everything is locked - when I press enter recovery my handset just freezes ?
5.1 said:
Hello....
How did you manage to get in to EDL mode..? I'm really curious. With stock bootloader? Since you can't access recovery
Also what is exactly displayed in Windows device manager?
You are using an outdated QFil version... It is from 2014 àr 2015.
Do a google search with: QPST_2.7.453.0 . This version seem to be from 2016.
Use the first link from the result. I analysed the files with virustotal, those seem clean or malware...
Also when plugging your usb cord to your PC, does your phone vibrate? Or does the LED blink in red?
You may have to press power button when plugging the usb cord or press power button for a certain amount of time before you plug the usb cord. I'm not completly sure, but your phone may not be in the "proper" EDL state to accept the QFil flash.
Good luck... :good:
Click to expand...
Click to collapse
Thanks pal if you check last post I wrote about my EDL mode forgot to tag you my apologies, as for my LED I've never seen that light up since I bricked it, even when google logo came up etc and while in the boot loader
Clarkeofcurtis said:
Thanks pal if you check last post I wrote about my EDL mode forgot to tag you my apologies, as for my LED I've never seen that light up since I bricked it, even when google logo came up etc and while in the boot loader
Click to expand...
Click to collapse
Light usually a red LED blink while in proper EDL state as far as I know. Could be something else on the N6P. Well, it looks like you are SOL. Sorry, I don't know what else to say, since you exhausted all possibilities...
Good luck...
Hello guys, i've got really hard problem with my j5 which is probably totally bricked. But. there is but, i can access recovery mode and connect it to the ADB, but still, aint that easy. While trying to flash new ROM, im getting up to 40 % and its shows "e:signature verification failed" after that it gets to 92% and stops. Total xfer: 2.00x on phone it shows as "E:failed to find /misc partition".
I've been trying literally everything.
Weird thing, cannot open adb shell, "error:closed" been trying killing server, starting server etc.
Most weird thing is J5 CANNOT ACCESS THE "DOWNLOAD MODE" which is the biggest problem in my case.
apart from that, i've got no TWRP or CMW installd, only stock recovery mode, whatever option im trying to get into, always gets same info "E:Failed to find /misc partition".
what else... I've been trying to make SD card as bootable device with android on it, if you've got any ideas about that, im happy to hear.
been trying several rooms, stock, lineage, other customs.
Tried several versions of adb..
sometimes adb shows info "deamon not started" which after i've got communicate that deamon started succesfully and transfered to port 500 something.
Please guys, help me with that. I've wasted about 60 over hours now :crying: getting sick.
anyone that could help ?
tropicca said:
anyone that could help ?
Click to expand...
Click to collapse
Hi there
Are the OEM luck and usbdebuge enable?
Did you tried to flash pit file with Odin?
And how did you wanted to install stock rom without download mode?!(is there any way?)
And the last what did you do to get this?
amirizad_7436 said:
Hi there
Are the OEM luck and usbdebuge enable?
Did you tried to flash pit file with Odin?
And how did you wanted to install stock rom without download mode?!(is there any way?)
And the last what did you do to get this?
Click to expand...
Click to collapse
I was not the first person that touched the phone.
i dont know if they are enabled, no access to the android at all.
i've been trying to push custom rom/ twrp etc. through adb.
There are plenty of samsung tools that allows you to do it, but requires download mode... so thats the reason why I'm asking.
Look up usb jigs. You can make one easily enough with a couple resistors and a usb lead. Here is a guide on how to make one https://www.instructables.com/id/USB-JIG-to-give-life-to-your-Bricked-mobile/#step1
Or you can buy one on like a cheap site somewhere.
Once the jig gets plugged into the device it force boots the device into download mode and you should be able to continue from there
garylawwd said:
Look up usb jigs. You can make one easily enough with a couple resistors and a usb lead. Here is a guide on how to make one https://www.instructables.com/id/USB-JIG-to-give-life-to-your-Bricked-mobile/#step1
Or you can buy one on like a cheap site somewhere.
Once the jig gets plugged into the device it force boots the device into download mode and you should be able to continue from there
Click to expand...
Click to collapse
already 've got one, not working ;/ works perfect on j3 2016
Phone was hard bricked using standart program Odin, it was bricked because i added 1 flash file needed, to 4 sections BL,AP,CP,CSC same file for each section, it's supposed to be only at AP, and its flashed with green PASS, what is surprising to me that nothing prevented to flash it, after it pass, phone black screen, no recovery or anything, just common hard brick "qhsusb_bulk" thing.
I tried load recovery from microsd 32gb, but nothing happens at all, still black screen, maybe i need correct debrick image?
What other options are for this phone?
Sorry to not have any help but I've done the exact same thing as you have to the exact same phone. Ticked all four sections in Odin instead of just AP. Got the green PASS and then the phone went dead. I must have misunderstood something in the instructions I was reading but it was too late. D'oh. Hard brick. I've been messing around with debrick files trying to get it to boot but not having any luck so far. I was using Odin in the first place to try and bring my phone back from "Custom Binary Locked by FRP" which randomly happened to my phone when I put it on after not using it for a while, never used any root stuff before now (the only other person I could find online who got the FRP error without rooting anything had eMMC failure, so my phone could be toast anyway.) I'll come back here if I have any luck with the debricking files.
DeTovergieter said:
Sorry to not have any help but I've done the exact same thing as you have to the exact same phone. Ticked all four sections in Odin instead of just AP. Got the green PASS and then the phone went dead. I must have misunderstood something in the instructions I was reading but it was too late. D'oh. Hard brick. I've been messing around with debrick files trying to get it to boot but not having any luck so far. I was using Odin in the first place to try and bring my phone back from "Custom Binary Locked by FRP" which randomly happened to my phone when I put it on after not using it for a while, never used any root stuff before now (the only other person I could find online who got the FRP error without rooting anything had eMMC failure, so my phone could be toast anyway.) I'll come back here if I have any luck with the debricking files.
Click to expand...
Click to collapse
This is basicly exactly my situation you mentioned from Odin to FRP lock screen 1:1 match, i was thinking that eMMC failed to, becouse tried Sdcard method, qfil flashing, absolutly nothing works, last thing im waiting to try is usb JIG i ordered, if you find any information or do any progress, be sure to share it, i will do it to if i find anything success, but if JIG wont work, than i suspect that eMMC failed, or phone have liquid damage somewhere, becouse USB sometimes disconnected randomly multiple times, and show Unknown device error on win10, also i took phone to repair shop, said i need reflash becouse bricked, he didnt fixed to, maybe not experenced at that,only things like replace screens
Well, I'm sure you, like me, have made absolutely zero progress on this device since nothing seems to work with it. The J5 SD cards don't work, you can even make your own debrick from a stock rom, but these didn't work for me either. No response at all of any kind to any SD card.
Presumably it should work like in this video, the LG here isn't responsive to anything, shows up as "Qualcomm HS-USB QDLoader 9008" then the SD card goes in and BOOM, device back. Also, that guy seems to be in the "old QDLoader mode" just like us so in theory I don't see any reason for the SD card to not work, maybe we just haven't found the right one?
Annoyingly, if Samsung ever released their files like the firehose (which I doubt they would) or they got leaked, then QFIL would work. But as it stands we don't have those files so we can't do anything with QPST/QFIL except see that it's the only thing that can communicate with the J5 in that state.
I'm not sure what a USB jig does, but looking on Google it seems like it just simulates button presses to hold the combination for Download Mode?
DeTovergieter said:
Well, I'm sure you, like me, have made absolutely zero progress on this device since nothing seems to work with it. The J5 SD cards don't work, you can even make your own debrick from a stock rom, but these didn't work for me either. No response at all of any kind to any SD card.
Presumably it should work like in this video, the LG here isn't responsive to anything, shows up as "Qualcomm HS-USB QDLoader 9008" then the SD card goes in and BOOM, device back. Also, that guy seems to be in the "old QDLoader mode" just like us so in theory I don't see any reason for the SD card to not work, maybe we just haven't found the right one?
Annoyingly, if Samsung ever released their files like the firehose (which I doubt they would) or they got leaked, then QFIL would work. But as it stands we don't have those files so we can't do anything with QPST/QFIL except see that it's the only thing that can communicate with the J5 in that state.
I'm not sure what a USB jig does, but looking on Google it seems like it just simulates button presses to hold the combination for Download Mode?
Click to expand...
Click to collapse
Im still researching, i even used same method to make own debrick image, i tried multiple versions, latest 6.1 android, than latest 5.1 android, even tried first firmware 5.1 released, still absolutly no reaction to phone, not even vibrate or anything, tried press multiple times button combinations, tried few SD cards, 32gb with 10speed, absolutly nothing at all, looks like we are on exactly same situation, im stil trying things, now probably will be USB jig, combination with MicroSD, im just waiting on few USB jigs i ordered, for few dollars, its usefull to have anyway for other situations, so if i found any sign if life i will definetly share here, becouse if my would work, definetly your would work to, i have no idea why its does absolutly nothing, i tried even diffrent battery from other phone, still same, and before i tried use Qualcom flash QFIL, try flash some unofficial firmwares, but looks like Samsung phones not very good at that, only LG or others its designed for that, basicly no infomation about Samsung phones, even no repair services online.so if you find any progress be sure to share it, i would definetly do it, if i discover anything.
I have the same problem as you. My sister was using a Samsung Galaxy J5 (2015) and the battery was growing bigger meaning that it could be dangerous. So we left that one smartphone in the corner without a battery. Well, after my Nexus 5 had a problem too, I decided to get back to my J5 that I gave to my sister. I had to buy a new battery for it so I did. When the battery arrived, I tried to turn it on, but it wasn't turning on. I connected it using a USB cable in my computer but instead of displaying the device's name, it displayed as QHSUSB_BULK. When I was asked to install drivers for the device, I did so, and the name changed to Qualcomm HS-USB QDLoader 9008 (COM8). I went it to a repair shop and they said it might be the freakin' screen!!! I mean, what? People all over the Internet having the same issue with me say that it is a hard brick. Hard brick has NOTHING to do with the screen, correct me if I am wrong. I also saw somewhere that I can only fix my device if only I replace the motherboard entirely (because replacing specific part of the motherboard is kind of dangerous and can cause even more problems...) I have no idea. I need help. I want to try flashing firmware with my SD card, but I have no image for my SM-J500FN device. I feel hopeless. They encourage me to buy a new smartphone. Something "modern". But what I know is that today's devices are more "brick-able" that those of old times. I want to install TWRP Recover again and finally root my device. I know how to do that to my Galaxy J5, but I can't do that when my smartphone is not turning on at all. It doesn't even vibrate!!
Retr0.Hacker said:
I have the same problem as you. My sister was using a Samsung Galaxy J5 (2015) and the battery was growing bigger meaning that it could be dangerous. So we left that one smartphone in the corner without a battery. Well, after my Nexus 5 had a problem too, I decided to get back to my J5 that I gave to my sister. I had to buy a new battery for it so I did. When the battery arrived, I tried to turn it on, but it wasn't turning on. I connected it using a USB cable in my computer but instead of displaying the device's name, it displayed as QHSUSB_BULK. When I was asked to install drivers for the device, I did so, and the name changed to Qualcomm HS-USB QDLoader 9008 (COM8). I went it to a repair shop and they said it might be the freakin' screen!!! I mean, what? People all over the Internet having the same issue with me say that it is a hard brick. Hard brick has NOTHING to do with the screen, correct me if I am wrong. I also saw somewhere that I can only fix my device if only I replace the motherboard entirely (because replacing specific part of the motherboard is kind of dangerous and can cause even more problems...) I have no idea. I need help. I want to try flashing firmware with my SD card, but I have no image for my SM-J500FN device. I feel hopeless. They encourage me to buy a new smartphone. Something "modern". But what I know is that today's devices are more "brick-able" that those of old times. I want to install TWRP Recover again and finally root my device. I know how to do that to my Galaxy J5, but I can't do that when my smartphone is not turning on at all. It doesn't even vibrate!!
Click to expand...
Click to collapse
Im sure its hardware failure, nothing can be done, i tried alot things, nothing worked, not even small progress, phone just dead, tried usb jig, tried to use every recover image from all firmwares, nothing worked, only fix to this phone is replace motherboard, but to access motherboard you need remove screen first, i give up on this phone, not worth time, tried everything, ether motherboard replacing or just get new phone
Vkrs said:
Im sure its hardware failure, nothing can be done, i tried alot things, nothing worked, not even small progress, phone just dead, tried usb jig, tried to use every recover image from all firmwares, nothing worked, only fix to this phone is replace motherboard, but to access motherboard you need remove screen first, i give up on this phone, not worth time, tried everything, ether motherboard replacing or just get new phone
Click to expand...
Click to collapse
Well, they suggest me to get a new smartphone because if I get to replace the motherboard it will be too expensive and maybe not worth it... I guess I will have to give up too, even if I loved that one... Thank you friend.
Retr0.Hacker said:
Well, they suggest me to get a new smartphone because if I get to replace the motherboard it will be too expensive and maybe not worth it... I guess I will have to give up too, even if I loved that one... Thank you friend.
Click to expand...
Click to collapse
Probably happened same thing like to you, i received phone from female, who used daily, it was already had this issue, definetly she didnt do anything software related things like flash, so im guessing hardware failed, thats why nothing you can do, only fix is most likely motherboard replacement, but at this point is not worth it, becouse will cost half phone price, so i rip"ed this phone, writed it off, its laying for parts, did what i can, tried all methods, usb jig worked on every samsung i have, s5, j5 2016, but execpt this one, this means is definetly phone dead, also tried to recovery with microsd, every single firmware, from 5 android to 6, all versions, created recovery, and none of them worked, also tried on few microsds, and absolutly was no progress, not even vibrate, dead entire time
Hi all,
So basically I was trying to install Pixelexperience to my Note 7 today and I messed it up big time. So I was having some issues with TWRP and one of the solutions (according to posts I found on Google) was to update the phone firmware. So I went to do that. Downloaded the lavander firmware for my Note 7, put it in the folder with other stuff I was downloading. One of these was firmware for Redmi A5 (which I didn't notice) and ended up flashing that. Now my phones screen is dead (I guess the rest of it also?). When I plug it in to PC the PC produces the sounds that something connected but running fastbood / adb devices doesn't return anything. I tried multiple times booting to fastboot / recovery but I have no idea when the phone is on or off. So it just produces sound on PC that it disconnected and connected like 1 second after but nothing still shows up on fastboot.
Did anyone had similiar issue and is there anything I can do? Or should I go look for a new phone?
Thank you for your time
Try to flash the whole rom again.
VD171 said:
Try to flash the whole rom again.
Click to expand...
Click to collapse
Well, I thought about that, but I don't know how to flash it since it seems I can't boot into fastboot. I've tried countless times and failed every time
vivida said:
Well, I thought about that, but I don't know how to flash it since it seems I can't boot into fastboot. I've tried countless times and failed every time
Click to expand...
Click to collapse
Try any tool:
Xiaomitool: https://www.xiaomitool.com/V2/Miflashpro: https://miflashpro.com/Miflashtool: https://xiaomiflashtool.com/
VD171 said:
Try any tool:
Xiaomitool: https://www.xiaomitool.com/V2/Miflashpro: https://miflashpro.com/Miflashtool: https://xiaomiflashtool.comI have tried but I just can't get the devices to boot into fastboot and I have no idea in what state it is since the screen doesn't show anything
Click to expand...
Click to collapse
Can you enter in recovery ?
VD171 said:
Can you enter in recovery ?
Click to expand...
Click to collapse
No, the same thing is happening. I just get the sound on PC and that's about it. It isn't recognized by the PC or any software that I tried to use
Try to get new cable and it will work
Eslamloka said:
Try to get new cable and it will work
Click to expand...
Click to collapse
After that's make your phone in edl mode then flash stock miui with miflash tool
Eslamloka said:
After that's make your phone in edl mode then flash stock miui with miflash tool
Click to expand...
Click to collapse
I receive cannot receive hello packet error message now
vivida said:
I receive cannot receive hello packet error message now
Click to expand...
Click to collapse
Sorry but i can't understand,,,is u tried to change a cable and it's working or not
Eslamloka said:
Sorry but i can't understand,,,is u tried to change a cable and it's working or not
Click to expand...
Click to collapse
I tried changing it but it doesn't work. The problem is I can't flash anything on MiFlash because it requires something like technicians account
vivida said:
I tried changing it but it doesn't work. The problem is I can't flash anything on MiFlash because it requires something like technicians account
Click to expand...
Click to collapse
before miflash firstly you must connect your phone with pc or laptop
Hello everyone, so here i am trying to flash a friend's a1000, but unfortunately, i'm unable to do so because when i try to enter the bootloader by holding the volume up key before plugging in the usb cable to start the process, it only connects to the computer for about 9 seconds, and then automatically disconnects, i get a coloured screen afterwards, and i would be forced to restart the device, i first suspected that it was the cable, but i was wrong, since i've already tried a bunch of cables, all with the same exact result, i also used 3 different computers, and i still got the same result, please respond if you have any idea.
Sisine said:
Hello everyone, so here i am trying to flash a friend's a1000, but unfortunately, i'm unable to do so because when i try to enter the bootloader by holding the volume up key before plugging in the usb cable to start the process, it only connects to the computer for about 9 seconds, and then automatically disconnects, i get a coloured screen afterwards, and i would be forced to restart the device, i first suspected that it was the cable, but i was wrong, since i've already tried a bunch of cables, all with the same exact result, i also used 3 different computers, and i still got the same result, please respond if you have any idea.
Click to expand...
Click to collapse
you need drivers to flash it. i flashed mine in september 2021 and most drivers didnt work. i ended up getting drivers with the same name for a diffrent phone and the flash worked. so try doing that it might end up working. i dont how i did it but it was really hard
Vuk1152 said:
you need drivers to flash it. i flashed mine in september 2021 and most drivers didnt work. i ended up getting drivers with the same name for a diffrent phone and the flash worked. so try doing that it might end up working. i dont how i did it but it was really hard
Click to expand...
Click to collapse
You're right, it is hard indeed, i've already tried so many drivers, i think i'm giving up lol, thanks a lot for the reply, i really didn't expect one since that specific phone is ages old by now !
Sisine said:
You're right, it is hard indeed, i've already tried so many drivers, i think i'm giving up lol, thanks a lot for the reply, i really didn't expect one since that specific phone is ages old by now !
Click to expand...
Click to collapse
thanks. i replied this cause i have the same phone which i want to custom rom but there arent any roms available.(if you have any roms, please let me know)i can try to find you the youtube video i used for the drivers if you tell me what they are called. (if you want to xd) i think its something like "mediatek drivers"
Vuk1152 said:
thanks. i replied this cause i have the same phone which i want to custom rom but there arent any roms available.(if you have any roms, please let me know)i can try to find you the youtube video i used for the drivers if you tell me what they are called. (if you want to xd) i think its something like "mediatek drivers"
Click to expand...
Click to collapse
I appreciate that, i'll let you know if i find a compatible rom for the device, i think the drivers are called CDC drivers if i remember correctly, i don't have the files, but i'm almost sure it's CDC, i'll be grateful if you can send me a link to that video.
Sisine said:
I appreciate that, i'll let you know if i find a compatible rom for the device, i think the drivers are called CDC drivers if i remember correctly, i don't have the files, but i'm almost sure it's CDC, i'll be grateful if you can send me a link to that video.
Click to expand...
Click to collapse
i dont think i ever used that cdc thing when flashing that phone. im pretty sure i used https://firmwarefile.com/lenovo-a1000 to get the stock firmware and just searched up "(driver name) download" on youtube and used some indian guys tutorial. you can try this video if you havent alredy (for the cdc driver)
Vuk1152 said:
i dont think i ever used that cdc thing when flashing that phone. im pretty sure i used https://firmwarefile.com/lenovo-a1000 to get the stock firmware and just searched up "(driver name) download" on youtube and used some indian guys tutorial. you can try this video if you havent alredy (for the cdc driver)
Click to expand...
Click to collapse
I'll try that one, thank you.
Sisine said:
I'll try that one, thank you.
Click to expand...
Click to collapse
np
Do you guys still have the files?
I managed to get the proper drivers and the phone is seen by the computer and I manage to flash it , but the phone is completly dead after the flash .
The power button wont do anything, plugging it into the charger doesnt do anything, I can only reflash it by connecting it to the pc while holding the volume up & down buttons.
Checking on old forums, aparently there are two versions of the phone , single sim and dual sim.
Also the revision number seems to be important for some reason, so mines is dual sim , revision 61 .
I believe this was the firmware that was on it previously, although the phone remained stuck at the boot logo : a1000_usr_s29798_1511241708_sprd7731_ro , but i cant find it anywhere , so I flashed the one you guys had , but now the phone is a dead brick after the flashing ends . Nothing on the screen, no response from any of the buttons, just dead.
CurlyBlonde said:
Do you guys still have the files?
I managed to get the proper drivers and the phone is seen by the computer and I manage to flash it , but the phone is completly dead after the flash .
The power button wont do anything, plugging it into the charger doesnt do anything, I can only reflash it by connecting it to the pc while holding the volume up & down buttons.
Checking on old forums, aparently there are two versions of the phone , single sim and dual sim.
Also the revision number seems to be important for some reason, so mines is dual sim , revision 61 .
I believe this was the firmware that was on it previously, although the phone remained stuck at the boot logo : a1000_usr_s29798_1511241708_sprd7731_ro , but i cant find it anywhere , so I flashed the one you guys had , but now the phone is a dead brick after the flashing ends . Nothing on the screen, no response from any of the buttons, just dead.
Click to expand...
Click to collapse
sorry, i deleted my lenovo a1000 files to focus on other phones. from what i have heard that issue is common with that phone. i know someone who flashed the firmware on their a1000 and got stuck in the same issue as you. i tried to help them unbrick it but it seems to be impossible. i think you need to do a board replacement if you want to use that phone again. also, i dont think that the phone revisions are that important cause i managed to get lenovo a1000m firmware on my lenovo a1000.