Related
I rooted my TPT with the yet another root exploit method while on version 0089_US, and it worked great. Then I installed RootKeeper and temporarilly unrooted. My TPT is not and never has been modified in any other way, no CWR, no apps deleted, nothing.
When I try to install the OTA ICS update, it will start to install, and then fail with some kind of assert failed error message that mentiones busybox, and then say error in /cache/update.zip.
Anybody know what's going on???
I had the same issues with the ROW update. I followed this thread (thoroughly) and got ICS with root intact.
http://forum.xda-developers.com/showthread.php?t=1723048
I'm confused. The fix was:
"Restored busybox from the same file mentioned before and it worked."
How do I "restore" busybox?
userno69 said:
I'm confused. The fix was:
"Restored busybox from the same file mentioned before and it worked."
How do I "restore" busybox?
Click to expand...
Click to collapse
Here's what I needed to do to get busybox restored and access to my stock recovery again:
1. Downloaded a previous update from Lenovo's site. (had to go two versions prior to find one with a busybox file in it).
2. Extract the Busybox file from the archive (system/xbin Directory)
3. Copy the file to your tablet
4. Using ES File Explorer or Astro, copy this Busybox over to the system/xbin Directory on your device. Note: I had trouble here with permissions that came down to a few settings in ES File Explorer (system access, write permissions, etc).
5. Reboot into recovery by pushing Vol + a few times after Lenovo appears.
Hope this helps.
-A
Both ES File Explorer and File Manager fail when attempting to overwrite the existing busybox.
Any suggestions?
garypen said:
Both ES File Explorer and File Manager fail when attempting to overwrite the existing busybox.
Any suggestions?
Click to expand...
Click to collapse
Can you verify your ES file explorer root settings (Root Explorer and Mount file system enabled). These settings are required to make changes to system files.
EpsilonTheGreat said:
Can you verify your ES file explorer root settings (Root Explorer and Mount file system enabled).These settings are requibe able to overwrite busybox.
Click to expand...
Click to collapse
Thanks! That enabled me to overwrite busybox. Now, I am crossing my fingers that the OTA update works.
It started downloading directly from the "check for update" page, rather than quickly saying an update was available, and asking to reboot and install, as it had been doing. So, perhaps it checks busybox before even DLing the update.
It's taking a while to DL. I'll post results after the next reboot ad install attempt.
garypen said:
Thanks! That enabled me to overwrite busybox. Now, I am crossing my fingers that the OTA update works.
It started downloading directly from the "check for update" page, rather than quickly saying an update was available, and asking to reboot and install, as it had been doing. So, perhaps it checks busybox before even DLing the update.
It's taking a while to DL. I'll post results after the next reboot ad install attempt.
Click to expand...
Click to collapse
I saw the exact same thing after fixing busybox. Glad it worked for you (so far)!
Worked like a champ. Rocking ICS on my TPT with root.
It's really not a huge diff from HC. But, lots of little things that I had become accustomed to on my ICS phone.
The tpt does seem a little faster now. Play store is working better, too.
I just wish I could replace that stupid Lenovo quick app icon with the android app launcher icon, like on my nexus. Why do they locate the apps icon at the very top corner? Makes no sense.
I've tried all the busyboxes that I can find and still no update. Can someone post a working one?
I used the one from the 0086US update.
I found one, I used the OTA update.zip
http://forum.xda-developers.com/showthread.php?t=1507285 OTA Update.zip A310_02_0039_0086_US
Also, I kept root.
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:4.0.3/ThinkPadTablet _A400_03/0065_0128_US:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:4.0.3/ThinkPadTablet _A400_03/0069_0130_US:user/release-keys")
Error in /tmp/sideload/package.zip
Summonabeeeetch!!!! I noticed its the first step of the script... any ideas? Anyone? Maybe Ian not destined for ics :-( any ideas?
daswahnsinn said:
I found one, I used the OTA update.zip
http://forum.xda-developers.com/showthread.php?t=1507285 OTA Update.zip A310_02_0039_0086_US
Click to expand...
Click to collapse
You can get it directly from Lenovo:
http://download.lenovo.com/slates/think/tablet1/ThinkPadTablet_A310_02_0039_0086_US.zip
Busybox is located in the system/xbin folder.
garypen said:
You can get it directly from Lenovo:
http://download.lenovo.com/slates/think/tablet1/ThinkPadTablet_A310_02_0039_0086_US.zip
It's located in the system/xbin folder
Click to expand...
Click to collapse
For some strange reason I couldn't get any of the ones from the lenovo site to work, Thank though this should help someone else for sure.
I was able to update to ICS with CW by editing the updater-script. I commented out the verification check.
ScotchtapeLoser said:
I was able to update to ICS with CW by editing the updater-script. I commented out the verification check.
Click to expand...
Click to collapse
Which ones did you comment out?
Your Tablet may vary....
I started with
Build.prop
Gmail
Anything starting with Google...
MarketUpdater
MediaProvider
Mediauploader
NetworkLocation
I would comment out the line, add the new updater-script to the zip file. Try it. When it threw out an error I would comment out that line... rinse and repeat
After a time I just became annoyed and comment out all of the apply_patch_check (around 450 lines). I do not advise using this shotgun approach.
bigsnack said:
Which ones did you comment out?
Click to expand...
Click to collapse
ICS OTA install busybox error
Hey guys I didn't want to start another thread because this one is very similar to the issue I am having now. My tablet asks me to install an OTA update but once its about half way done in recovery in spits out some kind of error(check attachment). When it comes to tablets Im a noob but I was wondering if you guys can give me some solid instructions on how to get past it?
Thanks in advance.
Reference this thread:
http://www.thinkpadtabletforums.com...ds-and-development/ics-ota-failing-w-busybox/
Right, so, through a bit of trial and error using guidance from the forums, this is how I updated to JB and kept root for WW after the update originally failed.
download BOTH files from here (massive thanks to ch3mn3y):
http://www25.zippyshare.com/v/91334594/file.html
http://www1.zippyshare.com/v/96461494/file.html
then extract the .zip file.
download the command file from here (massive thanks to krabappel2548):
http://www.mediafire.com/?yq1bt16mnm7tc8d
extract it.
place the dlpkgfile and command file, both unzipped onto your tab. Use a root explorer to paste the command file into /cache/recovery and the dlpkgfile (the actual file, not the folder) to /cache.
go to Voodoo OTA Rootkeeper and temp unroot.
turn off the tab.
boot into recovery with Vol - and power, then when it says to press volume up to boot into RCK, do it.
You'll see the android with the blue wires and it will go through the install process if you have done it right. let it do its thing.
obviously, when it has settled, restore root with Voodoo.
If you get the android with red exclamation mark, i reccomend downloading the ICS zip of your current firmware and SKU and sticking it on a micro SD card, and letting it restore any programmes you've deleted.
rickykemp said:
Right, so, through a bit of trial and error using guidance from the forums, this is how I updated to JB and kept root for WW after the update originally failed.
download BOTH files from here (massive thanks to ch3mn3y):
http://www25.zippyshare.com/v/91334594/file.html
http://www1.zippyshare.com/v/96461494/file.html
then extract the .zip file.
download the command file from here (massive thanks to krabappel2548):
http://www.mediafire.com/?yq1bt16mnm7tc8d
extract it.
place the dlpkgfile and command file, both unzipped onto your tab. Use a root explorer to paste the command file into /cache/recovery and the dlpkgfile (the actual file, not the folder) to /cache.
go to Voodoo OTA Rootkeeper and temp unroot.
turn off the tab.
boot into recovery with Vol - and power, then when it says to press volume up to boot into RCK, do it.
You'll see the android with the blue wires and it will go through the install process if you have done it right. let it do its thing.
obviously, when it has settled, restore root with Voodoo.
If you get the android with red exclamation mark, i reccomend downloading the ICS zip of your current firmware and SKU and sticking it on a micro SD card, and letting it restore any programmes you've deleted.
Click to expand...
Click to collapse
Will your last line lose root on us, or will voodoo root keeper save it via that or does it wipe/reset the entire system?
Ashcunak said:
Will your last line lose root on us, or will voodoo root keeper save it via that or does it wipe/reset the entire system?
Click to expand...
Click to collapse
When i ran ran the zip of .30 i did lose root, but it was easily restored using 1 click transformer root.
I tried it twice but it always failed at about 1/3 of the process... Hopefully I can reboot w/ any damage...
WHY!?? :'(
Btw here's the part of the log where it shows the failure in installation:
I:Enable RSA key verification.
Installing update...
Finding update package...
I:Update location: /cache/dlpkgfile
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1682 bytes; signature 1664 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Check : blob size = 13104069
Verifying current system...
file "/system/lib/libGLESv1_CM.so" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/lib/libGLESv1_CM.so", "ed4c7834196831836c73d0374529a0278c2fa91c", "a52756f5a63c9827632587d025ee28f67739bd97")
assert failed: apply_patch_check("/system/lib/libGLESv1_CM.so", "ed4c7834196831836c73d0374529a0278c2fa91c", "a52756f5a63c9827632587d025ee28f67739bd97")
E:Error in /cache/dlpkgfile
(Status 7)
Installation aborted.
I:result_code: 410
Check and format /storage to vfat if needed...
Mount /btmac successfully
Done
Btw the command file is just a file with content --update_package=/cache/dlpkgfile in it.
You can create it with notepad, save as .txt, and remove the .txt
rickykemp said:
When i ran ran the zip of .30 i did lose root, but it was easily restored using 1 click transformer root.
Click to expand...
Click to collapse
OH, wow, im so outa date thanks, i rooted on the first revision that came out and havent really watched whats out there for root options. i see this now thanks so much i was worried id have to all sorts of downgrading. link for anyone else whos "outa it" like me http://forum.xda-developers.com/showthread.php?p=26918790
WIIstpM said:
file "/system/app/Music2.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/app/Music2.apk", "c9bc168a88b5106e0e04f8e70023a4c33009021b", "cbb199983ab1cb9beee6b20ec4db659ccd49d757")
assert failed: apply_patch_check("/system/app/Music2.apk", "c9bc168a88b5106e0e04f8e70023a4c33009021b", "cbb199983ab1cb9beee6b20ec4db659ccd49d757")
Click to expand...
Click to collapse
Maybe u delete or freeze Music2.apk? First time when i forget to unfreeze /system apps my update failed too (but i dont remember when).
ch3mn3y said:
Maybe u delete or freeze Music2.apk? First time when i forget to unfreeze /system apps my update failed too (but i dont remember when).
Click to expand...
Click to collapse
I think I found the problem: I remember I pushed jelly bean's music2.apk in system/app! Restored the original music app.
Gonna try update again!
Now it the turn of libGLESv1_CM.so ...
Going to give it a try.
Just to make sure, is this for WW version, right?
ch3mn3y said:
Maybe u delete or freeze Music2.apk? First time when i forget to unfreeze /system apps my update failed too (but i dont remember when).
Click to expand...
Click to collapse
MM the Music app problem is resolved.. but now the same thing happens but with "/system/lib/libGLESv1_CM.so"
...
Tequila.CZ said:
Going to give it a try.
Just to make sure, is this for WW version, right?
Click to expand...
Click to collapse
Yep.
Thanks.
Looking good., but got this error:
file "/system/app/EmailWidget.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/app/EmailWidget.apk", "5655101db862ccc0b2e60bd8ee276192f80e0ac7", "25adaa94e23e2aa87a7dd7f01956ccbabbb960fc")
assert failed: apply_patch_check("/system/app/EmailWidget.apk", "5655101db862ccc0b2e60bd8ee276192f80e0ac7", "25adaa94e23e2aa87a7dd7f01956ccbabbb960fc")
E:Error in /cache/dlpkgfile
Already got this before my update notification stopped working.
I deleted Email app, returned it back to system but seems I dont have the right version. (found in someones dropbox posted here)
Also reflashed Ww. 30 hoping this would overwrite the widget with correct version. Obviously it did not...
Would be glad for any help.
As it is MY dlpkgfile it can need MY files. I could upload /system, but first its strange to copy/paste whole android and second it is 624mb and third it will work only for rooted and at least fourth i updated my pad.
If it helps my pad was reflashed to .30 using wolfs method cos i had screen issue.
Sent using tf300t - stock JellyBean (rooted)
ch3mn3y said:
As it is MY dlpkgfile it can need MY files. I could upload /system, but first its strange to copy/paste whole android and second it is 624mb and third it will work only for rooted and at least fourth i updated my pad.
If it helps my pad was reflashed to .30 using wolfs method cos i had screen issue.
Sent using tf300t - stock JellyBean (rooted)
Click to expand...
Click to collapse
Could you please try to upload just the EmailWidget?
When I tried using OTA I got an error on Email.apk first. Then I downloaded it from dropbox and it passed. But EmailWidget did unfortunately not.
Also trying to find a tool that could extract the .30blob file. I guess the apps should be there. Found something but probably Linux only so no go for me.
You guys made my day! I had the red triangle and couldn`t get the update anymore. Tried everything, nothing worked.
Now I just followed your guide, dl. your files and all went fine.
So sad I was ony able to hit the Tanks-button once. Thank you thousand times!
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Here is emailwidget .apk and .odex but from jb not ics cos i didnt made a backup. But i think that it wasnt changed.
http://db.tt/cYSWYcXo
Sent using tf300t - stock JellyBean (rooted)
ch3mn3y said:
Here is emailwidget .apk and .odex but from jb not ics cos i didnt made a backup. But i think that it wasnt changed.
http://db.tt/cYSWYcXo
Sent using tf300t - stock JellyBean (rooted)
Click to expand...
Click to collapse
Oh man. I love you. Here I come on JB!
The EmailWidget was the missing piece.
Big thanks to rickykem, ch3mn3y and overyone who helped to create this workaround!
y17dt said:
You guys made my day! I had the red triangle and couldn`t get the update anymore. Tried everything, nothing worked.
Now I just followed your guide, dl. your files and all went fine.
So sad I was ony able to hit the Tanks-button once. Thank you thousand times!
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
+1:good:
Can someone post the original /system/lib/libGLESv1_CM.so pleeease...
Sent from my LG-P970 using xda premium
WIIstpM said:
Can someone post the original /system/lib/libGLESv1_CM.so pleeease...
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
I only have it from JB. Unfortunately it seems the file was updated together with the system so it will most probably be useless.
Don't have a libs backup from WW.30
WIIstpM said:
Can someone post the original /system/lib/libGLESv1_CM.so pleeease...
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
Here you go, from ICS:
http://db.tt/z5B5Q3jL
Trimis de pe ASUS Transformer Pad TF300T
Tried updating from 4.2.1 to 4.2.2.
But assert check failed returning above file in results. Somehow it's been modified. No idea when and how.
Anyone running 4.2.1, could you please provide me this file.
Thanks in anticipation.
Sent from my Nexus 7 using Tapatalk HD
gurudev32 said:
Tried updating from 4.2.1 to 4.2.2.
But assert check failed returning above file in results. Somehow it's been modified. No idea when and how.
Anyone running 4.2.1, could you please provide me this file.
Thanks in anticipation.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I have the exact same issue!
Here is the list of only apps with root access in my tab.
Carbon - App backup and restore, Solid explore, Stick mount, SuperSU, System tuner pro and Terminal Emulator.
Thought to seek out the culprit!
Sent from my Nexus 7 using Tapatalk HD
https://dl.dropbox.com/u/17326185/debuggerd
MD5: B59443115C4181F49A57C1290EE3225B
https://dl.dropbox.com/u/17326185/build.prop
MD5: D9D1855E0C90049DC410A4406B802259
Pulled this from the 4.2.1 factory image. I seem to have got past the debuggerd error message now (though I need to revert my build.prop entirely, apparently).
Included build.prop (not yet tested) from 4.2.1 image too.
Working for me and now running 4.2.2.
At your own risk, yadda yadda, not responsible for explosions or anything less terrible, blah blah.
FWIW, I had been using Stickmount and superSU.
PhoenixTank said:
Pulled this from the 4.2.1 factory image. I seem to have got past the debuggerd error message now (though I need to revert my build.prop entirely, apparently).
Included build.prop (not yet tested) from 4.2.1 image too.
Working for me and now running 4.2.2.
At your own risk, yadda yadda, not responsible for explosions or anything less terrible, blah blah.
FWIW, I had been using Stickmount and superSU.
Click to expand...
Click to collapse
Thanks Now 'm on 4.2.2
In the future, If you want to pull arbitrary file(s) from Google N7 factory images, a useful skill set is to figure out how to use "sim2img" utility and loopback mounts (Windows need not apply).
Those system.img files shipped by Google are "sparse ext4 images" - they can not be directly mounted as a loopback, but that's where the "sim2img" utility comes in
The sequence goes like this:
- use sim2img to convert Google image file to regular ext4 image file
- loopback mount reg. image file
- grab whatever files you want (and check user/GRP ownership & modes)
It really is just that easy.
The "sim2img" utility is part of the android ext4_utils toolset. See this XDA thread from the Galaxy S forums for more details. (Yes the N7 system.img files from Google are also in this format.)
cheers
PhoenixTank said:
https://dl.dropbox.com/u/17326185/debuggerd
MD5: B59443115C4181F49A57C1290EE3225B
https://dl.dropbox.com/u/17326185/build.prop
MD5: D9D1855E0C90049DC410A4406B802259
Pulled this from the 4.2.1 factory image. I seem to have got past the debuggerd error message now (though I need to revert my build.prop entirely, apparently).
Included build.prop (not yet tested) from 4.2.1 image too.
Working for me and now running 4.2.2.
At your own risk, yadda yadda, not responsible for explosions or anything less terrible, blah blah.
FWIW, I had been using Stickmount and superSU.
Click to expand...
Click to collapse
How to make it? and i will lose all data? thanks
TheRejzo said:
How to make it? and i will lose all data? thanks
Click to expand...
Click to collapse
Big thanks.
Replacing the debuggerd file allowed twrp to load the 4.2.2 update.
Also interesting, other than titanium, the only other root app on this device is Stickmount.
Did not work for me ...
I have a N7 3G and the same message when trying to update. Replaced mine with the one from the download, no change, same error.
diba320 said:
Did not work for me ...
I have a N7 3G and the same message when trying to update. Replaced mine with the one from the download, no change, same error.
Click to expand...
Click to collapse
First of all, thanks a lot to PhoenixTank who provides me the solution. :good:
In fact to make it work, I had to change the permissions allowed on that file named "debuggerd", I checked what permissions were allowed on the original file and do the same on the copied one. I did it with ES explorer in root mod.
TheRejzo said:
How to make it? and i will lose all data? thanks
Click to expand...
Click to collapse
You'd need to backup and rename the existing debuggerd then move/copy the 4.2.1 debuggerd file to /system/bin/
Then match the permissions of the old debuggerd (I think it was 644, but I wouldn't swear by it).
The OTA zip should actually go through after that, or at least tell you about a new file you need to fix. You shouldn't lose any data, but you should probably clear cache and dalvik cache.
I did most of this via adb shell, but there are root file managers that can help. If you aren't confident about doing this and how it works, my posting was not really for you. Strongly suggest reading up until you feel confident before you start changing things around in the system partition.
diba320 said:
Did not work for me ...
I have a N7 3G and the same message when trying to update. Replaced mine with the one from the download, no change, same error.
Click to expand...
Click to collapse
Unfortunately the 3G version is different to the Wifi Nexus 7, and as you've found, the files will not work.
Since I posted, Google pulled the 4.2.1 factory images from the download site - I'm not really in a good position to help you here.
The 4.2.2 factory image might be of more use if you can't source the 3G specific files. i.e. flash the new factory image.
Had this same problem. Will try solution tomorrow morning. Probably will download the links rather than trying to extract them myself (though I may leave that for a later exercise).
Would like to note that I also use StickMount as well as SixAxis Controller, Wifi Key Recovery, AppSync and LMT Launch err.
Seems like stick mount is the common one though.
Sent from my Nexus 7 using xda app-developers app
PhoenixTank said:
https://dl.dropbox.com/u/17326185/debuggerd
MD5: B59443115C4181F49A57C1290EE3225B
https://dl.dropbox.com/u/17326185/build.prop
MD5: D9D1855E0C90049DC410A4406B802259
Pulled this from the 4.2.1 factory image.
Click to expand...
Click to collapse
bftb0 said:
In the future, If you want to pull arbitrary file(s) from Google N7 factory images, a useful skill set is to figure out how to use "sim2img" utility and loopback mounts (Windows need not apply).
Those system.img files shipped by Google are "sparse ext4 images" - they can not be directly mounted as a loopback, but that's where the "sim2img" utility comes in
The sequence goes like this:
- use sim2img to convert Google image file to regular ext4 image file
- loopback mount reg. image file
- grab whatever files you want (and check user/GRP ownership & modes)
It really is just that easy.
The "sim2img" utility is part of the android ext4_utils toolset. See this XDA thread from the Galaxy S forums for more details. (Yes the N7 system.img files from Google are also in this format.)
cheers
Click to expand...
Click to collapse
Thanks guys
Those 2 files worked.
I got past "Verifying current system" and am now on 4.2.2.
I wanted to try to get the files myself as an exercise but Google pulled the 4.2.1 images from their website.
What is weird... is that I noticed a /system/bin/debuggerd.bak file that I didn't make myself, don't know what did (though StickMount seems to be the current suspect).
The weird thing is that debuggerd and debuggerd.bak were exactly the same.
FunkyELF said:
I wanted to try to get the files myself as an exercise but Google pulled the 4.2.1 images from their website.
Click to expand...
Click to collapse
oldblue910 (OP of the OTA thread) has got you covered. Select the link on the rhs of the page as appropriate for your device (nakasi/nakasig)
cheers
I want to do this, but I can't find the system/bin folder, what root explorer apps do you guys use?
EDIT: Used Total Commander, copied the permissions from old file to new and voilah! It worked.
No need to download build prop.
Now I am on 4.2.2
EDIT 2: Now WiFi only says SAVED and not CONNECTED.
Just want to say THANK YOU!! I've been researching this error since Friday and finally found the solution here! And yes, I too have Stickmount!
Rody2k6 said:
I want to do this, but I can't find the system/bin folder, what root explorer apps do you guys use?
EDIT: Used Total Commander, copied the permissions from old file to new and voilah! It worked.
No need to download build prop.
Now I am on 4.2.2
EDIT 2: Now WiFi only says SAVED and not CONNECTED.
Click to expand...
Click to collapse
Can only recommend that you clear cache and dalvik cache. I have not experienced Wifi issues since the update.
To anyone I've helped, you are very welcome and I appreciate those thanks clicks too.
bftb0 said:
In the future, If you want to pull arbitrary file(s) from Google N7 factory images, a useful skill set is to figure out how to use "sim2img" utility and loopback mounts (Windows need not apply).
Those system.img files shipped by Google are "sparse ext4 images" - they can not be directly mounted as a loopback, but that's where the "sim2img" utility comes in
The sequence goes like this:
- use sim2img to convert Google image file to regular ext4 image file
- loopback mount reg. image file
- grab whatever files you want (and check user/GRP ownership & modes)
It really is just that easy.
The "sim2img" utility is part of the android ext4_utils toolset. See this XDA thread from the Galaxy S forums for more details. (Yes the N7 system.img files from Google are also in this format.)
cheers
Click to expand...
Click to collapse
can i do the reverse ? i.e. ext4 partition back to flashable img ?
that way it would be easier to root as I just need to dump a copy of su into it then flash.
And for Windows, just get oracle virtualbox(or your favorite VM, even virtual PC should work) and boot a copy of debian
chimpanzeexda said:
can i do the reverse ? i.e. ext4 partition back to flashable img ?
that way it would be easier to root as I just need to dump a copy of su into it then flash.
And for Windows, just get oracle virtualbox(or your favorite VM, even virtual PC should work) and boot a copy of debian
Click to expand...
Click to collapse
Yes. I did exactly the same thing, but for 4.2.1. Guess I need to repeat it now for 4.2.2. Note in this case "flashable" means the fastboot way (as with the Factory ROM flashes), not via custom recovery.
Uhh let's see - the script tool used for re-packing is ./mkuserimg.sh - see the links I provided above
I need some help... I'm rather noobie. Had issue with upgrading to 4.2.2 so copied the debuggerd and build.prop files over to the system/bin directory. Still failed to upgrade. Tried it again today and now the N7 will not boot up. I can see it's on but it just stops at a blank screen. I have stock 4.2.1 w/root. Stock bootloader. I'm thinking its refusing to boot because I forgot to change the file permissions on the debuggerd file but not sure how to try and fix it. Please advise...
UPDATE: Managed to flash the system partition for 4.2.2 so hoping I'm good to go. Asked this question in another post but is it necessary to update any of the other partitions?
Getting an assertion failure on /system/bin/debuggerd when trying to load the JWR66Y (stock) OTA update that showed up on my N7 tonight. I don't THINK I've installed anything that changed this file, but who knows. I found a copy called debuggerd_bak in the same directory, but it appears to be the same file.
This is the SHA1 of my current copy:
a2323a0c8e245e3879d6b8beff6b2c4802045271
Is there a different version that I need?
According to some forum searching, Stickmount modifies the file (and I'm not sure if it actually backs it up beforehand).
adammw said:
According to some forum searching, Stickmount modifies the file (and I'm not sure if it actually backs it up beforehand).
Click to expand...
Click to collapse
That's the weird thing about it; I've never installed Stickmount. I do have USB OTG Helper, though. I'm pulling a JWR66V factory image down from Google (had to dig around archive.org to find the link). If I can pull debuggerd out of it, I may be able to get back to a known state.
db2 said:
That's the weird thing about it; I've never installed Stickmount. I do have USB OTG Helper, though. I'm pulling a JWR66V factory image down from Google (had to dig around archive.org to find the link). If I can pull debuggerd out of it, I may be able to get back to a known state.
Click to expand...
Click to collapse
I'm doing the exact same thing as we speak. Good luck.
Got the file, only to find out that I need to restore a whole bunch of other files. I give up for now, but if you have the 3G Nexus 7 (2012), it's attached.
Well I pulled debuggerd out of the factory image, and that seemed to fix the error, but now I get "set_perm: some changes failed" with status 7 when I try to flash the update. Not sure what that means.
Is it possible to reflash just system.img to my current version without wiping data?
If your bootloader is unlocked, you can flash boot.img and system.img using fastboot and you will not loose any data. In my blog you can find a post how to update to 4.3 manually.
There we go. I just fastboot flashed system.img and boot.img, and the JWR66Y patch installed fine after that. Had to re-root and reinstall a couple app updates, but that's no big deal.
db2 said:
There we go. I just fastboot flashed system.img and boot.img, and the JWR66Y patch installed fine after that. Had to re-root and reinstall a couple app updates, but that's no big deal.
Click to expand...
Click to collapse
db2 can you please post the debuggerd file from 4.3. I'm also having this issue trying to flash the security OTA fro 4.3.
I don't know how to get the original debuggerd file from android 4.3.
Thanks
jalize said:
db2 can you please post the debuggerd file from 4.3. I'm also having this issue trying to flash the security OTA fro 4.3.
I don't know how to get the original debuggerd file from android 4.3.
Thanks
Click to expand...
Click to collapse
Sure, here you go. This is for the non-3G first-gen Nexus 7.
db2 said:
There we go. I just fastboot flashed system.img and boot.img, and the JWR66Y patch installed fine after that. Had to re-root and reinstall a couple app updates, but that's no big deal.
Click to expand...
Click to collapse
db2 said:
Sure, here you go. This is for the non-3G first-gen Nexus 7.
Click to expand...
Click to collapse
Thanks db2, but I'm looking for the Nexus 10 one. Sorry I see wrong thread. i do have the debuggerd.p file from the OTA. do you know how to get this to the normal debuggerd file?
jalize said:
Thanks db2, but I'm looking for the Nexus 10 one. Sorry I see wrong thread. i do have the debuggerd.p file from the OTA. do you know how to get this to the normal debuggerd file?
Click to expand...
Click to collapse
The .p is a patch file, which is why you have to have the correct version of the file to start from.
Here's a link to the N10 JWR66V IMAGE:
https://dl.google.com/dl/android/aosp/mantaray-jwr66v-factory-888d124e.tgz
This is the procedure I used to extract debuggerd:
http://forum.xda-developers.com/showthread.php?t=1860879
Wasn't too hard, but I ended up having to reflash system.img and boot.img anyway, because I was getting a weird set_perm error.
db2 said:
The .p is a patch file, which is why you have to have the correct version of the file to start from.
Here's a link to the N10 JWR66V IMAGE:
https://dl.google.com/dl/android/aosp/mantaray-jwr66v-factory-888d124e.tgz
This is the procedure I used to extract debuggerd:
http://forum.xda-developers.com/showthread.php?t=1860879
Wasn't too hard, but I ended up having to reflash system.img and boot.img anyway, because I was getting a weird set_perm error.
Click to expand...
Click to collapse
Thanks db2, will give it a try
It Worked !!!! Thanks again man!
set_perm error
db2 said:
Wasn't too hard, but I ended up having to reflash system.img and boot.img anyway, because I was getting a weird set_perm error.
Click to expand...
Click to collapse
SuperSU?
See HERE for an explanation and fix for this error.
-JR-
I have the Wi-Fi Nexus 7 with StickMount installed, and I just want to say the debuggerd file provided by @db2 in post #10 allowed me to update without problems when I flashed the OTA via TWRP.
Just remember to fix the permissions of the file first when you move it to system/bin.
mlj11 said:
I have the Wi-Fi Nexus 7 with StickMount installed, and I just want to say the debuggerd file provided by @db2 in post #10 allowed me to update without problems when I flashed the OTA via TWRP.
Just remember to fix the permissions of the file first when you move it to system/bin.
Click to expand...
Click to collapse
I confirm that adammw's file (post #5) worked for my 3g Nexust 7 2012. I was trying to update from JWR66V to JWR66Y. It only worked after replacing the latest TWRP with the stock recovery. Installing with TWRP did not work under any conditions: root, no root, manual update file, automatically updated file.
How do I need to fix permissions for debuggerd? I forgot to look on the original permissions and I don't know what are the correct ones.
p.s. I previously removed root, I removed the install-recovery.sh (changed attributes on install-recovery), stock recovery without success.
mindcsrusher said:
I confirm that adammw's file (post #5) worked for my 3g Nexust 7 2012. I was trying to update from JWR66V to JWR66Y. It only worked after replacing the latest TWRP with the stock recovery. Installing with TWRP did not work under any conditions: root, no root, manual update file, automatically updated file.
How do I need to fix permissions for debuggerd? I forgot to look on the original permissions and I don't know what are the correct ones.
p.s. I previously removed root, I removed the install-recovery.sh (changed attributes on install-recovery), stock recovery without success.
Click to expand...
Click to collapse
The update installer script runs a recursive permissions set (chown|chmod) e.g.:
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin"
0 = root
2000 = shell
0755 = -rwxr-xr-x
The above would have set the correct perms on all files in the /system/bin directory (including debuggerd) and any files requiring additional perms would have been set individually with the set_perm command
See my post HERE for more info
HTH,
-JR-
Hi everybody
When the factory images came out, I flash my N4 with the stock factory images that we used to find here : https://developers.google.com/android/nexus/images#occamkrt16s because it is now the KRT16S build
After a few days, when the KRT16S build came out, I was proposed in my phone to update it. I downloaded it, tried to flash it but nothing worked, I'm still on KRT16O and the OTA doesn't appear anymore... Then I remembered that I flashed a mod found here : http://forum.xda-developers.com/showthread.php?t=2527525 (that's a great mod btw) so I guessed that I could reflash the undo file available on the thread, flash the ota file dl mannually (I attached it in this thread) which I did through TWRP. Then I was able to see the problem, it told me that, from what I remember, Agenda.apk was missing (I think it's diary in english, not sure) then I remembered that I manually deleted some apps I never use (diary is one of them...)
So, what's next, shall I reflash the gapps to finally update my phone
Thanks for your help :laugh:
Are you using latest TWR? I did it ok
Sent from my Nokia 3210
howard bamber said:
Are you using latest TWR? I did it ok
Sent from my Nokia 3210
Click to expand...
Click to collapse
I run the 2.6.3.3 version I guess it's the latest because I flashed it a few days ago
I installed the few missing apps that i uninstalled and Calendar didn't create any error. This time it EmailGoogle.apk... I transformed it as a system application and I went to /system/app to change its name from com.google.android.apps.email or something to EmailGoogle.apk, didn't work... But I'm sure I'm on the way to achieve it :victory:
Here's the whole mesage :
Code:
Updating partition details...
Installing '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Checking for MD5 file...
Skipping MD5 check : no MD5 dile found.
Verifying current system...
"/system/app/EmailGoogle.apk" has unexpected contents.
E:Error executing updater binary in zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip
Error flashing zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Updating partition détails...
[CENTER][COLOR="Red"][SIZE="4"]Failed[/SIZE][/COLOR][/CENTER]
azertguigui said:
I run the 2.6.3.3 version I guess it's the latest because I flashed it a few days ago
I installed the few missing apps that i uninstalled and Calendar didn't create any error. This time it EmailGoogle.apk... I transformed it as a system application and I went to /system/app to change its name from com.google.android.apps.email or something to EmailGoogle.apk, didn't work... But I'm sure I'm on the way to achieve it :victory:
Here's the whole mesage :
Code:
Updating partition details...
Installing '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Checking for MD5 file...
Skipping MD5 check : no MD5 dile found.
Verifying current system...
"/system/app/EmailGoogle.apk" has unexpected contents.
E:Error executing updater binary in zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip
Error flashing zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Updating partition détails...
[CENTER][COLOR="Red"][SIZE="4"]Failed[/SIZE][/COLOR][/CENTER]
Click to expand...
Click to collapse
You can not install an apk in recovery. Use ES File Explorer to install the apk. In addition, to avoid the error, while you are in recovery, select "Mount" and uncheck the box "System" when flashing a zip file.
taodan said:
You can not install an apk in recovery. Use ES File Explorer to install the apk. In addition, to avoid the error, while you are in recovery, select "Mount" and uncheck the box "System" when flashing a zip file.
Click to expand...
Click to collapse
I did not installed it with TWRP, I did it by simply openning the apk while my phone is on, it installed the Email app...
But thanks anyway for the mount function, I'll give a try
azertguigui said:
I did not installed it with TWRP, I did it by simply openning the apk while my phone is on, it installed the Email app...
But thanks anyway for the mount function, I'll give a try
Click to expand...
Click to collapse
Simpler way to update without OTA package:
Download the factory image, and before running the flash-all script, open it with a text editor and change "fastboot -w update" to "fastboot update"
MameTozhio said:
Simpler way to update without OTA package:
Download the factory image, and before running the flash-all script, open it with a text editor and change "fastboot -w update" to "fastboot update"
Click to expand...
Click to collapse
You mean with the sdk? I don't know how to use it, when I flash something, it's with the recovery or the nexus root toolkit..
-From my Nexus 4-
UP
azertguigui said:
UP
Click to expand...
Click to collapse
**
azertguigui said:
UP
Click to expand...
Click to collapse
azertguigui said:
**
Click to expand...
Click to collapse
Not sure what you're trying to say here..
azertguigui said:
You mean with the sdk? I don't know how to use it, when I flash something, it's with the recovery or the nexus root toolkit..
-From my Nexus 4-
Click to expand...
Click to collapse
Try avoiding toolkits as they can lead to problems and leave you stuck with no idea what to do. Yes he is referring to the sdk. Only the platform-tools folder in the sdk is required so if you don't wanna bother downloading the complete file, just download the platform-tools from here and extract it to an appropriate location. Extract and move the Factory Image that you downloaded to your platform-tools directory. If you don't want your data to be erased, edit the flash-all script with a text editor and remove -w and save. Plug in your phone. Make sure you have the drivers installed. In the platform tools directory, press shift+right click> open command prompt here. Type adb devices. You will see "device <Serial Number>. If you don't, your drivers are faulty. Then type adb reboot bootloader. Once your phone has rebooted into bootloader, make sure that it is being detected by typing fastboot devices. You should see an output similar to adb devices. Now simply run the flash-all script and let it do its work. Reboot after flashing is completed.
Hope this helps!
try search any youtube on how to flash factory images to your device. I guess u'll find lots.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Words of advice, learn how to use ADB instead of relying solely on toolkits. It's very simple actually.
Now there's a simple way to update which is sideload. Oh and btw to sideload, you still need ADB though (this is why learning ADB is VERY important to us, the N4 users). Here is a video tutorial on how to perform adb sideload. All the links are attached in his youtube video.
Ibrahim.Rahman said:
Not sure what you're trying to say here..
Click to expand...
Click to collapse
:laugh: I quoted my own UP post but it told me that my post should have at least 2 letters, so I taped the spacebar twice and it wrote this
Ibrahim.Rahman said:
Try avoiding toolkits as they can lead to problems and leave you stuck with no idea what to do. Yes he is referring to the sdk. Only the platform-tools folder in the sdk is required so if you don't wanna bother downloading the complete file, just download the platform-tools from here and extract it to an appropriate location. Extract and move the Factory Image that you downloaded to your platform-tools directory. If you don't want your data to be erased, edit the flash-all script with a text editor and remove -w and save. Plug in your phone. Make sure you have the drivers installed. In the platform tools directory, press shift+right click> open command prompt here. Type adb devices. You will see "device <Serial Number>. If you don't, your drivers are faulty. Then type adb reboot bootloader. Once your phone has rebooted into bootloader, make sure that it is being detected by typing fastboot devices. You should see an output similar to adb devices. Now simply run the flash-all script and let it do its work. Reboot after flashing is completed.
Hope this helps!
Click to expand...
Click to collapse
Thanks, I'll give a try
saifulh2304 said:
try search any youtube on how to flash factory images to your device. I guess u'll find lots.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
arffrhn said:
Words of advice, learn how to use ADB instead of relying solely on toolkits. It's very simple actually.
Now there's a simple way to update which is sideload. Oh and btw to sideload, you still need ADB though (this is why learning ADB is VERY important to us, the N4 users). Here is a video tutorial on how to perform adb sideload. All the links are attached in his youtube video.
Click to expand...
Click to collapse
thanks guys, I'm gonna find tutorials on the web like the one you pointed to me
azertguigui said:
:laugh: I quoted my own UP post but it told me that my post should have at least 2 letters, so I taped the spacebar twice and it wrote this
Click to expand...
Click to collapse
Haha right!
Sent from my Nexus 4 using xda app-developers app