Hello!
I bought my Galaxy S a few days ago, and updated it to 2.2
But then the keypad and swype didn't have danish language.
Anyhow, i tried to install Darky's v8.1 gingerbread ROM (wipe)
I followed the instructions.
But when i went to recovery mode, and pressed the "apply update.zip" (something like that) it rebooted, but froze at the startup screenwhere it says GALACXY S, GT-I9000, SAMSUNG)
Now I can't enter my phone . I can't enter recovery mode, only the download mode.
How do i fix this???
is it like "spring cats" only for flashers and january? Thats like 5th misplaced topic here in a day.
To answer - reflash with odin. Read in faq in general section (I think its there).
Okay i will take a look at it. Thank you.
Btw, sorry if i misplaced it, I am just panicing at the moment
You need to give time for dalvik to be rebuilt. Guys, help or refrain from
posting. Mods know best.
Sent from my GT-I9000 using XDA App
Go to download mode and use odin to flash a stock firmware. You can download them from
www.samfirmware.com
Sent from my GT-I9000 using XDA App
wrong section.. also remember first boot after flashing a new ROM could take sometime..
kroHHn said:
Hello!
I bought my Galaxy S a few days ago, and updated it to 2.2
But then the keypad and swype didn't have danish language.
Anyhow, i tried to install Darky's v8.1 gingerbread ROM (wipe)
I followed the instructions.
But when i went to recovery mode, and pressed the "apply update.zip" (something like that) it rebooted, but froze at the startup screenwhere it says GALACXY S, GT-I9000, SAMSUNG)
Now I can't enter my phone . I can't enter recovery mode, only the download mode.
How do i fix this???
Click to expand...
Click to collapse
Read the first post in Darky's thread:
2nd thing:
The Wipe version has an issue - it's known.
Just install the v8.0 and then v8.1 No-Wipe. It works perfectly.
Rofl, i'm doing a facepalm right now
Anyways it worked, thanks guys!
The question is now, should i try again (8.0 ofc) or should i just be happy with 2.2 ??
Related
I had a stock I9000 with 2.3.4 XXJVQ. I rooted it with CF-ROOT 3.7 using these instructions: androidadvices.com/root-samsung-galaxy-gt-i9000-android-234-xxjvq-firmware/3/ and CF-Root-XX_UNK_JVQ-v3.7-CWM3RFS.tar and Odin3 v1.7 from the provided archive.
These worked all right and it also installed CWM 2.0
Then I downloaded CM7.1 stable from here: cyanogenmod.com/devices/samsung-galaxy-s and followed the instructions here to install: wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide#Method_via_Recovery
I wiped the data, wiped the cache and then selected "Install zip from sdcard" and then I choose the CM7.1 zip file and after a few seconds the phone entered a reboot cycle. For a moment the Cyanomodgen logo and the Samsung logo appeared, then a few lines of text, and then it rebooted and did the same.
I've waited about 10 minutes and nothing changed, and then proceeded to install CF-ROOT again via Odin thinking that it would solve it and revert back to what I had. Boy, was I wrong! Now it just hangs on the Samsung logo screen.
The phone still enters Download mode, so from what I've read it's recoverable, but I'm kinda scared to try anything else without knowing for sure that it would work because I don't want to brick it harder.
Since I'm a new user, the forum won't let me link properly. Sorry.
Any advice? Thanks.
pandronic said:
I had a stock I9000 with 2.3.4 XXJVQ. I rooted it with CF-ROOT 3.7 using these instructions: androidadvices.com/root-samsung-galaxy-gt-i9000-android-234-xxjvq-firmware/3/ and CF-Root-XX_UNK_JVQ-v3.7-CWM3RFS.tar and Odin3 v1.7 from the provided archive.
These worked all right and it also installed CWM 2.0
Then I downloaded CM7.1 stable from here: cyanogenmod.com/devices/samsung-galaxy-s and followed the instructions here to install: wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide#Method_via_Recovery
I wiped the data, wiped the cache and then selected "Install zip from sdcard" and then I choose the CM7.1 zip file and after a few seconds the phone entered a reboot cycle. For a moment the Cyanomodgen logo and the Samsung logo appeared, then a few lines of text, and then it rebooted and did the same.
I've waited about 10 minutes and nothing changed, and then proceeded to install CF-ROOT again via Odin thinking that it would solve it and revert back to what I had. Boy, was I wrong! Now it just hangs on the Samsung logo screen.
The phone still enters Download mode, so from what I've read it's recoverable, but I'm kinda scared to try anything else without knowing for sure that it would work because I don't want to brick it harder.
Since I'm a new user, the forum won't let me link properly. Sorry.
Any advice? Thanks.
Click to expand...
Click to collapse
Can you get 3 button recovery again? If you can just reflash cm7
Instead of reflashing the kernel through Odin you should have taken out the battery. Then 3 button comboed back into recovery and reflashed cm7
If you can't get into recovery again reflash a stock rom with odin.. then a kernel then has cwm recovery.. reboot into recovery mode then flash cm7.. and if you get the same boot loop as before pull the battery, 3 button into recovery and flash cm7 again.. then you will be good to go
Sent from my GT-I9000 using xda premium
Jason123420 said:
Can you get 3 button recovery again? If you can just reflash cm7
Instead of reflashing the kernel through Odin you should have taken out the battery. Then 3 button comboed back into recovery and reflashed cm7
If you can't get into recovery again reflash a stock rom with odin.. then a kernel then has cwm recovery.. reboot into recovery mode then flash cm7.. and if you get the same boot loop as before pull the battery, 3 button into recovery and flash cm7 again.. then you will be good to go
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
First time I entered CWM using the CWM app and selecting "reboot into CWM". Is there another combo besides home+vol down+power for dl mode?
Could you recomend a good stock ROM?
Thanks
pandronic said:
First time I entered CWM using the CWM app and selecting "reboot into CWM". Is there another combo besides home+vol down+power for dl mode?
Could you recomend a good stock ROM?
Thanks
Click to expand...
Click to collapse
volume up, home and power will give you recovery when your phone is turned off..
Any stock gingerbread will do when trying to go to cm7
Sent from my GT-I9000 using xda premium
The first time you flash CM7, you might need to flash it twice. AKA
1) Flash once
2) Reboot. Now you are stuck in bootloop.
3) Pull battery. Go into recovery mode again
4) Flash cm7 again
5) Should boot normally now.
It's a common occurrence.
Oops beat me to it
It doesn't go into recovery anymore (home+vol up+power). I'll try to flash a stock ROM with Odin and see how it goes.
Edit1:
For people having this problem. I've flashed using the ROM and instructions here:
androidadvices.com/update-samsung-galaxy-i9000-official-gingerbread-235-xfjva-firmware/2/
This is 2.3.5 XXJVT
Edit2:
I've went to this thread:
forum.xda-developers.com/showthread.php?t=788108
and got the proper CF-ROOT for XXJVT and flashed it with Odin3 v1.7
Edit3:
I've installed CM7.1 using the instructions linked in the first post and everything worked out fine. Thanks everybody.
pandronic said:
It doesn't go into recovery anymore (home+vol up+power). I'll try to flash a stock ROM with Odin and see how it goes.
Edit1:
For people having this problem. I've flashed using the ROM and instructions here:
androidadvices.com/update-samsung-galaxy-i9000-official-gingerbread-235-xfjva-firmware/2/
This is 2.3.5 XXJVT
Edit2:
I've went to this thread:
forum.xda-developers.com/showthread.php?t=788108
and got the proper CF-ROOT for XXJVT and flashed it with Odin3 v1.7
Edit3:
I've installed CM7.1 using the instructions linked in the first post and everything worked out fine. Thanks everybody.
Click to expand...
Click to collapse
Glad your up and running.
Sent from my GT-I9000 using xda premium
okay so I thought bricking android would be complicated but as it turns out it's quite simple.
Please cut me some slack because I am a n00b at all this. I am already googling for a solution and looking on forums but I haven't found anything YET so after a desperate hour of googling I thought of posting here (I will keep on trying to find a solution though).
Here is what I did:
A long while ago I rooted my Galaxy S. Rom was ClockworkMod (recovery says ClockworkMod Recovery v3.0.0.5) and the kernel was Talon. No problem with this.
Now I wanted to do a factory reset so I dialed that number yo need for a factory reset. I got a red text message warning me NOT to touch any button and it would reboot. The phone rebooted and I think I got into the recovery mode.
The icon was a top cat in an orange circle with an arrow. I guess that's part of the Talon kernel.
Anyways on recovery mode screen I saw an option called "wipe/factory reset" I've selected it - I was told it can't be undone- I've said OK- It said everything went fine so I selected reboot.
Now the phone won't reboot. It is stuck in a loop. It will always try to reboot.
So all I see is a GALAXY S i9000 screen followed by a Talos screen with a loading bar followed by the GALAXY S i9000 screen again and it will just loop.
No idea what to do :C
help, please! thanks a million everyone!
Try flash the talon kernel again or if u got a rom on your SD card flash that.
If this doesn't work.search for ezbase 3.0 and follow instructions on how to flash a rom with ODIN.
U can also find ezbase on "insanity rom" thread in the op(1 of the links)
And now your phone is recovered
zodiaxe66 said:
Try flash the talon kernel again or if u got a rom on your SD card flash that.
If this doesn't work.search for ezbase 3.0 and follow instructions on how to flash a rom with ODIN.
U can also find ezbase on "insanity rom" thread in the op(1 of the links)
And now your phone is recovered
Click to expand...
Click to collapse
well I've tried to put an update.zip on the internal storage of the phone because I don't have an external SD card.
I mounted the phone as mass storage device in the recovery mode but my win xp 32 bit would say it is a Samsung Galaxy S but there was an error with the new hard ware and it couldn't be mounted fff
so no idea what to do now?
This is normal, you delated youre whole System. First of all dont panik you able to enter ist downloadmode ? If so, than you'll bei able to install a new rom and you will be able to boot I'm also New here had the same problem with my phone. This is called a soft-brick. I was able to go in DM and flash a new rom with my galaxy s plus
Sent from my GT-I9001 using XDA
Diablob555 said:
This is normal, you delated youre whole System. First of all dont panik you able to enter ist downloadmode ? If so, than you'll bei able to install a new rom and you will be able to boot I'm also New here had the same problem with my phone. This is called a soft-brick. I was able to go in DM and flash a new rom with my galaxy s plus
Sent from my GT-I9001 using XDA
Click to expand...
Click to collapse
vielen lieben dank
yeh i guess i did a soft brick. So what exactly do I do now?
I have managed to copy an update.zip file I've found on my computer to the phone but the download mode gives me an error and says it can't install it.
Can you link me to the files I need to install on it with the help of the download mode? Thanks a lot
so I have already tried installing different roms which seemed to have worked fine
I have tried just any random rom (Simplicity) I could find on this forum. It installed but I am still stuck in a boot loop. I don't see the Talon graphic anymore but the Galaxy S animation but I am still stuck in a loop.
help :C
zodiaxe66 said:
If this doesn't work.search for ezbase 3.0 and follow instructions on how to flash a rom with ODIN.
U can also find ezbase on "insanity rom" thread in the op(1 of the links)
And now your phone is recovered
Click to expand...
Click to collapse
http://www.theandroidsoul.com/ezbase-rom-v3-0-full-installation-guide-w-video/
is what ive found when googling. of course ALL THE FILES are offline again. what a surprise.
really a shame. this looked so promising :C
i've flashed a different ROM in the mean time but it doesn't let me flash anything else anymore. that recovery mode is awful so i can only suggest no one uses simplicity rom
You need to flash a new firmware using odin, partition with 512 pit. Check this link for instructions and firmware. http://forum.xda-developers.com/showthread.php?p=14273101
Sent from my GT-I9000 using xda premium
I am very new to rooting and all the stuffs. However i decided to root my phone following a youtube video tutorial made by this guy called Ashwin on XDA. I followed all the instructions carefully and rooting was successful. Then i proceeded to install CWM recovery following another youtube tutorial made by the same guy and it was successfully installed. Afterwards i flashed RocketIcs rom v1 using the CWM recovery mode and it says the installation was successful...
however, after the installation i realized that my note would keep rebooting and rebooting after 30 secs or so. i am really scared now because i am really a noob in this field and i am at a lost what to do. I will really appreciate if anyone can help ;(
I think you didn't flash the abyss kernel b4 flashing the rocket rom
jcheong said:
I think you didn't flash the abyss kernel b4 flashing the rocket rom
Click to expand...
Click to collapse
i think i did. in the tutorial video i followed, i downloaded the abyss kernel 4.2 as directed and flashed it with mobile odin. Then i rebooted into CWM recovery mode and flashed the rocket ics rom v1. then started the bootloop.
to give you further details, my rooted note has kernel version N7000DXLC2 before i flashed the rocket ICS rom. please help i am really thankful!
Im new here too but I think I may know what the err is.
Do you have Titanium-backup App, Clockworkmod Recovery App &/or Nandroids on your Note? If not once this thing gets fixed I recommend you do some homework so that you don't lose everything next time.
Good News is it isn't Fully Bricked (I think)... If it was bricked than it wouldn't even boot at all. Better News is... I have been doing a lot of research - So this might work. It sounds to me that you are in a Boot loop.
In that event...
chasmodo said:
1. pull out your battery, wait for 1 minute
2. put it back in, boot into stock Recovery (volume up + home + power)
3. do a factory reset and wipe cache
4. reboot
Click to expand...
Click to collapse
Good Luck.
CrazyOGuy said:
Im new here too but I think I may know what the err is.
Do you have Titanium-backup App, Clockworkmod Recovery App &/or Nandroids on your Note? If not once this thing gets fixed I recommend you do some homework so that you don't lose everything next time.
Good News is it isn't Fully Bricked (I think)... If it was bricked than it wouldn't even boot at all. Better News is... I have been doing a lot of research - So this might work. It sounds to me that you are in a Boot loop.
In that event...
Good Luck.
Click to expand...
Click to collapse
yes i have titanium backup and clorkworkmod recovery installed but i dont have nandriods on my note. From what i have been researching, i heard that i have to flash a LPY stock rom and then flash the rocketics rom v1 again. Any idea or links to flash a LPY stock rom safely from my current state? thanks alot!
After you rebooted inte recovery, did you reboot recovery? Jag was the recovery text red? /snabben
Sent from my GT-N7000 using xda premium
snabben said:
After you rebooted inte recovery, did you reboot recovery? Jag was the recovery text red? /snabben
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
sorry i dont get it. i dont understand what u mean.
I might be mistaken but i think i had to reboot recovery to get the abyss, the red pill one and not the cwmr,
Hi, first post here so if I screwup any of the etiquette please tell me.
Ok, so I've had my P1000 for about two years now, no contract, not locked to sprint / verizon etc.
I had 2.3.3 at the start, but after seeing mannnny people flashing to ICS successfully I had to give it a go.
Attempted to flash using overcome kernel for CWM, failed and I had to odin back to 2.3.6 (couldn't find a 2.3.3 rom).
I kept it on 2.3.6, but I was unhappy and so am trying again:
It's important to know that I am now on a mac, so will not had access to odin, and instead am forced to use heimdall. Please don't post any odin specific instructions.
In order to get CWM I had to flash the overcome kernel, which includes the recovery mod.
I successfully used heimdall for this, following a specific instruction guide.
I then downloaded "cm-9-20120703-NIGHTLY-p1.zip" from get.cm, and copied it to my externalSD on my gt.
Booted into recovery, wiped all data/factory reset, wiped cache, wiped dalvik, and went to install form an externalSD.
I chose my file, and the installation / flashing (not sure as to the terms. ) began.
It went through a few messages, but however once it said "Checking state of BML/MTD" it reboots instantly and shows the cm startup for about five seconds before going into recovery. Always does this on startup, no way to change.
The only way to fix this is to go into recovery and wipe all data, but this leaves me on my 2.3.6 rom.
I have NO idea what's happening, and I can't use most guides due to them being odin specific.
If anyone can assist me, please do.
Don't link to any odin threads, and don't tell me to search, for I have been doing so for eight hours.
Cheers,
Zero
EDIT: SOLVED!!!
After flashing once it failed at BML/MTD, so I opened recovery and flashed from "internal sd". Worked a charm, now installing gApps.
Cheers for helping Priyana!
that is call boot loop.
Just boot to recovery and flash it once more
it is quite documented.
About etiquette, post [Q] in Q&A subforum, not general
priyana said:
that is call boot loop.
Just boot to recovery and flash it once more
it is quite documented.
About etiquette, post [Q] in Q&A subforum, not general
Click to expand...
Click to collapse
That's the thing - when I boot to recovery after flashing (and failing) CM9, it is a different sort of recovery and doesn't allow me to install from an externalSD.
Cheers for replying,
Zero
just the name change.
the internal and external got swapped around in that newer recovery
priyana said:
just the name change.
the internal and external got swapped around in that newer recovery
Click to expand...
Click to collapse
As I just noticed.
Installed PERFECTLY!
It's up and running - however I can't see a market?
Cheers,
Zero
You didn't flash gapps.
Didn't you read the instruction?
Sent from my GT-P1000 using xda app-developers app
priyana said:
You didn't flash gapps.
Didn't you read the instruction?
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
I gave up on instructions after five hours of them failing.
Reread now and just about to reflash with gapps
Cheers,
Zero
Yeah. Believe it or not, early adopter has advantages because we have read up all!
Sent from my GT-P1000 using xda app-developers app
Yeah
Works so well, already have tapatalk and all gapps are working perfectly.
And the instructions - I was following them perfectly, but they did not go in depth when it came to reflashing with the newly installed rom-manager of cm9.
All works perfectly now, thanks for your help
Sent from my GT-P1000 using Tapatalk 2
I've got this exact issue coming over from Frankenclean 2.8 on the samsung fascinate. I decided to update my rom as it was falling behind the 'curve' if you will.
I'm now stuck at a bootloop "samsung" and "S-cyanogen(mod)" screen. they just go back and forth. I'm following this http://forum.xda-developers.com/showthread.php?t=1238070 to the letter and still getting the issue. I've tried flashing a newer kernel that is for 4.x.x builds and no luck.
When I install or attempt to install cyanogen10 it fails on the bml/mtd check and it just reboots to those two screens.
I followed the 'fix' at section 9 but haven't had any luck getting cyanogen to install... I'd really appreciate a little help, ideas, questions, anything.
I know it's an older device, I'm just hoping someone out there with more dev knowledge than I possess "read: none" can help me out.
bump...
Got it to boot into a stock rom, but have 0 luck getting my nandroid to load up and be functional using CWM 2.4 (red). Which is what I made the recovery with.
Might end up with a stock phone if I can't figure it out, I don't mess with roms often.
Luckily I do have titainium backup so all my apps are saved. Just sucks to not have a sleek rom anymore. Not to mention I want jellybean. Any help is appreciated!
fixed it, 4.1 didn't like my phone, got hellybean 4.2 on it without a problem .
Only issue is that google voice to text doesn't work, nor google search.
Hi Peeps, Happy New Years
Don't Worry I read every thread on XDA and no one has a problem as similar as mines and don't know EXACTLY what type of brick I have.
I got this problem with my Galaxy Note (N7000):crying:
It all started when I was running Ultimate Rom v6 and decided to upgrade to kitkat.
I searched around and found that Spirit Rom had quite positive reviews.
So I downloaded the rom and tried to flash but then ended up with status 7 error.
I then found out I was using an outdated version of CWM (I think it was 6.0.3.7)
I then flashed this file by zedomax (http://downloadandroidrom.com/file/GalaxyNote/recovery/n7000-CWM-KitKatCompatible.zip)
because it had compatible recovery with Kitkat roms and CM 10.2 kernal. Installation went fine and I set up everything.
I then installed lollipop theme (It came with boot animation). Then I rebooted to see how the boot animation looked but to my despair I got stuck at Samsung Boot Logo Screen and couldn't get past it. I couldn't get into recovery, only downloading mode. So then I flashed stock JB rom with PC (Odin). The flashing was successful but I'm still stuck at Logo screen.
Also I would like to also mention that the phone was NEVER on ICS. It was on stock GB 2.3.6, then rooted and flashed Ultimate Rom V6.
Any help would be appreciated :highfive::victory:
GD people. Read. Go to the how to install a KitKat ROM thread.
Sent from my GT-I9205 using Tapatalk
AndroidSlave said:
GD people. Read. Go to the how to install a KitKat ROM thread.
Sent from my GT-I9205 using Tapatalk
Click to expand...
Click to collapse
@AndroidSlave
Calm down dude!
I read the thread properly.......
Unfortunately something went wrong and I'm asking for help (I really don't even know how I messed it up).......
Do you have a problem with that?
I have experience with rooting and custom roms and have never came across something like this.....
007Uzzi said:
@AndroidSlave
Calm down dude!
I read the thread properly.......
Unfortunately something went wrong and I'm asking for help (I really don't even know how I messed it up).......
Do you have a problem with that?
I have experience with rooting and custom roms and have never came across something like this.....
Click to expand...
Click to collapse
If the last thing you did was flash 4.1.2 via PC Odin then flash the correaponsing philz kernel in PC Odin, boot to recovery, and do a factory reset. If you don't want stock TW, then do the above, and then follow the guide on how to flash a KitKat ROM. I feel your error may involve not doing proper wipes, including preload.
Sent from my GT-I9205 using Tapatalk
AndroidSlave said:
If the last thing you did was flash 4.1.2 via PC Odin then flash the correaponsing philz kernel in PC Odin, boot to recovery, and do a factory reset. If you don't want stock TW, then do the above, and then follow the guide on how to flash a KitKat ROM. I feel your error may involve not doing proper wipes, including preload.
Sent from my GT-I9205 using Tapatalk
Click to expand...
Click to collapse
Thanks Dude , You helped think of of something
BTW I fixed it
Maybe my recovery was corrupted or something...... So I was browsing around sticky threads an somehow reasoned it out to flash a prerooted + cwm rom through odin.
This is what I did:
1. Download this http://d-h.st/HJM
2. Flash with PC Odin (Add via PDA button and make sure ONLY Auto reboot is checked)
3. Wait till completed
4. When completed you will still get stuck then....
5. Boot into recovery (Which will now be CWM)
6. Do a factory reset and wipe cache and dalvik cache
7. Reboot
8. Give the logo screen a minute or two
9. Then I get directly to welcome screen.
10. Done
One more thing is do you know what was the cause of this? It's really interesting to know...........
Yeah improper wipes or flashing the wrong kernel for the wrong rom
Sent from my GT-I9205 using Tapatalk