Hi, i' trying to flash persist.img to fix (hopefully) tilted accelerometer but when i try to erase or flash it i get error: FAILED (remote: partition write protected)
I have unlocked bootloader, twrp and root working
i have tried to change /persist permissions to rw-rw-rw but still got that error
what can i do to unlock it and reflash?
if i try to calibrate accelerometer it fails
any idea?
OS: MIUI 8.2.2.0 stable global
thanks
Persist flash failed
devildeva said:
Hi, i' trying to flash persist.img to fix (hopefully) tilted accelerometer but when i try to erase or flash it i get error: FAILED (remote: partition write protected)
I have unlocked bootloader, twrp and root working
i have tried to change /persist permissions to rw-rw-rw but still got that error
what can i do to unlock it and reflash?
if i try to calibrate accelerometer it fails
any idea?
OS: MIUI 8.2.2.0 stable global
thanks
Click to expand...
Click to collapse
Same problem here with my redmi 4x.
Related
Hi XDA guys, so i have this trouble and i don't know what to do, the problem is that my phone get bricked after updating whatsapp and now i can only boot the phone into fastboot an when i try to unlock the bootlader i get this, so help me please!!
Code:
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase userdata fail
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 8.603s
Victor Gtz said:
Hi XDA guys, so i have this trouble and i don't know what to do, the problem is that my phone get bricked after updating whatsapp... [/CODE]
Click to expand...
Click to collapse
Hi, maybe you could give us some more clear infos of what you have done exactly...
Why you want to unlock your bootloader?
Try to reflash an original firmware with RDS and if you want root use "TwerkMyMoto"...
5m00v3 said:
Hi, maybe you could give us some more clear infos of what you have done exactly...
Why you want to unlock your bootloader?
Try to reflash an original firmware with RDS and if you want root use "TwerkMyMoto"...
Click to expand...
Click to collapse
Well mi phone was working fine with stock firmware and locked bootlader, so i recive this whatsapp update and after this installation the phone shut down and get on again but with the boot logo of motorola and get stuck in it, and if i enter in fastboot non of the options work only the phone gets frized, so i was triyin to unlock the bootloader, for a chance to fix the problem with an update via RSD, but when i try to unlock the bootlader it gives me the error as i mention in the first post and i dont know what do
Victor Gtz said:
...so i was triyin to unlock the bootloader, for a chance to fix the problem with an update via RSD...
Click to expand...
Click to collapse
you dont need to unlock the bootloader to reflash your original firmware via RSD-Lite!
Follow this to install stock rom: http://forum.xda-developers.com/showthread.php?t=2643779
I got yesterday also an Update-Information from whatsapp. I will NOT install until it is confirmed as non-bricking. Thx for your info/warning!
5m00v3 said:
you dont need to unlock the bootloader to reflash your original firmware via RSD-Lite!
Follow this to install stock rom: http://forum.xda-developers.com/showthread.php?t=2643779
I got yesterday also an Update-Information from whatsapp. I will NOT install until it is confirmed as non-bricking. Thx for your info/warning!
Click to expand...
Click to collapse
i Just try using RDS Lite but in the step 4 the reboot never boot and the flash fail
Can you enter recovery? Selecting it in the fastboot menu, what happens? In RSD does it flashes and only in the reboot portion it fails? Did you try to turn it on without the external SD card?
As far as i can tell the device is trying to use the linux discard command, it seems like a wipe that gone wrong.
regnotp synagogue
thiagomtl said:
Can you enter recovery? Selecting it in the fastboot menu, what happens? In RSD does it flashes and only in the reboot portion it fails? Did you try to turn it on without the external SD card?
As far as i can tell the device is trying to use the linux discard command, it seems like a wipe that gone wrong.
Click to expand...
Click to collapse
Hi thiagomtl let me answer your questions, when i try to enter in recovery the phone gets stuck again with the motorola boot logo and after a while returns to fastboot mode, and when i try to flash whit RSD in the step 4 that is reboot, on the phone stays a command that says Rebooting Droidboot and nothing happens, and yeah when i do this operaions i always remove the sim card and the sd card , so if you now something ill appreciate a lot it!!
Try those in fastboot:
fastboot erase data
fastboot erase cache
After try RSD again.
5m00v3 said:
you dont need to unlock the bootloader to reflash your original firmware via RSD-Lite!
Follow this to install stock rom: http://forum.xda-developers.com/showthread.php?t=2643779
Click to expand...
Click to collapse
Are you sure about that ?
For original firmware there is no need to unlock
thiagomtl said:
Try those in fastboot:
fastboot erase data
fastboot erase cache
After try RSD again.
Click to expand...
Click to collapse
I already do that but im still getting this error
BLKDISCARD ioctl /dev/block/mmcblk0 fail
I am guessing that is an error in the emmc, the problem is that i don't know how to fix it
Victor, I'm having the exact same problem. Did you find any solution?
I'm having the exact same problem!!
What I did was that when it gets stuck waiting for reboot I did reboot it manually into fastboot mode again and process continues. The problem is that it gets stuck again when flashing the system partition. Bootloader won't let me erase the partition nor flash it.
Tried unlocking the bootloader and:
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase userdata fail
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 9.666s
Is there a way to know the original provider of the phone, to make sure I'm using the correct firmware?
ismael_mj23 said:
I'm having the exact same problem!!
What I did was that when it gets stuck waiting for reboot I did reboot it manually into fastboot mode again and process continues. The problem is that it gets stuck again when flashing the system partition. Bootloader won't let me erase the partition nor flash it.
Tried unlocking the bootloader and:
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase userdata fail
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 9.666s
Is there a way to know the original provider of the phone, to make sure I'm using the correct firmware?
Click to expand...
Click to collapse
You got a serious bug. There is a huge change your device is now broken beyond repair, i hope not. But can u access the recovery partition? Can u flash a custom boot image?
Hazou said:
You got a serious bug. There is a huge change your device is now broken beyond repair, i hope not. But can u access the recovery partition? Can u flash a custom boot image?
Click to expand...
Click to collapse
I also having the same problem after force power on/off when hang during TWRP format. Now the unit in hard brick. If able to force temporary boot into recovery using ram instead of rom, might have some hope. But it looks like no way to boot from ram. :crying:
same prob as victor gtz
fsd lite freezes at step 4, unlock bootloader doesnt work and so on and so forth, so anybody got a clue what to do?
Dudes
Same problem here, rsdlite didnt work for me and the bootloader cant be unlocked with the same error message. Theres any way to solve this? i read once that you can recover the android from the dead even if the boot isnt working, maybe thats not true at all.....
Neyzik said:
Dudes
Same problem here, rsdlite didnt work for me and the bootloader cant be unlocked with the same error message. Theres any way to solve this? i read once that you can recover the android from the dead even if the boot isnt working, maybe thats not true at all.....
Click to expand...
Click to collapse
It's true, but not for all devices. And if u have the above, the nand memory is broken. That can only be repaired by some kind of powercycle on chip level or anything.
Right.
So, I was opening youtube on the last version of CM 12.1. No xposed, stock kernel, XT1068 model, when all of a sudden the phone stopped working.
Youtube wasn't opening. The phone was stuck on the home screen, all I could do was just press the home/back/recent buttons. Even long pressing power button to reboot would just take me to the power menu but Wouldn't allow me to do anything.
So in the end I long pressed the power menu to force reboot the phone aaaand... stuck on the boot logo. Not on the bootanimation, on the Motorola Bootlogo.
Managed to get to fastboot mode, tried to go to recovery, but after the twrp splash screen It would reboot to the splash screen again.
So i decided to mfastboot the original firmware. Who knows? maybe something got corrupted on cm.
Now, mfastboot is giving me weird errors.
flash partition gpt.bin gives (bootloader) Preflash validation failed
flash motoboot motoboot.bin gives FAILED (data transfer failure (Unknown error))
flash boot boot.img freezes everything and i need to reboot it to try and get to fastboot again.
Anybody knows what I should do? I'm kinda desperate here...
Thanks in advance. Peace.
(by the way, latest motorola drivers, just so you know...)
EDIT. Also, on the phone, it says
"hab check failed for primary_gpt
Failed to verify hab image primary_gpt"
Hope I can help
Are you flashing a gpt.bin from a previous android version? You cannot downgrade gpt.bin or motoboot.bin so the error is normal. From what firmware version is the boot.img you are flashing from? Try downloading this twrp recovery img from here https://dl.twrp.me/titan and
Code:
fastboot flash recovery recovery.img
or
Code:
mfastboot flash recovery recovery.img
Then you can try flashing any rom like this AOSP one http://forum.xda-developers.com/moto-g-2014/development/rom-android-source-project-t3123109
Hope this helps. I understand how hard it is to have a phone that won't boot.
Maybe you should try to place the stock rom 4.4.4 and then upgrade to 5.0, with 4.4.4 rom the GPT will have a downgrade and then you update the GPT putting 5.0
LudwigFerdinand18 said:
Maybe you should try to place the stock rom 4.4.4 and then upgrade to 5.0, with 4.4.4 rom the GPT will have a downgrade and then you update the GPT putting 5.0
Click to expand...
Click to collapse
You cannot downgrade gpt
Well I somehow managed to reboot into recovery, but the great problem here is that it won't mount \data.
Now, maybe all I need is to reformat \data cause it got corrupted, but since TWRP won't mount it, I can't do much about it.
I found on another thread this command
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Which apparently formats the data partition of a phone. I suppose I'd have to change "ext4fs" into "f2fs", but I'm too scared to actually try it out.
Also because I don't know whether mmcblk0p8 is the right block for our data partition.
Jeez, I hate this.
Thanks for your help guys, but I don't think flashing recovery again would help. Nor downgrading, but I'll think about it.
EDIT.
Magic, just magic. After hours of tinkering I did EXACTLY THE SAME THINGS and now it's working. Restored the stock Rom and I'm off to install CM again.
Sorry guys and thanks so much!!!
My mi 8se is unlocked and twrp is installed the before.
My phone stuck at fastboot after update,
neither miflash or flashing twrp is worked.
miflash shows error message “ error:FAILED (remote: Check device console.)”
flashing twrp or boot image are failed.
shows the message FAILED( remote: Error flashing partition : Device Error )
I need help to solve this issue.
solved
problem solved by flashing system.img and boot.img.
however twrp cannot be flashed, still return error message in miui 11.0.2.0 china rom.
I have the same problem with Mi8 SE
hello i'm desperate The same thing happened to me when updating android 11.0.2 China. I tried flashing system and boot (are they come in android rom fastboot type?) but I get the error in CMD
“FAILED <remote: Error flashing partition“: write Protected>
I have the bootloader unlocked. hope help me please
Hi everybody
Tried to install a custom rom on my device and it has turned out to be a disaster. I'm completely stuck and have no idea what to do next. Tried everything i could find but i keep having the following problem.
Device: mi k20 davinci
Bootloader: unlocked
TWRP file: twrp-3.3.1-0-davinci.img
ROM: davinci_global_images_V11.0.4.0.QFJMIXM_20200117.0000.00_10.0_global_4c094d085a
TWRP had been succesfully installed but i broke it somehow and now i'm back in the fastboot mode. When trying to re-flash and boot twrp i recieve the following error:
"FAILED (remote: Failed to load/authenticate boot image: Load Error)"
If i try to flash the stock ROM with the miflash tool i receive the error
"Antirollback check error" "error"
if possible i just want to go back to stock and forget about this for now
Post it in K20 and not K20 Pro section.
I didn't know K20 had antirollback protection. Maybe try to flash a newer miui version, maybe a beta ?
Have you also tried "fastboot boot twrp.img" ?
oldbait said:
Hi everybody
Tried to install a custom rom on my device and it has turned out to be a disaster. I'm completely stuck and have no idea what to do next. Tried everything i could find but i keep having the following problem.
Device: mi k20 davinci
Bootloader: unlocked
TWRP file: twrp-3.3.1-0-davinci.img
ROM: davinci_global_images_V11.0.4.0.QFJMIXM_20200117.0000.00_10.0_global_4c094d085a
TWRP had been succesfully installed but i broke it somehow and now i'm back in the fastboot mode. When trying to re-flash and boot twrp i recieve the following error:
"FAILED (remote: Failed to load/authenticate boot image: Load Error)"
If i try to flash the stock ROM with the miflash tool i receive the error
"Antirollback check error" "error"
if possible i just want to go back to stock and forget about this for now
Click to expand...
Click to collapse
Flash Fastboot ROM through Command Prompt. https://in.c.mi.com/thread-334-1-1.html?t=1586384142148
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