JasJar ROM update - Another brick hits the wall - JASJAR, XDA Exec, MDA Pro Software Upgrading

I have downloaded the new Shipping ROM update from ClubImate.com (uni_cdl-me_11238_132_10301_ship.exe) and tried installing it onto my JasJar with a horrible result: it's now only good to use as a paper weight Initially everything looked fine; the ROM utility detected the device and correctly displayed the existing versions of CE image, Device Extended image and Device Radio image, along with the versions it was going to upgrade to. It reset the JasJar (what I'd think was erasing the current versions), but has since been unable to install the upgraded versions. Result: a (virtually) dead JasJar :evil:
I have done the following in order to try and get it up and running again:
1) Several soft and hard resets - the best effort is a screen (with no back light) saying 'Serial' at the top and 'v0.60' at the bottom.
2) Uninstalled ActiveSync and tried reinstalling both version 4.10 and 4.1
3) I have tried to complete the upgrade procedure on two different PCs; one running WinXP SP2 and Win2K SP4.
Despite these efforts, the ROM installation utility is unable to detect the device (ActiveSync's device detection has been dodgy from the word get-go, despite WinXP detecting it every single time - although saying it's unable to identify it) resulting in the following error message from the ROM Update Utility:
In the Dialog's title bar: "R:3030 D:21200 U:11000 P:857873 - CB1" and the message "Error 101: Connection Error".
Please, please, please (with sugar ontop); can anyone of all you clever people out there offer some help or hope?
Thank you very much :!:

sure you did hardresets?
You´re really stuck in bootloader? strange... if it happens to me, i just do the standard hardreset: keep the 2 softbuttons pressed, resest with the stylus, and the confirm with 0 (zero). did you do that?

Yup - really stuck
Yes, I'm afraid the normal hard reset (Soft keys+Stylus reset) followed by entering '0' to confirm the reset, only brings me back to the boot loader...

same here

Help?
I had the same problem once with my himalaya and it was due to a firewall and virusscanner.
I turned them off- Look in your taskmanager that there isn't still running a service in the background. then I reinstalled the update and tried i new hard reset.
This worked for me I hope it will help you too
Good luck

1. pres ctl alt sup
2. kill wcesMgr.exe and wcscomm.exe
3. Connect your jasjas
4. Now your bootloader must show USB in the screen
5. Run the upgrade.
It should works...
Good luck

here it is
http://forum.xda-developers.com/viewtopic.php?p=161210#161210

Dear oddball,
Did you find solution to your problem?
I have the same problem!
dherrero's solution did not work for me.
Hope to hear another solution.
Thanks

Sorted...
First of all, thanks a lot to everyone who tried to lend a helping hand (what an absolutely brilliant forum this is!!! ).
However, neither of the solutions suggested worked for me, as I after lots more trial and error, worked out that the problem had to be hardware related. And I'm pleased to say that fault wasn't in the JasJar; in fact it was down to an un-original sync cable :idea: ! I managed to lose the one that came with the device (along with the CD and everything else that was in the box ) and after consulting Club imate support, was (obviously wrongly) told that any standard min-USB cable would do the trick. Ordered a new cable from where I bought the JasJar, and hey presto, problem solved. ROM upgrade worked without a hitch on first attempt - I didn't even have to disable my anti-virus or fire-wall software.
It might not be the solution for everyone else who seems to be struggling, but it worked for me, so if you've run out of options, it's worth a go.
Again, thanks a lot - and good luck to those still seeking a solution.

I have the sam problem
CRAP cant work it out

Hi,
Had the same problem..
- flashing ROM said 100% successful, but after power+reset still got "serial v1.00"
- tried different ROMs, no luck
- tried power and hard reset, no luck
- then tried JasJar ROM again, no luck
- but then I tried the radio ROM flash and the power-reset brought it to life.
So I recommend trying
a) just the radio update first, if no luck
b) jasjar THEN radio
See how you go.
Michael

