131 replies to this topic

[dalyer]

Fagulhas, on 06 February 2013 - 05:23 PM, said:

The boot loader ultimately has to:

• Bring the kernel (and all the kernel needs to bootstrap) into memory
  
• Provide the kernel with the information it needs to work correctly
  
• Switch to an environment that the kernel will like
  
• Transfer control to the kernel

On the x86, the boot loader runs in Real Mode. Consequently it has easy access to BIOS resources and functions. Therefore it's a good place to perform memory map detection, detection of available video modes, loading of additional files, etc. The boot loader will collect this information and present it in a way the kernel will be able to understand.


From - http://wiki.osdev.org/Bootloader

Maybe I wasn't clear in my question. What I was curious about is what exactly is the difference between this bootloader and the previous one that might be expected to improve or solve the 3g reboot problem? Or is it not possible to say because these are only available in binary/image form? So the speculation was that a later bootloader might simply be "better" in terms of what initialization it does especially with regard to 3g functionality or something?

Hope that's clearer and sorry to be bothering you will all the questions but just trying to learn/understand...!

[Fagulhas]

dalyer, on 06 February 2013 - 05:34 PM, said:

Maybe I wasn't clear in my question. What I was curious about is what exactly is the difference between this bootloader and the previous one that might be expected to improve or solve the 3g reboot problem? Or is it not possible to say because these are only available in binary/image form? So the speculation was that a later bootloader might simply be "better" in terms of what initialization it does especially with regard to 3g functionality or something?

Hope that's clearer and sorry to be bothering you will all the questions but just trying to learn/understand...!

Yeah its clear and also yes, all we can get is the complete image and we are not able to read it. We can hex edit it and see a few things and from a quick diff we can see several differences tho we cannot tell what they actually affect us.

[fuddman]

Doh! Just had a reboot whilst phone was in car cradle!
First one since Sunday night. Definitely less frequent now though.

[dalyer]

Fagulhas, on 06 February 2013 - 05:56 PM, said:

Yeah its clear and also yes, all we can get is the complete image and we are not able to read it. We can hex edit it and see a few things and from a quick diff we can see several differences tho we cannot tell what they actually affect us.

OK - thanks.

[dalyer]

Has anybody ever collected any log info (logcat and/or kmsg) for one of these 3g reboots? Is that feasible - e.g. can it just be collected after the reboot or would it have to be logged in realtime? Would it help to pinpoint the problem?

[Pain_Deluxe]

After 2 Days on two ROMs NO reboots anymore:)

Hail Dazz and to all others.

[grabster]

No reboots today.
Hope it lasts.

[klezkk]

Meh... Still rebooting. Anyway, ima use the b952 update.app and unlock from scratch to double-check.

[ivan.arandjelovic]

klezkk, on 06 February 2013 - 11:16 PM, said:

Meh... Still rebooting. Anyway, ima use the b952 update.app and unlock from scratch to double-check.

I already did that ... don't waste your time

[Feahnor]

I'm getting this error. How can i fix it?



I'm using CM9 R8 and i have enabled root for adb and apps.

[dalyer]

Seems to be lots of info and maybe solutions for that error message if you Google...

[Feahnor]

Solved by uninstalling Bluestacks.

[scdswd]

I have not had any reboots. My journey: B894 -> B935 -> root+unlock+CWM -> MariDroi 4
I did test today. Wifi, BT, GPS and data on. I moved, used Navigator, some calls, some games. Battery is now 71% and NO RESET ! (how I know it?- installed boot logger and I have PIN on simcard- so it would appear).

Do I have a different bootloader or what?

Edited by scdswd, 07 February 2013 - 04:57 PM.

[backside]

Please, don't waste your time!

I check the scripts, and first I do a copy of my current bootloader:

# dd if=/dev/block/mmcblk0p9  of=./bootloader.img
# dd if=/dev/block/mmcblk0p14 of=./oemsbl.img

After these commands I check both files with the one in the ZIP posted on this thread: result? Files are IDENTICAL!

If the problems with 3G reboots (In my case, I really need to change to 2G to avoid them!) is related with the bootloader, we need to open the ICS (and not de GB) version!

