I have a zenfone 2 720p (ze550ml) on cm13. I was upgrading to cm14.1, but a certain update kit reset my bootloader back to stock (it was unlocked), so i was stuck in a bootloop. Smh the phone was unrooted the whole time.
Anw, i planned to flash it with stock rom, unlock the bootloader, then flash cm14.1. Which is not a problem.
But then, mid-sideloading stock rom (at 10% progress) by twrp recovery, my phone ran out of battery!
Now, it doesnt start. At. All. It will vibrate when power button is long-pressed at times (most of the time, no), but NOT EVEN THE ASUS LOGO APPEARS!
What do i do.. there is no way booting up the phone, let alone entering bootloader or recovery mode.
Any pointers...??????
harry.lin said:
I have a zenfone 2 720p (ze550ml) on cm13. I was upgrading to cm14.1, but a certain update kit reset my bootloader back to stock (it was unlocked), so i was stuck in a bootloop. Smh the phone was unrooted the whole time.
Anw, i planned to flash it with stock rom, unlock the bootloader, then flash cm14.1. Which is not a problem.
But then, mid-sideloading stock rom (at 10% progress) by twrp recovery, my phone ran out of battery!
Now, it doesnt start. At. All. It will vibrate when power button is long-pressed at times (most of the time, no), but NOT EVEN THE ASUS LOGO APPEARS!
What do i do.. there is no way booting up the phone, let alone entering bootloader or recovery mode.
Any pointers...??????
Click to expand...
Click to collapse
Try following this guide: http://forum.xda-developers.com/showthread.php?t=3284256
Sent from my GT-S7580 using Tapatalk
DodoGTA said:
Try following this guide: http://forum.xda-developers.com/showthread.php?t=3284256
Click to expand...
Click to collapse
Thanks! This is what I was looking for. Should've surfed more and I would've arrived at that thread, this is embarrassing *laughs*. Anyway thanks again!
Related
I know how to put the boot loader into fastboot mode, power on while holding up. Problem is, I can't get it to load. It started after installing the SlickV6 Rom. Anyway, when I attempted to load the bootloader, the phone shows a black screen inof the fastboot usb text. Worst of all, rebooting the phone will only boot back to this black screen. I have to LGPNST back to stock just to get the phone to load.
Edit: Ok, LGPNST Again, rooted, unloacked, then tried to use Quick Boot to boot directly to recovery, and I get the exact same issue. It's almost as if the recovery is corrupted and it's not allowing me to load the booloader. Problem is, if I can't get into fastboot usb mode, or recovery, I can't flash a new recovery. This is awesome.
plaster said:
I know how to put the boot loader into fastboot mode, power on while holding up. Problem is, I can't get it to load. It started after installing the SlickV6 Rom. Anyway, when I attempted to load the bootloader, the phone shows a black screen inof the fastboot usb text. Worst of all, rebooting the phone will only boot back to this black screen. I have to LGPNST back to stock just to get the phone to load.
Edit: Ok, LGPNST Again, rooted, unloacked, then tried to use Quick Boot to boot directly to recovery, and I get the exact same issue. It's almost as if the recovery is corrupted and it's not allowing me to load the booloader. Problem is, if I can't get into fastboot usb mode, or recovery, I can't flash a new recovery. This is awesome.
Click to expand...
Click to collapse
Try redownloading Freegee and rerunning it. After the phone boots up download GooManager, hit menu, and then choose install openrecovery script. Once it downloads and installs, power down the device. Hold volume up + power until you see the LG logo and it goes black with text. Press volume down twice and then power. It should boot into TWRP recovery. Once you make sure it's working you can flash Sk8's CWM recovery, I you want too.
It's the black screen with text that won't load. If I don't unlock the bootloader the phone ignores the button commands. Once I unlock the bootloader, the phone will boot fine, until I attempt to load the bootloader. It just loads a black screen and sits there forever. The phone will never boot past this, even while forcing a reboot by holding power. I'll give your method a shot. Worst that can happen is another LGPNST.
EDIT: Nevermind the above. It's the act of unlocking the boot loader that's actually causing the phone to not boot. After typing the above response, I unlocked via freegee and rebooted, it shows the LG Logo, then just a black screen and it's stuck. Running LGPNST again. I have no idea what could have happened to the booatloader that would cause it to be unable to unlock without bricking my phone.
EDIT 2: Just tried the freegee.bat from the PC. Says the phone has been liberated, but does the exact same thing. I am stumped. I hope I don't have to wait for ATT to release an update so I can run something other than stock.
Sent from my LG-E970 using Tapatalk 2
Looking through the freegee thread, this seems to be a common problem with the newest freegee. Gonna try an older version and see if that's the issue. If not, guess I'm stuck with simple root until I have time to get on irc and see if anyone knows how to fix the corrupted partition.
What firmware u flashing back to with lgnpst? 10o or 11c
Sent from my LG-E970 using xda app-developers app
10o
Sent from my LG-E970 using Tapatalk 2
Root with korean root then 0.5 freegee u should be fine
Sent from my LG-E970 using xda app-developers app
You mean LGPNST with Korean firmware? Never saw Korean root.
Sent from my LG-E970 using Tapatalk 2
I'm at work now but send me a pm or get on irc this evening and we can fix this for ya
Sent from my LG-LS970 using xda app-developers app
Ok, will do. Thanks in advance.
BTW, iamtha1, I tried the Korean Root. It took, but I had the same issue. The only upside to this is that I'm still able to use the phone. It's the stock firmware, but it's not so bad once you freeze the excessive AT&T bloat.
I am having the same problem, my battery has been acting weird so i drained it completely, now it wont even boot past the black screen with blue text saying recovery. The power button wont do anything so i just have to hard reboot (power +volume up). It will just boot back into that same screen... I have the sprint version with zvb and not rooted or unlocked. please help
Salsathe4th said:
I am having the same problem, my battery has been acting weird so i drained it completely, now it wont even boot past the black screen with blue text saying recovery. The power button wont do anything so i just have to hard reboot (power +volume up). It will just boot back into that same screen... I have the sprint version with zvb and not rooted or unlocked. please help
Click to expand...
Click to collapse
Why are you posting here then? Go to the Sprint LGOG forum.
Hey folks, last night I followed this guide http://forum.xda-developers.com/showthread.php?t=2708194 to get a custom bootloader installed on my tablet. Unlocking the bootloader was a bit strange, but worked. I downloaded the bootloader for the SGP511 wifi-only model and installed it without issues. After that, I rebooted and was stuck in a boot loop. The device starts by displaying the logo, then turns black and vibrates periodically a couple of times, then reboots and does the same over and over again. I had the device plugged in allowed to run for at least 45 minutes to see if it would help, but to no avail.
I can access the custom recovery included in the bootloader just fine, but the OS doesn't seem to like the new bootloader. Anyone know of a solution?
serazaziel said:
Hey folks, last night I followed this guide http://forum.xda-developers.com/showthread.php?t=2708194 to get a custom bootloader installed on my tablet. Unlocking the bootloader was a bit strange, but worked. I downloaded the bootloader for the SGP511 wifi-only model and installed it without issues. After that, I rebooted and was stuck in a boot loop. The device starts by displaying the logo, then turns black and vibrates periodically a couple of times, then reboots and does the same over and over again. I had the device plugged in allowed to run for at least 45 minutes to see if it would help, but to no avail.
I can access the custom recovery included in the bootloader just fine, but the OS doesn't seem to like the new bootloader. Anyone know of a solution?
Click to expand...
Click to collapse
You didn't read properly.
You have the new .402 firmware on your device, and the custom kernel / recovery is only compatible with .36 and .55 firmwares. (Doomlord is working on a new version, so just wait a few days.)
Press Volume-Up + Power for a few seconds (device will vibrate 3 times or so) to hard-reset the device.
Then flash a FTF of the .402 firmware with the xda Flashtool (not the Sony Flashtool) to restore functionality.
That worked like a charm, thanks a million and sorry for not reading the instructions properly!
hasenbein1966 said:
You didn't read properly.
You have the new .402 firmware on your device, and the custom kernel / recovery is only compatible with .36 and .55 firmwares. (Doomlord is working on a new version, so just wait a few days.)
Press Volume-Up + Power for a few seconds (device will vibrate 3 times or so) to hard-reset the device.
Then flash a FTF of the .402 firmware with the xda Flashtool (not the Sony Flashtool) to restore functionality.
Click to expand...
Click to collapse
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 on my phone when suddenly it just booted off for no reason, weird right? So now it just stays on the "LG" boot up screen and now do anything. I've tried everything and done everything right (as far as I know) before I get into that let me tell you what my device can do as of now:
Devices DOES have fastboot oem unlock done
Phone was rooted as well and working perfectly (or so I thought until this happened)
ADB doesn't seem to work, but fastboot when connected to the computer does.
Ex: ADB devices (blank)
but fastboot devices (shows phone connected)
I've tried rebooting into recovery (Power + down) doesn't do anything, however, {Power + down} then finger off power then {Power + down} again takes me to "factory reset" option, if done so the phone just hangs and removing battery on way to take it back to fastboot on pc, or bootloop again.
I've done the following steps using [LG-H901] Stock .img Files (Boot, System, and Recovery)
Code:
fastboot flash system system.img
then
fastboot flash boot boot.img
and finally
fastboot flash recovery recovery.img
I've tried booting the phone and still gets me stuck on bootloop, and doing the same {Power + down} gets to the same "factory reset" option only then freezes my phone if I agree to do so.
Is there something I've done wrong or incorrect? I will provide as much info as requested.
Thanks guys!
Update: Phone booted up to lockscreen after finishing "Android is starting..." procedures, then kept bootlooping and it is now doing "Android is starting.." procedures again. I'll keep it updated if it keeps doing so or anything of the sort.
Did you reply YES when trying to enter recovery? It will ask 2 times and bith times answer YES ... And if you DO have TWRP installed it will boot into twrp recovery.
Double0EK said:
Did you reply YES when trying to enter recovery? It will ask 2 times and bith times answer YES ... And if you DO have TWRP installed it will boot into twrp recovery.
Click to expand...
Click to collapse
This is the weirdest thing, phone worked for a bit then shuts off and does the same thing. all files and everyhing was in tact. ANy main reason behind this? I am desperate not to delete everything because i have important photos on there that were still there when it re-started again right now.
So to recap: At the moment doing the {factory reset} got me as far as using phone for like 2 minutes before ****ting out and sending me on a bootloop yet again.
Important Questions:
On all my other devices I am able to connect via usb and read devices, but on this phone I get the message when connecting to my computer "LGE Android MTP Device: Failed" whats this about?
Is there any way to save internal photo album images other than getting this to boot up and pray it stays on long enough to transfer data?
UPDATE 2: Phone has booted up and not froze (yet)? Testing to see if it will keep working so far so good. Unfortunately all my **** was deleted which bummed me out, would have honestly prefered to lose a $600 phone than all the family, friend, ext photos I had on my phone I made the huge mistake of saving to internal memory and never backing up. Smh.
Update 3: Phone is back at it again with the bootloop. I have no idea what is wrong, I've repeated the steps twice and phone doesn't seem to let up. It's fine until I hit that restart or shutdown button then it goes into bootloop heaven. I'm guessing this phone is done for? On an unrelated note it did fall on me, but worked fine afterwards, it was just sudden when it started doing this. Unless anyone has more suggestions I'd be glad to hear them. As of right now, this phone is toast.
You tube how to bake phones in the oven.
It could fix some potentially loose solders..or since everything was already wiped you should get a warranty replacement.. Should still be under factory warranty.
Double0EK said:
You tube how to bake phones in the oven.
It could fix some potentially loose solders..or since everything was already wiped you should get a warranty replacement.. Should still be under factory warranty.
Click to expand...
Click to collapse
I am thinking the warranty route. Is there anything specific I should do before doing so? I hear having "fastboot oem unlock" {Bootloader Unlocked} voids the warranty. Is this true that you might know of? Either way thanks I appreciate the information.
Sorry so late..
But you can try to fastboot oem lock it.
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