guyzz,
im having a problem with my phone rigt now
installed a couple days a ago doomkernel and flashed the xperia sspeed on my xps.
And today i wanted to flash the lebanon .73 http://forum.xda-developers.com/show....php?t=1569453 via the flashtool but it failed somehow and this is what flashtool reported.
22/035/2012 16:35:54 - ERROR -
22/035/2012 16:35:54 - ERROR - Error flashing. Aborted
22/035/2012 16:35:55 - ERROR - Drivers need to be installed for connected device.
22/035/2012 16:35:55 - ERROR - You can find them in the drivers folder of Flashtool.
the result is that i can't boot succesfully. Everytime i want to boot, the phone reboots at the doomkernel logo and goes off and again reboots at the doomkernel's logo. only way to stop the boot is to reset the phone bij holding powerbutten and up/down volume together (3Xvibration)
Please can someone save this phone, i m going crazy right noww
Did you already installed the drivers (again?) in C:\Flashtool\drivers
i dont think that it has to do something with the compitability of 73, cuz first i wass on lebanon root 73 and installed the doomkernel and it worked just fine, and thereafter i installed via the cwr the experia sspeed zip file.
and after a while i wanted to go back to my old rom by flashing the ftf file of the lebanon rom 73, but that failed as i mentioned above
which drivers ? is just installed thiss
http://androxyde.github.com/Flashtool/
look in the place where you have installed Flashtool.
Default location is: C:\Flashtool\drivers
there you will find one file with the name "Flashtool-drivers.exe"
with that u can install the drivers (it can take some time)
Bro you r the King you saved this phone and me too muahaha, im so happy i found out what you mentioned earlier, and its now flashing the rom ^^.
Related
I tried to unlock bootloader following the guide on the developer section (actually, only the "guide" in the header, 1 step). I tried multiple times, and this always happen (attachment)
edited:
This seems to be the situation for the fxp 123 too.
--
As I'm a noob. I have no idea whether to flash the fxp 123 with our without bootloader. Anyhow.. as my question says.. I can't do ether.
odd,
i actually did the exact same thing and its fine here.
this is what your trying to do yes ?(below)
•flash the azuzu kernel downgrade ftf with flashtool
•disconnect usb cable, press power button until phone vibrates shortly and immidiatly connect the usb cable again (it is supposed to be stuck at SE logo)
•start the batch file for unlocking bootloader, cause it says press any button before it starts, it won't start unlocking until you press any button
•now wait until flashtool recognizes your x10 (if flashtool doesn't do anything, check third post please! thx)
•close flashtool and then press any button in the cmd window that the unlocking process starts (please close flashtool, instead the bl unlock cmd and flashtool are constantly killing and restarting adb!!)
•after unlocking is finish you have to flash azuzu kernel upgrade
•now power on phone to check if the phone is starting after the unlock (if you are using a custom kernel yet with the bypass method and get stuck in a bootloop enter xrecovery and clear dalvik-cache, then your phone should boot up again fine)
•power off phone and flash dooms ck v05-fs with flashtool
•now flash the wifi modules for dooms ck with recovery. (atm the update.zips are for xrec, but for sure please always check dooms kernel-thread if there is anything changed)
•power on phone again and if everything is right, read the line under that one
•WOOOHOOO!!! Here you are with unlocked bootloader, custom kernel directly loaded AND without reflashing any rom, means you have kept your current installation
a.have you tried checking the S1Tool to see if you can unlock ive seen people saying its just not an option.
b. what are you choosing to flash ? i actually selected kernel straight away on the downgrade part
maybe use the s1tool and post that so people can respond to that
No. It says I only have to flash the X10_V1_BLRelock.ftf, if I'm going to a custom ROM afterwards.
Have I misunderstood?
i guess its me misunderstanding
could you like me the thread where you got the file from or your guide
if your unlocking your bootloader i find it odd that the file says BL''RELOCK''
anyways this is the guide i followed and worked like a charm.
http://forum.xda-developers.com/showthread.php?t=1254087&highlight=blrelock
the first post has the guide and my files were called the following
qsd8250 (zip file wich held the qsd8250_semc.bat)
wich allowed me to unlock the bootloader (this file had nothing to do with flashtool)
only used flastool for 2 things.
1) downgrade kernel
2) after qsd8250 was done unlocking bootloader to upgrade kernel to doomkernels V6 for UL bootloaders (was my choice of kernel)
That was the guide I used too.
"If you aren't keeping your current device configuration (because of flashing another rom after unlocking bootloader or anything else) the simplest way to unlock is to flash stock 2.3.3 rom, root it and use the bl unlock plugin from latest flashtool"
So i took the flash thing named bl_something..
---
As it seems that was wrong, can you give me a quick tutorial, as I didn't quit understand your way. and this one mention and easy way to do it if you'r going to change ROM at once.
tutorial read beyond the big text http://forum.xda-developers.com/showthread.php?t=1254087
basicly it says this.
1) get the files you need
semc bat is for x10i and x10a. But only if you haven't tried any simunlocking
the bl unlock file from this thread: http://forum.xda-developers.com/show....php?t=1253277 - thanks to the_laser
Kernel up/downgrade for flashtool from here: - thanks to azuzu im using FlashTool_0.2.9.1-GBready_root_xRec
and a custom kernel for Unlocked bootloaders (since your unlocking it )
i used doomkernels v6 for UL BL
Wifi modules for kernel if needed mine had it built in
and then the guide tells you to do this
Please make sure you have enabled usb-debugging in your current rom before starting with this!!
•flash the azuzu kernel downgrade ftf with flashtool
(i opened flashtool selected flash and then selected 'kernel downgrade' and in the other tab i skipped the 'loader' and selected 'kernel')
•disconnect usb cable, press power button until phone vibrates shortly and immidiatly connect the usb cable again (it is supposed to be stuck at SE logo)
(it asks you to do this and so i did)
1) turn off phone
2)unplug phone
3)hold back button
4)stil while holding back button plug phone in
5) flashtool takes over and you can let go
•start the batch file for unlocking bootloader, cause it says press any button before it starts, it won't start unlocking until you press any button
(when its done open the qsd8250 file wich you unzip(ped) and start the qsd8250_semc.cmd)
•now wait until flashtool recognizes your x10 (if flashtool doesn't do anything, check third post please! thx)
•close flashtool and then press any button in the cmd window that the unlocking process starts (please close flashtool, instead the bl unlock cmd and flashtool are constantly killing and restarting adb!!)
•after unlocking is finished you have to flash azuzu kernel upgrade
(same deal as the downgrade)
•now power on phone to check if the phone is starting after the unlock (if you are using a custom kernel yet with the bypass method and get stuck in a bootloop enter xrecovery and clear dalvik-cache, then your phone should boot up again fine)
•power off phone and flash the kernel you downloaded with flashtool
(the one you picked as said i used doomkernels v6 for UL BL)
•now flash the wifi modules if its needed with xrecovery. NOT FLASHTOOL!!!!
•power on phone again and if everything is right, read the line under that one
If you aren't seeing the se logo at turning on phone, but directly the custom kernel logo, you were succesfully. If you want to enter xrecovery you have to spam the back button now if the xperia logo appears instead of the se logo.
and thats it
all thnx should go to 9Lukas5 since i just copy / pasted evrything that he wrote
It's stuck here at the upgrade...
04/010/2012 20:10:39 - INFO - <- This level is successfully initialized
04/010/2012 20:10:39 - INFO - Flashtool Version 0.8.4.0 built on 2012-06-02 11:54:12
04/010/2012 20:10:39 - INFO - You can drag and drop ftf files here to start flashing them
04/010/2012 20:10:45 - INFO - Device connected in flash mode
04/010/2012 20:10:47 - INFO - Selected X10_aZuZu_Kernel_UpGrade_Generic.ftf
04/010/2012 20:10:47 - INFO - Preparing files for flashing
04/010/2012 20:10:47 - INFO - Please connect your device into flashmode.
04/010/2012 20:10:47 - INFO - Opening device for R/W
04/010/2012 20:10:47 - INFO - Reading device information
And when are the bat file finished, it didn't give a clear message, so after a while i exited it.
the bat file auto exits when completed cant remember but it asks you to press any key again and when you do it auto closes
make sure thats done and make sure you do this while flashtool is closed
so close flashtool before pressing any key in de bat file
and i dont see an error in the flash tool info you posted ? how is it stuck ?
i dont know if it matters but i actually upgraded straight away to the kernel i wanted to use
so instead of doing the kernel upgrade delivered with flashtool i upgraded to doomkernels v6 ULBL
seems like your almost there
The upgrade didn't continue..
I'll try your method instead, as for the bat tool.. it's "stuck" at the *daemon started successfully*
ah yeah ok
its bat file first while flashtools turned of
then when it auto closed turn flashtool back on and upgrade
I don't think you understood my explanation
First I downgraded
then I started the bat
then I closed the flashtool
then I pressed "any key" in the bat
then it got stuck on *daemon started successfully*, and it still get stucks there.
xVenator said:
I don't think you understood my exploitation
First I downgraded
then I started the bat
then I closed the flashtool
then I pressed "any key" in the bat
then it got stuck on *daemon started successfully*, and it still get stucks there.
Click to expand...
Click to collapse
I think u may be missing adb drivers on ur pc
Sent from my Xperia X10 using XDA
I think you might be right.
First, after a while just having the bat file opened this pops up: "error: protocol fault (no status)". Whatever that means, and it get stuck at the deamon thing again.
however when I start flashtool while having the bat file open it starts killing the apb server because it is out of date.
now.. what is adb server and how do I update/Install it?
Also, when I get this apb server thing installed ( can anyone link? ), can I use FXP 123 to upgrade with?
edit:
I used another computer, as I was away from my main computer. I got no problem with the adb server there, other than windows defender, but I manage to allow it
now, back to the question above: Can I install FXP 123 as custom kernal? instead of upgrade?
Thats what i did but with doomkernels v6 and no pro lems here ... maybe just to be safe flash the upgrade first then your fx123 its how the guide told us to do it
Sent from my X10 using xda premium
and so I did
Then I installed CM7 FXP123 .... stuck at CM7 loading logo
any idea what happend?
---
btw, thank you so much for the help so far! I really appreciate it and ofc used the thanks button! ^^
Redo de wipes ... enter recovery if you can? Its the rom loadin not kernel is it?
Then full wipe
Wipe cache partition
And wipe dalvik cache or whatever its called
In xrecovery its in adv option i believe
Ive googled some more and dalviks cache alone might even be sufficient
Sent from my CM7 Zmod / doomkernels v6 UL BL X10!
(And all that without bricking it) so far atleast.
xVenator said:
I think you might be right.
First, after a while just having the bat file opened this pops up: "error: protocol fault (no status)". Whatever that means, and it get stuck at the deamon thing again.
however when I start flashtool while having the bat file open it starts killing the apb server because it is out of date.
now.. what is adb server and how do I update/Install it?
Click to expand...
Click to collapse
To fully run adb u need to download java runtime environment and android SDK. The reason I think its adb is because it stops after saying starting daemon. This I think is adb starting
Sent from my Xperia X10 using XDA
Got everything working now.. except, I don't have a market app
As I said I just used another computer and the bat file worked, and after wiping all data as Bjornlindekens suggested I got it running.
Thanks all!
this is what i found so far.
(Amaurilol)
''Try finding an apk file for the market. Uninstall the one of your phone and install the downloaded one.''
http://www.filecrop.com/google-market.apk.html
flash google apps.zip if there is one ?(for your rom)
can you locate the market app in your settings/applications ?
only found 1 simular problem and doesnt say if its solved or not
and
(Ynkamat)
''Or else do a manual install of market app. We have a lots of them in apps section. Fix permissions. Use android commander from pc and install that app as a system app. But you need google account and its services to detect''
I formatted my system,data,cache,dalvik cache and didnt install any custom rom and rebooted directly
now it is stuck at the sony logo,I was using Ex MIUI v4 (ICS)
my bootloader was locked..
I tried connecting to flashmode in flashtool and in SEUS,but the phone isnt detected..
PLZ HELP ME
anivesh93 said:
I formatted my system,data,cache,dalvik cache and didnt install any custom rom and rebooted directly
now it is stuck at the sony logo,I was using Ex MIUI v4 (ICS)
my bootloader was locked..
I tried connecting to flashmode in flashtool and in SEUS,but the phone isnt detected..
PLZ HELP ME
Click to expand...
Click to collapse
Can you explain with more detail about "connecting to flashmode in flashtool" ?
I read in some posts-connect your phone to flashtool and flash the stock firmware files to get back your phone
I connected my phone with the volume key down to flashtool,but it stated an error and didnt proceed..
You erased everything, obviousely. But Flashtool should still work.
I'll go searching for a user who I know already did the same as you... maybe he'll have useful information
EDIT
Which error?
Feanor88 said:
You erased everything, obviousely. But Flashtool should still work.
I'll go searching for a user who I know already did the same as you... maybe he'll have useful information
EDIT
Which error?
Click to expand...
Click to collapse
It says ERROR-
thats it
Which sony logo, The first at boot or the boot animation one?
Are you able to boot your device in clockworkmmod?
Ok, let's do this:
-Start Flashtool
-Plug USB cable to PC
-Turn off the phone
-Press and hold volume down button
-Plug microUSB to the phone
-Post the complete Flashtool log
By the way, did you install flashmode drivers?
hsrbnr said:
Which sony logo, The first at boot or the boot animation one?
Are you able to boot your device in clockworkmmod?
Click to expand...
Click to collapse
He formatted everything, CWM included.
I installed the flashmode drivers..
It gets stuck at the black sony logo at the start and does nothing,I had to switch it off after removing the battery..
When I connect the phone in flashmode,it says error and says device disconnected and then the phone remains at sony logo..
I'll post the log soon
GOOD NEWS!
I tried flashtool again and this time it WORKED!!
THANK YOU TO ALL
p.s-Now I'm on stock GB .58
Try to flash a different ftf file and see, preferentially an old GB Build.
If this doesn't work,
Try updating to latest Flashtool.
Install the exe at /flashtool/drivers folder.
Then flash again.
Thanks,
Rick
Edit: Okay, never mind. It's done.
DragonClawsAreSharp said:
Try to flash a different ftf file and see, preferentially an old GB Build.
If this doesn't work,
Try updating to latest Flashtool.
Install the exe at /flashtool/drivers folder.
Then flash again.
Thanks,
Rick
Edit: Okay, never mind. It's done.
Click to expand...
Click to collapse
Actually I was first flashing the ICS .ftf file,then I flashed the .58 GB build and then it worked..
thanks for your response anyway
Hello guys.
I recently got an Xperia X10 mini with stock rom, 2.1a, officially updated with last and I decided to install GB.
I follow several tutorials and do the bootloader unlock correctly. After this, looking for a GB ROM, I see that firstly I need to change the Kernel (In this case, "[KERNEL] nAa-14 [23/8/12] Custom Gingerbread kernel" to install the "[ROM] MiniCM7-2.2.1 [10/6/12] Gingerbread 2.3.7".
Then, I copy the "E10_nAa-14_2.6.29.6-nAa-14.ftf" to the firmwares folder in Flashtool folder.
After this, I open the flashtool app, plug the phone in flash mode and click on the flash button. Then, select "Flashmode" and select the Firmware nAa-14, and the kernel.sin file. Press OK and the system starts copying files. Then, the program finish copying and says "now unplug the device and power it on".
I disconnect the cable and here comes the problem. The phone doesn't boots, nothing on screen, and when I try to connect in flash mode, flashtool says:
ERROR - Drivers need to be installed for connected device.
ERROR - You can find them in the drivers folder of Flashtool.
No leds and nothing in the screen. Is there any solution to make the phone come to live?
Thanks guys, any help is appreciated.
Not sure, but when I flashed from stock to MiniCM7 i did more steps than you.
- ROOTed
- installed CWM
- unlocked bootloader
And when flashed KERNEL - Flashtool after finishing told me: DONE - WAIT YOUR DEVICE WILL RESTART... So maybe you read something different (bad)...
(in my case phone not restart, but after unpluging and power on - new start logo appears)
Try the small red button under back-cover -> you should see it in lower left corner near the sticker. Maybe it helps... but only small chance
A couple of days ago my xperia mini pro started acting strange. after turning the screen off once, it wouldn't turn on. i coudn't see anything, if a call comes i hear the ringtone and can't answer it.the problem persisted on rebooting.
so i thought about installing cm 9.0 fresh again as i was gonna do it anyways. so i reboot it and get to cwm, i goto installing new cm and it says: finding update package, opening update package, installing update.... it got stuck here kept it for an hour and no luck. so i pulled the battery and reinserted it. on booting it got stuck in a bootloop. so i tried to restore my previous cm9 and it checked the md5 sum and started restoring system, and it stuck there. i tried restoring it to other backups and it gets stuck at some point in restoring sytem.
i can get into cwm but restoring gets stuck midway, so its not much use.
the xperiamini pro is rooted and bootloader unlocked. need help.
EDIT:
found the root cause
the cwm basically loses connection with the sd card after certain time. so can't restore, install, mount(for pc). all gets stuck midway. So i threw away the sd card. got a new one. copied the backup and voila its good as new. now i am back in cm9.1.
Re: CWM gets stuck and no rom
Change your kernel and try cwm again...
Regards,
AJ
Is there any way to know the battery percent in this situation. when connecting charger, it bootloops. and so i don't wanna use flashtool without knowing how much battery i have.
when i try to connect it via flashmode, it connects for some time and then starts booting
mnishamk said:
Is there any way to know the battery percent in this situation. when connecting charger, it bootloops. and so i don't wanna use flashtool without knowing how much battery i have.
when i try to connect it via flashmode, it connects for some time and then starts booting
Click to expand...
Click to collapse
Don't worry about battery. Kernel flash lasts 2-3 secs.
ctragas said:
Don't worry about battery. Kernel flash lasts 2-3 secs.
Click to expand...
Click to collapse
i cant use flashtool, after exactly 40 seconds on connecting via flashmod, the connection breaks and the devices boots. i tried flashmod with emma, it didn;t reboot but it doesn't have anything for my phone.
any way i can get links to other better kernels for sk17i. (maybe lupus?)
mnishamk said:
i cant use flashtool, after exactly 40 seconds on connecting via flashmod, the connection breaks and the devices boots. i tried flashmod with emma, it didn;t reboot but it doesn't have anything for my phone.
any way i can get links to other better kernels for sk17i. (maybe lupus?)
Click to expand...
Click to collapse
Use Fastboot. Copy boot.img to fastboot directory. Power off your phone. Go to fastboot directory, press the vol up button and connect phone with PC via USB cable. You'll hear the connection tone and led will become blue. Release vol up button. Run flash.cmd and it's done. All you need is 2-3 secs.
ctragas said:
Use Fastboot. Copy boot.img to fastboot directory. Power off your phone. Go to fastboot directory, press the vol up button and connect phone with PC via USB cable. You'll hear the connection tone and led will become blue. Release vol up button. Run flash.cmd and it's done. All you need is 2-3 secs.
Click to expand...
Click to collapse
which is fastboot directory for flashtool, or do i have to use sdk through cmd?
is it in drivers/sk17? under that which one?
can't use fastboot, flashtool says no drivers. when i try to install them windows says some drivers could not be installed and i get the same error
25/049/2013 18:49:56 - ERROR - Drivers need to be installed for connected device.
25/049/2013 18:49:56 - ERROR - You can find them in the drivers folder of Flashtool.
Re: CWM gets stuck and no rom
mnishamk said:
which is fastboot directory for flashtool, or do i have to use sdk through cmd?
is it in drivers/sk17? under that which one?
can't use fastboot, flashtool says no drivers. when i try to install them windows says some drivers could not be installed and i get the same error
25/049/2013 18:49:56 - ERROR - Drivers need to be installed for connected device.
25/049/2013 18:49:56 - ERROR - You can find them in the drivers folder of Flashtool.
Click to expand...
Click to collapse
The log tells you, what to do:
Go to c:/Flashtool/drivers folder and run exe. Install fastboot driver, flashmode driver, and your phones driver. (or simply install all)
Sent from my Xperia Ray using xda premium
Wechy77 said:
The log tells you, what to do:
Go to c:/Flashtool/drivers folder and run exe. Install fastboot driver, flashmode driver, and your phones driver. (or simply install all)
Sent from my Xperia Ray using xda premium
Click to expand...
Click to collapse
that was win 8 problem, solved it now getting this error
Device connected in fastboot mode
26/043/2013 18:43:50 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\boot.img
26/043/2013 18:43:50 - INFO - Flashing selected kernel
26/043/2013 18:43:51 - INFO - sending 'boot' (7428 KB)...
26/043/2013 18:43:51 - INFO - FAILED (remote: Unrecognized command, bork!)
26/043/2013 18:43:51 - INFO - finished. total time: 0.000s
26/043/2013 18:43:51 - INFO - FASTBOOT Output:
sending 'boot' (7428 KB)...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 0.000s
kernel is kernel_mini_pro_ics_lupus_v3_cwm
EDIT:
This is specifically a win 8 issue! couldn't do it in a lap with win 8 either. could easily do it with win 7.
now i am running lupus kernel and the restore still gets stuck
using cwm v5.0.2.7 (by KrSH)
I gave up on cwm, had a stock ftf lying around flashed it the old fashioned way.
its a far cry from cm, i feel like i'm in the stone age. but still beats having a useless phone.
too scared to try cwm again.
now back in cm9.
mnishamk said:
A couple of days ago my xperia mini pro started acting strange. after turning the screen off once, it wouldn't turn on. i coudn't see anything, if a call comes i hear the ringtone and can't answer it.the problem persisted on rebooting.
so i thought about installing cm 9.0 fresh again as i was gonna do it anyways. so i reboot it and get to cwm, i goto installing new cm and it says: finding update package, opening update package, installing update.... it got stuck here kept it for an hour and no luck. so i pulled the battery and reinserted it. on booting it got stuck in a bootloop. so i tried to restore my previous cm9 and it checked the md5 sum and started restoring system, all was well and then this phasebeam.apk came and it stuck there. i tried restoring it to other backups and it gets stuck at some point in restoring sytem.
i have a cwm v6. i haven't done a wipe data/system yet afraid the result might not be pretty.Now basically i have a phone which gets stuck in bootloop if opened normally and i can get into cwm but restoring gets stuck midway, so its not much use.
i tried using flashtool, when i connected in flashmod it recognised it but after 5 or 6 seconds the phone starts booting and the flashmod connectino breaks.
the xperiamini pro is rooted and bootloader unlocked. need help.
Click to expand...
Click to collapse
this a link of lww
but u can try for sk17i
see this process and try u can find a clear image of process
http://www.thinkdigit.com/forum/mob...on-rooting-live-walkman-works-other-also.html
sry for my bad english
Hello, Iam totaly f***ed up, I have Xperia P, rooted, unlocked bootloader, CWM recovery, with Cyanogenmod. Well at least last time CM worked, it was version for some tablet and I wanted to flash right ROM. But via CWM recovery it failed, so I connected phone to PC, launched "Minimal ADB and FASTBOOT" and flashed boot.img ( fastboot flash boot boot.img )from CM zip. It said it worked, but when I rebooted my phone, there was just red LED diode, and no light from screen or back/home buttons at all. When I wanted to flash stock firmware via "Flashtool", it said my devide drivers arent installed, but I installed them before from "drivers" folder in Flastool folder. So I downloaded some other drivers, but it f***ed up somehow, and now my computer cant install right drivers and when I connect my phone to PC in fastbootmode? (holding volume down when connecting USB), Iam stuck at Windows installing SOMC Flash Device, and it fails in couple of minutes. I really dont know what to do now. please help...
EDIT: ok my problem with SOMC Flash Device driver is solved... I just didnt hold volume down button long enough hope this will help someone too but still I have unusable phone and I need to instal stock firmware or something else that will help