Regards.

[dalyer]

Note: I have edited my post below after the fact in the light of later comments particularly from Dazzozo just so that people are not confused by some of the original stuff that I posted.

As mentioned earlier (and on the IRC transcripts) a request has gone into Huawei to provide an unlocked ICS bootloader. I guess it's a matter of wait and see. I'm sure that one of the guys here will let us know if/when they provide it?

It seemed to be going so well for me but one reboot this morning on the way to work and two more this afternoon - one after another - while sitting (relatively ) still eating lunch...

I'll leave 3G on for a bit longer to test further but if the "new" bootloader is actually identical to the "old" bootloader then any "improvements" must be placebo! (Deleted - backside presumably already had the relevant bootloader installed so that's why the new and old were the same but that will not be the case for everybody depending on what unlocked bootloader they installed).


And so far nobody has been able to provide a reasonable hypothesis as to why the bootloader might be relevant in this context in the first place... (Edit - presumably because the bootloader is a binary image with not much insight into what it does in detail - but there seems to be some correlation between using the later GB [unlocked] bootloader and a reduction in 3g reboots compared to the older unlocked GB bootloader. If/when Huawei unlock the ICS bootloader that is the best available).

Ultimately I will be toggling to 2G anyway to save battery. But thanks to those who have been trying to improve this situation.

Edit: oops - smiley overload above!

Edited by dalyer, 08 February 2013 - 11:15 AM.

[sssingletrack]

backside, on 07 February 2013 - 06:44 PM, said:

Please, don't waste your time!

I check the scripts, and first I do a copy of my current bootloader:

# dd if=/dev/block/mmcblk0p9  of=./bootloader.img
# dd if=/dev/block/mmcblk0p14 of=./oemsbl.img

After these commands I check both files with the one in the ZIP posted on this thread: result? Files are IDENTICAL!

If the problems with 3G reboots (In my case, I really need to change to 2G to avoid them!) is related with the bootloader, we need to open the ICS (and not de GB) version!

Regards.

I don't think Daz would release something that's exactly the same as the original. I guess the file has to be the same md5 as the phone would pick up on a different md5 for a boot loader? I might be wrong.

[dalyer]

backside, on 07 February 2013 - 06:44 PM, said:

After these commands I check both files with the one in the ZIP posted on this thread: result? Files are IDENTICAL!

You mean MD5s are the same?

Edit: post crossed with sssingletrack's.

Edited by dalyer, 07 February 2013 - 07:12 PM.

[vibracopilu]

backside, on 07 February 2013 - 06:44 PM, said:

Please, don't waste your time!

I check the scripts, and first I do a copy of my current bootloader:

# dd if=/dev/block/mmcblk0p9  of=./bootloader.img
# dd if=/dev/block/mmcblk0p14 of=./oemsbl.img

After these commands I check both files with the one in the ZIP posted on this thread: result? Files are IDENTICAL!

If the problems with 3G reboots (In my case, I really need to change to 2G to avoid them!) is related with the bootloader, we need to open the ICS (and not de GB) version!

Regards.

Don't be rude man, Daz is not just any noob! Reboots are now less often than before.

[kosac]

ok so after few days of testing.. 2 phones whith cm10.. both restarting on 3G.. when i move with car restarts more times then walking.. maybe problem is when swithing to another BTS?

[fr0do]

backside, on 07 February 2013 - 06:44 PM, said:

Please, don't waste your time!

I check the scripts, and first I do a copy of my current bootloader:

# dd if=/dev/block/mmcblk0p9  of=./bootloader.img
# dd if=/dev/block/mmcblk0p14 of=./oemsbl.img

After these commands I check both files with the one in the ZIP posted on this thread: result? Files are IDENTICAL!

If the problems with 3G reboots (In my case, I really need to change to 2G to avoid them!) is related with the bootloader, we need to open the ICS (and not de GB) version!

Regards.

If you read above you will see why. The bootloader is the latest GB one. If you already had that, then, well yes, the files will be the same.

Not everyone is on the same bootloader. It's not worthwhile if you have installed the last GB release to have it.

Edited by fr0do, 08 February 2013 - 08:28 AM.