Downgrade to 902 - No app or data loss

[grgguy]

I've been off the grid.for a couple of days and can't find the. 244 thread. I see we have a new leak. What did I miss ?

 

[maaybraak]

New build leaked...246. I'm waiting on SamuriHL to get back from vacation before I even think about it. They closed down the .244 thread for now.

Sent from my Jelly Beaned-Up ASUS Transformer Pad TF300T

 

[DroidST]

No need to FXZ back to 905 to take a new ICS update. So when the OTA is released and you're ready to move on from 232, the HoB will get an update and you'll be good to go from 232. (902 is out of the picture 100% now that we have the 905 FXZ....never go back to that again! ) If you want to go back to 905, you can from 232, but, I do NOT recommend it while keeping data. ICS data in GB is a bad bad combination. If you're happy on 232, sit tight and when the OTA update is released, I'll make sure it's supported and you'll be able to move directly to it from 232.

I'm still sitting on 232


If you remember (probably no ), I had two errors, I believe because there wasn't enough pause in the script at that time... so mbmloader and cdt.bin failed.. do you think this will be a problem going forward?

I did get two FAILED for mbmloader and cdt.bin (see output below)... assuming from THIS POST and next one, I can ignore these two failures, Correct?

I just ran the script on a never rooted Bionic.. always OTA except I went from OTA 905 to ICS 230 straight..

Used SamuriHL's scripted (updated by dfib for ICS 232 linked above), took about 45 minutes.. all seems well..

I did get two FAILED for mbmloader and cdt.bin (see output below)... assuming from THIS POST and next one, I can ignore these two failures, Correct?

What is mbmloader and cdt.bin used for?



Many thanks to SamuriHL, dfib and all others involved here..

Flashing 902 now...
* Fastboot flashing needed partitions...This will take about 5-10 minutes
< waiting for device >
        sending 'mbm' (256 KB)... OKAY [  0.035s]
                 writing 'mbm'... OKAY [  0.810s]
     rebooting into bootloader... OKAY [  0.275s]
   sending 'mbmloader' (40 KB)... FAILED (command write failed (No such file or
directory))
< waiting for device >
        sending 'mbm' (256 KB)... OKAY [  0.035s]
                 writing 'mbm'... OKAY [  0.500s]
     rebooting into bootloader... OKAY [  0.275s]
     sending 'cdt.bin' (16 KB)... FAILED (command write failed (No such file or
directory))
< waiting for device >
   sending 'logo.bin' (854 KB)... OKAY [  0.105s]
            writing 'logo.bin'... OKAY [  0.665s]
         sending 'ebr' (16 KB)... OKAY [  0.275s]
                 writing 'ebr'... OKAY [  0.455s]
         sending 'mbr' (16 KB)... OKAY [  0.240s]
                 writing 'mbr'... OKAY [  0.720s]
    sending 'devtree' (512 KB)... OKAY [  0.255s]
             writing 'devtree'... OKAY [  0.505s]
  sending 'system' (262144 KB)... OKAY [ 28.874s]
              writing 'system'... OKAY [ 15.617s]
  sending 'system' (229120 KB)... OKAY [ 25.213s]
              writing 'system'... OKAY [ 11.931s]
      sending 'boot' (8192 KB)... OKAY [  0.940s]
                writing 'boot'... OKAY [  0.875s]
  sending 'recovery' (9216 KB)... OKAY [  1.111s]
            writing 'recovery'... OKAY [  1.340s]
    sending 'cdrom' (12032 KB)... OKAY [  1.365s]
               writing 'cdrom'... OKAY [  1.865s]
sending 'preinstall' (262144 KB)... OKAY [ 29.293s]
          writing 'preinstall'... OKAY [ 14.926s]
