I just tried unlocking the BL from my official AT&T gingerbread using this guide, I tried flashing the sbf file with RSD and it got stuck and now my phone stays at this with the difference that mine gives me the option to try fastboot, RSD mode, Android Recover and another pletora of options I'm not sure i want to name.
So being able to try RSD again, i tried flashing this and it was appearently working but when it tried to set the device on BP Pass through mode, the device would go back to the Infamous screen and it wouldn't move from there.
Am I screwed? Do i have option?
I'm going to try to flash the stock FW to see what happens
Kenchinito said:
I just tried unlocking the BL from my official AT&T gingerbread using this guide, I tried flashing the sbf file with RSD and it got stuck and now my phone stays at this with the difference that mine gives me the option to try fastboot, RSD mode, Android Recover and another pletora of options I'm not sure i want to name.
So being able to try RSD again, i tried flashing this and it was appearently working but when it tried to set the device on BP Pass through mode, the device would go back to the Infamous screen and it wouldn't move from there.
Am I screwed? Do i have option?
I'm going to try to flash the stock FW to see what happens
Click to expand...
Click to collapse
use the automatic unlock tool found here:http://forum.xda-developers.com/showthread.php?t=1182871&highlight=automatic
do option 1 then option 3 (only use option 3 if on gingerbread) and you're good to go
Fastboot then use fastboot oem unlock command on PC. Reboot and it should work.
Sent from my MB860 using XDA Premium App
Thanks, I'll try it out and post back
I forgot to mention that my phone seems to be low on battery. Does it charge if it's not on the OS?
Noob Killed his phone
Hello, First time Poster here, please bare with me...
I really shouldn't of touched this.....
I have an Atrix w/ the newest updates to it, and attempted to unlock the phone. Everything started well, then it failed while writing to the device. Now, when I attempt to boot, I get the similar message of
SVF:405;1:2
Failed to boot 0x1000
With a 14 available options. I can get into fastboot, though I honestly am not sure what to do from there. I have the fastboot s/w downloaded, along with the gingerbread OS.
Did I just kill my phone?
I haven't still fixed mine because of the battery, I still have to find an external charger. Though, you can try the link from above.
Ok, I did the steps and now my phone is at a screen with the motorola logo with the dual core name on it and it has the word Unlocked on top of it.
What should i do?
the boot screen with motorola logo and unlock in corner will take awhile to load usually like 10 minutes but if it doesnt load for example i let mine sit for an hour and never loaded i just took the batter o and restart it and it rebooted and worked but use that as a last resort give it some time!
Omg i just fixed it!! Thx for the help!!
Mrniceguy0921 said:
the boot screen with motorola logo and unlock in corner will take awhile to load usually like 10 minutes but if it doesnt load for example i let mine sit for an hour and never loaded i just took the batter o and restart it and it rebooted and worked but use that as a last resort give it some time!
Click to expand...
Click to collapse
i think if the phone can be detected by PC, it should be a soft brick.. it is unfortunate my phone is booting loop and can not be read by PC, you're better than me..
Related
Hey folks,
I'm having some issues with my ATT Atrix. The phone keeps rebooting at the "Rethink Possible" screen. I bought this phone off of somebody on CL. I actually had the phone make it past the att screen a couple times. It made it to the setup up Motoblur screen but when I clicked start it just skipped it and takes me to the "Emergency Calls Only" screen. However the phone would just restart eventually at this screen as well. When the screen timed out I could not get the screen to turn back on at this point unless I unplugged the USB cord and plugged it back in. When the phone was on the Emergency Calls screen, my computer did recognize the phone and it did launch the motorola website. While I had the phone at this screen it did say that it had to force close android.process.com. I am coming from a captivate with rooting and flashing roms so I am familiar with Android. I am just trying to figure out where the problem could be with my Atrix. I am hoping somebody can point me in the right direction. Thanks for your time!
Your best bet will be to SBF that back to stock. Have you tried that yet? If not search for RSD Lite and SBF in the forums. There are several links and guides.
Is it unlocked?
I am not sure if it is unlocked as I cannot get past the emergency call screen. However, I will search SBF and research that option of setting it back to stock. I know when I flashed roms on the Captivate I would enter into recovery mode. I see in the Atrix that I would have to use Fastboot? The only reason I am worried about flashing a rom is that the phone reboots on its own so I would not want to hard brick it if it rebooted during a flash.
If it's unlocked you should see the word "unlocked" in the upper left corner of the boot logo screen, unless it was unlocked then flashed back or fruitcake in which case it will not say unlocked.
You should not have issues flashing from recovery if you have enough juice in your battery, which you maybe don't if you have been letting it sit rebooting. The rebooting is more than likely caused by an issue with a kernel, ROM, etc. Think of recovery as being similar to the BIOS on a PC. You enter into BIOS before the OS boots, etc., and this is before all the hardware has initialized and drivers have loaded, so the problem causing the reboots should not exist at that time. I would definitely try flashing a different ROM, and also a stock kernel.
It never said unlocked when I got the phone to turn on. I am having trouble getting the phone to turn on this time. I have downloaded RSD Lite and the 4.5.91 .sbf file to flash. I am just having trouble getting the phone started. Are there any ways to force the phone on. When I press the power button the green LED stays lit but nothing comes on the screen. When I plug into the charger it shows the moto symbol then goes to the Battery charging screen. Im not sure if the battery is correct because it says BHX5 1500mAh on the battery. Thanks for your help guys!
Update: I can get the phone into Fastboot and then Android Recovery Mode when the phone is plugged into the wall charger. However when I connect the phone to the computer via USB it just shows the green led when the phone is powered on. Anyway I can get the phone to boot into Fastboot while connected to the computer via USB?
Bump. Any way to get the phone to turn on when plugged into the computer or anyone know why there would be an issue of the phone turning on when plugged into the wall charger but only showing the green led when plugged into the computer? The battery shows 100% charged. Thanks
Update: I got the phone into RSD mode and flashed the 4.5.91 sbf but the phone only goes to the Emergency Call Screen. Is there anything else that can be done?
nishith611 said:
Update: I got the phone into RSD mode and flashed the 4.5.91 sbf but the phone only goes to the Emergency Call Screen. Is there anything else that can be done?
Click to expand...
Click to collapse
Did you fastboot -w before flashing the sbf? (Guess you don't really need to when flashing a sbf)
What may also help is flashing the boot.img file from whatever ROM you are using via fastboot.
Don't know if this will help, but it solves an issue when flashing to a different ROM from CM7, so maybe will help for you.
I know this might sound dumb, but do you have a sim card installed? Also, try to boot into recovery and just do a factory reset. @CaelanT already pointed out that this should be unnecessary since you flashed an sbf but it wouldn't hurt to try.
nishith611 said:
Update: I got the phone into RSD mode and flashed the 4.5.91 sbf but the phone only goes to the Emergency Call Screen. Is there anything else that can be done?
Click to expand...
Click to collapse
EDIT: I reread the OP and realized he had already tried to bypass the start screen.
That is not the correct battery. That is actually a battery used for the Droid X/X2. It seems they have pulled a switch-a-roo on you. (Probably because the Atrix battery could be used as an "Extended" battery in the DX/DX2) Anyways, it should still work but you can find the correct battery online, it should be a BH6X and should have a capacity of 1880/1930mAH.
nishith611 said:
...Im not sure if the battery is correct because it says BHX5 1500mAh on the battery. Thanks for your help guys!
Click to expand...
Click to collapse
Thanks for the reply. I tried to get the phone into recovery mode. I get to the Exclamation Point screen but it gives me no options for a factory reset. I saw that you have to touch the lower right hand side of the screen, but this doesn't do anything for me.
As far as flashing the boot.img file for the rom that I used. I flashed the stock 4.5.91 motorola rom. How can I find boot.img and would I flash it using RSD?
Also would it help if I flashed a custom rom instead of the stock Motorola 2.3.4 rom?
Could the battery not being the BH6X rom be the issue for it not getting enough power to stay on by itself?
Thanks for the help guys, I really appreciate it!
No, the sim card was not installed during the flash. However, I did install the sim card afterwards but the phone boots up and goes to the big green battery charging screen and does not go any further. However when the sim card is not plugged in I can get the phone to go to the Emergency Call screen.
nishith611 said:
As far as flashing the boot.img file for the rom that I used. I flashed the stock 4.5.91 motorola rom. How can I find boot.img and would I flash it using RSD?
Click to expand...
Click to collapse
The following are the instructions for flashing the boot.img. this was the solution to bootloops when trying to restore to a different ROM after CM7, but as I said previously, you never know if it will help or not:
1.Open up the Zip file of your current Blur ROM (Ninja, CherryBlur, Alien, etc.)
2.extract the boot.img file and copy to the directory where your fastboot is.
3.Pull phone battery & reinsert
4.Power on phone and go straight to Fastboot mode (Power + Vol Down)
5.Type "fastboot flash boot boot.img" (exclude quotation marks)
6.Once flashed, reboot phone using "fastboot reboot"
Sorry, don't know how to extract the boot.img from a sbf. Did a quick search and couldn't find instructions. Not something I have done before. Maybe someone else can help with this. I don't even know if this will work, but anything is worth a shot when you are stuck.
<edit> Which CWM are you using?
You can flash Romracers via fastboot if you are not using it. This may help you get into recovery.
Update: I got the phone to recognize the sim card and make phone calls and get wifi active. But the phone still reboots by itself. I can use all the functions of the phone except it just reboots by itself. I got into the About phone section and it says
Android: 2.3.4
Kernel: [email protected] # 2
I can get into the Android Market as well as everything else. Could this be a hardware issue that causes the phone to reboot by itself within a minute or so?
Edit: I can get the vol up and down buttons to work while the phone is working but the power button is not responsive to let me power the phone off. Could a hardware issue with the power button be causing the constant reboot loop?
Update: I got the phone to function with the OS working just fine (phone calls, texts, emails, etc..) but it keeps restarting on its own. The power button still does not work however, could this be a hardware issue? Thanks
Hey guys, I just got a Motorola Photon that I was trying to install the Photon Laser P.ROM
I think I messed up trying to install the SBF file with RSD Lite. (Was following these intructions: http://forum.xda-developers.com/showthread.php?t=1202666 but I forgot to restart the phone into RSD mode the first time I did it).
I proceeded to install the CWM Boostrap loader and boot into recovery and try to install the Photon Laster P.ROM. The ROM had appeared to install fine, but when waiting for it to boot for the first time it got stuck in a boot loop where it hung at the Motorola Logo (After the Dual Processor screen).
I went back and re-read instructions and realized I didn't boot into the RSD mode when installing that part, but when I went to try it again I get a "USB device not recognized error" when RSD Lite tries to re-enumerate. The screen on my Photon also gets glitchy... it's a black screen with a bunch of still noise (kinda like a bunch of polluted snow).
Can anyone point me in the direction of how to fix it?
I've tried pulling the battery and trying again. I've booted into Android recovery and whiped Data and tried again, but I'm still stuck.
When I boot the device into RSD mode and I try to run RSDLite with the SBF file from this thread (http://forum.xda-developers.com/showthread.php?t=1202666) it creates the image then just keeps giving me that glitched screen look. I've tried other USB ports, other cords, other laptops.
edit: I can't seem to boot into CWM either, if I have my phone plugged into the wall and turn it on it either stalls at the Dual Core screen, or the screen after that with the pulsing logo.
Go here: http://forum.xda-developers.com/showthread.php?t=1250697 and watch the video about un-bricking your device. you just have to flash the stock sbf file.
R2DeeTard said:
Go here: http://forum.xda-developers.com/showthread.php?t=1250697 and watch the video about un-bricking your device. you just have to flash the stock sbf file.
Click to expand...
Click to collapse
Video points to this thread -> http://forum.xda-developers.com/showthread.php?t=1202666 I had already tried this sbf file yesterday. When I try to flash to it, the phone reboots after creating the image and just goes to a glitched looking screen. RSDLite then failed to re-enumerate.
The video suggests trying different cables or usb ports. I did both of those and even tried a different computer.
edit: Also, the XDA thread linked above has a broken link to its sbf file.
Getting the same issue. Tehxno where u able to fix?
edit: error fixed by downgrading to 154 and then updating from there.
I'm having the same issue although my phone has now been hard reset (with some unfortunate signs of root/rom) and is trying to go thru intitial setup (touch the android) AND IT WILL NOT GO PAST THAT POINT. Just keeps force closing every app in the book.....an fix? other than rsd and sbf
iamanonymou said:
I'm having the same issue although my phone has now been hard reset (with some unfortunate signs of root/rom) and is trying to go thru intitial setup (touch the android) AND IT WILL NOT GO PAST THAT POINT. Just keeps force closing every app in the book.....an fix? other than rsd and sbf
Click to expand...
Click to collapse
go to recovery and wipe. reboot.
Best advice for that issue
Sent from my MB855 using XDA App
Re-enumerate Failed
I have tried EVERYTHING using all the versions with the RSD lite and I cannot get past the re-enumerate step... HELPPPPPPP please. My photon keep shutting off and I lost my WiFi.
Well I got myself into it this time. I have a Rogers Canada XT910 razr. I installed the Arctic rom and lost all my data connection, and all my apps and could not reload them from google play because it says they are already installed. So I did a wipe and reset and decided to try to use RSD to reflash the ics leak. The flash failed, and my phone is bricked. What's guy to do.
Thanks
John
http://forum.xda-developers.com/showthread.php?p=27944788
That's the leak you need I guess.
There's just one Problem. You need an patched Boot. Img and the system signed of the necessary GB Rom.
I've not searched this Thread for an boot. Img. Maybe someone posted one.
I'm not sure, if you can flash the European Fastboot Files, to get an working RazR, till there's an solution for you.
Gesendet von meinem XT910 mit Tapatalk 2
Thanks man. I had already side loaded the leak that you had linked to so I was on ics before I tried the arctic. I will try tonight to install the European version. I'll let you know how it goes.
Well I am at my wits end.
I eventually got my phone to reboot back into the Arctic rom I loaded, but can't figure out how to update this rom or load another. I have tried with RSD to flash a different flashboot files, but they all fail. I have down loaded a few different custom roms and loaded them on my sd card and tried updating my phone from external storage through the Android system recovery utility but action is always aborted. I can't load any apps like rom manager, file manager, or anything for that matter. When I go to the play store and look at my apps it says i already have them all installed and can't load any. What can I do?
Well I can't seem to leave well enough well enough. tried a few more things and now the phone won't boot. It gets to the Motorola logo and turns off. So can I can get to fastboot and recovery or off. Brutally expensive paper weight.
Can help
hammily said:
Well I can't seem to leave well enough well enough. tried a few more things and now the phone won't boot. It gets to the Motorola logo and turns off. So can I can get to fastboot and recovery or off. Brutally expensive paper weight.
Click to expand...
Click to collapse
I bricked my Rogers RAZR too and was able to fix it. It's a matter of finding the correct signed img and flashing it using the fastboot (when starting phone press power and hold volume up if I remember correctly). Will check what the name of the image is and get back to you. I flashed three or so different images before it would finally boot, then I was able to re-root it, install CWM and get back on my feet.:good:
The rom I loaded is European from here.
http://forum.xda-developers.com/showthread.php?t=1760702
I have been bricked before and fixed the issue, but after loading this custom rom the flash I used the first time with RSD does not work. I appreciate any help and I am willing to try what ever. I did not impress my wife with this one.
flash this
http://forum.xda-developers.com/archive/index.php/t-1634223.html
then reboot....it will work
Thanks I will try it after I get home from work today.
[TUTORIAL]
1. Download the empty_radio.img
2. Turn off the Razr
3. Power On the Razr and select Fastboot Mode AP
4. Open the command prompt CMD
5. Go to the folder where the radio is empty
6. Make flash the radio with the following command and then type "fastboot reboot"
7. Rest assured I tested on my Razr this command does not erase the radio
8. This command will only restart the fastboot
9. Now then turn off the Razr holding vol - and power
10. Plug the Razr holding vol + vol - and power and have it start normally
11. Now restart the fastboot screen will not show more ...
This stuff is over my head. I don't know how to do steps 4,5,6. I don't know what to do in command prompt, I can't find the folder where the radio is empty, and I don't know how to flash the radio. I am totally lost.
Does any body have any other Ideas?
Have you tried fastboot with rsd lite?
Sent from my DROID RAZR using xda premium
Yes I have tried flashing several different XML files from different ROM's With RSD lite 5.7. The flash always fails. In RSD it says that my phone is connected, but it does not show my IMEI it just has N/A in that box. When I hook up my wife's phone which is totally stock it does show her IMEI. Could this be part of the problem?
Hello everyone.
I own Motorola Atrix 4g AT&T with 2.3.4 / 4.5.91 Build.
I have read every single thread about Unlocking the bootloader yet I still cannot do it.
First I tried directly the fastboot unlock command for unlocking it but I had an error saying that OEM Unlock is not implemented. Thats OK since the stock bootloader isnt unlockable. So I downloaded RSD Lite as well as the two SBF files (the small pudding and the huge pudding (full version) of AT&T unlockable/pre root) Here is where I got stuck! I have the drivers properly installed and I tried both Windows7 and WindowsXP still i cant get past the boot logo. Here is the situation.
I connect the Phone in RSD Mode. In RSD Lite it shows as NS Flash Olympus and stays connected. When I load the SBF file and press start it gets to 100%. Then phone reboots and RSD Lites says that its waiting for phone to re-enumeration and after a while it gets the error message: Phone[0000]: Phone did not re-enumerate after RAM-downloader was sent.. Phone is still stuck on the Moto Logo untill I remove the battery. If I remove the battery Phone starts.
Am I missing something?
As far as I remember, once you flash pudding the phone will indeed seem unusable. Immediately after flashing pudding you need to go into fastboot and run the oem unlock commands, then you need to flash a custom recovery, then boot into recovery and flash a custom ROM. You miss any of these steps and the phone will very likely not boot.
ravilov said:
As far as I remember, once you flash pudding the phone will indeed seem unusable. Immediately after flashing pudding you need to go into fastboot and run the oem unlock commands, then you need to flash a custom recovery, then boot into recovery and flash a custom ROM. You miss any of these steps and the phone will very likely not boot.
Click to expand...
Click to collapse
The problem is that i cannot flash pudding since I get an error message after the extracting process when the phone is suppose to reboot and flash itself. It just reboots and stays with Motorola logo (RSD Lites gives me the error) and phone freezes untill I remove battery. After that when I power on the phone it just loads normally.
So the problem is that I cannot flash pudding.... simply because phone dosnt reenumerate after reboot....
Bump ...
I want to add that the phone dosnt have backlight in boot menus (ak. background light is turned off but i can still see the options in boot menus)
Also I am not able to install OTA Updates I get a triangle on the screen and phone boots into os with failed to update message.
Else phone is fully functional. I havnet done anything except rooting the phone and doing the tethering and webtop over hdmi hack.
m140n1 said:
Bump ...
I want to add that the phone dosnt have backlight in boot menus (ak. background light is turned off but i can still see the options in boot menus)
Also I am not able to install OTA Updates I get a triangle on the screen and phone boots into os with failed to update message.
Else phone is fully functional. I havnet done anything except rooting the phone and doing the tethering and webtop over hdmi hack.
Click to expand...
Click to collapse
Try this automated tool. There are several options to choose from.
Download tool here.
I just recently joined the rooting community a few days ago. I started by rooting my phone with petes rooting tool, and then sbf'd the phone back to android 2.3.4 before installing boot strap recovery on the phone. I was able to successfully flash the cyanogen 10 mod, with many exceptions. The first of these exceptions is that the phones keyboard did not work at all (unable to active phone, unable to do anything really), so I decided to look this up. I tried almost everything except installing a new gapps which I was in the process of doing when I hit a major roadblock. The problem I ran into was that when I re-installed the bootstrap recovery on the cyanogen 10 rom to get to the recovery mode in order to flash the gapps file, the phone became stuck on the M (dual core) boot screen. I was however able to access the boot menu (power+volume down), and tried to sbf the phone back to android 2.3.4 so that it would hopefully fix all of my stupidity. Little did I know that this would just increase my unluckiness with the rooting process, and the phone now will not boot into the boot screen. When I hold down (volume down+power) the phone simply flahes a screen and then will do nothing until I pop the battery out. After that, i tried simply turing the hone on by holding down just the power button, and it boot to a screen which displays "failed to boot 2" and then below that "starting RSD mode". From this screen I have tried to sbf to android 2.3.4, and also to android 2.3.5 multiple times, and every time it pops up with either an error on the computer, or "sec_exception: febe, 4e, 4e" and then an error on the computer. ANY HELP WOULD BE GREATLY APPRECIATED!!!! I AM OUT OF OPTIONS AT THIS POINT, AND AM STARTING TO PANIC! HELP ME!
Failed to boot, sounds like hardware failure
but you can try ezSBF, link in my list, might work.
sd_shadow's [Collection] of Links for Droid X2
Sent from my Clear using xda premium
vernon428 said:
I just recently joined the rooting community a few days ago. I started by rooting my phone with petes rooting tool, and then sbf'd the phone back to android 2.3.4 before installing boot strap recovery on the phone. I was able to successfully flash the cyanogen 10 mod, with many exceptions. The first of these exceptions is that the phones keyboard did not work at all (unable to active phone, unable to do anything really), so I decided to look this up. I tried almost everything except installing a new gapps which I was in the process of doing when I hit a major roadblock. The problem I ran into was that when I re-installed the bootstrap recovery on the cyanogen 10 rom to get to the recovery mode in order to flash the gapps file, the phone became stuck on the M (dual core) boot screen. I was however able to access the boot menu (power+volume down), and tried to sbf the phone back to android 2.3.4 so that it would hopefully fix all of my stupidity. Little did I know that this would just increase my unluckiness with the rooting process, and the phone now will not boot into the boot screen. When I hold down (volume down+power) the phone simply flahes a screen and then will do nothing until I pop the battery out. After that, i tried simply turing the hone on by holding down just the power button, and it boot to a screen which displays "failed to boot 2" and then below that "starting RSD mode". From this screen I have tried to sbf to android 2.3.4, and also to android 2.3.5 multiple times, and every time it pops up with either an error on the computer, or "sec_exception: febe, 4e, 4e" and then an error on the computer. ANY HELP WOULD BE GREATLY APPRECIATED!!!! I AM OUT OF OPTIONS AT THIS POINT, AND AM STARTING TO PANIC! HELP ME!
Click to expand...
Click to collapse
im not completely sure why you sbf'd after rooting the first time? no need for that. i would read up a bit more if you do get it working, watch tomsgt123 's videos on youtube so you know what youre doing. and you used the Gapps for cm10.1 not our version. that is why keyboard didnt work. read read read.
after reading abain, i guess you were on 2.3.5. and thats why you sbf'd. but rooting was not needed before sbf. hope you have better luck next time .
flash will fail if battery is too low, should be a low battery error though, but maybe not every time.
if it is low battery, you will need a charged battery or a tbh programing adapter
link to TBH adapter and dx2 external charger in my list
Sent from my XT862 using xda premium
Lorenzo VonMatterhorn said:
im not completely sure why you sbf'd after rooting the first time? no need for that. i would read up a bit more if you do get it working, watch tomsgt123 's videos on youtube so you know what youre doing. and you used the Gapps for cm10.1 not our version. that is why keyboard didnt work. read read read.
after reading abain, i guess you were on 2.3.5. and thats why you sbf'd. but rooting was not needed before sbf. hope you have better luck next time .
Click to expand...
Click to collapse
Do you have any advice on where I should go from here then? My phone is basically a useless hunk of technology until i can get it to boot back into cyanogen 10, or sbf it back to an android operating system. The RSD mode always fails when I try to normally sfd, but i have not tried EZ sbf yet..... any other suggestions?
vernon428 said:
I just recently joined the rooting community a few days ago. I started by rooting my phone with petes rooting tool, and then sbf'd the phone back to android 2.3.4 before installing boot strap recovery on the phone. I was able to successfully flash the cyanogen 10 mod, with many exceptions. The first of these exceptions is that the phones keyboard did not work at all (unable to active phone, unable to do anything really), so I decided to look this up. I tried almost everything except installing a new gapps which I was in the process of doing when I hit a major roadblock. The problem I ran into was that when I re-installed the bootstrap recovery on the cyanogen 10 rom to get to the recovery mode in order to flash the gapps file, the phone became stuck on the M (dual core) boot screen. I was however able to access the boot menu (power+volume down), and tried to sbf the phone back to android 2.3.4 so that it would hopefully fix all of my stupidity. Little did I know that this would just increase my unluckiness with the rooting process, and the phone now will not boot into the boot screen. When I hold down (volume down+power) the phone simply flahes a screen and then will do nothing until I pop the battery out. After that, i tried simply turing the hone on by holding down just the power button, and it boot to a screen which displays "failed to boot 2" and then below that "starting RSD mode". From this screen I have tried to sbf to android 2.3.4, and also to android 2.3.5 multiple times, and every time it pops up with either an error on the computer, or "sec_exception: febe, 4e, 4e" and then an error on the computer. ANY HELP WOULD BE GREATLY APPRECIATED!!!! I AM OUT OF OPTIONS AT THIS POINT, AND AM STARTING TO PANIC! HELP ME!
Click to expand...
Click to collapse
mine did the fail to boot thing back in september, i have to get a new x2. Try using a different computer, good luck
vernon428 said:
Do you have any advice on where I should go from here then? My phone is basically a useless hunk of technology until i can get it to boot back into cyanogen 10, or sbf it back to an android operating system. The RSD mode always fails when I try to normally sfd, but i have not tried EZ sbf yet..... any other suggestions?
Click to expand...
Click to collapse
With it powered off, hold power and volume up . See if you can get it into rsd mode . If so, sbf from there . Hope it works .
Lorenzo VonMatterhorn said:
With it powered off, hold power and volume up . See if you can get it into rsd mode . If so, sbf from there . Hope it works .
Click to expand...
Click to collapse
I can get into RSD mode, and the phone seems to SBF okay, until the SBF on the computer displays "failed", and the phone displays an error message. I am also using a fully charged battery during the whole process (my friend has the same phone so i swap batteries out with him to charge).
vernon428 said:
I can get into RSD mode, and the phone seems to SBF okay, until the SBF on the computer displays "failed", and the phone displays an error message. I am also using a fully charged battery during the whole process (my friend has the same phone so i swap batteries out with him to charge).
Click to expand...
Click to collapse
and you tried EZsbf?
try ezSBF
if you can't get it to work, you can go back, try using rsd lite, and look for Driver issues