Related
Hi,
I'm a happy new owner of the redmi note 4 and I've already unlocked the bootloader.
I would like to use google camera, and eventually adblock.
I've seen there are various way to
- install bootloaders (and it seems there are also various boatloaders)
- root the phone
- enable camera2 api, with and without root
- ...
Actually I like to keep the stock rom and the phone as vanilla as possible, as I've read there are redundant issue with custom rom. I also do like the idea of being able to update the phone "normally", which seems to be what you call OTA update . Also, I've seen that some app may not work if some verification fails ?
So basically the question could you explain me a bit the broad picture and what would you recommend ?
Thank's
PS : sorry I'm not super acurate, I rooted my LG G2 years ago and things seems to have evolved a lot since then.
jbonlinea said:
Hi,
I'm a happy new owner of the redmi note 4 and I've already unlocked the bootloader.
I would like to use google camera, and eventually adblock.
I've seen there are various way to
- install bootloaders (and it seems there are also various boatloaders)
- root the phone
- enable camera2 api, with and without root
- ...
Actually I like to keep the stock rom and the phone as vanilla as possible, as I've read there are redundant issue with custom rom. I also do like the idea of being able to update the phone "normally", which seems to be what you call OTA update . Also, I've seen that some app may not work if some verification fails ?
So basically the question could you explain me a bit the broad picture and what would you recommend ?
Thank's
PS : sorry I'm not super acurate, I rooted my LG G2 years ago and things seems to have evolved a lot since then.
Click to expand...
Click to collapse
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
I am using pixel experience 8.1 oreo rom in my redmi notr 4.and i have also install google canera mod.mgcmod5.i have done all the settings but ehen i am trying to take puctures its force closing and lagging..need solution..
ArK96 said:
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
Click to expand...
Click to collapse
After every OTA update do I need to re-flash everything?
ÀnkanKoley said:
After every OTA update do I need to re-flash everything?
Click to expand...
Click to collapse
If RedWolf succeeds OTA survival, then there is no need. But after OTA if RedWolf is replaced by stock recovery, then yes you'll have to flash everything once again. Refer RedWolf thread for more details on OTA survival.
ArK96 said:
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
Click to expand...
Click to collapse
Sounds right and great, thank's !
Two question.
- I've read somewhere that some custom recovery and/or root may cause some app to fail, notably banking app.
Well I used to use such app on my rooted G2 , but will it remain posible after folowing the process you suggest above ?
about redwolf, there is quite a lot of explainations in theses two links 1 and 2, however I can figure out how to install redwolf ?! what am I suppose to do with the .iso image available for download ? isn't there a step by step install guide somewhere ?
Thank's
jbonlinea said:
Sounds right and great, thank's !
Two question.
- I've read somewhere that some custom recovery and/or root may cause some app to fail, notably banking app.
Well I used to use such app on my rooted G2 , but will it remain posible after folowing the process you suggest above ?
about redwolf, there is quite a lot of explainations in theses two links 1 and 2, however I can figure out how to install redwolf ?! what am I suppose to do with the .iso image available for download ? isn't there a step by step install guide somewhere ?
Thank's
Click to expand...
Click to collapse
Use Magisk for root and once Magisk is installed enable Magisk hide for the banking app, this will hide root from that particular app.
Installing a custom recovery like redwolf :
1. Unlock your phone's bootloader.
2. Download the recovery image file, rename it to "recovery.img" and place in a folder on your computer. Make sure you have working ADB and fastboot drivers installed on this computer.
3. Connect your phone in fastboot mode (Volume Down + Power button)
4. Open command prompt in the folder containing the downloaded recovery. (Shift + Mouse right click)
5. Type the below command into the command prompt
fastboot flash recovery recovery.img
fastboot boot recovery.img
Once inside recovery flash ROM, Magisk, if ROM is MiUI flash lazyflasher too, or phone won't boot. If custom ROM ignore lazyflasher and flash GApps instead.
If recovery installation instructions confuse you there are infinite number of YouTube videos that will help you.
ArK96 said:
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
Click to expand...
Click to collapse
What would broke on miui camera?
amnher said:
What would broke on miui camera?
Click to expand...
Click to collapse
The HDR mode.
ArK96 said:
Use Magisk for root and once Magisk is installed enable Magisk hide for the banking app, this will hide root from that particular app.
Installing a custom recovery like redwolf :
1. Unlock your phone's bootloader.
2. Download the recovery image file, rename it to "recovery.img" and place in a folder on your computer. Make sure you have working ADB and fastboot drivers installed on this computer.
3. Connect your phone in fastboot mode (Volume Down + Power button)
4. Open command prompt in the folder containing the downloaded recovery. (Shift + Mouse right click)
5. Type the below command into the command prompt
fastboot flash recovery recovery.img
fastboot boot recovery.img
Once inside recovery flash ROM, Magisk, if ROM is MiUI flash lazyflasher too, or phone won't boot. If custom ROM ignore lazyflasher and flash GApps instead.
If recovery installation instructions confuse you there are infinite number of YouTube videos that will help you.
Click to expand...
Click to collapse
Thank's again , that's awesome!
Maybe a few more question
FIRST
at step 2) how do I make sure I have a working ADB and Fastboot drivers ?
As far as I understand, fastboot drivers should already be installed ; however I suspect ADB not to be installed.
Indeed, I've already unlocked the bootloader with this tutorial, and I can confirm the phone is unlocked from settings > more settings > developper options > Mi locking status.
So basically I've already installed MiUSBDrivers and ran miflashunlock. There are fastboot.exe, fastboot_unlock.exe and AdbWinApi.dll files in the miflash_unlock folder I downloaded and used to unlock, but I haven't used any of these later 3 files.
I have found this post to install ADB
SECOND
at step 4), the best would be to place the recovery image downladed from here into the folder containing ADB downloaded just above right ?
Then, go on with step 5)
THIRD
If everything went well, my phone is supposed to reboot in redwolf recovery, ok.
but whart do you mean by "Once inside recovery flash ROM" ?
Why am I suposed to flash a rom ?
To my understanding, I already have a rom, miui, and do not want to change for the moment.
Should I download the "Full Rom" from here, or the "Redmi Note 4 Qualcomm Latest Global Stable Version Fastboot File" rom from here ? If so, what souhld I do with the rom; where sould I place it, on the computer, on the phone ?
Or do I need to flash ROM only if I want to change/upgrade my rom ?
FOURTH
To flash Magisk and Lazyflasher.
I understood that redwolf recovery comes with Magisk, so I assume I'll only have to go to "install" tab of redwolf, and I'll find the Magisk file to flash.
Ok what about Lazyflasher ? is it also provided with redwolf ?
Or should I download it ? and if so where should I place the file ?
FIFTH (and last)
I assume once installed from recovery, Magisk will show himself as an app/icon on the "desktop", and I'll be able to selectively enable Magisk hide for the banking app.
Thank's again for your help.
Sorry if I have too many questions, I'm a little rusted, and prefer having a comprehensive picture of the porcess before jumping into it, and avoid one more post entitled helpppp pleeeeeese I bricked my phone
jbonlinea said:
Thank's again , that's awesome!
Maybe a few more question
FIRST
at step 2) how do I make sure I have a working ADB and Fastboot drivers ?
As far as I understand, fastboot drivers should already be installed ; however I suspect ADB not to be installed.
Indeed, I've already unlocked the bootloader with this tutorial, and I can confirm the phone is unlocked from settings > more settings > developper options > Mi locking status.
So basically I've already installed MiUSBDrivers and ran miflashunlock. There are fastboot.exe, fastboot_unlock.exe and AdbWinApi.dll files in the miflash_unlock folder I downloaded and used to unlock, but I haven't used any of these later 3 files.
I have found this post to install ADB
SECOND
at step 4), the best would be to place the recovery image downladed from here into the folder containing ADB downloaded just above right ?
Then, go on with step 5)
THIRD
If everything went well, my phone is supposed to reboot in redwolf recovery, ok.
but whart do you mean by "Once inside recovery flash ROM" ?
Why am I suposed to flash a rom ?
To my understanding, I already have a rom, miui, and do not want to change for the moment.
Should I download the "Full Rom" from here, or the "Redmi Note 4 Qualcomm Latest Global Stable Version Fastboot File" rom from here ? If so, what souhld I do with the rom; where sould I place it, on the computer, on the phone ?
Or do I need to flash ROM only if I want to change/upgrade my rom ?
FOURTH
To flash Magisk and Lazyflasher.
I understood that redwolf recovery comes with Magisk, so I assume I'll only have to go to "install" tab of redwolf, and I'll find the Magisk file to flash.
Ok what about Lazyflasher ? is it also provided with redwolf ?
Or should I download it ? and if so where should I place the file ?
FIFTH (and last)
I assume once installed from recovery, Magisk will show himself as an app/icon on the "desktop", and I'll be able to selectively enable Magisk hide for the banking app.
Thank's again for your help.
Sorry if I have too many questions, I'm a little rusted, and prefer having a comprehensive picture of the porcess before jumping into it, and avoid one more post entitled helpppp pleeeeeese I bricked my phone pen
Click to expand...
Click to collapse
ADB/Fastboot Drivers
Looks like you don't have ADB/Fastboot installed system wide. Although it is completely fine to use adb/fastboot in a folder, installing it system wide is much more convenient because you can open a command window in any folder and execute ADB/Fastboot commands. [URL="https://forum.xda-developers.com/showthread.php?t=2588979”]Here's the link[/URL] to download the system wide installer. Install it and REBOOT your PC.
Flashing RedWolf
Once drivers are installed and PC rebooted, connect phone in Fastboot mode and follow my previous instructions. Also now you can open command prompt in any folder and execute the commands since ADB/Fastboot is installed system wide.
Flashing ROM
Sorry if I confused you there in the previous post. If you wish to stick with your current MIUI ROM then you don't need to flash any ROM file.
Flashing Lazyflasher
You MUST flash lazyflasher since you want to stay with MIUI. If you install a custom recovery on MIUI without flashing lazyflasher, the phone will not boot and will be stuck at the MI logo. I've attached the file.
Flashing Magisk
Flash Magisk after lazyflasher. You may download the latest package from Magisk thread or use RedWolf's built in Magisk package as you said and update it later through the Magisk manager app. And yes, you can select which apps can be Magisk hidden.
ArK96 said:
ADB/Fastboot Drivers
Looks like you don't have ADB/Fastboot installed system wide. Although it is completely fine to use adb/fastboot in a folder, installing it system wide is much more convenient because you can open a command window in any folder and execute ADB/Fastboot commands. [URL="https://forum.xda-developers.com/showthread.php?t=2588979”]Here's the link[/URL] to download the system wide installer. Install it and REBOOT your PC.
Flashing RedWolf
Once drivers are installed and PC rebooted, connect phone in Fastboot mode and follow my previous instructions. Also now you can open command prompt in any folder and execute the commands since ADB/Fastboot is installed system wide.
Flashing ROM
Sorry if I confused you there in the previous post. If you wish to stick with your current MIUI ROM then you don't need to flash any ROM file.
Flashing Lazyflasher
You MUST flash lazyflasher since you want to stay with MIUI. If you install a custom recovery on MIUI without flashing lazyflasher, the phone will not boot and will be stuck at the MI logo. I've attached the file.
Flashing Magisk
Flash Magisk after lazyflasher. You may download the latest package from Magisk thread or use RedWolf's built in Magisk package as you said and update it later through the Magisk manager app. And yes, you can select which apps can be Magisk hidden.
Click to expand...
Click to collapse
Awesome !
Great to know that I should fisrt flash lazyflasher and then magisk.
Stupid, probably last question
Should I do everything up to and incliding flashing lazyflsher, rebot normally, and then reboot again in redwolf and flash magisk ?
of is this extra zealous ?
Thanks
jbonlinea said:
Awesome !
Great to know that I should fisrt flash lazyflasher and then magisk.
Stupid, probably last question
Should I do everything up to and incliding flashing lazyflsher, rebot normally, and then reboot again in redwolf and flash magisk ?
of is this extra zealous ?
Thanks
Click to expand...
Click to collapse
While it can all be flashed at one go, I suggest you to flash LF and once boot your device successfully and reboot to redwolf and flash Magisk afterwards.
ArK96 said:
While it can all be flashed at one go, I suggest you to flash LF and once boot your device successfully and reboot to redwolf and flash Magisk afterwards.
Click to expand...
Click to collapse
Thank you very much !
jbonlinea said:
Thank you very much !
Click to expand...
Click to collapse
No problem.
ArK96 said:
No problem.
Click to expand...
Click to collapse
hum, :silly:
the link you sent for adb do not work
jbonlinea said:
hum, :silly:
the link you sent for adb do not work
Click to expand...
Click to collapse
Here,
https://www.dropbox.com/s/mcxw0yy3jvydupd/adb-setup-1.4.3.exe?dl=0
ArK96 said:
Here,
https://www.dropbox.com/s/mcxw0yy3jvydupd/adb-setup-1.4.3.exe?dl=0
Click to expand...
Click to collapse
Excellent !
so
- I did installed redwolf recovery - changed settings as advised here
- flashed lazyflasher
- reboot -> wokrs I'm back on miui
- reboot in redwolf and flashed magisk
- reboot into android, installed rootchek, I'm rooted
- hide magisk from magisk manager for my apps --> working
Everything works
Further questions :
- Am I suppose to clean cache at some stage ? I can still do it now ?
- Is there some recomended module for magisk ? (not sure what they are for)
- as for everything else, I've seen many options to enable camera2api. Which one would you recomend ? is "persist.camera.HAL3.enabled=1" the only needed change or this treat rises something this
- is there a recomended version/release of google camera to use with miui9 global, latest update (not developper) (I've seen various reported issues depending on version/release)
- any other must/nice/interesting hacks to fully enjoy this phone ?
- any security recomendation ? (re-locking the bootloader ? instally some utilities... ?)
thanks
after that, I'll be done
jbonlinea said:
Excellent !
so
- I did installed redwolf recovery - changed settings as advised here
- flashed lazyflasher
- reboot -> wokrs I'm back on miui
- reboot in redwolf and flashed magisk
- reboot into android, installed rootchek, I'm rooted
- hide magisk from magisk manager for my apps --> working
Everything works
Further questions :
- Am I suppose to clean cache at some stage ? I can still do it now ?
- Is there some recomended module for magisk ? (not sure what they are for)
- as for everything else, I've seen many options to enable camera2api. Which one would you recomend ? is "persist.camera.HAL3.enabled=1" the only needed change or this treat rises something this
- is there a recomended version/release of google camera to use with miui9 global, latest update (not developper) (I've seen various reported issues depending on version/release)
- any other must/nice/interesting hacks to fully enjoy this phone ?
- any security recomendation ? (re-locking the bootloader ? instally some utilities... ?)
thanks
after that, I'll be done
Click to expand...
Click to collapse
Clean cache not required.
Magisk modules are MODs for your system but they are done without tampering your system. (Systemless MODs).
Try Dolby atmos ZTE Axon 7 audio MOD module, YouTube vanced module (100% Adfree, background play)..etc
Use Arnova's GCam.
Never ever relock bootloader with a custom recovery or custom ROM. Else irreversible brick.
I've repeated too much stuff that has been posted in the forum already, if you have any further doubts search the forum or use Google.
Flash through redwolf the attached file to enable camera2api. If you want to uninstall it later go to magisk manager and delete it.
Cheers.
ArK96 said:
Clean cache not required.
Magisk modules are MODs for your system but they are done without tampering your system. (Systemless MODs).
Try Dolby atmos ZTE Axon 7 audio MOD module, YouTube vanced module (100% Adfree, background play)..etc
Use Arnova's GCam.
Never ever relock bootloader with a custom recovery or custom ROM. Else irreversible brick.
I've repeated too much stuff that has been posted in the forum already, if you have any further doubts search the forum or use Google.
Flash through redwolf the attached file to enable camera2api. If you want to uninstall it later go to magisk manager and delete it.
Cheers.
Click to expand...
Click to collapse
Hi dude
I'm almost done but back to square 0, with blinking black screen at boot !
No crisis, I can still go to redwolf recovery, as well as fastboot.
How it happend ?
In magisk manager (on miui) I checked what modules were available in the download panel, and tried "Google Pixel 2 Experience" or something similar.
On reboot, the mi logo is displayed, then I have a black screen blinking on and off, without mi logo, just black, on and off
I thus wanted to unistal the mod with magisk module uninstaller, but the install fails and return that "magisk is not installed" and "magisk is required for this mod"
So I obviously couldn't try to uninstall the supposed failing module
I thus rebooted in redwold and installed magisk from redwolf (the included release), things went well
However, I still cant install magisk module uninstaller, getting the same error as above.
I took my chance and try to re-install magisk from the zip filed I downloaded, the install process was successfull, but I still can't install magisk mod uninstaller, and the black screen issue persist.
Lastly, I took my chance and try to re-install lazy flasher, the install process was successfull, but the black-screen issue persist.
To be honest, I'm a bit sctuck now.
What may be the right procedure to solve this problem ?
Am I screwed and do I have to reflash a whole rom ?
If so Should I do it from redwolf, and how ?
Or should I do it from the pc with fastboot, and how ?
Thanks for your directions
ps: i was interested by pixel 2 experience module as at it was written that it was compatible with mido and provides camera2api, which might have been a nice combo.
ps 2 : I also did installed dolby as you suggested, it worked but the demo crashed to app
ps 3 : I also did installed youtube vaccant, but I couldn't see any new app and my original youtube still had add and couldn't play in the back... not sure it reveals something on the effectiveness of magisk...
1. please read this very carefuly.this guide is made from my personal experience.
like some members of this forums told me and i think a little about it,there can be problem about downgrade to oreo with devices who have unlock device from operator.but i believe can be easily unlock with talk with operators,not sure,but be best to check it out by self.
firstly i am not noob,i am developer and compiler for many mtk device. sadly this is my FIRST
samsung device also snapdragon. so for me completely unknown.i want in first root and do custom roms but untill now
i dont find any device tree for this device.kernel source i have but device and vendor tree not.then i found i can
flash gsi on this device. so i do as i will explain in following text.
2. as many other of you i have update device on PIE and next days i install update i found possibility to flash gsi,
so i try. i found patched pie boot.img and try to flash gsi roms but none of them isnt boot.so i stop and again read gsi guide
for flash gsi.i read that devices shipped with some firmwares have chance to flash gsi roms.so i found oreo rom
for our device and flash it with odin.rom is boot without any problems.i set up all things as normall(google account)
and after all setup i go to device info and tap on build numbers 7-10 times and then developer settings is open,then i
checked if is there oem unlocking.(if you dont set up google account this settings will not shown(oem unlocking)).
when i see is ok and there,i power off device,go to download mode and connect with pc,and open odin,
and flash twrp(again thanks to ashyx).dont let odin to boot system(turn off auto rebbot in option),
so i reboot to recovery,go to wipe,choose format data,write yes and swipe.
after that i reboot to recovery you MUST flash oreo enforcing.zip,rmm and oreo patched boot.and go to install choose micro sd card and go to flash img. choose gsi rom you want and
flash it as system(pop up windows will ask wich partition you choose(system),then swipe to flash,after flashing you flash magisk,
and go to mount and mount system and reboot to system. firstly your device can reboot once-twice during,but dont worry
after that will go to boot and in short time,one- two minutes will boot.
3.now i must warning you.many of gsi roms work properly,but have many bugs.mtp dont works with pc in boot up,but in recovery
works without problems.for me is not problem,i can live with it.
3.1.sim card 2 is work but sim card 1 is not see it.also i can live with it.most of time i use 1 sim card,not both.
3.2.fm radio isnt show,and not work.
4.in short i give you again flash guide.
go to recovery (must be in oreo)
go to wipe-format data,write yes and swipe to format (many say to need back to recovery,i didnt do that but is your choice).
go to sd card and install oreo enforcing.zip,RMM bypass.zip and oreo patched boot.img
go to install and choose flash.img and choose gsi you want,and flash as system
go to install zip and flash magisk
then go to mount,mount system and reboot to system
device will reboot twice or more time and then after minute or two will reboot.be calm.
after device is reboot,enjoy.:good:
i will post some screenshots of booted gsi roms.oreo and pie.
list of booted gsi rom so far:
1. aex 5.7 oreo
2. aex 6.5 pie
3. aosdp pie(this rom not show network and sim cards)
4. aosp by phusson pie
5. bootlegger oreo
6. descendant 3.0 pie
7. dot os pie(dont show network and simcards)
8. havoc os pie
9. lineage 16 pie
10. RR oreo
11. RR pie
12. system DU oreo
13. xenon hd oreo
GSI with errors:
AOSDP (not shown sim cards,no network,all other stuff work,off course no fm radio)
Evolution X (dont want to boot.)
Octopus OS (dont boot)
Viper OS Official (not shown sim cards,all other stuff work except fm radio)
Dot OS (dont show sim cards,no network,no fm radio)
Liquid Remix (dont boot)
Omni rom (boot but goes constantly on reboot)
Pixel Expirience (boot but no sim cards and no network and no fm radio)
people one more notice: j4+ is ARM A ONLY device,dont flash any other gsi.
deleted
What version of RR Pie did you test? The May Release?
JDBS30 said:
What version of RR Pie did you test? The May Release?
Click to expand...
Click to collapse
all of them.
this link i used and choose one of them from your choice arm a only of course: https://get.resurrectionremix.com/?dir=gsi
I can't install Resurrection Remix
I face so much problems while installing custom roms, I tried Android Pie GSI, Pixel Experience, Resurrection Remix. But All of them crashes at boot animation. What can I do? I can't find any thread about that.
My phone is Samsung Galaxy J4+ (arm aonly).
Please help me?
elfennani said:
I face so much problems while installing custom roms, I tried Android Pie GSI, Pixel Experience, Resurrection Remix. But All of them crashes at boot animation. What can I do? I can't find any thread about that.
My phone is Samsung Galaxy J4+ (arm aonly).
Please help me?
Click to expand...
Click to collapse
my dear friend did you read my guide?. i explain wich gsi roms can flash and how.please read from start to end.it is very clear.
rudi021 said:
my dear friend did you read my guide?. i explain wich gsi roms can flash and how.please read from start to end.it is very clear.
Click to expand...
Click to collapse
Yes, I read everything, I tried Pixel Experience and Android Pie GSI before seeing this thread. So I decided to try Resurrection Remix, But it crashes while boot animation then after the phone gets restarted (bootloop)
elfennani said:
Yes, I read everything, I tried Pixel Experience and Android Pie GSI before seeing this thread. So I decided to try Resurrection Remix, But it crashes while boot animation then after the phone gets restarted (bootloop)
Click to expand...
Click to collapse
like i wrote your device must be on oreo,not on pie.thats my expirience.when i was on pie i cant boot any pie rom.after i flash oreo stock rom and flash twrp i flash and boot almost any gsi wich is aviable.you must be on oreo stock rom and then flash twrp,then flash oreo enforcing,rmm,then format data(write yes and swipe to format),then flash gsi as system,flash magisk,then go to mount and check system then reboot.thats it. maybe is my mistake i didnt write that you must do flash those thing before,but i supose people is knowing what must to do when do flash twrp. sorry.
rudi021 said:
like i wrote you must be on oreo,not on pie.thats my expirience.when i was on pie i cant boot any pie rom.after i flash oreo stock rom and flash twrp i flash and boot almost any gsi wich is aviable.you must be on oreo stock rom and then flash twrp,then flash oreo enforcing,rmm,then format data(write yes and swipe to format),then flash gsi as system,flash magisk,then go to mount and check system then reboot.thats it. maybe is my mistake i didnt write that you must do flash those thing before,but i supose people is knowing what must to do when do flash twrp. sorry.
Click to expand...
Click to collapse
How did you downgrade your firmware?
elfennani said:
How did you downgrade your firmware?
Click to expand...
Click to collapse
i found oreo firmware. if you want you can download from my google drive. here is link: https://drive.google.com/file/d/1KnqHZ8_EVTstJP5AMsMy_8Uc1QV-vMHe/view?usp=sharing
Please help
rudi021 said:
1. please read this very carefuly.this guide is made from my personal experience.
like some members of this forums told me and i think a little about it,there can be problem about downgrade to oreo with devices who have unlock device from operator.but i believe can be easily unlock with talk with operators,not sure,but be best to check it out by self.
firstly i am not noob,i am developer and compiler for many mtk device. sadly this is my FIRST
samsung device also snapdragon. so for me completely unknown.i want in first root and do custom roms but untill now
i dont find any device tree for this device.kernel source i have but device and vendor tree not.then i found i can
flash gsi on this device. so i do as i will explain in following text.
2. as many other of you i have update device on PIE and next days i install update i found possibility to flash gsi,
so i try. i found patched pie boot.img and try to flash gsi roms but none of them isnt boot.so i stop and again read gsi guide
for flash gsi.i read that devices shipped with some firmwares have chance to flash gsi roms.so i found oreo rom
for our device and flash it with odin.rom is boot without any problems.i set up all things as normall(google account)
and after all setup i go to device info and tap on build numbers 7-10 times and then developer settings is open,then i
checked if is there oem unlocking.(if you dont set up google account this settings will not shown(oem unlocking)).
when i see is ok and there,i power off device,go to download mode and connect with pc,and open odin,
and flash twrp(again thanks to ashyx).dont let odin to boot system(turn off auto rebbot in option),
so i reboot to recovery,go to wipe,choose format data,write yes and swipe.
after that i reboot to recovery you MUST flash oreo enforcing.zip,rmm and oreo patched boot.and go to install choose micro sd card and go to flash img. choose gsi rom you want and
flash it as system(pop up windows will ask wich partition you choose(system),then swipe to flash,after flashing you flash magisk,
and go to mount and mount system and reboot to system. firstly your device can reboot once-twice during,but dont worry
after that will go to boot and in short time,one- two minutes will boot.
3.now i must warning you.many of gsi roms work properly,but have many bugs.mtp dont works with pc in boot up,but in recovery
works without problems.for me is not problem,i can live with it.
3.1.sim card 2 is work but sim card 1 is not see it.also i can live with it.most of time i use 1 sim card,not both.
3.2.fm radio isnt show,and not work.
4.in short i give you again flash guide.
go to recovery (must be in oreo)
go to wipe-format data,write yes and swipe to format (many say to need back to recovery,i didnt do that but is your choice).
go to sd card and install oreo enforcing.zip,RMM bypass.zip and oreo patched boot.img
go to install and choose flash.img and choose gsi you want,and flash as system
go to install zip and flash magisk
then go to mount,mount system and reboot to system
device will reboot twice or more time and then after minute or two will reboot.be calm.
after device is reboot,enjoy.:good:
i will post some screenshots of booted gsi roms.oreo and pie.
list of booted gsi rom so far:
1. aex 5.7 oreo
2. aex 6.5 pie
3. aosdp pie(this rom not show network and sim cards)
4. aosp by phusson pie
5. bootlegger oreo
6. descendant 3.0 pie
7. dot os pie(dont show network and simcards)
8. havoc os pie
9. lineage 16 pie
10. RR oreo
11. RR pie
12. system DU oreo
13. xenon hd oreo
GSI with errors:
AOSDP (not shown sim cards,no network,all other stuff work,off course no fm radio)
Evolution X (dont want to boot.)
Octopus OS (dont boot)
Viper OS Official (not shown sim cards,all other stuff work except fm radio)
Dot OS (dont show sim cards,no network,no fm radio)
Liquid Remix (dont boot)
Omni rom (boot but goes constantly on reboot)
Pixel Expirience (boot but no sim cards and no network and no fm radio)
people one more notice: j4+ is ARM A ONLY device,dont flash any other gsi.
Click to expand...
Click to collapse
Thank you for sharing your experience. I was planning on trying to flash a GSI, but I have to wait 7 days for the OEM unlock on Stock Oreo. Of these files you listed, I do not have the "oreo patched boot." This is also necessary, and if so, where do I find it?
Thank you in advance and I count on your help.
Maxmiliano Coelho said:
Thank you for sharing your experience. I was planning on trying to flash a GSI, but I have to wait 7 days for the OEM unlock on Stock Oreo. Of these files you listed, I do not have the "oreo patched boot." This is also necessary, and if so, where do I find it?
Thank you in advance and I count on your help.
Click to expand...
Click to collapse
my dear friend just ask i will help you. this patched boot.img is made by ashyx. i will be bad member if i share his works without permissions.so i share with you his link. here is link for oreo patched boot.img https://androidfilehost.com/?fid=1395089523397921797
please follow instructions carefully. read twice and try to understand.enjoy.if you have any doubt please ask. thank you.
Thanks again. I am waiting for the 7 day period to reappear the OEM unlock option which disappeared when I returned to stock oreo. With your help, the procedure to be performed became clearer. When I do the procedure, can I continue to ask questions if any? I thank you once again.
Maxmiliano Coelho said:
Thanks again. I am waiting for the 7 day period to reappear the OEM unlock option which disappeared when I returned to stock oreo. With your help, the procedure to be performed became clearer. When I do the procedure, can I continue to ask questions if any? I thank you once again.
Click to expand...
Click to collapse
why not.i am not star just ask and if i can help i will please to do that.you can always send me personal message(PM) on xda
Maxmiliano Coelho said:
Thanks again. I am waiting for the 7 day period to reappear the OEM unlock option which disappeared when I returned to stock oreo. With your help, the procedure to be performed became clearer. When I do the procedure, can I continue to ask questions if any? I thank you once again.
Click to expand...
Click to collapse
like https://forum.xda-developers.com/member.php?u=9101376 say in reply if you have unlock before then your device is unlocked.so no need to wait another 7 days.you must just do follow tread for flash recovery.can miss first time,two but read guide and no fear.but you cant miss if you try again. once your device is unlock you can flash no metter numbers of flashing roms(stock 8 or 9)once is unlock thats it.so dont be affraid to ask help here or anywhere on our xda group.always some will help you.:good:
rudi021 said:
like https://forum.xda-developers.com/member.php?u=9101376 say in reply if you have unlock before then your device is unlocked.so no need to wait another 7 days.you must just do follow tread for flash recovery.can miss first time,two but read guide and no fear.but you cant miss if you try again. once your device is unlock you can flash no metter numbers of flashing roms(stock 8 or 9)once is unlock thats it.so dont be affraid to ask help here or anywhere on our xda group.always some will help you.:good:
Click to expand...
Click to collapse
Thank you! I followed in his footsteps and was successful in installing LineageOS 16. Working very well, but I felt a slight problem regarding the audio volume, which is extremely low.
I would like to ask one more question, which is about testing other GSI: Is there a need to install one of those files, or just the image and Magisk?
Thank you very much.
Maxmiliano Coelho said:
Thank you! I followed in his footsteps and was successful in installing LineageOS 16. Working very well, but I felt a slight problem regarding the audio volume, which is extremely low.
I would like to ask one more question, which is about testing other GSI: Is there a need to install one of those files, or just the image and Magisk?
Thank you very much.
Click to expand...
Click to collapse
once you perform flashing gsi,no need repeat every time this steps,just (at least i do like that) format data,reboot to recovery,flash gsi(as system.image) and flash magisk then mount system and reboot.about audio volume install viper fx audio apk(Magisk module),and then fix volume as your own.
kapmino269 said:
If anyone faced problems with booting some roms on
ROM LOGO NOT SAMSUNG .
use this :
https://www.androidfilehost.com/?fid=6006931924117925309
Tested on j415f
RR
AOSP
DESCENDANT ZERO .
Click to expand...
Click to collapse
sorry but this doesnt work on my side of flashing GSI.OREO base. i try on many gsi who doesnt boot but not help. i boot this PIE gsi (on oreo base): descendant 3.1.1.; Prisma os(still cant find way to get network,no sim detected);Havoc os (works perfectly);Dot os 3.0 (same no sim detect); RR 2019-04-06 very nice rom; AEX by enes sastim 2019-05-09(also very nice rom);Viper os (but is Official and dont let use it)(mean boot but no sim works);Zirconium aosp (work well but seems like android kitkat seems so simple(i dont like it);and many more with same problems,they booted but not have network work, or like omni rom booted but reboot and then all over again.have many roms but have problems with our device(mine is sm-j415fn). anyway i try do same in PIE update but cant boot any rom (gsi). why ? dont know? thats why i downgrade in oreo and can flash and boot almost all gsi on list. did they work or not is other story.thank you.
rudi021 said:
sorry but this doesnt work on my side of flashing GSI.OREO base. i try on many gsi who doesnt boot but not help. i boot this PIE gsi (on oreo base): descendant 3.1.1.; Prisma os(still cant find way to get network,no sim detected);Havoc os (works perfectly);Dot os 3.0 (same no sim detect); RR 2019-04-06 very nice rom; AEX by enes sastim 2019-05-09(also very nice rom);Viper os (but is Official and dont let use it)(mean boot but no sim works);Zirconium aosp (work well but seems like android kitkat seems so simple(i dont like it);and many more with same problems,they booted but not have network work, or like omni rom booted but reboot and then all over again.have many roms but have problems with our device(mine is sm-j415fn). anyway i try do same in PIE update but cant boot any rom (gsi). why ? dont know? thats why i downgrade in oreo and can flash and boot almost all gsi on list. did they work or not is other story.thank you.
Click to expand...
Click to collapse
me i have not a network on aex extended but on dot os i have
Envoyé de mon Phh-Treble vanilla en utilisant Tapatalk
kapmino269 said:
Guys , sorry I found error in my script and I fixed it I tested it on AEX official , I will test it in others then post it .
@rudi021
---------- Post added at 09:15 AM ---------- Previous post was at 08:29 AM ----------
v2 : https://www.androidfilehost.com/?fid=6006931924117930007
tested : work with rom logo bootloop 100%
Click to expand...
Click to collapse
thank you bro. i definetly try this on pie upgrade and inform you.thank you for your hard work. i am on vacation and when i come home i will try this.thank you and greetings from Croatia.:good:
also i stop build gsi roms for j4+ because my pc is old so i need little upgrade of same( RAM(have only 4 gb,need for pie at least 8 gb ,my motherboard can have 32 gb,), my processor is i3 but i will upgrade on i5 and after that i will continue work on it. but now i am on vacation with my wife and children and when i come hom ei will continue to work it.thank you once more.
Hello,
I've uploaded some image files for Nokia 3.2 and want to share them.
I've packed some images for Nokia 3.2 00WW variant (e.g. Magisk, fastboot ROM) and will upload user images for the 00EEA variant, too.
It just needs some more time to upload completely.
EDIT: I transfered all the files to Mega.nz
https://mega.nz/folder/hVMTiCbT#OhmmxhtKabnNn2hWfiIgHQ
P.S. if someone has the european Variant and wants to provide matching Magisk Patched boot images just send me a link to those and i will add them to my Mega.nz folder
Hello,
i just uploaded the patched boot image december 2019 for the europe 00EEA version in other thread under https://forum.xda-developers.com/attachment.php?attachmentid=4929795&d=1579367908.
Perhaps you can add it to your google drive.
Greetings
Hi, sorry i didnt see it. Could you created a Copy of it with dm-verity disabled? You can do it with superr's kitchen. So that we have a magisk Image for GSIs.
Thanks
P.S. i will Upload the magisk patched image tomorrow.
EDIT: I can Just remove dm verity on my own. :silly:
I've created a Telegram Channel for Nokia 3.2
Updates regarding Source Code, the Google Drive mirror (magisk stuff,Firmwares etc.) And any helpful information will be posted by me on the Channel.
Note information inside ReadMe file on the Google Drive link
TA-1156 Qcn
Hello, can you upload Nokia 3.2 TA-1156 models qcn file?
accidentally delete all partitions and now i want to restore imei numbers and serial number to get the mobile network
chinovaso said:
Hello, can you upload Nokia 3.2 TA-1156 models qcn file?
accidentally delete all partitions and now i want to restore imei numbers and serial number to get the mobile network
Click to expand...
Click to collapse
Hi I don't have any qcn file. My Nokia 3.2 is currently being repaired. But I've found a tool what could help you.
https://www.getdroidtips.com/download-imei-qcn-tool/
Just test it and look if it works
chinovaso said:
Hello, can you upload Nokia 3.2 TA-1156 models qcn file?
accidentally delete all partitions and now i want to restore imei numbers and serial number to get the mobile network
Click to expand...
Click to collapse
Thank you s3tupw1zard, but I try this tool already, it works , *06# when it checks it shows the imei numbers but there still no a gsm signal.
Also the serial number is shown as 012345678E0000 and in *#*#4636#*#* servise menu when i chek says Mobile radio is oFF
How to flash using fastboot
Hey mate
Can u guide me through flashing magisk boot img
Im kinda of confused becoz of A B partitions
Any detailed guide would be appreciated
Im on latest January update 2020
Nokia 3.2 (deadpool)
chinovaso said:
Thank you s3tupw1zard, but I try this tool already, it works , *06# when it checks it shows the imei numbers but there still no a gsm signal.
Also the serial number is shown as 012345678E0000 and in *#*#4636#*#* servise menu when i chek says Mobile radio is oFF
Click to expand...
Click to collapse
Hi,
I can't help you in this case. Best would be if you send it in.
You can get your imei with 'fastboot getvar all' (without quotes) to send it in.
You need the imei for sending it in. Dont worry about warranty the ar not allowed anymore to denying warranty due to new google terms.
Just go to nokia website and order a repair.
No0bGuy said:
Hey mate
Can u guide me through flashing magisk boot img
Im kinda of confused becoz of A B partitions
Any detailed guide would be appreciated
Im on latest January update 2020
Nokia 3.2 (deadpool)
Click to expand...
Click to collapse
I write a short guide into a new thread. I pack some files for gsi flashing together.
You will find this guide in about 30 Minutes on the Nokia 3.2 Guides section
Hello,
i uploaded the january 2020 patched boot.img for the European 00EA with dm-verify=off.
Please include on your googledrive!
https://forum.xda-developers.com/attachment.php?attachmentid=4956671&d=1582404743
Greetings
Using these images
Hi All
i've bought a Nokia 3.2 for installing lineageOS ! So i could unlock it and installed this ASOP-Image (probably the 00WW-Version) thru ADB and fastboot with the result to get a crappy OS without WiFI.
At the end i needed about 10 days to get a connection (probably thru qualcomm-drivers) to the pc again, where i can use your (hopefully working) images.
In order to avoid a malfunctioning NOKIA, i am asking about the right way to install the 00EA-Version:
Again i can use adb and fastboot, so first step is to use flash-user-bin.bat for flashing boot.bin, dtbo.bin, system.bin, vendor.bin and vbmeta.bin !
Now there should be a working OS with WiFI, second step would be patching boot_jan2020_dmOFF_00EA.img and third step patching twrp-3.2-dpl-00eea.img.
At last it should be possible to install LineAgeOS thru Magisk Manager (or CWM) ?
Thanks for your advices
Your device needs the images with the same version. So boot.img from January combined with firmware from December lead into bugs like WiFi not working. Reboot to bootloader, there is a info where either 00WW (international Variant) or 00EEA (European Variant) is written. I've uploaded a GSI base for both variants on the Google drive Link at the beginning of this thread. You can find both base 7z Files Inside GSI folder. But be sure which Variant you have. After executing flash-all.bat execute the other bat file (it will flash magisk patched img with dm-verity removed) and after that finishes you can flash any GSI to system.
And you can't install ROMs through Magisk. It is Superuser. You need to be in Bootloader mode.
And USB debugging needs to be on and your PC needs to be authorized by your device. Just activate USB debugging in developer options and type adb devices. There should appear a prompt.
thx
for fast reply. It should be 00EEA, because i've bought it in Austria. I think, i have seen it in the settings/my phone too.
So i will use the GSI-Version tomorrow. With Magisk-Manager i should could load this TWRP-Image (on a SD-Card) too ?
Stupid Question: what is the meaning of the shortciut GSI ?
Regards
other bat-file
s3tupw1zard said:
Your device needs the images with the same version. So boot.img from January combined with firmware from December lead into bugs like WiFi not working. Reboot to bootloader, there is a info where either 00WW (international Variant) or 00EEA (European Variant) is written. I've uploaded a GSI base for both variants on the Google drive Link at the beginning of this thread. You can find both base 7z Files Inside GSI folder. But be sure which Variant you have. After executing flash-all.bat execute the other bat file (it will flash magisk patched img with dm-verity removed) and after that finishes you can flash any GSI to system.
Click to expand...
Click to collapse
Hi s3tupw1zard !
where is this other bat-File ? This GSI (generic system image)-Folder of 00EEA is empty, but i've used user_images_00EEA.7z and this is working perfectly.
In spite of it i would like to change booting (with magisk-patched.img). but this is existing for 00WW only. I've tried to flash twrp-Image too, but there i've got errors, so i've flashed user_images_00EEA completely again.
Thanks for your work
At last
i could create something, but still there is something missing !
I've downloaded boot_nodm_magisk_patched.img from shared googleDrive and patched it with MagiskManager.
Unfortunelately i tried to flash this file without renaming - so i had to reset to factory settings, because booting was not working.
After that, i was remembering to rename this boot-file to boot.img, flashed to factory new system - following flashing the system with LineAgeOS from Andy - https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/ (renamed it to system.img)
The result: booting procedure for working LineAgeOS needs about 5 minutes and wifi is missing !
Does anyone have a clue ?
Do i need to setup system with user-Image (December 2019) from Manuels Google Drive before ?
ThankYou for advices
Gerhard
Then you flashed the wrong boot.img.
You must look for your Version - 00WW or 00EEA - and you must have the corresponding security level to your firmware, means January or December ........
00ww - 00eea
page1875 said:
Then you flashed the wrong boot.img.
You must look for your Version - 00WW or 00EEA - and you must have the corresponding security level to your firmware, means January or December ........
Click to expand...
Click to collapse
thanks for reply.
If i am lucky, i will use boot_jan2020_dmOFF_00EA.img next time - but for now i have (possibly) corrupted partition table file and so device is ended in a fastboot-mode loop - Android ONE Logo flashes up less than 1 second
So hopefully with fastboot flash partition Firmware\gpt_both0.bin (gpt_both0.bin from Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL) i can restore partition table file in spite of this 00WW-Version.
Does anyone have seen firmware for 00EEA-Version ?
cheers
Idiots Guide
The reason for infinite bootloop and ADB-Flash error messeage 'FAILED (remote: partition table doesn't exist)' may be (as i remember) is to rename boot.bin from user_images_00EEA of our wizard to boot.img.
Resetting to factory defaults is not possible anymore - so beware of it !
Patched Magisk v23 for A21s (A11/OneUI 3)
Since I've seen and tried installing Magisk via the default instructions from the legend topjohnwu himself, I noticed it does not work at all. The phone
just doesn't even boot into Android at all, and after researching I have seen that this is a very specific problem with the phone itself due to weird implementation from Samsung.
Extremely simplified, apparently there is a conflict with skip-initramfs because of System-as-Root and the A/B system partitioning introduced with Project Treble. I will still have to read more into it.
There are already patched Magisk apps/images for this phone available, but I noticed they are not really in active development (last patched Magisk was still v22), so I pulled the latest Magisk from the official repository and implemented the fix from this pull request on the official repo. They are not interested in accepting the pull request, so we'll have to do our own "Magisk" for the time being.
I will try to update this as much as possible and try to incorporate fixes, user feedback and more. This has been only tested on latest A11 and OneUI 3. I will also start working on TWRP soon.
Since the APK isn't signed yet, please uninstall Magisk Manager if present, and install this one. It will display a warning when installing, but don't worry.
Options to install:
Flash boot.tar from the ZIP in Odin on AP
Install the APK from this thread and patch your own boot image
magisk app-debug.apk working, but boot.img from
Model Number : SM-A217M
Region Code : COB
Device Version info :->>
BL version : A217MUBS5CUE2
AP version : A217MUBS5CUE2
DKXC said:
Patched Magisk v23 for A21s (A11/OneUI 3)
Since I've seen and tried installing Magisk via the default instructions from the legend topjohnwu himself, I noticed it does not work at all. The phone
just doesn't even boot into Android at all, and after researching I have seen that this is a very specific problem with the phone itself due to weird implementation from Samsung.
Extremely simplified, apparently there is a conflict with skip-initramfs because of System-as-Root and the A/B system partitioning introduced with Project Treble. I will still have to read more into it.
There are already patched Magisk apps/images for this phone available, but I noticed they are not really in active development (last patched Magisk was still v22), so I pulled the latest Magisk from the official repository and implemented the fix from this pull request on the official repo. They are not interested in accepting the pull request, so we'll have to do our own "Magisk" for the time being.
I will try to update this as much as possible and try to incorporate fixes, user feedback and more. This has been only tested on latest A11 and OneUI 3. I will also start working on TWRP soon.
Since the APK isn't signed yet, please uninstall Magisk Manager if present, and install this one. It will display a warning when installing, but don't worry.
Options to install:
Flash boot.tar from the ZIP in Odin on AP
Install the APK from this thread and patch your own boot image
Click to expand...
Click to collapse
Good job. thanks you, i wait updates
Elkingb said:
magisk app-debug.apk working, but boot.img from
Model Number : SM-A217M
Region Code : COB
Device Version info :->>
BL version : A217MUBS5CUE2
AP version : A217MUBS5CUE2
Click to expand...
Click to collapse
Forgot to mention that I used the latest DBT boot image for SM-217F/DSN. Not sure if it works for other models, but there aren't really many models anyways.
DKXC said:
Forgot to mention that I used the latest DBT boot image for SM-217F/DSN. Not sure if it works for other models, but there aren't really many models anyways.
Click to expand...
Click to collapse
For SM-217M Working full
everything is fine for the SM-217F
Im waiting for the twrp so much Good job!
To DKXC:
Hi There Expert,
I Would Recommend You To Upload Your Project To Github,
So Everyone Will Be Able To Give You Feedback
It Will Probably Help You In Developing A Better A21s Community
LonelyCracker said:
Github twrp a21s
Click to expand...
Click to collapse
Flashing this patched_magisk_v23\boot.tar ain't working.
Error displayed on the DL screen:
Only official released binaries are allowed to be flashed (BOOT)
My specs:
Loading ADB module.............OK
Starting ADB module...OK
Searching for SAMSUNG ADB device...OK
Checking device authorization...OK
Reading ADB device information...
ADB Serial Number : R58R52BFNKP
Model Name : SM-A217F
Device CodeName : A21S
Hardware : EXYNOS850 EXYNOS850
Modem Board : SHANNON318
HW Version : MP 0.500
BL version : A217FXXU5CUD6
AP version : A217FXXU5CUD6
CP version : A217FXXU5CUD4,A217FXXU5CUD4
CSC version : A217FOXM5CUD6
Android version : 11
Build date : Thu Apr 29 11:41:41 +07 2021
Country : Poland
IMEI : 35xxxxxxxx691
Serial Number : N/A
Carrier : XEO
Unlock by IMEI : Unknown
SIM State : ABSENT,ABSENT
Debug Level : 0x4f4c
CP Debug Level : N/A
Warranty VOID : 1
SIM operator : N/A
USB Settings : MTP,ADB
SamKEY Team (2017)
Installed app-debug.apk (patched Magisk) onto the phone.
Downloaded original XEO firmware.
Samfw.com_SM-A217F_XEO_A217FXXU5CUD6_fac.zip
Unzipped it.
Found AP file inside unzipped folder:
AP_A217FXXU5CUD6_CL21209953_QB39896814_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS11.tar.md5
Unpacked the AP file.
Contents:
Decoded the boot.img.lz4 file using LZ4 tool:
Copied boot.img file to the phone internal memory.
Opened Magisk and patched the boot.img file, which created magisk_patched-23001_nmETW.img in the phone Downloads folder
Copied patched file (magisk_patched-23001_nmETW.img) from the phone to my laptop - and changed its name to boot.img
Compressed it into boot.tar file using 7zip.
Restarted the phone into DOWNLOAD mode (using SamKey, or adb, or key combinantion, whatever).
Put boot.tar into AP section in ODIN.
Go to Options tab and disable "Auto Reboot", make sure "Re-Partition" is also disabled.
Aaand it fails again.
And the message in phone DL mode says:
Only official released binaries are allowed to be flashed(boot)
Perhaps vsmeta.img also needs to be included into the tar file?
No idea how to move on with this subject.
skazi.chris said:
Installed app-debug.apk (patched Magisk) onto the phone.
Downloaded original XEO firmware.
Samfw.com_SM-A217F_XEO_A217FXXU5CUD6_fac.zip
Unzipped it.
Found AP file inside unzipped folder:
AP_A217FXXU5CUD6_CL21209953_QB39896814_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS11.tar.md5
Unpacked the AP file.
Contents:
View attachment 5336407
Decoded the boot.img.lz4 file using LZ4 tool:
View attachment 5336525
Copied boot.img file to the phone internal memory.
View attachment 5336527
Opened Magisk and patched the boot.img file, which created magisk_patched-23001_nmETW.img in the phone Downloads folder
View attachment 5336541View attachment 5336543
Copied patched file (magisk_patched-23001_nmETW.img) from the phone to my laptop - and changed its name to boot.img
Compressed it into boot.tar file using 7zip.
View attachment 5336545
Restarted the phone into DOWNLOAD mode (using SamKey, or adb, or key combinantion, whatever).
Put boot.tar into AP section in ODIN.
Vá para a guia Opções e desative "Reinicialização automática", certifique-se de que "Re-Partição" também esteja desativado.
View attachment 5336551
Aaand ele falha novamente.
View attachment 5336553
E a mensagem no modo DL do telefone diz:
Apenas binários lançados oficialmente podem ser atualizados (boot)
View attachment 5336559
Talvez o vsmeta.img também precise ser incluído no arquivo tar?
Não tenho ideia de como seguir em frente com esse assunto.
Click to expand...
Click to collapse
Edit3: Use MiracleBox to pass the Prenormal you have to Checking, I had this problem on J7NXT, and I made this post to help.
Edit4: Full AP patch on Magisk, and use full patched on Odin.
First with Unlock, go to developer options and activate Unlock Bootloader, restart in download mode, Press the Vol UP button, if reset only, do it again, Download->VolUP Mode, until formatting, In download mode, with all Unlock, go to Odin. Now with the Magisk patched file modified for the A21s, the entire Magisk .tar, you don't need to unpack boot.img.lz4, After this it is normal to start, it will give you an unlocked system alert, just press the Power button to continue, then an Unofficial System warning will appear and just wait A few seconds it starts normally (first boot takes considerable time)
Some tips:
-With V23 use LsPosed to use Xposed framework, Edxposed has infinite log bugs, which causes conflict and slowdown.
-For SatefyNet, Use MagiskHide only apps needed to avoid unnecessary processes, install Universal SatefyNet Fix module, Only this gets through SafetyNet, you don't need to install additional modules for SafetyNet, it will just slow down the system.
For those who use Lucky Patcher:
-Use in LsPosed, and activate it for System Framework and Play Store, you don't need to activate for each app, it will only slow down. Use CorePatch to go through the signatures as Lucky Patcher cannot do this function on Android 11. Use Lucky Patcher with LsPosed as LP Patch's are not compatible with Android 11 But LSPOSED does, so it can work just fine.
For those who use Game Guardian:
-It is best to use a Virtual System, as its functions on Android 11 are limited as it is not 100% compatible.
All I have from my own experience is:
-Avoid redundant modules as much as possible, as they can affect the battery and the System.
To skazi.chris :
Try Unchecking Re-Partition
Jukmisael said:
Edit3: Use MiracleBox to pass the Prenormal you have to Checking, I had this problem on J7NXT, and I made this post to help.
Edit4: Full AP patch on Magisk, and use full patched on Odin.
First with Unlock, go to developer options and activate Unlock Bootloader, restart in download mode, Press the Vol UP button, if reset only, do it again, Download->VolUP Mode, until formatting, In download mode, with all Unlock, go to Odin. Now with the Magisk patched file modified for the A21s, the entire Magisk .tar, you don't need to unpack boot.img.lz4, After this it is normal to start, it will give you an unlocked system alert, just press the Power button to continue, then an Unofficial System warning will appear and just wait A few seconds it starts normally (first boot takes considerable time)
Some tips:
-With V23 use LsPosed to use Xposed framework, Edxposed has infinite log bugs, which causes conflict and slowdown.
-For SatefyNet, Use MagiskHide only apps needed to avoid unnecessary processes, install Universal SatefyNet Fix module, Only this gets through SafetyNet, you don't need to install additional modules for SafetyNet, it will just slow down the system.
For those who use Lucky Patcher:
-Use in LsPosed, and activate it for System Framework and Play Store, you don't need to activate for each app, it will only slow down. Use CorePatch to go through the signatures as Lucky Patcher cannot do this function on Android 11. Use Lucky Patcher with LsPosed as LP Patch's are not compatible with Android 11 But LSPOSED does, so it can work just fine.
For those who use Game Guardian:
-It is best to use a Virtual System, as its functions on Android 11 are limited as it is not 100% compatible.
All I have from my own experience is:
-Avoid redundant modules as much as possible, as they can affect the battery and the System.
Click to expand...
Click to collapse
Patching the entire TAR with patched Magisk did the trick. Thank you very much!
Did this solution also work on the latest SW update?
I tried all, but Stuck at ODIN prism.img
when I use the Magisk tutorial
How to Root Samsung Galaxy A21s using Magisk (Android 11)
Samsung Galaxy A21s is a budget smartphone with great features and decent performance. But there are some limits to what the phone can do without rooting
magiskapp.com
i get the error Only official released binaries are allowed to be flasehd (boot)
Relock/Unlock Bootloader is necessary, then it work with patching the complete AP file
thanks for the tips
DKXC said:
Patched Magisk v23 for A21s (A11/OneUI 3)
Since I've seen and tried installing Magisk via the default instructions from the legend topjohnwu himself, I noticed it does not work at all. The phone
just doesn't even boot into Android at all, and after researching I have seen that this is a very specific problem with the phone itself due to weird implementation from Samsung.
Extremely simplified, apparently there is a conflict with skip-initramfs because of System-as-Root and the A/B system partitioning introduced with Project Treble. I will still have to read more into it.
There are already patched Magisk apps/images for this phone available, but I noticed they are not really in active development (last patched Magisk was still v22), so I pulled the latest Magisk from the official repository and implemented the fix from this pull request on the official repo. They are not interested in accepting the pull request, so we'll have to do our own "Magisk" for the time being.
I will try to update this as much as possible and try to incorporate fixes, user feedback and more. This has been only tested on latest A11 and OneUI 3. I will also start working on TWRP soon.
Since the APK isn't signed yet, please uninstall Magisk Manager if present, and install this one. It will display a warning when installing, but don't worry.
Options to install:
Flash boot.tar from the ZIP in Odin on AP
Install the APK from this thread and patch your own boot image
Click to expand...
Click to collapse
Haha thank you so much bro it worked for M12 too I took the apk file and flashed
Olep84 said:
Did this solution also work on the latest SW update?
I tried all, but Stuck at ODIN prism.img
when I use the Magisk tutorial
How to Root Samsung Galaxy A21s using Magisk (Android 11)
Samsung Galaxy A21s is a budget smartphone with great features and decent performance. But there are some limits to what the phone can do without rooting
magiskapp.com
i get the error Only official released binaries are allowed to be flasehd (boot)
Relock/Unlock Bootloader is necessary, then it work with patching the complete AP file
thanks for the tips
Click to expand...
Click to collapse
Are you sure you unlock Bootloader?
[How To] Unlock Bootloader
How To Unlock Bootloader A21s. *** Disclaimer I am not responsible for any damage you made to your device You have been warned - Go to Settings -> About phone and find your build number. - Tap on your build number 6 times until you see...
forum.xda-developers.com
====#####=======
In relation to the topic, I think that this one will also be abandoned. Eagerly waiting for a developer to look at the A21S/M12 to finally get Magisk working without a patch
Olep84 said:
Did this solution also work on the latest SW update?
I tried all, but Stuck at ODIN prism.img
when I use the Magisk tutorial
How to Root Samsung Galaxy A21s using Magisk (Android 11)
Samsung Galaxy A21s is a budget smartphone with great features and decent performance. But there are some limits to what the phone can do without rooting
magiskapp.com
i get the error Only official released binaries are allowed to be flasehd (boot)
Relock/Unlock Bootloader is necessary, then it work with patching the complete AP file
thanks for the tips
Click to expand...
Click to collapse
Have you used the patched magisk or official one; see official one doesn't work on a21s and m12 i was getting that error before but it solved by using patched one see the first post and download the .apk
I have the SM-A215U. I get the impression this method won't work for me.
I have Developers Options, but do NOT have the OEM option in that menu.
Is there anyway to unlock it without that menu item?
dbreed53 said:
I have the SM-A215U. I get the impression this method won't work for me.
I have Developers Options, but do NOT have the OEM option in that menu.
Is there anyway to unlock it without that menu item?
Click to expand...
Click to collapse
No idea
Hi all.
I updated to the latest version last night, but I lost my root in the process.
I tired to re-root my GP6 yet unsuccessful. Anybody manage to do it?
Thanks.
Tried how? Assuming your bootloader is unlocked, the easiest way is probably:
Unhide Magisk on your phone for now (so PixelFlasher can find it to easily automatically patch your boot.img)
Enable USB debugging if you haven't already
Grab the T2B1 beta factory image (as by T2B1 it sounds like you're on the beta), and PixelFlasher
Use PixelFlasher to extract the boot.img from the factory image (red rocket icon right of the browse bar)
With your phone connected, hit Scan in the top right of PixelFlasher, and select your Pixel in the dropdown
With the extracted boot image extracted, hit "Patch" in PixelFlasher and let it do its thing
With the patched (band-aid icon) boot image selected, hit "Flash Boot" on the right, then let it do its thing again
You can hide Magisk again at this point.
You should have root back after doing all of that. Let me know if I missed anything or if it gets stuck anywhere.
Jaitsu said:
Tried how? Assuming your bootloader is unlocked, the easiest way is probably:
Unhide Magisk on your phone for now (so PixelFlasher can find it to easily automatically patch your boot.img)
Enable USB debugging if you haven't already
Grab the T2B1 beta factory image (as by T2B1 it sounds like you're on the beta), and PixelFlasher
Use PixelFlasher to extract the boot.img from the factory image (red rocket icon right of the browse bar)
With your phone connected, hit Scan in the top right of PixelFlasher, and select your Pixel in the dropdown
With the extracted boot image extracted, hit "Patch" in PixelFlasher and let it do its thing
With the patched (band-aid icon) boot image selected, hit "Flash Boot" on the right, then let it do its thing again
You can hide Magisk again at this point.
You should have root back after doing all of that. Let me know if I missed anything or if it gets stuck anywhere.
Click to expand...
Click to collapse
Have the same Problem, no root on latest Beta,
although following the above steps ( used them in the pasta for wach beta)
Anyone with root on newest Beta?
To be fair, I'm not rooting on the latest beta, I'm still on the standard TQ1A December release - the instructions I gave should apply to any version, but it's possible T2B1 has broken something. When you open the Magisk app, does it show that Magisk isn't installed, even after flashing the patched boot image?
Jaitsu said:
To be fair, I'm not rooting on the latest beta, I'm still on the standard TQ1A December release - the instructions I gave should apply to any version, but it's possible T2B1 has broken something. When you open the Magisk app, does it show that Magisk isn't installed, even after flashing the patched boot image?
Click to expand...
Click to collapse
Yes, same thing happened to me this morning after doing the common steps to retain root after applying an OTA. I then proceeded to patch the boot image using adb but stil no root access.
Edit. It appears that no one is able to root on T2B1, as someone said in the official guide rooting pixel 6 here on XDA
Same issue, tried with PixelFlasher, manual commands, diffrent Magisk versions, but still can't get it work
Strange, and interesting. May be worth filing a bug at the official Magisk github page if anyone is willing to go through the steps necessary to help troubleshoot the problem (doing all of the above with the latest debug version of Magisk, for starters; if you report a bug using any other version the bot will automatically close your issue). I would if I were running the beta or if we had working TWRP so I could backup and restore, but I juuust got my Pixel back to the way I like it on the non-beta after a factory reset.
Jaitsu said:
Strange, and interesting. May be worth filing a bug at the official Magisk github page if anyone is willing to go through the steps necessary to help troubleshoot the problem (doing all of the above with the latest debug version of Magisk, for starters; if you report a bug using any other version the bot will automatically close your issue). I would if I were running the beta or if we had working TWRP so I could backup and restore, but I juuust got my Pixel back to the way I like it on the non-beta after a factory reset.
Click to expand...
Click to collapse
I've already posted on Reddit r\Magisk [Help] Flashed magisk pathed pathed boot image T2B1.221118.006 don't works, but maybe submitting bug would be better. Yea, TWRP would be best but still nothing for A13 (and A12 I think). I remember that there was similar issue in older updates, but Canary made it work, but... not this time
Tried all the possible ways to root the phone, either using fastboot or Pixel Flasher, but no avail. Perhaps someone could successfully do it and tell all of us how
Same issue in Pixel 6a
Guys, see https://github.com/topjohnwu/Magisk/issues/6441.
It looks like Google released corrupted boot image.
To make it work, You need to patch and flash boot image from Pixel 7.
Pixel 6 -> Pixel 7 boot image.
Pixel 6 Pro -> Pixel 7 Pro boot image.
I don't know what about Pixel 6a.
So, should we download the same latest beta for pixel 7 and extract and patch the boot image inside of it?
BAlex9601 said:
So, should we download the same latest beta for pixel 7 and extract and patch the boot image inside of it?
Click to expand...
Click to collapse
Yea, everything else stays the same. Just after upgrade, instead of patching Pixel 6 boot.img, patch the one from Pixel 7 and flash it.
I've used Pixel Flasher for factory update and then in Magisk app I've patched image and then flashed it with fastboot flash boot <patched_boot.img>.
https://twitter.com/i/web/status/1602774339224367104
Yup broken.. should have read the thread.
m_pastuszek said:
Guys, see https://github.com/topjohnwu/Magisk/issues/6441.
It looks like Google released corrupted boot image.
To make it work, You need to patch and flash boot image from Pixel 7.
Pixel 6 -> Pixel 7 boot image.
Pixel 6 Pro -> Pixel 7 Pro boot image.
I don't know what about Pixel 6a.
Click to expand...
Click to collapse
Is this true? I'm downloading it now to test it. Will update later.
UPDATE:
Apparently, flashing Pixel 7 boot.img into Pixel 6 worked like a charm. I get the root back. Thanks guy!
Thanks for the hint regarding boot.img
I'm facing aslo this issue while updating
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' FAILED
Device version-bootloader is 'slider-1.2-9152140'.
Update requires 'slider-1.2-9228550'.
Actually I'm on T1B3.221003.008
Any idea? -> flashed bootloader manually -> solved