Related
Just got myself an N1 and now having problems with boot loop with/without Sim on.would flashing it with a custom Rom fix the problem? Please help!
-------------------------------------
Sent via HD2
Noob to noob advice
New to android, and was stuck in a boot loop recently.
Yes, flashing a custom rom worked. First you need to unlock the phone and get root.
Then you need Android SDK installed on your PC, and adb drivers.
Then within the SDK/tools folder, is fastboot.exe
I did fastboot flashed a recovery.zip, and then using Volume down and Power on, with the touchpad pressed too, accessed Bootloader, then scrolled into recovery,
and flashed the Cyanogenmod.zip that was copied on to my microSD card (you might need to do this via an microsd reader on your pc at this point),
and boom.
custom rom, and boot loop over.
http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
http://nexusonehacks.net/nexus-one-...o-install-cyanogen-mod-rom-on-your-nexus-one/
Another scenario to consider:
I encountered an infinite boot loop once when my battery went bad. In this case the Nexus one won't power on when unplugged, but an infinite boot loop will occur when it is plugged in and powered on.
Hope that helps.
ROM_Guest said:
Noob to noob advice
New to android, and was stuck in a boot loop recently.
Yes, flashing a custom rom worked. First you need to unlock the phone and get root.
Then you need Android SDK installed on your PC, and adb drivers.
Then within the SDK/tools folder, is fastboot.exe
I did fastboot flashed a recovery.zip, and then using Volume down and Power on, with the touchpad pressed too, accessed Bootloader, then scrolled into recovery,
and flashed the Cyanogenmod.zip that was copied on to my microSD card (you might need to do this via an microsd reader on your pc at this point),
and boom.
custom rom, and boot loop over.
http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
http://nexusonehacks.net/nexus-one-...o-install-cyanogen-mod-rom-on-your-nexus-one/
Click to expand...
Click to collapse
Thanks A lot!!!!
I was almost about to give up on this,ive been flashing windows mobile for quite some time now but Android is a totally new thing for me.It wasnt this hard for me on putting android on my HD2 lol.
You're welcome. Glad I could help
My stock 2.2.2 streak is rooted. i downloaded honeycomb boot animation, renamed the stock b.a. and named honeycomb b.a. Bootanimation.zip. and rebooted, and it worked. a couple days later i came across something new and cool, i wanted to put the Transformers boot animation on it. i then went back to system/media and deleted honeycomb b.a. and then renamed stock bootanimation.zip, and then i downloaded the zip and put it into data/local like it says. i then tried to boot it up, it showed the dell logo, then screen goes blank with backlight on and button LED's are also on. it also vibrates every 10 seconds...what the heck is going on, hopefully i didnt brick my phone :\
...by the way, i can put it into fastboot, and i can hold vol up vol down and power, to the recovery screen?
Any help or suggestions are highly appreciated, thanks in advance everybody.
Well, personally, I would boot into StreakMod recovery (fastboot flash it on if needed), mount the data partition, run adb shell from a connected pc, and rename the original bootanimation.zip back into place.
I've had to do the above on my wildfire, where it worked perfectly, so I do know that just a misconfigured bootanimation can indeed cause issues like you are seeing.
Good luck.
ill get on that
That'll be enough to get me started, thanks
whats the command, to flash recovery.img? the whole line, i know it may differ. but an example?
and how do i run adb shell?
You can get StreakMod from http://forum.xda-developers.com/showthread.php?t=840326 and there are some instructions in the first post, as well as a download link.
The flash command is
fastboot -i 0x413c flash recovery recovery.img
To run adb you will need to have installed the Android SDK (actually, I believe that it is possible to just install the adb tool itself, but I've never tried that). You can get full instructions for that, and download links at http://developer.android.com/sdk/installing.html
It is useful to have adb installed anyway if you're going to play around with flashing stuff - it can be used to transfer files on and off your streak, log into it via the shell, watch the debugging log (it is very reassuring to watch it be busy doing something when you're booting a new rom and the screen is telling you nothing)
If you know how to use adb and fastboot but dont want the entire sdk
http://mirror2.streakdroid.com/manii/Tools/Fastboot+ADB.zip
includes fastboot + adb + streak drivers
I was unlocked and rooted and ready to install CM7. I followed all the instructions in the Official Atrix CM7 OP to the T, but when it rebooted, I got stuck on the boot screen with "unlocked" and the red M logo.
I tried to repeat the process several times and ended kind of giving up, factory wiping, and then trying to restore my backup. It appeared to restore successfully, but when I rebooted the phone now wont boot at all. I can't even get it into recovery. No combination or order of button presses or battery pulls / usb plugins will turn it on. I just have a green light like it's charging but nothing is working.
Is it possible to brick your phone even after you have been successfully unlocked and rooted just while you are trying to install CM7?
Please help. I am really desperate here. . .
jimjenkins said:
I was unlocked and rooted and ready to install CM7. I followed all the instructions in the Official Atrix CM7 OP to the T, but when it rebooted, I got stuck on the boot screen with "unlocked" and the red M logo.
I tried to repeat the process several times and ended kind of giving up, factory wiping, and then trying to restore my backup. It appeared to restore successfully, but when I rebooted the phone now wont boot at all. I can't even get it into recovery. No combination or order of button presses or battery pulls / usb plugins will turn it on. I just have a green light like it's charging but nothing is working.
Is it possible to brick your phone even after you have been successfully unlocked and rooted just while you are trying to install CM7?
Please help. I am really desperate here. . .
Click to expand...
Click to collapse
are you using the right recovery? romracer or rom manager!
i am using the tenfar CWM included in the Atrix 4G Automatic Unlock script package. will this not work?
if not, how do I replace it with the right recovery if I cant even get into the phone?
jimjenkins said:
i am using the tenfar CWM included in the Atrix 4G Automatic Unlock script package. will this not work?
if not, how do I replace it with the right recovery if I cant even get into the phone?
Click to expand...
Click to collapse
no, that the old recovery you can use the rom manager if you have , or romracer latest recovery you can find that in the development section, also ther was instruction in the cm7 thread.
you should have left it alone at the M boot screen because it takes about 5-10min to boot after unlock and flash...
everything you do now will have to be through fastboot DO NOT SBF FLASH ANYTHING!!!
Go here to use Fastboot
then download the system.img and boot.img from here
use fastboot to push the boot.img and system.img to your phone
if it gets stuck at the M boot screen let it sit for at least 10min
EDIT: get Romracer recovery from here and push that through to your phone through fastboot
Yeah youre going to have to fastboot wipe recovery then fastboot flash recovery recovery.img
Just download rom racers and rename it..recovery.img
Sent from my GT-I9100 using xda premium
Great. Sorry to be such a noob, but do I decompress the CWM-recovery-atrix5.zip file and push the recovery.img file that's inside it? or push the CWM-recovery-atrix5.zip itself?
Also - every time I am able to get my phone into fastboot mode, it says my battery is too weak to flash anything. I cant seem to get the battery to charge enough to execute any fastboot commands. Any way around this? a powered usb hub?
jimjenkins said:
Great. Sorry to be such a noob, but do I decompress the CWM-recovery-atrix5.zip file and push the recovery.img file that's inside it? or push the CWM-recovery-atrix5.zip itself?
Also - every time I am able to get my phone into fastboot mode, it says my battery is too weak to flash anything. I cant seem to get the battery to charge enough to execute any fastboot commands. Any way around this? a powered usb hub?
Click to expand...
Click to collapse
If you can borrow another Atrix user's battery, or take yours to an AT&T store and see if they can charge it for you.
If you're able to get back into recovery then you can just flash the zip.
If not, you'll need to extract the recovery.img to use it with fastboot, or just download it directly from the OP in romracer's thread. (The left hand link is just the .img, the right hand side is the CWM .zip) Then place it in the same directory as fastboot.
So I can literally flash a different recovery from within another?
jimjenkins said:
So I can literally flash a different recovery from within another?
Click to expand...
Click to collapse
yes but it MUST be working proper first ! its ok to use rom managers cwm but i just prefer the otherone alawys have but n e way there are only 2 that are current (uptodate )
thoughs 2 and with romracers you can. chose
a color that you like not just blue
Sent from my MB860 using xda premium
Its the recovery from tenfar CWM. When I can get it into recovery it seems to be working - with the obvious exception of successfully installing CM7
So I can flash romracer recovery from inside tenfar recovery?
sorry if im being redundant - just dont want to screw it up!
thanks
Just download rom racers cwm. Img, head into fastboot and then fastboot flash recovery recovery-****** (whatever yer recovery image color u chose is)
Sent from my MB860 using Tapatalk
I was able after a full day of leaving the phone plugged in, to charge it up. Then I flashed the rom racer recovery, rebooted into recovery (new version), installed CM7, installed gapps, and voila! A working CM7 Atrix. thank you soo soo much guys.
Can't boot android/recovery
ClearFire said:
you should have left it alone at the M boot screen because it takes about 5-10min to boot after unlock and flash...
everything you do now will have to be through fastboot DO NOT SBF FLASH ANYTHING!!!
Go here to use Fastboot
then download the system.img and boot.img from here
use fastboot to push the boot.img and system.img to your phone
if it gets stuck at the M boot screen let it sit for at least 10min
EDIT: get Romracer recovery from here and push that through to your phone through fastboot
Click to expand...
Click to collapse
Please help!!!
The phone stuck in boot screen and overheat, then restart.
In recovery mode is just black screen.
Phone has Neutrino 2.6GT+ ROM whit Clemsyn's OC kernel 1.6GHz and it has unlocked bootloader.
Can I change the kernel without booting in os or recovery?
This problem show after I was extracting very big zip file and phone overheat.
firecode95 said:
Please help!!!
The phone stuck in boot screen and overheat, then restart.
In recovery mode is just black screen.
Phone has Neutrino 2.6GT+ ROM whit Clemsyn's OC kernel 1.6GHz and it has unlocked bootloader.
Can I change the kernel without booting in os or recovery?
This problem show after I was extracting very big zip file and phone overheat.
Click to expand...
Click to collapse
I am actually having this same problem.
My warranty-replacement (unrelated ear-piece failure) had 2.3.6 pre-installed. Thinking little of it, I unlocked the BL and rooted the phone as usual. After this, I tried to install a couple of the ROM's (Neutrino and Morrisoft) which I was most happy with on my previous Atrix.
After flashing either Neutrino or Morrislee's ROM, the phone hung on the M screen. Waiting approximately 30 minutes with no change, I pulled the battery.
When trying to enter recovery mode, the phone would state, "entering recovery mode..." Then go black.
I ended up using RSDLite and sbf flashing the stock 2.3.6 sbf file back to the phone. Then, I had to re-unlock the bootloader and re-root.
This never happened up to, and including 2.3.4, but did twice last night on these ROM's using 2.3.6, and I've flashed many ROM's and Kernels.
It happened to a lesser extent when trying to flash Clemsyn's stock enhanced kernel to the stock ROM, as I was able to enter recovery mode. Entering recovery mode, it would give errors: mounting cache, mounting system errors, and errors to accessing recovery and recovery log files.
Restore recovery would fail in this state, giving me the above errors as well.
Trying to mount the cache and system in recovery would fail. Trying to format cache and system then mounting these could occur temporarily, but would revert back to unmounted when a restore was attempted.
For these problems I pushed a recovery through fastboot.
Just one word: Fastboot. See if Fastboot works and flash everything from there. Or, as Alterna suggested, flash through RSDLite, but that a little dangerous and can brick your phone if you don't know what you are doing. Hope it helps.
Problem sloved!!!
Alterna said:
My warranty-replacement (unrelated ear-piece failure) had 2.3.6 pre-installed. Thinking little of it, I unlocked the BL and rooted the phone as usual. After this, I tried to install a couple of the ROM's (Neutrino and Morrisoft) which I was most happy with on my previous Atrix.
After flashing either Neutrino or Morrislee's ROM, the phone hung on the M screen. Waiting approximately 30 minutes with no change, I pulled the battery.
When trying to enter recovery mode, the phone would state, "entering recovery mode..." Then go black.
I ended up using RSDLite and sbf flashing the stock 2.3.6 sbf file back to the phone. Then, I had to re-unlock the bootloader and re-root.
This never happened up to, and including 2.3.4, but did twice last night on these ROM's using 2.3.6, and I've flashed many ROM's and Kernels.
It happened to a lesser extent when trying to flash Clemsyn's stock enhanced kernel to the stock ROM, as I was able to enter recovery mode. Entering recovery mode, it would give errors: mounting cache, mounting system errors, and errors to accessing recovery and recovery log files.
Restore recovery would fail in this state, giving me the above errors as well.
Trying to mount the cache and system in recovery would fail. Trying to format cache and system then mounting these could occur temporarily, but would revert back to unmounted when a restore was attempted.
For these problems I pushed a recovery through fastboot.
Click to expand...
Click to collapse
My problem like that and I use automated unlock tool to recover recovery, this recovery show some errors but I successfully flash cwm touch and reinstall Nutrition 2.6GT+
Rom: Stock
Rooted with KFU 0.9.5
TWRP 2.1
fff 1.4a
The problem I'm having is that when I boot my KF up it goes to fff. I get 3 options to boot from (this is whenever I power down the KF). When I choose to boot to recovery, the power light turns orange for two secs and then it boots; but back to the fff screen. I did this about four times in a row and it still boots back to the ffa screen.
If I choose ~normal boot~, It boots up fine. When I try to use KFU to boot to recovery or fast boot, it says that it is waiting for device. I tried this several times but no luck.
I want to get into recovery. That's my goal. I'm guessing that the KF is not booting in fastboot for it to go into recovery. I tried to reinstall TWRP 2.1 with KFU and it gets to the point where it's waiting for the device and nothing happens.
I'm not very advanced in this stuff. Please be patient with me. Thank you for all your help.
what command are you using to install recovery?
ok
download twrp 2.1.1.img onto pc
turn off kindle (20 second hold) with the usb cable unplugged from the kindle
open terminal where you have fastboot located.
type the following:
fastboot flash recovery </enter/path/to/recovery.img/here>
press enter
you should see waiting for device
then plug in your usb to kindle
this should power up the kindle and fastboot flash a new recovery.
then type
fastboot reboot
note:
(there is a space between recovery & /
i also find it easier to put a space after "recovery" then drag & drop recovery.img into terminal)
ok...
I did everything you said and the cmd console was still <waiting for device> after I plugged in the KF.
I checked in device manager and that's ok for the adb (it says: android composite adb interface).
Still looking to get into twrp recovery.
IndianaBond said:
I want to get into recovery. That's my goal. I'm guessing that the KF is not booting in fastboot for it to go into recovery. I tried to reinstall TWRP 2.1 with KFU and it gets to the point where it's waiting for the device and nothing happens.
Click to expand...
Click to collapse
There's probably something wrong in KFU's process. Could you at least show us its log or a screenshot?
reflash twrp using smirkit. than try to get into recovery again
Sent from my Galaxy Nexus using xda premium
if its waiting for device your pc is issuing fastboot command. so as you say its your kindle.
one of the above methods should work.
imho smikis's smirkit is nice to use
edit: can you copy and paste your commands after you try to flash new recovery
My Nexus 7 is at Android 4.2.1 and after installing the Elite Kernel to make it boot faster with CLockWork Mod, its stuck at the X animation. I can still access fastboot mode and clockwork recovery mod but I still can start the device. Please help
reflash your rom in your cwm recovery.
Tried
simms22 said:
reflash your rom in your cwm recovery.
Click to expand...
Click to collapse
I just tried doing that and it said it was succesfully installed but I need to reboot. After tapping reboot system my Nexus 7 is still stuck in that X animation and wont boot.
1100G19 said:
I just tried doing that and it said it was succesfully installed but I need to reboot. After tapping reboot system my Nexus 7 is still stuck in that X animation and wont boot.
Click to expand...
Click to collapse
go into the bootloader/fastboot and try booring from there. you also might need to wipe data/factory reset then reflash your rom. also, sometimes force rebooting from a bootloop will boot it(long press the power button while in the bootloop, hold the power button for 10-20 seconds).
I had this happen to me yesterday when trying to flash a custom kernel to use with CM 10.1. The way I was able to fix it, was to pull the boot.img from the ROM zip and flash it through fastboot in the bootloader. The short and simple way is this:
Open the command prompt or terminal in the folder where fastboot is on your computer, extract the boot.img from the zip file of the ROM your using and place it in the folder with fastboot, then on your Nexus 7, hold in power + volume up + volume down to turn it off. Then hold down volume down and press power to boot into the bootloader. Once there, type in the command prompt/terminal: fastboot flash boot boot.img then reboot and you should be good to go.
Can I just remove the ROM?
simms22 said:
go into the bootloader/fastboot and try booring from there. you also might need to wipe data/factory reset then reflash your rom. also, sometimes force rebooting from a bootloop will boot it(long press the power button while in the bootloop, hold the power button for 10-20 seconds).
Click to expand...
Click to collapse
So if I back up the devices files with CWM and factory reseting it will remove the backup, so is there a way to send the backup onto my laptop?
Also is it possible to just remove the rom because I feel like my life would be easier if I unintalled it.
Thank You!
Hmmmmmm
Hanger84 said:
I had this happen to me yesterday when trying to flash a custom kernel to use with CM 10.1. The way I was able to fix it, was to pull the boot.img from the ROM zip and flash it through fastboot in the bootloader. The short and simple way is this:
Open the command prompt or terminal in the folder where fastboot is on your computer, extract the boot.img from the zip file of the ROM your using and place it in the folder with fastboot, then on your Nexus 7, hold in power + volume up + volume down to turn it off. Then hold down volume down and press power to boot into the bootloader. Once there, type in the command prompt/terminal: fastboot flash boot boot.img then reboot and you should be good to go.
Click to expand...
Click to collapse
Its a bit complicated. Also how do I get the boot.img to my computer from my nexus 7 because when I connected the Nexus 7 folder is not under "My Computer"
Thank you
Sounds like you need to go to fastboot and flash 4.13 bootloader.
Sent from my Nexus 7 using xda premium
Dont know
rebel1699 said:
Sounds like you need to go to fastboot and flash 4.13 bootloader.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
How do I flash 4.13 bootloader?
All you have to do is download the same ROM on your computer that you have on your phone. If its stock 4.2.1, then download the factory image of it and extract the boot image from the zip file and follow the same steps I outlined, though instead of using: fastboot flash boot boot.img, it would be fast boot flash boot <name of boot image>.img
If you still have trouble, feel free to message me here or on GTalk and I'll walk you through it.
Sent from my Nexus 7 using Tapatalk HD
There's an important lesson to be learned here, and you unfortunately learned it the hard way. Never, ever, blindly flash something. You need to read the OP as well as catch up on at least the last page or two of the thread. Had you done so, you would have noted that Clemsyn's Elite kernels are not compatible with 4.2.1.
I'm not saying this to be a condescending, but rather to save you the possibility of getting into situations like this again. Fortunately, Nexus devices are easily recoverable from various user errors.