Database Develop

My Galaxy has failed to load :( Please help urgently

I have JG5 installed and put Docs v.7 on my phone was working well for 2 days and today I turned phone on and off and it loads , but a black screen.
The screen lock is there with clock, I slide glass away and just blackness.. no buttons bring up anything, I can't do anything because I cant get into debug mode I am unable to do anything
Please please help me asap

Read the FAQ first please. I'm pretty sure there is a solution for you there!
PS: Weird things can happen on CustomROMs because the result of removing/changing certain components of the f/w is not completely predictable!

I read that a few days ago,
Ive already done a factory reset via vol up + home and I can see the original background but there are all these errors popping up
Sorry the process android process. acore has stopped please try again. force close
there are dozens of them, touchwiz is broken everything...
I cant do anything there are errors coming up.. how do I put a safe update.zip onto my USB??

I cant even mount my USB due to the errors coming up and coming up everytime I force close on the last error
Please help me with some ideas.
I cant go into USB debug mode, I cant mount USB drive. I cant access anything on the phone.. what can I do?

In between all the errors popping up I managed to mount my USB and put SamSet 1.1 update on there, I vol up + home and loaded the update..
It restarted and the notification bar looks diff but all the errors are still coming on..
logsprovider
gallery
twlauncher
media..
I force close them all but they keep coming around..
Going into download mode enables debug mode yeah? If it doesnt I am screwed..
The phone was working beautifully for 2 days, nothing has changed for all this to go stupid I hate when tech goes wrong and you have changed nothing...

The laptop needed a reboot Flashed JG5 via odin and its all happy now
Please be cautious when applying custom ROM's is the lesson here. phew!

[Q] My SGS i9000 seems to be dead. Please help me :'/

Alright
First of all i would like to say that im a completly noob in android OS and that i possiblely have done something idiotic!
So.. was i getting annoyed by a slow phone (have voodoo lagfix installed and set to be ON. It seems to work like ****!)
I rebooted into recovery mode and entered advanced settings and i was curios about the partition setting.
Then i picked "partition" and set it be on "4096MB" and at last i picked it to be "ON"
I finished it and reboot the phone.
Now i only getting the startup logo and nothing happens.
I have the 3 button fix installed to be sure i can get into recovery mode again, and i have tested it and it WAS working.
Now it does not work with the Vol up+Home+Power button combination.
I can get 3 different screens like the startup logo, the download mode and the battery charging logo, which not showing any sign on charging.
instead it show the loading circle, frozen on the charging logo.
So what can i do ? - I really really hope there is a solution on this huge problem, because it is worthless now and i only got this phone less the a month.
Thank you.

You'll likely need to flash back to your stock firmware and start over (meaning you loose all data on your internal memory).
Do you know how to use odin? Do you know where to find your stock firmware? I'm on my phone right notes so can't provide any links but you can check the reference guide thread in the i9000 general forum (it's one of the stickied threads) on how to flash firmwares. You can find your stock firmware on http://samfirmware.com

[Q] please help motodroid possible brick

first of all i would like to thank anyone who tries to help me. i am somewhat new to the motodroid i own an evo and i am trying to help a friend. the phone is a verizon motodroid 1. the phone has been rotted for about a year he was running i think buggless beast at the time it died the initial problem was his baseband along with a few other software info went to unknown status. first he tried a backup, after not fixing the problem he contacted me and i decided to take a look at it after researching on multiple websites the best conclusion i found was to download the drivers for the phone, rsd lite, and the sbf files to reflash the phone back to stock.
i tried all of this with no good results know the phone wont boot past the M logo screen in the boot animation. the phone is unable to restore any backups at this point. every time i run rsd lite it seems to work and at what i believe is the end i get a fail. then when i hold up on the d-pad when turning on the device it reads.
bootloader
2c.7c
code corrupt
and the phone is now unable to charge the battery also the only thing i was successful at accomplishing was flashing the sbr recovery but still could not flash any rom or the update zip that someone had mentioned to flash
any help would be appreciated

ok my best hit at it is resetting the hone. i bought a used droid 1 and the previous owner had left the " connect the dot " lock screen on it so after googling some **** i came accross a site that said something about booting into recovery. hers the steps
slide screen up and press and hold " x " and power until you get a triangle on your screen. now press both, the volume up key and camera simatainiously untill text appears then select reset or factory reset. this worked for me so hope this helps.

that was all done before i tried to use rsd lite and had no results after using rsd lite it completly removes the stock image then rewrites a new one. the problem is the removal of the image passes but writing the image fails so i am left with nothing.

[Debricking] Hang at samsung animated logo

Hi everyone, I spent all day trying figuring this out, even if probably the solution was really stupid, so I thought of doing a little post for future reference. If you have no time for my babbling, feel free to go to the short version (I wanted to put a link here, but I still have to learn how to do it and it's almost dinner-time...). If this post happens to be a duplicate feel free to remove it.
=== Whole story ===​A week ago I got a Galaxy SIII mini N (GT-I8190N) and just kept it that way because I didn't had a win pc to use Odin. Yesterday I finally came back to my parents, powered up the win machine and followed an awful lot of different guides to manage to install the Macław CM 10.1. So, for short: installed CWM touch trough Odin, installed the root zip trough CWM and finally installed CM 10.1 & Gapps trough CWM. Here I did my first mistake: the first thing I did after installing CM was formatting internal and external SDs. Where the Nandroid backups of the working Samsung firmware were.
After some experiments I decided to go back to Samsung stock (reason 1: no gtalk, only hangouts, reason 2: NFC support still in development, reason 3: trying to restore SMS from a SmsContactsBackup I (luckily) had I messed up the SMS DB so much the app couldn't start). NOTE: Macław's ROM is amazing, I'm surely going to try it again when NFC support comes up. Sadly, I am an idiot who thinks he knows better so I ignored all the warnings of doing a wipe of data/cache and restoring the Samsung original recovery. I just went to Kies for a "Firmware upgrade and initialization" instead.
The result was a disaster. The phone rebooted but hanged at the Samsung animated logo. After a lot of hanging I decided to redo a Kies firmware upgrade. Obviously I had no luck. So I switched to Odin, took the image Kies downloaded (since I didn't want to wait an hour and an half to the download from unofficial sites) and flashed. And flashed. And flashed. Always without success. After a little bit I decided to try changing Odin options (repartition, NAND erase etc). Still nothing. So I started trying all the guides out there (here?): repartitioned with a PIT file, reflashed a CWM, reflashed stock recovery, various combinations in different orders of all the "solutions" above... You guessed right: nothing worked.
Since I read somewhere that there are Galaxy have 25 partitions (what the ****???) and saw that Odin was flashing only 8 or so I decided that something some the other partitions was missing, so I switched to Heimdall. Since the Win version didn't want to start, I did a fresh Ubuntu 13.04 install (lucky for me I happened to have an empty HD waiting to be installed on the server that I could use for an afternoon ), installed Heimdall, started figuring out how it works, realized I needed a custom-made package (nowhere to be found, apparently), started looking into the partition scheme to understand where the problem could have been... Finally I realized my skills are a tiny little bit inadequate for that and found a reference somewhere to a "hard reset".
In all this it never occurred to me to try and enter Samsung recovery. The first thing I noticed was that it didn't start right away with VolUP + Home + Power, but I had to keep them pressed a lot longer than what it's needed to go in download mode. In practice the SIII mini logo went up two times before showing the android with the open belly. Then finally the recovery appeared, I navigated to wipe data and cache with the volume buttons, accepted with the power button and rebooted. Thus I finally had a Samsung animated logo that was followed shortly by an "installing applications" loading bar and the first start configuration tool.
So, what I learned today:
1) Samsung tools are not necessary evil
2) if you don't understand what you're doing and you're doing it anyway, be prepared to suffer
3) we probably need a unified guide/troubleshoot the whole community can edit (wiki-like). Threads are great, but it's really easy to miss the obvious (for the whole time I was sure it was a bootloader problem, never occurred to me that there could have been some data left... also because I did a NAND wipe through Odin and I thought that was supposed to wipe personal data...) and often propose a solution without explaining the rationale behind it. I'm sorry if there's something like that out there somewhere, I wasn't able to find it
Thanks to you that bore my babbling
And now it's time for:
=== The short version ===​
Problem: I messed up doing a Kies reset after installing a custom rom (CM10.1) without the dues precautions; the result was a phone caught in an endless loop at the Samsung logo. Installing firmware with Odin didn't solve a thing.
Solution: I booted in recovery (volume up + home + power) and wiped data and cache. After that I rebooted and waited a little bit, a progress bar appeared and everything was fine (well phone was at factory default but at least now it's working ).
I hope all of this could be useful to someone

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