Heey xda,
I have a big problem here. I am on the point to kill this phone!
I did something like "touch screen firmware update v2.0" in the EM screen. Everything goes oke, till he automatic restarted. After the restart I am not able to hit the screen.
When I touch the screen it restart again.
Please someone help me!
You will have to do an FFU reset. Look at the "I bricked my phone" thread.
I am really new with this :S
No idea what you mean, I dont know anything about WP7 MANGO..
Which programs I need?
Please, if someone can help my I will donate for him!
I really need help.. I can get the master reset with buttons working it always jumps to recovery mode and the support tool doesnt work with it :S
I was able to install an costum .ffu on my windows phone (its from T-Mobile, not original mine is perm unlocked).
Everything goes oke, Till I update to MANGO 7720.
After that my WP crash when I hit touchscreen again
I have exactly the same problem
I have exactly the same problem. Please, can anyone help me?
Thank you
So the touch screen is working before Mango?
If so I suggest calling up Dell. They might have a different FFU file or files that can fix it. You will need one that reflashes the touch firmware If they do please post them here. Otherwise you might need to have your phone swapped out.
Touch screen working on mango. But I have install "touch screen firmware update v2.0" in the EM app and now phone restart always when I touching screen.
I try wrote to Dell support so I see what they reply to me.
Thank you
That is what I mean. Does the phone crash/restart when when you touch the screen on pre-mango?
---------- Post added at 03:11 PM ---------- Previous post was at 03:08 PM ----------
Beacuse if it is, go into the EM and downgrade the firmware to 1.6. Otherwise I can give you a program you can run on your desktop that will launch the EM app and hopefully allow you to click in there.
On pre-mango everything worked fine.
Please, can you give me this program? I thing, downgrade "touch screen firmware" in EM will help me, but now, I can't do it.
Thank you
Attached is the EM Launcher
My phone is not developer unlocked. Can you tell me what I have to do?
Thank you
Hmm then you are probably screwed. Call / email Dell.
This: ( http://forum.xda-developers.com/showthread.php?t=1411300 ) guide help me unbrick my DVP, everything worked fine on firmware version 7004, I can upgrade to 7392 and still worked fine, but when I upgrade to 7720 touchscreen again stop working. Any idea how to fix it?
Can I developer unlock my DVP on FW 7004 - 7392 and upgrade to 7720 with preservation developer unlock to use EM launcher and downgrade "touchscreen firmware" to v1.6?
Thank you
If you upgraded your firmware downgrade it prior to 7720
I already stopped to try get it working again..
It just screwed us xD
I bought a Nokia Lumia 800
Has anyone managed to figure out a fix for this for non developer phones? The only way I think this would be fixed is when Dell delivers a firmware update, which hopefully comes when Tango is released, but I don't think a firmware update will come until Apollo, and we're not even sure if that's going to happen for Gen 1 devices.
Solved
Hi, I had the same problem in October. I bought the phone, updated to Mango, played with it, played with EM. And bricked it by updating touchscreen firmware.
A few days later I managed to fix it.
So
1. Restore the previous soft from your Zune (before 7740)
2. Go to EM and "update" the touchscreen firmware to the old one
3. Update to Mango again
FIXED!!! At least worked for me
eugenie said:
2. Go to EM and "update" the touchscreen firmware to the old one
Click to expand...
Click to collapse
Can you give me the exact steps to downgrade the firmware back to v 1.6 in the EM app please and is it in a certain OS version? I've been dying from the lack of apps because they are only supported by Mango ):
There are plenty of tutorials on how to access the EM mode here.
Related
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?
I have a HD2 running wp7 7392. Really want to get mango. Have tried to force (phone airplan mode, laptop wifi off, plug and unplug ethernet cable). I have tried for 3 days and I have done this maybe 200 times. If I pull too quickly,
within a second, I get connection error. If too slow, 2 or 3 sec, I get "your phone is up to date" And I have tried every ms in between but never was able to get the upgrade! Does anyone else have this problem? Do I have to push deviceprovisioning.cab? I did not have to push this cab and was able to get 7008, then 7392 all through zune. But this time I just cant force. Also looking at the microsoft site, t-mobile phone are already in delivery phase! Drive me nuts! Any advise?
Let's see if I got it right you're on NODO with back to the future v2 and waiting for the official mango update?
Then the solution is quite simple: READ the rom thread! It's in the second or third post...
Anyway, here's the solution:
If you can wait for the official update (it's not out yet!), wait
If not (very likely!!), you've got to send deviceprovisioning.cab to get developer updates and then: just continue updating with zune and it should work just fine...
(or you can use the update cabs provide by xbmod...)
But however you're going to do this, read the rom thread. It's better for you, for your phone (much safer!!!)
upate: I can't wait any longer, so I pushed the deviceprovisioning.cab onto the phone. Right away, zune tells me that there is an update available (7403).
I am in the middle of the 7403. Looks hopeful. Just want to update so other who are stuck at the same place could benefit.
HD2 stuck at 7403, fix!
Hi All! Since august 15th 2012 my HD2 has been stuck at WP7 7403. Tried the force Mango trick very often, but didn't succeed. Very frustrating.
I found my solution in this topic, thank you chabun!
With WP7 Cab Sender I send Deviceprovisioning.cab wich I found here: http://forum.xda-developers.com/showpost.php?p=20696473&postcount=4498
After sending Deviceprovisioning.cab Zune showed an update (7720) wich I am installing right now. XDA did it again for me, tnx folks!
I went from v2 - 7004-7392cab -devicepro.cab- zune to 7403 - 80004005 error trying to install isv 7720.
Looked all over the internet for this code and somebody found a solution on this website(half way down the page)...it relates to a samsung device but if somebody can explain how do i apply this to hd2??
http://answers.microsoft.com/en-us/...o/60e728c6-2cfe-47fc-a996-344a9d1c2c0d?page=2
Ps i try cab 7403 to 7661 but fails with error code straight away..WHY?? Do i need devicepro.cab again?? What would be your advice /route if i wanted to try the cab install to mango? Detailed guide would be awesome
Im running out of patience now i think
Why dont you try to flash your device over Zune?
Just install V2 ROM and then follow the instructions and update via Zune.
Rosetti you couldnt have said better. I Updated All Through Zune. DeviceProvisioning.cab is needed for going from NODO to MANGO.
Yeah dude do it over Zune the last stages are way easier over zune
i can't believe i tried everything else but not this method...thanks all ..i will report back later 2nite..
I dont believe it!
all week i have been messing around with cabs files as people were constantly reporting errors with zune thats why i decided to avoid it but il be damned!
process took around 2hours from start to finish..still got cleanup to go but i rather get some sleep..
i just went from 7403 rom .turned phone off
format sd card
enter magldr - clear and enable stuff
usb mode
flash v2 rom
set up date and time
zune found february update
zune found 7392
Send devicepro.cab via cabsender
zune found 7720 took fooking ages
zune finds cleanup - gta wait till 2mro thou..
not one trick applied ie hard resets/change time zone/reserved space/virus off
it was as simple as that..good nite!
i followed yuki v2, then force update with zune i got 7xxx (forgot) then again force update i got 7392 but then i cant force it anymore to get 7403 (before final force to 7220). i tried 1 sec then pull the internet cable. no success. tried 3,4,5 secs, also no luck. comments?
Once I succeeded in installing Mango on HD2, but then I realised that it's not unlocked. So I flashed my phone again... and now I'm stuck on 7008 and Zune's not giving me any update.
Can you please help me? My hair is all grey
Matt.Murdock said:
Once I succeeded in installing Mango on HD2, but then I realised that it's not unlocked. So I flashed my phone again... and now I'm stuck on 7008 and Zune's not giving me any update.
Can you please help me? My hair is all grey
Click to expand...
Click to collapse
Have you tried forcing it??
I did and it worked now... (not before, didn't get the right timing)
Matt.Murdock said:
Once I succeeded in installing Mango on HD2, but then I realised that it's not unlocked.
Click to expand...
Click to collapse
How did you realise this, Venerable sir? Did it say it in toms xap(number of reasons)? Did you try to send dev-unlock-remove.cab then dev-unlock.cab?
You might have saved yourself some trouble and hair dye
Matt.Murdock said:
I did and it worked now... (not before, didn't get the right timing)
Click to expand...
Click to collapse
I have to say, I tried every possible timings (all between 0 and forever). Don't work for me. Worked with the NODO update on second try. Mango - no chance.
*edit: Don't know why. Yesterday cab sending did not work. Gave me an error. Went to bed. Just thought I'd give it a nother shot - worked. Sent the .cab and Zune found the update for my Phone instantly!
Now all I am lacking is the activation key - waiting for the replay by MS.
Thanks to all, that made this possible!
**EDIT²: Now after finding the update, and installing the first step to Mango, I get stuck at the CLEAN UP update. Can't get it solved. Any suggestions?
Hello guys,
I have a "small problem"
I upgraded my phone to wp 7.8 using seven-eighter, it all worked, wp7.8 looked great until i figured out i can't go to "about phone" its instantly kicking me back. The same thing is when i try to enter any thread it just kick me out instantly to main screen.
And i have no idea what to do. I tried soft reset (vol- vol+ and power) and it didnt work. I tried also to restore backup from zune. I have now older version of wp, but still can't go to messages or info about phone.
I found one or two information about this problem after updating mozart... but thats all, no solution. Any one have any ideas how to fix it?
If i posted this thread in wrong section im sorry. I just don't know where it should be.
Thanks
Hello. Have You managed to solve the problem? I have completely the same situation, and nothing seems to help it. I've tried with SevenEighter_LanguageRestore but it's the same!
I Have german version of the software, and it comes with Vodafone.
You forgot to update the languages/did not update your language correctly.
Go here http://forum.xda-developers.com/showthread.php?t=1306415
and send the correct language cabs to your phone using cab sender.
Hello,
I just applied the latest update C432B185 on a 8 pro honor; it remains blocked at restart. Another user reports an identical problem on the FRANDROID site.
Do not apply this update because the problem is blocking; you will no longer be able to use your honor 8 pro.
Solution on hold.
Thank you
I have the exact same problem. I started the update, and put it back in my pocket. I grabbed my phone after a few minutes and blindly touched the fingerprint sensor and pressed where normally the home button is. Instead, I catched a glimpse of a black screen, a triangle and a button. The button was at almost the same spot as where the home button normally is, so I clicked it and my phone restarted. After that, the only thing my phone does right now is show the white Honor logo with a lightblue blackground.
I already tried everything that can be done, I think.
Restarted the phone 20 times, did a 'user reset', cleared the cache 20 times and did a lot of factory resets (sometimes stuck at 99%).
Nothing made my phone work again. I also tried to use eRecovery to 'Download latest version and recovery' but that only resulted in 'Getting package info failed'.
If someone has any clue to what can be done to revive the Honor 8 Pro again (or to see some kind of logs to view what's going on), please... help! :crying:
The topic on Frandroid that Pascal was talking about: forum.frandroid.com/topic/261525-mise-%C3%A0-jour-qui-plante-le-smartphone
Hello,
I have exactly the same problem with my honor 8 pro.
I can't use it anymore, the user reset is staying 99%
If someone has a solution...
Also had the update, tried everything, wanted to flash other rom but i haven't got my product ID to unlock the bootloader.
Worst part of all, there is no care centre in The Netherlands...
so what im suppose to do? not sure at all, eRecovery fails,
using the dload method fails.
nothing seem to work atm...
Thank you for sharing this. It's not released in India yet seems but disabled the auto download update over wifi feature just in case.
Also, I can't connect to the phone with ADB or fastboot. /adb reboot recovery returns error: device unauthorized. This adb server's $ADB_VENDOR_KEYS is not set and ./fastboot getvar all returns FAILED (remote: Command not allowed). HiSuite (never tried before) can't find my phone on OSX and crashes after 5 minutes.
No root, no unlocked bootloader. Also shows FRP is locked.
Same here (france) Factory reset doesn't work, dload method doesn't either and the WIFI update doesn't find anything so I'm stuck with no phone for the moment :'(
Same here (Poland). Phone is bricked, second visit in service within 2 months :/
Oh ,god, i was about to let people know that a new update b185 had just come up until i see this post...I immediatly stopped the downloading process of this Update, so bad news for the ones who already applied the update and who got stuck now...
There might be an ultimate solution for bricked phone by using the DC Phoenix unlock software method...
Same Problem with the Honor 8Pro update
Hi,
Same problem in the Netherlands, Brabant.
Just downloaded the update for the Honor 8Pro.
Tried everything, also the eRecovery, Same problem with the package Failure.
Also E-mailed to HiHonor for an sollution, nothing so far.
Somebody got any tip? Can miss my phone for work..
Greeting from Oss, The Netherlands.
Same problem
Same problem here in The Netherlands. Literally nothing works. Never even rooted this device or anything like that. Also, what is this "download and recovery" in eRecovery even for if nothing downloads? I am very disappointed in this. Have no idea what I should be doing while normally I find a way to work around such problems.
TheVeeeMan said:
Same problem here in The Netherlands. Literally nothing works. Never even rooted this device or anything like that. Also, what is this "download and recovery" in eRecovery even for if nothing downloads? I am very disappointed in this. Have no idea what I should be doing while normally I find a way to work around such problems.
Click to expand...
Click to collapse
Zelfde probleem hier en nu een onbruikbare telefoon...
Nog geen half jaar oud!
Ik heb net Honor gemaild .. even afwachten tot morgen..
Sterkte alvast!
Thank you for the warning!
flash a stock rom by -=MoRpH=-.
these are factory firmwares and reset your device back to full stock, yes, even with locked bootloader!
Regards
OldDroid said:
flash a stock rom by -=MoRpH=-.
these are factory firmwares and reset your device back to full stock, yes, even with locked bootloader!
Regards
Click to expand...
Click to collapse
I have explicitly chosen to not root or otherwise mod my phone just yet. Does this void your warranty? Right now, I can send it back to the supplier and they will fix it. Of course if something else is faster (supplier says max. 3 weeks) then I am happy to try, if it does not void my warranty.
EDIT: and also, how can I see which version I need? I don't know how for sure which version I have, and of course I can't get into the UI anymore. As I posted before, ADB and Fastboot don't give me any info.
OldDroid said:
flash a stock rom by -=MoRpH=-.
these are factory firmwares and reset your device back to full stock, yes, even with locked bootloader!
Regards
Click to expand...
Click to collapse
Hello,
that didn't work.
:crying:
Krystal666 said:
Oh ,god, i was about to let people know that a new update b185 had just come up until i see this post...I immediatly stopped the downloading process of this Update, so bad news for the ones who already applied the update and who got stuck now...
There might be an ultimate solution for bricked phone by using the DC Phoenix unlock software method...
Click to expand...
Click to collapse
Thank you.
I have made use of many Huawei phones in recent years (Mate 7, Mate 9, P8 Lite, P9 Lite) and Honor 8 Pro. I quickly realized that this update was blocking; it was common sense to inform users of the Honor 8 Pro in order to limit the number of service returns, unnecessary time wastage, etc.
This is our precious ...
Welcome
Here in Holland this morning the same problem.
Thanks for the Info. No update notice for my phone (in Germany). Hopefully Huawei/Honor will have stopped the update rolling out. Jeez, don't these updates get tested before they're released?
You can use Firmware Finder for PC to send an update for installation via erecovery with changing your routers DNS.
Erecovery is used in customer services to install manually sent updates only. That's why it can't find anything without sending an update to your device.