I'm telling you guys something I've never seen before.
I bought a Realme 5 Pro (EU version it seems), and noticed that the installed ROM is quite old (November patched). So I tried looking for updates in the settings app, but there was none. Then I went to realme website:
https://www.realme.com/eu/support/software-update
And downloaded this ROM from that website:
https://download.c.realme.com/osupdate/RMX1971EX_11_OTA_0160_all_gOztiTWijElq.ozip
I went to the default file manager and clicked on it, and the update started right away, finishing after 2-3 minutes.
After the phone booted with the new ROM, everything was okay. The FM radio app went missing, but it was said in the changelog, so that didn't matter to me.
Then the most bizarre thing happened.
I went to the file manager and clicked on the ROM file once again, being damn sure that the update will not take place, because I've already installed this update. But the system accepted the update, rebooted to recovery, and started the whole charade one more time, including showing the percentage. It took exactly the same time as before.
I was half expecting something to go wrong, but to my relief everything was alright. After booting, the ROM version was the same as before (after updating the first time). Nothing changed.
I have never seen anything like this before. I have used phones from many manufacturers, but Everytime I try to update the system with the same ROM version as the one already installed, it would refuse the update, UNLIKE REALME.
Perfectly fine same on other oppo device
Try hard reset
After that,go to settings>update, and update it
Related
Alright, so here goes. I've searched the thread for the issue I'm having, but have come up empty handed. I'm not Droid noob, especially not when it comes to flashing roms. But, here are the details I have.
I had been following dragonzkiller's development on his ICS rom. I hadn't really put forth any effort looking lately until yesterday, and saw that he had the wifi and camera fixed, which were really my two biggest issues, so when I saw that, I was excited. I began working on getting it all running. I've had the x2 for about 5 months or so, and usually, the first thing I do, as soon as I get a new phone, is root it. Back in April, I rooted with GingerBreak. Worked good, no issues there. Back in June, apparently I still received the OTA update taking it to 2.3.5-418, which I found out last night had kinda broken my root. So, I went back to find a way to re-root. I did that, with a desktop .exe that went in, and was supposed to flash BSR to my phone also. After I ran that, all my root permissions started asking for options again, so I was relieved. Now, for the issues I'm having.
I downloaded an app in the play store called Online Nandroid Backup. For some reason, and I think this may be a dev issue with the app, it won't run a backup, and tells me that it wasn't able to be granted superuser permissions, even though it is prompting and I'm allowing. Issue number two is this. I've tried 3 different ways to get this working. I used ROM Toolbox Lite, selected the rom I wanted to flash, and wipe data and cache, no delvik. I've selected to run a backup of my current rom. When it boots into recovery, I only have 4 options. Reboot your phone, something about installing the rom from sdcard, wipe data, and wipe cache. I'm not given the backup option on the recovery. Furthermore, when I kinda just decided that since I hadn't had any trouble flashing a rom to any of my other phones I've had, I would just try to flash the rom, it gives me a prompt about 25% through the rom package saying E: signature could not be verified, or something to that extent.
Even though it has said not to use Rom Manager, I did download that and try that, and got pretty much the same outcome of no rom, just a bit different scenario going through. Rom Manager won't reboot into recovery, and when I select to do a backup, it reboots the phone straight up. I also used the manual entrance into recovery, volume up, but it tells me something about starting RSD protocol, and sticks at that forever.
My real questions are this... I've always ever used CWM. All of my previous phones have been supported by Rom Manager nicely, so when it came to downloading and flashing a rom on them, no problems at all. I have never used BSR, to my knowledge, so I'm not sure if the recovery screen I'm seeing is the actual BSR recovery, or if it's some other recovery. If it's not BSR, do I just flash it like I would a rom, then re-run into that? And does the signature issue that I'm running into mean that I have to wait for a signed version of the rom in order to work it? Is there any way to fix this issue, or am I basically SOL right this moment? Any information on how I can fix all of this would be greatly appreciated. Thank you.
Hi! I realise this if my first post I'd like to tread lightly; but I'm about 4 days into solving my issues and I just want to finish it...
I've had my Nexus i9020a (bought from Koodo) since ~May 2012. I upgraded to ICS sometime in the summer and sometime in the last few weeks it has started rebooting. I hadn't been installing new apps, etc. I'm not sure what the cause is. I 'Factory Reset' today in an attempt to resolve the issue, thinking it may be a program gone AWOL; but it has rebooted a few times since. I *just* looked through rebooting FAQ on this site and have edited the first few features listed there. I'm not sure if it has worked yet, but I'll get back to you on that. For the record, the only programs I have installed now are Swiftkey 3, Handcent and Beats (DDR simulator, updated in November).
In the meantime, before I found the solutions here, I decided to take another shot at unlocking the bootloader and try installing... probably CyanogenMod.
Specs: Windows 7 64 bit with Nexus S I9020a (Koodo) running 4.0.4 (4.1.1/2 OTA haven't come through, despite dozens of attempts at clearing the GSF cache, etc)
So I've been using the Nexus S: Full Update Guide found at:
hxxp://wiki.cyanogenmod.org/wiki/Nexus_S:_Full_Update_Guide
(It won't let me post the link)
I've followed the guide for installing the Android SDK, gone to CMD and typed 'adb devices' and had it show up. Theoretically, the SDK should be running fine.
Next, I turned on the USB debug mode. Then I booted up the bootloader, plugged the NS into the PC... and despite not having issue when the it's turned on (driver installed properly) windows says drivers have not been found for the device. Thus, when I type fastboot devices, it comes up with nothing.
I've been, and will continue perusing forums for this, but so far I haven't seen anyone with this specific problem.
Edit: I have also gone to the directory with fastboot/adb and used cmd to reboot into the bootloader, only to have windows 'ding ding ding' an unrecognised device.
2nd Edit.
I've gotten a stage further! I'll keep the thread open because I may come across something and it's nice to write my issues down. Seems my head can wrap around the problem a bit better. Anyway, I installed PDAnet and BAM, it works. Onto getting CWM installed! Thanks for the, uh, help!
3rd Edit.
CyanogenMod 10.0 stable is booting for the first time!! It's taking a while... but I appear to be on the home stretch! Also, my phone didn't reboot for a few hours before I installed CM. So if I don't end up somehow bricking it... and I mean, this first boot is taking a heck of a long time... The animation sets me at least a bit at ease... maybe 4.0.4 will work out...
Edit 4
I forgot to clear the app and cache data before flashing the ROM to the phone and thus the issue... after a VERY tension filled moment of pulling the battery during first boot... I rebooted, cleared said data and reflashed the ROM. After a boot, I realised I forgot the GAPPS zip and fixed that. Now I'm running CM10 Stable!! I'm stoked that after months of putting it off cuz last time I did it I didn't get anywhere after many days, but now it's done!! Thanks again for such an awesome site!
Thanks for sharing your experience instead of just saying "Mods please delete this i solved my own problem" :good:
Alright, this is a long story.
I own an LGMS500 from MetroPCS (or the LD500 Tmobile version).
A year back I rooted the phone, but a couple of months ago it started to act up Giving me the message "unfortunately, the process com.android.phone has stopped." at first a restart would fix it but a few days after it got to the point where I couldn't use it. So I set out to fix it.
I knew I needed to flash it back to stock ROM since a factory reset and a hard factory reset didn't do anything. But for some reason I decided that flashing a custom ROM was a better Idea. I ended up flashing the xperia ROM and it soft bricked it ( It turned on and booted but wouldn't let me past a black screen, yet I could lower the status bar).
Then I tried to flash the stock ROM or the "MS50010e_03.zip" to load with KDZ. from:
http://androidforums.com/threads/metropcs-unbrick-kdz-for-metropcs-updated-11-13-2013.788365/
But every time I tried it it came back with a parameter error, I changed many things with no avail, Then I figured that since the phone had a tmobile version I flashed the tmobile stock ROM onto the phone and it worked, even let me use data. But after a few days it stopped letting me use data, with a "Service Disabled message on the status bar where it should've shown the mobile carrier. When I went to check my phones mobile data status I noticed that My IMEI # was unknown.
After some research I came to the conclusion that something was wrong with my EFS folder since that's where all that information resides.
At the moment the phone restarts after about 3 minutes of usage, I should also mention that I rooted the phone after the tmobile stock ROM install because of what this thread suggested I should do.
http://forum.xda-developers.com/galaxy-s2/general/guide-recover-imei-9-steps-t1264021
Basically I need to know if my conclusions are correct and what kind of steps I should take to recover the phone if possible.
A
FIXED it
I just loaded the MS50012b_00.kdz from:
android creations on the weebly site (sorry I can't post links yet)
This is the only image that worked the first time. After that my phone worked normally, accessed the mobile network correctly and the crashing stopped.
I even installed the xperia ROM that is on that page. Everything is running smoothly now.
OK, when I got my S4, the first thing I did was to install clockworkmod, and then CM12.1 nightly. Everything was hunky dory until mid December. The nightly build came in, and I downloaded. I haven't been able to update live for a while, but from recovery it hasn't been a problem. Suddenly, clockworkmod tried, but got stuck at "detected ext4 filesystem" and there it stayed. I assumed just the nightly build, but nada since.
After consideration that clockwork was old, and maybe that was it, I've replaced my bootloader with twrp (latest version), and tried to make the update again. Lo and behold, it gets stuck at the same point.
Now, I'd quite like a ROM that supports viper4android, and matches 12.1, but it seems I can't install anything from recovery now. Suggestions?
For info, I always remove the SD card if I update or install a recovery, so that isn't the problem. Possibly one issue is that my volume down no longer works, meaning I have to boot, and then reboot to recovery, but since that works, I assume it's not the problem.
To be honest, if there's a fully working marshmallow rom out there, I'd even give that a go.
Ideas? My phone is working just fine (apart from the 07:28 crash every work day, stopping my alarm going off. Oddly, it doesn't crash at weekend when I don't want the alarm. I'm guessing a problem with the clock app, although the alarm is set for 6am)
Have you tried go back to stock with odin and then re-rooting? It could work.
Hi, I have this super-weird issue - my OOS got update to v12 and since then weird things happened:
It started to suddenly and immediately turn off and I couldnt do a thing. I did hard reset and noticed that turning on Gooogle Assistant (or using the mic at all) caused these resets. So I didnt activte Assistant. Unfortunnately, this caused my mic not to work at all.
So i have given up and decided to revert to previous rom - v11. Unfortunately, that is everything but simple:
I have downloaded ROM for EU from here oneplus site and tried both OP local update tool and this weird app named my application2. Both dont seem to work and im not sure why, I checked like 5 different ROM versions and I am kind of stuck. OP Local prompts me that I cannot install lower version of package than currently installed and this other app throws me pop up with this message: "Verification failed". I tried to google it and checked here on forum and I cant find similar thread.
Could anyone help me out with this?
I just went through this. I downgraded from 12L to 11. For some reason some of the roms do not want to be used by the local upgrade app. I used a different one from the one I will direct you to and it said that I couldn't downgrade. I just had to find the right one. Go here: https://forum.xda-developers.com/t/...a-oxygen-os-repo-of-oxygen-os-builds.3930585/
Under "signed flashable zips" in the op, click "click to show content". I don't know which one you need global/India or Europe. I specifically used the global/India OnePlus7ProOxygen_21.P.41_GLO_0410_2112101753.
Use the local upgrade tool app. Downgrading will completely wipe your phone. So, make backups of your backups. If you root your phone, make sure to freeze the System Update app to get rid of the annoying update notification. So happy to have root/twrp back.
Thanks, unfortunately I have rolled back to OOS 11 and it didnt solve a thing - i keep seeing this lightning symbol and phone turns off even on full battery, I cant make phone calls because any use of mic turns off the phone immediately and I have no clue what to do next with it.