hey guys, just wanted to ask if somebody has experienced something similar..
i had jacxhero running on my 32a without problems. tonight i had the phone on the charger, and in the morning it turns off everytime after the first splash screen. i can access the bootloader mode etc normally, just loaded cyans rom and it works. but...why this sudden inusability? i havent added any program or changed settings for the last 2 days or something...
I had the same problem but with a different ROM. It was the TIM ROM which can be found in the Sapphire Android Developement section here at Xda-Dev. I'm not quite sure if it's a nandroid backup or if it's an Update.zip, but as I had it installed it seemed to be the exact same ROM my device has been shipped with and it read the same numbers in the About-System dialog thingie and so on, it was like if it was the shipping ROM.
Always after about a day of usage or so it suddenly froze though, then the device reset itself and then endlessly looped at the bootscreen. Very annoying. It didnt happen with any other ROM since then...
Mineee..
That's weird..
But, you had any data connection?.. maybe it tried to update something!
Mine started rebooting after entering on suspend mode(not on the splash screen)! The program settings from the overclock just was pulled after I run out of battery (with the "forced" reboot) and started making conflict with the specs of the myhero rom.
Whats the developmental aspect of this thread??
None.........so please post in General.
Warning given.
seems like i got more problems since this "crash"
after reflashing to cyan after this startup error and then reflashing jacheroski 1.4, im able to load hero roms like jacheroski 1.4 on my magic and they work fine, but im not able anymore to load any roms without hero kernel it seems..
i tried with several roms like different versions (working before versions!!) of cyanmod, hofo,..they all loop at the last splash screen or stay black when it should come to the actual os(one step after the last splash).
am i "doomed" to stick to hero roms forever?^^
im using eng spl .2005...should i try to reflash something? or have you guys got any other ideas?
Related
have a tmo us hd2
had a past version of android with sense it worked fine. tried a different and got the pause at jumping to kernel so tried a clean version, it worked. ive booted it plenty of times, then tonight it stopped working
so im trying froyostone with sense and now it wont boot either
im on omega v7 newest and radio 2.1.5.28_2
I was on the same problem, i think you have the android files directly on your SD Card? So that is the problem, put them in a new folder android.
That helps me, the first boot was by me also possible, but after that all reboots end in "jumping to kernel"
nope. theyre in the android folder.
and i just tried switching to the 2.12 radio
the strangest part is that is was working the past few days and earlier today...
id understand a certain build not working but why would it randomly stop working.
Have you made, since this problem more reboots. I have on my HD2 sometimes that i must boot 2-3 times to come up
yup, tried multiple reboots and both radios
have you solved a problem? I've similar problem. Each time I turn on the phone - I'm getting this error. Sometimes it helps to remove "cache' folder and some others and restart twice or may be 3 times. But no working 100% solution.
My Results
ppp vr.
Market ok
WIFI ok
BT ok
whitout freezes
little bit more sensitive touch screen
Very good job, DEV team you are masters
When I'm getting stuck at jump to kernel, I normally remove and reinsert the sd card when I booted into WM and most of the time that fixes it.
I (and other members) have found that "Jumping to kernel..." freeze occurs when one is using Windows for a period of time. The solution is usually to re-boot and once Windows loads *immediately* boot into Android. This has not failed me yet! Before I was like you, wondering why sometimes I get the freeze and other times I don't...but a fresh boot into Android solved my issue.
Hope this helps.
have you changed the kernal lately or switched any file , or renamed anything
have you tried changing the startup.txt file? look around for that solution..it has been posted here many times.
I would give you a link but I am posting from my cell so it would be a little difficult.
Sent from my HTC HD2 using XDA app on darkstone froyo sense v2
Hey all, been poking around the forums and trying out various WM and Android ROMS and they all seem to work beautifully, kudos to the devs.
I seem to be running into a bit of a problem though.
My phone is an MP6900 (Vogue 100) from Bell. And while the roms work great, the second my phone goes into standby mode (when not attached to my comp) the phone resets.
I have tried four different roms, two android and two WM and the problem persists.
Also hard resets, battery removal etc etc to no avail.
I also tried to roll back the radio as that got updated when I went to my stock rom previously.
And to boot I can't seem to flash back to the stock ROM anymore, while I was able to even just yesterday. I get Error 262, for whatever reason.
I was wondering if anyone else has run into this issue and could point me in the right direction.
And I did a search on the forum (pre-registration) but couldn't find anything, sorry if this has been brought up before.
Again, great work on all of the ROMs! I had no idea phones had come this far. (Sad to say but true lol)
JustinHTC said:
Hey all, been poking around the forums and trying out various WM and Android ROMS and they all seem to work beautifully, kudos to the devs.
I seem to be running into a bit of a problem though.
My phone is an MP6900 (Vogue 100) from Bell. And while the roms work great, the second my phone goes into standby mode (when not attached to my comp) the phone resets.
I have tried four different roms, two android and two WM and the problem persists.
Also hard resets, battery removal etc etc to no avail.
I also tried to roll back the radio as that got updated when I went to my stock rom previously.
And to boot I can't seem to flash back to the stock ROM anymore, while I was able to even just yesterday. I get Error 262, for whatever reason.
I was wondering if anyone else has run into this issue and could point me in the right direction.
And I did a search on the forum (pre-registration) but couldn't find anything, sorry if this has been brought up before.
Again, great work on all of the ROMs! I had no idea phones had come this far. (Sad to say but true lol)
Click to expand...
Click to collapse
Sounds like a dying battery to me.
It worked fine in the original Windows though so that's why I am a bit baffled.
what happens if you put your device in bootloader and try to flash to stock? Error 262 is a connection error. basically happens whenever some event interrupts the flashing process (a dead battery will cause this). If you haven't yet, try to flash to stock via the method in this post (bootloader and then flash)
Tried that, didn't work. Just gets to 31% and pops 262 no matter how I try to do it.
The odd thing is though that I can flash any other ROM just fine.
Would reformatting the SD card work?
Figured it out. I used the 0.41 ROM to unlock the phone which was causing the issues. I reflashed with the 2.3.1 and everything works fine.
JustinHTC said:
Figured it out. I used the 0.41 ROM to unlock the phone which was causing the issues. I reflashed with the 2.3.1 and everything works fine.
Click to expand...
Click to collapse
0.41 was reportedly having tons of issues, you should have started from there
Glad you got it working.
Hi
I don´t really know what happened, but I was playing around with recovery roms and now the radio does not work (it does not register on network).
After whatever I did (cant really remember any more), my phone when it starts says Samsung Galaxy S GT-I9000 and it didn´t do that before when it worked.
The phone is a Vibrant, T-mobile branded SGS.
When I go into recovery mode, it says it is ClocworkMod recovery v2.5.1.2.
Also it´s really wierd, since it shows two bars for a couple of seconds when waking it up - and then it shows the icon for no connection.
Any tips on how to fix this?
mikasjoman said:
Hi
I don´t really know what happened, but I was playing around with recovery roms and now the radio does not work (it does not register on network).
After whatever I did (cant really remember any more), my phone when it starts says Samsung Galaxy S GT-I9000 and it didn´t do that before when it worked.
The phone is a Vibrant, T-mobile branded SGS.
When I go into recovery mode, it says it is ClocworkMod recovery v2.5.1.2.
Also it´s really wierd, since it shows two bars for a couple of seconds when waking it up - and then it shows the icon for no connection.
Any tips on how to fix this?
Click to expand...
Click to collapse
Well since you do not indicate what rom you are running I would suggest Odin back to stock and start over. Sounds like you might have flashed the wrong rom for your phone since you see the GT-I900. You could try to flash a rom like Nero V3 over your current rom first and see if that helps. If you do and still have issues I would still suggest Odin to stock and start fresh.
so wierd
changing to Nero worked.
And I tried like 4 ROM-s and they didn't work (and I have been flashing roms for about 2 years now).
thanks! But I feel like a total noob now ha ha
Hey guys!
Got a little problem here!
Here's the situation, I'm perfectly able to flash CM6.10 (? - The latest stable for Wildfire anyway), but I've had no luck when trying to flash CM7. Either, it gets stuck at the white HTC splash after flashing and rebooting, or it gets stuck at the CM splash screen. The arrow just stops moving around in circles and freezes!
Not completely sure what this could be, I clear everything before I flash CM7 so ... And I ofc admit that I'm no sort of expert in this area, as almost every single flash has been perfectly fine to me, so I thought that you guys could figure this one out .
Regards
Try flashing kernel v4.1 from the HCDR.Kernel thread from the Wildfire Android Development Zone. Since you say you have cleared everything as stated by the first post in CM7, guess I wont be going into that.
I actually tried that as a last resort before going to bed yesterday, and that solved the problem! So thanks anyway, you were right !
Later on I installed the Gapps for CM7, but then when i booted my phone, i got the "Low Memory"-warning that wants you to remove some apps, and all the apps started to crash all the time. Especially the browser, not entirely sure of what's causing all this!
Hi,
I had the same boot problem and 4.1 also fixed it for me. I've not had any low memory issues but I only really have the google applications... One problem I do have is that I don't seem to be able to pair with any Bluetooth devices, I just don't get long enough to type in the PIN!
Can't post a report on the dev thread as I'm new here...
Andy
PS Which 6.10 have you been using? Did you have any Bluetooth issues?
Hey guys,
My situation is this, I bought a HD2 from ebay and it had no rom on it at all, So like everyone else here I flashed the stock rom and it worked perfectly except for one freeze up that I can remember.
Then I continued looking through the forums and found that Android could be flashed onto NAND so like everyone else I did it.
After about two days of use the phone started freezing and shutting down every time I went to play an app for more than five minutes.
The problems I have now -
I can't re install the HD2 stock rom (2.10) because it gets stuck at 8% and decides to give me a 204 error.
I tried re installing the HD2 stock rom (1.48) and that just leaves me frozen and hanging at startup
Now in a last ditch effort I've used task29 on my device and then install stock rom but I still get stuck at boot screen. So I then flashed this Version 6.5.3.1.4b custom rom
So currently my device is useless.
I really would like Android 2.2 running smoothly on my device again so any help is welcome.
Device information -
Hardspl: 2.08HSPL
Radio: 2.15.50.14
MAGLDR 1.13
Some pictures of my device.
Uploaded with ImageShack.us
Uploaded with ImageShack.us