Just installed the new nightly which I found out after the fact was to version 12.1 (Android 5.1) from version 12.0. This of course means installing a new version of gapps for this version. I found and downloaded the new gapps, then went to reboot into recovery (it had been working prior to this). This time when I hit the volume down button on reboot, it just continued to boot normally. I even tried booting with the up button: same result. I can't access the play store because the gapps has to be updated first. Is there another way to get into recovery mode to install gapps? or alternatively another way to install it without recovery mode?
Found part of the answer
OK, found out how to reboot recovery with ADB. For anybody else who wants to know:
Install ADB on your computer if you haven't already
Run command shell (cmd)
Go to the platform-tools directory under where you installed ADB
If you're using ADB over network, type: adb connect {ip address of tablet}
type : adb reboot recovery
And that should get you into recovery mode
Now I just gotta get the correct version of gapps, the first one I got isn't working.
Related
I have a UK-bought SGT10.1, which I rooted shortly after purchase and installed CWM Recovery using Odin. I've been running In Paris for a while, and was about to update to v5. Last time I downloaded pershoot's kernel from droidbasement, I saw an updated version of CWM Recovery here: http://droidbasement.com/db-blog/?p=2370.
Being a security-type, running the latest versions is always the best option to me - and seeing I know my way around the console I figured I'll install adb/fastboot and use that this time instead of Odin. So I downloaded the SDK, installed the Tab 10.1 drivers (I've reinstalled Windows since I rooted), and grabbed the fastboot .exe from the previous revision and placed it inside android-sdk\platform-tools next to adb.
Now I'm trying to follow the instructions to install the extracted .img - but having some issues getting into fastboot mode in order to execute the commands. Running adb devices results in expected output, as does adb reboot recovery. However running adb reboot bootloader causes the device to reboot all the way back through to the lockscreen. I see some advice stating that to manually enter fastboot you reboot the device holding power+vol down, then pressing down to switch to the second option that isn't download mode. However that to me is the option to manually enter CWM Recovery, so now I'm confused. Running fastbooot reboot-bootloader cause
I don't want to brick my device, so I figured I'd ask for some advice here for getting into fastboot mode, and ask whether I can just flash the .zip inside CWM Recovery or if that is a very risky move?
Thanks in advance
I received my LG G Watch today and immediately set out to unlock the boot loader and to root it. It went easy, used the tools from http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863. ADB drivers worked for both fastboot and sideload at this point.
Now I wanted to upgrade to the new 5.1.1 from 5.0.2 so I downloaded the update.zip file and tried to use sideload to install it, which got me a code 7. I looked up how to solve this issue and came across this post:
JaLex77 said:
I was getting Status 7 as well.
I flashed TWRP, did a full wipe of system, Data, Cache.
(Do not install Supersu) Reboot to Bootloader.
Fastboot Flash system, recovery, boot from LG G Watch Restore Tools.
Reboot to Recovery.
ADB Sideload option.
Adb sideload update.zip from PC.
Sucess!
Optional:
reboot bootloader
Fastboot flash TWRP
reboot
Click to expand...
Click to collapse
So yes, I wiped /system/ and now it no longer boots. I can't install custom recovery OR revert to stock because the ADB driver no longer works in the fastboot screen. Sideload still works but I can't do anything useful with that AFAIK.
I've tried the Google usb_driver and Universal ADB USB driver with no change. In Device Manager it's identified as "Android" with the yellow triangle and as "Android Bootloader Interface" when the default driver installs.
How can I solve this?
Restore to stock with unlocked bootloader u cant update of its rooted.
Register ADB Driver
Lodorenos said:
I received my LG G Watch today and immediately set out to unlock the boot loader and to root it. It went easy, used the tools from http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863. ADB drivers worked for both fastboot and sideload at this point.
Now I wanted to upgrade to the new 5.1.1 from 5.0.2 so I downloaded the update.zip file and tried to use sideload to install it, which got me a code 7. I looked up how to solve this issue and came across this post:
So yes, I wiped /system/ and now it no longer boots. I can't install custom recovery OR revert to stock because the ADB driver no longer works in the fastboot screen. Sideload still works but I can't do anything useful with that AFAIK.
I've tried the Google usb_driver and Universal ADB USB driver with no change. In Device Manager it's identified as "Android" with the yellow triangle and as "Android Bootloader Interface" when the default driver installs.
How can I solve this?
Click to expand...
Click to collapse
There shouldn't be a yellow Triangle when the driver installs. You have to assign the proper driver.
Update Driver>Browse My computer for Driver Software>Let me Pick from a list of Drivers on my computer>Android Composite ADB Interface>Next Complete
I had received this error because I had my phone rooted when I attempted to install the OTA via the /cache method.
What I sugest to you, to get this installed properly is to download the newest version of LG G Watch Tools and restore your watch to 5.0.2 and root it, push the update to /cache and make the /cache/recovery/command file but instead of rebooting normally like you would to trigger the update, instead run adb reboot-bootloader and restore your watch again to 5.0.2. The restore leaves /cache alone so this will work. Once 5.0.2 has been restored, use the fastboot options to boot into Recovery Mode, the update will start and install properly.
I do suggest doing a factory reset after running the update, as I was experiencing some performance issues after having done this until I had done a quick reset. Now it's running fantastically.
To solve any ADB problems, you should install the ClockworkMod ADB drivers, then open Device Manager, find G Watch in there and then right click, hit Update Driver, Let me find one, choose to choose a driver manually and then tell it that it is an ADB Interface, choose any of the ADB drivers that appear and then hit next. ADB should work for you after that.
ADB however does not seem to work inside recovery for 5.0.2 as I was unable to sideload mine due to it not showing in device manager at all while in recovery mode.
I just unlocked my bootloader, flashed twrp, installed CM 13 on a T-Mobile Moto E 2015 4G LTE. It was all fine and good, but then I tried to install the google apps from gApps. I had the file in my storage. Logged into the recovery and hit install. I selected the zip file and I keep getting an error, "cannot unmount /system it is in use" What can I do? People say to flash a new recovery. There are no adb drivers for this. My computer recognizes the phone but adb command line does not. Please help me
The /system mounting issue seems to affect some people using official TWRP. Try using squid2's custom TWRP instead.
You can flash a new recovery two ways:
Method 1: Download squid's TWRP and copy the .img file to your microSD card. Boot the phone normally and install Flashfire from the Play Store. Give it root, select flash recovery, browse to your microSD and select squid's TWRP, reboot into recovery.
Method 2: Download and install/unzip Minimal ADB and Fastboot, download squid's TWRP to your computer and place the .img in the Install/Unzip directory, boot your phone into the bootloader (Pwn+Vol Down), connect to computer, open a command prompt in the Install/Unzip directory, type in "fastboot devices" and see if your device is listed/connected, then type "fastboot flash recovery TWRP.img" (or whatever the filename is) to flash it. Once it gives you the OKAY, disconnect and reboot the phone into recovery.
Hi all,
I appear to have done something wrong when flashing my device with boombox and flashing twrp. I seem not to be able to access recovery so I can update my boombox rom. I have tried button combinations, I have tried fastboot boot twrp.img in bootloader which just reboots my system, I have tried booting directly from home screen using adb which registers an error and I have tried re-flashing but unfortunately I cannot access recovery.
Any way I can get into recovery without erasing my data?
Jonnibravo said:
Hi all,
I appear to have done something wrong when flashing my device with boombox and flashing twrp. I seem not to be able to access recovery so I can update my boombox rom. I have tried button combinations, I have tried fastboot boot twrp.img in bootloader which just reboots my system, I have tried booting directly from home screen using adb which registers an error and I have tried re-flashing but unfortunately I cannot access recovery.
Any way I can get into recovery without erasing my data?
Click to expand...
Click to collapse
If you're rooted, give the reboot recovery app you installed after bootloader unlock root privileges.
If not then use the exact same PC ADB commands to boot to TWRP like during bootloader unlock.
I'm confused why you mention flashing TWRP after Boombox. Surely you didn't do that. You already had TWRP.
I am rooted, Recovery reboot just reboots the phone, I have tried to get into twrp by reinstalling but again does the same things just reboots the system after the corruption warning screen. I've also tried to install from the bootloader with the fastboot boot twrp.img command but it simply says waiting for device.
Sorry turns out I was flashing the wrong file from another tutorial, I was flashing 3.1.1 instead of 3.2.1
Jonnibravo said:
Sorry turns out I was flashing the wrong file from another tutorial, I was flashing 3.1.1 instead of 3.2.1
Click to expand...
Click to collapse
Then you didn't follow my bootloader unlock and root guide. I never mention that other TWRP, much less link to it.
You're going to have to load into Download mode and use fastboot commands, but you say you couldn't get past flashing TWRP.
Uninstall the LG Mobile Driver if you have them, then reinstall.
1st, reboot into OS, then open up Device Manager and change view to Show hidden devices. You should see a new category named 'ADB Interface' and underneath that 'Fastboot Interface (Google USB ID)'.
If not, you will also see 'ADB Device' for Other Devices category:
right click that to update driver software ---> Browse my computer for driver software ---> Let me pick from a list... ---> Show all Devices ---> Have Disk ---> Browse ---> C:\Program Files (x86)\LG Electronics\LG Mobile Driver ---> 'lgandbus' ---> 'LGE ADB Mobile Interface'
Download adb/fastboot software, download Joan TWRP 3.2.1 img file and place it in adb/fastboot folder, then send your phone into Download mode:
Open up cmd and type the following after changing directory to Adb/fastboot folder: fastboot devices (see if your device is there), fastboot flash recovery TWRP.img or (whatever file is named).img, then fastboot boot TWRP.img or (whatever file is named).img
Device: Asus Zenfone 6 with LineageOS 16 and LineageOS recovery
long story short, fastboot doesn't seem to working on my device anymore. I tried using a different cable, different computer, different operating system etc. I'm able to get output when I do "sudo adb reboot bootloader" but not always and only intermittently even the charging happens always. But whenever I reboot into the bootloader and do "sudo fastboot devices", I don't get any output
I need to flash the stock ROM on this device to be able to sell it.
Is it possible to flash the stock ROM on it without using fastboot? I tried using the LineageOS recovery to install the stock ROM but I get the following error
failed to verify package compatibility (result 1): runtime info and framework compatibility matrix are incompatible: Vbmeta version 0.0 does not match framework matrix 1.0. Installation aborted.
bezelfree said:
Device: Asus Zenfone 6 with LineageOS 16 and LineageOS recovery
...
failed to verify package compatibility (result 1): runtime info and framework compatibility matrix are incompatible: Vbmeta version 0.0 does not match framework matrix 1.0. Installation aborted.
Click to expand...
Click to collapse
You can't use LOS recovery to flash the stock rom, it's only to update LineageOs itself. If TWRP, Clockwork mod recovery, pitch black recovery or any other custom recovery is available, you'll surely be able to flash the stock ROM.
And most of the time fastboot isn't working because the drivers aren't installed.
Make sure you download adb and fastboot from here : https://developer.android.com/studio/releases/platform-tools
You can check out this : https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/
@bezelfree
A device's Stock ROM can get flashed via ADB
Code:
adb devices
adb reboot sideload
adb sideload <FULL_PATH_TO_STOCK_ROM_ZIP_FILE_ON_PC>
adb reboot
Raiz said:
You can't use LOS recovery to flash the stock rom, it's only to update LineageOs itself. If TWRP, Clockwork mod recovery, pitch black recovery or any other custom recovery is available, you'll surely be able to flash the stock ROM.
And most of the time fastboot isn't working because the drivers aren't installed.
Make sure you download adb and fastboot from here : https://developer.android.com/studio/releases/platform-tools
You can check out this : https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/
Click to expand...
Click to collapse
Thanks for the reply.
Installing TWRP would also require fastboot I guess which I don't have right now. Can I flash TWRP without using fastboot?
I'm using adb and fastboot from the packages provided by my Linux distribution. They are also on the latest version.
Code:
$ adb --version
Android Debug Bridge version 1.0.41
Version 30.0.4
$ fastboot --version
fastboot version 30.0.4
I did, however, try doing this on Windows using the same link you mentioned and fastboot still didn't work. ADB works but not reliably.
bezelfree said:
Thanks for the reply.
Installing TWRP would also require fastboot I guess which I don't have right now. Can I flash TWRP without using fastboot?
I'm using adb and fastboot from the packages provided by my Linux distribution. They are also on the latest version.
I did, however, try doing this on Windows using the same link you mentioned and fastboot still didn't work. ADB works but not reliably.
Click to expand...
Click to collapse
Weird, you can install TWRP from the mobile app if your LOS is rooted. If it's not tho you're blocked. How did you install LOS in the first place ?
Raiz said:
Weird, you can install TWRP from the mobile app if your LOS is rooted. If it's not tho you're blocked. How did you install LOS in the first place ?
Click to expand...
Click to collapse
After an entire day of messing around, I finally got it.
First of all, I still can't get fastboot to work. I had the LineageOS recovery on my phone. I flashed the TWRP installer ZIP file from the LineageOS recovery and booted into TWRP. I installed the stock ROM from my SD Card in TWRP and rebooted. The device was stuck on the boot animation. Rebooted and did a factory reset and got the stock ROM back.
But yeah, fastboot still doesn't work for some reason. Don't know why. But hey, I got what I wanted.
Thanks for the help.
bezelfree said:
After an entire day of messing around, I finally got it.
....
Thanks for the help.
Click to expand...
Click to collapse
Nice to see it worked
And, I don't want to tell you what you have to do but make sure to tell the next owner about that fastboot problem. He won't be able to recover anything if the phone is bricked, so make sure he understood what he bought (at an interesting price I imagine)