Database Users

[Firmware] Flashable JSS15R 3,15 Bootloader&Firmware update

For those of us who are rooted, don't want to update parts of the OS, who want to stay on an older versions of updated OS files, or just are on a custom ROM, here is a flashable of the firmware updates (which include bootloader).
This updates your bootloader to version 3.15.

Freeza, you rule... Just saying
Sent from my Nexus 7 using Tapatalk 4

Nice work!
Quick question for you, will the bootloader and firmware updates persist after custom ROM updates or will I need to reflash each time?
for example, I'm running CarbonRom at the moment which is based on JSS15Q - I've flashed this zip without any problems but will I need to reflash it when I install the next nightly?
Cheers
Macca

It will persist. No need to reflash.

sfhub said:
It will persist. No need to reflash.
Click to expand...
Click to collapse
Cheers, that's what I thought but there was no harm in checking

BigMacca said:
Cheers, that's what I thought but there was no harm in checking
Click to expand...
Click to collapse
I should be more clear, in the example you gave, it will persist, but if you do something that will flash the bootloader like factory restore or its updates, the bootloader could change

sfhub said:
I should be more clear, in the example you gave, it will persist, but if you do something that will flash the bootloader like factory restore or its updates, the bootloader could change
Click to expand...
Click to collapse
Yeah, I should have been clearer as well - I was basically checking that custom roms don't flash the bootloader (I'd assumed that a factory restore / ota update would)

Nice to see ya here Freeza!
I am currently on [JSS15Q] - CleanROM 1.6 I am wondering if this would work with my current rom as a dirty flash? anyone tired while on CleanRom 1.6?

DC_MTP said:
Nice to see ya here Freeza!
I am currently on [JSS15Q] - CleanROM 1.6 I am wondering if this would work with my current rom as a dirty flash? anyone tired while on CleanRom 1.6?
Click to expand...
Click to collapse
No problems here DC.
D

everything seems to be going well (using FLO Kangs cm10.2 Sep 5 build) will update if anything bad happens

Does firmware mean the audio driver, sensor driver, wifi driver etc?

bland.life said:
Does firmware mean the audio driver, sensor driver, wifi driver etc?
Click to expand...
Click to collapse
No, it means bootloader, resource power manager, trusted zone.

Quick queastion , I was on JSS15J when stock, flashed ROM that says now JLS36C. If I flash this will it erase everything and do I even need to? Thanks for the help.

It won't erase any user data. Whether you want to flash is up to you. You'll get it automatically if you wait for jls36g ota.

Why is the 3.15 bootloader not available as .img file in the google recovery as always? I normally flash bootloader ONLY by using fastboot?!

Awesome!
I flashed this and my dead gold fish came back to life!
You're the man, OP!

freeza said:
For those of us who are rooted, don't want to update parts of the OS, who want to stay on an older versions of updated OS files, or just are on a custom ROM, here is a flashable of the firmware updates (which include bootloader).
This updates your bootloader to version 3.15.
Click to expand...
Click to collapse
Will this work on stock? I can't get the ota to install.

Still JSS15Q after flashing?
freeza said:
For those of us who are rooted, don't want to update parts of the OS, who want to stay on an older versions of updated OS files, or just are on a custom ROM, here is a flashable of the firmware updates (which include bootloader).
This updates your bootloader to version 3.15.
Click to expand...
Click to collapse
After successful flashing this zip-file on my rooted JSS15Q version with TWRP the Android version is still JSS15Q. That's right? I expected JSS15R.
Greetings
Zorro16

relaxxer said:
Why is the 3.15 bootloader not available as .img file in the google recovery as always? I normally flash bootloader ONLY by using fastboot?!
Click to expand...
Click to collapse
If you want the 3.15 bootloader .img to flash in fastboot, I added it to the download section of this thread:
http://forum.xda-developers.com/showthread.php?t=2448015

Zorro16 said:
After successful flashing this zip-file on my rooted JSS15Q version with TWRP the Android version is still JSS15Q. That's right? I expected JSS15R.
Greetings
Zorro16
Click to expand...
Click to collapse
This is just the bootloader that came with 15R. If you want 15R, download and flash the full rom package.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Cannot install ROMs with CWM 2.5.1.8 or 2ndInit2.3

