Hi everyone,
I'm new here though but am a Xiaomi user from the beggining of Xiaomi into devices with Redmi Note 3G Enhanced.
Currently, I own a Redmi 4X and I would like your expert lights please. I've flashed the latest twrp from twrp.me for my santoni device. Then flashed the latest build from LineageOS Official source + Gapps before booting up for first time. Everything was working perfectly until I decided to flash the latest update of LineageOS as I've seen in my updater it was released. So, I downloaded it through the updater and tried to flash it...
I came up with this "Failed to unmount /system (device or resource busy)" after that re-booted to LineageOS and everything was messed up with Google Services & Apps etc. Then I went back to twrp recovery and tried to flash again the rom but I was still getting that message so I understood something am doing wrong. Also santoni has dm-verity enabled which I know something about but just an info. I really wanna stick with LineageOS on my Redmi 4X forever but I'm afraid to flash it again. I've flashed MIUI 10 Beta by fastboot but now I wanna go back to LineageOS forever (addicted).
My only problem is: After successfuly flashing LineageOS and Gapps, I cannot apply (flash) updates to update the ROM to the latest nightly build due to this error above.
Kind regards,
peryson
Try with different recovery. For example with this
Harukey said:
Try with different recovery. For example with this
Click to expand...
Click to collapse
Instead of trying an unofficial recovery, do I have an option to unmount system manually before flashing through Official TWRP?
peryson said:
Instead of trying an unofficial recovery, do I have an option to unmount system manually before flashing through Official TWRP?
Click to expand...
Click to collapse
You can download latest Lineage OS build and dirty flash it (without any wipes) (so you can unmout system parition). And I don't see any issue in using unoffical twrp.
I also have experienced same error once during upgrade "failed to unmount /system"
Eventually I wiped everything and did clean flash from scratch. This is really annoying issue and demonstrates that upgrade system is not 100% reliable for some reason.
I'm not sure however is it Lineage or twrp issue.
I am not responsible for bricked devices, or any other hardware malfunctions that come as a result of flashing anything. Please do some research if you have any concerns about features included in this ROM before flashing it
Hey everyone,
I am writing this guide because I spend all day trying to figure out how to upgrade my grandma's tablet from android 7 TouchWiz to android 9 pie. I did not create any of the files that I am about to link just putting all the info in one place because I feel it's needed.
Before starting my grandam's tablet was running android 7.0 TouchWiz. So if you are in the same situation do the following.
Download the following
Odin3-v3-10-7
SM-T350 Marshmallow Firmware (check second post for faster mirror)
TWRP-3.2.1
PIE ROM of Choice
Open Gapps (Remember Platform: ARM | Android Version : 9.0| Variants: Your Choice)
Root (Optional): Magisk
Instructions
1. Put your tablet in download mode by turning it off then pressing and hold [Power] [Vol-Down] & [Home] at the same time till a cyan warning screen appear.
2. Press Volume Up to Continue.
3. Connect the Tablet to the computer via USB stick
4. Extract the Odin and Marshmallow Firmware zip files and place it on the desktop
5. Run Odin and make sure you can see your device
6. Click on [AP] button and find the marshmallow firmware. Let Odin verify the file (take a second) then click start to begin the flashing process
7. After flashing the firmware the tablet will reboot and just wait for the welcome screen.
8. In the welcome screen skip everything till you get to the home screen then turn the tablet off and put it back into download mode (see step 1)
9. Now your tablet should still be connected to the computer and Odin should still be open.
10. In Odin go to the second tab (OPTIONS) and uncheck Auto Reboot (VERY IMPORTANT)
11. Now click on the [AP] button and find the TWRP zip file then click start to flash it
12. After the flashing process has been successful press and hold [Power] [Vol-Down] & [Home] to reboot. AS SOON AS THE SCREEN GOES BLACK LET GO OFF THE BUTTONS AND PRESS AND HOLD [POWER] [VOL-UP] and [ HOME] AT THE SAME TIME.
13. If you did it right you should be in TWRP. If not you have to repeat step 11 and 12
14. Make a NANBACKUP in TWRP and copy it to your computer
15. After that copy the PIE ROM and GAPP of your choice. (MAGISK IF YOU WANT ROOT) to the internal memory card or sd card whichever you have. I don't have an SD card so I copied it to the internal memory
16. In TWRP Wipe the System, Cache, Data and ART/Dalvik cache. (Recommended)
17. Flash the ROM, GAPPS
18. Flash the root solution of your choice (optional).
19. Reboot your device.
Thanks to @lividhen99 for the post that I got all this info
Thanks to everyone who creates and ported recoveries and ROM to this device. My grandma appreciated it ( we both hate TouchWiz)
PS. I will eventually come back and make a mirror of the marshmallow firmware file because it is so long and slow. If anyone wants to beat me to it please do
https://drive.google.com/open?id=1WyafpwMlGbBmocWhwhHxcrtgS0mFpoes
Heres a google drive mirror.
Is there a 64 bit version of Android Pie for the SM-T350? After following these instructions I couldn't install the 64 bit version of GApps, said it was not compatible. Is that a holdover from the Marshmallow firmware? The SM-T350 supposedly has an ARM 64bit processor so you'd think it could take the 64 bit GApps install but after these updates it shows that it'e the 32 bit version of Pie. I know I'm kind of rambling here but I guess you can follow what I'm trying to do. Thanks!
is this compatible with the sm-p355?
Is it necessary to do this from Marshmallow 6? Will this procedure work for Nougat 7.1.1?
Wimmer4Archery said:
Is it necessary to do this from Marshmallow 6? Will this procedure work for Nougat 7.1.1?
Click to expand...
Click to collapse
It should technically work, but if you get a black screen, downgrade to marshmallow and try again. Not all devices need to be downgraded, and nobody knows why
Great, thanks for the info! This sounds like a, great summer project while we are all locked in quarantine.
2 different PIE roms, when I follow the path to add an account (google) the screen goes black with small top bar icons and does not allow the process to continue (setup). which specific ROMS have worked>
ygthb said:
2 different PIE roms, when I follow the path to add an account (google) the screen goes black with small top bar icons and does not allow the process to continue (setup). which specific ROMS have worked>
Click to expand...
Click to collapse
Same issue. Hopefully someone has an answer
sunnyd71 said:
Same issue. Hopefully someone has an answer
Click to expand...
Click to collapse
Could you and ygthb send me the links for the rom's forums? in fact, you might want to ask the question on the rom's respective forum.
lividhen99 said:
Could you and ygthb send me the links for the rom's forums?
Click to expand...
Click to collapse
if ur talking about a tab a then youre in it already
elliwigy said:
if ur talking about a tab a then youre in it already
Click to expand...
Click to collapse
This is a thread on how to install roms on this device, it provides no roms besides the marshmallow one to fix the black screen issue.
Trying to get this to work, everything is fine until I try to load the new ROM and GAps, it's giving me error 7, specifically this:
- Confirming target device...
mount: Failed to mount /dev/block/by-name/vendor at /vendor: No such
file or directory
ui_print(): Failed to parse the argument(s)
Updater process ended with ERROR: 7
browenb said:
Trying to get this to work, everything is fine until I try to load the new ROM and GAps, it's giving me error 7, specifically this:
- Confirming target device...
mount: Failed to mount /dev/block/by-name/vendor at /vendor: No such
file or directory
ui_print(): Failed to parse the argument(s)
Updater process ended with ERROR: 7
Click to expand...
Click to collapse
What partitions did you wipe?
I might be a little late posting here but I am currently trying this with the SM-T350 that came with 7.1.1 and for some reason when I load the Marshmallow firmware to my tablet it never actually boots, it gets as far as flashing the Samsung logo on a black background then says Touchwiz.exe has encountered an error. Am I doing something wrong? I am following the instructions word for word as far as I can tell.
The marshmallow firmware never has to boot. If you want it to boot, factory reset (wipe data and dalvik cache). But you wipe system data and cache anyway when you install a rom.
lividhen99 said:
The marshmallow firmware never has to boot. If you want it to boot, factory reset (wipe data and dalvik cache). But you wipe system data and cache anyway when you install a rom.
Click to expand...
Click to collapse
Basically I just want to use TWRP to flash Magisk and use it to spoof for Pokemon Go. I did it previously on a Galaxy S5 but I never had a problem booting into the OS and just turning the phone off when I wanted to boot into recovery mode (TWRP) so I don't really know what I am doing but I am assuming I need it to boot normally for magisk to root the device. Unfortantely when I try to flash TWRP with the 7.1.1 firmware that comes stock on the device recovery just boots to a black screen so searching around has led me to the conclusion I need to downgrade to Marshmallow then try flashing TWRP but I never expected it to not boot normally xD Sorry this is a bit outside of my technical knowledge to say the least.
---------- Post added at 01:05 AM ---------- Previous post was at 12:50 AM ----------
I believe I understand what I need to do now. I managed to load into TWRP so at that point I can just flash any rom and use magisk to root. Any particular one you might suggest? Thanks for all the help by the way!
Gemininja said:
Basically I just want to use TWRP to flash Magisk and use it to spoof for Pokemon Go. I did it previously on a Galaxy S5 but I never had a problem booting into the OS and just turning the phone off when I wanted to boot into recovery mode (TWRP) so I don't really know what I am doing but I am assuming I need it to boot normally for magisk to root the device. Unfortantely when I try to flash TWRP with the 7.1.1 firmware that comes stock on the device recovery just boots to a black screen so searching around has led me to the conclusion I need to downgrade to Marshmallow then try flashing TWRP but I never expected it to not boot normally xD Sorry this is a bit outside of my technical knowledge to say the least.
---------- Post added at 01:05 AM ---------- Previous post was at 12:50 AM ----------
I believe I understand what I need to do now. I managed to load into TWRP so at that point I can just flash any rom and use magisk to root. Any particular one you might suggest? Thanks for all the help by the way!
Click to expand...
Click to collapse
OH! Well, now that you have that specific version of twrp booted, I would recomend either lineage os or crdroid for the SM-T350. If you just want stock Samsung, you can reflash the stock 7.1.1 firmware and grab the Nougat twrp for the sm-T355 from ashyx's galaxy tab a twrp page here: https://forum.xda-developers.com/galaxy-tab-a/development/recovery-t3426560 . It will boot on Nougat (7.1.1) but it cannot flash android pie (9.0) or Q (10.0) roms. It can still flash magisk though.
Crdroid (I released a newer build on the second to last page ?): https://forum.xda-developers.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t3912517/page32
Lineage: https://forum.xda-developers.com/galaxy-tab-a/development/rom-t3903258/page31
If you do end up flashing a custom rom, just wipe system, data, cache, and dalvik cache. Then flash the ROM zip, the gapps zip, and the magisk tnstaller zip. Just remember to enable magisk hide to pass safetynet whether you go custom rom, or not.
If you want the marshmallow firmware to boot, I think just wipe cache and dalvik cache. If that doesn't work, wipe data.
Wiping data will delete all your apps and settings and passwords, etc. It is essentially a factoy reset.
64 bit
Bookworm214 said:
Is there a 64 bit version of Android Pie for the SM-T350? After following these instructions I couldn't install the 64 bit version of GApps, said it was not compatible. Is that a holdover from the Marshmallow firmware? The SM-T350 supposedly has an ARM 64bit processor so you'd think it could take the 64 bit GApps install but after these updates it shows that it'e the 32 bit version of Pie. I know I'm kind of rambling here but I guess you can follow what I'm trying to do. Thanks!
Click to expand...
Click to collapse
the device isnt capable of running ARM64 however you can find regular ARM variants of lineageOS (what i used instead of flashing the stock firmware) and of gapps. my galaxy tab a (sm-t350) now runs android 10 and gapps 10.0 full, through this guide. just ignore the first software package and continue with the guide.
help! flashed from stock firmware (i don't remember version)...after a lot of time, is in the wizard section with a lot of error (unfortunately the process xxx has stopped), and the tablet reboot...what should i do?
I have installed the B895 ROM, downloaded from https://androidfilehost.com/?fid=961840155545586099.
Also i have a question - will the Sim-Lock go away if i flash LineageOS?
Can someone tell me if there is a ROM without Vodafone SIM Lock? Also i have installed TWRP from there:
[Recovery][BKL][EMUI 8.x only][Unofficial]TWRP 3.2.1-0 [14/04/2018]
Disclaimer This software comes wth no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device. Note: Currently Oreo 8.1 custom roms are supported only on BKL-L04 with EMUI 8.1 Download...
forum.xda-developers.com
Also i installed Magisk with TWRP, it seems that it has worked, because when i select internal storage over TWRP Menu it shows the capacity of it.
But i cannot open Magisk in System, it only displays it as an android app.
Also if i try installing LineageOS from
https://forum.xda-developers.com/t/rom-ota-7-1-2-lineageos-14-1-for-p8-lite.3824247/
It displays the output in the attached picture. Does someone know a workaround for that?
i tried to flash project sakura 5.1 with latest twrp which shows succeeded on terminal but it doesn't boot into system instead it booted into bootloader. i tried with older twrp and older versions of project sakura too, nothing worked. but the another rom called HariRom based on oneUI3.1 successfully flashed and booted normally to system. also i tried with another custom recovery called orangefox, which shows the boot cannot be located as error for all version of project sakura. can somebody help me with it?? i wish to install project sakura 5.1
ChapagainAB said:
i tried to flash project sakura 5.1 with latest twrp which shows succeeded on terminal but it doesn't boot into system instead it booted into bootloader. i tried with older twrp and older versions of project sakura too, nothing worked. but the another rom called HariRom based on oneUI3.1 successfully flashed and booted normally to system. also i tried with another custom recovery called orangefox, which shows the boot cannot be located as error for all version of project sakura. can somebody help me with it?? i wish to install project sakura 5.1
Click to expand...
Click to collapse
[EOL][ROM] [11] Project Sakura 5.1 [OFFICIAL] | VANILLA
does this rom have a working aod for samsung galaxy a40?
forum.xda-developers.com
Follow from here
Kenora_I said:
[EOL][ROM] [11] Project Sakura 5.1 [OFFICIAL] | VANILLA
does this rom have a working aod for samsung galaxy a40?
forum.xda-developers.com
Follow from here
Click to expand...
Click to collapse
i followed that in my first try which didnt worked and after that i tried other recoveries and versions of sakura . that didnt helped.
my phone is not rooted by the way
How to fix bootloops after coming from OneUI 3.x ports
1) Boot to TWRP
2) Download this vendor image
3) Install --> Flash image --> select image --> select vendor
4) Flash Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip from here
5) Flash the ROM.zip
i did installed vendor img but didnt find the option to wipe vender. and also i have tried installing dm-verity zip too. idk what that did but it was installed successfully and still didnt booted to system
Kenora_I said:
How to fix bootloops after coming from OneUI 3.x ports
1) Boot to TWRP
2) Wipe Vendor
3) Download this vendor image
4) Install --> Flash image --> select image --> select vendor
5) Flash Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip from here
6) Flash the ROM.zip
Click to expand...
Click to collapse
Actually no need i removed it.
So wiping vendor is in advanced wipe area in twrp. Dont reboot after it.
Then flash the image like i said.
Then flash the dm verity thing then flash the rom.zip
Kenora_I said:
So wiping vendor is in advanced wipe area in twrp. Dont reboot after it.
Then flash the image like i said.
Then flash the dm verity thing then flash the rom.zip
Click to expand...
Click to collapse
@Haridhayal i did installed it to my phone. version 5.2 actually. but its lagging, its overheating than stock rom while gaming. And mainly it crashes whenever i try to add security lock neither of the security option works . and i played call of duty mobile for some time and it quit automatically after some like 10 to 15 min. also the camera UI is terrible altho it captured well. and my phone did support fast charging on stock rom which now doesnot supported by project sakura. it takes almost 4-5 hours to get fully charged. what the hell happened with that?
ChapagainAB said:
@Haridhayal i did installed it to my phone. version 5.2 actually. but its lagging, its overheating than stock rom while gaming. And mainly it crashes whenever i try to add security lock neither of the security option works . and i played call of duty mobile for some time and it quit automatically after some like 10 to 15 min. also the camera UI is terrible altho it captured well. and my phone did support fast charging on stock rom which now doesnot supported by project sakura. it takes almost 4-5 hours to get fully charged. what the hell happened with that?
Click to expand...
Click to collapse
So it worked? It booted?
Yes, some features arent supported for some custom ROMs. Keep in mind custom ROMS won't perform like stock. Stock ROMS are made by people with the correct tools and 100% knowledge about the specific phone you are using sooooo....
Hello, ive been trying to download a GSI for like 3 days but it seems impossible because it keeps booting me into Odin Mode everytime. Heres the steps i did:
1. Go into Odin Mode
2. Flash TWRP
3. Format Data
4. Wipe Dalvik ,Cache, Data,System
5. Flash the Android 13 (i also tried with the LineageOS one too)
6. reboot to recovery
7. Flash Magisk
I have tried not flashing Magisk but it just puts me in infinite boot
Use older Android versions, for Android 13 you need probably fixed/updated vendor. Follow this guide.
nqnxev said:
Use older Android versions, for Android 13 you need probably fixed/updated vendor. Follow this guide.
Click to expand...
Click to collapse
What about the LineageOS GSI? will i be able to boot in it after flashing Android 9?
nqnxev said:
Use older Android versions, for Android 13 you need probably fixed/updated vendor. Follow this guide.
Click to expand...
Click to collapse
Hello, i have followed the guide and used the LineageOS new rom from the list of ROMs that was in the thread and everytime Android restarts the phone reboots, any solution?