Related
I tried different machines before I sorted the connectivity problem to establish connection to my device until finally my PC can recognise my device.
Now comes the next headache, after getting the connection established I clicked on firmware upgrade - it came up and displays some updates are available -
it shows my current version as:
(PDA)JE9/(Phone)JE9
available update as:
(PDA)JF4/(Phone)JF4
When clicked on 'proceed' - it brings up some warning for me to make sure they are fixed before I proceed further like power cables connected and some warning of not removing or doing anything during upgrade, after I check 'agree' it starts the download by letting me know that the binary files for the new firmware is being downloaded and after the dowload there seems to be a wait creating impatience for us as to what next...after a few seconds I can see the message above the progress bar saying that the upgrade process has begun..
I can see the screen on my SGS display come with the android logo on some work (like road construction work) and the message telling upgrade in progress do not disconnect...it stays in that state for around a minute...no progress in the progress bar....Now suddenly the PC says 'failed to convert to upgrade mode, try later' and even after stopping my phone continues to show the frozen screen with 'upgrade in progress' (getting us confused and scared and dont know if I can unplug - will this brick my device all sorts of question) until I shut down my SGS and reboot to see it is normal as before but whenever I connect for the firmware upgrade all that I know is I am pending new upgrade.
I am stuck and can't proceed further - I tried it many times with many machines no luck. Please anybody suggest a way out.
Some info on my device: Bought in UK, sim free phone from Singapore Singtel as I see the operator's animation in the startup screen.
Other details on firmware:
PDA:I9000DXJE9
Phone:I9000DXJE9
CSC:I9000OLBJE9
In the settings 'About Phone' carries details:
Version: DXJE9
Kernel: [email protected]# (does this mean the device is rooted already?)
I have another question since I saw somebody mention in another thread that whether he/she should do a european firmware upgrade or asian firmware upgrade - I still confused by this question as well, which upgrade will be pushed to you if you are using Kies as it is just one same application made available for download globally.
somebody please help me with the upgrade issue.
isn't there any dev who can help me on this, it looks like i am the only one experiencing this!!!
I don't think many people are getting the upgrade options via kies at the moment.
I'm not seeing it on UK JF3
so hope, there isn't an issue with my device. I am weary because this was purchased from an online site but purchased the device after checking it personally.
One more question, will an unlocked phone get locked after any new firmware updates?
Are sim free and unlocked phones follow different philosophy ie., after unlocking a phone does that become a sim free phone forever.
Second question, how does the OTA update work - if you are not tied to a service provider - does samsung send these directly to all sim free phones automatically, looking and searching for IMEI numbers? and will a rooted phone be allowed to upate to froyo or any official update (for example) via the official Kies?
thanks
There isn't any offical firmware updates, via Kies, and or any other method.
JaGuR said:
There isn't any offical firmware updates, via Kies, and or any other method.
Click to expand...
Click to collapse
Pls dont give wrong information. If you are suggesting something make it elaborate and clear.
I have clearly mentioned that I can see my current version as: (PDA)JE9/(Phone) JE9
Update available version:
(PDA) JF4/(Phone) JF4
thats what is displayed via Kies. I am also aware from this forum that some people can see the update whilst others dont see any.
Having said that, I was asking a techy questions as to whether a OTA upgrade or a upgrade via Kies from Samsung still happen if the phone is rooted and also if the phone is sim free and not attached to any service providers will the OTA upgrade will happen if so, is it based on IMEI number that will automatically be tracked OTA.
S
I was wondering if anyone found a solution to this problem? I am having the same problem.
I'm looking at this also.
after following this: (oh great, can't post links)
I had a problem updating to the official Foyo via Kies.
Finally got my PC to recognise the phone then started the update.
Phone screen went all green part way through and nothing was happening for about 20 mins so unplugged.
Phone would switch on but came up with a little picture on the screen and thats it.
so got it updated to JPM by booting into download mode and using odin. Took 5 mins once I downloaded all the files.
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?
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.
Hi all.
I got my hands on an LG G2 from verizon which used to be a display model, the problem is it won't charge beyond 38%, it displays a message about the charger not being compatible. So far I've used several chargers with no results
I'd like to know if rooting it and flashing a custom rom would get rid of this message and allow it to charge beyond that cap.
Soon I'll have the official charger anyway.
The second problem I found is that this phone has a different software version than a normal G2, in the end it has a "_DU" so ioroot will not root it as it will not recognize the software version name. This weird software version seems to be for the purpose of downloading an enabling a product showcase animation for using it on display at verizon stores, this animation is downloaded automatically after every factory reset, so it's very annoying, but it can be uninstalled nevertheless. My guess is this "DU" stands for display unit or something similar.
What I'm thinking could solve this problem is flashing an official firmware in download mode (to get rid of the _DU) and then try to root it in the normal way. Later I pretend to install cyanogenmod to see if the charging problem is gone.
Do you guys think this will work? I'm worried this prompt is not related to the rom, but the kernel itself, so uninstalling the stock rom would not work at all. Also, I don't know if it is possible to flash an official firmware just to get rid of the one with de "DU" in the end. I have very little experience with this device in particular.
Otherwise the phone is fully functional in every aspect, so I think this software version is indeed only meant to load the showcase animation. The current Sofware version it has says exactly "VS98011A_DU"
Thanks in advance.
Mr. Dildo said:
Hi all.
I got my hands on an LG G2 from verizon which used to be a display model, the problem is it won't charge beyond 38%, it displays a message about the charger not being compatible. So far I've used several chargers with no results
I'd like to know if rooting it and flashing a custom rom would get rid of this message and allow it to charge beyond that cap.
Soon I'll have the official charger anyway.
The second problem I found is that this phone has a different software version than a normal G2, in the end it has a "_DU" so ioroot will not root it as it will not recognize the software version name. This weird software version seems to be for the purpose of downloading an enabling a product showcase animation for using it on display at verizon stores, this animation is downloaded automatically after every factory reset, so it's very annoying, but it can be uninstalled nevertheless. My guess is this "DU" stands for display unit or something similar.
What I'm thinking could solve this problem is flashing an official firmware in download mode (to get rid of the _DU) and then try to root it in the normal way. Later I pretend to install cyanogenmod to see if the charging problem is gone.
Do you guys think this will work? I'm worried this prompt is not related to the rom, but the kernel itself, so uninstalling the stock rom would not work at all. Also, I don't know if it is possible to flash an official firmware just to get rid of the one with de "DU" in the end. I have very little experience with this device in particular.
Otherwise the phone is fully functional in every aspect, so I think this software version is indeed only meant to load the showcase animation. The current Sofware version it has says exactly "VS98011A_DU"
Thanks in advance.
Click to expand...
Click to collapse
Hey, what happened with the phone ?! Did you manage to root it and fix the battery problem, because i got the same phone, same problem and there is absolutely no info about it...
Probably you bought mr dildo's phone.....
_____________________________Write less read more and be smart
Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
MGArcher007 said:
Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
Click to expand...
Click to collapse
Have you resolved this issue, if so, would you mind sharing how you did it. I've been combing the net for a few days trying to discover what is going on and your issue appears to be exactly what I am experiencing. I've read about flashing back to my stock firmware using Odin but I cannot get into download mode, when I try and get there, the phone only says "recovery reboot" in blue small font on the top of the screen and reboots.
Thanks
Ladies and gents, I apologize for abandoning this thread. I forgot exactly how I got to get the phone to update, but if I recall correctly, it had to do with me putting the phone in download mode, downloading the original firmware and using ODIN to flash it. Afterward, the "unlocked" padlock symbol disappeared and the phone was able to get the OTA update from AT&T.
I have since moved from an LG G4 to a V20 and that is what I am currently playing with. I also have a Samsung Galaxy S6 Edge (which T-Mobile replaced my G4 with when the touch screen stopped responding). I was quite stoked to find out that there is a way to root it and (seemingly) unlock the bootloader, so I'll be toying with that this weekend to see what I can do. I'd love nothing more than to just wipe that Samsung-ified Android and install a vanilla Android or CM.
Good luck to anyone who is still trying to fix this issue. Again, my apologies. I'll dig through my archives and see if I can piece together what I did to get it going again. I still have the S5 Active. Best phone by far. It's a great backup phone for when the new stuff goes kaput.