Database Develop

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] Galaxy S stuck in boot-loop

Hi guys,
Gone through about 100 threads these last couple of days, but nothing helps, so have to start a new one.
What happened was that the other day my phone started ringing.
The screen however was black, so I could neither see who was calling nor answer the call.
I let it ring out, then I held the power button so it would shutdown.
Tried to restart it, and that's when the fun started.
The phone got stuck in a boot-loop, only showing the Galaxy S logo (not getting to the animated one).
Left it in this loop for several hours, since I've had problems recently with the phone needing to do this cycle 5-10 times before booting up.
This time it wouldn't boot, however.
I've tried putting the phone in a bag of rice for 18 hours, in case of any moisture inside, not helping.
Then I tried recovery-mode, formatting the whole thing, but I got the following error:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
Found this thread to try to fix the format error.
Got into download mode, but Odin does not recognize the phone, and I started believing all hope for fixing it without sending it in was gone.
I've also tried applying a couple of update.zip's from the SD-card, just to have tried it, but every package got Signature verifcation-error.
Anyway, when I headed to bed last night I left the phone in the boot-loop, and to my surprice, 8 hours later it had booted into first-time configuration.
YES!!!
Configured the phone with language etc., then all of a sudden the animated Galaxy S logo appeared...
And it appeared again, and again, and again for about 15 min., until I unplugged the battery.
And now I'm back at square one, stuck in the boot-loop (not getting to the animated logo)...
I have the latest versjon of KIES, not that it probably matters.
Does anyone have an idea of what the problem might be?

What rom were you using? stock or custom? Maybe it has something to do with lagfix if it was activated... im guesing, im not dev just normal user... Maybe try to reinstal usb drivers.

Just use odin 1.3 reflash official rom , everything would be OK.

Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.

mortenlm said:
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
Click to expand...
Click to collapse
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.

porkapple said:
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
Click to expand...
Click to collapse
Well, I would have if I knew... But stupid me thought that a phone was a phone.
How wrong was I?
Anyway, a little update here (the problem is kind of solved now):
Flashed the phone with 2.3.3 Gingerbread I found on dkszone, after running the steps in the previous mentioned thread.
And the phone started like a charm.
But after a few hours of configuring etc, I managed to insert the SD-card again, and all hell broke loose again...
Come to think about it, thats what I did yesterday too, so I've come to the conclusion that the SD-card is the main problem...
However, now the phone is slow... REAL slow... Kind of like my 1.5 year old HTC Touch Diamond 2 with WP6.5...
It takes up to 2 seconds to open menu items, keyboard etc.
Is there any way to fix that?
Or should I flash it with another ROM?

You mean the external sdcard? Maybe try to format it...

OK, so this is what I've now figured out:
The phone is damaged...
It seems that the internal SD has gone AWAL, and internal storage has somehow created itself on the external SD-card, thus the phone crashed when I switched cards...
When trying to format the USB-storage, I receive error: SD-card has been removed
So I guess I have to ship the phone off to Samsung ASAP...

Samsung Galaxy S I9000 - ICS 4.0.3 - Stopped Booting

Hi,
I installed a Cyanogenmod ICS 4.0.3. build 17 firmware on my Samsung Galaxy S I9000 almost 5 months ago from a tutorial. The update itself has been a fantastic experience from the start and I'm not sure if my current problem is even related to that firmware update. Apparently new users like me can't post URLs so I can't provide it now. If you need it let me know.
I have to admit that lately the phone has been rebooting every couple of days, or Android's been freezing and I had to remove the battery, but I didn't think too much of it. It wasn't too bad of a problem really, but this morning all of a sudden the device has become totally unusable. Help! :-/
The issue that's started since today is that my phone won't boot anymore. It seems to reboot somewhere during the boot process. There's only two screens that will be shown, before it reboots. When I remove the battery, put it back in and attach the charger, I will only see two charging screens. While charging, the device will also*reboot after a while.*
I can get into download-mode (volume-down + ok-button + power-key) but can't get into recovery mode (volume-up + ok-button + power-key).
Any ideas would be appreciated, thanks!
Greetings,
Adriaan
ps -> I have pictures of the booting screens and the charging screens but wasn't allowed to post them here. Again, if you need to see them please PM.

