[Q] Unlocking Boot-loader in RUU Mode - HTC Sensation

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.

Related

ADB Sideload not working for me

Despite all the good posts on here I have been unable to get my phone out of a boot loop, and am now quite desperate for help please!
If anyone can point me in the direction of a rom or kernel that will definitively work on my phone I will be eternally grateful
It was ok until I decided to unlock bootloader and root it.
Unlock bootloader went well, as did flashing TWRP and also CWM – I have a suspicion that it was rooting with OneClickRoot caused the problem.
After over a day of failure I discovered how to do ADB Sideload at this thread: I used CM11 I got from this thread: and also tried a Stock one from here:
sadly nothing worked, and I'm now afraid of filling my phone storage with large files. I have added some screen shots of my failed attempts with TWRP & CWM
they both fail, and TWRP does warn me not to reboot as I have no OS installed, but I had to keep on trying.
Another weird thing is that I cannot always reboot to recovery from the Hboot screen and have to re-flash a recovery image each time.
{
"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"
}
SOLVED
no need to reply now folks, I got the job done ... see here

TWPR or fastboot not working for DIG-L21HN?

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"
}

Question missing bootloader unlock in samsung download page

I locked the bootloader from download mode and now there is no unlock option (long press Vol +). OEM in download mode is on but when I try to install TWRP It says OEM is locked.
{
"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"
}
is it better than stock?
going to everyday?
Where you able to get the Lock Bootloader?
parsa_foss said:
I locked the bootloader from download mode and now there is no unlock option (long press Vol +). OEM in download mode is on but when I try to install TWRP It says OEM is locked.
View attachment 5632795
Click to expand...
Click to collapse
Bro, I think you locked the bootloader without installing the stock ROM. This is baaad. You should have flashed the stock firmware with Odin before locking the bootloader.
Now, I guess you can try booting to download mode, flashing the stock original ROM with odin. Then, if everything works, unlock the bootloader in the normal way and then flash TWRP.
You cannot flash TWRP if your bootloader is locked.

Phone Stuck At "Your Device Is Corrupted" [THREAD CLOSED]

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

SP Flash Tool - Error 3154 when flashing super-sign.img to phone

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?

Categories

Resources