[Q] Rooted Note 4 can't copy roms to phone - Sprint Galaxy Note 4 Q&A, Help & Troubleshooting

I rooted my note 4 and noticed it was really laggy so I planned to flash a new rom. Went into Twrp and did a full wipe and when I went to load my new rom onto the mounted phone (in Twrp) I got the error message in windows saying Cannot copy file "Its file size is larger than the device limit". I did some research and this seems to happen when a file is larger than 4 GB but the file I am trying to load isn't. I have 3 potential roms all around 1.2 GB and all give the same message when trying to put them on my SD card or the internal storage. Anyone know a fix for this. I tried going to the backup I made before trying the new roms and I get a boot loop so my 2 day old phone is partially bricked at the moment. I can still get into TWRP and I still can use Odin but I can't copy and past roms onto the phone. Any help would be appreciated thanks in advance.

This is still an issue but I found a workaround, a rather obvious one that in my panic I didn't think of. I just used my SD card reader and put the roms I wanted on my SD card then put it back in my phone and installed through twrp. This worked well but now the google play store isn't working for some reason even though I am using a mostly stock rom. I'll look at that roms thread for answers

tonygotskilz said:
This is still an issue but I found a workaround, a rather obvious one that in my panic I didn't think of. I just used my SD card reader and put the roms I wanted on my SD card then put it back in my phone and installed through twrp. This worked well but now the google play store isn't working for some reason even though I am using a mostly stock rom. I'll look at that roms thread for answers
Click to expand...
Click to collapse
Extract the file SDfix.apk from this zip,install and run it. It may solve the problem. This problem happens to me everytime I flash a stock rom and this cures it.

Same Problem Here
jhill110 said:
Extract the file SDfix.apk from this zip,install and run it. It may solve the problem. This problem happens to me everytime I flash a stock rom and this cures it.
Click to expand...
Click to collapse
How do I install SDFix.akp? All I have working is TWRP 2.8. Goal is to install HD Rev 82. Phone has no OS on it right now.

Download and install foldermount from the play store. Then run it and reboot. Should fix your issue.

teebright said:
How do I install SDFix.akp? All I have working is TWRP 2.8. Goal is to install HD Rev 82. Phone has no OS on it right now.
Click to expand...
Click to collapse
Extract it... Transfer to your phone... Tap it. You will get a "install" prompt... Install... Find it in the app drawer... Run it... Look carefully for the check box, it's hard to see... Viola... Your good to go... No need to go to the play store...

Thanks, but...
jhill110 said:
Extract it... Transfer to your phone... Tap it. You will get a "install" prompt... Install... Find it in the app drawer... Run it... Look carefully for the check box, it's hard to see... Viola... Your good to go... No need to go to the play store...
Click to expand...
Click to collapse
My phone is soft-bricked right now lol. I ended up copying the files via ADB with this helpful video:
https://www.youtube.com/watch?v=NaK5OxUeDKM
This line from cmd line w/ Minimal ADB and Fastboot did the trick:
adb push yourRomNameHere.zip /sdcard/.

Related

[Q] Root help:"Main version older"

