[Q] JWR66V -> JWR66Y OTA, debuggerd is buggered - Nexus 7 Q&A, Help & Troubleshooting

[Q] JWR66V -> JWR66Y OTA, debuggerd is buggered - Nexus 7 Q&A, Help & Troubleshooting

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-

Related

New update For July 2010

Do not install the new update, if you have or can get the link to it please provide it so we can take it apart. If you did install it, please try the root trick and let us know if it works.

Re: URL for OTA
8e3b63f96149.OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
I couldn't get any of the URL's to work...
android.clients.google.com/updates/partner/8e3b63f96149.OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
and
android.clients.google.com/updates/partner/OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
they both didn't work

tbonepitt said:
8e3b63f96149.OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
I couldn't get any of the URL's to work...
android.clients.google.com/updates/partner/8e3b63f96149.OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
and
android.clients.google.com/updates/partner/OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
they both didn't work
Click to expand...
Click to collapse
I wonder if google is checking the user agent? Or if not that, maybe just making sure the IP is coming from Verizon. Remember someone noted this will not work over WIFI, so I would try the URLs within the Eris's browser with wifi off if that is the case.
If you're using your home internet connection, it won't show up to google as Verizon wireless.

I just tried the URL's using 3G --- that didn't work either.

tbonepitt said:
I just tried the URL's using 3G --- that didn't work either.
Click to expand...
Click to collapse
Well damn.
Ok I wonder if they are caching the zip on your sdcard. You could try running the freeware program called "Recuva" on it which will recover deleted files and see if the file is still there.
http://en.wikipedia.org/wiki/Recuva

I tried installing the update but there was some type of error in the recovery menu or something. These are the stats I have now
Software Information:
Firmware version
2.1
Baseband version
2.42.00.01.22
Kernal version
2.6.29
[email protected] #46
Build number
2.36.605.1 jcase release-keys
Software number
2.36.605.1
Browser version
WebKit 3.1
PRI version
2.11_002
PRL version
51866
ERI version
3

bugger561 said:
Kernal version
2.6.29
[email protected] #46
Build number
2.36.605.1 jcase release-keys
Click to expand...
Click to collapse
Probably explains it right there.

Software Info
Firmware 2.1
Baseband version 2.42.01.04.27
Kernel version 2.6.29-8a03cb9a [email protected] #1
Build Number 2.37.605.4 CL185970 release-keys
Software number 2.37.605.4

bugger561 said:
I tried installing the update but there was some type of error in the recovery menu or something.
Click to expand...
Click to collapse
Is it still in your cache?

Here is a link that will work.
"https://android.clients.google.com/packages/desirec/OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip"
I can't post an actual link being a new user.

gr8grumpy said:
Here is a link that will work.
https://android.clients.google.com/packages/desirec/OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
I can't post an actual link being a new user.
Click to expand...
Click to collapse
That works! Thank you!

im pretty sure this is something i as a rooted user do not want to do however, are there any major bugfixes in this update?

