I have always used the "restore images" method to keep my Magisk after applying OTA updates (Magisk Manager -> Uninstall -> Restore images -> [update without rebooting] -> Magisk Manager -> Install to inactive slot), but after today's update, it didn't quite work. Now my phone won't boot, saying "Can't load Android system. Your data may be corrupt".
Now, I didn't realize it at first, but this was a more major update - an upgrade from Android 9 to Android 10, which is likely the problem. The error screen shows: "motorola/ocean_retail/ocean10/QPO30.52-29". The most I can do is perform a big factory reset (which might not even work) or reboot to stock recovery (do not have TWRP, as I installed Magisk before it was available for G7 Power and missed its release since).
Now, my go-to idea for a solution is to download the most recent ROM I can find - which unfortunately can't be the brand new Android 10 one, as it seems it's nowhere to be found yet - and flash the boot.img from it (and worry about reinstalling Magisk later, shouldn't be that much of a problem). However, I'm not sure if it's going to work, as perhaps an update this big has changed more than usual. Obviously I'd like to restore my phone to a state as close as possible to what it was yesterday, so before reflashing the entire ROM, I'd like to seek advice regarding any other solutions if possible.
I've also considered trying to use the Rescue and Assistant Tool to possibly download a good ROM. Does anyone have experience with this app?
I'd very much appreciate any and all help.
eworm92 said:
I have always used the "restore images" method to keep my Magisk after applying OTA updates (Magisk Manager -> Uninstall -> Restore images -> [update without rebooting] -> Magisk Manager -> Install to inactive slot), but after today's update, it didn't quite work. Now my phone won't boot, saying "Can't load Android system. Your data may be corrupt".
Now, I didn't realize it at first, but this was a more major update - an upgrade from Android 9 to Android 10, which is likely the problem. The error screen shows: "motorola/ocean_retail/ocean10/QPO30.52-29". The most I can do is perform a big factory reset (which might not even work) or reboot to stock recovery (do not have TWRP, as I installed Magisk before it was available for G7 Power and missed its release since).
Now, my go-to idea for a solution is to download the most recent ROM I can find - which unfortunately can't be the brand new Android 10 one, as it seems it's nowhere to be found yet - and flash the boot.img from it (and worry about reinstalling Magisk later, shouldn't be that much of a problem). However, I'm not sure if it's going to work, as perhaps an update this big has changed more than usual. Obviously I'd like to restore my phone to a state as close as possible to what it was yesterday, so before reflashing the entire ROM, I'd like to seek advice regarding any other solutions if possible.
I've also considered trying to use the Rescue and Assistant Tool to possibly download a good ROM. Does anyone have experience with this app?
I'd very much appreciate any and all help.
Click to expand...
Click to collapse
Hi. What software channel does your device have? There's already android 10 firmware available
LuisLFSS said:
Hi. What software channel does your device have? There's already android 10 firmware available
Click to expand...
Click to collapse
I've been running a RETAIL ROM and despite the software update channel showing in the settings as RETEU, the other OTA updates installed fine.
In this case what I've done is:
a) tried to "restore images" and install OTA normally. This didn't work - had to reflash the Android 9 ROM
b) tried to download and install the Android 10 RETAIL ROM from lolinet. This also didn't work. Reflashed again.
c) tried to flash the Android 10 RETEU ROM from lolinet. Same result again.
d) tried to flash the Android 9 RETEU ROM from lolinet. This actually worked no problem and I am now on this ROM, matching my software update channel.
e) tried to "restore images" and install OTA normally again, now that the software update channel is the same as the ROM I'm running. Still didn't work.
f) tried to uninstall Magisk and then install OTA normally. Even this didn't work.
I really have no idea what is wrong. For now, I've decided to simply not update but if someone has an idea on what might help, I'd be glad to hear it.
On a side note, when I got to that screen, not even re-flashing the OTA, correctly this time, (beware, new updates have 10 sparse system chunks instead of 9...) let me get past it, so the solution was to erase userdata. (no re-flashing involved) As for Magisk, I just re-patch/flash boot.img at every update, it's not like it's updated that frequently
eworm92 said:
I've been running a RETAIL ROM and despite the software update channel showing in the settings as RETEU, the other OTA updates installed fine.
In this case what I've done is:
a) tried to "restore images" and install OTA normally. This didn't work - had to reflash the Android 9 ROM
b) tried to download and install the Android 10 RETAIL ROM from lolinet. This also didn't work. Reflashed again.
c) tried to flash the Android 10 RETEU ROM from lolinet. Same result again.
d) tried to flash the Android 9 RETEU ROM from lolinet. This actually worked no problem and I am now on this ROM, matching my software update channel.
e) tried to "restore images" and install OTA normally again, now that the software update channel is the same as the ROM I'm running. Still didn't work.
f) tried to uninstall Magisk and then install OTA normally. Even this didn't work.
I really have no idea what is wrong. For now, I've decided to simply not update but if someone has an idea on what might help, I'd be glad to hear it.
Click to expand...
Click to collapse
This is kinda weird because reflash stock ROM android 10 should work for you... What errors did you get when trying to flash android 10?
eworm92 said:
I have always used the "restore images" method to keep my Magisk after applying OTA updates (Magisk Manager -> Uninstall -> Restore images -> [update without rebooting] -> Magisk Manager -> Install to inactive slot), but after today's update, it didn't quite work. Now my phone won't boot, saying "Can't load Android system. Your data may be corrupt".
Now, I didn't realize it at first, but this was a more major update - an upgrade from Android 9 to Android 10, which is likely the problem. The error screen shows: "motorola/ocean_retail/ocean10/QPO30.52-29". The most I can do is perform a big factory reset (which might not even work) or reboot to stock recovery (do not have TWRP, as I installed Magisk before it was available for G7 Power and missed its release since).
Now, my go-to idea for a solution is to download the most recent ROM I can find - which unfortunately can't be the brand new Android 10 one, as it seems it's nowhere to be found yet - and flash the boot.img from it (and worry about reinstalling Magisk later, shouldn't be that much of a problem). However, I'm not sure if it's going to work, as perhaps an update this big has changed more than usual. Obviously I'd like to restore my phone to a state as close as possible to what it was yesterday, so before reflashing the entire ROM, I'd like to seek advice regarding any other solutions if possible.
I've also considered trying to use the Rescue and Assistant Tool to possibly download a good ROM. Does anyone have experience with this app?
I'd very much appreciate any and all help.
Click to expand...
Click to collapse
Next time do the following:
1. Restart to bootloader
2. connect to PC, open ADB terminal and type
"fastboot getvar all" to get active slot
3. change active slot by
"fastboot -aa" => change to slot _a
"fastboot -ab" => change to slot _b
You are running a A/B device. Is there is any error after an update then change the slot to the last working one.
eworm92 said:
I've been running a RETAIL ROM and despite the software update channel showing in the settings as RETEU, the other OTA updates installed fine.
In this case what I've done is:
a) tried to "restore images" and install OTA normally. This didn't work - had to reflash the Android 9 ROM
b) tried to download and install the Android 10 RETAIL ROM from lolinet. This also didn't work. Reflashed again.
c) tried to flash the Android 10 RETEU ROM from lolinet. Same result again.
d) tried to flash the Android 9 RETEU ROM from lolinet. This actually worked no problem and I am now on this ROM, matching my software update channel.
e) tried to "restore images" and install OTA normally again, now that the software update channel is the same as the ROM I'm running. Still didn't work.
f) tried to uninstall Magisk and then install OTA normally. Even this didn't work.
I really have no idea what is wrong. For now, I've decided to simply not update but if someone has an idea on what might help, I'd be glad to hear it.
Click to expand...
Click to collapse
Check if you're running 10 sparse system image flash commands instead of 9 (The only difference between flashing Android 9/10)
I've tried everything proposed above: flashed to both slots, made sure to flash all 10 system sparsechunks.
I guess the solution is to erase userdata, which I've avoided doing thus far. What exactly am I gonna lose if I do?
eworm92 said:
I've tried everything proposed above: flashed to both slots, made sure to flash all 10 system sparsechunks.
I guess the solution is to erase userdata, which I've avoided doing thus far. What exactly am I gonna lose if I do?
Click to expand...
Click to collapse
Erasing userdata will make it like you had just bought the phone. (factory reset) I also had to do that, but I assumed it was because I'd forgotten to flash the 10th system sparsechunk, which caused a bootloop asking me to do a factory reset no matter what I did. (Unless blankflash/flashing Android 9 image was the solution, I just flashed the missing sparsechunk and erased userdata)
I'm just confused because it is an update. I'm supposed to be able to keep my data.
eworm92 said:
I'm just confused because it is an update. I'm supposed to be able to keep my data.
Click to expand...
Click to collapse
You're right, you should keep your data. But I had the same issue on my Moto G6 plus. It was only a security patch update without an Android upgrade.
After it was successfully installed I wasn't able to boot and had to erase my data.
Before factory reset, try switching partition for backup
I basically ran into the same problem today, the update banner popped up at an unfortunate moment and I clicked it in accident. I was also running a RETAIL rom.
The G7 Power didn't boot anymore, instead complaining that the image was corrupted, and did not go into recovery.
adb saw nothing, fastboot saw the device after the usual reboot into bootloader.
A mate of mine suggested switching to partition b with `fastboot set_active b` (or a if yours is set to b already) and after rebooting it failed to start ocean 9 instead of 10. Success ?! On the second reboot it came back up normal, which allowed me to do a normal backup of things before getting into the hassle of upgrading (which I have put off until I have more time).
ElFalko said:
I basically ran into the same problem today, the update banner popped up at an unfortunate moment and I clicked it in accident. I was also running a RETAIL rom.
The G7 Power didn't boot anymore, instead complaining that the image was corrupted, and did not go into recovery.
adb saw nothing, fastboot saw the device after the usual reboot into bootloader.
A mate of mine suggested switching to partition b with `fastboot set_active b` (or a if yours is set to b already) and after rebooting it failed to start ocean 9 instead of 10. Success ?! On the second reboot it came back up normal, which allowed me to do a normal backup of things before getting into the hassle of upgrading (which I have put off until I have more time).
Click to expand...
Click to collapse
That's the advantage of the A/B partition scheme. I already advised him to do so in post #6...
BTW: "adb devices" will recognizes your device only when fully booted up into system or TWRP.
WoKoschekk said:
That's the advantage of the A/B partition scheme. I already advised him to do so in post #6...
BTW: "adb devices" will recognizes your device only when fully booted up into system or TWRP.
Click to expand...
Click to collapse
Seems I was selectively blind I read #5 and #7 and somehow skipped that one exactly.
It's been a while since I did anything with adb, so I wasn't sure about when it detects things. I tried getting into TWRP, but at least on the A partition TWRP had been wiped by the update.
Anyway thanks for the solid advice!
Related
Google Play Store Pixel, stock feb update (nof26v), unrooted, unlocked bootloader. There's a longer back story to this issue I've encountered, but to cut to the chase:
I can successfully flash TWRP 3.0.2 RC1 and 2.79 SR3. I can boot into system and enjoy benefits of root. However, I've noticed that whenever I try to reboot SYSTEM, it only boots into recovery. Even when I boot into bootloader and flash stock boot.img, it'll just reboot into stock recovery, but never into system. My way out of this quasi soft-brick state is to flash stock boot.img and sideload ota and I'm good to go with all my settings/data intact, I'll just be unrooted (as expected). I can verify it survives reboot in this state.
Has anyone else encountered this before? Is there something in the latest SU that won't let it reboot properly? Is there a way I can force it to reboot a certain slot to somehow avoid this issue?
The way Android handles memory now, I don't ever feel the need to reboot. But one of the things that's essential for me is to edit build.prop to enable wifi tether and miracast. Thing is, it requires a reboot for those changes to apply, but as soon as I reboot...
I've had this all working before on the dec update and SuperSU-v2.79-201612051815.zip but then something really strange happened (long backstory referenced above) and it required me to have to re-root, only now it won't survive reboot.
Any insight is greatly appreciated!
I have never encountered this issue as a result of flashing Super SU. I have come across this when I updated to the latest image by just flashing a few components.. IE: i didnt flash the whole factory image.
Flashing the latest factory image to both slots and starting over fixed the issue for me.
Flash the image (flash_all.bat) then fastboot boot twrp and switch slots, flash factory image again.
Just my two cents.
k.s.deviate said:
Flashing the latest factory image to both slots and starting over fixed the issue for me.
Flash the image (flash_all.bat) then fastboot boot twrp and switch slots, flash factory image again.
Just my two cents.
Click to expand...
Click to collapse
Thanks for your input! Should I remove -w while flashing, or when you said starting over do you mean full wipe?
Was hoping to avoid going that route... Is there any way to salvage without wipe?
Let me also share the strange event I encountered which led me to this point:
As stated, I had December update with stable 2.79 and TWRP 3.0.2. I skipped Jan update and was planning to do the same for the Feb update, but for whatever reason, I went to check updates (knowing full well it wouldn't take since I'm not on stock recovery). It gave me the standard "downloading, installing..Oops, there's a problem" prompt and I went on my merry way.
A week or so later, I decided to manually reboot and upon boot, I noticed it said "Android is starting/configuring" something along those lines. Then I tried double tap to lock (Nova gesture) and it says phone wasn't rooted. I check and sure enough, no SU icon. Checked Android version and now it says I'm on Feb update.
Attempt to install latest from chainfire on play store and no dice. Decide to flash it instead. Downloaded 2.79 SR3. Booted temporary TWRP and flashed the install and SU and then I found that phone won't boot to anything but recovery. Now anytime, I modify the boot image in any way, I'm bricked on subsequent reboots until I flash stock boot image and sideload OTA.
How do you think the Feb update installed when it shouldn't have? Did it install to one slot while my other slot was TWRP+root?
I would guess that it may have installed onto the inactive slot, but it doesn't sound like it should have if you had TWRP and Su installed. However we are all still learning new things about the pixel every day.
I would recommend clean flashing the factory image to both slots and starting over. Sounds like something became corrupt.
What version of ADB and Fastboot are you running? This reboot to bootloader happened to me when I unknowing using an older version.
Try wiping the device completely push your factory image via ADB and fastboot and installed of TWRP RC1 use alpha 2 never had a issue with alpha 2 after flashing TWRP boot into stock then go back into TWRP then flash SuperSU
jamespark said:
How do you think the Feb update installed when it shouldn't have?
Click to expand...
Click to collapse
People have reported automatic OTA updates on rooted Pixel phones. You can shut off automatic OTA updates by following the following link. People report still getting a notification for updates after the setting change, but updates no longer happen automatically. The site below also lists a way to entirely shut off OTA notifications, yet that change causes my phone to stay awake constantly and never go into deep sleep, so I only recommend the link. There's a thread or two about FlashFire, which I may eventually get around to trying.
https://www.androidexplained.com/pixel-disable-ota-updates/
Are you okay with losing data? I can post the links I used to download SuperSU and a little guide to flash to stock and reroot. Maybe you'll be able to figure what you're doing wrong or just doing what I do step by step might fix it.
mngdew said:
What version of ADB and Fastboot are you running? This reboot to bootloader happened to me when I unknowing using an older version.
Click to expand...
Click to collapse
Definitely using an older version of adb and fastboot. I'll update and retry with the latest, thanks for the suggestion!
alluringreality said:
People have reported automatic OTA updates on rooted Pixel phones. You can shut off automatic OTA updates by following the following link. People report still getting a notification for updates after the setting change, but updates no longer happen automatically. The site below also lists a way to entirely shut off OTA notifications, yet that change causes my phone to stay awake constantly and never go into deep sleep, so I only recommend the link. There's a thread or two about FlashFire, which I may eventually get around to trying.
https://www.androidexplained.com/pixel-disable-ota-updates/
Click to expand...
Click to collapse
Thanks for the heads up! I had this setting enabled and I have since disabled it.
I really appreciate the community and all your help!
SOLVED
I'm pleased to report that I now have root that survives reboot!
- From stock: flashed TWRP and SU. verified root, edited build.prop and reboot system..... boots into recovery (the usual problem)
- switched active slots and flashed SU, reboot
- SU icon in app drawer but when launched: "supersu binaries not installed"
- reboot into recovery and flashed su, reboot
- su is installed, but build.prop changes didn't stick. edited build.prop, reboot system
- boots into recovery.
- flashed su, did NOT reboot, backed out, switched slots, flash SU to the other slot, reboot
- huzzah!
is it verified that android will alternate active slots upon each subsequent reboot (i.e. A/B/A/B/...)?
it would seem I was making changes and rebooting to the other slot which was jacked up, so I had to finally apply the same changes to both slots and now everything is working!
I honestly don't know what I just did, and I guess sometimes it's better to be lucky than smart lol but, boy, this two-system partition is a piece of work...
Thanks again to everyone for all your help!!
Hi,
So I followed this tutorial https://oneplus.gadgethacks.com/how...thout-losing-root-no-computer-needed-0192638/ (but I used more up to date downloads links than what was on the article) to update my phone to the latest oxygenos on my OnePlus 6.
The install went well, I could reboot on my phone without problems. The thing is when I ran magisk manager it said that magisk wasn't installed. So I rebooted to twrp and flashed again magisk then rebooted. Now when the phone rebooted and asked me for my pin number it automatically went to "Shutting down phone" and rebooted to twrp. So I flashed the magisk uninstaller but it didn't rebooted well. Then I thought I had to switch the active slot, so in twrp I switched to slot A. Then it rebooted on fastboot. I understood I did something really bad so I ran "fastboot --set_active=b" on my computer.
Now my phone cannot actually boot and everytime I get in twrp except that now it doesn't ask me to unlock the phone to decrypt it and just asks me if I want to get into twrp in read only mode. When I navigate to /sdcard, it is full of weird folder name which is because, if I understand well, twrp has failed to decrypt it.
Is my phone bricked? Can I recover data? Can I repair my installation?
EDIT: if you need more informations that I forgot to give don't hesitate to ask.
EDIT2: I tried to reboot to fastboot mode and issue on my computer "fastboot boot twrp-3.2.3-1-enchilada.img" to see if the official twrp could decrypt the data (I'm currently using bluespark's twrp). I get the following error: "FAILED (remote: unknown command)". I understand now I'm pretty ****ed. Right now I'd only like to recover my data (mostly hundreds of pictures) and then flash a stock rom (except if it's actually possible to repair the system and boot normally). How can I decrypt /sdcard if twrp can't do it?
Thanks in advance for your help, I'm pretty lost right now and it's quite an urgent situation.
I got a new error when issuing "fastboot boot boot.img" after I rebooted to System from twrp:
```
Downloading 'boot.img'
OKAY [ 0.692s]
booting
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Finished. Total time: 0.719s
```
Ok so now by restarting a couple of times to fastboot I successfully booted to official twrp using "fastboot boot.img" and it successfully decrypted my storage!!!
Now I think things are recoverable, how do I fix this bad boy? Reflashing last official oxygenos image could work?
noom4_5 said:
Ok so now by restarting a couple of times to fastboot I successfully booted to official twrp using "fastboot boot.img" and it successfully decrypted my storage!!!
Now I think things are recoverable, how do I fix this bad boy? Reflashing last official oxygenos image could work?
Click to expand...
Click to collapse
Once in your booted TWRP from 'fastboot boot twrp.img' ... Flash OOS (9.0.5 from xda forums), flash blu_spark-TWRP, reboot TWRP... Now you can root your phone (flash Magisk), flash a kernel. All should be good.
I would suggest in future, use these forums for download links, tutorials, and check this Q&A forum (literally 3-5 posts on first half of page 1 with similar problems. Just follow instructions to update if you don't know how (they are always on first page of the thread where you get your downloads from).
Thank you for your answer, everything's back to normal
I'll make sure to follow the official tutorials next time.
only4dank said:
Once in your booted TWRP from 'fastboot boot twrp.img' ... Flash OOS (9.0.5 from xda forums), flash blu_spark-TWRP, reboot TWRP... Now you can root your phone (flash Magisk), flash a kernel. All should be good.
I would suggest in future, use these forums for download links, tutorials, and check this Q&A forum (literally 3-5 posts on first half of page 1 with similar problems. Just follow instructions to update if you don't know how (they are always on first page of the thread where you get your downloads from).
Click to expand...
Click to collapse
Good advice. I'd also like to add so everyone is aware, it's a good idea to disable all magisk modules before an update. Also disable your lockscreen pin, fingerprint... Basically any security. You can always re-enable these once updated. It just makes for less complications when updating. I'd also recommend downloading magisk modules outside of the app and keep them in a folder called magisk modules. That way, if for some reason magisk didn't retain the ones you downloaded after disabling and installing an oos update, you don't have to rely on your memory to look up\install them.
thejase said:
Good advice. I'd also like to add so everyone is aware, it's a good idea to disable all magisk modules before an update. Also disable your lockscreen pin, fingerprint... Basically any security. You can always re-enable these once updated. It just makes for less complications when updating. I'd also recommend downloading magisk modules outside of the app and keep them in a folder called magisk modules. That way, if for some reason magisk didn't retain the ones you downloaded after disabling and installing an oos update, you don't have to rely on your memory to look up\install them.
Click to expand...
Click to collapse
I never disable/uninstall Magisk modules. Nor do I disable lockscreen pin, fingerprint.
Theres no point at all. If flash things logically (correctly) you won't reboot your system without non-stock recovery, or no root.
only4dank said:
I never disable/uninstall Magisk modules. Nor do I disable lockscreen pin, fingerprint.
Theres no point at all. If flash things logically (correctly) you won't reboot your system without non-stock recovery, or no root.
Click to expand...
Click to collapse
There absolutely is a point. Many people have had encryption issues in twrp when updating. In addition, I myself have had a magisk issue where one of the modules wouldn't run properly when updating to pie and as a result, it didn't boot. Using a terminal magisk module uninstaller in twrp to disable the module fixed the issue. This is merely advice to eliminate all possible failures when updating. If it works for you without doing these things, mazel tov, but this is for those that have had issues and want to minimize the odds of that happening again.
thejase said:
There absolutely is a point. Many people have had encryption issues in twrp when updating. In addition, I myself have had a magisk issue where one of the modules wouldn't run properly when updating to pie and as a result, it didn't boot. Using a terminal magisk module uninstaller in twrp to disable the module fixed the issue. This is merely advice to eliminate all possible failures when updating. If it works for you without doing these things, mazel tov, but this is for those that have had issues and want to minimize the odds of that happening again.
Click to expand...
Click to collapse
Fair enough. But moving from Oreo to Pie is a little bit different then Pie OTA updates. I have 6-7 modules recently in Magisk - and never uninstalled Magisk or removed modules while updating Android Pie.
When I came from Oreo, I did a clean wiped system. To me, that makes sense - because it is a dramatic change in the system (whereas OTA updates for same android version are pretty minuscule).
only4dank said:
Fair enough. But moving from Oreo to Pie is a little bit different then Pie OTA updates. I have 6-7 modules recently in Magisk - and never uninstalled Magisk or removed modules while updating Android Pie.
When I came from Oreo, I did a clean wiped system. To me, that makes sense - because it is a dramatic change in the system (whereas OTA updates for same android version are pretty minuscule).
Click to expand...
Click to collapse
The only module I had to manually remove, because OOS refused to boot after an update, was "OOS Native Call Recording Enabler".
And before I knew that was causing it... I factory reset, then everything was fine until the next update xD
I even made a Backup/restore magisk data script, but seeing as it backed up/restored that module too it would still refuse to boot after an update.
ante0 said:
The only module I had to manually remove, because OOS refused to boot after an update, was "OOS Native Call Recording Enabler".
And before I knew that was causing it... I factory reset, then everything was fine until the next update xD
I even made a Backup/restore magisk data script, but seeing as it backed up/restored that module too it would still refuse to boot after an update.
Click to expand...
Click to collapse
Same. But if you install it with version 8.0 after the update, it works again. Just f.y.i..
noom4_5 said:
I got a new error when issuing "fastboot boot boot.img" after I rebooted to System from twrp:
```
Downloading 'boot.img'
OKAY [ 0.692s]
booting
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Finished. Total time: 0.719s
```
Click to expand...
Click to collapse
noom4_5 said:
Ok so now by restarting a couple of times to fastboot I successfully booted to official twrp using "fastboot boot.img" and it successfully decrypted my storage!!!
Now I think things are recoverable, how do I fix this bad boy? Reflashing last official oxygenos image could work?
Click to expand...
Click to collapse
Can you tell me which TWRP image you used to get past this issue? I have tried both 3.2.3-1 and 3.3.0-0 several times with zero luck this far. Thanks!
wwwryan said:
Can you tell me which TWRP image you used to get past this issue? I have tried both 3.2.3-1 and 3.3.0-0 several times with zero luck this far. Thanks!
Click to expand...
Click to collapse
Answered my own question but wanted to leave this here for others just in case it is helpful. Using twrp-3.2.3-x_blu_spark_v9.91_op6.img I was able to fastboot boot the img file and this version of TWRP offered to decrypt. From there first thing I did was adb pull my entire sdcard to my PC for save keeping.
My issue was a result of restoring from an earlier backup to recover some data. I had recently updated to 9.0.5 but accidentally deleted something I had no backup for so was restoring a previous TWRP back from 9.0.4. After the restore I couldn't boot the OS and all official version of TWRP would no longer offer to decrypt my data. Of course, I could not restore the backup I had just taken either since it was encrypted on the internal SD card. From now on I will just take TWRP backups to external storage via OTG USB and not even risk it.
Happened to me a few days ago
You can NOT recover your data. But you will be able to fix your phone.
Just do a Factory Reset from TWRP (Wipes Everything) and a wipe of system etc
Then just sideload or put the latest OOS back on the phone and install it.
Trust me, I have tried everything for trying to recover and decrypt the data... Somehow our phones did change the Encryption Keys from /data/unencrypted so there is no way to recover unless you can get the same key out of luck of using the encryption algorithm and salting process that Android uses.
https://imgur.com/y8ENw77
https://imgur.com/q7BPOCy
I've done this a few times. Actually... every time I update; save for the last two times. Just two notes that you already seem to have figured out:
1) Always remember turn off your active modules. (Just turn them off, you don't need to uninstall them.) Simply doing that seems to have fix OTA issues for me. I try to do it before I even download the update and definitely before I install it.
2) No matter how badly I foul up (except for the first time), I never wipe it when trying to fix it. Just side boot Blu Spark TWRP and flash the OS again. Boot it up once without root. Then go ahead to side boot Blu Spark TWRP again to root. I never install TWRP to the device at all. Even with Blu Spark, it seems to get iffy with me. If I want to flash something, I just let it wait until I'm home so I can side load Blu Spark.
Hello everyone,
As I mentioned in the title, since I upgraded to Android 10, can't boot to recovery.
Dowloaded latest version of the Adb kit, and while issuing
adb reboot recovery
the phone reboots but goes to normal boot.
Tried manually (power + vol down etc.) and when choosing Recovery - same thing happens.
Needless to say that my laptop is authorized debug device and phone is in debug mode etc. - I have done this many times before Android 10 update.
All I try to do is to sideload the latest OTA as I did many times before because my phone is rooted and the updates do not install automatically.
Pixel (First generation)
Rooted with Magisk
Bootloader unlocked
Stock recovery (using TWRP without installing it when flashing Magisk)
Hope somebody can advise. Obviously there is something new in Android 10 which has to be set (like the need for debugging authorization for example, which I already did).
Thank you
John
Im getting a similar problem. I get stuck on th Google logo screen. I cant hard-reset, recovery mode or boot, the only things that works is th barcode.
Android 10 changed something in the ramdisk that you can't install TWRP directly on the phone. You have to boot it via PC using "fastboot boot <insert twrp image name>.img"
You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck
junglism93 said:
You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck
Click to expand...
Click to collapse
Thank you for the advice, however as I mentioned in my original post I don't want to install TWRP permanently , and the problem is that I cannot go to the stock recovery mode which has no connection to TWRP. There is something with Android 10 which changed since 9 and I'm interested to find what. Everything worked fine before the upgrade.
Also, the option to flash factory image and restore (I also have Titanium in addition to Google backup) is a too much of a hassle. I use this phone for real, not only to play with it.
Anyway, again thank you for your input.
John
Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.
I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.
junglism93 said:
Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.
Click to expand...
Click to collapse
You are right. I did open Magisk and from the uninstall options choosed "Restore images" (no need to do complete uninstall, which is the other option). After that I was able to boot in recovery etc. I guess this is what you meant in your PS. At the end re-flashed Magisk and all is back to normal.
I will alert the Magisk team about the issue (if they are not already aware).
Case closed.
Thanks again.
John
Master Cylinder said:
I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.
Click to expand...
Click to collapse
Please read my OP. I was clear that I DON'T want to install TWRP permanently and this was never the problem.
The problem is solved (kind of). See the other posts.
Thank you.
John
I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things
aholeinthewor1d said:
I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things
Click to expand...
Click to collapse
It works just fine.
Mzprx said:
It works just fine.
Click to expand...
Click to collapse
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks
aholeinthewor1d said:
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks
Click to expand...
Click to collapse
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John
Mzprx said:
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John
Click to expand...
Click to collapse
Thanks. Yea from what I can tell no one has had luck actually installing it on the Pixel with Android 10 yet. I'm familiar with how to fix everything if something goes wrong. I would try but others have already tried and failed. It won't install for them.
firstly, dont use whatever ****ty platform-tools you are using, get them from here.
secondly, you dont install recovery on android 10 yet, it doenst work. you have to just boot to twrp using `fastboot boot twrp.img` once you are in bootloader mode.
So I've got a US unlocked device running firmware version KB2005_15_200918. I've rooted it with magisk.
Few days ago I got an update notification, to update to 11.0.1.2.KB05AA. So, thinking I could do it like a pixel, I unrooted, installed the update and re rooted installing to the inactive slot (per @topjohnwu's instructions). On reboot I got stuck on the qualcomm kernel crash screen, leaving my slot_A install hosed.
After some tinkering, I was able to get up and running on slot B. However, slot A is hosed up with the update. (system update says failed, reboot to try again, when i do, hoses back up. Probably because it's setting the active slot to A again).
I've tried re-flashing the KB05AA stock boot image someone dd' and shared on here with no luck. And I don't want to use the unbrick tool, and ending up having to backup/restore all my data.
What are my options at this point to fix slot A, and take the update again? I'm coming from a pixel 3, and know nothing about flashing the factory images on this device or the best way to recover from this. Any advice would be appreciated.
-Michael_ said:
So I've got a US unlocked device running firmware version KB2005_15_200918. I've rooted it with magisk.
Few days ago I got an update notification, to update to 11.0.1.2.KB05AA. So, thinking I could do it like a pixel, I unrooted, installed the update and re rooted installing to the inactive slot (per @topjohnwu's instructions). On reboot I got stuck on the qualcomm kernel crash screen, leaving my slot_A install hosed.
After some tinkering, I was able to get up and running on slot B. However, slot A is hosed up with the update. (system update says failed, reboot to try again, when i do, hoses back up. Probably because it's setting the active slot to A again).
I've tried re-flashing the KB05AA stock boot image someone dd' and shared on here with no luck. And I don't want to use the unbrick tool, and ending up having to backup/restore all my data.
What are my options at this point to fix slot A, and take the update again? I'm coming from a pixel 3, and know nothing about flashing the factory images on this device or the best way to recover from this. Any advice would be appreciated.
Click to expand...
Click to collapse
Use msm tool or reflash stock via fastboot. Either way you gotta wipe one way or another.
Or maybe..
Try fastboot erase boot_a
Then fastboot flash boot_a boot.img. With the kernel you had on slot_a. Hopefully you backed it up prior to this. If not, see my first recommendation.
Thanks, I'll give my kernel backup a shot.
Update: Reinstalled the ROM without TWRP and Magisk and it is working fine.
How should I approach the desire to root then?
Hi,
short story:
unlocked my Xiaoxin Pad Pro running Android 11 ZUI 12.6.X. Worked fine afterwards.
Installed TWRP 3.4.2. from here https://unofficialtwrp.com/twrp-3-4-2-root-lenovo-tb-j706f/?amp
and followed the guide.
"fastboot format userdata" didnt work though and I found no solution, so I skipped it.
Error was mke2fs failed, Cannot generate image for userdata.
Nandroid backup didnt work either:
"Cannot create /data/media/0/twrp' folder (required key not available).
Failed to make backup folder."
Also, there was no system partition when I tried to back it up, only "super".
Solved the backup not possible problem by formating data in TWRP and trying it again.
Installed Magisk with adb sideload and booted..... into a fastboot brick.
Couldnt be solved by factory reset in TWRP and couldnt install new Global ROM .zips from here:
https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Pro/TB-J706F/
It said the files were corrupted.
Changed to Slot B in TWRP and the system booted normally.
Then I wanted to flash a Global ROM with QFIL.
It worked, but once the system booted up it told me "The current system is not compatible with the hardware. The device will power off automatically. It can work normally after flashing back to the factory version system"
In another XDA thread it was said, it is a kind of blocking thing in ZUI 12.6 (and maybe earlier) to prevent installing a Global ROM (on a chinese device). Tried to install the chinese version from the website then,
didnt work either.
Tried the older versions, all tested Android 10 versions are working, no A11 version is working though.
So question 1 is: "How can I change to A11 with root on Global ROM?"
Installed the newest one (the A11 ones arent working) as well as TWRP and Magisk
and it "worked".
But now the display isnt reaction in many cases. Have to click something like 5-10 times or I swipe up,
the screen goes up but when I lift my finger it goes down again instead of e.g. unlocking the screen.
Update 2: I can install OTA updates even with unlocked bootloader and Android 11 isnt available in my region (yet?), so maybe that's the reason the A11 versions didnt work for me.
The ZUI design was way better thouhj
Thxx