sending 'preinstall' (49152 KB)... OKAY [  5.476s]
          writing 'preinstall'... OKAY [  2.610s]
  sending 'webtop' (262144 KB)... OKAY [ 29.414s]
              writing 'webtop'... OKAY [ 16.887s]
  sending 'webtop' (262144 KB)... OKAY [ 28.282s]
              writing 'webtop'... OKAY [ 13.562s]
  sending 'webtop' (262144 KB)... OKAY [ 29.258s]
              writing 'webtop'... OKAY [ 13.562s]
  sending 'webtop' (262144 KB)... OKAY [ 29.418s]
              writing 'webtop'... OKAY [ 13.547s]
  sending 'webtop' (262144 KB)... OKAY [ 29.253s]
              writing 'webtop'... OKAY [ 13.597s]
   sending 'webtop' (54016 KB)... OKAY [  6.055s]
              writing 'webtop'... OKAY [  3.246s]
Press any key to continue . . .

The added pauses weren't needed for me. I only added them for those with those REALLY slow ass machines that need a little extra time to board the plane. HEHEHEHE And yes, those files are there for me, too. No idea what they are.

I don't think it's slow machines, I've got top notch laptop.. I think during the process there was something the motorola driver install was doing/needed to configure for adb, the popup happened right at mbmloader.. I think I was was to redo the process I wouldn't have the issue since the driver installation is complete.. I had rebooted a couple times before even running the script for the usb driver installation..

 

[twinkyz1979]

Have you ever seen a change log posted? You want the truth? It's identical to 244. In every way except the build number.

Sent from my Xoom using Tapatalk 2

Not so they fixed at least 1 problem i know of with 246 the using keyboard while charging issue or so i have read on other forums.

 

[Mike.757]

That has been a minor problem for me. I hope you are right!

 

[MichaelD]

I Installed
- Motorola USB & PC Charting Drivers [ Reboot ]
- House of Bionic 6.7
- HouseOfBionic Components 1.0
- HouseOfBionic 232 [ Reboot ]

I was starting with stock 905 & trying to move to 232.
I put the phone into USB Debug mode, plugged the USB cable in, then set to PC Charge Only.
I ran HoB & picked menu options 1 (Install 232) from 1st menu and 1, 2, 3, and 4 from the second menu.

The default power-on sequence for my phone is to go into FastBoot Flash Failure mode.

I am able to boot the phone by double-volume during power-on and select Normal Boot, but would like the phone to always boot to ICS, not fast boot flash failure screen.

At this point, do I need to "Repair AP Fastboot Error" or "Reinstall 232"?
...or heaven forbid FXZ to 905?

I did read that "Reinstall" is for when you can't boot your phone...but I can...its just not the default boot sequence, thus why I'm a bit confused about which one of the recovery options I need to use.
Yes, I've ready the FAQ page & didn't see anything explicitly about "Flash Failure".

As far as the RSDLite process, I was thinking that ran a bit quicker than the time estimate given in the script...and I am seeing an error in the below logs:

Here is the SWDL file:
09/23/12 00:26:47 --------------------------------------------------------------------------------
09/23/12 00:26:47 New Log Started For Software Download.
09/23/12 00:26:48 The FlashLog key is turned off.
09/23/12 00:26:51 00000f7c Phone.cpp 518 0 ERROR Generic failure when sending command.
09/23/12 00:26:51 00000f7c Phone.cpp 1754 0 ERROR GetTechnology failed: ERROR.
09/23/12 00:26:51 00000f7c Phone.cpp 518 0 ERROR Generic failure when sending command.
09/23/12 00:26:51 00000f7c Phone.cpp 1754 0 ERROR GetTechnology failed: ERROR.
09/23/12 00:26:51 00000f7c Phone.cpp 518 0 ERROR Generic failure when sending command.
09/23/12 00:26:51 00000f7c Phone.cpp 1754 0 ERROR GetTechnology failed: ERROR.
09/23/12 00:26:51 00000f7c Phone.cpp 518 0 ERROR Generic failure when sending command.
09/23/12 00:26:51 00000f7c Phone.cpp 1823 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
09/23/12 00:26:51 00000f7c Phone.cpp 518 0 ERROR Generic failure when sending command.
09/23/12 00:26:51 00000f7c Phone.cpp 1981 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
09/23/12 00:26:51 00000f7c Phone.cpp 518 0 ERROR Generic failure when sending command.
09/23/12 00:26:51 00000f7c Phone.cpp 1951 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.
09/23/12 00:26:51 00000f7c Phone.cpp 518 0 ERROR Generic failure when sending command.
09/23/12 00:26:51 00000f7c Phone.cpp 1870 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
09/23/12 00:26:51 Multi upgrade started for 1 phones
09/23/12 00:26:51 [Device ID: 0] 1/6 flash system "system.img"
09/23/12 00:28:46 [Device ID: 0] 2/6 flash boot "boot.img"
09/23/12 00:28:48 ERROR: 2/6 flash boot "boot.img" -> Phone returned FAIL. - on device ID 0.
09/23/12 00:28:48 [Device ID: 0] 2/6 flash boot "boot.img" -> Phone returned FAIL.
09/23/12 00:28:48 ERROR: Failed flashing process. - on device ID 0.
09/23/12 00:28:48 Multi upgrade finished.

 