Here's what it contains:
Code:
boot.img
radio.img
recovery.img
META-INF
META-INF/MANIFEST.MF
META-INF/CERT.SF
META-INF/com
META-INF/com/google
META-INF/com/google/android
META-INF/com/google/android/updater-script
META-INF/com/google/android/update-binary
META-INF/CERT.RSA
patch
patch/system
patch/system/framework
patch/system/framework/android.policy.jar.p
patch/system/framework/com.htc.android.easopen.jar.p
patch/system/framework/bmgr.jar.p
patch/system/framework/com.htc.android.pimlib.odex.p
patch/system/framework/svc.odex.p
patch/system/framework/android.test.runner.odex.p
patch/system/framework/core.jar.p
patch/system/framework/services.jar.p
patch/system/framework/ext.jar.p
patch/system/framework/com.scalado.util.ScaladoUtil.odex.p
patch/system/framework/svc.jar.p
patch/system/framework/com.htc.resources.apk.p
patch/system/framework/monkey.jar.p
patch/system/framework/pm.jar.p
patch/system/framework/com.google.android.maps.odex.p
patch/system/framework/com.scalado.util.ScaladoUtil.jar.p
patch/system/framework/input.jar.p
patch/system/framework/framework.odex.p
patch/system/framework/com.htc.android.pimlib.jar.p
patch/system/framework/framework.jar.p
patch/system/framework/framework-tests.odex.p
patch/system/framework/javax.obex.jar.p
patch/system/framework/framework-tests.jar.p
patch/system/framework/javax.obex.odex.p
patch/system/framework/com.htc.framework.odex.p
patch/system/framework/com.htc.android.easopen.odex.p
patch/system/framework/am.jar.p
patch/system/framework/android.test.runner.jar.p
patch/system/framework/android.policy.odex.p
patch/system/framework/input.odex.p
patch/system/framework/services.odex.p
patch/system/framework/pm.odex.p
patch/system/framework/ime.jar.p
patch/system/framework/ext.odex.p
patch/system/framework/ime.odex.p
patch/system/framework/bmgr.odex.p
patch/system/framework/core.odex.p
patch/system/framework/com.google.android.gtalkservice.odex.p
patch/system/framework/monkey.odex.p
patch/system/framework/com.htc.resources.odex.p
patch/system/framework/am.odex.p
patch/system/framework/com.htc.framework.jar.p
patch/system/lib
patch/system/lib/libt9.so.p
patch/system/lib/libandroid_runtime.so.p
patch/system/xbin
patch/system/xbin/crasher.p
patch/system/build.prop.p
patch/system/app
patch/system/app/HtcSettingsProvider.odex.p
patch/system/app/CustomizationSetup.apk.p
patch/system/app/DCSUtility.odex.p
patch/system/app/AccountAndSyncSettings.odex.p
patch/system/app/DrmProvider.odex.p
patch/system/app/HtcContacts.odex.p
patch/system/app/PackageInstaller.odex.p
patch/system/app/Weather.odex.p
patch/system/app/FlashLitePlugin.odex.p
patch/system/app/HtcDialer.odex.p
patch/system/app/HtcAddProgramWidget.odex.p
patch/system/app/AccountSyncManager.odex.p
patch/system/app/htcmsgwidgets.odex.p
patch/system/app/DCSWeather.odex.p
patch/system/app/DownloadProvider.odex.p
patch/system/app/com.htc.TwitterWidget.apk.p
patch/system/app/com.htc.StockWidget.odex.p
patch/system/app/Settings.apk.p
patch/system/app/PicoTts.odex.p
patch/system/app/HtcFootprints.odex.p
patch/system/app/Browser.odex.p
patch/system/app/htcbookmarkwidget.odex.p
patch/system/app/HtcDialer.apk.p
patch/system/app/FilePicker.odex.p
patch/system/app/HtcAddProgramWidget.apk.p
patch/system/app/CheckinProvider.odex.p
patch/system/app/Stock.odex.p
patch/system/app/Clicker.odex.p
patch/system/app/HTC_IME.apk.p
patch/system/app/Calculator.odex.p
patch/system/app/HtcFacebook.apk.p
patch/system/app/com.htc.WeatherWidget.apk.p
patch/system/app/HtcPhotoWidget.odex.p
patch/system/app/HtcFacebook.odex.p
patch/system/app/HtcPPST.odex.p
patch/system/app/VoiceDialer.odex.p
patch/system/app/HtcLockScreen.apk.p
patch/system/app/TelephonyProvider.odex.p
patch/system/app/HtcStreamPlayer.odex.p
patch/system/app/HtcTwitter.apk.p
patch/system/app/HtcContacts.apk.p
patch/system/app/PDFViewer.odex.p
patch/system/app/HTCSetupWizard.odex.p
patch/system/app/com.htc.MusicWidget.odex.p
patch/system/app/PCSCII.apk.p
patch/system/app/TtsService.odex.p
patch/system/app/htccalendarwidgets.odex.p
patch/system/app/FieldTrial.odex.p
patch/system/app/Settings.odex.p
patch/system/app/WeatherSyncProvider.odex.p
patch/system/app/HtcRingtoneTrimmer.odex.p
patch/system/app/CalendarProvider.odex.p
patch/system/app/HtcSoundRecorder.apk.p
patch/system/app/HTCCamera.apk.p
patch/system/app/SecretControlModem.odex.p
patch/system/app/Calendar.apk.p
patch/system/app/HTCNew.odex.p
patch/system/app/Launcher.odex.p
patch/system/app/Mms.apk.p
patch/system/app/DCSStock.odex.p
patch/system/app/Browser.apk.p
patch/system/app/HtcFootprintsWidget.odex.p
patch/system/app/UploadProvider.apk.p
patch/system/app/restartapp.odex.p
patch/system/app/CustomizationSetup.odex.p
patch/system/app/PCSCII.odex.p
patch/system/app/HTCSetupWizard.apk.p
patch/system/app/com.htc.WeatherWidget.odex.p
patch/system/app/WeatherProvider.odex.p
patch/system/app/UserDictionaryProvider.odex.p
patch/system/app/CertInstaller.odex.p
patch/system/app/Mms.odex.p
patch/system/app/ApplicationsProvider.odex.p
patch/system/app/DMPortRead.odex.p
patch/system/app/HtcSoundRecorder.odex.p
patch/system/app/WorldClock.odex.p
patch/system/app/MediaProvider.apk.p
patch/system/app/HTCAlbum.apk.p
patch/system/app/WorldClock.apk.p
patch/system/app/VpnServices.odex.p
patch/system/app/WeatherProvider.apk.p
patch/system/app/com.htc.TwitterWidget.odex.p
patch/system/app/Stock.apk.p
patch/system/app/htccontactwidgets.apk.p
patch/system/app/teeter.odex.p
patch/system/app/HtcLockScreen.odex.p
patch/system/app/Calendar.odex.p
patch/system/app/Flickr.odex.p
patch/system/app/Rosie.apk.p
patch/system/app/SocialNetworkProvider.odex.p
patch/system/app/FlashPlayer.odex.p
patch/system/app/Bluetooth.odex.p
patch/system/app/HtcWeatherWallpaper.odex.p
patch/system/app/HTMLViewer.odex.p
patch/system/app/HtcMusic.odex.p
patch/system/app/Rosie.odex.p
patch/system/app/WidgetDownloadManager.apk.p
patch/system/app/GoogleSearch.odex.p
patch/system/app/SettingsProvider.odex.p
patch/system/app/HtcLocationService.odex.p
patch/system/app/HTCCamera.odex.p
patch/system/app/HtcSyncwidget.odex.p
patch/system/app/Flickr.apk.p
patch/system/app/htcsearchwidgets.odex.p
patch/system/app/HtcClockWidget.odex.p
patch/system/app/HTC_IME.odex.p
patch/system/app/HtcNaviPanel.odex.p
patch/system/app/EPST.odex.p
patch/system/app/Mail.odex.p
patch/system/app/ContactsProvider.odex.p
patch/system/app/MediaProvider.odex.p
patch/system/app/UploadProvider.odex.p
patch/system/app/GSD.odex.p
patch/system/app/HtcMusic.apk.p
patch/system/app/Bluetooth.apk.p
patch/system/app/HtcTwitter.odex.p
patch/system/app/Phone.odex.p
patch/system/app/htcsettingwidgets.odex.p
patch/system/app/GlobalSearch.odex.p
patch/system/app/HtcLocationPicker.odex.p
patch/system/app/Mail.apk.p
patch/system/app/htcmailwidgets.odex.p
patch/system/app/WeatherAgentService.odex.p
patch/system/app/ContactsProvider.apk.p
patch/system/app/WidgetDownloadManager.odex.p
patch/system/app/CustomizationSettingsProvider.odex.p
patch/system/app/DCSImpl.odex.p
patch/system/app/Weather.apk.p
patch/system/app/htccontactwidgets.odex.p
patch/system/app/HTCAlbum.odex.p
patch/system/etc
patch/system/etc/security
patch/system/etc/security/otacerts.zip.p
patch/system/bin
patch/system/bin/btipsd.p
patch/system/bin/debuggerd.p

