Hey guys.
SGP312 model here, unlocked bootloader.
not sure what i did wrong here - i got to Fastboot mode and the blue light is on, when i run "Fastboot devices" i get the device name.
so i followed the explanation here: https://forum.xda-developers.com/xp...pment/ub-twrp-v3-2-1-xperia-tablet-z-t3735110
and did: "fastboot flash boot twrp-3.2.1-0-pollux_windy.img"
however, now my phone won't boot, and when i type "adb reboot recovery" i get "error: device not found" (even thought "Fastboot devices" gives me a response")
i tried fixing it with Flashtool, and everything works well until i get to "Wait for Flashmode" and im instructed to "unplug, power off, pres vol down, plug in USB cable" - this simply doesn't do anything =X
so.... how do i get out of this? all i want to do is install one of the newer roms from the forum (either Marshmallow or Oreo)
can anyone help me get out of this issue i've gotten myself into?
Caniv said:
Hey guys.
SGP312 model here, unlocked bootloader.
not sure what i did wrong here - i got to Fastboot mode and the blue light is on, when i run "Fastboot devices" i get the device name.
so i followed the explanation here: https://forum.xda-developers.com/xp...pment/ub-twrp-v3-2-1-xperia-tablet-z-t3735110
and did: "fastboot flash boot twrp-3.2.1-0-pollux_windy.img"
however, now my phone won't boot, and when i type "adb reboot recovery" i get "error: device not found" (even thought "Fastboot devices" gives me a response")
i tried fixing it with Flashtool, and everything works well until i get to "Wait for Flashmode" and im instructed to "unplug, power off, pres vol down, plug in USB cable" - this simply doesn't do anything =X
so.... how do i get out of this? all i want to do is install one of the newer roms from the forum (either Marshmallow or Oreo)
can anyone help me get out of this issue i've gotten myself into?
Click to expand...
Click to collapse
you flashed recovery to boot. So only recovery exists in boot section.
Of course tablet won't boot afterwards, as there is not kernel.
Download custom rom you want to install, unpack boot.img from roms zip files and flash via "fastboot flash boot boot.img"
Afterwards enter recovery and flash custom rom zip, gapps or whatever you need.
Rootk1t said:
you flashed recovery to boot. So only recovery exists in boot section.
Of course tablet won't boot afterwards, as there is not kernel.
Download custom rom you want to install, unpack boot.img from roms zip files and flash via "fastboot flash boot boot.img"
Afterwards enter recovery and flash custom rom zip, gapps or whatever you need.
Click to expand...
Click to collapse
I made same stupid mistake, so after getting the boot.img and ur command I get waiting for device. Any solution?
NoSuperHero said:
I made same stupid mistake, so after getting the boot.img and ur command I get waiting for device. Any solution?
Click to expand...
Click to collapse
enter recovery if it is installed and flash boot.img from there.
Rootk1t said:
you flashed recovery to boot. So only recovery exists in boot section.
Of course tablet won't boot afterwards, as there is not kernel.
Download custom rom you want to install, unpack boot.img from roms zip files and flash via "fastboot flash boot boot.img"
Afterwards enter recovery and flash custom rom zip, gapps or whatever you need.
Click to expand...
Click to collapse
I did the same thing knowing the outcome and then successfully flashed Lineage.
For future reference, with the Xperia Tablet z where should I be flashing the recovery if not to boot:
"fastboot flash *What goes here?* twrp-3.x.x-0-pollux_windy.img"
big ach said:
I did the same thing knowing the outcome and then successfully flashed Lineage.
For future reference, with the Xperia Tablet z where should I be flashing the recovery if not to boot:
"fastboot flash *What goes here?* twrp-3.x.x-0-pollux_windy.img"
Click to expand...
Click to collapse
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
where twrp.img is your recovery image.
Related
I have the castor windy version 16gb SGP511. I was previously rooted but not unlocked. I unlocked the boot loader. Installed the twrp image on the pac man thread which i think was dual recovery cause Philz,Cwm came out, so I can install lollipop version of the rom. Made a backup of the stock rom. Followed this instructions - Install the Lollipop ROM + GApps+SuperSU using whatever Recovery you have.
- Turn off device completely.
- Press <Volume Up> and plug USB cable.
- LED should turn blue.
- Send command: "fastboot erase recovery"
- Send command for Castor_Windy: "fastboot flash recovery TWRP_Castor_Windy.img"
- Send command for Castor: "fastboot flash recovery TWRP_Castor.img"
- Unplug USB cable.
- Device will reboot.
- When LED turns pink press <Volume Up> and <Volume Down> several times.
- You should now see TWRP
I wasnt fast enough so stock rom booted. I used Adb reboot recovery to access recovery and did as the above mentioned. Wiped i tried to install the rom which failed. Rebooted back to system and got stuck in Sony boot up screen. I can access fastboot. Read though the forums I have to find a ftf or a system image file and use a flash tool. What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Kamaleon said:
What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Click to expand...
Click to collapse
Try this Xperia downloader tool. Should let you see which versions are which. If you want an easy root, then stay away from the KitKat builds, unless you want to unlock bootloader.
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
Use Flashtool to flash your downloaded ftf file. Just make sure your device is charged.
http://forum.xda-developers.com/showthread.php?t=2335555
I believe flashtool will even install the drivers for your 511
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Kamaleon said:
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Click to expand...
Click to collapse
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Moscow Desire said:
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Click to expand...
Click to collapse
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Kamaleon said:
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Click to expand...
Click to collapse
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Moscow Desire said:
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Click to expand...
Click to collapse
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Kamaleon said:
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Click to expand...
Click to collapse
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Moscow Desire said:
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Click to expand...
Click to collapse
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Kamaleon said:
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Click to expand...
Click to collapse
Well, I'm not sure which route to take.
However, I will tell you what I have learned the other day.
I have the 521 with unlocked bootloader. Rooted with my own boot.img, flashed SuperSU using "flashboot boot recovery.img" (yeah, sometimes it doesn't show on the display, so it takes a few times).
Now, other day I was going to check out the new LyPop pre-rooted. Fastboot flash recovery recovery,img, and it won't boot it to recovery like it should. Like it's not flashed. Tried it a couple times. Now, I didn't install the dual recovery as I'm not sure how that kernel (boot.img) will interact with my current tabs OS. Not to mention I need it for my work until tomorrow. But strangely it sounds like the same issue you have.
This weekend I will investigate it. As for me, I will probably flash the Stock ftf lyPop build, and just root it using a modified boot.img.
One thing I do know, is flashing a custom recovery to the "recovery" partition, doesn't seem to work like it used to work on other devices. It seems the flashing to the "Fota kernel" partition seems to be the only method that works. This is what happens when you flash that dual recovery, or any recovery that has a boot image using "Fota". Probably explains why you can't get rid of it using "fastboot erase recovery". because it's erasing the wrong partition. Only flashing a full ftf gets rid of it, because the ftf has a new FotaKernel it flashes.
Eh, something like that. Will look at it this weekend.
I messed up i tried to reflash my phone back to stock from marshmallow rom on the thread here but i lost custom recovery and only thing i can get into is download mode, how can i fix this? I have abd install on my pc got the system image boot and recovery img but don't know what 2 do. Please help
xavier55 said:
I messed up i tried to reflash my phone back to stock from marshmallow rom on the thread here but i lost custom recovery and only thing i can get into is download mode, how can i fix this? I have abd install on my pc got the system image boot and recovery img but don't know what 2 do. Please help
Click to expand...
Click to collapse
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
soltheman said:
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
Click to expand...
Click to collapse
I'm kinda in the same boat now except that I already received the replacement device. Need to re-lock the old V10, but adb won't recognize my device at all. Any more option when that's the case? I can get into both download mode and fastboot. Phone is recognized by LGUP in download mode, but not by adb in fastboot mode for some reason.
(I've verified connection and driver using the other V10, the other V10 is recognized just fine)
soltheman said:
Your phone is in fastboot mode, not download mode. Small, but distinct difference.
Since you've installed a custom ROM, your bootloader should be unlocked. However, it may be a good idea to issue the oem unlock command through fastboot anyways. Use "adb reboot bootloader" and "fastboot oem unlock" to ensure that your bootloader is unlocked.
Now, since your phone is in fastboot mode, you can do one of two things: 1. Flash a custom recovery and restore your device to stock, or 2. Flash a custom recovery and continue using a custom ROM. Either way, you will need to install TWRP or another custom recovery image of your choice. The TWRP thread is located here: http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740 Since you're already in the bootloader/fastboot mode, all you would need to do is download TWRP and use "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" to install TWRP. Please note that the 'twrp.img' will vary depending on which version you download, it will probably look more like 'twrp-2.8.7.1-h901.img'. You can just rename the file or use the full file name in the fastboot commands.
Once in TWRP, you can flash whatever ROM you want. To restore your phone to stock, go to this thread and flash the .zip in TWRP http://forum.xda-developers.com/tmo.../lg-h901-stock-images-device-restore-t3241170 after doing the standard wipe procedure. :good:
Click to expand...
Click to collapse
thanks you saved me
baymon said:
I'm kinda in the same boat now except that I already received the replacement device. Need to re-lock the old V10, but adb won't recognize my device at all. Any more option when that's the case? I can get into both download mode and fastboot. Phone is recognized by LGUP in download mode, but not by adb in fastboot mode for some reason.
(I've verified connection and driver using the other V10, the other V10 is recognized just fine)
Click to expand...
Click to collapse
Yep. Your phone boots and everything, correct? Just factory reset it (Settings > Backup & Restore > Factory data reset). After its been reset, unlock it, turn on Developers Options, and enable USB debugging. After usb debugging is turned on, connect the v10 to your PC and be sure to hit "Always allow" when prompted by your phone. ADB should now be able to see your device.
If you can't get it to boot up, try restoring through LG UP/Bridge. I don't use any of LG's software, so I'm not sure what those apps can do and whether or not you'll be able to restore through them.
If nothing else, your phone is recognized in fastboot mode, so you can always manually flash the stock system images as well. You want to use the "fastboot flash boot boot.img", "fastboot flash recovery recovery.img", and "fastboot flash system system.img" commands After downloading the stock system images located in this thread: http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
If you haven't ever flashed system images from fastboot, please read this first, as I am not responsible if your phone turns into a paperweight! https://developers.google.com/android/nexus/images#instructions While the instructions are for nexus devices, it works pretty much the same, except you'd want to use the individual commands instead of a flash-all script.
Hope this helps!
soltheman said:
Yep. Your phone boots and everything, correct? Just factory reset it (Settings > Backup & Restore > Factory data reset). After its been reset, unlock it, turn on Developers Options, and enable USB debugging. After usb debugging is turned on, connect the v10 to your PC and be sure to hit "Always allow" when prompted by your phone. ADB should now be able to see your device.
If you can't get it to boot up, try restoring through LG UP/Bridge. I don't use any of LG's software, so I'm not sure what those apps can do and whether or not you'll be able to restore through them.
If nothing else, your phone is recognized in fastboot mode, so you can always manually flash the stock system images as well. You want to use the "fastboot flash boot boot.img", "fastboot flash recovery recovery.img", and "fastboot flash system system.img" commands After downloading the stock system images located in this thread: http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
If you haven't ever flashed system images from fastboot, please read this first, as I am not responsible if your phone turns into a paperweight! https://developers.google.com/android/nexus/images#instructions While the instructions are for nexus devices, it works pretty much the same, except you'd want to use the individual commands instead of a flash-all script.
Hope this helps!
Click to expand...
Click to collapse
Thanks for the follow up! No the phone would not boot at all and kept stuck at boot loop. I ended up just doing the OEM Lock and call it a day, the old device just won't boot to anything at this point.
I tried fastboot flash recovery recovery.img but it's giving some kinda kernel panic message and I was never able to get into recovery. This reminds me of the time when my Note 3 eMMC was fried, it wouldn't give a device ID to adb.
I think I am in the same boat too. I've been OEM unlocked yet recently my phone won't keep the TWRP recovery and keeps putting me into bootloop. I can't install a ROM and only thing I can do is fastboot mode. What did you do OEM lock the device? I am hoping that solution will get rid of that message bootloader unlocked during the bootloop and then I can try and get it serviced.
I am trying to put twrp on my tablet so I can install cyanogenmod but I am running into problems.
Device: sgp311 on android 5.1.1 and bootloader is unlocked.
1. I open cmd terminal from the folder that contains the latest twrp img.
2. I boot into fastboot mode by the cmd command "adb reboot bootloader"
3. I use the command " fastboot flash boot twrp.img" and it's successful (had an image but cant link it)
4. I use the command "fastboot reboot" and nothing my device stays blank, nothing appears on screen even after holding the power and volume up buttons to do a regular reset and hard reset. When I flash android 5.1.1 back on to my device all my data is still there.
I am also trying to use flashtool to revert too android kitkat but after flashing the firmware and booting up it just stays in a bootloop at the sony logo.
Anyone have any suggestions on what to do?
BrickedXperia said:
Anyone have any suggestions on what to do?
Click to expand...
Click to collapse
you're doing it right in general, but there are some issues, though.
Sony devices, like your SGP311 don't have recovery[*] partition, like nexus or other ones.
On Sony, you need to flash kernel with the integrated recovery.
On step 3, you're flashing presumably recovery image (without kernel) to boot partition. As it is not kernel, device is is not booting, which is expectable.
So you need to flash this with CM13 kernel + CM recovery. After flashing reboot device, press VOL- to enter recovery, make necessary wipes, and install CM13 Rom zip.
P.S: With Flashtool fastboot mode, flashing is done easier and faster.
Rootk1t said:
you're doing it right in general, but there are some issues, though.
Sony devices, like your SGP311 don't have recovery[*] partition, like nexus or other ones.
On Sony, you need to flash kernel with the integrated recovery.
On step 3, you're flashing presumably recovery image (without kernel) to boot partition. As it is not kernel, device is is not booting, which is expectable.
So you need to flash this with CM13 kernel + CM recovery. After flashing reboot device, press VOL- to enter recovery, make necessary wipes, and install CM13 Rom zip.
P.S: With Flashtool fastboot mode, flashing is done easier and faster.
Click to expand...
Click to collapse
Thank you, I flashed cyanogenmod recovery with adb commands and restarted it and it worked, I now have cyanogenmod on my tablet and it looks and feels way better than the stock rom.
As BrickedXperia, I am trying to put twrp on my tablet so I can install cyanogenmod but I am running into problems.
Device: sgp321 on android 5.1.1 and bootloader is unlocked.
No root (must I?)
1. I open cmd terminal from the platform-tools folder that contains the latest twrp img.
2. I boot into fastboot mode by the cmd command "adb reboot bootloader"
3. I use the command " fastboot flash boot twrp.img" but here it fails and gives an error.
I see from Rootk1t's reply that you have to do something with kernel. Would someone care to elaborate a bit? I am new to this stuff and it's not straight forward despite all the guides around. I would appreciate any help a lot.
What does the error say?
Something like
writing 'recovery'... failed (remote command not allowed)
Svenni84 said:
Something like
writing 'recovery'... failed (remote command not allowed)
Click to expand...
Click to collapse
if it says not allowed, check that bootloader state is really unlocked.
Rootk1t said:
if it says not allowed, check that bootloader state is really unlocked.
Click to expand...
Click to collapse
When I open the hidden service menu it really does say that it is. Is it any other way to confirm this?
I have a problem that i never make it into recovery again. I am used to adb/fastboot, this is my 5th device and i happily used different custom roms as lineage, havoc, crdroid for about 7 years and thus am familiar with the concepts of a/b, recovery, adb/fastboot and so on.
Now, when i "flash_all" with stock from here (V10.3.17.0.PFQEUXM) on my a3, i suppose both slots a and b are overwritten with stock. interestingly this stock rom only boots in a-slot, not in b-slot.
when i now just "fastboot flash recovery twrp...." with 3.3.1.2 and hit the manual enter to recovery (power + vol up), i just get a "no command" error - no twrp in sight.
i also tried this with flash_all V11.0.2.0.QFQEUXM rom (a10) and fastboot flash recovery twrp 3.3.1-17 Q from mauronofrio - same result.
anyone knows what i did wrong?
basically i didnt enter team win recovery for some good amount of tries which slightly terrifies me at this point. (help)
Should i use the global versions instead of the europe ones? Do i need to use "fastboot flash BOOT twrp.." instead of "fastboot flash recovery twrp.."?
I am also happy for suggestions where i could pose this issue more appropriate.
//update: i am now in stock rom and could root it with flashing a magisked boot.img but still cannot enter twrp recovery (-> "no command").
Ya you entered the wrong command it's
Code:
fastboot flash boot twrp.img
When you boot to twrp make sure to flash stock boot.img of the firmware which you are currently running and then flash twrp installer.zip flash both of these in twrp and do not reboot between flashes
thanks @garylawwd
garylawwd said:
Ya you entered the wrong command it's
Code:
fastboot flash boot twrp.img
Click to expand...
Click to collapse
So to be sure: i have stock 11.0.3.0 europe from here installed and i am in slot a now and i cannot go into twrp because it says "no command".
i go to fastboot now, then
Code:
fastboot flash boot twrp.img
with a recent twrp that can run android 10 from here and then power + vol up without switching slots.
garylawwd said:
When you boot to twrp make sure to flash stock boot.img of the firmware which you are currently running and then flash twrp installer.zip flash both of these in twrp and do not reboot between flashes
Click to expand...
Click to collapse
how can i flash a boot.img from twrp? i thought, i can only flash .zips from twrp? Also do i need to take spacial measures to be able to read internal memory in twrp?
//edit: i tried to flash named twrp but it wouldnt boot up into recovery, instead went straight into fastboot. so i flashed boot with stock boot again. no solution in sight.
Just FYI - "no command" is default welcome page of stock recovery. If you see it, you don't have TWRP installed.
_mysiak_ said:
Just FYI - "no command" is default welcome page of stock recovery. If you see it, you don't have TWRP installed.
Click to expand...
Click to collapse
Thank you. Still i would expect twrp to open.
Am i using a/b wrong? When i am on slot a and go into fastboot anf fastboot flash boot twrp.img, then i expect twrp to be installed in a, is that correct? Or is it always installed in the inactive slot and thus i had to switch to slot b before i install twrp to have it on a?
tutankpusch said:
Thank you. Still i would expect twrp to open.
Am i using a/b wrong? When i am on slot a and go into fastboot anf fastboot flash boot twrp.img, then i expect twrp to be installed in a, is that correct? Or is it always installed in the inactive slot and thus i had to switch to slot b before i install twrp to have it on a?
Click to expand...
Click to collapse
No idea with TWRP, never used it on this phone, Magisk is enough for me. But I would follow one of the available guides if you need to have TWRP installed.
_mysiak_ said:
No idea with TWRP, never used it on this phone, Magisk is enough for me. But I would follow one of the available guides if you need to have TWRP installed.
Click to expand...
Click to collapse
Thanks @mysiak_d
I used for example this method with this recovery bc it should work with android 10.
straight into fastboot instead recovery :/
Hi everyone,
I tried to install Lineage OS on my Xperia Tablet Z Wifi and followed the instructions here: https://wiki.lineageos.org/devices/pollux_windy/install
I am on Ubuntu and I did unlock the bootloader successfully. Then I tried to flash twrp but this is where things went wrong.
After entering
Code:
fastboot flash boot ./twrp-3.5.2_9-0-pollux_windy.img
the device did not start anymore. I can still enter fastboot mode and the device is recognized on the PC but else the only thing that happens is the LED blinking red.
Any ideas where to go from here are appreciated.
Rootk1t said:
you flashed recovery to boot. So only recovery exists in boot section.
Of course tablet won't boot afterwards, as there is not kernel.
Download custom rom you want to install, unpack boot.img from roms zip files and flash via "fastboot flash boot boot.img"
Afterwards enter recovery and flash custom rom zip, gapps or whatever you need.
Click to expand...
Click to collapse
I tried this but flashing the boot.img does not change anything unfortunately.
brickedmytablet said:
I tried this but flashing the boot.img does not change anything unfortunately.
Click to expand...
Click to collapse
You can reflash stock ROM via Flashtool v.0.9.18.6. or flash another boot.img to check if it boots or not.
Thank you, this worked for me.
Should have used the right twrp form the beginning. flash to boot works if it is the right version in my case scorpion_windy