Let me start by saying my Kaiser has been the most reliable and tweak friendly phone I've come across. About 2 weeks ago, however, I started having a strange issue with the boot up of the device from a power off state. Every so often if I boot it, the device hard boots from the internal rom, erasing everything I've changed since burning the rom onto it. I'm convinced it isn't the cooked rom because it worked fine formonths.
Has anyone come across this issue before? I'm more of a computer guy so forgive any illiteracy, but I'm worried it may be a storage problem of some sort.
If anyone has any idea of what is happening, or perhaps knows of a way to log what is happening, please let me know!
After this problem started happening, did you try any other ROMs? If so, did they exhibit the same problem?
Not that I am the world's authority on it but seeing as how I managed to get my IMEI changed with a simple ROM flash...amongst other issues dealing with incomplete flashing etc, seems you could have a corrupted BL, pop into the bootloader screen and have a look if there is any txt on the top right corner....even though it's erratic it could be sorted by a stock reflash and then flashing your personal flavour of ROM...
Vague but hope it helps..
topgunn said:
Not that I am the world's authority on it but seeing as how I managed to get my IMEI changed with a simple ROM flash...amongst other issues dealing with incomplete flashing etc, seems you could have a corrupted BL, pop into the bootloader screen and have a look if there is any txt on the top right corner....even though it's erratic it could be sorted by a stock reflash and then flashing your personal flavour of ROM...
Vague but hope it helps..
Click to expand...
Click to collapse
Haven't had the issue in about a week now (crossing fingers) but there was never any text in the top right. I may try reflashing to stock and then back again as you suggested tonight. I use spb backup so whenever the issue occurs im able to just run an exe and restart for full recovery but id rather not rely on that!
Reflashing stock is definitely a good idea, for a while virtually any 6.5 ROM would have a chance of acting up if you didn't flash back to stock first.
Related
Hey all,
Please forgive me if i've missed this somehow, but i searched and searched and no luck. Here's the dealio. What happened is that on my first ever flash attempt to flash our amazing phone, i somehow grabbed the captivate stock rom and flashed via odin.
Yeah. Imagine how that soft brick felt to a noob after mustering the courage...
Well in any case, after a little research and experimentation i moved on, and flashed again and again, but that AT&T WORLD PHONE splash screen (basically the first thing you see after reboot or power on) right before the correct T-MOBILE VIBRANT splash screen just won't go away!
I've flashed several times, after reverting to stock, or over the current rom, and the damn screen just won't go away
I can't say what files are left behind by residual after that first idiotic Captivate flash to cause this, or how they affect my phone. After multiple roms i think we all know there there are no 2 Vibrants alike! So i experience some reported issues and of course all sorts of others with any available here...
If anyone can give me a hand with this issue or point me in the right direction i would really appreciate it. This community is the best!
Thanks in advance,
K~
AFAIK youi have to update bootloader code
try to RE-install 3Button fix for Vibrant - it might replace the logo with Vibrants...
P.S: I am not a pro, if you brick it... then
Hi all, I'm a normal XDA user with my HTC hero.
My girlfriend recently bought the Rogers Samsung Captivate, and had a few issues with it. First the battery life was only lasting half the day. Then one day, it restarted itself 5 times. Then it seemed like it was laggy. At first when she told me about the battery issue I thought, ok maybe if we put a custom ROM on, it may help. So I rooted, put clockwork recovery, then installed Assonance ROM. We seemed to have gotten rid of the lag but the random restarts seemed to persist, then she was having Sms's coming in weird, so I decided we should put it back to stock and get it back to rogers. So i tried doing a restore from clockwork, but it still has the AT&T logo, and when the phone boots, I have a black screen that says no service on the top right, and swipe screen to unlock, but it won't unlock.
All I want is this thing back to stock, no AT&T screen so I can try to warranty this thing.
Thanks in advance for any help, I've done some searching and can't seem to get this thing back to life.
Thanks,
AZ
AbsoluteZero said:
Hi all, I'm a normal XDA user with my HTC hero.
My girlfriend recently bought the Rogers Samsung Captivate, and had a few issues with it. First the battery life was only lasting half the day. Then one day, it restarted itself 5 times. Then it seemed like it was laggy. At first when she told me about the battery issue I thought, ok maybe if we put a custom ROM on, it may help. So I rooted, put clockwork recovery, then installed Assonance ROM. We seemed to have gotten rid of the lag but the random restarts seemed to persist, then she was having Sms's coming in weird, so I decided we should put it back to stock and get it back to rogers. So i tried doing a restore from clockwork, but it still has the AT&T logo, and when the phone boots, I have a black screen that says no service on the top right, and swipe screen to unlock, but it won't unlock.
All I want is this thing back to stock, no AT&T screen so I can try to warranty this thing.
Thanks in advance for any help, I've done some searching and can't seem to get this thing back to life.
Thanks,
AZ
Click to expand...
Click to collapse
Go here....http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I896
Scroll down and you will see a link to the stock Roger's ROM.
Microwave...15 seconds...you don't want to overcook
I have that, i'm trying to install it, but it's taking a long time to start installing update. I've tried reformatting everything, I've tried renaming the Rogers stock to update.zip.
any thoughts on how long it should take to install, or any better instructions on how to get back to stock?
Still stuck at installing update after 15 minutes.
also, is there go instructions on how to get rid of the AT&T Logo, or will the stock rom/firmware fix that?
Ok So, I unzipped the stock firmware and it seems to have installed, but I still get the AT&T logo, and I'm still frozen at the swipe screen to unlock section. I can't swipe at all or do anything for some reason.
AbsoluteZero said:
Ok So, I unzipped the stock firmware and it seems to have installed, but I still get the AT&T logo, and I'm still frozen at the swipe screen to unlock section. I can't swipe at all or do anything for some reason.
Click to expand...
Click to collapse
I'd just like to post that I had this exact same issue when I tried to restore to my original ROM Manager backup, and a solution would benefit both of us.
Auridran said:
I'd just like to post that I had this exact same issue when I tried to restore to my original ROM Manager backup, and a solution would benefit both of us.
Click to expand...
Click to collapse
Did you end up being able to boot ok somehow?
AbsoluteZero said:
Did you end up being able to boot ok somehow?
Click to expand...
Click to collapse
Nope. I'd always be stuck at that black lock screen unable to unlock. After one erase and restore there was a background image instead of blackness, but it didn't go any further. I just decided to stick with Assonance, but that's not really an option for you unfortunately.
so I was wrong right from the beginning, I didn't flash Assonance, i flashed Cognitionv2.3b8. Sorry for the confusion
I clipped this from the above link to the rogers stock rom.
"Be aware when installing AT&T Firmware 2.2 and trying to recover to Rogers stock, you will have a short AT&T display on boot up. One way to remove this is to flash the phone with firmware from a Samsung I9000 model and then reflash it with the Rogers Firmware. This will remove the AT&T logo. However, there is a chance that this method may, in certain circumstances, leave a seemingly random pixlation on screen upon boot-up for the time the AT&T logo was meant to be displayed. A very minor issue and doesn't affect the phone or boot process"
So try to find a stock I9000 rom I guess. The assonance rom is based off the I9000(Or at least that what it says on boot :/). I'm not sure if that will be good enough. I'm running Assonance right now on my fiance's rogers captivate. It's been working great since she has gotten it. So maybe even just flashing Assonance will fix things for you.
As a side note, I returned my x10 with a custom rom on it for warranty and I never heard from them. My understanding(hearsay) is that it doesn't even go to rogers. I'm in Ontario, and I believe it goes to a refurbishing company that is contracted by rogers where they check for water damage.
So I'm not sure where you are located but it may be the same.
(Disclaimer: I'm not saying you WONT get billed for the phone if you send it back with custom rom on it.. I'm simply saying that I didn't and I have heard of others not being as well. Perhaps we were just lucky)
Good Luck.
If you try this let me know if it works, should I ever need to send hers in for warranty.
check your pm
Hi guys,
Gone through about 100 threads these last couple of days, but nothing helps, so have to start a new one.
What happened was that the other day my phone started ringing.
The screen however was black, so I could neither see who was calling nor answer the call.
I let it ring out, then I held the power button so it would shutdown.
Tried to restart it, and that's when the fun started.
The phone got stuck in a boot-loop, only showing the Galaxy S logo (not getting to the animated one).
Left it in this loop for several hours, since I've had problems recently with the phone needing to do this cycle 5-10 times before booting up.
This time it wouldn't boot, however.
I've tried putting the phone in a bag of rice for 18 hours, in case of any moisture inside, not helping.
Then I tried recovery-mode, formatting the whole thing, but I got the following error:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
Found this thread to try to fix the format error.
Got into download mode, but Odin does not recognize the phone, and I started believing all hope for fixing it without sending it in was gone.
I've also tried applying a couple of update.zip's from the SD-card, just to have tried it, but every package got Signature verifcation-error.
Anyway, when I headed to bed last night I left the phone in the boot-loop, and to my surprice, 8 hours later it had booted into first-time configuration.
YES!!!
Configured the phone with language etc., then all of a sudden the animated Galaxy S logo appeared...
And it appeared again, and again, and again for about 15 min., until I unplugged the battery.
And now I'm back at square one, stuck in the boot-loop (not getting to the animated logo)...
I have the latest versjon of KIES, not that it probably matters.
Does anyone have an idea of what the problem might be?
What rom were you using? stock or custom? Maybe it has something to do with lagfix if it was activated... im guesing, im not dev just normal user... Maybe try to reinstal usb drivers.
Just use odin 1.3 reflash official rom , everything would be OK.
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
mortenlm said:
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
Click to expand...
Click to collapse
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
porkapple said:
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
Click to expand...
Click to collapse
Well, I would have if I knew... But stupid me thought that a phone was a phone.
How wrong was I?
Anyway, a little update here (the problem is kind of solved now):
Flashed the phone with 2.3.3 Gingerbread I found on dkszone, after running the steps in the previous mentioned thread.
And the phone started like a charm.
But after a few hours of configuring etc, I managed to insert the SD-card again, and all hell broke loose again...
Come to think about it, thats what I did yesterday too, so I've come to the conclusion that the SD-card is the main problem...
However, now the phone is slow... REAL slow... Kind of like my 1.5 year old HTC Touch Diamond 2 with WP6.5...
It takes up to 2 seconds to open menu items, keyboard etc.
Is there any way to fix that?
Or should I flash it with another ROM?
You mean the external sdcard? Maybe try to format it...
OK, so this is what I've now figured out:
The phone is damaged...
It seems that the internal SD has gone AWAL, and internal storage has somehow created itself on the external SD-card, thus the phone crashed when I switched cards...
When trying to format the USB-storage, I receive error: SD-card has been removed
So I guess I have to ship the phone off to Samsung ASAP...
Hello All,
I'm fairly certain there isn't another thread asking this question, if I overlooked it I apologize in advance. Now to the point, I have a dell streak 7 and I have been having some stability issues with it for about the last week. What was happening is I was running Android 2.2.2 and my system would crash randomly eventually it wouldn't start back up. I tried doing a factory restore several times this didn't work so I re-flashed to restore the original file system and I installed the T-mobile system by mistake. I played around with this for a little bit and every thing seemed fine. So I decided to upgrade to 3.2 honeycomb, I flashed the DS7 did all of the set up steps and started reading about rooting the device (I didn't start any of the steps). While it was sitting next to me in sleep mode I noticed it just randomly reset itself and started booting up. I looked around in it and nothing seemed to be changed, so I powered it off and powered it back on to see if it would freeze up and crash again. it didn't so I put it back in sleep mode and kept reading. then the side lights came on and it froze up. I was able to get it to boot by going into recovery mode and then selecting boot normally. So my question is, is this some sort of hardware issue or something that I am doing wrong? I don't think it's hardware but I could be mistaken. Also, has anyone else had an issue like this and if so is there a known fix? I am going to try re-flashing to the original file system again and replace the restore .img and see if this helps. Also, I'm not sure if my DS7 is the mobile version or wifi only version. I entered the service tag at DELL's website and it said I had the mobile version, however it didn't have the t-mobile start up animation before I flashed it the first time and in the sim card slot there is a black piece of plastic or card (IDK which) lodged in there and it wont come out. Any help or advice on this would be greatly appreciated .
Thanks in advance-Woulfenstien
OK I'm pretty sure i got it solved. what I did was I re-flashed everything. I re-flashed the boot.img, the system.img, and the recovery.img using fastboot and then i re-flashed whole system with nvflash. It's been a couple of hrs. and this has seemed to work so far. I upgraded back to 3.2 honeycomb and rooted the device with no problems so far. If any other issues arise I will post them here along with what i did to fix it. I would also like to thank everyone on this forum who has posted the tutorials, it was a huge help I wouldn't have been able to fix my DS7 with out all of your help.
Thanks again-Woulfenstien
Hi all,
I recently purchased a second hand z1 c6903 (telstra branded), and decided I would start off by loading the iHackers custom rom on. (based off instruction in http://forum.xda-developers.com/showthread.php?t=2439328 and http://forum.xda-developers.com/showthread.php?t=2716182). Now I didn't use it a whole heap before doing this but I didn't notice any issues with the display before starting.
After the first step of downgrading to the Firmware 14.1.G.1.534 the display started going nuts. I suspected something may have gone wrong and started from scratch on another computer and re-flashed the firmware. Problem persisted but everything other than the display seemed to work so I continued rooting the phone, backing up the TA, unlocking the bootload and installing the rom. It all seemed to go fine.
Its hard to describe the issue with the display, its flickering and distorted (tried to make a vid sorry about the quality though https://youtu.be/nyD1o28ipdY)
If you can see in the video it does not do it really in some apps like the calendar and clock, others it does at first then stabilises, doesn't seem to do it at all in the drag down notification menu. Even though its difficult to see the icons, if you know where they are, they seem to respond fine like nothings wrong.
I searched everywhere but couldn't find anyone with a similar issue (May be out there but because the z1 has had such widespread issues with the touch screen thats all I could seem to find).
Was hoping someone with more experience or that has dealt with a similar issue could help in diagnosing the problem or provide a solution?
Thanks in advance
Dean
Wow o.o weird.
Did you flash the latest firmware version before flashing iHackers ROM?
U should try to flash another Kernel. There are many based on stock rom, like FXtrinity and X Honami. try them
Thanks guys.
I didn't flash to the latest, probably should have tried before continuing. Is that something worth trying now (I have never had any issues like this with roms etc I don't know where to start?) I also had flashed to the Kernel.ftf for C6903 (.133) as in the instructions.
I just tried the X-Honami v6 kernal. Still the same.
Anybody have any ideas?
Update:
I bricked it trying to revert back the the telstra branded firmware. Red flashing light. It did vibrate at one stage after pressing the power button but nothing since. Have just been charging it until I get a chance to try and fix it. Doesn't really detect it at all when connected via usb but the usb connection sound keeps going off.