Hi,
So, I'm a bit new to this device and also helping a friend so not sure what actually caused this, but here is the issue I am having.
Whenever I turn on the phone, it boots only to fastboot mode. This is also true whenever plugging the charger to the phone.
Bootloader is still locked, and trying to flash stock rom using pc tool or fastboot shows that it is successful but has no effect. I've tried this multiple times.
I could boot directly to twrp, using fastboot boot and twrp shows that it can't mount any internal partition.
Issuing df command from twrp shows no partition other than tmpfs. Mount shows similar output, with the addition of recovery partitions.
Anything I could do about this phone?
Bootloader never locks in mi4i.
Try flashing TWRP instead of just booting into it
use
fastboot flash recovery twrp.img
After flashing, allow modifications
and repair file system for system and data partitions to ext4 from wipe menu
madhurajkumar said:
Bootloader never locks in mi4i.
Try flashing TWRP instead of just booting into it
use
fastboot flash recovery twrp.img
After flashing, allow modifications
and repair file system for system and data partitions to ext4 from wipe menu
Click to expand...
Click to collapse
Well, when I check in fastboot oem device-info
Device unlocked is false.
Doesn't that mean it's bootloader is locked?
Also I did tried flashing TWRP, but it won't stick. After reboot the modification just seems gone.
Mi4i bootloader is unlocked by default as far I knew. Did you try
fastboot oem unlock
to unlock it?
Did repair file system not work when you tried it from twrp?
Related
Long story short I bricked my phone when trying to flash recovery using toolkit. Now my phone won't turn on and recovery is gone as well. Somehow my PC can recognize the phone in fastboot mode although there's nothing showing on the screen.
So I tried the method in this thread:
http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696
It shows I flashed everything and it shows green color in the tool but when I checked the partitions, boot.img, recovery.img, userdata.img, system.img, etc are still broken. At that time the bootloader was still unlocked.
Since my computer can still see the phone in fastboot so I tried to flash the original image in fastboot. Again everything went through with no error but the phone still wouldn't turn on and the partitions are still same broken/corrupted. However the bootloader became locked after this. So now I end up with no more solutions. Since bootloader says locked(although boot.img is actually corrupted) I can't flash or do anything in fastboot command.
So I guess I'm really SOL right now... My only hope right now is maybe there will be USB JTAG or Nand flasher but I don't know if anyone can repair that right now.
Any suggestions?
fastboot oem unlock
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase recovery
Now use twrp or cwm or whatever
fastboot boot recovery nameofrecovery.img
If your phone boots to recovery you may consider running e2fsck against data and cache partitions through adb shell
Best of luck
I unlocked my phone's bootloader and immediately flashed TWRP using Google's fastboot after that. I got a size mismatch warning in the fastboot screen but I assumed it was normal. I was planning on installing CM, but the system partition remained empty after "flashing" both the ROM and the GAPPS, even though there were no read/write errors in the recovery's log. As a result, the phone keeps booting into recovery, and the same thing happens with CWM. It's like the recovery thinks it is modifying the system partition but it in reality it is not. Maybe it has to do something with SELinux? Any ideas on how to fix this?
Update: I am able to flash stock and boot into it normally, but trying to flash anything in TWRP (even just SuperSU) will make the phone boot into recovery when turned on or rebooted normally.
Update: Flashing the stock boot.img in mfastboot after flashing anything in TWRP will make the phone boot into the system normally, but this workaround doesn't apply to CM12 installs, as it gets caught in a never-ending boot animation (at least more than 10 minutes), with what appears to be a moving/flickering line on screen (which has been reported before). My suspicion is that somehow the recovery is making a change to the boot partition when it shouldn't. SuperSU can be installed using this workaround, but not CM12.
Flashing the stock boot.img to the boot partition seems to not work anymore, it always boots into recovery no matter what's installed in there now. Now I have to do a fastboot boot boot.img every single time I reboot my phone, which doesn't make any sense at all for me if the stock boot.img is already in the boot partition. Somehow the recovery has a higher boot priority than the system?
DanielEGVi said:
Flashing the stock boot.img to the boot partition seems to not work anymore, it always boots into recovery no matter what's installed in there now. Now I have to do a fastboot boot boot.img every single time I reboot my phone, which doesn't make any sense at all for me if the stock boot.img is already in the boot partition. Somehow the recovery has a higher boot priority than the system?
Click to expand...
Click to collapse
Hi,
Running the following command in fastboot should fix the problem.
Code:
fastboot oem fb_mode_clear
Or the distributed boot / system / data (rom) for restoration?
I figured to HTCDEV unlock to allow fastboot to write to recovery
and then fastboot boot twrp to backup whats there before overlaying it.
why not try it?
https://forum.xda-developers.com/showthread.php?t=2798853
fuzzynco said:
Or the distributed boot / system / data (rom) for restoration?
I figured to HTCDEV unlock to allow fastboot to write to recovery
and then fastboot boot twrp to backup whats there before overlaying it.
Click to expand...
Click to collapse
Yes.
Captain_Throwback said:
One thing to note is that you CAN fastboot boot TWRP on this device, so if you don't want to overwrite stock recovery, you don't have to
Click to expand...
Click to collapse
Just make sure to do that from the bootloader menu, not the download mode. Download didn't work for me, command line in Windows was stuck on booting and the download mode said finished flashing, that's it. Once rebooted to the bootloader menu everything was fine. That's how I backed my original recovery as well. You'll probably need to unlock the bootloader on htcdev first though, at least that's what I did.
BolecDST said:
Just make sure to do that from the bootloader menu, not the download mode. Download didn't work for me, command line in Windows was stuck on booting and the download mode said finished flashing, that's it. Once rebooted to the bootloader menu everything was fine. That's how I backed my original recovery as well. You'll probably need to unlock the bootloader on htcdev first though, at least that's what I did.
Click to expand...
Click to collapse
Yes, I figured that, (htcdev.com bootloader unlock).
Thanks for the pointer, I really don't know which mode is for what ...
I think bootloader mode is for direct fastboot flashing
fastboot flash <partition> <file>
or fastboot boot <file>
and download mode & RUU mode is for things packaged
like an RUU. fastboot flash zip <file>
fastboot oem <--->
fuzzynco said:
Yes, I figured that, (htcdev.com bootloader unlock).
Thanks for the pointer, I really don't know which mode is for what ...
I think bootloader mode is for direct fastboot flashing
fastboot flash <partition> <file>
or fastboot boot <file>
and download mode & RUU mode is for things packaged
like an RUU. fastboot flash zip <file>
fastboot oem <--->
Click to expand...
Click to collapse
Recovery is to be flashed in download mode as has been on the HTC 10 the case. In fact download mode can be viewed at as fastboot mode of the phone.
Sent from my htc_pmeuhl using XDA Labs
Left a note here.
My first-batch U11 can be booted to twrp with "fastboot boot twrp-blahblah.img" under bootloader menu (I wish I didn't remember it wrong)
But it can't be done after it came back from repair (no power issue with unknown reason), which motherboard had been replaced and updated to Oreo already.
Anyway, it seems that stock-recovery backup is not required since there's reliable source of stock-recovery which inside the OTA file.
In devlopemed options there no OEM Unlock how to fix it Lenovo A5000
Does it have fastboot mode? Some Mediatek devices do not allow unlock bootloader, but you still be able to flash the boot, system, userdata and cache partitions in fastboot mode.
segfaulto said:
Does it have fastboot mode? Some Mediatek devices do not allow unlock bootloader, but you still be able to flash the boot, system, userdata and cache partitions in fastboot mode.
Click to expand...
Click to collapse
Yes, it's unfortunate that so many devices hide OEM unlocking. I fell victim to this annoying issue when trying to root my ANDR11/OneUI3.1 SAMSUNG a102u device. Unable to fix the problem and root the device.
segfaulto said:
Does it have fastboot mode? Some Mediatek devices do not allow unlock bootloader, but you still be able to flash the boot, system, userdata and cache partitions in fastboot mode.
Click to expand...
Click to collapse
yea it can run in to fastboot
also xiaomi redmi 3 pro
mi unlock say "conect to internet and try again"
whjyu
segfaulto said:
Does it have fastboot mode? Some Mediatek devices do not allow unlock bootloader, but you still be able to flash the boot, system, userdata and cache partitions in fastboot mode.
Click to expand...
Click to collapse
when i try to flash twrp it say its blocked
yarik303 said:
when i try to flash twrp it say its blocked
Click to expand...
Click to collapse
Some devices not allow flash recovery partition with bootloader locked, but since you can flash boot partition with locked bootloader then you can make a script to run on boot time to flash the recovery (I did it to fix a bootloop on my Lenovo tab and worked) or if your device is rooted you can flash recovery using terminal emulator, there is a program called SP Flash Tools, this is the program to flash Mediatek devices you can try it too.
Also, did you try run this command on fastboot mode:
fastboot oem unlock
or
fastboot flashing unlock
segfaulto said:
Also, did you try run this command on fastboot mode:
fastboot oem unlock
or
fastboot flashing unlock
Click to expand...
Click to collapse
fastboot flashing unlock = Failed (remote: unlnown command)
fastboot oem unlock = okay
fastboot flash recovery recovery.img = Failed (remote: download for partition 'recovery' is not allowed)
segfaulto said:
Some devices not allow flash recovery partition with bootloader locked, but since you can flash boot partition with locked bootloader then you can make a script to run on boot time to flash the recovery (I did it to fix a bootloop on my Lenovo tab and worked) or if your device is rooted you can flash recovery using terminal emulator, there is a program called SP Flash Tools, this is the program to flash Mediatek devices you can try it too.
Click to expand...
Click to collapse
SP Flash Tool = just dont flash in fastboot or in normal mode
also i have now on lenovo android system recovery 3e can i install twrp from that?
segfaulto said:
Some devices not allow flash recovery partition with bootloader locked, but since you can flash boot partition with locked bootloader then you can make a script to run on boot time to flash the recovery (I did it to fix a bootloop on my Lenovo tab and worked) or if your device is rooted you can flash recovery using terminal emulator, there is a program called SP Flash Tools, this is the program to flash Mediatek devices you can try it too.
Click to expand...
Click to collapse
i get root on it
GUYS I FIXED
1. A OEM UNLOCK IS NOT AN OPTION IN LENOVO A5000
2.I FLASHED TWRP BY FLASHR OR JUST BY ROOT
THEME CLOSED
Can you give me instructions exactly how you did it? I have tablet A7600H also has no OEM unlocking option
Merry Christmas guys,
I have a really unusual situation.
First time that I have tried all tricks I know and I can't get myself out of this difficult situation.
I was trying to update Magisk with a patched boot file and after a reboot I was not being able anymore to access the system but only this black screen with the Crashdump Mode is appearing.
I can access the Fastboot screen, but no way to reboot to the TWRP recovery or to flash another boot.img, even through some pc flashing utilities.
Is there anything to try through another slot or something else?
I also tried:
fastboot flash boot_a boot.img
and I get this error:
FAILED (remote: Flashing is not allowed for Critical Partitions)
But my bootloader is unlocked and other commands like fastboot reboot works normally.
After I flashed through fastboot the images of boot, abl, dtbo, fw I can only access the TWRP recovery where everything is decrypted.
Any other ideas?
Try booting temporary into TWRP by using this command
fastboot boot twrp.img
If you can't use MSMDownloadTool