Hi,
This is the first time I've tried rooting a device so bare with me :good:.
It's taken me a few attempt to get things working on my Defy MB525 I've managed to root it with SuperOneClick and install either CWM 2.5.1.8 or SndInit2.3 (which uses CyanogenDefy Recovery v5.0.3.1). I'm now at a stumbling block where when I try to install a custom ROM on the device I keep getting...
"E:error in /sdcard/*ROM name*.zip
(status 0)
Installation Aborted"
Is there something I'm doing wrong or is it just the recovery programs I'm using?

What's the ROM you are trying to install?

themaker69 said:
What's the ROM you are trying to install?
Click to expand...
Click to collapse
I've tried a few now. The latest 4.4 alpha roms by Quarx, CM10 Android 4.1.2 also by Quarx and MokeeOS 43.1 and all come up with error.

Try to wipe the sdcard.

I'm downloading the file on a different computer as maybe the Antivirus on the work PC is messing it about. Also does the class of SDcard make a difference? It's only a class 4 8GB.

themaker69 said:
Try to wipe the sdcard.
Click to expand...
Click to collapse
Formatting it now.

novakanedj said:
I'm downloading the file on a different computer as maybe the Antivirus on the work PC is messing it about. Also does the class of SDcard make a difference? It's only a class 4 8GB.
Click to expand...
Click to collapse
No, the class has nothing to do. Use recovery to wipe, and not windows.

novakanedj said:
Hi,
This is the first time I've tried rooting a device so bare with me :good:.
It's taken me a few attempt to get things working on my Defy MB525 I've managed to root it with SuperOneClick and install either CWM 2.5.1.8 or SndInit2.3 (which uses CyanogenDefy Recovery v5.0.3.1). I'm now at a stumbling block where when I try to install a custom ROM on the device I keep getting...
"E:error in /sdcard/*ROM name*.zip
(status 0)
Installation Aborted"
Is there something I'm doing wrong or is it just the recovery programs I'm using?
Click to expand...
Click to collapse
4.1 should install. 4.3 and 4.4 need a newer recovery.
Sent from my Nexus 7 using Tapatalk

hotdog125 said:
4.1 should install. 4.3 and 4.4 need a newer recovery.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
novakanedj:
From 4.1 to 4.3 I installed using last TWRP. For 4.4 you need to use this.

hotdog125 said:
4.1 should install. 4.3 and 4.4 need a newer recovery.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Which recovery installs do the newer versions need and is there an install guide for these?

novakanedj said:
Which recovery installs do the newer versions need and is there an install guide for these?
Click to expand...
Click to collapse
For 4.3+ you need to first install 4.1/4.2 first to get the newer recovery.
Sent from my Nexus 7 using Tapatalk

Right I've just managed to get cm-10-20131030-NIGHTLY-mb526.zip to install from Quarx. Will let you know if the install is successful.:good: I would like to eventually install 4.4 KitKat when a more stable release is available.
edit: Succesfully installed . Just got to put Gapps on now.

Just install the zip from SDcard using your current custom recovery.

hotdog125 said:
For 4.3+ you need to first install 4.1/4.2 first to get the newer recovery.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I noticed that after I flashed with the 4.1.2 Quarx from there was a new bootloader on it. This should make it easier. I had to wipe and start again yesterday because I cocked up the Gapps install. In the end I went with the 30th Oct 2013 build of CM10 by Quarx and got the Gapps from www.goo.im/gapps. All seems to be running fine now and finished setting it up last night.
My girlfriend has a phone she can use now as her old one broke and she didn't want to use the Defy as the data couldn't be switched off on the stock ROM and would cost her a lot on her data plan (500MB a mth). Her Mum got a new contract with a Desire C so the Defy was going spare .

[Q] Difference between HLTE and HLTEXX?

My note 3 is from Vodafone Australia. the model number is SM-N9005. I always assumed it was one of the "International" one. Then i tried flashing the official cyanogen mod nightly for "International" which was called HLTEXX when i tried it it said your phone is an HLTE and not and HLTEXX.
What's the difference? Are there 2 kinds of international?

Wait for a dev to reply this properly, and this should be in the Q&A Section I assume,
Remove the device check in updater-binary, as I guess it means (hlte and xxx) the same device. Some have suggested to use TWRP Recovery as well. This is according to my understanding of the issue.

They are both different ways to say the same thing. Some places the n9005 is referred to as hlte and some places it's hltexx. Now as for why the roms don't flash and give that error, i am not sure. Ppl have been reporting that on ALL roms but i haven't had any issues, the roms seem to flash fine for me. But others have to edit the updater script, also some reported that flashing via cwm worked for them without editing the updater script and others said switching to twrp helped them... This is the weirdest android phone I have owned.
Sent from my SM-N9005 using Tapatalk

