All about root/magisk/etc - OnePlus 7T Pro (Regular & McLaren) Q & A

Please read the whole post and answer all (if possible) of my questions, I don't mind if you give me links, I'll read myself. Just don't answer with 2 words that don't mean anything to me.
I want to get into rooting, custom kernals, etc but I really don't know where to start reading from. Anything I came across seems not detailed enough. My end goals are:
- To get enough info so I don't brick my phone or even if I do, I want to know how to fix it.
- Install a custoim kernel, so I can get battery life simillar to this guy.
- Get magisk working, so I can get AUX lenses on gcam working too.
In the past I have installed custom roms on my old LG G2 and everything was so simple, rooting was 1 click and installed TWRP too. Then just flashing roms, gapps, etc, but at the moment I feel my knowledge/experience is like I've never seen a computer or phone in my life.
1. First, where do I start from? Here? It doesn't say if I should have an unlocked bootloader, but other guides require that. I'm kinda confused.
2. If I need to unlock it, I read that it wipes everything, how do I backup without TWRP? Speaking of which, do I need it since there is no official one. Can I do a pre-root backup with OP switch and then restore from it after I've rooted and/or unlocked bootloader?
3. What's the deal with patched boot images, in what situation would I need one?
4. I've just updated to OOS 10.0.8.HD01BA. Does that make me unable to root with method from 1 because its so new or it doesn't matter? I've read somewhere that with OTA you lose magisk/twrp, is there a way to prevent that or I'll just have to do 1 again. Do OTAs return me back to stock kernel?
5. The guy above is using this kernel. It's supposed to be working on 7T Pro too. Has anytone tried it? If so how is it?
6. What about blu_spark kernel, is it good? Also I don't really get what the warning message mean :
"Reflash ROM -> flash TWRP --> reboot to recovery --> flash Magisk if you want (default, no plugins/modules) -> flash blu_spark."
How do I reflash stock rom? Also there is no official TWRP, so I guess it's better to not use this one or there is another way to install?
7. Speaking of which, what's the deal with FKM? What should I know about it?
8. If I root with 1, can I then install arter97's kernel with FKM?
9. How do I go back to stock kernel/rom/etc/lock bootloader in case I need warranty?
10. Is there anything that's recommended to read/know?

UndeadG2 said:
Please read the whole post and answer all (if possible) of my questions, I don't mind if you give me links, I'll read myself. Just don't answer with 2 words that don't mean anything to me.
I want to get into rooting, custom kernals, etc but I really don't know where to start reading from. Anything I came across seems not detailed enough. My end goals are:
- To get enough info so I don't brick my phone or even if I do, I want to know how to fix it.
- Install a custoim kernel, so I can get battery life simillar to this guy.
- Get magisk working, so I can get AUX lenses on gcam working too.
In the past I have installed custom roms on my old LG G2 and everything was so simple, rooting was 1 click and installed TWRP too. Then just flashing roms, gapps, etc, but at the moment I feel my knowledge/experience is like I've never seen a computer or phone in my life.
1. First, where do I start from? Here? It doesn't say if I should have an unlocked bootloader, but other guides require that. I'm kinda confused.
2. If I need to unlock it, I read that it wipes everything, how do I backup without TWRP? Speaking of which, do I need it since there is no official one. Can I do a pre-root backup with OP switch and then restore from it after I've rooted and/or unlocked bootloader?
3. What's the deal with patched boot images, in what situation would I need one?
4. I've just updated to OOS 10.0.8.HD01BA. Does that make me unable to root with method from 1 because its so new or it doesn't matter? I've read somewhere that with OTA you lose magisk/twrp, is there a way to prevent that or I'll just have to do 1 again. Do OTAs return me back to stock kernel?
5. The guy above is using this kernel. It's supposed to be working on 7T Pro too. Has anytone tried it? If so how is it?
6. What about blu_spark kernel, is it good? Also I don't really get what the warning message mean :
"Reflash ROM -> flash TWRP --> reboot to recovery --> flash Magisk if you want (default, no plugins/modules) -> flash blu_spark."
How do I reflash stock rom? Also there is no official TWRP, so I guess it's better to not use this one or there is another way to install?
7. Speaking of which, what's the deal with FKM? What should I know about it?
8. If I root with 1, can I then install arter97's kernel with FKM?
9. How do I go back to stock kernel/rom/etc/lock bootloader in case I need warranty?
10. Is there anything that's recommended to read/know?
Click to expand...
Click to collapse
1. Unlocked Bootloader is always required.
2. Yes it wipes everything, OnePlus switch works fine for backup and restore
3. Since there is no TWRP you'll need one to root.
4. Not necessarily. You can just grab whatever patched boot image (preferably for BA), fastboot boot it to see if it works, if it does then do direct install in Magisk Manager. You can maintain root after an update following this
https://topjohnwu.github.io/Magisk/ota.html , and yes, it'll bring you back to stock kernel.
5. ?
6 &7. You can do ahead and try different kernels however I recommend arter97.
Since there is no TWRP you'll need FKM to flash the kernel.
8. Yes.
9. Rooting doesn't really void warranty, but I'd use MSMTOOL to get back to 100% stock.
For stock kernel you can flash stock (or patched) boot image depending wether you want stock or stock root.
To get back to stock ROM, either use MSMTOOL or fastboot ROM, you can find both in guides section.
10. Guides section for fastboot ROM and msmtool.
For AUX module.
https://www.celsoazevedo.com/files/android/p/gcam-oneplus-7-t-pro/
Since there is no TWRP it can be tricky to get out of bootloop if you install a rogue module.
Use this then;
https://forum.xda-developers.com/7t-pro/how-to/guide-remove-magisk-modules-twrp-t3995677