This is the only thing in the patch script that makes me nervous.
Code:
assert(package_extract_file("recovery.img", "/tmp/recovery.img"),
write_raw_image("/tmp/recovery.img", "recovery"),
delete("/tmp/recovery.img"));
show_progress(0.016179, 1);
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
show_progress(0.016179, 1);
write_firmware_image("PACKAGE:radio.img", "radio");

I tried flashing on PlainJane which is the OTA update with a few changes and well it didn't work( On RA I modified the update script so it wouldn't flash recovery,boot,or radio and signed it give me an error and on the first assert). So I flashed the recovery that came with the update to see if it was the RA recovery giving problems and then tried to flash the OTA as is and still got the same error, so You probably have to be on a true no root, no nothing OTA for it to work. If anyone is willing to do it let me know so i can incorporate this OTA into PlainJane.

The radio should be safe. It's the other I'm worried about.
Sent from my Eris using XDA App

Stonent said:
The radio should be safe. It's the other I'm worried about.
Sent from my Eris using XDA App
Click to expand...
Click to collapse
I wouldn't be to sure they can lock the nand with the radio if they wanted, doubt they would do it thought. but if you have 1.49200 the engineering hboot you're good because you can flash anything with that.

"OTA 2.1plus" 2010-07-17 System Image
Here is the fully patched /system partition image (yaffs2 format) for those of you that want to start using the patched files.
http://www.megaupload.com/?d=3UBCFTHP
(see below for MD5 and file size)
This system image was created by running the 2010-07-17 "OTA2.1plus" OTA update against a FR'ed Leak-V3 ROM on the Eris
1) Start with a rooted Eris w/ 1.49.2000 S-OFF bootloader and Amon_RA
2) Wipe /system and /data
3) Install (via unyaffs or flash_image) system.img, userdata.img, boot.img, recovery.img from (unpacked) Leak-V3 PB00IMG.ZIP
4) Boot phone and let it configure itself
5) Move OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip to SD card root folder and rename as "update.zip"
6) Perform FR of Eris
7) Reboot, skip activation calls, shutdown
8) Boot (Vol-Up+End) LV3 Recovery, and perform sdcard:update.zip update
9) Finish update, reboot, skip activation, shutdown
10) Re-install Amon_RA via fastboot
11) Make Nandroid Backup
For disambiguation purposes only, I renamed the resulting system.img file
63a06b50ca291e62a9a7f6c8761a5284 ota21+_system.img (172,675,008 bytes)
I could have culled only the patched files into a zip, which would have reduced the size considerably, but I'm still rebuilding my dev station, and don't have everything I needed set up yet.
bftb0
PS Yes, I suppose I have a new radio on my phone now. Que sera, sera, sera.
PS2 Now you can stop worrying

