Downgrade to 902 - No app or data loss

[grgguy]

2 things. First, I'm gone for 4 days starting Thursday night, so, I can guarantee that I won't do another update to the HoB this week. Second, no update to the HoB is required to support a new leak. All you gotta do is use my naming convention...i.e. add (6724x) to the end of the filename...create a 24x directory, drop it in there, and run the HoB. It will prompt you for creating a new boot img. And when you're done rooting it, you can pull the recovery.img from your phone, as well. All the "update installers" do is add those 3 files to a 24x folder in the HoB for you.

I think we've already established that I'm not very techy with my flash comment dancedroid. That being said if a new leaks comes out while your gone I'll just wait for you to do all of the above . Thanks for your hard work and enjoy your weekend .

 

[altspeed]

Alright...I think I have figured something out. I bought the setCPU program a couple years ago when I was moding my OG Droid and Incredible. I downloaded that, and set my CPU from 1.2 to 1.0. Seems to be running much better. Haven't had a reboot in about 30 minutes of heavy use. That is a plus in my book, considering what I had before. Will continue to monitor it and see what happens. Fingers and toes crossed...

Word. This is the first "motofficial" 1.2 with problems I've seen. I forced the OC on mine because it didn't pass the stress test and it's rock solid, fortunate because when you force the OC you lose your 1000 Mhz slot and only have 300,575,800, & 1200 to work with.

 

[SamuriHL]

I think we've already established that I'm not very techy with my flash comment dancedroid. That being said if a new leaks comes out while your gone I'll just wait for you to do all of the above . Thanks for your hard work and enjoy your weekend .

I shouldn't be completely off grid while I'm gone as I'll have my bionic, xoom, and netbook with me. But I don't think I'll be able to do an update release while I'm away. Someone, however, would be able to provide a temporary zip file that people can unzip into their HoB directory to provide support for a new update. It's really MUCH simpler than it seems.

 

[Soocold]

That's why I'm so happy i got that 5th slot for 1.2

ICS Droid Bionic.

 

[refuzeandrezizt]

Well, I can confirm to all that the 1.2 was in fact my issue. I have been running it all day on 1.0 with absolutely no issues at all. On 1.2 I was lucky to get anywhere without it either freezing (resulting in a battery pull), or rebooting over and over and over and over and...well you get the point. When I get everything back to the way I like it, and have it going good for a few days, I will jack it back to 1.2 and just see what happens. May just be the fact that with the phone doing all the initial stuff, with the overclock, it just couldn't handle it all. Who knows, there is no rhyme or reason that I can see why some can run higher than others, besides the chips themselves...

 

[SamuriHL]

Well, at least you got it figured out. That's definitely good.

 

[refuzeandrezizt]

Sure is, I was ready to smash this thing early this morning. I use my phone for everything, so watching it reboot over and over was not a good thing. But I knew I could fix it one way or another, not my first go around. Now to just wait for the next leak...LMAO!

 

[Soocold]

Honestly i would try undervolting slot 4 the mV is very close between slot 4 and 5 it may be hanging up between switches. You could also change govners to something less aggressive

ICS Droid Bionic.

 

[altspeed]

Honestly i would try undervolting slot 4 the mV is very close between slot 4 and 5 it may be hanging up between switches. You could also change govners to something less aggressive

ICS Droid Bionic.

Smartassv2 is pretty amazing. Almost performance gov benchmarks, incredible battery life, very smooth.

 

[Aldroid33]

