Yesterday I installed CM7, I did everything according to the tutorials, I am running kernel 2.3.4. This morning I was recording a video of my daughter, but suddenly the camera forced closed and I was unable to access the camera, so I restarted my phone. Unfortunately my phone got stuck on a boot loop, so I tried wipe data/factory reset. Now my phone is stuck on the motorola logo and I don't know what else to do.
I tried applying update from sdcard but signature verification fails.
It sounds like you are going to have to sbf. That's the only downside to beta testing. Unexpected things might happen. Signature verification failed because when using stock recovery, the update.zip needs to be signed by moto.
Sent from my MB870 using xda premium
Thank you, I just sbf and everything is back to normal. First time installing custom rom, so I kinda panicked when the phone got stuck on the dual core logo!
I did the same thing. Sbfing will be your best friend and worst enemy lol
Sent from my MB870 using xda premium
Related
Hi I rooted and unlocked my bootloader about 3 weeks ago everything works fine for several days straight no f/c nothing I'm still running the ota. 4.5.9. From Att is the same when I rooted and unlocked the bootloader no problems ever then I try and get some sleep and turn my phone off and go to restart and I get stuck at rethink possible crap so I restore reboot all is well wait 4 days later and boom stuck at same screen after power off then on back to restore any body have any ideas I'm all ears.
Sent from my MB860 using XDA Premium App
Try installing a different ROM and see if you get the same problem. Maybe something is corrupt in your current ROM
Have you tried clearing your dalvik & regular cache?
Well I've never flashed a rom yet and I did wipe the cache and delvic I'm just running stock 2.3 ota should I flash a rom if so which one is most stable .
Sent from my MB860 using XDA Premium App
I'd recommend flashing romracers recovery then installing picrust from there. Since you're new to this, picrust should be a good place to start.
Good luck!
Sent from my MB860 using XDA App
Well im not new to roms bootloaders or flashing I have had evo 4g I have rom racer recovery already so you guys think its a problem with the stock rom then?
sent from unlocked rooted atrix.
Maybe the way its loaded onto your phone in particular is causing the problem. I've had the same rom on my phone and its international.
Sent from my MB860 using XDA App
Well do u think it may have been the root process or unlock process what's weird is I can reboot today five time 0 issues them boom problem im just stumped but will take the advice and flash a rom is there a stock 2.3 rom avaible I kinda like stock android
sent from unlocked rooted atrix.
Version 4.5.91.mb 860.att.us does this seen right for ota update im wondering now if when.I rooted or unlocked something changed. Because I remeber I had a soft brick.
sent from unlocked rooted atrix.
Any help would greatly be appreciated and those that have helped thanks a million I have flashed red pill and restored with titanium backup and still same problems it booted up fine then I used it for about and hour then tried to power down and reboot stuck at att rethink posibble . Is there a way to remove root and lock then bootloader back for.
sent from unlocked rooted atrix.
Judging by your post it seems your Atrix is not turning on. That is an issue.
Sent from my MB860 using XDA App
Well yes its a issue lol any idea how to fix I can make if turn on by wiping caches and factory reset then restore with titanium backups .then if runs and functions fine then craps out so your opinion hardware or software im within my 30 days AT&T may get it back I hope they don't notice the bootloader is unlocked though lol.
sent from unlocked rooted atrix.
Try fixing permissions through ROM manager, I find that when flashing a new ROM weird things happen and this usually fixes it. I'm hoping it's something as simple as that, because if not you may have a hardware problem.
you can prolly just go back to stock from a fruit cake and then start over .
Im going to try something this is getting old real quick. I want to turn my phone off sometimes just wish I new it would boot backup.
sent from unlocked rooted atrix.
I tried to flash CM7 beta, and it wouldn't go past the glowing red motorola logo. (I waited for a good five minutes) I went back to CWM to restore my backup of rooted stock. It ran through the process fine, but now it is just bootlooping. I have done a factory/data reset as well as wiping the cache multiple times. I tried flashing an SBF, but the phone went into the bootloop during the process. Now I have a dead phone that won't boot. Can someone please give me direction?
I know your phone is rooted by what you said, but is your phone have an unlocked bootloader? Did you have the latest recovery also?
Sent from my ATRIX 4G XDA Premium App
I have solved the problem. I found the solution in the following link for anyone that may find this thread.
http://forum.xda-developers.com/showthread.php?t=1177481&page=2
K, so i was looking for some different boots and and was going thru a few and rebooting.. no problem. Found one i liked thru rom toolbox, it was a different aokp boot. Im running aokp 6 so decided i liked it. CLicked on install from rom tooolbox and went to reboot to see if it took and wala.. i have a boot loop. Removed the battery umpteen times, cleared the cache partition from recovery but it wont let me into the phone. All i get is the big m then the boot anim and the recycle, over and over. is there any other way to get back in. Gonna go back to stock boot once i get in but getting there is the problem...
i formatted /wiped data.... still boot loopin. so do i have to sbf again?
Pull the battery, then put the battery back in and plug it into a charger. That should get you to bsr and from there reflash your rom.
Sent from my DROID X2 using xda premium
he already wiped date, bsr is gone
Sent from my DROID X2 using xda premium
You gotta SBF. Never use ROM Toolbox on the X2.
Yea I sbf'd last night. Back in working order. I only had stock recovery and nothing worked. Thank god I had a backup. Yea and I did not reinstall from TV. Live and learn. Thanks guys
It was bootlooping because of memory running out and it would crash. For ics roms its best to leave boot animations as they are to insure that what you experienced doesn't happen.
Sent from my DROID X2 using xda premium
I tried flashing the Droid DNA Cubed Kernel 2.4.2, but forgot to flash the modules before rebooting. When the phone loaded up, all I got was a black screen with a title bar that would restart when I tried to unlock. I then restarted, flashed the modules, and I continued to get the same black screen. I even tried flashing back to the stock kernel with no luck. The only thing that fixed it was doing a factory reset. I had rooted stock with an unlocked bootloader. I didn't see mention of a required factory reset, so what went wrong? Thanks.
I'm not sure what went wrong, and factory reset is not required.
How did you flash the kernel?
I flashed the boot.img from fastboot, then installed the modules in TWRP after the blackscreen.
StormChaser46 said:
I flashed the boot.img from fastboot, then installed the modules in TWRP after the blackscreen.
Click to expand...
Click to collapse
That's normally what I do but I flash the modules before booting, which is how it should be done.
Exact same thing happened to me. I did the factory reset and started from the beginning again. It really scared me but now I have actual root access with superSU having no issues. So much happier now.
Anyways, the point is. If you mess that step up, just factory restore and do it again... The right way lol
Sent from my HTC6435LVW using xda app-developers app
Just flashed back to stock kernel from Flash Image GUI because I kept getting crashes/restarts on cubed, and no black screen this time. Not sure what the problem was, just hope it doesn't happen again lol.
StormChaser46 said:
Just flashed back to stock kernel from Flash Image GUI because I kept getting crashes/restarts on cubed, and no black screen this time. Not sure what the problem was, just hope it doesn't happen again lol.
Click to expand...
Click to collapse
So you did a factory reset and tried cubed again but still didn't work?
It did work after a factory reset, but I got crashes/reboots out of nowhere. I saw other people were also reporting occasional crashing, so I'll stick with stock til it's a little more stable.
Understandable, I get a random hangups every other day or so and it restarts... But the pro's outweigh the cons imo. But I agree with you as well .
Coming from a DX, I got used to random reboots here and there after rooting hahah
Sent from my HTC6435LVW using xda app-developers app
I've been trying to load a new rom onto my fascinate sch-i500v for a few hours now. I previously had a 4.1 build (milestone I think) and cwm 4.0.1.0 installed. I've tried every rom from cw10 to hellybean to avatar and they all do the same thing. I wipe the cache, factory reset. Then installed from the zip file. At this point, the install starts to initiate, but the phone suddenly reboots and after a few seconds tries to load up the old rom (unsuccesfully, hence why I said I'm seeing the "initiating swagger" load screen forever)
Yesterday, I did this exact upgrade successfully to my other fascinate sch-500 (no v on the end for that one, not sure if that makes any difference).
That one rebooted suddenly as well, but it went back into the clockwork recovery and completed the install without a hitch.
Anybody have any suggestions? I'm sort of a noob, but I have flashed over ten phones...
Go back to stock and start over
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
Go back to stock and start over
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Thank you. i fugured that was what I needed to do, but I was afraid of how complicated it would be. LMFAO, it was pretty simple!