Hey ive been trying to root my evo all day it is on version 2.1-update1. I was able to root my brothers perfectly fine using the downloads and tutorial from the idiot-proof guide to rooting by thebiles. But on mine I get stuck right at the beginning, when i try to flash the PC36IMG my bootloader says main version older. I feel like ive tried everything if anyone can help I'd reallly appreciate it thanks.
Try simple root, and keep trying. I got that same error even with simple root on my buddies 3 times before it worked. Don't know why. Maybe try copying the pc36img to the sd card instead of letting simple root push it...gl!
I agree with the simple root approach. Not trying to highjack your post but I have a question back at you if I may. You say you have one root EVO and one not root? If so the the root has PRI 1.34 and the nonroot 1.40? Could you perhaps do a data speed comparison on these and post the results? I am real curious...
sorry man i saw your post like 2 minutes too late the simpleroot worked right before i refreshed this page thanks for the help though guys appreciate it
one more quick question while PC36IMG was flashing the 2nd "tp" file said bypassed next to it rather than OK like all the others and the first tp had a blank next to it...is this a problem i should look into before unlocking the nand and all that other good stuff?
No problem glad you got it working. This was kinda like going to the casino...getting up to go to the bathroom...coming back to see someone hit the jackpot on your machine....hahaha!!!
That is normal....mine did that.
thanks man appreciate it...one more question for anyone that can help, im using the idiot proof guide and im on step 56 but when i try to enter the adb shell i get an error from command prompt saying "error: more than one device and emulator" i entered the shell perfectly fine like 2 steps before that and used it to flash the new pc36img rom but now i get this error to enter shell again how do i fix this error?
Okay I came here thinking this might finally be it... but nope I tried all the solutions mentioned here but to no avail. I am frustrated and still getting the main version is older. Does anyone know what is causing this error. Please I'm using usb debugging I wiped and backed my SD and have ota that came out in June. I installed Microsoft net frame and htc drivers. I updated simple root and the update log said this was to fix the error but still getting the same error. Any suggestions
I have the same issue, pretty much have tried everything with no luck, kind bummed at the moment, hope someone can help
Thanks
I got to work FINALLY!!!!!
So finally i got the main version error older NO MORE. So i decided to share what i did in hopes that it will work for all of you frustrated out there.
1) Download simple root from xda forum, dont download it anywhere else. The first time i tried i downloaded it at another android forum and even though it may seem the same, this version for some reason was not pushing the files as it suppose to. So again download from forum. Search for it on XDA.
2) Be patient and prepare yourself.
3) Make sure you on the 147 ota version. Not froyo. or before any version before ota because you can use old simple root.
4) After you download it extract it to a folder. Choose whatever location suits you i like desktop so i can delete file after i use it and keep zip. Be sure to update the program. Open it and let it search for downlaod or go to root folder and search for the updater.
5) Before running the program check the obvious. Is usb debugging enable, Do i have microsoft netframe, Are my phone drivers correct. Is the usb cable correctly connected to my computer and phone. Did i choose charge only when connected to the computer.
6) Now on your phone, and this step did it for me, go to Settings>SDandPhoneStorage>FactoryDataReset. Brace yourself this will wipe data it will not change your version. But if you want do a backup the folder of your contacts and whatever you have in your SD card, this is the time to do so. Mount as disk drive, and remember to change back to CHARGE ONLY. I skipped this because rooting was more important than my girlfriends phone number.
7) Now youre noobiness is ready connect phone double check Step 5. In case you missed something.
8) Run the simple root downloaded from XDA forum. Wait for it to push files is wont take long but me patient. Think of it passing 180mb to sd card so it takes some time.
9) Phone will reboot in a screen with skating androids Push power button and WAIT. It will find file and you shouldnt be getting "main version older" reboot error you where getting if you paid close attention to detail. Now update push volume up.
10) Why so impatient wait for it to update files. Once its down just push volume up for reboot. First time it reboots after root or when u flash a rom it usually takes longer, enough to get u nervous but dont be WAIT.
11) Easy sailing now but youre not done yet. Hit recovery once your phone reboot. Choose the method you want i chose Clockwork it works just fine for flashing roms.
12) Congrats your fully root and can flash that cool rom youve been reading about. Suggestions: DamageControl or Cyanogen but go ahead and try whichever you like.
13) YOURE DONE WOOF
If for some reason, it happened to me with AvaFroyo, when you flash your rom it goes on a loop and keeps rebooting dont panic that is what the recovery is for just put your microSD on a card reader delete the rom that is giving you problem and place another one and Reflash. Read how to flash rom you have to wipe on Recovery menu everytime you flash a different rom.
I hope this helps...Its in plain english not Dev English so...

Solved: Ubuntu Linux user needs assistance with CMW that won't see sd card..

