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?
Related
Hi,
After a frustrating few hours, I've decided to give in and ask for help.... I've read just about every thread on this and other forums and just cannot get what I want.
The basics:
I have a new 4GB model, which appears to be chinese (chinese battery markings) and post the change to preloader - date on battery is 140418
Rather strangely, the ROM it came with was listed as 'P780_ROW_8G_S223_140901', even though the free storage, etc. showed that it was a 4GB model....
Following one of the excellent guides on here I managed to install TWRP and root it, even after the OTA update to S224 came through.
All fine, except that I found the UI a bit laggy coming from a Samsung S4 Active, so I thought I'd go to AOSP or similar.
This is where I have run into a brick wall. I've got SLXrom on there and it runs nicely, but I really wanted some KitKat goodness, and all the AOSP KK roms I can find (on Needrom, etc) require flashing over a Chinese base ROM.
I've spent several hours trying every combination of ROM and flashing method, and have completely failed to get a CN rom booting on my phone....
What I've tried already:
1. SP Flash Tools v3.1304.0.119 (Other version won't even try)
2. The linked 'stock' roms from another thread on here - P780_S135_130917_rooted_twrp_gapps and VIBEUI_V1.5_1419_5_DEV_P780_rooted_twrp_gapps
3. Changing the preloader.bin file for the later one for the newer phones
4. Flashing SLXROM_v26-Lenovo_P780-KIT(CN) from TWRP (says successful but never boots - blank screen only)
I know the drivers, etc. are installed correctly because I was able to flash TWRP via SPFT - but any of the above give me a 'BROM ERROR: S_FT_READBACK_FAIL(4009)' error.
I did have to use an altered scatter file to flash the recovery, but I tried the same modification with the ROMS and no success.
From what I understand, the main difference between CN and ROW roms is the partitioning, so I'm assuming that this is somehow at the bottom of the issue. What I can't find is the solution.
Couple of things I noted while trying:
1. Any flashing of a CN ROM would cause TWRP to not see the data partition - reflashing the Aroma partitioning app someone from here provided (thanks!) corrected that...
2. After flashing failed, Windows would give me a 'usb device failed' message on next plug in - pressing the reset button on the phone solved that.
3. None of the flashes destroyed TWRP, so I am guessing that they did not successfully flash even the recovery image. (not sure what order they are done in)
Can anyone give me any pointers to try now? Should I be able to flash a CN ROM from TWRP (English)?
Would getting a Chinese version of the recovery on there be a way forward? I did try that but again flashing failed.....
None of this would be an issue if there was a AOSP KK ROW build, but perhaps there will be one soon and I should just wait for that?
Any thoughts welcome - I've given up for the night because I was in danger of throwing the damn phone across the room!
Gavin
Solved
Okay, I finally managed it, with a lot of research, cursing and luck!
In case anyone else runs into the same issue, here are the steps I took - I'll try to upload the files I used to this post later.
FIRSTLY: MAKE SURE YOU HAVE A BACKUP, PARTICULARLY OF YOUR IMEI AND NVRAM - MTKDroidTools is the best way to go, there are other threads on it.
It may not be necessary, but if it is, don't complain when you cat explodes and you spiral into a world of gloom and doom - BACKUP FIRST!
The key was finding a CN ROM that could be flashed using SP_Flash_tools on to a phone that has a ROW ROM on it. For my device at least (post April 2014 bootloader Chinese 'speed' version), none of the ones linked on here would work....
However, I found one on 4pda.ru that does work - The page is in Russian, but Google Translate does a reasonable job.
The page is here, but the direct link to the file is here The ROM in question is 'VIBEUI_V2.0_1437_7.14.1_ST_by_sadist_v1.zip'
I also downloaded SP_Flash_Tool_v5.1352.01 from the same post, which worked for me, though other versions may work....
Pre Requisite Steps:
1. Make sure drivers are installed properly for the preload bootloader
2. Did I mention making a backup?
3. Extract the ROM zip to a suitable location
3. If your phone is one of the Chinese models after April 2014 (The date is on the battery on mine in the form: 140414), then replace the preloader.bin file in the ROM download with the 2014 version from here
4. Choose a suitable ROM for your device that can be flashed through recovery - There are several on NeedROM, personally I went with the AOSP-4.4.2-fix-PYRO_LS from here. Place this ROM on your SDcard so it will be accessible from the recovery.
5. Turn your phone off (do not plug it in yet)
6. Run SP_Flash_Tool_v5.1352.01 from the extracted file.
7. Click 'Scatter-loading' and browse to the ROM folder then load the MT6589_Android_scatter_emmc.txt file
8. Choose 'firmware upgrade' from the drop down list and make sure that all the files are ticked and the location field is filled in
9. Click 'Download'
10. Without turning your phone on, plug it into to your USB port.
11. The files should start downloading (First a red completion bar, then through various colours)
12. Wait until you get a green circle to show the download has worked. If you don't, then check the above steps again very carefully.
13. IMPORTANT - unplug the phone, then start it, while holding both up and down volume keys together. This will force it into TWRP. If you don't do this and let it boot into the ROM, then the original recovery will be reinstalled and you will have to start again.
14. You should get the 'Teamwin' logo, and then be in TWRP. It is the chinese version, but should be in English so no changes or translation needed.
15. Do a wipe (Not sure if this is essential but I did it) - The standard wipe is enough
16. Go to install and choose the zip you put on the SDcard earlier
17. The install should complete successfully. You may find it best to do another wipe (only minimum) here though I didn't.
18. Reboot and you should boot into Stock Android 4.4.2, with a few additions (Superuser is already installed - Lenovo Power Manager is added, etc.)
19. Choose your language and set up as you wish
20. Bask in the glory of a job well done.....
Troubleshooting:
If your phone does not flash correctly in step 11, don't worry. Make sure you have the correct files selected in Flash tools, and replace the 2014 preloader.bin if you forgot.
Press Download in SP Flash Tools again
Leave your phone plugged in, then take off the back and press the red reset button once. your phone will turn off, and then when it starts up it should immediately be detected and start flashing again.
If you never get the RED bar, then the drivers are not properly installed, so make sure that is done first. If you are on Windows 8, you will likely need to reboot into Advanced startup mode and disable Signature verification. There is a post on installing drivers that explains...
Hope that helps someone else avoid the hassle I went through. So far everything seems to be working fine and I have KitKat goodness without the Lenovo bloat. It definitely seems snappier and I can add the tweaks I want with Xposed.
If you like some of the Lenovo Apps, they do seem to mostly install and work fine on Stock Android, including the widgets. Props to lenovo for not needing their own launcher to work them!
Hey guys, I thought I'd spread the word on how to root this particular phone in 2018, if you're still stuck with it by any chance. TrapKernel has been breaking Wi-Fi when used on an updated Samsung firmware, and then there's the news of Chainfire quitting development on SuperSU. That being said, here is a fresh new root guide for this phone which would eliminate the need of TrapKernel and SuperSU (or even the development of a new custom kernel for this device altogether), using Magisk, which has become a pretty popular systemless root method.
Magisk comes with a ton of benefits, including a powerful systemless interface, as well as keeping device certification and SafetyNet intact, allowing you to use apps like Snapchat, Pokemon Go, Super Mario Run, and so forth.
Credit to @mcopeland1003` for the heads up on Magisk.
PREREQUISITES
A PC
Odin
Galaxy Core Prime not rooted by any other method, and has the stock kernel intact. (If you want to OTA update your phone be sure to do that before you root your Core Prime with this method!)
Unofficial TWRP SM-G360T1
Installing TWRP Recovery
Enable OEM Unlocking in developer options if you haven't already.
Then, put your device in download mode by pressing Power+Volume Down+Home Key.
Launch Odin on your PC, then connect your device to your PC.
Click on the AP Button and browse for your downloaded TWRP file.
Hit Start.
In my experience, my Core Prime for some reason did not let TWRP install on my phone; when I decided to boot into recovery it booted into Samsung's stock recovery. To get around this: before flashing TWRP, go into the options tab of Odin and uncheck Auto-Restart. Then flash TWRP and then remove the battery of your phone and unplug your device. This will not damage your device.
Now, boot your phone into recovery by pressing Power+Volume Up+Home to make sure TWRP's there. You can now boot back into android.
Installing Magisk
Sideload the Magisk Manager APK from this link onto your device.
Now we need to download the latest Magisk zip file to flash through TWRP. Open up Magisk Manager. Press the giant Install button, then Install, and finally Download Zip Only. The latest Magisk flashable zip will start downloading.
Once the file has finished downloading, boot into TWRP by powering off your phone then pressing the Power+Volume Up+Home keys simultaneously. Head into Install, and browse to /sdcard/MagiskManager. You should find a .zip file with a name like "Magisk-v16.0(1600).zip". Flash that, then reboot into system.
By the way, don't let TWRP install SuperSU. It'll pretty much defeat Magisk.
And there you have it, Magisk giving you root in a systemless fashion, without breaking Wi-Fi, device certification, and SafetyNet. Hope this guide helped you guys out.
Be still my heart
Glad you found it useful. I use it so my 7 year old can play his pokemon games and stuff like that, but use root for the extra storage.
twrp has official release for this phone i seen and used its app to add to recovery once rooted .. wish i didnt use first root method i seen as phone no wifi and cant get reconition from pc
It worked for a while then went belly up !
FazPhantom said:
Hey guys, I thought I'd spread the word on how to root this particular phone in 2018, if you're still stuck with it by any chance. TrapKernel has been breaking Wi-Fi when used on an updated Samsung firmware, and then there's the news of Chainfire quitting development on SuperSU. That being said, here is a fresh new root guide for this phone which would eliminate the need of TrapKernel and SuperSU (or even the development of a new custom kernel for this device altogether), using Magisk, which has become a pretty popular systemless root method.
.
Click to expand...
Click to collapse
Hello,
Using your method which worked for me initially on an SM-G360T1 then on bootup I got the dreaded Wrong Binary FRP enabled message. Since then I have flashed back to the stock ROM but the minute I install TWRP it won't boot past the Metro PCS screen. It just sits there and won't go any further. I have done this multiple times in hopes that it will somehow 'fix' itself...(yeah right) but that never happens.
One of the membes in the Androidcentral group sent me here to ask about the problem. I can't undestand if the frp was tripped by something, why did the phone work OK for 2 weeks and then quit? It would seem to me it would have done it right away but yet it worked fine with TWRP and magisk. I did NOT install any more apps or ROM's to the device that's what puzzles me.
Can you help me with some ideas? You guys are the decided experts and I am a newbie to all this but trying hard to learn as I go.
Many thanks in advance,
W T
Hi all,
So i am no developer and never will be but I do like to understand what i am doing, why i am doing it when I see instructions on the internet. I have just been flashing an unofficial custom LineageOS 15.1 ROM on my Samsung Galaxy A3 2017 and suffice it to say that took hours of working out what i need and I am still not entirely sure I was hoping someone could explain it in simple plain english?
I have seen videos on how to create a custom ROM based on ASOP and read a guide about including hardware drivers before you compile. I guess if the vendor (ex. Samsung) they make their drivers for the hardware open source and you can get them that is a big plus, but i guess those drivers is not everything, i can imagine bootloaders, recovery, root etc etc also plays a role?
So when i wanted to flash my Samsung Galaxy A3 (2017) i go on to XDA and look for my phone and scroll through the forum. Only to find out not that many roms for that model. probaly down to popularity
Anyway i was instantly overwhelmed regarding unlocking the OEM bootloader, installing TWRP recovery and then root the device with SuperSu, installing ODIN etc etc.
So i wonder could anyone explain all this in much simpler steps? I mean the process i read was basically this:
Enable developer options
enable OEM unlock
Install TWRP using ODIN but i also needed something named RMM-State_Bypass.zip ?? not sure what this is this needed to go on SDCARD
reboot phone into download mode and using ODIN to flash TWRP recovery
Boot into TWRP recovery and flash that RMM-State Bypass file
Then i had to root using SuperSU (is Magisk not preferred now?). but for this i was asked to download SuperSU and a "no-verify-opt-encrypt-6.0" file. which I am not sure what is. then put them on SDCARD and boot into TWRP recovery
Then i had to format data reboot into recovery and then flash RMM_State again from above, then flash that "no-verify-opt-encrypt-6.0" file followed by flashing the SuperSU zip file.
Now reboot device and I was root.
Now what the heck did i just do with those files and why is root needed when i shortly after had to copy LineageOS 15.1 to the SD card. boot into recovery and wipe "system, data, dalvik, cache" and then flash custom ROM followed by GAPPS.
When you wipe System, data, cache and dalvik. does that not undo the root we did above? I do not understand
I guess those no-opt-verify file and RMM State bypass probably has something to do with bypassing some Samsung stuff on the device. but really i would love for someone to take the time to write something up in plain simple english, or if this has already been done point to it so that i can read it.
Probably completely crazy but i would love to do a personal CUSTOM ROM for Samgung Galaxy A3 (2017) based on AOSP with GAPPS and thats it. obviously drivers from Samsung so the hardware works. I am fairly certain that following guides on the internet i could create my custom rom, provided that i have the samsung drivers. but i have no idea really what i am doing and why in order to install TWRP and root etc
Feel free to PM me if you feel like that instead
anddd use magisk.
Hello, all. This is my first time posting on XDA, so please bear with me.
I have succeeded in rooting my Samsung Galaxy Tab S6 (running Android 11) with Magisk using the System-As-Root method shown here. My primary reason for rooting my device was to get back the background clipboard access that was nerfed by Google in Android 10. I am utilizing the Magisk module Riru - ClipboardWhitelist as a workaround.
Unfortunately (and obviously), the Module only works when I boot to the Magisk in Recovery partition, through the key combos. Frankly, I have basically no use for the default boot partition since about 1/3 of the apps that I normally use rely on the clipboard access, and the other 2/3 rely on the previous group.
Is there any way to set the device to just automatically boot the the Magisk in Recovery Partition by default, so I don't have to hold down the key combo every time I start up my device? I am open to suggestions, and can follow written guides fairly well...
Otherwise, do I have to look at reflashing the firmware back to the Stock Android 9? If so, how to I get around the restriction in Samsung Download Mode that limits you to flashing the current firmware or newer?
Unless something has changed dramatically since I rooted my t860 (I think you transposed the digits) Magisk is not a recovery. For a recovery you need TWRP. Best help available is here: https://t.me/tabs6twrp
quasiperfect said:
Unless something has changed dramatically since I rooted my t860 (I think you transposed the digits) Magisk is not a recovery. For a recovery you need TWRP. Best help available is here: https://t.me/tabs6twrp
Click to expand...
Click to collapse
I used the method shown here. Magisk in Recovery refers to this.
Hey guys found our first custom ROM, it's not official but I've been using it for about a week now and the performance is excellent.
There is not many bugs that I've noticed and build is very stable. One big I've noticed is that when kernel is on performance, the screen does not go off automatically.
I've used Kernel Tasker to avoid this issue by turning on performance for certain apps and games, while keeping the system at Interactive for most tasks.
At the bottom is the link for instructions, the OS and gapps. There is a thread in this forum for passing safety net which I recommend. It solved all issues for me since magisk is failing safety net while other safety apps are passing. All the best rooting enjoy the ROM.
Redmi 9C (angelica) First Custom ROM! (Lineage OS 17 Android 10 )
This blog has move and will not be update again.For new update please open ▶▶
langithitam.wordpress.com
I have tried before you but can't flash it in recovery
After that my phone didn't boot more into system
So I flashed my phone and make workable you should remove this thread
MHaseebpk said:
I have tried before you but can't flash it in recovery
After that my phone didn't boot more into system
So I flashed my phone and make workable you should remove this thread
Click to expand...
Click to collapse
I am still using this ROM daily with no problems, before you flash make sure you remove Mi Account. If you do not remove account, phone will bootloop with any ROM you flash.
Pitch black recovery keeps restarting every time when I tried to flash this custom
I don't know what is wrong
Tried so much but in vein
Finally I flashed my phone and makes it workable
MHaseebpk said:
Pitch black recovery keeps restarting every time when I tried to flash this custom
I don't know what is wrong
Tried so much but in vein
Finally I flashed my phone and makes it workable
Click to expand...
Click to collapse
Defintely something wrong. I *did*remove my Mi Account, but to no avail, the phone keeps returning to Pich Black Recovery. I would say: not at all recommended to use this ROM. I am quite experienced in rooting phones, but this one fails in any respect. Do not use this ROM!
JoostA said:
Defintely something wrong. I *did*remove my Mi Account, but to no avail, the phone keeps returning to Pich Black Recovery. I would say: not at all recommended to use this ROM. I am quite experienced in rooting phones, but this one fails in any respect. Do not use this ROM!
Click to expand...
Click to collapse
I don't know what u guys are doing wrong but I'm still using this ROM till today, haven't found anything else but haven't really looked either.
Follow the instructions on the website to the T, wipe when it tells u to wipe and flash everything in order.
The model 9C I'm using is the global variant and it's not NFC. So perhaps you guys are using different variant but I doubt that could be the problem.
I believe somewhere u guys skipped or improvised a step because from my experience with rooting, 1 little detail skipped or over looked or something that might seem harmless can brick a phone.
I have been rooting since 2015 and my 1st phone was hauwei mate 7. Nearly hard bricked the phone and I had to pay to unlock bootloader using DC Unlocker. I rooted using a 3rd party rooting app, can't remember the name but it almost cost me the phone.
But this ROM works for me but it's a gsi ROM, it's not actually a custom ROM. There are other gsi ROMs out there that u could try. Download treble info for more info on which gsi is compatible.
Dawood99 said:
I don't know what u guys are doing wrong but I'm still using this ROM till today, haven't found anything else but haven't really looked either.
Follow the instructions on the website to the T, wipe when it tells u to wipe and flash everything in order.
The model 9C I'm using is the global variant and it's not NFC. So perhaps you guys are using different variant but I doubt that could be the problem.
I believe somewhere u guys skipped or improvised a step because from my experience with rooting, 1 little detail skipped or over looked or something that might seem harmless can brick a phone.
I have been rooting since 2015 and my 1st phone was hauwei mate 7. Nearly hard bricked the phone and I had to pay to unlock bootloader using DC Unlocker. I rooted using a 3rd party rooting app, can't remember the name but it almost cost me the phone.
But this ROM works for me but it's a gsi ROM, it's not actually a custom ROM. There are other gsi ROMs out there that u could try. Download treble info for more info on which gsi is compatible.
Click to expand...
Click to collapse
I remember now, King Root that was the culprit app I used with that hauwei mate 7. 1st and last time I ever rooted with 3rd party app. I was so proud of myself when I saved that phone lol still am.
Booting into Lineage ROM. Perhaps others will have difficulty but if u follow instructions carefully and phone has been rooted properly, it will work.
I recommend the guide for rooting by 0purple. How to root and pass safetynet.
Also very important remove Mi account and reboot phone to insure that phone won't lock similar to Google account lock. So remove all accounts and back up data. As the instructions indicate you will be wiping phone as OS requires a clean install.
i flash this customer rom to remove mi account after done camera not work! and after format user data now stuck at recovery i reflash it with stock rom and custom rom but always stuck at logo ! any solution pleas?
Got the same thing - kept on going to Pitch Black. Tried this - worked better https://androidfilehost.com/?fid=2188818919693787699
JaxxFrost said:
Got the same thing - kept on going to Pitch Black. Tried this - worked better https://androidfilehost.com/?fid=2188818919693787699
Click to expand...
Click to collapse
Is there no bugs in this rom
How did you flashed while pbrp keeps restarting?
MHaseebpk said:
Is there no bugs in this rom
How did you flashed while pbrp keeps restarting?
Click to expand...
Click to collapse
I think the ROM originally posted might have a problem. Try follow my link and use 'snooks4tech's' rom. There is also a different recovery and vbmeta in this download that I flashed in fastboot. The rest of the process I more or less followed as per dawood99's video, eg the step to wipe those 3 things in Pitchblack, copy this rom over, and install it along with Gapps and Magisk with Pitchblack. I don't see Magisk in my phone now though. I'm not very experienced with custom roms BTW so not too sure if I had the right Magisk file. Snooks4tech's download has got instructions as well and does not mention Magisk. Thanks to Dawood99 for the video, even if I had problems with the rom it gave me a good overview of the steps and I learned a lot.
PS maybe I didn't answer your question. I had to download the Mi flasher, somehow I got it back into Fastboot, I think by holding power and down volume, then flashed it back to stock Xiaomi. Then I started the custom rom flashing process again. I think I flashed Pitchblack again, and Snooks4tech's vbmeta and recovery. It then booted into Pitchblack properly again, and I could do the rest.
So far this rom is working reasonably well for me, Google play store doesn't work but I side-install APK's by downloading from browser. F-droid app is also intermittently not giving me any apps when I search.
Again I'm not expert at all this so take what I say with a pinch of salt, I could be talking rubbish here and there.
Both ROMs and Install Instructions cause in a boot into PBRP recovery (tried with v3.0+3.1) and MIUI also doesn't boot :-(
My steps:
- In PBRP recovery
-> adb reboot bootloader
In Bootloader
-> fastboot flash vbmeta vbmeta9c.img
Then I reboot phone with 3 different trys
-> 1. fastboot reboot
-> 2. Power On + Vol Up
-> 4. Power On + Vol Down
--> With all trys phone reboots into PBRP recovery
Push ZIP Files via MTP isn't possible, so:
-> adb push [LineageROM].zip /
-> adb push [GApps].zip /
Then in PBRP I go to "Install"
-> [LineageROM].zip with "Patch AVB2.0 Verity"
-> [GApps].zip also with "Patch AVB2.0 Verity"
Then I reboot to system from PBRP
But then PitchBlack reboots into recovery
Upgrade and downgrade of PBRP from 3.0 to 3.1 and back to 3.0 works without any problems.
Please help me, many thanks in advance!
/edit: Flashed original MIUI and reinstalled PBRP, then tried to install Lineage again, but boots only in recovery after flashing booth ROMs.
JaxxFrost said:
I think the ROM originally posted might have a problem. Try follow my link and use 'snooks4tech's' rom. There is also a different recovery and vbmeta in this download that I flashed in fastboot. The rest of the process I more or less followed as per dawood99's video, eg the step to wipe those 3 things in Pitchblack, copy this rom over, and install it along with Gapps and Magisk with Pitchblack. I don't see Magisk in my phone now though. I'm not very experienced with custom roms BTW so not too sure if I had the right Magisk file. Snooks4tech's download has got instructions as well and does not mention Magisk. Thanks to Dawood99 for the video, even if I had problems with the rom it gave me a good overview of the steps and I learned a lot.
PS maybe I didn't answer your question. I had to download the Mi flasher, somehow I got it back into Fastboot, I think by holding power and down volume, then flashed it back to stock Xiaomi. Then I started the custom rom flashing process again. I think I flashed Pitchblack again, and Snooks4tech's vbmeta and recovery. It then booted into Pitchblack properly again, and I could do the rest.
So far this rom is working reasonably well for me, Google play store doesn't work but I side-install APK's by downloading from browser. F-droid app is also intermittently not giving me any apps when I search.
Again I'm not expert at all this so take what I say with a pinch of salt, I could be talking rubbish here and there.
Click to expand...
Click to collapse
Thanks dude but I'm not responsible for making that video or am I responsible for the website or the files posted on it. I merely stumbled upon the ROM and I should not be credited for it. The creator is credited on the Website I believe and all credit should go to him.
Diotrihhi said:
Both ROMs and Install Instructions cause in a boot into PBRP recovery (tried with v3.0+3.1) and MIUI also doesn't boot :-(
My steps:
- In PBRP recovery
-> adb reboot bootloader
In Bootloader
-> fastboot flash vbmeta vbmeta9c.img
Then I reboot phone with 3 different trys
-> 1. fastboot reboot
-> 2. Power On + Vol Up
-> 4. Power On + Vol Down
--> With all trys phone reboots into PBRP recovery
Push ZIP Files via MTP isn't possible, so:
-> adb push [LineageROM].zip /
-> adb push [GApps].zip /
Then in PBRP I go to "Install"
-> [LineageROM].zip with "Patch AVB2.0 Verity"
-> [GApps].zip also with "Patch AVB2.0 Verity"
Then I reboot to system from PBRP
But then PitchBlack reboots into recovery
Upgrade and downgrade of PBRP from 3.0 to 3.1 and back to 3.0 works without any problems.
Please help me, many thanks in advance!
/edit: Flashed original MIUI and reinstalled PBRP, then tried to install Lineage again, but boots only in recovery after flashing booth ROMs.
Click to expand...
Click to collapse
Same problem
JaxxFrost said:
Got the same thing - kept on going to Pitch Black. Tried this - worked better https://androidfilehost.com/?fid=2188818919693787699
Click to expand...
Click to collapse
Tried this too but same problem
What about fm radio? does this rom include it? ty
haw fix the camera wont work ???
Dawood99 said:
Hey guys found our first custom ROM, it's not official but I've been using it for about a week now and the performance is excellent.
There is not many bugs that I've noticed and build is very stable. One big I've noticed is that when kernel is on performance, the screen does not go off automatically.
I've used Kernel Tasker to avoid this issue by turning on performance for certain apps and games, while keeping the system at Interactive for most tasks.
At the bottom is the link for instructions, the OS and gapps. There is a thread in this forum for passing safety net which I recommend. It solved all issues for me since magisk is failing safety net while other safety apps are passing. All the best rooting enjoy the ROM.
Redmi 9C (angelica) First Custom ROM! (Lineage OS 17 Android 10 )
This blog has move and will not be update again.For new update please open ▶▶
langithitam.wordpress.com
Click to expand...
Click to collapse
the speaker in calls is heard very quietly and the battery runs out very quickly
hi can anyonehelp me my side load is corrupted mtp does not work and my fastboot also does not work after trying to install this i dont know how to fix this and the rom does not work it auto boot to pitch black recovery