I downloaded and installed Preview 4 on my device.
Once it was installed I rooted and flashed TWRP. Everything was working well except TWRP. Each time I booted into Recovery, 'bad command' displayed on the screen.
Wondering if anyone else encountered this or has any suggestions for further troubleshooting.
Thanks.
Related
Hey guys, i have been having some major issues with my Nexus 7 WiFi. So basically, i was using it and it rebooted and asked me for an encryption key, I had never encrypted the device so i didn't know what it was talking about, i rebooted and it gave me the same message. Then, i booted into fastboot and tried to flash the stock google recovery image for 4.2.2. It didn't flash and it errored out for everything except the radio. Then it told me that i needed the grouper image, which is the one that i downloaded from google. It stopped booting so i grabbed a TWRP recovery and tried to flash it. It flashed and then when i went to wipe all the partitions except internal storage, nothing would wipe and it said it was unable to. Anybody have a solution to this or am a boned?
Thanks for your time guys, it is much appreciated!
Bump. Anyone at all know a solution?
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
I've the same problems with my nexus 4
gerardgerard said:
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
Click to expand...
Click to collapse
Hi gerardgerard,
I also wanted to flash my Nexus 4 with Cyanogenmod 12.1. So I installed TWRP into recovery and wiped everything, like it's explained in the wiki. I can also see the error "unable to mount /usb-otg". When I want to reboot the system I always get back to TWRP. Cyanogenmod doesn't boot correctly. Did you find a solution for the problem?
same problem
Hi
I'm having the same problem. As follows:
Cause (my mistake): I have been using Cyanogen-mod nightlies for a couple of months on my Nexus 4, and made the grave mistake of leaving the phone to upgrade one night but without it being plugged in properly - and it ran out of power part way through! (At least, that's what I think happened).
Fortunately, it would boot into bootloader and I could use adb/fastboot. I (re)installed TWRP 2.8.7.0 (from my Mac, using fastboot). And that works fine - I can boot into twrp ok.
Next I loaded the latest nightly from cm (using fastboot - is this what people call sideloading?) and used twrp to install it. It goes through the installation fine (the only error message is that it can't mount /usb-otg). But when I reboot it just goes back to twrp.
I then tried installing the earlier cm nightly that I know worked, but with the same result.
Finally, before I first installed cm I did a backup (using twrp), and I have tried recovering that. It seems to do all the right things, but again when I reboot it just goes back to twrp.
Any suggestions would be welcome.
Thanks
J
Flash back to a completely stock ROM and run through the set up to make sure everything works. Then copy CM to the phone, reboot to fastboot, flash twrp, immediately boot into recovery using the volume and power button without leaving fastboot, wipe data, cache, system, flash CM, reboot.
If the phone will not boot after flashing a stock ROM, boot to fastboot, flash the userdata.img file, and immediately go to stock recovery without leaving fastboot, wipe data/cache, reboot.
It works now!
I managed to fix the problem ... I found this guide for the Nexus 5:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
and I applied those instructions. It didn't work first time, so I just repeated them and now it's working. I used the 5.1.1 stock downloaded from https://developers.google.com/android/nexus/images#occam.
I guess this is what audit13 means in their post - so thanks are due there.
I will next reinstall twrp and cm and I don't expect any problems with that (having done it successfully before).
Smaje
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Mmmh, strange, I did a factory installation (latest 5.1.1 from Google) and started the same thing from scratch ... and guess what... the system is booting fine now.
No idea why it did not work on my first attempt .
Regards, mistersixt.
mistersixt said:
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Click to expand...
Click to collapse
Same here. Running stock until today, wanted to see a different ROM, flashed TWRP 3.0.0, it refused to boot anything else. Tried to flash DU, then tried Chroma. Did a full wipe, then an advanced wipe selecting everything, then a full format, same thing. Installed TWRP 2.8.7, same thing. Finally installed latest stock, it is now booting, optimizing apps. I don't know if installing a custom rom will work or not yet.
Edit: Yeap, after flashing stock 5.1.1 and installing TWRP 3 again, the phone is now booting into DU.
First time I did a wipe with TWRP, it complained that it couldn't mount /data. Since this is the first time doing it, I assumed it was normal. After going through a full format, it didn't complain about data anymore, but it did complain about something to do with /dev/zero and another file under /dev/. I assume it was trying to dd /dev/zero to a file under /dev/ that didn't exist.
+1
Done the whole process from scratch again and worked like a charm
Hello, same story here.
First I:
- unlocked bootloader
- flashed TWRP (last version)
- flashed Chroma and Gapps
- reboot
=> I consistently rebooted on TWRP. No way to properly install the ROM. No error message at all.
Then I found this thread, and did as described:
- flashed the latest stock ROM
- flashed TWRP again (took me ages to manage to do this: TWRP would not install. I don't know how I finally did it, but at some point it suddenly worked. Probably a driver problem)
- flashed Chroma and Gapps again
Bingo, this time it worked! I don't know why it didn't work the first time. Could it be linked to the bootloader unlock thing?
Hi, I need help in installing Recovery.
I unlocked the bootloader, installed TWRP and then CyanogenMod 13 ROM.
After this, Oxygen Os 3 got released. I downloaded the zip file and flashed through TWRP.
Oxygen OS got installed but after this, I couldn't go back in TWRP recovery.
I tried everything. I use "fastboot flash recovery twrp.img"
everything works
but when I boot in recovery, phone gets stuck on the LOGO and nothing happens.
Is there any way to solve this issue.
Almost the same for me.
When I flash oOS 3.0.2, unable to reboot using Grarak'sTWRP or TWRP-3.0.2-1.
Always stuck on boot logo without animation.
I reverted to old TWRP and oOS 2.2.1
piyushmodi01 said:
Hi, I need help in installing Recovery.
I unlocked the bootloader, installed TWRP and then CyanogenMod 13 ROM.
After this, Oxygen Os 3 got released. I downloaded the zip file and flashed through TWRP.
Oxygen OS got installed but after this, I couldn't go back in TWRP recovery.
I tried everything. I use "fastboot flash recovery twrp.img"
everything works
but when I boot in recovery, phone gets stuck on the LOGO and nothing happens.
Is there any way to solve this issue.
Click to expand...
Click to collapse
Try to install OOS recovery or Hybrid recovery.
Nobody ever learns or reads nowadays....
Read up on bootloader versions on Oneplus 2 and you will find the explanation perfectly understandable.
Thank You So much for your help. Finally it worked but I lost my data! Anyways, no issues.
Can you give us the way you fixed your problem .
Thanks
So basically what happened was I unlocked my bootloader using this tutorial https://wiki.pixelexperience.org/devices/fajita/install/#unlocking-the-bootloader after that I flashed the Pixel Experience Recovery and I did the rest of the steps. After all of that my phone worked perfectly and i had Pixel Experience Plus installed but I wanted to have TWRP Recovery instead of the Pixel Experience Recovery so I asked on the XDA discord on how I would flash TWRP if I already have Pixel Experience Recovery, then some guy told me to just flash TWRP in fastboot like I did for the Pixel Experience Recovery, so I did. After doing that I realized that was a huge mistake because my phone started booting only to TWRP. I looked around in TWRP and I found a button that said "Fix Recovery Bootloop" so I did that. After doing that my phone booted but my wifi wasn't working and my sound wasn't working. By sound I mean not only the speakers, but also when I connected my headphones via Bluetooth. If I switched to slot b on TWRP it would bootloop and after bootlooping 2 times brought me to the Pixel Experience Recovery saying that I might have corrupted my data and an option to factory reset. I clicked on the back arrow and booted into the bootloader and typed on my pc "fastboot boot twrp.img" and got back into TWRP recovery and switched the slot back to a. After switching it back it once again started booting into TWRP recovery when I tried to boot to the system. I did the same thing going to the settings and clicking "Fix recovery bootloop" and got back in the system. Sadly all of my problems still remain. Could someone here tell me what I should do and how to fix my phone?
M6D said:
So basically what happened was I unlocked my bootloader using this tutorial https://wiki.pixelexperience.org/devices/fajita/install/#unlocking-the-bootloader after that I flashed the Pixel Experience Recovery and I did the rest of the steps. After all of that my phone worked perfectly and i had Pixel Experience Plus installed but I wanted to have TWRP Recovery instead of the Pixel Experience Recovery so I asked on the XDA discord on how I would flash TWRP if I already have Pixel Experience Recovery, then some guy told me to just flash TWRP in fastboot like I did for the Pixel Experience Recovery, so I did. After doing that I realized that was a huge mistake because my phone started booting only to TWRP. I looked around in TWRP and I found a button that said "Fix Recovery Bootloop" so I did that. After doing that my phone booted but my wifi wasn't working and my sound wasn't working. By sound I mean not only the speakers, but also when I connected my headphones via Bluetooth. If I switched to slot b on TWRP it would bootloop and after bootlooping 2 times brought me to the Pixel Experience Recovery saying that I might have corrupted my data and an option to factory reset. I clicked on the back arrow and booted into the bootloader and typed on my pc "fastboot boot twrp.img" and got back into TWRP recovery and switched the slot back to a. After switching it back it once again started booting into TWRP recovery when I tried to boot to the system. I did the same thing going to the settings and clicking "Fix recovery bootloop" and got back in the system. Sadly all of my problems still remain. Could someone here tell me what I should do and how to fix my phone?
Click to expand...
Click to collapse
If the Sound+Wifi is the only thing that's killing you, Installing a Custom Kernel should do the trick.
Huskied said:
If the Sound+Wifi is the only thing that's killing you, Installing a Custom Kernel should do the trick.
Click to expand...
Click to collapse
What custom kernel do you recommend? Also I can't load videos on my phone. I'm running Android 11 btw.
M6D said:
What custom kernel do you recommend? Also I can't load videos on my phone. I'm running Android 11 btw.
Click to expand...
Click to collapse
MCD is worth a shot.