8 replies to this topic

[Telstar_2112]

I posted this on another site but this appears to be a better site for a possible solution.

 

"My Bionic was rooted so I never accepted the last update back about 7 months ago but that message kept coming up to update and I accidentally hit accept the other day.
I quickly removed the battery, rebooted, but then every minute or so it would power down to apply the update.
Within one of those minutes I quickly deleted the update file from the cache folder using root explorer. Now when it rebooted, it did not try to load the update, I could see my stuff but... still re-booted every minute or so. I guess this was probably not a good idea.
Long story short I tried a lot of stuff, wiping cache, resetting to factory, using rsd lite to try and flash it with both ICS then JB but kept getting errors such as "Signature not valid" or cdt.bin errors or
"Error in tmp/sideload/pkg.zip
Tmp/bp.img
Status 7 installation aborted."

Anyway...
Eventually with deleting the lines <oem-fb-mode> from the extracted JB xml file I was able to load JB using rsd-lite and it seemed to make it through without errors. I can get to theWelcome screen for set-up but damn -within a minute.. still reboots. So I think (not positive) JB is properly loaded but it is still re-booting. I also tried loading the same xml.zip files from the sd card. "

 

I was directed to houseofmoto so I followed that procedure "succesfully" with rsd lite loading the file (started with cdma_targa_9.8.2O-72_VZW-22_cfc but not sure if HofM modified it).  So phone boots, get past the red eye and get to the Welcome screen, hit start and get Please wait this may take a few minutes message but the phone still rebots after about a minute.  ( Battery is full and I have two batteries and a seperate charger.)  

 

During that minute I quickly check the phone system and see this:

system version: 98.72.22.xt875.verizon.en.us

Android version 4.1.2

build number: 9.8.20-72_VZW-22

 

 

Any ideas how to stop the rebooting?

TIA,

Telstar.

 

[Telstar_2112]

Forgot to attached file SWDL.txt:

02/09/14 17:37:27  --------------------------------------------------------------------------------
02/09/14 17:37:27  New Log Started For Software Download.
02/09/14 17:37:27  The FlashLog key is turned off.
02/09/14 17:37:30  00001aac Phone.cpp 531 0 ERROR Generic failure when sending command.
02/09/14 17:37:30  00001aac Phone.cpp 1778 0 ERROR GetTechnology failed: ERROR.
02/09/14 17:37:30  00001aac Phone.cpp 531 0 ERROR Generic failure when sending command.
02/09/14 17:37:30  00001aac Phone.cpp 1778 0 ERROR GetTechnology failed: ERROR.
02/09/14 17:37:30  00001aac Phone.cpp 531 0 ERROR Generic failure when sending command.
02/09/14 17:37:30  00001aac Phone.cpp 1778 0 ERROR GetTechnology failed: ERROR.
02/09/14 17:37:30  00001aac Phone.cpp 531 0 ERROR Generic failure when sending command.
02/09/14 17:37:30  00001aac Phone.cpp 1847 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
02/09/14 17:37:30  00001aac Phone.cpp 531 0 ERROR Generic failure when sending command.
02/09/14 17:37:30  00001aac Phone.cpp 2005 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
02/09/14 17:37:30  00001aac Phone.cpp 531 0 ERROR Generic failure when sending command.
02/09/14 17:37:30  00001aac Phone.cpp 1975 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.
02/09/14 17:37:30  00001aac Phone.cpp 531 0 ERROR Generic failure when sending command.
02/09/14 17:37:30  00001aac Phone.cpp 1894 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
02/09/14 17:37:30  Multi upgrade started for 1 phones
02/09/14 17:37:30  [Device ID: 0] 1/22 flash mbm "allow-mbmloader-flashing-mbm.bin"
02/09/14 17:37:31  [Device ID: 0] 2/22 reboot-bootloader
02/09/14 17:37:37  [Device ID: 0] 3/22 flash mbmloader "mbmloader.bin"
02/09/14 17:37:38  [Device ID: 0] 4/22 flash mbm "mbm.bin"
02/09/14 17:37:39  [Device ID: 0] 5/22 reboot-bootloader
02/09/14 17:37:44  [Device ID: 0] 6/22 flash cdt.bin "cdt.bin"
02/09/14 17:37:44  [Device ID: 0] 7/22 reboot-bootloader
02/09/14 17:37:49  [Device ID: 0] 8/22 erase cache
02/09/14 17:37:49  [Device ID: 0] 9/22 erase userdata
02/09/14 17:37:49  [Device ID: 0] 10/22 flash lbl "lbl"
02/09/14 17:37:49  [Device ID: 0] 11/22 flash logo.bin "logo.bin"
02/09/14 17:37:51  [Device ID: 0] 12/22 flash ebr "ebr"
02/09/14 17:37:52  [Device ID: 0] 13/22 flash mbr "mbr"
02/09/14 17:37:53  [Device ID: 0] 14/22 flash devtree "device_tree.bin"
02/09/14 17:37:54  [Device ID: 0] 15/22 flash system "system.img"
02/09/14 17:39:54  [Device ID: 0] 16/22 flash boot "boot.img"
02/09/14 17:39:57  [Device ID: 0] 17/22 flash recovery "recovery.img"
02/09/14 17:40:01  [Device ID: 0] 18/22 flash cdrom "cdrom"
02/09/14 17:40:05  [Device ID: 0] 19/22 flash preinstall "preinstall.img"
02/09/14 17:41:34  [Device ID: 0] 20/22 flash emstorage "emstorage.img"
02/09/14 17:41:35  [Device ID: 0] 21/22 flash webtop "vendor.img"
02/09/14 17:46:22  [Device ID: 0] 22/22 flash radio "radio.img"
02/09/14 17:46:27  [Device ID: 0] reboot
02/09/14 17:53:39  00000b20 Phone.cpp 1571 0 ERROR Waiting for phone's handle is setted successfully after restart [430000 ms] completion. failed
02/09/14 17:53:39  [Device ID: 0] Please manually power up this phone.
 

