Phone stuck at boot animation. - Lenovo A6000/Plus Questions & Answers

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

Related

Problem with installing TWRP

My phone came with version 66.77.... (MIUI 6) from the reseller.
I have installed TWRP, rooted the device using adb and then flashed 5.9.24. So far so good.
After some time i decided to try AOSP ROM. I made a backup in TWRP and then flashed AOSP using TWRP. No problems so far (cleared cache, dalvik etc)
Then I wanted to revert back to 5.9.24. I cleared cache dalvik etc, and then I cannot remember anymore if i have reflashed 5.9.24 or restored the backup made previously from TWRP, the thing I wasn't able to boot into recovery anymore. The phone was stuck on the teamwin logo if booted into recovery but normal boot was working fine.
Then i reflashed twrp using adb.
After doing that, my phone was still stuck on the teamwin logo when booting into recovery, but with normal booting i was getting infinite boot loops at Mi logo screen.
After several ours of tries, i was able to solve the normal booting problem by flashing the stock recovery (so the phone is now back on the 5.9.24 - and working fine) but when I try to flash twrp using adb the same symptoms as before:
- Recovery boot - stuck on teamwin logo screen
- Normal boot - boot loops
I already tried to flash via Updater app, Flashify and Windroid nothing worked.
Can anyone help me to get this custom recovery working, please?
Thanks
Regards,
Nick
lukke04 said:
My phone came with version 66.77.... (MIUI 6) from the reseller.
I have installed TWRP, rooted the device using adb and then flashed 5.9.24. So far so good.
After some time i decided to try AOSP ROM. I made a backup in TWRP and then flashed AOSP using TWRP. No problems so far (cleared cache, dalvik etc)
Then I wanted to revert back to 5.9.24. I cleared cache dalvik etc, and then I cannot remember anymore if i have reflashed 5.9.24 or restored the backup made previously from TWRP, the thing I wasn't able to boot into recovery anymore. The phone was stuck on the teamwin logo if booted into recovery but normal boot was working fine.
Then i reflashed twrp using adb.
After doing that, my phone was still stuck on the teamwin logo when booting into recovery, but with normal booting i was getting infinite boot loops at Mi logo screen.
After several ours of tries, i was able to solve the normal booting problem by flashing the stock recovery (so the phone is now back on the 5.9.24 - and working fine) but when I try to flash twrp using adb the same symptoms as before:
- Recovery boot - stuck on teamwin logo screen
- Normal boot - boot loops
I already tried to flash via Updater app, Flashify and Windroid nothing worked.
Can anyone help me to get this custom recovery working, please?
Thanks
Regards,
Nick
Click to expand...
Click to collapse
Tried this: http://en.miui.com/thread-152550-1-1.html?mobile=2
Sent from my 2014817 using Tapatalk
timberwolf60 said:
Tried this: http://en.miui.com/thread-152550-1-1.html?mobile=2
Sent from my 2014817 using Tapatalk
Click to expand...
Click to collapse
i saw the request of the message but i am not using a custom recovery on my phone,i use a custom dev rom made by miui france.
i think some china dev rom comes rooted by default with custom installer updater and gapps like mine.
i think twrp is not fully compatible with this device yet.
Have you try with sp flash tool method ?
http :// en.miui.com/forum.php?mod=viewthread&tid=156838&extra=page%3D4&mobile=2
I just installed TWRP for the first time ever. I used the Flashify App from the Play Store, installed it and gave it root permissions and just selected the TWRP image on the phones internal store. Seemed to work just fine and did not have to plug my phone into a computer

[TWRP] [G900H] Recovery Flash Successful, But Still At Stock Android Recovery

