Related
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.
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...
Hello y'all,
I've noticed that on the Pixel 2 and on many other A/B devices, there is a twrp zip available that can be flashed after flashing the twrp image to boot and booting into recovery and flashing the stock boot image (like we do on the Essential) which patches the ramdisk in the stock boot.img to add twrp to it so that twrp can be permanently installed on the device.
If I could make something like this myself, I would have a long time ago, but unfortunately, it's over my head. Just curious why something like this has never been made for the Essential. Also, but much less important, TWRP 3.2.3-0 is about to be released (code is on GitHub), yet the latest available to us is version 3.2.1-1.
I know one of you smart devs could make the zip to install twrp to the ramdisk (and possibly build the latest version of twrp also) probably in almost no time at all. I love my Essential, but having to connect it to a PC just to get into TWRP is very irritating.
When one of you guys have the time, could you give it a try? I'd be happy to test whatever you come up with.
Much thanks!
starcms said:
Hello y'all,
I've noticed that on the Pixel 2 and on many other A/B devices, there is a twrp zip available that can be flashed after flashing the twrp image to boot and booting into recovery and flashing the stock boot image (like we do on the Essential) which patches the ramdisk in the stock boot.img to add twrp to it so that twrp can be permanently installed on the device.
If I could make something like this myself, I would have a long time ago, but unfortunately, it's over my head. Just curious why something like this has never been made for the Essential. Also, but much less important, TWRP 3.2.3-0 is about to be released (code is on GitHub), yet the latest available to us is version 3.2.1-1.
I know one of you smart devs could make the zip to install twrp to the ramdisk (and possibly build the latest version of twrp also) probably in almost no time at all. I love my Essential, but having to connect it to a PC just to get into TWRP is very irritating.
When one of you guys have the time, could you give it a try? I'd be happy to test whatever you come up with.
Much thanks!
Click to expand...
Click to collapse
It's definitely possible but I don't know how many Devs would want to take this up. I'm all for the idea, I really miss having TWRP permanently, but you kinda get used to the whole PC flashing thang.
I don't know how different the Pixel 2 is in comparison to the Essential phone, but they both share A/B partitions, so it wouldn't be too outlandish if someone were able to port something like this over to our Mata's down the road.
?
starcms said:
Hello y'all,
I've noticed that on the Pixel 2 and on many other A/B devices, there is a twrp zip available that can be flashed after flashing the twrp image to boot and booting into recovery and flashing the stock boot image (like we do on the Essential) which patches the ramdisk in the stock boot.img to add twrp to it so that twrp can be permanently installed on the device.
If I could make something like this myself, I would have a long time ago, but unfortunately, it's over my head. Just curious why something like this has never been made for the Essential. Also, but much less important, TWRP 3.2.3-0 is about to be released (code is on GitHub), yet the latest available to us is version 3.2.1-1.
I know one of you smart devs could make the zip to install twrp to the ramdisk (and possibly build the latest version of twrp also) probably in almost no time at all. I love my Essential, but having to connect it to a PC just to get into TWRP is very irritating.
When one of you guys have the time, could you give it a try? I'd be happy to test whatever you come up with.
Much thanks!
Click to expand...
Click to collapse
MoistPicklez said:
It's definitely possible but I don't know how many Devs would want to take this up. I'm all for the idea, I really miss having TWRP permanently, but you kinda get used to the whole PC flashing thang.
I don't know how different the Pixel 2 is in comparison to the Essential phone, but they both share A/B partitions, so it wouldn't be too outlandish if someone were able to port something like this over to our Mata's down the road.
?
Click to expand...
Click to collapse
The problem lies in the way our touch driver is implemented. For lack of a better explanation, what good would it do to need to carry a type c mouse around to use twrp if touch doesn't work. Many many people have tried and failed getting touch to work on Oreo source, let alone P. That is why twrp resides on a nougat kernel meant for LOS. Someone I know even rewrote the driver in c, no go. It's gonna be tough sledding.
Does it have to be touch though? Could it be more old school clockworkmod recovery where you use the buttons or really like default recovery. I don't know enough about it but just a thought. You definitely get use to just downloading and flashing in twrp and it would be cool to find that with the PH-1.
Atleaset there is a way to use TWRP on the fly.
1) Root the phone the first time using the PC.
2) Copy the TWRP and boot.img(rooted) files to the Phone.
3) While booted and rooted, use apps like Rashr - Flash Tool or Flashify available on the playstore to flash TWRP and boot to it.
4) Once you are done using TWRP, flash the boot.img and boot to the phone.
Gundabolu SC said:
Atleaset there is a way to use TWRP on the fly.
1) Root the phone the first time using the PC.
2) Copy the TWRP and boot.img(rooted) files to the Phone.
3) While booted and rooted, use apps like Rashr - Flash Tool or Flashify available on the playstore to flash TWRP and boot to it.
4) Once you are done using TWRP, flash the boot.img and boot to the phone.
Click to expand...
Click to collapse
Been waiting for someone to share this for 6 months.. thanks lol
aer0zer0 said:
The problem lies in the way our touch driver is implemented. For lack of a better explanation, what good would it do to need to carry a type c mouse around to use twrp if touch doesn't work. Many many people have tried and failed getting touch to work on Oreo source, let alone P. That is why twrp resides on a nougat kernel meant for LOS. Someone I know even rewrote the driver in c, no go. It's gonna be tough sledding.
Click to expand...
Click to collapse
Thanks for the explanation. Now I understand why it hasn't been done before.
But why the issue with touch in TWRP with an Oreo kernel in the first place? What's so special/different/difficult about the touch driver that the Essential uses? And why does it work fine with TWRP with a Nougat kernel? No other devices (to my knowledge) have this issue.
Edit: I wonder if since TWRP worked with the touch driver from the Nougat kernel, if it could work with the P kernel? Maybe whatever was changed in Oreo that prevented it from working has been fixed?
starcms said:
Thanks for the explanation. Now I understand why it hasn't been done before.
But why the issue with touch in TWRP with an Oreo kernel in the first place? What's so special/different/difficult about the touch driver that the Essential uses? And why does it work fine with TWRP with a Nougat kernel? No other devices (to my knowledge) have this issue.
Click to expand...
Click to collapse
Hbtp_daemon (touchscreen) doesn't work in twrp on 8.x and newer sources.
Hbtp_daemon runs in userspace iirc, which is the problem. So an entire driver needs to be hogged together in order to get twrp to work. same process that worked on N doesn't work now.
aer0zer0 said:
Hbtp_daemon (touchscreen) doesn't work in twrp on 8.x and newer sources.
Hbtp_daemon runs in userspace iirc, which is the problem. So an entire driver needs to be hogged together in order to get twrp to work. same process that worked on N doesn't work now.
Click to expand...
Click to collapse
Not possible to use the driver in userspace after TWRP decrypts the device (userspace) using the default password (after any patterns or pins are removed from the lockscreen)?
Edit: And what the heck is the driver doing in userspace anyway? Shouldn't it be in /vendor? If the driver is in userspace, then how can the touchscreen work after a factory reset?
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
galakanokis said:
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
Click to expand...
Click to collapse
It doesn't after you lets say flash magisk and gapps they create a script in /system/addon....and when updatting lineage it runs the scripts in the addon folder which is how gapps and magisk get installed to the new updated system and boot.....first magisk and gapps have to be flashed in twrp....after that u shudnt need it on dirty flashes
galakanokis said:
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
Click to expand...
Click to collapse
@aer0zer0
This seems like the easiest solution to getting TWRP working on the Oreo and P boot images and being able to keep it permanently installed in ramdisk. Make TWRP use the volume up/down keys for scrolling and the power key to select. If the touchscreen is soooo difficult to get working, forget it. If someone really wants to use the touchscreen, they can use the existing TWRP version built on the Nougat boot image.
galakanokis said:
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
Click to expand...
Click to collapse
What can you do in Lineage recovery if you can't flash zips? Can you make backups? What else can you do? If you have it installed, could you attach a pic (assuming you have another phone/camera)?
Has anyone looked in the stock P kernel? I was poking around and noticed some twrp residual files. This was straight from the images zip from essential. I didn't touch it.Wth are they in there for? Could they have a better twrp on the back burner for kernel development purposes for Essential? It was in the ramdisk, ill look again tomorrow when I unpack the boot.img. it would make sense to have it in ramdisk, pixel 2 has it like that. Ill post screenshots after work. But, the conversation looks good folks, you are on to something. We could always bust out some phillz recovery, or clockwork mod.
starcms said:
What can you do in Lineage recovery if you can't flash zips? Can you make backups? What else can you do? If you have it installed, could you attach a pic (assuming you have another phone/camera)?
Click to expand...
Click to collapse
I would say it is more stock-ish as far as recoverys go. It's a stock LOS recovery. You can factory reset, flash or sideload update.zips or signed zips no regular custom ROM zips or magisk. It is meant to run on LOS, it only runs on LOS actually and not made for the flashaholics out there. It's a good start though.
Sorry, out right now and no other phone/camera handy.
Gundabolu SC said:
Atleaset there is a way to use TWRP on the fly.
1) Root the phone the first time using the PC.
2) Copy the TWRP and boot.img(rooted) files to the Phone.
3) While booted and rooted, use apps like Rashr - Flash Tool or Flashify available on the playstore to flash TWRP and boot to it.
4) Once you are done using TWRP, flash the boot.img and boot to the phone.
Click to expand...
Click to collapse
Just wanted to mention this works perfectly, tried it last night was able to get into TWRP and then back into my P Beta 3 with root, no issues. Thanks for this!
One could also theoretically copy a copy of the twrp boot. Img to the ex kernel manager backup file, and while booted into the system, hit restore kernel and since its in the boot partition it will flash it then reboot into recovery. Then from there flash your normal kernel and boot back to system/android.. i backup all my kernels after rooting them so after flashing otas, i can just flash my prerooted kernel and reboot without having to flash magisk
Edit. This works, i just did it, but u must make it reboot to bootloader to then tell it to reboot recovery. I dont know if flashify is the same
MoistPicklez said:
Just wanted to mention this works perfectly, tried it last night was able to get into TWRP and then back into my P Beta 3 with root, no issues. Thanks for this!
Click to expand...
Click to collapse
Hey, I'm just curious, before I try it, anyway when using flashify and selecting flash zip - does a recovery other than stock need to be present?
dirtyreturn said:
Hey, I'm just curious, before I try it, anyway when using flashify and selecting flash zip - does a recovery other than stock need to be present?
Click to expand...
Click to collapse
Not sure what you mean by that but to be honest all I did was take the TWRP11.img, and flashed it to boot (kernel) using Rashr, Flashify didn't load up oddly, then reboot to bootloader, select Recovery and bam, there was TWRP. Then to get back I just flashed my boot.img, and Magisk and all my modules and everything were all good to go. No issues at all. ?
Edit: as long as you have TWRP.img, your boot.img, and Magisk, you can easily get to TWRP and back, just make sure you have the img's you need and boom we all got TWRP on the fly.
Wish I had tried this sooner.
MoistPicklez said:
Not sure what you mean by that but to be honest all I did was take the TWRP11.img, and flashed it to boot (kernel) using Rashr, Flashify didn't load up oddly, then reboot to bootloader, select Recovery and bam, there was TWRP. Then to get back I just flashed my boot.img, and Magisk and all my modules and everything were all good to go. No issues at all. ?
Edit: as long as you have TWRP.img, your boot.img, and Magisk, you can easily get to TWRP and back, just make sure you have the img's you need and boom we all got TWRP on the fly.
Wish I had tried this sooner.
Click to expand...
Click to collapse
Hey, Rashr doesn't support this device(phone). I get a reboot to recovery option and if I tap cancel the app just closes. Did the app identify what it needed to?
In Flashify there are 3 options ,Flash - kernel,boot, and zip. What I'm curious about is , when choosing just the zip option - would twrp first need to be flashed to the boot partition?
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!
I had Magisk v23 working fine with Magisk hide but then I upgraded to v24. Magisk app successfully installed and shows Magisk not present. And when I try to DirectInstall Magisk, I get verification failed error. Attached both screenshots.
Now, I have installed and confirm TWRP is working but do not know how to make Magisk working again and it seems it gonna be a wipe. Any help appreciated.
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Step by step: Magisk 24.1 is new and as you have seen completely different.
Installation instructions: https://topjohnwu.github.io/Magisk/install.html
Issue is that on my other phone, Sony Xperia XZ Premium G8142, the same in-app upgrade weas successful with out any issues. I lost Magisk Hide but an extension recovered that function. But it all went haywire on this S8
xabu said:
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Step by step: Magisk 24.1 is new and as you have seen completely different.
Installation instructions: https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
This guide expects me to know what ROM I have. Thing is, I do not know what my device really is. It's running a ROM that I do not recognize (My post: https://forum.xda-developers.com/t/...l-and-odin-cannot-flash.4372669/post-86069051). I do not have the sources for it so I cannot acquire the required two files. Ramdisk is Yes as per my screenshot but I cannot follow the rest of the guide without the files.
try this
Check hardware and software info Galaxy:
*#12580*369#
Android 9 shows almost certainly a stockrom Pie .
xabu said:
try this
Check hardware and software info Galaxy:
*#12580*369#
Android 9 shows almost certainly a stockrom Pie .
Click to expand...
Click to collapse
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.
Your phone needs twrp and a new good custom ROM ...
HELP! S8 got bricked, can't access recovery mode and OEM is locked
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got an error where it reset my data, after data reset I was stuck at the boot screen with the logo . I've tried steps like flashing stock rom, odin...
forum.xda-developers.com
Here are certainly members of the forum with lots of expertise!
Doomer D. Great said:
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.
Click to expand...
Click to collapse
Maybe only European ?
xabu said:
Your phone needs twrp and a new good custom ROM ...
HELP! S8 got bricked, can't access recovery mode and OEM is locked
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got an error where it reset my data, after data reset I was stuck at the boot screen with the logo . I've tried steps like flashing stock rom, odin...
forum.xda-developers.com
Here are certainly members of the forum with lots of expertise!
Click to expand...
Click to collapse
I just TWRP it. It went smoothly. I love a new ROM but need to know what device is it.
Download mode say it is SM-G950N
Android say it is SM-950FD
Both SIM slots have the same IMEI number. This part is beyond my understanding.
I have Odin and know the basics. Just need to find a ROM I can go for: What official I should flash first and what custom. Any recommendation?
As soon as you make a TWRP total backup, you can see your boot.img and move a copy to your internal sd-card. There it can be picked up by Magisk and patched....Magisk will put it in your download folder on the internal sd-card ...
for the best Rom ask members with your S8 phone. I'am on the S7 Edge.
xabu said:
Maybe only European ?
Click to expand...
Click to collapse
Doomer D. Great said:
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.
Click to expand...
Click to collapse
Just found out:The "famous" secret codes only work on stock based ROMs ¯\_( ͡❛ ͜ʖ ͡❛)_/¯
xabu said:
As soon as you make a TWRP total backup, you can see your boot.img and move a copy to your internal sd-card. There it can be picked up by Magisk and patched....Magisk will put it in your download folder on the internal sd-card ...
for the best Rom ask members with your S8 phone. I'am on the S7 Edge.
Click to expand...
Click to collapse
I have been trying to make the total backup but I do not see any boot.img:
And I do not see the file in the Device/TWRP/Backups:
Again, I must be missing something obvious. And as per the Magisk guide, I need the boot.img
magisk 24 is ****, it's bricking MediaTek powered Samsung phones
Boot.img from TWRP backup
In clockworkmod kernel and recovery are backed up as IMGs. But in TWRP it is boot.emmc.win Anybody know how to convert jt to boot.img? Help will be really appereciated. Sent from my HTC One X using xda app-developers app
forum.xda-developers.com
I must tell you that my custom rom for the s7 gives me the boot.img as the first file as soon as i open the zip.
the boot.img can also be reached by downloading the right stock rom for your phone. In that case it is the best practice to patch the whole
AP file by using Magisk.