Hi All,
I installed Androot and recovery flasher and tried to update/backup the recovery.
But i can't. I only got message "backup failure".
As I understand i have to give root permissions to recovery flasher but androot don't ask me when recovery flasher start.
I'm sure, androot works because I give "root" to terminal and adb.
Can I give root manually? Or is any other options?
paganelle said:
Hi All,
I installed Androot and recovery flasher and tried to update/backup the recovery.
But i can't. I only got message "backup failure".
As I understand i have to give root permissions to recovery flasher but androot don't ask me when recovery flasher start.
I'm sure, androot works because I give "root" to terminal and adb.
Can I give root manually? Or is any other options?
Click to expand...
Click to collapse
Hi.
There are a few things we should check, and a few things to try.
1) Try running Androot again and see what happens. Does it say "already rooted" or anything else?
2) When you look at the list of installed apps, do you see the "Superuser" app? If you don't, you'll have to root the phone again and install Superuser.apk before you reboot. If you do see Superuser, open it and check the history and the settings. See if your backup app is listed in the logs.
3) Connect the phone to your PC and open a Command Prompt. Run "adb shell", then try to run "su". If you get "Permission denied", you aren't rooted, or Superuser hasn't been granted root privileges; look at the phone's screen to see if it asks you to "Allow" or "Deny" granting privileges.
4) Try SuperOneClick. I'm not positive, but I think they stopped development of Universal Androot (let me know if I'm wrong about this). SuperOneClick works through adb, so make sure "adb devices" lists your phone when connected to your PC. Download and install SuperOneClick, run it (as Administrator if you use Windows 7 or whatever), and click the Root button.
Once you've tried these steps, we'll have a better idea what's going on. It's possible that you were only given temporary root and it disappeared after a reboot. *shrug*
Let us know what happens. Cheers.
1. It says "already rooted"
2. Yes I see "Superuser' and 2 "rooted" applications "Terminal emulator" and "Unknown". "Unknown" appeared after I connected to the phone by adb shell su bla-bla.
3. See above. It was as you described.
4.Ok. I'll try!
DasBub said:
Hi.
There are a few things we should check, and a few things to try.
1) Try running Androot again and see what happens. Does it say "already rooted" or anything else?
2) When you look at the list of installed apps, do you see the "Superuser" app? If you don't, you'll have to root the phone again and install Superuser.apk before you reboot. If you do see Superuser, open it and check the history and the settings. See if your backup app is listed in the logs.
3) Connect the phone to your PC and open a Command Prompt. Run "adb shell", then try to run "su". If you get "Permission denied", you aren't rooted, or Superuser hasn't been granted root privileges; look at the phone's screen to see if it asks you to "Allow" or "Deny" granting privileges.
4) Try SuperOneClick. I'm not positive, but I think they stopped development of Universal Androot (let me know if I'm wrong about this). SuperOneClick works through adb, so make sure "adb devices" lists your phone when connected to your PC. Download and install SuperOneClick, run it (as Administrator if you use Windows 7 or whatever), and click the Root button.
Once you've tried these steps, we'll have a better idea what's going on. It's possible that you were only given temporary root and it disappeared after a reboot. *shrug*
Let us know what happens. Cheers.
Click to expand...
Click to collapse
Related
Hello,
I am stuck and it is really anoying. I am trying to flash CM on my LG L5 (e610)
I have installed adb, and rooted the device already. I have su and when i do a check
for adb to work 'adb devices' it shows up with my device. but when i enter 'adb shell' hit enter
and after that typ 'su' it does nothing.. nothing pops up on my phone.. i have USB debuging enabled and
it is in charge mode. What is it i do wrong?
-Fireworkfan
EDIT: I can use other commands, rebooting my phone with ADB works perfect.. what am i doing wrong with adb shell thing.. is there something i need to instal first? i only placed the .bin file in the directory of my phone.. Also i have 'SuperSU' shouldnt 'su' be something els? i am so confused
after you write adb shell, if you have SuperUser or SuperSU on your phone, unlock your phone and accept root for adb comands and after you can go with su and do what you want
Sabyn said:
after you write adb shell, if you have SuperUser or SuperSU on your phone, unlock your phone and accept root for adb comands and after you can go with su and do what you want
Click to expand...
Click to collapse
That is the whole problem, I do not get a grant or decline messages from my SuperSU... I have checked it over a 100 times, on the mainscreen or even with the app itself open. I do however get the Grant or Decline message when I use apps like pimpmyrom on my phone itself.. I have tried it on a different computer to now, again without succes.. anyone an idea? There would be someone that would like to help me over a chat with this problem?
This is for windows but it should be adaptable to other operating systems.
Here is a quick "how to" restore your su on stock if you dont have a backup, when you have lost it for what ever reason.
To confirm you have have lost su from your system, connect your device, open up a cmd window and type or copy and paste the following one at a time:
Code:
adb shell
Code:
su
If su "#" isnt retured then do the following:
Download the LATEST OTA update zip from here-
https://ouyafw.skumler.net/
and place in your adb folder for ease of use.
Connect a wired USB keyboard to the OUYA.
Boot into recovery using -
Code:
adb reboot recovery
Upon reboot, you will likely be presented with a black screen and an Ouya icon with "!". Press the home button on your keyboard.
Using the keyboard, navigate using "up","down" and "enter" to select update from adb.
When prompted, open a cmd and enter the following-
Code:
adb sideload RC-OUYA-1.0.346-r1_ota.zip
Replace the file name above as appropriate.
Upon completion reboot system and you will have regained su.:fingers-crossed:
NOTE: When sideloading the OTA firmware the build dates are compared to one another. If you try to sideload an older version you will receive a fail. Use the same build version or above.
F.A.Q.
Q. I recieve an error stating device not found in recovery.
A. You need to install the drivers for the recovery as you did for adb.
Q. I receive an error due to build.prop
A. When sideloading the OTA firmware the build dates are compared to one another. If you try to sideload an older version you will receive a fail. Use the same build version or above.
This is tried and tested on my device.
Thanks to
@rayman for the firmware link.
Timothy Graupmann for Youtube video.
Thank you, as i have a lost su and i don't want to wait for the next OTA update i will follow this method.
tonyeltriton said:
Thank you, as i have a lost su and i don't want to wait for the next OTA update i will follow this method.
Click to expand...
Click to collapse
No problem.
Did you lose su with the ouya toolbox or via something else.
dully79 said:
No problem.
Did you lose su with the ouya toolbox or via something else.
Click to expand...
Click to collapse
Well i think i have messed up with adb commands, after that i tried ouya toolbox with luck because the program said that my ouya should be rooted but it wasn't. I will restore lost su and then try again ouya toolbox.
Adb reboot recovery takes me to a black screen with ouya logo and " ! " under it.
tonyeltriton said:
Adb reboot recovery takes me to a black screen with ouya logo and " ! " under it.
Click to expand...
Click to collapse
Thats where you press "Home" on your attached usb wired keyboard to enter the options.
dully79 said:
No problem.
Did you lose su with the ouya toolbox or via something else.
Click to expand...
Click to collapse
Lol i did and this would have came in handy if I found it earlier but I figured it out and install the proper su file
I can confirm these instructions work perfectly. I factory defaulted my Ouya after rooting it and lost access to su in the shell even. These steps fixed my Ouya!
Sent from my Nexus 10 using Tapatalk 4 Beta
I'm stuck right here as far as download mode goes.
I installed TWRP on a d800 rooted with stock 4.2.2. The TWRP install went ok but it never booted afterward.
I can get into twrp, but can't sideload anything because the computer does not connect to the device, I hear the connection noise the computer makes but nothing in the device manager.
any ideas?
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
bender_007 said:
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
Click to expand...
Click to collapse
Thanks, I get
error: closed
I was wrong about my computer not seeing my device, it's in the device manager under Android and the adb drivers are installed.
I also renamed the rom to "update" to make it simpler
What's up now ?
Sorted it out or still issues there ?
I also tried the adb shell method.
I also tried this method through TWRP terminal and nada.
If I did something wrong here let me know, hopefully I can get it up and going
bender_007 said:
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
Click to expand...
Click to collapse
This is what I get when I do the above. The CMD prompt in located in the same directory as the adb files
ADB sees my device as this #
Gabriel51 said:
This is what I get when I do the above. The CMD prompt in located in the same directory as the adb files
ADB sees my device as this #
Click to expand...
Click to collapse
ok, let's do it like this
1. copy rom to c:\rom.zip
2. while in adb folder "adb push c:\rom.zip /sdcard/rom.zip"
that should work, you don't need sideload to be enabled.
Please test and report.
bender_007 said:
ok, let's do it like this
1. copy rom to c:\rom.zip
2. while in adb folder "adb push c:\rom.zip /sdcard/rom.zip"
that should work, you don't need sideload to be enabled.
Please test and report.
Click to expand...
Click to collapse
I moved the file to the root of my C drive changed the name to "rom.zip"
Copied the command you supplied and got this result
I know my phone is connected because I can reboot it by using the command " adb reboot"
I used this;
adb push C:\Android\sdk\platform-tools\rom.zip
And it is now ready to install through TWRP!
Hold your breath.......
Edit;
Failed but at least it's in the twrp list
"unable to open zip"
I think I got it, I was able to access the firmware update screen.
Sorry fir these incomplete responses, I don't want you to keep looking for a resolve while I do this.
If your still here?
I'll be back!
Success!
After nothing would work except for loading the rom through adb I decided to wipe the whole thing.
I reloaded the rom and when selected for install it opened instead of preparing for install so I thought I would reboot and when I did I was prompted by su that my device may have lost root and gave me the option to reinstall it, I chose yes and when rebooting it hung (normal) at the LG logo, however this time the charge light was flashing! I attempted to access "download" and was successful in loading the stock rom.
In the end it looks like TWRP was the culprit, it used to be my favorite but not for this device
All is well, thanks for your help...
Everything I've seen so far has resulted in someone bricking their phones, including somehow deleting their IMEI numbers or somehow resulting in their BT/WiFi not working. There were so many threads that it's hard to remember which one is which.
I've decided it's time to unlock/root my phone but I don't want to make the same mistakes and somehow brick my phone. Why was it that the partition with the IMEI was written over? What about the other bricks? What is the best method to unlock/root right now?
Often times mixing firmware from other regions will cause issues. For example flashing the US version with the G or international versions. By firmware, I'm referring to other system components besides /system and kernel. Radio/baseband, BT firmware, etc.
The other issue has to do with the axon7backup program. For greatest safety, this really should only be used to backup and flash recovery while the bootloader is still locked only.
I see, thanks.
I followed these guides:
- https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
- https://forum.xda-developers.com/axon-7/how-to/guide-root-xposed-safetynet-stock-rom-t3530906
Now my phone is unlocked and rooted... but after each reboot the annoying system apps I uninstalled return. I'm guessing this is because I have a systemless root?
So I guess my questions are now:
- Most importantly if a system root is required to keep changes such uninstalling system apps, how can I switch to that and is there anything I should be wary of? Is a system root guaranteed to be seen even with SUhide/whatever?
- How can I even know if the SafetyNet program is even working if according to that guide I can't even use it's check app to test it?
- What about SUhide? Like SafetyNet I don't seem to have a way to see anything regarding it.
There is no way to fully brick a device with the Qualcomm 820 SoC. It is more or less complicated, but even deleting the bootloader it is possible to recover the device with the appropriate Qualcomm flashing tools.
Regarding "easy" bricks, you will be able to recover any brick by using tenfar's Axon7tools, and DrakenFX guides. Also Just keep on had a backup of your boot.bin, recovery.bin (both using Axon7Tool), and the full ZIP for your device model in a FAT formatted SDcard.
The recovery process is just to flash back the boot.bin, then recovery.bin (using the same tool Axon7tool) and then from the stock recovery reinstall the full zip and optionals OTA.
Cyrus D. said:
I see, thanks.
I followed these guides:
- https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
- https://forum.xda-developers.com/axon-7/how-to/guide-root-xposed-safetynet-stock-rom-t3530906
Now my phone is unlocked and rooted... but after each reboot the annoying system apps I uninstalled return. I'm guessing this is because I have a systemless root?
So I guess my questions are now:
- Most importantly if a system root is required to keep changes such uninstalling system apps, how can I switch to that and is there anything I should be wary of? Is a system root guaranteed to be seen even with SUhide/whatever?
- How can I even know if the SafetyNet program is even working if according to that guide I can't even use it's check app to test it?
- What about SUhide? Like SafetyNet I don't seem to have a way to see anything regarding it.
Click to expand...
Click to collapse
You missed a step. Use Terminal or Terminal Emulator , type SU, then reboot disemmcwp
or
Go to adb shell while in TWRP and enter adb reboot disemmcwp
This will reset settings to allow system changes so they will "stick".
Good luck!
amphi66 said:
You missed a step. Use Terminal or Terminal Emulator , type SU, then reboot disemmcwp
or
Go to adb shell while in TWRP and enter adb reboot disemmcwp
This will reset settings to allow system changes so they will "stick".
Good luck!
Click to expand...
Click to collapse
Sorry I'm new to all this, I'm doing something wrong here.
So just to be clear it's:
- Type in "SU", enter it, then type "reboot disemmcwp", in TWRP's terminal?
That results in "SU not found" for me.
or
- Type in "adb reboot disemmcwp" in a command window opened in the adb folder on my PC while TWRP is running adb sideload?
That resulted in "* daemon not running. starting it now on port 5037 * * daemon started successfully * error: closed"
Edit: Just "reboot disemmcwp" in the terminal without SU first worked. So... what was I doing wrong?
Cyrus D. said:
Edit: Just "reboot disemmcwp" in the terminal without SU first worked. So... what was I doing wrong?
Click to expand...
Click to collapse
The su binary only exists if you open a terminal in an android app because apps do not have root permission. TWRP and adb shell automatically have root privileges.
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 ?