Related
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..
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
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
Hi guys,
My XT910 ran Cyanogenmod 11, Kitkat Nightly. Tonight an OTA update appeared (something called snapshot or something). Thought it might fix some thing that were not quite right in my version so decided to update. At some point during this process the screen went black then the M logo appeared than the android recovery menu (i can load it). And nothing else. I tried rebooting, wiping cache, reset to factory, nothing works. Copied several ROM on the sd card because i have the option to update from sd. Nada. I gotta tell you i'm on a Mac and i cant change that this week, no Windows till next week. And probably the battery is draining...
What to do?
This is how it goes:
I can not power down the device
It restarts periodically if no action taken
at first the M logo appears
instead of CM logo there is a robot with an exclamation mark inside a red triangle
i can get into recovery menu by pressing the volume keys
i can choose one of the options but nothing else
when applying updates from sd card (stock 4.1.2, nightly rom or snapshot rom) it goes up to "verifying update" then it abandons
Later edit:if i reboot from recovery menu and when it powers off i press pwr and vol- it goes to boot menu. No windows means no adb hence power off from that menu. when i plug in the charger, the M logo appears andstays there. Question: if it does actually charge the battery and i dont fix it before getting a windows, what kind of rom should i flash? Stock?
OK, I tried updating the M10 snapshot today over my current M9 snapshot that I had installed.
As it was updating, the screen went off and then I couldn't get anywhere past the M Logo, pressing the volume keys I'm also able to navigate to recovery etc.. but that's it.
I was not able to boot the phone off and even though the screen was off, I don't believe the phone was off. When I got home, the only thing I knew to do was to flash a stock JB rom using RSD Lite. But when I tried flashing it a few moments ago, it failed - the battery is low apparently. Putting it on charge I can now see a charging logo on the screen that is not centered, but I believe it is charging. Once I've got some juice I will try flashing it again, and then I think it's a whole process of rooting it, installing SafeStrap again, and then starting over with CM11.
I don't know if you can even get RSD Lite for MAC, but it's the only way I know that should work to get the phone back up and running.
Thanks for sharing.
There is no RSD for Mac, nor something similar. But i've managed to set up a virtual xp machine (modern.ie), installed everything, captured the usb port with the phone stating "usb connected". Unfortunately i just couldnt connect the phone to rsd, no matter what i did.
Oh gosh.
I managed to get my phone back by flashing the stock JB rom and then working from there.
Try going to the boot menu thing (hold down all keys) and then navigate to AP fastboot. RSD lite should see the phone in this mode.
But make sure the battery is OK first. I did manage to charge it to 40% and it then flashed after it had some charge. Seemed to flash it a little differently than other times. Also the phone said "Device is LOCKED", but thankfully it all worked out fine. Now I'm on CM11 09/15 Nightly.
Have you installed the Motorola drivers?
Maybe you can't do it through a VM.
Generated on a RAZR Maxx (XT910) using XDA's free mobile app.
d.casper.b said:
Oh gosh.
I managed to get my phone back by flashing the stock JB rom and then working from there.
Try going to the boot menu thing (hold down all keys) and then navigate to AP fastboot. RSD lite should see the phone in this mode.
But make sure the battery is OK first. I did manage to charge it to 40% and it then flashed after it had some charge. Seemed to flash it a little differently than other times. Also the phone said "Device is LOCKED", but thankfully it all worked out fine. Now I'm on CM11 09/15 Nightly.
Have you installed the Motorola drivers?
Maybe you can't do it through a VM.
Generated on a RAZR Maxx (XT910) using XDA's free mobile app.
Click to expand...
Click to collapse
"Device is locked" means that bootloader is locked in our phones,except those few developer edition models.
Sent from my Razr XT910
I'm glad you could do it. Mine seems to charge as well, it's now close to 24h since it bricked and i assume it would just die if it wouldnt charge in that particular state. Fortunately the keys on the Mac keyboard started working again after drinking beer two nights ago so i dont need to trick the virtual machine anymore, but unfortunately i just cannot get the rsd to see the phone on this VM. Probably should try a VM with windows 7 - i guess ill just do that. I have installed the drivers, the VM recognizes the phone (moto spyder adb...) but rsd wont see it, nor the adb driver installer (it needs to identify the device in order to install the proper drivers). I know that rsd is picky when it comes to usb cables, it might just not work with the original cable, but after trying 4 different cables i tend to think this is not the problem
P.S. I'm very upset on Google about killing Motorola and being disrespectful with its own customers (i mean i would have been expecting to be the first to get Android updates, not to wait one year to be able to update from 2.3 and i couldnt imagine they will not roll out RAZR updates after 4.1.2) so my next phone will be a Nokia Lumia. The coolest one, like my StarTac, my V70, my V3, my RAZR...
You maybe successful with a Windows machine
Indeed i was. It was fast and sound, no problems at all flashing stock rom. Though the phone didn't actually charged when plugged in and displaying the M logo. I had to actually sacrifice a usb cable and charge the battery directly.
I have the same problem - I updated to the last snapshot, and did a wipe in safestrap - and got bricked.
Only difference is I can't flash nothing! and in AP Fastboot mode the computer doesn't recognize anything.
Hi guys. So I have been going through xda and Google for hours and hours trying solutions, to no avail. I almost never post on forums for help because I can usually find the solution. Not this time. This is my last resort next to throwing my phone out a window or praying for death's sweet release.
The facts: I have a rooted Xperia Z3v. I tried to upgrade TWRP in order to follow some directions on upgrading to Nougat. I flashed TWRP from 2.8.X.X to 3.X.X.X. I rebooted and it never made it to the Sony logo. Now, if I plug the phone in to either a wall socket or PC it vibrates, endlessly at three second intervals, each time with red LED. If I try to enter flash mode, then its the same but with a brief green led after the red. I can enter fastboot (the only way to stop it vibrating while plugged in) and my PC sees it, including Flashtool, but since my bootloader is locked permanently, I can't really do much with it.
When plugged into the wall-charger, I noticed that the charger's LED changes from "Active" to "Inactive" with every vibration. I'm pretty sure I'm in a reboot loop. The screen is totally dead and there's no logo, but every three seconds it kills it self and comes back.
I have tried everything I could think of.
What I have:
I have the stock firmware ready to go
I have TWRP backups on SD card and PC
I have Flashtool
I think my drivers are good, but not 100% sure
I can fastboot
I'm at my wit's end and losing hope.
Please, I'm open to any suggestions at all.