Hi,
New nexus 10 arrived today. Installed drivers from NRT.
Computer cannot see the device with ADB (usb debugging enabled) so manually rebooted into bootloader.
Unlocked bootloader successfully with fastboot then restarted system.
Watched loading screen for 10 minutes then three button reset into bootloader.
Used fastboot to push twrp 2701 successfully.
Entered twrp, attempted backup, stated failed, lots of can't mount this or that errors.
Rebooted, watched loading screen for 10 minutes, three button reset to bootloader.
Pushed philz recovery and entered. Attempted backup failed again with similar errors. Internal storage showing as 0mb.
Rebooted and currently watching loading screen.
When in the bootloader fastboot recognised the device but not adb so i've no way of pushing a rom zip to the device in order to flash it with the recovery.
Any clues on what to try next appreciated.
Crisis over.
Pushed twrp over again and entered.
Loads of cannot mount errors, unable to backup existing rom.
Factory reset failed.
then...
Format data...and yay, that seems to have fixed it.
Was then able to factory reset, reboot and it loaded.
Downloading CM11 now to flash.
What a royal PITA lol.
Related
After I rooted my A500, I wanted a clean slate to work with, but when I tried factory resetting, everything stayed exactly the same as if the factory reset wouldn't complete. I tried wiping through ROM manager as well again with no results. I went into terminal emulator and gained superuser permissions, then typed in 'wipe' and it gave me the option to wipe the system or something else. Long story short, I typed in to wipe the system and everything went to hell. I got force close notifications one right after the other, my tablet popups starting coming up in different languages, and then the tablet shut off. When I went to reboot it, it stopped at the Acer logo screen. I had CWM recovery installed or so I thought (I had it installed through ROM manager but I can't boot into recovery or anything now). When I boot with the power button and Vol- it says:
Erasing Cache before SD update...
SD update cmd: recovery
--update_package=SDCARD: update.zip
Booting recovery kernal image
Recovery verified failed...
I've tried booting with the power button and Vol+ and flipping the rotation lock and after clearing the Userdata and Cache and rebooting, it sticks on the logo screen. I've read countless forums both here and elsewhere about downloading an update.zip to the SD card and letting the update run its course but nothing happens. I have no recovery access, no fastboot access, no CPUID, no nandroid backup, and no way to push files to the tab except through the external SD card.
The computer will recognize the device as an MTP device when plugged in via USB, but the drivers won't install. I've manually installed drivers from the Acer website and multiple third parties with no luck.
I really have no other ideas so I thought I'd come to you guys. Literally any help whatsoever would be appreciated so thanks in advance
Hey,
Very strange query but here goes. Rooted phone a while back and installed CM13 along with recovery. Was trying to update TWRP{ by downloading .img from their website, went to flashing, selected the file and hit recovery. Said it was succesful so attempted to reboot. Plugged in to charge and was charging but when I tried to switch it on, it was stuck in Cyanogen Bootloop (blue alien stayed on the screen for 10+ minutes). Tried rebooting to recovery by hitting power + volume down and instead of booting to TWRP, it takes me to a Cyanogen recovery screen where I see the following options:
Cyanogen Recovery.
- Reboot system now
- Apply update
- - -apply from ADB
- - -choose from emulated
- Factory reset
- - -system reset
- - -full factory reset
- - -wipe cache
- Advanced
- - -reboot recovery
- - -reboot to bootloader
- - -Wipe system partition
- - -view recovery logs
Here's what I tried as troubleshooting. Tried to do a system reset, factory reset and wiped cache and tried to restart my phone but no luck. Still stuck in boot loop with CM logo. Tried to reboot to bootloader but the screen is stuck with the 1+ logo for about 5 mins so gave up on that.
Basically, right now I can't access anything on the phone, can't find any way to reinstall a ROM and when I plug it into my Macbook, it is not recognised. So I'm screwed sideways. I had TWRP recovery set up so I have no clue how this happened but can anyone please help me with this.
If data isn't at risk try the Qualcomm recovery tool one the oneplus forum it's by nammand bhal (definitely butchered the name) but all data is lost and resets the phone to out of box conditions locked bootloader and Oos 2.2.1 so this is often a last measure (tool is Windows but may have Mac variant and the file is quite big)
My suggestion is to try to boot to bootloader again and flash TWRP
hmm mac book I don't have much experience with those
If you have a Windows pc you can use adb or on Mac if it has it. Also when it come to being found by a computer in recovery it should but again don't have a mac
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
AJay27 said:
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
Click to expand...
Click to collapse
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
justicesourglide said:
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
Click to expand...
Click to collapse
Actually I don't think the issue was with the Macbook since I have unlocked, flashed custom recoveries and sideloaded ROMs on several devices including OP2, OP3, Nexus 5, etc on mine. It might have been some accidental flashing error, which unfortunately ended up bricking your device.
I have the MetroPCS xt1765 running lineageos 14.1. When unlocking and doing all that jazz, the guide said that you can't flash twrp, only boot it. But I got annoyed that /data wouldn't mount so I just tried to flash it anyway and it worked. On cmd it said that the file wasn't signed or corrupt, but it still wrote to the device. I thought nothing about it at first but when I tried to boot the device it automatically when into twrp. I tried to reboot to system again, and the same thing happened.
Eventually /data successfully mounted and I was able to format it and install linage. I hoped that would fix the problem but it's still there. I believe I would need the stock boot image and probably stock recovery as well. I hope someone out there has these files.
Also when booting with factory mode, my data isn't working at all. The apn setting are right and all, but it's not working.
ZacharyTheUmbreon said:
I have the MetroPCS xt1765 running lineageos 14.1. When unlocking and doing all that jazz, the guide said that you can't flash twrp, only boot it. But I got annoyed that /data wouldn't mount so I just tried to flash it anyway and it worked. On cmd it said that the file wasn't signed or corrupt, but it still wrote to the device. I thought nothing about it at first but when I tried to boot the device it automatically when into twrp. I tried to reboot to system again, and the same thing happened.
Eventually /data successfully mounted and I was able to format it and install linage. I hoped that would fix the problem but it's still there. I believe I would need the stock boot image and probably stock recovery as well. I hope someone out there has these files.
Also when booting with factory mode, my data isn't working at all. The apn setting are right and all, but it's not working.
Click to expand...
Click to collapse
When it was booting to twrp only, you just select reboot bootloader and in bootloader select start and you will get system. This twrp doesn't read and clear bootloader control block (BCB) properly which causes this. There is a fix. I'll find the link.
Do you mean fastboot/bootloader mode? If yes, try this
steps i did:
installed twrp twrp-3.4.0-1-markw
flashed lineage-17.1-20200920-UNOFFICIAL-markw by shiabzzz
wiped data and cache, excluding internal storage
tried to flash gaps but failed due to error 20
flashed magisk
reboot.
now im stuck on bootloop. i know i should have deleted data before flashing the rom, not afterwards. when i press power+up it's not going to recovery.
how can i fix it?
are gaps mandatory for it to boot?
will my phone turn off when it runs out of battery, will i be able to go to recovery then?
update: i can access fastboot mode, but when connecting to pc and trying to boot to recovery it says "waiting for device".
Using the miflash tool I flashed stock firmware (some version of android 8) after previously having a custom ROM installed. Everything worked fine until I rebooted after updating to the latest version using OTA.
My phone never got past the android one screen where it would freeze part way through, and after removing my sim card I could get to the pin unlock screen before the lock screen but after inputting the correct pin it would reboot and ask me for it again and again. I can get into fastboot fine but since usb debugging wasn't enabled and my bootloader is locked I can't reflash.
Booting into recovery also only brings me to a screen where the android mascot has a red triangle with an exclamation mark and a message saying "No command", so I can't factory reset.
Is there anything I can do to unlock the bootloader in this state or factory reset? (all flash tools and fastbooting into TWRP require the bootloader to be unlocked which in turn requires usb debugging to be activated)
Thanks for your time.
Update: I messed around with stuff on the cli based tissot tool and used option 2 to boot me into TWRP. It didn't do that but brought me into android where a system process kept repeatedly closing until a random factory reset happened.
I then got into normal android for a bit before I had to reboot (did remember to unlock the bootloader this time). I can now install twrp fine but every time I install the stock rom using miflash or try to install resurrection remix through twrp I get the same bootloop issue.
For some reason also my internal storage is completely empty no matter what i do so i need to sideload roms via sd card. And sometimes twrp gives me the error "failed to mount /system"
Trying the latest version of LineageOS next.
Update 2: if you have the same issue I had, the only working fix I've found is this restore point for twrp. Have not tried to update yet in case it breaks again but will make a final update with how that goes.
[SOLVED] Mi A1 BOOTLOOP
THIS PROBLEM IS VERY ANNOYING!! (The reason is because i didn't backup EFS before i flash Custom ROM) And I would like to share how to RESOLVE it. **your phone must be Unlocked Bootloader. Search Google how to do it. (Quick tip: in Fastboot...
forum.xda-developers.com