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
Related
Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.
zero313 said:
Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.
Click to expand...
Click to collapse
at least you are getting something OTA
Ditto
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...
seanfrisbey said:
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...
Click to expand...
Click to collapse
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?
Same thing here
When I bought this device 3 weeks ago, I rooted it with z4root. Not too long after an update disabled z4root on the tablet.
I thought no big deal, but then today comes and I the OTA update won't work.
Anyone more experienced than me have any ideas of how to get this update applied properly?
Me too. Update failed to install. Not sure why. I have also tried unrooting.
FloatingFatMan said:
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?
Click to expand...
Click to collapse
I'm confused, if I froze an application, didn't unfreeze it but did a factory reset...wouldn't that resolve the issue?
ok so i woke up this morning and my a500 notified me the there was an update available so as you can imagine I was very happy to finally have this, so i updated and when it was done it said update successuful but when I checked it still said 3.01......WTF
Not rooted ever..
Those interested in getting back their OTA, properly backing up their original ROMS or restoring them, please follow the tutorials in this thread:
Going back to stock TUTORIAL
Be helpful and provide your firmware if you have a backup so we can build a database for those who don't.
Be sure to report what is working and what is not working for you once you've tried the tutorials!
Unlike the 14 threads on these matter I take the responsibility as OP to upgrade my original post as firmwares and new info becomes available.
Let's create a focused troubleshooting and tutorial thread,
Thanks.
I'm rooted via gingerbreak and the update worked fine while still rooted. It did break root. Just had to re-apply gingerbreak and all is good, back to root with latest update.
gingerbreak worked with official 3.1 ?
it didn't work with 'leaked' 3.1 ?
OTA
Ok after long night and hours of research i found out a lot.
1 if you have modded ad hoc in wpa_supplicant file recover the original file
2 if you have modded the phone.apk and telephoneyprovider.apk to save battery this is the reason why you won't get the update.
i put these files back and instantly got an update, i mean the exact second i set those back
i can't believe this my updates keep failing to install. FING POS i tried everything, factory reset
i have tried everything, even factory reset, it fails while installing after reboot
acer support are a bunch of retards, they don't even know they sell tablets????????
need help i can't upgrade, it fails every time
does anyone know where the install logs are
the log is \cache\recovery\last-log
Oklahoma City, OK noon CST
First attempt failed:
Changed the wpa_supplicant back to original and all went smooth the second time
I never changed anything and it failed.
**Edit: I rebooted my devices and left it completely alone after unzip and it rebooted into recovery mode and seems to be installing **
I had the same problem, It was pretty disheartening.... but I unrooted my device, re-booted and tried again and SUCCESS!!!
But now I can't get it to re-root using gingerbreak... HELP!
SUCCESS!
Ok. I got OTA update 4.010.08 (122.71 MB) this morning. It failed.
So I unrooted my device. Re-started it and tried again... SUCCESS!
I tried using Gingerbreak to root it again. FAIL!
So I used this: http://forum.xda-developers.com/showthread.php?t=1138228
SUCCESS!
Hope this helps those of you who are having problems.
No need to unroot nor go to stock.
I had the same issues. Then I simply used Acer Recovery to install stock recovery and everything worked fine.
Ceger
Acer Recovery?
Did Acer Recovery come with the tablet?
I tried the update numerous times over the last 4 days. Most of the time the download would fail, which I put down to my slow internet connection and overloaded Acer servers. But about 5 times it would finish downloading and then error out on install with a message about the update being invalid. I tried rebooting several times during this process. I have never rooted the tablet and only have a few apps installed as it was a recent purchase.
Finally it worked when I ejected the external SD card and rebooted. It may be a coincidence, but anyone else who gets the "invalid update" warning during install on an unrooted device may wish to try this prior to the download/install.
Just bought a new S4 GT-I9505, for some reason it just randomly reboots! It did it 5 times in 10 hours. I tried resetting it to factory in case the apps I had installed were causing it. I don't think they were because as soon as it switched on again after being reset it rebooted after about 5 minutes.
Any ideas?
Could it just be firmware related and I have to wait for an update? Or is it hardware?
Sent from my GT-I9505 using Tapatalk 2
Do you have a microSD card in the device? If so, what kind?
Are your SIM-card properly placed into the device?
It's a 8gb San disk ultra micro sd and I have just removed and inserted it and my sim. Both are fitted correctly.
Anyone?
I'm assuming you are running stock (not rooted etc). Are you using the latest firmware? Have you checked for a system update?
proctologist said:
I'm assuming you are running stock (not rooted etc). Are you using the latest firmware? Have you checked for a system update?
Click to expand...
Click to collapse
Stock, yes. I actually restored through kies so am fully up to date. Checked for an ota to be on the safe side though and nothing.
It has only rebooted once since 9am this morning so it's improved on yesterday!
I had the exact same problem with my s3.
New or of box it rebooted randomly and always when
i stayed the programs first time.
I returned it and got a new. That is what i recommend.
Same thing happens to me.
ParaLanche said:
Same thing happens to me.
Click to expand...
Click to collapse
Are you sending yours back?
if it stays on download mode try to flash a fresh stock firmware for i9505.. you can it from samfirmware.com.. it could help if it is due to a software issue,, otherwise its going to be a hardware issue..
did you try "wipe cache partition"?? sometimes it fixes some problem if it does not return, that s what i did with my reboot problem while playing video.
I'm having the same problem I cleaned cache several times and installed the cmw recovery again. Any ideas?
Thanks
Rooted devices
Have a read HERE - Maybe of some use for those with rooted devices :fingers-crossed:
I'm currently running the latest PureNexus (MM) with a pretty vanilla setup, I.e. no xposed, root, etc. All the sudden yesterday I had a hard crash while doing nothing in particular, a sudden reboot that sent me into a boot loop. It reboots right before the boot animation would appear. The only way I was able to fix it was to wipe the data partition. I was subsequently able to restore my backup and it booted successfully. The frustrating part is it's happened several times since then. In fact I can't keep it running more than a few hours without the same thing happening, even after doing a full wipe. Any ideas?
Thanks!
Arg, I tried flashing the new Android N system image (the official one) which basically flashes every partition and I'm still getting a boot loop. Is it possible that my SD card went bad?
ts_mpls said:
Arg, I tried flashing the new Android N system image (the official one) which basically flashes every partition and I'm still getting a boot loop. Is it possible that my SD card went bad?
Click to expand...
Click to collapse
Did you use flash-all.bat from google image or you flashed the images one by one?
I tried both. Both N and MM. Apparently I stumped Google too, they're sending me a new one.
that's weird... Glad you got a replacement though!
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.
Ever since I got this phone, There has always been this error "SIM card not detected" and it's extremely annoying to deal with as you have to restart the phone every time until it works (It took me 8 restarts to fix it today)
It's definitely not a hardware issue as my phone is brand new and so is my brother's phone (Tried both slots as well) and the sim card isn't even a year old
I've seen some people with the same issue. How in the world can this be fixed? I really don't want to return the phone as I like it very much
I'm rooted right now with stock rom but this has also occurred the first day (Totally stock)
This is happening to me as well and it's infuriating to say the least. I don't recall seeing the issue stock, it only seems to happen once I load magisk but I haven't fully tested that.
The issue is also usually preceeded by a reboot that gets stuck in the android one screen, meaning that I have to reboot the phone 3 times before it actually works. VERY annoying.
I think I'll re-flash the phone using the script that keeps my data and will run it stock for a few days to see if there's any difference.
Same here. I didn't experience a similar issue on 16.4 but there are other issues there. Hopefully when stable comes out, it'll work correctly.
I ran the phone re-flashed to stock yesterday and didn't run into the issue. The flashing process re-locks the bootloader so I think it's either:
1- Some issue with having an unlocked bootloader
2- Magisk 16.0 bug
3- Magisk 16.0 bug while bootloader is unlocked (I don't know if magisk can be installed but the bootloader re-locked after installing)
I had exactly the same issue on an Asus Zenfone 2. I was wondering if it was a sim card problem.
hacktek said:
I ran the phone re-flashed to stock yesterday and didn't run into the issue. The flashing process re-locks the bootloader so I think it's either:
1- Some issue with having an unlocked bootloader
2- Magisk 16.0 bug
3- Magisk 16.0 bug while bootloader is unlocked (I don't know if magisk can be installed but the bootloader re-locked after installing)
Click to expand...
Click to collapse
I did find the cause and how to fix it
The cause is the stock rom itself, It has issues regarding baseband but it doesn't happen to everyone and I don't know why
The only fix that I've found is to flash a custom rom.
I've been using aex rom for 2 weeks now and I haven't got a single issue so far