Asking questions like that is liable to piss someone off. Asking ETA's is not just in bad taste it's prohibited on XDA. Be thankful for what we've got.When do you plan to release this rom based on Android 12 ? Or even A13
Asking questions like that is liable to piss someone off. Asking ETA's is not just in bad taste it's prohibited on XDA. Be thankful for what we've got.When do you plan to release this rom based on Android 12 ? Or even A13
It's just a question, calm your pants. I have been using XDA a long time, far longer than this account has existed, I have donated to the dev of this rom and I have been releasing my own unofficial build of a romAsking questions like that is liable to piss someone off. Asking ETA's is not just in bad taste it's prohibited on XDA. Be thankful for what we've got.
I've been on XDA since honeycomb. Forgive me, I didn't realize I was in the presence of an XDA legend to whom the rules clearly do not apply. Since there isn't a written or unwritten rule about what comments can or cannot be replied to, I will continue taking my liberty, but thank you for your....inputIt's just a question, calm your pants. I have been using XDA a long time, far longer than this account has existed, I have donated to the dev of this rom and I have been releasing my own unofficial build of a rom
the dev has previously stated their intentions to update so I was just hoping they could share a bit more information.
Also, the dev saw my question and ignored it, I chose to not ask the question again or try to bring it to the devs attention, I was happy with them just ignoring my question, you didn't need to bring this old comment back up again
yes, a legend, I am happy with thatI've been on XDA since honeycomb. Forgive me, I didn't realize I was in the presence of an XDA legend to whom the rules clearly do not apply. Since there isn't a written or unwritten rule about what comments can or cannot be replied to, I will continue taking my liberty, but thank you for your....input
@optimumpro did exactly as you instructed.If you are updating from a previous release, you should already have TWRP 3.5.2 in both slots, as you were supposed to flash TWRP installer right after the rom. So, flash the rom, flash TWRP installer, then you can proceed to step 3.
You should flash the rom 2 times to make sure it's flashed to both slots because of the A/B partitioning@optimumpro did exactly as you instructed.
NOTE: downloaded ROM again to exclude possibly corrupted zip.
1 Flash ROM
2 Flash TWRP
3 Reboot TWRP
4 Reboot SYSTEM
But instead of booting into ROM, it boots 2x on android logo, then back to TWRP.
Since you have deviated from install instructions, possibly jumped to another rom and switched slots multiple times, you may need a fresh install with factory reset.@optimumpro did exactly as you instructed.
NOTE: downloaded ROM again to exclude possibly corrupted zip.
1 Flash ROM
2 Flash TWRP
3 Reboot TWRP
4 Reboot SYSTEM
But instead of booting into ROM, it boots 2x on android logo, then back to TWRP.
I was thinking that....but I didn't do it, since I had a simple way to boot to other working slotYou should flash the rom 2 times to make sure it's flashed to both slots because of the A/B partitioning
Boot twrp
Flash rom, Flash twrp, Reboot twrp
Flash rom, Flash twrp, Reboot system
Well I booted back to previously working slot after 1st failure, also Jaguar ROM from October.Since you have deviated from install instructions, possibly jumped to another rom and switched slots multiple times, you may need a fresh install with factory reset.
There is one more thing you should try: if you were trying to switch to Android 12 or 13 roms, your vendor partition on another slot was overridden. Jaguar does not touch vendor (it is stock). If that's the case, then boot into another slot that has normally booting Jaguar, use TWRP to back up vendor (not vendor image). Then reboot into twrp and restore vendor once, then within twrp switch to another slot and restore vendor again. That should fix vendor on another slot.
As I have said: back up Vendor (not image) from the working slot with TWRP, then restore it to the non-working slot. The fact that you are not having bootloop, but rather booting straight into TWRP is an indication that something is wrong with Vendor on non-working slot.Well I booted back to previously working slot after 1st failure, also Jaguar ROM from October.
This is 3rd upgrade after August one of Jaguar ROM, no other ROMs on either of the partitions, nor I flashed anything other than this ROM.
So really do not know what went wrong, unfortunately, logcat from PC fetches nothing when logging it from PC on failed boot after upgrade.
Let's try!As I have said: back up Vendor (not image) from the working slot with TWRP, then restore it to the non-working slot. The fact that you are not having bootloop, but rather booting straight into TWRP is an indication that something is wrong with Vendor on non-working slot.
@optimumpro , this actually worked! Thanks a bunch for the hint!As I have said: back up Vendor (not image) from the working slot with TWRP, then restore it to the non-working slot. The fact that you are not having bootloop, but rather booting straight into TWRP is an indication that something is wrong with Vendor on non-working slot.
Good. Get those 'thankyous' going: I just need 3 more for 15000.@optimumpro , this actually worked! Thanks a bunch for the hint!
The a0508be4453b9ec8d5ba927d271b01cb for JaguarOneplus6T_V27-VANILLA.zip is the correct one. You have the right file. XDA is probably using a different algorithm. Mine is MD5.Hi Optimumpro,
The download hash for V27 Vanilla LINK says:
f417f58cc0cee11ca2ace95011d0cc1f
But when I check the MD5 hash after downloaded, I am getting:
A0508BE4453B9EC8D5BA927D271B01CB
Does that MD5 hash in the download LINK refer to your original uploaded hash for the Vanilla V27 ZIP file??
Thanks again for keeping Jaguar alive for Oneplus 6/6T phones!
Those hashes are done by XDA, not me.Thanks for confirming the hash matches yours.
I noticed that both the Vanilla and Full download links have the same MD5 per V25, V26 and V27 -- I have not downloaded FULL, but I am guessing that those are the hashes of the FULL version?
XDA upload works in 1 out of 100 tries. AFH isn't working at all. Google drive is working fine. So, switch to incognito mode or try another browser.Hi Optimumpro,
Could you kindly please also upload the new January V28 release to XDA or Androidhosting? Because when I click google drive, I keep getting a blank page.
The MD5 from the previous release matched to yours last time I asked about it, so it should not be a problem if XDA displays their own hash in the download link.
...
And sorry for the late reply to your earlier question, I post on the OP6 thread too because I also own a OP6.
Thanks again for keeping this ROM alive for OP6/T users!
...
Just found out from another post that Androidhosting is going out of business?! Perhaps you can upload to Mega.NZ ??? They are quite reliable with fast download speeds.