Database Develop

USB/Charger reboot the phone, download mode lost, vibrant rom on i9000

OK guys I really badly need some help. My phone is in a non-workable state and I am starting to run out of options.
I did some mistakes but I will try to take out the details to list mostly the fact, hoping someone will take the time to give me directions.
- I have a galaxy s I9000 (switzerland/orange)
- I had upgraded to 2.2 via Kies.
- I got tired of the phone becoming increasingly slow. I found out about voodoo lag fix. I read 3000 forum posts, documentation and stuff, and when everything seemd easy enough, I installed voodoo via Odin.
- Here problems started. After installing voodoo, the phone booted, but the robot voice said "convert data partition. Not enough space on partition". Then again. And again. It was stuck in a boot loop. This problem doesn't seem to be documented anywhere i could find. The only instructions I could find on how to disable voodoo were to create some files on the disk, not very helpful when you can't boot the phone.
- I found a couple of threads with people who had the same message, and the advice their were given was to flash another rom.
- So I went to samfirmware.com and downloaded 2.2.1 for I9000 (JS8). I installed it through Odin. The phone booted, showed me the Galaxy S screen, then went black. Then it would vibrate every 20 seconds or so. Once, then 3 times in a row. I waited 30 minutes because in some places it said that may take long, but the situation didn't change. I rebooted, tried again after taking about the battery, wiped data, reset factory settings etc. The phone state wouldn't change, and I started to get a little desperate, because this was a stock rom, and if that didn't work...
- I read 3000 more threads, and phone a guy who had been in this situation, and got out of it by first installing "Eugene's JK2 froyo that never bricks" and then after wards reinstalling the stock rom.
- So I installed Eugene's rom. I knew it was trouble that it was a vibrant's rom, but I figured, I had read everywhere that as long as your phone supported download mode you could still always re-flash a new rom, so I decided give it a try.
- And the phone booted. Asked my pin, loaded stock android and all. I was happy at first, but then new trouble came. Now, whenever I plug in the USB, the phone's screen goes black after 4-5 seconds. When I unplug it, phone reboots. No charging battery appears when I plug the turned off phone on the charger.
- And worst of all, the buttons got mixed up. Vol up is vol down now. But more of a problem, 3 button recovery and 3 button download mode don't work anymore. I couldn't find a way to get them back. So I can't flash a new rom with Odin :-/.
- My latest was to install rom manager since I can access the market. I downloaded the tedgy rom. Installed the "clockwork recovery mode" from Rom Manager. It asked me if I had I9000 or vibrant, wasn't sure what it expected since I have now a vibrant rom on an I9000, but I put in I9000. Then I reboot telling rom manager to install Tedgy. I get a recovery mode screen which offers to reboot/reinstall packages/wipe data, then does a couple of operations, and finally gets stuck on :
can't open /cache/update.zip
(bad)
installation aborted
So there I go, with a vibrant rom on my I9000 (rooted, at least), a phone that can boot a half-functionnal android, but with a useless cable plug, an unchargeable battery, and a download mode I couldn't find... And waiting for my wife to get back with her phone so I can charge my battery again...
Any help or lead to help me get another rom installed on this phone again would be *greatly* appreciated. What other ways do I have to access download mode ? Or is there a way to get to it despite my buttons being messed up ? Maybe the rom manager issue can be fixed ?

OK well I got out of it somehow.
In case someone else had this same issue, here's how I got out of it :
1) Install ADB.
2) launch Odin
3) go to adb folder in command line and type "adb reboot download" but no enter just yet.
4) plug the usb cable on the phone.
5) type enter in the adb shell in the small window of opportunity you have before the screen goes blank. This reboots the download mode and allows new flashing via odin.

Any answer for this thread?
Did you fix the problem?
I'm stuck with the same case...

Flash gone wrong

Hi,
I've flashed multiple times before without an issue until today.
First, here's my background information:
Samsung Captivate (ATT)
Was running Continuum 5.4.1 but it felt laggy so I attempted to flash MIUI 1.5.13.
Here's what I did:
I wiped my phone using the Odin One click tool, then flashed CM7's kernel and then performed formats of the cache, system, and data, then installed MIUI RC2. After this step the phone should have restarted, then I planned to shut it down and reboot into recovery and flash 1.5.13 onto it.
My problem(s):
-Boot into recovery/download mode using key combinations is not working.
-The ADB console reports device not found when I try to run adb shell.
-The phone is undetected in Droidexplorer.
-When I attempt to download an app to boot to recovery with the phone says there is no space even though nothing has been installed other then MIUI.
What I would like to do:
Get back to stock with download/recovery modes working.
On a side note: MIUI works, but in a very limited way. I can navigate through it, but it won't allow the installation of applications due to there not being room on the phone (as said before).
Thanks!
Update - my phone was being identified as a Nexus S, so without those drivers my phone could not be debugged via USB. I now have the drivers and can perform ADB commands, however rebooting into recovery and into download mode both result in the phone restarting without going to the download or recovery mode.

