Develop Bugs

[Q] New Bootloader

Hi guys,
I have looked at numerous threads and just can't find exactly what I need or maybe I'm too dumb/too much of a noob to understand what I need, I am on CM10.1 nightlies with CWM and I can no longer flash the nightlies. It gives me assert fail messages. After some digging, I think the problem is that I need to update the bootloader as they no longer support the ICS bootloader (I am assuming I am on ICS bootloader, how would I know?). But then I couldn't find the latest bootloader and how to install it. Is that even the problem? Any help is appreciated or even if you can point me to the right thread, that would be awesome. Thanks for the help.

jlor23 said:
Hi guys,
I have looked at numerous threads and just can't find exactly what I need or maybe I'm too dumb/too much of a noob to understand what I need, I am on CM10.1 nightlies with CWM and I can no longer flash the nightlies. It gives me assert fail messages. After some digging, I think the problem is that I need to update the bootloader as they no longer support the ICS bootloader (I am assuming I am on ICS bootloader, how would I know?). But then I couldn't find the latest bootloader and how to install it. Is that even the problem? Any help is appreciated or even if you can point me to the right thread, that would be awesome. Thanks for the help.
Click to expand...
Click to collapse
I'm not 100% sure what the problem is, but I'll take you through step-by-step of what I'd do if my phone were giving me this problem.
Double check the md5sums of the CM10.1 Nightly Zip: It doesn't seem like this is the problem, but it's always the first thing I check.
Update your modem/firmware/baseband: I know the most recent build of LiquidSmooth require you to be on baseband MD4. You can get it over on Freeza's thread. The file you're looking for is:
MD4 Firmware:
MD4 Firmware/modem/baseband update
MD5: EEEAFDBE59CF9C5B492B1A591EC92D02
Click to expand...
Click to collapse
All you have to do is wipe cache and dalvik cache and flash this Rom in your recovery. Reboot and now you're on MD4.
Update your Recovery: I normally run the latest and greatest TWRP, but others like the stability of some of the older builds. I'd flash the latest 2.5.0.0 TWRP from Naddict's thread.
Those would be the first three things I'd try.

topherk said:
I'm not 100% sure what the problem is, but I'll take you through step-by-step of what I'd do if my phone were giving me this problem.
Double check the md5sums of the CM10.1 Nightly Zip: It doesn't seem like this is the problem, but it's always the first thing I check.
Update your modem/firmware/baseband: I know the most recent build of LiquidSmooth require you to be on baseband MD4. You can get it over on Freeza's thread. The file you're looking for is:
All you have to do is wipe cache and dalvik cache and flash this Rom in your recovery. Reboot and now you're on MD4.
Update your Recovery: I normally run the latest and greatest TWRP, but others like the stability of some of the older builds. I'd flash the latest 2.5.0.0 TWRP from Naddict's thread.
Those would be the first three things I'd try.
Click to expand...
Click to collapse
Awesome! Your 2nd suggestion worked! I had tried your other 2 suggestion already with no luck but #2 was what I needed. Thanks so much!

topherk said:
I'm not 100% sure what the problem is, but I'll take you through step-by-step of what I'd do if my phone were giving me this problem.
Double check the md5sums of the CM10.1 Nightly Zip: It doesn't seem like this is the problem, but it's always the first thing I check.
Those would be the first three things I'd try.
Click to expand...
Click to collapse
Yes that most definitely was his problem, the new cm10.1 nightlies require the md4 firmware update because of the bootloader.
Sent from the future via Xparent Green Tapatalk 2

[Q] Can't flash CM 10.1

Whenever I try to flash it in TWRP, I get
updating partition details...
installing /sdcard/roms/cm-10.1.0-d2att.zip
checking for md5 file...
skipping md5check: no md5 file found
assert failed: getprop("ro.product.device") == "
E: error executing updater binary in zip "/sdcard/roms...
error flasing zip "sdcard/roms/cm10.1.0-d2att...
updating partition details...
YES, my bootloader is up to date according to http://forum.xda-developers.com/showpost.php?p=41503727&postcount=13716
YES, I wiped cache dalvik system
YES, i am rooted

