Hello,
I have seen some threads related to root on Z3+/ Z4.
I have read from https://forum.xda-developers.com/crossdevice-dev/sony/patched-magisk-v12-sony-devices-t3582331 where it shows it can root directly to the stock ROM by patching.
I see that there is a requirement to do this from this thread: https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605.
I see the thread mentions about boot image. Where I can get my stock boot image from the phone directory?
Is there anything that I am missing prior for rooting/ TWRP?
Thanks.
Related
I have been rooting, unlocking, and loading Roms on other devices for awhile now, but I'm not familiar with how to manage stock updates. I can't seem to find anything, (so maybe this info could be added to a sticky).
I'm rooted with TWRP and a zipped OTA has been posted in anothet thread for my device, XT1064. What can I do to load it? Do I need to flash back to stock first? Can I simply run a fastboot command? I feel like I should know this by now but I'm a bit confused by all the different sources of information.
Thanks, all, for your help.
I have the same question. If someone who has done this, is out there, please let us know.
you tried asked in that other thread???
If is the OTA update do not use it!!!
If you received the OTA on your phone do not update!!!
you will brick your phone.
To install OTA revert back to stock with the factory image. You will go back to Stock Kernel and recovery.
Or wait til someone builds a stock updated ROM and flash that.
If is a image of the ROM, not the OTA, a already updated ROM just follow the instructions on the thread...
Yes, I did ask in the other thread, but I thought it would be better to post a new Q&A thread to keep from cluttering up the other one. Thanks for your help. I'll just wait for a flashable ROM..
Try this method:
http://forum.xda-developers.com/moto-g-2014/help/guide-update-to-lollipop-losing-apps-t2979971
The main idea with OTA is the incremental nature of the update. To keep OTA filesize to a minimum, the system will be patched, not completely overwritten.
So, if you have altered your system in any way, OTA will fail, because it tries to patch files that differ from what it expects. The OTA will check which device it is executed on and will perform various checksum tests before actually installing itself.
If you are experienced with flashing and know how to modify the update-script inside the OTA.zip, then you can go from XT1068-4.4 to XT1064-5.0.1.
But it is quite a lengthy process and not easy nor recommended
You have to go from XT1068-4.4 to XT1064-4.4 to 5.0 to 5.0.1 and must restore the modem. Last but not least the build.prob has to be modified to reflect dual-sim capability.
By the way, the need to lock the bootloader for OTA is a myth. It is not necessary.
So I've successfully rooted my view 10 however the dev department is dead currently and there isn't a custom recovery so my question is can I use something like flashify to flash it because I've installed magisk manager but don't want to go any further until I'm sure.
If you've used some other root method you'd first have to remove that.
After that you can use the Magisk Manager to patch a copy of your device's boot image which you can then flash manually.
Check the release thread for more installation instructions, and the installation and troubleshooting guide for general tips and tricks.
Didgeridoohan said:
If you've used some other root method you'd first have to remove that.
After that you can use the Magisk Manager to patch a copy of your device's boot image which you can then flash manually.
Check the release thread for more installation instructions, and the installation and troubleshooting guide for general tips and tricks.
Click to expand...
Click to collapse
Thanks. Yeah I read that thread, now my isie is trying to find the honor view 10s boot image for it to patch.
Yut kill
whymista said:
Thanks. Yeah I read that thread, now my isie is trying to find the honor view 10s boot image for it to patch.
Yut kill
Click to expand...
Click to collapse
Your device's forum is the place for that, but I saw you already asked. Let's hope you get an answer.
Judging from this thread it should be possible to use the Huawei Update Extractor to get the boot image.
Didgeridoohan said:
Your device's forum is the place for that, but I saw you already asked. Let's hope you get an answer.
Judging from this thread it should be possible to use the Huawei Update Extractor to get the boot image.
Click to expand...
Click to collapse
Yeah I found a tool that is supposed to do it on here as well as an app that is supposed to download the firmware, however so far after looking at a YouTube video about how to use it I've apparently not either done it correctly or haven't found the correct file because I've not seen the images. It says I need to find the update.app which I haven't found. I'll try again this evening when I get off work
Yut kill
whymista said:
So I've successfully rooted my view 10 however the dev department is dead currently and there isn't a custom recovery so my question is can I use something like flashify to flash it because I've installed magisk manager but don't want to go any further until I'm sure.
Click to expand...
Click to collapse
Please can you explain further how you went about it?
One way is to use this img from this thread https://forum.xda-developers.com/ho...stock-b122-t3730660/post75393193#post75393193 the other is through the tool they provide.
Hi,
I am very new to this android world so my queries might feel stupid. Actually i m here after 3 years and that is very long period in this world. I know about rooting(super Su), bootloader and recovery (stock,CM and TWRP) . Recently read about Magisk and got some queries. Hope you will help me out. These are not device specific but need to learn.
What i read/study i found these readings...
1. Magisk roots device systemlessly (does not touch system partition) so one can get OTA updates easily.
2.To install and run Magisk one needs to unlock the bootloader .
3.(Device Specific) My redmi MI Flash tool says,If you unlock the bootloader , you wont get OTA updates.
4.I have previously rooted my galaxy Y and uninstalled system apps. If i delete sys apps from magisk,still can we say that we are not touching system.
So all statements are true? or some? or none ?
Here my device is redmi 3s (6.0.1- MIUI 9.6.1.0 Global Stable).All these queries are just in relation to OTA system updates. Nothing related to warranty.
Thanking You
Yes.
Yes.
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
As long as you use Magisk's debloating feature of replacing files or directories with empty ones, you're good. The actual /system partition won't be touched. Use a module like the Debloater module by @veez21, or make a debloater module yourself.
Didgeridoohan said:
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
Click to expand...
Click to collapse
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?
inwell said:
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?
Click to expand...
Click to collapse
Yes. But, having both Magisk and a custom recovery (an OTA won't install with a modified boot image and a custom recovery installed) I always find it easier to download the update and flash it manually. But, like I said, I have no idea if this is true for Xiaomi.
1. Ok. i also heared that when you update your device,you lose root...not true ? Or you need to root again ?
2.In normal stock device,we get update notification and we downlaod then restart (as per convenience)device to update.
If i remove some system apps from my rooted device and unroot the device,manage to get stock recovery back ,will the OTA update system treat my device as Stock-untouched? And install updates just as stock device will do ?
3. Is boot.img and bootloader are same things? Coz i read that for re locking boot loader you need to flash boot.img from stock software. (But Some procedures just use fastboot and relock oem command-they wont use boot.img,dont know why )
I read that unrooting,restoring stock recovery and locking bootloader again is more difficult/complicated than the rooting procedure
Some one should come up with solution just like Windows Restore .If you want to go back to everything STOCK,just use that feature same as done to Restore Windows in its previous state.
Any update that also updates the boot image (which means pretty much all) will remove root. But, that's just a simple case of reflashing Magisk right after applying the update.
If you've touched /system in any way, removing system apps or even just mounting the /system partition read-write, an OTA will fail. To be able update with an OTA your /system and /vendor partitions need to be untouched and you need to have the stock boot image and stock recovery installed. If your device doesn't conform to this the OTA will fail.
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Going back to full stock is usually just a matter of flashing a full factory image/firmware package/stock ROM. Quite easy... Of course, some manufacturers make it harder than others.
Didgeridoohan said:
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Click to expand...
Click to collapse
Ok. As you say the two are different , but can you explain in simple words (terms) that how they both are related/linked/connected? Coz as i read some forums/posts i get to read
1. To relock/lock bootloader you need to flash boot.img which suggests these (terms) are linked/connected.
2. but same time some forums/post suggest no img file flashing but just a fastboot command(s) to relock bootloader. In this case it seems they are not linked/connected.
And if the above 2 statements are true and device specific then how the bootloader and boot image are linked and not linked in diff devices? what changes are made so that in some cases these are linked and in some not
Sorry for asking too much. But you were really very kind to help me out.Thank you once again
I'm not 100% accurate (and someone will hopefully come I'm and correct me if needed), but basically the bootloader checks that everything is alright and then starts up your device. After that the boot image (ramdisk and kernel) takes over. Ramdisk basically makes sure all the partitions are mounted, and the kernel is exactly what it sounds like. The core of the OS, making sure that everything is working as it should.
This is of course a huge over-simplification, so if you want more you'll have to search around (and there are tons of resources around the web).
The main reason I can think of right at the moment for wanting to flash a boot image before locking the bootloader is that it's generally a good idea to have your device fully stock and functional before doing so. After you've locked the bootloader there might not be any going back if things start acting up and you could end up with a nice paperweight.
Questions are good. That's how you learn. I do believe that you'd be much better of searching around the internet for your answers. They've been put out there many, many times.
Ok.Thank you very much.I will learn more ...
I rooted the e5 plus using this method: https://forum.xda-developers.com/mo...o-e5-plus-rhannah-backup-magisk-root-t3822702
This was different from what I'm used to as normally TWRP replaces the stock recovery and then root is applied. Here, TWRP is only used in fastboot and not applied permanently.
A couple of questions:
Since recovery is not replaced, can this device receive OTA updates with no issues?
Can a normal factory reset be done without soft bricking the device?
If I want to install zip files for mods etc, can I use the fastboot temp TWRP to do this and it will still work?
Are there any actions/caveats that should be done or avoided with this TWRP method?
Excuse my ignorance but I'm sure someone else may have the same question and I'd rather not brick my device.
Thank you.
shezzy83 said:
I rooted the e5 plus using this method: https://forum.xda-developers.com/mo...o-e5-plus-rhannah-backup-magisk-root-t3822702
This was different from what I'm used to as normally TWRP replaces the stock recovery and then root is applied. Here, TWRP is only used in fastboot and not applied permanently.
A couple of questions:
Since recovery is not replaced, can this device receive OTA updates with no issues?
Can a normal factory reset be done without soft bricking the device?
If I want to install zip files for mods etc, can I use the fastboot temp TWRP to do this and it will still work?
Are there any actions/caveats that should be done or avoided with this TWRP method?
Excuse my ignorance but I'm sure someone else may have the same question and I'd rather not brick my device.
Thank you.
Click to expand...
Click to collapse
OTA won't work if rooted, you'll have to flash stock boot or flash full stock ROM.
Flashing twrp causes issues because of avb and dm-verity
TWRP won't have access to data because of encryption and won't be able to write to system.
Basically you're only booting twrp to make a backup and then use Magisk to patch your boot.img for root. From there you can install magisk modules and Xposed as well as any apps you use that need root.
You might use the TWRP installer within Android to install TWRP but it didn't boot for me on my E5 Plus.
reaper-death said:
Basically you're only booting twrp to make a backup and then using Magisk to patch your boot.img for root.
.
Click to expand...
Click to collapse
Ok so that's the answer I was looking for. TWRP is ONLY for backing up in our case since it doesn't have access. Therefore, none of what I asked about will work.
shezzy83 said:
Ok so that's the answer I was looking for. TWRP is ONLY for backing up in our case since it doesn't have access. Therefore, none of what I asked about will work.
Click to expand...
Click to collapse
These Moto e5 + posts have become pointless.
No method works and if root does work it will have issues. The original poster can't fix the issue because they don't know what they are talking about half the time.
We need better people on here who can make a video or explain how to do this without ****ing with our heads ?
Like a person who knows what they are doing with that exact phone model and are not just saying **** for a post ?
Contact me if you need real help fixing these people's mistakes [not root] "fix a bricked phone"!
Hi all. Been a long time. Hope I can get some guidance here.
As always, I've been doing my research and testing, but I haven't got it quite right yet. Here is my issue:
I'm able to flash TWRP, but upon reboot, it reverts back to the stock Android recovery. Found out that its a security feature and you need to disable it. Is this where dm-verity comes into play? Do I need to flash a zip file in TWRP after flashing it, or flash something via ODIN in order to disable this security feature? Also, I've read that after flashing TWRP (and after removing dm-verity or before?), you need to format (not wipe) the /system and/or /data partitions in order to remove the encryption.
I'm a little confused as to the proper sequence of steps in order to accomplish this. I've read some guides here on XDA, but I'm still not getting it regarding after flashing TWRP. Or am I not supposed to flash TWRP first?
I know a little bit about Linux but I am by no means an expert.
My phone is the Note 9 N9600, dual sim, 128GB. Its running stock Samsung Android 10 (OneUI 2.1), Baseband version N9600ZHU4ETG1, Build number QP1A.190711.020.N9600ZHU4ETG1.
I also remember that in some situations, it may be necessary to downgrade the installed ROM in order to properly flash. Hope thats not the case here.
I will continue to search, but any advise would be greatly appreciated. Here is the guide that I've been using as a point of reference: https://forum.xda-developers.com/ga...ecovery-twrp-galaxy-note9-snapdragon-t3845536
Thanks
Talabis said:
Hi all. Been a long time. Hope I can get some guidance here.
As always, I've been doing my research and testing, but I haven't got it quite right yet. Here is my issue:
I'm able to flash TWRP, but upon reboot, it reverts back to the stock Android recovery. Found out that its a security feature and you need to disable it. Is this where dm-verity comes into play? Do I need to flash a zip file in TWRP after flashing it, or flash something via ODIN in order to disable this security feature? Also, I've read that after flashing TWRP (and after removing dm-verity or before?), you need to format (not wipe) the /system and/or /data partitions in order to remove the encryption.
I'm a little confused as to the proper sequence of steps in order to accomplish this. I've read some guides here on XDA, but I'm still not getting it regarding after flashing TWRP. Or am I not supposed to flash TWRP first?
I know a little bit about Linux but I am by no means an expert.
My phone is the Note 9 N9600, dual sim, 128GB. Its running stock Samsung Android 10 (OneUI 2.1), Baseband version N9600ZHU4ETG1, Build number QP1A.190711.020.N9600ZHU4ETG1.
I also remember that in some situations, it may be necessary to downgrade the installed ROM in order to properly flash. Hope thats not the case here.
I will continue to search, but any advise would be greatly appreciated. Here is the guide that I've been using as a point of reference: https://forum.xda-developers.com/ga...ecovery-twrp-galaxy-note9-snapdragon-t3845536
Thanks
Click to expand...
Click to collapse
once you boot into twrp then flash the 1st kernel 2nd magisk
Then follow this here flash 3rd multidisabler.zip and 4th forceencrypt_disabler_q.zip for Android 10 and format data.
The links are on the same guide