Well I'm saying I feel safe because I already have that radio. I've had it for a few months. It was extracted from the Sprint Hero.
BFTB0: FR?

Here's an edited update.zip i made. It patches everything and leaves the bootloader and recovery untouched.
http://www.multiupload.com/NUFVZNVDGD
I had to fix permissions on su afterward, but that's fairly easy with adb shell:
mount -o remount,rw -t yaffs2 /dev/mtd/mtd3 /system
chmod 06755 /system/bin/su
I TAKE NO RESPONSIBILITY IF YOUR PHONE GETS HOSED

Update

I received a notification for ota update and it failed, im not sure why is there a way to fix it?
See attachment of error

I suspect you renamed (or deleted) the BrowserProviderProxy apk and odex files to sideload the gnex browser and flash. I had done the same and my OTA failed with the same error. I renamed the browser.apk adding a .bak to the name and renamed my BrowserProviderProxy files back to the .apk and .odex extensions, and restarted. Then I copied the update zip from the /cache folder to the root folder and booted into recovery. Installed the zip in recovery and all was well. I used cwm recovery through Rom Manager and I had installed and run Voodoo OTA Rootkeeper before starting. I chose not to flash a new recovery and yes to trying to keep root after the update process.

Groid said:
I suspect you renamed (or deleted) the BrowserProviderProxy apk and odex files to sideload the gnex browser and flash. I had done the same and my OTA failed with the same error. I renamed the browser.apk adding a .bak to the name and renamed my BrowserProviderProxy files back to the .apk and .odex extensions, and restarted. Then I copied the update zip from the /cache folder to the root folder and booted into recovery. Installed the zip in recovery and all was well. I used cwm recovery through Rom Manager and I had installed and run Voodoo OTA Rootkeeper before starting. I chose not to flash a new recovery and yes to trying to keep root after the update process.
Click to expand...
Click to collapse
Thanks but now I'm getting this error, if someone has stock Gapps from 4.1.1 it would be great if they could send me the link for it ...I think that would help

