Develop Bugs

Cant install CM11

I was on CM10 and noticed that OTA CM updates no longer work. So as usual, I installed the latest TWRP, downloaded the latest CM11 nightly and proceeded to install. Every time I get an error.. something about bootloader. There is no need for me to update my bootloader because I already have the correct one. I checked.
I thought maybe the problem is TWRP and tried Clockwork. Same error. assert failed: getprop("ro.bootloader")... and then it lists differnt I747 models... then gives (Status 7) on the bottom
Why cant I update to CM11?
Thanks.
If it helps my bootloader is I747UCDLK3.

I was about to ask this same question. I am unable to flash any 4.4 rom... Am currently using task AOKP 10/31 and wanted to try kit kat.
Every 4.4 rom has failed to flash. I tried flashing the new modem in the cm thread as well... What am I missing?
Sent from my SGH-I747 using xda app-developers app

Try installing with CWM and check the CM11 updater script to make sure your bootloader is supported.

You need to make sure that your exact bootloader is listed in the asserts or it will error out... If your bootloader is not listed, then you need to upgrade to a bootloader that is in the list.. one compatable with your model... recommend only upgrading as far as you need to... careful with some of the latest bootloaders as they will brick your phone if you later try to downgrade...

I believe you need to update your bootloader for a KitKat ROM. Look for I747UCDMG2.

I figured it out. I updated to the latest cwm version and everything worked fine. Running liquid smooth now.
Sent from my SGH-I747 using xda app-developers app

[Q] Zip Install Error- this package is for "d2att" devices this is a "

Can't seem to find an answer to my question, and I've been at this since 9:00 this morning.
Tried to OTA 4.4 update my AT&T SGS3 last night, and the update soft bricked the phone. Initially I could get it to the spinning Death Star logo, but would freeze up at that point. After hours of trying almost anything, I installed clockwork custom recovery. Had it wipe all data, and now it hangs at the Samsung Galaxy SIII boot screen. Trying to install Cyanogenmod from sideload (since I can't get a 4.3 ROM to work because Kies won't recognize the device), but that errors off telling me "assert failed: getprop ("ro.product.device"). I followed the suggestion to remove the first line from the updater-script file, but now I just get "assert failed: getprop ("ro bootloader") for multiple bootloaders. When I tried to load an updated bootloader, I get the above error, which shows no device (it just says "this is a " and leaves it at that).
I've tried multiple bootloaders and multiple Cyanogen packages (both stable and nightly). What am I missing? Or am I out of luck? Any help is appreciated.

I'm assuming you are on 4.3 since you tried to update via Ota. Try flashing this from recovery. 4.3 custom stock rom I found in development section.
https://www.androidfilehost.com/?fid=23212708291681250
Or verify your current firmware build using adb or the built in terminal emulator in recovery.
Enter this:
getprop ro.bootloader
If it returns a 4.3 build you can flash the MJB firmware found in the general section. Flash with Odin.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

[Q] Soft bricked, No recovery and Odin fails?

