Hey Guys,
Thanks for the help in advanced.
I've been flashing Roms for my Atrix HD for the last few days and have had only one minor problem that I was able to figure out.
When I woke up this morning, I was going to try out Slim since it had downloaded overnight. I did everything as normal.
Wiped everything
Formated system
Installed and it failed.
Tried a couple more times and same thing. So I figured it must have corrupted on the download.
So I reinstalled holoblur which was my goto with the steps above and rebooted.
Now it won't boot past the boot loader unlocked screen.
I've tried holding power with up and down, and any combination I can think of. Nothing...
Any ideas?
photoshopgeek said:
Hey Guys,
Thanks for the help in advanced.
I've been flashing Roms for my Atrix HD for the last few days and have had only one minor problem that I was able to figure out.
When I woke up this morning, I was going to try out Slim since it had downloaded overnight. I did everything as normal.
Wiped everything
Formated system
Installed and it failed.
Tried a couple more times and same thing. So I figured it must have corrupted on the download.
So I reinstalled holoblur which was my goto with the steps above and rebooted.
Now it won't boot past the boot loader unlocked screen.
I've tried holding power with up and down, and any combination I can think of. Nothing...
Any ideas?
Click to expand...
Click to collapse
Never mind... just let me into CWM. Did the exact same thing too... weird.. Mods can delete if they wish.
Lol was posted in the wrong forum anyway
Sent from my Atrix HD using ProBAM rom and XDA 4 Premium
Related
anyone getting anything out of this log?
http://pastebin.com/YDNJK3RF
Wipe and reflash?
nxt said:
Wipe and reflash?
Click to expand...
Click to collapse
done a dozen of times. changed radios reflashed recovery! all!
the nandroid is working fine
Use a different rom or start from scratch on the one you're trying to use(not your nandroid)
Sent from my Nexus One using XDA App
JoshHart said:
Use a different rom or start from scratch on the one you're trying to use(not your nandroid)
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
i'am trying from scratch. wiped everything tried from the begining. even changed the radio
Yes - well I have observed these symptoms before.
The kernel is falling over loading the audio drivers.
It's very strange but if you slow the boot process down you can work around the problem and then get the phone to boot. Once it has booted once the problem doesn't tend to reoccur very often. I have only noticed this on a handful of phones although I can reproduce it from time to time.
When "stuck" (it is actually boot-looping as you observe) reboot to recovery using adb or finger-gymnastics and wipe dalvik-cache (or cache for that matter)... but you need only wipe one of them. Reboot the phone from recovery, should boot as normal but may take a loooooong time the first time...
Please report back, I'd be interested in your findings.
djmcnz said:
Yes - well I have observed these symptoms before.
The kernel is falling over loading the audio drivers.
It's very strange but if you slow the boot process down you can work around the problem and then get the phone to boot. Once it has booted once the problem doesn't tend to reoccur very often. I have only noticed this on a handful of phones although I can reproduce it from time to time.
When "stuck" (it is actually boot-looping as you observe) reboot to recovery using adb or finger-gymnastics and wipe dalvik-cache (or cache for that matter)... but you need only wipe one of them. Reboot the phone from recovery, should boot as normal but may take a loooooong time the first time...
Please report back, I'd be interested in your findings.
Click to expand...
Click to collapse
i will try it later tonight. the part that's bothering me it's that i loaded several kernels on my current nandroid and every single one is working fine! when i flash a new rom though i get this issues...
hmmmmm nop... not working. i flashed, and rebooted. pulled battery and wiped cashe same thing. then nandroid restore, flashed again, restarted, pulled battery and flashed dalvik. same thing...
i think i sorted out the issue... dunno why it happened but i flashed the stock rom part by part via fastboot and it seems that everything is fine now...
I had the same issue. It happened on every single ROM + Radio combination you can think of, including stock everything. Finally gave up and sent my N1 to get repaired. Received it a week ago and it's working again. They also re-locked my bootloader... And now here I am contemplating unlocking it again... but I don't want to go through that experience again.
I'd send it in rooted or not, if you still have the problem going back to stock.
If im running the 2.2 leak version and am having bootlooping issues and am unable to get into clockwork, can I just SBF to official 2.2?
yes you can
Cool reason I asked is because I did it last night and it just keeps boot looping now tried to flash it about 3 different times. Any suggestions as to how i can get it going? The SBF file fully flashes to the phone RSD doesn't give any errors and reboots phone as it normally would but when it starts up it just boot loops I actually left it going for about 30mins last night to see if it would strat up, so far it has not.
Just to make sure- and I know this is a lame question - but just to make sure - you are using the new 2.2 SBF...
VRZ_MB810_2.3.15_1FF_01
Yeah the SBF im using matches that file name. It was late last night so only really got to try and flash it a few times and im stuck at work now just trying to see if anyone else had any similar issues really. Also im on windows 7 64bit if that may cause any issues.
You may want to try wiping the data and cache from the default recovery. Power on your phone with the home key pressed and press the search key. You'll have options for wiping data and cache. Maybe you could still have remnants of the 2.2 leaks in there?
Sent from my DROIDX using XDA App
I think I tried that last night will do again to be sure though and thanks for all the help.
when I SBF'd back to stock 2.2 I had to boot back into recovery and apply the update.zip, once I did that it booted back up without issue.
Lol facepalm. The update.zip heh, did not try that yet. Gonna try it as soon as I get home and ill update when I do. Thanks for all the suggestions.
Got it to boot after doing factory reset thanks again for all the help
Hey guys,
I recently got a new phone so haven't been using my milestone anymore and a friend offered to buy it from me.
So I of course was going to flash a stock sbf back on for him, i chose to flash 2.2.1.
I immediately ran into problems.
First off it worked fine, rsd (ver 5.3.1) gave me a pass, i disconnected the phone and rebooted, the android logo shows up and all is joyful in the world.
This is where the problems arise...
I rebooted into recovery to do a full wipe, and a cache and dalvik wipe, then i rebooted once more.
Instead of rebooting normally the phone now just goes immediately to bootloader.
No matter what i try it jsut alays goes back to bootloader straight away. there is no error message it just says ok to program blah blah like normal.
i've since flashed all the different bootloaders, the vulnerable recovery, every single moto sbf i could find, i even tried removing the volume buttons and keyboard to make sure the buttons weren't broken and automatically taking me there due to a short.
no luck.
did i kill this milestone? seriously, any ideas would be appreciated because i am totally stumped now.
Cheers.
Please someone help. I still havent gotten any further with this.
Sent from my LG-P920 using XDA Premium App
Did you try restoring a stock nandroid, that is if you can enter recovery mode.
Sent from my GT-I9100 using Tapatalk
Firstly, this device has never been rooted or had anything flashed to it. It is completely stock.
My step-daughter has been having issues with her Droid 4. About a month back or so, she started noticing that it wouldn't boot. It would flash the Motorola logo, and then the screen would just hang on the bootanimation. Eventually if we rebooted (power+vol down) enough times it would boot up.
Last night however, this happened again and it would not boot at all. I tried rebooting many times and it would never get past the bootanimation. After about 20 or so reboots I figured it was time for a Factory Reset. After the reset however, it wouldn't even display the bootanimation. It would still display the Motorola splash screen, but after that the screen would just go black with the display is still on. I Factory Reset several more times and nothing. Eventually after a number of times rebooting, it finally booted up. Well that was yesterday. Today she had to reboot it and it wouldn't boot again. Would just hang on a black screen.
I'm about ready to send it back since it's still under warranty, but figured I would check here to see if any of the amazing XDA guru's had experienced this and found a solution. I searched Google and this forum and didn't really see anything. Any help would be greatly appreciated!
jdiamond7 said:
Firstly, this device has never been rooted or had anything flashed to it. It is completely stock.
My step-daughter has been having issues with her Droid 4. About a month back or so, she started noticing that it wouldn't boot. It would flash the Motorola logo, and then the screen would just hang on the bootanimation. Eventually if we rebooted (power+vol down) enough times it would boot up.
Last night however, this happened again and it would not boot at all. I tried rebooting many times and it would never get past the bootanimation. After about 20 or so reboots I figured it was time for a Factory Reset. After the reset however, it wouldn't even display the bootanimation. It would still display the Motorola splash screen, but after that the screen would just go black with the display is still on. I Factory Reset several more times and nothing. Eventually after a number of times rebooting, it finally booted up. Well that was yesterday. Today she had to reboot it and it wouldn't boot again. Would just hang on a black screen.
I'm about ready to send it back since it's still under warranty, but figured I would check here to see if any of the amazing XDA guru's had experienced this and found a solution. I searched Google and this forum and didn't really see anything. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Only other I can think to do would be to flash the fastboot files. A factory reset basically just wipes data while fastbooting it should reset the system itself to complete bone stock. You can do this using rsdlite or download a utility like jsnweitzel's ICS Only Utility in the Dev section.
Really sounds like a hardware issue to me since it's not rooted or anything but still might be worth a shot.
Sent from my Droid 4 - LiquidSmooth
kwyrt said:
Only other I can think to do would be to flash the fastboot files. A factory reset basically just wipes data while fastbooting it should reset the system itself to complete bone stock. You can do this using rsdlite or download a utility like jsnweitzel's ICS Only Utility in the Dev section.
Really sounds like a hardware issue to me since it's not rooted or anything but still might be worth a shot.
Click to expand...
Click to collapse
Thank you very much for the quick reply. I've downloaded jsnweitzel's ICS Only Utility and am charging up the phones battery so I can use it.
Just a quick question before I do this. I'm assuming that running the restore through ICS Only Utility is flashing a stock system image. That image is not rooted is it? Not that I would typically care, but if I do have to bring it back to Verizon I don't want them hassling me for rooting the device.
jdiamond7 said:
Thank you very much for the quick reply. I've downloaded jsnweitzel's ICS Only Utility and am charging up the phones battery so I can use it.
Just a quick question before I do this. I'm assuming that running the restore through ICS Only Utility is flashing a stock system image. That image is not rooted is it? Not that I would typically care, but if I do have to bring it back to Verizon I don't want them hassling me for rooting the device.
Click to expand...
Click to collapse
The image flashed in the fastboot process is completly stock, unrooted.
Sent from my Droid 4 - LiquidSmooth
Thanks for the help but that didn't do it. Guess I'll be taking it back to Verizon!
Sent from my SCH-I535 using xda app-developers app
Ok so I have an Atrix HD that I rooted then went to install paranoid android on here. I made the mistake to try and install using Factory Recovery. So it threw an error in Fastboot. I used Myth Tools to get it back to stock. Then used Myth to install CWM Root it and unlock bootloader. Then went to install paranoid android again... Everything seemed to be going well but it just stayed on the Glowing X for 10-15 minutes. Knew something was up with it not loading into OS by then. So I tried to reinstall it again. No luck. Tried to use Myth Tools to go back to factory. Would just stay at Dual Core logo and do nothing. I went back in and installed CWM and tried to install Pacman Rom and it just stays at Pac is loading.
Fastboot still shows Bootloader as unlocked as it should, but is this the reason why Myth could not get me back to factory? I just want to get it back to factory at this point and worry about Rooting and installing Rom later. I have been searching and trying anything I can find on here, and droid razr forum. As well as various other sites and artices i find from google. I am at a lose. Have I bricked it enough to not come back from this or am I just missing something simple? I am looking for insight or help to get me in the right direction. I am on day 3 now off trying to get it running again.
I have tried in CWM formating Cache and re mounting it in Advance, Also have tried formating system, cache, davik cache... I did receive the can not mount errors but having formatting cache and remounting i did not get the error again.
Just take it a step at a time. Get it booted into stock first.
Sent from my MB886 using xda premium
darknessrise1234 said:
Just take it a step at a time. Get it booted into stock first.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
but where to begin? Trying to get it back to stock is not working even though Myth Tools. It states it finished I do not get any errors through Fastboot yet it stays on Dual Core never moves as if it is bricked.
DeVoe41 said:
but where to begin? Trying to get it back to stock is not working even though Myth Tools. It states it finished I do not get any errors through Fastboot yet it stays on Dual Core never moves as if it is bricked.
Click to expand...
Click to collapse
read this
http://forum.xda-developers.com/showthread.php?t=2226527
Make sure you have the adb drivers installed on your computer and I've noticed this phone is weird about chargers find one that works for data too. U will know cause if you have adb installed through myth tools and you reboot into fastboot mode then your computer will recognize it. Make sure the only thing in the firmware folder in myth tools is your .zip whatever stock att firmware you want. Then in myth tools install stock and make sure you type in the response 2 when it asks if you are in fastboot mode or normal. Fastboot is choice 2. I'm a flashaholic I've tried every rom in our development forum lol. I have bricked my AHD more times then anyone should this always worked for me. Try these things see if they help
Sent from my MB886 using xda app-developers app
Clean Flash
DeVoe41 said:
Ok so I have an Atrix HD that I rooted then went to install paranoid android on here. I made the mistake to try and install using Factory Recovery. So it threw an error in Fastboot. I used Myth Tools to get it back to stock. Then used Myth to install CWM Root it and unlock bootloader. Then went to install paranoid android again... Everything seemed to be going well but it just stayed on the Glowing X for 10-15 minutes. Knew something was up with it not loading into OS by then. So I tried to reinstall it again. No luck. Tried to use Myth Tools to go back to factory. Would just stay at Dual Core logo and do nothing. I went back in and installed CWM and tried to install Pacman Rom and it just stays at Pac is loading.
Fastboot still shows Bootloader as unlocked as it should, but is this the reason why Myth could not get me back to factory? I just want to get it back to factory at this point and worry about Rooting and installing Rom later. I have been searching and trying anything I can find on here, and droid razr forum. As well as various other sites and artices i find from google. I am at a lose. Have I bricked it enough to not come back from this or am I just missing something simple? I am looking for insight or help to get me in the right direction. I am on day 3 now off trying to get it running again.
I have tried in CWM formating Cache and re mounting it in Advance, Also have tried formating system, cache, davik cache... I did receive the can not mount errors but having formatting cache and remounting i did not get the error again.
Click to expand...
Click to collapse
I have a suspicion that for some odd reason, as Mythtools probably should have taken care of this, that there are some lingering files and caches that would cause any rom to fail upon install. I just posted something about this earlier today.
Read my post on this thread:
http://forum.xda-developers.com/showthread.php?t=2394238
PM me with any questions or problems and click the Thanks button if I helped.
I'm sorry I forgot to update I was able to get the phone working just had to do it through command prompt forcing you to file . The issue I had was using safestrap to install a ROM which somehow killed root access and the bootloader was not unlocked so and pretty much bricked the phone.
Sent from my MB886 using xda app-developers app
For recent custom roms, you must use a CWM with an unlocked bootloader.