Fastboot? - Galaxy Note5 Q&A, Help & Troubleshooting

I've compiled AOSP and a kernel from the samsung open source zip, including the file mods, with out issue. I'm ready to flash that onto my phone, to start testing.
However, when I try to use adb to reboot into fastboot, the phone just reboots into normal user mode. I've enabled OEM unlock, under the dev options. I've also tried from multiple PC's. I've tried several combinations of up vol+down vol+ power, and have only managed to find safe mode, recovery mode, download mode, and soft reset.
Is there at trick, am I missing something entirely?
Follow up question, do I have to digitally sign my zImage and .img files? Can somebody point me to documentation on how to do this? When I tried to flash my zImage, it gets stuck at the Android boot screen. If I compare it to the rooted kernel in the dev section, the binwalk difference is just that there are several GPG Key databases behind the actual image for the rooted kernel, and mine is missing all references to a/the GPG database. What is that? I've tried various options in the kernel menuconfig, but I cannot figure this part out.
It's my first time, so please be gentle.

infurnus said:
I've compiled AOSP and a kernel from the samsung open source zip, including the file mods, with out issue. I'm ready to flash that onto my phone, to start testing.
However, when I try to use adb to reboot into fastboot, the phone just reboots into normal user mode. I've enabled OEM unlock, under the dev options. I've also tried from multiple PC's. I've tried several combinations of up vol+down vol+ power, and have only managed to find safe mode, recovery mode, download mode, and soft reset.
Is there at trick, am I missing something entirely?
Follow up question, do I have to digitally sign my zImage and .img files? Can somebody point me to documentation on how to do this? When I tried to flash my zImage, it gets stuck at the Android boot screen. If I compare it to the rooted kernel in the dev section, the binwalk difference is just that there are several GPG Key databases behind the actual image for the rooted kernel, and mine is missing all references to a/the GPG database. What is that? I've tried various options in the kernel menuconfig, but I cannot figure this part out.
It's my first time, so please be gentle.
Click to expand...
Click to collapse
the only way is to use the phone itself with a terminal emulater.
http://www.dorylabs.com/install-adb-and-fastboot-android-device-and-use-your-phone-tablet-like-pc/

Related

[Q] Fire HD with only TWRP installed

Hi all, I've been searching online and I haven't found anything that helps or even directly applies, so I broke down and decided to ask for help.
I was working off the guide to root my kindle, install TWRP and then a ROM, first time doing this.
SO let me break down where I'm at:
-rooted
-TWRP installed
-there's no .zip that I can find to stall from (checked sdcard folder and all others)
-can't load into original OS, logo goes from orange to blue on its own, and hangs there
-when plugged into PC, it is recognized but says no drivers are installed for it (no matter how many times i try reinstalling it.)
- I can get it into fastboot mode, but can't seem to load anything (I've read that fastboot doesn't work with twrp)
- adb sideload doesn't seem to work, it cannot find device
So how can I get a .zip file loaded to twrp, or restore the device, without adb seeing the device?
Is there a specific way to install the drives, or a way to get the .zip loaded through fastboot that I'm not aware of?
I'm sorry if this has been addressed before, I haven't seen this exact issue, and the fixes that seem close haven't worked :
thanks guys!
G_G_L said:
Hi all, I've been searching online and I haven't found anything that helps or even directly applies, so I broke down and decided to ask for help.
I was working off the guide to root my kindle, install TWRP and then a ROM, first time doing this.
SO let me break down where I'm at:
-rooted
-TWRP installed
-there's no .zip that I can find to stall from (checked sdcard folder and all others)
-can't load into original OS, logo goes from orange to blue on its own, and hangs there
-when plugged into PC, it is recognized but says no drivers are installed for it (no matter how many times i try reinstalling it.)
- I can get it into fastboot mode, but can't seem to load anything (I've read that fastboot doesn't work with twrp)
- adb sideload doesn't seem to work, it cannot find device
So how can I get a .zip file loaded to twrp, or restore the device, without adb seeing the device?
Is there a specific way to install the drives, or a way to get the .zip loaded through fastboot that I'm not aware of?
I'm sorry if this has been addressed before, I haven't seen this exact issue, and the fixes that seem close haven't worked :
thanks guys!
Click to expand...
Click to collapse
Without a working ADB connection, you can't get a file to your device in TWRP. You can restore your system, recovery, and boot images with fastboot, but your device must be in fastboot mode first. If you decide to do that, you'll have to restore your stock system, recovery and boot images, saved from the 2nd bootloader install instructions, then start the whole process all over again.
soupmagnet said:
Without a working ADB connection, you can't get a file to your device in TWRP. You can restore your system, recovery, and boot images with fastboot, but your device must be in fastboot mode first. If you decide to do that, you'll have to restore your stock system, recovery and boot images, saved from the 2nd bootloader install instructions, then start the whole process all over again.
Click to expand...
Click to collapse
Cheers! Excellent advise! I got it restored to stock!
I used the img files from here: http://forum.xda-developers.com/showthread.php?t=1951254
and followed the fastboot directions here: http://forum.xda-developers.com/showthread.php?t=2277105
now try it again! (and hopefully succeed!)

