I am trying to get a copy of the ADB binary found at /system/bin/adb on the Transformer and Transformer Prime.
All the original system dumps are dead (Megaupload/Multiupload are gone, and the mediafire and depositfile links are 404), and downloading the firmware from asus or other backups only provide a packed blob I don't have the tools to unpack.
This is a android/arm compiled version of the adb sdk tool. This is not the adbd daemon that is enabled by turning on usb development or adb over wifi. It actually lets you adb into other devices.
Can anyone share a copy from their Transformer?
Bump, noone?
Here's one from the Prime (the latest .21 build).
agentdr8 said:
Here's one from the Prime (the latest .21 build).
Click to expand...
Click to collapse
Is it zip file or renamed binary file.?
Says corrupted.
BTW, are these adb commands same as that of PC adb.?
Why don't you download a stock based ROM like Revolver or ARHD and extract adb?
ricardopvz said:
Why don't you download a stock based ROM like Revolver or ARHD and extract adb?
Click to expand...
Click to collapse
No problem mate, it is there in CM9, just saw it.
BTW i don't have Transformer prime, hence its rom is useless for me.
THe file is Error 404 :/
Related
Whenever I try to update, it will restart. Then an android with an orange progress bar will come up but in the middle, it will stop and the Android with the triangle with exclamation point inside would appear??
any solutions?
My version is in 3.2
What are you trying to update and how?
tweak89 said:
What are you trying to update and how?
Click to expand...
Click to collapse
I think I'm updating the tablet? I'm doing it OTA when I clicked check updates on the About Tablet area?
Are you running a stock system? Rooted? Any mods, kernels, custom recovery, buttons, languages, layouts, etc?
The update checks a lot of pieces before it will update the files, and if anything is different, it will fail.
sent from my cyanogen(mod) vision
gee one said:
Are you running a stock system? Rooted? Any mods, kernels, custom recovery, buttons, languages, layouts, etc?
The update checks a lot of pieces before it will update the files, and if anything is different, it will fail.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
I'm running stock but I do have it rooted. Other than that, nothing else. I haven't even flashed recovery.
How did you root? Which method? Homebrew?
The stock recovery might spit out a log file that will show you what is failing the update.
It's in /cache/recovery/log or maybe last_log.
You can use adb to pull it or copy it to your sdcard with a file explorer.
sent from my cyanogen(mod) vision
gee one said:
How did you root? Which method? Homebrew?
The stock recovery might spit out a log file that will show you what is failing the update.
It's in /cache/recovery/log or maybe last_log.
You can use adb to pull it or copy it to your sdcard with a file explorer.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
I used the root toolkit v7 that can be foundon the development section. I'm thinking that if I unroot the transformer, the update could work?
Or maybe if I just downloathe firmware from the asus website, will it work better? Though I don't know how to install it.
You have a few options:
1) find the recovery log and figure out what is causing the flash to fail. Replace the deviant file using your superuser powers.
Or
2) download the 8.6.5.9 stock firmware from ASUS and flash that, then perhaps the OTA will work.
Or
3) get freaky with the command line and cook up some insecure blobs or images to flash
I think option 2 would be easiest, although I don't know if it will wipe your data. The download is a zip file, which you unzip and copy your external sdcard. I think is should be a folder named ASUS/Update/some other zip. The whole folder structure gets copied to the external sdcard so that the ASUS folder is at the root of the ext sdcard. When you insert it into the slot, your TF will recogize it and ask you if you want to flash it.
At some point ASUS will probably release the full stock rom on their website and you can flash that to update to the latest and greatest.
sent from my cyanogen(mod) vision
gee one said:
You have a few options:
1) find the recovery log and figure out what is causing the flash to fail. Replace the deviant file using your superuser powers.
Or
2) download the 8.6.5.9 stock firmware from ASUS and flash that, then perhaps the OTA will work.
Or
3) get freaky with the command line and cook up some insecure blobs or images to flash
I think option 2 would be easiest, although I don't know if it will wipe your data. The download is a zip file, which you unzip and copy your external sdcard. I think is should be a folder named ASUS/Update/some other zip. The whole folder structure gets copied to the external sdcard so that the ASUS folder is at the root of the ext sdcard. When you insert it into the slot, your TF will recogize it and ask you if you want to flash it.
At some point ASUS will probably release the full stock rom on their website and you can flash that to update to the latest and greatest.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Owww. so 8659 is not the latest but the one on OTA? Will I lose root if flash that? and does root work on the newest update?
Yes, you will lose root and any custom recovery if you flash the stock image from the ASUS website. I think the tools in the dev section will still root as long as you have SBK v1 I.e., nvflash works on your tf. You rooted once, so it should be fine.
Hello,
i would like flash CWM on my TF101G so i can flash a rom. I have it rootet with ViperMod but what´s the next? I have testet nvflash but it´s fail. My serialnumber begins with BA0. What can i do?
With my Galaxy S2 that´s all so easy and with the Transformer so difficult
Sorry for my bad english, i´m from germany.
Not difficult at all, everything is there jsut have to do a little research.
RecoveryInstaller
http://forum.xda-developers.com/showthread.php?t=1346180
Thank you for your help but i can not install this apk it´s parsingerror
silence84 said:
Thank you for your help but i can not install this apk it´s parsingerror
Click to expand...
Click to collapse
try re downloading it or make sure that you are rooted
Titanium Backup says i have root. Loaded again but same error. I have Android 3.0.1 on the Tablet could be this the reason?
silence84 said:
Titanium Backup says i have root. Loaded again but same error. I have Android 3.0.1 on the Tablet could be this the reason?
Click to expand...
Click to collapse
Yeah, update to the latest firmware. It should work after that.
Try OTA Root Keeper (it might save your root so you don't have to root again).
IF not just update, run ViperMod again and install RecoveryInstaller
I can not flash the update. I put the Update on the SD, the system dedects also the update but after the restart the update breaks and the system restart again.
I desperate slowly
Did you extract the file you download to get to the zip file inside? You also have to rename that extracted file. I cant recall exactly what it need to be rename to but I'll check soon as i get near a PC
baseballfanz said:
Did you extract the file you download to get to the zip file inside? You also have to rename that extracted file. I cant recall exactly what it need to be rename to but I'll check soon as i get near a PC
Click to expand...
Click to collapse
"EP101_SDUPDATE.zip" i think this is what you have to rename the file
edit: Tips from Baseballfanz For those not able to get it working, a few things to check.
1-Make sure you actually extract the WW_epad-user-8.6.x.x.zip within the zip. Inside the file you download is an Asus folder, inside that is an Update folder, inside that is the WW_epad-user-8.6.x.x.zip file you'll be working with.
2-When renaming, if your PC is set to "hide known extension", you'll not see the .zip so if you type in .zip you'll get filename.zip.zip The file manager on the TF should show you the extension
3-Make sure it's on the root of the sd card and not within any folder.
4-Check spelling of files WW_epad-user-8.6.x.x.zip EP101_SDUPATED.zip
5-Micro sd card is in FAT32 format. Try a different card or format again (after saving your stuffs)
6-File manager on the TF sdcard is internal and Removable/MicroSD is the external sd card.
THESE ARE TIPS FROM BASEBALLFANZ POST SOMEWHERE ELSE ONLY I X'ED OUT THE FIRMWARE NUMBER TO DENOTE THE NEWEST FIRMWARE.... HOPE YOU DNT MIND
Thank you very mutch for your help. I have the last update installed 8.6.6.23 but i can this not rooted. ViperMod no longer works.
YYYEEEEAAAAHH
I have root with nachoroot. CWM is already on it. Many thanks again!
That's good to hear.
Hello, been around here just haven't posted yet. Anyways, I have a S/N: B70KAS420184 pad, on the .19 firmware, no rom, successfully rooted with razorclaw and clockwork running fine. I messed up flashing the ICS file and now I cant get anywhere. Entering recovery shows a status bar then instantly to the triangle with droid guy with exclamation point. It also will not get past the main eee pad screen and just hangs there. I tried nflash and when I run the download.bat (windows) the command prompt comes up, reads a few lines real fast then closes and the nvidia usb boot recovery disappears from the device manager list. Any help would be great please I've searched for everything. Tried this on two different computers, same result. Both running windows 7. Thanks, Josh.
Exact same problem here too. Tried putting stock firmware on SD card then hopefully it would install itself but to no avail.
Suggestions?
tomar5e said:
Exact same problem here too. Tried putting stock firmware on SD card then hopefully it would install itself but to no avail.
Suggestions?
Click to expand...
Click to collapse
I've seen the problem come up but have yet to see any sort of answer.
Jwezesa said:
I've seen the problem come up but have yet to see any sort of answer.
Click to expand...
Click to collapse
As far as I understand it with other devices, you can't flash a factory update.zip if you have custom recoveries (or at least shouldn't, because it would brick the device).
Is there any way to flash a recovery like others can do with nvflash?
tomar5e said:
Is there any way to flash a recovery like others can do with nvflash?
Click to expand...
Click to collapse
If your B70 is one of the earlier batches with sbk1, you can use NVflash.
Mine is B70KAS1796**. NVflash works.
Download the latest firmware from asus ( http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download )
unzip on computer
copy asus folder to Microsd
Copy file from /asus/update to root directory
rename updatelauncher file to EP101_SDUPDATE
reboot to recovery (power and volume down wait for words then volume up)
might help works for me (i have B70 not able to nvflash)
Sent from my Transformer TF101 using Tapatalk
Dreamboxuser said:
Download the latest firmware from asus ( http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download )
unzip on computer
copy asus folder to Microsd
Copy file from /asus/update to root directory
rename updatelauncher file to EP101_SDUPDATE
reboot to recovery (power and volume down wait for words then volume up)
might help works for me (i have B70 not able to nvflash)
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Unfortunatley Dreambox i have tried that but all i get is the triangle of doom. I think my recovery may be broken, and u have the later model tf101 (i think) so nvflash doesnt work for me. I install drivers for it then open download and it just flicks to a screen real quick then closes. Is that what is supposed to happen if you have the later model tf101?
thanks again.
Hmmm could be a problem with recovery but... could be a problem with the zip file.
As i am on a late model b70 as well i have been stuck a few times like that as well.
just to double check because these are the things that got me when i was stuck
did you unzip the downloaded file and copy the /asus/update/updatelauncher.... to the sd card
did you rename the file (update launcher) to EP101_SDUPDATE (this is case sensitive) and put it in the root of the SD card
Reboot to recovery volume and power down then when you see text in the top left corner press volume up?
anyone of these steps missed would cause the android with the triangle
Edit: If it boots to eee pad logo you should be able to save it. The only things that would give you the triangle would be the above and possibly wrong region code
Dude it worked, thanks heaps for that. Turns out i didnt unzip the file from the Asus website. I just assumed that was the ROM *facepalm*
Good job mate, i was nearly going to turf the tf101 and use that as an excuse to get the prime lol
No problem. Sorry about saving it tho...... Guess yer prime is gonna have to wait.
Im not seeing the update launcher file in the update folder. My update fold just has a zip file (US_epad-user8.6.5.21.zip) When I unzipped that, there are a few files and the google folder, within that folder, the only thing I have with udpate is update_binary and updater_script? Where is the updatelauncher file? Thanks
Jwezesa said:
Im not seeing the update launcher file in the update folder. My update fold just has a zip file (US_epad-user8.6.5.21.zip) When I unzipped that, there are a few files and the google folder, within that folder, the only thing I have with udpate is update_binary and updater_script? Where is the updatelauncher file? Thanks
Click to expand...
Click to collapse
Yep that is the one. Sorry wrong file name. Copy the asus/update folder So copy (US_epad-user8.6.5.21.zip) that to the root directory and rename it to EP101_SDUPDATE reboot into recovery and you should be in back in honeycomb.
So on the microsd you should have
Asus/update/ US_epad-user8.6.5.21.zip
EP101_SDUPDATE.zip
Plus all your other files
Sent from my Transformer TF101 using Tapatalk
I did this and when I boot into recovery (vol - & power them vol +) it shows the status bar like its going to install something for about 1 second then instantly to the triangle.
Did you make sure you unzipped the downloaded file.
Copied the ww.epad-user8.6.5.21 to root and renamed to EP101_SDUPDATE
These things can block you from proper recovery
Sent from my Transformer TF101 using Tapatalk
Edit: should say US instead of ww
I downloaded the zip file. Unzipped the file and I now have an ASUS folder within that is an update folder with the zip file I mentioned before. I copied the whole asus folder to the main root of a clean formated sd card. I copied the zip in the update folder and moved it to the main root of the card where the asus folder is. I renamed and ran recovery, same triangle...I am trying another sd card right now.
EDIT: With clean and new sd card it is now showing the status bar. Not sure how long this takes but good sign that it didn't go straight to the triangle! If this works I owe you a beer! Thanks so much
No problem
Have fun
Edit: It could take a while and it might stall but just be patient it should go through.
Sent from my Transformer TF101 using Tapatalk
Dreamboxuser said:
Hmmm could be a problem with recovery but... could be a problem with the zip file.
As i am on a late model b70 as well i have been stuck a few times like that as well.
just to double check because these are the things that got me when i was stuck
did you unzip the downloaded file and copy the /asus/update/updatelauncher.... to the sd card
did you rename the file (update launcher) to EP101_SDUPDATE (this is case sensitive) and put it in the root of the SD card
Reboot to recovery volume and power down then when you see text in the top left corner press volume up?
anyone of these steps missed would cause the android with the triangle
Edit: If it boots to eee pad logo you should be able to save it. The only things that would give you the triangle would be the above and possibly wrong region code
Click to expand...
Click to collapse
Works for the B60 too. Thanks for this! I knew as soon as I reflashed .21 from .19 that I had killed my recovery. I tried EVERYTHING I could think of to get it back and just didn't work. Glad I found this because I hadn't even thought about putting the EP101_SDUPDATE on the SD card.
Cheers!
Hi there. I try to install Asus Mynet app on another tablet (Nexus 7) but copying .apk and .odex files did not do the job. Is there another way to install? Thank you.
Sent from my ASUS Transformer Pad TF700T
It's possible that it only works on ASUS firmware. As each stock ROM is different from device to device.
Also, It could be that asus uses some sort of app framework. If they do, then you probably need to install it.
megamoz said:
Hi there. I try to install Asus Mynet app on another tablet (Nexus 7) but copying .apk and .odex files did not do the job. Is there another way to install? Thank you.
Sent from my ASUS Transformer Pad TF700T
Click to expand...
Click to collapse
You won't be able to copy the .odex file to the nexus 7 as the frameworks are different. You need to use the DEODEX version of mynet and copy that.
Either find a version of the ASUS Apps or download CROMI from my sig and extract it from there.
Here you go: https://www.dropbox.com/s/4ep95fr17d6cvc2/MyNet.apk
MartyHulskemper said:
Here you go: https://www.dropbox.com/s/4ep95fr17d6cvc2/MyNet.apk
Click to expand...
Click to collapse
I just tried downloading your link to the MyNet.apk file and it downloaded fine but when I click on the file to install it it fails.
Any suggestions.
SiriusDoggy said:
I just tried downloading your link to the MyNet.apk file and it downloaded fine but when I click on the file to install it it fails.
Any suggestions.
Click to expand...
Click to collapse
You can't install it like a normal apk as it will be signedprotected (?) differently.
You can insert it into your systm/app folder and change the permissions to the same as other system apps using root explorer or es file explorer - it might work that way. Remember to reboot after.
sbdags said:
You can't install it like a normal apk as it will be signedprotected (?) differently.
You can insert it into your systm/app folder and change the permissions to the same as other system apps using root explorer or es file explorer - it might work that way. Remember to reboot after.
Click to expand...
Click to collapse
Nope, tried that and it still doesn't work. BTW - the permissions were already the same as other apps.
Thanks for the idea though...
I have followed everything to a 't' and took the jb image 'renamed it' to (basically took out jb and kept 'recovery' and '.img') IS THAT CORRECT?
and when I ran the command for the image recovery it says image not found.
I even tried TWRP image and renamed... Same problem-
I know I posted some stupid stuff and I apologize - i have read a lot more into rooting and figured a lot out, but this is am @ a loss... Not sure what else to...
I plead for help
ganggreen777 said:
I have followed everything to a 't' and took the jb image 'renamed it' to (basically took out jb and kept 'recovery' and '.img') IS THAT CORRECT?
and when I ran the command for the image recovery it says image not found.
I even tried TWRP image and renamed... Same problem-
I know I posted some stupid stuff and I apologize - i have read a lot more into rooting and figured a lot out, but this is am @ a loss... Not sure what else to...
I plead for help
Click to expand...
Click to collapse
the image file needs to be in the same place that you are running fastboot from. for example i have C:/andriod abd where all my adb/fastboot drivers and .exe and such are and to flash a blob/img file i must put the file in that same folder because thats where fastboot looks for the blob/img.
ide bet money that this is your problem. and what fastboot command are you using? It would be helpful if you could be more descriptive of the steps you have tried
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
markymark567 said:
the image file needs to be in the same place that you are running fastboot from. for example i have C:/andriod abd where all my adb/fastboot drivers and .exe and such are and to flash a blob/img file i must put the file in that same folder because thats where fastboot looks for the blob/img.
ide bet money that this is your problem. and what fastboot command are you using? It would be helpful if you could be more descriptive of the steps you have tried
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
BTW-THANKYOU soo much for hekping
I will put more information up and pics to help-people see what I see and are doing
I actually made a file folder (I saw it on a YouTube video) and put all of the files needed for the recovery;for example
"rocovery1"=file folder (in c drive) and that folder includes the two(2) adb(.dll) files / the fastboot file (but my 'fastboot' file doesn't have an exe after it) does that matter-/and then of course the image file... ALL OF THAT IS IN A folder I named... should I have not done that? If not where would I find my adb files? Better yet how are they supposed to be listed?
Sent from my Galaxy Nexus using Tapatalk 2
ganggreen777 said:
BTW-THANKYOU soo much for hekping
I will put more information up and pics to help-people see what I see and are doing
I actually made a file folder (I saw it on a YouTube video) and put all of the files needed for the recovery;for example
"rocovery1"=file folder (in c drive) and that folder includes the two(2) adb(.dll) files / the fastboot file (but my 'fastboot' file doesn't have an exe after it) does that matter-/and then of course the image file... ALL OF THAT IS IN A folder I named... should I have not done that? If not where would I find my adb files? Better yet how are they supposed to be listed?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
FYI
Asus uses .blob NOT .img
Even if it's CWM or TWRP (either one would be '.blob') NOT '.img' - either one?
Sent from my Galaxy Nexus using Tapatalk 2
ganggreen777 said:
Even if it's CWM or TWRP (either one would be '.blob') NOT '.img' - either one?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Recovery is through fastboot, and fastboot for asus requires .blob. So yes, its blob irregardless.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
I AM ROOTED!
Sent from my Galaxy Nexus using Tapatalk 2