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...

Phone Doesn't Boot

Two weeks ago my phone randomly started to think it was charging every now and again. I thought nothing of it until One day it wouldn't boot. It would get stuck at the Samsung n7000 logo screen. I was able to boot into CWM so I did that and I tried to do a back up just because, but then it failed at backing up /data. It said it was corrupted. I went ahead and flashed another ROM and it booted just fine after that, but the charging problem persisted so I just ignored that. My phone just decided to not boot again so I was wondering if there was anything that could be done to save my phone. Also, I've always used a safe kernel.
TL;DR Phone doesn't boot. Randomly thinks it's charging and when I use CWM it says /data is corrupt. Flashing a new ROM only fixes it temporarily.

I think it is a hardware problem take a look at this thread http://forum.xda-developers.com/showthread.php?t=2008657

Thanks for the reply. f it persists I was probably gonna result in doing that. I am mainly looking for a solution to my other problem though.My phone sometimes just wont turn on at all.
I just went to a stock rom with ODIN installed a new kernel and then a new ROM so I'll see how that goes for a while, but if it's anything like before it wont last very long.

[Q] Boot lopp w/ AP, Plz help.

Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!

I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.

I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?

Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....

Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.

[Q] GT-N7100 multiple issues

Hi guys, first of all this is my first post here and won't be my last.
I am an Apple/iPhone long time user and want to tryout Android, just because I think it's time for a change , without knowing if I could get used to the new OS and wanting to spend as less as possible on this "endeavor" I bought a second hand Galaxy Note 2 GT-N7100 from a friend, the phone worked perfectly when I bought it, it had Android 4.1.2 on it and I wanted to update it to 4.4.2, did some research on the net about this (learned about the locked bootloader - this wasn't an issue for me coming from the iPhone) and updated the phone using Kies - and this is were the fun begins.
The update failed, and the phone was softbricked but could still go into download and recovery mode, after reading a few hours on the internet, I used Odin to flash a 4.3 stock rom for the n7100 which I downloaded from samsung-updates, the software got installed on the phone but it was very laggy (with the phone opened but locked, when I pressed the power button it took about 7-8 seconds for the display to light-up, the animations were very sluggish and phone was unusable).
I installed another ROM, using Odin, this time a 4.4.2, with the same results (every time I reset to factory setting and wipe cache from recovery - this didn't help).
I then installed clockwork recovery and rooted the phone then installed cyanogenmod 10.1 which worked almost ok but if i locked the phone after a few seconds the phone would restart, wipe cache/restore factory settings didn't help, i installed it again hoping it would be just an issue with the installation but had the same result, phone would restart.
I've followed all tutorials I could find related to this phone and this issue, installed several patches, reinstalled several stock roms, installed Criskelo rom, all with the same result, the phone is very very very slow and freezez after a while or it restarts after i lock the phone.
So, let me just give u some history on the phone, enumerate the symptoms and where I am right now:
History:
The phone was bought from Vodafone Romania, was never rooted and was never updated (before me ) and still has 3 months warranty.
Symptoms:
- Phone is very slow, unusable
- Freezes after the display is locked
- it is not recognized in windows, when I connect it i can hear the windows connect chime but the phone storage is not mounted, in device manager the phone is recognised as "cdc communication interface" which is not installed - i have the samsung drivers installed, and i have tried on other PC's with the same result, I also tried with several data cables - same thing - the phone works ok when in recovery/download mode
- sometimes when the phone is connected to the PC and the screen goes dark a gray battery appears with a "wait circle" and the phone freezes
- in recovery the phone displays 14 bynaries downloaded and also knox warranty void 1
- most of the roms freez in the language selection screen - i boot-up the phone (after i do a restore factory settings) the installing application dialog appears and then the language selection screen appears, then after 5-6 seconds the phone freezes - the freeze is not triggered by something I do it's triggered by time, after 5-6 seconds no matter what I do with the phone the phone freezes, if it makes any difference, exactly before the phone freezes the display brightness goes to the maximum setting.
Where I am right now
- I installed another stock rom, 4.4.2, it worked acceptable for a few minutes (it got passed the initial setup with no issues) then i left it on the desk, the display went dark and the battery thing happened again and the phone froze, i restarted the phone in recovery, did a factory reset, when the phone started it froze on the language selection screen.
I am at this for about a week now and I have no more ideas and no more patience, and run out of threads and tutorials to read, I am 1 step away of using the phone as a paperweight so please help, any idea would be appreciated, even if it's to enlighten me about what happened and telling me that the phone is bricked.
I am willing to try anything even if it is risky and can totally brick the phone, this is not my main phone and it's purpose is to help me understand android, and help me not make the same mistakes next time.
But, if it's possible I would like to fix the phone because even though it's pretty old it's still an ok phone.

Sorry wrong forum. You need N7100, not the n7000. Good luck.

Help ! Phone doesn't boot anymore

Hi. I have note 5 sm-920c with multiBoot,AryaMod ROM installed as primary rom and DrKetan secondary. All well and fine since this morning when I tried an app that changes resolutions (I changed to 1080x1920 and things stared crashing: systemUI, AirView, etc). After rebooting there wasn't anything on the screen but the wallpaper. So I connected the phone to USB and ran a few ADB commands to restore the resolution. After restaring everything was back to normal. Then out of the blue my phone restarted by itself and went into a bootloop: showing the black screen with samsung galaxy note 5 (and the little red text kernel is not seandroid enforcing - because of the multiboot) and immediately restarting. It wouldn't even get to the bootanimation. So I entered recovery and first wiped cache and dalvik - same thing happened. Flashed multiboot cleaner - same thing happened.
So now I'm trying to do a full reset to install a new rom. And the phone restarts DURING the reset while being in recovery. That's what scares me - because I haven't seen anyphone do this (it's not my first flashing exp). It doesn't even go into bootloader, it just keeps restaring. Only thing that works in the custom recovery - CWM.
Do you think it's a hardware fault? Like the sdcard failing? Or just software. Should I keep on trying flashing something from the phone since the files are there and I can still access them? Can I flash anything from Odin without entering the bootloader?
I'm asking now because I think it's serious and I don't want to **** it up anymore than I already did. Warranty is a NOGO right now, I at least have to get it to stock recovery even if the knox bit is tripped.
Any help appreciated.