Hi,
I think you have to reflash using odin. You can be happy to reach download mode

I'll try that, thanks.
switch_42 said:
Hi,
I think you have to reflash using odin. You can be happy to reach download mode
Click to expand...
Click to collapse

just to be sure...
Just to be sure, could you please check that my logic is correct?
First off: the tutorial I had followed had me follow a few procedures:
first I updated Galaxy S with XXJVU Firmware
then rooted Galaxy S on XXJVU Firmware
after that I flashed CM 9, ICS 4.0.3. build 17 to the device
To which of these steps were you referring? My guess would be to take the last one, but perhaps it's wiser to restart the tutorial from the beginning. I'd appreciate any additional support you can give me, you can understand that I don't want to brick my device due to my misunderstandings..

Seems like a high overclock or high underclock
Sent from my GT-I9000

Helloworld294 said:
Seems like a high overclock or high underclock
Click to expand...
Click to collapse
Not sure what you mean there. In any event I've never taken any steps to overclock or underclock my device. Maybe it's going senile and I get to buy a galaxy s III soon

*phew* well my problem's been solved. Since I was able to get into download mode I flashed a baseline rom with Odin and found my way back to ICS. One surprise along the way was that from the same tutorial I had followed (and had happy results from) a few months ago, the step of using Odin to root the device wasn't working, it kept getting stuck at 'zImage' during the process! What's more, after that I was getting the BSOD image (the phone, exclamation mark and computer), which I found could be helped by using a 'One-Click Unbrick for Samsung devices'.
That was a XXJVU firmware. After some snooping around I found a different firmware than the one I had previously used and had switched from a XXJVU firmware to a XXJW4 firmware through a page on XDA-Developers. Did that. It worked. And now I'm back to ICS again, yay!
Thanks for the help along the way!

My eMMC bug story

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:

[Q] Bizarre screen issues after flashing

