Received a Prime today, brand new. Powered on to 3.2, and almost immediately got the DMClient crash, while still going through the Android Wizard. Continually got it, tried force stopping, clearing cache and data on it, rebooting, etc. Wiped all data both via the bootloader and via settings, immediately came back. Was unable to get an update OTA - crashed immediately.
I downloaded .14 ICS update from ASUS, put it on the internal storage, and it immediately noticed it and offered to upgrade. Did the upgrade, wiped data. Again, during the step where you enter your Google credentials, started getting the DMClient crash. It clearly isn't the result of anything I've installed (since it was happening after a wipe before I was able to install anything!) I know .15 is out there, but updating via the menu is not an option. (Crash, crash, crash, crash.) I haven't seen any other complaints of it happening on a fresh clean install, where it seemed to be impossible to make it stop.
I guess I'm going to root and install .15 either from the dev section, or Virtuous Prime. But has *anyone* else had this happen? I don't understand how it can crash fresh stock install, unless there's some sort of hardware issue causing it. Not that it would be related anyway, but I do have a serial number.
Any help???
skunkiechris said:
Received a Prime today, brand new. Powered on to 3.2, and almost immediately got the DMClient crash, while still going through the Android Wizard. Continually got it, tried force stopping, clearing cache and data on it, rebooting, etc. Wiped all data both via the bootloader and via settings, immediately came back. Was unable to get an update OTA - crashed immediately.
I downloaded .14 ICS update from ASUS, put it on the internal storage, and it immediately noticed it and offered to upgrade. Did the upgrade, wiped data. Again, during the step where you enter your Google credentials, started getting the DMClient crash. It clearly isn't the result of anything I've installed (since it was happening after a wipe before I was able to install anything!) I know .15 is out there, but updating via the menu is not an option. (Crash, crash, crash, crash.) I haven't seen any other complaints of it happening on a fresh clean install, where it seemed to be impossible to make it stop.
I guess I'm going to root and install .15 either from the dev section, or Virtuous Prime. But has *anyone* else had this happen? I don't understand how it can crash fresh stock install, unless there's some sort of hardware issue causing it. Not that it would be related anyway, but I do have a serial number.
Any help???
Click to expand...
Click to collapse
What SKU are you? WW, DE, US, UK?
That really is no good. And it's odd that wipes/manual installs aren't cutting into it, usually the rewrites will help iron things like this out.
Like you said, rooting and trying other (older) updates and such would at least show us if it's consistent regardless of what you do.
Must be s/w issue though, so I'm stumped why you haven't absolved it yet
*EDIT:
And please realize that rooting and unlocking are not the same! You can root and install other updates and still keep your warranty. If you successfully unlock so that you can install Virtuous, you will not have a warranty.
US SKU, sorry about leaving that out. Is there any way a hardware issue could wreak havoc with DMClient? This is really perplexing.
Now that I think about it, though, I'm a bit reluctant to unlock the tablet and cause warranty issues while this is still happening...
EDIT: Hahaha - I realized as I was replying to you that didn't make any sense, and I shouldn't have said unlock!
buxtahuda said:
What SKU are you? WW, DE, US, UK?
That really is no good. And it's odd that wipes/manual installs aren't cutting into it, usually the rewrites will help iron things like this out.
Like you said, rooting and trying other (older) updates and such would at least show us if it's consistent regardless of what you do.
Must be s/w issue though, so I'm stumped why you haven't absolved it yet
*EDIT:
And please realize that rooting and unlocking are not the same! You can root and install other updates and still keep your warranty. If you successfully unlock so that you can install Virtuous, you will not have a warranty.
Click to expand...
Click to collapse
well technically rooting can void warranty also as it states it in there. tampering with root files or software. BUT at least we can unroot. plus hopefully Asus not to much by the books when device is rooted n sent in for warranty work. if anything, I'd remove root from device to be on the safe side n take no chances of them denying me warranty claim for something as simple as that.
but like you said though, if you unlock, kiss your warranty good bye..lmfao
demandarin said:
well technically rooting can void warranty also as it states it in there. tampering with root files or software. BUT at least we can unroot. plus hopefully Asus not to much by the books when device is rooted n sent in for warranty work. if anything, I'd remove root from device to be on the safe side n take no chances of them denying me warranty claim for something as simple as that.
but like you said though, if you unlock, kiss your warranty good bye..lmfao
Click to expand...
Click to collapse
Yeah, I'm not going to unlock until I know what's going on. I figured rooting isn't a big deal since it can always be unrooted. But I'd need to be unlocked to install another ROM, so I guess I don't see where this gets me very far. ACK! Frustrating!
skunkiechris said:
Yeah, I'm not going to unlock until I know what's going on. I figured rooting isn't a big deal since it can always be unrooted. But I'd need to be unlocked to install another ROM, so I guess I don't see where this gets me very far. ACK! Frustrating!
Click to expand...
Click to collapse
Just root. Follow my sig to PrimeTime (Root/Unroot).
Then we (that is, XDA'ers more knowledgeable than I) can get into your system files to see what's going on. You could even just try fixing its permissions and such.
If none of that works, manually blob to another update (also in my sig) and continue testing.
All of this will leave warranty intact so long as you unroot and rewrite any changed system files (probably with a reset/install).
buxtahuda said:
Just root. Follow my sig to PrimeTime (Root/Unroot).
Then we (that is, XDA'ers more knowledgeable than I) can get into your system files to see what's going on. You could even just try fixing its permissions and such.
If none of that works, manually blob to another update (also in my sig) and continue testing.
All of this will leave warranty intact so long as you unroot and rewrite any changed system files (probably with a reset/install).
Click to expand...
Click to collapse
I did root successfully after my first post. Here's what they look like currently:
-rw-r--r-- root root 167247 2012-02-14 08:51 DMClient.apk
-rw-r--r-- root root 668904 2012-02-14 08:51 DMClient.odex
That seems on par with everything else...
Does DMClient do anything other than manage OTA updates? Maybe the solution is just to remove it entirely. I have no problem manually downloading and installing updates, as long as there are no other issues!
skunkiechris said:
Does DMClient do anything other than manage OTA updates? Maybe the solution is just to remove it entirely. I have no problem manually downloading and installing updates, as long as there are no other issues!
Click to expand...
Click to collapse
This formats the internal SD card which makes this route a nuisance. It also requires hooking back up to a PC to re-root.
Again, I've no idea what to look for or what would cause this especially after wiping/resetting (I still wouldn't know otherwise lol ), but hopefully someone will come along who might know or ASUS will answer a support ticket.
Related
My Vibrant is telling me that T-Mobile has kindly sent me an update. I think it must be the GPS fix. It is rather persistent in that it won't let me choose when to install it. It will only allow me to delay for at most a day. This is quite annoying as I am preparing for a trip and really don't want to mess around with my phone right now.
I am running Vibrant9. Do I want to install this update? Is it gonna break anything? Thanks!
JJMT said:
My Vibrant is telling me that T-Mobile has kindly sent me an update. I think it must be the GPS fix. It is rather persistent in that it won't let me choose when to install it. It will only allow me to delay for at most a day. This is quite annoying as I am preparing for a trip and really don't want to mess around with my phone right now.
I am running Vibrant9. Do I want to install this update? Is it gonna break anything? Thanks!
Click to expand...
Click to collapse
Shouldn't break anything. Most are still waiting for the update. Personally I was impatient and flashed it through ODIN last night.
OK. I accepted the update. Phone is now stuck on "Vibrant" at reboot. Sigh. Proceeding to trying to restore ROM.
JJMT said:
OK. I accepted the update. Phone is now stuck on "Vibrant" at reboot. Sigh. Proceeding to trying to restore ROM.
Click to expand...
Click to collapse
Go to the Development section that are a few threads about this. I looks like anyone with a lag fix, or GPS fix (from JI2) where having this issue, plus I have seen stock people having it too.
Or you can go read my blog post here. the post tells the steps I took to get back the JFD, but you could flash JI6 instead.
you will need to flash JI6 with ODIN to restore, you can not just do a nandroid restore, it is an issue with the kernel and nandroid does not restore/backup the kernel.
*facepalm*@Samsung
http://forum.xda-developers.com/showthread.php?t=803492
Anderdroid said:
*facepalm*@Samsung
Click to expand...
Click to collapse
It's not Samsung or T-Mobile.. its that the OP performed tweaks so the ROM wasn't a 100.00% version of Stock. Tweaks including lag fixes, GPS fix, etc can cause this.
Personally, I don't know why if you're performing tweaks on your phone and are on a stock ROM. If you're going to tweak your phone, go the full way and tweak everything.
This is why t-mobile had the G2 nand locked..... so this type of user error won't cost them millions, replacing phones that the user messed up with blind stupidity.... that's only for the ones under warranty, you can still call in a lost phone and get replacements..
dan0zone said:
This is why t-mobile had the G2 nand locked..... so this type of user error won't cost them millions, replacing phones that the user messed up with blind stupidity.... that's only for the ones under warranty, you can still call in a lost phone and get replacements..
Click to expand...
Click to collapse
So now instead, they get flooded with returns because the phone isn't what people expected.
zephiK said:
It's not Samsung or T-Mobile.. its that the OP performed tweaks so the ROM wasn't a 100.00% version of Stock. Tweaks including lag fixes, GPS fix, etc can cause this.
Personally, I don't know why if you're performing tweaks on your phone and are on a stock ROM. If you're going to tweak your phone, go the full way and tweak everything.
Click to expand...
Click to collapse
That's not true, it is Samsung/T-Mobile fault. I know 3 people with 100% stock, unrooted, vibrants, 2 of them got stuck when they updated. the t-mobile forums filled with stock users with their phone stuck at the vibrant screen as well.
camalot said:
That's not true, it is Samsung/T-Mobile fault. I know 3 people with 100% stock, unrooted, vibrants, 2 of them got stuck when they updated. the t-mobile forums filled with stock users with their phone stuck at the vibrant screen as well.
Click to expand...
Click to collapse
And what are the chances of this?
Everybody lies.. especially when they're desperate and unwilling to accept the fact that they modified their phone. I don't see any reason why they wouldn't lie to T-Mobile and say that they didn't modify their phones if its "bricked." Because it is not bricked, all it takes is download mode and Odin. There are threads out there that break down on how to use Odin, it's not that difficult to do.
This is why I don't endorse "One Click" anything unless it is a long process. Sure, it makes everything easier but it makes people not think about what they're doing before they do it. Before one clicking, rooting was so simple, put something on your internal sd and boot into recovery and hit reinstall packages. If something like that is too difficult then they shouldn't be doing any modifications in the first place unless they understanding what they're doing.
The T-Mobile forum is not a valid source because there is no concrete proof that they didn't root their phone and modified something. Even rooting and removing bloatware then removing access to root would cause this.
Edit: Looking at the OP's recent posts.. he did indeed run a custom ROM but has possibly did some tweaking after reverting back to stock?
zephiK said:
And what are the chances of this?
Everybody lies.. especially when they're desperate and unwilling to accept the fact that they modified their phone. I don't see any reason why they wouldn't lie to T-Mobile and say that they didn't modify their phones if its "bricked." Because it is not bricked, all it takes is download mode and Odin. There are threads out there that break down on how to use Odin, it's not that difficult to do.
This is why I don't endorse "One Click" anything unless it is a long process. Sure, it makes everything easier but it makes people not think about what they're doing before they do it. Before one clicking, rooting was so simple, put something on your internal sd and boot into recovery and hit reinstall packages. If something like that is too difficult then they shouldn't be doing any modifications in the first place unless they understanding what they're doing.
The T-Mobile forum is not a valid source because there is no concrete proof that they didn't root their phone and modified something. Even rooting and removing bloatware then removing access to root would cause this.
Edit: Looking at the OP's recent posts.. he did indeed run a custom ROM but has possibly did some tweaking after reverting back to stock?
Click to expand...
Click to collapse
Well, I know the 2 people that updated stock and got stuck at the vibrant screen were 100% stock because they both called me on what they need to do. one came over and I fixed it with ODIN back to stock (JI6) and the other just said he'd call TMO and get a replacement. they dont even know what rooting is, or that there is a site like that that they can get files to do "one click root"
OK. I'm the OP and I'm back. I was traveling today (with a phone flashed back to stock - that's as far as I got before getting kicked out of the hotel). I've now got the ROM restored and I'm where I was before trying to install the update.
My question is this (probably simple): my phone still wants to do the update. How do I make it go away? I can't install it, and I don't want to have to postpone it every day. Is there a cache I can clear or something?
You could just update it through Odin. I'm on stock with root and JAC's oc/uv kernel and the OTA failed but Odin worked perfectly.
Yes, I will try to flash it with odin when I have the time and interest, but for now I have neither, and I just want the phone to stop bugging me. Ideas?
JJMT said:
Yes, I will try to flash it with odin when I have the time and interest, but for now I have neither, and I just want the phone to stop bugging me. Ideas?
Click to expand...
Click to collapse
It will only stop once you are on JI6
camalot said:
It will only stop once you are on JI6
Click to expand...
Click to collapse
OK. I guess I will have to try to push the update through odin. Can someone point me to a link to the files?
I'm kind of irritated by this whole thing. I'm pleased with tmo for pushing the update out, but I mean, really, even Windows allows you to decline to install an update.
http://forum.xda-developers.com/showthread.php?t=798125
chad658eku said:
http://forum.xda-developers.com/showthread.php?t=798125
Click to expand...
Click to collapse
Thanks for the link. It really looks to me that I'm going to need to flash to a stock ROM before flashing JI6. That, as they say, is a bummer.
As I am actually quite content at the moment with Vibrant9, it really seems to me that it would be easier to somehow remove whatever it is on my phone that is requesting that I update. Presumably there is an update.zip file sitting somewhere, that will be copied into sdcard before the updater involves reboot recovery. Any ideas where to look?
I would really rather not do any further flashing until is an official Froyo to flash to.
JWhipple said:
So now instead, they get flooded with returns because the phone isn't what people expected.
Click to expand...
Click to collapse
Flooded with returns by morons who think they are smart.
Ok, I'm going to preface this thread with the statement "I am a noob".
Now... I'm working on unlocking the bootloader so that I can start checking out roms (Virtuous Prime and Cornerstone). I rooted the tablet last night, and then tried to unlock the bootloader, but keep getting the message "Failed to unlock your device, please try again later". What is the problem here? It's been mentioned to me to try flashing the Asus .15 update from the site onto the tablet, and then trying a factory reset afterwards if that doesn't work. Anyone else had this problem and fixed it? I have tried unrooting and doing it also. When I try this, I am connected to the internet. Also, I am on the latest .15 update via an OTA update. I have not tried to unlock the boot loader or root previous to last night.
Thanks.
i to am having the same issue ! any help would be apprieciated.
Deathbyfugu said:
Yes, I did get it solved. I had to download the full 9.4.2.15 update from Asus, extract the .zip and rename the other .zip contained within it to "SD201_UPDATE.zip" and place it on the Micro SD. Then reboot the Prime and hold Vol Down and Power until some text appears on the upper left and then press Vol Up. This will reflash the official firmware and after that is done you can either try once more or do a factory reset. After a factory reset (if it didn't work after the initial process) it should work without an issue.
Click to expand...
Click to collapse
This is what I was told via a PM as he also had the same problem. I don't have an sd card here large enough to put the whole update on to flash (if I'm even understanding how this all works correctly)(it's only 512MB and the update is 547 or so).
I didn't want to do a factory reset quite yet as I need to backup the photos and things on my tablet. Although, I'm not sure; I may lose everything once I install a rom? I'm still researching all of this...
Go to Settings, About and check to see if you have a serial.
If not..
http://androidroot.mobi/2012/01/31/introducing-ratchet-the-unknown-serial-fix/
Have a nice day
Under "Status", the field that says "Serial number" is filled in with my correct/matching serial number, yes.
yes same here i had an unkown serial issues but i fixed that a couple days ago and havent been able to unlock this mug
I'll be giving the method mentioned to me via PM a try this evening when I get home from work if I don't have any other answers regarding how to make it work, and report back. Already backed up most of my important data.
Having the exact same problems plus I'm having trouble getting ANY updates working prior to wanting to unlock my bootloader... thought unlocking and update with new ROM would solve things...
Add me to the list of: "Failed to unlock your device. Please try again later"- serial number is listed and correct... :-/
Sent from my HTC ThunderBolt using Tapatalk
Sounds like something isn't working right on the server side. Maybe Asus is doing maintenance on the server or it crashed or they even disabled it.
Of course, when I finally decide, "OK, it's relatively safe to unlock, flash CWM and get some custom ROMs on here..." the unlock tool stops working. Hopefully just a temporary thing
Sent from my Transformer Prime TF201 using Tapatalk
Same issue here
I too am getting the issue. I re-downloaded .15 firmware, reinstalled, and factory reset and still no luck. Hoping its just something on the Asus end of things. really want some custom rom love on my prime.
same thing here everyone ughh
Hmm, well I guess at least it's not just me. Fudge, was really looking forward to getting this going.
Reloaded83 said:
Hmm, well I guess at least it's not just me. Fudge, was really looking forward to getting this going.
Click to expand...
Click to collapse
Yea me to. i wonder why its happening. I never had a serial issue and i received all the updates no problem
AndroidPhan said:
Yea me to. i wonder why its happening. I never had a serial issue and i received all the updates no problem
Click to expand...
Click to collapse
Same here.
I have a feeling Asus retracting the tool. or not allowing people to unlock anymore from all the complaining going on.
demandarin said:
I have a feeling Asus retracting the tool. or not allowing people to unlock anymore from all the complaining going on.
Click to expand...
Click to collapse
Why ASUS, why must you do such a thing?
For me the same problem, I received ota updates at .15 and I can not unlock. Solutions?
Thanks
Worked this morning 3/2/12 at 7:15 am Eastern time
Woke up this morning and figured I'd try again to unlock my prime, and what do you know, worked the very first time. Looks like maybe it was things on the Asus end. Please let me know if anyone else gets this to work today.
I managed to break the Wifi on my tablet. I had root, accidentally replaced a file I shouldn't have, thought that wiping and flashing the .21 update would work...it didn't. It wouldn't flash because a system file had been modified.
Because I broke the wifi, I can't unlock. I basically am stuck waiting for .21 to be rooted.
Devs, are we close to root? I'm sure you're working on it and I applaud your efforts. Is this firmware super closed off? I'm not asking for an ETA, but maybe more of a status update. Just let me know there is hope
EDIT: I fixed it! I was able to pull an .apk of OTA Voodoo Rootkeep from a previous Titanium Backup file. I installed the app, and it restored root for me! Its possible that I was already still rooted, but without the ability to d/l apps I couldn't do anything about it. Anyway, I'm back with a rooted .21!
I think I had a similar issue....was using wifi tethered to phone...with modded wpa files....Couldn't OTA for .21......no computer/no router to get a wifi connection.
Went to Mickey D's for a free wifi connection....downloaded and installed .15 (for orig files) via SD card.
After that was finished, used OTA to download .21 ...if there are still issues, download it and manually install it via SD card.
Here's instructions to do it via SD card:
http://service.asus.com/TF201_fwupdate
Yeah I had to do that method when I first updated to .21. But then, after .21 I couldn't tether even though the chanelog said ad hoc wifi was supported. So I tried that method again, and broke it. Now I have no root and no wifi.
Waiting for someone to find root for .21 is killing me. lol
Any Devs want to chime in and give us an update on the .21 root process?
http://transformerprimeroot.com/tra...orkmod-recovery-5-8-2-0-on-transformer-prime/
use this. windows didnt work for me, drivers were messed up.
i used the mac method with no drivers required. (same with linux) and it worked flawlessly. pushed CWM using this, then flashed primeval .21 firmware.
stock .21 but with root.
requires unlock
Thanks, but I can't even unlock due to no data connection
I wonder if I could do it with an USB Ethernet dongle?
We definately need some tool to recover from such positions... NVflash or anything. This way its just too risky to temper with files if you're not unlocked imho. I remember about 3-4 cases where people got issues because of trying to improve stuff by editing files like build.prop etc.
Gogo devs, Asus, nVidia... Anyone, give us some tools to be safe
Definitely. I purchased a square trade warranty so that when I unlock I am still covered. However, why should I have to?
I sincerely hope a dev can get us root one .21 at least, and maybe some kind of unlock tool that doesn't report to Asus. And of course, NVFlash
the unlock is just an APK from asus? cant download that and put on SD?
malaeus said:
the unlock is just an APK from asus? cant download that and put on SD?
Click to expand...
Click to collapse
Its simple enough to install, but the app requires a connection with Asus' servers to record the Prime's serial number and then distribute a unique unlock key.
McLiarpants said:
Its simple enough to install, but the app requires a connection with Asus' servers to record the Prime's serial number and then distribute a unique unlock key.
Click to expand...
Click to collapse
Ah was not aware of such communication. Sorry :-(
Have you tried going online with a usb ethernet dongle?
I was going to look into this option, but I was able to fix my wifi!
I pulled Titanium Backup .apk files of my old apps and installed voodoo rootkeeper. it restored root (its possible I never actually lost root, just the ability to d/l apps like root explorer because of broken wifi)! I then loaded my backup of root explorer and copied the correct wpa_supplicant file.
I then immediately unlocked and flashed Virtuous Prime .21. I purchased a square trade warranty with accidental damage protection in case I have any problems with it.
It would be nice to know if I could do that for my unrooted Prime I accidentally upgraded to .21 before rooting. My other Prime is on .21 with root.
I'm sure it is because you had root before, but maybe it's worth a try.
McLiarpants said:
I purchased a square trade warranty with accidental damage protection in case I have any problems with it.
Click to expand...
Click to collapse
Has anyone confirmed that squaretrade considers unlocking and intentionally voiding your warranty "normal use"? I too am getting disheartened waitig for .21 root method. I would love to install custom rom and never have to worry about it again if squaretrade will cover a bricked device. However, I'm afraid if I void my warranty ASUS might decide not to honor the device with warranty issues such as gps dongles, etc.
casey225 said:
Has anyone confirmed that squaretrade considers unlocking and intentionally voiding your warranty "normal use"? I too am getting disheartened waitig for .21 root method. I would love to install custom rom and never have to worry about it again if squaretrade will cover a bricked device. However, I'm afraid if I void my warranty ASUS might decide not to honor the device with warranty issues such as gps dongles, etc.
Click to expand...
Click to collapse
What I've heard from other people is that the warranty says that they don't support intentional hardware or software modifications that would also void the manufacturer's warranty. Such as unlocking or opening the unit. However, if you have the accidental warranty and you drop it after being unlocked, they will fix it or replace it.
So if you have a problem with it after unlocking, it may need an "accident" to happen before you send it into ST.
clouds5 said:
We definately need some tool to recover from such positions... NVflash or anything. This way its just too risky to temper with files if you're not unlocked imho. I remember about 3-4 cases where people got issues because of trying to improve stuff by editing files like build.prop etc.
Gogo devs, Asus, nVidia... Anyone, give us some tools to be safe
Click to expand...
Click to collapse
there is a method to recover from this, grab the full update not the patch one from asus website, put it on a microsd card, and boot recovery
McLiarpants said:
So if you have a problem with it after unlocking, it may need an "accident" to happen before you send it into ST.
Click to expand...
Click to collapse
Understood I would still have to hope that Squaretrade doesn't determine the true problem, otherwise, would be SOL on all fronts. I will try to wait it out for now, but, I think I hear Virtuous Prime calling my name as I type this message.
casey225 said:
Understood I would still have to hope that Squaretrade doesn't determine the true problem, otherwise, would be SOL on all fronts. I will try to wait it out for now, but, I think I hear Virtuous Prime calling my name as I type this message.
Click to expand...
Click to collapse
I am running VP now, but I really like AOKP. The only reason I'm running VP is because Polaris isn't working on AOKP. I know it has some bugs, but I can't work with the lag between hitting a key and the letter showing on the screen in other office apps. I also haven't been willing to pay $15-$30 for an app to see how laggy it is.
lilstevie said:
there is a method to recover from this, grab the full update not the patch one from asus website, put it on a microsd card, and boot recovery
Click to expand...
Click to collapse
The update wont install if any of the system files are modified. It would be nice if it did, but it doesn't, unfortunately.
TB Pro restore with rooted .21 (NOT UNLOCKED)
So I had a thought and I am not sure that this will work. I have a TF101 that was rooted on 9.4.2.17 then upgraded to 9.4.2.21 (without any rootkeeper installed). Still have root but decided to install Voodoo RootKeeper just in case.
I have TB Pro installed and the Dev claims that you can restore to dissimilar hardware. My thought is to restore the APP+DATA+SYSTEM backup to my TF201 that is currently running 9.4.2.21 without root.
Any thoughts on this idea?
Niles
Before everyone feels obligated to point this out... yes, I know this will prevent me from unlocking the bootloader. I plan to stick with stock ROM's, so that should not be a problem for me.
I've downloaded the OTA, and made a copy on me SD card.
When I try to run the update normally, it fails without any error message I can see.
When I rename the OTA file to update.zip and try to update from sdcard through recovery, I get an error message referring to build.prop. As far as I can remember, I have never done anything with build.prop on this device. In any event, I'm not sure what to do to fix this.
I would like to get the update installed. Any ideas?
Be glad, that it fails. There is something that do not match and if it would go through, your phone would be dead.
Look in the zip /meta-inf/com/android/metadata, open it and check what pre-build do you need. You must have this one in the phone without root or other changes.
peetr_ said:
You must have this one in the phone without root
Click to expand...
Click to collapse
I doubt that's true. My wife's photon was rooted and did the OTA just fine.
Ok. But after some readings here I wouldn't risk that.
friends, brothers, fellow technologically advanced people lend me your ears
yea, I "figured" it out. had the same problem, but now "at last" i'm on 2.3.5
you're going to have to flash (back to stock; unroot) as done in the qbking video here
http://www.youtube.com/watch?v=J94VcWk-CJc
but when you're choosing which sbf file to flash, dl, - pick '154'
i tried the 198_6 but that didn't work for me.
once you've flashed '154,' you'll have to do two updates before you get to the 2.3.5 one
.....note: after the first one, i lost wifi and 3g, but a quick reboot brought it back.
.............note 2: after you've flashed 154, your photono will take a while to find service, because it'll be deactivated on the phone,
but then it just gives you an option to 'activate' and you're good.
when i was rooted i got rid of some of the bloat sprint stuff; i think that's the 'root' of the problem.
alexthen said:
you're going to have to flash (back to stock; unroot)
Click to expand...
Click to collapse
Not really.
My device has never had anything but stock. It's rooted, but my wife's was also rooted and had no trouble.
I just copied her build.prop to my device and the update went without a hitch. I am fairly certain I never modified my build.prop, but I suppose it's possible. I had to use her 2.3.5 build.prop, too, since this happened after she upgraded.
I never did figure out what the problem was, so the issue that is the thread topic of figuring out what was keeping the update from succeeding is not actually solved. However, a potential solution to the failed upgrade is to copy a different build.prop.
Nexus 7, 2013, 16 gigs, wifi model.
Every few days(sometimes once a day) I get a 'new' android 4.3 update, which once it reboots into the teamwin bootloader, and finishes installing the update(which always seems to work for first 2 steps but says no contents in file, then 2 errors after) I lose root access and it asks if I want to reapply(which I do) and it loads as normal on a restart. I am with build number JWR66N now, but the info page on the TWRP window shows it updates JWR66N to (And I forgot the number here, but its different)
So I'd like to know, is it normal to have 'constant' android updates like this, and if not, what build number should I have?
I have had this issue since about a week after I got my nexus, its been rooted ever since, but in an attempt to fix this issue(Which is just annoying, I doubt its causing any real damage) I unrooted the nexus, updated it(Manually) and re-rooted it using the wugfresh rootkit.
What exactly is the issue here, and how can I fix it?
AtmaDarkwolf said:
Nexus 7, 2013, 16 gigs, wifi model.
Every few days(sometimes once a day) I get a 'new' android 4.3 update, which once it reboots into the teamwin bootloader, and finishes installing the update(which always seems to work for first 2 steps but says no contents in file, then 2 errors after) I lose root access and it asks if I want to reapply(which I do) and it loads as normal on a restart. I am with build number JWR66N now, but the info page on the TWRP window shows it updates JWR66N to (And I forgot the number here, but its different)
So I'd like to know, is it normal to have 'constant' android updates like this, and if not, what build number should I have?
I have had this issue since about a week after I got my nexus, its been rooted ever since, but in an attempt to fix this issue(Which is just annoying, I doubt its causing any real damage) I unrooted the nexus, updated it(Manually) and re-rooted it using the wugfresh rootkit.
What exactly is the issue here, and how can I fix it?
Click to expand...
Click to collapse
really this is just an issue I have and nobody else has seen it? Nobody at all has had this problem and knows the fix? Well gee!
Another bump just incase, its happened again: Update yet nothings actually changed, had to 'swipe to fix' root permissions in bootlader menu.
Here we are again, and i REALLY want to get this fixed, and i just can't accept that 'I'm the only bloody nexus 7 user world frakin wide who has this issue.
So here I am again hoping for some help.
Build JWR66N currently, every few days it tries to update android OS, and it FAILS TO UPDATE, (IT wants to update to JSS15R i think)
New update is 53.8 mb,
Someone please help me out here, how do I get it to either accept the update, or stop freaking out about it?
AtmaDarkwolf said:
Here we are again, and i REALLY want to get this fixed, and i just can't accept that 'I'm the only bloody nexus 7 user world frakin wide who has this issue.
So here I am again hoping for some help.
Build JWR66N currently, every few days it tries to update android OS, and it FAILS TO UPDATE, (IT wants to update to JSS15R i think)
New update is 53.8 mb,
Someone please help me out here, how do I get it to either accept the update, or stop freaking out about it?
Click to expand...
Click to collapse
So from all this time, you weren't able to find your answer using the power of internet?
Stock OTA updates cannot be applied with custom recoveries. That's why it's failing.
JSS15R is 8MB though, not 53.8MB. Either way, you can go back to full stock, recovery included after backing up your stuff. Then update, and reroot + re-install a custom recovery.
Aside from that, you're not really in the good section so don't be surprised you don't get any answer. This is strictly a N7 question, and XDA has a N7 sub section...
http://forum.xda-developers.com/forumdisplay.php?f=1673
polobunny said:
So from all this time, you weren't able to find your answer using the power of internet?
Stock OTA updates cannot be applied with custom recoveries. That's why it's failing.
JSS15R is 8MB though, not 53.8MB. Either way, you can go back to full stock, recovery included after backing up your stuff. Then update, and reroot + re-install a custom recovery.
Aside from that, you're not really in the good section so don't be surprised you don't get any answer. This is strictly a N7 question, and XDA has a N7 sub section...
http://forum.xda-developers.com/forumdisplay.php?f=1673
Click to expand...
Click to collapse
Yes, Must that I foolishly thought this was a ANDROID device and this may have been a similar issue(searched n7 forums and saw nothing) - and even with all the googling, I got nothing. BUT Now that I have 'followed your advice' (God I hope I can get my stuff back, backup didn't go as smooth as I had hoped, and 2 of my fav games I had to copy/paste myself to save them) All I've managed to do now was reset my device back to complete stock settings.... and this morning, Low and behold: SYSTEM UPDATE, ONCE AGAIN, same bloody one, same bloody problem, WILL NOT INSTALL.
So thanks. Next please? (Sorry if I sound a little angry, but I am, this forum, at least I THOUGHT, was full of people who liked to help others and KNEW what they were talking about, not trolls who tell people to 'use the search button' or go elsewhere for help. Honestly, after 2-3 hours a night googling this issue, for 3 weeks give or take now, trust me, I know its not like I have anywhere but here to go, the only reason I'm HERE, in THIS subforum, was because similar issues were posted about right here... more similar than anywhere else.)
Anyways, now I got a wiped device which I hope I can at least get back to where I was. Knowing NOW it had nothing to do with being stock or not, its simply unable to install update.
AtmaDarkwolf said:
Yes, Must that I foolishly thought this was a ANDROID device and this may have been a similar issue(searched n7 forums and saw nothing) - and even with all the googling, I got nothing. BUT Now that I have 'followed your advice' (God I hope I can get my stuff back, backup didn't go as smooth as I had hoped, and 2 of my fav games I had to copy/paste myself to save them) All I've managed to do now was reset my device back to complete stock settings.... and this morning, Low and behold: SYSTEM UPDATE, ONCE AGAIN, same bloody one, same bloody problem, WILL NOT INSTALL.
So thanks. Next please? (Sorry if I sound a little angry, but I am, this forum, at least I THOUGHT, was full of people who liked to help others and KNEW what they were talking about, not trolls who tell people to 'use the search button' or go elsewhere for help. Honestly, after 2-3 hours a night googling this issue, for 3 weeks give or take now, trust me, I know its not like I have anywhere but here to go, the only reason I'm HERE, in THIS subforum, was because similar issues were posted about right here... more similar than anywhere else.)
Anyways, now I got a wiped device which I hope I can at least get back to where I was. Knowing NOW it had nothing to do with being stock or not, its simply unable to install update.
Click to expand...
Click to collapse
you cant update your phone if it is rooted you have to unroot for that or just temporary unroot the option is available in supersu /superuser
and some apps like root keeper and you have to be on stock recovery
AtmaDarkwolf said:
*snip*
Click to expand...
Click to collapse
Not trolling, the sub categories are there for a reason.
Good luck!