Well, do you have the d2att or d2can s3? Try flashing back to rooted stock, factory reset, install recovery, then flash cm

It is because your recovery is saying you have a d2can recovery. Download Rom Manager from the market and flash the d2att recovery and then flashing it will not be an issue.

So I need CWM, not TWRP? Btw, I am sure that I got d2att cm.

mrhaley30705 said:
Well, do you have the d2att or d2can s3? Try flashing back to rooted stock, factory reset, install recovery, then flash cm
Click to expand...
Click to collapse
I have a Samsung Galaxy S3 I747M.
Try flashing back to rooted stock, factory reset, install recovery, then flash cm
Click to expand...
Click to collapse
Already tried that.

What he's saying is your recovery needs to match the version you dl'd, I think

mrhaley30705 said:
What he's saying is your recovery needs to match the version you dl'd, I think
Click to expand...
Click to collapse
Please provide me to the required links

Is it OK to install ATT CWM?

TimeAndroid said:
Is it OK to install ATT CWM?
Click to expand...
Click to collapse
Nvm, it worked. Please lock this thread!

could you tell me how that worked!!??

aleks1987 said:
could you tell me how that worked!!??
Click to expand...
Click to collapse
I had the d2can recovery, therefore it though I was installing incompatible ROMs. (d2att cm10.1). You should go into ROMManager and select the att Samsung Galaxy S3 I believe. Also, try updating your bootloader! Happy flashing, fellow Cyanogen-fanatic! ^_^

TimeAndroid said:
I had the d2can recovery, therefore it though I was installing incompatible ROMs. (d2att cm10.1). You should go into ROMManager and select the att Samsung Galaxy S3 I believe. Also, try updating your bootloader! Happy flashing, fellow Cyanogen-fanatic! ^_^
Click to expand...
Click to collapse
Ok thanks for the answer. I have a dout, i have i747m like you I think. I want to flash with d2att, Just Need the recovery for that rom?

You need root and recovery. If you have any problems, feel free to PM me.

Thanks let me try
Sent from my SGH-I747M using xda app-developers app

Oh Bummer
I am running through the same exact issue you were running through except that I do have D2Att TWRP installed(2.6.0.0 and it is verified for my S3). I have wiped it clean and downloaded the correct version of "cm-10.1.0-d2att.zip"
Any suggestions?

Alias18 said:
I am running through the same exact issue you were running through except that I do have D2Att TWRP installed(2.6.0.0 and it is verified for my S3). I have wiped it clean and downloaded the correct version of "cm-10.1.0-d2att.zip"
Any suggestions?
Click to expand...
Click to collapse
Not until we know what the error is.
Most likely out of date bootloader. Simple search will set you straight.
Sent from my SGH-I747 using xda app-developers app

Got it!
KorGuy123 said:
Not until we know what the error is.
Most likely out of date toothpaste. Simple search will set you straight.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Somehow my US-Att S3 had the Canadian boot loader (or a slightly corrupt, or an outdated bootloader<--most likely). So I found another guy with the same issue. I went to this thread and re-installed my bootloader through ODIN. Found newer versions of them from here:
http://forum.xda-developers.com/showpost.php?p=41503727&postcount=13716

Hey guys im still new to this but one thing i did figure out is i am on 4.1.2 (i assume you guys are too) and the bootloader seems to not be compatible with CM 10.1 and i am in the progress of flashing back to 4.1.1 for the old bootloader in hope that it will work ill keep updated!
***EDIT*** I just flashed back to 4.1.1 and low and behold cm 10.1.2 worked like a charm so i guess Alias18 method would be easier and quicker not sure if theres anymore risks that way though. if anyone would like the 4.1.1 firmware with root injected let me know.

[Q] Issue flashing from 4.2.2 to 4.3

