Related
Hello guys,
I have successfully rooted September update with the help of Flashfire. As there is no fastboot images released at the a time of writing this so I have to make use of dual slots of system. This can be adopted for future OTA's as well:
The process requires you to boot into ur previous slot. It mean that after you have updated you phone boots from updated slot but old slot is still there which can be rooted easily.
Now you have boot from old slot
Code:
fastboot set_active x
x means your old slot before update
Now u have to root this slot by flashing patched boot image.
After successful root use flashfire to backup your updated slot's boot and system , u can use any format I recommend use fastboot flashable.
Now you can use backed up boot to flash on updated slot and enable ever root while flashing.
Now you have rooted your updated slot .
Now you can boot into updated slot by using above code with 'x' being your updated slot identifire.
PS.
Stock September Boot
First boot might take long similar to flashing SuperSU via twrp ( it reboots after boot logo appears)
I used this https://forum.xda-developers.com/mi-5x/how-to/root-mia1-twrp-t3678453 to root my August build.
Google Inc said:
Hi how do i confirm whether a or b slot are previous update?
I need to reboot for further checking?
Click to expand...
Click to collapse
U can guess without rebooting in magisk manager, by boot image location
/dev/block/mmcblk0p22 --> means slot A
/dev/block/mmcblk0p23 --> means slot B
Also fast boot commands can be used for that
Sent from my Mi A1 using Tapatalk
m.atif said:
U can guess without rebooting in magisk manager, by boot image location
/dev/block/mmcblk0p22 --> means slot A
/dev/block/mmcblk0p23 --> means slot B
Also fast boot commands can be used for that
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
I guess slot A is August update and slot B is September update...
Reason: We had slot A activated by default so any new update (say September) will be installed in another slot (say B)...
I rebooted to slot A... opened Settings app -- About Phone -- It says August security patch...
Trying your method to root... Will reply back with the results...
thanks a lot bro
I said that bcz if someone flashes fastboot images , slot a is used for flashing by the provided falsh_all.bat file in stock image file.
Fastboot set _active a or b is not working.
Mr.Crucial said:
Fastboot set _active a or b is not working.
Click to expand...
Click to collapse
Use adb tools from chainfire's autoroot zip
Sent from my Mi A1 using Tapatalk
Google Inc said:
Hi how do i confirm whether a or b slot are previous update?
I need to reboot for further checking?
Click to expand...
Click to collapse
Execute this command in fastboot - fastboot getvar all
m.atif said:
Use adb tools from chainfire's autoroot zip
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
Thanks I have rooted my device with september security patch by using different way but got help from your guide
Greetings good friend! Can someone translate this to lay-man-terms coz it's too technical and although I am trying, it's really hard to understand. ???
---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------
Desire 1007 said:
Thanks I have rooted my device with september security patch by using different way but got help from your guide
Click to expand...
Click to collapse
Mate can you elaborate?? Thank you..
melmarPH said:
Greetings good friend! Can someone translate this to lay-man-terms coz it's too technical and although I am trying, it's really hard to understand.
---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------
Mate can you elaborate?? Thank you..
Click to expand...
Click to collapse
Go to fastboot mode.Enter command in ur pc fastboot set active b or a (which will have old firmware)and boot it.Root your old slot containing august security patch using old cf root and install flashfire
in flashfire load the latest magusk or supersu (which you can download from google)(recovery flashable),select new slot and click flash.
Thats all you get your phone rooted with september security patch.
Desire 1007 said:
Go to fastboot mode.Enter command in ur pc fastboot set active b or a (which will have old firmware)and boot it.Root your old slot containing august security patch using old cf root and install flashfire
in flashfire load the latest magusk or supersu (which you can download from google)(recovery flashable),select new slot and click flash.
Thats all you get your phone rooted with september security patch.
Click to expand...
Click to collapse
This doesn't work with Magisk, you get boot loops.
Incidentally, it looks like the developer of Magisk is looking for bootloop logs at https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/page372
I bet if someone could get some Magisk bootloop logs he could get Magisk working on the A1.
mobadass said:
This doesn't work with Magisk, you get boot loops.
Incidentally, it looks like the developer of Magisk is looking for bootloop logs at https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/page372
I bet if someone could get some Magisk bootloop logs he could get Magisk working on the A1.
Click to expand...
Click to collapse
Yeah! I wish I saw your post sooner. Anyway I flashed the stock boot.img of september and the bootloops ceased albeit with no root
mobadass said:
This doesn't work with Magisk, you get boot loops.
Incidentally, it looks like the developer of Magisk is looking for bootloop logs at https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/page372
I bet if someone could get some Magisk bootloop logs he could get Magisk working on the A1.
Click to expand...
Click to collapse
I didn't state a word about magisk, bcz I tried that in August build itself when magisk 14.1 beta was released , it didn't boot so posted about that in magisk thread too, u can't get any logs if the phone restart from splash screen again and again that's bootloop, some kernels have ADB enabled by default in kernel that way we can have logs but it's not possible in stock boot patched by magisk.
Even flashing magisk from flashfire gives same result.
Help!!! Unable to update to September
Hi,
I'm on the August update and I have successfully rooted. But I am unable to install September OTA to update. Can you please advise?
ForTheOne said:
Hi,
I'm on the August update and I have successfully rooted. But I am unable to install September OTA to update. Can you please advise?
Click to expand...
Click to collapse
If u happen to have a unmodified system partion , only flash stock boot.img through fastboot or flashfire (note to disable ever root)
If u have a modified system , them flash system.img from August update fastboot files with boot.img , I will suggest you to do this as you don't know if have modified the system or not (even remounting system bricks OTA). To do so
Code:
fastboot flash system_x system/image/location.img
fastboot flash boot_x boot/image/location.img
x means ur current active slot (a or b)
U can find stock files from miui.com downloads section
Anyine has normal boot.img for october update? or even modified?
any link to stock september boot image?
Hey mates, here is a simple guide to root all your future updates that come for our beloved Mi A1.
Requirement
should have bootloader unlocked
some knowledge of fastboot mode
latest updatesupersu.zip in hand (can be downloaded from xda)
prerooted one system with flasfire installed
Stepwise guide to root new updated system
If anybody have old system rooted he can root new updated system very easily by using flashfire and super su recovery flashable file.
Steps are
1. Go to rooted old system. Install flashfire.
2. Download update supersu 2.82 sr4
3. Start flashfire and press instal zip and select supersu sr4
4. Select the system which you want to root and click ok
5. Now select boot option and select the system you want to boot after flashing (most likely updated system)
6. Press flash
7. Voila. Its done
8. You will boot into new rooted system
9. This will also apply for all future updates too.
Desire 1007 said:
Go to fastboot mode.Enter command in ur pc fastboot set active b or a (which will have old firmware)and boot it.Root your old slot containing august security patch using old cf root and install flashfire
in flashfire load the latest magusk or supersu (which you can download from google)(recovery flashable),select new slot and click flash.
Thats all you get your phone rooted with september security patch.
Click to expand...
Click to collapse
Working great.
I tried and succeeded.
Looks really easy method even to root all future updates.
You are a genius
Thanks bro
Desire 1007 said:
Go to fastboot mode.Enter command in ur pc fastboot set active b or a (which will have old firmware)and boot it.Root your old slot containing august security patch using old cf root and install flashfire
in flashfire load the latest magusk or supersu (which you can download from google)(recovery flashable),select new slot and click flash.
Thats all you get your phone rooted with september security patch.
Click to expand...
Click to collapse
Please tell me what should I do next
I am now on September update which is on slot b
I went to fastboot and activated slot a and rooted using cf root and installed flashfire
In flashfire I selected Magisk 14.2 and flashed it on slot b
I rebooted
Right now I have the update prompt asking me whether to download and install the September update
What should I do?
Ex-Hunter said:
Please tell me what should I do next
I am now on September update which is on slot b
I went to fastboot and activated slot a and rooted using cf root and installed flashfire
In flashfire I selected Magisk 14.2 and flashed it on slot b
I rebooted
Right now I have the update prompt asking me whether to download and install the September update
What should I do?
Click to expand...
Click to collapse
make slot A active using fastboot
Desire 1007 said:
Go to fastboot mode.Enter command in ur pc fastboot set active b or a (which will have old firmware)and boot it.Root your old slot containing august security patch using old cf root and install flashfire
in flashfire load the latest magusk or supersu (which you can download from google)(recovery flashable),select new slot and click flash.
Thats all you get your phone rooted with september security patch.
Click to expand...
Click to collapse
Got stuck in bootloop after flashing magisk 14.2 to new slot any idea why?
s0917 said:
Got stuck in bootloop after flashing magisk 14.2 to new slot any idea why?
Click to expand...
Click to collapse
I have personally checked supersu v2.82 sr4.
If you are facing bootloop go to old slot and flash supersu using flashfire
s0917 said:
Got stuck in bootloop after flashing magisk 14.2 to new slot any idea why?
Click to expand...
Click to collapse
Please get the logs and post them here https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/page372
The developer of Magisk is wanting logs so they can fix the A1.
s0917 said:
Got stuck in bootloop after flashing magisk 14.2 to new slot any idea why?
Click to expand...
Click to collapse
For how much time you have been in bootloop. Is bootanimation running.
I think after flashing root you have to wait for about 10 minutes before start of phone.
Otherwise do whatever op suggested.
Desire 1007 said:
Go to fastboot mode.Enter command in ur pc fastboot set active b or a (which will have old firmware)and boot it.Root your old slot containing august security patch using old cf root and install flashfire
in flashfire load the latest magusk or supersu (which you can download from google)(recovery flashable),select new slot and click flash.
Thats all you get your phone rooted with september security patch.
Click to expand...
Click to collapse
Mr.Crucial said:
For how much time you have been in bootloop. Is bootanimation running.
I think after flashing root you have to wait for about 10 minutes before start of phone.
Otherwise do whatever op suggested.
Click to expand...
Click to collapse
So my phone keeps rebooting on its own like
Vibrate then the "Lock your bootloader warning" then the bootanimtion * reboot
Mr.Crucial said:
For how much time you have been in bootloop. Is bootanimation running.
I think after flashing root you have to wait for about 10 minutes before start of phone.
Otherwise do whatever op suggested.
Click to expand...
Click to collapse
Confirmed: With Magisk 14.2 you get stuck in a bootloop.
Ex-Hunter said:
Confirmed: With Magisk 14.2 you get stuck in a bootloop.
Click to expand...
Click to collapse
Can you help submit the log? I'm having trouble getting the log files.
Desire 1007 said:
Go to fastboot mode.Enter command in ur pc fastboot set active b or a (which will have old firmware)and boot it.Root your old slot containing august security patch using old cf root and install flashfire
in flashfire load the latest magusk or supersu (which you can download from google)(recovery flashable),select new slot and click flash.
Thats all you get your phone rooted with september security patch.
Click to expand...
Click to collapse
By your guide, you mean, In fastboot active august slot, & boot it. root it using cf root method.
then load flashfire & flash supersu on slot september, then reboot.
Will the phone automatically boot the september slot, or do we have to go again in fastboot, & set active september slot ?
osrox said:
By your guide, you mean, In fastboot active august slot, & boot it. root it using cf root method.
then load flashfire & flash supersu on slot september, then reboot.
Will the phone automatically boot the september slot, or do we have to go again in fastboot, & set active september slot ?
Click to expand...
Click to collapse
There are two methods
1. you have to set active system in fastboot
2.Before flashing ,cluck reboot and select updated slot
s0917 said:
Can you help submit the log? I'm having trouble getting the log files.
Click to expand...
Click to collapse
Me too. I'm not able to get any logs
Deleted
Hi, can i relock bootloader after root?
Harry Tang said:
Hi, can i relock bootloader after root?
Click to expand...
Click to collapse
Why you want to relock
You should not relock device after rooting as it can bootloop.
Still if you wish, then try it
Can any one help me ?
How to make slot B active ?
rex28818 said:
Can any one help me ?
How to make slot B active ?
Click to expand...
Click to collapse
Put your phone in fastboot mode and send command from pc
fastboot set_active b
I am rooted now.. Can I enable camera 2 api?? Someone please confirm
So as the official bootloader unlock broadened the audience of this from tinkerers/developers to basically everyone I thought this guide might me helpful for some...
PREREQUISITES:
- Unlocked bootloader (official or unofficial)
- latest magisk manager installed on phone (https://github.com/topjohnwu/Magisk/releases)
- latest fastboot and adb binaries from google(https://developer.android.com/studio/releases/platform-tools)
- latest twrp.img to boot (NOT FLASH), zip not needed (https://eu.dl.twrp.me/NB1/)
- Fully stock partitions (if you do not have this reflash latest stock via ostla), as OTA updates will do a integrity check.
- PC with WIN/OSX/LINUX with USB port^^ (on windows you might have to add .exe to the commands)
- disable automatic system updates in developer options, as you will still have to manually root the updated partition, so this makes sure you don't miss it. You still get notifications on available updates and can apply them easily(as you will see)
SETUP_STEPS:
1. Go into Magisk manager and "just download" the latest zip
2.1 Run
Code:
adb reboot bootloader
or reboot into download/fastboot mode via other means
2.2 Run
Code:
fastboot boot twrp-3.2.3-1-NB1.img
(change this when your version of twrp differs)
2.3 Flash the .zip magisk downloaded in 1.)
2.4 Reboot.
Congratulations you now have root!
STEPS_TO_UPDATE:
1. Go into Magisk Manager -> Uninstall -> Restore Images
2. Apply Update, DO NOT REBOOT YET
3. When step to finished and it promts you to reboot go into Magisk Manager -> Install -> Install to inactive Slot
Congratulations you can now reboot and will have an updated Android while keeping full root.
ALTERNATIVE GUIDE (without twrp, using prerooted boot.img)
(works for newest patch level, where twrp isn't working yet)
this guide works on newest patches as long as someone provides a prerooted boot.img.
So basically you either need a boot.img available or twrp...
Hopefully this helps until TWRP is compatible with September Security Patch
LINKS:
stock boot.img: (may to october patches)
https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
prerooted boot.img: (may to october patches)
https://cloud.vault81.de/s/AeHiE5HR2qonb3N
PREREQUISITES:
- same as above minus twrp
- patched/prerooted boot image (either create it yourself or use link provided here)
STEPS_TO_ROOT:
0.
Code:
adb reboot bootloader
or get into download mode otherwise
1.
Code:
fastboot boot NB1_prerooted_boot.img
1.1. The phone will boot into an temporarily rooted state,
2. Use magisk manager-> Install -> "Direct Install" to persist the root.
3. Reboot
Congrats you now have root even on versions where twrp isn't working yet....
Edit1:
Added link to all stock boot images from may to october security
Edit2:
Did the same for magisk prerooted
Edit3:
Added November images thanks to @czupyt
TWRP isnt working right now so whoever updated to September patch cant do anything except unlock bootloader. Unless someone can pull a boot.img from the newest patch so we can all patch it through Magisk and get root.
ironman38102 said:
TWRP isnt working right now so whoever updated to September patch cant do anything except unlock bootloader. Unless someone can pull a boot.img from the newest patch so we can all patch it through Magisk and get root.
Click to expand...
Click to collapse
I can try to do that once I get back home tomorrow...
I have working magisk on september patch so I should have both prerooted and Stock (cause Magisk backups those)
Trissi said:
I can try to do that once I get back home tomorrow...
I have working magisk on september patch so I should have both prerooted and Stock (cause Magisk backups those)
Click to expand...
Click to collapse
That would be much appreciated. Alot of people who just unlocked bootloader cant root and the maintainer of our TWRP will take a couple of days
indeed
ironman38102 said:
TWRP isnt working right now so whoever updated to September patch cant do anything except unlock bootloader. Unless someone can pull a boot.img from the newest patch so we can all patch it through Magisk and get root.
Click to expand...
Click to collapse
Simple Solution: A/B Partition System.
One Slot is the September Update, the other is August Update.
Update to September, Unlock, witch to other Slot with August Update, Boot Offical TWRP 3.2.3-0 (-1 not booting tho).
Now you can Install the Install Zip for the August BL and Magisk.
Bootup and use Magisk for Inactive Slot.
So did I, but I'm still on August Slot, I'll try to root the September Boot Partiton, and Install TWRP later when Fix arrived.
But rooted September doens't seem very... Stable
LoaderFabi said:
Simple Solution: A/B Partition System.
One Slot is the September Update, the other is August Update.
Update to September, Unlock, witch to other Slot with August Update, Boot Offical TWRP 3.2.3-0 (-1 not booting tho).
Now you can Install the Install Zip for the August BL and Magisk.
Bootup and use Magisk for Inactive Slot.
So did I, but I'm still on August Slot, I'll try to root the September Boot Partiton, and Install TWRP later when Fix arrived.
But rooted September doens't seem very... Stable
Click to expand...
Click to collapse
I'm already about to install the September patch again. I downgraded to May so I could root my phone and provide the clean boot.img from the stock September so people can root without twrp. And honestly A/B partition is still new to me that I still don't understand it
ironman38102 said:
I'm already about to install the September patch again. I downgraded to May so I could root my phone and provide the clean boot.img from the stock September so people can root without twrp. And honestly A/B partition is still new to me that I still don't understand it
Click to expand...
Click to collapse
A/B system is not Complex at all. It's just having 2x a Partiton Group (Boot, System, OEM and Recovery I think) and having the ability with Fatboot to simply switch between group A and group B.
You Inital Set up Partiton A (Nokia did for us with Nougat 7.1.1). If you Update, the Update will be extracted to Partition B, aftzer finishing you reboot to Partiton Group B, leaving group A untouched in Case of Error on Partition B.
That's it pretty much.
LoaderFabi said:
A/B system is not Complex at all. It's just having 2x a Partiton Group (Boot, System, OEM and Recovery I think) and having the ability with Fatboot to simply switch between group A and group B.
You Inital Set up Partiton A (Nokia did for us with Nougat 7.1.1). If you Update, the Update will be extracted to Partition B, aftzer finishing you reboot to Partiton Group B, leaving group A untouched in Case of Error on Partition B.
That's it pretty much.
Click to expand...
Click to collapse
No I get that but its just that I forget cuz this is my first phone with a/b partition. Anyway I got the phone to latest patch rooted so I'll see if I can get the untouched img
i'm on september security update and followed the seconde guide, but still show the android logo not booting the phone
eric194 said:
i'm on september security update and followed the seconde guide, but still show the android logo not booting the phone
Click to expand...
Click to collapse
On what step? Was it after you completed the guide? Or did the patched image not boot already?
If the patched image worked but it din't afterwards, you should reflash the stock_boot.img and redo the guide again because you probably flashed twrp and broke your bootloader...
As you can see in the prerequisites this guide requires a stock bootloader to start.
Trissi said:
On what step? Was it after you completed the guide? Or did the patched image not boot already?
If the patched image worked but it din't afterwards, you should reflash the stock_boot.img and redo the guide again because you probably flashed twrp and broke your bootloader...
As you can see in the prerequisites this guide requires a stock bootloader to start.
Click to expand...
Click to collapse
Nop I didn't flash twrp & Im on stock bootloader fresh september no modifications
eric194 said:
Nop I didn't flash twrp & Im on stock bootloader fresh september no modifications
Click to expand...
Click to collapse
So did the prerooted Image Boot?
If so it basically has to be your boot/system partition(I had mine compromised too and couldn't fix it with just flashing boot.img had to reflash everything via ostla)
If even the prerooted Image didnt boot im sorry i don't really know how to help, as I have working root with Magisk on September patch and the Image boots just fine for me....
eric194 said:
Nop I didn't flash twrp & Im on stock bootloader fresh september no modifications
Click to expand...
Click to collapse
Also you could Switch slots to revert back to august Patch and use the normal twrp guide then... And run the September Update via the magisk method
Trissi said:
Also you could Switch slots to revert back to august Patch and use the normal twrp guide then... And run the September Update via the magisk method
Click to expand...
Click to collapse
Ok I will try that hope it'll work
Edit : thanks dude it worked
Hey everyone;
My Nokia TA-1004 is on the July SP (4.88B_SP02) with unlocked bootloader (unofficial method), TWRP and Magisk installed.
Where can I find a stock boot.img to flash? I tried flashing the boot.img on this thread and although I can boot fine my wifi will be broken (I tried and had to restore nandroid backup). I also tried following the guide here but my OSTLA won't get past "Flashing Service Bootloader".
Any help?
Xayar said:
Hey everyone;
My Nokia TA-1004 is on the July SP (4.88B_SP02) with unlocked bootloader (unofficial method), TWRP and Magisk installed.
Where can I find a stock boot.img to flash? I tried flashing the boot.img on this thread and although I can boot fine my wifi will be broken (I tried and had to restore nandroid backup). I also tried following the guide here but my OSTLA won't get past "Flashing Service Bootloader".
Any help?
Click to expand...
Click to collapse
Flash the full Stock build (i think its even may patch), via ostla (https://forum.xda-developers.com/no...ia-8-official-firmware-links-updated-t3678487), then follow this guide then reapply all updates by following the update steps...
So which file do I have to download from https://drive.google.com/drive/folders/1t64iHuQQjmMnzcujZtjYplh6ipbiF6Cw ? I tried with the 488B one and got stuck on "flashing service bootloader"...
Xayar said:
So which file do I have to download from https://drive.google.com/drive/folders/1t64iHuQQjmMnzcujZtjYplh6ipbiF6Cw ? I tried with the 488B one and got stuck on "flashing service bootloader"...
Click to expand...
Click to collapse
Are you trying to use OST LA 6.1.2? Cuz that doesnt work
Hello everyone,
First of all, sorry if i post it in the wrong section and if i am not always making sense.
So here is my situation :
i have a HTC U11 which i rooted a long time ago with TWRP & SU.
I then switch SU to Magisk (a year ago), because i needed to hide my root from few apps.
I wanted to update magisk Manager, but i lamely failed
(i went to recovery mode, installed the uninstaller ZIP for Magisk in order to put a version above 18 but then i had a boot.img missing error)
So i did restore an old backup that i had from 2017...
Currently i have :
Version android : 7.1.1
Firmware version : 1.27.400.8
Magisk version : 18.1
Magisk Manager Version : v7.1.1
TWRP Version : 3.3.0.0-ocn
My questions :
I want to update my firmware. I mean, my phone tells me there is an update. Is it what we call OTA ?
After i've downloaded the new firmware version (1.27.400.21), i select install now, and my phone reboots to Recovery mode, but asks me for a password (to decrypt data).
What the hell is that ?
Also, i would like to be able to still install this new version (and the futures ones).
How do i do that ?
Is it possible to upgrade the Android version too ?
I wish not to have to wipe or lose data.
What's the point to wipe data, dalvik, cache ?
When you do it do you lose your personnal data ?
Many thanks for your helps and support
toto_rigolo said:
Hello everyone,
First of all, sorry if i post it in the wrong section and if i am not always making sense.
So here is my situation :
i have a HTC U11 which i rooted a long time ago with TWRP & SU.
I then switch SU to Magisk (a year ago), because i needed to hide my root from few apps.
I wanted to update magisk Manager, but i lamely failed
(i went to recovery mode, installed the uninstaller ZIP for Magisk in order to put a version above 18 but then i had a boot.img missing error)
So i did restore an old backup that i had from 2017...
Currently i have :
Version android : 7.1.1
Firmware version : 1.27.400.8
Magisk version : 18.1
Magisk Manager Version : v7.1.1
TWRP Version : 3.3.0.0-ocn
My questions :
I want to update my firmware. I mean, my phone tells me there is an update. Is it what we call OTA ?
After i've downloaded the new firmware version (1.27.400.21), i select install now, and my phone reboots to Recovery mode, but asks me for a password (to decrypt data).
What the hell is that ?
Also, i would like to be able to still install this new version (and the futures ones).
How do i do that ?
Is it possible to upgrade the Android version too ?
I wish not to have to wipe or lose data.
What's the point to wipe data, dalvik, cache ?
When you do it do you lose your personnal data ?
Many thanks for your helps and support
Click to expand...
Click to collapse
aq
Find out your cid/mid
You will need to flash the appropriate ruu (nougot) for your phone from here (sd card method)
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/htmlview
in order to receive the ota updates. And yes you will lose everything. Backup as much as you can . And once you go to pie there is no going back unless s-off. ( There is another way but more involved) . hth
Thanks for your reply.
How do i find my cid/mid ?
I tried yesterday to use adb, but i could NOT find my device in download mode... The only way i was able to see it was to boot in recovery mode.
Can i still get my cid & mid if can find my device whilst it's in recovery mode ?
So i understood that i need to download the right file, rename it, put it on the root of the SD CARD and then boot my phone in bootlader mode.
Don't i have at some point specify the ZIP file to use ? Does it mean it will detect it automatically ?
Then why doesn't it work if i put it on the root of the internal sotrage of my phone ?
If i flash a RUU, will my phone still be rooted and unlocked ?
toto_rigolo said:
Thanks for your reply.
How do i find my cid/mid ?
I tried yesterday to use adb, but i could NOT find my device in download mode... The only way i was able to see it was to boot in recovery mode.
Can i still get my cid & mid if can find my device whilst it's in recovery mode ?
So i understood that i need to download the right file, rename it, put it on the root of the SD CARD and then boot my phone in bootlader mode.
Don't i have at some point specify the ZIP file to use ? Does it mean it will detect it automatically ?
Then why doesn't it work if i put it on the root of the internal sotrage of my phone ?
If i flash a RUU, will my phone still be rooted and unlocked ?
Click to expand...
Click to collapse
I believe the adb command is "getvar all" while in the download mode. get the cid/ mid number reboot then get matching nougot ruu zip. rename to 2pzcimg. zip place in the root of sd card boot to download mode not bootloader, it will detect automatically, hth
Thanks.
Will my phone still be rooted ?
Will i have to reinstall Magisk & Magisk Manager ?
toto_rigolo said:
Thanks.
Will my phone still be rooted ?
Will i have to reinstall Magisk & Magisk Manager ?
Click to expand...
Click to collapse
Oh no it won't be, you will have to reinstall twrp, Magisk,
fair enough.
but sadly, adb doesn't work on my computer. I can't see my phone.
I only get something when my phone is in recovery mode.
download more & bootloader mode, i can't find it.
toto_rigolo said:
fair enough.
but sadly, adb doesn't work on my computer. I can't see my phone.
I only get something when my phone is in recovery mode.
download more & bootloader mode, i can't find it.
Click to expand...
Click to collapse
Try installing htc sync manager then reboot and run adb. You just may need the right drivers
I have read more about it and you're right it should be something like that.
Also, once i have flashed the RUU, rooted again, installed TWRP & Magisk, will i still be able to update OTA ?
I don't understand when some people say they uninstalled Magisk, intall the OTA and install Magisk back on...
Is it really the way to do it ? To be able to install latest OTAs ?
toto_rigolo said:
I have read more about it and you're right it should be something like that.
Also, once i have flashed the RUU, rooted again, installed TWRP & Magisk, will i still be able to update OTA ?
I don't understand when some people say they uninstalled Magisk, intall the OTA and install Magisk back on...
Is it really the way to do it ? To be able to install latest OTAs ?
Click to expand...
Click to collapse
You will have to install ota before rooting , once rooted or twrp installed Ota will not install. This is my understanding, if someone has a different approach please chime in. Installing just the firmware is a different animal and requires more reading!! Hth
Okay so we are on the same page.
So my question is ow do you keep installing OTAs when your phone rooted or with TWRP ??
also i remember my cid is HTC__060 which i believe is india.
Is there anyway i can change it to Europe ? I mean, is there any interest for me to do so ?
toto_rigolo said:
Okay so we are on the same page.
So my question is ow do you keep installing OTAs when your phone rooted or with TWRP ??
also i remember my cid is HTC__060 which i believe is india.
Is there anyway i can change it to Europe ? I mean, is there any interest for me to do so ?
Click to expand...
Click to collapse
Ota will stop once twrp is installed, I really don't see a benefit changing cid, but that's up to u ?
To install an OTA with twrp you have to:
1. Download the OTA in zip format (search in this forum).
2. Copy it to mobile memory.
3. Reboot to twrp and apply manually the zip.
If you are going to change the Cid, change to Taiwan version (that region has received more updates than the rest of the world).
Hi, today i flash the december update in my pixel 6a, now i can´t root, magisk patch the image but when i flash it (fastboot flash boot magisk-patched.img) the phone join in a bootloop and need to reinstall the rom, any help?
I have seen below another thread with the same problem but they talk about the QPR2 beta and I don't know if the same procedure applies with the December update.
Thanks!
What do you mean? If bootloader is unlocked and you run 'fastboot flash boot "file" ' will it work fine.
You can also check the magic managers logs on /cache.
dannyzamora said:
Hi, today i flash the december update in my pixel 6a, now i can´t root, magisk patch the image but when i flash it (fastboot flash boot magisk-patched.img) the phone join in a bootloop and need to reinstall the rom, any help?
I have seen below another thread with the same problem but they talk about the QPR2 beta and I don't know if the same procedure applies with the December update.
Thanks!
Click to expand...
Click to collapse
Make sure you don't have any Magisk mods that may need disabling and updating.
And no, the same procedure does not apply for the stable December update as it does for QPR2 Beta 1.
JonasHS said:
What do you mean? If bootloader is unlocked and you run 'fastboot flash boot "file" ' will it work fine.
You can also check the magic managers logs on /cache.
Click to expand...
Click to collapse
Yes, that is the procedure I am referring to, the one I have always used, it is strange, as I said, I have followed the same steps as always:
1. Download Factory image of december for Pixel 6a (the last one available in the web).
2. Extract boot.img
3. Patch it with latest magisk app (25.2)
4. Reboot to fastboot
5. Use command "fastboot flash boot magisk-patched.img"
The command is applied correctly but when rebooting the terminal stays in the "Google" logo and after a while it reboots and returns to the same "Google" screen, so in a loop.
Lughnasadh said:
Make sure you don't have any Magisk mods that may need disabling and updating.
An no, the same procedure does not apply for the stable December update as it does for QPR2 Beta 1.
Click to expand...
Click to collapse
I don't have any modules installed, it's a clean install of everything.
It will sound stupid but... I did the steps indicated in the other thread and I have solved the problem, I have root.
I downloaded the december image of the Pixel 7 Pro, extracted the boot.img, patched it with magisk and flashed it with the usual command "fastboot flash boot magisk-patched.img" and it let me boot without problems and working root.
thats crazy, Im on december update A13 and I had no issues whatsoever.
booted the image and then flashed through magisk instead of flashing it directly but still... if it were broken that wouldnthave worked
G5-User7080 said:
thats crazy, Im on december update A13 and I had no issues whatsoever.
booted the image and then flashed through magisk instead of flashing it directly but still... if it were broken that wouldnthave worked
Click to expand...
Click to collapse
I know, the truth is that it makes no sense that I have given me this problem because I did not see anyone else with the December update talking about this particular problem, the closest thing was the post I mentioned with the beta, the phone had just arrived from the SAT but I do not think this influenced the problem, it came with the November update and I updated it to the December update.
You mentionned you downloaded the image for the Pixel 7 pro. I assume you made a type and are not flashing a pixel 7 pro image to a pixel 6a? If not then get the right image file.
Otherwise I suggest using the Pixel Flasher software posted in this forum. It's a really good piece of software.
No hassle with manual flashing anymore.
With Pixel Flasher I even update to new security patches with keeping root in like 4-10 minutes, by just downloading the image and then clicking a couple buttons