Greetings. I'm using a Xiaomi Mi A3 (laurel-sprout). It's been not so easy to unlock the bootloader, but once done, I just can't bootthe recovery using the command fastboot boot twrp.img Booting FAILED (remote: 'unknown command') fastboot: error: Command failed I have double checked that I'm not in fastbootD and that my bootloader is unlocked. What could be the case?
manolius148 said:
Greetings. I'm using a Xiaomi Mi A3 (laurel-sprout). It's been not so easy to unlock the bootloader, but once done, I just can't bootthe recovery using the command fastboot boot twrp.img Booting FAILED (remote: 'unknown command') fastboot: error: Command failed I have double checked that I'm not in fastbootD and that my bootloader is unlocked. What could be the case?
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...omi-mi-a3-laurel_sprout.3987759/post-80625495
NOSS8 said:
https://forum.xda-developers.com/t/...omi-mi-a3-laurel_sprout.3987759/post-80625495
Click to expand...
Click to collapse
Thank you so much for your answer. By doing this, I get no error (in fact, I'm flashing it before) but anyway twrp does never boot. I have even tried the command ./fastboot reboot recovery to no avail.
So far, it's been impossible to set the TWRP up.
manolius148 said:
Thank you so much for your answer. By doing this, I get no error (in fact, I'm flashing it before) but anyway twrp does never boot. I have even tried the command ./fastboot reboot recovery to no avail.
So far, it's been impossible to set the TWRP up.
Click to expand...
Click to collapse
"fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)"
Did you do this?
NOSS8 said:
"fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)"
Did you do this?
Click to expand...
Click to collapse
Of course, that was my first attempt
manolius148 said:
Of course, that was my first attempt
Click to expand...
Click to collapse
I don't have this device so difficult to help you more, post your problem on the TWRP Thread.
Could be an active partition problem.
Related
Hello everyone, this is my first post on the forum.
I have a xiaomi redmi note 4 snapdragon with bootloader unlocked and when I try to install TWRP by ADB it installs it, but when I put the command "flashboot boot twrp.img" it stays in the fastboot logo.
Try using power and volume + to enter the recovery, but enter the original recovery
Can anyone help me? Thank you
Merli- said:
Hello everyone, this is my first post on the forum.
I have a xiaomi redmi note 4 snapdragon with bootloader unlocked and when I try to install TWRP by ADB it installs it, but when I put the command "flashboot boot twrp.img" it stays in the fastboot logo.
Try using power and volume + to enter the recovery, but enter the original recovery
Can anyone help me? Thank you
Click to expand...
Click to collapse
Which output do you get in ADB after you type in the command?
Merli- said:
Hello everyone, this is my first post on the forum.
I have a xiaomi redmi note 4 snapdragon with bootloader unlocked and when I try to install TWRP by ADB it installs it, but when I put the command "flashboot boot twrp.img" it stays in the fastboot logo.
Try using power and volume + to enter the recovery, but enter the original recovery
Can anyone help me? Thank you
Click to expand...
Click to collapse
Could be possible due to old drivers.
Try these platform tools
https://drive.google.com/file/d/13Sjej5zIJPm_yiJQOVR4rEocwbhDc9oh/view?usp=drivesdk
Noter2017 said:
Which output do you get in ADB after you type in the command?
Click to expand...
Click to collapse
downloading 'boot.img'...
OKAY [ 0.792s]
booting...
OKAY [ 0.558s]
finished. total time: 1.353s
After that, it disconnects from the PC and stays in the fastboot logo
MyNameIsRage said:
Could be possible due to old drivers.
Try these platform tools
Try and it does not work, the same thing happens :S
Click to expand...
Click to collapse
MyNameIsRage said:
Could be possible due to old drivers.
Try these platform tools
Click to expand...
Click to collapse
Try and it does not work, the same thing happens :S
Merli- said:
Try and it does not work, the same thing happens :S
Click to expand...
Click to collapse
What process do you follow?
I happened to do it, by copying the recovery file inside the platform tools folder.
Then inside the folder hold shift and right click. It will show an option to open command prompt window or open powershell window here. From there i wrote the commands, fastboot flash recovery recovery.img , and then manually booted to twrp by holding the vol up and power
MyNameIsRage said:
What process do you follow?
I happened to do it, by copying the recovery file inside the platform tools folder.
Then inside the folder hold shift and right click. It will show an option to open command prompt window or open powershell window here. From there i wrote the commands, fastboot flash recovery recovery.img , and then manually booted to twrp by holding the vol up and power
Click to expand...
Click to collapse
I followed that process and it did not work, try two different versions of Twrp and it still did not work. I resigne myself, and try to install the RedWolf recovery with the same process, and this time it works! :fingers-crossed: I could finally install another rom. Thanks for the help
Same problem here, really strange. First time I've this kind of problem.
Edit : Ok, problem solved. There is 2 things to do in addition of the main installation process (found here : https://wiki.lineageos.org/devices/mido/install#installing-a-custom-recovery-using-fastboot )
Firstly, you have to enable OEM Unlocking in Developer option menu. And not only enable USB Debugging. To enable it, click twice on the button "OEM Unlock" (if you click once, it will disable automatically when exiting Dev' menu).
Secondly, once you ran
Code:
fastboot flash recovery twrp-x.x.x-x-mido.img
, you also have to ran
Code:
fastboot boot twrp-x.x.x-x-mido.img
in order to reboot in recovery mode. Otherwise default recovery will automatically erase and replace TWRP.
These 2 steps are quite never documented, but are mandatory for Mido (Redmi Note 4) !!
Skip88 said:
Same problem here, really strange. First time I've this kind of problem.
Click to expand...
Click to collapse
In my case the problem appeared since repair and replace the screen. The unique twrp I could install from ADB was twrp RedWolf
Merli- said:
In my case the problem appeared since repair and replace the screen. The unique twrp I could install from ADB was twrp RedWolf
Click to expand...
Click to collapse
I've edited my post. There is 2 missing steps to be able to install TWRP correctly (then LineageOS^^).
thanks a lot u r a lifesaver.....
Skip88 said:
Same problem here, really strange. First time I've this kind of problem.
Edit : Ok, problem solved. There is 2 things to do in addition of the main installation process (found here : https://wiki.lineageos.org/devices/mido/install#installing-a-custom-recovery-using-fastboot )
Firstly, you have to enable OEM Unlocking in Developer option menu. And not only enable USB Debugging. To enable it, click twice on the button "OEM Unlock" (if you click once, it will disable automatically when exiting Dev' menu).
Secondly, once you ran
Code:
fastboot flash recovery twrp-x.x.x-x-mido.img
, you also have to ran
Code:
fastboot boot twrp-x.x.x-x-mido.img
in order to reboot in recovery mode. Otherwise default recovery will automatically erase and replace TWRP.
These 2 steps are quite never documented, but are mandatory for Mido (Redmi Note 4) !!
Click to expand...
Click to collapse
Thanks a lot u r a lifesaver.....trying it since last 2 days...now finally it worked after i followed ur above mentioned steps...now i just to wait to see if it isnt in bootloop and then i ll check my root status....thanks
Hello, i have my phone Huawei P20 Lite wich is bricked with Phone Locked and FRP lock. I tried to write recovery with fastboot but always receive 'Command not allowed'. It's because my bootloader isn't unlocked...
when i want to power on it's stuck on 'Attention! Please install the update again'
If anyone know how to solve that, please leave an answer there!
orpheum123 said:
Hello, i have my phone Huawei P20 Lite wich is bricked with Phone Locked and FRP lock. I tried to write recovery with fastboot but always receive 'Command not allowed'. It's because my bootloader isn't unlocked...
when i want to power on it's stuck on 'Attention! Please install the update again'
If anyone know how to solve that, please leave an answer there!
Click to expand...
Click to collapse
Hi there
Have you tried to go to eRecovery through power on and Volume+ buttons?
Yes
ars_chelsea said:
Hi there
Have you tried to go to eRecovery through power on and Volume+ buttons?
Click to expand...
Click to collapse
yes, but is stucked on Huawei logo..
orpheum123 said:
yes, but is stucked on Huawei logo..
Click to expand...
Click to collapse
Hallo there
Ok! So you can't really have an unlock code? Cause that would help a lot more... Anyway as for now from all cases I have seen you are telling me this is the hardest one. Altough there is one more chance that you should try.
If you have the stock recovery .img or a TWRP recovery .img you might be able to boot to it and do a hard reset which fixes your issue.
First download the adb tools from here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Then extract it to a random folder.
After you have the stock or TWRP recovery .img just copy it to this folder and open it.
If you don't have the stock recovery, I have a link to it here:
https://mega.nz/#!SR9RzKST!dhXS0yC-p_SvWu-SYYLaop1aRFzSulLVrnSXCVVJiGI
Then press shift + right click on the mouse, it should show an option called "Open a Powershell Window here in case you have Windows 10, or "Open a CMD window here" (on windows 8 and below) click that and a window will appear.
Next, if you are on windows 10 and the window says Windows Powershell type ".\fastboot boot imagenamehere.img" if not and you are on Windows 8 or below type "fastboot boot imagenamehere.img".
Where "imagenamehere" is your image name such as recovery.img or twrp.img or usually on this stock recovery recovery_ramdisk.img.
It should boot into recovery
That way you can factory reset if on stock recovery of course.
Either way you gotta lose all your data right now, there's just no way around it without losing data.
Cheers and best of hopes,
AS
ars_chelsea said:
Hallo there
Ok! So you can't really have an unlock code? Cause that would help a lot more... Anyway as for now from all cases I have seen you are telling me this is the hardest one. Altough there is one more chance that you should try.
If you have the stock recovery .img or a TWRP recovery .img you might be able to boot to it and do a hard reset which fixes your issue.
First download the adb tools from here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Then extract it to a random folder.
After you have the stock or TWRP recovery .img just copy it to this folder and open it.
If you don't have the stock recovery, I have a link to it here:
https://mega.nz/#!SR9RzKST!dhXS0yC-p_SvWu-SYYLaop1aRFzSulLVrnSXCVVJiGI
Then press shift + right click on the mouse, it should show an option called "Open a Powershell Window here in case you have Windows 10, or "Open a CMD window here" (on windows 8 and below) click that and a window will appear.
Next, if you are on windows 10 and the window says Windows Powershell type ".\fastboot boot imagenamehere.img" if not and you are on Windows 8 or below type "fastboot boot imagenamehere.img".
Where "imagenamehere" is your image name such as recovery.img or twrp.img or usually on this stock recovery recovery_ramdisk.img.
It should boot into recovery
That way you can factory reset if on stock recovery of course.
Either way you gotta lose all your data right now, there's just no way around it without losing data.
Cheers and best of hopes,
AS
Click to expand...
Click to collapse
will not work, because:
"downloading 'boot.img'...
OKAY [ 0.487s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.510s"
bootloader are locked, cant do anything!!
Arnys said:
will not work, because:
"downloading 'boot.img'...
OKAY [ 0.487s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.510s"
bootloader are locked, cant do anything!!
Click to expand...
Click to collapse
Yeah you are right, my bad :/
I have a simple one, have you tried "fastboot reboot recovery" via the same command line as well? I know it's obvious but that should work for you...
If it doesn't please send me the error code.
Cheers,
AS
I'm also having almost the same issue. My p20 lite is locked to Japan AU network and frp lock but it's not bricked. I want to use it here in Philippines that's why I'm planning to install a stock rom which will work here. Can you help me?
Hello, I have the exact same problem the guy above has, and I tried "Fastboot reboot recovery" and it still didn't work, I believe because of my cellphone. Do you have any more advice?
contact me i will try help
Hi kikson112!
If You are able to help in such problem I would like to ask You for help as well.
My case look similar.
My P20 lite with no reason (nothing I know) got locked . the screen is black and when I try to unlock it shows only time and weather in uper right corner. It looks like it would stuck in flipcover mode but I never had one.
I tried to reset it , reboot it but nothing help.
I tried to connect by Hisuite to download My data but it is not in debugg mode so I cannot connect.
During reset it looks like it is not loading the system.
When I connect my bluetooth headset it connects.
It is playing the alarm in the morning.
But I cannot do anything. The screen does not respond.
Any ideas what could I try to get My data would be apprieciate.
Hi kikson112!
If You are able to help in such problem I would like to ask You for help as well.
My case look similar.
My P20 lite with no reason (nothing I know) got locked . the screen is black and when I try to unlock it shows only time and weather in uper right corner. It looks like it would stuck in flipcover mode but I never had one.
I tried to reset it , reboot it but nothing help.
I tried to connect by Hisuite to download My data but it is not in debugg mode so I cannot connect.
During reset it looks like it is not loading the system.
When I connect my bluetooth headset it connects.
It is playing the alarm in the morning.
But I cannot do anything. The screen does not respond.
Any ideas what could I try to get My data would be apprieciate.
Click to expand...
Click to collapse
hi, for rescue data use converter to connect a mouse in usb port should work, in this case posible digitizer can be just broken, try download software math to ur phone and write it over sd card by 3 buttons (vol - vol + pwr) and post here if any changes
Umm, you can try to get Huawei to do it or youcan buy an unlock key to flash the stuff.
I think there is a special Huawei Flash mode but I don't remember how to access it anymore because I was a Huawei employee and I knew how before but I forgot. Sorry!
hi all, i have the same problem...Huawei logo...
I connect the mobile phone to the PC, press volume - and power and enter "Fastboot & Rescue Mode".
Phone locked
FRP lock
I try to give the command from the terminal, fastboot boot recovery_ramdisk.img, and I have the following messages:
F: \ P20 \ platform-tools_r29.0.5-windows \ platform-tools> fastboot boot recovery_ramd
isk.img
<waiting for any device>
Sending 'boot.img' (32768 KB) OKAY [0.963s]
Booting FAILED (remote: 'Command not
allowed ')
fastboot: error: Command failed
Then try Volume+ buttons, but it restarts showing the initial logo, without going to eRecovery
hi all, i have the same problem...Huawei logo...
I connect the mobile phone to the PC, press volume - and power and enter "Fastboot & Rescue Mode".
Phone locked
FRP lock
I try to give the command from the terminal, fastboot boot recovery_ramdisk.img, and I have the following messages:
F: \ P20 \ platform-tools_r29.0.5-windows \ platform-tools> fastboot boot recovery_ramd
isk.img
<waiting for any device>
Sending 'boot.img' (32768 KB) OKAY [0.963s]
Booting FAILED (remote: 'Command not
allowed ')
fastboot: error: Command failed
Then try Volume+ buttons, but it restarts showing the initial logo, without going to eRecovery
Click to expand...
Click to collapse
is fastboot working and upgrade mode ?
Hi,
My ANE-LX1 seems to be stuck in a bootloop.
I was trying to install lineageos 16 (official) or 18 (unofficial).
First I used potatonv to unlock the bootloader.
This seemed to work OK, but in fastboot mode it said bootloader unlocked (red), FRP locked (green).
Maybe this is the problem, I'm not sure why FRP wasn't reset.
I flashed the latest TWRP 3.5.0 for anne from their site.
I was roughly following the instructions here: https://wiki.lineageos.org/devices/anne/install
I did "fastboot flash recovery-ramdisk twrp...".
I was able to boot to TWRP and then I did a wipe. This got to a certain point and seemed to hang.
Eventually I rebooted and now the phone just boots to TWRP initial screen and sits there. I can't get to fastboot mode or stock recovery.
ADB sees the phone in this mode but commands time out.
If I power off the phone and turn it on again I get the "your device is unlocked" screen but then it goes straight to TWRP.
I left the battery run out and when I booted the "your device is unlocked" screen had the option to press a key to boot recovery but if I press nothing it tries to boot and nothing happens, if I press the volume key it goes to TWRP and again just hangs on the initial screen.
In hindsight I probably should have left the stock recovery as the instructions on openkirin and the ROMs forum say it is required.
It's been a while since I played around with custom ROMs, since before treble etc. so I've probably done something wrong.
Any advice is greatly appreciated!
Thanks
jcul said:
I've probably done something wrong.
Click to expand...
Click to collapse
Yes, you have installed wrong TWRP (version 3.4.0.x and 3.5.0.x is not fully compatible with our device and it's strongly not recommended do 'wipe data' runnig stock ROM , it may brick the phone).
- Try in fastboot mode run commands
fastboot erase userdata
fastboot reboot
- Try boot into Recovery update mode (turn off, then press and hold Power + both Volume buttons) and post the result.
Ya I spotted the 3.4.0 thread here just after I had flashed the latest.
I had followed the link from the lineageOS wiki and just installed the latest...
I can't seem to boot into bootloader / recovery update mode.
No matter what I do volume up / down / both I get to teamwin initial screen and it hangs there.
I get the "can't be trusted" screen I posted above when the phone turns on and then it goes to TWRP.
I think when the battery is completely drained I get the "can't be trusted" with "press volume up to boot erecovery" message so maybe I need to wait until it is in that mode and then press both volume buttons.
So I don't get fastboot access but I actually have adb access.
$ adb devices
List of devices attached
89U7N18530003337 recovery
$ adb shell
anne:/ # df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 1852668 68212 1784456 4% /
tmpfs 1912668 296 1912372 1% /dev
tmpfs 1912668 0 1912668 0% /mnt
tmpfs 1912668 4 1912664 1% /tmp
/dev/block/mmcblk0p43 112624 104 112520 1% /cache
Though if I run:
$ adb reboot bootloader
It just hangs.
jcul said:
So I don't get fastboot access
Click to expand...
Click to collapse
Install on PC "Minimal ADB and fastboot" tool, open it, turn off phone, hold Volume down and connect phone to the PC. It should work.
-Alf- said:
Install on PC "Minimal ADB and fastboot" tool, open it, turn off phone, hold Volume down and connect phone to the PC. It should work.
Click to expand...
Click to collapse
Sorry I mean I can't get the phone into bootloader mode. I do have ADB and fastboot installed.
The phone just goes straight to TWRP.
"fastboot devices" doesn't show anything. "adb devices" shows the phone once it's on the twrp screen.
jcul said:
Sorry I mean I can't get the phone into bootloader mode. I do have ADB and fastboot installed.
The phone just goes straight to TWRP.
"fastboot devices" doesn't show anything. "adb devices" shows the phone once it's on the twrp screen.
Click to expand...
Click to collapse
try one more trick - unplug phone, run command fastboot reboot (or fastboot oem get-build-number ) , ENTER. You will see a message Waiting for any device. Then use this method
-Alf- said:
turn off phone, hold Volume down and connect phone to the PC
Click to expand...
Click to collapse
Last chance - try get the phone into bootloader mode using Huawei Multi-Tool.
If it's just a software problem, dc-phoenix and the test point method (paid service) will help you. But it is possible that the emmc memory has died or the motherboard is damaged.
Thanks for the help with this.
I managed to get the device into bootloader mode eventually.
Code:
$ sudo fastboot oem get-build-number
(bootloader) :ANE-LX1 9.1.0.360(IRLC368E6R1P6)
OKAY [ 0.005s]
Finished. Total time: 0.005s
$ sudo fastboot erase userdata
Erasing 'userdata' (bootloader) success to erase cryypt info in oeminfo
OKAY [ 1.801s]
Finished. Total time: 1.818s
$ sudo fastboot reboot
Rebooting OKAY [ 0.024s]
Finished. Total time: 0.225s
I did the erase userdata and after that I was able to get into eRecovery like you suggested by holding both volume buttons.
I thought that would have been wiped after I flashed with TWRP but I guess not.
In eRecovery it said "Data Partition severely corrupted. To reset your device, please format the data partition", so I did that and now I'm back on the eRecovery screen.
I attached some images.
Should I be worried that the bootloader screen shows "FRP Lock"?
My goal is to install LineageOS so now that I've done a reset using the stock eRecovery should I be good to follow the steps here? Or do I need to first flash a stock recovery to the recovery-ramdisk over the TWRP I flashed before?
LOSQ/LiR - LineageOS 17.1/18.1-UNOFFICIAL-GSI
For those who want to try LineageOS 17.1/18.1-UNOFFICIAL-GSI . IMO stable enough to be used as your daily driver. LOSQ/LiR is not developed nor maintained by me! Credits: @eremitein Requirements: basically full stock EMUI 9.1, with stock...
forum.xda-developers.com
Thanks again
jcul said:
I was able to get into eRecovery like you suggested by holding both volume buttons.
I thought that would have been wiped after I flashed with TWRP but I guess not.
Click to expand...
Click to collapse
First of all - in Huawei devices we have two recoveries - Recovery and eRecovery.
- If I'm not mistaken, you have still TWRP on board (instead Recovery), can you boot into TWRP? (it's important)
- In eRecovery menu there's an option "Download latest version and recovery". Have you tried this method?
With FRP lock you cannot flash partitions from fastboot.
And yes, data partition is really corrupted ...
Unfortunately, there's no Service ROM for your build number, your phone is Single SIM, 'Three network' Ireland (correct me if I'm wrong), so you cannot restore your phone via dload method.
Hi,
Yes I selected the "download latest version and recovery" and it seemed to flash successfully.
I can now boot the device normally into the original stock 3 Ireland image.
Unfortunately, there's no Service ROM for your build number, your phone is Single SIM, 'Three network' Ireland (correct me if I'm wrong), so you cannot restore your phone via dload method.
Click to expand...
Click to collapse
Yes that's exactly right.
Is it possible to use a different single SIM variant stock image?
Now volume up takes me to stock EMUI recovery, with options to wipe etc.
Volume up + down takes me to EMUI saying update failed or something like that.
Volume down just boots normally, not to fastboot mode (do I need to have a USB cable inserted to get fastboot mode or is it somehow broken?).
I can get into fastboot by doing "adb reboot bootloader".
So now I have bootloader locked and FRP locked again.
Should I use potatonv again to unlock the bootloader and then try flash a custom ROM after doing a reset with the stock recovery?
Ideally I'd like to have a ROM with optional / hidden root so I can use banking apps but also have root access, but if I have to lose banking apps to have root then I'm OK with that.
jcul said:
Is it possible to use a different single SIM variant stock image
Click to expand...
Click to collapse
yes, but you have to rebrand the phone to another region, e.g. eu C432 - replace oeminfo and flash eu firmware (you get dual SIM because oeminfo for single is not available). The process will lock the BL again.
jcul said:
not to fastboot mode (do I need to have a USB cable inserted to get fastboot mode or is it somehow broken?).
Click to expand...
Click to collapse
Turn off the phone, hold Volume Down and connect to PC.
jcul said:
Should I use potatonv again to unlock the bootloader and then try flash a custom ROM after doing a reset with the stock recovery?
Click to expand...
Click to collapse
Yes, you can,
each bootloader code is permanent, it wont expire.
jcul said:
Ideally I'd like to have a ROM with optional / hidden root so I can use banking apps but also have root access,
Click to expand...
Click to collapse
Try CAOS
Thanks.
So I think this is what I will do.
1. Unlock bootloader using potatonv again (hopefully this time it will reset FRP Lock too as I have no google account on the phone this time).
2. Root phone using magisk so I can change oeminfo.
3. Flash oeminfo following this guide.
4. Download and flash ANE-LX1C432E5R1P7B132 from here using fastboot and do factory reset.
5. Flash CAOS rom over stock 9.1.0.132.
jcul said:
Thanks.
So I think this is what I will do.
1. Unlock bootloader using potatonv again (hopefully this time it will reset FRP Lock too as I have no google account on the phone this time).
2. Root phone using magisk so I can change oeminfo.
3. Flash oeminfo following this guide.
4. Download and flash ANE-LX1C432E5R1P7B132 from here using fastboot and do factory reset.
5. Flash CAOS rom over stock 9.1.0.132.
Click to expand...
Click to collapse
I've never done a rebrand running EMUI 9.1, I'm not sure if it works. Try downgrade to Oreo via HiSuite, then follow this tutorial - variant C/.
jcul said:
hopefully this time it will reset FRP Lock too as I have no google account on the phone this time
Click to expand...
Click to collapse
You can FRP unlock manually in Developer options - "Enable OEM unlock"
jcul said:
. Download and flash ANE-LX1C432E5R1P7B132 from here using fastboot and
Click to expand...
Click to collapse
Use only service ROM and dload method.
I decided to go straight for Lineage OS 18 unofficial.
Works great.
If I ever need to go back to stock then I guess I will have to go the rebrand route.
Thanks again for the help.
jcul said:
I decided to go straight for Lineage OS 18 unofficial.
Works great.
Click to expand...
Click to collapse
Yes, one of the best custom ROMs for hi6250 devices . Now fully compatible with Magisk !
jcul said:
Thanks again for the help.
Click to expand...
Click to collapse
No problem.
So I got a Lil c100 a couple days ago. It has a screen lock and the recovery mode don't work. Everyone says get it into fastbook amd use that to get to recovery. But the problem is after I get into fastboot the device isn't found. I've installed every USB driver known to man about fastboot or Nokia in general. And yet it still not popping up. Can sb help me?
swiftd3v said:
So I got a Lil c100 a couple days ago. It has a screen lock and the recovery mode don't work. Everyone says get it into fastbook amd use that to get to recovery. But the problem is after I get into fastboot the device isn't found. I've installed every USB driver known to man about fastboot or Nokia in general. And yet it still not popping up. Can sb help me?
Click to expand...
Click to collapse
anything yet?
swiftd3v said:
So I got a Lil c100 a couple days ago. It has a screen lock and the recovery mode don't work. Everyone says get it into fastbook amd use that to get to recovery. But the problem is after I get into fastboot the device isn't found. I've installed every USB driver known to man about fastboot or Nokia in general. And yet it still not popping up. Can sb help me?
Click to expand...
Click to collapse
What do you mean by "the device isn't found"?
wenyendev said:
What do you mean by "the device isn't found"?
Click to expand...
Click to collapse
The error I’m getting is “fastboot: usage: unknown device target recovery”
I am experiencing the EXACT same thing. No matter what box program Im using , nothing works! crazy. Please help. Id be happy with a factory reset. Atleast then I could get past the FRP.
Wow, I have not encountered that error yet.
I could only guess that it might be a problem of recovery.
How did you install your current recovery if not from fastboot?
diamant3 said:
The error I’m getting is “fastboot: usage: unknown device target recovery”
Click to expand...
Click to collapse
you're using fastboot reboot recovery?
Hey any update on this? I can say I've come across the same issue where their seems to either be no recovery or a corrupt one.
One thing I want to point out is (at least with the TracFone) that when I put the device in fastboot, and have wondershare tune go running, it displays the device as a Sony Xperia. The program still isn't able to connect to the device for me to attempt a reboot into recovery. It also reads the device as two other devices.
I'm hoping someone has encountered these findings and may also have a dump of the stock rom.if so I may be able to begin rooting for at least fix the recovery issue.
TaigaDaReck said:
Hey any update on this? I can say I've come across the same issue where their seems to either be no recovery or a corrupt one.
One thing I want to point out is (at least with the TracFone) that when I put the device in fastboot, and have wondershare tune go running, it displays the device as a Sony Xperia. The program still isn't able to connect to the device for me to attempt a reboot into recovery. It also reads the device as two other devices.
I'm hoping someone has encountered these findings and may also have a dump of the stock rom.if so I may be able to begin rooting for at least fix the recovery issue.
Click to expand...
Click to collapse
Also I'm going to use my Linux system to see if I get any results. Let me know if you've tried it as well.
fastboot oem unlock/fastboot flashing unlock has been blocked in the boot loader, only hope for root is another brom exploit like mtkclient or a temp root privilege escalation exploit
luridphantom said:
fastboot oem unlock/fastboot flashing unlock has been blocked in the boot loader, only hope for root is another brom exploit like mtkclient or a temp root privilege escalation exploit
Click to expand...
Click to collapse
Were you able to get fastboot to recognize the device?
Which OS are you testing on if you are?
TaigaDaReck said:
Were you able to get fastboot to recognize the device?
Which OS are you testing on if you are?
Click to expand...
Click to collapse
you need to use a special mtk boot mode script you can download here #101
Code:
computer:~ user$ python3 ~/Downloads/mtk-bootseq.py FASTBOOT /dev/tty.usbmodem14100
b'READYTOO'
Boot sequence sent
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock-go
FAILED (remote: 'unknown command')
fastboot: error: Command failed
testing on android 12, jan5 2022 update build 02US_1_030
luridphantom said:
you need to use a special mtk boot mode script you can download here #101
Code:
computer:~ user$ python3 ~/Downloads/mtk-bootseq.py FASTBOOT /dev/tty.usbmodem14100
b'READYTOO'
Boot sequence sent
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock-go
FAILED (remote: 'unknown command')
fastboot: error: Command failed
testing on android 12, jan5 2022 update build 02US_1_030
Click to expand...
Click to collapse
Hey thanks for the response.
So far I've been able to get the device to read in fastboot but I'm still unable to unlock the bootloader since as your saying it's definitely..."gimped" haha. I'll checkout the script and do some tests to see what I get.
TaigaDaReck said:
Hey thanks for the response.
So far I've been able to get the device to read in fastboot but I'm still unable to unlock the bootloader since as your saying it's definitely..."gimped" haha. I'll checkout the script and do some tests to see what I get.
Click to expand...
Click to collapse
if you're curious you can always reach out to this guy, he's able to get prototype boot loaders and stuff: https://twitter.com/Hikari_Calyx
might even know how to get test points to force it into brom for mtkclient
Hello, I'm a new user here. Lately I've been trying to root my Redmi Note 8 Pro. Following the standard procedure, I unlocked bootloader in the first place. Then, I downloaded usb and adb/fastboot drivers, searched for a twrp image compatible with my device and placed it in the adb folder. My problem is that after flashing the recovery, my phone sometimes goes into a bootloop, sometimes just boots normally and won't let me get in recovery. What am I doing wrong? I tried everything to make it work, even different versions of twrp and orangefox. Thanks :3 (if you need further information I'll kindly provide it to you).
read the instructions
https://twrp.me/xiaomi/xiaomiredminote8pro.html
aIecxs said:
read the instructions
https://twrp.me/xiaomi/xiaomiredminote8pro.html
Click to expand...
Click to collapse
Thanks for the response. I tried disabling avb before flashing twrp, but still, there's no way I'm booting into recovery after the device reboots. I also tried to temporarily boot twrp but it shows me an error:
Sending 'boot.img' (29152 KB) OKAY [ 0.641s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
fastboot boot can't work for SAR that's expected. flash TWRP recovery + vbmeta again, then press and keep holding Vol+ up button, type fastboot reboot, once you see TWRP release Vol button, swipe to allow modifications
aIecxs said:
fastboot boot can't work for SAR that's expected. flash TWRP recovery + vbmeta again, then press and keep holding Vol+ up button, type fastboot reboot, once you see TWRP release Vol button, swipe to allow modifications
Click to expand...
Click to collapse
Nothing seem to work. Holding the vol button just makes my phone bootloop. I really don't know what I'm doing wrong.
if the flashed custom recovery just bootloops then try another recovery
I believe there is a typo at TWRP page, try (reboot with holding Volume Up)
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
fastboot flash recovery twrp-3.7.0_9-0-begonia.img
fastboot reboot