140 replies to this topic

[ACS10]

Dazz has released a new modified bootloader which claims to have fixed the 3G reboot issue on our G300.

He posted the work in the CM9 thread but it might get overlooked by others so I thought a new thread would go down well.

"Update: an issue people frequently encountered for quite some time (3G reboots) was located in the unlocked bootloader images. This has been fixed. If you are having these issues, run the bootloader unlocking script here again.

Read: https://docs.google....Kq10K_-aeM/edit

Download: http://g300.thebrona...926-root-bl.zip

Dazz does it again.  

EDIT:  If you're getting "Permissions denied", do this - Settings >>> 'Developer Options' => 'Root access' => 'Apps and ADB'.  Thanks to fiah84.

Post your results here - has it fixed 3G reboots for you?

Massive thanks (as usual) to top G300 dev Dazz.

Edited by ACS10, 04 February 2013 - 03:59 PM.

[fiah84]

Well, I had 0 spontaneous reboots with whatever I had on my G300 before (no 3G coverage), so I guess I could be the control group

[peterck]

Will this work on the cm10.1  rom

[Dazzozo]

It's a bootloader...

[peterck]

I don't know if I have a problem with my 3g network it just shows this, so don't know if I need to fix it though cause I don't get any 3G reboot.

Attached Files

•  uploadfromtaptalk1359918480834.jpg   33.73K   303 downloads

Edited by peterck, 03 February 2013 - 07:13 PM.

[Dazzozo]

...what? Have you even installed it?

[ACS10]

That just means you don't have a signal.  This is a reworked custom bootloader which has nothing to do with the OS.

AFAIK everybody with the custom bootloader (i.e. everyone not on stock) has reboot issues to some degree.  On some roms I found it'd reboot sometimes when switching between 2g/3g (low 3g signal), under 10.1 it rebooted randomly while driving the other day.

This could potentially fix everybody's reboot problems.

Hats off to Dazz.

[ACS10]

I'll be reporting my findings this week - I've installed the new bootloader without issue.  Everything good!

[shadygad]

installed trying to fix the issue

[Pain_Deluxe]

i'm on infusion.

Can Capture the last lines :/(screenshooting) because the cmd close imendently after its done.

so is it done?

[peterck]

ACS10, on 03 February 2013 - 07:15 PM, said:

That just means you don't have a signal.  This is a reworked custom bootloader which has nothing to do with the OS.

AFAIK everybody with the custom bootloader (i.e. everyone not on stock) has reboot issues to some degree.  On some roms I found it'd reboot sometimes when switching between 2g/3g (low 3g signal), under 10.1 it rebooted randomly while driving the other day.

This could potentially fix everybody's reboot problems.

Hats off to Dazz.

I don't know if it's just no signal. when I turn on 2g network the signal works whereas when I turn on 3g network I have no signal

Attached Files

•  uploadfromtaptalk1359921162748.jpg   55.18K   182 downloads
•  uploadfromtaptalk1359921178936.jpg   55.07K   173 downloads

[Dazzozo]

Pain_Deluxe, on 03 February 2013 - 07:52 PM, said:

i'm on infusion.

Can Capture the last lines :/(screenshooting) because the cmd close imendently after its done.

so is it done?

yes

[dreamypuma]

Sorry to be a complete noob.

I'm using the Baidu Rom, and CWM v4. I've read the google doc,but i'm still not entirely clear on how I run this script?

Using windows, do I just leave the phone in USB debugging, and run the bootloader batch file?

When complete will I lose CWM?

[Pyntux]

I will install this new bootloader, but I haven't reboot problems with old bootloader...

[Pain_Deluxe]

Dazzozo, on 03 February 2013 - 07:53 PM, said:

yes

thanks my god:D

(in my scareness i have it done now it a couple of time Hope thats not a issue ^^)

So test it now over the night by loading the battery and tomorrow over the day.

Edited by Pain_Deluxe, 03 February 2013 - 08:01 PM.

[vibracopilu]

So considering that the bootloader is separate from the rom, even if I switch to another rom I will still have this fixed bootloader on my my device after I install it?

[jsevi83]

ACS10, maybe you should've waited until this was properly tested. I really hope this bootloader fixes 3g reboots but we still don't know if it does, it needs time to test and confirm.

[ACS10]

vibracopilu, on 03 February 2013 - 08:28 PM, said:

So considering that the bootloader is separate from the rom, even if I switch to another rom I will still have this fixed bootloader on my my device after I install it?

Once it's flashed it'll be there for good unless you change it yourself.  It won't affect anything with your rom or recovery.

@ jsevi83 It'll only get tested if people on here are willing to try it en masse   I've had no ill effects so there's no harm in trying. You can always flash the old bootloader if for any reason this one causes problems.

Edited by ACS10, 03 February 2013 - 08:50 PM.

[jsevi83]

ACS10, on 03 February 2013 - 08:50 PM, said:

@ jsevi83 It'll only get tested if people on here are willing to try it en masse   I've had no ill effects so there's no harm in trying. You can always flash the old bootloader if for any reason this one causes problems.

You are announcing it as "new bootloader that fixes 3g reboot issue". There are already some users in the irc chat testing it because they get reboots very often, so they can confirm if this bootloader fixes the issue. Anyway, I hope you won't have to change the title of this thread  

[vibracopilu]

dreamypuma, on 03 February 2013 - 07:53 PM, said:

Sorry to be a complete noob.

I'm using the Baidu Rom, and CWM v4. I've read the google doc,but i'm still not entirely clear on how I run this script?

Using windows, do I just leave the phone in USB debugging, and run the bootloader batch file?

When complete will I lose CWM?

My method (I previously had CM9 but the scripts weren't detecting my phone):

1) Flash B952 repack via CWM http://www.modaco.co...page__hl__ b952
2) Enable debugging after flashing the rom
3) Connect to the pc
4) instal the "Handset WinDriver"
5) Run "root-windows"
6) Run "bootloader-windows"

*If you still get some issues for step 5) and 6) try to change your usb port

Edited by vibracopilu, 03 February 2013 - 09:05 PM.