racer321 said:
Thanks but now I'm getting this error, if someone has stock Gapps from 4.1.1 it would be great if they could send me the link for it ...I think that would help
Click to expand...
Click to collapse
There are 237 assertions in the OTA update... Might be easier to just restore to stock 4.1.1 then update.

comminus said:
There are 237 assertions in the OTA update... Might be easier to just restore to stock 4.1.1 then update.
Click to expand...
Click to collapse
Wouldn't I loose all my data though :/

racer321 said:
Wouldn't I loose all my data though :/
Click to expand...
Click to collapse
Yeah... but you gave me an idea. I took the list of files to be patched from the OTA and made a cwm flashable zip with the 4.1.2 versions of the files, the kernel and bootloader. Since these are complete files, there are no patches which means the only assertions are to make sure it runs on a grouper device.
I've run it a few time myself and it seems to work fine. If you want to be a guinea pig and test it out, send me a PM and I'll send you a link.

Req: file - System/bin/debuggerd

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?

[Q] libril.so prevents OTA update on adb

I used the OTA update from 4.2.2 stock+unlock+root to get to 4.3. Everything goes well until adb update states that libril.so is not the right checksum and tells me no-go.
assert apply_patch_check fails on libril.so.
With that the process gives up.
Is there an easy way to manually put libril.so back? I've never changed the RIL, so im not sure how/why this file is different.

mickrussom said:
I used the OTA update from 4.2.2 stock+unlock+root to get to 4.3. Everything goes well until adb update states that libril.so is not the right checksum and tells me no-go.
assert apply_patch_check fails on libril.so.
With that the process gives up.
Is there an easy way to manually put libril.so back? I've never changed the RIL, so im not sure how/why this file is different.
Click to expand...
Click to collapse
I think I fixed it. The libril files were not original, so I downloaded a stock image, extracted the system.img file, changed it from sparse to raw, mounted it ext4, and put the originals on /system/lib. Working so far.

mickrussom said:
I think I fixed it. The libril files were not original, so I downloaded a stock image, extracted the system.img file, changed it from sparse to raw, mounted it ext4, and put the originals on /system/lib. Working so far.
Click to expand...
Click to collapse
Hi, I'm getting the same error message like you. Unfortunately I don't have access to a PC in these days so extracting the necessary file by myself is a bit difficult.
Would you please be so kind and send me the file you extracted in order that i can just simply push it into system with root explorer?
Thank you so much
Sent from my Nexus 7 using Tapatalk 2

[Q] Error Status 7 When Applying JWR66Y Update

I am having an issue applying the JWR66Y update to my nexus 7. I get the following when applying in sideload
assert failed: apply_patch_check("/system/bin/debuggerd", "d8ee8b6a18f902e8842a0bf706a35f4359ef73d8", "led6fc2f1287d0dccdaa4e50b917c0cd3dfa6a")
Thanks for any help

Bumped to keep on main page

Check your private messages.

Groid said:
Check your private messages.
Click to expand...
Click to collapse
I'm having the same problem, and I had to register to ask you to please share
Same hash values in the updater script.
EDIT: I have fixed it myself. I figured out how to use simg2img to unzip and mount the system.img from the factory image download, and from that I was able to grab the original file. Update successful!

Guys this is all well and good, but would it be possible to give a bit more info on how to fix the issue? Pretty please?

I don't have enough post's, so cant post a link.
Search for member AndDiSa and go to his blog, which has a link in his sig.
He has instructions to for extracting a factory image and installing with fastboot.
Has worked for me on the last two updates.

Or just Google for debuggerd, Nexus 7, android 4.3 and xda; there's a thread somewhere here where someone posted a copy. It's how I fixed mine when I upgraded.
Just download it and copy it to /system/bin. Easiest if you can do it in recovery, as Chainfire used that file for some of his software hacks for either Super SU or Stickmount and unfortunately it can get copied over again on boot or reboot.
Sent from my GT-N5110 using Tapatalk 2

Database Users

welcome