Guys,
I recently purchased my phone from someone already rooted and with Rogue recovery 1.10 on it. Today I had to recover from a weird screen lock loop and nothing would get me out of it except loading a recovery rom:
http://forum.xda-developers.com/showthread.php?t=1272585&highlight=service+loop
After loading this rom, my recovery changed to clockwork and now won't recognize any of my sd cards. I can boot up the phone fine now at least though, but I would like to flash another Rom.
I have Root explorer installed so I can go that route. Heimdall will work on my pc but not the gui frontend.
So, I was wondering if anyone can help me or guide me to a link to show me how to flash a new recovery from linux, Root Explorer, or Heimdall?
Has anyone had an issue with clockworkmod not seeing their sd card? I can see it fine from any file explorer installed on the phone.
Thanks.
Man... you got that info from the bad old days when CWM didn't like your internal SD card. So, here's what you do:
EK02 just officially came out, and it's pretty stable so far. You want to use Heimdall to flash a kernel that has the latest CWM and EK02. I suggest the latest Rogue EK02. Download that, and unzip it somewhere. There's a file named zImage, which is your kernel. If you have heimdall installed:
Code:
heimdall flash --kernel zImage
That will not only install the latest EK02 kernel, but the latest CWM that works with your internal SD card. After that, I suggest flashing the EK02 modem.
From there, you should be fine doing whatever other MOD/ROM flashing you want from the internal SD card without without worrying about mismatches between the kernel and the modem. You can do the modem with heimdall too, but I figured it's easier just to use CWM, and the fastest path to CWM, is a kernel with it packed in.
Warning: They've remapped most of the softkeys in CWM. Select is the search button, back is the back button, moving to the next item is the menu button. I didn't check the home button.
Edit: I just noticed you didn't say 'internal' sdcard. Do this anyway. If the latest stuff can't see your SD cards, I'm not sure what else you can do.
Heimdall....
trifthen..
Thanks for your reply.. Yes, I have not been flashing for a long while but am getting bakc in the game. Good info you gave me.
There's more to my situation that I didn't mention. While trying to fix this issue I also found Heimdall. But I have been looking for a version that will work with Ubuntu Lucid (which is what I have installed) to no avail. Here is what I have found:
Heimdall:
v. 1.3: the Deb will not work at all w Lucid. Dependency problems.
v. 1.2: same thing as above.
v. 1.1: I found a PPA with the command line version which works, but the frontend to 1.1 does not work.
I contacted the dev and am waiting to hear back.
I imagine it will be a nightmare to do this via command line with Heimdall.
It seems when I find a tool to fix this, another obstacle stands in my way. Im not giving up though...
So, I might have to borrow a windows pc or re-install windows in this one....Or dual boot a version of Linux that works with heimdall. Which version of Ubuntu will work for sure with it?
What a pain.
killabee44 said:
Or dual boot a version of Linux that works with heimdall. Which version of Ubuntu will work for sure with it?
Click to expand...
Click to collapse
I'm running Maverick, which itself is pretty old. I installed the 1.3.1 version just fine. Lucid? That's a good question.
I think it's time you upgrade, bucko.
Though, if you want to avoid Unity, you can just go to Maverick, or think about Mint. I'm going to be upgrading soon... there's a few tools I want to use that are too new for Maverick.
Yeah, there's a whole lot of candy in Oneiric Ocelot but Im hearing its pretty stable. You just have to get used to the interface. We'll see. I don't really like Unity too much but maybe a workaround can be found.
I like some of the features they implemented in Oneiric though.
I ended up installing 11.10 Oneiric in a VM. Im downloading the files needed now. Ill post back results.
Ok, I am getting an error from Heimdall:
"failed to detect compatible device"
My phone is in download mode and connected with a good cable. I have switched cables to no avail.
Another obstacle.. damn!
Im still researching this.
killabee44 said:
Yeah, there's a whole lot of candy in Oneiric Ocelot but Im hearing its pretty stable. You just have to get used to the interface. We'll see. I don't really like Unity too much but maybe a workaround can be found.
I like some of the features they implemented in Oneiric though.
I ended up installing 11.10 Oneiric in a VM. Im downloading the files needed now. Ill post back results.
Click to expand...
Click to collapse
If you don't like unity, you can always install gnome 3
sent from my Epic 4g Touch
coldblooded79 said:
If you don't like unity, you can always install gnome 3
sent from my Epic 4g Touch
Click to expand...
Click to collapse
Yea, but I thought that they finally did away with that ability..
I tried booting windows but was not able to install samsung kies for the drivers. I get all kinds of registration errors. Very flakey software...
So, the phone could not be detected in Windows because kies installs the drivers.
If anyone knows how to install those drivers manually, please let me know.
I decided to try heimdall again but this time via the command line. Same thing, can't detect the phone. Error is:
"Failed to detect compatible device"
The rom I had originally installed to get out of the device lock loop was:
Kernel: 2.635.7
Build: Gingerbread EG30
Baseband; S:0710-10.s.EG31
Could that have something to do with it?
Thanks..
Edit:
The only way I have been able to flash anything since the loop was to use this procedure:
http://forum.xda-developers.com/showthread.php?t=1272585&highlight=signal+loop
(the CWM restore procedure)
Are there any roms that you guys can recommend for me that I can flash in this way? Thanks.
Well I got it flashed. All of a sudden the version of CMW that wasnt working saw my sd card on one of the reboots. Go figure.
I just hope that there isn't anything wrong with my phone hardware wise...
Thanks for the replies and help. My nightmare is over.. for now lol.
killabee44 said:
Well I got it flashed. All of a sudden the version of CMW that wasnt working saw my sd card on one of the reboots. Go figure.
Click to expand...
Click to collapse
Wow. Glad you got that sorted out.
I'm not entirely sure why you were having trouble with Heimdall, but it might have something to do with trying to use it from a VM. There may also be some setup steps you missed after installing it. I'm guessing there's a config file somewhere so it knows device configs or something. You probably want to get that working eventually in case of emergency.
In any case, you should be fine with CWM from now on.
killabee44 said:
Yea, but I thought that they finally did away with that ability..
Click to expand...
Click to collapse
No. I use gnome 3 as my desktop.
sent from my Epic 4g Touch