stock partition imgs

so i found a way to extract KDZ's to get at the goodies inside. and i figured hey why not zip up the imgs for anyone that needs a restore can fastboot flash them? then i realized. why not make a recovery flashable zip? forr now here is the stock d415 imgs if you want your variants uploaded PM me your imei code from dialing *#26# and your variant
instructions
extract partitions you need (ignore the numbers in most of the file names, its the offsets so the restorre knows where they go)
open the directory you extracted them to and hold shift and right click with no files selected. n the menu hit open comand window here.
time to flash:3 this is assumng fastboot is in your path
Code:
fastboot flash PARTITION_NAME FILE_NAME
link will be added shortly enjoy!
Do you have the links? I have a D415 also . Desperately need the original files. I have a soft brick. I can't flash the original KDZ. Every time the LG Mobile Tool reboots my phone into fastboot mode, it stops at 9% and says phone was disconnected. I tried for hours trying to get it to work, but nothing, also tried different computers and still nothing. I'm thinking it might be a driver problem.
I can get into TWRP and I can fastboot commands. I just need to flash the original D415 images.
akuma148 said:
Do you have the links? I have a D415 also . Desperately need the original files. I have a soft brick. I can't flash the original KDZ. Every time the LG Mobile Tool reboots my phone into fastboot mode, it stops at 9% and says phone was disconnected. I tried for hours trying to get it to work, but nothing, also tried different computers and still nothing. I'm thinking it might be a driver problem.
I can get into TWRP and I can fastboot commands. I just need to flash the original D415 images.
Click to expand...
Click to collapse
Check this thread
@krchi
shinobisoft said:
Check this thread
Click to expand...
Click to collapse
I didn't use those images, I was able to restore a half working stock system. Some things were definitely messed up: storage space showed only 4gb, the screen would register screen swipes as single button presses. I ended up calling T-mobile and got an RMA, since I got this phone 4 days ago.
Thank you for the help though, I'm sure many people will find them useful

Deleted the whole os

