Database Develop

[Q] phone stuck in boot screen, HELP!

i had network problems (3g stopped working, don't know why), and had an old version of doc's. so i figured i'd install the new version after a wipe, see if that'd fix it.
just to be safe, i went in recovery (clockwork) and restored an earlier backup. it worked, but still no internet. upon remembering that this was the backup i made just after installing docs, i went back to my previous backup, stock rom, i think 2.1.
this is where stuff went wrong. i hadn't disabled the lagfix (forgot which one, i remember i had ext4 as filesystem), and now, no matter what i do, my phone won't go past the boot screen. big lettering galaxy s, smaller gt-i9000 and at the bottom samsung, you know the one.
i tried everything i could imagine. wipe data/factory reset, wipe cache partition, re-restore to the oldest backup. only then did i remember the lagfix and remove it. retried all of those, still no dice.
i can get into recovery mode, both clockwork and 2e, and i can get into download mode.
when i connect my phone to my pc, it doesn't notice. when selecting mount in clockwork, it mounts, and shows the two drives in my computer, but when i try to open one of the drives, i get nothing.
i installed docs rom a while back, and have wiped my pc since then, so i have no files from that. i have installed the android sdk, but don't know how to use it, let alone how to use it with a phone that doesn't show.
all i want is to get back to stock, for now. try again from there.
can i? or have i ruined my phone?
edit:
wow... take about relief.
i used odin to flash xxjpu, 2.2.1, and it seems to have worked!
in case anyone else is stuck on a boot screen, download mode with odin means you're safe.
anyone with more sense than i showed in my stupidity, sorry for adding another semi useless topic.

[Q] Phone suddenly «wiped» / won’t boot

Yesterday I suddenly found my phone to be turned off by itself. When I tried to turn it on again, nothing usually happened. Sometimes however, it looked like it would turn on, but the white bootlogo would barely show, or maybe up to a second, and then it would go black again. When connecting a charger the charging icon would show for a second, and then black again, and still the phone wouldn’t boot. Recovery or download mode wouldn’t work either. I was hoping it was only the battery that had just died, since the phone won’t work at all without the battery, even with the charger connected. But when I tested a friends battery today, it would still not boot, and my battery worked fine in his phone. But, at least it turned on each time now, showing the bootlogo for a second, and then all black again. Recovery mode still won’t work, but I’m able to get it in download mode. If I connect the phone to the PC by cable first, it won’t start or go in download mode, I have to get it in dowmload mode first and then connect. I was using stock system v2.3.3 from about a year ago, but with Clockworkmod kernel.
So what could have happened? I figure the system is either corrupt, or even wiped?
Or could the phone itself be badly corrupted?
I also have to mention, that a few months ago the internal and external SD-card was suddenly wiped, and I got a message about error on one of them and had to reformat.
Since download mode is ok, I hope there is a chance to maybe flashing the system again with Odin?
Is ther any way to connect the phone to the pc and get access to the memory to maybe copy whatever data still there, if any? Or can I reflash to just put the new system on top of everything without formatting?

I think your sd connectors are corroded or damaged. For your data try to flash the semaphore kernel by Odin to get a recovery (link ). After flashing, go into the recovery look for "mont and storage" and select "mount usb storage" or something like that. With your pc connect your device and copy your data in your pc like an usb stick.
If it doesnt work, say goodbye to your data and try to reflash a rom by Odin
Link here
http://hotfile.com/dl/140301534/be8872c/I9000XXJVU_I9000OXAJVU_OXA.rar.html
Instruction:
- Unzip the file
- Open Odin (if you don't have it download here )
-Put CODE in the PDA case
-Put MODEM in PHONE
-Put CSC in CSC
-Now Put your phone in Download Mode and connect it
-Press Start and don't touch anything until the great case above the yellow one became green.
Please reply me for more info

Thanks, I'll try that tomorrow morning at work, don't have the time today.
At least I do have a complete backup from about two months ago, so it's no disaster about the data. There's not really anything that important on the phone, it's just all the work setting everything up like I want it again.

Please reflash a stock rom with odin...

I was able to flash semapfore kernel, but still I couldn't get the phone in recovery mode.
Flashed stock firmware 2.3.3 (last nordic version), and the phone booted fine, but lots of old programs kept crashing and messing with the system. Best of all, everything on the internal sd was there, so all the latest titaniumbackup was there. So I copied this to the PC, did a factory reset, flashed CF-root again, copied the titaniumbackup and clockworkmod-backup to the internal sd, and cwm-backup is beeing restored as we speak. Then titaniumbackup will be restored and everything should be fine for now.
I'll be leaving for holiday in a week, so I don't want to use lots of time right now to do a clean setup of the phone. There is way too much other things I have spend my time on before the holiday. But after the holiday I think I'll just have to do so.
Thanks for helping.

For your apps who crash you have to wipe apps data (with TB).

The apps crashing when I just reflashed didn't really matter since I was going to install the backup anyway.
But a few apps kept crashing even after I flashed the backup. So wipe app data was what I eventually found out I had to do.

And so the same thing happened again.
But this time it doesn't seem like reflashing will help at all.
Crappy trashphone, it's been a disaster rom day one.

First backup every thing and wipe
Sent from my GT-I9000 using xda app-developers app

dakudakuji said:
First backup every thing and wipe
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
The phone won't boot, and won't go into recovery mode, only download mode.
When I turn it on the boot logo only shows barely, and then nothing happens, just like last time.
I've tried reflashing several times using Odin, but this time it doesn't help, phone still won't boot. I've tried both without repartition, and wit repartition (and pit).

My friend got me to put his phone on cm9 after using froyo for a long time.
The strange thing was that the method to get into recovery suddenly changed from volume up, power and home. For some reason it is now both volume buttons, home and power ..
Just thought I'd share this since your recovery should work after a kernel flash.
Sent from my GT-I9000 using xda app-developers app

[Q][GT-I9001] Ivendor CM10 plus CastagnaIT Kernel (from Softreboot to Hardbrick)

Hello everyone,
I just hardbricked my SGS+ and now I'm a bit curious how this could happen.
This is what I did:
I used to run CM9 RC5 from arco68 along with the Kernel for ICS from Christopher83 and CWM 6.0.1.2.
Because my phone always lost the wifi-connection and also had some freezes I decided to try out CM10 Beta 3 from ivendor.
I backuped my phone, downloaded the zips and even verified the MD5sums. Next I flashed CWM 6.0.1.9 as recommended in the thread from ivendor.
After exporting the nandroid backup and other stuff like photos to my computer I wiped everything as mentioned in the thread, flashed the two zips and rebooted. Everything went fine and I was almost ready with setting up my phone again when I got my first softreboot.
Suddenly it showed the CM-bootlogo and after maybe 10 seconds I was back on my homescreen. I got another two or three softreboots until I decided to flash the Kernel 3.x from CastagnaIT.
I rebooted into recovery, wiped cache and dalvik cache, flashed the zip and rebooted.
Now I wanted to reboot into recovery again to fix permissions but instead I got a softreboot and my phone stuck at the CM10 bootlogo.
I waited for around 5 minutes and then I just turned the phone off and booted into the recovery mode.
Because I wanted a clean install without any problems like softreboots I decided to wipe my phone again (data, cache, system) and just reflash the zip for CM10. And at this point everything went wrong.
I flashed CM10 but when I tried to flash gapps my phone just turned off. And no, the battery was not empty. In fact the battery was at around 50-60% and my phone was also connected to my computer.
I tried to turn on my phone but now it stuck at the Samsung bootlogo.
The next thing I did was probably a horrible mistake. I tried to un-brick my phone but I did not realize that I could boot into download mode without problems so I guess my phone wasn't softbricked at all.
Well, after that I still stuck at the Samsung bootlogo and couldn't enter recovery mode. I got into download mode somehow and maybe this was my second mistake. I tried to flash the "i9001Reset.zip" via Odin. Everything went fine but when Odin said "Close serial port and wait until rebooting" my phone was completely dead. I think it was while I tried to flash the reset-file when I got a message like "MBR: read failed". So somehow I managed to destroy my master boot record.
Now I can't turn on my phone or enter download nor recovery mode. I already removed the battery for about 45 minutes but this didn't work either.
My phone is dead but at least I saved the important data and maybe I'll get a new one through warranty. Or I just buy a Nexus 4.
My questions are:
What did I do wrong especially when I tried to save my phone?
How can I prevent such things from happening?
And at which point I should have got help here in the forum or elsewhere?
I would really appreciate some tips for the future because I already flashed and used a lot of different ROMs but this is the first time something really went wrong.
Thanks for reading and thanks for your help in advance.
(Please excuse my non-perfect englisch.)
Greetings,
Mangoniter

[Q] Update to 4.2.2 failed. Phone not booting!!!

Hi all,
Last night, i rooted by N7000 through PhilZ-cwm6-DDLSC-ODD-5.08.5-signed and was successful in doing that.
Later i wanted to update my device to 4.2.2. So i downloaded cm-10.1-20130727-NIGHTLY-n7000.zip file and kept in my external SD card.
Then in recovery mode,i wipe the factory data. There was option wipe data or wipe to install new ROM. I selected the latter one. Wipe for installing new om was successful. Then i went to update zip.file option. But since the file was in external sd card, it was not detected and i was not able to select the file. Then i rebooted the phone but only 'Samsung galaxy N7000' screen was coming and nothing was happening.
I rebooted my phone many times but same screen was coming. Then in morning i went in advance options. I selected Recovery Bootloader. Downloading screen was coming and nothing was happening. Then i switched my off and trying to start in recovery mode but its not starting.
I thin i have no checked USB debugging.
Kindly help soon as i am helpless without phone. Your early response will be highly appreciated.

With the option "install new Rom" you removed your old Rom from your device. So it is only logical that your device won't boot into it.
Next time follow the installation instructions given in the CM-thread exactly.
And of course you can choose a zip from external sd card in CWM. So take a look again.
Best thing to do for you: boot into download mode, install a stock Rom with PC Odin and use it without changing things.

Hey Thanks for the help. But now i am facing new problem.
I flashed my phone using odin with stock rom.
Later i rooted with PhilZ-cwm6-DDLSC-ODD-5.08.5-signed and then updated it with cm-10.1-20130727-NIGHTLY-n7000.
This time i was successful. My phone was updated to 4.2.2.
Then i used it for some time and switched it off for removing the external SD card. After that i tried to switch on my phone, its not working.
Nothing is appearing on screen. I charged it and then tried to switch it on but nothing is coming on screen.
When i try to switch on my phone in Recovery mode or in download mode a thin line on the screen appears and then disappears and then nothing comes on screen.
Help please. Last suggestion worked.Kindly advise

[Q] i9305 newest cyanogenmod does not boot

Hi.
Since yesterday my galaxy s3 lte i9305 does not boot anymore, the blue cyanogenmod logo keeps turning for hours. I can however still go to the recovery (which was a few month old cwm). I completely wiped the phone (both caches, data, internal sd, boot, firmware etc ... all but the modem) and reinstalled the newest cwm and the newest nightly build three times now using heimdall and the external sd (connected my external micro sd to my computer sd card reader via adapter and put the zip on it). Just now I installed twrp-2.8.5.0-i9305 as a new recovery and installed everything again, but everytime - and also now - despite the seemingly successful installation, the phone is stuck at the cyanogen bootlogo.
Any ideas on how to get my phone running again?
Cheers

ScPo said:
Hi.
Since yesterday my galaxy s3 lte i9305 does not boot anymore, the blue cyanogenmod logo keeps turning for hours. I can however still go to the recovery (which was a few month old cwm). I completely wiped the phone (both caches, data, internal sd, boot, firmware etc ... all but the modem) and reinstalled the newest cwm and the newest nightly build three times now using heimdall and the external sd (connected my external micro sd to my computer sd card reader via adapter and put the zip on it). Just now I installed twrp-2.8.5.0-i9305 as a new recovery and installed everything again, but everytime - and also now - despite the seemingly successful installation, the phone is stuck at the cyanogen bootlogo.
Any ideas on how to get my phone running again?
Cheers
Click to expand...
Click to collapse
I would try a factory reset from recovery and see if that helps. You did check the md5 for your downloads right?
Otherwise I would install the stock rom, then try again, this time(making sure you have a compatible recovery) just wipe caches, data, and format system, and then install CM

noppy22 said:
I would try a factory reset from recovery and see if that helps. You did check the md5 for your downloads right?
Otherwise I would install the stock rom, then try again, this time(making sure you have a compatible recovery) just wipe caches, data, and format system, and then install CM
Click to expand...
Click to collapse
I did do the factory reset. I just wiped the areas separately as well. Anyway, I took your advice and installed the latest stock rom. Now I got the Samsung logo slightly flashing blue for hours instead of the cyanogenmod logo. Did not do anything else.
I suspect that its a battery issue in some way. The last weeks the phone lost its charge very quickly very often (not constantly though). Yesterday, the phone was in my pocket and then went off. It went into the constantly trying to restart despite the lack of batteries state until I removed the battery. Maybe that gives any clue?

ScPo said:
I did do the factory reset. I just wiped the areas separately as well. Anyway, I took your advice and installed the latest stock rom. Now I got the Samsung logo slightly flashing blue for hours instead of the cyanogenmod logo. Did not do anything else.
I suspect that its a battery issue in some way. The last weeks the phone lost its charge very quickly very often (not constantly though). Yesterday, the phone was in my pocket and then went off. It went into the constantly trying to restart despite the lack of batteries state until I removed the battery. Maybe that gives any clue?
Click to expand...
Click to collapse
Try booting into stock recovery, then factory reset from there. Last time I went back to stock I had a bootloop until I did this, then it booted properly. If that doesn't work, maybe try new battery.
Have you tried booting up whilst plugged in to a usb charger?

noppy22 said:
Try booting into stock recovery, then factory reset from there. Last time I went back to stock I had a bootloop until I did this, then it booted properly. If that doesn't work, maybe try new battery.
Have you tried booting up whilst plugged in to a usb charger?
Click to expand...
Click to collapse
Thanks for your helpful input.
I did what you said, even tried it twice now. Phone is still booting after 20 minutes now. I also tried booting up while charging the phone, yes. That was my standard procedure actually, but nothing changes when I unplug it. I don't have a different battery and I am wary of buying one just for the sake of trying. Tried that when my galaxy s 1 broke down and that didn't save the phone. At this point I am contemplating if the phone (s3) is broken now or not. It still reliably boots to the recovery, but it doesn't do much else. How are the chances?
Or has anyone any idea on how to proceed?

ScPo said:
Thanks for your helpful input.
I did what you said, even tried it twice now. Phone is still booting after 20 minutes now. I also tried booting up while charging the phone, yes. That was my standard procedure actually, but nothing changes when I unplug it. I don't have a different battery and I am wary of buying one just for the sake of trying. Tried that when my galaxy s 1 broke down and that didn't save the phone. At this point I am contemplating if the phone (s3) is broken now or not. It still reliably boots to the recovery, but it doesn't do much else. How are the chances?
Or has anyone any idea on how to proceed?
Click to expand...
Click to collapse
Try to boot into recovery. Do a factory reset then boot straight into download mode and flash stock rom. You might have to redownload the firmware it could be corrupted.. If that doesn't work then you might have to send it in. It might cost about to fix. Or go to your local phone repair shop and see if they could fix it for cheaper
Sent from my GT-I9305 using XDA Forums