Fastboot crashes while updating with RUU

Search This thread

digitalism

Member
Oct 21, 2011
49
6
Hello all,

As the title states, I have been having the worst time trying to use the latest signed RUU for the AT&T M7:

RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe

I have attempted more than 20 times trying to get this damn thing to work, and each time fastboot crashes or I get an error 155. I am relocked, on a completely stock ROM:

RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2

I have done multiple things to get around the issue like having the phone already in fastboot when running the RUU, trying to run the RUU as admin, and even trying to run the RUU from the AndroidOS itself. I can't seem to find a .zip alternative for a command install and was maybe thinking that might work better.

Phone is CID: CWS__001, modelid: PN0712000, S-Off, HBoot 1.55, Relocked

Can anyone verify what the problem might be? This is beginning to really piss me off...

(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ****************
(bootloader) imei: ********************
(bootloader) meid: *******************
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
 

clsA

Senior Member
Aug 28, 2010
9,926
3,547
Central Florida
Hello all,

As the title states, I have been having the worst time trying to use the latest signed RUU for the AT&T M7:

RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe

I have attempted more than 20 times trying to get this damn thing to work, and each time fastboot crashes or I get an error 155. I am relocked, on a completely stock ROM:

RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2

I have done multiple things to get around the issue like having the phone already in fastboot when running the RUU, trying to run the RUU as admin, and even trying to run the RUU from the AndroidOS itself. I can't seem to find a .zip alternative for a command install and was maybe thinking that might work better.

Phone is CID: CWS__001, modelid: PN0712000, S-Off, HBoot 1.55, Relocked

Can anyone verify what the problem might be? This is beginning to really piss me off...

(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ****************
(bootloader) imei: ********************
(bootloader) meid: *******************
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Yeah that 4.4 RUU is really strange... It worked for me when it came out but I have never gotten it to work again. I just install the 3.x.502.x RUU and do the OTApkg.zip update's
 

digitalism

Member
Oct 21, 2011
49
6
Yeah that 4.4 RUU is really strange... It worked for me when it came out but I have never gotten it to work again. I just install the 3.x.502.x RUU and do the OTApkg.zip update's

Strange...but I ended up doing the same. I was hoping to find a .zip of this RUU, but have had absolutely no luck. Everything is running good now, so no troubles to speak of at the moment.

:)
 

digitalism

Member
Oct 21, 2011
49
6
Sad to say, but it seems like the AT&T section for the M7 is really lacking as far as ROM production and suitable software. I tried jumping over to the international M7 sections, SuperCID'd my phone, installed some various ROM's, all which ate up my battery much too fast for what I tend to like. So I swapped back to almost pure stock.

Any of you guys have a good recommendation as far as international M7 ROM's that use Sense 6 with decent battery conservation? I was previously on ARHD, tried out CleanROM, and a few AOSP releases. Each seemed to progressively destroyed my battery life after a few days, even restarting the phone didn't seem to fix the horrible battery consumption.
 

clsA

Senior Member
Aug 28, 2010
9,926
3,547
Central Florida
Sad to say, but it seems like the AT&T section for the M7 is really lacking as far as ROM production and suitable software. I tried jumping over to the international M7 sections, SuperCID'd my phone, installed some various ROM's, all which ate up my battery much too fast for what I tend to like. So I swapped back to almost pure stock.

Any of you guys have a good recommendation as far as international M7 ROM's that use Sense 6 with decent battery conservation? I was previously on ARHD, tried out CleanROM, and a few AOSP releases. Each seemed to progressively destroyed my battery life after a few days, even restarting the phone didn't seem to fix the horrible battery consumption.

I pretty much only use Stock Rooted with a custom kernel (ElementalX) or Insertcoin
 

Wonders_Never_Cease

Inactive Recognized Contributor
Jul 10, 2013
2,739
1,558
Um theres the rom I put out thats made from developer us build which is same as att device...battery life is good from whats been reported...
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    It happened to me as well. I couldn't complete the 4.4 RUU flashing. Instead, I had to flash the 4.3 RUU and then use the OTA package from stock recovery.