how to fix boot loop problem - Lenovo A7000 Questions & Answers

i try to porting rom for my device lenovo a7000 (for same chipset) by this guide
http://forum.xda-developers.com/k3-note/development/guide-porting-64bit-mtk-roms-cross-t3310605
and after porting rom itca stuck on boot so i wanted to how to solve this problem

tips you can follow:
1.remove supersu
2.firstly try replacing only etc/firmware,mddb
3.hw&egl(from both lib&lib64)
4.whole vendor folder and check if it boots
3.replace other files if u successfully booted your rom
happy porting

Related

[Q] twrp for zte nubia z9mini doesn't work

hi,every devs. i am new to compile twrp for zte nubia z9mini. i use cm12.1 source and compile successfully. but after i flash it. device can't reboot to twrp. when i try to reboot to twrp device always reboot to fastboot mod and said "no kernel(boot partition is bad)". i had use device treehttps://github.com/shouhu1993/android_device_zte_nx511j and kernel https://github.com/shouhu1993/NX511J_kernel.
i also try to use devicehttps://github.com/shouhu1993/nx511j_device that extract from boot.img in stock rom. but the same result.
i don't konw how to solve it. if you can help i would thank you a lot. sorry for bad english.
anyone help please?

Flashing CM13 Requirements

Dear All,
Please be informed that I have flashed MIUI 8 TWRP Recovery successfully, but the issue that I am not able to flash CM13 ROM because after flashing the CM13 ROM the device will stack on Mi Logo, so what I have to flash as right now I am using TWRP v3.0 with MIUI 8 v6.6.16 China Dev.
Please I need the proper boot.img and recovery.img for CM13, and the proper boot.img and recovery for both MIUI 7 and MIUI 8
Thanks.
Have you followed the installation instruction and got all the installation files from this thread (http://forum.xda-developers.com/mi-5/development/rom-cyanogenmod-13-t3402292) step-by-step?
Your problem usually results from a bad flash, either because of faulty recovery or incomplete flash.
Regarding boot and recovery images, those are included in the CM zip file. As for official versions, I suggest you to do a full Miflash flash_all, since the boot and recovery need to be matched to the correct data and system images to work properly.
Lazer Bear said:
Have you followed the installation instruction and got all the installation files from this thread (http://forum.xda-developers.com/mi-5/development/rom-cyanogenmod-13-t3402292) step-by-step?
Your problem usually results from a bad flash, either because of faulty recovery or incomplete flash.
Regarding boot and recovery images, those are included in the CM zip file. As for official versions, I suggest you to do a full Miflash flash_all, since the boot and recovery need to be matched to the correct data and system images to work properly.
Click to expand...
Click to collapse
Dear Lazer,
The issue has been solved. I have to be on MIUI 7 ROM then I can be able the flash the CM13 ROM.
Thanks.
only miui 7

Asus me170c not install update.zip

Hello,
You can solve this problem? I have a tablet Asus Me170c that recently the formate and install the official ROM (WW_V10.32.1.30.4) (asus.com/us/Tablets/ASUS_MeMO_Pad_7_ME170C/HelpDesk_Download/) by this method: (http: //forum.xda- developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466), then all is well and install the bootloader correctly, but try putting on the update.zip where is the rom from the bootloader (by renaming K01A_sdupdate.zip) and it does not work, I get to start putting android logo installing upgrade but after a few seconds I jump error.
Please can help me solve this problem and to install the official ROM that you want to install my tablet Asus ME170C.
Thanks, Greetings

After installing xpoesd in lenovo A7000 it can stuk on on boot loop

I am trying to install xposed in my lenovo A7000 but it couldn't install in my device it can bootloop my device.
I download xposed SDK21 from xda offical thread and i also try SDK22 & SDK23 but it couldn't install
in all SDK21,22,23 files arm,arm64 and x86 all try but couldn't install. arm and x86 give error update and arm 64 install successfully but it can stuck on boot
any dev. find solution for it .
Why did you try all. You just should not randomly try out everything. You should flash only things which are made for your cpu architecture. If your Lenovo a7000 phone is running marshmallow you must flash sdk23 and arm64 only. Also there in an uninstaller zip which you must flash if it gets stuck somewhere
It is easy to flash by following simple steps.dont need any backups,never fall into bootloop.first download xposedv78arm64.zip via XDA link And place it on SDcard.dont forget to dwnld the uninstaller.Because sometimes u face any problems simply uninstall it.Now enter into your Custom recovery (TWRP recommended)Now flash the zip.then clean cache/dalvik then reboot system.sometimes the boot takes upto5-10minutes so keep calm.after booted download Xposed installer apk install it and enjoy Custom ROM experience via module's.

[GUIDE] [F.A.Q.] [chef] [TREBLE] Common Hurdles and Solutions for First Timers!

This thread is meant to address all the common hurdles that are commonly faced by people who are new to treble devices (chef to be specific) and help them to troubleshoot/avoid some small yet critical steps during flashing new ROMs and working with fastboot and recovery in general. It will be continually updated with new stuff as it goes along.
I will be referring to the Motorola One Power and Moto P30 Note as chef only from now on.
The unlocking guide is available in This XDA Thread!
IMPORTANT:
1. Flashing refers to the process of doing a clean flash, with the inclusion of fastboot -w command
2. Latest ADB and Fastboot drivers are required to be installed, else the installation may halt mid-way.
3. Stock ROM refers to the Android One ROM for the Motorola One Power [XT 1942-2]
IMPORTANT: AS OF RIGHT NOW, PEOPLE WHO HAVE INSTALLED STOCK PIE (EITHER VIA UPDATE OR FIRMWARE) WILL NOT BE ABLE TO USE ANY OTHER ROM OTHER THAN THE STOCK PIE ROM. RADIO INTERFACE LAYER IS BROKEN IN OREO SOURCE BUILT ROMS AND THAT CURRENTLY INCLUDES LINEAGE 16 SO PLEASE WAIT FOR PIE SOURCE CODE FROM MOTOROLA FOR THAT TO BE FIXED.
1. I unlocked my chef . How do I flash TWRP in place of the stock recovery?
Solution:Currently you cannot as there is no recovery partition in the device. You have to manually boot TWRP onto the device using fastboot to use it. Follow as directed:
Boot the device into fastboot mode
Use command fastboot boot <path/to/TWRP.img> to boot TWRP temporarily.
2. I am done with TWRP and I want to flash Lineage OS 16 on my chef. I simply flash the .zip archive right?
Solution:No. Before you flash anything,
Take a backup of atleast your EFS and PERSIST partitions using TWRP and off-load it for safekeeping to restore in future if needed. You can also trigger a full backup if you require.
SUPER IMPORTANT: Flash this .zip file to copy the System A/B partitions. If this step is skipped, you will be responsible to brick your own device. THIS STEP IS ONLY REQUIRED ONCE AND ONLY ONCE IN THE LIFETIME OF YOUR DEVICE! YOU WON'T BE NEEDING THIS THE NEXT TIME YOU FLASH ANY ROM. .
After that, flash your dearest custom ROM and get going.
For Lineage OS 16, follow This XDA Thread.​
3. I am done testing LOS 16, I want to flash a GSI. Shall I use a stock Vendor Image for the GSI on my chef?
Solution:No. The stock Vendor image is causing bootloop issue in most GSIs. It is recommended to use Lineage OS Vendor to flash a GSI on chef. So flash LOS and then flash your favourite GSI.
Also, Super Important: for those who haven't used lineage before flahing a GSI, it is required to boot Lineage OS first before flashing a GSI. ​
4. I am done experimenting, I want to go back to the stock image. How do I proceed?
Solution:Follow this XDA thread for it. And don't install OTA updates directly from the device. It will come in the next step.​
5. I want to install OTA updates on the stock ROM. How do I proceed?
Solution:Follow this XDA post for it. The installation process is described here. You have to be clever enough to get the appropriate OTA update. ​
Credits:
@erfanoabdi : TWRP, LOS 16, AB partition management
@rushiranpise : Unlocking guide
@dayask : Testing the process, guide for reflashing stock ROM
@nageen9211 : Testing ROMs
For any additional queries, feel free to contact us at our Telegram Group
For more regular updates, follow our Telegram Channel
Always remember: You have to be smarter than your smartphone to be able to use it!
Cheers and Happy Flashing!​
Note to readers
The above guide is for stock kernels only (including lineage)
The custom Darkone Kernel has constant updates and fixes major bugs often. Please follow the linked thread to test it out if you want to. Cheers!
Anyone have flashed GSI ROM? FOr me after flash GSI HavocOS have bootloop :/
DIdn't flash copy system A/B partitions, stuck on bootloop with custom roms.
Watched some youtube videos and didn't read this post before flashing custom ROM. Flashed Custom ROM without flashing A/B partitions. Now I have a phone stuck on bootloop when done anything in TWRP. or I can use my phone with stock ROM installed by fastboot method.
Installing or restoring anything from TWRP results in boot loop.
Restoring the backup I made before flashing, completes the restoration process normally. But when rebooting to system, TWRP prompts me that no OS is installed. If I reboot anyway, its either stuck on bootloop or reboots to recovery and asks me to try again or factory reset, or boots into bootloader mode.
Installing custom ROM begins with Step 1, takes a bit time and starts step 2 and shows completed. Doesn't echos any comments. But when i reboot, same prompt shows saying no OS installed. Reboot anyway and stuck on bootloop or reboots to recovery and aks me to try again or factory reset, or boots into bootloader mode.
Now I installed stock ROM with fastboot method and phone is boots up into system just fine.
Sometimes TWRP can't mount anything.
So am I stuck with stock rom or is there any solutions?
Also, installing stock ROM with fastboot mode showed this error in between scripts
(bootloader) is-logical:xxx_a: not found
and
(bootloader) is-logical:xxx_b: not found
but is able to use the phone just fine with stock ROM.

Categories

Resources