I had Drew Garen's Broodcomb v3 running for awhile, but I wanted to return to stock to see if I had gotten the Gingy OTA yet. SBF'd back to .340 just fine. Found I hadn't gotten the update yet, so I went about going back to Broodcomb....except it won't work. I root with z4, bootstrap, then install the .595 from the Drew Garen site so I can then flash Broodcomb....but it never gets past the boot logo. I so the usual, format data/system, battery pulls, reflash.....and nothing has worked so far. Anyone have any ideas?
Just throwing this out there, but did you try using the stock recovery function to wipe user data and cache? Power off the phone, then hold down power and home until the andriod guy pops up with an exclamation point and then hitting search.
If that fails too then you might just want to SBF the phone back to the out of the box .340 build and try it again. I know on mine I've been having some strange things popping up with flashing ever since I started playing with the OTA release, but this doesn't look like the case for you somehow. Hmm...
I just gave up trying...went to try another of Drew's. Turns out, the .595 leak on his site was the problem. I got the 2 part zip file from Team Black Hat, and that did the job. Only now, I have another issue that came up when I didn't like another of Drew's roms....not I have a corrupt bootloader....YAAAAAAY!!! Time for more research
Related
Am stuck on The Rubix Logo. I was on Rubix 1.89 then I was messing around w/phone a lil bit so I decided to load the stock rom back. It loaded up fine. I attempted to load Rubix 1.93 and decided not to wipe (Stupid mistake) and now am stuck on Rubix boot loop. Can someone assist me in loading into Recovery when DX is powered off please. I hope no one mentions SBF. I have no clue how to even begin that process
Been in a similar situation. I assume we're talking about getting into clockwork recovery?
If that's the case, your only solution is an sbf if it isn't kicking you into clockwork already.
Getting into stock recovery is achieved by holding down the home and power buttons from power off.
SBFing is done from the bootloader. that is entered from power off by holding down power, volume down, and the camera button.
You will need the 2.2 sbf file and RSD lite 4.8 on your windows machine in order to perform sbf.
Yes You assumed right about CW, I knew it wouldn't be long before I Fd this up. I already have RSd lite 4.8(I think...have to double check). Where can I get this SBF 2.2 file from? I've looked all over but most links are dead This really Sucks..
Couldn't I just load the Leaked 2.3.320 file instead of the 2.3.15, since I wanted to do the upgrade anyway? or is it just not that Easy?
The 2.3.320 is just a system sbf. I think there were kernel changes that went with that you'll have to have. Standby for PM.
im in need of that 2.3.320 too i have a sitting brick that will not do recovery but can flash with a sbf
Not sure what your situation is but I posted some help over at DF as well and my issue has been resolved by Seph and these instructions I followed. Hope it works for you as well and fyi here's link(http://www.droidforums.net/forum/drod2169-x/99143-rubix-focused-1-8-9-1-9-3-a-34.html#post1021218)
First thing to try, is to wipe data and cache from the android recovery (NOT clockwork recovery.. as.. most liklely you can't get to clockwork recovery.
Easiest way:
--Battery Pull
--When you put the battery back in, hold down the home button the phone.
--As it powers up, let go of the home button when you see the M logo.
--It should go into android recovery. When you see the little droid with the ! in a triangle, hit the search button.
--From the menu, wipe data and cache, then reboot.. it should take you into Focused...
When you get back in.. the FIRST thing I suggest, is to reload 1.8.9.. as it sounds like you do not have the TBH leak (If you don't have it, you probably don't want it)...
PLEASE read the first post, that talks about the differences between 1.8.9, and 1.9.3...
Since you will have already wiped data and cache, you shouldn't need to when loading 1.8.9.. if you have troubles with loading it, just wipe data/cache again...
I wish I had come here first!!!! Been trying to get ROM Manager to work and finally got all excited because it seemed as though it had finally taken, well, now I am stuck in a the Rubix boot loop as well. I've wiped my cache as mentioned about but not data yet. My only option for that is to wipe data is to wipe data/ factory reset. Is it safe to do that since I am rooted? I was running OTA 2.2 rooted.
I am in sbf with rsd lite and can not get it to do anything after loading the file for sbf on my X. It recognizes it but the radio button for the start will not do anything.
rcnaimee826 said:
I wish I had come here first!!!! Been trying to get ROM Manager to work and finally got all excited because it seemed as though it had finally taken, well, now I am stuck in a the Rubix boot loop as well. I've wiped my cache as mentioned about but not data yet. My only option for that is to wipe data is to wipe data/ factory reset. Is it safe to do that since I am rooted? I was running OTA 2.2 rooted.
Click to expand...
Click to collapse
Someone please PM me and tell me what I am doing wrong!!!!
So I decided to give Tranquility a test and see how it compares to my currently running ApeX. I followed the usual procedures, data wipe/factory reset.....twice.
then installed TranQ and the TranQ App update.
The phone then boots up and freezes on the animation screen. So i reset it, then it won't boot at all past the Logo screen. Randomly it decides to boot up fine, but then 30 seconds of android and it reboots and freezes up.
So for some reason it won't let me boot into clockwork recovery, so i decide to just do the system only SBF it and be done.
So I've SBF'd it twice now, the first time it did a random restart and froze, and also kept the tranq boot animation. I did the 2nd sbf and it's got rid of the animation screen and back to droid, however the tranq boot logo is there.
I haven't proceeded to reactivate the phone yet, and just leaving it alone it hasn't restarted itself. I'm planning on rerooting and reinstalling clockwork recovery and see if i can get one of my old backups going.
But, any theories to what would have jacked it up so bad? and why the stock moto logo wasn't put back when SBF'ing?
update:
rerooted just fine using Z4, installed clockwork recovery just fine too.
Right now I'm doing a data wipe and reinstalling ApeX 1.3.1 from scratch from clockwork recovery. Then I'm gonna restore one of my backups.
Hopefully all goes well
update:
recovered to my backup just fine. Still didn't get rid of the tranq boot logo, thankfully i had a zip stored away of the stock logo so I installed that.
All is now well in the world.
Lesson from this......if it's working fine, leave yo sht alone!
Logo is stored in different place then a system sbf will update. That's not tranQ 's fault. I still use gummyJar though. Too much blur in TranQ for me
I had the exact same problem when I went from fission to tran q. I literally had to do the. 320 sbf then the. 340 sbf to get tran q to install right. Didn't like it and put fission back on
yea i had to do the same thing comming from fission, and because of it i am just staying on tranquility until Obsidian is more stable, then GOODBYE BLUR :-D
The trick to installing TranQ is to install it over stock. If you try to install it over another custom ROM you will have nothing but problems.
Sent from my DROIDX using XDA App
davidukfl said:
Lesson from this......if it's working fine, leave yo sht alone!
Click to expand...
Click to collapse
I feel your pain, but you shouldn't be discouraged (as long as you Nandroid, Nandroid, Nandroid!).
I also spent a week fiddling with TranQ before giving up due to random reboots. But I went ahead and installed GummyJar. It was worth it!
When you're ready to climb back onto the horse, you should try GummyJar. If you prefer a no-bur ROM, it's probably the best in terms of speed and stability.
well i had tried Gummy before, but it was a little buggy for me. Phone would restart after calls, hardware buttons wouldn't always work and a few other little things.
I actually just switched to Fission and it's pretty brilliant thus far. No problems at all, and the fission manager helps a lot
fmkaiba said:
Logo is stored in different place then a system sbf will update. That's not tranQ 's fault. I still use gummyJar though. Too much blur in TranQ for me
Click to expand...
Click to collapse
IT IS TranQ's fault. It is the only ROM that does this. Before you get rid of Tranq, you have to go in to the tools and set your boot logo back to stock. I have flashed many different ROMs and it is the ONLY ONE that makes sure to "leave its mark," LITERALLY.
had same problem when I went from fission. I had to sbf .32 then sbf .34 then did the tran q and it worked just fine after that. I didn't like it to much so I went back to fission. To get rid of the tran q I just did the same sbf method I did and went back to fission.
z06mike said:
IT IS TranQ's fault. It is the only ROM that does this. Before you get rid of Tranq, you have to go in to the tools and set your boot logo back to stock. I have flashed many different ROMs and it is the ONLY ONE that makes sure to "leave its mark," LITERALLY.
Click to expand...
Click to collapse
You're right on w/this..Its too bad I found out the hard way..
Ok guys, I have a good one for you. Tuesday I SBF'd my phone from my version of the .340 build to the factory VRZ_MB810_2.3.34_1FF_01 build that's on here. Reasoning was that I wanted to play with the OTA update to 2.3 and I was rooted and running Rubix 2.0 on it at the time.
That went fine and the OTA went without a hitch as well.
Now comes the fun part. Being the tinkerer that I am, I decided that I couldn't live without root access so I decided today that I would just SBF back to the VRZ_MB810_2.3.34_1FF_01 build and I was going to flash P3Droid's rooted GB release.
So I ran RSD, located my sbf file just I like I had, put the phone into bootloader (30.04 didn't change with the update) Let th SBF do it's work and now I'm bootlooping...
I wondered if this was just a Windows issue because I had to SBF a few times the other day just to get it to work. With that in mind, I exited my Windows virtual machine and tried it on my Linux box but to no avail.
I'm running out of options here...
Ideas?
Laramie1997 said:
Ok guys, I have a good one for you. Tuesday I SBF'd my phone from my version of the .340 build to the factory VRZ_MB810_2.3.34_1FF_01 build that's on here. Reasoning was that I wanted to play with the OTA update to 2.3 and I was rooted and running Rubix 2.0 on it at the time.
That went fine and the OTA went without a hitch as well.
Now comes the fun part. Being the tinkerer that I am, I decided that I couldn't live without root access so I decided today that I would just SBF back to the VRZ_MB810_2.3.34_1FF_01 build and I was going to flash P3Droid's rooted GB release.
So I ran RSD, located my sbf file just I like I had, put the phone into bootloader (30.04 didn't change with the update) Let th SBF do it's work and now I'm bootlooping...
I wondered if this was just a Windows issue because I had to SBF a few times the other day just to get it to work. With that in mind, I exited my Windows virtual machine and tried it on my Linux box but to no avail.
I'm running out of options here...
Ideas?
Click to expand...
Click to collapse
Boot into stock recovery and do a factory reset...
Sent from my DROIDX using XDA App
Nope, can't do that. There isn't a recovery to go back to. I don't have clockworks on this phone anymore.
Laramie1997 said:
Nope, can't do that. There isn't a recovery to go back to. I don't have clockworks on this phone anymore.
Click to expand...
Click to collapse
Its stock recovery...power off phone and then hold power and home button until you get the Android with the exclamation point. Then hit the search button
Sent from my DROIDX using XDA App
That wasn't quite what I was looking for since I don't have /sdcard/update.zip still on the card anymore. What IT DID allow me to get in and do was wipe cache which allowed a clean SBF.
THANKS!
Since I installed Aura 1.2.1.0 on my phone the power button has been getting really hot. I just installed Homebase v5 and its still the same thing. So im thinking its not the rom. Any ideas?
That's odd. The bottom of my phone gets hot, but not the power button. If you're on att or even if youre not, I suggest trying to get a warranty replacement.
Sent from my Unlocked CM7 Atrix
http://forum.xda-developers.com/showthread.php?t=1268698&highlight=fingerprint+scanner+hot
someone here said they fixed it by doing a factory reset; i suggest wiping EVERYTHING through fastboot, then clearing data/cache/dalvik in CWM and then reinstalling a stock ROM (fruitcake for example)
I did a clear data, cache, and dalvik wipe. What would be the difference in doing a fastboot wipe?
replace it
replace it b4 your warranty is out. my power button failed. and to many of these scripts require the power button to select options
Odd this happened to a homebase mega build I set my old man up with just last week did a back factory wipe then restored data and no problems so far, I though he left it in the car or sun or something when he said it was the finger print/power button. Even sat down and checked it out couldn't reproduce the problem or guess what happened no fp profile was even set active so. As mentioned above when in doubt replace they just upped the insure deductable x.x the 1st of this month
I got this once
removed the battery and reboot the device .. problem solved
I've rebooted, pulled the battery, got it working off the power cable (doesn't get hot then). Theres a warrant service place by work so ill revert it back to stock and just get it replaced.
I've had random moments when the phone felt like it was heating up towards the bottom, especially using the HKTW 2.3.4 build, but never on the power switch. I'd suggest just get a warranty exchange to be on the safe side. Better replace it now than when your warranty is over.
I know im gonna get flamed but how do I go back to the stock rom? Do I flash fruitycakes or sbf? I've read the threads on reverting back but their didn't seem to be any consistency.
riotburn said:
I know im gonna get flamed but how do I go back to the stock rom? Do I flash fruitycakes or sbf? I've read the threads on reverting back but their didn't seem to be any consistency.
Click to expand...
Click to collapse
fruit cake is the safest way to go back to stock. you can also flash the 2.3.4 gingerbread sbf file with rsd lite, but do NOT attempt to flash back to Froyo if you ever did the Gingerbread OTA update. if you're not sure, then just be safe and never revert back to Froyo.
flashing the gingerbread sbf file with remove your unlocked text on bootloader and revert you to a pure stock state.
So I took it to the warranty repair center and they replaced it no problem. Said shes seen it happen a few times already.
So I think I've royally F'd my DX. I was going to try rooting and flashing a new rom. I'm not a total noob (rooted gtab, nook color, Le Pan) but this is ****ing me up.
It was running 2.3.3 605 originally. I started out with just root, that seemed fine. I got superuser and busybox installed without a problem. I install clockwockmod and dx bootstrap. I was even able to get CWM 5.0.2 or whatever installed without any trouble like I had read.
I tried reading and following threads but I couldn't fallow on if I was missing steps. I have zero experience with rooting via scripts and I have no intention to learn and would rather go back to stock.
I immediately got problems with rebooting. It would not reboot via the power button. It would go to the Red M then just black screen. But it would boot just fine if I pulled out the battery and tried that way.
I did a factory reset thinking that would help, it didn't. I was still rooted but the problems got worse. Now I boot directly into CWM recovery and have to reboot from in there to get to the OS.
I read some more, thought I had figured more out. Installed Rom manger, installed Liberty3. I'm still booting straight into recovery but when I reboot from there I'm stuck at the spinning Liberty logo.
I need help, I've read and searched, if you want to be a **** have run. But I need my phone fixed. Hold my hand like I'm Hellen Keller and help please.
I would recommend reading the Droid X wiki at the Cyanogenmod website. I had some of the same issues until I followed the downgrade + root method and then installed ROM Manager and CM7 manually through recovery. Good luck!
Sent from my DROIDX using XDA App
Schwazilla said:
So I think I've royally F'd my DX. I was going to try rooting and flashing a new rom. I'm not a total noob (rooted gtab, nook color, Le Pan) but this is ****ing me up.
It was running 2.3.3 605 originally. I started out with just root, that seemed fine. I got superuser and busybox installed without a problem. I install clockwockmod and dx bootstrap. I was even able to get CWM 5.0.2 or whatever installed without any trouble like I had read.
I tried reading and following threads but I couldn't fallow on if I was missing steps. I have zero experience with rooting via scripts and I have no intention to learn and would rather go back to stock.
I immediately got problems with rebooting. It would not reboot via the power button. It would go to the Red M then just black screen. But it would boot just fine if I pulled out the battery and tried that way.
I did a factory reset thinking that would help, it didn't. I was still rooted but the problems got worse. Now I boot directly into CWM recovery and have to reboot from in there to get to the OS.
I read some more, thought I had figured more out. Installed Rom manger, installed Liberty3. I'm still booting straight into recovery but when I reboot from there I'm stuck at the spinning Liberty logo.
I need help, I've read and searched, if you want to be a **** have run. But I need my phone fixed. Hold my hand like I'm Hellen Keller and help please.
Click to expand...
Click to collapse
Don't use ROM manager and don't use dxbootstrap (unless you have usb debugging unchecked). I use d2 bootstrap always. And you will have the occasion of it going in to cwm when you boot phone back up. I dealt with it for while. And cwm should be 2502 or something like that when you're just rooted 605. Did you make a nandroid of your rooted 605 before you tried to flash liberty
? Hopefully you did. Go back to that. Then use d2 bootstrap to get in to recovery, wipe data, cache and dalvik, then select install ip from sd card, then choose zip, then scroll via volume down to the liberty file, select that and flash.
I used directions posted over at Androidforums.com under the All Things Root forum for the Dx. I had a couple of hiccups, but it was user error. I now have Liberty 3 running smoothly on my Dx. Check it out, including the guide and ROM lists.
HTH
chaz_
Schwazilla said:
So I think I've royally F'd my DX. I was going to try rooting and flashing a new rom. I'm not a total noob (rooted gtab, nook color, Le Pan) but this is ****ing me up.
It was running 2.3.3 605 originally. I started out with just root, that seemed fine. I got superuser and busybox installed without a problem. I install clockwockmod and dx bootstrap. I was even able to get CWM 5.0.2 or whatever installed without any trouble like I had read.
I tried reading and following threads but I couldn't fallow on if I was missing steps. I have zero experience with rooting via scripts and I have no intention to learn and would rather go back to stock.
I immediately got problems with rebooting. It would not reboot via the power button. It would go to the Red M then just black screen. But it would boot just fine if I pulled out the battery and tried that way.
I did a factory reset thinking that would help, it didn't. I was still rooted but the problems got worse. Now I boot directly into CWM recovery and have to reboot from in there to get to the OS.
I read some more, thought I had figured more out. Installed Rom manger, installed Liberty3. I'm still booting straight into recovery but when I reboot from there I'm stuck at the spinning Liberty logo.
I need help, I've read and searched, if you want to be a **** have run. But I need my phone fixed. Hold my hand like I'm Hellen Keller and help please.
Click to expand...
Click to collapse
Just re-flash ur phone dude. do you know how to do that? It's a pain in the butt. but it is always failsafe.