Im starting this new thread because I was not able to find a solution for my problem for about 2 weeks now.
Issue : Unable to install recovery. Im trying to install recovery by following this thread : http://forum.xda-developers.com/showthread.php?t=2221102 - in the 3rd step when i flash the recovery i get this error "command write failed - unknown error"
- tried almost all the different types of steps available in xda and also outside xda.
My Environment:
Win8 Pro 32bit
LG optimus L9 flashed and rooted by lelus method - Current ROM - P76020c
Installed all LG drivers - PC suite is installed
Have SDK manager installed
Device is recognized when I run the "adb devices" command keeping phone switched on.
Device is recognized when I run the "fastboot devices" command when phone is in fastboot mode.
So I guess this is not a driver issue.
Im also attaching screenshots of the error and the commands that I have ran ....
SOOOOOOOOOOOO ... whats the prob here .... ... anyone faced this same prob ???? HELPPPP
rkn989 said:
Im starting this new thread because I was not able to find a solution for my problem for about 2 weeks now.
Issue : Unable to install recovery. Im trying to install recovery by following this thread : http://forum.xda-developers.com/showthread.php?t=2221102 - in the 3rd step when i flash the recovery i get this error "command write failed - unknown error"
- tried almost all the different types of steps available in xda and also outside xda.
My Environment:
Win8 Pro 32bit
LG optimus L9 flashed and rooted by lelus method - Current ROM - P76020c
Installed all LG drivers - PC suite is installed
Have SDK manager installed
Device is recognized when I run the "adb devices" command keeping phone switched on.
Device is recognized when I run the "fastboot devices" command when phone is in fastboot mode.
So I guess this is not a driver issue.
Im also attaching screenshots of the error and the commands that I have ran ....
SOOOOOOOOOOOO ... whats the prob here .... ... anyone faced this same prob ???? HELPPPP
Click to expand...
Click to collapse
As always, use at your own risk.
Upload recovery image to sdcard and change the file name to recovery.img if that helps
flash via adb from your computer
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
or terminal emulator straight from the phone
Code:
su
busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
Lelus said:
flash via adb from your computer
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
[/QUOTE]
is this the exact code that we should type into the cmd after getting to fastboot mode ??? or shud this be ran while phone is switched on ???
Click to expand...
Click to collapse
rkn989 said:
is this the exact code that we should type into the cmd after getting to fastboot mode ??? or shud this be ran while phone is switched on ???
Click to expand...
Click to collapse
phone switched on, usb mode: camera or lg software
btw, you have unlocked the bootloader , right ?
Lelus said:
phone switched on, usb mode: camera or lg software
btw, you have unlocked the bootloader , right ?
Click to expand...
Click to collapse
yess .... my bootloader is unlocked ....
tried this and get an error - su not found - check screenshot
im not getting the command that we tried :
adb shell su -c busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
"su" stands for ???
and where should i copy the .img file to ?? (i copied it to the root of the ext sd card)
anyone any suggestions ?????
May be your file is corrupt. Just give it a try.
Download latest version of CWM Touch and Non-touch version from http://www.clockworkmod.com/rommanager and try again.
cmahendra said:
May be your file is corrupt. Just give it a try.
Download latest version of CWM Touch and Non-touch version from http://www.clockworkmod.com/rommanager and try again.
Click to expand...
Click to collapse
Ive already tried that ... have tried downloading the files many times .. already have 4-5 copies of both the normal and touch recoveries ...
Its the same error !!!!!!
And yu want me to try by the fastboot method rite ?? not the method lelus juzz said ???
Lelus said:
flash via adb from your computer
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
or terminal emulator straight from the phone
Code:
su
busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
Click to expand...
Click to collapse
Can yu explain this in more detail. ????
Sent from my LG-P760 using xda app-developers app
rkn989 said:
Ive already tried that ... have tried downloading the files many times .. already have 4-5 copies of both the normal and touch recoveries ...
Its the same error !!!!!!
And yu want me to try by the fastboot method rite ?? not the method lelus juzz said ???
Click to expand...
Click to collapse
Lelus is explaining you in details and he is expert here. I am just confirming that if you have tried the basic things or not. By the way, your fastboot drivers seem working as device responds to "fastboot devices" command properly.
The fastboot screen should show the phone is unlocked or not, exactly like this....does it show like this screenshot?
SW Upgrade mode also should show unlocked like this screnshot.
If not, you may not be yet Unlocked and fastboot will not work.
cmahendra said:
Lelus is explaining you in details and he is expert here. I am just confirming that if you have tried the basic things or not. By the way, your fastboot drivers seem working as device responds to "fastboot devices" command properly.
The fastboot screen should show the phone is unlocked or not, exactly like this....does it show like this screenshot?
SW Upgrade mode also should show unlocked like this screnshot.
If not, you may not be yet Unlocked and fastboot will not work.
Click to expand...
Click to collapse
I din know where exactly to run those commands, so asked detailed steps
And the my bootloader is unlocked, I get the fastboot boot mode when I run the adb reboot command to unlock bootloader, yday when I flashed my phone with v20c, I gt the second screenshot as yu mentioned, also i tried running that *# command from inside the phone and it showed bootloader status- unlock.
So I hope it is unlocked! !!
Sent from my LG-P760 using xda app-developers app
ATLASTTT !!!!!!!!!!!!! I have succeeded in flashing my recovery .....
but the resolution is strange .... it just worked fine in WIN7 .... isn't that strange ???????????
Related
I looked all over the internet for help with this phone. I rooted it for a friend and a week later, he said he restarted the phone and everything started force closing.
I troubleshot all day, and came to figure out that my only known to me as of now, is flashing CWM to it, via ADB. I am having several issues with setting up ADB, and getting the phone to communicate with my computer. Device manager DOES show that there is an ADB device installed correctly, so what would my next move be? I got the phone into FTM mode, (fastboot?) and I know that that is what I need to do to get ADB to communicate with my phone.
halp pls
Really no one can help???
bamp
cammiso94 said:
bamp
Click to expand...
Click to collapse
ADB Drivers for Windows Vista/7
Tutorial- http://www.youtube.com/watch?v=RDA8PpPSFuk
If you havn't found this yet...
Your answer is here: androidforums.com/flash-all-things-root/ Good luck!:good:
CWM Beta
From Android Forums ... Thanks to Junkie2100
this is an unfinished copy of cwm, tested to be almost completely functional
standard warnings apply, use at your own risk, you try to blame me for breaking your phone i will laugh at you
instructions:
fastboot method is possible, but i will go through the terminal/adb method
download the recovery file, and put it on the root of your sd. no folders, just directly on the sd
get your phone rooted and get a copy of terminal emulator or connect to it through adb on your computer, adb will require zte drivers and the adb program on the pc. the choice is yours
fire up adb by typing
Code (Text):
adb shell
in the command prompt, if its not working you dont have adb in the directory youre in, just copy adb.exe and the two .dll files to c:\windows\system32\ and itll work from anywhere, or learn how command prompt works
or fire up terminal emulator on the phone
on adb shell or terminal emulator type
Code (Text):
su
dd if=/sdcard/flash_cwm_test2.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
you will then need to run
Code (Text):
reboot recovery
and then hit reboot when cwm comes up, if it asks to disable recovery flashing press yes or it will put stock recovery back next time the rom boots
known bugs:
unmounting doesnt work
downloads:
w.ww.4shared.com/file/2qBR2Kfr/flash_cwm_test2.html
i apologize for it being 4shared, if someone wants to make a mirror ill put it up
Okay so as we all know Bootloader was unlock and they specify the steps, but im not able to do the command prompt section.(Below)
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/twrp-2.8.0.0_vs985-signed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I have the twrp image on my storage, but i used mtp not Ethernet due to the reason that Ethernet mode won't read my phone.
Can anyone help me on how to void my warranty and get CP working
Please no hating, barely learning this stuff
Thanks!!
You need to have USB debugging enabled on your phone, adb installed on your computer and the LG drivers installed. If you have all that the steps to unlock are quite clear.
Also your phone needs to be on and you need to keep an eye on it as you will have to enable a couple of things when they pop up on your phone, one is to allow your computer to see your phone in debugging mode and the other is to Grant super user permission.
batsup606 said:
Okay so as we all know Bootloader was unlock and they specify the steps, but im not able to do the command prompt section.(Below)
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/twrp-2.8.0.0_vs985-signed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I have the twrp image on my storage, but i used mtp not Ethernet due to the reason that Ethernet mode won't read my phone.
Can anyone help me on how to void my warranty and get CP working
Please no hating, barely learning this stuff
Thanks!!
Click to expand...
Click to collapse
You need to be able to get the phone operating in Ethernet mode; otherwise the computer cannot pass it commands. Alternatively, you can use a terminal emulator ON your phone itself. That's what I did as I didn't want to boot my desktop rig up before I left. It works exactly the same, except you don't type "adb shell", just open the term emu and start with the SU line.
It works fine if you do it from a terminal emulator on ur phone just fyi
laxattack said:
It works fine if you do it from a terminal emulator on ur phone just fyi
Click to expand...
Click to collapse
Can confirm. This is the way I did it since I don't have access to a computer until later tonight. Just type the exact commands (except for adb shell) in a terminal emulator and you are done.
I can also confirm this is working.
I had to download the LG updater or whatever (when you first plug the phone in; says installer) despite Win7 saying it had autoinstalled the drivers then ADB could see the device when in ethernet mode.
Also the last command didn't work (guess I didn't have the TWRP in the right place) and was forced to do a battery pull after the Factory Reset (didn't erase my data or settings), booted fine and then I just flashed the recovery with Flashify (and now can get into recovery) but YMMV.
FLASHIFY
Hey whats up the easiest way to install this is an app called Flashyify in play store works great im unlocked without using adb. Let the roms begin. Thanks for the hard work that everyone put in. Just put twrp image on phone before you open flashyify and open and install and recovery will be installed
airintak25 said:
Hey whats up the easiest way to install this is an app called Flashyify in play store works great im unlocked without using adb. Let the roms begin. Thanks for the hard work that everyone put in. Just put twrp image on phone before you open flashyify and open and install and recovery will be installed
Click to expand...
Click to collapse
+1
Hi, i have an acer liquid zest 4g t07, i cant find anyway on how to root it.
EDIT:
here's the solution https://forum.xda-developers.com/android/general/tutorial-root-acer-liquid-zest-4g-z628-t3534746
flamendless said:
Hi, i have an acer liquid zest 4g t07, i cant find anyway on how to root it.
Click to expand...
Click to collapse
Can you give me any information about your phone? model,kernel,android version,etc.
Ziisehahvulon said:
Can you give me any information about your phone? model,kernel,android version,etc.
Click to expand...
Click to collapse
According to CPU-Z
Model: T07 (t07_ww)
Manufacturer: acer
android version: 6.0
Api level: 23
Kernel: 3.18.19+(1469620262)
Would these suffice?
flamendless said:
According to CPU-Z
Model: T07 (t07_ww)
Manufacturer: acer
android version: 6.0
Api level: 23
Kernel: 3.18.19+(1469620262)
Would these suffice?
Click to expand...
Click to collapse
Do you have any any custom recoveries for your phone so we can flash a supersu.zip?
If not could you boot this recoveries I repeat boot not flash or install.
How to Boot into recovery without flashing:https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/
Custom Recovery:https://www.androidfilehost.com/?fid=24591023225178597
The custom recovery may not be for your phone but I have tried booting random recoveries to my phone similar to its specs and it worked!
SuperSU download in attachment
Is it possible to brick my device by that procedure?
flamendless said:
Is it possible to brick my device by that procedure?
Click to expand...
Click to collapse
Not the device but maybe the recovery but since you are booting it and not flashing it maybe it won't.I did this procedure to my phone but the 3g T06 model of acer liquid zest and it worked. Well I changed some links so that the recovery would be compatible for your chipset which is mt6735 and kernel 3.18.19+
PS.you need unlocked bootloader and developer options on for oem unlocking
Thank you, i will try that as soon as possible, although, whats the way to boot in bootloader in acer device?
flamendless said:
Thank you, i will try that as soon as possible, although, whats the way to boot in bootloader in acer device?
Click to expand...
Click to collapse
Turn off phone then hold power button and up button at the same time or you can boot in fastboot using ADB commands.
Make sure you have an unlocked bootloader and good luck!
PS. Unlocking bootloader formats the phone
Ziisehahvulon said:
Turn off phone then hold power button and up button at the same time or you can boot in fastboot using ADB commands.
Make sure you have an unlocked bootloader and good luck!
PS. Unlocking bootloader formats the phone
Click to expand...
Click to collapse
How to know if the bootloader is unlocked?
flamendless said:
How to know if the bootloader is unlocked?
Click to expand...
Click to collapse
I had problems for my phone but try this commands:
adb reboot bootloader
fastboot getvar all or fastboot oem device-info
if that doesnt work try:
adb shell
su
cat /proc/mtd
Ziisehahvulon said:
I had problems for my phone but try this commands:
adb reboot bootloader
fastboot getvar all or fastboot oem device-info
if that doesnt work try:
adb shell
su
cat /proc/mtd
Click to expand...
Click to collapse
Im in fastboot mode, but the device is not listed in adb
flamendless said:
Im in fastboot mode, but the device is not listed in adb
Click to expand...
Click to collapse
ADB cannot detect phone if in fastboot mode but fastboot commands can be accepted while adb commands cannot while in fastboot mode
after typing adb reboot bootloader type this command while in fastboot mode
fastboot get var all or just var if that doesnt work try fastboot oem device-info
if that doesnt work either reboot your phone not in fastboot mode type fastboot reboot then type this commands while you are in home screen
adb shell
su
cat /proc/mtd
Ziisehahvulon said:
ADB cannot detect phone if in fastboot mode but fastboot commands can be accepted while adb commands cannot while in fastboot mode
after typing adb reboot bootloader type this command while in fastboot mode
fastboot get var all or just var if that doesnt work try fastboot oem device-info
if that doesnt work either reboot your phone not in fastboot mode type fastboot reboot then type this commands while you are in home screen
adb shell
su
cat /proc/mtd
Click to expand...
Click to collapse
It just says waiting for device
flamendless said:
It just says waiting for device
Click to expand...
Click to collapse
do you have drivers for fastboot and adb?
If you do and still get errors get the latest version
When the cmd says waiting for device make sure that the device is in fastboot mode
its just a black screen with a text fastboot mode
Ziisehahvulon said:
do you have drivers for fastboot and adb?
If you do and still get errors get the latest version
When the cmd says waiting for device make sure that the device is in fastboot mode
its just a black screen with a text fastboot mode
Click to expand...
Click to collapse
Yes i have fastboot and adb, and yes the screen is black and theres a text at the bottom left that says fastboot mode
flamendless said:
Yes i have fastboot and adb, and yes the screen is black and theres a text at the bottom left that says fastboot mode
Click to expand...
Click to collapse
Try the version of adb and fastboot that I used
Ziisehahvulon said:
Try the version of adb and fastboot that I used
Click to expand...
Click to collapse
still says waiting for device,
flamendless said:
still says waiting for device,
Click to expand...
Click to collapse
That can be caused if you dont have drivers installed and are you sure you have developer options on and usb debugging on? Also bootloader unlocked?
Hmm can you give me a picture of the procedure?
Pic of the device and the pc.
The picture of the device while the pc is saying waiting device and vice versa
Ziisehahvulon said:
That can be caused if you dont have drivers installed and are you sure you have developer options on and usb debugging on? Also bootloader unlocked?
Hmm can you give me a picture of the procedure?
Pic of the device and the pc.
The picture of the device while the pc is saying waiting device and vice versa
Click to expand...
Click to collapse
Yes, in the setting, the usb debugging is enabled, and the allow bootloader to be unlocked oem something, i also hve the proper drivers installed,
I think the bootloader is something thats quite not right, tell me whats the complete details about that.
Ill try to provide images.
flamendless said:
Yes, in the setting, the usb debugging is enabled, and the allow bootloader to be unlocked oem something, i also hve the proper drivers installed,
I think the bootloader is something thats quite not right, tell me whats the complete details about that.
Ill try to provide images.
Click to expand...
Click to collapse
I'll give you proper details later I need to go to school
I'm trying to root my phone on linux, but once i do adb reboot bootloader, my device is nowhere to be found. anyone have a fix? I've searched everywhere.
/thread
Fixed my own issue by plugging the usb cable in the back of my computer. yup, seriously. Thanks to everyone trying to help. Also, thanks for not pointing out what a noob I am.
yepimjosh said:
I'm trying to root my phone on linux, but once i do adb reboot bootloader, my device is nowhere to be found. anyone have a fix? I've searched everywhere.
Click to expand...
Click to collapse
I am not familiar with Linux but on Windows waiting for device comes up when the driver for that phone is installed. May be you can look into it for a solution.
Install the drivers and then give it a try.
yepimjosh said:
I'm trying to root my phone on linux, but once i do adb reboot bootloader, my device is nowhere to be found. anyone have a fix? I've searched everywhere.
Click to expand...
Click to collapse
You need to install adb fastboot these are the instructions you need to type in the terminal you just opened. Type one line at a time and press enter after each. Allow Ubuntu to do it's stuff.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
after you reboot to the bootloader you use fastboot commands ,not adb
clsA said:
You need to install adb fastboot these are the instructions you need to type in the terminal you just opened. Type one line at a time and press enter after each. Allow Ubuntu to do it's stuff.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
after you reboot to the bootloader you use fastboot commands ,not adb
Click to expand...
Click to collapse
I have adb. I'm trying to say, when I'm in recovery mode, my phone is no longer found on my computer. Not just adb, the whole computer
yepimjosh said:
I have adb. I'm trying to say, when I'm in recovery mode, my phone is no longer found on my computer. Not just adb, the whole computer
Click to expand...
Click to collapse
What recovery ? Stock recovery does not support adb
clsA said:
What recovery ? Stock recovery does not support adb
Click to expand...
Click to collapse
Sorry, I'm messing up what I'm trying to say. I have adb and fastboot installed, running on ubuntu 16.04. I plug my phone in, open Terminal, and run adb devies. My device pops up, it's there. So I run adb reboot bootloader, my phone goes on the white screen with the android fellow, and all is good. Now, I i try adb devices again, nothing. I put in lsusb (lists all usb devices connected to computer), and nothing. So, naturally, when i try fastboot oem unlock and my code, I'm stuck on <waiting for device>
yepimjosh said:
Sorry, I'm messing up what I'm trying to say. I have adb and fastboot installed, running on ubuntu 16.04. I plug my phone in, open Terminal, and run adb devies. My device pops up, it's there. So I run adb reboot bootloader, my phone goes on the white screen with the android fellow, and all is good. Now, I i try adb devices again, nothing. I put in lsusb (lists all usb devices connected to computer), and nothing. So, naturally, when i try fastboot oem unlock and my code, I'm stuck on <waiting for device>
Click to expand...
Click to collapse
adb does not work in the bootloader
After reboot bootloader it's fastboot devices
If you get no response try a different usb port
Or different usb cord
Sent from my SM-N920T using Tapatalk
clsA said:
If you get no response try a different usb port
Or different usb cord
Click to expand...
Click to collapse
used the rear usb port and magically decided to work, edited the original post. Thank you for your help and I apologize for the much noobiness you had to encounter.
I am having trouble rooting my Galaxy J7 Prime sm-j727t
Every Odin version I use with every TWRP tar file I try to use doesn't work. They either Fail or Odin stops responding when I try to load the tar file into the AP.
I've tried just using the CF Auto Root and those fail as well.
Any ideas what the issue is? I've been trying for two days with no success
Is your bootloader unlocked?
Emir Çetin said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
I thought Samsung phones come with bootloader unlocked already??
BramaKnox said:
I thought Samsung phones come with bootloader unlocked already??
Click to expand...
Click to collapse
You can check bootloader with dialer (search it).
Of phone has fastboot mode you can check bootloader with fastboot commands (search it too)
Emir Çetin said:
You can check bootloader with dialer (search it).
Of phone has fastboot mode you can check bootloader with fastboot commands (search it too)
Click to expand...
Click to collapse
When I put the phone in FastBoot mode I have the following options
Reboot System Now
Reboot to Bootloader
Apply update from ADB
Apply Update from SD card
Wide data/factory reset
Wipe Cashe partition
Mount /system
View recovery logs
Run graphics test
Power off
Lacking storage booting
1-Install your phones drivers on your PC.
2-Install adb and fastboot tools. https://www.addictivetips.com/android/download-adb-and-fastboot/
3-Reboot to fastboot.
4-Connect your phone with USB cable.
5-Open command prompt in adb and fastboot folder
6-Type fastboot devices (If you don't see your device there is a problem in drivers or fastboot)
7-Type fastboot oem device-info
You can check your bootloader status in that screen.
Emir Çetin said:
1-Install your phones drivers on your PC.
2-Install adb and fastboot tools. https://www.addictivetips.com/android/download-adb-and-fastboot/
3-Reboot to fastboot.
4-Connect your phone with USB cable.
5-Open command prompt in adb and fastboot folder
6-Type fastboot devices (If you don't see your device there is a problem in drivers or fastboot)
7-Type fastboot oem device-info
You can check your bootloader status in that screen.
Click to expand...
Click to collapse
Am I doing something wrong here ? see attached for screnshot
Emir Çetin said:
1-Install your phones drivers on your PC.
2-Install adb and fastboot tools. https://www.addictivetips.com/android/download-adb-and-fastboot/
3-Reboot to fastboot.
4-Connect your phone with USB cable.
5-Open command prompt in adb and fastboot folder
6-Type fastboot devices (If you don't see your device there is a problem in drivers or fastboot)
7-Type fastboot oem device-info
You can check your bootloader status in that screen.
Click to expand...
Click to collapse
I tried a some other steps. Tried using the video on youtube on a tut. When I get to the oem unlock I just get stuck with a msg sayng "waiting for any device" my device is plugged in, from what I know I have updated the samsung drivers (from previous attempt of other methods) the adb bootloader cmd did put my phone into fastboot mode
(White box, blue arrow point down with a straight line under the point)
(Blue screen with Downloading...)
do not turn off target
What am I missing here?
I tried rooting TWRP 3.2.3. with Odin on the phone again and it still failed
Does anyone else have any more insight to a possible solution?
Have you checked bootloader with dialer?
BramaKnox said:
I am having trouble rooting my Galaxy J7 Prime sm-j727t
Every Odin version I use with every TWRP tar file I try to use doesn't work. They either Fail or Odin stops responding when I try to load the tar file into the AP.
I've tried just using the CF Auto Root and those fail as well.
Any ideas what the issue is? I've been trying for two days with no success
Click to expand...
Click to collapse
Witch android you are?