Hello All,
I have been using Illusion 4.2.2 and want to go to 4.3.
I have been facing the following issues -
1) After upgrading to the latest cwm (6.0.3.8), I tried flashing PA 4.3. With a clean wipe and format system, it gave me a status 7 error (installation aborted).
One of XDA members redirected me to this - http://forum.xda-developers.com/showthread.php?t=2321310. I followed this and following is the screenshot of what I have after upgrading the bootloader : (Below jpg which says "Just after upgrading bootloader)
2) I could now flash the rom but when I rebooted after flashing , I don't have root access and neither do I see any att network / data . Following are the screenshots -
(Just after flashing 4.3 Page 1/2 and No root access after flashing 4.3).
ND

_ND_ said:
Hello All,
I have been using Illusion 4.2.2 and want to go to 4.3.
I have been facing the following issues -
1) After upgrading to the latest cwm (6.0.3.8), I tried flashing PA 4.3. With a clean wipe and format system, it gave me a status 7 error (installation aborted).
One of XDA members redirected me to this - http://forum.xda-developers.com/showthread.php?t=2321310. I followed this and following is the screenshot of what I have after upgrading the bootloader : (Below jpg which says "Just after upgrading bootloader)
2) I could now flash the rom but when I rebooted after flashing , I don't have root access and neither do I see any att network / data . Following are the screenshots -
(Just after flashing 4.3 Page 1/2 and No root access after flashing 4.3).
ND
Click to expand...
Click to collapse
Some roms you have to turn on root access; should be in the install post. Are you running the right rom for your device?

thepoetlives89 said:
Some roms you have to turn on root access; should be in the install post. Are you running the right rom for your device?
Click to expand...
Click to collapse
I eliminated that possibility because the same thing happened with two different roms (PA 4.3 and Illusion 4.3). I am on ATT and this phone is a ATT phone , and I am flashing all roms within this thread

_ND_ said:
I eliminated that possibility because the same thing happened with two different roms (PA 4.3 and Illusion 4.3). I am on ATT and this phone is a ATT phone , and I am flashing all roms within this thread
Click to expand...
Click to collapse
I know with illusion you have to ::Settings -> Developer options -> Root access to apps and/or adb. to get root access. Where are you getting basebands from? The latest is I747UCDMG2 but I747UCDLK3 should work too. Get them from HERE

thepoetlives89 said:
I know with illusion you have to ::Settings -> Developer options -> Root access to apps and/or adb. to get root access. Where are you getting basebands from? The latest is I747UCDMG2 but I747UCDLK3 should work too. Get them from HERE
Click to expand...
Click to collapse
I flashed the Illusion 4.3 again and then flashed baseband using the this link (through ODIN).. I still see an unknown baseband in the about and no mobile network (image attached)
The root access got sorted out , thought. thank you !

_ND_ said:
I flashed the Illusion 4.3 again and then flashed baseband using the this link (through ODIN).. I still see an unknown baseband in the about and no mobile network (image attached)
The root access got sorted out , thought. thank you !
Click to expand...
Click to collapse
some more research told me that I have lost my imei number. I remember taking a backup of my efs folder the first time I rooted my phone a year back. Can anyone help me restore my network using that backed up folder ?

_ND_ said:
I flashed the Illusion 4.3 again and then flashed baseband using the this link (through ODIN).. I still see an unknown baseband in the about and no mobile network (image attached)
The root access got sorted out , thought. thank you !
Click to expand...
Click to collapse
Baseband is Here. I would suggest MG2 baseband as it is more compatible with 4.3 than older than LK3. Get it from the link i just gave you and follow instructions on the page. Only use odin for reverting back to STOCK.

thepoetlives89 said:
Baseband is Here. I would suggest MG2 baseband as it is more compatible with 4.3 than older than LK3. Get it from the link i just gave you. ^^ and flash through recovery. Only use odin for reverting back to STOCK.
Click to expand...
Click to collapse
I tried the MG2 but the baseband still shows up as Unknown in About

_ND_ said:
I tried the MG2 but the baseband still shows up as Unknown in About
Click to expand...
Click to collapse
Huh thats weird. The only thing i can think of is something is wrong with the rom or you are flashing a non d2att rom.

