Hi, i tried to install lineage OS, but got bootloop.
I unlocked bootloader with MediatekBootloaderUnlock cmd file. Did many manipulations, got LOS working with bugs, wiped everyhing.
I installed custom patched boot from 4pda (from other firmware V13.0.7.0.RKEMIXM_20220419)
from recovery and after rebooted to it.
After phone got into bootloop with POCO logo.
Cannot enter fastboot and recovery.
Only after holding volume down button i get a 4 seconds phone visible in PC as com3 mediatek usb port , after it bootlopps again
Through MTK bypass i disabled bootrom protection, and phone is staying in brom mode for 30 seconds,after goes to loop.
But then what should i do? I havent used SP flash tool much. In Miflash phone isnt visible.
i got out of bootloop . downloaded MIFlash pro 7.3.608.18
Spoiler
miflash_pro-en-7.3.608.18.zip
drive.google.com
downloaded firmwavre to fastboot 5.6 GB V13.0.7.0.RKEMIXM_20220419
Spoiler
Redmi Note 11S / POCO M4 Pro – Global Stable Version List – MIUI Download Xiaomi Official ROM
Unpack firmware archive .tgz ,again unpack .tar from it
inside folder images/download agent there is a file flash.xml
Open MIFlash pro 7.3.608.18 , choose on top SP Flash v6.
Choose file flash.xml in download xml
Authentication file.A bit harder. Folks from xda found a way to bypass brom through downloading python and other stuff.
Phone after holding volume down buttononly visible to pc by 4 seconds ,after disappear and goes to reboot.
i used a program MTK META UtilityV44, press MTK BRom - Disable Authconnect , connect phone with volume down button holded.
in a left screen of program you will see brom bprotection removed
{
"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"
}
Aftel go to SPFlashtoolv6 and press download - download only.
The system would start flashing .after 6 minutes there would be a green sucess button.disconnect phone
But after turning on MUIU logo flashed for 2 seconds and disappeared and phone booted to recovery MUIU and says "nv data corrupted"
I have installed orangefox.
After installed LOS 19 through fastboot. But it didnt start (before losing imei it didnt start too with orangefox) ,but after flashing patched boot from 4pda the system started.
So now i lost IMEI. Cant understand how to recover. I tried using MAUI Meta, but my phone is not visible.
can somebody please backup nvram/nvdata partition with MAUIMeta or SPflashtool?
would very much appreciate, i cant use my phone now, lost 200$
i have wrote imei numbers with maui meta, but radio is off in ingineering menu in LOS,stock ram doesnt turn on.
can please somebody backup nvram , nvdata,nvcfg with spflashtool? i would change the imeis to my
Wouldn't sharing our nvram etc. backups with you essentially mean you would be using our devices IMEI/MEID? I wouldn't be comfortable with this I'm afraid, sorry!
aricooperdavis said:
Wouldn't sharing our nvram etc. backups with you essentially mean you would be using our devices IMEI/MEID? I wouldn't be comfortable with this I'm afraid, sorry!
Click to expand...
Click to collapse
yes, if you make backup all of those data will be inside.
you can change the IMEI numbers to null in Maui Meta (connection with brom bypass using mtkmetautility v44, reboot to meta mode) , duty in meta mode -imei download, change them to 0 , save nvdata, then change IMEI back to yours.
or with hex editor,but i haven't used it.
i managed to start the phone with nvram and nvdata from rn11s.
miui stock ram, but im unable to write imei numbers.
if i flash nvram and nvdata in SPFT later my phone is not visible with maui meta
if i dont flash nvram,nvdata phone is visible in maui meta, but after writing imei nubmers nothing happen.
i tried Tft_mtk6 cracked tool, but it doesnt work aswell.
blacklinkin said:
i managed to start the phone with nvram and nvdata from rn11s.
miui stock ram, but im unable to write imei numbers.
if i flash nvram and nvdata in SPFT later my phone is not visible with maui meta
if i dont flash nvram,nvdata phone is visible in maui meta, but after writing imei nubmers nothing happen.
i tried Tft_mtk6 cracked tool, but it doesnt work aswell.
Click to expand...
Click to collapse
Can you send NVRAM and NVDATA of rn11s.. let me check.....
Same issues here...
Is the problem solved?
BoysNap said:
Can you send NVRAM and NVDATA of rn11s.. let me check.....
Same issues here...
Is the problem solved?
Click to expand...
Click to collapse
wherr to find
NVRAM and NVDATA?
Related
Hey Guys,
I made a mess. Yesterday i tried again to unlock my Bootloader the official way, but without success. Because i tried this for several weeks, I was so frustrated that finaly used the unofficial method with the changed emmc_appsboot and the MiFlash with a Global Stable Rom.
Now the drama began. Because I'm stupid as f*** , I used Kenzo Rom and not the Kate Rom. After that the Phone couldn't detect the Sim Card, the Wifi, Bluetooth and booted repeatedly. After reading a lot of Tutorials through the night, I was able to get a stable Rom, an recovered EFS, my IMEI back and a detected Sim Card.
But my Note won't get any Connection from the Sim Card. It always says 'no service' and I can't update the Rom through the Updater, also the region is stuck on China and I can't change that.
The Rest works fine. I can install apps, write Mails and so on. But the most important thing doesn't work and I can't think of anything else to do.
I attached some Screenshots from my Phone and the Tutorials I used.
I still got TWRP and Root on the phone.
It would be really great if you guys can help 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"
}
http://en.miui.com/thread-235865-1-1.html
http://en.miui.com/thread-299779-1-1.html
https://forum.xda-developers.com/redmi-note-3/how-to/flash-recover-efs-snapdragon-t3406789
the only way is by reflashing the efs(modem via fast boot) if you are not aware of such things just flash latest fastboot rom via mi flash tool..
adithyan25 said:
the only way is by reflashing the efs(modem via fast boot) if you are not aware of such things just flash latest fastboot rom via mi flash tool..
Click to expand...
Click to collapse
Already tried flashing latest fastboot. Still had problems like missing Sim or missing IMEI.
Thought about flashing an Mod with new Kernel and TWPR. Could this fix the problem?
trabuc said:
Already tried flashing latest fastboot. Still had problems like missing Sim or missing IMEI.
Thought about flashing an Mod with new Kernel and TWPR. Could this fix the problem?
Click to expand...
Click to collapse
http://bigota.d.miui.com/V8.5.1.0.M...ED_20170619.0000.00_6.0_global_5e15f747f5.tgz
try this fastboot rom...flash it in edl mlde by wiping everything including storage using mi flash tool
adithyan25 said:
try this fastboot rom...flash it in edl mlde by wiping everything including storage using mi flash tool
Click to expand...
Click to collapse
But this is also a Kenzo Rom
trabuc said:
But this is also a Kenzo Rom
Click to expand...
Click to collapse
this is the latest one..i strongly belive hour efs and modem file is damaged .. so i will suggest to use latest roms always
adithyan25 said:
this is the latest one..i strongly belive hour efs and modem file is damaged .. so i will suggest to use latest roms always
Click to expand...
Click to collapse
I believe that too, but i got an Kate Version. Flashing Kenzo Rom is what brought me here in the first place.
My bad flash
reflash a earlier kate rom and let it update to the current version. I did what you did (wrong rom flash) and it gradually fully restored itself to fully working via updates
I did it! The phone is working perfctly again!
Here is how i did it:
- I flashed the newest Global Rom in EDR Mode (this time the right one)--> still no signal
- Then I tried to unlock the bootloader but still had the 99% Problem
- I made an backup from the whole phone trough the ADB commands
- Then I unlocked the bootloader the unofficial way
- after that I flashed the correct Modemst1, Modemst2 and FSG files through fastboot ("fastboot flash modemst1 modemst1" and
so on
- then i rebooted the device
- now Miui wanted a password to start the device
- so I made a factory reset and rebooted again
- now everything worked (signal etc.)
- then I installed TWRP and made an backup from the whole device again (extra backup of the Modem and EFS)
- Then I flashed my device again with the MIFlash Tool and rebooted the device
- Everything still worked, Bootloader is locked again and I can get the normal updates
Now I try to unlock the bootloader offically. If it works, great. If not, it's ok. I will never again unlock it unofficially . Too much problems.
I got the correct Modemst and FSG files from someone here so I don't think that I'm allowed to put the link up here.
Thank you all for your support
WiFi "NVRAM WARNING: ERR 0x10" Problem Fixed
The reasons for the appearance of this error
1- Write Firmware After Select in SP FLASH TOOL to Format All + Download
2- After Root + Insert Nvram File for another Model
3- After Upgrade System by OTA Upgrade
Fix the error problem
1- Download MTK ALL USB Driver 1.0.4 -1.0.8
2- Download SN Writer Tool v1.1728
3- Download AP_BP_Base
4- Extracted Files
5- Install Drivers
6- Open SN Write Tool Folder and Double Click to SN Writer.exe
7- Select in Interface Program
{
"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"
}
8- Click "System Config" and select Choose
9- Click "Start" and Writing IMEI1 / IMEI2 / Wifi Address
10- Processing
11- Finish
========================= Notes: =========================
1- If you do not find the modem file, just watch the following video:
2- After and Before Processing:
========================================================
i dont have IMEI 1 and IMEI 2
what to do if you dont have IMEI 1 and IMEI 2 , when i searched in my phone i found IMEI UNKOWN ?
Amrati23 said:
what to do if you dont have IMEI 1 and IMEI 2 , when i searched in my phone i found IMEI UNKOWN ?
Click to expand...
Click to collapse
you can download in the google playstore the app System info for Android.. open the app and go to System -telephony and their it has to be..
DiaboliCall
other solution for fixing invalid imei on infinix note 3 pro ?
hi master i am having always the same msg (entering meta mode failed ) but i am in meta mode and its affiched in little letters in the downscreen, so what is the solution, i tried more versions of imei writer and always the same msg ???
Know IMEI Original Code
Amrati23 said:
what to do if you dont have IMEI 1 and IMEI 2 , when i searched in my phone i found IMEI UNKOWN ?
Click to expand...
Click to collapse
In your phone there you can find your imei number after removing your battery or back cover. If your phone comes with a fix battery and cover then you can find those number from your mobile box that give you with phone when you brought it.
Hello , have the same Problem with NVRAM Warning,
Where can I find the address data for the Wifi of my Teclast T8 Tablet?
Invalid IMEI and NVRAM Error is Not Fix
For my mistake I use the "format all" option when I flash my phone by SP flash tool*without backup necessary data. Now my phone shows "NVRAM warning: err= 0x10"**and WIFI*Mac address frequently change and also IMEI is invalid. For this reason how can I fix this problem? Please give me a proper solution.**
Note: Phone does not root yet.
Doesn't work. Waste of time. There isn't enough explanation for "5- Install Drivers".
In the driver ZIP file, there are two version 1.0.4 and 1.0.8. Why have two? Which to install? And in each of them, there are 3 versions of Driver_auto_installer, and an MTK_Driver_ext. I tried the last version of Driver_auto_installer, but the writing software kept failing with "SmartPhoneSN::ConnectWithPreloader():Get dynamic preloader comport timeout".
I tried to run the "DriverInstaller.exe" in MTK_Driver_ext, but Windows said it cannot run it. It turned out that the application is 64-bit. So, I tried the same thing on a 64-bit Windows PC, but I got the same errors.
Also, the AP DB something file, it contains multiple files that start with BPL/AP per each chipset. The OP did not explain which files to use.
Dear Community,
Model: Lenovo X2-CU (is that Vibe X2?)
It has these problems:
IMEI1 is unknown
NVRAM WARNING: Err=0x10(which results in wrong WiFi MAC address)
Also, IMEI2 is valid
I've, recently, tried to restore NVRAM(IMEI + WiFi MAC address) using SN Write Tool(after Format ALL + Download method using SP Flash Tool), but it gives:
{
"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"
}
After that, it just hangs in META mode:
Stock ROM X2-AP_ROW_S223_150528(it also supports X2-CU model) is downloaded from https://www.needrom.com/download/lenovo-x2-ap/. Which, also, includes Modem and AP databases for IMEI and WiFi MAC restore.
Files BPLGUInfoCustomAppSrcP_MT6595_S00_X2-AP-L_V2_1_lwg_n and APDB_MT6795_S01_L0.MP5_W15.20 were chosen while using tool.
I've tried near everything:
1. Reinstalling VCOM drivers(by the way, they are from Vibe X2 drivers)
2. Using different versions to restore NVRAM:
SN_Write_Tool_v2.1504.00
SN_Write_tool_exe_v2.1412.00
SN-Write-Tool.2.13
IMEI and SN Writer v1.5.3
3. Chaging USB port
All in all, what could gives these errors? How to restore NVRAM correctly then?
ERROR!!SwitchMDBIndex[1] : MetaResult = META_FAILED
Click to expand...
Click to collapse
SP_META_ConnectInMetaMode_r Error: maybe is DEFAULT_FAIL cause this error...
Error: Connect failed, Exit Meta Mode
Click to expand...
Click to collapse
Thank you very much,
Best regards
Try This
vv77vv said:
Dear Community,
Model: Lenovo X2-CU (is that Vibe X2?)
It has these problems:
IMEI1 is unknown
NVRAM WARNING: Err=0x10(which results in wrong WiFi MAC address)
Also, IMEI2 is valid
I've, recently, tried to restore NVRAM(IMEI + WiFi MAC address) using SN Write Tool(after Format ALL + Download method using SP Flash Tool), but it gives:
After that, it just hangs in META mode:
Stock ROM X2-AP_ROW_S223_150528(it also supports X2-CU model) is downloaded from https://www.needrom.com/download/lenovo-x2-ap/. Which, also, includes Modem and AP databases for IMEI and WiFi MAC restore.
Files BPLGUInfoCustomAppSrcP_MT6595_S00_X2-AP-L_V2_1_lwg_n and APDB_MT6795_S01_L0.MP5_W15.20 were chosen while using tool.
I've tried near everything:
1. Reinstalling VCOM drivers(by the way, they are from Vibe X2 drivers)
2. Using different versions to restore NVRAM:
SN_Write_Tool_v2.1504.00
SN_Write_tool_exe_v2.1412.00
SN-Write-Tool.2.13
IMEI and SN Writer v1.5.3
3. Chaging USB port
All in all, what could gives these errors? How to restore NVRAM correctly then?
Thank you very much,
Best regards
Click to expand...
Click to collapse
Hi there,
You can use the mobileuncletool and use the engineering mode to manually insert the imei number which can be found back of the phone or the phones box or evening the sim tray. Make sure that you root your device first before inserting the imei, it's more effective.
Thank you
KIBS2173
KIBS2173 said:
Hi there,
You can use the mobileuncletool and use the engineering mode to manually insert the imei number which can be found back of the phone or the phones box or evening the sim tray. Make sure that you root your device first before inserting the imei, it's more effective.
Thank you
KIBS2173
Click to expand...
Click to collapse
Dear KIBS2173,
I've already tried that and getting:
Also, I can't root this phone, because its firmware will fail to OTA update with it.
Thank you
Try This
vv77vv said:
Dear KIBS2173,
I've already tried that and getting:
Also, I can't root this phone, because its firmware will fail to OTA update with it.
Thank you
Click to expand...
Click to collapse
Hi there,
have you tried not putting a space between AT+EGMR.
If that doesn't work try this method
use mtk driod tool
https://androidmtk.com/download-mtk-droid-tool
However you need to root for this method and it's a must have, without root access you cannot insert the imei. So using this mtk driod tool you can insert the imei then reboot the phone and check if its working. If it's working then you can backup the imei using mtk driod tool and now you can unroot the device, reflash the whole firmware and then restore the imei using mtk driod tool.
But you need to have ROOT no matter what.
Thank you
KIBS2173
I have an Oppo A51w (Oppo Mirror 5) that I just reset to factory settings, out of nowhere when I restared the phone after that it shows encryption unsuccessful, and a reset phone button, which I couldn't press.
Going into ColorOS recovery mode, I tried wiping data and cache, but wiping data doesn't work because it says I have no space it needs at least 250mb, but I remember the phone does have plenty of space, more than 7gbs, so I don't get why it shows that.
As for fastboot mode it doesn't really do anything other than show its starting logo and text and it turns off? Is there anything else I'm supposed to do I'm not sure?
Anything I could do to get past the encryption screen? I don't mind having to fully reset the phone or flash it but I might need a guide.
There is also an install from sd option in the recovery mode, if somehow it can be fixed from there then please help me with that.
The android version is 5.1.1 and ColorOS 2.1.0i
The version that shows on the ColorOS recovery is 1.2
Android 5.1 is too old. I am not sure which fastboot commands are supported for this version but you can try this even if Fastboot works for few seconds.
fastboot -w
fastboot erase userdata
If the fastboot method does not work then you need to find a MSM Download tool and correct firmware for your device model and flash it.
NextGenMagisk said:
Android 5.1 is too old. I am not sure which fastboot commands are supported for this version but you can try this even if Fastboot works for few seconds.
fastboot -w
fastboot erase userdata
If the fastboot method does not work then you need to find a MSM Download tool and correct firmware for your device model and flash it.
Click to expand...
Click to collapse
Does this need USB debugging? I don't have it enabled and can't enable it because I can't get past the encryption screen.
I tried using MSM download tool but for some reason it won't detect my phone and I'm not sure which usb driver to use and how to install it.
The phone also isn't rooted.
Update:
The phone is now stuck on boot loop. I tried to flash it from sd card using stock rom from the official website, without wiping data first because it wasn't possible (needs 250mb of storage space even though there IS enough free space). It said it was successful, but after rebooting it just gets stuck on boot loop.
- for adb I'd need usb debugging? Which can't be enabled
- the phone isn't rooted, so no cwm
- msm download tool I tried, v4 and v5 doesn't work it says "Packed image not exist" but v1.6.7 does? except even it won't detect the phone, and the rom that i downloaded for that from a different source had different phone model options which i do not recognize (oppo15008.bin etc and rawprogram0_MSM_15070.xml) so I'm not sure which one to choose. Maybe I haven't installed the driver but I don't know which to install and how to.
I really have no experience with this and just tried different guides on the internet to get the phone working. For now I don't know what to do. Any help is appreciated.
Your device seems to have Qualcomm chipset so it can be repaired in the EDL mode (9008). Search google "unbrick oppo a51w". It will give you all info you need to fix this.
If your device is not detected even after installing correct drivers, then you need to use Test Point method (shorting JTAG pins) to access EDL mode. This step needs expertise to short correct pins, if your attempts fail then your best option is the Oppo service center.
NextGenMagisk said:
Your device seems to have Qualcomm chipset so it can be repaired in the EDL mode (9008). Search google "unbrick oppo a51w". It will give you all info you need to fix this.
If your device is not detected even after installing correct drivers, then you need to use Test Point method (shorting JTAG pins) to access EDL mode. This step needs expertise to short correct pins, if your attempts fail then your best option is the Oppo service center.
Click to expand...
Click to collapse
I searched and I seem to have tried following steps like this before and it didn't detect my phone even with Qualcomm driver installed, also didn't know which phone model mine is and I'm supposed to choose between these, how do I know?
{
"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"
}
southeeast said:
I searched and I seem to have tried following steps like this before and it didn't detect my phone even with Qualcomm driver installed, also didn't know which phone model mine is and I'm supposed to choose between these, how do I know?
Click to expand...
Click to collapse
Sorry, I cannot help with selection of firmware.
Is there any reason why you can't get this repaired in the Oppo service center?
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.