Loading custom ROMS - Engineering build included. - myTouch 3G Slide Android Development

Trying to root your phone and get a custom recovery on it and a custom rom?
Here are some important links needed to complete the task.
Although it sounds complicated, the process isn't all bad so long as you follow the steps in the proper order and exactly as written.
Step 1: Root - http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_HTC_Slide DO NOT TRY TO FLASH CUSTOM ROM YET - ONLY ROOT THE PHONE
Step 2: Flash an Engineering build. The engineering build downgrades you to a test build that allows you to easily boot into the custom recovery mode at a LATER time. Without this build after a custom rom has been installed it is VERY difficult to enter recovery mode to upgrade or change anything at a later date. TRUST ME.
http://forum.xda-developers.com/showthread.php?t=703076
Step 3: Re-root - The engineering build is not rooted by default. You must re-root the phone again to prep for the new recovery software and the new custom rom. - http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_HTC_Slide
Step 4: Flash - Finally you can flash whatever you please! - The above link in step three covers how to flash Cyanogenmod - Please refer to your custom rom's instructions to make sure you don't BRICK your phone!!!!!
Sticky?

matt897 said:
Trying to root your phone and get a custom recovery on it and a custom rom?
Here are some important links needed to complete the task.
Although it sounds complicated, the process isn't all bad so long as you follow the steps in the proper order and exactly as written.
Step 1: Root - http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_HTC_Slide DO NOT TRY TO FLASH CUSTOM ROM YET - ONLY ROOT THE PHONE
Step 2: Flash an Engineering build. The engineering build downgrades you to a test build that allows you to easily boot into the custom recovery mode at a LATER time. Without this build after a custom rom has been installed it is VERY difficult to enter recovery mode to upgrade or change anything at a later date. TRUST ME.
http://forum.xda-developers.com/showthread.php?t=703076
Step 3: Re-root - The engineering build is not rooted by default. You must re-root the phone again to prep for the new recovery software and the new custom rom. - http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_HTC_Slide
Step 4: Flash - Finally you can flash whatever you please! - The above link in step three covers how to flash Cyanogenmod - Please refer to your custom rom's instructions to make sure you don't BRICK your phone!!!!!
Sticky?
Click to expand...
Click to collapse
Seriously? You needed to create a new thread for this?
Three letters: meh

Even though its not mind blowing for the more experienced people on here, it really isn't broken down anywhere

matt897 said:
Even though its not mind blowing for the more experienced people on here, it really isn't broken down anywhere
Click to expand...
Click to collapse
Uhhhhh....
First post:
Next Guide For Flashing the ENG-BUILD with Test-key Recovery
http://forum.xda-developers.com/showthread.php?t=703076
Updating the Radio Once Everything Is Done
http://forum.xda-developers.com/showthread.php?t=705064
Click to expand...
Click to collapse
Your guide doesn't even bother to mention that you need to upgrade your radio after downgrading...
Oy vey.

And you really think this should be stickied?
Sent from my T-Mobile myTouch 3G Slide using XDA App

All hes trying to do is help no need to get on his case about what he missed or didnt..

I've NEVER had to "re-root" after flashing Eng build...

Yeah, there is no reason to reroot before flashing a custom ROM. That is just a waste of time, you are going to overwrite what you just did as soon as you flash the ROM.

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] What does the custom recovery do?

