While trying to root my phone using using briefmobiles instructions (http://briefmobile.com/motorola-atrix-4g-root), i rooted successfully. I then wanted to unlock my boot loader to add a rom using theses instructions http://forum.xda-developers.com/showthread.php?t=1167373&highlight=IHOP
While doing this i go to step 2. H) and my phone did not reboot to andriod it booted to a black screen that said SVF :105:1:2 Failed to boot 0*1000. Occasionally if i take the battery out and put it back in and turn the phone on it will come up with a list of things to do and if i dont choose something on the list in 5 seconds it will go to RSD mode. But it doesn't go to RSD mode it will go to Fastboot protocal support. I also have a choice to push the volume up button and selected something on the list and if i select RSD, i tryed to flash back to the original firmware but the device is not shown on RSD Lite. AM I BRICKED!!!????!!!
You are not hardbricked but softbricked. So don't panic. As long as you have that list you're fine..you want to get into fastboot.
Just follow the fastboot oem unlock instructions ...
Sent from my MB860 using XDA App
Unlock your atrix bootloader
1. Put the phone in RSD MODE
a) power the phone off
b) hold power and hold volume up
2. Flashing pudding
a) open rsdlite
b) connect the phone to the pc
c) click the ...
ATT USERS
d) browse and find C:\atrix\183_pudding.sbf
INTERNATIONAL USERS
d) browse and find C:\atrix\IHOP_Bell.sbf
e) select the phone in the lower panel after the status area says "connected..."
f) click start
g) wait for the flash to complete and reboot the phone
h) after the phone is all the way back in android to the lock screen unplug the phone
i) power the phone off
j) close rsdlite
3. Put the phone in fastboot mode
a) power your phone off
b) hold power and volume down
c) hit volume up (this should start fastboot mode)
4. Unlock the phone
a) open a command prompt on your windows pc
b) type the following in the command prompt
cd C:\atrix
fastboot oem unlock
c) it should then display something like the following in your command prompt
Unlocking your device can permenently VOID your warranty.
This process cannot be reversed. If you wish to proceed,
reissue the unlock OEM command containing the unique ID
of your device: XXXXXXXXXXXXXXXXXXX
OKAY [ 0.002s]
finished. total time: 0.002s
d) type the following replacing XXXXXXXXXXXXXXXXXXX with the unique ID from the previous command prompt.
fastboot oem unlock XXXXXXXXXXXXXXXXXXX
e) Type the following to reboot your device
fastboot reboot
This???
yes..
When you boot up your phone and you get that list...you want fastboot..
you should be here...
3. Put the phone in fastboot mode
a) power your phone off
b) hold power and volume down
c) hit volume up (this should start fastboot mode)
4. Unlock the phone
a) open a command prompt on your windows pc
b) type the following in the command prompt
cd C:\atrix
fastboot oem unlock
c) it should then display something like the following in your command prompt
Unlocking your device can permenently VOID your warranty.
This process cannot be reversed. If you wish to proceed,
reissue the unlock OEM command containing the unique ID
of your device: XXXXXXXXXXXXXXXXXXX
OKAY [ 0.002s]
finished. total time: 0.002s
d) type the following replacing XXXXXXXXXXXXXXXXXXX with the unique ID from the previous command prompt.
fastboot oem unlock XXXXXXXXXXXXXXXXXXX
e) Type the following to reboot your device
fastboot reboot
When i try to go into fastboot it says "Starting Fastboot Protocol support"
then under that it says "Battery is too low to flash"
What should i do?
timeshare1234 said:
When i try to go into fastboot it says "Starting Fastboot Protocol support"
then under that it says "Battery is too low to flash"
What should i do?
Click to expand...
Click to collapse
attempt to fastboot oem unlock anyways, if it doesn't work then you'll have to manually charge the battery with a USB cable, or use a battery from someone else's Atrix.
I tried to fastboot oem unlock but when i unpluged it from wall charger to computer, the phone turns off and wont turn back on unless it is connected to wall charger.
timeshare1234 said:
I tried to fastboot oem unlock but when i unpluged it from wall charger to computer, the phone turns off and wont turn back on unless it is connected to wall charger.
Click to expand...
Click to collapse
take out the battery, and plug into wall charger, place battery back into phone after it goes into charging mode and let it charge for half an hour or so. then try fastboot oem unlock again.
Like a wall charger where the battery (and only the battery) is connected to the charger? Kinda like a camera charger?
timeshare1234 said:
Like a wall charger where the battery (and only the battery) is connected to the charger? Kinda like a camera charger?
Click to expand...
Click to collapse
no, the wall charger that came with the phone. plug the phone up to the wall charger, without the battery in it. it will induce a charging mode for the phone, where you can't access anything but the screen will have a battery display on it.
after you get into charging mode, place the battery back into the phone and allow it to charge.
When i plug the phone into wall charger without the battery the screen displays
"SVF:105:1:2"
"Failed to boot 0x1000"
timeshare1234 said:
When i plug the phone into wall charger without the battery the screen displays
"SVF:105:1:2"
"Failed to boot 0x1000"
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=EQ6JNCvIe8k
charge your battery with this method then, and remember to never start modifying your phone without a 100% charge
It wouldn't charge...am i screwed?
I know what battery symbol you are talking about i have seen it on my phone before but i dont hink there is any way of getting that back because on the list of things to chose from at the top it said "no OS is found starting RSD in 5 seconds"
timeshare1234 said:
I know what battery symbol you are talking about i have seen it on my phone before but i dont hink there is any way of getting that back because on the list of things to chose from at the top it said "no OS is found starting RSD in 5 seconds"
Click to expand...
Click to collapse
if you hacked apart the USB cable and attached it correctly, it will feed a current directly into the phone. there is no battery symbol that appears, it's a direct charge and the phone doesn't even know that it's charging.
So even if i correctly attached it the phone won't do anything?
timeshare1234 said:
So even if i correctly attached it the phone won't do anything?
Click to expand...
Click to collapse
the battery will start to warm up, since it's having a current pushed into it. just hook up the positive and negative cables into the correct spots and then let your phone charge for half an hour or so.
My battery isn't heating up if i use another atrix battery will that work?
Yes it will work.
Sent from my MB860 using xda premium
The phone will only turn on when it is plugged into the wall, if i plug it into my computer and try to turn it on the green light turns on and then off after 3 seconds and nothing happens.
Related
I was on Neutrino 2.5, I flashed to 2.5p (without wiping).
It wasn't working as I wanted so I went in to recovery to reflash the google apps zip.
After that I'm now stuck in a boot cycle loop and I can't even boot in to recovery mode. When I try to enter recovery it says "Entering Android Recovery Mode" then the screen just goes blank.
Really sorry to make this my first post but I'm kinda freaking out right now. Don't have any idea how to recover from this.
rodabi said:
I was on Neutrino 2.5, I flashed to 2.5p (without wiping).
It wasn't working as I wanted so I went in to recovery to reflash the google apps zip.
After that I'm now stuck in a boot cycle loop and I can't even boot in to recovery mode. When I try to enter recovery it says "Entering Android Recovery Mode" then the screen just goes blank.
Really sorry to make this my first post but I'm kinda freaking out right now. Don't have any idea how to recover from this.
Click to expand...
Click to collapse
flash the recovery again using fastboot
Thanks for the reply. So my problem so is that I'm trying to boot in to RSD mode but it get the message "Battery is too low to flash".
I'm trying to charge the battery but whenever i plug it in to charge phone starts up and ends up in the boot cycle, and the battery doesn't end up charging.
How can i force the phone not to turn on when I plug it in to the wall charger?
Ok, I was able to McGyver a usb charger from an old cable and I got the battery charged enough where it would enter fastboot.
However... now I can't get either of my laptops to recognize the phone in fastboot.
I attach the phone to the usb port, turn the phone on and hold the volume down button. I press the volume up button when fastboot appears, the message "Starting Fastboot protocol support" appears and then nothing happens. Windows just sits there, the phone just sits there...
If I do moto-fastboot devices at the command prompt there is no serial.
Any thoughts?
Well, normally nothing happens until you issue a fastboot command. I usually boot into fastboot mode first, THEN connect the phone & open a command line, etc.
What happens if you do the above and type "fastboot devices"? Does it see your phone then?
Ok, so I tried your method, and installing some different windows drivers and now windows does recognize the phone!
For the record, I am on windows xp and currently i'm using driver version 2.0.40 (same problem with 2.0.53).
Now windows isn't able to install the fastboot drivers, it comes up as an unrecognized device. Is there a way to manually install the fastboot drivers?
Although it's recognized by windows, issuing the moto-fastboot devices command still returns blank.
hello,i tried to change the CID of my phone(gsm) and the usb cable was removed. now i think that it is bricked,and it shows "error device not found" in cmd. can anyone help me plz?:crying: am ready to donate as much as you want.
Can you still get fastboot to work? If so, try typing this command fastboot oem writecid 11111111
No mate,only the red led lights when connected to my pc. No sign of life after that. When i adb reeboot bootloader,it shows "device not found".
can you boot into bootloader using power+vol down(pull batery first)? If so go into fastboot mode and check if device is detected (type "fastboot devices" )
if all goes well you could maybe try running an RUU to get your phone working again
EM|NEM said:
can you boot into bootloader using power+vol down(pull batery first)? If so go into fastboot mode and check if device is detected (type "fastboot devices" )
if all goes well you could maybe try running an RUU to get your phone working again
Click to expand...
Click to collapse
Nothing hapens mate. Can't get in bootloader nor recovery. If i connect to charger or pc via usb,only the red led lights up. Nothing more.
So I have a Telus version of the HTC One X+ 64GB. I have been pretty familiar with flashing roms on samsungs. Wasn't the case so much with the HTC. So I decided to unlock boot loader, root, and flash a custom recovery. Decided to flash this rom from this thread. http://forum.xda-developers.com/showthread.php?t=2219520 not understanding how the boot.img works well guess what I didn't flash that. Now I'm stuck on the Panandriod 3+ boot logo. The phone from my understanding don't seem to wanna charge. Just gets a slow blinking red notification light. When I was able to get into recovery when the battery had charge I was unable to get the ad card to mount so I could add the boot.img to the phone to get fast boot to flash it. I have all the drivers installed on the PC but unsure if maybe the reason that recovery is unable to mount is because of HTC Sync is installed on the PC as well?
The whole reason for trying to flash a rom on this HTC is because I have the HTC One Developer Edition on the way and I wanted to learn as much about flashing HTC as I could so I wouldn't mess up and brick my HTC One when it came. Nowwwww I'm not so confident.
Two days research I have a little more knowledge but still unable to find a good thread or resource to fix this problem. I was able to get some charge thru to the phone when I selected recovery and it went to a black screen with the notification light pulsing red. It seems like its not fully bricked. I tried to use Cmd in windows to try and communicate and see if he phone would respond to the fast boot commands but to no lunch Cmd cannot find the phone. Do anyone know where I could start? Is there a tool kit that can send me back to stock? It was running 4.1.1 any help in the right direction would be great. Thank you guys.
You HAVE to flash the boot.img! Flash it in fastboot
fastboot flash boot boot.img
Without the new boot.img (which is the kernel) your Rom will not run.
Download the pizza boot.img
sixcarnage said:
You HAVE to flash the boot.img! Flash it in fastboot
fastboot flash boot boot.img
Without the new boot.img (which is the kernel) your Rom will not run.
Download the pizza boot.img
Click to expand...
Click to collapse
Hey thanks for replying
I downloaded the pizza boot.img but the issue I'm facing is charging it seems either very very slow on black screen or maybe it's not charging? But main issue is that PC cannot find the One X+ I will try this command but where do I place the pizza boot.img on windows?
The only thing is getting me is I'm getting the sound from windows when you connect a device when I plug the phone in USB but the cmd so far that I have tried even the All in one toolkit don't seem to see that the phone is connect USB in fast boot or boot loader mode. Think this is due to not enough charge? Plus should I just leave it in custom recovery to charge which is a black screen due to it says not enough charge to flash to charge my device?
sixcarnage said:
You HAVE to flash the boot.img! Flash it in fastboot
fastboot flash boot boot.img
fastboot erase cache
Without the new boot.img (which is the kernel) your Rom will not run.
Download the pizza boot.img
Click to expand...
Click to collapse
Corrected.
Gene1985 said:
Two days research I have a little more knowledge but still unable to find a good thread or resource to fix this problem.
Click to expand...
Click to collapse
I can hardly believe you didn't find anything that help you with this issue on this forum.
First is your SDK/ADB tool install on your computer?
It's not that complicated to flash the boot.img. Take the pizza boot.img and put it in your platform-folder of your SDk tool. Reboot your phone by holding Volume down and pressing Power button. In bootloader plug in your USB cable and at the prompt confirm that your computer is seen by typing this >fastboot devices if you have your serial confirmation then simply proceed with this at the prompt>fastboot flash boot insert_pizza_name_boot.img (enter) again at the prompt>fastboot erase cache (enter) the for rebooting >fastboot reboot (enter)
If you need more infos, you have everything required in my signature to help you.
Do you have the latest TWRP
Lucky Thirteen said:
Corrected.
I can hardly believe you didn't find anything that help you with this issue on this forum.
First is your SDK/ADB tool install on your computer?
It's not that complicated to flash the boot.img. Take the pizza boot.img and put it in your platform-folder of your SDk tool. Reboot your phone by holding Volume down and pressing Power button. In bootloader plug in your USB cable and at the prompt confirm that your computer is seen by typing this >fastboot devices if you have your serial confirmation then simply proceed with this at the prompt>fastboot flash boot insert_pizza_name_boot.img (enter) again at the prompt>fastboot erase cache (enter) the for rebooting >fastboot reboot (enter)
If you need more infos, you have everything required in my signature to help you.
Click to expand...
Click to collapse
Thanks Lucky, I noticed tonight I went thru everything in issues and I noticed that I didn't correctly have SDK set up right on my windows. Hopefully that this is the issue and that when I set it up right that I can fix this problem. This has been far different then Samsung to fix hahaha thanks again and kinda my bad for posting the question. But hopefully that works.
sixcarnage said:
Do you have the latest TWRP
Click to expand...
Click to collapse
No I don't have TWRP I have the recover that came in the noob tool kit. The none touch screen one lol. But I understand a fair bit on what I should have done. I'm gonna try and follow luckies link for the SDK set up and see if I can send the zip file to the phone then flash it in recovery. Just I hope the thing can charge. I had it on the charger for 4 hours today and it still said that there was not enough charge to flash I tried charging it in the boot loop and in recovery.
So I guess the issue is worse. The phone won't charge at all the red notification light blinks red but it don't seem to be charging at all I have looked for fixes and it says flash latest compatible recovery but it won't even discover the phone connected to windows with proper HTC drivers installed
Is your phone capable of booting in bootloader mode?
Lucky Thirteen said:
Is your phone capable of booting in bootloader mode?
Click to expand...
Click to collapse
Yea I am able Lucky. But what I tried today was to get RUU to recognize the phone to do that but no go. So tomorrow I'm gonna do a fresh reinstall on a new laptop of windows and install drivers again and all that. But as for boot loader mode it boots. I click recovery and I get a black screen. I can fast boot USB but I'm not quite sure about USB debugging is still turned on. If it where I'm sure I wouldn't have an issue with the PC not seeing the phone connected.
OK try this in bootloader mode with the USB plug
fasboot devices
Do you have a confirmation serial number?
Will do Lucky. Thanks for your time and patience. I will try this over the night. I really like to try and get this fixed and to understand how the htc works with installing roms and tweaks. I really don't wanna mess up my Develeper Edition of the HTC One that's on the way.
If you have your serial confirmation.
Download this recovery HERE
Move this file in your platform-tools folder
Press and hold the Shift key and right click on a empty space of that folder and select Open Command Window Here
In the command window with your phone in FASTBOOT USB mode
Type>fastboot flash recovery TWRP2500.img
(Success)
Type again>fastboot erase cache
(Success)
Unplug your USB cable
Hit one time Power
Select Recovery (Volume down)
Hit Power to Reboot in Recovery
Phone should charge in recovery even if the red light doesn't lit.
Just tried this on my phone with less than 10% and it worked flawlessly, after ~10 minutes my phone was at 13%+
Otherwise you will have to create a batch file and run it while your phone is in FASTBOOT USB mode :
Code:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
That should allow your phone to charge to the minimal required to flash or to re-unlock your bootloader.
Lucky Thirteen said:
If you have your serial confirmation.
Download this recovery HERE
Move this file in your platform-tools folder
Press and hold the Shift key and right click on a empty space of that folder and select Open Command Window Here
In the command window with your phone in FASTBOOT USB mode
Type>fastboot flash recovery TWRP2500.img
(Success)
Type again>fastboot erase cache
(Success)
Unplug your USB cable
Hit one time Power
Select Recovery (Volume down)
Hit Power to Reboot in Recovery
Phone should charge in recovery even if the red light doesn't lit.
Just tried this on my phone with less than 10% and it worked flawlessly, after ~10 minutes my phone was at 13%+
Otherwise you will have to create a batch file and run it while your phone is in FASTBOOT USB mode :
Code:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
That should allow your phone to charge to the minimal required to flash or to re-unlock your bootloader.
Click to expand...
Click to collapse
Thanks Lucky. I will try this first thing in the A.M I hope that works.
Lucky Thirteen said:
If you have your serial confirmation.
Download this recovery HERE
Move this file in your platform-tools folder
Press and hold the Shift key and right click on a empty space of that folder and select Open Command Window Here
In the command window with your phone in FASTBOOT USB mode
Type>fastboot flash recovery TWRP2500.img
(Success)
Type again>fastboot erase cache
(Success)
Unplug your USB cable
Hit one time Power
Select Recovery (Volume down)
Hit Power to Reboot in Recovery
Phone should charge in recovery even if the red light doesn't lit.
Just tried this on my phone with less than 10% and it worked flawlessly, after ~10 minutes my phone was at 13%+
Otherwise you will have to create a batch file and run it while your phone is in FASTBOOT USB mode :
Code:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
That should allow your phone to charge to the minimal required to flash or to re-unlock your bootloader.
Click to expand...
Click to collapse
worked like a charm Lucky. thanks i followed all the steps now im up and running. thanks again.
Great! This is a good news!
Please take the time to edit your OP and change your title to this : [SOLVED] BAD FLASH!!!! NOOB. Possible Brick HELP THANK YOU.
Happy flashing now!
For the life of me I can not get my wife's phone into bootloader mode. I have read tons of threads that all say to either hold down power and vol down OR plug in the usb cord (connected to computer) while holding the vol down button.
The power+vol down results in the recovery mode and the other causes a vibration then goes to the %charging screen.
I have adb working cause it returns the device number and also reboots... BUT neither <adb reboot recovery> OR <adb reboot-bootloader> does anything but reboot normally.
Here's the deal, I am trying to get her stock phone to run Android Pay but it fails the safety net. There is a chance that I unlocked the bootloader but without having access to fastboot I can't run <fastboot getvar unlocked> to check.
So my questions are:
Is there some way to get into fastboot that I am missing?
Is there a way to know if the bootloader is unlocked besides fastboot command?
Any thoughts on reasons a stock phone would fail safety net besides the unlocked bootloader is welcome also.
Thanks.
PS. This V-10 in nothing like ny Nexus phones. LOL
Hi guys,
This Is my first post so I hope I do it correctly. As the title says I am having problems with fastboot on my Acer Iconia One 10 B3-A40. I have enabled developer settings on my device and turned on the setting to unlock OEM. The problem is when I try to run the tablet in fastboot mode to unlock the OEM through ADB commands. When connected to my computer and running the command "adb devices" it shows my device Id and that it is connected. I then run the command "adb reboot-bootloader" to which the tablet switches off and makes the chime that it was disconnected from the computer and makes another chime and connects back onto the computer, the screen on my tablet remains blank with no indication it is in fastboot mode. When I run the command "fastboot devices" my device id shows up again that it is connected. When I originally tried to flash a patched boot image of my stock firmware it went through the process and failed mid way through saying it couldn be done cos the device was locked. After that I googled a bit to see what to do so that’s when I realised OEM unlock was to be switched on in developer settings and also using ADB commands. After returning to fast boot mode I ran the command "fastboot oem unlock" the 3 dots come up on command prompt to show the process is going but nothing happens on my device. Nothing will happen if I press the power button or the volume down button but if I press the volume up bottom, on command prompt it shows OKAY and then the amount of seconds it took to complete, the time changes based on how quick or long i take to press the volume up button but the device remains locked. I have being trying to find a solution for days and have searched everything i could find before making this post. It would be greatly appreciated if someone could help.