I posted this for the few people that were awaiting for the Herald kitchen.
So..i know that you must probably hate me till now, but sorry again i have to delay the porting of my Core Kitchen to the Herald.
It has come to my attention that there is still no way of flashing an Terra because there is no RUU and thus no means of flashing. I will see what i can do, meanwhile i got some work and i will leave for about 5 days.
If anybody has any ideas on how to help these people, please put it into action or give me a pm.
Cheers !
you can flash using Aserg's method which is what other cooker's have resorted to!
blackout203 said:
you can flash using Aserg's method which is what other cooker's have resorted to!
Click to expand...
Click to collapse
From what i understood ...
Aserg's method only works from ActiveSync . So this means that if you cook a rom with my kitchen and make a mistake and the rom doesn't work then you have a brick. That's why i didn't focused my attention on this. I was waiting for a proper RUU so that people wouldn't brick they're devices.
Hope you understand.
Well hopefully they roll out that new RUU for WM6 before the months end. Would love to do some experimenting with it during my vacation next month.
anichillus said:
From what i understood ...
Aserg's method only works from ActiveSync . So this means that if you cook a rom with my kitchen and make a mistake and the rom doesn't work then you have a brick. That's why i didn't focused my attention on this. I was waiting for a proper RUU so that people wouldn't brick they're devices.
Hope you understand.
Click to expand...
Click to collapse
Yes that´s true. And nothing to say sorry - you had enough trouble with your PC.
But this is what I got as away for falshing from bootloader.
The problem is that the singing of the nbh file doesn´t worfk correctly - i guess.
I've been using his tool from:
http://forum.xda-developers.com/showthread.php?t=311909
He doesn't really show a method, so what I've been doing is:
1. Using NBHExtract to dump an .nbh that's on the Herald Wiki.
2. I rebuild the .nbh using Dark Simpson's little utility using the information I had luckily written down before I bricked the phone. So I plug in my ROM (4.10.531.3) in the Version, HERA110 in Device ID. The only other thing is that I'm not sure about the CID.
3. Place the new .nbh file in a folder with an updater (the ROM Update Utility that comes with the ROMs from the Herald Wiki).
4. Get the phone into Bootloader mode, start the updater.
In this way I've got rid of the Invalid Device ID error (error 243 or something?) and now it goes to 3% and tells me that the image file is corrupt.
I'm very new at this so maybe you can see a flaw in what I'm doing, or maybe with your knowledge we can figure this out. I was *almost* to the point of trying to cook using a couple links you've posted (XIP, dumps, etc) and then put it all together in a signed .nbh, but Rapidshare was holding me back... making me wait 80 minutes between downloads -_-
Anyway... I've only been trying to update the OS.nb portion since I believe I only screwed up my OS, not anything else. I can still get into the bootloader, my IPL/SPL still reads 4.xxxxxx, and by "brick" I mean that the phone just hangs on bootup at the T-Mobile splash screen. Correct? Incorrect?
Click to expand...
Click to collapse
Perhaps we can work with it.
It is not a huge problem for HTC branded devices as there is a RUU to flash with if everything goes wrong. It's just a problem for our T-Mobile Wing and O2 Terra cousins (if they brick their devices). But it's nice to see some proper chefs taking an interest, never liked the pdaviet ROMS ever since they used a whole bunch of Faria's stuff without asking.
im running pdaviet now, but im hoping to see something other soon, its not bad though, just a bit slow..lots of "lagging" on the today plugin, I used the herald dump from tupisdin earlier, and installed my fav progs on that...was pretty dam fast on my phone...only problem was that it occupied more space on the main memory when stuff was not cooked into the rom itself...
trying to learn about cooking myself, not so easy as a thought
But I guess im lucky to have a unbranded htc p4350, If i brick, I just install the official Ruu from HTC
(btw, I DO use Vista for flashing, just changed the usb driver that WMDC uses to connect via USB to the old activesync 4.5 USB driver...)
Related
Hey All-
I'd appreciate any help anyone can offer. I am having problems updating to any of the WM6 ROMs out there (up here). One of a few things is happening:
1) Either RUU crashes just after it successfully sends my PDA in to bootloader mode, or
2) RUU is able to stay up, but for some reason, does not like the update file:
I either get an error: "This NBF file cannot be used for your PDA Phone. Please get a newer NBF file.", or
it suggests the nbf file is "corrupted", I think indicating the RUU util I am running is out of synch with what the PDA is expecting.
I'm using a T-Mobile MDA (Vario?) and Vista.
I've tried all of the solutions I have been able to find:
* changing the driver to HTC USB Sync so that it can "reconnect" once in bootloader
* various flavors of the update utility to get around the crash, which do not let me upgrade to the ROM of choice!
* hard reset of the device
* I even tried pulling down one of the ROM upgrades from the T-Mobile dowloads site and dropping that in with a WM6 ROM nbf file. That was a huge flop.
I know people have done this! I've seen it over and over again. So what in the world stupid thing am I doing to not make this work?
Thanks.
Joel Niemeyer
Seattle
RUU doesnt work on Vista. Use shelltool.
Thanks for the advice. I'm sure it was good advice, but I am three hours in to it running now, and I don't have a good feeling about it. I think it says it would take at least 15 minutes. Not 180! Ugh, now I wonder what I should do?
Joel
jniemeyer said:
Hey All-
* changing the driver to HTC USB Sync so that it can "reconnect" once in bootloader
Click to expand...
Click to collapse
How do you do that? Thank you because when i try to downgrade my ROM or w/e so that i can unlock it when i gots to bootloader the fred green blue thingy it doesnt reconnect to active sync and maybe thats my probelm...=[
chaos, just look around for the RUU with Vista instructions- they are everywhere!
hey mate,
just follow this instructions http://www.modaco.com/index.php?showtopic=252977 to falsh every official ROM under MS Vista. Surely, when it comes to WM6 you gotta use the Shelltool.
regards
irm
Answer for Vista
My question is why don't people just dual boot vista with xp or 2000/etc...that would solve a lot of issues about the problems with vista.. just boot to xp..
I figure if you have the $Funds$ to spend on a $250+ phone you could shell out $50 for a 150gb 16mb cache HDD for your pc and dual/tri/quad/etc... sheeet son i've been doing this for years with linux/m$/mac.
Gotta face it, some software just runs better on one OS over another. peace out.
can someone confirm shell tool work
ANTC said:
can someone confirm shell tool work
Click to expand...
Click to collapse
I tried it, took like 6 minutes then it was completed, knowingly it wasnt flashed right, but did the hard reset on the phone and was stuck at the SPL screen, so just loaded up VMWare to reflash.
It worked for me...
I flashed one of the WM6 ROMs using my Vista Ultimate computer. One of the main parts in making the thing work is remembering to put your computer in bootloader before doing it. On post #7 in the MoDaCo thread, it says this.
Once more, here is the link: http://www.modaco.com/RUU-on-Vista-It-can-be-done-the-ultimate-guide-t252977.html
so your saying witht hat tut you flash a custom rom??
Yes
Yes I was able to. I don't remember which, but I think i was Core 2.0
Yeah, I was able to use shelltool to make this happen. Thanks for the feedback, folks. Only hang up was that it had appeared to have seized up (was seemingly stuck before the "End" portion). I waited for like 3 hours before I finally threw up my hands and hard reset the unit. Low and behold my wizard booted up in to the new ROM and I have been good to do since!
I have no part in any of these programs; I just put the scattered pieces together. This worked on my brand new wing without any other modifications.
The included rom is the Touch-IT for The Wing Full http://forum.xda-developers.com/showthread.php?t=332789
Download the kit at:
http://rapidshare.com/files/58874111/herald.rar.html
Disclaimer:
This is free to use but at your own risk, I take no responsibility for any conflict, fault, or damage caused to your phone by this unlocking procedure. No warranties of any kind are given. Any commercial usage prohibited.
Instructions:
1. Unzip on c:\ use a folder name with no spaces on it.
2. Connect your phone to computer, make sure activesync is enabled (green icon)
3. Run herald-uspl.exe on your computer and follow instructions on screen.
4. If you have problems, install RAPI/EnableRapi.cab on your device, and retry after.
All credit goes to POF for HERALD-USPL-beta3.zip and of course the Touch-IT team for their great rom.
What about the XDA TErra? Someone tried??
It will most likely flash, but your keyboard will probably be messed up. Just download a more correct rom and pack the os.nb into a RUU_signed.nbh with the htc rom tool (by Dark Simpson). Then replace the RUU_signed.nbh in the RUU folder with one you made.
brazen1445 said:
It will most likely flash, but your keyboard will probably be messed up. Just download a more correct rom and pack the os.nb into a RUU_signed.nbh with the htc rom tool (by Dark Simpson). Then replace the RUU_signed.nbh in the RUU folder with one you made.
Click to expand...
Click to collapse
And that is the problem for ALL Terra user. There is no ROM!!! No RUU. Nothing for unbricking the devices if something goes wrong while flashing.....
That´s the big problem for ALL XDA terra user. O2 will not release an update...
papamopps said:
And that is the problem for ALL Terra user. There is no ROM!!! No RUU. Nothing for unbricking the devices if something goes wrong while flashing.....
That´s the big problem for ALL XDA terra user. O2 will not release an update...
Click to expand...
Click to collapse
they suck, they have not heard of customer service?
what about dumping the rom? picking out the oem folder and port a herald sys folder? maybe if the rgu files are intact in the terra device, they can be used somehow put into the kichen with sys and oem? hmm, xip might be a problem though.....nah, just a brainstorm....dont think its possible.
Dam, bribe a guy from terra service, make him leak a ruu on the net
Great work ! It's running on my O2 Terra with out great problems.
1. at any Softreset it send's an SMS to an nonexisted Reciver.
I changed the Keybord to Germen with this http://wiki.xda-developers.com/index.php?pagename=Changing_Device_Language
as i sayd great work
Ghostrider
I didnt know wings came CID locked.
Actually that comment sounds kind of retarded.
Reason I say all this is because I've instaled TouchIT and all the variations just fine on my stock Wing..
Are others having problems?
itje said:
what about dumping the rom? picking out the oem folder and port a herald sys folder? maybe if the rgu files are intact in the terra device, they can be used somehow put into the kichen with sys and oem? hmm, xip might be a problem though.....nah, just a brainstorm....dont think its possible.
Dam, bribe a guy from terra service, make him leak a ruu on the net
Click to expand...
Click to collapse
Have found one. But he will not release....
Damn. He is a real insider with a stupid brain. Germans are tooooooo near to rules.
Hehee.
And btw - the first Aserg ROM ever was based on my terra dump. But without an RUU - we cannot unbricke. Believe me - i tried everything
germans invented rules
TylerC161, I guess your just lucky. When I tied to flash with Aserg's method I would get an error that said:
ERROR [294] : INVALID VENDOR ID
This Update Utility cannot be used for your PDA Phone. Please check your Upgrade Utility.
Which, from what i gather, means your phone is CID locked. A quick search showed the following threads discussing the same thing.
http://forum.xda-developers.com/showthread.php?t=310790
http://forum.xda-developers.com/showthread.php?t=331324
http://forum.xda-developers.com/showthread.php?t=331443
http://forum.xda-developers.com/showthread.php?t=321144
http://forum.xda-developers.com/showthread.php?t=316512
http://forum.xda-developers.com/showthread.php?t=311628
Using this method saves you from going to IMEI-CHECK.CO.UK and paying $40. Also you can restore your phone back to factory for warranty work if need be. Am I the only one who finds this helpful?
I've been reading and trying this for days with no luck. I've fully unlocked my wizard and I'm now trying to flash to the 318 rom. But I have no clue how to do it. Could someone walk me through ho to do it? Most of the flashing done thus far has been an EXE file or through DOS. I must be missing something simple.
please help
follow this thread, enjoy
http://forum.xda-developers.com/showthread.php?t=298613
mikaarce said:
follow this thread, enjoy
http://forum.xda-developers.com/showthread.php?t=298613
Click to expand...
Click to collapse
I followed that one already. That's how I unlocked it. But all step 3.8 says is "your ready to flash...". Right now I don't understand exactly how to flash and I'd prefer not to "trial and error" it.
However, this morning I did open up the Hypercore kitchen and I think I'm on the right track. I'm at work so I can't try anything but I've printed up everything in that thread including all it's links and I'm going to give it a go once I get home. I'll report back once that's done.
Alright, after some more research and reading in the hypercore kitchen thread and all it's links, I think I may have it figured out.
I download and extract the files for the ROM I want, in this case 318 8.1 from theloon.
I then follow the instructions linked int he hypercore thread with dumping, and the pkgtool, buildos, etc.. If followed correctly, my wizard should be flashed with the new rom correct?
A confirmation would be nice. Any other comments you have are a bonus.
Another question though; what's the difference between the programs contained in the SYS and OEM folders compared to the ones in the build OS that i have the select? Aren't the ones in the folders already included in the ROM?
Your help would be greatly appreciated. I don't get confused too easily so as you can imagine i'm quite frustrated. I used to flash new versions and programs to my Razr but it was nothing like this.
dont get me wrong are you trying to cook your own rom, because hypercore is a kitchen, i suggest you download one of the roms that are made by reputable cooks, like the NBD series, TNT series, paradox, xmr, faria's, ingenetics, octavio's they differ in the apps and costumization included in the os and the builds, so just select download and flash
there's an executable file inside the roms once you unzip it and be careful if your using xp or vista
The only things I've been working with up until this point is BuildOS and nb2nbf. I haven't fully grasped the definition of "cooking" yet; whether it means altering files for my self or if the BuildOS selection list is considered cooking.
I think i was trying to do too much and using a file different from the one being referenced in the tutorial was a bit confusing. So to start, I decided to use Faria's Crossbow and the tutorial that came with it. It was very easy and I was able to flash my Wizard to that ROM without a problem. But the one i really want is Theloon's 318.
So, based off of what I learned last night I figured I just needed to replace the OEM, ROM, and SYS folders that came up when I unzipped Faria's crossbow with the ones from 318. Is this correct? Because I just tried that this morning and I get all the way to the CMD prompt right before it opens nb2nbf and it gives me an error (see attacment). If there's one thing I've learned from all these bricked devices floating around, it's to NEVER proceed when an error occurs.
What does this error mean? How can I fix it? Is my moving of the folders wrong? What am i missing?
just messin around trying to see what tools work, i got another error.
Ok, now I've got a bigger problem. I finally figured out what I was doing wrong. It's actually a lot simpler than I thought. i was just making it more complicated. Ok, I tarted the flash and at about 47%, it gave me a memory reference error. Now my Wizard won't go past the three-color screen and all it shows is my IPL/SPL 3.08. ActiveSync won't detect it, tried hard resetting, turning on while holding camera button, etc. What do i do now?
Now you start thinking... "Maybe I should have read the stickies on the Upgrading forums... bummer..."
The 3 color screen is called the BootLoader. As long you get that screen, your phone can be recovered. How to recover it?
- Use a Windows XP PC.
- Download Wizard_Love Rom (its somewhere, use google or search the forum, but then again, you wouldn't be having this problems IF you knew how to use the search button!)
- Press and hold CAMERA button and hit the reset, keeping the camera button pressed.
- Connect the Wizard to your pc using the USB cable.
- Start the Wizard_Love RUU utility that comes with it.
- Just press next until it starts flashing the ROM to it.
- Pray for it to finish without touching anything until the RUU says CONGRATULATIONS.
There... your phone is working again.
READ THE STICKIES BEFORE DOING ANYTHING AND USE THE SEARCH!
THIS QUESTION HAS BEEN ANSWERED FOR TOO MANY TIMES ALREADY!!!
PS: Maybe we should create a thread for helping the guys that don't follow stickies or care about the ALREADY info we have here... something like:
- 3 color screen: do this
- different IPL/SPL G3 on a G4 device: you are screwed.
I definately read the stickies over and over again. I've got a stack of printouts sitting in front of me that I've been reading for the past week.
I understand your frustration about questions like this but that's no reason to be rude. I used to be a moderator on pbnation.com so I know exactly how you feel. But the fact of the matter is that I'm not as familiar with these things as you are. I fixed the bootloader issue before I even read your response. i found the answer by re-reading one of my printouts that said the re-flash with official rom. So i did that and it worked. I knew I'd get flamed for posting but since I had already had a thread created, I figured it wouldn't hurt to post updates on my status.
I know how to flash roms now. It's actually quite easy. However, I ran into some issues that I'd like to explain in hopes that you realize I'm not taking advantage of you or not utilizing the tools and stickies.
i was having problems yesterday because of my work computer (I think). When extracting the files from Hypercore, they were not placed where they should have been and the tools wouldn't work properly. An example would be when opening buildOS it would give me the yes or no prompts. An IT friend allowed me to use his non-work laptop to do the exact same thing and I was able to use it without a hitch. The simple tmobile official rom update wouldn't even work on my work computer. So it's not just me.
I knew there was a reason that i couldn't follow it.
Regardless of your approach, I still thank you for your help.
I didn't mean to be rude... sorry about that. Its just that from your post count I thought your were like a newcomer like those that come here all the time, asking the same questions over and over again. Netherless, sorry for "helping" you the way I did.
I will have some tea now to relax care to join?
So, you've decided that your shiny new toy isn't very well setup by default. You flashed a ROM and lo and behold, you missed some instruction somewhere and now you think it's bricked.
Here's the good news:
It's not bricked!!
Bricked means that it's dead and it's in no way or shape recoverable.
There is still a chance. (As long as you didn't try to hardSPL with another Device's SPL...)
All you have to do is:
For the WING:
Hold the Camera button and WHILE holding it, soft reset the device (that means press the little hole above the memory card with the stylus.) That will bring you to the bootloader. Now download the appropiate RUU and run that program. A few minutes later and your new shiny toy is back to it's crappy OEM but working self!
I'll put in links for those who can't find them...
Here's tmobile's ROM.
WOW! That´s all??
Ok - then provide us a link to a XDA Terra RUU!!!!!!
hahahaha. Thanks for this help. Maby for some people it is usefull - but written 1000 times before.
ivanmmj said:
So, you've decided that your shiny new toy isn't very well setup by default. You flashed a ROM and lo and behold, you missed some instruction somewhere and now you think it's bricked.
Here's the good news:
It's not bricked!!
Bricked means that it's dead and it's in no way or shape recoverable.
There is still a chance. (As long as you didn't try to hardSPL with another Device's SPL...)
All you have to do is:
For the WING:
Hold the Camera button and WHILE holding it, soft reset the device (that means press the little hole above the memory card with the stylus.) That will bring you to the bootloader. Now download the appropiate RUU and run that program. A few minutes later and your new shiny toy is back to it's crappy OEM but working self!
I'll put in links for those who can't find them...
Click to expand...
Click to collapse
papamopps said:
WOW! That´s all??
Ok - then provide us a link to a XDA Terra RUU!!!!!!
hahahaha. Thanks for this help. Maby for some people it is usefull - but written 1000 times before.
Click to expand...
Click to collapse
I know it has been stated a million times. I'm just tired of the same question being asked over and over again and so here we are...
Too bad it'll be stated a million more times afterwards too.
falconeyez said:
Too bad it'll be stated a million more times afterwards too.
Click to expand...
Click to collapse
If we sticky it and threatened their lives if they don't read it... lol
ivanmmj said:
For the WING:
Hold the Camera button and WHILE holding it, soft reset the device (that means press the little hole above the memory card with the stylus.) That will bring you to the bootloader. Now download the appropiate RUU and run that program. A few minutes later and your new shiny toy is back to it's crappy OEM but working self!
Click to expand...
Click to collapse
It will not help!
ASerg said:
It will not help!
Click to expand...
Click to collapse
And we hold their pet's hostage?
ivanmmj said:
And we hold their pet's hostage?
Click to expand...
Click to collapse
Or better yet, tell them to send us their phones, then we "unbrick" them and sell them on eBay.
falconeyez said:
Or better yet, tell them to send us their phones, then we "unbrick" them and sell them on eBay.
Click to expand...
Click to collapse
Might work out, I get 10% of the over all sold
Ghostrider
Ghostrider said:
Might work out, I get 10% of the over all sold
Ghostrider
Click to expand...
Click to collapse
Fine, but I get 15% because it's my thread.
The instructions to do this are actually in my newbie thread. Which is a sticky.
TylerC161 said:
The instructions to do this are actually in my newbie thread. Which is a sticky.
Click to expand...
Click to collapse
I know, but most people don't search. I figured, maybe if it says "How to fix your bricked phone" on the title, they might get the idea.
It was actually done mostly as a joke...
help
I used the hardSPL from this thread..
http://forum.xda-developers.com/showthread.php?t=358225
It worked successfully and I was able to restart into WM6. Then I tried loading the TouchIT 4.4 and it installed cleanly with no errors. But when I went to restart it, my Wing just sits there at the CanonYang boot screen and never changes.
I tried using the steps here to restore the tmo default rom, but it after 1% on the progress bar, the screen goes blank and the CanonYang screen comes back. Is there anything I can do?
edit: I can get to the bootloader screen with the color bars. I'm not sure if this additional info will be of any help.
IPL 4.10.0002
SPL 4.70.Yang
gumbico said:
I used the hardSPL from this thread..
http://forum.xda-developers.com/showthread.php?t=358225
It worked successfully and I was able to restart into WM6. Then I tried loading the TouchIT 4.4 and it installed cleanly with no errors. But when I went to restart it, my Wing just sits there at the CanonYang boot screen and never changes.
I tried using the steps here to restore the tmo default rom, but it after 1% on the progress bar, the screen goes blank and the CanonYang screen comes back. Is there anything I can do?
edit: I can get to the bootloader screen with the color bars. I'm not sure if this additional info will be of any help.
IPL 4.10.0002
SPL 4.70.Yang
Click to expand...
Click to collapse
SPL 4.70.yang!!! your device is HARD-SPL!!
So going back to stockrom--> delete the SPL.nbh from EVERY RUU you are running.
Then it shouldn´t stop......
Big Thanks papa! That did the trick. My Wing is happy once again and running Open Touch. But I still want to give TouchIt another try.
And what if i cant find stock RUU mine came with some arabic keyboard and spl was 1.08 , thanks to Oli he didnt mention that SPL should be 4 or higher , so device is bricked since first Olis release and no way to find this arabic stock RUU.
Any Help ?????
Hitec
If the device had an spl of 1.08 prior to HardSPLing it, then you'll have to bring the device to your nearest repair center. There isn't a way around that. Oli doesn't know everything and that's the risk we take when we try new and experimental things that people create but have no way of testing. But, we live and learn. If it wasn't for that issue, you could always cook your own ROM and if the HardSPL was working, you could've easily flashed any ROM. But the keyboard wouldn't been wrong until you could find someone who had the correct keyboard and you extracted the ROM from it and cooked that keyboard driver into your ROM.
Oh noooo!!
Hi ivanmmj,
I used your guide to flashing my HTC P4350 at http://forum.xda-developers.com/showthread.php?t=358615.
It was in French and I wanted it in English. So I downloaded one of the official HTC ROMs "HTC_P4350_WWE_4.17.405.2_4.1.13.44_02.94.90_Ship.exe" assuming this was the English one because all the others couldn't have been.
I copied the "RUU_signed.nbh" from the above HTC ROM and put it into the RUU folder as instructed by yourguide (I didn't copy the SPL.nbh file). I then ran the herald-uspl.exe and everything went fine until the RUU utility stopped with the error "invalid vender ID".
The RUU exited without completing, now all I get when the device boots is the screen giving my IPL (1.08.001) and SPL (1.08.001). How do I flash another ROM from this state? I can't do it the "normal" way because ActiveSync can't see the device. When I try to use the RUU tool that comes with your tool, the progress bar shows then it says the tool can't be used with my device.
Someone please help!
foo_bar_baz said:
Hi ivanmmj,
I used your guide to flashing my HTC P4350 at http://forum.xda-developers.com/showthread.php?t=358615.
It was in French and I wanted it in English. So I downloaded one of the official HTC ROMs "HTC_P4350_WWE_4.17.405.2_4.1.13.44_02.94.90_Ship.exe" assuming this was the English one because all the others couldn't have been.
I copied the "RUU_signed.nbh" from the above HTC ROM and put it into the RUU folder as instructed by yourguide (I didn't copy the SPL.nbh file). I then ran the herald-uspl.exe and everything went fine until the RUU utility stopped with the error "invalid vender ID".
The RUU exited without completing, now all I get when the device boots is the screen giving my IPL (1.08.001) and SPL (1.08.001). How do I flash another ROM from this state? I can't do it the "normal" way because ActiveSync can't see the device. When I try to use the RUU tool that comes with your tool, the progress bar shows then it says the tool can't be used with my device.
Someone please help!
Click to expand...
Click to collapse
Oh wow. I'm so sorry. I think I may have forgotten to put up a warning for people that have an SPL lower than 4.0. Was your SPL lower than 4.0? If it was, you cannot use the USPL OR the HardSPL and they end up writing part of the ROM over your current SPL and brick the device. This, unfortunately, needs to be fixed by your local repair center. I'll talk to the Mods about unlocking that thread so that I can update it.
ivanmmj said:
Oh wow. I'm so sorry. I think I may have forgotten to put up a warning for people that have an SPL lower than 4.0. Was your SPL lower than 4.0? If it was, you cannot use the USPL OR the HardSPL and they end up writing part of the ROM over your current SPL and brick the device. This, unfortunately, needs to be fixed by your local repair center. I'll talk to the Mods about unlocking that thread so that I can update it.
Click to expand...
Click to collapse
Oh deary me! I am so dead now - I live in Tanzania, East-Africa. My "local" repair center is several hundred thousand miles away across The Big Blue. What exactly do the repair center folks do to fix the device? Perhaps I can soldier out myself with some guidance...
Thank you,
foo_bar_baz.
Hello, a few days ago CMONEX give me the SPL for CDMA Shift, she guide me to installed on my CDMA Shift and everything works fine, if I run "ecshift –bl" the WinMobile shows the colours bars and says "SPL-0.14.OliNex"
I couldn’t contact CMONEX again, we couldn't continue with the tests, I guess she’s busy
Now, what’s next? I want to cook a new ROM, but I’m not sure if I’m going well
I followed these posts:
http://forum.xda-developers.com/showthread.php?t=382609
http://forum.xda-developers.com/showthread.php?t=422914
I already dump the CDMA ROM and cooked a new one using the Shiftkitchen
Before flashing the ROM I want to know how to restore the factory version of the ROM for Snapvue, I deleted the restore partition (to have more space) and created an USB flash drive
Is it possible to restore snapvue using this USB restore drive?
Should I use the CustomRUU.exe to flash the cooked ROM?
Any help for creating the first Shift’s CDMA ROM will be very appreciated
Regards
Hello, a few days ago CMONEX give me the SPL for CDMA Shift, she guide me to installed on my CDMA Shift and everything works fine, if I run "ecshift –bl" the WinMobile shows the colours bars and says "SPL-0.14.OliNex"
I couldn’t contact CMONEX again, we couldn't continue with the tests, I guess she’s busy
Now, what’s next? I want to cook a new ROM, but I’m not sure if I’m going well
Click to expand...
Click to collapse
As u said u have done your custom ROM already if you HARD SPL'ed you can flash it using CustomRUU.exe
I followed these posts:
http://forum.xda-developers.com/showthread.php?t=382609
http://forum.xda-developers.com/showthread.php?t=422914
I already dump the CDMA ROM and cooked a new one using the Shiftkitchen
Before flashing the ROM I want to know how to restore the factory version of the ROM for Snapvue, I deleted the restore partition (to have more space) and created an USB flash drive
Click to expand...
Click to collapse
Restore Partition has nothing to do with You ROM side !
You can cook a "default" ROM from your Part01-04.raw's
Is it possible to restore snapvue using this USB restore drive?
Should I use the CustomRUU.exe to flash the cooked ROM?
Any help for creating the first Shift’s CDMA ROM will be very appreciated
Regards
Click to expand...
Click to collapse
Snapvue again has nothing to do with the recovery Partition this is just for your VISTA.
So to get u updated should wait for cmonex but as you have an mfg bootloader (colored screen) you should be able to bump a rom to your shift !
Greets
thanks for your answers, I am in contact with cmonex, hopefully soon we'll have a CDMA ROM
regards
would u please upload the HardSPL for CDMA Shift??
youzii said:
would u please upload the HardSPL for CDMA Shift??
Click to expand...
Click to collapse
Would love to have the Hard SPL for CDMA
Also can anyone confirm which rom can be used for a CDMA Shift ?
Eight years later........
Hi, I've lurked this graveyard since picking up a clio110. I appreciated all of the resources, information, and most of all; The Search Tool.
Since then, I acquired a clio200. I didn't realize the difference and I've bricked the WinMo board. I can still access bootloader but it seems I need a file. The file was shared by cmonex to a few members in need. The file name is: "RUU_ATLA_HTC_SPCS_1.14.651.1_0.14_2.30.00_1.33_PRL60711_SHIP_MO_Disable_PPST.exe"
I've seen mentioned in a few threads but cannot find it on the Google Drives nor the internet at large. Would a kind soul happen to have this file and be able to share it? I'm really bummed because it affects the audio hardware on the PC side since the audio components are on the WinMo board. You generousity can bring generousity. There are probably others out there that need the file and have given up. I really like the device and would really like to be able to make it work again. Please.
Snap vue hard reset
Ive also just obtained a htc shift, but whilst thevpreviuis own had restored the vista side ok. The snapvue side doesnt work as they have forgotten the password. There used to be tools to reset this but unsurprisingly the links are dead. If any one could make them available it woukd be a lifesaver
Thanks in advance
Useless_Alias said:
Hi, I've lurked this graveyard since picking up a clio110. I appreciated all of the resources, information, and most of all; The Search Tool.
Since then, I acquired a clio200. I didn't realize the difference and I've bricked the WinMo board. I can still access bootloader but it seems I need a file. The file was shared by cmonex to a few members in need. The file name is: "RUU_ATLA_HTC_SPCS_1.14.651.1_0.14_2.30.00_1.33_PRL60711_SHIP_MO_Disable_PPST.exe"
I've seen mentioned in a few threads but cannot find it on the Google Drives nor the internet at large. Would a kind soul happen to have this file and be able to share it? I'm really bummed because it affects the audio hardware on the PC side since the audio components are on the WinMo board. You generousity can bring generousity. There are probably others out there that need the file and have given up. I really like the device and would really like to be able to make it work again. Please.
Click to expand...
Click to collapse
Sorry, I checked my HTC Shift archived files and I don't have this RUU_ATLA_HTC_SPCS_1.14.651.1_0.14_2.30.00_1.33_PRL60711_SHIP_MO_Disable_PPST.exe file that you are after.
Flanimal said:
Sorry, I checked my HTC Shift archived files and I don't have this RUU_ATLA_HTC_SPCS_1.14.651.1_0.14_2.30.00_1.33_PRL60711_SHIP_MO_Disable_PPST.exe file that you are after.
Click to expand...
Click to collapse
Appreciate the dig. I still have that board if that file ever surfaces. Maybe one day. I have a couple other GSM based units that I still enjoy to this day!