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.
Related
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.
I have a little problem and could use some help. I was running superclean 2.9.2 and attempted to switch over to the community rom. Before flashing the rom I downloaded the stock CI500_VZW_DL09_ECLAIR.tar.md5 file and attempted to load that with Odin(yes i chose pda). I have used Odin multiple times in the past w/out issues. Well this time my screen went blank on the Odin was stuck on param.lfs. When i disconnected my phone it now boots to the screen with a phone, exclamation point and a computer. I closed Odin restarted my computer and tried again with the same result. I can still access the download mode and CWM. When I try to complete a nandroid restore the phone goes through the whole process and then when I click to reboot I get the same screen as above. My next step was to download DI01package3.tar.md5. I tried pushing this with Odin and it got stuck on sbl.bin. Please help me get my phone back.
I pulled my vortex out of storage the other day to tinker. It was rooted but fully updated stock 2.2.2
When I booted it up, it stayed on the boot animation 20+ minutes, until the battery ran out. I've tried booting it up again but it keeps bootlooping.
I figured I'd just flash a new ROM onto it, but I never put a custom recovery onto it and the only Vortex Recovery I found was this;
http://androidforums.com/getitnowmarketing/330813-all-one-recovery-thread.html
However, it says I need to do on-device commands and stuff to get it working, which obviously isn't an option.
Is there any other way you guys could think to resurrect my old Vortex? My Droid Charge is my phone now, this thing doesn't get much use anymore, but I'd still like to get it back in a usable form.
EDIT: FYI, already tried everything relevant in this thread: http://forum.xda-developers.com/showthread.php?t=1031596
If you flashed stock rom. Try hard reset.
Home+vol down / vol up+ power.
thank you! that button trick did the job!
EDIT:
well, it worked once, but the phone had been uncharged for a while so the battery died, and now i can't get the trick to work again >_<
is there a way to re-flash stock without a custom recovery?
I was having issues with my Motorola Photon Q LTE with the Stock ROM (it has bootloader unlocked and Rooted), but the problem was, when running apps that play video, they wouldn't work (it would just show a white screen with a film icon). Other phones work, just the Motorola Photon Q LTE was having issues with it. So, I figured i'd try another ROM....I had one problem after another with getting ROMs to work. Carbon ROM would install but would force close FaceBook (which is needed), another ROM gave an encryption error. I went between 2 or 3 recoveries and then found someone that said they had a "stock JB" ROM....I was tired and frustrated and wound up just clicking things b/c at this point, I was ready to toss the phone on the ground so hard that it would make it's way to the center of the earth! But, now i'm stuck on the FastBoot screen with it saying "Battery Low" so I can't flash a recovery onto it again. The battery was at 70% when I was in TWRP before that happened....now I can't get even get into Recovery or anything...
Okay, I think I got it fixed now......I managed to get it to take a charge. I had to plug it in, let it get to FastBoot and then push the Power Button....NOT hold it...just push it and it would turn the display off and start charging....its at TWRP now and installing a ROM...HOPEFULLY I can get passed the "Encryption Error" issue...
Last night I tried to flash TWRP just because I wanted to go to a custom ROM- alas, the phone now will not go past the google logo. It usually hangs there for 10-ish seconds and then reboots. Occasionally hangs there indefinitely. It's not a power button issue- the button worked just fine before flashing and I've confirmed it still works normally with a multimeter.
I tried to reflash stock using the Google images and "flashall.bat", which says it succeeded- but the phone still loops. I can get into fastboot, but I get the bootloop even in recovery. Running the similar script through Nexus Root Toolkit always fails on flashing the system partition- usually a buffer error due to a sparse header. Can't even seem to get it to do the "fastboot boot TWRP.img" or whatnot. I've flashed KitKat, Lollipop, and MM stock roms to no avail- they all say they succeed, then continue to bootloop.
I've tried just about everything I've seen on here- but not being able to get into recovery hampers efforts like repairing the persist partition.
Help?
When you boot into recovery, the phone reboots itself? If it does, it could be a sign of a failing power button.
When flashing a stock ROM, are you flashing userdata.img and then performing a factory reset/wipe before booting the phone with a stock ROM for the first time?
When I can get into recovery (without a restart), the phone is totally fine.
I think part of the issue is that the battery ran down while I was trying to do the repair- hence it trying to restart and failing. Power button still seems fine (again, confirmed with a multimeter). I left it plugged in to my iPad charger (since that's a 2A charger) overnight and it was still blinking red in the morning. I moved it upstairs and now I can't even make it that far.
Perhaps the battery was just shot by the time I got the "repair" done, hence the boot loops. Is there any way to revive it shy of cutting open the battery + charging manually (with a bench supply) or just replacing the battery altogether? I may try doing a motherboard swap with my working Nexus 5 just to see if it is in fact the battery.
When the phone is powered off and connected to a power source, do you ever see a flashing red LED? You flashed the correct twrp for the hammerhead?
I would try a new battery because it seems like everything is working.