Here's small guide about ClockworkMod Recovery / Team Win Recovery Project feature "ADB Sideload".
The example is done with TWRP but the basic idea with CWM is pretty much the same.
Required tools for uploading:
- Samsung Galaxy S3 mini with CWM/TWRP recovery
- Android SDK -> DOWNLOAD FOR OTHER PLATFORMS -> installer_r22.3-windows.exe
- Desired ROM to be installed, in this example it's DMod V6
The steps:
1) Install the SDK, start it and select "Android SDK Tools" and "Android SDK Platform-tools" and then "Install 2 packages"
{
"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"
}
2) Locate the "adb.exe" file that was installed with "Android SDK Platform-tools", It's usually in "C:\Program Files (x86)\Android\android-sdk\platform-tools". I decided to copy the "platform-tools" folder into c:\ and renamed it to "adb".
3) Copy the ROM you desire to install in the "adb" folder
4) Boot the phone into recovery, and select "Advanced":
5) Plug the USB cable in
6) Start "Command Prompt" in Windows (Start -> type in "cmd" to search box and select "cmd.exe")
7) Type: "cd \adb"
8) Type: "adb kill-server"
9) Type: "adb usb"
HTML:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
restarting in USB mode
10) Type: "adb devices"
HTML:
List of devices attached
sh3d7h3dj631f6a7 recovery
11) Select the "ADB Sideload" from the phone, swipe to start
12) Type: "adb devices"
HTML:
List of devices attached
sh3d7h3dj631f6a7 sideload
13) Type: "adb sideload DModV6.zip"
Wait for the upload to finish and you are done! Have fun installing DMod V6
WAIT! There's this error with adb:
HTML:
error: closed
1) Cancel the "ADB Sideload" from phone, return to "Advanced" menu
2) Read the guide again from step 8 and obey them!
can i fix this brick with side load?
http://img547.imageshack.us/img547/7113/4jmo.jpg
wareca said:
can i fix this brick with side load?
http://img547.imageshack.us/img547/7113/4jmo.jpg
Click to expand...
Click to collapse
Sideload might not be option for that because that is stock recovery.
Looks like you have lost atleast your cache partition, you might need to use Odin and reflash the whole phone again with PDA option.
I get the error no devices found. Any ideas how I can fix that?
Thanks
Thank you !
bro thanks to you you save me from 25 dollars i wish if someday i become rich you are on my mind i will donate you :angel:
mikma80 said:
Here's small guide about ClockworkMod Recovery / Team Win Recovery Project feature "ADB Sideload".
The example is done with TWRP but the basic idea with CWM is pretty much the same.
Required tools for uploading:
- Samsung Galaxy S3 mini with CWM/TWRP recovery
- Android SDK -> DOWNLOAD FOR OTHER PLATFORMS -> installer_r22.3-windows.exe
- Desired ROM to be installed, in this example it's DMod V6
The steps:
1) Install the SDK, start it and select "Android SDK Tools" and "Android SDK Platform-tools" and then "Install 2 packages"
2) Locate the "adb.exe" file that was installed with "Android SDK Platform-tools", It's usually in "C:\Program Files (x86)\Android\android-sdk\platform-tools". I decided to copy the "platform-tools" folder into c:\ and renamed it to "adb".
3) Copy the ROM you desire to install in the "adb" folder
4) Boot the phone into recovery, and select "Advanced":
5) Plug the USB cable in
6) Start "Command Prompt" in Windows (Start -> type in "cmd" to search box and select "cmd.exe")
7) Type: "cd \adb"
8) Type: "adb kill-server"
9) Type: "adb usb"
HTML:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
restarting in USB mode
10) Type: "adb devices"
HTML:
List of devices attached
sh3d7h3dj631f6a7 recovery
11) Select the "ADB Sideload" from the phone, swipe to start
12) Type: "adb devices"
HTML:
List of devices attached
sh3d7h3dj631f6a7 sideload
13) Type: "adb sideload DModV6.zip"
Wait for the upload to finish and you are done! Have fun installing DMod V6
WAIT! There's this error with adb:
HTML:
error: closed
1) Cancel the "ADB Sideload" from phone, return to "Advanced" menu
2) Read the guide again from step 8 and obey them!
Click to expand...
Click to collapse
getting this error while in recovery mode in adb
E:\Minimal ADB and Fastboot>adb usb
error: device not found
Edit: installed drivers from pdanet. done now. thanks
manikumary said:
getting this error while in recovery mode in adb
E:\Minimal ADB and Fastboot>adb usb
error: device not found
Edit: installed drivers from pdanet. done now. thanks
Click to expand...
Click to collapse
what drivers????????
bauerpower said:
what drivers????????
Click to expand...
Click to collapse
Dunoo:silly:
Done Google, Found those drivers, then worked.
bauerpower said:
what drivers????????
Click to expand...
Click to collapse
Oh the usual drivers required with windows. Best to install KIES, the drivers come with that.
Or http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
(LOL! "Samsung Andorid USB Driver for Windows")
Saved time and money
Thanks this really work, along with naked android driver that someone suggested. i saved time, money, and not having to replace my phone. now im full working and have the custom recovery working now, thanks a LOT!!
my command prompt is showing error
my command prompt shoows error in last when i send mt rom to my device
adb sideload rom.zip
it shows error
100 % but error sending
Mr22Me said:
my command prompt shoows error in last when i send mt rom to my device
adb sideload rom.zip
it shows error
100 % but error sending
Click to expand...
Click to collapse
And you got custom recovery installed? Not the default?
adb devices offline
hi, allways when i type adb usb and press enter he does this
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device offline
vdries said:
hi, allways when i type adb usb and press enter he does this
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device offline
Click to expand...
Click to collapse
Make sure the following:
1) Your phone is rooted and up and running in custom recovery (TWRP is better imo)
2) You have proper drivers installed in your Windows (KIES does this trick)
3) You have USB debugging enabled in the phone
after i do the guide it has install the rom i pushed but now when the phone get on
the LG logo showed and the rom logo showed and stuck there
THANK YOU! exactly what i was looking for and needed after completely "nuking" my phone of all data with TWRP.
when I type adb devices the second time when it should say sideload it says host instead??
true hard brick fix
wareca said:
can i fix this brick with side load?
http://img547.imageshack.us/img547/7113/4jmo.jpg
Click to expand...
Click to collapse
not sure about that but a true hard brick (nothing only activity is after pushing to two pins in the back right against mobo red light will come on for a few sec when plugged in other then that NO LIFE ) http://forum.xda-developers.com/showthread.php?t=2581166 (NOT MY WORK BUT I CAN VERIFY IT WORKS
ACTUALLY THIS IS THE LINK AND FILES I USED BUT TRUST XDA FOR ALL YOUR PROBLEMS....https://www.youtube.com/watch?v=wZEKzglmjtY
Nitefall said:
when I type adb devices the second time when it should say sideload it says host instead??
Click to expand...
Click to collapse
Sounds like you don't have sideload started from the custom recovery?
I have HTC One M7 and proper drivers (fastboot works). When I type
adb usb
I receive "error: device not found"
I just can get the bootloader, it can't load system. It is S-ON.
I found the way to do it here https://www.youtube.com/watch?v=PUjQnwULGzs
Related
Big thanks to tereg for the toolkit and the guys who rooted the EVO with a file write/chmod race condition exploit that gave me the idea for this.
jcase noticed that a race isn't actually necessary to exploit the chmod 777 on the file I've been working with, simplifying the script alot.
I used the files from the adb development pack that Tereg put together. Download them here. You don't need them for this root process as long as you have a working adb install.
THE SCRIPTS HAVE BEEN UPDATED MANY TIMES! Please be sure to re-download the new hack-v4.zip before you start if you a returning root seeker.
You will need adb access. Install the android sdk for your platform (macos, windows, linux) get it for your OS here.
If you don't know how to install the sdk, search xda, there are a ton of howtos for that.
Also, if you want to root and can't get your computer to talk to the phone or have some other weird computer related issue you can now try this method, which doesn't require a computer at all!
Unzip hack-v4.zip to somewhere, copy/move the files into your adb-sdk/tools directory/folder.
*updated files to hack-v4.zip @ 7-14-2010 10:43AM Central*
Files to download:
hack-v4.zip
A ROM file, I suggest EvilEris if you want to flash the whole phone OR EngTools.zip If you just want to be root. (Thanks jcase!)
Android SDK (skip if you have a working adb)
Instructions for linux/OSX. - Alternate instructions specifically for MAC
Have adb in your path, or move the files contained in hack-v4.zip into your sdk/tools directory so your pushes will work properly.
FOR ALL OS's Make sure your phone has Applications->Development->USB Debugging turned on.
Do NOT have your phone in Disk Drive Mode, have it in Charge Only.
Open a terminal window in your /tools/ directory. Type this at the prompt.
Code:
sh runinlinuxfromtools.sh
This will take a few minutes, follow the instructions on your screen.
If you get adb: command not found, try
Code:
sh runinlinuxadb.sh
Some people get a permission denied error. Try
Code:
chmod +x ./runinlinuxfromtools.sh
./runinlinuxfromtools.sh
Instructions for windows (thanks tereg!)
Download the hack.zip file and extract it to the desktop. So, you have a folder on the desktop called hack. I would recommend moving or copying those files (EDIT: that are contained in the hack folder) to the C:\android-sdk-windows\tools folder. Why? Because the script runs "adb ____" commands, and unless you've set up adb to be able to run anywhere within the command prompt, the script won't run. So, it will universally work if the files in the hack folder are placed in C:\android-sdk-windows\tools
So, open a command prompt by pressing WindowsKey+R, or going to Start-Run (in WinXP) and typing
Code:
cmd
in the text box there and press OK
If you are in Windows Vista/Windows 7, go to the Start Menu, then type in
Code:
cmd
in the search bar in the lower right-hand corner of the start menu and press enter, and locate Command Prompt in the search results, or go to Start -> All Programs -> Accessories -> Command Prompt
Type
Code:
cd C:\android-sdk-windows\tools
and press enter
Now, I recommend pushing the ROM you want to flash to the SD card now. So, if you download EvilEris3.0 for instance, make sure you download it to the C:\android-sdk-windows\tools folder, and then execute
Code:
adb push EvilEris3.0.zip /sdcard
Replace EvilEris3.0.zip with the name of the .zip file that you choose to download.
Then, type
Code:
runindos.bat
to execute the script.
You might have to run it 2 or 3 times for it to work. If it fails, just reboot the phone normally, then run
Code:
runindos.bat
again once the phone is booted back up and you're ready.
----------(Thanks again tereg!)
If your device reboots into a new screen with options on it, you now have root in recovery mode. At this point you will be flashing your Eris's brains, so YOUR PHONE WILL BE BLANK AFTER LOADING A NEW ROM! All of your apps/numbers will be gone from the phone.
I suggest a nand backup first.
Download and copy one of these ROM's to your sdcard as update.zip and flash it with flash zip from sdcard by selecting "Install zip from sdcard".
The first boot after loading a new ROM takes quite a while to show any activity to the screen. Give it a good 5 minutes before you start wondering if it's ever going to come back.
Eris ROMS
More things you can now do.
Replace that hateful HBOOT 1.49, and get a rooted STOCK phone.
Donate of you luv me!
-----------------
And some love for tereg! Donate a bit to him too, if you're feeling generous.
Dude, seriously. Put up a donate button. I would donate for your effort. This is absolutely amazing.
I will suck yo thang if this works...brb
If this is confirmed I'm returning my eris with the ****ty trackball and rooting a new one >_>
I love you so much for running with our small shot
when doing
cat > data/local/testfile
I get:
System cannot find the path specified
Oh and btw
This should work on ANY HTC Android 2.1 phone.
{
"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"
}
cptkrush said:
when doing
cat > data/local/testfile
I get:
System cannot find the path specified
Click to expand...
Click to collapse
crap, I'm kinda spaced out from glee right now. should be
/data/local/testfile
wag3slav3 said:
crap, I'm kinda spaced out from glee right now. should be
/data/local/testfile
Click to expand...
Click to collapse
lol, same thing...
do you want us to do a cd command, because the cat command does not exist i believe. It may not help that i have absolutely no idea what to do in the first place
cptkrush said:
when doing
cat > data/local/testfile
I get:
System cannot find the path specified
Click to expand...
Click to collapse
You're missing the first / in /data/local/testfile sir.
Yours cat > data/local/testfile
mine cat > /data/local/testfile
wag3slav3 said:
You're missing the first / in /data/local/testfile sir.
Yours cat > data/local/testfile
mine cat > /data/local/testfile
Click to expand...
Click to collapse
nope, that was just how i typed it out in the post, still not working.
How are we supposed to "run" the following?
/data/local/flash_image recovery /sdcard/recovery.img
reboot recovery
I keep getting "error opening /sdcard/recovery.img: No such file or directory", but I'm also not really sure if I'm missing something. I type it in EXACTLY as you put it, right?
ericFuels999 said:
How are we supposed to "run" the following?
/data/local/flash_image recovery /sdcard/recovery.img
reboot recovery
I keep getting "error opening /sdcard/recovery.img: No such file or directory", but I'm also not really sure if I'm missing something. I type it in EXACTLY as you put it, right?
Click to expand...
Click to collapse
cat is a unix command
we're on dos
dos doesn't have the same command
xnatex21 said:
cat is a unix command
we're on dos
dos doesn't have the same command
Click to expand...
Click to collapse
I understand that, but that wasn't my question. Refer to my previous post.
xnatex21 said:
cat is a unix command
we're on dos
dos doesn't have the same command
Click to expand...
Click to collapse
THIS EXPLAINS EVERYTHING, sorry for caps, but i got excited :3
any way to do this in DOS or am i gonna have to boot up ubuntu?
scratch that, wag3 got me covered.
xnatex21 said:
cat is a unix command
we're on dos
dos doesn't have the same command
Click to expand...
Click to collapse
You skipped the step where you do an adb shell.
You should be at the $ prompt on your phone for this.
ahem... I get permission error when I tree to reboot **epic sadface**
I"M DUMB I HAVE TO LEAVE SHELL FIRST
Put run 'adb shell' in the instructions before 'then do this'. Not everyone is going to pick up on that.
wag3slav3 said:
You skipped the step where you do an adb shell.
You should be at the $ prompt on your phone for this.
Click to expand...
Click to collapse
you should add
"do: adb shell"
to the first post.
hello all, I seem to be having a prob with KFU, im trying to install recovery per video instructions.
***********************************************
* Kindle Fire Utility 0.9.1 *
***********************************************
'findstr' is not recognized as an internal or external command,
operable program or batch file.
ADB Status: Online
ADB Rooted: Yes
Boot Status: Unknown
Please make a selection or hit ENTER to exit:
This is happening with 0.9.2 and 0.9.1
I tryed both
I read that someone else is or was having same issue.
findstr.exe is in the system32 folder also
{
"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"
}
a good practice is to put kfu 0.9.2 to c:\ and rename it to "kfu" that it is c:\kfu
to use it with stock 6.2.2 and burritoroot3 you have to patch the run.bat:
http://forum.xda-developers.com/showpost.php?p=21749205&postcount=792
Ok I will try that, um I have another question.
Is it ok that I flashed firefirefire on before I put the recovery on it.
Or do I have to remove it before I put the recovery on?
Thks
cloud71 said:
Ok I will try that, um I have another question.
Is it ok that I flashed firefirefire on before I put the recovery on it.
Or do I have to remove it before I put the recovery on?
Thks
Click to expand...
Click to collapse
it is ok but twrp will overwrite fff with a older version cause it has it integrated in the installation - would reinstall fff 1.2 afterwards
ok thankyou all very much, I will look for the newer version when recovery is on.
whats weaid now is when the adb server starts up now it says its an older version and needs to be updated. I guess as long as it works I'm not going to cross that bridge LOL.
God Bless
cloud71 said:
ok thankyou all very much, I will look for the newer version when recovery is on.
whats weaid now is when the adb server starts up now it says its an older version and needs to be updated. I guess as long as it works I'm not going to cross that bridge LOL.
God Bless
Click to expand...
Click to collapse
would use only the tools folder of kfu - there are all commands you ever need and no weird messages ...
if your question is answered or your problem is solved
please mark the subject of the topic (edit first post) with [Solved]
Looks like im still having the same prob.
***********************************************
* Kindle Fire Utility 0.9.2 *
***********************************************
'findstr' is not recognized as an internal or external command,
operable program or batch file.
ADB Status: Online
ADB Rooted: Yes
Boot Status: Unknown
Please make a selection or hit ENTER to exit:
I downloaded and patched the run.bat
still getting the samething
findstr.exe is a system command located in c:\windows\system32 !
would search over your c:\ if it is even there
how do you call the run.bat ?
open a (elevated) command prompt, cd to c:\kfu, type "run.bat" and enter
edit: just saw in your first post that it is there - maybe reregister it:
1) Click Start
2) Click Run
3) Type regsvr32 findstr.exe
4) Press Enter
5) Restart your computer
or "c:\windows\system32" is'nt in your "path" variable - type "path" at a command prompt and check
or it is corrupted (ie by maleware) - then you have to reinstall/repair it from system cd
Yes the findstr is in the system32 folder I chked.
I ran run.bat by clicking on it and have also ran it by using cmd prompt
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Mac>cd C:\KFU
C:\KFU>run.bat
I still get this :
***********************************************
* Kindle Fire Utility 0.9.2 *
***********************************************
'findstr' is not recognized as an internal or external command,
operable program or batch file.
ADB Status: Online
ADB Rooted: Yes
Boot Status: Unknown
Please make a selection or hit ENTER to exit:
not sure what is going wrong errrrr
just updated my last post ...
tried to register it ? - checked path variable ? - do simply "findstr -?" from command line ?
YAY putting that in the path var. worked thks bro
***********************************************
* Kindle Fire Utility 0.9.2 *
***********************************************
1 Bootmode Menu
2 BurritoRoot (Temporary)
3 Install Permanent Root with Superuser
4 Obtain Stock update.zip
5 Install latest TWRP Recovery
6 Extras
0 Recheck Device Status
ADB Status: Online
ADB Rooted: Yes
Boot Status: 4000
Please make a selection or hit ENTER to exit:
fingers and toes crossed
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Ok I did the backup, now the twrp is at 2.0, should I update it?
or can I just stay at this version, and also if I do update it. do I just install the update over top of the 2.0?
at some point I plan on putting a different rom like cm6 or cm7 or something else on it.
Oh and can I boot to recovery without it being plugged into pc and do the stuff on it without the pc now?
cloud71 said:
Ok I did the backup, now the twrp is at 2.0, should I update it?
or can I just stay at this version, and also if I do update it. do I just install the update over top of the 2.0?
at some point I plan on putting a different rom like cm6 or cm7 or something else on it.
Oh and can I boot to recovery without it being plugged into pc and do the stuff on it without the pc now?
Click to expand...
Click to collapse
there is only 1 twrp available and this is 2.0
you may want to install fff again that you have the newest version : http://forum.xda-developers.com/showthread.php?t=1369405
and you can boot into recovery by pressing the power button repeatently till it gets orange at startup (the yellow triangle)
Thkyou very much for all your help, couldnt have done it without you thanks
Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war
* or the current economic crisis caused by you following these directions.
* So don't be an *** ****
*/
DO NOT TAKE AN OTA WHILE ROOTED!!! YOU WILL HAVE A BRICK IN YOUR HANDS!!!
Hi, For while i try Root my Vivo Air and don't get much success with it... so i try a new ADB Driver* and that works :highfive:
Using vRoot you can easy root your phone BUT the problem is the Chinese SuperSU... so i get on Google a Script who Replace the Chinese SU to XDA's @Chainfire SuperSU :highfive:
So follow the Steps ;D
1 - Download vRoot , ADB installer (Just to have sure about the drivers) , Google ADB Driver Modificated to Vivo Air (Driver without Signature =/ ) and WolfDroid Script
2 - Install vRoot and ADB Installer on computer ;D
3 - Turn ON the USB Debugging ... (if you put the cable but don't appear the option to turn it on, go on settings -> about Device and click over "Build Number" 5 times to get developer Mode, than you go back and enter on Developer Options and turn on USB Debugging)
4 - than put the cable and wait the computer says about missing driver... than unzip the "Blu Vivo Air.rar"(Google Generic ADB Driver modificated to BLU Vivo Air) and go on device manager and follow the photo steps on FAQ above
5 - now turn off the Antivirus Firewall to ADB Daemon Server can Work without any restrictions
6 - execute vRoot and follow the steps on screen (Any doubts search on Youtube how to follow that) and at final step on rooting the phone will restart and maybe the computer recognized a MT65xx Driver installation but that isn't need to root... than he will show Rooted status on vRoot program
7- after all that you allow file copy to get acess to internal storage from phone to put the Folder MRW from WolfDroid Script.zip on phone and follow this steps from this official video from WolfDroid (Just to remember, is need to install a Terminal emulator app from google market to do this step)
8 - after replace the chinese SU to SuperSU you go to google market and update the SuperSU to lasted update and execute SuperSU to update the binaries and reboot
9 - Finish the process ;D
- FAQ:
1 - Question: Modificated Blu Vivo Air ADB Driver installation
Answer: you can try follow this steps from original Driver developer on Brazilian Forum (Just to remember.. the driver download already have all customizations about he describe on photos... LINK) or just follow this photos/steps on above
Go to Device Manager and right Click to select Update driver selected
{
"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"
}
Click on Browse My Computer for driver software
Click Let me pick...
Click Show ALL...
Have Disk...
Search...
Go to located Unzip Folder and select Android_WinUSB.inf ... than click Open(or two click on .inf) and than OK
Select the Android Composite ADB Interface and click NEXT and Accept if he ask if you want install this driver anyway
Now you Installed your ADB Driver working :highfive:
Have any question, Commit above... i will try answer you and maybe i can put here on FAQ to everyone :highfive:
Google ADB Driver Modificated to Vivo Air download link is broken. Can you fix it please.
broken link
there is a broken link in your post. can you please fix it. I'm trying to flash my vivo air.
thanks
DvDwx. said:
Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war
* or the current economic crisis caused by you following these directions.
* So don't be an *** ****
*/
DO NOT TAKE AN OTA WHILE ROOTED!!! YOU WILL HAVE A BRICK IN YOUR HANDS!!!
Hi, For while i try Root my Vivo Air and don't get much success with it... so i try a new ADB Driver* and that works :highfive:
Using vRoot you can easy root your phone BUT the problem is the Chinese SuperSU... so i get on Google a Script who Replace the Chinese SU to XDA's @Chainfire SuperSU :highfive:
So follow the Steps ;D
1 - Download vRoot , ADB installer (Just to have sure about the drivers) , Google ADB Driver Modificated to Vivo Air (Driver without Signature =/ ) and WolfDroid Script
2 - Install vRoot and ADB Installer on computer ;D
3 - Turn ON the USB Debugging ... (if you put the cable but don't appear the option to turn it on, go on settings -> about Device and click over "Build Number" 5 times to get developer Mode, than you go back and enter on Developer Options and turn on USB Debugging)
4 - than put the cable and wait the computer says about missing driver... than unzip the "Blu Vivo Air.rar"(Google Generic ADB Driver modificated to BLU Vivo Air) and go on device manager and follow the photo steps on FAQ above
5 - now turn off the Antivirus Firewall to ADB Daemon Server can Work without any restrictions
6 - execute vRoot and follow the steps on screen (Any doubts search on Youtube how to follow that) and at final step on rooting the phone will restart and maybe the computer recognized a MT65xx Driver installation but that isn't need to root... than he will show Rooted status on vRoot program
7- after all that you allow file copy to get acess to internal storage from phone to put the Folder MRW from WolfDroid Script.zip on phone and follow this steps from this official video from WolfDroid (Just to remember, is need to install a Terminal emulator app from google market to do this step)
8 - after replace the chinese SU to SuperSU you go to google market and update the SuperSU to lasted update and execute SuperSU to update the binaries and reboot
9 - Finish the process ;D
Click to expand...
Click to collapse
DvDwx. said:
- FAQ:
1 - Question: Modificated Blu Vivo Air ADB Driver installation
Answer: you can try follow this steps from original Driver developer on Brazilian Forum (Just to remember.. the driver download already have all customizations about he describe on photos... LINK) or just follow this photos/steps on above
Go to Device Manager and right Click to select Update driver selected
Click on Browse My Computer for driver software
Click Let me pick...
Click Show ALL...
Have Disk...
Search...
Go to located Unzip Folder and select Android_WinUSB.inf ... than click Open(or two click on .inf) and than OK
Select the Android Composite ADB Interface and click NEXT and Accept if he ask if you want install this driver anyway
Now you Installed your ADB Driver working :highfive:
Have any question, Commit above... i will try answer you and maybe i can put here on FAQ to everyone :highfive:
Click to expand...
Click to collapse
I am having issues getting a custom recovery installed on this phone . I tried an app that allowed to choosed twrp or cwm and it installs succesfully but when i reboot recovery it still bots to stock. Being there is no option in dev options to unlock oem bootloader I belive this is causing the issue. Any ideas or links . Thanks in advanced
Links are invalid. Can some please post new links?
Yes
does anybody have the "ADB Driver Modificated to Vivo Air"?
link is dead. thanks!
Preparation:
1. Make sure that your computer installed a driver
(Download link here )
2. Flash tool (SP flash tool recommended, download link here )
Please be careful and make sure that you have enough knowledge or we suggest that don't root your phone casualy.
1. Download the file from below link. you're going to save to somewhere you can remember it, for this tutorial, I'm going to use my desktop.
Dnowload link here
2. Unzip the file that you have downloaded just now.
3. Cope zipe file named "superSU_PRO_V2.49.zip" to your SD card and then turn off the phone.
4. Open flash tool, Click "scatter-loading" and choose the file named "p7000-recovery" which you have just saved in your computer.
{
"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"
}
5.Click download and then connect your phone with computer.
6. When you see a picture as below that means you have installed the third party recovery successfully.
7. Move out the battery and then put it back, press "power" + "VOL +" to enter recovery mode. ("VOL -" to choose, "power" to confirm)
http://bbs.elephone.hk/data/attachment/forum/201506/11/164351v74mw4840lullmwr.png
8. Choose "install zip" by pressing "VOL -" ,
9.Go to "choosezip from /sdcard"
10. Choose "superSU_PRO_V2.49.zip" , press "power" key to confirm.
11. Choose "yes-install superSU_PRO_V2.49.zip", press "power" key to confirm.
12. Congratulations!!! You have finished the whole process, now enjoy.
You can also root without flashing recovery.
1) Download and install SuperSU from Play Store, don't run it yet.
2) Enable USB Debugging and install ADB drivers.
3) Download this ZIP http://www37.zippyshare.com/v/SaH4NxFw/file.html , unzip to a folder and open command prompt in it.
4) Issue the following commands:
Code:
adb kill-server
adb root
adb connect localhost:5037
adb shell setenforce 0
adb shell mkdir -p /data/local/tmp/supersu/arm64
adb push su /data/local/tmp/supersu/arm64/
adb push supolicy /data/local/tmp/supersu/arm64/
adb push libsupol.so /data/local/tmp/supersu/arm64/
adb push update-binary-adb-arm64-v8a-21 /data/local/tmp/supersu/
adb shell chmod 0755 /data/local/tmp/supersu/update-binary-adb-arm64-v8a-21
adb shell /data/local/tmp/supersu/update-binary-adb-arm64-v8a-21
5) Don't reboot, run SuperSU, choose normal install, done.
Thanks
Thanks for all your work !
I followed all the directions and disabled the driver signature verification on my Windows 8.1 computer. I have a problem that when I plug in the phone to the computer (with the phone off) the computer recognizes it for a few seconds and then it does not anymore. I get the boopoopoop sound to incidate it is connected and the boopbum noise five seconds later indicating that it is off. Can anyone help?
GCbard said:
I followed all the directions and disabled the driver signature verification on my Windows 8.1 computer. I have a problem that when I plug in the phone to the computer (with the phone off) the computer recognizes it for a few seconds and then it does not anymore. I get the boopoopoop sound to incidate it is connected and the boopbum noise five seconds later indicating that it is off. Can anyone help?
Click to expand...
Click to collapse
If you can access adb (turn on debug mode in developer settings), then try my method above. No need to use preloader driver.
eLeKtriK EyE said:
If you can access adb (turn on debug mode in developer settings), then try my method above. No need to use preloader driver.
Click to expand...
Click to collapse
Thank you. I tried but the phone is not recognized as ADB. I have usb debugging checked and it still does not work. I even have all the drivers installed. Any suggestions?
Try with another computer, it must be windows 8 fault.
GCbard said:
Thank you. I tried but the phone is not recognized as ADB. I have usb debugging checked and it still does not work. I even have all the drivers installed. Any suggestions?
Click to expand...
Click to collapse
Download latest mtk droid tool's, i upload this some time's ago, this is Link.
https://mega.co.nz/#!2V9SRCRZ!xYn52zbVEfGze4zCyaUkfwStCUe0tt408IBpR-Tq-Fo
And here i add android commander. Try. For me working, but MTK DT no fully work
GCbard said:
I followed all the directions and disabled the driver signature verification on my Windows 8.1 computer. I have a problem that when I plug in the phone to the computer (with the phone off) the computer recognizes it for a few seconds and then it does not anymore. I get the boopoopoop sound to incidate it is connected and the boopbum noise five seconds later indicating that it is off. Can anyone help?
Click to expand...
Click to collapse
i had the same issues when i first tried flashing the device, some moderator in the eleforum stated that's normal for the phone to act like that, because it will just detect to flash for 1.5 sec and then jump into charging mode
do this steps and should work fine
1 - DO not connect the phone to the computer
2 - open the flash tool
3 - look for the scatter.txt file that you want to flash "either rom or recovery"
4 - click download on the top
5 - once the processes above have been done, connect the device and it will start the flashing process.
you are done.
TopoX84 said:
i had the same issues when i first tried flashing the device, some moderator in the eleforum stated that's normal for the phone to act like that, because it will just detect to flash for 1.5 sec and then jump into charging mode
do this steps and should work fine
1 - DO not connect the phone to the computer
2 - open the flash tool
3 - look for the scatter.txt file that you want to flash "either rom or recovery"
4 - click download on the top
5 - once the processes above have been done, connect the device and it will start the flashing process.
you are done.
Click to expand...
Click to collapse
Thanks! It worked.
I tried it , once I click download. I don't see it downloading anything. 0 b/s and -0 bytes.
TopoX84 said:
do this steps and should work fine (add : turn phone off)
1 - DO not connect the phone to the computer
2 - open the flash tool
3 - look for the scatter.txt file that you want to flash "either rom or recovery"
4 - click download on the top
5 - once the processes above have been done, connect the device trough usb cable (phone still off)
6- then turn it on and it will start the flashing process.
you are done.
Click to expand...
Click to collapse
Worked fine here (added some steps), did not install it from sd card as it is still in the old phone :
choosed install zip from last folder and then move to the folder where it is ( vol + /- to scroll down, power to validate). I put it on download folder (on the phone memory), but of course you can put it anywhere you want !
Very smooth install, thx for the great tutorial
Help me
Followed all your directions, when I click on download, nothing happens
yeah same here when I press "Download" nothing happens (Windows 8.1 x32)
If I use one of these methods to root my P7000, enable Link2SD and then unroot it, can I retain the Link2SD features?
I want to be able to install/move apps onto the SD card but I don't really want or need a rooted phone in the long term.
Re upload recovery:
adf . ly/1NoLAj
(without the spaces)
Hi, could you anybody please reupload files with CWM and Supersu.zip? The link doesn´t work
Edit: Sorry, the link is working, error in my browser
download link has broken. T_T
I've got " the load scatter file is invalid" is there any way to get through this problem? I've already tried different versions of SP flashtool still got the same. Files downloaded from Devblaze who reuploaded them! The first post's links don't work.
Procedure for making your computer ready for executing fastboot commands
Link for vedio demonstration : https://youtu.be/1amTkFxlQUY
2nd part of the vedio instruct how to install adb drivers
1 ) Install ADB drivers in windows using below link
https://drive.google.com/file/d/1lZ2pZLne6TV9YJLmS9P_EAteuAZn_BPs/view?usp=drivesdk
2) Download platform tools link :
https://drive.google.com/file/d/1HUAUNJnlOKUJCxSqVxNVRagV4XBGe-2Q/view?usp=drivesdk
2 ) extract it
3) whenever you want use fastboot commands
Goto platform tools and paste required file in platform tools folder
4) then from platform tools folder open Power shell or command prompt using (shift + right click ) in empty space
Then it will open command promt then you can execute fastboot commands
5 ) once check whether you installed ADB drivers perfectly or not by using this command
adb devices
If it does shows any devices
Then follow below link
https://youtu.be/LbAq6d2Du0U
That's it now your computer can be used for executing fastboot commands
There have some easy steps for solve it....
1) download platform-tools_r33.0.3-windows and Fastboot Driver go through the link
2) Type on Loaction url place "cmd" and hit enter
{
"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"
}
3) It will open same folder through CMD
4) type "adb devices"
Note! make sure that time your phone in user mode not fastboot mode
5) Then it will show your phone in cmd (Its not showing download and install adb drivers / MTP drivers and usb drivers to your PC links are below)
Xiaomi USB Driver Windows 32-bit/64-bit Download
Download the latest Xiaomi USB Driver for Windows from here. We have shared the official Xiaomi USB Driver for Windows to download.
mydrivers.online
Xiaomi ADB Driver [Download] for Windows 32-bit/64-bit
Download the latest and official Xiaomi ADB Driver for Windows 32-bit and 64-bit versions. We shared the official Xiaomi ADB Driver.
mydrivers.online
Xiaomi MTP Driver Download free Latest for Windows
Download the latest Xiaomi MTP Driver for Windows from here. The updated Xiaomi MTP Driver is provided here to download free for OS.
mydrivers.online
6) after that you confirm it using device manager
7) Then after go to cmd again type "adb reboot fastboot"
8) It will reboot to fastboot mode
9) Type in cmd "fastboot devices" (adb command only work in usermode)
10) Then it will show your phone in cmd (Its not showing download Fastboot Driver above I mentioned)
%% How to install FASTBOOT drivers %%
1) go to computer management
2) find android devie
3) click left click and click update driver
4) Brows in my computer > let me pick drivers > Have Disk >Browse> (select file in fastboot folder "android_winusb" andd hit enter )
Then it will show your phone in cmd fastboot mode
Enjoy it!!
LINK -- https://mega.nz/folder/7QMR0AJS#oS8CHzrAsY3Y0kl9ABBZrQ
more info refer - https://xiaomi.eu/community/threads/fastboot-mode-device-not-listed-resolved.63817/