Hello, I have an AT&T Tilt 2 and when I want to boot off xdandroid 2.2.1 I did the .cab file, soft reset, startup.txt, went into the program, update, boot. It types a bunch of codes, and stops at misc_register(): OK. And it stays there as long as I can see! It won't go any further, however, when I restart the phone, it boots normally in to WinMo. I'm running the stock shipped ROM. Does that have anything to do with it? I'm not getting any errors or anything, just stuck at that. And I know it's not me not waiting, because I've sat it down for 2 hours straight! Please help I really want Android on my Tilt 2.
P.S. I've tried RAR and CAB, also the Reference & Froyo!
Try a clean bundle. Format the card using the HP tool. Full format, FAT32.
Also, try this bundle. It's the newest of the new.
thephoneguru said:
Hello, I have an AT&T Tilt 2 and when I want to boot off xdandroid 2.2.1 I did the .cab file, soft reset, startup.txt, went into the program, update, boot. It types a bunch of codes, and stops at misc_register(): OK. And it stays there as long as I can see! It won't go any further, however, when I restart the phone, it boots normally in to WinMo. I'm running the stock shipped ROM. Does that have anything to do with it? I'm not getting any errors or anything, just stuck at that. And I know it's not me not waiting, because I've sat it down for 2 hours straight! Please help I really want Android on my Tilt 2.
P.S. I've tried RAR and CAB, also the Reference & Froyo!
Click to expand...
Click to collapse
Greetings,
I too have a Tilt 2. In the past I've had many problems with xdandroid and other android ports. I personally prefer to use the manual installation, that way I can control what and where things are placed. I'm currently running the the latest FRX04 release on my Tilt2. Here is how I got it working.
1..Download the RAR package.
2..Format your SD Card (not a quick format)
3..Copy the andboot directory to your SD Card
4..Replace the startup.txt with the one attached here.
5..In WinMo run Haret and let it do it's thing.
6..Once in Android test all your apps.
This worked for me, but until I switched to a newer SD Card I would have random reboots and hang ups.
Post any more complications you have I may be able to help you.
dcmedic said:
Greetings,
I too have a Tilt 2. In the past I've had many problems with xdandroid and other android ports. I personally prefer to use the manual installation, that way I can control what and where things are placed. I'm currently running the the latest FRX04 release on my Tilt2. Here is how I got it working.
1..Download the RAR package.
2..Format your SD Card (not a quick format)
3..Copy the andboot directory to your SD Card
4..Replace the startup.txt with the one attached here.
5..In WinMo run Haret and let it do it's thing.
6..Once in Android test all your apps.
This worked for me, but until I switched to a newer SD Card I would have random reboots and hang ups.
Post any more complications you have I may be able to help you.
Click to expand...
Click to collapse
ooooooh!
I will try this startup for my tilt2!
I am having issues like screen landscaping wrong way sometimes etc.
I will report back. Perhaps we get them to pack your startup in the file under "Tilt 2 ATT GSM" or something!
What SD card did you end up getting?
Thanks!
Prodeje79 said:
ooooooh!
I will try this startup for my tilt2!
I am having issues like screen landscaping wrong way sometimes etc.
I will report back. Perhaps we get them to pack your startup in the file under "Tilt 2 ATT GSM" or something!
What SD card did you end up getting?
Thanks!
Click to expand...
Click to collapse
I already had multiple sd cards, Tiad brought it up to try and change my sd card in a conversation the other day, but I'm using a SanDisk 2GB. My SanDisk 4GB is about 4 years old and believe they do wear out. Older cards aren't good for what we need here, since they are basically or on board device storage.
As for the landscaping, sometimes if a hold the phone flat it will switch to landscape left or right, but I usually do not have a problem when I'm holding it in the orientation I'm needing.
That is the same startup file I have used through out 3 different builds. FRX03, FRX04, and FROYO X. I did have overclocking in there, but come to find out it didn't help, I feel that it probably was the cause of a few of my restarts.
I hope everything works out for you. Report back..
dcmedic said:
I already had multiple sd cards, Tiad brought it up to try and change my sd card in a conversation the other day, but I'm using a SanDisk 2GB. My SanDisk 4GB is about 4 years old and believe they do wear out. Older cards aren't good for what we need here, since they are basically or on board device storage.
As for the landscaping, sometimes if a hold the phone flat it will switch to landscape left or right, but I usually do not have a problem when I'm holding it in the orientation I'm needing.
That is the same startup file I have used through out 3 different builds. FRX03, FRX04, and FROYO X. I did have overclocking in there, but come to find out it didn't help, I feel that it probably was the cause of a few of my restarts.
I hope everything works out for you. Report back..
Click to expand...
Click to collapse
will do!
which exact package are you using now?
link appreciated if not already posted above.
Is it a good idea to delete the ts-calibration file as in XDAndroid2.2Froyo.012211 ?
Any other cleanup measures?
Prodeje79 said:
will do!
which exact package are you using now?
link appreciated if not already posted above.
Is it a good idea to delete the ts-calibration file as in XDAndroid2.2Froyo.012211 ?
Any other cleanup measures?
Click to expand...
Click to collapse
I'm using the same package as arrrrrgh posted in Post #2. I just left the touch screen calibration file that came with the package. No other clean up, other than full format to fat32 with your preferred utility.
dcmedic said:
I'm using the same package as arrrrrgh posted in Post #2. I just left the touch screen calibration file that came with the package. No other clean up, other than full format to fat32 with your preferred utility.
Click to expand...
Click to collapse
OK cool, I will give that load a shot tonight.
As of now I am using: XDANDROID.2.2.1.AOSP.FRX03.21.11.10.FULL_PACKAGE
My screen issues are gone now with those tweaks! thanks so much!!!
Although now this thing seems dog slow.
I took out my line "clock-7x00.a11=500" which I think is just stock anyway.
You do not use this command as you noted issues overclocking. Thus yours should be stock speed too right?
This thing is sloooooow now from earlier with my old 'incorrect' stock config in the RAR package.
I also have the weird typing issue in which I press c once (on the hard keyboard slideout), but cccc appears. I think if I type a word super slow, it works better.
So if i type cingular at a decent pace, it will type out 'ccccingularrr'
Any leads on that?
you may need to delete your data.img file and rebuild it with the new startup.txt. that way android is running at stock speed during the setup. shot in the dark.
Sent from my Tilt 2 using the XDA mobile application powered by Tapatalk
Prodeje79 said:
OK cool, I will give that load a shot tonight.
As of now I am using: XDANDROID.2.2.1.AOSP.FRX03.21.11.10.FULL_PACKAGE
My screen issues are gone now with those tweaks! thanks so much!!!
Although now this thing seems dog slow.
I took out my line "clock-7x00.a11=500" which I think is just stock anyway.
You do not use this command as you noted issues overclocking. Thus yours should be stock speed too right?
This thing is sloooooow now from earlier with my old 'incorrect' stock config in the RAR package.
I also have the weird typing issue in which I press c once (on the hard keyboard slideout), but cccc appears. I think if I type a word super slow, it works better.
So if i type cingular at a decent pace, it will type out 'ccccingularrr'
Any leads on that?
Click to expand...
Click to collapse
Holy crap dude... search. You've asked so many questions that have been answered previously, seriously.
With that said, all the issues you describe are all related to the system_server bug. Just make a call to voicemail (or any call really) and it'll clear up. We're looking into the cause and a potential solution.
dcmedic said:
Greetings,
I too have a Tilt 2. In the past I've had many problems with xdandroid and other android ports. I personally prefer to use the manual installation, that way I can control what and where things are placed. I'm currently running the the latest FRX04 release on my Tilt2. Here is how I got it working.
1..Download the RAR package.
2..Format your SD Card (not a quick format)
3..Copy the andboot directory to your SD Card
4..Replace the startup.txt with the one attached here.
5..In WinMo run Haret and let it do it's thing.
6..Once in Android test all your apps.
This worked for me, but until I switched to a newer SD Card I would have random reboots and hang ups.
Post any more complications you have I may be able to help you.
Click to expand...
Click to collapse
Hello, thank you for the quick response. I did exactly what you said. And once I tap Haret it codes and stops at misc_register(): OK still... Any other suggestions? Thank you agian.
it probably doesn't matter, but is your phone all unlocked etc and able to be flashed with any winmo rom?
using olipro?
just trying to think of any differences with our phones.
Prodeje79 said:
it probably doesn't matter, but is your phone all unlocked etc and able to be flashed with any winmo rom?
using olipro?
just trying to think of any differences with our phones.
Click to expand...
Click to collapse
What is unlocked? Isn't that where T-Mobile would be able to use it?? If not, please explain. Sorry for my stupidness. lol
Is it like jailbreaking and/or rooting?
You do not need to do hardSPL unlocking to use Android from the SD card.
I would imagine with NAND builds you would... but since this all runs off the SD card, no need for HSPL.
Assuming you're using that build that was posted in post #2, it should work just fine - did you make any changes to it, or just extract it to the root of your SD and hit haret.exe...?
thephoneguru said:
What is unlocked? Isn't that where T-Mobile would be able to use it?? If not, please explain. Sorry for my stupidness. lol
Is it like jailbreaking and/or rooting?
Click to expand...
Click to collapse
well mainly just the hard SPL unlocking. Not the sim.
very easy.
see the stickies here: http://forum.xda-developers.com/forumdisplay.php?f=490
mainly:
Hard-SPL Unlocker for Rhodium (AT&T Tilt 2) Released and Updated! New FAQ added!
http://forum.xda-developers.com/showthread.php?t=550131
and flashing...
[Resources] Flashing your First GSM Rhodium Rom (For Noobs)
http://forum.xda-developers.com/showthread.php?t=550540
if you do this don't forget to task 29!
http://forum.xda-developers.com/showthread.php?t=649191
I use the energy rom GTX:
http://forum.xda-developers.com/showthread.php?t=562773
I just backed up all my contacts on my SD card with pimbackup and restored them to the new rom....
Again, to thephoneguru - you do not need to do that ^^.
Only if you want to install a custom WinMo ROM, or if you're flashing to full Android (which is not recommended at the moment!) do you need to do HSPL.
arrrghhh said:
You do not need to do hardSPL unlocking to use Android from the SD card.
I would imagine with NAND builds you would... but since this all runs off the SD card, no need for HSPL.
Assuming you're using that build that was posted in post #2, it should work just fine - did you make any changes to it, or just extract it to the root of your SD and hit haret.exe...?
Click to expand...
Click to collapse
I did not make any changes at all I just put the androot directory on the root of my sd, went to the file explorer and tapped haret.exe. Also, the sd card was just formatted (non quick format) to FAT32.
arrrghhh said:
Again, to thephoneguru - you do not need to do that ^^.
Only if you want to install a custom WinMo ROM, or if you're flashing to full Android (which is not recommended at the moment!) do you need to do HSPL.
Click to expand...
Click to collapse
well we get the picture!
its the only difference I can think of in our phones.
I say give it a shot, it is so simple!
Prodeje79 said:
well we get the picture!
its the only difference I can think of in our phones.
I say give it a shot, it is so simple!
Click to expand...
Click to collapse
How is it so simple? Can you explain the procedure? Thank you.
thephoneguru said:
How is it so simple? Can you explain the procedure? Thank you.
Click to expand...
Click to collapse
He posted a lot of links on how to do it... Post #15?
It won't have any effect on your issue tho. It'll only enable you to flash custom ROMs if you so choose to do so.
Let's focus on your issue. Can you tell me where it stops? Does it always stop at the same place? Have you tried different kernels? Any different builds? Have you tried the newest FRX04 build?
Related
Hey guys. I really , really , really, (can't emphasize that enough), need your help. I flashed my Vogue about a week ago with the 19588 ROM using PPC Geeks Kitchen.
I ended up having to do a warranty exchange because my volume button came a little loose. Well, I went to Flash back to the Stock Alltel ROM, the one that is on the HTC site, thats linked on this page, the one I always use, and now I'm screwed.
It makes it to 43 percent and says theres a communication error. The really weird thing is, I can flash any other ROM to the phone, just not the Alltel ROM. Below , I've listed what I've tried, so you get an Idea. I'm beggin you to help me out here.
*I started out with CokeMan 2.31 , and the 19588 Cooked PPCGeeks Kitchen ROM.
*After the first 5 failed attempt to flash the Alltel ROM, I flashed CokeMan v0.41, and then flashed Mustangs Clean ROM w/o GPS. (this is when I figured out other ROM's will work)
*I re-downloaded the Alltel ROM from HTC's website 6 times, and have tried it on three separate computers and no luck.
*I tried almost ten different ROM's , and each time tried flashing the Alltel ROM afterwords.
*I extracted the Alltel ROM to a folder. Downloaded a blank RUU folder. Copied all of the files from the alltel folder to the RUU folder. (All of the files that were in the Alltel Folder, and not in the RUU folder.) It actually flashed all the way thru, but is now stuck at the HTC screen, and says NO RADIO at the bottom. I just stopped trying, and now am turning to the PPC Gods, you guys. SO PLEASE HELP ME OUT. I have to sent the thing back by monday, or they charge me.
I've always been able to flash to the Alltel ROM from and ROM i've ever used, and never had this trouble before in my PPC life. It always just relocks the phone.
PLEASE PLEASE PLEASE HELP!!!
flash using the sd card
Sounds like you've flashed the f*** out of that phone, suprised it didn't overheat ! Anyways, try the SD method. Also, what radios have you been adding on, or originated with on the ROM you had when you first started.
Also, I'll be quite honest, if I had to return the phone for any reason and couldn't flash back, I'd probably break it to pieces and say it was run over!
how to use SD anyone? please? ive never tried
does it really matter what ROM is on there ...if your having a button problem? You obviously didn't cause the issue because of the ROM.
faroreefer said:
does it really matter what ROM is on there ...if your having a button problem? You obviously didn't cause the issue because of the ROM.
Click to expand...
Click to collapse
Whoa! Never seen this before! If you change the ROM you completely void your warranty.
TweakMan said:
how to use SD anyone? please? ive never tried
Click to expand...
Click to collapse
1. Format your MicroSD card to FAT32 (YES - FAT 32 32 32!! not just plain old FAT) (again, this is not required if your card is already fat32; it is ok to have other data on the card). I have read that the card needs to be 2gb or smaller, though I'm not sure how much truth, if any, there is to that...
2. Extract the .NBH you desire to flash from the exe or zip or w/e put it on the microsd card rename it from RUU_signed.nbh to VOGUIMG.NBH
3.Put the MicroSD card in your phone and Get To the BOOTLOADER screen (camer+power+reset) it should then start updating with the .NBH on the SD card and the procedure should begin automatically.
quoted from here: http://forum.ppcgeeks.com/showthread.php?t=17473
and also, like the champ said, what radios have you flashed?
EDIT: and, which alltel rom are you trying to flash? if you were reverting back to a non-gps/lower radio rom, you did make sure to downgrade the spl properly using these instructions here correct?
* http://forum.ppcgeeks.com/showthread.php?t=24906
or here:
* http://forum.ppcgeeks.com/showthread.php?t=24979
good luck man!!
If you can't flash it, make sure to make it so it can't even start up... you need to completely brick it so it can't get to the bootloader, just not even turn on. Then you can blame HTC and get a new one
derekwilkinson said:
If you can't flash it, make sure to make it so it can't even start up... you need to completely brick it so it can't get to the bootloader, just not even turn on. Then you can blame HTC and get a new one
Click to expand...
Click to collapse
You can't be serious with this, right? The idea here is to fix it, not blame HTC, because I'm sure that would go over real smooth with the carrier.
TheChampJT said:
You can't be serious with this, right? The idea here is to fix it, not blame HTC, because I'm sure that would go over real smooth with the carrier.
Click to expand...
Click to collapse
lol agreed
What's the update?
If it's bricked and you have insurance, wrap your Touch in a damp cloth, put it in the microwave on high for 2 seconds, and voila!
piscesjoey said:
If it's bricked and you have insurance, wrap your Touch in a damp cloth, put it in the microwave on high for 2 seconds, and voila!
Click to expand...
Click to collapse
OH! Another one! After the voila, you call your carrier and say what exactly?
TheChampJT said:
OH! Another one! After the voila, you call your carrier and say what exactly?
Click to expand...
Click to collapse
You say it doesn't work anymore. From VZW, you get one in 1-2 days and you are done. Been there. Done that.
etexter said:
You say it doesn't work anymore. From VZW, you get one in 1-2 days and you are done. Been there. Done that.
Click to expand...
Click to collapse
Well that sounds like a horrible idea! Lol I mean if it has to be done then yeah just go to a GPS ROM and then flash back and it will brick and you can send it in if you have TEP from Sprint or something.. But first I think he wants to FIX the phone not destroy it and start over
My touch is also bricked. It boots to the Sprint logo and stops there.
What do you mean a button problem.
My Touch's green and red buttons stopped working before updating. But the phone still worked. After updating the ROM, even the phone stop working.
Could you please elaborate on this?
faroreefer said:
does it really matter what ROM is on there ...if your having a button problem? You obviously didn't cause the issue because of the ROM.
Click to expand...
Click to collapse
dongdongdog said:
What do you mean a button problem.
My Touch's green and red buttons stopped working before updating. But the phone still worked. After updating the ROM, even the phone stop working.
Could you please elaborate on this?
Click to expand...
Click to collapse
The first post dealt with a broken button.
When the screen on the cellphone goes blank, the cellphone looses the sync and I can't continue upgrading to 6.1. What am I doing wrong?
Plus, *offtopic* I'm tired of removing my SD card to boot my cellphone. Is there a fix for this?
1) When flashing, you have to have the sd removed.
2) No need for a fix since its such a stupid thing.
3)You either ain't flashing correctly or you didn't SDA and surreal unlocked properly. And which ROM are you upgrading to?
Capitan Totti said:
1) When flashing, you have to have the sd removed.
2) No need for a fix since its such a stupid thing.
3)You either ain't flashing correctly or you didn't SDA and surreal unlocked properly. And which ROM are you upgrading to?
Click to expand...
Click to collapse
I'm sorry for not editing my post, because I fixed it. The updater is wrong, it says to press next when the cellphone is activesync'ed. I got tired of trying to fix this and pressed next (While the cellphone WAS NOT activesynced) and it worked :S hahaha. WOW 6.1 (6.1 rose with remade) changed ALOT I'm really happy and the SD card glitch fixed itself.
Glad everything worked out.
Apparently I installed the wrong Energy ROM into my Sprint, I was setting myself to do so when my wife came and distract me so I entered the wrong thread, downloaded and installed it!!
Anybody can give a north!! Please!!
Thanks,
Eladio
eladiogomes said:
Apparently I installed the wrong Energy ROM into my Sprint, I was setting myself to do so when my wife came and distract me so I entered the wrong thread, downloaded and installed it!!
Anybody can give a north!! Please!!
Thanks,
Eladio
Click to expand...
Click to collapse
First I would say bad idea blaming your wife in print. That only spells trouble for you later.
I would say take the SD card out, place a CDMA-based ROM on it, put it back in, go into bootloader, and reflash from the card. NRG doesn't cook radio's into his ROMS so you should be good with just an OS flash.
And just in case you don't know how to flash from SD.
1. Unplug USB cable (not necessary, but KISS)
2. With the phone off, press and hold the vol down rocker then press the power button
3. You'll see the rainbow boot-up, then from there just follow the commands on the screen.
4. After is says Upgrade complete (or something similar, it'll be white text in a blue box in the middle of the screen), press the reset button.
Voila.
Hope this helps.
eladiogomes said:
Apparently I installed the wrong Energy ROM into my Sprint, I was setting myself to do so when my wife came and distract me so I entered the wrong thread, downloaded and installed it!!
Anybody can give a north!! Please!!
Thanks,
Eladio
Click to expand...
Click to collapse
Man up and take responsibility for your own actions, Eladio.
eladiogomes said:
Apparently I installed the wrong Energy ROM into my Sprint, I was setting myself to do so when my wife came and distract me so I entered the wrong thread, downloaded and installed it!!
Anybody can give a north!! Please!!
Thanks,
Eladio
Click to expand...
Click to collapse
I'm wondering just what excatly she was doing to distract you so much that you would flash a GSM ROM on your CDMA device.....
Just follow the instructions in the second post. Next time try to use a proper thread title. "Big Mistake!!! Help" Really doesn't help you any faster!
I could make a small joke about your post but I'm not gonna... ....today....
This thread will probably be closed very soon. You better search before blaming your wife next time
eladiogomes said:
Apparently I installed the wrong Energy ROM into my Sprint, I was setting myself to do so when my wife came and distract me so I entered the wrong thread, downloaded and installed it!!
Anybody can give a north!! Please!!
Thanks,
Eladio
Click to expand...
Click to collapse
You are lucky you only temporarily lost the phone. Other people have worse experiences.
That aside it is easy to fix as mentioned above just put the cdma rom nbh file on the root of sd card and make sure it is called RHODIMG.nbh and then enter into boot loader. The rom will install automatically and you will have your phone restored
cr1960 said:
I'm wondering just what excatly she was doing to distract you so much that you would flash a GSM ROM on your CDMA device.....
Click to expand...
Click to collapse
Please post pics!!!
kimtyson said:
Please post pics!!!
Click to expand...
Click to collapse
lmao...its musta been good
tmotp2jc said:
First I would say bad idea blaming your wife in print. That only spells trouble for you later.
I would say take the SD card out, place a CDMA-based ROM on it, put it back in, go into bootloader, and reflash from the card. NRG doesn't cook radio's into his ROMS so you should be good with just an OS flash.
And just in case you don't know how to flash from SD.
1. Unplug USB cable (not necessary, but KISS)
2. With the phone off, press and hold the vol down rocker then press the power button
3. You'll see the rainbow boot-up, then from there just follow the commands on the screen.
4. After is says Upgrade complete (or something similar, it'll be white text in a blue box in the middle of the screen), press the reset button.
Voila.
Hope this helps.
Click to expand...
Click to collapse
Well, I agree with this causing problems... I was so desperate I wasn't thinking!!! BIGGER MISTAKE!!!
Regarding your instructions it was just perfect, I actually struggled about 3 more hours and none of the ROMs I had/downloaded were working, I thought I really screwed bad... after some more search I found what was happening! The MicroSD card that came with the phone is formated FAT and not FAT32, therefore everytime I was trying it wasn't finding the ROM...
Anyway, all is working now, thanks a lot for the quick response yesterday!
Guys, you're so funny, and helpful too!
I better don't go into details of what she was doing...
I'll do my homework next time, tks for all help!
I have the T-mobile touch pro 2. when i try to boot it, it says directory does not exist. I downloaded the 10/4 one i think. It's the latest blazin one.
Did you format your SD card first? Did you make sure you installed the CAB to your SD? Also, questions like this should go in the Project Android thread.
it is on the SD but it was not formatted. Is it necessary to format?
charburble said:
it is on the SD but it was not formatted. Is it necessary to format?
Click to expand...
Click to collapse
Not always, but it couldn't hurt. All of those 1's and 0's get confused
Alright lol. Ill try formatting it and if it doesn't work I'll post here again
Also if you are from germany and use this android updater:
you need to edit the path from "storage card/andboot" to "speicherkarte/andboot"
it worked for a couple of days, now...i have the same "directory does not exist" problem.
what may have happened?
i can not format the card, because i have to much information on it. anything else?
bogdan_wrc said:
it worked for a couple of days, now...i have the same "directory does not exist" problem.
what may have happened?
i can not format the card, because i have to much information on it. anything else?
Click to expand...
Click to collapse
Eh, something's bungled. You can try deleting (moving, renaming) your data.img, and you know it's possible to copy the data off the card, format it, and copy the data back on to the card, right!??!
Android's still kinda fickle, as this project is still very experimental and changing very quickly. I'm hoping to get to the level that the Vogue got to, but that took a VERY long time!
arrrghhh said:
Eh, something's bungled. You can try deleting (moving, renaming) your data.img, and you know it's possible to copy the data off the card, format it, and copy the data back on to the card, right!??!
Android's still kinda fickle, as this project is still very experimental and changing very quickly. I'm hoping to get to the level that the Vogue got to, but that took a VERY long time!
Click to expand...
Click to collapse
updated with the new startup up utility..and works fine
Where would you go to update the new startup utility
charburble said:
Where would you go to update the new startup utility
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=807117
I tried installing it and rebooting. It gave me the same problem. Am I doing something wrong?
charburble said:
Where would you go to update the new startup utility
Click to expand...
Click to collapse
THIS startup utility.
I installed the startup utility. Wierd thing is, Android worked a lot better before i installed this. The speaker worked, games ran faster, and the whole phone was better.
charburble said:
I installed the startup utility. Wierd thing is, Android worked a lot better before i installed this. The speaker worked, games ran faster, and the whole phone was better.
Click to expand...
Click to collapse
You can feel free to revert to your previous setup, which I assumed never worked. You'll have to actually sort out how you broke it tho, unless you just do a fresh install of a clean build from the archives.
Alright, whenever there is a new update for the Android, the android on my phone totally crashes. It doesn't boot after even if I update. The only way to totally fix it is to redownload and install it.
charburble said:
Alright, whenever there is a new update for the Android, the android on my phone totally crashes. It doesn't boot after even if I update. The only way to totally fix it is to redownload and install it.
Click to expand...
Click to collapse
I wouldn't use the update utility, it causes issues. I manually update, and it always works.
charburble said:
Alright, whenever there is a new update for the Android, the android on my phone totally crashes. It doesn't boot after even if I update. The only way to totally fix it is to redownload and install it.
Click to expand...
Click to collapse
How does it 'totally crash'? Does it do the rhod100 thing of the HaRET loading indicator getting to the end then nothing happens, does it crash during the boot text, or does it crash somewhere else?
Hello guys, I have to ask you a question that I can not resolve for months.
I have a HTC TOUCH PRO, and every kernel I try to always have problems.
At first the device works well and is also very fast, but hopelessly after a while it stops. When you first start can last hours and then crash, but already the second hangs after a few seconds.
I've tried almost every kernel, even the "msm-htc-linux-20101204_005141-package.tar" by the comments that seems to be the best for my device, but nothing. I'm desperate and I do not know what to do.
Can you tell me how to solve this?
Waiting for reply.
Thanks to everyone that I will respond.
I'm not sure what your problem actually is. Sounds like the system_server bug... Make a call to voicemail, phone should speed back up.
Also, the newest kernel is 1253. The autobuild service has fallen behind GIT, see this thread to get the most up-to-date GIT commits.
i must only update with this kernel?
master9 said:
i must only update with this kernel?
Click to expand...
Click to collapse
The kernel (zImage) goes hand-in-hand with the modules file.
Still not sure what you mean tho.
The problem is very simply. Any kernel I use the phone freezes.
This kernel (1253) is very very fast, but nothing, however, the phone freezes.
master9 said:
The problem is very simply. Any kernel I use the phone freezes.
This kernel (1253) is very very fast, but nothing, however, the phone freezes.
Click to expand...
Click to collapse
You say it's fast, but the phone freezes...?
Where does it freeze?
XDAndroid is far from 'stable'...
Us Touch Pro owners can't use 1253 due to certain things reported not working with this kernel. 1243 (i believe 124?) works fine.
djdafreund said:
Us Touch Pro owners can't use 1253 due to certain things reported not working with this kernel. 1243 (i believe 124?) works fine.
Click to expand...
Click to collapse
O___o I did not realize that. All RAPH's...? Do we have logs? I need information man!
I'm not sure about all raph's per-say, but in the other normal FRX03 thread (within the past 4 pages i believe, if that) there was a user or two complaining about something not working (i wish i remembered, maybe data) not working, and i told them to revert back because of issues the new kernel(s) had, and he reported back "thanks, that fixed it." So SOMETHING is wrong for sure with Touch Pro's, but don't know for sure if it effect's diamond user's also. Sorry.
Update- Now i remember, it's http://forum.xda-developers.com/showpost.php?p=10590080&postcount=4072, the screen shifting problem. It shift's the screen over to the left by so many pixels, and get's shifted more and more as your using it. It was actually like 14-15 pages back (too much traffic, LOL), but since i use camera a lot, i am using 1214 (last recent one VC did) as i use his camera build, so i can take picture's. I did witness the screen shifting myself in my separate FRX03 build i have (since just use the camera build though solely). But was using 1241 i believe for my non-camera build.
djdafreund said:
I'm not sure about all raph's per-say, but in the other normal FRX03 thread (within the past 4 pages i believe, if that) there was a user or two complaining about something not working (i wish i remembered, maybe data) not working, and i told them to revert back because of issues the new kernel(s) had, and he reported back "thanks, that fixed it." So SOMETHING is wrong for sure with Touch Pro's, but don't know for sure if it effect's diamond user's also. Sorry.
Update- Now i remember, it's http://forum.xda-developers.com/showpost.php?p=10590080&postcount=4072, the screen shifting problem. It shift's the screen over to the left by so many pixels, and get's shifted more and more as your using it. It was actually like 14-15 pages back (too much traffic, LOL), but since i use camera a lot, i am using 1214 (last recent one VC did) as i use his camera build, so i can take picture's. I did witness the screen shifting myself in my separate FRX03 build i have (since just use the camera build though solely). But was using 1241 i believe for my non-camera build.
Click to expand...
Click to collapse
Oh right, that. Screen shifting seems isolated to the RAPH800 and DIAM500. Probably RAPH500 as well, and I'm not sure what the other DIAM is... perhaps there is a DIAM800, not sure. Either way, seems to only be the CDMA devices.
But of course LOL. I personally love my Touch Pro, but WOULD love to upgrade if i had the money. But yeah, the dreaded shift problem til it's fixed. Not a BIG deal for now, since previous kernals will hold us off til that's fixed.
Nothing, i have the same problem
master9 said:
Nothing, i have the same problem
Click to expand...
Click to collapse
You still haven't properly elaborated on your actual problem. Vagueness will get you nowhere, except frustrate people.
I did not understand what you mean. I'm trying everything I was recommended and I can not solve this problem. I try to re-explain.
The problem is very simple: the phone, any kernel I mountains, after a couple of minutes it stops. I can not wait to give other details because the problem is just that.
Everything works (including wireless), the system is fast but is hopelessly blocked.
When you first start working for hours, just minutes after the second start.
master9 said:
I did not understand what you mean. I'm trying everything I was recommended and I can not solve this problem. I try to re-explain.
The problem is very simple: the phone, any kernel I mountains, after a couple of minutes it stops. I can not wait to give other details because the problem is just that.
Everything works (including wireless), the system is fast but is hopelessly blocked.
When you first start working for hours, just minutes after the second start.
Click to expand...
Click to collapse
Seems to be a pretty big language barrier here... "any kernel I mountains"...?
So has Android ever worked for you? What build(s) have you tried?
Sorry, my fault: "any kernel I mount".
Sorry but i can't speak english very well.
I have try a lot of build: kenya, cyanmod, FRG83.R6 ecc..
but the result don't change.
master9 said:
Sorry, my fault: "any kernel I mount".
Sorry but i can't speak english very well.
I have try a lot of build: kenya, cyanmod, FRG83.R6 ecc..
but the result don't change.
Click to expand...
Click to collapse
What about FRX03? I can't really help you with any build but that one - if you're using a different build, you'll need to get help in those threads. Generally if you just throw up a post like this, use FRX03 (or AOSP, whatever) as your base to test off of.
If it works in that build, but doesn't work in one of the others - then it's that build. If they fail in both builds, then it's a general issue with Android - or, you've just done something wrong .
I also think the same thing because no version I work, all give the same problem.
This is my steps:
1 - Extract all the package (eg superfroyo) to the root of SD, also replace the kernel (of course renaming the new kernel in "zKernel") and also the module, copying them always in the root.
2 - Put the file "startup.exe" HARETSTARTUP of the root and put the file "startup.exe" contained in INSTALL-NPKINSTALL in startups.
3 - Starting in the INSTALL file inside the folder NPKINSTALL.
4 - After the procedure I restart the phone and after i start the file "HARET".
At this point the system starts, it's fast and it all works perfectly but crashes for no reason without giving me the opportunity to do anything, I can only do a soft reset.
Kindly tell me if something wrong in the procedure.
Keep in mind, most neopeek variants require two partiations to be setup as primary (one FAT32 and one EXT2). You might find it a tad difficult in finding someone to help you troubleshoot your process unless you seek help from with-in the thread that you downloaded superfroyo or any other neopeek variants. It is rare to find but then again, you could just as easy try out FRX04 and post your feedback in that thread too. See THIS post for info on downloading the FRX04 update file but you will probably need to downoad THIS package first, then update the system.ext2, rootfs and kernel package after the fact. Stinebd has links for the rootfs in his sig.
n-Joie! (Enjoy)
master9 said:
I also think the same thing because no version I work, all give the same problem.
This is my steps:
1 - Extract all the package (eg superfroyo) to the root of SD, also replace the kernel (of course renaming the new kernel in "zKernel") and also the module, copying them always in the root.
2 - Put the file "startup.exe" HARETSTARTUP of the root and put the file "startup.exe" contained in INSTALL-NPKINSTALL in startups.
3 - Starting in the INSTALL file inside the folder NPKINSTALL.
4 - After the procedure I restart the phone and after i start the file "HARET".
At this point the system starts, it's fast and it all works perfectly but crashes for no reason without giving me the opportunity to do anything, I can only do a soft reset.
Kindly tell me if something wrong in the procedure.
Click to expand...
Click to collapse
Again, you're using funky version. As R^72 said, get help with those versions in that thread.
If you want help, at least try FRX03. You haven't even given it a shot. Then you can update to FRX04, and if that all works - then try something more complicated like a Neopeek build!