Hello guys,
I finally got this great phone but I'm having all kind of problems here.. missing my old samsung s3 mini
As said in the title I managed to unlock the bootloader but, for some strange and unknown reason, i decided to lock it back again. The problem is that I don't have a custom recovery or root.. but security is on (S-On).
While being in fastboot I've no problems with the fastboot "flash unlocktoken Unlock_code.bin" string. After I confirm that I want to unlock it, a quick white boot page with the HTC logo appears for a super short time and then it boots off showing a battery image and a blinking red light. (just to be clear; fix to this is to press volume up, volume down and power button for a while).
After the boot the bootloader is still locked.. or relocked I should say.
I'm thinking that -cause I'm also having some issues with battery heat, reaching easily 50celsius, and battery drain- the problem is the battery.
Do you have any idea of what to do? Having this phone and not being able to "make it mine" is slowly killing me.. day by day. So If you DO have any idea, please, please help me.
PS
if i unplug the phone after the fastboot flash string and, just after having it unplugged, confirm to unlock the bootloader, the phone just boot off -not having the red light problem tho-
Sorry if not clear.. not mother tongue ^^
No? Nothing I can do about this? Guess I'll keep everything on stock
Related
Hello all,
as the title says, one of my touch diamond's is stuck in bootloader screen.
I didnt do anything in between it working and not working, it was on my desk, put it there working, got it 5mins later, and it was in bootloader screen (tricolor screen).
What i've already done to try and fix it:
flash it with the original HTC rom, flash completes succesfully, phone reboots to tricolor screen, so no solution there.
install mtty and format the phone, this completes, reboot the phone, again goes to the bootloader.
reflash the phone with original rom after cleaning it with mtty, flash again completes succesfully but when it reboots after flashing it just goes to bootloader again.
Tried to flash a Hardspl: stuck at 0% and stays there. so that doesnt work.
BUT! when in mtty i give the "boot" command, it DOES start to boot WM. but then again, when i turn the phone of, and on again, or it reboots because of first start after flash, it goes to bootloader again. The VOLDOWN button is NOT stuck, cause when it boots i can use the vol buttons perfectly fine.
Anyone got an suggestion in how to unbrick it? i have a second, perfectly working diamond here too, if that helps in any way.
Some more info ive just seen in mtty, when i told it to boot, it said ONE BAD BLOCK IN CE, remove block ---- to ---- (dont know the exact numbers anymore)
hi..i had something like that...
just download this.
"RUU_Signed_1_93OliNex_HSPL_UnsignedEdition"
it's only 1.7MB and it's will make it work.. atleast it did the job for me...
Hi,
My T mobile touch diamond stuck in bootloader screen? Any experties to help me please.
Thanks in advance.
Hi guys,
I have been trying to unbrick my Turbo to get my pics back but not having any luck... hoping someone can help.
Background:
Bought this phone refurbished about 1 1/2 yrs ago and used Sunshine to unlock bootloader, installed TWRP, rooted, all was fine until last weekend. Battery was totally dead (battery icon wouldn't even show up with power button press). Plugged it in to charge and when I came back to it it was on the bootloader screen (robot lying down with his hatch opened). I can go to the Logs entry and it says 'Failed to validate boot image'. Any other option does nothing (except power off and Barcodes). Cannot boot into recovery. I can see phone info on bootloader screen along with "Device is UNLOCKED. Status Code: 3" "Software Status: Modified" but flashing has not helped.
Tried reflashing TWRP and stock Recovery and Boot with mfastboot, the phone seems to take them (no errors from mfastboot) but no change. I tried to flash the logo.bin from a stock image and the phone seemed to take it ok but after rebooting, the robot image and menu are gone (the text is still there... 'AP Fastboot Flash Mode (Secure)' with other info). The battery icon is also gone and all I see is 'static' when the low battery icon should be displayed attempting to power up with low battery. Same static seems to have replaced the 'Bootloader Unlocked' warning screen which flashed briefly before stopping on bootloader.
Are there any suggestions of how to get this phone back to life? I am really only concerned with getting the photos off (I already have a replacement; G5+). For some reason ADB does not see the phone. Any help would be appreciated!
Thanks
Hank
Hey
yesterday i almost bricked or maybe bricked my phone. Accidentally changed partition from B to A. Today my phone boot only to nokia logo and stuck on it
Many hours readed about this phone back to life. Recover mode not work, fastboot mode not work. This phone one chance to turn off is completly battery discharge.
If no chance to get back this phone to normal i will get throw it to trash
Classic example of a softbrick can't really call it a hardbrick tbh. PM me all of the details and I'll later make a tutorial if we manage to fix it up.
mati5000 said:
Hey
yesterday i almost bricked or maybe bricked my phone. Accidentally changed partition from B to A. Today my phone boot only to Nokia logo and stuck on it
Many hours reading about this phone back to life. Recover mode not work, fastboot mode not work. This phone one chance to turn off is completely battery discharge.
If no chance to get back this phone to normal i will get throw it to trash
Click to expand...
Click to collapse
I did the same thing.
- Downgrade to Oreo
- unlocked officially bootloader
-fastboot boot twrp.img
booted to twrp- Flashed zip on both slot with latest twrp
Changed slot A to slot B and
we have same problem.
How did you solve your issue?
Did you wait for battery-drain?
Or other combination of buttons.
I tried all the button-combination without success.
Hope you could give advice
Regards
Edit: How to solve!
I simply waited until the battery ran out
When battery was completely dead and no Nokia-logo any more
Then I charged the battery 3% juice without booting
and from there I entered recovery-mode with the help of a USB cable.
Holding the volume+ button while connecting the USB-cable
From TWRP-recovery I changed to the other inactive slot
and whooala, that's it!
I have OEM unlocked my nokia 8 boot loader by nokia official method ,
Then I decide to flash twrp and magick
When boot twrp it give an error that locked
Then I checked some forums and find a way ,
I do what is guided in that forum
Change boot slot b to a ... and I flashed twrp then I flash rom , at the end of flash slide to reboot , then I reboot but after that there is no response in device it went blank and black.....
If I connected to PC in some flash tool it show hs com 3008 and connecting sound in pc but mobile being blank and i cant even get to fast boot mode becoz device get blank ( while connected in pc if I power on or hold power but connection sound will come from my pc but no device or unknown device )
Pls help friends, really dunno what to do
Pls help !
Respond soon pls
Same as me bro.. my ta 1004 is dead after unlocking bootloader official method. And i flash boot twrp and magisk. But my phone always bootlop. I try to flash with ost la. An qfil to recover. But i stuck in download mode. And i try to flash with twrp slide load .
And my phone is dead now.. i can do anithing. My phone can turn on now... i charge it .. but still not respond
Anyone help me
Hey, sorry to bother everyone with another bootloop thread by I just can't for the life of me work out if I'm doing something wrong, or my device is more of a dud than usual.
So got the phone yesterday, did some ota updates ended up in a bootloop.
Now at this point my bootloader wasn't unlockable as I hadn't enabled it in developer settings.
By some miracle it managed to boot itself back into the OS after an hour of fiddling and i decided to enable the option in developer settings.
Now I've unlocked the boot loader and got all the flashing related fastboot commands working i've
Flashed a stock image using the miflash tool, seems to succeed but then on reb but once it's done i'm still in a boot loop!
I've been able to boot into twrp a few times (though most of the time I can't and am still in a bootloop)
Tried flashing a custom rom, but I always seem to be in a boot loop after attempting that.
Throughout the last few hours i've also managed to hit the os a couple of times but it seems very easy to accidently put it back in a bootloop.
If anyone has advice of something to try, that would be great.
(was trying stock image version 10.0.9.0, going to try and go back to stock Oreo)
Smtih said:
Hey, sorry to bother everyone with another bootloop thread by I just can't for the life of me work out if I'm doing something wrong, or my device is more of a dud than usual.
So got the phone yesterday, did some ota updates ended up in a bootloop.
Now at this point my bootloader wasn't unlockable as I hadn't enabled it in developer settings.
By some miracle it managed to boot itself back into the OS after an hour of fiddling and i decided to enable the option in developer settings.
Now I've unlocked the boot loader and flashed a stock image using the miflash tool which all seems to go swimmingly, but once it's done i'm still in a boot loop!
Throughout the last few hours i've managed to get into the os a couple of times.
I've been able to boot into twrp a few times (though most of the time I can't)
Tried flashing a custom rom, but I always seem to be in a boot loop after attempting that.
Sometimes it goes to a failed to boot screen, while other times it seems to loop endlessly.
If anyone has advice of something to try, that would be great.
(was trying image version 10.0.9.0, going to try and go back to stock Oreo)
Click to expand...
Click to collapse
Try some custom kernel, or patched boot img
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
NotOverHere said:
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
Click to expand...
Click to collapse
Yeah, A2 have A/B partition and if update is faulty and the phone ends in bootloop, after a few failed boots, it will boot from other partition.
NotOverHere said:
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
Click to expand...
Click to collapse
I think something along these lines is how i managed to get into the phone the first time and enable oem unlocking.
After a lot of playing around I was able to get the phone to boot by flashing the latest Oreo image (9.6.16)
After that tried going to a pie image again from fast-boot image (10.0.8) and once again ended up in a boot loop.
Lastly I flashed a fast-boot image of the latest ota (10.0.10) and managed to boot in.
So phone is at least all working now. Thanks for everyones help. Just hope the next ota doesn't bootloop the phone again.
@NotOverHere: When the phone finally does boot up, do you find it's stable and reboots are fine after that?
Smtih said:
I think something along these lines is how i managed to get into the phone the first time and enable oem unlocking.
After a lot of playing around I was able to get the phone to boot by flashing the latest Oreo image (9.6.16)
After that tried going to a pie image again from fast-boot image (10.0.8) and once again ended up in a boot loop.
Lastly I flashed a fast-boot image of the latest ota (10.0.10) and managed to boot in.
So phone is at least all working now. Thanks for everyones help. Just hope the next ota doesn't bootloop the phone again.
@NotOverHere: When the phone finally does boot up, do you find it's stable and reboots are fine after that?
Click to expand...
Click to collapse
Plss post the link of 10.0.10
Hello all,
I have been using my Pixel 4 XL for years, and all of a sudden it shut down, and now it keeps being stuck in a booting loop.
I get to Google's logo and the loading animation ... and then it turns black, and starts all over, in a loop.
I am able to access the bootloader and recovery mode.
I tried a complete wipe through recovery mode, didn't change anything.
I wanted to flash original images, but the bootloader is locked and I haven't found any way to unlock it without going through the phone settings (which doesn't boot anymore).
All fastboot flashing related commands fail stating my device is locked.
Would you have any suggestion ?
Anything I should try before considering my device is completely dead ?
Thanks in advance
utundu said:
Hello all,
I have been using my Pixel 4 XL for years, and all of a sudden it shut down, and now it keeps being stuck in a booting loop.
I get to Google's logo and the loading animation ... and then it turns black, and starts all over, in a loop.
I am able to access the bootloader and recovery mode.
I tried a complete wipe through recovery mode, didn't change anything.
I wanted to flash original images, but the bootloader is locked and I haven't found any way to unlock it without going through the phone settings (which doesn't boot anymore).
All fastboot flashing related commands fail stating my device is locked.
Would you have any suggestion ?
Anything I should try before considering my device is completely dead ?
Thanks in advance
Click to expand...
Click to collapse
Try sideloading an OTA image. You can do that with a locked bootloader.
Thanks Lughnasadh
I've tried multiple times, and the process fails randomly, at different percentages ...
The phone suddenly reboots and the laptop displays " adb: failed to read command: No error"
The weird thing is it doesn't reboot and can stay up for super long while on the bootloader.
With a locked bootloader the rescue OTA (full OTA image flashed via adb) is all you have. I would try a different data cable (A-to-C) first and then move to a different computer. Make sure the new PC is running the latest adb/fastboot binaries. This is why I unlock the bootloader on every Pixel in my family. Even though they will never root the phone, if the fit hits the shan you have many more options. BTW, I just traded in my son's P4XL and got $285 trade-in on a 6a. Net cost was less than $150. The deal just ended but will likely come back again. Same deal was offered earlier but included a pair of first-gen earbuds. Wish you luck on getting your old phone working. The P4XL is still my primary phone and is still working well.