I just got an OTA update and from VNS-L21C432B160 to B370 which was around 1.94GB but I wanted to make a clean install so I removed superSu from the app did a factory reset first then went back to update where it now showed something around 1.24GB. So I went through with the update everything seemed fine until I couldn't find the Dual-Sim manager. I went to About Phone section and noticed that my build number was NRD90M test-keys. How can I get a clean C432B370 from this point on?
Same thing hapened to me.
After update, strange build, but no BT functionality and no file explorer. Contacted Support, told to do Factory reset. Now gets interesting.
Factory reset failed after 6%, now im stuck with device with no keyboard?!? Basicaly, i can just recieve call's.
And to top it up, PC dont see device, cant upload anything on SD card to try 3 button update etc.
Before I have downgraded from N to MM because of camera problem, to do so, I had flashed Dual Sim OEM per instructions, I can think that that is causing some problems.
Targyen said:
Same thing hapened to me.
After update, strange build, but no BT functionality and no file explorer. Contacted Support, told to do Factory reset. Now gets interesting.
Factory reset failed after 6%, now im stuck with device with no keyboard?!? Basicaly, i can just recieve call's.
And to top it up, PC dont see device, cant upload anything on SD card to try 3 button update etc.
Before I have downgraded from N to MM because of camera problem, to do so, I had flashed Dual Sim OEM per instructions, I can think that that is causing some problems.
Click to expand...
Click to collapse
Same thing happens to me with factory reset, fails at 6% boots back like it performed a factory reset. I'm greeted with the first time welcome screen. No keyboard no file explorer no updater. I managed to dictate apkmirror on chrome and downloaded gboard and esfile manager. And I lost my SD card to perform a 3 button method. Can I do the 3 button without an sdcard? Maybe using the internal storage?
EDIT: Well I did the 3 button method and failed at verification. Anyone can help me how do I get out of this?
EDIT 2: Back to MM with this tut https://forum.xda-developers.com/huawei-p9lite/how-to/tutorial-rollback-n-to-mm-c432-devices-t3563955 and downloading B370 thorugh the official updater again
EDIT 3: Everything went smoothly and after, I even got B380 OTA.
EDIT 3.5: Did a factory reset after B380 and everything is working.
Related
Not sure if I'm the only one, and if I am that really sucks, but I got tired of waiting for the OTA and decided to install the update via the fastboot method, unlocked my bootloader installed without a problem.
However the issue now seems to stem from transferring media files to my tablet, which I never had a problem doing, a pop up window will tell me that android.media.storage has stopped, giving me an option to report and to simply tap okay.
Not sure reporting ever does anything, and if it does I've never seen it change a single thing at all, but after I tap okay or send the report, any files transferring will just exit out, then if I unplug my usb and plug it back in, it doesn't seem to recognize the tablet at all.
I've so far remedied this, not sure if it's a permanent fix or temporary, by going into settings>apps>all, then from there tapping the app, clearing data and cache, restarting my tablet with a hard reset and it seems to be working for the moment.
However transferring files since the update are sluggish at best, and taking a 356MB folder of images used to take maybe a few minutes, 5 or 7 at the most, now it's hanging there at times with the transfer time increasing.
As a matter of fact I'm transferring said 356MB folder right now and it's stuck at 10 minutes to finish and hasn't moved for about 10 minutes.
If anybody else is having these problems, can you suggest ways you've fixed it? Or do I simply need to either do a factory reset or straight up flash it again to fix the problem?
Also, I made another article detailing my problems with updating, which I've since fixed obviously, but Recovery Mode isn't anywhere to be found, I do the regular method and before it showed the android with the red triangle and below him it would say no command, now it just shows the android with the same triangle with no wording underneath at all.
I've also re-downloaded the official factory image 4.4 from google's developer site and tried to manually flash recovery onto it, and it says that it succeeded but then when it goes back to fastboot and I choose recovery it loads then shows me the android with the red triangle.
I've even tried downgrading back to 4.3 but it tells me during the rewrite of the bootloader that there's a signature mismatch.
In addition, this should be the last revision to my issue, I've even tried re-flashing 4.4 and now that's kicking back an error saying there's a signature mismatch, so I can't go into recovery, I can't downgrade, I can't flash a recovery image to my tablet, I think I screwed up in ever updating to 4.4.
Im having the same problem with Media Storage when transferring pictures via Android File Transfer on Mac, tried it on Windows also, same problem.
It happens with my Nexus 4 on KitKat also!!
I still havent found a way to fix it, did you (OP) ever find a fix?
Cheers
Stewart
StuMcBill said:
Im having the same problem with Media Storage when transferring pictures via Android File Transfer on Mac, tried it on Windows also, same problem.
It happens with my Nexus 4 on KitKat also!!
I still havent found a way to fix it, did you (OP) ever find a fix?
Cheers
Stewart
Click to expand...
Click to collapse
Nope no fix yet, I haven't tried transferring a large number of files since, oddly enough, I finally did get the OTA update and it installed 4.4 again.
It didn't take long and the file size was puny, only about 32MB, I assume it installed what was missing, but I haven't noticed anything out of the ordinary since the official updated kicked in.
Yeah I have the latest OTA also, but I am still having the same issue!!
StuMcBill said:
Yeah I have the latest OTA also, but I am still having the same issue!!
Click to expand...
Click to collapse
Not really sure why it's different for you, like I said I got tired of waiting for the OTA and manually flashed the factory image, that's when the problems started, but after a few days I got a notification that the new update was ready which really confused me.
But I installed the downloaded update without a hitch, booted like normal and I just finished transferring a 100MB folder of images to my N7 without an error popping up on my tablet saying something crashed, so I can only assume for the moment until I transfer a larger folder, that the DL'd update fixed the problem.
I've also heard people flashing it again, or side loading it, or even a factory reset would fix the problem, but there weren't many replies as to this actually fixing the data transfer problem.
Problem with downloading ota update kitkat 4.4
I have stock rom and waited for the ota update. It came this morning and while downloading twice the verification failed.i rebooted and the screen came up download failed and had a retry button which i tried to activate and does nothing, The screen has been stuck on the return download for over 12 hours. My wifi connection is strong. Any ideas?
manow91 said:
I have stock rom and waited for the ota update. It came this morning and while downloading twice the verification failed.i rebooted and the screen came up download failed and had a retry button which i tried to activate and does nothing, The screen has been stuck on the return download for over 12 hours. My wifi connection is strong. Any ideas?
Click to expand...
Click to collapse
Take anything I say with a grain of salt as I'm not the greatest guy to ask for help, I only really ask questions here and I'm just going to suggest what to do, if you do it is up to you and I take no responsibility for your device having further issues.
1. Hard reset your device and upon it rebooting, check for the update again and try downloading it again
2. If that doesn't work then back up your data
3. After backing up your data do a factory reset on your device and once you've booted back up to Android, check for the update again and install
4. If that doesn't work, I'm not sure what else to suggest, this is what I would do to try and fix the problem, but for my situation it was unique in that I tried fixing it various ways that seemed to make it worse before it got somehow better.
I hope issuing a factory reset works for you, if not then that hard reset does when you try to redownload the update.
JohnathanKatz said:
Take anything I say with a grain of salt as I'm not the greatest guy to ask for help, I only really ask questions here and I'm just going to suggest what to do, if you do it is up to you and I take no responsibility for your device having further issues.
1. Hard reset your device and upon it rebooting, check for the update again and try downloading it again
2. If that doesn't work then back up your data
3. After backing up your data do a factory reset on your device and once you've booted back up to Android, check for the update again and install
4. If that doesn't work, I'm not sure what else to suggest, this is what I would do to try and fix the problem, but for my situation it was unique in that I tried fixing it various ways that seemed to make it worse before it got somehow better.
I hope issuing a factory reset works for you, if not then that hard reset does when you try to redownload the update.
Click to expand...
Click to collapse
Thanks for your reply back. Yep i also thought of the same 4 step solution as yourself but i also heard from 2 people that had the same thing happen to them and they thought it could be a goggle server problem, So i am going to wait to see if it sorts itself out over the next few days
manow91 said:
Thanks for your reply back. Yep i also thought of the same 4 step solution as yourself but i also heard from 2 people that had the same thing happen to them and they thought it could be a goggle server problem, So i am going to wait to see if it sorts itself out over the next few days
Click to expand...
Click to collapse
That could be too, just thought I'd take a shot, hope it works out for you.:good:
For a week my G935A worked fine... direct out of the box I flashed ENG Kernel and Rooted, then installed apps and configured - no issues.
Today it was working then it hung on wake.. I tried to reboot and now it gets stuck at the AT&T logo and vibrates 3 times - over and over
I can get to Odin and Recovery screens easily so I tried to flash the ENG Kernel again & deleting Cache Partition few times - didnt fix it.
Also tried booting into Safe Mode - it never gets there, stays at AT&T logo.
When I go into the Recovery menu, I see at the bottom, in red... "dm-verity verification failed"
Anyone know how I can recover from this without Factory Reset? It took 6 hours to reinstall and config all my apps - really want to avoid that.
thx for the help!
as far as I know there is no way to fix and save your stuff. I had the same problem with G930A and even doing a factory reset would only allow my phone to boot but then I get apps crashing and then a reboot puts you back at ATT logo and the vibrates. Best to ditch the whole engboot and go back to stock until a more stable rooting method comes out.
Some searches shows posts that say using Odin to flash HOME_CSC without having to wipe and everything survive
... Where can I get HOME_CSC? I dl'd stock rom and dont see it in there.
thx!
Same here this morning on my 930A w/ PK1....went to watch a youtube vid and everything google related began crashing.
Only been on engboot for a couple days but did flash the v15 debloat last night. hmmmm.
Any luck with the files or procedure LivinOne?
Update: Flashed the PK1 CSC and got into recovery.
Wiped cache and reboot, same failure mode....sad face.
Flashed CSC again, into recovery, factory reset, wiped cache.
Back to setting my "new" device up.
Dec 30 update: Same crash, SEMI same problem.
I get the single vibration followed by the 3 vibrations after I put my pin in from a restart.
Same symptoms prior, all background activities began crashing.
Running all PK1 files from QRhinehardt post.
Any thoughts?
I ended up wiping and flashing the T-Mobile firmware and using the ENG bootloader (but not rooted yet). It is WAY faster than the AT&T was. I've only had issues with Wifi Calling (it doesnt seem to work most of the time)
s7 at&t
Hi, did you first flash with eng bootloader and then tmobile rom? I miss this step...I appreciate your help please
Single vibration followed by the 3 vibrations
Hi, were you able to fix the problem? I'm also getting the single vibration followed by the 3 vibrations.
Do you know why is this occurring? I performed a wipe cache and factory reset but still nothing.
bweegn said:
Same here this morning on my 930A w/ PK1....went to watch a youtube vid and everything google related began crashing.
Only been on engboot for a couple days but did flash the v15 debloat last night. hmmmm.
Any luck with the files or procedure LivinOne?
Update: Flashed the PK1 CSC and got into recovery.
Wiped cache and reboot, same failure mode....sad face.
Flashed CSC again, into recovery, factory reset, wiped cache.
Back to setting my "new" device up.
Dec 30 update: Same crash, SEMI same problem.
I get the single vibration followed by the 3 vibrations after I put my pin in from a restart.
Same symptoms prior, all background activities began crashing.
Running all PK1 files from QRhinehardt post.
Any thoughts?
Click to expand...
Click to collapse
In I should say desperate hope and waiting for official Nougat, and by carefully following this forum , I have found that we have new update, of course it is still MM, but I have decide to give it a try. So I downloaded it, unzipped it in dload folder on my SD card, and installed it. It all went like charm. But, When I have done factory reset. I have found that my poor P9lite become stuck in initial setup. For six damn hours I have struggled to revive my device. And, I have finally done it. Reflashed old B161, done factory reset, and my phone is now working.
So there goes my question: As far I know, the reason for stuck is that in B170 there is no android web-view.? Or I am wrong.
Now I will not flash any other official upgrade, unless it is proven correct and full.
It's working very well. I have not any problem (I flashed full version without wipe)
I have flashed B170, factory reset phone and it's working without hickups.
And android web view:
maka1105 said:
I have flashed B170, factory reset phone and it's working without hickups.
And android web view:
Click to expand...
Click to collapse
I did not say that it is not working, but I could not pass wifi setup. It has repeatedly bringing back to the wifi plus page. When I tap disable, it opens account screen just for second and then brings me back to wifi+ , same when tap on enable.
Similar hickups were mentioned in this forum, but for L31 and B161 firmware. But I did not had those hickups on my L21. Just to say, I have done factory reset on B161 today, just after I give up all hope, and B161 worked as it should. On the other case, B171 did not.
I am fully stock, unlocked. Updated recently to 7.1.1 B01. Now I tried to do OTA to B02 and if just entered recovery mode without doing anything. After reboot, it reported that system update did not match the phone. Wtf?
Perhaps it has to do with the unlocked bootloader.
I had the same problem,but at 1st,thought is was a TWRP and root problem.
So I did a factory reset and flashed the full official 7.1.1 B01,TWRP and root were gone after that,but still the same error when trying to install B02.
I gave up on it and went for NucleaRom,since the audio distortion is fixed now...
Sorry, bootloader is locked, my bad.
Sent from my ZTE A2017G using Tapatalk
I had this issue exactly as you described.
Ended performing a wipe+factory reset.
After that B02 installed without any issues.
Take your sd-card out.
++chris++ said:
Take your sd-card out.
Click to expand...
Click to collapse
There is none.
SD card was one of the typical causes for ending up in recovery mode + update not matching phone.
Basically most times people had an old ZIP in the root of the sd card.
I removed my old update ZIPs from phone and sd card and had no more problems anymore.
If you do not have a sd card, maybe you still have an old update zip in the basic folder of the phone.
It maybe worth checking. Most times it is just a kind of peanuts causing such problem. Just have to find out, where it's hiding
It worked today on 3rd attempt, I did absolutely nothing.
Sent from my ZTE A2017G using Tapatalk
So basically, few months ago i tried to root the phone, get new recovery and different rom. If I remember correctly I got stuck trying to get custom recovery to work, because everytime I restarted phone it would be replaced by the stock one. So I left the phone as it was, and disabled the TWRP app on it. Problem was, I could not update phone. Today I tried to completely revert to stock.
I flashed stock recovery but when I tried to install update from the phone storage, it did not even give me option to select a file.
I tried to update the recovery to newer one which gave me the option to select a file, but the installation got canceled after few seconds, putting me back on the file selection screen in recovery.
I tried to instal TWRP but I can't even boot into it at all because the phone is just stuck with blackscreen and lightblue led light.
I tried to ADB sideload the newest stock rom that I downloaded from OP5 site but this one went to around 50% and then crashed as well.
I also tried to do the update using the Settings>System update > Local Upgrade but this one also fails once it gets into recovery.
I tried wiping cache/reset system settings or wiping every data on the phone before any update but none of it seems to help and everytime I restart the phone afterwards the TWRP app is still there needing an update.
I tried to just lock the bootloader but I got the "Your device is corrupt. It can't be trusted and will not boot" message followed by link to google support. I assume that is because of the TWRP app that is on the phone but I can't get rid of it no matter what I try. I tried searching for people having simillar problems but I couldn't find anything that would help me.
Any suggestions?
Thanks in advance.
You can go with the last resort and use the Unbrick tool.
https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706