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.
Related
I tried to use the modified Touchwiz with no avail. I replaced the new touchwiz file and renamed the old one. I restarted my phone, but when I unlocked my screen, I got into a loop of my new touchwiz file not responding. I've tried a couple things so far but nothing's worked so far. I've tried a couple things, but I'm still getting nothing. I'll update this with what I end up with.
Thanks in advance.
EDIT: I just formatted my system and data from clockwork. Now, I'm stuck at the boot screen when I start up my phone. I think I'm just digging my hole deeper.
Factory Reset through Clockwork Recovery seems the best option? Not sure what you mean by formatting system and data, but a factory reset should do it.
If all else fails, you can always flash a original ROM from Samfirware.com through Odin (if you can get into Download mode).
Of course your phone won't start up if you empited your system and data folder! It's like formatting your harddrive and expecting Windows to be able to boot.
Just flash a new rom using ODIN.
2 nights ago I thought I would have a go at installing ULTIMATE ROM 3.0. I have flashed many Roms on my Galaxy S before and not had a problem yet. I have ClockworkMod Recovery 2.5.1.0 installed.
However, this time- something went wrong. I don't think the installation completed properly. When I tried to reboot the system (to go back into my previous ROM) I wasn't able to. The Samsung logo appeared before the phone booted back into Recovery mode.
I tried to re-flash my previous working update.zip but had problems. I wasn't able to properly re-flash as the Installation would abort for various reasons. After doing cache clearing and data/factory reset I still had no luck. I resorted to reformatting the sdcard. Still didn't solve the flashing problem.
Throughout the whole time I was able to adb into the phone, browse the file system and I could push files on to it and take files off. But Kies wouldn't recognise the phone and Odin isn't able to complete a transfer to the phone (not sure why).
Today, I am able to successfully flash update.zip files (at least, that's what it looks like) but the phone ALWAYS boots into ClockwordMod recovery.
I am fast running out of ideas. Does anyone have any suggestion?
How can I tell if my ROMs are really 'there' but I can't access them because ClockworkMod is preventing them from booting?
hmmm... me too.. stuck in a loop, that keeps going back to the CWM recovery menu, and no matter what i do, keeps going back to it... cant even get to the download screen to flash (again).... here i was thinking no matter what happens when installing custom roms, i can always flash to my stable secure rom, but not this time... need some software that can perform surgical operations, any suggestions?
bradels said:
2 nights ago I thought I would have a go at installing ULTIMATE ROM 3.0. I have flashed many Roms on my Galaxy S before and not had a problem yet. I have ClockworkMod Recovery 2.5.1.0 installed.
However, this time- something went wrong. I don't think the installation completed properly. When I tried to reboot the system (to go back into my previous ROM) I wasn't able to. The Samsung logo appeared before the phone booted back into Recovery mode.
I tried to re-flash my previous working update.zip but had problems. I wasn't able to properly re-flash as the Installation would abort for various reasons. After doing cache clearing and data/factory reset I still had no luck. I resorted to reformatting the sdcard. Still didn't solve the flashing problem.
Throughout the whole time I was able to adb into the phone, browse the file system and I could push files on to it and take files off. But Kies wouldn't recognise the phone and Odin isn't able to complete a transfer to the phone (not sure why).
Today, I am able to successfully flash update.zip files (at least, that's what it looks like) but the phone ALWAYS boots into ClockwordMod recovery.
I am fast running out of ideas. Does anyone have any suggestion?
How can I tell if my ROMs are really 'there' but I can't access them because ClockworkMod is preventing them from booting?
Click to expand...
Click to collapse
myrobelle said:
hmmm... me too.. stuck in a loop, that keeps going back to the CWM recovery menu, and no matter what i do, keeps going back to it... cant even get to the download screen to flash (again).... here i was thinking no matter what happens when installing custom roms, i can always flash to my stable secure rom, but not this time... need some software that can perform surgical operations, any suggestions?
Click to expand...
Click to collapse
Thats too bad guys,and i m sorry to hear that news.I would like to havean answer but i dont...
The fact is that since most people in this forum use some custom roms,and all of us think the same,that we can always go back,so it would be great if you give some more details about what happened to you,and mybe why it went wrong,and it would be even better if one of the BIG guys would give some explanation about this...
I already thinking of not updating my rom anymore,dot want to end up in looping too,so lets see if someone will find something.Good luck guys..
By the way,i didnt get it right,CWM recovery cannot load your backup????
I just got an idea,but not sure if or how it would work or not.
Since you can push file with ADB,if soeone made a clean backup with his CWM (o e mail,contacts,setting saved) and send it to you,so that you log in with CWM recovery and flash that ???
Just an idea..maybe stupid dont know...
Its not very clear if youve tried this already but cant you just boot into recovery through adb? or does that not work either?
So I'm trying to get my VZN Galaxy Tab back on its feet. After trying to get Gingerbread in it so I can use Netflix - and failing - I'm going through a lot of motions.
Okay. First I rooted it with Super One Click. I should have been happy with that, but noooo. Then I tried flashing GB on it (I wish I can remember which ROM I started with...it's a mess. I think the pit file was gt-p1000_mr? Does that sound right?).
When that didn't work, I went to the much-cross-posted procedure for returning it to stock using Heimdall and SCH-i800_VZW_stock. Tried it five times. Each time, it booted into the Galaxy Tab/Samsung logos, then a fast glimpse of scrambled letters for a second followed by twinkly music, then black nothingness. It would then bootloop. I attempted to boot into recovery to wipe data/cache, but I couldn't get there. Vol-Up/Pwr just brought up the logo and scrambled video again.
Since I was still able to get into download mode, I tried flashing another ROM...this one the "P1000XXJQ1_P1000XXJQ1_P1000XXJPZ" method. With this, I was able to also flash CWM so I have SOME recovery mode. Sadly, booting brings up the GT/SAMSUNG logos and I get the spacey animation, but after that, again - blackness. This time, however, the Menu/Home/Back/Search buttons light up, so something's happening in there.
Also, booting into CWM, I cannot get my sdcard to be recognized. I tried different cards, so there's something goofy with the slot itself, I'm guessing.
So nothing is really working, but since I can get into CWM and also download modes, I'm holding out hope that this is not completely bricked.
I just need to find the right method of getting it back to a functioning tablet. If anyone has any suggestions, I'm all eyes. Thanks so much.
UPDATE: I tried reflashing stock using the tried and true method. But this time, I went in and flashed CWM replacing the stock recovery which never worked for me. I got the Galaxy Tab/Samsung logo, and at long last, the animated VZW logo. Then it would bootloop there. I booted into CWM recovery and wiped the data/system and the cache from the first page. It still booted and bootlooped the same. This time, I booted into recovery, went to the mounts and storage section and formatted the system, data and cache. Opening logo only. CWM again, and got a whole bunch of "cache missing" messages. But I think I'm getting closer. Back to work.
UPDATE II: So the farthest I can get is the animated VZW logo using the combo of the stock flash through Heimdall, then flashing CWM with Odin. Still no sdcard access. Anything I should try here? Thanks.
same question here
Did anyone figure out how to restore Verizon tab?
hi, yes i will admit i am still very new to the whole rooting/flashing/mods etc, but i f-ed up my captivate bad... first i should tell ya how i got to the point where i am now... (dont worry will be the abridged version):
-got phone, couldnt sideload apps
-rooted phone and enabled install of sideloaded apps
-tried to backup rom/phone with clockwork, learned that i had to flash modded kernal
-backed up and flashed new kernal (flashed clockwork recovery & backed up rom)
-learned about voodoo, so reflashed a voodoo kernal
-started to have issues with static, speaker volume, basically anyone who called me or i called couldnt hear me and was all static
-reflashed different kernal
-got ballsy, backed up rom again, and all user/system data, and attempted to flash custom rom (firefly3.0)
-flash failed... tried to reflash, failed again... error said parameters did not match
-tried restoring original backed up rom, failed again, and again...
-then, boom, phone boots up and am able to make calls and receive them, cant send text though..
-scoured the forums, and tried to fix phone/restore to stock.
-flashed odin, and then BRICKED!!!!
*NOW ALL PHONE DOES WHEN I TURN IT ON IS BOOT TO ATT SCREEN AND THEN OFF, THEN ATT SCREEN, THEN OFF.. TRIED BOOTING INTO RECOVERY, DOWNLOAD MODE AND STILL NOTHING WORKS...
wondering what happened, or what i did wrong, what i can do to fix my phone (if possible)????
any of u wicked smart devs care to help out a little 'ol noob?? please
obviously its not bricked!
i hate that misnomer. you are bootlooping....
you need a jig at this point if normal means of getting into download mode do not work
(power down phone, pull battery. put battery back in, and while holding vol up+down, plug into computer.) if that doesnt put you in download mode, you definitely need a jig.
once you get that jig, flash a custom cwm kernel, then try flashing a new rom. you dont need to boot into stock, which is what you are stuck on now.
BY DEFINITION: A BRICK IS SOMETHING THAT NO LONGER POWERS ON, AT ALL
Damn beaten to the punch.
Sent From My Captivating Shanna, yes I Named My Phone get over it.
I've been looking all over this site but I can't find anything. I suppose that it's partly because I'm not sure about the problem myself.
A couple of months back (maybe more) I upgraded to the ICS infinitum rom (blue version) with midnight kernel. It was great - the phone worked fine. Well I'm exaggerating, it ****ed up every once in a while. Programs would automatically shut down and it would get really slow after a while. But all in all it wasn't bad, and it was stable enough for me most of the time....
Then, last Thursday everything seemed to go apart, every program on the phone was shutting down. So I thought I'll just restart and it will be fine. When I did, the phone did not come back on. the kernel would load and then it was stuck on the start-up animation in infinite loops.
Now, to be frank, this isn't the first time this has happened. So I didn't panic. Last time I just used the CMW recovery to re-install the kernel and the rom (I keep the files on the sd card). But this time, I wanted to try to avoid the factory wipe for as long as I could, and try finding a different option, knowing that if all else fails, I have something to revert back to.
Then I did the mistake of deleting the init.d file without re-installing anything. I wanted to, but accidentally clicked on the 'reboot now' option. And then all went to ****. The kernel didn't load. I went to recovery and it couldn't mount the sd card so I couldn't re-install it.
I tried flashing a new kernel using odin, and it did get me a bit better: my CWM recovery can read the sd. However, I still can't mount the system. Even worse, when I get to the infinitum zip roms and re-installing it brings up the status 7 error (which, after searching, seems to come up for different reasons for each person)
Despite installing a new kernel, when I reboot the phone now it doesn't load the kernel anymore, it just stays stuck on the welcome screen. I tried using the recovery to re-install a different kernel, it worked, but the phone still won't start - it now automatically skips to the recovery mode. I don't know if I should try flashing a rom through odin, and I'm too afraid to try anything at all now...
Can anyone help me? Is there any way to restore the init.d file or maybe that has nothing to do with my problem?
uvii said:
I've been looking all over this site but I can't find anything. I suppose that it's partly because I'm not sure about the problem myself.
A couple of months back (maybe more) I upgraded to the ICS infinitum rom (blue version) with midnight kernel. It was great - the phone worked fine. Well I'm exaggerating, it ****ed up every once in a while. Programs would automatically shut down and it would get really slow after a while. But all in all it wasn't bad, and it was stable enough for me most of the time....
Then, last Thursday everything seemed to go apart, every program on the phone was shutting down. So I thought I'll just restart and it will be fine. When I did, the phone did not come back on. the kernel would load and then it was stuck on the start-up animation in infinite loops.
Now, to be frank, this isn't the first time this has happened. So I didn't panic. Last time I just used the CMW recovery to re-install the kernel and the rom (I keep the files on the sd card). But this time, I wanted to try to avoid the factory wipe for as long as I could, and try finding a different option, knowing that if all else fails, I have something to revert back to.
Then I did the mistake of deleting the init.d file without re-installing anything. I wanted to, but accidentally clicked on the 'reboot now' option. And then all went to ****. The kernel didn't load. I went to recovery and it couldn't mount the sd card so I couldn't re-install it.
I tried flashing a new kernel using odin, and it did get me a bit better: my CWM recovery can read the sd. However, I still can't mount the system. Even worse, when I get to the infinitum zip roms and re-installing it brings up the status 7 error (which, after searching, seems to come up for different reasons for each person)
Despite installing a new kernel, when I reboot the phone now it doesn't load the kernel anymore, it just stays stuck on the welcome screen. I tried using the recovery to re-install a different kernel, it worked, but the phone still won't start - it now automatically skips to the recovery mode. I don't know if I should try flashing a rom through odin, and I'm too afraid to try anything at all now...
Can anyone help me? Is there any way to restore the init.d file or maybe that has nothing to do with my problem?
Click to expand...
Click to collapse
I suggest flash 3-file GB rom via odin with ticked re-partirion and phone bootloaderupdate.
First of all init.d has nothing to do with the boot of kernel and ROM itself. It's just like autostart in Windows, so if it's missing it shouldn't cause problems.
My solution is to flash a complete stock Gingerbread ROM using Odin. You can get them at sammobile.com. Then afterwards flash a custom kernel and then whatever you like.
If you need help,feel free to ask me
Sent from my Gameboy Color
Yes! Thank you! That worked!!
It happened again! just 10 days later.
Is the Infinidtum rom ****ed up in any way?
it's stuck on the loading part of the rom