This is a much simpler and hasslefree process.
Download the root file from : here.
Instructions :
Put the downloaded root.zip in external sdcard.
Go to the stock recovery.
Select apply update from sdcard.
Select root.zip
Flash
Reboot
Please let me know if there are any problems!
Proof : forum.xda-developers.com/showpost.php?p=37976783&postcount=9
Credits :
Phil for finding the method..
I do not respond to tech support via PM
Stock recovery? How does it pass if not signed by samsung?
tys0n said:
Stock recovery? How does it pass if not signed by samsung?
Click to expand...
Click to collapse
This zip is made for stock.
Its been signed..
I do not respond to tech support via PM
Shaaan said:
This zip is made for stock.
Its been signed..
I do not respond to tech support via PM
Click to expand...
Click to collapse
A question i was about to ask...
But the answer and the /wink really rocks!
Thanks!
Root failed
Rebooted to recovery via ADB.
Started root.zip, result is following:
E:failed to verify whole-file signature
E:signature verification failed
I wonder what is wrong with this device! Nothing normal works on this.!
I do not respond to tech support via PM
Sv: [ROOT] Root JB
ladislav.heller said:
Rebooted to recovery via ADB.
Started root.zip, result is following:
E:failed to verify whole-file signature
E:signature verification failed
Click to expand...
Click to collapse
Ok, just as every other "signed". Zip's made for this model :-\
Sent thru time and space from my s3mini.
It doesnt work for me.
E:failed to verify whole-file signature
E: signature verification failed
I have stock Official 4.1.1 android version si stock recovery
XXALJL build.
tys0n said:
Ok, just as every other "signed". Zip's made for this model :-\
Sent thru time and space from my s3mini.
Click to expand...
Click to collapse
This zip is signed using Google developer keys. These keys get past Samsungs signature verification!
We have been using this zip on various 4.0+ devices..
I do not respond to tech support via PM
Shaaan said:
This zip is signed using Google developer keys. These keys get past Samsungs signature verification!
We have been using this zip on various 4.0+ devices..
I do not respond to tech support via PM
Click to expand...
Click to collapse
Maybe Samsung has its own signing key? Or the verification method was modified...
Our device has some kind of next generation security. So I've read somewhere on this forum, and all of bypass security mods and hacks that worked on other devices don't work on this device. Like triangle away and other stuff..
Sent from my GT-I8190 using Tapatalk 2
ladislav.heller said:
Maybe Samsung has its own signing key? Or the verification method was modified...
Click to expand...
Click to collapse
Yep, although it was worth trying. Older Samsung devices could be rooted this way (the Galaxy Y for example).
tested and not work faile signature verification and after tested with signing your zip with md5sum only signe and not work some message faile signature verification
spawk said:
tested and not work faile signature verification and after tested with signing your zip with md5sum only signe and not work some message faile signature verification
Click to expand...
Click to collapse
same for me! its not working... :crying:
Samsung digital certificate
Attached is the original Samsung digital certificate extracted from sec_csc.zip. You can open it in Windows and import if you want (just remove the .txt extension). But unfortunately it has no private key so we can't create signing hash for script files, etc.
ladislav.heller said:
Attached is the original Samsung digital certificate extracted from sec_csc.zip. You can open it in Windows and import if you want (just remove the .txt extension). But unfortunately it has no private key so we can't create signing hash for script files, etc.
Click to expand...
Click to collapse
Have you considered contacted Samsung to obtain their private key? I see no reason why they wouldn't give it to an unknown third party.
xd.bx said:
Have you considered contacted Samsung to obtain their private key? I see no reason why they wouldn't give it to an unknown third party.
Click to expand...
Click to collapse
Not yet
Actually I don't know their contact address.
Maybe I should write to [email protected] which is in the certificate?
ladislav.heller said:
Not yet
Actually I don't know their contact address.
Maybe I should write to [email protected] which is in the certificate?
Click to expand...
Click to collapse
I think that xd.bx has been 100% ironic in his post.
Would anyone with official 4.1.2 has been successful with this method make a confirmation here please? Thx!
Shaaan said:
This is a much simpler and hasslefree process.
Download the root file from : here.
Instructions :
Put the downloaded root.zip in external sdcard.
Go to the stock recovery.
Select apply update from sdcard.
Select root.zip
Flash
Reboot
Please let me know if there are any problems!
Proof : forum.xda-developers.com/showpost.php?p=37976783&postcount=9
Credits :
Phil for finding the method..
I do not respond to tech support via PM
Click to expand...
Click to collapse
benjaminv said:
Would anyone with official 4.1.2 has been successful with this method make a confirmation here please? Thx!
Click to expand...
Click to collapse
No it's not working with stock recovery.
Related
Hi all,
I'm trying to make an update.zip for users to install my app easily in recovery mode. It sounds trivial, and should basically just copy the apk into /data/app/.
Before I sign it, the zip contains (as shown by "unzip -t"):
Code:
data/app/com.keramidas.TitaniumBackup.apk
META-INF/com/google/android/update-script/update-script
The update-script is as follows:
Code:
show_progress 0.1 0
copy_dir PACKAGE:data DATA:
show_progress 0.1 10
Then I signed the update.zip with:
jarsigner -verbose -keystore my_keystore update.zip my_key
When I launch:
jarsigner -verify update.zip
I get "jar verified".
But in Clockwork recovery, my update.zip does not work - and signature verification is disabled, afaik.
EDIT: I have uploaded the update.zip there:
http://matrixrewriter.com/android/files/update.zip
Any ideas ?
Thanx in advance for any help
joel.bourquard said:
Hi all,
I'm trying to make an update.zip for users to install my app easily in recovery mode. It sounds trivial, and should basically just copy the apk into /data/app/.
Before I sign it, the zip contains (as shown by "unzip -t"):
Code:
data/app/com.keramidas.TitaniumBackup.apk
META-INF/com/google/android/update-script/update-script
The update-script is as follows:
Code:
show_progress 0.1 0
copy_dir PACKAGE:data DATA:
show_progress 0.1 10
Then I signed the update.zip with:
jarsigner -verbose -keystore my_keystore update.zip my_key
When I launch:
jarsigner -verify update.zip
I get "jar verified".
But in Clockwork recovery, my update.zip does not work - and signature verification is disabled, afaik.
EDIT: I have uploaded the update.zip there:
http://matrixrewriter.com/android/files/update.zip
Any ideas ?
Thanx in advance for any help
Click to expand...
Click to collapse
Hey Joel
Just curious has this been sorted yet? I would love a .zip so I can flash it after a new ROM when I don't have data.
FHL09 said:
Hey Joel
Just curious has this been sorted yet? I would love a .zip so I can flash it after a new ROM when I don't have data.
Click to expand...
Click to collapse
Hi dear Androlute overlord
Unfortunately no, I haven't got any hint on how to fix the zip file. Looking forward to having a working file!
I tweeted about it today, so I'm hoping someone will help...
Thanks
It's okay, the zip file works now. The update-script was misplaced
Hi Joel,
DO we have to sign the zip file created or would it be possible for your app to sign the file?
Thanks NSCXP2005
nscxp2005 said:
Hi Joel,
DO we have to sign the zip file created or would it be possible for your app to sign the file?
Thanks NSCXP2005
Click to expand...
Click to collapse
Hi,
The generated zip files are not signed - sorry.
I would love to incorporate the necessary signing code into my app, but unfortunately the signapk tool seems to require several Sun-only crypto classes, which don't exist on Android. If you know of a java implementation that can sign a zip file without using these Sun-only imports, please let me know and (as long as it's in the public domain) I'd be glad to include it in my app.
Thanks!
ok, Thanks.
Could you tell me how to sign the Update.zip that has been created by your app?
nscxp2005 said:
ok, Thanks.
Could you tell me how to sign the Update.zip that has been created by your app?
Click to expand...
Click to collapse
I have never really done it (or succeeded to do it), to be honest.
You need to use the "signapk" tool. I tried with Sun's standard "jarsigner" tool that comes with the JDK, but it wasn't considered as properly signed by the recovery image I have (Clockwork).
If you have more success than me, please let me know...
ok, thanks Joe, I hope you manage to find a way to sign the update.zip in the future.
Keep up the great work!!
EDIT Joel, I finally managed to flash your app in Recovery!!
Go here and look at the Update Maker made by DMzda
Update Maker
I hope you manage to implement this in to your update generator
I hope this helps
All the best
NSCXP2005
Hi!
I signed a custom kernel with SignApk.jar and recovery console cannot verify it.
I get
E:No signature
E:Verification failed
Signing the same source zip with testsign.jar results in a positive verification.
Comparing the resulting CERT.SF files I realized that SHA1-Digest-Manifest is different. The reason why: two files are interchanged in the list. But that can't be the problem, can it?
I'm trying and using zipSigner from maket, and it's quite complete and straightforward for signature
I used SignApk few times with no success, and do not know other methods at the moment ^^
If you used the test keys with signapk.jar, it would likely do the same thing as testsign.jar does. The difference is the keys used to sign the package, which can cause one to fail and the other to be ok.
imnuts said:
If you used the test keys with signapk.jar, it would likely do the same thing as testsign.jar does. The difference is the keys used to sign the package, which can cause one to fail and the other to be ok.
Click to expand...
Click to collapse
Let me guess: it is not documented which keys and keystrenghts are okay for signapk?
Der_Caveman said:
Let me guess: it is not documented which keys and keystrenghts are okay for signapk?
Click to expand...
Click to collapse
I think the keys that are required are the Android test keys, but I don't know where you would get them to use with signapk.jar
So this is only a problem of custom recovery?
I tried also jarsigner with no luck.
Sent from my LG-P500 using XDA App
why don't you just toggle signature verification? it will disable signature verification.
I can sign with testsign.jar so there is no problem flashing something- I only wanted to know why I can't put in my own cert.
Here is another ZIP for the ICS dlpkgfile: h t t p : / / dl.dropbox.com/u/3547656/dlpkgfile%20%28AsusTransformerICS%29.zip
Here is the exact same file on MediaFire: h t t p : / / w w w . mediafire.com/?k3fm9mwswhx4k8r
I will upload the same ZIP to a dedicated server as well.
Remove the spaces in the http parts of the link.
Do NOT flash in recovery.
Posted a link to MediaFire as well. If either one of these links are non-working, then I will upload to my dedicated server.
how can we use this?
wertico said:
how can we use this?
Click to expand...
Click to collapse
if you are a modifier, then you could repack the zip, add SU, mod it how you want, and release it as a rom, or really anything..
This cant be installed right?
rafa6571 said:
This cant be installed right?
Click to expand...
Click to collapse
it could if you own a TW TF101.. otherwise, no.
im trying to get this file from the download sites but the links you gave arent workin if i can get this i can prolly add su and zip it
neofreek01 said:
im trying to get this file from the download sites but the links you gave arent workin if i can get this i can prolly add su and zip it
Click to expand...
Click to collapse
Working fine here. Make sure you remove the spaces in the links.
flying_pigs, if you've updated, please, do the following:
1, Flash CWM or Rogue recovery
2, Reboot to recovery
3, Select Backup, Advanced Backup, and only do a backup of system!
4, Upload this backup image somewhere, and post the link
Problem is, many of us can't apply the patch for some reason. This would help it!
fonix232 said:
flying_pigs, if you've updated, please, do the following:
1, Flash CWM or Rogue recovery
2, Reboot to recovery
3, Select Backup, Advanced Backup, and only do a backup of system!
4, Upload this backup image somewhere, and post the link
Problem is, many of us can't apply the patch for some reason. This would help it!
Click to expand...
Click to collapse
Sorry to say that I have not updated yet and won't have time to make use of this file till much later.
I was just uploading this file since the other Dropbox link went down.
I got a TW TF101, how do I use the file?
My build Number is:
HTK75.TW_epad-8.6.5.13-20110925,
FOTA does not work for me.. says no update for me with my current IP (eu) :-/
Do I need 8.6.5.21 before this update?
So my lovely TF101 is not rooted (and so there's also no CWM etc.).
But I think there is a way to install it manually, isn't it? Something like renaming the file, transferring it to a SD card... Or am mixing something up? Then I'll probably have to wait the 7 days until it is supposed to be here in Germany (I really wonder why it should take that long...)
synaps1s said:
I got a TW TF101, how do I use the file?
My build Number is:
HTK75.TW_epad-8.6.5.13-20110925,
FOTA does not work for me.. says no update for me with my current IP (eu) :-/
Do I need 8.6.5.21 before this update?
Click to expand...
Click to collapse
Yes you do.
I'm downloading a .21 TW zip file right now, it's taking forever. Later tonight I can release a safe cwm zip for you to get to .21.
Right, so, through a bit of trial and error using guidance from the forums, this is how I updated to JB and kept root for WW after the update originally failed.
download BOTH files from here (massive thanks to ch3mn3y):
http://www25.zippyshare.com/v/91334594/file.html
http://www1.zippyshare.com/v/96461494/file.html
then extract the .zip file.
download the command file from here (massive thanks to krabappel2548):
http://www.mediafire.com/?yq1bt16mnm7tc8d
extract it.
place the dlpkgfile and command file, both unzipped onto your tab. Use a root explorer to paste the command file into /cache/recovery and the dlpkgfile (the actual file, not the folder) to /cache.
go to Voodoo OTA Rootkeeper and temp unroot.
turn off the tab.
boot into recovery with Vol - and power, then when it says to press volume up to boot into RCK, do it.
You'll see the android with the blue wires and it will go through the install process if you have done it right. let it do its thing.
obviously, when it has settled, restore root with Voodoo.
If you get the android with red exclamation mark, i reccomend downloading the ICS zip of your current firmware and SKU and sticking it on a micro SD card, and letting it restore any programmes you've deleted.
rickykemp said:
Right, so, through a bit of trial and error using guidance from the forums, this is how I updated to JB and kept root for WW after the update originally failed.
download BOTH files from here (massive thanks to ch3mn3y):
http://www25.zippyshare.com/v/91334594/file.html
http://www1.zippyshare.com/v/96461494/file.html
then extract the .zip file.
download the command file from here (massive thanks to krabappel2548):
http://www.mediafire.com/?yq1bt16mnm7tc8d
extract it.
place the dlpkgfile and command file, both unzipped onto your tab. Use a root explorer to paste the command file into /cache/recovery and the dlpkgfile (the actual file, not the folder) to /cache.
go to Voodoo OTA Rootkeeper and temp unroot.
turn off the tab.
boot into recovery with Vol - and power, then when it says to press volume up to boot into RCK, do it.
You'll see the android with the blue wires and it will go through the install process if you have done it right. let it do its thing.
obviously, when it has settled, restore root with Voodoo.
If you get the android with red exclamation mark, i reccomend downloading the ICS zip of your current firmware and SKU and sticking it on a micro SD card, and letting it restore any programmes you've deleted.
Click to expand...
Click to collapse
Will your last line lose root on us, or will voodoo root keeper save it via that or does it wipe/reset the entire system?
Ashcunak said:
Will your last line lose root on us, or will voodoo root keeper save it via that or does it wipe/reset the entire system?
Click to expand...
Click to collapse
When i ran ran the zip of .30 i did lose root, but it was easily restored using 1 click transformer root.
I tried it twice but it always failed at about 1/3 of the process... Hopefully I can reboot w/ any damage...
WHY!?? :'(
Btw here's the part of the log where it shows the failure in installation:
I:Enable RSA key verification.
Installing update...
Finding update package...
I:Update location: /cache/dlpkgfile
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1682 bytes; signature 1664 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Check : blob size = 13104069
Verifying current system...
file "/system/lib/libGLESv1_CM.so" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/lib/libGLESv1_CM.so", "ed4c7834196831836c73d0374529a0278c2fa91c", "a52756f5a63c9827632587d025ee28f67739bd97")
assert failed: apply_patch_check("/system/lib/libGLESv1_CM.so", "ed4c7834196831836c73d0374529a0278c2fa91c", "a52756f5a63c9827632587d025ee28f67739bd97")
E:Error in /cache/dlpkgfile
(Status 7)
Installation aborted.
I:result_code: 410
Check and format /storage to vfat if needed...
Mount /btmac successfully
Done
Btw the command file is just a file with content --update_package=/cache/dlpkgfile in it.
You can create it with notepad, save as .txt, and remove the .txt
rickykemp said:
When i ran ran the zip of .30 i did lose root, but it was easily restored using 1 click transformer root.
Click to expand...
Click to collapse
OH, wow, im so outa date thanks, i rooted on the first revision that came out and havent really watched whats out there for root options. i see this now thanks so much i was worried id have to all sorts of downgrading. link for anyone else whos "outa it" like me http://forum.xda-developers.com/showthread.php?p=26918790
WIIstpM said:
file "/system/app/Music2.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/app/Music2.apk", "c9bc168a88b5106e0e04f8e70023a4c33009021b", "cbb199983ab1cb9beee6b20ec4db659ccd49d757")
assert failed: apply_patch_check("/system/app/Music2.apk", "c9bc168a88b5106e0e04f8e70023a4c33009021b", "cbb199983ab1cb9beee6b20ec4db659ccd49d757")
Click to expand...
Click to collapse
Maybe u delete or freeze Music2.apk? First time when i forget to unfreeze /system apps my update failed too (but i dont remember when).
ch3mn3y said:
Maybe u delete or freeze Music2.apk? First time when i forget to unfreeze /system apps my update failed too (but i dont remember when).
Click to expand...
Click to collapse
I think I found the problem: I remember I pushed jelly bean's music2.apk in system/app! Restored the original music app.
Gonna try update again!
Now it the turn of libGLESv1_CM.so ...
Going to give it a try.
Just to make sure, is this for WW version, right?
ch3mn3y said:
Maybe u delete or freeze Music2.apk? First time when i forget to unfreeze /system apps my update failed too (but i dont remember when).
Click to expand...
Click to collapse
MM the Music app problem is resolved.. but now the same thing happens but with "/system/lib/libGLESv1_CM.so"
...
Tequila.CZ said:
Going to give it a try.
Just to make sure, is this for WW version, right?
Click to expand...
Click to collapse
Yep.
Thanks.
Looking good., but got this error:
file "/system/app/EmailWidget.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/app/EmailWidget.apk", "5655101db862ccc0b2e60bd8ee276192f80e0ac7", "25adaa94e23e2aa87a7dd7f01956ccbabbb960fc")
assert failed: apply_patch_check("/system/app/EmailWidget.apk", "5655101db862ccc0b2e60bd8ee276192f80e0ac7", "25adaa94e23e2aa87a7dd7f01956ccbabbb960fc")
E:Error in /cache/dlpkgfile
Already got this before my update notification stopped working.
I deleted Email app, returned it back to system but seems I dont have the right version. (found in someones dropbox posted here)
Also reflashed Ww. 30 hoping this would overwrite the widget with correct version. Obviously it did not...
Would be glad for any help.
As it is MY dlpkgfile it can need MY files. I could upload /system, but first its strange to copy/paste whole android and second it is 624mb and third it will work only for rooted and at least fourth i updated my pad.
If it helps my pad was reflashed to .30 using wolfs method cos i had screen issue.
Sent using tf300t - stock JellyBean (rooted)
ch3mn3y said:
As it is MY dlpkgfile it can need MY files. I could upload /system, but first its strange to copy/paste whole android and second it is 624mb and third it will work only for rooted and at least fourth i updated my pad.
If it helps my pad was reflashed to .30 using wolfs method cos i had screen issue.
Sent using tf300t - stock JellyBean (rooted)
Click to expand...
Click to collapse
Could you please try to upload just the EmailWidget?
When I tried using OTA I got an error on Email.apk first. Then I downloaded it from dropbox and it passed. But EmailWidget did unfortunately not.
Also trying to find a tool that could extract the .30blob file. I guess the apps should be there. Found something but probably Linux only so no go for me.
You guys made my day! I had the red triangle and couldn`t get the update anymore. Tried everything, nothing worked.
Now I just followed your guide, dl. your files and all went fine.
So sad I was ony able to hit the Tanks-button once. Thank you thousand times!
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Here is emailwidget .apk and .odex but from jb not ics cos i didnt made a backup. But i think that it wasnt changed.
http://db.tt/cYSWYcXo
Sent using tf300t - stock JellyBean (rooted)
ch3mn3y said:
Here is emailwidget .apk and .odex but from jb not ics cos i didnt made a backup. But i think that it wasnt changed.
http://db.tt/cYSWYcXo
Sent using tf300t - stock JellyBean (rooted)
Click to expand...
Click to collapse
Oh man. I love you. Here I come on JB!
The EmailWidget was the missing piece.
Big thanks to rickykem, ch3mn3y and overyone who helped to create this workaround!
y17dt said:
You guys made my day! I had the red triangle and couldn`t get the update anymore. Tried everything, nothing worked.
Now I just followed your guide, dl. your files and all went fine.
So sad I was ony able to hit the Tanks-button once. Thank you thousand times!
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
+1:good:
Can someone post the original /system/lib/libGLESv1_CM.so pleeease...
Sent from my LG-P970 using xda premium
WIIstpM said:
Can someone post the original /system/lib/libGLESv1_CM.so pleeease...
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
I only have it from JB. Unfortunately it seems the file was updated together with the system so it will most probably be useless.
Don't have a libs backup from WW.30
WIIstpM said:
Can someone post the original /system/lib/libGLESv1_CM.so pleeease...
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
Here you go, from ICS:
http://db.tt/z5B5Q3jL
Trimis de pe ASUS Transformer Pad TF300T
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