[Q] A Wary Traveller

Hello all I am in a bit of a situation.
This is the second time I have posted regarding me causing my galaxy note 2 to be out of order. Today I used TWRP to wipe my OS then also deleted all of my data wiping the os's I had downloaded. I only have a Mac thus the help for Mac's and Android is very limited thus I am wondering if there would be any way to get this fixed without using a Windows computer right now my phone is stuck rebooting.
Sorry to bother you all again,
Max
I don't know if I understand your post fully, but... It sounds like you wiped the device, and wiped the ROM that you downloaded? I've seen this increasingly lately.
Anyways..
Download another ROM and place it on an external SD card. You'll need an adapter to be able to hook the SD up to the computer. Or just borrow someone's SD. (just don't wipe it too)
Put the SD in and flash the ROM. just shut the phone off and when you're ready, use the three button combo to get back to TWRP.
Please hit the triangle on the side of your post and report it for thread maintenance to be moved. This thread (A question thread) belongs in the Q&A section.
Brad.S. said:
I don't know if I understand your post fully, but... It sounds like you wiped the device, and wiped the ROM that you downloaded? I've seen this increasingly lately.
Anyways..
Download another ROM and place it on an external SD card. You'll need an adapter to be able to hook the SD up to the computer. Or just borrow someone's SD. (just don't wipe it too)
Put the SD in and flash the ROM. just shut the phone off and when you're ready, use the three button combo to get back to TWRP.
Please hit the triangle on the side of your post and report it for thread maintenance to be moved. This thread (A question thread) belongs in the Q&A section.
Click to expand...
Click to collapse
Is there any way I could do it without an SDcard?
mmckenna11 said:
Is there any way I could do it without an SDcard?
Click to expand...
Click to collapse
With a Mac, not that I know of.
Give it a few hours and maybe someone with higher knowledge of mac+android will chime in.
The phone is blank right now, I would hesitate to even try to turn it on. You could use windows and Odin. You might be able to adb the files to the device..But that is more learning/hassle than the SD. Using the SD is really the easiest.
I'd let you borrow mine but shipping would take a while (haha)
I have an iMac and have the same problem. Android file transfer doesn't even recognize my device for MTP transfer. But I have four other windows machines here, so no biggie for me.
How would you go about doing it using windows?
mmckenna11 said:
How would you go about doing it using windows?
Click to expand...
Click to collapse
Install Odin and grab the stock OS files
Place the phone into download
And push the stock os to the phone
It would be as if you were going back to full stock.
There are numerous guides on how to do it.
Here are a bunch of resources:
http://forum.xda-developers.com/showthread.php?t=1987541
if you install a VM on your mac, or if you have one already installed, then just run it, install Odin on it, and install the stock ROM that way..
wase4711 said:
if you install a VM on your mac, or if you have one already installed, then just run it, install Odin on it, and install the stock ROM that way..
Click to expand...
Click to collapse
Exactly what I do! Parallels 7 does the trick for me if my windows box has a non specific color screen of death.
Sent from my SGH-I317 using xda app-developers app
For ATT they all seem to be in .zip file format yet you cant use that with odin so how would i go about doing this?
How do you place a file directly into a directory so i can use recovery to flash it on?!

Need help badly. No OS cannot boot passed twrp/cwm

Hello. Ive been 3 days with no phone now and am at my wits' end. I converted to developer, and in trying to clean install a ROM, messed something up...badly.
I can flash TWRP or CWM both through Odin, but no roms work at all. All of them get stuck at system.img.ext4 for about 10 minutes and then it fails. I cant flash anything through recovery, either, because neither recovery program can read my SD card for some reason. Ive read up on similar issues, but all of the fixes involve formatting the SD card through a functioning ROM, which isnt a possibility for me. I am desperate at this point...very desperate. Also, Ive tried the XDA IRC rooms but i'm not sure if i even join them correctly, as for days i cant get even a single letter response from any of the listed participants. Ive gotta be doing something wrong. Any help would be greatly appreciated. At this point i dont care if i lock my bootloader forever i just NEED a working phone.
Smartswitch doesnt work because it wont recognize my device, and when prompted for a S/N, nothing works...ive tried everything from the IMEI to the SIM s/n from the original package sleeve.
SOLVED:. talked to Samsung reps and confirmed that the note4 in fact has no serial number and that function if the recovery tool doesn't work for them. Did a day or researching on ADB stuff, which was new to me, and got cm13 successfully working via side load. After that, cm formatted the memory card to he readable, and all seems right in my note4 world for now.
8wrlobo said:
SOLVED:. talked to Samsung reps and confirmed that the note4 in fact has no serial number and that function if the recovery tool doesn't work for them. Did a day or researching on ADB stuff, which was new to me, and got cm13 successfully working via side load. After that, cm formatted the memory card to he readable, and all seems right in my note4 world for now.
Click to expand...
Click to collapse
So what exactly did you do been trying to get a rom to work on mine that I did the dev convert on. I was on the latest ota update. Got it rooted and flashed a different kernel got it to boot on stock firmware but can't get any other rom to install and boot.
Sent from my SM-N910V using XDA-Developers mobile app
slowpoke2006 said:
So what exactly did you do been trying to get a rom to work on mine that I did the dev convert on. I was on the latest ota update. Got it rooted and flashed a different kernel got it to boot on stock firmware but can't get any other rom to install and boot.
Sent from my SM-N910V using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah Odin and sd card options all fell flat on their faces for me...I never did figure out the system.img.ext4 hangup I got from odin.
In the end, I used Odin (3.9 iirc) to flash twrp. Flashing two or cwm both never gave me any trouble. From there, I downloaded the cm13 latest build from the thread here and followed this guide (http://forum.xda-developers.com/showthread.php?t=2317986). Sideload failed for me as well, but I was able to push the rom to my phone.
I downloaded a adb/fastboot program (https://androidmtk.com/download-minimal-adb-and-fastboot-tool) and in the x86 program files folder for it, made a new folder called FML lol and moved the ROM zip folder into it. Then did
abd push ___________.zip /sdcard/_________.zip. (note that I don't remember exact adb commands...it had been hours of frustration. Definitely consult the experts (not me) here before trying what I did. In the end it worked great. Good luck.
It was my first experience with adB stuff and tons of trialife and and error but I sure learned tons after all the research and frustration.
8wrlobo said:
Yeah Odin and sd card options all fell flat on their faces for me...I never did figure out the system.img.ext4 hangup I got from odin.
In the end, I used Odin (3.9 iirc) to flash twrp. Flashing two or cwm both never gave me any trouble. From there, I downloaded the cm13 latest build from the thread here and followed this guide (http://forum.xda-developers.com/showthread.php?t=2317986). Sideload failed for me as well, but I was able to push the rom to my phone.
I downloaded a adb/fastboot program (https://androidmtk.com/download-minimal-adb-and-fastboot-tool) and in the x86 program files folder for it, made a new folder called FML lol and moved the ROM zip folder into it. Then did
abd push ___________.zip /sdcard/_________.zip. (note that I don't remember exact adb commands...it had been hours of frustration. Definitely consult the experts (not me) here before trying what I did. In the end it worked great. Good luck.
It was my first experience with adB stuff and tons of trialife and and error but I sure learned tons after all the research and frustration.
Click to expand...
Click to collapse
OK so once you were able to get the rom pushed to your phone it installed fine? I just can't get them to install and boot right. What version were you on and did you do safe updates? Guess I'll have to start a new thread on it
Sent from my SM-N910V using XDA-Developers mobile app
I was/am at PA1. I did the smartswitch emergency recovery to stock PA1 and then redid the developer conversion, before having a hangup and wiping everything with twrp...like everything (BAD idea). That is what caused all my odin and sd card woes to begin with.

is there any way to root without twrp?

Yes, it's me again. Yes, I have written about this already. Yes, still the same problem.
So, as some of you may know, I have a huge problem with flashing TWRP. No matter how hard I try, no matter what my pc OS is, I get this problem every time, when I try to move from official MIUI to any other ROM.
At this time I'm using Ubuntu 18.04 LTS, but it gets to the same point as on Windows. I reboot to bootloader via ADB, my device is on fastboot devices list, and when I enter 'fastboot flash recovery twrp.img' or 'sudo fastboot flash recovery twrp.img' - nothing happenes. Terminal is like frozen, there is no information what's going on (no sending recovery). When I had Windows, I used to reset (to be clear - format) my PC, and then it worked for some time. Theoritically I could do the same with Ubuntu, but hey guys, I think we can all agree that it shouldn't work like that, should it? Right now, the only way for me is to root my phone first, then it would be easy. But guess what! Root requiers TWRP, TWRP requiers root. Annoying LOOP.
I'd be really thankfull if someone answered this thread, even wrong, trying is what counts, right?
Download TWRP app and try flashing using the app. Never tested it. Your best bet run window simulator on PC or go library or use someone's computer. Takes like 1 min to root. I have bricked my phone million times already, piece of cake to bring it back to life.
Asheque said:
Download TWRP app and try flashing using the app. Never tested it. Your best bet run window simulator on PC or go library or use someone's computer. Takes like 1 min to root. I have bricked my phone million times already, piece of cake to bring it back to life.
Click to expand...
Click to collapse
To flash TWRP via app I need root. And I see no way to root my phone. But the windows emulator sounds like a good idea Gonna try that. And I have tried on my brothers computer one day, didnt work
Hilus said:
To flash TWRP via app I need root. And I see no way to root my phone. But the windows emulator sounds like a good idea Gonna try that. And I have tried on my brothers computer one day, didnt work
Click to expand...
Click to collapse
Go on your brothers computer, download TeamViewer. Message me and I can do it for you.
Asheque said:
Go on your brothers computer, download TeamViewer. Message me and I can do it for you.
Click to expand...
Click to collapse
Right now I am making a bootable windows, to see if this works. If it fails I'll text you
Hilus said:
Right now I am making a bootable windows, to see if this works. If it fails I'll text you
Click to expand...
Click to collapse
Sounds good. Very easy once you have it setup. Keep in mind you have to reinstall TWRP and root every time you update MiUi OS. For me the global update is like every Friday so I have to reinstall TWRP and Root every week.
Asheque said:
Sounds good. Very easy once you have it setup. Keep in mind you have to reinstall TWRP and root every time you update MiUi OS. For me the global update is like every Friday so I have to reinstall TWRP and Root every week.
Click to expand...
Click to collapse
After some time, I gave up. Last hope was to try one more time on my brother's PC, and luckly - it worked. Everything ended good for me, but I still don't get it why sometimes my PC decides to go along and work with me and sometimes it just doesn't care. I am aware that flashing official MIUI wipes custom recovery, that's why I usually don't come back to it from any other custom ROM. Anyway, I'm really thankful for your help Asheque, thanks for all advices, and I think one day I will come back exactly to this thread and read them again. Appreciate it!
Hilus said:
After some time, I gave up. Last hope was to try one more time on my brother's PC, and luckly - it worked. Everything ended good for me, but I still don't get it why sometimes my PC decides to go along and work with me and sometimes it just doesn't care. I am aware that flashing official MIUI wipes custom recovery, that's why I usually don't come back to it from any other custom ROM. Anyway, I'm really thankful for your help Asheque, thanks for all advices, and I think one day I will come back exactly to this thread and read them again. Appreciate it!
Click to expand...
Click to collapse
I am glad it worked out Make sure you install Magisk apk and flash Magisk.zip for root access and pass safetynet if you want to use Google Pay. Also, highly recommend you download GBoard Theme module from Magisk. It's the best, makes Google Keyboard freaking awesom.
Asheque said:
I am glad it worked out Make sure you install Magisk apk and flash Magisk.zip for root access and pass safetynet if you want to use Google Pay. Also, highly recommend you download GBoard Theme module from Magisk. It's the best, makes Google Keyboard freaking awesom.
Click to expand...
Click to collapse
Thanks so much, I'm gonna try it out

Categories

Resources