So, I rooted my device following this https://forum.xda-developers.com/nokia-8/how-to/guide-how-to-root-nokia-8-ability-to-t3848390, but I cannot update my nokia...
The only thing I did different was that I had to rollback my device (with this guide) to June update, and then proceed accordingly.
When I try to update now, I keep getting an error on the update: "Couldn't update. Installation problem".
Can someone please help me? I am ok with both manual or automatic updates, but I need to update.
You only need to flash the stock (untouched) version of the boot partition to the active slot with relevant patch, which is June version at your occasion. Go to this page: https://forum.xda-developers.com/nokia-8/development/nb01-stock-boot-imgs-fixing-wifi-t3854310
***
Edit: See my second post.
Also there is magisk uninstall feature, which you can restore the partition to stock and update and then magisk-root the inactive partition (newly installed system).
I have not upraded my phone, yet. That is, I didn't try anything I mentioned here.
Click to expand...
Click to collapse
Dr. Slump said:
You only need to flash the stock (untouched) version of the boot partition to the active slot with relevant patch, which is June version at your occasion. Go to this page: https://forum.xda-developers.com/nokia-8/development/nb01-stock-boot-imgs-fixing-wifi-t3854310
Click to expand...
Click to collapse
Thanks, I'm in the same situation, unlocked bootloader and rooted on the October patch, do I flash the stock Oct patch and then update via OTA?
Thanks!
vonManstein said:
Thanks, I'm in the same situation, unlocked bootloader and rooted on the October patch, do I flash the stock Oct patch and then update via OTA?
Thanks!
Click to expand...
Click to collapse
That is right. You are welcome.
Also there is magisk uninstall feature, which you can restore the partition to stock and update and then magisk-root the inactive partition (newly installed system).
I have not upraded my phone, yet. That is, I didn't try anything I mentioned here. You may verify the ideas by wandering at some topics like that:
https://forum.xda-developers.com/nokia-8/how-to/guide-how-to-root-nokia-8-ability-to-t3848390
Dr. Slump said:
You only need to flash the stock (untouched) version of the boot partition to the active slot with relevant patch, which is June version at your occasion. Go to this page: https://forum.xda-developers.com/nokia-8/development/nb01-stock-boot-imgs-fixing-wifi-t3854310
***
Edit: See my second post.
Click to expand...
Click to collapse
The magisk uninstall have not worked, the same error persists... I'm gonna try the first method you mentioned, and will be back with results, thanks!
Edit: also, could you please provide steps for doing that?
Not sure if supposed to do that through Nokia software, twrp or fastboot.
Thanks again
guideo said:
The magisk uninstall have not worked, the same error persists... I'm gonna try the first method you mentioned, and will be back with results, thanks!
Edit: also, could you please provide steps for doing that?
Not sure if supposed to do that through Nokia software, twrp or fastboot.
Thanks again
Click to expand...
Click to collapse
It is "fastboot flash". It seems OK. This is what I will do if magisk uninstall doesn't work for me. But, again, you should know that I have not tried this yet.
Also, if your plan is to upgrade to pie, AFAIK there is some preliminary problems with it. They are mentioned in relevant topics here. I think it is better to wait for a better version.
Dr. Slump said:
It is "fastboot flash". It seems OK. This is what I will do if magisk uninstall doesn't work for me. But, again, you should know that I have not tried this yet.
Also, if your plan is to upgrade to pie, AFAIK there is some preliminary problems with it. They are mentioned in relevant topics here. I think it is better to wait for a better version.
Click to expand...
Click to collapse
Hi, thanks for the help.
The command fastboot flash boot "june.img" worked, but now I can't turn on my WiFi... It turns on then off again on its own...
Im gonna tinker around a little with it, but probably be back on the 25th or 26th, due to xmas.
Thanks a lot and merry christmas to you
Worked with may patch...
I think that my device was trying to apply the June patch, and so it was in may patch.
Ive installed it and now the update is ongoing.
Gonna try to re-root it after the holidays
I'm not going to apply the pie update, gonna wait for a while.
Thanks a lot man! You saved my device :laugh:
guideo said:
Worked with may patch...
I think that my device was trying to apply the June patch, and so it was in may patch.
Ive installed it and now the update is ongoing.
Gonna try to re-root it after the holidays
I'm not going to apply the pie update, gonna wait for a while.
Thanks a lot man! You saved my device :laugh:
Click to expand...
Click to collapse
I just got to the september update (should have stopped in august), but now I cannot root my device... TWRP wont boot, neither the prerooted september image.
If you have any idea about this, I would really appreciate! Thanks!
guideo said:
I just got to the september update (should have stopped in august), but now I cannot root my device... TWRP wont boot, neither the prerooted september image.
If you have any idea about this, I would really appreciate! Thanks!
Click to expand...
Click to collapse
Thanks, marry christmas to you, too. TWRP won't work because there isn't a dedicated recovery partition anymore, it was patched into boot partition and wiped out with the flashing
If you are trying the prerooted boot image with "fastboot boot", it is broken after the august update. If not, maybe it is better to download the stock image to /sdcard and patch it with your latest magisk, later upload it to computer and "fastboot flash" it.
So guys any way to root official pie with december security patch?
nabil427 said:
So guys any way to root official pie with december security patch?
Click to expand...
Click to collapse
You can find a twrp-prepatched boot image for Pie + December Patch here: https://cloud.tmsp.io/s/nb1?path=/Boot Images/2018-12
Enter download mode and use fastboot to flash it into your active boot partition (either boot_a or boot_b, depending on the output of "fastboot getvar current-slot").
Then boot into recovery mode (using adb reboot recovery, or by shutting the phone down and pressing volume up while connecting it to the PC) and flash the Magisk installer .zip
THMSP said:
You can find a twrp-prepatched boot image for Pie + December Patch here: https://cloud.tmsp.io/s/nb1?path=/Boot Images/2018-12
Enter download mode and use fastboot to flash it into your active boot partition (either boot_a or boot_b, depending on the output of "fastboot getvar current-slot").
Then boot into recovery mode (using adb reboot recovery, or by shutting the phone down and pressing volume up while connecting it to the PC) and flash the Magisk installer .zip
Click to expand...
Click to collapse
Hi,
thank you for your help but i'm stuck in boot here are the commands I did:
C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe getvar current-
slot
current-slot: b
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe boot twrp-3.2.3
-1-NB1.img --slot=b
downloading 'boot.img'...
OKAY [ 0.127s]
booting...
OKAY [ 5.208s]
finished. total time: 5.337s
I've also tried to boot on TWRP 3.2.3-1 but same issue I could not boot onto it and then flash it.
Any Idea ?
Regards
>> Hi, never mind working OK thx
Dr. Slump said:
Thanks, marry christmas to you, too. TWRP won't work because there isn't a dedicated recovery partition anymore, it was patched into boot partition and wiped out with the flashing
If you are trying the prerooted boot image with "fastboot boot", it is broken after the august update. If not, maybe it is better to download the stock image to /sdcard and patch it with your latest magisk, later upload it to computer and "fastboot flash" it.
Click to expand...
Click to collapse
This worked for me with September boot. Just did what you said and then "fastboot flash boot patched_boot.img".
Thanks again
Related
So, I wiped all data, system, cache, internal storage using TWRP and then I flash the system.img to System Image and boot.img to Boot into 2 slots (A & B). Consequently, I lose TWRP and root. I have gone back to May Security Patch Nokia 8 TA-1004. I have updated and updated up until October 2018 Patch.
Then, I tried to use "fastboot boot twrp.img", however it doesn't work. It is just stuck to POWERED BY ANDROID LOGO. Flashing twrp will break the wifi and I do not want that. Anybody has solutions for this? I can't get it to boot to TWRP. I use Android stock recovery and apply update in SD Card, not working as well.
I really want to have access root. All because of that stupid random restart occurs in this thread https://forum.xda-developers.com/nokia-8/help/nokia-8-sudden-restart-occurred-randomly-t3852357
Note: During flashing system.img which reverts back to stock one, I didn't use fastboot command. I use TWRP to revert back.
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
https://drive.google.com/file/d/11A8-jK0hm4j-ah3HwPpk8i_hwcoIwPBx/view?usp=drivesdk
ironman38102 said:
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
https://drive.google.com/file/d/11A8-jK0hm4j-ah3HwPpk8i_hwcoIwPBx/view?usp=drivesdk
Click to expand...
Click to collapse
Is this the latest stock boot image (october patch)?
For resolve a lower security than september can't boot to twrp try this method.
Boot to download mode. Then Use command.
Fastboot reboot bootloader => for enter again download mode
Fastboot boot twrp.... It will go to twrp well.
Topogigi said:
Is this the latest stock boot image (october patch)?
Click to expand...
Click to collapse
Um I think cuz Magisk took this backup right during the Install to Second Slot option
ironman38102 said:
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
https://drive.google.com/file/d/11A8-jK0hm4j-ah3HwPpk8i_hwcoIwPBx/view?usp=drivesdk
Click to expand...
Click to collapse
This is October patch? If it does, you are a lifesaver.
ValKyre said:
For resolve a lower security than september can't boot to twrp try this method.
Boot to download mode. Then Use command.
Fastboot boot bootloader => for enter again download mode
Fastboot boot twrp.... It will go to twrp well.
Click to expand...
Click to collapse
YOU SIR, ARE ROCK. This is very much working for me. I can boot already to twrp. No longer stuck in POWERED BY ANDROID LOGO.
Although you have mistyped the command. It should be "fastboot reboot bootloader". Anyway, thank you. I have given my thanks to you.
godofknife said:
This is October patch? If it does, you are a lifesaver.
YOU SIR, ARE ROCK. This is very much working for me. I can boot already to twrp. No longer stuck in POWERED BY ANDROID LOGO.
Although you have mistyped the command. It should be "fastboot reboot bootloader". Anyway, thank you. I have given my thanks to you.
Click to expand...
Click to collapse
Yup ... Sorry with my head not remember true command hehe
ironman38102 said:
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
Click to expand...
Click to collapse
So can i use this img to root with Magisk with patch boot image option? Is this October patch?
Edit: Stuck on Powered by Android logo => not October boot img
Mo4o293 said:
So can i use this img to root with Magisk with patch boot image option? Is this October patch?
Edit: Stuck on Powered by Android logo => not October boot img
Click to expand...
Click to collapse
My bad I guess
ironman38102 said:
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
https://drive.google.com/file/d/11A8-jK0hm4j-ah3HwPpk8i_hwcoIwPBx/view?usp=drivesdk
Click to expand...
Click to collapse
I wonder if some kind soul can offer some wisdom, I unlocked my bootloader and flashed twrp. All fine so far.
I then upgraded to Pie.
I then flashed Magisk.
I was getting some strange Magisk behaviour so uninstalled it but for some reason it did'nt restore stock boot and Play Store was misbehaving.
I then flashed this boot image ^^ and yes, very stupidly, I now have no wifi (my MAC address is screwed).
I can boot to OS but I have no File Manager, nor root and I don't really know what to try from here.
I cant get to recovery (twrp or stock), it just get stuck on the Powered by Android logo.
I have debugging enabled but adb just reports my device as offline.
I cant get in to fastboot mode either.
Really appreciate some help from a kind soul
Ta
Hello i unlocked bootloader and after working so hard i finally booted twrp img to my nokia 8 and from there i cant access to twrp it always opens stock recovery.pls help me.....
I tried 2 to 3 times but i cant access twrp the process was successful but cant access it
I would say if it does not boot to it, its not there. Just flash twrp again. Use the latest from their website to do it.
Am I the only one on XT1900-7 stuck on the August update? I mean considering it's NOVEMBER now... it's pretty infuriating. My phone is locked (I suppose... if it ever was) btw.
TeamRainless said:
Am I the only one on XT1900-7 stuck on the August update? I mean considering it's NOVEMBER now... it's pretty infuriating. My phone is locked (I suppose... if it ever was) btw.
Click to expand...
Click to collapse
Same here waiting for it as I hope it fixes the Android Auto connectivity issue .... wonder why it takes so long
Italy, XT1900-7 RETEU stuck on 8.0 August patch here, too.
I hope they're working hard on Pie!
Just got the October update Today. Apparently it was released Oct 4th... we just didn't GET it.
Same here
TeamRainless said:
Just got the October update Today. Apparently it was released Oct 4th... we just didn't GET it.
Click to expand...
Click to collapse
Same here ... just started the installation, but I doubt it will be an 8.1 update based on numbers it's "just" a security update ... will see what it fixes and what will be broken I would love to have Android Auto working without errors
the same **** here
Can I install thiw wia TWPR because i am rooted and I can not update?
vidra said:
Can I install thiw wia TWPR because i am rooted and I can not update?
Click to expand...
Click to collapse
No, only with stock recovery and all stock partitions.
Comby_sk said:
No, only with stock recovery and all stock partitions.
Click to expand...
Click to collapse
So if I restore /boot I should be able to do it?
vidra said:
So if I restore /boot I should be able to do it?
Click to expand...
Click to collapse
And /system too. I do flash fastboot rom without erase userdata and than flash OTA from adb sideload. Check my guide in moto x4 thread.
Comby_sk said:
And /system too. I do flash fastboot rom without erase userdata and than flash OTA from adb sideload. Check my guide in moto x4 thread.
Click to expand...
Click to collapse
I cannot seem to find it, can you please link it?
vidra said:
I cannot seem to find it, can you please link it?
Click to expand...
Click to collapse
1. fastboot flash 8.0 OPWS27.57-40-22 (remove command "fastboot erase userdata" from script) - use this guide - after flash do not reboot to system
2. reboot to stock recovery (how to enter recovery) - install OTA from adb sideload - october 2018 OTA Blur_Version.27.301.32.payton.retail.en.US (save as zip)
3. reboot to system
if you want root gain
4. reboot to bootloader and use fastboot boot twrp.img
5. in twrp flash magisk and reboot to system
Comby_sk said:
1. fastboot flash 8.0 OPWS27.57-40-22 (remove command "fastboot erase userdata" from script) - use this guide - after flash do not reboot to system
2. reboot to stock recovery (how to enter recovery) - install OTA from adb sideload - october 2018 OTA Blur_Version.27.301.32.payton.retail.en.US (save as zip)
3. reboot to system
if you want root gain
4. reboot to bootloader and use fastboot boot twrp.img
5. in twrp flash magisk and reboot to system
Click to expand...
Click to collapse
I don't have the permission to download the OTA.
Comby_sk said:
1. fastboot flash 8.0 OPWS27.57-40-22 (remove command "fastboot erase userdata" from script) - use this guide - after flash do not reboot to system
2. reboot to stock recovery (how to enter recovery) - install OTA from adb sideload - october 2018 OTA Blur_Version.27.301.32.payton.retail.en.US (save as zip)
3. reboot to system
if you want root gain
4. reboot to bootloader and use fastboot boot twrp.img
5. in twrp flash magisk and reboot to system
Click to expand...
Click to collapse
I keep getting E: failed to mount / if i use sideload and failed yo unmount / if I try to install from sdcard in official recovery.
How do I solve that?
Reboot to bootloader and check software status is official.
Comby_sk said:
Reboot to bootloader and check software status is official.
Click to expand...
Click to collapse
I have falsed everything back but it says modified. Did I miss something?
If software status is modified, you cannot install OTA from SD card or from adb sidelod. You will try fastboot flash with "fastboot erase userdata", but you will lost all pictures, settings etc. I dont know if this helps.
Comby_sk said:
If software status is modified, you cannot install OTA from SD card or from adb sidelod. You will try fastboot flash with "fastboot erase userdata", but you will lost all pictures, settings etc. I dont know if this helps.
Click to expand...
Click to collapse
Yes, but shouldn't the flag get reset back to official when I restored factory firmware.
vidra said:
Yes, but shouldn't the flag get reset back to official when I restored factory firmware.
Click to expand...
Click to collapse
It does not.. it will remain modified.. even if you root.. the flag is triggered that helps the folks at Moto recognise the Device is tampered or something.. and I dont think there is a way to get it to official
Abhishek Survase said:
It does not.. it will remain modified.. even if you root.. the flag is triggered that helps the folks at Moto recognise the Device is tampered or something.. and I dont think there is a way to get it to official
Click to expand...
Click to collapse
So how con I install the OTA?
I really messed up when trying to root my phone.
I think i accidently flashed an incorrect boot.img to my phone.
Now I can't get it to boot anymore.
After this I now can't even let my XZ3 boot into twrp recovery also.
Everytime I do a fastboot boot twrp.img i get this:
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
Click to expand...
Click to collapse
So i'm stuck and don't know how to boot it.
any ideas?
r3v0 said:
I really messed up when trying to root my phone.
I think i accidently flashed an incorrect boot.img to my phone.
Now I can't get it to boot anymore.
After this I now can't even let my XZ3 boot into twrp recovery also.
Everytime I do a fastboot boot twrp.img i get this:
So i'm stuck and don't know how to boot it.
any ideas?
Click to expand...
Click to collapse
Did you apply the vbmeta parameters?
Did you tried magisk 19.x? (19 may generate bootloops, I recommend my bundled 18.1)
You can always get the stock boot.img from the boot.sin in the stock firmware (April, the may twrp is not published).
Just unsin.exe the file (unsin.exe from XDA).
MartinX3 said:
Did you apply the vbmeta parameters?
Did you tried magisk 19.x? (19 may generate bootloops, I recommend my bundled 18.1)
You can always get the stock boot.img from the boot.sin in the stock firmware (April, the may twrp is not published).
Just unsin.exe the file (unsin.exe from XDA).
Click to expand...
Click to collapse
Where can I find the latest stock firmware?
I've been searching for it for hours now.
The unsin.exe I found already
r3v0 said:
Where can I find the latest stock firmware?
I've been searching for it for hours now.
The unsin.exe I found already
Click to expand...
Click to collapse
The latest (without twrp support, because I shared the first build on telegram for testing) is downloadable via Emma.
You could also use xperifirm and newflasher from XDA
In xperifirm you can choose the region, hopefully one region has still the April firmware.
PS: I see notifications for new posts or answers easily in my big threads, but it gets difficulty for the different device sections on XDA (in the app).
MartinX3 said:
The latest (without twrp support, because I shared the first build on telegram for testing) is downloadable via Emma.
You could also use xperifirm and newflasher from XDA
In xperifirm you can choose the region, hopefully one region has still the April firmware.
Click to expand...
Click to collapse
xperifirm I can use. But Emma won't recognize the phone obviously as it doesn't boot.
You mentioned the april release. Is that necessary?
r3v0 said:
xperifirm I can use. But Emma won't recognize the phone obviously as it doesn't boot.
You mentioned the april release. Is that necessary?
Click to expand...
Click to collapse
Just if you want to install twrp on your phone.
The April twrp may "fastboot boot twrp.img" with broken decryption but an installation would only lead into a not working twrp.
MartinX3 said:
Just if you want to install twrp on your phone.
The April twrp may "fastboot boot twrp.img" with broken decryption but an installation would only lead into a not working twrp.
Click to expand...
Click to collapse
At this moment all I want is to be able to boot it again.
But everytime I try to fastboot a boot.img to the phone I get:
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
r3v0 said:
At this moment all I want is to be able to boot it again.
But everytime I try to fastboot a boot.img to the phone I get:
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
Click to expand...
Click to collapse
Do you use the newest fastboot version?
And the xz3 twrp?
Execute
fastboot -v
Please
MartinX3 said:
Do you use the newest fastboot version?
And the xz3 twrp?
Execute
fastboot -v
Please
Click to expand...
Click to collapse
I use this version:
fastboot version 28.0.3-5475833
And I have the latest xz3 twrp
r3v0 said:
I use this version:
fastboot version 28.0.3-5475833
And I have the latest xz3 twrp
Click to expand...
Click to collapse
Oh. Maybe 28.0.2 or 28.0.1 are working better?
Did you boot the stock firmware without any modification once first?
Edit:
Interesting
28.0.3 must be so new that even google didn't publish a changelog.
MartinX3 said:
Oh. Maybe 28.0.2 or 28.0.1 are working better?
Did you boot the stock firmware without any modification once first?
Click to expand...
Click to collapse
When I got the phone I booted it.
After that I managed to unlock the bootloader.
Then I tried to root it.
And that's when I think I fastbooted the wrong boot.img.
r3v0 said:
When I got the phone I booted it.
After that I managed to unlock the bootloader.
Then I tried to root it.
And that's when I think I fastbooted the wrong boot.img.
Click to expand...
Click to collapse
Maybe yes.
I never saw this message. Hmmm.
At least one xz3 user I know from is happy with the twrp.
Weird, very weird.
I whish I could reproduce it.
MartinX3 said:
Maybe yes.
I never saw this message. Hmmm.
At least one xz3 user I know from is happy with the twrp.
Weird, very weird.
I whish I could reproduce it.
Click to expand...
Click to collapse
TWRP worked until I messed up the boot.
When I now try to fastboot flash boot boot.img I get this:
FAILED (remote: 'Error flashing partition : Volume Full')
I managed to get it to boot to twrp. I guess at some time I set-active it to b. Setting it back to a solved the not booting twrp.
Now I used the vbmeta.img from twrp to set vbmeta.
Gonna try rooting it again now.
OS not booting yet.
r3v0 said:
I managed to get it to boot to twrp. I guess at some time I set-active it to b. Setting it back to a solved the not booting twrp.
Now I used the vbmeta.img from twrp to set vbmeta.
Gonna try rooting it again now.
OS not booting yet.
Click to expand...
Click to collapse
I recommand flashing the entire firmware via newflasher.
Remove the userdata.sin so you don't wipe your phone.
MartinX3 said:
I recommand flashing the entire firmware via newflasher.
Remove the userdata.sin so you don't wipe your phone.
Click to expand...
Click to collapse
So, I just found out You're the developer of what I downloaded.
Can I flash this one:
H9436_Customized CE1_1316-3759_52.0.A.3.84_R9B.tar.gz
through newflasher?
r3v0 said:
So, I just found out You're the developer of what I downloaded.
Can I flash this one:
H9436_Customized CE1_1316-3759_52.0.A.3.84_R9B.tar.gz
through newflasher?
Click to expand...
Click to collapse
Muahahahaha [emoji14]
You mean my old uploaded firmware?
That's just the last version before Sony changed the DRM
Better you use the 52.0.A.8.25 , it is the April stock firmware and compatible with the newest twrp so far.
I hope it is still available through xperifirm.
Ok, thanks so far. You pointed me in the right direction. Hopefully I get my Xz3 running again. ??
r3v0 said:
Ok, thanks so far. You pointed me in the right direction. Hopefully I get my Xz3 running again. [emoji1303]
Click to expand...
Click to collapse
I'm optimistic, that you'll achieved success.
MartinX3 said:
I'm optimistic, that you'll achieved success.
Click to expand...
Click to collapse
In the end.
Now i'm struggling with an error with newflasher.
No usb device with vid:0x0fce pid:0xb00b
Click to expand...
Click to collapse
Oh yeah, I'm on linux. So I'll have to do all my windows stuff through a VM
UPDATE: @Titokhan has confirmed this issue was fixed with the latest 9.5.4 update!
Ok so I did some things today to my phone and I ended up with the 9.5.4 version of the OOS ROM.
Earlier in the week I did NOT have the ability to "fastboot boot img" but now I do.
Can somebody please verify that the latest version of the ROM brings back the fastboot boot command?
if the latest version doesn't fix it I will post a quick guide about how I was able to get it back on mine. I'll turn this post into a guide at that point.
I'm on the unlocked international version.
texasaggie1 said:
Ok so I did some things today to my phone and I ended up with the 9.5.4 version of the OOS ROM.
Earlier in the week I did NOT have the ability to "fastboot boot img" but now I do.
Can somebody please verify that the latest version of the ROM brings back the fastboot boot command?
if the latest version doesn't fix it I will post a quick guide about how I was able to get it back on mine. I'll turn this post into a guide at that point.
I'm on the unlocked international version.
Click to expand...
Click to collapse
My device is still stuck on 9.5.3 but I know I can boot img when I switch slots
Logan0829 said:
My device is still stuck on 9.5.3 but I know I can boot img when I switch slots
Click to expand...
Click to collapse
Here's the 9.5.4 ota https://drive.google.com/file/d/1-0eczDjrIR7Op3Ut-2mVKicjuxPXH-Ar/view?usp=drivesdk
Also, I didn't have to do anything special to get fastboot boot img to work
I can confirm that the dev team fixed the fastboot boot part with the recent most 9.5.4.GM21AA/9.5.5.GM21BA OTA update.
Titokhan said:
I can confirm that the dev team fixed the fastboot boot part with the recent most 9.5.4.GM21AA/9.5.5.GM21BA OTA update.
Click to expand...
Click to collapse
That's great to hear now I don't have to flash back boot img Everytime I test a twrp build.
I'm on 9.5.5 and I still can't get "fastboot boot ..." to work using the latest fastboot binaries from google. Says something like unrecognized command every time I've tried. What steps did you change to get it working pre-9.5.5?
I tried re-rooting after updating and now it says Your device is corrupt. It cant be trusted and may not work properly.
It freezes on the Google if I continue. Not sure what happened.
Any remedy for this?
features99 said:
I tried re-rooting after updating and now it says Your device is corrupt. It cant be trusted and may not work properly.
It freezes on the Google if I continue. Not sure what happened.
Any remedy for this?
Click to expand...
Click to collapse
Need more specific details, like specific method of rooting, version of Magisk, updating to what?, etc...
Unfortunately you may have to flash the factory image and start all over again if no one else can help you with it. At least you have the option. Sucks when that happens.
I mean... the first message just sounds like the bootloader unlocked message which would show up even if you could fully boot in.
I wouldn't factory reset over just this though. Flash the factory image without the -w parameter in flash-all.bat
jljtgr said:
I mean... the first message just sounds like the bootloader unlocked message which would show up even if you could fully boot in.
I wouldn't factory reset over just this though. Flash the factory image without the -w parameter in flash-all.bat
Click to expand...
Click to collapse
I agree. Flashing the factory image without the -w would likely allow him to boot up again. But it would be helpful for that person to tell us exactly what they did so we can help them avoid it in the future, e.g. maybe they flashed the stable version of Magisk instead of Beta or Canary, or maybe they tried a direct install instead of patching the boot image, etc...
Ok guys sorry for not giving more details.
So I rooted awhile back when I got the phone, havent updated in a long time so I thought it was time.
I updated to Android 11 with the latest security updates and tried to re-root.
I updated Magisk to the latest version and patched the matching boot image, but Im pretty sure I used the stable version.
I should of researched it more as Im reading the beta method is the way to go.
I opened the command prompt with the following commands:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
fastboot reboot
Seems like everything went ok...
Then afterwards got the corrupted message and Google hang.
I can still load to fastboot but recovery or rescue doesnt work.
So where can I go from here? I only rooted a few phones in the past so Im still learning and reading lots of posts.
Also I didnt modify my own boot image, but one I downloaded from a matching build.
I really appreciate the help
features99 said:
Ok guys sorry for not giving more details.
So I rooted awhile back when I got the phone, havent updated in a long time so I thought it was time.
I updated to Android 11 with the latest security updates and tried to re-root.
I updated Magisk to the latest version and patched the matching boot image, but Im pretty sure I used the stable version.
I should of researched it more as Im reading the beta method is the way to go.
I opened the command prompt with the following commands:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
fastboot reboot
Seems like everything went ok...
Then afterwards got the corrupted message and Google hang.
I can still load to fastboot but recovery or rescue doesnt work.
So where can I go from here? I only rooted a few phones in the past so Im still learning and reading lots of posts.
I really appreciate the help
Click to expand...
Click to collapse
I would try fastboot flashing the stock boot image first.
If Magisk says you're on a version before 21.0, the patched image won't work for Android 11. Stable is currently 20.4 released in March.
Lughnasadh said:
I would try fastboot flashing the stock boot image first.
Click to expand...
Click to collapse
tried that..it didnt work
features99 said:
tried that..it didnt work
Click to expand...
Click to collapse
Then I would flash the December factory image using fastboot but with the -w removed from the flash-all.bat file so it won't erase your data.
Lughnasadh said:
Then I would flash the December factory image using fastboot but with the -w removed from the flash-all.bat file so it won't erase your data.
Click to expand...
Click to collapse
Yes that worked, didn't know about edited the .bat to remove the the -w and saving all data. Back in business for now...
Thank you all for expertise, much appreciated!
features99 said:
Yes that worked, didn't know about edited the .bat to remove the the -w and saving all data. Back in business for now...
Thank you all for expertise, much appreciated!
Click to expand...
Click to collapse
No problem. Glad you got it going. As I see you've already found out, Magisk Beta 21.1 is a good way to go. Canary as well but then you may run into problems in the future when Canary gets updated since those are "cutting edge" builds.