FORUMS

XDA Picks: Best Apps of the Week (May 15 – 30)

Apps are at the front and center of any smartphone experience, and with over a … more

Google No Longer Sending Calendar SMS Notifications

In a not entirely surprising move, Google announced that it’s putting an … more

Enable Multi-Window Mode on M Developer Preview

What was not mentioned in yeterday’s keynote was Android M’s multi-window … more

I/O Summary: Google Cardboard Virtual Reality

One year ago, Google introduced cardboard. Amazingly enough, that was all it took to fire … more

baseband question

Thanks Meter: 78
 
By orateam, Senior Member on 13th January 2014, 07:30 PM
Post Reply Subscribe to Thread Email Thread
I have the good MDK baseband and currently on Hyperdrive AOSP. I wanted to upgrade my radio. Is this the same as baseband, will it break something?
 
 
13th January 2014, 08:14 PM |#2  
Senior Member
Flag Decatur
Thanks Meter: 843
 
More
Quote:
Originally Posted by orateam

I have the good MDK baseband and currently on Hyperdrive AOSP. I wanted to upgrade my radio. Is this the same as baseband, will it break something?

Radio is separate from build base...

safestrap enabled, Hyperdrive driven
13th January 2014, 08:36 PM |#3  
heath2805's Avatar
Senior Member
Flag Baltimore, MD
Thanks Meter: 430
 
More
Quote:
Originally Posted by orateam

I have the good MDK baseband and currently on Hyperdrive AOSP. I wanted to upgrade my radio. Is this the same as baseband, will it break something?

Yes radios are the baseband version. Heres where the radios are, but to be safe I would make sure the MD5 matches before flashing in recovery. http://forum.xda-developers.com/show...php?p=46550751

Sent from my SCH-I545 using Tapatalk
15th January 2014, 04:44 AM |#4  
OP Senior Member
Flag Orlando
Thanks Meter: 78
 
More
Quote:
Originally Posted by heath2805

Yes radios are the baseband version. Heres where the radios are, but to be safe I would make sure the MD5 matches before flashing in recovery. http://forum.xda-developers.com/show...php?p=46550751

Sent from my SCH-I545 using Tapatalk

Thanks.

And just because i can't figure this one thing out. How come so many people who upgrade their phones are locked out of unlocking/root, yet i can go up and down ?
15th January 2014, 04:55 AM |#5  
thedoman's Avatar
Senior Member
Flag Ohio
Thanks Meter: 87
 
More
Could flashing a radio other than mdk on mdk bootloader Bork your ability to make calls? I flashed mk2 radio over mdk bootloader and could not make calls on Sammy roms but could if I flashed cm based roms.

Sent from my SCH-I545 using Tapatalk
Last edited by thedoman; 17th January 2014 at 06:46 AM.
15th January 2014, 04:58 AM |#6  
gnubian's Avatar
Senior Member
Flag Asheville
Thanks Meter: 119
 
More
Quote:
Originally Posted by orateam

Thanks.

And just because i can't figure this one thing out. How come so many people who upgrade their phones are locked out of unlocking/root, yet i can go up and down ?

You can go up and down in terms of radios and android versions, not builds. We're you to odin to anything but mdk you would be stuck in a state where you could not regain an unlocked bootloader. All builds have a root method though. If this is something you don't understand I would research it more, simply to prevent you from accidentally losing your mdk build.
15th January 2014, 02:17 PM |#7  
OP Senior Member
Flag Orlando
Thanks Meter: 78
 
More
Quote:
Originally Posted by gnubian

You can go up and down in terms of radios and android versions, not builds.


ahh, so narrowed it down to builds. So what is a build? I have ODINed before, obviously to MDK. When a build, such as hyperdrive or eclipse 4.4.2 is made, it seems that they keep the parts that link back to MDK. What is that part? The reason i ask is because i want to start making my own builds and would like a deep understanding so i don't screw up.
15th January 2014, 06:13 PM |#8  
gnubian's Avatar
Senior Member
Flag Asheville
Thanks Meter: 119
 
More
Quote:
Originally Posted by orateam

ahh, so narrowed it down to builds. So what is a build? I have ODINed before, obviously to MDK. When a build, such as hyperdrive or eclipse 4.4.2 is made, it seems that they keep the parts that link back to MDK. What is that part? The reason i ask is because i want to start making my own builds and would like a deep understanding so i don't screw up.

Those roms (I'm assuming) don't touch the bootloader, which is the part of the mdk build that you must not change in order to maintain the loki exploit that allows you to load custom roms and kernels. If you build a rom from aosp source or what have you just make sure it doesn't include any parts of the bootloader/boot chain and you should be ok.

Read this if you haven't already

http://forum.xda-developers.com/show....php?t=2606501
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes