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.
How do you root the Thunderbolt after the 7/8/11 OTA?
Rooting using the old method doesn't work anymore?
flooritnfly said:
How do you root the Thunderbolt after the 7/8/11 OTA?
Click to expand...
Click to collapse
you would use the same process as before.
lostnuke said:
you would use the same process as before.
Click to expand...
Click to collapse
Yeah, use the same method. After your rooted, flash the rooted OTA stock Rom (google it) and also flash the its radio. That's what I did.
Sent from my rooted stock OTA MR2 Thunderbolt
So.... I can use this (http://forum.androidcentral.com/thu...unroot-windows-updated-5-20-w-mr1-update.html) like I did before then just flash the new radio that was released on 7/8 ?
Well now after 7/8, you have to flash while standing on your head. Yeah, its crazy like that.
bthomp21 said:
Well now after 7/8, you have to flash while standing on your head. Yeah, its crazy like that.
Click to expand...
Click to collapse
That is too funny.
I am unable to install the 7/8 Combo Radio package after installing DasBAMF Stripped 1.8.6
Constantly says "Installation Aborted."
Anyone else with this experience? I thought that I had read that this combo worked.
Got this sorted. I was using an MR1 package, not MR2, apparently. Using a different packaging of the OTA update flashed in via HBOOT.
BoulderGeek said:
I am unable to install the 7/8 Combo Radio package after installing DasBAMF Stripped 1.8.6
Constantly says "Installation Aborted."
Anyone else with this experience? I thought that I had read that this combo worked.
Click to expand...
Click to collapse
Your flashing it through the bootloader right? You can't use clockwork to flash it.
Sent from my rooted stock OTA MR2 Thunderbolt
Thunderbolt/Android Noob
OK .. I have this HTC Thunderbolt .. I want to root it .. I have read the forums up and down ... I saw the link above to AndroidCentral that shows how to root it, and one over in the Thunderbolt Development forum that says MR1 Perma Root ...
I would like to know the best route for me to go with minimal risk of bricking. I have flashed my wife's LG Ally a couple of times .. was easy enough, just ran an exe
All of the ones I have found for the thunderbolt seem to be a lot more complex. Is there a OneClick method I can run that will include the new radio (so i can get the latest fixes)?
If not, I am willing to go the ADB route (I have the Android SDK installed) but I dont know how to update the radio.
Thanks, and sorry to ask a question that seems to have already been answered, I am only asking b/c I did not understand your answers above ..
Use adb to root. Radio is done through hboot. Power off phone. Then hold vol key down and power on. Will bring you to hboot. Make sure radio is at root of SD card and is named properly. There is a sticky in the DEV section that will walk you through it.
courtesy of my rooted bolt
I just used the XDA development one. The key point is to read it carefully several times and be sure you understand each step. Ask questions beforehand if you are not sure about something. And be sure to follow each step exactly. Typos are the biggest risk, so go slow and read what you've typed on each line before hitting enter.
The radio file needs to be renamed to PG051IMG.zip and placed on the root of the SD card. Then power off and boot into bootloader. It'll load automatically after you hit +volume to confirm "yes ".
I had several flashes that resulted in the Exclamation Point warning triangle. Pulling the battery and USB cable and reinstalling power got me back to a running build.
It took me a while to do every step. I wanted to skip steps, not realizing that you needed the downgrade and RUU flashes to get S-OFF and unlock.
Once that was all done, I went to DasBAMF Stripped and found the OTA radio in this thread http://forum.xda-developers.com/showthread.php?t=1160346.
So far, so good. Calibrating battery now and trying to personalize and optimize to my best ability.
Ok so from what I gather there are no issues that would prevent any of the previous methods from working post 7/8 update? That includes the one click app thats been floating around for a few months right?
I've been holding off root for months, but my patience has finally run out, time to do what I should have done from the beginning.
EDIT
on second thought, I think I'll just do it the good old fashioned way
I did the 7/8 update, and was fine with it. I just wanted to get the Verizon bloatware off. I had problems installing the stock debloated ROMs, so i ran with BAMF to test, and since it worked, I kept it. My rooting came after the recent OTA.
The once-click and .bat methods didn't work so well for me, so I followed the full instructions in a CMD window (I can't call that POS in DOS a shell).
Most of my time was installing a correct Java JDK (had to use x86 instead of x64) and getting ADB dialled in.
KO'B said:
Ok so from what I gather there are no issues that would prevent any of the previous methods from working post 7/8 update? That includes the one click app thats been floating around for a few months right?
I've been holding off root for months, but my patience has finally run out, time to do what I should have done from the beginning.
EDIT
on second thought, I think I'll just do it the good old fashioned way
Click to expand...
Click to collapse
I had the same thinking and wanted it the quick and easy way. Doing the research and taking the time (and beers ) to do it manually was very informative and satisfying when i got done. It was said already but ive been able to apply any feature that an official OTA would give long before its normally released to verizon customers. I love my Tbolt and wouldnt have it any other way.
BryanB32 said:
I had the same thinking and wanted it the quick and easy way. Doing the research and taking the time (and beers ) to do it manually was very informative and satisfying when i got done. It was said already but ive been able to apply any feature that an official OTA would give long before its normally released to verizon customers. I love my Tbolt and wouldnt have it any other way.
Click to expand...
Click to collapse
Doing things the long way has never really scared me, but some of the horror stories I kept hearing a month or two back about instability of GB roms had me a bit hesitant to go for it.
It does appear to be a bit more involved than what I am accustomed to, but I have used ADB before, I was just trying not to this time.
Can someone give me a bit of advice actually.
I'm on the end of Step 4 found in the Developement section, and when I hit Bootloader, it brings up a second menu not mentioned in the posts, what do i do from here?
Nevermind once again, screwed up the name of the zip file
I used the auto root method 3 times so far and worked great. I did the full last update and lost root so I had to redo it load Rom and just added the radio file in hboot.
try auto root its fast and simple just follow the commands on the screen!
I have an unrooted HTC Aria (AT&T) that i upgraded to Froyo a couple of weeks ago. I have been using it for a while and i don't like the performance with the new upgrade, it used to be a LOT snappier before.
I would like to know if its possible to revert the phone to Factory Defaults (Eclair 2.1) and where i can get the ROM since HTC is no longer providing it in its website.
I'm not interested in rooting my phone nor custom roms i just want it the way it was at the moment I took it off the box and turned it on for the first time.
If the downgrade is possible I would really appreciate if someone could provide a list of steps to follow to make it happen.
Thanks in advance.
Check out this thread: http://forum.xda-developers.com/showthread.php?t=971119. You can but you will still have the updated HBOOT (Bootloader). You will have to use the ROM linked in post 3 (Original 2.1 Rom)
P.S - Search before starting new threads on the same topic.
http://www.mediafire.com/?cj56c2gfk86k8oe
This is the original ship ROM. I downloaded this back when I first got my phone (first day the Aria was released) and have kept it for future use. This was even before they added the ability to receive OTA updates, so you won't even have to worry about being notified about the 2.2.2 OTA update.
Now, you should be able to just run this and have it downgrade everything (except HBOOT, but that isn't a problem unless you want to root). I haven't actually done it before but it should work.
If it doesn't work, there is another way that will definitely work, but I'll explain that if the need arises. Let me know if you run into any problems.
Theonew said:
Nope. Not possible since you don't want to root your device.
Click to expand...
Click to collapse
It is possible. You can downgrade everything except the HBOOT. (Meaning, he will have the original ROM like he wants but be unable to use Unrevoked, which he doesn't care about.)
drumist said:
It is possible. You can downgrade everything except the HBOOT. (Meaning, he will have the original ROM like he wants but be unable to use Unrevoked, which he doesn't care about.)
Click to expand...
Click to collapse
That post I made was a mistake. That's why I edited it. Sorry I didn't get to change it in time.
Theonew said:
Check out this thread: http://forum.xda-developers.com/showthread.php?t=971119. You can but you will still have the updated HBOOT (Bootloader). You will have to use the ROM linked in post 3 (Original 2.1 Rom)
P.S - Search before starting new threads on the same topic.
Click to expand...
Click to collapse
To be honest the advice from those threads is not really very good anyway. You don't need temp root on your device. There are easier methods that ought to work fine. Namely, just putting the 2.1 RUU zip as LIBEIMG.zip on your SD card. But from what I've read, even just running the RUU should be enough.
(Nevermind, this doesn't work.)
Thanks for you advice, in fact did some research before creating the thread, but all the threads i found were about people who wanted to downgrade to get the root back, so they were either redirected to other threads or were given a lot information not relevant to what i really need.
drumist said:
This is the original ship ROM. I downloaded this back when I first got my phone (first day the Aria was released) and have kept it for future use. This was even before they added the ability to receive OTA updates, so you won't even have to worry about being notified about the 2.2.2 OTA update.
Now, you should be able to just run this and have it downgrade everything (except HBOOT, but that isn't a problem unless you want to root). I haven't actually done it before but it should work.
If it doesn't work, there is another way that will definitely work, but I'll explain that if the need arises. Let me know if you run into any problems.
Click to expand...
Click to collapse
I tried this but for some reason i got a BOOTLOADER VERSION ERROR [140] message. Thanks for your help anyway.
eljuanpelos said:
I tried this but for some reason i got a BOOTLOADER VERSION ERROR [140] message. Thanks for your help anyway.
Click to expand...
Click to collapse
Don't give up yet. This next method should work if that one didn't.
Download this file: http://www.mediafire.com/?ct1ay7t93d8g742
Rename the zip file as LIBEIMG.zip (don't extract it) then place it on your SD card (not in a subfolder).
Then turn the phone completely off, and press VOL DOWN + power to turn the phone back on. It should detect the file after a couple seconds and start flashing it automatically. At this point just be patient for a minute or two, then press VOL UP key to start the update process when it asks you to. After that, be patient while it does everything. It takes about 5 minutes to finish installing everything and will reboot once during the process. After it's done (it will tell you when it's done), the phone will reboot and there will be a scary looking screen but JUST WAIT about 10 seconds and it will boot normally. Then you're good to go.
After you're done with this, make sure to DELETE the LIBEIMG.zip file from your SD card. Otherwise it will ask you every time you go into HBOOT if you want to apply the update.
Good luck.
drumist said:
Don't give up yet. This next method should work if that one didn't.
Download this file:
Rename the zip file as LIBEIMG.zip (don't extract it) then place it on your SD card (not in a subfolder).
Then turn the phone completely off, and press VOL DOWN + power to turn the phone back on. It should detect the file after a couple seconds and start flashing it automatically. At this point just be patient for a minute or two, then press VOL UP key to start the update process when it asks you to. After that, be patient while it does everything. It takes about 5 minutes to finish installing everything and will reboot once during the process. After it's done (it will tell you when it's done), the phone will reboot and there will be a scary looking screen but JUST WAIT about 10 seconds and it will boot normally. Then you're good to go.
After you're done with this, make sure to DELETE the LIBEIMG.zip file from your SD card. Otherwise it will ask you every time you go into HBOOT if you want to apply the update.
Good luck.
Click to expand...
Click to collapse
Unfortunately this method doesn't work either, it throws an error that says "Main Version is older, Update Fail!"
I could have sworn I've read about this working before. I would have tested it first myself but I don't have a phone that isn't S-OFF. Sorry for making you jump through hoops.
You could try the methods in the other threads linked above. I guess you do need temp root to do a downgrade.
Alternatively, you could use AlphaRevX to S-OFF, install Clockwork, and install the factory original, unrooted ROM. The downside of this is that it requires voiding your warranty if you have one.
Easiest way would be to run the official 2.2 RUU update from HTC. 100% stock.
Sent from my Liberty
Optic2 said:
Easiest way would be to run the official 2.2 RUU update from HTC. 100% stock.
Sent from my Liberty
Click to expand...
Click to collapse
He wants to return to android 2.1 so that wouldn't help whatsoever. Plus he already did that which is why he wants to downgrade.
Oh my bad, I didn't read the whole thread. Hmm why do you want to downgrade to 2.1?
Sent from my Liberty
Optic2 said:
Hmm why do you want to downgrade to 2.1?
Sent from my Liberty
Click to expand...
Click to collapse
This is the reason which he said in his post:"I don't like the performance with the new upgrade, it used to be a LOT snappier before."
drumist said:
This is the original ship ROM. I downloaded this back when I first got my phone (first day the Aria was released) and have kept it for future use. This was even before they added the ability to receive OTA updates, so you won't even have to worry about being notified about the 2.2.2 OTA update.
Now, you should be able to just run this and have it downgrade everything (except HBOOT, but that isn't a problem unless you want to root). I haven't actually done it before but it should work.
If it doesn't work, there is another way that will definitely work, but I'll explain that if the need arises. Let me know if you run into any problems.
Click to expand...
Click to collapse
One question... I have HTC Gratia, which is operator free, so can I restore your original (backuped) ROM on my phone and update it, so I can use it just like original one?
I'm rooted and originally de-crapped my phone which kept the first update from installing. However, with some help from posters here I was able to find the missing file, get it properly replaced and the update then worked.
I assumed that would mean I would be good from then on and kept everything intact. Now the latest update is out and I once again cannot update but it's been long enough that I'm now not sure about the process for getting this working.
Any help would be appreciated.
Agrajag27 said:
I'm rooted and originally de-crapped my phone which kept the first update from installing. However, with some help from posters here I was able to find the missing file, get it properly replaced and the update then worked.
I assumed that would mean I would be good from then on and kept everything intact. Now the latest update is out and I once again cannot update but it's been long enough that I'm now not sure about the process for getting this working.
Any help would be appreciated.
Click to expand...
Click to collapse
Come on guy, there is like 10 other threads over here talking about not being able to install the update. Anyway, there is a thread right here that has all of the apk files of the device. I cant find it now cause im on my cell. Ifyou cant find it by the time I finish work I'll post the link. that didnt work for me so I fastbooted my phone with the factory image, rooted, protected root, unrooted,install one update, installed the latest update, and restored root. good luck.
I actually looked but didn't notice others having an issue so I might have just missed it. I assumed, like last time, others would have the issue so I was actually surprised not to find 10 threads with people talking about it.
I couldnt find the thread i was talking about cause my stupid self was too lazy to click one button to add it to my favorites but it looks like this could work for you.
http://forum.xda-developers.com/showthread.php?t=1362956
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.