Curious that I see no reports of install problems with Mango on the Dell....yet, especially with those coming from any of the Beta's. Has anyone seen any reports anywhere?
I'm here to report 1.
I was on Mango release build. I flashed back to 7004, and followed the update path to 7008, then 7403 then the release build.
When completed, the VP is in a reboot cycle triggered by any touch. I've done this several times.
The reboot cycle appears as follows:
The update completes with no error and the final reboot starts. On reboot, if no sim is in place, the sim error screen appears. This is normal. Touch the screen to close, forces a reboot, regardless of the update complete message.
Repeat process, this time with a sim in place, Update is installed, success messages appear in zune and on the phone. Disconnect phone, touch the screen, reboot occurs.
Repeat process. let the phone reboot until it reaches the desktop. connect via cable to zune. The device is recognized, but NO sync occurs. Go to settings/update and the current build is recognized. Restore is available, and will work.
if the screen goes dark, slide up or touch power will bring up the Lockscreen. Wifi does show, so does 3g and battery, but NO lockscreen release options are available. Again, any touch forces reboot.
I've reported to Microsoft, but was not considered serious since it cannot be reproduced.
Did the update with my HD7 so Zune, the downloads, etc are in place and working.
Getting back to 7392 is an option, so I am not dead in the water. But wanted to make sure reports of problems with the update were reported.
Since I flashed back to 7004, I lost the firmware updates. I noticed that the subsequent updates do NOT flash any firmware. According to MS EULA, all updates are cumulative...contain all previous updates. I have flashed from 7004, to 7008, to 7392 to 7304. During none of these flashes has the firmware been updated. the 105 firmware is maintained. I thought I read that the 7420 update included the 219 firmware....
anyone else having this problem?
http://forum.xda-developers.com/showthread.php?t=1280097
Please read my problem I have encountered and how I have solved, hope this helps.
After step 6 while trying to install Mango I recieve error code 801812c1.
I faced a problem while updating to Mango via Zune software.
My phone kept restarting while installing 7.10.7720.68 update. Stuck in step 8/9 for about 30 mins.
I did the following to recover, nothing worked.
1. I guess my phone got bricked, stuck in an infinite restart loop. I cancelled my update and removed the data cable. Removed battery and put it in again, tried restarting, still in infinite loop. Thanks DELL & Microsoft!
2. I read in Dell forum that I have to turn off my phone, then hold down Power Button + Volume Down + Camera button to enter PC download mode, so that I can restore it from Zune software. Trying it now.
3. Restore from Zune doesn't work, even its stuck at 0% for about 30mins.
4. After a few tries, removing battery, removing the SIM and doing some random stupid stuff, tried again the restoration seemed to work, I mean it started to restore.
5. Finally, I guessed its time for me to give up. Restoration failed with Error Code 8018009B. So its bricked for now.
6. I was greeted with this nice message from Windows Phone support tool
"Communicating with device. Please wait for Recover button to be enabled.
Support Tool version 4.8.2345.0
The tool cannot recover this phone. Please contact technical support."
I didn't even force the update, it was regular update which I was able to start from Zune without forcing it. NOW ITS BRICKED!
7. I took my phone to Dell Service Center, those guys couldn't figure out the problem, they said its a new phone here in India and don't have any technician to fix it.
I posted the same in Engadget, I got no response from anyone, so am posting here hoping to get a solution. I at least want my phone working, I'm happy without mango.
theonlyremedy said:
I faced a problem while updating to Mango via Zune software.
My phone kept restarting while installing 7.10.7720.68 update. Stuck in step 8/9 for about 30 mins.
I did the following to recover, nothing worked.
1. I guess my phone got bricked, stuck in an infinite restart loop. I cancelled my update and removed the data cable. Removed battery and put it in again, tried restarting, still in infinite loop. Thanks DELL & Microsoft!
2. I read in Dell forum that I have to turn off my phone, then hold down Power Button + Volume Down + Camera button to enter PC download mode, so that I can restore it from Zune software. Trying it now.
3. Restore from Zune doesn't work, even its stuck at 0% for about 30mins.
4. After a few tries, removing battery, removing the SIM and doing some random stupid stuff, tried again the restoration seemed to work, I mean it started to restore.
5. Finally, I guessed its time for me to give up. Restoration failed with Error Code 8018009B. So its bricked for now.
6. I was greeted with this nice message from Windows Phone support tool
"Communicating with device. Please wait for Recover button to be enabled.
Support Tool version 4.8.2345.0
The tool cannot recover this phone. Please contact technical support."
I didn't even force the update, it was regular update which I was able to start from Zune without forcing it. NOW ITS BRICKED!
7. I took my phone to Dell Service Center, those guys couldn't figure out the problem, they said its a new phone here in India and don't have any technician to fix it.
I posted the same in Engadget, I got no response from anyone, so am posting here hoping to get a solution. I at least want my phone working, I'm happy without mango.
Click to expand...
Click to collapse
Sorry to hear this....but, I think you'll be happier with Mango...About your phone...
If this was NOT a forced update, Dell may be able to help you. Microsoft has made updating 'almost' brick free. If you log into Zune, a backup is made, you're using the cable that came with dell, not using a USB hub, have a solid internet connection,and are NOT forcing the update, the blame for the problem could fall onto the update itself.
As part of a test team, I used to try and brick Windows Phones. The easiest test was to remove the cable during different phases of update. I was never able to brick the phone. Sudden power loss on the PC also was tested. Never was able to brick a phone. Apparently the download and transfer process is done in parts, meaning the update is downloaded, completed, then transferred to the phone, then installed. If the update is interrupted during download, no worries, or even transfer, no worries, reboot the phone, try again.
The process of install is done 100% on the phone so no bad cables, or shut down of internet can impact it. Even if connection between PC and phone are lost during the install portion, the message still tells you to check the phone. The install will continue.
that leaves only the relationship between the installation and the files itself. If the update package is corrupt or damaged, then it may not be able to successfully complete. If this is the case, you have an issue with Dell and Microsoft. Since Microsoft can only help you with software, I argue that you would have relief, as in possible phone replacement, from Dell.
Do you have a way of contacting Dell from India?
alodar1 said:
Curious that I see no reports of install problems with Mango on the Dell....yet, especially with those coming from any of the Beta's. Has anyone seen any reports anywhere?
I'm here to report 1.
I was on Mango release build. I flashed back to 7004, and followed the update path to 7008, then 7403 then the release build.
When completed, the VP is in a reboot cycle triggered by any touch. I've done this several times.
The reboot cycle appears as follows:
The update completes with no error and the final reboot starts. On reboot, if no sim is in place, the sim error screen appears. This is normal. Touch the screen to close, forces a reboot, regardless of the update complete message.
Repeat process, this time with a sim in place, Update is installed, success messages appear in zune and on the phone. Disconnect phone, touch the screen, reboot occurs.
Repeat process. let the phone reboot until it reaches the desktop. connect via cable to zune. The device is recognized, but NO sync occurs. Go to settings/update and the current build is recognized. Restore is available, and will work.
if the screen goes dark, slide up or touch power will bring up the Lockscreen. Wifi does show, so does 3g and battery, but NO lockscreen release options are available. Again, any touch forces reboot.
I've reported to Microsoft, but was not considered serious since it cannot be reproduced.
Did the update with my HD7 so Zune, the downloads, etc are in place and working.
Getting back to 7392 is an option, so I am not dead in the water. But wanted to make sure reports of problems with the update were reported.
Click to expand...
Click to collapse
Called Dell Mobility. Even though I could restore back to previous version, they offered to replace the device, which I took.
Kind of sad though, I've never had problems with wifi or anything else on this phone. In fact the only problem ever with a VP was me dropping the thing. I'm hoping the refurb I get will also not be a problem.
alodar1 said:
Sorry to hear this....but, I think you'll be happier with Mango...About your phone...
If this was NOT a forced update, Dell may be able to help you. Microsoft has made updating 'almost' brick free. If you log into Zune, a backup is made, you're using the cable that came with dell, not using a USB hub, have a solid internet connection,and are NOT forcing the update, the blame for the problem could fall onto the update itself.
As part of a test team, I used to try and brick Windows Phones. The easiest test was to remove the cable during different phases of update. I was never able to brick the phone. Sudden power loss on the PC also was tested. Never was able to brick a phone. Apparently the download and transfer process is done in parts, meaning the update is downloaded, completed, then transferred to the phone, then installed. If the update is interrupted during download, no worries, or even transfer, no worries, reboot the phone, try again.
The process of install is done 100% on the phone so no bad cables, or shut down of internet can impact it. Even if connection between PC and phone are lost during the install portion, the message still tells you to check the phone. The install will continue.
that leaves only the relationship between the installation and the files itself. If the update package is corrupt or damaged, then it may not be able to successfully complete. If this is the case, you have an issue with Dell and Microsoft. Since Microsoft can only help you with software, I argue that you would have relief, as in possible phone replacement, from Dell.
Do you have a way of contacting Dell from India?
Click to expand...
Click to collapse
Thanks alodar1..
I asked Dell to do a service and added that I don't need an replacement. The service guy said the phone is new and they are not trained to service this, so they would only do a replacement. I'm not ready to do a replacement, they ask me to go for international warranty, moreover they replace with factory refurbished phones.
BTW, I would like to know if there is anyway to format the memory card without removing or replacing. Right now I have another problem whenever I press the power button to boot my phone it directly goes to Software Download mode, the camera button was never pressed.
While trying to repair using Windows Phone Tool, I received this error "The tool cannot recover this phone, please contact technical support", so being a little curious I fired up .NET Reflector and loaded the tool to find out what was happening, I found that the this error is thrown if the phone is not Samsung made (see attached file). Is there any similar tool for Dell Phones?
*UPDATE 1* Is there anyway to force flash without using Zune, any third party tool, Zune seems to go to restore mode and can't find my phone. I have a feeling that erasing the contents of SD card will solve the problem.
*UPDATE 2* I did the registry trick and was able to see my DVP in Computer window. But instead of one DVP, I see 2 and both have storage of 3.75 GB each. But my DVP is 16GB, both DVP are empty. Previously I was never able to see my DVP even after registry patch. Now I have feeling that corrupt drivers caused the problem, yesterday I completely removed and reinstalled Zune Software, now the registry patch worked.
Please let me know with problem my DVP could be hardware fault or just the software. If its hardware then I'll go for replacement right away.
Just recieved my replacement VP. Ordered yesterday around noonish. Went downstairs to get the Motorola Xoom box that was delivered...and the VP was there too. Bonus....
Did not come with Mango....but....there's not a scratch on this thing....not a rub, not a bump...nothing. Still has plastic in places I doubt they would put plastic after refurb. I'm wondering if I got one of hte left over new ones....
Doesn't matter....Mango won't install no matter what...so...maybe I'll try ICS.
My Mango is now Ripe..
alodar1 said:
My Mango is now Ripe..
Click to expand...
Click to collapse
Nice to hear that!
alodar1 said:
Since I flashed back to 7004, I lost the firmware updates. I noticed that the subsequent updates do NOT flash any firmware. According to MS EULA, all updates are cumulative...contain all previous updates. I have flashed from 7004, to 7008, to 7392 to 7304. During none of these flashes has the firmware been updated. the 105 firmware is maintained. I thought I read that the 7420 update included the 219 firmware....
anyone else having this problem?
Click to expand...
Click to collapse
How do you flash it back to 7392? I need to flash mine.
theonlyremedy said:
Nice to hear that!
How do you flash it back to 7392? I need to flash mine.
Click to expand...
Click to collapse
not a flash, but a restore. I've always made copies of my backups ...
You an't reflash as the user above me already said, that said, the backups are stored in
=> %userprofile%\AppData\Local\Microsoft\Windows Phone Update
so for backing up your restore poiints you can copy that folder and then keep it.
theonlyremedy said:
Nice to hear that!
How do you flash it back to 7392? I need to flash mine.
Click to expand...
Click to collapse
I was just curious. I wanted to fix my phone. The backup restore didn't work. I was just looking for some way to flash it or at least format the SD Card, so that I reinstall OS and can get my phone working. After four days of trying to fix my phone, I finally gave up and sent it for service to Dell. I even copied a little bit of code from phone support tools and tried them, I was just able to get the phone details without any problem, Mango was installed in the phone, but still it didn't boot. It would be good if we find a way to touch the SD card and format it from PC, probably we'll be able to revive many bricked phones. I would be happy to join the project if some one starts it. I can write C# code.
Mine is an error during backup
Error Code 801812DC during backup
I also add new thread.
If anyone knows, please tell me what I need to do.
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?
So here's the thing for my focus. When we all heard about the trick to force the updates through the Hungary IP thing, I got upgraded to 7008. I managed to force the actual NoDo update, but everytime I did it, I would get error: 801812C1, which meant that the software mode on my phone isn't correct.
I did some research and I found that when in Connect To PC mode, it wasn't recognized as a WP7 phone or something like that, so it didn't update the driver as it should have.
Then the Windows Phone Support Tool comes along about a week or so later, and I try that to see if it would do any good, but nothing. In fact, in the Connect to PC mode, it said that there was no device found.
And I also noticed that when actually connected to the PC in Connect to PC mode, I never see the red sign that meant don't disconnect the phone. So I'm assuming that is my problem.
As of now, I've tried most of the solutions I've found (i.e updating drivers manually, skipping the driver update when promted, running the Fixit tool on the KB posts for the specified error, disconnecting, hard resetting THREE TIMES NOW and so on. )
So thats where I am at this point, extremely frustrated, and hoping that if AT&T rolls out the update, it might work for some reason, but my fate seems grim.
Anyone wanna offer suggestions?
I was thinking maybe I could flash back to 7004 and who knows, my problems will disappear.
Or.... yeah, any and all suggestions welcome. Thanks.
I think I'm lucky my phone isn't bricked or anything at this point. -___-
Please, please, please help!
Backup your stuff on the phone and perform a hardreset.
Don't give up, young Jedi. I ran into the same problem as you. It was very frustrating. What I did was go back and redo everything I had done up to a point. I went into the registry and put it back to AT&T. Then I removed the ChevronWP7 ringtone (doubt that did anything, but whatever). I went into Chevron and undid whatever I had done previously. Undid the Hungary thing. Then rebooted the phone. I then redid everything again, did the Hungary thing again and tried the timing. Got up to 50 seconds and suddenly everything worked.
Good luck!
Like I said, I've resetted the phone, backup or not, I dontthinkit matters, at least 3 times now.
nathantw said:
Don't give up, young Jedi. I ran into the same problem as you. It was very frustrating. What I did was go back and redo everything I had done up to a point. I went into the registry and put it back to AT&T. Then I removed the ChevronWP7 ringtone (doubt that did anything, but whatever). I went into Chevron and undid whatever I had done previously. Undid the Hungary thing. Then rebooted the phone. I then redid everything again, did the Hungary thing again and tried the timing. Got up to 50 seconds and suddenly everything worked.
Good luck!
Click to expand...
Click to collapse
will try this. To clarify, I need to sideload the registry app, return the value to ATT ( which is 0? Right?) then do what exactly in chevron? Like what exactly am i undoing in this procedure ?
Thanks a bunch
Sorry, it's been so long ago since I updated my phone (last week <hee-hee>) I forgot. I hope I'm right, but Chevron allows you to unlock your phone. I relocked it, rebooted, then unlocked it again. Then started the procedure that's in everyone's instructions all over again. Yes, the 000-88 was put back to ATT-US. Went out of the registry program, rebooted, then went back in and put 000-88 back in.
nathantw said:
Sorry, it's been so long ago since I updated my phone (last week <hee-hee>) I forgot. I hope I'm right, but Chevron allows you to unlock your phone. I relocked it, rebooted, then unlocked it again. Then started the procedure that's in everyone's instructions all over again. Yes, the 000-88 was put back to ATT-US. Went out of the registry program, rebooted, then went back in and put 000-88 back in.
Click to expand...
Click to collapse
Tried it. Didn't do anything.
Hi all,
My firmware has been the same since the day I bought it, which also was the day of release here in the UK, so it was 2.3.3. Today it said that a firmware upgrade was available, so I selected to download and install it. After a while it rebooted, showed it installing, then booted up normally. I got the main screen again and it said there were more software updates available, so I said to install those too. Again it rebooted, showed installation progress, then when booting up, it now gets permanently stuck on the boot screen where it just shows the Samsung Gaiaxy S II logo (along with the GT-I9100 text). I've left it for over 30 mins and nothing changes. I've tried rebooting several times, both with charging cable in and out, removed the battery for a few minutes and tried again, but it won't get beyond this screen anymore.
I looked at the thread about what to do about this situation (boot loop) which involved erasing user data, so I did this. The message that also came up during erasure said that it wiped the cache too. Tried rebooting after that but it's still stuck.
Is there a way to fix this?
Note that I've never installed custom firmware and never rooted my phone. I also don't have a 32-bit version of Windows, so can't use Odin (it never picks the device up). Plus I don't wish to void the warranty. Is it possible to get the official update zip package which I can flash from the recovery menu?
Thanks
Thom
Is there not a warranty provided by your cell carrier? I know in the us most carriers provide a 1 year warranty with all devices. They would exchange it gladly especially since you did everything by the rules.
Sent from my i897 running MIUI 1.8.19 with TalonMTD kernel.
xijar said:
Is there not a warranty provided by your cell carrier? I know in the us most carriers provide a 1 year warranty with all devices. They would exchange it gladly especially since you did everything by the rules.
Click to expand...
Click to collapse
Yes, it's under standard warranty. I bought it sim-free without being tied to a network. I have already contacted Samsung and they said they'll email me details of the service centre to return it to, but I was hoping for a solution before needing to do that.
Nothing you can do without odin picking the phone up.
I use 64bit windows and it picks up fine, make sure you have the drivers installed (see the link in my sig, for my 4shared, where you can get them) or if you have kies installed you have them but make sure to kill all kies processes first in task manager.
But in the end, best bet is just to send it in, to make sure you dont void your warranty
Sorry this is a mistake.
darkixion said:
Hi all,
My firmware has been the same since the day I bought it, which also was the day of release here in the UK, so it was 2.3.3. Today it said that a firmware upgrade was available, so I selected to download and install it. After a while it rebooted, showed it installing, then booted up normally. I got the main screen again and it said there were more software updates available, so I said to install those too. Again it rebooted, showed installation progress, then when booting up, it now gets permanently stuck on the boot screen where it just shows the Samsung Gaiaxy S II logo (along with the GT-I9100 text). I've left it for over 30 mins and nothing changes. I've tried rebooting several times, both with charging cable in and out, removed the battery for a few minutes and tried again, but it won't get beyond this screen anymore.
I looked at the thread about what to do about this situation (boot loop) which involved erasing user data, so I did this. The message that also came up during erasure said that it wiped the cache too. Tried rebooting after that but it's still stuck.
Is there a way to fix this?
Note that I've never installed custom firmware and never rooted my phone. I also don't have a 32-bit version of Windows, so can't use Odin (it never picks the device up). Plus I don't wish to void the warranty. Is it possible to get the official update zip package which I can flash from the recovery menu?
Thanks
Thom
Click to expand...
Click to collapse
How did you erase user data?
Sent from my GT-I9100 using XDA Premium App
inkyadrian said:
How did you erase user data?
Click to expand...
Click to collapse
When it was switched off, I held down Vol-Up, Home and the power button. There was an option in the menu called "wipe data/factory reset". There's also a "wipe cache partition" option, the action of which is performed in the wipe data option anyway.
Hey guys,
I've bought my MX4 Pro almost a year ago, but decided only now to ask for your help. Hope you'll be able to guide me to fixing the several problems i have.
First of all, phone came with Flyme 4.5.7I and right from the start there were some features not working. Most important, the fingerprint screen unlock isnt working. After capturing my fingerprint, when i try to enable it to unlock screen it just takes me back to the home screen.
Another issue is getting sometimes (it happens randomly) a no sim error. Sometimes restarting is enough, sometimes i need to take out the sim card and insert it back.
Ever since i've tried to update firmware, hoping it would solve my problems. Nothing has worked.
Dowloaded the update.zip (no matter which version) and placed it in root directory. When i try to open it with the document app i get two options, view and extract. Can't update. Also starting the phone using volume+ and power button (update screen) has always produced the same results: Firmware corrupt. Tried doing it with clearing data, without that, no difference. Tried with a .bin file, same thing.
As far as i know the bootloader is locked, and i remember checking if the device is properly rooted and IT IS NOT.
So, the more android savvy people here can help? I'm lost and i really enjoyed the phone so far, but i dont really know what to do from now on. Is it a faulty device? (This would be the worse, since the phone was bought from China).
I can provide any additional details if needed.
Thanks in advance
P.S. I remember trying every tutorial/solution out there, nothing has seemed to work. I also may be dumb, not sure.
I already opened an RMA for the phone but they have no stock so I figured I'll take another shot at it.
The short version is that my gf messed up and updated the system while transferring her data from her old phone with the tapNgo thing.
I've done multiple facory resets, downloaded the rom from ZTE support, put it on SD, flashed it from recovery and deleted cache and nothing helps.
I don't have the exact error log anymore since I don't have the phone with me now but it reads something along the lines of
loading /proc/devices/audio/sound------ cannot find file/directory.
I looked it up and after a lot of Googling it seems like the symlink to the actual driver folder is missing and I have no idea why.
Does anyone know if i can fix this with an ADB shell?
Alternatively, I tried to follow some of the many guides out there to put the phone in EDL mode and relfash it with XiamiFlash utility but after trying 3-4 downloads and 900 versions of misflash all I ever get is "reading hello packet... unable to communicate to com4"
Haaaalp please?
*edit* this is pretty much exactly the same as what I'm getting: https://forum.xda-developers.com/android/help/sound-card-detected-t3379736
The problem with the phone is it makes no sounds?
gpz1100 said:
The problem with the phone is it makes no sounds?
Click to expand...
Click to collapse
the sound drivers for the OS is missing completely, no sound no microphone.
The syslog looks like this(this is from another phone its its the exact same problem):
AudioDaemon: Opening sound card state : /proc/asound/card---/state
AudioDaemon: Open /proc/asound/card---/state failed : No such file or directory
AudioDaemon: Sleeping for 100 ms
Strange issue indeed. Which model do you have? Which specific firmware file are you flashing to it?
I would think flashing the full unmodified factory firmware using the stock recovery will wipe the phone completely, including the /data partition.
Everything worked before? Help me understand the order of events. What is tapngo?
While in the midst of transferring information to or from the phone, a software update appeared and she accepted/installed it?
Its the A2017U model.
I had tried the 1.1.0 B15 firmware from SD card as well as the 1.0.0 B29 older firmware.
Right now its on B17 Nougat 7.1.1, the phone runs and works perfectly just has no audio hardware.
I wasn't there for the exact procedure but basically she powered it on, it asked for sim, she inserted that, tapped the "transfer my data" and then held the two phones together to get the NFC process started. That starts the bluetooth transfer process and it takes a really long time where it transfers all data and apps from the old phone.
At this point the phone still made sounds when adjusting the volume etc.
Somewhere in that process the "update available" notification came up and she pressed the option to install it.
After I got home I tried to figure out what is wrong, first i thought the phone wasn't registered on the cellphone network but then after a bit i figured out the audio is the issue, then i did a factory reset both from the phone UI and tried again from recovery mode, both times chose the "erase all data" option but neither time did it help at all.
I don't really know enough about phones but i think its the bootloader/something very early on thats messed up. Either that or the audio chip really just did fry.
My hope was to get the full factory image for everything that you need to install with the EDL mode thing but I can't find any good reliable guides for that.
It's the first thread in the development section.. Stickied even.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Get this package - B15-NEW_FULL (Nougat)
I really don't understand zte's numbering scheme. Newer versions get lower numbers. Makes no sense. That's the full firmware except for the fastboot which passes commands. At this point it's a non issue given the issue you're having.
So I don't need to load TWRP on it, I can still keep it just stock with unlocked bootloader?
I tried that miflash thing before, i had it connected un usb download mode but nothing worked for me, I'll try doing this guide when i get home step by step again.
Their firmware numbers is based on numbers and letters 1.0a-z and then 1.1a-z so 1.0z1 is less that 1.1a1
Ok I have an update
Did miflash, nothing changed.
Ulocked bootloader and miflashed the bootloader from the sticky thread.
The phone made the startup sound and audio worked for a few seconds after android started up and then stopped again
*edit*
ok so after it showed signs of life i re-locked the bootloader, and did the OTA updates to 7.1.1 and the audio seems to be working for good now!!
Conclusion seems to be the bootloader was the key to get it working again. Hope this helps others if it comes to it.