Related
If you haven't already done so, install Rom Manager and flash Clockworkmod Recovery. It doesn't replace the actual recovery partition or the files that restore it so it won't affect flashing the update.
If you received an OTA notice don't flash it. You can go into /system/cache and copy it, or download it from the links in other threads. Place the update zip (no need to rename it) on the root of your sd card.
To install the update you must be fully stock (root is okay). That means any changed or deleted system files (including bootanimation.zip) will prevent the update from flashing. You will get a status 7 error. If you used Bloat Freezer you must defrost all before flashing the zip or it will error.
Also, have available whatever zip you used to root your Nexus one (i.e., su.zip or superboot, etc.) and put on the root of your sd card.
Once your system is back to stock reboot into CWM recovery and select flash zip from sd card. Then flash the 2.3.6 update file. Then DO NOT reboot yet. Now flash your root zip. After you have flashed both the udpate and the root zip you can reboot your phone. No need to wipe anything.
When your phone reboots you will have 2.3.6 and it will still be rooted. No bootloader gymnastics necessary.
I am using stock (almost) version of GRJ22 , but unfortunatelly I got the status 7 error when I tried to apply the update via clockworkmod recovery. I guess that's because I have already integrated some system apps into ROM using Titanium Backup.
So, if I flash stock vanilla GRJ22, then SU, then GRK39F (the incremental update) and finally SU again, won't that do the job??
Thanks..
Nikos_s3 said:
I am using stock (almost) version of GRJ22 , but unfortunatelly I got the status 7 error when I tried to apply the update via clockworkmod recovery. I guess that's because I have already integrated some system apps into ROM using Titanium Backup.
So, if I flash stock vanilla GRJ22, then SU, then GRK39F (the incremental update) and finally SU again, won't that do the job??
Thanks..
Click to expand...
Click to collapse
Yes, that will do nicely. Just need to get back to GRJ22 stock before you can flash the udpate. The updater-script does an assert and checks the md5 checksum of every system file before it allows the update to flash. If it doesn't find all stock files or checksums don't match what it is looking for, you get a status 7 error and the line above will show which file it stopped on. So you can look at those messages and keep restoring files it wants (if only a few) without having to flash completely back to stock.
I guess that would take much time, as almost all of my google apps are integrated into ROM...so I will try to follow the procedure I wrote earlier and if that won't work, I will try a ready stock,rooted ROM (Fireb33 has done it already)..
thanks mate..
Why so complicated?
You can update to 2.3.6 AND keep root even much more simple:
1.) Update from OTA to 2.3.6 (and loose root).
2.) Flash Superboot from Madaco and get back root.
Done in 3 minutes.. No need to flash, recover, overwrite and/or whatever, no need for ADB, no messing:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/
Bexton said:
You can update to 2.3.6 AND keep root even much more simple:
1.) Update from OTA to 2.3.6 (and loose root).
2.) Flash Superboot from Madaco and get back root.
Done in 3 minutes.. No need to flash, recover, overwrite and/or whatever, no need for ADB, no messing:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/
Click to expand...
Click to collapse
That's only for those who have the bootloader unlocked?
_raz_ said:
That's only for those who have the bootloader unlocked?
Click to expand...
Click to collapse
Well, yep. That method indicates your (phones) bootloader is unlocked. But as it's the N1, unlocking the bootloader is just 19 (up to 25) characters away -> "fastboot(-linux) oem unlock".
Edit: By the way, i looked up that post from an android platform engineer:
Code:
groups.google.com/group/android-platform/msg/b7d83992dd92accb?dmode=source
The N1 is just made for that.
tried superboot but wifi down
I flashed the update for 2.3.6 and then superboot but my wifi gives an error when I try to turn it on.
New Superboot file for GRK39F?
Is there a new Superboot file for the new OTA update?
jboxer said:
If you haven't already done so, install Rom Manager and flash Clockworkmod Recovery. It doesn't replace the actual recovery partition or the files that restore it so it won't affect flashing the update.
If you received an OTA notice don't flash it. You can go into /system/cache and copy it, or download it from the links in other threads. Place the update zip (no need to rename it) on the root of your sd card.
To install the update you must be fully stock (root is okay). That means any changed or deleted system files (including bootanimation.zip) will prevent the update from flashing. You will get a status 7 error. If you used Bloat Freezer you must defrost all before flashing the zip or it will error.
Also, have available whatever zip you used to root your Nexus one (i.e., su.zip or superboot, etc.) and put on the root of your sd card.
Once your system is back to stock reboot into CWM recovery and select flash zip from sd card. Then flash the 2.3.6 update file. Then DO NOT reboot yet. Now flash your root zip. After you have flashed both the udpate and the root zip you can reboot your phone. No need to wipe anything.
When your phone reboots you will have 2.3.6 and it will still be rooted. No bootloader gymnastics necessary.
Click to expand...
Click to collapse
I want to update to gingerbread and looking for the proper guidance going forward. I've done some looking around the forums but i'm still unclear if i need to unroot or install a stock build, etc. What i know is the phone is rooted and sim unlocked. How can i check to see if the bootloader is open/locked?
Current specs:
android version 2.2.1
Baseband 32.41.00.32U_5.08.00.04
Kernal Version 2.6.35.9-cyanogenmod
Mod Version: Cyanogenmod-6.1.1-N1
Build: FRG83D
edit:
Please treat me like an idiot and walk me through this process. It's be utterly frustrating and I'm a stone's throw away from busting out my Nokia 3390 (equipped with led disco keypad).
If your bootloader is unlocked you will see an unlocked padlock on the boot up screen...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About the guide
This guide is to provide information about the phone and directions about modding your phone. Most of the stuff is already posted in the forums while some of it is not. I'll try my best to explain how the stuff works for Moto E. How to Root, recover, troubleshoot so you don't screw up your phone by flashing something you're not supposed to.
Standard Disclaimer:** I'm NOT responsible for any damage you do to your phone trying to mod it. Understand how to recover from issues carefully. **
Index
I just bought a Moto E, now what?
Starting Up -Drivers, ADB and Fastboot.
Facts - Bootloader & Recovery.
Beginning the workout
Unlocking Bootloader
Flashing Custom Recovery
Rooting.
I just bought a Moto E, now what?
Congratulations on your phone. Now you should understand the device you have.
Moto E has three variants,
XT1021 - Single SIM
XT1022 - Dual SIM
XT1025 - Dual SIM with TV
Determine what variant you have. Its important as some mods maybe specific to one device and might not work with other.
To get more info about your device, I'd recommend giving this FAQ thread some time.
[FAQ] Frequently Asked Questions For Moto E
Starting Up - Drivers, ADB & Fastboot
So let us begin. You need to setup your system first.
Drivers, Get your drivers from Motorola Motorola Device Manager. Install it.
ADB & Fastboot.
[Option 1]
(Android SDK), Android SDK is the Android Software Development Kit. It includes the tools to develop apps and debug your device.You need it in order to mod your device and recover sometimes.Get it from Android SDK Its a big package in terms of size.
[Option 2]
If you don't plan to develop anytime soon and concerned with the size, you can get the Minimal ADB & fastboot from [TOOL]Minimal ADB and Fastboot
Setting UP ADB & Fastboot:
You need to set you path variables so you can run ADB & Fastboot commands without worrying about your present directory.
Extract your SDK package to a directory. (or installation path in case of minimal)
Run SDK Manager.exe. It might show few packages available to download. Tick everything under tools.Click Install packages. Accept license. Install
Naviagte to platform-tools (it should have files adb.exe & fastboot.exe)
Copy the path
Now goto Control Panel > System
Click Advanced system settings
Click environment variables
In the box, find 'Path' under system variables. Select it and click Edit
Now, Paste your SDK path in the Variable Value after a ; (It should be something like this C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;I:\Android SDK\platform-tools Click OK
Done, close the boxes and windows.
Now time for validation. To verify if you've setup the system correctly.
Get your phone and goto Settings>About Phone.
Tap on Build Number 7-10 times (until it says 'You are a developer'), You've enabled developer options.
Goto Settings> Developer options.
Under Debugging, tick USB DebuggingClick OK.
Connect your phone to your PC (on a USB 2.0 port). It might install some drivers, let it finish.
Now open the command prompt on your PC.
Type
Code:
adb devices
.
You will get a prompt on your phone to authorize. Tick 'Always Allow from this computer' And click OK.
It will show the device ID followed by 'device'.
Done, your system is ready.
IMP: If you encounter some errors. Check Troubleshooting.
Facts - Bootloader & Recovery & Rooting.
Bootloader
Bootoader is a small code that reside in your device. When your phone is turned ON, it loads all the hardware and the software of your device and make your phone come alive.
Locked BL & UNLocked BL: Locked BL is a little insurance (for most users)for your device. It checks everything your system can flash(install) thus helps to keep it safe from unwanted or corrupted files. This sounds cool at beginning but is a nightmare for developers. This means there is no way to rewrite the stock recovery of your phone and limiting the things you can do with it(bye bye custom ROMs).
Unlocked BL on the other hand allows to rewrite the recovery (almost everything) on your phone with a custom one, but it also include the risks(everything good, comes with a price). You Lose your warranty (permanently) and your phone is vulnerable to bricking.
Its totally your choice if you want to unlock your BL or wish to remain on stock.Recovery
Then we have the Stock Recovery, this little part of your phone is also locked and cannot be removed or changed from your phone, it will allow you to make Recovery stuff like Full Wipe (Data and Cache) and install Update.zip(specific only) files.
A custom recovery is a special recovery. This allows Android Phones to do recovery tasks, like deleting data, installing recovery Zips and so on; The tasks you are allowed to do with Stock Recovery are pretty basic. Here is where TWRP comes into play.
TWRP is a Recovery that allows you to not only do basic tasks but also create Backups, Restore Them, Fix Permissions and quite a lot of other useful stuff like flashing Custom ROMs.
A Custom Recovery is installed by flashing the Recovery Partition in your Android Phone with a Custom Image.
Most importantly and commonly, Recovery is used to flash update.zip files. These files could be anything from ROM zip to apps,or certain modified system files. Whenever you see the term, "Recovery flashable", this is what meant by it. They are always in *.zip format.Rooting.
So, what’s rooting and why everyone talks about it.
Phones come “locked” , this means users can only do basic usage of their phones, installing/uninstalling apps, wallpapers and basic stuff. You can see but not touch any System file, or change the actual behavior of Android. Rooting just means you have access to your phone like an Administrator(in windows) or SuperUser(in linux), meaning you can access and change system files, delete/create files and folders and so on.
Rooting simply involves giving user rights to modify system, this is done by pushing (installing) 'su' binary into system. This can only be done by a Custom recovery and needs unlocked Bootloader. There are other methods to push 'su' binary to android system but none of those work as of now for Moto E. Unlocking BL and flashing through TWRP is the only method available. Beginning the workout
So now that you know your phone and the terms, you can begin modding it. The process followed is simple:
Unlock your Bootloader
Flash a custom Recovery
Flash Root binary
Flash the custom ROM (Optional)
Unlocking your Bootloader:
This is the first step for modding.
IMPORTANT: Unlocking your Bootloader will void your warranty permanently(Not applicable to EU users.). You cannot claim your warranty once you request the unlock key. No matter if you don't unlock, relock it or the issue is unrelated to Bootloader. That is Motorola Policy.
Also, all your apps, data, photos,music on your internal memory will be wiped make sure to back it up before proceeding.
You can follow the Guide to unlock BL by @Falcon G
[GUIDE]Unlock Bootloader - Moto E
It is well detailed.Flash Custom Recovey
After you have unlocked your Bootloader, you can flash a Custom recovery.As of now, TWRP & CWM are available for Moto E
You can easily flash it using the TWRP manager app from play store (not tested) Play Store Link
Or you can flash the recovery manually:
Manual Flash:
Download TWRP from TWRP.. Or ClockworkMod from this thread.
If its an *.img file then rename it to recovery.img . If its compressed archive (*.zip or *.tar) then extract and rename it.
Boot you phone into fastboot mode. (See tips)
Connect you phone to PC
Goto the folder where you extracted your recovery. Shift+Right Click, select 'Open Command Prompt Here'.
Type in command prompt
Code:
fastboot flash recovery recovery.img
(it should give a partition size mismatch error, don't worry about it)
Reboot.
Done.
Root
You have a custom recovery, now you can flash the root package.
You can check this thread for root, or follow the procedure below.
Download the SuperSU from this thread. DO NOT Extract it.
Copy the .Zip file to your phone. (Internal sdcard recommended)
Boot into recovery(See Tips)
Chose, flash Zip from sdcard
Chose the zip file you copied and confirm
Reboot
Done. You are now rooted. Check the phone it should have the SuperSU app.
[Optional] Flashing a custom ROM
Finally, you can flash your desired Custom ROM.
IMP: Please DON NOT ask for recommended/best/stable ROM in this thread or anywhere in the Forum. It is against forum rules
Make a complete Backup, Most important, in case you get into some error, you'll need it to recover.
You will lose your apps in the process when you wipe /data. So backup your apps too.You can use Titanium Backup or any other app from Play Store.
Download the required ROM from Dev section.(Make sure you have the correct ones depending your variant)It should be a *.zip file. DO NOT extract.
[Optional] Download Gapps. Make sure you have the ones for KK.It should be a *.zip fil as well. Again, DO NOT extract.
Download any add-ons required (like the dual-sim fix for CM)
Copy the files to your sdcard root directory, or any folder just remember it(internal recommended, however external will also work fine)
Boot into recovery.
Make a backup. Chose backup & restore amd create a complete backup.
Wipe /data /cache /dalvik cache.In case you are updating the same ROM, like flashing a nightly, you can skip wiping /data and only wipe /cache and /dalvik cache.(just for reference it is called dirty flashing).
Select 'Install zip from sdcard', navigate to the ROM .zip and select it. Let it finish.
Similarly, flash any Add-ons you have like gapps.
Reboot. First boot will take some time, be patient.
Tips and Troubleshooting
Commands can be entered via command prompt after you've setup the ADB. However, if you don't want to connect to your PC for a simpe command, download Terminal Emulator from Play Store.
Boot into Bootloader
ADB
type into cmd
Code:
adb reboot bootloader
Terminal
Code:
reboot bootloader
Manually
Power off,
Hold Power+VolUp+VolDown
In Bootloader, VolDown is used to scroll, VolUp is used to select
Boot into Recovery
ADB
Code:
adb reboot recovery
Terminal
Code:
reboot recovery
Manual
Power Off.
Hold Power+VolUp+VolDown
Scroll to recovery by using VolDown
Select Recovery by pressing VolDown
Move your App Data to sdcard using Link2SD (Coming Soon)
Flashing back your stock ROM.
Follow this guide.
[GUIDE] Restore Moto E Stock Firmware.
Manualy updating official 4.4.4 with TWRP.XT1022
Requirements: Unmodified Stock 4.4.2. Your system shouldn't be modified. All your system apps should be present & unmodified. Doesn't matter if you're rooted or have TWRP. If you have some stock files missing, either restore a nandroid if you have or flash stock ROM. Just follow troubleshooting steps.
Troubleshooting:Fixing fie verification error due to modified system files.
Extract your stock ROM
Boot to fastboot mode (bootloader)
Flash these files ONLY
Code:
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
This will restore your system to stock without afecting Recovery or user apps.
Reboot
Now continue with flashing the update
Thanks to @Deadly for verifying this method.
Flashing the Update .zip
Method 1: A little difficult,involves manually replacing the updater script, apt for advanced users
If you already have the original OTA file (Either extracted or downloaded)
Download the updater script from here. updater script
Either extract the .Zip file or use a file manager to navigate to META-INF>com>google>android
replace the updater script by the modifed one. Rezip if you've extracted (7-Zip recommended with 'store' compression)
Copy the zip to your sdcard or external card.
Boot into Recovery(TWRP)
Wipe Cache & Dalvik
Select Install
Select your Zip file and confirm.
Reboot
Done.
Method 2:.Easier method and ready to flash zip
If you haven't downloaded the OTA or don't mind downloading an additional file (~60 MB)
Download file .Blur.Zip
Copy the zip to sdcard (internal or external)
Boot to recovery
Wipe cache and Dalvik
Select Install.
Select the Blur.zip
Reboot
Done.
IMP:
Flashing will take a few minutes so be patient.
Some users have reported that after OTA custom recovery doesn't stick(unconfirmed as of now).
If you flash it using TWRP, your custom recovery will be intact and you can re-root.
Thanks to @Gogeta for providing the OTA Zip file.
Nice Guide I'll reserve one here for future
Nice job man.
Falcon G said:
Nice Guide I'll reserve one here for future
Click to expand...
Click to collapse
Hetalk said:
Nice job man.
Click to expand...
Click to collapse
Thanks guys. Remind me if I've missed something.
Any tips on SIM Unlock method
neo.ank said:
Thanks guys. Remind me if I've missed something.
Click to expand...
Click to collapse
I have rooted Moto E but with SIM Lock. Any custom ROM can remove this?
orionmb said:
I have rooted Moto E but with SIM Lock. Any custom ROM can remove this?
Click to expand...
Click to collapse
Not likely. Though it depends on the type of lock it has.
BTW, whats your variant and your carrier.?
neo.ank said:
Not likely. Though it depends on the type of lock it has.
BTW, whats your variant and your carrier.?
Click to expand...
Click to collapse
I have XT1021 and locked to O2 UK. Cannot find anyone from the paid services who can provide the unlock code so decided to root and investigate if its possible this way. Running CM11 (4.4.4).
A much appreciated thread. Good work buddy! :good::highfive:
But a clarification is regarding warranty:
neo.ank said:
Unlocking your Bootloader:
This is the first step for modding.
IMPORTANT: Unlocking your Bootloader will void your warranty permanently. You cannot claim your warranty once you request the unlock key. No matter if you don't unlock, relock it or the issue is unrelated to Bootloader. That is Motorola Policy.
Also, all your apps, data, photos,music on your internal memory will be wiped make sure to back it up before proceeding.
Click to expand...
Click to collapse
While Indian customers will deinitely loose warranty if they've rooted or unlocked the boot-loader, I don't think it's applicable to EU customers. Please look here for more information.
Please make the appropriate changes if I'm right. Cheers!
orionmb said:
I have XT1021 and locked to O2 UK. Cannot find anyone from the paid services who can provide the unlock code so decided to root and investigate if its possible this way. Running CM11 (4.4.4).
Click to expand...
Click to collapse
You will need the unlock code. Flashing a ROM wouldn't unlock it.
Perhaps the paid unlock services haven't listed it yet.It might be available in near future. Can't say anything for sure.
Ex-Hunter said:
A much appreciated thread. Good work buddy! :good::highfive:
But a clarification is regarding warranty:
While Indian customers will deinitely loose warranty if they've rooted or unlocked the boot-loader, I don't think it's applicable to EU customers. Please look here for more information.
Please make the appropriate changes if I'm right. Cheers!
Click to expand...
Click to collapse
Added to the guide. :good:
Added manually flashing OTA for XT1022 using TWRP
neo.ank said:
Added manually flashing OTA for XT1022 using TWRP
Click to expand...
Click to collapse
Thank you for the extensive guide and update instructions.
So I should flash stock ROM, then flash TWRP
then the update.
Is it correct process.?
coefficientoffriction said:
Thank you for the extensive guide and update instructions.
So I should flash stock ROM, then flash TWRP
then the update.
Is it correct process.?
Click to expand...
Click to collapse
Yes you are absolutely right.
neo.ank said:
Yes you are absolutely right.
Click to expand...
Click to collapse
I'm flashing stock ROM now. I will post the result after trying your file.
Its not working....It shows failed using step 2... !!
dubai1991 said:
Its not working....It shows failed using step 2... !!
Click to expand...
Click to collapse
Which method did you use.?
And can you post the exact error you got.? at which step.?
it fails while verifying the zip file. tried with unticking the zip file verification and error is binary error... !!!
---------- Post added at 08:04 PM ---------- Previous post was at 07:58 PM ----------
Method 2.. Zip file verification failed.
dubai1991 said:
it fails while verifying the zip file. tried with unticking the zip file verification and error is binary error... !!!
---------- Post added at 08:04 PM ---------- Previous post was at 07:58 PM ----------
Method 2.. Zip file verification failed.
Click to expand...
Click to collapse
Is your system unmodified.?
Have you modified or removed any system app?
Where is the Ota update zip....
Sent from my XT1022 using XDA Premium 4 mobile app
Does anyone have or know where to get a stock recovery image for the BTV-W09?
When I flashed the US "003" update manually through the dload folder method, my TWRP was replaced by the stock recovery. I have left it there, and since flashed TWRP to recovery2. The update failed, but I ended up with stock recovery and the tablet no longer rooted. I would try that first. If that doesn't work for you and if you are on the US version "002" firmware let me know and I should be able to send you a backup of my recovery partition bit if you need the eRecovery from the recovery2 partition, I will be unable to help you.
I am on the US version “003”, I updated before flashing TWRP and rooting. TWRP was flashed recovery not recovery2. No worries though, Im sure someone will post a recovery as rooted people will be needing to flash OTA updates soon.
If you are on "003", try updating the unzipped "Update.Zip" from the dload file. I found a copy of the update.zip on my internal SD in directory called HwOUC. If you can't find it, I still have my file. The Update will most likely fail, but that should give you the standard recovery back. then I suggest you flash TWRP to Recovery2. TWRP actually is easier to access from Recovery2 becuase all you have to do is hold the volume up key down for a few seconds from the unlocked bootloader screen to boot into TWRP. Once you have TWRP re-installed you can then just flash the super user zip file to regain your root.
I am not sure if it is because I now have unlocked the bootloader, have recovery2 with TWRP or updated the file to enable the 5Ghz modem , but even with having the standard recovery partition back my system did not pass the altered system check and allow me to flash the OTA. I am not quite experienced enough to try and use Flashfire to force the update, since there is a warning about Huawei devices being easy to hard brick. Hopefully someone who has updated and then rooted will post an .img file of the updated system partition so it can be flashed with TWRP (at least I think that is what those of us who have already rooted will need to do).
I looked for the update.zip but it doesn’t exist anywhere. These updates are usually removed after the update completes successfully. Plus I’ve done a factory reset since updating, which may have deleted it. I wanted to see if enabling the 5GHz radio would stick after the reset (it did). The 5GHz radio hack was really my only reason to root. I didn’t alter my system partition with TWRP, so I may still be able to take an OTA update if I had the factory recovery. Ive stopped rooting all of my non Nexus devices. Since Google releases almost monthly security updates which usually unroots anyway it’s just too much hassle to keep root. If you want to post the update.zip somewhere I could give it a try, if not that’s cool. Im sure a factory image will be available at some point.
I have posted the Update.zip file to the following location:
http://www.mediafire.com/file/ug1pe2w38ddkxm9/update.zip
Let me know how things go.
Coming from a Nexus 7 I'm use to many of the img files you flash for restoring.
Using update extractor I now see many of those files (003 update) and some I have no idea about or how to flash them.
BOOT.img - OK
CRC.img - ?
CURVER.img - ?
EFI.img - I know what EFI is just never flashed it on an Android device.
FASTBOOT - OK
FW_HIFI.img - ?
FW_LPM3.img - ?
RECOVERY.img - OK
SENSORHUB.img - ?
SHA256RSA.img - No what it is normally but never flashed.
TEEOS.img - ?
TRUSTFIRMWARE.img - Interesting, but have no idea. - ?
VERLIST.img - ?
XLOADER.img - ?
Like many of us I'm in the same boat. Unlocked, Flashed recovery and rooted and cannot install update 003.
I've flashed the recovery.img from update 03. I've done a factory reset a few times. Odd enough it maintains 5Ghz wifi after doing a reset. I'm stumped and not sure of so many of the other .img files. Might one of them help me get the update to pass if I flash it. That or we wait for a full release and not an OTA to grab all the files we need. Really think I need system.img to make it work but the update doesn't include it.
Thanks johe for providing the 003 update.zip. I may try flashing the recovery.img this weekend. Ill let you know how it goes.
Jmjm003, I believe the issue with updating with the OTA is due to changes detected in the system partition after rooting/unlocking. Im not sure of a way around this other than flashing the full system partition, and we don’t have the factory ROM available yet. Im also new to Huawei devices and their partition structure so hopefully the development community will grow around this device and provide better solutions. I also can confirm the 5GHz stayed enabled after a factory reset, the question remains would it hold after an OTA update.
I have a UK XT1604 Retail device which is running the current TWRP and is rooted with the stock rom.
The device was rooted with the guide from here, but at the time I didn't realise device encryption was not enabled...
Now I'm trying to enable to device encryption, but the process never starts (by the looks of it) the phone reboots to the Moto/Lenovo logo and just sits there. A manual reboot brings back the normal OS with no changes. I've seen some other posts which say I need to un-root, and other which say I just need to re-flash the boot.img file
Can someone tell me the correct process for enabling device encryption and re-rooting the device after.
I was unable to find the stock UK Retail image for this phone, but I have found a o2 version - can I use any .img files I need from that safely ? My other option is - I have an identical none-rooted device, if I fastboot TWRP (rather than install) can I extract and use the .img files from that device on mine? - This has been uploaded this morning - but its not 100% clear is this is UK and for the XT1604
Can anyone confirm the current 3.1.1-0 supports encrypted file systems and can access them?
Very new to all this Android stuff so any help is very welcome.
You should be able to unroot from the SuperSU app (at least that's what I did) and then encryption will work normally.
bsevcenk said:
You should be able to unroot from the SuperSU app (at least that's what I did) and then encryption will work normally.
Click to expand...
Click to collapse
I'd seen the option but wasnt sure if I needed the full un-root, or just 'disable super user' I presume once I've encrypted I just need to re-flash the SuperSU zip file?
iam-q said:
I'd seen the option but wasnt sure if I needed the full un-root, or just 'disable super user' I presume once I've encrypted I just need to re-flash the SuperSU zip file?
Click to expand...
Click to collapse
You'll need to do a full un-root, encrypt, and then you can flash the SuperSU zip again.
So the encryption worked fine & is set with a password. Now I'm unable to access TWRP in recovery mode as it won't accept the known working password.
I Changed the password to a PIN and that allows me to access TWRP - but if I change it back to a password TWRP flat refuses to accept it. I've seen old issues relating to earlier versions to TWRP where people had the same issue, but nothing relating to the current version. Any ideas?
I just bought the Honor 8 and immediately unlocked and rooted it via Magik. Of course not long after that, I get a notification that there is an update available. You obviously cannot update the phone by simply pressing the "update" button since we have a non-stock recovery. I did a fair amount of research to find out how I could get the update and I wanted to share what I found. All of this information is out there already, but generally speaking it is spread out in many different threads. Hopefully these directions can help someone else.....
First, the usual disclosures.....
Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this GUIDE
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
1) Make a NANDroid backup using TWRP: if the new update locks the phone, you will need this backup to restore data after unlocking it
2) Unroot your phone: honestly I did not do this step myself because I simply didn't think about it. The update process worked for me without unrooting but I am also using Magik which doesn't alter the system files. To ensure success I would definitely recommend you unroot. You will have to reroot the phone after the update regardless if you unrooted or not, so you aren't saving any steps by keeping root at this point. If you have used a different root method besides Magik, you must unroot prior to attempting an upgrade.
3) Obtain stock recovery.img file: the update won't work with TWRP as your recovery, so we need to flash the original Huawei recovery to replace TWRP. If you already have a copy of the stock recovery skip to step 4. If you are like me you don't have a copy of the stock recovery image on hand and we will need to extract it from the stock ROM image. Using a computer (not your phone) download the stock ROM image for your device. This website seems to have a list of recent versions and it is where I downloaded the L14 B389 version that I used.
Download the Huawei Update Extractor software and unzip the folder on the computer. Open the HuaweiUpdateExtractor app and use the software to extract the "Recovery.img" file. Here is a Youtube video showing how to do this. Please note, although the video shows several files being extracted you only need to extract the "Recovery.img" file for our use. Move the stock recovery image to your ADB folder so you can flash it in step 4.
4) Flash the stock recovery image: use the stock recovery file and flash it to recovery using the same instructions as you used to flash TWRP in the first place. If you need a refresher, look at section 2 (parts 1-5) of the first post in this thread. Just make sure you substite the name of the stock recovery image instead of the TWRP.img
5) Reboot into system
6) Install Update: go to the Settings - System Update menu on your phone. In the upper right corner, click on the three dots and it will bring up a menu where you can choose "Download latest full update". Click on this. This will start the update process by downloading the full ROM and not just the smaller update package. For me the package size was approaching 2gb, so make sure you are ready to handle that size transfer. After the download is complete, start the update process. I was nervous at first, but everything went fine. If for some reason the update fails, I would reboot and try again. I did have one failure, but I cannot explain if it was a bad download, or something I did wrong (like not unrooting the phone prior to attempting the update). It worked fine the second attempt.
7) Reboot: the phone will reboot and you should check the status to make sure you are on the latest version.
8) Flash TWRP recovery: I read where people said full updates would lock your phone and you would have to start from scratch unlocking it (and therefore wiping all data). This was not the case for me and this update using this method. I was simply able to flash TWRP again. You should be a rock star at flashing recoveries by now so get to it and flash TWRP again. If your phone is locked, then read the note at the bottom of this post.
9) Reboot into system
10) Flash Magik zip: reboot into recovery and flash Magik zip to get SuperSU.
11) Install Magik modules: reboot into system. Reinstall any Magik modules you use as they don't get carried over from the previous installation.
12) Enjoy your updated phone
If for some reason the full update did lock the phone, then you will need to unlock it again before you can flash TWRP. You have already done this before, so use whatever method was successful for you. Obviously this will fully wipe your phone. After flashing TWRP and Magik, I would make a backup of that raw "stock" image just in case this next step doesn't work. After making the backup, you can try to restore just the data partition of the NANDroid backup you made in step 1 (click restore in TWRP, select the backup made in step 1 but deselect everything except the "data" partition before starting the restore process.) I have never done this, but I have read it will recover all your data (apps, etc) without affecting the system partition and therefore it won't mess up the upgrade. I would not recommend doing this if going from Marshmallow to Nugget or Nugget to Oreo however. In those cases, it is better to simple start fresh and redownload all of your apps.
Thank you for this thread.
Hello sic,
I am having the same issue with my Huawei GR-5 2017 and like you, I have my fair share of researching for weeks now and I was really happy to stumble on this thread.
Before I start with the process, I have a few questions for you. I hope you could help me (even though this thread is half a year ago).
Can you elaborate steps 1 and 2 or could you provide me a link on how to do those?
I got xposed installed im on emui 8 i also tried flashfire but it only turns the phone off.. Ist it eneugh to uninstall xposed? And can i get the recovery img from fullota? And must i restore images in magisk? I will try it without xposed installed. And a theory: is the information abaut bootloader unlock stored in a partition like oeminfo? If it is we could restore oeminfo.