A friend of mine with a Google Nexus 4 attempted to root on 4.4:
"The unlocking of the bootloader went without a hitch, and I downloaded the CWM non-touch from here:http://www.clockworkmod.com/rommanager, in the "Nexus 4" row, and "Download Recovery" column, named "6.0.4.3". I placed the file on the desktop, flashed it onto the phone, and booted into it using the volume keys and the power button to select "Recovery mode" on the bootloader screen. From there, I wanted to reboot the phone, so I clicked the first option, the "reboot system now" selection. I received the message "ROM may Flash stock recovery on boot. Fix? THIS CAN NOT BE UNDONE.", and not wanted to do anything to mess up the installation, clicked the "*****Go Back*****" option. And then I received another message saying, "Root access is missing. Root device? THIS CAN NOT BE UNDONE." Again, I clicked the "*****Go Back*****" option, not wanting to mess up the recovery. It suddenly booted into the stock ROM, showing the Google screen with a little unlock symbol at the bottom. Then it moved on to the Kit Kat boot sequence, the one with the 4 different colored circles and all that. I waited for it to boot back into the stock ROM, but it stayed on that screen, a bootloop. I then proceeded to hold the power button to turn it off. I booted it again, and it bootlooped again. So I went back to CWM and wiped the data/factory reset, wiped the cache partition, and went into advanced and wiped the dalvik cache. Then I rebooted it once more, and it bootlooped once again. So now I've turned it off, and am attempting to find a solution to fix this. As a last resort, I can always unroot it and wipe the data again. But I would prefer to not to have to re-unlock and re-flash the phone, unless there is no other option. During this entire period, the phone was connected by USB cable to the computer, up until I wiped the data and caches, where I unplugged it, and allowed it to boot."
*****So overall, after installing CWM, the phone was put into a bootloop. factory reset was done, as well as wiped cache partition and dalvik cache*****
is there a way to get the device rooted, without using the traditional unroot method? I feel as if the error (if any) was simple, therefore there should be a simple solution. Thanks!
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 everyone,
As the title states, I'm stuck at the boot screen. It's got the Google logo with an unlock symbol at the bottom of the screen.
I was trying to update to the recent AOKP release (I had been on an earlier release) and something went wrong.
From this page http://forum.xda-developers.com/showthread.php?t=1766684 I followed these instructions:
Wipe data/factory reset, wipe cache, and wipe dalvik cache, then go into mounts & storage and format system (if using CWM). To format system w/TWRP, select Wipe then System!!!
I think the issue occured after I selected to wipe SYSTEM.
Now, I can get to the fastboot menu (volume down + power). I can select restart bootloader/recovery mode/start...but the phone always stops at the GOOGLE logo (with the unlock symbol at the bottom).
So then I tried to use the WugFresh tool kit to go "Back to Stock" with Current Status of "Soft-Bricked/Bootloop" but that didn't work either. The command prompt lines came up on the PC and it said everything was supposed to reboot (and may do it a few times) but mine just sat at the fastboot menu. When I tried again, I noticed a lot of things failing in the automated command prompt.
So now I'm not sure what to do. Can anyone help me?
Thanks
Edit: I should mention that I did update the bootloader first to makoz10o from http://forum.xda-developers.com/showthread.php?t=2105983
I have a brand new Note 4 that had the power switch fail after one month.
T-Mobile has sent me a replacement, so I performed the factory reset data wipe on the old one. My next step was to use Odin to re-flash the stock firmware. I was previously running stock KitKat, but had used CF-auto-root.
After selecting the factory reset option from settings, it rebooted into recovery. One of the options is Wipe Data/ Factory Reset, but I can't select it because the power button doesn't work.
Taking the battery out just brings it back to the same place.
There is also a message "dm-verity verification failed" at the bottom of the screen.
The device is not enumerating on USB at all so I can't use ADB, fastboot, or Odin.
How can I escape recovery to complete the data wipe and get into download mode?
So after stupidly trying to update twrp through twrp instead of fastboot, I can only access fastboot and the universal bootloader installed on the phone. If I don't do anything, the phone simply goes through universal bootloader and I see a small penguin before the screen goes back and I need to restart the phone again. However, in the bootloader I can select to go to fastboot which does work. I've tried flashing TWRP through fastboot (fastboot flash recovery twrp...) and it said success however after clicking 'reboot to recovery', the phone once again just boots to the bootloader and I'm back at square one.
Thank you so much if anyone can help!
FYI, you can update TWRP using TWRP. Nothing wrong with that, I do it all the time. It's faster and easier to do so.
You might have an incompatibility between bootstack and TWRP.
So, please provide us more info.
ROM:
Bootstack used:
TWRP version:
What were you trying to do besides updating TWRP?:
Funny thing... I'm having the exact same problem.
I instaled TWRP (3.1.1-0-9c3b7e99) using the AxonToolkit 1.2.1.
Everything went smooth with the toolkit. I could get into TWRP and did some back-ups (as recommended), then wipe Dalvik/ART Cache, System, data, cache, and finally, try to install LineageOS 15.1.
I used the files:
- ZTE_A7LOSv1_UniversalBootStack.zip
- A2017U_OreoModem.zip
- lineage-15.1-20180810-UNOFFICIAL-axon7.zip
UniversalBoot and Modem were installed correctly, but I got an error when trying to install Lineage. I can't remeber the error number but it said something like: "this ROM is for device ailsa_ii_axon7 but this device is ."
Since then... my phone is in eternal loop and can only get into Fastboot. Can't access TWRP.
Thanks in advance to anyone willing to help me.
Don't mind... I have it back.
After many reboots, It only seems that this is working different with the Universal O bootloader. On the main screen, I tap the volumen button, choose "Recovery", reboot, press the power button on the main screen, press it again, the Linux Pinguin appears, press power button again, and then TWRP is back.
After that, I got to wipe and do the normal ROM installation process.
LS997 (September 2016 security patch), got to the end of root and couldn't reboot into TWRP recovery. The device is recognized in ADB while in fastboot but when I'm at the secure startup it's unrecognized, like USB debugging is disabled.
https://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278
If you've hit secure startup the phone has likely booted into regular Android far enough to replace twrp with stock recovery. Reboot into fastboot and reflash twrp (you can use the newest twrp if you want). Once done flashing unplug from PC and pull the battery. Reinsert the battery then boot into twrp via the factory reset/volume button method: hold volume down, press power until the screen turns on then (still holding vol - ) tap power repeatedly until a prompt to factory reset appears. Approving it twice boots twrp if it's installed, otherwise stock recovery will do the reset.
Once in twrp go to wipe, then format data (type yes to confirm), then go to reboot, then recovery. Once twrp restarts flash your choice of magisk/supersu.
Once one of those two is installed it makes it so twrp won't be replaced.
Phoenix591 said:
If you've hit secure startup the phone has likely booted into regular Android far enough to replace twrp with stock recovery. Reboot into fastboot and reflash twrp (you can use the newest twrp if you want). Once done flashing unplug from PC and pull the battery. Reinsert the battery then boot into twrp via the factory reset/volume button method: hold volume down, press power until the screen turns on then (still holding vol - ) tap power repeatedly until a prompt to factory reset appears. Approving it twice boots twrp if it's installed, otherwise stock recovery will do the reset.
Once in twrp go to wipe, then format data (type yes to confirm), then go to reboot, then recovery. Once twrp restarts flash your choice of magisk/supersu.
Once one of those two is installed it makes it so twrp won't be replaced.
Click to expand...
Click to collapse
Did this, got to the set-up screen (languages, accessibility) and an error ¨com.android.phone has stopped¨ spammed the screen. I tap ¨stop app¨ and the pop-up comes back immediately.
I tried to fix it by factory resetting (in the settings, NOT using the volume down/power button menu OR TWRP) and now I´m stuck in TWRP. Every time I try to reboot to System, it boots to TWRP now.
strapdad said:
Did this, got to the set-up screen (languages, accessibility) and an error ¨com.android.phone has stopped¨ spammed the screen. I tap ¨stop app¨ and the pop-up comes back immediately.
I tried to fix it by factory resetting (in the settings, NOT using the volume down/power button menu OR TWRP) and now I´m stuck in TWRP. Every time I try to reboot to System, it boots to TWRP now.
Click to expand...
Click to collapse
Power down, then boot to twrp using the volume buttons. Use the wipe menu there to do the reset.
Phoenix591 said:
Power down, then boot to twrp using the volume buttons. Use the wipe menu there to do the reset.
Click to expand...
Click to collapse
Wiped it, still get the com.android.phone errors.
Unfortunate, makes doing anything impossible with so many error popups.
strapdad said:
Wiped it, still get the com.android.phone errors.
Unfortunate, makes doing anything impossible with so many error popups.
Click to expand...
Click to collapse
Reflash your variant's official KDZ using [PARTITION DL] with patched LGUP leaving [aboot], [abootbak], [recovery], [recoverybak] partitions unchecked.
- Once the flash finishes & phone reboots, do a battery pull so phone doesn't fully boot (wiping recovery & encrypting data)
- Insert battery again
- While pressing volume down button - reinsert usb cable so it boots into fastboot mode.
- Follow dirtysanta guide for your variant from running step3.bat onwoards (which flashes TWRP back into your otherwise stock phone).
LS997, no official KDZ. Use VS995, but dump everything with LGUP (bar userdata) before hand