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.
I tell you I unlock it first, then I had problems with some widgets and I learned some new updates.
Then, I made a backup with Sony_Ericsson_Backup_and_restore.
After searching, I root my phone with "GINGERBREAK" downloaded from the internet (GingerBreak-v1.20) and finally settled "Titanium Backup" to remove some applications from my operator, then install the CLOCKWORDMOD (do not know what for) and and finally I started to flash ...
After root, flashing with FlashTool_0.2.9.1.
I suggested steps for flashing and inserted this update: "LT15i_4.0.A.2.368_Generic Global", with "wiped ...", which is to delete everything and set it to zero ..
Normal work for me ... I sent version 2.3.2 to 2.3.3 (thinking I would send to 2.3.4). It was great ... Then I appeared a notice of samsung (on phone), to install version 2.3.4 (4.0.1.A.0.283 I think it was that number) and when it started to install warned me he was going to shut down, spent 6 or 7 minutes and not lit. I tried to turn it on and vibrated, then vibrate him again and try to turn rang again, but soon ...
Then I could not turn ...
Once this happened I was like crazy trying to fix the COMPANIOM, but nothing ...
I flash again, this time with this "LT15i_4.0.2.A.0.42_ (1247-1041). Ftf" but did not recognize the flashtool as the first time coming out of the mobile code when you open the program loads and displays the model number of the phone, it did not appear.
Finally, press flash and began. (To this already, before, try reinstalling the Global LT15i_4.0.A.2.368_Generic where my computer does not recognize, nor giving flash, just not recognized out in red letters)
When flashing with the latest LT15i_4.0.2.A.0.42_ (1247-1041). Ftf, the normal flashing until the end. But my phone just did not work. The light that was on the side of my phone was green ...
I sent a technician and he said he could not ....=/
I hope you can help and serve as a case to be resolved.
Thank you very much, good luck!
With bootloader unlocked by other methods different to setool one you will get bricked after try to install an OTA update
In order to get phone back to life just flash this with flashtool
http://www.mediafire.com/download.php?v4d3jdf136ymaxr
If you are interested in fix that annoying problem with ota update check this thread
http://forum.xda-developers.com/showthread.php?t=1126358
Greetings
ozfred said:
.... then install the CLOCKWORDMOD (do not know what for) ......
Click to expand...
Click to collapse
Lol dude, don't install things if you don't know what are those for
But i did it...u_U! So, now?
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.
Long story short I'm working on loading a new (has not been used) LG V20 with Lineage OS and obviously have to pre-root the phone but I'm having problems and any help would be appreciated.
I'm currently working on trying to get DirtySanta working but in the command line when I run "run-as con" during ./step1.sh I get, "run-as: unknown package: con"
My questions are...
What am I missing?
Are there step by step instructions for completely re-loading these phones to LineageOS from factory to fully running?
The phone has the factory Android 8.0.0 and has NO data on it that needs to be saved. FastBoot is NOT working, I've tried many times.
Enable OEM unlock is not a option in the developer options on the phone.
Visseroth said:
Long story short I'm working on loading a new (has not been used) LG V20 with Lineage OS and obviously have to pre-root the phone but I'm having problems and any help would be appreciated.
I'm currently working on trying to get DirtySanta working but in the command line when I run "run-as con" during ./step1.sh I get, "run-as: unknown package: con"
My questions are...
What am I missing?
Are there step by step instructions for completely re-loading these phones to LineageOS from factory to fully running?
The phone has the factory Android 8.0.0 and has NO data on it that needs to be saved. FastBoot is NOT working, I've tried many times.
Enable OEM unlock is not a option in the developer options on the phone.
Click to expand...
Click to collapse
If you took the time to the dirty santa thread then you'd know that your phone's security patch date is date where ds has been patched, you need to be on a security patch date prior to Dec 2016
Sent from my LG-H910 using XDA Labs
Now I remember why I didn't post on these threads much. People just assUme that the posting person is a COMPLETE idiot.
This is a HELP forum where people come to get HELP and information, there's no reason to point fingers. A simple, "BTW that version you're running is a patched version, you'll need to roll it back to a prior, follow these links..." version would have done just fine.
With that I'd reply........
I realized I needed a older firmware last night when I was fighting with it for hours. I rolled it back to a firmware, dated 12-24-2016 and managed to get BadSanta to work but it caused my phone to go into a non-stop vibrate, it wouldn't complete boot and was basically bricked. I then found from another site that explained EXACTLY how to put the phone in download mode and then re-flashed the ROM (BTW, for those that don't know, you power off, hold the volume up and then plug in your data cable) but then put Android 7.0 Build number NRD90M.
The problem I am running into is everyone's information isn't is sync.
Some say how to proceed but don't say on what build number to proceed.
Some say to roll back to Android 7 Naugut but don't say which version because there are many versions of that version.
Personally I don't understand why a ROM can't be flashed via the download mode but then again I'm not a programmer.
So with that, after many hours I've made some progress but I am disappointed in how complicated and time consuming it is. I'm seriously considering a Pinephone for me and this phone (once completed) for my wife.
Right now I'm in the process of following this thread....
https://forum.xda-developers.com/v20/how-to/lgv20-vs995-verizon-aio-post-06-19-2017-t3624326
Later, after I get some work done.
Thanks for the reply though.
Well seems the BadSanta isn't working on my phone, as soon as I get past step3 and it reboots the screen is all scrambled and the vibrate motor runs continuously.
I've managed to get into TWRP once and followed the instructions but it bricks the phone at the LG startup screen.
Reloading the fastboot image doesn't do any good.
So seems I'm stuck with the stock firmware.
Can't say I didn't try.
Instructions I followed are here...
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
Visseroth said:
Well seems the BadSanta isn't working on my phone, as soon as I get past step3 and it reboots the screen is all scrambled and the vibrate motor runs continuously.
I've managed to get into TWRP once and followed the instructions but it bricks the phone at the LG startup screen.
Reloading the fastboot image doesn't do any good.
So seems I'm stuck with the stock firmware.
Can't say I didn't try.
Instructions I followed are here...
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
Click to expand...
Click to collapse
The vibration is normal if it's the VS995, which I'm sure you are using, right?
And the phone is not bricked, it's normal to see that warning at the start-up screen (about the device being corrupt....). Just be patient and give it time to boot.
The scrambled screen (static on boot) is also normal, just flash lineage 17.1, afaik it doesn't have static on the vs995
On a side note: double check the dirtysanta thread, you'll find most of these there
Really? I tried for many hours, multiple times and no go.
Yes it is the VS995, I guess I forgot to post that.
I did at one point get to a point where I could see a image behind all the garbled corruption on the screen and I did know that the corrupt notification was normal, that's how I made it to the TWRP once but I just couldn't get the screen fuzzy corruption to go away and the phone was still stuck vibrating non-stop.
Maybe I'm missing something?
And I only managed to get to the TWRP bootloader once.
Are all the features on the phone working on LineageOS 17.1?
I really wanted to get the phone not only up to date but limit the spying as much as possible with a device already designed to spy.
This phone is really for my wife, I'm thinking of ordering myself a PinePhone and giving that a whirl.
Visseroth said:
Really? I tried for many hours, multiple times and no go.
Yes it is the VS995, I guess I forgot to post that.
I did at one point get to a point where I could see a image behind all the garbled corruption on the screen and I did know that the corrupt notification was normal, that's how I made it to the TWRP once but I just couldn't get the screen fuzzy corruption to go away and the phone was still stuck vibrating non-stop.
Maybe I'm missing something?
And I only managed to get to the TWRP bootloader once.
Are all the features on the phone working on LineageOS 17.1?
I really wanted to get the phone not only up to date but limit the spying as much as possible with a device already designed to spy.
This phone is really for my wife, I'm thinking of ordering myself a PinePhone and giving that a whirl.
Click to expand...
Click to collapse
On stock, after it is done booting, press the power button once to turn off the main screen, then cover the upper left corner with your hand till the second screen turns off (abt 5 - 7 sec). Turn the screen back on and use your phone.
About lineage,