Unsure, could be that hboot 1.55+ is not allowing to even pass a bad commandline to recovery/anywhere, so i wanna check something else
I am here, had work troubles. What can I try )))))))))))))))))))
Unsure, could be that hboot 1.55+ is not allowing to even pass a bad commandline to recovery/anywhere, so i wanna check something else
I am here, had work troubles. What can I try )))))))))))))))))))
Ehhh, i don't have warranty and receipt.
But i have cable for charging. I can use to whip myself 'till next official RUU.
You couldn't be more wrong. Your problem was easy to solve compared to his. You didn't have "active cmdline overflow" error and you could boot to recovery. But, cudos to you for trying to helpYou seem to be exactly in the same boat as I was until yesterday, and I managed to restore my phone to working condition. (Look up my thread in this forum with 'Bootlooping....Android Revolution GPE' in the title box. You will see how I was helped out. You have to follow the instructions carefully).
Also that doesn't look like a signed firmware.zip from an OTA, for one thing it's way too big, firmware.zip shouldn't do a FULL-WIPE, and they are actually signed/encrypted, otherwise we could all compile our own firmware.zip to flash even with S-On.
All the OTApkg.zip I have captured contained firmware.zip that had no encryption on them at all. you can open any of then in 7zip without error. Rom.zip pulled from a RUU is a different story
True, you can usually extract them using 7zip or WinRAR (but not using Windows Explorer), but they are still signed, for example:
signed firmware.zip (notice the fist 0x100bytes, before the zip identifier [PK]):
unsigned zip:
Also, if you try changing a signed zip using WinRAR (probably the same with 7-zip), you'll get an error; it extracts just fine, but here for example i tried deleting the recovery.img directly in the zip and got an error:
Notice how WinRAR identifies it as an SFX ZIP, not a normal ZIP; it's assuming the sfx module is in there.
But you booted the phone, right?Remains to be seen if we got lucky, or if this is a workaround for S-On and hboot 1.55+
(that's why i didnt post what we did... need more confirmation)