- Deleted -
I made this when i was noob and i thought that for disabling adb security i made something very cool that could help a lot.
good job I'll be doing tests
it says that it finishes installing but it does not initiate me with the keys nor with fastboot
Hello everyone! I modified this port of the CWM recovery from the Sony Xperia M to allow by default adb commands like adb shell, etc.
Installation: (you need to have installed LK Bootloader)
1) Download the recovery from below.
2) Open fastboot and type fastboot flash recovery ´path to file adb-cwm.img´ and then press enter.
3) After flashing the recovery, remove the battery and add the battery.
Hi! Can you create new link for LK Bootloader? bcs any link not worked in xda!!! PLS
Related
hi everyone,
I'm coming from this thread http://forum.xda-developers.com/showthread.php?t=1834761
I have been stuck for more than one week now and i didn't find any solution.
My problem is that I'm currently stock in a clockworkmod recovery boot loop on my Asus Transformer Prime without adb/fastboot connection:
1 - I had install CM9 stable on my Transformer Prime, after a wide data and then send throw "adb push" the CM9.zip,
2 - I reboot by CM9 in recovery mod to install Gapps,
3 - I install the Gapps zip,
4 - I ask to clockworkmod to reboot,
5 - Since then I'm in a clockworkmod recovery boot loop without adb/fastboot connection (witch used to be working),
If kown how can I get adb/fastboot connection back to be able to find my device with the adb command " adb devices " and then be able to send this command => " dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 "
Thank you for your understanding,
Kind regards,
Adb and fastboot are two different things... Fastboot is obtained buring booting process with vol down pressed, then not selecting recovery with volume up. So you should have fastboot access.
In this case I would suggest to fastboot flash TWRP (see on their website for instructions) it will perhaps fix things or at least give you adb access.
If you use cwm take the old 5.8.2.0 modded for not looping with reboot to recovery feature, or stay with twrp.
I would look at the following thread for unbricking the TF201:
http://forum.xda-developers.com/showthread.php?t=1514088
Sounds like you might fall into Option 1a.
I was having your same issue but it was because I rebooted into recovery from the reboot option on the CM10 rom. In any event, I couldn't get adb to work or recognize my device no matter what. I then decided to use my macbook pro. I can tell you that using adb on a mac is much easier as you don't have to download the drivers or sdk, just the platform tools. Here's a link: http://forum.xda-developers.com/showthread.php?t=1387527. I know this may not help if you or someone you know doesn't have a mac, but it saved me.
So I'm in the process of trying to Root my ZTE Smarttab 10 on firmware v03b.
Ive been following instructions on the following pages:
http://forum.xda-developers.com/showthread.php?t=1629630
http://forum.xda-developers.com/showthread.php?t=1473555
The instructions are spread out across those threads and my problem starts kind of early in the process.
My goal is to use ADB to boot in to the Bootloader and then use a recovery rom to use TWRP to install a rom.
What i have done:
I have installed the ZTE Drivers
I have installed the SDK tools and updated it.
Now when the tablet is running normally I can see it in ADB and is able to run the command.
ADB Reboot Bootloader
This reboots the devices to a black screen (I assume this is the bootloader) and windows recognizes that a device is there.
The problem is that when I try to see this from ADB i cannot see the device when running ADB Devices.
This makes the next step impossible as I need to use ADB to boot a recovery rom.
So I would have posted in the development treads listed above but as I dont have 10 posts (this being my first post) I cannot post in the threads above.
I'm confident that this is a driver problem and I have uninstalled and re-installed all the drivers related to this including SDK.
But no luck yet.
Where other people say they have succeeded is when in the device manager they have ADB interface and ZTE Handset ADB interface listed.
This is the state where I'm at but I still cannot see the device in ADB.
Anyone have any insight on this kind of problem and can offer any help for a solution or direction to get to the solution.
Thank you for your help and attention!
//Nagarutu
Vodafone (ZTE) SmartTab10 3.2 HoneyComb
You can't use adb in bootloader mode, you want fastboot. So when you do 'adb reboot bootloader'. It reboots to the black screen (that is the bootloader). Try typing 'fastboot devices' and see if you're device comes up. It should if you have all drivers installed correctly and fastboot on your system. Then you'll be able to do 'fastboot flash recovery recovery.img' to install the custom recovery, then a 'fastboot reboot' and lastly an 'adb reboot recovery' will get you into your custom recovery to flash a new rom. Don't forget to make a backup.
matt4321 said:
You can't use adb in bootloader mode, you want fastboot. So when you do 'adb reboot bootloader'. It reboots to the black screen (that is the bootloader). Try typing 'fastboot devices' and see if you're device comes up. It should if you have all drivers installed correctly and fastboot on your system. Then you'll be able to do 'fastboot flash recovery recovery.img' to install the custom recovery, then a 'fastboot reboot' and lastly an 'adb reboot recovery' will get you into your custom recovery to flash a new rom. Don't forget to make a backup.
Click to expand...
Click to collapse
Thank you for the help ! it cleared things up for me.
Now the trouble's continue.
With the firmware im on (v03b) you cannot use the fastboot flash method but only fastboot.
And they way it is supposed to be done is that you run
fastboot boot recovery.img (recovery being a twrp recovery for my device)
When its booted to TWRP i should be able to see it in ADB to be able to run the following commands to it:
--> adb remount
--> adb shell
--> ln -s /system/xbin/su /system/bin/su
However I cannot get it to show in ADB (or fastboot) when its booted in to TWRP.
Any ideas?
I managed to solve the last bit to.
Now it was actually a driver problem, so i just updated the driver in device manager and located the ADB driver from ZTE and it worked to boot in to TWRP and then to flash the device.
Now I have CM10 installed and is smiling!
Took me 4 days but damn it its done!
Thanks for the help!
Glad you've figured it out
1a
2a
3a
4a
5a
hi
I have sony ericsson neo v(MT15i) with unlocked bootloader
my phone is locked with password and I do not know the password.(I need my contacts and other data) , adb debug is not active
I want to install cwm via fastboot , then I will be able to install aroma file manager and I will be able to delete "password.key' and "gesture.key"
if you have adb and fastboot in your pc the only way i can help is this:unzip recoveryneo.zip and get recoveryneo.img.put it in androidsdk/tools.(you must have fastboot there too).then in terminal type:
Code:
fastboot devices (you must see the SN of your device)
fastboot boot recoveryNeo.img
after finish
fastboot reboot
this will not install cwm on your phone.this will just boot in recovery without install it.after you reboot there is no recovery.
Hello
A newbie here ...
My new phone "Lenovo Vibe C (A2020)" does not allow me to install any kind of custom recovery on it, I tried the following methods ...
1- SP Flash Tool: doesn't detect my phone at all, even after installing all drivers (Qualcomm, MTK, Etc ,,, ).
2- Adb and fastboot: whenever I try to flash a recovery, it only shows (waiting for a device) command, even after being detected by "adb devices" command, and showing device ID.
3- flashing apps: I used flashify and thrasher, at the beginning they both show a successful flashing process, up until rebooting to recovery, then only shows "Lenovo" logo for a second right before turning the phone off.
that's what i did, any help would be appreciated.
Note: the phone isn't even indexed in the site's database ... I wonder why!
You should unlock the bootloader first after rooting your device
Hello there. I do hope that you can still boot your device normally. If you can, please do make a backup of your rom.
(a) Download and install the latest driver for your device
(b) Download the latest adb and fastboot tool (I recommend Minimal ADB and Fastboot)
(c) Download the custom recovery image. Save/copy it on the root directory of your ADB and Fastboot folder.
(d) In your device, go to settings > developer > enable oem unlocking and usb debugging (which is I guess you already did).
(e) Now open your terminal/cmd: adb reboot bootloader (this will boot your device in fastboot)
(f) In terminal/cmd: fastboot oem unlock (or fastboot oem unlock-go)
(g) Now flash the custom recovery: fastboot flash recovery "recovery.img"
***I suggest you try first if the custom recovery image works: fastboot boot recovery.img
(h) Reboot into recovery and check if it works.
Ospider said:
Hello
A newbie here ...
My new phone "Lenovo Vibe C (A2020)" does not allow me to install any kind of custom recovery on it, I tried the following methods ...
1- SP Flash Tool: doesn't detect my phone at all, even after installing all drivers (Qualcomm, MTK, Etc ,,, ).
2- Adb and fastboot: whenever I try to flash a recovery, it only shows (waiting for a device) command, even after being detected by "adb devices" command, and showing device ID.
3- flashing apps: I used flashify and thrasher, at the beginning they both show a successful flashing process, up until rebooting to recovery, then only shows "Lenovo" logo for a second right before turning the phone off.
that's what i did, any help would be appreciated.
Note: the phone isn't even indexed in the site's database ... I wonder why!
Click to expand...
Click to collapse
Check my thread for custom marshmallow rom and twrp recovery .
https://forum.xda-developers.com/android/general/bliss-rom-lenovo-vibe-c-a2020a40-t3567812
rolland.arriza said:
Hello there. I do hope that you can still boot your device normally. If you can, please do make a backup of your rom.
(a) Download and install the latest driver for your device
(b) Download the latest adb and fastboot tool (I recommend Minimal ADB and Fastboot)
(c) Download the custom recovery image. Save/copy it on the root directory of your ADB and Fastboot folder.
(d) In your device, go to settings > developer > enable oem unlocking and usb debugging (which is I guess you already did).
(e) Now open your terminal/cmd: adb reboot bootloader (this will boot your device in fastboot)
(f) In terminal/cmd: fastboot oem unlock (or fastboot oem unlock-go)
(g) Now flash the custom recovery: fastboot flash recovery "recovery.img"
***I suggest you try first if the custom recovery image works: fastboot boot recovery.img
(h) Reboot into recovery and check if it works.
Click to expand...
Click to collapse
But how about a person WITHOUT PC? Including me.
My le eco le pro 3, during a normal day, stopped working.
If i try to turn it on i see the "LeEco powered by android" and after 10 seconds it turns off with a blue led.
I can not access the recovery mode, only the fastboot mode.
What fastboot command do i have to do to fix this? :crying:
If you can reach fastboot that is great already, i dont know if they bundle their devices with a recovery so you'll need to find a recovery for your device (quick google search, look for TWRP)
Also grab the drivers for your phone so you'll be able to write the recovery you downloaded.
Download the Google Universal ADB + Fastboot package (the 10 seconds installer)
Once everything is done, you'll need to go to the folder containing ADB and Fastboot with a command prompt
In the same folder you put the downloaded recovery. Put your phone in recovery mode, plug it, and type in the cmd : fastboot devices
If it recognize something you are good to go, you type fastboot flash recovery recoveryname.img
Then lookup for a Rom, i'm sure there is plenty of it, you'll flash the Rom either with sideload or if you have TWRP via Transfer
Gtahero74 said:
If you can reach fastboot that is great already, i dont know if they bundle their devices with a recovery so you'll need to find a recovery for your device (quick google search, look for TWRP)
Also grab the drivers for your phone so you'll be able to write the recovery you downloaded.
Download the Google Universal ADB + Fastboot package (the 10 seconds installer)
Once everything is done, you'll need to go to the folder containing ADB and Fastboot with a command prompt
In the same folder you put the downloaded recovery. Put your phone in recovery mode, plug it, and type in the cmd : fastboot devices
If it recognize something you are good to go, you type fastboot flash recovery recoveryname.img
Then lookup for a Rom, i'm sure there is plenty of it, you'll flash the Rom either with sideload or if you have TWRP via Transfer
Click to expand...
Click to collapse
Thank you so much.
I have type c broken, so i cannot plug it into my pc (i have found replacement).
I found this guide https://forum.xda-developers.com/le-pro3/how-to/flashing-guide-roundup-leeco-le-pro-3-t3511901
If i don't want to root, do i have to unlock the bootloader anyway?
It might be a stupid question, but I do not know much about this.
Yeah you will need to unlock the bootloader in order to flash a new rom
But roms aren't rooted so you can relock your bootloader after