Related
I was in the process of replacing framework-res.apk and missed the step of changing the permissions before replacing it. I found several threads on how to unbrick the phone by flashing a new ROM but I was hoping I can somehow fix the permissions on the framework file and be done. I installed adb and I already had the LG USB drivers installed but when I run adb devices it doesn't list anything. Windows 7 shows "LG AndroidNet Phone" and a removable disk under "Safely Remove Hardware" so I think I have the right drivers.
Is there hope that I can fix the file permissions?
BTW, I'm a newb so I may be missing something. And also scared of having to flash a ROM
I need help.
do you have CWM in the phone ? if so boot into that and run adb devices and see if it finds it their
No, I don't. Other than using DooMLoRD zergrush to root the phone a few months ago, I have not messed with anything else.
gabcon73 said:
No, I don't. Other than using DooMLoRD zergrush to root the phone a few months ago, I have not messed with anything else.
Click to expand...
Click to collapse
unless your phone will boot normaly to the home screen or you have CWM on it you will haveto flash the koren rom theirs no way to get it into recovery that i know of ... have you tryed a factory reset ?
I replied to you at another thread, so I'll repeat here.
What you need to do is re-root while it's looping. It might take you 100 tries before it succeed , but eventually it should succeed.
After that you can try fix the permissions, but if the new .apk file is not copied successfully first time it might get you in boot loop again, so I'd recommend at that point push the .apk again and then change the permissions.
I found that zergrush dated 2011-10-21 has more chances to succeed, because it has more retries before it gives up, the new version tries only few times and gives up too quickly.
I've attached the root I was using with 3 versions of zergrush.
Open CMD window and execute root.bat, let it copy all needed files to the phone. If it fails, try execute loop.bat, it will just execute zergrush indefinitely , so you can go do other stuff. You can check if root succeeded by opening another CMD window and type: adb shell
then, if it shows sign "$" type su, if it shows "#" you are good to go.
P.S.
This method only works with AT$T stock rom, if you are on LU6200 you are probably out of luck, as their root requires wifi and user interaction...
Having CWM is very handy in such situations, not only because you can restore backups, but because you'll have root access.
Thanks [email protected], I'll give it a try. And yes, I have the stock ROM.
I'm having problems downloading root.zip, I've tried two computers and different browsers, it only downloads 554 bytes.
Yeah, for some reason it was downloading 404 page...
I reuploaded it.
I let the loop.bat run overnight without success so I decided to call AT&T and have it replaced under warranty. The new phone arrived today and I've been busy reinstalling and reconfiguring. I may install CWM just so I can easily recover from a backup in case I do some other stupid thing to the phone.
Thanks guys
Hello everyone!
I've been coming to this site for a few weeks now. What a ton of helpful information! I finally decided to create an account though, because I had a question I couldn't seem to get answered.
I'm fairly new to android, this a100 tablet is my first device I've "owned" but have worked with and have a little experience with other android devices. I'm pretty good with Linux, being an IT admin. I'm sure my issue is minute, I'm just stumped as to what is causing the problem.
I've upgraded my a100 to the latest ICS build. I've installed the drivers from acer (unfortunately after windows detected the device drivers first) and I am trying the quickroot method I found in the development forum. I can run the windows .bat file, and everything goes through CMD so quickly that I am not able to read whats happening, but it reboots my device and says root achieved. I've got super user installed, it won't find any updates for the SU in the settings menu, says failed every time it looks for them. I open terminal emulators, still getting $ instead of #. Tried a terminal command I read about for root, where I put the root and SU files at mnt/sdcard and use the command to install, no luck.
Am I truly rooted? I cant tell anymore. I just want to unlock the bootloader, install cwm, and flash an a500 custom rom to it.
Any help at all is greatly appreciated. I'm sure I'm overlooking something, but Im not sure. I can add a legacy device, add Acer's ADB driver, but the fastboot one gets a code 10 and cannot start.
Thanks!
pbrady5 said:
Hello everyone!
I've been coming to this site for a few weeks now. What a ton of helpful information! I finally decided to create an account though, because I had a question I couldn't seem to get answered.
I'm fairly new to android, this a100 tablet is my first device I've "owned" but have worked with and have a little experience with other android devices. I'm pretty good with Linux, being an IT admin. I'm sure my issue is minute, I'm just stumped as to what is causing the problem.
I've upgraded my a100 to the latest ICS build. I've installed the drivers from acer (unfortunately after windows detected the device drivers first) and I am trying the quickroot method I found in the development forum. I can run the windows .bat file, and everything goes through CMD so quickly that I am not able to read whats happening, but it reboots my device and says root achieved. I've got super user installed, it won't find any updates for the SU in the settings menu, says failed every time it looks for them. I open terminal emulators, still getting $ instead of #. Tried a terminal command I read about for root, where I put the root and SU files at mnt/sdcard and use the command to install, no luck.
Am I truly rooted? I cant tell anymore. I just want to unlock the bootloader, install cwm, and flash an a500 custom rom to it.
Any help at all is greatly appreciated. I'm sure I'm overlooking something, but Im not sure. I can add a legacy device, add Acer's ADB driver, but the fastboot one gets a code 10 and cannot start.
Thanks!
Click to expand...
Click to collapse
You do have Superuser and it's su binary, so yes, you should be rooted. Try this app if you want to be sure: https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en.
Besides the root checker that theonew pointed you too I have always found downloading and installing Titanium Backup from the market as a surefire way of determining if root was successful.
Upon first run it will ask for SU permissions and should present you with a dialog box asking if that is ok with you. I always answer yes and make sure that the "remember this selection" box is checked.
That will be the first sign that you are rooted. Then, The program should provide you with a summary where you will see a bunch of green check marks. Most notably Busy Box should have a green checkmark and it will probably state Installed from program or something to that effect.
Wahla, you have confirmed you are rooted.
BTW, I recommend this program for it's ability to backup your apps which makes flashing new rom's easier as the apps can then be restored after performing a data wipe which is usually a requirement of flashing new Roms. Just be sure you understand that sometimes restoring app's AND their associated DATA can mess with a new ROM. In that case you can simply install the APP only. which still saves you the time and bandwidth of re-downlaoding it from the market.
Good luck and welcome to the playground.
Finally, the OTA came out. But it's still not available in my area here (Malaysia) so I have to wait for it to come. But I'm a little short of patience here, and while the OTA zip files is out, I thought I could just sideload it via adb. But when I try to make it work, I spent 4 hours facing some adb problems. I'm using Linux most of the time, and I have Android SDK downloaded. It was so troublesome to make adb work. Initially adb just couldn't find my device. So I Googled about it, and did some modifications on the PC to solve the usb problem and finally adb could connect to my device (while in Android). Then I started to follow the instructions to sideload. I booted into TWRP recovery using adb command and just to be sure, I ran ./adb devices again while the device is in recovery. But then adb shows no device connected. Trouble. I thought it's the problem with some drivers so I used Windows to try it again. Same problem again. Then I started to Google about it and found some forums that mention that it only works when I manually boot into recovery (Volume Down+Power+Volume UP). I followed. And finally, it solved it. It was only the first problem. Then I pressed into adb sideload mode in TWRP and started sideload mode. And just to be sure again, ./adb devices, no device connected again. I thought it's some bug in TWRP, I stopped sideload mode, and went back to the main menu of TWRP (where adb once can detect the device) and ./adb devices again. Guess what, it shows no device again. Problematic. I restarted my pc for many times, switching from Windows and Ubuntu for many times, repeated the above steps for many times, but the problem is just so random. I even changed the usb cable but no luck. So I decided not to use adb anymore and I've Googled for just flashing ota in TWRP. But there's just very few articles on it. Most of them are using adb and stock recovery. Some of it mentioned that if custom recovery is present then it shouldn't have to be so complicated but none of them shows how to use custom recovery. And one of them says I could just flash the OTA zip file through custom recovery but no instructions for it. The last one is my ideal method now, but because of lack of references, I'm not sure about it.
In short:
-Nexus 7 with TWRP
-problems when using adb to communicate with my device whether it's in normal boot, TWRP recovery, sideload mode, or whatever
-problem is so random and I cant figure out whats the problem
-tried installing and uninstalling and installing drivers again and again
-I dont wanna lose my data
-fed up
Question:
Is the OTA zip file recovery flashable? I dont wanna mess with adb anymore. It just wont work properly with me. Or I have to wait for OTA to reach me?
Are you completely stock (besides the custom recovery)? In other words, have you made any changes to your system partition? (have you uninstalled any app? removed any system apk? installed XPosed framework? edited any file on the system partition?)
If your system partition is not completely stock, OTA may not work (depending on which file you modified).
If you are stock, yes, you can download the OTA zip file to your device (make sure you get the right one), and reboot into recovery, and just install it from recovery.
According to Androidpolice, 4.4.4 -> 5.0: razor LRX21P from KTU84P is available at http://android.clients.google.com/p....signed-razor-LRX21P-from-KTU84P.5a0f7a47.zip
If your device is the razor, and is currently on LRX21P, you can download this and flash it.
jj14 said:
Are you completely stock (besides the custom recovery)? In other words, have you made any changes to your system partition? (have you uninstalled any app? removed any system apk? installed XPosed framework? edited any file on the system partition?)
If your system partition is not completely stock, OTA may not work (depending on which file you modified).
If you are stock, yes, you can download the OTA zip file to your device (make sure you get the right one), and reboot into recovery, and just install it from recovery.
According to Androidpolice, 4.4.4 -> 5.0: razor LRX21P from KTU84P is available at http://android.clients.google.com/p....signed-razor-LRX21P-from-KTU84P.5a0f7a47.zip
If your device is the razor, and is currently on LRX21P, you can download this and flash it.
Click to expand...
Click to collapse
Thanks for answering. This helped me a lot. As I remember I did not modify the system except for xposed which I uninstalled beforehand. What's the worst that could happen if I flash the ota on a modified system?
ImjuzCY said:
Thanks for answering. This helped me a lot. As I remember I did not modify the system except for xposed which I uninstalled beforehand. What's the worst that could happen if I flash the ota on a modified system?
Click to expand...
Click to collapse
When you uninstalled XPosed, I hope you opened XPosed app and clicked the "Uninstall" button from there (instead of just uninstalling XPosed app itself). If not, you will need to reinstall XPosed, uninstall from within the app, and the uninstall the app.
(XPosed modifies a file on your system partition - if you use the uninstall from within the app, it will restore the original file. If you just uninstall the app, the modified file will be left on the system partition).
Worst case scenario - the OTA will fail. I don't think it will cause your existing OS to stop working.
jj14 said:
When you uninstalled XPosed, I hope you opened XPosed app and clicked the "Uninstall" button from there (instead of just uninstalling XPosed app itself). If not, you will need to reinstall XPosed, uninstall from within the app, and the uninstall the app.
(XPosed modifies a file on your system partition - if you use the uninstall from within the app, it will restore the original file. If you just uninstall the app, the modified file will be left on the system partition).
Worst case scenario - the OTA will fail. I don't think it will cause your existing OS to stop working.
Click to expand...
Click to collapse
Yeah i uninstalled it within the installer app and left the installer installed and hope it will work with lollipop in the future.
ImjuzCY said:
Yeah i uninstalled it within the installer app and left the installer installed and hope it will work with lollipop in the future.
Click to expand...
Click to collapse
cool! (it will almost certainly require a new XPosed app because of all the changes that Lollipop brought, but it won't hurt to leave it installed)
Edit: Just read http://forum.xda-developers.com/showpost.php?p=56748099&postcount=5 - looks like you will need to uninstall XPosed too
ImjuzCY said:
Yeah i uninstalled it within the installer app and left the installer installed and hope it will work with lollipop in the future.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56748099&postcount=5
Please help and please be kind and patient with this senior citizen.
I have a rooted Nexus 7(2013). It is rooted at 4.4.4.
I saw the released Android updates to lollipop that I want to use and I need help with the procedures as I have to deroot my Nexus 7 first?
I also want to break it down to steps.
I assume that to update to lollipop, I would need to:
Backup using Nandroid
Deroot my Nexus.
Go to the Android site, then update to the latest version of lollipop.
When the upgrade if over, then re-root.
Even, though I was able to root my Nexus 7, I have forgotten many of the specifics.
Please help guide me as I think I need to:
Backup my Nexus 7 – I have both Titanium Backup Pro and Nanroid Backup Pro
Should I use Nandoid Online backup to ensure I can recover?
Nandroid Settings - Please help me with these Nanroid settings aftger selecting Custom Backup.
Backup Name – UTZ Timezone
Type – TWRP or Clockworkmod – I assume I select TWRP
Normal Backup Mode?
Do I select any of Yaffs2 as Tar or Exclude Dalvik Cache, Exclude Google Music Files.I have to admit, I have no idea what Dalvik and Yaffs2 are.
I will move to TWRP backup to my PC because it winds up being about 3gb and I haisve a 16gb Nexus 7.
This is where I get very confused. What exactly do I do and use start the derooting? Should I use the WugFresh(1.99) toolkit?
After derooting, I should NOT restore anything. I do an upgrade of Android to lollipop.
After my Nexus 7 is lollipop, I would need to do a recovery/restore of my Nandroid backup??
I have the following products that might help:
Titanium Backup Pro
Nandroid Backup Pro
BusyBox Pro
SuperSu
Root Checker Basic
NoBloat Free
Thank you for your time, expertise, kindness and patience in advance
Jon
Need a little more information. Understand you are rooted, but do you have custom recovery installed?
You actually don't need to remove the root before you update to lollipop if you use a factory image from Google.
Nexus7 and lollipop
SwoRNLeaDejZ said:
Need a little more information. Understand you are rooted, but do you have custom recovery installed?
You actually don't need to remove the root before you update to lollipop if you use a factory image from Google.
Click to expand...
Click to collapse
This is where I get confused and think that I am overcomplicating things.
I don't know if I have a custom recovery installed? I assume that I would have had to have made one. :crying:
How can I check? In Nanroid?
Can I make a new one?
It is great if I don't have to remove the root to upgrade to lollipop. When I was promoted by Google to update to lollipop, it failed, because I was rooted.
The bottom line is that I want to upgrade to 5.x and want my Nexus 7 rooted. :good:
Please tell me what information you need.
Thank you,
Jon
jolo100 said:
This is where I get confused and think that I am overcomplicating things.
I don't know if I have a custom recovery installed? I assume that I would have had to have made one. :crying:
How can I check? In Nanroid?
Can I make a new one?
It is great if I don't have to remove the root to upgrade to lollipop. When I was promoted by Google to update to lollipop, it failed, because I was rooted.
The bottom line is that I want to upgrade to 5.x and want my Nexus 7 rooted. :good:
Please tell me what information you need.
Thank you,
Jon
Click to expand...
Click to collapse
Alright, so the fact that your Nexus received the prompt to update tells me that you do not have custom recovery installed.
What you are going to want to do (easiest way to update as far as I am concerned) is just flash a factory image from Google. In order to do this, you will need to get your hands on a few things first:
1.) Windows PC/Laptop
2.) Micro USB cable
3.) ADB and Fastboot files (http://forum.xda-developers.com/showthread.php?t=2588979)
4.) Factory Image from Google for Lollipop for the N7 (https://developers.google.com/android/nexus/images - If you have the 2013 N7, get the one that says 5.0.1 (LRX22C) under the heading "Factory Images "razor" for Nexus 7 [2013] (Wi-Fi)")
5.) ADB/Fastboot USB drivers (your Nexus should install them when plugged in while booted to the Bootloader)
Now, download the ADB and fastboot files. Go to that thread, and follow the instructions to install ADB and Fastboot SYSTEM WIDE so that ADB and Fastboot will work from any directory (makes the rest of this process VERY easy). Once you run through that installer, and everything is good, download the system image listed above. Once it is downloaded, go to the directory it was downloaded to, and UNZIP it (right click it and select Extract here, or open the file and select Extract All).
Now, power off your N7, and then power it on, holding VOLUME DOWN. You will be booted into the BOOTLOADER, this is known as FASTBOOT MODE. Now, connect USB cable to the Nexus 7. The computer will probably say "Installing Device Driver Software". Let it finish. Now, press the START button, and in the search box, type CMD. A command window will open up. Type in the following without the quotes: "fastboot devices".
Now it should show something like this:
Code:
List of attached devices
HJFK54HSWE fastboot
If it says nothing, then the drivers are not working. Reply back to this thread, and I will explain how to update the drivers (don't want to confuse you now). Now assuming that everything is working correctly, all you still have to do is flash the 5.0.1 factory image. Close the command window that is open, and go to the directory where you downloaded the factory image. There is a file inside that folder called "flash-all.bat". With the tablet connected and in fastboot mode, double click the flash-all file. That will do EVERYTHING necessary to flash the factory image, and your tablet will reboot in lollipop.
Now, I don't think this will overwrite the root. If it does, and when you reboot, SuperSU or Superuser (whichever you were using before) isn't in your app draw, then reply here, and we will root you up.
"Factory Images "razor" for Nexus 7 [2013]
Why the hell is it named 'razor' in DL area?? This machine is 'FLO', right???
Razor is the name for all 2013 Nexus 7s. From there, you have deb and flo to differentiate between the LTE and Wi-Fi models.
nhizzat said:
Razor is the name for all 2013 Nexus 7s. From there, you have deb and flo to differentiate between the LTE and Wi-Fi models.
Click to expand...
Click to collapse
Actually, Razor is Google's code name for the Flo, and the Deb is the RazorG. Just like the Nexus 9 is the Flounder on XDA and Volantis on the Google image site. There are almost always two code names for Nexus devices (the community code name, and then Google's, just to keep everything as confusing as humanly possible..)
^^ LOL, but how totally stupid. In their own factory images download area, there are SEPARATE download areas for WIFI/LTE... why in God's name don't they use DEB/FLO? -______-
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Jameswebb97 said:
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Click to expand...
Click to collapse
Use duces script to flash June google factory image.
jlokos said:
Use duces script to flash June google factory image.
Click to expand...
Click to collapse
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Make sure you are trying to open from the correct location, and put .\fastboot
EvilDobe said:
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Click to expand...
Click to collapse
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
simplepinoi177 said:
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Click to expand...
Click to collapse
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Jameswebb97 said:
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
Click to expand...
Click to collapse
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Jameswebb97 said:
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Click to expand...
Click to collapse
EvilDobe said:
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Click to expand...
Click to collapse
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
simplepinoi177 said:
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
Click to expand...
Click to collapse
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
Hey I'm so glad you got it working! Leave me a "Thanks!" would make it up to me ... I'm always happy to help out and get things figured out...yet I don't get the satisfaction of knowing if it does end up helping a lot of the time because a good number don't come back with their experience...so thanks for that! Glad you got it going...
EvilDobe said:
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Click to expand...
Click to collapse
And it's as @EvilDobe means.....
I remember back in the days of the Motorola Droids (OG Droid1, Droid 3, & Droid 4) where you could really mess things up and come out with a big ol' "brick" "paperweight" as there were many instances where you could not come back from (i.e. updating to a certain point, then attempting to downgrade when Google/Motorola/Verizon put blocks that breaks it). But this isn't the case these days. @Jameswebb97, at least with the Pixel 2's, Oreo and/or P(Android OS 9), it's actually more difficult than easy to get that too far gone. The only reason why I can help so many troubleshooting their issues is because I, myself, have wrecked my current device in some serious ways! So I can relate and have experience in helping in the same situations. I've gotten it to where it says "device is corrupt," (which isn't all that uncommon), BUT with the added desperate troubleshooting where I had to wipe/erase, changing partition types, format several partitions, even go about "resizing" the partition to match the "target extraction size" of the Full Factory flash, and even as far as learning to manually flash the various system partitions and that there are two (system_a & system_b) but, in Google's infinite wisdom(?), one flashes to system_a and the other to system_other!!! And I haven't even started on reading others' issues when going after the Slot A and Slot B complications -- I didn't even attempt to touch this in that troubleshooting story.
My point is: I think I've broken my device farther than most people and got it so close to the brink, and yet I was able to bring it back and am still using that same device today (most people would usually, at that point, go and get a RMA replacement). Honestly, as long as you have access to Bootloader Mode (which Google, in their infinite wisdom, seems to have placed it in the main board memory or separate memory rather than storage as to make it always accessible which makes it hard to "lose"), you have a really good (seemingly perfect) "safety net" in which you can always flash back to a working, stock state -- which is why it's the best policy to just make good backups before experimenting so, if anything, you get back to this state and restore all your data. I'm not trying to convince you to root or to try custom ROMs or anything -- even though there are many great reasons and capabilities of rooting -- I am simply appealingl to your sense of curiosity and reassure you so you aren't held back and you don't restrict and limit yourself if you don't want to, but are to fearful to experiment.
I hope you don't take this post as "lecturing" or anything, just some thoughts I hope you consider...
Glad it worked out in the end for you!