I've had my G1 for almost a year now, and have flashed almost every rom out there on it. For the last month I've been sticking with Cyanogens most recent builds. The other day the phone shut off then when i powered it up it wouldnt boot, it wouldnt go into recovery either. The only thing i could do is enter bootloader. So i flashed one of my backups, I noticed the recovery image was gone as well so i flashed that back too. 2 hours later the same thing happended again. Has anybody encountered this? Any thoughts other than sending it back to T-mo (which i plan on doing if i have no other options)?
Sounds to me like you may have flashed 1 to many roms. Your NAND may be corrupt or just dead and sending it to Tmobile or repalcing the motherboard
I've been flashing roms left and right since CM left to find something just as good. Unfortunately I haven't found anything as good! CM your the man. I've flashed JF, Akirah, JacRom, Jacheroski, & CM multiple times each. Sometimes 4 or 5 times a night. Annoying yes, but I need my phone functioning a certain way.
Hope my phone isn't on the way out! Just got a 8gb micro!
Not really sure about the relevence of that last post but whatever.
I'm not sure about the memory being corrupt, if it were I would think I'd get an error when flashing, but maybe. Anyone else have any ideas?
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.
All,
I received a replacement N1 yesterday from HTC as my previous one developed an earpiece issue. After unlocking the bootloader for the first time, it seems that the phone is overheating and randomly rebooting. I reflashed to stock, with the only exception being the unlocked bootloader using a guide found on this forum.
This was my first experience unlocking the bootloader and trying to flash a rom. I've attached a logcat to see if any info can be provided.
Thanks.
EDIT:
N1 - 1 day old HTC refurb
2.2.1
FRG83
Baseband - 32.41.00.32U_5.08.00.04
Kernel - 2.6.32.9-27240-gbca5320
Is the phone actually getting hot?
This is why I don't get why people get a phone and IMMEDIATELY start loading custom ROMs and such on it.. Use it stock for a few days to make sure it's good.
No it's not getting overly hot. My original N1 got much hotter.
Its my fault for not waiting, I do realize this.
I did wait 6 hours or so, but I know it wasn't enough. Got a bit anxious to load CM6.1.
I had first accidentally loaded Insecure boot which made the rebooting much more common, but went back to stock, and loaded superboot. Everything was fine for a little while, then the rebooting started again.
Just trying to see if I can figure out the issue before giving HTC a call.
etacv said:
No it's not getting overly hot. My original N1 got much hotter.
Its my fault for not waiting, I do realize this.
I did wait 6 hours or so, but I know it wasn't enough. Got a bit anxious to load CM6.1.
I had first accidentally loaded Insecure boot which made the rebooting much more common, but went back to stock, and loaded superboot. Everything was fine for a little while, then the rebooting started again.
Just trying to see if I can figure out the issue before giving HTC a call.
Click to expand...
Click to collapse
when i got my nexus back in early january, i dont think that i waited more than a hour before i unlocked the bootloader anyways, your phone seems fine. iy could just be the stock rom you flashed or kernel panics(i doubt). flash cyanogenmod and see if you still get the reboots. unlocking the bootloader doesnt have anything to do with a phone overheating and rebooting. besides, what is overheating? how hot does it get? ive gotten mine to 49C(120F) before
Well that's the thing, it really hasn't gotten that hot. I was just assuming it could be related as it was rebooting after sitting on the charger for a while or trying to download multiple apps from the Market. I was able to get as far as downloading ROM Manager and was part way through the CM6.1 download when the reboots from hell came back.
I used the Signed Passion FRG83 images to reflash.
I'm now attempting to format the SD card to see if it changes anything.
etacv said:
Well that's the thing, it really hasn't gotten that hot. I was just assuming it could be related as it was rebooting after sitting on the charger for a while or trying to download multiple apps from the Market. I was able to get as far as downloading ROM Manager and was part way through the CM6.1 download when the reboots from hell came back.
I used the Signed Passion FRG83 images to reflash.
I'm now attempting to format the SD card to see if it changes anything.
Click to expand...
Click to collapse
it sounds like youre stressing the phone(kernel). try to download 1 thing at a time for now. are you overclocked by chance?
I am not. The phone is bone stock at the moment.
Hm, it looks like i'm on FRG83 not 83D. The SD card is having some issues unmounting and i'm not receiving the OTA update to 83D
Yes - it is overheating!
My original phone did not have the problem. Every replacement phone I got from HTC crashes after 5 minutes or less on every application that made my original phone warm to the touch.
Applications that cause this:
RoboDefense
Tower Raiders
Speed Pi (run multiple times)
Curling
I am trying to get HTC to send me a 3rd replacement!
So as an update I formatted the SD card, and it seemed to have helped for a while.
I had the phone in the charger last night and was speaking on the phone for about 10-15 minutes until it started rebooting again. This time it was stuck on the X so i had to remove the battery.
Not sure what's going on...
So looking through the logcat's i've noticed these lines as failed:
E/Zygote ( 58): setreuid() failed. errno: 17
W/DevicePolicyManagerService( 78): failed parsing /data/system/device_policies.xml java.io.FileNotFoundException: /data/system/device_policies.xml (No such file or directory)
D/SntpClient( 78): request time failed: java.net.UnknownHostException: north-america.pool.ntp.org
I'm not sure if it means anything.
The firmware was downgraded to FRG33 and OTA updated to FRG83D
Will probably be sending this back and hoping the unlocked bootloader won't make it cost a fortune to repair...
This Bell I9000m that this wonderful place helped me figure out how to toss CM7 Nightly into Just had a melt down this past week I need to figure out if I'm boned or not.
I was pulling my media off the internal SD card with Teracopy the night before it all happened in usb mass storage mode and ever since the data was pulled. Icons on my desktop would only start displaying AndroidMarket like logo's and not launching anything. So i would reboot the phone to see if it was just acting silly and it would only get worse.
So I tried factory resetting and clearing all the cache's via CWM bootloader than load the OS to no avail the system simply stopped booting so I tried installing via zip the original nightly that I had left on the internal SD that was a signed release... The install didnt pass the signature check.
At this point I've just put trying on hold to come and ask around here. Am i screwed or am I just around the corner from having my damn phone back.... again .... I need ideas or solutions to this problem.
***UPDATE***
Bell has sent the phone back with the note on the file, "Replaced Major Component" I cant even begin to imagine what that means. Besides everything is apparently less broken? Although i was recording a meeting in full 720P and it decided to randomly stop recording at 47 minutes without any apparent reason.
If anyone reads this and comes up with any ideas as to what may be able to be done let me know please.
I'm trying EZOdin and easybase but the format does not like to work regardless of the PIT file i use it never seems to play well. But im guessing its probably a good idea to start fresh.
Try regular Odin and see what it says but if you internal SD is hooped it will still flash but it won't boot. You are trying the EZbase Froyo 3 part file with pit?
You could try a stock rom also but note you may need to add a DBdata file to the stock rom if you repartition as you need a db data file and it is not included in jl2 or kc1. I guess kies used the existing one from eclair and that is why it is not there.
It sounds like it could be a dying SD card (especially the heavy file use just before issues started). Have you ever had to replace your handset yet?
G
Bell has had my phone for service twice the first time they charged me 60$ for some reason and the second time they did not.
But both times they just reloaded the phone and returned it to me even though both times were similar problems its like they're just trying to avoid having to deal with giving me a replacement.
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