Phone updated from 13.0.2.0 to 13.0.4.0 accidentally or by itself, not sure, received the latest OTA and after reboot root is gone...
How can i get root back without loosing data or formatting?
You need to reinstall it using adb method, remember: everytime you update you loose the root
xNAPx said:
You need to reinstall it using adb method, remember: everytime you update you loose the root
Click to expand...
Click to collapse
Will i use data/settings if i reinstall magisk via adb?
You mean lose? Nope you won't as you are not formatting anything
xNAPx said:
You mean lose? Nope you won't as you are not formatting anything
Click to expand...
Click to collapse
Sorry, i meant loose data... And last question, which adb method should i use? I don't have twrp installed either as it wasn't available while i was rooting 13.0.2.0... Not sure if it's available now...?
GODSPD said:
Sorry, i meant loose data... And last question, which adb method should i use? I don't have twrp installed either as it wasn't available while i was rooting 13.0.2.0... Not sure if it's available now...?
Click to expand...
Click to collapse
Adb method doesn't need twrp, it is a bit more difficult to inject the root but you don't need to go through twrp. Just search on Google you will find several guides, I can tell you that you need the boot.img of the installed ROM in order to complete the process. You usually find this file into the fastboot ROM zip package
xNAPx said:
Adb method doesn't need twrp, it is a bit more difficult to inject the root but you don't need to go through twrp. Just search on Google you will find several guides, I can tell you that you need the boot.img of the installed ROM in order to complete the process. You usually find this file into the fastboot ROM zip package
Click to expand...
Click to collapse
So I'm guessing it's the same process as last time, the required boot.img will need to be from the updated 13.0.4.0 version? I barely remember how i did it initially, if you have any guides that work id really appreciate it
For the version 13.0.2.0 I used tge boot.img of the same fastboot ROM, I don't know if it would work with another boot.img honestly
I cannot seem to find the boot.img for the latest ota...
xNAPx said:
For the version 13.0.2.0 I used tge boot.img of the same fastboot ROM, I don't know if it would work with another boot.img honestly
Click to expand...
Click to collapse
cannot find a boot.img for 13.0.4, cannot extract it from payload.bin either via python, nothing seems to be working
xNAPx said:
For the version 13.0.2.0 I used tge boot.img of the same fastboot ROM, I don't know if it would work with another boot.img honestly
Click to expand...
Click to collapse
I tried it and boot looped to the bootloader...try at your own risk
tensux said:
I tried it and boot looped to the bootloader...try at your own risk
Click to expand...
Click to collapse
Did you manage to get it done? Apparently you can extract the 13.0.4 boot.img from the roms payload.bin file but i couldn't get it done myself... Did you manage to root yours?
GODSPD said:
Did you manage to get it done? Apparently you can extract the 13.0.4 boot.img from the roms payload.bin file but i couldn't get it done myself... Did you manage to root yours?
Click to expand...
Click to collapse
no in fact I had to switch to xiaomi.eu. i couldnt get anything else to flash. it kept failing at the same spot, i dont quite remember but had the name "super" in it
Just wait for the fastboot ROM guys
xNAPx said:
Just wait for the fastboot ROM guys
Click to expand...
Click to collapse
if we only knew when and where that will be released
Usually a week or two after the recovery release
Related
Hey.
My N6 got an error after I tried to update. I saw somewhere that installing the update on a rooted device (stock everything, just root) would be successful but it would remove root. Tried and got the error message with the android guy and a warning sign or something like that just with the "error" text, no more. I unrooted and rebooted, after some time the update prompted again and tried, same result.
I did some searches and just a few people have commented this issue, no answers yet.
Any ideas?
OscarBrito said:
Hey.
My N6 got an error after I tried to update. I saw somewhere that installing the update on a rooted device (stock everything, just root) would be successful but it would remove root. Tried and got the error message with the android guy and a warning sign or something like that just with the "error" text, no more. I unrooted and rebooted, after some time the update prompted again and tried, same result.
I did some searches and just a few people have commented this issue, no answers yet.
Any ideas?
Click to expand...
Click to collapse
Has to be completely stock. No root, custom kernel or recovery. How did you unroot. Have to flash factory image to remove root. Can't just remove the app. Forget OTAs if you are gonna root. Have to reflash factory image anyway so might as well just flash the updated image.
KingRoot
prdog1 said:
Has to be completely stock. No root, custom kernel or recovery. How did you unroot. Have to flash factory image to remove root. Can't just remove the app. Forget OTAs if you are gonna root. Have to reflash factory image anyway so might as well just flash the updated image.
Click to expand...
Click to collapse
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.
OscarBrito said:
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.
Click to expand...
Click to collapse
Your system is still modified. Even if remove the files the partition has been modified. If you have custom recovery or kernel it also won't flash. Have to flash back to stock so might as well just fastboot the updated factory image.
OscarBrito said:
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.
Click to expand...
Click to collapse
None of the unroot options put things back to 100% stock. They just remove root. The only way to remove all traces is to fastboot flash the system.img
If you're going to run rooted, forget about OTA and learn about fastboot.
General > sticky roll-up > adb and fastboot
Reset
prdog1 said:
Your system is still modified. Even if remove the files the partition has been modified. If you have custom recovery or kernel it also won't flash. Have to flash back to stock so might as well just fastboot the updated factory image.
Click to expand...
Click to collapse
Can I backup, do a factory data reset and then do the update? Then root again and restore my stuff.
OscarBrito said:
Can I backup, do a factory data reset and then do the update? Then root again and restore my stuff.
Click to expand...
Click to collapse
Nope. Have to flash stock image as posted above.
prdog1 said:
Nope. Have to flash stock image as posted above.
Click to expand...
Click to collapse
Dang. I don't like to mess with flashing and custom recoveries but I guess now I most.
I'm looking at Flashify. Download the stock image with the patch already on it and flash it that way. Do you recommend doing it that way?
Another thing, Any good and simple backup tool? I just want to skip the part where I need to configure everything again.
OscarBrito said:
Dang. I don't like to mess with flashing and custom recoveries but I guess now I most.
I'm looking at Flashify. Download the stock image with the patch already on it and flash it that way. Do you recommend doing it that way?
Another thing, Any good and simple backup tool? I just want to skip the part where I need to configure everything again.
Click to expand...
Click to collapse
You can't flash the stock image with flashify. Use fastboot as I have already advised.
Titanium backup is a great backup app, but you won't wipe the device if you only flash the system.img, boot.img and radio.img
danarama said:
You can't flash the stock image with flashify. Use fastboot as I have already advised.
Titanium backup is a great backup app, but you won't wipe the device if you only flash the system.img, boot.img and radio.img
Click to expand...
Click to collapse
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.
OscarBrito said:
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.
Click to expand...
Click to collapse
Fastboot works with Linux also.
OscarBrito said:
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.
Click to expand...
Click to collapse
No worries. Linux is even easier. You just stick the fastboot binaries in /usr/bin
Note, you'll probably need to use sudo / su to call fastboot.
danarama said:
No worries. Linux is even easier. You just stick the fastboot binaries in /usr/bin
Note, you'll probably need to use sudo / su to call fastboot.
Click to expand...
Click to collapse
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.
OscarBrito said:
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.
Click to expand...
Click to collapse
Better chance of bricking it with ToolKit than with manual fastboot. I run stock rooted with TWRP also. Takes 2-3 minutes to update with fastboot. If toolkit fails will most likely need fastboot to fix it anyway.
OscarBrito said:
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.
Click to expand...
Click to collapse
Don't use toolkits unless you can use fastboot..so just use fastboot. I'm not saying this for fun you know...if anything, its quite boring having to say this to everyone on a daily basis
Use fastboot please. Read my fastboot thread. You understand that fastboot is Googles method for flashing Google android on the google nexus? It should be pretty clear that this is the best tool for the job.
danarama said:
Don't use toolkits unless you can use fastboot..so just use fastboot. I'm not saying this for fun you know...if anything, its quite boring having to say this to everyone on a daily basis
Use fastboot please. Read my fastboot thread. You understand that fastboot is Googles method for flashing Google android on the google nexus? It should be pretty clear that this is the best tool for the job.
Click to expand...
Click to collapse
Don't get me wrong, I'm not afraid of a terminal, but well, you are right going with a terminal rather than a tool.
I'm finishing my backup and then doing all this manually, thanks a lot, both.
OscarBrito said:
Don't get me wrong, I'm not afraid of a terminal, but well, you are right going with a terminal rather than a tool.
I'm finishing my backup and then doing all this manually, thanks a lot, both.
Click to expand...
Click to collapse
I can't see how any Linux user would be afraid of terminals
Yeap, just tried to Flash my Super Awesome Nexus 5 with the LMY48I Update Zip file (10mb), via TWRP, while Rooted and I got the Nice Red Error... So I guess I have to download the Factory image LMY48I and via fastboot just flash the system.img if nothing else has been modified since LMY48B... In case I loose Root Access I might just reflash the script via TWRP... I will post update if anyone interested...
imor said:
Yeap, just tried to Flash my Super Awesome Nexus 5 with the LMY48I Update Zip file (10mb), via TWRP, while Rooted and I got the Nice Red Error... So I guess I have to download the Factory image LMY48I and via fastboot just flash the system.img if nothing else has been modified since LMY48B... In case I loose Root Access I might just reflash the script via TWRP... I will post update if anyone interested...
Click to expand...
Click to collapse
You will lose root. Flash supersu from recovery before first boot
Ok, just confirming here before I mess up. I have an international N6 rooted with stock recovery running LMY47Z. I can't update OTA. So I should flash the full stock image and then run cf-auto-root before rebooting.
Is this correct? Will I lose my user data when I do this? If so, what's the easiest way to backup and restore? Can't I flash the 25MB update .zip instead?
Thanks!
Hey, i've my mi A2 in August Patch (v9.6.10.0 ODIMIFE)
And
1. Bootloader Unlocked
2.Rooted
3.HAL3 Enabled
4.System Modified
What shoud i do to update to the latest(September) security patch.
I'm having serious wifi issue so that i'm desperate to update the latest OTA
Uinstall magisk, install ota use patched boot with magisk, ez.
T4Ump said:
Uinstall magisk, install ota use patched boot with magisk, ez.
Click to expand...
Click to collapse
This won't help him as he also modified the system partition
---------- Post added at 03:47 PM ---------- Previous post was at 03:46 PM ----------
rafihasan710 said:
Hey, i've my mi A2 in August Patch (v9.6.10.0 ODIMIFE)
And
1. Bootloader Unlocked
2.Rooted
3.HAL3 Enabled
4.System Modified
What shoud i do to update to the latest(September) security patch.
I'm having serious wifi issue so that i'm desperate to update the latest OTA
Click to expand...
Click to collapse
Next to putting stock boot you need to flash system partition again. Backup your data first just to be sure you have it before you might need to flash the complete August image
Benjamin_L said:
This won't help him as he also modified the system partition
---------- Post added at 03:47 PM ---------- Previous post was at 03:46 PM ----------
Next to putting stock boot you need to flash system partition again. Backup your data first just to be sure you have it before you might need to flash the complete August image
Click to expand...
Click to collapse
Im idiot, i was wrong Yea, put stock boot and install ota then patched boot
T4Ump said:
Im idiot, i was wrong Yea, put stock boot and install ota then patched boot
Click to expand...
Click to collapse
This won't be enough if he mounted or modified system partition as he said. Ota will still fail even with stock boot.
Benjamin_L said:
This won't be enough if he mounted or modified system partition as he said. Ota will still fail even with stock boot.
Click to expand...
Click to collapse
I disabled all magisk plugins, camera api, ios emoji, etc ****s after this i flash stock boot and install ota works.
T4Ump said:
I disabled all magisk plugins, camera api, ios emoji, etc ****s after this i flash stock boot and install ota works.
Click to expand...
Click to collapse
Depends on what you do. I used AdBlock and restoring stock boot was not enough for me that time
If you modified anything directly in system then your only option is to download the full rom and flash it with fastboot
http://bigota.d.miui.com/V9.6.13.0....0.ODIMIFE_20180913.0000.00_8.1_fbd1120565.tgz
Backup your data first and be careful, it will will wipe your data by default
I updated the toolkit to force update using fastboot. just run the unbrick option. Make sure to make a backup first, just in case
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
Edit: Also, if you have any bugs please let me know, I can fix it today.
Nebrassy said:
If you modified anything directly in system then your only option is to download the full rom and flash it with fastboot
http://bigota.d.miui.com/V9.6.13.0....0.ODIMIFE_20180913.0000.00_8.1_fbd1120565.tgz
Backup your data first and be careful, it will will wipe your data by default
Click to expand...
Click to collapse
Is there any way i can do this without wiping my data?
rafihasan710 said:
Is there any way i can do this without wiping my data?
Click to expand...
Click to collapse
I guess you can, choose clean all, and flash_all_except_data.bat in the corner in miflash, careful not to choose lock
but you should take a backup anyway, you never know
Nebrassy said:
I guess you can, choose clean all, and flash_all_except_data.bat in the corner in miflash, careful not to choose lock
but you should take a backup anyway, you never know
Click to expand...
Click to collapse
Can You Please Explain the whole procedure step by step....
Sorry...i'm a noob
rafihasan710 said:
Can You Please Explain the whole procedure step by step....
Sorry...i'm a noob
Click to expand...
Click to collapse
http://en.miui.com/a-232.html
rafihasan710 said:
Is there any way i can do this without wiping my data?
Click to expand...
Click to collapse
You do not need to flash all. Yesterday I have updated my unlocked and rooted phone with changed system partition without any trouble, and all my apps and data are still with me. Just flash stock system and boot images via fastboot, then make OTA update. Then copy new stock boot.img to your phone, open Magisk Manager, click Install, patch boot.img, copy patched_boot.img back to PC and flash it via fastboot. That is all. For me the most difficult part was to wait for downloading 3 Gb of data from terribly slow miui.com.
drauger said:
You do not need to flash all. Yesterday I have updated my unlocked and rooted phone with changed system partition without any trouble, and all my apps and data are still with me. Just flash stock system and boot images via fastboot, then make OTA update. Then copy new stock boot.img to your phone, open Magisk Manager, click Install, patch boot.img, copy patched_boot.img back to PC and flash it via fastboot. That is all. For me the most difficult part was to wait for downloading 3 Gb of data from terribly slow miui.com.
Click to expand...
Click to collapse
Can You Provide me the necessary file links.
By the way, Thank You Very Much.
drauger said:
You do not need to flash all. Yesterday I have updated my unlocked and rooted phone with changed system partition without any trouble, and all my apps and data are still with me. Just flash stock system and boot images via fastboot, then make OTA update. Then copy new stock boot.img to your phone, open Magisk Manager, click Install, patch boot.img, copy patched_boot.img back to PC and flash it via fastboot. That is all. For me the most difficult part was to wait for downloading 3 Gb of data from terribly slow miui.com.
Click to expand...
Click to collapse
And please provide the fastboot commands for flashing all of those.
rafihasan710 said:
And please provide the fastboot commands for flashing all of those.
Click to expand...
Click to collapse
Did you do some research by yourself or are you expecting others to do the work for you? It's really not that hard..
Benjamin_L said:
Did you do some research by yourself or are you expecting others to do the work for you? It's really not that hard..
Click to expand...
Click to collapse
I'm sorry for that.
But as you've done this before so i just want to follow your proceedure strictly.
I don't want my phone to be bricked.
If you can help please do...
rafihasan710 said:
I'm sorry for that.
But as you've done this before so i just want to follow your proceedure strictly.
I don't want my phone to be bricked.
If you can help please do...
Click to expand...
Click to collapse
I understand your fear but try looking for commands and procedures yourself in the first place and then ask if this is right. Will help you more than just copy pasting stuff, you don't understand. This way you will become knowledgeable yourself but it takes time of course. Don't fear!
Benjamin_L said:
I understand your fear but try looking for commands and procedures yourself in the first place and then ask if this is right. Will help you more than just copy pasting stuff, you don't understand. This way you will become knowledgeable yourself but it takes time of course. Don't fear!
Click to expand...
Click to collapse
Thank You
Hi everyone,
I have some months before accidentally reset after ota update on magisk and lost root. Unfortunately I cant find this FW anywhere since it was almost immediatly been replaced by 10.0.16, and the only thread having such old firmware was using filehosting from which the links expired.
I tried doing a system ota, but it won't work. I don't expect anyone to extract the boot.img for me just share the 10.0.14. if available, i would prefer not to wipe system data, since now without root i can't backup, and Helium is no longer supported.
Thank You.
Ikarus01 said:
Hi everyone,
I have some months before accidentally reset after ota update on magisk and lost root. Unfortunately I cant find this FW anywhere since it was almost immediatly been replaced by 10.0.16, and the only thread having such old firmware was using filehosting from which the links expired.
I tried doing a system ota, but it won't work. I don't expect anyone to extract the boot.img for me just share the 10.0.14. if available, i would prefer not to wipe system data, since now without root i can't backup, and Helium is no longer supported.
Thank You.
Click to expand...
Click to collapse
OTA updates usually don't touch the boot image so you could use the fastboot or recovery ROM V10.0.13.0 from here https://flashxiaomi.com/download-install-miui-rom-for-xiaomi-mi-a2-all-miui-firmwares/ also you can flash a recovery and backup your boot image to patch it through Magisk or flash directly the zip (a lower version)
SubwayChamp said:
OTA updates usually don't touch the boot image so you could use the fastboot or recovery ROM V10.0.13.0 from here https://flashxiaomi.com/download-install-miui-rom-for-xiaomi-mi-a2-all-miui-firmwares/ also you can flash a recovery and backup your boot image to patch it through Magisk or flash directly the zip (a lower version)
Click to expand...
Click to collapse
Thank you for replying,
i thought about it but if it proves not the case, and they changed the hex i wouldnt like bootloops or problems down the road. If it works i will try to backup and go to latest android 9, since many are complaining about version 10 with emmc apparently forgotten.
Also unfortunately i lost twrp, and don't have a sd cardfor flashing,and wouldn't like to wipe data to install twrp.
I thought about it and my only course of action is getting the boot.img, dd is out of option since I am not rot, is there a non root way to unpack if it turns out 10.0.13 causes a bootloop?
Sorry if some things don't make sense I am getting back to this after a long hiatus, can I still extract the img. from zip, or do I have to upack it with python?
Thank you.
Ikarus01 said:
Thank you for replying,
i thought about it but if it proves not the case, and they changed the hex i wouldnt like bootloops or problems down the road. If it works i will try to backup and go to latest android 9, since many are complaining about version 10 with emmc apparently forgotten.
Also unfortunately i lost twrp, and don't have a sd cardfor flashing,and wouldn't like to wipe data to install twrp.
I thought about it and my only course of action is getting the boot.img, dd is out of option since I am not rot, is there a non root way to unpack if it turns out 10.0.13 causes a bootloop?
Sorry if some things don't make sense I am getting back to this after a long hiatus, can I still extract the img. from zip, or do I have to upack it with python?
Thank you.
Click to expand...
Click to collapse
It was a minor/small update, I doubt it causes a bootloop.
You can flash Orange Fox through fastboot, no need to wipe data and from there either just flash Magisk or backup your boot and patch it if you prefer this method.
Not sure to which image you refer, no need to unpack the image by any method.
SubwayChamp said:
It was a minor/small update, I doubt it causes a bootloop.
You can flash Orange Fox through fastboot, no need to wipe data and from there either just flash Magisk or backup your boot and patch it if you prefer this method.
Not sure to which image you refer, no need to unpack the image by any method.
Click to expand...
Click to collapse
Thank you again, for orange fox especially,
I thought I needed Payload dumper, or is that only after android 10?
Thanks for the help, i only liked your replies, i dont know if they removed thanks globally or only on QA forums
Ikarus01 said:
Thank you again, for orange fox especially,
I thought I needed Payload dumper, or is that only after android 10?
Click to expand...
Click to collapse
No, if you refer to a method to unpack the ROM it comes either in zip format (recovery) or in tar.gz format (fastboot), you just need to unpack it with something like Winrar other 7zip and inside you will find the boot image.
It's a global change, in this new platform they removed the thanks option, I disagree but this is how it is.
SubwayChamp said:
No, if you refer to a method to unpack the ROM it comes either in zip format (recovery) or in tar.gz format (fastboot), you just need to unpack it with something like Winrar other 7zip and inside you will find the boot image.
Click to expand...
Click to collapse
Oh that is good to hear!
Thank You again you really helped me here.
Sadly I can only like your post, I guess that is the new rep system?
Have a good day!
Cheers
I'm running NE2215_11_C.26. Its rooted. I let the OTA updater do its thing but it just gives me a generic error message with no information about what is wrong. Is it because I'm rooted? Could it be a region problem since this is a North American device in India?
yes. read the proper root thread.
DiGtal said:
I'm running NE2215_11_C.26. Its rooted. I let the OTA updater do its thing but it just gives me a generic error message with no information about what is wrong. Is it because I'm rooted? Could it be a region problem since this is a North American device in India?
Click to expand...
Click to collapse
Easiest / Fastest way to solve this issue is to unroot fully through Magisk (disable all modules too), reboot. Take the update. Reroot with booting a patched boot image. That will always be the most fool proof way to update this phone, even cross region from my knowledge.
if you are rooted you don't have to update via OTA but you have to use localupdate.apk after disabling magisk modules and uninstalling images from magisk! operations: disable magisk modules and reboot/uninstall magisk image/oxygen updater download OTA to root directory/install localupdate.apk and update from there without reboot/done update open magisk and click install reboot after OTA!
morgan76 said:
if you are rooted you don't have to update via OTA but you have to use localupdate.apk after disabling magisk modules and uninstalling images from magisk! operations: disable magisk modules and reboot/uninstall magisk image/oxygen updater download OTA to root directory/install localupdate.apk and update from there without reboot/done update open magisk and click install reboot after OTA!
Click to expand...
Click to collapse
Android 12 Local update will allow you to update with no need to disable or unroot.
Just pull the update file to the pc, Payload it for the Boot.img and flash the Boot.img back though magisk.
Pull the flashed file back to the pc, do the local update and boot up fully.
ADB Boot the now flashed Boot.img Via the PC it and then direct install
FKX1997 said:
Android 12 Local update will allow you to update with no need to disable or unroot.
Just pull the update file to the pc, Payload it for the Boot.img and flash the Boot.img back though magisk.
Pull the flashed file back to the pc, do the local update and boot up fully.
ADB Boot the now flashed Boot.img Via the PC it and then direct install
Click to expand...
Click to collapse
not true for this model
g96818 said:
I literally did it 3 hours ago
Click to expand...
Click to collapse
@FKX1997 Prove it. C30 full rom doesn't exist for this model.
FKX1997 said:
Android 12 Local update will allow you to update with no need to disable or unroot.
Just pull the update file to the pc, Payload it for the Boot.img and flash the Boot.img back though magisk.
Pull the flashed file back to the pc, do the local update and boot up fully.
ADB Boot the now flashed Boot.img Via the PC it and then direct install
Click to expand...
Click to collapse
you can't extract boot.img from update you need full rom
morgan76 said:
you can't extract boot.img from update you need full rom
Click to expand...
Click to collapse
Local update is a full rom installation. OTA is a partial update
FKX1997 said:
Local update is a full rom installation. OTA is a partial update
Click to expand...
Click to collapse
Still waiting for you to prove the c30 full rom for this model exists.
g96818 said:
Still waiting for you to prove the c30 full rom for this model exists.
Click to expand...
Click to collapse
Considering you can install 2213 on 2215, that would be why
FKX1997 said:
Considering you can install 2213 on 2215, that would be why
Click to expand...
Click to collapse
Op never asked to change regions, so therefore you're a liar trying to confuse people. You should apologize to the op and hope he didn't brick his phone following your lie
g96818 said:
Op never asked to change regions, so therefore you're a liar trying to confuse people. You should apologize to the op and hope he didn't brick his phone following your lie
Click to expand...
Click to collapse
Dude, it just seems you have a problem. Pipe it please
FKX1997 said:
Dude, it just seems you have a problem. Pipe it please
Click to expand...
Click to collapse
You're the one that came in with an attitude, been proved wrong, now in denial, and trying to pass the blame.
Go figure for someone who shoots from the hip.
I have a patched boot.img that I used to root C.26. Will it work on this one too? What's the location of the boot.img on the phone? I could get that via file manager since I'm rooted. Does the android 12 localupdate work for android 13 as well?
What's the latest full OTA version? Does payload dumper still work? I'm going to try to get the stock boot image just in case.
DiGtal said:
I have a patched boot.img that I used to root C.26. Will it work on this one too? What's the location of the boot.img on the phone? I could get that via file manager since I'm rooted. Does the android 12 localupdate work for android 13 as well?
What's the latest full OTA version? Does payload dumper still work? I'm going to try to get the stock boot image just in case.
Click to expand...
Click to collapse
Best not to mismatch revisions. You can find a pre patched NE2115 C.30 in @g96818's thread. Otherwise you can make your own.
I personally pull them from the NE2213 full zips (since we don't get full releases at NE2215 anymore) and patch that via magisk, it works fine cross region as long as you ONLY boot it once for the magisk install. Never had any issues with this method.
How do I make my own boot.img? Does the payload dumper still work? The go version does not work with deltas. While I can use the easier methods I want to try making my own boot.img as a learning exercise.
DiGtal said:
How do I make my own boot.img? Does the payload dumper still work? The go version does not work with deltas. While I can use the easier methods I want to try making my own boot.img as a learning exercise.
Click to expand...
Click to collapse
I, personally, extract boot.img from NE2213 full Zip using FBE. This is the ONLY thing to use this tool for. Then transfer that to phone, disable all modules, unroot, reboot. Take the next OTA, reboot. Then go into Magisk, patch the new boot image you xfer'd earlier, copy that back to computer. Use ADB Fastboot to BOOT the image, and finally go into Magisk for a direct install. Reboot, and you're done.
So, i've rooted my xiaomi note 5 with magisk, and i wanted to do the same with my main phone, and now i cant unlock my phone because i dont want my data lost (the apps are the most important and i have all my other data backed up) and i came across mediatekbootloaderunlcok and im just wondering is it patched or does it still work? because if it works then im definitely rooting my phone. id appreciate it if any of you guys answered my question
thanks
Just use mtkclient
boofiboi said:
Just use mtkclient.
https://github.com/bkerler/mtkclient
Click to expand...
Click to collapse
the hell is that lol
boofiboi said:
Just use mtkclient.
https://github.com/bkerler/mtkclient
Click to expand...
Click to collapse
also it worked and my phone is unlocked now but theres an issue, when i flash orangefox it just cant go to recovery then vibrates and goes back to the OS
Fixed. Its a tool that abuses mediateks BROM mode accesibility to do a bunch of stuff
SzymcioYa said:
also it worked and my phone is unlocked now but theres an issue, when i flash orangefox it just cant go to recovery then vibrates and goes back to the OS
Click to expand...
Click to collapse
Currently having the same issue. No other recovery other than Spark from BananaDroid works.
boofiboi said:
Currently having the same issue. No other recovery other than Spark from BananaDroid works.
Click to expand...
Click to collapse
R.I.P you guys.
Even TWRP doesn't work?
AltFantasy said:
R.I.P you guys.
Even TWRP doesn't work?
Click to expand...
Click to collapse
yup. it doesnt, tried it
The only TWRP version that works for me is the Dimenzino forks, but those only boot. ADB sideload crashes the recovery, decryption doesnt work thus MTP also doesnt work.
Any other recovery i try also locks me from booting before i reinstall spark.
I've been hating every second with this phone.
When i compare the experience of modding it to my old Redmi 8, this phone is such a pain.
IMEI backups
No ROM's work
No recovery's work.
Now that I have only 1 IMEI i can no longer even go back to MIUI.
boofiboi said:
Currently having the same issue. No other recovery other than Spark from BananaDroid works.
Click to expand...
Click to collapse
cant seem to find it, can you give me the link to the website?
SzymcioYa said:
cant seem to find it, can you give me the link to the website?
Click to expand...
Click to collapse
https://sourceforge.net/projects/rom-lord/files/A13/Recovery/Spark/recovery.img/download
This is the only recovery that has so far worked for me to install a ROM through sideload. Otherwise its pretty useless.
Looking at the rom-lord files, theres quite a few roms/recoveries in there, ill try to test the recoveries and let you know.
boofiboi said:
The only TWRP version that works for me is the Dimenzino forks, but those only boot. ADB sideload crashes the recovery, decryption doesnt work thus MTP also doesnt work.
Any other recovery i try also locks me from booting before i reinstall spark.
I've been hating every second with this phone.
When i compare the experience of modding it to my old Redmi 8, this phone is such a pain.
IMEI backups
No ROM's work
No recovery's work.
Now that I have only 1 IMEI i can no longer even go back to MIUI.
Click to expand...
Click to collapse
well, I mean, it's MediaTek....
you can just go port TWRP to your device by yourself, OR use GSI ROMs! (though, GSIs are very.... general, and so, they might not work with certain hardware inside your phone, because they're designed to be a one-size-fits-all solution.) even better, go make a custom ROM for your device by yourself!
boofiboi said:
https://sourceforge.net/projects/rom-lord/files/A13/Recovery/Spark/recovery.img/download
This is the only recovery that has so far worked for me to install a ROM through sideload. Otherwise its pretty useless.
Click to expand...
Click to collapse
all i want is to root my redmi 9 lol
i actually flashed this and it just still didnt do anything and just sent me to miu recovery soo.. yeah
SzymcioYa said:
all i want is to root my redmi 9 lol
i actually flashed this and it just still didnt do anything and just sent me to miu recovery soo.. yeah
Click to expand...
Click to collapse
So, I figured out how to fix SHRP and other stuff not booting.
Download the last android 11 firmware from here, get the fastboot version. Flash it and then just proceed to flash SHRP and all your roms like normal.
boofiboi said:
So, I figured out how to fix SHRP and other stuff not booting.
Download the last android 11 firmware from here, get the fastboot version. Flash it and then just proceed to flash SHRP and all your roms like normal.
Click to expand...
Click to collapse
so if i do it i can flash anything i want? sweet!
boofiboi said:
So, I figured out how to fix SHRP and other stuff not booting.
Download the last android 11 firmware from here, get the fastboot version. Flash it and then just proceed to flash SHRP and all your roms like normal.
Click to expand...
Click to collapse
but this will delete all my info right?
SzymcioYa said:
but this will delete all my info right?
Click to expand...
Click to collapse
Yes it will, back it up first
If you just want to root it, get the latest firmware from that website, extract the boot.img and patch it via the magisk app.
then just flash it via fastboot.
boofiboi said:
If you just want to root it, get the latest firmware from that website, extract the boot.img and patch it via the magisk app.
then just flash it via fastboot.
Click to expand...
Click to collapse
uh, can u fix it with any other way without needing to back up anything?