Database Develop

[Q] Stuck on logo screen suddenly. Ideas?

Hi,
Last night my Galaxy S was low on battery, and I kept trying to turn it on for it to die right away (it was working as expected I guess)
This morning after I charged my phone it wouldn't turn on at all! It loads to the logo screen, makes that jingle sound and then holds and doesn't turn on.
I can get to recovery and download mode.
I put OCLF on like 2 months ago, but haven't modded/flashed ANYTHING since. It is very bizarre how it just died.
I'm wondering what my options are now. Obviously I would rather not loose all my personal files. Since I can get into download mode, can I just flash a new firmware? I'd like FroYo anyway, but I haven't got a clue what to do.
Great start to the year – !
Cheers,
Mitch
EDIT: I just decided to try the "Clear User Cache" option and then reboot to no avail. Now I can't get back into recovery mode!?!? Download mode still works. Huhh?? Is this expected? Have I lose Recovery Mode entirely now? Crap.

seeeems like an odin flash via the download mode is the only way. There are a few tutorials on this site and even tut vids on youtube so you should be fine if you just follow everything they do (as long as it works for them of course)

How do I know what version to flash? I have read a few tutorials and they all have started with "Dial x and check you have y" etc. Obviously I can't do any of that.
What is the *safest* firmware I can flash?
My phone currently has some optus variety.
Please forgive the noodish question.
Mitch

Where are you located? And who is your provider?

Hi,
I'm in Sydney Australia and my provider is Optus.
Thanks

Hi,
I still can't get my phone working and am not clear how to proceed.
What would be the best firmware to flash to my Optus Galaxy S that bricked out of the blue? Should I just send it back to Samsung?
Thank You

m1tch37 said:
Hi,
I still can't get my phone working and am not clear how to proceed.
What would be the best firmware to flash to my Optus Galaxy S that bricked out of the blue? Should I just send it back to Samsung?
Thank You
Click to expand...
Click to collapse
Hey mate go to samfirmware and get I9000DTJG4 thats the stock optus rom once you get phone up and running then upgrade to 2.2.1.

Sounds like you'll need to do a flash of a stock rom..
By the way, the old oclf had some issues that might lead to system corruption (unfortunately I'm not very sure exactly what it does, or whether it could lead to this problem). I'd suggest getting one of the newer lag fixes available here when you do get your phone running again

tragusman said:
Hey mate go to samfirmware and get I9000DTJG4 thats the stock optus rom once you get phone up and running then upgrade to 2.2.1.
Click to expand...
Click to collapse
tragusman has got it right. Depending on what the issue is, you'll either recover nicely or your phone is toast. Flash the above stock firmware and give it a shot. Note that you'll likely loose your data and settings.
If you're new to flashing firmwares, check the great reference guide on where to find Odin and how to use it (this is the app you'll use to flash the above firmware).
http://forum.xda-developers.com/showthread.php?t=723596
After flashing, try getting into recovery mode. If you can look for an error message under the standard menu. Can't get to d/l mode? You're probably in trouble. Get into recovery and see an error msg? Post the error here or google it for a solution. No error msg? You're probably ok - restart the phone.
Good luck.

Thanks guys.
I'm about to try it now, but before I start potentially breaking my phone even more, I was just thinking: Could I just send it back to Samsung? Would they fix it, or identify right away I have changed something and void my warranty.
Mitch

m1tch37 said:
Thanks guys.
I'm about to try it now, but before I start potentially breaking my phone even more, I was just thinking: Could I just send it back to Samsung? Would they fix it, or identify right away I have changed something and void my warranty.
Mitch
Click to expand...
Click to collapse
If it's broke, you can't break it any more I've sent phones back in for support after flashing back stock firmware (flashing it after it "died").

Keeps rebooting after Darky 8.1 update

Now just had a little problem. I updated to Darky's 8.1 no wipe version. It updated fine but the first time it booted, it froze. Now it keeps doing a boot cycle over and over again. I see the i9000m screen but I do not get to the S logo screen or in this case the transformer screen because it reboots. Can you help me plz? Thanks.

Zink6 said:
Now just had a little problem. I updated to Darky's 8.1 no wipe version. It updated fine but the first time it booted, it froze. Now it keeps doing a boot cycle over and over again. I see the i9000m screen but I do not get to the S logo screen or in this case the transformer screen because it reboots. Can you help me plz? Thanks.
Click to expand...
Click to collapse
try a re flash of another ROM preferably a stock ROM then start all over again, similar thing happened to me earlier, i am quite new to all this but i dont know if its the kernel or lagfix i had what caused this...
i re flashed back to froyo and then installed darkys ROM then re installed my kernel last.. all is good (for now)

