Hello, my phone is stuck ath the sony logo, when I restart it it just stays there. What should I do to make my phone work again?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is the last working picture of my phone
mrdjibrilo said:
Hello, my phone is stuck ath the sony logo, when I restart it it just stays there. What should I do to make my phone work again?
Click to expand...
Click to collapse
Stock, no root or recovery?
Have you used flashtool before?
EDIT: First of all turn it off: hold power | volume up untill you feel 3 vibrations. and charge.
ChikeD said:
Stock, no root or recovery?
Have you used flashtool before?
EDIT: First of all turn it off: hold power | volume up untill you feel 3 vibrations. and charge.
Click to expand...
Click to collapse
thanks I did that, the power/volume combo, and it turned off, and then I used this http://talk.sonymobile.com/t5/Xperi...ctions-using-Pc-Companion-Windows/td-p/249946, if anyone has the same problem this will solve it!
mrdjibrilo said:
thanks I did that, the power/volume combo, and it turned off, and then I used this http://talk.sonymobile.com/t5/Xperi...ctions-using-Pc-Companion-Windows/td-p/249946, if anyone has the same problem this will solve it!
Click to expand...
Click to collapse
Now I would recommend building your flashtool flashable firmware file from PCC/SUS files.
flashtool: http://www.flashtool.net/
Guides:
http://mytechencounters.wordpress.c...eate-an-ftf-file-of-your-xperia-ics-firmware/
http://forum.xda-developers.com/showthread.php?t=2188129
ChikeD said:
Now I would recommend building your flashtool flashable firmware file from PCC/SUS files.
flashtool: http://www.flashtool.net/
Guides:
http://mytechencounters.wordpress.c...eate-an-ftf-file-of-your-xperia-ics-firmware/
http://forum.xda-developers.com/showthread.php?t=2188129
Click to expand...
Click to collapse
i was trying to put cyanogenmod's kitkat4, but it failed, and started showing only the sony logo, while trying to fix it(before i saw this thread), i flashed the c-mod's kernel onto my phone, that didnt help, and now i'm not able to update my phone using the sony site link which is given above, it says, "unkown software is present in the phone, so cant install". Somebody please help!! :crying::crying:
dont panic bro
lalithesh said:
i was trying to put cyanogenmod's kitkat4, but it failed, and started showing only the sony logo, while trying to fix it(before i saw this thread), i flashed the c-mod's kernel onto my phone, that didnt help, and now i'm not able to update my phone using the sony site link which is given above, it says, "unkown software is present in the phone, so cant install". Somebody please help!! :crying::crying:
Click to expand...
Click to collapse
stay calm i know how u feel.flashing kernel wont help u cus u missing some system file that why your phone won't boot.Just do as i say
1.download flashtool here the link http://www.flashtool.net/download.php
2.download xperia p stock firmware jb or ics or gb(i recommend jb this link http://forum.xda-developers.com/showthread.php?t=2322163 )
3.learn how to use flashtool (i think already know how to use it but if u dont try to search google)
4.flash it done
work or not please tell me maybe i can help u more
flashtool is ur last option, 1st u need to repair using SUS. since u can open ur phone so its not going to be any problem in repair it using SUS. just open sus, close ur phone and press power and up down button and plug the usb to enter flashmode.
1st of ll power off your phone bu presiing power & Vol+button ubtill you feel 3 vibrations,then Charge your phone for atleast 1 hr.Then flash the stock JB/ICS/GB firmware (ftf(including kernel)),whichever you want.Thats it!
dara007_168 said:
stay calm i know how u feel.flashing kernel wont help u cus u missing some system file that why your phone won't boot.Just do as i say
1.download flashtool here the link http://www.flashtool.net/download.php
2.download xperia p stock firmware jb or ics or gb(i recommend jb this link http://forum.xda-developers.com/showthread.php?t=2322163 )
3.learn how to use flashtool (i think already know how to use it but if u dont try to search google)
4.flash it done
work or not please tell me maybe i can help u more
Click to expand...
Click to collapse
Thanks a lot dara, really appreciate your help.., I did what u told me to, and my phone is up and running now...! I had the flashtool, I flashed the stock .100 firmare on to my phone, and then moved on to the honami ROM.. Sorry for the late reply....
lalithesh said:
Thanks a lot dara, really appreciate your help.., I did what u told me to, and my phone is up and running now...! I had the flashtool, I flashed the stock .100 firmare on to my phone, and then moved on to the honami ROM.. Sorry for the late reply....
Click to expand...
Click to collapse
good to hear that bro
Sent from my Xperia U using xda app-developers app
Same problem on my XU with Honami
I have been facing the same problem with Honami on my Xperia U. I used the experimental v12 kernal. DO not reboot your phone (eihter in cwm or normal reboot). I was switching my sim and I forgot that the phone would reboot. It got stuck and I had to use flashtool, reroot and go thru the pain. This has happened thrice to me now. Dont let your phone reboot, restart. If you want to restart, then power off and then power on.
I am kinda scared that if this happens when I am away, I wont be able to repair the phone without a computer, flashtool, stock kernal, firmware. Even cwm is not accessible when this happens and its very scary.
The Rom otherwise is the smoothest JB you'll find, everything works well. I have already put in all the usual apps like whatsapp, gmail, hangout, stock fm radio from xperia, maps etc. No facebook - it is process and memory hogger.
I want to build a flashable ftf of my current setup of honami so I can flash it using flashtool. How do I do that. I dont want to flash the stock firmware and then restore the honami everytime. Is it possible to build an ftf and a boot.img kernal of your custom rom and kernal to flash with flashtool?
lalithesh said:
Thanks a lot dara, really appreciate your help.., I did what u told me to, and my phone is up and running now...! I had the flashtool, I flashed the stock .100 firmare on to my phone, and then moved on to the honami ROM.. Sorry for the late reply....
Click to expand...
Click to collapse
hi,
when you downloaded the rom from the link,
was is in *.tar format?
how did you manage to use it in flashtool?
thanks in advance.
Edits...
google-ed & got the full rom in *.tff format from the following link:
h t t p:// android.sc/install-official-jelly-bean-4-1-2-6-2-a-1-100-firmware-on-sony-xperia-p/
booting into 6.2.A.0.400
Stuck at Sony Logo
Heres the entire story which i posted as question but havent recieved a reply yet. Hope someone checks this and helps
OK i ve been trying to flash a new custom rom on my Xperia P, i looked at a number of guidelines and doing things step by step.
Since im very new to this i downloaded a few Roms. I was following the guide "http://droidors.com/2014/07/08/update-xperia-p-lt22i-to-android-4-4-4-kitkat-with-slimkat-custom-rom/2/" and everything was going fine. I reached the step to "fastboot flash boot boot.img", i did that and then went on the next step to boot in CWM Recovery and install the zip rom and the Gapps. During the Zip Rom install i got status 7 error.
Now, i noticed that i might have flashed the wrong Rom so rechecked the guide and installed the correct Rom which is mentioned in "http://forum.xda-developers.com/xperia-u/p-development/rom-slimkat-4-4-2-release-candidate-t2657795" and installed it through Fastboot. But now THE PROBLEM IS, AFTER I FLASHED THE INCORRECT IMG, MY PC IS NOT RECOGNISING THE XPERIA P SAYING IT DOESNOT RECOGNISE THE DRIVERS, therefore im not able to copy the ROM Zip on the SDcard, to then run it from CWM.
Please help.
After sometime i tried the below
After I flashed the SlimKat Rom, and things went out of hand ( till this point i could see Slimkat logo at boot and could also go in CWM Recovery ), I tried to restore through Nandroid Backup i had done. As soon i selected the restore option and then the backup file, within 2-3 seconds the phone went off, and then on boot all i can do is see "SONY" on screen. Nothing else happens.
Ok, now i tried to flash the stock Rom through this link "http://forum.xda-developers.com/xperia-u/p-development/ftf-firmware-xperia-p-generic-world-t2322163", through flashtool to bring my phone back to life. I installed the drivers as per instructions from drivers folder, but for some reason the pc is just not accepting. I did install through this exact method yesterday night and it worked perfectly.
Please suggest. I hope im asking at the right place.
Urgent help please
Kindly advise, im stuck with no spare phone.
OK, the flashing tool from Sony, EMMA enabled me to flash the jb firmware (it recognised my xperia p ) . once I got that working I managed to flash Cm11 on my device, with assistance from another user..
Thanks.. Hope it helps someone
General info on how to come out of soft brick, or bootloop, or status 7 error.
What you did is the right thing.
For someone who might experience the same thing ( flashed the kernel, got some error, and is stuck at bootloop), or has got the status 7 error, follow the below steps:
1) Download the LT22i_6.2.A.1.100.ftf file from the net, google a bit and u will find a download link.
1) Press and hold the power button + Vol Up. The phone vibrates once, and then after about 2 seconds, vibrates thrice, only then leave the keys. IT IS IMPORTANT TO WAIT FOR 3 VIBRATES. The phone is powered off now.
2) Hold the vol Up key and connect to the pc, it will connect in the fastboot mode, indicated by a violet notification light. If u dont get the violet light, you have not connected in the fast boot mode. remove the connection and repeat the above steps if necessary.
3) In flashtool, select the ftf file and carry on with the next instructions.
4) When it asks you to disconnect the phone and connect by holding menu key, disconnect the phone, hold the vol down key and connect it back. The flashing process will continue.
5) Disconnect once its done. Start the phone, wait till it loads up, Restart again, let it settle for about 5 min, you are good to go.
For status 7 error:
It is usually caused because of the kernel and rom not being compatible, or if the kernel is not compatible with the phone.., Follow the above steps to come out of it, find the right kernel and proceed as usual.. Hope this will help someone, Press thanks if it did.., Cheers.
I have a sony v3+ when i start it,it has stucked on the sony logo. what do i do
Related
There is people out there that can't figure out how to use PC Companion to fix their phones, this tutorial is going to show you how to reinstall the stock Android 2.3 SE firmware and Kernel wich is usefull if you are stuck at the SE Logo, experiencing battery drain issues or if you just want to make a fresh install of a custom ROM
I am not responsible if you break your phone (more than it is already ) so do it at your own risk.
This is a really easy process so keep calm if you follow all the steps i bet your phone will be fixed
Before doing this you have to consider a couple of things:
You are going to lose all your data.
If your phone is Rooted, Root will be gone (you are going to lose superuser and xrecovery aswell).
Phone it's going to be like if it was brand new (it will include all the Service Provider useless apps and default settings).
Be sure to have at least 50% of battery life because PC Companion is going to download the stock ROM from server when your X10 is already connected in flash mode and this could take a while. If you need to charge the battery and you are stuck at SE logo: take the battery out, connect phone to charger then put the battery in.
External Memory will be formatted so your photos, music and everything in SD will be wiped.
Ok, Let's do it!!
- Don't Connect your phone to USB yet and Open PC Companion. (if Support Zone doesn't show up restart your PC and try again)
Then just follow the instructions:
1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2.
3.
4.
[/IMG]
5.
6.
Sometimes after this step it says something about Server Connection Error or something, this means your PC can't connect to SE servers so you should check your internet connection or your firewall settings, sometimes SE servers are down (happened to me, if this is the case just try again later).
7.
8. Now this is the tricky part BE SURE TO HAVE AT LEAST 50% BATTERY LEFT BEFORE DOING THIS STEP and turn your phone off:
If in this step your phone turns on to the SE logo instead of the GREEN LED just unplug your phone, take the battery out and try to put the battery in first but inmediately after press and hold the back button and plug X10 to USB, then green led will appear and release back button
After 15 minutes or something (it depends on your PC's internet connection speed) your phone will be flashed and it will restart by itself and it will be fixed
Sorry if my english sucks it isn't my native language xD
Hope this helps all the noobies out there! and don't worry your PC Companion won't be in spanish like mine, peace
Very Good
Great post there my friend! easy simple to follow (even though pc companion is in Spanish ). My question is what if the phone does not want to boot at all? So no S.E. logo appears or anything, can the pc companion still repair the x10 and get it to work again? not that mine is just curious...
now this message..
Agera said:
Great post there my friend! easy simple to follow (even though pc companion is in Spanish ). My question is what if the phone does not want to boot at all? So no S.E. logo appears or anything, can the pc companion still repair the x10 and get it to work again? not that mine is just curious...
Click to expand...
Click to collapse
If you are able to set X10 into Flash Mode it still can be flashed, the only problem would be how to charge the battery.
Sent from my X10i using XDA App
romasalah said:
now this message..
Click to expand...
Click to collapse
Try running PC Companing like an admin, if the problem continues try uninstalling/reinstalling PC Companion, by the way sometimes the SE server is down so you may get an error about it, when that happens just try again later.
CescVicious said:
If you are able to set X10 into Flash Mode it still can be flashed, the only problem would be how to charge the battery.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Its my friends phone, he cant fix it nor can be bothered so he went and got himself another phone and is willing to sell the phone to me for $100, but his telling me it wont boot at all.. so if use my battery instead of his there might be a possibility i can get it going into flash mode?
Agera said:
Its my friends phone, he cant fix it nor can be bothered so he went and got himself another phone and is willing to sell the phone to me for $100, but his telling me it wont boot at all.. so if use my battery instead of his there might be a possibility i can get it going into flash mode?
Click to expand...
Click to collapse
Maybe, but the only way to be sure is doing it
i do all the steps but when its trying to connect to the phone it says to me to tab mount while i'm stuck at SE logo
Is there any way to go from 2.1 back to 1.6. My wife has this phone and hates the new update.
Sent from my Inspire 4G using XDA Premium App
So if i follow that it will return my phone to stock firmware? So xrecovery gone as well?
Andybrit said:
So if i follow that it will return my phone to stock firmware? So xrecovery gone as well?
Click to expand...
Click to collapse
Yes xrecovery will be gone.
Sent from my X10i using XDA Premium App
Ok thanks. I haven't rooted my phone yet (only got it a few days ago), but i could root my phone, installed xrecovery and enable JIT. Then once gingerbread comes out i do this and restore it back to normal and upgrade using sony's updater?
Yes I am pretty sure.
Sent from my X10i using XDA Premium App
Is there any way I can put on any kind of rom when all of my partitions are empty (hence stuck on Sony Ericsson Logo), and the usb port is broken?
Thanks CescVicious. it works finanly.
Do you need a video how to repair your phone ? +.+
pc companion does not repair
hiii i tried to repair my x10i but pc companion says software not available...
any other solutionnnn????
I'm having the same problem as Mr. Hello. I'm not exactly experienced at this, but I've flashed my phone about 7 times since the first 2.1 appeared before the official release. I'm currently running 2.3 cyanogenmod 7. I've given it about 2 months worth of testing and regardless of what people have said, it's the worst of the three 2.3 roms I've tried. The only feature I truly enjoy that most mods don't have is the auto screen orientation for all apps including the app menu. I found a nice stock 2.3 and I'd like to try it out and wanted a fresh stock base to go from. I thought this would be less work than finding the appropriate firmware/baseband/rom but its turning into more. Any help would be appreciated.
Right now i am on xperia s rom android version 2.3.4 unlocked bootloader can i use this guide and will i be able to get the stock rom back
Goder101 said:
I'm having the same problem as Mr. Hello. I'm not exactly experienced at this, but I've flashed my phone about 7 times since the first 2.1 appeared before the official release. I'm currently running 2.3 cyanogenmod 7. I've given it about 2 months worth of testing and regardless of what people have said, it's the worst of the three 2.3 roms I've tried. The only feature I truly enjoy that most mods don't have is the auto screen orientation for all apps including the app menu. I found a nice stock 2.3 and I'd like to try it out and wanted a fresh stock base to go from. I thought this would be less work than finding the appropriate firmware/baseband/rom but its turning into more. Any help would be appreciated.
Click to expand...
Click to collapse
Have you tried it yet? What happened?
sudersanmurthy said:
Right now i am on xperia s rom android version 2.3.4 unlocked bootloader can i use this guide and will i be able to get the stock rom back
Click to expand...
Click to collapse
Yes works on all Xperias to go back to 100% stock. Pretty sure this relocks bootloader and everything.
~Jaramie
from my LT28at rooted & eating an Ice Cream Sandwich
alright..
i've read possibly 5 or 6 threads from start to end, post by post last week..
some people faced similiar problems but none of them faced exactly the same..
only one guy did, but i don't know if he could solve it or not..
i'm trying to install Wolf's gingerbread ROM but i have a problem on flashing..
i've downloaded all the files in this topic and followed all the directions there correctly..
i have installed SEMC Flash Drivers..
tried different USB ports..
but i keep receiving this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
anyone faced the same problem before or can help about solving it?
*
edit:
here is a similiar thread but i get the error sooner..
**
edit:
this either didn't work..
the green led never turn on, until i put the battery back in..
***
edit:
can this be the problem:
in the tutorial's pictures "Firmware Content" frame shows the included .sin file
****
edit:
I solved the problem with a very wierd way.
Hope it helps when you try.
After you've extracted and installed Flashtool;
go to your computer's Control Panel.
Open "Clock, Language and Region".
Click "Region and Language".
Choose format as English (United Kingdom); and location as United States.
Click ok and close control panel.
Now you shold be able to see loader.sin and kernel.sin files inside "Firmware Content" frame when you open Flashtool.
Same error to me...I try everything, every tool that I found for X10 but nothing help it...I also try wotan server with several different firmwares but always same error...ERROR: file header write failed!
I think that is imposible to repair without some dongle like setool...
i try to help...
1.first root ur stock rom n install xrecovery....
2.backup stock rom using xrecovery..
3.wipe data, wipe cache, n wipe dalvik cache using xrecovery...
4. install wolfbreak rom using "XRECOVERY".. When finish, put out the battery
5.lastly install the 2.3.3 n .71 baseband using flashtool....
phobias1903 said:
edit:
can this be the problem:
in the tutorial's pictures "Firmware Content" frame shows the included .sin file
Click to expand...
Click to collapse
wtf dude, you are missing some files there!??! "loader.sin & kernel.sin" ... try re-downloading the flashtool from that thread (http://forum.xda-developers.com/showthread.php?t=1196808)
cikgu senaman said:
1.first root ur stock rom n install xrecovery....
Click to expand...
Click to collapse
man, thats the point where we have problem..
slikk76 said:
wtf dude, you are missing some files there!??! "loader.sin & kernel.sin" ... try re-downloading the flashtool from that thread (http://forum.xda-developers.com/showthread.php?t=1196808)
Click to expand...
Click to collapse
i have downloaded them but i'll try again..
Hey I've had the same exact problem for about 3 months now I've tried everything i can think of.
i even made a battery charger from a usb cord to make sure it wasn't the battery being dead...
D:
any news?
I was having the EXACT same issue that led me to this thread. I had a custom kernal loaded so not sure if that was why I was getting "error flash aborted". Anyhow as someone mentioned here, I held down the back button until the entire flash was completed. That finally worked. Thanks!
One2many said:
I was having the EXACT same issue that led me to this thread. I had a custom kernal loaded so not sure if that was why I was getting "error flash aborted". Anyhow as someone mentioned here, I held down the back button until the entire flash was completed. That finally worked. Thanks!
Click to expand...
Click to collapse
I've had this issue for about a month, I'll try your method when i get home
I had come to the conclusion it was some kind of NAND deterioration
AusX10 said:
I've had this issue for about a month, I'll try your method when i get home
I had come to the conclusion it was some kind of NAND deterioration
Click to expand...
Click to collapse
hi! have you somehow restored your x10 back to life?
if it is NAND problem, have someone found a way to repair/replace it?
necrohades said:
hi! have you somehow restored your x10 back to life?
if it is NAND problem, have someone found a way to repair/replace it?
Click to expand...
Click to collapse
Nope sorry mate I have two devices, that's why i assume its hardware failure because they were both flashed the same way and my primary one is fine (running FXP45)
The bricked X10 is actually from a much newer batch which is odd, you would think the first one to die would be the one i have been flashing roms on since i debranded my 1.6 rom!
The phone is beyond my help now i think because its not even getting into flash mode and neither SEUS or flashtool can see it. It slowly got worse and worse until it wouldn't do anything at all.
I have been using Wolf's tweaked GB ROM for ten days.
I solved the problem with a very wierd way.
Hope it helps when you try.
After you've extracted and installed Flashtool;
go to your computer's Control Panel.
Open "Clock, Language and Region".
Click "Region and Language".
Choose format as English (United Kingdom); and location as United States.
Click ok and close control panel.
Now you shold be able to see loader.sin and kernel.sin files inside "Firmware Content" frame when you open Flashtool.
X10 failure in flashing ROM
I experienced a very hard situation after an unsuccessful ROM flashing onto my x10. Flashing procession was nearly finished but error message was happened and then aborted! Since that my device was permanently unbootable at all, when press the switch button to turn it on, there was no vibration nor SE boot up logo, just a red light brinked up for a few seconds. It seemed to be permanently dead. I tried many ways to reflash ROM onto the device via SE PC Companion, SESU, FlashTool but the program couldn't detect the device nor wiring on flash mode.
The device could not be accessed at all. Is there any experts who can solve this problems, please show me and the other owners how to fix X10 in this matter upon the software; programs, and the obvious procession. That would be greatly appreciated.
tommyboy_bkk said:
I experienced a very hard situation after an unsuccessful ROM flashing onto my x10. Flashing procession was nearly finished but error message was happened and then aborted! Since that my device was permanently unbootable at all, when press the switch button to turn it on, there was no vibration nor SE boot up logo, just a red light brinked up for a few seconds. It seemed to be permanently dead. I tried many ways to reflash ROM onto the device via SE PC Companion, SESU, FlashTool but the program couldn't detect the device nor wiring on flash mode.
The device could not be accessed at all. Is there any experts who can solve this problems, please show me and the other owners how to fix X10 in this matter upon the software; programs, and the obvious procession. That would be greatly appreciated.
Click to expand...
Click to collapse
blinking red you say?
try to charge your battery first, probably using a desktop charger, or another fully charged battery, and re-do flashing through either SEUS or repair thru PCCompanion.
blinking red led indicates battery power too low to boot.
if that fails, i'm afraid you have to try and see a tech
phobias1903 said:
After you've extracted and installed Flashtool;
go to your computer's Control Panel.
Open "Clock, Language and Region".
Click "Region and Language".
Choose format as English (United Kingdom); and location as United States.
Click ok and close control panel.
Click to expand...
Click to collapse
I was able to flash back to stock generic firmware 2.0.A.0.504 using this, not sure if this was the fix or coincidental. Using X10 Flash tool 0.5.3.0.
From there I have flashed the correct BB, Doom kernel for unlocked and recovery yadda yadda. The phone lives (for now...)
Hi All,
I have an Xperia Z2 D6503 South Africa (Vodacom) .402
I would like to de-brand it and possibly root it (will think on this).
Currently I am downloading D6503_17.1.2.A.0.314_Generic CA.ftf. Is this the right thing to do?
I am looking at XperiFirm but I am not sure how to find generic firmware there. I do get an option for 1281-8114/South Africa/Customized ZA (ver 314). What is this Customized operator? Is it essentially generic?
Currently I really hate Vodacom's customization. had them on my S3, S4 and now Z2 and they just break all the time. Plus I can barely use my dialer/contacts/call log so just want to reload but preferably sans operator crap.
I know there are plenty of threads out there that may possibly answer this question for me but I have not been able to find much regarding South African firmware and I am loath to just wing it without a little info from someone in the know.
Any help would be much appreciated!
Many Thanks
Tarn
tarnalcock said:
Hi All,
I have an Xperia Z2 D6503 South Africa (Vodacom) .402
I would like to de-brand it and possibly root it (will think on this).
Currently I am downloading D6503_17.1.2.A.0.314_Generic CA.ftf. Is this the right thing to do?
I am looking at XperiFirm but I am not sure how to find generic firmware there. I do get an option for 1281-8114/South Africa/Customized ZA (ver 314). What is this Customized operator? Is it essentially generic?
Currently I really hate Vodacom's customization. had them on my S3, S4 and now Z2 and they just break all the time. Plus I can barely use my dialer/contacts/call log so just want to reload but preferably sans operator crap.
I know there are plenty of threads out there that may possibly answer this question for me but I have not been able to find much regarding South African firmware and I am loath to just wing it without a little info from someone in the know.
Any help would be much appreciated!
Many Thanks
Tarn
Click to expand...
Click to collapse
Yes, "Customized" firmwares are those debranded ones.
You'll be fine with the Customized ZA.
Jackos said:
Yes, "Customized" firmwares are those debranded ones.
You'll be fine with the Customized ZA.
Click to expand...
Click to collapse
Thank you Jackos! Wasn't expecting such a fast response! I really appreciate it! :good:
BRICKED!
So I managed to brick my Z2 using the latest version of FlashTool/Xperifirm.
I upgraded it to 4.4.4, using a Generic UK variant as it is not yet available in my country, and my battery started draining tons faster and half of my apps would just close randomly (no errors) almost as if the back button was being pushed so much so that I could not type any messages or anything.
I tried to re-flash the previous 4.4.2 version (RSA Generic) and that just resulted in a boot loop. So I am back up and running using 4.4.4 but it is not going too well. Could anyone please give me some advice on the best step forward?
tarnalcock said:
So I managed to brick my Z2 using the latest version of FlashTool/Xperifirm.
I upgraded it to 4.4.4, using a Generic UK variant as it is not yet available in my country, and my battery started draining tons faster and half of my apps would just close randomly (no errors) almost as if the back button was being pushed so much so that I could not type any messages or anything.
I tried to re-flash the previous 4.4.2 version (RSA Generic) and that just resulted in a boot loop. So I am back up and running using 4.4.4 but it is not going too well. Could anyone please give me some advice on the best step forward?
Click to expand...
Click to collapse
Let me get a few screen shots ready then I'll help... I bricked mine last week - no issues...
---------- Post added at 03:13 PM ---------- Previous post was at 02:54 PM ----------
Here is what you should do:
01] Install the following drivers (assuming that flashtool is already installed) C:\Flashtool\drivers\Flashtool-drivers.exe and select the first two boxes as shown and the Z2 boxes at the bottom:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
01] Load Flashtool
02] Turn off the phone
03] Hold down the Vol-down button (and keep it down) and plug in the USB (hold the buttol will you see some output in Flashtool). You should see Windows install the Flashmode drivers in your taskbar if it has not done so yet. Flashtool should also show that the device is in flashmode. It is crusial that these flashmode drivers are installed before flashing. Just to make sure that the flashmode drivers are installed, remove the USB and repeat the pressing of Vol-Down whilst plugging the USB.
If all seems fine with flashmode in flashtool, remove device and go on to selecting the shown FTF, double click it after it is queried from the server and build the FTF ON YOUR OWN PC. Do not download an FTF from a site. They could be damaged. When selecting the files to build the FTF, select all files EXCEPT the *.ta ones. They should NOT be selected.
Then flash with the following boxes ticked and unticked:
Puffin617 said:
Let me get a few screen shots ready then I'll help... I bricked mine last week - no issues...
---------- Post added at 03:13 PM ---------- Previous post was at 02:54 PM ----------
Here is what you should do:
01] Install the following drivers (assuming that flashtool is already installed) C:\Flashtool\drivers\Flashtool-drivers.exe and select the first two boxes as shown and the Z2 boxes at the bottom:
01] Load Flashtool
02] Turn off the phone
03] Hold down the Vol-down button (and keep it down) and plug in the USB (hold the buttol will you see some output in Flashtool). You should see Windows install the Flashmode drivers in your taskbar if it has not done so yet. Flashtool should also show that the device is in flashmode. It is crusial that these flashmode drivers are installed before flashing. Just to make sure that the flashmode drivers are installed, remove the USB and repeat the pressing of Vol-Down whilst plugging the USB.
If all seems fine with flashmode in flashtool, remove device and go on to selecting the shown FTF, double click it after it is queried from the server and build the FTF ON YOUR OWN PC. Do not download an FTF from a site. They could be damaged. When selecting the files to build the FTF, select all files EXCEPT the *.ta ones. They should NOT be selected.
Then flash with the following boxes ticked and unticked:
Click to expand...
Click to collapse
Wow! Thank you for the informative post there Puffin. This is the same process I used to unbrick it but I had to stick with the newer ftf (4.4.4). Supposedly something to do with partitioning. Will ticking the boxes as you have done allow me to switch back to 4.4.2?
tarnalcock said:
Wow! Thank you for the informative post there Puffin. This is the same process I used to unbrick it but I had to stick with the newer ftf (4.4.4). Supposedly something to do with partitioning. Will ticking the boxes as you have done allow me to switch back to 4.4.2?
Click to expand...
Click to collapse
I did. I was on 4.4.4. I bricked my device by trying to install the TWRP recovery 2.8. I flashed the 314 (4.4.2) build to get my phone unbricked and started over...
PS: This does a full wipe of internal sdcard
Puffin617 said:
I did. I was on 4.4.4. I bricked my device by trying to install the TWRP recovery 2.8. I flashed the 314 (4.4.2) build to get my phone unbricked and started over...
PS: This does a full wipe of internal sdcard
Click to expand...
Click to collapse
I will try that. Thank you. Initially 4.4.4 seemed to be behaving but it has started doing random things again. Which is sad. I like the new look. And there are some nice little features I could get used to. Really don't know how they could release it so buggy. Then again I am way ahead of my country's release cycle. By the time we get 4.4.4, Lollipop will be old news already hahaha.
del.
Thanks Puffin617!
Thank you Puffin617. I was able to restore my phone as described.
I think the trick was ultimately ticking the 'Data' box which then overwrote the partition as I had previously left this un-ticked to preserve my data.
tarnalcock said:
Thank you Puffin617. I was able to restore my phone as described.
I think the trick was ultimately ticking the 'Data' box which then overwrote the partition as I had previously left this un-ticked to preserve my data.
Click to expand...
Click to collapse
Yip. Appart from the /data partition, that /sdcard/Android/data folder on the internal sd card is a poison when updating/changing between ROMs. I delete that folder EVERY time I flash a ROM.
Puffin617 said:
Yip. Appart from the /data partition, that /sdcard/Android/data folder on the internal sd card is a poison when updating/changing between ROMs. I delete that folder EVERY time I flash a ROM.
Click to expand...
Click to collapse
Good to know! Do you think that is what may have caused all of my problems with 23.0.1.A.0.32 in the first place? Was such weird behavior!
Volume button never worked
keyboards kept collapsing as if the back button was pushed (stock android/minuum/swiftkey all did the same)
apps would close randomly
Google Play Music would pause every time the screen orientation changed or if I turned a page too fast in Play Books.
Battery drain was significantly faster (10% passive drain in about 1.5 hours)
4k recording would not open, nor would the camera stay open for more than a few seconds (this was very intermittent)
In fact I eventually became convinced that there was a physical fault with the phone, but this is not the case (thank God!).
tarnalcock said:
Good to know! Do you think that is what may have caused all of my problems with 23.0.1.A.0.32 in the first place? Was such weird behavior!
Volume button never worked
keyboards kept collapsing as if the back button was pushed (stock android/minuum/swiftkey all did the same)
apps would close randomly
Google Play Music would pause every time the screen orientation changed or if I turned a page too fast in Play Books.
Battery drain was significantly faster (10% passive drain in about 1.5 hours)
4k recording would not open, nor would the camera stay open for more than a few seconds (this was very intermittent)
In fact I eventually became convinced that there was a physical fault with the phone, but this is not the case (thank God!).
Click to expand...
Click to collapse
23.0.1.A.0.32 was a test build - not an official release. You should've flashed 23.x.x.x.167
Puffin617 said:
23.0.1.A.0.32 was a test build - not an official release. You should've flashed 23.x.x.x.167
Click to expand...
Click to collapse
Ah. My bad I just Googled the version number quickly while posting to be accurate (fail!). haha! I did do 23***167_R2B (Generic UK)
Hey guys!
First of all i do not know if offering a donation for people helping out someone is again the rules here on xda, if so please tell me.
I will make a short intro and tell you that i yesterday received a Z2 from a friend that had upgraded himself with a newer phone so i got this one for free as a gift. (Had an Galaxy SII before)
And guess what, first thing i do is bricking it, genius..
When i got the phone i decided to "what the heck i want to root it" (because i rooted my SII without any problems) Anyhow i looked online and came across this guide made by arul20be, here on xda: http://forum.xda-developers.com/xpe...ck-d6502-03-23-4-0-546-completeguide-t3171219
So i fallowed the guide downloaded everything except that i could not use adb-setup-1.4.2 nor could i use adb-setup-1.4.3. The installation did not extract any files, so i found version 1.3 of ADB and it worked. The rest went flawlessly until i came to the last step, where i booted in to recovery with Dual recovery and installed flashable_D6503_23.4.A.0.546.zip. After that i did as instructed, cleaned cache/dalvik. After that i tried to exit the recovery and choose i think it was "power off system", you guys that are familiar with Dual recovery probably understand where i pressed. After that my phone shut down and after a while either it started up or i started it(don't remember) and it shows the SONY logo, nothing more happened. It didn't not shut down or do anything so i let it be for like an hour or so and then decided to hard shutdown it by pressing power and volume up key. i tried to start it up after a while again to see if maybe something happens, nothing happend and i let the phone be on during the night to see if anything could happen.
So today when the the story was the same i looked online to try to solve the problem, i tried to enter recovery mode by pressing on and then pressing volume up and down but nothing. Did
try to hard factory rest by pressing the red button for a couple of seconds, but nothing. it vibrates three times and then the sony logo comes up again. (is it called bootloop?)
The status now is that the phone, if plugged in to a power source like PC, or wall it will show the SONY logo even if you shut it down with power off and volume up. in other words the phone restarts itself. The only way to shut it down is to do it without a power source.
The fallowing tools+files has been used:
adb-setup-1.3.exe
flashtool-0.9.19.8-windows.exe
rootkitXperia_20140719.zip
Z2-lockeddualrecovery2.7.154-BETA.installer.zip
D6503_17.1.2.A.0.314_UK Generic.ftf
flashable_D6503_23.4.A.0.546.zip
So the thing is that i really want to upgrade myself with a new phone. In the same time i got like under one bitcoin that i had for a while and because of my stupidness i feel like i can donate to that to the first person who engages him/herself to that level so i can use my phone again.
Sorry for the long post! Thanks in advance!
axeljooo said:
Hey guys!
First of all i do not know if offering a donation for people helping out someone is again the rules here on xda, if so please tell me.
I will make a short intro and tell you that i yesterday received a Z2 from a friend that had upgraded himself with a newer phone so i got this one for free as a gift. (Had an Galaxy SII before)
And guess what, first thing i do is bricking it, genius..
When i got the phone i decided to "what the heck i want to root it" (because i rooted my SII without any problems) Anyhow i looked online and came across this guide made by arul20be, here on xda: http://forum.xda-developers.com/xpe...ck-d6502-03-23-4-0-546-completeguide-t3171219
So i fallowed the guide downloaded everything except that i could not use adb-setup-1.4.2 nor could i use adb-setup-1.4.3. The installation did not extract any files, so i found version 1.3 of ADB and it worked. The rest went flawlessly until i came to the last step, where i booted in to recovery with Dual recovery and installed flashable_D6503_23.4.A.0.546.zip. After that i did as instructed, cleaned cache/dalvik. After that i tried to exit the recovery and choose i think it was "power off system", you guys that are familiar with Dual recovery probably understand where i pressed. After that my phone shut down and after a while either it started up or i started it(don't remember) and it shows the SONY logo, nothing more happened. It didn't not shut down or do anything so i let it be for like an hour or so and then decided to hard shutdown it by pressing power and volume up key. i tried to start it up after a while again to see if maybe something happens, nothing happend and i let the phone be on during the night to see if anything could happen.
So today when the the story was the same i looked online to try to solve the problem, i tried to enter recovery mode by pressing on and then pressing volume up and down but nothing. Did
try to hard factory rest by pressing the red button for a couple of seconds, but nothing. it vibrates three times and then the sony logo comes up again. (is it called bootloop?)
The status now is that the phone, if plugged in to a power source like PC, or wall it will show the SONY logo even if you shut it down with power off and volume up. in other words the phone restarts itself. The only way to shut it down is to do it without a power source.
The fallowing tools+files has been used:
adb-setup-1.3.exe
flashtool-0.9.19.8-windows.exe
rootkitXperia_20140719.zip
Z2-lockeddualrecovery2.7.154-BETA.installer.zip
D6503_17.1.2.A.0.314_UK Generic.ftf
flashable_D6503_23.4.A.0.546.zip
So the thing is that i really want to upgrade myself with a new phone. In the same time i got like under one bitcoin that i had for a while and because of my stupidness i feel like i can donate to that to the first person who engages him/herself to that level so i can use my phone again.
Sorry for the long post! Thanks in advance!
Click to expand...
Click to collapse
Dude.. I suggest keep this phone as a showpiece.. And buy a new phone.. Z5 or Z3 with the latter being cheap... Or shell some bucks and give it to Sony service..
But i do hope your phone gets alright again..
[emoji5] [emoji5]
Sent from my D6502 using Tapatalk
EthanDev said:
Dude.. I suggest keep this phone as a showpiece.. And buy a new phone.. Z5 or Z3 with the latter being cheap... Or shell some bucks and give it to Sony service..
But i do hope your phone gets alright again..
[emoji5] [emoji5]
Sent from my D6502 using Tapatalk
Click to expand...
Click to collapse
well that was not much for help..
axeljooo said:
well that was not much for help..
Click to expand...
Click to collapse
Agree man.. But thats all you can expect from a noob [emoji13]
Sent from my D6502 using Tapatalk
Try with flashtool 0.9.18.6. On 0.9.19.x I had some problems with booting (one time stucks at sony logo, one time bootloop, one time freezes all the time, on tme flathtool crashed...)
Download Flashtool 0.9.18.6 and download and flash 23.4.A.0.546 ROM from here: https://mega.nz/#!n1YlBAhI!HX8WPPyjLDJGnUZ-9_Xom96OFZcDUfasgzjuagrj2UE (this is compiled by me FTF File, I'm using it when sth goes wrong) and then, when it boots (must boot because it's not hardbrick), charge it to 100%, download 23.1.A.1.28 5.0.2 ROM from here https://docs.google.com/uc?id=0By-vo9NJkgzJVUo0dVNreFNvSjg&export=download
And flash this ROM and reboot and DO NOT UPDATE. Install KingRoot (the newest is the best) and root it, then install XZ Dual Recovery and that's all.
Hope I helped, if not, write me in comment what went wrong, and, if any errors in flashtool are shown, copy and paste to comment and let mi see them.
Bruce666 said:
Try with flashtool 0.9.18.6. On 0.9.19.x I had some problems with booting (one time stucks at sony logo, one time bootloop, one time freezes all the time, on tme flathtool crashed...)
Download Flashtool 0.9.18.6 and download and flash 23.4.A.0.546 ROM from here: https://mega.nz/#!n1YlBAhI!HX8WPPyjLDJGnUZ-9_Xom96OFZcDUfasgzjuagrj2UE (this is compiled by me FTF File, I'm using it when sth goes wrong) and then, when it boots (must boot because it's not hardbrick), charge it to 100%, download 23.1.A.1.28 5.0.2 ROM from here https://docs.google.com/uc?id=0By-vo9NJkgzJVUo0dVNreFNvSjg&export=download
And flash this ROM and reboot and DO NOT UPDATE. Install KingRoot (the newest is the best) and root it, then install XZ Dual Recovery and that's all.
Hope I helped, if not, write me in comment what went wrong, and, if any errors in flashtool are shown, copy and paste to comment and let mi see them.
Click to expand...
Click to collapse
Thank you for the reply! i can not see how much my phone is charged and when i charge it the SONY logo shows up, so i do not know how much that drains the battery. But i will wait an hour or so then. Will try method after that! Though my phone was gone, but what i have now read myself to is that Hard brick is first when the phone is totally dead.
Before you answered i was going to do this guide:
http://forum.xda-developers.com/showpost.php?p=53220435&postcount=4
But i will go with your instead first. Should i uninstall my current flashtool and download Flashtool-0.9.18.6-windows.exe instead for now then while i wait for my phone to charge?
found this the file here https://drive.google.com/file/d/0B4sYgaP5RMK0S1pzUnMzdWd3UnM/view
Edit: did not read your post properly, will start with your custom ROM soon!
axeljooo said:
Thank you for the reply! i can not see how much my phone is charged and when i charge it the SONY logo shows up, so i do not know how much that drains the battery. But i will wait an hour or so then. Will try method after that! Though my phone was gone, but what i have now read myself to is that Hard brick is first when the phone is totally dead.
Before you answered i was going to do this guide:
http://forum.xda-developers.com/showpost.php?p=53220435&postcount=4
But i will go with your instead first. Should i uninstall my current flashtool and download Flashtool-0.9.18.6-windows.exe instead for now then while i wait for my phone to charge?
found this the file here https://drive.google.com/file/d/0B4sYgaP5RMK0S1pzUnMzdWd3UnM/view
Edit: did not read your post properly, will start with your custom ROM soon!
Click to expand...
Click to collapse
Yes, uninstall your flashtool and install 0.9.18.6
Bruce666 said:
Yes, uninstall your flashtool and install 0.9.18.6
Click to expand...
Click to collapse
of course, stupid of me
A question: was the rom 23.4.A.0.546 ROM really right for Z2? because Flashtool says hold "Back button" and plug in the phone. Z2 does not have a back button, but maybe you could house volume down?
Bruce666 said:
Yes, uninstall your flashtool and install 0.9.18.6
Click to expand...
Click to collapse
Done the first part with your custom ROM. Seems like you are getting the 0.15 BTC! will take it to next steep in an hour!
Thx!
Sorry I forgot. It requires flashmode You can reach it by pushing vol-
Bruce666 said:
Sorry I forgot. It requires flashmode You can reach it by pushing vol-
Click to expand...
Click to collapse
Did install your custom ROM without any problem!
i have charged my phone for 4h, but still only 54% charged.. so will get back here tomorrow!
axeljooo said:
Did install your custom ROM without any problem!
i have charged my phone for 4h, but still only 54% charged.. so will get back here tomorrow!
Click to expand...
Click to collapse
You can only use custom roms with an unlocked boot loader. Locked boot loader requires a sony kernel.
**edit**
Read the instructions he gave you, it's a modified stock rom so that should be fine. I've bricked mine and the flashtool has resolved it so hopefully it will for you
Um... Considering the fact that your phone boots up, I strongly recommend you to try a fresh install with pc companion.... I had somewhat a similar issue and it was the last resort for me and it worked...
Bruce666 said:
Try with flashtool 0.9.18.6. On 0.9.19.x I had some problems with booting (one time stucks at sony logo, one time bootloop, one time freezes all the time, on tme flathtool crashed...)
Download Flashtool 0.9.18.6 and download and flash 23.4.A.0.546 ROM from here: https://mega.nz/#!n1YlBAhI!HX8WPPyjLDJGnUZ-9_Xom96OFZcDUfasgzjuagrj2UE (this is compiled by me FTF File, I'm using it when sth goes wrong) and then, when it boots (must boot because it's not hardbrick), charge it to 100%, download 23.1.A.1.28 5.0.2 ROM from here https://docs.google.com/uc?id=0By-vo9NJkgzJVUo0dVNreFNvSjg&export=download
And flash this ROM and reboot and DO NOT UPDATE. Install KingRoot (the newest is the best) and root it, then install XZ Dual Recovery and that's all.
Hope I helped, if not, write me in comment what went wrong, and, if any errors in flashtool are shown, copy and paste to comment and let mi see them.
Click to expand...
Click to collapse
I am currently downloading https://docs.google.com/uc?id=0By-vo9NJkgzJVUo0dVNreFNvSjg&export=download and will flash soon. I just have some questions, because i fallowed this guide:
"http://forum.xda-developers.com/xperia-z2/development/stock-d6502-23-1-0-726-complete-guide-t3085893" and did install both rootkitXperia_20140719 and lockeddualrecovery. did those programs get wiped when i installed your custom ROM? Sorry for all the questions but i am trying to get a grip how the phones software works, and so i dont mess anything more up when installing kingsroot etc.
Btw. Kingsroot should i download that from google play or is it through PC? If i should download their APK.
Kingroot download apk from here http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Then install xzdual recovery from nut via PC but turn off anti-virus because it shows virus (it's exploit) and then push prerooted zip to sdcard and install via twrp but remember to make factory reset (wipe data and cache - wiping cache can take up to 10 minutes). If you root via kingroot you won't lose data, but when installing prerooted Rom you'll lose your data (but internal memory won't be wiped)
Bruce666 said:
Kingroot download apk from here http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Then install xzdual recovery from nut via PC but turn off anti-virus because it shows virus (it's exploit) and then push prerooted zip to sdcard and install via twrp but remember to make factory reset (wipe data and cache - wiping cache can take up to 10 minutes). If you root via kingroot you won't lose data, but when installing prerooted Rom you'll lose your data (but internal memory won't be wiped)
Click to expand...
Click to collapse
Ok thanks. so i should download the kingsroot apk and install it from my phone? correct?
Yes, but install it on 5.0.2 rom
Bruce666 said:
Yes, but install it on 5.0.2 rom
Click to expand...
Click to collapse
of course! is this the right place?
http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.25
btw. what does the dual recovery do? never really understood it. and whats a bootloader? Sorry for the questions
Yes, but download for Z2 filename: Z2-lockeddualrecovery2.8.25-RELEASE.combined.zip when you install it, phone will reboot to TWRP Recovery, so before you install it, place prerooted rom zip to sdcard
Bruce666 said:
Yes, but download for Z2 filename: Z2-lockeddualrecovery2.8.25-RELEASE.combined.zip when you install it, phone will reboot to TWRP Recovery, so before you install it, place prerooted rom zip to sdcard
Click to expand...
Click to collapse
Ok! so prerooted rom, is that like the flashable rom? or can i for example choose to install like Cyanagenmod?
This is not anything new for experienced users, but it will help the newbies.
NOTE: This is, still, the standard process to flash stock ROMs on ANY Samsung running Android, you can use the same drivers, software and key combo for Download mode on other variant or model, what you need to change is the firmware file of course. So feel free to use this guide as reference.
The Stock ROM or Stock Firmware is the software that comes preinstalled in your phone when is brand new, in this case is Samsung's own modification of Android called TouchWiz. If you ran into problems like system apps FCs all the time, bootloops, softbricks,etc... Or if you adventure on the "custom world" (Root, Xposed, aftermarket roms, etc) and things go south, it happens... The stock rom can be flashed to fix those problems and/or get your phone back to a working state again, hence the importance of this procedure.
The tool to flash firmwares on Samsung phones running Android is called Odin, and in order for Odin to recognize your phone in Download Mode (more on that later) it also needs some drivers. You can download both things from the following links:
Odin 3.10 from MEGA*
<Mod Edit> 4shared link removed
PLEASE READ [*]
1. Both files are in .RAR5, so you need to use WinRAR 5 or above to be able open them.
2. They also are password protected (sorry about that, but i offer them on several sites already). Password is: Tecnoriales
Now you need the firmware for your SPECIFIC MODEL, country and carrier are not important, but model IS, deadly. So, don't even try to flash another variant stock rom in you phone, you can and will end up with a hard brick, and good luck fixing that.
Sammobile is the biggest repository for Samsung firmwares, so use that.
J320F and DS - J320F and J320F/DS (Dual SIM) are the same.
J320FN
J320H
J320M
J320FXXU0AQL1 Mirror on MEGA (Netherlands) - I downloaded it from Sammobile and re-uploaded to MEGA. Same .RAR5 stuff and Tecnoriales password.
For any other variant or any Samsung phone for that matter, use the search tool with your model: https://www.sammobile.com/firmwares/
How to flash the Stock ROM using Odin​Before you star please charge your battery to 100%.
1. Install the Samsung Drivers
2. Turn off your phone and enter Download Mode pressing Vol+- Home and Power. Youll see a warning in the screen, accept it pressing Vol+.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Plug your phone to the PC using your usb cable and give it some time for the driver to kick in if it is the very first time.
4. Run Odin as Admin. Check the COM Port is illuminated and you see Added in the log below.
5. Click the AP button and load the *.tar file you downloaded from sammobile. i. e.: J320FXXU0AQL1_J320FDBT0AQK1_J320FXXU0AQI1_HOME.tar.md5 - At this point Odin will hang (stop responding) for some time while it loads the firmware file, that will depend on your PC, from some seconds to a couple of minutes. Be patient.
6. Once Odin un-freezes, go to Options Tab and make sure Re-Partition is unchecked.
7. Press Start to initiate the flashing process, it will take a while. The phone will reboot and when you see a green Pass in Odin it will be safe to unplug your phone..
First boot might take some time depending on the condition of your phone. That's it, your phone should be working again as intended (by Samsung).
Extra: Recovery Mode key combo with phone turned off is Vol+, Home and Power, from here you can perform a Factory Reset.
All the above information is in this video i made. Video is in Spanish tough.
Sorry for my english, good luck and happy flashing.
Does this apply to the SM-J327P? It would greatly help newer users
Sent from my Samsung SM-J327P using XDA Labs
Sands207 said:
Does this apply to the SM-J327P? It would greatly help newer users
Sent from my Samsung SM-J327P using XDA Labs
Click to expand...
Click to collapse
For any Samsung running Android, since idk, the original Galaxy S? The process has not changed. Of course youll need to download the SPECIFIC Rom for your J327P.
mauriciognr said:
For any Samsung running Android, since idk, the original Galaxy S? The process has not changed. Of course youll need to download the SPECIFIC Rom for your J327P.
Click to expand...
Click to collapse
Thank you i appreciate it ?
Does this also restore stock recovery too?
I'm trying to avoid flashing twrp so that I can backup stock recovery but I can't get fastboot to work so my only option would be to flash the custom recovery onto the phone.
I don't want to be stuck without a way to restore stock recovery in case something goes wrong.
CyberZot said:
Does this also restore stock recovery too?
I'm trying to avoid flashing twrp so that I can backup stock recovery but I can't get fastboot to work so my only option would be to flash the custom recovery onto the phone.
I don't want to be stuck without a way to restore stock recovery in case something goes wrong.
Click to expand...
Click to collapse
Yes it restores stock recovery ,when flashing with Odin it will always flash stock recovery
Scorpionea said:
Yes it restores stock recovery ,when flashing with Odin it will always flash stock recovery
Click to expand...
Click to collapse
Thank you very much!
Thank you. Your post hepled me.
Hello,
i want to upgrade my phone, samsung J3 (2016) SM-J320F (dual sim).
I fallow your tutoo, i only find version 5.1.1 on Sammobile
Can we find version 6 or 7 anywhere ?
Thank you for your help.
Bests regards.
Christophe
tof225391 said:
Hello,
i want to upgrade my phone, samsung J3 (2016) SM-J320F (dual sim).
I fallow your tutoo, i only find version 5.1.1 on Sammobile
Can we find version 6 or 7 anywhere ?
Thank you for your help.
Bests regards.
Christophe
Click to expand...
Click to collapse
This is the wrong turtorial for you it is to get your phone back to your original software and thats 5.1.1
J320 to Android 7.1
tof225391 said:
Hello,
i want to upgrade my phone, samsung J3 (2016) SM-J320F (dual sim).
I fallow your tutoo, i only find version 5.1.1 on Sammobile
Can we find version 6 or 7 anywhere ?
Click to expand...
Click to collapse
Even though it was mentioned this is the wrong page I don't see why you can't be given some helpful info. The firmware you're looking for to get Android 7.1 is, J320W8VLU2BQK1 J320W8OYA2BQK1 (Its listed for Canada) search for it online.
**Note
If you cant get through the welcome screen. Reset data on recovery
I can't get Odin to work on my SM-J320A (ATT version)
its running this firmware i think: J320AUCS3BQL2
and nougat 7.1.1
holding volume down + home + power. Odin mode starts and asks for confirmation. (volume up to continue, volume down to restart) But nothing happens. LOL All i can do is pull the battery and if i try recovery mode it says "No command", hangs for awhile then goes into recovery mode.
Is USB debugging on, required?
Odin mode works fine on my other Galaxy phones. Anyone have this issue before? thanks
CLovecraft said:
I can't get Odin to work on my SM-J320A (ATT version)
its running this firmware i think: J320AUCS3BQL2
and nougat 7.1.1
holding volume down + home + power. Odin mode starts and asks for confirmation. (volume up to continue, volume down to restart) But nothing happens. LOL All i can do is pull the battery and if i try recovery mode it says "No command", hangs for awhile then goes into recovery mode.
Is USB debugging on, required?
Odin mode works fine on my other Galaxy phones. Anyone have this issue before? thanks
Click to expand...
Click to collapse
Try to turn on usb debbuging and oem unlock
2gg1 said:
Try to turn on usb debbuging and oem unlock
Click to expand...
Click to collapse
Thanks.
Update: my soft brick issue is fixed now. (it was stuck on a boot loop for awhle but seems to have fixed itself after 20 reboots)
So i can boot into operating system.
Next i turned on OEM unlock and USB debugging but Odin mode still doesn't work, though.
Now, another minor problem. The home button doesn't work, but seems physically okay (this phone has barely been used and looks pristine) Could be a firmware issue related to Dalvik Cache. but without being able to flash firmware i cannot confirm. Recovery mode still shows a "No command" screen, dead robot, and 50 seconds later goes into what looks like stock recovery.
Update 2. Tried factory reset which seems to have helped. it boots faster into the operating system now. :good:
so i did this now i wanted to install touchwiz rome on 6,0,1 android but it bootloops i hear i need some baseband but what baseband i need someone can help pls
Looking for J320A
CLovecraft said:
Thanks.
Update: my soft brick issue is fixed now. (it was stuck on a boot loop for awhle but seems to have fixed itself after 20 reboots)
So i can boot into operating system.
Next i turned on OEM unlock and USB debugging but Odin mode still doesn't work, though.
Now, another minor problem. The home button doesn't work, but seems physically okay (this phone has barely been used and looks pristine) Could be a firmware issue related to Dalvik Cache. but without being able to flash firmware i cannot confirm. Recovery mode still shows a "No command" screen, dead robot, and 50 seconds later goes into what looks like stock recovery.
Update 2. Tried factory reset which seems to have helped. it boots faster into the operating system now. :good:
Click to expand...
Click to collapse
What did you end up doing to pull this off? I've got the exact same model phone, but cannot seem to find the firmware on Sammobile.