First off, I know I'm a new member, and I did watch the video, I've been searching the forum for days now trying to find someone with the exact some problem as me but I've come to the conclusion I must be special as I haven't seen this problem else where. Lucky me...
Let me start off with some information about the phone.
Carrier: Vodafone AU (says XSE on the recovery screen)
Baseband Version: I9020XXKI1
Bootloader Version: I9020XXKL1
HW Version: Rev 52
Model: Nexus S i9023
Lock State: Unlocked
Primary computer: iMac
Fairly certain I have USB debugging turned off :\
I rooted and unlocked the phone and was running the latest CyberGR mod ROM and the latest AirKernel kernel. The phone was running brilliantly, not a problem in the world, very smooth, very fast, excellent battery life, I loved it. Only thing I didn't like was how the keyboard became unresponsive at times. For that reason, I think I'll be switching to the Bugless Beast ROM and thalmus kernel when (if) I get this phone fixed.
So a few days ago, the power button on my Nexus S stuffed up and wouldn't work anymore. Completely unresponsive. I couldn't lock/unlock my phone using the power button. I had to either connect/disconnect it from the USB or turn it on/off by taking the battery out to be able to use it. Needless to say, this got very tedious very quickly and I decided to unroot it and send it back to Samsung.
I looked into how to unroot and came across the Odin app and decided that I'd use that to unroot. (noob error on my behalf, I realise now) Regardless of what I'd read, Odin doesn't work on a Nexus S apparently and although I didn't flash to stock, my phone became significantly less useable, half the time it wouldn't respond to anything I did on it. I tried to boot into CWM and although I was able to do so, it was useless as my power button wasn't working.
At this stage, I took out the battery, put it back in and the phone booted up again. I didn't press the power button, it just booted up straight away. I took it out again and held the volume up button on the side and this time, I didn't get put into the CWM menu, but the normal Android recovery menu. I went to press the volume up and down buttons but nothing worked. Power button is still unresponsive.
When I don't boot into recovery, it goes past the Google screen with the unlocked lock on the bottom of it, and goes to a screen where it says "Android" in a metallic style (I disable the boot animation logo in CyberGR mod so I was used to this screen) and it just hung on there, it never booted up past that screen.
Every time I tried to use fastboot -w to wipe the phone, or oem lock or anything, I would just get < waiting for device >
I plugged it into my Windows 7 laptop, tried the one_click_stock app and got the message that my phone has no boot.img. I then googled problems regarding the boot.img and no one really had any solutions that helped me out.
The SDK won't recognise my phone is there, but the sound pops up on Windows saying a device has been connected and disconnected but it never shows up.
Is it bricked or unfixable? Clearly warranty is void, not sure if I should just take it into Vodafone and ask for a new phone (as its still within warranty period, hence why I wanted to lock it and flash a stock ROM).
Very sorry for the lengthy post, I know I was meant to be brief but I thought the more information I could give, the better chance there would be for anyone to help me out. Thanks.
Make the root of your phone with any application in the market and install the recovery ClockworkMod touch with Rom manager premium or Rom toolbox Pro. Restart recovery using Rom manager or Rom toolbox and do a full cleaning on the phone. Wipe only data and cache.
Now, select from mount and storage mount USB storage and copy over to your i9020 storage any rom ( try using the cm9 ). If the installation is successful restart, if not try some other roms. More than that I do not know how to help.
P.s.: In theory it should go smoothly, otherwise I do not assume any liability for further damage to the phone ... Good luck!
Did you know you can operate cwm using the capacitive search button instead of the power button?
Alfaneo said:
Make the root of your phone with any application in the market and install the recovery ClockworkMod touch with Rom manager premium or Rom toolbox Pro. Restart recovery using Rom manager or Rom toolbox and do a full cleaning on the phone. Wipe only data and cache.
Now, select from mount and storage mount USB storage and copy over to your i9020 storage any rom ( try using the cm9 ). If the installation is successful restart, if not try some other roms. More than that I do not know how to help.
P.s.: In theory it should go smoothly, otherwise I do not assume any liability for further damage to the phone ... Good luck!
Click to expand...
Click to collapse
Thanks for the reply, I can't actually boot into the phone or get to any market place or any screen that could make the phone useable at all, it just sits on the CyberGR android screen for when you disable the boot animation.
bedalus said:
Did you know you can operate cwm using the capacitive search button instead of the power button?
Click to expand...
Click to collapse
I was pressing the search button (the volume buttons were working when I could boot into CWM) and the text just disappeared off the screen and just showed the logo. I can no longer boot into CWM.
I've installed Ubuntu and I'm going to try running the unrbickable java app that a user on here created, hopefully that may work.
Related
Yesterday i found out that my phone doesn't turn on even when the battery is full. I called HTC this morning and they asked me to ship it in. However , right after i hang up the phone, i put in the battery, my phone MAGICALLY BOOTED UP.
I found out it was the power button that was not working. I wanted to use this opportunity to wipe the system. ( My phone is rooted w/o unlocking the bootloader) I downloaded Passmig and placed it in SD. AND THEN, i did something very stupid. I clicked the " return phone to factory" button. (i know i should've done that in the recovery instead) but now my phone can't boot into the OS anymore. and also i can't get into the recovery to wipe or apply passmig because my volume button also DOESN"T WORK!!!!
Does any of you genius have any advices? Truly desperate for one.
p.s. i was on the cyanogen 6 ( Rod's mod) if that is at all important. I have the clock work recovery installed.
Tried flashing rom in fastboot using the sdk?
Sent from my FroyoEris using XDA App
I literally had the worst combination of events take place the other day:
So, I was running Firefly 3.0, and I planned on replacing it with a gingerbread ROM, (since my apps weren't saving data, for some reason), and I started to notice that my unlock button was starting to hang a bit. I thought this was just another side effect from Firefly 3.0 acting weird.
So, I boot to download, and flash the CM7 kernel with CWM 3.0 on it, and it passes.
The next step is to navigate around in CWM to install the ROM file before you can boot up. But, the power/lock button still doesn't work! So I'm stuck in CWM 3.0, unable to boot correctly. The touch buttons don't work like they do in CWM 2.x, so I'm... stuck.
So, I call Samsung, and I'm having a replacement sent to me within the week, since I can't even power on/off my phone (if it wasn't for CM7's auto-boot when you put the battery in)
So, already having adb installed on my Linux boot, I jump over there to send the adb reboot download command. All this does is reboot the phone "normally"!
What are my options here? I've already copied everything off my phone with adb, and I'm not afraid to use terminal commands to flash something usable just to get it back to stock before I send it back.
*cough*JIG * COUGH*
Sent from my SAMSUNG-SGH-I897 using XDA App
Would that work with CWM 3.0/CM7 Kernel? I've always had weird issues with plugging things in and it just booting up, even when my power button worked.
The jig should work...the only thing that would cause the cm7 kernel to boot when plugged in is if it was off and you were only trying to charge it. The jig just redirects some power into pin 4 telling the bootloader to initiate download protocol...kinda the same way your phone knows when its hooked to a mountable usb port and when its charging out of the wall or something.
similar issue
I recently attempted a flash of fantasy II (2.3.5) captivate, and i got the bootload, and kernel installed and then installed the stock 2.3.5 rom to flash fantasy II over. . . . well after getting the stock rom, i found it had what i wanted, so i was going to stick with that.
i noticed about ten minutes after getting that rom, that my lock button was not working, and the phone would auto boot, i would pull the battery and put it back in and BOOM at&t boot screen right away, not one button pushed, I have bricked and unbricked my phone since then, and i am now simply running 2.1 stock, however; the dang lock button still does not respond at all, and it will auto boot still, is this the kernel or the bootloader? I know its not the rom now . . . . Please help this is awful!
and if you have a solution that i can download please post it!
Yesterday my phone started acting up. All running process crashed and not many was able to start. I had to constantly click "force close". I think this started after I installed the Google+ app, but not sure.
I have tried uninstalling all unnecessary apps, without luck. I then tried wiping to factory settings by using the Android menu, but without any changing. I then tried by holding vol+ and power, going in to recovery and wiping both to factory and app cache. This doesn't change anything either. By googling I can see some suggests to hold vol- and power, to get to a another wiping-functionality but this just boots my Nexus S to normal state - no menu appears.
Has anybody an idea of what I can do?
Edit: more info; if I click "Report" and investigate the message sent to Google, I see that error has something to do with SQLite-relatet classes. Which makes some sense, alot of my changes are reset each time the phone is rebooted. For instance did I miss a call a couple of hours before the phone went crazy - this is shown at each boot in the notification area eventhough I clear the area and/or goes to missed call section
Factory reset via menu does delete all your "custom" apps, so I'd say it's not one of the existing apps causing problems.
The way you describe function after your factory reset sounds like factory reset didn't work properly.
If you feel safe I'd recommend rather flashing 2.3.4 again using either Odin or the OTA zip from Google (requires open bootloader).
I think you're right that factory reset doesn't do what is expected. Once I click it, the phone reboots and shows the Android guy next to an unwrapping package. This lasts only 2 seconds, then it reboots itself again and goes into normal phone mode (where all the app-crashing starts again).
I have not flashed or rooted my phone before, but I will consider this now since my NS is pretty much a brick. Thank you for your swiftly response.
Edit: Shouldn't I get a menu, when I push and hold vol- button, while turning on the device? Right now it just boot as normal.
Before you use odin....try going into rom manager a reflashing clockwork! Ive had that android dude on my screeen but reflashibg via rom manager always fixed it. Try that
Sent from my Nexus S using XDA Premium App
Wow my Nexus has totally shut me out.
I cannot use ClockworkMod unfortunately since I am not able to root my phone. It is not detectable via USA (when I use vol+/pwr and connect USB). I am unable to check the USB Debugging option on the phone. Each time I check it, go to home-screen and back to the menu, it has de-selected it again. Also I noticed when I read the info that is sent to Google for all those app-crashes I get, I see SQLiteException and error in an SQLite.java file. So it seems like some database layer is broken.
I read one could copy the ClockWork.img to my phone and use the standard recovery option to flash the img (I think). But when I go into the recovery menu, the file is gone. When I boot the phone again, it has deleted the .img file - eventhough if I copy it to several different folders, they are all gone :-(.
I feel pretty screwed at the moment. How can I else wipe all data?
I'd recommend to check if your device is correctly identified in windows. Missing USB drivers might cause problems. Get the latest drivers and a guide from here.
If you succeed booting into fastboot properly (vol up and power) you can follow this guide. Get the latest cwm recovery.img here.
Last option would be to boot into download mode (vol up + vol down + power + plugging in usb cable) and use Odin from samfirmware.com
--
All options require correctly working USB drivers.
I managed to unlock the bootloader, by quickly turning on USB-debugging (before any processes started to crash) and install the drivers from this post:
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
A reboot later, I got this message:
"System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Right below was a button saying "Im feeling lucky" (??)
I installed ClockworkMod using fastboot and tried "Fixing permissions" with no luck. I will try some ROM later on, and hope it will bring my phone back
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
rentaric said:
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
Click to expand...
Click to collapse
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
DennisRP said:
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
Click to expand...
Click to collapse
See I'm no expert on this whole thing. At this point I'd just flash a whole new system via Odin. Prolly not the smartest or safest option, but that's what I'd do because I don't know better. If that wouldn't fix it either, I'd return the phone on warranty
I was looking at Odin from the start, since nothing else seemed to be working.
So right now I got started on Odin. Followed the .pdf steps and flashed the bootloader at first succesfully. I was asked to remove the battery and re-connect my NS. Began downloading "pda" and "phone", but at around 10% a big fat red "fail" message appeared and now I just see the Google-logo on startup. I still cant flash any roms via fastboot.
Im too tired too right now, been working with this for 14 hours straight. I will look at it tomorrow evening. Thanks for your help rentaric
Weird, you're not the first one who had trouble running Odin using their guide.
Overall it's pretty simple.
Enter download mode. Vol up vol down and power at the same time while plugging in the USB cable. Start Odin, should show a yellow colored box with a port number. Uncheck everything but reset timer and auto reboot. Unzip the correct zip file from samfirmware.com (check if you got i9020 or i9023 and get the universal Odin exe), apply file from the folder accordingly. Bootloader and bootloader. Phone and modem. Pda and pda. Csc can remain empty (will change carrier info in fastboot).
Double check md5 hash to avoid broken files.
Sent from my Nexus S using XDA App
rentaric said:
Weird, you're not the first one who had trouble running Odin using their guide.
Click to expand...
Click to collapse
Of course I did not go to bed, how should I be able to sleep with a broken phone .
The firmware suggested on samfirmware.com for my phone, was 2.3.3 and some other version (my phone was 2.3.4.2/GRJ22 or something similar, I suspect that might be the cause. Also I unchecked everything, that might also have been of importance). The flash will always fail when everything was downloaded - it then said something about "remote" and "Loke" and then fail. But as I mentioned, I had succesfully flashed boot.img (2.3.3) thus no boot occured now. I googled the correct bootloader, used fastboot and was booting succesfully again.
I began looking more into the sdcard, as error-messages was leading me this way. To compress 4 hours of investigations into a few lines, it seems as my PBA is malfunctioning as other xda-members have experinced. Only solution is sending the phone to Samsung for a PBA replacement. I purchased the phone in Bestbuy USA and the danish Samsung partners are not too joyfull about this - I will contact Samsung and hope they can help me.
I experinced the exact same thing as this poor guy - http://forum.xda-developers.com/showthread.php?t=993403
Every thing you try to do to /sdcard is worthless.
Formatting (USB/using CWM/using adb shell linux commands) says "Succes" but nothing happens.
Copying files says "Succes" but nothing happens. If I boot phone into CWM, mount usb and upload new rom/apk/whatever and try to do a "install update.zip" it fails with some mounting errors.
Im ready to go cry in a corner - I really want this to be fixable via software, but I probably have to realize that this is a hardware issue.
Apparently Samsung doesn't offer worldwide warranty for cellularphones :´(. God it sucks to pay repair-expenses on a 1 month old mobile.
Hi and Thanks to all the help that I have found here since my problem started a week ago. I am a Noob. I
PHP:
am becoming an informed Noob.
I am copying my response post from http://forum.xda-developers.com/showthread.php?p=37915235#post37915235 her as it outlines my trail;
Begin cut n paste:
Quote:
Originally Posted by MrKickstand View Post
Are you rooted?
Sent from my SGH-I997 using xda app-developers app
Same response:;
[B]Infuse 4G Firmware 2.3.6 ;Baseband 1977UCLB3;Kernal 2.6.35.7-1997UCLB3-CL997492; Build Gingerbread.UCLB3[/B]
[I]Superuser present and active. ADB Root response same= "adbd cannot run as root in production builds"
[I]When I power off and and press the power button, all I get is the progress wheel and an empty battery logo, over and over. Remove battery, count to 10, reinsert battery, after a couple of seconds the progress wheel then nothing.Press and hold power button same as previous. I can not enter recovery, I can enter download and that's the only way I can boot currently is by re-flashing with ODIN the 1997UCLB3.tar.md5. I can reboot with adb reboot. (Nothing happens when I use the 3 button to get into recovery since before the first Odin Flash.)
History: First occurrence Thursday 2/21/13 with no charging when plugged into the charger (3 tried) Read most of the posts here regarding no charge and boot loop (never got to SAMSUNG logo). Downloaded ODIN and the above ROM and re-flashed when my phone booted, I had everything and was rooted. I was happy until I turned it off and tried to turn back on. same progress wheel and empty battery, I re-flashed and did a hard reset, re-flashed and now my data was gone, reinstalled some things, turned the phone off, same no start. Used heimdall back to stock and when running, as expected, but when off, no start.
Yesterday I downloaded SDK and could ADB reboot. Then I dismantled my phone and cleaned what little just had gotten inside, inspected the power button with magnification and noted nothing wrong reassembled inserted battery and pressed power, same results. Re-flashed to get up and tested all functions which seem to working. I have dropped the phone intentionally several time to no avail.
I can turn the screen off with the power button and wake it up. I can lock the camera with the power button and wand unlock it. I don't know if there is an additional circuit connected to the power button for start and I really need to re-solder ( a little scary for me) with a sharp tip and steady hand. I am considering purchasing a cracked screen phone on eBay and swapping mother boards.
At present, I just don't turn the phone off and use Airplane mode at night. I appreciate the work that I see on this forum and will be grateful for any solutions.[/I]
End cut n paste:
Since that date: I have factory reset a few times due to rebooting via download mode and flashing via Odin because upon reflash I lose my mobile connectivity (No wireless service, IMEI as if the Sim was not in) Reset fixed that but of course I had to reinstall all my Apps, google acct. etc (My restore will not come up to clear cache and reboot. I do not have a Recovery mode nor a back up and numerous attempts to get CWM have failed.
I do not intend to turn this phone off until I get a replacement which should be in my hands Tuesday. I am asking for a clean GB rom for Odin that will let me reboot without changing anything. I have jscott30's unbrick Roms that have gotten me where I am and don't want to reflash back to stock anymore, Thanks a 1 to the 1oth power jscott 30 and to qkster for his guides. Without the recovery, I am at a loss of what to do. So I will be cool with a point to a clean UCLB3 Rom to reflash should my phone freeze before Tuesday
Thanks and Make a woman Happy today for Valentines
After you go back to stock and flash a working cwm kernel make sure you release power on logo keep holding vol buttons for at least a min,sometimes it takes a few.I'm sure you did but some people don't.
Sent from my SGH-I997 using Tapatalk 2
I never get to the Logo
Thanks, but I never get to the LOGO.
I tried to flash a CWM kernal and it failed with an error on reboot about something not being formatted, At each "return to stock" Odin, I select the format button and since I can't get to recovery on my own, use the Settings, Privacy, Factory reset with Fromat USB, I have the 1997UCLB3-roo.tar.md5 that I will use if my phone turns off or goes dead to reflash back to life.
TJj33p3rz said:
After you go back to stock and flash a working cwm kernel make sure you release power on logo keep holding vol buttons for at least a min,sometimes it takes a few.I'm sure you did but some people don't.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Oldbutnew said:
Thanks, but I never get to the LOGO.
I tried to flash a CWM kernal and it failed with an error on reboot about something not being formatted, At each "return to stock" Odin, I select the format button and since I can't get to recovery on my own, use the Settings, Privacy, Factory reset with Fromat USB, I have the 1997UCLB3-roo.tar.md5 that I will use if my phone turns off or goes dead to reflash back to life.
Click to expand...
Click to collapse
if you can use odin,
flash jesse's option c.
this will give you the base rom with lidroid boot into recovery option
download this: http://forum.xda-developers.com/showthread.php?t=1702026
flash it in cwm. use the back up the whole rom option.
this will back up just about your whole setup at any one point and make restoring easier.
you had mention about not being able to get into recovery...
what i was wondering is: while running the rom, if you use the pull down status bar menu, go to the far right, there are some reboot options..one of which is recovery..what happens if you choose that option?
Thanks qkster!
I think I tried Option C a couple of days ago and something didn't go right. I figured it was because I couldn't wipe the cache in recovery. I had aslso attempted your kernal flash using the program you recommended. On reboot I got the something not formatted right. I had used my laptop and USB to copy the kernal file to a folder I made in the Infuse. But to be clear. Since I can't clear the caches in recovery, just flas option c, selecting PDA? (No PIT or phone?)
I do want to get the C.
As for the infuse Toolkit, you mean after I get CWM vis Jesse's option C?
You ask about the pull down status bar "when running ROM" is that in ODIN it self? I am not sure where you mean,
Thanks for your patience,
qkster said:
if you can use odin,
flash jesse's option c.
this will give you the base rom with lidroid boot into recovery option
download this: http://forum.xda-developers.com/showthread.php?t=1702026
flash it in cwm. use the back up the whole rom option.
this will back up just about your whole setup at any one point and make restoring easier.
you had mention about not being able to get into recovery...
what i was wondering is: while running the rom, if you use the pull down status bar menu, go to the far right, there are some reboot options..one of which is recovery..what happens if you choose that option?
Click to expand...
Click to collapse
Oldbutnew said:
Thanks qkster!
I think I tried Option C a couple of days ago and something didn't go right. I figured it was because I couldn't wipe the cache in recovery. I had aslso attempted your kernal flash using the program you recommended. On reboot I got the something not formatted right. I had used my laptop and USB to copy the kernal file to a folder I made in the Infuse. But to be clear. Since I can't clear the caches in recovery, just flas option c, selecting PDA? (No PIT or phone?)
I do want to get the C.
As for the infuse Toolkit, you mean after I get CWM vis Jesse's option C?
You ask about the pull down status bar "when running ROM" is that in ODIN it self? I am not sure where you mean,
Thanks for your patience,
Click to expand...
Click to collapse
I'm wondering if you may have several things confuse..or at least the terminology anyway.
In order to flash Jesse's option C, you have to be in DOWNLOAD mode (DL or dl) and flashed with Odin on your PC.
When you have the phone running, if you touch the top of the screen and pull it down, you have the status bar menu. You can sweep the icons to the right for additional options.
if you are looking to wipe cache for what ever reason, here is one option without using recovery menu:
https://play.google.com/store/apps/...251bGwsMSwxLDEsIm1vYmkuaW5mb2xpZmUuY2FjaGUiXQ..
if you are looking for an easy way to get into recovery, here is another app:
https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot&hl=en
It's making progress
qkster said:
I'm wondering if you may have several things confuse..or at least the terminology anyway.
In order to flash Jesse's option C, you have to be in DOWNLOAD mode (DL or dl) and flashed with Odin on your PC.
When you have the phone running, if you touch the top of the screen and pull it down, you have the status bar menu. You can sweep the icons to the right for additional options.
if you are looking to wipe cache for what ever reason, here is one option without using recovery menu:
[I can't post links yet}
feature=search_result#?t=W251bGwsMSwxLDEsIm1vYmkuaW5mb2xpZmUuY2FjaGUiXQ[/url]..
if you are looking for an easy way to get into recovery, here is another app:
{del} /play.google.com/store/apps/details?id=com.siriusapplications.quickboot&hl=en[/url]
Click to expand...
Click to collapse
It's most likely my attempt to communicate with unfamiliar terms:
I can and always have been able to get into Download Mode, and flashed Jesse's C via Odin that way. Originally back at the beginning, It was Odin and Jesse's B that got my phone up. but it didn't solve the problem of not being able to turn the phone on with the power button. It was Wednesday evening that I attempted to load the kernel you had to add CWM, that's when it failed and then the Jesse C failed on Odin and I had no wireless connection or IMEI etc. Back to your unbrick then the factory reset with phone running and using the Privacy menu.
Until I downloaded the Quick Boot at your recommendation, I have not been able to enter Recovery from a phone in the off status. (Recovey ran at the end of each Odin flash). Thanks also for the Cache Cleaner.
Now when I pull down my top bar, nothing scrolls left to right or right to left and I don't ever recall seeing that happen in the last 1.5 years.MIne just shows L-R Wifi; Blue T; GPS; Flight Mode; Screen rotation.
Now I am good as long as the phone doesn't freeze and I have to remove the battery. I have in those cases I have re flashed Jesse's B to bring the phone up. Only the last time I ended up with no wireless (No Sim recognized and it was installed), and I went back to stock to regain it. So I am a bit paranoid about re-flashing anything new now. But knowing me I will before the weekend is done. The Reboot app is what I have been trying to figure out how to do. When I get the new phone and get it up and running and stable, I'll attempt to re melt the on button solder and possible the USB connector solder too. USB connection now dies if the screen time out turns the screen off. (If i keep the screen alive by doodling on it no problem transferring files.)
Thanks for your help I am a bit compulsive so all of this is my current obsession.:laugh::laugh:
Oldbutnew said:
Now when I pull down my top bar, nothing scrolls left to right or right to left and I don't ever recall seeing that happen in the last 1.5 years.MIne just shows L-R Wifi; Blue T; GPS; Flight Mode; Screen rotation.
Thanks for your help I am a bit compulsive so all of this is my current obsession.:laugh::laugh:
Click to expand...
Click to collapse
you're right about the status bar..looking over jesse's description, you would have to flash the lidroid as an extra
http://forum.xda-developers.com/showthread.php?t=1698972
there is something odd about your phone though...possible hardware issues...you should not have to keep screen on to complete a background task.
under Display..there should be an option to keep the screen on longer than default if you it
gl
I do believe it's hardware too.
qkster said:
you're right about the status bar..looking over jesse's description, you would have to flash the lidroid as an extra
http://forum.xda-developers.com/showthread.php?t=1698972
there is something odd about your phone though...possible hardware issues...you should not have to keep screen on to complete a background task.
under Display..there should be an option to keep the screen on longer than default if you it
gl
Click to expand...
Click to collapse
I set it on 2 minutes and touch the screen often. Funny it doesn't have an issue in DL mode, Sometimes I wiil have SUB Connected and no charging and It'll connect in the back ground, lose connection repeatedly and all of a sudden show the charging Icon, which I haven't see since all this began 9 days ago.
This phone has had some big drops. last one about 4 days before this began, vibrated off my table saw onto the concrete floor,
Thanks.
New phone works as advertised
Oldbutnew said:
I set it on 2 minutes and touch the screen often. Funny it doesn't have an issue in DL mode, Sometimes I wiil have SUB Connected and no charging and It'll connect in the back ground, lose connection repeatedly and all of a sudden show the charging Icon, which I haven't see since all this began 9 days ago.
This phone has had some big drops. last one about 4 days before this began, vibrated off my table saw onto the concrete floor,
Thanks.
Click to expand...
Click to collapse
Ok eBay phone arrived this afternoon. Factory reset, Odined, Jesse's C option. Yeah, CWM recover. I loaded most of my programs and backed up my ROm. I will experiment on my old one now.
New thing happening. I still can't start the phone from Off. BUT if I plug in the charger and hold down the on button and the down volume button after a few cycles of the dead battery icon, I get a charging icon and the phone is charging. Now with that icon working I can hold the power button down and the phone starts. Charger or USB need to be plugged in for that to work.
Update on the Start button.
Oldbutnew said:
Ok eBay phone arrived this afternoon. Factory reset, Odined, Jesse's C option. Yeah, CWM recover. I loaded most of my programs and backed up my ROm. I will experiment on my old one now.
New thing happening. I still can't start the phone from Off. BUT if I plug in the charger and hold down the on button and the down volume button after a few cycles of the dead battery icon, I get a charging icon and the phone is charging. Now with that icon working I can hold the power button down and the phone starts. Charger or USB need to be plugged in for that to work.
Click to expand...
Click to collapse
Thursday Update:
Recap of current state:
Factory Reset from phone/security/fatory reset.
Flashed Jesse's C option with odin https://www.facebook.com/jennifer.waddell.963/photos_stream?ref=ts and let it boot all the way. Next I down loaded Quickboot (see qksters link above) and restarted in Recovery. Voila Red CWM. Cleared cache; factory reset; Advanced cleared davlik cache. Rebooted and let it fully load. Turned off to enter download.mode and Odined a second time Option C.Everything looked good on all accounts, reentered Google data etc. like a factory reset requires. Re installed Quickboot and booted to CWM and backed up my ROM.
I turned the phone off and the start button wouldn't work still, but I held it a long time with the down volume button (not sure this is necessary, just what I did) and all of a sudden instead of the dead battery logo, I got a charging battery logo and it was 87% charged. First time I had seen this in while. I pressed and held the power button and the Samsung Logo came up and the phone booted. (Slow boot compared to the new Infuse I now have.) So now my old phone was working, but not up to 100%.
I charged the battery to 100% and turned it off and left it off for the day/night. Yesterday I got it to turn on with all the buttons pressed and it booted, said connect battery charger/low battery 1%, h'mmm. I charged again to 100% and turned it off all day and night. Same issue this morning. Something is draining the battery when fully off. SO I still have a hardware issue I believe, just not sure what it is.
Thanks for any insight, I'll keep experimenting.
Oldbutnew said:
Thursday Update:
Recap of current state:
Factory Reset from phone/security/fatory reset.
Flashed Jesse's C option with odin https://www.facebook.com/jennifer.waddell.963/photos_stream?ref=ts and let it boot all the way. Next I down loaded Quickboot (see qksters link above) and restarted in Recovery. Voila Red CWM. Cleared cache; factory reset; Advanced cleared davlik cache. Rebooted and let it fully load. Turned off to enter download.mode and Odined a second time Option C.Everything looked good on all accounts, reentered Google data etc. like a factory reset requires. Re installed Quickboot and booted to CWM and backed up my ROM.
I turned the phone off and the start button wouldn't work still, but I held it a long time with the down volume button (not sure this is necessary, just what I did) and all of a sudden instead of the dead battery logo, I got a charging battery logo and it was 87% charged. First time I had seen this in while. I pressed and held the power button and the Samsung Logo came up and the phone booted. (Slow boot compared to the new Infuse I now have.) So now my old phone was working, but not up to 100%.
I charged the battery to 100% and turned it off and left it off for the day/night. Yesterday I got it to turn on with all the buttons pressed and it booted, said connect battery charger/low battery 1%, h'mmm. I charged again to 100% and turned it off all day and night. Same issue this morning. Something is draining the battery when fully off. SO I still have a hardware issue I believe, just not sure what it is.
Thanks for any insight, I'll keep experimenting.
Click to expand...
Click to collapse
it could be your battery that is bad.
try a new one if you have not tried several others:
http://www.ebay.com/itm/New-Premium...902705?pt=PDA_Accessories&hash=item27ca3fca31
qkster said:
it could be your battery that is bad.
try a new one if you have not tried several others:
http://www.ebay.com/itm/New-Premium...902705?pt=PDA_Accessories&hash=item27ca3fca31
Click to expand...
Click to collapse
I have tried several other batteries now with the same results.
Yesterday, I decided it would be a good idea to use this phone as a practice platform for a Jelly Bean upgrade.with scott.hart.bti's http://forum.xda-developers.com/showthread.php?t=1776129
Everything went as advertised and I was pretty happy for a while. I was following the instructions quite literally and after flashing the CM9, I removed the external SD card and that messed up getting back into recovery, but I got there. From reading, I understand that I need the IC flash to preserve the EFS file, but not absolutely sure that I can't remove the SD card before starting the process altogether. CM9, then CM10.
Since all my programs needed to be re-downloaded and installed, I had the "Bright idea" to restore the backup in CWM that I did just before the upgrade. Bad idea, now I had a phone that would not boot.
Is there a way to upgrade to JB and not have to re-install all my programs? I will try the Nandroid backup in CWM
To get back working again, I could get into download mode, but not recovery, so I did J scotts back to stock, then the option C to get CWM and used quick boot to get into recovery and reflashed with an experiment of using your Quick wipe in stead of factory reset on this go. Again when I took the SD out at the finish of the CM9 I had a little trouble getting into the recovery to continue. When it did get to recovery, I finished flashing per the instructions, but when it booted I only had a partial group of programs, Google play was the most notable omission. I took a deep breath and did a factory reset, and managed to get into recovery and started with a flash of CM10 again and this time all ok.
I did a couple of boots with quick boot and powered down for the night with it plugged into the charger. This morning I can not get anything up. Battery charging icon shows and goes away (CM10 battery logo) I can get into download, but not recovery and don't really want to Odin back to stock and go from there, but may do that and leave it in GB while I update the new phone.
My conclusion is that it's hardware and possibly USB connector. IN GB the USB cable wouldn't connect so I used Software data cable. In JB it worked. Still confusing, but I'll keep at it.
Thanks for your patience and my learning curve!
Yesterday, I started unlocking my bootloader on Xperia J ST26i in order to eventually finish with installing ParanoidAndroid 3. It all went successful until I got to the last step of rooting the device. This - http://forum.xda-developers.com/showthread.php?t=2183737 - is the method I used. I was confused when I got to step 16, because the kernel I copied for flash didn't show up. So, I'd finish with two choices after shutting the phone down, having exited CWM Recovery. I would either open CWM again, after seeing LEDs glowing purple/blue in order to press Volume down key to enter CWM - or to ignore and finish seeing grayscreen. Luckily, I was able to find a JB 4.1.2 kernel for my rooted Xperia J, so I put it and flashed it instead of the ICS kernel provided on the thread I referred to. That solved the problem. I had JB 4.1.2 installed and rooted with ROM Manager installed along with SuperSU app. The next step I was going to do was to install a ClockWork Recovery, I hesitated installing PA3 directly without a recovery image. Ironically, CW Recovery is what really made all the problems now. Searching on Google I found a way to boot directly to ClockWork Recovery, I pressed and held the buttons for initiating it but I ended up with literally no way to normally boot the phone. So, I couldn't turn on the phone except in fastboot mode. In fastboot, I whiped all the data, reset to defaults, reinstalled the boot.img and JB kernel, however after all the resets and whipping anything that, according to many sites and devs, should make the phone function again...it failed. After a dozen times of taking out the battery, button combos I ended up not being able to access neither fastboot mode with CWM showing all those options for whipping, installing etc. Only phone's upper LED was working and it blinked red so I recharged the phone, then it was all the same but it'd blink green. After another hour of trying to turn on the phone in any mode, nothing good happened. When I held the power button, it vibrated but after a minute or so only green LED activated. Then I downloaded recovery exit zips that I'd install if ever got to CWM again. I tried once again to directly boot into CWM recovering by holding the power button down and both sides of volume rocker. It blinked light blue, then green and later blue. Device flasher couldn't read the phone, so I opened flash mode. It read it, but any installation of boots or kernels failed because of the phone that either disconnected or simply failed. There was no way for me to put more files on Internal Storage or SD Card, only those LEDs started behaving the way I described. After another twenty times of battery removing, 10 second and 30 s waiting, button combos, anything I could find on Google, nothing changed. Except, suddenly, the computer is able to link with the phone after holding power button for boot that only activated the green/blue/violet LED. Still, no response from flashing program, still failed to enter fastboot, CWM, direct CWM Recovery etc. But, now when my phone is, let's say, turned on with green or blue light, I can access SD Card and Internal Storage via Windows Explorer. Just below the hard drives, I can see my phone. Great? No, it's not Xperia J as it should be, PC detects Xperia Tipo. I also noted that it's mistaken SD Card for Internal Storage... Let's see what happens when I remove SD card from the device. Please help...
Bricked
And yes, this means it's bricked. Can't boot into CWM or anything. It's only good as a storage unit, energy consuming or as a brick. I got this phone in January so please don't tell me it's irreversibly hard bricked.
dave96m said:
And yes, this means it's bricked. Can't boot into CWM or anything. It's only good as a storage unit, energy consuming or as a brick. I got this phone in January so please don't tell me it's irreversibly hard bricked.
Click to expand...
Click to collapse
Okay, so first calm down. Any sign of life means it's not hard bricked but just soft bricked.
1st download flashtool: link
2. download ur stock ftf link
3. flash it with flashtool
and u should be fine again, back to stock with a fresh phone.
Can't fastboot device - remember: button combos don't work
I've also found some solutions for more severe soft-bricking, by the way. Anyway, how to make phone open fastboot? I've said it's unresponsive to all of the button combo commands. Though, I tried one more time.
Opened the flashtool... Held volume up and plugged in the USB cable...
17/009/2013 22:09:51 - INFO - <- This level is successfully initialized
17/009/2013 22:09:51 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
17/009/2013 22:09:51 - INFO - You can drag and drop ftf files here to start flashing them
17/009/2013 22:09:57 - INFO - Device disconnected
17/010/2013 22:10:12 - INFO - Device connected with USB debugging off
17/010/2013 22:10:12 - INFO - For 2011 devices line, be sure you are not in MTP mode
Immediately, upper LED started glowing green, then it turned itself off after a minute. The phone is still connected.
Remember to pull up battery (and pull in of course ) than go to flashtool, fastboot PWR + Vol Up.
Solved
http://forum.xda-developers.com/showthread.php?p=41506173#post41506174 See my last post, scroll down. Thanks for help, guys
sony xperia j - alarm problem
Hi guys,
I bought Sony Xperia J and 2 months ago I upgraded the Android to the latest version 4.1.2 (Jelly Bean).
After the upgrade the Alarm on the phone does not go off, it starts to ring (the alarm) only when I press the button to unlock the phone, I've read somewhere that when the screen is off the clock is not refreshes properly or something like that.
Can you please, help me?
Regards
Lol I know that feel bro.... It happened to me few days ago but no worries i just flashed the firmware using flashtool whenever i failed. Now i'm happy with my CM10 with vengeance kernel... its not the phone that's causing the problem its up to us how we handle it and i didnt find PA3 that interesting it was too laggy for me...
I didn't experience any of such problems that you have, but still listen to the man's advice. Install CM10. It speeds up your device, gives you options, frees your Android. My friend knows the feeling of switching from iPhone to Nexus 4 and he's like he's enlightened or something, well once again, the feeling is the same if you switch from stock Android to CM or Paranoid. I suggest you install CM because Paranoid made me a lot of problems when installing even though I did everything right, and people claim that CM is more stable...
http://forum.xda-developers.com/showthread.php?t=1997251