Related
TL;DR: Nexus 9 bootloops with every ROM other than stock.
My Nexus 9 will bootloop whenever any custom ROM is installed on it. I follow the usual steps in TWRP (downloading ROM and Gapps, wiping factory reset, flashing the zips and wipe dalvik/cache) will not get any error during installation and regardless of the ROM, I will get my nexus stuck on Google logo. Then I will have to unroot and install stock again and it'll work.
Ive also tried Wugfresh Nexus Root Toolkit and it won't work either. As long as Im on stock, I can root as well and everything is fine.
Any idea what could be happening? I wanna get rid of the damn lag. Have tried Cyanogenmod, Slimrom6 and Pure Nexus Project. All with their recommended gapps and will always end up with my tablet stuck in the Google logo.
Any help is very appreciated.
Sounds like you are doing everything right..
How long are you waiting for the device to start up ? Is it possible you aren't simply waiting long enough ? I'd give it a good 10 - 20 minutes on 1st boot before deciding it's hung in a boot loop.
I am having the exact same problem. I have tried so many roms that install correctly and then when flashing gapps and rebooting it is stuck on the Google logo. And I left my tablet on for a few hours so its definitely bootlooping.
The only thing that comes to mind is bootloader... If you coming to androind 7.x from android 6.x, you need to flash new bootloader (for example via ADB), otherwise you'll end up in a bootloop.
yup, happening to me too. so, how can i flash the factory image now? thanks.
It's in the stickies. http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Sent from my Nexus 5X using XDA-Developers mobile app
links to 7.x compatible bootloader where?
maelfilk said:
If you coming to androind 7.x from android 6.x, you need to flash new bootloader (for example via ADB), otherwise you'll end up in a bootloop.
Click to expand...
Click to collapse
I understand that i'll have to use adb (actually fastboot) to flash the bootloader. But where do i get the right one for android 7.x and flpunder device?
Could you please post the links for that?
Thanks in advance!
nexacan said:
I understand that i'll have to use adb (actually fastboot) to flash the bootloader. But where do i get the right one for android 7.x and flpunder device?
Could you please post the links for that?
Thanks in advance!
Click to expand...
Click to collapse
You can download the necessary image here: https://developers.google.com/android/images
Inside the archive you'll find bootloader and vendor
bootloader flashing process: enough to "fastboot flash bootloader boot*.img"?
maelfilk said:
You can download the necessary image here: https://developers.google.com/android/images
Inside the archive you'll find bootloader and vendor
Click to expand...
Click to collapse
I assume i need the latest 7.0.0 (NRD91N, Nov 2016) bootloader which is inside the latest build?
Then i will need to go through the process like:
Code:
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
Or do i have to do more like described here (Steps 8-9)?
Your help is appreciated, thanks again!
ps: for others who got stuck in the bootloop and don't know how to stop it or turn off the device:
1. reboot into recoverymode in case you have twrp
2. open a terminal
3. type in
Code:
poweroff
an hit enter
Yes, NRD91N
Well , all i did was simple
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
once complete
fastboot reboot-bootloader
That's it
Still not booting...
maelfilk said:
Yes, NRD91N
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
fastboot reboot-bootloader
...
That's it
Click to expand...
Click to collapse
Thanks for clarifying that. Unfortunately i still can't boot into AOSP_flounder_11-18-2016.zip
which i flashed afterwards. The bootloader is shown correctly though. But when i start the
Nexus 9 the message https://g.co/ABH is shown in red.
Which rom are you running? A CM build or AOSP?
ps: trying with cm-14.1-20161027-UNOFFICIAL-flounder.zip now, but boot seems to hang too and the upper part
of the Nexus 9 is getting really warm. I will leave it for 15 more minutes to wait and see what happens.
nexacan said:
Thanks for clarifying that. Unfortunately i still can't boot into AOSP_flounder_11-18-2016.zip
which i flashed afterwards. The bootloader is shown correctly though. But when i start the
Nexus 9 the message https://g.co/ABH is shown in red.
Which rom are you running? A CM build or AOSP?
Click to expand...
Click to collapse
Hmm sorry i don't knwo why this is happening.
Currently i reverted back to marshmallow roms, i find them more stable.
Do you have twrp? After flashing bootloader i go to twrp and do complete wipe and format data, then flash new rom. I had no problems booting.
maelfilk said:
Do you have twrp?
Click to expand...
Click to collapse
Sure, the latest from TWRP
twrp-3.0.2-1-flounder.img 13M 2016-08-24 16:30:03 EDT
maelfilk said:
After flashing bootloader i go to twrp and do complete wipe and format data, then flash new rom. I had no problems booting.
Click to expand...
Click to collapse
I will try it again - exactly as you describe it. Maybe i missed a step.
How long did you wait after reboot for the system to start up?
nexacan said:
Sure, the latest from TWRP
twrp-3.0.2-1-flounder.img 13M 2016-08-24 16:30:03 EDT
I will try it again - exactly as you describe it. Maybe i missed a step.
How long did you wait after reboot for the system to start up?
Click to expand...
Click to collapse
About 10-15 minutes
It works now!
Thank you maelfilk, i got i running now.
CM boots properly now - though i cannot configure it. During the Setup process
in the first step of selecting the language it crashes. I am sure this will be fixed
with a later version of CM-14.1.
Does someone know any other source for CM-14.1 for flounder?
Meanwhile i will try AOSP again.
Edit: AOSP boots properly but unfortunately WLAN does not work in the AOSP_flounder_11-18-2016.zip build.
I guess this is why you stick to the 6.x builds maelfilk.
большое спасибо
nexacan said:
большое спасибо
Click to expand...
Click to collapse
Glad it works
As for wlan problem, did you flash the vendor as well? If not it might be the problem
link to the "vendor"
maelfilk said:
Glad it works
As for wlan problem, did you flash the vendor as well? If not it might be the problem
Click to expand...
Click to collapse
Man, you are so helpfull! Where do i find the "vendor" (drivers?) please?
I guess i will find it as it is described here
nexacan said:
Man, you are so helpfull! Where do i find the "vendor" (drivers?) please?
I guess i will find it as it is described here
Click to expand...
Click to collapse
In the archive with bootloader is another archive with vendor and other images. Just flash it in twrp as in the instructions in the link you gave. If you have trouble with wlan or camera it usually means that vendor is outdated.
Black bootscreen and hanging after flashing vendor.img (only vendor.img)
maelfilk said:
In the archive with bootloader is another archive with vendor and other images. Just flash it in twrp as in the instructions...
Click to expand...
Click to collapse
I did that and now there is no bootscreen, and the Nexus 9 does not boot up
Maybe i am missing something again? I did a wipe and fresh install, but that did not help.
Also TWRP disappears after flashing vendor.img
nexacan said:
I did that and now there is no bootscreen, and the Nexus 9 does not boot up
Maybe i am missing something again? I did a wipe and fresh install, but that did not help.
Also TWRP disappears after flashing vendor.img
Click to expand...
Click to collapse
Are you sure you chose to flash vendor.img in vendor partition in twrp?
Hi Guys,
I've got a SGP511 WiFi only (castor_windy), with root access and an unlocked bootloader. but to install AOSP 7.1 I need to update my version of TWRP to 3.0.0.
I installed TWRP via TabZ2-lockeddualrecovery2.8.26 batch file and can access recovery but every time i select install look at my SD card and change to images and select the castor_winsy 3.0.0 image i dont get an option to install to recovery i only get kernel how do i resolve this ?
I have re flashed FW (KitKat) via flashtool loads of times
rooted
installed TabZ2-lockeddualrecovery2.8.26 batch file
and every time i get the same option.... cant flash to recovery or boot only kernel
i have attached a screenshot so that nobody thinks i am going mad
can you please help me thanks :fingers-crossed:
It's been a while since I used TWRP 2.8.XX...so no idea what's the issue there but I'd just flash TWRP recovery via fastboot. Worked for me without any problems :good:
T4ke5 said:
It's been a while since I used TWRP 2.8.XX...so no idea what's the issue there but I'd just flash TWRP recovery via fastboot. Worked for me without any problems :good:
Click to expand...
Click to collapse
Hi ... Is that using the ADB fastboot recovery TWRP.img?
I am on KitKat just wondering if that's why it won't work have you got to be on 6.01 ?
Well, actually it shouldn't matter on which Android version you are, but to have the latest boot.img and radio.img installed I'd flash the latest stock ROM available here on XDA which means by the way having TWRP 3.0.2.0 as well and after that you might be ready for AOSP 7.1
Just have look at kulvertti's thread in the "General" subforum. Since you have already intalled a custom recovery there shouldn't be any problems.
Lockeddual recovery is not compatible with any custom rom
Please follow the instructions in the thread
rcstar6696 said:
Lockeddual recovery is not compatible with any custom rom
Please follow the instructions in the thread
Click to expand...
Click to collapse
Hi @rcstar696 have you got a link to the instructions please as I can't seem to find it ... thanks
nickbaker66 said:
Hi @rcstar696 have you got a link to the instructions please as I can't seem to find it ... thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/xpe.../aosp-6-0-marshmallow-sony-xperia-z2-t3235935
first two steps of instruction
rcstar6696 said:
http://forum.xda-developers.com/xpe.../aosp-6-0-marshmallow-sony-xperia-z2-t3235935
first two steps of instruction
Click to expand...
Click to collapse
Hi @rcstar6696,
i had no problem flashing the boot.img that part was ok but when i went to flash the recovery it never seemed to work for me, in the terminal window in the SDK programme tools folder which is the same folder as the image i downloaded from your thread is in (Twrp-3.0.0-0-castor-windy.img and twrp_castor_windy.img) it said something about sizes but said it went ok tried to boot into recovery and it never worked
in the terminal window whilst my SGP511 was in fastboot mode i typed fastboot recovery Twrp-3.0.0-0-castor-windy.img is this is correct script or have i got this wrong ?
i am currently on Kitkat does this matter
thansk
nickbaker66 said:
in the terminal window whilst my SGP511 was in fastboot mode i typed fastboot recovery Twrp-3.0.0-0-castor-windy.img is this is correct script or have i got this wrong ?
thansk
Click to expand...
Click to collapse
The right command is
fastboot flash recovery PathToRecovery*
Click to expand...
Click to collapse
*C:\stuff\more_stuff\TWRP_castor-windy.img for instance
T4ke5 said:
The right command is
*C:\stuff\more_stuff\TWRP_castor-windy.img for instance
Click to expand...
Click to collapse
Cheers guys I'll give that a go
T4ke5 said:
The right command is
*C:\stuff\more_stuff\TWRP_castor-windy.img for instance
Click to expand...
Click to collapse
rcstar6696 said:
http://forum.xda-developers.com/xpe.../aosp-6-0-marshmallow-sony-xperia-z2-t3235935
first two steps of instruction
Click to expand...
Click to collapse
hi guys i tried what you said and still could get it to work, please see screenshot and check if i have entered something wrong, i dont thinki have but i might be wrong
is it because i have not done the boot image first via fastboot ?
Looks quite good. Did you already try to enter the recovery?
T4ke5 said:
Looks quite good. Did you already try to enter the recovery?
Click to expand...
Click to collapse
i tried to access recovery via the down volume button when the tablet starts up but no green light appears and it just starts normally ...... i ve not flashed the boot.img first then flashed recovery as ive seen it can be done via recovery the only option left now is to try flashing the boot.img first .... i have no option but to try that tonight and see if that can do it that way
@T4ke5 @rcstar6696 thanks very much guys for your help TWRP on 3.0.0 now and AOSP 7.1 installed now
Sweet! :good:
T4ke5 said:
Sweet! :good:
Click to expand...
Click to collapse
Don't laugh but I can't put my WiFi code in because there's no keyboard just tap to speak how can I have the keyboard back lol
T4ke5 said:
The right command is
*C:\stuff\more_stuff\TWRP_castor-windy.img for instance
Click to expand...
Click to collapse
Cheers mate worked a treat
Since there's no thread about it yet (in here then), I'll just make this one so that there won't be any more confusion for TWRP links.
Do keep in mind that if you use the official bootloader unlock method, you won't receive OTA updates anymore from Asus.
Have a great day and happy flashing
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
I'm using more current Twrp and magisk 16 I do not know which is preventing the biometric reader
rinampa said:
I'm using more current Twrp and magisk 16 I do not know which is preventing the biometric reader
Click to expand...
Click to collapse
At the time, I do not know either what is causing this. Because the Oreo rom is rather bugged a bit. (Lower audio, wifi not turning on once it's off and now this)
What twrp should i use for nougat version?
HnsAlczr said:
What twrp should i use for nougat version?
Click to expand...
Click to collapse
Since it's nougat, preferably use 20180304. Once on Oreo, you can flash the latest.
+)KEV1N(+ said:
Since it's nougat, preferably use 20180304. Once on Oreo, you can flash the latest.
Click to expand...
Click to collapse
After i flash twrp thru adb reboot it on twrp works properly but when i reboot to system im stuck at Asus Logo, did i do something wrong on the process?
HnsAlczr said:
After i flash twrp thru adb reboot it on twrp works properly but when i reboot to system im stuck at Asus Logo, did i do something wrong on the process?
Click to expand...
Click to collapse
Did you upgrade your system to Oreo? If so, did you have substratum themes on?
I wonder when he opens the twrp he asks for the PIN number , password or something?
How do I unlock the ZenFone 3 Zoom bootloader on Android Oreo ?
ZueiraBR said:
How do I unlock the ZenFone 3 Zoom bootloader on Android Oreo ?
Click to expand...
Click to collapse
https://www.asus.com/br/Phone/ZenFone-3-Zoom-ZE553KL/HelpDesk_Download/,Select the android operating system, Versão UnlockTool_2018_0629(android O)
2018/06/29740.7 KBytes.
Read the instructions carefully.
+)KEV1N(+ said:
Since there's no thread about it yet (in here then), I'll just make this one so that there won't be any more confusion for TWRP links.
Do keep in mind that if you use the official bootloader unlock method, you won't receive OTA updates anymore from Asus.
Have a great day and happy flashing
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Hi all, does not work with WW-80.30.76.10 . Help me please
personal I flashed the twrp by adb fastboot soon then I entered i REBOOTED-SYSTEM by own twrp! but when I turned it off and put it in recouvery mode (twrp) it goes into the original factory recovery! Does anyone know the solution ??
Delaias1995 said:
personal I flashed the twrp by adb fastboot soon then I entered i REBOOTED-SYSTEM by own twrp! but when I turned it off and put it in recouvery mode (twrp) it goes into the original factory recovery! Does anyone know the solution ??
Click to expand...
Click to collapse
Installed twrp by fastboot goes into recovery in twrp restart the always by twrp.
After updating to twrp new version I can not update more firmware, I have to download recovery stock
I am having problems in twrp I can not install rom always error 7 in this last update how to solve?
Please, I appreciate your help.
+)KEV1N(+ said:
Since there's no thread about it yet (in here then), I'll just make this one so that there won't be any more confusion for TWRP links.
Do keep in mind that if you use the official bootloader unlock method, you won't receive OTA updates anymore from Asus.
Have a great day and happy flashing
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Is there any UN-OFFICIAL unlock method ? tks
Can someone help me? I can't find the correct version (or doesn't even exist) of twrp for my zenfone zoom s.
(UL-Z01H-WW-80.30.76.74)
Unlocking Bootloader1. Make sure you have a sim and active mobile data. Then go to about phone tap build number 7-8 times. After that go to advanced settings > developer options > turn on OEM unlocking and then check if this device is secure and click add account and device.
2. Download Mi unlock tool from here. Extract it and paste it in C:/unlock. or else your device won't be recognized for unlocking.
3. Open Mi unlock tool and then enter the Mi account which was on your device. Put your device in fastboot mode by pressing vol- and power and then connect to PC. Press unlock and if it tells you to wait you have no other option but to wait. If your mi flash tool shows connect your device even after you have connected it. Follow this guide here.
4. After you have unlocked your bootloader reboot your phone.
Flashing TWRP and Rooting via magisk
1. Download this TWRP image here. Thanks to the original developer mauronofrio.
2. Download adb and fastboot tools here and install it.
3. Now put your phone in fastboot mode and connect it with your pc. Now where you have downloaded the TWRP file rename it to TWRP.img and open a CMD window there if you don't know how just google.
4. Type the following commands
1. fastboot devices
2. fastboot flash recovery TWRP.img
3. fastboot reboot recovery.
Click to expand...
Click to collapse
5. Your phone will boot into TWRP now. But TWRP will be overwritten by stock miui recovery to stop that you need to flash Magisk. Download this zip move it to internal storage then flash by tapping on install and swipe to flash. Reboot your device. Reboot to recovery again to check if TWRP is present.
Now your device is rooted
OR
Flash latest OrangeFox Recovery if you don't want magisk.
Flashing A rom
1. Download.
2. Flash.
3 Format Data.
Done
Feel free to ask any questions. And don't point a finger at me for messing your device.
My mi unlock tool says can't get info. I using Indian version miui 12
Thanks for the useful guide. I have a quick question, does this works with MIUI 12?
igeekyayush said:
My mi unlock tool says can't get info. I using Indian version miui 12
Click to expand...
Click to collapse
Sorry for late reply. Have you installed the drivers correctly? Try using another port in your pc or use this mi unlock tool version zip
Doombuggie85 said:
Thanks for the useful guide. I have a quick question, does this works with MIUI 12?
Click to expand...
Click to collapse
Yes, it does.
hello,
thanks for the reply sir. yes i've tired changing port, pc everything. today i've factory reset my phone and added mi account and now i'm getting 7 days wait time. let's see now
LoadOP2 said:
Sorry for late reply. Have you installed the drivers correctly? Try using another port in your pc or use this mi unlock tool version zip
Click to expand...
Click to collapse
igeekyayush said:
hello,
thanks for the reply sir. yes i've tired changing port, pc everything. today i've factory reset my phone and added mi account and now i'm getting 7 days wait time. let's see now
Click to expand...
Click to collapse
Okay keep the sim inserted and use the device for 7 days. And if it doesn't work try using older version of unlock tool.
Hi there!
Silly question: is it possible to install TWRP but keep the official ROM? (phone is unlocked)
_benedict_ said:
Hi there!
Silly question: is it possible to install TWRP but keep the official ROM? (phone is unlocked)
Click to expand...
Click to collapse
Flashing a custom rom is optional. You don't NEED to flash a rom to get TWRP...
---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------
I've unlocked the bootloader using the unlock tool and waited for 7 days,
But i rooted the device using a different method where i patched a boot.img and flashed that to the device.
Will this method still work for me as I'm already rooted but just want TWRP so i can flash other ROMs.. The post says you have to flash magisk from the (temporary) TWRP for the TWRP to stay as the recovery..
Will the magisk on my phone and the magisk installed here collide?
I just want TWRP so i can switch to a custom rom, so any input is appreciated!!
_benedict_ said:
Hi there!
Silly question: is it possible to install TWRP but keep the official ROM? (phone is unlocked)
Click to expand...
Click to collapse
Skip the flashing a rom part and you will be good to go.
But i rooted the device using a different method where i patched a boot.img and flashed that to the device.
Will this method still work for me as I'm already rooted but just want TWRP so i can flash other ROMs.. The post says you have to flash magisk from the (temporary) TWRP for the TWRP to stay as the recovery..
Will the magisk on my phone and the magisk installed here collide?
I just want TWRP so i can switch to a custom rom, so any input is appreciated!!
Click to expand...
Click to collapse
You can flash twrp and then check if it persists. If not flash magisk again their is no thing as magisk colliding lol. Just make sure you flash a newer version. And if nothing works flash stock rom and then twrp.
If you have the stock boot IMG flash it and then intsall twrp and magisk.
smsry said:
Flashing a custom rom is optional. You don't NEED to flash a rom to get TWRP...
Click to expand...
Click to collapse
LoadOP2 said:
Skip the flashing a rom part and you will be good to go.
Click to expand...
Click to collapse
Haha, makes sense! Thank you for your answers
Nevermind.. i got it to work pretty easily..
I have twrp on this device and Pixel Experience ROM and it's working all fine..
But there's this one thing where when booting to recovery, it asks me to input a password for User(0) when i try to input anything it says password failed..
From reading the log, it says it's for decrypting data(8f I'm not mistaken)
Is this important? Do i need to decrypt it?
Currently the ROM works fine with no errors, so I'm not gonna bother, but would still like to know what this "decrypting" thing is..
smsry said:
Nevermind.. i got it to work pretty easily..
I have twrp on this device and Pixel Experience ROM and it's working all fine..
But there's this one thing where when booting to recovery, it asks me to input a password for User(0) when i try to input anything it says password failed..
From reading the log, it says it's for decrypting data(8f I'm not mistaken)
Is this important? Do i need to decrypt it?
Currently the ROM works fine with no errors, so I'm not gonna bother, but would still like to know what this "decrypting" thing is..
Click to expand...
Click to collapse
Yes, If you use a lock screen enter that password it will be decrypted. You will have to format data if you decide to flash any other rom anyway.
flashed twrp but not able to boot into recovery.
igeekyayush said:
flashed twrp but not able to boot into recovery.
Click to expand...
Click to collapse
There can be many reasons for that. Please tell me the error or what's actually happening. Then only I can be of help.
Sir ive used xiaomi flashtool v2 after that and it worked. Thanks sir. After that i updated to latest twrp from that chinese one.
LoadOP2 said:
There can be many reasons for that. Please tell me the error or what's actually happening. Then only I can be of help.
Click to expand...
Click to collapse
Joyeuse
Hello, Does it work for Joyeuse (European version)?
The name of TWRP says Curtana -Unified
rfguy said:
Hello, Does it work for Joyeuse (European version)?
The name of TWRP says Curtana -Unified
Click to expand...
Click to collapse
Yes Unified means all Snapdragon 720g Devices which include Joyeuse, Curtana, Gram, Excalibur.
Hey buddy, thank you for this quick step-by-step guide. I flash ROMs since 2012 and you know what? It helped me the same. Having all stuff needed for go from stock to custom concentrated in one place (plus some useful tip like the Magisk flash at the end) it's always useful and time-saving. Thank you
2 Micro-notes about fastboot btw:
- write 'fastboot (with lowered 'f'): it may confuse some newbie
- it's 'reboot' instead of 'boot'
Hello, I have a tablet Xperia Z2 andriod 6.0.1, the original sony rom. I can't upload TWRP, everything loads fine with fastboot and TWRP won't boot because I'd like to install LineageOS. Bootloader unlocked correctly.
Sorry for my bad english and please help
From what I found out, it is possible to upload a custom rom via NUT'S Dual Recovery. Only the download page of this program and the links are inactive. If anyone has it, please link to the NUT'S Dual Recovery program
As you know fastboot, try this and see if you have luck.
Extract your custom rom zip and reveal your .img files.
Put the .img files into the same folder with fastboot.exe
fastboot erase cache
fastboot erase data
fastboot flash system system.img
fastboot flash boot boot.img
If you have luck, it will boot into system. Backup, always, beforehand as it will delete all your data.
Thank you very much, thanks to this I somehow managed to launch TWRP. I have installed LineageOs 18.1, the system works.
Silny033 said:
Thank you very much, thanks to this I somehow managed to launch TWRP. I have installed LineageOs 18.1, the system works.
Click to expand...
Click to collapse
Could you please describe your steps? I followed the instructions in lineage's wiki, tried flashing the latest castor compatible lineage recovery, tried different TWRP versions... It's always the same: fastboot prints "OKAY" but I can't boot into recovery.
My device is unlocked, but not rooted.
Testing Tester said:
Could you please describe your steps? I followed the instructions in lineage's wiki, tried flashing the latest castor compatible lineage recovery, tried different TWRP versions... It's always the same: fastboot prints "OKAY" but I can't boot into recovery.
My device is unlocked, but not rooted.
Click to expand...
Click to collapse
Hello, did you try fastboot boot twrp twrp.img, and flash TWRP in TWRP as soon as you get into it?
Testing Tester said:
Could you please describe your steps? I followed the instructions in lineage's wiki, tried flashing the latest castor compatible lineage recovery, tried different TWRP versions... It's always the same: fastboot prints "OKAY" but I can't boot into recovery.
My device is unlocked, but not rooted.
Click to expand...
Click to collapse
I'm in the same situation except I only tried with Lineage recovery for now. What did you end up doing? Many thanks.
LR7875 said:
Hello, did you try fastboot boot twrp twrp.img, and flash TWRP in TWRP as soon as you get into it?
Click to expand...
Click to collapse
Shall I try this? At this stage I haven't even tried TWRP. I only tried LineageOS Recovery but same situation as @Testing Tester : impossible to boot into it. What TWRP version do you recommand? @Silny033 which version worked for you?
Bonpotiron said:
Shall I try this? At this stage I haven't even tried TWRP. I only tried LineageOS Recovery but same situation as @Testing Tester : impossible to boot into it. What TWRP version do you recommand? @Silny033 which version worked for you?
Click to expand...
Click to collapse
I did everything as LR7875 advised, boot twrp first and then LineageOS 18.1 and it works fine. I have twrp 3.2.1-1
Silny033 said:
I did everything as LR7875 advised, boot twrp first and then LineageOS 18.1 and it works fine. I have twrp 3.2.1-1
Click to expand...
Click to collapse
LineageOS 18.1 really? I'm confused because the instructions on Lineage website say that the last nightly built is LineageOS 17.1 – [ Android 10.0.0 (Android 10) ] of 2021-10-06
LR7875 said:
As you know fastboot, try this and see if you have luck.
Extract your custom rom zip and reveal your .img files.
Put the .img files into the same folder with fastboot.exe
fastboot erase cache
fastboot erase data
fastboot flash system system.img
fastboot flash boot boot.img
If you have luck, it will boot into system. Backup, always, beforehand as it will delete all your data.
Click to expand...
Click to collapse
What do you call 'system' please? is it the custom rom or the recovery?
Is this procedure similar to yours? the user also has the SGP511 device. https://forum.xda-developers.com/t/...for-castor-castor_windy.4210181/post-84710741
Bonpotiron said:
What do you call 'system' please? is it the custom rom or the recovery?
Click to expand...
Click to collapse
1. Unzip the lineageos zip
2. Find system.img (special case it is system.new.dat.br, tell me if it is)
3. Execute the aforementioned command
LR7875 said:
1. Unzip the lineageos zip
2. Find system.img (special case it is system.new.dat.br, tell me if it is)
3. Execute the aforementioned command
Click to expand...
Click to collapse
it is system.new.dat.br
Bonpotiron said:
LineageOS 18.1 really? I'm confused because the instructions on Lineage website say that the last nightly built is LineageOS 17.1 – [ Android 10.0.0 (Android 10) ] of 2021-10-06
Click to expand...
Click to collapse
This is the latest unofficial version from this topic: https://forum.xda-developers.com/t/rom-unofficial-lineageos-18-1-for-castor-castor_windy.4261491/
It is stable on this
Bonpotiron said:
it is system.new.dat.br
Click to expand...
Click to collapse
Ok and what happens if you 'fastboot boot twrp.img'?
Try this
If it gets into twrp immediately wipe and flash lineageos
@LR7875 the device enters recovery in a hidden way, as the display stays black.
I managed to install Lineage 17.0 with these instructions: https://forum.xda-developers.com/t/...for-castor-castor_windy.4261491/post-85738643
Boy, that was tricky !
Seems like the graphics driver of the recovery is broken.