Having a small issue here. I just picked up a Juno (Tmo branded). Its completely stock, no 3rd party apps.
Anyway I'm trying to flash a new rom (clean rom, 6.1 rom..ect). When I start the flasher, it gets to 2% then fails. The phone reboots and operates normally. I get a error message on the computer telling me there is a problem flashing.
Im running vista sp1 on my macbook. I also tried this on a dell laptop (xp s2), same problems.
BTW: Software Ver on the phone: 1.03.531.4
did you CID unlock?
you might need to do that first so that you can run the Upgrade
Yea I'm pretty sure I CID unlocked it. Maybe I ran it a few times too many, I'm not sure.
I did get it to work. What I did was upgrade the "Official" FW first. I went to the tmobile upgrade site and got the updater from them and updated. That went fine, but it was still tmo branded fw.
The I ran jumpspl.exe, I guess that unlocked it. The unit rebooted but the screen remained off. I then ran the Clean Rom flasher and it worked. The progress bar never appeared on the device but it was on the computer and went up to 100%, device rebooted a few times, took a while each time as it did. Finally I had a usable phone
run jump spl then you upgrade your rom.
Related
hey guys,
ok running out of ideas, nothing is working.
upgraded to radio 1.43 yesterday which went fine. little while later saw phoen had frozen. rebooting showed me the no gsm error...
so i got going, followed all the instructions on the bricking threads without any luck.
its stuck in bootloader. i can flash an OS-only upgrade (been using windows black) which works fine, even LOADS windows when i reboot, but freezes (and gives the no gsm error on boot.)
however ANY other OS i try using, or even trying to upgrade hardspl or the radio gives a communications failure. so for e.g. if i get a radio upgrade, run it when the windows mobile is all up and runing, it'll go through the reboot process but then have a communication error once the status bar of the upgrade shows up (if at all). then when i reboot it only loads the bootloader, and even trying to change this using mtty has no effect - still only bootloader. trying anything from bootloader alone yields nothing.
IPL 1.01
spl 1.40 olipro
would appreciate any help you guys can offer. and yes, i've gone through the wiki and explored all the bricking threads and have not found a solution...
quick update on this: most likely more serious than i thought.
i downloaded the full htc rom upgrade including radio extrom etc etc:
HTC English QTEK_001 2.11.255.1 03/07/07 2.11.255.102 1.38.00.10 32.71.7020.12H 15673.3.3.1 3.3.1 1.11 108 Thread 1,2,3
as found in the wiki. it started upgrading, got to 13% at which point i'm guessing it starts the radio upgrade. at 13% it freezes and there's a communication failure on my pc.
usb cable is secure and intact, i know thats not the issue.
have i busted my rom or what??
Looks like the exact same issues as a number of people here:
http://forum.xda-developers.com/showthread.php?t=309079
Looks like there are enough cases of this from capable users for it to be looked into further? its not like we're all newbies and just mucking about... i've been flashing this device since i got it!
Hello everyone here:
I have bought a Cinglar 8525 about 3 month ago. Because enthusiasm of flashing rom, I start to flash rom one week after the purchase.
I flashed the hard spl v7,and flashed new OS rom image.
During the flashing, nothing special happened.
After two months usage, one time a software stopped responding, I thought it might be network failure or something like that and simply reset the device,then the nightmare began.
The device boot into bootloader automaticlly without the pressing of OK and Power button.I tried to reset the device by push the reset pin but it does not work, the device always boot into bootloader, after a few step of tring, it turns out the device maybe dead and I pull off the battery to make the device totally shut off, then install the battery again, and leave the device black screen.
After some time, I reset the device again , it boot into the OS this time. After some configuration that need reset , I reset the device ,but again ,it boot into bootloader.
So my device is very unstable now, even "fragile". Boot, maybe into OS, maybe into bootloader.
Can someone explain this? Or help me solve it?
some addional information:
I have flashed using card-flash method with the Manufacture Traditional Chinese Version( I came from China and the phone is origionally unlocked and I have hardspl v7 on it ).
After the flash ,the device can boot into OS this first time I reset the device, but after second reset,it still goes into the bootloader.
After a long time, I plan to flash one of the cooked ROM when I purchase the device, and ready to return the device the the seller to sort it out. But after this flash, the device just RETURN to normal ! I think it maybe back in normal and I have no execuse to return the device.So I start to use it normally.
After half a month of usage , the "bootloader mode" came again,similar steps to last time it "crash" ( device halt, reset, boot into bootloader ).
May someone diagnose this?
You're running wm6.1, aren't you? Try wm 6 as its more stable or if you wanna stick with 6.1 try PDAViets roms (19701 or 19900). They're english though....
Please note the "unstable" I mentioned is not something like halt frequently,application auto close up,etc.It's the bootloader stuff.
But I thought the problem might be irrevelant to the OS version, the "crash" occur first time when I use a ROM of wm6.0 and "crash" second time when I use a ROM of wm6.1
do some reading on wm6.1, it causes stuff like what you are describing....
After deep search in my brain, the "crash" might be occured during two version of ROM and both with wm6.1 .
Can you provide some link describing this problem of wm6.1 ? I just wondering if it is my device hardware failure or not.Or due to my some improper operation during ROM flashing process. Thank you.
Use the search function. There are a heap of threads... Some people recommend flashing a stock rom THEN flashing the wm6.1 of choice. This DOES seem to fix the problem.. Cheers...
yinx said:
some addional information:
I have flashed using card-flash method with the Manufacture Traditional Chinese Version( I came from China and the phone is origionally unlocked and I have hardspl v7 on it ).
After the flash ,the device can boot into OS this first time I reset the device, but after second reset,it still goes into the bootloader.
After a long time, I plan to flash one of the cooked ROM when I purchase the device, and ready to return the device the the seller to sort it out. But after this flash, the device just RETURN to normal ! I think it maybe back in normal and I have no execuse to return the device.So I start to use it normally.
After half a month of usage , the "bootloader mode" came again,similar steps to last time it "crash" ( device halt, reset, boot into bootloader ).
May someone diagnose this?
Click to expand...
Click to collapse
Please note this, I have done it before, I 'll do some search work.
Is there some evidence or something that the 6.1 rom of 19701 kernel has solved this problem ? I really like the thread function in SMS message in 6.1 so I want to stick in wm6.1 .
I have honestly only had problems with th 19919/19202 versions of wm 6.1. Tried 19900 with no problem and REALLY liked the speed. 19213 is SLIGHTLY faster and again no problems. Try ne of these if you MUST have wm6.1. The stability seems to get better and better as the chefs progress up the versions. Cheers...
Untill now I can't get my phone out of bootloader, I've flashed many ROMs including manufacture shipped ROM, but the phone still remain in one screen.Wondering if it can work out. Frustrated....
Start from 9:00 this morning I kept flashing my phone with different version of ROM, try to get out the bootloader,but still not working.
After a reset of frustrating "not working", I put down the phone,and do some other job,when I came back,I have transfered another ROM to the microSD and ready to flash the ROM.Before flash I thought "may I reset the phone again? may be the bootloader will go away", then I reset the phone as normal, after a while , the splash screen appear! I enter the OS, thinking the bootloader problem has go away. But when I complete some setting and reset the phone again, the phone finally fall in bootloader again.
So what ......
check for bad blocks using MTTY.... On upgrading section.
Cheers...
This I also have tried out. But I see no bad block on it, and I even do a forcibly fix to the NAND and with no avail.
I have sent the phone to a service center, it is said they might going to change a chip on the phone.
Wish my phone good luck.
I tried to flash a 6.1 rom to my shadow, but that was back in the day when my WMD did not work. When I tried to flash it, it got stuck in the bootloader mode. It took me awhile to research how to fix it, but eventually I got the re flash of the orignal t-mobile rom to work. Im wondering if I now that my windows media device software will work, if the flashing will? I'm a bit paranoid as I have no back up t-mobile phone and wonder if 6.1 is even worth it.
Also, the issue came because during the flash it said make sure it is connected to active sync, but I have WMD because I am on Vista.
What do you guys think? Should I be able to upgrade the shadow or should i just leave it alone
I bought a second hand O2 XDA atom exec recently. So far I like the phone, except it seems a bit sluggish sometimes (compared to my HTC harrier WM2003) and the wifi will NOT turn on. I tried using the O2 wireless manager, and the WM wi-fi utility. They both fail to turn the wifi on. The wifi self diagnostic returns "GetAdapterInfo() return FALSE..."
After doing some web searching I am aware that it has 802.11b. I figured that its probably a driver issue. From what I understand the only way to install drivers is to flash it with a ROM that has working wifi.
Im not sure whether to stick with WM5 or move to WM6.
My current:
WM 5.0 OS 5.1.195 (Build 14955.2.3.0)
Version:
CMOS: 55.44
ExtRom: EX0033
Hardware: C1
Radio: R060822N_MN2ARC_RS00013
ROM: 20060721B1WWE
Ive noticed that most ROMs don't state if bluetooth/wifi/FMradio is working, or which input methods work, (ie. transcriber, block recognizer etc). Is there a way to tell without installing it on the device first?
Thinking of using either: (it won't let me post links.)
wiki.xda-developers.com/index.php?pagename=ATOM_Exec_Upgrades (the WM5 roms)
forum.xda-developers.com/showthread.php?t=397725 High Performance Abusalza's in Blue WM6.1
forum.xda-developers.com/showthread.php?t=396799 ATOM EXEC WM6.1 20080417A6WWE ~ ULTRA LOW BATTERY CONSUMPTION [For Evaluation Only]
Any help or comments would be greatly appreciated.
Thanks in advance.
ROM upgrade froze at 73%
In fear of bricking my phone I decided to stick with WM5, I downloaded one of the official ROMs from the wiki. The update froze at 73% (I left it over night), so I downloaded another ROM (off the same page) and now its also frozen at 73%.
Anybody know why its freezing at that point?
Any advice to get my phone into a working state again? I'm thinking of trying a WM6 rom.
Im starting to wish I had done a ROM dump before I started.
EDIT: I forgot to mention, when I soft-reset the phone it says "Update Utility" and nothing more.
Tried a WM6.1, still gets stuck at 73%. Anybody know whats going on?
knoppies said:
In fear of bricking my phone I decided to stick with WM5, I downloaded one of the official ROMs from the wiki. The update froze at 73% (I left it over night), so I downloaded another ROM (off the same page) and now its also frozen at 73%.
Anybody know why its freezing at that point?
Any advice to get my phone into a working state again? I'm thinking of trying a WM6 rom.
Im starting to wish I had done a ROM dump before I started.
EDIT: I forgot to mention, when I soft-reset the phone it says "Update Utility" and nothing more.
Tried a WM6.1, still gets stuck at 73%. Anybody know whats going on?
Click to expand...
Click to collapse
mines is froze at the boot screen how to do i fix it any ideas
I had an O2 XDA atom exec and so far when i had i was able to use the wifi promptly without any hassle. I just turned on the wifi and searched a connection then poof, i started browsing the net already. The battery however drained fast. If you are having trouble with the wifi, as you have stated that it gives error issues maybe you should have it reprogrammed or check if first if you have open wifi connections.
theblogpostwriters.com
i got one recently. Wifi connection isnt going well. I did once connect it to my 802.11b network, but a few minutes later it doesnt and never able to connect successfully
confused
the developer itself doesn't provide the legal upgrade of 6.5, or i mustn't have known it..
knoppies said:
In fear of bricking my phone I decided to stick with WM5, I downloaded one of the official ROMs from the wiki. The update froze at 73% (I left it over night), so I downloaded another ROM (off the same page) and now its also frozen at 73%.
Anybody know why its freezing at that point?
Any advice to get my phone into a working state again? I'm thinking of trying a WM6 rom.
Im starting to wish I had done a ROM dump before I started.
EDIT: I forgot to mention, when I soft-reset the phone it says "Update Utility" and nothing more.
Tried a WM6.1, still gets stuck at 73%. Anybody know whats going on?
Click to expand...
Click to collapse
I rather think that you should first check whether your phone is really bricked, to read the instructions regarding this and to see how to recover from the brick click here!
After you have recovered you phone, I recommend that you use Windows Mobile 6.5!
Thanks!
Always glad to help!
My phone currently updating to version 7008 - needs update to Zune too which is downloading first.
Was on 7004.
Will let you know what happens!
I can't see any changes...
Also no saving of the changes you make in Camera or so on...
Is this the update before March Update!?
Yeah, this is just an update to pave the way for future updates. You'll find nothing new here.
skycamefalling said:
Yeah, this is just an update to pave the way for future updates. You'll find nothing new here.
Click to expand...
Click to collapse
Is the Camera any better...? could be into the realms of imagination here but took a photo and it seemed clearer than previous efforts on standard settings. Phone also 'seems' a little zippier.
Not totally sure so guess things aren't that different.
Backup worked nicely though.
Mine is in the process of updating. The backup process takes a while.
I wonder if we can use someone elses backup to restore a phone? I only ask because I flashed my UK T-Mobile device with the unbranded Samsung one because it was said that it fixed Bluetooth problems. However, it has had no effect, and now I can't take my phone back to T-Mo because it's not running the original firmware. If I can get it back to UK spec, then I can take it back to a shop and swap it for a (hopefully) working one...
Done. It is only a preparatory update for the actual update containing copy and paste, improvements to Windows Phone Marketplace et.al. Ergo, it doesn't contain any new functionality and won't remove or hinder any installed jailbreak functionality.
Yup, more playing, definitely no changes I can find...camera taking a better photo just happened to be a picture in better light.
This update has bricked my Omnia 7.
When I connected my Omnia 7 to Zune today, I was notified of an update. Zune updated itself and quit. I restarted Zune and it informed me there was an update for my phone. I clicked update now and it got to step 6/10 rebooting phone. The phone evenually rebooted and Zune reported the following:
RESTORATION ERROR
An error prevented the restoration of your phone to its previous version. Your phone cant be used in its present condition and there are no restore points for it on this computer. Thephone might restart and return to normal if you disconnect it. For further assistance, contact your mobile operator.
ERROR CODE C101002E
Thanks Microsoft, that's a really helpful message. NOT.
I have manually updated to the latest Zune, rebooted my PC, rebooted my phone, and I get the same thing every time.
THIS IS NOT GOOD ENOUGH MICROSOFT. My Omnia 7 is now a brick.
Loconinja said:
This update has bricked my Omnia 7.
When I connected my Omnia 7 to Zune today, I was notified of an update. Zune updated itself and quit. I restarted Zune and it informed me there was an update for my phone. I clicked update now and it got to step 6/10 rebooting phone. The phone evenually rebooted and Zune reported the following:
RESTORATION ERROR
An error prevented the restoration of your phone to its previous version. Your phone cant be used in its present condition and there are no restore points for it on this computer. Thephone might restart and return to normal if you disconnect it. For further assistance, contact your mobile operator.
ERROR CODE C101002E
Sorry for that. I was afraid of this happening to me when the update stalled at the 7th step
Thanks Microsoft, that's a really helpful message. NOT.
I have manually updated to the latest Zune, rebooted my PC, rebooted my phone, and I get the same thing every time.
THIS IS NOT GOOD ENOUGH MICROSOFT. My Omnia 7 is now a brick.
Click to expand...
Click to collapse
Sorry about that. I was afraid of this happening to me, after the update stalled for an hour at the 7th step, so I disconnected. Luckily nothing happened to my device. But apparently several Omnia 7 are experiencing this.
Sort it out, MS.
First things first. I was updated Zune to the recent version, because I was curious it will resolve a problem with login user on one of my computers. One (Windows Vista) works fine, but another one, Windows 7 (both 32-bits versions) works fine with Zune + Market.
Silent Shark said:
I wonder if we can use someone elses backup to restore a phone? I only ask because I flashed my UK T-Mobile device with the unbranded Samsung one because it was said that it fixed Bluetooth problems. However, it has had no effect, and now I can't take my phone back to T-Mo because it's not running the original firmware. If I can get it back to UK spec, then I can take it back to a shop and swap it for a (hopefully) working one...
Click to expand...
Click to collapse
I've done the same. I have (branded) T-Mobile UK phone and decided update to unbranded one. I choose version I8700XENJK1 (but I tried another one before) - for me, one difference is language Dutch / Belgium if I remember correctly.
I've read this thread and I was wondering if my phone will find update... I had no information about this.
I return home, connect Omnia to computer and update process start immediately. I had no problem with update at all. Phone during update reboots twice (or more) and it looks stable. I haven't noticed any changes or improvements... maybe it's working a little bit faster, but maybe it's a auto-suggestion.
Loconinja said:
This update has bricked my Omnia 7.
When I connected my Omnia 7 to Zune today, I was notified of an update. Zune updated itself and quit. I restarted Zune and it informed me there was an update for my phone. I clicked update now and it got to step 6/10 rebooting phone. (...)
THIS IS NOT GOOD ENOUGH MICROSOFT. My Omnia 7 is now a brick.
Click to expand...
Click to collapse
Sorry for that mate. I really had not problem with update.
Loconinja said:
This update has bricked my Omnia 7.
When I connected my Omnia 7 to Zune today, I was notified of an update. Zune updated itself and quit. I restarted Zune and it informed me there was an update for my phone. I clicked update now and it got to step 6/10 rebooting phone. The phone evenually rebooted and Zune reported the following:
RESTORATION ERROR
An error prevented the restoration of your phone to its previous version. Your phone cant be used in its present condition and there are no restore points for it on this computer. Thephone might restart and return to normal if you disconnect it. For further assistance, contact your mobile operator.
ERROR CODE C101002E
Thanks Microsoft, that's a really helpful message. NOT.
I have manually updated to the latest Zune, rebooted my PC, rebooted my phone, and I get the same thing every time.
THIS IS NOT GOOD ENOUGH MICROSOFT. My Omnia 7 is now a brick.
Click to expand...
Click to collapse
have you tried taking back battery and then reboot again?
http://twitter.com/#!/WinPhoneSupport
hard-reset Focus, should be similar to omnia 7
http://www.technipages.com/samsung-focus-hard-reset-using-hardware-keys.html
Update error
801012DD Error code - we couldnt create a backup of your phone
Help !!!!!
Have you got samsung tools installed?
I have tried twice to install the update. Both times I got stuck at 7 or of 100 with 100%.
The only thing I have done my phone is to unlock it with chevron.
Altough I did have it in flight mode at the time to prevent relocking.
Do you think that would have affected anything?
Still nothing showing up for me yet. Those who got the mini update does your 3 button combo into download mode now work if you had a phone that didnt let it happen before?
Lordao
lordao said:
Still nothing showing up for me yet. Those who got the mini update does your 3 button combo into download mode now work if you had a phone that didnt let it happen before?
Lordao
Click to expand...
Click to collapse
Three button combo now gives me the rather scary option to Format or Cancel. I thought Cancel would be the way to go....
Successful Updaters: Please post your Firmware revisions
For those who have managed to get the update installed without error, can you please post here your firmware revisions. We may be able to work out which models are affected by the issue.
There are rumours that this update only affects firmware versions JI9 and JJ4 while the JK1 firmware is unaffected.
http://www.zdnet.com/blog/hardware/windows-phone-7-update-bricking-some-samsung-omnia-handsets/11501
gc48067 said:
Three button combo now gives me the rather scary option to Format or Cancel. I thought Cancel would be the way to go....
Click to expand...
Click to collapse
Are you saying the Download Mode is no longer accessible after updating?
scoob101 said:
For those who have managed to get the update installed without error, can you please post here your firmware revisions. We may be able to work out which models are affected by the issue.
There are rumours that this update only affects firmware versions JI9 and JJ4 while the JK1 firmware is unaffected.
http://www.zdnet.com/blog/hardware/windows-phone-7-update-bricking-some-samsung-omnia-handsets/11501
Click to expand...
Click to collapse
How can I check which firmware revision I am using?