problem after installing miui 5.10.25 - GiONEE Elife E7

i was on miui 5.7.31.it was working fine.then i ported to 5.10.25 and the screen went awry(multiple strip lines and background not clearly visible) and my twrp recovery became chinese.Then again i wiped system,data and cache and ported 5.7.31, rooted the phone and flashed twrp 86 using rom toolbox.Althogh the recovery came back to previous one but my background screen shows iuni logo even when i open my camera app(although the logo is not visible in the actual pic)....please help

Related

[Q] LG L7 P700 CyanogenMod

Hi,
I have installed CyanogenMod 10.2 from this thread: http://forum.xda-developers.com/showthread.php?t=2396115.
Previously the phone had the original LG Android 4.0 ICS software.
First i've bricked the bootloader and installed CWM. Then I installed CyanogenMod.
I tried to boot the phone. After half an hour with the Cyanogen boot logo I got panic and went into recovery where I did a factory reset(wipe data) and I wiped the cache partition and the dalvik cache. Then I rebooted the phone and suddenly it works.
Have I made any mistakes?
Until now it works very fine.
Another problem is that when I boot the phone first the LG logo appears then there are some artifacts (see the picture) and then the cyanogen boot logo appears.
Is that normal? Should I reinstall all?
I hope you can help me
If you flash a ROM, you have to wipe data, cache and dalvik. So maybe the first time you forgot to do it, that's why it didn't boot. And the artifacts are normal on 4.3 ROMS with more RAM !
Sent from my LG-P700 using XDA Premium 4 mobile app
error123 said:
Hi,
...I installed CyanogenMod.
I tried to boot the phone. After half an hour with the Cyanogen boot logo I got panic and went into recovery where I did a factory reset(wipe data) and I wiped the cache partition and the dalvik cache. Then I rebooted the phone and suddenly it works.
Have I made any mistakes?
Click to expand...
Click to collapse
I installed the same ROM doing a full wipe and also my LG L7 crashed showing the initial animation during the first boot. I restarted the phone by holding down the power button and this has made ​​the second start regularly.
error123 said:
Another problem is that when I boot the phone first the LG logo appears then there are some artifacts (see the picture) and then the cyanogen boot logo appears.
Is that normal? Should I reinstall all?
Click to expand...
Click to collapse
The initial graphic artifact, after the LG logo, seems to be a normal thing: it appears for a few seconds and then everything works fine.

(Help) S5 Stuck in bootloop after factory reset

Hey guys, my galaxy S5 was rooted, running a version of TWRP (can't remember the specific version) and was also running the latest version of Cyanogenmod available for the S5.
I went to factory reset the phone in the settings tab in Cyanogenmod and now all my phone will do is display the teamwin logo as if about to boot into recovery then go black, then display it again (bootloop)
Anyone any suggestions on how to fix?
Cheers, Lewis
Try reflashing cyan.
tapatalked
I've tried it, Odin won't recognise my phone
You're also not able to flash it via custom recovery?
tapatalked
Tactical_trax said:
I went to factory reset the phone in the settings tab in Cyanogenmod and now all my phone will do is display the teamwin logo as if about to boot into recovery then go black, then display it again (bootloop)
Click to expand...
Click to collapse
As rajman already pointed out, you can remove the battery, insert again and power on with the buttons volume+ and home pressed and hold. This should start Twrp right away. From there you can try to do a wipe of data, cache, dalvik and eventually internal SD and reboot. If this still does not help you can copy the cm installation zip to your external SD and flash it with Twrp.

G530H Black Screen After Flashing a custom ROM

Hello
I just tried to installed custom ROMS (one is the CyanogenMod 12, and the other is PAC-ROM)
What I did is, backup the stock ROM with Philz recovery and wipe my data (factory reset, cache, and dalvik).
Then I successfully installed the Custom ROM with the recovery, and reboot my phone.
What happened is, when the SAMSUNG logo appeared, at the top of the screen, appeared a red colored text 'kernel is not seandroid enforcing'
and then, my phone stuck in a black screen. (no any messages, just a black screen).
I'm Using the stock firmware: G530HDCU1AOF1_G530HOLB1AOF1_G530HXCU1AOD1_HOME.tar
(https://samsung-firmware.org/downlo...al-Sim)/7f11/XID/G530HDCU1AOF1/G530HOLB1AOF1/)
Any one can help with my prob? Thank You
motionfrog said:
Hello
I just tried to installed custom ROMS (one is the CyanogenMod 12, and the other is PAC-ROM)
What I did is, backup the stock ROM with Philz recovery and wipe my data (factory reset, cache, and dalvik).
Then I successfully installed the Custom ROM with the recovery, and reboot my phone.
What happened is, when the SAMSUNG logo appeared, at the top of the screen, appeared a red colored text 'kernel is not seandroid enforcing'
and then, my phone stuck in a black screen. (no any messages, just a black screen).
I'm Using the stock firmware: G530HDCU1AOF1_G530HOLB1AOF1_G530HXCU1AOD1_HOME.tar
(https://samsung-firmware.org/downlo...al-Sim)/7f11/XID/G530HDCU1AOF1/G530HOLB1AOF1/)
Any one can help with my prob? Thank You
Click to expand...
Click to collapse
That's because you're using the Kitkat firmware nd trying to install a lollipop ROM. Upgrade your Firmware to Lollipop nd then install these ROM.

Phone stuck at boot animation.

I have a rooted Lenovo A6000 Plus.
Today, I was trying to install custom TWRP recovery, after which I planned to install XPOSED framework.
I installed the framework(used ADB). My device went into TWRP recovery.
I rebooted the device, but was unable to go into TWRP again.
So I flashed the recovery again. Again, my device went into TWRP recovery, but this time, it auto-installed XPOSED. After reinstallation, my device showed the Lenovo logo, after which the screen went black. I removed the battery to switch it back. But again, the Lenovo logo appeared, after which the screen went black. After a few times, I just let my phone sit at the black screen. L8r the boot animation appeared (I had a custom one installed).
Now my phone is just stuck at the animation.
P.S. I have tried removing the battery and rebooting many times.
PLEASE HELP URGENTLY!
@adityapathak343, the XPOSED package also comes with a Uninstaller zip, which you would've found on the same page. Just flash that zip with TWRP, and if the phone still doesn't boot then wipe the cache and dalvik partition through TWRP only.
flash stock rom
Download and flash stock ROM
It will definitely going to be ok
Download stock ROM from firmwarefilecom
Just download & flash from recovery
I have link but can't able to share right now

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

Categories

Resources