Hey Guys, I just switched over to this phone from the S3, and before that from the Samsung Vibrant, so I'm no stranger to flashing, recoveries and (hopefully) following instructions.
I have the C6603 with locked bootloader.
Rooted using doomlords' easy rooting
Put on recovery "cwm-locked XZ v4"
Reboot into recovery, wipe factory reset, and flash "RomAur v8.0 AROMA" using all the appropriate settings.
Reboot recovery, and and I boot loop around the Sony screen. I've had to use flashtool 5 times in a row to go back to stock, and for some reason can't load this specific ROM. MD5 on the .zip's check out. Tried a different ROM as well, and this last time phone wouldn't even turn on. Is there a crucial step I'm missing somewhere?
I transferred a couple more ROMs ot the external SD card, but I'm unsuccessful in flashing any ROM successfully. Either bootloop or screen showing nothing.
Use Twrp instead
Sent from my C6603 using xda app-developers app
Tried TWRP as well... still the same thing.
Have tried using TWRP as well as Clockwork, and still either softbrick, or bootloop around Sony screen.
Have tried EXCELSUS_Z_v4
monXdifiedZ
avatar nightly
and Android 4.3
and RomAUR, and havn't gotten past the Sony symbol with any of them.
I have gone back to stock to "C6603_10.1.A.1.434_UK unbranded" about 10 times now... Thoughts?
If you are flashing the newer roms you need to update to an newer kernel bootloader first ..
The stock you are flashing is older ...
If you don't have the newer kernel you will appear to have soft bricked ..
Most of the rom threads state that you need to be on a "compatible" base first.
Xperia Z (C6603) 10.3.1.A.0.244 - Generic - Central Europe
but you may have to downgrade your kernel to a 243 version to flash , then restore the 244 kernel , to be able to maintain root ..
There are several guides for this ..
Watcher64 said:
If you are flashing the newer roms you need to update to an newer kernel bootloader first ..
The stock you are flashing is older ...
If you don't have the newer kernel you will appear to have soft bricked ..
Most of the rom threads state that you need to be on a "compatible" base first.
Xperia Z (C6603) 10.3.1.A.0.244 - Generic - Central Europe
but you may have to downgrade your kernel to a 243 version to flash , then restore the 244 kernel , to be able to maintain root ..
There are several guides for this ..
Click to expand...
Click to collapse
Thank you! That was it. Before kernels were usually packaged with the ROM's, is the reason they are not with the xperiaZ, because some phones have locked/unlocked bootloader? So different kernal/rom combos?
bobo89 said:
Thank you! That was it. Before kernels were usually packaged with the ROM's, is the reason they are not with the xperiaZ, because some phones have locked/unlocked bootloader? So different kernal/rom combos?
Click to expand...
Click to collapse
It's just the way it is with SE/Sony Phones.
XperienceD said:
It's just the way it is with SE/Sony Phones.
Click to expand...
Click to collapse
They are locked by default. Even more, if tour Phone is carrier branded, only Sony can unlock it.
Even in that case, most probably they Will not unlock it
Sent from my C6603 using xda app-developers app
Related
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
hi guys, i have some issues during installation process. when i try to install any ROM it just dont accept it. ive followed exact instructions and checked for my version, baseband, rooted, installed xrecovery, wiped data, install rom, again full wipe and again it seems that doesnt work. i checked also for requirements, i have unlocked bootloader, have stock kernel but no lucky at all. im desperate, i dont wanna to stuck again with eclair because its poor in comparation with >2.2. i havent mentioned that earlier about 3 months ago i succed to install gingerv20 without any problem but now i cant. pls help
If you have unlocked your bootloader then why are you on stock kernel?? :what:
Flash the correct & latest nAa or alfs kernel and then the corresponding compatible rom.
Also don't do full wipe AFTER you have flashed the rom!!
Sent from my E15i using xda app-developers app
U are not mentioning that u have installed a kernel with flashtool. If you are using a Rom which requires custom kernel then you have to flash first it with flashtool
Sent from my ST26i using xda app-developers app
You better use cwm instaid of xrecovery. If you have indeed unlocked your bootloader then you can install the kernel with flashtool and the cwm will be included. Also as i have already told you see what kernel the rom works with!
hey guys, when i choosed what rom i will download, in requrement said that will work with stock kernel and i didnt flashed it. but before that rom i flashed it with flashtool to try others and also didnt work...im not that noob, i can read but im sure that i srewed something up...i'll continue to try and i'll let u know have i succed...tnx anyway
After many roms tryed i finally succed to install 'Update-GingerElite.V2', and i didnt FULL WIPED after installing it as ''cdeox8'' said, and he was right. In requrements just said that that need to be rooted, Baseband 015, Sony Ericsson Stock Kernel and that was true, but i tryed few of roms who required same things but they didnt work. Anyway im not gonna to risk anymore with roms, i like this GingerElite so im gonna keep it for the moment. When i buy other phone im goona make some experiments tnx guys anyway
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.
So i rooted and had custom roms on my Z1 lastyear but had to go back to origional due to network issues i had and left it stock since going through rooting it and the whole process i didnt want to do again.
the problem i am having is the original threads that I looked up ALL the download links for the files required and Nut's .ftf are unavailable...
is there any new links threads that im missing out on? i looked at the thread on the development forum but same deal , dead links
currently sitting at
C6906
4.3
3.4.0-perf-g4f35567
14.2.A.0.290
i believe this is the rom i need to downgrade to hence why i didnt update.
any help would be appreciated. i can use the guides for the process and commands to use inside flashtool, i just need the correct files so i dont have the incorrect network problems i had before, and i dont want to brick my phone either.
Files needed for custom recovery to root and install custom rom
sorvis said:
So i rooted and had custom roms on my Z1 lastyear but had to go back to origional due to network issues i had and left it stock since going through rooting it and the whole process i didnt want to do again.
the problem i am having is the original threads that I looked up ALL the download links for the files required and Nut's .ftf are unavailable...
is there any new links threads that im missing out on? i looked at the thread on the development forum but same deal , dead links
currently sitting at
C6906
4.3
3.4.0-perf-g4f35567
14.2.A.0.290
i believe this is the rom i need to downgrade to hence why i didnt update.
any help would be appreciated. i can use the guides for the process and commands to use inside flashtool, i just need the correct files so i dont have the incorrect network problems i had before, and i dont want to brick my phone either.
Click to expand...
Click to collapse
Ok so you should first download Z1-lockeddualrecovery2.8.3-RELEASE.installer.zip, just google it, I cant put links up.
Unzip it and execute the install script, make shure you activate USB Debbuging, it will ask you if you are rooted or not, if not it will still install custom recovery and you can root from there, you can also flash custom roms from there.
just a few things i gotta clear up if someone could answer :
Since im on a locked bootloader, which development thread do i use...
do i flash custom kernals or no? (pretty sure this would brick since the bootloader is locked?)
i know how to flash customs i just dont wanna go through the process of soft bricking and getting flashmod and sony to restore it like last time...
Edit:
i can get it rooted, and dual recovery installed... but every rom i try to install (even when it says its compatable) i get a sony logo or nothing at all...
do i have to update to 490 first?
Hi guys, i have an s4 active i9295 with a bootloop, so i decided to flash stock rom via odin as i always did with samsung phones with this problem but every time i flash a rom (i tried different ones) the phone restarts as normal but when the samsung logo appears then it says on the top left with blue letters revocery booting, then it does something with a progress bar and an android logo above and restarts. When it boots again its back at the bootloop, im an absolute noob in this but what i understand is happening is that the phone is reverting the flash i did with odin and i want to know what am i doing wrong, is this supposed to happen? Any help will be much appreciated
Hello,
Welcome to XDA.
To better assist you, your thread will be moved to your device Q&A forum linked below.
http://forum.xda-developers.com/galaxy-s4-active/help
The experts there may be able to help. Good luck.
I need help, its quite an expensive phone to just give up and throw it away
nexware said:
Hi guys, i have an s4 active i9295 with a bootloop, so i decided to flash stock rom via odin as i always did with samsung phones with this problem but every time i flash a rom (i tried different ones) the phone restarts as normal but when the samsung logo appears then it says on the top left with blue letters revocery booting, then it does something with a progress bar and an android logo above and restarts. When it boots again its back at the bootloop, im an absolute noob in this but what i understand is happening is that the phone is reverting the flash i did with odin and i want to know what am i doing wrong, is this supposed to happen? Any help will be much appreciated
Click to expand...
Click to collapse
C'mon guys you may know what is going on with my s4, no matter what i do it bootloops, tried everithing
pit + firmware on odin, still bootloops, wipe data/cache after and before flashing, still bootloops, i researched a lot and tried almost everithing with the same result, please help me, i'll personally bake a cake to the first nice guy to help me get out of the bootloop
nexware said:
C'mon guys you may know what is going on with my s4, no matter what i do it bootloops, tried everithing
pit + firmware on odin, still bootloops, wipe data/cache after and before flashing, still bootloops, i researched a lot and tried almost everithing with the same result, please help me, i'll personally bake a cake to the first nice guy to help me get out of the bootloop
Click to expand...
Click to collapse
I'll try to help you, what did you install or modify that caused the bootloop in the first place? Was your device rooted? Did you have custom recovery? What recovery? Did you have a custom ROM? What ROM?
Droidriven said:
I'll try to help you, what did you install or modify that caused the bootloop in the first place? Was your device rooted? Did you have custom recovery? What recovery? Did you have a custom ROM? What ROM?
Click to expand...
Click to collapse
I received the phone as it is with the bootloop, don't know much of its state before but i was told that it was a bad flashing procedure the cause of the problem. It had stock recoverys from the different roms i flashed in odin: I9295XXUDOB4
I9295XXUCNE5
I9295VJUDOF1
There was one time i managed to make it boot flashing CWM and installing cyanogenmod 12.1 but on restart it kept bootlooping again and i was unable to get it to boot again even repeating exactly the same steps i did before.
I want to make an absolute clean firmware flash with the original rom that this phone came in my country (VJUBMK4) but from what i understand once im on newer versions (im not sure if 4.3 or 5.0) i cant downgrade.
I really don't know what is it causing the bootloop, how can i get the pone to factory firmware? Am i doing something wrong?
nexware said:
I received the phone as it is with the bootloop, don't know much of its state before but i was told that it was a bad flashing procedure the cause of the problem. It had stock recoverys from the different roms i flashed in odin: I9295XXUDOB4
I9295XXUCNE5
I9295VJUDOF1
There was one time i managed to make it boot flashing CWM and installing cyanogenmod 12.1 but on restart it kept bootlooping again and i was unable to get it to boot again even repeating exactly the same steps i did before.
I want to make an absolute clean firmware flash with the original rom that this phone came in my country (VJUBMK4) but from what i understand once im on newer versions (im not sure if 4.3 or 5.0) i cant downgrade.
I really don't know what is it causing the bootloop, how can i get the pone to factory firmware? Am i doing something wrong?
Click to expand...
Click to collapse
Ah, it sounds like you have one of the devices with locked bootloaders then if you can't downgrade, if that is the case you can't use CWM, TWRP, CM or AOSP custom ROMs, those devices have to use Safestrap and modified Stock ROMs. Or you may can unlock the bootloader. I'm not sure that is your problem but you can check it out.
You can flash the newest stock firmware and just be done with it, you may not be able to root and flash custom but the device will at least work.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
Ah, it sounds like you have one of the devices with locked bootloaders then if you can't downgrade, if that is the case you can't use CWM, TWRP, CM or AOSP custom ROMs, those devices have to use Safestrap and modified Stock ROMs. Or you may can unlock the bootloader. I'm not sure that is your problem but you can check it out.
You can flash the newest stock firmware and just be done with it, you may not be able to root and flash custom but the device will at least work.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
How can i be sure that the device has a locked bootloader? If that's the case, what can i do to make it to just work as stock? I need a special kind of stock firmware?
nexware said:
How can i be sure that the device has a locked bootloader? If that's the case, what can i do to make it to just work as stock? I need a special kind of stock firmware?
Click to expand...
Click to collapse
Boot into download mode by holding the volume down + power button and see what is the device name listed there
nexware said:
How can i be sure that the device has a locked bootloader? If that's the case, what can i do to make it to just work as stock? I need a special kind of stock firmware?
Click to expand...
Click to collapse
Take the cover off and pull the battery, the label under the battery should have the model number for the phone.
If the model is GT-i9295, then you have an unlocked bootloader and should be able to flash any firmware.
If the model is SGH-i537, then you have a locked bootloader and can only flash firmware meant for that phone.
Once we know which phone you have we can help you.
JASONRR said:
Boot into download mode by holding the volume down + power button and see what is the device name listed there
Click to expand...
Click to collapse
It says this:
PRODUCT NAME: GT-I9295
CURRENT BINARY: Custom
SYSTEM STATUS: Official
CSB-CONFIG-LSB: 0x30
SECURE DOWNLOAD : ENABLE
WRITE PROTECTION: ENABLE
eMMC BURST MODE enabled
Devo7v said:
Take the cover off and pull the battery, the label under the battery should have the model number for the phone.
If the model is GT-i9295, then you have an unlocked bootloader and should be able to flash any firmware.
If the model is SGH-i537, then you have a locked bootloader and can only flash firmware meant for that phone.
Once we know which phone you have we can help you.
Click to expand...
Click to collapse
Its GT-i9295
Can you flash VJUCNI1 or VJUDOF1?