Related

[GUIDE][HOW-TO] Flashing a Custom ROM

Before I begin, Mods, PLEASE pin this. I (when I was a noob) had absolute difficulty installing ROMs. This is very noob-friendly, fixes Status 7 errors, and is easy to follow.
Alright friends and future flashers. I used to have difficulty installing ROMs. Now that I know how (after going through numerous tutorials), I'd like to make it easy for ALL of you. Enjoy your Custom ROM!
Before beginning, you need Android's SDK,Flashtool and The latest Official firmware.
If ever your phone needs to install drivers, let it install, don't unplug the phone or whatever.
And, battery at least 30%. Mine does it at even 20% without issues, but just to be safe.
Step 1: Revert to Stock
You don't need to downgrade. After flashing the latest stock kernel, I have flashed every single GB and ICS ROM in existence without issues, so you don't need to flash a specific one. But, latest one tends to be more stable. Here's what you do:
Get the latest Global ftf for your phone. Then, flash it using Flashtool. I won't go into specifics, but PM me if needed
By Now, you should have a stock EVERYTHING. Boot up the phone, run through the whole set up process. Once you are done, you need to get your IMEI number. Do this by following the steps here.
In the end, you should have the bootloader unlocked. If you come up with something like bootloader already unlocked, then you are good to go. Now onto......
Step 2: Preparing your Flash.
Download the ROM of your choice. I'd recommend FXP's Unofficial CyanogenMod9 as it has the best stability and no ICS Multitouch issues. If it is GB, any ROM will do. Most of them are stable.
Now, in the case of CyanogenMod, they often come with their own custom Kernel. It is in the zip file, known as boot.img, and you simply extract it to your platform-tools folder in the android-sdk folder you downloaded to unlock the bootloader. This is also true for some MIUI ROMs I've come across. Read their forum posts for more info on which kernel to use.
Copy the ZIP file to your sdcard. It does not have to be the root of SDcard, anywhere will do.
By the end, your Custom ROM's ZIP file will be in your SDCard, and the kernel file (a.k.a. boot.img or whatever_the _kernel_name_is.img) will be here:
32bit Windows: C:/Program Files/Android/android-sdk/platform-tools
64bit Windows: C:/Program Files(x86)/Android/android-sdk/platform-tools
Now we can
Step 3: Flash your Custom ROM
In the folder above (depending on OS version) press Shift+RightClick. Options will show up. Select "Open Command Prompt Here". A Command Prompt will open (duh).
Turn off your phone. Wait 10 seconds. While plugging in your phone, press the Menu button (the Right button). The LED Indicator should turn blue. This shows your in fastboot mode. If it starts to boot, rip out the battery and try again. DON'T STOP PRESSING UNTIL IT TURNS BLUE.
Now, type EXACTLY AS FOLLOWS, ONE AT A TIME. Just type in the lines with the "-" before it, but don't put in the "-" when typing it. The line underneath in brackets is an explanation, so you understand what is happening.
-fastboot devices
(This is actually a quick test I do to see if my phone is connected in flash mode or not. If nothing happens, it is not in flash mode or the drivers are installing)
-fastboot flash boot boot.img
(This is telling fastboot to FLASH the BOOT partition of your phone with the file specified. If you are using a different kernel, simply replace boot.img with the name of the kernel, ending with .img and wait for it to finish. Won't take long)
-fastboot reboot
(This causes the phone to reboot)
Now, while it is starting up, keep repeatedly pressing the Volume Down button until you are in ClockWorkMod Recovery (Assuming you are using it. CWM is the most popular and most kernels use it) Then, If you choose to, make a backup. I personally don't, as it is not too big an issue and I never revert to an old ROM anyway.
After that, choose Factory Reset. This will remove ALL data in your phone except your Stock ROM. Then, Clear Cache. You might've noticed it already did that when you Factory Reset, but this is for safety. Finally, in advanced, Wipe Dalvik-Cache and Wipe Battery Stats. I do this all the time for safety.
Now, the fun bit. GO to Install ZIP from SDCard. Select Choose ZIP, find your ROMs ZIP file, and install. It might take awhile, but not too long. Just be patient. When it finishes, flash anything else the ROMs forum post says to flash (Gapps, Patch, etc) and select Reboot Phone.
Step 4: Done!
Your phone will start up. First time is always slow, but this WILL WORK. Congratulations. You now have a Custom ROM
If you get a Status 7 error while flashing a ROM, reboot recovery and wipe everything again. If that doesn't work, flash official firmware and try again.
Credits to:
-Google: Providing Android SDK and Gapps
-Androxyde: Flashtool
-Madfysh: List of Official ICS ROMs
FXP: Creating CyanagonMod9
-And YOU!
P.S.: If you're confused, or feel this could use something extra PM me.
And uh, if it needs to be moved, please do so. Thanks!
I do know there is THIS but I felt some of his steps were unnecessary. Example, rooting. Any custom ROM will be rooted, so there will be no need to worry about that. And he also provided overclocking tips and an unofficial bootloader unlock which are hazardous and potentially permadamaging to the phone.
PLEASE Don't spoil the mood man!!
This is a development section where even Noob Devs know how to flash a Custom Rom!! PLeaseee Pleaseeee ... Move it
Alright man. How would I move it? Cause, I only RECENTLY started being active on the forums.
Jass5991 said:
I do know there is THIS but I felt some of his steps were unnecessary. Example, rooting. Any custom ROM will be rooted, so there will be no need to worry about that. And he also provided overclocking tips and an unofficial bootloader unlock which are hazardous and potentially permadamaging to the phone.
Click to expand...
Click to collapse
Don't say that thread is unnecessary; they put everything in one thread cause it's easy to find. the first step we should do is rooting if we are noops. Then we will be curious about unlock or custom rom later.
Sent from Xperia Neo using AOKP B40
Still dev thread so if you don't know how you should not be trying
It goes like this no dl link no thread
but still is a good post
some unnecessary parts
some dodgy parts
But good for noob never-ending Questions
Maybe Q&A
Reck1993 said:
Don't say that thread is unnecessary; they put everything in one thread cause it's easy to find. the first step we should do is rooting if we are noops. Then we will be curious about unlock or custom rom later.
Sent from Xperia Neo using AOKP B40
Click to expand...
Click to collapse
Okay. I will add an easy rooting instructions to it.
kormatoes said:
Still dev thread so if you don't know how you should not be trying
It goes like this no dl link no thread
but still is a good post
some unnecessary parts
some dodgy parts
But good for noob never-ending Questions
Maybe Q&A
Click to expand...
Click to collapse
Thanks kormatoes. Could you gimme some of the unnecessary/dodgy parts?
Jass5991 said:
I do know there is THIS but I felt some of his steps were unnecessary. Example, rooting. Any custom ROM will be rooted, so there will be no need to worry about that. And he also provided overclocking tips and an unofficial bootloader unlock which are hazardous and potentially permadamaging to the phone.
Click to expand...
Click to collapse
1) actually that(which you linked) tutorial is good, it just need some updating. but your tutorial is different than that.
2) root is certainly not unnecessary! not all people will go for custom roms, specially as most of them are for unlocked BL.
3) unofficial unlock is not hazardous, it is tricky, but it paid of if we look on the advantage against official unlock
Nice from you that you wrote all this, it's based only for custom roms's, thread which is already sticked is for basic things, which any noob should know.
But still, this looks kinda cluttered, and from noob(which you intend this to) point of view, to long/complicate to read
Madfysh said:
1) actually that(which you linked) tutorial is good, it just need some updating. but your tutorial is different than that.
2) root is certainly not unnecessary! not all people will go for custom roms, specially as most of them are for unlocked BL.
3) unofficial unlock is not hazardous, it is tricky, but it paid of if we look on the advantage against official unlock
Nice from you that you wrote all this, it's based only for custom roms's, thread which is already sticked is for basic things, which any noob should know.
But still, this looks kinda cluttered, and from noob(which you intend this to) point of view, to long/complicate to read
Click to expand...
Click to collapse
Thank you all big guns
but there should be a start-up kit for newbie
There can be a Starter Section with due permission
lalit387 said:
Thank you all big guns
but there should be a start-up kit for newbie
There can be a Starter Section with due permission
Click to expand...
Click to collapse
As it is, I am attempting to code a batch file to automatically run the entire flashing process, including kernel and ROM. Having a small issue where it does not wipe dalvik and cache. It also doesn't flash the custom ROM

