Right, I'm new to this, so I might be a total idiot, but I can't get into the bootloader. I've tried the ADB commands and rebooting into bootloader from recovery mode. On both occasions, the phone just restarts normally. It is a T-Mobile variant but I don't think it's carrier locked because I can use an O2 sim fine? I'd appreciate some advice.
Related
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
hi - i have in my nexus 5 only the google logo and the unlocked key is on the screen;
when i get to fast boot it does see the device.
when ienter " fastboot oem device-info
igot device tampered true
device unlock true
off mode charge - true
when i try to write twrp recovery it says sending recovery okay and writing recovery okay.
but ucant enter to the recovery of twrp.
when i try to flash an image it says:
writing bootloader
failed (remoteflash write failure)
rebooting into bootloader okay
writing radio - failed remoteflash write failure
target reported max size of 1073741824bytes
is there any way to save my phone?
i can enter adb its says on the phone "now send the package you want to apply to the device with "adb sideload filename"..
how do i can send an image?
thank u
re
i try to flash with the lg flash rool - i did everything ok and it stuck in 6% and says"user data erase fail" what can i do?
You're using the batch commands included with the stock ROM to re-flash?
Hi my Nexus 5 also suddenly die too. And I have the same exact problem that you have when trying to flash it. I looked for hours on the internet tried formatting, erasing and many other alternatives and nothing. There are some people experiencing this same problem like us. For no reason the memory is getting corrupt or died. I get mant errors on the cache when I boot to regular recovery. The only recovery that I have manage to boot to (except for the original one) is Clockworkmod using fastboot boot "therecoveryname.img". With clockworkmod I have adb working but still can get the phone to boot or accept factory images. I can't lock the bootloader either.
I think this error was cause by the software. There was a very similar problem that never got fixed for the nexus 7 when lollipop came out.
Do you need to lock the bootloader? Once locked, you cannot flash anything via fastboot commands, not even a stock ROM.
No I don't need to. I tried just to see if the phone will relock itself. I read somewhere in the internet that if you can't relock/unlock the device the nand if fried.
If you look for these errors there are people with LG G2 and LG G3 that are having something similar happen. I think LG hardware is partly behind the problem. I call Google and told them about it and the put me through LG which want me to send the phone for repairs but not free. My guess is that it will be way to expensive to repair and that is not worthy.
Hopefully someone with real repair skill can give us light if this is something fixable by software.
audit13 said:
Do you need to lock the bootloader? Once locked, you cannot flash anything via fastboot commands, not even a stock ROM.
Click to expand...
Click to collapse
I had two different Nexus 5 phones that were stuck in a bootloop with the spinning coloured KK animation.
Every time I unlocked the bootloader, the bootloader would always re-lock itself when rebooting. Even when I managed to unlock the bootloader, I could not re-flash a stock ROM because the bootloader kept relocking itself.
Whenever I unlocked the bootloader, the phone would only take 2 ot 3 seconds to wipe the phone which is too fast.
In the end, I purchased a nexus 5 with a smashed screen to use its motherboard in my defective N5.
I have never come across a post where someone was able to solve the problem unless they had LG replace the motherboard with a new imei.
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.
Hey everyone,
I have an LG G5 and I'm trying to hardreset it. I can't turn it on because it always goes into "incompatible module" mode, telling me to change the battery. The power button also doesn't work anymore.
I have however managed to get it into fast boot mode. From there I tried to use
Code:
fastboot erase userdata
but it says that the bootloader is locked. I checked with LG and they said that my particular phone (from Australia) can't officially be unlocked.
Now I'm looking for a way to either unofficially unlock it or to wipe all data with fast boot without having to unlock it. I can't use adb because it somehow doesn't recognize my phone, fastboot does.
Thanks,
Josh
Hello there
I bought my SM-A125F\DS a few months ago and rooted it. It was working fine. A few weeks ago, I changed my SIM card, made a phone call and put my phone aside and didn't check it for a couple of hours. When I picked it up again, I saw no antenna bars. Turns out I have no IMEI on either SIM slots (says Unknown in About Phone tab). Since I kept no backups, I download the latest ROM from Samfrew and flashed it using Odin. I also ticked Nand Erase and PIT reset. Still no IMEI. And now Android OS is eating 99% of my memory and it just keeps restarting.
Now I am trying to relock the bootloader using ADB before taking it to a service center. Connecting my phone and entering either one of
fastboot flashing lock, fastboot oem lock, and fastboot oem relock
gives me
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Any help on either step of the way is much appreciated.
P.S. I am no tech savvy. The more detailed your answer, the better.
Cactus1ne said:
Hello there
I bought my SM-A125F\DS a few months ago and rooted it. It was working fine. A few weeks ago, I changed my SIM card, made a phone call and put my phone aside and didn't check it for a couple of hours. When I picked it up again, I saw no antenna bars. Turns out I have no IMEI on either SIM slots (says Unknown in About Phone tab). Since I kept no backups, I download the latest ROM from Samfrew and flashed it using Odin. I also ticked Nand Erase and PIT reset. Still no IMEI. And now Android OS is eating 99% of my memory and it just keeps restarting.
Now I am trying to relock the bootloader using ADB before taking it to a service center. Connecting my phone and entering either one of
fastboot flashing lock, fastboot oem lock, and fastboot oem relock
gives me
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Any help on either step of the way is much appreciated.
P.S. I am no tech savvy. The more detailed your answer, the better.
Click to expand...
Click to collapse
I believe the bootloader is locked in much the same way it is unlocked. Reboot to download mode, hold one of the Volume buttons until the bootloader screen appears, and select the option to relock your device.
Before you do that, though, I would suggest performing a complete flash with data wipe using Odin.
@Cactus1ne
This IMEI bug could be due to rooting.
Try this guide, it helped many people.
Try this guide https://forum.xda-developers.com/t/...y-no-imei-no-sim.4386753/page-2#post-86588571
V0latyle said:
I believe the bootloader is locked in much the same way it is unlocked. Reboot to download mode, hold one of the Volume buttons until the bootloader screen appears, and select the option to relock your device.
Before you do that, though, I would suggest performing a complete flash with data wipe using Odin.
Click to expand...
Click to collapse
Thanks for the quick reply, much appreciated.
I have already tried complete data wipe using Odin; didn't work. But I had totally forgotten about the bootloader screen (rookie mistake). I'll definitely do that after trying what @Jerffelly suggested.
Jerffelly said:
@Cactus1ne
This IMEI bug could be due to rooting.
Try this guide, it helped many people.
Try this guide https://forum.xda-developers.com/t/...y-no-imei-no-sim.4386753/page-2#post-86588571
Click to expand...
Click to collapse
Worked like a charm. Much love to you and @dronkit for the detailed and easy-to-follow guide. I struggled a bit with the stuck on file analysis from Odin and device unauthorized from adb; nothing an xda forum search won't fix though.