Database Info

Rom Flashing a Fuze

Ok you guys have talked me into atleast trying some roms before I abandon the fuze and go back to my 8525 and/or iphone.
Ive read through
http://forum.xda-developers.com/showthread.php?t=436053
and
http://forum.xda-developers.com/showthread.php?t=410150
Im not a noob when it comes to flashing Ive done it countless times on the 8525.
1st problem is I cant get HardSLP installed on the device. I navigate through all of the menus and when I get to the progress bar it sits for a min and pops an error saying device is not connected. This is after its allready seen the device, verified the batter charge, read which version is on the phone etc.
I'm on a vista machine if that matters although Ive never had an issue with the 8525.
Next, Ive read some people are having issues at going back to orginal everything for return purposes. Can anyone prove or disprove this?
and I think thats it for now.
Thanks in advanced

Uncheck Enable advanced network functionality under the USB to PC network connections section (settings, connections).
Thats what did it for me.. had the same problem.

I have it unchecked other wise it would not sync.

Flash via MicroSD. Safest and best way to flash.

AllTheWay said:
Flash via MicroSD. Safest and best way to flash.
Click to expand...
Click to collapse
Don't I need to get HardSLP installed first?

hondaguyjoe said:
Don't I need to get HardSLP installed first?
Click to expand...
Click to collapse
Try unplugging the USB cable and plug it into another port. If it's plugged into a front USB use a back one if you can.
Also try putting your phone into the bootloader (holding down volume down + reset hole)
See if you can flash it that way.
If that doesn't work. Delete the device driver from you PC and start over.

Captivate not detected by computers

Okay, I honestly have googled the crap out of this, and scoured the forums and all, but I can't seem to find a solution. My Captivate seems to have become invisible to computers. I've tried it out on 3 different laptops, tried installing kies, installing drivers, restarting the computers, restarting the phone, restarting the usb debugging, turning mass storage on and off, still the computers give no indication that the phone is even there.
I'm guessing the problem is within my phone, as it doesn't work on any computer, and I'd like to get it worked out, as I was hoping to try out Cyanogen mod, and Odin won't work without usb connection. For the record, I am running Firefly 2.4 with the Suckerpunch #50 kernel. Anyone have any ideas?

Try flashing a more updated kernal
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

Same Here...
I have also been trying to find a solution to this after I flashed Di11i's 6.0 awhile back apparently my phone can no longer be picked up in download mode by Odin either XD I was also hoping to also try Cyanogenmod.

Tried updating Suckerpunch, no go. Suppose I could try another kernel, but I'm a little nervous as bricking finally seems like a real possibility. Also, I haven't read about anyone having this problem with suckerpunch. This is seriously going to cramp my style.
Sent from my SGH-I897 using XDA App

I was having the same problem trying to istall darky's ROM.
unplug phone from computor
reboot in colckwork recovery
select "mounts and storage"
select "mount usb storage"
select "mount"
Then select "back" until you can roboot
Hope that helps.
p.s. I've been having this problem all week with every custom ROM i have installed.

I thought that one had potential, but no go. Thanks for the try, though.

I found that after I was still having the same problem when back in stock.
Odin3 would not see the phone in debugging mode, but would see the phone in sync mode.
phone would not mount. I would select mount phone from dropdown, the phone would give normal mounting response, but the computer would not see the phone.
Here is what I finally did.
uninstalled the SGS driver
reinstalled the driver as administrator
while waiting for it to install
entered recovery mode on phone and cleared cache and all user data
read a book while waiting for driver to finish installing...
rebooted computer
enabled USB debugging
connected phone to computer - got an installing driver for device message
ODIN3 worked fine after that
USB mounted with no trouble
did a master clear and everything worked fine
rooted to phone with AIO toolbox - everything went fine and I ODIN3 one click and three button see the phone properly in debugging mode, and USB still mounts properly.
I doubt if clearing the cache and stuff did anything, but it doesnt hurt. I suspect I made a change to the phone that confused the driver. Im also not sure if connecting for the first time in dubugging mode is important or not, but i suggest doing it to be safe

timpac said:
Okay, I honestly have googled the crap out of this, and scoured the forums and all, but I can't seem to find a solution. My Captivate seems to have become invisible to computers. I've tried it out on 3 different laptops, tried installing kies, installing drivers, restarting the computers, restarting the phone, restarting the usb debugging, turning mass storage on and off, still the computers give no indication that the phone is even there.
I'm guessing the problem is within my phone, as it doesn't work on any computer, and I'd like to get it worked out, as I was hoping to try out Cyanogen mod, and Odin won't work without usb connection. For the record, I am running Firefly 2.4 with the Suckerpunch #50 kernel. Anyone have any ideas?
Click to expand...
Click to collapse
Load up odin and then try connecting in download mode and see if odin detects it.