Hello guys,
I have around 2-year old Note GT-N7000 which I tried flashing a week ago. I did a few steps (don't remember any though) and something went wrong. Everything with the phone was working fine except the keyboard was typing 'null' and the screen had a weird problem. The phone will boot normally and the screen would be fine until it turns off (auto off or manually by button). Now if I try to switch on the screen it would start as if it's warming up. A sky with tiny stars kind of scene would appear and the brightness will keep increasing. The phone is functioning at this point and so is screen but nothing can be seen. I know this because I can receive a phone in this state by guessing the swipe location and swiping. Once in this mode, I have no option but to restart the phone. And then again everything works fine as long as I do not let the screen go off.
I got panicked and after a full research of 5 days on XDA, I decided to flash another ROM, probably a JB. I rooted my phone, install CWMR, bought mobile odin pro only to mess the things further. I downloaded the Ultimate Alliance ROM v3 and tried flashing it using the mobile odin. I guess I didn't follow the instructions properly and the phone went into bootloop. I then flashed GB KJ1 using ODIN which landed me at N7000 screen freeze and not able to enter recovery mode. Then I flashed AbyssKernel which helped me boot properly. Once I was in I realized I'm still on GB so probably JB never got installed.
Now the current problems are:
1. The keyboard is still typing nulls
2. The screen is still going into comma
3. There is a yellow triangle at the GT-N7000 screen.
My phone version is:
Baseband version: N7000XXLSO (it was N7000DDLR1 two hours ago)
Kernel: 2.6.35.7-N7000XXKJ1-CL627135
Build No: GINGERBREAD.XXKJ1
Sorry all this is noob stuff and maybe there is a solution in the forum already but after 5 nights of research and lots of messing around, I am not sure what do I do next. I certainly don't want to hard brick the phone.
Desperately need your help to come out of this mess. Even I'm happy to have the oldest stock ROM.
Thanks in anticipation and sorry for the long post.

trunoob said:
Hello guys,
I have around 2-year old Note GT-N7000 which I tried flashing a week ago. I did a few steps (don't remember any though) and something went wrong. Everything with the phone was working fine except the keyboard was typing 'null' and the screen had a weird problem. The phone will boot normally and the screen would be fine until it turns off (auto off or manually by button). Now if I try to switch on the screen it would start as if it's warming up. A sky with tiny stars kind of scene would appear and the brightness will keep increasing. The phone is functioning at this point and so is screen but nothing can be seen. I know this because I can receive a phone in this state by guessing the swipe location and swiping. Once in this mode, I have no option but to restart the phone. And then again everything works fine as long as I do not let the screen go off.
I got panicked and after a full research of 5 days on XDA, I decided to flash another ROM, probably a JB. I rooted my phone, install CWMR, bought mobile odin pro only to mess the things further. I downloaded the Ultimate Alliance ROM v3 and tried flashing it using the mobile odin. I guess I didn't follow the instructions properly and the phone went into bootloop. I then flashed GB KJ1 using ODIN which landed me at N7000 screen freeze and not able to enter recovery mode. Then I flashed AbyssKernel which helped me boot properly. Once I was in I realized I'm still on GB so probably JB never got installed.
Now the current problems are:
1. The keyboard is still typing nulls
2. The screen is still going into comma
3. There is a yellow triangle at the GT-N7000 screen.
My phone version is:
Baseband version: N7000XXLSO (it was N7000DDLR1 two hours ago)
Kernel: 2.6.35.7-N7000XXKJ1-CL627135
Build No: GINGERBREAD.XXKJ1
Sorry all this is noob stuff and maybe there is a solution in the forum already but after 5 nights of research and lots of messing around, I am not sure what do I do next. I certainly don't want to hard brick the phone.
Desperately need your help to come out of this mess. Even I'm happy to have the oldest stock ROM.
Thanks in anticipation and sorry for the long post.
Click to expand...
Click to collapse
Jesus Christ, way to get yourself into a mess... The null keyboard just means you have to reflash the csc correctly. Extract the gb rom file and it should reveal a csc file, input that into the csc part of mobile odin and flash.
Screen problems... How old is your battery?
Triangle issue, just download triangleaway app from play store and run.
Hopefully you've learnt something about following directions to a t. Don't think you've done any lasting damage though, you're lucky.
Sent from my GT-N7000 using xda premium

Thanks a lot for the quick help.
The battery is as old as the phone i.e. about 2 years.
I had flashed the same phone around an year ago and I faced similar screen issue when I tried flashing ICS last year and then I reflashed GB (the current ROM I guess) and the problem disappeared. Do you think it could be because of wrong flashing as well?
Is there is safe route to a relatively safe flashing which could reassure whether I should buy a new battery or not? Or shall I go ahead and invest in the battery regardless?
Thanks once again.

trunoob said:
Thanks a lot for the quick help.
The battery is as old as the phone i.e. about 2 years.
I had flashed the same phone around an year ago and I faced similar screen issue when I tried flashing ICS last year and then I reflashed GB (the current ROM I guess) and the problem disappeared. Do you think it could be because of wrong flashing as well?
Is there is safe route to a relatively safe flashing which could reassure whether I should buy a new battery or not? Or shall I go ahead and invest in the battery regardless?
Thanks once again.
Click to expand...
Click to collapse
Safest flash would be to flash latest gb rom for your region. I'd be amazed if the battery wasn't dead though, they usually only last just over a year. Symptoms of dead battery are screen flicker, sudden power loss and gain, physical swelling (put on flat surface and spin) colour change on screen, amongst other things.
Sent from my GT-N7000 using xda premium

SpyderTracks said:
Safest flash would be to flash latest gb rom for your region. I'd be amazed if the battery wasn't dead though, they usually only last just over a year. Symptoms of dead battery are screen flicker, sudden power loss and gain, physical swelling (put on flat surface and spin) colour change on screen, amongst other things.
Click to expand...
Click to collapse
Thanks a lot for the help. I could successfully flash GB 2.3.6 from Dr Ketan's thread and everything is working like charm. The screen issue that I mentioned is gone.
Thanks once again.

trunoob said:
Thanks a lot for the help. I could successfully flash GB 2.3.6 from Dr Ketan's thread and everything is working like charm. The screen issue that I mentioned is gone.
Thanks once again.
Click to expand...
Click to collapse
Good news, well done
Sent from my GT-N7000 using xda premium