Hi all,
My Samsung Galaxy S5 G900H, I updated it to stock Samsung Android 6.0.1. Now I want to root it. AS I've read in some of the other threads that flashing TWRPand then the latest SuperSU works. I went ahead and flashed TWRP using ODIN. Odin was successful and my phone rebooted and phone is working fine. But when I try to go into recovery, stock Android recovery pops up. I wonder why?? Can anyone point me out?
try this recovery you will be solved...
juz flash it with Odin 3.09
https://www.androidfilehost.com/?fid=24459283995296044
As rewards hit Thanks
Use twrp 3.0 by fevax i was had same problen but when u flash it reboot to recovery then to systen
I flashed this same recovery earlier. It is not working for me.
It's the same one I flashed earlier. Not working for me. Should I try to reflash the stock firmware and try again??
"flash it reboot to recovery then to system" Important point. This worked. Instead of rebooting directly after flashing. I flashed recovery, then removed battery to turn device off. Then rebooted into recovery. It WORKED.
I think rebooting into system first rewrites TWRP with stock recovery.
guru_iyer's Avatar
Edit
"flash it reboot to recovery then to system" Important point. This worked. Instead of rebooting directly after flashing. I flashed recovery, then removed battery to turn device off. Then rebooted into recovery. It WORKED.
I think rebooting into system first rewrites TWRP with stock recovery.

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

I would like some help please

I kind of messed up. I have had no issues up till now. I have flashed Baikal os and found there were problems with youtube. I figured it was just that rom then found that every other rom I tried had the same issue. I flashed the stock Nougat (on accident mind you) and thought I could just do the update to 8.1 oreo. The issue is that it restarted into twrp. From there, I can't boot into any rom. I haven't tried stock rom but everything I have tried does not work. When twrp is finished flashing both the rom and gapps, I clean (sometimes not) the cache and restart into system. It keeps rebooting into twrp instead of into the rom. What should I do? I have never had this issue before...
Update: I can only boot into my phone if I boot from the bootloader. I can't boot from recovery, like clicking on boot into system from recovery.
Update # 2: using the tool by drtechie, I flashed the Oreo stock firmware/rom. The issue is that even with the recovery wiped, something keeps making my phone try to boot into recovery. I got the screen for people who dont have a custom recovery installed. Still clueless. Getting desperate because I kind of want my g5 plus back...
Factory reset your phone from twrp
I don't understand exactly what you are trying to say but if your problem is "Twrp bootloop means no matter what you do you are not able to get out from twrp" than type this in twrp terminal
In twrp terminal :
dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
And again reboot to recovery. Flash any rom now you will be able to boot into system

Phone stuck in bootloop!

So i started to update viper4android and i accidentally pressed volume up which tries it to install via AROMA now my phone is stuck on bootloop, it just keeps rebooting to recovery trying to install the viper4android, is there any possible way to get out of this or my phone is dead?
Any help will be appreciated,
TIA
a safe haven said:
So i started to update viper4android and i accidentally pressed volume up which tries it to install via AROMA now my phone is stuck on bootloop, it just keeps rebooting to recovery trying to install the viper4android, is there any possible way to get out of this or my phone is dead?
Any help will be appreciated,
TIA
Click to expand...
Click to collapse
You didn't specify your exact phone model, so assuming KLTE
AFAIK aroma does not work well with our TWRP
Can you pull the battery and then boot directly to recovery so you can wipe system/cache/Dalvik and then flash the ROM again?
If recovery is messed up, can you pull battery, then boot to download mode so you can reflash TWRP in Odin/Heimdall, or better yet flash latest stock Rom (caution if you have a g900V/A with stock locked bootloader) in Odin/Heimdall, followed by TWRP?
Post again if you need more help, and try to include as many specifics as possible eg exact phone model, TWRP version, Rom zip filename, Gapps, etc. I'll try to help if I can
I am very sorry for not posting the model number, mine is G900I (KLTEDV), everytime i turn on the phone it just keeps booting onto the recovery and goes to install the viper4android but it fails to do that and reboots again and again, its impossible to do anything basically, not booting onto the rom or anything. Recovery version is TWRP 3.2.2-0, it opens up directly to the zip file which is viper4androidfx-aroma.zip and tries to flash it and crashes and the whole process starts again, pulling the battery didnt break the chain it just keeps rebooting to do that again!
I reflashed a new twrp recovery ver 3.2.3-0, but it still tries to flash that zip file again! Even after deleting the file itself it still tries to flash it and keeps rebooting!
How do i get rid of this twrp loop!? This is so weird!
P.S: After reflashing twrp the phone boots to the rom normally but i cant access recovery anymore, whenever i go to recovery it goes on in an infinite bootloop (cleared cache and dalvik cache using es explorer root), I am also on LineageOs 16.0, tried stock recovery but the stock recovery also keeps bootlooping.
P.S this viper4android is a magisk module!
NVM, solved it by flashing stock rom! Thanks!

Categories

Resources