Introducing XDA:DevCon – A Conference For Developers By Developers
XDA Developers Android and Mobile Development Forum
Forgot your password?
 
Post Reply+
Tip us?
 
Crysis21
Old
#1  
Crysis21's Avatar
Recognized Developer - OP
Thanks Meter 2625
Posts: 1,098
Join Date: Sep 2010
Location: Timisoara

 
DONATE TO ME
Question [Q] Changing Bootloader - Discussion - What's the safest way?

Hi guys, I want to change my phone bootloader and also to a friend of mine. But I have some nasty experience with bootloader upgrading so I though that a discussion here would be good, so everyone know what to do in the future.

For example, I use ODIN for firmware upgrades, but as you all know it has a quite big rate of failures, caused by different reasons. On the other hand, we have Heimdall which is supposed to be safer and has more options than ODIN (bootloader flash only and such things).

The point is, while we are in download mode, and the flashing of bootloader fails, after restart... well... there won;t be a start anymore. The phone will be dead. What I was thinking is: what if we don't thick restart on ODIN or Heimdall and if flashing the boot loader fails, the phone will remain in download mode. Couldn't this be the opportunity to try again? After all, all we need is download mode.

We could try second time with Heimdall, or another full firmware with odin... what do you say guys?


Remaining in download mode gives us a second chance to bootloader writing?

Sorry if I've been really fuzzy in my ideas but I'm very sleepy right now.
The Following User Says Thank You to Crysis21 For This Useful Post: [ Click to Expand ]
 
Benjamin Dobell
Old
#2  
Recognized Developer
Thanks Meter 463
Posts: 823
Join Date: Jul 2010
Location: Melbourne

 
DONATE TO ME
Quote:
Originally Posted by Crysis21 View Post
Remaining in download mode gives us a second chance to bootloader writing?
Unfortunately no. If a flash fails it's because the phone has stopped responding to commands. The phone won't continue responding to commands until you've booted into download mode again. It's for this very reason I don't actually have a "no reboot" option for Heimdall, it would be pretty much pointless.

However luckily if you're just flashing a secondary bootloader the device can still be booted up using a custom jig. This is because devices store a backup secondary bootloader that can be used if the first one is corrupt. A custom jig seems to cause the device to boot using this backup secondary bootloader.

However as far as I can tell if you stuff up the primary bootloader then you're toast. This would require a JTAG fix. I'm not actually sure if this has ever even happened though.
Heimdall - Open-Source Cross-Platform Galaxy S Firmware Flashing Software
[LISTING] Firmware with Fixed (OS X Compatible) Secondary Bootloader (Sbl.bin)
The Junkheap – Experimental Device Donations

If any of my work interests you and you'd like to support me or help cover the cost of development, donations are very much appreciated. Alternatively you could purchase one of Glass Echidna's apps from the Android market i.e. Anti-Squish.

Google Plus: +Benjamin Dobell
 
Crysis21
Old
#3  
Crysis21's Avatar
Recognized Developer - OP
Thanks Meter 2625
Posts: 1,098
Join Date: Sep 2010
Location: Timisoara

 
DONATE TO ME
The thing is, 4 months ago I ended up on JTAG. After messing the bootloader I managed to get download mode with custom JIG. But after that I don;t know exactly the mistakes I've made, but I ended up with a dead phone. No JIG working, nothing. So... yes it happened. I am toasted already with bootloader changing) that's why I was asking if remaining in Download mode helps with somthing.

Thanks for your answer
 
Benjamin Dobell
Old
#4  
Recognized Developer
Thanks Meter 463
Posts: 823
Join Date: Jul 2010
Location: Melbourne

 
DONATE TO ME
Sorry I should have been clear. I know there are cases where users have hard-bricked their phone and not even a custom jig would help so JTAG was required.

During the early stages of Heimdall's development, prior to the custom jig discovery, I bricked my device to the point of not being able to charge. This was because either boot.bin or params.lfs failed to flash due to a bug in a alpha release of Heimdall. We didn't know about custom jigs then so I was unable to actually test if it was recoverable.

However, all the hard-brick cases that I've heard sufficient detail about, turn out to be a result of users flashing a primary bootloader that was not designed for their device. So what I should have said is that I'm not sure if anyone has ever actually failed to sucessfully flash a primary bootloader (other than me with an alpha build).

Anyway unfortunately there's not a whole lot that can be done to 100% remove the risk of bricking. Either the secondary bootloader USB control software is buggy or the hardware itself is crap and sometimes it doesn't get on well with some people's USB ports. Unless we come up with a way to easily replace the bootloaders from the device itself then the best thing you can do is use a reliable USB port.
Heimdall - Open-Source Cross-Platform Galaxy S Firmware Flashing Software
[LISTING] Firmware with Fixed (OS X Compatible) Secondary Bootloader (Sbl.bin)
The Junkheap – Experimental Device Donations

If any of my work interests you and you'd like to support me or help cover the cost of development, donations are very much appreciated. Alternatively you could purchase one of Glass Echidna's apps from the Android market i.e. Anti-Squish.

Google Plus: +Benjamin Dobell
The Following User Says Thank You to Benjamin Dobell For This Useful Post: [ Click to Expand ]
 
chenthu
Old
#5  
chenthu's Avatar
Member
Thanks Meter 9
Posts: 59
Join Date: Sep 2011
Location: Madurai
Thanks for the information...
 
Post Reply+
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

report this ad
Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Go to top of page...