I'm following the steps in the link below to root my phone:
http://forum.xda-developers.com/show....php?t=1426377
At step 3, I did get a successful message (I can't remember the message now, but, it seemed successful), but, what exactly does it do? Should I have an extra recovery file on my computer or phone? I don't see any new file created on my computer. So, I just want to make sure it worked properly before moving on.
Thanks.
new file
mordsith said:
I'm following the steps in the link below to root my phone:
http://forum.xda-developers.com/show....php?t=1426377
At step 3, I did get a successful message (I can't remember the message now, but, it seemed successful), but, what exactly does it do? Should I have an extra recovery file on my computer or phone? I don't see any new file created on my computer. So, I just want to make sure it worked properly before moving on.
Thanks.
Click to expand...
Click to collapse
Oops, overlooked this question. If you were communicating with your phone using adb, i don't think anything was created on the computer. The successful thing was unlocking the phone I think, so you could install a custom recovery, which lets you install custom roms. If you've already installed a new rom and run through the setup, I gotta figure the installation of the recovery was successful, as you can't flash custom rom without having a custom recovery installed first. Remember that with some roms you must download the appropriate gapps to provide a handful of the google apps that couldn't be included in the custom rom.
What does the custom recovery do?
pbergonzi said:
Oops, overlooked this question. If you were communicating with your phone using adb, i don't think anything was created on the computer. The successful thing was unlocking the phone I think, so you could install a custom recovery, which lets you install custom roms. If you've already installed a new rom and run through the setup, I gotta figure the installation of the recovery was successful, as you can't flash custom rom without having a custom recovery installed first. Remember that with some roms you must download the appropriate gapps to provide a handful of the google apps that couldn't be included in the custom rom.
Click to expand...
Click to collapse
No worries, it's probably better that this question is separated in a new thread, anyways.
I didn't move on. I restrained myself from going ahead! Thank goodness you answer pretty fast . Learned the hard way in other experiences.
So, I didn't install a custom rom and based on the original post, I gather, there is no need to., so I'll skip it for now. However, can I install it later, correct, after following the remainder of the instructions?
Thanks.
custom rom
mordsith said:
However, can I install it later, correct, after following the remainder of the instructions?
Thanks.
Click to expand...
Click to collapse
You can do ANYTHING!!! You are an infinite soul, unbound by nature and the laws of physics.
And I'm sure you will be able to flash a custom rom following the instructions when you want to, seeing as you have the good sense to read and be cautious.

Softbricked my phone exactly eight times this week... wtf am I doing wrong (NC5)?

Guys I'm really coming to an end here with all these flashing custom Roms stuff...
Why is it that all these Rom Developers just assume you to know everything and never give step by step instructions on things? For example it would just be like 1. full wipe 2. flash rom 3. profit. If it was that phucking simple I wouldn't be getting soft bricked every time I try to flash a rom using twrp or safestrap would I?
I'm on nc5 right now and I tried flashing these two Roms(http://forum.xda-developers.com/galaxy-s4-verizon/orig-development/rom-dirty-unicorns-v9-1-t3025820 and http://forum.xda-developers.com/showthread.php?t=2643031) and it soft bricked me eight times already.
I downloaded this stock firmware (https://www.androidfilehost.com/?fid=23501681358539677) so I can unbrick my phone and installed both twrp and safestrap to flash the above two custom roms and I can't phucking do it. It softbricks me everytime after it says it's gonna reboot.
What do I do guys? I mean why is it keep getting softbricked and why is no one willing to give you a step by step instruction on how to install twrp and safestrap on to your phone? And plus, even if you do for some reason flash twrp or safestrap and back up your files, you're still phucked if you flash the custom rom and it gets you stuck in a boot loop WITH NO WAY TO REBOOT RECOVERY. What the phuck is even the purpose of backing up if you're gonna get stuck in a bootloop anyways and you can't flash in recovery..?
jkim204 said:
Guys I'm really coming to an end here with all these flashing custom Roms stuff...
Why is it that all these Rom Developers just assume you to know everything and never give step by step instructions on things? For example it would just be like 1. full wipe 2. flash rom 3. profit. If it was that phucking simple I wouldn't be getting soft bricked every time I try to flash a rom using twrp or safestrap would I?
I'm on nc5 right now and I tried flashing these two Roms(http://forum.xda-developers.com/galaxy-s4-verizon/orig-development/rom-dirty-unicorns-v9-1-t3025820 and http://forum.xda-developers.com/showthread.php?t=2643031) and it soft bricked me eight times already.
I downloaded this stock firmware (https://www.androidfilehost.com/?fid=23501681358539677) so I can unbrick my phone and installed both twrp and safestrap to flash the above two custom roms and I can't phucking do it. It softbricks me everytime after it says it's gonna reboot.
What do I do guys? I mean why is it keep getting softbricked and why is no one willing to give you a step by step instruction on how to install twrp and safestrap on to your phone? And plus, even if you do for some reason flash twrp or safestrap and back up your files, you're still phucked if you flash the custom rom and it gets you stuck in a boot loop WITH NO WAY TO REBOOT RECOVERY. What the phuck is even the purpose of backing up if you're gonna get stuck in a bootloop anyways and you can't flash in recovery..?
Click to expand...
Click to collapse
If anyone could give me a step by step guide on how to install any android 5.0 custom rom (preferably roms with the least amount of apps installed) from my current version of phone NC5, I will donate $50 thru paypal.
Thank you.
jkim204 said:
If anyone could give me a step by step guide on how to install any android 5.0 custom rom (preferably roms with the least amount of apps installed) from my current version of phone NC5, I will donate $50 thru paypal.
Thank you.
Click to expand...
Click to collapse
Listen man these developers take alot of time out of their busy schedule just to support our locked down phone, the least you can do is show some gratitude and do a little research on your own before trying to bash them for "lack of instructions" .
On Dan's GPE thread last night numerous people clearly told you once you upgrade your phone past MDK you CAN NOT RUN TWRP or CWM your only option is SafeStrap & Safestrap compatible ROMS. I actually linked you to an AOSP ROM for Safestrap so you can check that out before you try flashing ROMS that are not compatible with your device.
A little reading around on some threads goes quiet a ways! As mentioned, you can only use SS compatible ROMs since you have a locked phone. That explains all of your soft bricks. Use a compatible ROM and you will see how easy it is to actually use SS with numerous ROMs on this board. Some great ROMs here actually!
To the OP, sell your phone and buy one based on MDK software. You may pay a slight premium but you'll have the freedom to flash anything you want.
Type in rootjunky for youtube videos. I used his step by step processes for install of safe strap and more. I am new to this also. Very helpful. It's a learning experience. I have had to reset device like 6 times also.
---------- Post added at 04:32 PM ---------- Previous post was at 04:24 PM ----------
scrillakev said:
Listen man these developers take alot of time out of their busy schedule just to support our locked down phone, the least you can do is show some gratitude and do a little research on your own before trying to bash them for "lack of instructions" .
On Dan's GPE thread last night numerous people clearly told you once you upgrade your phone past MDK you CAN NOT RUN TWRP or CWM your only option is SafeStrap & Safestrap compatible ROMS. I actually linked you to an AOSP ROM for Safestrap so you can check that out before you try flashing ROMS that are not compatible with your device.
Click to expand...
Click to collapse
Can you help me with something regarding a post about a problem with hyperdrive install on vrufnc5 Verizon s4 with safe strap installed?noticing after my wipe and right when I swipe to install rom it says unable to mount E:system/orig but goes through whole install process when done I flash modules. Then on reboot I get Verizon detected software not authorized take to store for more help. Well got back to idin...etc..Please help if u don't mind. Thanks

New to Sony, best guide & Q's before taking the plunge.

Hello all,
Im after purchasing a Z5c but before i do i was wanting to know a few things. Im coming from a samsung device which i find so simple to flash. The Z5c will probably be running MM.
I will be wanting to root the device and run xposed from the moment i get it. If i follow this guide:- https://forum.xda-developers.com/z5-compact/general/guide-how-to-root-z5c-painful-using-t3549388
Is this the best guide to use for a sony noob?
1. Will i still be running the stock sony firmware (inc kernal)?
2. All aspects of phone working (finger print, BionZ, x-reality engine, camera de-noise etc)
3. A custom recovery.
Thanks In advanced
OK, so i went for it any way after a lot more reading and hitting problems along the way. So i'll update this with what ive learnt. I did use the guide i've linked above.
I had to downgrade so went through the downgrade instructions and then followed the guide.
At Step 1 - Backup the TA partition, it took me three tries for it to work & a reboot after the first try, only hint i can give is just to try it a few times as is mentioned in the guide.
At Step 2 - Unlock the boot loader I had an issue with the command. The -i command was not recognised in the latest version of platformtools. I had to use a previous version (will update this post with a link).
At Step 6 - Patch the kernel. (1) I had a few issues. superuser.zip was not properly intergrated so i had to flash the zip in recovery after finishing the rest of the guide. (2) I believe the integrated TWRP has issues with backup (ref) so either skip it and flash this version or add it, its up to you. If you do add it and encounter an error similar to this " Skipping TWRP recovery. No kernel modules for 3.10.84-perf-XXXXXXX available" follow this guide.
I skipped putting xposed in the kernel and just flashed the zip via recovery & installed the installer all from the official xposed page after everything was setup.
Thanks for reporting your experiences. I have had my Z5C for a month now. I am wanting to root it, so your experiences are helpful and encouraging.
Does the camera continue to work? I do not want to lose the camera.
Keep on reporting please!
You wont lose the camera, every stock-based custom kernel here has a DRM fix to emulate the keys if they are not found.

All about root/magisk/etc

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

Categories

Resources