worked for me first time but when i went to sgs tools to upgrade your apps ie gallery, camera, it said no busybox installed but went ahead and done fine in v8.0 and i see that cwm changed from red to green too went to market for busybox to download it but when it goes to install phone just reboots all the time mmmm...

Easiest way out of cycling boot:
pull battery
place it in
bring phone in download mode (not recovery!)
prepare Odin with a stock ROM
connect the phone to your PC and give it a kick thru Odin
When done feel free to switch again to Darkys (8.0) with wipe (you will loose data) and afterwards upgrade to 8.1.

stepsch said:
Easiest way out of cycling boot:
pull battery
place it in
bring phone in download mode (not recovery!)
prepare Odin with a stock ROM
connect the phone to your PC and give it a kick thru Odin
When done feel free to switch again to Darkys (8.0) with wipe (you will loose data) and afterwards upgrade to 8.1.
Click to expand...
Click to collapse
YES !!! i agree, it is a pain.. but we love our phones and we would do anything for them its always best to flash back to standard FW if you ever get a problem...

I myself experienced this. Whenever I installed a new software, it would just boot. I got fed up because darky's forums are also down and there is no discussion. flashed doc's rom. Now everything is fine.

...mh... but it's not caused by Darkys ROM. This cycling boot feature may appear at all ROM, at all lag fix actions and so on. It depends how proper you interact with phone- and ROM-features while configuring. A lil disturbance during your session (by you or battery issue or whatelse) or a not so well prepared basic from where you start and your unlimited-feature-wishlist-and-paint-it-golden-one-click-action is enough to interrupt the whole thing and run into trouble.
It was and is all the same - since DOS or C64. And it will be the same, even when iPhone is on level 12.x or Android will be able to beam you elsewhere thru the barcode scanner.
It's a game. Nothing more. And game means lot of fun - and in the beginning a certain thrill when your phone stuck first time and you are thinking: "... f*ck... bricked..."

yup same for me
cycle boot thing
didnt enable download mode before that....
can get into debug screen thou but wiping it doesnt help
anyone with a suggestion on what i can try? warrenty = off so im screwed otherwise

anyone with a suggestion on what i can try? warrenty = off so im screwed otherwise
Just tell the warranty guy darky screwed it .
OR
http://forum.xda-developers.com/showthread.php?t=853950
jje

cant even boot the phone mate
so ehm i dont get it....how can odin help me ?
is there any way of getting it into download mode still when it doesnt boot up? i heard about that JIG thing they made themself...isnt that just like the microusb cable that comes with it to the pc? i dont get it sorry if im trippin but im maddd at myself for even trying this lockscreen thing

http://forum.xda-developers.com/showthread.php?t=819551
jje

Thanks guys for all the replies. Now I did try flashing a stock rom but with no results. Was still having the same thing happening to me. If you guys can give me the link to the files you used to solve this problem, that would be great. Also just for your information I have a Bell i9000m unlocked running on fido. And NO its not an sd card failure lol.
As for DarelSteilz85, I did make one of those JIG usb for myself. It easy, just get the micro usb and strip it bare to the point you can see the pins on the usb which usually are connected to the wires and get a resister to connect one pin to another. Now for which pins, I remember it was 4 and 5 that you had to connect through the resistor but double check as I am not sure. Also the resistor has to be a certain level which I forgot so double check that also. Good luck.

http://forum.xda-developers.com/showthread.php?t=853950
What i use for problems .
jje

[Q] Bricked my phone and don't know how to fix

I really need some help with my Zio m6000 cricket junk. I bricked it and can't figure out for the life of me how to fix it.
I read post after post in this forum and did everything I can think of and nothing is working. I have all the programs I think I need to dump the rom on my pc. None of them will even read that the phone is connected to the pc.
I sent message after message and only a few have responded but none knew how to help me. I thank those who did try though. I know there has to be a way to unbrick a Zio phone by now. None of the posts in the forum explain this in full detail because they are ALL from a year or more ago, or just don't explain in todays times how to do it.
I'm so close to just taking my hammer and smashing the phone and take the total loss with it. I can't affored to buy another phone, and Cricket service eats a **** for helping me replace the phone.
CAN ANYONE PLEASE FOR THE LOVE OF GOD HELP ME INSTAL, RUN, PROGRAM WHAT NEEDS PROGRAMMED OR WHATEVER IT IS I NEED TO DO TO GET MY PHONE WORKING AGAIN????????
TC
(SOLVED)