[Q] Installing CM-10.2 Android-4.3

Hey guys, I've rooted, installed CWM Recovery, Unlocked Bootloader, and installed CyanogenMod on another phone before.
The thing is, I've had this phone for about 6 months and wanted to do the same. However, after browsing through the forums, man are there a lot of scary sh*t going down. I would like the request the procedure to install CyanogenMod safely, without losing any Keys/IMEI/XReality/DRMkeys/Etcetera.
I dont know if the method given by FXP is supposed to be this straight forward, but I too like others, do not want to risk losing important stuff if it can be avoided (Keys/IMEI/XReality/DRMkeys/Etcetera).
HOWTO
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
Click to expand...
Click to collapse
Frankly speaking, the forums is pretty much jumbled up, and the existing [Guide] Threads are either incomplete (Lacking important steps), or Unclear (Non-Specific steps).
Perhaps someone could do me a favour by using the template that I have below to help me, and possibly others, to install CM 10.2 on our beast of a phone.
Template:
1. Backup TA and DRMkeys and stuff: http://forum-xda-developers-com/backup
2. Root: http://forum-xda-developers-com/root
3. Recovery : http://forum-xda-developers-com/recovery
4: Unlock Bootloader: http://forum-xda-developers-com/ulbl
5: Install FXP's CM 10.2 :http://forum.xda-developers.com/showthread.php?t=2461286
Something like that would suffice I think, as long as no important steps are missing that would cause me to lose stuff unique to my phone, that cannot be recovered if I didn't back it up.
P.S. My version is 14.1.B.2.257
P.P.S. Thank you in advance.
1. Root
2. Backup TA (VERY IMPORTANT)
3. Install Recovery and unlock the bootloader, or the other way around. Both ways work.
4. Install ROM by following the "guide" that you quoted above.
Sent from my C6833 using Tapatalk
I'm on 14.1.B.2.257, I believe reverting to the previous version causes data to be lost unless you back it up right. *Sighs* How troublesome.
Xenogenics said:
I'm on 14.1.B.2.257, I believe reverting to the previous version causes data to be lost unless you back it up right. *Sighs* How troublesome.
Click to expand...
Click to collapse
you will have to back up the data anyways. I think unlocking the bootloader does a factory reset, as well one is needed going from stock to CM if i unforget correctly
I am also wondering about this. I'm currently running firmware .257.
I understand that I need to back up the TA partition first (though I'm not exactly sure on what I will loose if I don't). I also understand that to do this I need to root the stock rom. I understand that in order to root, I'll need to first downgrade to an earlier firmware using flashtool. However, after that I'm not so sure what I need to do. As far as I can see, the only method of gaining root currently is to use vRoot, which is currently under investigation for IMEI mining.
How else can I root the device? I was thinking of maybe using the recovery for locked bootloaders here: http://forum.xda-developers.com/showthread.php?t=2426739
Following by flashing SuperSU from recovery as per usual.
Will this work, keeping the TA partition intact so that I can back it up before flashing CM? Assuming so, would I even need to downgrade from the .257 firmware at all?
Thanks,
i have CWM now so can flash custom roms like i did on other phones right?
what does unlocking the bootloader give me? unless i'm wrong and i have to unlock to flash?
all i've done so far is do a backup is all. (did a TA backup a while back though)
stiggy2012 said:
I am also wondering about this. I'm currently running firmware .257.
I understand that I need to back up the TA partition first (though I'm not exactly sure on what I will loose if I don't). I also understand that to do this I need to root the stock rom. I understand that in order to root, I'll need to first downgrade to an earlier firmware using flashtool. However, after that I'm not so sure what I need to do. As far as I can see, the only method of gaining root currently is to use vRoot, which is currently under investigation for IMEI mining.
How else can I root the device? I was thinking of maybe using the recovery for locked bootloaders here: http://forum.xda-developers.com/showthread.php?t=2426739
Following by flashing SuperSU from recovery as per usual.
Will this work, keeping the TA partition intact so that I can back it up before flashing CM? Assuming so, would I even need to downgrade from the .257 firmware at all?
Thanks,
Click to expand...
Click to collapse
OK, so looking into this further, you already need to have root to be able to flash the "CWM for locked bootloader" rocovery. So as far as I can see, the only way to get root in order to back up the TA partition is to give your IMEI to the Chinese via vRoot?
Thank god the stock rom is so good.
tommo123 said:
i have CWM now so can flash custom roms like i did on other phones right?
what does unlocking the bootloader give me? unless i'm wrong and i have to unlock to flash?
all i've done so far is do a backup is all. (did a TA backup a while back though)
Click to expand...
Click to collapse
You have to unlock the bootloader to flash custom ROMs. You can flash stock ROMs without unlocking it, but you have to unlock it if you want CM, PAC, PA etc.
Sent from my C6833 using Tapatalk
really, so what would happen if i tried to flash an aosp rom now? would the system partition essentially be read only?
sorry for the Qs but haven't had a locked bootloader since the htc desire (although the s-off for that one was to remap the partitions to allow more room for data) and the reasons for unlocking don't seem to be the same.
tommo123 said:
really, so what would happen if i tried to flash an aosp rom now? would the system partition essentially be read only?
sorry for the Qs but haven't had a locked bootloader since the htc desire (although the s-off for that one was to remap the partitions to allow more room for data) and the reasons for unlocking don't seem to be the same.
Click to expand...
Click to collapse
Nothing will happen if you try it now. You can easily unlock the bootloader by going to Sony's Dev site, request your key and use Flashtool to unlock it. It takes a couple of minutes once you have Flashtool and the drivers installed. It's also perfectly safe to unlock it and you will lose your warranty. BUT you can easily relock it again if something happens to your ZU and the warrenty will be back.
Remember to backup your TA before you unlock your bootloader. It contains a lot if device info and your unique DRM keys. Unlocking the bootloader will wipe the system partition, but you will still have root, photos, music etc. (But do a backup of those just in case).
Sent from my C6833 using Tapatalk
i think that's where i got confused with drivers - unlocking.
i have already done a backup of my TA part so that side of it is ok. i'll leave unlocking until there's a rom i want to try. possibly a complete 4.4 or something.
cheers LM
tommo123 said:
i think that's where i got confused with drivers - unlocking.
i have already done a backup of my TA part so that side of it is ok. i'll leave unlocking until there's a rom i want to try. possibly a complete 4.4 or something.
cheers LM
Click to expand...
Click to collapse
If you've already backed up your TA, it means that you have the drivers installed, so job done All you have to do is to install Flashtool and get your key from Sony (which you will get on your email straight away). Either way, just ask here if/when you want to unlock it so we can guide you through it (it's very easy though).
ran flashtool but gave me driver errors - missing. unable to install the drivers included (i guess due to windows 8 driver signing)

