I was trying to use xposed framework and I rebooted to install it and now my phone is stuck in a bootloop. I rooted it and it had the latest firmware. I can get into twrp. I tried using flashtool but the phone disconnects while flashtool is preparig files to be flashed. I tried repairing with sony pc companion but it says no software is available for my phone after it detects it in flash mode.
thanks for any help
Extract System.sin and Kernel.sin files from Firmware ftf file and try to flash it using fastboot method.
Ok! I am stuck at the sony logo then a screen appears saying that something went wrong while i was updating the device.
all I did was flash a wrong recovery image for my old phone & then this happened
what I tried:
1. tried to update from the flash tool (didn't work)
2. tried the sony PC companion & it didn't work either, it either says that I have modified software that can't be updated or says that my system doesn't have any updates
my phone is ZR C5502, bootloader was unlocked when I flashed the wrong recovery image.
Please help me I need the phone to work
Thanks in Advance
Teeeee said:
Ok! I am stuck at the sony logo then a screen appears saying that something went wrong while i was updating the device.
all I did was flash a wrong recovery image for my old phone & then this happened
what I tried:
1. tried to update from the flash tool (didn't work)
2. tried the sony PC companion & it didn't work either, it either says that I have modified software that can't be updated or says that my system doesn't have any updates
my phone is ZR C5502, bootloader was unlocked when I flashed the wrong recovery image.
Please help me I need the phone to work
Thanks in Advance
Click to expand...
Click to collapse
Did you take the backup of DRM keys and TA partition while unlocking bootloader? Sony PC comp does not support unlocked phones. you will have to restore the DRM keys and TA partition.
If you have lost both of these, then flash custom kernel and stock or AOSP based ROM using flashtool. search in forums for more info
Thank You!
I Had the Backup & tried Relocking the Bootloader but the PC companion couldn't help me, anyway, I flashed a flash custom kernel and stock ROM using flashtool, thank you so much :good:
I rooted my K3 note using Kingroot and everything was fine but I then replaced it with SuperSU and that worked. Once everything was done with SuperSU it said to update binary. I update via normal way then reboot and the reboot has me on the boot loader .I removed the battery and tried to leave it off then reboot and it didn't work. I tried to factory reset using the recovery mode and even that didn't work. Please help.
You need to flash stock ROM which includes the stock recovery via SPF tool.
Flash rom via flashtool
http://forum.xda-developers.com/k3-note/general/organized-thread-lenovo-k3-note-k50-t3158522
Hello everybody,
I rooted my Xperia Z1 about 8 months ago in order to install the 5.1.1 update which didn't roll out for my device probably because it was a global version (5.0.1 was the last OTA). I did a clean install with no problems, flashed DualRecovery, SuperSu, and BusyBox was working just fine. Everything was working perfectly.
About 3 months ago, I tried updating BusyBox, only to tell that the update failed (couldn't install in the path it used to be try changing the path), I read and read, and found that the solution was to delete a certain file from root that prevented me from modifying certain folders and their content(even with root access), and then do a clean install in a different path than the former one. However, I couldn't gain root access to my files, no root explorer worked! It bugged me, but I was busy at that time, so I couldn't resolve it.
Few weeks later I tried rebooting into recovery, but no method worked, no apps, no key combination, no adb, nothing at all worked! After 2 hard days I managed to install TWRP recovery using NUTS recovery project. I rebooted several times, and it was still working. I then installed BusyBox with no problems, and everything was back to perfect. Later I decided to install CM 12.1 because I always used on my Samsung Galaxy Nexus and I always loved it. So using my now working recovery, I backed everything up on a USB and then flashed CM 12.1 WITHOUT its recovery along with a GAPPS package.
CM was installed, which then rebooted into its recovery and tried to install the GAPPS package. The GAPPS installation was a fail. CM recovery asked me to try using TWRP to do such installation ( go figure! ); in fact, CM recovery couldn't flash anything besides another CM 12.1 update. After this point I wasn't able in any possible way to enter TWRP nor install it. Even if I want to flash using fastboot I couln't! adb reads my device just fine, and can use it to reboot into flashmode, which doesn't seem to be functioning properly. The blue light turns on but there isn't a thing on the screen, fastboot can't recognize is it and hence I can't flash anything using fastboot.
Should I reflash partitions if this could be done on Z1? ( I did it before on my Nexus ) Can I use Odin? I even doubt I can enter download mode on my phone
Any help would be much appreciated.
Thanks in advance!
Anyone?
No?
Ok! :sad:
Is your bootloader unlocked? To run cm on our z1 you need an unlocked bootloader because cm needs a custom kernel.
You can try Sony companion app or androxydes flashtool in combination with a pre-rooted ftf to reach stock again.
The thing is even Sony flashtool (Emma) is not reading my phone, it detects a device in the USB port, but not the device!
I managed to install TWRP using TWRP Manager app that I downloaded from APKmirror website. I installed GApps and it is working fine right now.
TWRP Manager said that I should have a FOTA recovery or something like that, and if I don't have one then I am installing the recovery on my responsibility.
Still no bootloader or flash mode. Neither Emma nor Odin are identifying the phone. Although my phone lights blue, but the screen shows nothing!
Mohdhamm said:
The thing is even Sony flashtool (Emma) is not reading my phone, it detects a device in the USB port, but not the device!
Still no bootloader or flash mode. Neither Emma nor Odin are identifying the phone. Although my phone lights blue, but the screen shows nothing!
Click to expand...
Click to collapse
AFAIK, Emma hasn't been updated for a LONG time. It will remain defunct with no updates and no support. Use flashtool from androxyde if you want to continue using Sony's stock ROM.
No bootloader or flash mode detection: That usually means the drivers that interfaces with your phone is missing. Search around XDA for the correct fastboot and adb drivers for your PC's OS.
My approach for fixing your issue: Find the right drivers and put a stable Lollipop ROM on your sdcard. If you have fastboot working (make sure you have unlocked bootloader), flash boot image from the Lollipop zip and flash the recovery image found in some Lollipop threads. If everything goes well, your phone will bootloop, but you'll have working recovery. Press Vol Down when the Sony Logo appears on screen to enter TWRP. Since you saved a backup of your phone elsewhere, erase all the partitions (minus sdcard), format them to ext4, and flash the Lollipop ROM from your sdcard.
i was having kingroot as my superuser so i was installing supersu by terminal emulator and when i restarted my phone it just shows sony and xperia logo and then it again restarts and doesn't swicth ons.
after this i was installing the stock rom using the flash tool but the flash tool is showing "ERROR- root: this bundle is not valid"
i changed the rom version but still its happening. i also followed this link http://forum.xda-developers.com/xperia-z/help/flashtool-bundle-valid-identify-device-t3257879http:// of xda but its still happening......:crying::crying::crying:
Same here.
When open Flash Tools this message appears. Without phone connected.
Already removed and re-installed Flash Tools and Drivers... Still Nothing.
I have the same problem as well please help me !
Nothing to care about, says Androxyde.
http://forum.xda-developers.com/showpost.php?p=66286134&postcount=3116