Related
Ok next problem.
I have xda2i and have used the unlock tool from this forum... thank you will donate to help forum....
The problem is when I remove old sim to put the new one in the poxy phone hard boots itself
Is there a way to swap sims without loosing all data
Thanks in advance
its easy, do it in under a minute and youll be fine
at least, thats the case for a SIM change for the Magician, I can imagine it being the same for your device
so: just be damned fast
Hi John, just keep your XDA plugged into the power adapter and you will not loose your settings. For some reason they mostly all do this. There are some folks that say their XDA's work as they should but most people have the same problem as we do.
Bob
I suprised it hard resets when you do this ... whenever i have done it, it never hard reset once (i've done it alot).
i know if you take longer than 20 minutes to do anything without the battery attached it hard resets.
As someone said ... just leave it plugged into the AC adapter when your doing it, that should keep the backup battery topped up
Perhaps its the backup (20min battery) thats faulty wth your phone.
Im really really hoping that someone can help me here
It started this morning around 10:00 or so - I took my phone out to check my messages, everything is working fine. I lock the phone and put it standby (power button) and *surprise*, it locks up and wont come out of standby
So i just re-set it (like im forced to do 20 times a day) and instead of booting it went straight to this red/green/blue screen. At the bottom of the screen it just says "Serial" but doesn't actually give a serial.
I instantly thought it was bricked, so i removed the battery and left it out for a few mins. Then i put the batt back in, and it booted normally. I used it throughout the day with no problems.
Fast forward a few hours and it does it again but now it wont boot at all (ive reset the thing like 100000 times in the last hour ive been working on it).
WTF is going on?? Im really really hoping that it isnt too screwed to fix
The last program I installed was the SPB pack, but that was over a month ago, and i use the phone every day, multiple times a day.
Oh, and to make things worse i was planning on relying on my TomTom tomorrow
and the text on that screen says:
Kais1*0
SPL-1.56.0000
CPLID-8
And at the bottom it just says "Serial" but none is given.
This blows
Have you recently tried to flash your phone? Have you ever? If you never have flashed it or attempted to use Olipof's app, then take it to the store and demand a new one.
Do you see "USB" instead of "Serial" if you connect your sync cable to your phone when in the bootloader?
If so, I would download the latest carrier-branded rom and flash it to your device. As long as the rom is designed for your device, then you do not need to do anything special prior to running the file from your PC.
grandpareza said:
Have you recently tried to flash your phone? Have you ever? If you never have flashed it or attempted to use Olipof's app, then take it to the store and demand a new one.
Click to expand...
Click to collapse
I have never flashed it but i have spilled water near it (on the counter, the phone got wet but that was months ago and has no relation to this).
Can they check if it has been wet before?
When i plug it into my computer it says USB instead of serial. Should I try to re-flash with an updated rom and see if it fixes it or just take it in?
If you find me on MSN IM ([email protected]) we can run a diagnostic & see what the problem is.
GSLEON3 said:
If you find me on MSN IM ([email protected]) we can run a diagnostic & see what the problem is.
Click to expand...
Click to collapse
Thanks, ill give you a buzz.
I need to finish and email a few things first (shouldnt take more than 30mins).
Actually, ill just message you tomorrow or something.
Ive been really busy this week.
well did you get it fixed? what did you do?
Yikes, that happened to a friend of mine, but he flashed his and then had to reflash it. I think there is a place on the back under the battery that they use to tell if it's been wet. I would take it back, even if flashing it fixes it, you don't want it to happen again.
oh and it doesn't mean serial like a serial number, it is a serial connection.
I havent been able to get it fixed.
I think ill try to flash it this weekend and see if that fixes it
You'll only make problems worse if you reflash. I've analyzed the MTTY output you've sent me & you have a bad NAND storage blocks.
You need to follow the directions I sent to your email account via MSN IM.
DO NOT REFLASH UNTIL YOU'VE TAKEN CARE OF THE BAD BLOCKS!!!
this happened to me and someone else in XDA a while back. I saw his thread (link below) and then PMed him. I will copy / paste our PMs:
http://forum.xda-developers.com/showthread.php?t=344402
jackjohnson said:
dockular said:
jackjohnson said:
dockular said:
Sup Jack, my Tilt is doing the
Kais1*0
spl-1.56.0000
cpld-8
Serial
problem that you had talked about. I read that huge thread, lots of great info in there. Although its unfortunate what happened to you, I'm really grateful of all the troubleshooting that you've done before me, so I know what works and what doesn't. Interesting to note that I have had the Tilt since the day it came out, and never cooked/ flashed my rom. I have been using the Tilt rom the whole time with no problems. Otherwise I'm a huge power user and have a ridiculous amt of software installed.
So after everything was all said and done, did you end up just replacing the device? Thanks again man
-Anthony
Click to expand...
Click to collapse
Anthony,
Yea I went ahead and replaced it. No matter what I did to reflash the original bootloader, and flash the original rom, I always ended up with that same problem. Did you notice that if you can't get it out of the bootloader, but you connect it to your computer, and while it's connect, you soft reset, that it boots? Just curious. that's what happened to me. Either that or I would have to yank the sim and battery, then try.
My tilt was working fine for about a month with a flashed rom, up until I started installing gobs of software on it. Just a thought. If I were you, I would get the device replaced. Especially if you've never flashed a new rom on it - it definitely should not be doing that.
Scott
Click to expand...
Click to collapse
My computer has been broken for a month or two. To answer your question - I haven't been connecting it to anything other than an AC outlet. Anything installed in the last couple months was installed OTA... I usually just obtain a CAB by downloading it directly onto my device.
Also, its weird but sometimes after I drain the batter with the RGB screen then recharge it (this process takes about a day) then hit the reset button, it will actually boot correctly. I am on the third time this has happened. It was bricked for a couple days, then after a combination of charging / depleting got it to boot into windows. Then it happened again, then again.
As long as I don't restart the phone it will stay in windows... If I restart then I lose it for a day or so. Interesting to note that since this has happened, phone calls connect, but I can't hear the other party and they can't hear me.
Also, I use the mini usb out to a 3.5mm stereo jack to stream shoutcast into my car stereo while driving. Last week (at the onset of my problem) the music was playing from the Tilt's speakerphone, and not going through the headphone jack as it normally would. A restart fixed this, but when it happened again a day or so later, the next restart is what got me to that boot screen for the first time.
One of us should post this in the forum...
Click to expand...
Click to collapse
And just an update, I never sent back my phone or did anything as far as bad blocks go. I just let the battery drain and booted it right up and now it works perfect. I have since installed a few cooked rooms and radios and have had no issues since. This RGB screen was isolated to just those few days that we were talking about in the PMs.
Click to expand...
Click to collapse
dockular said:
this happened to me and someone else in XDA a while back. I saw his thread (link below) and then PMed him. I will copy / paste our PMs:
http://forum.xda-developers.com/showthread.php?t=344402
jackjohnson said:
And just an update, I never sent back my phone or did anything as far as bad blocks go. I just let the battery drain and booted it right up and now it works perfect. I have since installed a few cooked rooms and radios and have had no issues since. This RGB screen was isolated to just those few days that we were talking about in the PMs.
Click to expand...
Click to collapse
Umm... GOOD FOR YOU!!!
I had him perform a diagnostic & it reported HE HAS A BAD BLOCK! So unless you're psychic or can be sure that every problem with Boot Loader is the same as the one you had, I suggest sticking to what you know.
BTW, search the CURRENT threads, in the KAISER forum, & you'll see I've helped a few dozen people with this & similar issues.
Click to expand...
Click to collapse
dude i wasn't telling him to not follow your advice. was just letting him know my story. as a matter of fact, after reading your original post I have decided to check for bad blocks on my phone.
GSLEON3;2021681
[B said:
Umm... GOOD FOR YOU!!![/B]
I had him perform a diagnostic & it reported HE HAS A BAD BLOCK! So unless you're psychic or can be sure that every problem with Boot Loader is the same as the one you had, I suggest sticking to what you know.
BTW, search the CURRENT threads, in the KAISER forum, & you'll see I've helped a few dozen people with this & similar issues.
Click to expand...
Click to collapse
Well, this has happened to one of our phones. Can you just post the fix here instead of requiring the email/IM rotuine?
Hey there all, first off, I have searched for the problem I'm having, and I couldn't find anything. So I figured the Q&A was the place to ask.
I recently received a new/refurb cappy to replace my original (It was pressing the home button repeatedly). The old one was a 1009 build and it worked fine with odin (both versions) and download and all that. The new one however, works with 3 button fix, but Odin wont see it. It shipped from att with the 2.2 already on it, along with 3e recovery. I have rooted the new one, but that's as far as I can get.
So my question is:
Can I switch the new phone back to 2.1 to be able to root/custom rom/etc?
(Also, when I have my battery in the original phone, it shows as normal [whatever its charged to], but when it is in the new phone, it shows as 5% and won't charge, no matter how long I leave it there. Any thoughts?)
sounds like a defective phone. battery wont charge? is it any battery or just the one from the old phone? also can you see the sdcard on the pc with the phone on? and are you using windows xp or windows 7?
AReynante said:
Hey there all, first off, I have searched for the problem I'm having, and I couldn't find anything. So I figured the Q&A was the place to ask.
I recently received a new/refurb cappy to replace my original (It was pressing the home button repeatedly). The old one was a 1009 build and it worked fine with odin (both versions) and download and all that. The new one however, works with 3 button fix, but Odin wont see it. It shipped from att with the 2.2 already on it, along with 3e recovery. I have rooted the new one, but that's as far as I can get.
So my question is:
Can I switch the new phone back to 2.1 to be able to root/custom rom/etc?
(Also, when I have my battery in the original phone, it shows as normal [whatever its charged to], but when it is in the new phone, it shows as 5% and won't charge, no matter how long I leave it there. Any thoughts?)
Click to expand...
Click to collapse
Sorry if this is a stupid comment, but I really just have to ask...
Did you turn USB Debugging on?
If the answer is yes, then I have to agree with the above post. It's sounding a lot like a faulty phone.
The battery is my original one from my first captivate. The phone does show up on the computer when I plug it in, I can access the sd card. Using Win7 64 bit.
I called warranty about it, and they're sending a replacement battery, but really I'd rather stick with my old phone. The new one doesn't like being rooted/cwr'd
Good day folks,
I am in a bucket of hot soup at the moment with my Galaxy S.
Firstly, my Micro USB port has decided to call it a day (I have tried the alcohol cleaning trick and all other "fixes" at this stage I am contemplating getting a new MicroUSB port and installing it) . At the moment the only thing it can do is charge the phone and so perhaps I should be grateful for small mercies.
However, No USB means download mode is now unavailable to me.
This also impacts rooting with a PC. A lack of root means I cannot update my gps.conf, I cannot install a custom recovery and I cannot install custom roms. I also cant back-up or re-install my apps using titanium. I also cant use googletalk 1.3+ wth voice and video calling.
Secondly, my Internal SD card is mounted by the system and recognised as "USB storage". I can still use most apps even though its mounted with the wrong name however certain apps looking for Internal SDcard cannot find my storage. So I need to somehow change that. How do I do that?
For an individual used to running custom roms and tweaking my device any which-way I please, I find my galaxy s very unattractive right now.
I got into this situation when I was coming from Jetpack and I was moving to Simplicity. Simplicity just would not boot. At this point my phone was stuck with no ROM and after sitting and fiddling for about 5 hours with a several micro usb cables and plugging and unplugging my phone odin recognised it for one last flash and i was able to get stock JVT on it. I lost Clockword Mod 3 and so now stuck with stock recovery and thats as good as having no recovery
I really dont want to buy a new phone till I can make a decision between Nexus Prime and Galaxy S3. Im a firm believer in as close as possible to a 2 year phone cycle and my galaxy s has just turned 1 year 3 months.
So if i can root this thing I have now and survive another 6-9 months I'll be a happy man.
Help? Suggestions?
Cheers guys
You say you got stock on it... Any particular reason that you cant give it in for repair? SGS is 2 year warranty as remember...
Also crazy idea, if it is possible, turn cf-root into a update.zip and get it signed LOL. Or check to see if you can use cyanogenmod, and work your way around from there?
Lastly which you should probably do first, another computer?? (or did i miss that?) Oh and check drivers, reinstall them.. (I dont know what fixes you have tried...i just know you've tried)
Talon26 said:
You say you got stock on it... Any particular reason that you cant give it in for repair? SGS is 2 year warranty as remember...
Click to expand...
Click to collapse
Really didnt know that about the warranty. Not practical for me as the country I bought it in is different to the country in which I reside. And Samsung Here wont support/honour the warranties from There yeah what a pain . When I bought the phone I semi-bricked it and had to ship it back and forth to the other country. At the time it was worth it because the shipping values were less than 25% the value of the phone. However now shipping would be almost 100% of the current value of the phone.
Talon26 said:
Also crazy idea, if it is possible, turn cf-root into a update.zip and get it signed LOL.
Click to expand...
Click to collapse
Talon26 said:
Or check to see if you can use cyanogenmod, and work your way around from there?
Click to expand...
Click to collapse
Im looking right now.... will let you know how it goes.
Talon26 said:
Lastly which you should probably do first, another computer?? (or did i miss that?) Oh and check drivers, reinstall them.. (I dont know what fixes you have tried...i just know you've tried)
Click to expand...
Click to collapse
List of "fixes" include amongst others,
1) Different makes of micro-usb cables.
2) Different computers, 3 to be exact.
3) Cleaning the USB port , alcohol trick , scratching with a wire trick , tissue paper trick.
4) Driver un/re-install on all three machines.
5) Rebooting phone interspersed with varying combinations of cable, computer, cleaning steps all to no avail.
All in all, the ownership of this galaxy has been a bit of a pain because I got it within a week of its release and it turns out it was part of that notorious batch that had no 3BR hence the intial semi-bricking.
wmanyati said:
Talon26 said:
Or check to see if you can use cyanogenmod, and work your way around from there?
Click to expand...
Click to collapse
Im looking right now.... will let you know how it goes.
Click to expand...
Click to collapse
Nope, no can do, need root and need CWM. Has anyone ever wanted to root so badly in their life ?
Hey, did you find any solutions? I have the same problem and I can't find any answer to it... Please help
Try this method this worked for me once:
1. Remove battery, plug usb cable with other end connected to pc, insert battery and switch on. I expect you've selected the usb debugging
Sent from my GT-I9000 using Tapatalk
Monu123 said:
Try this method this worked for me once:
1. Remove battery, plug usb cable with other end connected to pc, insert battery and switch on. I expect you've selected the usb debugging
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Tried that and it didnt work thanks.
Yeah i did some research its probably a moisture problem. Idk why and how it got it. It seems that i can charge but driver failed to install/tried reinstall still fail. Any solutions?
Sent from my LG-P500 using XDA App
hellodzulz said:
Yeah i did some research its probably a moisture problem.
Click to expand...
Click to collapse
It is definitely a moisture problem. I managed to change the USB port and that didnt make a different but I also noticed that my board is starting to corode.
So i tried to cleaning the coroded bits gently with a piece of cloth soaked in alcohol and I had one last flash and so I finally managed to root and get clockwork mod.
hellodzulz said:
Idk why and how it got it.
Click to expand...
Click to collapse
After doing a lot of research I discovered that this galaxy s is very prone to moisture issues.
1) Its not well put together so moisture does tend to get into it.
2) Moisture from your hands
3) The daily heating and cooling effects of sun. Especially if you live in a humid environment. The moisture condenses internally in the device. I live 100m from the beach.
4) I also use my phone to monitor my regular cycling activies. I ride in the rain etc and although I have what I thought was a splashproof case for the phone, it still has been quite moistened.
hellodzulz said:
Any solutions?
Click to expand...
Click to collapse
Well given that you cant stop the corroding its only a matter of time before the phone eventually fails so I would recommend the following;
1) Stop storing any data on your internal card I now bought a 32GB sd card and I will just use that so if the phone fails I simply bin it and put the card in a new device.
2) Regularly back-up your device
3) Start saving for a new device
4) Get a new motherboard for the device
5) A scum-bag thing to do is hard reset it and sell it to someone who isnt aware of its data storage properties.
Thanks dude i tought it was the driver fault. Quite sad for my dad
Sent from my LG-P500 using XDA App
me too!
wmanyati said:
Secondly, my Internal SD card is mounted by the system and recognised as "USB storage". I can still use most apps even though its mounted with the wrong name however certain apps looking for Internal SDcard cannot find my storage. So I need to somehow change that. How do I do that?
Click to expand...
Click to collapse
did you resolve this issue?
I ripped my SD slot out a few months back after getting a card stuck in it, I threw the Nook in a corner in disgust and left it there,
I've tried to get it back up and running over the last few days, I've charged it fully over two days using the wall charger but it refuses to boot - I have nothing at all displayed. when i plug it into my PC I hear the noise it makes when a usb device is plugged in but that's it - nothing..
So with all the methods of restoring it need the SD slot..I guessing it's a gonna??
Any ideas??
Could try to convert back to stock. There is a 3 finger method of restoring your nook back to stock. You can find the link here in XDA right here. http://forum.xda-developers.com/showthread.php?t=1461172
Then you can take it back to B&N for a replacement if its still under warranty. Don't be so hardcore with losing on game-mode next time
I tried that last night but will try again with a fresh head ....
Nope..not having it, Tried everything now, using the three finger method brings nothing up on the nook screen at all - totally blank although the pc ssems to respond by making a couple of bleeps so assumed this was akin to the nook being turned on , tried it eight times and nothing..I really do think it's dead...
There is a program in the sdk (/tools/ddms) that allows you to see what is on the screen (and take screenshots). I believe this pulls from what the system is pushing to the screen (not what is actually on the screen). If that is the case, you can hit the power button like you normally would to bring up the lock screen, refresh using the application and see if it is pushing anything. You'd have to be quick, because if the NC is in standby, it won't show anything.
Also, you may want to try pulling some logcats to see what is going on.
I think the nook should be unplugged from the computer when trying the 8 failed boots. Also make sure to hold down the power button at least 8 seconds to make sure the nook is really off.
Sent from my NookColor using xda app-developers app
Can't seem to get the pc to see the Nook, it asks for OMAP3630 driver??
DDms can't see the nook ..
tried the 8 failed boot method...
All is not well
Its now on a popular auction site for spares..I give in.
new one bought and on its way..
p2daz said:
Its now on a popular auction site for spares..I give in.
new one bought and on its way..
Click to expand...
Click to collapse
PM me... I can either fix it and send it back... or perhaps we can work out a price to buy it from you.
I have the same problem. The only way I could get it to recognize it was by holding power for 8 seconds and then would go away after a ssecond or [email protected]
DizzyDen said:
PM me... I can either fix it and send it back... or perhaps we can work out a price to buy it from you.
Click to expand...
Click to collapse
Thank you for the offer but I've bought another and might as well keep it for spares, the postage to the states and back alone would cost what I've paid for the replacement.
Or you could tell me how you would fix it ;-)
What I would wind up doing depends a lot on what is on it already, and what methods were used... first thing I'd do is modify ROM's to ensure mmcblk0p8 was seen as sdcard... then go from there...
I wish I could give you a definitive "Do this, then this, and finally this" type of answer... but there are so many variables in place there's no way I can without knowing more of what is there...
If you have a custom ROM on it... go to playstore and get adb wireless