Related
in short: i need the mojo`s stock android rom in a form wich i can flash with twrp!
Hey Guys,
i am new here. i can t undersund why i can t directly write this thread in the mojo dev section where it belongs: http://forum.xda-developers.com/mad-catz-mojo/development
it says i have not enough rights for that - not understundable for me.
to the case:
already from the beginning i had the mojo, i worried becouse there were no recovery system like romanger or twrp available. i worried, if i make me the whole work, with installing configuring apps and system and an error occured, that i will have no posibility to play a working backup back and exact like that, it was comming:
suddenly sixaxis app wasn t working anymore and gave me the error-message: couldn t load hcl-library-something.
i deletet data and cache of this app, deinstalled, reinstalled, still the same proplem. so my worst nightmares came true.
now i had the choice to set the system to factory defaults (not sure if with this the spoken error were fixed) and lose everything and make the whole work again, or forget it and put the mojo to ebay or to look if in the meanwhile a recovery system is available so that i would have the whole work again, but then, through the posibility of recovery i am on the safe side.
so i decide it and i found out that now a twrp was available and and a unoffical cm12 rom:
[ROM][UNOFFICIAL][mojo] CyanogenMod 12 Mad Catz M.O.J.O: http://forum.xda-developers.com/mad.../rom-cyanogenmod-12-mad-catz-m-o-j-o-t2976401
let me say, that i am not a linuxfreak or a nerd. i see me as an enduser. i want to use things only, i don t have the time, nerves and even the intention to be more.
explanation: if you want for example fly to anywhere, you must not know how exact a plain is working, becouse you only want to use it.
so you buy an ticket jump into the plain and thats it.
i say that through i am no expert, i managed to install twrp and i managed to flash the custom rom.
then the problems began. after flashing it seems that i have no root. so i must research an half day to find out that you must hit seven times dev options to give the root setting free. i don t understund why people do this and don t give this information clear out. if anyone is able to install an costum rom, then you must not save him, with trying to hide the posiblity of root! this makes no sense for me.
my problem actual is that i need the stock rom, becouse the only thing i ever wantet was a working recovery system and this i have now.
i only installed the cm12 rom, becouse there was no stock rom, so i have had no choice.
I hope anyone can provide me the orginal mojo stock rom that i can flash it with twrp.
so if possible, please help me.
best regards
p.s.: forgive me my bad english wich isn t my foreign language. my german is much better
[email protected] said:
in short: i need the mojo`s stock android rom in a form wich i can flash with twrp!
Hey Guys,
i am new here. i can t undersund why i can t directly write this thread in the mojo dev section where it belongs: http://forum.xda-developers.com/mad-catz-mojo/development
it says i have not enough rights for that - not understundable for me.
to the case:
already from the beginning i had the mojo, i worried becouse there were no recovery system like romanger or twrp available. i worried, if i make me the whole work, with installing configuring apps and system and an error occured, that i will have no posibility to play a working backup back and exact like that, it was comming:
suddenly sixaxis app wasn t working anymore and gave me the error-message: couldn t load hcl-library-something.
i deletet data and cache of this app, deinstalled, reinstalled, still the same proplem. so my worst nightmares came true.
now i had the choice to set the system to factory defaults (not sure if with this the spoken error were fixed) and lose everything and make the whole work again, or forget it and put the mojo to ebay or to look if in the meanwhile a recovery system is available so that i would have the whole work again, but then, through the posibility of recovery i am on the safe side.
so i decide it and i found out that now a twrp was available and and a unoffical cm12 rom:
[ROM][UNOFFICIAL][mojo] CyanogenMod 12 Mad Catz M.O.J.O: http://forum.xda-developers.com/mad.../rom-cyanogenmod-12-mad-catz-m-o-j-o-t2976401
let me say, that i am not a linuxfreak or a nerd. i see me as an enduser. i want to use things only, i don t have the time, nerves and even the intention to be more.
explanation: if you want for example fly to anywhere, you must not know how exact a plain is working, becouse you only want to use it.
so you buy an ticket jump into the plain and thats it.
i say that through i am no expert, i managed to install twrp and i managed to flash the custom rom.
then the problems began. after flashing it seems that i have no root. so i must research an half day to find out that you must hit seven times dev options to give the root setting free. i don t understund why people do this and don t give this information clear out. if anyone is able to install an costum rom, then you must not save him, with trying to hide the posiblity of root! this makes no sense for me.
my problem actual is that i need the stock rom, becouse the only thing i ever wantet was a working recovery system and this i have now.
i only installed the cm12 rom, becouse there was no stock rom, so i have had no choice.
I hope anyone can provide me the orginal mojo stock rom that i can flash it with twrp.
so if possible, please help me.
best regards
p.s.: forgive me my bad english wich isn t my foreign language. my german is much better
Click to expand...
Click to collapse
try:
ftp://86.54.116.234/pub/software/mojo/
Not sure if it's flashable
gwaldo said:
try:
Not sure if it's flashable
Click to expand...
Click to collapse
i am also not sure if its flashable and i don t want destroy my mojo.
you are the first one, since i startet this threat, who are concern and tried to help.
thank you!
greetings
[email protected] said:
i am also not sure if its flashable and i don t want destroy my mojo.
you are the first one, since i startet this threat, who are concern and tried to help.
thank you!
greetings
Click to expand...
Click to collapse
Hi,
I'm not an andriod expert , and i too have no interest in trashing my mojo.
maybe ask on the dev forum for cm12 thread.
I'm 75% sure it will work :-\
gwaldo said:
Hi,
I'm not an andriod expert , and i too have no interest in trashing my mojo.
maybe ask on the dev forum for cm12 thread.
I'm 75% sure it will work :-\
Click to expand...
Click to collapse
i tried to write there:
i am new here. i can t undersund why i can t directly write this thread in the mojo dev section where it belongs: http://forum.xda-developers.com/mad-...jo/development
it says i have not enough rights for that - not understundable for me.
Click to expand...
Click to collapse
, but its not possible for me and it looks my thread get not moved to the correct section.
maybe someone with an stock mojo can install twrp:
[RECOVERY][mojo] TWRP 2.8.2.0 recovery Mad Catz M.O.J.O. :http://forum.xda-developers.com/mad...overy-twrp-2-8-2-0-recovery-mad-catz-t2973640
make a bakcup of his system with it and give me the rom.
i think this should work.
[email protected] said:
i tried to write there:
, but its not possible for me and it looks my thread get not moved to the correct section.
maybe someone with an stock mojo can install twrp:
[RECOVERY][mojo] TWRP 2.8.2.0 recovery Mad Catz M.O.J.O. :http://forum.xda-developers.com/mad...overy-twrp-2-8-2-0-recovery-mad-catz-t2973640
make a bakcup of his system with it and give me the rom.
i think this should work.
Click to expand...
Click to collapse
You can ask in the cm12 thread
gwaldo said:
You can ask in the cm12 thread
Click to expand...
Click to collapse
thank you! did so.
[email protected] said:
thank you! did so.
Click to expand...
Click to collapse
It's flashable just flash the zip and your back on stock.
Unjustified Dev said:
It's flashable just flash the zip and your back on stock.
Click to expand...
Click to collapse
thats sounds great. thanks!
can you please say me wich file exactly i need from the link?
there are several .zip files
[email protected] said:
thats sounds great. thanks!
can you please say me wich file exactly i need from the link?
there are several .zip files
Click to expand...
Click to collapse
I use MO0205-TS
Unjustified Dev said:
I use MO0205-TS
Click to expand...
Click to collapse
thank you very much! then my problem should to solved.
you also seem to be responsible for the MOJOs twrp-port. also thank you for that!
i was waiting for such an recovery system since i bought the mojo.
now i can work without beeing afraid to have no backup for the worst case.
nice work!
greetings
Unjustified Dev said:
It's flashable just flash the zip and your back on stock.
Click to expand...
Click to collapse
Unable to flash on my end. It's there an update to this?
paulie_gogetit said:
Unable to flash on my end. It's there an update to this?
Click to expand...
Click to collapse
Flash, the remix OS rom first and then flash this rom. It has to do with the partition structure. i was also unable to flash the stock rom after having CM12 on my mojo, but I first flashed remix OS and then was able to flash the stock rom.
I'm now running the stock rom happily and will not go back to any custom roms. The bottom line is that there is just one dev doing custom rom work and while I appreciate his work, It just doesn't seem like any of the custom roms are there yet in regards to stability.
Is there a keyboard sequence to get into recovery? I have bricked my MOJO because I failed to realize that it failed to flash the stock firmware after I wiped it.
(EDIT) I found a solution to the above!
Okay so the method I used to get into recovery is to use the MoDaCo root tool and edit the superboot-windows.bat file and change boot.superboot.img
to twrp-2.8.7.0-mojo.img. Of course you have to have the TWRP image as well to do this. This got me into TWRP, but the following issue still stands.
Okay, I can't seem to get Remix OS or the factory rom to install, CM12 installs fine though, anyone know how to fix this?
Side note:
I have a TWRP backup of my other MOJO but TWRP doesn't see anything when I choose restore, and I have tried choosing internal and SD card for the source to no avail, does anyone know how to get around that? Or is this just a current issue with this version of TWRP on the MOJO?
Please help need mojo stock rom
Hello all some reason my stock rom didn't back up and I've lost it please if anyone can help I need the stock rom for madcatz mojo thank you
konser13 said:
Hello all some reason my stock rom didn't back up and I've lost it please if anyone can help I need the stock rom for madcatz mojo thank you
Click to expand...
Click to collapse
Me too
Sent from my LG-H815 using Tapatalk
Their is a way to get it back to stock
To 1eyedmonster I had left information but I will explain how to do this if you can use ( Firefox internet browser ) you can download the stock frameware from madcatz site where you can find stock 4.2.2 for the m.o.j.o. link to original thread http://forum.xda-developers.com/mad...refox-to-download-madcatz-mojo-4-2-2-t3431587
imseanross1 said:
Is there a keyboard sequence to get into recovery? I have bricked my MOJO because I failed to realize that it failed to flash the stock firmware after I wiped it.
(EDIT) I found a solution to the above!
Okay so the method I used to get into recovery is to use the MoDaCo root tool and edit the superboot-windows.bat file and change boot.superboot.img
to twrp-2.8.7.0-mojo.img. Of course you have to have the TWRP image as well to do this. This got me into TWRP, but the following issue still stands.
Okay, I can't seem to get Remix OS or the factory rom to install, CM12 installs fine though, anyone know how to fix this?
Side note:
I have a TWRP backup of my other MOJO but TWRP doesn't see anything when I choose restore, and I have tried choosing internal and SD card for the source to no avail, does anyone know how to get around that? Or is this just a current issue with this version of TWRP on the MOJO?
Click to expand...
Click to collapse
If you still have issues entering recovery install terminal emulator from play store
Make sure usb debugging enabled in developer options
Then open terminal emulator and enter following commmnds you will need a keyboard for this Then follow these steps
Adb devices (enter)
Adb reboot recovery (enter)
Then you should be in twrp
CAUTION TO NOT LOOSE TWRP
I read two posts that say v21, now again on V8.5, put the stock recovery back instead of twrp. This is probably a side effect of a fresh stock /system and wipe of /data.
As a preventive step, when done flashing and wiping reboot to recovery FIRST, before booting the system It will allow recovery to handle removing the recovery-from-boot.p that flashes stock recovery.
I just patched the modified V7.4.2 up to the newly released 8.3 now 8.4. 8.5, 8.7,9.0 -V9.2 Patch
New update has been made from V17 to V21 of the non prime version of R1-HD, Non prime is behind on security patch (2017-05-05)
Copied ROM from phone and made twrp install ROM from it.
* No preloader change (official updates change the preloader to block your ability to use sp flash tools for rom flashing)
* No lk.bin change __ this part is what allows you to choose boot options(boot menu when power and volume pressed together)
* No "FOTA" app Fota has now been left in to make it easier to get next update, if that ever happens.
* No opera browser
* No adds (removed in the modified 7.4.2)
* Custom boot logo (only done on v8.3, there was no interest in this so abandoned)
--Newer versions of rom left stock, Leaving mods up to user.
** while it is not necessary to do a wipe with this ROM, I still recommend it.
**Thanks:
** @vampirefo needed his patched v7.4.2 in order to apply this new 8.3 patch and again for 8.4
** @ColtonDRG OR @jasonmerc I do not remember which one made it: For the image used in the custom logo
and the modified zip is here .
Roms are rootable with SuperSU, flashed in twrp after install. Must be done in systemless mode. In order to patch system veridy in boot.img
Logo update did not work on original rom changing link to updated version
BLU rolled v8.3 back to v7.4.2 because of app compatability issues. V8.4 is there fixed release. Both 8.3 and 8.4 are modified prime roms with ads stripped
V21 is the non prime update.
Unmodified V6.1
==>NON-ROOTED-logo-not-replaced-modified-V8.3
==>Fixed Logo modified NON_ROOTED V8.3
==>>modified V8.4
==>>modified V8.5
==>>Full with Ads V8.7
==>>Full with Ads V9.0
==>>Patch For V9.2 must be flashed on top of fresh V9.0
****Run debloat ==>script to remove ads if you need/ want to, or remove from zip before flashing ****
alt. manual example: before reboot, while still in twrp. Select mount and put checkmark next to system. Then run these two commands in adb terminal
Code:
adb shell rm /system/priv-app/com.amazon.*/com.amazon.*.apk
adb shell rm /system/app/Adups*/*.apk
==>>Modified V21
** stand alone logo installs
I flashed this but I didn't get the custom boot logo.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
I had that happen to my second phone too.
I don't have an explanation yet.
I even made a separate update.zip , that one didn't make the logo change either. I did eventually change it with sp flash tool.
I tried with both recoveries.
and multiple /dev location formats. and for whatever reason my one phone did not accept the logo change from recovery.
And the other test phone it worked.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
Neither did I but it all seems to be working fine
Been using this for about a day now, likewise no custom boot logo, but that's fine. Otherwise, it's been running super well. A lot better than the previous mostly stock version did for me with the bloatware APKs removed after the install. A lot of the general idiosyncrasies of the previous version of the stock rom seem to have gone away for me. It seemed to have weird storage management issues, errors moving to SD, broken symlinks that prevent apps from moving or being reinstalled, and a lot of other little non-storage issues, but so far, none off that here.
Long story short, good work! I hope we eventually see proper 7.x roms through some of the efforts going on, but in the meanwhile, your work here has made life a little bit better on 6.
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
**logo-update is same as composite but with alt updater-binary
**composite-logo screenshot is in op
**stock logo will return to original BLU logo
mrmazak said:
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
Click to expand...
Click to collapse
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Serenitybs said:
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Click to expand...
Click to collapse
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
Somebody already tried this out
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
It was just wishful thinking. I have no idea how all of this is done. All I know is @mrmazak has helped me to fall in love with my phone again with this V8.3. The 7.4.2 did seem a bit buggy for my phone but this update works beautifully and I didn't even root it. If this remains true I will be happy with this phone for awhile even on 6.0
Really confused right now.
I was browsing through the settings menus. And found in the Settings-security- menu a toggle labeled "quick boot" ( not to be confused with "fastboot") . I enabled it then rebooted to see if it booted quicker. Didn't seem to make much if any difference. So I went back to turn it back off. And it wasn't there. I checked in my other phone , it wasn't there on that one either.
Did any body see this menu item, and if so where is is it?
Edit 1:
Few more power off , power on cycles to compare times. With other phone and defiantly seems to have turned on some faster boot option.
This phone goes from off to on in 5-6 seconds other phone takes about 20.
Edit 2:
OK , I panicked for a minute.
Couldn't find the setting and thought that it was another way to block sp flash tool by preventing you from ever being fully powered off.
But the setting was in accessibility not security.
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
detroitredwings said:
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
Click to expand...
Click to collapse
The mode changer app is technically a security issue. I did have that warning a few times when using mode changer app from the XDA thread of the developer, then when I used the app downloaded from f-droid it worked with systemless root and didn't give the security warning.
The app downloaded from f-droid worked for me as well, many thanks!
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Letitride said:
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Click to expand...
Click to collapse
I also had an app that previously work, say is not compatible now.
Maybe has to do with apps that have links to pay accounts. And that has something to do with trustzone. (Tee1 & tee2)
Those sections I left out of the update. I will add it back in and test. Update when I do. It is also possible this problem is why Blu rolled back there update.
**EDIT**
well that didn't go well at all.
I flashed the new trustzone.bin files from the official update. Now phone no longer turns on and no longer connects to flash tool
**EDIT 2**
After much persistence and many failed attempts to get phone recognized in pc again. Finnaly got to a point that phone was cycling between "preloader" driver and "usb serial device", and with careful timing was able to start sp flash tool at just right time and the flashing back to original trustzone files seems to have recovered phone.
for the record i am not sure what steps made it work. But I was shifting back and forth between leaving phone sit on charge, then on charge with rubber band wrapped around power button, then not plugged in , and not plugged in with rubber band on power button.
Okay... persistence is key in customization, i guess! I am getting somewhere here!
mrmazak said:
The first link is needed to get phone unlocked so you can install twrp.
Click to expand...
Click to collapse
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
OldSkewler said:
Okay... persistence is key in customization, i guess! I am getting somewhere here!
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
Click to expand...
Click to collapse
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Many ways to do that.
Easiest is to copy to phone while phone is connected to PC.
Cam also download file from internet with your phone.
Bottom line is get zip file to the phone boot to recovery and install
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
mrmazak said:
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Easiest is to copy to phone while phone is connected to PC.
Bottom line is get zip file to the phone boot to recovery and install
Click to expand...
Click to collapse
Right on man! I am officially running 8.3 ROM with April 5th 2017 Security Patch Level! Geez.. it was not easy but I got this working!
MrMazak, I followed all your instructions on both links, so could you tell me what exactly I have on my phone? Is it rooted? Bootloader Unlocked? The phone seems to be working fine but I don't know what level of access I have. Honestly I don't even know exactly what the differences between all these terms are.
Also, do I have or not SU? One of the steps under the .bat I believe install it. How do I access it?
Thanks again!
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Weasel0 said:
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
Click to expand...
Click to collapse
My install is pretty fresh, couple of hours, but as far as I can tell all is working fine with Wifi, As a matter of fact this is a new device only connected with Wifi and no SIM Card.... internet works fine.
I have a Galaxy J3 (2016) J320ZN.
I have rooted it, and would like to install TWRP then xsposed, maybe even another ROM if there is any that will work.
Will the TWRP posted here for other models work on my phone?
How about ROMs? Thank you.:silly:
azlemad said:
I have a Galaxy J3 (2016) J320ZN.
I have rooted it, and would like to install TWRP then xsposed, maybe even another ROM if there is any that will work.
Will the TWRP posted here for other models work on my phone?
How about ROMs? Thank you.:silly:
Click to expand...
Click to collapse
I've only just worked this out myself and was going back to update my post...did a search and that's how I found your question.
I've had so much trouble with this... either, you couldn't get root using SuperSU.zip through TWRP (there's another thread on this)... because you'd get stuck in a bootloop and my "solution" was to flash CF-Auto-Root again... without realizing that CF-Auto-Root wipes to stock recovery XD. Through this, though I lost my phone re-set up and TWRP.... I saw that there was a dm-verity error which I don't understand but know there is a patch.... and maybe that's why people were getting bootloops? I'm really not an expert at all. I just try until something works.
SO, you could just first try flashing TWRP for J3lte from the link I provided and then the latest SuperSU and see if that works now.....(earlier versions did not) if it doesn't work and you get stuck in a bootloop then flash CF-Auto-Root (available at: https://download.chainfire.eu/986/C...3lteusc-j3lteusc-smj320r4.zip?retrieve_file=1) and start again. I PERSONALLY only had success without a bootloop ONCE I added the dm-verity patch to my install procedure:
The TWRP that will work for the J320ZN is j3lte: https://dl.twrp.me/j3lte/
I used the latest version twrp-3.2.1-0-j3lte.img.
If you need in-depth help look for a tutorial or quote me and I'll respond & try walk you through it. I know that model J320YZ uses the same TWRP and there is a tutorial on XDA for the basics.....
Once TWRP is installed and you've booted into TWRP recovery and you've formatted, Install SuperSU.zip through the "Install" button on TWRP. You must have SuperSU.zip on your external SD card (click "Select Storage" to select it).
https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
I used v.2.82 SR5
Finally, BEFORE REBOOTING, I installed no-verity-opt-encrypt-6.0.zip using the same TWRP "Install" button method - which was also on my external SD card
https://androidfilebox.com/miscellaneous/dm-verity-and-forced-encryption-disabler/
Then you can reboot, and set up your phone. Xposed works. If you already ran the fixes using Apps2SD to fix security measures that prevntd Link2SD from creating mountscripts, that stays fixed after all of this.
BACK UP YOUR PHONE FIRST 'cos you'll have to reset it all up again. Samsung Smart Switch (on your PC) helps, as will Titanium Backup.
Now.... as I said I'm not an expert. I don't understand why things are the way they are. Nor am I responsible if the dm-verity wasn't needed, which is why maybe you should just try TWRP then latest SuperSU first. BUT for me, I had bootloop and needed the 3rd step of dm-verity patch.
As for Custom ROMS... I have no real interest in those, so that's something you'll have to experiment with yourself, or ask someone else
IMPORTANT: I thought I'd better add that once you've got TWRP and root installed... and want to install Xposed, you cannot use the official version for Android 5.1.1. It will not work on our Samsung Touchwiz Stock ROMS. You can either install a custom ROM first, or you will have to use the Unofficial version by wanam that will work on device.
Here's a tutorial: https://www.tricksfolks.com/install-xposed-framework-samsung-lollipop-marshmallow/
Make sure to select from the download links the file for 5.1.1 and our hardware is arm so download that file, not arm64 version or x86 version. Should be xposed-v87.1-sdk22-arm-custom-build-by-wanam.zip
Also note, I had some issues with the Xposed Installer (apk) - latest one 3.2. Didn't want to register the wanam framework that I flashed in TWRP. So, I rolled back to 3.1.5 and that works OK. You'll have a big red warning telling you not to update THEIR framework... but ignore that and just go to Downloads and install away.
The article I linked above with the tutorial and download links has an earlier version of the Xposed Installer so you could try that if you can't find v.3.1.5. Just don't use v.3.2
ALSO ANYBODY PLEASE UPDATE ME IF YOU GOT TWRP AND ROOT WITH OR WITHOUT DM-VERITY PATCH. I'd like to know so I can learn more about this stuff. Still a novice.
Annnnnd I just realized you were the one that PMed me a few weeks ago to get me working on this and that you'd broken your phone hehehehe.
Well, I'm just updating it on all the J320ZN threads now for future folk.
Winston Churchill said:
Annnnnd I just realized you were the one that PMed me a few weeks ago to get me working on this and that you'd broken your phone hehehehe.
Well, I'm just updating it on all the J320ZN threads now for future folk.
Click to expand...
Click to collapse
lol
yeah, that was me sadly -_-
But thank you very much anyway, for taking the time and effort to post this, I'm sure it'd be useful to somebody out there
Winston Churchill said:
I've only just worked this out myself and was going back to update my post...did a search and that's how I found your question.
I've had so much trouble with this... either, you couldn't get root using SuperSU.zip through TWRP (there's another thread on this)... because you'd get stuck in a bootloop and my "solution" was to flash CF-Auto-Root again... without realizing that CF-Auto-Root wipes to stock recovery XD. Through this, though I lost my phone re-set up and TWRP.... I saw that there was a dm-verity error which ...
As for Custom ROMS... I have no real interest in those, so that's something you'll have to experiment with yourself, or ask someone else
Click to expand...
Click to collapse
Wow, thanks for going through the pain so I may not have to go through so much. Would you be able & willing to help me get my wife's SM J320ZN rooted so I can get the sd card used for apps? She doesn't need too much on there but the bloody thing goes to low memory way too soon. I'd love to know if I can get a better os on there too if you can make any suggestions.
I've got enough knowledge to be able to install lineageOS onto my crappy moto e & get that working ok but I'm still on the steep learning curve.
If you can, please provide a step-by-step guide to do this? I know you've said most of what needs to happen in your posts, but when I see "Once TWRP is installed and you've booted into TWRP recovery and you've formatted,..." I'm wondering what should get formatted, what shouldn't, etc
Warm regards
I am super new to rooting I mainly use it for PokemonGo. I am following this video on YouTube.
Basically when I flashed via Odin, I then install Magisk. Then everything is working and rooted BUT when I restart my phone my Magisk is then magically unrooted (I dont know if this is the right term) it says 'Magisk is not installed' and underneath that is says 'Magisk Manager is up to date'
So why does it keep doing this? Everytime this happens I need to Flash again via Odin and do the whole procedure again. This only happens when I restart the phone. Why does it keep doing this and how do I fix this? I will pay someone who can fix this for me. Ive been trying to figure out for the past day and Im going insane. I have no knowledge about rooting etc like i said i just want to play Pokemongo location spoofing.
Appreciate everyones help.
Dude you're giving me......double vision! Oh oh
StoneyJSG said:
Dude you're giving me......double vision! Oh oh
Click to expand...
Click to collapse
What do you mean lol
littlepuppies said:
I am super new to rooting I mainly use it for PokemonGo. I am following this video on YouTube.
Basically when I flashed via Odin, I then install Magisk. Then everything is working and rooted BUT when I restart
Click to expand...
Click to collapse
Are You aware that you have to reboot via keycombo, just as you would boot into recovery and then release the buttons, after vibrate and samsung logo, or alternatively use an app like quick reboot pro ?
You have a double post of the same topic.
blackspy_ said:
Are You aware that you have to reboot via keycombo, just as you would boot into recovery and then release the buttons, after vibrate and samsung logo, or alternatively use an app like quick reboot pro ?
Click to expand...
Click to collapse
Yes but I'm not 100% sure if I'm doing it correctly. Well my magisk is installed so I'm doing it right? But like I said when I restart my mobile magisk is not installed in the app. May I ask what's this reboot Pro? If that will solve the restart problem I would.happily pay. Can you tell me more?I'm really nooby thank you sir
Im seeing doubles.
Hey Everyone,
Just got my hands on an X606F and as usually I could not stand the stock Android 10 OS.
I eventually took a chance and tested flashing the LineageOS 19 GSI from Andy Yan (Android 12), and it worked out extremely well. Everything worked out of the gate, I installed the version with Gapps preloaded and that worked as well. I basically follow this guide, but swapped the custom rom with the one linked below from Andy Yan.
Use this guide:
https://forum.xda-developers.com/t/...d-11-android-12-and-root-with-magisk.4376127/
only difference is DO NOT INSTALL MAGISK AS THIS ROM IS ALREADY ROOTED.
But Swap CAOS11 rom with the one below here. I personally find LineageOS my favorite of all the alternative ROMs out there so I am happy i got this to work.
Andy Yan's LineagOS GSI build (Use this one)
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS.img.xz
Link to folder with other builds (No Gapps...etc)
https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
IF anyone has any questions let me know.
Cheers,
SniperFox
Thanks for your post, it is a good news. After reading your post I’m tempted to try this on my X606X. I will probably do when I find some time. Meanwhile, have you observed any issue ?
This sounds like Great News, as I, too, really don't enjoy the Lenovo UI. And... I cannot get OTAs, as I am already rooted with TWRP and Magisk from this forum: httrecovery-tb-x606f-tb-x606fa-unofficial-twrp-3-6-x-for-lenovo-tab-m10-fhd-plus
However, to be certain:
I 'should' be able to then Install LineageOS by copying from the Link Provided above to an ExtSD, along with GApps, and just wipe, and install from TWRP ?
Also, I'm not familiar with the .xz file compression, do I need to convert it to a .zip file ?
Thanks !
Hi, would this version work on TB-X704F ?
Thx.
I’ve tried LineageOS on X606X (LTE version) and I was not lucky. Settings app was crashing each time I went to network settings. Screen was always on or always off. Only way to switch from one to another was to connect or to disconnect USB cable. Any option in settings for screen was not working.
I can confirm that TWRP for TB-X606F/TB-X606FA is working fine on this model.
I tried also CAOS11 but it was a bit laggy. Everything worked, but when I started to mess with Magisk it didn’t want to boot anymore. So I’m back to stock, and confident that one day I will find working Android 12 for this model.
I'm going to plop this question down here, but it's only sort of relevant: what is going on with the navigation bar? My home/back/recents button are all in the bottom right corner of the bar and in the centre are icons for play store, camera, and something else.
How do I go back? I can't find any of the options. I tried this ROM, CAOS11, and an AOSP flavour, and they all had the navbar set up that way. All the other ROMs also crashed the Phh-Treble UI Tuner whenever I tried to change the navbar. I went back to stock, and it returned to normal. Is this an Android 11+ thing? It's awful.
SniperFox22 said:
Hey Everyone,
Just got my hands on an X606F and as usually I could not stand the stock Android 10 OS.
I eventually took a chance and tested flashing the LineageOS 19 GSI from Andy Yan (Android 12), and it worked out extremely well. Everything worked out of the gate, I installed the version with Gapps preloaded and that worked as well. I basically follow this guide, but swapped the custom rom with the one linked below from Andy Yan.
Use this guide:
https://forum.xda-developers.com/t/...d-11-android-12-and-root-with-magisk.4376127/
only difference is DO NOT INSTALL MAGISK AS THIS ROM IS ALREADY ROOTED.
But Swap CAOS11 rom with the one below here. I personally find LineageOS my favorite of all the alternative ROMs out there so I am happy i got this to work.
Andy Yan's LineagOS GSI build (Use this one)
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS.img.xz
Link to folder with other builds (No Gapps...etc)
https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
IF anyone has any questions let me know.
Cheers,
SniperFox
Click to expand...
Click to collapse
Thanks so much.
Everything worked out without a hitch.
But how do I edit or get rid of those apps in the navigation bar??? They're an eyesore and pretty useless to me.
sirp0p0 said:
I'm going to plop this question down here, but it's only sort of relevant: what is going on with the navigation bar? My home/back/recents button are all in the bottom right corner of the bar and in the centre are icons for play store, camera, and something else.
How do I go back? I can't find any of the options. I tried this ROM, CAOS11, and an AOSP flavour, and they all had the navbar set up that way. All the other ROMs also crashed the Phh-Treble UI Tuner whenever I tried to change the navbar. I went back to stock, and it returned to normal. Is this an Android 11+ thing? It's awful.
Click to expand...
Click to collapse
Holy crap. You read my mind.
What a waste!
Nice to see so many people experimenting with this tablet. It would be nice if we had a dedicated subforum for this device.
I have been trying out several ROMs/GSIs with Android 11 and 12, but all of them are performing really laggy after a couple of days. Overall system perfomance and latency seems slow and choppy.
Especially YouTube is very laggy and shows heavy artifacting on almost every video making me think a lot of ROMs cant make proper use of hardware codec acceleration.
Another problem is getting Netflix to work, whereas on the stock ROM I had 1080p playback with a modded apk, on other custom ROMs I cant even launch the app, sadly no success with the Kodi Netflix add-on either.
My plan was to see if I could improve perfomance by removing Lenovo's bloat and using microg to replace gapps, but it turned out perfoming worse than before.
Maybe this device is just too weak for this kind of modding.
Thoughts on these issues? And which ROMs have you personally enjoyed? I think I might go back to stock for now, give the roms some time to develop further and try again at the end of the year.
Zelodos said:
Nice to see so many people experimenting with this tablet. It would be nice if we had a dedicated subforum for this device.
I have been trying out several ROMs/GSIs with Android 11 and 12, but all of them are performing really laggy after a couple of days. Overall system perfomance and latency seems slow and choppy.
Especially YouTube is very laggy and shows heavy artifacting on almost every video making me think a lot of ROMs cant make proper use of hardware codec acceleration.
Another problem is getting Netflix to work, whereas on the stock ROM I had 1080p playback with a modded apk, on other custom ROMs I cant even launch the app, sadly no success with the Kodi Netflix add-on either.
My plan was to see if I could improve perfomance by removing Lenovo's bloat and using microg to replace gapps, but it turned out perfoming worse than before.
Maybe this device is just too weak for this kind of modding.
Thoughts on these issues? And which ROMs have you personally enjoyed? I think I might go back to stock for now, give the roms some time to develop further and try again at the end of the year.
Click to expand...
Click to collapse
Hi @Zelodos, thank you so much for the feedback about custom ROMs you've been messing around with.
I'm the owner of a Lenovo TB-X606F tablet (Lenovo Tab M10 FHD Plus) experiencing the Netflix issue that prevents me from watching content at 1080p resolution. With DRM Info app, I've checked that the Security Level of mine is L3, whereas yours and some others' tablets (which are exactly the same model: TB-X606F) are L1...
Could you tell me which FW version is running your tablet? I've been reading on Lenovo Forums for a while and I've picked up the two most relevant posts relating this issue:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://forums.lenovo.com/topic/findpost/1088/5020213/5502643
GitHub Link for the Netflix modded apk: https://github.com/longseespace/netflix_patch/releases
https://forums.lenovo.com/topic/findpost/1088/5050995/5294237
I wonder if flashing the TB-X606F_S300429_211101_BMP firmware version can make a difference for me to get L1 Security Level, instead of L3... Or maybe the FW version your tablet is running currently can sort it out, I don't know. Just let me know, please. Thanks in advance.
SniperFox22 said:
Hey Everyone,
Just got my hands on an X606F and as usually I could not stand the stock Android 10 OS.
I eventually took a chance and tested flashing the LineageOS 19 GSI from Andy Yan (Android 12), and it worked out extremely well. Everything worked out of the gate, I installed the version with Gapps preloaded and that worked as well. I basically follow this guide, but swapped the custom rom with the one linked below from Andy Yan.
Use this guide:
https://forum.xda-developers.com/t/...d-11-android-12-and-root-with-magisk.4376127/
only difference is DO NOT INSTALL MAGISK AS THIS ROM IS ALREADY ROOTED.
But Swap CAOS11 rom with the one below here. I personally find LineageOS my favorite of all the alternative ROMs out there so I am happy i got this to work.
Andy Yan's LineagOS GSI build (Use this one)
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS.img.xz
Link to folder with other builds (No Gapps...etc)
https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
IF anyone has any questions let me know.
Cheers,
SniperFox
Click to expand...
Click to collapse
Hello I have a problem installing custom ROMs on this specific tablet mate. When CAOS 11 or any other custom ROM is installed and I want to reboot, TWRP brings a message that OS is not installed do you want to reboot? Then sticks twice at Lenovo logo and boots to TWRP.... It doesn't boot at the custom ROM...
vassiliszacharis said:
Hello I have a problem installing custom ROMs on this specific tablet mate. When CAOS 11 or any other custom ROM is installed and I want to reboot, TWRP brings a message that OS is not installed do you want to reboot? Then sticks twice at Lenovo logo and boots to TWRP.... It doesn't boot at the custom ROM...
Click to expand...
Click to collapse
My suggestion is to use the Lenovo recovery tool linked here. (Lenovo's tool is very good and its hard to brick these, so good job there at least)
Rescue and Smart Assistant (RSA) - Lenovo Support CA
pcsupport.lenovo.com
Then use this tool to reset the tablet to the stock OS. Most likely what happened is you tried to flash an OS that was built on a different version of Android. Make sure that your using a build that is based on the right version of Android. After you do that recovery you should be up to Android 10, as it uses the latest image for the tablet. This means you need to use a CAOS 10 not CAOS 11. You will need to reinstall TWRP first again, as this will be removed when you recover. Let me know if you have issues and Ill keep an eye out for any new posts.
Cheers,
Sniper Fox
SniperFox22 said:
My suggestion is to use the Lenovo recovery tool linked here. (Lenovo's tool is very good and its hard to brick these, so good job there at least)
Rescue and Smart Assistant (RSA) - Lenovo Support CA
pcsupport.lenovo.com
Then use this tool to reset the tablet to the stock OS. Most likely what happened is you tried to flash an OS that was built on a different version of Android. Make sure that your using a build that is based on the right version of Android. After you do that recovery you should be up to Android 10, as it uses the latest image for the tablet. This means you need to use a CAOS 10 not CAOS 11. You will need to reinstall TWRP first again, as this will be removed when you recover. Let me know if you have issues and Ill keep an eye out for any new posts.
Cheers,
Sniper Fox
Click to expand...
Click to collapse
Cheers Sniper. Indeed I returned back to stock ROM by using Lenovo tool that is very easy to install it. I installed TWRP 3.6.x for Lenovo Tab M10 FHD Plus which is suitable for Android 11 and Android 12. Can I ask you please what was your procedure of installing Android 12 custom ROM on that tablet?
vassiliszacharis said:
Cheers Sniper. Indeed I returned back to stock ROM by using Lenovo tool that is very easy to install it. I installed TWRP 3.6.x for Lenovo Tab M10 FHD Plus which is suitable for Android 11 and Android 12. Can I ask you please what was your procedure of installing Android 12 custom ROM on that tablet?
Click to expand...
Click to collapse
I would try Andy Yan’s Lineage OS GSI builds. Those are generally where you want to start as those are more likely to be compatible. Also make sure when you flash the custom rom you follow the directions from that original link closely. If you miss a step it’s easy to screw it up where it does what you said and either boot loops or doesn’t see the OS. I think you might be limited to lineage OS version 19 with this tablet. Newer OS might not work.
Added comment. I have also tried Ubuntu Touch and it works well on this tablet. Wifi, Bluetooth, audio all work, as does charging. Although the app market for Ubuntu touch is not great it seems to be getting better.
SniperFox22 said:
Added comment. I have also tried Ubuntu Touch and it works well on this tablet. Wifi, Bluetooth, audio all work, as does charging. Although the app market for Ubuntu touch is not great it seems to be getting better.
Click to expand...
Click to collapse
How did you manage this mate? Also when I am trying this command after install TWRP: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
It is not recognised... How can you overpass this? Maybe this is my problem. I just installed vbmeta without disable it .. Any ideas?
vassiliszacharis said:
How did you manage this mate? Also when I am trying this command after install TWRP: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
It is not recognised... How can you overpass this? Maybe this is my problem. I just installed vbmeta without disable it .. Any ideas?
Click to expand...
Click to collapse
I think your problem is related to this part of the instructions
"After flashing the recovery, you must reboot into recovery to ensure that TWRP permanently installs. If the `fastboot reboot recovery` command does not work for you, hold down the power button to power off the device, then hardware boot into TWRP by holding down both volume buttons + power button to boot into TWRP. If you do not perform this step, the device will boot normally and TWRP will be erased. After booting into TWRP, wipe -> format data."
If you don't boot directly back into TWRP after installing and wipe -> format data you will get that error.
As far as the installation of the Ubuntu Touch, you NEED to be on Android 9 to install it. So you have to downgrade to the original firmware that was Android 9. When you do the Lenovo recovery unfortunately it only give you the newest Android 10 rom. So you need to download the historic ROM for this tablet that is Android 9. Then its as easy as running the Ubuntu Touch installer on your PC. If you try to do it with Android 10 on the device to start it will fail. Ubuntu touch is pretty cool.
cheers mate for your help! respect. Is there any android 12 custom ROM we can use on this tablet?
been using lineage 19.1 on my tb-x606f and is really smooth, but I don´t know what SU app could use. I tried flashing magisk but it creates a conflict with the rom itself.
Does anyone have a download for the boot.img? I would love to do this but cant find a boot image to use for the vbmeta.img