Related
Phone oneplus3t, 64GB model EU
Oxygen OS 3.5.4
Android 6.0.1
Bootloader: unlocked
Im having problems with flashing/booting TWRP
It flasheh succsesfully, but it doesnt boot. This is the error i get in the comand prompt: Boot twrp: failed (remote: dtb not found).
I tried flashing it via oneplus3t "all in one tool" and i tried it with downloading only the TWRP.img and flashing it in comnad prompt myselfe. Always the same problem. I also tried a modified TWRP which i found on the thred here somewhere: same problem.
It flashes, but doesnt "open" or boot. Right after I flash it if i click "recovery" it just goes back to the fastboot menu where i started.
I also tried this before i updated it on the oxygen 3.5.4
Please help, Thanks
Did you use the specific twrp recovery for the 3T? This one: https://dl.twrp.me/oneplus3t/
And did you follow a guide. This one for instance: https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/
jann32 said:
Phone oneplus3t, 64GB model EU
Oxygen OS 3.5.4
Android 6.0.1
Bootloader: unlocked
Im having problems with flashing/booting TWRP
It flasheh succsesfully, but it doesnt boot. This is the error i get in the comand prompt: Boot twrp: failed (remote: dtb not found).
I tried flashing it via oneplus3t "all in one tool" and i tried it with downloading only the TWRP.img and flashing it in comnad prompt myselfe. Always the same problem. I also tried a modified TWRP which i found on the thred here somewhere: same problem.
It flashes, but doesnt "open" or boot. Right after I flash it if i click "recovery" it just goes back to the fastboot menu where i started.
I also tried this before i updated it on the oxygen 3.5.4
Please help, Thanks
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=kTdKmceC5xU watch this video
Hi,
I just purchased a used Xperia Z1 C6903 and I am trying to put the latest Nougat Resurrection Remix on it. I need to get TWRP going first which I got stuck at trying to flash it.
I was able to get the phone downgraded to 14.1.G.1.534 using flash tool (ver 0.9.24.3). I did this following the guide here https://forum.xda-developers.com/showthread.php?t=2439328.
I was able to root it using Kingoroot.
I was able to unlock the bootloader using flashtool. Using *#*#7378423#*#*, the phone now reports Bootloader Unlocked: yes. See attached screenshot.
The part that I got stuck at is trying to flash TWRP in Fastboot. The command lines and error are below. The main error being "FAILED (remote: Command not allowed)"
I don't have an option in developer's options to "Unlock OEM bootloader". I read some other Xperia users being able to fix this problem by checking this.
I am running Windows 8.1. I am relatively sure that my drivers are correct. I had gotten a "drivers too old" error before in Flashtools but I was able to correct it by reinstalling new drivers.
I tried having debugging checked and unchecked before going into Fastboot and made no difference.
Tried both twrp-2.8.7.0-honami and twrp-3.0.2.0-honami with no success. Tried shortening file name to trp.img with no success.
Tried different 2 different adb files around the web with no success.
I read somewhere someone mentioned briefly that TWRP can be flashed using Flashtools. Is that true? I wasn't able to find a full guide for it.
Any help would be appreciated!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery trp.img
target didn't report max-download-size
sending 'recovery' (13672 KB)...
OKAY [ 0.433s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.439s
Well I was able to get TWRP on there by installing the XY Dual Recovery. The problem with it is that the Resurrection Remix's installation instruction says to use TWRP 3x or higher. TWRP on XY is only at 2.8.7.0. I couldn't find a TWRP 3x flashable zip file for Honami and TWRP wouldn't flash TWRP 3x IMG file I found. Fastboot is still giving me the same Command Not Allowed error.
Any ways, I went ahead and flashed RR with 2.8.7.0. When I tried to flash GAPPs after it says there is insufficient space. I have at least 9GB+ internal storage. So not sure what the deal is there.
I also lost Dual Recovery and root after first RR boot.
Looking into getting re-rooted and reinstalling XY Dual Recovery now.. And then flashing GAPPS after.
Anyone know what the consequences are for installing RR with a lower rev of TWRP?
So the RR Rom does have root but it just doesn't have apps root. Only ADB root. I cant flash the su add on from Lineage's site since I lost recovery. I ended up FTF back to stock and then reflashed everything, the ROM then pico version of GAPPs (pico worked) and then the su addon. The su addon had an error when flashing in TWRP.
Any ways, long story short the whole thing didn't work. Still stuck with RR Without recovery. Su addon didnt work from the flash. And for whatever reason my SIM is not detected and I lost my IMEI in RR. I read that this is a known issue with C6902 but I have the C6903 and I had confirmed this through the service menu before ROM flash. Maybe problems with flashing RR without the latest TWRP.
The Command Not Allowed is still an issue that I dont know how to resolve. So I still can't flash newer version of TWRP.
Any help would be appreciated....
I guess I will try to find a ROM that 's compatible with TWRP 2.8.7.0.
OK! I figured out what the Command Not Allowed problem is!
I've been following the flash guides from a few websites. And they all reference this syntax for flashing TWRP.
Fastboot flash recovery twrp.img.
This syntax didn't work for me. All those websites properly copycat each other.
That syntax is either incorrect or just didnt work for my setup for some reason. I kept searching for ways to flash TWRP and found another website that uses a different syntax. I gave it a go and TWRP flashed right away. This is the syntax that worked for me.
Fastboot flash boot twrp.img
At least that part of the problem is resolved.
Even after flashing RR with TWRP 3.0.20, the SIM/IMEI is still not showing. Recovery is still lost on first boot. Reinstalling TWRP on top of RR causes RR to not boot any more. I will have to look into the RR thread to investigate more.
I will mark this thread as Solved for the Command Not Allowed.
Crossed out everything cause that was not the correct solution. Striked them out to keep them as part of the troubleshooting steps history.
Oops duplicated post.
OK! So it looks like I have to correct myself here on my previous solution.
My solution from earlier for using "Fastboot flash boot twrp.img" is incorrect apparently. Don't use this!
That was the reason why my TWRP was lost after RR boot. The recovery partition comes after the boot and system partition. By flashing the recovery into boot, it screws up the order.
Nevertheless, the Command Not Allowed was still a problem if I tried to use "Fastboot flash recovery twrp.img"
Any ways I was still looking into this problem and started looking into the boot.img stuff and saw someone uses this command line: "fastboot erase boot". This helps someone being able to flash a boot.img when the user was having the Command not Allowed problem trying to flash a different img for the boot partition.
This gave me an idea to try and use "fastboot erase recovery".
I gave it a try and I was able to use "fastboot flash recovery twrp.img" afterwards! It was done in a second.
Then I went through the normal steps of flashing RR and TWRP stayed this time. So now all is good with everything!
Any ways to recap, my full steps used for my RR Installation:
1. Flashtool to flash an Android 5.1.1 stock rom. I used C6903_14.6.A.1.236_1276. (obtained through Flashtool, Xperifirm) Your phone has to run in 5.1.1 for the SIM and IMEI to work in RR. Don't need to flash modem.zip, that's for C6902 only.
2. Fastboot flash erase recovery
3. Fastboot flash recovery twrp.img
4. Follow instructions to flash RR normally.
5. Resize system partition size (for flashing GAPPS micro size or larger).
6. Flash GAPPS.
7. Flash su addon from Lineage's website to allow root for apps and ADB.
I hope this helps someone with similar problems in the future. Thanks to those who stop in to see me ramble to myself about silly stuff
I had the same error message and was able to successfully flash using the phone and the Android Studio Emulator app.
I was already rooted and had an unlocked bootloader.
I tried this solution and it said error: cannot "recovery": No such file or directory LOL even though it's right here and I use it all the time..........I just can't figure it out.
I dirty flashed a new version of xiaomi.eu stable build, and it caused TWRP to uninstall itself.
Whenever I hold power on and volume up it just goes to fastboot.
Now I tried reinstalling TWRP like I've done many times before, but it keeps throwing an error. The error I get is when trying to boot without flashing the img. When I do this, I get the error:
Code:
fastboot boot TWRP.img"
downloading 'boot.img'...
OKAY [ 1.609s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.675s
Anyone gotten any ideas on what could be going on here? I'm scared to try anything as my phone currently works, but I need TWRP back to update my phone to a different versions and to install the clock mod again.
Thanks!
Got it to load once, but now back to square one. Throwing same error.
Now when running the command fastboot reboot recovery it's saying
Code:
fastboot: usage: unknown reboot target recovery
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Try on a computer with a USB 2.0 port, or a different usb cable, had the same issue once
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
I have the same error. How can I fix this pls?
MrkoZino said:
I have the same error. How can I fix this pls?
Click to expand...
Click to collapse
Flash the latest official rom then start all over again. Follow the post above you about miflash.
Hello, I've had the same problem, then flashed latest dev rom via MiFlash and it booted, but now after I flash any custom ROM in TWRP i have this issue again and need to reflash chinese ROM. How can I flash any custom rom?
i'm stuck in the same issue. stuck in fastboot and it would not load recovery. any fix?
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
greendra8 said:
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Click to expand...
Click to collapse
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
DJPlaya said:
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
Click to expand...
Click to collapse
long time ago now. but i remember at one point having to flash the stock firmware using the mi unlock tool. i also remember trying every single version of twrp and rom until one finally worked. sorry i can't help much but i believe that's how i eventually fixed it.
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Marihot said:
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Click to expand...
Click to collapse
Where do you get these .img files?
iconoclasthero said:
Where do you get these .img files?
Click to expand...
Click to collapse
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Marihot said:
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Click to expand...
Click to collapse
Please tell the details for this method
greendra8 said:
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
Click to expand...
Click to collapse
BROOOOOOOOOO HAHAHAHAHAHA I LITERALLY JUST READ YOUR COMMENT AND 10 SECONDS LATER I FLASH THE ROM WITH "CLEAN ALL AND LOCK" Im a f-king dumb bro
Marihot said:
你好，我也经历过同样的事情。
这个方法帮助我摆脱它。
尝试使用 adb 从要在 hh 中安装的 rom 中重新刷新一些文件映像。
将下面的文件从 rom 映像复制到 adb 文件夹
1.system.img（adb >> fastboot flash system system.img中的命令）
2. boot.img（adb 中的命令，如#1，更改 img 文件的名称）直到 #6
3. 供应商.img
4.dtbo.img
5. 自定义.img
6. 杂项.img
7. 现在用adb刷twrp/recovery.img（选择twrp与你要安装的rom兼容）
8. adb 的“fastboot boot recovery.img”
9. twrp刷入rom
Click to expand...
Click to collapse
Thank you, brother
try fastboot set_active a
or fastboot set_active b
Hi everyone,
I've unlocked my mi 9t pro (8gb version) today (purchased from Hong Kong sent to Melbourne/Australia) and tried to flash TWRP. When I finally got into TWRP I deleted everything through advanced wipe (this is probably where I stuffed up). I rebooted and now I'm forever stuck in the fastboot screen.
I can use the cmd fastboot to re-load the twrp.img successfully. If I do that, I hold UP+PWR and it just returns me to fastboot screen. However, when I try to use 'fastboot boot twrp.img' I get the following error;
Code:
downloading 'boot.img'...
OKAY [ 1.398s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.408s
I can't go anywhere from here. I've attempted to use the miflash tool, but it's just throwing errors at me.
Any help here would be great.
If you have any questions, please don't hesitate to ask.
Thanks,
Raddest
raddest said:
Hi everyone,
I've unlocked my mi 9t pro (8gb version) today (purchased from Hong Kong sent to Melbourne/Australia) and tried to flash TWRP. When I finally got into TWRP I deleted everything through advanced wipe (this is probably where I stuffed up). I rebooted and now I'm forever stuck in the fastboot screen.
I can use the cmd fastboot to re-load the twrp.img successfully. If I do that, I hold UP+PWR and it just returns me to fastboot screen. However, when I try to use 'fastboot boot twrp.img' I get the following error;
I can't go anywhere from here. I've attempted to use the miflash tool, but it's just throwing errors at me.
Any help here would be great.
If you have any questions, please don't hesitate to ask.
Thanks,
Raddest
Click to expand...
Click to collapse
Needs flashing images manually from adb
EpickBroVlad said:
Needs flashing images manually from adb
Click to expand...
Click to collapse
I've flashed boot.img logo.img dtbo.img vbmeta.img through fastboot. Haven't done anything through ADB though. Can you give more details please?
edit: I've just tried adb reboot tw.img (tw being the TWRP) and I got this;
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot tw.img
adb server version (32) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found
edit 2: Also worth noting, I'm pretty sure I never enabled USB debugging before all of this...
raddest said:
I've flashed boot.img logo.img dtbo.img vbmeta.img through fastboot. Haven't done anything through ADB though. Can you give more details please?
edit: I've just tried adb reboot tw.img (tw being the TWRP) and I got this;
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot tw.img
adb server version (32) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found
Click to expand...
Click to collapse
I've messed my Mi9t by wiping presist and system partitions and as a cherry on top I've flashed stable of xiaomi.eu miui 11 based on android 10 on beta xiaomi.eu miui 10 based on android 9. Partition table was messed and phone was done... Even miflash didn't helped.
raddest said:
Hi everyone,
I've unlocked my mi 9t pro (8gb version) today (purchased from Hong Kong sent to Melbourne/Australia) and tried to flash TWRP. When I finally got into TWRP I deleted everything through advanced wipe (this is probably where I stuffed up). I rebooted and now I'm forever stuck in the fastboot screen.
I can use the cmd fastboot to re-load the twrp.img successfully. If I do that, I hold UP+PWR and it just returns me to fastboot screen. However, when I try to use 'fastboot boot twrp.img' I get the following error;
Code:
downloading 'boot.img'...
OKAY [ 1.398s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.408s
I can't go anywhere from here. I've attempted to use the miflash tool, but it's just throwing errors at me.
Any help here would be great.
If you have any questions, please don't hesitate to ask.
Thanks,
Raddest
Click to expand...
Click to collapse
If you have access to fastboot then you haven't killed it. You need to use MiFlash and try different official fastboot ROMS until you get the same as it came with (same rom not neccessarily same version number). Make sure you flash using "clean all and flash" and DON'T select lock.
Eventuallly one will work, you may have to try diffent versions of MiFlash and different ROMS but stick with it.
Also put the IMIE from the box it came in, into the Xiaomi authenticator site and if it's in Chinese, stick to chinese roms.
Your phone's only bricked if you can't access fastboot... something I once did to a Mi8 Pro.
reboot on fastboot
download first FASTBOOT ROM for your china version (Miui 10)
download miflash
install this rom throough miflash
regards
pjcarrmole said:
If you have access to fastboot then you haven't killed it. You need to use MiFlash and try different official fastboot ROMS until you get the same as it came with (same rom not neccessarily same version number). Make sure you flash using "clean all and flash" and DON'T select lock.
Eventuallly one will work, you may have to try diffent versions of MiFlash and different ROMS but stick with it.
Also put the IMIE from the box it came in, into the Xiaomi authenticator site and if it's in Chinese, stick to chinese roms.
Your phone's only bricked if you can't access fastboot... something I once did to a Mi8 Pro.
Click to expand...
Click to collapse
Is there any particular version of miflash that will work? When I try to run the latest (MiFlash20181115) I get the messages to 'Please install driver'. I click install, and it gives me errors. I'll attach what I'm seeing. I'll try different versions of miflash.
edit: Ok I've tried a different version of Miflash which doesn't throw driver errors at me when I install it. It can detect my phone in fastboot mode. I guess I need a list of mi 9t pro global fastboot roms. I'm looking for that. I've downloaded miui_RAPHAELGlobal_V10.3.3.0.PFKMIXM_67fb825970_9.0.zip but I'm pretty sure that's a regular ROM. I'm going to google 'mi 9t pro global fastboot rom' and see what I can find. Thanks!
Hopefully this works. Will it re-lock my bootloader if I select 'clean all' only?
raddest said:
Is there any particular version of miflash that will work? When I try to run the latest (MiFlash20181115) I get the messages to 'Please install driver'. I click install, and it gives me errors. I'll attach what I'm seeing. I'll try different versions of miflash.
edit: Ok I've tried a different version of Miflash which doesn't throw driver errors at me when I install it. It can detect my phone in fastboot mode. I guess I need a list of mi 9t pro global fastboot roms. I'm looking for that. I've downloaded miui_RAPHAELGlobal_V10.3.3.0.PFKMIXM_67fb825970_9.0.zip but I'm pretty sure that's a regular ROM. I'm going to google 'mi 9t pro global fastboot rom' and see what I can find. Thanks!
Hopefully this works. Will it re-lock my bootloader if I select 'clean all' only?
Click to expand...
Click to collapse
I'm guessing you may have a China rom if it's an 8gb version and definitely if it's 8gb/256gb. Latest fastboot roms can be found here:
https://xiaomifirmwareupdater.com/miui/raphael/
I'd try the latest of any rom with clean all. DO NOT SELECT CLEAN ALL AND LOCK unless you're sure its' the original rom variant that came with the phone.
PS I have the China rom, debloated and with all google goodness and it's easy to do, if you ever wanted to relock the bootloader in the future for google play.
Probably disable driver signature in Windows or an older version of me flash ( can't recall what i have since my laptop is semi dead ) , and make sure you actually install those drivers ( about 5 of them ) .
SOLVED
Ok, here's the fix that worked for me.
The latest Miflash didn't work, it's the portable version (I think) so it didn't come with the drivers and didn't run. I downloaded the next miflash which was MiFlashSetup_eng.msi. I can't find the download link at the moment, but it was an install package not the .zip with the contents.
Next, I found the global fastboot rom, which was called raphael_eea_global_images_V10.3.1.0.PFKEUXM_20190723.0000.00_9.0_eea_f70f6415ea.tgz (3.2gb).
From fastboot I ran the XiaoMiFlash.exe. I moved the fastboot rom to the same root folder of the flash program. Pointed it to the folder the fastboot rom was in, and clicked flash. Don't forget to select 'clean all' not 'clean all and lock' from the app.
That was it, and it worked. After it flashed everything (took a bit of time) I unlocked my phone again using mi unlock app. Installed TWRP, and DID NOT do advance flash, just left it on the default stuff. Did that, and am now using pixelexperience 9.0.
Again, thanks to everyone for replying, I'll be clicking thanks. I hope this helps anyone else in the same situation as I was. If you need any more information, please don't hesitate to post here.
Thanks,
Raddest
Hey Everyone recently my device got stuck at android one logo and so after analyzing it I understood that it was in a hard brick condition. so I tried the Xiaomi Flash Tool to flash the original firmware but every time it had some kind issues such as
1. cannot Flash Bluetooth_a error
2. FAILED (remote: Error flashing partition : Write Protected)
Can anyone suggest me how can I remove this Write Protection.
earlier build - HavacOS ,bootloader unlocked.
PS- Also tried the oem edl mode but it showed an error programmer file not found using the MiFlashTool (Beta) and with the latest build
3. error cannot read from com3 (read hello packet)
Any suggestions would be appreciated.
How did you brick the phone?
Anyway, can you boot into fastboot?
If yes, try booting into TWRP (fastboot boot twrp.img) and use the fix boot loop command.
Exxdeea said:
How did you brick the phone?
Anyway, can you boot into fastboot?
If yes, try booting into TWRP (fastboot boot twrp.img) and use the fix boot loop command.
Click to expand...
Click to collapse
Yes, I can boot into fastboot! but every time it got stuck at the TWRP splash screen/Logo. tried with different versions too.
Also using ( fastboot flash boot_a twrp.img ) and ( fastboot flash boot_b twrp.img) gives an error of write protected .
And as far as how I bricked- I don't have any idea , it was working fine but then suddenly it stooped responding.
(As things usually happen suddenly. )
This looks like the solution:
https://forum.xda-developers.com/mi-a2/how-to/fix-twrp-freeze-splash-logo-t4065173
Exxdeea said:
This looks like the solution:
https://forum.xda-developers.com/mi-a2/how-to/fix-twrp-freeze-splash-logo-t4065173
Click to expand...
Click to collapse
Thanks for replying but still no hope.
here is another error.
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'cache' (56 KB) FAILED (remote: 'Error: Last flash failed : Write Protected')
fastboot: error: Command failed
Write protected. How can I remove This?
Same Problem
Try using 4pda version which is X.X.X.X-5. That worked for me. Also, try switch slot a/b from fastboot
Pandu Ahbar said:
Same Problem
Click to expand...
Click to collapse
What does "fastboot getvar unlocked" say?
If you are sure that you have previously unlocked phone:
1. maybe try to lock and then unlock again with
fastboot flashing unlock
and
fastboot flashing unlock_critical
2. try to flash stock, forget about miflash, use fastboot from latest platform tools
If you have not unlocked phone before, and have not set "OEM unlock" in Settings -> Developer, and rebooting 7+ times does not switch A/B slots into working ROM, then look into TestPoint/EDL guide.
Death_17 said:
Yes, I can boot into fastboot! but every time it got stuck at the TWRP splash screen/Logo. tried with different versions too.
Also using ( fastboot flash boot_a twrp.img ) and ( fastboot flash boot_b twrp.img) gives an error of write protected .
And as far as how I bricked- I don't have any idea , it was working fine but then suddenly it stooped responding.
(As things usually happen suddenly. )
Click to expand...
Click to collapse
Same problam bro how can i solve i don't know and i also use last time havoc os
have you tried test point method?
Death_17 said:
Yes, I can boot into fastboot! but every time it got stuck at the TWRP splash screen/Logo. tried with different versions too.
Also using ( fastboot flash boot_a twrp.img ) and ( fastboot flash boot_b twrp.img) gives an error of write protected .
And as far as how I bricked- I don't have any idea , it was working fine but then suddenly it stooped responding.
(As things usually happen suddenly. )
Click to expand...
Click to collapse
Aerobatic said:
What does "fastboot getvar unlocked" say?
If you are sure that you have previously unlocked phone:
1. maybe try to lock and then unlock again with
fastboot flashing unlock
and
fastboot flashing unlock_critical
2. try to flash stock, forget about miflash, use fastboot from latest platform tools
If you have not unlocked phone before, and have not set "OEM unlock" in Settings -> Developer, and rebooting 7+ times does not switch A/B slots into working ROM, then look into TestPoint/EDL guide.
Click to expand...
Click to collapse
Vishal656 said:
Same problam bro how can i solve i don't know and i also use last time havoc os
Click to expand...
Click to collapse
have you tried test point method?
Same problem for me write protected error
How to fix it
Death_17 said:
Yes, I can boot into fastboot! but every time it got stuck at the TWRP splash screen/Logo. tried with different versions too.
Also using ( fastboot flash boot_a twrp.img ) and ( fastboot flash boot_b twrp.img) gives an error of write protected .
And as far as how I bricked- I don't have any idea , it was working fine but then suddenly it stooped responding.
(As things usually happen suddenly. )
Click to expand...
Click to collapse
Same problem any suggestions how to fix this
same problem someone give solution
try flashing "super_empty.img" file then install your current ROM through pixel experience recovery
blacksrj531 said:
try flashing "super_empty.img" file then install your current ROM through pixel experience recovery
Click to expand...
Click to collapse
Bro you don,t understand it's write protected