I rooted my Yoga Book , and all was working great until this morn when I opened Magisk, and it said there was two updates available. One for Magisk Manager, which installed fine, and one to Magisk 18.1. That did not go fine! I did the direct install as recommended and when the tablet rebooted, I got multiple bootloader errors, and I cannot get back into the operating system. Right now it is in the Android recovery, the stock one. I cannot get back to TWRP. The only ADB commands I can send to it are from side load. When I try to side load the twrp image, I get an error on the tablet stating failed to open driver control, no such file or directory. If I could get into TWRP, I could restore the tablet from a backup. I have attached a photo of the errors I am getting. Any help would be appreciated!
Edit: I installed Intel Platform Flash Tool, and the stock Nougat ROM, but apparently it does not recognize the tablet.
https://ibb.co/58YbgpW
I think the root of my problem is the ADB/Fastboot drivers. In Control Panel, the tablet is showing as "Cherry Trail Tablet" with the drivers not installing. I installed the ADB drivers again, but cannot get them to see the tablet. I am pretty sure I had ADB debugging turned on in the tablet since I rooted this thing back in December.
I got it back up and running. It was as I suspected , the ADB drivers for it were not installed. One I got that I was able to go into TWRP and restore from my backup. Once I get it rooted again, I will make another. I would REALLY recommend that anybody that is rooting this tablet (or any other one), make a complete backup in TWRP, on an external SD card, NOT the internal storage. It just saved me!! lol
Bro what drivers did you use and from where???
Related
So I got this Tablet a few days ago and wanted to get root. It came with the 3.2 update already installed so I read around and saw I needed to downgrade the os, root, flash recovery, then flash a rom via recovery.
I plan to install this rom:
http://forum.xda-developers.com/showthread.php?t=1290318
It is basically stock acer 3.2 with root. Which is all I really want.
I followed method 2 here:
http://forum.xda-developers.com/showthread.php?t=1276227
After booting and installing the unstable version to be able to get root, then I did the adb push for cwm and itsmagic. Wasn't sure what to do after this so I rebooted. (I tried downloading the acer recovery installer but my market would not let me type anything in with all the force closes)
So after reboot I am unable to get adb to show it as a listed device and everytime I try to copy the rom over I need I get an error "Cannot copy *filename* The device has either stopped responding or has been disconnected"
In frustration I figured I didn't get cwm installed properly so I downloaded the apk from the web and installed it via dropbox. It let me apply it and actually boot into recovery.
I powered off and tried getting back in but my pc still fails to see the device listed in adb or save files to it via the basic windows file explorer.
I'm currently letting the update install itself (I flashed back the original recovery via acer recovery installer) don't know if this will fix it.
If anyone can help, it would be much appreciated.
Update:
It upgraded me to 3.1 but I still can't save anything to my tab (atleast the fc's are gone). It doesn't list anything on my tab just shows 0 files. Not sure how to get this fixed.
Update:
I did a factory reset. Now it detects it and I'm able to save the rom to it. I did the root, and flashed cwm thru acer recovery installer. (avoiding adb entirely). However when I'm in there now it says "E:Can’t mount /sdcard". Read some folks are throwing it on a usb drive and flashing it that way.(BTW I put the rom zip on the root file directory, not on the external SD). Will update if it works or not.
*RESOLVED*
Got it working. It installed off the USB thumb drive just fine. Was able to install the 3.2 root Rom mentioned earlier. Everything is working as it should. Able to read and write to and from the device now. Showing superuser in my apps. Now to start removing the crap Acer put on there
This is just in case anyone runs into the same problem. Took a few hrs but its working nice
Basically I suggest this if you wish to just install the the 3.2 stock rom via cwm
1.) Since the unstable flash doesn't clear your data, download and install everything you will need first. ex: Acer Recovery Installer, Iconia Root. Put the rom on the root drive and/or a thumb drive.
2) Flash the downgrade.
3) Run the Iconia Root tool.
4) Run the Acer recovery installer (since you'll have root now) and reboot to recovery
5) Flash the rom. If it doesn't detect it try it on a usb thumb drive. Done
I always put my ROMS on an external microSD. That is the only thing I use my SD card for, and as far as I can tell is always the recommended place to store your ROMS for updating. In the root of the microSD card.
Glad to hear you got it working though.
Guys i think i made a mess...
Earlier when i had installed a fresh copy of windows 7, my PC showed me nexus 4 MTP under Portable Devices from where i could transfer files and all...(i didnot had the android-SDK Kit with adb at that time)
I wanted to flash stock image back so for that i downloaded the WUG's Dev KIT 1.7.3 and so when it was checking for my ADB status i didnot return that allow PC to read adb on my Phone and so the TOOLKIT gave an error...so i went for the initial setup to install drivers in which the step states to uninstall every installed driver related to my NEXUS...i did so...after wards in step 2 it asked to to install the Google/universal ADB drivers which i did and i finally restarted my pc....
Now what issue i am having is that neither my ADB is connecting nor my device is showing under portable devices...!!!
Guys please help...i am unable to fix this because i want to make a clean my internal storage but not without making a backup of Picx, Music and Downloads and esp. the Titanium and TWRP BCKP files!!!
HELP HELP HELP!!! :crying::crying::crying::crying:
And now my Lappy is not even trying to install the Nexus 4 driver, earlier it used to show not installed
I have a Advent Tegra Note 7
Upgraded to kitkat and OTA 2.4.1
Used Tomsgt supertool 2.4.1 tool to root, installed TWRP (and made a backup image of my freshly installed system)
I've since added some games and apps and spent a fair bit of time customizing the system, but when I attempt to run Titanium Backup it tells freezes when "asking for root rights" so I ran "root checker basic" from playstore, which tells me I don't appear to have proper root access..
Here's a break down of what I've done, I've tried to keep it conscise...
I have tried installing a SuperSU, SuperUser and SU Update fixer, Also reinstalling the SuperSU-v1.94.zip using both cwm and twrp... Still no proper root access.
Ideally I'd like to try some other things to get root access before reflashing and having to reinstall my apps and settings, can anyone help or suggest anything else I could do.? I can't think of anything I could of accidentally done to break root access, this is still quite a clean system just setup in the past two days.
P.S.When using the supertool impacter tool and scan for usb driver I get a "no such device" error, even though the device is listed in the previous screens.. also I suspect the correct drivers are there as ADB seems to work fine
they flashing SuperSU-v1.99r4.zip from http://download.chainfire.eu/447/SuperSU/. I haven't had issues with root via either method.
If that fails you can use the n7root.img which is downloadable here: https://github.com/linux-shield/shield-root/blob/master/root_tn7.img?raw=true then go into fastboot mode and then type fastboot boot root_tn7.img. DO NOT USE FASTBOOT FLASH BOOT with this image as it will make it bootloop, just use fastboot boot command.
SOLVED
Thanks for the pointers hacktrix2006.. I tried supersu-v1.99r4.zip also v2 no luck. Had a quick look for how to get into fastboot mode.. couldn't access it from the bootloader.. so decided to take a backup image and restore to stock kitkat 4.4.2 via tomsgt latest tool 2.4.1 including doing Wipe data. then reinstalled TWRP then applied root.... AND noticed a screen saying something like ROOT ACCESS MAY BE FAULTY.. WOULD YOU LIKE TO FIX THIS.. I also think there was a warning about "be careful this action is irreversable" - I suspect the previous time I hadn't understood this properly and selected NO !! Anyway this time I said yes and now have ROOT YAY!
Now I start a re setup of the system and installation of apps etc.. I guess it's often a bit smoother 2nd (or 3rd 4th etc) time around
OK thx again for the encouragement, plus now I have a little more experience to offer someone else who may be struggling in this area.
no problem!
Alas with the upcoming Update, on Monday I find myself in a plexing place on how to reinstall SuperSU once more via a TRWP that just terminates on a Black Screen on my 4k TV.
I had thought to try patching though my Computer Monitor via a HDMI to DVI Connector. And, allthough it does work well enough once fully booted. There is not a chance in Hell of it liting up for TWRP, or even the Bootloader for that matter.
While TWRP may we'll be the best recovery I was wondering if anyone has ever bothered to port a different Recovery to the Shield (e.g. Philz, ClockworkMod etc..)
Just as an aside would any of these other Recoveries suffer from the same bug? It would be a PItA if I had to wait a week before I went to visit my Old Man just to go though the motion (and embarrassment), of having to flash SuperSU on his FHD TV again.
While this doesn't exactly answer your question, TWRP does have a CLI. Once installed and in TWRP recovery, and connected via ADB, I believe all you have to do is issue the TWRP command to see it's listing of features and other commands. I've flashed su and other .zips to my shield this way a few times.
Here's the relevant link and documentation.
https://test.twrp.me/doc/openrecoveryscript.html
So, example would be
adb shell
twrp install /sdcard/SuperSU.zip
Are those commands to be sent via ADB, or Fastboot, or something totally other again?
~crap... I spent way to much time trying to fix the Old Man's GPS (WinCE) Device. I can't read any more lol.
Ok I think I managed to get as far as ...
Code:
# twrp install /sdcard/SuperSU.zip
TWRP does not appear to be running. Waiting for TWRP to start . . .
I can only suspect that it's hanging on the Permissions change Switch that you have to swipe though before actually getting into TRWP.
It may or may not be helping that I'm also loading TWRP off of the /sdcard/ instead of bricking my recovery fully by installing it outright.
NOT that it would kill the Shield off or anything as drastic as this. But I doubt I'll ever see the recovery again. Lol to heck with 4k!
Ok so I went back and, actually installed TWRP as the Shield's Recovery. And now it's working. So if I have to reinstall SuperSU, as I suspect I'll will after tomorrow's Update to Nougat. Then I should hopefully be able to reinstall SuperSU though the ADB Shell (as above)...
Again thank you kindly a signed a 4k'er!
Hey. I long story short - I have wiped OS, and the only thing that I can do is use fastboot and also install TWRP or stock recovery.
I found OxygenOS file, but cant install it as there are problems sideloading the file to the device, it looks like ADB drivers on PC are not recognizable. Can someone help me to get back OS? Thanks
Tried a lot of things but anyway nothing happens.
BooBzi said:
Hey. I long story short - I have wiped OS, and the only thing that I can do is use fastboot and also install TWRP or stock recovery.
I found OxygenOS file, but cant install it as there are problems sideloading the file to the device, it looks like ADB drivers on PC are not recognizable. Can someone help me to get back OS? Thanks
Tried a lot of things but anyway nothing happens.
Click to expand...
Click to collapse
Push the OOS rom via usb to the phone, command: adb push namerom /scard
Next time check the drivers installation result first.
I wish I knew the reply above mine.
How I fixed my issue:
I installed the latest TWRP 3.1.1 in one of the installation guides on this forum for the OP5. Make sure you pick the version that is called the "last latest build". I was able to flash a full zip for 4.5.2 and it worked!
chaojimbo said:
I wish I knew the reply above mine.
How I fixed my issue:
I installed the latest TWRP 3.1.1 in one of the installation guides on this forum for the OP5. Make sure you pick the version that is called the "last latest build". I was able to flash a full zip for 4.5.2 and it worked!
Click to expand...
Click to collapse
I had problems with ADB drivers, anyway got back to life:
1) booted to TWRP
2) adb push ".zip" /sdcard/.
3) tried installing it at TWRP, no success, so get back stock recovery and flashed the file there.
So my issue is resolved. thanks!