Flashed TWRP and Lineage OS but getting error while booting - ZTE Trek 2 Questions & Answers

Hi All,
I was able to successfully install TWRP and get Lineage OS installed but when I am booting initially I get an error message, it waits 5 seconds and then boots into the O/S.
https://i.imgur.com/qTzytc5.jpg
Is this because it's a custom rom? If not can someone let me know what I did wrong? Also I noticed that the phone dialer isn't working and see others having a similar issue. Are there any custom roms where this is working? If not and I want to go back to the stock rom, can I just apply the update.zip via TWRP?
Thanks for the help,
Nick

npolite said:
Hi All,
I was able to successfully install TWRP and get Lineage OS installed but when I am booting initially I get an error message, it waits 5 seconds and then boots into the O/S.
https://i.imgur.com/qTzytc5.jpg
Is this because it's a custom rom? If not can someone let me know what I did wrong? Also I noticed that the phone dialer isn't working and see others having a similar issue. Are there any custom roms where this is working? If not and I want to go back to the stock rom, can I just apply the update.zip via TWRP?
Thanks for the help,
Nick
Click to expand...
Click to collapse
if you can apply update.zip from twrp and the phone dialing does not work "only in some mobile operators" and on that adventecia of the screen in image that you uploaded, that error is because you started twrp for the first time without flashing root and rom, why root and rom has integrated dm-verity disabled
dm-verity boot: is responsible for verifying the first boot system partitions, such as boot, data, system etc ...
there is a file with name no-verity-opt-encrypt-6.0.zip that serves to deactivate dm-verity boot, but the adventecia the only way to remove it is with stock rom, back flashing the stock rom.

Related

[Q] D803 Help!

Hello XDA Developers,
I had a device that was rooted on stock rom and recovery. What happened was that an OTA was installed and it went to the "boot verify certification" screen. I had to install Ubuntu to get TWRP running again.
I'm able to boot into TWRP, and I tried installing different ROMs, using adb sideload, from Stock ROM, ParanoidAndroid, and Madri-ROM.
The first one was able to install, but when I reboot the phone, I get stuck on the LG logo. I wait for an hour and it still does not do anything.
So now I try the other two custom ROMs, and I get an error saying "E:Error executing updater binary in zip "... .zip".
Then it reads "Error flashing zip '... zip'.
My question is: What else can I do to get this phone working again? I would like stock ROM, and preferably stock recovery back (Recovery is secondary).
Thanks in advance,
DaAznMan
Note: When I use adb sideload, the .zip file that gets transferred becomes a file called 'sideload.zip'. Is that correct? If not, what do I need to do to fix it?

[GUIDE] How to get CM 14.1 working.

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

Can't boot to recovery.

Phone is Lenovo A6000, not plus. I installed multiple TWRPs, 3.1.0 and 2.9 something.
I even installed CWM, still couldn't boot to the recovery.
Now, I know how to flash with fastboot, and I know how to boot. Booting doesn't work at all, it says "booting" and never finishes.
Flashing says "okay" and I reboot, do a reboot to recovery, and I get put into bootloader/fastboot.
Any help? I just bought the phone today, no one messed with it.
Edit: Nevermind. CWM installed. How do I install TWRP, so it works? Also, forgot to mention that the phone has the latest stock rom, 4.4.4.
Edit#2: While trying to install "TWRP-3.1.0-Lenovo-A6000.img",
I got an error.
"Can't open /tmp/update.zip (bad)"
"Installation aborted."
Edit#3: Same error with multiple TWRP images.
First of all the twrp 3.1.0 is meant for nougat roms. Since you are flashing that recovery on KitKat rom which it won't support. So first try updating phone to stock lollipop. Then flash twrp 2.8. then take a complete backup(most important) and save it on SD card. After that flash any rom you want. If you are flashing marshmallow or nougat rom then after flashing rom flash 3.1.0 twrp.
I have long ago (10 minutes after last edit) fixed the problem already by flashing stock firmware through some weird software, and then started updating to latest lollipop firmware, and then installed TWRP 3.1 and then installed RR android version 7.1.2. But, thank you for trying to help. I hereby ask a moderator to close the thread because the problem was resolved. Thank you.

Stuck in bootloop in all LOS and OOS based roms