thepoetlives89 said:
Huh thats weird. The only thing i can think of is something is wrong with the rom or you are flashing a non d2att rom.
Click to expand...
Click to collapse
I suspected that but since a lot of people are already using that rom and I made sure I am downloading d2att , those things are eliminated.
I am thinking the 4.3 flashing erased my previous efs folder and that is why it cannot find my imei number anymore - resulting in no network.

_ND_ said:
I suspected that but since a lot of people are already using that rom and I made sure I am downloading d2att , those things are eliminated.
I am thinking the 4.3 flashing erased my previous efs folder and that is why it cannot find my imei number anymore - resulting in no network.
Click to expand...
Click to collapse
When you get imei back i would suggest a nvbackup to make sure you keep a good backup of your imei.

thepoetlives89 said:
When you get imei back i would suggest a nvbackup to make sure you keep a good backup of your imei.
Click to expand...
Click to collapse
I had a nvbackup but since I flashed a different of baseband , I was not able to recover.
Anyways, I flashed stock through odin and looks like I have my network back.
Any recommendation of which 4.3 rom will not cause this again ? Anyone ?

try updating roms from ics up to 4.3and update modem and bootloader.

Unable To Update Cm 4.1.2 Assertion Errors

I'm trying to go from 4.1.2 to the next stable CM Rom.
My first attempt I received assertion errors. did some research on this and find it very confusing ie…. bootloader updates , remove assertion line in the installer script. I even went to CM and tried to use there updater and almost bricked my phone.
I have read the post by CM regarding the firmware change but haven't seen the fix yet or at least read somthing I trust on my own.
My Recovery is TWRP v2.6.3.1
Model # SGH-T999
Android Version 4.1.2
Baseband Version T999ULLJ4
Kernel Version: 3.0.48-cyanogenmod-ge67063c [email protected] #2 Tue Nov 13 23:04:58 PST 2012.
CPU ARM7 Processor rec0(7l)
Cyanogen Version 10-20121114-NIGHTLY-dt2tmo
Build Date: Tues Nov 13 23:02:54 PST 2012
Build Number: cm_d2tmo-userbug4.1.2JZO54K eng.20121113.230148.test-keys
Can someone point me in the right direction?
Thanks in advance..

Please use GetProp from Google Play. Find out the value for ro.bootloader. If it is not UVDMD5 or UVUEMJ4, (I suspect you have UVULLJ4) then flash this After the reboot, use Getprop again. This time you should see the value for ro.bootloader to be UVDMD5.
Once this is complete, proceed with the CM flash. Remove any asserts as you mentioned. If that's indeed CM for D2TMO (AKA SGH-T999) then you shouldn't have to make any assert changes.

modem upgrade UVULLJ4 to UVDMD5
Perseus71 said:
Please use GetProp from Google Play. Find out the value for ro.bootloader. If it is not UVDMD5 or UVUEMJ4, (I suspect you have UVULLJ4) then flash this After the reboot, use Getprop again. This time you should see the value for ro.bootloader to be UVDMD5.
Once this is complete, proceed with the CM flash. Remove any asserts as you mentioned. If that's indeed CM for D2TMO (AKA SGH-T999) then you shouldn't have to make any assert changes.
Click to expand...
Click to collapse
GetProp confirms it is currently UVULLJ4 and I will upgrade to UVDMD5 using T999_UVDMD5_firmware_v4.
Then flash :
cm-10.2.0-d2tmo.zip
gapps-jb-20130813-signed
superuser.zip
I hope this works and thank’s for your response….
Note: before I do this can I go back to my current image and reflash the UVULLJ4 modem ... just asking ???
also when I flash the modem should I proceed to the flashing the new rom or will 10-20121114-NIGHTLY-dt2tmo run on the UVDMD5 modem?

You don't have to flash superuser.zip. The CM Rom is Rooted. You just have to enable Root for Apps with the special steps. Its done that way to make it noob proof.
If you flash the Bootloader, Your modem will stay what it is at present. So you don't really have to re-flash it. But you can if you want. CM will work with either modem. You should choose a modem that gives you better signal. I'd reccomend UVDLJC modem as it has least signal problems.

