Related
[updated]
I consider buying a Moto G8 plus, or a G8 power. A disadvantage of the plus is that it only has Android 9, has not even received 10, and probably will never get 11. Besides, I read that Motorola's in general has a bad reputation regarding updating.
I came across the GSI/Treble topic. I have no experience with it. As I understand, it would enable me to the update to 11 myself. And keep doing that for later versions, or even 10 to start with.
Please correct me if I am wrong.
I found explanations like these.
Android 11 R GSI for Treble Supported Android device
Generic System Image
So my question are.
Is the G8 plus compatible to start with?
Has anyone actually used it already?
What did you do, is there a DSU?
Does it easily work? Did you run into problems?
How much did it influence functionality of your phone? For the Motorola part, GSM, other?
Thanks a lot!
Treble is supported by the G8 Plus, so if you can unlock the bootloader, you should be able to install it.
Unlock Bootloader code is available from Motorola.
Run a couple of GSI on other devices; Android 10.
Reluctant to try moto g8 plus. Carl
It is supposed to support treble project. But I must warn you. I got a G8 plus, unlocked the bootloader, tried to upgrade to Android 10 using a GSI rom and couldn't make it work. Not even with lineage, not even with the stock rom again. It is still semi- bricked without being able to make it work since couple days ago. There is something weird about this phone, all the things that should work and which do actually work on other Android phones , with this, they just don't.
EDIT//
I made it work again flashing all files from stock rom 1 by 1 after locking and unlocking bootloader again.
But i think for a long time i won't be in the mood to try and play with the system of this phone again.
Couchraver said:
It is supposed to support treble project. But I must warn you. I got a G8 plus, unlocked the bootloader, tried to upgrade to Android 10 using a GSI rom and couldn't make it work. Not even with lineage, not even with the stock rom again. It is still semi- bricked without being able to make it work since couple days ago. There is something weird about this phone, all the things that should work and which do actually work on other Android phones , with this, they just don't.
EDIT//
I made it work again flashing all files from stock rom 1 by 1 after locking and unlocking bootloader again.
But i think for a long time i won't be in the mood to try and play with the system of this phone again.
Click to expand...
Click to collapse
I'm in the same situation. The most weird thing was that the GSI ROM from android official developers website worked. (but that ROM is just for testing apps on a simulator or something like that)
Even TWRP is not working 100%.. It boots fine into recovery but touch stop working after flashing into boot partition.
so I flashed back to stock rom and is running again.
I just managed to install the GSI from phhusson/treble_experimentations, but I had to flash vbmeta.
ecobos said:
I just managed to install the GSI from phhusson/treble_experimentations, but I had to flash vbmeta.
Click to expand...
Click to collapse
if the GSI rom served you? could you give screenshots? and how did he do it?
I have gotten lineage os 17.1 successfully working on my g8 plus with the help of a unofficial build from Andy Yan I think. There was also a Android 10 gsi build but it wasn't as great as lineage os so I flashed lineage and it booted right up first try successfully working with root and mauronofrios build of twrp working so you get all things working with the g8 plus but nothing has released officially. Hope this helps!
SnowTalker said:
I have gotten lineage os 17.1 successfully working on my g8 plus with the help of a unofficial build from Andy Yan I think. There was also a Android 10 gsi build but it wasn't as great as lineage os so I flashed lineage and it booted right up first try successfully working with root and mauronofrios build of twrp working so you get all things working with the g8 plus but nothing has released officially. Hope this helps!
Click to expand...
Click to collapse
Could you make a tutorial to be able to install it successfully? Thank you
chevy42 said:
Could you make a tutorial to be able to install it successfully? Thank you
Click to expand...
Click to collapse
Yeah sure. Go to https://www.google.com/url?sa=t&sou...FjAAegQIBRAB&usg=AOvVaw26jTQFwtpMBNoOek36E-3g
And make sure you get the latest twrp build and download it, after that put the build on your PC and your phone. Then on your PC open a powershell or command prompt on your desktop (shift plus right click) put your phone in bootloader mode and on your PC do the following command: "fastboot boot name.img" name is the name on the build btw and if successful you should boot into twrp, after that click install and choose the twrp build img and flash it. After that reboot your phone and go to magisk manager and download the zip for root and go back to twrp and flash that and then reboot and you now have root.
As for custom roms just follow this tutorial I found from
https://www.google.com/url?sa=t&sou...Vaw1DjEbfH6672uJRqdf82EiX&cshid=1592440507846
I hoped this helped, if it didn't you can ask me about it
SnowTalker said:
Yeah sure. Go to https://www.google.com/url?sa=t&sou...FjAAegQIBRAB&usg=AOvVaw26jTQFwtpMBNoOek36E-3g
And make sure you get the latest twrp build and download it, after that put the build on your PC and your phone. Then on your PC open a powershell or command prompt on your desktop (shift plus right click) put your phone in bootloader mode and on your PC do the following command: "fastboot boot name.img" name is the name on the build btw and if successful you should boot into twrp, after that click install and choose the twrp build img and flash it. After that reboot your phone and go to magisk manager and download the zip for root and go back to twrp and flash that and then reboot and you now have root.
As for custom roms just follow this tutorial I found from
https://www.google.com/url?sa=t&sou...Vaw1DjEbfH6672uJRqdf82EiX&cshid=1592440507846
I hoped this helped, if it didn't you can ask me about it
Click to expand...
Click to collapse
I'm scared to jump my phone haha, I wish there was a video tutorial to do it better.
chevy42 said:
I'm scared to jump my phone haha, I wish there was a video tutorial to do it better.
Click to expand...
Click to collapse
Unless you do something really stupid with twrp or root, it really wasn't a bother, honestly it was pretty easy but it took me a while to find things as this was my first phone to root successfully... But it's up to you if you want to risk it. imo it isn't bad to try something new either
SnowTalker said:
Unless you do something really stupid with twrp or root, it really wasn't a bother, honestly it was pretty easy but it took me a while to find things as this was my first phone to root successfully... But it's up to you if you want to risk it. imo it isn't bad to try something new either
Click to expand...
Click to collapse
How about the rom? Is it faster than the stock rom? What bugs does the rom have?
chevy42 said:
How about the rom? Is it faster than the stock rom? What bugs does the rom have?
Click to expand...
Click to collapse
The ROM plus flashed gapps (google apps) uses less ram then the stock ROM but it takes away motos core features including the double chop to turn the flashlight on and other things. Plus you can't use the ultra wide lense anymore and you would have to have a aftermarket camera (I use a google camera port) there is a lot of wins and losses but in the end I think lineage os is better than stock for the customization imo.
---------- Post added at 12:57 AM ---------- Previous post was at 12:55 AM ----------
chevy42 said:
How about the rom? Is it faster than the stock rom? What bugs does the rom have?
Click to expand...
Click to collapse
Oh and I forgot, I have not experienced any bugs other than the system UI stopping randomly (very rare) so it's a really well bug free ROM (in my use).
Robert_X said:
[updated]
I consider buying a Moto G8 plus, or a G8 power. A disadvantage of the plus is that it only has Android 9, has not even received 10, and probably will never get 11. Besides, I read that Motorola's in general has a bad reputation regarding updating.
I came across the GSI/Treble topic. I have no experience with it. As I understand, it would enable me to the update to 11 myself. And keep doing that for later versions, or even 10 to start with.
Please correct me if I am wrong.
I found explanations like these.
Android 11 R GSI for Treble Supported Android device
Generic System Image
So my question are.
Is the G8 plus compatible to start with?
Has anyone actually used it already?
What did you do, is there a DSU?
Does it easily work? Did you run into problems?
How much did it influence functionality of your phone? For the Motorola part, GSM, other?
Thanks a lot!
Click to expand...
Click to collapse
I personally don't recommend you to buy a Motorola. since Lenovo bought Motorola they are not the same and they all have connectivity problems. In addition, the moto g8 plus has problems with wifi, Bluetooth and screen burn.
felixp_ said:
I personally don't recommend you to buy a Motorola. since Lenovo bought Motorola they are not the same and they all have connectivity problems. In addition, the moto g8 plus has problems with wifi, Bluetooth and screen burn.
Click to expand...
Click to collapse
I haven't had any problems with WiFi or Bluetooth, I haven't got a screen burn in yet (knock on wood) but I think you got a defected device. Lenovo isn't bad with they're new devices I think they are ok although I wasn't around when it was just Motorola
chevy42 said:
if the GSI rom served you? could you give screenshots? and how did he do it?
Click to expand...
Click to collapse
Sure, here's one
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
One gotcha is that Bluetooth audio didn't quite work. I had to disable a2dp offloading and disable audio effects from the treble config to get them to work.
ecobos said:
Sure, here's one
One gotcha is that Bluetooth audio didn't quite work. I had to disable a2dp offloading and disable audio effects from the treble config to get them to work.
Click to expand...
Click to collapse
How is the performance of the phone with that rom?
ecobos said:
Sure, here's one
One gotcha is that Bluetooth audio didn't quite work. I had to disable a2dp offloading and disable audio effects from the treble config to get them to work.
Click to expand...
Click to collapse
Which GSI did you manage to install?
chevy42 said:
How is the performance of the phone with that rom?
Click to expand...
Click to collapse
It seems pretty decent, haven't had any perf issues. My brother has the same phone but with the stock ROM and perf seems similar. Anything in particular you were looking for?
merlinolillo said:
Which GSI did you manage to install?
Click to expand...
Click to collapse
system-quack-arm64-ab-floss.img.xz from phhusson/treble_experimentations (sorry, I'd link but I'm a newb here so I still can't post outside links ).
I ended up installing google play services in the end because otherwise a 2FA app I need for work, plus a bank app would refuse to work, sadly. I used the "pico" variant of opengapps.
Any one working on a twrp recovery for infinix smart 5 x657?
I need of it.thanks
I
Gentleman101 said:
Any one working on a twrp recovery for infinix smart 5 x657?
I need of it.thanks
Click to expand...
Click to collapse
I have been searching for it's twrp but have not been able to get it so incase you do inform me please
Hello, I've noticed that the [twrp of infinix hot 2 ](https://eu.dl.twrp.me/d5110/) does work on smart infinix 5 X657C .. Try it, It might work.
I couldn't get root access yet using Magisk, but this is literally my first time doing this so there's a good chance I'm doing something wrong.
actually after trying to flash the image I'm now stuck in an infinite looping boot (which is bad because this is my mom's phone and now I'm in trouble).
Gentleman101 said:
Any one working on a twrp recovery for infinix smart 5 x657?
I need of it.thanks
Click to expand...
Click to collapse
Where you able to root the phone in the first place? If you were, you shouldn't have so much need for TWRP. You should be able to flash GSIs from fastboot itself.
Traditional-Wind said:
actually after trying to flash the image I'm now stuck in an infinite looping boot (which is bad because this is my mom's phone and now I'm in trouble).
Click to expand...
Click to collapse
Trying to flash what image: the stock image of or custom one?
Traditional-Wind said:
Hello, I've noticed that the [twrp of infinix hot 2 ](https://eu.dl.twrp.me/d5110/) does work on smart infinix 5 X657C .. Try it, It might work.
I couldn't get root access yet using Magisk, but this is literally my first time doing this so there's a good chance I'm doing something wrong.
Click to expand...
Click to collapse
is x657 the same as x657C? if not, whats the difference
VicKrypt said:
Trying to flash what image: the stock image of or custom one?
Click to expand...
Click to collapse
There is no custom images for this phone. In fact, the firmware isn't released. So you can't nether root it nor flash a custom ROM. As I mentioned, I heard that using a similar enough twrp image (a custom one, and I mentioned the source) wasn't a success and resulted in a bricked phone. The goad was to acquire root access on the phone.
The reason that lead me to do it was because `fastboot boot` did, in fact, work. but didn't give me root access, so I thought maybe `fastboot flash` will work.
MrKonic said:
is x657 the same as x657C? if not, whats the difference
Click to expand...
Click to collapse
according to what I found online (i.e. https://www.mobilesum.com/mobile/infinix-smart-5) the only difference is the camera. IDK if that will affect something related to the firmware or the boot image (If your intention is the same as mine, which is to root the phone).
But I assume (and I hope) they're both the same on every other level (nothing else is mentioned so if there's any other differences, only the company knows).
Something to note. The phone asked me to send a bug report twice. And gave me the share dialogue (meaning that I can send it to whomever I choose). I sent them to myself using whatsapp. And now, I'm saving a copy of 2 bug report that I assume they should be sent to the company (seems like the bug report was produced by the system). AFAIK it's useless, but just in case. Here's the output of `tree` on linux. If someone thinks there's something useful there. I'll share it.
bt
Traditional-Wind said:
according to what I found online (i.e. https://www.mobilesum.com/mobile/infinix-smart-5) the only difference is the camera. IDK if that will affect something related to the firmware or the boot image (If your intention is the same as mine, which is to root the phone).
But I assume (and I hope) they're both the same on every other level (nothing else is mentioned so if there's any other differences, only the company knows).
Click to expand...
Click to collapse
btw, have you rooted yours?
There certainly are not any custom ROMs f
Traditional-Wind said:
There is no custom images for this phone. In fact, the firmware isn't released. So you can't nether root it nor flash a custom ROM. As I mentioned, I heard that using a similar enough twrp image (a custom one, and I mentioned the source) wasn't a success and resulted in a bricked phone. The goad was to acquire root access on the phone.
The reason that lead me to do it was because `fastboot boot` did, in fact, work. but didn't give me root access, so I thought maybe `fastboot flash` will work.
Click to expand...
Click to collapse
or the phone (given how unpopular it is), but I'm talking about Generic System Images. Using fastbootd and disabling AVB I believe it should be possible to change the OS and even root it!
VicKrypt said:
There certainly are not any custom ROMs f
or the phone (given how unpopular it is), but I'm talking about Generic System Images. Using fastbootd and disabling AVB I believe it should be possible to change the OS and even root it!
Click to expand...
Click to collapse
please elaborate this simply for the newbies present. including mineself
VicKrypt said:
There certainly are not any custom ROMs f
or the phone (given how unpopular it is), but I'm talking about Generic System Images. Using fastbootd and disabling AVB I believe it should be possible to change the OS and even root it!
Click to expand...
Click to collapse
I just realized that infinix smart 5 has a flashable stock ROM available online. I guess I didn't search well enough last time. Or maybe it wasn't available back then. So I bricked a phone for nothing unfortunately.
I couldn't find any (back when I wanted to do it) so I grabed a TWRP image of infinix hot 2 (because they have a similar CPU, and they're the same brand) and I tried fastboot boot instead of fastboot flash (just to try it out before flashing) it worked, but when I flashed it. The phone was bricked (beyond repair).
MrKonic said:
please elaborate this simply for the newbies present. including mineself
Click to expand...
Click to collapse
He suggested to do the same as this guide
[Guide] Unlocking Bootloader and Disabling VerifiedBoot
/* Your warranty is now void (or isn't ? who am I to judge ?) */ Finally, we got a shiny DeepTesting.apk that compatible with Realme 6 Pro. Thanks to barakcodam for leaking it, and Rizezky for providing a Google Drive mirror of it. Disclaimer...
forum.xda-developers.com
just with a different phone. But I assume you don't really have to care about it.
Instead, if you want to root the phone. Then here's a good video about how to do it.
When you need to download the ROM, you can get it from this link which I wish I found earlier :'(
Infinix Smart 5 X657/X657B Firmware Flash File (Stock ROM)
Android always opens the door to various possibilities such as flashing custom ROM or kernel or APK modding etc. So if you have accidentally bricked your
www.getdroidtips.com
I assume if you follow the video and use the stock ROM. You'll have a rooted infinix smart 5 by the end of the day.
Good luck (and please let me know if it worked, I'd be eager to know).
Traditional-Wind said:
There is no custom images for this phone. In fact, the firmware isn't released. So you can't nether root it nor flash a custom ROM. As I mentioned, I heard that using a similar enough twrp image (a custom one, and I mentioned the source) wasn't a success and resulted in a bricked phone. The goad was to acquire root access on the phone.
The reason that lead me to do it was because `fastboot boot` did, in fact, work. but didn't give me root access, so I thought maybe `fastboot flash` will work.
Click to expand...
Click to collapse
I've seen the firmware on a couple of sites bro
MrKonic said:
please elaborate this simply for the newbies present. including mineself
Click to expand...
Click to collapse
Talking about root, with the correct firmware (and techniques) there shouldn't be any reason why the phone would be non-root-able. There's no official TWRP for the device and I haven't seen anyone port one for it, so going the TWRP way would most likely cause a brick. But after patching the boot.img from the correct firmware and disabling AVB by flashing the VBMeta (which most people ignore), patched_boot should be flashable in fastbootd if not in fastboot.
Talking about custom ROMs, there are no custom ROMs for the device (just like there aren't for the Infinix Hot 8, Smart 3 Plus, Hot 10 Play, e.t.c), but a lot of people have successfully flashed GSIs. Generic System Images are pure AOSP code that run on Trebllized devices. You can do more research on GSIs yourself.
Traditional-Wind said:
He suggested to do the same as this guide
[Guide] Unlocking Bootloader and Disabling VerifiedBoot
/* Your warranty is now void (or isn't ? who am I to judge ?) */ Finally, we got a shiny DeepTesting.apk that compatible with Realme 6 Pro. Thanks to barakcodam for leaking it, and Rizezky for providing a Google Drive mirror of it. Disclaimer...
forum.xda-developers.com
just with a different phone. But I assume you don't really have to care about it.
Instead, if you want to root the phone. Then here's a good video about how to do it.
When you need to download the ROM, you can get it from this link which I wish I found earlier :'(
Infinix Smart 5 X657/X657B Firmware Flash File (Stock ROM)
Android always opens the door to various possibilities such as flashing custom ROM or kernel or APK modding etc. So if you have accidentally bricked your
www.getdroidtips.com
I assume if you follow the video and use the stock ROM. You'll have a rooted infinix smart 5 by the end of the day.
Good luck (and please let me know if it worked, I'd be eager to know).
Click to expand...
Click to collapse
I did not suggest you do exactly what was done in that video. The method may vary slightly for MTK devices. It'd be more similar to this (for rooting)
https://www.google.com/url?sa=t&sou...o7QBegQIBRAB&usg=AOvVaw1dN51TuGa6a9LA07Nota-q
For flashing GSIs it'd be similar to this
How to install GSIs on dynamic partition devices
Traditional-Wind said:
I just realized that infinix smart 5 has a flashable stock ROM available online. I guess I didn't search well enough last time. Or maybe it wasn't available back then. So I bricked a phone for nothing unfortunately.
I couldn't find any (back when I wanted to do it) so I grabed a TWRP image of infinix hot 2 (because they have a similar CPU, and they're the same brand) and I tried fastboot boot instead of fastboot flash (just to try it out before flashing) it worked, but when I flashed it. The phone was bricked (beyond repair).
Click to expand...
Click to collapse
'Bricked beyond repair'? A phone is hard-bricked only if it doesn't turn on at all when plugged in, and doesn't show up on the PC or show any sign of life. Else, you'd still be able to recover it.
Alright guys I finally flashed a GSI on my Infinix Smart 5 X657C yesterday. It's Lineage OS 19 (a64 bvS), Android 12 (I'd been on XOS 6.2 Android 10 previously). I got screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
to prove that it's possible to root the device, if done correctly. I'm yet to flash phh-Magisk and orange-state disabler anyway (I wasn't sure A12 would even work in the first place)
VicKrypt said:
Alright guys I finally flashed a GSI on my Infinix Smart 5 X657C yesterday. It's Lineage OS 19 (a64 bvS), Android 12 (I'd been on XOS 6.2 Android 10 previously). I got screenshots
View attachment 5642989 57c View attachment 5642991 View attachment 5642999 View attachment 5643001 View attachment 5643003 View attachment 5643005
to prove that it's possible to root the device, if done correctly. I'm yet to flash phh-Magisk and orange-state disabler anyway (I wasn't sure A12 would even work in the first place)
Click to expand...
Click to collapse
what's the process please
can you write down the steps
but mine isn't X657c
Dear XDA Guru / Expert,
Good Day. I need help urgently here.
2015 i purchase Mi 4i mobile device and took many nice photo but forgot transfer out.
2021 last month i open this Mi 4i would like to download the file , unfortunately this device perform Auto upgrade.
Half way while auto upgrade , this mobile running out of battery.
After reopen , it keep appearing the Mi Logo.
I check many website mentioned i need perform FASTBOOT to Flash the ROM.
I checked also the bootloader is not lock.
However i did perform the Flash the ROM with lastest ROM / Factory ROM.
Please give me some advise what i should do in order for me can go back to normal ?
So that i can download the photo out from this mobile ?
Appreciate & welcome your reply.
Thank you
ak9999 said:
Dear XDA Guru / Expert,
Good Day. I need help urgently here.
2015 i purchase Mi 4i mobile device and took many nice photo but forgot transfer out.
2021 last month i open this Mi 4i would like to download the file , unfortunately this device perform Auto upgrade.
Half way while auto upgrade , this mobile running out of battery.
After reopen , it keep appearing the Mi Logo.
I check many website mentioned i need perform FASTBOOT to Flash the ROM.
I checked also the bootloader is not lock.
However i did perform the Flash the ROM with lastest ROM / Factory ROM.
Please give me some advise what i should do in order for me can go back to normal ?
So that i can download the photo out from this mobile ?
Appreciate & welcome your reply.
Thank you
Click to expand...
Click to collapse
Probably when you flashed the firmware through fastboot you have overwritten the files in there. As your bootloader is unlocked the better would be to flash a custom recovery on it and then pull all the files you want.
SubwayChamp said:
Probably when you flashed the firmware through fastboot you have overwritten the files in there. As your bootloader is unlocked the better would be to flash a custom recovery on it and then pull all the files you want.
Click to expand...
Click to collapse
Hi SubwayChamp,
Good Day. Yea - i do agree your point of view, First of all thanks for your reply.
I flash my ROM previously on this device too , after complete the flash it working well.
Before i flash the ROM , the device perform auto upgrade but half way no battery & it force to shut down , after reopen it stuck at MI logo so without any choice i only choose to flash the ROM.
Actually i am not so expert on android ROM, by the way what is different between custom recovery vs those i got from XiaoMi official ROM ?
Mind tell me more on how to fix it please ?
Thank you
ak9999 said:
Hi SubwayChamp,
Good Day. Yea - i do agree your point of view, First of all thanks for your reply.
I flash my ROM previously on this device too , after complete the flash it working well.
Before i flash the ROM , the device perform auto upgrade but half way no battery & it force to shut down , after reopen it stuck at MI logo so without any choice i only choose to flash the ROM.
Actually i am not so expert on android ROM, by the way what is different between custom recovery vs those i got from XiaoMi official ROM ?
Mind tell me more on how to fix it please ?
Thank you
Click to expand...
Click to collapse
To know which direction to take, first we have to know how exactly you flashed the ROM you mentioned, which ROM was and through which tool.
Hi SubwayChamp,
Good Day. thanks for your reply.
I using official xiaomi - MiFlash as the tools to reflash the ROM.
ROM that i use - ferrari_global_images_6.7.5_20160523.0000.23_5.0_global
You may find attached Flash Log as reference.
Hope you can give me some good idea to resolve this issue.
Thank you
ak9999 said:
Hi SubwayChamp,
Good Day. thanks for your reply.
I using official xiaomi - MiFlash as the tools to reflash the ROM.
ROM that i use - ferrari_global_images_6.7.5_20160523.0000.23_5.0_global
You may find attached Flash Log as reference.
Hope you can give me some good idea to resolve this issue.
Thank you
Click to expand...
Click to collapse
I saw in your other thread flashing process took only 94s, if it is the case then it's not flashing properly.
From the three options that's above on the tool, don't remember to use only the option format data, not relock bootloader or try to keep your data. (picture of reference)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And also in case you used fastboot to flash your device, I recommend you try through EDL mode
SubwayChamp said:
I saw in your other thread flashing process took only 94s, if it is the case then it's not flashing properly.
From the three options that's above on the tool, don't remember to use only the option format data, not relock bootloader or try to keep your data. (picture of reference)
View attachment 5482635
And also in case you used fastboot to flash your device, I recommend you try through EDL mode
Click to expand...
Click to collapse
Hi SubwayChamp,
Thanks for prompt reply.
I think what you mentioned make sense - it's not flashing properly.
My Question
================
1) Related with Option to Flash
I am using save user data option at this moment.
But the option you suggest clean all & Lock will clear all my existing Picture or File from this mobile right?
2) Related your recommendation EDL mode
I don't think i able go others mode except Fastboot now because whenever my mobile open it's in Fastboot only.
Sorry to say actually study computing but i am newbie in all these , i don't even know what's EDL mode.
Thanks for your input.
ak9999 said:
Hi SubwayChamp,
Thanks for prompt reply.
I think what you mentioned make sense - it's not flashing properly.
My Question
================
1) Related with Option to Flash
I am using save user data option at this moment.
But the option you suggest clean all & Lock will clear all my existing Picture or File from this mobile right?
Click to expand...
Click to collapse
Not the option Clean all & Lock because this will lead your hopes even far distant, a locked device with Qualcomm only can be flashed through EDL mode, fastboot mode will be impossible if you relock bootloader. I suggested using the option Format data because WHEN the flashing is successful one of the things that avoid the device to boot normally is the old data that it is still there. Anyway, this won't make difference while you don't get the tool to flash properly.
ak9999 said:
2) Related your recommendation EDL mode
I don't think i able go others mode except Fastboot now because whenever my mobile open it's in Fastboot only.
Click to expand...
Click to collapse
Some Xiaomi devices, while bootloader is unlocked can be sent to EDL mode using hardware buttons, with device off pressing the both volume buttons at exactly the same time you connect your device to PC, in case this method doesn't work you should need to use "the test point method" is a way slightly difficult to get it but... to flash through EDL mode you need to install the Qualcomm 9008 USB drivers https://www.thecustomdroid.com/qualcomm-hs-usb-qdloader-9008-drivers/
And if you want to keep trying in fastboot mode, you could switch to other Mi Flash tool versions if it makes difference. Always is better to move all your firmware to the same directory where Mi Flash tool is, also avoid all the spaces in the path/name.
ak9999 said:
Sorry to say actually study computing but i am newbie in all these , i don't even know what's EDL mode.
Thanks for your input.
Click to expand...
Click to collapse
{Mod edit: Quoted post has been deleted - Oswald Boelcke}
What does this mean? You only quoted my post.
{Mod edit: Quoted post has been deleted - Oswald Boelcke}
Actually i din't not flash any file at first, it stuck at MI Logo due to some auto upgrade , i not sure it's MIUI Upgrade or Android Upgrade but i saw the word Android ......too bad half way due to my batery issue.......when i reopen MI Logo keep appear so i wish reflash the ROM able to help but it seem.....not really....
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile variants, the fastboot scripts are just bricking them. Well I found a fix for these issues. Those who just want to convert can skip the MSM Tool process and get right to the conversion process as long as they're already running OOS11.
First thing is first, you need to be on OOS11. If you have a T-Mobile variant and you have flashed it with India firmware, you have to use a modded T-Mobile MSM: https://forum.xda-developers.com/t/...ariant-flashing-as-well.4454357/post-87050821
If you have a T-Mobile variant that hasn't used the Indian 9 Pro MSM Tool, is on OOS12, and you're just wanting to convert, you need this tool: https://forum.xda-developers.com/t/oneplus-9-11-2-22-2-t-mobile-msm-download-tool.4276119/
If you have a global variant or a global variant that has been flashed with Indian firmware, you can use this MSM (choose O2 for global or India for India in the Target dropdown, check Sha256, uncheck use lite firehose, it's a multi-target MSM Tool): https://mega.nz/file/ZWtGxTSb#UZ6aSOR2UTYrCao2fQNJ1IN5LSxPNBOxzel1kihnnJs
If you don't know how to use the MSM Tool, there are other guides around here, that's outside of the scope of this post.
Once you are back on OOS11, unlock the bootloader. We also need USB debugging enabled.
Now we need a tool called Fastboot Enhance. This wonderful tool allows you to directly flash OTAs from fastbootd and it doesn't have the same brick risk that flashing with fastboot scripts does.
Download it and unzip it somewhere.
Next we need the OOS11 global downgrade package (or whatever region you are wanting to switch to, global is recommended for T-Mobile variants) from here: https://forum.xda-developers.com/t/oneplus-9-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4254579/
Fire up command prompt in the folder you have your platform tools and run:
adb reboot fastboot (if you do adb reboot bootloader you will then need to type fastboot reboot fastboot to get to fastbootd)
This will take you into fastbootd. It will have a screen that has three different languages to choose from on it. Go ahead and fire up Fastboot Enhance now.
It may take a few seconds for the app to recognize the device but when you see it in the list, double-click it to get to the main screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Check that it says that the device is in fastbootd. Now we just need to click Flash Payload.bin and choose the OTA we downloaded earlier (we don't even need to extract the zip, the app does that for us). If it pops up with an unrecognized partitions error, you're either not in fastbootd, you didn't MSM back to stock (you cannot do this with a custom recovery), or you grabbed an OOS12 OTA. Do not continue and check that everything is correct otherwise you will brick and have to start all over with the MSM Tool. Likewise, if it pops up an alert about cow partitions, don't continue. Go to the partitions screen and search for cow and delete them all.
Once it's done, boot the device, factory reset it in the settings (this is mandatory as Fastboot Enhance does not erase the device like a normal downgrade would do and this can cause problems), set it back up, and then do the OTA process to get back to where you want to go.
Hey bud. So I ended up having too india again. After flashing nameless, it locked up completely. I followed along, but maybe I made a mistake around this point?
Once I was able to boot into India, i just used another msmtoolkit, this successfully converted my Pro to the proper OP 9 5g (the cutout for the cam was aligned so it worked) and i was now on 11.2.10.10
i then let the phone just OTA itself to Android 12.1 c.48
this is when i attempted to get into the latest nameless ROM that requires us to go from OOS 11 based system for the tom to A12.
did i mess up? Should i have flashed 12.1 again?
because the additional flash requirements were fairly straight forward. .
i unlocked the bootloader and then re-enabled /adb debugging the 12.1 and rebooted to bootloader
i flashed the 3 images i extracted from the payload of the latest 12.1 nameless zip and flashed them
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
Click to expand...
Click to collapse
while in the same fastboot, i selected recovery boot. i was in the lineage recovery system, this is where i formatted and sideloaded in the same session
when i rebooted i was qualcom killed. could sitll fastboot but nothing would take so i just started over. i am now on my 2nd toolkit flash (india-pro to non-pro global.
i may just stick with the latest release that doesnt require 12. it doesnt help that im 2 days no sleep (unrelated but not helping) but even saying that, i feel i had most of what was required done, but im a big dummy so who knows
youre knowledge is sexy
THANK YOU SIR, true gentleman. Your post I guess was the only one convincing enough that it was finally brushed through the beta testing phase enough that it would be worth trying. No real risk here considering its just using that awesome tool you mentioned in the post, which i've never heard of. will be using for now on. Dunno about any testing with this method so i thought i would owe the community my post. i saw the sahara error post not too long ago talking about a fix with no testing yet xD that made me laugh honestly. But yeah my phone is now converted global through payload.bin flash in fastbootd. Tmo Variant had me & my girls phone networked unlocked through the one guy that was doing it for free on here a while back.. then applied for unlock code and did it officially, never tried to convert due to brick concerns, so i had the easy route through the methods involved in this post, considering i was still on oos 11 with bootloader unlocked when reading this. anyways, i think its safe to say its fixed pretty hyped to flash roms now and not get bootlooped and excited to see where this variant is gonna go! thanks again mate.
applyscience said:
Hey bud. So I ended up having too india again. After flashing nameless, it locked up completely. I followed along, but maybe I made a mistake around this point?
Once I was able to boot into India, i just used another msmtoolkit, this successfully converted my Pro to the proper OP 9 5g (the cutout for the cam was aligned so it worked) and i was now on 11.2.10.10
i then let the phone just OTA itself to Android 12.1 c.48
this is when i attempted to get into the latest nameless ROM that requires us to go from OOS 11 based system for the tom to A12.
did i mess up? Should i have flashed 12.1 again?
because the additional flash requirements were fairly straight forward. .
i unlocked the bootloader and then re-enabled /adb debugging the 12.1 and rebooted to bootloader
i flashed the 3 images i extracted from the payload of the latest 12.1 nameless zip and flashed them
while in the same fastboot, i selected recovery boot. i was in the lineage recovery system, this is where i formatted and sideloaded in the same session
when i rebooted i was qualcom killed. could sitll fastboot but nothing would take so i just started over. i am now on my 2nd toolkit flash (india-pro to non-pro global.
i may just stick with the latest release that doesnt require 12. it doesnt help that im 2 days no sleep (unrelated but not helping) but even saying that, i feel i had most of what was required done, but im a big dummy so who knows
youre knowledge is sexy
Click to expand...
Click to collapse
Did you use the copy partitions zip? You will brick if you don't do that after a MSM.
Process is:
MSM
Upgrade to C.48
Extract boot, dtbo, and vendor_boot from ROM
Fastboot flash dtbo, vendor_boot, and boot in that order
Reboot to recovery
Factory reset
Run copy partitions script
Reboot recovery
Flash ROM
Reboot
It shouldn't brick if you follow that process exactly.
zacattackkc said:
THANK YOU SIR, true gentleman. Your post I guess was the only one convincing enough that it was finally brushed through the beta testing phase enough that it would be worth trying. No real risk here considering its just using that awesome tool you mentioned in the post, which i've never heard of. will be using for now on. Dunno about any testing with this method so i thought i would owe the community my post. i saw the sahara error post not too long ago talking about a fix with no testing yet xD that made me laugh honestly. But yeah my phone is now converted global through payload.bin flash in fastbootd. Tmo Variant had me & my girls phone networked unlocked through the one guy that was doing it for free on here a while back.. then applied for unlock code and did it officially, never tried to convert due to brick concerns, so i had the easy route through the methods involved in this post, considering i was still on oos 11 with bootloader unlocked when reading this. anyways, i think its safe to say its fixed pretty hyped to flash roms now and not get bootlooped and excited to see where this variant is gonna go! thanks again mate.
Click to expand...
Click to collapse
Awesome, glad that it worked for you! There were two other testers before you as well as myself that have confirmed this method works, I guess I should have put that in the post. Thanks for being a guinea pig
question; so now that i did it through advanced boot app, does that mean my phone is officially seen as a global one? can i use global regular msm? can i use fastboot payload files for global, ect?
zacattackkc said:
question; so now that i did it through advanced boot app, does that mean my phone is officially seen as a global one? can i use global regular msm? can i use fastboot payload files for global, ect?
Click to expand...
Click to collapse
So your phone will be seen as global by OTAs but not the MSM. You would have to use a modded MSM Tool that flashes global firmware while targeting your device model.
EtherealRemnant said:
So your phone will be seen as global by OTAs but not the MSM. You would have to use a modded MSM Tool that flashes global firmware while targeting your device model.
Click to expand...
Click to collapse
damn.. that seems to be the culprit of everyone's hard brick.. so what about fastboot flashing oem software for global? I'm guessing that's not a problem because otas are of similar format, but just in a smaller package because it's adding only the updated parts instead of the full ROM.. and is this enhanced fastboot app an alternative to using msmtool and then unlocking bootloader and then flashing custom roms? kinda seems like it would be. and as a matter of fact after using the enhanced fastboot tool I went ahead and put it into fastbootd and flashed payload and it wouldn't boot at first. The app itself gave me an error regarding some cow partitions (really strange and very new concept for me) and told me that I could possibly fix everything if I deleted the cow partitions so I did and then formatted data and it booted into nameless AOSP. This might be the new way to flash custom roms due to the simple fact that it's way quicker than having to use NSM tool and then unlock bootloader and then do all the intricate flashing custom ROM parts. Just put in a fast boot d and flash just always have to make sure you format data afterwards to decrypt. This hasn't been fully tested at least not that I'm aware of
zacattackkc said:
damn.. that seems to be the culprit of everyone's hard brick.. so what about fastboot flashing oem software for global? I'm guessing that's not a problem because otas are of similar format, but just in a smaller package because it's adding only the updated parts instead of the full ROM.. and is this enhanced fastboot app an alternative to using msmtool and then unlocking bootloader and then flashing custom roms? kinda seems like it would be. and as a matter of fact after using the enhanced fastboot tool I went ahead and put it into fastbootd and flashed payload and it wouldn't boot at first. The app itself gave me an error regarding some cow partitions (really strange and very new concept for me) and told me that I could possibly fix everything if I deleted the cow partitions so I did and then formatted data and it booted into nameless AOSP. This might be the new way to flash custom roms due to the simple fact that it's way quicker than having to use NSM tool and then unlock bootloader and then do all the intricate flashing custom ROM parts. Just put in a fast boot d and flash just always have to make sure you format data afterwards to decrypt. This hasn't been fully tested at least not that I'm aware of
Click to expand...
Click to collapse
So honestly I haven't wanted to mess with it too much because it's such a chore to MSM and set everything back up. I can confirm the conversion works as long as you don't ignore any errors and continue (as you found out yourself with the cow files) but as for switching between custom ROMs, fastbootd is part of the custom recovery that we use to flash these ROMs and I don't know if it's possible to get a full flash using that custom recovery. When I tried to use an OOS12 OTA to skip having to use the MSM Tool to go back to stock, I got a partitions error and it rebooted to fastboot. Upon trying to flash the stock boot, dtbo, and vendor_boot, it bricked. I decided it was more important to figure out how to help people with their initial conversion process and I was frustrated because this particular brick was refusing to go into edl until I putzed around with the phone for a few minutes and managed to get it. It just isn't worth me possibly having an unrecoverable brick so I didn't mess with it any further.
In theory though, moving between custom ROMs using the same base firmware should be fine. People will have to test and find out.
EtherealRemnant said:
So honestly I haven't wanted to mess with it too much because it's such a chore to MSM and set everything back up. I can confirm the conversion works as long as you don't ignore any errors and continue (as you found out yourself with the cow files) but as for switching between custom ROMs, fastbootd is part of the custom recovery that we use to flash these ROMs and I don't know if it's possible to get a full flash using that custom recovery. When I tried to use an OOS12 OTA to skip having to use the MSM Tool to go back to stock, I got a partitions error and it rebooted to fastboot. Upon trying to flash the stock boot, dtbo, and vendor_boot, it bricked. I decided it was more important to figure out how to help people with their initial conversion process and I was frustrated because this particular brick was refusing to go into edl until I putzed around with the phone for a few minutes and managed to get it. It just isn't worth me possibly having an unrecoverable brick so I didn't mess with it any further.
In theory though, moving between custom ROMs using the same base firmware should be fine. People will have to test and find out.
Click to expand...
Click to collapse
ive been playing with them for the last 20 hours almost nonstop. im back to being tmobile but no msm tool (yet) will work with it. I tried almost every tmobile msm and a plethora of others have yet to work with it since. i also cant get my unlock_code.bin to work since i think somehow the code dont match with the region that it was applied with was. so i cant unlock my bootloader to get any conversion scripts or flashing commands to work. fastbootenhanced doesn't work either. i dont know what to do, please help me cuz i goofed hard as hell somewhere.
YourLocalDund33 said:
ive been playing with them for the last 20 hours almost nonstop. im back to being tmobile but no msm tool (yet) will work with it. I tried almost every tmobile msm and a plethora of others have yet to work with it since. i also cant get my unlock_code.bin to work since i think somehow the code dont match with the region that it was applied with was. so i cant unlock my bootloader to get any conversion scripts or flashing commands to work. fastbootenhanced doesn't work either. i dont know what to do, please help me cuz i goofed hard as hell somewhere.
Click to expand...
Click to collapse
Is the MSM saying device not match image, is it an unsupported target TMO error, what's the error?
EtherealRemnant said:
Is the MSM saying device not match image, is it an unsupported target TMO error, what's the error?
Click to expand...
Click to collapse
the msm is saying its a device mismatch and it thinks its the Indian variant but everything else is T-Mobile (stock), sorry about the late reply, its a holiday for me here.
Edit: I am Android version 12 now on T-Mobile, but I trying to get back to global rooted if that helps any with where I'm wanting to go with it
Edit 2: when I tried to use the multi msm tool provides I couldn't get O2 to show as an option anywhere, only Indian again.
YourLocalDund33 said:
the msm is saying its a device mismatch and it thinks its the Indian variant but everything else is T-Mobile (stock), sorry about the late reply, its a holiday for me here.
Edit: I am Android version 12 now on T-Mobile, but I trying to get back to global rooted if that helps any with where I'm wanting to go with it
Edit 2: when I tried to use the multi msm tool provides I couldn't get O2 to show as an option anywhere, only Indian again.
Click to expand...
Click to collapse
If it thinks it's an Indian variant, you use my modded MSM and select India for the target.
I recovered my bricked LE2110 from Oneplus 9 pro Indian msm tools and I wish to restore it to Oneplus 9 global rom. I try to use the "Fastboot enhance (version 1.3)" to flash the payload.bin into my LE2110, but I cannot find any "lfash" button ! The only button I can see is "Extract Image", am I missing something ? I try local upgrade but it cannot find the firmware file ! Please help !
EtherealRemnant said:
If it thinks it's an Indian variant, you use my modded MSM and select India for the target.
Click to expand...
Click to collapse
Thats why i edited my post, I tried to use the modded tool but it only gives the option for the indian variant. the 02 option is not there boss.
YourLocalDund33 said:
Thats why i edited my post, I tried to use the modded tool but it only gives the option for the indian variant. the 02 option is not there boss.
Click to expand...
Click to collapse
Which mod are you using? There have been a bunch posted in this forum.
EtherealRemnant said:
Which mod are you using? There have been a bunch posted in this forum.
Click to expand...
Click to collapse
the one from the op. its the one thats said its multi support for indian and global
YourLocalDund33 said:
the one from the op. its the one thats said its multi support for indian and global
Click to expand...
Click to collapse
Try this one.
3.56 GB file on MEGA
mega.nz
That one is also multi target. Both of these have been tested, I don't know why it's not working for you. You can also try not selecting a target and see what happens, I have found I don't always need to select the target if my device firmware hasn't been too corrupted.
Beware that with this one, you can't unlock the bootloader until after you go to OOS12 because OnePlus bugged the erase script on 11.2.10.10.
EtherealRemnant said:
Try this one.
3.56 GB file on MEGA
mega.nz
That one is also multi target. Both of these have been tested, I don't know why it's not working for you. You can also try not selecting a target and see what happens, I have found I don't always need to select the target if my device firmware hasn't been too corrupted.
Beware that with this one, you can't unlock the bootloader until after you go to OOS12 because OnePlus bugged the erase script on 11.2.10.10.
Click to expand...
Click to collapse
I'm already OOS12. still couldn't unlock bootloader. I was on chat with Oneplus support for an hour or so just a few minutes ago. They were a little slow with understanding the situation (didn't mention to them using a lot of modded msm tools) but I did tell them I used the tool to reset it to stock. that and my unlock_code.bin was no longer working. They put me on chat with the higher team and then the supervisor herself overtook chat and had a look at when my original application for my phone was. She decided she will reissue me a new code and said after 24-48hrs ill get the new code via email. How familiar are you with the erase script with the msm tool?
YourLocalDund33 said:
I'm already OOS12. still couldn't unlock bootloader. I was on chat with Oneplus support for an hour or so just a few minutes ago. They were a little slow with understanding the situation (didn't mention to them using a lot of modded msm tools) but I did tell them I used the tool to reset it to stock. that and my unlock_code.bin was no longer working. They put me on chat with the higher team and then the supervisor herself overtook chat and had a look at when my original application for my phone was. She decided she will reissue me a new code and said after 24-48hrs ill get the new code via email. How familiar are you with the erase script with the msm tool?
Click to expand...
Click to collapse
It's not the MSM Tool that's borked, it's the ROM itself.
Looking for a stock c61 LE2115 Global boot.img (oneplus 9)
I overwrote mine trying to root and now I can't get the phone to boot back into c61. I have access to fastboot though
hello gyus, i have a xiaomi redmi 12c. how can i install magisk? there aren't tutorial
Removed
jericho82 said:
+1
I buy this phone too and starting to UBL [still wait 4 days more] but i searched for TWRP is nowhere to found, and about root think i believe it's like usually goes with MAGISK but twrp is nowhere to be found can somebody made TWRP for redmi 12C [Helio G85]
Click to expand...
Click to collapse
Have you tried to patch boot.img and flash it?
To install Magisk TWRP isn't needed at all
[GUIDE] Magisk Root without TWRP
Hello guys. I've seen this device development for custom rom and custom recovery are slow (they did it in privat currently, invited user or someone who want to join). The unofficial twrp having issue with encrypted device (asking for password)...
forum.xda-developers.com
razor992 said:
Have you tried to patch boot.img and flash it?
Click to expand...
Click to collapse
no, it's still tomorrow night i think because MI UNLOCK gave me 1 week for UBL, tomorrow nights will do magisk patch
jwoegerbauer said:
To install Magisk TWRP isn't needed at all
[GUIDE] Magisk Root without TWRP
Hello guys. I've seen this device development for custom rom and custom recovery are slow (they did it in privat currently, invited user or someone who want to join). The unofficial twrp having issue with encrypted device (asking for password)...
forum.xda-developers.com
Click to expand...
Click to collapse
TWRP i need for safety, just in case of errors in the future
jericho82 said:
no, it's still tomorrow night i think because MI UNLOCK gave me 1 week for UBL, tomorrow nights will do magisk patch
Click to expand...
Click to collapse
You can unlock instant
(MTK) UNLOCK BOOTLOADER WITHOUT WAITING A WEEK
Hey! (PROBABLY) WORKS ON ALL MTK DEVICES This is my first thread so pls don't eat me if something has been written wrong I found a method, that allows you unlock bootloader without xiaomi unlocking software. Now, you don't need to wait 168...
forum.xda-developers.com
@jericho82
The phone is running MIUI 13, thus it's Linux kernel should be version 5.1+ what makes rooting Android via Magisk obsolete: progressive users flash KernelSU
GitHub - tiann/KernelSU: A Kernel based root solution for Android
A Kernel based root solution for Android. Contribute to tiann/KernelSU development by creating an account on GitHub.
github.com
jwoegerbauer said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@jericho82
The phone is running MIUI 13, thus it's Linux kernel should be version 5.1+ what makes rooting Android via Magisk obsolete: progressive users flash KernelSU
GitHub - tiann/KernelSU: A Kernel based root solution for Android
A Kernel based root solution for Android. Contribute to tiann/KernelSU development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
I think it’s older kernel
razor992 said:
You can unlock instant
(MTK) UNLOCK BOOTLOADER WITHOUT WAITING A WEEK
Hey! (PROBABLY) WORKS ON ALL MTK DEVICES This is my first thread so pls don't eat me if something has been written wrong I found a method, that allows you unlock bootloader without xiaomi unlocking software. Now, you don't need to wait 168...
forum.xda-developers.com
Click to expand...
Click to collapse
LOOOOLLL NO THANKS, Before This 12C, I've Been Try That Instant UBL With An Cheap Redmi 9C BUT FAILURE AND FINALLY I MUST REMOVE THE BATTERY, For Normally One, The 9C Is Easy To Instant UBL Because I Myself Doned With 9C Instant UBL Over Than 5 Time, But The Last 9C (Using New Firmware) Cannot Be Instant UBL Except Waiting Officialy, So This 12C I Prefer Using Safe Method LMAO
jwoegerbauer said:
@jericho82
The phone is running MIUI 13, thus it's Linux kernel should be version 5.1+ what makes rooting Android via Magisk obsolete: progressive users flash KernelSU
GitHub - tiann/KernelSU: A Kernel based root solution for Android
A Kernel based root solution for Android. Contribute to tiann/KernelSU development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
razor992 said:
I think it’s older kernel
Click to expand...
Click to collapse
Yea The Redmi Last 2022 And 2023 Using New Kernel And Firmware Thats Why In Above I Mention "I Failed To Instant UBL Redmi 9C That Usually Can Be Easily Done", So I Still Search For Tutorial But None Can Be Found, I'm Not Afraid Bout Diassembly Phone BUT This Phone Is My Wife's... So I Must Done With Safety Root, And BTW My Redmi 12C Using Kernel 4.19, Android 12, Miui 13, If Im not Mistaken, 2 Days Ago I Search Throughout The Chinese Site (I Can Read And Talk A Few Chinese Characters But Not Too Much) The 12C Has Same With Poco C55 But I Searched Poco C55 None To Be Found Too LMAO
FYI : I Just Receive Information From My Friends From Beijing China, He Can Root 12C Earth Redmi And TWRP Using TWRP 3.4.0.0 DaVinci, BUT He Is In Official China Rom Stable, I Don't Know With Global, Let Me Try Tonights Or By Tomorrow Mornings, Let's Not Gave Up A Hope, I Believe There Is A Way To Jailbreak This One Phone
Edit Failed Because I Can't Flash At All, Using SP Flash Tool Always Broom Error, While Mi Flash Tool error When Installing Driver, I Already Make Boot.img Patch With Magisk But Trouble On Flashing, Any Help?
Edit 2 : Try temporary boot via adb always error "TOO MANY LINKS", While im afraid to flash using adb because it's side A/B type boot, so for a while maybe i can't do anything unless there is twrp for this phone, so my case for this phone is closed here [so sorry can't do anything much for help, bcoz this phone is my wife's phone so i don't want to ruin her mood if i forcing to far more than this and if anything goes bad brrrr... can't think of it anymore lmao], I hope someday or a few days again there is more master to gave hand to try root and gave this phone twrp recovery
jericho82 said:
Edit Failed Because I Can't Flash At All, Using SP Flash Tool Always Broom Error, While Mi Flash Tool error When Installing Driver, I Already Make Boot.img Patch With Magisk But Trouble On Flashing, Any Help?
Edit 2 : Try temporary boot via adb always error "TOO MANY LINKS", While im afraid to flash using adb because it's side A/B type boot, so for a while maybe i can't do anything unless there is twrp for this phone, so my case for this phone is closed here [so sorry can't do anything much for help, bcoz this phone is my wife's phone so i don't want to ruin her mood if i forcing to far more than this and if anything goes bad brrrr... can't think of it anymore lmao], I hope someday or a few days again there is more master to gave hand to try root and gave this phone twrp recovery
Click to expand...
Click to collapse
Try with another pc…if you get driver error
NB : Finally can TEMP BOOT magisk patch Boot.img but not working, i think because the DISABLE DM VERITY is necessary need so i can't do anything if it mean FLASHING, the magisk it's still N/A/not installed even i boot temp from magisk patch boot.img while the twrp is can't boot [still error too many links], so i gave up till this processing, btw i try 2 twrp from orange fox anddavinci but it same error too many links, i think as long the DISABLE DM VERITY installed the magisk wont work and i cannot change A side because its always unknown command and the GETVAR always on side B so im stuck on this exploration and finally gave up]
Lol Finally Rooted Redmi 12C Earth, I've Doned, This Is My 2nd Creation After Narzo 50A LMAO
jericho82 said:
Lol Finally Rooted Redmi 12C Earth, I've Doned, This Is My 2nd Creation After Narzo 50A LMAO
Click to expand...
Click to collapse
Can you share how you done it?
razor992 said:
Can you share how you done it?
Click to expand...
Click to collapse
will compile file later and upload bruh
jericho82 said:
will compile file later and upload bruh
Click to expand...
Click to collapse
Thank you, I tried without success. Magisk work?
razor992 said:
Thank you, I tried without success. Magisk work?
Click to expand...
Click to collapse
Full work, zygisk, lposed, all works like charm, flawless if i must said, imei, signal and everything was safe, ok and still excellent