You want to update your device, you have the OTA zipfile, but you don't know how to use it, you don't want to bricked your device!
That's why I've wrote this guide. I'm not the writer, just an adaptor for xda member
By downloading, flashing these files and use this guide you agree to the following:
Your warranty is now void.
We are NOT responsible for bricked devices, 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 use it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, I will laugh at you with all of my teeth.
Support is limited. I do this as a hobby in our free time. I'll do my best to help you if you state your problem in clear English, with as much information as you can (what mods you selected, have you wiped, when exactly does the error occur, what type of phone you have, what carrier, logcat and so on. The more information you offer, easier for me to help you. If you do not ask for support in clear English and with no information what-so-ever we will ignore your issue
Click to expand...
Click to collapse
Before to flash or use fastboot lines command, you need to read quietly this guide. Download all files in one folder (it's easier to find all files in the same folder).
Prerequisite: Your Nexus 7 LTE should be running Android 4.4.2 (KOT49H) or (KVT49L -for Verizon). You will not lose your data using this method
Step 1.
Download the update zip
=> Download link for almost of users => cac1a204d3770a20fdce28f6ed3418fdd36abd5d.signed-razorg-KTU84L-from-KOT49H.cac1a204.zip - md5: 34adc31c6647de18547c405133072381
=> Download link for Verizon users => f0c2187ff1dba772cff3fa7f99f0e6bd38ecb62b.signed-razorg-KTU84L-from-KVT49L.f0c2187f.zip - md5: 663b29478d60babb2f0cbb6fc506f111
Charge your Nexus 7 to at least 60% battery level
Don't forget to enable USB debugging
Don't forget - Backup your tab’s storage,
you can choose to change the file’s name to ‘update.zip’. take care
Be sure to read the instructions and carry on...
Step 2.
Reboot your Nexus 7 LTE and hold the Vol+Down button while it's booting up.
Once you see the fastboot menu and the word Start, press Vol+Up a few times until you see Recovery and then press the Power button to enter recovery
You will see an Android with a red exclamation point.if you have stock recovery
Now press Vol+Up+Power together, and you should see the menu below:
Select the 2nd option called apply update from adb.
Step 3.
Connect your Nexus 7 LTE to your computer with your USB cable.
Make sure you have a recent version of adb that supports the sideload command (if you don't, download the latest Android SDK to ensure your adb is up-to-date).
Place the update.zip package from Google in the Android SDK/platform-tools folder on your computer, but do not unzip it. And open up a command prompt
(cmd in Windows)
(regular shell in Linux and Mac) in the same directory as the zip file.
and type
Code:
adb sideload <the name of the zip file that you've done>.zip
if you have changed the name of the update file to ‘update.zip’, then enter: adb sideload update.zip
You should see the progress bar go up to 100%, like so:
sending: 'sideload' 100%
Click to expand...
Click to collapse
At this point, the device should have started installing the update 4.4.3 OTA :victory:
Step 4.
Reboot - you're done.
Enjoy Android 4.4.3 on your Nexus 7 LTE... we just need to waiting the next release for KK4.4.4
Just in case
Reserved for me
Is this zip compatible with TWRP? I tried flashing the zip but it failed, and I did verify the md5 checksum was correct.
Hizpanick said:
Is this zip compatible with TWRP? I tried flashing the zip but it failed, and I did verify the md5 checksum was correct.
Click to expand...
Click to collapse
I've tried before to install my OTA update and the install is failed. I'm with TWRP also
That's why I'll edit my OP without this process. I have rename the zip file to update.zip
For info I have this result:
Code:
- verifying current system
"/system/bin/debuggerd" has unexpected contents
E:Error executing updater binary in zip '/sdcard/update.zip
Error flashing sip '/sdcard/update.zip
Updating partition details
So if you haven't received the OTA update for 4.4.3, use the adb sideload process.
So I tired with the adb sideload process, and still get the same failure:
"/system/bin/app_process" has unexpected contents.
E: Error executing updater binary in zip "/data/media" (looks like it cuts off at this point)
Since I have TWRP, I used adb sideload by going to Advanced ->Adb sodeload and then swiping to turn on adb sideload. My ADB version is 1.0.31, and the file did copy succesfully.
EDIT: Maybe this doesn't work for me because I'm stock rooted?
Hizpanick said:
So I tired with the adb sideload process, and still get the same failure:
"/system/bin/app_process" has unexpected contents.
E: Error executing updater binary in zip "/data/media" (looks like it cuts off at this point)
Since I have TWRP, I used adb sideload by going to Advanced ->Adb sodeload and then swiping to turn on adb sideload. My ADB version is 1.0.31, and the file did copy succesfully.
EDIT: Maybe this doesn't work for me because I'm stock rooted?
Click to expand...
Click to collapse
I haven't been able to get this to install either. Does root or custom recovery cause the installation to fail?
Sent from my Nexus 7 using Tapatalk
i am getting a status 7 error in /tmp/update.zip
help?
I don't know exactly what is the problem. I've used this process for updating my N7.
After the flash with adb sideload, I am back completely stock, unlocked, rooted but stock recovery, not twrp.
Sent from my N7 LTE from XDA Assist and use TapatalkPro
So I found out why I was getting my particular error and it was because I had Xposed framework installed. I uninstalled that and was able to flash the OTA. However, I lost root, but kept TWRP. So I flashed the updated SuperSU.zip (http://www.androidfilehost.com/?fid=23501681358555830) and I had root back. Re-installed Xposed Framework and now everything is updated and working
So you got the update to flash in twrp?
I uninstalled xposed and it still doesn't work with stock recovery and kernel. Got too much setup to redo it all
Sent from my SCH-I605 using Tapatalk
worked for me.
Related
Hi,
After changing my phone's date into the future, my G2 Touch told me there was an update available, so I told it to go ahead and apply it. When the phone rebooted it came up with this message:
E:No signature (218 files)
E:Verification failed
Installation aborted
I have nandroid installed on the phone. At least I think that's what's installed - I haven't played with any ROM stuff since November I think, when I changed the bootloader (I think - if that's what's giving me the option to do a nandroid backup now) and installed the newest T-Mobile G2 ROM.
Should the phone be able to install the OTA update, or will I have to replace the bootloader in order to get the OTA update on there? If I do have to replace the bootloader, will that require a full wipe?
James
Completely the same problem with HTC Hero after European OTA update. It has been rooted while ago (by following instructions from this forum) and now after setting up date in the future and confirming update, phone reboot and I get "Android System recovery" screen with menu and this message bellow it:
Build: CyaanogenMod v1.4 + JF
Finding update package ...
Opening update package ...
Veryfing update package ...
E: No signature (218 files)
E: Verification failed
Installation aborted.
Click to expand...
Click to collapse
I have the same problem (I did not write down the message, so I'm not sure which "Build:" was listed) .
The update fails, the phone reboots and then works under the old build. Under "settings/about phone" there is also no info about the update. Can one force the phone to download the update a second time? Would this help?
Bye
Nick
P.S. I'm running the phone in Germany over e-plus as network provider. The updates was done over a WiFi connection. The phone is not branded - was from the free market and not from a provider.
Hey,
got the same problem. At least I could extract the official OTA-update-zip to publish it here (see attachment)
There also is a "recovery.img" in the update zip, so I guess usually the OTA update will kill custom recovery bootloaders. We could replace the "recovery.img" in the zip with a hacked one before applying the update.
However first we should fix the verification error...
P.S.: Also Germany, not branded, Vodafone Network
Does anyone know if I will lose all my data if I reflash the original recovery.img onto my phone?
As I used flashrec to flash ra-recovery.img I keept all my data. So I don't belive you will lost any of your data except of your actual recovery image.
At last, we can try to flash origianl RUU, but with this we lost all our personal data.
----
I tried it. I installed flasrec.apk using ASTRO and used this app to flash the recovery.img from here mentioned/linked OTA update zip. Afterwards I changed date again and was able to install OTA Update without errors and loosing personal data. Now I'm without nandroid because of changing recovery image. Keep cool at this procedure installing these flashes takes long time in boot process - I was really near an hard reset ...
Flashing the original recovery.img should not be a problem.
However, I don't want to lose root access, and thus I will wait for the official HTC 2.1-update (hoping someone publishes it online) and then flash it by myself..
I don't mind losing root access at this moment (the reason I rooted my phone was to get wifi tethering but never got it working with a mac).
Since I am total noob with android stuff, I would highly appreciate some step by step instructions or link where I can find what to do. Thanks guys.
Hi, I've been trying to install the recovery.img from the update but I get this message with flashrec 1.1.3:
Code:
"Flash FAILED: Could not run command."
I'm using WWE 405.66 flashed with ra-recovery img 1.6.2... and the rom is rooted.
What am I doing wrong?
I can't even install ra-recovery with flashrec now and I have installed ra-recovery 1.6.2 this morning (I was using 1.5)
And yes, I know I'm going to lose ra-recovery.
rseffner said:
As I used flashrec to flash ra-recovery.img I keept all my data. So I don't belive you will lost any of your data except of your actual recovery image.
At last, we can try to flash origianl RUU, but with this we lost all our personal data.
----
I tried it. I installed flasrec.apk using ASTRO and used this app to flash the recovery.img from here mentioned/linked OTA update zip. Afterwards I changed date again and was able to install OTA Update without errors and loosing personal data. Now I'm without nandroid because of changing recovery image. Keep cool at this procedure installing these flashes takes long time in boot process - I was really near an hard reset ...
Click to expand...
Click to collapse
What was the rom you were using when you flashed the official recovery?
alvaritolalala said:
Hi, I've been trying to install the recovery.img from the update but I get this message with flashrec 1.1.3:
Code:
"Flash FAILED: Could not run command."
I'm using WWE 405.66 flashed with ra-recovery img 1.6.2... and the rom is rooted.
What am I doing wrong?
I can't even install ra-recovery with flashrec now and I have installed ra-recovery 1.6.2 this morning (I was using 1.5)
And yes, I know I'm going to lose ra-recovery.
Click to expand...
Click to collapse
Try the following:
- Copy the recovery.img to your SD card
- Turn off the phone, turn it on with Buttons "HOME"+"ONOFF" pressed such that the ra-recovery which you already have starts
- connect to your phone by cable using "adb shell"
- Then with root access you can flash the image by typing "flash_image recovery /sdcard/recovery.img"
This should do it
jamesots said:
Hi,
After changing my phone's date into the future, my G2 Touch told me there was an update available, so I told it to go ahead and apply it. When the phone rebooted it came up with this message:
E:No signature (218 files)
E:Verification failed
Installation aborted
I have nandroid installed on the phone. At least I think that's what's installed - I haven't played with any ROM stuff since November I think, when I changed the bootloader (I think - if that's what's giving me the option to do a nandroid backup now) and installed the newest T-Mobile G2 ROM.
Should the phone be able to install the OTA update, or will I have to replace the bootloader in order to get the OTA update on there? If I do have to replace the bootloader, will that require a full wipe?
James
Click to expand...
Click to collapse
hey,
I had same problem
go to All programs--> Recovery Flasher--> Restore backup
then restart and update OTA
Greetings from Zagreb, Croatia
Hey guys.
So, for those of you, who do NOT care about root for now, here's what worked for me:
1.: Download the zip-file with the OTA Update, mentioned on the first page and extract it.
2.: Connect your Hero to your PC and copy the recovery.img from the OTA onto your sdcard. Disconnect from computer.
3.: Boot your phone into the bootloader (Home + PWR).
EDIT: Now connect the phone to the pc again!
4.: open the command prompt of your pc, navigate to your Android SDK folder. (If it is not installed, download it and make sure you've got the needed drivers. Otherwise: Download them, using the Setup.exe from Android SDK)
5.: Here are the needed commands:
Code:
adb shell
$su
mount -a
flash_image recovery /sdcard/recovery.img
6.: reboot your phone after exitting the command prompt.
7.: Factory reset, reboot again
8.: And well, wait for the update-window again and be happy, now it should work
EDIT 2:
Any questions? Just leave a reply
@Revoluzifer
OK I did exactly as you explained, but having problem with su command:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
I know I know, you're going to say my phone is not rooted at all But believe me it was and some apps that require root access are there (screenshot, wifi tether etc.).
I even tried to find su cmd with find:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
But got nothing as you can see.
Ideas?
@dinke:
Which bootloader / recovery console is installed?
Means, what do you see, after booting with Home + PWR?
Also try to input $su instead of just su.
But first tell me your "hack" if any
@Revoluzifer
Thanks for quick reply
I see Android system recovery screen, not sure if this is nandroid or what but have this text on the screen with following options:
Android system recovery <2>
Use trackball to highlight;
click to select.
[Home+Back] reboot system now
[Alt+S] apply sdcard:update.zip
[Alt+W] wipe data/factory reset
[Alt+B] nandroid v2.2 backup
[Alt+R] restore latest backup
[Alt+F] repair ext filesystems
-------------------------------
Click to expand...
Click to collapse
And bellow menu there is build ID:
Build: CyanogenMod v1.4 + JF
I don't remember exact procedure that I applied for rooting hero, but I followed instructions from this forum (I can try by searching for exact thread if that may help you).
Edit: I applied root procedure by following instructions on these two links:
http://forum.xda-developers.com/showpost.php?p=4257045
http://forum.xda-developers.com/showthread.php?t=559613
That sounds just perfect
CyanogenMod 1.4 is exactly the same recovery console i have had before.
(Btw, Hero is not officially supported by CM anymore, had a nice discussion yesterday in cyanogen IRC )
So, try to use $su instead of su, that's what I typed and it all worked just great.
But you definitely first booted into bootload and then connected the phone to your pc again?
Tell me if this worked for you, please...
Greetz,
Sven
dinke said:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
Click to expand...
Click to collapse
Forget about the "su". You are already root.
(You can see this, as there's a '#' in front)
Just do the mounting and flashing
Oh... You're right, nerdture... didn't see the #
I *think* I've tried mount no matter of missing 'su' cmd and it didn't work either but will try again as soon as I manage to find some cable to connect hero with macbook (no longer nearby windows machine but have sdk installed on mac so should be working as well)
Revoluzifer said:
But you definitely first booted into bootload and then connected the phone to your pc again?
Click to expand...
Click to collapse
Yes
Hi!
Yesterday night, I was on the lookout for emoji font for my phone. To no avail finding colored emoji icons, I ended up going to Font Changer (Root) but found nothing there either. Since I just discovered the app, I thought, why not just try something new? A new font? So I downloaded a font, made a backup of my old font and rebooted the phone. But then it was done. My phone didn't start anymore and was stuck on booting. I went over to Modaco forums, downloaded a custom recovery and then downloaded one of the many dedoxed roms there. I tried to flash it, but in avail.
-- Install /data/media
Finding update package...
Opening update package...
Verifying update package...
Installation aborted.
So I downloaded another ROM to try. Same error. I tried to download the stock firmware from ASUS. Same error. What is causing this?
Keep in mind, I have done a data/factory reset wipe! The phone was obviously rooted before the incident! I did not have a custom recovery before the incident! I have tried 4 different ROMs! I am currently on Modaco's custom recovery!
ROMs tried -
* Deodexed TW ROM (Padfone 2)
* Deodexed WWE ROM (Padfone 2)
* [Pre MCR WWE ROM (Padfone 2)
* PadFone2 Firmware: V10.4.11.13 Only for JP SKU (Android 4.1) (STOCK)
Current recovery -
* Modaco R1 Custom Recovery
try restoring with the phone plugged in to a power source.
it worked for me when i got the same message trying to update.
Uzrbital said:
Hi!
Yesterday night, I was on the lookout for emoji font for my phone. To no avail finding colored emoji icons, I ended up going to Font Changer (Root) but found nothing there either. Since I just discovered the app, I thought, why not just try something new? A new font? So I downloaded a font, made a backup of my old font and rebooted the phone. But then it was done. My phone didn't start anymore and was stuck on booting. I went over to Modaco forums, downloaded a custom recovery and then downloaded one of the many dedoxed roms there. I tried to flash it, but in avail.
-- Install /data/media
Finding update package...
Opening update package...
Verifying update package...
Installation aborted.
So I downloaded another ROM to try. Same error. I tried to download the stock firmware from ASUS. Same error. What is causing this?
Keep in mind, I have done a data/factory reset wipe! The phone was obviously rooted before the incident! I did not have a custom recovery before the incident! I have tried 4 different ROMs! I am currently on Modaco's custom recovery!
ROMs tried -
* Deodexed TW ROM (Padfone 2)
* Deodexed WWE ROM (Padfone 2)
* [Pre MCR WWE ROM (Padfone 2)
* PadFone2 Firmware: V10.4.11.13 Only for JP SKU (Android 4.1) (STOCK)
Current recovery -
* Modaco R1 Custom Recovery
Click to expand...
Click to collapse
Try some other recoveries
Lky CWM or TWRP
Sent from my A116 using Tapatalk 2
Same happened to me, but I got it up and running again!
Earlier today I bricked my Padfone 2 too by installing 3rd part font. After a reboot to apply the changes, it got to the boot logo but never any further.
I got it up and running again, :victory: and to those out there in same or similar situation, here's a tutorial on what I did:
Before we start, there's a few things you need;
1.1 Latest ADB version (I used 1.0.31)
1.2 Latest Fastboot version
1.3 CWM Recovery
1.4 Latest ASUS USB Drivers (available from ASUS Support site)
1.5 Padfone 2 Firmware (available from ASUS Support site)
*** NOTE: For ease of use, place extract and place all of the above to the same folder.
*** NOTE: Inside the Padfone 2 Firmware ZIP file, there's another ZIP file. This is the one we need! The one I used was called "WWE_A68-10.4.15.1-0-ota-user.zip"
*** NOTE: This method does not install CWM Recovery on your phone, it only boots it temporarily.
If you have all of the above, continue to step 2;
2.1 Booting your Padfone 2 into Fastboot mode
2.2 Press and hold Power + Volume up buttons
In Fastboot mode, connect your phone to your computer and launch cmd. Wait for windows to install necessary drivers if needed.
3.1 Navigate your CMD to the folder containing ADB, Fastboot and CWM Recovery (recovery.img)
3.2 In CMD type:
Code:
fastboot boot recovery.img
In the CWM Recovery on your phone, select the option titled "Install ZIP from sideload".
Use the volume keys to navigate and select by pressing the power button.
4.1 In CMD, transfer the Padfone 2 Firmware by typing
Code:
adb sideload [firmware-file-name.zip]
- Example from my case, I wrote:
Code:
adb sideload WWE_A68-10.4.15.1-0-ota-user.zip
4.2 When it is done, you'll be presented with CWM Recovery's screen again, select "Reboot system now".
4.3 CWM Recovery will present you with a warning saying: "ROM may flash stock recovery on boot. Fix?" - Select "NO".
[EDIT]
In some, if not all cases, Windows will try to install new drivers, but fail. If windows installed the drivers correctly, skip this step.
To solve this, go to device manager by entering the Start menu, right-click Computer and select “Manage”. Select the Device Manager.
You should see a failed device named A68. Right-click it and select “Update device software”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “Have Disk”
Now browse and navigate to the folder you extracted your ASUS USB Drivers to and select the file named “android_winusb.inf”
Select “ASUS Android ADB Interface” and install.
Added files and a neat pdf tutorial.
[/EDIT]
All done! You should have a working Padfone 2 again!
Please note that you may need to root your phone again.
Please credit if used
/HelmerN
brickeddd
hey i just tried all these methods and while trying to boot recovery.img with CMD nothing else happens but CMD says <waiting for device>. My SD card is empty and i have no ROMs on international storage so i can't install. I am using TWRP custom recovery. I have no idea what to do anymore. Please help!
zimbou said:
hey i just tried all these methods and while trying to boot recovery.img with CMD nothing else happens but CMD says <waiting for device>. My SD card is empty and i have no ROMs on international storage so i can't install. I am using TWRP custom recovery. I have no idea what to do anymore. Please help!
Click to expand...
Click to collapse
listen : about your problem which is <waiting for device> just unplug the usb cable from your phone and plug it again but you have to do very fast so i want you to pull the usb a little bit and connect it again but do it fast after that the cmd its gonna recognize your phone %100 try it ,,,,,
What's going on I had my watch rooted tried, make it back to stock tried it, rooted it and once more tried it I get error 7 everytime
I'm using Ubuntu 14
I can't even sideload
Drivers are all working
But for some reason my Linux machine won't talk to my watch
Can someone help all I need is some codec
I'm sure this has been answered before (infact, I remember answering this exact question).. The stock recovery has ADB broken, so sideloading doesn't work, nor does ADB's shell. The reason you're getting error 7 is because you re-rooted, which changes app_process32, which the update is looking to patch and finds that it doesn't have what it expected there. That said, here's something you can do.
Follow the instructions found somewhere else on these to push the update to /cache/recovery with the watch rooted, I'm not sure if the stock recovery image has an apply /sdcard/update.zip option, but you may be able to get away with pushing the update there.
If you're using the /sdcard/update.zip option, make sure that the update is pushed. If your watch is rooted, you need to unroot it manually by using the image found in the Restore Tools image. (If you're on 5.1 I believe it's 49Ksystem.img but I can't remember.), you'll be doing fastboot flash system <system-image>, then reboot into recovery and hit the apply update.zip option. You're done.
If stock recovery does NOT have an apply update.zip option, you need to search on the G Watch forum here, there is a proceedure that involves pushing the ZIP to /cache/ and writing a recovery script into /cache/recovery. You will need to stage that, but instead of rebooting when the instructions tell you, you need to reboot to the bootloader (adb reboot-bootloader) and preform the step I stated above, reflashing your current version's system image. Once finished, simply reboot and the OS will start updating automatically.
NOW! The Easy Way!
Download the latest LG G Watch Restore Tool package (I think it's 9.8 now), it has been updated with the latest Android Wear image. So all you need to do is start it and run Return to Stock, your watch will be restored to 5.1.1
I was rooting my sons Kindle Fire HD 7 4th Gen on rom 4.5.3
I installed TWRP but wiped the system not thinking. Now all I get is an error message saying:
This package is for "full_ariel" products; this is a "omni_ariel".
E:Error excuting updater binary in zip '/sdcard/update-kindle-20.4.5.3_user_453011120.zip'
Error flashing zip '/sdcard/update-kindle-20.4.5.3_user_453011120.zip'
All I get is white amazon logo when normal boot and TWRP recovery and I have ADB access.
I need a rom that will flash that'll get be back up and running. I even tried some custom ones but get same error.
Is there a way to push stock rom to a folder and reboot and it'll install? If so, what do i rename file and where do i put it?
n2outlaw said:
I was rooting my sons Kindle Fire HD 7 4th Gen on rom 4.5.3
I installed TWRP but wiped the system not thinking. Now all I get is an error message saying:
This package is for "full_ariel" products; this is a "omni_ariel".
E:Error excuting updater binary in zip '/sdcard/update-kindle-20.4.5.3_user_453011120.zip'
Error flashing zip '/sdcard/update-kindle-20.4.5.3_user_453011120.zip'
All I get is white amazon logo when normal boot and TWRP recovery and I have ADB access.
I need a rom that will flash that'll get be back up and running. I even tried some custom ones but get same error.
Is there a way to push stock rom to a folder and reboot and it'll install? If so, what do i rename file and where do i put it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=62349128
n2outlaw said:
Now all I get is an error message saying:
This package is for "full_ariel" products; this is a "omni_ariel".
E:Error excuting updater binary in zip '/sdcard/update-kindle-20.4.5.3_user_453011120.zip'
Error flashing zip '/sdcard/update-kindle-20.4.5.3_user_453011120.zip'
All I get is white amazon logo when normal boot and TWRP recovery and I have ADB access.
I need a rom that will flash that'll get be back up and running. I even tried some custom ones but get same error.
Is there a way to push stock rom to a folder and reboot and it'll install? If so, what do i rename file and where do i put it?
Click to expand...
Click to collapse
I'd try using TWRPs advanced/adb sideload to sideload the 4.5.3 update bin. (Leave it named as bin.) Keep wifi off. If it works, follow one of the root guides from the point of blocking ota updates in 4.5.3, rooting and reinstalling TWRP. If it doesn't work you will have lost TWRP as well as system, so may want to see if someone posts a surefire solution. (If you use windows, you'll have to install or update the adb driver once you enter TWRP's sideload mode.) Good luck!
DoLooper said:
I'd try using TWRPs advanced/adb sideload to sideload the 4.5.3 update bin. (Leave it named as bin.) Keep wifi off. If it works, follow one of the root guides from the point of blocking ota updates in 4.5.3, rooting and reinstalling TWRP. If it doesn't work you will have lost TWRP as well as system, so may want to see if someone posts a surefire solution. (If you use windows, you'll have to install or update the adb driver once you enter TWRP's sideload mode.) Good luck!
Click to expand...
Click to collapse
I did try that and from USB and the same thing.
sd_shadow said:
http://forum.xda-developers.com/showthread.php?p=62349128
Click to expand...
Click to collapse
Thanks!! I used a link inside of the one you gave.
Return to Stock
Code:
* I'm 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 the products you find here 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.
* Your warranty could be void if you tamper with any part of your device / software.
* Same statement for XDA.
YOU WILL NEED A PC FOR THIS
First,
Make sure your bootloader is already unlocked before proceeding. The bootloader unlock method can be found here: https://forum.xda-developers.com/nokia-3-2/how-to/how-to-unlock-bootloader-disassembling-t4096623
Even if your bootloader is already unlocked, I would recommend to still go to the link I provided above.
Procedure:
1. Download Magisk and Magisk Manager from here.
2. Download boot images specific for your current Android version from this thread: https://forum.xda-developers.com/t/ota-dump-nokia-3-2-boot-images-00ww.4109621/
3. Connect you Nokia 3.2 to your PC. Make sure you have enabled USB debugging and have the Automatic system updates disabled in the Developer Settings!
(You will be needing ADB and Fastboot tools to run commands like in the following steps.)
4. Type this in Terminal available for your PC (e.g. PowerShell, Terminal for macOS/Linux, etc.)(I do not recommend CommandPrompt as you cannot drag&drop files into it.) :
Code:
adb install <drag the Magisk Manager apk here>
or you can manually type the location of the Magisk Manager apk file instead of dragging it into the Terminal.
NOTE: you shouldn't include both "<" and ">" symbols before/after dragging a file onto a chosen Terminal app!
5. Type:
Code:
adb reboot bootloader
your Nokia 3.2 will reboot into fastboot/bootloader after typing this command.
6. Now that your Nokia 3.2 is on fastboot mode, type:
Code:
fastboot boot <drag here the downloaded patched_boot.img>
7. Your device will boot temporarily with Magisk installed and with root privileges. In this way, your root is not yet permanent. Follow the next steps to make your root permanent.
8. After booting, go to the Magisk Manager app, click on Install button beside the "Magisk is up to date". Then, click on Install again. Now click on the "Direct Install (Recommended)" button.
9. Wait for the download process, after that Magisk Manager will flash Magisk. (making your root permanent)
10. After the installation process, click the Reboot button.
11. Reboot done! Now Magisk is completely installed into your device!
Other Tips:
1. Enable MagiskHide in the Magisk Manager Settings in order to pass SafetyNet.
2. JUST INSTALL MODULES, DO NOT INSTALL ANY ROOT APPS UNLESS YOU KNOW WHAT YOU ARE DOING!!
3. MAKE SURE THE MODULE YOU'LL INSTALL IS COMPATIBLE FOR NOKIA 3.2!
In order to know if the Module you'll install is compatible for Nokia 3.2. Make sure the module is listed as compatible with:
* Stock/Vanilla/AOSP (This is because Nokia 3.2 is an Android One phone, meaning it runs in Pure Android. Pure Android are also called Stock/Vanilla/AOSP.)
* Android 10
Click to expand...
Click to collapse
That's pretty much it! Just comment if you would like to ask more questions! Have a nice day everyone!
Credits to @topjohnwu - the creator of Magisk!
How to do OTA updates on Nokia 3.2 with Magisk.
This is how you can install OTA updates without losing Magisk root:
Just follow the steps here:
https://topjohnwu.github.io/Magisk/ota.html
If that doesn't work, try reflashing the stock image from fastboot with:
Code:
fastboot flash boot boot.img
then
Code:
fastboot reboot
after the boot process, boot your phone into fastboot/bootloader again then type:
Code:
fastboot boot patched_boot.img
once boot completed, Install the OTA update from Setting. (DO NOT CLICK ON RESTART NOW)
then go to the Magisk Manager app again. Install Magisk again, but this time Install to Inactive Slot.
Reboot!
Done!
And if installation problem persists, just download this file and run either the .bat file or the .sh file.
Note: This file consists of Nokia 3.2 fastboot ROM images of Android 9, October 2019 update. This means that if you’re on Android 10 this will downgrade your Nokia 3.2!
UPDATE: I’ll be posting a better method without downgrading your Nokia 3.2 soon!
Terminologies:
flash-all - flashes every partition aside from vendor, system, boot, dtbo, and aboot. (Recommended for those who are facing bootloop issues, and/or ROM issues.)
flash-user - flashes vendor, system, boot, dtbo, and aboot partition only. (Recommended for those are only facing installation problems when doing system updates.)
.sh - a shell script file that is made for macOS and/or (probably) Linux. BUT MAKE SURE YOU HAVE INSTALLED android-platform-tools PACKAGE FIRST
.bat - a Windows Batch file. (You know what it means.)
All went good till step 7 but in step 8 when i click on instal button it says no connection as wifi is off but also wifi unable to on. i keep on pressing the wifi button but it again switches to off. Also when i restart phone, the root is uninstalled, kindly help
ch.ebaad said:
All went good till step 7 but in step 8 when i click on instal button it says no connection as wifi is off but also wifi unable to on. i keep on pressing the wifi button but it again switches to off. Also when i restart phone, the root is uninstalled, kindly help
Click to expand...
Click to collapse
Hello, in that case try doing it again but right after Step 6, when your phone boots up, unlock your phone and then don't touch it for a while so it can boot up properly, if done properly you can notice the Wi-Fi on and you must also able to open apps. Also make sure you're using the correct patched_boot.img!