Well SamuriHL, I got myself in a mess. I am on 244 and it was running well, I decided to try AKOP CM-10 KEXEC on Bootstrap 5.2.? (from Obsidian's thread which was booting up in recovery every time and was supposed to reboot in BP Tools...felt pretty safe ) Well, I had the great idea that I should keep my data and see what happens next. Also, forgot that KEXEC is a Safestap 2.11 only ROM. But, flashed anyways and bootlooped on the AKOP boot animation. It's pretty nice. I tried to get into the Bootstrap recovery, but it kept on reebooting int the AKOP boot animation, which is still pretty nice. I tried going into BP tools and it again booted into AKOP boot animation, which I no longer like....any more. I tried to go into stock recovery and wiped Factory Reset, wiped cache, but could not get my Nandroid to flash from CWM, nor could I get to my internal memory to flash a downloaded zip file. (should have thought of that before and loaded a rom into my SD-ext.

So, I upgraded to HOb 6.1, put my phone in fastboot and tried to repair 244, however I could not finish and go int stock recovery. I am getting an invalid flash mode indication. No error messages, I just can't get to stock recovery. I tried to press "R" to repair fastboot, but that didn't work either. I read the entire op and I am stumped. Help! Please...

 

[SamuriHL]

Oh man. This may be one of the situations I was talking about where we need a real FXZ. First, let me lecture so everyone gets this damn point across to them....

FIRST RULE OF NOT GETTING BURIED IN THE HOLE YOU MAKE...STOP DIGGING.

It's nice that you tried to fix it on your own, but, in the end you may have made things worse for yourself. This is going to be a lot of work, and I can't promise you that I can dig you out of this one. UGH.

Number 1....your sdcard-ext....does it have 244 update zip on it still?

If yes, proceed. If no....STOP. Pull the sdcard, and get the update on the root of the sdcard. Then proceed.

Number 2...in the 244 directory, is there a recovery.img? If not, STOP. Install the 244 update support installer, and verify recovery.img is in there. Then proceed.

Follow my instructions to the letter and do not deviate.

o) Rename the rsd\SWDL.txt file to SWDL.txt.old
o) Put your phone in AP fastboot mode....clearly shouldn't be hard in this case. cough cough
o) Connect it to USB
o) Run the HouseOfBionic.bat
o) REINSTALL 244 option
o) Option 3....let it complete and then shut off the phone. Leave it off
o) Post me the contents of the new SWDL.txt file

We will continue after that.

 

[SamuriHL]

6.2 RELEASE


o) G****** stupid ******ing bugs....Fixed the REPAIR Fastboot Error option.

 

[SamuriHL]

Also, advanced HoB users....I'm going on vaca for a few days starting Thursday night. There is a very high chance that 244 will soak Friday afternoon. If that happens, you will see an influx of users on this thread and my droidrazr HoB thread wanting to upgrade to that build. I need a couple things...first someone needs to pull the soak build and md5 hash it against the HoB 244. If they are the same, then all that needs to be done is to help those having issues. Make them READ my OP and FAQ. But a LOT of 232 users are going to want to update without losing data. All they gotta do is install the HoB and use the INSTALL 244 option. And not skip any freaking steps.

 

[Aldroid33]

Thanks for the assurances Sam, I know I probably made it worse. I thought that I knew exactly what to do. However, I'm pretty sure that 244 is on the SD card root. The HOb checked the MD5 and confirmed it was correct. However, I am not sure how I can get to my phone's SD Card's root directory, since I am being told that I am getting a fastboot flash errror (I was not able to get back to the boot menue), so how do I check the f'n SD card? :blink: and look at the 244 recovery directory. Also, I need to change batteries, I have a few of them and a charger.:biggrin:
Big extended battery installed, still showing "Invalid Flash Mode (S) (Boot Faliure)

 

[SamuriHL]

Ok, you didn't quite fully understand what I said. I'll try again. sigh.

First, the sdcard can't be checked in the phone. I said it'd have to be pulled from the phone and checked via some other means. Another phone, and sdcard adapter, whatever. If you can't do that, well, you're going to have to go on faith that it's on there. Not recommended, but, nothing I can do anything about.

Second, I didn't ask you to look on the sdcard for the recovery.img file. I asked you to look in the SamuriHL_HouseOfBionic\244 directory. To make sure a recovery.img file is there.

I'm quite well aware you can't get anywhere beyond the fastboot issue with your phone. 6.1 did have an error in the REPAIR Fastboot error option. You may wish to update to 6.2 and try that option again to see if it repairs the fastboot error so you can get into stock recovery. It might.