I've looked but can't find - 8525, TyTN, MDA Vario II, JasJam Software Upgradin

Hi, (again)
I've searched the forums(and wiki), but can't find out a few things.
Is it possible that if a hermes is only showing the windows splash screen that the OS is only part there?
Is there a way of seeing via a PC how far into its boot process it is?
Is there a way of sending just the OS to a bricked device? (preferably through the SD method)
What will the boot loader do with certain files, E.G we know about hermimg.nbh but what about autostart files? can we get the device to start the SSPL-HERM.exe file via the SD card in the bootloader?
I'm determined to get my hermes back from the dead, and if i manage it i will of coarse share the info, but if anyone else has any ideas/thoughts suggestions please let me know.

checking your post history, you have a corrupted CID type 2c brick. Very bad. Corrupted CID prevents SD image load. sspl method won't work b/c it is a Windows Mobile executable & you can't get OS to boot.
What bootloader version did you end up with (shown on tri-color screen)?

Worst kind, 1.09
I know i've got a very very slim chance of recovery, but even if it takes me months, i'm going to try and get it working, gives me a project if nothing else.

ouch
If in-place bl level 0 patch is developed you may find a way to unbrick...

Sounding like an idiot.....Huh?
What patch? Is there a thread link?
Thanks

It hasn't been developed yet Your mission awaits!

Related

Htc tytn dead

I was flashing my tytn with the new rom with bootloader 1.09 after 8% the usb cord came out and now my tytn is dead its stuck in bootloader mode..spl 1.09...please help
I am also in this boat, except my usb cord didn't fall off, it just stopped updating at 6%.
Connect to the device using mtty and type info 2. If you're CID is corrupt, then you're out of luck just like me.
It seems that the only way to fix this problem is to send the unit back to a service center and get the main board replaced. Unless anyone else has any other ideas. In BL 1.04 you could bypass the CID check but in 1.06 and 1.09 that bug has been fixed.
Great job HTC, you really messed everyone up now, I hope you're ready to start replacing some board on account of your ignorance to create a sufficient backup routine. I guess this means less money of new development and less devices from HTC in the near future.
Because you're in bootloader mode, you might be able to flash the 1.04 bootloader downgrader in; which would then allow you to re-flash any firmware.
Nope, even in boot loader mode I can't go back to 1.04. It doesn't recognize the CID and keeps saying invalid vendor id.
The only possible fix I can see is if someone hacks the hermes and finds a way to cook a rom and not check the CID. Otherwise, it's a full board replacement.
Somehow there has got to be a way to "Bypass" the CID check.
What I was trying to say, if you use the IMEI-CHECK downgrader it will bypass the CID checking enough to get you back down to 1.04?
Yes. Imei-check downgrades your bootloader to 1.04
sn00x said:
Yes. Imei-check downgrades your bootloader to 1.04
Click to expand...
Click to collapse
But to run imei-check unlocker you need a running OS (it needs to transfer files via activesync to the device) and your IMEI should be not screewed while checking it from bootloader. Otherwise it will not work.
I've tried everything possible to get out of bootloader mtty says my cid is corrupt.does anyone know a number for the service center
depends on your country, go into htc website and look at it:
http://www.htc.com
Pof you are correct. The CID is completely corrupt, the radio sectors have a bad record, and the phone can't boot past the windows mobile splash screen. So the only way we can fix this problem, is to hack the flashing of the rom to not check the CID at all. If this can be done, then we're in business.
On another note, I've been seen 1 of these problems arise every day now. Someone either pulls the usb cord or the flashing just crashes.
I think there is a serious enough priority to hack the hermes rom flashing now aside from crossbow. We really need some resources on this so that we don't ever have to go through these problems again.
In the words of Russel Peters (a famous Canadian comedian)... Pof, be a man, do the right thing. Hehehe.
pof said:
But to run imei-check unlocker you need a running OS (it needs to transfer files via activesync to the device) and your IMEI should be not screewed while checking it from bootloader. Otherwise it will not work.
Click to expand...
Click to collapse
But does that "other solution" which can't be posted here anymore bypass that requirement, as it runs through the bootloader and not activesync?
no it doesn't. The update still checks the CID before updating.
And it also needs activesync to transfer the fake bootloader to the device... remember it starts with M3100v3cUnlock.exe too....
Ooh, forgot about that bit .

