Related
So I got my shiny new device today, and it feels really nice. I worked with the launcher it came with, tried another one, and realized that yep, I gotta root and install a new rom. The notification bar just annoys me too much as I'm used to having quick actions and other things in there.
So, I followed a few guides, and finally worked my way through to having my command line find my device and can successfully reboot it into fastboot mode.
At that point, I realized that I can boot into recoveries without flashing them first (essentially trying them out to see how it works). However, I tried the 4 official version on the twrp site, and one made by a user here (cuoco92). They all successfully boot into the recover using the command "fastboot boot nameOfFileHere.img". At this point, every single recovery failed to respond to touch and volume presses. I can press the power button to turn off the screen, and pressing power to turn the screen back on shows a locked recovery screen, but I can't slide the screen to unlock it.
This is quite concerning to me. I don't want to flash a recovery for good if it's not working properly. I hope this makes sense. Or, is it normal to just flash a recovery and hope for the best? Do recoveries work with just booting to them without being flashed?
I haven't rooted and/or flashed any devices in about 5+ years, the last being a phone from virgin mobile that supported sd cards. When installing new roms, do we store the zips in the root of the phone, or does this get cleared out/deleted when doing the wipe cache/dalvik/etc?
Personally, I just want to make sure I don't rush into this, as there seems to be fragmented results when searching around for twrp not working with touch. I know these things have been asked before plenty of times, and I hope I don't come across as another "ugh, this again" post. I really appreciate any responses!
you never did, then just leave it as it is...its a nice phone eui is not bad... take it easy
Try booting the official TWRP recovery. As far as I remember, some of the versions tweaked by Cuoco92 had issues with the touch panel.
Anyway, EUI is not that bad, as your were told. While I used it, I also used an app called "Notification Toggles", which lets you get Quick Settings like toggles on notification area. It's nice and easy to set up, and the results, although not the same as having the AOSP toggles, is quite nice and convenient.
BTW, which stock ROM did your phone come with?
I have tried 4 different official twrp files (all from the twrp site). My phone is an x820 6gb/64gb and came with EUI version: 5.8.019S (Stable). EUI is nice, very fast and sleek. Maybe I do just need to get used to it, or maybe it's just me itching to try out the different options available since I finally have a phone is not carrier/manufacturer locked down.
Heyyo, hmm that's very odd indeed! I wonder if maybe by temporary booting Cuoco92's TWRP it could have messed up your recovery hmm...
I'd recommend first to flash the stock recovery over your current one and then reboot to fastboot and then flash TWRP. Hopefully this will erase any problem that Cuoco92's recovery could have caused.
This was the guide I followed and it worked flawlessly for me
https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
I never actually flashed any of them. I have only ever just tried booting into them using "fastboot boot recovery name.img". I have not used the fastboot flash command for any of the files.
The only thing I can do after booting the recoveries is hold the power button and eventually the phone will boot up normally.
Remember that I just wanted to boot them to make sure they worked before flashing them. I'll be checking out the guide you linked shortly.
Haven't flashed any of them eh? Hmm should work just fine then... Have you tried TWRP 3.0.2-0 ? I know that one was built with Marshmallow sources
As for which ROM to try? I'd recommend OmniROM if you want to try a custom Nougat ROM.
If you want to see why I think so? I made a massive post or two about it here heh
https://forum.xda-developers.com/le-max-2/help/party-rom-best-help-t3691165/
Thank you so much for the guide you linked. I'm making a little bit of progress here.
I found a twrp recover by cuocos92 that is labeled V3 (apparently from what I read in other threads, V3 seems to be good with the 6gb/64gb models). This recovery allows the use of the touchscreen . Remember that I am only using the "fastboot boot" command so no flashing yet.
Now that I am in a working recovery, I kept hitting "keep read only" so that the stock recovery would not be replaced. I set out to make a backup. Well that kept failing with attempts of trying to mount /system and such. Off to more reading, found out that using the Wipe->Swipe to Factory Reset inside twrp fixes this. I did that. I successfully created a backup.
Now to try to flash the SuperSU zip I have, which was previously copied to the root of the phone from my pc. Can't see any zip files on the internal storage. Reboot the phone (forgetting that it takes a long time after the wipe). Copy the backup to my pc. Copy the SuperSU back to root of phone. Restart the process of adb and fastboot -> back into the cuocos92 V3 recovery. Still no zip to be found. Couldn't mount system again...
Did some more reading. I just attempted the Wipe->Format data. I am currently rebooting back into the phone to set it up again. Apparently, a lot of people say this needs to be done if we did not reboot after unlocking the bootloader. Since twrp has been asking for a password each time I entered it, the format data is supposed to solve this.
I'll edit/post again with more steps or results.
I apologize for the second post here, but this seems more than should go into an appended edit:
After doing the Wipe->Format data, it's advised to reboot back into the recovery. Without flashing the twrp cuocos92 recovery, my thoughts are it would just be back into the stock recovery. At least the twrp version works, so I have no problems with flashing it. And then I'll have to Wipe->Format data again, reboot back into recovery, and then I can flash my SuperSU zip. But how can I get my SuperSU zip on the phone?
Doesn't Wipe->Format data remove it? Everytime I reboot my phone after that the SuperSU on the root of the phone is gone. I can't seem to mount to my pc from the recovery either, clicking the usb storage just unchecks itself right away, and clicking the enable MTP doesn't seem to do anything. So, even if I flash the recovery, Wipe-Format data again, reboot back into the recovery, I still don't see a way of getting the SuperSU zip onto the phone anyways.
I know it probably sounds like I'm whining by now about how things aren't as easy as it seems. I'm trying to be descriptive in what I am doing and what's happening.
Hmm by chance are you using Windows 10? At least I've noticed for me it fails to properly mount the correct drivers for ADB and MTP for TWRP. I'd recommend checking device manager.
If I remember correctly here's what mine looked like at first
https://photos.app.goo.gl/wXaqbi3OeH3bKEf62
Select MTP > update driver > browse my computer > let me pick > (standard MTP Device) > MTP USB Device
Sorry I'm not in front of my PC but I'm sure it's something like that to solve it
If that doesn't work? You can always use...
Code:
adb push ROM.zip /sdcard
Which will copy the zip file to the root of your data storage (on the Le Max 2 much like the One Plus 3 they use /Sdcard as a shortcut since we don't have external Sdcard hardware).
As for system read only? Swipe to allow modifications. Can't flash a ROM properly if the system is read only eh? Hence the failed to mount system.
It's really just there as a disclaimer to cover their ass in case people use TWRP improperly and brick their device. Following green man gaming's guide is safe as I've used it plus many other people as you'll see in his replies
I'd also recommend following the guide and flashing TWRP to your recovery. I only did boot recovery image for backup and then booted to EUI and copied that backup to my PC.
Format data is handy to get rid of encryption and also give you full access to your storage capacity because when I didn't before I didn't get 54.43GB of data storage only something like 40GB.
Tbh I haven't used any custom EUI ROMs but if you're fighting with TWRP? I know Cuoco92's eui has a fastboot installable version
Hope this helps
Well thank you so much for the information. I am running windows 10, but never saw mtp under portable devices, only the phone name Le Max 2. That's ok, as I booted (still not flashed) into recovery and this time I swiped to allow modifications. I still couldn't mount /system but I was able to use the adb push command and the SuperSU file appeared inside the /sdcard directory when looking under Install inside twrp. I swiped to flash the zip, then hit reboot system. Looking in the SuperSU app, I noticed that the setting "Install SuperSU into /system" is greyed out. Well, at least I think it worked.
At this point in time, since things appear to be working, I'll be flashing the recovery and installing OmniRom (it was either this or Resurrection Remix). I think if the play store just works on OmniRom like people mention, it'll be worth it.
So, my steps will be to:
adb -> fastboot -> fastboot flash recovery fileName.img
recovery -> wipe -> factory wipe (using factory to get rid of system encryption) -> reboot back into recovery
recovery -> wipe -> dalvik/cache (do i still need to do this after factory wipe?)
adb -> adb push romFileName.zip /sdcard
adb -> adb push gapps.zip /sdcard
recovery -> install -> /sdcard -> romFileName.zip
recover -> install -> /sdcard -> gapps.zip
At any point do I need to flash SuperSU again? I guess I should after flashing the rom/gapps because, afterall, SuperSU is an app.
Once again, thank you so much for all the information that you have already provided!
Heyyo, it's always recommended to do a full wipe when installing a different ROM so you should format data, wipe system, data, dalvik and cache and then install the ROM of choice with Gapps of choice
Wiping system is OK when flashing a ROM as it'll write into system.. plus there's always the risk of instability if system is not wiped if a Gremlin setting is left over from previous ROM
I'd recommend using Magisk v14.3 over SuperSU as SuperSU doesn't have the same functionality as Magisk for passing SafetyNet...
Plus Magisk is full open source software (FOSS) where as SuperSU is closed source so gotta love that open source (this part is more personal preference since Android is built upon open source and people working together).
Plus there's really cool Magisk modules you can do like ART Optimizer and so fourth if you check the XDA forum section for it
Also, you're welcome! We all had our start on XDA at different points and passing on the knowledge I find is just as important as the ROMs we love
Don't use SuperSU. Magisk is the way to go for rooting nowadays. Easy, systemless, updated frequently to pass safetynet. It's a no brainer.
Hey Guys,
as far as i could find out so far, you use TWRP to flash a Custom Rom from the Tablets Recovery Mode, this requires a rooted device, and to do this you flash a prerooted rom somehow, which includes TWRP already, which you then use to flash the rom you actually want on your device.
Another possibility was to flash a Kernel (with TWRP?) to get the same results...
Now I absolutely can´t find a tutorial for dummies, to do that, or find the required files.
After i found it kinda complicated to unlock the bootloader, since most of the tutorials didn´t even mention you need advanced mode and a special Google USB Driver from Sony´s Developer Page, to even get that working, i would really appreciate if someone could give me a step by step with links.
If a tutorial exists, pls give me a link as well, cause i looked the whole day yesterday, and found jack.
cheers
yes, you need to do all that. i just went through this yesterday and used this tutorial:
https://forum.xda-developers.com/showthread.php?t=2747676
once you are unlocked, follow the instructions for your rom, usually to flash the boot and recovery images with fastboot. two things to watch out for though, if you are using an oreo rom make sure your twrp version is 3.2 or better, secondly, if twrp give an error where it cant mount the partitions to wipe them use the change format option under wipe/advance to change to ext4 (which essentially re-formats the partition) and you should be good to flash the rom after that.
here is another tutorial to help get adb, fastboot, and the drivers up and going:
https://forum.xda-developers.com/showthread.php?t=2588979
answer yes to everything, i can't remember if i loaded in sony specific driver on top of that or not.
goodluck!
Hello! i have used the search tool to see if there is a custom recovery for my device but i am unable to find any. I found TB-X103F custom twrp but im unsure about trying it!.
I may be rather early as this tablet only recently came out.
Lenovo X 104F- 1 GB RAM
I own the same tablet , found also a solution to root it . Just to try other Custom ROMs you do not need to root it ....it is project TREBLE compatible ! This means that you can , with fastboot and ADB , install various GSI images )
ATTENTION : this method does not allow you to go back easily to the factory ROM !!! If you wish to do so, you need to root your Tab and make a full backup with one of the solutions described here in XDA ! Titanium or so .
I have installed Lineage 15 (Oreo 8) on my device and it runs without any problem ......Custom ROMs based on Pie make still some issues ! Be aware , that for one or other reason on my tablet i can install only ROM that is less than 1 GB after unzip !!!
Artarun said:
I own the same tablet , found also a solution to root it . Just to try other Custom ROMs you do not need to root it ....it is project TREBLE compatible ! This means that you can , with fastboot and ADB , install various GSI images )
ATTENTION : this method does not allow you to go back easily to the factory ROM !!! If you wish to do so, you need to root your Tab and make a full backup with one of the solutions described here in XDA ! Titanium or so .
I have installed Lineage 15 (Oreo 8) on my device and it runs without any problem ......Custom ROMs based on Pie make still some issues ! Be aware , that for one or other reason on my tablet i can install only ROM that is less than 1 GB after unzip !!!
Click to expand...
Click to collapse
Care to share any links?
Since Lenovo/Motorola added our E10 / TB-X104F to the recovery tool I decided to play around with hacking apart this awesome and terrible table. Long-story-short... you can unlock it using the normal FASTBOOT commands. A MAGISK modified BOOT.IMG does work which gave me full root access to the tablet. If people are interested I'll write up a guide... but a little bit of research on MAGISK and grabbing the Lenovo recovery tool will be your first step if starting from scratch.
Next step is getting a recovery image. I'm currently looking into getting this tablet into the TWRP BUILDER queue, but at the time of this writing their queue is full.
UPDATE: Just saw the TWRP BUILDER team has had everything on hold for over a month now. Guess I'll need to see about building this locally in my free time.
kpfx said:
Since Lenovo/Motorola added our E10 / TB-X104F to the recovery tool I decided to play around with hacking apart this awesome and terrible table. Long-story-short... you can unlock it using the normal FASTBOOT commands. A MAGISK modified BOOT.IMG does work which gave me full root access to the tablet. If people are interested I'll write up a guide... but a little bit of research on MAGISK and grabbing the Lenovo recovery tool will be your first step if starting from scratch.
Next step is getting a recovery image. I'm currently looking into getting this tablet into the TWRP BUILDER queue, but at the time of this writing their queue is full.
UPDATE: Just saw the TWRP BUILDER team has had everything on hold for over a month now. Guess I'll need to see about building this locally in my free time.
Click to expand...
Click to collapse
I've been looking for one also and was gonna see about working on one
Artarun said:
I own the same tablet , found also a solution to root it . Just to try other Custom ROMs you do not need to root it ....it is project TREBLE compatible ! This means that you can , with fastboot and ADB , install various GSI images )
ATTENTION : this method does not allow you to go back easily to the factory ROM !!! If you wish to do so, you need to root your Tab and make a full backup with one of the solutions described here in XDA ! Titanium or so .
I have installed Lineage 15 (Oreo 8) on my device and it runs without any problem ......Custom ROMs based on Pie make still some issues ! Be aware , that for one or other reason on my tablet i can install only ROM that is less than 1 GB after unzip !!!
Click to expand...
Click to collapse
I can attest to this, I flashed the last Resurrection Remix Oreo GSI (12/21/18) and a (Magisk) rooted kernal I got from firmware (Lenovo MOTO Smart Assistant). And so far everything seems to be working fine.
So I also flashed resurrection remix pie gsi... it works as well... only thing is it doesn't come with gapps... and without twrp i can't flash a gapps package. The resurrection remix I used was the final oreo build... zt has gapps pre-installed... you have to register the device with google because it is not certified... but after that everything seem good. One thing to mention is both the oreo and pie builds are "go edition" so some features are missing because of that... one in particular I noticed is notification access for 3rd party apps... go edition devices don't have that feature
Do either of you all have a step-by-step guide to rooting the device and installing either the Lineage or RR ROM?
Also, what works and what doesn't on the tablet afterwards?
44Guest said:
Do either of you all have a step-by-step guide to rooting the device and installing either the Lineage or RR ROM?
Also, what works and what doesn't on the tablet afterwards?
Click to expand...
Click to collapse
Use Lenovo MOTO Smart Assistant to repair your tablet (you wont actually repair tablet, just using to get firmware)
Follow steps to get to download the firmware (it will save to ProgramData folder, its hidden folder... in widows anyway)
Take the boot image (boot.img) from firmware folder and transfer to storage on tablet
Instal magisk manager and use to patch the boot image you transfered from computer
Transfer patched boot image back to computer
Download the latest oreo gsi for resurrection remix or lineage
Use fastboot to unlock bootloader
Use fast boot to flash gsi
Use fastboot to flash patched boot image
Google anything you need help with...
I used the resurrection remix oreo also because there is a build that has gapps pre-installed... the pie version works but doesn't have gapps pre-installed and without twrp I couldn't find a way to install them
After tablet boots up install magisk manager and you will be rooted
You will need to register your device with google because it will not be certified... that was a pain to get done even though the process is pretty straight forward
So far only "issues" I have encountered are not actually issues they are due to the fact that the resurrection remix gsi is android "go edition" I haventr tried lineage because I like the customization options that resurrection remix offers
Here is the magisk patched boot image I made so you can skip that part...
https://www.mediafire.com/download/x4d3xp8w3e8bw3g
Just to confirm the sequence of events (and thank you for the magisk-altered file):
1. Move magisk-modified boot image to the tablet.
2. Download latest version of Lineage OS or RR; move that file to the tablet as well
3. DL magisk manager APK and move that to the tablet as well
3. Boot the tablet into Bootloader and flash the new OS file first
fastboot flash recovery file.img
4. Then flash the boot.img altered by magisk
fastboot flash recovery boot.img
5. Reboot the tablet (will it load with the new ROM?)
6. Install magisk manager
Questions on the flashing:
A: Do you flash the .img and the ROM through fastboot shell command on your computer or do you install them in recovery mode?
4niner4 said:
Just to confirm the sequence of events (and thank you for the magisk-altered file):
1. Move magisk-modified boot image to the tablet.
2. Download latest version of Lineage OS or RR; move that file to the tablet as well
3. DL magisk manager APK and move that to the tablet as well
3. Boot the tablet into Bootloader and flash the new OS file first
fastboot flash recovery file.img
4. Then flash the boot.img altered by magisk
fastboot flash recovery boot.img
5. Reboot the tablet (will it load with the new ROM?)
6. Install magisk manager
Questions on the flashing:
A: Do you flash the .img and the ROM through fastboot shell command on your computer or do you install them in recovery mode?
Click to expand...
Click to collapse
So you want all files on the computer at first...
When you unlock bootloader it will wipe the tablet.
Flash the the gsi image then the magisk patched boot image using fastboot (there are instructions on xda regarding flashining gsi... you have to wipe system before flashing)
After tablet reboots to resurrection remix move the magisk manager apk to the tablet and install it... open magisk manager and you should have magisk installed giving you root and so much more.
Before you attempt this make sure you familiarize yourself with all the steps... search google/xda.
Also... I will say this... I tried to just root the tablet first but it wouldn't boot after so I tried to fix it using the Lenove tool and it failed... flashing the resurrection remix gsi with the patched boot image saved me from a lot of headache and wasted time... I would prefer if it was not a "go edition" rom but its still better than stock.
Sorry, more follow-up questions:
1. My bootloader is unlocked. It did not wipe the device (I used the "developer options" in the "Settings" menu to do it. Fastboot indicates the bootloader is unlocked. Do I need to redo unlocking the bootloader? For what it's worth, all my attempts to flash everything with my presumably unlocked bootloader have been unsuccessful.
2. Where did you find a .gsi of Lineage OS 15 for the Lenovo TB-X104F? I cannot find one.
Thanks
4niner5 said:
Sorry, more follow-up questions:
1. My bootloader is unlocked. It did not wipe the device (I used the "developer options" in the "Settings" menu to do it. Fastboot indicates the bootloader is unlocked. Do I need to redo unlocking the bootloader? For what it's worth, all my attempts to flash everything with my presumably unlocked bootloader have been unsuccessful.
2. Where did you find a .gsi of Lineage OS 15 for the Lenovo TB-X104F? I cannot find one.
Thanks
Click to expand...
Click to collapse
Make sure you fastboot flash unlock and fastboot flash unlock_critical. Just look an here for the links for lineage gsi. It flashes just fine and is super easy. I have resurrection remix on my 104f. I'm trying to compile twrp for it right now but hard to do with kids lol also if you use the lenovo tool you can download the recovery files which has boot recovery and all that in it and you can use magisk to patch the boot.ing and then copy that to the Lenovo tool and replace the stock boot img then recover it and you now have a working patched boot.img. I went through the same thing
Any Luck?
Any luck with that twrp? I'm willing to test it out...
Would like to be able to use the resurrection remix pie rom with gapps. So I can hopefully give some helpful feedback... one warning I am an amateur at anything beyond using fastboot and some adb commands, but I can learn pretty quick if i have the time to spend...
Another warning I have a sub-par windows pc to work with (and its the wife's) it prob can't run Linux in VM.
Disable "go edition" in Resurrection Remix Oreo
Using root explorer...
Navigate to /system
Copy build.prop to internal storage
Navigate to where you saved copy of build.prop
Edit build.prop that you copied to internal storage...
Find ro.config.low_ram=true and change to ro.config.low_ram=false
Save and exit file
Copy edited build.prop back to /system (make backup of original and overwrite with edited one)
Set permissions to owner read write (rw-------)
Navigate to /sbin/.magisk/mirror/system
Copy build.prop to internal storage
Navigate to where you saved copy of build.prop
Edit build.prop that you copied to internal storage...
Find ro.config.low_ram=true and change to ro.config.low_ram=false
Save and exit file
Copy edited build.prop back to /sbin/.magisk/mirror/system (make backup of original and overwrite with edited one)
Set permissions to owner read write (rw-------)
Reboot
This allowed me to set notification access again (its disabled in "go edition")
Hey guys, I'm trying to follow the steps in this thread to install Resurrection Remix Pie on the tablet using fastboot but whenever I try to flash a ROM to the system partition I get a (remote: size too large) error.. Does anyone know why this could be? I've tried using flags like -S, I've wiped the partitions and I don't know what else I can try. I have tried with Lineage, AOSiP and RR GSIs.
Thanks.
I cant get this to work.. What version of RR or Lineage OS works with tb-x104f?
up..................
I got the final version of rr oreo running fine... no luck with the latest rr pie unfortunately...
Anyone know if this is an A or AB device?
Since i am newbie to this forum and all this rooting stuff, i am lately confused about lot of stuff about poco f1 in respect of flashing new rom over miui rom and also over some other custom rom plus back up/restore of existing rom.
I faced lot of problems of encryption and decryption and had to format my phone number of times. I am listing out few procedure for installing new rom over other customer rom and miui rom which i learned from this wonderful forum plus also the procedure of backing up your existing rom. So request all the experience developers to guide newbie like us step wise so we can also enjoy the fruitful advantage of this lovely forum.
for installing new rom i learned from this link https://forum.xda-developers.com/poco-f1/help/to-custom-rom-want-to-install-rom-t3902913 to follow the below mentioned procedure. I also posted my respective questions along with this step for answer from my beloved developers.
1. Remove pattern and pin. If you don't do this step then you will have to factory reset your phone with stock MIUI. (Is it compulsory to remove pattern and pin, what if we remove lock screen password by simply deleting these files from twrp
1.gatekeeper password key
2.gatekeeper pattern key
3.locksettings.db
4.locksettings.db-shm
5.locksettings.db-wal
will there be a problem)
2. Wipe all except internal storage and external storage.(this is understood)
3. Flash vendor and rom.(do i really need to flash vendor before flashing rom and this is applicable to all the custom roms i mean if i have pixel rom and want to install nytrogen rom, do i need to flash vendor all the time....plus where can i get this vendor file, can anyone provide a link for that)
4. Flash disableforceencryption with magisk 18.0.(this is very important to me, what is disableforceencryption file do,do i need to flash every time whenever i try to flash new custom rom)
5. Flash your twrp again so it isn't replaced by stock.(i still did not understand this part but still which twrp to flash official one or unofficial one, since official one gave me lot of trouble so i had to revert back to unofficial one, kindly provide your input in this)
Further for backing up your existing rom following steps have been learned from some different thread, kindly provide your input whether the same is right or wrong.
System image
Vendor image
Boot
Data
Modem
Efs
Please co-operate on this because lot of newbie like me facing different problem, your valuable input can bring smile on our faces.
Thanks in advance.
mandyady said:
Since i am newbie to this forum and all this rooting stuff, i am lately confused about lot of stuff about poco f1 in respect of flashing new rom over miui rom and also over some other custom rom plus back up/restore of existing rom.
I faced lot of problems of encryption and decryption and had to format my phone number of times. I am listing out few procedure for installing new rom over other customer rom and miui rom which i learned from this wonderful forum plus also the procedure of backing up your existing rom. So request all the experience developers to guide newbie like us step wise so we can also enjoy the fruitful advantage of this lovely forum.
for installing new rom i learned from this link https://forum.xda-developers.com/poco-f1/help/to-custom-rom-want-to-install-rom-t3902913 to follow the below mentioned procedure. I also posted my respective questions along with this step for answer from my beloved developers.
1. Remove pattern and pin. If you don't do this step then you will have to factory reset your phone with stock MIUI. (Is it compulsory to remove pattern and pin, what if we remove lock screen password by simply deleting these files from twrp
1.gatekeeper password key
2.gatekeeper pattern key
3.locksettings.db
4.locksettings.db-shm
5.locksettings.db-wal
will there be a problem)
2. Wipe all except internal storage and external storage.(this is understood)
3. Flash vendor and rom.(do i really need to flash vendor before flashing rom and this is applicable to all the custom roms i mean if i have pixel rom and want to install nytrogen rom, do i need to flash vendor all the time....plus where can i get this vendor file, can anyone provide a link for that)
4. Flash disableforceencryption with magisk 18.0.(this is very important to me, what is disableforceencryption file do,do i need to flash every time whenever i try to flash new custom rom)
5. Flash your twrp again so it isn't replaced by stock.(i still did not understand this part but still which twrp to flash official one or unofficial one, since official one gave me lot of trouble so i had to revert back to unofficial one, kindly provide your input in this)
Further for backing up your existing rom following steps have been learned from some different thread, kindly provide your input whether the same is right or wrong.
System image
Vendor image
Boot
Data
Modem
Efs
Please co-operate on this because lot of newbie like me facing different problem, your valuable input can bring smile on our faces.
Thanks in advance.
Click to expand...
Click to collapse
1. Yes, if you are able to find all the files related to locks, then you can delete them and boot. But it is much easier to remove the locks before flashing the new ROM.
3. Vendor firmware has to be flashed if you wipe. Also when some custom ROM specifically asks for a particular version of vendor firmware. The vendor firmware can be found on the download page of Xiaomi.
4. When the OEM ROM is flashed, it will encrypt your phone. Custom ROMs require unencrypted phone (some of them don't). But the TWRP now handles encryption/decryption and so, in my opinion, you don't need DFE zip at all if you have the correct TWRP (you already seem to have it).
5. If you are flashing OEM ROM, the built in recovery will overwrite the TWRP. To avoid this, you can flash Magisk immediately after flashing the ROM, before booting. It will preserve TWRP. No need for re-flashing TWRP if you are flashing custom ROM since they do not have in-built recovery. Further, I understand that the unofficial TWRP handles encryption/decryption better. So stick with it unless you have problems with it.
If you backup all the partitions, you can choose which ones to restore, the downside being that a lot of space will be required. But it is safer.
Hope you are smiling!
So, this is the first time I'm installing a custom rom and I was following along with this guy:
(I found the xda steps to be too confusing to follow) and everything was going just fine until around the 5.20 min mark where after flashing TWERP on the device through Odin I was supposed to press the volume - & the power key to restart the device and as soon as the device went black I was supposed to then press volume + & the power key which I did but then I got this: (attachment)
(btw, even when I don't press the volume + & power key afterwards I get the same result)
Can this still be fixed or have I bricked my device?
Hi @Winter413
I found a wonderful description on the installation of TWRP here .... maybe it's easier to follow though it's for the 8.
Just read the whole story .... your troubles while installing TWRP are not at all new.
It's a kind of trick which you learn as soon as you want to root your phone, or want a good user friendly recovery backup app.
HELP! S8 got bricked, can't access recovery mode and OEM is locked
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got an error where it reset my data, after data reset I was stuck at the boot screen with the logo . I've tried steps like flashing stock rom, odin...
forum.xda-developers.com
Hope it might be of help ....
Nice Sunday for you !
Here on the forum you will be able to meet all the specialists you need.
[RECOVERY] [OFFICIAL] TWRP 3.6.x for Galaxy A10 Exynos series [SM-A105] [4 January 2022]
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
Hi @xabu
First I'd like to greatly apologise you for answering so late. I did not mean to be rude I just didn't want to reply with "ok, I'll be working on it than" & I actually wanted to get something done first. I decided to do things that way becouse I thought that I'll find some time to do this rather soon however unexpected things happened that kept me from doing it but now I have some time & have done something in this regard so enough of my excuses let's get to what I did & what I want to ask you about:
So first I went onto the s8 thread you suggested & I flashed vbmeta_disabled & to my suprise when I restarted again & pressed volume up + power it actually booted into TWRP "and relief washed over me in an awesome wave" but then I went on to get lineage os on it and it doesn't show up in TWRP. I have also gotten some other stuff (magisk & a few files from NanoDroid) & those show up just fine. I got the file from here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/
& the link I got from this thread: https://forum.xda-developers.com/t/rom-gsi-guide-lineage-os-a10-a105f.4078093/
& as far as I'm concerned that is the only thread about lineage os on this phone on xda so that doesn't work I guess.
I have also tried this: http://www.mediafire.com/file/4w6vaq4lu2tbjfj/lineage-17.0-20200110-UNOFFICIAL.zip/file
& this: https://mega.nz/file/gw4QTYSS#IqqswGusWIW5l10LyvSfmtVUoE4gqn6_g6jywH96Z5Q
& got this:
(I've done these sequentially but I hope that doesn't make any functional difference however one important thing is the first one goes 'till the first "done" and the second one is the rest. You surely could figure that out by yourself but I wrote this just for clarity's sake.)
P.S. I know that both of the error messages I got seem to refer in one way or another to the fact that I'm not using an sd card for this operation, however as far as I'm concerned it should also be possible to install lineage os to the internal storage of the phone & that is what I want to achieve with this.
P.S. 2
I forgot to mention that I obviously wiped everything properly before trying to install lineage os so that's not the problem.
Hi Winter ,
it's important to check if you found the right version of TWRP:
Samsung Galaxy A10
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
every other version might get you in trouble.
And then: there is still no official LineageOS for the A10 (this gives problems too)
[ROM] [GSI] [GUIDE] Lineage os A10 A105F
A guide for how to install Lineage OS [ GSI ] on Samsung A10 A105F Notes / Warning! Use at your own risk, I’m not responsible for bricking your device. Make sure to backup your important data before everything. here is a summary of the steps I...
forum.xda-developers.com
should be the place to be, though there is not too much activity there ...
but look at this thread too:
Samsung Galaxy A10 ROMs, Kernels, Recoveries, & Ot
Improve your Samsung Galaxy A10's battery life, performance, and look by rooting it and installing a custom ROM, kernel, and more.
forum.xda-developers.com
with many good ideas.
Whatever:
I learned that LineageOS should be installed before other additions like Magisk and G-apps. Do this from internal storage and not from an external sd-card.
In TWRP we always make a Zip queue before installing but always starting with the OS or ROM.
You should be successful now you experienced how to install TWRP.
Always check for the right version or ask in the threads.
Thanks for coming back to me though I just wanted to help you
with installing TWRP and I don't have a A10 at my disposal.
Sincerely @xabu
Ps: I saw that you had courage enough to experiment. Be careful but go for it.
Hi @xabu
So as I mention I made it work by flashing this file through odin while in dowload mode & then restarting & pressing the volume up + power buttons which was supposed to take me to twrp & it did & twrp for me seems to be working just fine so I'm a little hesitant to try & install some different version of it but if you think that's the issue than I will try installing those other versions.
As soon as you are in TWRP and it functions fine, then just look to it's version and go to the link which I gave you for the newest version of TWRP for the A10.
"
If you intend to root your (a10) device, be advised that Magisk will be installed to the recovery partition, not the usual boot partition. Both TWRP and Magisk-rooted Android boot using the recovery kernel, with the device's hardware keys used to choose between TWRP and Android at boot time.
You are therefore strongly advised to first root your device with Magisk and then pre-root a TWRP image before flashing it to recovery. The usual path of installing TWRP prior to rooting is problematic on this device, because the Magisk installer does not support installation to recovery from TWRP. Furthermore, prior rooting of the device with Magisk carries the significant advantage of disabling various device protection mechanisms that you will otherwise need to take care of manually."
In this website the instructions about flashing TWRP to your device goes further .... so try to understand it step by step.
If you want to install Magisk, then you should know that from some weeks ago, Magisk started a complete new life with new important instructions: look here:
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
As you can see .... there is a lot to do and to learn.
Hope you'll enjoy it like your
"and relief washed over me in an awesome wave"
no one could have said it better .
PS:
Flashing TWRP without first flashing a vbmeta image with verity disabled will render your device unable to boot.
is especially for your kind of device and certainly not in general.
Alright, so I checked my twrp version with your link & I have the latest one so everything is fine. I also got lineage os 18.1 & it seems to have installed just fine. So now it's time for Magisk. So first I'm also kinda following this guide:
& Wolfgang recommends to not only install the .zip file but also Magisk manager & I couldn't find any link to download it.
"The usual path of installing TWRP prior to rooting is problematic on this device, because the Magisk installer does not support installation to recovery from TWRP" so does that mean that I have to go back to the download mode & from there flash the root file in odin & then install magisk.apk like here?:
2. flash root file:
enter download mode ( see instructions above here )
flash the file in Odin ( choose PDA, select the file and the start )
3. install magisk:
install magisk.apk (download link above here > and then follow the instructions in the app (the app will ask once for reboot).
Also, If you're curious, the "and relief washed over me in an awesome wave" is an almost direct quote (I only changed "washes" to "washed") from my favourite movie - American Psycho.
@xabu
If you liked my previous post, does that mean that I should do the steps I mentioned?
Dearest @Winter413 ....
No, this does not mean that you should do the steps mentioned.
Again read the instructions on the official TWRP where they help you with Magisk. You can always upgrade the moment all works.
I'm not familiar enough with your device. All is working here on the S7.
A complete different device as I noticed while studying your situation.
My like also shows my admiration for your courage to root your phone and try out how to go further and further.
Ps: https://github.com/topjohnwu/Magisk/releases/tag/v24.1
What about Magisk Manager? Do I need that?
And also this :
2. flash root file:
enter download mode ( see instructions above here )
flash the file in Odin ( choose PDA, select the file and the start )
3. install magisk:
install magisk.apk (download link above here > and then follow the instructions in the app (the app will ask once for reboot).
Is from this:
https://forum.xda-developers.com/t/rom-gsi-guide-lineage-os-a10-a105f.4078093/#post-82196787
So that's why I asked where or not I should back off to the download screen and flash the root.
Winter413 said:
And also this :
2. flash root file:
enter download mode ( see instructions above here )
flash the file in Odin ( choose PDA, select the file and the start )
3. install magisk:
install magisk.apk (download link above here > and then follow the instructions in the app (the app will ask once for reboot).
Is from this:
https://forum.xda-developers.com/t/rom-gsi-guide-lineage-os-a10-a105f.4078093/#post-82196787
So that's why I asked where or not I should back off to the download screen and flash the root.
Click to expand...
Click to collapse
Yes you need the new Magisk manager. If you want a rooted phone.
But as I told you....Magisk is changed maybe a month ago .... this means totally new instructions ... so keep this in mind while working with older instructions.
And also regarding the root - If I've gone this far than I might as well go further & attain some more control over my device & also learn a bit about how computers work along the way. This is definitely not the last project of this kind that I'll be doing. I'm already running Pop os on my main computer instead of windows (however I did use windows for this whole process as Odin is unfortunately unavailable for linux). For now I'm also very very slowly learning javascript (I'll try to pick up the pace cuz it's really bad) & once I buy myself a new computer I'll try installing arch on it & using that as my daily driver & yeah, further carrer routes in IT & such are definitely also something that I'll be looking into so while pretty inconmpetent I'm not afraid to play around with computers.
Alright than. If everything is different about Magisk now than I will definitely look into how to properly install both Magisk.zip & Magisk Manager.
So I must admit I haven't looked to much into rooting yet & it seems that It is not required to install a custom rom, however this sounds pretty cool:
Advantages of rooting include the possibility for complete control over the look and feel of the device. As a superuser has access to the device's system files, all aspects of the operating system can be customized with the only real limitation being the level of coding expertise. mmediately expectable advantages of rooted devices include the following:
1. Support for theming, allowing everything to be visually changed from the color of the battery icon to the boot animation that appears while the device is booting, and more.
2. Full control of the kernel, which, for example, allows overclocking and underclocking the CPU and GPU.
3. Full application control, including the ability to fully backup, restore, or batch-edit applications, or to remove bloatware that comes pre-installed on some phones.
4. Custom automated system-level processes through the use of third-party applications.
5. Ability to install software (such as Xposed, Magisk, SuperSU, BusyBox, etc.) that allows additional levels of control on a rooted device or management of root access.
Winter413 said:
Alright than. If everything is different about Magisk now than I will definitely look into how to properly install both Magisk.zip & Magisk Manager.
Click to expand...
Click to collapse
Yes learn about the denylist and Zygisk !
So from my understanding currently the steps left are:
1. installing Magisk.zip & Magisk Manager
2. Installing NanoDroid
3. & perhaps locking my bootloader afterwards to make my device more secure? (I think that's something that should be done but correct me If I'm wrong)
& then I can finally start using my phone on Lineage os, right?