Hey everybody!
I need a little help: I wanted to install the Unlimited ROM on my BL locked Xperia Mini Pro... I download the file, put it on my SD card, insert the SD card and boot my phone into recovery.
I format System, Data, and Cache, and go to flash the zip. When I tried, it said there was no SD card inserted!
Because I am a complete idiot, I try to reboot and it obviously won't go into recovery...
I already tried to flash the stock ROM with Flashtools, but it failed.
Does anyone have a solution to my problem?
Thanks in advance,
MustangEmile
Flashtool should work well, tell us which error you get
Or you try the repair options of PC Companion or Sony Update Service
Sent from my Nexus 4 running Android 4.4
mihahn said:
Flashtool should work well, tell us which error you get
Or you try the repair options of PC Companion or Sony Update Service
Sent from my Nexus 4 running Android 4.4
Click to expand...
Click to collapse
Sorry for the late answer, been in school all day...
Here is the log of the flash:
03/007/2014 17:07:40 - INFO - <- This level is successfully initialized
03/007/2014 17:07:40 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
03/007/2014 17:07:40 - INFO - You can drag and drop ftf files here to start flashing them
03/007/2014 17:07:45 - INFO - Device disconnected
03/007/2014 17:07:51 - INFO - Selected SK17i_4.1.B.0.587_Official French.ftf
03/007/2014 17:07:51 - INFO - Preparing files for flashing
03/007/2014 17:07:59 - INFO - Please connect your device into flashmode.
03/008/2014 17:08:05 - INFO - Device connected in flash mode
03/008/2014 17:08:05 - INFO - Opening device for R/W
03/008/2014 17:08:05 - INFO - Start Flashing
03/008/2014 17:08:05 - INFO - Processing loader
03/008/2014 17:08:05 - INFO - Checking header
03/008/2014 17:08:05 - INFO - Ending flash session
03/008/2014 17:08:05 - ERROR -
03/008/2014 17:08:05 - ERROR - Error flashing. Aborted
03/008/2014 17:08:06 - INFO - Device connected in flash mode
Click to expand...
Click to collapse
I will try PC Companion, but I doubt it'll work...
Thanks for answering,
MustangEmile
EDIT: PC Companion doesn't recognize the phone...
Whenever I soft-brick my xmp, flashing a new kernel and starting over does the trick, but considering flashtool is not working for you... that's a bit more complicated than I thought.
First off, have you checked your FTF's integrity? exact file size? checksum? have you successfully used it in the past?
Also, can you boot to fastboot mode? if so, unlock your bootloader via sony's dev site and flash a custom kernel, as most of them have CWM built in. It's possible to start over from there.
Maybe it shut down when the flashing is about to start
Sent from my Xperia P
Pixelado said:
Whenever I soft-brick my xmp, flashing a new kernel and starting over does the trick, but considering flashtool is not working for you... that's a bit more complicated than I thought.
First off, have you checked your FTF's integrity? exact file size? checksum? have you successfully used it in the past?
Also, can you boot to fastboot mode? if so, unlock your bootloader via sony's dev site and flash a custom kernel, as most of them have CWM built in. It's possible to start over from there.
Click to expand...
Click to collapse
I've already used this ftf multiple times in the past... I can't unlock my BL: My Xperia Mini Pro was bought through Orange and they disable the possibility to unlock it...
KiyazumiJr said:
Maybe it shut down when the flashing is about to start
Sent from my Xperia P
Click to expand...
Click to collapse
I highly doubt it: it's still on at the end, but thanks for your hypothesis
How sad, hope you can get it back up and running.
MustangEmile said:
I've already used this ftf multiple times in the past... I can't unlock my BL: My Xperia Mini Pro was bought through Orange and they disable the possibility to unlock it...
I highly doubt it: it's still on at the end, but thanks for your hypothesis
Click to expand...
Click to collapse
Try reinstalling the drivers and either connect the phone before selecting the ftf that you want to flash or select ir first and when the popup to connect the phone appears, connect it
Sent from my Nexus 4 running Android 4.4
Related
i tried flashing my X10 mini pro using Flashtool, but got this error:
Code:
02/006/2011 03:06:30 - INFO - Searching Xperia....
02/006/2011 03:06:30 - INFO - Found at USB\VID_0FCE&PID_ADDE\5&11AE52C9&0&4
02/006/2011 03:06:30 - INFO - Start Flashing
02/006/2011 03:06:31 - INFO - VER="R8A029";DATE="20100601";TIME="12:17:00";
02/006/2011 03:06:31 - INFO - Flashing loader
02/006/2011 03:06:31 - ERROR - Error flashing. Aborted
02/006/2011 03:06:31 - INFO - Now unplug the device and power it on
02/006/2011 03:06:31 - INFO - Then go to application settings
02/006/2011 03:06:31 - INFO - turn on Unknown Sources and Debugging
And my phone gets stuck on the white Sony Ericsson screen, so cant change the app settings, nor can i access CWM..
Please help me.. thank you!
did you take off your battery and reboot? which version off flash tool do you have? there are different versions out there http://androxyde.github.com/Flashtool/ is your version similar? i guess you are on stock? i hope this helps. Post more Information if nothing works repair your phone with companion
yes i took off the battery and rebooted.. and the flashtool version is the same as the one you have linked in the above post...
and yes i'm running on stock... phone is rooted..
Are you trying to flash the bootloader without unlocking it or trying to flash an official Sony Ericsson ROM? If you trying to flash the bootloader the 'R8A029' should be 'r8A029' with a lower case 'r', you'll need to use a bootunlocker to do that. (be sure to read the instructions or else you can hard brick your phone!)
Sent from my U20i using Tapatalk
domics said:
if nothing works repair your phone with companion
Click to expand...
Click to collapse
obsidian_eclipse said:
Are you trying to flash the bootloader without unlocking it or trying to flash an official Sony Ericsson ROM? If you trying to flash the bootloader the 'R8A029' should be 'r8A029' with a lower case 'r', you'll need to use a bootunlocker to do that. (be sure to read the instructions or else you can hard brick your phone!)
Sent from my U20i using Tapatalk
Click to expand...
Click to collapse
Thank you both for your replies and giving me more knowledge on flashing androids
But PC companion did the trick for me
Mimmi is back to normal special thanks to domics for suggesting me to use pc companion..
thank you!
Hi,
I have this behavior in my u20i phone that the phone will not boot. When i connect it to my PC, the PC detects the phone momentarily for around 5 seconds and then it disconnects and this will continue until i disconnect it. Does this mean my phone is bricked? Is this what a bootloop is? I read many threads on this forum, and for whoever was facing the problem of bootloop, he was atleast getting SE logo.
Now coming to my problem, i used s1tool to get the present details of my phone and it shows the following:
RUNNING S1_EROM VER "R8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/00BC"
LOADER VERSION: "R4A045"
MODEL (from GDFS): U20i
SOFTWARE VERSION: 1235-3411_2.1.1.A.0.6
CUSTOM VERSION: 1238-7170_R4B
.
.
SEMC SIMLOCK CERTIFICATE
The loader version tells me that the bootloader is not unlocked. Tried using SEUS update service to fix my phone back, but after completion, i still am stuck with this boot-looping. Any other suggestions? Any more information required to debug my problem? I had installed a custom rom which was working well (MiniCM7Pro_V21) until i restarted my phone which is when i got this problem. (had got a problem like this before but using SEUS had worked that time)
I can enter the flashmode of the phone atleast but thats it (this gives me some glimmer of hope )
My last resort will be to give my phone to the SE service guys but i wanna know what the problem is before i give it to them.
try again using SEUS????
Yashu1019 said:
try again using SEUS????
Click to expand...
Click to collapse
Already tried both SEUS and also using PCCompanion repair option, none of them are working for me...
Looks like a dying post faiyyaz helping out, but has come to a point where hez stuck, but anyway thanks a lot faiyyaz...Man, i just dont wanna give up and give it so SE guys, want to fix it my way...Anyway, any more suggestions will be helpful...
Attaching the messages exchanged:
faiyyaz said:
R[O]K.O. said:
faiyyaz said:
R[O]K.O. said:
Hi, Its regarding a question i posted on xda developers, http://forum.xda-developers.com/showthread.php?t=1518652
Any help would be very much appreciated...
Click to expand...
Click to collapse
bro.. u aren't getting the Sony Ericsson logo when turn on?? n just to clear your confusion your bootloader is locked o no worries of that.. n 2ndly did u try the latest SEUS..? if not give it a try.. if not working PM again .
Click to expand...
Click to collapse
Used SEUS 2.12.3.5, got a successful message at the end, disconnected the phone and started the phone back again, but problem still exists...Any other ideas i can try out?
Click to expand...
Click to collapse
well that's weird.. i think the only way u can get it working is as you can get into flashmode, you can unlock bootloader then flash the nAa kernel as its got inbuilt CWM recovery,so u can get into recovery mode.. then u can flash a custom ROM.. a perfect ROM would be MiniCm7 by nAa itself n then if u want to get back to stock.. u may flash stock kernel.. then relock bootloader n then use SEUS to get back to Stock ROM.. its a long proceduce but i think it shall work.. if any query fell free to ask.hope that helps you
note: Make sure your following proper instructions while unlocking bootloader , use my tool if u want SE Tweaker Tool n follow correct instruction n read its main thread before u use it..
Click to expand...
Click to collapse
faiyyaz said:
R[O]K.O. said:
Oh and 1 more thing, how can i enable USB debugging when i cannot switch on the phone, by any external means possible?
Click to expand...
Click to collapse
Well sorry mate.. But I thought ur usb debugging might be on.. so I guess the unlock bootloader thing wont work for u.. Maybe u should try givin it to the service center if its under gaurante.. Else il see if there is any other way u can through..
Sent from my U20i using xda premium
Click to expand...
Click to collapse
Hmm. Tricky. Have you tried using Flashtool to put a stock firmware back on?
Sent from my U20i using XDA App
Ticklefish said:
Hmm. Tricky. Have you tried using Flashtool to put a stock firmware back on?
Sent from my U20i using XDA App
Click to expand...
Click to collapse
Just tried it a few mins back, heres what i had on the flashtool disp:
03/030/2012 02:30:56 - INFO - Selected U20i_2.1.1.A.0.6_Baseband_015.ftf
03/030/2012 02:30:56 - INFO - Preparing files for flashing
03/030/2012 02:30:56 - INFO - Please connect your device into flashmode.
03/031/2012 02:31:03 - INFO - Device connected in flash mode
03/031/2012 02:31:03 - INFO - Opening device for R/W
03/031/2012 02:31:03 - INFO - Reading device information
03/031/2012 02:31:03 - INFO - Phone reading for flashing.
03/031/2012 02:31:03 - INFO - Start Flashing
03/031/2012 02:31:03 - INFO - Flashing loader
03/031/2012 02:31:05 - INFO - Loader version : R4A045 / Bootloader status : UNROOTABLE
03/031/2012 02:31:05 - INFO - Flashing amss_fs.sin
03/031/2012 02:31:05 - INFO - Flashing cache.sin
03/031/2012 02:31:06 - INFO - Flashing fota1.sin
03/031/2012 02:31:06 - INFO - Flashing kernel.sin
03/031/2012 02:31:10 - INFO - Flashing amss.sin
03/031/2012 02:31:21 - INFO - Flashing fota0.sin
03/031/2012 02:31:22 - INFO - Flashing finished.
03/031/2012 02:31:22 - INFO - Please wait. Phone will reboot
03/031/2012 02:31:22 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
03/031/2012 02:31:22 - INFO - Device connected in flash mode
03/031/2012 02:31:23 - INFO - Device disconnected
03/031/2012 02:31:25 - INFO - Device connected in flash mode
03/031/2012 02:31:49 - INFO - Device disconnected
03/031/2012 02:31:55 - INFO - Device connected with USB debugging off
Click to expand...
Click to collapse
Tried starting the phone but am having the same problem still...
Have given the phone today to the SE guys, will let you guys knw if it gets fixed or not (they tried updating, said they used some factory sent updater which didn't work after which they said its a hardware issue, which somehow i doubt)...
Got my phone back today and its in good working condition. They said they replaced the flexicable of my minipro which was faulty. Anyway am happy that its working now and am ready to flash a rom into it again Thanks for all your help and suggestions...
i have a friend using samsung galaxy s2, and he said he is using some special modified usb that will make the bootloader enter download mode so that he flashed original firmware into his phone after it is bricked...
for x10 mini pro is there such cable? i need it because i think my phone is hardbricked...
it is bootloader unlocked and i flashed the original stock rom into the phone(in attempt to save condition where flashing customised kernel wasnt successful and it keep bootlooping...), and now i cant root it, cant On the phone to enter usb debugging mode, i cant do anything about it, i read so many threads but really didnt help me... , i can say that i tried all of them already...the phone just keep bootlooping the sony erricson logo on and off... using SEUS also didnt help because it shows i have latest version... and now i cant even flash other kernels because flashtool will show some error anyone facing this problem before? before i throw my phone my last hope will be the special usb that i want to find
jasonmiracle said:
i have a friend using samsung galaxy s2, and he said he is using some special modified usb that will make the bootloader enter download mode so that he flashed original firmware into his phone after it is bricked...
for x10 mini pro is there such cable? i need it because i think my phone is hardbricked...
it is bootloader unlocked and i flashed the original stock rom into the phone(in attempt to save condition where flashing customised kernel wasnt successful and it keep bootlooping...), and now i cant root it, cant On the phone to enter usb debugging mode, i cant do anything about it, i read so many threads but really didnt help me... , i can say that i tried all of them already...the phone just keep bootlooping the sony erricson logo on and off... using SEUS also didnt help because it shows i have latest version... and now i cant even flash other kernels because flashtool will show some error anyone facing this problem before? before i throw my phone my last hope will be the special usb that i want to find
Click to expand...
Click to collapse
Samsung phones can only be flashed using special cables, that is true, but SE provided a flashmode that always works, by turning off your phone and pressing the back-button before you plug in your usb-cable... In regards to that they're miles ahead of Samsung. Do you know how to get to Repair mode in SEUS or PC Companion?
SmG67 said:
Samsung phones can only be flashed using special cables, that is true, but SE provided a flashmode that always works, by turning off your phone and pressing the back-button before you plug in your usb-cable... In regards to that they're miles ahead of Samsung. Do you know how to get to Repair mode in SEUS or PC Companion?
Click to expand...
Click to collapse
the repair mode is something like flashing it using flashtool right? wait for the screen asking to connect with flashmode, off phone, press back button then plug in usb, but then SEUS shows i am having newest software? there is guide to make SEUS identify i am not having newest software version, but that is by turning on the phone, and getting file manager to edit something .prop files?
but sadly i really cant do that because i cant even turn on my phone now... what should i do? any other way to change the files inside my phone to make the SEUS detect i am not newest software so that it can download and flash the original rom inside my phone?
jasonmiracle said:
the repair mode is something like flashing it using flashtool right? wait for the screen asking to connect with flashmode, off phone, press back button then plug in usb, but then SEUS shows i am having newest software? there is guide to make SEUS identify i am not having newest software version, but that is by turning on the phone, and getting file manager to edit something .prop files?
but sadly i really cant do that because i cant even turn on my phone now... what should i do? any other way to change the files inside my phone to make the SEUS detect i am not newest software so that it can download and flash the original rom inside my phone?
Click to expand...
Click to collapse
Try to flash THIS with flashtool, it's complete latest (2.1.1.A.0.6) firmware (Kernel and ROM) from SE.
(It comes in at about 213.5MB, although the site may report it's smaller. It will keep downloading until it's done though)
SmG67 said:
Try to flash ubuntuone.com/16ffDIwsKeeof1ILUZrL55 with flashtool, it's complete latest (2.1.1.A.0.6) firmware (Kernel and ROM) from SE.
(It comes in at about 213.5MB, although the site may report it's smaller. It will keep downloading until it's done though)
Click to expand...
Click to collapse
alright let me try this... nice ubuntuone...fast download speed
SmG67 said:
Try to flash [with flashtool, it's complete latest (2.1.1.A.0.6) firmware (Kernel and ROM) from SE.
(It comes in at about 213.5MB, although the site may report it's smaller. It will keep downloading until it's done though)
Click to expand...
Click to collapse
01/000/2012 23:00:05 - INFO - Selected U20_2.1.1.A.0.6_Unbranded_unlockedBL.ftf
01/000/2012 23:00:05 - INFO - Preparing files for flashing
01/001/2012 23:01:07 - INFO - Please connect your device into flashmode.
01/001/2012 23:01:19 - INFO - Device connected in flash mode
01/001/2012 23:01:20 - INFO - Opening device for R/W
01/001/2012 23:01:20 - INFO - Reading device information
01/001/2012 23:01:20 - INFO - Phone ready for flashmode operations.
01/001/2012 23:01:21 - INFO - Start Flashing
01/001/2012 23:01:21 - INFO - Processing loader
01/001/2012 23:01:21 - INFO - Checking header
01/001/2012 23:01:21 - INFO - Ending flash session
01/001/2012 23:01:21 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
Click to expand...
Click to collapse
not working...do i have to flash all the .sin files? this error caused by me choosing all the .sin files... last hope..
jasonmiracle said:
not working...do i have to flash all the .sin files? this error caused by me choosing all the .sin files... last hope..
Click to expand...
Click to collapse
You said your bootloader was unlocked.. That doesn't seem to be the case...
Try This one, for locked bootloader instead.
SmG67 said:
You said your bootloader was unlocked.. That doesn't seem to be the case...
Try This one, for locked bootloader instead.
Click to expand...
Click to collapse
yup, problem i cant flash roms other than stock roms because of locked bootloader...now i can only flash stock kernel, but cant update via SEUS/PCC because it cant detect newest version, probably because of 2.1update 1 version...do you have version 2.1 stock kernel? just wanna try other alternatives... by flashing stock older rom, hopefully SEUS will update it to 2.1update1 version...so far method that you provided now, and method that i think now is the last 2 method...
jasonmiracle said:
yup, problem i cant flash roms other than stock roms because of locked bootloader...now i can only flash stock kernel, but cant update via SEUS/PCC because it cant detect newest version, probably because of 2.1update 1 version...do you have version 2.1 stock kernel? just wanna try other alternatives... by flashing stock older rom, hopefully SEUS will update it to 2.1update1 version...so far method that you provided now, and method that i think now is the last 2 method...
Click to expand...
Click to collapse
Did you try to flash my latest suggestion and just boot up your phone?
SmG67 said:
Did you try to flash my latest suggestion and just boot up your phone?
Click to expand...
Click to collapse
man, your BL unlocked rom works like charm!!! so far flashing fine!!! 62% now... praying that no error pops out...
SmG67 said:
Did you try to flash my latest suggestion and just boot up your phone?
Click to expand...
Click to collapse
bro, THANKS for your BL locked stock firmware!!! it worked!!! my phone booted, now i am choosing languages!! where did you get that .ftf thing? really a lifesaver...
but one more question, now that i can turn on my phone, that i want to flash other roms, i have to root my phone and unlock BL flash with custom kernel, and flash other roms right? this is my first flashing thats why took so long time digging, finally i got solution from you today when i gave up hope and asked question on xda :good:
02/011/2012 00:11:31 - INFO - Selected U20_2.1.1.A.0.6_Unbranded_lockedBL.ftf
02/011/2012 00:11:31 - INFO - Preparing files for flashing
02/011/2012 00:11:34 - INFO - Please connect your device into flashmode.
02/012/2012 00:12:09 - INFO - Flash canceled
02/012/2012 00:12:19 - INFO - Selected U20_2.1.1.A.0.6_Unbranded_lockedBL.ftf
02/012/2012 00:12:19 - INFO - Preparing files for flashing
02/012/2012 00:12:21 - INFO - Please connect your device into flashmode.
02/012/2012 00:12:28 - INFO - Device connected in flash mode
02/012/2012 00:12:29 - INFO - Opening device for R/W
02/012/2012 00:12:29 - INFO - Device connected in flash mode
02/012/2012 00:12:29 - INFO - Reading device information
02/012/2012 00:12:29 - INFO - Phone ready for flashmode operations.
02/012/2012 00:12:29 - INFO - Start Flashing
02/012/2012 00:12:29 - INFO - Processing loader
02/012/2012 00:12:29 - INFO - Checking header
02/012/2012 00:12:29 - INFO - Flashing data
02/012/2012 00:12:31 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Bootloader status : UNROOTABLE
02/012/2012 00:12:32 - INFO - Processing kernel.sin
02/012/2012 00:12:32 - INFO - Checking header
02/012/2012 00:12:32 - INFO - Flashing data
02/012/2012 00:12:35 - INFO - Processing fota1.sin
02/012/2012 00:12:35 - INFO - Checking header
02/012/2012 00:12:35 - INFO - Flashing data
02/012/2012 00:12:35 - INFO - Processing fota0.sin
02/012/2012 00:12:35 - INFO - Checking header
02/012/2012 00:12:35 - INFO - Flashing data
02/012/2012 00:12:36 - INFO - Processing amss_fs.sin
02/012/2012 00:12:36 - INFO - Checking header
02/012/2012 00:12:36 - INFO - Flashing data
02/012/2012 00:12:36 - INFO - Processing amss.sin
02/012/2012 00:12:36 - INFO - Checking header
02/012/2012 00:12:36 - INFO - Flashing data
02/012/2012 00:12:55 - INFO - Processing system.sin
02/012/2012 00:12:55 - INFO - Checking header
02/012/2012 00:12:55 - INFO - Flashing data
02/014/2012 00:14:42 - INFO - Processing userdata.sin
02/014/2012 00:14:42 - INFO - Checking header
02/014/2012 00:14:42 - INFO - Flashing data
02/014/2012 00:14:52 - INFO - Processing cache.sin
02/014/2012 00:14:52 - INFO - Checking header
02/014/2012 00:14:52 - INFO - Flashing data
02/014/2012 00:14:52 - INFO - Ending flash session
02/014/2012 00:14:52 - INFO - Flashing finished.
02/014/2012 00:14:52 - INFO - Please unplug and start your phone
02/014/2012 00:14:52 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
02/014/2012 00:14:53 - INFO - Device connected in flash mode
Click to expand...
Click to collapse
jasonmiracle said:
bro, THANKS for your BL locked stock firmware!!! it worked!!! my phone booted, now i am choosing languages!! where did you get that .ftf thing? really a lifesaver...
but one more question, now that i can turn on my phone, that i want to flash other roms, i have to root my phone and unlock BL flash with custom kernel, and flash other roms right? this is my first flashing thats why took so long time digging, finally i got solution from you today when i gave up hope and asked question on xda :good:
Click to expand...
Click to collapse
Yeh, you got it That is the basic procedure. As long as you follow the instructions in the kernel and rom threads carefully you should be ok.
The .ftf is made from the Sony Ericsson firmware that gets downloaded when you repair using SEUS or PC Companion. Not everyone can use the repair-option, that's why i keep it lying around
SmG67 said:
Yeh, you got it That is the basic procedure. As long as you follow the instructions in the kernel and rom threads carefully you should be ok.
The .ftf is made from the Sony Ericsson firmware that gets downloaded when you repair using SEUS or PC Companion. Not everyone can use the repair-option, that's why i keep it lying around
Click to expand...
Click to collapse
thats really a lifesaver ... these weeks i kept digging about other ways other than SEUS... until i know that my phone is Soft bricked, i think there is other ways to solve it :victory: thanks to you flashing custom roms now glad that i have phones to use again waiting for the nexus
SmG67 said:
Yeh, you got it That is the basic procedure. As long as you follow the instructions in the kernel and rom threads carefully you should be ok.
The .ftf is made from the Sony Ericsson firmware that gets downloaded when you repair using SEUS or PC Companion. Not everyone can use the repair-option, that's why i keep it lying around
Click to expand...
Click to collapse
but i wonder why i flashed nna's jb kernels or ics kernels, my phone got into bootloop unable to start up? bootloop at nna loader... thats the problem last time that kept me trying many things and messed up my phone..
jasonmiracle said:
but i wonder why i flashed nna's jb kernels or ics kernels, my phone got into bootloop unable to start up? bootloop at nna loader... thats the problem last time that kept me trying many things and messed up my phone..
Click to expand...
Click to collapse
Follow the instructions carefully, for JB you need to do wipe data/factory reset (in xRecovery or CWM) before you flash the new kernel, and you have to format /system partition in mount and storage menu of CWM to get the proper partition size. After that you install the nAa's JB ROM and appropriate Google Apps, and if that is successful, wipe data/factory reset, wipe cache and in advanced menu wipe dalvik-cache and wipe batterystats... Then Reboot and wait...
SmG67 said:
Follow the instructions carefully, for JB you need to do wipe data/factory reset (in xRecovery or CWM) before you flash the new kernel, and you have to format /system partition in mount and storage menu of CWM to get the proper partition size. After that you install the nAa's JB ROM and appropriate Google Apps, and if that is successful, wipe data/factory reset, wipe cache and in advanced menu wipe dalvik-cache and wipe batterystats... Then Reboot and wait...
Click to expand...
Click to collapse
as what you said i only did not wipe data/factory reset, wipe cache and in advanced menu wipe dalvik-cache and wipe batterystats then Reboot after successful flashing gapps and rom...
Hello, help needed pls
My problem:
-Neo L vibrates when switched on but the screen stays black and the phone heats progressively.
- while on, it happened 2 times that the screen got black during the day. I could take a call once by flipping my finger on the black screen(phone was ringing).
What I tried to solve the issue after reading the forums:
-charge the phone, remove sd and sim card and start the phone. (succeeded 4 or 5 times out of around 50tries in 5 days, doesn't work anymore)
-update the phone and delete all my downloaded apps during the few times where the phone managed to start (didn't help)
-Used Sony PC companion to repair the phone (didn't help).
What I did not do:
- i didn't try flashing whatsoever or mess with the phone in any way(it's my first android phone). Really.
-As far as I know the phone did not receive a choc that could have caused the problem.
- i didn't try calling underwater. Aside from humidity i can not see any cause there
Any idea on how to solve this issue or the cause of the problem would be very helpful. Thanks.
First way
Use my mega guide for neo L in my sig below
And head over to that thread and find unbrick in there !
If that doesn't help then it's mean u can either go to sony or sell it
It is 100% hardware faulty if unbrick doesn't help :angel:
Good luck
Second way
By the way use SUS ! Don't use that suck PC Companion !
SUS is always great
Saingpor said:
First way
Use my mega guide for neo L in my sig below
And head over to that thread and find unbrick in there !
If that doesn't help then it's mean u can either go to sony or sell it
It is 100% hardware faulty if unbrick doesn't help :angel:
Good luck
Second way
By the way use SUS ! Don't use that suck PC Companion !
SUS is always great
Click to expand...
Click to collapse
Hello, thanks for the quick answer,
If you don't mind I think i will start with the second way..looks more reasonable. By SUS you mean Sony ericson Update Service I guess.
I didn't try flashing the phone, if second way doesn't work, do you still think unbrick is appropriate? will it void my warranty (valid in a faraway country)?
Thanks
smead221 said:
Hello, thanks for the quick answer,
If you don't mind I think i will start with the second way..looks more reasonable. By SUS you mean Sony ericson Update Service I guess.
I didn't try flashing the phone, if second way doesn't work, do you still think unbrick is appropriate? will it void my warranty (valid in a faraway country)?
Thanks
Click to expand...
Click to collapse
Unless u unlock BL then it will void your warranty !
I'd prefer flashtool over SUS ! :angel: In some case , what if your pc hang during downloading firmware via SUS ! What if it is in the middle of process ! For unbrick using flash method will be million time easier and save a lot of time !
How can flash ftf void your warranty ? Don't worry mate
Saingpor said:
Unless u unlock BL then it will void your warranty !
I'd prefer flashtool over SUS ! :angel: In some case , what if your pc hang during downloading firmware via SUS ! What if it is in the middle of process ! For unbrick using flash method will be million time easier and save a lot of time !
How can flash ftf void your warranty ? Don't worry mate
Click to expand...
Click to collapse
Sorry, I'm completely new to all this. I'll try as you say tonight after work, thanks again, will keep you updated.
smead221 said:
Sorry, I'm completely new to all this. I'll try as you say tonight after work, thanks again, will keep you updated.
Click to expand...
Click to collapse
Don't worry mate ! And a warm welcome to here !
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- THank to people when they are helping you / You are helped out / Be nice :angel:
Saingpor said:
Don't worry mate ! And a warm welcome to here !
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- THank to people when they are helping you / You are helped out / Be nice :angel:
Click to expand...
Click to collapse
So, here is first result at step 3 of flashing the device from flashtool:
25/023/2013 10:23:14 - INFO - Selected MT25i_4.1.B.0.631_SONY MOBILE by wewenk.ftf
25/023/2013 10:23:14 - INFO - Preparing files for flashing
25/023/2013 10:23:26 - INFO - Please connect your device into flashmode.
25/023/2013 10:23:32 - INFO - Opening device for R/W
25/023/2013 10:23:33 - INFO - Start Flashing
25/023/2013 10:23:33 - INFO - Processing loader
25/023/2013 10:23:33 - INFO - Checking header
25/023/2013 10:23:33 - INFO - Ending flash session
25/023/2013 10:23:33 - ERROR -
25/023/2013 10:23:33 - ERROR - Error flashing. Aborted
25/023/2013 10:23:34 - ERROR - Drivers need to be installed for connected device.
25/023/2013 10:23:34 - ERROR - You can find them in the drivers folder of Flashtool.
I installed flashmode driver after this, there was also drivers for different xperias but i didnt see the Neo L, was there just the flashmode driver to install manuall?
Anyway, second try gives this:
25/047/2013 10:47:23 - INFO - Device connected in flash mode
25/047/2013 10:47:32 - INFO - Selected MT25i_4.1.B.0.631_SONY MOBILE by wewenk.ftf
25/047/2013 10:47:32 - INFO - Preparing files for flashing
25/047/2013 10:47:48 - INFO - Please connect your device into flashmode.
25/047/2013 10:47:48 - INFO - Opening device for R/W
25/047/2013 10:47:48 - INFO - Start Flashing
25/047/2013 10:47:48 - INFO - Processing loader
25/047/2013 10:47:48 - INFO - Checking header
25/047/2013 10:47:48 - INFO - Ending flash session
25/047/2013 10:47:48 - ERROR -
25/047/2013 10:47:48 - ERROR - Error flashing. Aborted
25/047/2013 10:47:49 - INFO - Device connected in flash mode
Any idea of what went wrong?
smead221 said:
So, here is first result at step 3 of flashing the device from flashtool:
25/023/2013 10:23:14 - INFO - Selected MT25i_4.1.B.0.631_SONY MOBILE by wewenk.ftf
25/023/2013 10:23:14 - INFO - Preparing files for flashing
25/023/2013 10:23:26 - INFO - Please connect your device into flashmode.
25/023/2013 10:23:32 - INFO - Opening device for R/W
25/023/2013 10:23:33 - INFO - Start Flashing
25/023/2013 10:23:33 - INFO - Processing loader
25/023/2013 10:23:33 - INFO - Checking header
25/023/2013 10:23:33 - INFO - Ending flash session
25/023/2013 10:23:33 - ERROR -
25/023/2013 10:23:33 - ERROR - Error flashing. Aborted
25/023/2013 10:23:34 - ERROR - Drivers need to be installed for connected device.
25/023/2013 10:23:34 - ERROR - You can find them in the drivers folder of Flashtool.
I installed flashmode driver after this, there was also drivers for different xperias but i didnt see the Neo L, was there just the flashmode driver to install manuall?
Anyway, second try gives this:
25/047/2013 10:47:23 - INFO - Device connected in flash mode
25/047/2013 10:47:32 - INFO - Selected MT25i_4.1.B.0.631_SONY MOBILE by wewenk.ftf
25/047/2013 10:47:32 - INFO - Preparing files for flashing
25/047/2013 10:47:48 - INFO - Please connect your device into flashmode.
25/047/2013 10:47:48 - INFO - Opening device for R/W
25/047/2013 10:47:48 - INFO - Start Flashing
25/047/2013 10:47:48 - INFO - Processing loader
25/047/2013 10:47:48 - INFO - Checking header
25/047/2013 10:47:48 - INFO - Ending flash session
25/047/2013 10:47:48 - ERROR -
25/047/2013 10:47:48 - ERROR - Error flashing. Aborted
25/047/2013 10:47:49 - INFO - Device connected in flash mode
Any idea of what went wrong?
Click to expand...
Click to collapse
Plz check no final verification and see !
If not work then Reboot PC and install fastboot and flashmode driver in flashtool/driver ! There is no neo L driver so just install the 2 that i mentioned !
Plz note windows 8 cause some serious problem which i cant help ! If u r 7 then it is fine !
Hey Saingpor,
It seems the flash was successful. It said Flash successful but afterwards it said something like flashtool needs usb debugging and something else to be activated in order to work (which i can't check since the screen stays black).
So anyway, flash done, phone still not working. I tried changing the microsd and flashing again but with no result. Do you think that it's possible that this one time the phone fell over a month ago can be the cause of a hardware defect that affects the phone now? And if it's from origin, is it possible that the phone works perfectly for 3 months then suddenly stops working?
I don't get this. Anyway, thanks for your help.
smead221 said:
Hey Saingpor,
It seems the flash was successful. It said Flash successful but afterwards it said something like flashtool needs usb debugging and something else to be activated in order to work (which i can't check since the screen stays black).
So anyway, flash done, phone still not working. I tried changing the microsd and flashing again but with no result. Do you think that it's possible that this one time the phone fell over a month ago can be the cause of a hardware defect that affects the phone now? And if it's from origin, is it possible that the phone works perfectly for 3 months then suddenly stops working?
I don't get this. Anyway, thanks for your help.
Click to expand...
Click to collapse
Go to Sony center mate
Sent from neo L using Stock Modded
Hey guys.
It appears you may get this quite a bit, as per usual i've attempted to root and install a custom ROM onto my Xperia Z2.
It seems I've bricked it and I can't seem to install a recovery. Each time I try to flash a recovery I keep getting errors with loader.sin.
Code:
30/048/2014 13:48:39 - INFO - Device connected in flash mode
30/048/2014 13:48:40 - INFO - Opening device for R/W
30/048/2014 13:48:40 - INFO - Reading device information
30/048/2014 13:48:40 - INFO - Phone ready for flashmode operations.
30/048/2014 13:48:40 - INFO - Current device : C6903 - BH91897U0D - 1276-0589_R3C - 1274-8313_14.4.A.0.108 - HUTCH1-LTE_14.4.A.0.108
30/048/2014 13:48:40 - INFO - Start Flashing
30/048/2014 13:48:40 - INFO - Processing loader.sin
30/048/2014 13:48:40 - INFO - Checking header
30/048/2014 13:48:40 - ERROR - Processing of loader.sin finished with errors.
30/048/2014 13:48:40 - INFO - Ending flash session
30/048/2014 13:48:40 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x800A0017 ";
I need to know what's causing this error, and if there's any fix for it. Right now when I try to power on my Xperia Device, it just Vibrates. (If I carry on holding the power button it just vibrates at intervals of 3-4 seconds?)
I've tried searching for fixes of the error but nothing seems to be coming up. Any advice or help is greatly appreciated.
Kubeintosh said:
Hey guys.
It appears you may get this quite a bit, as per usual i've attempted to root and install a custom ROM onto my Xperia Z2.
It seems I've bricked it and I can't seem to install a recovery. Each time I try to flash a recovery I keep getting errors with loader.sin.
Code:
30/048/2014 13:48:39 - INFO - Device connected in flash mode
30/048/2014 13:48:40 - INFO - Opening device for R/W
30/048/2014 13:48:40 - INFO - Reading device information
30/048/2014 13:48:40 - INFO - Phone ready for flashmode operations.
30/048/2014 13:48:40 - INFO - Current device : C6903 - BH91897U0D - 1276-0589_R3C - 1274-8313_14.4.A.0.108 - HUTCH1-LTE_14.4.A.0.108
30/048/2014 13:48:40 - INFO - Start Flashing
30/048/2014 13:48:40 - INFO - Processing loader.sin
30/048/2014 13:48:40 - INFO - Checking header
30/048/2014 13:48:40 - ERROR - Processing of loader.sin finished with errors.
30/048/2014 13:48:40 - INFO - Ending flash session
30/048/2014 13:48:40 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x800A0017 ";
I need to know what's causing this error, and if there's any fix for it. Right now when I try to power on my Xperia Device, it just Vibrates. (If I carry on holding the power button it just vibrates at intervals of 3-4 seconds?)
I've tried searching for fixes of the error but nothing seems to be coming up. Any advice or help is greatly appreciated.
Click to expand...
Click to collapse
It says right here
30/048/2014 13:48:40 - INFO - Current device : C6903 - BH91897U0D - 1276-0589_R3C - 1274-8313_14.4.A.0.108 - HUTCH1-LTE_14.4.A.0.108
Click to expand...
Click to collapse
It says right there your device is a C6903 which is an Xperia Z1, not a Z2
Please post in the Xperia Z1 section as i cant help you all too much
This is Xperia Z2 Section
(D6502/D6502/D6565/S0-0F)
Envious_Data said:
It says right here
It says right there your device is a C6903 which is an Xperia Z1, not a Z2
Please post in the Xperia Z1 section as i cant help you all too much
This is Xperia Z2 Section
(D6502/D6502/D6565/S0-0F)
Click to expand...
Click to collapse
It may say that, but unfortunately I can 100% guarantee to you that my phone is an Xperia Z2.
The version of my phone is D6502 but it's coming up as an Xperia Z1?
Kubeintosh said:
It may say that, but unfortunately I can 100% guarantee to you that my phone is an Xperia Z2.
The version of my phone is D6502 but it's coming up as an Xperia Z1?
Click to expand...
Click to collapse
Odd, it showed as C6903 in the log
(c6903 is Z1 LTE version)
Make sure you install all the drivers for Fastboot, flashmode, Z2 device drivers
Run flashtool as admin and when installing drivers
Not sure what else to tell you :/
If your on linux run as sudo or su
Redownload your FTF sometimes it can Corrupt and cause a processing issue
Here is a brick recovery guide
http://forum.xda-developers.com/showthread.php?p=53220435
Envious_Data said:
Odd, it showed as C6903 in the log
(c6903 is Z1 LTE version)
Make sure you install all the drivers for Fastboot, flashmode, Z2 device drivers
Run flashtool as admin and when installing drivers
Not sure what else to tell you :/
If your on linux run as sudo or su
Redownload your FTF sometimes it can Corrupt and cause a processing issue
Here is a brick recovery guide
http://forum.xda-developers.com/showthread.php?p=53220435
Click to expand...
Click to collapse
Thanks for your help, I'm re-downloading everything onto a new computer I've installed Flashtool and the drivers for Fastboot and Flashtool and Z2 drivers. Just waiting for the FTF to download and give that a try. Since I have Sony PC Comp on my laptop I figured that might be something that's getting in the way so I'll try it on my Desktop to see if that makes any difference.
I'll reply here if I fix it or any other errors come up. Thank you for your help.
So after a lot of fiddling about and thought processing, It's working again.
Somehow I've managed to downgrade it to a Z1 which i'm not happy about but atleast it's working. What I think I did, was installed a Z1 boot.img, making it come up as a Z1 through the drivers. Hence why it wasn't seeming to work. Would there be anyway to upgrade the software in any way or form?
Kubeintosh said:
So after a lot of fiddling about and thought processing, It's working again.
Somehow I've managed to downgrade it to a Z1 which i'm not happy about but atleast it's working. What I think I did, was installed a Z1 boot.img, making it come up as a Z1 through the drivers. Hence why it wasn't seeming to work. Would there be anyway to upgrade the software in any way or form?
Click to expand...
Click to collapse
I have no idea,
Im generaly confused because it shouldent work at all if you installed a Z1 boot image
Envious_Data said:
I have no idea,
Im generaly confused because it shouldent work at all if you installed a Z1 boot image
Click to expand...
Click to collapse
That's why i'm extremely confused as to why it worked. It is a definite D6, yet it's running Z1 Firmware. Maybe i've uncovered something.
@Kubeintosh
Can you check with CPU -Z about your processor/SOC model.
https://play.google.com/store/apps/details?id=com.cpuid.cpu_z
If it's Snapdragon 800 ,it's Xperia Z1 ,If it's 801 it's Xperia Z2 .
In case it's Xperia Z2 ,then you will need to flash Z2 FTF ticking the option "No final verification"
However ,Doing this trick on an Xperia Z1 might hard brick the device .
You need to verify what device you have. first and foremost.