I recently wanted to try moving onto a different build of Android. Before I was using Desire build with hastarin's kernel. I wanted to go ahead and try a Nexus build and replaced the Android folder with the newer one. For some reason after the opening animation and it going onto the lockscreen it vibrates and turns off. Always doing the same thing. I even tried changing to another build and now it's doing it for all of them. Anyone here that can help me figure this out? It was working fine before without a problem. I am using radio 2.15, Dutty's Rom (which is Android friendly), I don't know if I forgot to erase something or what. Please anyone else having this problem at least post if this is happening and if anyone has resolved it please tell me how. Thank You.
Forgot to mention I use an extended battery and that this itself could be the issue. Seems to be solved. Still have the problem, but at least I know why. No one has seemed to solve it
BTW can the mods put this in the FAQ somewhere? It's pretty important and it's somehow nowhere near the 1st post of the HD2 Android FAQ.
I had same problem. when i deleted the google maps cache folder on sd card everything went fine.
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 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?
3rd thread, about 4th rom flashed
constant issues with builds. have gone from stock to:
cm 6.1.3 -apps crashing, random crash notices i.e "phone book has crashed force close" - "the process com.android.phone has stopped unexpectedly"
cm 7 - random reboots, opening browser caused power cycle, wifi issues, lag (thread posted, no solutions at the forefront)
currently on tripnraver pre release. now another issue. no signal what so ever.
original baseband on this xperia x10a is .55. it is suggested to use with bands 52 or 49.
loading either of these basebands. which ive done. doesn't seem to fix the no signal problem. the description states should be backwards compatible even if appropriate bb is not installed on device. yet no luck.
attempting to flash either baseband fails to resolve this problem. currently trying to flash back to stock and try another full reinstall and baseband flash in flashtool.
any ideas would be a great help. having to flash x number of times between roms is getting quite time consuming
thanks everyone.
if you want to stay on the miui rom, you can flash the baseband patch located here and stay on whatever baseband works best for you (I'm on .55 and find it fantastic), then when you load the rom, go to dev tools>bad behaviour>crash the system server.
http://forum.xda-developers.com/showthread.php?t=1011608
Otherwise, I would recommend wolfbreaks cm 6.1.3, as it is the most stable. You must have done something wrong during installation as I never had an issue with his roms.
The only issue I have ever had with any rom is MiUi and thats because I used the wrong baseband. You must be doing something wrong for you to be having problems
if you want, try this flash, it's trips miui pre-final with the baseband patch implemented.
http://www.multiupload.com/KCKE9K2WKN
worked with my .54 baseband
thanks so much for the links to the baseband patches. i remember coming across a thread that posted it but unfortunately forgot to book mark. so im definitely going to go ahead and try with the patch installed. hopefully all works well
each rom ive flashed has been done properly according to instructions. cache wiped, dalvik, and full reset as per menu options in xrecovery.
one way or another i experienced lag for the most part, and as mentioned some random crashes. never had reset on wolfs rom just error messages at times. trips rom worked excellent, smooth and quick. hopefully with the patch implemented everything will work flawlessly
thanks you guys
*Updated
Flashed over rom with baseband patch. signal working. everything running smooth.
except for when using camera zoom. zoom default displays 0x. as soon as the option is selected it spawns an immediate force close
any patches? or similar outcome for anyone else?
i will outline my steps below so everyones up to speed on how i performed this flash.
- flashed back stock in SEUS
- root with one click (success)
- installed busy box (market)
- installed xrecovery apk
- booted into xrec
1. full factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
5. install custom zip from sd card
6. selected trips rom with bb patch implemented
5. reboot
Camera zoom doesn't work in most ROMs yet and the lag you were experiencing was likely just the FW "settling" it can take a little bit and a couple reboots sometimes for the phone to calibrate itself properly.
Sent from my X10i using XDA Premium App
thanks cmoney. maybe ill try my luck with cm7. give it a few reboots and hope for the best. great rom. im really loving trips iphonesque style
clean smooth and quick. everythings working great. hoping the zoom may get fixed soon enough. only other inquiry i have with regards to this rom is the apps2sd.
this feature is essential to myself personally. and it is not working as ive noticed on this rom. ive read a thread with regards to a fix for the last release. i checked the settings for an enable option in case the feature requires being manually set as active but nothing listed. within sd settings state reads as unavailable. if anyone has an answer as to whether this fix will function with the current pre release. ill be going ahead with completeling the flash and reporting what i find back on this thread.
thanks again everyone
Try Wolfbreaks rom. It's very very stable for me. It has cam and everything upto date.
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
thesoundofsilence said:
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
Click to expand...
Click to collapse
works for me on trips newest....
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
thesoundofsilence said:
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
Click to expand...
Click to collapse
I dunno man, it works fine for me, but I copied data from my 0.3.2 xrecovery image, so that might be why. try flashing that apps2sd fix for 0.3.2, should work fine
damn it. i just found that thread. found the links to the fixes. so far ive tried miui32_a2sd_fix.zip. and flashed that over with xrec prior to reboot. which did nothing.
there are two more links so im going to try those two flashes as well and hope that one of them will do the trick. if its working when utilizing .32 patches then ideally the bloody thing would have to work here. thanks for the input though dtox. much appreciated
I don't know what else to suggest man
From the feedback I see in the miui thread, everyone else is reporting it working!
Did you factory wipe, wipe cache partition, and wipe dalvik cache before install? then flash the miui 1.0.zip, and flash immediately the baseband patch then reboot into the rom.
Remember not all apps allow apps2sd so use something like android system info, go into the applications tab click on one, click manage and then see if the option "move to sd" is highlighted. Like I said check a few though, not all apps can be moved
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
thesoundofsilence said:
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
Click to expand...
Click to collapse
Try it again but without the fix...
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
thesoundofsilence said:
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
Click to expand...
Click to collapse
No idea man, like I said it is fine for everyone else so I'm so no big development will arise that will make it function with your phone....
maybe it has something to do with 10a. i dont know. but the point is it shouldn't even be doing this regardless. hypothetically if its froyo and it has apps2sd built in. it should work. its not the way ive flashed. the phone supports it. so my only conclusion the rom must not be as compatible as stated. and from reading different posts about the prev builds sometimes the patches worked at other times they didnt. and also the fact that the rom is claimed to work without the need for a bbpatch. yet without the patch instaled phone caught no single. i guess certain unexplainable glitches can be bound to happen at times but any how ill give it one last go.
if nothing comes out of that then im giving up on that build because it seems relatively hopeless.
lol I'm using an x10a...
Still man you're the only person reporting this. Don't you find that strange? What baseband are you using anyhow?
Hi
Sorry if this has been cleared up in another thread, but I cannot find the answer to this problem.
I am running Gingerbread 2.3 (Cynogen) on my phone via the file manager method. Everything was fine until one day after I booted back into Android after a normal soft reset - The keyboard would keep hitting "Q" no matter what I pressed. I could not open The browser as I would get an error message.
I thought maybe it was the extended battery I was using, so I reformatted my sd card, re booted gingerbread and everything was back to normal.
Then last week it happened again. I dont remember installing anything new. It is also not the build Im sure, because this did happen a while ago on another Cynogen mod I used.
I am pulling my hair out wondering what to do. There is no point in reinstalling it because it will happen at a seemingly random time again.
Does anyone have any clue or suggestions on how to fix this??
Thanks
Frosty1148 said:
Hi
Sorry if this has been cleared up in another thread, but I cannot find the answer to this problem.
I am running Gingerbread 2.3 (Cynogen) on my phone via the file manager method. Everything was fine until one day after I booted back into Android after a normal soft reset - The keyboard would keep hitting "Q" no matter what I pressed. I could not open The browser as I would get an error message.
I thought maybe it was the extended battery I was using, so I reformatted my sd card, re booted gingerbread and everything was back to normal.
Then last week it happened again. I dont remember installing anything new. It is also not the build Im sure, because this did happen a while ago on another Cynogen mod I used.
I am pulling my hair out wondering what to do. There is no point in reinstalling it because it will happen at a seemingly random time again.
Does anyone have any clue or suggestions on how to fix this??
Thanks
Click to expand...
Click to collapse
Maybe it's a bug in the ROM
Try different rom and see if this problem still persists, if yes, maybe a hardware problem related issue
Cheers
There are a few roms with 100% support for the official extended batteries(s). Your best bet is to go with one of them.
Sent from my HD2 using XDA App
Ok first and foremost...I have tried searching
I have been a lurker most of the time here on xda seeing as if I just search and read I'll get most of my answers, but not this time.
Ok some background info first:
TMOUS US HD2 1024Leo
Radio: I'm not 100% sure but I did a task29 that supposedly flashed 2.15.50.14
HSPL: 2.08
MAGLDR 1.13
I bought this phone about a year ago, flashed tytung's Nexus HD2 Gingerbread rom which worked flawlessly for about 10 months or so. One day the phone froze up, pulled battery then inserted and the rom reset to the point where it was like new. Around that time tytung's ICS AOSP thread came alive and I followed it closely watching the updates and what not.
I never installed it until Beta 10. Followed his instructions, set up the partition to 200MBs with a cache of 45MB...45MB for cache because I suspect I may have some bad NAND blocks. Anyways install went flawlessly, everything that was supposed to work, worked...ect ect
Used it for about 24hrs then all of a sudden it froze, when I rebooted I started getting all these random apps crashing(gapps[google apps?], Email, Google Login Services ect), needless to say I task29'd the HD2 and reinstalled everything, worked fine for a day then everything started crashing again.
So after all that info I'm just wondering if someone is experiencing the same problems and/or can maybe lead me in the right direction to figure out this problem.
I know its only a beta but I havent read many posts containing my problems. So Im just left wondering if my NAND is going bad completely and I need a new phone or if theres just something I'm doing wrong.
Before i begin - I have no experience with that Rom, these are just common general ideas.
1) as the rom starts well and then only after a day it breaks, maybe it is because of something (update) getting installed on your device. Have you tried fixing permissions after you encounter the problem?
Or try figuring out which update of which app does it.
2)It also might be the problem of the nand bad blocks, if you suspect it, but if thats the case, there is not really a lot you can do...
No offense, but that's the reason its beta. It doesn't have all the bugs worked out yet.
If you're looking for a daily driver, you should try something more stable.
Hi,
Not sure if you still have this problem..
Have you tried re-installing the ROM again or a different ROM to confirm if the issue is with your phone (hardware) or with the ROM (beta version)?