Database Users

2.1 OTA Rom - Root Edition - Download

ATTN: My rom is bare basic, if your looking for a more streamlined rom
check out grdlock bluid based on the same source. Link removed because of assholes.
SNIP SNIP Several others released far more indepth and better roms, use them (like grdlock's).
http://www.androlib.com/android.application.com-hookerbots-rpics-twDt.aspx
I don't take donations. If you like my worth, the above app is from my favorite author, support him and of course XDA.

jcase said:
# id
uid=0(root) gid=0(root)
# busybox whoami
whoami: unknown uid 0
# busybox uname -a
Linux localhost 2.6.29-564a4a15 #1 PREEMPT Thu Feb 25 15:56:06 CST 2010 armv6l GNU/Linux
#
Just wanted to put that out there. If not one else puts out a better rom based on OTA tomorrow, I'll release it.
Its just bare OTA with su/superuser.apk.
Click to expand...
Click to collapse
That's exactly what i'm looking for an OTA with su added.
Thanks! can't wait for the upload.

i see you conquered the problem. MAGIC! well done

Thanks jcase! Will be testing tomorrow. Don't forget to rm /system/etc/security/otacerts.zip

flashing now. letting it run overnight should let me know if the stock Messages app bug is fixed. if not, Handcent it is!

So once again... no root for us that went to the 2.1 leak?

LexusBrian400 said:
So once again... no root for us that went to the 2.1 leak?
Click to expand...
Click to collapse
Nope. In order to flash a new rom without root, the HTC signature needs to be valid. In order to preserve root, the rom was modified by jcase to include su which breaks the signature hash. So, while you will be able to update to the official OTA update (assuming version is higher, which I believe to be the case), you can't install this rom.
Since most people will be updating to the OTA 2.1 away from the leak or away from 1.5, I'd personally recommend installing the OTA 2.1 directly from HTC. We'll likely be targeting it for root exploits next and abandoning version 1.5.

hoban_eris said:
Since most people will be updating to the OTA 2.1 away from the leak or away from 1.5, I'd personally recommend installing the OTA 2.1 directly from HTC. We'll likely be targeting it for root exploits next and abandoning version 1.5.
Click to expand...
Click to collapse
To be clear, install the otaroot rom released by jcase if you already have root. Install the OTA rom direct from HTC if you currently have the leaked 2.1.

hoban_eris said:
Nope. In order to flash a new rom without root, the HTC signature needs to be valid. In order to preserve root, the rom was modified by jcase to include su which breaks the signature hash. So, while you will be able to update to the official OTA update (assuming version is higher, which I believe to be the case), you can't install this rom.
Since most people will be updating to the OTA 2.1 away from the leak or away from 1.5, I'd personally recommend installing the OTA 2.1 directly from HTC. We'll likely be targeting it for root exploits next and abandoning version 1.5.
Click to expand...
Click to collapse
Thanks for the clarification. I really appreciate it. Can't wait for OTA root
The new 2.1 is exactly what I wished the last leaked 2.1 would have been. Its working so much better with no noticeable lag at all.
Thanks again guys!

wipe data
I have root now and am currently running the .3 rom, question
1. is this just an update to what i am running now?
2. Do i need to preform a wipe?
3. if i dont wipe does the phone maintain all my apps and settings i.e email google etc?

Damn, I was just uploading my all-in-one batch script and then I noticed this had been released... I started making a rom of it, then I noticed you already did! hah!
Thanks for being a night owl and already doin the work jcase. I'm gonna incorporate this into the all-in-one script.

mv error: cross-device link
i have updated this rom, works great!
bu i can't mv from /system/app to /sdcard
error message is "cross-device link"
but i had already remount the /system partion as rw, and i notice that rm is working fine - i can remove files in /system/app, but can't move to another directory!
before update to this rom, mv is working correct
any advice?
btw, there is no busybox in this rom

liushk said:
i have updated this rom, works great!
bu i can't mv from /system/app to /sdcard
error message is "cross-device link"
but i had already remount the /system partion as rw, and i notice that rm is working fine - i can remove files in /system/app, but can't move to another directory!
before update to this rom, mv is working correct
any advice?
btw, there is no busybox in this rom
Click to expand...
Click to collapse
same problem here. you can copy files and then remove the source. that's what I've been doing for my moves. As for busybox, I installed it myself, but I'm sure someone (if not me) will release an update.zip to install it sooner rather than later.

hoban_eris said:
same problem here. you can copy files and then remove the source. that's what I've been doing for my moves. As for busybox, I installed it myself, but I'm sure someone (if not me) will release an update.zip to install it sooner rather than later.
Click to expand...
Click to collapse
thanks for reply
I tried install busybox myself, but it dosn't work. this is my steps:
adb push busybox /sdcard/
adb shell
remount /system
mv /sdcard/busybox /system/xbin
failed
adb shell
remount /system
switch to another console
adb push busybox /system/xbin
failed
and, there is no "cp" command, I didn't find another way to copy from /system/app to /sdcard/

Wipe??
I just want to reiterate denonlake's question, does installing rooted OTA 2.1 require a wipe of DATA and CACHE partitions like the original root process? Can we preserve settings through this flash or is it best to go through the whole setup process again?

The mv and cp commands are in busybox. I did not install busybox, so you don't have them. The Toolbox that comes with the OTA is lacking them.
Install busybox yourself, or wait for grdlock or ivan's release.

in case anyone is interested, the Messages app bug and cell standby bugs are fixed in this release too (as well as the already known gmail login bug fix) the phone also seems to power down a lot faster than previous leaks.
havent tested google voice yet, probably cant till later today. someone else feel free..

shickfaced said:
I just want to reiterate denonlake's question, does installing rooted OTA 2.1 require a wipe of DATA and CACHE partitions like the original root process? Can we preserve settings through this flash or is it best to go through the whole setup process again?
Click to expand...
Click to collapse
I first tried installing from zip through recovery.
This did not appear* to work.
Next, wiped device and cache, then installed zip through recovery.
Success!
*My experience is limited. Maybe it did work, but nothing on the phone appeared changed.

Ok so this is just a rooted version of the Official OTA 2.1 right??? Nothing else has been done to it??

rustyman14 said:
Ok so this is just a rooted version of the Official OTA 2.1 right??? Nothing else has been done to it??
Click to expand...
Click to collapse
All this info is in the first post... X_X
jcase said:
This is the 2.1 OTA Rom with su, a modified sh, SuperUser.apk and spare_parts.apk added (root). Thats it, nothing else modified.
Click to expand...
Click to collapse

[ROM DUMP] Viewsonic Stock 3389

Anyone able to post a system dump of a GTablet that is stock with the latest OTA applied? I want to look at the stock framework and see about creating my own custom ROM - I am coming from the Android phone dev environment and would love to start putting together a custom ROM and/or themes
Thanks in advance.

jerdog said:
Anyone able to post a system dump of a GTablet that is stock with the latest OTA applied? I want to look at the stock framework and see about creating my own custom ROM - I am coming from the Android phone dev environment and would love to start putting together a custom ROM and/or themes
Thanks in advance.
Click to expand...
Click to collapse
Download here: http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3389-user.zip
Unpack system.img with unyaffs, a binary exists for both windows and linux on the web.
Might have to run as admin in windows: unyaffs.exe system.img
Linux: chmod +x unyaffs
./unyaffs system.img

rothnic said:
Download here: http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3389-user.zip
Unpack system.img with unyaffs, a binary exists for both windows and linux on the web.
Might have to run as admin in windows: unyaffs.exe system.img
Linux: chmod +x unyaffs
./unyaffs system.img
Click to expand...
Click to collapse
Thanks! It's what I needed. wasn't sure if that update was one that completely started over or just patched what existed.

Their updates are complete system.img wipes, so 3389 is a good starting point.

roebeet said:
Their updates are complete system.img wipes, so 3389 is a good starting point.
Click to expand...
Click to collapse
In the Android phone arena, we see more update.zip's that are applied via a custom recovery (CW or AmonRA) since we haven't fully cracked (most) system recoveries. Here it looks like any update.zip can be used with the system recovery...
We also don't flash system images, instead we format the SYSTEM partition and then copy the new system or data package over via:
copy_dir PACKAGE:system SYSTEM:
copy_dir PACKAGE:data DATA:
What are the parameters for creating an update.zip for this? What signed process is needed with the system recovery?

What custom roms are you familar with? I really like Apex on my droid x

jerdog said:
In the Android phone arena, we see more update.zip's that are applied via a custom recovery (CW or AmonRA) since we haven't fully cracked (most) system recoveries. Here it looks like any update.zip can be used with the system recovery...
We also don't flash system images, instead we format the SYSTEM partition and then copy the new system or data package over via:
copy_dir PACKAGE:system SYSTEM:
copy_dir PACKAGE:data DATA:
What are the parameters for creating an update.zip for this? What signed process is needed with the system recovery?
Click to expand...
Click to collapse
Unsure what you are saying exactly. Since they don't have to be signed, I hardly ever mess with it. Most of mine have been canabalized stock update.zip's, like you downloaded.
Also, typically we have had better luck with updater-script(updater-binary required and found in your downloaded 3389 update) format/syntax compared to the update-script one.

lilgotti56 said:
What custom roms are you familar with? I really like Apex on my droid x
Click to expand...
Click to collapse
On the Evo, there's (to name a few):
- Myn's
- Azrael X
- Calkulin's EViO
All have taken the stock, and removed as much bloat as is possible and then added in enhancements that make use of the full capabilities of the phone, etc.

rothnic said:
Unsure what you are saying exactly. Since they don't have to be signed, I hardly ever mess with it. Most of mine have been canabalized stock update.zip's, like you downloaded.
Also, typically we have had better luck with updater-script(updater-binary required and found in your downloaded 3389 update) format/syntax compared to the update-script one.
Click to expand...
Click to collapse
That is great they don't need to be signed - much easier to put together.
What has been the issue with the update-script process?

USA 1.141.07 update fix with. .img's

Crsdr37 said:
Alright Guys in the USA. I will be posting the .img files to fix your device or update your device to 1.141.07 if you have either used the chinese update fix or some other various fix that left you with a different boot image. The instructions are simple.
1. Connect your tablet to the computer via USB. Put the boot.img and the system.img on your SD Card. Also put the Update.zip then use a file explorer to move the update.zip to the root of your SD card. Which is external SD. If you use Astro. (Alternatively you can just take your SD card out and put it in your computer to put the update.zip.)
2. You need to first push the boot.img
-Open ADB type su then hit enter. (your device will prompt for superuser you must select allow) Then enter the command below.
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p2 (hit Enter)
3. Then push the system.img
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
4. Force shutdown your device when those finish (as your screen may not turn on.)Then hold volume - and the power button "until the green android comes up very important do not let them go just because the device turns on" to start the update.zip. Let it finish (Your device will reboot when it completes.
5. Enjoy the fact your device is back to stock and you can now update when future updates release.
To push the files you will need adb shell. If you dont know what that is look it up, It is part of the android development kit. Second these 2 commands will push the files to their proper mount block. You must push the boot.img first then the system.img These files are for the USA update 1.141.07
http://www.megaupload.com/?d=TNDCAYC8 - System.img -MD5-2b4e2fea567ac883bb483fc96b1fdc9d
http://www.mediafire.com/?7b5llkk8bnmnd23 -Update.zip
http://www.mediafire.com/?3qahjh3twi6jc9t -Boot.img -MD5-4477d6739dd1e3b3ba1dbf94be7fe8f0
Here are 2 Mirrors To download the boot.img you will need to download both as the uploader made it a 2 part file making it easier for some countries to download. Give thanks yo ardatdat if these came in handy.
http://www.zshare.net/download/91195486183633a0/
http://www.zshare.net/download/9119547812fdf5fa/
I will check periodically on this thread if anyone has questions or needs Help. Guve a huge shout out to deckofficer54 as he is a co-worker and friend that dumped these files for me when I screwed my system up.
Click to expand...
Click to collapse
** Alright guys I am just posting this link for when you just do the update.zip because you are already on 1.104.05_COM_GEN1 and you have a different kernel then the update.zip, What will happen is when you reboot the tablet from just doing the update.zip you may have WIFI error. These files should resolve that issue. Once again they are only if you have WIFI Error on reboot. To install these you will need some type of file explorer that has rw access to the file system. I rec. Root Explorer. To install these follow these instructions.
1. Copy both modules to your SD card does not matter where.
2. With your File Explorer/Manager Copy both of these files. (Root Explorer will let you multi-select if you hit the menu button.)
3. Navigate to System/Lib/Modules.
4. **This step is very important- You must Mount your System for RW access. If you don't they will not copy. Once you have RW just hit the paste button and then reboot your device.
5. **This step is for anyone still having wifi error after reboot. (Stop being lazy lol and just do all the steps. From the top by mounting the boot.img and system.img that way your device is 100% stock there for no checksum issues.
http://forum.xda-developers.com/attachment.php?attachmentid=601473&d=1305842073 - This is the wifi modules Download Link.
Thank you thor2002ro for posting these on your kernel modules thread. Which is found here for anyone having any other issues.
http://forum.xda-developers.com/showthread.php?t=1058713
Happy Updating
​
Alright guys here is the list of supporters thus far for the unbricking and or updating of your tablet. If I missed someone let me know.
Supporters:
Euclid's Brother -Awesome tool to flash the images Making your lives easier one click at a time. If you want an easier way download these images and use this app https://market.android.com/details?id=com.interphaze.Acer_ROM_Flasher
bhageman -Donation
aerichards1977 -Donation
Sent from my PC36100 using XDA Premium App

thanks so much for this. to verify my build number is 1.141.07_COM_GEN1 is that right?

Success! This worked like a charm! I didn't have to use the recovery img I just used the update.zip.
After update:
Kernel: g9b3ce2b
Build: Acer_A500_1.141.07_COM_GEN1
Good work and thanks!
edit: Actually I guess I do have one issue right now. After the update my wifi stopped working. When I go to the wifi settings I see "Error" under Wi-Fi and the check box is grayed out so that it can't be clicked. Any help?

Had a German 1.112 build i guess, bricked it and revocered it with Acer_A500_1.122.01_EMEA_GEN5. Used boot and system image and then updated and it really works!!! Thank you very very very much!!!
EDIT1: I even not lost my settings and can set the language to German too!!
EDIT2: Root gone (as expected), used Gingerbreak (tab version) and everything works fine.

phone.ds said:
Had a German 1.112 build i guess, bricked it and revocered it with Acer_A500_1.122.01_EMEA_GEN5. Used boot and system image and then updated and it really works!!! Thank you very very very much!!!
Click to expand...
Click to collapse
Your Very Welcome. Took me some time to get all the files but this **** works like a frickin charm. I wish it wasnt such a pain in the ass but hey its fixed.

ryutsuke said:
Success! This worked like a charm! I didn't have to use the recovery img I just used the update.zip.
After update:
Kernel: g9b3ce2b
Build: Acer_A500_1.141.07_COM_GEN1
Good work and thanks!
edit: Actually I guess I do have one issue right now. After the update my wifi stopped working. When I go to the wifi settings I see "Error" under Wi-Fi and the check box is grayed out so that it can't be clicked. Any help?
Click to expand...
Click to collapse
well the only thing I can think of it either the lib modules for wifi are messed up in which case I can post a link with them or the kernel is different. I would use the 2 .img that I posted then use the update zip. That way the images replace your kernel which is always the root cause of wifi errors.

here is a link to the wifi lib modules. You need to use something like root explorer. To mount the system as rw. Then navigate to system/lib/modules and copy those two files into there with the system mounted as rw. Reboot and see if it fixes the issue!!
http://www.megaupload.com/?d=OKU671AP

futty said:
thanks so much for this. to verify my build number is 1.141.07_COM_GEN1 is that right?
Click to expand...
Click to collapse
Yes you are now stock and able to update when they release 3.1

dont we need to flash flexrom.img to be 100% stock?

The flexrom was flashed with the update zip
Sent from my A500 using XDA Premium App

confirmed working as well.

Crsdr37 said:
here is a link to the wifi lib modules. You need to use something like root explorer. To mount the system as rw. Then navigate to system/lib/modules and copy those two files into there with the system mounted as rw. Reboot and see if it fixes the issue!!
Click to expand...
Click to collapse
Am I missing something or did you maybe forget the link =P

Ah **** lol give me 1 second
http://www.megaupload.com/?d=OKU671AP
Sent from my A500 using XDA Premium App

Did those libs help at all?a like I said if they don't the only fix I I now would be to go back to the german or chinese update then flash both. Img then update.
Sent from my A500 using XDA Premium App

Image updates
Maybe some file corruption?! Loaded per the directions and on boot got error:
"Secure Boot Image LNX checksum fail"
Going back to the Chinese Rom.

You get that only when do don't do all three'. Once you reboot after pushing the 2 images. You have to hold down the volume - and the power button it will then run the update zip to complete.
Sent from my A500 using XDA Premium App

Crsdr37 said:
Yes you are now stock and able to update when they release 3.1
Click to expand...
Click to collapse
thanks so much again. you are a god i bet you helped millions by doing this

That was my intentions I came from the evo forums. Everybody there helps each other. Im just hoping people here pick it up and start helping when people have questions.
Sent from my A500 using XDA Premium App

ryutsuke said:
Success! This worked like a charm! I didn't have to use the recovery img I just used the update.zip.
After update:
Kernel: g9b3ce2b
Build: Acer_A500_1.141.07_COM_GEN1
Good work and thanks!
edit: Actually I guess I do have one issue right now. After the update my wifi stopped working. When I go to the wifi settings I see "Error" under Wi-Fi and the check box is grayed out so that it can't be clicked. Any help?
Click to expand...
Click to collapse
Did you ever get wifi working
Sent from my A500 using XDA Premium App

tomlogan1 said:
Maybe some file corruption?! Loaded per the directions and on boot got error:
"Secure Boot Image LNX checksum fail"
Going back to the Chinese Rom.
Click to expand...
Click to collapse
Were u able to get past the checksum error?
Sent from my A500 using XDA Premium App

OTA official update recieved 10/05/12

Hi!
Recieved OTA, official update today. Europe. Do not have the details, as i updated it in a hurry. Still same sense/android version. It was minor (about 6mb) "performance" update.
Anyone have any details on this?
EDIT: The update is version 2.42.405.4
Sent from my HTC Vision using XDA

olavnn said:
Hi!
Recieved OTA, official update today. Europe. Do not have the details, as i updated it in a hurry. Still same sense/android version. It was minor (about 6mb) "performance" update.
Anyone have any details on this?
Sent from my HTC Vision using XDA
Click to expand...
Click to collapse
same for me. this the first time i received update while rooted. i downloaded that small update but still did not run it beacuse i am afraid of having S-ON.

The cynic in me think that this may satisfy various insane Apple vs Android things rather than be of any use.
Little sad its not a better version of Android, like 2.3.5.. That would have been nice. I'm happy with Sense 2.1 though.

Any chance of someone grabbing it off their phones and uploading it somewhere?
-Nipqer

Update Archive
I've just got this update, and uploaded it here:
www_filedropper_com/otavisiongingerbreadshtcwwe2424054-2424052release258556lmz8pa872xa8ocgl
I can't post it as a link to it as I'm a noob. Oh well.

thanks
It is clearly a Gingerbread update.
My assumption is, it is in the best case Sense 3.5. Maybe not even that

Software Information:
Android Version:2.3.3
HTC Sense Version: 2.1
Build number: 2.42.405.4 CL192788 release keys
never locked Desire Z

It's still Android 2.3.3 and Sense 2.1
But I think it's a really useful update, in my case I am not having Sense restarts anymore (well, just one, after closing Temple Run). The closing app/going back to homescreen process looks really more fluid now.

could someone please check /data/local.prop for ro.HOME_APP_ADJ=1??
EDIT: downloaded the file... nothing special found... just a bunch of blindness from all those Ps

Can anyone confirm whether its safe to flash if root / S-OFF?
Thanks in advance!
Craig

craiglay said:
Can anyone confirm whether its safe to flash if root / S-OFF?
Thanks in advance!
Craig
Click to expand...
Click to collapse
I'm just root and S-off on 2.3 HTC ROM and installation failed.

thunderbillo said:
I'm just root and S-off on 2.3 HTC ROM and installation failed.
Click to expand...
Click to collapse
Through recovery?
I've now had a look through the update.zip and it seems to patch a fair few system apps as well as firmware.zip which contains boot.img, rcdata.img and recovery.img. I'd suggest if these were successfully flashed we'd loose root and S-OFF as well as recovery (CWM or 4EXT).
I'm still really not sure what this update is about..

I have a question. Does this update eliminates resetting Sense?

craiglay said:
Through recovery?
Click to expand...
Click to collapse
I've seen the error message in CWM when i were pressed POWER because i were blocked.

as007 said:
I have a question. Does this update eliminates resetting Sense?
Click to expand...
Click to collapse
I have not seen the changelog, but on mine its almost gone. It happens less often after the update, in my opinion. And i also feel its running abit smoother. That might be a placebo effect
I have another bug, gallery not updating new pictures, so have to run sd scan to refresh it. The update did not fix this.

thunderbillo said:
I've seen the error message in CWM when i were pressed POWER because i were blocked.
Click to expand...
Click to collapse
I'd imagine because the certificates to flash have changed... I'm not too hot on Android hacking but depending on how you got root, the certs probably got changed or invalidated. It also looks like it flashes a new kernel which may part of the issue.
However, if you've flashed something like Unity v10 like I have, its still a higher version of kernel provided in the update!
---------- Post added at 10:04 PM ---------- Previous post was at 09:58 PM ----------
olavnn said:
I have not seen the changelog, but on mine its almost gone. It happens less often after the update, in my opinion. And i also feel its running abit smoother. That might be a placebo effect
Click to expand...
Click to collapse
I've not really seen the launcher reload issue at all before.. I've seen apps closed due to low RAM but the system stays rather stable, killing background apps. Maybe they've been playing with the figures from the Supercharger Mod which tweaks this very thing.
I have another bug, gallery not updating new pictures, so have to run sd scan to refresh it. The update did not fix this.
Click to expand...
Click to collapse
I've never had this bug.. on 2.42.405.2

I was offered the update today, and I installed it on my stock Gingerbread Desire Z. As far as I can see nothing much changed, but Windows 7 doesn't seem to find the device anymore when trying to connect it as USB mass storage device. Anyone else seeing this, or could I be having some other problem here?
Cheers,
Rob

craiglay said:
Can anyone confirm whether its safe to flash if root / S-OFF?
Thanks in advance!
Craig
Click to expand...
Click to collapse
i tried but the update failed may be because of S-OFF. i think phone should be s-on in order to run that update.

I just succeeded with the update on my rooted system.
Here is what can succeed for people with stock system, just with superuser+busybox installed.
Note that this update will unroot, so you have to re-install SuperUser ZIP package from the recovery menu.
These commands are needed on Linux system with root privileges (I a not sure, whether update images are UID sensitive.)
Code:
#!/bin/sh
rm -f update.zip
mkdir update
cd update
unzip -XK ../OTA_Vision_Gingerbread_S_HTC_WWE_2.42.405.4-2.42.405.2_release_258556lmz8pa872xa8ocgl.zip
mkdir firmware
cd firmware
unzip ../firmware.zip
rm recovery.img
#rm rcdata.img (this part is not needed, most people leave radio and rcdata in random state during the rooting process, this just sets it to value for WWE phones)
rm ../firmware.zip
zip -r ../firmware.zip *
cd ..
rm -r firmware
zip -r ../update.zip *
cd ..
rm -r update
Then flash update.zip from the recovery menu, and then the upper mentioned SuperUser package.
(Note: Not verified! I forgot to add firmware.zip to the image, so I needed to flash system.img separately as PC10IMG.zip.)
---------- Post added at 03:56 AM ---------- Previous post was at 03:42 AM ----------
If there is anybody with unchanged and unrooted stock system, then it would be nice to provide patched system.img as a strart point for modders.
Steps to do it. (It should be safe.)
1. Have at least 600 MB on the sdcard mounted on the phone (and not on computer).
2. Get fre3vo from the downgrade howto
Run this on your machine with adb:
Code:
adb push fre3vo /data/local/tmp
adb shell chmod 755 /data/local/tmp/fre3vo
adb shell /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
# Exploit should succeed.
adb shell
# You should get # prompt here
cat /dev/block/mmcblk0p25 >/sdcard/system.img
rm /data/local/tmp/fre3vo
Then reboot for dropping the temp root and post system.img somewhere for others.
Note: It is safe to apply this vendor update even if you plan to root sometimes in future. This update did not patch the security hole exploited by fre3vo, so this utility still works on HTC_WWE_2.42.405.4.
@qwasson: How did you get the file you posted?

Flashable ROM with this OTA merged in:
http://forum.xda-developers.com/showpost.php?p=26040258&postcount=6945
Just sharing.

[Q] JWR66V -> JWR66Y OTA, debuggerd is buggered

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-