Hi All,
I had Lineage 14.1 ROM on my Nexus 9.
I wanted to use Xposed framework for a project which does not work with 7.0+.
Hence I want to go back to 6.0 ROM.
I have tried 3 different 6.0 ROMs so far, all of which resulted in bootloop.
Just now I flashed 14.1 Lineage OS again and it boots up just fine.
Can anybody tell me what I'm missing here? I'm using TWRP recovery 3.1.1-0
pikudroid said:
Hi All,
I had Lineage 14.1 ROM on my Nexus 9.
I wanted to use Xposed framework for a project which does not work with 7.0+.
Hence I want to go back to 6.0 ROM.
I have tried 3 different 6.0 ROMs so far, all of which resulted in bootloop.
Just now I flashed 14.1 Lineage OS again and it boots up just fine.
Can anybody tell me what I'm missing here? I'm using TWRP recovery 3.1.1-0
Click to expand...
Click to collapse
Gotta wipe everything, including internal storage, factory reset. Also the vendor and bootloader for 6.0
madbat99 said:
Also the vendor and bootloader for 6.0
Click to expand...
Click to collapse
Can you elaborate on that? What exactly do you mean?
pikudroid said:
Can you elaborate on that? What exactly do you mean?
Click to expand...
Click to collapse
If you are going back to 6 with a custom ROM, you also need to flash the vendor image from that version of Android as well. Just download the factory image of 6.0 from Google's factory image page, then extract the zip, then extract the zip that's in there. In those files will be a vendor.img. put it in the tablet somewhere you can find it (like download folder) or on USB stick or wherever you're putting the ROM zip you're flashing. When flashing ROM and gapps also install vendor image to vendor partition. TWRP has the option to flash image files.
This is something needed on 64 bit Android devices.
Bootloader has to be installed with fastboot, but come to think, I don't think you have to downgrade bootloader. Pretty sure having the newer bootloader is fine. Vendor should match the version of Android you're using though.
madbat99 said:
If you are going back to 6 with a custom ROM, you also need to flash the vendor image from that version of Android as well. Just download the factory image of 6.0 from Google's factory image page, then extract the zip, then extract the zip that's in there. In those files will be a vendor.img. put it in the tablet somewhere you can find it (like download folder) or on USB stick or wherever you're putting the ROM zip you're flashing. When flashing ROM and gapps also install vendor image to vendor partition. TWRP has the option to flash image files.
This is something needed on 64 bit Android devices.
Bootloader has to be installed with fastboot, but come to think, I don't think you have to downgrade bootloader. Pretty sure having the newer bootloader is fine. Vendor should match the version of Android you're using though.
Click to expand...
Click to collapse
Thanks a lot. Flashing vendor.img worked for me.
pikudroid said:
Thanks a lot. Flashing vendor.img worked for me.
Click to expand...
Click to collapse
Glad it helped. Hope I didn't over-explain, lol
Related
I have uploaded the latest androd 6.0.1 MMB29K.
I have twrp installed - the latest I believe.
super su - 2.46 pro
I installed the ElementX kernel - can't remember witch page I followed to root my nexus 9. but it suggested this.
Now I can't set a pin for my sudoers
tried uninstalling and reinstalling no luck.
I have ex kernel manager and it says there is a new version available, but I need superSU 2.61 - witch means the new beta version.
Looking at the thread http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
looks like I have refrash a stock boot
"
If you are coming from any SuperSU install in /system, you must re-flash the stock system partition contents prior to installing this.
"
how do I do this ?
What does the new kernel give me ?
Any idea on why my supersu doesn't let me use pin codes ?
KeyzerSuze said:
I have uploaded the latest androd 6.0.1 MMB29K.
I have twrp installed - the latest I believe.
looks like I have reflash a stock boot
"
If you are coming from any SuperSU install in /system, you must re-flash the stock system partition contents prior to installing this.
"
how do I do this ?
What does the new kernel give me ?
Any idea on why my supersu doesn't let me use pin codes ?
Click to expand...
Click to collapse
Latest TWRP for Nexus 9 is twrp-2.8.7.1-flounder
Get the latest factory image and unzip the contents a few times then use fastboot to flash both boot.img and system.img.
From TWRP Flash SuperSU-v2.62-3 first and then the latest ElemetalX kernel (if you want it, not needed for root).
Never used pin codes with supersu, so don't know about that.
corkiejp said:
Latest TWRP for Nexus 9 is twrp-2.8.7.1-flounder
Get the latest factory image and unzip the contents a few times then use fastboot to flash both boot.img and system.img.
The latest SuperSU-v2.62-3
From TWRP Flash that first and then the latest ElemetalX kernel (if you want it, not needed for root).
Never used pin codes with supersu, so don't know about that.
Click to expand...
Click to collapse
Flashing vendor.img is a good idea as well, just to make sure everything is synced up.
I'm I going to have to reinstall all my apps again ?
Sent from my Nexus 6P using Tapatalk
KeyzerSuze said:
I'm I going to have to reinstall all my apps again ?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Flashing just boot.img, system.img and vendor.img, will not wipe data.
And leaves data untouched, so won't need to reinstall apps again. Just don't flash the full factory image.
(Note: Flashing the full factory image can also be done without wiping data)
Thanks did it and all good.
Sent from my Nexus 6P using Tapatalk
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?
So, I've been trying to flash CyanogenMod 12.1, since I'm still stuck on EMUI 3.1, because I can't flash OTA updates (I've tried everything, dload method, and yes I have unrooted and used the stock recovery)
Every time I try to flash a ROM via TWRP it turns off for a second and then boots back to TWRP starting screen. Also, when I boot my phone the boot animation's Honor H is red for some reason.
Thanks in advance!
Fonku said:
So, I've been trying to flash CyanogenMod 12.1, since I'm still stuck on EMUI 3.1, because I can't flash OTA updates (I've tried everything, dload method, and yes I have unrooted and used the stock recovery)
Every time I try to flash a ROM via TWRP it turns off for a second and then boots back to TWRP starting screen. Also, when I boot my phone the boot animation's Honor H is red for some reason.
Thanks in advance!
Click to expand...
Click to collapse
Are you sure you have the right boot.img and recovery.img?
Usually that symptoms are due to messed partitions.
Did you flash current img files or did you got them from a different rom version?
zinko_pt said:
Are you sure you have the right boot.img and recovery.img?
Usually that symptoms are due to messed partitions.
Did you flash current img files or did you got them from a different rom version?
Click to expand...
Click to collapse
Well, actually I once bricked my phone and had to restore through a TWRP backup, that only had the System and Boot partitions and it was the B130 version when I had B140, but it worked. So, do I need to completely flash everything or can I just pick up some files from somewhere?
Fonku said:
Well, actually I once bricked my phone and had to restore through a TWRP backup, that only had the System and Boot partitions and it was the B130 version when I had B140, but it worked. So, do I need to completely flash everything or can I just pick up some files from somewhere?
Click to expand...
Click to collapse
No, you need to have all the files from the same version.
Flash boot, recovery, cust and system.
zinko_pt said:
No, you need to have all the files from the same version.
Flash boot, recovery, cust and system.
Click to expand...
Click to collapse
So, is there a FULL KIW-L21C432B140 restore packet somewhere?
Thanks for your help!
Fonku said:
So, is there a FULL KIW-L21C432B140 restore packet somewhere?
Thanks for your help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288
You can use B130 as it is also Lollipop. But all the img from the same rom. You can update to B350 manually after, but first you need a stable rom working.
Let us know man if you fixed your phone. So if not, we can give firther recommendations.
Sent from my Galaxy Tab 3 using XDA Labs
Hello,
I just managed to generate TWRP recovery for S912 Android 9 version, you can install the official TWRP app to flash with in the ROM.
But after reboot the ROM goes back to stock recovery, so for now i am installing everytime i need to use recovery, unless i am able to find a permanent solution.
Link to TWRP
Suggestions welcome if you have for keeping the recovery persistent.
Regards
I was able to keep it persistent but if I go to install all I get for folder names is a mess. Using Superceleron's generic SC normal pie rom. Appeared to install magisk but magisk manager didn't see it and I lost superuser access so I had to reflash rom. I hope you or others can pick up on TWRP for this. Unfortunately I don't have the knowledge so can only test. Liking the Superceleron rom on my T95Z(2/16) much better than poison or stock (so far... still testing...). Glad to see these old devices getting some new love. Hopefully it will continue.
rickpub said:
I was able to keep it persistent but if I go to install all I get for folder names is a mess. Using Superceleron's generic SC normal pie rom. Appeared to install magisk but magisk manager didn't see it and I lost superuser access so I had to reflash rom. I hope you or others can pick up on TWRP for this. Unfortunately I don't have the knowledge so can only test. Liking the Superceleron rom on my T95Z(2/16) much better than poison or stock (so far... still testing...). Glad to see these old devices getting some new love. Hopefully it will continue.
Click to expand...
Click to collapse
Jumbled charcters is because the ROM is encrypted and this recoveery is not able to decrypt it.
Bumping this, going to test this on Aidans rom
Update: could not confirm if it works it looks like the reset button is not mapped on Aidans rom. The weird thing is it works if I use the USB burn tool but not when I do a regular boot.
Doctorbeefy said:
Update: could not confirm if it works it looks like the reset button is not mapped on Aidans rom. The weird thing is it works if I use the USB burn tool but not when I do a regular boot.
Click to expand...
Click to collapse
Do you mean we can flash using amlogic usb burning tool, I am now struggling to install this ROM on khadas 64 android 9 ROM by Highway star
Hi @eagledipesh!
I managed to install your TWRP successfully on Aidan's ROM, thank you very much!
First I unpacked the Aidan' ROM with the Customizatio Tool, then I replaced the original recovery with your TWRP. I repackaged the ROM and flashed it with the AMLogic USB Burning Tool.
With TWRP and I did a full backup and I was also able to restore without errors. However, after restoring and booting the system, it gets stuck on AndroidTV splash screen.
Maybe I need to port the correct TWRP, because when unpacking your recovery with AIK, I saw in one of the files that the model is gxm_q201_2g, but my Android Box is gxm_q200_3g.
1. What base TWRP did you use to create your TWRP?
2. I tried porting TWRP myself from Aidan's ROM recovery, I can even get into recovery, but the letters are all scrambled. Can you help me make my own port?
ulissesemuman said:
Hi @eagledipesh!
I managed to install your TWRP successfully on Aidan's ROM, thank you very much!
First I unpacked the Aidan' ROM with the Customizatio Tool, then I replaced the original recovery with your TWRP. I repackaged the ROM and flashed it with the AMLogic USB Burning Tool.
With TWRP and I did a full backup and I was also able to restore without errors. However, after restoring and booting the system, it gets stuck on AndroidTV splash screen.
Maybe I need to port the correct TWRP, because when unpacking your recovery with AIK, I saw in one of the files that the model is gxm_q201_2g, but my Android Box is gxm_q200_3g.
1. What base TWRP did you use to create your TWRP?
2. I tried porting TWRP myself from Aidan's ROM recovery, I can even get into recovery, but the letters are all scrambled. Can you help me make my own port?
Click to expand...
Click to collapse
I used one of the twrp port guides, twrp was stock one, with stock recovery extracted from initial Android 9 builds by Highway star'
You can use the official twrp as base and then recovery from any of rom for your device
eagledipesh said:
I used one of the twrp port guides, twrp was stock one, with stock recovery extracted from initial Android 9 builds by Highway star'
You can use the official twrp as base and then recovery from any of rom for your device
Click to expand...
Click to collapse
Are you talking about the Wiko Highway Star? Any special reason for using this ROM as a base? How do I know which version of TWRP to use?
i create a twrp for my amlogic T972 but can't boot into it, don't know where to start fix bug
Can you help me build a twrp for this? Or can you teach me do that? Thank you @eagledipesh
Is there now a working TWRP for the Yoka KB2 Pro 3gb on Android 9.0? I would prefer to have an img file, but if there is really no other way, I would also take the zip version.
Thank you and best regards
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.