Hello eveybody.
I have a question. Actually I have more .. a lot, but for now:
Up to what buildnumber is it possible to root the P8 Lite?
(Because I had B605 and tried to root it but failed. Got stuck in logo, and now I have stock rom B609.
Still trying to root but get all kind of errors and weird things I dont understand ... I am a newbie at this though.)
Oh, also what else do i need to do before trying to root for the tenth time ? (Log out of Huawei account? reset facory settings? ... or anything?)
Kind regards,
TommyWhite
TommyWhite said:
Hello eveybody.
I have a question. Actually I have more .. a lot, but for now:
Up to what buildnumber is it possible to root the P8 Lite?
(Because I had B605 and tried to root it but failed. Got stuck in logo, and now I have stock rom B609.
Still trying to root but get all kind of errors and weird things I dont understand ... I am a newbie at this though.)
Oh, also what else do i need to do before trying to root for the tenth time ? (Log out of Huawei account? reset facory settings? ... or anything?)
Kind regards,
TommyWhite
Click to expand...
Click to collapse
Your can error every versions... I'm on B610 and have rooted it with Magisk... I guess you already have rooted it before so you're not new to this... Well anyway, to root you must have TWRP recovery, and the root file... Boot into recovery mode and simply flash the root file...
What error did you get while rooting on B605?
You probably got stuck in boot animation because you flashed superSU in system mode. It should be installed in system-less mode. Magisk will install only in system-less mode and I think it's better at passing the safetynet.
amageek said:
Your can error every versions... I'm on B610 and have rooted it with Magisk... I guess you already have rooted it before so you're not new to this... Well anyway, to root you must have TWRP recovery, and the root file... Boot into recovery mode and simply flash the root file...
What error did you get while rooting on B605?
Click to expand...
Click to collapse
Thanks for replying :good:
What do you mean with "Your can error every versions..."? .. Do you mean you can root every version?
I am very new to this. Half of the time I dont know what the H im doing, and all of the time I only have a slight idea of what is going on in the Phone. For example I dont even know what a root file is, could you tell me?
How did you root with Magisk if I may ask? And whats the difference with SuperSu?
I had all kinda errors and issues along the way from B605 to B170 and B123 Android 5 back to 6 and B609. (I could make a thread of it ... maybe it helps others???)
Because today I finaly rooted my Phone.
Weirdly enough root checker basic sais it isnt but other root checkers say it is (and my device itself said after reboot that it was) ... so what to make of that?
Can I update the Phone now its rooted without unrooting it?
@keikari
Thanks for responding.
But im afraid I cannot quite follow you.
Could you explain a bit more please?
(Can you also maybe read the last bit of my other reply?)
TommyWhite said:
@keikari
Thanks for responding.
But im afraid I cannot quite follow you.
Could you explain a bit more please?
(Can you also maybe read the last bit of my other reply?)
Click to expand...
Click to collapse
You can't update phone which is rooted(as far as I know).
Do you have TWRP recovery installed?
If you had TWRP installed and you rooted by flashing SuperSu(this is what other guy meant with "root file"). By default SuperSu installs in system mode(meaning it does it thing into system partition). You need to install other zip file first to make it install system-less mode(meaning it does it thing into boot partition).
Magisk is also flashable zip and similiar to SuperSU. If you use apps that need to pass safetynet(like netflix) you want to root with magisk.
Don't know did that helped at all. It's hard to explain when I only know how to use it but don't know why/how it works : D
And if you don't mind doing factory reset before updating, you can also install official updates in TWRP.
Uhhhmmm ok. Well I had to copy eu.chainfire.supersu-1 folder from boot folder to system folder so I dont know what to call that than.
I have TWRP now yes thank you.
But I dont understand about safetynet, coz I just tried Netflix and it works just fine ... and I got SuperSu not Magisk.
By the way when I press on SuperSu nothing happens ... how come?
Also your telling me that I can install official update with TWPR without unrooting it?
And, if you dont mind telling me, whats better to make backup with TWPR or Titanium backup?
While im at it ... if I make a backup of rooted Phone and accidently unroot it by update or something cant i just restore the backup to unroot it again?
Thanks in advance, sorry for the many questions. (Ill learn a lot; )
1. I don't think you can just copy superSu stuff(though not 100% sure, I rarely do things manually if I don't have to. Mostly because lack of knowledge : D )
2. Maybe stock rom passes safety net and it's nothing to really think about as an user. Because if everything works like you want -> no reason to care. If doesn't work -> now you care and you can find answer since you have something to look for
3. Root isn't actually thing you can loose. It's thing that you just install in the rom. As user you can think it like an app.(which just has to be installed a bit differently).
4. When you press SuperSu, Supersu app should open (maybe your copying broke it)
5. TWRP is to back up whole rom(or some partitions). Like if you "soft brick" your device or format system/boot/data partition you can restore it back exactly like it was with TWRP backup. You should do this every time you install new rom or some stuff that modifies system like xposed. It saves time and nerves if things don't work.
5.1 Titanium back up is to back up app and/or app data(like progress in games). This is good if you are changing rom or wanting to re-install your current rom.
6. You'll soon understand the actual concept of the root. Like with p8lite only thing you need to worry is that you have unlocked bootloader. Which you should have since you were able to install TWRP.
7. About installing firmware in TWRP is kind of easier, because stock method will need non-rooted firmware and only few exactly correct firmwares can be installed on top of your current firmware. With TWRP you can even install roms from other kirin 620 devices. (My phone is honor 4x, but I used to use p8lites firmwares because it had more updates) TWRP updating will wipe data.
Happy to help. I think I answered most of your questions in that, ask if you need better details. It would be hard to write guide that has all basics explained the way it would be easy to understand, you'll learn faster when you keep trying and ask question as they come(like you have) at some point you will do something wrong and be like **** this **** and start over again. Then it will became easier and you will also learn that it's difficult to actually brick this phone(some people are too scared about it and few have succeeded in it, but no idea how : D) )
Thanks for using actual english in your questions. :good:
TommyWhite said:
Uhhhmmm ok. Well I had to copy eu.chainfire.supersu-1 folder from boot folder to system folder so I dont know what to call that than.
I have TWRP now yes thank you.
But I dont understand about safetynet, coz I just tried Netflix and it works just fine ... and I got SuperSu not Magisk.
By the way when I press on SuperSu nothing happens ... how come?
Also your telling me that I can install official update with TWPR without unrooting it?
And, if you dont mind telling me, whats better to make backup with TWPR or Titanium backup?
While im at it ... if I make a backup of rooted Phone and accidently unroot it by update or something cant i just restore the backup to unroot it again?
Thanks in advance, sorry for the many questions. (Ill learn a lot; )
Click to expand...
Click to collapse
By default, SuperSu installs root in system mode. It will fail the SafetyNet test (which checks if the android system is modified or not if it fails, you can't run SnapChat and Android Pay will not work too). If you root by Magisk, the SafetyNet test will pass..
To make it clear, since you have TWRP, download the Root file (SuperSu or Magisk) and then flash the root file from TWRP... Copying and pasting won't work.
These are the files: SuperSu v 2.78 and Magisk v 13.3.. Download either of these files and flash through TWRP..
And yes, I meant you can root...
---------- Post added at 01:08 ---------- Previous post was at 01:04 ----------
To answer your other question, when you update your phone it will unroot it... You can root it again by simply flashing those files...
Do Refer the MEGA Thread for more information... Banakafallata has explained everything neatly...
amageek said:
By default, SuperSu installs root in system mode. It will fail the SafetyNet test (which checks if the android system is modified or not if it fails, you can't run SnapChat and Android Pay will not work too). If you root by Magisk, the SafetyNet test will pass..
To make it clear, since you have TWRP, download the Root file (SuperSu or Magisk) and then flash the root file from TWRP... Copying and pasting won't work.
These are the files: SuperSu v 2.78 and Magisk v 13.3.. Download either of these files and flash through TWRP..
And yes, I meant you can root...
Click to expand...
Click to collapse
Isn't magisk 14 https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 better than 13.3 or does it have some bugs?
keikari said:
Isn't magisk 14 https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 better than 13.3 or does it have some bugs?
Click to expand...
Click to collapse
Yes but I haven't uploaded the file in my Mega Cloud... He can update it ..
keikari said:
1. I don't think you can just copy superSu stuff(though not 100% sure, I rarely do things manually if I don't have to. Mostly because lack of knowledge : D )
2. Maybe stock rom passes safety net and it's nothing to really think about as an user. Because if everything works like you want -> no reason to care. If doesn't work -> now you care and you can find answer since you have something to look for
3. Root isn't actually thing you can loose. It's thing that you just install in the rom. As user you can think it like an app.(which just has to be installed a bit differently).
4. When you press SuperSu, Supersu app should open (maybe your copying broke it)
5. TWRP is to back up whole rom(or some partitions). Like if you "soft brick" your device or format system/boot/data partition you can restore it back exactly like it was with TWRP backup. You should do this every time you install new rom or some stuff that modifies system like xposed. It saves time and nerves if things don't work.
5.1 Titanium back up is to back up app and/or app data(like progress in games). This is good if you are changing rom or wanting to re-install your current rom.
6. You'll soon understand the actual concept of the root. Like with p8lite only thing you need to worry is that you have unlocked bootloader. Which you should have since you were able to install TWRP.
7. About installing firmware in TWRP is kind of easier, because stock method will need non-rooted firmware and only few exactly correct firmwares can be installed on top of your current firmware. With TWRP you can even install roms from other kirin 620 devices. (My phone is honor 4x, but I used to use p8lites firmwares because it had more updates) TWRP updating will wipe data.
Happy to help. I think I answered most of your questions in that, ask if you need better details. It would be hard to write guide that has all basics explained the way it would be easy to understand, you'll learn faster when you keep trying and ask question as they come(like you have) at some point you will do something wrong and be like **** this **** and start over again. Then it will became easier and you will also learn that it's difficult to actually brick this phone(some people are too scared about it and few have succeeded in it, but no idea how : D) )
Thanks for using actual english in your questions. :good:
Click to expand...
Click to collapse
Thank you very much for helping and letting me feel at ease with that last bit! Buttuhm if I used Dutch I dont think I would get very much help here, but thanks for thanking me (My English is not so good though)
Sorry for the late responce. Ive been busy ... also with reading and searching ... but seems like the more I read the more questions I get.
Anyways:
1. In the tutorial I finally tried it said in the end "7. Now open /device/data/app and locate folder eu.chainfire.supersu-1 cut and paste in folder /device/system/app with following rights rwx r-x r-x" and it worked. (Im not sure weither I may post the link of that tutorial here. Its some blogspot.)
2. Mobile banking doesnt work anymore. It sais it doesnt recognize my device ... so If its not to hard to switch to Magisk, I would like that.
3. But I cannot just uninstall SuperSu and install Magisk now can I? (Im trying to figure that out, among all the other stuff new to me.)
4. Lol ye I have been a bit of an idiot there or drunk or something, cause it works just fine.
5. Ok so it makes an images of your whole device so to speak, right? But I guess TWRP will be gone after a official update or a stock ROM is installed? When I make a back up with TWPR it names it date Balong500311 or something. I had the Balong bug several days ago but its gone now ... I hope. In aida64 it sais Board: Balongv8r1sft and in project menu it sais CP version: some number (balong) ... its very strange.
5.1 So TWRP is better it backs up everything.
6. Ok, but I wanna know .. Everything!!!! :victory:
7. I dont understand your first sentence here at all. (Remember im realy realy new to this. For to new to be going installing ROMs from other devices )
amageek said:
By default, SuperSu installs root in system mode. It will fail the SafetyNet test (which checks if the android system is modified or not if it fails, you can't run SnapChat and Android Pay will not work too). If you root by Magisk, the SafetyNet test will pass..
To make it clear, since you have TWRP, download the Root file (SuperSu or Magisk) and then flash the root file from TWRP... Copying and pasting won't work.
These are the files: SuperSu v 2.78 and Magisk v 13.3.. Download either of these files and flash through TWRP..
And yes, I meant you can root...
---------- Post added at 01:08 ---------- Previous post was at 01:04 ----------
To answer your other question, when you update your phone it will unroot it... You can root it again by simply flashing those files...
Do Refer the MEGA Thread for more information... Banakafallata has explained everything neatly...
Click to expand...
Click to collapse
Yes thank you. But I finally rooted it after a bunch of trouble. Softbricks, balong bug, all kinds of errors and issues. And I was finally able to root it in a very strange way ... and almost accidentally. And not with the newest TWRP (does that matter?) nor the newest SuperSu. When I flashed the newest SuperSu in not the newest TWRP it got softbricked.
So Im a bit ... uhm more cautious now hoping it will all go more smoothly from now on.
I will search Banakafallata's thread.
Oh by the way. You have B610 right? Do you still have the local update function in the menu of updater?
TommyWhite said:
Yes thank you. But I finally rooted it after a bunch of trouble. Softbricks, balong bug, all kinds of errors and issues. And I was finally able to root it in a very strange way ... and almost accidentally. And not with the newest TWRP (does that matter?) nor the newest SuperSu. When I flashed the newest SuperSu in not the newest TWRP it got softbricked.
So Im a bit ... uhm more cautious now hoping it will all go more smoothly from now on.
I will search Banakafallata's thread.
Oh by the way. You have B610 right? Do you still have the local update function in the menu of updater?
Click to expand...
Click to collapse
Great to know that you've rooted, though by some weird way... It doesn't matter much, the difference between older and newer SuperSU is very less... But for TWRP, newer lets you flash stock update.zip whereas older doesn't...
https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
Do read this
amageek said:
Great to know that you've rooted, though by some weird way... It doesn't matter much, the difference between older and newer SuperSU is very less... But for TWRP, newer lets you flash stock update.zip whereas older doesn't...
https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
Do read this
Click to expand...
Click to collapse
Ok that will not unroot my device right? Ill do that tommorow, its very late here in Holland ... 3:40 am???
Do you still have the local update function in the menu of updater in B10 (your device)? Id like to know ver much pls.
Thanks in advance!
TommyWhite said:
Ok that will not unroot my device right? Ill do that tommorow, its very late here in Holland ... 3:40 am???
Do you still have the local update function in the menu of updater in B10 (your device)? Id like to know ver much pls.
Thanks in advance!
Click to expand...
Click to collapse
No, the local update option is not there from Marshmallow onwards. But you can flash a zip for it too... Yes, updating your device to newer build (updates) will unroot your device... But you can root it again
TommyWhite said:
Thank you very much for helping and letting me feel at ease with that last bit! Buttuhm if I used Dutch I dont think I would get very much help here, but thanks for thanking me (My English is not so good though)
Sorry for the late responce. Ive been busy ... also with reading and searching ... but seems like the more I read the more questions I get.
Anyways:
1. In the tutorial I finally tried it said in the end "7. Now open /device/data/app and locate folder eu.chainfire.supersu-1 cut and paste in folder /device/system/app with following rights rwx r-x r-x" and it worked. (Im not sure weither I may post the link of that tutorial here. Its some blogspot.)
2. Mobile banking doesnt work anymore. It sais it doesnt recognize my device ... so If its not to hard to switch to Magisk, I would like that.
3. But I cannot just uninstall SuperSu and install Magisk now can I? (Im trying to figure that out, among all the other stuff new to me.)
4. Lol ye I have been a bit of an idiot there or drunk or something, cause it works just fine.
5. Ok so it makes an images of your whole device so to speak, right? But I guess TWRP will be gone after a official update or a stock ROM is installed? When I make a back up with TWPR it names it date Balong500311 or something. I had the Balong bug several days ago but its gone now ... I hope. In aida64 it sais Board: Balongv8r1sft and in project menu it sais CP version: some number (balong) ... its very strange.
5.1 So TWRP is better it backs up everything.
6. Ok, but I wanna know .. Everything!!!! :victory:
7. I dont understand your first sentence here at all. (Remember im realy realy new to this. For to new to be going installing ROMs from other devices )
Click to expand...
Click to collapse
1. Oh, I just realized that that copy was to make superSU a system app instead of user app. (This only affects superSU app, not other stuff it installs) If you install SuperSU in system mode it will cause bootloop.
2. I guess you can try use superSu uninstaller or try to uninstall from superSU app. Then just go magisk thread and download latest stable magisk and install it in TWRP. You can take backup of boot partition if you want so it will be easy to fix if you get bootloop.
5(I guess). Yes, you're right.
You can always get to bootloader mode and just flash TWRP again. I'm not sure is there any reason to care about balong "bug". I guess it might prevent updating with stock method and maybe some cust partition related stuff but I know almost nothing about that.
5.1 If you want to change rom and it's sometimes good to do facotry reset before installing new rom. In this case you need titanium backup to have app progress saved.
6. All I know about rooting is that you install magisk or superSU and then use it(so can't help with anything deeper) : D
7.I'll try again, but shorter
Normal update method only allows you to update on an unmodified firmware(Non-rooted) and it does kind of strict version checking.
If you are ok with doing factory reset before installing you can download update with/from "firmware finder"(can be found somewhere from this devices forum and probably also from honor 4x and 4c forums) to install update in TWRP(zip files from firmware finder have update-script in them. Official site updates doesn't have it.) This way there is no version checking. If you are doing this remember to reboot recovery when installation is done(it will go to stock recovery) and to factory reset. Then you can flash TWRP and do rooting stuff.
I wrote this a bit tired, so I hope the words are in order which they might make some sense.
amageek said:
No, the local update option is not there from Marshmallow onwards. But you can flash a zip for it too... Yes, updating your device to newer build (updates) will unroot your device... But you can root it again
Click to expand...
Click to collapse
Ok. But I tried local update by pressing vol up + vol down and powerbutton and it tried to update but failed.
Now I'm glad it failed coz it would have unrooted my phone as I understand.
Did it fail coz the phone is rooted? Or is that pherhaps because of what keikari said: "only few exactly correct firmwares can be installed on top of your current firmware"? That I cant update from B09 to B10.
keikari said:
1. Oh, I just realized that that copy was to make superSU a system app instead of user app. (This only affects superSU app, not other stuff it installs) If you install SuperSU in system mode it will cause bootloop.
2. I guess you can try use superSu uninstaller or try to uninstall from superSU app. Then just go magisk thread and download latest stable magisk and install it in TWRP. You can take backup of boot partition if you want so it will be easy to fix if you get bootloop.
5(I guess). Yes, you're right.
You can always get to bootloader mode and just flash TWRP again. I'm not sure is there any reason to care about balong "bug". I guess it might prevent updating with stock method and maybe some cust partition related stuff but I know almost nothing about that.
5.1 If you want to change rom and it's sometimes good to do facotry reset before installing new rom. In this case you need titanium backup to have app progress saved.
6. All I know about rooting is that you install magisk or superSU and then use it(so can't help with anything deeper) : D
7.I'll try again, but shorter
Normal update method only allows you to update on an unmodified firmware(Non-rooted) and it does kind of strict version checking.
If you are ok with doing factory reset before installing you can download update with/from "firmware finder"(can be found somewhere from this devices forum and probably also from honor 4x and 4c forums) to install update in TWRP(zip files from firmware finder have update-script in them. Official site updates doesn't have it.) This way there is no version checking. If you are doing this remember to reboot recovery when installation is done(it will go to stock recovery) and to factory reset. Then you can flash TWRP and do rooting stuff.
I wrote this a bit tired, so I hope the words are in order which they might make some sense.
Click to expand...
Click to collapse
Thanks again, I copied some bits to remember. I hope you were not tired of me not understanding things. You said I should just ask so here I go again
I understand most of what you wrote but:
TWPR can make a back up/an image of the device, right? But that image doesnt include apps and app data (or data at all?)? And Titanium doesnt back up firmware I guess.
So how do I make a backup of everything (except of the hardware) then?
Also Im in a dilemma about updating TWPR, because you said it will whipe data (what data actually?) and amageek said I need new TWPR for stock updates. So I need the "backup of everything first" I guess ... what to do? I have TWPR 3.0.2 now by the way.
Also cant I just download Magisk from Google Play now that my phone is rooted ... or is that being stupid?
7: Its strange, coz I remember I had my phone rooted (with the help of some old tutorial they should remove imo) but accidentally downgraded my phone with it to lollipop (one of the many failures I encountered ). But just with local updates B052 to B132 to B170 back to some 2KB B132 to marshmallow B609 ... something like that ... it was unrooted again.
Anyway, by update script you mean a script only TWPR can read?
And therefor TWPR does not check the version allready installed?
Is that correct?
But after this you say: "If you are doing this remember to reboot recovery when installation is done (it will go to stock recovery) and to factory reset.
Then you can flash TWRP and do rooting stuff."
I dont get that, coz that means you have to start all over again ... or do I miss something?
Im sorry, im doing the best I can.
TommyWhite said:
Ok. But I tried local update by pressing vol up + vol down and powerbutton and it tried to update but failed.
Now I'm glad it failed coz it would have unrooted my phone as I understand.
Did it fail coz the phone is rooted? Or is that pherhaps because of what keikari said: "only few exactly correct firmwares can be installed on top of your current firmware"? That I cant update from B09 to B10.
Click to expand...
Click to collapse
Do you have have stock recovery or TWRP recovery? If you have TWRP recovery then fish stock recovery and then try updating again...
Related
I wanted to install Xposed on my Samsung Galaxy Note 4 SM-910C Version 6.0.1
So through a lot of "googling" i found a way to root my phone with Chainfire through Odin Flashing, which worked (Root Checker confirmed it so i guess it worked)
After a few more google searches i managed to flash TWRP Recovery through Odin which also worked.
Here's where i went a bit off instructions: After TWRP i went on to attempt installing Xposed Firmware on to my phone. I downloaded An Xposed APK from the instruction website i was reading but it also required i download another Xposed file which i went on to install through TWRP recovery. This particular File i donwloaded from another source since the one on the instruction site's mirror was broken, it was Armv7 and it matched what my phone's hardware required.
After installing this Xposed file on TWRP i went on to reboot my phone but before this TWRP told me that root access wasn't installed and prompted me to install SuperSU, this really confused me since Root checker said that i already had Super User turned On. I don't know why but i actually agreed to it and installed it AGAIN.
My phone rebooted until the animated Samsung Logo came on and it never moved past that for about an hour.
Right now all i can do is pull my battery out and boot recovery, i tried factory resetting my phone and wiping everything. now what happens is TWRP keeps on prompting me to install SuperSU and now it doesn't even reach the animated Samsung logo it always gets stuck on the [Samsung GALAXY Note 4].
I'm sorry if i posted this text wall but i thought these details might help, can anyone help me?
Edit: Sorry for the title don't know how to change it, fyi i wanted to change that to "Messed up trying to install Xposed Framework"
SpoonOjiisan said:
I wanted to install Xposed on my Samsung Galaxy Note 4 SM-910C Version 6.0.1
So through a lot of "googling" i found a way to root my phone with Chainfire through Odin Flashing, which worked (Root Checker confirmed it so i guess it worked)
After a few more google searches i managed to flash TWRP Recovery through Odin which also worked.
Here's where i went a bit off instructions: After TWRP i went on to attempt installing Xposed Firmware on to my phone. I downloaded An Xposed APK from the instruction website i was reading but it also required i download another Xposed file which i went on to install through TWRP recovery. This particular File i donwloaded from another source since the one on the instruction site's mirror was broken, it was Armv7 and it matched what my phone's hardware required.
After installing this Xposed file on TWRP i went on to reboot my phone but before this TWRP told me that root access wasn't installed and prompted me to install SuperSU, this really confused me since Root checker said that i already had Super User turned On. I don't know why but i actually agreed to it and installed it AGAIN.
My phone rebooted until the animated Samsung Logo came on and it never moved past that for about an hour.
Right now all i can do is pull my battery out and boot recovery, i tried factory resetting my phone and wiping everything. now what happens is TWRP keeps on prompting me to install SuperSU and now it doesn't even reach the animated Samsung logo it always gets stuck on the [Samsung GALAXY Note 4].
I'm sorry if i posted this text wall but i thought these details might help, can anyone help me?
Edit: Sorry for the title don't know how to change it, fyi i wanted to change that to "Messed up trying to install Xposed Framework"
Click to expand...
Click to collapse
Since you have twrp, find supersu.zip and save into sdcard. Flash supersu.zip to gain root access. And for xposed. Make sure it is arm-sdk23.
Sent from my SM-G925F
Rosli59564 said:
Since you have twrp, find supersu.zip and save into sdcard. Flash supersu.zip to gain root access. And for xposed. Make sure it is arm-sdk23.
Sent from my SM-G925F
Click to expand...
Click to collapse
Did a quick google search do these work?
download.chainfire.eu/696/supersu/
androidsage.com/2016/04/06/how-to-install-xposed-framework-on-marshmallow-update-with-xposed-v81/
and btw how exactly do i save this into my sd card, i can't get past the product logo.
also thanks a lot for replying man
edit: oh wait if you mean put the zips into an external sd card imma try that now. thx
Hi,
You have to use custom built version of xposed if you use stock or any touchwiz-based-rom(other versions cause bootloops). Just google 'xposed custom build by wanam'. Hope that helps.
Just wanted to clear some stuff up, if i am able to flash supersu.zip and a custom built xposed framework, will my phone stop getting stuck on the product logo?
Because being unable to use my phone normally is my top priority right now. The root and getting xpose3d installed is secondary. I really can't get through the product logo, i hope someone can shed some light on this.
but still, i really appreciate your replies.
SpoonOjiisan said:
Just wanted to clear some stuff up, if i am able to flash supersu.zip and a custom built xposed framework, will my phone stop getting stuck on the product logo?
Because being unable to use my phone normally is my top priority right now. The root and getting xpose3d installed is secondary. I really can't get through the product logo, i hope someone can shed some light on this.
but still, i really appreciate your replies.
Click to expand...
Click to collapse
I strongly believe you flashed wrong xposed zip. There is no arm7 zip by wanam. Hence find arm-sdk23. I think the last 1 is v81.
Supersu is just to give you root access. I won't causing phone to stuck at boot logo. Or do you mean splash screen showing 'samsung galaxy note 4'?
Sent from my SM-G925F
I honestly don't know if that will solve the problem, but you can try it. If it doesn't work, try flashing a rom via recovery or stock rom via odin. Since your data is already gone, I would suggest you wiping your phone completely and flashing a custom rom(I have a SM-N910C as well and I use erobot). Before doing anything, do a full backup in recovery, just in case.
Edit: If you wiped everything in recovery, including /system, that is probably the reason why your phone is stuck. Flash a rom and yo should be good.
Yeah that one exactly, splash screen showing note 4.
so based on what you guys said i should first flash a ROM so it works normally and then i can attempt for Supersu and Xposed arm-sdk23? was watching this random video you think i might have somehow wiped my touchwiz OS? was fiddling around in the Recovery trying to solve it you think i might have done that?
Since you have the same phone and you are using erobot i might go for that same ROM just to be on the safe side, i don't want to try something random.
So first try flashing custom ROM >> SuperSU >> Xposed
That's what i'm going for (i might need confirmation haha kinda scared now, i think i almost bricked my phone)
I believe your phone has to be rooted before you can install a custom rom. I can't tell if your is, but I would do the following:
Make a full backup in twrp>flash supersu again just to make sure the phone has root access>flash a custom rom.zip from your SD card>boot the custom rom, if everything works, flash xposed CUSTOM BUILD(!) and install the xposed installer.apk
I am not a pro, so wait for someone to confirm what I have written. I suggest you to use erobot as your custom rom because of the user-friendly aroma installer. Erobot is prerooted if you choose custom kernel in aroma installer, so keep in mind not to choose stock kernel.
Hope it helped
SuperSU >> Erobot >> Xposed
Ok got it, its currently 23:36 here in the Philippines guess i'm going to sleep, i'm doin that stuff tomorrow confirmation or not.
I can't really afford to throw this phone and it was a gift. So you guys have no idea how much i appreciate your help. /downslash/ Rosli thanks a bunch guys. goodnight
Hi there.. dont worry about the su not install button.. its common as i've aslo rooted my phone through chainfire an it does show me too. Click on do not install..an yeah you have flashed wrong xposed that bricked your phone.. did you backed up your phone before flashing xposed framework? If so try to restore..if not try to get in downloading mod an flash the official framework through odin.. try visiting sammobile.com there tou will get the official framework.. before flashing read ann the instruction or take a look to video tutorial on youtube about how to unbrick phone.. this might help you all the best
Hey guys, first of all sorry about my english, im french.
So my problem is: I tried rooting my Axon 7 A2017U many times, with different guides. I always end up with a softbricked phone, having to restore to stock using MiFlash.
My bootloader is unlocked, i have stock recovery and stock rom for now.
Whenever i flash TWRP, either the signed one (from @tenfar) or unsigned (and up to date) ones, i can't go past the menu saying something like "your phone cant be checked for corruption, please lock your phone [...]" it just freeze. i did read somewhere that i should flash chainfire's root or a special .zip that, i guess, disabled some check that could prevent booting a phone with unsigned stuff/edited system (after flashing TWRP, so it could boot) that didn't work out. i think i found that information in some LineageOS thread here on XDA.
My ultimate goal would be to get a rooted stock nougat 7.1.1, up to date TWRP recovery and to be able to switch to LineageOS to try it out soon.
For what it is worth, i rooted many phones over the years, so while i'm no expert, i should be able to follow most of the steps you give me.
Thanks alot!
What version of TWRP did you flash first?
I have the same root problem i can not install in twrp install in twrp ok but su application displays no root cause i have latest twrp
KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one
KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one
Okay. Download and flash this one alone via fastboot and see what happens. This is one the I personally use. It is required for any of the newer versions to work properly.
twrp-3.0.2-2-a2017u.img
You can choose to rename it to just recovery.img, then:
1. fastboot flash recovery recovery.img
or
2.
if you choose to work with the same filename:
fastboot flash recovery twrp-3.0.2-2-a2017u.img
Select reboot to recovery from the bootloader menu now and try again.
Either way, should work fine. I know you mentioned you knew the basics, but just want to be sure.
Also forgot to mention. If TWRP works but you still can't get your phone to boot, you need to follow this guide here
You can start from the part that says:
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N)
-----------------------------------------------------
Again, that's the ROM I personally use if I want to go back to stock, not the one from the ZTE site.
Gonna try it and give feedback. thanks for taking time to help!
edit: im downloading the rom from the link you shared.
like you said, i can get TWRP to boot but not the phone.
So if i use full stock from ZTE, it can't boot with modified recovery?
edit 2: i don't know what worked, i think it might be the bootstack. or the rom by DrakenFX. now i can boot to the rom with a TWRP recovery installed. It worked, but i soft bricked again trying to flash SuperSU. So now i'm retrying with an updated TWRP.
I haven't tried that yet, but I really suspect that's the reason you're having problems. I rarely use pure stock ROMs. Like you, I'm not an expert in Android Development so I can't tell you why. Just been a flashaholic for years so made a few observations.
Which supersu are you installing? If you're swiping to the right in twrp, you need to install the dm-verity zip or supersu 2.79. There's some issues with newer builds.
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable
Click to expand...
Click to collapse
Glad you're up and running root. :good:
lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
Click to expand...
Click to collapse
Yeah, like I mentioned before that was the base TWRP you needed to flash first, before any of the newer ones. You weren't intended to use it indefinitely.
There's a lot of Dev love for our device now and support is growing ... exciting new ROMs cropping up. Don't hesitate to try them out.
From the forum I followed these step to install magisk:
- Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot
- After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally
- After booting up installed Magisk Manager and both Magisk and Magisk manager shows green tick (installed)
But at this stage, whenever I open Magisk, it shows a recommendation to install a ZIP, if I agree to install it, phone gets stuck in recovery again.
If I choose not to install recommended zip and click Install > Direct Install, phone gets stuck in recovery again anyway
Everytime it gets stuck I have to wipe all data and start all over again. Anyone else facing same issue? Any solution?
Really frustrated right now.
My current rom is : DAVINCIIN INDIAN Global_V11.0.2.0
Used latest magisk manager 7.4.0
I have official recovery, not TWRP.
Afraid that flashing TWRP now will brick it for good.
UPDATE: Got the solution here, thanks @pikchu289 !
Twrp up to now is the best way
But check some stuff first
1.unlock the boot loader
2.chech if the magisk zip/img is corrupted or any file
3.does your os support this magisk version
Any way you can flash twrp because many people had already tried it and tested it from installing zips/ROMs/mods etc.. to backup files/data or even fixing some corrupted files that caused boot loops manually
But there are various things that doesn't work usually such as restoring system partition but never worry about this because if any thing failed just use miflash tool to go back to official/stock rom
Edit : I think something's wrong with your magisk version number
I have no idea which rom youre using or why on earth you didn't install TWRP before messing around with the os but some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch
Solve this solution
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
pikchu289 said:
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
Finally someone with an answer!
Thanks... Will try and see if it works...
UPDATE: IT WORKED!
Aserar said:
I have no idea which rom youre using
Click to expand...
Click to collapse
Maybe I should've used font size 72 while writing the rom I'm using above.
Aserar said:
why on earth you didn't install TWRP before messing around with the os
Click to expand...
Click to collapse
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
Aserar said:
some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch
Click to expand...
Click to collapse
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-
It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
stone_henge said:
Maybe I should've used font size 72 while writing the rom I'm using above.
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-
Click to expand...
Click to collapse
Aserar said:
It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
Click to expand...
Click to collapse
Sorry for being harsh... I understand you actually tried to help. It's actually really frustrating when facing a problem that has no straightforward solution.
Sorry mate.
finally i founded how to fix this issue without formating data of ur device
--just the flash the same the full custom rom or stock rom that u r using currently on . and boom restart. and ur issue fixed
Install a magisk zip without TWRP. TWRP takes too long. Instead use Aodin to flash a rom specific to your device version. Make sure it is not corrupted as well
Hey guys,
first time posting here so i dont kow how to style the text, so sorry about that.
last time i rooted a phone was on my sony xperia sp , where all i had to do was to go to towelroot .com and click to root.
I tryed to root my OP6T yesterday, after some setbacks i managed to sucessfully do it.
I did it like this:
1. Downloaded full ROM of OOS 10.3.2,
2. copied the payload to a program called payload dumper that extracted the boot image.
3. Copied the boot image to the phone
4. opened Magisk manager and selected install from source where i chose the boot.img
5. it created a copy called magisk_patched.img
6. booted in fastboot
7. on my pc used the command prompt to "fastboot boot magisk_patched.img"
booted normally and i had root.
but then problem appeared
#Problem 1
everytime i rebooted my phone i would loose root and it would say Magisk not installed. To get it back i would need to perform step 7 again and it was not ideal to do that everytime i turned off my phone.
#Problem 2
While tryng to solve problem 1 i read that i needed to open magisk manager and "Install to Inactive Slot (After OTA)."
After doing that it rebooted but now it wont boot at all, even if i try to "fastboot boot magisk_patched.img" the cmd gives me error:
fastboot boot magisk_patched.img
downloading 'boot.img'...
OKAY [ 0.838s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.845s
now my phone is just sitting there i dont want to reset it again. it would be the 4th time that i need to set up my phone in 2 days, so im trying to see if there are alternatives.
If reset is really the only way, i read that with root you can make a full backup of your phone and then restore it. How to do that? can i do it in the situation im in?
How can i root my OP6T running OOS10.3.2, and keep it? Whats the right method bc the one i followed seemed flawed.
I also tried one that had TWRP but maybe i did something wrong bc it didnt work., also there is no official one working for 10.3.2.
What is happening is normal with those instructions (they aren't right).
All you need to do is install TWRP. Do not use the official one, it is out of date. Use TWRP from this thread Link here. The TWRP from that thread is from the official maintainer. It works fine with OOS 10.
- You need to get the phone in fully working order again. Which may mean you need to use the fastboot ROM, as you've probably "goofed" something up at this point. (no offense meant). Make sure your phone boots and such after this.
- For OOS 10 with the phone in fastboot, fastboot boot recoveryimgfilename.img (<-- For OOS 10 you will need TWRP 3.3.1-32 Q Unofficial by mauronofrio from the thread I linked to above) This will boot to TWRP.
- Now run TWRP 3.3.1-32 Unofficial Installer by mauronofrio this will install TWRP. The installer is the same for Android 9 and 10, doesn't matter.
- Once the installer runs, click back, choose reboot to recovery. If you boot to the system, you have to start over. Reboot to recovery!
- Install Magisk 20.3 <-- The current version. The official download page. After that you can reboot to the system. You should now have a rooted, phone with Magisk, and TWRP installed.
Any questions ask.
OhioYJ said:
What is happening is normal with those instructions (they aren't right).
All you need to do is install TWRP. Do not use the official one, it is out of date. Use TWRP from this thread Link here. The TWRP from that thread is from the official maintainer. It works fine with OOS 10.
- You need to get the phone in fully working order again. Which may mean you need to use the fastboot ROM, as you've probably "goofed" something up at this point. (no offense meant). Make sure your phone boots and such after this.
- For OOS 10 with the phone in fastboot, fastboot boot recoveryimgfilename.img (<-- For OOS 10 you will need TWRP 3.3.1-32 Q Unofficial by mauronofrio from the thread I linked to above) This will boot to TWRP.
- Now run TWRP 3.3.1-32 Unofficial Installer by mauronofrio this will install TWRP. The installer is the same for Android 9 and 10, doesn't matter.
- Once the installer runs, click back, choose reboot to recovery. If you boot to the system, you have to start over. Reboot to recovery!
- Install Magisk 20.3 <-- The current version. The official download page. After that you can reboot to the system. You should now have a rooted, phone with Magisk, and TWRP installed.
Any questions ask.
Click to expand...
Click to collapse
So getting it straight, i need to first reset my phone and then do the steps you described.
Can i backup the data first with TWRP to restore it later and avoid setting up everything again?
Davide1713 said:
So getting it straight, i need to first reset my phone and then do the steps you described.
Can i backup the data first with TWRP to restore it later and avoid setting up everything again?
Click to expand...
Click to collapse
Supposedly. I've never used that function of TWRP. Some people have luck with, some people restore things that shouldn't be restored and end up having to wipe the phone again. Personally I just use TitaniumBackup like I always have. I would search for information on that in the TWRP thread if you want to try method. I don't know enough on that to provide solid information.
OhioYJ said:
Supposedly. I've never used that function of TWRP. Some people have luck with, some people restore things that shouldn't be restored and end up having to wipe the phone again. Personally I just use TitaniumBackup like I always have. I would search for information on that in the TWRP thread if you want to try method. I don't know enough on that to provide solid information.
Click to expand...
Click to collapse
Hey man,
Thank you so much. It worked and i stay rooted even after reboot.
May i ask how you use the Titanium Backup, i think back in the days all i used it for was uninstalling system apps. Or if you know some nice guides. If you know other good things to checkout now that i have root i would appreciate it, i have been far away from rooting for too long.
Once again thank you so much
Davide1713 said:
Hey man,
Thank you so much. It worked and i stay rooted even after reboot.
May i ask how you use the Titanium Backup, i think back in the days all i used it for was uninstalling system apps. Or if you know some nice guides. If you know other good things to checkout now that i have root i would appreciate it, i have been far away from rooting for too long.
Click to expand...
Click to collapse
I use it to back up app and app data primarily. It allows me to restore data to apps after a clean install. Since I have the Pro version it's just a batch action (one click essentially). There is also a way to create a flashable .zip you can use in TWRP, although I haven't tried that method, as I'm typically not restoring apps, just data. I also use it remove apps from time to time.
OhioYJ said:
I use it to back up app and app data primarily. It allows me to restore data to apps after a clean install. Since I have the Pro version it's just a batch action (one click essentially). There is also a way to create a flashable .zip you can use in TWRP, although I haven't tried that method, as I'm typically not restoring apps, just data. I also use it remove apps from time to time.
Click to expand...
Click to collapse
Hey man, im sorry i am once again in need.
Idk why but at first i can reboot the system normally without issues. but after a while once i set up everything it just doesnt boot anymore. Am i missing something? do i have to do anything with magisk? download a module or something?
Could it be that google security update is the fault?
Davide1713 said:
Hey man, im sorry i am once again in need.
Idk why but at first i can reboot the system normally without issues. but after a while once i set up everything it just doesnt boot anymore. Am i missing something? do i have to do anything with magisk? download a module or something?
Could it be that google security update is the fault?
Click to expand...
Click to collapse
When you installed everything originally did you fix everything with a clean install? Both slots are the same version of Android? (Like you don't have something weird going on like Android 9 on one and Android 10 on another?)
You definitely have something abnormal going on. There shouldn't be anything in Magisk that you have to do, at least not to prevent crashing. I normally hide it, but that has to do with keeping apps from detecting root.
OhioYJ said:
When you installed everything originally did you fix everything with a clean install? Both slots are the same version of Android? (Like you don't have something weird going on like Android 9 on one and Android 10 on another?)
You definitely have something abnormal going on. There shouldn't be anything in Magisk that you have to do, at least not to prevent crashing. I normally hide it, but that has to do with keeping apps from detecting root.
Click to expand...
Click to collapse
I got it to boot by uninstalling magisk,
I am 100% sure i dont have two different version of android in different slots, bc yesterday i was in big trouble and nothing was working and i flashed on both slots the same version of android 10(dont remember exactly wich one as i tried a couple, but they were the same).
Today when i couldnt boot anymore i went into stock recovery, factory reset -> when it booted i placed the stockOS.zip file in the phone and applied update from local file -> after that i factory reset again from the system settings, so i think the phone should have installed it properly.
Only after that i did what you told me and installed TWRP and Magisk. and as i said it worked and i could restart my device etc..
After a while when i restarted i couldnt boot anymore and went to bootloader. Removing Magisk fixed it,apperantly on install magisk creates a copy of the boot.img that it restores on uninstall, and i booted to system.
Now i can use my phone but dont have root.
Im very thankful for you being there and helping me out trough this, i cant thank you enough
GuestD2272 said:
I got it to boot by uninstalling magisk,
I am 100% sure i dont have two different version of android in different slots, bc yesterday i was in big trouble and nothing was working and i flashed on both slots the same version of android 10(dont remember exactly wich one as i tried a couple, but they were the same).
Today when i couldnt boot anymore i went into stock recovery, factory reset -> when it booted i placed the stockOS.zip file in the phone and applied update from local file -> after that i factory reset again from the system settings, so i think the phone should have installed it properly.
Only after that i did what you told me and installed TWRP and Magisk. and as i said it worked and i could restart my device etc..
After a while when i restarted i couldnt boot anymore and went to bootloader. Removing Magisk fixed it,apperantly on install magisk creates a copy of the boot.img that it restores on uninstall, and i booted to system.
Now i can use my phone but dont have root.
Im very thankful for you being there and helping me out trough this, i cant thank you enough
Click to expand...
Click to collapse
Not sure if you're still having this issue but I'll post the solution just in case anyone gets stumped, does a google search, and comes across this post. You were using the wrong command.
"fastboot boot" just lets you boot with the img so you can verify that root works.
"fastboot FLASH boot" will flash it and root will stick after reboot.
No need to jump through hoops with TWRP and such.
Hi everyone. I'm new here on XDA and this is my first post so if I'm doing this wrong, please let me know below or provide a link if my problem has already been solved, thank you.
I have an s8+(SM-G955F, dream2ltexx/dream2lte), running 9.0.0. I have both, TWRP(3.3.1) and Magisk(latest) + edxposed(for what is worth). I am also running a custom kernel A2N. I received a week ago an OTA update and I would like to apply it. This is my first ever OTA update on a rooted device so I read a ton of posts and tutorials in the past few days, also backed up everything using TWRP. From what I understood(and please feel free to correct me if I'm wrong or show a better solution) I need to first install the default recovery image, lose TWRP, unroot, do the OTA and after that, reinstall TWRP and Magisk(I think I also need to return to stock kernel, not sure).
Important: I would very much like to not factory reset my phone if this is possible.
Now, I have a few questions:
1. Where can I get my default recovery.img ? (I tried to find it on https://desktop.firmware.mobi/device:468 but they don't have anything for android 9)
2. Do I also need to get and install my default kernel ? If so, where can I also get it ?
2. After I flash the recovery.img what is the best thing to do with Magisk ? (completly uninstall or just restore image ?)
3. After everything is done, will flashing TWRP require to remount the partitions ?(because that will also mean I have to factory reset at some point)
4. It would also be super helpful if you could provide me a link from where I can download OTA updates as zip files(if there exist such a place). The version that I need is: G955FXXS8DTC1
I cannot thank you enough for everything and sorry for the long post
Hope you have a safe, beautiful day !
P.S. I already tried to do the OTA update after backup. It tried to flash it throw TWRP and, of course, it failed(error: 7)