resolved and thanks
Perseus71 said:
You don't have to flash superuser.zip. The CM Rom is Rooted. You just have to enable Root for Apps with the special steps. Its done that way to make it noob proof.
If you flash the Bootloader, Your modem will stay what it is at present. So you don't really have to re-flash it. But you can if you want. CM will work with either modem. You should choose a modem that gives you better signal. I'd reccomend UVDLJC modem as it has least signal problems.
Click to expand...
Click to collapse
I just want to say thank you Perseus71 & DocHoliday77 . you Perseus71 for responding to my questions and Doc for his threads and links to the info and software we need thanks again.
p.s. I am up in running and now looking at KiTKat . that brings a question can I now move to KitKat on my current modem I can repost my current config if you need it [ should be above ] Im running 10.2 stable with the UVDMD5 modem

mitboss said:
I just want to say thank you Perseus71 & DocHoliday77 . you Perseus71 for responding to my questions and Doc for his threads and links to the info and software we need thanks again.
p.s. I am up in running and now looking at KiTKat . that brings a question can I now move to KitKat on my current modem I can repost my current config if you need it [ should be above ] Im running 10.2 stable with the UVDMD5 modem
Click to expand...
Click to collapse
The MD5 you have on tends to give lots of wakelocks.. If you want try the UEMJ4 from @Docholiday's modem thread. If not go back to what you had. Your choice really.

UEMJ4 - Tried it
Perseus71 said:
The MD5 you have on tends to give lots of wakelocks.. If you want try the UEMJ4 from @Docholiday's modem thread. If not go back to what you had. Your choice really.
Click to expand...
Click to collapse
I tried UEMJ4 but speed test performance forced me to go to another Baseband Version T999ULLJ4.
This is the first one you recommend to me and it performs well for me so far
p.s. I've since moved on to CM 11 and have been going through nightly's
I'm currently running Cyanogen Version 10-20121117-NIGHTLY-dt2tmo,
I have worked through some issues ie... bluetooth error, occasional F/C... over all I'm quite pleased with the Nightly's :good:

Signal and data and failing

I loaded CM-13.0 nightly and have Been updating as the updates come but when I go to make a call it takes forever to go through and start ringing and sometimes it r just hangs up. The data keeps going from LTE to nothing and no SIM . I can't get mms either. Can someone tell me what to do.thanks.
Sent from my SGH-T999 using Tapatalk

HUCCG said:
I loaded CM-13.0 nightly and have Been updating as the updates come but when I go to make a call it takes forever to go through and start ringing and sometimes it r just hangs up. The data keeps going from LTE to nothing and no SIM . I can't get mms either. Can someone tell me what to do.thanks.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Same thing is happening to me. I've tried using OctOs M and now I am on PacRom 6.0.1 and I am having the same "No sim card" error. I can text and call, but no Data whatsoever.
Have you tried changing your APN settings for your network on your phone?

wmzed said:
Same thing is happening to me. I've tried using OctOs M and now I am on PacRom 6.0.1 and I am having the same "No sim card" error. I can text and call, but no Data whatsoever.
Have you tried changing your APN settings for your network on your phone?
Click to expand...
Click to collapse
are you on the latest baseband for your phone?

ratchetrizzo said:
are you on the latest baseband for your phone?
Click to expand...
Click to collapse
My stock OS Is 4.1.2 and is running Baseband UVAMB7. Do I need to go for the higher updates for the LTE to work?

wmzed said:
My stock OS Is 4.1.2 and is running Baseband UVAMB7. Do I need to go for the higher updates for the LTE to work?
Click to expand...
Click to collapse
I think you need to be on UVUBOH1.
https://forum.xda-developers.com/showthread.php?t=1949687 has the list of FW and it looks like you are using a super super old baseband.

ratchetrizzo said:
I think you need to be on UVUBOH1.
https://forum.xda-developers.com/showthread.php?t=1949687 has the list of FW and it looks like you are using a super super old baseband.
Click to expand...
Click to collapse
Do I need to use ODIN for this? I tried installing UVUBOH1 with TWRP, but I get an error when I installing it:
"could not find 'META-INF/com/google/android/update-binary' in the zip file"

