Jump to content

Unknown Baseband


Recommended Posts

Posted

Hey fellows, I don't know if you noticed or if this happens with anyone else but the thing is that under About Phone I got "Baseband: Unknown"...

It didn't give me any problems but it shouldn't be like this...

I unlocked without the qcn backup and just restored mac address, don't know if this has anything to do.

Currently running CM7 v3.0.

Posted (edited)

yeah I got that too ;)

I unlocked before the wifi fix came,also,I have changed partitions with TPT.

So who knows,could be anything.

Edited by Guest
Guest Kayusumi
Posted

There is no baseband information in build.prop of CM7 v3.0, so do v2.5

But you can find it in v2.0

Guest Frankish
Posted

I didn't know there was a custom partition method for skate?

Posted (edited)

I didn't know there was a custom partition method for skate?

Still needs work.

You get an error at 44%

but it workss fine.

Edited by Guest
Guest trueno2k
Posted (edited)

http://android.modac...from-ztes-site/

Still needs work.

You get an error at 44%

but it workss fine.

If you haven't read my post from http://android.modac...ost__p__1844362 I found that the boot.img used in Amphoras' image.bin files was the culprit... The boot.img file used in his image.bin's are basically recovery.img files renamed... So I replaced the boot.img file with 2.3.5 super2root.img file found http://www.sharaget....packge-uNCNm6tM, this fixed the 44% error, however, the super2root.img renamed boot.img is an actual 2.3.5 android boot image and so when the phone is left to reboot (on it's own) after TPT'ing, the boot.img would try loading the rom on the phone which of course there is no rom flashed... SO, to get CWM recovery to load, you'll need to hold the VOL- button (either during the TPT or immediately after the TPT has finished) until the phone reboots again for the second time and then CWM will then boot up, so that you can go ahead with flashing your phone... Hopefully this will help temporarily fix the flash error issue and give you access to CWM recovery after TPT'ing your OMC/Skate..

Happy Flashing ^_^

EDIT: Just a thought... I just realised this 44% error linking to boot.img could be due to not having the right partition layout for the boot sector within the partition_zte.mbn file when Amphoras HEX'ed it for repartitioning the OMC/Skate... It could be quite possible that Amphoras just needs to HEX the partition_zte.mbn boot sector to accommodate for the size and endpoint of the boot.img and startpoint for the next partition sector... any opinions???

Edited by trueno2k
Guest trueno2k
Posted

Hey fellows, I don't know if you noticed or if this happens with anyone else but the thing is that under About Phone I got "Baseband: Unknown"...

It didn't give me any problems but it shouldn't be like this...

I unlocked without the qcn backup and just restored mac address, don't know if this has anything to do.

Currently running CM7 v3.0.

I was just reading your post again and I've come across this too... I can't remember if I had lost my baseband before or after unlocking my OMC or whether I lost my baseband when I used the qcn wifi fix or whether it's something to do with version 3 of CM7 for Skate... So far, my OMC hasn't behaved any differently or oddly at this moment but it does worry me that my OMC can fail on something without the baseband present... anyone got any leads to why we're getting no baseband number/code???

Posted

I was just reading your post again and I've come across this too... I can't remember if I had lost my baseband before or after unlocking my OMC or whether I lost my baseband when I used the qcn wifi fix or whether it's something to do with version 3 of CM7 for Skate... So far, my OMC hasn't behaved any differently or oddly at this moment but it does worry me that my OMC can fail on something without the baseband present... anyone got any leads to why we're getting no baseband number/code???

Because CM7 is not giving this info to the phone.

This should be fixed by adding this info into its build.prop, I tried but no luck.

I just flashed Elitemovil and it presented me the current baseband.

Guest dibbles
Posted

Because CM7 is not giving this info to the phone.

This should be fixed by adding this info into its build.prop, I tried but no luck.

I just flashed Elitemovil and it presented me the current baseband.

Did you install his latest Z3 ROM...? If so, as I can't read the thread, what do you need to do in the way of caches on the SD card to prepare the installation..?

Does it run ok and is it rooted..?

Thanks

Posted

Did you install his latest Z3 ROM...? If so, as I can't read the thread, what do you need to do in the way of caches on the SD card to prepare the installation..?

Does it run ok and is it rooted..?

Thanks

I didn't need to do anything, just a normal flash through cwr.

Guest dibbles
Posted (edited)

Well I decided to create a EXT 3 partition through CWM and then a 256mb cache, again through CWM.

It worked a treat and now through the GUI of ASD2 I see that it is using the cache over on the SD card.

The ROM's really good and I have never had so much room for my apps etc.

I figured out that was advised and so did accordingly.

Edited by dibbles
Guest trueno2k
Posted

Because CM7 is not giving this info to the phone.

This should be fixed by adding this info into its build.prop, I tried but no luck.

I just flashed Elitemovil and it presented me the current baseband.

Okay, thanks for the information... I also tried adding the baseband code line (ro.build.baseband_version=P743B01) back into the build.prop file and rebooted but, I still also get unknown baseband... Was this line of code removed intended?... How might Z3 Elitemovil be able to show this and not CM7.1?

Guest trueno2k
Posted

Okay, thanks for the information... I also tried adding the baseband code line (ro.build.baseband_version=P743B01) back into the build.prop file and rebooted but, I still also get unknown baseband... Was this line of code removed intended?... How might Z3 Elitemovil be able to show this and not CM7.1?

Sorry for double posting but have we got anywhere with this situation?... I would like to know why this is happening and how it affects the phone, please :P ??? :D

Posted

Sorry for double posting but have we got anywhere with this situation?... I would like to know why this is happening and how it affects the phone, please :P ??? :D

Well I didn't bother anymore with this, but the appropriate person to answer this would be Lalit...

From what I've been reading and searching it seems to be a common issue on some CM7's...

Guest tilal6991
Posted

Well I'm not really sure why it doesn't work but ill check.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.