Hi everyone,
Got my 6P a few days ago. First thing I did was unlock the bootloader, flash the MTC20F image and get on with my day. Now I didn't flash the userdata file because well.. I just didn't.
Anyway, with every reboot now, I get the message about your device software can not be checked for corruption and it says to re lock my bootloader. Phone works fine though. I've left the BL unlocked.
Decided to venture into the world of Android N, enrolled my device into the beta program. OTA notification came. I hit restart and install. After 'Processing the update package', it rebooted into recovery and showed the green android guy with 'error' written underneath him.
Recovery log showed:
E: Failed to Map file
installation aborted
So I rebooted and I'm still in MM (obviously), and nothing happened except a huge waste of my time. This didn't happen on my Nexus 6 when I enrolled for Android N DP1 and it received and installed the OTA with an unlocked bootloader.
So what's up with this? Any ideas?
Is there a way I can get my hands on the NPD90G OTA and sideload through stock recovery without losing my data?
All replies will be appreciated.
Sent from my Nexus 6P
I have not tried yet but I would use Nexus Root Toolkit. Choose flash stock / unroot. In the workflow underneath where you choose the factory image there is a check box in Setttings for "No Wipe Mode". I would read up a bit and see if this grenades the install from 6 -> 7 but it is a good place to start.
Related
Hello
I am using a nexus 4 and today the kitkat update showed up on was downloaded and their was a notification... I clicked that and it took me to the screen which says that you will update to four point four etc etc.. I clicked reboot and install then it rebooted and said updating system then suddenly it showed me an error there was an Android lying down with a red triangle above it I shut down the phone and rebooted then the phone started up and everything was normal there was no update but my phone works on four point three..
. I use a rooted phone could this be Beal cause of root help
I yes that notification doesn't appear now
If you have a root phone and made changes to the /system partition then the OTA update can fail. You can manually download the OTA package here, read the instruction in the same thread on how to sideload. http://forum.xda-developers.com/showthread.php?t=2145848
Just remember that on rooted phones, there is a possibilty the update fail and you won't be able to boot and require flashing factory image to restore it and losing all your data in the process.
eksasol said:
If you have a root phone and made changes to the /system partition then the OTA update can fail. You can manually download the OTA package here, read the instruction in the same thread on how to sideload. http://forum.xda-developers.com/showthread.php?t=2145848
Just remember that on rooted phones, there is a possibilty the update fail and you won't be able to boot and require flashing factory image to restore it and losing all your data in the process.
Click to expand...
Click to collapse
But I did not tamper with system files so I don't think there is a possibility of that.....
The update notification is not sowing up I went to about phone and clicked system updates but now it shows your phone is up to date
I have a 910C at v.5.1.1. I received a 100MB system update a few days ago. The update seems to have been successful as everything works while phone is booted to OS. However I cannot get into TWRP when I try to boot into recovery.
I've also tried to flash TWRP using the unified toolkit and odin. I have the professional ver of toolkit which enables it to work with 5.1.1. Anyway it always boots into stock recovery and the ODIN flash won't take. When I boot to recovery it comes to the android thingy saying installing updates and then fails after a minute of so with message, "no command found." I think this is what is breaking everything. I've cleared everything and done a factory reset but still see the same behavior.
Does anyone know how I can fix this?
Thank you,
@_metafizik
Hi, did you able to fix your issue? I am facing same issue.
Quick question:
I am very used to flashing so this isn't new to me. I recently updated to android build MHC19I. I'm use to the "lock your bootloader" warning, but now that I'm on TWRP 3.0.0-1, I'm also receiving the "your device is corrupt" warning. Now this doesn't seem to affect day to day use, so I don't seem to care, but am I doing something wrong? I usually wouldn't receive that message.
Thanks!
dbroer91884 said:
Quick question:
I am very used to flashing so this isn't new to me. I recently updated to android build MHC19I. I'm use to the "lock your bootloader" warning, but now that I'm on TWRP 3.0.0-1, I'm also receiving the "your device is corrupt" warning. Now this doesn't seem to affect day to day use, so I don't seem to care, but am I doing something wrong? I usually wouldn't receive that message.
Thanks!
Click to expand...
Click to collapse
Have you flashed SuperSU since flashing this version of TWRP? I haven't been able to pinpoint the cause of this message, but I believe it occurs when you have a modified /system partition (from installing TWRP). If I recall correctly (I had it a while ago) flashing SuperSU seemed to get rid of it. Could be a coincidence but that was my experience.
Heisenberg said:
Have you flashed SuperSU since flashing this version of TWRP? I haven't been able to pinpoint the cause of this message, but I believe it occurs when you have a modified /system partition (from installing TWRP). If I recall correctly (I had it a while ago) flashing SuperSU seemed to get rid of it. Could be a coincidence but that was my experience.
Click to expand...
Click to collapse
Here is the crazy thing.
So I hadn't flashed anything but TWRP, didn't modify the system partition at all, and that message would come up. I then flashed the latest Pure Nexus (actually then removed Root) and the message is now back to just the relock the bootloader message. I checked what build was used in that rom, and it is some crazy build (MHC19J) which isn't even available on the the Android Factory Images site. So I don't really know. As of now though, I'm just back to the normal lock your bootloader message.
dbroer91884 said:
Here is the crazy thing.
So I hadn't flashed anything but TWRP, didn't modify the system partition at all, and that message would come up. I then flashed the latest Pure Nexus (actually then removed Root) and the message is now back to just the relock the bootloader message. I checked what build was used in that rom, and it is some crazy build (MHC19J) which isn't even available on the the Android Factory Images site. So I don't really know. As of now though, I'm just back to the normal lock your bootloader message.
Click to expand...
Click to collapse
TWRP itself modifies the system partition in order to persist through reboots, I believe this is what causes the message to appear.
I think the Warnung is only red then the vendor image with the cert.check goes wrong the mhc19j is the last march build from the nexus5x and the devs changed the Rom for the angler- so try to flash the vendor image Märchen from Angler the mhc19i and the Rom certificate check goes right and the yellow Warnung is back.....i had for a few days the same Problem.... Download the vendor in the Rom thread and flsh it with wugs toolkit and then reboot.... Sry for my terrible english
Enrolled in the beta program and allowed it to download and install the 1.1gb Nougat file.
After reboot, still shows 6.0.1.
Any ideas on what happened, or more importantly, what to do to get to 7.0?
Thanks!
You 100% stock?
xxBrun0xx said:
You 100% stock?
Click to expand...
Click to collapse
Yep, no root, no recovery, nothing.
I'm having same problem
after I got OTA and update to 7.0 Still It showing 6.0 so I opt out beta program and soon as I got downgrade to 6.0 message I opt-in again
and I download OTA and install one more time.
now I got bootloop. device is completely stock. no unlock oem or usb debug or root. so when I'm trying to flash factory image.
it keep showing " FAILED (remote: device is locked. Cannot erase)"
so I can't fastboot flash or adb
I don't know what to do.
OK, I ended up downloading and sideloading it. Shows 7.0 now.
I had that problem too. previously using stock MM, no rooted etc. after downloading the N by joining the developer program, it downloaded but after reboot still showed 6.0.1 but with August security update. it also said that i have the latest software version.
a couple hours later, software update notification popped up again and after re-download it shows the 7.0
wililye said:
I'm having same problem
after I got OTA and update to 7.0 Still It showing 6.0 so I opt out beta program and soon as I got downgrade to 6.0 message I opt-in again
and I download OTA and install one more time.
now I got bootloop. device is completely stock. no unlock oem or usb debug or root. so when I'm trying to flash factory image.
it keep showing " FAILED (remote: device is locked. Cannot erase)"
so I can't fastboot flash or adb
I don't know what to do.
Click to expand...
Click to collapse
That's identical to my situation. Will see what Google say when I ring them.
I had a Media Pad M3 with unlocked bootloader, rooted and TWRP as recovery. As I wanted to update my ROM to BTV-DL09C100B311 I had some problems in TWRP an thought updating step by step would be a good idea. So I downloaded all missing ROMs throught FrimwareFinder and startet with BTV-DL09C100B307_fullOTA.
The installation in TWRP with ADP sideload worked and when I restartet my device a was a bit suprised that the yellow "Bootloader is unlocked - your device is unsecure" message was missing. I restarted again and the message is still missing. I thought OK perhaps I can now install all updates through the EMUI build in process without FirmwareFinder or TWRP.
EMUI downloaded the update and asked me to restart and install. After the restart the install process went to 20% and told me then there was a verification error. When I restarted the tablet again I got a screen similar to the yellow "Bootloader is unlocked - your device is unsecure". The screen is red an told me "Your device has failed verification an may not work properly".
Now I'm stuck. No updates work and TWRP could not be started or installed again.
I tried reinstall TWRP with fasboot (https://forum.xda-developers.com/mediapad-m3/development/twrp-greatslon-mod-t3489232) but I get the error FAILED (remote: "command not allowed"). I tried the newest TWRP mod from https://androidfilehost.com/?w=files&flid=125388 but same error.
Phone and FRP are still unlocked, as shown in FASTBOOT&RESCUE MODE so this is not the cause of the above mentioned fastboot error.
I installed the Android SDK completly and downloaded the newest toolkit (https://developer.android.com/studio/releases/platform-tools) but still get the above error. So I dont think its a driver problem either.
I did not try to unlock the bootloader again. I don't think this makes sense even if I still have the original codes.
I would like to get TWRP back and update the tablet to the newest ROM version. And it would also be nice to know what happened here
Thanks in advance for everyone helping me back on track. I think the first step should be get over the FAILED (remote: "command not allowed") error and install TWRP again.
I got it
Needed to unlock the bootloader again. Even so it throws an error the red starting screen disappeared an I got the usual yellow one back and i could install TWRP.
//Edit
Managed to get to newest Version with this updater: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
sebbo2015 said:
I got it
Needed to unlock the bootloader again. Even so it throws an error the red starting screen disappeared an I got the usual yellow one back and i could install TWRP.
//Edit
Managed to get to newest Version with this updater: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Click to expand...
Click to collapse
I am also looking for a way to update my rooted M3 (WiFi edition) to the latest available version with security patch line of November.
Now I wonder whether with this updater in your post above this works immediately or if I also have to go through all the difficulties you faced?
Is it possible to install updates with a rooted device with this updater or do you always need to unlock the bootloader again?
Thanks for your help!
Just tried it out now and it worked! Data is still there, homescreen icons are a little bit messed up and root is gone (no problem).
This is great because I was looking now for a long time to find a way to update a rooted M3 with new OTA updats (all the usual way fails).
I used to do it with going back to stock and a factory reset being involved.
Funny that you presented me the solution with your problem.
Glad that you shared it.
Now the only thing I am missing is to install the Xposed Framework on the M3. If you know how to do this let me know (I am using Super SU).
Borkse said:
Funny that you presented me the solution with your problem.
Glad that you shared it.
Now the only thing I am missing is to install the Xposed Framework on the M3. If you know how to do this let me know (I am using Super SU).
Click to expand...
Click to collapse
Im happy I could help. I dont use Xposed.
Hi, can you, please, describe this in steps? What I have to do before standard OTA update should work? And when (and how) to open bootloader once more? Thank you very much.
Standard ota updates will not work. If you already have an unlocked bootloader you have to use this method https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279 to manual update your M3 to the newest version.
If you have no unlocked bootloader please check this first https://forum.xda-developers.com/mediapad-m3/development/twrp-greatslon-mod-t3489232