Hi guys, been using my rooted but otherwise stock OOS rom with TWRP and Magisk for the past few weeks. Today I decided to take the plunge and try either the Lineage OS or Resurrection Remix roms.
I'm using the latest OFFICIAL TWRP.
So I decrypted following the instructions to flash "no-verity-opt-encrypt-5.1.zip", then format data. All went well, so I then sent over the ROMS I wanted to try out. I started with the official ResurrectionRemix. Bootloop. Then the unofficial LineageOS. Bootloop.
Ok, well I guess I'm not gonna get to use any of the cool new OS's for awhile. I'll install the full stock firmware zip so I can have a working phone again. Bootloop.
Now when I say bootloop, the phone is booting to the BootAnimation and just repeating it. It shows the proper boot animation for whatever zip I have installed (resurrection/LOS/OOS), but it stays on there for up to 20 minutes before I have to hard reboot to the recovery again.
I decided to install the stock recovery trying a few methods. I first tried the ALL-IN-ONE tool. It said it flashed the recovery fine, so I booted to the recovery and after staying on a black screen for too long, the language options came up and I sighed a breath of relief. But before I could select English with the volume buttons, it rebooted by itself. It did this again when I manually entered recovery. So I figured maybe the tool flashed the wrong version, so I googled stock recovery for OnePlus 5, I found a few random links for stock recoveries for the OP5 and flashed them, but they more or less do the same thing or not boot at all.
I've tried changing the filesystem for both Data and System using any combinations of EXT4 and F2FS. Everything results in boot animation bootloops.
I have been flashing Roms since the Samsung Galaxy S3 and every phone since and never had any problems.
Currently when trying to install the stock Full OOS official zip with TWRP, the phone won't even go to the boot animation, it only goes to a black screen with the top LED in a light blue color.
I have also tried every version of TWRP there is for the OnePlus 5. Unofficial, Official, 3.1.1-0 and 3.1.1-1.
So I guess my question is....What filesystem is each partition supposed to be on and for which OS?
Lineage based:
System: ?
Data: ?
OOS Based:
System: ?
Data: ?
And any ideas on getting my phone running again?
And anyone have an official confirmed working version of the stock recovery? The one from ALL-IN-ONE TOOL doesn't work for me. It loads the language selection, then the screen goes black with a light blue LED on the top of the phone.
Actually I'm getting that on some roms instead of the bootanimation, like FreedomOOS. What does it mean when you have a black screen and a white LED?
Man, I really thought I was getting somewhere. If I boot into TWRP, change the Data partition to "F2FS", then flash the stock recovery, the stock recovery will boot, however, when inside the stock recovery and I try to flash the stock zip, it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
Ok, I have the official stock recovery from the OnePlus site, but still can't use it. Here is was happens depending on how I left it with TWRP:
System: F2FS
DATA: F2FS
- Stock recovery will load after some time, freeze, then the screen goes black with white LED on top.
System: EXT4
DATA: F2FS
- Stock recovery loads fine, I can go through the settings and install from SD card, but when I do it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
System: EXT4
DATA: F2FS
- If I try to flash stock rom through TWRP, it just boot loops on the animation forever.
I have now also tried flashing the stock boot.img, but no difference.
I have 2 things you can try!
First, replace the bootloader with stock and do a factory reset:
1. flash the stock recovery over
2. then in fastboot mode enter, fastboot oem lock (This forces the phone to wipe cache and data, and also do a complete reset)
Did it work? if yes YAY if not go to Second!
Second if your system.img is ****ed up you have to replace it!
Download the newest version of the stock rom from oneplus link here
Unpack it
research how to use an extractor to convert the system.new.dat to system.img
once thats completed enter fastboot mode and flash the new system.img over with Fastboot flash system system.img
now go into recovery and do a factory reset and wipe cache, and dalvik
Please reply back wether or not this work
"Ihave 2 things you can try! First, replace the bootloader with stock and do a factory reset..."
Is the bootloader simply the boot.img?
After doing the first thing, it simply says that the device is corrupt and will not boot. But it is locked again.
But I will have to unlock it again to do any further flashing.
Hmm, I think I may have gotten it. After unlocking again, flashing the stock recovery and boot.img, then locking again and wiping in the stock recovery, I have finally booted into the stock rom.
I still have no idea what went wrong, and I really want to know, so that in the future I can flash other Roms, like LineageOS.
I mean, I followed the steps exactly.
If it says the device is corrupt it simply means you got something else besides stock rom.
So now unlock it and try the system.img instead
It was because I still had TWRP with the stock rom.
I got it working though, thanks for your help.
Do you have any idea on what might have went wrong when trying to flash the lineageOS based roms and why it got messed up so royally?
Great to hear you fixed it ^_^
Probably some minor bug, if you wanna try installing lineageos again use the 3.1.1 TWRP build that supports backups and do a full backup so you don't have to go thru all this again
---------- Post added at 12:17 AM ---------- Previous post was at 12:13 AM ----------
Not really just try again but remember to use TWRP 3.1.1, as 3.1.0 don't support backup and probably have been part of your problem
If your trying again and gets it successfully installed could you do me a favor and test if Drivedroid works on it? And pm me the result, I'm looking for a rom where Drivedroid will work... Haven't found one so far
You know, I did do a backup with the OFFICIAL TWRP, but it also resulted in a bootloop. I made the backup after decrypting, so I don't know why it bootlopped.
https://forum.xda-developers.com/oneplus-5/development/rom-unified-lineageos-7-1-2-t3635483
Is this the one you tried installing?
I tried like every ROM at one point yesterday, but I think I started with
https://forum.xda-developers.com/oneplus-5/development/rom-resurrection-remix-n-7-1-2-t3636578
Did you remember Gapps?
Also in some cases its better not to root before you have the custom rom running, you usually only need a custom bootloader like TWRP
Yeah, I tried with Gapps, and I never rooted before first trying to boot.
As of yesterday Ressurrection remix, released the first official stable build so try again your should'nt have any problems if you follow the guide 100%
Ever find a solution? I'm stuck here now. Can't get any ROM to boot up, they all get stuck on the boot animation
Bump. I am also stuck in this state