I also want to know this, and how to detect if the one i have is hlte or hltexx

JazonX said:
Wait for a dev to reply this properly, and this should be in the Q&A Section I assume,
Remove the device check in updater-binary, as I guess it means (hlte and xxx) the same device. Some have suggested to use TWRP Recovery as well. This is according to my understanding of the issue.
Click to expand...
Click to collapse
Can i move the thead myself to the Q and A section?:

hi,
i had the error flashing a rom and i switched from twrp to cwm now it works!
but i still want to know what the difference is!

Hakired said:
i tried flashing the official cyanogen mod nightly for "International" which was called HLTEXX when i tried it it said your phone is an HLTE and not and HLTEXX.
Click to expand...
Click to collapse
i can also not install the nightly hltexx.
bought my device in germany.
no problem with temasek unoffical and probam.

Hakired said:
My note 3 is from Vodafone Australia. the model number is SM-N9005. I always assumed it was one of the "International" one. Then i tried flashing the official cyanogen mod nightly for "International" which was called HLTEXX when i tried it it said your phone is an HLTE and not and HLTEXX.
What's the difference? Are there 2 kinds of international?
Click to expand...
Click to collapse
I also have Aussie Vodafone stock. hltexx is fine for me. See my answer below. I assume it must read product device and not product name. I have used a number of different firmware now and all good. I would assume yours is from the same place.
johanveld said:
I also want to know this, and how to detect if the one i have is hlte or hltexx
Click to expand...
Click to collapse
Check your Build Prop located in System (use root explorer or a similar app) and you will see this;
ro.product.name=hltexx
ro.product.device=hlte
So this is where people are getting confused because it is both depending on what you read.

Hakired said:
My note 3 is from Vodafone Australia. the model number is SM-N9005. I always assumed it was one of the "International" one. Then i tried flashing the official cyanogen mod nightly for "International" which was called HLTEXX when i tried it it said your phone is an HLTE and not and HLTEXX.
What's the difference? Are there 2 kinds of international?
Click to expand...
Click to collapse
hltexx is product name, hlte is device name
hlte refers to many models, including N9002, N9005, N9006, N9008, N9009
while hltexx is N9005
you can use my app Phone INFO to get more information.

i removed the first line from the updater script and successfully flashed cm nightly in twrp.

johanveld said:
hi,
i had the error flashing a rom and i switched from twrp to cwm now it works!
but i still want to know what the difference is!
Click to expand...
Click to collapse
but im already using CWM tho XiaoLu's custom CWM 6.0.4.5 i think

not-i said:
I also have Aussie Vodafone stock. hltexx is fine for me. See my answer below. I assume it must read product device and not product name. I have used a number of different firmware now and all good. I would assume yours is from the same place.
Check your Build Prop located in System (use root explorer or a similar app) and you will see this;
ro.product.name=hltexx
ro.product.device=hlte
So this is where people are getting confused because it is both depending on what you read.
Click to expand...
Click to collapse
have you tried the cyanogen nightly htlexx?
Are you telling me to edit my build prop?
What i was trying to do was dirty flash the Cyanogen Nightly on top of Temasek. I didnt believe a full wipe would help, Do you reckon I should? Just wanted to try out the Cyanogen but im pretty happy with Temasek's

A.N.Droid said:
i removed the first line from the updater script and successfully flashed cm nightly in twrp.
Click to expand...
Click to collapse
im kinda newbie and this seems difficult. No idea what an updated script is. Is that part of the ROM im flashing or within the recovery?

not-i said:
Check your Build Prop located in System (use root explorer or a similar app) and you will see this;
ro.product.name=hltexx
ro.product.device=hlte
So this is where people are getting confused because it is both depending on what you read.
Click to expand...
Click to collapse
My build prop says this.
ro.product.name=hltexx
ro.product.device=hltexx
So afterall it was hltexx but Cyanogen says it's only hlte.. strange. I'm going to try and do full wipe then flash cyanogen.

Hakired said:
So afterall it was hltexx but Cyanogen says it's only hlte.. strange. I'm going to try and do full wipe then flash cyanogen.
Click to expand...
Click to collapse
if it still doesnt work you could do this:
open the cm nightly archive (i use winrar), navigate to \META-INF\com\google\ and extract the file updater-script.
open in a text editor of your choice.
remove the first line and save the edited file. (you dont need to know a thing about programming to realize that this is the device check)
drag and drop the edited file into that folder in the archive and overwrite the old file.
flash. enjoy !