Is there a Stock rom with right 2 left languages?

Hello!
How are you?
Own the LS990 and i use it in Israel on a GSM network after Sprint unlocked it.
Phone is rooted and on primegsm rom v5 (Also tried CloudyG3 2.5).
Any time that i need 2turn off n' on the device, language changed from Hebrew to English.
But even if it could be fixed, i prefer the stock.
What i wanted to ask is:
1. In case i'm back to stock - it could be risky bc's the phone could be locked AGAIN?
2. What is the easiest way to do it without losing ROOT too? (Plz see the following steps - this is how i should do it?)
Flash the zip(called also TOT) -> in LG Flash select "Board DL" -> reboot into "MiniOS" -> unplug the USB cable and press and hold the power button-> Chose in "Normal Boot"
I must know that I understood that correctly...Can u plz aprove it?
Which ZIP should I dounload and use from the following list?
(It is just a webpage...by pressing on it nothing will started)
http://downloads.codefi.re/autoprime/LG/LG_G3/LS990
Thanks!
1. As far as I'm concerned, once Sprint unlocks your phone for GSM, it should be good to go.
2. You will lose root doing the LG Flash method. You will need to install a rom in a recovery in order to keep root.
@djinnerman
Thank for your replay!
1. That nice to hear and know.
2. I really DONT KNOW how to do that.
Can you explain me (one anyone else) how to back to stock step by step?
Also - help me to find the correct file of the stock rom so i wont brick my device?
Thanks again!!!
Well, before I go any farther, I want to clarify what you want to do. Are you wanting to flash a new ROM or go back to stock?
I want to return stock and stay roooted.
Here's a snippet from a previous post I did about rerooting their device and returning to stock.
I would suggest following instructions on downgrading to ZV4 (since stump root works for force brute in order to root your phone).
http://forum.xda-developers.com/spri...1#post54912191
Once you fully restore back to default stock, you will need to go ahead and install stump root. http://forum.xda-developers.com/lg-g...rizon-t2850906
It will allow you to brute force root, which should take about 5 minutes.
After you reboot, you should have root. Go to the market and download supersu. From there you should be able to have root access.
Click to expand...
Click to collapse
If you want a recovery for backups etc, I would get TWRP : http://forum.xda-developers.com/lg-g...8-2-0-t2966129
Or download TWRP manager and flash it from there.
If you want stock capabilities and have all the Sprint crap taken out for a minimalist stock ROM, try out BarePapa http://forum.xda-developers.com/spri...a-zva-t3146284
OK:
1. Right now i am rooted and got PRIMEGSM 4.5 & TWRP.
2. If i want to get back to STOCK (which probably remove the root) - what is the best way to do if i want to flash it manually (by twrp)?
Thank you!
If you already have TWRP and all that jazz and want to just flash it with a zip file, go here http://forum.xda-developers.com/spr...990-zvb-root-method-zvb-rooted-stock-t3211878
A quick google or forum search here led me to this. "ls990 stock rom" or "ls990 zvb"
@djinnerman
I want to verify if i understood you right:
In case i have TWRP (what is "all that jazz"?) - all I need is to download the ZIP of the stock rom and flash it?
That's it?
Thank you so much dud!
shabydog said:
@djinnerman
I want to verify if i understood you right:
In case i have TWRP (what is "all that jazz"?) - all I need is to download the ZIP of the stock rom and flash it?
That's it?
Thank you so much dud!
Click to expand...
Click to collapse
Yes, follow Method A and you'll have stock lollipop
Make sure you wipe cache, dalvik cache, system, and data. Wipe/Advanced/ as well as a backup of your current ROM.
@djinnerman
You'r the MAN !!!!
Thank you so muchhh!
1 More:
If i use the LS990 on a GSM network out of u.s - probably i would need to flash the modem too, so it better to flash
LG-LS990ZVB-Flashable.System.Boot.zip
&
LG-LS990ZVB-Flashable.Modem.RPM.TZ.zip
too?
"Flashable.System.Boot" = ROM?
shabydog said:
@djinnerman
You'r the MAN !!!!
Thank you so muchhh!
1 More:
If i use the LS990 on a GSM network out of u.s - probably i would need to flash the modem too, so it better to flash
LG-LS990ZVB-Flashable.System.Boot.zip
&
LG-LS990ZVB-Flashable.Modem.RPM.TZ.zip
too?
"Flashable.System.Boot" = ROM?
Click to expand...
Click to collapse
Yes. Autoprime mentions that the two zip files in the directory are the flashable ones. I do not have experience in flashing for gsm, but as far as I know, you need to have it unlocked from Sprint, which should be simple. You should have a sim card slot for the gsm carriers and go from there.
I ran into this post not too long ago: http://forum.xda-developers.com/sprint-lg-g3/general/unlock-sim-gsm-how-to-t2853594
It already unlocked and I use it on a GSM network. I have a Sim card slot in my LS990.
Anyone can tell me:
If currently I use the phone on a GSM network - Can i just flash the ROM without the modem?
Thank you very much!

