Hello everyone I'm new here.
I got my D855 upgraded to CM14 couple of days ago using TWRP and it was a little buggy, so I decided to stick with the nightly update. And I also noticed that they just released CMR so I flashed my recovery from TWRP to CMR, hoping to get better compatibility. But I was wrong, during my latest upgrading, also my first time using CMR, after the installation process completed, it just stucked there. After half an hour waiting I decided to pull the battery out, which opened pandora's box, the system just wouldn't load, stucked on the CM face page forever.
Then I tried lots of stuff, none of which worked:
go to recovery and use usb to transfer TWRP image to /sdcard then flash it back to TWRP, so that I could flash the rom again cuz previously didn't have any issue with TWRP - failed because CMR had no function for usb connection
adb push TWRP image to /sdcard then flash it - failed because somehow usb debugging is disabled
adb sideload to flash TWRP - failed because usb debugging is disabled
fastboot flash TWRP recovery - failed, CMR does allow me to reboot to bootloader but when I connected and typed "fastboot devices" in terminal, nothing showed up
Any ideas? Thanks in advance!
Nov 21: Problem solved by flashing factory rom using LG flash tool, defly a brick saver
Related
Hey guys!
Well, I was trying to reflash Vanir+DirtyV (I was with CM11+Fancy but I like to make some changes from time to time) and I also decided to flash the most recent TWRP in the process because I had the 2.7.0.0 one and I thought the newer one would be better optimized.
After flashing the new recovery I tried to use adb commands to push the flashable zips but it came without success so I tried to reflash the old TWRP from fastboot (I had done a complete wipe of all the partitions excluding USB OTG before rebooting into the fastboot)
I don't think it is a driver problem because some hours ago everything was fine with adb and fastboot but what could it be? I am without any OS in the system but I rooted the device before rebooting into fastboot and I can go into recovery nicely I just can't connect anything with the laptop
OK, so maybe I've missed a step in the process... I have TWRP and CM12.1 running on my first Nexus 7 2013 WiFi (FLO) no problem...
Today, I unlocked the bootloader (OEM UNLOCK from Minimal ADB and Fastboot) and immediately fastboot flash recovery twrp-2.8.6.0-flo.img
Reboot into recovery, somehow the entire system is wiped out... only thing that works is TWRP.
I go through the process to restore back to Stock 5.1.0 (LMY47O) from https://developers.google.com/android/nexus/images
Now the system boots again, but when attempting to access recovery I just get the dead android with the red exclamation mark.
I fastboot flash recovery twrp-2.8.6.0-flo.img again, and again the system is wiped out. So this time I go in and fastboot flash system system.img from the stock image zip. Now the system boots and Recovery gives me a red exclamation mark again...
It's as if TWRP and Stock Android 5.1 are somehow incompatible and eating each other?! Except this doesn't explain why after doing the flash-all.bat that somehow the stock recovery doesn't work even with the stock ROM.
AND I JUST DID THIS A WEEK AGO ON ANOTHER DEVICE!
Another thing I'm struggling with is that when I'm in TWRP I can't get it to mount to the PC properly (I've done every driver combination imaginable). It'll show up in the "My Computer" list but no sub-folders show up (maybe this is because the entire "SDCard" has been wiped and there's no system structure?) and it won't let me copy files (like the Cyanogenmod zip to be installed).
Surely I'm missing something stupidly simple here. Please help me out!
MODERATOR: I accidentally created this thread in the other N7 forum, if someone can delete it please? It's at http://forum.xda-developers.com/nexus-7/help/recovery-kill-t3091308
Thanks!
So, with stock 5.1 booting and running fine, I just went through and did a fastboot flash recovery recovery.img using the recovery extracted from the android developers website (factory image), and I still get the little dead android with the red exclamation mark.
/edit apparently ^^^^ is expected behavior, just never saw it before... still doesn't explain why when I fastboot flash recovery twrp.img and reboot into twrp, the entire system has been wiped out and I can't mount or adb sideload to get CM.zip onto the device.
OK - this FIXED IT ALL: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
Apparently can't use TWRP from their website on the new hardware revision of the Nexus 7 (my other device is a few rev older)... you'd think they'd update that on their website?
I wasn't able to adb sideload from recovery though I could when the phone was on. so i tried clearing cache from stock recovery and it got interrupted. Now when i start the phone, boot loops and i can't even enter recovery. Any help please!
Update
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?
AnudeepS said:
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?
Click to expand...
Click to collapse
Where are you getting your adb/fastboot toolkit? If using the ones your Linux distro (Debian, Ubuntu, etc) provided, then consider them out of date. I had the same problem with fastboot recognizing my phone...once I downloaded fresh ones from Google's SDK, I was back in business!
Am on windows and i had fastboot_adb(1.0.32) already installed.
Update
I could update by flashing through Kernel Adiutor app (needs root permission & Busybox). Root lost when flashed complete firmware and root remained when flashed just the update file.zip.
what i did was-
I put zip file (completely downloaded firmware from ASUS website-also tried OTA downloaded and updated the phone) on MicroSD card, renamed the file MOFD_SDUPDATE.zip. This flashed through Kernel Adiutor app- recovery- cwm-flash.
Re-reooted the phone with 1 click method (method #3) when flashed the complete rom. If you just flash the update zip root remained.
All working fine for now.
PS: I use Z008 2gb model.
Hi all.
After OTA upgrade to android 6 of unlocked unrooted nexus 7 2013 WiFi i decided to unlock and install twrp.
I used adb and fastboot to flash version 2.8.7.
It went smooth but after reboot to recovery, twrp shell returns "can't mount *" for all partitions. And the device is bootlooping into this state (unless I boot into bootloader).
The worst part is that my pc wont recognise the tablet when connected. Adb devices returns an empty list. So i cant even flash stock recovery or do anything uing adb/fastboot.
HELP!!!!
[solved] falshed factory image manually using fastboot
It seems fastboot recognized the device while adb/pc couldn't.
I downloaded Android 6 factory image from google and flashed-all that.
Just updating in case some other noob who doesn't fully understand adb/fastboot relations.
I just got my OnePlus 3 last week and I am having some issues trying to root it. Initially, I was using Win7 and could not get anything to work (phone was never recognized - yes drivers were installed). I went to my laptop with Ubuntu 16.04 and had some success. I was able to unlock the phone; however, when I tried to flash twrp.img (and recovery.img), I kept getting a fastboot permissions denied error. I was using sudo and fastboot devices worked. Also, if I try "sudo fastboot boot twrp.img" nothing happens on the phone (or pc for that matter). I am totally perplexed. The OS on the phone is Oxygen 3.2.4. Thanx for any assistance.
Bill
Install all driver (1+ Mobile Usb driver and Adb)
Than Follow Toolkit Method On Xda.. Its work Fine For me... ? and Follow their Video
I had a similar problem with mine. I could flash TWRP but it wouldn't stick. Reboot the phone and try again, the factory recovery would be back. I tried every version of TWRP, adb, fastboot and the toolkit -- same result.
Finally fixed it by using the toolkit to flash the previous version of TWRP, then using TWRP to flash the latest version without rebooting the phone. With that done, no problems after rebooting system.
Now I can flash new ROMs.
How old does twrp have to be before you get positive results?