Related
***THIS INSTALLER IS ONLY FOR WINDOWS***
Hey Guys!
I have recently seen a lack of network tools that are available for terminal usage on Android. I recently found an app called dSploit that contains all of the primary network tools for android, so I decided to separate them from the package and make them available in a standalone format. So, I present to you:
NetworkTools for Android!
This package includes:
- arpspoof
- ettercap
- hydra
- tcpdump
- all required library files
Prerequisites:
1. A rooted android phone
2. The correct ADB drivers for your phone
Installation:
1. Unpack the NetworkTools compressed folder
2. Run Install.bat
3. Follow the instructions
4. Enjoy!
DOWNLOAD: View attachment NetworkTools.zip
You can contact me with any questions or concerns.
LK
What really one will use this for?
usb to ethernet adapter apk
Hi,
I've been already both a Usb to lan from CD-r king where I tried to use for configuration on my modem/ router but does not work 'coz as per verifying my note ll on netcfg, the ip add still 0000. Please have advise if I need to install the corresponding software driver for the usb to lan adapter.
Thank you,
Great
Thanks so much man, you simply rock.
I only had one problem, it was that adb couldn't have root access to my phone.
For future users, in order to do that go to settings -> development options and enable root access for Applications AND adb (well at least that's how it is on CyanogenMod 10).
Again, great job.
Cya!
Nycryptic said:
***THIS INSTALLER IS ONLY FOR WINDOWS***
Hey Guys!
I have recently seen a lack of network tools that are available for terminal usage on Android. I recently found an app called dSploit that contains all of the primary network tools for android, so I decided to separate them from the package and make them available in a standalone format. So, I present to you:
NetworkTools for Android!
This package includes:
- arpspoof
- ettercap
- hydra
- tcpdump
- all required library files
Prerequisites:
1. A rooted android phone
2. The correct ADB drivers for your phone
Installation:
1. Unpack the NetworkTools compressed folder
2. Run Install.bat
3. Follow the instructions
4. Enjoy!
DOWNLOAD: View attachment 1886684
You can contact me with any questions or concerns.
Click to expand...
Click to collapse
Just found this. Hydra? Wow, I'm impressed. Nice work, sir!
Thanks dude, it works great
makeing some system problems
Nycryptic said:
***THIS INSTALLER IS ONLY FOR WINDOWS***
Hey Guys!
I have recently seen a lack of network tools that are available for terminal usage on Android. I recently found an app called dSploit that contains all of the primary network tools for android, so I decided to separate them from the package and make them available in a standalone format. So, I present to you:
NetworkTools for Android!
This package includes:
- arpspoof
- ettercap
- hydra
- tcpdump
- all required library files
Prerequisites:
1. A rooted android phone
2. The correct ADB drivers for your phone
Installation:
1. Unpack the NetworkTools compressed folder
2. Run Install.bat
3. Follow the instructions
4. Enjoy!
DOWNLOAD: View attachment 1886684
You can contact me with any questions or concerns.
Click to expand...
Click to collapse
i installed it and everthing works greet
but after i installed it when i try to reboot
my phone not booting and i need to format /system
also after installing when trying to tern wifi on it's
not working
can someone help me
I'm getting the same problem with my xperia t
Can you create an uninstaller? I installed it and resulted in a bootloop. My phone is the Samsung Galaxy Note 3 Neo SM-N750, running on Pac-Man rom.
plz help....
Could you please provide etterfilter and also how can we inject java-script using etercap
After doing this
my phone stucks in boot loop
volumeup+power button not working help
my phone is zenfone 5 rr rom
My phone got in boot loop as well.. Does anyone know how to fix that?
Thanks
rdegelo said:
My phone got in boot loop as well.. Does anyone know how to fix that?
Thanks
Click to expand...
Click to collapse
You need to reflash your stock firmware or reboot from backup if you created one.
Hİ brother I install the this pack, but I have a questions. "how to use this programs"
a orginally Hydra or Ettercap commads is work or we use a another commads?
and what must terminal use ? a android terminal or termux ??
arpspoof error: Android 5.0 and later only support position-independent executables
I got this message when try to run it
"arpspoof": error: Android 5.0 and later only support position-independent executables (-fPIE).
rdegelo said:
My phone got in boot loop as well.. Does anyone know how to fix that?
Thanks
Click to expand...
Click to collapse
I just had the same problem. Here is how I fixed it without reflashing the rom:
1) I extracted libcrypto.so and libssl.so from my rom installation zip and copied it to my phone storage
2) in recovery (I used orangefox and terminal), copy and replace these two files to /system/lib/
3) reboot your phone
I also removed the binaries arpspoof, ettercap, etterfilter, etterlog, usernames, tcpdump, hydra in /system/bin and libraries libgif.so, libltdl.so, libssh.so, libpcap.so in /system/lib but I don't think these are reason behind the boot loop.
Hello,
i have been reading guides all the day and no-one had a solutions to my problems so i would like to write my own to help out others who are encountering my same issues.
----------------------------------------------------------------------------------------
This guide is for Windows and explains everything you need to update your Nexus 7 (2013) Wifi (flo) from 4.3 JSS15R to 4.4 KRT16O
----------------------------------------------------------------------------------------
1) disconnect table from USB cables if it is connected to the pc
2) go http://developer.android.com/sdk/index.html and download the SDK
3) unzip the SDK in C\
4) go in C:\adt-bundle-windows and start the SDK Manager
let is load and scan for all possible updates.. when it has finished click on Deselect All then choose only these to packages:
Tools --> Android SDK Platform Tools
Extra --> Google USB Driver
if the Android SDK Platform tools are updated then you will only have 1 package to download else you will see Install 2 Packages, click it, then select Accept Licence and click Install.. wait it to finish and then close
5) let's now download the factory image
Nexus 7 2013 only WIFI (flo) "razor" is here: https://developers.google.com/android/nexus/images#razorkrt16o and download the first link of the page (4.4 (KRT16O) Link)
Nexus 7 2013 MOBILE/LTE (deb) "razorg" is here: https://developers.google.com/android/nexus/images#razorgkrt16o and download the first link of the page (4.4 (KRT16O) Link)
for some reason the MD5 checksum and SHA1 for the flo version dont match but i read people have been able to install this image anyway (i installed the OTA so i did'nt try this install)
unzip the downloaded file and you should get a .tar file.. unzip it again and you should get a bunch of files.. i got the following ones:
1)bootloader-flo-flo-03.14.img
2)flash-all.bat
3)flash-all.sh
4)flash-base.sh
5)image-razor-krt16o.zip
place all these files in C:\adt-bundle-windows\sdk\platform-tools\
6) now let's install the drivers correctly and flash the update
First thing, keep the Nexus 7 not connected to the USB cable. Then switch it on and go into Settings --> Storage click on the Options and choose USB computer connection and make sure to have the CAMERA (PTP) selected.
Now go into developer options and select Stay Awake and USB Debugging
Go back to the home screen and connect the tablet to the PC.. let the PC try to install it by himself.
Now press WINDOWS+R and run devmgmt.msc
If you see a device called Nexus 7 with a yellow sign then right click on it and choose Update software driver.
Then select the second option (find a driver on the computer), then select the second option (choose manually a driver from a list), now click first option (show all the devices), then click Driver disk button, then browse to C:\adt-bundle-windows\sdk\extras\google\usb_driver\ and choose android_winusb.inf and do ok.
The box should fill with a device called Android Composite ADB Interface, choose that and do next
To check if you have done right do:
WINDOWS+R and run cmd
in cmd do cd.. until you get into C:\
then do cd adt-(tab) to autocompile and enter
then do cd sdk enter
cd platform-tools enter
adb.exe devices enter
the daemon should start and you should get a list of devices attached showing you a code made of numbers and letters.. this is your nexus 7.
if cmd says the device is unauthorized then look at your tablet and allow the computer to operate
let's now install the driver also in fastboot so to do this always in cmd type
adb.exe reboot-bootloader
the tablet will reboot into the bootloader and you will see an android with the open tummy
now inside the command prompt window run the following commands:
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
fastboot -w update image-razor-krt16o.zip
if everything has gone right you should have updated using the factory image and the tablet should reboot by now...
else continue reading:
if you had any issues we can then try to update through OTA which means you will need to download another package
the nexus 7 ONLY WIFI OTA: http://android.clients.google.com/p....signed-razor-KRT16O-from-JSS15R.3a3951e8.zip
not sure if the nexus 7 LTE OTA url has been released or not because i can't find it.. if anyone has the link and can point it out to me i would be glad to add it here
download it and place it always in
C:\adt-bundle-windows\sdk\platform-tools\
rename it to something easier and redo
adb.exe sideload ota_zipfilename (enter)
everything should go fine now, so it will reboot.. configure the tablet again if it is the case
7) changing recovery
download latest recovery from here http://techerrata.com/browse/twrp2/flo
place the download img into C:\adt-bundle-windows\sdk\platform-tools\
then reboot to bootloader using adb or simply switch the table on keep vol down down
in cmd type
fastboot.exe flash recovery recoveryimagefile
8) rooting the tablet
btw sideloading the zip for rooting requires a custom recovery such as TWRP so step 7 must be achieved in order to root this way
download the latest superSU from here http://download.chainfire.eu/supersu
go into recovery mode passing by the bootloader
do another adb sideload passing this time the zip for supersu
everything done hopefully
hope this helps others which had issues with drivers and had issues with the original factory image 4.4 (KRT16O) giving the E: signature verification failed
Great guide!
The package for the link https://developers.google.com/android/nexus/images#razorkrt16o fails verification for me as well and does not install once its side loaded. So it's probably beneficial to just point to the other link.:good:
haet said:
Great guide!
The package for the link https://developers.google.com/android/nexus/images#razorkrt16o fails verification for me as well and does not install once its side loaded. So it's probably beneficial to just point to the other link.:good:
Click to expand...
Click to collapse
The factory image isn't meant to be side loaded. It needs to be installed using fastboot/bootloader.
If I understand this correctly, it fails because ADB sideload is intended for zips and not image files.
If you use the flash_all.bat (or whatever it is, slips my mind at the moment) it will flash a complete factory image.
The zip on the other hand is intended for sideloading and should update the OS no problem.
cincibluer6 said:
If I understand this correctly, it fails because ADB sideload is intended for zips and not image files.
If you use the flash_all.bat (or whatever it is, slips my mind at the moment) it will flash a complete factory image.
The zip on the other hand is intended for sideloading and should update the OS no problem.
Click to expand...
Click to collapse
Gotcha.
There is quite a size difference between the the zip and the tgz format. Is this only because of compression format? Or is it more beneficial to flash one over the other?
cincibluer6 said:
If I understand this correctly, it fails because ADB sideload is intended for zips and not image files.
If you use the flash_all.bat (or whatever it is, slips my mind at the moment) it will flash a complete factory image.
The zip on the other hand is intended for sideloading and should update the OS no problem.
Click to expand...
Click to collapse
There are zips and then there are ZIPS
It isn't the type of archive that is critical but the contents of the zip. Zip is just a generic archive format and can store anything.
The OTA zips include specific content. In particular they are
signed by google
include an install script to handle patching, replacing files, and setting up permissions
include an install utility to run the script
include individual patch files
include whole files if the patches would be too large
have a specific directory structure where everything is supposed to be located
The factory images are also delivered in an archive. They are first archived in a tar format, which just collects a bunch of files and doesn't compress. Then they are gzip'd which is a Gnu archiver which performs a similar job to zip, but uses a different format and algorithm. Within the original tar archive there is also a zip archive. That zip contains images of the kernel, recovery, rom, user and data partitions, but it doesn't include the aforementioned items that make a zip into an OTA-style zip.
The factory images are NOT meant to be flashed in recovery. Recovery will be expecting the stuff above that OTA-style zips have. If you try to flash the factory image, the first point of failure is the signature verification fails, because it isn't signed (and even if it were signed, it wouldn't be signed in the way recovery is expecting)
So what is the difference between flashing via Recovery and the OTA-style zip vs running flash-all and the factory image?
The OTA-style flash will go and examine each file it needs to patch to make sure it is stock JSS15R. It must do this because it doesn't have the complete KRT16O file, only a patch (difference between the JSS15R and KRT16O versions of the file) that only makes sense if applied to the original JSS15R file. Even if there is a one space difference in the file, the patch would fail.
Since the OTA-style patches files (in general) it will leave files you have added in place. In particular the files installed to keep root are left in place and so are apps, sounds, images, etc. you added to the ROM (/system) partition. So you ask why do you lose root? You don't lose the root files that were installed, they are neutered because at the end of the OTA-style install, it resets the permissions in all the directories to what they are supposed to be. This drops the special permissions you gave the root files to do their job. Also the OTA-style patch does not directly overwrite your recovery. Upon first boot, there is a script that runs which builds the new recovery using the installed kernel. This is why if you immediately (prior to reboot) run the SuperSU install script after the installation of the OTA-style update.zip, you can restore root and keep your recovery. The SuperSU install script replaces the script that builds the new recovery, with its own file. It also reinstalls and sets the permissions on the root files. So in effect, you have root and have prevented stock recovery from being installed over your custom recovery.
The Recovery that you use to run the OTA-style update.zip is just special program that boots up on the linux kernel and accepts certain actions. The source code for Recovery along with the kernel is published. People can easily replace Recovery with their own custom program and that is why you have custom recoveries.
The factory images on the other hand install through the bootloader. This is a low-level program similar to BIOS on PCs. It has more limited functions and the code is proprietary. It is harder to do custom bootloaders because the source code isn't published.
The bootloader has a more limited set of functionality and you communicate with bootloader using a different program called fastboot.
The bootloader expects the files you give it to be .img files or you can give it a zip archive full of .img files. These are not patches of files like the OTA. These are complete images to replace the existing partitions. It is like a Norton Ghost image (factory image style) of your entire hard drive vs an incremental backup (OTA-style) of just the files that changed.
Given they are full images, they will overwrite the partitions completely so anything you had on them before is wiped out and overwritten.
Also full images are always larger than OTA patch-style updates because they contain everything rather than just the changed file patches.
By default they use the -w option in the fastboot install instructions, which will wipe your user data as well, but you can remove the -w option and keep your user data, though there are always a small percentage of upgrades where it won't work to keep your user data (same with the OTA).
Anyway that is just a brief summary. There are many more details and nuances I didn't list.
^^ I won't go ahead and quote you but thanks for the full on summary. I knew what .tgz was and all that (using Linux for a few years now) but I'm new to most of the Android like stuff.
Thanks for clarifying and explaining it so well.
Just gave the sideload of SuperSU a shot and was given two errors:
failed to verify whole-file signature
signature verification failed
haet said:
Just gave the sideload of SuperSU a shot and was given two errors:
failed to verify whole-file signature
signature verification failed
Click to expand...
Click to collapse
You cannot sideload the SuperSU update.zip using stock recovery because it isn't signed by Asus/Google.
It is signed, but using a generic cert.
You need to use custom recovery like TWRP or CWM to install it. You can use their menu system to choose the file or if they have sideload, you can sideload using custom recovery.
sfhub said:
You cannot sideload the SuperSU update.zip using stock recovery because it isn't signed by Asus/Google.
It is signed, but using a generic cert.
You need to use custom recovery like TWRP or CWM to install it. You can use their menu system to choose the file or if they have sideload, you can sideload using custom recovery.
Click to expand...
Click to collapse
Makes sense. Thanks for the help!
Windows 2008 server usb drivers?
This guide was great, and everything worked fine until I reboot into recovery and choose to adb sideload an image. Then, the device doesn't get recognized, and the google drivers don't work. So, I can't see the device with the ADB interface driver.
Does any have experience with this? Am I out of luck? I couldn't find anyone talking about drivers for windows server 2008 anywhere -- but usually win7 drivers work fine -- just not here.
I don't have another windows installation anywhere, so if there isn't an answer, I will just have to wait for OTA
** UPDATE **
I found some universal drivers from Koushik Dutta: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Those drivers worked! Then I used the OTA download (your second option), sideloaded it, and got the update. Now running KitKat, so thanks a bunch! hopefully someone else will find this driver option useful.
I'll give those universal drivers a go. Hell, I've tried everything else on the Internet with complete failure. One last try before I give up.
Sent from my SM-P600 using XDA Premium HD app
jbwray said:
This guide was great, and everything worked fine until I reboot into recovery and choose to adb sideload an image. Then, the device doesn't get recognized, and the google drivers don't work. So, I can't see the device with the ADB interface driver.
Does any have experience with this? Am I out of luck? I couldn't find anyone talking about drivers for windows server 2008 anywhere -- but usually win7 drivers work fine -- just not here.
I don't have another windows installation anywhere, so if there isn't an answer, I will just have to wait for OTA
** UPDATE **
I found some universal drivers from Koushik Dutta: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Those drivers worked! Then I used the OTA download (your second option), sideloaded it, and got the update. Now running KitKat, so thanks a bunch! hopefully someone else will find this driver option useful.
Click to expand...
Click to collapse
You sir are a genius (and the driver author). I had the exact problem and looked everywhere. I am low tech, too. So following these two guides;
http://phandroid.com/2013/11/13/how-to-install-kitkat-nexus-7/
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
I am now on 4.4. And everything is intact. Thank you!
I also ran into Google USB driver problems after the Nexus dropped into recovery mode. So I gave up trying to use Windows 8 and switched over to using Ubuntu workstation. Getting ADB to run on Ubuntu is very easy and so flashing the Kit Kat OTA file was a breeze.
On Ubuntu there's no need to install the full SDK just to get ADB and Fastboot; the process is outlined here: http://forum.xda-developers.com/showthread.php?t=1860108. From there it's just simple command line entries from a terminal i.e. "adb devices."
I was disappointed to see Google has kept the black top and bottom bars for tablets. I usually run Teslacoil's launcher and installed their beta launcher with transparent bars a welcome relief.
doorunrun said:
I also ran into Google USB driver problems after the Nexus dropped into recovery mode. So I gave up trying to use Windows 8 and switched over to using Ubuntu workstation. Getting ADB to run on Ubuntu is very easy and so flashing the Kit Kat OTA file was a breeze.
On Ubuntu there's no need to install the full SDK just to get ADB and Fastboot; the process is outlined here: http://forum.xda-developers.com/showthread.php?t=1860108. From there it's just simple command line entries from a terminal i.e. "adb devices."
I was disappointed to see Google has kept the black top and bottom bars for tablets. I usually run Teslacoil's launcher and installed their beta launcher with transparent bars a welcome relief.
Click to expand...
Click to collapse
If you install the latest Google search apk and GEL from the nexus 5, you will have transparent nav bar.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using Tapatalk 4
Hi. This will wipe the device right? We should have a backup before proceeding?
ganstar said:
You sir are a genius (and the driver author). I had the exact problem and looked everywhere. I am low tech, too. So following these two guides;
http://phandroid.com/2013/11/13/how-to-install-kitkat-nexus-7/
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
I am now on 4.4. And everything is intact. Thank you!
Click to expand...
Click to collapse
You should also know that Google has drivers as well located at http://developer.android.com/sdk/win-usb.html, which is what you would have downloaded right after you installed the SDK package.
For those who can't get their devices recognised even after doing everything correctly. Just boot the tablet and change from MTP to PTP. Worked for me.
Sent from my Nexus 7 (2013)
I was on PTP. still didn't work
BreakShadow said:
For those who can't get their devices recognised even after doing everything correctly. Just boot the tablet and change from MTP to PTP. Worked for me.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I was on PTP. Still didn't work until I found those drivers. The drivers from Google were what I was using, but they didn't support the device in fastboot mode for the version of windows I was using. (2008 server R2)
haet said:
You should also know that Google has drivers as well located at http://developer.android.com/sdk/win-usb.html, which is what you would have downloaded right after you installed the SDK package.
Click to expand...
Click to collapse
I had those, they didn't work for me, as others have noted as well.
LENOVO ROM DOWNLOADER V5.0 by robterza (Outdated. use LENOVO K3 WORKSHOP V2.X instead.)
This app is for official Marshmallow (6.0) Lenovo Roms ROW-DEV-ST. (K50a40-K50T5).
* Can backup the Stock Roms and restore back for OTA updates 100%
* Can Flash your favorite Custom Roms as well.
* Can root and unroot , and add you favorite apps by zip package
* Can backup your apps before flashing a new Rom and restore them after flash.
* Can backup your NVRAM partition.
* Can flash your personal Custom Recovery. (TWRP is the default).
* Can download Lenovo roms by a rom list.
This is my personal app that i use to mod my K3 Note. Made in html (hta) and vbscript.
It is not perfect like a professional one, maybe there are some bugs, but it does the dirty job.
what we do by hand, it does with some clicks.
VIDEO TUTORIAL tips: They are of the previous version REV4.4 But very similar to version 5.0
=========================================================================
NEW 14/09/2016
LENOVO ROM DOWNLOADER V5.0 Voice assistant
DOWNLOAD: GOOGLE DRIVE
[INSTALL] COPY or OVERWRITE THE "Lenovo_K3_Rom_Downloader" FOLDER IN C:\
DONE.**
PATCH to V5.1 27/09/2016 (READY FOR DOWNLOAD)
[INSTALL] COPY or OVERWRITE THE "Lenovo_K3_Rom_Downloader" FOLDER IN C:\
DONE.**
**************************************************************************************************
Update for LENOVO ROM DOWNLOADER V5.x/5.1
Download only through, the "UPDATE" button in application
UPDATE to V5.2 16/10/2016 (New)
V5.2 PatchFix 26/10/2016 (New)
**************************************************************************************************
TIP: YOU DONT NEED PATCHED BOOT IMG. THE APP, PATCHES THE BOOT IMG, ON the FLY.
* Pc Minimum Screen Res 1024X768. Windows Xp/Vista/Seven/8/10.
* Mandatory sound card on PC.
**************************************************************************************************
Pc DRIVERS:
-> VCOM and how to install
-> Lenovo USB For K3 Note
Another Voice TextToSpeech HERE:
**************************************************************************************************
FAST GUIDE FOR BEGINNERS
Frequently Asked Questions:
Q. My AntiVirus program says the app may be harmful.
A. The exe files I compiled are not digitally signed with a Microsoft certificate, so certain AntiVirus programs will pick it up as potentially harmful when it is not. They will pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.
Q. While I was trying to unroot during flashing stock boot.IMG, I can't find stock boot.img file in the app.
A. Click "Update" button, and you can download your stock boot.img from MegaDrive. Download them in right folders of the app for easy find. Example: "STOCK_S433_boot.img" in the "K50a40StockBoot" folder.
Q. I am on Stock , what is the first step for rooting?
A. First step before rooting is make "Stock Backup"(you need for OTA Update) and then "Flash TWRP", you will be guided by voice assistant and popup messages. [Tip] For more, read the "Fast guide for beginners".
Q. Can't flash patched boot image. My phone boots into TWRP, I selected adb sideload but nothing happens.
A. ADB in Android and ADB in recovery are two different drivers. If you are running Win10 you could be in luck because it's generic driver.
Boot the phone into recovery and then disconnect/reconnect it to the PC. With a lot of luck Windows detects a new device and installs the driver automatically. If not go through the driver update routine in Device Manager.
**************************************************************************************************
FOR HELP IN REALTIME JOIN "LenovoRomDownloader" CHAT https://demo.rocket.chat/channel/LenovoRomDownloader
**************************************************************************************************
====================================================================================
** The development of "Lenovo Rom Downloader" is completed with version V5.2. There will be no more updates.**
====================================================================================
**************************************************************************************************
Here is the source code of "Lenovo Rom Downloader V5.0.
In my view, my application is complete and finished.
If someone wants to improve it, in graphics, dialogs, popups, he is welcome, as long as the new development, put my name "@ robterza-XDA" as a creator of the sources.
**************************************************************************************************
If my app is usefull for you, don't forget to vote the Poll and press Thanks button and rate this thread!
LENOVO K3 WORKSHOP V2.X - Root/UnRoot and OTA Update 100% for K50T5/K50a40
LENOVO K3 WORKSHOP V2.X
"Lenovo K3 Workshop" is the evolution of "Lenovo Rom Downloader". Smaller but does more stuff.
Download Mediafire:
Download Megadrive:
*WARNING*: For the program to work properly, you need to install the Lenovo drivers. With the USB attached, run the test with the "Test Device" button. Very important are the Adb drivers for TWRP recovery. In TWRP mode and in normal mode, install the "Lenovo Composite ADB Interface" driver, and everything should work fine.
*Other Warning*: The exe files I compiled are not digitally signed with a Microsoft certificate, so certain AntiVirus programs will pick it up as potentially harmful when it is not. They will pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.
Provide downlink in google drive
Can you please provide download link in google drive, I can't download this LENOVO ROM DOWNLOADER V5.0 from your mega link
Thanx Very Much
On next Patch release, i will add "boot.img PATCHER on fly" . Stay tuned
Can someone please share a screenshot of their system/vendor/etc I am looking for some files that I'm missing. Thank you very much!
patch file has virus detected.
saintsoh said:
patch file has virus detected.
Click to expand...
Click to collapse
Its a false positive! Scan the "Lenovo_K3_Rom_Downloader" folder for test.
I Will remove the "INSTALLER PATCH" and make "PATCH ZIP PACKAGE".
I suspect that is the "INSTALLER" that creates the false positive.
any DIY youtube video ??
becleanstayclean said:
any DIY youtube video ??
Click to expand...
Click to collapse
This is the previous version REV4.4 But will give you an idea.
https://www.youtube.com/channel/UCKGmKDa3Ni0yC7Eo29xqujQ
robterza said:
On next Patch release, i will add "boot.img PATCHER on fly" . Stay tuned
Click to expand...
Click to collapse
"Lenovo Rom Downloader V5.0 Patch.zip" READY for download. :good:
robterza said:
"Lenovo Rom Downloader V5.0 Patch.zip" READY for download. :good:
Click to expand...
Click to collapse
still prompt with virus, trust anti-virus or ur patch........
saintsoh said:
still prompt with virus, trust anti-virus or ur patch........
Click to expand...
Click to collapse
The app code is very simple.
Extraxt the zip package in a Temp folder and scan the files one by one. Let's see which one give you the alert.
restore from quarantine, rescan seem ok.
test download the patch, it be quarantine becoz of virus.
saintsoh said:
restore from quarantine, rescan seem ok.
test download the patch, it be quarantine becoz of virus.
Click to expand...
Click to collapse
I think the problem is the "Donate" button on the main screen. When you click "Donate" the app launches internet explorer and opens the Paypal web page. I think your AV, interpret as trojan. Now. i will remove the "Donate" button from main screen, repack the patch and send you for new test. Thank you.
i think its google download, all files except checkupdate r prompt with virus.
saintsoh said:
i think its google download, all files except checkupdate r prompt with virus.
Click to expand...
Click to collapse
Thank you for testing. As i said, its false positive. :good:
yea, i think so too.
restore files from qurantine n rescan didnt prompt any virus.
thanks.
While I was trying to unroot during flashing stock boot.IMG I can't find stock boot.img file for s424 please provide it bro I have 13mb ota update but I can't update bcoz of root
Ayuagr said:
While I was trying to unroot during flashing stock boot.IMG I can't find stock boot.img file for s424 please provide it bro I have 13mb ota update but I can't update bcoz of root
Click to expand...
Click to collapse
Click "update" button, and you can download your stock boot.img from MegaDrive in the K50a40 folder.
Hey together,
I really hope someone out there is still using a A500 Tablet and may be able to help me fix a weird issue i encounter on every ROM i tried so far.
I installed the ROMs mentioned in this Thread: https://forum.xda-developers.com/iconia-a500/general/2018-a500-upgrade-threaddownloads-to-t3832293
And all of them come with the Same Problem for me.
If i try to open the Google PlayStore or something else that wants me to login into a Google Account it just says: "There was a problem communicating with Google Servers" "Try again later"
anyone knows of this issue ? All the fixes several Google searches gave me did not help to fix that issue for me on any of the ROMs.
help would be highly appreciated
kind regards
Finn
Hi,
have you read the tips? It says:
"- Google play will not work right if you do not format your data partition to f2fs. (You can do this in recovery)"
Have you tried it?
Matra-PB said:
Hi,
have you read the tips? It says:
"- Google play will not work right if you do not format your data partition to f2fs. (You can do this in recovery)"
Have you tried it?
Click to expand...
Click to collapse
That may not be the problem I've hear a lot of people are having this problem. But it's a good place to start if he hasn't tried it yet.
Success story upgrading A500 in 2019 July
finneus_ said:
Hey together,
I really hope someone out there is still using a A500 Tablet and may be able to help me fix a weird issue i encounter on every ROM i tried so far.
I installed the ROMs mentioned in this Thread: https://forum.xda-developers.com/iconia-a500/general/2018-a500-upgrade-threaddownloads-to-t3832293
And all of them come with the Same Problem for me.
If i try to open the Google PlayStore or something else that wants me to login into a Google Account it just says: "There was a problem communicating with Google Servers" "Try again later"
anyone knows of this issue ? All the fixes several Google searches gave me did not help to fix that issue for me on any of the ROMs.
help would be highly appreciated
kind regards
Finn
Click to expand...
Click to collapse
First my thanks to the forum key members for providing answers to queries and to all the key contributors of SW/ROMS in this forum. I followed the procedures from this forum to Flash / upgrade my Acer Iconia A500 on 4.0.3 ICS that was sitting in a trunk for the last few years. Summary of steps I tried out.
STEP 1: Install the Acer device drivers listed in the links in this forum on your Laptop/Computer even if by default your Windows 10 OS (assuming you are on Win10 like me) is able to recognize the A500 connected to the USB port.
USB_Acer_1.00.0524_A30HA31HA32H_A.ZIP
STEP 2: ROOTING the Acer A500.
1. The tablet should be already upgraded to stock ICS for A50x (or stock ICS A10x/A510 for other tablets).
2. On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch ON. If you do not see this menu, then click 7 times of the Android Build No. listed under settings and come back to the menu above to enable USB Debugging.
3. Connect the tablet to the computer (Before connection it is recommended to update the driver for a tablet from here: A10x, A50x, A510).
4. Since most of the discussions regarding flashing A500 were from 2011, the earlier Gingerbreak method for rooting did not work.
I downloaded the following file from this forum to root my tablet.
ICS_rooting_A10x_A5xx.zip
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
Note: The McAfee Antivirus software started tagging a file 'mempodroid' within this ZIP file Tools folder as a virus or malicious file. This rooting method uses the 'mempodroid' exploit which is detected as a VIRUS by McAfee and Qurantined. So restore from Qurantine and check list of files are still present in the folder. If not verify 8+8 files in folders again.
As per inputs in this forum, I restored the files quarantined and then suppressed McAfee SW for the duration of my upgrade activities on my laptop and was able to successfully extract all the files in the ZIP file to a local folder on the laptop. This ZIP file has adb and fastboot - two key programs useful for rooting your A500 apart from SU or superuser base file used in step 2. The file to run is the BAT file runit-win.bat if you are on windows. At the end of this step your tablet should be rooted. You may check by installing the RootCheck app from Google Playstore.
Step1a: Install a File Manager app from the Google playstore. This will help you extract the CPU ID and convert it with the SBK tool to get the SBK number/string. important steps SBK tool was available in file - SBCalc_v1.1.ZIP available in this forum.
STEP 2b: SUPERUSER and SUPERSU installation
1. Install SuperUser.apk first.. (IMP - Its available in this forum. Its like a base version for superSU to install over. If you do not install SuperUser.apk, then each time you try installing SuperSU, you would get an error message about a SU file being incompatible.)
2. Then install an older version of SuperSU downloaded from the website - filename -> eu.chainfire.supersu_v2.65-265.ZIP . Newer versions will not work. U got to install an older version as new version seems to be a paid SW.
3. Next Open SuperSU app on your tablet and let it update itself a couple of times each time opening and closing the app after the upgrade.
4. Remove SuperUser.apk file as now its no longer needed.
5. Now that you have ROOT access and SuperUSer access
6. Install Titanium Backup. File name in this forum- update-recovery-TWRP-rev2.0-beta4.ZIP . This will help you to flash/upgrade ROM software on your tablet.
Twrp 2.8:
http://www.mediafire.com/file/e7wpny5f39vw3pc/update-recovery-TWRP-rev2.0-beta4.zip/file
Compressed Archive (.ZIP)
File size: 4.91MB
Uploaded: 2018-08-14 21:40:26
https://www.mediafire.com/download/e7wpny5f39vw3pc
STEP 3: Install an Unlocked Bootloader i.e. unlocked bootloader Skrillax v9 - file name in this forum BabSector.rar or A500-Bootloader-Nvflash.ZIP
Once you have reached this step, you now have the basic tools needed for the final ROM upgrade of the tablet.
I did get error message after the reboots that happened after Unlocking the Bootloader. Someting about a LNX partition not being okay or some such msg. Each time I just WIPED the Cache and selected similar options to wipe System, Data, User, Dhelvic cache (spelling incorrect) etc. Since you have not installed the final OS or ROM for your tablet yet, no harm in deleting these partition data. Actually its recommended to wipe, format in f2f formats etc. all of which is possible using the TWRP Recovery software you installed in step 2. Choose Recovery menu option each time the tablet boots or gives errors.... using the volume rocket and power buttons. More info -> Go through this thread and install unlocked bootloader.
https://forum.xda-developers.com/showthread.php?t=1622425
Flashing Bootloader Steps
-------------------------
1. generate your SBK from cpuid
2. put tab in APX by holding reset (small pinhole bottom right side)
and pushing power for 3-4 sec. - then release reset approx 1 sec. later
the screen should be blank and power button should be lit - plug in USB to PC.
2. Run A501 A.bat - when finished reboot tab to recovery (win 7 and under
right click on A501 A.bat and select Run as Administrator)
3. run Recovery(power and volume-) ->WIPE -> "Advanced wipe ->System (only)and swipe to wipe.
4. unplug USB and reboot tab to APX
5. plug in USB afer it is in APX mode -> Run A501 B.bat (win 7 and under
right click on A501 B.bat and select Run as Administrator)
Bootloader unlock tutorial
--------------------------
Step 1: Get your cpuid - https://forum.xda-developers.com/showthread.php?t=1624645
Step 2: Convert it into an SBK - https://forum.xda-developers.com/showthread.php?t=1810618
Step 3: Download the A500 drivers
- http://www.mediafire.com/file/pde8rojv1t8gnif/USB_Acer_1.00.0524_A30H_A31H_A32H_A500_A501.zip/file
Step 4: Download the files to install the bootloader
- http://www.mediafire.com/file/o7m2ouwo6zuod4d/A500-Bootloader-Nvflash.zip/file
Step 5: Follow the instructions in "how to.txt"
Step 6: Download a rom and flash in twrp
This tutorial is based of
https://forum.xda-developers.com/showthread.php?t=2450119 thread so big thanks to KaijiKun .
Bootloader unlock files:
http://www.mediafire.com/file/o7m2ouwo6zuod4d/A500-Bootloader-Nvflash.zip/file
STEP 4. Downloaded file omni-4.4.4-20150210-a500-IconiaHD.ZIP as I was not sure version omni 5.1.1 was as stable as Omni4.4.4 reading all the threads in this forum.
First rename the downloaded OMNIROM file as update.zip .
OmniRom 4.4.4
http://www.mediafire.com/file/ghd72j3g618kk9g/OMNIROM-5.1.1-Tegraowners_ROM_v13t2.zip/file
File size: 244.66MB
Uploaded: 2015-04-05 17:40:14
STEP 5: Install another tool adb_fast.ZIP. This tool is also available in this forum.
Note:You need to copy the update.zip file to your computers folder where this tool adb_fast is installed. In mine it was C:\Program files (x86)\Minimal ADB and Fastboot folder. This adb_fast file creates an application shortcut on your computer desktop. Clicking on the short cut launches adb and fast boot programs I mentioned at the beginning.
STEP 6: Copy the file to the SD card (16GB) of your tablet.
Run the adb_fast tool from your desktop shortcut. This will open a Command Prompt type black screen window where you can enter the code as given below. Note you may need to see how your SD card is listed in a file manager in your computer
Code:
adb push update.zip /mnt/sdcard/update.zip --- NOTE: this creates mnt folder on internal storage and I had to then move the file using TWRP recovery tool installed in step 2, to the SD card.
adb push < ------- is the push command.
rom.zip < ------- is the name of the Rom zip file.
/sdcard < ------- is the location your pushing the Rom to.
E.) Reboot tablet with Power+Down Arrow i.e. This will start the Upgrade process for the tablet to OMNIROM 4.4.4
-- Power Button + UP VOLUME pressed... then release Power button after LED lights.
-- System will boot to commmand prompt
STEP 7: Install GAPPS using pico gapps short version and Wipe Data/Factory reset ----------------?>and wipe cache partition?
Reboot after 1st reboot
G.) https://opengapps.org/ to install a minimal version of Google Apps on the tablet.
File name -> pa_gapps-modular-mini-4.4.4-20150410-signed.ZIP
Root tablet again and install SuperSU if you need it
other info.
You can use TWRP to flash the OmniROM on the tablet or you can use the following in worst case senario to do the same.
Code:
fastboot devices
fastboot flash update.zip -- check if syntax is ok from threads in this forum
fastboot reboot-bootloader
copied below from other threads ---->
I find that a large amount of complaints in developer threads are due to people not properly wiping before a flash.
Of course there is times when a 'dirty' flash is fine, but if you're ever not sure, wipe as cleanly as possible.
fastboot allows for about the cleanest of wipes by the way. And each partition can be done separately too.
Code:
fastboot erase system
fastboot erase data
fastboot erase cache
can all be done individually, but to do these all in one command
Code:
fastboot erase system -w
If possible I recommend to do these steps before flashing a ROM, and now that you know you can do this all within fastboot mode i suggest to try it out, its quick and painless!
Don't forget to wipe your kernel too! (fastboot erase boot)
~Important~ If your device uses an emulated SD card (as in no removable micro SD but an SD partition on phone)
Then be careful wiping data/userdata as this will erase all contents of internal SD - you are forewarned!
ADB= Android Debugging Bridge (ADB)
[TOOL]Minimal ADB and Fastboot [2-9-18]
https://forum.xda-developers.com/showthread.php?t=2317790&page=12
First a short explanation:
Fastboot, like ADB, is a tool to communicate from PC to Android phone. There are times when it is a must to use, and times when it is just helpful.
ADB is used within your recovery or within your OS, but when you are in bootloader mode and need to communicate with your phone then you need fastboot.
And you may ask why would i ever need this?
Well many reasons. Main one is knowledge, learning the ins and outs of fastboot, like learning ADB, can get you out of many jams.
And if you want to unlock your bootloader this is done through fastboot. Granted HTC's unlock is... well crap, but for a Nexus this is how its done.
One other reason I have to stress is learning for safety reasons, This is about the safest way possible to flash firmware to your phone (ie Radio, Hboot, Recovery)
Lastly you may want to know the limitations,
There are many of course, this isnt JTAG, it will not resurrect a hard brick, but it often save peoples phones from 'soft bricks' and lots of time when know how and when to use it.
Think of fastboot as the program that takes over when ADB cant be used, it works with firmware more than software.
https://forum.xda-developers.com/showthread.php?t=1624645&page=3
GUIDES
---------------
Civs Guide to flashing the bootloader http://forum.xda-developers.com/showthread.php?t=1622425
Walkthrough using APXFLASH tool at Step 6 http://forum.xda-developers.com/showthread.php?t=1624645&page=2
From Civato's OP of The Guide: nvFlashToolPackages
Skrilax_CZ bootloader thread http://forum.xda-developers.com/showthread.php?t=1619913 and should be "required reading" for anyone mucking about in their tabs internals!!!!
Rollback to HC
jazzyjames guide http://forum.xda-developers.com/showthread.php?t=1516012
Iconia Root http://forum.xda-developers.com/showthread.php?t=1138228 /gingerbreak: For returning to Honeycomb
----------------
To get my CPUID, I have followed the steps below:
Open yr file explorer, esfile explorer is a great one....navigate to:
/sys/firmware/fuse/acer_cpuid - add a zero to the front!
To get CPUID get a Root browser of some sort and go to sys/firmware/fuse/acer_cpu_id
convert my CPUID into SBK?
--------------------------
https://forum.xda-developers.com/showthread.php?t=1055354&page=6
What Does Root Give Me?
1. Full control over your system
2. Ability to alter system files. You can replace many parts of the "Android Core" with this including:
o Themes
o Core apps (maps, calendar, clock etc)
o Recovery image
o Bootloader
o Toolbox (linux binary that lets you execute simple linux commands like "ls") can be replaced with Busybox (slightly better option)
o Boot images
o Add linux binaries
3. Run special apps that need more control over the system
o SuperUser (lets you approve or deny the use of root access to any program)
o Task Manager For Root (Lets you kill apps that you otherwise could not kill)
Tether apps (like the one found at [android-wifi-tether.googlecode.com])
4. Backup your system
o You can make a folder on your SDCARD and backup all of your .APK files to your SDCARD (helps if an author decides to "upgrade" you to a version that requires you to pay to use the version you just had)
5. Relocate your (browser/maps/market) cache to your /sdcard
6. Relocate your installed applications to your /sdcard
7. Reboot your phone from the terminal app easily (su <enter> reboot <enter>)
Turn the rotation lock off.
-------------------------------------------------------
SUMMARY - Regardless of version, rooting is the same... next
** Unlock the bootloader.
** Fastboot flash a Custom Recovery (TWRP).
** Download to the Tablet, Chainfire's SuperSU root updater .zip
** Boot into the previously fastboot flashed Custom Recovery, and flash the SuperSU updater .zip.
** Reboot - you're rooted.
-------------------------------------------------------
PS. I tried to maintain a log in Notepad during my upgrade. Unfortunately did not write detailed instructions and link to required files. Above is a summary of what worked for me.
Can not root
sukasis said:
First my thanks to the forum key members for providing answers to queries and to all the key contributors of SW/ROMS in this forum. I followed the procedures from this forum to Flash / upgrade my Acer Iconia A500 on 4.0.3 ICS that was sitting in a trunk for the last few years. Summary of steps I tried out.
STEP 1: Install the Acer device drivers listed in the links in this forum on your Laptop/Computer even if by default your Windows 10 OS (assuming you are on Win10 like me) is able to recognize the A500 connected to the USB port.
USB_Acer_1.00.0524_A30HA31HA32H_A.ZIP
STEP 2: ROOTING the Acer A500.
1. The tablet should be already upgraded to stock ICS for A50x (or stock ICS A10x/A510 for other tablets).
2. On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch ON. If you do not see this menu, then click 7 times of the Android Build No. listed under settings and come back to the menu above to enable USB Debugging.
3. Connect the tablet to the computer (Before connection it is recommended to update the driver for a tablet from here: A10x, A50x, A510).
4. Since most of the discussions regarding flashing A500 were from 2011, the earlier Gingerbreak method for rooting did not work.
I downloaded the following file from this forum to root my tablet.
ICS_rooting_A10x_A5xx.zip
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
Note: The McAfee Antivirus software started tagging a file 'mempodroid' within this ZIP file Tools folder as a virus or malicious file. This rooting method uses the 'mempodroid' exploit which is detected as a VIRUS by McAfee and Qurantined. So restore from Qurantine and check list of files are still present in the folder. If not verify 8+8 files in folders again.
As per inputs in this forum, I restored the files quarantined and then suppressed McAfee SW for the duration of my upgrade activities on my laptop and was able to successfully extract all the files in the ZIP file to a local folder on the laptop. This ZIP file has adb and fastboot - two key programs useful for rooting your A500 apart from SU or superuser base file used in step 2. The file to run is the BAT file runit-win.bat if you are on windows. At the end of this step your tablet should be rooted. You may check by installing the RootCheck app from Google Playstore.
......
Click to expand...
Click to collapse
Hi sukasis, i was unable to root the tablet. I download all and run the runit.win.bat (trying normal, as admin, and open a cmd as admin and then navigate to the bat to execute).
- It say device connected
- Then push 7 files correctly
- Executing of the main script. (it freeze here a lot of time)
Then error: protocol fault (no status)
The file "su" isn't created
Not getting root!
I try in USB 3.0 and 2.0 same error.
I have windows 10.
I uncheck the Debugging mode and it's bring another error, so i believe the connection is good because in debug mode can push files.
I don't know whate else i can do.
Hi ladies&gentlemens
I'm going to leave a guide here, on how to fix 5g on oos11 or custom ROMs, I'll try my best to be noob friendly
You can skip the first step, if enabling diag mode through engineeringmode.apk, dial *#801# works for you
1. You will have to root your phone, as engineeringmode.apk/dial *#801# does not work on this rom
go to the official magisk site, and download magisk 25.1 apk, make it zip by changing the file extension from apk to zip, after that flash it using ADB sideload, after how the device will boot up, open the magisk app (let it update), open settings, turn on zyigsk and enforce denylist, open configure denylist, and hide Google pay, google play services, google play store, and pretty much any banking apps
2. you will need to enable diag mode: enable USB debugging in developer options after that open cmd, terminal, PowerShell whatever you prefer on your pc, and enter ADB commands:
ADB devices
ADB shell
su
setprop sys.usb.config diag,adb
now your phone is in diag mode
3. google for qualcomm diag drivers and install it after that open the device manager and you will see 2 unknown devices there (model of your device *IN2013* for example) update them(by picking disk, driver urself) to Qualcomm HS-USB MDM Diagnostics 90B6
4. google for qpst tool and download it and install it after that, Open QPST, and you should see devices in ports and active phones list, click Start Clients -menu -> QPST EFS Explorer and select your device (SDX55) and wait a few minutes, then go to policyman directory and copy carrier_polixy.xml , carrier_polixy.xml_Subscription01 , lte_feature_restrictions file to your desktop or somewhere safe, it will be your backup just in case, after how you copied it, you will need to delete the same files (NOT FROM YOUR PC! FROM YOUR PHONE, ON QPST TOOL IN POLICYMAN DIRECTORY!)
5. download the zip from here, extract the files from the zip and copy them to the policyman directory, drop and drag them one each time
6. Congratulations now you can close qpst tools etc, and reboot your phone
links to useful sources will be in USEFUL.txt
DISCLAIMER: I DO NOT GUARANTEE THAT THIS WILL WORK ON ALL CUSTOM ROMS, I'VE TESTED IT ONLY ON PROJECT ZEPHYRUS AND OOS11, AND I AM PRETTY SURE THAT IT WILL WORK ON MOST OF THE CUSTOM ROMS IF NOT ALL, ALSO YOU AGREE THAT YOU WILL DO IT ON YOUR OWN RISK!!!