[fxz] 4.4.2 183.46.15

[2useless]

09/14/14 22:20:50 Multi upgrade started for 1 phones
09/14/14 22:20:50 [Device ID: 0] 1/17 flash partition "gpt.bin"
09/14/14 22:20:50 [Device ID: 0] 2/17 flash sbl1 "sbl1.mbn"
09/14/14 22:20:51 [Device ID: 0] 3/17 flash sbl2 "sbl2.mbn"
09/14/14 22:20:52 [Device ID: 0] 4/17 flash sbl3 "sbl3.mbn"
09/14/14 22:20:53 [Device ID: 0] 5/17 flash rpm "rpm.mbn"
09/14/14 22:20:54 [Device ID: 0] 6/17 flash tz "tz.mbn"
09/14/14 22:20:54 [Device ID: 0] 7/17 flash aboot "emmc_appsboot.mbn"
09/14/14 22:20:55 [Device ID: 0] 8/17 flash modem "NON-HLOS.bin"
09/14/14 22:21:09 [Device ID: 0] 9/17 flash fsg "fsg.mbn"
09/14/14 22:21:09 [Device ID: 0] 10/17 erase modemst1
09/14/14 22:21:10 [Device ID: 0] 11/17 erase modemst2
09/14/14 22:21:11 [Device ID: 0] 12/17 flash logo "logo.bin"
09/14/14 22:21:12 [Device ID: 0] 13/17 flash boot "boot.img"
09/14/14 22:21:17 [Device ID: 0] 14/17 flash recovery "recovery.img"
09/14/14 22:21:22 [Device ID: 0] 15/17 flash system "system.img"
09/14/14 22:26:40 [Device ID: 0] 16/17 erase tombstones
09/14/14 22:26:41 [Device ID: 0] 17/17 erase cache
09/14/14 22:26:43 [Device ID: 0] reboot
09/14/14 22:33:53 000000b0 Phone.cpp 1571 0 ERROR Waiting for phone's handle is setted successfully after restart [430000 ms] completion. failed
09/14/14 22:33:53 [Device ID: 0] Please manually power up this phone.
09/14/14 22:41:03 000000b0 Phone.cpp 3974 -1 ERROR CPhone::WaitForPhone timed out. Iteration-1
09/14/14 22:41:03 [Device ID: 0] Please manually power up this phone.
09/14/14 22:48:13 000000b0 Phone.cpp 3974 -1 ERROR CPhone::WaitForPhone timed out. Iteration-2
09/14/14 22:48:13 [Device ID: 0] Please manually power up this phone.
09/15/14 01:10:19 --------------------------------------------------------------------------------

 

[SamuriHL]

Reflash just system. Before reinstalling root after doing so check about phone again.

Sent from my SM-P600 using Tapatalk

 

[2useless]

Reflash just system. Before reinstalling root after doing so check about phone again.

Sent from my SM-P600 using Tapatalk

It shows the right version after reflashing. I wasn't too concerned about it, I was just curious about why it seemed to show a bizarre version before. Thanks. :good:

 

[SamuriHL]

The only thing I can say is that something messed with your build props. I had zero doubt that the phone contained the proper partitions but the build prop file was clearly messed with by something. In any case, you should be able to re-root it and be fine from here on out.

 

[bweN diorD]

well that was anti-climactic, i was hoping he flashed a maxx rom so i could try it

 

[SamuriHL]

well that was anti-climactic, i was hoping he flashed a maxx rom so i could try it

I know the result of that, too. qhsusb dload is not something you wish to encounter.

 

[bweN diorD]

I know the result of that, too. qhsusb dload is not something you wish to encounter.

lol! im such a noob, i had to google that
i guess it pays to know just how stupid i can be before i do something really bad
i always read too much before i try anything, i guess thats why i have had 10-12 premium phones and never bricked one

 

[SamuriHL]

lol! im such a noob, i had to google that
i guess it pays to know just how stupid i can be before i do something really bad
i always read too much before i try anything, i guess thats why i have had 10-12 premium phones and never bricked one

LMAO! My first brick experience was with the Bionic and it lasted about 36 hours. Timmy10shoes fixed me up though and we unbricked it and got it back on the OTA path. When the ICS leaks started coming I decided to write myself a quick tool to help myself install the leaks without losing data or bricking the phone. Timmy convinced me to create a new thread and post it. Thus started the House of Bionic and the rest is history. Never bricked a phone since.

 

[2useless]

After flashing the fxz, it listed the proper system version and Android version. However, after I flashed CWM and rooted, it reverted back to how my previous screenshot looked. I would be fine with it, but for some reason the Google voice commands don't work now (worked with just the fxz flashed) and says 'Can't reach Google at the moment'. Everything else seems to work fine. I'll reflash the fxz and pinpoint at which step everything enters ****upland.

 

