Hello. I have been reading on these forums for a while now. I always go here to find out information about smartphones. I have had this captivate for quite some time now. Probably about 2 years. When I was first given the phone it wouldn't do anything but go into download mode and my friend just gave me the phone because he actually had 2 broken ones and i was able to make a completely working captivate from the pieces from the 2. but the other would go straight to download mode if i hit the power button. the guy gave me the one that was constantly in download mode for fixing his other phone. This phone also had an lcd problem untill i came across a captivate that someone had torn the power connectors off so i used the lcd from that phone and put it on the captivate that was constantly in download mode. i plugged it into the charger and it shows a loading screen alot like what an iphone shows when it is loading. and after long enough it would show a battery partially charged. at this point i can push the power button and it powered on and went into safe mode. so I factory reset it and it still has the same problem. i have even formated the internal storage and tried many different roms. the first i tried was serendipity VII it was a great gingerbread rom but it also had the problem. i later flashed cm9 and icyglitch kernel. icy glitch is amazing however ics is old now. in ics the download mode problem still exists. Now the real problem to all of this that makes me think it is a hardware problem is i have recently tried about every jellybean rom with the combination of demon and semaphore and semaphore unofficial kernel and they also have this problem. however there is another problem with any of the jellybean roms i try. they will all work perfectly. i just have to install them 2 times. first install installs semaphore kernel andsays it needs to repartition. i guess cause its coming from icy glitch kernel. then it restarts into the semaphore cwm and then i reinstall jellybean rom and reboot and the phone just laggs unbelievable unless plugged into the charger. i mean the booot animation will move like 1 frame every 10 seconds. i have tried changing the voltage and overclocking it once it starts up. everything works perfectly until the second i unlug the charger then it does the extreeeeem lagg. From my experiences with this phone i would have to say that it is the power management ic on the logicboard. My question is what do you guys think i should do. i am back on icyglitch kernel and the outdated slim ics. i would really like to get jelly bean working and i would also like to be able to boot my phone with out a charger and an electric outlet.
sorry for such a long post i just thought that some of this information could give someone on here an idea of what is wrong with my phone.
Thanks for any help you guys can give.
anarchybob6 said:
Hello. I have been reading on these forums for a while now. I always go here to find out information about smartphones. I have had this captivate for quite some time now. Probably about 2 years. When I was first given the phone it wouldn't do anything but go into download mode and my friend just gave me the phone because he actually had 2 broken ones and i was able to make a completely working captivate from the pieces from the 2. but the other would go straight to download mode if i hit the power button. the guy gave me the one that was constantly in download mode for fixing his other phone. This phone also had an lcd problem untill i came across a captivate that someone had torn the power connectors off so i used the lcd from that phone and put it on the captivate that was constantly in download mode. i plugged it into the charger and it shows a loading screen alot like what an iphone shows when it is loading. and after long enough it would show a battery partially charged. at this point i can push the power button and it powered on and went into safe mode. so I factory reset it and it still has the same problem. i have even formated the internal storage and tried many different roms. the first i tried was serendipity VII it was a great gingerbread rom but it also had the problem. i later flashed cm9 and icyglitch kernel. icy glitch is amazing however ics is old now. in ics the download mode problem still exists. Now the real problem to all of this that makes me think it is a hardware problem is i have recently tried about every jellybean rom with the combination of demon and semaphore and semaphore unofficial kernel and they also have this problem. however there is another problem with any of the jellybean roms i try. they will all work perfectly. i just have to install them 2 times. first install installs semaphore kernel andsays it needs to repartition. i guess cause its coming from icy glitch kernel. then it restarts into the semaphore cwm and then i reinstall jellybean rom and reboot and the phone just laggs unbelievable unless plugged into the charger. i mean the booot animation will move like 1 frame every 10 seconds. i have tried changing the voltage and overclocking it once it starts up. everything works perfectly until the second i unlug the charger then it does the extreeeeem lagg. From my experiences with this phone i would have to say that it is the power management ic on the logicboard. My question is what do you guys think i should do. i am back on icyglitch kernel and the outdated slim ics. i would really like to get jelly bean working and i would also like to be able to boot my phone with out a charger and an electric outlet.
sorry for such a long post i just thought that some of this information could give someone on here an idea of what is wrong with my phone.
Thanks for any help you guys can give.
Click to expand...
Click to collapse
2 things, probably needs a new mobo and/or battery (thinking mobo though) and your volume down is probably stuck or dirty, making your phone go in download mode all the time.
Did you try flashing Odin KK4 with bootloaders and start fresh from there?
BWolf56 said:
2 things, probably needs a new mobo and/or battery (thinking mobo though) and your volume down is probably stuck or dirty, making your phone go in download mode all the time.
Did you try flashing Odin KK4 with bootloaders and start fresh from there?
Click to expand...
Click to collapse
What is odin kk4?if its the korn kernel i have tried it and semaphore kernel and they both installed but semaphore had the extreme lagg problem and korn kernel worked but the power issue was still there i installed the cwm .zip version tho would this make a difference? I have used odin one click to restore it to factory defaults. I think that should have ruled out any firmware issues, but im not sure. maybe i need to do the master clear thing that it shows on odin. It does seem like it could be a bootloader issue becuase the phone was originally on some half working rom when i got it and i know the guy i got it from said he was always flashing new roms on it. when i got it it already had this problem. then i flashed all kinds of roms and kernels trying to c if it was a firmware issue. I dont think the volume button is stuck because I use my phone daily even with this very annoying defect. It never turns the volume down on its own. the power button does stick sometimes but thats not too often. i have actually tried another battery in the phone too with the same results.
Do you think that having the wrong bootloader would cause something like this? I know from experiences installing linux and hackintosh that the bootloader is crucial to how the system runs. I did the one click restore and i would think that would also restore the original eclair bootloader but it still had the issue. then from there i flashed a GB rom then an ICS rom and a JB rom. I think these would each have their own different bootloaders and maybe they are conflicting. i always clear cache and dalvic cache before installing a new rom.
Is there anymore software i could try troubleshooting on my phone or is this seeming like a hardware problem?
anarchybob6 said:
What is odin kk4?if its the korn kernel i have tried it and semaphore kernel and they both installed but semaphore had the extreme lagg problem and korn kernel worked but the power issue was still there i installed the cwm .zip version tho would this make a difference? I have used odin one click to restore it to factory defaults. I think that should have ruled out any firmware issues, but im not sure. maybe i need to do the master clear thing that it shows on odin. It does seem like it could be a bootloader issue becuase the phone was originally on some half working rom when i got it and i know the guy i got it from said he was always flashing new roms on it. when i got it it already had this problem. then i flashed all kinds of roms and kernels trying to c if it was a firmware issue. I dont think the volume button is stuck because I use my phone daily even with this very annoying defect. It never turns the volume down on its own. the power button does stick sometimes but thats not too often. i have actually tried another battery in the phone too with the same results.
Do you think that having the wrong bootloader would cause something like this? I know from experiences installing linux and hackintosh that the bootloader is crucial to how the system runs. I did the one click restore and i would think that would also restore the original eclair bootloader but it still had the issue. then from there i flashed a GB rom then an ICS rom and a JB rom. I think these would each have their own different bootloaders and maybe they are conflicting. i always clear cache and dalvic cache before installing a new rom.
Is there anymore software i could try troubleshooting on my phone or is this seeming like a hardware problem?
Click to expand...
Click to collapse
Start by flashing Odin KK4 from this post: http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3 - That will clean your phone of w/e was on it before.
From there, you can flash Corn Kernel to get back to a JB ROM. Although, know that if you had the wrong bootloaders, your phone wouldn't boot and it would show color stripes.
Also, before flashing a ROM, you should wipe system and factory reset to make sure everything is clean (Backup your stuff first).
BWolf56 said:
...your volume down is probably stuck or dirty, making your phone go in download mode all the time...
Click to expand...
Click to collapse
I had a similar problem with my Sprint Galaxy S2 D710 (Epic 4G Touch) - my phone would randomly reboot every few days, and it kept getting more frequent. I thought it was the ROM, the overclock, etc. I flashed back to a stock ROM, and stock clock speeds. Eventually, I noticed that even brushing the power button would wake the screen, and about 10 seconds later the phone would reboot. I cleaned the button with some 95% isopropyl (rubbing) alcohol, and it worked better for a few weeks. It started acting up again, so I bought and installed a replacement power button.
Long story short, I got a new power switch, soldered it in place, and have had zero problems since!
The i897 Captivate uses the same switches for power and volume up/down. These switches are notorious for failing, so that's probably the issue with your phone. Try cleaning them, or you can buy a new switch for about ten bucks on ebay.
YouTube has numerous "teardown" or "disassemble" videos and several eBay sellers offer the switch you'll need.
(They don't include the skills needed to replace it. It's a tiny switch - about 4mm long, and you'll need a good soldering iron and a steady hand. Do you have a friend who's pretty good at soldering stuff?)
Related
Hi,
I have lost the ability to use my internal and external storage memory. Is there anyone that can tell me how to fix this. I am at a loss.
Thanks
Zack Cadieux
I have the same problem after flashing JPH firmware. (I know how to flash FW, I've been flashing every FW as it was released)
It says that there is an I/O error in mmcblk0p1.
I think i'm screwed as well.
Not one person knows what is going on
Hi,
Im supprised that even the dev's know nothing about this issue. I have read almost every thread and nothing to show how to respolve this issue. Is there anyone???
I had the same problem. I have a Bell Vibrant which I flashed to JPH using the Kies method, rooted, then One Click Lag Fix. Things worked for about a day then I lost my storage. Luckily I did the samsung 3 button fix first.
I downloaded the Tmobile Stock Rom, and used the following instructions to flash.
http://forum.xda-developers.com/showthread.php?t=734475
It booted up to the Tmobile Rom, and everything worked. I then used Odin to flash back to JPH.. rooted.. and now am contemplating the Lag Fix.
Not sure if it was related to the problem but I had my phone connected to my computer transferring files before all hell broke loose. I may have yanked the USB without unmounting... Just a thought.
Good Luck..
Dawgplg said:
I had the same problem. I have a Bell Vibrant which I flashed to JPH using the Kies method, rooted, then One Click Lag Fix. Things worked for about a day then I lost my storage. Luckily I did the samsung 3 button fix first.
I downloaded the Tmobile Stock Rom, and used the following instructions to flash.
It booted up to the Tmobile Rom, and everything worked. I then used Odin to flash back to JPH.. rooted.. and now am contemplating the Lag Fix.
Not sure if it was related to the problem but I had my phone connected to my computer transferring files before all hell broke loose. I may have yanked the USB without unmounting... Just a thought.
Good Luck..
Click to expand...
Click to collapse
My situation is about the same. I did the update and applied the root and lag fix. Phone worked fine for a day or so and then it just locked up and couldn't detect the sd cards anymore. I rebooted and it was stuck on the S for over 30 minutes...I flashed HJ2 and when it rebooted all that happens is I get a gray blinking battery if it's attached via USB and if on battery it boots up to the I9000 initial screen and shuts down. Lucky for me the shop will do a swap when they restock in about a week. Back to the HTC for now.
LordSoth said:
My situation is about the same. I did the update and applied the root and lag fix. Phone worked fine for a day or so and then it just locked up and couldn't detect the sd cards anymore. I rebooted and it was stuck on the S for over 30 minutes...I flashed HJ2 and when it rebooted all that happens is I get a gray blinking battery if it's attached via USB and if on battery it boots up to the I9000 initial screen and shuts down. Lucky for me the shop will do a swap when they restock in about a week. Back to the HTC for now.
Click to expand...
Click to collapse
Dont recall if I did any of the Recovery options, but I remember the big Grey Battery... You could even try flashing back to JPH through Odin... It may wake it up. But good to hear they will replace it, at least you have something to fall back on.
Dawgplg said:
Dont recall if I did any of the Recovery options, but I remember the big Grey Battery... You could even try flashing back to JPH through Odin... It may wake it up. But good to hear they will replace it, at least you have something to fall back on.
Click to expand...
Click to collapse
There was another thread I read about this exact same issue happening and the guys had to return the phones in the end. Yea I was lucky I was under the 30 days limit. By the time I get a new one hopefully a proper Froyo build will be out.
Has anyone tried using the i9000 Froyo rom (like this) with the new Froyo kernel? Could I try it, using the following procedure? I would like to try it, but don't want to brick my phone.
1) Remove SIM and MicroSD
2) Open Odin, load the i9000 Froyo PDA file and the i9000 Froyo CSC file.
3) Leave auto reboot checked and repartition unchecked.
4) Boot the phone into download mode.
5) Flash.
6) After reboot, get back into download mode.
7) Reopen Odin and load the stock Captivate kernel (From this thread) in the PDA box and a pit file (which one???).
8) Ensure auto reboot is checked and repartition is not checked.
9) Flash.
Would this work? Also, what if any PIT file would I use?
Thanks in advance
I'm trying this now. First attempt from the Cappy leaked Froyo failed. I just flashed back to JF6. Gonna try above with the I9000 pit and see what happens.
If it was that easy we wouldn't have needed xcaliburs reorient kernel Unless Samsung made some major changes under the hood your probably stuck with one ROM+kernel or the other for right now.
TMC_Sherpa said:
If it was that easy we wouldn't have needed xcaliburs reorient kernel Unless Samsung made some major changes under the hood your probably stuck with one ROM+kernel or the other for right now.
Click to expand...
Click to collapse
but i dont think the reorient kernel was NEEDED. i ran the i9000 with stock captivate kernel (as instructed in that post) for a week or 2 and didnt have any problems whatsoever.....BT and HSUPA didnt work, but small price to pay
now that we have a kernel from 2.2 build, we should be able to apply 2.2 captivate kernel with JPK and run it...
i think i will give it a shot today
I just tried it using the steps I outlined above. I would *not* reccomend doing it; it didn't work for me. Once I flashed the kernel, the phone would get stuck at the AT&T "World Phone" screen (formerly the i9000 splash, but I guess the kernel changes that). Being stuck at this screen, it would intermittently vibrate 1-buzz, 2-buzzes, and repeat about every second. I assume that's some sort of error message? After trying to reboot it a few times, I eventually got the "phone-!-computer" screen, and was only able to successfully reflash it by removing the battery, holding volume down, and plugging in USB, and was able to get into download mode to flash with Odin. Heads up.
Didn't work for me either....and, the usual method to get in to download mode (off and plugged in to PC with battery charge icon showing, holding down vol up/down and then power and the release power at black screen) did not work. Had to power off, remove battery & SIM, then hold down vol up/down and plug USB in and then release vol up/down.
boomerod said:
Didn't work for me either....and, the usual method to get in to download mode (off and plugged in to PC with battery charge icon showing, holding down vol up/down and then power and the release power at black screen) did not work. Had to power off, remove battery & SIM, then hold down vol up/down and plug USB in and then release vol up/down.
Click to expand...
Click to collapse
Basically, same here. I guess we'll have to wait for someone to figure this out.
well damn....thats lame. how come the i9000+cap kernel worked great in 2.1?
Pirateghost said:
well damn....thats lame. how come the i9000+cap kernel worked great in 2.1?
Click to expand...
Click to collapse
2.2 and 2.1 are different software so its easily possible that Samsung changed whatever allowed it to work.
Sent from my SAMSUNG-SGH-I897
the 2.2 leak is basically an i9000 rom, its not fully tweaked to ATT wants yet... thankfully
yeah I can't understand why on earth you would want to run an i9000 firmware which is at least just as buggy but not designed for your device at all... JPK (latest i9000) was built the same day as JI6...
Speaking for myself, I just want Bluetooth voice controls, which work on the I9000 Froyo but not on this leaked Cappy Froyo. I confirmed that again today by flashing to I9000 (most recent release on Samfirmware) - BT voice commands worked perfectly.
boomerod said:
Speaking for myself, I just want Bluetooth voice controls, which work on the I9000 Froyo but not on this leaked Cappy Froyo. I confirmed that again today by flashing to I9000 (most recent release on Samfirmware) - BT voice commands worked perfectly.
Click to expand...
Click to collapse
I was running i9000 ROM as well with captivate Froyo kernel (in which I noticed a slight increase in performance) but there was no voice while calling only a hiss. I installed the modem.bin from Captivate froyo and it worked.. for 10 sec and then I got reboot loop and decided to go to stock froyo. Wondering if there is a possibility to make it work with a modem from 2.1, but I believe is highly improbable.
Now I am back at the AT&T build but I must say that there are few things which I really don't like. Like the lag when changing home screens. If I go to 7 and press home button it takes 1-2 seconds to get back to the main one.
I indeed found it much faster in opening gallery and loading the thumbnails plus very good results in Linpack. Quadrant still doesn't give me more than 985 which is half of 2.1 with lag fix but that's not relevant.
I want to run i9000 rom because I am from Europe and I would like to have Swype in Romanian for example + that the i9000 rom doesnt mind if I have the "Use wireless networks" On or Off, GPS will still connect in less than 10 sec, thing impossible to achieve with ATT ROM (from my experience).
the reason why i want i9000 froyo with 2.2 capt kernel is because i really like 'euro stock' rather than 'US stock,' which is edited after the carriers mess with it. i know u can erase those and stuff, but i prefer using a clean rom, and adding my own configurations with an update.zip.
han.azuki said:
the reason why i want i9000 froyo with 2.2 capt kernel is because i really like 'euro stock' rather than 'US stock,' which is edited after the carriers mess with it. i know u can erase those and stuff, but i prefer using a clean rom, and adding my own configurations with an update.zip.
Click to expand...
Click to collapse
same here....i hope someone takes on this task soon...i would love i9000 froyo on my captivate
Pirateghost said:
same here....i hope someone takes on this task soon...i would love i9000 froyo on my captivate
Click to expand...
Click to collapse
+2 I love the i9000 rom and I'm not sure I'll update to 2.2 until we get one. I had Froyo on my N1 so I've used it before but after getting rid of the stock rom I don't want to go back. I don't want to update just to update.
Quite an adventure
OK, so even though this is embarrassing at some level, I'm still going to share this experience with the forum (just in case someone else does this to themselves).
So, as the OP posted (had been thinking about it since 3AM this morning after I found that this leaked Cappy Froyo does not have BT voice commands implemented) I decided to try out the I9000 Froyo (most recent posted on samfirmware.com) and then try flashing the Cappy Froyo kernal to see if I could get a working combo. Well, I never got as far as the OP in that I was never able to successfully flash the Cappy kernal.
I ended up stuck (for most of the day) with a very unstable combo: I9000 Froyo with Cappy JF6 baseband. Originally, the problem was I could not get in to download mode using all the normal, well-know methods. I was then able to - see my earlier post - but was unable to get past File Analysis in Odin. I then tried rebooting and then was not able to get back in to download mode to save my life, not even using the method that originally worked for me. So, here is the lesson I learned (other than not screwing around too much with my phone):
It seems that I needed a download mode method for the I9000. I got to battery charge screen with phone connected to PC, then held down ONLY the volume down button and the power butting and presto, download mode.
I still had issues getting past File Analysis; what ultimately worked was JF6 on-click solution. So, after all day screwing around with this, including trying to get into download mode through adb (to no avail), I've learned my lesson. I'm back to where I've been for the past month: really thinking about abandoning AT&T and this crappy, broken GPS, slow to get Froyo Cappy (which otherwise I like very much) and switching to Sprint and the Evo. Sigh...I'm under contract and don't want to pay a cancellation fee, damn!!
Here's a snipped from logcat while the phone is stuck at the AT&T logo. If anyone knows what to do about this...
http://pastebin.ubuntu.com/504711/
boomerod said:
It seems that I needed a download mode method for the I9000. I got to battery charge screen with phone connected to PC, then held down ONLY the volume down button and the power butting and presto, download mode.
Click to expand...
Click to collapse
I had to do the same, except that when I did it, I was getting the Phone-!-Computer screen.
damis648 said:
I had to do the same, except that when I did it, I was getting the Phone-!-Computer screen.
Click to expand...
Click to collapse
Did you ever get back to stock? I think we had a good thought...
I guess I have to admit that I like to tinker. What I need to do is get another phone that I leave alone so I don't loose my communication to the world.
-Edit-
Back at the leaked Cappy Froyo...guess I'll just live with this until we finally get a fully functional Froyo.
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
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
I'm using mi3 with Euphoria-OS 0509 version. My phone will suddenly shutdown itself even the battery is full.
I tried re-flash this ROM, but no help.
It happens every time when I use the phone in no time. But It won't happen when charging.
Maybe there's a problem on your phone's battery. Try to bring it on a service center.
error01671 said:
I'm using mi3 with Euphoria-OS 0509 version. My phone will suddenly shutdown itself even the battery is full.
I tried re-flash this ROM, but no help.
It happens every time when I use the phone in no time. But It won't happen when charging.
Click to expand...
Click to collapse
What do you mean by "suddenly shutdown itself"?
Do you see 1) the closing down routine? Or 2) does the phone simply not respond to pressing the power button?
If it's 2), plenty of ROMs exhibit the "screen OFF death", where the phone is actually still active but you can't get the screen to light up. try flashing another ROM. Paranoid Android is the most stable ROM for me.
If it's 1), still try flashing another ROM, and it it is still closing down, it's a hardware issue (hopefully battery), so service centre time.
paul c said:
What do you mean by "suddenly shutdown itself"?
Do you see 1) the closing down routine? Or 2) does the phone simply not respond to pressing the power button?
If it's 2), plenty of ROMs exhibit the "screen OFF death", where the phone is actually still active but you can't get the screen to light up. try flashing another ROM. Paranoid Android is the most stable ROM for me.
If it's 1), still try flashing another ROM, and it it is still closing down, it's a hardware issue (hopefully battery), so service centre time.
Click to expand...
Click to collapse
In my case, my phone's screen will suddenly frozen while I'm using, and turn off itself. I need to hard reboot the phone. I used flashed this rom few months ago and change to PAC rom, no such problem until I flash this rom again, all roms were clean flash and the battery was calibrated. So I think it might be the hardware problem.
error01671 said:
In my case, my phone's screen will suddenly frozen while I'm using, and turn off itself. I need to hard reboot the phone. I used flashed this rom few months ago and change to PAC rom, no such problem until I flash this rom again, all roms were clean flash and the battery was calibrated. So I think it might be the hardware problem.
Click to expand...
Click to collapse
Well, if the phone was OK with a different ROM, that implies your current ROM is the problem - try another one.
I recall having had the same behaviour in the past, when I was trying a lot of ROMs in quick succession - so I don't know which one(s) it was.
All the same, it doesn't sound like hardware/battery. Make a Nandroid backup in recovery, then flash eg PAC ROM or Paranoid Android - wait a day before adding all your apps etc - and see if you get that issue again.
paul c said:
Well, if the phone was OK with a different ROM, that implies your current ROM is the problem - try another one.
I recall having had the same behaviour in the past, when I was trying a lot of ROMs in quick succession - so I don't know which one(s) it was.
All the same, it doesn't sound like hardware/battery. Make a Nandroid backup in recovery, then flash eg PAC ROM or Paranoid Android - wait a day before adding all your apps etc - and see if you get that issue again.
Click to expand...
Click to collapse
OK, I got some conclusions, and it might be a hardware problem.
First, I replaced the battery with same ROM, it still got SOD.
Then I flash Omni, PAC, Euphoria-OS, all got SOD like before.
So I return to MIUI, no SOD, but I got random reboots and sometimes Wi-Fi will disconnect itself even in its range.
Now I'm using Ivan's AOSP, still got random reboots and Wi-Fi problem.
And now I need this phone to work because I don't have a backup, waiting for new Nexus!!