So I had CM11 working flawlessly on my phone but I was going to switch to T-Mobile and the phone can't be unlocked from AT&T unless it's a stock rom. So last night I looked up how to flash it back to stock through Odin and that failed (Loading I747UCDLK3) so then I followed a method posted by Mrhayley30705 (http://forum.xda-developers.com/showpost.php?p=46954804&postcount=119) and that still didn't work. Now I'm stuck at a firmware screen that tells me the firmware upgrade encountered an issue. Kies doesn't do anything for me and when I try to use heimdall to re-flash the recovery.img it tells me "ERROR: Failed to access device. libusb error: -12".
I spent about four hours reading and looking different things up but I can't find anything. I don't care about any of the warranty counts or data stored on the phone I just need it back up and running, either stock or CM11 like I had. I can still access the download mode. I would really appreciate any help!

Can you boot into download mode and have access to a Windows machine? If you do, use Odin to flash Philz Touch for the d2lte and see if you can boot into recovery. If you can boot into recovery, copy CM11 back onto your phone to make sure if can boot to the phone's desktop and get a signal.
Once that works, try this thread to flash back to stock 4.3 (assuming you never had stock 4.4 on your phone): http://forum.xda-developers.com/showthread.php?t=2540998

I just got to class but I will try this when I get home and let you know the results!

Okay so I managed to get Philz on there, got into recovery and did a reset/wipe, reinstalled CM and I'm up and running but I've got no service. I appreciate the help so far!! This is great!
Okay so upgrading to the CM nightly I was using prior to this it restored basically everything except the IMEI which is preventing me from getting service.

So the digitizer works? What is the baseband on your phone? Do you have an imei #?

audit13 said:
So the digitizer works? What is the baseband on your phone? Do you have an imei #?
Click to expand...
Click to collapse
Phone works fine from what I can tell, outside of not getting a signal it's back to the way it was before I even started playing with it. Baseband is Unknown and my IMEI # is blank.
http://forum.xda-developers.com/showthread.php?t=1784877 I was going to test that, will that help?
Lesson learned, don't mess around with this stuff unless I learn more about it..

The link is not for the ATT s3, it is for the T-mobile version so I would not follow that guide.
Try flashing an older version of CM like 10.2. If you still don't have an imei or baseband, you may need to reflash the mjb bootloader and modem.

audit13 said:
The link is not for the ATT s3, it is for the T-mobile version so I would not follow that guide.
Try flashing an older version of CM like 10.2. If you still don't have an imei or baseband, you may need to reflash the mjb bootloader and modem.
Click to expand...
Click to collapse
I just tried to install 10.2 and it tells me it failed, (Status 7) it spammed a bunch of getprop("ro.bootloader") == I747(then a bunch of different letters for each one). I'm assuming that means I need to reflash the mjb bootloader and modem?

You may need to reflash to the mjb bootloader and modem in order to get your imei back.

Do you by chance have a link to the proper one that I need to install? The one I found shows 4.3 but says it will brick my phone if I'm trying to downgrade from 4.4.
It also seems I have no sound either.

Once you have a 4.4 bootloader on your phone, you cannot flash back to a 4.3 or 4.1 bootloader.
Do you have terminal emulator on your phone? If you do, run this in a terminal window: getprop ro.bootloader (you need the spaces and press enter).

audit13 said:
Once you have a 4.4 bootloader on your phone, you cannot flash back to a 4.3 or 4.1 bootloader.
Do you have terminal emulator on your phone? If you do, run this in a terminal window: getprop ro.bootloader (you need the spaces and press enter).
Click to expand...
Click to collapse
I747UCUFNE4 is the response it gave.

You have a 4.4 bootloader.
http://www.sammobile.com/2014/06/18...to-att-and-canadian-variants-of-galaxy-s-iii/
Did you try flashing a stock KK ROM?
http://forum.xda-developers.com/galaxy-s3-att/general/modem-4-4-2-modems-i747-i747m-t2856577

I didn't, I'll give that a try now!

It worked! Yaaaaaaaaaaaaaay. I love you!!

DextarRogue said:
It worked! Yaaaaaaaaaaaaaay. I love you!!
Click to expand...
Click to collapse
Excellent :highfive:
What did the trick? Updating the modem or flashing a new KK ROM?
It's important to share your knowledge with other XDA members.

So I followed the Philz recovery from Download mode through Odin, then through that recovery I installed CM11, booted the phone, upgraded to the newest CM nightly then I grabbed the modem, adb pushed it to the phone in recovery, installed the zip and boom! IMEI is back as is calling. Signal continues to be really low but it's always been like that!

Unable to flash CM 11 using TWRP

Hello
I am currently running the latest version of TWRP (openrecovery-twrp-2.8.1.0-d2att) and I am trying to flash CM 11, but I get an error in red "Failed"
I am even getting a failed error as well when flashing the bootloader in the thread below.
I have successfully been able to flash SlimKat 4.4.4 and Dirty Unicorn with no problems. I think I had the same problems as well when trying to flash Paranoid Android.
I have tried flashing the files from both the external SD card and Internal. No go.
This is the thread I am following: http://forum.xda-developers.com/showthread.php?t=2682905
Here is the error I get when flashing:
You cannot flash from your current bootloader. Current version: I747MVLUEFNE6
E: Error executing updater binary in zip '/external_sd/Flash/CM/1/boot_CWM_I747MVLUEMK5.zip'

Try using the latest version of Philz Touch for the d2lte to flash files.
You can flash the most recent zip from TWRP.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/

audit13 said:
Try using the latest version of Philz Touch for the d2lte to flash files.
You can flash the most recent zip from TWRP.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Click to expand...
Click to collapse
Ok, so I flashed the latest zip using the TWRP App rebooted into PhilZ Recovery and tried to flash the bootloader ( boot_CWM_I747MVLUEMK5.zip) from here: http://forum.xda-developers.com/showthread.php?t=2321310
Still got an error: Please upgrade to latest binary...You cannot flash from your current bootloader. Current version: I747MLUFNE6
E: Error in /storage/sdcard1/Flash/CM/1/boot_CWM_I747MVLUENK5.zip (Status 7) Installation aborted

Do not flash any bootloader to your phone. It is good that it did not flash mk5 over ne6. This will brick for phone.

audit13 said:
Do not flash any bootloader to your phone. It is good that it did not flash mk5 over ne6. This will brick for phone.
Click to expand...
Click to collapse
Ok thanks. Where can I find the latest boot-loader for my device? I was trying to follow this guide to flash CM11 and it told me to download the latest boot-loader and update it: http://forum.xda-developers.com/showthread.php?t=2682905
I guess the thread I wrote above is an outdated guide to flashing CM11. Would you happen to know the steps I should take to flash cm11 for my device with my current bootloader?
BTW I still can't flash the CM11 Rom in Philz Touch Recovery.

Iv never had any issues using philz touch to flash.

drakemiller40 said:
Ok thanks. Where can I find the latest boot-loader for my device? I was trying to follow this guide to flash CM11 and it told me to download the latest boot-loader and update it: http://forum.xda-developers.com/showthread.php?t=2682905
I guess the thread I wrote above is an outdated guide to flashing CM11. Would you happen to know the steps I should take to flash cm11 for my device with my current bootloader?
BTW I still can't flash the CM11 Rom in Philz Touch Recovery.
Click to expand...
Click to collapse
You have the ne6 bootloader. Do you have an i747m or i747? It will make a difference when it comes to flashing an updated bootloader and modem.
Are you downloading the latest CM11 from the cyanogen site?

audit13 said:
You have the ne6 bootloader. Do you have an i747m or i747? It will make a difference when it comes to flashing an updated bootloader and modem.
Are you downloading the latest CM11 from the cyanogen site?
Click to expand...
Click to collapse
Thanks for helping out so far. My Model number that shows up in "About Device" in my phone's settings say SGH-I747M. Yes I am downloading the latest CM11 Nightly build here : http://download.cyanogenmod.org/?device=d2lte
P.S.
Will I bay able to go back to stock if I don't like CM11? I heard that it will brick my phone from rolling back the boot loaders. What if I restore from a nandroid backup, will that work to restore to stock without bricking my device?

With a custom recovery, you can create a backup, flash your ROM, and you can restore the backup if you don't like cm11.

audit13 said:
With a custom recovery, you can create a backup, flash your ROM, and you can restore the backup if you don't like cm11.
Click to expand...
Click to collapse
Ok thats good. Though I still have the problem of flashing CM11. It still fails on me on TWRP or Philz Touch Recovery. Any ideas on how to fix this problem?

What error are you getting? What cm11 ROM are you flashing?

audit13 said:
What error are you getting? What cm11 ROM are you flashing?
Click to expand...
Click to collapse
Never mind, found out that I had to run the factory reset in PhilZ Touch first then flash the rom. Alls good, but didn't like CM11.
Though why didn't it work on TWRP?

I had issues with TWRP flashing ROMs too. Once I switched to Philz which is based on CWM, I had no issues flashing the same ROMs that TWRP would not flash.

I need to restore IMEI and baseband to original state ,SGH-I747

deal all
after fixing the hard bricked i found another problem there are no IMEI or baseband so i could not to mobile network
My phone is :-S3 SGH-I747 (Unlocked sim)
so how to solve this ,

restore imei and baseband
Well, I did a couple of weeks ago was to find a restoring image.
Here it is https://www.androidfilehost.com/?w=files&flid=21292 , here you can download the modem and image, flash both CWM! .
The files no are mine, just like I share the way I found it, good luck! Jeje sorry for my english, Greetings let me know if you could

Here is the modem, just flash with cwm, and download the ucu4_restore and the same, flash! Good luck

I ran through a recovery with the download you provided. Was working fine, then after the "preparing to Flash Baseband UCUFNE4" I got an error:
"assert failed: getprop("ro.bootloader") == "I747UCUFNE4"
E: Error in /data/media/ATT_GALAXYS3_UCUFNE4_Modem.zip
(Status 7)
Installation aborted."
Can someone please help me restore my IMEI and Baseband back onto my Galaxy S3. This almost worked, but then got the error.

vishulm said:
I ran through a recovery with the download you provided. Was working fine, then after the "preparing to Flash Baseband UCUFNE4" I got an error:
"assert failed: getprop("ro.bootloader") == "I747UCUFNE4"
E: Error in /data/media/ATT_GALAXYS3_UCUFNE4_Modem.zip
(Status 7)
Installation aborted."
Can someone please help me restore my IMEI and Baseband back onto my Galaxy S3. This almost worked, but then got the error.
Click to expand...
Click to collapse
Do you know what bootloader and modem you had on your phone prior to your problems? Knowing that is important for determining how to proceed. Samsung made this phone easy to brick messing with bootloaders or getting mismatched firmware.
You can install the Phone Info Samsung app by vndnguyen to get the bootloader and modem.
Or you can enter this in a terminal app or adb shell:
Code:
getprop ro.bootloader
getprop gsm.version.baseband

jason2678 said:
Do you know what bootloader and modem you had on your phone prior to your problems? Knowing that is important for determining how to proceed. Samsung made this phone easy to brick messing with bootloaders or getting mismatched firmware.
You can install the Phone Info Samsung app by vndnguyen to get the bootloader and modem.
Or you can enter this in a terminal app or adb shell:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
Click to expand...
Click to collapse
My bootloader was I747UCUFNJ2
PDA Version: I747ucdlk3
CSC Version I747ATTDLK3
IMEI and Baseband is missing/removed.
Does that help?

Go here
https://forum.xda-developers.com/ga...ile-sgh-i747ucufne4v4-4-2attall-odin-t3305899
and scroll down to the 3rd post where you can download the NE4 Odin files off chuckles google drive. Then go get a copy of Odin. You will be connecting your phone to your PC for this. This process will get your baseband back, but you will lose everything as flashing these files is like doing a factory data reset.
Yes I know you're on NJ1 or 2, but this will jump you back to NE4 and you can just use TWRP to get back to NJx if you want. Personally I have my s3 stuck on NE4 because it can use towel root.

vishulm said:
My bootloader was I747UCUFNJ2
PDA Version: I747ucdlk3
CSC Version I747ATTDLK3
IMEI and Baseband is missing/removed.
Does that help?
Click to expand...
Click to collapse
I agree with @StoneyJSG. That odin flashable full firmware update he linked is your best bet.
It will downgrade your bootloader to NE4 and match it up with the NE4 modem, but that has been proven safe. We used to think you couldn't downgrade this phone's bootloader at all after the MJB (jellybean I think) firmware, but it turns out once you're on a kitkat booloader (NE4, NJ1, NJ2) you can downgrade as long as you don't try to roll back to something earlier than kitkat.
I have successfully used that to downgrade from NJ1 to NE4 for a full phone restore, and others have reported rolling back from NJ2 in that thread.