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
Related
hey guys is will need some help with this device im not kind of a noobie on this kind of things bcs i been working with several phones, like the veteran xperia10, galaxy ace, motoroi2, etc etc. but never with a tablet
here is what it happens a friend ask me if i can upgrade his sgt-p1010 to a newer version, honeycomb or maybe ics, i´ve read a lot of posts regarding this on how to upgrade it trough odin everything was fine until the reboot of the device, bcs by my mistake i flash a rom of the 7.7" tab and this one is a 7" only now the tab is not turning on, odin is not recognizing it, either samsung kies or the pc. buttons are not responding it wont charge and cant enter to download mode.
I REALLY NEED HELP FROM U GUYS, HOPE U CAN HELP ME
ps. srry for my english :laugh:
This kind of thing can result in the inability to boot which can only be repaired by the use of specific hardware, i.e. this could be a "hard brick". Then again, maybe it can be restored to working order by flashing it again (a "soft brick"). So the very first thing you need to know is, can it get to download mode?
Turn it off, if it's switched on, and charge it for a couple of hours,say four hours. Use the original charger connected to mains. It doesn't matter if it shows anything, or nothing on the screen, let it charge. This is to make sure flashing it won't fail because it doesn't hold a charge.
Now connect it to the PC with the original USB cable. Then after making sure it's switched off, switch it on by pressing the On/Off button, while simultaneously the Volume UP switch. Press them both at the same time, and keep them pressed! If you're lucky you'll get the yellow graphic with the download text. A phone symbol, an !, and a PC symbol is fine too. Even if it doesn't show anything, you may be in download mode, so install the right drivers, and hopefully Odin or Heimdall will recognise is, and will allow you to flash the right ROM.
well i already let it charge for all night long and nothing happens after i perfomed the flashing the screen was totally in black but it doesnt shoes anything i mean the tab was turned on, then apparently batterie dies and after that is not charging. already tried with the heimdall thing but it says that device is not connected.
I think that this is going to be a HARD BRICK
so do u thhink there is another way to solve it?????
or it will be necessary the JTAG stuff???? bcs i dont want to try that it seems that is very difficult to me bcs i dont know nothing about hardware jejejeje
You have installed the Heimdall driver? It's called zadig.exe. Then you have to go to download mode and connect the Tab to the PC with the USB cable. Then Heimdall hopefully will detect the Tab.
If there's no way software will revive the Tab, it's hard bricked and will need hardware to get it working again. There's this guy mobiletechvideos.com who will repair any kind of brick. Basically he uses the JTAG on the board of the Tab and a special box to flash the right ROM to the Tab, even when it's dead. Some here have tried the service, and they say he's quite reliable. Another way is to modify your Tab with Adam Outler's Unbrickable Mod. It's brilliant, you can't soft brick your Tab after that, but it involves soldering very small components on the board of the Tab. The mobiletechvideos guy can do it for you I believe.
Well, I guess you just got a hardbrick .
The only way to fix this problem is go to SAMSUNG SERVICE CENTER.
Sent from my GT-P1000 using xda app-developers app
Past few days were the worst for me as I had Hard Bricked my Captivate.
*** History*** (You may skip this is you wish)
This all started few days ago, like every cappy owner I too had a craze of testing different Roms, untill i settled for RemICS. But soon after a month I got bored and moved to Nostalgic 6.2. The rom looks good, but then when I called someone, there was a lot of static on the line and the other person could not hear me. So I decided to try a different modem, so I installed a different modem and things went back to normal.
Later I found another post on XDA, a comparision table for different modems on captivate. So i wanted to give a try, & this is when things started to get rough.
I installed a few modems and then found that my mobile would not get any network signal. So I planned to use ODIN One-Click (I897UCJF6-final-OCD-REV0) and go back to factory. I used ODIN and was able to go back to factory and everything was back to normal.
***When & How I Messed up my Cappy***
As I was back to Factory (2.1) I wanted to upgrade it to GingerBread. I used Samsung Kies to update it to 2.2 Froyo and while this happened, Kies downloaded the firmware, however while flashing the phone it was stuck at 3% and was there for about 4 hours and wouldnt move further, and the screen was solid green and no images or characters. So I took the risk and manually killed Kies and rebooted the phone. Now the phone would come to AT&T screen and was stuck there, tried the firmware update again and still had the same issue. This is when I decided to go back to Factory using ODIN. Used Odin to flash the phone again and it wouldnt move ahead of Factoryfs.rfs and would be stuck there for hours. So I took the risk and disconnected the cable (I know there is a risk of hard brick, but I trust this phone so much and was impatient to give it another go) and restarted the process. It again did the same thing, but this time the phone shutdown and was on a Black Dead screen. I disconnected the phone and tried to put it to download mode and it wouldnt work. The phone would just not show any signs of life. Connected the charger to check if there is any display and still had a dead screen & no sound. ODin would not recognise the phone anymore and no signs of any PCI device in device manager. Even tried Heimdal and still no go. Tried this for the whole day and i was preety satisfied that this might need JTAG.
I had also left a post for connexion2005 on http://forum.xda-developers.com/showthread.php?t=1041042
By now I had started to surf ebay looking for another Cappy or Infuse. All the signs that the phone gave me were of a Hard Bricked Captivate. However I did notice that if I reseat the battery and then try to power ON the phone, there was no sign of life, but after leaving it for 20 minutes the phone would get a little warm. So I knew that the phone was still alive, just a no video/no post kind of situation.
It was 11:00 pm when it just struck to me that I should try Linux, as there was a faint possibility that Linux may recognise the phone if it was in any kind of life mode.
So i grabbed a copy of Ubuntu and installed it on the same laptop, where the phone showed no life and used the same usb cable. Well once the OS was installed all I did was tried using the Vol UP + Vol Down + USB to put it into download mode and to my surprize the phone immediately went into Download Mode and there was display. :good::good::good::laugh::good::good::good:
Then I just flashed the phone with ODIN and went back to factory........ and everything is back to normal. :laugh::laugh::laugh:
I wouldnt be trying to brick the phone again, but if anyone has a hard bricked phone can definately try this and hopefully should be able to boot back. Please let me know if it wokred for you.
I am not sure if this is the right section to post this but, definately it worked for me where the phone showed all the symptoms of a Hard Bricked Cappy. If the moderators feel it should move to a different section, please feel free to move it.
I am now convinced that Captivate is Immortal...... :angel:\m/:angel:
Please use the Thanks:good: button if this worked for you.:good:
I may not be able to recreate the issue and havent captured any images, but if you have a dead cappy, you can definitely try this and let me know.
Glad your phone got fixed, thanks for taking the time to write it. I'd suggest moving it to captivate general though. This is the development thread.
You didn't have a hard bricked cappy. You had a soft bricked cappy. A hard bricked cappy is when the primary and secondary bootloaders get corrupted, this also breaks download mode. You interrupted the odin process when it was at factoryfs, which is a long time after it's already successfully installed bootloaders.
The fact it booted right into download mode shows us that it had simply been soft bricked the whole time. This has nothing to do with linux, Kies had installed its own USB drivers that do not support the proper communication with the phone in download mode, this is why when you tried to odin it was being so fussy - it was using Kies USB drivers.
A simple removal of kies, installation of the correct samsung USB drivers, and plugging your phone into a different USB port even would have allowed odin to flash properly. This is why when you went into linux it worked right off the bat, because you didn't have kies and kies drivers in linux.
The captivate is far from immortal - I invite you to see what happens when you interrupt an odin session while it is flashing boot.bin and sbl.bin - you'll have yourself a real hard brick very quickly
fohdeesha said:
The captivate is far from immortal - I invite you to see what happens when you interrupt an odin session while it is flashing boot.bin and sbl.bin - you'll have yourself a real hard brick very quickly
Click to expand...
Click to collapse
believe it or not my cable got pulled out right in the middle of the factoryfs and since i cud still enter download mode i tried it again and then my power got cut in boot.bin part, and i was actually still able to boot into download mode even when nothing showed up on my screen, all i did was first pull the battery, hold the down and up volume button, insert usb into phone and insert battery, and somehow it booted into download mode according to odin, so idk the phone may not be invincible, but its close
fohdeesha said:
You didn't have a hard bricked cappy. You had a soft bricked cappy. A hard bricked cappy is when the primary and secondary bootloaders get corrupted, this also breaks download mode. You interrupted the odin process when it was at factoryfs, which is a long time after it's already successfully installed bootloaders.
The fact it booted right into download mode shows us that it had simply been soft bricked the whole time. This has nothing to do with linux, Kies had installed its own USB drivers that do not support the proper communication with the phone in download mode, this is why when you tried to odin it was being so fussy - it was using Kies USB drivers.
A simple removal of kies, installation of the correct samsung USB drivers, and plugging your phone into a different USB port even would have allowed odin to flash properly. This is why when you went into linux it worked right off the bat, because you didn't have kies and kies drivers in linux.
The captivate is far from immortal - I invite you to see what happens when you interrupt an odin session while it is flashing boot.bin and sbl.bin - you'll have yourself a real hard brick very quickly
Click to expand...
Click to collapse
And unbrickable mod fixes this. Therefore the captivate is pretty much immortal. You can even take a hard bricked cappy, do the unbrickable mod once it's already broken, and still have it return to working order.
Way say you now?
Arisenhavok91 said:
Way say you now?
Click to expand...
Click to collapse
What*
I would say of course JTAG'ing a hardbrick is capable of unbricking it, same for about any other device in the world with volatile memory based firmware. this is not a magical new discovery.
They aren't called hard bricks because they become impossible to recover, corrupting bootloaders is called a hardbrick because it takes HARDware modification to fix, not software utilizing the preexisting hardware. Anything else? Anyone else have some wonderful insider info as to how linux can make download mode magically appear? I'm loving the knowledge in here, really. If you're going to spread misinformation, we please ask that you do it in the correct subforum.
Of course, I argued that the Samsung Captivate is "immortal" due to it's ability to be resurrected at times when even a JTAG would fail.
So back to my point of you saying "the captivate is far from immortal" - what say you now?
Edit: If you can't take someone poking fun as such, please don't bother to respond. I won't look back at this even if you do reply, so please, take a chill pill... or some midol.
Arisenhavok91 said:
So back to my point of you saying "the captivate is far from immortal" - what say you now?
Click to expand...
Click to collapse
I would continue to say the captivate is far from immortal, in the same context as my original post you seem so excited to quote - in a software recoverable situation. We are not talking about JTAG and hardware modification anywhere in this thread. he was claiming the captivate is immortal in regards to all situations being software recoverable by magically switching to a different OS, if you could please put on your reading comprehension and context goggles the pieces of the puzzle might start coming together. Also, do not ask questions you won't bother reading the answer to. Thanks!
I say the captivate is pretty much inmortal! xD even without power button ive been using it with no problem and getting into DLmode.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
A few posters here claim that the G2 is unbrickable - but I think I can challenge that. It started off with me wrongly flashing the Cloudy ROM 3.0 - what I didn't realise only till later was that it was intended for the Korean variant of the G2. Dummy move indeed.. I had previously taken the necessary precautions and took a full titanium backup and ROM backup onto a USB drive via TWRP - I previously ran Cloudy ROM 2.2 with Dorimanx Kernel on KK 4.4.2.
Right now, the phone doesn't seem to power on via buttons. When I plug it to the PC via the USB, I get "QHSUSB_BULK" as an unknown device only.. no black screen while on, no drives or COM port.
First off I want to be clear that I know I and only I am responsible for bricking my phone - The reason I'm in this mess is completely down to my stupidity, and trusting 'educated guesses' instead of confirming specs black of white. Just wanted to be clear in case anyone gets the wrong impression.
So this is more or less the sequence of events;
1. After flashing, I got stuck in fastboot mode.. (can't find the link) I followed one post where I needed to flashed .img files via the Fastboot CLI (similar to ADB). I used the images from the LG G2 D802 16GB in europe. source.. It was a toss up between the EUR and non EUR, and so I made the first of my so called 'educated guesses' that sent this phone deeper into the ground.
2. Something went wrong as when I rebooted the phone (had no idea what had gone wrong at the time), I got no logo. After some time, I noticed the screen on with a black background. when plugged into the pc, the QHSUSB_BULK would appear and with it a bunch of drives that Windows thought needed repairing. so I followed This .. I installed ubuntu, booted to terminal so I don't get those auto discovery pop ups, I used the images recommended there for my device (again, it seemed to make sense to use the same that the OP was using for my LG G2 D802 16GB in europe... After I rebooted, it was to my horror that the screen didn't even turn on, with no drives being detected via USB.. just the QHSUSB_BULK. This is what made me realise that the culprit was most probably using wrong images rather than improperly executing the instructions.
3. I opened the phone and tried shorting some capacitors where I'm supposed to see the drives again to no avail. I even tried shorting the capacitors ends as described here to no avail. I done a good full hour shorting the hell out of those capacitors (the post says to keep at it till it works cos it can sometimes be a bit tricky) but I saw no change. I would like to try the DL mode described there but I can't figure out what I have to ground from the images shown in the post regarding the "BOOT CONFIG".
This is basically the state the phone is in at the moment. so to recap:
No bootloader,
no recovery,
no fastboot,
no download mode,
no drives when in QHSUSB_BULK mode,
no COM port.
From the multitude of unbricking guides here, I gather that I either need to see that bunch of drives again when via USB or a COM port. I tried installing Qualcomm drivers, thinking that if the pc recognises the device, I might get the pc to identify the COM port, but the driver couldn't be installed for the QHSUSB_BULK device (got some error.. I can update this post later).
I tagged this post as a question.. i'm sure there's a question here somewhere...
HELP?!
bump.
Could really use a little help... anything
kuwlij said:
bump.
Could really use a little help... anything
Click to expand...
Click to collapse
You can ask @somboons
he came from deep hard bricked.
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
http://forum.xda-developers.com/lg-g2/development-d802/tools-mini-srk-tool-d802-t3098163
:good:
.
...
When I first tried to enter QHUSB_BULK mode on mine, I took ages. Seriously, ages. It kept not showing the drives. Important thing to remember, in my opinion, is to use Linux (latest Ubuntu in my case). If you keep trying, eventually they will pop up for a split second. I can't remember how I did it, but you have to use a partition tool, I think, to get it to freeze the positions of the drives. Then, once it's 'mounted' them, you can try (and keep trying) to flash to each partition.
Mine was well and truly screwed, so I flashed a blank partition table on, then flashed each image onto that. It took a lot of trial and error, though, because it kept not showing the drives.
furzewolf said:
When I first tried to enter QHUSB_BULK mode on mine, I took ages. Seriously, ages. It kept not showing the drives. Important thing to remember, in my opinion, is to use Linux (latest Ubuntu in my case). If you keep trying, eventually they will pop up for a split second. I can't remember how I did it, but you have to use a partition tool, I think, to get it to freeze the positions of the drives. Then, once it's 'mounted' them, you can try (and keep trying) to flash to each partition.
Mine was well and truly screwed, so I flashed a blank partition table on, then flashed each image onto that. It took a lot of trial and error, though, because it kept not showing the drives.
Click to expand...
Click to collapse
Mine was exactly the same I also had a blank partition table.. Anyway just keep trying because It took me a while to get mine working.. I was trying to short the capacitors but it seems to be quite hard sometimes especially if you aren't carefull.. Because you can start to mess with the soldering of the capacitors and it'll be harder after that.. It happened to me..
Anyway here's something I've wanted to ask everyone, after I sucessfully put my phone back to life, it seems like the middle button isn't working, the LED and the volume rockers are fully working, but if I ever press the power button after some time it shutdowns just like if I pressed and hold for a while, has anyone got this problem? It seems like the flex cable or something is damaged but i wanted to be sure it's really damaged or just something I could solve.. thanks and sorry for the off topic..
kuwlij said:
bump.
Could really use a little help... anything
Click to expand...
Click to collapse
This
HTML:
http://forum.xda-developers.com/showthread.php?t=2582142
saved my D802.Take time to read all post
Hi guys,
Over about an year ago I SIM unlocked a SAMSUNG GALAXY S4 AT&T. Several weeks ago it stared showing a gray lock on the bootscreen, but it would boot up. Now it just won't boot up or anything. Computer can't detect it. Plugging it into a wall socket does not do anything. It's not the battery I tried with another one. I honestly can't remember if I rooted the phone when I sim unlocked it. I also can't remember his Android version, maybe it was 4.2.x or 4.4.x .... I just don't remember, it was more than a year ago.
What I noticed was that if I remove the battery, leave it out for a while and then plug it back in I have about a 3-second window where the screen turns on and shows the gray lock again. After that it turns off.
I've been reading online, but I can't find a definite answer. Some say it's a USB port problem, others say it's a hard brick.
Please guys, help.
Sounds like a hard brick. Plug it in without the battery. different port at least.. then check device manager and if you see something like "QLoader 9008" under COM PORTSor something similar, then its telling you it cannot communicate with the motherboard.. Qfuse blew.. and chances are the version was 4.4.2. I mean the screen will not turn on at all, no boot, no recovery, i mean if odin doesnt detect it.. then it's a hard brick in more than one way. Sometimes this happens. they call it sudden death syndrome lol.. and since you did some minor modification (please, sim unlock is basically routine now) you are correlating it with that. If Odin does detect it, which it will show "COM:#HERE Added!" or whichever.. then you have a shot.. you might need to use some brick files if you can get the phone into download mode. I mean there's other options like getting a new EMMC or... JTAG types of stuff, quick soldering.. it's a fuse that blew when updating whatever it was updating... or.. it just died. That also happens.
there are other ways to fix it if it shows up like that.. usually getting a debrick image with that exact same OS that he had, boot loader and all.. it has to be a class 10 (or better) sd card.. you simply use something like win32has to match the speed of the boot process and if it is fried, then after about 60-90 seconds, you'll get a boot screen. 16GB is optimal.. or 32GB. Remember... class 10 or better. 10 MB/s minimum speed, usually. Sometimes you'll get away with a crappy card but at least try to do 16 or 32.. there's so much info about it. You just need to use win32 disk imager.. it'll write it to the SD card. FAT32 obviously is the needed file system at the very least. You can also use linux, which is what I actually prefer, but if you're in windows, then just use win32 disk imager. don't try to open the debrick image. just.. look for it.
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.