trouble in paradise... why can't i flash roms?

first off let me start off by saying, yes, i'm a noob. i started out by reading all the posts in every thread i could. i have a x10ht that i bought at the local asian mall, not knowing that there were so many problems unlocking it
this is the second failed attempt at flashing a new rom onto my phone. i must say, i am not impressed. it froze the last time, i'm not sure where, and this time at 47%. kinda annoying when u think about it. i took the precautions and followed instructions, but to no avail
can anyone help? i'll give all the details i can...
bl 1.09
radio 1.14
old rom was 1.35
What state is it in now?
if i plug it in to the pc, it goes into bl 1.09
so, i was able to flash the old softbank rom onto it, but now i'm stuck with a japanese device with a sim lock on it(i think). i can't even set up activesync to try to update again. any ideas guys?
I don't have much xp with the ideosyncracies of the Softbank X01ht, but you should be able to build a sspl RUU featuring the os.nb of your choice. I believe you don't want to try flashing the radio ROM area but an os.nb only flash should restore the english version of your choice.
I'd look for confirmation on the above conjecture however, before trying these steps:
download the ruu of your choice and extract the signed nbh file using winrar or equivalent (the exe is an executable rar file)
use nbhextract or nbhdump to extract all the files
use Olipro's RUU builder to create a sspl RUU with only os.nb (use the 06_os.nb extracted from step 2)
flash this onto your device
This procedure should raise a lot of questions for you to research the answers to. The answers are all here I assure you. In researching, you will learn about the techniques of custom flashing for Hermes and whether they can really be used safely on your device.
Flashing the japanese ROM shouldn't have SIM locked you again. However, if it is you can research your free solution on this thread or you can purchase unlock from here.
Also: please explain what you mean by "Can't set up Activesync"
the only problem is right now i can't even access my device... there appears to be some sort of lock on it, something to do with usim and i have no clue what it says. but i can't do anything with it
Its probably saying the SIM is incorrect. You may well be SIMLocked....
You need to get it to the today screen to do sspl flashing. Try resetting with no SIM installed. the first thing you should see after the WM splash is the phone dialer saying "The SIM is missing" in japanese. Hit the cancel button which on my TyTN is the first labeled button above the green button to return to the today screen (you may have to experiment to find the right button).
i do get that, but after a few seconds, it goes to a screen where you can put in a code and there is writing on the left soft button, but you can't select it, i assume until a suitable length code is input, and it has no ok button, so i can't even get out of it... help!!!
and by can't set up activesync i mean that i can only get into the today screen for a very limited time, and activesync doesn't seem to connect fast enough, so i'm kind of stuck.
This happens when there's no SIM installed?
yes, it does. but i may have found out something. i can connect to my hermes through activesync on my work computer... hmmm... let me see here...
wow, that was an experience
so i think i'm good, i'll update you guys as teh day goes on, but i may have fixed this myself, and i feel so releived.
yes, the same usim message was coming up regardless of the way i started it up, but i had about 20 seconds of pda usage before it would come up. i got activesync working via the work laptop on the usim screen, and was able to copy sspl over, i restarted and quickly ran sspl, which got me into des's bootloader. from there, it was just a matter of running the ruu i wanted to run in the first place, WM6 .2, and voila, we seem to be back in business... but i don't ever want to do that again, so i think i'm going to flash that hard sspl... but first to test the radio's and and other features.... wow. last time the flash ****ed up on me, i had to pay this guy $30 to fix it, and tho he did, he never wanted me to know how so i could do it myself next time. screw him!!!!
thanks to everyone and their hard work on the forums here. without you, i'd be styling with a razr rather than hacking this thing apart like it was an xbox or psp....

Wierd Issue

