Ok I am a noob but have looked and tried most everything. Here is my problem my photon is crapping out lots of force closes so I tried to root and unlock it which I did. I had no problems with root/unlock so I then tried to install codename android(ice cream sandwhich) and something didnt work. I ended up in a boot loop so I tried to flash back to 198_6 which all went well until the final reboot. I got a failed to boot 4 error and nothing would fix this I ran pudding unlock sbf and it unlocked and the phone booted up.
So here is my problem I can not lock the phone and it boot it always (after at least 10 flashes with all 3 versions of sbf) it will fail to boot error 4 on me everytime but again sbf pudding and its unlocked and will boot up.
I really want to shove this phone down sprints throat with all the problems but I cant with it unlocked.
I have tried downloading the stock recovery and removing pudding and still boot error 4 run pudding in rsdlite and bam unlocked and phone boots up any help would be great. Forgot to add that I did a reset right before I did the no pudding sbf and all my contacts and apps were gone had to setup the phone from scratch after no pudding boot 4 failure ran pudding had to set up phone from scratch all apps and texts were gone but all my contacts are back?
If someone has a step by step on a new op or something to make this phone stable and stop force closing stuff I will take that also as thats my main concern I need the phone to work.
I really dont understand the lingo and what roms and kernels and stuff are so please dumb it down best you can thanks.
I would like to finish with thank you to all who post and the developers you guys rock.
I had the same problem the other day. Download a 2.3.4 sbf and use RSD lite to install it. Problem solved.
After that I used nandroid to put back my old system backup with all my apps and data right where I left them.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
You have to wipe your system data and cache prior to flashing one of the sbf's to go back to complete stock. Sounds like your SBFing over your custom rom.
Sent from my MB855 using XDA
Related
Hello,
I've been searching the forums for this but basically I did Gingerbreak/Gingerblur 4.5 from the now zombified post. I have since over looked the update 4.5.91 because I don't want to hard brick the phone, but now it looks as though I'm stuck on Gingerblur.
1) I CANNOT restore to factory settings via the phone (Get stuck in Failed to Boot 2 Starting RSD Mode lock out) no matter what I do.
2) After going into RSD protocol support, It will not recognize my phone at all on RSDLite v5.0 (so can't flash SBF files)
3) If I select Android Recovery it will result in "Failed to Boot 2"
I've been looking at the threads for the latest stuff, but none of them seem to address my issue. Any thoughts on how the heck I get this thing fixed? I'd like ideally to get Android 2.3.4 and the latest and greatest, but don't want to brick the phone. Any help would be greatly appreciated
BTW it works just fine in Gingerblur, but I'd like not to be stuck with that forever...
You are not unlocked. Feel free to flash an sbf as hard brick has to do with unlock and bootloader stuff.
My thoughts would be to just unlock your bootloader. Start with the pudding thread
sent from my Atrix via XDA premium
Well, perhaps I should have gone back to stock image first before doing Pudding.
Soft bricked my phone now. Stuck in Failed to Boot 2 - Starting RSD Mode
I will download the 1.26 from here:
http://forum.xda-developers.com/showthread.php?t=991072
and try to do a restore...I hope I haven't screwed my phone up...
I did the same and flashed it back to stock i used rsdlite 5.5 and used my country specific SBF.
It is back to stock but webtop Isnt working
Actually sorry. To clarify, I'm using this thread instead for the SBF.
http://forum.xda-developers.com/showthread.php?t=1125944
Will see if web top is a concern IF the stock file flashes properly...
Being on anything won't effect an sbf flash. Go ahead and rsd to gingerbread. Or pudding
sent from my Atrix via XDA premium
I got it back to 1.26
One thing people don't mention is if you have an older version of RSD Lite it will NOT recognize the phone with the latest drivers...(and there are a wealth of older RSDLites floating around so to a newer person it's not quite evident which is latest)
It's now on 1.26. I will try the bootloader unlock, pudding, etc later when I feel more comfortable...
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?
Hi,
I got a refurb Atrix 4G from AT&T today in the mail to replace my Atrix 4G that had the wifi/bluetooth radio go bad.
Anyways, I attempted to root this new Atrix using the method from here: Atrix Forums root 4G using fastboot.
If you'll note, those instructions omit the 'chmod' command that is found on the instructions here on xda (I downloaded the preinstall.img from xda, since the other link was bad)
After I rooted, (but I have not rebooted) I transferred using USB mass storage everything that was on my old atrix (I told windows to overwrite everything during the copy)
I also used ADB to push Titanium Backup APK.
After that, the phone restarted unexpectedly.
The phone would startup and restart partially through the startup, occassionally I would see the unlock screen for a moment, but usually it would constantly cycle through the Motorola animation then turn off with the green led, then back on.
I figured I messed up the root or something, so I used the Android Recovery to wipe my user data and cache, that didn't work, so I used RSD Lite and pushed the signed ATT 4.5.91 SBF to the phone. I wiped the user data/cache using Android Recovery again after the sbf. Still the same reboot cycle.
Anything else I can try to revive it?
forum.xda-developers.com/showthread.php?t=1421261
This, then SBF again (with the latest RSD lite).
Still broken?
If you aren't unlocked, do so, then maybe try a fruitcake.
PM me with issues.
I got errors from fastboot when it erased system/boot/webstop/preinstall... Trying RSDLite again.. then unlock, will report back.
I erased partitions (with errors see above), rsd'd the OTA locked sbf again, then I unlocked, still rebooting.
I'm thinking it's something hardware-related since the phone will get all the way to the unlock/motoblur setup screen after a battery pull. but will only do the moto-logo after that.
Can I undo the unlock if I need to send it back? It's not clear to me if using RSD lite with the OTA locked signed ATT 4.5.91 sbf will brick it..
tuxp3 said:
Can I undo the unlock if I need to send it back? It's not clear to me if using RSD lite with the OTA locked signed ATT 4.5.91 sbf will brick it..
Click to expand...
Click to collapse
Can't lock it again.
Great, will ATT take it back? I've only had it a few hours and the problems began before I unlocked.
Dunno. I personally haven't read any reports of phones being rejected for warranty because of an unlocked bootloader, but since you only just got it as a replacement for another one, they may scrutinize you more.
Does it seem like it could be a battery issue? I'd like to think it's not, but my old phone had a similiar rebooting problem (although it would reboot well after startup)
Any help/advice would be appreciated, thank-you!
Mine was purchased Mar/11, I had unlocked bootloader, and running Darkside ROM, all was good.
Then haptic feedback/vibration started cutting in/out.
Tried going back to CM7, Aura... no resolution. Read on xda re: some people having hardware issues with vibe mechanism, so loaded up NFHimself's Gobstopper (thanks!) to make phone appear as stock as possible, and took in to Bell for service. Came back from Motorola repair shop, vibes fixed, running GB 2.3.6. Battery life absolutely sucks, which is what started me down this whole road of custom ROMs in first place!! As I said, Darkside was awesome, almost double battery life for same usage.
So... I want to re-unlock and get going again, really unsure where to start. Some have said follow exact same steps and unlocking first time, others say no need to repeat fastboot oem unlock, and others say just jump in at flashing a custom (Romracers) recovery??
I am leery of using RSDlite and IHOP again, heard bad things about messing with .sbf files after phones software has been updated??
I read another thread on here about antifuses, and such, not sure if that's the case, but for sure the unlocked message no longer appears during boot.
The intro on NFHimslelf's Froyo Gobstopper thread alludes to the fact that you need to RE-unlock after flashing it, and now for sure after Motorola techs updated phone, so... kindly, where should I start &/or what steps should I skip to get back to where I was without bricking??
Thanks very much!
Just flash the IHOP unlock SBF. Even if it reports as failing the install just pull the battery then reboot. Should see unlocked on the boot screen. Then boot to fastboot, flash recovery, reboot to recovery and flash your ROM or backup.
Sent from my Xoom using xda premium
d3athsd00r
Thanks very much for your reply! I will try tonight after work and report back!
I'm back in business! Thanks again
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.