I was trying to install havoc os on my moto g5 plus, i rooted with magisk and unlocked the bootloader, and when i tried to flash the havoc rom it gave me error 255, i upgraded the twrp and when i rebooted to install the rom it gave me error 7
Then i tried to keep my stock rom and it just wont load, it tells me the password is correct when it loads but the data is corrupted and need to factory reset, but when i do that it just loads twrp
when i connect the phone to my pc it shows that the sd is normal but the internal storage only has the twrp folder which makes me believe i currently have no OS
please help me
You must be flashed wrong Ver of Havoc, Happened with me
Try to flash any other Custom Rom
Try some 32 bit android 7.1 ROM.. I suggest Resurrection Remix 5. I got error because twrp was not 64 bit.
mercvv said:
I was trying to install havoc os on my moto g5 plus, i rooted with magisk and unlocked the bootloader, and when i tried to flash the havoc rom it gave me error 255, i upgraded the twrp and when i rebooted to install the rom it gave me error 7
Then i tried to keep my stock rom and it just wont load, it tells me the password is correct when it loads but the data is corrupted and need to factory reset, but when i do that it just loads twrp
when i connect the phone to my pc it shows that the sd is normal but the internal storage only has the twrp folder which makes me believe i currently have no OS
please help me
Click to expand...
Click to collapse
First thing first Back up ur persist and efs....
Now download pixel experience Rom and clean flash it.
Related
Hi,
So I have created this thread just because I can see many people creating new threads as after flashing CM 14.1, their phone doesn't boot up. So for all those who are going to flash CM 14.1 or have already flashed it and can't get it working, this thread is for you.
What you will need:
1. Rooted OnePlus X (Obviously)
2. Custom Recovery (TWRP recommended)
3. Latest CM 14.1 build
4. Arsenic Kernel or BlackReactor Kernel
So this is how you get CM 14.1 working on your OPX (make sure your battery is above 80% just to be sure that nothing will go wrong considering battery's point of view)
Make sure you have backed up everything before performing the following steps as the process will wipe your data completely. (I would recommend to take a Titanium backup of all user apps and then taking a nandroid backup of system and data)
1. Download the required files and place them in your SD Card or internal storage
2. Reboot your device into recovery
3. Go to wipe, and swipe to factory reset (Note! This will completely wipe all the data from your device including app data and SMS! This won't wipe the contacts but just to be safe, have a backup of all your contacts)
4. Go to Wipe again, and go to Advanced wipe, select the following partitions - System, Cache, Dalvik cache. Swipe to wipe (Note! Make sure you have a backup of the System as this will wipe the Operating System from your phone!) Although this step isn't necessary, I like to do it.
5. Go to install, and direct to the location where you have saved the CM 14.1 zip file and the kernel. Select the files, and swipe to flash.
6. If you want anything else in your system, direct to that location, select the zip file, and swipe to flash. (Note! You need not flash the SuperSU zip file as CM offers Root access in developer options)
7. Reboot your system and wait for it to boot.
Viola! Your device is now running official CM 14.1 nightly.
Hope this helps! ?
Downloads:
1. Latest CyanogenMod nightly - found here https://download.cyanogenmod.org/?device=onyx
You can have any version of the nightly as long as it is CM 14.1
2. Arsenic Kernel R32 (or R31) - http://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Open the above thread and follow the guide
OR
Black Reactor kernel v1.0 - http://forum.xda-developers.com/oneplus-x/development/kernel-blackreactor-kernel-oneplus-x-t3460989
-Reserved-
Good Evening, @aamodjoshi23 THX a Lot. You are my Hero. Finally it works.
greetings
If you're facing some Error 7 while trying to flash cm 14.1, you can try updating the bootloader following this
http://forum.xda-developers.com/showpost.php?p=69267239&postcount=2560
I used the Oxygen OS 3.13 full ROM as recommended, edited updater-script (following those instructions)
Immediately after flashing the OOS 3.13 rom, you don't have to reboot.
I immediately flashed twrp 3.0.3 original from https://dl.twrp.me/onyx/
I then rebooted into twrp 3.0.3 (using the reboot button in twrp, then bootloader)
Then I installed (in this order):
cm 14.1 (https://download.cyanogenmod.org/?device=onyx)
arsenic kernel (as recommended above)
opengapps
Not sure if this step is necessary, but I wanted to let twrp patch the rom to not overwrite twrp so I rebooted into twrp again (using reboot --> bootloader in twrp)
Then I used reboot --> system
First boot took a while, but now I have nougat!!
kenel zip every time
Do i need to flash the kenel zip every time I update the the cm 14.1 zip file?
allons-y said:
Do i need to flash the kenel zip every time I update the the cm 14.1 zip file?
Click to expand...
Click to collapse
Yes, as when you flash the CM 14.1 build, the kernel that is provided with the build is also flashed, and that is not supported. So you need to flash it every time you flash a CM 14.1 build, but if you want to flash any other build, something like CM 13.0, then you need not as the kernels provided in those are supported.
aamodjoshi23 said:
Yes, as when you flash the CM 14.1 build, the kernel that is provided with the build is also flashed, and that is not supported. So you need to flash it every time you flash a CM 14.1 build, but if you want to flash any other build, something like CM 13.0, then you need not as the kernels provided in those are supported.
Click to expand...
Click to collapse
Hi,
I have a very specific problem. I rooted my Oneplus x few months back and everything was fine. I use to get update notifications and after downloading it use to update automatically. But since last 2 months i download the update files but it takes me to recovery and then i cant find the zip file to flash/install. (i also started using external sd card two months back, but not sure if it has to do anything with this). I tried searching a solution on web - tried checking 'system' under Mount tab, installed an app for auto update and some more but no use. I even connected my phone in recovery mode to laptop and copied the zip file to internal memory but while flashing it gave error.
Now i am not sure what the problem is. Do i need to update my recovery or something else. Pls help.
shashanksachdeva said:
Hi,
I have a very specific problem. I rooted my Oneplus x few months back and everything was fine. I use to get update notifications and after downloading it use to update automatically. But since last 2 months i download the update files but it takes me to recovery and then i cant find the zip file to flash/install. (i also started using external sd card two months back, but not sure if it has to do anything with this). I tried searching a solution on web - tried checking 'system' under Mount tab, installed an app for auto update and some more but no use. I even connected my phone in recovery mode to laptop and copied the zip file to internal memory but while flashing it gave error.
Now i am not sure what the problem is. Do i need to update my recovery or something else. Pls help.
Click to expand...
Click to collapse
First of all we need more info about your current ROM recovery etc.
Fap4k said:
First of all we need more info about your current ROM recovery etc.
Click to expand...
Click to collapse
I installed CM 13.0-20160928-NIGHTLY-onyx and the recovery is: TWRP v2.8.7.0 | blu_spark r8
I'll be grateful for a solution.
shashanksachdeva said:
I installed CM 13.0-20160928-NIGHTLY-onyx and the recovery is: TWRP v2.8.7.0 | blu_spark r8
I'll be grateful for a solution.
Click to expand...
Click to collapse
In October oneplus updated to 6.0.1 officially i.e OOS 3 it brings new bootloader to the device as you are using old recovery you can't flash new update..so you need to upgrade to latest bootloader by following thread available in general section or you can flash stock recovery and upgrade to latest OOS and flash whatever you want to flash..I recommend you to see how to upgrade bootloader in general section if you are planning to flash custom ROMs or if want to flash latest OOS then simply flash stock recovery and upgrade. onece you updated to OOS 3 after that you can flash new official twrp 3.0.3.0 from its official page.
Edit: for old bootloader you need stock 5.1.1 recovery..which is not available in official oneplus download page..so just follow below link
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Fap4k said:
In October oneplus updated to 6.0.1 officially i.e OOS 3 it brings new bootloader to the device as you are using old recovery you can't flash new update..so you need to upgrade to latest bootloader by following thread available in general section or you can flash stock recovery and upgrade to latest OOS and flash whatever you want to flash..I recommend you to see how to upgrade bootloader in general section if you are planning to flash custom ROMs or if want to flash latest OOS then simply flash stock recovery and upgrade. onece you updated to OOS 3 after that you can flash new official twrp 3.0.3.0 from its official page.
Edit: for old bootloader you need stock 5.1.1 recovery..which is not available in official oneplus download page..so just follow below link
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
shashanksachdeva said:
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
Click to expand...
Click to collapse
This is because you flashed wrong recovery twrp 3.0.3 is for new bootloader and you are on old bootloader..that's why it all happened..so you just need to flash old recovery..then follow given link to upgrade bootloader and recovery.
shashanksachdeva said:
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
Click to expand...
Click to collapse
I've got a good news and bad news for you.
The bad news is, no one has the older 2.8.x TWRP image files and there are no threads that have the download links for the older version of TWRP. So you're stuck and you have lost your recovery. You have lost everything... Having no recovery means you can't do a lot of things like factory reset, any wipe of a partition, you won't be able to update your system, you won't be able to flash zip files to enhance your experience and many more... I'm sorry my friend...
The good news is, I've got you covered. I had saved the older TWRP so that if anyone one day would need that recovery image, I would be able to help them.
Download the older TWRP from here : https://drive.google.com/file/d/0B2Ms-zaNd3SiTmpxX0UtYUV2R1k/view?usp=drivesdk
Flash it. You should get back your recovery.
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Plush suthar said:
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Click to expand...
Click to collapse
Which ROM you are on currently?
If possible post screenshot of about device in setting.
Fap4k said:
Which ROM you are on currently?
If possible post screenshot of about device in setting.
Click to expand...
Click to collapse
using resurrection remix marshmallow 6.0...
Plush suthar said:
using resurrection remix marshmallow 6.0...
Click to expand...
Click to collapse
Did you ever updated bootloader?
If not than update your bootloader and install latest recovery!!
Plush suthar said:
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Click to expand...
Click to collapse
By stuck on boot, I didn't know you meant that it showed only the OnePlus logo and not even powered by Android.
In that case, follow this guide to update your bootloader :
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Hey fellas,
so I rooted my phone and tried to install some Magisk modules, but after rebooting it got stuck in the TWRP bootloop. So I flashed the Nandroid backup and it got stuck in the OOS boot animation. After that I tried reflashing OOS, but it didn't change anything, so I tried Lineage OS and now it won't even get past the Oneplus logo at the beginning and keeps restarting.
Thanks in advance
EDIT: when I flash the stock ROM through TWRP it installs normally, but then when I try to reboot it says there is no OS. So I flashed the stock OS to try adb sideload, but my pc says it cannot read the zip.
I also decrypted my phone through the OP5 Decrypt App, before the bootloop it worked for some time.
Of course I wiped everything before every action.
if you can bootup into recovery, try go into advanced and format data and system.
if you can't your last chance is using adb - flash a default rom.
Is it any different than wiping everything? Because it didn't do anything. I can access both twrp and fastboot so I guess it's not that bad
sounds like you went from unencrypted to an encrypted rom and your data is encrypted, or visa versa.
yep, it's vice versa, I used the OP5 Decrypt App after rooting. Is OP5 encrypted by default?
If you've tried the Android 8.0 Rom, just go to the official OP5 support site and download stock rom, flash it via ADB sideload if you can. (Don't forget to format data etc etc..) and restart from scratch.
Unlock BL if it's relock, then flash TWRP and go for a custom ROM. That's what I did, happened to me 2 days ago.f
EDIT : Oh you just flashed Magisk.. Well, try this anyway.
I tried flashing Lineage, but I can't install Oxygen
Ok, so apparently OOS boots up only after relocking the bootloader. And I had to make adb use more RAM to get sideload to work.
I am currently using a OnePlus 5 which used to run on a stock based rom, xxxNoLimits v3.1
Since the dev ended the support I wanted to revert back to pure OOS, so I downlaoded the newest 5.1.5 zip and followed the instructions using the newest blu_spark twrp recovery but right after pressing the "flash" button I kept getting error 7, so I download the zip from a mirror link and I have also tried the newest version of codeworkx twrp, still error 7. Then I tried flashing the original stock recovery in order to flash the zip but it instantly threw me back to the zip selection menu, flashing the zip via adb sideload kept quitting at exactly 47%. At this point I was pretty frustrated, I flashed twrp codeworkx again and wiped EVERYTHING, which includes the system, data, cache, dalvik partitions and then I also did a format on the data partition, the point was that now I would have a clean phone only running twrp and I thought I could easily flash the newest zip now without any problems, NOPE, still error 7!!! Now I am stuck here, the stock recovery doesnt let me flash anything and I've tried 4 different versions of twrp recoverys and every single one gives me the same error, I even dug up an older version of OOS, I think it which I had running for a few weeks without any probles so I knew that the zip was not corrupted but same error
Now I had given up and wanted to restore the backup I did just in case anything goes wrong, well, restoring the backup fails when it tries to restore the data partition, so I unchecked everything except system, system image and recovery but it didnt work, now I am sitting here with my phone telling me that there's no OS installed. any advice?
Use Unbrick Tool and Restore
Hey,
You can Flash your Mobile using the Unbrick tool at - https://androidfilehost.com/?w=files&flid=204903
Use the Latest file which I guess comes with OOS 5.1.3 - https://androidfilehost.com/?fid=962339331458999196
If you try to Go to Open Beta ROM First Flash Open Beta 12--> Open Beta 13 --> Open Beta 17
freaky2xd said:
I am currently using a OnePlus 5 which used to run on a stock based rom, xxxNoLimits v3.1
Since the dev ended the support I wanted to revert back to pure OOS, so I downlaoded the newest 5.1.5 zip and followed the instructions using the newest blu_spark twrp recovery but right after pressing the "flash" button I kept getting error 7, so I download the zip from a mirror link and I have also tried the newest version of codeworkx twrp, still error 7. Then I tried flashing the original stock recovery in order to flash the zip but it instantly threw me back to the zip selection menu, flashing the zip via adb sideload kept quitting at exactly 47%. At this point I was pretty frustrated, I flashed twrp codeworkx again and wiped EVERYTHING, which includes the system, data, cache, dalvik partitions and then I also did a format on the data partition, the point was that now I would have a clean phone only running twrp and I thought I could easily flash the newest zip now without any problems, NOPE, still error 7!!! Now I am stuck here, the stock recovery doesnt let me flash anything and I've tried 4 different versions of twrp recoverys and every single one gives me the same error, I even dug up an older version of OOS, I think it which I had running for a few weeks without any probles so I knew that the zip was not corrupted but same error
Now I had given up and wanted to restore the backup I did just in case anything goes wrong, well, restoring the backup fails when it tries to restore the data partition, so I unchecked everything except system, system image and recovery but it didnt work, now I am sitting here with my phone telling me that there's no OS installed. any advice?
Click to expand...
Click to collapse
Flashing newest oos doesn't always work l have had this sometime l have had to go back 3 oos versions then flash them in order to flash the latest release.
freaky2xd said:
I am currently using a OnePlus 5 which used to run on a stock based rom, xxxNoLimits v3.1
Since the dev ended the support I wanted to revert back to pure OOS, so I downlaoded the newest 5.1.5 zip and followed the instructions using the newest blu_spark twrp recovery but right after pressing the "flash" button I kept getting error 7, so I download the zip from a mirror link and I have also tried the newest version of codeworkx twrp, still error 7. Then I tried flashing the original stock recovery in order to flash the zip but it instantly threw me back to the zip selection menu, flashing the zip via adb sideload kept quitting at exactly 47%. At this point I was pretty frustrated, I flashed twrp codeworkx again and wiped EVERYTHING, which includes the system, data, cache, dalvik partitions and then I also did a format on the data partition, the point was that now I would have a clean phone only running twrp and I thought I could easily flash the newest zip now without any problems, NOPE, still error 7!!! Now I am stuck here, the stock recovery doesnt let me flash anything and I've tried 4 different versions of twrp recoverys and every single one gives me the same error, I even dug up an older version of OOS, I think it which I had running for a few weeks without any probles so I knew that the zip was not corrupted but same error
Now I had given up and wanted to restore the backup I did just in case anything goes wrong, well, restoring the backup fails when it tries to restore the data partition, so I unchecked everything except system, system image and recovery but it didnt work, now I am sitting here with my phone telling me that there's no OS installed. any advice?
Click to expand...
Click to collapse
Hi ! Do you have some news about it ? I have the same issue since Monday...
I've tried like anything i've found and even more, but nothing did the job ...
The only way to have my OP5 working is downgrade to an old version running Android 7.1.1
Hello everyone, I'm trying to flash Havoc os 3.0 alongside with BitGaps, but it always ends up in a bootloop (I always wait one hour in the "android" boot screen). My device is the A205G with Android 10. I successfully flashed TWRP using the guide posted here in xda (also flashed magisk), then I flashed Havoc and BitGaps (wiping dalvik, cache, data and system first and then doing a factory reset), but ended up in a bootloop after rebooting to system. In a second try after reinstalling Android 10 stock rom I followed the steps shown in a youtube video (can't post link since I'm a new user) with no luck (still getting a bootloop). In a third try I just flashed the stock rom, then flashed twrp with odin and tried to flash Havoc without flashing Magisk at any moment, still bootloop. Any ideas or suggestions on what could be wrong? I've only flashed one device before with a custom rom so I'm not an expert in this area, any help will be appreciated.
Downgrade phone to Android 9, later flash twrp, then install system and Gapps.
GamingMichu said:
Downgrade phone to Android 9, later flash twrp, then install system and Gapps.
Click to expand...
Click to collapse
Thank you so much! Worked perfectly.
No problem bro. If you have problems, write to me, I will try to help.
Hi,
I used Lineage OS 17.1 Lavender on my Xiaomi Redmi Note 7. I used their recovery to install the ROM and open gapps. Recently I downloaded the Brave Browser and I wanted to enable rewards. I than googled, that Brave doesn't allow rewards on rooted phones. I decided to wipe the entire phone, since I don't use the root functionality and to re-flash Lineage OS 17.1. I factory reseted the phone and wiped everything, just like I did, when I installed Lineage for the first time. I clicked on "Yes" when prompted that the ISO couldn't be verified, and waited for the flash. After a while I was "greeted" with Updater process ended with Error 7. I did some research and found out that it is something to do with the updater file verification and that I should try and delete some lines. I did that, but the error persisted. I than decided to try another ROM. I used Pixel Experience since it was working on my device before. Unfortunatly I had no luck. Same error message. I than tried to flash TWRP with fastboot, which worked. Wiped my device, just like they say it in all the guides (Dalvik, Data, Cache) and tried to flash Lineage (still no luck), than PixelExperience (still no luck) and Magisk worked. After I flashed Magisk I tried Lineage and Pixel once again, but still the same error.
If you know, how to fix that error I will be so glad. Is it possible that my device is bricked and beyond recovery? Thank you in advance.
update your tvvrp
Which firmware do you have installed? Use stable to maximum compatibility, on some ROMs if you have latest you gonna get that error. Also, use the latest TWRP or Orange Fox.
As Tatoh said, this error occurs when you have old firmware flashed on your RN7, some roms require specific version but usually flashing latest stable will give you best compatibility, here you have xda links to latest xiaomi firmware files: https://forum.xda-developers.com/redmi-note-7/development/firmware-xiaomi-redmi-note-7-t3925871