[Aldroid33]

Did you read the last 4 or 5 pages of this forum? Samuri is on vacation! Nobody should have tried to use HoB unless they really knew how to use it correctly because your main source of support is unavailable. I would recommend FXZ'ing back to 905 and waiting for Samuri to return before you brick your phone. Sorry!

In the meantime check settings/about phone an see if you are in 232 or still in 905. Also check to see if you are rooted. If you are in 232 and rooted, you could try: Repair 232/ Repair Fastboot Failure.

But the better option is to just fxz back to 905, load your backup data, you did read the op and backed everything up first! Then wait for Samuri to return from vacation before trying Hob again.

 

[sargentmajord]

I Installed
- Motorola USB & PC Charting Drivers [ Reboot ]
- House of Bionic 6.7
- HouseOfBionic Components 1.0
- HouseOfBionic 232 [ Reboot ]

I was starting with stock 905 & trying to move to 232.
I put the phone into USB Debug mode, plugged the USB cable in, then set to PC Charge Only.
I ran HoB & picked menu options 1 (Install 232) from 1st menu and 1, 2, 3, and 4 from the second menu.

The default power-on sequence for my phone is to go into FastBoot Flash Failure mode.

I am able to boot the phone by double-volume during power-on and select Normal Boot, but would like the phone to always boot to ICS, not fast boot flash failure screen.

At this point, do I need to "Repair AP Fastboot Error" or "Reinstall 232"?
...or heaven forbid FXZ to 905?

I did read that "Reinstall" is for when you can't boot your phone...but I can...its just not the default boot sequence, thus why I'm a bit confused about which one of the recovery options I need to use.
Yes, I've ready the FAQ page & didn't see anything explicitly about "Flash Failure".

As far as the RSDLite process, I was thinking that ran a bit quicker than the time estimate given in the script...and I am seeing an error in the below logs:

Here is the SWDL file:
09/23/12 00:26:47 --------------------------------------------------------------------------------
09/23/12 00:26:47 New Log Started For Software Download.
09/23/12 00:26:48 The FlashLog key is turned off.
09/23/12 00:26:51 00000f7c Phone.cpp 518 0 ERROR Generic failure when sending command.
09/23/12 00:26:51 00000f7c Phone.cpp 1754 0 ERROR GetTechnology failed: ERROR.
09/23/12 00:26:51 00000f7c Phone.cpp 518 0 ERROR Generic failure when sending command.
09/23/12 00:26:51 00000f7c Phone.cpp 1754 0 ERROR GetTechnology failed: ERROR.
09/23/12 00:26:51 00000f7c Phone.cpp 518 0 ERROR Generic failure when sending command.
09/23/12 00:26:51 00000f7c Phone.cpp 1754 0 ERROR GetTechnology failed: ERROR.
09/23/12 00:26:51 00000f7c Phone.cpp 518 0 ERROR Generic failure when sending command.
09/23/12 00:26:51 00000f7c Phone.cpp 1823 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
09/23/12 00:26:51 00000f7c Phone.cpp 518 0 ERROR Generic failure when sending command.
09/23/12 00:26:51 00000f7c Phone.cpp 1981 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
09/23/12 00:26:51 00000f7c Phone.cpp 518 0 ERROR Generic failure when sending command.
09/23/12 00:26:51 00000f7c Phone.cpp 1951 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.
09/23/12 00:26:51 00000f7c Phone.cpp 518 0 ERROR Generic failure when sending command.
09/23/12 00:26:51 00000f7c Phone.cpp 1870 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
09/23/12 00:26:51 Multi upgrade started for 1 phones
09/23/12 00:26:51 [Device ID: 0] 1/6 flash system "system.img"
09/23/12 00:28:46 [Device ID: 0] 2/6 flash boot "boot.img"
09/23/12 00:28:48 ERROR: 2/6 flash boot "boot.img" -> Phone returned FAIL. - on device ID 0.
09/23/12 00:28:48 [Device ID: 0] 2/6 flash boot "boot.img" -> Phone returned FAIL.
09/23/12 00:28:48 ERROR: Failed flashing process. - on device ID 0.
09/23/12 00:28:48 Multi upgrade finished.