I'm not the most experienced, so I am not entirely sure if this will work, but I know it fixed my bootloop issue. Have you tried doing a factory restore? To do so, hold the power button and the volume down button. A screen will pop up, simply navigate using your scroll ball and select the factory restore option. Note that this will erase all Apps and user data on the phone (mine stayed rooted and kept some of the settings I changed via file manager). Sorry if this doesn't help, I hope that you figure it out soon. I'm sure some people on here can help you more than I can.
Sent from my Sprint Zio using XDA App

Flash the openzio 2.1 rom, it is based on the stock 2.2 rom
Sent from my Zio using XDA Premium App

Mattix724 said:
Flash the openzio 2.1 rom, it is based on the stock 2.2 rom
Sent from my Zio using XDA Premium App
Click to expand...
Click to collapse
This ^^ or you can run the 2.2.1 update by downloading it HEREhttp://www.mediafire.com/?8749zbtls66k8qchttp://www.mediafire.com/?8749zbtls66k8qchttp://www.mediafire.com/?8749zbtls66k8qc once downloaded follow steps below. ***You may run into trouble on a Win7 Machine, so I would advise doing this on a vista or XP computer.****
1. connect your phone to your computer via USB
2. Place phone in Modem Download Mode By holding the Power(red) Call(green) and volume up and down buttons.
3. Run the updater let it run its course.
4. Let it reboot (or manually reboot) - it may take up to five minutes to boot.

Thank you guys for all your advice
Thank you all, sinisin got me on google talk today and helped me step by step to reflash my whole phone to the new rom and get it working again for me . I would NEVER have done it myself, if anything I would have made the phone worse trying. lol, I have to thank you all for your help but most of all the biggest thanks has to goto sinisin for being very patient with the whole process and getting my phone running again for me. THANK YOU SINISIN.
So far i'm killing the battery for the calibration part of the instructions and all seems very good so far.
I also want to say and give extreme credit to all involved with making the custom 2.1 rom and getting it working. THANK YOU GUYS. ITS AWSOME! to what I've seen of it so far. I haven't messed with it just yet but getting ready to reinstal most of my apps back to my phone and DELETE clockworkmod from its sd card so i hopefully never brick it again using that crap. I knew better and was such a dummy noob for trying to use it.
Thank you again guys as well as you sinisin,
TC

Stuck in Fastboot
Fate43 said:
This ^^ or you can run the 2.2.1 update by downloading it HEREhttp://www.mediafire.com/?8749zbtls66k8qchttp://www.mediafire.com/?8749zbtls66k8qchttp://www.mediafire.com/?8749zbtls66k8qc once downloaded follow steps below. ***You may run into trouble on a Win7 Machine, so I would advise doing this on a vista or XP computer.****
1. connect your phone to your computer via USB
2. Place phone in Modem Download Mode By holding the Power(red) Call(green) and volume up and down buttons.
3. Run the updater let it run its course.
4. Let it reboot (or manually reboot) - it may take up to five minutes to boot.
Click to expand...
Click to collapse
Hey ive tried this method but it keeps looking for the phone in debugging.
It only stays in Fastboot and thats the only thing that loads up.
Ive tried flashing the system.img's that i have found all say successful but it always boots back up into Fastboot.
Let me know if you have another method or any suggestions.
Thanks

If your M6000 Zio is a brick, run the leaked 2.2.1 from Zclusive. You will need to put the Zio into modem download mode then start the update.
Sent from my Zio using XDA Premium App

roketteere said:
Hey ive tried this method but it keeps looking for the phone in debugging.
It only stays in Fastboot and thats the only thing that loads up.
Ive tried flashing the system.img's that i have found all say successful but it always boots back up into Fastboot.
Let me know if you have another method or any suggestions.
Thanks
Click to expand...
Click to collapse
If it is going into fastboot your not pressing the correct buttons on boot up. You have to push the Red, Green and Both volume buttons simultaneously and the phone will boot into Modem Download mode.

Update Failed
Ok I have installed the Modem drivers from Kyoceras website and made sure its connected in download mode. It says download mode on it.
Then I downloaded and opened the 2.000CR.5 etc
When it looks for the phone it says Update Failed.
Never picks it up. And I am running Windows XP just incase you wanted to know.
Its SP3.
Any ideas on why its not working for me?
Thanks again everyone for helping

[Q] samsung ATIV S rebooting all the time!!