[LDubs]

It's probably best to re-post this in the House of Moto thread, folks monitor that thread closely and can address this over there.

[SamuriHL]

It's a hardware issue.  Most likely it's trying to overlock the cpu to 1.2 and having issues.  The only way to fix it that I'm aware of is to root it and drop the speed down...assuming you can get far enough to do it.  Flashing stuff isn't going to fix this.

[Telstar_2112]

Damn. Yes very unlikely I can do all that in the condition it is in. Weird thing is that it started right after I accidentally accepted the update and then pulled the battery.

[SamuriHL]

Yea, on some phones they were a little aggressive with the overclocking.  A few phones couldn't handle it.  Yours appears to be one of them.  It's unlikely any Bionic is under warranty at this point, either.  And you can't downgrade.  So basically, you appear to be stuck.

[Telstar_2112]

If I go into the boot mode (up,Down and Power) and boot using "BP HW Diag & Boot AP" then I can get in and it does not do the rebooting. I can get into settings and set up my wifii, but the phone is blank and wants to do a Welcome /setup and gets to a point that says I need a sim card, which is in the phone but I have since gotten a new phone  it is either just not valid or more likely corrupted.  When I look at the settings, about phone, Baseband version is unknown, Network is unknown, MEID, IMEA, ICCID, PRL, MIN, phone number are all UNKNOWN.

 

Any ideas?  Do I need to re-activate the phone and get a new sim card to continue trying to fix this.

 

If I go back to regular boot mode I still get the rebooting.  Can anyone tell me what is the differnce is in this boot mode?

[chrisp6825]

Well, if Sam's hunch about the phone having an issue with the new clock speed is correct, then simply clocking the phone down should allow you to boot normally. Though, it's quite possible something else is causing the problem, since you're able to boot at all... Try clocking down to 1000mhz and boot normally. You'll need to root and install an app similar to setCPU. The issue with the phone not detecting the Sim card may be due to you booting in HW diag mode. Saying that it is listing your imei etc as unknown makes me assume this. Sent from my XT875 using Tapatalk 2

[d73t]

Damn...I guess I got lucky with mine, I was overclocked to 1.5 with jbx, and I was one of the ones that didn't get the bump to 1.2 with ICS.