Related
Hi friends,
I think I have bricked my X10i B'cuz the phone is struck at the Sony Ericsson logo.
What I tried to do?
I was in tripndoid MIUI, so I wanted to upgrade the rom to black edition, so I tried to unlock the boot-loader, I had successfully downgraded the firmware and unlocked the boot-loader and also updated to custom kernel (doomloard)
After that I got in CWM recovery mode and installed the .zip file after cleaning the system cache and dalviks cache, Now the phone refuses to start nor get into flash mode.
I tried removing the battery and reinstalling the battery, but as soon as I put the battery back on the phone lights up at the Sony logo.
Even If it try to charge the phone from the electrical socket, the led of the phone does not turn on, it still gets into the Sony logo and stops there.
The phone gets recognized in the flash tool, its tells the phone is in ADB mode. I cannot put the phone on flash mode anymore.
I tried looking in various threads, but could not get a concrete answer, please help. I have limited access to internet, So i do not have PC companion to try and repair my phone. Is there any way that I can get back my phone alive.
Edit: I just plugged it in, I can get into flash mode.. Anyone please help me how can I flash back to any rom..
Did you flash the upgrade firmware after downgrading and unlocking firmware? Sometimes the Kernel doesn't support certain ROMs as well and it can't boot into the system.
The easy method of flashing the stock SE firmware is by using the X10 Flashtool. Simply download and install it (you might have to turn off anti-virus software as it's listed as a virus of some kind) and install the stock SE 2.3.3 firmware and press flash. Instructions will pop up and your phone will be as good as new. It does mean that you lose everything like ck, recovery, unlocked bootloader, etc.
You can find the Flashtool and the stock firmwares here:
http://forum.xda-developers.com/showthread.php?t=920746
EDIT: To do flashing, you will have to turn the phone off. The X10 may turn on when you reinsert the battery too soon, like you have described. Generally, you should take the battery out for about 5 seconds before reinserting it so the phone actually turns off and doesn't turn back on.
Good luck and don't forget to hit thanks if this helped in some way
@ Panzerfaust101 - I have already hit thanks
I figured it out myself.. here is how I made it through..
Problem - was in the Kernel, just out of some instinct I downloaded Doom's kernel v.006 and some how got the phone into flash mode and flashed the kernel.
After that I was able to navigate into recovery and install the new ROM, but my problem did not stop. Now the phone got struck in the new RoM's startup screen.
So again I downloaded the right version of Doom's kernel for the RoM and flashed it again. So I got the problem solved, but I realized the phone radio was not working, So I again downgraded the firmware and ran the bootunlocker and then updated the phone back to the right kernel.
Now I am able to enjoy the new ROM.
Yeah, it should be your ck. I flashed a ck before (can't remember which one), but for one reason or another, I couldn't get cwm-based recovery working, so I tried another one which couldn't boot anything up properly, so I'm back on stock 2.3.3 (was on the MIUI-based BlackHD Edition. Brilliant ROM btw) waiting for beta+ CM9 ROM for X10 to be released
Btw, for future reference, can you link me the exact Doom ck that you used? I'm probably going to install a custom ROM on mine again and I need to know one that will be guaranteed to work without a problem. Thanks
Cool, you will need Doom's kernal - X10_FXP_DooMKernel-v05a-BootManager-v1.3
Also hope you have the bootlocker unlocked, if not you need to use X10_aZuZu_Kernel_Downgrade_Generic firmware and unlock the boot loader after that you can directly upgrade the firmware to Doom's kernel and install the RoM.
Thanks to DooM and aZuZu for the files.
Kernal link
http://forum.xda-developers.com/showthread.php?t=1362392&page=90
i've your same problem...how i can plug-in in flash mode?
Try this trick!!!
Remove the battery.
Connect your phone to system with the battery still out.
Now hold the back button and put the battery on, green led will glow.
Now you are on flash mode and this would stay for not more than 5-10 secs
You should have quick fingers, so that you should select the firmware or any update within those ten sec's. Keep trying this will work... BTW its was the only way I could revive my phone.
but pc don't recognize my x10...
Shindoruk said:
but pc don't recognize my x10...
Click to expand...
Click to collapse
Are you using a flashtool or Pc Companion? Also please reinstall the adb drivers to your PC and check again.
amrth said:
Try this trick!!!
Remove the battery.
Connect your phone to system with the battery still out.
Now hold the back button and put the battery on, green led will glow.
Now you are on flash mode and this would stay for not more than 5-10 secs
You should have quick fingers, so that you should select the firmware or any update within those ten sec's. Keep trying this will work... BTW its was the only way I could revive my phone.
Click to expand...
Click to collapse
Is that the method you use to flashing? I've seen it quite a lot on these forums, but I haven't personally used it before and I've been curious as to what they did. Generally, don't you prepare to flash by pressing the flash button on Flashtool and following the instructions that pop up? i.e. disconnect and turn off phone, hold back button, reconnect phone. I've always used this method for flashing. Doesn't it work properly for some devices?
Also, if the battery's out and the flashing takes 10+ seconds, what happens? does it stay on once it's detected a device flashing the firmware?
Panzerfaust101 said:
Is that the method you use to flashing? I've seen it quite a lot on these forums, but I haven't personally used it before and I've been curious as to what they did. Generally, don't you prepare to flash by pressing the flash button on Flashtool and following the instructions that pop up? i.e. disconnect and turn off phone, hold back button, reconnect phone. I've always used this method for flashing. Doesn't it work properly for some devices?
Also, if the battery's out and the flashing takes 10+ seconds, what happens? does it stay on once it's detected a device flashing the firmware?
Click to expand...
Click to collapse
The ten seconds isnt a standard just a rough idea. Yeah the flashtool way is proper way to enter flashmode it just that the USB socket on this model isn't the best, many people had problems and basically just found their own way around it.
Sent from my X10i using XDA App
Pleeease, I need help.
My x10 enters in flash mode with the green led, but it still only 10 seconds on, after that change to SE logo and that's it...I think that it's because it ran out of battery...any solution for this!?!?
After that I can leave it connected by USB but still being with the SE logo and it doesn't seem that the battery is charging.
Even if I take off the battery, put in again and simply connect it by USB the SE logo shows again...I don't know what else to do...
This is Flash tool log:
11/035/2012 15:35:25 - INFO - Device connected in flash mode
11/035/2012 15:35:44 - INFO - Device disconnected
11/035/2012 15:35:45 - INFO - Device connected with USB debugging off
11/035/2012 15:35:45 - INFO - For 2011 devices line, be sure you are not in MTP mode
Did you flash the upgrade firmware after downgrading and unlocking firmware? Sometimes the Kernel doesn't support certain ROMs as well and it can't boot into the system.
The easy method of flashing the stock SE firmware is by using the X10 Flashtool. Simply download and install it (you might have to turn off anti-virus software as it's listed as a virus of some kind) and install the stock SE 2.3.3 firmware and press flash. Instructions will pop up and your phone will be as good as new. It does mean that you lose everything like ck, recovery, unlocked bootloader, etc.
You can find the Flashtool and the stock firmwares here:
http://forum.xda-developers.com/showthread.php?t=920746
I wish i can download the .ftf from the link that u had provided , please can any1 provide me a correct link, so i can unbrick my phone.
Panzerfaust101 said:
Is that the method you use to flashing? Doesn't it work properly for some devices?
Also, if the battery's out and the flashing takes 10+ seconds, what happens? does it stay on once it's detected a device flashing the firmware?
Click to expand...
Click to collapse
Kind of a late reply, apologies for that. Yes I followed the same method as listed. Some times your method works but not always!!!
If the battery is below 5% i believe the system will not get you into the flash mode. Since flashing hardly takes few seconds, I suppose the available battery will hold on.
BTW my trick starts only after I get into the flash tool
laneyofdeath said:
The ten seconds isnt a standard just a rough idea. Yeah the flashtool way is proper way to enter flashmode it just that the USB socket on this model isn't the best, many people had problems and basically just found their own way around it.
Click to expand...
Click to collapse
+1, I agree to this.
_CoRo_ said:
Pleeease, I need help.
My x10 enters in flash mode with the green led, but it still only 10 seconds on, after that change to SE logo and that's it...I think that it's because it ran out of battery...any solution for this!?!?
Click to expand...
Click to collapse
I don't think its cuz of a battery issue, It cuz of kernel issue. Kindly give a backdrop of what you are trying to do? Might be helpful to correlate the actions.
uglyprince said:
I wish i can download the .ftf from the link that u had provided , please can any1 provide me a correct link, so i can unbrick my phone.
Click to expand...
Click to collapse
Yes mate I tried the same tool that you have posted. Yeas I did upgrade the firmware to custom kernel and then went ahead with the installation.
Try this link : http://www.mediafire.com/?3ol6gpykaa5acwo
Thank 7hr08ik for this link. Please use the FXp kernal, not DooM.
Major update is that DooM kernel version that I had installed was completely a phone crasher, So I had to update the kernal and the RoM for a newer version.
Right now I am using FXP kernal with v3 of the blackedition HD v1.3 RoM, So far So good
Cheers
Amrth
Okay, I'm not sure exactly what you'll need to know to help, so I'll just tell you what I think is important....
Current situation:
- If I boot the phone normally it freezes at the SONY screen and goes no further.
- If I attempt to boot into recovery mode, it loads the CWM screen (logo in the middle with instructions at bottom), but no actual menu or options. After about 5 seconds, this screen disappears, the phone reboots and then gets stuck on the SONY screen.
- If I connect the phone to the computer in Flashmode Flashtool recognizes it as being connected, but regardless of what I do, after about 2mins the phone reboots, loses connection with the computer, and freezes on the SONY screen as before mentioned.
- If I connect the phone to the computer normally while stuck on the SONY screen, the PC recognizes it though doesn't allow me to do anything to it, and Flashtool says I need to install drivers (I have installed every driver that comes with Flashtool).
How I got here:
- I've rooted the phone
- I've flashed Z2_DooMLoRD_AdvStkKernel_FW-438-v05
- I've unlocked the bootloader (via Flashtool)
- I've installed [Rom][Unofficial]Slim Rom 4.4.4 based on CM11.0, ROM for the Sony Xperia Z2
The phone was okay up until this point, however I wasn't happy with the ROM so I tried to reboot into recovery mode to wipe and install Carbon. This is when the trouble began.
Now it seems I can't do anything :/
Please help. This phone is literally 3 days and it looks like I've completely screwed it >.<
Thanks!
How to recover your device from almost any kind of brick
Requirements
Check the pinned sites
Flashtool
FTF of choice for your device
2 Rubber bands (I am serious but only if your device has no response)
Step1
unplug your device from anything
open flashtool on your pc
plug your cable into your PC
do not plug the cable into your device
Step2
Hold your power button and your volume up button at the same time
your device should buzz 3 times
(this should take a few secconds)
if it does not take a few seconds then you need to put a rubber band around your device holding your power button and your volume up button, DO NOT LEAVE MORE THAN IT NEEDS TO BE LEFT, wait patiently for your device to buzz 3 times
Step 3
once your device has buzzed 3 times you are free to flash a FTF as your device is powered off
step4
if you dont know how to flash a FTF but have gotten as far as installing flashtool,Z2 drivers and downloading a FTF FOR YOUR DEVICE... then folow this step
within your flashtool window click on the lightning icon at the top left
select flashmode
navigate to where you downloaded your FTF (OR put your FTF in your /flashtool/firmwares folder)
select your FTF
Flashtool should give you a prompt to plug in your device
hold volume down and plug in your device
step5
wait for it to finish flashing
step6
your device is now recovered, enjoy...
Sent from my D6503 using XDA Premium 4 mobile app
I bricked my phone doing this:
- root with eazyroot
- installed dual recovery
- full wipe
- install carbon + gapps
bum... bricked
i cant even see the Sony logo
Then i use the method mentioned by Envious_Data and my phone returned from hell
Good luck dude... hope u can fix that
carloscarvalho said:
I bricked my phone doing this:
- root with eazyroot
- installed dual recovery
- full wipe
- install carbon + gapps
bum... bricked
i cant even see the Sony logo
Then i use the method mentioned by Envious_Data and my phone returned from hell
Good luck dude... hope u can fix that
Click to expand...
Click to collapse
You didn't unlock your bootloader?
Isn't Carbon ROM AOSP?
If it is, it needs an unlocked bootloader or it will get bricked
Unbalanced said:
Okay, I'm not sure exactly what you'll need to know to help, so I'll just tell you what I think is important....
Current situation:
- If I boot the phone normally it freezes at the SONY screen and goes no further.
- If I attempt to boot into recovery mode, it loads the CWM screen (logo in the middle with instructions at bottom), but no actual menu or options. After about 5 seconds, this screen disappears, the phone reboots and then gets stuck on the SONY screen.
- If I connect the phone to the computer in Flashmode Flashtool recognizes it as being connected, but regardless of what I do, after about 2mins the phone reboots, loses connection with the computer, and freezes on the SONY screen as before mentioned.
- If I connect the phone to the computer normally while stuck on the SONY screen, the PC recognizes it though doesn't allow me to do anything to it, and Flashtool says I need to install drivers (I have installed every driver that comes with Flashtool).
How I got here:
- I've rooted the phone
- I've flashed Z2_DooMLoRD_AdvStkKernel_FW-438-v05
- I've unlocked the bootloader (via Flashtool)
- I've installed [Rom][Unofficial]Slim Rom 4.4.4 based on CM11.0, ROM for the Sony Xperia Z2
The phone was okay up until this point, however I wasn't happy with the ROM so I tried to reboot into recovery mode to wipe and install Carbon. This is when the trouble began.
Now it seems I can't do anything :/
Please help. This phone is literally 3 days and it looks like I've completely screwed it >.<
Thanks!
Click to expand...
Click to collapse
Okay I used to get into this kind of situation when I used HTC One, and what I did is try to flash recovery and unlocked bootloader again "using command".
And problem has solved. I think it is pretty much same for Xperia Z2, (ftf flashing method is not useful in this situation.)
I hope you know how to flash custom recovery using command. If not I think there is some thread that explains how to flash recovery and unlock the bootloader using command, if you can't find it plz let me know. Hope you have recovered phone next time I check this thread. Good luck mate :good:
HussainQ said:
You didn't unlock your bootloader?
Isn't Carbon ROM AOSP?
If it is, it needs an unlocked bootloader or it will get bricked
Click to expand...
Click to collapse
Yeah... I know... A newbie mistake...
I Just follow the instruction available in the site. And there is just "root and recovery"
No bootloader mentioned
But u r right... Thats the reason
Sent from my awesome Xperia Z2 using XDA Premium
@Envious_Data: Bro, thank you so much for that. I my z2 have only 1 day, and i god damn it bricket, that even screen wasn't working. So for other people who had bad luck: first I rooted using Community Rootkit, then unlocked bootloader, and at the end I flashed via fastboot boot.img which one i extracted from zip file from this thread - http://forum.xda-developers.com/showthread.php?t=2702001. Command prompt showed that it works. I rebooted phone sony logo showed up, but then disappeared, and then was crying and sorrow. Three years of rooting,flashing without any problem, and now that. Thank you one more time, that's a great lesson
I do have some advice for people
1. Try to find help threads for your device, i have one for Z2 that gives some useful info, ill be adding more soon
2. Once you have got the jist of flashing then try to expand on that, i do recomend roms first because its harder to brick from a rom than a kernel or a non stock based rom such as CM11 or AOSP
3. Always keep a stock flashable rom (kernel too if you have a unlocked bootloader) on your device
Sent from my D6503 using XDA Premium 4 mobile app
I too hard brick my Z2, only solution is the same as for Z1 http://forum.xda-developers.com/showthread.php?t=2646405
Sorry friend :`
discipuloosho said:
I too hard brick my Z2, only solution is the same as for Z1 http://forum.xda-developers.com/showthread.php?t=2646405
Sorry friend :`
Click to expand...
Click to collapse
A hard brick is by definition not recoverable by the user, requiring either special equipment ie jtag or RMA to fix.
I am quite surprised, and intrigued, at people flashing cm or AOSP on a two day old phone, was Sony experience that awful? You'd maybe be better served with a nexus device.
ghostofcain said:
A hard brick is by definition not recoverable by the user, requiring either special equipment ie jtag or RMA to fix.
I am quite surprised, and intrigued, at people flashing cm or AOSP on a two day old phone, was Sony experience that awful? You'd maybe be better served with a nexus device.
Click to expand...
Click to collapse
True friend, but I had an Xperia MT11i (Neo V) and all (fastboot, flashtool, CM, etc) was always no problem.
I've taken today for service (with CM11 (and cm kernel)) and see what happens ...
@Unbalanced I don't think your Z2 Hardbricked, if it were not ignite. Luck
Hi all, if it helps I did the same thing last night. Flashed CM11 without a recovery and wanted to revert back to my nandroid backup. I flashed doomloards kernal via fastboot. CWM started with no menu and just bootlooped. I then thought it may be a CWM issue, maybe no file structure or something. I flashed XZDuelKernal via fastboot and booted into CWM again and experienced the same issue. As this is a duel recovery, I then booted into TWRP. Recovery started and I was able to flash another zip then recover my nandroid backup. If you get this menu issue with CWM,try and flash a TWRP recovery and boot into that.
Also, as mentioned before, this is not a hard brick. It's just incompatible software and is easily fixed if you know what you are doing and prepared (nandroid backup, knowledge about fastboot and flashmode, ftf, recovery, unlocked bootloader).
Sent from my D6503 using Tapatalk
Stuck
Hi.
I believe (although I'm not sure) that I have bricked my Xperia Z2 in some way. When I press the 'power' button, the phone vibrates once and does nothing. I have tried to hold the 'power on' and 'volume up' buttons for a long time (half an hour with rubber bands), and nothing happens (as explained earlier in the thread).
I believe I am able to access the fastboot though, through 'Terminal' app on OSX. From there I can " ./fastboot devices " and get confirmation that they have loaded. I am also able to perform other tasks from here, such as flashing a recovery and " fastboot erase system -w " (which I believe may have got me to where I am now). I've been following things on this thread: http://forum.xda-developers.com/showthread.php?t=2277112
I have no experience in rooting or flashing, but attempted to flash a custom ROM because there were step by step instructions.
Anyway, I firstly used Sony's rooting procedure whereby an unlock code is generated etc. Eventually I gained access to the Recovery mode (via clockwork), and wiped the phone, installed the ROMAur zip and GApps zip. However, when I booted, it kept giving me warnings saying the apps were crashing. I've since gotten lost completely and need someone to help bail me out.
I'm hoping I can sort things out via the fastboot.
Thanks in advance for your help.
scoobard said:
Hi.
I believe (although I'm not sure) that I have bricked my Xperia Z2 in some way. When I press the 'power' button, the phone vibrates once and does nothing. I have tried to hold the 'power on' and 'volume up' buttons for a long time (half an hour with rubber bands), and nothing happens (as explained earlier in the thread).
I believe I am able to access the fastboot though, through 'Terminal' app on OSX. From there I can " ./fastboot devices " and get confirmation that they have loaded. I am also able to perform other tasks from here, such as flashing a recovery and " fastboot erase system -w " (which I believe may have got me to where I am now). I've been following things on this thread: http://forum.xda-developers.com/showthread.php?t=2277112
I have no experience in rooting or flashing, but attempted to flash a custom ROM because there were step by step instructions.
Anyway, I firstly used Sony's rooting procedure whereby an unlock code is generated etc. Eventually I gained access to the Recovery mode (via clockwork), and wiped the phone, installed the ROMAur zip and GApps zip. However, when I booted, it kept giving me warnings saying the apps were crashing. I've since gotten lost completely and need someone to help bail me out.
I'm hoping I can sort things out via the fastboot.
Thanks in advance for your help.
Click to expand...
Click to collapse
Download ftf file for your device and flash via flashtool.
mariosraptor said:
Download ftf file for your device and flash via flashtool.
Click to expand...
Click to collapse
Thanks for the quick reply Mario. I did just that (using Kuwait FFT for the D6503), and everything appears to be back to normal. Unfortunately I still have not got root access and can't remove the bloatware. As for the bricking issue however, it's solved. Thanks.
I was playing with dual recovery and thought I would try to flash CM11 (bad idea in hindsight locked bootloader). Long story short I have a SGP561 32GB Verizon model that will not boot. What it will do is boot stock recovery (worthless as far as I can see), go into fastboot the blue LED turns on not the screen. If I hit the power button it gives a weak vibrate and does nothing else. If I connect it to my PC the LED blinks and it vibrates a lot (I am guessing some kind of unauthorized software detected warning I seen something similar on my Galaxy S 3 when I unlocked it but Odin is easy). I know how to fix it the problem is all of the recovery packages I have found are for others models. If anyone could post a system dump for the SGP561 it would be very helpful. Or point me to a fastboot flashable recovery with instructions on how to do so. If you need more info just ask. Thanks.
Maxim512 said:
I was playing with dual recovery and thought I would try to flash CM11 (bad idea in hindsight locked bootloader). Long story short I have a SGP561 32GB Verizon model that will not boot. What it will do is boot stock recovery (worthless as far as I can see), go into fastboot the blue LED turns on not the screen. If I hit the power button it gives a weak vibrate and does nothing else. If I connect it to my PC the LED blinks and it vibrates a lot (I am guessing some kind of unauthorized software detected warning I seen something similar on my Galaxy S 3 when I unlocked it but Odin is easy). I know how to fix it the problem is all of the recovery packages I have found are for others models. If anyone could post a system dump for the SGP561 it would be very helpful. Or point me to a fastboot flashable recovery with instructions on how to do so. If you need more info just ask. Thanks.
Click to expand...
Click to collapse
Okay so I asked around and I found the Sony update service will let you get the firmware. I am back up and running.
Two things. Does ur tablet say it's rooted when u got it? Also where did u get the Sony updater? Thx
Sent from my HTC6525LVW using Tapatalk
I followed this guide:
https://forum.xda-developers.com/xperia-xa/how-to/f31xx-how-to-root-xperia-xa-noob-t3430170
With some specific files (boot and recovery images) from here:
https://forum.xda-developers.com/xa-ultra/how-to/how-to-root-xperia-xa-ultra-dual-t3439173
The rough steps that I took:
Put the UPDATE-SuperSU-v2.76-20160630161323.zip in the microsd
Unlocked the bootloader
"fastboot flash boot boot.img" and "fastboot flash recovery recovery.img"
Booted into TWRP
Since the internal data was shown as (0) , I Wiped the device.
Installed SuperSU-v2.76 from the microsd
Rebooted the device
It did an automatic reboot after going through the logos (I guess this part is expected after installing SuperSU)
After that, it gets stuck on the Xperia logo (the video logo keeps playing)
Now, after I turn on the device:
It goes through the Sony logo
It goes through the Android logo
It gets stuck on the Xperia logo (while playing the logo)
It doesn't get passed the Xperia logo.
Things I can still do:
I can boot into TWRP recovery (yay?)
I can use adb sideload with TWRP
I can't yet get back into fastbood mode, but I guess I can if I keep at it. I could go to fastbood mode before, but for some reason I can't anymore. I think it has to do with drivers. By default it recognizes the device as "SEMC flash drive" and will not recognize it as fastboot. After about a minute or so, it will disconnect the "SEMC flash drive" and boots the phone.
Give it to me straight, is my phone actually bricked?
If not, please let me know what I can do to fix it. It is very much appreciated to hear from anyone about this. Thank you all in advance.
If you need any additional info (logs, phone details, etc. etc.) feel free to ask me and I will happily comply.
If you can't get through the bootanimation, then yes that's kind of a soft brick. A solution would be to flash an official firmware from xperifirm (preferably .100 or .111 in order to to install root successfully) and then get everything done with simple baby steps. After flashing, you can wipe your data (if you wanna), reboot and then install root (I do not recommend flashing supersu and wiping at the same time when using an official firmware).
Note: Because we are stuck with only official fws, boot and recovery files can only work on specific fws
sexxualization said:
If you can't get through the bootanimation, then yes that's kind of a soft brick. A solution would be to flash an official firmware from xperifirm (preferably .100 or .111 in order to to install root successfully) and then get everything done with simple baby steps. After flashing, you can wipe your data (if you wanna), reboot and then install root (I do not recommend flashing supersu and wiping at the same time when using an official firmware).
Note: Because we are stuck with only official fws, boot and recovery files can only work on specific fws
Click to expand...
Click to collapse
Hey
Thanks for your reply on my cry for help.
So basically get the firmware from Xpeifirm, make sure boot is working fine (basically back to square one ... sorta), then root by installing the SuperSU again. right?
I had already looked at Xperifirm before this. but I couldn't figure out how to properly use it. and now I'm a bit stuck.
I followed these:
https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
https://www.youtube.com/watch?v=X_Y-BOWlQdw
But when I follow the steps, I get stuck here (when creating the bundle using the bundler in flash tools) :
http://imgur.com/a/wl3Cc
Any ideas on how to proceed?
Also another question. Can I get away with using adb sideloader instead of flashtool? some driver problems that are bugging me ...
Appreciate your response and thank you so much!
sony- android- xperia- off
good day! i hope im on the correct thread. i am having this issue on my xperia xa ultra dual.
everytime i turn the device on, it displays the sony logo, then the android logo, the xperia logo, then it turns off. i cant seem to get past through this regardless if i'll press the volume- and power or the volume+ and power. im almost certain that this can be fixed by doing something on the flashtool. i guess i just dont know how to do it. a step-by-step tutorial is greatly appreciated.
Can you get it into fash mode? If you can just flash ftf file for your phone.
Sent from my F3213 using xda premium
mchlbenner said:
Can you get it into fash mode? If you can just flash ftf file for your phone.
Sent from my F3213 using xda premium
Click to expand...
Click to collapse
hi. thanks for the response! i tried to flash the stock ftf for my f3212 and now it doesn't boot at all! T___T it will only show a steady red light if its connected to the PC.
Unfortunately this is a known issue when flashing after only red light when plug in for charging.
If you are under warranty send in for service their no known fix for this.
It happened to me I junk it.
And got another one.
Sent from my F3213 using xda premium
anyone can help me? I've tried to root my cherry mobile flare s play, I've flash twrp on it but it always boot in recovery it doesn't boot in system partition so I tried wiping the cache and dalvik cache, still doesn't boot so I tried flashing another recovery/rom and it just get worst it's now stuck in boot loop I've already tried the abd reboot-bootloader and always fall in error: device not found., I hope someone notice my case. thanks
Hello, this happens when the system is actually corrupted
you may reflash stock then twrp then root again
or just get a custom recovery for your device
you must go in bootloader for stock rom or twrp for custom rom, and that's fine your phone just needs a rom and its good to go
good luck
TheShadowMC said:
Hello, this happens when the system is actually corrupted
you may reflash stock then twrp then root again
or just get a custom recovery for your device
you must go in bootloader for stock rom or twrp for custom rom, and that's fine your phone just needs a rom and its good to go
good luck
Click to expand...
Click to collapse
but how can I boot it on bootloader? key combinations like vol+ and power or any combo doesn't work, only if someone can teach me how to boot it on bootloader or fastboot then there would be no problem for me, I don't know what to do now
Hello again, take out the bettery then put it back and use the bootloader combo
if it didnt work take out the bettery and flash through sp flash tool
nothing to worry about, i didnt notice that your phone can be flashed through sp flash, since it just requires the phone to be off
not really such a scary situation
TheShadowMC said:
Hello again, take out the bettery then put it back and use the bootloader combo
if it didnt work take out the bettery and flash through sp flash tool
nothing to worry about, i didnt notice that your phone can be flashed through sp flash, since it just requires the phone to be off
not really such a scary situation
Click to expand...
Click to collapse
will it work even if my device don't have battery on it?
kiltot24 said:
will it work even if my device don't have battery on it?
Click to expand...
Click to collapse
sp flash for my knowledge would work even when the battery is out it doesnt matter, just load the scatter press download button and connect the phone with battery off
good luck again:highfive:
-Hope- said:
sp flash for my knowledge would work even when the battery is out it doesnt matter, just load the scatter press download button and connect the phone with battery off
good luck again:highfive:
Click to expand...
Click to collapse
in my case I can't flash even a recovery image using sp flash tool. any help? sorry if I look like an ignorant any way thanks for your help guys, I really appreciate
no no problem, however what's the problem ?
I'm trying to flash a custom recovery on it but it doesn't work, I'm trying to flash twrp, the one I've flash before, because I don't have the stock rom of my device so I'm doing the process partially. I'm aiming to flash twrp and then restore my saved back up.
Hello,
i think your device stock frimware is there on google, however when you try to flash what error does it give or what happens ?
It doesn't show any error message and not showing any progress at all. my device just blink showing that the battery is charging though the battery is not present.
if it didnt detect it try pressing the volume up or volume down to make sure while connected ( and download button is pressed
just blink until it reaches time out.
I'm sure that my cable is working, it works on other device. I already install all the drivers I need.
is there a way to stop my device from simultaneous booting? it appears to be detected on device manager but just for a few sec, then reboot and appear again.
ensure the ROM is loaded properly in the flash tool.
Switch off the phone and remove battery.
press the start button in the flash tool to initiate the ROM flashing process. The process will be in hold, waiting for the phone to accept the new firmware.
Now connect the phone to computer.
Try these. Press and hold VOLUME DOWN OR VOLUME UP OR POWER+VOLUME UP OR POWER+VOLUME DOWN. One of these should work and the flashing process should start.
can I obtain the stock rom from the same device? I have the same model and it works properly. I can't download the stock rom from mediafire it always fail due to poor internet connection so I'm looking for another way.
I tried updating my driver then my device was recognized but when I flash the recovery image it displays 100% but in red color.
kiltot24 said:
I tried updating my driver then my device was recognized but when I flash the recovery image it displays 100% but in red color.
Click to expand...
Click to collapse
are you using the latest sp flash tool ?
yes thanks my device works fine now thank you for your help, the only problem now is how will I restore my device imei, it can be changed in engineer mode using at+ command but it be deleted again once conduct a factory reset in short it just set a temporary imei for my device, is there a way to change my device imei permanently?