opcow said:
Load up odin and then try connecting in download mode and see if odin detects it.
Click to expand...
Click to collapse
Not a thing. That's actually when I first noticed that the phone wasn't being recognized, as a matter of fact. I was doing the cyanogen mod thing, already applied the efsbackup.zip. Which didn't hurt anything fortunately, or I'd be completely screwed.

Charge won't go into USB mode

First off, I have 3 Charges in the house. One is stock , one is on GBE 1.8 still and mine is GBE1.9RC2.3 with EXT4 on /system, /data, /dbdata and /cache. So, I have some idea what I'm doing.
This issue is driving me crazy. My daughter's Charge (stock with voodoo) will not connect properly so she can sync with Doubletwist. If I plug my phone it, it is recognized as a USB device and Doubletwist see it without a problem so it shouldn't be the drivers on the computer. When I plug hers in, the phone asks if I want to turn on USB mode (like mine does), but the computer says device drivers failed and it shows up only as a CD drive. Doubletwist will not work with that.
I've gone through her phone several times looking for the magic switch that will make it work, but I can't find anything. I've tried 3 different computers - all of which recognize my phone fine, but not hers...
Any help would be greatly appreciated. I'm just about to the point of flashing her phone with GBE1.9RC2.3 and telling her to get over not having TW (she's just used to it) and hoping that the new rom will work.

