its not bootlooping its stuck at the htc scrren u get after it completes the second boot screen....the staus bar appears then disappears and leaves me stuck at the htc screen
what should i do???
i have tried formatting ext3 partition and reflashing but it never works!
any suggestions????
Happened to me too, i solved it by repartitioning my whole card, i think it's bad to only erase the ext3 when you are hopping builds. Probably from hopping JAC to Drizzy, or maybe it's just the old build to the new HTC dump. I really dunno. but thats what i did and it worked.
I first just turned off my phone and turned it back up. Everything loaded, but i had a 0% chance to recieve messages. So yeah it's important to let it fully load.
Bzerk1 said:
Happened to me too, i solved it by repartitioning my whole card, i think it's bad to only erase the ext3 when you are hopping builds. Probably from hopping JAC to Drizzy, or maybe it's just the old build to the new HTC dump. I really dunno. but thats what i did and it worked.
I first just turned off my phone and turned it back up. Everything loaded, but i had a 0% chance to recieve messages. So yeah it's important to let it fully load.
Click to expand...
Click to collapse
ok thanks ill try this ...gotta backup all my music and apps and all that good stuff first
i just flashed champion and it worked perfectly so it is the new hero dump thats causing my problem
Related
Ok so my G1 is jacked up appariently...
What im running is in my sig, basically what happened is i was using my phone today, the thing was working absolutely fine with no issues whatsoever, but was a little on the slow side, so i figured that i would reboot it to speed it up some
So i rebooted it, the G1 screen came up, everythings fine... Then the blue Android screen came up, everythings fine... Then the Android screen went away and instead of going to home all it did was stay on a black screen and hasent done anything whatsoever, ive tried pulling the battery and rebooting multiple times and it always hangs on this black screen... i wasent even doing anything when i was on it last, it was just a little slow so i thought ide give it a reboot...
any help would be appreciated on how to get my phone back!
Try to boot w/o the cd card. Or try to flash a nandroid backup. Or flash the newest cyan rom 4.0.4.
Sounds like it crashed on you, reboot into recovery, wipe so the whatever the problem was does not carry over and flash a new rom or try a nandroid backup if you got one. Yes this has happened to me and this should work for you
"Theme :: Open Home"
ummm is Open Home an actual theme made for cyan 4.0.2 or are you referring to the app on the market called OpenHome?
I just flashed the latest JAC's hero. Everything seemed fine ( I did wipe cuz I went from CM 4.0.4 ), but now I got stuck at the HTC logo. I don't think I am really stuck cuz I just received a phone call and I answered it fine. I can even unlock the screen by dragging down but after that, it's the HTC logo, I can't get pass ! Please help !!!
Bad flash/corrupt download? You have the correct partitions and radio/spl right?
evilkorn said:
Bad flash/corrupt download? You have the correct partitions and radio/spl right?
Click to expand...
Click to collapse
Yes, I have 3 partitions ( FAT32/EXT3/32mb-SWAP ). I did flashed the Haykuro's SPL so there's hell no way it's because of my redio or SPL. Thanks for replying anyway
Wipe, reflash, it's a bad launcher, well rosie. Might be a bug, if it happens again, change roms
gridlock32404 said:
Wipe, reflash, it's a bad launcher, well rosie. Might be a bug, if it happens again, change roms
Click to expand...
Click to collapse
Well I don't think it's a bootloop since all the buttons light up and the phone went to sleep ! Never had this before, it's just weird though
It's not a bootloop, I just told you what it is, I had it happen on a cyan rom with the advance launcher
gridlock32404 said:
It's not a bootloop, I just told you what it is, I had it happen on a cyan rom with the advance launcher
Click to expand...
Click to collapse
It's just hanging there on the HTC screen ! What do you suggest ? I read from the development section and they said it took a while to get it booted up the first time
te_quiero_forever_girl said:
It's just hanging there on the HTC screen ! What do you suggest ? I read from the development section and they said it took a while to get it booted up the first time
Click to expand...
Click to collapse
that is correct how long did you let it sit? It can take up to about 15 minutes to get the setup screens.
dude it just takes a while for your phone to get used to hero. this happens every time i flash one but after half an hour it gets hella fast. give it time
Thank u guys, I waited patiently and the phone finally booted up ! My only concern is that I just reformatted my SD to get 96 MB SWAP. I tried to upgrade to ext3 by typing upgrade_fs but when I pressed print to double check, it was still ext2 =.=" Any suggestion ?
Nvm, I did it though ( it was just a bad mistake when I entered the script in parted )
For some odd reason everytime I try to install the cyanogen rom v4.0.4 I believe its one of the stable ones, I do everything to root my fone and install the rom and my fone says its done w the updates and to reboot it and when I do it stays @ the g1 screen. Now I take the battery out and press the cam and end buttons to reinstall the dreaimg to take it back to rc29 state. When I power it up it works just fine the lil android dude pops up and i put in my info and then just redo the steps to the cyanogen rom and for some reason my fone will install everything I will assume properly and i go to reboot it and it stays on the tmobile g1 screen.
I need help! I have tried and tried and Idk what to do now.
This all started bc I deleted something from the cm updater and my fone hasnt worked since...if ne one can help me plz email me @ [email protected]....
Thanx!
SekSayLiLRaver said:
For some odd reason everytime I try to install the cyanogen rom v4.0.4 I believe its one of the stable ones, I do everything to root my fone and install the rom and my fone says its done w the updates and to reboot it and when I do it stays @ the g1 screen. Now I take the battery out and press the cam and end buttons to reinstall the dreaimg to take it back to rc29 state. When I power it up it works just fine the lil android dude pops up and i put in my info and then just redo the steps to the cyanogen rom and for some reason my fone will install everything I will assume properly and i go to reboot it and it stays on the tmobile g1 screen.
I need help! I have tried and tried and Idk what to do now.
This all started bc I deleted something from the cm updater and my fone hasnt worked since...if ne one can help me plz email me @ [email protected]....
Thanx!
Click to expand...
Click to collapse
try flashing another build. or wait about 15 maybe 20mins and see if goes away. or just do wipe... or i bet its your sd card try getting to the point where it hangs take out the sd card and then turn it on again.
The first boot after each flash or dalvik-cache dump will take a long time. Just be patient.
Fingerlickin said:
The first boot after each flash or dalvik-cache dump will take a long time. Just be patient.
Click to expand...
Click to collapse
Yes a real long time, right fingerlickin. lol
But if you loaded RC29 back then your gonna have to reroot.
I would suggest wiping if you issue isn't fixed by waiting. I've had to wipe a few times jumping between Experimental and Stable builds mainly because of big Donut differences in the build's.
Fixed???
I think it may have fixed it self, I had my friend look @ it and I had taken the sd card out of it and showed him what happened and he left it alone and it came up w/ an update now he did and its working now like normal...SOoO im scared to try again jus bc i dont wanna f*** it up again but Im stubbern and w/ the info ive learned so far on all these sites I just may do it all over again.
Use THIS guide next time.
Fingerlickin said:
Use THIS guide next time.
Click to expand...
Click to collapse
Show off.
And then use this to partition your card.
http://forum.xda-developers.com/showthread.php?t=535914
I quess I'm a show off too.
Cyanogenrom not working???? HELP!
For some reason every time i dl the cyanogen rom on my g1 it doesnt work i do everything have followed every step and it doesnt work....but i downloaded jf just to see if it worked and it did but im still wondering why this cyanogen rom 4.0.4 doesnt work??? [email protected]
Hi,
So I have been facing this problem for the past 2 month, my SD Card has been getting corrupted alot lately. ONLY EXT partition though, the FAT partition remains intact. I never faced this problem back when I was using JF 1.5 (Long back) This only started happening a while after I started using AOSP 1.6 (With Expansion). Later on I flashed ADP 1.6 , I thought it might be something to do with that ROM. But unfortunatly I was faced with the same result. It happened just 10 min. ago . My phone was working absoloutely fine, I had received a call and then 20 min. later I wanted to grab an app from the market and my phone just completely Froze........I knew it had ****ed up. It restarted Automatically and as usual all Apps are gone as a result of the corruption.
Sometimes, repairing the parition from the recovery console solves the issue, but thats only SOMETIMES. mostly I have to restore the backup from BART or NANDROID . (Which also never restores right away, but after wiping everything on the phone first !!!!!!!! :S)
Please help me out if you have ANY idea whats causing this!
Thanks.
i suggest backing up what you can.. then.. try a fresh start by formation the sdcard and repartationing and before install all your apps back.. try a few out and see if get the same thing.. if then it may be time for a new sdcard
Thanks for the suggestion mate....but I have formatted the card all the way back to RAW mode and repartitioned it again and did a fresh install of everything.........same result. Its not app related. If it was , it would have happened the same time I run that specific application, but it just happens randomly. A new SD Card is the only other possible reason. I will buy one and try :S
Thanks anyway for your help.
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.