Hello Guys!
I tried flashing Omni rom (the latest nightly build) to my N7100 but it failed in TWRP and now my phone boots into twrp every time, that's all it can do. What should I do?
autox3c said:
Hello Guys!
I tried flashing Omni rom (the latest nightly build) to my N7100 but it failed in TWRP and now my phone boots into twrp every time, that's all it can do. What should I do?
Click to expand...
Click to collapse
An error message would be helpful. You could try downloading again, and compare md5s (preferably) or download size. That or use a different/older version of omni if this one isn't working.
Related
So today I received a XT 1056. I then proceeded to unlock the bootloader and flash SU.
So I then tried flashing a CM 12 nightly build and all went well. I was able to setup the device until the screen was locked and then the phone instantly starts looping through the "Unfortunately, system UI has stopped." error. I've tried flashing an older version of the ROM, and I've tried numerous other 5.0 ROM's but each one will crash as soon as the screen is locked.
And it would not seem like a great idea to revert to an older version of Android and risk bricking the device.
So if someone could advise me how to get rid of the loop error it would be much appreciated.
I have TWRP 2.8.3 currently flashed if that makes any sort of difference....
Install the gApps...
690sid said:
Install the gApps...
Click to expand...
Click to collapse
I tried a fresh install of this CM12 with the gapps it says to use and once again I can setup the phone and as soon I get to the home screen the system UI loop happens. http://forum.xda-developers.com/moto-x/development/rom-unofficial-nightly-lollipop-5-0-t2960768
I also saw your post in that thread to try flashing with these instructions, but it still has the same error.
1 - Download an earlier version of the ROM that booted on you phone along with the gapps.
2 - Flash the ROM and gapps with a suitable recovery... CWM or TWRP 2.6.
3 - Download the latest release that you want to install.
4 - Flash the latest release over the pre - installed ROM without wiping anything.
Is it possible to just flash 4.4.4 or do I risk bricking the device?
At the beginning, please forgive me the quality of my English.
Me and other friends using c6903 have posted on the forum about trouble with running Nougat ROMs:
- [ROM][7.1.X][27/07/17][STOCK-CAMERA][3.4 KERNEL][TESTING] LineageOS 14.1 - UNOFFICIAL
- [ROM] [7.1.2] [OMS] [OFFICIAL] [Honami] Resurrection Remix Nougat v5.8.3 [01/08/2017]
- [ROM] [7.1.2] [Substratum/OMS] [UNOFFICIAL] [Honami] Android Ice Cold Project 12.1
For example LinageOS 14.1.
I flashed build from 11/07 without any problems.
Everythings worked fine, but when i try to flash newest build I encountered a big problem.
Bootanimation continues 2-3 sec. and phone turn off [check plz video].
Then only the launch button was active.
Everything I do exactly the same as in 11/07 build.
Why rom can't run?
The situation applies to all the above versions.
Resurrection Remix Nougat from 28/06 booted fine too.
Newer versions not...
One of friends - MIcHiJK - suggested that this could be a problem with changing the screen for "fake".
Me and him changed screens probably for counterfeiting.
Maybe someone else did it and have this problem?
....but why build from 11/07 (LinageOS), 26/08 (RR) and 20/06 (ACIP) booted without any problems?? In my case change screen was earlier.
What have I done so far to solve the problem.
- used TWRP 3.0.0 and 3.0.2
- Always full wiped (a few times format internal storage using twrp too)
- flashed roms when using Cyanogenmod 12.1
- flashed roms when using stock .236
- restored software using EMMa and Flashtool, then root (kingroot), flashed twrp by fastboot, full wipe, flash rom - without result
- used others kernels referenced by creators roms (flashed after installation rom).
Nothing worked.
I know I'm not alone. Many guys have problem like me.
Is anyone able to give a solution?
May God bless guy which will solve our problems!
"https://youtu.be/sOBquHNlbzQ"
Hello to all ppl which had this problem.
Since I replace my broken original xperia z1 Display, I wasn´t able to boot any of the new Nougat rom releases.
I solved this problem with a new Kernel.
Super Lamic Posted this Kernel to test the Battery Life but with this Kernel the problem was solved and I was able to run the new Releases on my fake Display.
Kernel Link: https://mega.nz/#!RN1nFYRT!546WMDdM2ToJEeZlleKTjS-TdR54rkYiOGKUDDWQ-t0
Install new LineageOS build on your xperia z1 with TWRP 3.1 (with 3.0 it wasnt able to install the boot.img).
Before you reboot select images, boot and flash the boot.img.
Then the new build should run without problems.
On other roms like Resurrection Remix it endet in invinite boot so I was just able to run normal Lineage.
I hope it helped someone. Im still interested what the devs changed that causes this problem. And I hope there will be improvments in future that this problem wont happen anymore.
same problem for me like OP. Would be interesting whats the reason for this behaviour that some nougat roms don't run on phones with replaced display. for me some still run, but then i have the problem that recovery is not available.
For those wo will flash AICP maybe this solution will work in RR too.
In normal Lineage it worked when i flashed cm12.1 Nouagt Kernel after flashing LOS 14.1.
But for RR or AICP it ended in infinite boot. Here is how I managed to get it work.
1. Download AICP (Latest Version [2017/08/01]) then download AICP (Version 2017/06/20).
2. Delete 'boot.img' from the Latest Version zip and put the 'boot.img' from the older relase into the Latest
3. Boot into TWRP 3.1 or 3.0, Wipe all and flash your Latest AICP zip with the older boot.img.
4. Boot phone. The z1 will show you just the Sony Logo. I waited some Minutes and powered off with power + volume up.
5. Connect phone in fastboot mode on PC and flashed cm12.1 Nougat Kernel.
6. Type 'Fastboot Reboot', the phone Turns on with the newer Boot screen where xperia stands on the bottom. You will finally see AICP Boot Animation and after some time rom boots.
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
Aaskereija said:
same problem for me like OP. Would be interesting whats the reason for this behaviour that some nougat roms don't run on phones with replaced display. for me some still run, but then i have the problem that recovery is not available.
Click to expand...
Click to collapse
Just Install Recovery via Fastboot. If you dont know how to do this you need to set up android sdk. You will find many tutorials in the internet.
MIcHiJK said:
Just Install Recovery via Fastboot. If you dont know how to do this you need to set up android sdk. You will find many tutorials in the internet.
Click to expand...
Click to collapse
really funny. sound good, doesn't work
Aaskereija said:
really funny. sound good, doesn't work
Click to expand...
Click to collapse
How did you installed the rom?
From which rom you came and which recovery did you used and how did you installed the recover?
different ways, but mostly with my standard custom-rom Tesla which is on Android 5.1.1. TWRP is on 3.1 which i install via cmd (fastboot flash recovery) cause build in recovery of tesla is broken.
Or i go over latest stock with dualrecovery, flash boot.img of the custom-rom (wich work) and then flash rom. but still recovery is gone after that.
@Aaskereija
I can tell you how I installed. I never lost my recovery. I came from xproject rom and I had nuts dual recovery. I flashed via fastboot advanced kernel, rebooted directly into inbuild TWRP 3.1, wiped all and flashed nougat rom. I had no recover so I flashed via fastboot official TWRP 3.0 and now I have a recovery. Since I installed TWRP one Time i never done it again. Everytime I flash a new rom it's still there. Maybe you try some different ways to install a nougat rom cuz it should work we all have the same device. Another question. Can you give me link to TWRP 3.1 for honami. I can't find TWRP 3.1 for z1 I used it just with advanced kernel. I just can find official TWRP on the internet witch is outdated
Guys, you don't have to create threads for this. I'll have an aftermarket display too, so I'll be forced to fix it anyway. And I have an idea what can be wrong...
MIcHiJK said:
@Aaskereija
I can tell you how I installed. I never lost my recovery. I came from xproject rom and I had nuts dual recovery. I flashed via fastboot advanced kernel, rebooted directly into inbuild TWRP 3.1, wiped all and flashed nougat rom. I had no recover so I flashed via fastboot official TWRP 3.0 and now I have a recovery. Since I installed TWRP one Time i never done it again. Everytime I flash a new rom it's still there. Maybe you try some different ways to install a nougat rom cuz it should work we all have the same device. Another question. Can you give me link to TWRP 3.1 for honami. I can't find TWRP 3.1 for z1 I used it just with advanced kernel. I just can find official TWRP on the internet witch is outdated
Click to expand...
Click to collapse
how do u installed it? fastboot flash recovery or else?
i was mistaken, its 3.0.2 not 3.1 if u still ned it, download
Aaskereija said:
how do u installed it? fastboot flash recovery or else?
i was mistaken, its 3.0.2 not 3.1 if u still ned it, download
Click to expand...
Click to collapse
Android Sdk put twrp.img in platform tools folder then open CMD in this foder, fastboot flash recovery TWRP.img.
I asked about twrp cuz in advanced kernel is TWRP 3.1 inbuild but I can't find just the twrp 3.1 IMG without kernel. Strange.
Hi everyone,
I'm new here though but am a Xiaomi user from the beggining of Xiaomi into devices with Redmi Note 3G Enhanced.
Currently, I own a Redmi 4X and I would like your expert lights please. I've flashed the latest twrp from twrp.me for my santoni device. Then flashed the latest build from LineageOS Official source + Gapps before booting up for first time. Everything was working perfectly until I decided to flash the latest update of LineageOS as I've seen in my updater it was released. So, I downloaded it through the updater and tried to flash it...
I came up with this "Failed to unmount /system (device or resource busy)" after that re-booted to LineageOS and everything was messed up with Google Services & Apps etc. Then I went back to twrp recovery and tried to flash again the rom but I was still getting that message so I understood something am doing wrong. Also santoni has dm-verity enabled which I know something about but just an info. I really wanna stick with LineageOS on my Redmi 4X forever but I'm afraid to flash it again. I've flashed MIUI 10 Beta by fastboot but now I wanna go back to LineageOS forever (addicted).
My only problem is: After successfuly flashing LineageOS and Gapps, I cannot apply (flash) updates to update the ROM to the latest nightly build due to this error above.
Kind regards,
peryson
Try with different recovery. For example with this
Harukey said:
Try with different recovery. For example with this
Click to expand...
Click to collapse
Instead of trying an unofficial recovery, do I have an option to unmount system manually before flashing through Official TWRP?
peryson said:
Instead of trying an unofficial recovery, do I have an option to unmount system manually before flashing through Official TWRP?
Click to expand...
Click to collapse
You can download latest Lineage OS build and dirty flash it (without any wipes) (so you can unmout system parition). And I don't see any issue in using unoffical twrp.
I also have experienced same error once during upgrade "failed to unmount /system"
Eventually I wiped everything and did clean flash from scratch. This is really annoying issue and demonstrates that upgrade system is not 100% reliable for some reason.
I'm not sure however is it Lineage or twrp issue.
I was on latest stock PIE. First I tried to flash HEX kernel over stock PIE, but this resulted into bootloop.
Then I tried to flash, AICP and CRDROID, for both, it says, "error applying update: 7(errorcode::kinstalldeviceoppenerror) updater process ended with error 1".
Need help here ASAP. As I unable to boot to system right now. Using TWRP : 3.3.1 as TWRP 3.2.3 gets only black screen.
shivamg95 said:
I was on latest stock PIE. First I tried to flash HEX kernel over stock PIE, but this resulted into bootloop.
Then I tried to flash, AICP and CRDROID, for both, it says, "error applying update: 7(errorcode::kinstalldeviceoppenerror) updater process ended with error 1".
Need help here ASAP. As I unable to boot to system right now. Using TWRP : 3.3.1 as TWRP 3.2.3 gets only black screen.
Click to expand...
Click to collapse
I think Thats because of TWRP 3.3.1 version cuz this version got some issues for installing or updating roms.
Maharram said:
I think Thats because of TWRP 3.3.1 version cuz this version got some issues for installing or updating roms.
Click to expand...
Click to collapse
Any suggestion regarding which twrp should I use?
shivamg95 said:
Any suggestion regarding which twrp should I use?
Click to expand...
Click to collapse
I have tried pitch black and team win recovery project and everytime i get black screen. Im using fastboot to flash anything but idk u can flash hex kernel with fastboot or not. Just ask it from the hex kernel thread
literally just been messing with the exact same problem - try the pitch black recovery twrp - i cant find the link, have a look, if not come back here and I make available via dropbox or something. Everything failed with the error you get, i tried with this version and pixel rom installing !!!
Hello,
I'm trying to install custom ROMs but I can't get past Error 7 on my T710
Tried different versions of TWRP 3.3.1 and TWRP 3.4.0, tried many other ROMs, tried removing 'assert' from ROMs and many other different methods, still no luck.
Flashed the original firmware now, tried everything over again (flash TWRP, flash ROMs (full wipe/format) and still same issue.
I was able to flash LineageOS on my T713 without any issues, like that ROM a lot and want to use the unofficial version for T710.
Please help.
mx900 said:
Hello,
I'm trying to install custom ROMs but I can't get past Error 7 on my T710
Tried different versions of TWRP 3.3.1 and TWRP 3.4.0, tried many other ROMs, tried removing 'assert' from ROMs and many other different methods, still no luck.
Flashed the original firmware now, tried everything over again (flash TWRP, flash ROMs (full wipe/format) and still same issue.
I was able to flash LineageOS on my T713 without any issues, like that ROM a lot and want to use the unofficial version for T710.
Please help.
Click to expand...
Click to collapse
Any chance of testing older versions of TWRP?
Found this: "Q: Whenever I try flashing any (lineage-17.1) build, I get the following error in TWRP: Updater process ended with ERROR: 7
A: This error appears whenever you try to flash an Q-based rom within a version of TWRP older than 3.4. Simply flash the linked below version 3.4 or higher, reboot back into recovery, and flash the rom zip again. "
From: "https://forum.xda-developers.com/t/...ab-s2-sm-t710-t810-t715-t815-19-9-15.3187202/ "
might help