I recently formatted everything on my nexus 6 and I mean everything, the OS too. And I can't fix it, there was nothing on the forums or threads about this and how to fix it. Could you please help me?
Boot into the boatloader and flash the fastboot image.
Sent from my DROID Turbo 2
I have Ben an apple guy for 5 years just bought the nexus, I know how to get in to the boot loader but how do I flash the image? I tried downloading the image from the Google developers website but it said it failed ins
talling it!
Big-Blunt said:
I have Ben an apple guy for 5 years just bought the nexus, I know how to get in to the boot loader but how do I flash the image? I tried downloading the image from the Google developers website but it said it failed ins
talling it!
Click to expand...
Click to collapse
you cant use the flash-all, you need to flash each part separately. ynzip the file, then flash each .img file sepately. btw, ive deleted the whole os before. if you already have twrp installed, it wouls be a much easier fix using twrp instead.
How do I unzip the file in the boot loader?
Big-Blunt said:
How do I unzip the file in the boot loader?
Click to expand...
Click to collapse
i dont remember the program i used on my laptop, maybe 7zip.
The file downloaded from Google has a second zip inside. Unzip twice with 7 zip. The system image is inside the embedded zip file.
I assume you have the SDK from Google... Place all image files in the platform tools folder. I rename the images boot, radio, system, etc. to simplify typing the commands when actually flashing the images. DO NOT add the, " .IMG" when renaming.
Then:
Fastboot flash bootloader bootloader.IMG
Fastboot reboot-boitloader
Then same for system, radio, data and cache with out the reboot line.
When all files are flashed then fastboot reboot and enjoy
My brains are exploding rn, idk what or how to do anything, maybe u will think I'm dumb but I don't know what u guys are saying, could anyone post full instructions on how I would do it
The ONLY thing that you need to revive your device is alive bootloader. Every OS has its bootloader, and it determines what to load before system loaded.
I guess you did that foolish things on recovery. Then it won't kill itself of bootloader for sure.
Then there's always a chance. Try to boot into bootloader and switch it to fastboot mode.
Just flash stock rom image provided by google as described above.
You need to do some googling about fastboot and/or look for the beginners guide posted in the forums. You could use wugsfresh toolkit as well. I'm not being a douche not linking them,I'm to stoned
Google anything you don't understand
Sent from my Nexus 6 using Tapatalk
Do you know if your bootloader is unlocked?
You say you're an Apple guy - are you using a Mac? If you have access to a Windows machine I suggest you install Wugfresh's Nexus Root Toolkit and use the "Install & test drivers" button to set up the required drivers to connect your Nexus 6 to the computer. The walkthrough is comprehensive and extraordinarily simple - brilliant piece of programming. There is no Mac version.
Download the factory image (https://developers.google.com/android/nexus/images?hl=en#shamu image MMB29K).
Find the Fastboot/ADB programs on the web (I may have used the Minimal ADB & Fastboot tool, I can't remember exactly) and create a directory containing both programs plus their associated bits and pieces. I recommend making the path as simple as possible - e.g. C:\ADB for ease of navigation ( see below).
(While reading up on this, I came across this, which you may find useful - http://www.android.gs/install-set-up-adb-mac-os-x-linux/).
Unzip everything in the factory image, including the zip inside the zip as Larzzzz82 said, then copy the unzipped *.img files into the ADB Fastboot directory.
Boot your N6 into bootloader.
Open a CMD window and navigate to the ADB directory.
To check that you're connected, type (you don't need caps, this is just to make it clearer) FASTBOOT DEVICES. You should see something like "djdgkdjhgkdfj device" in response; if it's blank you're not connected - go through the driver setup again to see what you've missed.
Once you're successfully connected, you can install your new image following the instructions in this thread:
http://forum.xda-developers.com/google-nexus-5/help/stuck-launching-flashstock-bat-t3244470
I did ask for an expert to run a more experienced eye over them to correct any errors or to remove any pointless reboot commands, but nobody did either, so I guess they're ok. It's what I did and it worked for me. I've just noticed that it includes a line "fastboot flash recovery twrp.img" which you can ignore for the moment - though you may want to do this later when you have a working device.
Come back if you want any clarifications.
Happy new year (and, I hope, device...)
I tried I guess flashing the image through the recovery mode in the mount section but it said it failed,
Big-Blunt said:
I tried I guess flashing the image through the recovery mode in the mount section but it said it failed,
Click to expand...
Click to collapse
No no no you do not flash images through the recovery
Use Wugfresh's Nexus root and toolkit to restore it. Pretty easy.
@wolfen69 - duck and take cover...
I was going to suggest exactly that, since I'm a big fan of Wugfresh's NRT, but recommending it doesn't half bring down the flak... that's why I recommended using it initially at least to get the PC set up properly to connect and then get on with learning how to do it manually.
Personally in this situation using the NRT is exactly what I'd do myself. But now I'm retiring to my bunker for a while.
dahawthorne said:
@wolfen69 - duck and take cover...
I was going to suggest exactly that, since I'm a big fan of Wugfresh's NRT, but recommending it doesn't half bring down the flak... that's why I recommended using it initially at least to get the PC set up properly to connect and then get on with learning how to do it manually.
Personally in this situation using the NRT is exactly what I'd do myself. But now I'm retiring to my bunker for a while.
Click to expand...
Click to collapse
That's OK if people disagree with my recommendation. People are entitled to their opinions.
I tried for hours to do it the manual way and could never get it to work. And I'm a person who is VERY tech savvy. I had a computer repair business and have written advanced linux tutorials. I gave up and started using wugfresh. Has worked great for me. Others are free to do what works for them.
If you dont flash the images through the recovery mode then how do you flash it? I cant flash through command because the phone dosent have usb debugging enabled and its not in developer mode. I tried the nexus root toolkit as well and that didnt work either. Plz i need help!
So how much of my instruction did you follow? What exactly have you tried? Step by step. If you're vague then we can't help you. Error messages?
How did you delete the OS if your phone isn't unlocked?
Sent from my DROID Turbo 2
So i put it in recovery mode and when i tried resetting to factory i accidentally clicked advanced wipe and deleted everything so now its stuck in the boot loop. What i have tried was i downloaded the img file 6.0 shamu from googles site and drag and dropped on internal memory with my pc. Then in recovery mode i went mount and selected the img and it said error.

Factory Reset to Stock (8.0) from root 8.0 updated to 8.1 - No USB Connection

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.

Question How i got my CE 5G working after a soft brick. And the problems i came up against.

Before i start many thanks to Aman - thanks for being extremely patient and helping out no end.!!
So, first and foremost i followed the instructions in the rooting guide and for me it went wrong. I wasnt sure i was doing it correctly but like following a **** satnav i blindly carried on and soft bricked it.....not to worry im all good again - this was my 3 week journey. I thought it would be good to put down my experience as while ive rooted a lot of phones in my life at the same time i dont do them that often so i always find that im always... "learning again".
Followed the instructions on the other thread and downloaded the image, extracted it using the payload dumper - that itself was a pain in the arse as i couldnt get the linked one running - spent a good few afternoons, gave up and found one called "payload dumper 2021" which gave me a convenient exe to run and that worked fine (hurdle one over) - im trying to find the link to it so i can post it here but i cant...if i can ill update this thread...
I think this is where i started going wrong...i patched the boot.img from the downloaded os and flashed my phone. I got a black screen after booting (looking like it was dead) but if i held down the power button the reboot window showed up. Tried a wipe of cache etc etc but it didnt change.....not sure what i did after that as it was 3 weeks ago but ended up with a softbricked phone - all it would do on boot was crash dump. i had fastboot and recovery.
I tried the MSM tool on 3 different bits of hardware and none worked. Always hit the Firehose timeout error at 16seconds.
I also tried manually flashing the images but hit an error when i tried to reflash the product and system images....filesystem error.
Cue Enhanced Fastboot
Release v1.3.0 · libxzr/FastbootEnhance
New icon Add support for opening zips with payload.bin inside Add support for showing progress on taskbar
github.com
Put the phone into fastbootd and away you go. I actually had a couple of these phones to do so used the Oxygen updater to get the latest version of the os (i got 11.0.11.11EB13BA) - extracted that, patched it with magisk so it was ready to go.
Once i had reflashed the phone - using the enhanced fastboot Aman told me to delete the "cow" paritions first - this was where i was hitting the error manually flashing. Browse to the payload.bin file and it did the rest. Phone rebooted and it was alive again. Back into fastboot to install the patched boot,img (this was taken from 11.0.11.11EB13BA). Once rebooted i installed magisk by copying it over to the phone first and then a straight install.
Reboot the phone again, once booted with usb debugging on i then launched "adb shell" then type "su" - the request for root appeared on the phone and im done,
Not sure what the legalities of sharing the above OS image and the patched boot.img that goes with it are.
If anyone gets stuck ill try my best to help as others have helped me.
ComfySofa said:
Before i start many thanks to Aman - thanks for being extremely patient and helping out no end.!!
So, first and foremost i followed the instructions in the rooting guide and for me it went wrong. I wasnt sure i was doing it correctly but like following a **** satnav i blindly carried on and soft bricked it.....not to worry im all good again - this was my 3 week journey. I thought it would be good to put down my experience as while ive rooted a lot of phones in my life at the same time i dont do them that often so i always find that im always... "learning again".
Followed the instructions on the other thread and downloaded the image, extracted it using the payload dumper - that itself was a pain in the arse as i couldnt get the linked one running - spent a good few afternoons, gave up and found one called "payload dumper 2021" which gave me a convenient exe to run and that worked fine (hurdle one over) - im trying to find the link to it so i can post it here but i cant...if i can ill update this thread...
I think this is where i started going wrong...i patched the boot.img from the downloaded os and flashed my phone. I got a black screen after booting (looking like it was dead) but if i held down the power button the reboot window showed up. Tried a wipe of cache etc etc but it didnt change.....not sure what i did after that as it was 3 weeks ago but ended up with a softbricked phone - all it would do on boot was crash dump. i had fastboot and recovery.
I tried the MSM tool on 3 different bits of hardware and none worked. Always hit the Firehose timeout error at 16seconds.
I also tried manually flashing the images but hit an error when i tried to reflash the product and system images....filesystem error.
Cue Enhanced Fastboot
Release v1.3.0 · libxzr/FastbootEnhance
New icon Add support for opening zips with payload.bin inside Add support for showing progress on taskbar
github.com
Put the phone into fastbootd and away you go. I actually had a couple of these phones to do so used the Oxygen updater to get the latest version of the os (i got 11.0.11.11EB13BA) - extracted that, patched it with magisk so it was ready to go.
Once i had reflashed the phone - using the enhanced fastboot Aman told me to delete the "cow" paritions first - this was where i was hitting the error manually flashing. Browse to the payload.bin file and it did the rest. Phone rebooted and it was alive again. Back into fastboot to install the patched boot,img (this was taken from 11.0.11.11EB13BA). Once rebooted i installed magisk by copying it over to the phone first and then a straight install.
Reboot the phone again, once booted with usb debugging on i then launched "adb shell" then type "su" - the request for root appeared on the phone and im done,
Not sure what the legalities of sharing the above OS image and the patched boot.img that goes with it are.
If anyone gets stuck ill try my best to help as others have helped me.
Click to expand...
Click to collapse
Told ya, that the people in the telegram group could may help you out!
Happy to hear that everything is working again
Yep - many thanks - just trying to help spread the knowledge a bit.!
ComfySofa said:
Before i start many thanks to Aman - thanks for being extremely patient and helping out no end.!!
...
Click to expand...
Click to collapse
ComfySofa said:
..
If anyone gets stuck ill try my best to help as others have helped me.
Click to expand...
Click to collapse
Hi, seems like I have managed to brick my phone as well that was received this morning only and I proceeded to root it. Tried the MSM Tool, but that doesn't seem to be detecting the OnePlus Nord CE 5g, device manager showed my phone as QUSB_BULK_CID:... which wasn't correct so installed the QualComm USB Drivers from here after which the phone was detected as QDLoader9008..However, that doesn't seem to have helped as well as there was absolutely nothing happening in the MSM Tool
Am wondering what can be done to revive the phone?
sam_htc_touch said:
Hi, seems like I have managed to brick my phone as well that was received this morning only and I proceeded to root it. Tried the MSM Tool, but that doesn't seem to be detecting the OnePlus Nord CE 5g, device manager showed my phone as QUSB_BULK_CID:... which wasn't correct so installed the QualComm USB Drivers from here after which the phone was detected as QDLoader9008..However, that doesn't seem to have helped as well as there was absolutely nothing happening in the MSM Tool
Am wondering what can be done to revive the phone?
Click to expand...
Click to collapse
Well, lets try.....first and foremost you need a rom and you need the enhanced fastboot software.....ill see if i can find a link...
Try this version....
[TOOL][Windows] Fastboot Enhance [Payload Dumper & Image Flasher]
Fastboot Enhance What it can do? - Show fastboot vars - Switch between fastbootd & bootloader - Switch between A & B slot - Flash Payload.bin in fastbootd - Flash images - Erase partitions - Delete logical partitions - Create logical partitions...
forum.xda-developers.com
Then, get it into fastbootd mode....
Once youre in fastbootd mode - can be fiddly....get the latest plaform tools download and type in fastboot reboot fastboot while your in standard fastboot mode (with the green "start" at the top left)
youll know when your in fastbootd as it looks like recovery but says fastbootd in the middle of the screen....launch the fastboot enhanced and the click on the load payload.bin file from the extracted .zip file of the rom you downloaded - i got 11.0.11.11 using the oxygen downloader app but if youre phone is bricked im not sure than can be loaded up on another phone....
ComfySofa said:
Well, lets try.....first and foremost you need a rom and you need the enhanced fastboot software.....ill see if i can find a link...
Click to expand...
Click to collapse
Thanks for the super quick response
I had already tried the Fastboot Enhance v1.3.0, but that doesn't seem to detect my phone either. Wondering if I have lost ADB etc and hence the phone is not being detected anymore? And that is the first thing that needs to be fixed somehow?
Youre more than welcome....its needs to be in fastbootd mode for the enhanced fastboot to do its work....what have you got at the moment onscreen?
ComfySofa said:
Youre more than welcome....its needs to be in fastbootd mode for the enhanced fastboot to do its work....what have you got at the moment onscreen?
Click to expand...
Click to collapse
It's completely black, I was earlier able to get into Recovery Mode, but that's no longer happening as well - Did manage to somehow come into Safe Mode (shown at the bottom left corner) earlier but at the moment its completely black.
ok. if you hold the power and up volume down without the usb cable in to hard reset it then when it vibrates the once hold the down volume button down (hopefully that should get it into standard fastboot mode)
ComfySofa said:
ok. if you hold the power and up volume down without the usb cable in to hard reset it then when it vibrates the once hold the down volume button down (hopefully that should get it into standard fastboot mode)
Click to expand...
Click to collapse
somehow not able to get into fastboot mode anymore, it shows the standard warning about bootloader being unlocked and then proceeds to attempt to boot with red dot in between and smaller white circles revolving around it...this goes into an endless loop - the only way to come out of that is by long pressing the power button which brings up the option to either "power off" or "restart"
and the story repeats :-(
Well, if its any consolation yours is in better shape than mine was....youve still got a sort of working os.....! mine just went to crash dump mode....99% sure youve still got fastboot its just gonna be a bit of a faff getting into that mode....definately the way youre doing the key pressing/holding...

Categories

Resources