10 replies to this topic

[o0beaner]

So I made a grave mistake, and grabbed the latest stock firmware to flash via RSD because my partition tables had become damaged, and I was unable to use encryption which I need for work.That was obviously the 9.30.1 package. I have since read that the exploits to unlock the bootloader were corrected as of 9.16.x, which is scary, but the AP Fastboot screen still shows me as having an unlocked bootloader, and when I try to flash a ROM I am greeted by the stock 'WARNING BOOTLOADER UNLOCKED' splash.

 

The problem is, it never moves from that spot. Did flashing 9.30.1 somehow break my ability to flash ROMs even though my BL is unlocked?

 

Steps executed:

 

RSD to 9.30.1

Fastboot flash recovery (tried TWRP, Philz, CWM)

Wipe, wipe, wipe

Flash ROM (Tried AOSPA, CM 10.2/11)

Reboot

Phone hangs at BL warning splash

 

Anyone have any ideas?

[johnthehillbilly]

Ok...... Apparently the rsd to 9.30 was sucessfull...... Which version of twrp did you use?..... (May not have been the right version)..... The BL unlocked screen is simply a "boot logo" not all ROMs will have a "custom" logo.....it can be changed on its own if you choose......are you trying to flash a ROM that is not for the 926..... Or "too old" for your system version?.......

[johnthehillbilly]

Also...... Most ROMs require you to mount system in twrp etc to flash properly........ Just a thought in case you missed that step

[o0beaner]

I have tried:

 

unified TWRP 2.7.0.0

unified philz 6.25.9

xt926 TWRP-2.6.3.0

xt926 CWM 6.0.44

 

I am trying to flash two roms that I was using successfully until a day ago.They are both for the unified msm8960. I did try an xt926-specific rom, with the same results, however.

 

That warning logo typically fires off before the ROM's boot animation. Prior to the RSD, I had replaced it with the stock Motorola 'M' logo through fastboot, but that was obviously changed. I have left the phone sitting for well over 10 minutes after flashing just to see if it ever finished the boot cycle, but it never does.

 

Edit: I tried flashing both ways, mounting system and not.

[johnthehillbilly]

2.6.3.0 twrp is also what I use....... Maybe try backup and wipe internal and external storages..... Run RSDLite again (pay close attention for any failures )..... Re-flash twrp....... (Make sure you power off then boot into recovery directly after to avoid problems) ....... Yes the logo will be changed to the bl unlocked warning with a full rsd, not a big deal tho, it won't have any effect on the flashing process.......

[o0beaner]

Yeah, no dice. No failures during the RSD process. Tried, for kicks, to roll back to a previous firmware, but obviously the trustedzone flash fails if I do that.

[johnthehillbilly]

Go here

Please Login or Register to see this Hidden Content

...... You will find that to an extent, you can indeed "roll back" Sam has made it possible with the universal script and / or his FXZ generator (mentioned within the HoM thread)....:)

[johnthehillbilly]

With house of moto you can also have it flash your custom recovery and custom boot logo as well......

[o0beaner]

Yeah, but it doesn't let me flash a previous firmware. I did go through the process, and it fails in the same place that my RSD attempt fails, which is the trusted zone, or tz.mbn, which is where the bootloader hole was located before they patched it. Now, apparently, the trusted zone partition can't be written to, or at least in a way that anyone knows about.

[johnthehillbilly]

You can actually skip flashing the TZ partition with HoM.... and you can "downgrade"

[o0beaner]

Haven't seen how to do that. I've tried removing them from the scripts that the generator creates, but then the other partitions fail to flash.