Hey guys! I haven't been in the rooting community for a while and when I was my phone was end of life. How can I accept an OTA while being rooted?
I assume I will have to unroot through SuperSU, update like normal, then re-root with the latest SuperSU. Is that correct? I saw some using FlashFire, but I am kind of uneasy about an automated app rooting my device.
Some additional info:
Phone on Feb security update
Phone rooted with latest SuperSU
I did not install custom recovery, only booted it to flash SuperSU
I don't want to lose any data on my phone
Thanks in advance guys! Hopefully with your help I can get this bad boy updated!
Bump?
No one can help me?
Google android factory OTA. That will get you to Google's full ota which you will need to sideload with adb. Full instructions are on the page with the download. And probably a dozen how to's posted here in the last couple of days.
What I did i downloaded from herehttps://developers.google.com/android/images#sailfish unzipped the file edited the batch took the -w out saved the file and ran the Bach file re installed twrp and root should not loose anything but its a possibility this link will you better directions its what I used https://forum.xda-developers.com/showpost.php?p=71321307&postcount=31
It's a bit more involved, but I always download the latest factory image, edit the batch file to remove the "-w" which doesn't wipe it. Then I boot back into TWRP and install the TWRP zip (not necessary if you don't want to keep it), then install SuperSU zip.
Here's the easiest method in my opinion (No PC required). This method requires TWRP recovery.
With TWRP already installed, download the next "Sailfish" OTA from here - https://developers.google.com/android/ota. Notice I said "next", not latest. If you're several OTA's behind you'll want to download all of the updates to bring you current. For example, I started yesterday on NMF26V and these are all of the files I downloaded.
{
"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"
}
You'll also need the latest TWRP, SuperSu, and any mods you plan to install. Now we're ready to start.
Boot to TWRP and install the "Next" OTA file. No need to do any wipes, just simply flash it. When it completes, immediately flash TWRP installer, then reboot.
Now reboot back to TWRP, flash the next OTA, immediately flash TWRP again, and reboot. Continue this until you're on the latest update.
Now simply boot back to TWRP and flash SuperSu. I also installed Elemental (after an additional reboot for good measure) as I like the swipe to sleep function.
Sent from my Pixel using Tapatalk
What's the reasoning behind having to do each OTA in order?
joshw0000 said:
Here's the easiest method in my opinion (No PC required). This method requires TWRP recovery.
With TWRP already installed, download the next "Sailfish" OTA from here - https://developers.google.com/android/ota. Notice I said "next", not latest. If you're several OTA's behind you'll want to download all of the updates to bring you current. For example, I started yesterday on NMF26V and these are all of the files I downloaded.
You'll also need the latest TWRP, SuperSu, and any mods you plan to install. Now we're ready to start.
Boot to TWRP and install the "Next" OTA file. No need to do any wipes, just simply flash it. When it completes, immediately flash TWRP installer, then reboot.
Now reboot back to TWRP, flash the next OTA, immediately flash TWRP again, and reboot. Continue this until you're on the latest update.
Now simply boot back to TWRP and flash SuperSu. I also installed Elemental (after an additional reboot for good measure) as I like the swipe to sleep function.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
dejanspa said:
What's the reasoning behind having to do each OTA in order?
Click to expand...
Click to collapse
You're welcome to try going straight to the latest OTA but it's my understanding that each one only contains the updates from that specific release. If it fails you could always modify the flashall.bat file of a full restore image and flash it with your computer. Then boot TWRP with fastboot, flash TWRP from the booted TWRP, and install SuperSu.
Sent from my Pixel using Tapatalk
Okay. Also in this method you don't have to modify any file to get rid of the "-w" so it won't wipe data? If I do what you did all my files and apps should still be there when I reach the last OTA.
Sorry iphone convert so i'm new to this.
joshw0000 said:
You're welcome to try going straight to the latest OTA but it's my understanding that each one only contains the updates from that specific release. If it fails you could always modify the flashall.bat file of a full restore image and flash it with your computer. Then boot TWRP with fastboot, flash TWRP from the booted TWRP, and install SuperSu.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
dejanspa said:
Okay. Also in this method you don't have to modify any file to get rid of the "-w" so it won't wipe data? If I do what you did all my files and apps should still be there when I reach the last OTA.
Sorry iphone convert so i'm new to this.
Click to expand...
Click to collapse
Nope. Nothing to modify as long as you download the OTA files from the link I posted and not the full image files from a different section. The image files are the ones that have the flashall.bat file that have to be modified before flashing. There's nothing to modify in the OTA's. That's another reason I like my method as I have 78GB or pics/videos/music that I'd hate to lose.
Sent from my Pixel using Tapatalk
joshw0000 said:
Here's the easiest method in my opinion (No PC required). This method requires TWRP recovery.
With TWRP already installed, download the next "Sailfish" OTA from here - https://developers.google.com/android/ota. Notice I said "next", not latest. If you're several OTA's behind you'll want to download all of the updates to bring you current. For example, I started yesterday on NMF26V and these are all of the files I downloaded.
You'll also need the latest TWRP, SuperSu, and any mods you plan to install. Now we're ready to start.
Boot to TWRP and install the "Next" OTA file. No need to do any wipes, just simply flash it. When it completes, immediately flash TWRP installer, then reboot.
Now reboot back to TWRP, flash the next OTA, immediately flash TWRP again, and reboot. Continue this until you're on the latest update.
Now simply boot back to TWRP and flash SuperSu. I also installed Elemental (after an additional reboot for good measure) as I like the swipe to sleep function.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Thanks, this was new for me :highfive: I always used to flash the system, boot etc, but this was a lot easier :good::victory:
Juhler said:
Thanks, this was new for me :highfive: I always used to flash the system, boot etc, but this was a lot easier :good::victory:
Click to expand...
Click to collapse
Glad I could help.
Sent from my Pixel using Tapatalk
For the April OTA update I was able to install the file that came to the phone using FlashFire. Trying to uninstall SuperSU and then take the OTA on the phone hadn't worked the previous two times I had tried it. When I tried the March OTA update on the phone with FlashFire it also didn't work, so I'm not clear if the latest FlashFire update was why the April OTA on the phone worked without issue. I thought maybe I needed to use the restore option in FlashFire to get it to work, but on the April OTA it turned out that I didn't need to use any of FlashFire's restore options like I had been planning on trying. For the April OTA to the phone, using FlashFire ended up being quicker and simpler than the previous manual process I had been doing to install the files Google posts online and then root the phone again. Since I'm using SuperSU to root the phone, I'll keep using FlashFire to update if it keeps working like it did this month.
Yeah OTA updates are patches not full OS files so must be done in order.
Using flashall with -w removed is the cleanest method as it rewrites all system files.
Personally I'm not a fan of patching the OS.
Related
Installed on my nexus LOLIPOP version through ADB / Fastboot.
How should I do now to upgrade to 5.0.1?
Do the same with the 5.0.1 image.
Thiagooo said:
Installed on my nexus LOLIPOP version through ADB / Fastboot.
How should I do now to upgrade to 5.0.1?
Click to expand...
Click to collapse
You can With adb sideload update ota manually without lose data
Here's how to upgrade to 5.0.1 on rooted Nexus 5
N/A
Err...
Why are you... Original question has been addressed already.
Yeah. I'm sure. Please stop suggesting toolkits to people.
Edward.Bernard said:
This is an easy way to upgrade to 5.0.1 without losing any data, though you will lose custom recovery and root. But those are easy to recover and are included here...
Setting up
You'll need a Windows PC, Nexus Root Toolkit software (WugFresh), and Flashify app (or similar)
Actually, the NRT software is not needed, but it makes the process stupidly easy. You can also do this by fastboot over ADB
Be sure to perform a full nandroid backup, just in case, though you shouldn't need it.
And absolutely backup your custom recovery using Flashify (or whatever you use)
Factory images
Forget about the OTA update and go to the Google Developers site for the factory images you want
Download the file to your PC, then unzip it and any zipped files contained within it (it's like one of those Russian dolls)
Now find the .img files for "boot," "bootloader." "radio," and "system." Move them into a new folder that you can easily find.
There are other image files, but you don't want those, because they'll over-write your data.
Flashing using Nexus Root Toolkit
Open NRT and be sure that you select your CURRENT model and build in the upper left-hand corner.
Under Advanced Utilities, click Launch
Under Fastboot Flash, click Boot [Kernel], then browse for you boot.img file and click Open.
Let NRT do the rest.
Repeat this Fastboot Flash process for Bootloader, Radio, and System in that order.
After you flash the system image, your Nexus will reboot and complete the update.
Re-root
In the process, you've lost root so reboot your phone back into bootloader
In the NRT main menu, change your model and build in the upper left-hand corner to reflect 5.0.1
The software will need to restart and update.
Now, under the Root heading, click Root
When your phone reboots, your superuser will request to be updated. Allow it, and reboot.
Now open Flashify, flash your custom recovery, and reboot.
You're done!
Click to expand...
Click to collapse
Boooooooooooooooooooooooooooooooooooooooh Learn how to use adb and fastboot yourself and teach this to inexperienced users.
Incredibly complex solutions.......!
Easier just return to stock flash via OTA and reroot... I think this is the easiest method (despite for me is still a little bit ****ty) to go with Android latest updates
Don't like the Google Dev imaging and flashing option
I dont know if this ota zip will work but you can try?, assuming you dont want to lose your data by going with googles images
phandroid.com/2014/12/15/nexus-5-6-android-501-factory-image-ota-update-zip/
MiSSigNNo said:
Incredibly complex solutions.......!
Easier just return to stock flash via OTA and reroot... I think this is the easiest method (despite for me is still a little bit ****ty) to go with Android latest updates
Don't like the Google Dev imaging and flashing option
Click to expand...
Click to collapse
How is that the easiest solution?
Flash stock, then ota? Why not just flash 5.0.1 stock and NOT ota?
rootSU said:
How is that the easiest solution?
Flash stock, then ota? Why not just flash 5.0.1 stock and NOT ota?
Click to expand...
Click to collapse
I believe that is what he meant, just picked the wrong words. He meant 5.0.1 image when he used the term OTA.
JayR_L said:
I believe that is what he meant, just picked the wrong words. He meant 5.0.1 image when he used the term OTA.
Click to expand...
Click to collapse
Its hard on a forum where punctuation isn't used often. I envisage that there should be a comma between "stock" and "flash". True, it could also be a full stop missing.
That said, I've seen many threads where people just say flash stock then ota so I've assumed this is the same..
JayR_L said:
I believe that is what he meant, just picked the wrong words. He meant 5.0.1 image when he used the term OTA.
Click to expand...
Click to collapse
With the NRT you just go back flashing to stock bootloader and then you can upgrade via OTA no-pain. After that you can reinstall back twrp (for example) and re-root device. No downloads required from external sources.
If you have to flash you have to go and pick the img and after that re-root. For me is a pain looking for the flash img every version! And worst part having to reboot for each image... boot, radio, system...
But I suppose it is a matter of preferences.
3 step method:
{
"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"
}
PD: BTW 5.0.1 only have boot and system for flashing?
Still though... Toolkits are bad. Use them at your peril and if you screw up, we're not wasting our time teaching the basics to fix it, that you would know if you did it properly the first time.
And reboot each time? What???
...and looking for image every time? Same place every time mate
You shan't need a toolkit. For one, Google themselves have put instructions on how to flash a factory image directly. And again, you shan't use toolkits.
And you DO NOT reboot for every image. You flash all of them at once, then you reboot.
Anyway this thread has degenerated to, plain and simply, diarrhea.
Ive tried several rooting methods and ended up bricking my phone every time. I'm running 6.0.1, build number mmb29k.n920tuvu3dpg1. Recently heard of cf-auto-root but the package they have has a different build number(MMB29K.N920TUVU2DPD1) with the model number and android version being the same. Will the cf-auto-root method work? Or should I be using a different method? (I'm new to this whole rooting thing, came over from iPhone. Jailbreaking was far easier)
jaycuzhommie said:
Ive tried several rooting methods and ended up bricking my phone every time. I'm running 6.0.1, build number mmb29k.n920tuvu3dpg1. Recently heard of cf-auto-root but the package they have has a different build number(MMB29K.N920TUVU2DPD1) with the model number and android version being the same. Will the cf-auto-root method work? Or should I be using a different method? (I'm new to this whole rooting thing, came over from iPhone. Jailbreaking was far easier)
Click to expand...
Click to collapse
Don't make it harder than it is
Odin flash TWRP
Boot to recovery
Copy the newest version of SuperSU to the phone and flash it
Reboot ...your rooted
Sent from my SM-N920T using Tapatalk
jaycuzhommie said:
Ive tried several rooting methods and ended up bricking my phone every time. I'm running 6.0.1, build number mmb29k.n920tuvu3dpg1. Recently heard of cf-auto-root but the package they have has a different build number(MMB29K.N920TUVU2DPD1) with the model number and android version being the same. Will the cf-auto-root method work? Or should I be using a different method? (I'm new to this whole rooting thing, came over from iPhone. Jailbreaking was far easier)
Click to expand...
Click to collapse
to the be a novice as i, him agrees read well and and follow the instructions of post # 2 here
http://forum.xda-developers.com/tmo...rom-n920tuvu1boh4-5-1-1-deodexed-ciq-t3194270
as already have the last firmware not have that install still the instructions since the step # 7 as in the image.
{
"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"
}
already the firmware the have for future if you wish render it to stock and clean
javierduran said:
to the be a novice as i, him agrees read well and and follow the instructions of post # 2 here
http://forum.xda-developers.com/tmo...rom-n920tuvu1boh4-5-1-1-deodexed-ciq-t3194270
as already have the last firmware not have that install still the instructions since the step # 7 as in the image. View attachment 3848895
already the firmware the have for future if you wish render it to stock and clean
Click to expand...
Click to collapse
This is a much better guide for his model
http://forum.xda-developers.com/showthread.php?t=3361990
Sent from my SM-N920T using Tapatalk
You only have to do is flash TWPR in odin (don't forget to uncheck F. Reset time and auto-reboot) before you flash the recovery, download the flashable Super SU and place it on SD , memory, otg or wathever. Just flash recovery, when odin ends, then boot directly into recovery and flash the super su and you are done. if you no want to install custom recovery, you must look for other options
clsA said:
Don't make it harder than it is
Odin flash TWRP
Boot to recovery
Copy the newest version of SuperSU to the phone and flash it
Reboot ...your rooted
Click to expand...
Click to collapse
I've read through a lot of the rooting threads here. From what I can see, the older stuff (2015) required flashing a new kernel as well. Is that just not the case anymore? Did I misread?
The Apostle said:
I've read through a lot of the rooting threads here. From what I can see, the older stuff (2015) required flashing a new kernel as well. Is that just not the case anymore? Did I misread?
Click to expand...
Click to collapse
That's correct the new SuperSU modifies the kernel for you
Sent from my SM-N930F using Tapatalk
clsA said:
Don't make it harder than it is
Odin flash TWRP
Boot to recovery
Copy the newest version of SuperSU to the phone and flash it
Reboot ...your rooted
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
I have attempted this twice and both times no luck. First attempt I flashed via odin the twrp .tar file and it was blocked by FRP. Had no clue what that was because there is no mention of it in the guide posted. Second attempt I turned on Oem unlocking in settings menu thinking that would work and flashed that successfully but the phone wouldnt boot or go into recovery. I ended up flashing the stock DPG1 firmware to fix the no boot issue and now im back at square one.
Am I missing something? Been rooting and Roming my phones forever but need a little help with this 1 thanks.
wrecless said:
I have attempted this twice and both times no luck. First attempt I flashed via odin the twrp .tar file and it was blocked by FRP. Had no clue what that was because there is no mention of it in the guide posted. Second attempt I turned on Oem unlocking in settings menu thinking that would work and flashed that successfully but the phone wouldnt boot or go into recovery. I ended up flashing the stock DPG1 firmware to fix the no boot issue and now im back at square one.
Am I missing something? Been rooting and Roming my phones forever but need a little help with this 1 thanks.
Click to expand...
Click to collapse
It works. I did it again last night after taking the PG1 update. All you need to do is... 1) boot into DL mode. 2) flash the TWRP tar file in the AP slot via Odin. 3) flash SU in recovery. That's it... you're done.
The Apostle said:
It works. I did it again last night after taking the PG1 update. All you need to do is... 1) boot into DL mode. 2) flash the TWRP tar file in the AP slot via Odin. 3) flash SU in recovery. That's it... you're done.
Click to expand...
Click to collapse
Strange because thats exactly what I did. After flashing TWRP with oem unlock off in Odin all the phone would to is either show the T-mobile logo forever or boot to download mode. I saw something about removing google account. Did you also do that first?
wrecless said:
Strange because thats exactly what I did. After flashing TWRP with oem unlock off in Odin all the phone would to is either show the T-mobile logo forever or boot to download mode. I saw something about removing google account. Did you also do that first?
Click to expand...
Click to collapse
I've did not remove my Google account. I've read that too but believe the circumstances were different.
You said you have OEM unlock ticked off? Should tick it on (so it shows blue)
You may want to dload the official PG1 FW from Sammobile.com and flash from scratch.
I updated to EMUI 5 with nougat, i think i lost my root. Went back to TWRP and about 60% of the way through the install phone reboots by itself with the phone not being rooted. Tried different superSU versions along with an adb sideload, same thing. Anyone have any idea what i'm doing wrong?
richbumx said:
I updated to EMUI 5 with nougat, i think i lost my root. Went back to TWRP and about 60% of the way through the install phone reboots by itself with the phone not being rooted. Tried different superSU versions along with an adb sideload, same thing. Anyone have any idea what i'm doing wrong?
Click to expand...
Click to collapse
twrp is not yet able to flash supersu successfully, if u want to root then flash a patched boot.img from here https://mega.nz/#!69IlASwI!FjF5rhALGGA_tusum7FdXgnO1R45ZIpdrahNa0UXT-8
Root working with B360 (L09 only at the minute)
thanks to @Atarii
Reboot into bootloader mode
Extract files and "fastboot flash boot boot.img"
Reboot into system
Install phh's SuperUser app from Play Store
OR
if u have twrp flash it thru twrp
raza3434 said:
twrp is not yet able to flash supersu successfully, if u want to root then flash a patched boot.img from here https://mega.nz/#!69IlASwI!FjF5rhALGGA_tusum7FdXgnO1R45ZIpdrahNa0UXT-8
Root working with B360 (L09 only at the minute)
thanks to @Atarii
Reboot into bootloader mode
Extract files and "fastboot flash boot boot.img"
Reboot into system
Install phh's SuperUser app from Play Store
OR
if u have twrp flash it thru twrp
Click to expand...
Click to collapse
Hello I have B380 and just tried this, flash the modified boot.img, and install the phh's su but still not rooted, do you have an idea?
remi13014 said:
Hello I have B380 and just tried this, flash the modified boot.img, and install the phh's su but still not rooted, do you have an idea?
Click to expand...
Click to collapse
(for L09)
u didn't mention u are on b380, anyways here is the boot.img for b380,
https://mega.nz/#!ekJVzLyY!pOhWHYpdhuRSFtBvxGYlMMFH5hFg0TG8bG17D13ZohM
raza3434 said:
(for L09)
u didn't mention u are on b380, anyways here is the boot.img for b380,
https://mega.nz/#!ekJVzLyY!pOhWHYpdhuRSFtBvxGYlMMFH5hFg0TG8bG17D13ZohM
Click to expand...
Click to collapse
i'm on L-04.. would this not work for me then?
richbumx said:
i'm on L-04.. would this not work for me then?
Click to expand...
Click to collapse
i dont know its atariis work you can ask there, @Atarii go to his profile search for b378, actually this boot.img is for p9 but due to same kernel it works on h8
richbumx said:
i'm on L-04.. would this not work for me then?
Click to expand...
Click to collapse
Try this boot image. You can flash it from twrp. Do not clear the cache or davlik. Reboot and install the phh super user apk.
https://forum.xda-developers.com/attachment.php?attachmentid=4070615&d=1489245825
https://forum.xda-developers.com/showpost.php?p=71382542&postcount=85
Parleyp
parleyp said:
Try this boot image. You can flash it from twrp. Do not clear the cache or davlik. Reboot and install the phh super user apk.
https://forum.xda-developers.com/attachment.php?attachmentid=4070615&d=1489245825
https://forum.xda-developers.com/showpost.php?p=71382542&postcount=85
Parleyp
Click to expand...
Click to collapse
I just tried this and it WORKS! I'm on EMUI 5 with my L-04. Now I can FINALLY block ads! Thanks for the info!
richbumx said:
i'm on L-04.. would this not work for me then?
Click to expand...
Click to collapse
parleyp said:
Try this boot image. You can flash it from twrp. Do not clear the cache or davlik. Reboot and install the phh super user apk.
https://forum.xda-developers.com/attachment.php?attachmentid=4070615&d=1489245825
https://forum.xda-developers.com/showpost.php?p=71382542&postcount=85
Parleyp
Click to expand...
Click to collapse
skrapmetal said:
I just tried this and it WORKS! I'm on EMUI 5 with my L-04. Now I can FINALLY block ads! Thanks for the info!
Click to expand...
Click to collapse
So we know it works on the L04 and L14. Does not work on L09.
L09 works
parleyp said:
So we know it works on the L04 and L14. Does not work on L09.
Click to expand...
Click to collapse
Wrong
{
"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"
}
Thanks for the update. I am happy is is working on yours.
skrapmetal said:
I just tried this and it WORKS! I'm on EMUI 5 with my L-04. Now I can FINALLY block ads! Thanks for the info!
Click to expand...
Click to collapse
I am also trying to get root on an H8 FRD-L04. So does this boot.img file get flashed in twrp like any other zip file or do I need to choose different options in twrp to write it to the correct place?
Also can you tell me which version of twrp you are using? There seem to be several floating around on xda.
Have you had any other issues with apps that need root since you did this? I'd like to get my favorite xposed mods working on my H8.
vouty said:
I am also trying to get root on an H8 FRD-L04. So does this boot.img file get flashed in twrp like any other zip file or do I need to choose different options in twrp to write it to the correct place?
Also can you tell me which version of twrp you are using? There seem to be several floating around on xda.
Have you had any other issues with apps that need root since you did this? I'd like to get my favorite xposed mods working on my H8.
Click to expand...
Click to collapse
Unzip the file first, that should leave you with bootr.img I think it's called. Make a backup just in case, but yes, flash it just like you would anything else, no need to wipe anything and no I did not change any settings.
I'm using TWRP 3.0.3 found here https://forum.xda-developers.com/honor-8/development/twrp-t3566563
I have tried at least 5 apps that have needed root and have not had any issues. I haven't tried xposed yet though.
skrapmetal said:
Unzip the file first, that should leave you with bootr.img I think it's called. Make a backup just in case, but yes, flash it just like you would anything else, no need to wipe anything and no I did not change any settings.
I'm using TWRP 3.0.3 found here https://forum.xda-developers.com/honor-8/development/twrp-t3566563
I have tried at least 5 apps that have needed root and have not had any issues. I haven't tried xposed yet though.
Click to expand...
Click to collapse
And so the bootr.img is 'pre-rooted" so I don't then need to flash "SuperSU-v2.79-201612051815-EMUI5.0.zip" or any other SU zip file, or format the Data partition as some other threads have mentioned, to get root, is that correct?
vouty said:
And so the bootr.img is 'pre-rooted" so I don't then need to flash "SuperSU-v2.79-201612051815-EMUI5.0.zip" or any other SU zip file, or format the Data partition as some other threads have mentioned, to get root, is that correct?
Click to expand...
Click to collapse
I did not format or wipe anything. I simply backed up my boot.img and flashed bootr.img. I did not flash anything else. After that, I rebooted and installed phh Superuser from the play store. That's it.
skrapmetal said:
I did not format or wipe anything. I simply backed up my boot.img and flashed bootr.img. I did not flash anything else. After that, I rebooted and installed phh Superuser from the play store. That's it.
Click to expand...
Click to collapse
Sounds easy enough. I'll give it a try. Then I'm gonna go for getting xposed and adaway working.
hi, i confirm the modified boot.img (b378) and root works with b380 rom ?
Thanks
Jsbcterpper said:
You are right , i agree with you
Click to expand...
Click to collapse
No.
It does work in the L09, check my post on the previous page.
I was rooted on 9.5.4 with the Patched Boot Image. I had 2 modules enabled in magisk (call recording and substratum). Wanted to update to 9.5.5 and did this:
1. Download and install update
2. No reboot
3. Open Magisk and disable the modules
4. Select Install install and then Install to Inactive Slot (After OTA)
5. Rebooted
6. Phone booted so I opened magisk and enabled my modules
7. Rebooted
Now the phone doesn't boot up properly. It goes all the way to first screen asking for my passcode and then turns off and does to stock recovery. Please someone tell me what to do so I don't lose my data!!
Install TWRP, install stock image.
"Bring to life and not delete all" - Are you Thanos?
djsubterrain said:
"Bring to life and not delete all" - Are you Thanos?
Click to expand...
Click to collapse
If I was I would turn a lot of people to ash...
But as for my phone since I was offline the world for 3 hours and got no answers I decided to try to flash stock boot.img
After flashing it in fastboot phone booted up normally and I have everything. Now I'm on 9.5.5 and want to root the phone... Should I go with the TWRP method? I was thinking to delay to flash TWRP since it isn't stable yet. If I open Magisk in phone and select install and then again install and then select option "Select and patch a file" and select boot.img, will it work?
eltarod said:
If I was I would turn a lot of people to ass...
But as for my phone since I was offline the world for 3 hours and got no answers I decided to try to flash stock boot.img
After flashing it in fastboot phone booted up normally and I have everything. Now I'm on 9.5.5 and want to root the phone... Should I go with the TWRP method? I was thinking to delay to flash TWRP since it isn't stable yet. If I open Magisk in phone and select install and then again install and then select option "Select and patch a file" and select boot.img, will it work?
Click to expand...
Click to collapse
"I would turn a lot of people to ass..."
{
"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"
}
The TWRP version is stable enough for use just now. I would flash the rooted boot image (You will lose wifi if you're on 9.5.5) and then flash TWRP installer along with flashing magisk again, then download one of the kernels provided (I'm using ElementalX on 9.5.5 and it's working fine) and flash that in TWRP, then you should have TWRP, root and working wifi, etc.
djsubterrain said:
"I would turn a lot of people to ass..."
The TWRP version is stable enough for use just now. I would flash the rooted boot image (You will lose wifi if you're on 9.5.5) and then flash TWRP installer along with flashing magisk again, then download one of the kernels provided (I'm using ElementalX on 9.5.5 and it's working fine) and flash that in TWRP, then you should have TWRP, root and working wifi, etc.
Click to expand...
Click to collapse
When you say rooted boot.img...What do you mean? I took the stock boot.img, put in phone memory and selected in magisk. Magisk made a new boot.img and flashed that. After that phone didn't boot up like before and went to recovery mode. So to fix it I flashed again stock boot.img
I updated the same way as you (didn't disable my Magisk modules though). Everything went OK, kept root, but something borked in my /system folder and now can't make any changes in it (buildprop, hosts).
I'm not installing any unofficial TWRP, going to reflash the patched boot.img again to see if that works. If not, will go for a clean install. Worth a try?
eltarod said:
When you say rooted boot.img...What do you mean? I took the stock boot.img, put in phone memory and selected in magisk. Magisk made a new boot.img and flashed that. After that phone didn't boot up like before and went to recovery mode. So to fix it I flashed again stock boot.img
Click to expand...
Click to collapse
Rooted boot image : https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-root-oneplus-7-pro-patched-boot-t3931205
Follow that guide but, as I said, your rom is a later version so your wifi will break until you flash a compatible kernel, I'm using ElementalX with 9.5.5 and it's fine.
You would be best installing TWRP as soon as you can from here : https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322 since you'll be best using this to flash ElementalX
I'm guessing you flashed an incremental ota and not the full system image in step one? Might be your issue.
Sent from my GM1917 using Tapatalk
Flash stock boot IMG and uninstall substratum overlay themes, u will always want to do that before u update, then reflash patched boot image, then u can reinstall your themes
---------- Post added at 01:17 AM ---------- Previous post was at 12:55 AM ----------
larsdennert said:
I'm guessing you flashed an incremental ota and not the full system image in step one? Might be your issue.
Sent from my GM1917 using Tapatalk
Click to expand...
Click to collapse
No he said he was able to boot after the update, it was when he enabled his modules, more than likely its a substratum theme issue
I just bought 12s Ultra, but my seller already installed MIUI 13 stable EU.
1. I want to update to MIUI 14, but i dont want to risk anything, since i have no warranty. Why can't i see upgrade options like : "Download update package" or "update settings".
2. If i download latest MIUI 14 EU rom from miui eu site, then "choose update package" , will it just work, or i need to upgrade twrp, or do something more?
3. I live in Turkey, but i can do just fine with official China rom. I just need Android Auto and Garmin Watch app sync. Do these work with the latest official Chinese rom? I'd like to have OTA updates installed automatically. I don't want to upgrade with dirty way, an error can cost me too much.
{
"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"
}
sleepingawake said:
I just bought 12s Ultra, but my seller already installed MIUI 13 stable EU.
1. I want to update to MIUI 14, but i dont want to risk anything, since i have no warranty. Why can't i see upgrade options like : "Download update package" or "update settings".
2. If i download latest MIUI 14 EU rom from miui eu site, then "choose update package" , will it just work, or i need to upgrade twrp, or do something more?
3. I live in Turkey, but i can do just fine with official China rom. I just need Android Auto and Garmin Watch app sync. Do these work with the latest official Chinese rom? I'd like to have OTA updates installed automatically. I don't want to upgrade with dirty way, an error can cost me too much.
Click to expand...
Click to collapse
Update the TWRP(A12) if necessary, download the update via OTA then follow the instructions of the OTA.
To be sure, post a screenshot like this.
Spoiler: ROM
I used to fastboot updates with pc, i don't want to spend my time with those.
This device will get frequently updates from xiaomi, and i'd like to use that advantage. Which way should i go?
Install original chinese rom for ota updates?
I don't want to set everything again and again after each upgrade, for this i need ota updates i guess.
sleepingawake said:
I used to fastboot updates with pc, i don't want to spend my time with those.
This device will get frequently updates from xiaomi, and i'd like to use that advantage. Which way should i go?
Install original chinese rom for ota updates?
I don't want to set everything again and again after each upgrade, for this i need ota updates i guess.
Click to expand...
Click to collapse
Check or install this TWRP twrp-3.7.0_12-v7.2_A12-thor-skkk.img.
Then download the rom(xiaomi.eu_multi_THOR_V14.0.5.0.TLACNXM_v14-13) via ota and update via OTA and TWRP.
Used a Weekly for regular updates.
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/
EDIT:
Once installed the A13 rom, update the TWRP (A12->A13).
NOSS8 said:
Check or install this TWRP twrp-3.7.0_12-v7.2_A12-thor-skkk.img.
Then download the rom(xiaomi.eu_multi_THOR_V14.0.5.0.TLACNXM_v14-13) via ota and update via OTA and TWRP.
Used a Weekly for regular updates.
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/
Click to expand...
Click to collapse
Thanks a lot.
So after i do these, i will get OTA updates occasionally automatically right? I used to install roms from pc on my old devices, but takes too much time researching what to do.
sleepingawake said:
Thanks a lot.
So after i do these, i will get OTA updates occasionally automatically right? I used to install roms from pc on my old devices, but takes too much time researching what to do.
Click to expand...
Click to collapse
Yep, you will get a notification and need to use OTA.
Before performing the update, I advise you to remove the security from the lock screen and restart and then perform the update.
In this way the installation will be done directly and in case of problem your data will be recoverable since decrypted.
NOSS8 said:
Yep, you will get a notification and need to use OTA.
Before performing the update, I advise you to remove the security from the lock screen and restart and then perform the update.
In this way the installation will be done directly and in case of problem your data will be recoverable since decrypted.
Click to expand...
Click to collapse
I checked my installed recovery :
3.6.2_12-Xiaomi12SUltra_v5.6_A12
So without pc method :
I go to recovery, backup recovery, download your link 3.7x version, install recovery, reboot recovery, reboot system. And then install rom same way right.
I checked oem unluck and debugging ON, in case something goes wrong.
Searched a lot, haven't found a proper guide updating recovery sorry.
sleepingawake said:
I checked my installed recovery :
3.6.2_12-Xiaomi12SUltra_v5.6_A12
So without pc method :
I go to recovery, backup recovery, download your link 3.7x version, install recovery, reboot recovery, reboot system. And then install rom same way right.
I checked oem unluck and debugging ON, in case something goes wrong.
Searched a lot, haven't found a proper guide updating recovery sorry.
Click to expand...
Click to collapse
Put the new TWRP in the internal storage then with the TWRP install / select img / select recovery both partitions if asked.
Or with CMD
REC VERSION
fastboot*** flash recovery_ab twrp.img
***After flash used this command:
./fastboot reboot recovery (Power Shell)
fastboot reboot recovery(cmd)
NOSS8 said:
Put the new TWRP in the internal storage then with the TWRP install / select img / select recovery both partitions if asked.
Or with CMD
REC VERSION
fastboot*** flash recovery_ab twrp.img
***After flash used this command:
./fastboot reboot recovery (Power Shell)
fastboot reboot recovery(cmd)
Click to expand...
Click to collapse
CMD is for pc, i dont have a ADB installed pc now.
So for just on phone, my way is gonna work?
TWRP updated from TWRP.
Oh, i forget to check both partitions, should do it again with checked both?
Will install your suggested rom at home. Thanks.
sleepingawake said:
CMD is for pc, i dont have a ADB installed pc now.
So for just on phone, my way is gonna work?
TWRP updated from TWRP.
Oh, i forget to check both partitions, should do it again with checked both?
Will install your suggested rom at home. Thanks.
Click to expand...
Click to collapse
You can download the rom from the phone by modifying the user agent of your browser (PC).
NOSS8 said:
You can download the rom from the phone by modifying the user agent of your browser (PC).
Click to expand...
Click to collapse
Yes, but don't want to waste my mobile internet for 5gb will be home soon.
I did TWRP update by mistake without selecting both partitions option, should i do it again with that option selected, or it will be fine without?
sleepingawake said:
Yes, but don't want to waste my mobile internet for 5gb will be home soon.
I did TWRP update by mistake without selecting both partitions option, should i do it again with that option selected, or it will be fine without?
Click to expand...
Click to collapse
Happened to me too, didn't see a difference.
Just make sure it's up to date.
NOSS8 said:
Happened to me too, didn't see a difference.
Just make sure it's up to date.
Click to expand...
Click to collapse
Thanks i just upgraded to miui 14 with your guide.
But after install finished unzipping messages, i got lots of failed notifications in twrp saying failed to install . And it ended saying : "no os is installed. Restart anyway?"
I was very scared that i bricked the device. After 2 minutes it just started. Seems working now.
What were those errors?
sleepingawake said:
Thanks i just upgraded to miui 14 with your guide.
But after install finished unzipping messages, i got lots of failed notifications in twrp saying failed to install . And it ended saying : "no os is installed. Restart anyway?"
I was very scared that i bricked the device. After 2 minutes it just started. Seems working now.
What were those errors?
Click to expand...
Click to collapse
The rom is installed correctly, ignore the final errors
NOSS8 said:
The rom is installed correctly, ignore the final errors
Click to expand...
Click to collapse
Thanks for your all help. Have a nice day/night.