Hi everyone. I have a problem I can't seem to resolve. I tried updating to the OTA jellybean update a couple weeks ago, it seemed to go ok. I then tried to go back to an earlier version of eclipse rom I was using. Now when I power on the phone I get AP Fastboot Flash Mode (S) (Flash Failure). I can select normal boot and it will go into my ICS Rom that I have loaded in slot 1 after going thru my safestrap recovery program. So the phone is not unusable, just very annoying to use. My question is, how can I get the fastboot flash mode flash failure warning to not show up every time I reboot the phone? I've tried loading the Stock JB Rom from verizon, Blur_Version.6.7.246.xt875.verizon.en.us with RSD Lite, but when I try to extract the files with RSD, I get the error "Please check input file. Either XML format is wrong or image files associated with it are missing." I just want to be able to get a stock rom back on my phone, without any errors when I boot it, I don't care if I have root, safestrap, or anything else, I just want a properly working phone. Any suggestions how to get rid of the boot flash failure warning? Thanks!!!! Richard
Update.... Looks like I really screwed it up now. Tried to rsd lite a JB rom, got about 1/2 way, to copying system image, then hung up. Now when I reboot, it won't even go into recovery or normal mode... Stoopid operator malfunction..... Any suggestions on which rom I can try to install via RSD Lite to help get it back going? It will still go into AP fastboot mode.
He's dead, Jim. Nothing is working, no rom will load, they either fail or hang up. Now both of my batteries are dead, and it won't even try to do anything. Any suggestions?? Guess I'm in the market for another phone. Maybe some of the gurus on here have some advice. Thx.
He's alive, Jim!!!!!
rlg999 said:
He's dead, Jim. Nothing is working, no rom will load, they either fail or hang up. Now both of my batteries are dead, and it won't even try to do anything. Any suggestions?? Guess I'm in the market for another phone. Maybe some of the gurus on here have some advice. Thx.
Click to expand...
Click to collapse
Thanks to some other posts on here, http://forum.xda-developers.com/showthread.php?t=2236980 I tried installing the system and preinstall img files manually thru moto fastboot. They seemed to hang up after a few minutes, but I tried to install the files anyway. Afterwards, I was able to get into recovery mode and do a system wipe and reinstall the JB rom that I had on my SD card. Now a couple hours later, I got the pageplus 4g issue fixed again, and just finished rooting it with the tutorial on XDA http://forum.xda-developers.com/showthread.php?t=2256439.
You guys are awesome! Thanks for all your hard work.
Related
2 nights ago I thought I would have a go at installing ULTIMATE ROM 3.0. I have flashed many Roms on my Galaxy S before and not had a problem yet. I have ClockworkMod Recovery 2.5.1.0 installed.
However, this time- something went wrong. I don't think the installation completed properly. When I tried to reboot the system (to go back into my previous ROM) I wasn't able to. The Samsung logo appeared before the phone booted back into Recovery mode.
I tried to re-flash my previous working update.zip but had problems. I wasn't able to properly re-flash as the Installation would abort for various reasons. After doing cache clearing and data/factory reset I still had no luck. I resorted to reformatting the sdcard. Still didn't solve the flashing problem.
Throughout the whole time I was able to adb into the phone, browse the file system and I could push files on to it and take files off. But Kies wouldn't recognise the phone and Odin isn't able to complete a transfer to the phone (not sure why).
Today, I am able to successfully flash update.zip files (at least, that's what it looks like) but the phone ALWAYS boots into ClockwordMod recovery.
I am fast running out of ideas. Does anyone have any suggestion?
How can I tell if my ROMs are really 'there' but I can't access them because ClockworkMod is preventing them from booting?
hmmm... me too.. stuck in a loop, that keeps going back to the CWM recovery menu, and no matter what i do, keeps going back to it... cant even get to the download screen to flash (again).... here i was thinking no matter what happens when installing custom roms, i can always flash to my stable secure rom, but not this time... need some software that can perform surgical operations, any suggestions?
bradels said:
2 nights ago I thought I would have a go at installing ULTIMATE ROM 3.0. I have flashed many Roms on my Galaxy S before and not had a problem yet. I have ClockworkMod Recovery 2.5.1.0 installed.
However, this time- something went wrong. I don't think the installation completed properly. When I tried to reboot the system (to go back into my previous ROM) I wasn't able to. The Samsung logo appeared before the phone booted back into Recovery mode.
I tried to re-flash my previous working update.zip but had problems. I wasn't able to properly re-flash as the Installation would abort for various reasons. After doing cache clearing and data/factory reset I still had no luck. I resorted to reformatting the sdcard. Still didn't solve the flashing problem.
Throughout the whole time I was able to adb into the phone, browse the file system and I could push files on to it and take files off. But Kies wouldn't recognise the phone and Odin isn't able to complete a transfer to the phone (not sure why).
Today, I am able to successfully flash update.zip files (at least, that's what it looks like) but the phone ALWAYS boots into ClockwordMod recovery.
I am fast running out of ideas. Does anyone have any suggestion?
How can I tell if my ROMs are really 'there' but I can't access them because ClockworkMod is preventing them from booting?
Click to expand...
Click to collapse
myrobelle said:
hmmm... me too.. stuck in a loop, that keeps going back to the CWM recovery menu, and no matter what i do, keeps going back to it... cant even get to the download screen to flash (again).... here i was thinking no matter what happens when installing custom roms, i can always flash to my stable secure rom, but not this time... need some software that can perform surgical operations, any suggestions?
Click to expand...
Click to collapse
Thats too bad guys,and i m sorry to hear that news.I would like to havean answer but i dont...
The fact is that since most people in this forum use some custom roms,and all of us think the same,that we can always go back,so it would be great if you give some more details about what happened to you,and mybe why it went wrong,and it would be even better if one of the BIG guys would give some explanation about this...
I already thinking of not updating my rom anymore,dot want to end up in looping too,so lets see if someone will find something.Good luck guys..
By the way,i didnt get it right,CWM recovery cannot load your backup????
I just got an idea,but not sure if or how it would work or not.
Since you can push file with ADB,if soeone made a clean backup with his CWM (o e mail,contacts,setting saved) and send it to you,so that you log in with CWM recovery and flash that ???
Just an idea..maybe stupid dont know...
Its not very clear if youve tried this already but cant you just boot into recovery through adb? or does that not work either?
Hi, I think I have a major problem with my phone.
When doing a rom install the phone got stuck and did not respond to anything. Eventually got the phone back to life using NVflash. Re-installed the blazing rom from a back up and the phone was back to normal. However less than 24hrs later the phone spontaneously crashed to dead again. Nothing will restore it. Using NVflash again its get stuck at "waiting for bootloader to intialize. I have read all the other similar post and tried all their suggestions...but to no avail. Is there any thing else I could try. Is there a different boot.img file I can use...since this is the only thing that gets loaded when I run nvflash.bat.
thanks for any help you can offer.
You should try to restore a Stock ROM, see http://forum.xda-developers.com/showthread.php?t=1127849.
Or flash another ROM, like Cyanogen or another, to see if the problem still occurs: if it still occurs, it doesn't come from boot.img but from a deeper problem.
I can't even load a recovery image via NVFlash let alone choose a stock rom!
I need some help please. I seem to be in a pickle, though I’m not bricked. (At least, not yet.) So I rooted my phone last night, using [GUIDE][NOOB]Step-By-Step Instructions for New Stock Bionic Owners. Everything went great, and I got root. I followed the guide to get the .901 update, which went fine. Tried the ROM suggested, and liked it. Thought I would try Eclipse v2.1. I installed it, but I like Visual Voicemail, so I decided to use my Nandroid that I did right after root and revert back. Here is where problems started.
After the restore, it wouldn’t boot. Passed the Moto Dual Core logo and hung up. Allowed 10 minutes and after nothing, I flashed back to the backup I made after installing Eclipse. It booted fine. So I decided to go back to stock rom, debloat it how I like it and just run the debloated stock. Here is where problems started. I can’t find a flashable copy of the stock. Just a couple of guides on using RSD Lite. This is for Bricked Bionic’s, but I decided to try it, since one of the guides said it works to get back to OTA.
Downloaded the RSD Lite and the full system file to flash. I put my phone into the mode to flash (Power + Volume Down), unpacked the file with RSD Lite and tried to flash. Got an error.
Failed flashing process. Failed flashing process. 1/15 flash cdt.bin"cdt.bin"-> Phone returned FAIL.; phone connected.
Now, when I reboot my phone, it goes back to the Fasboot Flash Mode screen saing (Failed). I can boot into recover (Volume Up + Volume Down + Power) and do a Normal Boot, and it boots fine.
I tried a Factory Reset, and it just reset’s on Eclipse v2.1.
I want to simply get back to stock. Rooted or unrooted, I don’t care. I’ll reroot if I need to.
I also tried to download the STOCK Deodexed files. The links are dead. Figured if I went back to one of those stock images, I could unroot and see if everything was ok.
Suggestions?
Hmm..I think your mistake was in safeboot when you tried to go back to original back up you were suppose to toggle safe system so that it would be disabled. From there you would've been able to restore your original system and boot up just fine. It was mentioned in the guide through some posts.
Sent from my DROID BIONIC using Tapatalk
ms0chez said:
Hmm..I think your mistake was in safeboot when you tried to go back to original back up you were suppose to toggle safe system so that it would be disabled. From there you would've been able to restore your original system and boot up just fine. It was mentioned in the guide through some posts.
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
So I need to turn Safe Mode off in SafeStrap and flash? I had thought about that, but I was worried about totally bricking the phone. I'm pulling SafeBoot now, and will try the flash.
EDIT...
SafeMode is off, and rebooted. I'm back to .875 Stock Rooted. So far, so good.
I can either flash from here (haven't tried yet) or stay here. When I boot, I'm still booting into Fastbook with (Flash Failure). Any way to get that off, other than flashing back to stock and locked through RSD Lite?
Your mistake was trying to restore from the un safe system. You can toggle safe system and you'll be ok. Or, reinstall a ROM to your safe system.
To clarify: don't flash a ROM with safe system disabled. toggle back to safe mode, and then pickup my directions from the format /system step. You can try another ROM no problem then.
I bet you can find the visual voicemail APK and add it whichever ROM. Copy paste into system/app directory.
Thanks. I'm used to flashing with the Thunderbolt and the XOOM. Not used to safestrap, just normal CWM.
Any idea how to stop the phone from booting into Fastboot? Having to do it the long way still. I'd be happy staying this way, if I can get that resolved.
Actually the problem was you tried to restore to a backup of a pre .901 system which has different radios which flashing doesn't like.
As for the flash failure, get the fxz files and put them in a folder with adb and fastboot. Then run this command in a prompt:
fastboot flash device_tree.bin
When you get a flash failure you just need to flash something to fix it; flashing device_tree.bin won't affect anything.
Its one solid file with a weird extension. Is there a way to unpack it? I am out right now and don't know the extension by heart.
Its a zip, just extract it
Sent from my DROID BIONIC using XDA App
Now, I'm scratching my head. (Again) I've worked with ADB with my Xoom, so I'm not a noob at that part. ADB doesn't see my phone. My computer does, and the phone know's it's plugged in. However when I try to flash the file, it can't find the device. I checked "adb devices" and it's not on the list.
So I decided to go ahead and flash completely back to stock with RSD Lite. Still get's the same error message. (I did check the MD5 SUM on the file. It's correct.) Safe Mode is off in Safestrap. Here is what the Fastboot screen looks like on my phone.
AP Fastboot Flash Mode (S)
0A.61
Battery OK
OK to Program
Transfer Mode:
USB Connected
Since I've not seen the Fastboot screen on this phone until this started, I don't know if the (S) has meaning. Like, it thinks the phone's still in SafeMode?
I noticed one of the options in safestrap is to disable safestrap. Thought about trying that, but.... Unsure.
I just installed safestrap, and planned to install the darkdroid rom. it was all going according to plan, until it wasn't
Booted into safestrap. made my initial back up. wiped data/cache. Installed rom from zip. Bootloop. I can't get past the safestrap menu. screen just goes black. sometime it will start over again sometimes not.
I tried using safestrap to recover. same issue.
I was going to use RSDlite to try to recover, but it won't let me select AP fastboot. nothing happens when I hit the up volume-up key to select ap fastboot. RSDlite does not need to see my phone.
I just need to get my phone back. at this point i do not care what i have to flash, i just need it to work! Thoughts? any help? I need it
well.... not so dead in teh water i guess.... just disabled teh safe system, and booted back to original.
but still do not know what happene with the install of darkdroid. Any thoughts on what i may have done wrong? does it matter if i download the zip to my pc and then transfer to sdcard, or shoudl i dl it right to the phone?
heart attack averted, but still need help updating my POS
There shouldn't have been a problem, although i usually just download via my phone. try downloading something stable like liberty or mavrom or an earlier steel droid. If it still messes up then you know the problems on your end. Sounds like just a bad flash though try downloading it again from your phone with a good constant wifi connection and try again.
I tested a few roms that only worked with bootstrap and not safestrap. Try installing it in bootstrap
EDIT: Wish I could delete this. Just found a post about how to fix this...but it involves opening the phone and messing with the hardware. Wish someone could walk me through it :s
So, I hope I didn't, but here is the scenario:
Wanted to install Lollipop ROM from KitKat...tried, failed, found out I needed to have a downgraded radio. Okay...use LG Flash Tool to give myself another try. Load up Jellybean...couldn't figure out how to flash custom recovery in Jellybean as all tutorials are outdated or just didn't work when I tried them, so I thought the best way to do it was to get the Kitkat OTA from Verizon and let it install, then flash a custom recovery (since I figured out how to do that with Kitkat...Autorec), then flash the old radio then the Lollipop ROM and voilà. However, when waiting for the download for Verizon OTA, I tried again to install a custom recovery, and when tried to load it, I just got a black screen. So I just decided to go back into the Android OS and install the OTA once it finished downloading...
The OTA finished downloading and I clicked install, my phone then rebooted...and stupid me didn't even realise what I have just done. The OTA tried going to recovery mode to install...but there's nothing there. Now I am stuck at a black screen that is trying to start recovery mode and when trying to reboot and get into download mode, it won't let me and just goes to the broken recovery mode.
So...can't really think of any other options for me. What can I do? When I plug it into my computer, it connects my phone as like 20 different drive letters that all say they need to be formatted.
So my question is...what can I do?