[killrhythm09]

Well, which CWM and root packages are you using?

 

[2useless]

I am using CWM 6.0.4.9 and SuperSU 2.02.

The problem had to do with the tethering hack.
http://xdaforums.com/showthread.php?t=2578410

Again, the only real problem I had was not having Google Now/Voice work, everything else seemed to operate fine. I put the old 'build.prop' back on and it made everything go back to normal

 

[killrhythm09]

You were using a tethering hack for the Droid Ultra...

Why didn't you just use this?

http://xdaforums.com/droid-razr-hd/orig-development/mod-native-tether-exploit-build-183-46-t2872547

 

[SamuriHL]

As I said, something overwrote your build props. You never mentioned a tethering hack in your original posts. When people leave out information it wastes a lot of time.

Sent from my SM-P600 using Tapatalk

 

[SamuriHL]

I flashed 'VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml' using your utility with the KEEP DATA option.

I don't know what to say. I for sure didn't hunt around for a Maxx fxz and I certainly don't have a copy of one sitting around on my PC. I downloaded the .zip you posted above and used your utility to flash it. Afterwards I flashed dhacker's CWM (v6.0.4.9) and SU (UPDATE-SuperSU-v2.02.zip). That is it. I did nothing else.

This, specifically, is what I'm referring to. That part about "I did nothing else" was simply not true and wasted everyone's time.

Sent from my SM-P600 using Tapatalk

 

[2useless]

This, specifically, is what I'm referring to. That part about "I did nothing else" was simply not true and wasted everyone's time.

Sent from my SM-P600 using Tapatalk

:good:

 

[SaddleTramp]

after 4 shots of cheap rye whiskey I was able to do this update. Thanks, my only recomindation would be some better Scotch!

 

[axcelgo]

Hi guys,
As a rookie who decided to start his rooting and unlocking exploits with the Droid RAZR HD some months ago using the towelroot method and motapocalypse way back in June, but has done nothing aside from install titanium backup to remove Verizon bloat on stock (stock recovery would also be present unless unlocking changed that?); can I make these assumptions:

On stock recovery, to install the latest ota, just re-download system apps to avoid the RSD method
After taking the ota, flash a custom recovery
Install a custom ROM if desired
If a custom ROM is installed and another ota is released e.g. Android L, just reflash a stock.img of the bootloader to take the ota.
If no custom ROM is installed, but a custom recovery is flashed, then regaining root access is done by side loading a super user.
If a custom ROM is installed, and a custom recovery is flashed, then root is obtained the same way as above.
Profit???

 

[killrhythm09]

Hi guys,
As a rookie who decided to start his rooting and unlocking exploits with the Droid RAZR HD some months ago using the towelroot method and motapocalypse way back in June, but has done nothing aside from install titanium backup to remove Verizon bloat on stock (stock recovery would also be present unless unlocking changed that?); can I make these assumptions:

On stock recovery, to install the latest ota, just re-download system apps to avoid the RSD method
After taking the ota, flash a custom recovery
Install a custom ROM if desired
If a custom ROM is installed and another ota is released e.g. Android L, just reflash a stock.img of the bootloader to take the ota.
If no custom ROM is installed, but a custom recovery is flashed, then regaining root access is done by side loading a super user.
If a custom ROM is installed, and a custom recovery is flashed, then root is obtained the same way as above.
Profit???

How exactly are you going to re-download system apps? I don't know what you removed, but it's not like all the bloat that comes with stock is on the Play Store. Besides, even if they are, you'd have to manually convert them to system apps and make sure they are the exact same version and have the same permissions as before.

I would just use RSD Lite and save yourself a lot of trouble.

Yes, you can flash custom recovery and ROMs after taking the OTA if you want. I assume you would be taking the OTA to update to the KK bootloader, otherwise there's no point if you want to use custom ROMs.

As for the question about an Android L OTA it's kind of a moot point because it won't be coming to this device, but it wouldn't be as simple as just updating the bootloader like that. I always RSD back to stock if I want to take an OTA because I also remove bloat with Titanium and do several other mods that would probably interfere with a stock update.

As long as you're bootloader unlocked, no root exploits are needed and you should always be flashing a SU package in recovery if you need root.

 

[madkel]

Just want to say thanks SamuriHL for the files, your tools, and thorough instructions (not only these but previous ones as well). It has definitely helped me get the most out of my phone, and your work is greatly appreciated!

 

[zekemo]

Just want to say thanks SamuriHL for the files, your tools, and thorough instructions (not only these but previous ones as well). It has definitely helped me get the most out of my phone, and your work is greatly appreciated!

QFT