Closed GoogleCodeExporter closed 9 years ago
when was the file downloaded?
if it was not in the past hours, delete and redownload. (same link)
I changed a script inside the file to compensate for some strange boot.img
cmdline parameters set by romdevs.
If the problem persists (which I hope not, can't test right now) boot into
recovery after your bootloop, and give me /proc/last_kmsg
Original comment by showp1984
on 5 Apr 2012 at 11:10
The new version did fix it, sorry that I didn't test it on my own. Strange
thing is, that only these "special" parameters ended in that bootloop. With the
standard ones it worked without problems (with the same version). Maybe bad
luck.
Original comment by cweine...@gmail.com
on 5 Apr 2012 at 11:16
Not strange, the cmdline inside your boot.img you used probably was at it's
limit (from the length, probably some garbage). If you set default parameters,
my script will detect that and make no change, but other values will then be
set, which leads to a too long cmdline = no boot.
Glad it worked for you.
Original comment by showp1984
on 5 Apr 2012 at 11:36
Original issue reported on code.google.com by
cweine...@gmail.com
on 5 Apr 2012 at 11:05