HTC One M7 :: Stuck On Bootloader Screen - How To Get Out Of This Cycle
Sep 6, 2015
So I fell asleep with my phone when i woke up it was on the bootloader screen, I thought this was no big deal and just had it reboot as it boots up it goes directly back into the bootloader. Ive tried everything apart from factory reset.
my x10 mini is stuck in a cycle of switching its self on and off again before it reaches the home screen, been like it for 2 days, was fully charged when it started and drained the battery eventually doing this, put it on charge and it started the cycle again, and i can't connect it to a P.C via usb because it's not on long enough to recognize the device.
had a slight moment where wifi had shut off.. but it fully downloaded.. pressed install.. and it installed.. (i think) but it booted up to the bootloader screen.. says:err: A5,69,25,00,27battery OKOK to programconnect USBData Cable
Totally stock Defy, upgraded to 2.2 and on its 2nd ear speaker.While in the browser the phone froze compleatly, so after waiting a while I pulled the battery, and on restarting it went straight to a bootloader screen.Then when i connect to the PC it, just changes the last line to Transfer Mode OK.I have tried the Start button and Volume rocker switch, but this seems to do nothing. Please tell my "Life proof" phone isn't dead before my 2 year contract is up!? I have tried googling, but all the help I can find, seems to be for people who are rooting their Devices, I would just like to state that is not what I was, or am trying to do.
about a week ago my bb was dropped into a cup of tea (which had sugar and milk in) and i quickly took out the battery and stuck it in a bowl of uncooked rice for a few days. It was working about 2 days ago, except the keyboard was sticky so I turned it off and got some isopropyl alcohol cleaner and followed some instructions on how to open it all up and clean it which i did. Before i cleaned it i turned it on and the loading screen came up, only it gets to about 5 or 10 percent then restarts itself which it then proceeds to do over and over. I have looked into this problem and it seems i need to reinstall the os?
Recently I updated my BBM app, and my phone got stuck in a reboot cycle, I was able to solve that problem when I installed the Desktop Manager, and all was well. However, about a week after I fixed my phone, my regular text messaging started acting up. It first started where I would have one person's entire conversation copied in my main messages. Now it's just getting worse. For instance, I texted my mom, and on my main messaging screen under today, there's are about 15 copies of the same conversation. It does this with EVERY SINGLE CONVERSATION I HAVE. Then, it starts to not even show up in my main messaging, and the only way I can receive my texts are if I go through the notifications button. It's not that my texting doesn't work, it's just that all of this is EXTREMELY annoying, and difficult to deal with.
Have tried holding various keys in an attempt to access a BIOS screen or some such thing to no avail (why aren't cell phones more like computers?). As for how my phone got to this state...
-I wanted to add custom ring tones to my recently purchased Samsung Intensity but found that texting them to myself via vzwpix.com led to a significant decrease in quality and the costs would quickly add up as I attempted to fix the issue by editing the sound files in Audacity and texting newer versions to my phone
-To get around using vzwpix.com, I found a method of putting the files directly on the phone by installing the phones drivers to my computer using Samsung PC Studio 3 and moving them directly to the phone using Qualcomm Product Support Tools. The method is copy+pasted below for reference
-After a while I got the ring tone to how I wanted it and went to delete the experimentation files on the phone. I had done this in the past through the phone's interface without issue (though an attempted file rename had caused a quick freeze which was solved by removing and replacing the battery), but this time it froze when attempting to delete the final file
-The phone would not respond to any keypad presses including the power button, so I chose to restart the phone by removing and putting back in the battery
-The phone will no longer pass the "Verizon Wireless" screen and reboots after hanging on that screen for ~7 seconds
Pasted below is the complete method I used to transfer the files for reference. Other smarter methods may exist, but given the issue I had with vzwpix.com, my lack of a mircoSD card, and my desire to avoid media messaging charges I elected to go with this method. Credit goes to ch from the Mobiledia forums for figuring this out and typing this up. It works beautifully aside from the issue I have had. I suggest that anyone who chooses to use it remove sound files from the phone only through QPST and not through the phone's interface.
Software required: 1.Samsung PC Studio 2. QPST (Or other software to allow you to browse the phone's file system)
1. Install Samsung PC Studio (Will only be used to install drivers for the intensity) 2. Change USB Port Map to "Modem" on your phone a. Go to Settings & Tools > Phone Info > and then press the # button. b. Enter 000000 for the lock code. c. Select option 2 "Port Map" d. Select option 4 "USB" e. Select option 4 "Modem" 3. Plug phone into usb port. 4. Go to device manager and install drivers for the unidentified devices a. The drivers will be located in C:Program Files SamsungSamsung PC Studio 3 5. Start QPST EFS Explorer 6. Browse to brewmodmr on the phone 7. Delete MrInfo.db 8. Drag and drop your mp3 ringtone files into this directory 9. Restart the phone. 10. A new MrInfo.db file will be created. Copy it to your desktop. 11. Edit the file with notepad. You should see an entry for each sound file in the directory, followed by |0|0 or something like that. For the first file change the second 0 to a 2. For the next file change that same zero to a 3, and so on. I guess the second zero just needs to be a 2, 3, or 4. 12. Copy MrInfo.db back to the phone in same directory. 13. Reboot the phone and your mp3 will show up under the "My Ringtones" menu.
Greetings, my phone recently froze on me, and I couldn't even reboot by holding down the power button. Instead I opted to reboot via the Power Button + Volume Down method. This forced it to shut down, but upon rebooting, the phone is now in a loop. It shows the Droid at launch, then makes it to the red eye, but after sitting on the red eye a moment, it freezes, then restarts the cycle again.
Things I have tried:
Forcing another reboot via Power + Volume Down Going into the Boot Mode Selection to use Normal Power Up Going to BMS and trying Recovery (Wiped data/factory reset) Attempted to enter Safe Mode (Didn't seem to work, cycled again at eye) Fastboot Lastly, tried launching to Tools in BMS. Same as above.
At this point I am at a loss as to what to do. I would like to not have to send this out, and to fix it here, but is it comes to that, I guess I'll take it to Verizon and see about getting it shipped out, and getting a replacement.
Oh, also this is a stock phone, the only "modifications" I had was Go Launcher and Go Lockscreen. I was, when this happened, going to check my Google Reader app, and that is when it froze on me. (Never had it happen before this)
My Storm2 running official Verizon .713 has suddenly gotten stuck in a boot cycle. It will reboot, get as far as the "BlackBerry" screen, maybe 2 or 3 % into the progress bar, then it will give the white background "freeze/crash" screen but it only flashes momentarily such that I cannot read the error it is giving, then reboots, starting the process all over again in a seemingly endless cycle. Is there any way I can fix this or do I need to wipe the phone and reinstall everything, losing all my data?
I am an IT technician, and we use BES at my company. I have been handed a phone by one of my fellow employees exhibiting the dreaded reboot cycle problem. Yes, I know there are lots of other threads on this, but some are dead ends and some just rehash the same old thing. I'm not certain, but I think this may be different and deserve its own thread. I am working with a BlackBerry Curve 8310 stuck in the known reboot loop. Black screen for 5 seconds, white screen with hourglass for 5 seconds, black screen for 5 seconds, rinse/lather/repeat.
I have tried: 01) Using BBSAK to wipe the device (without Desktop Manager open or running). 02) Using JL_Cmder to wipe the device (without Desktop Manager open or running). 03) Installing the BlackBerry Java Developer Kit and running the wipe variable command on JavaLoader.exe (without Desktop Manager open or running). 04) Deleting vendor.xml and running loader.exe with and without the /nojvm variable from /Program Files/Common Files/etc (without Desktop Manager open or running). 05) Using BlackBerry Desktop Manager to load the newest OS (hey, why not). 06) Tried every combination possible of booting the phone without the battery and inserting it at just the right time, over and over and over again, while all of the processes above attempt to run (BBSAK, JL_Cmder, Loader.exe, etc). 07) Doing all of the above on a Windows XP Professional PC instead of my Windows 7 Ultimate x86 PC. 08) Doing all of the above on a different BlackBerry Curve 8310 without a reboot problem (it works every time; wipe the OS, install the newest one, no issues at all, I'm very familiar with the process). 09) Trying all of the above using a completely different battery. 10) Trying all of the above with the SIM card removed (there is no media card, so no issues there).
As far as all of the documented steps to resolve this known issue, I've tried them all in every which way using every combination I could possibly imagine or invent on the fly, and I've made absolutely, positively no progress whatsoever. The BlackBerry Curve 8310 continues its auto-reboot-5-seconds-into-loading process, and it prevents any of the utilities above to communicate with the phone long enough to establish a handshake before it reboots again. It doesn't seem to matter when I insert the battery at all. The farthest I get is using the loader.exe method (step 04 above). Once it gets to the device initialization step, however, and I insert the battery back in, the reboots simply continue. I am at a loss, and I've done everything that I know to do or that I've learned to do via research on multiple messageboards. Aside from sending teh phone out for repair, what steps are there to take that I have not yet taken to fix this myself? Note that there is no report of the phone being dropped, jarred, or physically mishandled in any way. Nonetheless, could it be that this is not software-related, but hardware-related? What am I missing?
i recently tried flashing my v3m to altell. But it fail in the process and now it just shows the altell boot then goes to bootloader mode. But when trying to reflash it gets to flash group 2 and fails. I used rsd lite and radio comm. FLASH FAILED: Tx RQHW boot cmd failed. Boot Command: RQHW M-Link error 0008: DeviceIoControl() result falied during USB device I/O.
About 3 years ago i bought an HTC M7. And yesterday i tried to unlock the bootloader for the first time using HTCdev and all went well. I also managed to install CWM at that time. When i tried installing a custom marshmallow rom i received several errors and decided i wanted to revert back. So i relocked the bootloader but now i have no os installed and if i try unlocking the bootloader again i get stuck on white screen with htc logo and purple letter at top entering recovery... After this screen i have to wait for the battery to die before i can do anything with the phone again (stuck)
I have tried flashing a different recovery file but i keep getting remote: signature verify fail. Without unlocking bootloader i cannot get anything to work. I have no working mobile phone atm.
I have a nexus 5 that I was preparing to hand down to my wife. I had transfered everything over to my new phone, and initiated a factory reset. It rebooted to the "erasing" screen, and sat there for about 20 minutes, before switching to the dead android screen (w/ red triangle.) I thought that was odd, did some searching, and tried the recovery mode from the bootloader. That produced the same results. So now I'm stuck.
From the boot loader I can access the following options:
Start -> Erases for ~20 minutes, then dead android Restart Bootloader -> Screen goes blank, phone vibrates, and then back to the bootloader screen Recovery Mode -> Erases for ~20 minutes, then dead android Power off -> turns off the phone
I called Google, and the tech support hadn't heard of anything like this. Because it's almost two years old, he transferred me to LG's tech support, who basically said find a local repair shop, or they could RMA it for an unknown cost.I'm pretty sure the phone is bricked at this point, which is frustrating, because it was running stock android - completely unmodified. I think I might have rooted it once, months ago, but I can't imagine that that would have caused this issue. I had even received and installed Marshmallow OTA, and it was running perfectly.
Anyway, some program I might be able to use on the PC to regain access to my device.
Literally the only information I can provide about the phone at this point in time is as follows: Product_Name - hammerhead Variant - hammerhead D820(H) 32GB HW Version - rev_11 Bootloader Version - HHZ12k Baseband Version - H8974A-220.127.116.11.27 Carrier Info - None Serial Number - 047.... Signing - Production Sercure Boot - Enabled Lock State - Unlocked
Upon turning on my Triumph, the phone states the phrase "Incoming Download Mode" once, then repeats the following message over and over, on a black screen: "polling, get oemsbl_mode = 1". Apparently this is the bootloader mode. I am Not inadvertently or intentionally holding down the volume down button or any other button at the same time as the power button, as many forums mention as the possible problem. I have tried: pulling the battery for hours; pulling the battery and holding down the power key for 30 seconds; pressing the volume up and down keys a lot when the phone is off and the battery out (in case up or down volume button is stuck), then powering up the phone. In none of the above scenarios is the phone connected to anything via USB cord. At the time my phone developed this problem about 48 hours ago, I was simply surfing the web on my phone.
On my lock screen there's a small black bar that says 'Bill Cycle' and has some other information on it and no matter what I do I can't get it to go away. It just stays on my lock screen and therefore I can't see my wallpaper behind it.
Just wanted to upgrade my sisters phone which was running an old 5.1 version (custom rom, so the phone was unlocked and rooted already) to an android 6.0.1 custom rom. So I flashed newest twrp and flashed 6.0.1 bootloader and radio.img via fastboot using wugfresh tool and the files from the thread on here. now when trying to get into recovery, I am stuck at the google logo.
My phone is a HTC M7 ... My phone went flat one day after i charged battery and turned phone on it now goes straight to the boot loader screen which says LOCKED for some reason ... I can't seem to get passed this screen now.
after the reboot the only thing my screen ever displays is garbled colored pixels even after pulling the battery. Fastboot still works just fine, so I tried wiping everything and reflashing but it still never shows anything but this screen. I even tried reflashing older versions of the bootloader and nothing works.
So, I turned on my phone and now it goes straight to the bootloader. So, when I select "Start" option, screen turns black (can still see backlight shining though). It was sitting there for hours, but screen stayed black.
I did have a rooted phone, but I hadn't tinkered with it for about 6 months.
I think its fair to say not all is well in BB Land for many Storm users. 23 months ago the Storm "revolution" began. 11 months later the Storm 2 appeared. And, now, after only 9 months, AT&T has released the Torch. Within all that time countless Android devices have surfaced, the iPhone has held its own, and many other companies have tried to take a piece of the smartphone pie, as well. There's so much temptation out there. I, like many of you, have a sweet-tooth for tech, so when I see another device release with the hype, performance, praise & sales to back it up, I no doubt feel the envy. I remind myself that my Storm2 still functions well and gets me through the day. A new device may provide some fun for a bit, but ultimately, its not going to revolutionize my day by all that much. Now, here's when I do some math.
Storm1 release day $200 something Accessories $100 T-Mobile contract Termination Fee $200 Verizon's monthly access in advance fee $60 I don't remember on what, but prob spent more that day... Signed up for 2-year contract... Approximate Monthly Bill $130 x 11 = $1430 11 months later Storm 2 purchase w/accessories $377.66 Signed another 2-year contract. Approximate Monthly Bill $130 x 10 = $1300
So, I figure Since I signed on with Verizon in October of '08 (21 months ago) I've spent about $3700 to carry the Storm 1 and 2. I think its fair to say, at this point, the Storm 2 is soon to be Obsolete. From all indications, a "refreshed" Storm 2 with enough memory to run OS6 is all I have to look forward to this year, and if I want that for the promo price I'll have to begin another 2-year contract. And how long will it take before the next Storm device is released? See, here's my problem. These companies come out with new phones all the time. Its not just once a year anymore when we see these dazzlers appear. The 2-year contract feels like a trap at this point.
Honestly, I don't mind spending the money on technology. Its one of my favorite things in life. But, at some point, I need to be real with myself and admit that I can't be happy with any phone for half the life of a contract. It would be wise for me to let a contract expire for once and see what the market is like. It would even make more sense for Blackberry to make a phone that doesn't get left behind after 9 months, yet RIM only houses their devices with enough specs to compare with outdated technology. How much does that turn you on? How much does the new Torch commercial turn you on? Its a vicious cycle.
Twice yesterday afternoon and once this am my 9700 power cycled / rebooted itself. This is a pain as I have berry buzz and have to reconfigure my profile as the settings are gone after a power cycle. Do I have a virus? I have Quickpull installed but not configured to automatically run. Do I need to install Quickpull? Any help would be appreciated.
I am not real sure about the exact os number I am using but I do know its 5.0 something. I cant get to about screen fast enough to let you know. But anyway it is in a reboot cycle and will not stop. This worked great for 3 or 4 months then all of a sudden when I woke up this morning it is in a constant reboot. I have tried the tutorial blog on how to recover but it is not working. Anyone have a recomendation for me. or point me to another option to fix this?
The issue I am facing is that my Bold will power up, load 2/3 of the way, then proceed to a white screen with a wiping status bar. It will then freeze around 54% (not always 54%, maybe 48%, sometimes up to 50%), reboot, and repeat.Blackberry is recognized in Loader and Desktop Manager however will fail to connect to JVM because it will repeat the wiping. It does load the software (only if I catch it with the red LED and screen off). I tried the latest desktop manager and the latest updates. I've pull the battery many many times for long periods of times.