U didnt brick ur phone if u can boot by going into the recovery menu an selecting normal boot u just need a successful flash of an image file fxz back to 905 an then side load 232 by taking the update zip out of hob an putting it on ur external sd-card ur lucky its the 232 build or u would have been SOL HOB is mainly for updating to a 235+ build cuz there is not fxzing back

 

[sargentmajord]

I Installed
- Motorola USB & PC Charting Drivers [ Reboot ]
- House of Bionic 6.7
- HouseOfBionic Components 1.0
- HouseOfBionic 232 [ Reboot ]

I was starting with stock 905 & trying to move to 232.
I put the phone into USB Debug mode, plugged the USB cable in, then set to PC Charge Only.
I ran HoB & picked menu options 1 (Install 232) from 1st menu and 1, 2, 3, and 4 from the second menu.

The default power-on sequence for my phone is to go into FastBoot Flash Failure mode.

I am able to boot the phone by double-volume during power-on and select Normal Boot, but would like the phone to always boot to ICS, not fast boot flash failure screen.

At this point, do I need to "Repair AP Fastboot Error" or "Reinstall 232"?
...or heaven forbid FXZ to 905?

I did read that "Reinstall" is for when you can't boot your phone...but I can...its just not the default boot sequence, thus why I'm a bit confused about which one of the recovery options I need to use.
Yes, I've ready the FAQ page & didn't see anything explicitly about "Flash Failure".

As far as the RSDLite process, I was thinking that ran a bit quicker than the time estimate given in the script...and I am seeing an error in the below logs:

Here is the SWDL file:
09/23/12 00:26:47 --------------------------------------------------------------------------------
09/23/12 00:26:47 New Log Started For Software Download.
09/23/12 00:26:48 The FlashLog key is turned off.
09/23/12 00:26:51 00000f7c Phone.cpp 518 0 ERROR Generic failure when sending command.
09/23/12 00:26:51 00000f7c Phone.cpp 1754 0 ERROR GetTechnology failed: ERROR.
09/23/12 00:26:51 00000f7c Phone.cpp 518 0 ERROR Generic failure when sending command.
09/23/12 00:26:51 00000f7c Phone.cpp 1754 0 ERROR GetTechnology failed: ERROR.
09/23/12 00:26:51 00000f7c Phone.cpp 518 0 ERROR Generic failure when sending command.
09/23/12 00:26:51 00000f7c Phone.cpp 1754 0 ERROR GetTechnology failed: ERROR.
09/23/12 00:26:51 00000f7c Phone.cpp 518 0 ERROR Generic failure when sending command.
09/23/12 00:26:51 00000f7c Phone.cpp 1823 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
09/23/12 00:26:51 00000f7c Phone.cpp 518 0 ERROR Generic failure when sending command.
09/23/12 00:26:51 00000f7c Phone.cpp 1981 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
09/23/12 00:26:51 00000f7c Phone.cpp 518 0 ERROR Generic failure when sending command.
09/23/12 00:26:51 00000f7c Phone.cpp 1951 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.
09/23/12 00:26:51 00000f7c Phone.cpp 518 0 ERROR Generic failure when sending command.
09/23/12 00:26:51 00000f7c Phone.cpp 1870 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
09/23/12 00:26:51 Multi upgrade started for 1 phones
09/23/12 00:26:51 [Device ID: 0] 1/6 flash system "system.img"
09/23/12 00:28:46 [Device ID: 0] 2/6 flash boot "boot.img"
09/23/12 00:28:48 ERROR: 2/6 flash boot "boot.img" -> Phone returned FAIL. - on device ID 0.
09/23/12 00:28:48 [Device ID: 0] 2/6 flash boot "boot.img" -> Phone returned FAIL.
09/23/12 00:28:48 ERROR: Failed flashing process. - on device ID 0.
09/23/12 00:28:48 Multi upgrade finished.