wmzed said:
Do I need to use ODIN for this? I tried installing UVUBOH1 with TWRP, but I get an error when I installing it:
"could not find 'META-INF/com/google/android/update-binary' in the zip file"
Click to expand...
Click to collapse
Yes, download https://www.androidfilehost.com/?fid=24052804347821137
NOTE, if you click on "UVUBOH1" and not the androidfilehost link in the FW thread, it links you to the wrong FW and you'll flash UVUBNC1! Make sure you click the androidfilehost link underneath UVUB0H1.
Then flash it with odin.
Afterwards let it reboot and upgrade, then odin TWRP back and either restore a nandroid or flash the rom of your choosing
Oh also, if you're still on 4.1 and on a touchwiz rom, you may want to factory unlock it before you upgrade.. Just because you can. Follow the unlock thread on here

ratchetrizzo said:
Yes, download https://www.androidfilehost.com/?fid=24052804347821137
NOTE, if you click on "UVUBOH1" and not the androidfilehost link in the FW thread, it links you to the wrong FW and you'll flash UVUBNC1! Make sure you click the androidfilehost link underneath UVUB0H1.
Then flash it with odin.
Afterwards let it reboot and upgrade, then odin TWRP back and either restore a nandroid or flash the rom of your choosing
Oh also, if you're still on 4.1 and on a touchwiz rom, you may want to factory unlock it before you upgrade.. Just because you can. Follow the unlock thread on here
Click to expand...
Click to collapse
Thank you so much! I will try this out soon and respond with the results! And I had already unlocked my device :. I had to root and use the RegionLock app to unlock it, as the *#197328640# menu option did not work for me.

wmzed said:
Thank you so much! I will try this out soon and respond with the results! And I had already unlocked my device :. I had to root and use the RegionLock app to unlock it, as the *#197328640# menu option did not work for me.
Click to expand...
Click to collapse
how did you make out?

ratchetrizzo said:
how did you make out?
Click to expand...
Click to collapse
Was quite a bit of trouble at first . I managed to download and flash the software. flashed TWRP via odin.
Then through TWRP, I rooted by using the Knox remover zip (as i was on official 4.3, my service signal did shoot up to normal again!). Installed SuperSU.
Now when I try to flash any ROM via TWRP it gives errors such as "Status 7", or error reading MD5 when I try to backup software.

wmzed said:
Was quite a bit of trouble at first . I managed to download and flash the software. flashed TWRP via odin.
Then through TWRP, I rooted by using the Knox remover zip (as i was on official 4.3, my service signal did shoot up to normal again!). Installed SuperSU.
Now when I try to flash any ROM via TWRP it gives errors such as "Status 7", or error reading MD5 when I try to backup software.
Click to expand...
Click to collapse
Make sure twrp is up to date for d2tmo, and make sure the rom you are flashing is 4.3 or later. I'm pretty sure that once you're on the latest 4.3 rom you can't flash anything lower

ratchetrizzo said:
Make sure twrp is up to date for d2tmo, and make sure the rom you are flashing is 4.3 or later. I'm pretty sure that once you're on the latest 4.3 rom you can't flash anything lower
Click to expand...
Click to collapse
Got the latest TWRP running, but still the same issue trying to flash OctOS M, PACROM 5.0.1, etc.

wmzed said:
Got the latest TWRP running, but still the same issue trying to flash OctOS M, PACROM 5.0.1, etc.
Click to expand...
Click to collapse
That's strange, I'm using 3.0.2.0 and the latest 999L baseband and I haven't had any issues with flashing.
I'm Using the MM pac rom but I've tried CM14.1 nightly builds with no problem

ratchetrizzo said:
That's strange, I'm using 3.0.2.0 and the latest 999L baseband and I haven't had any issues with flashing.
I'm Using the MM pac rom but I've tried CM14.1 nightly builds with no problem
Click to expand...
Click to collapse
I have finally managed to figure it out. You need to completely format the entire ROM currently installed from your phone. Once that is done, you can add any ROM to install properly. I'm running well on OctOS-N 3/17/2017 build.
Thanks all for your help.