Try using ODIN and repartitioning. I have good videos on standard ODIN and Heimdall on YouTube just search them. If you can not get out of this contact me, I have been able to partition debrick in the past and it's actually considered by me far more annoying than standard bootloader JTAG in certain situations. Let's hope yours is easier to bail out of!

First of all thanks for the reply and direction.
Secondly:
After working on this all last night I was able to get the phone recognized by Odin and my computer, now I am stuck at one of two screens depending on what I do.
If the phone is powered off then plugged in, the battery charging screen appears but there is no animation and after unplugging it the battery charging image remains.
If I power the phone on it hangs on the Samsung boot screen.
Repartitioning does sound like the proper direction for me to take, but, when I use Odin it freezes while setting up the connection to the phone.

when the phone is powered off try holding both vol keys and plugging in the cable. That could possibly get you to download mode. If not try vol down/pwr at the same time since you are now on GB bootloaders the keys are a bit different. Let me know what happens and good luck

maybe you should try to build a jig and use it to get into the download mode first. or you can buy it on ebay, just search for "micro usb jig".

I've tried every volume and power combination possible to no avail, I can't get into download mode. I've given in and am exchanging my phone. Thanks for the help anyway guys!

Phone suddenly acting up need some help

I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.

whoisthisis said:
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
select recovery by holding the vol buttons and power on boot just like fastboot. press vol - for recovery. when u see dead droid hit both vol up and vol down and theres the recovery

Thanks, I was finally able to get into recovery. Wiped data and did a factory reset which again got stuck at the logo screen. Went back into fastboot and ran RSDlite again to flash the stock ROM which gets me to the "Welcome to Droid4" screen where it says "touch the android to start" but the touchscreen is unresponsive. Starting to think there is something physically wrong with the phone....

send it to motorola, I've heard their customer support is pretty good. but if you voided your warranty by rooting/flashing other roms, I've heard bricking the phone and sending it in works to get a new one too

The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....

whoisthisis said:
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
Click to expand...
Click to collapse
So it has been a couple days now and the phone works totally fine. It looks like the problem was that by removing whatever bloatware that I did, the phone's OS got borked when VZW pushed an update of some kind. Flashing the stock ROM without doing a factory wipe would temporarily solve the problem but eventually the update would get pushed again and the whole thing would lock up again. The factory wipe + reinstall seems to have been the solution to the problem.

[HELP] Applied to big theme for TWRP, can't nothing do

I can't turn on the donwload mode, reboot to system, even flash something.
Any ideas?

you have to fix bootloader,maybe you must use JTAG box for it.good luck

Problem solved
OK. I "magically" rebooted to download mode and flashed cwm via odin.
In the morning I was hurrying and didn't write everything here. The recovery was working, the theme was for bigger resolution and I've just seen part of the screen. Before I chose in ROM Manager to reboot to twrp so everytime it booted, it was the twrp. I took out the battery, then put it again, turned the phone on and hold the combination of buttons to get to dwnld mode. I hold it and hold and after 3 reboots I've seen the dwnld mode screen. I was never so happy
Thread can be closed

I hope you learned a lesson here today. You cant just flash sh*t to your phone.

The "soft brick" is maybe my new tradition. Earlier I had SE X10MP and I've also softbricked it. That was my 1. Android phone and I didn't know how to fix it. After some time I knew much more about Android and my device. Then I noticed that I could fix it myself. In service they just reflashed the soft. That was everything xd

Galaxy S Plus problem (GT-I9001)

So recently I got my sister's old phone and now I'm trying to put KitKat on it( http://forum.xda-developers.com/showthread.php?t=2579431) but there is something really wrong with this phone. I bricked this phone a long ago while trying to put cyanogenmod on and now I'm wondering what the hell did the repairs man do to this phone.
1. Doesn't have a recovery mode, all combinations are leading to download mode.
2. When trying to factory reset from settings menu it shuts down and starts bootlooping.
3. When booting up the phone and then deleting all downloaded apps and changing settings, after a restart everything is back to the way it was.
4. Tried everything to get Cwm on it but simply can't get the drivers for download mode to flash with Odin.
I'm not so experienced with this kind of stuff and maybe someone can help me.