Ok I have searched the forums pretty hard the last couple of days, and I have not found anyone that has the same issue as mine. It's not too big of a deal as everything operates but it is an issue all the same. This is all of course after I have succesfully ran HARD SPL v7 and upgraded to Black 3.0.1. Basically I decided to use POF's SuperCid Unlocker 3a (yes I know if I had HARD SPL 7 then why go through the trouble of Unlocking my CID, let's call it a need to mess with things) and everything went succesful. Then after the fact I read that it is still good even if you have SuperCID to upgrade the SPL to 2.10 and have read some peoples signatures and it appears that they have succesfully done this. Here is my issue;
When I run the CustomRUU it autodetects my SPL no problems, HARD-SPL? is checked, everything seems to go fine until it gets to the boot loader, once it is there, the progress bar pops up, zings to 100% and then reboots, cool? no because it didn't actually upgrade anything everything is still the same. Ok, so I tried the format SD card and rename *.nbh file to HERMIMG.nbh and put only it on the card, when I go to bootloader it does a quick flash to the screen like it recognizes the image but then goes to boot loader and nothing changes (the flash is so quick I can't even read whatever message it may be showing). I have tried pretty much every flashing method I can come across. MTTY wont recognize that I even have a USB port so I have been unable to try that method. So two questions:
I have SuperCID, so should I continue to even bother to get to 2.10?
If so, is there anything else I can try? Or do I need to get MTTY to work and try that as that is really the only thing left?
Thanks for any and all help anyone can provide.
PuckX said:
Ok I have searched the forums pretty hard the last couple of days, and I have not found anyone that has the same issue as mine. It's not too big of a deal as everything operates but it is an issue all the same. This is all of course after I have succesfully ran HARD SPL v7 and upgraded to Black 3.0.1. Basically I decided to use POF's SuperCid Unlocker 3a (yes I know if I had HARD SPL 7 then why go through the trouble of Unlocking my CID, let's call it a need to mess with things) and everything went succesful. Then after the fact I read that it is still good even if you have SuperCID to upgrade the SPL to 2.10 and have read some peoples signatures and it appears that they have succesfully done this. Here is my issue;
When I run the CustomRUU it autodetects my SPL no problems, HARD-SPL? is checked, everything seems to go fine until it gets to the boot loader, once it is there, the progress bar pops up, zings to 100% and then reboots, cool? no because it didn't actually upgrade anything everything is still the same. Ok, so I tried the format SD card and rename *.nbh file to HERMIMG.nbh and put only it on the card, when I go to bootloader it does a quick flash to the screen like it recognizes the image but then goes to boot loader and nothing changes (the flash is so quick I can't even read whatever message it may be showing). I have tried pretty much every flashing method I can come across. MTTY wont recognize that I even have a USB port so I have been unable to try that method. So two questions:
I have SuperCID, so should I continue to even bother to get to 2.10?
If so, is there anything else I can try? Or do I need to get MTTY to work and try that as that is really the only thing left?
Thanks for any and all help anyone can provide.
Click to expand...
Click to collapse
Did you look on the bootloader screen to see if your SPL changed? To my knowledge the only place you can see it is in the bootloader screen (tri-color screen) And flashing Olipro's Hard SPL only takes a couple seconds so it sounds to me like it is working as designed.
Or are you trying to flash a different rom? If so then try deleting everything you have in the directory you are using and re-downloading. You might have over-written the file you want to flash with the HardSPL one. You shouldn't be using the hard spl wrapper to flash a rom in any case, i believe that is mentioned in bold at the top of the Hard SPL thread.
Ok nevermind I was able to get it to work and MTTY was the answer. This is the 2 steps I had to follow:
From the thread: http://forum.xda-developers.com/showthread.php?t=291723
sp3dev said:
Hi. I`ve finally found the way to connect mtty and run rom update utility in Vista. tested on rtm 6000.
First of all, connect your device when it`s in bootloader.
next, open Windows Mobile Device Center and in connection settings uncheck Allou USB Connections.
next, goto contol panel-administrative tools-services and start windows mobile device connectivity and windows mobile device 2003 connectivity
next, goto device manager and find your device and update the driver to the one from AS 4, i attached it, wceusbsh.inf.
then, kill wmdc.exe with any taskmanager
You are Ready. run ruu or connect MTTY. I guess that vista default driver uses another port, not WCEUSBSH001, that`s why we have to use the old driver.
Click to expand...
Click to collapse
Then Do This:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootloaderMFG
Flashing SPL-1.01 MFG instructions
Put hermes in bootloader mode (side ok + power button + softreset)
Connect Hermes to computer using USB cable.
Open mtty.exe, select "USB" from the dialog box, then hit Ok.
Hit enter twice and you'll see the "USB>" prompt.
Then type these commands: (note the use of 'lnb*s*')
USB>task 32
Level = 0
USB> lnbs SPL-1.01.nbs 50020000
USB> task 8
Device will reboot after this, with bootloader 1.01-MFG on it.
Once I was able to do all this I was succesfully at 1.01 at which point I ran the Custom RUU and upgrade to 2.10 without issue. Once again all right there in the forums, just had to be pieced together to find a solution.
Thank you all for all your dedication to these projects, you make owning a PDA more fun than I am sure was originally intended. I love messing with things.
I have also attached the necessary files from the original posts to perform this for anyone else facing this issue.
PuckX said:
Ok nevermind I was able to get it to work and MTTY was the answer.
Click to expand...
Click to collapse
Cool, glad you got it working

Maybe easy fix for someone that is not me.

I inherited this device from a moron. So Moron --> Moron i suppose.
I am trying to flash any rom. I just flashed Schaps 4.40. Works great. It flashed with spl 3.00 from olio.
When i intentionally put it in bootloader mode, it goes to SPL 2.03
When i try to flash a ROM, it runs SPL 1.09, then returns with error 260 ( I have rebooted and reconnected, still same issues).
I am running Vista 64 bit. I have no idea what is going on. I get the same herror when i try to run the Hardspl7 loader.
Any help or ideas are greatly appreciated.
try flashing through the microsd card, see wiki for instructions
i shoudnt have to do the workaround with the storage card, that doesnt fix the issue. Isnt there a way to get rid of my outdated bootloader 1.09? That seems to be the problem here.
how the hell would you even go from spl2.04 to 1.09?? are you even freaking sure your spl is 1.09 and its not just the sspl?
use the sd card method and install hardspl, with it, i just posted a howto in the hardspl thread. if you still dont think you have to use this "workaround" then by all means go ahead and start troubleshooting, error 260 is an open port error, search for it, the step you should take to troubleshoot are out there
I'm in the same boat, when I do flash the boot screen shows SPL1.09. If I manually enter boot screen it shows SPL2.03. It did this after I ran the olipro sim unlocker and tried to upgrade it back to hard SPL V7
stesul411 said:
I'm in the same boat, when I do flash the boot screen shows SPL1.09.
Click to expand...
Click to collapse
yes yes, everyone who is running the upgrade using the force spl is also having this "problem".....unfortunately, there is no known fix for this "problem" cause i dont think anyone really wants to fix it.
XtreMe_G said:
how the hell would you even go from spl2.04 to 1.09?? are you even freaking sure your spl is 1.09 and its not just the sspl?
use the sd card method and install hardspl, with it, i just posted a howto in the hardspl thread. if you still dont think you have to use this "workaround" then by all means go ahead and start troubleshooting, error 260 is an open port error, search for it, the step you should take to troubleshoot are out there
Click to expand...
Click to collapse
It never was 2.04, it is 2.03. And i followed your directions:
"ok, lets see if i get this right.
1. download hardspl v7 from the first post.
2. extract ruu_signed.nbh and rename it to HERMIMG.nbh
3. copy it to a microsd card, make sure the card is formatted as fat32
4. download sspl-herm from here
5. extract SSPL-HERM.exe and copy it to your phone.
6. insert sd card and run sspl-herm.exe on the phone.
7. you should see the tri-color screen and then it should change to this
8. press power button to start flashing
9. reset when you get the msg that its done."
This did not work. extracted, renamed, extracted, ran sspl-herm.exe from the phone, and it goes to the spl-1.09.ds bootloader, and never changes to the other screen.
Why does no one want to fix this? How many others are experiencing this issue?
Thread has been renamed in order to classify the problem better.
http://forum.xda-developers.com/showthread.php?p=2055596#post2055596

HardSPL won't succeed

Hi All,
I'm new to the PDA-world and the Hermes. I'm trying to Hard SPL my Hermes, but it fails everytime.
When I run 2.10 - Hard-SPL-V7, it kills activesync and my connection is lost and I get always the message "error 260, Update error".
I have the latest framework edition and tried it on 3 pc's (1 Vista, 2 XP)...
What am I doing wrong?
Hope somebody can help me....
Kind Regards,
Micha
1). dont connect to active sync. open active sync and untick "allow usb connections".
2). put hermes into bootloader and connect to usb.
3). run ruu_wrapper.exe
should update to hard spl....
dont forget to tick "allow usb connections" again or you wnot be able to sync..
error 260 is an open port error.
if you wish to flash new os would advise to use sd card method. its safer than using the computer. just make sure you have greater than 50% battery power. happy flashing
Thnx, will give it a try.
First I have to flash HardSPL before I can flash a new OS, don't I?
yep, sorry, should have said run the ruu_wrapper for hard spl. My bad...
im having the same problem. I also tried the way ultramag recommended but i also received the same ending. After time i try i get the Error 260 Update error. Im running SPL 2.04 and the HTC WM6 rom from the HTC website. Does any one know what the problem is?
ultramag69 said:
2). put hermes into bootloader and connect to usb.
Click to expand...
Click to collapse
NOOOOO, that won't work, you need the SSPL to deploy to the phone, if you're running stock HTC bootloader this won't work at all, otherwise we'd have no need for Hard-SPL
hey olipro, then how would i fix this. Im running the stock rom from the HTC website with no hacks. Im trying to load PDA Corners V9 rom. Any ideas on how to fix? thanks!
Take a peek at the guide i wrote about updating the hardspl. Theres some explanation about why we need to use SSPL and the procedures.
http://www.mrvanx.org/hermes_guide/hardspl
thats the guide i used. it still gives me the error. I even unchecked "allow connections" cause i read somewhere that that would help.
i did this two days ago on my phone, im running windows vista on my home laptop and got any number of errors and problems trying to do it via sync with the phone (even after reading the vista troubleshooter, with the drivers etc)
What i ended up using was the memory card upgrade, dump the file onto the memory card and go into bootloader with the card installed.
worked fine doing that way, maybe less risky as there is no chance of the usb cable coming out.
just make sure you have a good battery charge on the phone.
Help Help Help w bricked 8525
I got into this position trying to upgrade WM5 to WM6 from HTC site.
Process got to 20% and just stayed there.
I reconnected usb cable and got a vendor id error
Then I get the Error [260]: CONNECTION
I have read a lot of posts and have tried the sd method (although i am not 100% clear) and all i get is the screen with four colors, red, green blue and white.
I believe this is the bootloader? I have downloaded RUU_signed.nbh, renamed it to hermimg.nbh, installed on root of my SD card and held OK, soft reset and power button:
My display reads:
HERM100
IPL-1.04
HERM100
SPL-2.03
This is where my journey ends.
All post indicate that the device can be reflashed and have the OS reinstalled. I can't get there from here.
Can anyone please help?
blackdog9692 said:
I have read a lot of posts and have tried the sd method (although i am not 100% clear) and all i get is the screen with four colors, red, green blue and white.
Click to expand...
Click to collapse
How big is your SD card? Flashing only works with cards <2GB. Also, sometimes certain cards just don't work for flashing, and just swapping to a different card fixes the problem.
I assume you searched the wiki, and found the relevant pages on the Hermes (including SD Card Flashing and other things about flashing/upgrading) there?
Still Lost
My SD is 2GB and I have tried many times but i just keep getting the 4 color screen. rt now when i boot from the SD my screen goes white and displays "Loading..." and then returns to bootloader screen. When i attempt to flash the rom via PC to WM5 or WM6 i get the Error 260, i also get a vendor ID error sometimes.
How can i find the key 8525 thread that i am told has the answer to my delima? I keep picking up bits and pieces but am missing some key steps and tips.
blackdog9692 said:
My SD is 2GB and I have tried many times but i just keep getting the 4 color screen. rt now when i boot from the SD my screen goes white and displays "Loading..." and then returns to bootloader screen.
Click to expand...
Click to collapse
That sounds like the SD card is formatted incorrectly. Make sure it's formatted using fat32, nothing else will work.
Still not there from here
Thanks for your help. Before I formatted the SD FAT32, nothing would happen doing the bootloader reset. OK/ON/reset button.
After format and only the hermimg.nbh file renamed as indicated, I then get what looks like the loading process but back to the bootloader screen.
Q1: This is an AT&T 8525, it was perfectly fine before failure from WM5 to WM6 (process froze at 20%), what is the RUU file that I need to put on SD??
Q2: After "Loading ..." I try the WM5 PC upgrade of ROM via USB cable, I get the load process to appear to work but it gets to 1% and the phone reboots and the PC reports error [294]: Invalid vendor ID. If I do this again I will get the Error [260]. Ive repeated the process several times.
Is this the normal course to take or should the "SD Method" (with the WM5 or WM6 RUU.. file) complete the process to a working OS?
Q3: Is my situation hopeless? ATT will take my out of warrantee 8525 and reflash for $129. Reading the threads it seems that like me this can be done by me, this is my desire.
Q4: I still am confused by some basic terms and assumed steps. I dont understand "Hard SPL" or OLI's IPLs/SPLs and when and when to use them.
The newbe guide has been off line. I will look again. Is there a single place to read about "radio PDAs and the 8525 and understand the software build and custom options?
Sy for the long post. But still want to fix if possible or I will be force to mail in for ATT repair.
Thank you all.
blackdog9692 said:
Q4: I still am confused by some basic terms and assumed steps. I dont understand "Hard SPL" or OLI's IPLs/SPLs and when and when to use them.
Click to expand...
Click to collapse
Oh boy, you haven't installed HardSPL? You are walking a bit of a line there mate...
HardSPL is a custom boot loader that makes bricking your phone when flashing much harder to do, and helps large amounts in the recovery process if you phone does brick.
Does the phone boot at this point? If so, do not try flashing the phone again. Go get a copy of HardSPL and install it, then try flashing from the SD.
I still wonder why people didn't read before bricking...
Anyway, you should start reading now and wiki is your friend. Your SPL is 2.03, so look at the bottom of the page (there is only one solution till now, so good luck with that):
Code:
1. Boot OS using KITL+PB
2. Do no disconnect your HERMES till the end of the step 6
3. Download SSPL on HERMES by wifi from ie explorer
4. Launch SSPL then flash Hard-SPL from your computer
5. Put your hermes in bootloader mode
6. Flash any radio in NBH format from your computer
Still researching and working this bricked 8525
Thanks for coming to my aide. I believe that I have Hard SPL'd my device. I downloaded Olipro's Hard SPL v7. extracted the RUU_ file and renamed to hermimg.nbh.
I then put it on an SD card and held the keys and reset. The device displayed a white screen and "Loading..." appeared. Afterward the 8525 returned to the stipped boat loader screen and that is where I am now.
Some of the help i receive and read on wiki threads has me confused with what to do next and how "exactly" to do it.
It does seem that I am not alone and people have fixed their phones and the process to do this is on the forum. I'm just still missing something.
Help me further if u can.
Thank you.
blackdog9692 said:
Thanks for coming to my aide. I believe that I have Hard SPL'd my device. I downloaded Olipro's Hard SPL v7. extracted the RUU_ file and renamed to hermimg.nbh.
Click to expand...
Click to collapse
FYI: bad form to PM someone and post the same thing here. Keep it in the thread so others can be helped as well.
As I replied in the PM, if I'm understanding your post correctly, the phone boots to the tri-colour screen?
What text is showing on the screen? This will tell if HardSPL is on the phone or not.
jdc said:
What text is showing on the screen? This will tell if HardSPL is on the phone or not.
Click to expand...
Click to collapse
We already know that the phone is without HardSPL, according:
My display reads:
HERM100
IPL-1.04
HERM100
SPL-2.03
This is where my journey ends.
Click to expand...
Click to collapse
There is small chance (read my previous post) to unbrick device with SPL2.03 so better try to get this back from where you take it.
And please, change topic, because this brick isn't HardSPL fault at all.
Edit: oh dear, it's even not your topic ...good game, I'm off

Categories

Resources