Related
I wiped my device and now can't install CM because it thinks it is castor and not castor_windy. It is a wifi z2 tablet.
I used tool from this thread to gain root. After I used root checker basic to check I was rooted and it said I was.
http://forum.xda-developers.com/showthread.php?t=2784900
I used tool from this thread to install custom recovery, I believe successfully. I was able to reboot into recovery afterwards.
http://forum.xda-developers.com/showthread.php?t=2794175
To try and install CM I tried to follow the instructions in this post.
http://forum.xda-developers.com/showpost.php?p=53994500&postcount=1
To do 4&5 in twrp, I wiped cache, system and dalvik. I got the problem in the following picture (pictures are all links because I couldn't work out how to get them small enough to attach).
https://drive.google.com/file/d/0BxoU7oR5AJUeVnE4LXpEd0t6c0k/edit?usp=sharing
It eventually formatted all three.
I then tried to install CM, PA gapps, and recovery (as suggested in the recovery thread to make sure keep recovery after reboot). This happened.
https://drive.google.com/file/d/0BxoU7oR5AJUeT2pkZE53UUdRUDA/edit?usp=sharing
I didn't make a backup in advance because I am an idiot. I do have TA backed up.
What did I do wrong and how can I fix it please?
If I understand you correctly, you have tried too flash CM without unlocking your bootloader first.
As far as I know, this is not possible: Due to the locked bootloader, the CM Kernel cannot be installed and hence CM won't work anyways.
With locked bootloader, you can only flash stock-based ROMs which share the Kernel with the original ROM.
You can use flastool to flash a TFT (stock firmware), then your tablet should work again.
For flashing a real CM which requires an unlocked bootloader see here: http://forum.xda-developers.com/showthread.php?t=2708194
Bootloader unlocking: http://forum.xda-developers.com/showthread.php?t=2747676
Have fun!
BabelHuber said:
If I understand you correctly, you have tried too flash CM without unlocking your bootloader first.
As far as I know, this is not possible: Due to the locked bootloader, the CM Kernel cannot be installed and hence CM won't work anyways.
With locked bootloader, you can only flash stock-based ROMs which share the Kernel with the original ROM.
You can use flastool to flash a TFT (stock firmware), then your tablet should work again.
For flashing a real CM which requires an unlocked bootloader see here: http://forum.xda-developers.com/showthread.php?t=2708194
Bootloader unlocking: http://forum.xda-developers.com/showthread.php?t=2747676
Have fun!
Click to expand...
Click to collapse
Thank you. You are exactly correct, I didn't unlock the bootloader first.
Would this flashtool work given I am currently in twrp and have no OS? If it would it is showing the links for the ROM for SGP511 and this is 512. Is it the same or do I need a different link for the ROM?
http://xperiafirmware.com/8-firmware/50-sony-xperia-z2-tablet-wi-fi-sgp512
Thanks. Trying to have fun.
spanielhead said:
Thank you. You are exactly correct, I didn't unlock the bootloader first.
Would this flashtool work given I am currently in twrp and have no OS? If it would it is showing the links for the ROM for SGP511 and this is 512. Is it the same or do I need a different link for the ROM?
http://xperiafirmware.com/8-firmware/50-sony-xperia-z2-tablet-wi-fi-sgp512
Thanks. Trying to have fun.
Click to expand...
Click to collapse
Look at developer.sonymobile.com/unlockbootloader
IRRC you need to use fastboot to unlock the device. Afterwards, you can install Cm. If you are lucky you don't need to flash a stock ROM first.
BabelHuber said:
Look at developer.sonymobile.com/unlockbootloader
IRRC you need to use fastboot to unlock the device. Afterwards, you can install Cm. If you are lucky you don't need to flash a stock ROM first.
Click to expand...
Click to collapse
Thank you. Have unlock key from Sony now.
I am currently in recovery. Should I be able to reboot the bootloader from recovery and get into fastboot that way? (Reminder I have no OS.)
spanielhead said:
Thank you. Have unlock key from Sony now.
I am currently in recovery. Should I be able to reboot the bootloader from recovery and get into fastboot that way? (Reminder I have no OS.)
Click to expand...
Click to collapse
OK I tried this and bad things. Before the device was detected by my laptop, now it is not and it hangs at the sony logo and no led. Am I f***ed?
spanielhead said:
OK I tried this and bad things. Before the device was detected by my laptop, now it is not and it hangs at the sony logo and no led. Am I f***ed?
Click to expand...
Click to collapse
I would suggest non Sony software anyway. I still have my bootloader, but since it's not allowed to be unlocked I can't use Sony software either.
spanielhead said:
OK I tried this and bad things. Before the device was detected by my laptop, now it is not and it hangs at the sony logo and no led. Am I f***ed?
Click to expand...
Click to collapse
Not at all :good:
By long-pressing the power button (10 seconds or so) the tablet shuts down
Do the following:
- Get your Sony unlock key
- Install the Android SDK (Software Developers Kit) on your PC
- Install all necessary Xperia drivers (Google is your friend, don't remember where I got mine from)
Using fastboot:
- Connect your tablet to the PC while simultaneously pressing 'Volume up'. When the LED is blue you are in fastboot mode
- Unlock your tablet like described by Sony
- Install CWM from fastboot mode
- Reboot
- Enter recovery (press 'Volume up' when the LED is pink)
Copy files to tablet:
- Use the adb command line tool from Android SDK (in the same folder as fastboot)
Copy CM11 and GAPPs to tablet:
via Windows CMD: adb push filename.zip /sdcard/ROMs/filename.zip
- Flash CM11/ GAPPS via recovery
Done!
BabelHuber said:
Using fastboot:
- Connect your tablet to the PC while simultaneously pressing 'Volume up'. When the LED is blue you are in fastboot mode
- Unlock your tablet like described by Sony
Click to expand...
Click to collapse
Have restored device to stock, then rooted and installed custom recovery (as in original post).
Can't get into fastboot mode. Trying as stated above fails. Screen stays off with blue LED. Same thing happens if I reboot into bootloader via flashify or recovery. fastboot devices then does not detect device. It does for my phone so think that means fastboot works.
I must have missed something (again). Thank you for your patience.
Edit: bootloader now unlocked with flashtool.
Edit 2: Used flashtool to fastboot flash boot.img from M9 snapshot (was this my mistake, not CM10?). Now can only get into fastboot, can't get into recovery. Without recovery I require an img file of the rom, is that correct?
hasenbein1966 said:
I don't understand why you guys are so generous with your time and energy and write at length to help people who are too lazy and too careless to read properly and thus f*** up their devices...
Click to expand...
Click to collapse
I made a mistake, possibly multiple mistakes. I will continue to make mistakes. This forum is for people like me who don't know what they are doing to ask for help. No one has to offer that help. I am greatly appreciative when they do.
spanielhead said:
Can't get into fastboot mode. Trying as stated above fails. Screen stays off with blue LED.
Click to expand...
Click to collapse
When the screen stays off with blue LED, you ARE in fastboot mode!
In case fastboot does not work, you haven't installed the according drivers on your PC.
spanielhead said:
Used flashtool to fastboot flash boot.img from M9 snapshot (was this my mistake, not CM10?). Now can only get into fastboot, can't get into recovery. Without recovery I require an img file of the rom, is that correct?
Click to expand...
Click to collapse
You must have done something wrong - I had no problems whatsoever.
Just try it again:
- Flash CWM as described
- Factory reset, format system, format data, wipe cache, wipe Dalvik cache (format data/media only if the internal SD-card should be wiped, too!)
- Flash the boot.img from the CM11 ZIP-file
- Enter CWM and use the adb push-command to flash CM11/GAPPs
- Install CM11 and GAPPs via recovery
Good luck :good:
BabelHuber said:
When the screen stays off with blue LED, you ARE in fastboot mode!
In case fastboot does not work, you haven't installed the according drivers on your PC.
You must have done something wrong - I had no problems whatsoever.
Just try it again:
- Flash CWM as described
- Factory reset, format system, format data, wipe cache, wipe Dalvik cache (format data/media only if the internal SD-card should be wiped, too!)
- Flash the boot.img from the CM11 ZIP-file
- Enter CWM and use the adb push-command to flash CM11/GAPPs
- Install CM11 and GAPPs via recovery
Good luck :good:
Click to expand...
Click to collapse
Did you ever manage to install cm11?
I have the same error, device thinks is Castor when its a sgp512. I tried both and soft bricked it, got out, rooted it again and still have the same error. I did unlock the bootloader, i am rooted, I know how to go into fastboot, flashmode, cwm, twrp, etc. But CM11 does not work!
Very frustrating.
Any ideas?
anyone?
Edit: Problem was that I wasnt flashing the kernel first as stated here: http://wiki.cyanogenmod.org/w/Install_CM_for_castor_windy
Are you saying you missed this one
fastboot -i 0xfce flash boot boot.img
BabelHuber said:
When the screen stays off with blue LED, you ARE in fastboot mode!
In case fastboot does not work, you haven't installed the according drivers on your PC.
You must have done something wrong - I had no problems whatsoever.
Just try it again:
- Flash CWM as described
- Factory reset, format system, format data, wipe cache, wipe Dalvik cache (format data/media only if the internal SD-card should be wiped, too!)
- Flash the boot.img from the CM11 ZIP-file
- Enter CWM and use the adb push-command to flash CM11/GAPPs
- Install CM11 and GAPPs via recovery
Good luck :good:
Click to expand...
Click to collapse
I finally found some time to do this. Flashed boot.img using fastboot (didn't work using flashtool which I think was the most recent problem), flashed m9 in recovery, downloaded and adb pushed then flashed pa zero day GAPPS in recovery, and all is right with the world.
@BabelHuber how might I buy you a beer or coffee to thank you properly?
I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
geek-x said:
I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
Click to expand...
Click to collapse
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
geek-x said:
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
Click to expand...
Click to collapse
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
es0tericcha0s said:
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
Click to expand...
Click to collapse
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
geek-x said:
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
Click to expand...
Click to collapse
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
es0tericcha0s said:
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
Click to expand...
Click to collapse
I tried flashing the firmware.zip file from the thread but I got a FAILED: (remote: not allowed) error in command prompt at the end of the process, what did I do wrong?
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
UPDATE:
Thank you so much es0tericcha0s, I really appreciate the support, I got the /data mount issue fixed finally. I just had to flash an older twrp recovery image and then reflashed the new one in fastboot and I could then flash CM successfully.
I can't believe I finally unbricked this phone, its been bricked since Sunday. Once again, es0tericcha0s, Thank you!
geek-x said:
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
Click to expand...
Click to collapse
You might need to RUU back then. If you have issues with the RUU exe, then you can extract the rom.zip and install it like you did the firmware. There are quite a few tutorials on how to extract it, or there might already be a version floating around for your phone.
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.
So I am stuck on TWRP 2.7.1.0 and i am running slimrom 4.4.4 on a c6833 and the reason for this is because it's the only thing that will boot on my phone. There was some intense trial and error a few months ago and a few days with a bricked phone but I finally got it running again, and I am nervous about messing things up again.
I am wanting to move to a more up to date ROM either scrubber port 5.1 or remix 5.1.1, but they both ask for updated TWRP to install. And I can't update TWRP using the TWRP tool from the store. It downloads but when it tries to install it says there is a problem. Previously, trying to update TWRP would result in SONY bootloops. I was about to try the dd method but just wanted to make sure it was safe.
I am a bit of an idiot (I got rid of my encrypted keys on day 2 of owning the phone) so any help would be appreciated.
Thanks!
walkingagh said:
...
Click to expand...
Click to collapse
The easiest way is to use Rashr. It should set everything up automatically. You may then reboot to recovery from the ROM, or by holding Vol- when the LED turns purple on boot-up.
If that doesn't work, for whatever reason, try dd or Flashtool. Using Flashtool, you can flash openrecovery-twrp-2.8.5.0-togari.img with the phone in Fastboot mode.
Let me know if you have any further questions!
Used Rashr...and now I can't get into recovery. I can still boot into my phone, but booting into recovery just fails with a yellow LED?
So Rashr still says I have 2.7.1.0 installed. :/
walkingagh said:
Used Rashr...and now I can't get into recovery. I can still boot into my phone, but booting into recovery just fails with a yellow LED?
Click to expand...
Click to collapse
Alright, you likely need a newer kernel first. Using Flashtool, you can flash this boot.img (newest AICP kernel) to the boot partition using the Fastboot mode (or use fastboot manually from the Flashtool/x10flasher_lib folder with "fastboot flash boot boot.img"). At this moment, you'll no longer be able to boot into the ROM, so make sure you've done all necessary backups and are ready to install a newer ROM. Then use Flashtool/Fastboot to flash the openrecovery-twrp-2.8.5.0-togari.img file to your recovery/FOTAKernel partition ("fastboot flash recovery openrecovery-twrp-2.8.5.0-togari.img"). You should be able to enter recovery now.
Awesome thanks! Will I need to do this each time I flash a ROM? Or can I just jump from something like scrubber to something else?
I know this is an old thread but is that the boot image I need to run TWRP 3? If so, can I do this via dd?
Triflot said:
Alright, you likely need a newer kernel first. Using Flashtool, you can flash this boot.img (newest AICP kernel) to the boot partition using the Fastboot mode (or use fastboot manually from the Flashtool/x10flasher_lib folder with "fastboot flash boot boot.img"). At this moment, you'll no longer be able to boot into the ROM, so make sure you've done all necessary backups and are ready to install a newer ROM. Then use Flashtool/Fastboot to flash the openrecovery-twrp-2.8.5.0-togari.img file to your recovery/FOTAKernel partition ("fastboot flash recovery openrecovery-twrp-2.8.5.0-togari.img"). You should be able to enter recovery now.
Click to expand...
Click to collapse
That file has expired, any chance you can re-post it?
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