my mda pro is be gone (turn on)
thank for everyone!
my jj is in bootload three day!cannt turn on
today i just update firmware of xda exec,finished! i do soft reset !my jj is be come back!
now i try update to cht! good luck!!

now my jj is cht!
if you want to update lanuage :
1:download rom and rar a new folder
2:delet firmware file
3:use no_id.exe to update,
maybe 5min finished ,it is fast!
then kick -and- and reset (hard reset)
now become cht version!
good luck

Related

Help! M5000ruu.exe load failed now now device!

Had a search but cant find anything on here to help.
Downloaded M5000ruu.exe from Orange.
Followed instructions, including sof boot of device.
Connected via AS,
Ran the install program again.
Install program halfway through complainied it could no longer see the device.
M5000 rebooted and now all i have is USB v2.01
Have tried removing battery, and done hard reset, with both options tried, but neither come back with anything.
AS ver 4.1.0. (build 4841)
USB was direct connect not through Hub.
What do I do now???
Thanks in advance! :twisted:
also happened by me. not with this rom. mostly hard reset several times will help/ otherwise reinstall this rom when this won't work ( what i did ) installed official qtek rom aku 2 later reinstalled new rom et voila...
good luck
Having read a few more threads I feel a bit happier that Im not the only one to have this.
Just tried again having left battery out for some time and seems to be going through now.
Scary as hell though
Thanks for your reply
remember: when updating rom remove phone sim AND memory card !!!!!!

When installing WM6, ActiveSync auto disconects. What to do?

Hello everyone.
I have just bought my Hermes (AT&T 8525) after one year of planing so. It came with WM5. I downloaded some of the ROMSs, radio and bootloaders commented here. I tried reading all the vast infromation in this forum and the wiki, but still having a problem.
THE PROBLEM IS AS FOLLOW:
When I start the flashing process, using HTC_TyTN_WWE_3[1].54.255.3_6275_1.48.00.10_108.exe or RUU_Hermes_CINGULAR_WWE_3.1.57.502.1_6275_1.48.00.00_108
... everything goes well, until the progress bar appears in my PC. When it appears, ActiveSync in my PC closes and my Hermes goes to stand by (the lcd goes off) so I cannot complete the installation process.
The phone works pretty well and I'm really amazed for all its capabilities. But still, I'm stucked with wm5.
Why do you think this happened?
PS: I flashed the radio (1.51.00.10) and bootloader (HARD SPL v7). My ROM version is 2.15.502.3. I use "ActiveStink" to sync my files without problems.
Any advice will be more than welcome!!
I'm no expert but that appears to be normal behaviour!
ActiveSync is only used at the start of the process. After a few files have been transfered, Activesync is closed and a different link is established. If you just leave it for a short while longer, a progress bar should appear on the Hermes too.
Yes, ActiveSync will disconnect. The RUU takes over the connection. Have you let it sit - sometimes it takes a minute for the progress bar to move.
Have you consulted www.mrvanx.org for help on the flashing?
todd_jg said:
Yes, ActiveSync will disconnect. The RUU takes over the connection. Have you let it sit - sometimes it takes a minute for the progress bar to move.
Have you consulted www.mrvanx.org for help on the flashing?
Click to expand...
Click to collapse
I'm having the same problem - always have. The message tells me that I'm disconnected and that I should check my USB connect etc. I left that box up there for about 15 minutes. Now I've closed the box and have waited several minutes with no activity. This is pretty aggravating. Thanks for any help.
try turning off your antivirus aplication. thats work for me flashing my tytn to wm6.
I've done everything.... I guess
Hi...
Yes, I consulted the www.mrvanx.org, excellent tutorials.
I flashed without problem the radio and bootloader. The progress bar started to "progress" and everything was fine. The only problem I have is flashing the WM6.
I don't remember where, but I readed that flashing the bootloader "Hard SLP v7" causes my HTC not to accept any Oficial WM6 ROM. The article said that I only had the chance to flash a coocked or modified ROMs. Is this true?
If not... what else can it be? I also closed all my applicacations including the antivirus, goback, disabled the internet connection, the logictec mouse center, etc. and nothing, the same as Chicoh happens to me.
"Error 260: Connection... check the USB cable bla bla bla."
Should I restart in safe mode to do the flashing?
Should I try to install a modified ROM?
Have in mind I've tried three different official ROMs: WWE, Cingular and spanish.
Thanks to all the comunity!!!
Saludos desde México!!
Greetings -
I had a similar problem and couldn't get the thing get going. My solution was to load it from the SD card. This worked flawlessly.
liquidsilver said:
Greetings -
I had a similar problem and couldn't get the thing get going. My solution was to load it from the SD card. This worked flawlessly.
Click to expand...
Click to collapse
I'm trying that as we speak. I have a good feeling about this. I'm a little concerned that I didn't think of it though. Makes perfect sense - Skip the middle man.
UPDATE: Crap. No luck. Thanks all the same though. I'm not giving up.
What OS are you using, xp or vista? My vista 'top had the same problem wouldnt flash for the longest time and i had to use my xp.
However, it does work now. Not entirely sure why.
Now I had success!!!
Hello my friends.
It seems that the article I readed days ago detailing that after flashing the Hard SPL v7, I could only install a modified ROM, not an official one from HTC or Cingular.
I downloaded Black Satin and installed it without any troubles. The entire process lasted only 3 minutes!!!
I wanted to have an official ROM, don't ask me why, and never tried the "other" ROMs that are actually excellent!!! some apps that were on WM5 are not in WM6, which is kind of sad, but if there's something that I love of WM Smartphones is that I can download and install whatever I want or develop it if it doesn't exist!!!
By the way, I use Windows XP Pro.
Thanks for all the support!!!
PS: Before flashing the Hard SPL v7, I tried installing the cingular WM6, but didn't make it. That's why I readed almost all the pages and threads here in xda-developers and found that flashing a new bootloader was a very good idea. The rest of the story is known by you.

