Disclaimer:
Your warranty may be void
I by no means take responsibility if you brick your device. I have not tested my methodology nor am I sure of the firmware differences between releases.
I noticed that when flashing Oxygen 2.2.0 new firmware was released. Some people may have need for it if they are on a custom ROM and don't feel like flashing stock and then restoring from a backup.
THIS IS NOT FLASHABLE!!!
INSTALLATION
1. Extract the archive
2. Copy the firmware folder to the highest directory (/)
3. Replace the files
4. Reboot
5. Pray
Immediate feedback is appreciated from those still using the firmware from older versions. Uploading firmware from previous versions is appreciated as well. In the future I will try to make a flashable image.
Download:
https://drive.google.com/file/d/0B7CLqaEGT92ATWVBbllvakh5eHM/view?usp=docslist_api
Reserved
I don't know what are you trying to do, confused.
http://forum.xda-developers.com/oneplus-x/general/rom-mirrors-official-oxygen-os-rom-ota-t3301797
ChavitoArg said:
I don't know what are you trying to do, confused.
http://forum.xda-developers.com/oneplus-x/general/rom-mirrors-official-oxygen-os-rom-ota-t3301797
Click to expand...
Click to collapse
I'm providing new firmware in place of the entire ROM. People may not want to download the entire ROM.
RJDTWO said:
I'm providing new firmware in place of the entire ROM. People may not want to download the entire ROM.
Click to expand...
Click to collapse
What do you mean with firmware? Isn't the ROM the firmware?
sydeu said:
What do you mean with firmware? Isn't the ROM the firmware?
Click to expand...
Click to collapse
Firmware is the basis from where hardware can interact with software. The entire ROM isn't in and of itself firmware as it includes an operating system (in the case of Oxygen, Android). Essentially I'm providing the libraries from /firmware which are specific to the device itself.
RJDTWO said:
Firmware is the basis from where hardware can interact with software. The entire ROM isn't in and of itself firmware as it includes an operating system (in the case of Oxygen, Android). Essentially I'm providing the libraries from /firmware which are specific to the device itself.
Click to expand...
Click to collapse
Is this useful if you are on cm12.1 /cm13?
sydeu said:
Is this useful if you are on cm12.1 /cm13?
Click to expand...
Click to collapse
That's the thing; I'm not entirely sure. I believe the only updated binaries were for the the camera. If you've flashed 2.2.0 you should already have them. I wouldn't attempt it unless you're familiar with fastboot and reflashing the stock ROM as a whole that way. It should help with the camera, but no guarantees.
RJDTWO said:
That's the thing; I'm not entirely sure. I believe the only updated binaries were for the the camera. If you've flashed 2.2.0 you should already have them. I wouldn't attempt it unless you're familiar with fastboot and reflashing the stock ROM as a whole that way. It should help with the camera, but no guarantees.
Click to expand...
Click to collapse
Haven't flashed 2.2.0. Doesn't have access to my pc for 10 days so I'll have to wait u til then before I play around too much.
I think cm has updated with the oos 2.2.0 things though.
sydeu said:
Haven't flashed 2.2.0. Doesn't have access to my pc for 10 days so I'll have to wait u til then before I play around too much.
I think cm has updated with the oos 2.2.0 things though.
Click to expand...
Click to collapse
Good to know. So in short, don't attempt this unless your ROM has yet to include it.
I did just test it though and it works. There's a definitive difference between the camera firmware used
...and that was on CM 13
Related
Just FYI: https://forums.oneplus.net/threads/cm-11s-44s-ota-is-out.173057/
...didn't see the typical insta-thread here, heh.
Greetings friends,
Happy Weekend! Thanks to our buds at Cyanogen, a new OTA will be rolling out to your phones starting today. This new release includes some new fixes such as a resolved SSLv3 POODLE security issue and updated touchscreen firmware.
The OTA will be released slowly and therefore some regions might receive it before others. Once you’ve received your OTA please let us know what you think! Any further issues you may find can also be reported directly to Cyanogen.
Here’s a comprehensive list of changes you’ll find in this update:
Fixed issues with memory causing screen artifacts
Fixed issues with random reboots and instability
Fixed issues with WiFi and modem crashes
Fixed issues with Filesystem
Fixed issues with “black bar”
Fixed issues with persist partition corruption
Fixed issues with AT&T VoLTE
Click to expand...
Click to collapse
Edit: Forgot to mention... this includes a new modem, I know people are always interested in that.
As a side note, I've been running the build as part of an early access test for a few days now... has been extremely solid for me.
Edit again: LINKS!
• Link to the OTA: http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
MD5: 684bc3eb256f06a912505628551cba24
Super mini guide: As long as your system is stock, flash away in stock or custom recovery. I always re-flash the SuperSU zip immediately following, YMMV.
• Link to the OTA with a modified script (by @gianton) for installing regardless of system changes: https://mega.co.nz/#!EdBQ1Y4C!P85kyvVp1iR_I4IiuLKPxGBqskE3fueWe0OGAFidGEg
MD5: 3b5729b07200c0e53a02f6b1225fc79c
FAQ (since people are allergic to reading and searching):
1. ZOMG WHY NO WIFI AFTER OTA?: Because you used a custom kernel and didn't clean up your system files properly. Either follow that kernel threads instructions for OTA-prep'ing or flash back to that kernel.
2. I don't run CM 11S but I can totally flash this CM11S update, right?: No. If you want to flash the 44S OTA update, get yourself to CM11S 38R.
Zip file?
Inviato dal mio OnePlus One
Lolli......Oh wait <.< (Joke post)
Should have grab the zip.
hunter0389 said:
Should have grab the zip.
Click to expand...
Click to collapse
I did, but... as someone that hasn't tested for CM before, I'm not entirely clear on their position of a tester sharing. I wouldn't want to piss anyone off unnecessarily.
dmarden said:
I did, but... as someone that hasn't tested for CM before, I'm not entirely clear on their position of a tester sharing. I wouldn't want to piss anyone off unnecessarily.
Click to expand...
Click to collapse
I understand. Since the OTA is out, would you mind sharing the zip?
Got this link off Android Police article....
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
blkhwkz said:
Got this link off Android Police article....
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
Click to expand...
Click to collapse
Great, that makes me feel much better about posting it. I added your link to the OP.
If I update this new build will it break my root ?
vikramdhani said:
If I update this new build will it break my root ?
Click to expand...
Click to collapse
Not in any meaningful way. Just have the SuperSU zip on your phone and flash it after you flash the OTA.
going to be constantly refreshing for OTA. Currently on stock, unrooted, and planning on leaving it that way for now, can the zip be flashed in stock recovery?
dmarden said:
Great, that makes me feel much better about posting it. I added your link to the OP.
Click to expand...
Click to collapse
can i install with twrp?
zipper for TWRP?
mobbarley said:
going to be constantly refreshing for OTA. Currently on stock, unrooted, and planning on leaving it that way for now, can the zip be flashed in stock recovery?
Click to expand...
Click to collapse
I flashed it in TWRP, so I assume stock recovery is also fine.
nicola1989 said:
can i install with twrp?
Click to expand...
Click to collapse
Yes.
mittimus said:
zipper for TWRP?
Click to expand...
Click to collapse
The one in the OP is identical to the one I received as a tester and I flashed it in TWRP.
How do I keep root?
Sent from my A0001 using XDA Free mobile app
Crinkypops said:
How do I keep root?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I just keep the SuperSU zip on my phone and flash it immediately after the OTA whenever they come out.
dmarden said:
I just keep the SuperSU zip on my phone and flash it immediately after the OTA whenever they come out.
Click to expand...
Click to collapse
Perfect. Flashing now through TWRP.
Sent from my A0001 using XDA Free mobile app
mobbarley said:
going to be constantly refreshing for OTA. Currently on stock, unrooted, and planning on leaving it that way for now, can the zip be flashed in stock recovery?
Click to expand...
Click to collapse
If it contains "signed" it is flashable by stock too
Flashing the ZIP from AP did not work....going to reboot and try again.
reinert012 said:
Flashing the ZIP from AP did not work....going to reboot and try again.
Click to expand...
Click to collapse
Please also elaborate on "did not work" if it fails again... it's identical to the test build ZIP I received which flashed fine. Did you make any system modifications (if so, those will need to be reverted probably)?
OK guys. Before you bite my head off, I'm an experienced ROM flasher and a junior ROM developer....I've been rooting every phone/tablet I get, I know how to use adb/fastboot and even made a personal stock ROM....like I said....junior not an expert lol....I currently have a nexus 5,6,7(2013). Now, I will be getting my new nexus 6p gold 32gig tomorrow (Tuesday). I have read about the new /vendor partition. Since I ha e never had to deal with that, I need your help. Any info about it before I root it tomorrow would be much appreciated!!!
From my understanding is that it contains the propitiatory drivers, libraries, and such, but what I found out creating my ROM is that it does not contain all of them. If you decide to create your own ROM from AOSP, then I can help you with it.
dl200010 said:
From my understanding is that it contains the propitiatory drivers, libraries, and such, but what I found out creating my ROM is that it does not contain all of them. If you decide to create your own ROM from AOSP, then I can help you with it.
Click to expand...
Click to collapse
So, flashing ROMs and such....I don't have to mess with vendor?
Just if there is a newer version out. I think now u can flash the vendor. Img via twrp 3.0 if I'm not wrong
jamescable said:
So, flashing ROMs and such....I don't have to mess with vendor?
Click to expand...
Click to collapse
Depending on the ROM, sometimes you do. If you have previously been using a Layers theme for example, you'd need to flash the vendor partition when flashing a new ROM otherwise the data well carry across (Layers resides in the vendor partition).
Heisenberg said:
Depending on the ROM, sometimes you do. If you have previously been using a Layers theme for example, you'd need to flash the vendor partition when flashing a new ROM otherwise the data well carry across (Layers resides in the vendor partition).
Click to expand...
Click to collapse
Is it correct that twrp does this job now in 3.0?haven't tried for myself yet
pa.pn2 said:
Is it correct that twrp does this job now in 3.0?haven't tried for myself yet
Click to expand...
Click to collapse
From what I've seen posted, yes. I haven't tried it myself though.
Heisenberg said:
From what I've seen posted, yes. I haven't tried it myself though.
Click to expand...
Click to collapse
I guess you are talking about flashing the Vendor image itself - not a flashable version of the vendor ? (probably a dumb question but I thought clarification for me and any other who might be confused couldnt hurt?)
jamescable said:
So, flashing ROMs and such....I don't have to mess with vendor?
Click to expand...
Click to collapse
Only time I flash the vendor is when updating to the latest of the ROM I use. Also going to the latest vendor factory img from google in the process. And like the other guy said when going from a layers ROM to anything else.
mocsab said:
I guess you are talking about flashing the Vendor image itself - not a flashable version of the vendor ? (probably a dumb question but I thought clarification for me and any other who might be confused couldnt hurt?)
Click to expand...
Click to collapse
Yes that's right.
as of 3.0.0-0 you can flash vendor and system images in twrp
More details in the Verizon Note 4 forum here.
XDA:DevDB Information
EFIDroid, Kernel for the T-Mobile Samsung Galaxy Note 4
Contributors
abraha2d, m11kkaa
Source Code: https://github.com/efidroid
Kernel Special Features: UEFI, MultiBoot
Version Information
Status: Beta
Current Beta Version: 0.1
Beta Release Date: 2017-03-18
Created 2017-03-20
Last Updated 2017-03-31
THIS IS INCREDIBLE!! Greatest thing since sliced bread where is the donation link this an amazing piece of development 2nd lvl bootloader f yaaaa!!
vegoja said:
THIS IS INCREDIBLE!! Greatest thing since sliced bread where is the donation link this an amazing piece of development 2nd lvl bootloader f yaaaa!!
Click to expand...
Click to collapse
Believe me, I didn't do much work. You can donate to @m11kkaa, though. He's the developer of EFIDroid (if you didn't already know that...). I believe he has a donation link in his profile...
Sent from my Samsung Galaxy Note 4 using XDA Labs
This is great but is there a way to uninstall it (if necessary) and get back to the primary ROM (stock or Lineage OS) without losing data?
tried to do a bit of light research and couldn't find what's different between this and other preexisting multiboot solutions. I've been using Dual Boot Patcher for sometime without issues. Is this somehow better? and if so, how?
Mtotallywired said:
tried to do a bit of light research and couldn't find what's different between this and other preexisting multiboot solutions. I've been using Dual Boot Patcher for sometime without issues. Is this somehow better? and if so, how?
Click to expand...
Click to collapse
EFIDroid is what you would call a "second-stage bootloader". The main advantage over Dual Boot Patcher (at least for me) is that you no longer have to patch zip files before installing. Also, EFIDroid is more than just a multi-boot solution. Quoting @m11kkaa:
efidroid tries to focus on simplicity, and doesn't require any kernel modifications etc.
in general: well having such a powerful bootloader in your boot stage gives you lots of possibilities, like multiboot, replacements/additions for kernels/ramdisk/cmdline.
This project has a lot more potential than what's currently implemented. i.e. you can give samsung devices fastboot and sony devices a standalone recovery. Also you can natively boot GNU GRUB if you're into booting linux kernel's the desktop way.
Click to expand...
Click to collapse
The two solutions are similar enough that you can migrate your setup from Dual Boot Patcher to EFIDroid without losing any data. I'll try to post a guide later this week.
I was I under the impression dual boot required multiple ROMs running the same kernel... If that is the case a huge advantage efi has is each ROM having their own boot img. I'm currently running 3 ROMs a lollipop a marshmallow and of course a nougat. I really just wanted to see all 3 latest android os running flawlessly on 1 device. And I did just that hats off to the developer for this.
baharvey7817 said:
This is great but is there a way to uninstall it (if necessary) and get back to the primary ROM (stock or Lineage OS) without losing data?
Click to expand...
Click to collapse
There's an uninstall button in the app. Or, you could just flash the original boot.img via TWRP (basically what the uninstall button does).
I'm a noob...What is this? Where do I need to go to learn about why I would want this...Please explain lol
mlock420 said:
I'm a noob...What is this? Where do I need to go to learn about why I would want this...Please explain lol
Click to expand...
Click to collapse
you can look at their website, and then decide if you want this level of control over your phone.
http://efidroid.org/
Thanks for bringing us this tool. One thing I can't figure out...how do we Odin a different bootloader? I have DOK2 loaded now, and want to put Dr. Ketan's on the phone. The sub instructions say to Odin the BL and CP, as the ROM is generally generic. There us also a datafix and an essential fix that needs to be applied. Doing all of that is easy, but how do I keep two separate bootloaders (LP and MM) totally separate? If I flash a LP over a MM, my camera breaks, and if I flash a MM over LP, WiFi breaks. And I'm not talking about dirty flashes, a full system, data, and cache wipe 3x. Only Odin back to the base ROM keeps my phone happy.
1freedude said:
Thanks for bringing us this tool. One thing I can't figure out...how do we Odin a different bootloader? I have DOK2 loaded now, and want to put Dr. Ketan's on the phone. The sub instructions say to Odin the BL and CP, as the ROM is generally generic. There us also a datafix and an essential fix that needs to be applied. Doing all of that is easy, but how do I keep two separate bootloaders (LP and MM) totally separate? If I flash a LP over a MM, my camera breaks, and if I flash a MM over LP, WiFi breaks. And I'm not talking about dirty flashes, a full system, data, and cache wipe 3x. Only Odin back to the base ROM keeps my phone happy.
Click to expand...
Click to collapse
There's no way to have two different bootloaders. EFIDroid comes between the bootloader and the boot.img, so it has no control over the bootloader.
EDIT: EFIDroid may be able to emulate the behavior of another bootloader... you would have to ask @m11kkaa for details...
Where can I download this for T-mobile ??
Sent from my SM-N9300 using Tapatalk
CousinMikeyP said:
Where can I download this for T-mobile ??
Sent from my SM-N9300 using Tapatalk
Click to expand...
Click to collapse
Here is the LINK. You can see more info HERE
I downloaded and started up the EFIdroid unofficial apk but got the following message:
=====================================
Error
Can't load device info. Please check your connection.
/data/user/0/org.efidroid.efidroidmanager.debug/files/devices.json (No such file or directory)
override ota server try again
===============================================
Could you please explain what's going on? Seems that this version is different from the one i downloaded in March. Could it be that it's not getting root access? What can I do to get around this error?
baharvey7817 said:
I downloaded and started up the EFIdroid unofficial apk but got the following message:
=====================================
Error
Can't load device info. Please check your connection.
/data/user/0/org.efidroid.efidroidmanager.debug/files/devices.json (No such file or directory)
override ota server try again
===============================================
Could you please explain what's going on? Seems that this version is different from the one i downloaded in March. Could it be that it's not getting root access? What can I do to get around this error?
Click to expand...
Click to collapse
I will have to look into it... The EFIDroid app error messages are not exactly the most helpful kind. (Good thing the app is being phased out soon). That particular error message could mean many things, but most likely it's a connection issue. We will continue this in Slack.
Will this work on tw 7.0 if i was porting a rom. Also why wont aosp kernel work on tw.. i always thought tw was aosp with skin..
Go to back to the link posted above where you got the unofficial apk and go to post #83. The OP posted an apk there that works fine on our phone.
baharvey7817 said:
I downloaded and started up the EFIdroid unofficial apk but got the following message:
=====================================
Error
Can't load device info. Please check your connection.
/data/user/0/org.efidroid.efidroidmanager.debug/files/devices.json (No such file or directory)
override ota server try again
===============================================
Could you please explain what's going on? Seems that this version is different from the one i downloaded in March. Could it be that it's not getting root access? What can I do to get around this error?
Click to expand...
Click to collapse
RaySCLA said:
Go to back to the link posted above where you got the unofficial apk and go to post #83. The OP posted an apk there that works fine on our phone.
Click to expand...
Click to collapse
Tried what you suggested but it didn't work either. So, I chose the 'nuclear option': I wiped the phone completely then reinstalled the stock Marshmallow ROM. using Odin. After that i installed TWRP v3.0.2 (trltetmo) and Supersu v2.79 as well as Busybox v1.26. Only then was I able to install EFIDroid successfully. Now, I'm able to boot the stock rom as well as Resurrection Remix.
It seems that if your going to install EFIDroid you must have the phone rooted using SuperSU. Using Magisk to root your phone instead of SuperSu won't work (at least it didn't work in my case).
lowkeyst4tus said:
Will this work on tw 7.0 if i was porting a rom. Also why wont aosp kernel work on tw.. i always thought tw was aosp with skin..
Click to expand...
Click to collapse
This should work anywhere, regardless of ROM... But btw, it's a stretch to say TW is just a skin on top of AOSP. In fact, TW is probably the farthest you can get from AOSP... There's a lot of significant differences that make AOSP kernels incompatible with TW ROMs...
Hi all, is it worth waiting for the official Oreo update before unlocking?
Will it be a advantage to flash after taking the update, or doesn't it really matter?
I've been putting it off for a while but I'm starting to get board of waiting.
Have you read the forum regarding people who are having various issues, oreo is in beta stage at best, so if you want functionality of your phone as it is, then either wait as I am or consider a nougat rom.
Regards Ray
What is the rush? Is there a problem with your device as it is? Is there some feature of Oreo that can't live without?
Unless you understand the implications of rooting/romming this device, ALL of them including potential issues going back to stock and relocking the bootloader, just stay stock and wait... If you did understand all the implications than you probably wouldn't be asking this question.
Till Motorola releases the oreo update they won't release the kernel source for this device . And Kernel source would be important for stable rom.
I had this feeling too. I really, really, wanted to be on Oreo because of theming and the new features. I unlocked my phone, installed TWRP, failed, and bricked it. I was able to recover and, well, no more ROMing for me. I'd wait for the stable Oreo ROM. It's worth the wait.
reCoded said:
I had this feeling too. I really, really, wanted to be on Oreo because of theming and the new features. I unlocked my phone, installed TWRP, failed, and bricked it. I was able to recover and, well, no more ROMing for me. I'd wait for the stable Oreo ROM. It's worth the wait.
Click to expand...
Click to collapse
You are a senior member how you failed?
Flashing phones isn't a worry for me, I've done every phone I've had.
All I was asking is, is there any advantage in getting the new bootloader that will come with the stock Oreo.
ugupta100 said:
You are a senior member how you failed?
Click to expand...
Click to collapse
Just because I'm a senior member doesn't mean I know how to do everything. Jumping from 32-bit ROMs to 64-bit ROMs is much different than with a 32-bit ROM. I can easily install a 32-bit ROM but installing 64-bit TWRP requires extra stuff which I didn't do, which bricked my device.
reCoded said:
Just because I'm a senior member doesn't mean I know how to do everything. Jumping from 32-bit ROMs to 64-bit ROMs is much different than with a 32-bit ROM. I can easily install a 32-bit ROM but installing 64-bit TWRP requires extra stuff which I didn't do, which bricked my device.
Click to expand...
Click to collapse
Thanks for the warning, I'll keep that in mind.
reCoded said:
Just because I'm a senior member doesn't mean I know how to do everything. Jumping from 32-bit ROMs to 64-bit ROMs is much different than with a 32-bit ROM. I can easily install a 32-bit ROM but installing 64-bit TWRP requires extra stuff which I didn't do, which bricked my device.
Click to expand...
Click to collapse
Can you expand on this a little?
I thought it was just a matter of flashing the newest version of twrp with 64bit support and finding a 64bit ROM you liked?
eemgee said:
Can you expand on this a little?
I thought it was just a matter of flashing the newest version of twrp with 64bit support and finding a 64bit ROM you liked?
Click to expand...
Click to collapse
It doesn't work like that since the stock software is 32-bit and the TWRP version is 64-bit. You have to flash a modified boot.bin file (or something like that) to make the software compatible with 64-bit TWRP. I'm not too sure what to do since I couldn't find any tutorials.
reCoded said:
It doesn't work like that since the stock software is 32-bit and the TWRP version is 64-bit. You have to flash a modified boot.bin file (or something like that) to make the software compatible with 64-bit TWRP. I'm not too sure what to do since I couldn't find any tutorials.
Click to expand...
Click to collapse
Well they kept that quiet! I had a look around and wouldn't see anything either.
1) Is there a list of available Roms for this tablet?
2) If there isn't a list of roms, perhaps people could post the ones they have and I can make a new post containing links to roms that I will maintain as long as people let me know when/if links die.
*Old roms are just fine, just as long as they are unique.
3) Are there any amazon stock roms available I can flash with TWRP?
*I didn't know if you can somehow flash an amazon stock rom with it and then just customize it, pre root it? then make an image of it myself with TWRP.
Wishful thinking, is it that simple?
Also if there are any knowlageble people on any of this subject we should make an IRC channel on libera.chat.. I can start if if there is interest.
Thanks,
likwidchz said:
1) Is there a list of available Roms for this tablet?
2) If there isn't a list of roms, perhaps people could post the ones they have and I can make a new post containing links to roms that I will maintain as long as people let me know when/if links die.
*Old roms are just fine, just as long as they are unique.
3) Are there any amazon stock roms available I can flash with TWRP?
*I didn't know if you can somehow flash an amazon stock rom with it and then just customize it, pre root it? then make an image of it myself with TWRP.
Wishful thinking, is it that simple?
Also if there are any knowlageble people on any of this subject we should make an IRC channel on libera.chat.. I can start if if there is interest.
Thanks,
Click to expand...
Click to collapse
1. return to stock recovery
2. and flash it from adb sideload ( stockrom )
789mod said:
1. return to stock recovery
2. and flash it from adb sideload ( stockrom )
Click to expand...
Click to collapse
Thanks, yeah... I was looking more for a method to flash via twrp and not use anything stock other than the OS image. There were a couple releases of two different roms that were pre rooted stock. I didn't know how popular those were.
I'm just running into weird issues. I have an app I'm writing in processing.org for andriod and the frame rates I'm getting varies so much on different roms. The rom i'm using is one of these
lineage-12.1-20200505-UNOFFICIAL-suez
lineage-14.1-20190926-UNOFFICIAL-suez
Super old, but honestly if that's what I get, that's what I get.
I tried this too
5620_Fire_HD_10_pre_rooted_optimized_stock_rom-signed
Based on how all this stuff works, I didn't know if I had the ability to download the latest amazon image and make my own flashable rom to "try out" vs be in a situation where I would update it all and then not able to go back. I'd rather not.
Thanks for the response.
likwidchz said:
Thanks, yeah... I was looking more for a method to flash via twrp and not use anything stock other than the OS image. There were a couple releases of two different roms that were pre rooted stock. I didn't know how popular those were.
I'm just running into weird issues. I have an app I'm writing in processing.org for andriod and the frame rates I'm getting varies so much on different roms. The rom i'm using is one of these
lineage-12.1-20200505-UNOFFICIAL-suez
lineage-14.1-20190926-UNOFFICIAL-suez
Super old, but honestly if that's what I get, that's what I get.
I tried this too
5620_Fire_HD_10_pre_rooted_optimized_stock_rom-signed
Based on how all this stuff works, I didn't know if I had the ability to download the latest amazon image and make my own flashable rom to "try out" vs be in a situation where I would update it all and then not able to go back. I'd rather not.
Thanks for the response.
Click to expand...
Click to collapse
are you want stock rom and root it or what ?
try stock rom and root it mgisk from twrp
I would like to try all the available roms to figure out which one works the best with the app I'm writing.
But I only want to try roms flashable with TWRP.
Best rom for this device is
5.1.1
789mod said:
Best rom for this device is
5.1.1
Click to expand...
Click to collapse
Have a file name of that rom so I can google sleuth and give that a try?
You know I was tempted to make a post that just has a link to all the roms available.
Is found here 12.1 Cyanogen
Is that this one? lineage-12.1-20200505-UNOFFICIAL-suez.zip