Hello!
I am following the 'How to root DIG-L21HN' phone thread, and after downloading the images they provided (they are supposed to be modified TWRP for this specific model, or so I understood) and flashing them using the 'fastboot flash recovery 1streco.img' command my computer shows the following:
target reported max download size of 532676608 bytes
sending 'recovery' (21456 KB)...
OKAY [ 0.680s]
writing 'recovery'...
OKAY [ 0.447s]
finished. total time: 1.136s
Click to expand...
Click to collapse
However, when I try to get into recovery mode on the phone itself, I am greeted with the default Huawei recovery, and not TWRP. I tried downloading another TWRP file from another site, supposedly for the same model, but got the same results...
One other interesting thing I noticed is that the phone does not boot into fastboot mode if I use the command on the PC, but it does if I manually do it (vol down + power).
OEM is unlocked, USB debugging in on, fastboot is enabled and I can see the device using the 'fastboot devices' command... It's like if there was another layer of security that I don't know.
What can this be? Any ideas?
Hello Dear
How you able to unlock bootloader?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
Hi All
Can anyone please tell me if it is possible to unlock the boot-loader while the phone is stuck in RUU mode?
I am unable to boot the phone normaly, or enter the bootloader.
I have been trying to re-flash the stock RUU, but the process hangs at 32%, please see my post here: HTC Sensation XE - RUU 3.33.401.153 stuck while flashing
One of the possibilities that are making the RUU fail is that there is a problem with the phone mounting partitions.
The phone in question was using Team Win Recovery Project.
So I am hoping to be able to re-unlock the phone again and install 4EXT Recovery to fix the issues, so I can then re-flash the stock RUU.
I have read and followed the HTC instructions for re-unlocking the phone.
Code:
[B]fastboot flash unlocktoken Unlock_code.bin[/B]
sending 'unlocktoken' (0 KB)...
OKAY [ 0.153s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.010s]
finished. total time: 0.165s
I am expecting to see something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But the phone does not display anything more then the RUU mode logo.
Thanks for your time.
Best Regards.
Hello,
I bought this phone and didnt notice that it has only Android 7. Exists some custom firmware with higher Android for install on it?
Apparently not.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thing is that this is a nearly 4 year old device from a brand that doesn't have much of a name in the smartphone industry and virtually no community. As far as I can see there isn't even a way to unlock the bootloader of this device. Couldn't even find a way for their newer (2020) U710S so I'm afraid it's a dead end.
I did oem unlock with fastboot.
Also I tried boot original recovery.img by command
Code:
fastboot boot recovery.img
just for test, but it won't work, it displays "No command" on screen and broken android logo. It has MT6750 processor, I found some TWRP recovery images for same chip, but I do not want flash it with fastboot flash recovery twrp.img, becouse im scaried about bricking it. It's safe to flash recovery.img with this TWRP image? It's possible to get back stock recovery.img, if it won't work?
I tried it and it was not able to work, so i did original flash. And really, stok recovery gave me the same error, "no command", also new phones, when someone tries boot to recovery from bootloader menu gave same error, so its manufacturer problem
More Details:
i am able to enter fastboot mode but not recovery mode
reason for this :
i downgraded my nord from oos 12 to oos 10 and my dumb brain decided to lock the bootloader while it had just finished installing, so the "enable oem unlock" option in the developer options is probably switched off
when i try to unlock the bootloader using FASTBOOT OEM UNLOCK , i get the message
FAILED (remote: 'Flashing Unlock is not allowed')
fastboot: error: Command failed
Please respond ASAP
Use MSM Tool
CYB3R0ID694 said:
Use MSM Tool
Click to expand...
Click to collapse
i saw that the device needs to be in edl mode to ab able to use msm but when i try to press volume up and down for 40 seconds and connect the usb, the device automatically boots and gives the message "Your device is corrupted. it can't be trusted and will not boot"
this is what i get when i try to unlock using adb
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Finally Got It After several tries
~ Thread Closed
I have unlocked my Realme C2's bootloader and my device shows this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But when I input the "adb reboot bootloader" command the phone booting into this (USB Debugging is "ON")
I have flashed TWRP and it showed "OKAY", but when I input the "fastboot reboot recovery" my phone rebooting into ColorOS!, what is going on? Please help.
patraputt said:
I have unlocked my Realme C2's bootloader and my device shows this
View attachment 5673129
But when I input the "adb reboot bootloader" command the phone booting into this (USB Debugging is "ON")
View attachment 5673131
I have flashed TWRP and it showed "OKAY", but when I input the "fastboot reboot recovery" my phone rebooting into ColorOS!, what is going on? Please help.
Click to expand...
Click to collapse
If you are on ColorOS, 1stly, use COS TWRP ( not RUI TWRP ), 2ndly, u should try : fastboot oem reboot-recovery instead of fastboot reboot recovery.
So I bricked my UleFone Note 8 when trying to install a GSI ROM.
Have been trying to recover using SP Flash Tool.
Was getting the
Error 3154: BROM ERROR: S_DA_SDMMC_WRITE_FAILED (3154)every time I was trying to flash. So I decided to flash one file at a time.
All files went ok, except "super" (references to super-sign.img) It's a 2.1GB file.
So I can see, it's not a connection issue of any kind. Maybe the size of this file bringing an issue?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BTW I'm using SP Flash Tool from my Linux Mint PC.
Would really appreciate some help on this pls.
Update:
I just remembered that when I initially tried installing the GSI ROM, I experienced this error (I was using fastboot adb method):
target reported max download size of 16777216 bytes
wiping userdata...
Invalid logical-block-size 512: must be a power of 2 and at least 4096.
Segmentation fault (core dumped)
Maybe this is causing the Error 3154: BROM ERROR: S_DA_SDMMC_WRITE_FAILED (3154) and thus the super file is not be flashed successfully?