Hi.
I'm not too sure if my phone is now past the point of no return.
After attempting to install the 2.2 updated for the galaxy s via going around the region limitation (regedit), I had a number of errors with the installation and tried to rectify it by doing a clean install. Only to follow directions and get a bad install with twlauncher etc failing to start up persistently.
SO, I used odin to try and create a completely new flashed firmware, following further recommended instructions. After attempting to restart my SGS and thinking I would get to the final step I was led to a screen flashing "at&t world phone" in an infinite loop, is it now game over for my phone or is there a way out of this?
Insurance to the rescue
After reading a similar post, I've decided just to use my insurance and either wait or don't push my phone past lagfix.
Once bitten twice shy.
Related
y helo thar :3
Okay, to sum it up, today I bought a used Bell Samsung GT-i9000M and realized that the owner never updated his phone to Gingerbread (2.3) from his current version of 2.1. Basically, I did the same procedure as in THIS (EDIT: I think I just realized that the stops shown in that link, having next to nothing to do with updating your phone to 2.3 - kjawekjawen - post still stands, of course) post.
In Odin, everything seemed like a success, until (after Odin labeled it as a success apparently) my phone just started rebooting and rebooting, not getting past the first booting screen (that first black screen showing Samsung i9000 logo, I think).
I can still access the download mode, but my phone just doesn't boot up anymore (gets stuck on this same logo and just keeps restarting 'til the pigs come round).
I'm just afraid to do anything with my phone right nao. Consisder the fact that I am pretty much a noob in this whole hackz0r, elite department of the internets and cellphones. I would love (no homo, hurhurhur) for somebody to assist me through this, because I don't want to end up turning my cellphone into something resembling a clay brick.
:3
Thanks in advance for whoever could help me.
PROBLEM SOLVED: http://androidadvices.com/update-samsung-galaxy-gt-i9000-gingerbread-xxjvr-234-firmware/6/
OK, here is my story with my Galaxy Note brick. Though I never tried custom ROMs after upgrading to ICS but rooted with temp CWM & superSU. All seem to be working ok. One fine day I did a factory reset, booting failed, Stock ROM with PC ODIN stuck at FACTORYFS. Then comes XDA with a solution to use a patched PIT file.
Vola, my phone was up and running with ICS but missing 3GB space. It wouldn't have bothered me had the phone been stable. It used to freeze 2-3 times a day especially while downloading from Google play. Digging further in XDA forums for a fix cleared about eMMC bug and and no way returning back to normal So I ran to SSC with a factory reset phone hoping they will replace mobo, as it failed to boot and stuck at Samsung logo. Told them that Kies update to ICS 4.0.4 caused the problem. But couple of hours later, I got my phone back but with 8.24GB space & ICS 4.0.4
Now, I needed a fool proof way of bricking but couldn't go for pulling out battery half way through stock flash ROM. Thought it would be tricky to explain what I was upgrading when I've already got the latest stock ROM just a day ago from SSC. hmmm... then I got hold of stock PIT file... flashed it. And now perfectly stuck at home screen. No recovery menu but only download mode.
Next visit to SSC within 24hours and a simple story line with a sad face.... "Installed many apps, caused force close. So I did a Factory reset. And the phone does not boot now". It was stuck on the very first screen.
Finally it is gone for mobo replacement and expected to be ready in 2 days - covered under warranty Now coming to my question part, "What are the quick essentials checks to be done before accepting my phone from SSC" I really wish that it is all fixed properly and I do not want to visit a service center again
arvichan said:
OK, here is my story with my Galaxy Note brick. Though I never tried custom ROMs after upgrading to ICS but rooted with temp CWM & superSU. All seem to be working ok. One fine day I did a factory reset, booting failed, Stock ROM with PC ODIN stuck at FACTORYFS. Then comes XDA with a solution to use a patched PIT file.
Vola, my phone was up and running with ICS but missing 3GB space. It wouldn't have bothered me had the phone been stable. It used to freeze 2-3 times a day especially while downloading from Google play. Digging further in XDA forums for a fix cleared about eMMC bug and and no way returning back to normal So I ran to SSC with a factory reset phone hoping they will replace mobo, as it failed to boot and stuck at Samsung logo. Told them that Kies update to ICS 4.0.4 caused the problem. But couple of hours later, I got my phone back but with 8.24GB space & ICS 4.0.4
Now, I needed a fool proof way of bricking but couldn't go for pulling out battery half way through stock flash ROM. Thought it would be tricky to explain what I was upgrading when I've already got the latest stock ROM just a day ago from SSC. hmmm... then I got hold of stock PIT file... flashed it. And now perfectly stuck at home screen. No recovery menu but only download mode.
Next visit to SSC within 24hours and a simple story line with a sad face.... "Installed many apps, caused force close. So I did a Factory reset. And the phone does not boot now". It was stuck on the very first screen.
Finally it is gone for mobo replacement and expected to be ready in 2 days - covered under warranty Now coming to my question part, "What are the quick essentials checks to be done before accepting my phone from SSC" I really wish that it is all fixed properly and I do not want to visit a service center again
Click to expand...
Click to collapse
Be in safe kernel if your on ics. You could check your device of the bug by downloading eMMC check in google play. Dont put your fate in that if your on stock ics rom not rooted you will not get the bug, be on the safe side.
arvichan said:
OK, here is my story with my Galaxy Note brick. Though I never tried custom ROMs after upgrading to ICS but rooted with temp CWM & superSU. All seem to be working ok. One fine day I did a factory reset, booting failed, Stock ROM with PC ODIN stuck at FACTORYFS. Then comes XDA with a solution to use a patched PIT file.
Vola, my phone was up and running with ICS but missing 3GB space. It wouldn't have bothered me had the phone been stable. It used to freeze 2-3 times a day especially while downloading from Google play. Digging further in XDA forums for a fix cleared about eMMC bug and and no way returning back to normal So I ran to SSC with a factory reset phone hoping they will replace mobo, as it failed to boot and stuck at Samsung logo. Told them that Kies update to ICS 4.0.4 caused the problem. But couple of hours later, I got my phone back but with 8.24GB space & ICS 4.0.4
Now, I needed a fool proof way of bricking but couldn't go for pulling out battery half way through stock flash ROM. Thought it would be tricky to explain what I was upgrading when I've already got the latest stock ROM just a day ago from SSC. hmmm... then I got hold of stock PIT file... flashed it. And now perfectly stuck at home screen. No recovery menu but only download mode.
Next visit to SSC within 24hours and a simple story line with a sad face.... "Installed many apps, caused force close. So I did a Factory reset. And the phone does not boot now". It was stuck on the very first screen.
Finally it is gone for mobo replacement and expected to be ready in 2 days - covered under warranty Now coming to my question part, "What are the quick essentials checks to be done before accepting my phone from SSC" I really wish that it is all fixed properly and I do not want to visit a service center again
Click to expand...
Click to collapse
Just check the service job sheet whether they replaced the mobo or not before taking the delivery ? As simple As that.
got my gnote back with new mobo
Well, it is almost like the 'law of attraction'... I didn't want any problem and when I got my gnote today... guess what ? phone vibration didn't work. I had to go back to the SSC.
Fortunately, they responded immediately and the SSC guy fixed it on the spot without another round of formal servicing process. As explained to me, an insulation sticker of the vibrator was not removed while slipping in the new mobo. I didn't care less to understand if that is true as I was excited to get my phone with 11GB internal storage .
All seem to be working fine as of now with stock ICS 4.0.4 :good:
Hi everybody
I'm really not lazy men, I check almost all posts here on the best forum in the world xda. I face this problem before 2 days, I unlock my phone with Galaxy_Ace_Unlock and root it, everything was worked perfect and suddenly it lose mobile signal. I check phone locking and it was locked again.
It wasn't main problem , then I read on this forum that this aplication is not safe and I uninstall it, after that I rebote my phone and got strange problem. I can't boot my phone I only get samsung boot screen 1 sec and it keeps restarting every sec. When I charge my phone via charger I don't see anything just screen is blanking.
More one thing, when I deleted app galaxy ace unlock I deleted from sd card root file that I use to root my phone.
I need help I try flashing it with odin 4.38 and no success, I can enter download mode, everything pass perfect and I got message PASS but phone can't boot, when it's finishing with odin on last step phone restart it self and keep blanking. This is very anoying problem, please help me if you can.
I use swisscom galaxy mini s5570 and I don't know how to solve this.
I try many different stock rooms but no success, always when I finish with odin it's successfull but I can't boot, I can't access recovery mode because phone is blinking all the time.
I know that this forum is most powerfull and tha we have the best experts, better than android developers that have, and I'm sure that you can help me in some way.
More once, I can enter download mode and flash with odin but I can' boot.
Sorry for my bad english I'm from Bosnia and my first language is Bosnian
Thanks, Reuf
If you can enter download mode, ODIN will most probably work. I think you have gone wrong while working with ODIN. Follow these instructions carefully and double check whether the correct files are selected for each category.
If you still have the problem try flashing a custom recovery and a custom ROM.
Or, the other most probable thing is some hardware error, the only thing to do then is to go to a Samsung center, and act dumb (like you do not know anything about rooting) and if you warranty is not void, they might get it right for you..
domsnelter said:
If you can enter download mode, ODIN will most probably work. I think you have gone wrong while working with ODIN. Follow these instructions carefully and double check whether the correct files are selected for each category.
If you still have the problem try flashing a custom recovery and a custom ROM.
Or, the other most probable thing is some hardware error, the only thing to do then is to go to a Samsung center, and act dumb (like you do not know anything about rooting) and if you warranty is not void, they might get it right for you..
Click to expand...
Click to collapse
I can't go to the Samsung center because I bought phone from my friend. It was a new phone I got it in the box but he bought it in Swiss. I will try some other ROM but really I try many of them.
I think my phone is lost
reufjaha said:
I can't go to the Samsung center because I bought phone from my friend. It was a new phone I got it in the box but he bought it in Swiss. I will try some other ROM but really I try many of them.
I think my phone is lost
Click to expand...
Click to collapse
But even in Swiss they have warranty agreements and receipts so if it is new you should have such purchasing receipts - otherwise your friend pulled you over the barrel.
Anyway, maybe you tried a ROM w/o boot-image to prevent from bootloops.
Maybe you should try the 2.3.5 version coming from samsung:
http://www.sammobile.com/firmware/?page=3&model=GT-S5570&pcode=AUT&os=1&type=1#firmware
Hello folks.
Had a go at rooting Samsung i9000. It's quite old, and clearly clogged up to the hilt with the apps very laggy and frequently crashing. I quite fancied getting rid of the bloatwear too and the bloody annoying splash screen at start up!
Needless to say, it's all gone belly up. I've tried a couple of things using the guides here, but I don't want to keep pushing my luck in case I completely brick the device.
I'm running an i9000 in the UK on the o2 (Well, giffgaff) network. It was running Gingerbread, 2.3.5 I think. As it stands, I can get into the download option, but nothing else. I had used Odin 3, but have since read that the highest level is 1.83, which I now have. This might have caused the initial problem, but it's "soft" bricked. I've tried to flash over a stock rom again, but I keep getting failure notices. I can't get past the "Can't open the serial (COM) port" error message on Odin. I've downloaded the drivers and they have successfully installed.
One thing I don't think I did beforehand was to enable USB debugging.
I also tried the guide on here which uses the pit method, and curiously enough, it went through without the COM port error. The only thing that did, however, was to remove the "Phone + PC" logo. I am still able to get into download though.
Help! I am due to get a new phone very shortly, but it would be very useful to get the phone working again in the meantime! Any help very much appreciated.
If Kies is running in background it will fail, Go into Kies, Tools -> Preferences, unselect "Run Samsung Kies automatically when a device is connected", save the change, close out of Kies, and then restart ODIN. Try flashing now.
Try uninstalling Kies and then reboot and install the Samsung Drivers. Try then.
PFFFFFFFFFFFFFFFFTTT, sent from my i9000
Hi XDA community,
I'm scared out of my mind. Tried rooting for the first time ever, but don't actually know what I'm doing. Using various guides I found in these forums, I:
1. Used HTCdev to unlock the bootloader
2. Used ADB to install TWRP 3.0.2-0
3. Used TWRP to install UPDATE-SuperSU-v2.76.zip
Once that finished, my phone tried booting up (the white HTC logo) but now it has the red development build text at the bottom.... and then it gets into an infinite boot loop.
I don't know how to fix my phone. Please someone here with guidance, please help.
I've got the same identical issue.
I was able to get out of the boot loop by holding volume up and power, and I got back to download mode. From there, since the SU update I tried to install boot looped me (I was following this tutorial), I jumped ahead and just installed cm13 as I was planning to.
This install went fine, but then I ran into the issue of the rom not recognizing my sim card. I've been researching this problem and I guess I need to update my baseband? I tried for hours but I do not know how to accomplish this, and couldn't figure it out for the life of me. This thread on the cyanongenmod forum seemed to be the closest thing to help I could find, but still it didn't help very much.
So at this point now I'm trying to back out and unroot my phone and get everything back to factory settings; it doesn't feel worth it anymore to me since I've just had trouble every step of the way. I've been trying to follow this post to get back to at least a usable factory rom. But I can't even get this one to install because I cannot access my phone through adb while it's in download mode. Furthermore the instructions are just confusing me because I'm not so versed in the nomenclature of these procedures.
Is there anyone that can help me get back to complete stock t-mobile sense? Or if not, help me get my cm13 rom to recognize my sim card so I can at least have my phone working in some capacity? I'd be tremendously grateful of either. I'm really in over my head here and quite scared I won't be able to figure this out.