25 minutes looking on the forums didn't really help me with what i need help with. i flashed Crossbow from a CID unlocked ex Faria aku 3.3 XDA Mini S, and i couldn't get signal, or play any sounds, in addition...the phone was extremely slow! i read that this is due to my device being CID unlocked, when i should flash an operator rom (to reCID lock it), then continue with the upgrade. surely this contradicts what threads say about phones MUST be CID unlocked otherwise you'll brick your phone etc. how can i get Crossbow Underground to be stable, and run normally?
also, my Faria 8mb aku 3.3 has moments of being lightning fast, and long periods of being stupidly slow (i.e. 10 seconds to unlock the phone from standby), does anybody know why it does this, and what i could do to fix it. Hard reset didn't do anything, and it's only getting slower. if i just left the phone after it being really slow, normally it will sort itself out and run fast again, after half an hour or so. the processor is set to default (not that this makes a difference as 260mhz doesn't speed it up), and i only have the normal programs on there.
any help atall will be greatly appreciated,
thanks,
thepolice
thepolice said:
25 minutes looking on the forums didn't really help me with what i need help with. i flashed Crossbow from a CID unlocked ex Faria aku 3.3 XDA Mini S, and i couldn't get signal, or play any sounds, in addition...the phone was extremely slow! i read that this is due to my device being CID unlocked, when i should flash an operator rom (to reCID lock it), then continue with the upgrade. surely this contradicts what threads say about phones MUST be CID unlocked otherwise you'll brick your phone etc. how can i get Crossbow Underground to be stable, and run normally?
Click to expand...
Click to collapse
I'm running Most Beautiful Edition so can't comment on Underground specific issues, but I don't think anyone has said that you should re-CID Lock your phone (actually I don't think you can, but thats another topic ). What I have suggested (and seen others suggest) is to always go back to an official ship ROM before upgrading. I went from Faria's AKU 3.3 straight to MBE and had all sorts of weird issues (active sync problems, Outlook complaining the calendar was corrupt, and more). I was frustrated and reflashed the TMobile 2.26 rom to go back to Faria's then it hit me I didn't do this before doing WM6. So I put MBE back on, and its worked great since. So I'm a firm believer now to take the extra time to move back to a shipped official ROM before loading a new custom one..
...the processor is set to default (not that this makes a difference as 260mhz doesn't speed it up)
Click to expand...
Click to collapse
Use batterystatus (for me I'm using .04.200 and not the beta 1.x one as it caused me issues) and have that overclock your device. If you can't see a difference, then I wonder if you have some hardware issue with your Wizard. I'm now running overclocked at 260Mhz via BatteryStatus and its been very stable and there is a definite improvement.
mfrazzz said:
I'm running Most Beautiful Edition so can't comment on Underground specific issues
Click to expand...
Click to collapse
Thanks, that was really useful
I can't run Most Beautiful, when i flashed it, it wouldn't boot atall. But this may be because i didn't flash the shipped rom before, is this likely?
When i flash the shipped rom, upon boot, the spl and ipl go back to 2.26...surely this means it's relocked. Should i flash the t-mobile rom instead? or wont this work as it wasn't the shipped rom - if that makes sense.
anyway, thanks so much for you help, you've explained a lot to me
thepolice said:
I can't run Most Beautiful, when i flashed it, it wouldn't boot atall. But this may be because i didn't flash the shipped rom before, is this likely?
Click to expand...
Click to collapse
Thats possible. can't say its likely, but its possible
When i flash the shipped rom, upon boot, the spl and ipl go back to 2.26...surely this means it's relocked. Should i flash the t-mobile rom instead? or wont this work as it wasn't the shipped rom - if that makes sense.
Click to expand...
Click to collapse
Yes when you flash the shipped rom the IPL/SPL will change to what comes with that ROM (for TMobile one it will be 2.26). That does NOT relock it. Only if you go back to a 1.x ROM will you have to deal with being relocked.
Example, I'm on a Cingular 8125. If I tried (out of the box) to flash the TMobile 2.26, it wouldn't work as its CID Locked. But after doing the CID Unlock, I can now flash TMobile, QTEK, O2, or whatever because it is CID Unlocked. And as long as I stay with 2.x roms, I can switch around as much as I want (it does't get relocked).
So definetly go back to an official shipped rom (and Tmobile 2.26 is the highly recommended one by about everyone), and then flash whichever custom rom you want to try. Its extra work to reflash an official rom but I think it removes problems some people see when they go from custom to custom.
thank you very much, i got my phone sorted now, and everything is clear to me.
It's okay now...got it sorted
Just curious, but what are you running now? And what worked for you?
mfrazzz said:
Just curious, but what are you running now? And what worked for you?
Click to expand...
Click to collapse
Right now i'm running the Faria 8mb. i was running Crossbow Underground, but i didn't see the point in going to all the efforts to fix the keyboard problems (because then I'd have to fix the predictive text) as the Faria Crossbow rom is coming out soon, i'll just get that...can't wait!
All the problems i had seemed to be becuase i wasn't flashing the shipped rom before the new one.
Related
I ran it according to farias instructions I thought. It flashed but now I cant install anything and I cannot write to the storage card or the phone, any cab i try to install is unsuccessful and I cannot save any files to the storage card or the phones memory.
And it appears that I cannot flash the rom again. Am I screwed?
What is you IPL / SPL? IS your phone a G3 or G4? Can you get to the bootloader? (turn off your phone (pull the battery if you have to) then hold the camera key down while you turn it on). You can flash directly to the bootloader (even though activesync won't connect.
BTW: If this stuff makes you nervous, you probably shouldn't be cooking... Your phone will do all sorts of weird stuff when you screw up a build. And you should really know how to recover from most things that can happen...
I have done this before, this is the first time I have ever had a problem. my IPL/SPL is 2.26. And the phone is unlocked.
beowolf said:
I have done this before, this is the first time I have ever had a problem. my IPL/SPL is 2.26. And the phone is unlocked.
Click to expand...
Click to collapse
ok, cool... wasn't sure... So can you get to the bootloader?
yes I can get to it
I am flashing back to the t-mobile 2.26 rom. Working so far, I will leave the cooking alone. Can you recommend a good wm6 rom that doesnt have any problems?
"doesn't have problems" is the catch
I'm partial to my own Crossbow Reloaded ones, but they aren't perfect. If you don't hit the keypad issue with 1.7 though, its pretty close
Core 2.0n is very good and nice and clean.
Also NBD and Wizard Mobile 6 are both supposed to work well.
The new "official" rom we are playing with is beta, but I have to say its really fast and we aren't seeing much wrong with it (but its only been 12 hours since its been released). There are a couple of issues that are fixed with cabs (CommManager for one).
As for cooking, you probably eith had something wrong in a .rgu or somesuch. Just takes a number of builds and flashes to get it right to where it boots (then you debug what you forgot in packages and start over )
OK, I read the posts here about flashing to button 1.05, then Tmobile 2.26 then WM6 roms. Why even bother with the Tmobile 2.26, I just went straight from the button to faria wm6. Does it have to do with the IPL/SPL being 2.26 instead of 1xx as they are now, if so what is IPL/SPL and why does it matter. Appreciate all answers.
mikejj2004 said:
OK, I read the posts here about flashing to button 1.05, then Tmobile 2.26 then WM6 roms. Why even bother with the Tmobile 2.26, I just went straight from the button to faria wm6. Does it have to do with the IPL/SPL being 2.26 instead of 1xx as they are now, if so what is IPL/SPL and why does it matter. Appreciate all answers.
Click to expand...
Click to collapse
Nothing personal, but all the information here is tried and proven. If you want to take shortcuts, be prepared to wind up with an unstable (or even bricked) device. Glad you were able to do that successfully, but it has been shown in numerous threads (especially back in January and February when WM6 was new for us) that if you have IPL/SPL that is not 2.xx and you are running WM6, you will have weird errors and an unstable device. Go back and read some of the old threads for the early WM6 roms, and numerous times in the threads people complained about issues after upgrading that most others didn't have. After asking for their IPL/SPL and seeing that one or the other was 1.xx, then having them upgrade to 2.xx the problem almost always (like 99% of the time) went away.
Basically IPL/SPL are like the BIOS on your PC. Running an older BIOS can cause Windows all sorts of problems due to bugs, device driver compatibility with the newer os, etc...
So for the extra 10mins or so it takes to flash the official T-Mobile 2.26 (or whatever other rom with an IPL/SPL of 2.xx or higher) you will save yourself a lot of grief.
What about just flashing button 1.05/ then using the IPL/SPL 3.08 upgrade before you flash to whatever? Ive used this method about 10 times in the last week to recover from crashed cooks and other whatnot and it seems to be rock solid.
As to MrFrazz thanks for the answer, thats kind of what I was thinking.
werD said:
What about just flashing button 1.05/ then using the IPL/SPL 3.08 upgrade before you flash to whatever? Ive used this method about 10 times in the last week to recover from crashed cooks and other whatnot and it seems to be rock solid.
Click to expand...
Click to collapse
Yeah this is what I was just thinking as well, I downloaded the 3.08 and I think ill give it a whirl but I notice most people here use the 2.26 also.
I wander why it is that the wm6 roms don't update the IPL/SPL?
mikejj2004 said:
I wander why it is that the wm6 roms don't update the IPL/SPL?
Click to expand...
Click to collapse
I've never flashed a 3.xx IPL/SPL. I've never seen a reason to go to that version (and have seen where a few people went to 3.08 or somesuch and couldn't flash back down to a lower IPL/SPL. May have been their phone but I just don't want to hassle with 3.xx until its shown its needed). The main point is you need to get to something above 1.xx (so yes, 3.xx would apply in that case if thats what you want. But remember higher version is not always better, no matter what the geek side of us wants to believe ).
As for why not hav ethe IPL/SPL in our custom WM6 roms? Because if I release a rom that has IPL/SPL in it, then this rom would brick a G4 device if the person just tried to flash it without using ShellTools. So for the sake of the G4 community, I think most rom cooks leave it out. Plus, once you put an IPL/SPL on your phone, you really don't ever need to change it again. The advice of going back to an official rom between custom roms isn't for the IPL/SPL but to clean up the extended rom.
mfrazzz said:
I've never flashed a 3.xx IPL/SPL. I've never seen a reason to go to that version (and have seen where a few people went to 3.08 or somesuch and couldn't flash back down to a lower IPL/SPL. May have been their phone but I just don't want to hassle with 3.xx until its shown its needed). The main point is you need to get to something above 1.xx (so yes, 3.xx would apply in that case if thats what you want. But remember higher version is not always better, no matter what the geek side of us wants to believe ).
As for why not hav ethe IPL/SPL in our custom WM6 roms? Because if I release a rom that has IPL/SPL in it, then this rom would brick a G4 device if the person just tried to flash it without using ShellTools. So for the sake of the G4 community, I think most rom cooks leave it out. Plus, once you put an IPL/SPL on your phone, you really don't ever need to change it again. The advice of going back to an official rom between custom roms isn't for the IPL/SPL but to clean up the extended rom.
Click to expand...
Click to collapse
Listen to mfrazzz. He knows what he is talking about. LOL
You are able to do whatever you want to with your device, but always remember this, alot of us have tried every possibility and have seen nearly every issue with the device, from frozen bootloader screen, to bricks, I myself have had one or 2 bricks. Luckily for me, I know how to deal with AT&T.
A word of wisdom, why make the same mistakes by rebuilding the wheel when someone else has already done it.
hey Guyz. I have a Tilt that a customer gave me that got bricked while trying to flash one of dutty's roms...Problem is that the genius didn't load up Hard SPL even tho he told me that he did...now He wants me to fix it...even tho he didn't follow my instructions and read the WiKi...I kno that on the Hermes it was able to be unbricked. Is the same for the Kaiser possible? I would greatly appreciate your help as my customers are loving the work you guyz do here in nyc..
Thanks in Advance!
Cristian
What is the current status of the phone?
Can you get into the bootloader at all?
If you can get to the bootloader you should be able to load the AT&T AKU v0.4.4 ROM (the unoffical upgraded AT&T ROM). Once you get that loaded you should flash HardSPL immediately.
Let me know how it goes...
Cheers.
I bricked my tilt when it was less than 24 hours old... I recovered it with a BETA of the ATT rom and THEN redoing the hardspl thingy - worked a treat.
Do a search for tolt bricked and you should find afew threads for it.
The rom is called something like RUU_Kaiser_ATT_WWE....._Internal.exe
It goes to the Tri-Color Screen but stays there..I'll go ahead and research it so I can find the original AT&T and load it up...It shows a lot..workin for at&t and being a member on xda...U guyz have no idea how ya make life easier for my tilt customers b/c at&t truly dropped the ball on the rom...and by offering alternatives..u make the user experience so much better...thanks!
HTCFAN0923 said:
It goes to the Tri-Color Screen but stays there..I'll go ahead and research it so I can find the original AT&T and load it up...It shows a lot..workin for at&t and being a member on xda...U guyz have no idea how ya make life easier for my tilt customers b/c at&t truly dropped the ball on the rom...and by offering alternatives..u make the user experience so much better...thanks!
Click to expand...
Click to collapse
If you are at the bootloader screen (Tri-Color) then the phone is not bricked. In the sticky at the top on how to revert back for warranty replacement, it has links for the various roms. Just flash an official AT&T rom on it and you should be good to go. Then do the HardSPL.
Cool that you work for AT&T and hang out here! If you have any other warranty returns, I can give you my address as I wouldn't mind having a backup or two...
BTW: The AT&T ROM for the Tilt is actually quite good in the big picture of things. At least the phone is usable (slower than it should be and less memory than it should have, but its still very usable and stable on the official rom). If you want to ***** about official roms, go back to the 8125 and its official rom. The while the device (at the time) was great, that rom made the phone almost worthless (super slow, battery problems, bad radio, dropped calls, freezing, etc). I can't tell you how many people that run custom roms on the Wizard just can't believe what that phone is actually capable of.
Ok, sorry, got off topic there...
does Hard-SPL needs to be flashed just once on a device or does it need to be installed every tome a new ROM is going to be Flashed onto it?
mfrazzz said:
If you are at the bootloader screen (Tri-Color) then the phone is not bricked. In the sticky at the top on how to revert back for warranty replacement, it has links for the various roms. Just flash an official AT&T rom on it and you should be good to go. Then do the HardSPL.
Cool that you work for AT&T and hang out here! If you have any other warranty returns, I can give you my address as I wouldn't mind having a backup or two...
Click to expand...
Click to collapse
For some reason, it's not being recognized by my Activesync. I got it to recognize it but now it sayz Error 294: Invalid Vendor ID...I'm using the RUU_Cingular_WWE Rom for the Kaiser...so I'm flabbergasted at this point...
Quick Silver said:
does Hard-SPL needs to be flashed just once on a device or does it need to be installed every tome a new ROM is going to be Flashed onto it?
Click to expand...
Click to collapse
Only once! Than you can flash as much as you like!
HTCFAN0923 said:
For some reason, it's not being recognized by my Activesync. I got it to recognize it but now it sayz Error 294: Invalid Vendor ID...I'm using the RUU_Cingular_WWE Rom for the Kaiser...so I'm flabbergasted at this point...
Click to expand...
Click to collapse
ActiveSync will not recognize your device when in BootLoader mode!
The Vendor ID error means the ROM cannot be loaded on the Tilt without HardSPL. You need an original Tilt ROM. (That's what I think about this)
HTCFAN0923 said:
It goes to the Tri-Color Screen but stays there..I'll go ahead and research it so I can find the original AT&T and load it up...It shows a lot..workin for at&t and being a member on xda...U guyz have no idea how ya make life easier for my tilt customers b/c at&t truly dropped the ball on the rom...and by offering alternatives..u make the user experience so much better...thanks!
Click to expand...
Click to collapse
Oddly enough the "Original" Tilt ROM will not install on a Tilt that does not already have HardSPL on it (to spell it out for you, the CID of the ROM does not match the Tilt's stock SPL). If you check the "reverting back" sticky you'll find all this info already, though it is deep in the thread.
The AKU v.0.4.4 ATT Beta ROM does have the correct CID and will flash on a stock Tilt. SO that is what you are forced to resort to at this point. Once you get the beta ROM installed you can (and probably should) install HardSPL.
After all that, if you decide you want to return or warranty the phone follow the "revert" thread to restore it to "stock" form.
Some additional notes on your problem...
ActiveSync will not connect in Bootloader mode (this is expected). You should see a device show up in Device Manager however, I can't recall the exact description however.
quick flash procedure:
put phone in bootloader
connect usb cable
install ROM
FYI, the problem may not be a bricked tilt... you could try Pof's fix which involves using MTTY.exe to boot the phone, depending on how your "customer" tried to flash it it may just need a kick in the pants to restore it. (search Pof's SSPL for the Kaiser thread for instructions, the thread was closed so you will have to look deep).
<climbing on my soapbox>
Lastly... your use of the word "customer" concerns me... are you charging people for the work you do to their phones? If so, do you donate to the people who make it possible? I'm probably just misunderstanding you, but if you're profiting from others work, perhaps you should contribute (especially if you're coming here to ask for help).
</climbing down>
Good Luck!
Cheers.
Customers as in I work for an AT&T corporate owned Retail location and they have bought Tilts from me. They kno my Tilt has been modded and they usually want to do the same. I don't charge them for doing mods to their Tilts. This still remains a community where we help each other and I cherish that. Greed has no place here.
as far as ur suggestions...It looks like I'm gonna be drunk @ 4am on XDA tonite...lol...
HTCFAN0923 said:
Customers as in I work for an AT&T corporate owned Retail location and they have bought Tilts from me. They kno my Tilt has been modded and they usually want to do the same. I don't charge them for doing mods to their Tilts. This still remains a community where we help each other and I cherish that. Greed has no place here.
Click to expand...
Click to collapse
That's cool... my misunderstanding then. Hopefully no hard feelings .
All in all it sounds like the guy wants a custom ROM so you should probably get the ATT Beta ROM and install that. And then install HardSPL.
Check Kyphur's second post in the thread below for the ROM you want.
http://forum.xda-developers.com/showthread.php?t=343198
Thanks for the info sycho...I'll get to it after work..
Good news! The AKU 0.33 worked! Thanks for ur help sycho!
how can i re-install the window? at tilt 8925
i have wm6.1
i want to reset it so the error message shud gone like Recover ?
@kaal,
It seems what you want to do is a HARD RESET. Please visit Kaiser Wiki and read through. You'll know your phone better that way.
@HTCFan & Sirsycho, Glad you both sort it out in the community spirit Cheers!
sirsycho said:
Oddly enough the "Original" Tilt ROM will not install on a Tilt that does not already have HardSPL on it (to spell it out for you, the CID of the ROM does not match the Tilt's stock SPL). If you check the "reverting back" sticky you'll find all this info already, though it is deep in the thread.
The AKU v.0.4.4 ATT Beta ROM does have the correct CID and will flash on a stock Tilt. SO that is what you are forced to resort to at this point. Once you get the beta ROM installed you can (and probably should) install HardSPL.
After all that, if you decide you want to return or warranty the phone follow the "revert" thread to restore it to "stock" form.
Some additional notes on your problem...
ActiveSync will not connect in Bootloader mode (this is expected). You should see a device show up in Device Manager however, I can't recall the exact description however.
quick flash procedure:
put phone in bootloader
connect usb cable
install ROM
FYI, the problem may not be a bricked tilt... you could try Pof's fix which involves using MTTY.exe to boot the phone, depending on how your "customer" tried to flash it it may just need a kick in the pants to restore it. (search Pof's SSPL for the Kaiser thread for instructions, the thread was closed so you will have to look deep).
<climbing on my soapbox>
Lastly... your use of the word "customer" concerns me... are you charging people for the work you do to their phones? If so, do you donate to the people who make it possible? I'm probably just misunderstanding you, but if you're profiting from others work, perhaps you should contribute (especially if you're coming here to ask for help).
</climbing down>
Good Luck!
Cheers.
Click to expand...
Click to collapse
Because of you folks and this thread, I have a working device as opposed to a paperweight...Thanks!!!
I am in dire need of some help when it comes to flashing custom ROMs. It appears that I can no longer flash custom ROMs. I can successfully flash the official 1.62 ROM from HTC website, the dumped TILT ROM, the Kaiser dumped ROM, and the WM6.1 WWE 3.03.405.0_radio_sign_25.70.40.02_1.64.06.04, but any other ROM I can’t. Let me explain my meaning of not being able to flash a ROM. Once it flashes 100% and reboots, when the “Tap the screen to begin to set up your windows-mobile device” is supposed to be displayed, all I get is a blank white screen. If I touch my stylus to the screen the text shows up, but none of the colored pictures that suppose to be in the back ground. Every section of the setup just displays the text no background images. Even my today screen won’t display any background images.
Does anyone have any information on this? I’ve abused this thread http://forum.xda-developers.com/showthread.php?t=314615 like a cheap dirty whore trying to find a solution, but no avail. Any help will be GREATLY appreciated.
kjones2k1 said:
I am in dire need of some help when it comes to flashing custom ROMs. It appears that I can no longer flash custom ROMs. I can successfully flash the official 1.62 ROM from HTC website, the dumped TILT ROM, the Kaiser dumped ROM, and the WM6.1 WWE 3.03.405.0_radio_sign_25.70.40.02_1.64.06.04, but any other ROM I can’t. Let me explain my meaning of not being able to flash a ROM. Once it flashes 100% and reboots, when the “Tap the screen to begin to set up your windows-mobile device” is supposed to be displayed, all I get is a blank white screen. If I touch my stylus to the screen the text shows up, but none of the colored pictures that suppose to be in the back ground. Every section of the setup just displays the text no background images. Even my today screen won’t display any background images.
Does anyone have any information on this? I’ve abused this thread http://forum.xda-developers.com/showthread.php?t=314615 like a cheap dirty whore trying to find a solution, but no avail. Any help will be GREATLY appreciated.
Click to expand...
Click to collapse
are you using 6.1 radios or the 6.0 radios?
P1Tater said:
are you using 6.1 radios or the 6.0 radios?
Click to expand...
Click to collapse
For each ROM, when ever I flashed, it changed my radio. For instance Alex's 1.62 rom, when I flashed his ROM, it already to changed my radio to the need radio to 1.27.14.09
kjones2k1 said:
For each ROM, when ever I flashed, it changed my radio. For instance Alex's 1.62 rom, when I flashed his ROM, it already to changed my radio to the need radio to 1.27.14.09
Click to expand...
Click to collapse
some come with radios, but most dont. You have to be sure if you need an AT$T specific radio or not.
P1Tater said:
some come with radios, but most dont. You have to be sure if you need an AT$T specific radio or not.
Click to expand...
Click to collapse
When I was running the WM6.1 3.03 ROM with radio 1.64.X.X, I flashed to Alex 1.62 ROM and my radio changed to 1.27.X.X. Didn't this flash change my radio?
kjones2k1 said:
When I was running the WM6.1 3.03 ROM with radio 1.64.X.X, I flashed to Alex 1.62 ROM and my radio changed to 1.27.X.X. Didn't this flash change my radio?
Click to expand...
Click to collapse
yes, if those are the only two flashes you have done, then it sounds like you might have had the unfortunate luck of having a bad flash. Reflash again and see what happens.
Edit:
Did you also do a hard reset at the "tap here to begin screen alingment" screen? If not, always do so.
P1Tater said:
yes, if those are the only two flashes you have done, then it sounds like you might have had the unfortunate luck of having a bad flash. Reflash again and see what happens.
Edit:
Did you also do a hard reset at the "tap here to begin screen alingment" screen? If not, always do so.
Click to expand...
Click to collapse
I always hard reset when flashing new roms (learned alot in the kasier wiki). This is what I'm trying. Flashing to ATT 1.62 (Offical from HTC website) > manually flashing to 1.27.04.09 radio > Flashing to Alex's 1.62 ROM
Anyone else have any suggestions?
I have a few ideas that I think may help. PM me when you get a moment. It may Late saturday or sunday till I can get back to you, but I need to know a coupl of things. So, if you're still stuck, let me know.
GSLEON3 said:
I have a few ideas that I think may help. PM me when you get a moment. It may Late saturday or sunday till I can get back to you, but I need to know a coupl of things. So, if you're still stuck, let me know.
Click to expand...
Click to collapse
PM sent
Check out the ROM Upgrading section of the Kaiser wiki under 'Troubleshooting' to learn how to enter bootloader mode.
Assuming that you installed HardSPL the first time you flashed, once you've booted into this mode, reconnect your device to your USB cable and flash another ROM.
For those who haven't looked at the Kaiser wiki in a while, I've completely revamped it w/TOC pages to make it alot easier to use (shameless plug)
_Alex_ said:
Check out the ROM Upgrading section of the Kaiser wiki under 'Troubleshooting' to learn how to enter bootloader mode.
Assuming that you installed HardSPL the first time you flashed, once you've booted into this mode, reconnect your device to your USB cable and flash another ROM.
For those who haven't looked at the Kaiser wiki in a while, I've completely revamped it w/TOC pages to make it alot easier to use (shameless plug)
Click to expand...
Click to collapse
?? This is not my issue. I'm not a complete beginner when it comes to flashing. Ever since I flashed the WM6.1 3.03 ROM I haven't been able to flash a custom ROM without having an image problem. I can still flash OEM type ROMS without the image issue, but not custom ROMS. I have the problem with images once a custom ROM has been flashed. If more clarification of problem is needed, I am will to give it.
This may be extreme and largely untested, but have you tried 'clear storage' on the WM6.1 ROMs and chosen 'delete NAND' (or something to that effect)?
That should wipe your ROM memory clean, although I'm not sure if that would help or hinder your cause, as I haven't heard anyone try it yet...
Hope this helps!
_Alex_ said:
This may be extreme and largely untested, but have you tried 'clear storage' on the WM6.1 ROMs and chosen 'delete NAND' (or something to that effect)?
That should wipe your ROM memory clean, although I'm not sure if that would help or hinder your cause, as I haven't heard anyone try it yet...
Hope this helps!
Click to expand...
Click to collapse
No, I haven't tried, but I guess I'll give it try when I get back in town on thursday.
Sorry I had to bug out....
Alex, his problem is a little different than a RUUBNH error that's commonly seen. I tried walking him through a CE reset using MTTY & he can't even communicate with his bootloader. MTTY wouldn't establish a USB connection. I agree that formating the Nand may help, but I think you really should also try & reflash hardspl as well. I suggest the new version with AT command support. I have seen a few funky hardspl flashes that inhibit communication, although rare.
I didn't forget you though Kjones, & I'm trying to duplicate your problem & find an answer.
I've flashed my palm pre with ease. I've also done the same to my Samsung Transform. There have always been guides on how to do so. I'm having trouble finding any guide on how to flash a custom rom to my Arrive. Can anyone point me in the right direction?
first: you are going to need to install HSPL. when you reboot with holding down the "volume - " button, what shows up as the SPL? 1.x? good, install the HSPL, anything higher? you'll have to downgrade.
Once you install the HSPL, it is as simple are running the RUU updater from ansar or the DFT rom
here is the HSPL
http://forum.xda-developers.com/showthread.php?t=1195647
and here is the SPL downgrader
http://forum.xda-developers.com/showpost.php?p=22574586&postcount=970
Thanks, for the help..
Those roms are horrible to download. Terribly slow and often lose the connection. I finally got both of them after several hours of retrying. Trying the anasr rom first
cdowers said:
Thanks, for the help..
Those roms are horrible to download. Terribly slow and often lose the connection. I finally got both of them after several hours of retrying. Trying the anasr rom first
Click to expand...
Click to collapse
in my opinion the DFT rom is a bit better. Ansar's would not allow updating the PRL, and would also throw an error on reboot. DFT is running smoothly on mine for the past week.
jeffc313 said:
in my opinion the DFT rom is a bit better. Ansar's would not allow updating the PRL, and would also throw an error on reboot. DFT is running smoothly on mine for the past week.
Click to expand...
Click to collapse
what version is yours?
4?
blanket said:
what version is yours?
4?
Click to expand...
Click to collapse
I'm running the "DFT Freedom Gold_C V1 for Sprint"
if I am reading things right I need to run the rom upgrade utility to downgrade my spl to version 1.xx from the current 4.xx but I can't get the ruu to work, I keep getting error 260 connection. Any idea what I am doing wrong? The readme file says to reset the device and or the computer, which I've tried but still get the error.
Also, if I restore my phone to nodo will that accomplish the same thing (downgrade to spl 1.xx)?
turdsamich said:
if I am reading things right I need to run the rom upgrade utility to downgrade my spl to version 1.xx from the current 4.xx but I can't get the ruu to work, I keep getting error 260 connection. Any idea what I am doing wrong? The readme file says to reset the device and or the computer, which I've tried but still get the error.
Also, if I restore my phone to nodo will that accomplish the same thing (downgrade to spl 1.xx)?
Click to expand...
Click to collapse
you should only have to run the utility to downgrade the SPL. When you boot up the phone into the bootloader by holding down "Volume -" on boot, do you get the "Serial" at the bottom?
When you plug into your PC, does it change to "Usb" for that same line?
It does say serial at the bottom but it doesnt change when I connect it to the pc, if it is already connected to my pc when I boot into bootloader mode it does say usb though.
edit: I figured it out, apparently the driver didnt install
so, I've successfully flashed my arrive to the dft freedom rom and I love it (especially enabled internet sharing) but now I have a noobish question. Is the rom updateable? (through Zune or otherwise) or will I have to flash again and reload all my apps and contacts in order to apply an update?
This is why I've been holding off flashing. I haven't NEEDED the ICS yet and I was worried whether or not it would take updates. So I was going to wait until an update started pushing and see what everyone else experienced.......
turdsamich said:
so, I've successfully flashed my arrive to the dft freedom rom and I love it (especially enabled internet sharing) but now I have a noobish question. Is the rom updateable? (through Zune or otherwise) or will I have to flash again and reload all my apps and contacts in order to apply an update?
Click to expand...
Click to collapse
Honestly, I'm not sure. But the chances of sprint pushing out any more updates is pretty low. 7720 is a very old build, you'd think that they would have done an update since then.
I currently have the stock Rom on the HTC Arrive on Sprint. For those of you that have done it, is it worth putting in a custom ROM?
I just finished flashing dft gold_c v1 rom on my arrive that I got today. I'm liking it a lot so far and it seems faster than stock rom. I like the additional apps and being fully unlocked for loading whatever I want. I'm brand new to the arrive but the flash went smoothly.
houdini13 said:
I just finished flashing dft gold_c v1 rom on my arrive that I got today. I'm liking it a lot so far and it seems faster than stock rom. I like the additional apps and being fully unlocked for loading whatever I want. I'm brand new to the arrive but the flash went smoothly.
Click to expand...
Click to collapse
Awesome! I want to be able to backup all of my SMS messages before I do it though. Is that possible without the custom ROM?
Was unable to save my SMS without a custom ROM so I did it anyway. so far everything is working great. I'm using DFT Freedom Gold_C V1.
Anyone know the differences between the DFT Freedom Gold and Ansar's ROM ?
I haven't tried Ansar's rom yet since there were issues with the prl and network update functions. Now that he has a new tango version out that fixes it, I may try it soon. It will be hard to leave the dft rom because it works perfectly for me and I have it all set up the way I want it. The few added features of tango may make me switch though...like video mms.