I am trying to flash GS3 (Canadian Rogers unlocked) i747m with cm10.2 d2att from SD through Philz Touch, but my install fails half thru "Installation aborted, please update binary"
I made 2 backups to SD card, so I easily recovered back, but trying to understand what has happened, first time doing it, and I am not sure why. Please help.
Model: SGH-I747M
Android: 4.4.2
Baseband: I747MVLUFNF2
Kernel: 3.4.0-1784548
Build: KOT49H.I747MVLUFNF2
Any particular reason you want cm10.2? Since you are on a KK bootloader and modem, I would go with a cm11 install for the d2lte.
Is your recovery up to date?
audit13 said:
Any particular reason you want cm10.2? Since you are on a KK bootloader and modem, I would go with a cm11 install for the d2lte.
Is your recovery up to date?
Click to expand...
Click to collapse
Only reason was that 10.2 is stable release and I wasn't sure if cm11 is compatible with my bootloader.
Philz Touch 6 Recovery , I believe was the last build for d2lte I found.
Philz Touch 6.48.4 ClockworkMod v6.0.5.0
Not sure why you're getting that error. CM10.2 is basically JB while CM11 is KK.
I suggest trying CM11.
audit13 said:
Not sure why you're getting that error. CM10.2 is basically JB while CM11 is KK.
I suggest trying CM11.
Click to expand...
Click to collapse
Thanks,
I tried cm11 and install was flawless.
Related
Hi Guys,
I am asking this question after 3-4 days of searching on XDA... here it goes....
I updated my T999 via kies to 4.3 ... hate it, it has knox which doesn't let me root properly. I tried going back to previous android versions, tried with odin but its not letting me, it gets FAIL error . Tried to install a custom rom " liquid smooth" get error 7" . Seems like I cannot flash anything .....
Long story short, if there is any way to flash a custom rom "i.e. liquidsmooth" on my SGH-T999 which is on Official firmware 4.3 - which has knox in it. I want custom rom without any knox in it.
Thanks in advance :good:
First you need to Root and install custom Recovery. Please get into Download mode and try to flash custom Recovery. If that succeeds then please flash ATT Insecure Kernel.
Perseus71 said:
First you need to Root and install custom Recovery. Please get into Download mode and try to flash custom Recovery. If that succeeds then please flash ATT Insecure Kernel.
Click to expand...
Click to collapse
Thanks:good:
Here is a noob question, will flashing an ATT insecure kernel would get rid of know, & then i can install any rom?
No it won't remove Knox. You need Knox Remover for that. The insecure Kernel only allows you to get stable Root.
Hi, Thanks a lot for your reply
As of now I have successfully removed Knox
However even now I cannot install a custom rom, first i got status 7 error, therefore i removed asserts from the rom but now I am getting error saying Installation Aborted, tried with both CWM and TWRP but error persists.. Any idea how to overcome it?
Thanks!
Perseus71 said:
No it won't remove Knox. You need Knox Remover for that. The insecure Kernel only allows you to get stable Root.
Click to expand...
Click to collapse
Please Specify your current State Bootloader, Recovery, Rom, Kernel.
What Rom are you trying to Flash ? Thread Link please.
Perseus71 said:
Please Specify your current State Bootloader, Recovery, Rom, Kernel.
What Rom are you trying to Flash ? Thread Link please.
Click to expand...
Click to collapse
Hi I am trying to flash liquidsmooth rom d2tmo version 2.39 and 2.37
Model - SGH- T999
Kernal Version : 3.0.31-1962493
[email protected]#1
Thu Oct 31 03:28:26 KST 2013
Build Number
JSS15J.T999UVUEMJC
I have TWRP recovery v 2.6.3.0
How can i get bootloader?
tshaikhonweb said:
Hi I am trying to flash liquidsmooth rom d2tmo version 2.39 and 2.37
Model - SGH- T999
Kernal Version : 3.0.31-1962493
[email protected]#1
Thu Oct 31 03:28:26 KST 2013
Build Number
JSS15J.T999UVUEMJC
I have TWRP recovery v 2.6.3.0
How can i get bootloader?
Click to expand...
Click to collapse
Use another Rom. Liquid had some issues with certain bootloaders.
To Get Bootloder, install GetProp from Play Store and look for ro.bootloader.
Perseus71 said:
Use another Rom. Liquid had some issues with certain bootloaders.
To Get Bootloder, install GetProp from Play Store and look for ro.bootloader.
Click to expand...
Click to collapse
Thanks so there is no way i can install liquidsmooth :crying:
what other rom would u recommend?
tshaikhonweb said:
Thanks so there is no way i can install liquidsmooth :crying:
what other rom would u recommend?
Click to expand...
Click to collapse
Please can you first update TWRP to 2.6.3.1 ? Then try Liquidsmooth again. If it fails, try Slim Bean 4.3
Perseus71 said:
Please can you first update TWRP to 2.6.3.1 ? Then try Liquidsmooth again. If it fails, try Slim Bean 4.3
Click to expand...
Click to collapse
Hi, I updated TWRP tried flasing rom, no vain,
reflash firmware, tried liquidsmooth 2.0 was stuck at liquid smooth logo for one hour, reflashed back to 4.3
:crying:
You can flash any 4.3 Rom. The new Bootloader will prevent you from flashing older Roms.
Any attempts to flash older bootloader will hard brick your phone.
Perseus71 said:
You can flash any 4.3 Rom. The new Bootloader will prevent you from flashing older Roms.
Any attempts to flash older bootloader will hard brick your phone.
Click to expand...
Click to collapse
This crap from Samsung is like they are following those Apple's restrictions. Damn Samsung!!! Lets all boycott them. Time to move to Windows phones.
Hello everyone,
I am looking for any assistance with my problem. I was running CM 10.2 without any issues. I installed CM 11 M2 and began having LTE issue where download/upload speed is under 1mbps. I have been attempting to upgrade to newer versions of CM 11, however I keep getting “Status 7 error”
In an attempt to correct the problem I have done all the steps listed below, none of which have worked.
updated CWM recovery to 6.0.4.7
Edited the “Updater-Script” located in META-INF/com/google/android
a. Deleted everything from assert to first semi colon
b. Replaced M3 assert with assert from CM 11 Snapshot M2 (which included my baseband version)
c. Inserted my baseband version into CM 11 M3
Used ‘Toggle signature verification”
Selected ‘Fix Permissions” in CWM
Attempted CM 11 Nightlies dated after M3
Question- I have read that some users have had success using TWRP instead of CWM. However CWM backups wont work with TWRP. Is it worth the effort to transition to using only TWRP? I am considering flashing back to CM 10.2, then using TWRP to create a back up and then flash CM 11 M3.
I am using CWM version 5.5.3.7
Using a rooted GS3 on ATT (I747)
Current OS- CM 11-20140104-SNAPSHOT-M2-d2att
Baseband version- I747UCDLK3
I originally followed instructions listed here to backup/ root and flash my ROM- http://forum.xda-developers.com/showthread.php?t=2179330
Thanks in advance for any feedback.
I was in a similiar situation and this did the trick: http://forum.xda-developers.com/showthread.php?t=2321310
FWIW I updated bootloader AND modem to achieve LTE stability in my old daily driver (Slim) and install a newer CM variant. I believe only the bootloader is actually needed to get past your Error 7 Assert Failed situation.
Ghostnyc said:
Hello everyone,
I am looking for any assistance with my problem. I was running CM 10.2 without any issues. I installed CM 11 M2 and began having LTE issue where download/upload speed is under 1mbps. I have been attempting to upgrade to newer versions of CM 11, however I keep getting “Status 7 error”
In an attempt to correct the problem I have done all the steps listed below, none of which have worked.
updated CWM recovery to 6.0.4.7
Edited the “Updater-Script” located in META-INF/com/google/android
a.Deleted everything from assert to first semi colon
b.Replaced M3 assert with assert from CM 11 Snapshot M2 (which included my baseband version)
c.Inserted my baseband version into CM 11 M3
Used ‘Toggle signature verification”
Selected ‘Fix Permissions” in CWM
Attempted CM 11 Nightlies dated after M3
Question- I have read that some users have had success using TWRP instead of CWM. However CWM backups wont work with TWRP. Is it worth the effort to transition to using only TWRP? I am considering flashing back to CM 10.2, then using TWRP to create a back up and then flash CM 11 M3.
I am using CWM version 5.5.3.7
Using a rooted GS3 on ATT (I747)
Current OS- CM 11-20140104-SNAPSHOT-M2-d2att
Baseband version- I747UCDLK3
I originally followed instructions listed here to backup/ root and flash my ROM- http://forum.xda-developers.com/showthread.php?t=2179330
Thanks in advance for any feedback.
Click to expand...
Click to collapse
You're on the lk3 bootloader and modem, you need newer bootloaders try the MJ2 bootloader and the MJB modem. Avoid the MJB bootloader until necessary once you flash it you're stuck forever without Odin.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
theramsey3 said:
You're on the lk3 bootloader and modem, you need newer bootloaders try the MJ2 bootloader and the MJB modem. Avoid the MJB bootloader until necessary once you flash it you're stuck forever without Odin.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the quick response
I'm a relative newbie at this, but after looking into the bootloader as per your suggestion I have 2 questions
In CM 11 M3 updater script- my bootloader is listed in the asserts. This means it is supported, correct?
You suggested updating to MJ2, however I only found MG2, is this an appropriate bootloader to use?
jasapper said:
I was in a similiar situation and this did the trick: http://forum.xda-developers.com/showthread.php?t=2321310
FWIW I updated bootloader AND modem to achieve LTE stability in my old daily driver (Slim) and install a newer CM variant. I believe only the bootloader is actually needed to get past your Error 7 Assert Failed situation.
Click to expand...
Click to collapse
Thanks this worked for me and I was able to updated to the latest nightly on my i747m
idzy said:
Thanks this worked for me and I was able to updated to the latest nightly on my i747m
Click to expand...
Click to collapse
I need some clarification before I proceed - do I reinstall LK3 or install the next one in line which would be MG2.zip?
Ghostnyc said:
I need some clarification before I proceed - do I reinstall LK3 or install the next one in line which would be MG2.zip?
Click to expand...
Click to collapse
Are you getting assert errors (error 7) while trying to flash a new rom ?? if so, look at the list that is shown in the error when you try to install. Only upgrade the bootloader as far as you need to get a good install... also be sure that the bootloader you flash (if needed) is for your model of phone. I747 = AT&T. I747M is Canadian (Telus, Bell, Rogers....) I recently had to upgrade my bootloader to install 3.3 Quantum rom... went with MF1 Canadian bootloader as MK5(newest) will not let you downgrade without bricking your phone.....
Try the MJ2 (leaked 4.3 bootloader with no knox and you can downgrade with desktop Odin to whatever you want) it might be in the bootloader thread if not it is in the development section just search for MJ2.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
theramsey3 said:
Try the MJ2 (leaked 4.3 bootloader with no knox and you can downgrade with desktop Odin to whatever you want) it might be in the bootloader thread if not it is in the development section just search for MJ2.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I finally got a moment to update my bootloader to MG2 and install CM11 M3 and both were done successfully. However I am still experiencing issue with LTE speeds crawling under 1mbps.
I have been researching this issue and on cyanogenmod forums someone mentioned that it could be a radio issue (RIL- Radio Interface Layer).
Does anyone have any thoughts or experience with this?
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.
Trying to install CM11, but so far I keep getting either a "Status 7" or aborted error message. I have tried many of the fixes, but so far no luck.. I think I created this issue when I upgraded to 4.4.2. I would be happy to go back to a stock version and then CM11, but I have not been able to do that either. Here is my current phone details:
Phone Model: Samsung Sgh--I747
Device Type: d2att
Product Name: d2uc
CSC: ATT
Product Code: SGH2I747MBBATT
Boot Loader: I747UCUFNJ1
Baseband Version: I747UCUFNE4
PDA Version: I747UCUFNE4
CSC Version: I747ATTFNE4
Build Version: K0T49H.I747UCUNE4 (I747UCUNE4)
Android Version: 4.4.2
Let me know if you need any other details. I originally followed this thread to get to where I am now:
http://forum.xda-developers.com/showthread.php?t=2789917
Robert
please quit trying to go back to stock if you are referring to bootloader.! you will most likely brick your device!!! STOP.
which recovery are you currently using ?
have you only tried flashing CM11?
err on the side of kindness
mrrocketdog said:
please quit trying to go back to stock if you are referring to bootloader.! you will most likely brick your device!!! STOP.
which recovery are you currently using ?
have you only tried flashing CM11?
Click to expand...
Click to collapse
I'm currently using philz_touch_6.15.4-d2att and have also tried current versions of CWM and Twrp with the same results. CM11 and CM10.2 were both tried as well as editing the updater-script in the Cm11 zip file and removing the "assert checks".
Robert
6.15.4 is too old to flash kk roms. Status 7 errors can be caused by an outdated recovery.
Try the latest fir the d2lte from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
audit13 said:
6.15.4 is too old to flash kk roms. Status 7 errors can be caused by an outdated recovery.
Try the latest fir the d2lte from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Click to expand...
Click to collapse
I did try the latest CWM and Twrp with the same results. I flashed AOKP just fine. Something strange about my phone. Maybe it has something to do with me replacing my motherboard recently? Relaced my Sgh-T999 with the Sgh-i747???
Anyways, it's back up and running
Thanks,
Robert
Hey everyone, I'm working on making my dad's phone usable again. He has an S3 that was previously mine that had been running custom roms and was rooted. My brother installed an OTA update that, while not hard bricking the phone (after fixing a soft brick), made cell service nonexistent.
Basically, my baseband, IMEI, network, and phone number all are unknown. In my brother's diagnosis, he tried replacing the rom (as it was originally soft bricked) , and I believe downgrading to 4.1.1 from 4.3. Right now it is running a 4.1.1 rom called The Devils Reject v7.
I've tried installing basebands, going back to stock (I'm not sure if I've been doing it right, though), and installing CM. Some problems I'm encountering are Status 7 errors when flashing stock Roms through the recovery, or for that matter, CM roms. It is definitely still rooted and I have Philz v. 6.0.7.
I really have no idea what to do, so if anyone has any ideas at all, I'd be very appreciative.
Thank you so much.
Status 7 errors can be caused by an outdated recovery.
The latest Philz can be found here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Before flashing any more basebands, flash philz, flash cm11, determine the bootloader on the phone, and flash a matching modem.
audit13 said:
Status 7 errors can be caused by an outdated recovery.
The latest Philz can be found here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Before flashing any more basebands, flash philz, flash cm11, determine the bootloader on the phone, and flash a matching modem.
Click to expand...
Click to collapse
Thank you so much for your input
Unfortunately, after flashing the latest Philz you linked to, I'm still encountering the Status 7 error when trying to flash CM11. I think the D2ATT one is correct, no?
You should be flashing ROMs and recoveries made for the d2lte.
Which Philz did you flash?
audit13 said:
You should be flashing ROMs and recoveries made for the d2lte.
Which Philz did you flash?
Click to expand...
Click to collapse
Oh wow, can't believe I was installing the wrong version. I tried the latest CM11 for the D2LTE model and am still seeing a status 7 error when flashing. I'm running the latest Philz for D2LTE also. Strange right?
Try flashing an leer version of cm10.2 or cm11.
audit13 said:
Try flashing an leer version of cm10.2 or cm11.
Click to expand...
Click to collapse
Some good news! After a "Clean for new rom install" option in Philz I was successfully able to install CM11 D2LTE. Still no baseband, IMEI, etc. Should I try to flash a modem now?
Flashed the 4.4 modem (UCUFNE4) and it seems to be working! Thanks so much for your help, seriously. I really, really appreciate it.
Awesome! Glad you got it all working.