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.
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 here is my problem, i've wiped my phone so many times to try out every rom/kernel that is posted. The last time i clicked the wrong file to sbf to unlock it and ended up flashing the 235 electrify pudding sbf. (had them all in the same folder...dumbass)
I was able to get rid of the 108 svf error by flashing the boot.img back to the photon ones via fastboot. But still would get the 106 anytime i went to try and flash the sbf.
I've tried in Ubuntu as well as windows 7 to flash it back but nothing has worked since it wants a 235 sbf, and it locked the bootloader.
So I said screw it and tried flashing the electrify 2.3.5 and it loaded up and everything, but i'm stuck on the activation screen and cant get past it. (tires to activate through Verizon)
The 2.3.5 update also removed the bootloader unlock in fast boot even with the id number.
So as easy as it was to flash it right to the electrify sbf, i think once the sprint 2.3.5 sbf is out i should be able to go back. Or once an unlock is found to unlock the bootloader, i can flash the files via fastboot.
I haven't tried messing around with nvflash, since my computer doesn't show the apx when its in that mode.
Update: Was able to bypass activation by booting in to "Boot Android {No BP}" like on the droid x2.
Did you get bootstrap working?
TrojanZulu said:
So here is my problem, i've wiped my phone so many times to try out every rom/kernel that is posted. The last time i clicked the wrong file to sbf to unlock it and ended up flashing the 235 electrify pudding sbf. (had them all in the same folder...dumbass)
I was able to get rid of the 108 svf error by flashing the boot.img back to the photon ones via fastboot. But still would get the 106 anytime i went to try and flash the sbf.
I've tried in Ubuntu as well as windows 7 to flash it back but nothing has worked since it wants a 235 sbf, and it locked the bootloader.
So I said screw it and tried flashing the electrify 2.3.5 and it loaded up and everything, but i'm stuck on the activation screen and cant get past it. (tires to activate through Verizon)
The 2.3.5 update also removed the bootloader unlock in fast boot even with the id number.
So as easy as it was to flash it right to the electrify sbf, i think once the sprint 2.3.5 sbf is out i should be able to go back. Or once an unlock is found to unlock the bootloader, i can flash the files via fastboot.
I haven't tried messing around with nvflash, since my computer doesn't show the apx when its in that mode.
Update: Was able to bypass activation by booting in to "Boot Android {No BP}" like on the droid x2.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Was able to root it via the photon torpedo, even though it says it fails, it wont install the apks from the root program but it is rooted. Just downloaded them off market and ran root updater.
Was able to get system recovery to install and booted in to it just fine. but it soft bricks after i install the skiny4g zip file, boots up the first time all the way to the US Cellular boot screen then resets, and then loops the Moto Dual Core icon. Tried the "Boot Android {No BP}, and same effect, also tried just wiping cache and then wiping the system and still the same results.
Update: Finely got Skinny4G to boot, took 3 tires and the last time i wiped system 2 times in mounts and storage, shows up as sprint and 2.3.4 and its looking at sprint wireless towers, just trying to activate it now.
Phone activated on sprint, 3g works with out any issue, but the wifi and 4g is dead, now i just have to wait for the electrify unlock or 2.3.5 sbf for sprint.
Hey man, i did the same i flashed 235pudding by mistake, so i tried using the 2.3.5 sbf form electrify and it was going great until !switching phone to bp.. something else" then it stopped on 99% and failed to flash... i waited for 5 minutes just to be sure nothing else happened... it didnt
Then i pulled battery and powered the phone again this time it didnt said the "failed to boot 2" but it didnt started it just sits on the motorola dual core logo.
I pulled battery and powered it trying to go into RSD mode and it just doesnt appears :O
I pulled battery and tried to go into fastboot and doesnt appears either.... i just can turn it on and it sits on moto logo.... any help ideas? Tnks
__________________________________
Edit: I pressed vol up and down while power button and it finally appeared RSD mode.... but battery too low to flash, im gonna charge the battery on an external charger for an hour and report later if RSD lite actually recognizes the device.
_____________________________________
YEAH! After charging battery the process completed, im an international user so its not very imporanto to me Spront or US cellular, the phone boots good without my sim... but as soon as i put it in it says " modem did not power up (0)" so...
Does Anyone knows where to go form here?
Thanks
jokersax11 said:
Did you get bootstrap working?
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Bootstrap install just fine after rooting.
Unbrick yourself
I want to thank Koriotto and everyone else who suggested and or tried the idea of flashing a 2.3.5 rom to save our backs. Now to everyone who has flashed 2.3.5 electrify pudding into their photons:
Disclaimer:
1°This will bootlock your phone until a working pudding for 2.3.5 is released.
2°I have no idea whether this will work with sprint whatsoever since I can't try it out being an "international" user, but at least your phone won't be a total brick. However, my common sense tells me this most likely won't work with Sprint.
3ºThere is a leaked Photon 2.3.5.sbf lurking amid devs, but as far I know it hasn't been released to the public yet. However, in case you do get ahold of it, please provide me the link so that we can try it out and see if we can help the Sprint folks get back to a stock Sprint rom. "Internationals" most likely won't care.
1°Try to get as much juice as you can into your battery.If you can, use someone else's fully loaded battery or charge yours with an universal battery charger (extremely cheap and easy to find). Your phone won't charge while in rsd or fastboot mode.
2°Download and install the appropriate Motorola drivers (x32 or x64 according to your windows flavor)
3°Download Electrify 2.3.5 SBF from here: https://rapidshare.com/#!download|8...19.0-19-release-keys-signed-USC-US.rar|530398
4°Get your device into RSD mode. If your loader says RSD mode, go to step 5. If your loader says nothing or is stuck on "Flashboot", don't worry. Power off your device and then press Volume down + power. The phone will turn on and then off. Then power on normally and you will be on RSD mode. If this doesn't happen the first time you try it, just keep repeating the forementioned process until you get into RSD mode.
5°Flash the SBF file you downloaded with RSD Lite
6°Live to win!
UPDATE: link from Team US Cellular seems to be down. I'll personally upload the file once I get home tonight.
Yeah. Praise US Cellular.
Sprint can I haz 2.3.5 yet?
Thanks so much for unbricking my Photon
Worked like a charm for mine !
Thanks !!!!
firtermish said:
I want to thank Koriotto and everyone else who suggested and or tried the idea of flashing a 2.3.5 rom to save our backs. Now to everyone who has flashed 2.3.5 electrify pudding into their photons:
Disclaimer:
1°This will bootlock your phone until a working pudding for 2.3.5 is released.
2°I have no idea whether this will work with sprint whatsoever since I can't try it out being an "international" user, but at least your phone won't be a total brick. However, my common sense tells me this most likely won't work with Sprint.
1°Try to get as much juice as you can to your battery.If you can, use someone else's fully loaded battery or charge yours with an universal battery charger (extremely cheap and easy to find). Your phone won't charge while in rsd or fastboot mode.
2°Download and install the appropriate Motorola drivers (x32 or x64 according to your windows flavor)
Click to expand...
Click to collapse
the download link doesn't work,would u plz give u a new download link,I need to unbrick my phone.
Thank u.
motiam4 said:
the download link doesn't work,would u plz give u a new download link,I need to unbrick my phone.
Thank u.
Click to expand...
Click to collapse
Original link went went down. Already corrected with one from Team US Cellular. Happy downloading
any updates with unlocking the bootloader for 2.3.5 flashed from sbf?
Hey guys, i think i bricked my Atrix. I was trying to flash CM7. The phone is rooted, SIM unlocked, and was running the stock 2.3.4 ROM on ATT 4.5.91. It was fully funtional (well aside from endless reboots, hangs, crashes, etc) until this evening. it wont get past the dual core screen. i need this damn thing for work. preferably by tomorrow.
heres exactly what i did, in order, and with whatever versions i was able to remember.
I snagged the latest CM7 ROM, Dec 10.
Also snagged ATT latest radio ROM.
had Clockwork Recovery installed already
-DEVICE IS ROOTED, BOOTLOADER UNLOCKED AND SIM UNLOCKED-
batch backed up all user apps
attempted to boot into CWM recovery with power+vol down
-kept getting android exclamation point icon
-plugged phone in and went via CWM (when it boots, if its plugged in i get into recovery mode)
went to backup and restore, made backup of internal SD card to external SD card
installed CM7 ROM from EXTERNAL sd card (just noticed it says to install from INTERNAL SD card)
did NOT data wipe/factory reset, was rushing through and totally forgot
DID wipe cache partition
installed latest radio ROM
attempted to reboot
all i get is the dual core screen.
can i reflash, wipe, or reset it via RSD lite, or some other way? NV flash? any help would be great; i have an old HTC tilt i can use but good god who wants to use THAT nowadays?
...and btw i am not so much a noob as much as i am impatient; i rushed through this (i have screwed with this phone and others a lot, and should have paid more attention. i JUST finished building 2 home server rigs tonight, including manually recovering files from some fools RAID0 arrays and got cocky
Have you tried redoing the process? Doing proper wipes and then installing cm7? Also, how long did you wait until you decide it was no good?
let's say if you can still go into CWM recovery, you can try factory reset, and then do the installation form the zip again. don't forget to wipe the data this time, but according to what you've written, you only see triangle with exclamation mark (default android recovery??), then may be you can choose RSD mode at the start-up and flash a stock ATT Rom first, then, follow the correct footsteps. Don't worry, Atrix is really hard to be bricked totally.
i cant get past the dual core screen, but i do have access to RSD lite and it sees the atrix, so im waiting for the same stock 2.3.4 rom to download, flash, and retry (correctly this time). thanks so far! i have NEVER been able to access recovery via vol down and power for some reason on this phone.
EDIT/UPDATE
well, attempting to flash the original SBF via RSD lite 5.6 didnt help; now i get the dual core boot screen, but i cant enter RSD protocl support OR anything via power/vol down, and upon turning it on, the screen no longer says 'unlocked'. awesome.
i get to 99% flashing the stock SBF, and get this message. RSD lite is no longer recognizing the phone, vol up and power does nothing, basically i have the dual core screen and thats it.
'Error switching phone to BP Pass through mode'
...thoughts?
spiderx_mm said:
then may be you can choose RSD mode at the start-up and flash a stock ATT Rom first, then, follow the correct footsteps. Don't worry, Atrix is really hard to be bricked totally.
Click to expand...
Click to collapse
DO NOT take this advice! Flashing SBF after unlocking bootloader can absolutely be the fastest way to brick your phone. Also, it is very easy to brick your phone!
Can you get into fastboot?
Try a full wipe per below:
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
If you can't get into recovery, you can flash the ROM through fastboot, and also flash romracers recovery.
This will give you the cleanest install. After flashing CM7, leave your phone sitting until it boots into the OS, which can take 15 minutes. I believe the long first boot times after flashing are due to the kernel being flashed with the ROM. Then leave it another 10 minutes before flashing the radio, (latest radio for ATT Atrix is 36P radio found in the Fruitcake thread).
yes USE FASTBOOT
Sent from my MB860 using Tapatalk
ok things have now gotten VERY strange. First off, my Atrix was SIM unlocked, bootloader unlocked, and rooted on 2.3.4 4.1.91.
for over 5 hours i tried everything, figuring it was hard bricked. i went to sleep, with the intent of heading over to ATT to get it replaced under warranty.
...power it on just for the hell of it, and IT BOOTED. stock 2.3.4. does NOT accept the t-mobile sim (NO LONGER SAYS UNLOCKED ON BOOT SCREEN), and apparently is not rooted OR bootloader unlocked from what i can tell. i had left the battery out the whole time, but left it plugged into the wall charger.
so now i guess i root, BL unlock, SIM unlock, and CORRECTLY flash CM7... FUN!
UPDATE
Rooted, bootloader unlocked, SIM (still) unlocked, and running CM7. thanks to everyone! i still have NO IDEA how it went from a hard brick to a stock boot, with locked BL and no root.
Your bootloader won't lock again and when you do a stock sbf it will get rid of root.
Sent from my MB860 using Tapatalk
i am aware the BL cannot be locked again, i went through the process mostly because i wasnt sure, my phone no longer said unlocked in the top left, so i also checked to make sure it was SIM unlocked. i have NO IDEA what/how i did what i did, but im up and running CM7 now, so no worries.
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)
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