so recently my droid decided to take a **** on me
it was going in a bootloop so i decided to sbf_flash the 2.3.0 sbf since it was already updated and it successfully completed flashing as well as rebooting and everything
but now it goes from the motorola logo straight into the bootloader screen and it just says
Bootloader 3.25
Battery OK
OK to program
Connect USB
Data Cable
i tried multiple data/cache wipes and even multiple flashes and i still get this damn bootloader screen
im about ready to toss this thing hahahaha
help please?
I'm having the same issue but mines says D2.37 Battery Ok, etc.
Related
So from the beginning: I SBF'd my phone back to stock a couple days ago and it was working fine. I was rooted bootstraped all that I tried to flash one of the Liberty roms and I was stuck at the liberty fist screen.
I figured the problem was I was on stock 2.3 or whatnot and I tried to flash back to 2.2. SBF again right? Well little did I know my battery was semi low and during the flash process my battery fell below the threshold and now it has an error message on the phone bootloader update screen that says "CODE INVALID."
When I try to SBF it with RSDLite and the 2.3.20 SBF file I get an error that says: Phone is not compatible with multi-interface superfile. (0x703B)
It also doesn't detect what kind of phone it is when I plug it in either. It just says phone[0000].
Am I totally screwed?
boot into recovery (shutdown or remove battery, put battery back into place, press Power+X on the keybroard) and do a full data wipe then reboot.
I had my 4G xoom unlocked and rooted, installed Tiamat 2.2 on it (which then killed the 3G) so I decided to flash back to stock, but somehow screwed up the backup, managed to go back to factory 3G image with the HRI66.zip file I found in another thread. It unrooted my phone and relocked it, but now it's in a constant reboot loop, showing the honeycomb images for nearly 45 minutes now. What's my options? My computer wont talk to it, because I can't even get into it to enable USB debugging.... UGH!
sooo..... I let my device run dead.... then powered it up, went into fastboot mode, which took me straight to the unlock screen.... because I didn't lock it when I unrooted it.... All fixed..... except still NO 3G!!!!!
My Nexus 5 seems to get stuck at the update screen (the standing green android with the spinning polyhedron) after flashing to stock(+unroot) with softbrick/bootloop checked. The flash completed without error. I've left it at this screen for over an hour and not only does it not progress it doesn't even get to the progress bar at the bottom.
This afternoon my (unrooted, bootlocked, stock) N5 turned itself off 3 times while on the charger. Powered back on and then would find it turned off 20 or so minutes later when I checked it again. After the third time it booted to the "Google" screen and would go no further. I tried a hard reset but it gave an error. So I plugged it into my laptop and fired up Wug's NRT, unlocked the bootloader (at which point it got stuck at the same update screen described above for around an hour). I held power till it went off, booted back into bootloader (which showed as unlocked) and performed the flash to stock(+unroot) with softbrick/bootloop checked and ended up at the update animation again. Any thoughts other than RMA?
****Edit: Finally got the phone to boot after fastboot booting twrp. Was able to to wipe the phone (after multiple attemps blocked by can not mount storage/cache/etc/etc errors). Flashed 4.4 and the phone now boots to android BUT radio is non-functional (no signal despite being in my normal coverage area), any attempt to add an APN causes a hard reboot (had to go through all the setup screens again). Additionally, the phone won't turn off, even hard power downs (holding the button for 30 secs) lead to an immediate reboot. Still RMAing but I was able to relock the bootloader.
You really shouldn't RMA a phone after messing it up yourself by using a toolkit when you didn't know what you were doing.
Flash the factory images manually. That should get your phone up and running again.
Chromium_ said:
You really shouldn't RMA a phone after messing it up yourself by using a toolkit when you didn't know what you were doing.
Flash the factory images manually. That should get your phone up and running again.
Click to expand...
Click to collapse
Performed a manual flash with the exact same results. There is apparently something wrong with the hardware (which may explain why it was turning itself off and then wouldn't boot past the google logo.
gallahad2000 said:
Performed a manual flash with the exact same results. There is apparently something wrong with the hardware (which may explain why it was turning itself off and then wouldn't boot past the google logo.
Click to expand...
Click to collapse
Yep, I would agree.
I have looked at multiple guides on this and other sites, googled and tried stuff and I cannot resolve this problem. Hopefully I am posting in the right place.
I took the jump and unlocked the bootloader on my Moto G first generation, XT1034 successfully. I flashed TWRP 2.8.60.xt1034.zip with adb and this was successful. Then I flashed Super SU 4.6 Update and that was successful. I got into trouble I guess when I tried to flash Cyanogenmod 12.1 nightly. I used TWRP to flash via install. The flash had an error, which unfortunately I didn't write down. I believe it was something to do with a partition. However, it looked like the flash failed. At this point and for hours I have been trying to fix the "Warning Bootloader Unlocked Loop I am stuck in.
I have been able to get into the phone and flash via adb commands. I've tried several commands suggest to fix this that I have found in forums. I have tried flashing several recoveries including an older TWRP per the method in this thread, a clockworkmod - and the original 2.8.6.0.xt1034. When I get into the phone bootloader which is available, I have not been able to access any options in recovery. Pushing the power button on recovery leads to a blank screen sometimes followed by a recovery starting or a Motorola Logo starting up and a couple times a recovery. TWRP has started a couple times, but never gets past the intro screen, where it locks up. clockworkmod (clockworkmod-6.0.4.7-falcon.img started once after flashing through adb and gave me flash options. I tried to sideload, didn't understand, went back and the recovery locked up. These recoveries no longer load at all.
Through all of this the "Warning Bootloader Unlocked" logo screen comes up after plugging into the computer (Windows 8.1).
Example, I open the phone bootloader by waiting for the phone screen to go from the "Warning Bootloader Unlocked" screen to blank - it cycles from logo to blank. If I'm quick the phone and hard boot the phone will boot into bootloader. I connect to the laptop through USB. When I toggle to recovery and hit the power button the screen goes blank, the Motorola Logo pops up, goes blank and then the "Warning Bootloader Unlocked" appears. The Laptop then seems to connect and disconnect as the Warning screen comes on and turns off.
The factory selection just goes to a blank screen.
I would really appreciate some advice on how to get the phone back to a state in which I can work with it and try again. It is very difficult wading through all of the information out there. I've learned a lot through this issue, but can't take it any further.
Thanks, Jeff
Solved - Stuck in "Warning Bootloader Is Unlocked" Loop
This resolution took many hours to figure out, but I finally got there with this guide - http://forum.xda-developers.com/showthread.php?t=2542219, this thread - http://forum.xda-developers.com/showthread.php?p=54855457#post54855457 and this thread - http://forum.xda-developers.com/gen...e-firmware-t3042687/post59139823#post59139823.
I tried RSD Lite on different computers and USB cables I could not get the device recognized. So I ended up with the MfastbootV2 method to reload stock firmware, which I found on the firmware thread above - this was big, as my phone is with Wind Mobile in Canada and the link is the right one. The only thing I picked up from a different website was to use a computer with USB 2 ports. This is what I did, but I don't know one way or the other if USB 2 was needed. .
Can't thank you hard working guys enough for the time you take to put these threads together. I'm back up and running. As a bonus, after a big clean up in the process, my phone is running fast again.
Thanks everyone.
Hello Everyone,
I have been trying to help my friend with his soft-bricked G3. He wasn't rooted and had never even played with flashing anything, it just stopped booting one day and would display the "LG Life's Good" boot screen for a few seconds before going black and then just repeating this endlessly. I was able to get into recovery and download mode so I used the tot method to flash back to stock after a hard reset just produced the same results.
When I flashed the stock firmware, everything appeared to work fine, it went through the MiniOS bootup and everything, said success, gave me the hard reset status screen so when it finished I pulled the battery as instructed and rebooted but the phone still has the same issue. I have tried to run factory reset through recovery now that I flashed the new firmware and it still does the same thing, just hangs at the boot screen for a few seconds before going black and then trying again, endlessly.
Has anyone encountered this before? Is it bricked?
Thanks.
The_mamba said:
Hello Everyone,
I have been trying to help my friend with his soft-bricked G3. He wasn't rooted and had never even played with flashing anything, it just stopped booting one day and would display the "LG Life's Good" boot screen for a few seconds before going black and then just repeating this endlessly. I was able to get into recovery and download mode so I used the tot method to flash back to stock after a hard reset just produced the same results.
When I flashed the stock firmware, everything appeared to work fine, it went through the MiniOS bootup and everything, said success, gave me the hard reset status screen so when it finished I pulled the battery as instructed and rebooted but the phone still has the same issue. I have tried to run factory reset through recovery now that I flashed the new firmware and it still does the same thing, just hangs at the boot screen for a few seconds before going black and then trying again, endlessly.
Has anyone encountered this before? Is it bricked?
Thanks.
Click to expand...
Click to collapse
Pretty common prob plug it in to the wall charge see if it boots sometimes it still wont but most of the time it will the battery quality on the g3 is crap they last at most a year with a few exceptions i would first order a battery.