Related
Hello!
First of all, thanks to all you repliers!
I'd really like to know a few things creating a ROM:
1. how can I create an update.zip starting from a system.img? (I know how to sign) In case can I simply install the img and then push /system changes, like root or busybox?
2. how can I install busybox manually? Can I create a script which does the job for me (i.e. busybox --install command at first boot then delete the script itself), avoiding me to write loads of symlinks?
3. when I've created an update.zip, is it easy to root the ROM? I mean, just push su and SuperUser.apk? Or I need a particular boot.img?
Thanks
elegos said:
Hello!
First of all, thanks to all you repliers!
I'd really like to know a few things creating a ROM:
1. how can I create an update.zip starting from a system.img? (I know how to sign) In case can I simply install the img and then push /system changes, like root or busybox?
Click to expand...
Click to collapse
Clockwork Recovery won't install system image files for some reason. You'll need to dump the yaffs2 filesystem then zip it up into the update.zip, then use an updater-script to set unix permissions (zip doesn't preserve these). Also, there's no need to sign the update.zip. It's only meaningful to the device's firmware if it is signed by the device's manufacturer.
elegos said:
Hello!
2. how can I install busybox manually? Can I create a script which does the job for me (i.e. busybox --install command at first boot then delete the script itself), avoiding me to write loads of symlinks?
Click to expand...
Click to collapse
Certainly. You can add a script and call it from updater-script during the install.
elegos said:
Hello!
3. when I've created an update.zip, is it easy to root the ROM? I mean, just push su and SuperUser.apk? Or I need a particular boot.img?
Thanks
Click to expand...
Click to collapse
Boot image is irrelevant to a properly rooted system. Just adding SuperUser should be sufficient.
That's cool!
1. as of the system.img, I see there is a system folder too - is that just enought zipping it?
2. may you please tell me how to call a script within an edify updater-script please?
3. thanks
I don't understand. You have a system.img and a system folder? In what? What are you starting from? If you use a zipped system, you WILL need to set unix permissions, symlinks and modes as these are NOT preserved in a zip file.
As far as calling scripts, something like this:
run_program PACKAGE:installbusybox.sh
Ok, here is a new version of OTA2 for US tablets that should be flashable in CWR and should keep CWR and root without requiring the use of OTA rootkeeper. I would still protect root with OTA Rootkeeper and temp unroot before updating (you can try it without temp unroot but it has caused some problems for other users). This update will still scan all your system apps so you need to restore or unfreeze any system apps that you deleted or froze using Ti Backup.
Instructions:
This update is for owners of US tablets with root and ClockworkMod Recovery. Make sure your battery is well charged before flashing this, a dead battery mid update can create major problems!
1. Install OTA Rootkeeper and protect root. You should now temp unroot. Users who did not temp un-root have had issues with su access after updating.
2. Download the update below and put it on your external sdcard
3. Restore any system apps that you have removed
4. Reboot into ClockworkMod Recovery (Shutdown Thinkpad, turn on and press vol+ repeatedly until you see booting recovery image)
5. I would also highly recommend making a nandroid backup if you have not previously done so.
6. Select install zip from sdcard>choose zip from sdcard then browse to and select the update you downloaded here
7. update.zip will run, it will check your system apps during the update and may fail if you have changed something, if so the error message should explain why
8. Reboot tablet; it will be a very long reboot. This is normal; it seems to take forever but just let it boot.
9. Use OTA Rootkeeper to restore root.
Flash at your own risk! I am not responsible if this totally bricks your tablet! This is the US update, do not flash if you are using a tablet from another region! Seriously this stuff could cause problems.
ThinkPadTablet_A310_02_0039_0086_US_CWR.zip
-----------------------------------------
Original Message
So I would like to modify the new OTA so I get the updates without losing root and my current recovery. It is my understanding that the file: \META-INF\com\google\android\updater-script contains the instructions for how the update should run. Can I simply modify this script so that it won't delete root or overwrite my recovery or boot and then flash it in CWR? It looks like it would be pretty straight forward but it would be nice to get some information from someone more knowledgeable so that I don't mess something up and brick my TpT. One obvious line to remove would be where it deletes superuser.apk and su. There is also a section where it patches the boot image, I'm not sure what this patch does but I am worried that maybe somehow they might lock the bootloader. EDIT: I updated, and still have CWR so the bootloader didn't get locked. The other lines I would remove are the ones that reference recovery. If someone with knowledge of android would be willing to help me with this then I will upload my modified update.zip (assuming it works) so that others can avoid the hassle.
So I think that the process would be to delete the current \META-INF\ folder, then put in my modified updater script in \META-INF\com\google\android\updater-script and sign the update with SignApk.jar? Is this the correct process? Any help would be greatly appreciated.
Thanks.
I attached the original updater-script below for anyone interested in taking a look.
I appreciate you posting the file. I've never worked with Android code and this was a great intro.
I'm not sure this will work. Although I'm not super knowledgeable in this.
I did find these two threads.
http://forum.xda-developers.com/showthread.php?t=1185881
http://forum.xda-developers.com/showpost.php?p=21351145&postcount=101
Of course, the latter is in respect to the Galaxy Nexus, and I am sure most of those people have unlocked bootloaders, etc. So again, not sure if those shed any more light on it, but am also curious on a process like this.
The update popped up on my tablet last night and I clicked "more info" and from what it lists, does not seem to be very many fixes
So I successfully updated in ClockworkMod Recovery without losing CWR and without deleting my Superuser.apk and su files by modifying the updater-script in the update.zip. Unfortunately it still messed up my superuser permissions somehow and I ended up having to use ADB while booted into CWR to push and symlink the proper files to get su working again (OTA Rootkeeper wasn't functioning properly because the files were there but the permissions were messed up). I have modified the update.zip so that now it deletes the superuser.apk and su files but keeps clockworkmod recovery. With this and OTA Rootkeeper I think you should be able to update while keeping CWR and restoring root. I will also provide directions here for those seeking to make their own modifications and possibly improve upon my efforts, but proceed with caution.
So what I did was open the zip in winrar and extracted the updater-script. I then edited some lines of code using Notepad++, deleting the ones that referred to deleting recovery or installing a new recovery as well as the lines to delete superuser.apk and /system/bin/su and /system/xbin/su. I also commented out a couple lines at the beginning (assert(getprop("ro.product.device") == "Indigo") because I was getting an error code status 7 when it was trying to perform this check while using clockwork mod. I checked my build.prop and it does say Indigo so I don't know why the check failed but just removing the check was easier for me than figuring out the problem (generally it is not good to remove such checks but I was sure I had the right file). In Notepad++ you must select save as and choose type all files then just save it with the same name. Then replace the updater-script in your zip file with the modified one, I used winrar and chose the compression to just be store (ie no compression). Then you need to delete the CERT.RSA, CERT.SF, and MANIFEST.MF files in the META-INF folder of your update.zip and you sign the update.zip using testsign.jar. Then your new modified update.zip is ready to go.
I think that the reason things did not work out for me is that there are a bunch of lines in the updater script about symlinking and setting permissions for stuff in /system and I think /system/bin/su was originally symlinked to /system/xbin/su which is the real file so things got messed up and I had the files still but the symlink and or permissions were messed up. I eventually fixed this by booting into CWR mounting system and using adb to repush /system/xbin/su and setting permissions and making the new symlinked su file in /system/bin just like the last lines of Dan's Thinkpad root bat file did.
Here is a modified update.zip that should delete your Superuser files but keep your ClockworkMod Recovery. I think that with this file you can use OTA Rootkeeper to make a root backup, temp unroot, then boot into CWR and update to the new OTA then you should be able to reboot and use OTA Rootkeeper to restore root and download Superuser from the market, while keeping CWR through the entire process.
Flash at your own risk! I am not responsible if this totally bricks your tablet! This is the US update, do not flash if you are using a tablet from another region! Seriously this stuff could cause problems.
That being said I think it will work. I followed this guide to sign my update.
Original updater-script
Modified updater-script in the update.zip linked above (this one deletes Superuser /system/bin/su and /system/xbin/su but keeps CWR)
Modified updater-script that I flashed on my tablet (this one messed up my su but doesn't delete the files)
If you need a good online file locker join Dropbox here and we'll both get an extra 250mb of space.
Unfortunately that update.zip didn't work for me, game me an error in CWR.
Is the other method, replacing the update scrip in the OTA and trying it ?
freezepop said:
Unfortunately that update.zip didn't work for me, game me an error in CWR.
Is the other method, replacing the update scrip in the OTA and trying it ?
Click to expand...
Click to collapse
Depending on the error you can likely edit the updater-script yourself and successfully installed. Most errors are due to changes in system apps causing them to fail checks. If you remove an app check you should probably remove the corresponding patch for that app in the updater script. What error did you have?
Ok, here is a new version of OTA2 for US tablets that should be flashable in CWR and should keep CWR and root without requiring the use of OTA rootkeeper. I would still protect root with OTA Rootkeeper and temp unroot before updating (you can try it without temp unroot but it has caused some problems for other users). This update will still scan all your system apps so you need to restore or unfreeze any system apps that you deleted or froze using Ti Backup.
Instructions:
This update is for owners of US tablets with root and ClockworkMod Recovery. Make sure your battery is well charged before flashing this, a dead battery mid update can create major problems!
1. Install OTA Rootkeeper and protect root. You should now temp unroot. Users who did not temp un-root have had issues with su access after updating.
2. Download the update below and put it on your external sdcard
3. Restore any system apps that you have removed
4. Reboot into ClockworkMod Recovery (Shutdown Thinkpad, turn on and press vol+ repeatedly until you see booting recovery image)
5. I would also highly recommend making a nandroid backup if you have not previously done so.
6. Select install zip from sdcard>choose zip from sdcard then browse to and select the update you downloaded here
7. update.zip will run, it will check your system apps during the update and may fail if you have changed something, if so the error message should explain why
8. Reboot tablet; it will be a very long reboot. This is normal; it seems to take forever but just let it boot.
9. Use OTA Rootkeeper to restore root.
Flash at your own risk! I am not responsible if this totally bricks your tablet! This is the US update, do not flash if you are using a tablet from another region! Seriously this stuff could cause problems.
ThinkPadTablet_A310_02_0039_0086_US_CWR.zip
jhankinson said:
Ok, here is a new version of OTA2 for US tablets that should be flashable in CWR and should keep CWR and root without requiring the use of OTA rootkeeper. I would still protect root with OTA Rootkeeper just in case something goes wrong but don't temp unroot before updating and see if root still works after the update. This update will still scan all your system apps so you need to restore or unfreeze any system apps that you deleted or froze using Ti Backup.
Instructions:
This update is for owners of US tablets with root and ClockworkMod Recovery. Make sure your battery is well charged before flashing this, a dead battery mid update can create major problems!
1. Install OTA Rootkeeper and protect root (just in case), you shouldn't need to temp unroot though with this update.
2. Download the update below and put it on your external sdcard
3. Restore any system apps that you have removed
4. Reboot into ClockworkMod Recovery (Shutdown Thinkpad, turn on and press vol+ repeatedly until you see booting recovery image)
5. I would also highly recommend making a nandroid backup if you have not previously done so.
6. Select install zip from sdcard>choose zip from sdcard then browse to and select the update you downloaded here
7. update.zip will run, it will check your system apps during the update and may fail if you have changed something, if so the error message should explain why
8. Reboot tablet; it will be a very long reboot. This is normal; it seems to take forever but just let it boot.
Flash at your own risk! I am not responsible if this totally bricks your tablet! This is the US update, do not flash if you are using a tablet from another region! Seriously this stuff could cause problems.
ThinkPadTablet_A310_02_0039_0086_US_CWR.zip
Click to expand...
Click to collapse
Thank you for your work. I have ROW version and waiting OTA2 for that, but still now I know how to modify update-script. I have a question, why not to remove any unneeded software from update and remove check for installed software which are already removed?
redbaron said:
Thank you for your work. I have ROW version and waiting OTA2 for that, but still now I know how to modify update-script. I have a question, why not to remove any unneeded software from update and remove check for installed software which are already removed?
Click to expand...
Click to collapse
Different people have removed different apps so one person may want the patch while another might want it skipped. I was just posting a generic version here that works for stock system apps. If others want to further customize their script then they are welcome improve upon it or customize it for their own system.
jhankinson said:
Ok, here is a new version of OTA2 for US tablets that should be flashable in CWR and should keep CWR and root without requiring the use of OTA rootkeeper. I would still protect root with OTA Rootkeeper just in case something goes wrong but don't temp unroot before updating and see if root still works after the update. This update will still scan all your system apps so you need to restore or unfreeze any system apps that you deleted or froze using Ti Backup.
Instructions:
This update is for owners of US tablets with root and ClockworkMod Recovery. Make sure your battery is well charged before flashing this, a dead battery mid update can create major problems!
1. Install OTA Rootkeeper and protect root (just in case), you shouldn't need to temp unroot though with this update.
2. Download the update below and put it on your external sdcard
3. Restore any system apps that you have removed
4. Reboot into ClockworkMod Recovery (Shutdown Thinkpad, turn on and press vol+ repeatedly until you see booting recovery image)
5. I would also highly recommend making a nandroid backup if you have not previously done so.
6. Select install zip from sdcard>choose zip from sdcard then browse to and select the update you downloaded here
7. update.zip will run, it will check your system apps during the update and may fail if you have changed something, if so the error message should explain why
8. Reboot tablet; it will be a very long reboot. This is normal; it seems to take forever but just let it boot.
Flash at your own risk! I am not responsible if this totally bricks your tablet! This is the US update, do not flash if you are using a tablet from another region! Seriously this stuff could cause problems.
ThinkPadTablet_A310_02_0039_0086_US_CWR.zip
Click to expand...
Click to collapse
I flashed this zip. It didn't delete su or Superuser.apk, yet apps cannot get root access afterward. any suggestions?
mandrsn1 said:
I flashed this zip. It didn't delete su or Superuser.apk, yet apps cannot get root access afterward. any suggestions?
Click to expand...
Click to collapse
That is what happened to me originally, it can be fixed though. Did you make a backup with OTA Rootkeeper? If so open Android Terminal emulator and type:
/system/su-backup
mount -o remount,rw /system
cp -f /system/su-backup /system/xbin/su
ln -s /system/xbin/su /system/bin/su
chown root /system/xbin/su
chmod 6755 /system/xbin/su
Then reboot your tablet. I believe this should fix your root access. If you don't have a backup I think you can also fix it by running adb while booted into CWR. I can give you those instructions if this doesn't work.
Apparently you should temp un-root before installing my update then restore your su backup with OTA Rootkeeper after updating.
You wear the crown
Thanks for posting the fix, too. Waiting for reboot to finish.
Really appreciate all your hard work. The instructions you posted for me in thinkpad forums worked perfectly and I learned a lot in the process.
toenail_flicker said:
Thanks for posting the fix, too. Waiting for reboot to finish.
Really appreciate all your hard work. The instructions you posted for me in thinkpad forums worked perfectly and I learned a lot in the process.
Click to expand...
Click to collapse
Did the fix work for you?
Still waiting for reboot. I waited about 20 minutes and rebooted manually. So far it still hasn't made it in for me to try the fix.
---------- Post added at 09:58 PM ---------- Previous post was at 09:44 PM ----------
jhankinson said:
Did the fix work for you?
Click to expand...
Click to collapse
Fix not yet working. Got this far
/system/su-backup
mount -o remount,rw /system
cp -f /system/su-backup /system/xbin/su
error message
cp: applet not found
Any ideas?
toenail_flicker said:
Still waiting for reboot. I waited about 20 minutes and rebooted manually. So far it still hasn't made it in for me to try the fix.
---------- Post added at 09:58 PM ---------- Previous post was at 09:44 PM ----------
Fix not yet working. Got this far
/system/su-backup
mount -o remount,rw /system
cp -f /system/su-backup /system/xbin/su
error message
cp: applet not found
Any ideas?
Click to expand...
Click to collapse
try
busybox cp -f /system/su-backup /system/xbin/su
may have to type busybox before some of the other commands too if they give an error.
So my line would be
busybox cp -f /system/su-backup /system/xbin/su
cp: applet not found
Just a quick note of thanks for getting me through this. Root is wonderful!
If
cp -f /system/su-backup /system/xbin/su
fails, use
dd if=/system/su-backup of=/system/xbin/su
instead.
jhankinson said:
Ok, here is a new version of OTA2 for US tablets that should be flashable in CWR and should keep CWR and root without requiring the use of OTA rootkeeper. I would still protect root with OTA Rootkeeper just in case something goes wrong but don't temp unroot before updating and see if root still works after the update. This update will still scan all your system apps so you need to restore or unfreeze any system apps that you deleted or froze using Ti Backup.
Instructions:
This update is for owners of US tablets with root and ClockworkMod Recovery. Make sure your battery is well charged before flashing this, a dead battery mid update can create major problems!
1. Install OTA Rootkeeper and protect root. You should now temp unroot. Users who did not temp un-root have had issues with su access after updating.
2. Download the update below and put it on your external sdcard
3. Restore any system apps that you have removed
4. Reboot into ClockworkMod Recovery (Shutdown Thinkpad, turn on and press vol+ repeatedly until you see booting recovery image)
5. I would also highly recommend making a nandroid backup if you have not previously done so.
6. Select install zip from sdcard>choose zip from sdcard then browse to and select the update you downloaded here
7. update.zip will run, it will check your system apps during the update and may fail if you have changed something, if so the error message should explain why
8. Reboot tablet; it will be a very long reboot. This is normal; it seems to take forever but just let it boot.
9. Use OTA Rootkeeper to restore root.
Flash at your own risk! I am not responsible if this totally bricks your tablet! This is the US update, do not flash if you are using a tablet from another region! Seriously this stuff could cause problems.
ThinkPadTablet_A310_02_0039_0086_US_CWR.zip
Click to expand...
Click to collapse
Thx jhankinson, this work for me. my TPT 1838 US.
Hi,
This is just to let everyone know that the latest updates being pushed by Asus breaks Voodoo OTA Rootkeeper's su backups.
Basically it removes the setuid bit from the su backup that is kept in /system/su-backup and from all binaries in the /system partition.
So you will lose root and will not be able to restore it with Rootkeeper after this OTA.
Luckily, the "1-Click Transformer Root" tool still works on it:
http://forum.xda-developers.com/showthread.php?p=26918950
So you can gain root once again and keep your stock recovery with OTAs enabled.
Cheers!
idcrisis said:
Basically it removes the setuid bit from the su backup that is kept in /system/su-backup and from all binaries in the /system partition.
Click to expand...
Click to collapse
Do you still have the OTA dlpkgfile? If so, could you please share it somewhere (dropbox/box.com/wuala/etc.)?
sbiriguda said:
Do you still have the OTA dlpkgfile? If so, could you please share it somewhere (dropbox/box.com/wuala/etc.)?
Click to expand...
Click to collapse
Here you go:
http://www.mediafire.com/?d1cq2f911ipd35r
From what I can see the culprit seems to be these lines in the updater-script:
Code:
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
Let us know if you find another place to hide the damn thing.
Maybe /system/.subackup or /system/.subackup/.subackup
Worth a try perhaps.
idcrisis said:
Code:
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
Let us know if you find another place to hide the damn thing.
Maybe /system/.subackup or /system/.subackup/.subackup
Click to expand...
Click to collapse
Nope, set_perm_recursive traverses the entire hierarchy, so the first line will nuke the setuid/setgid bits on whatever executable it finds under /system.
I'm a bit puzzled - though - since the same line is present in each and every OTA released by Asus and to my knowledge no-one has ever had any problem with OTA Rootkeper.
sbiriguda said:
Nope, set_perm_recursive traverses the entire hierarchy, so the first line will nuke the setuid/setgid bits on whatever executable it finds under /system.
I'm a bit puzzled - though - since the same line is present in each and every OTA released by Asus and to my knowledge no-one has ever had any problem with OTA Rootkeper.
Click to expand...
Click to collapse
I had also kept another copy for safekeeping in case they manually detected for the Rootkeeper copy of su. This was stored as /system/etc/su-backup and had mode 06755 as /system/su-backup.
Both were changed to 00755 by the update presumably from the first line.
I would think the second line would be present in all the past updates, but the first may not have been or for some reason wasn't working properly in the previous updates.
Or something very strange happened on my tablet. Unlikely as I have kept everything very close to stock.
Someone else may be able to confirm by tomorrow perhaps when it's been pushed far and wide.
The tf101 9.2.1.24 update nukes Voodoo backups to
Hello, i was able to restore su backup from voodoo after upgrading from 21 to 24 on my tf101, without any problems
Rooted with wolf's method 3 on .21
Regards
PERI also works on the latest update
Confirmed on other tablets, 9.2.2.6 breaks Rootkeeper by wiping the setuid bit from all binaries in /system recursively.
Onwards to next idea!
So I have the asop 4.2.1 built with make otapackage but every time I try to install it using TWRP I get an error 7
What I did:
- built the ota
- deleted recovery folder
- flashed rom - got an error 7
Any tips on this? Thanks.
up?
try not deleting anything and flash again, there might be something in the install script that relies on it. for anything it tries to do there and wont find it will throw an exception and break the install. after you have your cause you can still worry about the recovery.
vomer said:
So I have the asop 4.2.1 built with make otapackage but every time I try to install it using TWRP I get an error 7
What I did:
- built the ota
- deleted recovery folder
- flashed rom - got an error 7
Any tips on this? Thanks.
Click to expand...
Click to collapse
vomer,
You have to remove these lines from '/META-INF/com/google/android/updater-script' file (in your ota zip).
Code:
package_extract_dir("recovery", "/system");
set_perm(0, 0, 0544, "/system/etc/install-recovery.sh");
i.e, search 'recovery' in 'updater-script' and remove that line.
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-