Set the USB settings to "Ask on Connection", it's a known problem with Gummy. Also, if that doesn't work you will need to flash the SD card fix(if you haven't already)

blarrick said:
Set the USB settings to "Ask on Connection", it's a known problem with Gummy. Also, if that doesn't work you will need to flash the SD card fix(if you haven't already)
Click to expand...
Click to collapse
I have tried ask on connection. The phone does ask but doesn't end up working right. This phone is stock. Not Gummy. I think I voodoo'd it but need to verify. Regardless of the kernel and recovery its running Verizons latest rom software - EE4?
Could the SD Fix work even on stock?
Sent from my SCH-I510 using XDA Premium App

Try the trick that worked for the Fascinate. Plug her phone into the usb with usb debugging enabled then reboot the phone while it is still connected.

Also try re-installing the Samsung drivers on the computer.

tdenton1138 said:
Could the SD Fix work even on stock?
Click to expand...
Click to collapse
I may be wrong on this, but my understanding was the sd card showing up as a CD drive on EE4 roms stemmed from flashing a custom kernel, which seems applicable in this case if the phone is stock with voodoo. When this happened to me I already had the fix file on the sd card, and flashing the fix ... well, fixed it.

I too was having similar issues with this on my charge running rc2.3, lo and behold, all I needed to do was reboot my pc, then reconnect my charge to the usb cable... Its been so long since I have actually used my desktop properly. Lol
Sent from my Transformer TF101 using XDA Premium App

help flashing / back to stock

hi i have a Samsung galaxy S 4G (SGH-T959V) it has the rom slimsaber
i want to install the stock rom but i cant access the download mode
also doesnt charge while its turn off , but charges fine while its turn on

Vongolazer0 said:
hi i have a Samsung galaxy S 4G (SGH-T959V) it has the rom slimsaber
i want to install the stock rom but i cant access the download mode
also doesnt charge while its turn off , but charges fine while its turn on
Click to expand...
Click to collapse
The charging not being fully functional is not a surprise as SlimSaber is based on Android 4.4 which has problem with the charging for our phones.
The next question is, how are you trying to access download mode?
From what I've heard, a download jig is the way to go. However, I don't have one so I turn off my phone, push both volume buttons in, and, with the other end of the USB cable already in the computer, plug in the USB. Sometimes it doesn't go first time so try it a few times (also can take a couple of seconds). It should bring up yellow warning screen asking if you want to continue. Flash away (assuming you have the right files)!

well i have tried with the button combination like you said , but nothing appears and my computer only says ¨unknown usb device¨ and when i try from the recovery it just reboot.

Vongolazer0 said:
well i have tried with the button combination like you said , but nothing appears and my computer only says ¨unknown usb device¨ and when i try from the recovery it just reboot.
Click to expand...
Click to collapse
Yes, the download mode reboot from recovery not working is a known issue. Fixing it would have probably involved messing with the bootloaders so it wasn't done (if i recall correctly).
Since I'm assuming you're on Windows, have you installed the USB drivers? Also, it would be worth trying a different USB cable and a different USB port if you haven't already. Typically the ones on the back of a desktop are the best. If you have a laptop, trying ports on the other side is recommended.
Can you transfer files from the phone as a mass storage device? Does the phone act as if its plugged in when it is (ie is there a notification to connect storage to your pc?). In Device Manager on your computer, could you please list off any unknown devices. If you have linux, the output of the command "lsusb" would be great (if not, don't worry).

Phone Bricked After Installing OTA Update

I recently purchased an Oneplus 7 pro from Ebay and the phone was working fine. It's locked to T-Mobile and it prompted me to take an update, I believe the update was for November 2019 and was almost 2 gb in size. I rebooted the phone when it said to reboot to install the new features, and the phone never came back on after that. I tried charging it for hours, tried holding the power button + volume up/down buttons to get it to reboot, and none of this has done anything for the phone. There's no sign of life, the phone was working great prior to the update.
Is there any suggestions for fixing this?
Thanks.

adrunkenmess1 said:
I recently purchased an Oneplus 7 pro from Ebay and the phone was working fine. It's locked to T-Mobile and it prompted me to take an update, I believe the update was for November 2019 and was almost 2 gb in size. I rebooted the phone when it said to reboot to install the new features, and the phone never came back on after that. I tried charging it for hours, tried holding the power button + volume up/down buttons to get it to reboot, and none of this has done anything for the phone. There's no sign of life, the phone was working great prior to the update.
Is there any suggestions for fixing this?
Thanks.
Click to expand...
Click to collapse
go here https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659 and use the global version. that will allow you bootloader unlock phone when done.

MrSteelX said:
go here https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659 and use the global version. that will allow you bootloader unlock phone when done.
Click to expand...
Click to collapse
Thanks for the link, I downloaded everything and disabled driver enforcement but my phone is still not showing up in Device Manager. The computer makes a noise as I connect it to the USB port, but other than that it isn't doing anything.

adrunkenmess1 said:
Thanks for the link, I downloaded everything and disabled driver enforcement but my phone is still not showing up in Device Manager. The computer makes a noise as I connect it to the USB port, but other than that it isn't doing anything.
Click to expand...
Click to collapse
with the phone off, hold vol up and plug usb cable in. It should boot to edi mode then.

MrSteelX said:
with the phone off, hold vol up and plug usb cable in. It should boot to edi mode then.
Click to expand...
Click to collapse
I think it was the cable I was using that was causing it....used a better usb cable and it recognized in the Device Manager.
I can't flash it though as it gives error "param preload device not match image"

Hi,
I'm assuming you are trying to revive the phone using MSM tool. If so, the only successful way to do this is to connect the phone to a USB 2.0 port using the official cable. This will make the phone appear on the tool and then you can proceed.
adrunkenmess1 said:
I think it was the cable I was using that was causing it....used a better usb cable and it recognized in the Device Manager.
I can't flash it though as it gives error "param preload device not match image"
Click to expand...
Click to collapse

amirage said:
Hi,
I'm assuming you are trying to revive the phone using MSM tool. If so, the only successful way to do this is to connect the phone to a USB 2.0 port using the official cable. This will make the phone appear on the tool and then you can proceed.
Click to expand...
Click to collapse
I was able to get it to flash successfully. I used the files from the tmobile to international conversion since it required a hacked MSM tool. I'm a complete Noob at phone flashing and really spent a LOT of time reading tonight to figure it out. Phone flashed successfully but said the battery was now too low to turn on. At least it says something!
I'm charging it up now and hopefully it works after this!

amirage said:
Hi,
I'm assuming you are trying to revive the phone using MSM tool. If so, the only successful way to do this is to connect the phone to a USB 2.0 port using the official cable. This will make the phone appear on the tool and then you can proceed.
Click to expand...
Click to collapse
I use a USB 3.0 and USB c port on my computer and no issues

OK so I manage to get the phone flashed to the international version using the MSM tool. I then downloaded the DP 3 developer file like suggested. I put it in the root for my phone, went to system settings, system update, and got to install it locally. It installed 100% and then asked me to reboot for the changes to take effect.
I reboot the phone and then nothing, it's black and unresponsive the way it was when this whole thing started.
I'm sure I can just reflash the international file with MSM to get it working, but is there any reason why updating my phone in this manner always fails and a way for me to fix it?

jamescable said:
I use a USB 3.0 and USB c port on my computer and no issues
Click to expand...
Click to collapse
Really, I couldn't get the phone to come up on the MSM tool in the Qualcomm mode on USB 3 port. But when I connected the cable to the USB port, it appeared there.

adrunkenmess1 said:
OK so I manage to get the phone flashed to the international version using the MSM tool. I then downloaded the DP 3 developer file like suggested. I put it in the root for my phone, went to system settings, system update, and got to install it locally. It installed 100% and then asked me to reboot for the changes to take effect.
I reboot the phone and then nothing, it's black and unresponsive the way it was when this whole thing started.
I'm sure I can just reflash the international file with MSM to get it working, but is there any reason why updating my phone in this manner always fails and a way for me to fix it?
Click to expand...
Click to collapse
MSM phone, unlock bootloader and flash twrp. Use twrp to flash system update and see if it works