Related
Hi everyone I'm pretty new to the whole Android world, I've read a lot of stuff through this forum and in general through the internet but I haven't got to the point of really understanding this clear.
I performed the rooting and sim unlocking following the guide on this forum, so basically I had to install the ClockworkMod Recovery.
I read that having installed a custom kernel (or rom, not clear the difference) or a custom recovery (or bootloader, like CWM in this case) voids the warranty.
I also read that is pretty simple to restore the stock kernel/firmware by simply flashing it on with Odin, but what about the Recovery?
I found this post http://forum.xda-developers.com/showthread.php?t=1286432&highlight=stock+bootloader my questions are:
1. Is having the phone flashed with stock kernel (but a different than the original recovery, e.g. CWM) enough to bring the phone back in warranty conditions?
2. flashing the stock unrooted kernel following the above thread will restore also the original android recovery console?
3 if not is there a way of getting rid of CWM and restoring the original android recovery? (I read "just flash it with odin like you did with CWM, but where do I find the package (image) to flash?)
4 the stock kernel in the post seems to me "not official" in the sense that has been ripped from a user, is there any chance that we (SGHI777) will get something more official like the international kernels (GTI9001) that you can find on samfirmware?
5 this is extra, if I have a rooted GS2 (following the forum procedure so CWM+original kernel) will I be able to install official update through Kies? (I'm asking cause the unlock security flaw bugs me a lot...)
Thank you very much to everyone that will answer.
frabass said:
Hi everyone I'm pretty new to the whole Android world, I've read a lot of stuff through this forum and in general through the internet but I haven't got to the point of really understanding this clear.
I performed the rooting and sim unlocking following the guide on this forum, so basically I had to install the ClockworkMod Recovery.
I read that having installed a custom kernel (or rom, not clear the difference) or a custom recovery (or bootloader, like CWM in this case) voids the warranty.
I also read that is pretty simple to restore the stock kernel/firmware by simply flashing it on with Odin, but what about the Recovery?
I found this post http://forum.xda-developers.com/showthread.php?t=1286432&highlight=stock+bootloader my questions are:
1. Is having the phone flashed with stock kernel (but a different than the original recovery, e.g. CWM) enough to bring the phone back in warranty conditions?
2. flashing the stock unrooted kernel following the above thread will restore also the original android recovery console?
3 if not is there a way of getting rid of CWM and restoring the original android recovery? (I read "just flash it with odin like you did with CWM, but where do I find the package (image) to flash?)
4 the stock kernel in the post seems to me "not official" in the sense that has been ripped from a user, is there any chance that we (SGHI777) will get something more official like the international kernels (GTI9001) that you can find on samfirmware?
5 this is extra, if I have a rooted GS2 (following the forum procedure so CWM+original kernel) will I be able to install official update through Kies? (I'm asking cause the unlock security flaw bugs me a lot...)
Thank you very much to everyone that will answer.
Click to expand...
Click to collapse
On nearly all Samsung phones, recovery is a part of the kernel. Flash a new kernel, you've flashed a new recovery.
The stock kernel zImage is as official as it gets - nothing is more official than what was actually flashed into the device by the manufacturer and sold on launch day. The additional evidence that it's official is that it passes the bootloader signing checks, eliminating the "custom kernel" warning screen.
We won't see a samfirmware release until AT&T releases an update.
Stock rooted shouldn't affect OTA updates, however sometimes things you do WITH root (such as debloating) will interfere with OTAs.
Once an OTA update becomes available, expect its fixes to be integrated into ROM releases fairly soon.
FYI there are three components you should know about. Kernel>ROM>Modem
The kernel It's the core/kernel of an operating system. It's main functions are to interact with the hardware a.k.a. Device Drivers, to manage resources (things like memory management and processor time sharing a.k.a. multi-tasking), service interrupt requests, network services and the like. It also provides a System Call Interface (API) to the user space (apps running on the machine) so the apps can use system resources.
Now the why so many part... First of all in general there are MANY options available when compiling (building) the kernel. Things like CPU schedulers, file system support, system type support, etc. etc. etc. So there are many different ways to configure the kernel and that gives many options to "test" and see which might work better or not. Some of them are dead giveaways like compiling the kernel for MIPS and trying to run it on the SGS2 won't work but some are "tweaks" that may help a little or a lot, like CPU management options.
Second part of the why so many is the code. Again as mentioned above things like changing code to make the colors of the display more or less sharp (display device driver), make the file system faster (voodoo lag fix) or overclocking the processor, and different "modem" tweaks are all "enhancements" that people have made to the original Linux kernel source. So those things "creep" into existence over time, since there are many people working on them, and you see different versions of the Kernel from that as well.
Anyone that plays music can relate to the options available in that there are only 12 notes on a guitar fret board but millions (or more) ways to put them together to play music. There are certain things that have to be present in the Kernel (notes) but writing code to enhance them and/or combining options at compile time is much broader (music).
The ROM. ROM is actually Random Access Memory and we flash an image to the "ROM" (which it really isn't but I'll leave that one alone). The "ROM" in this case is the operating system (a version of embedded Linux), which is the basic software needed to run and admin the phone, things like the Kernel, bootloader, device drivers, and file system plus any user apps like the phone dialer, launcher, etc. that are included in the ROM. As you can imagine the possibilities of customization are almost endless when it comes to the ROM. Different kernels, different drivers, different apps and many combinations of those.
The modem is actually part of the kernel. It's the device driver for the phone hardware. Being that it's part of the kernel it "works with" other code that's elsewhere in the kernel and ROM that is "tweaked" for a particular phone in this case. So when you see "use an i777 modem with an i777 kernel" it's because the code in the modem is written to work with the other code in the kernel. It doesn't necessarily mean it will brick the phone and/or not work but it quite often means it won't work the best if it's not "matched".
Actually the modem is NOT part of the kernel. The modem firmware runs on an entirely separate processor (not one of the main application cores.) - the RIL (Radio Interface Layer - part of the ROM) bootloads that processor by sending the modem firmware to it via a serial port when the system boots.
The baseband processor is almost never listed in a phone's specs because it's a "hidden" part of the system. Very often a device like ours will have more CPU cores than just the advertised application processor cores. For example, early Qualcomm MSM7000-series chips had two processors, one for applications and one for radio. Some people labeled these chips as "dual core" even when they really weren't - the two CPUs were completely different.
Similarly, we have two ARM Cortex-A9 cores acting as applications processors, an unknown ARM core doing radio work (much simpler, slower, and power-efficient than the two A9s), and possibly another application-specific ARM core hidden in the GPS chipset. Maybe more.
ok so i just got a galaxy note clone, its not a 5.3 in screen, its a 5inch, 1gz processor, 4gb rom, 512 ram,dual sim, 3g device, the exact model is a PAE8000 Android 4.0.3 5 inch Screen Smartphone. or so its called on ebay. looks pretty lagit, i mean i cant see spending 500+ for a name, that just me though, anyways, not to get off subject. how would you go about rooting this thing and what roms would you use? would you use ODIN? based on what ive seen it looks like its running pure ICS.i guess what im asking is...has anyone on here played with one of these? any help, tips, tricks and rooting info would be great!
The problem with these china clones is that while it may look identical, but that's about it. Everything else is different.
I quite sure you cannot use any kind of method that is used for Gnote (root, roms, kernels) because the hardware/firmware is different thus it requires soft mods that is specifically compiled for your phone. Think your phone as another phone altogther and not in any way associated with Gnote other that its similar looks.
For rooting, I'm sure you cannot use odin because the program and files are specific for Gnote. Maybe you can use those universal rooting app, eg. Superoneclick, I won't say it will work... but you might get lucky.
Another problem is you have to search for clockworkmod that is specific for your phone.. because its phone specific and you may not want to flash Gnote's cwm on this device, you may end up with a brick phone.
I would not recommend rooting your device if you haven't found cwm for it because you may want to backup the entire phone in its stock condition first before starting to meddle around with system files after root. Experimenting with mods/scripts etc after root may have the side effect of having your phone unable to boot into android. If you don't have cwm, you may not have a backup to fallback too.
yea i know, just trying to see if anyone else has played with the same device, if anyone has, please chime in!
Hi,
I'm currently waiting for my Xiaomi device and I have some questions before rooting the phone and doing some other mods.
First of all I'll mention that I've got huge experience in flashing roms, modding etc (just not with Xiaomi), so you don't have to use noob-friendly language.
1)I bought the "Pro" variant, with 16MPx, sdcard expansion and snapdragon 650.
So can I flash any rom that is included in this section: http://forum.xda-developers.com/redmi-note-3/development or is there a difference between Redmi Note 3 Snapdragon & Note 3 Pro?
According to this thread: http://forum.xda-developers.com/redmi-note-3/development/snapdragon-note-ensure-threads-titled-t3351620 it's the same, but I just want to be 100% sure as I just bricked my previous device by flashing a wrong ROM (from other device)
Oh, and I hope the storage option doesn't really matter for ROM flashing, right?
2)I've seen some 2 methods of unlocking bootloader. First one is official, where we sometimes have to wait for some longer time to get the code and the second one is unofficial.
Are there any (dis)advantages using both of the methods, and do I have to use developer ROM to unlock it the official way? Which one is safer?
3)In case my phone would be stuck in a bootloop, can I use MiFlash to repair it?
Do I need to have modified boot.img to do this?
4)Let's assume I have China ROM stable edition. Will I be able to install via update menu the dev version (with locked bootloader) and obtain root by doing this?
5)Can I use FlashFire to flash any zip (of course not a ROM), like some audio mods etc, or am I only allowed to install Xposed with it?
6)Let's say I just flashed a ROM through TWRP but forgot to delete the emmc_appsboot.mbn file. I didn't reboot the phone yet. Will flashing a new ROM (with deleted file), restoring old backup or just deleting the file from system partition (If it exists there) prevent it from bricking?
7)What's with the modified boot.img? I don't quite understand what it's for and when to use it.
Ok, so I think that's all for now. I know these are a lot, but I just want to have some basic information about the phone before I start rooting it.
If you know some good threads that will answer my questions, please post them as an answer.
1.you can't use roms from Redmi Note 3 for Redmi Note 3 PRO;they have differnt CPU;first is equipped with an Mediatek CPU,second one is equipped with an Qualcomm CPU
2.safer method is official method;but why you need this;look around and you will see many people screaming after unlocking BL,installed TWRP,so on and finally BRICK.So my advice:Stay Safe.MIUI OS offers to you all what you needersonalization,good battery life,speed,security.Additionaly unfinished roms and not fully tested software can damage hardware of device
3.you can use MIFlash to repair device,it does exist many guides here or on MIUI Forum
4.yes you can;from China stable----->China developer and from Global stable------>Global developer;this is the order
5.i suppose that ,when you have BL unlocked and root acces,it might be possible
6.i guess not because files chianges occur after OS reboot
7.http://forum.xda-developers.com/showthread.php?t=2587462
1) If you're on the Pro, you're on the Pro. You can only flash for that specific model. The PRO have Snapdragon cpu/gpu, and the non pro version have Mediatek, which make it completely different device. Always be sure that you flash roms that have KENZO in their filename. If you flash ROM made for Mediatek, you'll possibly have a 180 grams brick.
2) I'm still waiting for official unlock code, but after 11 days still haven't got it. Unlocked it by the unofficial way and because I wasn't aware what bastards Xiaomi are, I'v managed to hard brick it so I had to open it and use the two pins for flashing. Please follow the guides in here. The disadvantage of the unofficial way is that EVERY time before you flash new rom, you have to open the archive of the rom, enter the firmware-update folder and delete the emmc_appsboot.mbn. Failing to do that will get you with locked bootloader and the only way to fix the device is by the method I've used (the story above).
3) Better reflash with TWRP. I haven't used any other tool since unlocking the bootloader and flashing the twrp recovery
4) No
5) Yes
6) No. You've already overwritten the mmc_appsboot.mbn the first time. Always check for that file and delete it before flashing. Always.
7) I don't get it also. Some people have problems with wifi without modified boot.img (kernel). Haven't got such problems by now.
ok.
So regarding the point 1. Yes, I know that there's mediatek version also.
But the link I've provided redirects to Note 3 Snapdragon forum.
The thing I wanted to know if there are only 2 types of devices:
a)mediatek, 13mpx, no sdcard,etc
b)snapdragon,16mpx, sdcard
c)snapdragon, 13mpx, no sdcard - it does not exist right?
So for eg. this rom: http://forum.xda-developers.com/redmi-note-3/development/rom-resurrectionremix-v5-6-7-xiaomi-t3365872 is for option b right?
Regarding #2. If I unlock the bootloader official way, do I also have to delete emmc... from the zip before flashing?
#2. Ok, so if I don't get TWRP, how may I backup the whole ROM?
As we know flashing some zip files, or even android itself may not boot after some time. So is there any alternative to TWRP backup (that would copy whole system)?
The snapdragon one is with 16 mpx camera and sd slot (or second sim). It comes in two variants - 2gb ram and 16 gb internal storage or 3gb ram and 32 gb of internal storage. The camera and the cpu are the same in both versions. That's why I've told you to only flash roms that have Kenzo in its name
For non rooted devices,it does exist MI PC Suite for create backup/restore from back-up
Exactly see the fourth question getting different answers.
Too many threads, conflict.... Answers,... ****ty bootloader, my advice if u don't understand things ,don't go 4 unlock.
Dont buy if you not yet ordered
Why not?
I'll receive it on monday probably, so it's too late anyway.
the thing is, that I like modding the phones and unlocking bootloader in Xiaomi will be just a matter of time, that's why I want to learn some basic stuff about this phone.
Because he hadn't read what all the guides say and then end up with hard bricked devices
The phone is a beast.
Yeah, you're probably right. I hope the N3PRO will be at least as good as my z2
Could you tell me one thing. Do I need to delete emmc... file from zip, when I've unlocked the phone official way?
Edit: I think I've got my answer here: http://forum.xda-developers.com/showpost.php?p=66618701&postcount=5
After official unlock, you should be able to do whatever you like. I'm still on the unofficial way, but got unlock permission today. Will let you know what is going on tomorrow (probably, if I have time to reflash).
Gentlemen,
What apk should I use to root with success a Caterpillar :laugh: CAT S31 running Android Nougat 7.1.2 ?
In a first step, I would like to throw away all the G***** ecosystem.
In second step, I also would like to replace Nougat by LineAgeOS.
As LineAgeOS doesn't provide a firmware img for this mobile, it is realistic to choose an image from another mobile using same CPU (snapdragon 210) and same GPU ( Adreno 304) ?
Thanks for your help
SolidSnake
Also interested...
As I can't create new Threads and this one fits totally my needs I would like to continue here.
I am trying to change the OS of a friends phone from his Android 7.1.2 to LineageOS. I was able to successfully change my OS to Lineage on my HTC U11 and some other phones,
but I just can't do anything with the CAT S31 and can't unlock the phone at all. Tried rooting it with KingRoot, RootKHP Pro, ZYKURoot, iRoot and many others.
And I guess that is the main reason I get the following error when I try to flash TWRP:
Code:
UNKNOWN:~$ fastboot flash recovery ~/Downloads/twrp.img
target reported max download size of 262144000 bytes
sending 'recovery' (46312 KB)...
OKAY [ 1.536s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 1.537s
Possibly working rooting method
I found this on another forum:
A set of software for obtaining ROOT privileges.
Driver_Qualcom_m.7z (9.27 MB) [link]
Enter HS QDSLoad 9008 mode from Vol + and Vol- off state and connect without releasing to USB
MiracleBox [link]
The Boot image is processed on the phone by the Magisk manager, then uploaded to the phone using Miracle again from the computer.
MagiskManager-v7.3.2.apk (2.71 MB) [link]
Just in case,
Backup firmware without / Data partition [link]
Attached files
XposedInstaller_3.1.5-Magisk.apk (2.96 MB) [link]
Click to expand...
Click to collapse
But as I don't understand much of carriers on unlocking bootloaders and stuff, could anyone post more information about this method if anyone decides to follow it? That was from a user which says he got to root the phone and that's how they did it. Also the person doesn't talk about unlocking the bootloader, for example.
Just want to make sure it can be rooted before I buy it, because I won't buy a phone that can't be rooted and I'm having a hard time finding a good rugged phone that can be rooted...
EDIT: I've uploaded everything to a folder on my MediaFire account here: http://www.mediafire.com/folder/thqmkg68l2h2r. In case anyone tries this, please say here if it worked! Also, I can't link MiracleBox... They had a "special" version of it there and I think it's better for me to not link it... But search for MiracleBox on Google. You'll find it.
EDIT 2: I'm not into this anymore - from the moment I decided not to buy the phone (not too long after this comment). I'm leaving the link because people still download from it, so maybe it's useful. If it's not useful at all, someone please tell me and I'll delete it.
Wow... its really a tumbleweed here... i have decided not to purchase or use any smartphones whatsoever until it is possible to flash a ROM in this phone... but for some reason the developers are not interested and this is the only phone im interested in.. fml
dokha said:
Wow... its really a tumbleweed here... i have decided not to purchase or use any smartphones whatsoever until it is possible to flash a ROM in this phone... but for some reason the developers are not interested and this is the only phone im interested in.. fml
Click to expand...
Click to collapse
If you really want that to happen, I think you should try another phone.... I'm done with CAT phones. Only the more expensive ones can be rooted with 100% certainty - because there are tutorials about that and not just people saying how they did it in a random post like the one I found (and not all models, I think) -, and I don't remember about ROM flashing (didn't get to that - can't buy them, anyways, too expensive).
Perhaps you could try Blackview? I'm going for them. In my case, BV9500 (not Pro or Plus - but Plus is out of question because there's no root, I think). I think from now on, I'll try to always buy a MediaTek powered phone. As long as you have a ROM and the scatter file, your phone possibly won't brick. SP Flash Tool will save you. As it did with me various times (and I did everything that wasn't supposed to be done and still always worked xD - I only read about what shouldn't be done months after changing phone and getting it to work always). BV9500 has a MediaTek chipset, and a forum has ROMs for it. In any case, even if they hadn't, I can generate my own with SP Flash Tool and have a copy of the stock ROM that came with it, so if I brick it, I can restore it completely. Root seemed to be also to be possible, so I chose it. Gonna buy it when I can.
Sum up, if you want to be possible to flash ROMs of a phone, I'd say go for MediaTek powered devices. I'll try not to go away from them again, as I did with my One Plus X (even though I can flash ROMs on it, but I still trust MediaTek with SP Flash Tool more than others, since my experience with it was "do whatever you want, you can't brick anyways" (and I never did haha)). Can't be completely sure that still happens on newer MediaTek chipsets, but I guess I'll find out by myself if I ever do such stupid things again (after reading, not sure I will haha).
EDIT: You might also want to try RockChip powered phones. I have a tablet with a chipset from them and it's possible to flash partitions with a tool like with MediaTek chipsets with SP Flash Tool. So I'd go for one of those 2. I guess I'll only go for devices where I can flash partitions whenever I want, without having to unlock the bootloader first (less safe as anyone can do whatever they want if they steal the phone, but at least I can't brick them).
Thank You!
DADi590 said:
If you really want that to happen, I think you should try another phone.... I'm done with CAT phones. Only the more expensive ones can be rooted with 100% certainty - because there are tutorials about that and not just people saying how they did it in a random post like the one I found (and not all models, I think) -, and I don't remember about ROM flashing (didn't get to that - can't buy them, anyways, too expensive).
Perhaps you could try Blackview? I'm going for them. In my case, BV9500 (not Pro or Plus - but Plus is out of question because there's no root, I think). I think from now on, I'll try to always buy a MediaTek powered phone. As long as you have a ROM and the scatter file, your phone possibly won't brick. SP Flash Tool will save you. As it did with me various times (and I did everything that wasn't supposed to be done and still always worked xD - I only read about what shouldn't be done months after changing phone and getting it to work always). BV9500 has a MediaTek chipset, and a forum has ROMs for it. In any case, even if they hadn't, I can generate my own with MTK Droid Tool and have a copy of the stock ROM that came with it, so if I brick it, I can restore it completely. Root seemed to be also to be possible, so I chose it. Gonna buy it when I can.
Sum up, if you want to be possible to flash ROMs of a phone, I'd say go for MediaTek powered devices. I'll try not to go away from them again, as I did with my One Plus X (even though I can flash ROMs on it, but I still trust MediaTek with SP Flash Tool more than others, since my experience with it was "do whatever you want, you can't brick anyways" (and I never did haha). Can't be completely sure that still happens on newer MediaTek chipsets, but I guess I'll find out by myself if I ever do such stupid things again (after reading, not sure I will haha).
Click to expand...
Click to collapse
Wow.. thanks for this info Ive never heard of Blackview, definatley going to check them out, :highfive: hopefully I can find a phone no larger than 4.7 inches.. any more than that its just cumbersome for me..
@solidsnake6 @DADi590 any update on it? I've found this:
Install Android 10 on Cat S31 | RootBox Tools
This method teaches you How to install Android 10 on Cat S31, and it's safe, secured and easy to apply update to your smartphone.
rootboxtools.com
&
Cat S31 Root with SuperSU Using TWRP Recovery
On this page, we are going to share with you a guide on how to root your Cat S31 with SuperSU using TWRP or Custom Recovery.
www.mobilewithdrivers.com
kamolinkaaa said:
@solidsnake6 @DADi590 any update on it? I've found this:
Install Android 10 on Cat S31 | RootBox Tools
This method teaches you How to install Android 10 on Cat S31, and it's safe, secured and easy to apply update to your smartphone.
rootboxtools.com
&
Cat S31 Root with SuperSU Using TWRP Recovery
On this page, we are going to share with you a guide on how to root your Cat S31 with SuperSU using TWRP or Custom Recovery.
www.mobilewithdrivers.com
Click to expand...
Click to collapse
Just to say here, I'm not into this anymore haha. I was until I decided not to buy the phone. But I still left the link in case anyone would be interested in whatever I have there which I don't remember (and various seem to be interested, so I'm leaving it there).
That is FAKE. Do not install the APK, it is a program for you to download games and programs.
Hello, until now I avoided to root my device (SGP612 / Stock Marshmallow), because I did not want to risk to lose the drm-keys or do other damage.
Besides that, there some apps, which will not run on rooted devices as netflix (at least I suppose so).
Now working on Tasker and other tools the demand of root is increasing more and more. But still I want to take it restrained and looking for a way to limit the root via ADB. I'm not sure, if that is possible, but I think, that would be a good compromise. Online I found a huge amount of guides and threads "how to root", but all of them, at least it looks like that, ending with an unlocked bootloader, TPRP, SuperSU and so on. I did not read all of them, because that would take years and these guides may also be outdated or even worse incorrect.
Therefor I'm here to ask you about yours assessment.
My main goal would be to:
- Make a full backup
- Protect the DRM-Keys and other irreversible stuff
- No app should be able to detect that the device has been rooted respectively modified on system-level
- Void a reset of the current setup
- Install some apps to system via adb and grant some permissions, uninstall few oem-apps
- Tweak a few settings via adb
Is that possible? And if so, are there some good and simplified guides, which I should read?
Wrong forum. This is for Z3 Compact phone. What you want is https://forum.xda-developers.com/z3-tablet-compact
You can root the phone without unlocking the bootloader, so I would assume that you can do the same with the tablet. You have to flash with an older ROM/kernel first, though, but it is doable.
temporary2010 said:
Wrong forum. This is for Z3 Compact phone. What you want is https://forum.xda-developers.com/z3-tablet-compact
You can root the phone without unlocking the bootloader, so I would assume that you can do the same with the tablet. You have to flash with an older ROM/kernel first, though, but it is doable.
Click to expand...
Click to collapse
I will ask the moderation to move my thread, thanks for the hint.
That sounds complicated to flash an older ROM, especially if no suitable instructions are known to me.
BTW. I prefer to stay at stock.
I am pretty sure you posted in the right forum. Everything you mention is possible, except making a full backup. I wouldn't know how without root or twrp. You can backup your TA partition with a special tool to save your drm keys. It uses the 'dirty cow' exploit so you may need to downgrade first (which wipes your data).
I think root via ADB requires a custom rom. You need to unlock your bootloader, which wipes all data. Alternatively, you can root your device with Magisk. It can hide itself from detection for a set of apps that you select.
M1chiel said:
I am pretty sure you posted in the right forum. Everything you mention is possible, except making a full backup. I wouldn't know how without root or twrp. You can backup your TA partition with a special tool to save your drm keys. It uses the 'dirty cow' exploit so you may need to downgrade first (which wipes your data).
I think root via ADB requires a custom rom. You need to unlock your bootloader, which wipes all data. Alternatively, you can root your device with Magisk. It can hide itself from detection for a set of apps that you select.
Click to expand...
Click to collapse
The thread has been moved by now, so that should be ok.
But still, I do not want any custom-rom. My experience with such on other devices in the past was very frustrating and a waste of time. Had always stability issues on driver-level and other misbehavior. On one samsung device I tested around ten or more roms and all of them was quite ****ty...
And until now it sounds like, I need to install a custom before I even can start to make backups and such. But I want a backup of the status quo, to which I could always rollback, if things gets ugly.
I like the current stock, is a good and stable base, a few tweaks and it would be perfect for me. Of course, I did not test any customs on my current device to be able to make some substantiated conclusion on that but I'm to distrustful to follow this path, especially not when there is no way back.
I miss any imagination what is possible and what is not, or what effect a particular measure entails. Therefor I can't estimate the accuracy of any guide and there are hundreds of them out there, and it looks like the approach is sometimes different. I started reading some of them, but stopped it because I could not retrace the content.
Can you recommend a good guide, which could work out for me and whats the name of the tool to backup the drm-keys? Thanks...
Check here for the TA backup https://forum.xda-developers.com/cr...rsal-dirtycow-based-ta-backup-t3514236/page47
I am very happy with this rom, the developer recently issued a Pie alpha (which I haven't tried yet)
https://forum.xda-developers.com/z3...m-aicp-android-ice-cold-project-o8-1-t3731197
There's a guide for rooting + recovery @ https://forum.xda-developers.com/z3...to-rooted-lollipop-locked-bootloader-t3083980
Be sure you follow the instructions very carefully, since you are flashing (the system partition) with the ROM from a Z3 phone.
The process is similar to the Z3 phones:
- flash to an older ROM
- root
- install custom recovery
- using custom recovery, flash with a prerooted, updated ROM
No need to unlock bootloader and no need for custom ROMs.
Asides from that, I don't know how to do the rest of the stuff in your list.
(I'm debating on getting a used Z3t, which is why I'm researching root possibilities .)