Related
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
simms22 said:
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
Click to expand...
Click to collapse
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
briman0094 said:
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
Click to expand...
Click to collapse
important thing to forget to mention
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
simms22 said:
important thing to forget to mention
Click to expand...
Click to collapse
I guess I assumed that when I said "continues to boot normally" people would assume I could re-enable "OEM Unlock" if needed
scryan said:
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
Click to expand...
Click to collapse
All the console output indicates success, and it boots to the initial "TEAMWIN" logo for a few seconds and reboots.
No Recovery Similiar issue
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
ray6279 said:
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
Click to expand...
Click to collapse
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it.
Click to expand...
Click to collapse
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
nhizzat said:
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
Click to expand...
Click to collapse
A screenshot of an e-mail from a Google employee regarding Android Pay and SafetyNet.
50% JOY No Fastboot?
simms22 said:
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
Click to expand...
Click to collapse
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
ray6279 said:
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
Click to expand...
Click to collapse
one question.. what is perm recovery?? the only recovery that works on the n6 is twrp recovery.
and when you are in her recovery, is it showing you the right location where the files should be? if nit, you csn change the lication.
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
ray6279 said:
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
Click to expand...
Click to collapse
your welcome, but you are still off in one bit of fact. you use fastboot, not adb, to flash a recovery(and system.img)
edit.. you can use apps like flashify to flash recovery, if you have root already.
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
ray6279 said:
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
Click to expand...
Click to collapse
ok, when wiping, dont do the first option wipe, itll wipe your whole phone clean. you need to select the advanced options and pick what you want wiped. fastboot is the way to unlock your bootloader, or flash a recovery. also, you use it to flash a system.img or any part of it.
adb is a general linux that can be used with android, anywhere but in the bootloader(only fastboot in the bootloader).
bootloader isnt the usb connection between the device and the pc, its part of the phone that boots it and decides if the rom is safe to run. thats why we unlock it. so we can flash roms eithout googles key.
fastboot is the tool that you use to do whatever needs to be fone in the bootloader, adb everywhere else.
a recovery you need if you want to flash custom roms, kernels, supersu, or other mods. you can also wipe different partitions with the recovery, or make a "nandroid' backup. thats a bavkup of everything. its like a complete snapshot of everything during the time you made it. if you ever mess up your phone, you can restore it, and you will be at the exact same place when you made the backup.
anything else?
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.
I’m also having an issue regarding my XZ1 Compact and Xperifix. I purchased Xperifix and I tried to use it with my XZ1 Compact (G8441, 47.1.A.12.179) yesterday. Unfortunately, it did not work.
Unlike the online video which demonstrates the process, when my phone boots during the process, the white Sony intro screen remains visible for a long time. Then I get a message saying: “It appears that TWRP is not booting. Please do it manually…” followed by instructions on how to do so. I follow these, eventually pressing volume down until TWRP appears, and then reconnecting the USB and pressing OK.
Although Xperifix indicates that it is continuing the process, TWRP remains on screen and nothing further happens. Eventually, I get the same “It appears that TWRP is not booting. Please do it manually…” message for a second time. Again, I follow there instructions. As before, Xperifix seems to indicate that it is performing normally. I then get a message telling me to check my phone to check that all has worked correctly. Unfortunately, it has not.
I have now completed this process perhaps six or seven times and the same thing happens every time. Can anybody please advise as to what I may be doing wrong or what I need to do in order for the software to run as intended?
Prior to running Xperifix, I unlocked my bootlaoder, resulting in green pictures from the camera. I was aware that this would happen, but I did so with a reasonable level of confidence that Xperifix would then resolve this issue for me. Obviously, it has not. So, even if there is no advice out there on how to get Xperifix to run successfully on my device, any advice on other methods of getting around this DRM issue would also be much appreciated.
Thank you in advance
Free25 said:
I’m also having an issue regarding my XZ1 Compact and Xperifix. I purchased Xperifix and I tried to use it with my XZ1 Compact (G8441, 47.1.A.12.179) yesterday. Unfortunately, it did not work.
Unlike the online video which demonstrates the process, when my phone boots during the process, the white Sony intro screen remains visible for a long time. Then I get a message saying: “It appears that TWRP is not booting. Please do it manually…” followed by instructions on how to do so. I follow these, eventually pressing volume down until TWRP appears, and then reconnecting the USB and pressing OK.
Although Xperifix indicates that it is continuing the process, TWRP remains on screen and nothing further happens. Eventually, I get the same “It appears that TWRP is not booting. Please do it manually…” message for a second time. Again, I follow there instructions. As before, Xperifix seems to indicate that it is performing normally. I then get a message telling me to check my phone to check that all has worked correctly. Unfortunately, it has not.
I have now completed this process perhaps six or seven times and the same thing happens every time. Can anybody please advise as to what I may be doing wrong or what I need to do in order for the software to run as intended?
Prior to running Xperifix, I unlocked my bootlaoder, resulting in green pictures from the camera. I was aware that this would happen, but I did so with a reasonable level of confidence that Xperifix would then resolve this issue for me. Obviously, it has not. So, even if there is no advice out there on how to get Xperifix to run successfully on my device, any advice on other methods of getting around this DRM issue would also be much appreciated.
Thank you in advance
Click to expand...
Click to collapse
Just a wild guess, as I have zero experience with Xperifix: make sure you are on the latest TWRP version (posted yesterday) to get data partition decryption to work for sure (independent on which security patch level you are on).
I advice you to use the official support you purchased with Xperifix.
4rz0 said:
I advice you to use the official support you purchased with Xperifix.
Click to expand...
Click to collapse
Good point I didn't realize it was paid-for software.
Free25 said:
what I need to do in order for the software to run as intended?
Click to expand...
Click to collapse
It sounds like you don't have the right drivers installed. You need Google USB drivers to be registered when you plug the phone in while running TWRP. This is tricky because by default Windows chooses the wrong drivers and you have to manually add/change them while TWRP is running. If you start the Xperia fix, manually start TWRP, set system as writable then plug it back in, you will see Xperiafix take control of the phone and reboot it. The fact it doesn't makes me think it's drivers.
Don't forget that Windows10 lies to you when it says it's installed the ADB drivers and you have to go into safe mode and 'disable signature checking' on the driver install
Xperiafix works, I used it, but getting the drivers right took me a couple of days..
You could read through the original app thread to find out a little bit more about how it works and there are even links to the drivers
you have to install at first the USB drivers for XZ1c.
if use use Windows 8+ you have to boot into the deactivated driver signature mode and install the driver.
On xperifix I can tell you, it downloads every time an old TWRP for XZ1C, which won't work with new firmware versions.
download the new TWRP version from our TWRP thread. then download portable minimal adb and fastboot, extract it on a place.
next step, start cmd.exe from start menu, enter the following command to switch in cmd into the path:
cd <path you have extracted minimal adb and fastboot >
enter the following command and don't execute it:
fastboot flash recovery <path were your downloaded TWRP is>
don't execute it!
reboot your phone into fastboot.
now start xperifix, click on fix device, and when you have a white Sony logo, plug out phone and reboot again into fastboot.
now switch to cmd.exe and execute the command.
press the key "up" to get the command again and replace the words "flash recovery" with "boot" and execute it again.
now your phone will boot into correct TWRP and let xperifix finish it's progress.
after restart, all should work.
you have at least to install the magisk manager and you will have working cam and magisk.
Thanks for all the advice thus far. I had already contacted the guys at Xperifix but am awaiting a response from them.
Within TWRP, the box marking the system read-only was already unchecked.
I had already visited https://developer.sony.com/develop/drivers/ and downloaded the ZX1 Compact drivers.
When in fastboot mode, my phone is recognised in device manager as Android Device – Sony ADB Interface. And, if I open a command prompt window from the Minimal ADB and Fastboot folder and enter “fastboot devices”, my phone is recognised.
Would this – the fact that my device is being recognised in fastboot mode - indicate that I have the correct drivers installed?
Sorry for all the newbie questions – I’d rooted a phone previously but it was years back, I’ve forgotten more than I remember, and I’m in a bit over my head. My own fault but, again, any further help in resolving this gratefully received. As you said Didgesteve, it works, I just need to figure out where I’m going wrong
if you test fastboot devices and you get a serial number, the driver is correct working.
test it with my method to replace TWRP after xperifix is started.
Raz0Rfail, just saw your post after my last response. Will take a look over that now. Thank you.
Free25 said:
I just need to figure out where I’m going wrong
Click to expand...
Click to collapse
Check out the link to the drivers I posted above, there's a how to video that's helpful
On the TWRP download list, I don’t see an option for the XZ1 Compact; only for the XZ or XZ premium. For both of these options, the most recent TWRP version listed is 3.2.1-0, and this is the version that Xperifix installed on my device. Would this indicate that Xperifix is giving me the most recent version?
Free25 said:
On the TWRP download list, I don’t see an option for the XZ1 Compact; only for the XZ or XZ premium. For both of these options, the most recent TWRP version listed is 3.2.1-0, and this is the version that Xperifix installed on my device. Would this indicate that Xperifix is giving me the most recent version?
Click to expand...
Click to collapse
Here you get the correct twrp for XZ1C:
https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
Didgesteve said:
Check out the link to the drivers I posted above, there's a how to video that's helpful
Click to expand...
Click to collapse
Thanks, I did have a look at that, but from what I'm seeing and reading (unless I'm missing something), it seems like this mightn't be a driver issue.
Free25 said:
Thanks, I did have a look at that, but from what I'm seeing and reading (unless I'm missing something), it seems like this mightn't be a driver issue.
Click to expand...
Click to collapse
The driver you use works.
What else is your problem?
I suspect that it’s TWRP, as you suggested. I downloaded ‘twrp-3.2.1-0-lilac-14’ and ‘twrp-3.2.1-0-lilac-14.img.asc’ (thank you for the link). I already had Minimal ADB and Fastboot installed.
I changed cmd directory to C:\Program Files (x86)\Minimal ADB and Fastboot, then entered ‘fastboot flash recovery C:\Users\25D\Downloads\TWRP\twrp-3.2.1-0-lilac-14’ (to where I had extracted the .img file)
I rebooted the phone into fastboot, activated Xperifix, waited for the white Sony screen, plugged out the phone, turned it off, plugged it back in in fastboot and executed the command. I erred somewhere however, as I received the response that the command is not recognised.
Probably a very elementary mistake on my part. Can you see where I went wrong?
the twrp filename has to be twrp-3.2.1-0-lilac-14.img with tab key you can do autocomplete
Tried it a few times now, got the
fastboot flash recovery C:\Users\25D\Downloads\TWRP\twrp-3.2.1-0-lilac-14.img
and
fastboot boot C:\Users\25D\Downloads\TWRP\twrp-3.2.1-0-lilac-14.img
to run successfully after rebooting in fastboot during the Xperifix process.
Still no joy though
The idea for correct path is, press shift + right mouse click on image file, then click copy path in contextmenu.
In cmd right mouse click and click on insert.
Thanks, I got the right path in the end and the flash recovery and boot seemed to run fine but it didn't seem to have any effect on the results from Xperifix
Free25 said:
Thanks, I got the right path in the end and the flash recovery and boot seemed to run fine but it didn't seem to have any effect on the results from Xperifix
Click to expand...
Click to collapse
Post the log files from C:\Xperiafix
This will show what's happening
Drivers is still my top guess
Hi guys, i need some help pleeease!
I was with the November security patch on my cell phone, I unlock the bootloader and went to use the friend tool (https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585) to activate the camera2api.
But it gave problem and the cell phone did not turn on, it was locked in the screen of android one.
So I downloaded the patched_boot.img from the version I was in and put it via fastboot. did not work.
Now, my phone is in this situation: I tried to use MiFlash (three versison: 2018528, 2017720 and 20151028) and they fail in the middle of the process, accusing "FAILED (command write failed (Unknown error))".
And: when I try to connect the cell phone normally, it shows the unlocked bootloader warning and goes straight to the fastboot, even without my request. This is strange. Perhaps because the system is damaged by the miflash unfinished
Obs: bootloader are unlocked and i can access twrp
If anyone can help me I will be very grateful and happy
What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...
AsItLies said:
What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...
Click to expand...
Click to collapse
Hi.
The tool (her topic link is up there) promised to activate camera2api without root my device (allowing OTAs in the future).
I believe she did a "temporary root" with a "temporary" boot.img just to activate the camera2api, and when it rebooted, it would return to normal boot.img without root. I do not know if I could explain it well.
The current issue is that it seems that the system is currently "destroyed or corrupted". Can not I reinstall the entire system through TWRP? Or something like this
Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work
AsItLies said:
Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work
Click to expand...
Click to collapse
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?
erickxd said:
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?
Click to expand...
Click to collapse
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.
AsItLies said:
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.
Click to expand...
Click to collapse
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:
erickxd said:
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:
Click to expand...
Click to collapse
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.
AsItLies said:
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.
Click to expand...
Click to collapse
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me
erickxd said:
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me
Click to expand...
Click to collapse
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers
AsItLies said:
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers
Click to expand...
Click to collapse
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?
erickxd said:
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?
Click to expand...
Click to collapse
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.
Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861
ckpv5 said:
Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861
Click to expand...
Click to collapse
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:
AsItLies said:
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.
Click to expand...
Click to collapse
I can access twrp when I flash ''fastboot boot twrp.img" in powershell, so until the next reboot I have access to twrp
erickxd said:
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:
Click to expand...
Click to collapse
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.
ckpv5 said:
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.
Click to expand...
Click to collapse
Hmm thanks for the answer!
Even when the operation fails after transfer a couple of archives before the system.img??? (on the Miflash)
If my phone was locked, Miflash could transfer these couple of archives before the operation fails?? Or if bootloader is locked, zero files can be passed by Miflash, and the error is apresented at the beginning of the operation?
Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.
prokaryotic cell said:
Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.
Click to expand...
Click to collapse
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?
erickxd said:
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?
Click to expand...
Click to collapse
Before someone can explain that, why don't you answer the question asked .. in fact at least 3 people was asking/telling ...
"Have you successfully unlocked critical partitions?"
Without the proper answer from you, not easy to help.
Hello there.
Just like title says - I've got my hands on new Redmi 9 (lancelot) nfc 4/64 version. I've unlocked it from Mi stuff successfully yesterday and wanted to install there twrp, magisk and titanium backup to clean a bit and maybe to have foundations for further change of rom.
However, my phone gaves answers, that I do not understand correctly.
Firstly - after first instalation of twrp via adb it booted into this. However, after choosing option to boot to system from it, power off via ui and then another try to enter recovery...it gave me stock miui recovery again. When I've tried the same steps for second time, phone finished, but after restart it entered bootloop. I've followed steps from this guide - https://miui.blog/redmi-9/download-install-twrp-and-root-redmi-9-codename-lancelot/
After some time I've managed to make low-level rom instalation again (12.0.4 official lancelot rom, dated 31st of Mar, 21) to at least being able to communicate with it (done with usage of miflash 2018 version and rom in *.tgz file). This time, I've used help from this page - https://www.getdroidtips.com/guide-flash-miui-rom-xiaomi-devices/ - had some troubles with mediatek based phones before in my life, so it wasn't from scratch, but some time to understand it were needed.
Phone is working again, but this rom is based on Android 10 (which I would like to keep, if it won't cause too much trouble). And I think because of that fastboot mode changed now into fastbootD mode, where old commands from adb does not recognize the device, thus no flashing recovery action etc can be taken.
Is there a workaround here? I've stumbled across some articles about installing clean Generic System Image with Android 10 on this phone (since it has been released with android greater, than number 8), but again - this requires to have custom recovery, prefeably twrp. I cannot do anything about it, because I got back to stock recovery (which now at least works, yesterday phone was so twisted at one point, that he cannot even load this recovery, but somehow managed to open system and fastboot modes normally (!!!)).
Is there a way to work it out? Older miui version, older android version, then twrp, then update via twrp? Or an alternative method, since google changed something in partitions again (not sure, if I get it right, but it might be it)? I would actually like to stay somewhere around miui (at least let it be official with ota support without too much issues), but without twrp I cannot do anything. I also do know, that there aren't any official twrp/pbrp yet (just betas). Could it also be the issue with troubles with installing it and staying it on the phone?
buczek0711 said:
Hello there.
Just like title says - I've got my hands on new Redmi 9 (lancelot) nfc 4/64 version. I've unlocked it from Mi stuff successfully yesterday and wanted to install there twrp, magisk and titanium backup to clean a bit and maybe to have foundations for further change of rom.
However, my phone gaves answers, that I do not understand correctly.
Firstly - after first instalation of twrp via adb it booted into this. However, after choosing option to boot to system from it, power off via ui and then another try to enter recovery...it gave me stock miui recovery again. When I've tried the same steps for second time, phone finished, but after restart it entered bootloop. I've followed steps from this guide - https://miui.blog/redmi-9/download-install-twrp-and-root-redmi-9-codename-lancelot/
After some time I've managed to make low-level rom instalation again (12.0.4 official lancelot rom, dated 31st of Mar, 21) to at least being able to communicate with it (done with usage of miflash 2018 version and rom in *.tgz file). This time, I've used help from this page - https://www.getdroidtips.com/guide-flash-miui-rom-xiaomi-devices/ - had some troubles with mediatek based phones before in my life, so it wasn't from scratch, but some time to understand it were needed.
Phone is working again, but this rom is based on Android 10 (which I would like to keep, if it won't cause too much trouble). And I think because of that fastboot mode changed now into fastbootD mode, where old commands from adb does not recognize the device, thus no flashing recovery action etc can be taken.
Is there a workaround here? I've stumbled across some articles about installing clean Generic System Image with Android 10 on this phone (since it has been released with android greater, than number 8), but again - this requires to have custom recovery, prefeably twrp. I cannot do anything about it, because I got back to stock recovery (which now at least works, yesterday phone was so twisted at one point, that he cannot even load this recovery, but somehow managed to open system and fastboot modes normally (!!!)).
Is there a way to work it out? Older miui version, older android version, then twrp, then update via twrp? Or an alternative method, since google changed something in partitions again (not sure, if I get it right, but it might be it)? I would actually like to stay somewhere around miui (at least let it be official with ota support without too much issues), but without twrp I cannot do anything. I also do know, that there aren't any official twrp/pbrp yet (just betas). Could it also be the issue with troubles with installing it and staying it on the phone?
Click to expand...
Click to collapse
After to flash TWRP you have to flash the vbmeta.img and then boot to TWRP not through commands but manually with hardware buttons, don't allow device to boot to system before to boot to custom recovery otherwise this will be overwritten again.
I've done that with this vbmeta, one and only difference might be that I was trying to get into twrp by commands (however, it did not work XD). Overwritten isn't an issue in my opinion, since I do have booted to recovery after installing it yesterday and then from it choose option "reboot to system". After poweroff from system and then trying to get into recovery, then stock showed.
I'm currently trying this - https://c.mi.com/oc/thread-3312019-1-0.html
After putting this command to cmd - bcdedit /set testsigning on lancelot shows somewhere, but I cannot install it (most likely due to this issue about encrypted drivers). I'll try to overcome it now.
Yea, well, I've tried this method from link listed above, phone still enters fastbootd mode, still is not-visible from cmd started from google platform tools folder (which a subfolder to working adb). Not sure what to do now.
buczek0711 said:
I've done that with this vbmeta, one and only difference might be that I was trying to get into twrp by commands (however, it did not work XD). Overwritten isn't an issue in my opinion, since I do have booted to recovery after installing it yesterday and then from it choose option "reboot to system". After poweroff from system and then trying to get into recovery, then stock showed.
I'm currently trying this - https://c.mi.com/oc/thread-3312019-1-0.html
After putting this command to cmd - bcdedit /set testsigning on lancelot shows somewhere, but I cannot install it (most likely due to this issue about encrypted drivers). I'll try to overcome it now.
Click to expand...
Click to collapse
No, this is not the method to boot to recovery from what I pointed out, you don't have to firstly power off device but from fastboot commands you can type either fastboot or fastbootd reboot and inmediately press the volume up till the TWRP logo appears, the fastboot/d command will act same as it be the power button.
The thread explains how to install unsigned drivers in Windows, not to set it on your Redmi but is for your PC. If you succesfully get the drivers installed then you have to reboot your PC entering again in safe mode (not normal mode) and from there the commands through fastbootd are generally the same than those for fastboot.
buczek0711 said:
Yea, well, I've tried this method from link listed above, phone still enters fastbootd mode, still is not-visible from cmd started from google platform tools folder (which a subfolder to working adb). Not sure what to do now.
Click to expand...
Click to collapse
Just to be sure you are doing fine and not missing something the adb commands work while device is on and fastboot/d commands work only in fastboot mode.
Can you attach some SS to see what you are typing and the error that brings the cmd?
Hm, you say, that I can type fastbootd into cmd and this will be recognised? It seems that it cannot be recognised in this case, when I'm trying to type fastbootd powershell says "unknown command".
Typing fastboot /d devices results in "waiting for device", despite phone being in fastbootd all the time.
I'll attach ss tomorrow - it is time to sleep for me now, gotta wake up early. Then we will also know something else, when it comes to behavior after restart pc (once again, I've done it all in one sit, it might be an issue here).
PS. if you want english errors, I'll have to use powershell - cmd is in my native language (polish). Found out, that it doesn't really matter, which program you use, powershell simply can do more, while cmd dates back 30 years or so.
Anyway - phone is still booting to miui 12 and android 10 normally, I do not set there google acc or lock yet, so don't know if there's any issue with it (most likely no).
I've also stumbled across some dude from indonesia, who had the same phone, miui 12.0.1 with android 10 and he installed successfully twrp, then magisk, but he also put some small img - misc misc.img. Could it be the issue?
I'm giving link to this material on YT -
FROM WHAT I SEE IN THE THUMBNAIL, this version of twrp is even the same (code number and english translated from chinese), that once worked here (md5 of the file might be different, though).
There's also an option to reinstall again whole adb, platform tools, drivers from official miunlock app etc, but since I do not had ANY android-related problems on this pc with previous phones, I'm not sure if this is worth our time.
And I think that if I would misspell something in cmd program would give me error instantly, instead of behaving like it was nothing - i've made tons of errors before and cmd/powershell always informed me about it in first line of their texts.
buczek0711 said:
Hm, you say, that I can type fastbootd into cmd and this will be recognised? It seems that it cannot be recognised in this case, when I'm trying to type fastbootd powershell says "unknown command".
Typing fastboot /d devices results in "waiting for device", despite phone being in fastbootd all the time.
Click to expand...
Click to collapse
Yes, fastboot works normally while in cmd, this is intended for that, no problem to enter firstly toi Power Shell but you can switch to cmd from PS just typing cmd and all the commands from here will be for cmd, doesn´t matter at all how many old is, cmd can work inside PS keeping the same aspect.
buczek0711 said:
I'll attach ss tomorrow - it is time to sleep for me now, gotta wake up early. Then we will also know something else, when it comes to behavior after restart pc (once again, I've done it all in one sit, it might be an issue here).
PS. if you want english errors, I'll have to use powershell - cmd is in my native language (polish). Found out, that it doesn't really matter, which program you use, powershell simply can do more, while cmd dates back 30 years or so.
Anyway - phone is still booting to miui 12 and android 10 normally, I do not set there google acc or lock yet, so don't know if there's any issue with it (most likely no).
I've also stumbled across some dude from indonesia, who had the same phone, miui 12.0.1 with android 10 and he installed successfully twrp, then magisk, but he also put some small img - misc misc.img. Could it be the issue?
I'm giving link to this material on YT -
FROM WHAT I SEE IN THE THUMBNAIL, this version of twrp is even the same (code number and english translated from chinese), that once worked here (md5 of the file might be different, though).
There's also an option to reinstall again whole adb, platform tools, drivers from official miunlock app etc, but since I do not had ANY android-related problems on this pc with previous phones, I'm not sure if this is worth our time.
And I think that if I would misspell something in cmd program would give me error instantly, instead of behaving like it was nothing - i've made tons of errors before and cmd/powershell always informed me about it in first line of their texts.
Click to expand...
Click to collapse
You don't need to reinstall nothing, just from the downloaded SDK platform do all that you want to avoid misspelling path and folder directories, I mean place the files you need to use in the same directory and open terminal prompt (PS) in the same folder where adb/fastboot binaries are, pressing right mouse button and shift at same time.
I feel you are missing something simply here, not so hard to do.
The misc.img partition that you mentioned is just to restore something that went wrong in the process.
But if you are happy with this Miui ROM then great. No hurry to answer that, give your time to rest.
I also feel, that there is something simply to overcome, Only the fastbootd is new Stuff to me. However, any time I was doing something with Snap, i was long after finish by the current time (almost a month with It and 3rd day with fastbootd issue).
I don't get it. Now when I've tried to enter fastboot mode...phone entered it (fastboot, not fastbootD). Then I've installed pitch black recovery and sucessfully booted into it by restarting phone and then pressing vol up. Now I'm trying with magisk and another entry to pbrp.
Second try gave me stock recovery again. What is wrong with it XD?
something is wrong. Installing twrp resulting in nothing (stock recovery is still there), installing pitch black resulting in successfully boot into new recovery. However, this recovery does not see any zip (magisk zip, to be exact, that I've put there before it to root phone). After boot into system and then power it off to boot into recovery...phone boots into stock recovery. Should I downgrade system to miui 11 to be able to get over it? Or should I wait until miui 12.5 enters redmi 9?
My tries of installing it has been done by using cmd with admin rights, if it does make any difference.
buczek0711 said:
something is wrong. Installing twrp resulting in nothing (stock recovery is still there), installing pitch black resulting in successfully boot into new recovery. However, this recovery does not see any zip (magisk zip, to be exact, that I've put there before it to root phone). After boot into system and then power it off to boot into recovery...phone boots into stock recovery. Should I downgrade system to miui 11 to be able to get over it? Or should I wait until miui 12.5 enters redmi 9?
My tries of installing it has been done by using cmd with admin rights, if it does make any difference.
Click to expand...
Click to collapse
I think you are not following the right direction, if you want consider what I pointed out; you don't have to power off device prior to boot to recovery for first time but you have to type from fastboot (no matter fastbootd) and inmediately from there boot to the custom recovery, when you succesfully booted to custom recovery then flash the recovery zip if there is one (PBR and OFR have one) and if not a zip then flash the image again to the recovery partition, also check if there is some installer apart from the image that can fix it in the ramdisk partition, at this point your issue is solved, next step is to reboot device to system normally, if you don't have any issue on that then OK but if you can´t there some steps more that you should do, but let this for last.
Ok, let's group it.
I do not think that particular matter of how do I restart phone matters here (at least, I do not believe it, that it does anything).
Option to restart to recovery from adb still not working.
Trying to find magisk.zip in main directory of internal storage still fails under pitch black recovery project.
From new stuff - I now got an error message, while opening pbrp, most likely with the issues about system being read-only (not sure though, since I do not remember it now, might look into it once more). I have the options to mount partitions, available from main menu, but since I do not used it at all before, I do not know, how to deal with it.
Also - my system boots normally, it must have overwritten recovery (or at least header of it) sometime during boot, since custom recovery is unavailable to access after first full reboot.
I'll try now to install newer version of twrp from yt that I've posted days back. I would also try with orange fox (however, i cannot find img for it, just source code, don't get it).
Is there someone, who can and will to help me?
Situation looks this - on this 12.0.4 MIUI with android 10 I'm unable to install ANY recovery (either phone do not restart to recovery after proper command from cmd or it boots into it, but after visiting system and then to recovery again it shows stock (even without any operations or updates from ota).
I cannot force to work either twrp 3.4.2b, twrp 3.5.2, pitch black recovery 3.0.0 beta.
After trying to install magisk 21.4 zip from twrp 3.4.2b phone entered bootloop, because f**k you, user, I cannot even get it to fastboot mode now (btw, fastboot now works, fastbootD is luckily a long-gone crap).
All cmd's have been run with admin rights. There are NO SUCH THING, as misspelling (cmd and adb would not execute command ,if it is misspelled, either command or filename). I've installed drivers once again and used cmd from dedicated folder with adb fastboot portable version (runned as admin, of course).
Now I'm downloading older version of rom for fastboot (miui 11.0.9) with android 10. Something has to finally work on this piece of junk.
Writting each time is success (cmd says "OKAY" nad displays time, it took to do so), downloading recovery image to start from it also works, there aren't any errors in cmd, yet phone still isn't working.
Where's the issue with it? Apart from being mediatek, which seems to somehow enormously hardened any flashing? I did not encounter anything like this with qualcomm, yet mediatek still manages to pisses me off with their really weird implementations and working (???) of their stuff.
another update from battlefield. Managed to finally get mediatek verify bypass in smart phone flashing tool, however it ended with forcing me to format anything in the phone (if not, program would not let me install anything).
Second problem is forcing me to disable verify, yet command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img put in fastboot mode (yes, it works now) does not work, because adb says, that "--disable-verity" is not a recognised command.
SPFT cannot properly download images from phone and welcomes me with error about download exception, happening either in recovery part or in boot part. SInce I do have access to fastboot now, I can overcome it (I think).
Old miflash tool to install roms via fastboot says it cannot flash rom in locked stage (I might have lost unlocked status, but I'm not sure about it). Do you know ways to overcome it?
It is me again (inb4 use edit). Had to unlock phone again by using miphone unlocker (it went ok). Still cannot flash using SPFT, miflash started showing idiotic errors like "no file in directory" or "cannot access to directory" (it could before, I did not changed name of it). Will continue reporting of progress (or the so-called "progress").