As soon as I try to flash CM 10.2 to my phone I get this error assert failed getprop( ro.bootloader ) l710. Does anyone know how to fix this?
agonizing said:
As soon as I try to flash CM 10.2 to my phone I get this error assert failed getprop( ro.bootloader ) l710. Does anyone know how to fix this?
Click to expand...
Click to collapse
are you running the MD4 firmware?
(if you've taken the mk3 update, do not try to flash md4. you'll brick your phone)
jdelano said:
are you running the MD4 firmware?
(if you've taken the mk3 update, do not try to flash md4. you'll brick your phone)
Click to expand...
Click to collapse
MD4 should be a recognized bootloader in the updater-script for CM 10.2, which makes me think he probably has MK3. Removing the assert lines altogether will prevent an error involving the bootloader check, as long as it is a d2spr ROM (i.e. don't remove them from a ROM meant for a different carrier and then try to flash, bad things will happen, that is why the asserts are there in the first place). MK3 is included in the asserts for the new CM 11 builds by the way.
A point of clarification as well. Flashing is fine, there are no bootloader changes involved, it is when you try to push a .tar "return to stock" file via Odin which is designed to restore a non-Knox bootloader that causes major damage if you already have a phone cursed by the Knox bootloader. Therefore, if you are already OTA'd to the MK3 with Knox bootloader, DO NOT, under any circumstances, push a .tar that is based on the MD4 bootloader.
Mr. Struck said:
MD4 should be a recognized bootloader in the updater-script for CM 10.2, which makes me think he probably has MK3. Removing the assert lines altogether will prevent an error involving the bootloader check, as long as it is a d2spr ROM (i.e. don't remove them from a ROM meant for a different carrier and then try to flash, bad things will happen, that is why the asserts are there in the first place). MK3 is included in the asserts for the new CM 11 builds by the way.
A point of clarification as well. Flashing is fine, there are no bootloader changes involved, it is when you try to push a .tar "return to stock" file via Odin which is designed to restore a non-Knox bootloader that causes major damage if you already have a phone cursed by the Knox bootloader. Therefore, if you are already OTA'd to the MK3 with Knox bootloader, DO NOT, under any circumstances, push a .tar that is based on the MD4 bootloader.
Click to expand...
Click to collapse
I'm a newbie at this kind of stuff but yes i do have mk3. So can i not flash to cm 10.2? Or what do I have to do to get the flash to work properly?
agonizing said:
I'm a newbie at this kind of stuff but yes i do have mk3. So can i not flash to cm 10.2? Or what do I have to do to get the flash to work properly?
Click to expand...
Click to collapse
Flashing 10.2 is perfectly fine, or any other custom ROM for that matter. Remember, Android build number has nothing to do with your boot loader version. I will post later for you a link to instructions on how to modify or delete the assert lines to enable flash of CM 10.2, or I would also recommend just go straight to CM 11 official version, your boot loader is recognized by the newest updater-script. Let me know your preference.
Mr. Struck said:
Flashing 10.2 is perfectly fine, or any other custom ROM for that matter. Remember, Android build number has nothing to do with your boot loader version. I will post later for you a link to instructions on how to modify or delete the assert lines to enable flash of CM 10.2, or I would also recommend just go straight to CM 11 official version, your boot loader is recognized by the newest updater-script. Let me know your preference.
Click to expand...
Click to collapse
I got CM 11 to work last night, but it was too unstable for me. I'd rather use CM 10.2 since its a stable version. So can you teach me how to remove the assert lines?
agonizing said:
I got CM 11 to work last night, but it was too unstable for me. I'd rather use CM 10.2 since its a stable version. So can you teach me how to remove the assert lines?
Click to expand...
Click to collapse
http://androidforums.com/virgin-mobile-galaxy-s3-all-things-root/791952-all-in-one-guide-modifying-custom-sprint-roms-virgin-mobile-use.html
This link is for a tutorial I posted on Android Forums for the use of my fellow Virgin Mobile users who want to use Sprint ROM's. Ignore the VM specific items; the principle, though is universal in terms of modifying or deleting the assert lines once you know where to look for them. I would recommend just deleting that set of lines altogether, but if you want to replace one the current Sprint bootloader is L710VPUCMK3. Previous version of MD4 is already listed in the asserts if that happens to be your bootloader for anyone else interested, which would mean no modification needed. Too bad about CM 11, I have been running it since the official versions started being built, and it is beyond awesome for me. Currently on the first build for 4.4.2 from 12/12, with the newest test build of dkp kernel from 12/13 as well, and everything works virtually flawlessly.
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.
I had my phone rooted before the update, but then I thought I'd try going without root once the update came out. But now I am rooted once again and running the "T999L 4.3 deodexed, Knox Free". But when I try to install cm (I tried 11 and 10.2), I either get the executing updater binary error, status 7 error, and when I removed the asserts, it just aborted installation. Any help or suggestions are greatly appreciated
Update your Recovery to the latest version.
Perseus71 said:
Update your Recovery to the latest version.
Click to expand...
Click to collapse
I did that, tried both CWM and TWRP and it's still aborting the flash. It seems like the only rom it's letting me install is the deodexed 4.3
Actually I had a issue a few days where I accidentally wiped my internal memory and that is why I installed te deodexed 4.3, could that be a reason why nothing is working properly (I'm able to make backups but not restore them and what I mentioned before in my fist post)? Should I install the original 4.3 (with knox and everything) to get my phone on the correct thing and then use the knox remover from the forum before trying again?
wanderingghost said:
I had my phone rooted before the update, but then I thought I'd try going without root once the update came out. But now I am rooted once again and running the "T999L 4.3 deodexed, Knox Free". But when I try to install cm (I tried 11 and 10.2), I either get the executing updater binary error, status 7 error, and when I removed the asserts, it just aborted installation. Any help or suggestions are greatly appreciated
Click to expand...
Click to collapse
Why dont you try this:
S3Rx 3.0
http://forum.xda-developers.com/showthread.php?t=2326763
Its basically the same thing, except its debloated with a few mods..
Just be sure you have the MK4 Modem..
if you have not updated the bootloader (DONT) It will trip your warranty counter..
Just be sure you flashed the MK4 Modem, then flash the 4.3 rom..
Also be sure to Flash the T999L Connectivity patch on top
with the Insecure Kernel.. If you dont flash the Kernel you will lose wifi connectivity..
Zaphodspeaks said:
Why dont you try this:
S3Rx 3.0
http://forum.xda-developers.com/showthread.php?t=2326763
Its basically the same thing, except its debloated with a few mods..
Just be sure you have the MK4 Modem..
if you have not updated the bootloader (DONT) It will trip your warranty counter..
Just be sure you flashed the MK4 Modem, then flash the 4.3 rom..
Also be sure to Flash the T999L Connectivity patch on top
with the Insecure Kernel.. If you dont flash the Kernel you will lose wifi connectivity..
Click to expand...
Click to collapse
Do I also flash the MD5 file that's right above the t999l data connectivity patch? On the download link it says t999 so I'm not sure
wanderingghost said:
Do I also flash the MD5 file that's right above the t999l data connectivity patch? On the download link it says t999 so I'm not sure
Click to expand...
Click to collapse
Yes.. Flash that (Its the ROM), then flash the Connectivity patch (its the T999L patch), then flash the insecure Kernel..
Zaphodspeaks said:
Yes.. Flash that (Its the ROM), then flash the Connectivity patch (its the T999L patch), then flash the insecure Kernel..
Click to expand...
Click to collapse
Oops, I somehow missed realizing that that was the rom and was downloading an older version of it that was lower down on the post. I got this rom to work, but I am still unable to install other custom roms. I really liked the CM11 (4.4) rom, but after updating to 4.3 (unrooted), I am unable to install anything but 4.3 roms so it seems. I did update to the latest version of twrp and I also tried cwm, but I'm still getting failure messages, any idea on how to fix that? Thanks for your help so far
wanderingghost said:
Oops, I somehow missed realizing that that was the rom and was downloading an older version of it that was lower down on the post. I got this rom to work, but I am still unable to install other custom roms. I really liked the CM11 (4.4) rom, but after updating to 4.3 (unrooted), I am unable to install anything but 4.3 roms so it seems. I did update to the latest version of twrp and I also tried cwm, but I'm still getting failure messages, any idea on how to fix that? Thanks for your help so far
Click to expand...
Click to collapse
To be honest there isnt much difference between 4.4 and 4.3.. other than ART..
I much rather stay on 4.3 because it has App Ops, where 4.4 had it removed..
I much rather have an AOSP rom rather than Touchwiz, but no other ROM i have found that is non Touch Wiz
that has Wifi Calling
Zaphodspeaks said:
To be honest there isnt much difference between 4.4 and 4.3.. other than ART..
I much rather stay on 4.3 because it has App Ops, where 4.4 had it removed..
I much rather have an AOSP rom rather than Touchwiz, but no other ROM i have found that is non Touch Wiz
that has Wifi Calling
Click to expand...
Click to collapse
True, but I guess my issue is that I can't install any of the CM roms, not even 10.2 which is based on 4.3. I just like CM because of the customization and the rom you linked me to has some of them, but not all. I've already tried unrooting and re-rooting, but that still did not help. Is there a different way you're supposed to root after the 4.3 update? I've always followed the instructions on DocHoliday's T999L/T999N thread and before 4.3, I was able to use twrp to flash t999 roms without removing asserts, but now even removing the asserts, I can't install any custom roms
wanderingghost said:
True, but I guess my issue is that I can't install any of the CM roms, not even 10.2 which is based on 4.3. I just like CM because of the customization and the rom you linked me to has some of them, but not all. I've already tried unrooting and re-rooting, but that still did not help. Is there a different way you're supposed to root after the 4.3 update? I've always followed the instructions on DocHoliday's T999L/T999N thread and before 4.3, I was able to use twrp to flash t999 roms without removing asserts, but now even removing the asserts, I can't install any custom roms
Click to expand...
Click to collapse
I have been able to install a couple of CM 10.2 Roms.. Not sure what ones I flashed, because I couldnt connect my phone to my PC via USB..
the phone started to act a bit bazaar.. So I reverted to something I knew..
Zaphodspeaks said:
I have been able to install a couple of CM 10.2 Roms.. Not sure what ones I flashed, because I couldn't connect my phone to my PC via USB..
the phone started to act a bit bazaar.. So I reverted to something I knew..
Click to expand...
Click to collapse
Different CM 10.2 roms as in stable, rc, nightly? I tried the stable version earlier and still no luck. I'm kind of starting to give up on it because I'm just getting frustrated lol
wanderingghost said:
Different CM 10.2 roms as in stable, rc, nightly? I tried the stable version earlier and still no luck. I'm kind of starting to give up on it because I'm just getting frustrated lol
Click to expand...
Click to collapse
Im pretty new to this area myself.. I've had a few trial and error issues..
Flashing Nexus devices is far to easy compared to this.. But since they have no Micro SDcard reader..
I'll never own a Nexus phone..
This is the first phone I've rooted, I didn't have problems until after 4.3. But would you happen to know where I can find instructions on how to unroot this device? I was going to try to find an 100% 4.3 stock rom, unroot, and then try this (http://forum.xda-developers.com/showthread.php?t=2563955) to see if it would work and if it didn't, then I'll just leave my phone unrooted. But I can't find any instructions anywhere, the only one's I can find are DocHoliday's but that's to return to stock 4.1.2
Never mind, I figured out
With Odin is it safe to apply updated boot loader on top of the old one
Good thread here: http://forum.xda-developers.com/showthread.php?t=2321310
Its been so long since I did my phone, when I click on PDA its browsing for a file. Which file do I use? Also any ideas on why my play store won't work. I have read about going to download manager and enabling it but there is no enable button. Any other ideas? I have a att galaxy s3. Thanks
What bootloader is currently on your phone? Any particular reason you need to update the bootloader?
Let me start at beginning. I am running task650, android v. 4.2.2. My inbound text just stopped coming thru. Art said everything was fine on their end so figured it was time for new ROM. I have twrp 2.5.0.0. I want to put the kit kat ROM on. I have the ROM downloaded. I am trying to update my boot loader, correct?? When I open Odin and click on Odin, then PDA, it wants to browse for a file that is where I don't know what to do. By the way thanks for the help
You cannot use Odin to flash a custom ROM. You must have a custom recovery installed. You must also be running the most current recovery to flash KK ROMs. Did you look at the ROM's updater script to see what bootloaders are supported?
Thanks audit, I guess I need to do some more reading.
Is there a thread out there to walk me thru step by step to apply kit kat
The easiest thing to do would be to update your TWRP to the latest and try flashing a KK ROM you like.
If the ROM is not supported you will receieve an assert error and the installation will stop. I suggest you start with that before attempting to update the bootloader and modem.
Updating a bootloader and modem can cause endless headaches unless you really understand how to deal with issues that may appear. Maybe some custom KK ROMs will run on JB bootloaders and modems.
Can you take a look at my latest post in this section and see if you can tell me my next step. Thanks Audit
Do you have a link to the Kit Kat ROM you want to install?
What is the baseband on your phone?
These are two important things to know before flashing or changing anything.
not to be buttin in audit/tepee , but i was on mj2 bootloader and modem and never had an issue flashing KK ROMs. the only issue that i've read about is no wifi (on touchwiz ) which was fixed by flashing ktoonsez's kernel.
(FINALLY bit the bullet and updated bootloader/modem and have issues with non-unified builds)(and that SMALL issue of no-going-back) lol.
just my two cents.
err on the side of kindness
mrrocketdog said:
not to be buttin in audit/tepee , but i was on mj2 bootloader and modem and never had an issue flashing KK ROMs. the only issue that i've read about is no wifi (on touchwiz ) which was fixed by flashing ktoonsez's kernel.
(FINALLY bit the bullet and updated bootloader/modem and have issues with non-unified builds)(and that SMALL issue of no-going-back) lol.
just my two cents.
err on the side of kindness
Click to expand...
Click to collapse
Very true.. If the updater script supports the phone's bootloader, no need to update it.
I am trying to update my SGH-i747M to run CyanogeMod. I have done this before on my Galaxy S2, so I am somewhat familiar with what I am doing, but am now stuck with a bootloader issue.
My CM Rom, GApps, are allready on the phones SD Card. I have installed CWM Recovery. I have backed up, and wiped the phone.
I am following these instructions:
http://wiki.cyanogenmod.org/w/Install_CM_for_d2att
There is a massive warning:
"CM10.1 and newer are not compatible with ICS bootloaders on this device. Update your device's firmware or you will get assert failures in recovery."
This is where I am stuck. Before I started this process, I let the phone on stock rom perform its latest software update.
When trying to install CM-11 I get assert failures. I can see from the script that I747MVLUEMK5 is supported by CM11. I assume this is due to bootloader. My current version is I747MVLUFNE6. I downloaded I747MVLUEMK5 and tried to install. I get the error "You cannot flash from your current bootloader.Current Version: I747MVLUFNE6"
I researched this thread:
http://forum.xda-developers.com/showthread.php?t=2321310&page=25
I figured I would try to dowload the second most recent version I747MVLDMF1 as I can see from the CM11 failure script that it is also supported. I cannot find it anywhere available for download. No download links I have found work.
I am stuck and do not know how to proceed. I thought this was going to be easy, and I am at the stage where I literally just install CM11, but cannot proceed. Please help.
Do not attempt to flash i747 modems and bootloaders onto the i747m and vice versa as this could brick your phone.
I recommend flashing the latest stock i747 rom from sammobile, flash the latest Philz, and then cm11.
Is there any reason to upgrade bootloader to anything newer that mk5? I have an i747m (Bell) with mk5 bootloader and modem that I have been running CM11 on for a long time. I am now running CM12 (actually CyanideL), and everything seems fine. Should I upgrade either my modem or bootloader? If so, to what?
Some of the newer ROMs require an up-to-date bootloader and modem.
If everything is working, no need to update in my opinion. If you decide to update, the safest way would be to flash back to completely stock, take the OTA updates until you are running the latest stock ROM.
audit13 said:
Some of the newer ROMs require an up-to-date bootloader and modem.
If everything is working, no need to update in my opinion. If you decide to update, the safest way would be to flash back to completely stock, take the OTA updates until you are running the latest stock ROM.
Click to expand...
Click to collapse
How do I know if a ROM requires a higher bootloader and/or modem? Will it refuse to install/run?
Do more recent bootloaders fix bugs, improve effiencies or reduce battery drain, or any other tangible thing?
huladaddy said:
How do I know if a ROM requires a higher bootloader and/or modem? Will it refuse to install/run?
Do more recent bootloaders fix bugs, improve effiencies or reduce battery drain, or any other tangible thing?
Click to expand...
Click to collapse
i upgraded from mj2 to ne4 and did not not notice any difference.
usually the OP will state if needs a higher version bootloader/modem.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Newer isn't always better for some.
If you want to know if a particular ROM will run on your bootloader, you can either try to load the ROM or you can look at the ROM's updater script to see which bootloaders are supported.
Hello,
Trying to install the custom ROM cyanogen mod 11.
http://forum.xda-developers.com/showthread.php?t=2682905
First time I ever attempt to flash a custom rom.
In the guide it asks to DL Bootloader & Modem. My baseband is:
I747MVLUFOB3
I can't find any baseband corresponding to this one.
Here I found a firmware that correspond to my base band.
http://www.sammobile.com/firmwares/database/SGH-I747M/
Not sure if it is useful...
Any way to install the custom room??
Cheers
Just a nickname said:
Hello,
Trying to install the custom ROM cyanogen mod 11.
http://forum.xda-developers.com/showthread.php?t=2682905
First time I ever attempt to flash a custom rom.
In the guide it asks to DL Bootloader & Modem. My baseband is:
I747MVLUFOB3
I can't find any baseband corresponding to this one.
Here I found a firmware that correspond to my base band.
http://www.sammobile.com/firmwares/database/SGH-I747M/
Not sure if it is useful...
Any way to install the custom room??
Cheers
Click to expand...
Click to collapse
Which variant of the galaxy s3 do you have? You should be able to flash any ROM compatible with your phone using TWRP or Phil touch recovery.
I have the i747m (rogers canada). I have TWRP 2.8.7.0 & rooted with Kingo root. Somehow it was the only way to root it. Tried Towel root & odin but both were doing nothing.
TWRP was installed a long time ago. I recently made an update on kies (what a mistake sign...). I was on 4.4.2 before and after the firmware update on kies.
I got a spare S3 motherboard (with cpu etc.) I might try on that one first but I need to disassemble & assemble everything... not very tempting.
I usually just use odin and http://www.sammobile.com/firmwares/ to start fresh and root again when I want to upgrade bootloader and modems.
As you saw at sammobile, OB3 is the latest official release for the i747. You do not need to do anything to your baseband (modem) to run CM11. You may want to verify that your bootloader (firmware) matches the modem. This can be done from within TWRP. Go to the advanced menu and in the terminal enter
Code:
getprop ro.bootloader
You should get a return ending in OB3.
I suspect the CM 11 updater-script has not been updated to account for the just released OB3 firmware. If that is the case, you could always edit the script in the roms zip file.
@dawgdoc
When I entered the command, it returned me:
I747MVLUFOB3
Secondly, I have not tried to install CM11 (or the newer version CM12?). I do not know if it works. I just want to make sure I can flash and not brick my phone.
My phone is not the d2att (i747), it is d2can (i747m). I believe these two are very similar but enough different to cause problem.
So, can I install CM11 or 12?
You are talking about changing a zip file... The newb I am know how to do that, but what exactly - that he doesn't know. So I would rather not mess with that. I guess TWRP checks if the firmware of the bootloader / modem matches to those from a compatible list and simply updating that list would allow me to install the build?
I was thinking about this ROM:
http://forum.xda-developers.com/galaxy-s3-att/development/unofficial-cyanogenmod-12-t2968854
Don't know the exact difference with the CM12 but it says d2can.
However, the BaNkS GAPPS - GAPPS link does not work... I don't know what that is.
Just a nickname said:
@dawgdoc
When I entered the command, it returned me:
I747MVLUFOB3
Secondly, I have not tried to install CM11 (or the newer version CM12?). I do not know if it works. I just want to make sure I can flash and not brick my phone.
My phone is not the d2att (i747), it is d2can (i747m). I believe these two are very similar but enough different to cause problem.
So, can I install CM11 or 12?
You are talking about changing a zip file... The newb I am know how to do that, but what exactly - that he doesn't know. So I would rather not mess with that. I guess TWRP checks if the firmware of the bootloader / modem matches to those from a compatible list and simply updating that list would allow me to install the build?
I was thinking about this ROM:
http://forum.xda-developers.com/galaxy-s3-att/development/unofficial-cyanogenmod-12-t2968854
Don't know the exact difference with the CM12 but it says d2can.
However, the BaNkS GAPPS - GAPPS link does not work... I don't know what that is.
Click to expand...
Click to collapse
The unofficial CM12 -5.1.1 by @matrixzone is good for the i747M, aka d2can. If you have any doubts, ask on that thread if it is updated to run on OB3? Matrixzone is active on the forums and should respond to your question. Also I just checked the updater-script for the latest CM11 official nightly and it is set up to run on the i747M.
So, either should run with no problems for you.
What is the bootloader and modem version needed and how do I get them without getting a locked bootloader? I'm on i747M with 4.1.1 Stock rom with DLK4 modem and bootloader. There are newer bootloaders and modems that can be flashed through recovery but some people have been getting bricks when messing with bootloader.
THey say to use Official firmwares to have it update the bootloaders but which one is the proper firmware version to get the proper bootloader and modem version to allow DATA 4g LTE after flashing CM12.1 Lollipop rom?
Chupacabra117 said:
What is the bootloader and modem version needed and how do I get them without getting a locked bootloader? I'm on i747M with 4.1.1 Stock rom with DLK4 modem and bootloader. There are newer bootloaders and modems that can be flashed through recovery but some people have been getting bricks when messing with bootloader.
THey say to use Official firmwares to have it update the bootloaders but which one is the proper firmware version to get the proper bootloader and modem version to allow DATA 4g LTE after flashing CM12.1 Lollipop rom?
Click to expand...
Click to collapse
I see audit13 is helping you in the other thread, therefore I will not confuse things and also reply here.
dawgdoc said:
I see audit13 is helping you in the other thread, therefore I will not confuse things and also reply here.
Click to expand...
Click to collapse
But the newest firmware is bad because it has evil bootloader.
Chupacabra117 said:
But the newest firmware is bad because it has evil bootloader.
Click to expand...
Click to collapse
Check my long post over there.