Related
Hi Guys,
Long shot i know, but i am trying to boot into recovery to re-install my friends OS, the problem is:-
1) USB slot doesn't work for reading in (only charging) so can't use ADB
2) Volume keys don't work, so can't get in that way
The phone is also not rooted !
I have tried a few terminal emulators, but they all need root access (so it seems) in order to reboot into recovery, does anyone know anyway in which this can be done (or anyway in which i can root the bloody thing so i can then run the command from a terminal emulator) ? I've tried several old root apk's, but none of them work..
Cheers
danhughes1961 said:
Hi Guys,
Long shot i know, but i am trying to boot into recovery to re-install my friends OS, the problem is:-
1) USB slot doesn't work for reading in (only charging) so can't use ADB
2) Volume keys don't work, so can't get in that way
The phone is also not rooted !
I have tried a few terminal emulators, but they all need root access (so it seems) in order to reboot into recovery, does anyone know anyway in which this can be done (or anyway in which i can root the bloody thing so i can then run the command from a terminal emulator) ? I've tried several old root apk's, but none of them work..
Cheers
Click to expand...
Click to collapse
And forgot to say, the phone is gingerbread official firmaware
danhughes1961 said:
Hi Guys,
Long shot i know, but i am trying to boot into recovery to re-install my friends OS, the problem is:-
1) USB slot doesn't work for reading in (only charging) so can't use ADB
2) Volume keys don't work, so can't get in that way
The phone is also not rooted !
I have tried a few terminal emulators, but they all need root access (so it seems) in order to reboot into recovery, does anyone know anyway in which this can be done (or anyway in which i can root the bloody thing so i can then run the command from a terminal emulator) ? I've tried several old root apk's, but none of them work..
Cheers
Click to expand...
Click to collapse
Gingerbread for our device can only be rooted from Odin, by flashing kernel with embeded su file. For that you will need USB slot (obviously you can't flash anything in Odin without it). And USB jig only open Download mode, can't get you to recovery.
After years fo relying on the XDA community, I thought I'd give something back. I've been for a few days now trying to get the phone properly rooted, however being a bit cautious due to completely screwing up my last phone, was being very careful.
Obviously - This guide carries all the T&Cs you'd expect... will void your warranty, could brick your phone, could fry all electronic devices within a 50 meter radius and such... USE AT YOUR OWN RISK.
Also, credit goes to the people for their hard work in making this possible. I'm only responsible for writing this post.
I'm not sure if you could have gotten away with not doing any of the steps below, but it's this sequence that I followed.. so feel free to play about.
To start off, you need the following
Ingredients
HiSuite software. I used what came with the device. If you put it in HiSuite mode, you should get a folder mounted that contains this software.
USB developer mode needs to be enabled (follow HiSuite's guide as even IT needs debugging mode enabled).
ADB - I used the latest version of Minimal ADB and Fastboot
Download TWRP from here
P7 Easy Update and Adjust from here
King Root from here (I've tried the lot and is the only one I found that actually worked).
Super SU from here. Put it on your phone storage for later.
Preparation
Install ADB, HiSuite and King Root.
Connect the phone to the pc via the USB, turning on PC Suite (HiSuite) mode and USB Debugging enabled. HiSuite should automatically load.. close it
Run King Root and start the rooting process. This should cause your phone to reboot a few times. now, following the application - towards the end of the process it says something about installing a recovery, but (at least on mine) didn't seem to install correctly. Never mind though - phone will still boot as normal, and we'll take care of the recovery next
place the Easy update and adjust excecutable in the folder where you installed ADB and run it (make sure phone is in pc Suite mode with USB debugging again and close the HiSuite app if it pops up on your PC). Note that in the ADB folder you will find a new /recovery/ folder, as well as a stock recovery image. Place the TWRP recovery image we downloaded earlier in this folder as well.
From within the Easy update, select [3] - Delete set_immutable.list / Full root.
After that Select [2] - Flash Recovery (Stock or custom)
Select the TWRP recovery. This will reboot your phone and flash the recovery image, loading back up as normal.
Go back to the Easy update app and select to reboot into recovery. If you attempted this before the last step (7), you'd just see two boot cycles, back into the normal boot up.
flash the Super SU zip and reboot
the next time you boot up, you will get a notification that king user needs something... you need to disable (or uninstall via titanium backup).
And that's it! You have root!
Hi there, just out of curiosity, do you think this method will work for b135?
Cryonisis said:
Hi there, just out of curiosity, do you think this method will work for b135?
Click to expand...
Click to collapse
Everything bar the set_immutable part worked for me.. for that i followed the below:
http://forum.xda-developers.com/ascend-p7/general/rooted-p7-l10-609-t3003605
hope that helped
Wrong thread guys soz.
TWRP recovery version?
Hi,
Will I have to download TWRP version compatible with EMUI 3.1 (which is mine case) or I can use TWRP 2.8.1.0 link that is in your post?
Thank you in advance!
Credits go to: @ashyx, @mauam, @jedld, @Chainfire
Prerequisite:
Padded kernel for T280
http://forum.xda-developers.com/attachment.php?attachmentid=3881481&d=1474417563 (unpack with 7zip and put it to memory card)
SYSTEMMODE SuperSU (REQUIRED)
http://forum.xda-developers.com/attachment.php?attachmentid=3861602&d=1472738213 (put it to memory card)
All required drivers from Samsung Smart Switch
Odin 3.10
TWRP
https://www.androidfilehost.com/?fid=312968872162492913
Your unit should be fully charged
OEM unlock and USB Debugging enabled and allow your host computer
Steps:
1. Connect your tablet with your host computer
2. Open prompt and locate to your adb folder (platform-tools) and enter
Code:
adb reboot download
If it doesn't work, look at your tablet to see any prompt to allow your host computer
3. Open your Odin. Make sure auto reboot is not checked (but TWRP isn't overridden). Choose AP and locate your TWRP file. You may see secure check failed. Don't worry. Just press and hold power+volume down+home key together and wait for few seconds.
4. Enter TWRP by pressing power+volume up+home key together. You should see the boot screen. Keep pressing these buttons until the boot screen disappears. You should enter TWRP.
5. Locate your memory card. Flash systemmode SuperSU first, go back, and flash padded image as "boot".
6. (Optional) wipe cache and dalvik cache.
7. Reboot
8. It may take a while to boot up
9. You tablet rooted.
Hey, this works! Thank you for writing it up!
Success on a Samsung A6 SM-T280 (version 5.1.1 if memory serves).
Instructions weren't clear enough, got **** stuck in toaster...
Nah jk, it worked man!
EDIT: This is a lot harder than I thought it would be.... I lost root and did a reset and did it all again. This time after I got it rooted, I got rid of the SuperSU and downloaded the one from market. It updated binary easily.
sovereignjerk said:
Instructions weren't clear enough, got **** stuck in toaster...
Nah jk, it worked man!
EDIT: This is a lot harder than I thought it would be.... I lost root and did a reset and did it all again. This time after I got it rooted, I got rid of the SuperSU and downloaded the one from market. It updated binary easily.
Click to expand...
Click to collapse
I keep getting Custom Binary (Recovery) blocked from FRP lock. Did you get this as well?
mdsohal02 said:
I keep getting Custom Binary (Recovery) blocked from FRP lock. Did you get this as well?
Click to expand...
Click to collapse
Make sure you OEM unlock under the developer settings.
jedld said:
Make sure you OEM unlock under the developer settings.
Click to expand...
Click to collapse
Thank you Sorry, I haven't rooted an android device since the EVO 4G. Things have changed in the meantime.
---------- Post added at 02:48 AM ---------- Previous post was at 02:11 AM ----------
Does anyone know how to disable the OTA update notification once I am rooted ?
Does really count as a root? I thought needed bootloader...
sovereignjerk said:
Does really count as a root? I thought needed bootloader...
Click to expand...
Click to collapse
Yes, it's root.
The key is the recovery has SHA key embedded to bypass the bootloader.
mingkee said:
Yes, it's root.
The key is the recovery has SHA key embedded to bypass the bootloader.
Click to expand...
Click to collapse
Hi guys, has anyone tried APP2SD after rooting.?
After Step 3 it takes me to a warning screen with two options 1. Vol up to continue 2. Vol down to restart device.
So I go with option 1 but instead of taking me to TWRP it takes me back to download mode and at the top left corner this is what is shown.
ODIN MODE (In Red)
SECURE DOWNLOAD: ENABLE (In Blue)
MDM DOWNLOADBLOCK: O (In Red)
PRODUCT NAME: SM-T280
CURRENT BIN: CUSTOM
SYSTEM STATUS: CUSTOM
FRP LOCK: OFF
USB Init Start!
USB core reset done
I made sure to uncheck auto reboot but couldn't find anything about TWRP not being overridden so maybe that's the problem, what am I doing wrong?
Can someone do a video tutorial about this root?
Sorry for the dumbness, but i have never used this adb, this is only confusing part.
I laptop running windows 10, all drivers, files on sd card as you state.
Any further guidance i would appreciate.
Best wishes
Wingchundub said:
Sorry for the dumbness, but i have never used this adb, this is only confusing part.
I laptop running windows 10, all drivers, files on sd card as you state.
Any further guidance i would appreciate.
Best wishes
Click to expand...
Click to collapse
i advise you to search youtube on how to use adb. This is how i learned. Its too complicated to write it. But when you see video its easy. In simplest way adb is cmd opened in adb file. Than in cmd you write commands like adb flash, or adb format and stuff
Wingchundub said:
Sorry for the dumbness, but i have never used this adb, this is only confusing part.
I laptop running windows 10, all drivers, files on sd card as you state.
Any further guidance i would appreciate.
Best wishes
Click to expand...
Click to collapse
You don't need adb. Just boot to download mode normally.
ashyx said:
You don't need adb. Just boot to download mode normally.
Click to expand...
Click to collapse
Ashyx
Will link2sd/app2sd after root.?
ahmedyar91 said:
Ashyx
Will link2sd/app2sd after root.?
Click to expand...
Click to collapse
I don't see why not.
Will try and post
Finally rooted.
I came across this post and worked first time.
I installed supersu via trwp, then flashed img as boot in trwp also.
Worked perfectly
http://forum.xda-developers.com/gal...covery-samsung-galaxy-tab-a6-sm-t280-t3475381
ecstaseey said:
After Step 3 it takes me to a warning screen with two options 1. Vol up to continue 2. Vol down to restart device.
So I go with option 1 but instead of taking me to TWRP it takes me back to download mode and at the top left corner this is what is shown.
ODIN MODE (In Red)
SECURE DOWNLOAD: ENABLE (In Blue)
MDM DOWNLOADBLOCK: O (In Red)
PRODUCT NAME: SM-T280
CURRENT BIN: CUSTOM
SYSTEM STATUS: CUSTOM
FRP LOCK: OFF
USB Init Start!
USB core reset done
I made sure to uncheck auto reboot but couldn't find anything about TWRP not being overridden so maybe that's the problem, what am I doing wrong?
Click to expand...
Click to collapse
Here's a more detailed guide. It's based on this thread: http://www.droidviews.com/root-samsung-galaxy-tab-a-sm-t280-and-install-twrp/
raakaysh said:
Here's a more detailed guide. It's based on this thread: http://www.droidviews.com/root-samsung-galaxy-tab-a-sm-t280-and-install-twrp/
Click to expand...
Click to collapse
That is the old method and no longer relevant.
Just follow the steps in the OP below.
http://forum.xda-developers.com/showthread.php?t=3475381
I recently bought this device. I usually root/unlock bootloader on my devices. I haven't attempted anything on this watch yet, but I did try to enter recovery mode. I reset the device and waited for the screen to turn off. Once the screen turned on and showed the LG insignia, I swiped my finger from the top left corner down to the bottom right (as I read on another post). This took me to the bootloader. After that, I selected the recovery option. This caused the classic Android with it's chest open, red triangle, with an exclamation point. My current phone (OnePlus 3) has an unlocked bootloader and root. I doubt it's related, but could that be causing an issue since they're connected? Android Pay works on the watch even though it won't work on the rooted phone.
Is there not a stock recovery on this device, is it locked, or is this a result of the current state of my phone?
The red triangle means a fatal loading error and all processes have ceased. In other words it isn't letting you into the recovery, same if you hold the two buttons you can get to the bootloader but selecting recovery gives you the same result.
Even if you managed to get to the recovery, there is no known way to connect it to the PC, so you cannot unlock the bootloader.
matejdro said:
Even if you managed to get to the recovery, there is no known way to connect it to the PC, so you cannot unlock the bootloader.
Click to expand...
Click to collapse
No known way to connect it while in the bootloader menu? I've been using it with Android Studio to work on watch faces and an instrument tuner. I haven't tried connecting while in the bootloader menu though.
The command is:
adb connect (your watch ip address)
Thinking about it though, I think they both have to be on the same WiFi network. Maybe it's not possible.
This only works with ADB (when watch is fully turned on). It does not work with bootloader.
Works on download mode as well but couldnt get anything to do in there
Grumps said:
Works on download mode as well but couldnt get anything to do in there
Click to expand...
Click to collapse
Do tell more. You can actually connect to the watch when it is in download mode?
matejdro said:
Do tell more. You can actually connect to the watch when it is in download mode?
Click to expand...
Click to collapse
Yes had to setup my home wifi to be open. then reboot in download mode
But as i said once in download i dunno what we can try?
Gets IP adress which is the same ip it gets with adb and can connect with adb on that ip so it is possible to connect to wifi somehwo in that download mode.
Youtube Video : https://youtu.be/IVNmEXj-6Pk
Trying to get lg Flash tool to connect but need dll. it has network option so it should be possible
Can even ping the ip so we should be able to do something?
Wow that is awesome. I assume this could be used to flash custom recovery (and subsequently root the device), if somebody figures out how.
matejdro said:
Wow that is awesome. I assume this could be used to flash custom recovery (and subsequently root the device), if somebody figures out how.
Click to expand...
Click to collapse
Hopefully. Older Samsung phones are rooted via download mode so maybe it will be possible somehow
Well, I plan to try it as well, using your findings (thx!) with this.Wish me luck. Having flashing available is just one step. we don't have twrp or magisk yet
Hello, could you please repost your video? because I am trying to do the same, and I am failing. I set up guest wifi between my laptop and the watches. it is not protected by any password/wpa. watches are pingable, and I am able to adb to it. but after rebooting to bootloader, I am unable to connect. I would like to perform at least oem unlock, but I can't, as I am unable to connect to it.
Could you please provide more detailed howto?
BTW, that red exclamation mark while in Recovery: Press crown button and top button once at the same time. Recovery will open.
From there, we can sideload ZIP. Question is, what zip? I can only assume that it has to be genuine firmware (OTA) and that it has to be downloaded to internal memory prior of rebooting to recovery. So manual update is possible.
Problem I have right now is, that bootloader is locked, and in order to unlock it, we'll need fastboot connection. But the bootloader in the watch does not support so called 'SoftAP' feature. Seems like it will need an update from Google. But when this will happen I don't know. Possibly with Android 9 update? There must be a way, but LG says that they do not share technical specs, ATT gave me unlock code (I assume for SIM unlock, but my watches are already SIM unlocked). Any ideas? There has to be a way to connect to watch once in recovery, download or bootloader (all three modes are fully functional, just without wireless connectivity).
Question
Virnik0 said:
BTW, that red exclamation mark while in Recovery: Press crown button and top button once at the same time. Recovery will open.
.
Click to expand...
Click to collapse
I have a Ticwatch Pro and am trying to get past the exclamation/no command screen when going into recovery. I have tried literally every combination of button presses with the two side buttons and still cannot get any results. Google searches have turned up little in the way of solutions. So, to all the smart folks here on XDA, how can I get this damn watch into recovery!?!?
(background on why - didn't wear the watch for a few weeks, watch battery dies. When charged and rebooted, got a message that my watch was locked with find my device. From there, I have tried all my potential passwords to unlock but nothing worked. I am left to reset outside the OS now so help is GREATLY appreciated)
you need to press in "phone info" long press until you see adb enable bro
Greetings,
I recently got a Pixel 2 XL and the first thing I did was try to root with SuperSU and TWRP. I had some issues with it and someone suggested Magisk. It worked great and I was able to update from the 8.0 to 8.1 with root. I kept up with the latest Magisk installs until the past week or so.
My phones USB port appears to have failed partially. Luckily I can still charge, but there is no way to see the device storage from a PC. Support has defaulted, after much troubleshooting, to an RMA solution with a refurbished phone. Thankfully, this seems to be covered by warranty and isn't going to pose a cost issue. However, through the troubleshooting I was forced to do a factory reset. I looked up some information regarding factory reset with rooted devices. I cannot find the exact tutorial I followed or thread I gained the how-to information, I'm not sure which it was. I simply searched how to factory reset magisk 8.1 device. It was quick and most of the stuff I find now has the same information.
Open Magisk, uninstall. Open TWRP, uninstall. Device Settings, Factory Reset. Easy
This seemed to have worked. I didn't run into any locked hardware issues thankful because I don't have USB to really flash something to it.
Before I continued, prior to attempting the reset I fully backed up the device to my computer using ES File Explorers FTP transfer over the wifi. This was great, lots of photos were able to be saved with no hassle. I copied the entire root directory and have it backed up.
The problem with the reset is that while Magisk remained uninstalled, TWRP has a basic file installed that upgrades to the full app. I still have root, which would have been nice, except I still need to unroot and go back to factory settings before I can send this device in.
Before I make a mistake moving forward, I want to find the best way to unroot, (preferrably relock the boot also), and return to factory stock as it was the day I got it so I can return in it in the best state I can.
I am running rooted android 8.1.0 Pixel 2 XL with kernel 4.4.88 if the helps. When I reset to factory defaults TWRP remains installed and root persists. I cannot connect via USB and run android dev tools to flash anything directly. How can I restore this device? I should have all original kernels backed up. During the root process I remember them saying to copy the old ROMs first and I performed every step exactly. I do have access to move files to and from the device via WiFi. Is it this even possible?
PS, does anyone think the firmware and rooted install could be the problem with the USB? It seems entirely like failed hardware to me but the troubleshooting was extremely thorough and seems to indicate softare/firmware are likely to be the issue instead of the hardware issue that was determined. Could this still rooted device have corrupted the USB transfer? It seems I should do my best to rule this out as well, more so than just giving them a factory reset device. I'd rather keep my phone if it can be fixed easily, than obtain a possibly low quality heavily used refurbished model.
Regards
Did you try removing and reinstalling the drivers?
Sent from my MI 5 using Tapatalk
teddy0209 said:
Did you try removing and reinstalling the drivers?
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
I assume you mean for the PC. Yes, I have tried uninstalling and reinstalling both using Microsofts found drivers and directly sent packages from the support team. Updates and 2 different PCs. DevKit installed on the one I originally used to root and a new PC with fresh driver installs.
They wouldn't suggest drivers for the phone, if you know of a way to install new drivers for the phone, please let me know, I'd definitely give that a shot.
Regards
BlazzedTroll said:
I assume you mean for the PC. Yes, I have tried uninstalling and reinstalling both using Microsofts found drivers and directly sent packages from the support team. Updates and 2 different PCs. DevKit installed on the one I originally used to root and a new PC with fresh driver installs.
They wouldn't suggest drivers for the phone, if you know of a way to install new drivers for the phone, please let me know, I'd definitely give that a shot.
Regards
Click to expand...
Click to collapse
I should include all troubleshooting I mentioned for those that think they have a solution for the dead USB. My original request was for the OTA flash directions without USB, but I think a lot of people will want to suggest fixes for the phone as I suggested in the PS section.
Step 1: Check computer software.
Windows users, check to see if you have the latest version of Windows Media Player and have installed all recent system updates. Visit omitted for more information.
Mac users, make sure you install and are using Android File Transfer. Visit omitted for more information.
Step 2: Check for system updates.
On your device, go to "Settings" > Scroll down to "System" > Touch "About phone" (or tablet) > Touch "System updates".
If your device has a modified OS, troubleshooting may not resolve your device issue. Re-image your device back to Android factory settings using the instructions from the following link: omitted
Step 3: Restart your device in safe mode.
With the device on, hold the Power button to get the "Power off" prompt.
Touch and hold "Power off" until the "Reboot to safe mode" prompt appears.
Touch "OK" to reboot in safe mode.
Note: To exit safe mode later, simply restart the device normally.
Step 4: Unlock your device.
Before connecting the device to a computer, if your device is password protected, unlock your device. A locked device will not connect to the computer.
Step 5: Connect USB cable directly into computer.
If the USB cable is connected through a USB hub or extension, unplug the cable from the hub/extension and plug it directly to the computer.
A pop-up window should appear.
Mac users will have the Android File Transfer window appear.
Windows users may have a pop-up window appear. If not: On the computer, click the Windows Start button on the bottom left > click Computer > under Portable Devices, click on the device > click on the device's Internal Storage.
Step 6: Test if you can transfer files.
Try transferring a small file.
If file transfer works, success! No need to do the next steps.
If file transfer still isn't working (no pop-up windows to allow file transfer), proceed to Step 7.
Step 7: Change your USB computer connection settings.
Android 6+ Marshmallow only:
Plug in the device.
Slide down the notifications drawer from the top of the screen.
Touch the notification saying "USB for charging."
Touch the option for "File Transfers".
Test file transfer again (from Step 6). If the file transfer does not work, proceed to Step 8.
Older Android OS Versions:
Go to "Settings", under "Device," touch "Storage" > touch the "Menu" button (three vertical boxes at the top right) > touch "USB computer connection".
Only Media Transfer Protocol (MTP) should be checked. Uncheck MTP, check and then uncheck PTP, then re-check MTP.
Test file transfer again (from Step 6). If the file transfer does not work, proceed to Step 8.
Step 8: Windows Only: Install Google USB Driver.
Go to omitted and click the blue button on the right labeled "Download Google USB Driver."
After the download completes, right click the file ("latest_usb_driver_windows.zip") and select "Extract All."
Follow the USB Driver installation instructions available here: omitted
Test file transfer again. If file transfer still isn't working (no pop-up windows to allow file transfer), proceed to Step 9.
Step 9: Turn on "Developer options" and disable USB debugging.
Go to "Settings."
If using a phone, swipe down the screen with two fingers, then touch "Settings."
If using a tablet, swipe down the screen from the right side of the top of the screen, then touch "Settings."
Scroll down to "System" and touch "Developer options." If you don't see "Developer options," turn them on as follows:
Touch "About phone."
Scroll down to the "Build number."
Touch "Build number" 7 times to activate "Developer options."
Under "Debugging," verify that the box for "USB Debugging" is not checked. If it is checked, touch the checkmark to uncheck "USB Debugging."
Once USB Debugging has been deactivated, test file transfer again.
Step 10: Try different USB connections.
Try plugging the USB cable into a different USB port on the same computer.
Try connecting to the same computer but using a different/spare USB cable.
Try connecting your device to another computer.
Click to expand...
Click to collapse
My apologies on readability, I tried to include HTML formatting. I couldn't figure it out, the options support code highlighting but not the code itself.
Additionally, I tried different USB cables, safe mode, and the factory reset that I could perform.
@BlazzedTroll
Summary:
You've uninstalled Magisk, so you don't have root access when booted. TWRP still remains, so you have root access there.
If I read you correctly, what you need to do is to get rid of TWRP. Right?
Download the corresponding factory image, extract recovery.img and flash that by issuing the Install Image option in TWRP.
Just make sure you've done everything you need to before doing this, since you can't get back to a custom recovery if your USB really is busted. Other things to do could include flashing the system.img the same way to revert any possible /system modifications, etc.
Didgeridoohan said:
@BlazzedTroll
Summary:
You've uninstalled Magisk, so you don't have root access when booted. TWRP still remains, so you have root access there.
If I read you correctly, what you need to do is to get rid of TWRP. Right?
Download the corresponding factory image, extract recovery.img and flash that by issuing the Install Image option in TWRP.
Just make sure you've done everything you need to before doing this, since you can't get back to a custom recovery if your USB really is busted. Other things to do could include flashing the system.img the same way to revert any possible /system modifications, etc.
Click to expand...
Click to collapse
When you say corresponding factory image, does that mean I need the exact one that came on the device? Or just the latest factory image for the right device?
*EDIT* Never mind that, I found the backup folder in the Unified Toolkit which contains a compressed zip just like the ones on the site. I'll use that and transfer to my device over WiFi and use TWRP to flash it and come back with the results.
Thank you for your assistance
@Didgeridoohan
I have a backup locally saved that resembles those packages. I was unable to locate a recovery.img in either my saved file or the one on the site. My version that was backed up was 1.171019.011, which is 8.1. I know my phone came originally with 8.0 so I tried looking at one of the those for a recovery.img and still could not locate one.
In the zip there are several files
bootloader-taimen-tmz12a.img
flash-all.bat
flash-all.sh
flash-base.sh
another zip
radio-taimen-g8998-00164-17... .img
inside the second zip, many more .img files looked promising
abl.img
aes.img
android-info.txt
boot.img
cmnlib.img
cmnlib64.img
devcfg.img
dtbo.img
hyp.img
keymaster.img
laf.img
modem.img
pmic.img
rpm.img
system.img
system_other.img
tz.img
vbmeta.img
vendor.img
xbl.img
Same files in all 3 zips I checked.
TWRP only expects recovery.img for "BACKUP EXISTING RECOVERY"
TWRP also has "TWRP FLASH", which I did as one of my troubleshooting steps before and got the Google Pixel 2 XL (taimen) flash. These still keep the TWRP and root, which I believe is to be expected for that flash option.
DELETED
BlazzedTroll said:
I assume you mean for the PC. Yes, I have tried uninstalling and reinstalling both using Microsofts found drivers and directly sent packages from the support team. Updates and 2 different PCs. DevKit installed on the one I originally used to root and a new PC with fresh driver installs.
They wouldn't suggest drivers for the phone, if you know of a way to install new drivers for the phone, please let me know, I'd definitely give that a shot.
Regards
Click to expand...
Click to collapse
You're right, I mean for PC...
You can usually get twrp backups from same device with same rom and flash it on yours via twrp ( ask on your device forum)... You will need system.img, recovery.img, and boot.img... I'm not so sure if you can relock the device without working usb/fastboot...
Sent from my MI 5 using Tapatalk
@BlazzedTroll
My apologies... I'm still not used to these damned A/B devices. :laugh:
If I remember correctly, recovery is included in the boot image, so what you need to do is flash the stock boot.img file to slot A. Don't know if this is possible in TWRP.
teddy0209 said:
You're right, I mean for PC...
You can usually get twrp backups from same device with same rom and flash it on yours via twrp ( ask on your device forum)... You will need system.img, recovery.img, and boot.img... I'm not so sure if you can relock the device without working usb/fastboot...
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
I'll give this a shot, I have system.img and boot.img, as I said in reply to Didgeridoohan, I do not have a recovery.img in the files.
Sad news about relocking, but that should be OK.
Thanks for lending some help
Didgeridoohan said:
@BlazzedTroll
My apologies... I'm still not used to these damned A/B devices. :laugh:
If I remember correctly, recovery is included in the boot image, so what you need to do is flash the stock boot.img file to slot A. Don't know if this is possible in TWRP.
Click to expand...
Click to collapse
That's alright. I don't know much of anything about them. It's easy enough to follow tutorials and if I had my USB connection I could do as you say pretty quickly. The problem is I don't understand what TWRP even is. There doesn't seem to be an option to flash you own custom img. "TWRP FLASH" only lets you select from the latest versions and downloads the one you select and starts the flash. "BACKUP EXISTING RECOVERY" expects a recovery.img and doesn't let me select anything other than that. I could try renaming system.img to recovery.img, but until I find out what the difference between the images is, I'm not to keen on trying that one. Sounds like a good way to get hosed before I return it. At this time, I would think without having USB access the folks at Google would be happy to have root on the phone. Rather return it working, but rooted, than bricked.
So I was trying to follow some other suggestions and it seems like maybe the device is actually not rooted anymore.
There is no SU file located in system/bin or system/xbin.
When I download something like "Root Checker" it gets stuck verifying the root.
I tried to use apps like rashr and flashify to flash a stock recovery and neither app will load properly suggesting no root access.
This means when I ran the uninstalls, everything did uninstall and unroot but the TWRP install must not be very clean (I don't think it's being maintained anymore for most devices). So I need to try and find where this app is located and remove it manually before I run the recovery again. If I solve this I'll post back.
BlazzedTroll said:
So I was trying to follow some other suggestions and it seems like maybe the device is actually not rooted anymore.
There is no SU file located in system/bin or system/xbin.
When I download something like "Root Checker" it gets stuck verifying the root.
I tried to use apps like rashr and flashify to flash a stock recovery and neither app will load properly suggesting no root access.
This means when I ran the uninstalls, everything did uninstall and unroot but the TWRP install must not be very clean (I don't think it's being maintained anymore for most devices). So I need to try and find where this app is located and remove it manually before I run the recovery again. If I solve this I'll post back.
Click to expand...
Click to collapse
You don't have root access, since you uninstalled Magisk. TWRP has it's own root, so while booted to recovery you can still do root stuff...
The only way to restore the stock recovery is to flash the boot image to your device.
And TWRP is pretty much the only maintained custom recovery for most devices...
Just a small note: this demonstrates the issues with using toolkits... It's just to click away and you never really learn how things actually works. Can bite you in the bee-hind when things go south.
Didgeridoohan said:
You don't have root access, since you uninstalled Magisk. TWRP has it's own root, so while booted to recovery you can still do root stuff...
The only way to restore the stock recovery is to flash the boot image to your device.
And TWRP is pretty much the only maintained custom recovery for most devices...
Just a small note: this demonstrates the issues with using toolkits... It's just to click away and you never really learn how things actually works. Can bite you in the bee-hind when things go south.
Click to expand...
Click to collapse
At this point I've just ordered the RMA replacement and I'll send it in. Hopefully those at Google are able to verify that the hardware malfunction is entirely unrelated to the root and they still honor the warranty. If the USB hadn't failed, I would easily flash back to stock as you have suggested. It's a fairly trivial action.
I agree somewhat with the idea that toolkits can be problematic in this way. There was quite a bit involved in running through the toolkit, it wasn't that One-Click root/jailbreak type stuff. I issued all of the commands over ADB and was fairly knowledgeable about what actions I was performing. This issue lies in this toolkits maintenance. The latest update to TWRP removed a ton of features and I'm unable to find the other version. Magisk was fully uninstalled as expected. TWRP did not make it clear that the flashed recovery would in fact contain was is essentially an ad for their toolkit. The placeholder app, as they call it, is literally just an ad that pops up when your recover that says "Don't forget to install us!". You can't even remove that file from the recovery partition, you must reflash to remove it. So the problem isn't just that you don't learn how it works, it's that you aren't forced to go through the changes with a fine-toothed comb as you would creating your own recovery. Had I created my own recovery I would have left it stock so that in the event of a failure such as this you are returned to factory stock without any changes except the unlocked bootloader. I guess in the future I'll have to do this myself. I did take the easy way out and just run the defaults from the toolkit in most cases.
Thanks to you and the others who threw in some helpful suggestions.
For anyone stumbling across this in the future, the problem is a 'semi-rooted' recovery can't be flashed without USB transfer capabilities. The solution is to RMA the faulty hardware hopefully. They should be reflashing all phones they get after repair/refurbish anyway.
Best Regards
For future reference...
BlazzedTroll said:
Greetings,
I recently got a Pixel 2 XL and the first thing I did was try to root with SuperSU and TWRP. I had some issues with it and someone suggested Magisk. It worked great and I was able to update from the 8.0 to 8.1 with root. I kept up with the latest Magisk installs until the past week or so.
My phones USB port appears to have failed partially. Luckily I can still charge, but there is no way to see the device storage from a PC. Support has defaulted, after much troubleshooting, to an RMA solution with a refurbished phone. Thankfully, this seems to be covered by warranty and isn't going to pose a cost issue. However, through the troubleshooting I was forced to do a factory reset. I looked up some information regarding factory reset with rooted devices. I cannot find the exact tutorial I followed or thread I gained the how-to information, I'm not sure which it was. I simply searched how to factory reset magisk 8.1 device. It was quick and most of the stuff I find now has the same information.
Open Magisk, uninstall. Open TWRP, uninstall. Device Settings, Factory Reset. Easy
This seemed to have worked. I didn't run into any locked hardware issues thankful because I don't have USB to really flash something to it.
Before I continued, prior to attempting the reset I fully backed up the device to my computer using ES File Explorers FTP transfer over the wifi. This was great, lots of photos were able to be saved with no hassle. I copied the entire root directory and have it backed up.
The problem with the reset is that while Magisk remained uninstalled, TWRP has a basic file installed that upgrades to the full app. I still have root, which would have been nice, except I still need to unroot and go back to factory settings before I can send this device in.
Before I make a mistake moving forward, I want to find the best way to unroot, (preferrably relock the boot also), and return to factory stock as it was the day I got it so I can return in it in the best state I can.
I am running rooted android 8.1.0 Pixel 2 XL with kernel 4.4.88 if the helps. When I reset to factory defaults TWRP remains installed and root persists. I cannot connect via USB and run android dev tools to flash anything directly. How can I restore this device? I should have all original kernels backed up. During the root process I remember them saying to copy the old ROMs first and I performed every step exactly. I do have access to move files to and from the device via WiFi. Is it this even possible?
PS, does anyone think the firmware and rooted install could be the problem with the USB? It seems entirely like failed hardware to me but the troubleshooting was extremely thorough and seems to indicate softare/firmware are likely to be the issue instead of the hardware issue that was determined. Could this still rooted device have corrupted the USB transfer? It seems I should do my best to rule this out as well, more so than just giving them a factory reset device. I'd rather keep my phone if it can be fixed easily, than obtain a possibly low quality heavily used refurbished model.
Regards
Click to expand...
Click to collapse
Try downloading a stock Fastboot Image for your device then unzip it, collect boot.img, then flash just the stock boot.img from TWRP. Should solve the issue upon the following reboot with no more TWRP or root. If youre on magisk or systemless SuperSU. Not locking the bootloader though lol that's hopeless without usb function unless it's possible to lock bootloader using the terminal command with an WiFi ADB app from another device then follow with "adb reboot bootloader", "fastboot boot TWRP.img", then flash stock boot.img from there. I'm just spitballing the second one lol, but if it'll make it to the TWRP part successfully it should work in theory unless the WiFi ADB connection can't make it past reboot which I've never tried. Should probably get an unlock box like NCK Box Pro or whatever supports your device and you'll always know if the port is ****ed or not and flash back to full locked stock with the box if it isn't. It's what I do now. Handy little ****ers lol.