Hey there. I'm new here, and to be honest, I'm new to the world of smart phones. The 4xHD is my first smartphone and I've had it for about a year now. I've noticed that it performs really badly on the 4.1.2 JB so I've decided to root it, unlock the bootloader, flash cwm and get a Cyanogenmod 10.1.3 up and running on it.
Long story short, I've rooted my phone and followed this http://forum.xda-developers.com/showthread.php?t=2245836 thread to unlock the bootloader but it didn't really go as planned. I did the things in the cmd app on the phone, and did the first line of cmd on my lap top (adb reboot bootloader) and when I wanted to do the second line (fastboot oem unlock) the cmd said it was waiting for the device. I waited for 5 minutes and nothing was happening on the device. It was stuck on the LG screen (not the one with flashing lights, just the logo screen). I pulled out the USB and pressed volume down and the power button just in case. Then I pulled out the battery, turned on my phone and went to the 3845#*880# secret menu to check the bootloader status. When I tapped on the bootloader unlock check thing, it said "Unlock".
So, did I just unlock the bootloader? Operation successful? Is there a possibility that I didn't unlock the bootloader in a correct way so it will brick my device when I try to flash cwm and Cyanogen?
I'm really sorry if this thread is in a wrong section or something. I searched on the xda but couldn't find the answer to my question.
Thanks in advance
EDIT: I'd also like to mention that in no part have I encountered the screen which said "you're about to unlock your bootloader, warranty voiding, blah blah blah, are you sure you want to proceed"
I have a HTC One MIni that is stock in a fastboot loop every time I turn it on. I can't get any option from bootloader to work. So after doing some reading here I was going to unlock the phone and try to fix it but I can't unlock the phone. So fastboot was able to get the code and I went to htdev and get the unlock.bin file and I can run it with fastboot and it says it is all good but the disclaimer that it is supposed to come up after this on the phone, never comes up. I thought maybe restarting it would show it is unlocked but no luck. So I'm stuck with the phone only booting on fastboot mode and not being able to unlock it and therefore can't install anything to fix it. Is there a way I can fix it?
Thank you
My HTC One mini swtiched off a couple of days ago and since then only load to bootloader menu no matter what I click or do. It goes also automatically to this screen as soon as I plug it with the charger even if did not press the on/off key.
I tried to unlock the bootloader according to the instructions on HTCDev.com site. Everythings work till the last step, as no menu appear on my phone asking me if I want to unlock the bootloader or not.
I also tried to use RUU to install a new Firmware. The phone showes a black screen for a couple of seconds and then restart again to bootloader screen. I got an error afterwards.
The phone was running on a stock firmware, no root, no custom recovery, or any other thing.
Can anyone help me to solve this problem. It seems my phone has no OS or something like that.
PLEASE HELP
Hi guys n gals
it appears ive inadvertantly deleted my rom i successfully unlocked bootloader installed recovery but over killed me wiping. Sso ive got an unlocked bootloader, have access to fasboot and recovery but fone is stuck at bootlader screen. How do I flash a rom now? as when hooked to a pc its no longer recognised. any help much appreciated!!!
moh19814 said:
My HTC One mini swtiched off a couple of days ago and since then only load to bootloader menu no matter what I click or do. It goes also automatically to this screen as soon as I plug it with the charger even if did not press the on/off key.
I tried to unlock the bootloader according to the instructions on HTCDev.com site. Everythings work till the last step, as no menu appear on my phone asking me if I want to unlock the bootloader or not.
I also tried to use RUU to install a new Firmware. The phone showes a black screen for a couple of seconds and then restart again to bootloader screen. I got an error afterwards.
The phone was running on a stock firmware, no root, no custom recovery, or any other thing.
Can anyone help me to solve this problem. It seems my phone has no OS or something like that.
PLEASE HELP
Click to expand...
Click to collapse
I seem to be in the same situations... although I got to it in a different way. Where did you download the RUU from? is it version-main: 4.14.401.2 or higher?
Try: rootwiki dot net and search for htc one mini bootlocker unlock....this helped me to UNLOCK and put TWRP recovery on it... maybe it gets you a step closer.
HELP! I was locking my bootloader, on my Moto G3, but now it shows the bootloader message, then the android character, with the words on top saying, "Erasing...", and keeps going. When I write something on adb, it says <Waiting for Device>!
HELP!
why in hell would you want to lock your bootloader? can you go in bootloader and use fastboot?
Any "Erasing..." steps on this device can take forever, give it a minimum of 30 minutes to complete.
Giving use some more info on what you did and the current state would be helpful.
And BTW, the only reason to relock the bootloader is for your own security... There is no other reason to lock the bootloader, even stock and (re)locked will show the device was modified in the bootloader.
Sent from my Motorola XT1575 using XDA Labs
As per title, it just happened while I was using the phone while charging. Trying my luck as I'm not in the country(Australia) that I bought my Pixel from. Grateful for any suggestion that the sub can provide. Non rooted stock rom
You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.
Yes only bootloader. What you have mentioned do not require recovery mode right ? Cos I can't boot into it. Thanks for your reply
k.s.deviate said:
You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.
Click to expand...
Click to collapse
The bootloader would have needed to have been unlocked already.
indifferent1 said:
The bootloader would have needed to have been unlocked already.
Click to expand...
Click to collapse
no it doesnt, I suggested unlocking the bootloader first, that way it factory resets. this might fix the problem, if not its unlocked so he can flash the factory image.
Bump? I'm having this problem as well.
Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.
graymoment said:
Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.
Click to expand...
Click to collapse
I'm having the same issue. My wife's Pixel entered a continuous boot loop today. It only loads the white screen that says "Google." I can enter the bootloader, but when I select "recover," it goes back to the bootloop. As far as I know, she is on Android 8.1, debugging mode is off and the phone is 100% factory.
If anyone has solved this issue, it would be greatly appreciated!
Thanks
has anyone figured this out?? this happened to me today, i was using the phone, the poof it restarted itself and stayed in a boot loop. i can get into the recovery, i tried wipe/factory reset. any suggestions? google told me i need to send it to whatever company to get it fixed or get a new phone. verizon told me to go through insurance. insurance told me to go through verizon because i may be able to use the extended warranty. went back to verizon but they wont take it because the screen cracked a year ago. its not a deep crack and it didnt affect the phone at all, never had an issue. so now i go back to assurion and now they need an affidavit about my screen being cracked. im at a loss.... i havent rooted a phone since my droid x, then s3 days. so im essentially new again!
Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots
thedosbox said:
Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots
Click to expand...
Click to collapse
I had the same thing happen yesterday (not long after the Android 10 update). I was finally able to get it to boot after multiple tries and it stayed up long enough for me to enable "OEM unlocking" in Developer options. Now at least I have the option of unlocking the bootloader and re-flashing the OS with an image directly from Google.
Has anyone been able to get past this problem by reflashing the image? I suspect the underlying problem is some kind of hardware fault with eMMC, DDR, or the SOC itself.
One other interesting behavior I noticed is that the only way to shut it down and stop the bootloop is to select the "Power off" option in the bootloader menu. However, if I plug it in to charge when it is fully powered "off", it will start up the bootloop again.
Same sitution here. A couple of days after installaing it suddenly went inte a G-bootloop frenzy.
Erratic though, sometimes I could boot up (2-3/40 boots) but then it froze and started again.
Also Recovery and Safemode is very hard to get into.
Got in once or twice out of 100 boots, Bootloader Fastboot is generally reachable though.
It exhausted the battery and now I'm holding off trying to interfere, until I get more info off the net.