Very Strange Brick Problem

Hi guys, I've read and used the forum for years and upgraded my Cingular 8525 a ton without troubles (followed Vanx's method for vista and for upgrading), but this is the first time I'm really stuck without a clue.
I had Schaps latest OS on my phone working fine for about three days. It was charging with the USB hook up to my Computer. I pulled the USB out and the phone entered bootloader. I couldn't get it out. I tried using mtty to no avail, hard reset ect., but finally used the SD loading method to put TNT's latest on it (don't know why this worked). Here's the thing though, the phone will load fine on first load after I flash, but if I soft reset or turn the phone off and on it goes right into bootloader mode. The only way I can get it to load up again is to connect it to the computer's USB, take out the battery and then put it back in. the OS then boots up without fail.
I have read a ton and searched on the forum, and if any of you can help me understand what the hell I can do to fix my phone I would really appreciate it. I will post anymore info you guys would like, I really need your help on this one.
Thank you so much!
Hi,
I posted exactly the same problem today ! here:
http://forum.xda-developers.com/showthread.php?t=381284
It's really strange !
Dave
I've been reading everything and it appears that Schaps's new version seems to have this problem sometimes....I have the exact same problem as everyone else (mtty gives me the same results), and flashing a new rom doesn't get rid of it....I hope there is some way to fix this!
maybe I'll try flashing a new radio and see if that helps things....
I did notice that flashing Schaps 4.31 seems to include radio 1.50 and I had changed my anyway to 1.43 as I thought that was better for my area.
Not sure a radio will help. Maybe a different ROM version will ? Maybe 3.54 ?
I have flashed TNT's rom as well and it still has the problem now....I'm flashing a new radio as I type, I'm going to have to reflash the OS too, it just got stuck again as it was restarting.
Just a quick thing, I think I have solved my problem (not sure if it is permanent) by powering the phone off and on. Not resetting, just a simple power off. I spoke to a colleague who said the way it shuts down is different to soft reset (makes sense) and I haven't powered my phone off properly for a long time.
I have tried soft reset a couple of times since doing this and it hasn't gone to the bootloader screen once.
Maybe this is the simple fix.
I will keep you posted.
try to flash OFFICIAL ROM first , maybe there are few bug / missing file when error appear while flashing other ROM.
I hope it will help you both.
rgds,
ermen
Use mtty to see if yo have any bad blocks... I've had a few problems the same as yours and found I had 1 or 2 extra bad blocks, after the 2 "factory standard" bad blocks I got on my jasjam of course. hope this helps...
My fix didn't work.
Not sure what I am suppossed to see when I run "task 2a".
Has anyone had any luck fixing this ?

Energy ROM semi bricked my Dash, help needed! (And appreciated)

Hello everyone, I am really new to this forum having received the Dash 2 days ago. Looking to get it up to speed I flashed the 6.5 Energy Rom according to instructions. I think that was a very bad move, because now the cellphone is stuck on the Loading Energy Rom screen. I have searched the forum for answer and have already tried the following:
1- Entering bootloader and flashing original ROM. No luck because EVERY rom I have gotten, be it from here and T-Mobile, it says invalid vendor ID.
2-Tried to perform a hard reset. Did not work.
3-Flash the original ROM through the memory card. No avail.
The phone cannot connect to active sync, so I can't install any cooked ROMS. I think the solution is installing the original ROM by the bootloader, but I cant seem to find a compatible one. My cell information is the following:
Bootloader screen info: ONBL 1.22.0000 SPL 1.22.0000 IU
EXCA 100 S/N SZ713FE05873.
Is there any way with that information someone can tell me which ROM to use? Or any other tip/hint/suggestion? Any help will be greatly appreciated!
I have the same Bootloader screen info: ONBL 1.22.0000 SPL 1.22.0000 IU value and i was able to restore my phone to working status with the following ROM
http://www.megaupload.com/?d=IJIVTIMF
Hope this help
10507
Thank you very much 10507! I'll download it now and see if it works.
Thanks for the file but it appears that it is for the SDA. It dit not work
luisro said:
Thanks for the file but it appears that it is for the SDA. It dit not work
Click to expand...
Click to collapse
That's odd, I was able to restore my Excalibur/Dash after flashing the corrupted EnergyRom.
Hope you will find a way to resolve your problem.
10507
But how did you do it? Flashing it through USB or through the memory card? The weird thing is that when I run the EXE the cellphone that appears in the picture of the program is an SDA. But well I will try it again and thank you for the help!
I used bootloader method and connected my phone through USB for flashing. Remember to remove your memory card when flashing.
well, I've been in your situation for almost 3 days now, and still no solution for it, maybe it's time to put it in the box and purchase a new one , all thanks to the broken EnergyROM ...
Ok guys. Don't give up. Believe it or not, a Dash is NOT easy to brick like some other devices. the steps are fairly clear but let me refresh:
- Go into bootloader by holding the camera button and powering on the phone
- Connect the USB cable, you will hear the ba-bing USB connect sound on your PC (if u don't thats why you're having issues flashing)
- Download and unpack a "factory sealed" signed ROM. I use this one: http://rapidshare.com/files/7886560...S_1.33.422.1_4.1.13.51_03.07.90_Ship.exe.html
- With USB connected and the phone in the multicolor bootloader, run RomUpdateUtility.exe, check the boxes, it next, bla bla bla.
- It will look for your device for 20 seconds. then hit "update" and next.
- It should then start flashing the Excalibur Brightpoint Factory ROM back onto your phone
- If you can't get this far or it fails, try a different PC or Flash from the SDcard
** NOTE: If flashing from USB, REMOVE the SD CARD! This is the biggest mistake of most people trying to flash from USB.
Good luck.
ookba said:
Ok guys. Don't give up. Believe it or not, a Dash is NOT easy to brick like some other devices. the steps are fairly clear but let me refresh:
- Go into bootloader by holding the camera button and powering on the phone
- Connect the USB cable, you will hear the ba-bing USB connect sound on your PC (if u don't thats why you're having issues flashing)
- Download and unpack a "factory sealed" signed ROM. I use this one: http://rapidshare.com/files/7886560...S_1.33.422.1_4.1.13.51_03.07.90_Ship.exe.html
- With USB connected and the phone in the multicolor bootloader, run RomUpdateUtility.exe, check the boxes, it next, bla bla bla.
- It will look for your device for 20 seconds. then hit "update" and next.
- It should then start flashing the Excalibur Brightpoint Factory ROM back onto your phone
- If you can't get this far or it fails, try a different PC or Flash from the SDcard
** NOTE: If flashing from USB, REMOVE the SD CARD! This is the biggest mistake of most people trying to flash from USB.
Good luck.
Click to expand...
Click to collapse
Thanks ookba for cheering us up. I'm having the same problem like many, many people in this forum hopeless seeing our dash not responding to every solution proposed in this forum and the only thing that we have right now is keep trying to flash and see if it works. I will try again in different PC and see what happens. I'll let all of you know if I finally resurrect my s621.
Thanks everyone for all the help! It's hard to find people that are so helpful on internet forums. I'm still in the same situation as gmaniac and alexalexoe but hopefully we can find something that will fix our problems
luisro said:
Thanks everyone for all the help! It's hard to find people that are so helpful on internet forums. I'm still in the same situation as gmaniac and alexalexoe but hopefully we can find something that will fix our problems
Click to expand...
Click to collapse
This problem is ridiculously weird to why some members are able to restore their phone to original factory condition, and others are not able. Therefore, I have search from trustworthy sites and from friends for difference made ROM. Hopefully, one of these ROMs with help out anyone...........
1.33.422.1 (Worldwide English, WM6)
http://rapidshare.com/files/7886560...S_1.33.422.1_4.1.13.51_03.07.90_Ship.exe.html
1.27.405.1 (Worldwide English, WM6)
http://rapidshare.com/files/100235639/HTC_S620_WWE_1.27.405.1.exe
1.22.531.6 (T-Mobile USA, WM6)
http://www.mediafire.com/download.php?z4vjgzxisrz
1.22.531.4 (T-Mobile USA, WM6)
http://www.mediafire.com/download.php?yygkw1d5xmc
1.11.531.1 (T-Mobile USA, WM5)
http://rapidshare.com/files/104641948/T-Mobile_DASH_WM5_V_1.11.531.1.exe.html
Excalibur_BRIGHTSTAR_PTB_1.30.514.2_4.1.13.47_ 02.98.90_Ship
http://www.mediafire.com/?9gbwdzd2omg
Thanks 105507 but no success at all, I even found 2 more factory roms in the web and also they don't work. I own an unbranded international version s621 manufactured by Brightstar corporation (I tried to flash Brightstar's stock rom but it didn't work) and I noticed this because in the warranty docs it says brigthstar corporation and originally the phone came with WM5.
not that this will help. but this is one of the reasons why people should be really installing the hardspl so if you have a bad flash, you dont have to install a stock rom. any rom whether be it cooked or not will work. but this hardspl must be done prior to installing ANY rom. the hard spl is done by jockyw2001. send him a pm to see if theres anyway to get that on the phone, even in its current state.
edit: here's the link to the hardspl: http://forum.xda-developers.com/showthread.php?t=329605
luisro said:
Hello everyone, I am really new to this forum having received the Dash 2 days ago. Looking to get it up to speed I flashed the 6.5 Energy Rom according to instructions. I think that was a very bad move, because now the cellphone is stuck on the Loading Energy Rom screen. I have searched the forum for answer and have already tried the following:
1- Entering bootloader and flashing original ROM. No luck because EVERY rom I have gotten, be it from here and T-Mobile, it says invalid vendor ID.
2-Tried to perform a hard reset. Did not work.
3-Flash the original ROM through the memory card. No avail.
The phone cannot connect to active sync, so I can't install any cooked ROMS. I think the solution is installing the original ROM by the bootloader, but I cant seem to find a compatible one. My cell information is the following:
Bootloader screen info: ONBL 1.22.0000 SPL 1.22.0000 IU
EXCA 100 S/N SZ713FE05873.
Is there any way with that information someone can tell me which ROM to use? Or any other tip/hint/suggestion? Any help will be greatly appreciated!
Click to expand...
Click to collapse
My phone is the same your phone but ONBL 1.33.0000 and SPL 1.33.0000
I'm trying to find the original rom of this line but not found. Please help me!
Have you done a reset? My friend fixed his by trying reset a few times. He reset it, walked away...., it took long time to see whether it booted over; if not, do it again...
By the way, he leave the sim card in; and, you need to remove your micro sd card.
On an official site it is possible download ROM for your phone. It is flashing from bootloder mode. It some times helped me, while I have not flashed hard SPL.
luisro said:
Thanks everyone for all the help! It's hard to find people that are so helpful on internet forums. I'm still in the same situation as gmaniac and alexalexoe but hopefully we can find something that will fix our problems
Click to expand...
Click to collapse
Hi my friend, I wish you lucky!!!
by the way, where country you're from, I have some Shipped Roms here for brazilian Excalibur (S621), maybe it could help, if the answer is yes, let me know to made this one come to you
http://wiki.xda-developers.com/index.php?pagename=Elf_GoldCard
Furious Girlfriend (oh My beloved Helloween died with my ROM's)
Boy oh Boy...
My ROM's are now in heaven
Girlfriend deleted they (I'm so sorry...)
But, pay attention in this thread
http://forum.xda-developers.com/showthread.php?t=381726
In there have a sort of shipped ROM's and maybe coud help you
Good luck my friends
A friend from XDA have some Shipped Rom's and will upload it for you, shortly he'll post something here

[Q] Touch Diamond :: permanent reboot :: bootloader update back to Stock SPL imposs.

Hi,
experiencing a problem with my Xda O2 branded German Touch Diamond:
after switching on the WiFi the device rebooted itself and continued to reboot permanently until I remove the battery. Battery is full actually.
I flashed the original ROM successfully (previous one was a BliZZard custom ROM v5), but the device is still continues to reboot.
For warranty reasons I need to flash the original stock SPL back, but no success with this. I flashed it couple ot times and the flashing CustomRUU.exe showed success each time. But after prooving the SLP it still shows 1.93.Olinex.
I tried also any other HardSPLs like Olinex 1.37... again the same problem. 1.93.Olinex is showed on boot.
Any idea how to solve the flashing problem or maybe also any hint about the reboot problem?
I have important stuff on the 4 GB internal flash. How can I read the contets considering the above problem?
Any help highly apprechiated!
Cheers
same problemm
Same problem. Any help?
tekata said:
Hi,
experiencing a problem with my Xda O2 branded German Touch Diamond:
after switching on the WiFi the device rebooted itself and continued to reboot permanently until I remove the battery. Battery is full actually.
I flashed the original ROM successfully (previous one was a BliZZard custom ROM v5), but the device is still continues to reboot.
For warranty reasons I need to flash the original stock SPL back, but no success with this. I flashed it couple ot times and the flashing CustomRUU.exe showed success each time. But after prooving the SLP it still shows 1.93.Olinex.
I tried also any other HardSPLs like Olinex 1.37... again the same problem. 1.93.Olinex is showed on boot.
Any idea how to solve the flashing problem or maybe also any hint about the reboot problem?
I have important stuff on the 4 GB internal flash. How can I read the contets considering the above problem?
Any help highly apprechiated!
Cheers
Click to expand...
Click to collapse
Any chance to MTTY? Might help, just guessing...
Or try to flash a new radio ROM as the wifi hardware might be stuck in a state that is unknown to the drivers. Flashing a radio is supposed to reset hardware but I may be wrong.
Really guessing here but symptoms shows relation to radio hardware.
Cheers,
Cina.
sspl
You need to run sspl first before flashing to the stock SPL. I did had this same problem changing my HSPL before.
You can find the sspl on the olipro CID/Security/Sim Unlocker, I think.
Hello, my solution to this was conductive interconnect of metalic parts as you can see here
://i.ytimg.com/vi/UUnH8O-1jII/0.jpg
(of course with http on the beginning, i'm not allowed to post links)
on the left with aluminium tape (sorry for image quality, found it on web).
It also seems that the sim card reader has to be conductively connected with the above em shielding.
Hope it will help
it´s a battery problem ... get a different one and your phone should be fine
Dreamtheater2003 said:
You need to run sspl first before flashing to the stock SPL. I did had this same problem changing my HSPL before.
You can find the sspl on the olipro CID/Security/Sim Unlocker, I think.
Click to expand...
Click to collapse
Please correct me if I am wrong. But as far as I understood, it is only possible to SSPL the phone after running the system on it (e.g. inside windows mobile) and not from outside (e.g. USB connection or so). The problem is, that I cannot access win mobile at all! It is continuosly rebooting in an infinite loop. Not even able to see the windows mobile logo at start.
@cina
how do I MTTY the phone? any idea, link, tool? again: if I have to be "in the system" in order to check, whats wrong, then it will fail.
@edefux
Do you already had such a case? I am not sure, if buying a new battery is economical enough only in order to try, if it works. I admit, it could be the battery. But running the phone with the charger switched on, should show if its the battery or not. I tried with charger on, but obviously this didn't solve the problem. Or do you mean, that in the battery there is some sort of "short circuit", that's confusing the Diamond no matter if the charger is on or not?
@DiamondFlower
Thanks for the suggestion. I'll give it a try, when I tried everything else
This will be the final try before burrying the precious Diamond.
Cheerz
MTTY.
tekata said:
Please correct me if I am wrong. But as far as I understood, it is only possible to SSPL the phone after running the system on it (e.g. inside windows mobile) and not from outside (e.g. USB connection or so). The problem is, that I cannot access win mobile at all! It is continuosly rebooting in an infinite loop. Not even able to see the windows mobile logo at start.
@cina
how do I MTTY the phone? any idea, link, tool? again: if I have to be "in the system" in order to check, whats wrong, then it will fail.
...
Cheerz
Click to expand...
Click to collapse
See this post for MTTY. This is the second post on Diamond ROM thread pinned for easy access anyway. Please search before you post!
If you can enter bootloader mode with VolDown pressed while reboot you're off to go. You can plug in USB cable and you can flash SPL, Radio or any new ROM. I assumed this based on your first post:
tekata said:
I flashed the original ROM successfully (previous one was a BliZZard custom ROM v5), but the device is still continues to reboot.
Click to expand...
Click to collapse
Cheers,
Cina.
it is a battery problem i´m 99,9% sure of it - i had the same case ... it was driving me crazy ... different roms, radios, but the problem persisted - luckily at that time i was working at a cell phone provider and could try different hardware, which finally brought me to the solution to switch the battery.
edefux said:
it is a battery problem i´m 99,9% sure of it...
Click to expand...
Click to collapse
Maybe I'm a bit unlucky, but I've got the 0,1%. Took a new battery, this didn't solve the problem though.
i´m sorry it didn´t work for you ... !
it's ok! it didn't work - actually I could have thought about it wont work: beforehand I sent the item to the mobile operator guarantee team and they returned it back - no warranty of course (due to olinex bootloader which I wasn't able to remove) and stating: Fremdeinwirkung/ Totalschaden (total loss). And because I sent it without battery and they obviously checked it ... suppose with a fresh or "good" battery. And it still didn't work for them, so...
I'll try to open it and see if there is some short circuit around the metal shielding. Maybe I'm lucky then.
Anyway thanks guys about the hints and suggestions!
tekata said:
Please correct me if I am wrong. But as far as I understood, it is only possible to SSPL the phone after running the system on it (e.g. inside windows mobile) and not from outside (e.g. USB connection or so). The problem is, that I cannot access win mobile at all! It is continuosly rebooting in an infinite loop. Not even able to see the windows mobile logo at start.
Click to expand...
Click to collapse
I'm not sure if its called sspl but you can run it from boot loader and it will black out your phone. after that you need flash the new bootloader.
I'm thinking its not a bootloader problem though...

Categories

Resources