Related
I tried to root my phone today by using the Nexus 4 toolkit. In the process of rooting the phone, the use connection is physically disconnect by myself well it was an accident. After that, I only got unlocked bootloader, but I am not be able to get the recovery and the SU in the phone. When I try to repeat the steps, it is stucking at " cannot connect device" or sometimes "failed ... unknown error" or even "protocol error"(if I remember correctly. It seems that the connection is gone between the phone and the desktop under the fastboot mode. But under the normal Android OS, I am able to connect my phone to desktop to do the data transfer things.
I am seeking for help here. I hope I explain my problem properly that you guys can understand. Here is error I got sometime when I connect my phone to PC.
The button is OK in the pic.
hilts425 said:
I tried to root my phone today by using the Nexus 4 toolkit. In the process of rooting the phone, the use connection is physically disconnect by myself well it was an accident. After that, I only got unlocked bootloader, but I am not be able to get the recovery and the SU in the phone. When I try to repeat the steps, it is stucking at " cannot connect device" or sometimes "failed ... unknown error" or even "protocol error"(if I remember correctly. It seems that the connection is gone between the phone and the desktop under the fastboot mode. But under the normal Android OS, I am able to connect my phone to desktop to do the data transfer things.
I am seeking for help here. I hope I explain my problem properly that you guys can understand. Here is error I got sometime when I connect my phone to PC.
The button is OK in the pic.
Click to expand...
Click to collapse
Accidently hit the thanks button
The phone`s bootloader is allready unlocked.
- Is the phone recognized in adb and fastboot mode? If not install the 0.72 usb naked drivers.
- Flash CWM recovery in fastboot mode from here http://clockworkmod.com/rommanager, choose touche or non touch.
- flash superSU 1.20 from here http://forum.xda-developers.com/showthread.php?t=1538053 in CWM recovery.
- Install BusyBox from Google Play.
- Done.
gee2012 said:
Accidently hit the thanks button
The phone`s bootloader is allready unlocked.
- Is the phone recognized in adb and fastboot mode? If not install the 0.72 usb naked drivers.
- Flash CWM recovery in fastboot mode from here http://clockworkmod.com/rommanager, choose touche or non touch.
- flash superSU 1.20 from here http://forum.xda-developers.com/showthread.php?t=1538053 in CWM recovery.
- Install BusyBox from Google Play.
- Done.
Click to expand...
Click to collapse
how do I flash cwm in fastboot?
hilts425 said:
how do I flash cwm in fastboot?
Click to expand...
Click to collapse
Install the android sdk platform-tools and once installed:
- open cmd terminal and type: adb reboot bootloader
- type: fastboot devices and you should see a serial number if the usb drivers are nstalled correctly
- then type: fastboot flash recovery recovery-(name of the recovery).img
Read some threads to get familiar with your phone and to learn how to flash, root, use adb and it`s commands etc etc.
gee2012 said:
Accidently hit the thanks button
The phone`s bootloader is allready unlocked.
- Is the phone recognized in adb and fastboot mode? If not install the 0.72 usb naked drivers.
- Flash CWM recovery in fastboot mode from here http://clockworkmod.com/rommanager, choose touche or non touch.
- flash superSU 1.20 from here http://forum.xda-developers.com/showthread.php?t=1538053 in CWM recovery.
- Install BusyBox from Google Play.
- Done.
Click to expand...
Click to collapse
the official recovery does not work now! Any ideas?
hilts425 said:
the official recovery does not work now! Any ideas?
Click to expand...
Click to collapse
Yes it works, but it will not flash the SU zip. You need a custom recovery for that.
gee2012 said:
Yes it works, but it will not flash the SU zip. You need a custom recovery for that.
Click to expand...
Click to collapse
OK when I choose the recovery I only appears the android robot with a "!" and I can not do nothing there. Is this a bad sign?
hilts425 said:
OK when I choose the recovery I only appears the android robot with a "!" and I can not do nothing there. Is this a bad sign?
Click to expand...
Click to collapse
ok when i flash the recovery in the cmd
it says
failed (command write failed unknown error.)
Hello,
I've rooted my device and installed the hellfire Kitkat rom. Since I was not fully satisfied I wanted to go back to stock rom and then install the latest update from LG.
But now the device only boots into recovery (CWM V6.0.4.7)
I can install a backup ROM but when I reboot it enters recovery again.
I tried entering download mode by pressing "volume UP key" and then plugin usb but it enters recovery again.
Can someone help me please?!
sander-w said:
Hello,
I've rooted my device and installed the hellfire Kitkat rom. Since I was not fully satisfied I wanted to go back to stock rom and then install the latest update from LG.
But now the device only boots into recovery (CWM V6.0.4.7)
I can install a backup ROM but when I reboot it enters recovery again.
I tried entering download mode by pressing "volume UP key" and then plugin usb but it enters recovery again.
Can someone help me please?!
Click to expand...
Click to collapse
I'm going to be cautious replying here because I'm a noob, but did you try using ADB to issue commands through adb sideload in cwm? If you go to "load zip" (or something along those lines) then "load using adb" (or something similar) in CWM, you can use adb to issue these commands with your computer and it should fix it (at least, it fixed a boot loop for me when I was stuck with TWRP). Here's the link:
http://forum.xda-developers.com/showthread.php?t=2451696
First of all. DON'T PANIC!
And even before that - make a nandroid backup! Go in CWM and make a full backup.
You have recovery working so you should be able to load System on it ok.
I am not an expert but let me try to guide you step by step.
1. Make a backup!
2. Download a rom on your computer. MAKE SURE ITS FOR YOUR MODEL # of LG G2
List of roms here:
3. Make sure you have over 70% battery
4. Go into recovery CWM
5. Use Wipe > Swipe to Factory Wipe
(go back on bottom right corner)
6. Go Advanced from HOME screen of CWM
7. Click ADB sideload
7b. (I assume you have the drivers loaded. If not make sure ADB is loaded in windows and device manager shows it. Download basic ADB package so you have "adb.exe" file in it)
8. put your rom in the same folder where you have "Adb.exe"
9. Open command prompt on windows. Goto the folder where ADB.exe is. Then Type "adb push (filename) /sdcard/(filename)". Example, "adb push rom.zip /sdcard/rom.zip"
10. Wait until it finishes its transfer(a message will appear saying the filename, file size and the speed of the transfer per sec when it finishes)
11. Wait for a while or reboot your cwm so that the filename will appear
12. just reflash the file in CWM (Install > choose file). Wipe after again.
13. Voila!
By any chance did you successfully go back to stock 4.2.2 and then took the OTA and then got the recovery loop? If so this will help http://forum.xda-developers.com/showthread.php?t=2451696
Drachenminister said:
By any chance did you successfully go back to stock 4.2.2 and then took the OTA and then got the recovery loop? If so this will help http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
I did manage to restore the backup rom of 4.2.2 Then I downloaded the 4.4 OTA update and installed it. Then it hangs in recovery.
Do I need to have TWRP installed or does this work with CWM too?!
sander-w said:
I did manage to restore the backup rom of 4.2.2 Then I downloaded the 4.4 OTA update and installed it. Then it hangs in recovery.
Do I need to have TWRP installed or does this work with CWM too?!
Click to expand...
Click to collapse
Basically what you need is a root shell whether it's via adb or built into recovery (cwm or twrp)
Searching the forum for "cwm bootloop ota" might give you detailed instructions for your case
Drachenminister said:
By any chance did you successfully go back to stock 4.2.2 and then took the OTA and then got the recovery loop? If so this will help http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
When I try to run "adb shell" I get a message "error: closed" what does it mean?
When I run adb devices it returns a serial number. so it looks like it is able to communicate with my g2.
sander-w said:
When I try to run "adb shell" I get a message "error: closed" what does it mean?
When I run adb devices it returns a serial number. so it looks like it is able to communicate with my g2.
Click to expand...
Click to collapse
Weird, you can try and add the commands directly enclosed in parentheses like adb shell "dd if=...."
Drachenminister said:
Weird, you can try and add the commands directly enclosed in parentheses like adb shell "dd if=...."
Click to expand...
Click to collapse
It seems that my device was in sideload mode. when I disabled sideload mode I followed the instructions on this pag
http://forum.xda-developers.com/showthread.php?t=2451696
And it worked!!!
Thanks for your help all!!!!
So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Edit: I solved my issue by downloader the stock B08 system on my S5 and then i placed it in the external sd. Then i put the SD back into the Axon and installed the system. After i had installed the system and booted into the OS i could enter adb with my device being recognized and after that i flashed twrp by using ADB.
I have a new problem though and that is that i can't install the 3.1.0.0. twrp. it only boots into black screen when i enter recovery. I can use the 3.0.4.0. version though.
You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?
senny22 said:
So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Click to expand...
Click to collapse
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?
nonamesl said:
You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?
Click to expand...
Click to collapse
Correct. It simply reboots.
Yup, i tried installing the B29 stock system on my G model and so i suppose i had the wrong bootstack becasue this is where my problems started.
I get to the stock android recovery.
raystef66 said:
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?
Click to expand...
Click to collapse
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.
senny22 said:
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.
Click to expand...
Click to collapse
You should see your phone as QUSB_BULK. Installed the ZADIG drivers ? That may cure the problem.
After that, imo, it is important you can reboot edl and flash TWRP recovery again AND when it recounts, you pull usb.
Normally you will have replaced recovery , reboot ok and you can enter TWRP and fastboot also.
ps : sometimes it is also advisable to go to ADB RECOVERY directly and do the processes.
ps2 : when TWRP backup, you can always put it on SD via other phone and in TWRP restore. Normaly you're good to go then...
Try the Marshall London Bootloader Interface driver maybe?
nonamesl said:
Try the Marshall London Bootloader Interface driver maybe?
Click to expand...
Click to collapse
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?
senny22 said:
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?
Click to expand...
Click to collapse
Installing the driver and using it for the phone (device manager -> change driver manually (or something of the sort)) worked for me, but it could differ. Let me know. You don't have to uninstall other drivers just use that specific one for your phone by switching the driver manually via device manager.
Hi guys,
Unable to boot after c*cking up a manual upgrade from B10 to B11 on my A2017G and would love your input. I feel like if I can just install TWRP again it should be an easy fix. Here's some specifics:
1. my phone is unlocked, rooted and running stock firmware.
2. I was trying to install stock recovery to install the B11 update. I did so but also tried to install another zip (B10 bootloader?) which I seem to have flashed wrong. Now just get the screen as shown on attachment and cannot boot.
3. Stock recovery seems to have been flashed and I can boot to this. From here I can boot to bootloader but can't seem to do anything from there.
4. I try update via ADB with the sideload command, but get the message "E:footer is wrong. E: Signature verification failed. Installation aborted".
5. I try to Update from SD as have the firmware zip file and TWRP on the root of my external SD card, but get the message "Couldn't Mound /sdcard, aborted."
6. The only time my phone shows as a connected device in ADB is when I try to sideload files. No other ADB code seems to work, only get the message "error: closed" on the terminal.
Assuming I've got all the firmware files (and full backups on my external SD) I feel like if I can just install TWRP again it should be an easy fix. So, any ideas on how I install TWRP given situation above?
Best,
Neil
nstirton said:
Hi guys,
Unable to boot after c*cking up a manual upgrade from B10 to B11 on my A2017G and would love your input. I feel like if I can just install TWRP again it should be an easy fix. Here's some specifics:
1. my phone is unlocked, rooted and running stock firmware.
2. I was trying to install stock recovery to install the B11 update. I did so but also tried to install another zip (B10 bootloader?) which I seem to have flashed wrong. Now just get the screen as shown on attachment and cannot boot.
3. Stock recovery seems to have been flashed and I can boot to this. From here I can boot to bootloader but can't seem to do anything from there.
4. I try update via ADB with the sideload command, but get the message "E:footer is wrong. E: Signature verification failed. Installation aborted".
5. I try to Update from SD as have the firmware zip file and TWRP on the root of my external SD card, but get the message "Couldn't Mound /sdcard, aborted."
6. The only time my phone shows as a connected device in ADB is when I try to sideload files. No other ADB code seems to work, only get the message "error: closed" on the terminal.
Assuming I've got all the firmware files (and full backups on my external SD) I feel like if I can just install TWRP again it should be an easy fix. So, any ideas on how I install TWRP given situation above?
Best,
Neil
Click to expand...
Click to collapse
Are you able to boot into EDL mode by typing ADB reboot edl ?
If so you can flash desired recovery with axon7tool
marcus.linkenbach said:
Are you able to boot into EDL mode by typing ADB reboot edl ?
If so you can flash desired recovery with axon7tool
Click to expand...
Click to collapse
Hi, thanks for your reply. Unfortunately not, just get the message "error: closed" in the terminal. Is there a button combination I could press in order to get into EDL?
nstirton said:
Hi, thanks for your reply. Unfortunately not, just get the message "error: closed" in the terminal. Is there a button combination I could press in order to get into EDL?
Click to expand...
Click to collapse
Try vol+ + vol- + power
it seems that the only time my device will show as connected in ADB is when I navigate through Recovery and select the "Apply Update from ADB" option. But even then, whilst it shows as connected, it only seems to allow the "sideload" command. Please see screenshot of Terminal. So at no other time will it show as a connected device.
Similarly, to have it show up in Device Manager, it'll only show when I switch the phone off, hold down Vol+ & Vol- and attached the power cable.
You are still on MM. So you are able to boot into bootloader.
adb reboot bootloader
fastboot devices
Now it should show your device as fastboot
If so you can now flash recovery with “fastboot flash recovery recovery.img“
marcus.linkenbach said:
You are still on MM. So you are able to boot into bootloader.
adb reboot bootloader
fastboot devices
Now it should show your device as fastboot
If so you can now flash recovery with “fastboot flash recovery recovery.img“
Click to expand...
Click to collapse
Thanks for your reply. Unfortunately as mentioned the only time my device shows as connected in Terminal is when I select "Update via ADB" whilst in recovery. Otherwise the device never shows as connected in adb.
So unfortunately fastboot doesn't seem to be an option for me.
Perhaps my drivers are out of whack but assuming what I've done to my phone hasn't changed that, it must be something PC - side.
nstirton said:
Thanks for your reply. Unfortunately as mentioned the only time my device shows as connected in Terminal is when I select "Update via ADB" whilst in recovery. Otherwise the device never shows as connected in adb.
So unfortunately fastboot doesn't seem to be an option for me.
Perhaps my drivers are out of whack but assuming what I've done to my phone hasn't changed that, it must be something PC - side.
Click to expand...
Click to collapse
But what if it shows your device as sideload? Can't you there reboot into fastboot?
No, it doesn't accept the command. Only one accepts is sideload. You can see from my screenshot a few posts back that the device is connected but shows different to how it normally would.
Breakthrough!
I seemed to follow the steps I've tried 100 times today and I now have TWRP installed again!
Thanks again to those who helped
I just bought a Huawei Y5 2017 ( MYA-L22)
I was Unlock bootloader this device but i cannot find TWRP file to root this device
Does Anyone know how to root it?
Please teach me
Thank everyone for reading
Same here. Anybody has TWRP for this device?
ranchoiphohuyen said:
I just bought a Huawei Y5 2017 ( MYA-L22)
I was Unlock bootloader this device but i cannot find TWRP file to root this device
Does Anyone know how to root it?
Please teach me
Thank everyone for reading
Click to expand...
Click to collapse
Download Kingoroot for pc and install it. Enable USB debugging on your phone and connect it to the pc. Open Kingoroot, it will detect ur phone automatically. Remember to connect your pc to internet. Click the ROOT button and it will root your phone.
I found TWRP from this site but something's weird
Check this link: romprovider.com/2017/10/twrp-root-huawei-y5-2017-mya-l22/
I downloaded the TWRP found there but when I tried to do "fastboot boot recovery.img", it says "failed (remote unknown command)"... Did the TWRP from that link worked for you or any of you guys here?
enzo22 said:
Check this link: romprovider.com/2017/10/twrp-root-huawei-y5-2017-mya-l22/
I downloaded the TWRP found there but when I tried to do "fastboot boot recovery.img", it says "failed (remote unknown command)"... Did the TWRP from that link worked for you or any of you guys here?
Click to expand...
Click to collapse
Working with twrp at times becomes a little complicated, why don't you try rooting tools?
Augustoandro said:
Working with twrp at times becomes a little complicated, why don't you try rooting tools?
Click to expand...
Click to collapse
One reason why I don't want to try rooting tools is that I want to backup my stock rom without root access.. So I want to install a custom recovery first but I only saw one for this device and it seems to be not working yet. I also want to extract my stock recovery.img but I need to fastboot boot TWRP for that
I'm also interested in just straight Rooting this device, not interested in ROMs etc. I tried APK KingRoot (latest) and after doing a 'Root Check' with an app it did not come back rooted. Can someone provide tools & steps for the newbie please?
much thanks
x86 said:
I'm also interested in just straight Rooting this device, not interested in ROMs etc. I tried APK KingRoot (latest) and after doing a 'Root Check' with an app it did not come back rooted. Can someone provide tools & steps for the newbie please?
much thanks
Click to expand...
Click to collapse
Please take a backup of ur data before proceeding further.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and ur phone will reboot.
Download Kingoroot for pc on your pc and install it.
Enable USB debugging on your phone.
Connect your pc to internet.
Connect your phone to pc with a USB cable.
Open Kingoroot, it will detect your phone automatically.
Click the root button and wait for the process to complete.
Augustoandro said:
Please take a backup of ur data before proceeding further.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and ur phone will reboot.
Download Kingoroot for pc on your pc and install it.
Enable USB debugging on your phone.
Connect your pc to internet.
Connect your phone to pc with a USB cable.
Open Kingoroot, it will detect your phone automatically.
Click the root button and wait for the process to complete.
Click to expand...
Click to collapse
i have gotten to the kingoroot part. i have tried multiple times on windows AND android and windows fails and android gets stuck at 90%
uneedsomemilk said:
i have gotten to the kingoroot part. i have tried multiple times on windows AND android and windows fails and android gets stuck at 90%
Click to expand...
Click to collapse
If Kingoroot is not working, give a try to some other rooting tools.
Augustoandro said:
If Kingoroot is not working, give a try to some other rooting tools.
Click to expand...
Click to collapse
Did some research, you need to do a system less root in android 6. Anyone know any guides of how to do that?
hi
i flashed huawei y5 2017 twrp and wanted back to stock recovery tried with adb , now i have no android os neither twrp , phone just shows huawei logo and restarts itself again and again, cant turn on or off , no vol up/down and power buttons work , can anyone help ? is there way to restore or isntall stock rom in this situation or phone is junk now ? (just showing huawei logo and keeps restarting itself) thank you
its huawei y5 2017 mya-L22
SuperSu app for root
I think you can try SuperSu, This Also the best app to get root access. Download SuperSu.
or find here - https://forum.xda-developers.com/apps/supersu
This is a hard fone to Root, the normal 1-Click Rooting Apps don't work in my trials. Kingroot & SuperSU both don't work.
This fone wont copy Apps to SD card either, I have APP2SD Pro & have tried loads of others. Has anyone got APP 2 SD to work? It sucks my fone out of memory already just with apps alone, no music or anything.....
x86 said:
This is a hard fone to Root, the normal 1-Click Rooting Apps don't work in my trials. Kingroot & SuperSU both don't work.
This fone wont copy Apps to SD card either, I have APP2SD Pro & have tried loads of others. Has anyone got APP 2 SD to work? It sucks my fone out of memory already just with apps alone, no music or anything.....
Click to expand...
Click to collapse
Just change default location of storage to sd card. It works for me. To manually move apps to SD, just copy and paste the folders from data and obb in android folder of internal storage to external storage. I uses this to move the data of my games and it worked
[/COLOR]
enzo22 said:
Check this link: romprovider.com/2017/10/twrp-root-huawei-y5-2017-mya-l22/
I downloaded the TWRP found there but when I tried to do "fastboot boot recovery.img", it says "failed (remote unknown command)"... Did the TWRP from that link worked for you or any of you guys here?
Click to expand...
Click to collapse
I SOLVED IT!!!!!!!!!
just keep the same name and write fastboot flash recovery twrp-huawei-y5.img
THAT SOLVED THE ERROR
the trouble in huawei MYA-L13 android 6.0 is when flash recovery y5 2017 can go inside of that .
the scroll in down place, dont move all and just cant go inside twrp... all is ok the phone works. but can go inside twrp...
I have MYA-L22. I have rooted it and already installed twrp but the system is only read only right right after I flashed magisk. Now I only have root right but I can't flash anything besides magisk.
altera011 said:
I have MYA-L22. I have rooted it and already installed twrp but the system is only read only right right after I flashed magisk. Now I only have root right but I can't flash anything besides magisk.
Click to expand...
Click to collapse
Search f2fs loopback bug and go from there.
Can someone provide me MYA-L22 stock recovery.img ?