Running AOPK, Milestone 5. Phone was running great, a bit laggy, but all was fine.
Turned on fastcharge, plugged phone into the wall charger, took a nap, woke up and the screen had the Google Logo. Dead. nothing, can't reboot, can't get into recovery mode, nothing. I can't get to the recovery mode screen but no no options work. PC doesn't recognize it probably because of the fastcharge option being turned on.
I've got a new one on the way, but this is frustrating.
Any ideas?
Stumped.
Denver
Wait, so you already purchased a new one? I bet you could get this one fixed. There are plenty of guides on here to help resolve the issue. Hell, I'm in Denver as well and wouldn't mind working with you to try and get it out of brick.
A new one should be fedex'd tomorrow. My schedule might permit some time to meet, but the phone is not accessible via PC so not sure how we go about trying to repair.
First of all, please don't use the word brick until you know it's a brick. If it still powers on, it is not a brick. A software issue does not cause a brick.
Now, can you boot into the bootloader (i.e., turn the device off, hold volume up and volume down, and press and hold power)?
If so, just follow this, and it will restore your device to stock.
A little progress?
Well I have had a bit of luck getting into recovery mode this morning, but with little progress.
When getting to the recovery mode I'm getting this error
E:can't mount cache/recovery/command
E:can't mount cache/recovery/log
E:can't open /cache/recovery/log
E:can't mount/cache/recovery/last_log
E:can't open /cache/recovery/last_log
Although phone is recognized on PC via device manage, can't see device using fastboot device command nor can see it as a external drive.
Have tried:
Wipe data/factory reset
backup and restore
wipe cache partition
All attempts initially look good, then the screen text gets fuzzy, and then goes into a reboot loop.
denverdesktop said:
[snip]
Although phone is recognized on PC via device manage, can't see device using fastboot device command nor can see it as a external drive.
Click to expand...
Click to collapse
That is because your fastboot driver is not set up properly.
denverdesktop said:
Have tried:
Wipe data/factory reset
backup and restore
wipe cache partition
Click to expand...
Click to collapse
How about trying my suggestion for the post above??
Continued
I have been trying your suggestions. Device shows up in device manager as Samsung Galaxy Nexus ADB interface. I open a command prompt where the fastboot loader software was extracted, type the command "fastboot devices", hit enter and get nothing back, but output of directory name.
denverdesktop said:
I have been trying your suggestions. Device shows up in device manager as Samsung Galaxy Nexus ADB interface. I open a command prompt where the fastboot loader software was extracted, type the command "fastboot devices", hit enter and get nothing back, but output of directory name.
Click to expand...
Click to collapse
If it is showing up as "Samsung Galaxy Nexus ADB interface", there is likely one of two things wrong: your fastboot driver is not installed properly, or you are not booted in fastboot mode.
Sent from my Galaxy Nexus using Tapatalk 2
sound like you are trying to run fastboot command in recovery and fastboot won't be recognized in recovery maybe run adb reboot bootloader then try fastboot commands.
Sent from my Galaxy Nexus using xda premium
Related
I have messed up while trying to run Backtrack 5 on my Defy. As I got some errors when executing the bt script, I attempted to install the busybox several times. The effect is that, after reboot, I have an infinite boot loop. I can access the recovery (unfortunately the stock version), however it opens with the following errors:
E:Can't open /cache/recovery/command
E:Can't open /cache/recovery/caller
and after wiping the cache I get:
E:Can't mount CACHE:recovery/log
Is it possible to somehow fix the filesystem without performing the factory reset?
If not, then is it possible to access the phone memory in order to backup stuff such as messages, before the factory reset or flashing new ROM?
Any ideas much appreciated!
It looks like you're stuck :/.
If you had usb debug on before having problems then maybe you could try using adb during the bootloop? I don't know how to use it though.
CM7 + CM9 double boot
crakeron said:
It looks like you're stuck :/.
If you had usb debug on before having problems then maybe you could try using adb during the bootloop? I don't know how to use it though.
CM7 + CM9 double boot
Click to expand...
Click to collapse
If you have done up and set adb correctly , run
Code:
adb logcat
Herpderp Defy.
Thanks for your suggestions!
I'm pretty sure I left the USB debugging switched on. However the phone isn't detected by ADB interface (adb devices). The "adb logcat" is waiting for the device throughout the whole boot loop, as well as when accessing recovery and bootloader menus.
Only in the bootloader menu, the computer installed the drivers for Motorola Flash Interface, and I can see a device called S Flash OMAP3630 plugged in.
Is it possible to access the memory using this interface?
I accidently erased everything from the KF2, all I have on it now is the recovery.
How can I get a rom back on the device?
When I plugged it in the computer under Device Manager it says Portable Devices >> F:/
When I go to my computer to try to enter f:/ its inaccessible.
How can I fix this?
Thanks!
Same issue here. Understood the instruction to wipe everything before installing ROM to mean "System" and "Internal Storage" as well. Now the downloaded ROM and "gapps" zip files are gone...
Found something called "ADB Sideload" in TWRP, could that help?
Like the OP, would appreciate some help. Kindle is a brick for now...
chipsndukes
Back Up & Running
First You need a Fastboot Cable.
Run The Recovery Tool. (Options 1 then 2)
When its completed unplug the Fastboot Cable and press and hold the power button until the KF2 turns off.
Turn it back on and you are all set to Root it!
Rooting
[ONE-CLICK] Automated Freedom-Boot and TWRP installer
OK, thanks LEGEND94, that helped !
Only difference to above: did not use a Fastboot cable to get into fastboot mode, rather fmkilo's technique here: http://forum.xda-developers.com/showthread.php?t=2117224
Held off button to shut down and restarted without having to do anything else, did not have to type any command to get out of fastboot mode.
Am restarting root and ROM flashing, hopefully will work this time.
Thanks again,
chipsndukes
chipsndukes said:
OK, thanks LEGEND94, that helped !
Only difference to above: did not use a Fastboot cable to get into fastboot mode, rather fmkilo's technique here: http://forum.xda-developers.com/showthread.php?t=2117224
Held off button to shut down and restarted without having to do anything else, did not have to type any command to get out of fastboot mode.
Am restarting root and ROM flashing, hopefully will work this time.
Thanks again,
chipsndukes
Click to expand...
Click to collapse
even though legend was OP, his method was a bit overkill, but totally fine.
Once you have recovery, or even the bootloader, you should NEVER need to restore. From the bootloader you can get into fastboot now, and from fastboot you can get the recovery.
As for putting files on, I'm not sure. I could look it up but you both got your issues solved. If someone coming here does need the help, PM me and I can look it up, but from what i remember on other android devices, usually the recovery somewhere has an option to mount USB like a storage device (probably bad wording there) but basically just like when you "turn on usb storage" in the android OS.
I am ASSUMING TWRP has something similar, and if I'm wrong, I'm sure you can always ADB to push the files onto the device from your PC in fastboot mode.
iytrix said:
even though legend was OP, his method was a bit overkill, but totally fine.
Once you have recovery, or even the bootloader, you should NEVER need to restore. From the bootloader you can get into fastboot now, and from fastboot you can get the recovery.
As for putting files on, I'm not sure. I could look it up but you both got your issues solved. If someone coming here does need the help, PM me and I can look it up, but from what i remember on other android devices, usually the recovery somewhere has an option to mount USB like a storage device (probably bad wording there) but basically just like when you "turn on usb storage" in the android OS.
I am ASSUMING TWRP has something similar, and if I'm wrong, I'm sure you can always ADB to push the files onto the device from your PC in fastboot mode.
Click to expand...
Click to collapse
Unfortunately usb Mount doesn't work in the kf2 twrp. I would love the option.
You CAN adb sideload from twrp though.
--
Sent from my Kindle Fire 2, CM 10.1
What I did above is the easiest way, the sideload didn't even work!
chipsndukes said:
Held off button to shut down and restarted without having to do anything else, did not have to type any command to get out of fastboot mode.
Click to expand...
Click to collapse
One change to the above statement. I did have to get out of fastboot mode, but it was confusing how because the terminal emulator was now gone.
I did this instead via a command window with the Fire plugged into the computer. I sent the "fastboot -i0x1949 oem idme bootmode 1" command while in the root directory for the KF2_SRT_10.2.3 restore package, there is a fastboot.exe file there.
Hope that helps.
chipsndukes
I have a Nexus 32gb 2013 model that I've rooted with Wug's Nexus root toolkit v. 2.04. Everything was all find and dandy when I tried to update to Timer's Rom (not his fault) and I somehow deleted the operating system. The Nexus just shows the "Google" logo with a unlocked logo beneath and nothing happens. I did do a backup when I originally unlocked and rooted the Nexus but when I tried to install the backup, it does nothing. I already tried the DeVeiw thing and it did nothing. Actually it did help my PC recognize my phone again. To make it worse, I tried to install something to the Nexus but the computer won't recognize the Nexus. Neither will it load anything from an OTG cable. I took it to some place in town and they told me although the Nexus charges without any issues, the port might be messed up but I think this was his way of saying he has no idea what's up. Any ideas would be greatly appreciated. P.S. I still have access to TRWP (V. 2.8.4) and under "Restore" I do have a backup in there named cm_flo_userdebug 4.3.1 JLS361 blablabla. I already tried to install that with no luck. Am I boned? Any ideas would be greatly appreciated.
Does your computer see it when it's in fastboot? If so, flash a factory image (with fastboot) and start over.
And don't use toolkits.
No. Sadly it does nothing when I plug it in.
Does your computer recognize it while in bootloader? When in recovery, do you mount /system?
It does nothing when I plug it in. Not sure what you mean by me mounting the system.
1. Try shutting down the tablet all the way (screen black and fully off).
2. Then, hold down the power and volume down button. You should arrive to the "Fastboot" menu. While there, you should flash a recovery. Get TWRP for your device (really nice sideload).
3. Run a fastboot to flash a recovery so you can install an OS, like so:
Code:
fastboot flash openrecovery-twrp-2.8.5.0-flo.img
4. Reboot after installing TWRP. Hold power and volume down again.
5. Use your volume rocker to select "Recovery Mode" and press the power button. TWRP should start up.
6. Go into "Advanced" and select "ADB Sideload".
7. Sideload a ROM to your device by using:
Code:
adb sideload cyanogenmod.zip
Do GAPPS now if you need to.
8. Reboot, clear caches, and get back online.
---
If ADB refuses to sideload, make sure you've installed the proper ADB drivers for the device.
pacificfils said:
1. Try shutting down the tablet all the way (screen black and fully off).
2. Then, hold down the power and volume down button. You should arrive to the "Fastboot" menu. While there, you should flash a recovery. Get TWRP for your device (really nice sideload).
3. Run a fastboot to flash a recovery so you can install an OS, like so:
Code:
fastboot flash openrecovery-twrp-2.8.5.0-flo.img
4. Reboot after installing TWRP. Hold power and volume down again.
5. Use your volume rocker to select "Recovery Mode" and press the power button. TWRP should start up.
6. Go into "Advanced" and select "ADB Sideload".
7. Sideload a ROM to your device by using:
Code:
adb sideload cyanogenmod.zip
Do GAPPS now if you need to.
8. Reboot, clear caches, and get back online.
---
If ADB refuses to sideload, make sure you've installed the proper ADB drivers for the device.
Click to expand...
Click to collapse
I tried doing this but there is no way for me to side load anything because the PC wont recognize it. I think I am boned. I seriously wondering if there is something wrong with the USB connection even though it charges, I cant seem to get the PC to recognize it. The Nexus goes into TWRP but it wont recognize an OTG cable. When I connect it and try to select it, it just doesn't register. I wonder if I need to changed the USB board?Any other ideas before I do that? P.S. thanks for any help guys, I really appreciate any input.
Hello,
Something interesting happened... I have rebooted to fastboot, unlocked, jumped back to fastboot, and there were few thing to select "reboot" "shutdown" "reboot bootloader" "reboot recovery". I thought to myself, well lets look how does the stock recovery looks like... And now I'm stuck with this.
https://youtu.be/ea1gZ_KohAw
It doesn't matter how long I press the power button... It still reboots into this nonsense...
So... Anyone encountered the same problem?
Should I just wait until the battery will drain?
On the screen it says:
E:failed to mount /cache (invalid argument)
E:Can't mount /cache/recovery/last_locale
EDIT: SOLVED
Ereniemis said:
Hello,
Something interesting happened... I have rebooted to fastboot, unlocked, jumped back to fastboot, and there were few thing to select "reboot" "shutdown" "reboot bootloader" "reboot recovery". I thought to myself, well lets look how does the stock recovery looks like... And now I'm stuck with this.
https://youtu.be/ea1gZ_KohAw
It doesn't matter how long I press the power button... It still reboots into this nonsense...
So... Anyone encountered the same problem?
Should I just wait until the battery will drain?
On the screen it says:
E:failed to mount /cache (invalid argument)
E:Can't mount /cache/recovery/last_locale
EDIT: SOLVED
Click to expand...
Click to collapse
how did you solve??
xlylegaman said:
how did you solve??
Click to expand...
Click to collapse
Okay...
1) booted to fastboot through http://forum.xda-developers.com/huawei-watch/development/guide-boot-fastboot-mode-t3225382
2) booted to recovery, not with "FLASH" just with "fastboot boot twrp.img" (e.g. http://forum.xda-developers.com/hua...p-twrp-2-8-7-0-recovery-huawei-watch-t3224714 )
3) went to "reboot" in TWRP and clicked "reboot to recovery", since I haven't flashed the recovery, just booted into it, it rebooted to the stock recovery.
4) In stock recovery I have done factory reset and it started to work again.
PS: I rebooted from TWRP to stock recovery, because the TWRP couldn't mount any of my /system/ /cache/ /data/, but the stock worked flawlessly.
Won't work
Ereniemis said:
Okay...
1) booted to fastboot through http://forum.xda-developers.com/huawei-watch/development/guide-boot-fastboot-mode-t3225382
2) booted to recovery, not with "FLASH" just with "fastboot boot twrp.img" (e.g. http://forum.xda-developers.com/hua...p-twrp-2-8-7-0-recovery-huawei-watch-t3224714 )
3) went to "reboot" in TWRP and clicked "reboot to recovery", since I haven't flashed the recovery, just booted into it, it rebooted to the stock recovery.
4) In stock recovery I have done factory reset and it started to work again.
PS: I rebooted from TWRP to stock recovery, because the TWRP couldn't mount any of my /system/ /cache/ /data/, but the stock worked flawlessly.
Click to expand...
Click to collapse
I tried the above but after the bootloop adb won't recognize my device, so after entering bootloader I can't flash twrp. Any solutions?
Check your drivers, if you have eg. windows 7/8/8.1/10 you will have to install proper driver... which is not-official driver for hwatch, and I had to restart windows in "developer mode" "disable driver signatures" and then I have succesfully installed drivers and the computer recognized it.
To install hwatch drivers I've used this https://www.reddit.com/r/hwatch/comments/3n9ckp/how_to_get_adb_access_over_usb/
and maybe you can use this, but I'm not sure http://forum.xda-developers.com/huawei-watch/general/unlocking-easy-t3205219
Ereniemis said:
Check your drivers, if you have eg. windows 7/8/8.1/10 you will have to install proper driver... which is not-official driver for hwatch, and I had to restart windows in "developer mode" "disable driver signatures" and then I have succesfully installed drivers and the computer recognized it.
To install hwatch drivers I've used this https://www.reddit.com/r/hwatch/comments/3n9ckp/how_to_get_adb_access_over_usb/
and maybe you can use this, but I'm not sure http://forum.xda-developers.com/huawei-watch/general/unlocking-easy-t3205219
Click to expand...
Click to collapse
I tried installing the drivers from the above link, and disable signature verification too. Tried the second method suggested to force the drivers also and still no success.
Is it possible that my watch sin't allowing ADB access?
When the new update came, I factory reset my watch, unlocked bootloader, tried rebooting into recovery so i could flash and this happened.
Will I have to replace the watch?
Doesn't work. Makes me think my partitions are f**ked. In the past, I was able to odin myself out of this. I have no idea what to do guys.
Any idea?
FIXED: By doing what he said before by booting to TWRP. But when you do, do this. WIPE -> Advanced wipe -> Select Cache -> tap "Repair or change File System" -> Repair. After this, I had no more bootloops when going to stock recovery. Now to figure out why I keep throwing the error 7 when updating to MM.
hi
i managed to get mine working as well ! (Thanks to abhanli, pkt_lnt and skin180)
make sure you are in fastboot menu on your watch (holding the power button till switches off and the pressing again after vibrates)
most important thing next is to press shift and right click anywhere in the adb folder on your computer, and then run command prompt from there, otherwise adb will not load up and you will think that you have just run a dodgy script !
unlock your bootloader (typing "Fastboot Oem Unlock" in the command prompt in adb folder)
then you can use steps of skin180 (link above)
OR
https://developer.android.com/wear/preview/downloads.html
scroll down to huawei watch and choose second download option (non preview image for after testing) (thanks pkt_lnt)
extract into your adb folder (located in c:\)
then using the command prompt in adb folder, navigate to that extracted folder (using dos commands)
then if you are on windows, type "flash-all.bat"
hey presto - will work !
when it reboots, you may think "darn it still has spinning dots !" but if you wait about 5-10 mins it progresses past that stage and comes up with welcome screen !
My watch is working again !
HUAWEI customer services are a pile of POO. Their repair centre in UK is waste of time. They never answer the phone and never reply to messages.
If the Huawei watch wasnt so beautiful, i'd never bother with them !
Good luck and thanks all.
Good work poorak!
But, you only need to post this information once, not several times on different threads....
galaxys said:
Good work poorak!
But, you only need to post this information once, not several times on different threads....
Click to expand...
Click to collapse
thought id help as many people as i can for which ever thread they get to whilst searching for a solution !
Hwatch bootloop issue
Hi i have hwatch with bootloop too, tried to do everything i could and i can't get my computer to recognise hwatch, i only get "unknown device" in manager, i have stock recovery, locked bootloader and bricked device i've tried to force instal drivers, dissabling signed drivers, and manually from "naked drivers" post above, no success, PLEASE help
Recovery bootloop
titus1001234 said:
Hi i have hwatch with bootloop too, tried to do everything i could and i can't get my computer to recognise hwatch, i only get "unknown device" in manager, i have stock recovery, locked bootloader and bricked device i've tried to force instal drivers, dissabling signed drivers, and manually from "naked drivers" post above, no success, PLEASE help
Click to expand...
Click to collapse
Hi, i have the same problem. My watch has an infinite recovery bootloop. I tried to turn on the watch in fastboot mode but it isn' t recognized by the pc, no feedback sounds or unrecognized driver, it's like it isn"t connected. Did you solve the problem?
Ereniemis said:
Hello,
Something interesting happened... I have rebooted to fastboot, unlocked, jumped back to fastboot, and there were few thing to select "reboot" "shutdown" "reboot bootloader" "reboot recovery". I thought to myself, well lets look how does the stock recovery looks like... And now I'm stuck with this.
https://youtu.be/ea1gZ_KohAw
It doesn't matter how long I press the power button... It still reboots into this nonsense...
So... Anyone encountered the same problem?
Should I just wait until the battery will drain?
On the screen it says:
E:failed to mount /cache (invalid argument)
E:Can't mount /cache/recovery/last_locale
EDIT: SOLVED
Click to expand...
Click to collapse
this thing happen to me but not in my watch in my phone, Im currently using huawei gr5 2017, what should i do? please help me
poorak said:
hi
i managed to get mine working as well ! (Thanks to abhanli, pkt_lnt and skin180)
make sure you are in fastboot menu on your watch (holding the power button till switches off and the pressing again after vibrates)
most important thing next is to press shift and right click anywhere in the adb folder on your computer, and then run command prompt from there, otherwise adb will not load up and you will think that you have just run a dodgy script !
unlock your bootloader (typing "Fastboot Oem Unlock" in the command prompt in adb folder)
then you can use steps of skin180 (link above)
OR
https://developer.android.com/wear/preview/downloads.html
scroll down to huawei watch and choose second download option (non preview image for after testing) (thanks pkt_lnt)
extract into your adb folder (located in c:\)
then using the command prompt in adb folder, navigate to that extracted folder (using dos commands)
then if you are on windows, type "flash-all.bat"
hey presto - will work !
when it reboots, you may think "darn it still has spinning dots !" but if you wait about 5-10 mins it progresses past that stage and comes up with welcome screen !
My watch is working again !
HUAWEI customer services are a pile of POO. Their repair centre in UK is waste of time. They never answer the phone and never reply to messages.
If the Huawei watch wasnt so beautiful, i'd never bother with them !
Good luck and thanks all.
Click to expand...
Click to collapse
problem is i can't find that download
Files Installed:
1.) Android SDK ( Android Studio ) for ADB Purposes
2.) SR3-SuperSU-v2.79-SR3-20170114223742 ( Which I have not been able to drop into root directory. Just the Internal Shared Storage
3.) twrp-3.1.1-0-bullhead.img ( Click Link For Source Download )
Alright,
I have tried flashing TWRP onto my Nexus 5X and can't seem to make this happen.
When I open up ADB from right clicking in my "platform-tools" folder and selecting "Open command window here", I start by putting my phone into the bootloader mode by typing the command, "adb reboot bootlader". I have to do this due to my volume down button not responding anymore. This should NOT prevent me from navigating any menus located inside the TWRP recovery menu as well as the default recovery screen. If I just use the Volume Up to go through the menus, it loops.
Ok, now, if I am in the bootloader, I want to type the following command into my ADB. That command would be the following:
fastboot flash reboot twrp-3.1.1-0-bullhead.img and/or
fastboot flash twrp-3.1.1-0-bullhead.img
When I do this, the only response I get from the ADB is, <Waiting for any device>...
So yeah..It just sits there and doesn't do anything.
When I am booted into the phone and I type the following command:
adb devices
I get the appropriate response back which is the hex output of the device. I can also make this output happen via, "Recovery Mode ( ADB Sideload )
I understand that ADB and Fastboot are 2 different territories when it comes to inputting/outputting data. On the ADB side, things seem to work as they should. On the Fastboot side, I don't have any recognition from the device itself.
CWM is not available from my understanding when it comes to the Nexus 5X on 7.1.2. I have looked and looked and could not figure out how to make that happen. However, I did see that TWRP works just fine one numerous Nexus devices so there really shouldn't be any issues flashing my device.
I have unlocked the bootloader and it is ready to be flashed with the TWRP custom recovery. I just can't seem to get it to flash as of right now and the recovery menu gives me a message saying, . I have been able to get past this, "No Command" error by simply holding the power button while simultaneously pressing the volume up button to enter the default recovery screen.
There is no option that says Flash from SD Card. Speaking of SD Card, this Nexus 5X doesn't even have a spot for an SD card so therefore a SD Card does not exist for this phone. How do you tell a phone to mount a drive that doesn't exist? Still confused about this as I have also tried to access the root folder so I can drop the SuperSU file into.
That should wrap up the issues I am having. Once again, I'm simply just trying to root this Nexus 5X on the latest android version 7.1.2. Any help to get this moving along would be greatly appreciated!
Thanks guys!
DarkXShadowX21 said:
Files Installed:
1.) Android SDK ( Android Studio ) for ADB Purposes
2.) SR3-SuperSU-v2.79-SR3-20170114223742 ( Which I have not been able to drop into root directory. Just the Internal Shared Storage
3.) twrp-3.1.1-0-bullhead.img ( Click Link For Source Download )
Alright,
I have tried flashing TWRP onto my Nexus 5X and can't seem to make this happen.
When I open up ADB from right clicking in my "platform-tools" folder and selecting "Open command window here", I start by putting my phone into the bootloader mode by typing the command, "adb reboot bootlader". I have to do this due to my volume down button not responding anymore. This should NOT prevent me from navigating any menus located inside the TWRP recovery menu as well as the default recovery screen. If I just use the Volume Up to go through the menus, it loops.
Ok, now, if I am in the bootloader, I want to type the following command into my ADB. That command would be the following:
fastboot flash reboot twrp-3.1.1-0-bullhead.img and/or
fastboot flash twrp-3.1.1-0-bullhead.img
When I do this, the only response I get from the ADB is, <Waiting for any device>...
So yeah..It just sits there and doesn't do anything.
When I am booted into the phone and I type the following command:
adb devices
I get the appropriate response back which is the hex output of the device. I can also make this output happen via, "Recovery Mode ( ADB Sideload )
I understand that ADB and Fastboot are 2 different territories when it comes to inputting/outputting data. On the ADB side, things seem to work as they should. On the Fastboot side, I don't have any recognition from the device itself.
CWM is not available from my understanding when it comes to the Nexus 5X on 7.1.2. I have looked and looked and could not figure out how to make that happen. However, I did see that TWRP works just fine one numerous Nexus devices so there really shouldn't be any issues flashing my device.
I have unlocked the bootloader and it is ready to be flashed with the TWRP custom recovery. I just can't seem to get it to flash as of right now and the recovery menu gives me a message saying, . I have been able to get past this, "No Command" error by simply holding the power button while simultaneously pressing the volume up button to enter the default recovery screen.
There is no option that says Flash from SD Card. Speaking of SD Card, this Nexus 5X doesn't even have a spot for an SD card so therefore a SD Card does not exist for this phone. How do you tell a phone to mount a drive that doesn't exist? Still confused about this as I have also tried to access the root folder so I can drop the SuperSU file into.
That should wrap up the issues I am having. Once again, I'm simply just trying to root this Nexus 5X on the latest android version 7.1.2. Any help to get this moving along would be greatly appreciated!
Thanks guys!
Click to expand...
Click to collapse
That's because you are entering commands that do not exist.
To temporarily live boot TWRP, enter the following. TWRP resets back to stock recovery after a reboot:
fastboot boot twrp-3.1.1-0-bullhead.img
To actually flash TWRP, enter the following. Flash root to keep TWRP if desired:
fastboot flash recovery twrp-3.1.1-0-bullhead.img
I use "ADB push" to transfer files from my MacBook to my 5X. You should be able to do this in TWRP. FYI, I transfer files to /sdcard since I usually intend to use it on the device. If I were using Windows, I believe this is the exact command to transfer files:
adb push filename /sdcard/Download
Sent from my Nexus 5X using Tapatalk
In you shoes, I would try Wugsfresh NRT. That thing helped me several times in the past. Its very straightforward and user-friendly and everything is well explained there. Take your time.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
That's because you are entering commands that do not exist.
To temporarily live boot TWRP, enter the following. TWRP resets back to stock recovery after a reboot:
fastboot boot twrp-3.1.1-0-bullhead.img
To actually flash TWRP, enter the following. Flash root to keep TWRP if desired:
fastboot flash recovery twrp-3.1.1-0-bullhead.img
I use "ADB push" to transfer files from my MacBook to my 5X. You should be able to do this in TWRP. FYI, I transfer files to /sdcard since I usually intend to use it on the device. If I were using Windows, I believe this is the exact command to transfer files:
adb push filename /sdcard/Download
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
jugoslavpetrovic said:
In you shoes, I would try Wugsfresh NRT. That thing helped me several times in the past. Its very straightforward and user-friendly and everything is well explained there. Take your time.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you guys for the help! I successfully rooted my Nexus 5X! It's time to go exploring into the roots! :good: