Database Develop

[Q] More details about flashing

Hi, everyone. I believe these questions are not covered in this forum yet.
Is it possible to just flash kernel from FTF file?
Is it possible to convert or package kernel (IMG / ELF) file to FTF file?
If above 2 are possible, does that mean that kernel can be flashed from flashmode instead of Fastboot mode & thus eliminating the need to unlock bootloader?
Are the firmware & kernel of Xperia T / TX / TL / V interchangeable?
Is there any risk trying to flash other firmware or kernel or anything that is not compatible?
Is there any risk trying to flash kernel (IMG /ELF) file & custom ROM with locked bootloader?
Is flashing stock advanced kernel equivalent to flashing stock kernel?
I believe these questions are worthwhile to be added into the All In One thread as well.
Appreciate for the knowledgeable input from u all. Thx in advance! =)

SCC2002 said:
Hi, everyone. I believe these questions are not covered in this forum yet.
Is it possible to just flash kernel from FTF file?
Is it possible to convert or package kernel (IMG / ELF) file to FTF file?
If above 2 are possible, does that mean that kernel can be flashed from flashmode instead of Fastboot mode & thus eliminating the need to unlock bootloader?
Are the firmware & kernel of Xperia T / TX / TL / V interchangeable?
Is there any risk trying to flash other firmware or kernel or anything that is not compatible?
Is there any risk trying to flash kernel (IMG /ELF) file & custom ROM with locked bootloader?
Is flashing stock advanced kernel equivalent to flashing stock kernel?
Click to expand...
Click to collapse
These questions have been answered
1) yes, stock only
2) No
3) No, to flash custom kernel you need fastboot, hence you need unlocked bootloader
4) No, but you can try and see
5) There is always a risk when you flash something to your phone.
6) No risk, because without an unlocked bootloader it wont work*
7) No, Stock advanced kernel is a custom kernel based on stock with cmw and a few other things incorpprated, whilst stock kernels are stock kernels.
EDIT
* from number 6) you may soft brick the phone, but just flash a stock based rom back and it will work again. The problem will be with flashing a rom that needs a custom kernel that our phone will not support because you have a locked bootloader.
SCC2002 said:
I believe these questions are worthwhile to be added into the All In One thread as well.
Appreciate for the knowledgeable input from u all. Thx in advance! =)
Click to expand...
Click to collapse
Why didnt you ask in that thread then? I have spent the time to add them to the FAQ there...

gregbradley said:
These questions have been answered
1) yes, stock only
2) No
3) No, to flash custom kernel you need fastboot, hence you need unlocked bootloader
4) No, but you can try and see
5) There is always a risk when you flash something to your phone.
6) No risk, because without an unlocked bootloader it wont work*
7) No, Stock advanced kernel is a custom kernel based on stock with cmw and a few other things incorpprated, whilst stock kernels are stock kernels.
EDIT
* from number 6) you may soft brick the phone, but just flash a stock based rom back and it will work again. The problem will be with flashing a rom that needs a custom kernel that our phone will not support because you have a locked bootloader.
Click to expand...
Click to collapse
Thank u so much for ur answers. Sorry for didn't manage to find them. =)
1 - 4. My questions arose are bcoz that in order to root firmware later than 7.0.A.3.195 needs to downgrade to 7.0.A.1.303. However, I'm owning a Xperia TX, which having the firmware of 7.0.A.3.197 & the earliest firmware I found for Xperia TX is 7.0.A.1.307. That's why I am not sure whether Xperia T's 7.0.A.1.303 firmware works on Xperia TX.
5. Well, what I mean is additional risk from usual flashing. =)
7. If that's the case, does installing CWM recovery with the phone rooted but locked bootloader resulting in a custom kernel?
Why didnt you ask in that thread then? I have spent the time to add them to the FAQ there...
Click to expand...
Click to collapse
Well, I was thinking that these questions are better asked on a separate thread then. Anyway, thx a lot for compiling the All In One thread. It's very useful. More details can be added though. =)

SCC2002 said:
Thank u so much for ur answers. Sorry for didn't manage to find them. =)
1 - 4. My questions arose are bcoz that in order to root firmware later than 7.0.A.3.195 needs to downgrade to 7.0.A.1.303. However, I'm owning a Xperia TX, which having the firmware of 7.0.A.3.197 & the earliest firmware I found for Xperia TX is 7.0.A.1.307. That's why I am not sure whether Xperia T's 7.0.A.1.303 firmware works on Xperia TX.
5. Well, what I mean is additional risk from usual flashing. =)
7. If that's the case, does installing CWM recovery with the phone rooted but locked bootloader resulting in a custom kernel?
Click to expand...
Click to collapse
1-4) The 303 and 307 firmware are basically the same FW. 303 for the T and 307 for the TX. also 195 is for the T and 197 is for the TX.
5) If you flash something that is not compatable then you can either get various results ranging from no apparent bugs, to slightly buggy formware, to soft bricks or inthe worst case a hard bricked phone.
7) No, installing recovery is seperate to having a custom kernel with recovery incorported within it.

gregbradley said:
1-4) The 303 and 307 firmware are basically the same FW. 303 for the T and 307 for the TX. also 195 is for the T and 197 is for the TX.
5) If you flash something that is not compatable then you can either get various results ranging from no apparent bugs, to slightly buggy formware, to soft bricks or inthe worst case a hard bricked phone.
7) No, installing recovery is seperate to having a custom kernel with recovery incorported within it.
Click to expand...
Click to collapse
5. Hard-brick. Does that mean the phone is irrecoverable any more? In what case would result in this condition?
Oh yea, another question. In this case, downgrading the firmware is required to root the phone. So, does downgrading the kernel only, but not the firmware possible to give the same effect?

SCC2002 said:
5. Hard-brick. Does that mean the phone is irrecoverable any more? In what case would result in this condition?
Click to expand...
Click to collapse
Hard brick means your phone is properly FUBAR'd
SCC2002 said:
Oh yea, another question. In this case, downgrading the firmware is required to root the phone. So, does downgrading the kernel only, but not the firmware possible to give the same effect?
Click to expand...
Click to collapse
Maybe, try it and see. But i think a whole flash of the firmware is needed.

SCC2002 said:
Oh yea, another question. In this case, downgrading the firmware is required to root the phone. So, does downgrading the kernel only, but not the firmware possible to give the same effect?
Click to expand...
Click to collapse
I had read that for some other devices (I think Xperia P) flashing just the old kernel, then rooting then flashing the new kernel works to keep root without flashing system folder or anything else. Give it a try, worse case you just flash again full ftf and start over.

gregbradley said:
Hard brick means your phone is properly FUBAR'd
Maybe, try it and see. But i think a whole flash of the firmware is needed.
Click to expand...
Click to collapse
Spectre51 said:
I had read that for some other devices (I think Xperia P) flashing just the old kernel, then rooting then flashing the new kernel works to keep root without flashing system folder or anything else. Give it a try, worse case you just flash again full ftf and start over.
Click to expand...
Click to collapse
Happy New Year, guys! Thx for the answer. I've tried just flashing the kernel. Doesn't work. Succeeded rooting after flashing the whole firmware. =)
Anyway, now I'm stuck in the process of upgrading the firmware. I can't seem to find a stock ROM for Xperia TX (LT29i) 7.0.A.3.197 firmware. I just gone through all the hard ways to create a stock ROM myself & successfully flashed it. Perhaps bcuz of the improper build, my WiFi can't be turned on & there might be other problems coming up later.
Now I am also worrying that would it cause any prob to my phone. I followed this guide to create the ROM.
http://forum.xda-developers.com/showthread.php?t=1931189
& I took the META-INF folder from this custom ROM.
http://forum.xda-developers.com/showthread.php?t=2040989
Plz kindly help that if there's any resource to the stock ROM or any way to fix this, as well as have a look if there is any side effect from flashing that ROM. Many thanks! ><

Wifi not working is because you have to copy and rename the /system/lib/modules/prima/prima_wlan.ko file to just /system/lib/modules/wlan.ko
I use this for making my own versions: http://forum.xda-developers.com/showthread.php?t=633246

Spectre51 said:
Wifi not working is because you have to copy and rename the /system/lib/modules/prima/prima_wlan.ko file to just /system/lib/modules/wlan.ko
I use this for making my own versions: http://forum.xda-developers.com/showthread.php?t=633246
Click to expand...
Click to collapse
Really? That's all? There's no other side effect from the way that I built the ROM? Am I building ROM with a proper way?
Do I've to keep the original file at the original location? Why is it that we need to modify this, just wondering?
Btw, I heard that there's a prob with MAC address with this method from another forumer. Is this true?

SCC2002 said:
Really? That's all? There's no other side effect from the way that I built the ROM? Am I building ROM with a proper way?
Do I've to keep the original file at the original location? Why is it that we need to modify this, just wondering?
Btw, I heard that there's a prob with MAC address with this method from another forumer. Is this true?
Click to expand...
Click to collapse
I kept the other file in the original location. Not sure about any Mac address issue. Worked fine for my device. Not sure about the way you use to build the rom. I just use the android kitchen since its pretty quick and easy.
Sent from my Sony Xperia™ TL

[solved] No service with Paranoid Android 4.1 ROM: Help please

I installed Paranoid Android rom coming from JB with cocore 9.0. I followed the instructions (installing boot.img then the rom, gapps and supersu). Everything went smooth but I ended up with "no service". Apparently my sim card is not recognized. I use an italian SIM (TIM).
Any suggestion?
I had to revert back to my (nandroid backupped) old rom.
Sincerely
G.

gianpaoloc said:
I installe Paranoid Android rom coming from JB with cocore 9.0. I followed the instructions (installing boot.img then the rom, gapps and supersu). Everything went smooth but I ended up with "no service". Apparently my sim card is not recognized. I use an italian SIM (TIM).
Any suggestion?
I had to revert back to my (nandroid backupped) old rom.
Sincerely
G.
Click to expand...
Click to collapse
Do Factory reset.

shut_down said:
Do Factory reset.
Click to expand...
Click to collapse
Done, before and after installing the rom. Same result.
I also tried revierting back to my old rom (re-flashed with odin) and reistalling PA from the beginning. Same result.
I forgot to mention my device is a GT-I9070P. I thought it was the same as I9070 apart from the NFC (which I do not care about). Is this correct?
Any other suggestion?
Thanks
G.

gianpaoloc said:
Done, before and after installing the rom. Same result.
I also tried revierting back to my old rom (re-flashed with odin) and reistalling PA from the beginning. Same result.
I forgot to mention my device is a GT-I9070P. I thought it was the same as I9070 apart from the NFC (which I do not care about). Is this correct?
Any other suggestion?
Thanks
G.
Click to expand...
Click to collapse
Can you make sure that you re-install the firmware (stock ROM) Firmware GT-i9070P with similar, I mean with the Stock ROM GT-i9070p not GT-I9070 Stock ROM? Due to my knowledge although one brand, but both devices have different firmware (specially Stock ROM). As an example here.

gianpaoloc said:
Done, before and after installing the rom. Same result.
I also tried revierting back to my old rom (re-flashed with odin) and reistalling PA from the beginning. Same result.
I forgot to mention my device is a GT-I9070P. I thought it was the same as I9070 apart from the NFC (which I do not care about). Is this correct?
Any other suggestion?
Thanks
G.
Click to expand...
Click to collapse
In that case you must follow this guide: http://forum.xda-developers.com/showthread.php?t=2191628

shut_down said:
In that case you must follow this guide: http://forum.xda-developers.com/showthread.php?t=2191628
Click to expand...
Click to collapse
You deserve the biggest possible thanks!!!
Indeed, I substituted the "tee" folder in paranoid android rom with the tee folder I found under my own I9070P JB rom (/system/lib/tee) and restarted from the beginning. This time everything went smooth and I have my network.
For those interested, I was using a samsung original I9070P JB rom, so the "tee" folder is the one coming from the original samsung firmware and it worked flawlessly with CM11 based paranoid android.
Thanks a lot!
Sincerely
G.

[Q] Camera stopped on NUTT 4.4.2 rom after rooting

is their any way to fix the issue of camera stoppage on Nutt method of rooting and installed 4.4.2 kitkat update.... Nutt told three solutions
You have 3 things to try to fix it, try them one at a time:
Clear dalvik-cache only;
Clear the camera app settings;
Do a factory reset in TWRP or PhilZ (this should keep your internal storage safe);
flash the ROM package again;
boot until you can test the camera;
If it works go back to recovery to restore a backup of data.
and unfortunately i tries everyone but still issue is thier..... can anyone knows how to fix it....
Before posting your replies please remember that i have lost DRM keys in back and got fixed camera issue by Sony 4.3 update....
any developer or NUTT please help me out

Hi, did you read this? Read this please, if the problem is like mine was, i copied what you have to do
http://forum.xda-developers.com/showthread.php?t=2706426
Did you make a TA-Partition Backup BEFORE unlocking the bootloader? If yes- Just restore it & you are fine.
If not, thats what you have to do/what i did to make it work.
First of all NOT STRIPPED ftf`s becasue it is only the kernel as far as i know. You have to download the whole original rom which is about 1gb.
+Edit. Do not exclude any options in Flashtool like Ta, kernel or anything else !!!! Just choose your ftf and flash!
First flash original 290. FTF with your branding (for me it was vodafone)
The camera should work there. If yes continue.
Flash original 681. ftf with your branding if possible.
The cam should work there too. If yes continue.
Now you are good to go, put your custom rom on SD Card-
Flash custom kit kat kernel/or stock with recovery
Boot into CWM and flash your Rom. Your Cam should work.
LG

how can i get original Zip file of .681 of my brand... i downloaded NUTT given Zip file from there....i have installed .136 now and camera is working fine but i wanna update to kitkat ....

HAK821 said:
how can i get original Zip file of .681 of my brand... i downloaded NUTT given Zip file from there....i have installed .136 now and camera is working fine but i wanna update to kitkat ....
Click to expand...
Click to collapse
well i meant to install ftf file not zip file. if its working on 136. try to flash zip file of kit kat, should work

[Q] eXizistenZ ultra 4.0.0 bootloader

I am new to rooting and stuff.
So recently I bought Sony Xperia SP C502 .
The current firmware version is 12.1.A.1.205 .
I want to root my phone and install eXistenZ 4.0.0( rom based on stock rom )
My bootloader is locked.
Bootloader unlock is allowed.I don't want to unlock the bootloader.
Is it possible to root and install the rom without unlocking the bootloader ?
Will rooting and installing the rom automatically unlock it ?
please help I am a noob.

Existenz is for unlocked and locked bootloader

TsunaH said:
Existenz is for unlocked and locked bootloader
Click to expand...
Click to collapse
So installing it won't unlock my bootloader ?
Because i don't want to lose DRM keys and BE2.

See bro
Root it using app called towel root
Install super su not from play store
Install busybox installer from playstore
Install a custom recovery
And flash it
You won't be unlocking your bootloader

You can flash it on locked bootloader too.Flashing this rom won't unlock your bootloader

Existenz Ultra 4.0.0 - Awesome Rom
Existenz Ultra 4.0.0 is really awesome rom with all good features which covered honami as well as sony features.
Battery is good, and most of all AR effect which comes with the rom is the most enjoyable feature ever experienced.
But if this rom will be having good audio mod like Viper4Android.. viz. coz i have observed sound is a little bit less than stock. sorry for my bad english.
ROM Rocks......:good:

Steps for Switching Rom
I am currently using Cm11 on sony xperia sp, I have a unlocked BL and root access.
I would like to switch to a new custom rom now like XperianZe. I tried also, and in the process i bricked and also had a bootloop.
Can anyone please explain the detailed steps to do a fresh install to a new custom rom like XperianZe.

sanusunnyk said:
I am currently using Cm11 on sony xperia sp, I have a unlocked BL and root access.
I would like to switch to a new custom rom now like XperianZe. I tried also, and in the process i bricked and also had a bootloop.
Can anyone please explain the detailed steps to do a fresh install to a new custom rom like XperianZe.
Click to expand...
Click to collapse
Just follow the mentioned instructions in the respective thread. And as for Xperianz as you mentioned, you have to read this post.
Based on the post, it seemed the installation is straight forward. What makes you have a bootloop? Did you flashed the kernel mentioned in the thread via fastboot?

TechnoSparks said:
Just follow the mentioned instructions in the respective thread. And as for Xperianz as you mentioned, you have to read this post.
Based on the post, it seemed the installation is straight forward. What makes you have a bootloop? Did you flashed the kernel mentioned in the thread via fastboot?
Click to expand...
Click to collapse
yes, you guessed correct. i tried flashing the kernel. And the phone didn't start at all.. not even power up.
Later i read a post in XDA, in which it was described that i should do a hard rest by pushing the hole button at back and then try to boot.
Tats when i got boot-loop. I again flashed the custom kernel (DooMLoRD) and did installed CM11 again using CM recovery. Then the phone booted cm 11.
I followed this link and tried doing so. which resulted in phone not powering up and then boot-loop.
So now if i install Xperianz ROM following instruction in this link, it should be working properly correct?
Am sorry if am asking dump questions. Now am a bit scared to try to switch to this cutom ROM as i may end up bricking the phone again. The thing is I really don't want to mess it up again.
I am new to rooting n playing around with custom ROM. CM11 was my first try and was a success in first go.
Thank you for helping me.

sanusunnyk said:
yes, you guessed correct. i tried flashing the kernel. And the phone didn't start at all.. not even power up.
Later i read a post in XDA, in which it was described that i should do a hard rest by pushing the hole button at back and then try to boot.
Tats when i got boot-loop. I again flashed the custom kernel (DooMLoRD) and did installed CM11 again using CM recovery.
But now am a bit scared to try to switch to this cutom ROM as i may end up bricking the phone again. That's why i asked if anyone could give me detailed steps on how to do so.
I am new to rooting n playing around with custom ROM. CM11 was my first try and was a success in first go.
Thank you replying
Click to expand...
Click to collapse
I am concerned about how you flashed the kernel. How did you flash the kernel provided in the thread? Did you use adb or FlashTool?
If you want to try any other you can use Existenz as it require only the stock kernel.

TechnoSparks said:
I am concerned about how you flashed the kernel. How did you flash the kernel provided in the thread? Did you use adb or FlashTool?
If you want to try any other you can use Existenz as it require only the stock kernel.
Click to expand...
Click to collapse
I used FLashtool to flash the kernal.
If my understanding is correct, As of now i am not on stock kernal. When instaling CM11, I flashed the kernal of DoomLord for getting CM 6. recovery.
If this is the case should i flash the stock kernal first and then give a try for Existenz?

sanusunnyk said:
I used FLashtool to flash the kernal.
If my understanding is correct, As of now i am not on stock kernal. When instaling CM11, I flashed the kernal of DoomLord for getting CM 6. recovery.
If this is the case should i flash the stock kernal first and then give a try for Existenz?
Click to expand...
Click to collapse
Well Existenze require most Sony things out of the box, so you'll first need to have Stock ROM in place before flashing it's ZIP. I've dug through the Xperianze thread for you and seemed like your problem is not to be found in the thread. If you really want to try out Xperianze, you might want to flash the kernel via fastboot using adb, rather than Flashtool.

TechnoSparks said:
Well Existenze require most Sony things out of the box, so you'll first need to have Stock ROM in place before flashing it's ZIP. I've dug through the Xperianze thread for you and seemed like your problem is not to be found in the thread. If you really want to try out Xperianze, you might want to flash the kernel via fastboot using adb, rather than Flashtool.
Click to expand...
Click to collapse
Thanks a lot.
I will try it out. and let you.
Again Thanks a lot for your help.

camera not working (Galaxy S III i9305 / flashed ClockworkMod+touch / Cyanogen 10.1.

Samsung Galaxy S III i9305 LTE
flashed with CWM 10.1.3 (based on Android 4.2.2)
Compilation number: cm_i9305-userdebug 4.2.2 JDQ39E eng.jenkins.20130923.145024 test-keys
Photo camera stopped from working.
When I tap on Camera icon there is message that can't connect to camera. Camera is not starting.
I read probably everything. I did everything that I suppoused that can help me ... no results
There is lot of possible sollutions, but none of them provides result. I hope that anybody known solution ...
There is one post which I dont understand:
http://forum.xda-developers.com/galaxy-s3/general/jb-4-1-2-camera-driver-t2006128
> 1. Please dial in stock dialer the following: *#34971539#
What does it mean ?
When I tried to call this number (like normal phone call) I have message (in translation to english): "There is a problem with connection or MMI code is not correct"
PS.
When I flashed CWM 11 camera was working but I need to have CWM10 because is based od Android < 4.4
I have to had Android 4.1 – 4.3 because only on those version Samsung DriveLink application is working.
I want to use phone in my Toyota car with mirror link for full mirroring car's display.
Drive link from GooglePlay:
https://play.google.com/store/apps/details?id=app.scm&hl=pl
And Drivelink from Samsung:
supported android versions: 4.1 – 4.3

Hello and good evening/night? ?,
it's a known problem on all ROMs for I9305. I am on Resurrection Remix 5.5.5 Sammy and have the same problem.
No one of the devs had found a solution for this.

even DriveLink not works
Trafalgar Square said:
Hello and good evening/night? ,
it's a known problem on all ROMs for I9305. I am on Resurrection Remix 5.5.5 Sammy and have the same problem.
No one of the devs had found a solution for this.
Click to expand...
Click to collapse
even DriveLink not works I am a little bit depressed ... I lost guarantee for my smartfon without any result ((

howto install jellybean 4.3 original but with CWM bootloader ?
marcint43 said:
even DriveLink not works I am a little bit depressed ... I lost guarantee for my smartfon without any result ((
Click to expand...
Click to collapse
Do you know how to install 4.3 Jellybean original version - preferably with my current CWM bootloader ?
Maybe original version of android - no Cyanogen wil work ...
in 4.3 version of android there is a chance to do that ...

marcint43 said:
Do you know how to install 4.3 Jellybean original version - preferably with my current CWM bootloader ?
Maybe original version of android - no Cyanogen wil work ...
in 4.3 version of android there is a chance to do that ...
Click to expand...
Click to collapse
Just flash the stock firmware with odin.
Try THIS SITE and see if your country region is there
If not sammobile.com has a comprehensive list(the download is very slow)

can I put any of those zip files ?
noppy22 said:
Just flash the stock firmware with odin.
Click to expand...
Click to collapse
but this will erase my CWM recovery, is it true ?
Is it possible to have CWM recovery with stock Android ?
I downloaded from Sammobile ZIP: I9305XXUEML9_I9305PRTEML1_PRT.zip (this is 4.3 android)
..but for now I have I9305XXUFNJ1 displayed in my phone ... is this OK or I can brick my phone ?
In pull-down menu there are possibilities:
2014-10-01 Poland (T-mobile) 4.3 I9305XXUENH1 I9305TPLENH1
2014-05-01 Poland (T-mobile) 4.3 I9305XXUENC1 I9305TPLENE1
2014-01-01 Poland (PLUS) 4.3 I9305XXUEMKC I9305PLSEMK1 NO
2014-01-01 Poland (Play) 4.3 I9305XXUEML9 I9305PRTEML1 <<<====This one I downloaded, from:
sammobile /firmwares/download/24228/I9305XXUEML9_I9305PRTEML1_PRT/
I don't know if I have "branded" phone ... for Poland there are "Play" "Tmobile" Plus" zip file...
I know that previous owner of phone bought it at "Orange" telecomunication operator. I dont see any operator logo etc on phone ...
Is this relevant which version I will take ?
Maybe just "the newer the better" ?
Odin doesn't works for me on any windows machine that I have. I am struggling with Heimdall software ...
I successfully made this:
heimdall flash --RECOVERY recovery-clockwork-touch-6.0.4.7-i9305.img --no-reboot

region ok, but ...
noppy22 said:
Try THIS SITE and see if your country region is there
Click to expand...
Click to collapse
yes there is my region (Poland) but only 4.4.4 version

marcint43 said:
yes there is my region (Poland) but only 4.4.4 version
Click to expand...
Click to collapse
I see 4.3 - I9305XXUENC1 / TPLENE1 Poland T-Mobile version from the tsar3000 site?? Anyway the one you downloaded from sammobile will be fine
The branded versions only give you different bloatware. It shouldn't make any difference otherwise(other than slightly older/newer baseband). And yes it will overwrite the recovery, but you can install cwm later.
I'm not sure what the process is exactly with heimdall as I have odin, but I think it is similar

noppy22 said:
I see 4.3 - I9305XXUENC1 / TPLENE1 Poland T-Mobile version from the tsar3000 site??
Click to expand...
Click to collapse
yes, I see it on the list, but when I try to download via "mirror 1 or 2 links" - I am redirected to another list - where there is only 4.4.4 versions
After few hours I have to go to work, so I am going to sleep now, but tomorrow I will flash phone with that version
Did you heard that flashing from 4.4.4 just to 4.3 will brick the phone ? (because of changes in "knox bootloader"??? My coleague says that ...)
and "I have to downgrade to 4.2 and than upgrade to 4.3 ... is it true ?

marcint43 said:
yes, I see it on the list, but when I try to download via "mirror 1 or 2 links" - I am redirected to another list - where there is only 4.4.4 versions
After few hours I have to go to work, so I am going to sleep now, but tomorrow I will flash phone with that version
Did you heard that flashing from 4.4.4 just to 4.3 will brick the phone ? (because of changes in "knox bootloader"??? My coleague says that ...)
and "I have to downgrade to 4.2 and than upgrade to 4.3 ... is it true ?
Click to expand...
Click to collapse
What is the latest stock version you have had on the phone? If you have never had 4.4.4 stock, then you should be fine. Just always use the 4.3 to go back to stock and you will always have the old bootloader.
Maybe check your bootloader before you do anything

DriveLink needs GoogleApps libraries! (pure CyanogenMod is not enough)
BINGO! After installing GoogleApps.zip (for 4.4.3) DriveLink app started to run - not crashing anymore ...
but the car still not see any phone ... but this is because of android version ..4.4.4
Android have to be in 4.1-4.3 versions.

noppy22 said:
What is the latest stock version you have had on the phone? If you have never had 4.4.4 stock, then you should be fine. Just always use the 4.3 to go back to stock and you will always have the old bootloader.
Maybe check your bootloader before you do anything
Click to expand...
Click to collapse
Originally I was had 4.4.2 version, original samsung, before any changes.
Then I installed ClockworkMode custom recovery ... and next CyanogenMod 11 android clone (based on 4.4.4 android).
Than I downgraded CyanogenMod to 10.1.3 version (based on 4.2.? android), just because I did'nt find any 10.2 Cyanogen (based on 4.3 android).
Next I again installed CyanogenMod 11 (android 4.4.4) ... as I have now.
Recovery is still CLockworkMode (with TouchPhiz) ...nice and functional (with working adb from my Linux).
Oh, I exactly did that what is described on site: https://wiki.cyanogenmod.org/w/Install_CM_for_i9305
(using CWM as custom recovery)
> Maybe check your bootloader before you do anything
how ? What do you mean ?

marcint43 said:
Originally I was had 4.4.2 version, original samsung, before any changes.
Then I installed ClockworkMode custom recovery ... and next CyanogenMod 11 android clone (based on 4.4.4 android).
Than I downgraded CyanogenMod to 10.1.3 version (based on 4.2.? android), just because I did'nt find any 10.2 Cyanogen (based on 4.3 android).
Next I again installed CyanogenMod 11 (android 4.4.4) ... as I have now.
Recovery is still CLockworkMode (with TouchPhiz) ...nice and functional (with working adb from my Linux).
Oh, I exactly did that what is described on site: https://wiki.cyanogenmod.org/w/Install_CM_for_i9305
(using CWM as custom recovery)
> Maybe check your bootloader before you do anything
how ? What do you mean ?
Click to expand...
Click to collapse
You can see in download mode. It will say something like "Knox warranty void 0x1" or something similar. This means you have the new bootloader.
But anyway, it sounds like you have found a way for drivelink to work? Try installing a custom JB rom like CM 10.1.3 or Alliance rom and you should have it working

CM10.1.3 - drivelink doesnt work
noppy22 said:
You can see in download mode. It will say something like "Knox warranty void 0x1" or something similar. This means you have the new bootloader.
But anyway, it sounds like you have found a way for drivelink to work? Try installing a custom JB rom like CM 10.1.3 or Alliance rom and you should have it working
Click to expand...
Click to collapse
Yes, I have in download mode message about knox 0x1
Even now, when I have CM10.1.3 installed.
unfortunately over CM 10.1.3 DriveLink is crashing
App starting, then it asks me about "DriveLink account" (WTF?) when I skip all questions - Drive link starting up with beautifull picture an then message appears: that Drive Link has been stopped....
PS. without google apps - it crashes immediately
I will try with 4.3 stock android ...(but now I have to charge batteries because CM has been crashed and discharged me battery almost completly )
PS2. I am installing this DriveLink:
http://www.colmoschinxtreme.com/android/item/drivelink

@marcint43
I noticed on the link you posted that drivelink only works with touchwiz. The stock rom should work fine, but another alternative would be to use a custom touchwiz rom like Alliance Rom. I used this rom a while ago and loved the customization and less bloat than stock(plus all the other advantages of having root access)

AllianceROm and heimdall problem with stock
noppy22 said:
Alliance Rom
Click to expand...
Click to collapse
I will try that at first
Just flash with adb sideload is possible ? It is downloading now ... but I see that size is about 1GB ... so is there recovery included ?
I dont understand well what is written on page you have written...
BTW. anybody knows how to use heimdall software to flash stock version ?
this have to be like described on: http://www.htcmania.com/showthread.php?t=698436
?
so: unzip , untar ... and next:
heimdall flash --BOOT boot.img --RECOVERY recovery.img --SYSTEM system.img --CACHE cache.img --HIDDEN hidden.img --RADIO modem.bin --BOOTLOADER sboot.bin --TZSW tz.img
?
(Odin doesn't works for me ... on any computer that I have with windows )

marcint43 said:
Just flash with adb sideload is possible ? It is downloadin.....
Click to expand...
Click to collapse
this was stupid sorry
There is special part of installation guide: .... If you don't want to use ROM Customizer to select your options you can reboot into recovery and flash the ROM zip. Default install is Stock Kernel, All Samsung and Google Apps and Stock Theme.
for startup is the best
Next time I will short ROM

marcint43 said:
I will try that at first
Just flash with adb sideload is possible ? It is downloading now ... but I see that size is about 1GB ... so is there recovery included ?
I dont understand well what is written on page you have written...
Click to expand...
Click to collapse
If you still have CM installed, download "ROM customizer" from the play store, and follow the steps from post #3 in the alliance rom thread. AFAIK the recovery will stay the same as the one you have already

recovery overwritten ?
noppy22 said:
If you still have CM installed, download "ROM customizer" from the play store, and follow the steps from post #3 in the alliance rom thread. AFAIK the recovery will stay the same as the one you have already
Click to expand...
Click to collapse
...ok, but ...by default ... "ALL" .... without Customizer ... this will overwrite my recovery too ? I will lost my CWM recovery and any other will be installed instead ?

marcint43 said:
...ok, but ...by default ... "ALL" .... without Customizer ... this will overwrite my recovery too ? I will lost my CWM recovery and any other will be installed instead ?
Click to expand...
Click to collapse
I can't remember whether the recovery was over-written, I don't think so. It would be easy to re-install your favourite recovery anyway......