When trying to SBF, my phone keeps boot looping. How can I get it to boot?
Bootlooping during the flash sequence?
Well the flashing will bootand reboot the phone during the process.That is normal.
Watch this and skip to 3:40 into it should cover you if this is your problem.
http://www.youtube.com/watch?v=J94VcWk-CJc
No, I meant after it finished.
You flashing with RSD lite?
Yes, I am.
I guess the other important question is, what file are you trying to flash?
/www .holylivingfuck.com/ACS/SBFs 198.7 on here. I tried a few different ones, all with the same results.
So you are sure you ran the RSD flashing till it said to manually reboot the phone?
I havent seen this before but it could be battery level related? The process was interupted due to your battery level being low before starting the RSD flashing process..?
Fixed it, I had to go to recovery and wipe data and the cache.
Good to knwo you fixd it. Was it a hunch or did you find the answer somewhere?
I googled SBF boot loop and came across someone who had the same issue with their Droid 3. Someone suggested to wipe data/cache, the guy did it and it worked for him, so I tried it and it worked for me too.
Related
So I think I may have screwed myself. I was following this guide for changing the battery icon to 1% increments instead of 10%, went to reboot and now my photon is stuck on the Motorola Dual Core technology screen. I can't get adb to recognize it and its been stuck like this for a good 20 minutes. Any thoughts? Am I screwed?
i had this exact problem 3 nights ago
Download rsdlite 5.3.9 , 5.0 would not support the phone.
download either 198-6 or 198-7 sbf found in the devolpment sections
you can flash it with the rsdlite program by booting to rsd, Vol up + power
make sure you have full battery and it will reboot a couple times on its own at the end i had to do a manual reboot but it told me i needed to. your phone will reactivate on reboot
I've been trying to boot to RSD but it seems stuck on that as well.
EDIT: sorry I guess I didn't realize I need RSDlite to make this work. I found a youtube video with links on how to flash this sbf so hopefully this will work. Downloading the 400+mb sbf file now (slow internet so its gonna be ~40 minutes), but after that I'll try flashing.
Are you unable to boot into rsd mode even after pulling the battery? If so then I'm not sure that you will be able to use the sbf file to go back to stock. It's worth a try either way though I suppose if worst comes to worse you can take it back to sprint.
SNAAAAKEE said:
Are you unable to boot into rsd mode even after pulling the battery? If so then I'm not sure that you will be able to use the sbf file to go back to stock. It's worth a try either way though I suppose if worst comes to worse you can take it back to sprint.
Click to expand...
Click to collapse
I didn't realize I needed RSDLite to push the SBF (I really had no idea what rsd mode was). I managed to find a video from qbking on how to unbrick the Photon and follow that. It worked and I am back to where I was.
Thanks guys and a special thanks to Shabbypenguin who helped talk me through the ordeal a bit on IRC.
So I got my Photon up and running again but...I can't make calls with it. I tried to Update profile/Update PRL just to see what would happen but...they both result in force closes on settings and bringing me back to About Phone. I'm going to try and have Sprint reactivate it but...anyone have any thoughts?
You may want to do a factory data reset before trying to flash the sbf again via rsdlite.
Sent from my MZ601 using XDA App
So I managed to reactivate my phone with Sprint. However now I have no data (unless roaming). I read that I may have to update PRL in About phone to get my data back but...whenever I try to update PRL or profile it force closes.
Anything I can do to fix this? I restored everything I had frozen via titanium backup but perhaps something is missing here that is force closing those two?
Durp. Factory reset solved this issue. Data/phone capabilities restored and customization process, take 2, begins now.
Thanks to those that helped again and hopefully this thread will help someone should they soft brick their photon.
.cruiser said:
You may want to do a factory data reset before trying to flash the sbf again via rsdlite.
Sent from my MZ601 using XDA App
Click to expand...
Click to collapse
I am having similar issues as described in this thread with flashing my Photon (back to stock). I forgot to factory reset before I began the flash process and now I can't get access to the O/S so my question is how do you do a factory reset without going into the Android O/S? Can you do this from fastboot/nvflash/RSD?
Ok, simply out of frustration I have exhausted all my options and my phone is acting weird I think. I did the factory reset, tried fruitcaking, and even doing sbf. I am at a stock 2.3.4 however when I want to upgrade to try different roms it is extremely unstable and I always get boot loops. Yes I did try the wiping caches and everything before and even after.
So my question is am I doing something wrong? I had even relocked my device from sbf and unlocked it again by cleaning my device. My phone is rooted and unlocked stock rom atm. I'm not sure what to do at this point but either throw the phone at the wall or sell it.
Please help thanks. I tried searching but I believe my situtation is different.
Let me note that I was able to run the Alien rom just fine on my atrix it is 2.3.4 based I believe.
Have you tried the fastboot wipe option? http://forum.xda-developers.com/showthread.php?t=1421522
I've been using this as of late as some of my flashes (even factory resetting in recovery) have had lingering settings and artifacts.
I will definetely try this when I get home. Thanks I'll keep this updated.
Either it wont boot and it just restarts or it starts to boot and wont complete the process its just an endless loop. I have had it on ICS before but for some reason it took over 20 bootloops and it finally showed... I'm not sure where to start.
bump, that method doesnt work... I still need help any other alternatives please..
Are updating roms on romracers latest recovery or old recovery versions?
So I know there are few threads out there already on this topic, and i read through them, and I think my situation is a little different. I fully Factory reset my phone. I am on .173 right now, but when I go to apply the update, it downloads, reboots, installs about 25%ish, then the icon turns to the droid+exclamation inside a triangle, it reboots to home screen, and a message pops up that the install failed. I have the DRUtility 1.51. I've tried running the update with and without ROOT enabled. I've lost track of what RECOVERY mod im using/running and not sure how to find out what it is, but I think that is what is preventing the update from completeing. I've had Bootstrap installed at some point but that should be gone now since i did a factory reset. I also had clockwork mod installed at some point too. But I assume that is gone now as well due to the factory reset.
Any help would be greatly appreciated!
EDIT: Also my android version shows 2.3.6
Factory resets just clear the data on your phone. You will need to fastboot.
[TSON] said:
Factory resets just clear the data on your phone. You will need to fastboot.
Click to expand...
Click to collapse
sorry for being noob, but how do i do that and what is it? or can you point me to a thread that clarifies that?
EDIT: I found a youtube link detailing a fastboot method complete with RSD Lite 5.6.4 link and FastBoot file links. However, in the video it shows that it restores the phone to android version 2.3.5. This seems to be outdated. Will it still work for my purposes?
My issue is now resolved.
Used Droid RAZR Utility 1.51
Booted into AP Fastboot mode and used the utility to revert to .173
booted phone ran the update without issue.
Thank you mattlgroff for a great Utility.
Okay, I tried to flash the CM10 Rom on my girlfriend's Electrify that's flashed to cricKet (been flashed for a few months) last night. And it would not flash the ROM. I am rooted, I have the bootloader unlocked. CWM installed also. VERSION: will edit when i can boot
She was running CM7 which was very buggy, random reboot issues. So I decided I was going to flash the CM10 Unofficial mod, I tried to install like four or five times. Ran the "Aroma Prep.zip", then tselected install zip from SD. It kept showing the CM7 loading screen and kept bootlooping forever. So I kept pulling the battery trying to reinstall thinking I did something wrong.
NOW HER BATTERY IS DEAD!
I can't turn on the phone, tomorrow morning I am going to try to SBF the stock rom, but don't I need to be able to boot the phone in order to do so? What can I do, my girlfriend isn't very happy.
Okay, as I was typing this, it randomly booted...I can randomly get it to boot. I think the SBF would work I am scared to move to my Windows PC and try to use RSD Lite because it will take another 20-40 min to boot the f#*^@^* phone.
PLEASE HELP!
Tried RSD Lite, got the phone to enter RSD Recovery Mode....Buuuuuut
Code:
Starting RSD Protocol Support
Battery is Too Low to Flash
Does it charge in Clockwork Mod? Guess I will find out.:silly:
I thought that I broke my phone too my first time flashing CM9, Leave it on the charger overnight, and give it another shot in the morning. When I was flashing the first time I didn't have a charger, and it died on my half way through the third attempt at installing, leaving it just as un responsive as yours
My issue was just a user error, double check your files of your rom, re download them if necessary, and go over the instructions with a fine tooth comb.
It's pretty hard to brick these things, and seeing how you were still able to get to recovery is a good sign that it can be fixed.
Worst case, you'll have to start from scratch trying to flash it back to cricket once you get the rom situated.
Good to hear!
Well good news as of now, I put it on the charger and am not flashing the stock SBF.
I will let you know how that goes. I don't know why I was having trouble with the flash though. I had NO TROUBLE WHAT-SO-EVER when I flashed CM7 about two or three months ago. Really confusing why it wouldn't stick and kept bootlooping at the CM7 screen when it said installation complete.
So I am out of panic mode, and I think/hope my girlfriend will be after the SBF is done flashing!:good:
Got error at 99% in RSD Lite
Failed to boot 1
did battery pull and try to SBF again
Failed to boot 1
PwrReason:USB_cable
Starting Fastboot protocol support
How are you charging? Try an AC adapter and maybe a different cable
If you have failed to boot 1, your only option is to unlock it. Flash unlock.sbf.
peetr_ said:
If you have failed to boot 1, your only option is to unlock it. Flash unlock.sbf.
Click to expand...
Click to collapse
Okay i found the file you were talking about...
derpunlock.sbf and it fixed my error.
Now I can boot! I am about to check and see if she still has Root.
My cricKet PRL stuck, my APN settings are still in the phone, and everything is working. Time to root again
help
saiyaneye said:
Okay i found the file you were talking about...
derpunlock.sbf and it fixed my error.
Now I can boot! I am about to check and see if she still has Root.
My cricKet PRL stuck, my APN settings are still in the phone, and everything is working. Time to root again
Click to expand...
Click to collapse
im stuck too everytime i flash it in rsd says svf:106:1:2 sec_exception: b655,wddc,eb help please
I tried to reload the stock 4.5.141 image using the instructions in post 4 of the Solutions to Common Problems thread.
I erased cache, erased userdata, flashed boot and flashed system, and all the messages looked OK. On reboot I got the dreaded message. I can't get back to fastboot.
I have downloaded RSD Lite 6.1.4 and it sees the phone, so I hope it's possible to get something on the phone.
What now?
kjmck said:
I tried to reload the stock 4.5.141 image using the instructions in post 4 of the Solutions to Common Problems thread.
I erased cache, erased userdata, flashed boot and flashed system, and all the messages looked OK. On reboot I got the dreaded message. I can't get back to fastboot.
I have downloaded RSD Lite 6.1.4 and it sees the phone, so I hope it's possible to get something on the phone.
What now?
Click to expand...
Click to collapse
C
Download 4.5.141 sbf use rsd lite..rsd always fixed mine bricked many times.if u was on 234 must lock boot loader use 234 sbf rsd.then go up.to 236
markwoo said:
C
Download 4.5.141 sbf use rsd lite..rsd always fixed mine bricked many times.if u was on 234 must lock boot loader use 234 sbf rsd.then go up.to 236
Click to expand...
Click to collapse
Thank you. I kept looking after I posted, but all the links to .sbf from this forum were dead. I was on Android 2.3.6, build 4.5.141.
The only .sbf I could find was entitled "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf".
Now I need to find someplace to charge the battery to attempt the re-flash. Screwing up the previous flash also killed the battery.
I understand that if I'm "Starting RSD mode" the only thing I can do to get a working phone is flash a .sbf using RSD Lite.
Is that true?
kjmck said:
Thank you. I kept looking after I posted, but all the links to .sbf from this forum were dead.
Click to expand...
Click to collapse
All SBF files have been removed from XDA because they are too dangerous.
ravilov said:
All SBF files have been removed from XDA because they are too dangerous.
Click to expand...
Click to collapse
Can you recommend a "safe" alternative for me?
kjmck said:
Can you recommend a "safe" alternative for me?
Click to expand...
Click to collapse
Did you go through this thread? There's a common solution to the "failed to boot" problem.
That said, there are times when you just have to use a SBF and there is no alternative. However, since dealing with SBFs is potentially dangerous, no one around here with experience will ever recommend you that, nor will they give you support. It's just too much responsibility. Kinda sad to say, but if that is really the case (that there is no other way but SBF), you're pretty much on your own.
It's worse now.
I went back to the linked thread, downloaded Automatic Bootloader Unlock 4.2 and fired it up.
Option 3 only works for people who can get to fastboot. That's not me.
I looked at the bold note below about flashing the 4.5.91 sbf using RSD Lite 5.3.1. So I uninstalled RSD Lite 6.x and installed RSD Lite 5.3.1. When I tried to flash 4.5.91 it got to the end and gave a message "Internal error programming phone".
Now I still see "Failed to boot 4" (NOT 0x1000) and "Starting RSD mode", but now RSD doesn't see the phone.
Am I REALLY SCREWED now?
It's better now.
I tried nottach's way of getting fastboot: hold power and volume-up while inserting the battery.
Once I had fastboot I tried again flashing 2.3.6, with the same result.
I still had fastboot, so I tried to flash recovery using Autounlock 4.2. It failed with
Code:
erasing 'recovery' ... FAILED (status read failed (too many links))
sending 'recovery' ... OK
writing 'recovery' ... FAILED (status read failed (too many links))
My phone came newly-refurbished from Motorola, with 2.3.6 build 4.5.141. I had rooted (but not unlocked) my previous phone and backed up everything with Titanium Backup. I had rooted and restored everything to the new phone, but the system would not allow me to register fingerprints and would not perform a factory reset. So I had tried to flash a fresh system; that's how I got to "Failed to boot 4".
I may still be able to return this phone to Best Buy on the grounds that it would not do fingerprints or resets, so I am reluctant to try unlocking the BL unless I'm reasonably sure it will work, but if I can get to a working system I could at least use the phone.
I have a working Eclipse environment on my laptop. Might this be a way to re-format the partitions on the phone so I can flash recovery, boot and a system?
I reviewed more carefully posts 2 & 4 in the Solutions to Common Problems thread, and realized I had slightly different command files (no fastboot.exe, just moto-fastboot.exe). I downloaded the one specified in the post, and tried to flash AT&TGB234_boot.img and AT&TGB234_system.img (I renamed them to boot.img and system.img).
When I rebooted this time I got
Code:
SVF:108:2
Failed to boot 3
Starting RSD mode
I'm still looking for a way to a working phone.
Try flashing the unlock SBF (pudding) before going to fastboot, and then try flashing boot and system from fastboot.
ravilov said:
Try flashing the unlock SBF (pudding) before going to fastboot, and then try flashing boot and system from fastboot.
Click to expand...
Click to collapse
SORRY for ur problem i know they say sbf are not safe but me i never had 1 single issue using it mine said the same thing and went failed to boot fastboot all i did was plug the phone into rsd used the 236.sbf you mentioned early and restored it back never failed me used rsd over 100 times with 5 different atrixes never had a single issue i can recall...i had to cut a usb cable tape red wire to + and black to - on the battery my phone was in fastboot that was all had to work with but it ran rsd fixed it i have seen failed to boot a few times using rom manager to install recovery before if u can get the sbf u talked about its worth trying i have it but dont know how to share it with u. mine was under warrranty i told AT&T i got the over the air 236 update and it said failed to boot they called motorola moto said give that man a new phone i didnt however share the fact the bootloader was unlocked and rooted and had tried many diffrent roms on it over a period of time but however i did end up fixing it and sent the replacment back.if u are usa att not sure about internation the sbf u mentioned is the 1 i use....not sure what u was trying to do that got u into this the sbf pudding mentioned is safe and have used it in the 234 days but to me since 236 has come out rsd never seemed to me to be an issue..mine is 4.5.151 now they say u cant go back haven't tryed that..lol but i dont use the phone now got me htc one x+ now.hope u fix ur phone man....
ravilov said:
Try flashing the unlock SBF (pudding) before going to fastboot, and then try flashing boot and system from fastboot.
Click to expand...
Click to collapse
THANK YOU!
I knew I had seen "pudding" before, and I found it in the Automatic Unlock 4.2 folder. I had tried doing this from the menu, but it failed. I opened Main.bat and found the SDL command line to flash pudding, and when I did it from the command line it worked!
Installing 4.5.141 from fastboot failed, so I tried to flash recovery but that failed too.
I went back to Automatic Unlock. Unlock completed successfully, but the follow-ons did not. I should have made notes as I went.
I was able to boot the phone into 4.5.141, and installed SuperUser.apk, SetCPU and Titanium Backup * Root. SetCPU runs, so I'm both unlocked and rooted.
If I hadn't seen your message I'd have taken the phone to Best Buy today. Your suggestion was the key. I have my phone back, and you have my thanks.