disclaimer - sorry i really have no idea what i am doing and my goal is to just go back to my normal phone
my phone is poco f1 and now i can only access fastboot and this "powered by android" screen. fastboot into twrp doesnt work because of "boot command is not allowed in lock state" error
hello all so i tried rooting my phone and then realized that its going really badly (i have a more details about it down) so i decided to flash stock rom using techno treatment's tutorial on it but along the way i have faced a couple of problems - when trying to install drivers, program crashes, and others below
first time i flashed i got an error (timeout error in logs) , so i tried to flash again but this time i left it open for some time (at around 500 seconds i pressed flash again, in logs it shows that flashing already started) and when i came back it was at 12000 seconds still flashing so i closed miflash and am flashing once again but with a shorter folder path (desktop\xiaomi\firmware).
after this i deleted 2 lines in flash_all.bat because i kept getting stuck on echo mismatching image and device. after this everytime i try to flash i get this error - error:Erasing 'boot' FAILED (remote: 'Erase is not allowed in Lock State')
and also error:Erasing 'boot' FAILED (remote: 'Erase is not allowed in Lock State') in the other log file
and after this i tried to go into fastboot but noticed that the fastboot logo is different, it was a bunny with a hat repairing android robot but now it is android robot repairing itself
{
"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"
}
(this is what it looks now)
what i did before flashing stock - sorry my memory isnt the best this is all in a span of around 5 hours and my phone is pocophone f1. so at first i followed munchys tutorial on how to root, i succesfully enabled bootloader then in twrp i flashed recovery with some errors like failed to mount /system and 3 others like this but i ignored and continued then i installed magisk and after that in the video he goes into his phone no problem but i had "no os" and i think i just clicked around like backing up, restoring and wiping. then i thought i need a rom because its an os right? so i installed lineage and that was the last time when i could put files into my phone through usb. then i flashed the zip and after that rebooted and got "cant load android system, your data may be corrupt" so i pressed format something like that and did it a few times (i think this is when i couldnt put my files) until eventually saw that its no use so i went back to twrp and again clicked around until eventually wiping everything now i have no os and i cant transfer anything through usb.
Hi @medioqre
Seems like you are in locked bootloader state. You can not flash any ROM with locked bootloader unless you are enter EDL mode. See youtube tutorial to access edl mode for Beryllium
khusika said:
Hi @medioqre
Seems like you are in locked bootloader state. You can not flash any ROM with locked bootloader unless you are enter EDL mode. See youtube tutorial to access edl mode for Beryllium
Click to expand...
Click to collapse
Hi, to confirm - entering edl mode requires me to open up my phone right? how would i do that and how would i close it up after?
Thank you!
medioqre said:
Hi, to confirm - entering edl mode requires me to open up my phone right? how would i do that and how would i close it up after?
Thank you!
Click to expand...
Click to collapse
That's right, but i recommend go to the service center if you aren't able to do it.
khusika said:
That's right, but i recommend go to the service center if you aren't able to do it.
Click to expand...
Click to collapse
Hi again, its been 10 days.
so i have not went to a service center yet, because my city is too small for that. But i have a question. i didnt do anything else with my phone but today i decided i could do something and i booted it and i found out i can access fastboot mode and recovery mode, and in here i can see -
main menu, mi-recovery 3.0
and this one option
"connect with miassistant" which just gives me a picture of a phone if its plugged or unplugged with usb and under theres is a link to this website pcsuite.mi.com which doesnt work.
does this change my situation?
medioqre said:
Hi again, its been 10 days.
so i have not went to a service center yet, because my city is too small for that. But i have a question. i didnt do anything else with my phone but today i decided i could do something and i booted it and i found out i can access fastboot mode and recovery mode, and in here i can see -
main menu, mi-recovery 3.0
and this one option
"connect with miassistant" which just gives me a picture of a phone if its plugged or unplugged with usb and under theres is a link to this website pcsuite.mi.com which doesnt work.
does this change my situation?
Click to expand...
Click to collapse
If you are still in locked bootloader, you can't write firmware through fastboot or recovery
Why don't you try unlocking the bootloader officially?
Related
Hey so it's me again,
I wiped my phone via TWRP because I couldn't access it (went to type the correct password and it always said I was wrong), aaand, now it's stuck on the Mi logo screen.
Again, I looked up demos on how to fix it, and it hasn't worked. As far as I know, all I can get into is fastboot mode (won't even turn off).
My plan was to flash the default stable ROM onto it via MiFlash (as that's what most of the demos recommended) but I can't even get to that stage because I need to get into EDL mode, which I can't do.
Please help.
- Roisin.
Why would you need to get it into EDL? Put it in fastboot and open miflash, download the correct files and flash stock MIUI. You can get back to flashing other stuff after.
Honestly the only reason I thought that was because I read it somewhere, I'm not great with this phone (obviously) :')
Though I do remember trying that and it came up with an error, I'll try it again after school and I'll get back to you. Thanks.
WizardyNinja said:
Hey so it's me again,
I wiped my phone via TWRP because I couldn't access it (went to type the correct password and it always said I was wrong), aaand, now it's stuck on the Mi logo screen.
Again, I looked up demos on how to fix it, and it hasn't worked. As far as I know, all I can get into is fastboot mode (won't even turn off).
My plan was to flash the default stable ROM onto it via MiFlash (as that's what most of the demos recommended) but I can't even get to that stage because I need to get into EDL mode, which I can't do.
Please help.
- Roisin.
Click to expand...
Click to collapse
Happened to me too after wiping one of the partitions I shouldn't have when reinstalling CM. I just re-unlocked using the Mi Unlock program on Windows and then flashed CM13 back. Booted perfectly.
@banana_bender thanks for the tip!
I attempted to flash the ROM and it didn't work. All the tutorials with using MiFlash have a different version, it's confused me.
{
"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"
}
You need to select flash all at the bottom
harishmenace said:
You need to select flash all at the bottom
Click to expand...
Click to collapse
There's only "clean all", "save use data", and "clean all and lock" at the bottom. :/
*EDIT* nevermind I found it, gonna try it now!
WizardyNinja said:
Hey so it's me again,
I wiped my phone via TWRP because I couldn't access it (went to type the correct password and it always said I was wrong), aaand, now it's stuck on the Mi logo screen.
Again, I looked up demos on how to fix it, and it hasn't worked. As far as I know, all I can get into is fastboot mode (won't even turn off).
My plan was to flash the default stable ROM onto it via MiFlash (as that's what most of the demos recommended) but I can't even get to that stage because I need to get into EDL mode, which I can't do.
Please help.
- Roisin.
Click to expand...
Click to collapse
Yes, you need get into EDL to flash. Try this .cmd file on fastboot.. Wait until its boots to edl and red led pops up.. Then use ur MiFlash. Remmbr edl mode wont have any display. Just the red led indication.. Hope it helps
Sent from my Xiaomi Mi 5 using XDA Labs
Hello,
My LG-D280N is bricked... i think... every time it boots it goes on a purple screen called Demigod crash handler, it also does the same thing when i try to factory reset it
So i had no choice but to flash a new room to hopefully fix it, THANKFULLY it does go to download mode without crashes and it does show up on my device manager as "Android bootloader interface" but even so the flashtool says port(USB or Serial) not found, here is what the phone says
{
"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"
}
As i was writing all that, it actually booted to android!!!! but there are infinite " app stopped" messages, it's impossible to go to settings and try to hard reset or rather it's impossible to go anywhere, looks to me like re-flashing a brand new stock rom is the only choice
i should say that i put this phone in my closet two months ago and it was fine! when i tried to use it today it was like that but anyway, is there anything i can do? I really need to fix that phone
Thanks alot, i really appreciate any help
An update... the phone responds to fastboot commands from ADB tools, it doesn't show up on "adb devices" list though
Wonder if there is a way to use to use fastboot commands to flash a kdz file?
More updates... i used a tool to extract everything from the KDZ file and reflashed the following files like this:
fastboot flash boot boot.bin
fastboot flash factory factory_475136.bin
fastboot flash factory recovery.bin
fastboot flash aboot aboot_144384.bin
fastboot flash aboot abootb_150528.bin
Now i could of have done something either right or extremely stupid BUT ever since i did that factory reset mode actually worked! no more demigod crash handlers and i also stopped seeing those small "boot verification errors" in the corner and the phone actually booted and saw the initial welcome screen, so it actually factory reseted! BUT even though it did I STILL saw the sea of "*instert app here* has stopped" which makes it impossible to navigate the phone
But for whatever reason, it's now stuck on the startup logo after a reset, well even if i screwed up badly, download mode still works like before sooo it's not much different, at the very least i got rid of the stupid demigod crash handler
I've been working on that phone for hours now... been researching on google with little to no information about this at all, most solutions involve the flash tool WHICH doesn't work so i had to come up with my own ideas... and to make matters worse nobody here has gave me clues on how to fix it which is why i give these updates, maybe all this information will help you come up with a solution
Another update... i was wondering why it wouldn't be detected by my flashtool... until it hit me... the download mode itself has problems, thankfully fastboot still worked and i was able to reflash it using one of the files i extracted from the KDZ file
After this, my download mode now works correctly, it displays everything right and is now recognized by the flashtool! finally some real freaking progress, working on this thing is such a pain but finally im getting somewhere, but it's not over yet, right now im waiting for the device to reach 40% of charge before i flash the rom, hopefully no errors will occur as it has already been a HUGE pain and time consuming
Final update... i have successfully flashed the stock rom, after a whole day of trial and error i did it, let me summarize
My problem was mostly that the download mode itself needed to be reflashed, for whatever reason it was broken or not properly configured but whatever the case, it needed to be reflashed using fastboot in order to work correctly and be recognized by the LG Flashtool, after i reflashed it, it was fine and the LG Flashtool FINALLY recognized my device, but the LG Flashtool would CRASH whenever i clicked the "Read Phone Information" button, not sure why but i tried 4 times until it finally worked, not sure what happened there but who cares, it worked out, then it finally started flashing until it said "error connecting to the server", took me sometime and research to realize that it's SUPPOSED to do that and that i should ignore the message and NOT close it because if i do the whole flashtool stops, after this i let it sit in the background and do all the flashing, it was fine until 77%, it gave me an error message and said that i should try to reset my device back into download mode, then it retried doing the whole process all over again AND THANKFULLY this time it successfully did it, the phone now boots to Android as normal, the sea of "app stopped" message is also gone thankfully and so that's pretty much it...
My absolute stupid mistakes and problems with this could help other people avoid those same mistakes and problems so i won't delete the post since as i said, it can prove to be useful to others
Hello friends, I hope you are well. I am writing to everyone to see if anyone can help me with this big problem.
Yesterday install the Rom Pixel Experience, all good, all the steps to perfection and others, had microSD at that time so flash the boot.img by Fastboot. It seems to install the Boot.img in the Recovery TWRP partition, or something like that. Because I do not have the Recovery either, when I try to go to the recovery, the window "Bootloader Unlocked" appears, but it does not take me anywhere, only to the boot of the rom, it is something very strange and the truth scares me. I clarify: I can not access the Fastboot, nor the download mode, nor the recovery, because it does not.
There will be another way: ????
PLEASE IF SOMEONE CAN HELP ME, FIND ANOTHER METHOD TO ENTER THE FASTBOOT OR DOWNLOAD MODE, THE SOLUTION THAT WORKS WILL PAY ME WELL TO THE PROPONGA, PLEASE, I DO NOT WANT TO LOSE MY MOBILE, I BUY IT WITH A LOT OF EFFORT.
Last night I dawned on the boot logo, until it was completely downloaded and at this moment it continues to do so ... By GOD!
When trying to enter the Fastboot or download mode, it takes me here:
{
"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"
}
Image extracted from: https://www.tomshw.it
Then he starts loading the rom and stays there all the time .:
Image extracted from: https://www.tomshw.it
I can not access Fastboot, nor download mode, nor recovery, because it has disappeared. There will be another way to enter the Fastboot or download mode, because the phone actually woke up until I wake up today and was even charged. PLEASE.
Hey, sorry for your sad state. Following process worked for me when I got stuck yesterday like that.
1. Connect your phone to PC ( make sure adb/fast boot is setup)
2. Hard reboot your phone with power plus volume down button.
3. As soon as your phone turns off, press volume down only and keep it pressed till you enter fastboot.
4. After this phone should be recognised in PC and you should be able to boot in TWRP using fastboot.
ZestyManu said:
Hey, sorry for your sad state. Following process worked for me when I got stuck yesterday like that.
1. Connect your phone to PC ( make sure adb/fast boot is setup)
2. Hard reboot your phone with power plus volume down button.
3. As soon as your phone turns off, press volume down only and keep it pressed till you enter fastboot.
4. After this phone should be recognised in PC and you should be able to boot in TWRP using fastboot.
Click to expand...
Click to collapse
Hope this works for you @Yeriorlando. @gimpy1 had a similar issue when installing Havoc ROM. Part of the problem seems to be when installing the custom kernel?
gimpy1 said:
It was operator error (generally is) on my part, I'm sure. The only thing I did different that I can remember is installing the 9.0 boot image in twrp differently. I installed it in the recovery option first (intentionally, should not have), instead of ticking only the boot choice. I did not untick the recovery option (should have never ticked it in the first place, but I was trying to correct a problem on the ROM, and misread a post).
Click to expand...
Click to collapse
He was able to reinstall TWRP using fastboot.
gimpy1 said:
Thx, Chaz. I pulled out my printed instructions from your post, and once I was able to get my device recognized (that did take a couple of tries), reinstalling twrp was pretty easy.
I'm back in business thanks to you.:good:
Click to expand...
Click to collapse
IF you still can't after the suggestion at top, maybe @SGCMarkus or @runningnak3d have some tips?
Unless you have an H932, then if you get the error that: "Your device software can't be checked for corruption" then you have fastboot. It is literally impossible to have that message on a WTF rooted phone and NOT have working fastboot.
So, as @ZestyManu said -- make *sure* your phone is powered off. If you have to let, the battery die. Then hold vol down + plug in the USB cable (no need to touch the power button) and you will enter fastboot.
-- Brian
Thank you all. I have solved the problem in a super crazy way, to pure ADB, not fastboot .... Pure ****ing adb ... Hehehehe. Thanks to @ChazzMatt
Hello everyone,
I've been googling this for the past couple days it's been driving me crazy. Stock 7 (I think), should have been unlocked but is showing locked.
1. My friend gave me the Nexus 9 which turned off one day, then wouldn't turn on again.
2. I plugged it in, and it turned on fine. Assumed bad usb port, he said keep it. I enabled developer options, then did "OEM [bootloader?] unlock" and "USB Debugging" toggles on (from memory, may not be right phrasing)
3. While trying to back up his data on it by ADB Pull, it would randomly stop. Using it, it would reboot unexpectedly.
4. So I went to Software Update.. bad idea in retrospect probably it rebooted during or something? It was fully charged and on AC power but I wasn't watching it.
5. I come back and it keeps bootlooping. Went into recovery, says "Device Locked" - Tried clearing cache, no difference. Tried sending bootloader unlock command with fastboot, says I have to delete all data to unlock.
The only lead that I have is that it might be possible to image TWRP to recovery, then boot into it so that I can get files off it (With OTG Flash drive or USB?) - I wanted to ask for help here first.
I did my best to search for this prior, but I've been out of the ROM game since 2012 cyanogenmod days.. Hope that it's possible to save my friend's data, and then also to flash a new ROM which will solve the reboot issue.. Thanks!
Boot to recover, then when you get the Android mascot with the belly open, press ( I think vol up plus power) to get to a functional recovery with ADB support.
gk1984 said:
Boot to recover, then when you get the Android mascot with the belly open, press ( I think vol up plus power) to get to a functional recovery with ADB support.
Click to expand...
Click to collapse
Thanks GK,
After going into recovery mode, there's the android mascot with the belly open as you describe. Then, I do (VolUp+Pwr) and it produces this screen below, which I'm guessing people call "fastboot". When I'm there, my Win10 PC makes the "USB item attached" noise, and I can use fastboot commands, but adb devices won't show anything. Do you have any ideas?
{
"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 thought I could use the fastboot access I have to flash twrp, but I get the following error. I switched the "OEM Unlock" toggle, but i'm guessing that doesn't mean anything until I unlock the bootloader in recovery (which necessitates deleting all the files). I followed the directions on the twrp website which claim that root isn't needed, but I guess unlock is.
Code:
PS C:\Users\User Profile\Downloads\platform-tools_r30.0.1-windows\platform-tools> .\fastboot flash recovery twrp.img
Sending 'recovery' (13254 KB) OKAY [ 0.838s]
Writing 'recovery' (bootloader) Device State : Locked
FAILED (remote: 'Can not flash any images while device state is locked!')
fastboot: error: Command failed
Thanks again,
luciant
luciant said:
Thanks GK,
After going into recovery mode, there's the android mascot with the belly open as you describe. Then, I do (VolUp+Pwr) and it produces this screen below, which I'm guessing people call "fastboot". When I'm there, my Win10 PC makes the "USB item attached" noise, and I can use fastboot commands, but adb devices won't show anything. Do you have any ideas?
I thought I could use the fastboot access I have to flash twrp, but I get the following error. I switched the "OEM Unlock" toggle, but i'm guessing that doesn't mean anything until I unlock the bootloader in recovery (which necessitates deleting all the files). I followed the directions on the twrp website which claim that root isn't needed, but I guess unlock is.
Thanks again,
luciant
Click to expand...
Click to collapse
You need to be in recovery for adb to work. The Android with belly open is recovery but you need to unlock it with a button combo. Fastboot won't work unless you unlocked the bootloader.
I may have the steps a little off for getting to recovery but I'm sure searching how to boot to recover for the Nexus 9 will find you the right steps. It's been a long time since I've used the stock recovery on this tablet.
For future bootloopers: Well in the end, I wasn't able to figure out how to pull files using the stock HTC Nexus 9 recovery. Since it was locked, I wasn't able to install or execute TWRP .img , and unlocking it meant losing the files. It was weirdly looping even in Recovery & Fastboot. I tried every mode, and different drivers in the device manager, but ADB couldn't connect. Maybe it's not meant to for security purposes.
If you're bootlooping even in recovery, try the following:
I gave up on trying to recover the data, and decided to just unlock the bootloader. booted to Fastboot (Pwr+Vol Down on start up, select Recovery, Pwr+Vol Up, should say "Fastboot") Then I used fastboot oem unlock, which unlocked the bootloader and Deleted ALL DATA. Then, I could flash TWRP, using fastboot flash recovery twrp.img. Once I flashed TWRP, I booted to twrp recovery using Pwr+Vol Up at boot, wiped all partitions. Then I went to TWRP Advanced -> ADB sideload. Issued adb sideload ota.zip, and this gave me a clean stock install.
Thanks gk for your advice.
Usure how I ended up in this state:
Phone is an Ace Pro 5G, originally with indian rom, that I flashed using Oxygen Updater to CPH2415_11.C.22 (GLO A13).
Everything went fine, installed Magisk started to restore all my apps... I after some reboots, it ended up in boot loop. No idea why.
I can access recovery & fastbootd througt Fastboot enhance, but the weird thing is that I cannot use the touch screen in fastbootd, only volume keys and power button to select options. Quite useless as any operation pops up a dialog, and I cannot click the OK button.
Already tried to flash through Fastboot enhance multiple versions of oxygenos, including stock rom CPH2413 A05, and it always end up in boot loop.
Any idea on what I can flash to recover from this state? My guess would be fastbootd got somehow broken...
you need sent to the after-sales，the 9008 need to authorization
Petronius42 said:
Usure how I ended up in this state:
Phone is an Ace Pro 5G, originally with indian rom, that I flashed using Oxygen Updater to CPH2415_11.C.22 (GLO A13).
Everything went fine, installed Magisk started to restore all my apps... I after some reboots, it ended up in boot loop. No idea why.
I can access recovery & fastbootd througt Fastboot enhance, but the weird thing is that I cannot use the touch screen in fastbootd, only volume keys and power button to select options. Quite useless as any operation pops up a dialog, and I cannot click the OK button.
Already tried to flash through Fastboot enhance multiple versions of oxygenos, including stock rom CPH2413 A05, and it always end up in boot loop.
Any idea on what I can flash to recover from this state? My guess would be fastbootd got somehow broken...
Click to expand...
Click to collapse
after fastboot enhance flash, trying wiping the data from the recovery
Yeah so it was actually hard bricked, ended up paying thoses 20$ to get it restored though remote desktop by some oneplus employee (google ministryofsolutions)
So I've bricked again like 10 minutes after my previous, trying to restore an app using Titanium Backup. I guess it does not support oxygenos very well...
Anyway, I may have found a way to unbrick without MSM!
I tried to flash stock CPH2415 and other versions though fastboot enhance without any success (black screen, only recovery and fastbootd working every time).
What I noticed, is that my device was incorrectly recognized in fastbootd mode:
{
"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"
}
"ossi" is the 10 Pro, not 10T... weirdly enough, it was correctly labeled in the tool before rebooting in fastbootd.
So what I tried was flashing the same playload.bin but without rebooting in fastbootd (when the device name is correctly recognized as "taro"), ignoring the bunch of unrecognized partition and the warning message "you should reboot to fastbootd".
And Tadaaaa, it worked...
Petronius42 said:
So what I tried was flashing the same playload.bin but without rebooting in fastbootd (when the device name is correctly recognized as "taro"), ignoring the bunch of unrecognized partition and the warning message "you should reboot to fastbootd".
And Tadaaaa, it worked...
Click to expand...
Click to collapse
You got very lucky. It means that whatever was borked wasn't a partition that needed to be flashed in fastbootd. It could have easily gone the other way as those unrecognized partitions just got skipped. Others have found this out the hard way.
Also, TiBu hasn't been updated in years. Switch to Swift Backup.
EtherealRemnant said:
You got very lucky. It means that whatever was borked wasn't a partition that needed to be flashed in fastbootd. It could have easily gone the other way as those unrecognized partitions just got skipped. Others have found this out the hard way.
Also, TiBu hasn't been updated in years. Switch to Swift Backup.
Click to expand...
Click to collapse
No but I did flash the same payload.bin through Fastboot enhance in fastbootd mode, which did not resolve the issue. Probably because of the incorrect detection of the 10T in 10 Pro?
Flashing the same payload.bin through Fastboot enhance in fastboot mode did the trick (and the device name was taro, not ossi)
Good advice for Swift Backup, thanks.