google-code-export / bricked

Automatically exported from code.google.com/p/bricked
Other
0 stars 0 forks source link

Flashing with "special" parameters ends in a bootloop #85

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Rename to 
Bricked-3.0-v0.55-b7-gpuoc-ics-maxkhz=1566000-minkhz=310500-gov=lazy-maxscroff=4
32000
2. Flash in recovery
3.

What is the expected output? What do you see instead?
Expected: Device booting.
Instead: Bootloop, device hangs at bootsplash.

What version of the product are you using? On what operating system?
Bricked-3.0-v0.55-b7-gpuoc-ics (The version before you published the "fix" for 
the OrDroid ROM) on InsertCoin 5.1.7.

Please provide any additional information below.
I never used any other kernel besides bricked, not even for testing. Also I 
never used any other ROM besides InsertCoin. So there should be no "modified" 
files or something like this.

To solve the problem I flashed Bricked-3.0-v0.55-b7-gpuoc-ics with standard 
parameters: Voila - the device booted.

Original issue reported on code.google.com by cweine...@gmail.com on 5 Apr 2012 at 11:05

GoogleCodeExporter commented 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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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