Thanks it worked. Now to see if it's fully functional with my phone.

Hakired said:
Could you send me your updater script file with the deleted line? When i opened it in notepad they were not in lines and it just goes on and on so I deleted some stuff concerning the checks and it looks like this.
|| abort("This package is for \"hltexx\" devices; this is a \"" + getprop("r ...
I get an error status code: 6
but it does not check for the phone model anymore.
Click to expand...
Click to collapse
great that it works for you now !
please do not use the attached file anymore, its outdated !

sermon edgedai
i have install the rom with the updater-script file
now i have a bootloop with the massage
Kernel is not seandroid enforcing
set warranty bit: kernel
pls help mee

NeoGoku123 said:
i have install the rom with the updater-script file
now i have a bootloop with the massage
Kernel is not seandroid enforcing
set warranty bit: kernel
pls help mee
Click to expand...
Click to collapse
Knox bootloader / kernel not compatible
This arrived to me on another device. I tried flash a Rom MJ2 non Knox over a ML1 Knox. The flashing by Odin was good but the Knox bootloader installed not liked it and give me that error at boot, and the phone not started.
I made a Mod Kernel-ML1.tar.md5 to flash by Odin and problem solved. MJ2 worked whit ML1 kernel.

NeoGoku123 said:
i have install the rom with the updater-script file
now i have a bootloop with the massage
Kernel is not seandroid enforcing
set warranty bit: kernel
pls help mee
Click to expand...
Click to collapse
could be that the attached file is outdated. you have to modify it by yourself next time.
can you get into recovery ? if so, wipe and install a rom.
if not, can you get into download mode ? if so, flash stock rom with odin.
if not, pull the battery and try again.

[Q] CM11 and tmo D801

I have been trying to flash CM11 to my G2(Tmo) but the problem I am running into is that no matter what tut I follow I end up with the same result. Fail. I have attached a pic of my screen if that helps. I have TWRP v2.6.3.2 installed and everything but install runs fine. The error that comes up on the install screen is "E:Error executing updater binary in zip '.........'. I am a noob to flashing/roms sorry If more information is needed just let me know.
Thanks.

DireArcticWolf said:
I have been trying to flash CM11 to my G2(Tmo) but the problem I am running into is that no matter what tut I follow I end up with the same result. Fail. I have attached a pic of my screen if that helps. I have TWRP v2.6.3.2 installed and everything but install runs fine. The error that comes up on the install screen is "E:Error executing updater binary in zip '.........'. I am a noob to flashing/roms sorry If more information is needed just let me know.
Thanks.
Click to expand...
Click to collapse
To flash CM11 and most kitkat roms, you'll need to update TWRP. The most up-to-date version for the D801 (T-Mobile G2) is v2.6.3.5, which can be found in the CMB thread under G2 Android Development (T-Mobile): http://forum.xda-developers.com/showthread.php?t=2568732 . The update is a flashable zip, so download it to your phone, reboot to recovery, and install it using your existing TWRP. After a reboot into recovery you should be updated, and you should be able to flash CM11.

thanks
flutterguy317 said:
To flash CM11 and most kitkat roms, you'll need to update TWRP. The most up-to-date version for the D801 (T-Mobile G2) is v2.6.3.5, which can be found in the CMB thread under G2 Android Development (T-Mobile): http://forum.xda-developers.com/showthread.php?t=2568732 . The update is a flashable zip, so download it to your phone, reboot to recovery, and install it using your existing TWRP. After a reboot into recovery you should be updated, and you should be able to flash CM11.
Click to expand...
Click to collapse
Thank you sssoooooo much, after a week of pulling my hair out I am happy to say I now have CM11 on my G2.

flutterguy317 said:
To flash CM11 and most kitkat roms, you'll need to update TWRP. The most up-to-date version for the D801 (T-Mobile G2) is v2.6.3.5, which can be found in the CMB thread under G2 Android Development (T-Mobile): http://forum.xda-developers.com/showthread.php?t=2568732 . The update is a flashable zip, so download it to your phone, reboot to recovery, and install it using your existing TWRP. After a reboot into recovery you should be updated, and you should be able to flash CM11.
Click to expand...
Click to collapse
I'm having a similar problem on my d802. I will go and try. Thank you for this answer!
Sent from my LG-D802 using Tapatalk

Plain Water said:
I'm having a similar problem on my d802. I will go and try. Thank you for this answer!
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Have the same problem. But cant find out what the newest twrp is. i have now 2.6.3.2. But cant find 2.6.3.5. I found one 2.6.3.3 but when i try to push it just imput file is not a loki image.
Can you please find TWRP version that works with mine g802 and cm11 ?
Thanks

markula78 said:
Have the same problem. But cant find out what the newest twrp is. i have now 2.6.3.2. But cant find 2.6.3.5. I found one 2.6.3.3 but when i try to push it just imput file is not a loki image.
Can you please find TWRP version that works with mine g802 and cm11 ?
Thanks
Click to expand...
Click to collapse
I just download the Freegee app ant updatet to 2.6.3.3 and it work, if any other with LG 802 have problems.

Good to know. Thanks for the post.
Sent from my LG-D801 using XDA Premium 4 mobile app

[Q] ART to Dalvik and Titaniun Backup

I'm currently running CM11 (02-07) with ART enabled. I'm thinking of upgrading to the current nightly, but I'm not sure if I need any special steps with ART.
I will be flashing the ROM manually because I need to modify the device number, so I'll probably be doing a reset before, which will of course reset back to Dalvik and remove all my apps.
Now my quesion is, can I backup my apps and user data while in ART with Titanium, and then restore them in Dalvik? I'm thinking of keeping Dalvik so I can flash stock remote and camera.
Thanks,
Vic

Did a Titanium backup, clean install and everything is ok. ART is good, but I'm happy to be able install the remote and camera, and maybe try xposed framework.

victorbrca said:
Did a Titanium backup, clean install and everything is ok. ART is good, but I'm happy to be able install the remote and camera, and maybe try xposed framework.
Click to expand...
Click to collapse
How did you get CM11 to flash on your wind variant g2. When I flash it fails. Its also says no MD5 file found. Please Help.

AndroidNoobeee said:
How did you get CM11 to flash on your wind variant g2. When I flash it fails. Its also says no MD5 file found. Please Help.
Click to expand...
Click to collapse
Here.
http://forum.xda-developers.com/showthread.php?t=2611749
Sent from Tapatalk.

victorbrca said:
Here.
http://forum.xda-developers.com/showthread.php?t=2611749
Sent from Tapatalk.
Click to expand...
Click to collapse
I followed the guide. But when I flash CM it fails. Do need certain kernel or something? What am I doing wrong? Also I have the wind variant if thats important.

AndroidNoobeee said:
I followed the guide. But when I flash CM it fails. Do need certain kernel or something? What am I doing wrong? Also I have the wind variant if thats important.
Click to expand...
Click to collapse
How did you flash recovery?
Sent from Tapatalk.

victorbrca said:
How did you flash recovery?
Sent from Tapatalk.
Click to expand...
Click to collapse
I flashed twrp v2.6.3.2 through flashify. I realize this isn't the most updated version of twrp for my g2 but when i flash the updated vesion (v2.6.3.4) it fails.

AndroidNoobeee said:
I flashed twrp v2.6.3.2 through flashify. I realize this isn't the most updated version of twrp for my g2 but when i flash the updated vesion (v2.6.3.4) it fails.
Click to expand...
Click to collapse
I would go to the thread and ask for help. Also paste the error you get when you try to flash CM11.
Sent from Tapatalk.

victorbrca said:
I would go to the thread and ask for help. Also paste the error you get when you try to flash CM11.
Sent from Tapatalk.
Click to expand...
Click to collapse
I noticed you are using a furnace kernel,Did you flash CM11 with stock lg kernel? If so what version of twrp did you use. I don't understand the problem because I have the dame model as you.

AndroidNoobeee said:
I noticed you are using a furnace kernel,Did you flash CM11 with stock lg kernel? If so what version of twrp did you use. I don't understand the problem because I have the dame model as you.
Click to expand...
Click to collapse
Again, post back at that other thread with the details of what you did and what error you are getting. The more detail you can give the more we can help.
In a nutshell, the recovery that you install will dictate what ROM will work on your device. For some of the ROMs in that thread you will need to install a kernel, but that depends. And I'm not sure what error you are getting.
Sent from Tapatalk.

victorbrca said:
Again, post back at that other thread with the details of what you did and what error you are getting. The more detail you can give the more we can help.
In a nutshell, the recovery that you install will dictate what ROM will work on your device. For some of the ROMs in that thread you will need to install a kernel, but that depends. And I'm not sure what error you are getting.
Sent from Tapatalk.
Click to expand...
Click to collapse
It won't allow me because the thread is only for developers.