need URGENT help! - Upgrading, Modifying and Unlocking

im trying to flash my htc p4000...
i unlocked it, and tryed to flash the new 6.1 rom, now my phone starts up and just freezes on the telus screen.
first i was sent here, and downloaded the 2.4 unlocker, but it kept freezing, so i downloaded this one HERE
used that...it seemed to work, that i ran 2.4 from the first link, which didnt appear to do anything.
than i ran the RUU i had with the new rom nueROM v2.0 Build 5022.

k, i just finished running to official 6.0 rom off the telus website and its booting up now.
PHEW.
this is what happens when an impatient person dosnt get help
if someone knows how to help me out please post....

so...
can someone help me upgrade to 6.1....with it booting.

Related

Can't Flash Back!!!

Please someone, anyone, help me out.
I recently flashed my trinity to Bepe's Rom...everything went alright.
Then today I attempted to flash it back to LVSW's rom.
I've done Hard SPL, updated the radio etc...
when I flash LVSW or MUN rom's rom, everything seems to go smoothly, but when the device resets I still have Bepe's Rom.
Tried several times to no avail.
Can anyone help me?
Flash once with an official HTC ROM, then flash with the ROM of your choice
Official Rom DOn't Work
Thx for suggestion re: flashing with an official rom. I flashed with an HTC rom, but still no joy.
It seems to flash fine, but after finishing still got bepe rom!!!
God this thing is like a curse, I just wanted to try it out now it seems that I'm stuck with it permanently.
Someone plz help...
How long does it take you to flash the ROM? Approximately.
It usually takes about 1min 30sec - 2 min to flash the cooked roms.
The official rom takes about 7 or 8 min... definately longer than the cooked ones.
Remove your SD Card an try to flash again, thats very strange!
Sorted...thx.
I was starting to freak out. The SD card was the problem.
You're a legend mate...
Thanks, good to hear that there is no problem any more

can't flash artemis, uspl not running correctly

hi there.
this is my first post, and unfortunately, it is asking for help..
i recently bought a artemis, and the last couple days i've been searching on roms, both cooking and flashing.
i've tested a couple roms, from vanilla to touch, b&b and others, every single one without a problem. for all of them i've user XP sp2 in a virtual machine (VMWare). everything went ok, cid unlocking and flashing the roms perfectly, and as i finally decided to cook my own rom, i started looking for generic roms from htc, to see what they looked like, so i could had a better understanding on how to cook a good rom to settle my needs.
unfortunately, i flashed a rom, don't now for sure wich, but it's from o2, and from that moment on, i could not flash anymore.
every time i try to run the uspl, i can't get the spl to 1.11.000. it stays on 3.07.000.
i've tried running several times in a row the uspl, then flashing, tried flashing a generic rom, hardspl, arte and uspl, tried running the .nbh from the sd with no success (although there seems to be a fix for that, will try that tomorrow), tried getting into boot and flashing.
but the funny thing is, in the uspl, when it is running, and reaches 70% it jumps to 100%.
and whenever i try to flash it, obviously, i get the error 270 update error.
so, after that, any ideas? the artemis is running smoothly, without a problem, although not with its original rom, and locked to a different provider (it's cid locked to vodafone portugal)
thanks in advance
edit: i've had the chance to test the sd flashind, again, with no result
no ideas anyone?
nevermind, managed to get over it.
used an upgrade from the htc in the language my pda is locked. solve it
I have the same problem. I am working with it !

Corrupt ROM on the Dash

I recently tried the WM6.1 version on my dash and it worked fine. I actually flashed it twice with this update and I had no problems. So last night I decided to put the original update from t-mobile back on my phone and so I downloaded this update from their website and flashed it onto there with no problems. I waited a whole night and decided that I didn't like it as much as I like 6.1 so I decided to put that version back on and now whenever I get to the point where it is updating, it goes to about 3% and then my phone restarts and the program lets me know that the version of the ROM is corrupt. I've tried downloading a different copy of the same ROM but it still happens.
I'd like to know how to fix this so I could continue using wm6.1 in my phone.
Thanks!
You need to unlock your phone.
Follow the manual that is stickied in page 1

Issues Flashing New Radio

I know that I have already posted on someone else's thread, so I figured rather than hijacking someone else, I would start my own.
Here is my issue. I have tried every posted method out there for flashing Radios into my Sprint Vogue (flashed to MetroPCS). I am currently on NFSFAN's 1.00.6.5 Rom (21864), with radio 3.37.10.
I have tried...
*Flashing from SD card with a fat32 formatted 2 GB card, renamed radio to VOGUIMG.NBH (upper and lower case),
*Flashing via USB with ActiveSync on,
*Flashing via USB with ActiveSync off,
*Flashing via USB with bootloader preset,
*Flashed back to the Alltel rom used for SuperCID and tried to flash radio while in that rom,
*I have tried with radios 3.42.30, .40, and .50.
The only thing I have not tried has been mtty, but somehow I have my doubts that it will work.
Every time the RUU runs, it starts and the progress quits at 8%, with my phone being rebooted. Also, the RUU displays error message 328....
I have searched all over and tried a few things but most of them are related to the Titan and not to the Vogue. If anyone has encountered this issue and knows how to solve it, I am open for suggestions. Thanks...
I suggest your flash your phone with the stock rom of bell if your want the 3.42.5 radio. Just reset as soon as your see the 3 second customization screen.
Then unlock phone, and then flash your fav custom rom.....
SL said:
I suggest your flash your phone with the stock rom of bell if your want the 3.42.5 radio. Just reset as soon as your see the 3 second customization screen.
Then unlock phone, and then flash your fav custom rom.....
Click to expand...
Click to collapse
I'll give that a shot. Thanks for the suggestion...
@SL
I followed your advice to a certain extent. I went with the latest Sprint official rom, which carried 3.42.30 in it. This seemed to work ok. I still cannot go to .40 but I guess if I flash from the original carrier that had this rom, I will be in good shape (Bell with .50, etc). Do you know which carrier has .40? Thanks for the help!!!
@ SL
I finally went over to the Bell rom that can be found in HTC's official website. I am finally up and running with 3.42.50!!!
I will probably try to make a sticky or a post describing the problem and the solution for people with the same issue, which I have seen quite a bit looking for an answer...
Once again, thanks for all your help!

[Q] Unrooting desire, 140 error, bricked?

Hi after days of searching the internet I have finally realised I need to post here and ask for help, sorry if this has been posted before though as I have really looked hard everywhere!
Anyway, after flashing a RCMix rom my desire started to drop calls as soon as I either picked up or answered one and only ever rarely got 2G signal in what I know is H signal zones. I changed roms but the problem persisted and after countless hours of searching and trying my sim in other phones, I have deducted that it is my desire which is the problem.
So I'm going to take it back to a t-mobile store, as I were unrooting using the RUU exe I got the 140 error, my phone will no longer boot but still has bootloader, fastboot and recovery working! Is my phone bricked, I can't find any help anywhere on how to put my desire back to stock
Please could any of you shine some light onto my situation?
Many many thanks
You have recovery? Did you try installing another rom to make the phone work again?
After that you can try to unroot it again, I think...
Okay, I will try installing a froyo rom now, will post the results of a second unroot...
Right very strange indeed, just flashed AceSMod007 and signal problems have seem to have gone away (although I had tried this before with many roms - maybe the unrooting process fixed my phone somehow?)... so this means there is no need to unroot and send back to t-mobile, hmmmm all seems to good to be true! thanks for the help though, wouldn't of tried flashing another rom if you hadnt mentioned it

Categories

Resources