The only img file that failed to flash by looking at the error log is the boot img it looks like u try to do an upgrade from a 235+ instead of a 905

 

[SamuriHL]

No sargentmajord I made it do that for all installs. They simply need to do a repair fastboot error. I'm out. Stop screwing up phones whole I'm gone!

Sent from my Xoom using Tapatalk 2

 

[sargentmajord]

No sargentmajord I made it do that for all installs. They simply need to do a repair fastboot error. I'm out. Stop screwing up phones whole I'm gone!

Sent from my Xoom using Tapatalk 2

Lmao omg samuri i got everyone an there neighbor on my thread (newbs) asking how to fxz back thanks for dumping ur sh/t pile on me xD but ok an i dont use HOB i do my own mad scientist method to move between builds

 

[MichaelD]

The only img file that failed to flash by looking at the error log is the boot img it looks like u try to do an upgrade from a 235+ instead of a 905

Prior to last night, the only updates I've ever given my phone where the ones that VZW pushed to me OTA. Before starting, I did check & I was on 905. While I did grab the 244 installer from the Internet (1st page of thread), I did NOT run it (or anything that I thought to be 235+ ).

Here are the md5sums of the files in my Desktop\SamuriHL_HouseOfBionic\232 folder/directory:
e002c1650f0f73c5be8543acf1329cbc Blur_Version.5.9.905.XT875.Verizon.en.US(67232).zip
e1678ad0854cdb7d699c646fabf8454f boot.img
ac6e88ba88b880e4cc0b244e6d3f7fe9 recovery.img

Since I've got a semi-working phone (just a inconvenience to boot), I'll wait for Samuri to return from vacation to advise on corrective action.

I've seen some suggestions on the internet (not related to HoB) that suggest flashing ANY file will cause the Flash Failure error to go away.

A few other things I noticed: The md5sum of my 232\boot.img doesn't match the md5sum in the HoB's rsd_script directory.
From the logs, it looks like RSD didn't flash preinstall.img or grfs.img , so I'm really not sure of the state of how well 232 update went on.

And MD5SUMs for the stuff I downloaded:
3cfb8aab5ded24348da90fd17aebd01e SamuriHL_HouseOfBionic_(232).exe
262f48b9462e462f2e0988dd4f325c79 SamuriHL_HouseOfBionic_(244).exe (I did *NOT* execute this)
4a12bc838861a6f0ebc4e8a5ed2ef86b SamuriHL_HouseOfBionic_(6.7).exe
54b9dbfd9ea56f55261644fd3c3b7240 SamuriHL_HouseOfBionic_COMPONENTS_(1.0).exe

 

[Aldroid33]

You could try repair fastboot error in the repair 232 menu, that's reccomended by the man, otherwise wait for Samuri

 

[sargentmajord]

You could try repair fastboot error in the repair 232 menu, otherwise wait Sir Samuri

I would just fxz since it is 232 i did it yesterday also U HAVE TO USE A FULL FXZ when going back to gingerbread cuz the ICS data is still on there an it will throw ur bionic into an epileptic seizure

 

[MichaelD]

No sargentmajord I made it do that for all installs. They simply need to do a repair fastboot error. I'm out. Stop screwing up phones whole I'm gone!

Sent from my Xoom using Tapatalk 2

SamuriHL: Thanks! I did the Repair Fastboot error & my Bionic books up like normal!
It looks like that menu option flashed the cdt.bin from Blur_Version.5.9.905.XT875.Verizon.en.US(67232).zip to clear the flash error in FastBoot.
Enjoy the remainder of your vacation!