I have a nexus 10 v4.4.4, finally wanted to root it and install a custom recovery (cwm). I used the same method as i used on my nexus 5 with the same application - nexus toolkit. All drivers are installed, clicked on "unlock", booted into the screen where i should click "yes" in order to unlock bootloader. The devices rebooted and stuck in the booting animation. Searched a lot and read a lot, but i cant make the device boot normally. I am able to boot into fastboot (i suppose, the screen where you can skip between options like "recovery, "power off" and "restart bootloader". Can anyone give me a hand with restoring the device?
EDIT
ok i was able to fix this issue. In case anyone encounters the same exact issue, this is what went wrong and what was made in order to make everything work:
1. make sure fastboot recognizes your device, by typing in command line "fastboot devices". if your device is not listed, first fix this (check drivers and connectivity). i had to reboot my pc in order to communicate with my nexus.
2. now boot to fastboot by holding vol up + vol down + power button.
3. launch NTK and simply select "back to stock" and check "soft brick \ bootloop" option.
4. the app with download the image and afterwards everything is automated. you will reboot to the setup screen.
BIG thanks to WugFresh and his awesome tool Nexus Root Toolkit v1.8.6.
I am trying to unlock the bootloader on this thing.
I've gone in to Settings > Developer Options and checked 'OEM unlocking'.
I've enabled USB debugging.
I plugged the phone in and issued 'adb reboot-bootloader'.
...Then the phone powers off, comes on and just gives me the Huawei logo as if it is stuck. It does not respond to 'fastboot devices' or 'adb devices', only solution is battery out/battery in.
I then tried powering on using power+volume up to get to recovery (which works) and choosing the option for 'reboot to bootloader'. I get the same Huawei logo screen as above.
I then tried powering on using power+volume down, this takes me to what appears to be a hardware test page which is all in chinese. Looks the same as this: http://imgur.com/a/eE3hb
I have now rooted with Kingroot and tried again, although I know that it shouldn't make any difference at the bootloader stage whether I am rooted or not. But worth a try.
Anyone have any ideas?
Thanks
There isn't a forum for the Y5...but there is this thread full of general info for the Y5: http://forum.xda-developers.com/android/development/huawei-ascend-y5-codename-y560-l01-t3281367
You may find what you need there....
I bricked my opx I was able to bring it to life but the ****ty recovery doesn't let me flash anything so I am stuck no OS and boot loader locked and my computer isn't recognizing the dam thing I have installed SDK tools and google USB drivers but for some reason I am not able to get the Dan thing to connect right when I try via adb sideload it starts then the phone says fail...... Please help I am love this device and brand but I am getting really mad I am about a week in to trying to fix this but no luck I am using windows 10 also
We can try to unlock the bootloader as it is now, but that doesn't usually work unless you checked "OEM Bootloader Unlock" in the system settings before the device was bricked. Hindsight is 20/20 but as a word of advice for the future, never ever mess with a device unless you know the bootloader is unlocked or have made it possible to unlock it later without the OS. It also doesn't void the warranty on OnePlus devices to do so.
So first things first, the recovery will normally only flash the stock ROM as provided by OnePlus. You can download that file from here: http://downloads.oneplus.net/2016-04-02/opx/OnePlus_X_OxygenOS_2.2.1/. For future reference, when the bootloader on a device is locked the bootloader will not boot any software that isn't complete stock. If you try and change the OS or Recovery and it's not stock, the bootloader will not load it. This goes for any Android device.
If ADB sideload is working for you but hasn't been installing on the device (as-in, it sends the file but the device fails to install it) then you should be able to just sideload the zip file. It'll be slow though since it's about 780megs. If it doesn't send it then you can try using the ADB "push" command which is like copy and paste. You "push" the file from your computer to a folder on the device (you can see what folders are available using "adb shell" and then navigating with CD "change directory" and LS "list". If you can't find the sdcard you may have to mount it). Once again, it'll push slowly but once it does you should be able to install it from the internal memory.
If that works and it boots, go to Settings -> About Phone and tap the Build Number until it says you've enabled developer settings. Go to Settings -> Development and turn on "OEM Unlocking". Power the phone down. Hold the Power key and Volume Down until it shows the OnePlus logo and "Fastboot". I believe if you have the Android SDK you have the Fastboot program (it's commandline like ADB). Open CMD or Powershell and as long as it's the only device plugged into the computer you should be able to simply type "Fastboot oem unlock" and it will unlock the bootloader. Once again, it doesn't void your warranty.
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
levijoseph said:
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
Click to expand...
Click to collapse
Try power plus volume up button to go to fastboot mode.
If it not working then connect your android to pc and enable adb. Type "adb devices" enter then type "adb reboot bootloader" and enter. It boots your android in fastboot mode.
If adb commands not working then install adb and fastboot drivers and try again.
https://forum.xda-developers.com/showthread.php?t=2317790
In most devices, volume up + power boots up the recovery options, volume down + power boots the device into fastboot mode (volume buttons first plus power, pressing power button first would boot the device normally).
levijoseph said:
When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked.
Click to expand...
Click to collapse
How did you install the custom recovery? Try flashing the recovery.img again (I'm guessing, since you have root, that you did not "flash" (fastboot flash recovery recovery.img) TWRP but just "boot" (fastboot boot recovery.img) it and installed SuperSU).
Ashwinrg said:
Try power plus volume up button to go to fastboot mode.
If it not working then connect your android to pc and enable adb. Type "adb devices" enter then type "adb reboot bootloader" and enter. It boots your android in fastboot mode.
If adb commands not working then install adb and fastboot drivers and try again.
https://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
Okay, so that did work, and I was able to enter fastboot mode. However, once I scrolled down to "recovery mode" and tried to enter, I got the same "no command" screen.
rolland.arriza said:
In most devices, volume up + power boots up the recovery options, volume down + power boots the device into fastboot mode (volume buttons first plus power, pressing power button first would boot the device normally).
How did you install the custom recovery? Try flashing the recovery.img again (I'm guessing, since you have root, that you did not "flash" (fastboot flash recovery recovery.img) TWRP but just "boot" (fastboot boot recovery.img) it and installed SuperSU).
Click to expand...
Click to collapse
I used the official moto g4 root guide on this website to root my phone and I'm pretty sure I booted, not flashed, the recovery img (mine is named twrp-3.0.2-0-athene). So, I tried using the command you provided to flash the recovery img and I got a < waiting for any device > message in the command prompt. My phone is plugged in and my recovery img is in the adb / fastboot folder. Any idea what this means? Thank you for the help guys
edit: If it helps to know this, my phone has usb debugging enabled and it is recognized by my pc. I type adb devices and my moto g4 serial number does indeed show up.
levijoseph said:
I am very new to this, I rooted my Moto G4 and now I need to download SUHide in order to play Pokemon Go. When I try to enter recovery via my fastboot/abd folder I get a < waiting for any device > message. When I hold down the power + volume down button my phone just turns on as normal without entering bootloader even though my bootloader is unlocked. I tried downloading an app that loads recovery for me but when I tried that I got a "no command" screen with a little green robot.
From what I've read, it's possible I didn't flash my trwp properly? I don't know how this is possible since I just rooted my phone. I would appreciate some help, I'm afraid to take any random guesses at the risk of ruining my phone. Sorry if I'm missing something obvious or not giving enough info, I'm not very tech savvy.
Click to expand...
Click to collapse
If you are trying to flash twrp recovery on your android then rename your twrp to recovery.
Boot your android in fastboot mode,
Navigate to folder that you have recovery. Press shift and right click and click on open command here and type "fastboot devices" and enter
"fastboot flash recovery recovery.img
It flash your recovery to your android.
Ashwinrg said:
If you are trying to flash twrp recovery on your android then rename your twrp to recovery.
Boot your android in fastboot mode,
Navigate to folder that you have recovery. Press shift and right click and click on open command here and type "fastboot devices" and enter
"fastboot flash recovery recovery.img
It flash your recovery to your android.
Click to expand...
Click to collapse
Did all that, getting:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
error: cannot load 'recovery.img'
Also, per the suggestion of other users on these forums, I tried to hold down power and press volume up during the "no command" screen after attempting to enter recovery. That sent me into Android Recovery but it's not the twrp platform I used when originally rooting my phone.
How did you unlock the bootloader? have you tried: fastboot oem unlock?
You need to "allow oem unlocking" on developer options (which I guess you already did). Then reboot in bootloader: (a) adb reboot bootloader. In fastboot, you need to unlock the bootloader first: (b) fastboot oem unlock (or unlock-go). Then you can try to flash that recovery.img: (c) fastboot flash recovery "name of the file.img"
edit: fastboot oem unlock restores the device to factory settings. You need to configure and enable again "usb debugging" and "oem unlocking" (which are disabled by default). You can then proceed to fastboot flash
Hi to all,
I have a question about my device.
I hope that I have posted this correctly; if not please accept my apologies.
I have a Letv Le 2 Pro X620. This has the MTK CPU (not snapdragon).
The phone had the stock ROM on it with EUI and it got the updates.
In the last update about a month ago, Google Service stopped working; and I therefore wanted to flash a different ROM on to fix that; as well as to finally get rid of the chinese apps which annoyed me.
SO I downloaded a ROM from XDA https://forum.xda-developers.com/le-2/development/rom-lligera-t3538654 (thanks).
The device was unrooted and had the stock recovery.
I used the basic adb and fastboot command prompt applications. I already enabled developer mode in the phone and had also enabled debugging and unlocking boot loader.
In the adb/fastboot I entered the command to unlock "fastboot oem unlock" and "fastboot oem unlock go". IT would confirm and complete and then I went onto flash the recovery.
HERE IS WHERE THINGS DIDNT GO AS EXPECTED.
And I ended up doing this multiple times (i.e oem unlocking, and flashing recovery)
I tried using TWRP twrp-3.2.1-0-s2; and also downloaded a pack "Le2RootMegaPack" which had Letv-X620-Twrp-3.0.2-0 .
IT would complete successfully; but on reboot I would get an error message like "Orange State. Your phone can not be trusted" (this is not the exact message but close to it).
The message only seemed to come once as if I restarted it would disappear.
When I went back to fastboot it would say locked until i did over the fastboot oem unlock command (in other words I had to unlock everytime).
Also when I go to reboot; something about "Lock" would come in the command prompt statuses just before it rebooted.
It seems like the bootloader kept getting locked again.
So I could not boot into TWRP.
I then tried using the "fastboot boot xx.img" command which after several attempts and variations worked.
I flashed the Letv-X620-Twrp-3.0.2-0 and then "fastbook boot" booted from ANOTHER version of TWRP (as it would not boot using that same TWRP).
Then when the phone was about to restart I held up the volume up button and it booted to TWRP.
(That recovery (which I booted from) was from the ROM LeEco+x620+CM13+Rom+v145+by+Kangburra which I also downloaded from XDA.)
However the touch screen wouldnt work and I had to use a USB mouse (using the adaptors/OTG cable) and was able to control the phone in the TWRP.
I wiped the dalvik and cache and loaded the rom and it completed. then it asked to reboot which i did; and then it just wouldnt start.
The present status is that there is nothing on the Phone. I cannot boot to recovery nor to fastboot.
The only reaction I get from the phone is if I plug in a USB cable (charger). I have it plugged into the PC and the PC sound for when a device is plugged in and the sound for when a device is plugged out plays rapidly within 2-3 seconds (ie it connects/disconnects quickly).
The adb/fastboot commands do NOT work. The computer does not include it in devices etc.
I would therefore be grateful if I can have some assistance. I would like the phone to work again (obviously).
Thank you for your time.