Hi,
could someone send me the /system/bin/debuggerd file from JOP40D.
It has been modified somehow and blocks my upgrade...
Thanks, Goldstein
You can extract the file using the directions here:
http://forum.xda-developers.com/showthread.php?t=1945938
Hi,
problem is, that there is no factory image for JOP40D.
In the meanwhile, I solved the problem by flashing the new 4.2.2 factory image.
But what I really like to know is, which app changed the /system/bin/debuggerd. It created a /system/bin/debuggerd.backup but this one seemed also to be corrupt (not the stock version).
I had stickmount on the device and tried to mount CIFS/SMB shares with some apps.
Maybe some knows, which app created this backup file...
Regards,
Goldstein
theninjapirate said:
You can extract the file using the directions here:
http://forum.xda-developers.com/showthread.php?t=1945938
Click to expand...
Click to collapse
You can also try reapplying the update corresponding to your current Android version :
I just solved the same error by applying the 4.2.1 update again on my Nexus 7 4.2.1 tablet,
using clockworkmod, which left already up-to-date files alone but corrected /system/bin/debuggerd.
Upgrading to 4.2.2 went just fine after this manipulation, which suggest I had an older
version of /system/bin/debuggerd that did not match the expected one...
Elnareen said:
You can also try reapplying the update corresponding to your current Android version :
I just solved the same error by applying the 4.2.1 update again on my Nexus 7 4.2.1 tablet,
using clockworkmod, which left already up-to-date files alone but corrected /system/bin/debuggerd.
Upgrading to 4.2.2 went just fine after this manipulation, which suggest I had an older
version of /system/bin/debuggerd that did not match the expected one...
Click to expand...
Click to collapse
If your on a custom recovery just use this.
http://forum.xda-developers.com/showthread.php?t=2148381
Sent from my Nexus 10 using Tapatalk HD
Elnareen said:
You can also try reapplying the update corresponding to your current Android version :
I just solved the same error by applying the 4.2.1 update again on my Nexus 7 4.2.1 tablet,
using clockworkmod, which left already up-to-date files alone but corrected /system/bin/debuggerd.
Upgrading to 4.2.2 went just fine after this manipulation, which suggest I had an older
version of /system/bin/debuggerd that did not match the expected one...
Click to expand...
Click to collapse
Could you please put a link to the 4.2.1 update because it is no longer available from google's site.
theninjapirate said:
But what I really like to know is, which app changed the /system/bin/debuggerd. It created a /system/bin/debuggerd.backup but this one seemed also to be corrupt (not the stock version).
Click to expand...
Click to collapse
I'm not sure I'm helping those participating in the discussion here, but for stalkers and to tie up loose threads, it was stickmount that replaced /system/bin/debuggerd, from what I've read in other discussions about why the OTA update to 4.2.2 was being blocked. I had the problem and I had installed stickmount too.
shonangreg said:
I'm not sure I'm helping those participating in the discussion here, but for stalkers and to tie up loose threads, it was stickmount that replaced /system/bin/debuggerd, from what I've read in other discussions about why the OTA update to 4.2.2 was being blocked. I had the problem and I had installed stickmount too.
Click to expand...
Click to collapse
Thanks for sharing that. I for one solved it by downloading a fresh copy of debugerd from a stock image and then applied the update.
Sent from my Nexus 7 using Tapatalk HD
Related
Could someone post up the US ICS OTA file? I don't see it available on Lenevo's download site yet: http://download.lenovo.com/slates/think/tablet1/
It is on the Lenovo FTP
ftp://slatesftp:[email protected]/ThinkPadTablet_A310_03_0069_0130_US.zip
mandrsn1 said:
It is on the Lenovo FTP
ftp://slatesftp:[email protected]/ThinkPadTablet_A310_03_0069_0130_US.zip
Click to expand...
Click to collapse
upload it if you have it please the link is down now
Sent from my ThinkPad Tablet using Tapatalk 2
ker2gsr said:
upload it if you have it please the link is down now
Sent from my ThinkPad Tablet using Tapatalk 2
Click to expand...
Click to collapse
That link is still working for me. I don't have a service i can upload to right now.
mandrsn1 said:
That link is still working for me. I don't have a service i can upload to right now.
Click to expand...
Click to collapse
from your tablet or PC? no dropbox?
Sent from my ThinkPad Tablet using Tapatalk 2
ker2gsr said:
upload it if you have it please the link is down now
Sent from my ThinkPad Tablet using Tapatalk 2
Click to expand...
Click to collapse
Here a dropbox till its on the http:
http://dl.dropbox.com/u/11001249/ThinkPadTablet_A310_03_0069_0130_US.zip
US needs two update files if going the FTP site download route.....~A310~(291M) and ~A400~(4.9M).
eldata said:
US needs two update files if going the FTP site download route.....~A310~(291M) and ~A400~(4.9M).
Click to expand...
Click to collapse
I was able to download both from the FTP here: ftp://slatesftp:[email protected]/slates/think/tablet1/
Now the question I am wondering is... Is it worth it? Potentially sacrificing root and CWR? I have been running 0.0.7.3 CM9 build for many months now and am curious to what you all think.
Pros/Cons? I've heard battery life is terrible, which is odd because I feel like I have good battery life on the CM9 Port. Also... Is root completely gone? Does OTA Rootkeeper help? My biggest concern (I'd probably even lose root if it is fixed), does the pen work as advertised? Or is the infamous 'pen wonk' bug still present?
Pen wonk = writing notes for ~10-15 minutes, pen is suddenly not responsive. Sleep/waking the device fixes it usually. This has been present in every stock Honeycomb build as well as all the CM9 Port builds so I am very curious if this is fixed because I believe it is a hardware issue (Lenovo please prove me wrong). Any info would be much appreciated.
obscure.detour said:
Now the question I am wondering is... Is it worth it? Potentially sacrificing root and CWR? I have been running 0.0.7.3 CM9 build for many months now and am curious to what you all think.
Pros/Cons? I've heard battery life is terrible, which is odd because I feel like I have good battery life on the CM9 Port. Also... Is root completely gone? Does OTA Rootkeeper help? My biggest concern (I'd probably even lose root if it is fixed), does the pen work as advertised? Or is the infamous 'pen wonk' bug still present?
Pen wonk = writing notes for ~10-15 minutes, pen is suddenly not responsive. Sleep/waking the device fixes it usually. This has been present in every stock Honeycomb build as well as all the CM9 Port builds so I am very curious if this is fixed because I believe it is a hardware issue (Lenovo please prove me wrong). Any info would be much appreciated.
Click to expand...
Click to collapse
I was able to go from a rooted, CWM'd device (US 64GB) to a fully rooted device without CWM.
After a few painful steps to get an old busybox file restored and stock recovery enabled, the upgrade process was very simple and so far it is working very well with ICS. There hasn't been enough time to judge battery life yet....
Make sure you follow the instructions that other's have posted about using RootKeeper. That is the only thing I needed to use to restore root perfectly.
armondole said:
After a few painful steps to get an old busybox file restored and stock recovery enabled, the upgrade process was very simple and so far it is working very well with ICS.
Click to expand...
Click to collapse
I updated with CWR rather than reverting to stock recovery. Everything worked fine. However, it did get rid of the stock recovery.
armondole said:
I was able to go from a rooted, CWM'd device (US 64GB) to a fully rooted device without CWM.
After a few painful steps to get an old busybox file restored and stock recovery enabled, the upgrade process was very simple and so far it is working very well with ICS. There hasn't been enough time to judge battery life yet....
Make sure you follow the instructions that other's have posted about using RootKeeper. That is the only thing I needed to use to restore root perfectly.
Click to expand...
Click to collapse
That is good news about the ability to keep root. At least in keeping root, we should theoretically be able to restore CWR.
mandrsn1 said:
I updated with CWR rather than reverting to stock recovery. Everything worked fine. However, it did get rid of the stock recovery.
Click to expand...
Click to collapse
How were you able to update using CWR?
obscure.detour said:
That is good news about the ability to keep root. At least in keeping root, we should theoretically be able to restore CWR.
How were you able to update using CWR?
Click to expand...
Click to collapse
I commented out the lines of the update script that checked for "indigo" in build.prop.
so you're now on official ISC with Root AND CWM ??
it's a great news !
quyTam said:
so you're now on official ISC with Root AND CWM ??
it's a great news !
Click to expand...
Click to collapse
No, when ICS installed, it got rid of CWM.
mandrsn1 said:
I commented out the lines of the update script that checked for "indigo" in build.prop.
Click to expand...
Click to collapse
Do you mind posting how you did the whole install process? Thanks.
bigsnack said:
Do you mind posting how you did the whole install process? Thanks.
Click to expand...
Click to collapse
I did not have CWR to start.
I downloaded the update through the "update" menu on the device.
Update failed due to gps.conf being modified.
Reverted to what I thought was old gps.conf, update still failed.
Install CWR
Try update through CWR
Still fail, due to indigo being required in build.prop (this error is caused by CWR)
Commented out the Indigo lines in the update-script in the update
Flashed again
Still failed for gps.conf.
Commented out each line in update-script mentioning gps.conf
flashed again, it worked.
I take you flashed 310 first then 400?
Where is the script located?
bigsnack said:
I take you flashed 310 first then 400?
Where is the script located?
Click to expand...
Click to collapse
The update-script is in the META-INF/com/google/android folder in the zip. a # sign will comment out any line.
Do I put the number sign in the front?
bigsnack said:
Do I put the number sign in the front?
Click to expand...
Click to collapse
Here is the file i used
http://dl.dropbox.com/u/8479005/updater-script
Hello TPT community,
I Just got this tablet mainly because of the included digitizer and was wondering if anyone could give me a guideline on how to speed things up for this tablet. The tablet came with honeycomb 3.1 included and I am finding it pretty sluggish and unresponsive in general tasks. I went into settings to do a software update but it seems there is no 4.0 update available. There doesn't seem to be a toggle for pen only input in the settings either. Is the normal process for flashing a new Rom to root, then install CWM, and flash Roms?
I'm kind of a n00b here, but that is the right process in general.
For you, there should be a 4.0 update, but you might have to try a few times. After you are running ICS (4.0) you can root and load Koshu's JB rom.
Aren't there problems with rooting ICS?
Sent from my ThinkPad Tablet using xda app-developers app
Absolutely no problms rooting ics
Sent from my Micromax A50
Okay well I went into settings, about tablet, system updates, check for updates. It always says "your system is up to date" even though I know I'm on 3.1
Sent from my ThinkPad Tablet using xda app-developers app
Lets see if we can figure out why it won't update. In settings -> about tablet, what is listed for model number, android version, and kernel version?
Edit:
Found this - http://forums.lenovo.com/t5/ThinkPa...ystem-updates-OTAs-not-installing/ta-p/713571
It might help... I'm also searching for a manual download for ota3 or ota 3.5 from lenovo that you can load in recovery.
Edit 2:
Sorry, I need more coffee...
Is this a wifi only tablet or a 3g tablet? What region is it?
I attached the info in a picture. I dont know how to find out what region or wifi/3g it is though. I don't have a sim to test it. I got it from here: http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=7473177&CatId=6845
It is wifi only, also found this interesting thread - http://forums.lenovo.com/t5/ThinkPad-slate-tablets/thinkpad-1839-update/td-p/975085
Apparently the Tiger Direct refurb is a custom SKU and is SUPPOSEDLY not upgradeable... tho I would think there are ways around that. At least now I know what we are working with here.
da_reeseboy said:
It is wifi only, also found this interesting thread - http://forums.lenovo.com/t5/ThinkPad-slate-tablets/thinkpad-1839-update/td-p/975085
Apparently the Tiger Direct refurb is a custom SKU and is SUPPOSEDLY not upgradeable... tho I would think there are ways around that. At least now I know what we are working with here.
Click to expand...
Click to collapse
So any ideas on how to update to ICS? The ROM in android development section says it requires me to have ICS first.
Unfortunately no... sorry. I'm still a n00b with android devices. Maybe someone with a little more knowledge will chime in now that we know what we are dealing with.
You can root your tablet and go straight to Jelly Bean 4.1.1 or 4.1.2. It's fast and cool! The only little bug is with wifi!
Gesendet von meinem CM10 0.8.1 overclocked Jelly Bean 4.1.1 Thinkpadtablet
troemer said:
You can root your tablet and go straight to Jelly Bean 4.1.1 or 4.1.2. It's fast and cool! The only little bug is with wifi!
Gesendet von meinem CM10 0.8.1 overclocked Jelly Bean 4.1.1 Thinkpadtablet
Click to expand...
Click to collapse
A wifi bug is pretty big. The only connectivity mine has is wifi
I tried to install the adb drivers so I can root it but it says the driver has been tampered with so I can't install. I am on windows 8
Sent from my ThinkPad Tablet using xda app-developers app
@troemer: Not sure if you noticed it or not, but in Koshu's cm10 thread it says:
Requirements
This build uses the Lenovo ICS kernel, you need to upgrade to stock ICS first (Make sure you keep root!)
Click to expand...
Click to collapse
This is why he is trying to get the ICS update.
Daedalus_ said:
A wifi bug is pretty big. The only connectivity mine has is wifi
I tried to install the adb drivers so I can root it but it says the driver has been tampered with so I can't install. I am on windows 8
Sent from my ThinkPad Tablet using xda app-developers app
Click to expand...
Click to collapse
The wifi bug actually isn't that big, just set wifi to always on like suggested. As far as the tampered drivers error, you will probably have to : a) search for a way to install unsigned drivers on win8
or b) use a winxp/win7 pc.
Be careful tho... flashing after having stock ICS is needed for a reason.
Flashing what?
Daedalus_ said:
Flashing what?
Click to expand...
Click to collapse
Based on this:
Daedalus_ said:
A wifi bug is pretty big. The only connectivity mine has is wifi
Click to expand...
Click to collapse
I was worried you were gonna try to just jump straight to JB.
Hey there,
well one way is to try flashing the upgrade directly but like da_reeseboy already mentioned, there is a high possibility that it will fail. Only other way would be to flash the bootloader directly (that most likely the part, that keeps the JB kernel from booting on non ICS kernels) but there is a high bricking chance and eventually the firmware for some of the hardware needs to be updated, too, to work properly.
It looks like there's hope - this guy has the same weird software version as you - http://forum.xda-developers.com/showpost.php?p=37487649&postcount=6. He used the directions in that thread to upgrade to ICS.
Edit -
Full thread: http://forum.xda-developers.com/showthread.php?p=37487649#post37487649
Koshu said:
Hey there,
well one way is to try flashing the upgrade directly but like da_reeseboy already mentioned, there is a high possibility that it will fail. Only other way would be to flash the bootloader directly (that most likely the part, that keeps the JB kernel from booting on non ICS kernels) but there is a high bricking chance and eventually the firmware for some of the hardware needs to be updated, too, to work properly.
Click to expand...
Click to collapse
Just trying to think outside the box (noob style), what if he:
1. Installed CWM
2. Restored a clean 0075 nandroid from someone here on xda
3. Restored stock recovery
4. Checked for OTA to ICS
In my mind the software version is what is holding him back from updates, so I'm thinking that restoring an 0075 nandroid will put him in a position to get the update correctly... but I am still new to this so I could be WAY off.
da_reeseboy said:
Just trying to think outside the box (noob style), what if he:
1. Installed CWM
2. Restored a clean 0075 nandroid from someone here on xda
3. Restored stock recovery
4. Checked for OTA to ICS
In my mind the software version is what is holding him back from updates, so I'm thinking that restoring an 0075 nandroid will put him in a position to get the update correctly... but I am still new to this so I could be WAY off.
Click to expand...
Click to collapse
Thanks for still helping! Do I need a special CWM? I just root and install CWM from the market? Honeycomb is really annoying because some apps I use are only for newer androids such as Hulu plus.
Hi all - I just received a notice on my Nexus 7 that there is a system update to install. I already installed 4.3 build JWR66V a couple weeks ago. Anyone know what this update is? I can't seem to find any information anywhere. My device is unlocked and rooted, running stock.
Yeah, google has released a newer version, so if you're on stock, why not update?
Sent from my Nexus 7 using Tapatalk 4
It's an update from build JWR66V to JWR66Y, still Android 4.3.
If it's an OTA update, always install it.
It fixes a couple of issues after the 4.3 update
Sent from my Nexus 7(2012) that has zero issues.
Is it possible to update via ota when the device is unlocked and rooted? I updated it but it still says JWR66V, not Y. But when I look for an update it says up to date.
Gesendet von meinem Nexus 7 mit Tapatalk 4
Got the same issue as dakoookie
Sent from my Nexus 7 using Tapatalk 4
Will this update unroot it?
Yes you'll still recieve the update it just hasnt been pushed to you yet if it says up to date. Factory images for it are already up waiting on someone to make a zip for CWM
nikola1970 said:
Will this update unroot it?
Click to expand...
Click to collapse
OTA's always remove root
Apparently not. I updated but I still have root
Sent from my Nexus 7 using Tapatalk 4
Me too, but gives error when installing =(
Rooter and bootloader unlock
Had an error at then end of the installation but looks like it succeed to update it coz when i started my device it said that my applications are optimizating for the new version or something like that.
Build is JWR66V now, there is no any system updates now. Root is still there.
nikola1970 said:
Had an error at then end of the installation but looks like it succeed to update it coz when i started my device it said that my applications are optimizating for the new version or something like that.
Build is JWR66V now, there is no any system updates now. Root is still there.
Click to expand...
Click to collapse
Then the update failed the new OTA is JWR66Y
Lol the same questions.
Every.
Single.
Time.
FYI, I lost root.
Lost root also
NeoMagus said:
OTA's always remove root
Click to expand...
Click to collapse
Guess nobody believed me :silly:
Anybody working on a zip yet for the update??
If you lost root and it put you back on stock recovery just reflash your recovery then supersu
For the folks that are having "error" during the update, restart your n7 then clear cache and data from framework services and check for updates again and it should come up. Also make sure you at least have 80% battery level:good:
It's supposed to fix the phantom screen touch problem and a few other things I'm sure someone will come up with root G.B.Y.
Sent from my Nexus 7
There's an OTA .zip for build JWR66Y here... but there appears to be a problem with symlink permisssions.
But there is also a solution here http://forum.xda-developers.com/showthread.php?t=1745781&page=53 and a modified version of the OTA that fixes the permissions. Worked for me flashing via TRWP.
Incidentally, I also lost root after upgrading... not sure why... but not a big problem, as I reflashed SuperSU v1.51 in TWRP.
-----------------------------
Not quite sure what this very minor upgrade is supposed to accomplish, given 4.3 was only rolled out 4 weeks or so, ago.... but I suspect it has a lot to do with a minor screwup on Googles part, the details of which can be found here... http://forum.xda-developers.com/showthread.php?t=2382880.
I think (and I could be wrong), build JWR66Y is {AOSP JSS15J + Gapps}... in other words, JSS15J, released as Factory Stock instead of AOSP.
And the full factory image of JWR66Y is already available on the Google Developer website here and it's immediate predecessor, JWR66V has been 'pulled' and is no longer available for download.
Anyway, take a look at the above link, and you should see what I'm getting at.
Rgrds,
Ged.
grouper zip that was linked worked great here. No issues here now
I flashed the GE 4.3 for i9505, which is the following ROM
http://forum.xda-developers.com/showthread.php?t=2348272
Today I've received an 16MB OTA that told me the feature I can find contacts directly when dialing. (p.s. I'm using the zh-CN language.)
Obviously, it cannot be updated cause the model is mismatch though I made it a try somehow.
My TWRP returned "status 7" err.
I googled it and found a version JWR66V.S015 (my current is S014).
Does anyone got this update?
Is there anyway to flash in or just waiting for new ROM?
p.s. I'm a newbie here and I don't have the permission to reply in the DEV forums
jarmal's new ROM comes out! QUEST CLEAR. Lock plz.
http://forum.xda-developers.com/showthread.php?t=2348272
legendt said:
I flashed the GE 4.3 for i9505, which is the following ROM
http://forum.xda-developers.com/showthread.php?t=2348272
Today I've received an 16MB OTA that told me the feature I can find contacts directly when dialing. (p.s. I'm using the zh-CN language.)
Obviously, it cannot be updated cause the model is mismatch though I made it a try somehow.
My TWRP returned "status 7" err.
I googled it and found a version JWR66V.S015 (my current is S014).
Does anyone got this update?
Is there anyway to flash in or just waiting for new ROM?
p.s. I'm a newbie here and I don't have the permission to reply in the DEV forums
Click to expand...
Click to collapse
I also have GE rom and i also found it very strange that i got OTA update, however i didnt choose to install it incase i receive errors, which if i understood correctly you said it did give errors.
delphe88 said:
I also have GE rom and i also found it very strange that i got OTA update, however i didnt choose to install it incase i receive errors, which if i understood correctly you said it did give errors.
Click to expand...
Click to collapse
I would be perfect if only I9505 can be transformed into I9505G.
GE rom is faster and more stable than any other TW/AOKP/CM10.2 roms at present.
delphe88 said:
I also have GE rom and i also found it very strange that i got OTA update, however i didnt choose to install it incase i receive errors, which if i understood correctly you said it did give errors.
Click to expand...
Click to collapse
so it's not safe to do this update?
giodecia said:
so it's not safe to do this update?
Click to expand...
Click to collapse
Not exactly. Currently we cannot install this update so it is uncertain whether it is safe or not
legendt said:
Not exactly. Currently we cannot install this update so it is uncertain whether it is safe or not
Click to expand...
Click to collapse
Thanks...I'm a noob about flashing, so when you flash your smartphone with another ROM you generally can't update via OTA?
giodecia said:
Thanks...I'm a noob about flashing, so when you flash your smartphone with another ROM you generally can't update via OTA?
Click to expand...
Click to collapse
Almost right. Better to say once if you have a third-party recovery, you cannot install OTA with right pattern.
Just threw together a video showing how to manually update your Nexus 7 to 4.4 KitKat.
Hopefully this cuts down the questions. You must be on the 4.3 JSS15R build to update.
Video:
http://youtu.be/bgjH2E5oi0Y
qbking77 said:
Just threw together a video showing how to manually update your Nexus 7 to 4.4 KitKat.
Hopefully this cuts down the questions. You must be on the 4.3 JSS15R build to update.
Video:
http://youtu.be/bgjH2E5oi0Y
Click to expand...
Click to collapse
Can you rename the ota.zip to just ota.zip?
godutch said:
Can you rename the ota.zip to just ota.zip?
Click to expand...
Click to collapse
Yes.
sfhub said:
Yes.
Click to expand...
Click to collapse
Thanks, easier than copying these filenames with hashes
Any specific reason that it only works with the 4.3 JSS15R build instead of the 4.3.1 JLS36I build? Is one just the WiFi version?
Craysh said:
Any specific reason that it only works with the 4.3 JSS15R build instead of the 4.3.1 JLS36I build? Is one just the WiFi version?
Click to expand...
Click to collapse
Yes right now there is no update zip for the LTE N7. I will update my site once that zip comes available
I just upgraded. It seems that the ota package doesn't contain the new launcher that the Nexus 5 uses. There is no Google Now home screen as the far left screen and the app drawer still contains a tab for widgets. Is there a separate app to install now from the store?
codahq said:
I just upgraded. It seems that the ota package doesn't contain the new launcher that the Nexus 5 uses. There is no Google Now home screen as the far left screen and the app drawer still contains a tab for widgets. Is there a separate app to install now from the store?
Click to expand...
Click to collapse
Those features are for the N5 only.
Craysh said:
Any specific reason that it only works with the 4.3 JSS15R build instead of the 4.3.1 JLS36I build? Is one just the WiFi version?
Click to expand...
Click to collapse
Yeah it does a signature check of your system files and the ota file, if one does not check out the update won't apply
I get an error when it tries to install the update - something to do with the BasicDreams.apk not being valid (or something along those lines). It then aborts the installation. Not sure if anyone else is running into this problem, or if there's something I can do to fix it. I'm running stock, but rooted, and I've switched back to the standard recovery image from TWRP to try the install.
Thanks!
Thanks man, I've never used the stock recovery before, so had no clue how to get past the broken robot screen. Your video helped a lot!
Does anyone know the way to do this on a Mac?
Question?
Hello,
I can't get the side load to work because it no longer recognizes my nexus 7 when i enter recovery mode? is there a quick fix for this?
im rooted,using cuatom.kernel and recovery
if i flash the stock kernel and recovery and do what u did on the video,will i lose root or lose any data??
Sent from my Nexus 7 using xda app-developers app
Ignore plz
Sent from my Nexus 7 using xda app-developers app
Just as a note, adb sideload method works with twrp installed. Same steps as the guide but the sideload option is located under the advanced tab.
Sent from my Nexus 7 using XDA Premium 4 mobile app
konradsa said:
Watch the video, the answer is right there.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks!! :good:
Sorry goober, I answered to the wrong post by accident. I intended to answer to the guy asking about the recovery mode.
But I think the Mac procedure should be pretty similar, the archive download from Google contains the same tools for Mac. Just not sure how driver installer works on Mac.
Sent from my Nexus 7 using xda app-developers app
Still not having any luck. I can sideload the file onto the tablet fine, but when it gets to the "Verifying current system" stage I get an error saying:
"/system/app/BasicDreams.apk" has unexpected contents
E:Error in /tmp/update.zip
(Status 7)
Installation aborted
I've tried this several times and keep getting the same result. I'm rooted, but running the stock kernel and rom, and using the stock recovery. Any help on this would be greatly appreciated.
Will this work on a stock rooted N7?