Hey there,
My friend downloaded and installed Color OS6 update. His phone got bricked. He has tried all the things but couldn't solve the issue yet. It's been more than a week. Can you please link me to any solutions.
Also, the official update to fix the issue, i.e., http://download.c.realme.com/osupdate/RMX1801EX_11_OTA_0210_all_YkJueYPOAFXQ.ozip isn't installing and displaying "Installation Failed" after waiting forever. Service Centre guys are saying that they will do it, but data will have to be wiped.
In order to fix the bootloop, data needs to be reformatted via the stock recovery, then only flash the latest OTA. Should work(at least for me).
Related
To my delight, I got the OTA update or whatever it is, the official thingie to update to 4.4, icon and all.
I start it up, it goes through the motions, then it gives me a nondescript error (( The little Android looked like how it did when it's awaiting a bootloader instruction. ))
Does this mean my Android stock is borked? Do I need to factory wipe? I am confused. I did, however, download the Google-based Nexus 2012 KitKat build and I attempted to ADB it, and it gave me yet another error, with this - E:Error in /tmp/update.zip.
Any help that can be given would be wonderful.
I have the same issue. I wiped the cache and done a factory reset but it didn't fix the issue. I downloaded Nexus root toolkit as it has a unbrick feature and ran that but it seems to have made it worse, I can no longer get into recovery.
Hey guys,
My wifes Tab 4 recently did the OTA update to Lollipop (5.0.1) and has been having a problem ever since. After being in use for a few minutes after the update it suddenly locked up and rebooted itself. Thought nothing of it at first, but then it did it again, and now randomly reboots all the time, sometimes after only a minute of use. I've tried clearing the cache partition and factory reset, neither gave any improvement. Then i figured maybe the OTA download was the probblem so i flashed it back to Kitkat using Odin and all worked fine again for a few days. I turned off the OTA update checke and she was perfectly happy with it again.......
......until it downloaded the update all over again.
Before allowing it to update again i connected it to the PC and did the update via Kies instead. All seemed to be fine for about 5 minutes and then started rebooting. Again, cleared cache and factory reset. Again no improvement.
Then tried flashing the update via Odin again. Still no improvement.
I'm drawing a blank on this one. I've tried everything I can think of and still not been able to solve this one. The only thing i've been able to figure out so far is that for whatever reason it doesn'T randomly reboot if its connected to the PC via USB...............
Anyone got any ideas how to sort this?? Samsung have offered to take it in for repair and I'Ve been offered a refund from the retailer, but I'd rather avoid those options if possible.
Thanks!
I have the same problem and nobody Knows. I will back to kitkat. let me know if you fixed. sorry for my english im cuban.
Good morning,
I'm stuck with a big problem on my Note 3 HLTE.
Here's the story : I was previously on the PAC Rom 5.1 and I wanted to change to get the CM13.0 that was just released. So I've performed the full wipe (dalvik, cache and factory reset) and then when I wanted to update the OS, it didn't work. I ended up with a phone in recovery, telling me that there was no OS installed on it.
after several attempts, I then tried to revert back to a stock ROM based on 4.4.2 with Odin. The installation went on without any problems, I was able to get through the first install with my Gmail account and then the phone rebooted, and that's where I got the bootloop curse.
what I did then, was to redo an install via Odin with my carrier stock rom, and I got a FAIL message. So, I retried an install with Odin by adding a PIT file and another ROM still based on 4.4.2. the install worked, as I was able to set up my Gmail account and so on. At this stage, I wasn't able able to get any signal for calls, 4G . In parameters, the baseband was identified as "Unknown". Then, the phone rebooted again, and I got the bootloop curse again...
My last attempt has been to install my carrier stock ROM after performing a full wipe, with ODIN. The install was successful and I got the phone rebooted to stuck on bootloop.
So, here's where I am, and I would like to solve this problem, please. What I think is that, due to the fact that I was on Lollipop, the bootloop might be due to the downgrade attempt to KK. So if there's any way to solve this problem, I'm eager to take it.
Thank you !
Hey Guys,
I've been able to resolve my bootloop problem.
I've installed TWRP with Odin, made a full wipe including data (I've saved them before), and I installed the CM12.1 by Temasek, and way to go, the phone is running fine ^^
Now, I'm just stuck with the lost IMEI thing and baseband. SO my question now is : if I want to install my operator stock ROM for getting back, should I just choose the Lollipop ROM, or can I take the KK one without getting stuck in bootloop again ?
Thank you !
I originally had OOS3.0.2, and I tried to get Beanstalk rom installed. Beanstalk didn't load correctly, and I softbricked my phone. I managed to go through the recovery of downloading the qualcomm drivers and that weird updating program and then sideload an older version of OOS (2.2). I went to this link and did method 1 https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/. But when I get things fixed up, I can't seem to update to CM13, or even to do a normal update with root, without root, with twrp, without twrp. Nothing. Strangely enough, no matter what I've been doing, the data I had from the very original pre-screw-up time is still all there. Every time I try an update it hangs on the 1+ screen and stays there. How can I get past this? I can't seem to upgrade, and I'm stuck in lollipop.
Well I was still able to get into my phone and do a stock recovery from the Update and Restore option from the phones settings menu, so that fixed it.
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