Related
After I flashed the atrix alien port to my X2 my phone no longer recognizes my battery and will not charge it. Is anyone else having this problem? Are there any fixes to address this problem? If this has been addressed somewhere else I apologize I couldnt find it. Any help is appreciated, dont want to have to sbf back to stock.
Thanks
AW
atcbrownie said:
After I flashed the atrix alien port to my X2 my phone no longer recognizes my battery and will not charge it. Is anyone else having this problem? Are there any fixes to address this problem? If this has been addressed somewhere else I apologize I couldnt find it. Any help is appreciated, dont want to have to sbf back to stock.
Thanks
AW
Click to expand...
Click to collapse
Are you on v0.2 or v0.2.2?
when it happened to me I'd made the mistake of installing the rom over froyo
dragonzkiller said:
Are you on v0.2 or v0.2.2?
Click to expand...
Click to collapse
using v0.2.2. I just sbf'ed to 2.3.3 and am letting the batt charge again and am going to try to wipe the battery stats and see if that works. Thanks for the help, I will post my results.
Well just finished sbf'ing and flashing v0.2.2 again making sure to wipe dalvik, battery, cache, and data factory reset. Still get the battery message that says battery not recognized wil not charge.
If there are not any other ideas by tomorrow morning when I get up I will sbf again and try to download again and re-flash v0.2.2. Maybe a file was corrupt or something, I dunno.
Has anyone else had this problem?
Are you using a Motorola battery? Sometimes generics don't play well with custom roms.
Sent from my DROID X2 using xda premium
yep stock battery.
Well i have other issues other than the battery. The phone randomly goes crazy and just starts acting like I am hitting buttons, opening programs and typing random letters. I tried re-downloading the rom and re-flashing but still the same issues with the battery. I guess I will sbf back to stock and wait for another update. who knows it may be an issue with my phone since no one else seems to have this problem.
Thanks
AW
I've been using this ROM version since I released it and have yet to run into any problems you described. Is there any other information you can give me?
Sent from my DROID X2 using XDA App
Yes this happend to me. What you did was probally flashed oved 2.2. Thats a no.no. Heres the fix. RSD flash the official verizon 2.2. then root with gingerbreak. Then install custom recovery. Enter recovery mode. Wipe all. You must do this for it to work.Flash P3's pre rooted gingerbread. After install then go into recovery, wipe again then flash alien rom. It worked for me. You cant cross flash roms, they have to go into this order. 2.2, 2.3.3, 2.3.4.
Sent from my DROID X2 using, wait is that a Gorilla?
Furioustylez said:
Yes this happend to me. What you did was probally flashed oved 2.2. Thats a no.no. Heres the fix. RSD flash the official verizon 2.2. then root with gingerbreak. Then install custom recovery. Enter recovery mode. Wipe all. You must do this for it to work.Flash P3's pre rooted gingerbread. After install then go into recovery, wipe again then flash alien rom. It worked for me. You cant cross flash roms, they have to go into this order. 2.2, 2.3.3, 2.3.4.
Sent from my DROID X2 using, wait is that a Gorilla?
Click to expand...
Click to collapse
I appreciate your effort to help but this is not what happened. I flashed from the official Verizon 2.3.3, then used red lite to she back and tried again. I have tried this rom at least 4 times now everytime I get the same results.
Dragon, thanks for your willingness to help. Basically what happens is the rom v0.2.2 flashes with no errors. When the phone boots I immediately get a message saying that my battery is not recognized and that I need to install a moto battery. After I hit the ok button the phone acts like a pc when you mash on the keyboard all different apps open up, random keys get typed, when I hit the home button the programs just open back up like ten at a time. Its kinda hard to explain. When I get off work tomorrow I will try to reflash ATRIX alien and post a video of what is going on.
atcbrownie said:
When the phone boots I immediately get a message saying that my battery is not recognized and that I need to install a moto battery. After I hit the ok button the phone acts like a pc when you mash on the keyboard all different apps open up, random keys get typed, when I hit the home button the programs just open back up like ten at a time. Its kinda hard to explain. When I get off work tomorrow I will try to reflash ATRIX alien and post a video of what is going on.
Click to expand...
Click to collapse
I have seen videos of x2s doing this on youtube, probably need a new phone
Sent from my DROID X2 using XDA App
atcbrownie said:
I appreciate your effort to help but this is not what happened. I flashed from the official Verizon 2.3.3, then used red lite to she back and tried again. I have tried this rom at least 4 times now everytime I get the same results.
Dragon, thanks for your willingness to help. Basically what happens is the rom v0.2.2 flashes with no errors. When the phone boots I immediately get a message saying that my battery is not recognized and that I need to install a moto battery. After I hit the ok button the phone acts like a pc when you mash on the keyboard all different apps open up, random keys get typed, when I hit the home button the programs just open back up like ten at a time. Its kinda hard to explain. When I get off work tomorrow I will try to reflash ATRIX alien and post a video of what is going on.
Click to expand...
Click to collapse
Unfortunately, there appears to be no real solution to this. I hate to say that, but no one else is having these issues, then it must simply be a problem with your phone. I wish you luck, but there's not much I can do if your phone is acting up. I wish there was more I could do to help.
dragonzkiller said:
Unfortunately, there appears to be no real solution to this. I hate to say that, but no one else is having these issues, then it must simply be a problem with your phone. I wish you luck, but there's not much I can do if your phone is acting up. I wish there was more I could do to help.
Click to expand...
Click to collapse
Thanks for your help I don't know what the issue is, it doesn't happen on stock gingerbread just on the ATRIX rom. Thanks anyway. I will keep an eye on your dev thread and will try again when the next patch comes out.
when i was on the alien port i did not have any battery problems. did the same thing as you sbf'ed to the official verizon 2.3.3 rooted and then onto the alien rom. my friend was having some issues however and what helped him was sbf'ing to 2.2.2, then rooting, then flashing p3's pre-root gingerbread onto that. after that his phone accepted the alien rom just fine. not sure what if any difference there is between the methods but it helped him.
Yeah like I said you cAnt do that . You have to flash 2.2 first
Sent from my DROID X2 using XDA Premium App
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.
I put the miui rom on my phone and i did the factory reset so now i have to reactivate my phone. The problem is it wont reactivate when i dial *228 it says problem with activation. What could be the problem please help.
Try *22899
got the same thing
Unless the Verizon activation is down again. Was a few weeks ago. Just curious as to why u did a factory reset in miui?
Sent from my Eclipsecrack using Xparent Blue Tapatalk
Update...activation works scratch that.
Sent from my Eclipsecrack using Xparent Blue Tapatalk
I had the same problem a couple of weeks ago. Called Verizon and they were doing updates. Next morning I called and they said it was back up. However I still could not activate then I restored to stock and activated no problem. Then restored my cm7 without activation and then it was fine.
Do a backup now and restore back to stock. Activate and then restore your miui.
Can I sbf? If so does anyone know any good tutorials
Sent from my DROID X2 using XDA App
Did you do a nano back up of your stock rom? If so just restore that. If not do that first before making changes that way you can save yourself from a SBF.
if you do not know how to do a nano backup follow this http://forum.xda-developers.com/showthread.php?t=1318083
Sadly no does that mean I am screwed
Sent from my DROID X2 using XDA App
Follow this to sbf http://forum.xda-developers.com/showthread.php?t=1317707
Then after you activate root and download the tenfar recovery from stickies then make a nano backup first that way if you get in trouble you just restore back to stock.
Travisdroidx2 said:
Follow this to sbf http://forum.xda-developers.com/showthread.php?t=1317707
Then after you activate root and download the tenfar recovery from stickies then make a nano backup first that way if you get in trouble you just restore back to stock.
Click to expand...
Click to collapse
Thanks for the help
Sent from my DROID X2 using XDA App
No problem the sbf is not as bad as some might make it sound. You just have to make sure you download all the drivers and the SBF file and rsd lite. If you get stuck do be scared to ask. Also if you never did a SBC remember to get your phone to communicate with rsd lite you turn phone off and hold power and volume button up at same time and it will boot you to red mode then you are good.
Travisdroidx2 said:
No problem the sbf is not as bad as some might make it sound. You just have to make sure you download all the drivers and the SBF file and red lite. If you get stuck do be scared to ask. Also if you never did a SBC remember to get your phone to communicate with rsd lite you turn phone off and hold power and volume button up at same time and it will boot you to red mode then you are good.
Click to expand...
Click to collapse
+1 takes a couple min to download and install beyond that its easy easy lemon squeezy
Sent from my Eclipsecrack using Xparent Blue Tapatalk
Also if your phone bootloops after sbf do not panic it is normal sometimes coming from a custom rom. You can fix it easily by doing a restore factory reset in android recovery not bsr. If you do not know how to do it let us know and we will explain it.
So if you do bootloop after sbf rebooted your phone 100% then pull battery and put it back in. Now instead of hitting up volume and power this time use down volume and power at same time. You will see fastboot use volume down button to scroll down to android recovery. When you see android recovery then hit volume up this will bring you to android and big grey triangle then hit both volume up and down at same time. Now you will be in android recovery. Volume rocker to factory reset and hit the power button and use volume buttons to choose yes. After its done select reboot and you will load up just fine after that.
Let us know if it works for you. Or if you have any more questions. Remember cm7 is awesome unless you need HDMI. Eclipse is great as well and HDMI works. I have eclipse nano back up so if I need HDMI I can just restore.
Did all the stuff last night it all worked fine. I had the bootloop and it worked. Reactivated it with no problem. Once again thanks for all the help.
Sent from my DROID X2 using XDA App
LAWSON72 said:
Did all the stuff last night it all worked fine. I had the bootloop and it worked. Reactivated it with no problem. Once again thanks for all the help.
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
Awesome! Glad to help I remember being in your shoes before. Did you make your nano back up of stock to make it easier for you?
Ya I did a backup this time
LAWSON72 said:
Ya I did a backup this time
Click to expand...
Click to collapse
Perfect now you can try a rom if you like it then back it up. I have had up to 4 different Roms backed up so you can restore which ever you like. Glad it helped! Just make sure you stick with the same kernal like the 2.3.4. If you ever go to 2.3.5 you will have to sbf back to 2.3.4 to get the kernal right.
If you could put [solved] in your title next to your problem and this might help someone else with the same issue.
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.
Since the last time I flashed CM7, RSD (any version) with any SBF file doesn't wipe my phone the way it used to. It's gotten to the point I can no longer flash custom ROMs. If I don't wipe data/cache first, it will flash a new SBF yet leave the apps that were on it before hand. And when I try to flash a custom ROM, I get an error every time. Did I mess up something down in the locked areas that can never be fixed? Is there another way to wipe the phone to a more original or basic point? Right now I'm completely wiping the int and ext sd-cards, wiping data/cache/dalvik, SBFing to 2.2.2, and OTAing back up to see what happens, though I'm doubting it will help.
edit: Didn't work. Still can't flash a custom ROM. I can run rooted stock 2.3.5 though, guess that's what I'm stuck with. Better than nothing.
Performing an SBF does not wipe any user data from the phone. Wipe the phone using the stock recovery before performing the SBF. There are many threads on here on how to SBF, root, and install your favorite ROM.
RyanThaDude said:
Performing an SBF does not wipe any user data from the phone. Wipe the phone using the stock recovery before performing the SBF. There are many threads on here on how to SBF, root, and install your favorite ROM.
Click to expand...
Click to collapse
It doesn't matter if I wipe everything or not, I still can't flash a custom ROM. Get an error every time, and have to SBF to get it bootable again. I had weird issues the first time I ran CM7 and tried to SBF back to stock. Took multiple battery pulls and random button pushing while rebooting before I could get it back into RSD mode. This last time let me SBF back fine, but I get the PASS result instead of the REBOOT PHONE MANUALLY now and can't flash anything.
Scur827 said:
It doesn't matter if I wipe everything or not, I still can't flash a custom ROM. Get an error every time, and have to SBF to get it bootable again. I had weird issues the first time I ran CM7 and tried to SBF back to stock. Took multiple battery pulls and random button pushing while rebooting before I could get it back into RSD mode. This last time let me SBF back fine, but I get the PASS result instead of the REBOOT PHONE MANUALLY now and can't flash anything.
Click to expand...
Click to collapse
Try this a files sometimes corrupt.
Download all new. Perform the sbf, while the phone reboots do the volume down power button thing to get into Android Recovery. Once there wipe data and cache....
I have about 10 cables in my house...only two or three work for flashing and such...try a different cable....
DROID DOES, Apple did...like I forgot when
Pixelation said:
Try this a files sometimes corrupt.
Download all new. Perform the sbf, while the phone reboots do the volume down power button thing to get into Android Recovery. Once there wipe data and cache....
I have about 10 cables in my house...only two or three work for flashing and such...try a different cable....
DROID DOES, Apple did...like I forgot when
Click to expand...
Click to collapse
I have a couple good cables that always work, tried them both. Wiped data and cache on SBF reboot, too. Rooted with One click and Pete's both. So far, nothing works.
are you sure, sbf is flashing correct?
try different version like 2.2.3 or 2.3.5
and check system info after to verify
then update.zip or flash 2.3.4 sbf
or try ezsbf to flash and/or root
Sent from my MB870 using xda premium
i've seen usb cables work with one device and not another, can be hard to tell
Sent from my MB870 using xda premium
sd_shadow said:
are you sure, sbf is flashing correct?
try different version like 2.2.3 or 2.3.5
and check system info after to verify
then update.zip or flash 2.3.4 sbf
or try ezsbf to flash and/or root
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
I've tried 2.2.2, 2.3.3, and 2.3.4 all, then updated. I've tried 3 different versions of RSD. Exact same result. Haven't heard of ezsbf though, I'll check it out.
http://www.droidxforums.com/forum/droid-x2-hacks/41697-tool-ezsbf-dx2.html
it's an iso file you burn to cd or thumb drive, reboots pc to a Linux os
with options to flash sbf and root with zergrush
works for some, when rsd lite or rooting failed
Sent from my MB870 using xda premium
... Have you thought that maybe the recovery your using is corrupted? Download that apk again (the plain one not the patched cm7/9 version) and give that
Sent from my MB870 using xda app-developers app
Scur827 said:
Since the last time I flashed CM7, RSD (any version) with any SBF file doesn't wipe my phone the way it used to. It's gotten to the point I can no longer flash custom ROMs. If I don't wipe data/cache first, it will flash a new SBF yet leave the apps that were on it before hand. And when I try to flash a custom ROM, I get an error every time. Did I mess up something down in the locked areas that can never be fixed? Is there another way to wipe the phone to a more original or basic point? Right now I'm completely wiping the int and ext sd-cards, wiping data/cache/dalvik, SBFing to 2.2.2, and OTAing back up to see what happens, though I'm doubting it will help.
edit: Didn't work. Still can't flash a custom ROM. I can run rooted stock 2.3.5 though, guess that's what I'm stuck with. Better than nothing.
Click to expand...
Click to collapse
The reason why you can't flash custom ROMs such as CM7 or CM9 is that you keep going to 2.3.5 or maybe even trying on 2.2.2 or 2.3.3. I have a check to prevent you from using any version besides 2.3.4. Restoring a nandroid won't cut it either. You must SBF back to 2.3.4, wipe data/cache, root (using zergRush or Pete's Root Tools), install the unpatched BSR, and flash CM7 or CM9.
As for why your apps show up still after an SBF, like you said, you didn't wipe data/cache and the apps are stored in the data directory on your phone. An SBF does not wipe data or cache.
LordRalh3 said:
... Have you thought that maybe the recovery your using is corrupted? Download that apk again (the plain one not the patched cm7/9 version) and give that
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
That's the only thing I haven't tried I think, I'll give it a try. Good idea.
Droid X2 > Eclipse 2.2.1 > Tapatalk
dragonzkiller said:
The reason why you can't flash custom ROMs such as CM7 or CM9 is that you keep going to 2.3.5 or maybe even trying on 2.2.2 or 2.3.3. I have a check to prevent you from using any version besides 2.3.4. Restoring a nandroid won't cut it either. You must SBF back to 2.3.4, wipe data/cache, root (using zergRush or Pete's Root Tools), install the unpatched BSR, and flash CM7 or CM9.
As for why your apps show up still after an SBF, like you said, you didn't wipe data/cache and the apps are stored in the data directory on your phone. An SBF does not wipe data or cache.
Click to expand...
Click to collapse
I haven't tried to flash CM7 or CM9 since the last time I came off of it. I really like having the camcorder around my daughter. That was my only problem with either. they worked great when they were on. I've mostly been trying to get Eclipse back on.
I think that CM7 had something to do with my problem, though. I've flashed it twice before. The first time was hell coming back to stock, I thought my phone was bricked for about an hour. It took multiple boot attempts, battery pulls, and button mashing before I finally could get back to RSD mode to flash a SBF.
Everything seemed fine for a couple months, until I tried CM7 once again. When I tried to come back off of it the second time, RSD gave it a PASS at the end instead of hanging on REBOOT PHONE MANUALLY like it always did before, and has every time since then (was hit and miss before). Now I can still flash a SBF and update an OTA (but only after doing a *228 to download and install it, can't flash an OTA file from recovery), but if I try to flash any ROM (and I've tried a half dozen of them) while using any root method, I get an error while flashing, and have to wipe everything possible to be able to SBF back to stock. I've tried flashing ROMs at least 20 times over the past few days. Either something got messed up, somewhere in an area that both RSD and recovery don't touch, or it's a hardware issue. That's the only thing I can come up with.
Now, I don't believe it's CM7's fault. At all. There are just too many people who enjoy. I simply believe there was something odd or wrong about my phone.
Its like you know the words but not which ones go with what things... Flashing and sbfing are two completly different things, and there is no button mashing involved pull your battery one time, hold power and volume up at the same time, that puts you in rsd mode to sbf, to get over a bootloop just go to android recovery (power button and volume down then cycle to recovery) you don't flash roms in this recovery just wipe data/cache. If you grabbed the right sbf file (check your android version in about phone should be 2.3.4 ) you can root with motorola one click and install the bootstrap recovery program NOT THE CM7 VERSION, Plug phone into the wall bsr WIPE DATA/CACHE and flash cm7, its a standard process and your phone is not special
Sent from my MB870 using xda app-developers app
LordRalh3 said:
Its like you know the words but not which ones go with what things... Flashing and sbfing are two completly different things, and there is no button mashing involved pull your battery one time, hold power and volume up at the same time, that puts you in rsd mode to sbf, to get over a bootloop just go to android recovery (power button and volume down then cycle to recovery) you don't flash roms in this recovery just wipe data/cache. If you grabbed the right sbf file (check your android version in about phone should be 2.3.4 ) you can root with motorola one click and install the bootstrap recovery program NOT THE CM7 VERSION, Plug phone into the wall bsr WIPE DATA/CACHE and flash cm7, its a standard process and your phone is not special
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
Fine, I don't FLASH an SBF file. But I've flashed ROMs on the X2 alone at least a hundred times, I know what's what. I know the difference between stock recovery and BSR. I know the difference between BSR and the CM7 version, and when to switch over. I know what wiping data does, what wiping cache does, what the Dalvek cache is and what wiping it does, what fixing permissions really does.
When I say I couldn't SBF out of CM7, I mean after flashing CM7 the first time, I ran RSD Lite and used SBF 2.3.4-380 to get back to stock. RSD gave me an error, and stopped. I couldn't reboot the phone, it just hung up on the red M. Holding vol down+power hung up on the red M. Holding vol up+power hung up on the red M. So I would pull the battery and try it again. And again. And again. No buttons, every button. Letting it sit on the red M for 30 mins. Eventually I got a weird RSD message at the top (and no, not the vol up+power RSD message), different from the others, and I could SBF again. I still got an error, but could vol down+power into the regular menus, so once I got into the standard RSD mode the next SBF went fine, except I got a pass at the end instead of having RSD hang up on the reboot phone manually message it always got before. And since then I don't get the boot loops after it reboots like it used to, though the pass message is hit and miss. I've SBFed dozens and dozens of times since then, used fresh downloads and different versions of everything, and I've never seen another boot loop afterwards. Something, somewhere, is definitively different. I have a few good cables that have always worked, and I've switched them out. I've wiped and formatted everything possible on the phone several times. It's just not the same as it was before CM7. And after coming off of CM7 the second time, I've gotten a pass at the end of the SBF every single time. Another new thing after a CM7 flash.
Like I said, I don't think it's a CM7 issue, I just think there is something wrong with my phone on a level I can't touch, and it really didn't like CM7. It isn't operator error. Give me any instructions you like for getting me on, say, Molten (since it's 2.3.4-380 and the simplest to flash). I'll follow them to the T, but it won't work. I can't *228 anymore, so I can't download a system update, and I get a file signature error if I try to flash an update from stock recovery. I'm stuck on stock 2.2.2, 2.3.3, 2.3.4, or 2.3.5. I can still root them using any method, except 2.3.5 since it requires carrying root over with OTA Rootkeeper from 2.3.4.
Sorry if i came off too negatively btw its just that this phone is SOOOOO close to indestructible programming wise... Your next step is to burn ezsbf and head to someone elses computer and try that
Sent from my MB870 using xda app-developers app
LordRalh3 said:
Sorry if i came off too negatively btw its just that this phone is SOOOOO close to indestructible programming wise... Your next step is to burn ezsbf and head to someone elses computer and try that
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
Me too, just woke up.
I tried ezsbf yesterday on a laptop, no change. Tried a fresh copy of BSR from a different source this morning, no luck there either. I'm completely out of ideas now, there's nothing I haven't tried alternatives to. But I have a fully functional phone rooted on 2.3.4, and sometime in the near future I'll be getting something new and shiny, so it could be worse. When I do get a new one, this one will be perfect to have GrooVe IP on it for my 8 yr. old daughter, and the big screen is nice for games.
Droid X2 > Eclipse 2.2.1 > Tapatalk
Scur, I uploaded a nandroid of eclipse 2.3
don't know if that will work any better
but who knows, it just might work for you
http://www.mediafire.com/?7b71gn1j3r2dwrj
edit: if you problem is kernel related, it's not going help
also have you been checking the kernel,
System version:
1.3.418
Android version:
2.3.5
Baseband version:
N_03.13.31P
Kernel version:
[email protected]#2
sd_shadow said:
Scur, I uploaded a nandroid of eclipse 2.3
don't know if that will work any better
but who knows, it just might work for you
http://www.mediafire.com/?7b71gn1j3r2dwrj
edit: if you problem is kernel related, it's not going help
also have you been checking the kernel,
System version:
1.3.418
Android version:
2.3.5
Baseband version:
N_03.13.31P
Kernel version:
[email protected]#2
Click to expand...
Click to collapse
Here's where I am now. With a method to root 2.3.5, I can SBF it and root. It will let me flash Eclipse 2.3, but will lose root when it flashes. So I can get Eclipse 2.3, but it's unrooted and I haven't found a way to root it after flashing yet. Odd there. I have a couple abd tips to try to get it going, but I'm going to try your nandroid first. Much thanks.
Droid X2 > Rooted 2.3.5 > Tapatalk
The nandroid worked like a charm, I thank you good sir.
Droid X2 > Eclipse 2.3 > Tapatalk