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.
Related
Hello!
I've been unable to flash any roms for at least a month because of this. Both TWRP and CWM fail to flash anything because of a error 7.
This is almost always caused by the first line in the META-INF/com/google/android/updaterscript. However, all of the roms are for the d2spr, and all of the updaterscript info is correct. In the phone, the buildprop correctly states the model as D2SPR and L710. So, I have no other ideas as to how to fix my phone. Please help.
Thanks in advance!
Have you updated to the latest bootloader and most current recovery?
hewey_mx5 said:
Have you updated to the latest bootloader and most current recovery?
Click to expand...
Click to collapse
To be honest, I've never updated my bootloader after unlocking it. How might a gentleman go about that?
Yeah that is probably your problem. Just go here : http://forum.xda-developers.com/showthread.php?t=1910947
In the first post, download the MD4 firmware. Boot into recovery, wipe cache and dalvik, then flash it just like a rom.
You can head over to freeza's stock rooted thread and grab the "MD4 Firmware" zip. The reason you are getting that error is because the updater-script checks to see if you are on the MD4 bootloader. If you are not, the flash fails because the newest CM builds require certain components for RIL that are only present in the MD4 firmware.
EDIT: Follow the link that was kindly posted above.
Hi everyone I flashed my GFs phone to I747UCDMG2 bootloader. Updated the TWRP to the latest via goomanager.
I get the following error when I try to install the zip. See the picture below, can someone help me? I am on Hypervision ROM RLS15
I suggest installing the latest Philz Touch Recovery via Odin.
audit13 said:
I suggest installing the latest Philz Touch Recovery via Odin.
Click to expand...
Click to collapse
this didn't help got the same error
Is it possible the device ID on the phone doesn't match the ROM? Have a look at the updater script in the ROM to make sure it matches the phone.
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.
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.
New Phone, Who dis?
Hello, Huskied here, And I am requesting help installing this Nougat safely on this Galaxy S4 on T-Mobile.
Keep in mind, This is still on 4.4.4 KitKat, Haven't installed an update just yet, unrooted, and it's a SGH-M919 type.
Build Number KTU84P .M919UVUFNH7
any help would be appreciated.
Here's what I would do:
Flash the latest stock ROM from Sammobile.com with Odin;
Flash twrp for the m919;
Save the rom and appropriate gapps to the phone's internal storage or sdcard; and
Flash the custom ROM, flash gapps, reboot.
audit13 said:
Here's what I would do:
Flash the latest stock ROM from Sammobile.com with Odin;
Flash twrp for the m919;
Save the rom and appropriate gapps to the phone's internal storage or sdcard; and
Flash the custom ROM, flash gapps, reboot.
Click to expand...
Click to collapse
Thank you. And one more thing, Some ROMs require LP Bootloader. Where can I get that?
Flashing the latest stock ROM will give you the latest bootloader.
audit13 said:
Flashing the latest stock ROM will give you the latest bootloader.
Click to expand...
Click to collapse
Tried today, Couldn't find any stock ROM for the jfltetmo. Found a bootloader that's supposed to boot the ROM I would like, Failed and could only boot into recovery until I restored 4.4.4.
Any thoughts?
If the phone baseband is running these latest fok3 ROM, that is the newest bootloader for the phone as indicated here: https://www.sammobile.com/firmwares/galaxy-s4/SGH-M919/TMB/
Btw, that nougat in the original is not for the m919 so don't flash it as it may hard brick phone.
audit13 said:
If the phone baseband is running these latest fok3 ROM, that is the newest bootloader for the phone as indicated here: https://www.sammobile.com/firmwares/galaxy-s4/SGH-M919/TMB/
Btw, that nougat in the original is not for the m919 so don't flash it as it may hard brick phone.
Click to expand...
Click to collapse
Rip, Thanks for the tip! and also the warning!