|
||||
Quote:
First... I did not call my carrier and say that I burned a custom ROM to my phone and now it won't work. I simply told them that I was applying an update from UTStarcom (lie) and something happened during the update and now my phone won't work. Second... I have been a systems administrator for over 5 years and I have no fear in screwing up a pc (pocket pc), because I know that there is a way to fix it. Although, it may take a little while sometimes. **An update... I followed Colonel's directions and was able to flash back to factory ROM, then I upgraded to Kitchen R3 (reading the BUGS thread first) with minimal apps and I am running perfectly fine now. Thank you to those who provided assistance. |
|
||||
Congrats!
Now, if you'd have just posted here first, you'da been fine. You did call your carrier for support after applying a non-approved rom, even if you lied about it - carriers sure don't want to provide warranty support for that. Which is why they bitched to MS to shutdown xda-developers, which they did (well, they pushed it underground, anyway...) Welcome aboard, and happy rom hacking. |
|
||||
MY XV6700 NEEDS SOME TLC
Ok i have a problem and I really don't know my way around on here that well but am willing to fish . my xv6700 wont sync with my computer at all after I put on kirvin_aku_3.5 nojunk.....tried the bootloader mode and it only go's to were it says serial and just sit's there.....was just gonna drop $$ and get another one like this, but know you guy's could help me out of this jam and save me the money.
|
|
||||
bb,
Don't panic. A similar thing happened to me today. I think the posts above correctly describe how to resolve the issue. Basically, my phone was stuck in bootloader and kept going back there no matter what I did. I used the uni_exitbootloader_173 file available from this site (in downloads). That got me out of bootloader and gave me a functional phone, but I still could not flash any new ROMs -- even the last Sprint official ROM. Any time I tried, I went right back to bootloader and got stuck there. Finally, I followed this procedure and it solved my problem: 1. ran uni_exitbootloader_173 to get out of bootloader 2. put the phone back in bootloader (power, notes, reset) (yes, intentionally) 3. flashed to an old 3.5 rom using the APACUpgrade_NOID tool (I happened to use Colonel's, but I think any ROM (Kirvin's, Sardinours, Jbaby, etc.) would work .. the point is just to flash using the NOID tool from bootloader, rather than the fully automated one that starts with your phone sync'ed to the computer). Now my problem was fixed. I built a new ROM using the R4 kitchen and flashed without a problem. Frankly, I'm not sure how I got myself in that mess, but this is how I got out of it. Everything is fine... and it should be for you too. |
|
|
|