'The System has been Destroyed' when installing TWRP zip in hotboot TWRP

UPDATE - Did not manage to find a way to get TWRP installed permanently but did manage to install Lineage OS 16 (which was my end goal) via hotboot of their recovery IMG, so happy with that at least! Appreciate any help given!
Not sure what I am doing wrong. have never come across this before!
I just completely reset my phone to stock via MiFlash
I then boot into TWRP recovery from Fastboot
I then install the TWRP installer in TWRP
I then reboot to recovery but get 'The System has been Destroyed'
I can still boot into the stock ROM
I can still boot into Fastboot
I just can't seem to get TWRP to install, I can only access it in hotboot
Any help would be amazing!
It's a known issue with Stock Pie and permanent TWRP.
A solution is to install magisk before booting to system
Tepig said:
It's a known issue with Stock Pie and permanent TWRP.
A solution is to install magisk before booting to system
Click to expand...
Click to collapse
Oh well damn, I will give that a shot thank you!
Tepig said:
It's a known issue with Stock Pie and permanent TWRP.
A solution is to install magisk before booting to system
Click to expand...
Click to collapse
Unfortunately did not do the trick for me
I installed TWRP then magisk, then rebooted to system
I then rebooted back to recovery but still get 'The system has been destroyed' message
MoonCakeHug said:
Unfortunately did not do the trick for me
I installed TWRP then magisk, then rebooted to system
I then rebooted back to recovery but still get 'The system has been destroyed' message
Click to expand...
Click to collapse
Never install twrp on stock pie. You'll get the same message. Hotboot it only.
MoonCakeHug said:
Unfortunately did not do the trick for me
I installed TWRP then magisk, then rebooted to system
I then rebooted back to recovery but still get 'The system has been destroyed' message
Click to expand...
Click to collapse
From what I have tried it seems that it is a bug with stock pie, custom roms with pie and stock oreo don't have this problem.
Anyway, you can basically get the same functionality by hotbooting but it's less convenient.
I have TWRP installed and resurrection remix. Maybe their TWRP works for you, just check the instructions and give it a try.
I think you should install TWRP in both slot A and B for it to work.
MoonCakeHug said:
Unfortunately did not do the trick for me
I installed TWRP then magisk, then rebooted to system
I then rebooted back to recovery but still get 'The system has been destroyed' message
Click to expand...
Click to collapse
Weird, it used to work for me when I was on stock pie.
I'm on a custom rom right now so I cannot test if it still works.
Sorry
I also have the same problem but now I'm on a custom rom and the TWRP without magisk works, but I would like to try an sGSI, on a custom rom does the procedure work?
Try another twrp
I'm here also had the same problem on mi A2 lite
But Rom run smooth and stable for a long time that I even forgot I have no twrp. Instead I backed up with titanium bk just in case. So ,Hotbooted with adb.... less convinient but u get to where u wanna flash though

Categories

Resources