For my fellow Stingray users (and possibly Everest users as well, if they're having similar issues), I was one of the group of people who couldn't get data on any 4.4 roms after going through the BigPart process. After a bunch of trial and error (and some excellent suggestions from fellow community members, I was able to get data working again and I'm happily enjoying KitKat on my three-year-old Xoom. If you've got a bit of patience and an hour or so, I believe I've got the solution to help you restore your data as well.
IMPORTANT: This entire process should be completely harmless to your Xoom, and the goal here is to help the group of Stingray users who lost all data functionality to repair that issue so that they can enjoy the full benefits of Android 4.4 (and potential future updates). That said, you do this at your own risk, and in doing so, you agree not to hold me accountable if you brick your Xoom, or if it dies, loses data (you’re going to lose everything but what’s on your SD Card, so think about that before you start the process), or any other unforeseen circumstances.
STAGE 1: Reverting to Stock Partitions
1.) DISCLAIMER: Any and all data on anything but your external SD Card will be completely wiped. If there are any back-ups you value, move them to your SD Card, your computer, or a cloud storage account. There’s no getting them back once you start this process.
2.) First off, you need to make sure you have everything you need downloaded and ready. You will need the following on your SD Card:
-TWRP 2.6.3.0 touch recovery from @runandhide05
-TWRP 2.6.3.0 BigPart touch recovery from @runandhide05
-a standard partition Stingray rom (I used CM 10.1 from @Steady Hawkin, 10/28 build, which you can find here)
-(optional) GApps package for standard partition rom (I used the 02.20.2013 Unified GApps found here, but you seriously don’t need them for anything.
-your BigPart rom of choice (I went with CM 11, which you can find in this thread, but there’s also OmniRom, which you can find in this thread, both of which were kindly ported by @Schischu. If you opt for Omni, you’ll also need a flashable zip file of the Superuser app of your choice.)
-your 4.4 GApps of choice (I use the PA Modular Full GApps, but any 4.4 GApps will be fine once you’ve repartitioned)
-Universal Xoom root .zip file, created by @solarnz (which you can find here)
As well as the following on your computer:
-The Android SDK, specifically ADB and Fastboot (if you don’t have this set up yet, start at the very beginning: http://developer.android.com/sdk/index.html)
-a stock android rom for the Stingray (I used HRI66, which you can find here)
-TWRP 2.6.3.0 touch recovery from @runandhide05
And one last thing:
-A good wifi connection (either through a wireless router or using your phone or other device with a data plan)
3.) Reboot your tablet into recovery and flash the non-BigPart TWRP 2.6.3.0 touch recovery. DO NOT REBOOT YET!
4.) Tap the Home icon, tap the Wipe tab, tap the Advanced Wipe tab, and wipe everything but sdcard (that means Dalvik Cache, System, Cache, Data, and Internal Storage)
5.) Tap the Home icon, tap the Reboot tab, tap the Recovery tab. You will get a “No OS” warning, tap “Reboot Anyway”. You will be prompted to install SuperSU – ignore this and reboot into recovery.
6.) Once you’re back into recovery (CAUTION: THIS MAY TAKE SOME TIME. BE PATIENT AND LET YOUR TABLET DO ITS THING!) You may get a warning about data being encrypted, but just tap the Home icon, then tap the Wipe tab. Tap the Format Data tab, type “yes” when prompted, and wait for your data to format. Go back to the main wipe menu, tap the Advanced Wipe tab, and select System and Cache and proceed to wipe them.
7.) Tap the Home icon, tap the Reboot tab, tap the Recovery tab. Again, you will get the “No OS” warning and the prompt to install SuperSU – ignore both of them and allow your tablet to reboot into recovery, which, again, may take some time. (I’ve done this process multiple times and each time, the amount of time that it needed on various reboots was different, so be patient if you don’t want to brick your Xoom.)
8.) Tap the Mount tab. Sdcard, Cache, and Data should be checked; System should be unchecked. Tap the box next to System, make sure that it mounts without any errors, and then uncheck it again. If you’ve made it this far, you’re back to the standard partitions.
9.) Tap the Install tab. Your external sdcard should be showing by default. Flash your standard partition rom (in my case, CM 10.1) and your GApps, if you so choose (though again, they serve no purpose).
10.) Tap the Home icon, tap the Reboot tab, and tap the System tab to reboot into your chosen standard partition rom. Ensure that everything loads (again: this may take some time) and go through the setup process.
11.) Go into Settings and enable developer options (Settings --->About Tablet--->tap Build Number several times until Developer options are enabled.
12.) Go into Developer options and make sure that Android debugging is checked. Now you’re ready for Stage 2.
STAGE 2: Returning to stock Honeycomb
1.) Find your stock Honeycomb rom (as mentioned earlier, I used HRI66) and unzip it into a folder of its own.
2.) Inside the folder you unzipped, you may find another folder designated MZ600_HRI66. Inside that folder, there will be four files, boot.img, recovery.img, system.img, and userdata.img
3.) Copy those files into the folder that has adb.exe and fastboot.exe (if you simply installed the Android SDK as instructed, it’ll be inside the platform-tools folder, which is itself inside the sdk folder).
4.) Connect your Xoom to your computer using a USB data cable (preferably a Motorola one if you have one available) and ensure that there is a notification that says “Android debugging enabled” (if you don’t see this notification, go back into Settings --> Developer options, and make sure that “USB debugging notify” has a check in the box next to it).
5.) Open a command prompt in the directory that contains adb.exe and fastboot.exe (Windows 7 and up, click the File tab and choose “Open Command Prompt”; if you’re on Vista or older, I can’t help you, but I’m sure Google can).
6.) Enter the following command:
Code:
adb reboot bootloader
7.) Your tablet will reboot to the red “M” logo and it should say “Fastboot protocol initiated” at the top in white letters. If so, proceed to step 8; if not, and assuming your tablet has rebooted normally, try step 6 again.
8.) Enter the following commands into your command prompt, one at a time, and let each one compete. You’ll get a series of status updates in both your command window and on your tablet as each process completes. Wait for it to say “Done!” before entering the next command.
Code:
fastboot flash boot boot.img
Code:
fastboot flash system system.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash userdata userdata.img
Code:
fastboot erase cache
9.) Once all those steps have completed, enter one last Fastboot command:
Code:
fastboot reboot
10.) Your tablet should now reboot into factory Honeycomb and you can disconnect from the USB cable. As mentioned before, this is one of those reboots that could take a few seconds up to several minutes, so just be patient!
NOTE: These next several steps are much easier to complete if you have a high-speed wifi connection. At this point, if you don’t have a data connection, don’t panic, at least not yet. I tried multiple times to activate my device on the Verizon network, and while it said it was successful each time, I never managed to get a 3G connection back. Your best bet is to connect to Wifi and continue the process.
11.) On your tablet, go to Settings --> About tablet --> System Updates. More than likely, your tablet has already started downloading the next update, so you can just sit back and wait for it to download. You’ll get a notification when the download is complete. While you’re waiting, on your computer, move boot.img, system.img, recovery.img, and userdata.img from your ADB folder back into a folder where you’ll have them on-hand if you need them again.
12.) Once you get the notification that the update is downloaded, you’ll have the option to reboot and install or install later. Choose to reboot and install. Your tablet will reboot into the stock Android recovery and install the update, then go to the “M” logo screen and more white text will appear. Wait for this to complete and your tablet to reboot again.
13.) Repeats steps 11 and 12 until you receive and install the IMM76L build (I believe that’s the one) – it’ll be Ice Cream Sandwich and your data should be working. If it’s not, then I’m not sure what to suggest. Your tablet will attempt to download the stock 4.1.2 build (JZO45M) and if it completes, it’s not a big deal, but MAKE SURE YOU DON’T INSTALL IT!
14.) Go to Settings --> Developer options and turn on USB debugging again. (If everything is grayed out, tap the On/Off slider in the upper righthand corner to make the checkbox clickable). At this point, you’re ready for Stage 3.
STAGE 3: Re-rooting
1.) On your computer, find the copy of TWRP 2.6.3.0 touch recovery from @runandhide05 (the standard one, not the BigPart one, yet), and unzip it into its own folder. Copy the recovery.img file from the unzipped folder into the same directory that contains adb.exe and fastboot.exe. IT IS CRUCIAL THAT YOU REMOVED THE RECOVERY.IMG FILE THAT YOU USED TO GET BACK TO STOCK EARLIER!
2.) Connect your Xoom to your computer via USB data cable and ensure that the USB debugging notification appears and that your computer recognizes your Xoom.
3.) Open a command prompt in the directory with adb.exe and fastboot.exe and enter the following command:
Code:
adb reboot bootloader
4.) Your tablet will reboot to the “M” logo screen and it will again say “Fastboot protocol initiated”. When it’s ready, enter the following command into your command prompt:
Code:
fastboot flash recovery recovery.img
5.) Once you get the “Done” notification in the command prompt and on your tablet, enter the following command:
Code:
fastboot reboot
6.) Your tablet will reboot, and when you see the “M” logo screen, wait three seconds and press the Volume Down key. “Android recovery” will appear, press the Volume Up key.
7.) Your tablet will now boot into TWRP 2.6.3.0 and it may “hang” at the TWRP splash screen for some time – that’s normal, wait it out, and when TWRP loads, tap the Install tab. Navigate to the root of your external sdcard (if it’s not showing by default), choose the Xoom Universal root.zip file, and install it.
8.) Tap the Home icon, tap the Reboot tab, and tap System from the reboot menu. Your tablet should boot back into ICS, but you should now have a superuser app installed (ChainsDD’s, I believe). If that’s the case, and you’ve still got data functionality, then it’s time to move to Stage 4.
STAGE 4: BigPart and KitKat
1.) Reboot your tablet into recovery (you have two options – either shut down your tablet, power it back on, wait three seconds at the “M” logo screen and then press Volume Down, followed by Volume Up when it says “Android Recovery”, or reconnect your tablet to your computer with a USB data cable, open a command prompt in your adb directory, and enter the following command: adb reboot bootloader)
2.) Reboot your tablet into recovery and flash the TWRP 2.6.3.0 BigPart touch recovery. DO NOT REBOOT YET!
3.) Tap the Home icon, tap the Wipe tab, tap the Advanced Wipe tab, and wipe everything but sdcard (that means Dalvik Cache, System, Cache, Data, and Internal Storage)
4.) Tap the Home icon, tap the Reboot tab, tap the Recovery tab. You will get a “No OS” warning, tap “Reboot Anyway”. You will be prompted to install SuperSU – ignore this and reboot into recovery.
5.) Once you’re back into recovery (CAUTION: THIS MAY TAKE SOME TIME. BE PATIENT AND LET YOUR TABLET DO ITS THING!) You may get a warning about data being encrypted, but just tap the Home icon, then tap the Wipe tab. Tap the Format Data tab, type “yes” when prompted, and wait for your data to format. Go back to the main wipe menu, tap the Advanced Wipe tab, and select System and Cache and proceed to wipe them.
6.) Tap the Home icon, tap the Reboot tab, tap the Recovery tab. Again, you will get the “No OS” warning and the prompt to install SuperSU – ignore both of them and allow your tablet to reboot into recovery, which, again, may take some time.
7.) Tap the Mount tab. Sdcard, Cache, and Data should be checked; System should be unchecked. Tap the box next to System, make sure that it mounts without any errors, and then uncheck it again. If you’ve made it this far, you’ve successfully repartitioned your tablet back to BigPart.
8.) Tap the Install tab. Your external sdcard should be showing by default. Flash your BigPart rom (and, if you’re installing Omni, your superuser zip file, or, if you’re not flashing one of Schischu’s KitKat roms, the corresponding BigPart boot img or the ElementalX kernel). NOTE: BECAUSE THIS WASN'T SUCCESSFUL FOR EVERYONE, FOR THIS STEP, PLEASE FLASH SCHISCHU'S JANUARY 4TH VERSION OF CM 11 FOR THE STINGRAY, WHICH YOU CAN FIND HERE.
NOTE: You probably can flash your GApps at this point as well; however, I’m detailing the process as I had success with it.
9.) Tap the Home icon, tap the Reboot tab, and tap the System tab to reboot into your chosen BigPart rom. Go through the setup process, ensure you have data, and if you do (and you didn’t do so already), reboot and install your GApps.
NOTE: You may get com.android.phone force close errors when going through setup – if this happens, it’s a good thing – pull your SIM card and reboot, complete setup, re-insert SIM card and reboot again.
If this post helped you, then give thanks to the following people (because they did all the hard work):
@bigrushdog (for the hard work on BigPart) @realjumy (for the hard work on BigPart)
@Schischu (for the excellent KitKat roms)
@xyrcncp (for clarifications that led to a minor breakthrough) @rapson2000 (for thinking outside the box and leading to my breakthrough)
There are probably a bunch of other people who contributed that I missed, but I wanted to get this up there in case other people were still having issues.
Reserved to answer any questions that may arise.
LTE data still not working
All your instructions were good and working, up until I reinstalled Cyanogenmod 11 (cm-11-20140203-UNOFFICIAL-2235+0100-stingray.zip). Then I lost data again. I'm guessing from your instructions and how things stopped working that there's something about the re-partitioning process that makes the LTE APKs just stop working.
The Xoom is detecting the LTE network, just as before, there are no bars and no data connection. Looks like I'll have to repartition again and use a ROM that sticks with the old partitions and wait for a possible fix to this issue.
variatbg said:
All your instructions were good and working, up until I reinstalled Cyanogenmod 11 (cm-11-20140203-UNOFFICIAL-2235+0100-stingray.zip). Then I lost data again. I'm guessing from your instructions and how things stopped working that there's something about the re-partitioning process that makes the LTE APKs just stop working.
The Xoom is detecting the LTE network, just as before, there are no bars and no data connection. Looks like I'll have to repartition again and use a ROM that sticks with the old partitions and wait for a possible fix to this issue.
Click to expand...
Click to collapse
I've repartitioned multiple times now - once from stock, rooted Jelly Bean, and got no data, then back to standard partition and CM 10.1 with only 3G, back to BigPart with no data, then I followed the steps that I wrote up here and now I'm BigParted on CM 11 with data. So it's not the repartitioning process. I'm a testament to that. What were you on when you did the BigPart process for the first time?
Edit: if you're willing to do the whole process again, would you try installing the very first CM 11 that Schischu released? I should've specified that that's the rom I installed first after repartitioning this time. One I had working data, I updated to the latest version.
Sent from my HTC6435LVW using xda app-developers app
Help with MZ605 (Everest) stock (step 10 of stage 2)
Thank you very much for your work on the data problem.
I have a Brazilian MZ605 (WIFI + 3G) and the problem I'm facing is that after flashing the stock rom it don't allow me to proceed to the configuration menu if I don't put a valid SIM card, and that is my dead end, it isn't recognizing my SIM card so I cannot follow the rest of your guide...
Do you have any idea on how I could force the stock to ignore the first SIM verification?
Thank you in advance!
LTE data still not working
webeougher said:
What were you on when you did the BigPart process for the first time?
Click to expand...
Click to collapse
I was first using OmniROM of January 12, though I can't quite recall. Then I also tried CM 11 and no dice there. Following your process, when I first reverted to CM 10.1 on original partitions, data was immediately present again.
It was there through all the reversions to stock 3.2.2, and through every OTA update Motorola sent to the device. In fact, some of the updates wouldn't even show up except over Mobile Data.
One thing that might make a difference is that this Xoom is on a business account through Verizon. It's not part of a shared data plan, but there might be a different categorization perhaps?
Anyways, I'm not going through all that partitioning and flashing again just now. I will though, eventually do a Nandroid backup and try again, once I see here or elsewhere that something might have changed for me. I have spent just too much time on this, and data is more important in this case than KitKat.
Thiago Delatorre said:
Thank you very much for your work on the data problem.
I have a Brazilian MZ605 (WIFI + 3G) and the problem I'm facing is that after flashing the stock rom it don't allow me to proceed to the configuration menu if I don't put a valid SIM card, and that is my dead end, it isn't recognizing my SIM card so I cannot follow the rest of your guide...
Do you have any idea on how I could force the stock to ignore the first SIM verification?
Thank you in advance!
Click to expand...
Click to collapse
This is a stupid question, but did you flash the stock rom I linked in this thread, or a stock Everest rom?
Sent from my HTC6435LVW using xda app-developers app
webeougher said:
This is a stupid question, but did you flash the stock rom I linked in this thread, or a stock Everest rom?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Not stupid at all, it could make all the difference!
I flashed the MZ605 Brazilian, MZ601 International and the one you linked. The formers booted and asked for the SIM card and the last just didn't boot. I put two different SIM cards and it didn't work, I was wondering it there were a way to circumvent the first check. I also read somewhere that the MZ601/MZ605 US Retail version didn't check for a SIM card on the first boot, but I didn't find an official stock rom for such a device (I don't even know if these devices exist).
The next trial would be with the MZ600 Verizon 3G, but I'm not that confident that it is gonna work...
Another problem is that I stopped using the 3G data on Xoom for more than one year, so I can't even tell if the SIM card would be recognized nowadays...
Beside that, what choices do we have? Is it possible to avoid the first boot SIM card verification? Is it possible to extract the baseband files from another MZ605 and put them in mine?
Do you know what kind of file/library is the baseband?
Another thing, how the modem stays working if we completely clean the internal storage of Xoom going from the official to the CM11 (on your procedure)? What I'm missing...?
Thank you very much for your guide, I didn't know how to revert the bigPart
Regards,
Thiago
So @webeougher ...I FINALLY had some time to sit down with my Xoom and try this. In the interest of verifying that this process works, I went through your guide step by step without deviation and... SUCCESS! I'm back to BigPart CM11 w/ full 4G LTE!!! Thanks for taking the time to write out such a detailed guide! It was just about perfect.
I have just two things to mention... First, the link to the stock image HRI66 didn't work. I had to look elsewhere (http://rootzwiki.com/topic/1586-stock-images/). Also, in step one of stage 4, the adb command should be "adb reboot recovery", not "adb reboot bootloader"... correct?
One last thing, at this point should we start recommending people not attempt BigPart / CM11 if they start from stock Jelly Bean?
Again, I can't tell you how stoked I am to be back up and running. This... all of it... BigPart, CM11 for Xoom, and the fix for the no data situation... it's all awesome.
Awesome! It's amazing that somebody was able to figure out the process with all of
it's steps, and have it actually work.
I am back on my feet now, have my CM 11 Bigpart, as well as 4G LTE. Woo!
Thank you!
About the only thing I did differently was to do the "fastboot oem lock" after reflashing the
baseline honeycomb partition images. I always thought you had to have the thing locked before
it would allow you to do OTA updates. Whatever.
I then let the OTA updates go by(except for that final one), then did a "fastboot oem unlock"
before applying the universal root. Other than the locking & unlocking, I followed your instructions
exactly. Perfecto!
rmkenney12 said:
Awesome! It's amazing that somebody was able to figure out the process with all of
it's steps, and have it actually work.
I am back on my feet now, have my CM 11 Bigpart, as well as 4G LTE. Woo!
Thank you!
About the only thing I did differently was to do the "fastboot oem lock" after reflashing the
baseline honeycomb partition images. I always thought you had to have the thing locked before
it would allow you to do OTA updates. Whatever.
I then let the OTA updates go by(except for that final one), then did a "fastboot oem unlock"
before applying the universal root. Other than the locking & unlocking, I followed your instructions
exactly. Perfecto!
Click to expand...
Click to collapse
It's not necessary to relock to get OTAs, so long as you're running a pure stock rom.
Sent from my Galaxy Nexus using xda app-developers app
webeougher said:
4.) Tap the Home icon, tap the Wipe tab, tap the Advanced Wipe tab, and wipe everything but sdcard (that means Dalvik Cache, System, Cache, Data, and Internal Storage)
...
8.) Tap the Mount tab. Sdcard, Cache, and Data should be checked;
Click to expand...
Click to collapse
There was aleady a problem with Step 4... unable to mont /cache - therefore Failed to wipe /data and /cache.
Step 8 also showed NO /data-partition.
I downloaded the original Xoom stock boot,system,recovery (MZ601) MZ601_H.6.1-38-5_TMO_Germany...
Code:
fastboot flash boot boot.img
Code:
fastboot flash system system.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash userdata userdata.img
Code:
fastboot erase cache
Click to expand...
Click to collapse
boot status - done!
system status - done!
recovery status - done!
userdata status | | | | | | | | | | | | | | | | | | | | | | - done! (there have been such weird lines)
formatting cache: CAC status: -done!
Rebooting - after 60 min of M-logo I quit.
Is there a way to TOTALLY MANUALLY repartition the xoom and recover everything from scratch?
EDIT: New development: not even in fastboot mode I'm able to flash anything anymore... CWM recovery (recovery-clockwork-touch-6.0.3.2-everest.img and recovery-Tiamat-R4c-100611-1150-cwm.img) for example: status done! Still TWRP
Thank you and Question
First off thank you this worked perfectly for me, everything worked like it was supposed to! Now the question is; After I have followed these steps, can I update to the newer version of CM 11, because there are a couple things that are buggy in the first couple version?
semp3rfi said:
First off thank you this worked perfectly for me, everything worked like it was supposed to! Now the question is; After I have followed these steps, can I update to the newer version of CM 11, because there are a couple things that are buggy in the first couple version?
Click to expand...
Click to collapse
Absolutely. I flashed to whatever the latest nightly was when I completed the process, and I've updated several times through the CM updater as well and data still works as intended.
Sent from my HTC6435LVW using xda app-developers app
Thank you
webeougher said:
Absolutely. I flashed to whatever the latest nightly was when I completed the process, and I've updated several times through the CM updater as well and data still works as intended.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Awesome thanks for the reply!
What does this whole sequence actually accomplish? Is the problem that we have the wrong radios installed, and this is a way to get the right ones installed? If so is there a way to extract the new radios so that they can be installed directly?
I am just trying to understand the process, and see if it can be simplified.
Thanks much for coming up with a solution. I will try it soon.
I'm no developer, but my best theory is that these BigPart roms and kernels use proprietary files from ICS. By taking the OTA to JB, something changed. I tried flashing other radio files and nothing worked, so when it was suggested that only people who had taken the OTA were losing data, I went through this process just on a whim to see if it worked. When it did, I didn't really think much else about it.
Sent from my HTC6435LVW using xda app-developers app
thx
The for this topic really informative
Wow
Talk about a long process but it worked for me! Thank you so very much!
I did have an issue with the google keyboard fc on me after going through the whole process but I ended up downloading the go keyboard (not selecting it) and for some reason that took care of the Google keyboard fcing.
I also used the omnirom instead of cm.
Again, thanks for your hard work!
Wanted to thank you. I pulled out the ole Xoom and flashed Omni and the data wasn't working... But you're instructions got me back on track. Thanks again bro! :good:
On 3 separate Nokia 6.1 (2018) TA-1050 devices, after the OTA upgrade from Android 9 to Android 10 (using either the December 2019 Stable Android 10 Full OTA update with version number V4.10C, or using the May 2020 Full OTA update with version number V4.15C), I encountered a bootloop. Many users with Nokia devices for which Nokia released an OTA upgrade from Android 9 to Android 10 report the same:
After the OTA is applied, the phone restarts, the screen goes black, the phone restarts again, until finally the following screen is displayed:
(sorry for not posting a screenshot - as a new user I am apparently not allowed that privilege until I have made 10 posts, so I have to put in the literal text of the screen instead, using the color scheme of the real screen)
Android Recovery
nokia/plate2_00mm/PL2 sprout
10/QKQ1_190828.002/00ww_4_10C
user/release-keys
Use volume up/down and power.
Cannot load Android system. Your data may be corrupt. If
you continue to get this message, you may need to perform
a factory data reset and erase all user data stored on this
device.
Try again
Factory data reset
Supported API: 3
Boot Reason: enablefilecrypto_failed
In the rest of this post I will refer to this screen as the enablefilecrypto_failed screen.
Note the numbers I indicated in bold in this screen, which indicate that the phone is attempting to start Android 10.
Even though I searched the Internet extensively for several months, I did not find a complete solution for this issue. After a lot of trial and error, I have found a working solution myself, which I am documenting here. The idea behind this procedure is to make sure that both slots in the phone get upgraded to Android 10, which the OTA, by design, does not do.
If you have a Nokia 6.1 or a similar Nokia phone (with A/B slots) with the symptom as described above, you are welcome to try this solution AT YOUR OWN RISK!
Please note that following this procedure will result in the complete erasure of all user data stored on the phone! Save whatever data you need on external storage!
Prerequisites
Android Platform Tools: ADB and Fastboot (download here)
The procedure does not require the phone to be unlocked or rooted.
Procedure
If you are on the enablefilecrypto_failed screen, follow these steps to try to boot your phone from the inactive slot, which should not have been touched:
a. First of all, just for good measure, select "Try again" with the volume keys, then press the power button. The phone will restart. If you get the same screen again, try it up to five times. Your phone should turn off completely after the third time. You can turn it on again to try a further few times.
b. Connect the phone to the computer using the USB cable. If the phone was off, the phone will turn on and show the battery charge screen.
c. From the battery charge screen, or the enablefilecrypto_failed screen, press and hold the volume down key (make sure you do not accidentally select "Factory data reset"), then press and hold the power key. Keep both pressed throughout the power up sequence. You will end up with a screen showing the android one logo and on top the words "Download mode". From now on we will refer to this screen as the bootloader screen.
d. Open a Command Prompt on the computer, and change the current directory of the command prompt to the folder in which the platform tools were installed.
e. Type in the following command, and at its end press the Enter key:
Code:
fastboot getvar current-slot
You will see either: current-slot: a or current-slot: b. On some phones, the slot character may be prefixed by an underscore (i.e. _a or _b). Write down the current slot.
f. We now want to make the inactive slot active. If the current slot was a (or _a), you want to type the following command (if the current slot was prefixed by an underscore, then also put an underscore before b in the following command), then press Enter:
Code:
fastboot --set-active=b
If the current slot was b (or _b), then type the command (if the current slot was prefixed by an underscore, then also put an underscore before a in the following command), then press Enter:
Code:
fastboot --set-active=a
You will see either Setting current slot to 'a' or Setting current slot to 'b', depending on which slot has been made active.
g. Now reboot the phone by typing the following command and pressing Enter:
Code:
fastboot reboot
h. Your phone may come up with the following screen:
Android Recovery
nokia/plate2_00mm/PL2 sprout
9/PPR1.186610.011/00ww_3_54P
user/release-keys
Use volume up/down and power.
Cannot load Android system. Your data may be corrupt. If
you continue to get this message, you may need to perform
a factory data reset and erase all user data stored on this
device.
Try again
Factory data reset
Supported API: 3
Boot Reason: enablefilecrypto_failed
Note that this screen shows that the phone has switched to Android 9, as indicated by the numbers I placed in bold in the above screen.
If so, make sure "Try again" is selected, then press the power button. Your phone will restart and Android 9 will come up, which will give you the opportunity to back up your phone before proceeding.
Backup the phone
a. Make sure your contacts, calendar entries, etc., are completely synchronized with whatever cloud provider you are using (usually Google).
b. To backup Whatsapp messages, go into Whatsapp settings and perform a backup either to the cloud, or to phone memory.
c. To backup SMS and MMS messages, use an app like "Anything to SMS".
d. Connect the phone with the computer using a USB cable, and copy the entire contents of the phone memory to a new folder on the computer. Make sure this copy is complete, including the backups of Whatsapp, SMS messages, and any other app-specific data, as well as your documents, pictures and videos, and anything else you want to keep.
e. If your phone is rooted, you may want to additionally use Titanium Backup to make a complete backup of all apps and their data, and use a custom recovery like TWRP to make a NANDroid backup. Make sure these backups are moved off the phone, as you will be required to perform a complete "wipe" of the entire phone.
To make further troubleshooting easier, you may want to enable Developer Mode and USB Debugging:
a. Open Settings->About phone
b. Scroll down until Build number
c. Tap 7 times on Build number
d. When prompted, enter phone PIN or password
e. Exit Settings
f. Open Settings->System->Advanced->Developer options
g. Scroll down to USB debugging and turn it on
h. Exit Settings
i. If not prompted to allow USB debugging, disconnect and then reconnect the USB cable. You should see a prompt on your phone asking whether to allow USB debugging from a specific device (the computer the phone is connected to). You should answer affirmatively to this prompt.
Further preparations
a. If your phone is rooted, disable all apps that require root (for example the firewall), and completely uninstall Magisk, restart the phone when prompted.
b. Before continuing, either connect the phone to a charger, or make sure the phone is (almost) completely charged.
c. Open Settings->System->System update. Let the phone check for updates, download the update, follow the prompts, resume the upgrade it necessary, allow the system update to install, and, when prompted, restart the phone (even if you already did all of this in the past). Your phone will restart and return to the enablefilecrypto_failed screen. Before continuing with the next part, make sure the enablefilecrypto_failed screen shows the version numbers corresponding to Android 10 (as shown at the beginning of this post).
Booting into recovery from the enablefilecrypto_failed screen showing the version numbers corresponding to Android 10
a. If you have a custom recovery permanently installed, follow the next steps until you see the custom recovery screen.
b. If disconnected, connect the phone to the computer using the USB cable.
c. While making sure "Try again" is selected, press the power button.
d. The moment the phone restarts, press and hold the volume up key, then press and hold the power key. Keep both pressed throughout the power up sequence. If you have a custom recovery permanently installed, it should come up now. If you have the stock recovery, you will end up with a screen showing an android robot lying down on its back, with a red triangle over its open belly, and the words "no command" below it. To enter the stock recovery from this screen, hold the power key and tap the volume up key once. You will then see a screen with a larger menu (see below); this is the stock recovery screen. From now on we will refer to this screen as the stock recovery screen. If you end up again with the enablefilecrypto_failed screen instead, try the above steps again; the timing of step d is quite critical.
The stock recovery screen looks like this:
Android Recovery
nokia/plate2_00mm/PL2 sprout
10/QKQ1_190828.002/00ww_4_10C
user/release-keys
Use volume up/down and power.
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Mount /system
View recovery logs
Run graphics test
Run locale test
Power off
Supported API: 3
Boot Reason: (null)
Using ADB to sideload the Full OTA upgrade from the stock recovery screen
Please note the links provided here are the official links to the Full OTA for the Nokia 6.1 (2018) "PL2_sprout". If you are attempting these steps on a different Nokia phone, you will have to find the correct links for the corresponding Full OTA upgrade. Do not use the links provided here.
a. Check the Android 10 version number in the stock recovery screen.
b. If the Android 10 version is 4_10C, then, on the computer, download the Full OTA upgrade from here: https://android.googleapis.com/pack.../c6260831df0acdfe9828f18bcea7ffb556f4b2e5.zip
If the Android 10 version number in the stock recovery screen is 4_15C, then download the Full OTA upgrade from here: https://android.googleapis.com/pack.../bb7fea8687fc11e36c298f2b8e49c0116a174e11.zip
c. If you have a custom recovery on your phone, now press the keys to start the ADB sideload.
d. If you have the stock recovery, on the phone, use the volume down key to move the selection to "Apply update from ADB" and press the power key to confirm the selection.
e. On the computer, open a Command Prompt, and change the current directory of the command prompt to the folder in which the platform tools were installed.
f. Type in the following command, replacing [complete path to filename] with the complete and exact path to the file downloaded in step b above, including the full name of the file itself, and at the end of the command press the Enter key:
Code:
adb sideload "[complete path to filename]"
The phone screen will show it is finding the package, opening the package, verifying the package, and then it will install the package in two steps: Step 1/2 and Step 2/2.
g. When the two steps have completed, you may see some error messages about the recovery log on the phone. You can safely ignore these errors.
h. The menu entry selected on the phone screen should now be "Reboot system now". Press the phone power button to restart the phone.
i. In some cases, the phone will now start normally into Android 10, with all data intact. If so, congratulations! You can skip the rest of this post.
j. In most cases, the phone will again show the enablefilecrypto_failed screen. You will want to select "Try again" with the volume keys and press the power button to try to start the phone normally again.
k. When you have tried this 5 times, you can assume it is not going to work. Select "Factory data reset" with the volume keys and press the power button.
l. The phone will prompt you with a warning "Wipe all user data? THIS CANNOT BE UNDONE!" Select "Factory data reset" with the volume keys, and press the power button.
m. The phone will now wipe all user data, and then turn off.
n. When the phone has turned off for a good while, press the power button (you may need to hold the power button a bit longer than usual). The Nokia logo should come up. The Nokia logo will stay on the screen for a relatively very long time. Your phone should eventually start the Android 10 startup sequence ("Welcome" etc.), in which you will be asked to set up your phone.
o. My recommendation is to connect the phone to WiFi and allow it to download and install all applicable OTA updates before you continue to set up the phone. These incremental OTA upgrades do not usually cause the issue we experienced with the Full OTA upgrade from Android 9 to Android 10.
Links to various sites, posts and blogs which I used to prepare the above:
Reddit describing the issue, with actual screenshots: https://www.reddit.com/r/AndroidPreviews/comments/f2uqz7/nokia_61_got_stuck_in_loop/
Another article describing the issue, with a simpler fix which works for some phones: https://www.techmesto.com/possible-fix-nokia-smartphone-stuck-on-download-mode-after-ota-update/
Article describing how to apply OTA using ADB Sideload, including links to official OTA downloads: https://www.the***********.com/nokia-6-1-plus-android-10-update/
Link to discussion on Nokia community which was the main inspiration for my above post: https://community.phones.nokia.com/discussion/comment/149245/#Comment_149245
Link to thread here on XDA Developers about what seems to be a similar issue with the Nokia 7.1: https://forum.xda-developers.com/nokia-7-1/help/android-10-bootloop-update-t4022893/page3
Link to official TWRP FAQ with explanation about ADB Sideload: https://twrp.me/FAQ/
Link to unofficial TWRP recovery which supports encryption on the Nokia 6.1 (2018) (useful only if the phone has an unlocked bootloader): https://forum.xda-developers.com/nokia-6-2018/development/unofficial-twrp-3-4-0-0-team-win-t4122949
Information about the install of Magisk: https://www.xda-developers.com/how-to-install-magisk/
Information about applying OTA updates with Magisk installed (this procedure does not seem to work for the Full OTA upgrade from Android 9 to Android 10, through no fault of Magisk): https://topjohnwu.github.io/Magisk/ota.html
I welcome any comments to this post.