Related
Hey, I've been following Cyanogen mods guide about flash_image to flash PSFmod onto my phone. I can use ADB to push files to my SD card and stuff, but when I follow this:
Code:
Temporarily allow app to run from the sdcard (use mount to find the correct device for your sdcard, ie: the /dev/block/BLAH part)
mount -o remount,exec /dev/block//vold/179:1 /sdcard
cd /sdcard
./flash_image recovery /sdcard/recovery.img
But I get this error:
Code:
error scanning partitions
Does anyone know how to fix it?
You get that error from which of those commands ?
From flash_image.
Whenever I run flash_image from my phone now, I get that partition error.
Is it because I'm on a Desire Z?
Beegee7730 said:
From flash_image.
Whenever I run flash_image from my phone now, I get that partition error.
Is it because I'm on a Desire Z?
Click to expand...
Click to collapse
Where did you get the flash_image utility from ? Was it from somewhere that has verified it to work on DZ ?
Dude u might brick ur phone lol ...try using Rom manager .....its safer
Sent from my HTC Vision using XDA App
I would use fastboot to flash a new recovery. You're sure what you're flashing is ok for the Vision, right ?
steviewevie said:
Where did you get the flash_image utility from ? Was it from somewhere that has verified it to work on DZ ?
Click to expand...
Click to collapse
I got it from the Cyanogen Mod Wiki, should I look for a different version?
theXeffect said:
Dude u might brick ur phone lol ...try using Rom manager .....its safer
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I would but the recovery I'm flashing isn't supported by Rom Manager.
steviewevie said:
I would use fastboot to flash a new recovery. You're sure what you're flashing is ok for the Vision, right ?
Click to expand...
Click to collapse
How do I use Fastboot? It should be okay for it, as it's the G2 version of Psfmod.
Beegee7730 said:
How do I use Fastboot? It should be okay for it, as it's the G2 version of Psfmod.
Click to expand...
Click to collapse
If you've got adb all setup via installing the SDK etc, then fastboot should work fine too. I think you need the engineering bootloader though.
Boot the phone into fastboot by holding down the trackpad button and holding the Power button, with the phone off. Or you can put it into hboot with Volume Down and Power and then select "Fastboot" from the menu.
It should then say "Fastboot" on the phone. With the USB cable plugged in that should say "Fastboot USB", and if you run "fastboot devices" on your PC it should show up your phone in the same way that "adb devices" normally would.
If that's all working you can run "fastboot flash recovery filename.img" to flash "filename.img" to recovery.
steviewevie said:
If you've got adb all setup via installing the SDK etc, then fastboot should work fine too. I think you need the engineering bootloader though.
Boot the phone into fastboot by holding down the trackpad button and holding the Power button, with the phone off. Or you can put it into hboot with Volume Down and Power and then select "Fastboot" from the menu.
It should then say "Fastboot" on the phone. With the USB cable plugged in that should say "Fastboot USB", and if you run "fastboot devices" on your PC it should show up your phone in the same way that "adb devices" normally would.
If that's all working you can run "fastboot flash recovery filename.img" to flash "filename.img" to recovery.
Click to expand...
Click to collapse
Wait a sec.
steviewevie said:
If you've got adb all setup via installing the SDK etc, then fastboot should work fine too. I think you need the engineering bootloader though.
Boot the phone into fastboot by holding down the trackpad button and holding the Power button, with the phone off. Or you can put it into hboot with Volume Down and Power and then select "Fastboot" from the menu.
It should then say "Fastboot" on the phone. With the USB cable plugged in that should say "Fastboot USB", and if you run "fastboot devices" on your PC it should show up your phone in the same way that "adb devices" normally would.
If that's all working you can run "fastboot flash recovery filename.img" to flash "filename.img" to recovery.
Click to expand...
Click to collapse
Tried few days ago with a kernel,but don`t works too.
You mean I need the eng hboot,then it should work,right?
Otherwise fastboot don`t work.
C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (4214 KB)... OKAY [ 0.891s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.891s
C:\android-sdk-windows\tools>
Beegee7730 said:
C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (4214 KB)... OKAY [ 0.891s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.891s
C:\android-sdk-windows\tools>
Click to expand...
Click to collapse
You haven't got S-OFF. You need S-OFF to flash a custom recovery.
I do have S-Off, I followed this and when I boot into fastboot it says "S-OFF" in green text at the top.
Beegee7730 said:
I do have S-Off, I followed this and when I boot into fastboot it says "S-OFF" in green text at the top.
Click to expand...
Click to collapse
ok, do you have the engineering bootloader ? Does it say "SHIP" or "ENG" at the top.
steviewevie said:
ok, do you have the engineering bootloader ? Does it say "SHIP" or "ENG" at the top.
Click to expand...
Click to collapse
SHIP.
I assume I need to reflash it with the engineering one?
Beegee7730 said:
SHIP.
I assume I need to reflash it with the engineering one?
Click to expand...
Click to collapse
Yeah I think you need the engineering bootloader for fastboot to work fully. I didn't think you'd get that sort of error for no eng bootloader though.
steviewevie said:
Yeah I think you need the engineering bootloader for fastboot to work fully. I didn't think you'd get that sort of error for no eng bootloader though.
Click to expand...
Click to collapse
Code:
C:\android-sdk-windows\tools>adb push hboot-eng.img /data/local
1598 KB/s (0 bytes in 1048576.000s)
Is that supposed to happen?
Beegee7730 said:
Code:
C:\android-sdk-windows\tools>adb push hboot-eng.img /data/local
1598 KB/s (0 bytes in 1048576.000s)
Is that supposed to happen?
Click to expand...
Click to collapse
Did it work and is the file there in /data/local now ?
Do a checksum on the eng hboot before you flash it, as per the guides, to make sure it's not corrupted.
steviewevie said:
Did it work and is the file there in /data/local now ?
Do a checksum on the eng hboot before you flash it, as per the guides, to make sure it's not corrupted.
Click to expand...
Click to collapse
Ah, managed to flash it.
Will test and report back when done.
EDIT:
It works!
Thanks alot!
steviewevie said:
Yeah I think you need the engineering bootloader for fastboot to work fully. I didn't think you'd get that sort of error for no eng bootloader though.
Click to expand...
Click to collapse
I think too,the same with my HTC Hero.
Fastboot wont work without engineering bootloader/hboot!
So the same at Desire Z.
Hello,
I wanted to update one SE Arc Experia already running cm7, but with a few months old Rom.
fastboot is not detecting my device, and I have no ideas why. After a few hours of search, I am still unable to fastboot it.
Arc is running fine with cm7.2.0 with FXP Kernel, debug is ON.
I am on Ubuntu 11.10, and everything is correctly set up. I already flashed Rom & Kernel in the past. The file 51-android.rules is in /etc/udev/rules.d.
Code:
#SE Arc Xperia
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”0fce″, ATTRS{idProduct}==”014f″, OWNER:="gabx", GROUP:="plugdev", MODE=”0666″
the usb is working :
Code:
[email protected]:~/Xperia/xperia$ lsusb
Bus 001 Device 005: ID 0fce:0dde Sony Ericsson Mobile Communications AB
fastboot executable is in my box, with correct permission. The fastboot command works.
The phone is correctly in download mode, with the blue led (turn off, press menu, plug USB).
When I fastboot devices, I have no entry :
Code:
[email protected]:~/Xperia/xperia$ fastboot devices
[email protected]:~/Xperia/xperia$
Weird, the -i 0x0fce option doesn't seems correct:
Code:
[email protected]:~/Xperia/xperia$ fastboot -i 0x0fce devices
usage: fastboot [ <option> ] <command>
.../.... list here of all otions and command
Sudoing doesn't change anything.
Code:
[email protected]:~/Xperia/xperia$ fastboot reboot
< waiting for device >
The device is not detected. Why ??
TY for any help
EDIT
As I couldn't fastboot my device, I placed the boot.img from cm7 update on my sdcard. then from terminal emulator on my device:
Code:
flash_image boot /sdcard/boot.img
Then reboot in recovery, but now black screen, can't boot at all!!
gabx said:
The device is not detected. Why ??
TY for any help
Click to expand...
Click to collapse
Funny how I lost a whole day investigating the same issue Answer: invalid fastboot binary. Use this one
gabx said:
As I couldn't fastboot my device, I placed the boot.img from cm7 update on my sdcard. then from terminal emulator on my device:
Code:
flash_image boot /sdcard/boot.img
Then reboot in recovery, but now black screen, can't boot at all!!
Click to expand...
Click to collapse
Don't use flash_image, it doesn't work with Xperias
Cheers,
z
zdzihu said:
Funny how I lost a whole day investigating the same issue Answer: invalid fastboot binary. Use this one
Don't use flash_image, it doesn't work with Xperias
Cheers,
z
Click to expand...
Click to collapse
TY so much. Yes, a lot of wasting time, checking everything on my Linux box!! Your answer is nice to me, as I was doubting about my Linux set up, and now I feel safe.
I managed to settle everything today on a Winodows box, in just 15 mn! Fastbooted boot.img, flashed update from sdcard, et hop!
TY for the binary. I will use it next time on my Linux box.
fastboot -i 0x0fce devices
Click to expand...
Click to collapse
shouldnt it be
Code:
fastboot -i 0xfce devices
instead?
try running
Code:
fastboot -i 0x0fce
.
You might also require running it as root. At least that's what i'm forced to do everytime, i guess it has sth to do with the udev entry but not sure what.
Also running as root means i'm not able to use tools like FlashTool, but if you just need fastboot, it will probably work.
Cheers,
G
g el said:
try running
Code:
fastboot -i 0x0fce
.
You might also require running it as root. At least that's what i'm forced to do everytime, i guess it has sth to do with the udev entry but not sure what.
Also running as root means i'm not able to use tools like FlashTool, but if you just need fastboot, it will probably work.
Cheers,
G
Click to expand...
Click to collapse
You need to add the udev rule mentioned in OP and it will work for regular users too.
Code:
#SE Arc Xperia
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”0fce″, ATTRS{idProduct}==”014f″, OWNER:="yourusernamehere", GROUP:="plugdev", MODE=”0666″
Also, I don't use 'fastboot -i 0x0fce' (just fastboot <command>) and it still works fine
Cheers,
z
zdzihu said:
You need to add the udev rule mentioned in OP and it will work for regular users too.
Code:
#SE Arc Xperia
SUBSYSTEMS==”usb”, ATTRS{idVendor}==”0fce″, ATTRS{idProduct}==”014f″, OWNER:="yourusernamehere", GROUP:="plugdev", MODE=”0666″
Also, I don't use 'fastboot -i 0x0fce' (just fastboot <command>) and it still works fine
Cheers,
z
Click to expand...
Click to collapse
Agree totally, no need sudoing, neither use option. As previoulsy mentioned, a wrong binary was the only culprit. Usually, fastboot is trivial in Linux, with the only condition being the correct android rules in /etc/udev.
I cant flash everything on fastboot mode
i have usb enabled and bootloader unlocked latest
status: Bootloop, no recovery
only fastboot mode
help for a fix ... I bricked the tab
TRIED TO RETURN TO STOCK WITH FLASH ALL.BAT BUT ALL PARTITIONS END WITH UNKNOWN COMMAND
help i paid 700 $ for this tab ... i can reboot anduse fastboot mode... bootloader unlocked
Alessandro999 said:
help i paid 700 $ for this tab ... i can reboot anduse fastboot mode... bootloader unlocked
Click to expand...
Click to collapse
Are you using the latest FASTBOOT.exe?
Can you screenshot the CMD?
unknown commands usually indicate an error in the command not the execution of the command.
parakleet said:
Are you using the latest FASTBOOT.exe?
Can you screenshot the CMD?
unknown commands usually indicate an error in the command not the execution of the command.
Click to expand...
Click to collapse
i have fixed!!! just relock the bootloader... waiting for delete and erasing.... unlock the bbotloader and waiting for esasing
now can flash all i want
Alessandro999 said:
i have fixed!!! just relock the bootloader... waiting for delete and erasing.... unlock the bbotloader and waiting for esasing
now can flash all i want
Click to expand...
Click to collapse
Good job
I was trying to flash LineageOS but didn't work. I then attempted to fix my mistake. My attempts only made the problem worse as now I can only use fastboot. There is no recovery or OS.
I do have the latest ADB and Fastboot drivers on my computer.
I have unlocked the bootloader.
Code:
fastboot oem unlock
...
FAILED (remote: Device already unlocked)
When I flash the factory image, I get this message:
Code:
writing 'bootloader'...
FAILED (remote:unsupported command)
This happens when I try to flash the other images found in the factory images file from Google individually. This also happens when I try to flash the latest TWRP recovery image.
The following commands also return a "remote: unsupported command" error:
Code:
fastboot erase [partition]
fastboot format [partition]
I have also locked and reunlocked the bootloader but doing this does not change anything when flashing again.
When the bootloader is locked and I return to the screen after pressing lock and volume down, there is a red box that reads:
Code:
OS on your tablet is damaged. Needs recovery.
This goes away when unlocking again.
I have tried Unified Android Toolkit but have run into the same "remote: unsupported command" response.
This highlights all my attempts to fix my tablet. Thanks for reading up to this point.
I've seen suggestions to use fwtool but I can't wrap my head around how to use it. If that is the only way to fix my tablet, can someone show me how to use it to solve my problem? Keep in mind I can only use fastboot. No recovery or OS.
Is there a flashall file in the image from Google?
sabrdawg said:
Is there a flashall file in the image from Google?
Click to expand...
Click to collapse
Yes. When I run it, get into the same message.
Code:
writing 'bootloader'
FAILED (remote: unsupported command)
I was just reading about someone else who had a similar issue, and it was recommended for them to update their ADB and fastboot. Hope this helps!
viii_xvi said:
I was trying to flash LineageOS but didn't work. I then attempted to fix my mistake. My attempts only made the problem worse as now I can only use fastboot. There is no recovery or OS.
I do have the latest ADB and Fastboot drivers on my computer.
I have unlocked the bootloader.
Code:
fastboot oem unlock
...
FAILED (remote: Device already unlocked)
When I flash the factory image, I get this message:
Code:
writing 'bootloader'...
FAILED (remote:unsupported command)
This happens when I try to flash the other images found in the factory images file from Google individually. This also happens when I try to flash the latest TWRP recovery image.
The following commands also return a "remote: unsupported command" error:
Code:
fastboot erase [partition]
fastboot format [partition]
I have also locked and reunlocked the bootloader but doing this does not change anything when flashing again.
When the bootloader is locked and I return to the screen after pressing lock and volume down, there is a red box that reads:
Code:
OS on your tablet is damaged. Needs recovery.
This goes away when unlocking again.
I have tried Unified Android Toolkit but have run into the same "remote: unsupported command" response.
This highlights all my attempts to fix my tablet. Thanks for reading up to this point.
I've seen suggestions to use fwtool but I can't wrap my head around how to use it. If that is the only way to fix my tablet, can someone show me how to use it to solve my problem? Keep in mind I can only use fastboot. No recovery or OS.
Click to expand...
Click to collapse
Hi, did you tried to lock fastboot then unlock it again. Try also to change the bootloader or the kernel with fastboot or boot directly twrp without installing it
rhmanoa said:
Hi, did you tried to lock fastboot then unlock it again. Try also to change the bootloader or the kernel with fastboot
Click to expand...
Click to collapse
I have locked and unlocked the bootloader. I have also flashed bootloader and kernel images from the factory images and I get the same "Remote: unsupported command" message.
rhmanoa said:
Boot directly twrp without installing it.
Click to expand...
Click to collapse
I don't think I understand this. By "twrp" you mean boot straight into recovery mode, I can't. Every time I try to, I am stuck on the Google screen. I left it on that for an hour with no change.
sabrdawg said:
I was just reading about someone else who had a similar issue, and it was recommended for them to update their ADB and fastboot. Hope this helps!
Click to expand...
Click to collapse
Can you direct me to where to download the latest drivers? You look like you're more familiar with this than I am and me being new to using fastboot, I may have gotten an older version.
This should help
https://developer.android.com/studio/run/win-usb.html
sabrdawg said:
This should help
https://developer.android.com/studio/run/win-usb.html
Click to expand...
Click to collapse
It appears I have the latest drivers. To make sure nothing's changed, I flashed the factory image again and it gives the same response as before.
viii_xvi said:
I don't think I understand this. By "twrp" you mean boot straight into recovery mode, I can't. Every time I try to, I am stuck on the Google screen. I left it on that for an hour with no change.
Click to expand...
Click to collapse
fastboot boot twrp-3.1.1-1-dragon.img
Vartom said:
fastboot boot twrp-3.1.1-1-dragon.img
Click to expand...
Click to collapse
I am greeted with "remote: image verification failed".
viii_xvi said:
I am greeted with "remote: image verification failed".
Click to expand...
Click to collapse
Is the boot loader unlocked before this command is executed?
Vartom said:
Is the boot loader unlocked before this command is executed?
Click to expand...
Click to collapse
Yes, it was unlocked. I tried relocking, reunlocking, and executing the same command but it still gave me the same message.
I got exactly the same problem. Any solution for this?
Bolemichel said:
I got exactly the same problem. Any solution for this?
Click to expand...
Click to collapse
I've read relocking and unlocking the bootloader fixes it so that you can flash through fastboot. This didn't work for me, unfortunately , and haven't been able to fix my Pixel C.
Are you sure you no recovery? I was not able to fix my tablet because I foolishly deleted my recovery and was stuck in dev mode but unable to flash anything. As long as you have a recovery, you can fix it. I don't remember exactly how but you'll be able to find it.
viii_xvi said:
I've read relocking and unlocking the bootloader fixes it so that you can flash through fastboot. This didn't work for me, unfortunately , and haven't been able to fix my Pixel C.
Are you sure you no recovery? I was not able to fix my tablet because I foolishly deleted my recovery and was stuck in dev mode but unable to flash anything. As long as you have a recovery, you can fix it. I don't remember exactly how but you'll be able to find it.
Click to expand...
Click to collapse
lock/relock has no effect. Unfortunatelly recovery is broken, tab will reboot when I try to enter recovery.
I'm in contact with google and try to get a new unit now
I also have the same problem and I am so disappointed that I cannot figure it out....#pls forgive my poor English#who can help me ..it is same to me that I have no idea to use so called"fwtool"tool.
Guys I have been trying to fix this for the past week and found these two posts.
[RECOVERY][TWRP][dragon]
April 1, 2017 .. and it's not an April Fools' Day Joke --> TWRP for Pixel C is official now ! https://twrp.me/google/googlepixelc.html I would like to continue this thread for publishing test builds and other troubleshooting. Once the changes...
forum.xda-developers.com
XCEED :: [KERNEL] :: [AOSP/Stock/PureNexus] :: [v9.xx / Android 7.1.2]
Exceed the limitations /// XCEED kernel Only for Pixel C If this technology provides value to you a donation for the time spent creating it is very welcome! NOTE: The screenshots are actual screenshots from my Pixel C, though your...
forum.xda-developers.com
It explains how to use fwtool, it's actually pretty straightforward. The second link above has the download link for fwtool. Once you download it, start your pixel in fastboot mode while connected to your laptop. In the command line:
Code:
adb push <path to fwtool>/fwtool /sdcard/Download/fwtool
You should get a message like this below:
fwtool: 1 file pushed, 0 skipped. 4.7 MB/s (43880 bytes in 0.009s)
Then open the shell in adb using:
Code:
adb shell
then go to your download directory and check the dev_boot_fastboot_full_cap flag using the commands below:
Code:
cd /sdcard/Download/
fwtool vbnv read dev_boot_fastboot_full_cap
The output for me was:
Code:
127|dragon:/ # cd /sdcard/Download/
dragon:/sdcard/Download # fwtool vbnv read dev_boot_fastboot_full_cap
Firmware debug Tool
dev_boot_fastboot_full_cap = 0
I then set the flag to 1 using fwtool as below.
Code:
fwtool vbnv write dev_boot_fastboot_full_cap 1
After running this, check the flag again using fwtool vbnv read dev_boot_fastboot_full_cap again. It should now display 1. After doing this, I was able flash using fastboot
I hope this helps everyone and good luck...
Evren Tekin said:
Guys I have been trying to fix this for the past week and found these two posts.
[RECOVERY][TWRP][dragon]
April 1, 2017 .. and it's not an April Fools' Day Joke --> TWRP for Pixel C is official now ! https://twrp.me/google/googlepixelc.html I would like to continue this thread for publishing test builds and other troubleshooting. Once the changes...
forum.xda-developers.com
XCEED :: [KERNEL] :: [AOSP/Stock/PureNexus] :: [v9.xx / Android 7.1.2]
Exceed the limitations /// XCEED kernel Only for Pixel C If this technology provides value to you a donation for the time spent creating it is very welcome! NOTE: The screenshots are actual screenshots from my Pixel C, though your...
forum.xda-developers.com
It explains how to use fwtool, it's actually pretty straightforward. The second link above has the download link for fwtool. Once you download it, start your pixel in fastboot mode while connected to your laptop. In the command line:
Code:
adb push <path to fwtool>/fwtool /sdcard/Download/fwtool
You should get a message like this below:
fwtool: 1 file pushed, 0 skipped. 4.7 MB/s (43880 bytes in 0.009s)
Then open the shell in adb using:
Code:
adb shell
then go to your download directory and check the dev_boot_fastboot_full_cap flag using the commands below:
Code:
cd /sdcard/Download/
fwtool vbnv read dev_boot_fastboot_full_cap
The output for me was:
Code:
127|dragon:/ # cd /sdcard/Download/
dragon:/sdcard/Download # fwtool vbnv read dev_boot_fastboot_full_cap
Firmware debug Tool
dev_boot_fastboot_full_cap = 0
I then set the flag to 1 using fwtool as below.
Code:
fwtool vbnv write dev_boot_fastboot_full_cap 1
After running this, check the flag again using fwtool vbnv read dev_boot_fastboot_full_cap again. It should now display 1. After doing this, I was able flash using fastboot
I hope this helps everyone and good luck...
Click to expand...
Click to collapse
Yes, but no adb without recovery
Hi,
I want to install TWRP so I can Install nAOSP ROM 8.1 for Xperia S on my phone.
The phone's bootloader is unlocked and the phone is rooted. I downloaded the correct version of TWRP from here (nozomi).
I tried installing via ADB (I followed the instructions here), but the command:
Code:
fastboot flash recovery twrp-3.2.3-nozomi.img
Fails with:
Code:
Sending 'recovery' (12964 KB)
(bootloader) USB download speed was 33272kB/s
OKAY [ 0.415s]
Writing 'recovery'
(bootloader) Flash of partition 'recovery' requested
FAILED (remote: 'Partition not found')
Finished. Total time: 0.437s
I understand that this is because Sony phones don't have separate recovery partition, and that their recovery is incorporated to the boot.img (see here).
I then tried using the dd install method as described on the project's homepage.
Code:
$ ./adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p11
25929+1 records in
25929+1 records out
13275872 bytes transferred in 3.747 secs (3543066 bytes/sec)
Although this seems to work (i.e. I don't get an error message), I cannot, try what I might, make the phone boot into recovery.
Can anyone tell me what I'm missing?
Just for anyone that comes across this post, I ended up solving my problem by flashing TWRP to boot.
Don't know if this is recommended or not, but it worked like a charm. I am now running nAOSP ROM 8.1 on my Xperia S.
_jack said:
Just for anyone that comes across this post, I ended up solving my problem by flashing TWRP to boot.
Don't know if this is recommended or not, but it worked like a charm. I am now running nAOSP ROM 8.1 on my Xperia S.
Click to expand...
Click to collapse
How exactly did u do that...i have spent over a week trying to do it.
sweetbanana said:
How exactly did u do that...i have spent over a week trying to do it.
Click to expand...
Click to collapse
Just replace "recovery" with "boot".
Code:
sudo fastboot flash boot twrp-3.2.3-nozomi.img
_jack said:
Just replace "recovery" with "boot".
Code:
sudo fastboot flash boot twrp-3.2.3-nozomi.img
Click to expand...
Click to collapse
I did that to my Xperia S and it worked too, but after i reboot to system. It just puts me to Cyanogen recovery and idk how I have Cynaogen recovery but its there. And its just stuck there, and wouldnt let me boot to Android. The recovery mode for cyanogenmod is the only thing thats there. I flashed twrp to boot (when i was at the twrp fastboot) and it didnt anything at all. Which made my xperia bricked. I had to reflash the firmware 3 times to troubleshoot the problem.
ZebastianJV said:
I did that to my Xperia S and it worked too, but after i reboot to system. It just puts me to Cyanogen recovery and idk how I have Cynaogen recovery but its there. And its just stuck there, and wouldnt let me boot to Android. The recovery mode for cyanogenmod is the only thing thats there. I flashed twrp to boot (when i was at the twrp fastboot) and it didnt anything at all. Which made my xperia bricked. I had to reflash the firmware 3 times to troubleshoot the problem.
Click to expand...
Click to collapse
Try flashtool to install twrp. twrp link: https://androidfilehost.com/?fid=1322778262904003720
Thx, i hope this works. Cause again, i dont like to keep reflashing the firmware cause its broken when i have the recovery.
ZebastianJV said:
Thx, i hope this works. Cause again, i dont like to keep reflashing the firmware cause its broken when i have the recovery.
Click to expand...
Click to collapse
No, it won't be a problem.
ZebastianJV said:
Thx, i hope this works. Cause again, i dont like to keep reflashing the firmware cause its broken when i have the recovery.
Click to expand...
Click to collapse
i had the same issue i just flashed the firmware boot.img with flashtools 0.9.8.0
Extract with 7zip/winrar/winzip. Use this kernel via flashtool. has recovery. note for unlocked bootloaders only