Hi, so I run OxygenOS 3.1.3 and with the stock recovery but with SuperSU installed, but I wanted to update it to 3.1.4. So I downloaded the ROM from the official downloads.oneplus.net and chose the ROM and downloaded. But for some reason I thought that I had flashed the older 2.2.2 ROM which I had in my internal storage, so I flashed the other ROM (which was actually the 2.2.2 ROM). Then I realised that the first time I had flashed the ROM was the correct one and I the second time I had flashed the lollipop rom. Then I went to the recovery, and flashed the 3.1.4 ROM. After flashing the ROM, when I started booted up the device, I had all the apps, but it was as if all the data of each and every app was wiped. Like I had to set up each and every app back. Why did this happen? Is it because I accidently flashed the lollipop ROM on the marshmallow ROM? Or is it because of the 3.1.4 ROM? I am just curious to know the issue here. Thanks in advance
Related
So I have recently downloaded the Renovate 4.1 rom and tried to update with full wipe since update feature seemed broken. Now when phone rebooted after flash it sticks at HTC Quietly Brilliant boot screen. Logs from full wipe install showed no errors. Do I have to download the new stock kernel before i update? If so, will it be a problem if I flash new kernel now that the 4.1 rom is installed?
EDIT: Problem was fixed by flashing new kernel.
so ive been out of the loop for a while (2-3 years) but decided to updated my old omega v34, boeflla kernel jellybean s3 to the one in my sig (essentially blisspop+boeflla 4 alpha 13+gapps lollipop).
i updated my boot manager to twrp as suggested. rebooted. i did a format data, folowed by delvik cache and cache wipe, then a system wipe. i then installed the rom and gapps, then rebooted. i was still on the old kernel at this point.
as i rebooted i experienced some hanging, and then after taking off the battery and rebooting and finishing the setup process, i rebooted and installed the latest lollipop boeffla kernel. i still got some hanging so i full wiped again and repeated the process of installing the rom/gapps. my modem as remained the same and i have not updated it since last i did 2012.
as of now, i am still experiencing some freezes, but not as frequent as before and some slowdown. is there something that i messed up or forgot to do in the installation? any help is greatly appreciated.
@rab1412000412:
1. TWRP is a recocery, not a bootloader.
2. Maybe, you should update your firmware 1st. What modem is installed?
ddlj1 from 2012. i changed my gapps and its much more stable now.
@rab1412000: then you had old 4.1-firmware and can be happy, that LP-ROM didn't refresh your modem. I recommend to go back to your old firmware. Make sure, that IMEI and net access are ok. Then update via KIES, OTA or Odin to newest 4.3. Backup this version and flash any ROM you want.
I was using the Blekota Note 4(based on Kitkat) on my i9300 when it one day suddenly it restarted on its own and went into a bootloop and heated up. So I took out the battery and tried starting it again by clearing cache and dalvik cache. But it was still stuck at bootloop. After about 3 hours, somehow it came back on its own, but all the data and settings were lost. The downloaded apps were present, but their settings were lost.
Since I would have to again set up all apps, I wanted to try a new rom, Lollipop based. I downloaded the latest RESURRECTION REMIX (5.5.7) apps and downloaded the OpenGapps micro package. But after trying a clean install, the boot loop problem was still there. I tried with a different Gapp package, from OmniRom thread (all were for Android 5.1) but still no help. Even flashing the ROM alone would be of no help. I remembered I had a similar problem after flashing Boeffla kernel and the solution in that case was flashing a new version of the kernal. I tried that also. But no help.
I changed my recovery from CWM to TWRP as someone in some thread mentioned that it could help. But still No avail. In doing a clean rom, I tried almost 3 roms, cleaned cache, system, dalvik cache and even the internal storage and tried all other combinations. BUT THE SAME BOOT LOOP PROBLEM REMAINED.
As a last resort I had to flash the original 4.3 JellyBean firmware hoping that performing a clean install from that would help. But even after that the boot loop remains. Someone please help me flash a Lollipop based rom. This thing is driving me crazy now.
There's still 1 basic procedure: flash a 3part firmware with PIT-file for repartition.
Pit files should only be considered as a last resort.
Clear data and reflash stock rom and repeat once more. I have had cases where the rom didnt fully clear on a normal single flash.
Dont let it boot to rom. Do the two data wipes from recovery only.
I wish I stole my HTC M9.
Hi!
I recently installed lineageOS 14 over stock 6.0, since everyone praised it. However, it randomly rebooted in my pocket during the day hourly, so I decided to go back to stock.
But it neither boots with stock based rom, nor on a freshly installed stock with flashtool. It stucks at the bootanimation for hours, and doesn't reboot like it does in similar situations.
What the hell is that, could anyone help me?
(Btw my Z1C has the same problem)
I also installed Lineage OS, but after having a problems with keyboard i revert to stock with flash tool ver 0.9.18.6. I accidentally installed 5.1.1 uk version then after reboot i download new 6.0.1 ver and installed it over. Phone is working ok, no reboots. Maybe you should try to install again stock rom or change the flash tool version
Wipe APPS_LOG and USERDATA is mandatory when rolling back to previous Android versions, maybe you have missed that part?
iXaidyiu said:
Wipe APPS_LOG and USERDATA is mandatory when rolling back to previous Android versions, maybe you have missed that part?
Click to expand...
Click to collapse
Last time I think it did work without wiping userdata, so I didn't check those to wipe, however, to make sure I did a factory reset before from recovery. But I guess apps_log is not erased with a factory reset?
Anyway, thank you very much, I will try again this way.
Ps. It might be the cause that it still didn't boot when I tried a different rom with flashtool.
Update: Thank you, that did the trick, successfully booted!
Hej everyone,
I flashed a custom rom from mi-globe a few months. It was working great. Then I had the not so incredible idea of updating with latest miui eu 12, because the weekly update from the update menu was not working. It kinda worked, but it got too buggy. So I wanted to come back to a xiaomiEU Stable Rom.
It is now that problems begin. When I flashed miui eu 12, I got recovery loop. Lost all my data trying to fix, but I was able to flash the stock rom via the amazing XiaomiADBFastbootTools in my GNU/Linux distro. It worked! But the main issue is can not flash the custom rom again. I download the custom rom in the internal storage, flash the twrp via fastboot, enter recovery, create full backup, wipe to factory reset and flash the custom rom. Everything seems successful, but then I get a recovery loop again and when I try to restore the backup, the data folder is filled with folders and files with random chars in the names. Apparently the data folder becomes read-only for some reason as well. Then I have to flash the stock rom and tried everything again. I have done it at least 5 times now. I have searched a lot for some solution and nothing works
I have tried the OrangeFox recovery and the mi-globe rom, same issue. I really want a custom rom :fingers-crossed:, but I have no idea what to do anymore. If I could at least restore my backed up stock rom, it would help a lot.
Please help me out and sorry I posted in the wrong section.