Root/Unroot frustrations

I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
noxarcana said:
I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
Click to expand...
Click to collapse
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
This method works perfectly on T860.
***********************
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
jhill110 said:
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
Click to expand...
Click to collapse
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
noxarcana said:
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
Click to expand...
Click to collapse
Did you get the bootloader unlocked?
Unlocking the bootloader:
https://www.getdroidtips.com/how-to...to_Unlock_Bootloader_on_Samsung_Galaxy_Tab_S6
To get to download mode it's volume up and volume down then plug your pc into device. NOT POWER AND VOLUME DOWN. This can be a pain in the back side.
If you do it this way you'll get the option unlock / lock bootloader or go to bootloader mode.
If you follow the instructions perfectly and then follow the instructions for rooting it will work.
Move on to root.
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Install TWRP.
TWRP :
https://forum-xda--developers-com.c...b-s6/development/recovery-twrp-3-3-1-t3975587
I hope this helps you out.
If you have anymore questions just ask.
Disable DM VERITY ENCRIPTION DISABLER
PATCHED ODIN
jhill110 said:
Did you get the bootloader unlocked?
Click to expand...
Click to collapse
Yep, bootloader unlock was easy. I'll give root another try with your steps in a couple of days when I'm off work. Sorry if I came across a bit aggressive in my previous posts; I have a tendency to do so even when I'm not frustrated.
This has been so frustrating to me because I know rooting is usually a simple process; as you said previously.
jhill110 said:
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Click to expand...
Click to collapse
So, yea, I'm a bit late getting around to this. Sorry.
This is where things get hung up. Everything flashes just fine and I can even get into TWRP; however, when I try to boot the tablet i get the Galaxy Tab S6 screen, then the warning about the bootloader being unlocked, and back to the Galaxy Tab S6 screen but with a "unofficial software" warning....and repeat. It just boot loops and this is where I've since I started this thread.
Also, returning to stock doesn't completely remove root traces as I can't use Samsung Pass and I simply get a warning about the device seemingly being rooted even though it isn't.
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
bartleby999 said:
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
Click to expand...
Click to collapse
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
noxarcana said:
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
Click to expand...
Click to collapse
My bad for some reason I just read that as Samsung Pay. But yeah Samsung Pass also doesn't work with root, I'm not sure if that is permanent though as I've never used Samsung Pass, but did come across this thread https://forum.xda-developers.com/general/rooting-roms/samsung-pass-knox-tripped-devices-t3687977 it is possible to get some components of Knox to function again, (I have a working Secure Folder) so might be worth taking a look.
As for you question...
You should give this thread a good read... https://forum.xda-developers.com/galaxy-tab-s6/development/recovery-twrp-3-3-1-t3975587
Basic steps are... Unlock the bootloader and then boot into system and ensure it's unlocked in settings. You may need to connect to the web, I can't remember tbh
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
bartleby999 said:
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
Click to expand...
Click to collapse
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
noxarcana said:
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
Click to expand...
Click to collapse
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
bartleby999 said:
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
Click to expand...
Click to collapse
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
noxarcana said:
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
Click to expand...
Click to collapse
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
bartleby999 said:
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
Click to expand...
Click to collapse
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
noxarcana said:
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
Click to expand...
Click to collapse
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
bartleby999 said:
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
Click to expand...
Click to collapse
Yea, it looks like Samsung made some "wifi improvements" in OneUI 2.5 and that's causing some kernel issues preventing wifi from working. I think I could find a kernel fairly easily, but I think I'm just going to wait for a kernel update. If it never comes, I'll find an older kernel. Thanks for the help!