Ok.
first off, Hii!! this is my first ever time writing on XDA.
Any way, i know this is not a new issue.. but my ATIV S is rebooting every 5 seconds after the 8.1 update via preview for developers.....
i did a lot of digging before writing here and found this thread : http://forum.xda-developers.com/showthread.php?t=2718023
I followed the instructions and flashed the GT-I8750_DXBMJ1_R_signed ROM along side the GT-I8750_VJALL3_P csc (this is the only combination that gave me some results.
After flashing, my phone did manage to boot up finally but with a twist. Trying to restart the phone sends me back to the boot loop forcing me to reflash everything again.
i tried the tip from the thread to download the preview for developers app and try to update the phone again (claiming it will resolve the issue) but as soon as the phone goes to reboot before the update the boot loop comes back and we're back to squire one.... so i'm kinda stuck.... is there any kind of FIX i can try to help me sad situation? :crying::crying::crying::crying:

I've had a lot of issues with my Ativ S as well.
Your rebooting issue seems recognizable, maybe this thread will help : https://social.msdn.microsoft.com/F...ime-after-wp-81-update?forum=winphoneosissues
Anyway, I'm on the latest Developer Preview update, my Firmware version is : 2424.14.9.3
It seems the phone is much more stable now, however i'm only using this phone for development, there is no sim card present anymore.
Switched to a new Nokia for my main device.
Advice : If you want a decent Windows Phone, buy a Nokia, not a Samsung or HTC.

Thank you for the reply!
i did some more digging and found that flashing the GDR2 FW 2424 actually helps. after that the is a need to update the phone to the official GDR3 update in the phone updater in settings. i am trying that as we speak and really hope it will work
BTW this ATIV S is my backup phone and not my daily driver (i use a Galaxy s4) i just wanna fix it up to use as my work phone. my trust in windows phone is gone for now XD
EDIT: OK, so i followed the thread and applied the instructions...
at first, i flashed the GDR2 official ROM with the instructed csc file and everything booted up well. at this point they say that if the phone is to be restarted the boot loop will come back (it did when i tested it)
afterwards, i installed the preview for developers app and started updating to the official GDR3 update as instructed. it finished up and booted up well. the next step was to update to 8.1... i did and at first it worked well but as soon as i disconnected the USB cable, the loop returned again. (if i connect the USB cable back it's booting up normally)
BTW i tried doing it all from scratch and noticed that in every step of the process, if i disconnect the cable the loop come's back and disappears as soon as i plug it back in... anyone has any idea what to do next?

Microsoft Lumia 640 LTE lost imei after Windows 10 update.

Hello im a newbie on the lumia front, i used the Windows insider app to update to win 10 but after the install the fone was left in boot loop so i used the thread install 1024? In lumia to fix the mess. However acter the flash i got the "successful flash" message but when the fone rebooted i was left with no imei number & cant leave flight mode. I hope somebody out there knows of a way to fix this problem. Thanks in advance to anyone that can help. Dave.

mrdavetarthur said:
Hello im a newbie on the lumia front, i used the Windows insider app to update to win 10 but after the install the fone was left in boot loop so i used the thread install 1024? In lumia to fix the mess. However acter the flash i got the "successful flash" message but when the fone rebooted i was left with no imei number & cant leave flight mode. I hope somebody out there knows of a way to fix this problem. Thanks in advance to anyone that can help. Dave.
Click to expand...
Click to collapse
First try Hard Reset, if that wont help, the go back to stock 8.1 update 2 (with Windows Device Recovery Tool), then with slow ring update it to 10586.11. For now use only what Microsoft offers, dont experiment for now, because you'll have a problem again. There is a lot of bugs on no official builds.

Hello Opus Dei, ive followed your instructions to the letter but still cant leave flight mode. Do you have anymore ideas on how i can releave my problem? I dont know if this info will help you any - I'm using a Microsoft Lumia640 LTE, i was on stock rom then i installed the insiders app & updated my phone but i used the "fast" method. The first update was fine then a couple of days later i had another update note so i did that but when the update was finished & the fone went to reboot itself it just kept boot-looping, i left it doing this overnite but still no joy so i used the "install 105##" but when the fone rebooted it was stuck in flight mode & i cant get round it & i'd bought the fone for my sons birthday which is this week so im willing to try any of your instructions to solve the problem. Im hoping you or anybody else has a solution to get me out of this situation. Thanks to all the helpers - Dave.
Ive noticed that in the "extras & info" section it says "Mobile Operator 000-GB" which ive found to mean open network but my fone was bought locked to Vodafone & when i turn it on its branded with Vodafone. Could this be anything to do with my problem?