so I installed v6 supercharger and I used the kernel tweaks and now im boot looping.
I tried to wipe data from factory recovery, and im still boot looping.
I cant get past the M logo....
does anyone know how to get into the modified recovery to run a restore?
tprouty said:
so I installed v6 supercharger and I used the kernel tweaks and now im boot looping.
I tried to wipe data from factory recovery, and im still boot looping.
I cant get past the M logo....
does anyone know how to get into the modified recovery to run a restore?
Click to expand...
Click to collapse
If you've tried wiping from android recovery and you're still stuck at M, you'll have to sbf.
Sent from my MB870 using xda premium
Jubomime said:
If you've tried wiping from android recovery and you're still stuck at M, you'll have to sbf.
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
This.
Sent from my MB870 using xda premium
Get the init scripts I the cm7 .zip and push to correct spot...the set correct perms.
Tapin' the Talk on the xSquared
If you're getting stuck at the M while trying to boot back into BSR, then it means you didn't flash the patched BSR after installing CM7. You must install the new BSR after booting into CM7 if you wish to flash anything after that.
At this point, since you used the V6 Turbocharger scripts (which HAS a disclaimer that it CAN cause bootloops, so I would suggest staying away from it), you're going to have to SBF back and start over since you can't even boot up to even try to fix the issue. If you would have installed the patched BSR after installing CM7, then you would be able to boot into BSR and reflash CM7 to fix your issue.
Factory reset won't help. it doesn't wipe out the init.d scripts which is why that didn't help.
I have installed the patched BSR, and used it so I know it works.
tprouty said:
I have installed the patched BSR, and used it so I know it works.
Click to expand...
Click to collapse
Okay. Usually, the hanging at the M is a sign of using the wrong BSR. I guess at this point, your only recourse is to SBF.
Just remember, the original BSR can be used BEFORE you flash CM7 on. But, once you have CM7, you must install and run the patched BSR before you attempt to reboot into BSR or you get the symptoms you were describing.
I had this issue the first time I used CM7. I ran the APK to install the program, but I forgot to actually RUN the BSR application and tell it to install itself and then click on the Recover button. So, even though I installed the APK itself, I forgot to actually install the recover program to run upon reboot.
Luckily, I wasn't at a boot loop, so I just booted back into CM7 and finished the steps I missed.
The problem is probably caused by the V6 Supercharger script. They may not work with CM7. As well as probably all the other scripts out there unless its modified right.
Thanks for all the input, trying to start the SBF now.
I had BSR all set for CM7, ran the install recovery after loading CM7 and actually installed a zip(speedy V7) after being on CM7.
I removed all those files with speedy and wanted to use V6 because it worked better when i was on eclipse than speedy did. I was running the scripts and wanted to test the waters with the kernel script and thats where i got hung up. all the other scripts in V6 workd great! lesson learned dont mess with kernel tweaks when i get back up!
The I/O scheduler tweak in KAK is known to cause bootloops on the X2
SBF'd from my tasty X2 MAXX
Related
Um think i just did something stupid, I flash flaux123 new kernel for cm7 and I also flashed the 4.5.91 wake on volume zip.. Now im stuck with a bootloop.. And I had just set my phone up with all my apps and the way I wanted it.. So my question is can I come from the bootloop some how without having to redo the whole install of CM7??
That feature is already built into CM. Wipe it and re-install. Since you're running pre-beta software its something you're going to have to get used to anyway...
henrys01 said:
That feature is already built into CM. Wipe it and re-install. Since you're running pre-beta software its something you're going to have to get used to anyway...
Click to expand...
Click to collapse
oh ok, thx and u right imma have to get used.. Im a flash junky anyways..lol
I had the same issue. I went in and did a data wype and it fixed the boot loop
Sent from my Motorola Atrix 4G MB860 using XDA App
you could also try to flash the boot.img from inside the cm7 zip, if you're stuck in a boot loop after wiping cache/user data
Hello guys.. I got a serious problem with my atrix.
today morning , I tried to install the CM7 and it was success. It works well,
but It's not my style so I wanted to go back to pure stock rom.
I used RSD and flashing olympus 4.5.91 rom. and my Atrix died.
it was just appeared M logo and turn off, and appeared M logo and turn off again and again.
what should I do in this happen? OMG................. i have to use my phone asap..................................
plz help me clever guys!!!!
Thanks
Can you get into recovery? You should've flashed fruitcake. RSD is a no-no.
Sent from my MB860 using XDA App
Nono flashing a gingerbread. Sbf wont hurt anything. But fruitcake is easier yes. Also plug your phone into the wall outlet. Let it do its thing. Then pull the battery out while its still plugged in. Leave it out 30 seconds. Then stick it back in and see if it charges.
Sent from my MB860 using Tapatalk
Phalanx7621 said:
Nono flashing a gingerbread. Sbf wont hurt anything. But fruitcake is easier yes. Also plug your phone into the wall outlet. Let it do its thing. Then pull the battery out while its still plugged in. Leave it out 30 seconds. Then stick it back in and see if it charges.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Hi guys, I'm having the same problem as the OP. Here's my story:
- Got my phone with 2.3.4/4.5.91.
- Used Automatic Scripts to unlock BL and root.
- Everything was working fine.
- Flashed Tenfars' recovery.
- Everything fine again.
- Switched to RomRacer's recovery to test it.
- All good so far.
- Flashed CM7 thru recovery and it all went down.
- Got in a bootloop, showed CM7 boot animation and rebooted.
- Tried to ditch CM7, so restored my backup previously done via Recovery.
- Bootloop again, instead of CM7 animation, showed the M logo and reboot.
- Freaked out.
Fastboot and recovery work. Connected the charger and displayed the battery charging. Am thinking about installing some "Official Motorola 2.3.4/4.5.91 MSU" that is recommended on the Auto Script.
dr_tracker said:
Fastboot and recovery work. Connected the charger and displayed the battery charging. Am thinking about installing some "Official Motorola 2.3.4/4.5.91 MSU" that is recommended on the Auto Script.
Click to expand...
Click to collapse
Since you can get into fastboot and recovery, just try flashing a fruitcake.
Are you still using romracer's CWM? Was the backup you're trying to flash made with romarcer's or Tenfar's? I now people had issues when trying to flash backups made with tenfar's after upgrading to romracer's. I think it had to do with how each CWM formats.
ghost_og said:
Since you can get into fastboot and recovery, just try flashing a fruitcake.
Are you still using romracer's CWM? Was the backup you're trying to flash made with romarcer's or Tenfar's? I now people had issues when trying to flash backups made with tenfar's after upgrading to romracer's. I think it had to do with how each CWM formats.
Click to expand...
Click to collapse
Thanks, downloading fruitcake as we speak, the one that reads "2.3.4 System and Boot NO Webtop (Updated Newest Script)", right???
Backup was made with Tenfar's, I instaleld Romracer and flashed CM7, switched back to Tenfar prior to restore, so not to mix backups.
One Q, after I flash this fruitcake, can I restore my backup and go on with my stock motoblured life???
TIA.
dr_tracker said:
One Q, after I flash this fruitcake, can I restore my backup and go on with my stock motoblured life???
TIA.
Click to expand...
Click to collapse
That I don't know. Don't see why not. But I don't want to give advice on something I haven't done personally. Plus I have never used tenfar's recovery. ( I believe it's out of date?) Search time
Sent from my MB860
You can't restore backups made with tenfars recovery with romracers later on.
Thanks alot guys, fruitcake did the trick. At the Motoblur registration screen, just rebooted to recovery and restored my backup, everything is up again.
long story short ......with the new beats audio news out i flashed that and got stuck at the M logo on boot.
I pulled the battery plugged in and booted but still the same, stuck at M logo. Why is my bootstrap not working? i used it earlier today.
I also tried getting into the stock android recovery but then it just gets stuck at the android guy next to the triangle with the ! in the middle.
How do i get back into bootstrap so i can flash my nandroid backup! Thanks guys!
p.s. i have tried it numerous times hoping it would eventually work but nothing.
droid x2
2.3.4
rooted
stock rom
Did you flash the zrecovery before you rebooted?
http://forum.xda-developers.com/showthread.php?t=1426062
Might save you next time
Also if you wiped data your bootstrap will be gone.
not sure what zrecovery is?
i have the bootstrap recovery installed and have been using that for months without a hitch, just after i flashed the beats audio zip this morning (in bootstrap), i can't get it to even boot. im stuck at the M logo. and if i pull the battery and plug in, it won't even start up to bootstrap. I just want to flash my nandroid backup
i didn't wipe data, just flashed the zip. chose reboot in Bootstrap like normal and bam, stuck at M logo.....any way to force back into bootstrap? I was literally just in bootstrap 1 hr ago so i know its there....just not loading
Not that I aware of besides doing a sbf rooting again and installing bootstrap and then you can restore your nano back up.
Be sure to pull the battery for 30 sec put back and then plug in to get cwr to boot. Or Then try to access stock recov pwr on & rocker down to wipe data.
Thanks for the help!
As far as I know, the only way to get into bootstrap is through the bootstrap app itself. Which you need to be able to get into your phone to do. I do think you can get into it by rebooting while plugged in but maybe this doesnt work if you did something to mess up the startup. As was mentioned already, your only choice most likely is to SBF, root and install bootstrap again and then restore your backup.
I beg to differ. As long as charge mode was never put back to normal which is also a mistake.
jsgraphicart said:
As far as I know, the only way to get into bootstrap is through the bootstrap app itself. Which you need to be able to get into your phone to do. I do think you can get into it by rebooting while plugged in but maybe this doesnt work if you did something to mess up the startup. As was mentioned already, your only choice most likely is to SBF, root and install bootstrap again and then restore your backup.
Click to expand...
Click to collapse
if u have BSR installed and u haven't wiped data or flashed any new ROM, u can just power down/battery pull and u will boot into BSR, it hijacks charge only mode
Sent from my DROID X2 using Tapatalk
sending out an SBF, my God there are great tutorials here in General and Android Dev sections... Cwr is not part of DX2 BSR is, but you wiped and lost that. To enter stock Android Recovery you just hit power button volume down...but that won't help you now...so just SBF and root then restore your backed up material through Titanium backup.... Install BSR and NANDroid back...you did make NANDroid backups I assume, if not I suggest starting to. Good luck
Dee Ex Two - See Em Seven
viskey said:
long story short ......with the new beats audio news out i flashed that and got stuck at the M logo on boot.
I pulled the battery plugged in and booted but still the same, stuck at M logo. Why is my bootstrap not working? i used it earlier today.
I also tried getting into the stock android recovery but then it just gets stuck at the android guy next to the triangle with the ! in the middle.
How do i get back into bootstrap so i can flash my nandroid backup! Thanks guys!
p.s. i have tried it numerous times hoping it would eventually work but nothing.
droid x2
2.3.4
rooted
stock rom
Click to expand...
Click to collapse
sending out an SBF, my God there are great tutorials here in General and Android Dev sections... Cwr is not part of DX2 BSR is, but you wiped and lost that. To enter stock Android Recovery you just hit power button volume down...but that won't help you now...so just SBF and root then restore your backed up material through Titanium backup.... Install BSR and NANDroid back...you did make NANDroid backups I assume, if not I suggest starting to. Good luck
Dee Ex Two - See Em Seven
ashclepdia said:
if u have BSR installed and u haven't wiped data or flashed any new ROM, u can just power down/battery pull and u will boot into BSR, it hijacks charge only mode
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
Thats what I thought. But the OP cant get that to work from what I get. Is that method still supposed to work if you cant even boot the phone?
As long as you do not wipe data BSR should be installed. If you pull battery and put it back in before you even try to boot plug it in to wall charger. This will take you straight to BSR before you ever try to boot. Then you can get back to your nano back up.
"I also tried getting into the stock android recovery but then it just gets stuck at the android guy next to the triangle with the ! in the middle."
@ the triangle Push the middle of the rocker to get to stock recovery. (both up and down at same time)
skwoodwiva said:
"I also tried getting into the stock android recovery but then it just gets stuck at the android guy next to the triangle with the ! in the middle."
@ the triangle Push the middle of the rocker to get to stock recovery. (both up and down at same time)
Click to expand...
Click to collapse
Good advice skoodwiva. Is is safe to use stock recovery? If so why do we have a special one?
Sent from my MB870 using XDA App
king..kranium said:
Good advice skoodwiva. Is is safe to use stock recovery? If so why do we have a special one?
Sent from my MB870 using XDA App
Click to expand...
Click to collapse
Stock recovery wont allow you to flash stuff to the phone or backup your ROM or stuff like that. Thats why we have a special one to do those things.
Stock is good for flashing an ota (no need to rename just make it start w/ a number so it will be first in a mess of zips at the root of your external sd)
And wiping data.
jsgraphicart said:
Thats what I thought. But the OP cant get that to work from what I get. Is that method still supposed to work if you cant even boot the phone?
Click to expand...
Click to collapse
I'm not sure...been a while since I got to M logo stuck without wiping data or doing something that trashes BSR which would make it not work...
by the way viskey
what it's this "beats" zip u flashed??
by the way viskey
what it's this "beats" zip u flashed??[/QUOTE]
I was wondering the same thing.
First of all, THANK you for making progress on freeing our phones!
I have read every thread I can find on this, but I cannot find an answer to my specific problem.
I will try to make this brief.
Now onto my problem.
I am on Gingerbread 2.3.4
I tried yesterday to go to CM7
I followed the directions posted here.
I get to step 12 on the " HowTo: Perform a bootstrap (or nandroid) backup and recovery of your Motorola Droid X2" where I am tapping recovery mode and the phone reboots - but when plugged into a wall charger, I get stuck at the dreaded dual core screen.
Since this happened, I have went into my ASR and selected wipe cache, wipe partition and also did the factory data reset while the phone was booted up.
Even in this state, which should be reset to factory if I understand this correctly - when I plug into a wall outlet, it still will not boot past the dual core screen.
Any ideas?
One question I have is, how do I wipe davilik cache?
Please help!!
Reinstall dx2bsr.apk Run it. Install recovery. Set recovery mode. Flash cm7 Then wipe all 3. Then while still in cwr flash ReRecoverydx2.cm7..... see my sigy link.
skwoodwiva said:
Reinstall dx2bsr.apk Run it. Install recovery. Set recovery mode. Flash cm7 Then wipe all 3. Then while still in cwr flash ReRecoverydx2.cm7..... see my sigy link.
Click to expand...
Click to collapse
On it.
Thank you sincerely for your help! I know how noobish I am.
skwoodwiva said:
Reinstall dx2bsr.apk Run it. Install recovery. Set recovery mode. Flash cm7 Then wipe all 3. Then while still in cwr flash ReRecoverydx2.cm7..... see my sigy link.
Click to expand...
Click to collapse
Hmm.. Well, I may need more detailed instructions.
I reinstalled dx2bsr.apk.
Ran it
installed recovery
set recovery mode
Then I am stuck. I am not sure what this means "Flash cm7 Then wipe all 3. Then while still in cwr flash ReRecoverydx2.cm7"
I am able to boot into the os now, but it still sticks at the dual core screen.
I'm sorry I a$$umed you were on Blur. No?
If ON cm7 you must install the cm7 (see the OP) bsr.apk.
ejlarson249 said:
Hmm.. Well, I may need more detailed instructions.
I reinstalled dx2bsr.apk.
Ran it
installed recovery
set recovery mode
Then I am stuck. I am not sure what this means "Flash cm7 Then wipe all 3. Then while still in cwr flash ReRecoverydx2.cm7"
I am able to boot into the os now, but it still sticks at the dual core screen.
Click to expand...
Click to collapse
to wipe dalvik cache you go into advanced and then scroll down to dalvik cache and then if you want wipe battery stats. That should work out of it all. If anything, sbf back to 2.3.4, root, and then retry with the OG bootstrap and see where that takes you
No matter what I do, various combinations of putting the stock bootstrap back in, it will not reboot while plugged in. It freezes on the dual core screen.
I have done a full wipe, it still will not boot while on AC.
Ideas?
You are trying to boot What Rom???
If you have already flashed cm7 you MUST allow it to boot ( do a stock recovery wipe if needed-stuck @ m) then install cm7bsr.apk.
ejlarson249 said:
No matter what I do, various combinations of putting the stock bootstrap back in, it will not reboot while plugged in. It freezes on the dual core screen.
I have done a full wipe, it still will not boot while on AC.
Ideas?
Click to expand...
Click to collapse
are you running the bootstrap while plugged in? try untethering it, running BSR then plugging it in when your phone turns off.
What I want to accomplish is running CM7.
I am currently running 2.3.4.
This is so frustrating!
I am currently reading through the link in your sig, but that isn't clear enough either.
Sorry, I am not getting this, there is too much jargon I don't understand. LOL!
ejlarson249 said:
What I want to accomplish is running CM7.
I am currently running 2.3.4.
This is so frustrating!
I am currently reading through the link in your sig, but that isn't clear enough either.
Sorry, I am not getting this, there is too much jargon I don't understand. LOL!
Click to expand...
Click to collapse
sorry, bro, are you booting into the bootstrap (BSR) while you're plugged into the wall outlet? If you are try to run BSR while not plugged into <the wall> and then once the phone shuts off [black screen] plug it in and then see if it boots into BSR.
You can boot to blur 234.
reinstall our old bsr and get it working.
This should get you to cwr.
---------- Post added at 10:23 AM ---------- Previous post was at 10:19 AM ----------
Then flash cm7 and gapps then wipe all three than flash rerecovery.cm7
I would suggest SBFing back to stock 2.3.4 blur and then follow the steps in the OP for cm7. Seems your very setup is very screwed up at this point. Sometimes it is just easier and faster to do a quick SBF and start over. Just my two cents
Well through some combination of things, it looks like I am magically in CM7.
Thanks all!
motcher41 said:
I would suggest SBFing back to stock 2.3.4 blur and then follow the steps in the OP for cm7. Seems your very setup is very screwed up at this point. Sometimes it is just easier and faster to do a quick SBF and start over. Just my two cents
Click to expand...
Click to collapse
Btw OP, you should probably learn how to do this. (sbf'ing)
It has saved ass after ass.
thelowend said:
Btw OP, you should probably learn how to do this. (sbf'ing)
It has saved ass after ass.
Click to expand...
Click to collapse
yes, yes it has, haha
Sent from my MB870 using Tapatalk
Okay, so I was going to install the new cm9 alpha rom that was released. But every time I try to BSR; superuser denied the permission. Even though I have it set to allow it.
But what I though was weird was that if I powered my phone off. Then plugged it into a charger, that the BSR screen appeared. So I made a nandroid recovery of my 2.3.5 OS and then tried to flash cm9. But then it started to give me errors. So I then was gonna just recover the nandroid backup since I factory reset and clear cache. but then it froze trying to recover.
Then I though that I should just power back on my phone then try it again. So I did that and now the BSR screen won't appear it just shows the motorola logo and stays there. HELP!!
I think we will need clarification of your abbreviations before we can help you. Do you mean, SBF or BSR. SBF means you use RSDLite to re-flash your phone to a stock state, and BSR is your Boot Strap Recovery. Unless I'm missing something.
Sent from my DROID X2 using XDA
BSR sorry...
Have you tried holding down the volume button when you power up, plugged into the wall? That should get you into Android Recovery. I believe you may see a lil Droid with a triangle. Then press both volume up and down at the same time. Your menu should appear.
The first problem I saw when reading the OP was that you need to be on 2.3.4 to flash CM9.
jsgraphicart said:
The first problem I saw when reading the OP was that you need to be on 2.3.4 to flash CM9.
Click to expand...
Click to collapse
Totally... right...
You will throw so many errors running 2.3.5 kernal ( which only goes back to 2.3.4 with an sbf)
Sent from my MB870 using Tapatalk 2
6Flip9 said:
Totally... right...
You will throw so many errors running 2.3.5 kernal ( which only goes back to 2.3.4 with an sbf)
Sent from my MB870 using Tapatalk 2
Click to expand...
Click to collapse
Yeah i sbf back to 2.3.4 and had to re-root my phone and start all over. So everything is working fine. I think the problem was that I updated to 2.3.5 and it unrooted me but still had the superuser.apk installed but not let me have su permission. eather way I fixed it.