Alright I've received the email to unlock the bootloader now I have some questions before using it..

Alright, I've received the email as the title implies but here are the questions I have before I proceed into the whole process
Is there a way to backup the stock image without TWRP? if so how do you get the stock image backed up if it's impossible how to back up the stock bootlover/recovery before installing TWRP if I were to get rid of TWRP one day?
also is it possible to just root the system without flashing anything to avoid data loss? this would be the preferred option actually, thanks! (Using the be2028 t-mobile version, if there's a premade backup that'll be cool too.)
animenote said:
Alright, I've received the email as the title implies but here are the questions I have before I proceed into the whole process
Is there a way to backup the stock image without TWRP? if so how do you get the stock image backed up if it's impossible how to back up the stock bootlover/recovery before installing TWRP if I were to get rid of TWRP one day?
also is it possible to just root the system without flashing anything to avoid data loss? this would be the preferred option actually, thanks! (Using the be2028 t-mobile version, if there's a premade backup that'll be cool too.)
Click to expand...
Click to collapse
I am just getting back to messing around with phones after about 5 years. So many things have changed and I am trying to get answers here as well.
I used TWRP and Magisk to root my phone. Installing TWRP will not wipe your data as it is flashed to a different partition but to install TWRP you have to unlock the bootloader and that will wipe your userdata. And no, I don't believe there is any possibility of rooting without unlocking the bootloader. If you decide you want to go back to stock, there are stock roms available and you can re-lock the bootloader on the N10 so you should be able to set it back to just like it was when you first bought it. I say should because I have never done it, just read that it can be done when I unlocked and flashed mine.
I wish I could be of more help but so many things have changed in the years since I've been away from doing this stuff I feel like a total noob again.
animenote said:
Alright, I've received the email as the title implies but here are the questions I have before I proceed into the whole process
Is there a way to backup the stock image without TWRP? if so how do you get the stock image backed up if it's impossible how to back up the stock bootlover/recovery before installing TWRP if I were to get rid of TWRP one day?
also is it possible to just root the system without flashing anything to avoid data loss? this would be the preferred option actually, thanks! (Using the be2028 t-mobile version, if there's a premade backup that'll be cool too.)
Click to expand...
Click to collapse
No I do not believe there's a way to gain root without flashing anything. There's no need to backup anything you can always use the MSM download tool to restore your device. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4204445/ You should be able to find most of the stock imgs on here already if you'd really need to flash back. I'm no expert either, just my experience with this phone in particular has been pretty straightforward. I never backed up anything lol.
Twrp is iffy i made a backup I'll never use, check out the post about flashing international rom to tmo and metro devices, that's my backup. Also you can run 11.0.3/2 firmware and boot 11 gsi's the post about lir rom has the info. Flash the product_gsi.img referenced there, I have never deleted my product partition and I only leave oos ten installed long enough to take ota's. There are more roms in the source forge page referenced with lir rom post. Flash magisk via recovery, either side load or twrp, pay attention that it flashes partition sda14(super image) or wifi breaks.

Categories

Resources