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.
Related
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 got my Vogue late 2008 and unlocked it and have had many different ROMs on it. Until recently, I was running NFSFAN's 6.5 v1 ROM. I *cough* got mad at my phone because it was not responding and pushed hard on the screen *cough*. Happens to everyone right ? Anyway, now the screen is all white with a bunch of lines on the left, Verizon is shipping me a new one. Problem, or not, is I told them I had no thrid-party apps on it, which I do, and I have unlocked it and put a custom ROM on it, illegal w/ Verizon right? Can I factory reset or something to get WinMo 6.1 back on it so they don't get mad if indeed they can get it working? Note the screen does not work at all.
EnterpriseNX01 said:
I got my Vogue late 2008 and unlocked it and have had many different ROMs on it. Until recently, I was running NFSFAN's 6.5 v1 ROM. I *cough* got mad at my phone because it was not responding and pushed hard on the screen *cough*. Happens to everyone right ? Anyway, now the screen is all white with a bunch of lines on the left, Verizon is shipping me a new one. Problem, or not, is I told them I had no thrid-party apps on it, which I do, and I have unlocked it and put a custom ROM on it, illegal w/ Verizon right? Can I factory reset or something to get WinMo 6.1 back on it so they don't get mad if indeed they can get it working? Note the screen does not work at all.
Click to expand...
Click to collapse
You should be able to just put it into bootloader (by pushing power,camera, and soft reset button) and then flash your stock verizon 6.1 rom. That would erase all your apps and put it back to how it was when you bought it. Though it would still show that you have the phone unlocked with imcokeman in your bootloader..
You can't drop the phone because that would show cracks.
You can't make it wet because that's detectable.
Most people forget, this is an electronic device and there is 1 easy fix.
Put a big magnet... I mean BIG magnet next to it for about a minute or two.
No visible/obvious damage
But that sucker will definitely be wiped
Barogi44 said:
You should be able to just put it into bootloader (by pushing power,camera, and soft reset button) and then flash your stock verizon 6.1 rom. That would erase all your apps and put it back to how it was when you bought it. Though it would still show that you have the phone unlocked with imcokeman in your bootloader..
Click to expand...
Click to collapse
To add a few things to what Barogi is saying...
You can flash back the device to WM 6.1 stock from Verizon. Flashing another rom is not illegal, but it does void the warranty since you need to hardSPL to do that. So, even if you did take it back to stock, you have the issue of relocking.... (not really an issue, but..)
Do as Barogi suggested and make sure you hard reset the device after you flashed (just in case any programs survived the flash). After you are done, simply download this and run it. That's it, problem solved...
Good luck!
egzthunder1 said:
To add a few things to what Barogi is saying...
You can flash back the device to WM 6.1 stock from Verizon. Flashing another rom is not illegal, but it does void the warranty since you need to hardSPL to do that. So, even if you did take it back to stock, you have the issue of relocking.... (not really an issue, but..)
Do as Barogi suggested and make sure you hard reset the device after you flashed (just in case any programs survived the flash). After you are done, simply download this and run it. That's it, problem solved...
Good luck!
Click to expand...
Click to collapse
just to let you know it seems your link is broken.
Barogi44 said:
just to let you know it seems your link is broken.
Click to expand...
Click to collapse
Ahhhgggrrr! Why are all my links coming down? Damn it! I think I have it at home, I will upload it later....
Thanks barogi! I can always count on you
egzthunder1 said:
Ahhhgggrrr! Why are all my links coming down? Damn it! I think I have it at home, I will upload it later....
Thanks barogi! I can always count on you
Click to expand...
Click to collapse
haha welcome!
OK....long story short...finally decided to delve into rooting and custom roms. Flashed CM6 yesterday and everything was going great. Then suddenly yesterday evening as I was swiping between home screens on my device everything froze, and I have been trying to recover ever since.
Anything I flash now just freezes, and i have a touch panel-fail so even when i do get a rom to boot i cant actually get into set it to usb mode or anything.
using bootloader i can not get it to connect using the adb driver so that I can push via adb.
about an hour ago I was successfully able to run the latest RUU and it ran successfully, but device is still way laggy (takes 15 minutes to boot) and no touch screen.
Any help would be greatly appreciated!!! don't know where to go from here. From what I have read its not bricked because I can get into Bootloader and Recovery???
Just a shot in the dark here, but it sounds like since you're stock now it's an actual hardware failure.
lil-dice said:
Just a shot in the dark here, but it sounds like since you're stock now it's an actual hardware failure.
Click to expand...
Click to collapse
Is there way I can verify that the RUU did indeed flash *EVERYTHING* back to stock?
It seen like you have a HARDWARE issues, Re-Boot the Stock Rom. Call Sprint and explain what's going on with your phone, please *DO NO'T MENTION YOU ROOTED YOUR PHONE* Tell them you try to wipe your phone and it was really laggy before you wipe, since you gonna Re-Boot the stock rom the phone is going to get UNROOTED, I know this cause I work at Sprint... So good luck...
jalexishg said:
It seen like you have a HARDWARE issues, Re-Boot the Stock Rom. Call Sprint and explain what's going on with your phone, please *DO NO'T MENTION YOU ROOTED YOUR PHONE* Tell them you try to wipe your phone and it was really laggy before you wipe, since you gonna Re-Boot the stock rom the phone is going to get UNROOTED, I know this cause I work at Sprint... So good luck...
Click to expand...
Click to collapse
I definitely wont rule out hardware issues...this is a refurb device i just swapped my original EVO for on Monday. I guess I just want to rule out any software issues for sure.
You mention that re-booting the stock rom will UNROOT the phone...however I hav no way to currently re-boot the rom??
Also looks like i can not get into recovery now, when I select the option in the bootloader it just takes me to the screen with a picture of a device and a red triangle
azkevman said:
I definitely wont rule out hardware issues...this is a refurb device i just swapped my original EVO for on Monday. I guess I just want to rule out any software issues for sure.
You mention that re-booting the stock rom will UNROOT the phone...however I hav no way to currently re-boot the rom??
Click to expand...
Click to collapse
Get a Memory Card adapter for PC or use anything that will let you connect your SD card to your computer... As soon as you put the *ORIGINAL STOCK ROM* in your SD card your phone will do everything by itself...
jalexishg said:
Get a Memory Card adapter for PC or use anything that will let you connect your SD card to your computer... As soon as you put the *ORIGINAL STOCK ROM* in your SD card your phone will do everything by itself...
Click to expand...
Click to collapse
ok, going to try this now...
I assume I need to load it onto my sd card as the pc36IMG.zip so that i can load it from the bootloader?
you got it...just put it on the root of sdcard and good luck.
Sent from my PC36100 using Tapatalk
azkevman said:
ok, going to try this now...
I assume I need to load it onto my sd card as the pc36IMG.zip so that i can load it from the bootloader?
Click to expand...
Click to collapse
Yeah... Good luck... Let me know how everything went..
OK, so I loaded this ROM: http://forum.xda-developers.com/showthread.php?t=874091 onto my sd card as PC36IMG.zip
It loads the zip then says parsing for about 1 second then just reverts back to the HBOOT option ???
Doesn't ask me if i want to install????
Looks like I grabbed only the OTA update rom that was posted on that page. I am going to try the odexed version on this page: http://forum.xda-developers.com/showthread.php?t=874251
azkevman said:
Looks like I grabbed only the OTA update rom that was posted on that page. I am going to try the odexed version on this page: http://forum.xda-developers.com/showthread.php?t=874251
Click to expand...
Click to collapse
I can upload the version I use... Give a sec.(Uploading)
OK here you go !! http://www.megaupload.com/?d=EKDYV9I5 I hope this help you !
jalexishg said:
OK here you go !! http://www.megaupload.com/?d=EKDYV9I5 I hope this help you !
Click to expand...
Click to collapse
Thanks, I will let you know how it goes.
is nand unlocked on the phone?
asafegous said:
is nand unlocked on the phone?
Click to expand...
Click to collapse
I think so, on the bootloader it still shows "S-off" ...doesn't that indicate it is still unlocked?
OK, so I was able to flash the file in the bootloader. It looks like it won't load past the 'HTC EVO 4g' splash screen.
ARGGGGGGGGGGGGGG!!!!!!!!!!!!
But the Installation finish without problems ?
jalexishg said:
But the Installation finish without problems ?
Click to expand...
Click to collapse
yeah, as far as i can tell. It said it completed and gave me the option to press the power button to reboot.
It did finally load up...after about 15 minutes, but touchscreen is still erroring out and not funtional.
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?
So I flashed Skyraider tonight, wiped data, installed the ROM, and booted up the phone. I was halfway through setting up my Google account when the phone froze and rebooted. Except, it didn't boot back up. It did the "vibrate five times and flash the LED" thing. Didn't think it was a big deal, so I pulled the battery, tried to boot it back up. But it does the same thing.
I can get into the hboot menu, and if the phone is plugged into the computer, it'll boot up into Skyraider, but it can't read the SD card or the internal storage. So, essentially, a pretty screwy phone. I also cannot boot back into recovery. It just does the vibrating thing when I try. My computer doesn't detect the SD card or storage, either. (The SD card is fine, though. I put it in another phone and everything is still there.)
I have no idea what happened with it. I don't know if this is some random hardware damage, or if I should find an RUU and try to fix it or what.
I've had the worst luck with phones these past few weeks.
Any suggestions?
What version of CM Recovery do you have?
I would go back to stock and redo everything again. Download this file
http://www.fourty.net/~berzerker/stockstuff/PB31IMG_3.26.605.1_RUU.zip
Rename it PB31IMG.zip and put it on the root of your SD card, boot into the bootloader and let the update run its course. This will bring you back to a completely stock 2.2. From there you can re-root and do as you please.
I was on CW 2.5.1.2. But everytime I try to get into the recovery, the phone just vibrates five times and the LED flashes green. I'm also not sure that hboot is seeing my SD card. I'm going to try it, though.
Here is the RUU if you need it
http://shipped-roms.com/index.php?category=android&model=Incredible
The bottom one on that page is the Stock 2.2 build.
g00s3y said:
Here is the RUU if you need it
http://shipped-roms.com/index.php?category=android&model=Incredible
The bottom one on that page is the Stock 2.2 build.
Click to expand...
Click to collapse
I appreciate it, but hboot isn't recognizing the SD card.
I'm really thinking there's some hardware damage.
godsmacked4653 said:
I appreciate it, but hboot isn't recognizing the SD card.
I'm really thinking there's some hardware damage.
Click to expand...
Click to collapse
I'm not sure if it works, but can you boot into hboot and run the RUU from there and update. I don't think you need to have a working SD Card in order to do that, but I could be wrong. At least then it will be stock and no worries if you take it to verizon.
g00s3y said:
I'm not sure if it works, but can you boot into hboot and run the RUU from there and update. I don't think you need to have a working SD Card in order to do that, but I could be wrong. At least then it will be stock and no worries if you take it to verizon.
Click to expand...
Click to collapse
Do you mean running the Windows RUU? I tried that last night, but it could never find the device. ADB recognizes it, though, so idk what the problem was.
godsmacked4653 said:
Do you mean running the Windows RUU? I tried that last night, but it could never find the device. ADB recognizes it, though, so idk what the problem was.
Click to expand...
Click to collapse
If you have the unrevoked USB drivers installed I believe that is what causes it. You have to have the "stock" drivers for the phone installed on the PC for it to work, that was a problem I was having when trying to run the RUU.
g00s3y said:
If you have the unrevoked USB drivers installed I believe that is what causes it. You have to have the "stock" drivers for the phone installed on the PC for it to work, that was a problem I was having when trying to run the RUU.
Click to expand...
Click to collapse
I do have the stock drivers. I used unrevoked on Linux, and I've tried the RUU in Windows. But still no go.
I'm probably just going to take it up to Verizon today. If it can't boot, they really can't see that I've changed anything, right?
very true, good luck
g00s3y said:
very true, good luck
Click to expand...
Click to collapse
yes, good luck let us know ho it goes....
Kent_Davis said:
yes, good luck let us know ho it goes....
Click to expand...
Click to collapse
The sales rep looked at it for two minutes, and they're overnighting another Incredible to me.
So on one hand, I'm pretty happy about how easy it was.
On the other hand, I'd rather keep the AMOLED screen.
Does anybody know if I'm going to get a refurb, or will I get a new SLCD model?
If you had AMOLED first and they give you an SLCD, you can ***** at them and they have to give you an AMOLED one. Cuz that's what you payed for.
Sent from my ADR6300 using XDA App
dpwhitty11 said:
If you had AMOLED first and they give you an SLCD, you can ***** at them and they have to give you an AMOLED one. Cuz that's what you payed for.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
^ that. I just had to have a new one sent to me, its coming today. When I called tech support I asked them about what one I would be getting. They said that because I bought an AMOLED, I would be getting an AMOLED replacement.
g00s3y said:
^ that. I just had to have a new one sent to me, its coming today. When I called tech support I asked them about what one I would be getting. They said that because I bought an AMOLED, I would be getting an AMOLED replacement.
Click to expand...
Click to collapse
Yep. I got my replacement today. It's an AMOLED. As far as I can tell, all the hardware is working like it should.
This is probably the easiest time I have EVER had with Verizon.
But for future reference, five vibrations + blinking green LED = replacement.
I had same problem yesterday, five vibr.+ green blinks, but I had access into bootloader. I decided to reflash stock rom. Finally fixed problem
Sent from my ADR6300 using XDA Premium App