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...
Related
ever since i replaced the PCB board in the "chin" on my phone with one that came from a white G1 (mine is black) I cannot keep root for more than a few hours and then ill start getting an acore force close error and i cannot get rid of it.
I have to flash the DREAIMG.nbh file to get rid of the acore error. for some reason if i upgrade to non-rooted tmo newest update, my phone works perfectly fine but then as soon as i root the phone, itll work fine for awhile but then suddenly get that error.
also every time after i root my phone and then i get this folder on my SD that ive never seen before called LOST.DIR but its empty.
I know its not an app error because there isnt anything on my phone other than what came with it.
any ideas?
I have that empty .lost directory on my card also but I have had root for months, normally whenever I got the acore crash, it was just that I did not wipe before a flash though, would just reboot,wipe, flash, problem solved though
i swear ive tried every combination of wiping/installing/flashing and getting root. im not a noob at getting root and flashing roms either..been doing it since JF first came out.
its got to have something to do with the board that i replaced...not sure why that would matter though
I was just saying in my exp, it is weird that a board would that unless somehow it is malfuncting
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?
Hi guys,
I have a problem with my Magic 32B and hope one of you guys could figure out where this all come from.
Since a couple of weeks my magic has become very unstable and I would say I have about 20 to 30 freezes or reboots a day. It suddenly started when I switched from a nightly froyo to another and since then regardless on the ROM I flash I always have the same behaviour (I'm currently on the CM6 RC1).
I tried the following:
- full wipe via AmonRa + format of SD (128 SWAP + 512 EXT + FAT) clean reinstall of a presumably stable rom --> failed keeps rebooting or freezing
- I did a fastboot erase system -w + flash of a clean ROM --> failed
The bizarre thing is it never crashes when the phone is USB plugged on my laptop, therefore I've never seen a logcat showing anything bad ...
Also I can't identify any pattern or scenario which would systematically frag my magic... Even when I install a fresh new ROM, it can work pretty well for as long as an hour but then start being screwed up.
I've spent quite some time on this forum desperately looking for someone experiencing the same troubles but so far unsuccessfully ...
Would you guys have any idea ?
cheers
ZeRoT
zerot said:
Hi guys,
I have a problem with my Magic 32B and hope one of you guys could figure out where this all come from.
Since a couple of weeks my magic has become very unstable and I would say I have about 20 to 30 freezes or reboots a day. It suddenly started when I switched from a nightly froyo to another and since then regardless on the ROM I flash I always have the same behaviour (I'm currently on the CM6 RC1).
I tried the following:
- full wipe via AmonRa + format of SD (128 SWAP + 512 EXT + FAT) clean reinstall of a presumably stable rom --> failed keeps rebooting or freezing
- I did a fastboot erase system -w + flash of a clean ROM --> failed
The bizarre thing is it never crashes when the phone is USB plugged on my laptop, therefore I've never seen a logcat showing anything bad ...
Also I can't identify any pattern or scenario which would systematically frag my magic... Even when I install a fresh new ROM, it can work pretty well for as long as an hour but then start being screwed up.
I've spent quite some time on this forum desperately looking for someone experiencing the same troubles but so far unsuccessfully ...
Would you guys have any idea ?
cheers
ZeRoT
Click to expand...
Click to collapse
Probably other people will say it, but wrong forum.
Also, what ROMs have you flashed after the nightly froyo? Nightly froyos are cautioned, which I'm sure you knew.
yep, I used a couple of FroYo SP French Connection nightlies and then switched to CM V6.0.0-RC1.
(sorry if it's the wrong forum, @admins, please feel free to move it to wherever make sense)
zerot said:
Hi guys,
I have a problem with my Magic 32B and hope one of you guys could figure out where this all come from.
Since a couple of weeks my magic has become very unstable and I would say I have about 20 to 30 freezes or reboots a day. It suddenly started when I switched from a nightly froyo to another and since then regardless on the ROM I flash I always have the same behaviour (I'm currently on the CM6 RC1).
I tried the following:
- full wipe via AmonRa + format of SD (128 SWAP + 512 EXT + FAT) clean reinstall of a presumably stable rom --> failed keeps rebooting or freezing
- I did a fastboot erase system -w + flash of a clean ROM --> failed
The bizarre thing is it never crashes when the phone is USB plugged on my laptop, therefore I've never seen a logcat showing anything bad ...
Also I can't identify any pattern or scenario which would systematically frag my magic... Even when I install a fresh new ROM, it can work pretty well for as long as an hour but then start being screwed up.
I've spent quite some time on this forum desperately looking for someone experiencing the same troubles but so far unsuccessfully ...
Would you guys have any idea ?
cheers
ZeRoT
Click to expand...
Click to collapse
This may not be your problem, but I found personaly that as soon as I enabled swap, my phone became a bit unstable. It was not rebooting itself when I had compcache on. Then I turned that off and switched to swap and now my phone rebooted itself sometimes. For me compcache was noticeably faster but swap multitasks better. So I've kept swap in spite of reboots. I have also found that switching between them either way my phone becomes unstable and rebooted itself multiple times before becoming stable on compcache or at least not rebooting as much on swap.
Sent from my HTC Magic using XDA App
well i had the same issue. nothing helped, i reinstalled the spl, radio, rom, recovery, everything.
the only thing that helped is :
REROOTING YOUR PHONE
there´s no other way.
have a good day.
zerot said:
Hi guys,
I have a problem with my Magic 32B and hope one of you guys could figure out where this all come from.
Since a couple of weeks my magic has become very unstable and I would say I have about 20 to 30 freezes or reboots a day. It suddenly started when I switched from a nightly froyo to another and since then regardless on the ROM I flash I always have the same behaviour (I'm currently on the CM6 RC1).
<snip>
Click to expand...
Click to collapse
I would expect a Donut based ROM to be fine. Which ROMs have you tried since the freezing/rebooting problem started?
The next time it reboots you should take a copy of /proc/last_kmsg and post it here. You can do so with:
Code:
adb shell cat /proc/last_kmsg > last_kmsg.log
Reboot cycle
I'm sorry if I'm in the wrong area, but I also have the same problem. I have a mytouch 3g (32B). I recently flashed it with "Froyo SPF Connection" and that made it reboot just about every 30 seconds. I restored it to the 1.6 Donut rom and it kept rebooting but repeated the process and now it seems fine. The problem is I don't want the 1.6 rom but that's all can have right now since everything else slows it down and freezes it. Please help me solve this problem. I'm opened to any useful recommendations and every help is appreciated.
benjaminb007 said:
I'm sorry if I'm in the wrong area, but I also have the same problem. I have a mytouch 3g (32B). I recently flashed it with "Froyo SPF Connection" and that made it reboot just about every 30 seconds. I restored it to the 1.6 Donut rom and it kept rebooting but repeated the process and now it seems fine. The problem is I don't want the 1.6 rom but that's all can have right now since everything else slows it down and freezes it. Please help me solve this problem. I'm opened to any useful recommendations and every help is appreciated.
Click to expand...
Click to collapse
Eclair ROMs are just as stable as donut ROMs and as fast as donut. Just don't use Froyo till it's stable. Use CM5.0.8 or any CM variant and you should be fine.
I'm having the same problem after flashing the new radio the phone will boot and as soon as its done loading the home screen it will reboot then load the home scree and turn off
Flashed French Connection ROM few days back and have had same problems as above ever sense.. Flash other ROM's and they constantly Reboot. cy 6.0 Working for me now, But only my Nandroid back up of it. Re flashed it fresh and it reboots...
why dont you reroot ur phones like i told you?
This freezing and rebooting problem is weird - it doesn't make sense a lot of the time.
I've developed a ROM based on AOSP 2.2 for the G1 and it also seemingly randomly freezes or reboots.
When it reboots it's usually the result of an ARM9 crash and so far I have tracked it down to a call to a proprietary library function which doesn't return to the correct return address. It seemingly returns to a random address and the consequences of doing so is random. Sometimes it causes a freeze or a reboot and other times it doesn't.
I'm starting to suspect something in the JNI code is causing the problem but it's difficult to track it down.
FroYo SP French Connection is overclocked to 614 by default. My Mytouch (32B) reboots and freezes constantly if i don't turn it down to 576. Try turning the overclock down in set cpu to 528 first then if its stable you can try turning it up a little.
Urgh, I hadn't considered clock speed as a potential problem.
What if some of our phones are unstable at the default Froyo maximum of 528 MHz?
I am (was) in the same situation (Magic 32B). It started with CM6 RC1 first and after it, my nandroid backups got weird too! I always wiped everything and rebooted by myself several times. I never played with overclocking, compcache or ext partition - but after trying other FROYO ROMs as well, even a clean install of CM5.0.8 final was unstable got fc's and rebooted...
So, after one year of trying nearly every ROM out there, i finally made a decision: i went back to my stock rooted 1.5 cupcake!! Yes, 1.5! I never tried this ROM before - even in my first days i immediately switched to sense...
And what should i say? I'm blown away by the speed and stability of this ROM! Unbelievable! ... sad day ... really sad ....
And my decision after that: i will wait for an official FROYO for Magic, which was at least officially announced...
sad, sad, sad...
alutastisch said:
why dont you reroot ur phones like i told you?
Click to expand...
Click to collapse
Well, i think - like my approach - rerooting will not bug down the fault in FROYO ROMs. I hope it will be sorted out, but for me the daily flashing is over for now. I really appreciate the hard work of all the devs and i also donated to some, but at the end of the day i just want my phone and don't want to wait for going to homescreen or missing a call because of the lags...
sad, sad, sad...
akivlin said:
Urgh, I hadn't considered clock speed as a potential problem.
What if some of our phones are unstable at the default Froyo maximum of 528 MHz?
Click to expand...
Click to collapse
Well, I think default for stock unrooted phones is like three hundred something you could try that but it would be really slow.
hudl said:
I am (was) in the same situation (Magic 32B). It started with CM6 RC1 first and after it, my nandroid backups got weird too! I always wiped everything and rebooted by myself several times. I never played with overclocking, compcache or ext partition - but after trying other FROYO ROMs as well, even a clean install of CM5.0.8 final was unstable got fc's and rebooted...
So, after one year of trying nearly every ROM out there, i finally made a decision: i went back to my stock rooted 1.5 cupcake!! Yes, 1.5! I never tried this ROM before - even in my first days i immediately switched to sense...
And what should i say? I'm blown away by the speed and stability of this ROM! Unbelievable! ... sad day ... really sad ....
And my decision after that: i will wait for an official FROYO for Magic, which was at least officially announced...
sad, sad, sad...
Well, i think - like my approach - rerooting will not bug down the fault in FROYO ROMs. I hope it will be sorted out, but for me the daily flashing is over for now. I really appreciate the hard work of all the devs and i also donated to some, but at the end of the day i just want my phone and don't want to wait for going to homescreen or missing a call because of the lags...
sad, sad, sad...
Click to expand...
Click to collapse
I totally agree. I know waiting for the official Froyo for the Magic may take years before it's finally released, but I'm tired of flashing and testing new roms every day without getting the results I want. As a result of this frustration, I will go back to Donut 1.6 for now and wait for the official update. Hopefully 5.1 won't be out before we finally get the update
TJ Gonz said:
Well, I think default for stock unrooted phones is like three hundred something you could try that but it would be really slow.
Click to expand...
Click to collapse
Yes, I will find out the maximum Donut clock speed and test at that speed.
TJ Gonz said:
Well, I think default for stock unrooted phones is like three hundred something you could try that but it would be really slow.
Click to expand...
Click to collapse
I modified the kernel to allow only the following frequencies:
09-12 01:41:12.579 D/setcpu ( 281): Autodetecting Frequencies
09-12 01:41:12.599 D/setcpu ( 281): Frequencies autodetected: 122880 128000 245760
Click to expand...
Click to collapse
Unfortunately the phone still rebooted due to an ARM9 crash.
I've attached a small CM6 RC1 update as a test fix for the ARM9 crashing.
Anyone experiencing random freezing or reboots should give it a try by copying it to your SD card and boot to recovery to flash it.
If you install the test fix but still experience random reboots I'd appreciate if you could upload a copy of /proc/last_kmsg to http://android.pastebin.com and post the link to it in here. A logcat up to the point of the reboot would be very helpful too.
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.
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...