I try to install .img file in recovery, but after install this, my phone shutdown in software brick....
AyalaE96 said:
I try to install .img file in recovery, but after install this, my phone shutdown in software brick....
Click to expand...
Click to collapse
Don't use install img option on twrp it may not work always
Instead of that you can flash recovery using fastboot with "fastboot flash recovery (the name of recovery).img) command
raminta said:
Don't use install img option on twrp it may not work always
Instead of that you can flash recovery using fastboot with "fastboot flash recovery (the name of recovery).img) command
Click to expand...
Click to collapse
I tried, and it didnt work...
AyalaE96 said:
I tried, and it didnt work...
Click to expand...
Click to collapse
Do you have unlocked bootloader???
raminta said:
Do you have unlocked bootloader???
Click to expand...
Click to collapse
yep
raminta said:
Do you have unlocked bootloader???
Click to expand...
Click to collapse
I solved it, I first must install Repack boot with "fastboot flash boot ...img"
After install recovery with "Fastboot flash recovery ...img"
My error Because I should read this first...
Dees_Troy said:
Note that the Z2, like most other Sony devices does not have a proper bootable recovery. As such you have to install a kernel that includes a recovery with it. For a time I will try to continue to supply updated stock kernels repacked with TWRP in them. If you are running one of my kernels or have a custom ROM like OmniROM installed, you can install TWRP in the FOTAKernel partition to stay on the latest version of TWRP.
Device page on our website
Mirror 1
Mirror 2
To install a stock kernel, boot the device into fastboot mode and then from your computer: fastboot flash boot path/to/filename.img
Click to expand...
Click to collapse
However is it true? With latest updates there was bootloader update which brings (or at least should as Sony said) /recovery partition (or more gives access to it, coz partitions was probably always there).
However how it exactly works? I always thought that onee flashed update with newest bootloader will leave new bootloader and this partition forever. But I got Z2 with .291, downgraded it to 4.4.2 for Root and TA backup and than tried to flash recovery to recovery partition, but got error: FAILED (data transfer failure (Unknown error)).
Does it mean that only on latest update(s) there is possibility to use this partition?
Never tried it on my ZU before. I just started form latest 5.1.1.
EDIT: OK, so what i assumed was right - on 6.0.1 I was able to flash the recovery to it's partition.
Now the problem is with booting into it. How? With Power + Vol- it still stright to boots to OS...
EDIT2: adb reboot recovery boots to different bootloader screen (Power+Vol- gives SONY screen and adb gives SONY + XPERIA screen.
However it still boots strght to Android...
Any idea what I'm doing wrong? I have 23.5.A.1.291 + unlocked bootloader + TWRP 3.0.2-0 (official) flashed with fastboot flash recovery img.
I'm 100% sure that SONY screen (w/o XPERIA) is the right one as I have identical one on my ZU when booting into bootloader-recovery mode. But why here it don't boot TWRP, but OS?
HELPPPP
Pleaseeeee tell me how did you flash twrp 3.0? I have tried almost everything it now seems impossible for me... Pleaseee helpp me T_T ... Thankk youuu
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?
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?
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 :/
I am using Asus zenfone 3. And I have installed TWRP in it. But the phone is not booting to system (os) . And the TWRP I installed , the touch does not work for it. If I boot to system, it shows the boot logo and turns off. What can I do now?
LavanTech said:
I am using Asus zenfone 3. And I have installed TWRP in it. But the phone is not booting to system (os) . And the TWRP I installed , the touch does not work for it. If I boot to system, it shows the boot logo and turns off. What can I do now?
Click to expand...
Click to collapse
To me it seems that phone's boot-loader is got corrupted. Not unusual when installing TWRP.
jwoegerbauer said:
To me it seems that phone's boot-loader is got corrupted. Not unusual when installing TWRP.
Click to expand...
Click to collapse
Do u have any solution??
LavanTech said:
Do u have any solution??
Click to expand...
Click to collapse
Did you have enabled in Developer Options the USB debugging & OEM unlock features before the device bricked.?
LavanTech said:
I am using Asus zenfone 3. And I have installed TWRP in it. But the phone is not booting to system (os) . And the TWRP I installed , the touch does not work for it. If I boot to system, it shows the boot logo and turns off. What can I do now?
Click to expand...
Click to collapse
Also I cannot install with flash tool , I'm getting unhandled exception error!
jwoegerbauer said:
Did you have enabled in Developer Options the USB debugging & OEM unlock features before the device bricked.?
Click to expand...
Click to collapse
Ya! I eabled usb debugging , unlocked bootloader also OEM unlock.
LavanTech said:
Also I cannot install with flash tool , I'm getting unhandled exception error!
Click to expand...
Click to collapse
Re--flash Stock Recovery.
jwoegerbauer said:
Re--flash Stock ROM.
Click to expand...
Click to collapse
Both are enabled!!!
LavanTech said:
Both are enabled!!!
Click to expand...
Click to collapse
I've edited the cited post. Re-read.
jwoegerbauer said:
Re--flash Stock Recovery.
Click to expand...
Click to collapse
I have stock rom downloaded, which software can I use to flash ?? Pls give any link to download.
jwoegerbauer said:
I've edited the cited post. Re-read.
Click to expand...
Click to collapse
Pls provide me link for downloading stock recovery and software to flash!
LavanTech said:
I have stock rom downloaded, which software can I use to flash ?? Pls give any link to download.
Click to expand...
Click to collapse
To get rid off of TWRP you flash Stock Recovery.
I think the correct command sequence is
Code:
adb reboot
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery <STOCK-RECOVERY-IMAGE-FILE>
fastboot reboot-bootloader
fastboot erase cache
fastboot reboot
Search for the appropriate Stock Recovery image by yourself. GIYF ...
If you instead want to re-flash Stock ROM then the correct command sequence would be
Code:
adb reboot
adb devices
adb reboot bootloader
fastboot devices
fastboot flash-all <STOCK-ROM-IMAGE-FILE>
fastboot reboot
Try going back to stock (Fastboot/download mode/Odin, depending on the device)
Thank You!
I have successfully went to fastboot mode and flashed the stock rom! Thank you for your support!! ?? The phone is working now in the Android 7.
BUT,
now if i install twrp custom recovery, i don't know what happens, after restarting to system i cannot boot to system , it just shows the boot animation and just goes off or sometimes it boots to fastboot mode.
then if i flash the stock rom again using the sd card in the the default recovery mode after flashing that stock recovery, it works again.
Also if I install TWRP recovery, TWRP could not install any Roms ! it just says that Updater process ended with error 6 or 7 randomly.
So, how do I install custom recovery and roms in it now?
LavanTech said:
So, how do I install custom recovery and roms in it now?
Click to expand...
Click to collapse
Assumed the TWRP.IMG you use is the correct one, then there is no need to install TWRP recovery, booting into it is fully enough - this will preserve device's Stock Recovery
Code:
fastboot devices
fastboot boot <TWRP.IMG>
The TWRP is booting perfectly! But if I install any zip file i.e ROM or Mods, it says that Updater process ended with error 6 or 7!!
This is the problem with TWRP.
And, if install TWRP in the phone, then restart the phone , if I restart to system, it doesn't work ,just it shows the boot animation and turns off.
LavanTech said:
The TWRP is booting perfectly! But if I install any zip file i.e ROM or Mods, it says that Updater process ended with error 6 or 7!!
This is the problem with TWRP.
Click to expand...
Click to collapse
This is not TWRP recovery related, but it's related to the Custom ROM zip-file you try to flash: The ROM zip-file you try to flash isn't made for your device.
jwoegerbauer said:
This is not TWRP recovery related, but it's related to the Custom ROM zip-file you try to flash: The ROM zip-file you try to flash isn't made for your device.
Click to expand...
Click to collapse
I'm trying to flash ASUS ZENFONE 3 LINEAGE OS 16
MY DEVICE : ASUS ZENFONE 3 ZE552KL
THE FILE : https://mirrorbits.lineageos.org/fu...age-16.0-20200727-nightly-zenfone3-signed.zip
I am using the file which is for my device only! But it is not working, what should I do?
LavanTech said:
I'm trying to flash ASUS ZENFONE 3 LINEAGE OS 16
MY DEVICE : ASUS ZENFONE 3 ZE552KL
THE FILE : https://mirrorbits.lineageos.org/fu...age-16.0-20200727-nightly-zenfone3-signed.zip
I am using the file which is for my device only! But it is not working, what should I do?
Click to expand...
Click to collapse
Start a new thread ...
Here is the new thread
Here is the new thread :- https://forum.xda-developers.com/android/help/twrp-issues-asus-zenfone-3-t4145317
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