Hey guys, I'm in trouble. Need urgent help.
I was trying to install OOS & xXx rom from a clean install. But after flashing OOS & TWRP, probably I boot into wrong Slot. So now I'm stuck with Fastboot mode, cannot even go to Recovery. Can anyone help me out here so that I don't have to format the phone & re-unlock again?
TIA
nipun1110 said:
Hey guys, I'm in trouble. Need urgent help.
I was trying to install OOS & xXx rom from a clean install. But after flashing OOS & TWRP, probably I boot into wrong Slot. So now I'm stuck with Fastboot mode, cannot even go to Recovery. Can anyone help me out here so that I don't have to format the phone & re-unlock again?
TIA
Click to expand...
Click to collapse
If wrong slot is the only thing you messed up,
hook the phone in fastboot mode to PC and use the adb command (assuming you have appropriate drivers/adb already installed on your pc):
fastboot --set-active=_a
Change the slot from a to b if slot a does not get you to recovery. This command simply make either slot a or b active so you can boot into the correct slot.
Make sure you copy the command exactly as it's posted
Good luck!
Gr8man001 said:
If wrong slot is the only thing you messed up,
hook the phone in fastboot mode to PC and use the adb command (assuming you have appropriate drivers/adb already installed on your pc):
fastboot --set-active=_a
Change the slot from a to b if slot a does not get you to recovery. This command simply make either slot a or b active so you can boot into the correct slot.
Make sure you copy the command exactly as it's posted
Good luck!
Click to expand...
Click to collapse
Hello, thanks a lot for your prompt response. But it is showing this error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nipun1110 said:
Hello, thanks a lot for your prompt response. But it is showing this error.
Click to expand...
Click to collapse
How current are your fastboot (and adb) executables? From the command line, try entering:
Code:
adb version
I'm getting Android Debug Bridge version 1.0.40. If you're seeing something older than that, try a more recent version of adb and fastboot.
maigre said:
How current are your fastboot (and adb) executables? From the command line, try entering:
Code:
adb version
I'm getting Android Debug Bridge version 1.0.40. If you're seeing something older than that, try a more recent version of adb and fastboot.
Click to expand...
Click to collapse
Finally I got the solution. Thanks man. that command prompt u sent me was a little incorrect. There will be no "_" before "a". Thanks a lot for your help. Highly grateful.
nipun1110 said:
Finally I got the solution. Thanks man. that command prompt u sent me was a little incorrect. There will be no "_" before "a". Thanks a lot for your help. Highly grateful.
Click to expand...
Click to collapse
That wasn't me. It was Gr8man001 that gave you the advice that worked.
nipun1110 said:
Finally I got the solution. Thanks man. that command prompt u sent me was a little incorrect. There will be no "_" before "a". Thanks a lot for your help. Highly grateful.
Click to expand...
Click to collapse
maigre said:
That wasn't me. It was Gr8man001 that gave you the advice that worked.
Click to expand...
Click to collapse
true command : '''' fastboot --set-active=a '''' is it?
For me not work... please help.
https://i.hizliresim.com/pbOkpJ.png
Same thing here. In addition, I am unable to find a newer version of adb. Mine is 1.0.32.
I bricked my phone trying to update twrp. It will reboot to fastboot but not to system. A reboot to system has a dark screen and a small blue light in the notch. I'm thinking (and hoping) that changing the active slot will get it going again. I updated to Experience when the phone was new and want to go Pie, so the original should be in the other slot.
Any help will be appreciated.
zulu657 said:
Same thing here. In addition, I am unable to find a newer version of adb. Mine is 1.0.32.
I bricked my phone trying to update twrp. It will reboot to fastboot but not to system. A reboot to system has a dark screen and a small blue light in the notch. I'm thinking (and hoping) that changing the active slot will get it going again. I updated to Experience when the phone was new and want to go Pie, so the original should be in the other slot.
Any help will be appreciated.
Click to expand...
Click to collapse
Try the msm recovery tool, just Google how to unbrick OnePlus 6, it'll wipe your phone and install OOS 5.x.x but it will help you for sure
szybki_ben said:
Try the msm recovery tool, just Google how to unbrick OnePlus 6, it'll wipe your phone and install OOS 5.x.x but it will help you for sure
Click to expand...
Click to collapse
I looked at that one first, but would much rather swap the partitions and see if that will save it before trying the full wipe. Also looked at the Qualcomm drivers and can't seem to get that to work either. I am more used to working on a chromebook and going back to Windoze has been a challenge.
zulu657 said:
I looked at that one first, but would much rather swap the partitions and see if that will save it before trying the full wipe. Also looked at the Qualcomm drivers and can't seem to get that to work either. I am more used to working on a chromebook and going back to Windoze has been a challenge.
Click to expand...
Click to collapse
I don't think that you have to install Qualcomm drivers, I didn't install them and it still worked
szybki_ben said:
I don't think that you have to install Qualcomm drivers, I didn't install them and it still worked
Click to expand...
Click to collapse
The drivers were for another unbrick solution, I believe. I've looked at so many it's now hard to keep them separate. My original quest was to make another slot active. Another member tried the fastboot text and it didn't work -- same for me. A few posts later said to check the adb version. Mine is 1.0.32 and apparently there is now 1.0.40. I cannot find that one. The fastboot text was: fastboot --set-active=a. Didn't work for me either. Said unknown command.
I can boot into twrp but it is stuck on the opening screen.. Possible I can fastboot a new twrp and save it that way.
zulu657 said:
The drivers were for another unbrick solution, I believe. I've looked at so many it's now hard to keep them separate. My original quest was to make another slot active. Another member tried the fastboot text and it didn't work -- same for me. A few posts later said to check the adb version. Mine is 1.0.32 and apparently there is now 1.0.40. I cannot find that one. The fastboot text was: fastboot --set-active=a. Didn't work for me either. Said unknown command.
I can boot into twrp but it is stuck on the opening screen.. Possible I can fastboot a new twrp and save it that way.
Click to expand...
Click to collapse
If you can boot into recovery then booting a fresh img is a good idea, good luck!
szybki_ben said:
If you can boot into recovery then booting a fresh img is a good idea, good luck!
Click to expand...
Click to collapse
Just tried that one -- No Cigar!!! I followed the instructions for installing recovery on a new install. It said to use the text: fastboot boot recoveryimgrecovery.img I had renamed the Blu-spark img to recovery.img. The result was: no file or directory with this name. I was in the folder with adb, fastboot, recovery.img and all the rest of the files for OP6.
There used to be a way to install twrp with adb if I recall, but I can't find it. I know it was for an earlier phone. I have had OnePlus phones from the first one.
Very frustrating!!! I hate to wipe the phone because this should be a simple thing. Of course those are the ones that really get you....
Hmmmm, evidently the command fastboot set active=a is not a command in adb v1.0.32. When I tried it, I got a list of the commands and that one isn't in it.
Trying to find a later version of adb without success.
There has to be a way to change the active partition without formatting the phone. The phone had the original OS and I upgraded to Experience when I got it and have been using it ever since. Experience should be on another partition, so if I can change partitions, I should be on the original OS.
Would that not be correct???
Related
https://dl.twrp.me/cheryl
Razer Phone Install Instructions
Read these instructions and follow them carefully. Failure to do so may result in not being able to update the device in the future and there are no factory images available.
The Razer Phone uses the newer AB partition scheme first introduced on the Pixel 1. As such there is no recovery partition. Instead, the recovery is part of the boot image. Unlike the Pixel devices, Razer has disabled fastboot boot so there is no way to temporarily boot TWRP to perform an installation.
Getting into fastboot mode or recovery on the Razer Phone requires plugging the device into a USB cable. I would recommend against flashing or performing recovery-related actions unless you have access to a USB cable and port so that you can get back into recovery should something go wrong. Power off the device. Hold volume up to get into recovery or volume down to get into fastboot mode. Plug the device in while holding the appropriate button and the device should boot to the mode you selected. If it boots up to the charging screen, try a different USB cable or port. Make sure you are able to boot the device to fastboot via USB cable before flashing anything.
We are going to use the other boot slot to flash the initial copy of TWRP and boot TWRP. To do this you will need to turn on developer options and enable USB debugging. You will also need to enable OEM unlocking and unlock the bootloader. I am not going to discuss how to get the proper drivers installed or assist you with doing these basic steps. There's tons of guides elsewhere for these items if you need it. I will say that unlocking the bootloader requires using fastboot flashing unlock instead of fastboot oem unlock. Once you have adb working, run this command:
adb shell getprop ro.boot.slot_suffix
It should say:
[ro.boot.slot_suffix]: [_a]
Or:
[ro.boot.slot_suffix]: [_b]
Make note of whether you are currently using slot A or B. Next power off the device and boot to the bootloader using your USB cable and volume down. You want to switch to the other boot slot. If you are currently on slot A, type this:
fastboot --set-active=_b
Or on slot B type this:
fastboot --set-active=_a
You should see something like this:
Setting current slot to 'a'...
OKAY [ 0.042s]
finished. total time: 0.042s
I found the bootloader on the Razer Phone to be extremely finicky and I had to run the command multiple times until I got it to run successfully. You may have to hold the power button for 15 seconds to force power off the device and then re-enter fastboot mode. Keep trying until it works. Once it's on the right boot slot, type this:
fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot
Your device should now boot into TWRP. From here, decrypt your device if needed at the password prompt. DO NOT swipe to allow modifications until after you make your initial backup; instead tap on the read-only button. Go to the reboot page and tap on the button at the bottom to switch back to the slot you were originally using. Go to the backup page in TWRP and back up Boot and System Image. It is HIGHLY recommended that you save this backup in a safe spot on your computer because you may need to restore it to take official OTA updates from Razer. Once you have finished making your backup, run this command:
adb push twrp-installer-3.2.1-0-cheryl.zip /sdcard
In TWRP, tap on Install and browse to the zip and install it. TWRP will now be installed to both slots. TWRP is now installed and you can reboot and use your device as normal, though with TWRP installed, you won't be able to take OTA updates without restoring the stock boot image.
MTP is disabled because it causes a kernel panic sometimes with the stock kernel. ADB also does not work with the stock kernel which makes transferring files between your PC and the device when using the stock kernel a bit of a challenge. The TWRP bootable image does have working ADB though and you can copy files to a SD card or USB stick if needed.
Reserved!
Thanks you so much @Dees_Troy
Let development begin
Awesome work! :highfive:
Awesome! Now we just need to let the dev fun begin! BTW You Rox!
Edit: Im trying to do a full backup of the current state of my phone. went into TWRP and selected every partition and hit backup. Was flying along till it got to Data and it just stopped. No movement @ 40% for about 5 minutes so far Is it working for anyone else? does it just take insanely long with no percentage increase, or am I just being paranoid cause its my new phone lol
Edit 2: I just cancelled it and backed up everything but Data and it went fine, I'm now attempting to backup JUST Data.. Ill have to restore 2 backups seperately, but it appears to be working
Final Edit: All good.. not sure what happened the first backup but doing them seperately worked. Rooted with Magisk 15.1 and running beautifully! Gonna try out some root stuff like Xposed.. Thanks for all your hard work devs & testers!
@Dees_Troy Thanks for your work. Broken link https://github.com/TeamWin/android_device_razer_cheryl
Please update when you have time
Another thing in your instruction consider that on european razer phone the right command is this (I've found problem only for slot b in slot a work without -i 0x1532)
ffastboot -i 0x1532 flashing unlock
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i get the no devices/ emulators found
EDIT: I didn't realize you had to do that part with the phone on. so when I boot in to bootloader i have slot b and type the command to switch to a. all I see is waiting for devices. thats when I redo it until it writes correct?
RicardoSal24 said:
i get the no devices/ emulators found
EDIT: I didn't realize you had to do that part with the phone on. so when I boot in to bootloader i have slot b and type the command to switch to a. all I see is waiting for devices. thats when I redo it until it writes correct?
Click to expand...
Click to collapse
I've Uses this command to open bootloader?
fastboot -i 0x1532 flashing unlock
If yes command for your device work add -i 0x1532
raimondomartire said:
I've Uses this command to open bootloader?
fastboot -i 0x1532 flashing unlock
If yes command for your device word add -i 0x1532
Click to expand...
Click to collapse
I would still get the message saying <waiting for any device>
RicardoSal24 said:
I would still get the message saying <waiting for any device>
Click to expand...
Click to collapse
Verify your driver in setting. You must add google driver
raimondomartire said:
Verify your driver in setting. You must add google driver
Click to expand...
Click to collapse
link please
RicardoSal24 said:
link please
Click to expand...
Click to collapse
https://developer.android.com/studio/run/win-usb.html
not able to update the driver manually
---------- Post added at 12:49 PM ---------- Previous post was at 12:20 PM ----------
apparently there's no "compatible" driver software for a x64 bit system
RicardoSal24 said:
not able to update the driver manually
---------- Post added at 12:49 PM ---------- Previous post was at 12:20 PM ----------
apparently there's no "compatible" driver software for a x64 bit system
Click to expand...
Click to collapse
Use this
http://www14.zippyshare.com/v/ufYG71o0/file.html
I remember seeing something about no Wi-Fi in the other thread from the chat about source code. Is that still an issue? I ask because I completed this and have no Wi-Fi. Just double checking I didn't miss something
raimondomartire said:
Use this
http://www14.zippyshare.com/v/ufYG71o0/file.html
Click to expand...
Click to collapse
My problem is getting the drivers to work. I've tried Robin. That succeeded. But updating drivers in Device Manager doesn't work. It says there are no compatible drivers for the phone. And if I can't update drivers I can't get the phone to be recognized in Device Manager so adb can work
edit
DarkestSpawn said:
I remember seeing something about no Wi-Fi in the other thread from the chat about source code. Is that still an issue? I ask because I completed this and have no Wi-Fi. Just double checking I didn't miss something
Click to expand...
Click to collapse
Try switching slots in Twrp then restart.
I have a bit of an issue. TWRP has been flashed to both A and B because it didn't reboot to TWRP the first time so i did it again and now i can't boot into system. Stupid mistake i know but what can i do about it?
Xshooter726 said:
Try switching slots in Twrp then restart.
Click to expand...
Click to collapse
No problem also for me. I can share my slot b image
---------- Post added at 02:59 PM ---------- Previous post was at 02:44 PM ----------
Firebuster said:
I have a bit of an issue. TWRP has been flashed to both A and B because it didn't reboot to TWRP the first time so i did it again and now i can't boot into system. Stupid mistake i know but what can i do about it?
Click to expand...
Click to collapse
Try to boot in bootloader mode from twrp and after write fastboot reboot
Hello !
Just acquired an HTC U12+ in replacement for my brave Oneplus One, that i kept updated to Android Pie. Compare to my old One, HTC didn't make it easy to make mod...
As I hate all these stupid UI, i want AOSP without the google app as much as i can, so i wanted to try the Android Pie GSI "FLOSS", hoping it works great.
Anyway since yesterday i spend a lot of time trying to install TWRP on my U12, and fastboot and adb make me crazy. First i unlock the bootloader with the describe procedure, it works fine, i use fastboot from offical repo of ubuntu 18.10. I red all the thread and understand that i must boot first twrp and then flash it with the installer. The problem is fastboot and adb are not working after unlocking the bootloader. I am using the USB type C to type A cable from HTC.
My phone was with firmware 1.25 with june patch when i bought it. So i download the right version of TWRP. Fastboot is not working anymore and i get an error of "protocol". Then i see in the FAQ that you need to use the last version from google. This fastboot didn't worked much more, "too many links" error or similar. I tried different usb port of my pc, it seems the usb 3.0 and 3.1 do this, with usb 2.0 error is different, it said "downloading boot.img" and nothing happens. Then i tried to update to 1.30, but fastboot is not working more. I tried in windows, i install the htc driver and use the latest fastboot, same errors. Also tried another pc running ubuntu 18.04 without success.
Right now "fastboot devices" find the U12 properly but all command show error, and "adb devices" shows nothing in download mode.
I guess the problem come from the usb cable ? I live in a small town in the middle of nowhere and have no type c cable, so i ordered two new cable among other accessories, i hope they works but i won't have them before two week probably more (revolution in coming in France ).
But what i don't understand, if it's a problem with the cable, why fastboot was working when i do the "fastboot flash unlocktoken Unlock_code.bin" to unlock the bootloader, and then it refuse to work ?
Regards !
When you do fastboot devices and U12 shows up then you should be alright.
To boot TWRP you must be in boot loader, NOT download mode.
fastboot boot twp.img
It has worked for me just fine on windows, macOS, and Ubuntu
---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------
Use
fastboot --version
To see what fastboot version you have. Latest should be 28.0.1
Hello,
Thank you for your answer. I know the difference between the fastboot and download mode, i try everything but the problem is always the same. My fastboot is the latest from the xda topic :
./fastboot --version
fastboot version 28.0.1-4986621
For example i just try again, it's connected to the usb 2.0 port of my pc, i'm in fastboot (recovery) and not download mode :
./fastboot devices
FA8731F01429 fastboot
./fastboot boot twrp-3.2.3-2-ime.img
Downloading 'boot.img' ... and nothing happens
If it's connected to usb 3.0 or 3.1, get the "too many links" error.
Edit : another exemple, if i use the fastboot from kubuntu 18.10 repo :
[email protected]:~$ fastboot devices
FA8731F01429 fastboot
[email protected]:~$ fastboot boot twrp-3.2.3-2-ime.img
< waiting for any device >
@ghstmm
I've read your posts and I can't stop feeling that there's something off, obviously. Don't be mad at me cuz I'm not an expert, but you might be in the wrong mode. You should be in "Bootloader" mode which is different than "Recovery" mode.
That is a strange issue.
Several users on the Pixel 2 forum had the same issue and a different cable worked. I don't know how a cable only works with certain commands.
Looks like you're doing it right however. Unfortunately it might simply be a cable.
Maybe try flashing a boot.img that already has twrp in it so you can just use the bootloader recovery option?
---------- Post added at 08:35 AM ---------- Previous post was at 08:27 AM ----------
k_l_o said:
@ghstmm
I've read your posts and I can't stop feeling that there's something off, obviously. Don't be mad at me cuz I'm not an expert, but you might be in the wrong mode. You should be in "Bootloader" mode which is different than "Recovery" mode.
Click to expand...
Click to collapse
You should be on this screen.
BOOTLOADER
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes i am to this screen when i use fastboot. Not have the same info in the screen though. I cannot make a photo now so i will just write what i see :
press volume key etc...
Fastboot Mode (in red)
PRODUCT_NAME - HTC_Phone
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - FA8731F01429
SECURE BOOT - PRODUCTION
SECURE STATE - S-ON
DEVICE STATE - UNLOCKED (U) (in red)
KEY STATE - NONE
*** Software status: Modified *** (in red)
Guess i will try again when i'll get the other cable, but it's very strange indeed.
@ghstmm
Have you installed the latest HTC drivers?
Edit:
Forgot to mention I had the "too mank link" error because my HTC Drivers were out of date when I replaced my HTC 10 with the HTC U12+
k_l_o said:
@ghstmm
Have you installed the latest HTC drivers?
Edit:
Forgot to mention I had the "too mank link" error because my HTC Drivers were out of date when I replaced my HTC 10 with the HTC U12+
Click to expand...
Click to collapse
I mostly use linux so their is no driver, but in windows i install the HTC SYNC MANAGER. It finds the phone when firmware was in 1.25, but after update to 1.30 i got a message saying this software is deprecated and the manager didn't find the phone. What driver should i use ?
Regards
ghstmm said:
I mostly use linux so their is no driver, but in windows i install the HTC SYNC MANAGER. It finds the phone when firmware was in 1.25, but after update to 1.30 i got a message saying this software is deprecated and the manager didn't find the phone. What driver should i use ?
Regards
Click to expand...
Click to collapse
I brought up the HTC Sync Manager only for the purpose of installing the drivers. I uninstall the Sync Manager portion of the package afterwards. Anyway, try this link for the latest HTC Driver:
http://www.mediafire.com/file/g4r62oz2v9b1x0q/HTC-Mobile-Driver-v4.17.0.001.zip
I was already in v4.17.0.001. Guess i have to wait now for the new cable, hope it solve the problem...
Hello,
Normally no problem with the cable provided in the box of HTC! It is true that the U12 is pretty capricious! sometimes it takes several times with ADB!
It is not a problem of ADB version even the version 'htc_fastboot' of 2016 works at home!
PS: The most painful is the touch button to go into bootload Pffffffffff
Alan-B said:
Hello,
Normally no problem with the cable provided in the box of HTC! It is true that the U12 is pretty capricious! sometimes it takes several times with ADB!
It is not a problem of ADB version even the version 'htc_fastboot' of 2016 works at home!
PS: The most painful is the touch button to go into bootload Pffffffffff
Click to expand...
Click to collapse
I don't have any problem with adb, it works always without issues. Yeah sometimes it's difficult to boot into bootloader, but I use adb for that also
Sent from my HTC U12+ using XDA Labs
Just to know, when you run fastboot boot image are in you in the correct directory where the image file is?
master66 said:
Just to know, when you run fastboot boot image are in you in the correct directory where the image file is?
Click to expand...
Click to collapse
I try pretty much everything, inside or outside the platform-tools directory, also renamed twrp several time but no success.
Good news, i make it works I receive the cables todays, and even if the fastboot boot twrp.img still didn't work for any reason, adb works with the two cable i ordered. So i root the phone and use magisk to install twrp.
Strange thing, adb didn't work in download mode, only in android.
ghstmm said:
I try pretty much everything, inside or outside the platform-tools directory, also renamed twrp several time but no success.
Good news, i make it works I receive the cables todays, and even if the fastboot boot twrp.img still didn't work for any reason, adb works with the two cable i ordered. So i root the phone and use magisk to install twrp.
Strange thing, adb didn't work in download mode, only in android.
Click to expand...
Click to collapse
If fastboot wasn't working, then it's a driver issue. If you're in bootloader/download, you have to install them completely new again. Also TWRP has to be booted from bootloader, not download....
Sent from my HTC U12+ using XDA Labs
DeeZZ_NuuZZ said:
If fastboot wasn't working, then it's a driver issue. If you're in bootloader/download, you have to install them completely new again. Also TWRP has to be booted from bootloader, not download....
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Hello,
Again i was using the fastboot to fastboot, and download to adb
However i get a more serious problem. Now that twrp is working i tried to flash the gsi img. It works but when i start android ask me a password, so i look for the problem and it seems i just didn't wip data. I go back to twrp and perform data and wipe again, i wanted to flash again the gsi image. Problem is their wasn't anything in the sdcard directory (i didn't wip internal storage, so why ?). I try to adb to push to send again the gsi img, but when i go to twrp and go to the adb option, i get "adb devices sideload" and every command :
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb push /home/satan/system-arm64-ab-floss-su.img /sdcard
adb: error: connect failed: closed
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb usb
error: closed
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb devices
List of devices attached
FA8731F01429 sideload
I guess i got a very bad idea to reboot my phone as their was no os. So now the phone is rebooting constently. How i can i go again to twrp ?
Edit : i didn't understand everything from this A/B partition system... i guess my phone is brick now ?
ghstmm said:
Hello,
Again i was using the fastboot to fastboot, and download to adb
However i get a more serious problem. Now that twrp is working i tried to flash the gsi img. It works but when i start android ask me a password, so i look for the problem and it seems i just didn't wip data. I go back to twrp and perform data and wipe again, i wanted to flash again the gsi image. Problem is their wasn't anything in the sdcard directory (i didn't wip internal storage, so why ?). I try to adb to push to send again the gsi img, but when i go to twrp and go to the adb option, i get "adb devices sideload" and every command :
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb push /home/satan/system-arm64-ab-floss-su.img /sdcard
adb: error: connect failed: closed
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb usb
error: closed
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb devices
List of devices attached
FA8731F01429 sideload
I guess i got a very bad idea to reboot my phone as their was no os. So now the phone is rebooting constently. How i can i go again to twrp ?
Edit : i didn't understand everything from this A/B partition system... i guess my phone is brick now ?
Click to expand...
Click to collapse
No not bricked, but you can't sideload an img. Just get it back to sdcard and flash it from there, also for GSI it is better to wipe from stock recovery
Sent from my HTC U12+ using XDA Labs
Ok but how do i go back to the recovery ? The phone is just constently rebooting. From now to go to recovery i waited to be in android, press power button and down right after black screen, now i can't do that.
ghstmm said:
Ok but how do i go back to the recovery ? The phone is just constently rebooting. From now to go to recovery i waited to be in android, press power button and down right after black screen, now i can't do that.
Click to expand...
Click to collapse
This is a quote from the root thread:
"Long press (sometimes really long!) the Power button until you feel the vibration motor (not the feedback) kick in. When it kicks in let go of power button quickly and push volume down to boot into bootloader."
If I remember correctly this is how I was able to get my phone into bootloader when my phone was also in a boot loop. The timing must be precise or you will not get it into bootloader mode. Good luck.
Sent from my HTC U12+ using Tapatalk
mauiblue said:
This is a quote from the root thread:
"Long press (sometimes really long!) the Power button until you feel the vibration motor (not the feedback) kick in. When it kicks in let go of power button quickly and push volume down to boot into bootloader."
If I remember correctly this is how I was able to get my phone into bootloader when my phone was also in a boot loop. The timing must be precise or you will not get it into bootloader mode. Good luck.
Sent from my HTC U12+ using Tapatalk
Click to expand...
Click to collapse
Ok i get it Short timing indeed.
Edit : I finally install the latest android 9 pie gsi. It's working great and i love the floss version, but their is a few bugs : no brightness adjustment, localisation not working and few screen bugs (icon mostly).
Anyway thanks you all for your help
[SOLVED] Please read through, hopefully this helps someone!
Ive tried numerous threads and followed the steps always end up with some sort of error.
Device manager shows:
Kedacom USB Device>Android Bootloader Interface
errors:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
fastboot: error: Could not check if partition xbl has slot all
fastboot: error: Could not check if partition xbl_config has slot all
and continues with this error for what ever its trying to flash "has slot all"
flashing logical patitions error:
no such partition or partition not found
I keep researching and every video that shows what to do or posts, i can only get so far before my results dont match and there is no option or description for what to do if getting an error.
edit: adb devices shows nothing, but fastboot devices shows serial.
TIA
I think you have the wrong drivers, try these and check in windows update if your Qualcomm drivers are up to date in the optional updates. Also if fastboot is working and the bootloader is unlocked, you can download the latest full oos 12 and flash it all.
LaviLev said:
Ive tried numerous threads and followed the steps always end up with some sort of error.
Device manager shows:
Kedacom USB Device>Android Bootloader Interface
errors:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
fastboot: error: Could not check if partition xbl has slot all
fastboot: error: Could not check if partition xbl_config has slot all
and continues with this error for what ever its trying to flash "has slot all"
flashing logical patitions error:
no such partition or partition not found
I keep researching and every video that shows what to do or posts, i can only get so far before my results dont match and there is no option or description for what to do if getting an error.
edit: adb devices shows nothing, but fastboot devices shows serial.
TIA
Click to expand...
Click to collapse
If you need the latest oos I can link it here.
Nimiskiv said:
If you need the latest oos I can link it here.
Click to expand...
Click to collapse
Please do! currently DLing the drivers posted Thank you!
https://android.googleapis.com/packages/ota-api/package/435fc808f603bbc8a63ce30fd944676a65a61d6f.zip
LaviLev said:
Please do! currently DLing the drivers posted Thank you!
Click to expand...
Click to collapse
Oh but be careful that's for kebab 2005
Here's the repo
[OnePlus 8T][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
Added 11.0.5.6 KB05AA full zip from support website to OP
forum.xda-developers.com
Nimiskiv said:
Oh but be careful that's for kebab 2005
Here's the repo
[OnePlus 8T][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
Added 11.0.5.6 KB05AA full zip from support website to OP
forum.xda-developers.com
Click to expand...
Click to collapse
Anything with "kebab" in the beginning is OOS 12
Nimiskiv said:
https://android.googleapis.com/packages/ota-api/package/435fc808f603bbc8a63ce30fd944676a65a61d6f.zip
Click to expand...
Click to collapse
ok ty, looks like is c11 the first android 12 update for the OP8T, downloading now. Hopefully i can get it to flash.
LaviLev said:
ok ty, looks like is c11 the first android 12 update for the OP8T, downloading now. Hopefully i can get it to flash.
Click to expand...
Click to collapse
Use the MSM tool first
Nimiskiv said:
Use the MSM tool first
Click to expand...
Click to collapse
can not get phone to edl stuck in fastboot only. tried all the commands and physical button configs and still only get fastboot. Any workarounds?
I downloaded Fastboot Enhance, which allowed me to flash a bin file, but the phone still wont boot. I had to check ignore unknown partitions for it to flash. Now i can access fastbootd and when choose boot to recovery it loads what looks to a limited recovery similiar to fastbootd.
Any advice?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LaviLev said:
I downloaded Fastboot Enhance, which allowed me to flash a bin file, but the phone still wont boot. I had to check ignore unknown partitions for it to flash. Now i can access fastbootd and when choose boot to recovery it loads what looks to a limited recovery similiar to fastbootd.
Any advice?
View attachment 5683905
Click to expand...
Click to collapse
That's a stock OOS recovery you're seeing.
BillGoss said:
That's a stock OOS recovery you're seeing.
Click to expand...
Click to collapse
Any advice or known methods to get me running from here?
LaviLev said:
Any advice or known methods to get me running from here?
Click to expand...
Click to collapse
Run the MSM tool in edl, since now it should work fine. Also did the drivers work? If not you need to uninstall them in windows device manager, then reinstall them
LaviLev said:
Any advice or known methods to get me running from here?
Click to expand...
Click to collapse
Well, you've never said in your initial post what it was that you were trying to do.
Now that you are in the stock recovery you can select Advanced> reboot fastboot.
This will put you into fastbootd mode where you can do things like flash partitions and, more importantly, flash the logical partitions.
But, if you don't know how to do this and get out of whatever mess you're in , then use MSM Tool to reset your phone.
BillGoss said:
Well, you've never said in your initial post what it was that you were trying to do.
Now that you are in the stock recovery you can select Advanced> reboot fastboot.
This will put you into fastbootd mode where you can do things like flash partitions and, more importantly, flash the logical partitions.
But, if you don't know how to do this and get out of whatever mess you're in , then use MSM Tool to reset your phone.
Click to expand...
Click to collapse
I just reread my initial post, damn I started typing mid thought.. my bad!
I tried msmtool, but it doesn't load up a com port. All the listed methods with holding both vol buttons after already hitting start then plugging in did not work as I don't think it sees it at all.
Haven't found a thread with fastboot instructions that didn't require something I couldn't get to, to restore the phone. other methods fail writing to numerous areas when flashing.
trying this...
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
LaviLev said:
trying this...
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
Click to expand...
Click to collapse
OK was able to execute the first 4 fastboot commands, the it hung on the first flash --slot=all
In the end i just boot the phone in fasbootd using fastboot enhance and then using the flash bin file option in FE to flash the OOS 12 FILE @Nimiskiv shared.
Final boots into OOS, hope all works I will be testing to see for a day or two before i switch back from the 6, also before all this the 8T went a12_c11 to a12_c33
right now update for c20 came up!?
Any additional insight or final thoughts appreciated. Thanks again all!
LaviLev said:
OK was able to execute the first 4 fastboot commands, the it hung on the first flash --slot=all
In the end i just boot the phone in fasbootd using fastboot enhance and then using the flash bin file option in FE to flash the OOS 12 FILE @Nimiskiv shared.
Final boots into OOS, hope all works I will be testing to see for a day or two before i switch back from the 6, also before all this the 8T went a12_c11 to a12_c33
right now update for c20 came up!?
Any additional insight or final thoughts appreciated. Thanks again all!
Click to expand...
Click to collapse
check if EDL is working now, its very important for edl to work, because if something happens in the future, you need edl to reset.
Hello.
I've followed instructions as in this thread https://forum.xda-developers.com/t/root-psyche-root-xiaomi-12x-with-magisk.4455293/
only 1 thing I did wrong is downloading 13.02 boot.img file instead of 13.04 boot.img which wasn't available at that time.
After I flashed phone was stuck in Recovery mode bootloop, then for some reason it just got stuck in normal bootloop.
after that I downloaded 13.04 boot.img which was for my version, patched it on another phone in magisk, repeated instructions and now it's stuck in fastboot bootloop.
I also want to mention that I don't have external SD card so I was using boot.img directly from my pc.
Please help me.
There was solution to use Mi Phone Assistant but program doesn't detect my phone.
Edit: I'm green in these kind of termins so want to mention that it doesn't constant rebooting, just everytime I try to boot it goes into fastboot.
If phone is ADB enabled try this
1. Connect Windows desktop computer with phone via USB cable what came with phone
2. In Windows Command prompt run command sequence
Code:
adb devices
adb reboot
to exit phone into NORMAL boot ( i.e. system mode -> ANDROID OS)
xXx yYy said:
If phone is ADB enabled try this
1. Connect Windows desktop computer with phone via USB cable what came with phone
2. In Windows Command prompt run command sequence
Code:
adb devices
adb reboot
to exit phone into NORMAL boot ( i.e. system mode -> ANDROID OS)
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When in fastboot adb devices didn't find any devices
this screenshot is after I entered in recovery mode but you see it yourself...
Looks like USB Debugging isn't got successfully enabled on phone.
xXx yYy said:
Looks like USB Debugging isn't got successfully enabled on phone.
Click to expand...
Click to collapse
Does it mean that phone is forever bricked? Can you throw me some words of hope please.
it is not forever bricked. you just messed up with the boot image. try the troubleshooting steps from the link you ve posted with a different cable. or a different usb. or a different pc. the app should detect the phone at some point.
Fytdyh said:
it is not forever bricked. you just messed up with the boot image. try the troubleshooting steps from the link you ve posted with a different cable. or a different usb. or a different pc. the app should detect the phone at some point.
Click to expand...
Click to collapse
Thank you for advice, I will try.
Fytdyh said:
it is not forever bricked. you just messed up with the boot image. try the troubleshooting steps from the link you ve posted with a different cable. or a different usb. or a different pc. the app should detect the phone at some point.
Click to expand...
Click to collapse
Tried on different PC, didn't work. I doubt it's USB cable because it's original and I unlocked bootloader with it before. I'm desperate...
Edit: I think it's because of software that my phone doesn't get detected, https://prnt.sc/G232WPcRRqC1 mi unlock tool does detect it although only in fastboot mode, not recovery.
edit2: mi pc suite detects my phone in Fastboot mode but writes this... https://prnt.sc/4dB06CtvIfhz
can you enter in recovery mode ? when you enter in recovery mode, what options do you have ?
kiknalex said:
Tried on different PC, didn't work. I doubt it's USB cable because it's original and I unlocked bootloader with it before. I'm desperate...
Edit: I think it's because of software that my phone doesn't get detected, https://prnt.sc/uwS8qnna60rX mi unlock tool does detect it...
Click to expand...
Click to collapse
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Code:
fastboot flash boot boot.img
You may then boot to the OS via the below command
Code:
fastboot reboot
Sidenote: To avoid such scenarios in the near future, please refrain from directly flashing the boot.img. Rather first temporary boot via
Code:
fastboot boot magisk_patched_boot.img
And then use the Direct Install feature of Magisk for permanent root
Fytdyh said:
can you enter in recovery mode ? when you enter in recovery mode, what options do you have ?
Click to expand...
Click to collapse
https://prnt.sc/Oyjs9lxGVFX8 It's same as in this picture, not my phone tho. I didn't try erase data because I think it will disable USB debugging and I chose to wait for answers on forums.
binary**# said:
Sidenote: To avoid such scenarios in the near future, please refrain from directly flashing the boot.img. Rather first temporary boot via
Code:
fastboot boot magisk_patched_boot.img
And then use the Direct Install feature of Magisk for permanent root
Click to expand...
Click to collapse
Hey, thanks for help, I want to clarify 2 things:
1.
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Do I do it with stock boot.img or I should patch it?
2. Isn't that the same as instructions I linked in thread post?
kiknalex said:
Hey, thanks for help, I want to clarify 2 things:
1.
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Do I do it with stock boot.img or I should patch it?
2. Isn't that the same as instructions I linked in thread post?
Click to expand...
Click to collapse
flash the stock image first. after you get a fully fuctional phone attempt the rooting guide. as in, booting the phone as normal, be relieved that you did not hard brick it. then try again, and follow every step of the way.
Fytdyh said:
flash the stock image first. after you get a fully fuctional phone attempt the rooting guide. as in, booting the phone as normal, be relieved that you did not hard brick it. then try again, and follow every step of the way.
Click to expand...
Click to collapse
I just did it and situation is same, it enters bootloops in fastboot... I just remembered one thing and don't know how important it is but maybe makes a difference.
If I recall correctly, when I first flashed patched.img, the installation process wrote sending boot_b but after that it always said sending boot_a
like in this screenshot https://prnt.sc/t931it_cCodT .
Maybe it is root of problems?
I also want to mention a little detail that I rememeber.
When I was checking MIUI updates on site, the release was Stable BETA but only recovery was available, although now fastboot is available too, it's just Stable - without Beta, Perhaps my ROM was Stable Beta and not stable? It's 13.04 GLOBAL.
well, it does have importance. newer devices have 2 partition for booting. while older have only 1.
try this
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
kiknalex said:
Hey, thanks for help, I want to clarify 2 things:
1.
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Do I do it with stock boot.img or I should patch it?
2. Isn't that the same as instructions I linked in thread post?
Click to expand...
Click to collapse
Oh, I forgot to mention that you should only download the same version of Fastboot ROM that was installed on your device. And then flash the stock boot.img from that ROM to both slots using the commands given by @Fytdyh
Fytdyh said:
well, it does have importance. newer devices have 2 partition for booting. while older have only 1.
try this
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
Tried still same... maybe it's something with vbmeta.img?
or if your inactive partition is still non-corrupted [fingers crossed] then you could try booting it via that slot. For that, change the active partition via
Code:
fastboot set_active other
and then
Code:
fastboot reboot
binary**# said:
Oh, I forgot to mention that you should only download the same version of Fastboot ROM that was installed on your device. And then flash the stock boot.img from that ROM to both slots using the commands given by @Fytdyh
Click to expand...
Click to collapse
I downloaded same. :|.
I don't mind using another ROM if it will fix my issues, is it even possible to install from situation like this?
I shifted from apple to android recently and I decided to root my device OnePlus 8t KB2001 (I believe I have Android 12) as I wanted to install kali on it. Therefore I decided to follow instructions on this website. I did not type the steps because I did not want to lose out on any key details.
I performed all the steps till here:
I did not perform step 6, instead, I performed step 7 as I wanted to install TWRP Recovery on my phone permanently.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
According to the instructions I was supposed to boot my device to TWRP. Since I am currently booted to Fastboot, I used the Volume Keys to bring up the Recovery option and hit the Power key to confirm the decision.
As per the instruction as soon as my OnePlus boots to TWRP, it will ask to decrypt data. I was supposed to simply enter my phone’s password/PIN to proceed ahead but this never happened. Instead, I am stuck in a situation where I am seeing the following screen:
I searched every single option and there's no Online Update (keep data) option. I am stuck in this loop for hours. Even the option of formatting data doesn't remove this RECOVERY.
I don't know if this information would help but I can enter the Fastboot Mode by tapping on "Advanced" and selecting "Reboot to fastboot mode".
It would be really helpful if someone can tell me a fix to this problem as I really don't want to throw this phone away as I just got it today.
You probably flashed a version of TWRP made for Android 11 while having Android 12. You can try flashing a compatible version (unofficial) which you can find here.
I have not had the exact problem you describe but I don't think you'll end up discarding your phone. Just plan to read a lot on the forums, try a lot of things and potentially spend several days working through the problem. Bookmark the useful instructions you find so you can return to re-read and make notes as you go along. Start with booting a different version of TWRP and see what happens. The images you posted are of the stock recovery, not TWRP recovery. Make sure the TWRP.img you are trying to boot resides in the folder that your command prompt is pointing to.
TheNewHEROBRINE said:
You probably flashed a version of TWRP made for Android 11 while having Android 12. You can try flashing a compatible version (unofficial) which you can find here.
Click to expand...
Click to collapse
Thank you for this link. I followed these steps and I am out of the continuous recovery loop. My phone now directly boots to Team Win Recovery Project. Although I have a feeling my phone no longer has any oxygen OS. I tried rebooting into System but I am taken back to the TWRP screen. Any idea what is happening?
FakeGemstone said:
I have not had the exact problem you describe but I don't think you'll end up discarding your phone. Just plan to read a lot on the forums, try a lot of things and potentially spend several days working through the problem. Bookmark the useful instructions you find so you can return to re-read and make notes as you go along. Start with booting a different version of TWRP and see what happens. The images you posted are of the stock recovery, not TWRP recovery. Make sure the TWRP.img you are trying to boot resides in the folder that your command prompt is pointing to.
Click to expand...
Click to collapse
Thank you, this really gives me hope that my money will not go to waste. Now I am just in the process of trying to find a solution where I can my make phone the way it was which is without having any TWRP
kooluser said:
Thank you for this link. I followed these steps and I am out of the continuous recovery loop. My phone now directly boots to Team Win Recovery Project. Although I have a feeling my phone no longer has any oxygen OS. I tried rebooting into System but I am taken back to the TWRP screen. Any idea what is happening?
Click to expand...
Click to collapse
I think I know what happened:
The OnePlus 8T is a device which uses a technology called Virtual A/B. In practice, it has two slots for the operating system called 'a' and 'b' of which only one is active at a time. When you do an OTA upgrade the upgrade gets installed to the inactive slot and then the phone is asked to switch slot on the next boot. If the phone can't boot after this slot switch, it will switch back to the previous slot to prevent bricking itself. So what I think it happened when you flashed the wrong TWRP is that the phone tried to boot into recovery from your current slot but failed because of incompatibility. Then, it switched the active slot to the inactive slot where you probability have another version of OxygenOS that can't boot (probably because it's older than your current one). After some attempts, the phone goes into recovery but this time it loads the stock one because it has switched slot and the recovery is subject to this Virtual A/B mechanism too.
If this is what happened you can do as follows:
- reboot into fastboot
- switch the active slot by doing
Code:
fastboot --set-active=other
- flash the correct TWRP you downloaded before on this slot by doing
Code:
fastboot flash recovery <recovery file name>.img
After doing this you should be able to boot both into the system and into TWRP.
TheNewHEROBRINE said:
I think I know what happened:
The OnePlus 8T is a device which uses a technology called Virtual A/B. In practice, it has two slots for the operating system called 'a' and 'b' of which only one is active at a time. When you do an OTA upgrade the upgrade gets installed to the inactive slot and then the phone is asked to switch slot on the next boot. If the phone can't boot after this slot switch, it will switch back to the previous slot to prevent bricking itself. So what I think it happened when you flashed the wrong TWRP is that the phone tried to boot into recovery from your current slot but failed because of incompatibility. Then, it switched the active slot to the inactive slot where you probability have another version of OxygenOS that can't boot (probably because it's older than your current one). After some attempts, the phone goes into recovery but this time it loads the stock one because it has switched slot and the recovery is subject to this Virtual A/B mechanisms too.
If this is what happened you can do as follows:
- reboot into fastboot
- switch the active slot by doing
Code:
fastboot --set-active=other
- flash the correct TWRP you downloaded before on this slot by doing
Code:
fastboot flash recovery <recovery file name>.img
After doing this you should be able to boot both into the system and into TWRP.
Click to expand...
Click to collapse
THANK YOU SO MUCH!!! THIS SOLUTION SOLVED MY PROBLEM!
I can't express how happy I am right now!! I really thought I lost my phone forever. My phone has now successfully booted up and I can now actually use this device
kooluser said:
THANK YOU SO MUCH!!! THIS SOLUTION SOLVED MY PROBLEM!
I can't express how happy I am right now!! I really thought I lost my phone forever. My phone has now successfully booted up and I can now actually use this device
Click to expand...
Click to collapse
I'm happy for you too
TheNewHEROBRINE said:
I'm happy for you too
Click to expand...
Click to collapse
I just have one more question, so now if I have to boot into TWRP what steps should I follow? As I still have to download Magisk on my phone to properly root it
Did you flash TWRP after switching slot? If so you should be able to boot into it by holding power and volume down while turning the phone on.
Yes I flashed the TWRP as you specified below
Code:
fastboot flash recovery <recovery file name>.img
and once I press the power and the lower volume button I am taken into fastboot option. Once I am there which option should I select? Start, recovery or something else?
kooluser said:
Yes I flashed the TWRP as you specified below
Code:
fastboot flash recovery <recovery file name>.img
and once I press the power and the lower volume button I am taken into fastboot option. Once I am there which option should I select? Start, recovery or something else?
Click to expand...
Click to collapse
To root your phone you can follow this guide: https://forum.xda-developers.com/t/...national-kb2000-kb2001-kb2003-kb2005.4178675/
You actually don't strictly need TWRP to root. I suggest that you always try to follow guides that are on XDA rather than searching for random websites with Google.
TheNewHEROBRINE said:
To root your phone you can follow this guide: https://forum.xda-developers.com/t/...national-kb2000-kb2001-kb2003-kb2005.4178675/
You actually don't strictly need TWRP to root. I suggest that you always try to follow guides that are on XDA rather than searching for random websites with Google.
Click to expand...
Click to collapse
Thank you for the link. To perform this step do I need to do anything special right now? As I believe TWRP is still on my phone
kooluser said:
Thank you for the link. To perform this step do I need to do anything special right now? As I believe TWRP is still on my phone
Click to expand...
Click to collapse
It's not a problem to have TWRP installed.
TheNewHEROBRINE said:
It's not a problem to have TWRP installed.
Click to expand...
Click to collapse
Thank you so much for helping me and solving all my queries
kooluser said:
I just have one more question, so now if I have to boot into TWRP what steps should I follow? As I still have to download Magisk on my phone to properly root it
Click to expand...
Click to collapse
You can install magisk from TWRP recovery.
Changing slots is also possible there.